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)

vi_ 2011-03-03 11:44

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.

Quote:

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
This is an ideal powertop output. Bear in mind though that this is in offline mode. When connected to the GSM network you can probably expect around 700-800 wakeups over the 30 second period.

vi_ 2011-03-03 11:46

Re: High Battery Consumption
 
Quote:

Originally Posted by bman (Post 959548)
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


Do the procedure as detailed earlier in this thread and come back. Then we can talk.

bman 2011-03-04 22:44

Re: High Battery Consumption
 
i did follow your procedure
offline mode
battery out
keep in offline mode
wait 4 mins
load xterm n power top
run and lock screen
wait 50 sec
then copied n pasted??

after posting this i finished reading the thread and saw about flashlight extra doesnt uninstall all settings so done that rebooted and is now working good again

udaychaitanya16 2011-03-05 12:31

Re: High Battery Consumption
 
@vi_ This is the output after exactly following the procedure specified by you.I am on kernel version 46.I have two homescreens.No flashlight.Disabled the OM weather widget before taking this.I have been having horrible battery life like 9 hrs max.I never complained though.please help me find out the culprit. Powertop 1.13.3
status: Unknown job: pmtrackerdaemon
Sleeping for 11 seconds before sampling
Collecting data for 30 seconds
Sample interval was 30m 30s 28625us

C# | Ratio | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
C0 | 98.4% | | 1150 MHz | nan% |
C1 | 0.0% | 0.8ms |
C2 | 0.1% | 14.6ms |
C3 | 0.2% | 56.2ms |
C4 | 1.3% | 698.0ms |

IRQ# | Activity | Type | Name
--------+------------+----------------+---------------------------
56 | 432 | INTC | i2c_omap
86 | 267 | INTC | mmc1
12 | 179 | INTC | DMA
37 | 98 | INTC | gp
11 | 66 | INTC | prcm
57 | 24 | INTC | i2c_omap
21 | 9 | INTC | SGX
225 | 1 | GPIO | omap2-onenand

PID# | Activity | Name | Function Entry (Expire)
--------+------------+----------------+---------------------------
0 | 41 | <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
38 | 25D| awk | cpufreq_governor_dbs (delayed_work_timer_fn)
0 | 20 | <kernel core> | hrtimer_start (tick_sched_timer)
1548 | 19 | osso-xterm | schedule_hrtimeout_range (hrtimer_wakeup)
584 | 13 | mmcqd | queue_delayed_work (delayed_work_timer_fn)
706 | 6 | bme_RX-51 | sys_timer_settime (posix_timer_fn)
844 | 4 | Xorg | queue_delayed_work (delayed_work_timer_fn)
803 | 3 | sgx_perf | queue_delayed_work (delayed_work_timer_fn)
30 | 3 | mount | setup_wb_timer (wb_timer_fn)
1533 | 2 | pdflush | blk_plug_device (blk_unplug_timeout)
771 | 2 | mce | schedule_hrtimeout_range (hrtimer_wakeup)
666 | 2 | dsme | do_nanosleep (hrtimer_wakeup)
666 | 2 | dsme | __enqueue_rt_entity (sched_rt_period_timer)
706 | 2 | bme_RX-51 | sys_timer_settime (posix_timer_fn)
706 | 2 | bme_RX-51 | do_nanosleep (hrtimer_wakeup)
706 | 2 | bme_RX-51 | schedule_timeout (process_timeout)
695 | 2D|<kernel module> | queue_delayed_work (delayed_work_timer_fn)
1 | 2D| <kernel core> | queue_delayed_work (delayed_work_timer_fn)
844 | 1 | Xorg | hrtimer_start (it_real_fn)
1323 | 1 |mafw-dbus-wrapp | queue_delayed_work (delayed_work_timer_fn)
1502 | 1 | browserd | futex_wait (hrtimer_wakeup)
1441 | 1 |tracker-indexer | schedule_hrtimeout_range (hrtimer_wakeup)
1441 | 1 |tracker-indexer | journal_get_write_access (commit_timeout)
1533 | 1 | pdflush | journal_get_write_access (commit_timeout)
1554 | 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: 12%|INA: 0%| ON: 1%| 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: 79%|RET: 5%|INA: 0%| ON: 15%| now:(ON)
neon |OFF: 81%|RET: 10%|INA: 7%| ON: 1%| now:(ON)
mpu |OFF: 81%|RET: 10%|INA: 7%| ON: 1%| 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 1235, 41.2/s | IRQ 1076, 35.9/s | Timers 159, 5.3/s
HW wakeups 66, 2.2/s | Real gp_timers expired 98, 3.3/s
cheers.

