Re-registering to GSM network
prishelec at gmail.com
Tue Oct 21 00:23:43 CEST 2008
Yes, it checks for reregistering, and this is a good solution right now. But
for the future I would like to have a possibility to configure that
I know that my phone behaves like this, so I would like to issue this SLEEP
command during turning my phone on and forget about bouncing. I don't want
to wait for it to reregister 5 times before going quiet. And in an hour
again. What if someone would be calling during that time? I will loose the
I know this is just a workaround but I think we can add an options like
'auto', 'sleep2' and 'sleep4' in a future. sleep2 - for people who are sure
that they have this problem, sleep4 for those who are sure they doesn't, and
'auto' for those who doesn't know yet (default behavior like now) :)
Right now I just modified unsolicited.py, to issue SLEEP=2 once and not to
issue SLEEP=4. And I don't have reregistering problem at all.
On Mon, Oct 20, 2008 at 11:53 AM, Alastair Johnson
<alastair at truebox.co.uk>wrote:
> arne anka wrote:
> >> In bug #1024 mickey and also mwester talked about the power consumption
> >> of this change... Quoting one of the comments you can read:
> >>> While this increases power consumption, it will make a significant
> >>> difference to all people who want to use their Neo as a day-to-day
> >>> phone.
> > i certainly hope, the use of that fix is configurable, then!
> > i never had re-registering problems and with suspens/resume i get a
> > battery life time of about 3 to 4 days now ...
> A quick look at the fix in FSO suggests it only uses SLEEP=2 if it sees
> frequent reregistration, and reverts to SLEEP=4 after an hour anyway. If
> you never see frequent reregistration then SLEEP=2 will never be
> enabled. I think the mwester patch for qtopia does the same thing.
> support mailing list
> support at lists.openmoko.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the support