2.100.17 Battery life

[Guest thenext1]

So, welcome to the first publicly available battery life report for the 2.100.17 firmware :huh:

Here was my daily usage yesterday:

09h Disconnect from mains plug. Reboot.

11h 1 minute call

13h 30 minutes WiFi browsing

13:15 Battery icon had already gone down 1 step

18h Received 2 SMS

21-22h Light 3G usage (VERY light: only msn chatting), and 1 small app downloaded from Market

21:05 Second battery icon step gone

22h 3 minute call

02h Battery icon is halved

02h-02:30 WiFi browsing

02-09h Sleeping with radio on, wifi off, data off

This morning the battery was at the yellow level and 17% charge.

Am I the cause, or battery life just sucks again?

Note that data is always off when I don't use it, and I'm almost always under 3G coverage.

thank you

[Guest gi4257]

So, welcome to the first publicly available battery life report for the 2.100.17 firmware :huh:

Here was my daily usage yesterday:

09h Disconnect from mains plug. Reboot.

11h 1 minute call

13h 30 minutes WiFi browsing

13:15 Battery icon had already gone down 1 step

18h Received 2 SMS

21-22h Light 3G usage (VERY light: only msn chatting), and 1 small app downloaded from Market

21:05 Second battery icon step gone

22h 3 minute call

02h Battery icon is halved

02h-02:30 WiFi browsing

02-09h Sleeping with radio on, wifi off, data off

This morning the battery was at the yellow level and 17% charge.

Am I the cause, or battery life just sucks again?

Note that data is always off when I don't use it, and I'm almost always under 3G coverage.

thank you

I installed 2.100.07 with malez and pph oc 920. I use setcpu with profiles (temperature and screen off => lowest frequency). I didn't notice any battery drain, at least not more than before

[Guest thenext1]

I installed 2.100.07 with malez and pph oc 920. I use setcpu with profiles (temperature and screen off => lowest frequency). I didn't notice any battery drain, at least not more than before

Last time with 1.000.39 I used it much harder, like 3-4 hours of browsing a day, and it lasted more... I'm baffled

EDIT: I noticed that "Android System" is always high in battery usage...like 98% android system 2% idle.. this must be a bug

Edited September 3, 2010 by thenext1

[Guest mmick]

Last time with 1.000.39 I used it much harder, like 3-4 hours of browsing a day, and it lasted more... I'm baffled

EDIT: I noticed that "Android System" is always high in battery usage...like 98% android system 2% idle.. this must be a bug

I also don´t know what is happening but on every ROM I have "Android System" is consuming a lot. Both LS2.1, LCR1.8.0.1 and on .39.

Why does it use so much energy? Shouldn´t the system rest when I´m doing...nothing?

[Guest ginja]

it's me or whenever a new updates comes out it's always battery issues again, it's a freaking SMARTPHONE, what do you expect from it???????????????

[Guest thenext1]

it's me or whenever a new updates comes out it's always battery issues again, it's a freaking SMARTPHONE, what do you expect from it???????????????

Battery life is on the fall since 2.1 has come out.

I would expect being able to make 2 days out of it, at least, when using it so lightly. Have a friend that's still on 1.6 and he makes 3-4 days with about the same usage pattern (in his words, but since he works and I'm a student, i think he uses the phone more than i do)

Edited September 3, 2010 by thenext1

[Guest Riekr]

i can confirm 3-4 days when i was on 1.6 (on old lcr1.6 also 2-3 days), the point is not what i would expect from a smartphone but which is the best combination of components to achieve a longer battery life which make everyone happy :huh:

[Guest thenext1]

I'll try that option "wipe battery stats" on the recovery menu...when the phone has finished charging

[Guest jayziac]

I didn't notice anything change in terms of battery use from previous 2.1 roms. I still get about 3-4 days with EDGE data, off during sleep. And no extra services running in the background except the required 'GTalkService' and keyboard IME. I think you may have a runaway process/app that is eating up the battery.

[Guest thenext1]

I didn't notice anything change in terms of battery use from previous 2.1 roms. I still get about 3-4 days with EDGE data, off during sleep. And no extra services running in the background except the required 'GTalkService' and keyboard IME. I think you may have a runaway process/app that is eating up the battery.

I don't have any tasks either..no sync jobs (I don't sync data with google), no periodic checks, etc..only a widget displaying the credit left on my simcard that updates every 1hr (when internet is accessible!)

I don't have processes runnning at fuull cpu

I have just charged my battery to 100% using my desktop computer, so it charges slower and better (i think so), and "wiped the battery stats" on the recovery

We'll see in a day or two

[Guest vikings123]

I don't have any tasks either..no sync jobs (I don't sync data with google), no periodic checks, etc..only a widget displaying the credit left on my simcard that updates every 1hr (when internet is accessible!)

