On Monday, August 26, 2013 01:17:09 PM Radek Polak wrote: > > To give you a simple example: on N900 maemo you have "scanning period" in > > settings-internet, which makes device scan for WLAN APs only every 5, 10, > > ... even 30 min. This is needed since the WLAN chip cuts thru the battery > > in less than 3 hours when you constantly scan for APs. Clearly a userland > > issue where kernel can't do much. Now you can start to blame kernel WLAN > > driver for not doing proper powersaving but that won't help establish a > > decently working usable OS on N900. > > I think in case of QtMoko on GTA04 we can blame kernel/HW a little bit > more, since we are using suspend to RAM whereas N900 is always on (which > really cool btw). So while GTA04 is in standby there should be idealy just > PMU+RAM+modem turned on, everything else should be off. But something is > wrong and noone has yet figured what it is. At best there is ~16mA with > omap enable_off_mode - but then we hit "imprecise external abort" bug so > currently we have ~22mA at best. If you compare this with GTA02 or N900 > it's really bad. GTA02 is 12mA and i'd say N900 is even better. Together > with reenumerating modem it makes GTA04 barely usable even for a few > hardcore supporters but unusable for normal users.
Btw you can try even with bare rootfs. E.g. Neil Brown is running very bare debian with just some custom made phone app, but the power consumption is the same - and it's quite expected because all the userspace is stopped in suspend. Regards Radek
_______________________________________________ Openmoko community mailing list email@example.com http://lists.openmoko.org/mailman/listinfo/community