zimon 2011-03-05 14:24

Re: High Battery Consumption
 
If you enclose copy+paste from terminal, please use CODE-tags, like below:

Quote:

Originally Posted by udaychaitanya16 (Post 961158)
@vi_ This is the output after exactly following the procedure specified by you.I am on kernel version 46.I have two homescreens.No flashlight.Disabled the OM weather widget before taking this.I have been having horrible battery life like 9 hrs max.I never complained though.please help me find out the culprit.

Code:

Powertop 1.13.3
status: Unknown job: pmtrackerdaemon
Sleeping for 11 seconds before sampling
Collecting data for 30 seconds
Sample interval was 30m 30s 28625us

C#      | Ratio  | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
    C0 |  98.4% |          |  1150 MHz |  nan% |
    C1 |  0.0% |    0.8ms |
    C2 |  0.1% |  14.6ms |
    C3 |  0.2% |  56.2ms |
    C4 |  1.3% |  698.0ms |

IRQ#    | Activity  | Type          | Name
--------+------------+----------------+---------------------------
    56 |        432 |          INTC | i2c_omap
    86 |        267 |          INTC | mmc1
    12 |        179 |          INTC | DMA
    37 |        98 |          INTC | gp
    11 |        66 |          INTC | prcm
    57 |        24 |          INTC | i2c_omap
    21 |          9 |          INTC | SGX
    225 |          1 |          GPIO | omap2-onenand

PID#    | Activity  | Name          | Function Entry (Expire)
--------+------------+----------------+---------------------------
      0 |        41 |  <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
    38 |        25D|            awk | cpufreq_governor_dbs (delayed_work_timer_fn)
      0 |        20 |  <kernel core> | hrtimer_start (tick_sched_timer)
  1548 |        19 |    osso-xterm | schedule_hrtimeout_range (hrtimer_wakeup)
    584 |        13 |          mmcqd | queue_delayed_work (delayed_work_timer_fn)
    706 |          6 |      bme_RX-51 | sys_timer_settime (posix_timer_fn)
    844 |          4 |          Xorg | queue_delayed_work (delayed_work_timer_fn)
    803 |          3 |      sgx_perf | queue_delayed_work (delayed_work_timer_fn)
    30 |          3 |          mount | setup_wb_timer (wb_timer_fn)
  1533 |          2 |        pdflush | blk_plug_device (blk_unplug_timeout)
    771 |          2 |            mce | schedule_hrtimeout_range (hrtimer_wakeup)
    666 |          2 |          dsme | do_nanosleep (hrtimer_wakeup)
    666 |          2 |          dsme | __enqueue_rt_entity (sched_rt_period_timer)
    706 |          2 |      bme_RX-51 | sys_timer_settime (posix_timer_fn)
    706 |          2 |      bme_RX-51 | do_nanosleep (hrtimer_wakeup)
    706 |          2 |      bme_RX-51 | schedule_timeout (process_timeout)
    695 |          2D|<kernel module> | queue_delayed_work (delayed_work_timer_fn)
      1 |          2D|  <kernel core> | queue_delayed_work (delayed_work_timer_fn)
    844 |          1 |          Xorg | hrtimer_start (it_real_fn)
  1323 |          1 |mafw-dbus-wrapp | queue_delayed_work (delayed_work_timer_fn)
  1502 |          1 |      browserd | futex_wait (hrtimer_wakeup)
  1441 |          1 |tracker-indexer | schedule_hrtimeout_range (hrtimer_wakeup)
  1441 |          1 |tracker-indexer | journal_get_write_access (commit_timeout)
  1533 |          1 |        pdflush | journal_get_write_access (commit_timeout)
  1554 |          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:  12%|INA:  0%| ON:  1%| 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:  79%|RET:  5%|INA:  0%| ON:  15%| now:(ON)
  neon |OFF:  81%|RET:  10%|INA:  7%| ON:  1%| now:(ON)
    mpu |OFF:  81%|RET:  10%|INA:  7%| ON:  1%| 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  1235,  41.2/s | IRQ 1076,  35.9/s | Timers  159,  5.3/s
