[debian/fso] phonefsod: unpredictable pin dialog and questions abot config options

[Klaus Kurzmann]

Am Freitag 22 Januar 2010 18:52:58 schrieb arne anka:
> within normal operation (runlevel) phonefsod does not work predicatble.
> small changes in the phonefsod.conf made it stop entirely (w/o any useful
> info in the log despite DEBUG) and small changes in eg fsodeviced seemed
> to fix that ...
> 
> what looks far more confusing to me is, that phonefsod always gets a lower
> pid than fsodeviced, fsousage or frameworkd -- despite being started later
> according to the number assigned in /etc/rc3.d:
> S01dbus
> ...
> S02fso-deviced
> S02fso-frameworkd
> ...
> S03phonefsod
> 
> since accessing (activating?) the gsm means, one of the otheres has to be
> activae already.
> 
> but after a few repeated tests, a reliable way to make phonefsod to pop
> the pin dialog seems to be:
> - stop everything (fso and maybe dbus), i do that by swithcing to runlevel
> two which does not start anything
> - manually start dbus, fso-deviced and fso-frameworkd
> /etc/init.d/dbus start ; /etc/init.d/fso-frameworkd start
> - let cook slowly
> - after a few minutes tart everything else, i do that with
> init 3
> which starts X and phonefsod
> - pin dialog will pop up every time
> 
> but that certainly is no way to go in case of an emergency reboot or
> similar ...
> to me it looks either like one of the timeout issues again -- in zhone,
> neil worked around that by retrying until eventually the registration
> would be possible.
> or phonefsod starts far too fast and fails to access the not yet available
> gsm, never recovering from that disappointment.
hmm, strange thing. This is exactly what we intend to do... retry to access 
FSO until it appears on the scene... and then list the resources and register 
GSM if it is there... if not, wait for the signal that the GSM resource 
appeared.

> 
> in the course of actions, i was wondering about the phonefsod.conf (yes, i
> read the comments):
> - "should ophonekitd try to activate GSM on startup" -- what does
> ophonekitd has to do with phonefsod.conf?
ouch - nothing :P don't remember if that part of the conf came from ophonekitd 
and I forgot to adjust the comment or if I was still used to the old name when 
writing that comment. Should read phonefsod.

> - gsm_reregister_timeout = 60 -- what does "reregister" mean here? when is
> the first registering attempted?
reregister kicks in when you are without network coverage. Either on start or 
afterwards. It determines the seconds how often to schedule a try to register 
to the network. This is needed, because we don't get notified if some usable 
network (re-)appears.

> - "when to show idle screen" -- disabling the associated option does not
> disable the idle screen at all and there's no parameter to disable
Disabling it lets the default kick in, which is aux,lock. Try if setting it to 
an empty string works. Should.

> - auto_suspend = [never|normal|always] -- what part does "auto suspend"
> refer to? the freerunner as such? a resource? what is the difference
> between "normal" and "always"?
suspend to mem the complete device. Not refering to a specific resource. It is 
using FSO for that (org.freesmartphone.Usage.Suspend). Normal does _not_ 
suspend the device while the battery is getting charged. Always does suspend 
it even then.

-- 
Klaus 'mrmoku' Kurzmann