Active Topics
-
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 5 hrs, 20 mins ago -
TLS 1.2 for N9 is ready (28)
to MeeGo / Harmattan by smartblu9 - 6 hrs, 35 mins ago -
Maemo repository (3)
to Community by torsen - 22 hrs, 4 mins ago -
Error after installing Leste on sdcard (11)
to Maemo 7 / Leste by Maemish - 1 day, 19 hrs ago -
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 3 days, 2 hrs ago - more...
| The Following User Says Thank You to uros For This Useful Post: | ||
 |
|
2012-01-26
, 21:47
|
|
Posts: 254 |
Thanked: 146 times |
Joined on Dec 2010
@ Antwerp Belgium
|
#2
|
Originally Posted by uros
Hey uros
Durring idle time, my device rapidly eat battery. Using CSSU fully updated, no battery patch.
How to find and kill that process, Top command looks OK.
Maybe you can install powertop to see what's eating your battery.
If you search here for powertop you'll see a lot of threads about battery life and also a lot of results if you post the output.
I also have the latest CSSU, KP49 and both speed and batterypatch installed and on top of that OptimizeN900.
I know there's a controversy here on TMO about these patches,
but here's my output with the original battery from december 2009
Code:
BusyBox v1.19.3 (Debian 1.19.3power4) built-in shell (ash)
Enter 'help' for a list of built-in commands.
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 36371us
C# | Ratio | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
C0 | 0.4% | | 1150 MHz | nan% |
C1 | 0.1% | 2.7ms |
C2 | 0.4% | 3.0ms |
C3 | 2.4% | 354.4ms |
C4 | 96.8% | 4151.3ms |
IRQ# | Activity | Type | Name
--------+------------+----------------+---------------------------
56 | 90 | INTC | i2c_omap
57 | 79 | INTC | i2c_omap
11 | 38 | INTC | prcm
37 | 31 | INTC | gp
12 | 4 | INTC | DMA
21 | 2 | INTC | SGX
PID# | Activity | Name | Function Entry (Expire)
--------+------------+----------------+---------------------------
0 | 17 | <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
1243 | 5D| kernel-config | cpufreq_governor_dbs (delayed_work_timer_fn)
737 | 4 | bme_RX-51 | sys_timer_settime (posix_timer_fn)
1 | 3 | <kernel core> | queue_delayed_work (delayed_work_timer_fn)
696 | 3 | dsme | __enqueue_rt_entity (sched_rt_period_timer)
1209 | 2 | osso-xterm | schedule_hrtimeout_range (hrtimer_wakeup)
737 | 2 | bme_RX-51 | sys_timer_settime (posix_timer_fn)
737 | 2 | bme_RX-51 | do_nanosleep (hrtimer_wakeup)
737 | 2 | bme_RX-51 | schedule_timeout (process_timeout)
726 | 2D|<kernel module> | queue_delayed_work (delayed_work_timer_fn)
696 | 2 | dsme | do_nanosleep (hrtimer_wakeup)
0 | 1 | <kernel core> | hrtimer_start (tick_sched_timer)
593 | 1 | mmcqd | queue_delayed_work (delayed_work_timer_fn)
955 | 1 | hald | schedule_hrtimeout_range (hrtimer_wakeup)
1225 | 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: 99%|RET: 0%|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: 96%|RET: 2%|INA: 0%| ON: 0%| now:(ON)
neon |OFF: 96%|RET: 2%|INA: 0%| ON: 0%| now:(ON)
mpu |OFF: 96%|RET: 2%|INA: 0%| 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 292, 9.7/s | IRQ 244, 8.1/s | Timers 48, 1.6/s
HW wakeups 38, 1.3/s | Real gp_timers expired 31, 1.0/s
Nokia-N900:~#
__________________
.................................................. ...........
..........................
................................N900 is a way of life....................
surfing the web, navigate, chat, ttweet, email, scan, hack, share, tweak...
.....................and you can also use him to make a call
.................................................. ...........
..........................
................................N900 is a way of life....................
surfing the web, navigate, chat, ttweet, email, scan, hack, share, tweak...
.....................and you can also use him to make a call
|
|
2012-01-29
, 18:31
|
|
Posts: 85 |
Thanked: 36 times |
Joined on Jun 2010
@ Berlin/Germany
|
#4
|
Hi,
my battery drains about 20% in 3 hours, while phone is locked, no wifi, no 3g data, no gps active, cpu usage is low (batterygraph).
I run powertop and saw some differences between my and your output!
First the C1-C4 lines are looking very different, also in "Power domain activity breakdown" part, the dss and core lines show "ON: 100%"!
Could this be the cause for my abnormal battery drain?
I have current cssu, kp49 (also tried pre v50, no difference), no speedpatch, no batterypatch. Tried dsp profile and default profile.
Maybe my battery is just broken? My n900 is nearly two years old, so maybe its time to change the battery?
Here is the complete output of powertop, maybe someone can help me:
my battery drains about 20% in 3 hours, while phone is locked, no wifi, no 3g data, no gps active, cpu usage is low (batterygraph).
I run powertop and saw some differences between my and your output!
First the C1-C4 lines are looking very different, also in "Power domain activity breakdown" part, the dss and core lines show "ON: 100%"!
Could this be the cause for my abnormal battery drain?
I have current cssu, kp49 (also tried pre v50, no difference), no speedpatch, no batterypatch. Tried dsp profile and default profile.
Maybe my battery is just broken? My n900 is nearly two years old, so maybe its time to change the battery?
Here is the complete output of powertop, maybe someone can help me:
Code:
Powertop 1.13.3
status: Unknown job: pmtrackerdaemon
Sleeping for 11 seconds before sampling
Collecting data for 30 seconds
Sample interval was 00m 30s 16754us
C# | Ratio | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
C0 | 2.2% | | 1150 MHz | nan% |
C1 | 1.5% | 73.8ms |
C2 | 19.5% | 30.5ms |
C3 | 34.3% | 205.9ms |
C4 | 42.5% | 1159.3ms |
IRQ# | Activity | Type | Name
--------+------------+----------------+---------------------------
56 | 2219 | INTC | i2c_omap
37 | 158 | INTC | gp
11 | 104 | INTC | prcm
83 | 39 | INTC | mmc0
57 | 38 | INTC | i2c_omap
86 | 24 | INTC | mmc1
12 | 11 | INTC | DMA
21 | 10 | INTC | SGX
67 | 6 | INTC | ssi_p1_mpu_irq0
225 | 6 | GPIO | omap2-onenand
71 | 4 | INTC | ssi_gdd
311 | 2 | GPIO | ssi_p1_cawake_gpio
PID# | Activity | Name | Function Entry (Expire)
--------+------------+----------------+---------------------------
0 | 56 | <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
38 | 34D| awk | cpufreq_governor_dbs (delayed_work_timer_fn)
0 | 28 | <kernel core> | hrtimer_start (tick_sched_timer)
839 | 23 | bme_RX-51 | sys_timer_settime (posix_timer_fn)
8758 | 18 | osso-xterm | schedule_hrtimeout_range (hrtimer_wakeup)
839 | 18 | bme_RX-51 | schedule_timeout (process_timeout)
1252 | 16 | hildon-home | schedule_hrtimeout_range (hrtimer_wakeup)
597 | 8 | mmcqd | schedule_timeout (process_timeout)
839 | 6 | bme_RX-51 | sys_timer_settime (posix_timer_fn)
625 | 6 | mmcqd | schedule_timeout (process_timeout)
968 | 3 | Xorg | hrtimer_start (it_real_fn)
968 | 3 | Xorg | queue_delayed_work (delayed_work_timer_fn)
1 | 3 | <kernel core> | queue_delayed_work (delayed_work_timer_fn)
597 | 3 | mmcqd | queue_delayed_work (delayed_work_timer_fn)
625 | 3 | mmcqd | queue_delayed_work (delayed_work_timer_fn)
728 | 3 | dsme | __enqueue_rt_entity (sched_rt_period_timer)
928 | 2 | sgx_perf | queue_delayed_work (delayed_work_timer_fn)
839 | 2 | bme_RX-51 | do_nanosleep (hrtimer_wakeup)
754 | 2D|<kernel module> | queue_delayed_work (delayed_work_timer_fn)
728 | 2 | dsme | do_nanosleep (hrtimer_wakeup)
597 | 2 | mmcqd | schedule_timeout (process_timeout)
2585 | 2 | browserd | futex_wait (hrtimer_wakeup)
508 | 1 | kmmcd | schedule_timeout (process_timeout)
15 | 1 | kswapd0 | schedule_timeout (process_timeout)
1321 | 1 | qtlockscreen | schedule_hrtimeout_range (hrtimer_wakeup)
903 | 1 | mce | schedule_hrtimeout_range (hrtimer_wakeup)
597 | 1 | mmcqd | cfq_completed_request (cfq_idle_slice_timer)
597 | 1 | mmcqd | laptop_io_completion (laptop_timer_fn)
625 | 1 | mmcqd | schedule_timeout (process_timeout)
12821 | 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: 76%|RET: 20%|INA: 0%| ON: 3%| 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: 0%| ON: 100%| now:(ON)
neon |OFF: 42%|RET: 34%|INA: 19%| ON: 3%| now:(ON)
mpu |OFF: 42%|RET: 34%|INA: 19%| ON: 3%| 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 |
dss | DSS_STBY | DSS_IDLE
per | GPIO2 | GPIO3 | GPIO4
| GPIO5 | GPIO6 |
Total wakeups 2872, 95.7/s | IRQ 2621, 87.4/s | Timers 251, 8.4/s
HW wakeups 104, 3.5/s | Real gp_timers expired 158, 5.3/s
|
|
2012-01-29
, 19:21
|
|
Posts: 5,795 |
Thanked: 3,151 times |
Joined on Feb 2007
@ Agoura Hills Calif
|
#5
|
Batteries definitely age. Find the battery thread and buy Scud batteries.
__________________
All I want is 40 acres, a mule, and Xterm.
All I want is 40 acres, a mule, and Xterm.
| The Following User Says Thank You to geneven For This Useful Post: | ||
|
|
2012-01-29
, 19:38
|
|
Posts: 254 |
Thanked: 146 times |
Joined on Dec 2010
@ Antwerp Belgium
|
#6
|
Originally Posted by bitrocky
It could be your battery but my battery is now 2 years and one month and still very alive...
Hi,
my battery drains about 20% in 3 hours, while phone is locked, no wifi, no 3g data, no gps active, cpu usage is low (batterygraph).
I run powertop and saw some differences between my and your output!
First the C1-C4 lines are looking very different, also in "Power domain activity breakdown" part, the dss and core lines show "ON: 100%"!
Could this be the cause for my abnormal battery drain?
I have current cssu, kp49 (also tried pre v50, no difference), no speedpatch, no batterypatch. Tried dsp profile and default profile.
Maybe my battery is just broken? My n900 is nearly two years old, so maybe its time to change the battery?
As for core and dss on 100%, probably that'll be the reason for draining your battery so fast.
There are a few threads about powertop and on the Wiki page you'll find some more information.
I'll hope some experts read your post to comment on how to solve this.
Something to read, here, here and if you search on powertop, you'll see a lot of threads about battery life.
__________________
.................................................. ...........
..........................
................................N900 is a way of life....................
surfing the web, navigate, chat, ttweet, email, scan, hack, share, tweak...
.....................and you can also use him to make a call
.................................................. ...........
..........................
................................N900 is a way of life....................
surfing the web, navigate, chat, ttweet, email, scan, hack, share, tweak...
.....................and you can also use him to make a call
Last edited by peter2p; 2012-01-29 at 19:51.
| The Following User Says Thank You to peter2p For This Useful Post: | ||
|
|
2012-01-29
, 20:19
|
|
Posts: 1,523 |
Thanked: 1,997 times |
Joined on Jul 2011
@ not your mom's FOSS basement
|
#7
|
Check your dictionaries guys. If they are corrupted, hildon-input-plugin or the like will keep eating battery like hell.
|
|
2012-01-30
, 13:54
|
|
Posts: 85 |
Thanked: 36 times |
Joined on Jun 2010
@ Berlin/Germany
|
#8
|
Originally Posted by don_falcone
How can I do this?
Check your dictionaries guys. If they are corrupted, hildon-input-plugin or the like will keep eating battery like hell.
|
|
2012-01-30
, 13:56
|
|
Posts: 3,074 |
Thanked: 12,964 times |
Joined on Mar 2010
@ Sofia,Bulgaria
|
#9
|
Try to ininstall kernel-power-settings to see if there is any difference.
|
|
2012-01-30
, 14:18
|
|
Posts: 85 |
Thanked: 36 times |
Joined on Jun 2010
@ Berlin/Germany
|
#10
|
I uninstalled kps (copied kernel-config before) and rebooted
it seems to help, I have less wakeups.
but dss and core is still on!?
but now w/o kps, I get a okay-requester with "Package kernel-power-settings not found" on startup and everytime I unlock my phone!?
Do you know where it come from?
it seems to help, I have less wakeups.
but dss and core is still on!?
but now w/o kps, I get a okay-requester with "Package kernel-power-settings not found" on startup and everytime I unlock my phone!?
Do you know where it come from?
How to find and kill that process, Top command looks OK.