HW wakeups      66,  2.2/s |    Real gp_timers expired  98,  3.3/s


cheers.


udaychaitanya16 2011-03-05 17:23

Re: High Battery Consumption
 
@zimon
i googled for how to code-tag just like you said but got nothing.i copied from terminal and i pasted it to notes in my device and from there posted here.please give an idea.
regards

devi01 2011-03-05 18:00

Re: High Battery Consumption
 
Try the new battery workwd fine ,see the links my thread:
http://www.mugen-power-batteries.com.../view/id/1357/

zimon 2011-03-05 18:08

Re: High Battery Consumption
 
If you click "quote&Reply" on my previous post, you will see how CODE-tags are used. Also if you use [Go Advanced] there is "#"-button which will bring the CODE-start and -end tags.

In your powertop output it shows your CPU is active ("98.4%") almost whole 30s time. So something is running. You could try to see with top or with htop what process is running in the background.

udaychaitanya16 2011-03-06 18:13

Re: High Battery Consumption
 
@Thank for your kind answer.As of now i have flashed it.using very limited apps like
1.queen beecon
2.f-aircrack
3.pen pen ,conboy
4.vnc viewer
5.auto dis connect,simple brightness app.
Now i have put into re use -smartreflex
since 7.45 pm to 11.45 pm phone lost 4 percent of charging till now.at present happy with that.will see what happens.

bman 2011-03-10 09:51

Re: High Battery Consumption
 
install battery graph and install 5 or so apps every 2 days or so
in your idle time (sleeping) battery graph shouldnt display many (if any) purple bars if its all good install next lot of apps

Juhgu 2011-03-14 23:35

Re: High Battery Consumption
 
Uninstalled catorize - had no idea it could cause battery issues until I read the forums - and battery life significantly improved.

Here's a battery graph from yesterday, just for reference. With no use and internet connection off your phone shouldn't use more than 10-15% of battery per 24 hours. (I guess?) I bought my phone when N900 came out, 15 months ago or so, and it's been in heavy use ever since. I'm quite happy with how well the battery still performs.

(The little notch there is from actual phone use.)

http://koshiyoka.biz/juhgu/temp/n900battery.png

StocChr 2011-09-29 14:52

Re: High Battery Consumption
 
hi guys,

my battery lasts less and less in the last time
can someone check my powertop output?
( Offline Modus after an Restart )

btw. what the hell is the fmtx process while in offline modus?

cheers

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

C#      | Ratio  | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
    C0 |  0.6% |          |  1150 MHz |  nan% |
    C1 |  0.0% |    0.4ms |
    C2 |  2.1% |    9.7ms |
    C3 |  9.4% |  113.1ms |
    C4 |  87.9% |  943.8ms |

IRQ#    | Activity  | Type          | Name
--------+------------+----------------+---------------------------
    56 |        113 |          INTC | i2c_omap
    37 |        91 |          INTC | gp
    11 |        87 |          INTC | prcm
    86 |        31 |          INTC | mmc1
    57 |        29 |          INTC | i2c_omap
    21 |          9 |          INTC | SGX
    12 |          4 |          INTC | DMA