I don't have processes runnning at fuull cpu

I have just charged my battery to 100% using my desktop computer, so it charges slower and better (i think so), and "wiped the battery stats" on the recovery

We'll see in a day or two

I got the same feeling (no accurate measurement of usage) that the new ROM drains battery faster than previous versions.

It used to last more than one day for previous version. It can only last less than 16 hours.

[Guest Brins0]

I got the same feeling (no accurate measurement of usage) that the new ROM drains battery faster than previous versions.

It used to last more than one day for previous version. It can only last less than 16 hours.

I must say, I've noticed far faster battery drain, and a consistently high process usage for the android system process. For now, despite the overwhelmingly high performance increase, I've dropped back to the old 2.1 rom I was using.

Edit: I also noticed that the 'Dialer' process was using a lot of CPU time as well...

Edited September 4, 2010 by Brins0

[Guest matroska]

Hi guys,

the problem with android system draining all the battery is the proximity sensor. It has never been fixed so far. I would suggest to deactivate proximity sensor through settings -> phone -> advanced settings -> sensibility sensor (and deactivate it).

Let me know if you solve the problem.

Aldo

[Guest thenext1]

Hi guys,

the problem with android system draining all the battery is the proximity sensor. It has never been fixed so far. I would suggest to deactivate proximity sensor through settings -> phone -> advanced settings -> sensibility sensor (and deactivate it).

Let me know if you solve the problem.

Aldo

Let's also try that, thank you

[Guest vikings123]

Hi guys,

the problem with android system draining all the battery is the proximity sensor. It has never been fixed so far. I would suggest to deactivate proximity sensor through settings -> phone -> advanced settings -> sensibility sensor (and deactivate it).

Let me know if you solve the problem.

Aldo

I tried that and found no significant improvement.

[Guest thenext1]

I tried that and found no significant improvement.

I also tried this and this might have made a little difference in standby discharge rates. Also, now "standby" is correctly the 1st item in the battery usage screen, instead of "android system".

After this and the "wipe battery stats" thing, my battery lasted a little more than 2 days (but with even lighter use)

[Guest rmyorston]

I got my Acer Liquid a couple of weeks ago. After playing with it all day I left it in standby fully charged. The next morning it had lost about a third of its charge. Disappointing.

After much Googling and experimentation I think the issue I was seeing is the one reported in this bug:

Issue 443: LocationManagerService doesn't release its partial wakelock

It seems that there's a race condition in the location manager which (sometimes) results in a wake lock being held even after all applications that were using the location service have exited. When this happens the phone can't sleep and because it's the location manager that's holding the wake lock the time is accounted to Android System.

Since finding out about this I've been very cautious when using any apps that use the location service. After closing such apps I check that the wake lock isn't being held (using the battery history information available via the Spare Parts app or dialling *#*#4636#*#*). Often it isn't, but sometimes it is. When it is the only way I know to fix the resulting battery drain is to reboot the phone.

The bug is reported to be fixed in Froyo.

[Guest thenext1]

I got my Acer Liquid a couple of weeks ago. After playing with it all day I left it in standby fully charged. The next morning it had lost about a third of its charge. Disappointing.

After much Googling and experimentation I think the issue I was seeing is the one reported in this bug:

Issue 443: LocationManagerService doesn't release its partial wakelock

It seems that there's a race condition in the location manager which (sometimes) results in a wake lock being held even after all applications that were using the location service have exited. When this happens the phone can't sleep and because it's the location manager that's holding the wake lock the time is accounted to Android System.

Since finding out about this I've been very cautious when using any apps that use the location service. After closing such apps I check that the wake lock isn't being held (using the battery history information available via the Spare Parts app or dialling *#*#4636#*#*). Often it isn't, but sometimes it is. When it is the only way I know to fix the resulting battery drain is to reboot the phone.

The bug is reported to be fixed in Froyo.

That one is an old 2009 bug and it was already fixed by the time of last October, as you can see from the replies.

To "solve" that Battery Usage weirdness (i quoted Solve because it doesn't seem to affect to battery life very much) try to disable the P-sensor under call settings => advanced settings. Then, just press the power button while calling to turn off the screen. Yes it's a non-solution but hey we're experimenting...

[Guest rmyorston]

That one is an old 2009 bug and it was already fixed by the time of last October, as you can see from the replies.

It was fixed in October last year, both in CyanogenMod and Google's version. But Google fixed it in the Froyo branch (follow the link in comment 8 of the bug report). 2.100.17 is based on Eclair so it has the bug.

[Guest mmick]

It was fixed in October last year, both in CyanogenMod and Google's version. But Google fixed it in the Froyo branch (follow the link in comment 8 of the bug report). 2.100.17 is based on Eclair so it has the bug.

What´s the difference between 1.100.xx and 2.100.xx?