[pkg-fso-maint] debian: issues with latest packed fso

[arne anka]

>> - fso needs probably some better detection for recamping
>
> If I read correctly upstream bug
>
>   https://docs.openmoko.org/trac/ticket/1024#comment:55
>
> various workarounds should be available for it,

where do you read that? (and how do you know which commenbt is #55?)
afaiu, the workaround is disabling deep sleep, ie using SLEEP=2, in fso it  
is achieved by

ti_calypso_deep_sleep = never

in frameworkd.conf.

> is this not the case for
> Debian?  And if you do not experience the same bug with fso images, do
> you know what is different in Debian?

i am not sure, i understand, what you're saying -- but i was referring not  
to fso images (never used those) but to the older debian package.
my understanding is, that fso tries to detect by itself if the phone is  
prone to #1024, and accordingly enables or disables deep sleep.
 from my experinece that detection does not work (reliably).
inhowfar improvements were made in newer fso versions, i can't say.


> However, according to
>
>   http://totalueberwachung.de/blog/2009/06/03/freerunner-deep-sleep-standby-time
>
> Openmoko bug #1024 there should be a "final" workaround.

disabling deep sleep.  according to joerg(?) the standby time may increase  
by up to 25% with a hw fix, but improving power management in the kernel  
will yield better over all results.
nevertheless, if i get hold of someone able to do that, i certainly will  
get the hw fix (the usual bigger capacitator) since my fr suffers badly  
 from #1024.