PID#    | Activity  | Name          | Function Entry (Expire)
--------+------------+----------------+---------------------------
  1951 |        30 |          fmtxd | schedule_hrtimeout_range (hrtimer_wakeup)
  1822 |        17 |    osso-xterm | schedule_hrtimeout_range (hrtimer_wakeup)
      0 |        13 |  <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
      0 |        13 |  <kernel core> | hrtimer_start (tick_sched_timer)
      1 |        12D|        preinit | cpufreq_governor_dbs (delayed_work_timer_fn)
  1042 |          7 |      bme_RX-51 | sys_timer_settime (posix_timer_fn)
    45 |          6 |          mmcqd | schedule_timeout (process_timeout)
    45 |          3 |          mmcqd | queue_delayed_work (delayed_work_timer_fn)
  1164 |          3 |          Xorg | queue_delayed_work (delayed_work_timer_fn)
  1042 |          3 |      bme_RX-51 | schedule_timeout (process_timeout)
    823 |          3 |          dsme | do_nanosleep (hrtimer_wakeup)
    823 |          3 |          dsme | __enqueue_rt_entity (sched_rt_period_timer)
  1135 |          2 |      sgx_perf | queue_delayed_work (delayed_work_timer_fn)
  1042 |          2 |      bme_RX-51 | sys_timer_settime (posix_timer_fn)
  1042 |          2 |      bme_RX-51 | do_nanosleep (hrtimer_wakeup)
    857 |          2D|<kernel module> | queue_delayed_work (delayed_work_timer_fn)
      0 |          1 |  <kernel core> | queue_delayed_work (delayed_work_timer_fn)
      1 |          1D|  <kernel core> | queue_delayed_work (delayed_work_timer_fn)
      1 |          1 |  <kernel core> | queue_delayed_work (delayed_work_timer_fn)
  1406 |          1 |          iphbd | schedule_hrtimeout_range (hrtimer_wakeup)
  1958 |          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:  96%|RET:  2%|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:  88%|RET:  7%|INA:  0%| ON:  3%| now:(ON)
  neon |OFF:  88%|RET:  9%|INA:  2%| ON:  0%| now:(ON)
    mpu |OFF:  88%|RET:  9%|INA:  2%| 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 |          SR1 |          SR2
        |
  ckgen |          CORE |          PERI |          96M
        |          48M |          12M |          54M
        |      EMU_CORE |
    per |        GPIO2 |        GPIO3 |        GPIO4
        |        GPIO5 |        GPIO6 |

Total wakeups  490,  16.3/s | IRQ  364,  12.1/s | Timers  126,  4.2/s
HW wakeups      87,  2.9/s |    Real gp_timers expired  91,  3.0/s


Anazif 2011-10-03 09:33

Re: High Battery Consumption
 
Quote:

Originally Posted by StocChr (Post 957110)
hi guys,

the battery consumption of my n900 drives me crazy.

charge over-night

10 hours of Standby ( with Bluetooth and 3G Internet ) and 1 hour talk time and the battery have to be loaded

this really sucks, any ideas?

cheers

I experienced similar problem with my N900, eventually I noticed that anytime I start the internal browser, the battery consumption peaks afterwards, even after closing the browser. So anytime I start the browser I had to restart the device to prevent the high power consumption. So what I did was to download a third party browser which I now use and I stopped using the original maemo browser entirely. Now my power usage has improved and I get longer battery time.

StocChr 2011-11-30 07:06

Re: High Battery Consumption
 
hi,
i have tested my device after a power-cycle (with battery removal).
the results are more than depressing. i can't say that kp49 is 100% responsible for this.
so if it's so, sorry for off topic, but maybe someone can help me to get a working device back.

i have charged my device till 19:00, the battery lasts till 04:00
9 hours in offline mode with obviously no cpu usage and no usage

what the hell is going on with me device?

http://www.id-t.at/data/kp49-2.png

i performed powertop befor testing, the output seems more than nice:
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 6226us

C#      | Ratio  | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
    C0 |  0.4% |          |  1150 MHz |  nan% |
    C1 |  0.1% |    0.4ms |
    C2 |  3.0% |    5.6ms |
    C3 |  6.3% |  72.1ms |
    C4 |  90.2% | 1690.7ms |

IRQ#    | Activity  | Type          | Name
--------+------------+----------------+---------------------------
    12 |        398 |          INTC | DMA
    56 |        152 |          INTC | i2c_omap
    37 |        90 |          INTC | gp
    57 |        50 |          INTC | i2c_omap
    86 |        17 |          INTC | mmc1
    202 |        17 |          GPIO | wl1251
    11 |        10 |          INTC | prcm
    21 |          9 |          INTC | SGX

