What %

---

Hi again...what should be the % of the android os it should be in order that you guys find it acceptable and really good...range wise


Thanks

Originally Posted by spupuz

same for me ... it was the same also for nuhetri-reloadedv2.3.0 when i did applied the toggles dunno why.... wildestpixel any hints on that?

my theory

why because no aosp 4.0.4 is out only stock port and then all the source code mod like notificacion widgets and that stuff is taken from 4.0.3 framework returning the bug

but the dev has said is only a bug shows miscalculation and no affect batery life im not sure of belive that in any case the batery life with bug and no bug is not as big. you can do another changes to policy , kernel and that to have a great batery life

Originally Posted by pikerumx

my theory

why because no aosp 4.0.4 is out only stock port and then all the source code mod like notificacion widgets and that stuff is taken from 4.0.3 framework returning the bug

but the dev has said is only a bug shows miscalculation and no affect batery life im not sure of belive that in any case the batery life with bug and no bug is not as big. you can do another changes to policy , kernel and that to have a great batery life

actually i'm not able to determine if the battery life is the same or not with bug and without so i will probably flash only slim an then try how is the battery.

---------- Post added at 03:23 PM ---------- Previous post was at 03:05 PM ----------

as found in other posts:

That's because the framework used in the MOD is from the previous version (4.0.3), as far as I know.
Anyway people shouldn't really care much about it as it doesn't affect battery life at all.
It's just a bug that shows miscalculation as explained by Dianne Hackborn, an Android dev.

Hi, sorry it took me so long to provide the source link of Dianne's article.
I've got it now.
You can read it here: https://plus.google.com/105051985738...ts/FV3LVtdVxPT

And I think this one post, also by her, explains everything:

"Dianne Hackborn - Prior to 4.0, there were no wake locks computed for Android OS. It is now just the dumping ground for all of the time the device was awake that wasn't otherwise blamed on someone. So it is (total awake time) - (total app/system wake lock time) - (total screen on time).

There was also a bug that was my fault in 4.0.0-4.0.3 where this was computed incorrectly and would add the screen on time instead of subtract it.
Jan 18, 2012"

Note the one that I bolded.
It was a bug in 4.0.0 to 4.0.3.
It's been fixed in 4.0.4 as you can see it yourself.
But the MOD uses 4.0.3 framework, that's why the Android OS bug returns.

CMIIW

I don't know if it's related, but after updating from 1.5 to 1.6, at least one app that I purchased on Android Market is listed as "not available for your device." Did anything change at this end that might have caused this?

Sent from my Nexus S using xda premium

Originally Posted by glennkaonang

Hi, sorry it took me so long to provide the source link of Dianne's article.
I've got it now.
You can read it here: https://plus.google.com/105051985738...ts/FV3LVtdVxPT

And I think this one post, also by her, explains everything:

"Dianne Hackborn - Prior to 4.0, there were no wake locks computed for Android OS. It is now just the dumping ground for all of the time the device was awake that wasn't otherwise blamed on someone. So it is (total awake time) - (total app/system wake lock time) - (total screen on time).

There was also a bug that was my fault in 4.0.0-4.0.3 where this was computed incorrectly and would add the screen on time instead of subtract it.
Jan 18, 2012"

Note the one that I bolded.
It was a bug in 4.0.0 to 4.0.3.
It's been fixed in 4.0.4 as you can see it yourself.
But the MOD uses 4.0.3 framework, that's why the Android OS bug returns.

CMIIW

ok you point it, in any case Battery Life in 4.0.3 and 4.0.4 is so bad :7

Originally Posted by satthienthan1

Hi wildestpixel

You can mod for volume button open lock screen. Because now i only use power button open the lock screen i afraid power button broken.

Sorry for bad english

+1

Inviato dal mio Nexus S usando Tapatalk

Just to show I don't think the calculation bug is an issue I'm a heavy user and here are my stats:





Sent from my Nexus S using Tapatalk

is there any fix for yellow blink screen after pressing sleep/power button? i9020A?

Originally Posted by vigorito

is there any fix for yellow blink screen after pressing sleep/power button? i9020A?

Use voodoo control app to change rgb values and the flicker goes.

Sent from my Nexus S using xda premium