-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said: > Am Fr 21. März 2008 schrieb Andy Green: >>> Yep, i see. But we have to drive the LCM anyway during call, no? >> I don't know why we do that when it is just illuminating your earlobes. > > There has to be a way (=button, =LCM) to end the call at least ;-) > Sure it's not nice to have CPU running full power for some task that can be > done in GSM chipset (though i'm not sure this is a common feature for these > chips. Maybe we really need a specialized chip for this), but switching off > display is sth that can be done only while you really have the phone pressed > to your ear - there are all kinds of user interaction (e.g. Hold, > Mute/Volume, DTMF) and usefull info (e.g. duration, BattState) during > established call, that need a working LCM. We have no keyboard! Just TS. > You're not suggesting an interface-free phone you have to shake or sth to end > the call?
I wonder if it can track in which orientation you hold the phone while you are speaking, and wake the CPU and display when this changes beyond some threshold. One way or another moving the phone from your ear to where you can see the display to change states (or even see the battery state or call duration or buttons for DTMF or volume) is a "gesture" we can detect and react to by waking the CPU. > However, to throttle down the CPU while call sure is a good thing, that's > worth looking for different ways to cancel echo. Well we can think about it some more, but the biggest win can come when we suspend the CPU, it is the natural first goal I think. And because the GSM stuff is so autonomous already and interaction during a call is relatively rare, it seems possible. - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFH5BapOjLpvpq7dMoRAncgAJ90hMoEetVbQP33mncd4yX9n1euawCfefVE esUBiLgc2yAkvAdO3o0w9B0= =J6JN -----END PGP SIGNATURE-----