PID#    | Activity  | Name          | Function Entry (Expire)
--------+------------+----------------+---------------------------
      0 |        30 |  <kernel core> | hrtimer_start (tick_sched_timer)
      0 |        27 |  <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
    744 |        22 |        wl12xx | schedule_timeout (process_timeout)
  2098 |        19 |    osso-xterm | schedule_hrtimeout_range (hrtimer_wakeup)
      1 |        15D|        preinit | cpufreq_governor_dbs (delayed_work_timer_fn)
    744 |        10 |        wl12xx | queue_delayed_work (delayed_work_timer_fn)
    869 |          9 |      bme_RX-51 | sys_timer_settime (posix_timer_fn)
    45 |          3 |          mmcqd | queue_delayed_work (delayed_work_timer_fn)
  1186 |          3 |          Xorg | queue_delayed_work (delayed_work_timer_fn)
    744 |          3 |        wl12xx | schedule_timeout (process_timeout)
  1511 |          3 |      wlancond | ieee80211_ioctl_siwpower (ieee80211_dynamic_ps_timer)
    869 |          3 |      bme_RX-51 | schedule_timeout (process_timeout)
    826 |          3 |          dsme | do_nanosleep (hrtimer_wakeup)
    826 |          3 |          dsme | __enqueue_rt_entity (sched_rt_period_timer)
      1 |          3D|  <kernel core> | queue_delayed_work (delayed_work_timer_fn)
  1139 |          2 |      sgx_perf | queue_delayed_work (delayed_work_timer_fn)
    869 |          2 |      bme_RX-51 | do_nanosleep (hrtimer_wakeup)
    853 |          2D|<kernel module> | queue_delayed_work (delayed_work_timer_fn)
    14 |          1 |        pdflush | journal_get_write_access (commit_timeout)
      1 |          1 |  <kernel core> | inet_initpeers (peer_check_expire)
  2113 |          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:  0%|RET:  0%|INA:  0%| ON: 100%| 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:  0%|RET:  0%|INA:  0%| ON: 100%| now:(ON)
  neon |OFF:  90%|RET:  6%|INA:  2%| ON:  0%| now:(ON)
    mpu |OFF:  90%|RET:  6%|INA:  2%| ON:  0%| now:(ON)
  iva2 |OFF:  0%|RET:  0%|INA:  0%| ON: 100%| now:(ON)

Clock activity breakdown at end of period
Domain  | Active clocks
--------+---------------+---------------+------------------
  iva2 |        IVA2
  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  908,  30.3/s | IRQ  743,  24.8/s | Timers  165,  5.5/s
HW wakeups      10,  0.3/s |    Real gp_timers expired  90,  3.0/s


HELLASISGREECE 2011-11-30 08:06

Re: High Battery Consumption
 
^ kp 49 was responsible in my case.

had no problems with 48

StocChr 2011-11-30 08:19

Re: High Battery Consumption in Standby
 
and what was your solution?

vi_ 2011-11-30 09:27

Re: High Battery Consumption in Standby
 
First off all make sure you have 'pastebinit' installed (apt-get install pastebinit)

1. Put device in offline mode.
2. Turn off device.
3. Remove battery.
4. Insert battery.
5. Power on.
6. Stay in offline mode.
7. Wait 4 minutes (for device to settle).
8. Run this code as root:

Code:

sleep 10; powertop > ./out; powertop >> ./out; powertop >> ./out
9. Immediately lock the screen and leave it for 5 minutes.
10. Connect to the internet and type in:

Code:

pastebinit ./out
11. Paste URL here.

vi_ 2011-11-30 09:29

Re: High Battery Consumption in Standby
 
THEN, remove kernel-power-settings and do the same again.

Post results.

freemangordon 2011-11-30 10:19

Re: High Battery Consumption in Standby
 
Quote:

Originally Posted by vi_ (Post 1130934)
THEN, remove kernel-power-settings and do the same again.

Post results.

Will you give me some hint on how KPS correlate with the fact that:

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


WTF?

StocChr 2011-11-30 10:31

Re: High Battery Consumption in Standby
 
2.6.28.10-power49 with kernel-power-settings
http://pastebin.com/tH0A89yJ

2.6.28.10-power49 without kernel-power-settings
http://pastebin.com/59M1Z1uf

2.6.28-omap1
http://pastebin.com/gpNkK62D

vi_ 2011-11-30 10:35

Re: High Battery Consumption in Standby
 
