maemo.org - Talk - 400% battery performance improvement?

maemo.org - Talk (https://talk.maemo.org/index.php)

- Nokia N900 (https://talk.maemo.org/forumdisplay.php?f=44)

- - 400% battery performance improvement? (https://talk.maemo.org/showthread.php?t=84038)

400% battery performance improvement?

This is freaking me out!:eek:

My N900 used to have terrible battery life. 3-4 hours max. really crappy. I talk all about it in this thread

Suddenly, yesterday I noticed it had gone ~8 hours and still had juice. Today, 14 hours after I took it off the charger, it still reports 35% battery. This is after 9 months of crappy battery life.

WhhaawwtThaFaaarrk? 400% increase?!?

Why is this? I'm afraid to reboot it else the magic will escape!

Anyone care to speculate on this? I'm really interested in folks ideas on this.

Here's some stats & observation.:

Last updates I ran were over a month ago.
Been running overclocked at 250-850MHz.
All hardware is turned on.
all repos enabled
Not running much; wifi, ssh, X. CPU is at <10%.
Same standard BL-5j battery for months.
Other than battery life, it has run perfectly.
it used to run very warm to the touch, always.
now it stays cool to the touch

I started poking around and found lots of this in the syslog:

Code:

[39710.458679] bq27x00-battery 2-0055: battery is not calibrated! ignoring capacity values

[39715.800842] bq27x00-battery 2-0055: battery is not calibrated! ignoring capacity values

[39720.871185] bq27x00-battery 2-0055: battery is not calibrated! ignoring capacity values

And for comparison (see my other thread), here's typical top output:

Code:

Mem: 142680K used, 92580K free, 0K shrd, 396K buff, 28824K cached

CPU:  2.4% usr  5.7% sys  0.0% nic 91.3% idle  0.0% io  0.0% irq  0.3% sirq

Load average: 0.03 0.09 0.09 1/298 20788

  PID  PPID USER     STAT   RSS %MEM %CPU COMMAND

20347 17426 root     R      728  0.3  1.7 top

30369 30360 user     S      672  0.2  1.7 top

   10     2 root     SW       0  0.0  1.5 [omap2_mcspi]

13687 13659 root     S      696  0.3  1.1 top

  948     1 root     S     6888  2.9  0.5 /usr/sbin/ohmd --no-daemon

17228 17181 root     S     1840  0.7  0.5 {sshd} sshd: root@pts/4

here's what powertop says:

Code:

[1|root@Nokia-N900|~]powertop

Powertop 1.13.3

status: Unknown job: pmtrackerdaemon

Sleeping for 11 seconds before sampling

Collecting data for 30 seconds

Sample interval was 00m 30s 33264us



C#      | Ratio  | Avg/dura | Frequency | Ratio

--------+--------+----------+-----------+--------+

     C0 |   4.2% |          |  1150 MHz |   nan% |

     C1 |   0.0% |    0.5ms | 

     C2 |   1.0% |    3.3ms | 

     C3 |   8.6% |  199.6ms | 

     C4 |  86.1% | 1521.0ms | 



IRQ#    | Activity   | Type           | Name

--------+------------+----------------+---------------------------

     37 |        239 |           INTC | gp

     57 |        234 |           INTC | i2c_omap

     11 |        109 |           INTC | prcm

     56 |         90 |           INTC | i2c_omap

     12 |         80 |           INTC | DMA

    202 |          5 |           GPIO | wl1251



PID#    | Activity   | Name           | Function Entry (Expire)

--------+------------+----------------+---------------------------

      0 |          8 |  <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)

  18954 |          3D|  kernel-config | cpufreq_governor_dbs (delayed_work_timer_fn)

    693 |          1 |           dsme | __enqueue_rt_entity (sched_rt_period_timer)

    552 |          1 |         wl12xx | queue_delayed_work (delayed_work_timer_fn)

      0 |          1 |  <kernel core> | hrtimer_start (tick_sched_timer)

    977 |          1 |            mce | tsc2005_start_scan (tsc2005_esd_timer_handler)

  20072 |          1 |       powertop | do_nanosleep (hrtimer_wakeup)



Power domain activity breakdown

Domain  | % of time spent in states

--------+---------+---------+---------+---------+----------

usbhost |OFF: 100%|RET:   0%|INA:   0%| ON:   0%| now:(OFF)

    sgx |OFF: 100%|RET:   0%|INA:   0%| ON:   0%| now:(OFF)

    per |OFF:  94%|RET:   0%|INA:   0%| ON:   4%| now:(ON)

    dss |OFF: 100%|RET:   0%|INA:   0%| ON:   0%| now:(OFF)

    cam |OFF: 100%|RET:   0%|INA:   0%| ON:   0%| now:(OFF)

   core |OFF:  86%|RET:   8%|INA:   0%| ON:   4%| now:(ON)

   neon |OFF:  86%|RET:   8%|INA:   0%| ON:   4%| now:(ON)

    mpu |OFF:  86%|RET:   8%|INA:   0%| ON:   4%| now:(ON)

   iva2 |OFF: 100%|RET:   0%|INA:   0%| ON:   0%| now:(OFF)



Clock activity breakdown at end of period

Domain  | Active clocks

--------+---------------+---------------+------------------

   core |          SDRC | HSOTGUSB_IDLE |      OMAPCTRL 

        |     MAILBOXES |

   wkup |          GPT1 |       32KSYNC |         GPIO1 

        |          WDT1 |           SR1 |           SR2 

        |

  ckgen |          CORE |          PERI |           96M 

        |           48M |           12M |           54M 

        |      EMU_CORE |

    per |         GPIO2 |         GPIO3 |         GPIO4 

        |         GPIO5 |         GPIO6 |



Total wakeups   773,  25.8/s | IRQ  757,  25.2/s | Timers   16,   0.5/s

HW wakeups      109,   3.6/s |     Real gp_timers expired  239,   8.0/s

Here's lshal for the battery:

Code:

[1|root@Nokia-N900|~]lshal -s -u '/org/freedesktop/Hal/devices/computer_power_supply_battery_bq27200_0'

udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_bq27200_0'

  battery.charge_level.current = 0  (0x0)  (int)

  battery.charge_level.design = 2056  (0x808)  (int)

  battery.charge_level.last_full = 0  (0x0)  (int)

  battery.charge_level.percentage = 0  (0x0)  (int)

  battery.charge_level.rate = 117  (0x75)  (int)

  battery.is_rechargeable = true  (bool)

  battery.present = true  (bool)

  battery.rechargeable.is_charging = false  (bool)

  battery.rechargeable.is_discharging = true  (bool)

  battery.reporting.current = 1637  (0x665)  (int)

  battery.reporting.design = 2056  (0x808)  (int)

  battery.reporting.rate = 117  (0x75)  (int)

  battery.reporting.technology = 'Li-ion'  (string)

  battery.reporting.unit = 'mAh'  (string)

  battery.technology = 'lithium-ion'  (string)

  battery.type = 'primary'  (string)

  battery.voltage.current = 3593  (0xe09)  (int)

  info.capabilities = {'battery'} (string list)

  info.category = 'battery'  (string)

  info.parent = '/org/freedesktop/Hal/devices/computer'  (string)

  info.product = 'Generic Battery Device'  (string)

  info.subsystem = 'power_supply'  (string)

  info.udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_bq27200_0'  (string)

  linux.hotplug_type = 2  (0x2)  (int)

  linux.subsystem = 'power_supply'  (string)

  linux.sysfs_path = '/sys/class/power_supply/bq27200-0'  (string)

what do you think is going on with this? lemme know if you'd like any other info.

Re: 400% battery performance improvement?

There are many possible causes of crappy battery life that might invisibly go away, and they are discussed in the many battery life threads. One of my favorites is the cell phone switching from one type of signal to another.

Re: 400% battery performance improvement?

i have similar experience with NITdroid...

more then 5hrs of On-screen(continual use till battery cry for recharge) time and 4hrs on wifi hotspot... more then 15hrs on normal use...
and it was cold too as you mentioned

the reason i felt for it was 'heapsize' which was not set by me so it ws '20m' only & no swap...

after changing both of them i.e heapsize to '36m' & enabling swap.. NITDROID BECAME A MAMMAL i.e always hot & hungry ;)
this is what i observed, it might be wrong

so is there a similar concept of heapsize in maemo too

Re: 400% battery performance improvement?

@knoxy420,

What kernel are you using?
Are you loading the bq27x00_battery module?

Can you remember if you did anything in these last days that might have affected the kernel?

Re: 400% battery performance improvement?

Every BL-5J has a chip inside which keeps track of the amount of charge a battery can hold. It seems like yours was off by a large amount or simply defect.

You can re-calibrate it yourself or purchase a new battery if the one you're currently using does turn out to be defect.
http://talk.maemo.org/showpost.php?p...&postcount=846
http://talk.maemo.org/showpost.php?p...postcount=1176

Re: 400% battery performance improvement?

you're aware that the speed patch is generally not considered good?

Re: 400% battery performance improvement?

Quote:

Originally Posted by qhubekela (Post 1201223)

you're aware that the speed patch is generally not considered good?

This has nothing to do with speedpatch (hopefully!) as his battery was even draining while the phone was off (probably ACTDEAD anyway..)

Re: 400% battery performance improvement?

Quote:

Originally Posted by reinob (Post 1201184)

@knoxy420,

What kernel are you using?
Are you loading the bq27x00_battery module?

Can you remember if you did anything in these last days that might have affacted the kernel?

Running kernel:

Code:

Linux Nokia-N900 2.6.28.10-power50 #1 PREEMPT Sun Mar 18 20:10:56 EET 2012 armv7l GNU/Linux

bq27x00 is loaded:

Code:

[1|root@Nokia-N900|~]lsmod

Module                  Size  Used by

bq27x00_battery         6480  0 

power_supply            6916  1 bq27x00_battery

I haven't done any updates/hacking on the phone in over a month.

One day it would die quickly. Now it lasts all day.

Re: 400% battery performance improvement?

Quote:

Originally Posted by ffha (Post 1201209)

I have 2 bl5js. Both exhibited the poor battery life. I haven't tried my spare since this one got "better". Given the junk about battery calibration in syslog, I'd say something changed.

Re: 400% battery performance improvement?

Quote:

Originally Posted by reinob (Post 1201250)

This has nothing to do with speedpatch (hopefully!) as his battery was even draining while the phone was off (probably ACTDEAD anyway..)

I do have speed patch & battery patch installed from back when I didn't know any better. However the battery life issues were the same with a clean reflash.

Whatever was eating batteries was generating a large amount of heat so that the phone was always noticibly warm. I figured there was a short somewhere or something.