Thomas Zimmermann <[email protected]> writes:
> Only .conf in /etc/freesmartphone are insteresting.
>
> So just set loglevel there :)
FWIW, I wonder/suspect if some of these weird "so-and-so doesn't work
after suspend" bugs are attributable to filesystem corruption.
I had never experienced "no GSM after suspend" before, but a couple of
days ago my FR starting suffering from this 100% reliably. So I went to
/etc/freesmartphone to look for places to set loglevel, and in the
process of that discovered an "Input/output error" on one of the files
there. (I think it was the gpsd pickle file; unfortunately I don't
still have the details.)
I also noticed that, once the FR had got into a bad "no GSM" state:
- the GSM modem was actually still fine - shown by normal-sounding GSM
interference on my car radio
- the FR would never suspend again (obvious leading to quick battery
drainage)
- shutdown was unusually slow, and/or it took too shutdown instructions
(using the Quick Settings) to get the FR to actually shut down.
I think this all points to a software problem (rather than anything in
the GSM chip), caused by some key file(s) being corrupted, and maybe
more specifically something that leaves the FR being confused about its
suspend/resume state. (e.g. in some sense the resume did not complete
100%)
However, even more than the details above, it suggests to me that people
experiencing such bugs should check their root filesystem for
corruption, and hence that it would be good to provide a way to make it
very easy for them to do that. I'm afraid I don't have a specific
suggestion for that, but maybe someone else has?
Regards,
Neil
_______________________________________________
Shr-User mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-user