You can stop now, we have located the problem.

With KP settings:

Code:

C#      | Ratio  | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
    C0 |  0.2% |          |  1150 MHz |  nan% |
    C1 |  0.0% |    0.3ms |
    C2 |  3.3% |    9.4ms |
    C3 |  4.2% |  104.3ms |
    C4 |  92.3% | 1730.5ms |

Code:

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:  0%|RET:  0%|INA:  0%| ON: 100%| 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:  0%|RET:  0%|INA:  0%| ON: 100%| now:(ON)
  neon |OFF:  92%|RET:  4%|INA:  3%| ON:  0%| now:(ON)
    mpu |OFF:  92%|RET:  4%|INA:  3%| ON:  0%| now:(ON)
  iva2 |OFF:  0%|RET:  0%|INA:  0%| ON: 100%| now:(ON)

Code:

Total wakeups  520,  17.3/s | IRQ  404,  13.5/s | Timers  116,  3.9/s
HW wakeups        3,  0.1/s |    Real gp_timers expired  54,  1.8/s

Without KP settings:

Code:

C#      | Ratio  | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
    C0 |  0.2% |          |  1150 MHz |  nan% |
    C1 |  0.0% |    0.2ms |
    C2 |  0.2% |    2.4ms |
    C3 |  2.9% |  215.9ms |
    C4 |  96.7% | 2903.8ms |

Code:

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:  96%|RET:  3%|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:  90%|RET:  5%|INA:  0%| ON:  3%| now:(ON)
  neon |OFF:  91%|RET:  6%|INA:  1%| ON:  0%| now:(ON)
    mpu |OFF:  91%|RET:  6%|INA:  1%| ON:  0%| now:(ON)
  iva2 |OFF: 100%|RET:  0%|INA:  0%| ON:  0%| now:(OFF)

Code:

Total wakeups  276,  9.2/s | IRQ  225,  7.5/s | Timers  51,  1.7/s
HW wakeups      24,  0.8/s |    Real gp_timers expired  30,  1.0/s


You will notice while the results are not that significantly different, there is a shitload more DMA activity and IRQing going on when KP-settings is installed. While the CPU is not hammering some hardware on the n900 is. Notice the extra 100% ONs in the power domain table for with KP settings.

Also, 2900mS sleep? HOLY ****! ultimate power saving!

There is an ancient bug in KP settings. I had issues with KP settings since version 26. I never figured out why it caused all these wake ups I just know in some circumstances it does.

This is why I do not use KP settings. I have the script extracted from the deb so I can quickly load/unload settings but it does not do the whole startup thing, I do that from an Xsession script.

vi_ 2011-11-30 10:39

Re: High Battery Consumption in Standby
 
Quote:

Originally Posted by freemangordon (Post 1130961)
Will you give me some hint on how KPS correlate with the fact that:

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


WTF?

I have absolutely no idea why KP settings occasionally causes the n900 to spazz out like mongo-tard. I think it is something to do with the scripts it runs at startup.

Anyway the evidence is clear. Remove KP settings, problem goes away. Re-install KP settings and it may eventually sometime come back.

I mentioned it around 1 year ago, no one cared. I just stopped using KP settings and thought nothing more of it after that.

StocChr 2011-11-30 10:50

Re: High Battery Consumption in Standby
 
vi_ you are the man, big thanks !! you make me laugh with some of your explanations :)
"Also, 2900mS sleep? HOLY ****! ultimate power saving!" :D:D

i have some questions:
- do you use kernel power?
- what brings me kernel power without kernel settings for the device performance?
- is it possible to oc the device and do the smart reflex thing without settings?

btw. thanks man!

panjgoori 2011-11-30 10:55

Re: High Battery Consumption in Standby
 
yes kernel49 consumes battery more than power48. my phone dropped 7% battery in 8 hours. my phone was in stand by mode and also offline mode was activated. i haven't had any issue like this in kp48.

StocChr 2011-11-30 10:59

Re: High Battery Consumption in Standby
 
Quote:

Originally Posted by panjgoori (Post 1130975)
yes kernel49 consumes battery more than power48. my phone dropped 7% battery in 8 hours. my phone was in stand by mode and also offline mode was activated. i haven't had any issue like this in kp48.

