maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Nokia N900 (https://talk.maemo.org/forumdisplay.php?f=44)
-   -   High Battery Consumption in Standby (https://talk.maemo.org/showthread.php?t=70436)

StocChr 2011-03-01 10:23

Re: High Battery Consumption
 
ok i will give it a try
you don't need the output from top?

vi_ 2011-03-01 10:27

Re: High Battery Consumption
 
no, just the output from powertop

StocChr 2011-03-01 10:42

Re: High Battery Consumption
 
C2 is always more...

Code:

Nokia-N900:~# powertop
Powertop 1.13.3
status: Unknown job: pmtrackerdaemon
Sleeping for 6 seconds before sampling
Collecting data for 30 seconds
Sample interval was 00m 30s 8941us

C#      | Ratio  | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
    C0 |  7.9% |          |  1150 MHz |  nan% |
    C1 |  92.1% |  135.5ms |
    C2 |  0.0% |          |
    C3 |  0.0% |          |
    C4 |  0.0% |          |

IRQ#    | Activity  | Type          | Name
--------+------------+----------------+---------------------------
    37 |        431 |          INTC | gp
    56 |        212 |          INTC | i2c_omap
    86 |        69 |          INTC | mmc1
    12 |        54 |          INTC | DMA
    57 |        46 |          INTC | i2c_omap
    21 |          9 |          INTC | SGX

PID#    | Activity  | Name          | Function Entry (Expire)
--------+------------+----------------+---------------------------
      0 |        363 |  <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
  3510 |        19 |    osso-xterm | schedule_hrtimeout_range (hrtimer_wakeup)
    647 |        18 |          dsme | __enqueue_rt_entity (sched_rt_period_timer)
      0 |        11 |  <kernel core> | hrtimer_start (tick_sched_timer)
    684 |          7 |      bme_RX-51 | sys_timer_settime (posix_timer_fn)
    567 |          6 |          mmcqd | queue_delayed_work (delayed_work_timer_fn)
    567 |          6 |          mmcqd | schedule_timeout (process_timeout)
    843 |          3 |          Xorg | queue_delayed_work (delayed_work_timer_fn)
    684 |          3 |      bme_RX-51 | schedule_timeout (process_timeout)
    647 |          3 |          dsme | do_nanosleep (hrtimer_wakeup)
    793 |          2 |      sgx_perf | queue_delayed_work (delayed_work_timer_fn)
      1 |          2 |  <kernel core> | queue_delayed_work (delayed_work_timer_fn)
    684 |          2 |      bme_RX-51 | sys_timer_settime (posix_timer_fn)
    684 |          2 |      bme_RX-51 | do_nanosleep (hrtimer_wakeup)
    673 |          2D|<kernel module> | queue_delayed_work (delayed_work_timer_fn)
    843 |          1 |          Xorg | hrtimer_start (it_real_fn)
  3610 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
  3624 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
  3638 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
  3652 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
  3666 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
  3680 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
  3694 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
  1139 |          1 |    hildon-home | queue_delayed_work (delayed_work_timer_fn)
  3708 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
  3722 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
    751 |          1 |            sh | setup_wb_timer (wb_timer_fn)
    14 |          1 |        pdflush | blk_plug_device (blk_unplug_timeout)
    567 |          1 |          mmcqd | schedule_timeout (process_timeout)
  3736 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
  1492 |          1 |tracker-indexer | schedule_hrtimeout_range (hrtimer_wakeup)
  1492 |          1 |tracker-indexer | journal_get_write_access (commit_timeout)
  3750 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
  3764 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
  3778 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
  3792 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
  3566 |          1 |      powertop | do_nanosleep (hrtimer_wakeup)

Power domain activity breakdown
Domain  | % of time spent in states
--------+---------+---------+---------+---------+----------
usbhost |OFF:  0%|RET: 100%|INA:  0%| ON:  0%| now:(RET)
    sgx |OFF:  97%|RET:  0%|INA:  0%| ON:  2%| now:(OFF)
    per |OFF:  0%|RET:  0%|INA:  0%| ON: 100%| now:(ON)
    dss |OFF:  0%|RET: 100%|INA:  0%| ON:  0%| now:(RET)
    cam |OFF:  0%|RET: 100%|INA:  0%| ON:  0%| now:(RET)
  core |OFF:  0%|RET:  0%|INA:  0%| ON: 100%| now:(ON)
  neon |OFF:  0%|RET:  0%|INA:  0%| ON: 100%| now:(ON)
    mpu |OFF:  0%|RET:  0%|INA:  0%| ON: 100%| 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
        |
  ckgen |          CORE |          PERI |          96M
        |          48M |          12M |          54M
        |      EMU_CORE |
    per |        GPIO2 |        GPIO3 |        GPIO4
        |        GPIO5 |        GPIO6 |

Total wakeups  1292,  43.1/s | IRQ  821,  27.4/s | Timers  471,  15.7/s
HW wakeups        0,  0.0/s |    Real gp_timers expired  175,  5.8/s


zimon 2011-03-01 10:50

Re: High Battery Consumption
 
dmesg | tail
and
tail /tmp/Xorg.0.log
...can also give hints what is wrong and using CPU all the time.

StocChr 2011-03-01 10:51

Re: High Battery Consumption
 
2 Attachment(s)
attached you can find the package lists

thegodfaather 2011-03-01 10:56

Re: High Battery Consumption
 
Dude .. in my N900, to save battery i have reduced the screen brightness to pt 2 & have disabled the touch vibration .. these things showed me a greater impact on my n900 battery life though i dont use 3g here

for more info visit <removed>

StocChr 2011-03-01 11:00

Re: High Battery Consumption
 
1 Attachment(s)
Xorg.0.log attached...

Quote:

Nokia-N900:~# dmesg | tail
[ 1494.503814] wlan0: Trigger new scan to find an IBSS to join
[ 1495.503753] kb_lock (GPIO 113) is now closed
[ 1495.745880] kb_lock (GPIO 113) is now open
[ 1498.902191] wlan0: Trigger new scan to find an IBSS to join
[ 1499.347503] wlan0: Creating new IBSS network, BSSID ba:64:15:ee:09:ae
[ 1500.456207] wlan0 reports beacon loss when not associated
[ 1500.722412] wlan0: no IPv6 routers present
[ 1564.097473] kb_lock (GPIO 113) is now closed
[ 1564.245880] kb_lock (GPIO 113) is now open
[ 1568.370880] slide (GPIO 71) is now open

vi_ 2011-03-01 11:09

Re: High Battery Consumption
 
Why do you have both battery graph AND battery eye installed, you are running an extra daemon than you need.

kernel power settings is still listed in that list, heavily implying you have not uninstalled it.

In fact I see a whole raft of things you where asked to remove before we started this whole troubleshooting procedure.

I give up. I can't do this. You didn't even click the thanks button.

StocChr 2011-03-01 11:11

Re: High Battery Consumption
 
hey dude, i check the packagelist

there are MANY packages i already uninstalled, today and months ago!!!

trust me!

vi_ 2011-03-01 11:12

Re: High Battery Consumption
 
UNINSTALL ALL FLASHLIGHT PROGRAMS, FMTX WIDGET, LENS COVER REMINDER, KERNEL POWER SETTINGS, ADVANCED POWER, MYMENU AND WTF THIS IS: offscr-anglemeter 1.0.1

THESE PROGRAMS POLL THE HARDWARE.
LIKE I KEPT SAYING!!!
OMG.

FFS.

MEGA F/PALM

/vi_

vi_ 2011-03-01 11:13

Re: High Battery Consumption
 
http://talk.maemo.org/showpost.php?p...3&postcount=72

StocChr 2011-03-01 11:15

Re: High Battery Consumption
 
advanced-power 0.4.2-4 user/desktop 188
advanced-power-monitor 0.5.3-3 user/utilities 216
ati85 1.4.1-1 user/science 2059
battery-eye 0.8-0pre1 user/utilities 204
com-ea-app-nfsuc 20.0.28 user/games 116200
community-ssu-enabler 0.6-5 user/system 84
docstogo 2.000.315 user/hidden 8152
drnoksnes 1.3.4 user/games 1260
fastsmsevo 0.1-7 user/utilities 64
flashlight-applet 0.4-5 user/desktop 284
flashlight-extra 0.1-3 user/desktop 152
flashlight-extra-gtk 0.2 user/desktop 96
kernel-power-settings 0.11 user/system 140

and many others

StocChr 2011-03-01 11:16

Re: High Battery Consumption
 
Quote:

Originally Posted by vi_ (Post 958001)
UNINSTALL ALL FLASHLIGHT PROGRAMS, FMTX WIDGET, LENS COVER REMINDER, KERNEL POWER SETTINGS, ADVANCED POWER, MYMENU AND WTF THIS IS: offscr-anglemeter 1.0.1

THESE PROGRAMS POLL THE HARDWARE.
LIKE I KEPT SAYING!!!
OMG.

FFS.

MEGA F/PALM

/vi_

already uninstalled these things, no idea why this **** is listening in the package list

StocChr 2011-03-01 11:33

Re: High Battery Consumption
 
packages only disappear when i type for example:

dpkg -P kernel-power-settings

vi_ 2011-03-01 11:33

Re: High Battery Consumption
 
ok sorry bro, I was outta my mind.

I cannot further trouble shoot this problem remotely. My only advice is to re-flash emmc and rootfs. This will give you a clean system. Fear not though, you have learned a great deal about what programs you like and which you don't. After a re-flash, you will know exactly what you want to install and how to customise the machine to your likening.

Don't fear the re-flash. I hosed my n900 in about 2 days when I got it. The next install lasted about a week. Then a month later I needed a re-flash again! My current install has lasted around a month now and is stable and safe. This is all part of the learning process.

When you reach a stable safe system, install backupmenu by robbiethe1st, make a backup of your system to your mmc then the next time (if ever again) you need to revert you can just revert to the backup.


Remember re-flash rootfs AND emmc.

Good luck.

StocChr 2011-03-01 11:37

Re: High Battery Consumption
 
damn it... i flashed my n900 three or four times... i know what these means,
much work, that the system is like now

slender 2011-03-01 12:35

Re: High Battery Consumption
 
Quote:

Originally Posted by StocChr (Post 958029)
damn it... i flashed my n900 three or four times... i know what these means,
much work, that the system is like now

You have problem exactly because you have system that is like now. Backup PIM data and restore it but do not restore applications from backup.

Try to restore default kernel. Btw do you have micro sd card inserted?

StocChr 2011-03-01 12:42

Re: High Battery Consumption
 
micro sd... normally yes, these forenoon no

efekt 2011-03-01 13:02

Re: High Battery Consumption
 
Quote:

Originally Posted by StocChr (Post 957842)
hello,

i installed battery graph and watched the battery over night:
8.00pm-10.00pm: charging
10.00pm-7.30am: handy idle
7.30am-8.00am: telephon call
8.00am: automatically shut down

12 hours standby and 0,5 hour voice call and the battery is dead
http://www.id-t.at/data/batterygraph.jpg

cpu usage seems to be normal!
maybe the battery should be replaced?

any other hints?

cheers

Dude, as I suggested earlier here - READ MY THREAD. I have the exact same problem, and all the solution people suggested you here were raised in my thread as well - it could've saved you A LOT of time...

StocChr 2011-03-01 13:09

Re: High Battery Consumption
 
i think that these are two different problems!
my n900 have 0% at C2 - C4
your n900 have on alle C stages %

slender 2011-03-01 13:45

Re: High Battery Consumption
 
btw.
"normal" idle usage is something like in this pic on right side:
http://img684.imageshack.us/img684/9...0100412103.png
Still some spikes from cpu that could be probably from some daemon.

Just for reference.

.edit
And when comparing remember to check x-scaling

StocChr 2011-03-01 14:13

Re: High Battery Consumption
 
BIG NEWS

after backup the full system with backupmenu and multiboot i had to reflash the stock kernel via maemo flasher

i will post the powertop output in a few minutes

i think we got it.... stay tuned

StocChr 2011-03-01 14:19

Re: High Battery Consumption
 
can someone of the pro's tell me, if the output is normal yet...
i've already made friends with a reflash,
now i'm in the conflict of conscience!!

powertop: ( no widgets, no sdcard, offline and restarted )

Code:

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 65979us

C#  | Ratio  | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
C0 |  10.0% |  |  600 MHz |  63.3% |
C1 |  0.0% |  0.2ms |  550 MHz |  0.0% |
C2 |  3.1% |  9.1ms |  500 MHz |  0.4% |
C3 |  13.2% |  146.5ms |  250 MHz |  36.3% |
C4 |  73.8% |  887.1ms |

IRQ#  | Activity  | Type  | Name
--------+------------+----------------+---------------------------
37 |  504 |  INTC | gp
56 |  204 |  INTC | i2c_omap
11 |  118 |  INTC | prcm
86 |  55 |  INTC | mmc1
57 |  41 |  INTC | i2c_omap
12 |  17 |  INTC | DMA
21 |  10 |  INTC | SGX

PID#  | Activity  | Name  | Function Entry (Expire)
--------+------------+----------------+---------------------------
0 |  440 |  <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
1 |  32D|  preinit | cpufreq_governor_dbs (delayed_work_timer_fn)
3193 |  18 |  osso-xterm | schedule_hrtimeout_range (hrtimer_wakeup)
757 |  17 |  dsme | __enqueue_rt_entity (sched_rt_period_timer)
0 |  10 |  <kernel core> | hrtimer_start (tick_sched_timer)
792 |  7 |  bme_RX-51 | sys_timer_settime (posix_timer_fn)
44 |  6 |  mmcqd | schedule_timeout (process_timeout)
44 |  4 |  mmcqd | queue_delayed_work (delayed_work_timer_fn)
936 |  2 |  Xorg | hrtimer_start (it_real_fn)
892 |  2 |  sgx_perf | queue_delayed_work (delayed_work_timer_fn)
848 |  2 |  sh | setup_wb_timer (wb_timer_fn)
757 |  2 |  dsme | do_nanosleep (hrtimer_wakeup)
1 |  2D|  <kernel core> | queue_delayed_work (delayed_work_timer_fn)
792 |  2 |  bme_RX-51 | sys_timer_settime (posix_timer_fn)
792 |  2 |  bme_RX-51 | do_nanosleep (hrtimer_wakeup)
792 |  2 |  bme_RX-51 | schedule_timeout (process_timeout)
1194 |  2 |  signond | futex_wait (hrtimer_wakeup)
3321 |  1 |  sleep | do_nanosleep (hrtimer_wakeup)
3335 |  1 |  sleep | do_nanosleep (hrtimer_wakeup)
3349 |  1 |  sleep | do_nanosleep (hrtimer_wakeup)
804 |  1 |  dbus-daemon | queue_delayed_work (delayed_work_timer_fn)
3363 |  1 |  sleep | do_nanosleep (hrtimer_wakeup)
3377 |  1 |  sleep | do_nanosleep (hrtimer_wakeup)
3391 |  1 |  sleep | do_nanosleep (hrtimer_wakeup)
3405 |  1 |  sleep | do_nanosleep (hrtimer_wakeup)
3419 |  1 |  sleep | do_nanosleep (hrtimer_wakeup)
1194 |  1 |  signond | schedule_hrtimeout_range (hrtimer_wakeup)
44 |  1 |  mmcqd | cfq_completed_request (cfq_idle_slice_timer)
3433 |  1 |  sleep | do_nanosleep (hrtimer_wakeup)
3447 |  1 |  sleep | do_nanosleep (hrtimer_wakeup)
14 |  1 |  pdflush | blk_plug_device (blk_unplug_timeout)
3461 |  1 |  sleep | do_nanosleep (hrtimer_wakeup)
3475 |  1 |  sleep | do_nanosleep (hrtimer_wakeup)
3489 |  1 |  sleep | do_nanosleep (hrtimer_wakeup)
3249 |  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:  97%|RET:  0%|INA:  0%| ON:  2%| now:(OFF) per |OFF:  86%|RET:  3%|INA:  0%| ON:  10%| 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:  73%|RET:  12%|INA:  1%| ON:  12%| now:(ON) neon |OFF:  73%|RET:  13%|INA:  3%| ON:  10%| now:(ON) mpu |OFF:  73%|RET:  13%|INA:  3%| ON:  10%| 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 |
ckgen |  CORE |  PERI |  96M
|  48M |  12M |  54M
|  EMU_CORE |
per |  GPIO2 |  GPIO3 |  GPIO4
|  GPIO5 |  GPIO6 |

Total wakeups  1519,  50.6/s | IRQ  949,  31.6/s | Timers  570,  19.0/s HW wakeups  118,  3.9/s |  Real gp_timers expired  248,  8.3/s

any hints what's now to do?!

slender 2011-03-01 14:23

Re: High Battery Consumption
 
Run powertop couple of times (to minimize margin for error) to get idle wakeups and use n900 for awhile and run powertop again. I mean that test your setup for couple of days before making any conclusions.

.edit
From here you can look for references:
http://wiki.maemo.org/N900_software_...ement#Powertop
I would say that something like ~500 wakeups and mostly in C4 state is pretty much ok for completely idle N900. This is not scientific measurement just stuff from my head.

StocChr 2011-03-01 14:27

Re: High Battery Consumption
 
ok, i will uninstall not used things
will set up the kernel power and will observe the system with powertop and batterygraph

btw. how to clean up the maemo-user-package-list

vi_ 2011-03-01 14:31

Re: High Battery Consumption
 
Please dont tell me you re-flashed both emmc and rootfs then DID NOT restore with backup menu?

StocChr 2011-03-01 14:47

Re: High Battery Consumption
 
i created a backup with backupmenu
then i flashed only the kernel

Code:

flasher-3.5 -F <firmware-image> --flash-only=kernel -f -R
no emmc no rootfs reflash

StocChr 2011-03-02 13:18

Re: High Battery Consumption
 
after several problems, i did yesterday night a full reset.
i flashed the eMMC and the rootfs

i installed all programms, overclocked, cssu, ...

Code:

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 29606us

C#      | Ratio  | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
    C0 |  0.7% |          |  1150 MHz |  nan% |
    C1 |  0.0% |          |
    C2 |  1.6% |    7.8ms |
    C3 |  4.0% |  63.4ms |
    C4 |  93.7% | 2343.4ms |

IRQ#    | Activity  | Type          | Name
--------+------------+----------------+---------------------------
    56 |        198 |          INTC | i2c_omap
    37 |        76 |          INTC | gp
    11 |        50 |          INTC | prcm
    86 |        35 |          INTC | mmc1
    57 |        22 |          INTC | i2c_omap
    21 |          9 |          INTC | SGX
    12 |          4 |          INTC | DMA

PID#    | Activity  | Name          | Function Entry (Expire)
--------+------------+----------------+---------------------------
      0 |        23 |  <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
  2205 |        19 |    osso-xterm | schedule_hrtimeout_range (hrtimer_wakeup)
      0 |        19 |  <kernel core> | hrtimer_start (tick_sched_timer)
    38 |        16D|            awk | cpufreq_governor_dbs (delayed_work_timer_fn)
    600 |          7 |          mmcqd | schedule_timeout (process_timeout)
  1018 |          4 |          Xorg | queue_delayed_work (delayed_work_timer_fn)
    897 |          4 |      bme_RX-51 | sys_timer_settime (posix_timer_fn)
    986 |          3 |      sgx_perf | queue_delayed_work (delayed_work_timer_fn)
    600 |          3 |          mmcqd | queue_delayed_work (delayed_work_timer_fn)
    678 |          3 |          dsme | do_nanosleep (hrtimer_wakeup)
    678 |          3 |          dsme | __enqueue_rt_entity (sched_rt_period_timer)
      1 |          3D|  <kernel core> | queue_delayed_work (delayed_work_timer_fn)
  1018 |          2 |          Xorg | hrtimer_start (it_real_fn)
    897 |          2 |      bme_RX-51 | sys_timer_settime (posix_timer_fn)
    897 |          2 |      bme_RX-51 | do_nanosleep (hrtimer_wakeup)
    704 |          2D|<kernel module> | queue_delayed_work (delayed_work_timer_fn)
    897 |          2 |      bme_RX-51 | schedule_timeout (process_timeout)
    30 |          1 |          mount | setup_wb_timer (wb_timer_fn)
    14 |          1 |        pdflush | blk_plug_device (blk_unplug_timeout)
    600 |          1 |          mmcqd | schedule_timeout (process_timeout)
      1 |          1 |  <kernel core> | inet_initpeers (peer_check_expire)
      0 |          1 |  <kernel core> | queue_delayed_work (delayed_work_timer_fn)
  2225 |          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:  97%|RET:  0%|INA:  0%| ON:  2%| now:(OFF)
    per |OFF:  97%|RET:  1%|INA:  0%| ON:  0%| 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:  93%|RET:  2%|INA:  0%| ON:  3%| now:(ON)
  neon |OFF:  93%|RET:  4%|INA:  1%| ON:  0%| now:(ON)
    mpu |OFF:  93%|RET:  4%|INA:  1%| ON:  0%| 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 |
  ckgen |          CORE |          PERI |          96M
        |          48M |          12M |          54M
        |      EMU_CORE |
    per |        GPIO2 |        GPIO3 |        GPIO4
        |        GPIO5 |        GPIO6 |

Total wakeups  517,  17.2/s | IRQ  394,  13.1/s | Timers  123,  4.1/s
HW wakeups      50,  1.7/s |    Real gp_timers expired  76,  2.5/s

cheers

zimon 2011-03-02 16:11

Re: High Battery Consumption
 
yes. now it seems to stay at C4 level as it should when idle.

p900 2011-03-02 17:48

Re: High Battery Consumption
 
This is my powertop output in case someone can help me find what drains my battery.
it's not a serious situation but I feel my battery can perform better (around 15% more)

Code:

Powertop 1.13.3
sh: status: not found
Sleeping for 11 seconds before sampling
Collecting data for 30 seconds
Sample interval was 00m 30s 16297us

C# | Ratio | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
C0 | 1.5% | | 600 MHz | 0.0% |
C1 | 1.3% | 3.8ms | 550 MHz | 0.0% |
C2 | 77.1% | 127.2ms | 500 MHz | 0.0% |
C3 | 14.3% | 538.2ms | 250 MHz | 100.0% |
C4 | 5.7% | 569.9ms |

IRQ# | Activity | Type | Name
--------+------------+----------------+---------------------------
57 | 289 | INTC | i2c_omap
56 | 171 | INTC | i2c_omap
37 | 161 | INTC | gp
11 | 137 | INTC | prcm
21 | 5 | INTC | SGX
86 | 2 | INTC | mmc1

PID# | Activity | Name | Function Entry (Expire)
--------+------------+----------------+---------------------------
0 | 296 | <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
38 | 86D| awk | cpufreq_governor_dbs (delayed_work_timer_fn)
1204 | 60 |hildon-status-m | schedule_hrtimeout_range (hrtimer_wakeup)
0 | 39 | <kernel core> | hrtimer_start (tick_sched_timer)
793 | 21 | mce | schedule_hrtimeout_range (hrtimer_wakeup)
3820 | 19 | osso-xterm | schedule_hrtimeout_range (hrtimer_wakeup)
709 | 12 | bme_RX-51 | sys_timer_settime (posix_timer_fn)
3786 | 8 | skyhost | futex_wait (hrtimer_wakeup)
593 | 8 | mmcqd | schedule_timeout (process_timeout)
3780 | 7 | skyhost | do_nanosleep (hrtimer_wakeup)
546 | 7 | wl12xx | schedule_timeout (process_timeout)
546 | 7 | wl12xx | queue_delayed_work (delayed_work_timer_fn)
593 | 6 | mmcqd | queue_delayed_work (delayed_work_timer_fn)
709 | 6 | bme_RX-51 | schedule_timeout (process_timeout)
10 | 4 | omap2_mcspi | inet_twsk_schedule (inet_twdr_hangman)
3771 | 4 |telepathy-pecan | schedule_hrtimeout_range (hrtimer_wakeup)
593 | 4 | mmcqd | cfq_completed_request (cfq_idle_slice_timer)
1215 | 3 | hildon-desktop | queue_delayed_work (delayed_work_timer_fn)
807 | 3 | sgx_perf | queue_delayed_work (delayed_work_timer_fn)
2801 | 3 | browserd | futex_wait (hrtimer_wakeup)
3771 | 3 |telepathy-pecan | neigh_add_timer (neigh_timer_handler)
793 | 3 | mce | tsc2005_start_scan (tsc2005_esd_timer_handler)
1258 | 3 | wlancond | ieee80211_ioctl_siwpower (ieee80211_dynamic_ps_timer)
709 | 2 | bme_RX-51 | do_nanosleep (hrtimer_wakeup)
1 | 2D| <kernel core> | queue_delayed_work (delayed_work_timer_fn)
665 | 2 | dsme | do_nanosleep (hrtimer_wakeup)
665 | 2 | dsme | __enqueue_rt_entity (sched_rt_period_timer)
862 | 1 | Xorg | hrtimer_start (it_real_fn)
862 | 1 | Xorg | queue_delayed_work (delayed_work_timer_fn)
709 | 1 | bme_RX-51 | sys_timer_settime (posix_timer_fn)
1204 | 1 |hildon-status-m | queue_delayed_work (delayed_work_timer_fn)
593 | 1 | mmcqd | schedule_timeout (process_timeout)
546 | 1 | wl12xx | schedule_timeout (process_timeout)
3771 | 1 |telepathy-pecan | sk_reset_timer (tcp_write_timer)
1 | 1 | <kernel core> | inet_initpeers (peer_check_expire)
3788 | 1 | skyhost | schedule_hrtimeout_range (hrtimer_wakeup)
3964 | 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: 99%|RET: 0%|INA: 0%| ON: 0%| now:(OFF)
per |OFF: 20%|RET: 77%|INA: 0%| ON: 2%| now:(ON)
dss |OFF: 0%|RET: 0%|INA: 0%| ON: 100%| now:(ON)
cam |OFF: 100%|RET: 0%|INA: 0%| ON: 0%| now:(OFF)
core |OFF: 0%|RET: 0%|INA: 96%| ON: 3%| now:(ON)
neon |OFF: 5%|RET: 14%|INA: 77%| ON: 2%| now:(ON)
mpu |OFF: 5%|RET: 14%|INA: 77%| ON: 2%| 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 | MMC2 |
core3 | USBTLL
wkup | GPT1 | 32KSYNC | GPIO1
| WDT1 |
ckgen | CORE | PERI | 96M
| 48M | 12M | 54M
| EMU_CORE |
dss | DSS_IDLE
per | GPIO2 | GPIO3 | GPIO4
| GPIO5 | GPIO6 |

Total wakeups 1395, 46.5/s | IRQ 765, 25.5/s | Timers 630, 21.0/s
HW wakeups 137, 4.6/s | Real gp_timers expired 161, 5.4/s
~ $


vi_ 2011-03-02 18:23

Re: High Battery Consumption
 
Quote:

Originally Posted by StocChr (Post 958842)
after several problems, i did yesterday night a full reset.
i flashed the eMMC and the rootfs

i installed all programms, overclocked, cssu, ...

Code:

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 29606us

C#      | Ratio  | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
    C0 |  0.7% |          |  1150 MHz |  nan% |
    C1 |  0.0% |          |
    C2 |  1.6% |    7.8ms |
    C3 |  4.0% |  63.4ms |
    C4 |  93.7% | 2343.4ms |

IRQ#    | Activity  | Type          | Name
--------+------------+----------------+---------------------------
    56 |        198 |          INTC | i2c_omap
    37 |        76 |          INTC | gp
    11 |        50 |          INTC | prcm
    86 |        35 |          INTC | mmc1
    57 |        22 |          INTC | i2c_omap
    21 |          9 |          INTC | SGX
    12 |          4 |          INTC | DMA

PID#    | Activity  | Name          | Function Entry (Expire)
--------+------------+----------------+---------------------------
      0 |        23 |  <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
  2205 |        19 |    osso-xterm | schedule_hrtimeout_range (hrtimer_wakeup)
      0 |        19 |  <kernel core> | hrtimer_start (tick_sched_timer)
    38 |        16D|            awk | cpufreq_governor_dbs (delayed_work_timer_fn)
    600 |          7 |          mmcqd | schedule_timeout (process_timeout)
  1018 |          4 |          Xorg | queue_delayed_work (delayed_work_timer_fn)
    897 |          4 |      bme_RX-51 | sys_timer_settime (posix_timer_fn)
    986 |          3 |      sgx_perf | queue_delayed_work (delayed_work_timer_fn)
    600 |          3 |          mmcqd | queue_delayed_work (delayed_work_timer_fn)
    678 |          3 |          dsme | do_nanosleep (hrtimer_wakeup)
    678 |          3 |          dsme | __enqueue_rt_entity (sched_rt_period_timer)
      1 |          3D|  <kernel core> | queue_delayed_work (delayed_work_timer_fn)
  1018 |          2 |          Xorg | hrtimer_start (it_real_fn)
    897 |          2 |      bme_RX-51 | sys_timer_settime (posix_timer_fn)
    897 |          2 |      bme_RX-51 | do_nanosleep (hrtimer_wakeup)
    704 |          2D|<kernel module> | queue_delayed_work (delayed_work_timer_fn)
    897 |          2 |      bme_RX-51 | schedule_timeout (process_timeout)
    30 |          1 |          mount | setup_wb_timer (wb_timer_fn)
    14 |          1 |        pdflush | blk_plug_device (blk_unplug_timeout)
    600 |          1 |          mmcqd | schedule_timeout (process_timeout)
      1 |          1 |  <kernel core> | inet_initpeers (peer_check_expire)
      0 |          1 |  <kernel core> | queue_delayed_work (delayed_work_timer_fn)
  2225 |          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:  97%|RET:  0%|INA:  0%| ON:  2%| now:(OFF)
    per |OFF:  97%|RET:  1%|INA:  0%| ON:  0%| 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:  93%|RET:  2%|INA:  0%| ON:  3%| now:(ON)
  neon |OFF:  93%|RET:  4%|INA:  1%| ON:  0%| now:(ON)
    mpu |OFF:  93%|RET:  4%|INA:  1%| ON:  0%| 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 |
  ckgen |          CORE |          PERI |          96M
        |          48M |          12M |          54M
        |      EMU_CORE |
    per |        GPIO2 |        GPIO3 |        GPIO4
        |        GPIO5 |        GPIO6 |

Total wakeups  517,  17.2/s | IRQ  394,  13.1/s | Timers  123,  4.1/s
HW wakeups      50,  1.7/s |    Real gp_timers expired  76,  2.5/s

is the cpu usage now, as it should be?

cheers


finally you got it! What you have there is about as good as you can get 'stock'. For further battery, enable smart reflex 1+2 and overclock 250-805. Don't install programs that poll the hardware or widgets that relentlessly autoupdate.

Job done.

vi_ 2011-03-02 18:32

Re: High Battery Consumption
 
Quote:

Originally Posted by p900 (Post 959046)
This is my powertop output in case someone can help me find what drains my battery.
it's not a serious situation but I feel my battery can perform better (around 15% more)

Code:

Powertop 1.13.3
sh: status: not found
Sleeping for 11 seconds before sampling
Collecting data for 30 seconds
Sample interval was 00m 30s 16297us

C# | Ratio | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
C0 | 1.5% | | 600 MHz | 0.0% |
C1 | 1.3% | 3.8ms | 550 MHz | 0.0% |
C2 | 77.1% | 127.2ms | 500 MHz | 0.0% |
C3 | 14.3% | 538.2ms | 250 MHz | 100.0% |
C4 | 5.7% | 569.9ms |

IRQ# | Activity | Type | Name
--------+------------+----------------+---------------------------
57 | 289 | INTC | i2c_omap
56 | 171 | INTC | i2c_omap
37 | 161 | INTC | gp
11 | 137 | INTC | prcm
21 | 5 | INTC | SGX
86 | 2 | INTC | mmc1

PID# | Activity | Name | Function Entry (Expire)
--------+------------+----------------+---------------------------
0 | 296 | <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
38 | 86D| awk | cpufreq_governor_dbs (delayed_work_timer_fn)
1204 | 60 |hildon-status-m | schedule_hrtimeout_range (hrtimer_wakeup)
0 | 39 | <kernel core> | hrtimer_start (tick_sched_timer)
793 | 21 | mce | schedule_hrtimeout_range (hrtimer_wakeup)
3820 | 19 | osso-xterm | schedule_hrtimeout_range (hrtimer_wakeup)
709 | 12 | bme_RX-51 | sys_timer_settime (posix_timer_fn)
3786 | 8 | skyhost | futex_wait (hrtimer_wakeup)
593 | 8 | mmcqd | schedule_timeout (process_timeout)
3780 | 7 | skyhost | do_nanosleep (hrtimer_wakeup)
546 | 7 | wl12xx | schedule_timeout (process_timeout)
546 | 7 | wl12xx | queue_delayed_work (delayed_work_timer_fn)
593 | 6 | mmcqd | queue_delayed_work (delayed_work_timer_fn)
709 | 6 | bme_RX-51 | schedule_timeout (process_timeout)
10 | 4 | omap2_mcspi | inet_twsk_schedule (inet_twdr_hangman)
3771 | 4 |telepathy-pecan | schedule_hrtimeout_range (hrtimer_wakeup)
593 | 4 | mmcqd | cfq_completed_request (cfq_idle_slice_timer)
1215 | 3 | hildon-desktop | queue_delayed_work (delayed_work_timer_fn)
807 | 3 | sgx_perf | queue_delayed_work (delayed_work_timer_fn)
2801 | 3 | browserd | futex_wait (hrtimer_wakeup)
3771 | 3 |telepathy-pecan | neigh_add_timer (neigh_timer_handler)
793 | 3 | mce | tsc2005_start_scan (tsc2005_esd_timer_handler)
1258 | 3 | wlancond | ieee80211_ioctl_siwpower (ieee80211_dynamic_ps_timer)
709 | 2 | bme_RX-51 | do_nanosleep (hrtimer_wakeup)
1 | 2D| <kernel core> | queue_delayed_work (delayed_work_timer_fn)
665 | 2 | dsme | do_nanosleep (hrtimer_wakeup)
665 | 2 | dsme | __enqueue_rt_entity (sched_rt_period_timer)
862 | 1 | Xorg | hrtimer_start (it_real_fn)
862 | 1 | Xorg | queue_delayed_work (delayed_work_timer_fn)
709 | 1 | bme_RX-51 | sys_timer_settime (posix_timer_fn)
1204 | 1 |hildon-status-m | queue_delayed_work (delayed_work_timer_fn)
593 | 1 | mmcqd | schedule_timeout (process_timeout)
546 | 1 | wl12xx | schedule_timeout (process_timeout)
3771 | 1 |telepathy-pecan | sk_reset_timer (tcp_write_timer)
1 | 1 | <kernel core> | inet_initpeers (peer_check_expire)
3788 | 1 | skyhost | schedule_hrtimeout_range (hrtimer_wakeup)
3964 | 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: 99%|RET: 0%|INA: 0%| ON: 0%| now:(OFF)
per |OFF: 20%|RET: 77%|INA: 0%| ON: 2%| now:(ON)
dss |OFF: 0%|RET: 0%|INA: 0%| ON: 100%| now:(ON)
cam |OFF: 100%|RET: 0%|INA: 0%| ON: 0%| now:(OFF)
core |OFF: 0%|RET: 0%|INA: 96%| ON: 3%| now:(ON)
neon |OFF: 5%|RET: 14%|INA: 77%| ON: 2%| now:(ON)
mpu |OFF: 5%|RET: 14%|INA: 77%| ON: 2%| 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 | MMC2 |
core3 | USBTLL
wkup | GPT1 | 32KSYNC | GPIO1
| WDT1 |
ckgen | CORE | PERI | 96M
| 48M | 12M | 54M
| EMU_CORE |
dss | DSS_IDLE
per | GPIO2 | GPIO3 | GPIO4
| GPIO5 | GPIO6 |

Total wakeups 1395, 46.5/s | IRQ 765, 25.5/s | Timers 630, 21.0/s
HW wakeups 137, 4.6/s | Real gp_timers expired 161, 5.4/s
~ $



there are not enough picard f/palms in the world for this.

do EVERYTHING that was explained to the last guy including 'the procedure'. Come back, tell us what you have done and post your results. Only then can we trouble shoot.

egoshin 2011-03-02 19:17

Re: High Battery Consumption
 
Well, I didn't read the whole thread but from initial "top" output it seems the problem with hildon-home again. It can loop if some modification is done in "Application" menu. Or it is related with installation of some group application menu software, please search forum.

Temporal 2011-03-03 06:17

Re: High Battery Consumption
 
Did you install flashlight-extra, camkeyd or dbus-switchboard? I would BET that any of these are your bad guys. If flashlight-extra is installed, you'll need to do this:
http://talk.maemo.org/showpost.php?p...p;postcount=19

StocChr 2011-03-03 06:53

Re: High Battery Consumption
 
Quote:

Originally Posted by vi_ (Post 959066)
finally you got it! What you have there is about as good as you can get 'stock'. For further battery, enable smart reflex 1+2 and overclock 250-805. Don't install programs that poll the hardware or widgets that relentlessly autoupdate.

Job done.

i played with smartreflex with following results:

250-850MHz: device reboot after enabling smartreflex
250-805MHz: device runs smooth without reboots

what does smartreflex exactly do? why it doenst run with 850MHz?
what about ignore nice load? 0 or 1?

cheers

EDIT: my kernel configuration

Code:

MINFREQ=250
MAXFREQ=805
FREQS="0:30,90 250:38,180 500:48,360 550:48,400 600:54,430 700:54,430 750:54,430 805:54,430 850:54,500 900:54,500 950:54,500 1000:60,500 1100:72,520 1150:72,520 "
SMARTREFLEX_VDD1=1
SMARTREFLEX_VDD2=1
GOVERNOR=ondemand
IGNORE_NICE_LOAD=0
UP_THRESHOLD=75
SAMPLING_RATE=150000
POWERSAVE_BIAS=0


udaychaitanya16 2011-03-03 07:09

Re: High Battery Consumption
 
please somebody with a good battery life post the output of powertop here so that people like me will get a chance to further decipher wt is going with our batteries.Thank you.

StocChr 2011-03-03 07:12

Re: High Battery Consumption
 
Quote:

Originally Posted by udaychaitanya16 (Post 959447)
please somebody with a good battery life post the output of powertop here so that people like me will get a chance to further decipher wt is going with our batteries.Thank you.

http://talk.maemo.org/showpost.php?p...2&postcount=70

StocChr 2011-03-03 09:14

Re: High Battery Consumption
 
Quote:

Originally Posted by vi_ (Post 959066)
finally you got it! What you have there is about as good as you can get 'stock'. For further battery, enable smart reflex 1+2 and overclock 250-805. Don't install programs that poll the hardware or widgets that relentlessly autoupdate.

Job done.

i played with smartreflex with following results:

250-850MHz: device reboot after enabling smartreflex
250-805MHz: device runs smooth without reboots

what does smartreflex exactly do? why it doenst run with 850MHz?
what about ignore nice load? 0 or 1?

cheers

EDIT: my kernel configuration

Code:

MINFREQ=250
MAXFREQ=805
FREQS="0:30,90 250:38,180 500:48,360 550:48,400 600:54,430 700:54,430 750:54,430 805:54,430 850:54,500 900:54,500 950:54,500 1000:60,500 1100:72,520 1150:72,520 "
SMARTREFLEX_VDD1=1
SMARTREFLEX_VDD2=1
GOVERNOR=ondemand
IGNORE_NICE_LOAD=0
UP_THRESHOLD=75
SAMPLING_RATE=150000
POWERSAVE_BIAS=0


bman 2011-03-03 09:54

Re: High Battery Consumption
 
i reflashed my phone recently and slowly started adding apps back on
and watching 2 see if any cause high cpu usgae when idle as i had that problem b4
i got to flash light extra hexahop and kanban and got high cpu usage so uninstalled kanban and hexahop and still had high cpu so uninstalled flash light extra and it stopped
i then installed flash light extra gtk version and cpu looked fine for a few hrs so installed hexahop and kanban and then got high cpu usage again so uninstalled both of them again and was still high cpu usage so uninstalled flash light extra gtk aswell and still having high cpu usage when the phone is idle
yet b4 i installed those apps it was running perfect not using any cpu usage unless i unlocked it and used it
now over night its draining the bttery real fast and battery graph is showing steady cpu usage while it should be doing nothing ??
is there settings left behind that can cause this?


Code:

home/user # powertop
Powertop 1.13.3
status: Unknown job: pmtrackerdaemon
Sleeping for 11 seconds before sampling
Collecting data for 30 seconds
Sample interval was 30m 30s 19867us

C#      | Ratio  | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
    C0 |  98.5% |          |  1150 MHz |  nan% |
    C1 |  0.0% |    0.4ms |
    C2 |  0.1% |    8.6ms |
    C3 |  0.4% |  164.6ms |
    C4 |  1.1% |  922.5ms |

IRQ#    | Activity  | Type          | Name
--------+------------+----------------+---------------------------
    37 |        442 |          INTC | gp
    56 |        236 |          INTC | i2c_omap
    11 |        170 |          INTC | prcm
    86 |        89 |          INTC | mmc1
    57 |        30 |          INTC | i2c_omap
    12 |        24 |          INTC | DMA
    225 |        14 |          GPIO | omap2-onenand
    21 |          9 |          INTC | SGX

PID#    | Activity  | Name          | Function Entry (Expire)
--------+------------+----------------+---------------------------
      0 |        364 |  <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
    38 |        47D|            awk | cpufreq_governor_dbs (delayed_work_timer_fn)
      0 |        22 |  <kernel core> | hrtimer_start (tick_sched_timer)
  3374 |        19 |    osso-xterm | schedule_hrtimeout_range (hrtimer_wakeup)
    668 |        19 |          dsme | __enqueue_rt_entity (sched_rt_period_timer)
    581 |        17 |          mmcqd | schedule_timeout (process_timeout)
    707 |          7 |      bme_RX-51 | sys_timer_settime (posix_timer_fn)
    581 |          5 |          mmcqd | queue_delayed_work (delayed_work_timer_fn)
  1008 |          3 |          Xorg | queue_delayed_work (delayed_work_timer_fn)
    707 |          3 |      bme_RX-51 | schedule_timeout (process_timeout)
    962 |          2 |      sgx_perf | queue_delayed_work (delayed_work_timer_fn)
      1 |          2D|  <kernel core> | queue_delayed_work (delayed_work_timer_fn)
    707 |          2 |      bme_RX-51 | sys_timer_settime (posix_timer_fn)
    707 |          2 |      bme_RX-51 | do_nanosleep (hrtimer_wakeup)
  1246 |          2 |        signond | futex_wait (hrtimer_wakeup)
  1352 |          2 |  BatteryGraphd | start_this_handle (commit_timeout)
    668 |          2 |          dsme | do_nanosleep (hrtimer_wakeup)
    30 |          2 |          mount | setup_wb_timer (wb_timer_fn)
  3565 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
  1246 |          1 |        signond | schedule_hrtimeout_range (hrtimer_wakeup)
  3579 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
  3593 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
  1352 |          1 |  BatteryGraphd | schedule_hrtimeout_range (hrtimer_wakeup)
  3607 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
  3621 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
  3635 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
  1352 |          1 |  BatteryGraphd | ubifs_wbuf_write_nolock (wbuf_timer_callback_nolock)
  3649 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
    693 |          1D|<kernel module> | queue_delayed_work (delayed_work_timer_fn)
  3663 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
  3677 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
      1 |          1 |  <kernel core> | inet_initpeers (peer_check_expire)
  3691 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
    934 |          1 |            mce | schedule_hrtimeout_range (hrtimer_wakeup)
  2307 |          1 |      browserd | futex_wait (hrtimer_wakeup)
  3705 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
  3719 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
  3733 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
  1032 |          1 | hald-addon-bme | schedule_hrtimeout_range (hrtimer_wakeup)
  3479 |          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:  97%|RET:  0%|INA:  0%| ON:  2%| now:(OFF)
    per |OFF:  86%|RET:  5%|INA:  0%| ON:  7%| 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:  64%|RET:  20%|INA:  1%| ON:  12%| now:(ON)
  neon |OFF:  64%|RET:  22%|INA:  5%| ON:  7%| now:(ON)
    mpu |OFF:  64%|RET:  22%|INA:  5%| ON:  7%| 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 |
  ckgen |          CORE |          PERI |          96M
        |          48M |          12M |          54M
        |      EMU_CORE |
    per |        GPIO2 |        GPIO3 |        GPIO4
        |        GPIO5 |        GPIO6 |

Total wakeups  1558,  51.9/s | IRQ 1014,  33.8/s | Timers  544,  18.1/s
HW wakeups      170,  5.7/s |    Real gp_timers expired  186,  6.2/s


vi_ 2011-03-03 11:41

Re: High Battery Consumption
 
Quote:

Originally Posted by StocChr (Post 959440)
i played with smartreflex with following results:

250-850MHz: device reboot after enabling smartreflex
250-805MHz: device runs smooth without reboots

what does smartreflex exactly do? why it doenst run with 850MHz?
what about ignore nice load? 0 or 1?

cheers

EDIT: my kernel configuration

Code:

MINFREQ=250
MAXFREQ=805
FREQS="0:30,90 250:38,180 500:48,360 550:48,400 600:54,430 700:54,430 750:54,430 805:54,430 850:54,500 900:54,500 950:54,500 1000:60,500 1100:72,520 1150:72,520 "
SMARTREFLEX_VDD1=1
SMARTREFLEX_VDD2=1
GOVERNOR=ondemand
IGNORE_NICE_LOAD=0
UP_THRESHOLD=75
SAMPLING_RATE=150000
POWERSAVE_BIAS=0


This talks about smartreflex.

Think of smart relfex as a scaling for the cpu voltage. How exactly it interacts with undervolting I am not sure, however from my own mesaurable results (with battery graph) I can see that the best way to minimise the gradient of the mAh curve is by using SR 1+2 and overclocking 250/805.

Unfortunatley 805 is the maximum you can overclock with SR enabled so you will have to choose, SR+max cpu of 805 or no SR and max CPU of 1150 (or whatever you hardware can take).

I for one have two schemes. 'profile':SR1+2 ON,CPU@250-500 with starving voltages and 'overclock':SR1+2 OFF,CPU@500-1000 with starving voltages.


All times are GMT. The time now is 18:18.

vBulletin® Version 3.8.8