On Fri, 18 Jul 2008 15:12:45 +0200 Joerg Reisenweber <[EMAIL PROTECTED]> babbled:
> Am Fr 18. Juli 2008 schrieb arne anka: > > > Touchscreen is not a "wake from suspend" source, so as you suggest it > > > didn't get to suspend to make this trouble. > > > > not sure i understand you correctly, but several times i experience that > > the fr, while seemingly in suspended state, answers to a screen tap > > showing several console messages (whihte font, black background) and then > > switching to the lock screen. > > > > otoh, what i meant was: when the fr frequently wakes up the screen becomes > > sensitive and any tap would prevent the fr from going back to suspend -- > > so if in one of these moments of short resumes the screen ist tapped and > > again and again the fr would never resume thus draining the battery > > quickliy. > > And what is it that stops us from disabling ts, just reenabling it when we > see a valid wake-source to stay in user-land (e.g. inbound call, RTC, > powerbutton...)? no kernel mechanism to "power down" ts (like you can power down bluetooth for example)? :) -- Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> _______________________________________________ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community