my phone lost 100% in 9 hours, offline mode and standby !!

vi_ 2011-11-30 11:02

Re: High Battery Consumption in Standby
 
Quote:

Originally Posted by StocChr (Post 1130973)
vi_ you are the man, big thanks !! you make me laugh with some of your explanations :)
"Also, 2900mS sleep? HOLY ****! ultimate power saving!" :D:D

i have some questions:
- do you use kernel power?
- what brings me kernel power without kernel settings for the device performance?
- is it possible to oc the device and do the smart reflex thing without settings?

btw. thanks man!

- do you use kernel power?

Of course, the things pali and freeman have achieved recently make it essential for me.

- what brings me kernel power without kernel settings for the device performance?

If you copy the kernel power kernel-config script. For example copy kernel-config to a file called kernel in /usr/bin or something (be extremely careful or you will braek everything!) then un-install KP-settings you will still have kernel-config (now called kernel) available. The difference is it will not load at boot time.

PROCEED WITH CAUTION!

Only do the following if you KNOW your OC settings will not crash your device or you may endup with a boot-loop!

edit /etc/pmconfig. Here you can set your max/min clock speed and SR. As for setting allowed freqs and DSP freqs you need to stick a script in either event.d or Xsession that echos the appropriate values to the appropriate places. I used xsession, however you could just hi-jack an event.d script like the non gui swappolube event.

- is it possible to oc the device and do the smart reflex thing without settings?

See above.


However I must add none of this is compatible with anything else that muddles with your kernel settings (i.e. battery patch script and speed patch script).

vi_ 2011-11-30 11:10

Re: High Battery Consumption in Standby
 
Quote:

Originally Posted by panjgoori (Post 1130975)
yes kernel49 consumes battery more than power48. my phone dropped 7% battery in 8 hours. my phone was in stand by mode and also offline mode was activated. i haven't had any issue like this in kp48.

No it doesn't. KP49 is to the n900 as glass tables are to coprophagia.

HELLASISGREECE 2011-11-30 11:30

Re: High Battery Consumption in Standby
 
Quote:

Originally Posted by StocChr (Post 1130910)
and what was your solution?

removed kp49

must get kp48

StocChr 2011-11-30 11:45

Re: High Battery Consumption in Standby
 
i extracted "kernel-config" and "dsp" from the kernel-power-settings_0.13_armel.deb

i copied kernel-config and dsp to my device, ok!

and how must look my event.d file or the xsession file ( didn't do this before ) to load "kernel-config" and "dsp" on start up?

vi_ 2011-11-30 12:02

Re: High Battery Consumption in Standby
 
I AM IN NO WAY RESPONSIBLE FOR ANYTHING THAT OCCURS BY YOU FOLLOWING THESE INSTRUCTIONS! AT YOUR OWN RISK.

Well if you have extracted 'kernel-config' make a copy of it somwhere then uninstall KP-settings. Then copy kernel-config to /usr/bin.

Check kernel-config still works after uninstalling KP settings.
Check Your device can handle your 'dsp' profile ( no reboots etc).

If that works then as root enter this:

Code:

echo "#!/bin/sh" > /etc/X11/Xsession.post/80kernel-config
echo "sudo kernel-config load dsp" >> /etc/X11/Xsession.post/80kernel-config

Now reboot and cross your fingers. dsp profile should be loaded after boot.

StocChr 2011-11-30 12:15

Re: High Battery Consumption in Standby
 
ok, i do it on my own risk :)
kernel-config is normaly stored in /usr/sbin
should i save it to .../bin or .../sbin?

vi_ 2011-11-30 12:17

Re: High Battery Consumption in Standby
 
If it is normally in /usr/sbin you should copy the new version (after uninstallation) to /usr/sbin.

vi_ 2011-11-30 12:22

Re: High Battery Consumption in Standby
 
also make sure /etc/X11/Xsession.post/80kernel_config is executable...

StocChr 2011-11-30 12:45

Re: High Battery Consumption in Standby
 
i saved the kernel-config file to /usr/sbin
chmod +rwx /usr/sbin/kernel-config

i saved the the frequency schemes to /usr/share/kernel-power-settings

and then i executed:

Code:

echo "#!/bin/sh" > /etc/X11/Xsession.post/80kernel-config
chmod +rwx /etc/X11/Xsession.post/80kernel-config
echo "sudo kernel-config load dsp" >> etc/X11/Xsession.post/80kernel-config

loading kernel-config with dsp profile works flawless on startup
but the problem with the ON things are still there

see... http://pastebin.com/6bUbe13X

vi_ 2011-11-30 13:10

Re: High Battery Consumption in Standby
 
And KP settings is DEFINITELY uninstalled?

Um, wait, wtf?

Why when you are doing the procedure is fmtxd and mv running?

StocChr 2011-11-30 13:14

Re: High Battery Consumption in Standby
 
i didn't install KP settings since i uninstalled it today for the powertop things.

i downloaded the .deb file from meamo packages and extracted the kernel-config file and the frequency scheme!
it seems that kernel-config alone is responsible for the ON things

StocChr 2011-11-30 13:38

Re: High Battery Consumption in Standby
 
is it possible to overclock by editing the /etc/pmconfig and loading a frequency scheme from kernel-power?

or is it possible to edit the /etc/default/kernel-power file as i like

vi_ 2011-11-30 13:44

Re: High Battery Consumption in Standby
 
I have this in a script that is triggered by /etc/X11/Xsession.post/. Just modify your xsession.post/50kernel_config to launch this script.

Obviously alter the script to reflect your own needs.

Code:

#!/bin/sh
echo "550000 850000 950000 1000000 1100000 1150000" > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/avoid_frequencies
echo 150000 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate
#echo "90 90 180 360 400 430 430 430 430 500 500 500 500 520 520" > /sys/power/dsp_opps_rate
echo "1" > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/ignore_nice_load
echo "87" > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold

#Camera button through lock screen
echo 0 > /sys/devices/platform/gpio-switch/cam_focus/disable
chmod 444 /sys/devices/platform/gpio-switch/cam_focus/disable

No you cannot just add random sh|te to /etc/pmconfig.

StocChr 2011-11-30 14:15

Re: High Battery Consumption in Standby
 
hey vi_ i build my own Xsession Script, maybe you can proofreading it for me before i will test it on my device?!

i tried to put all things from the kernel-settings dsp profile in the xsession script:

Code:

echo "250000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

echo "805000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

echo "125000" > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/avoid_frequencies

echo "0 125000 250000 500000 550000 600000 720000 805000 850000 900000 950000 1000000 1100000 1150000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies

echo "30 30 38 48 54 60 60 60 60 60 60 60 72 72" > /sys/power/vdd1_opps_vsel

echo "90 90 180 360 400 430 520 600 600 600 600 600 600 600" > /sys/power/dsp_opps_rate

echo "1" > /sys/power/sr_vdd1_autocomp

echo "1" > /sys/power/sr_vdd2_autocomp

echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

echo "95" > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold

echo "300000" > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate

echo "0" > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/ignore_nice_load

echo "0" > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/powersave_bias

analog you can look at the dsp code:

Code:

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


vi_ 2011-11-30 14:27

Re: High Battery Consumption in Standby
 
Quote:

Originally Posted by StocChr (Post 1131087)
hey vi_ i build my own Xsession Script, maybe you can proofreading it for me before i will test it on my device?!

i tried to put all things from the kernel-settings dsp profile in the xsession script:

Code:

echo "125000" > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/avoid_frequencies

echo "30 30 38 48 54 60 60 60 60 60 60 60 72 72" > /sys/power/vdd1_opps_vsel

echo "90 90 180 360 400 430 520 600 600 600 600 600 600 600" > /sys/power/dsp_opps_rate

echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

echo "95" > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold

echo "300000" > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate

echo "0" > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/ignore_nice_load

echo "0" > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/powersave_bias


Set max+min scalling speeds in /etc/pmconfig.
Set smartreflex in /etc/pmconfig.

Other wise it is fine.

You can set almost everything from pmconfig. You no longer need to set voltage values as SR will do it for you.

Just make sure the script runs with no errors before you set it to start automatically from xsession.post.

Also, just use xsession to start your script. Stick you script elsewhere.


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

vBulletin® Version 3.8.8