maemo.org - Talk
Page 3 of 5 12 3 45
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Maemo 5 / Fremantle (https://talk.maemo.org/forumdisplay.php?f=40)
-   -   Battery Dies too Quickly (https://talk.maemo.org/showthread.php?t=71843)

xweirdow23 2011-04-06 13:54
Re: Battery Dies too Quickly
 
Quote:
C# | Ratio | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
C0 | 6.4% | | 900 MHz | 2.3% |
C1 | 0.9% | 2.0ms | 550 MHz | 0.0% |
C2 | 23.4% | 11.1ms | 500 MHz | 4.3% |
C3 | 69.3% | 141.5ms | 250 MHz | 0.0% |
C4 | 0.0% | | 125 MHz | 93.5% |

IRQ# | Activity | Type | Name
--------+------------+----------------+---------------------------
61 | 1434 | INTC | i2c_omap
37 | 864 | INTC | gp
11 | 617 | INTC | prcm
56 | 307 | INTC | i2c_omap
57 | 260 | INTC | i2c_omap
86 | 117 | INTC | mmc1
21 | 35 | INTC | SGX
12 | 33 | INTC | DMA
225 | 12 | GPIO | omap2-onenand
67 | 8 | INTC | ssi_p1_mpu_irq0
71 | 8 | INTC | ssi_gdd
311 | 4 | GPIO | ssi_p1_cawake_gpio
369 | 4 | twl4030 | twl4030_keypad
i want to check if this is right

Switch_ 2011-04-06 14:04
Re: Battery Dies too Quickly
 
Run it as
Code:
root
bro and then post up the output. I'm guessing you got a segmentation fault which is why it's not complete.

Non-root = segfault

Although not liking the distinct lack of C4 sleep. Want to see HW Wakeups.

xweirdow23 2011-04-06 14:10
Re: Battery Dies too Quickly
 
ops sorry here

Quote:
C# | Ratio | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
C0 | 8.0% | | 900 MHz | 21.5% |
C1 | 1.0% | 1.0ms | 550 MHz | 0.2% |
C2 | 43.6% | 10.8ms | 500 MHz | 2.9% |
C3 | 47.3% | 93.1ms | 250 MHz | 7.0% |
C4 | 0.0% | 9.2ms | 125 MHz | 68.4% |

IRQ# | Activity | Type | Name
--------+------------+----------------+---------------------------
61 | 1469 | INTC | i2c_omap
56 | 1429 | INTC | i2c_omap
37 | 1227 | INTC | gp
11 | 996 | INTC | prcm
12 | 795 | INTC | DMA
57 | 537 | INTC | i2c_omap
21 | 195 | INTC | SGX
86 | 107 | INTC | mmc1
369 | 67 | twl4030 | twl4030_keypad
202 | 57 | GPIO | wl1251
225 | 19 | GPIO | omap2-onenand
67 | 13 | INTC | ssi_p1_mpu_irq0
71 | 12 | INTC | ssi_gdd
311 | 6 | GPIO | ssi_p1_cawake_gpio

PID# | Activity | Name | Function Entry (Expire)
--------+------------+----------------+---------------------------
0 | 812 | <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
792 | 138 | mce | schedule_hrtimeout_range (hrtimer_wakeup)
2366 | 113 | osso-xterm | schedule_hrtimeout_range (hrtimer_wakeup)
37 | 99D| awk | cpufreq_governor_dbs (delayed_work_timer_fn)
0 | 70 | <kernel core> | hrtimer_start (tick_sched_timer)
453 | 41 | wl12xx | schedule_timeout (process_timeout)
9 | 39 | twl4030-irq | input_handle_event (input_repeat_key)
1488 | 36 | skyhost | futex_wait (hrtimer_wakeup)
453 | 34 | wl12xx | queue_delayed_work (delayed_work_timer_fn)
^[[A 840 | 22 | Xorg | schedule_hrtimeout_range (hrtimer_wakeup)
716 | 13 | bme_RX-51 | sys_timer_settime (posix_timer_fn)
1156 | 12 | wlancond | ieee80211_ioctl_siwpower (ieee80211_dynamic_ps_timer)
840 | 9 | Xorg | queue_delayed_work (delayed_work_timer_fn)
615 | 9 | mmcqd | queue_delayed_work (delayed_work_timer_fn)
1540 | 8 | browserd | futex_wait (hrtimer_wakeup)
615 | 8 | mmcqd | schedule_timeout (process_timeout)
812 | 7 | sgx_perf | queue_delayed_work (delayed_work_timer_fn)
1483 | 7 | skyhost | do_nanosleep (hrtimer_wakeup)
716 | 6 | bme_RX-51 | schedule_timeout (process_timeout)
615 | 4 | mmcqd | cfq_completed_request (cfq_idle_slice_timer)
615 | 3 | mmcqd | laptop_io_completion (laptop_timer_fn)
792 | 3 | mce | tsc2005_start_scan (tsc2005_esd_timer_handler)
1121 | 3 | hildon-desktop | queue_delayed_work (delayed_work_timer_fn)
695 | 3 | dsme | __enqueue_rt_entity (sched_rt_period_timer)
2366 | 3 | osso-xterm | do_nanosleep (hrtimer_wakeup)
1 | 2D| <kernel core> | queue_delayed_work (delayed_work_timer_fn)
10 | 2 | omap2_mcspi | neigh_add_timer (neigh_timer_handler)
716 | 2 | bme_RX-51 | do_nanosleep (hrtimer_wakeup)
695 | 2 | dsme | do_nanosleep (hrtimer_wakeup)
1537 | 2 | browserd | futex_wait (hrtimer_wakeup)
1488 | 1 | skyhost | sk_reset_timer (tcp_write_timer)
1534 | 1 | browserd | schedule_hrtimeout_range (hrtimer_wakeup)
2357 | 1 | browserd | futex_wait (hrtimer_wakeup)
1484 | 1 | skyhost | futex_wait (hrtimer_wakeup)
1475 | 1 | telepathy-haze | schedule_hrtimeout_range (hrtimer_wakeup)
1484 | 1 | skyhost | journal_get_write_access (commit_timeout)
897 | 1 | hald-addon-bme | schedule_hrtimeout_range (hrtimer_wakeup)
1475 | 1 | telepathy-haze | sk_reset_timer (tcp_write_timer)
2380 | 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: 85%|RET: 0%|INA: 0%| ON: 14%| now:(OFF)
per |OFF: 47%|RET: 43%|INA: 0%| ON: 9%| 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: 46%|INA: 24%| ON: 28%| now:(ON)
neon |OFF: 0%|RET: 47%|INA: 43%| ON: 9%| now:(ON)
mpu |OFF: 0%|RET: 47%|INA: 43%| ON: 9%| 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 |
dss | DSS_IDLE
per | GPIO2 | GPIO3 | GPIO4
| GPIO5 | GPIO6 |

Total wakeups 8450, 281.7/s | IRQ 6929, 231.0/s | Timers 1521, 50.7/s
HW wakeups 228, 7.6/s | Real gp_timers expired 203, 6.8/s
Nokia-N900:~# powertop > output.txt

vi_ 2011-04-06 14:17
Re: Battery Dies too Quickly
 
And you can confirm this output is from a 'fresh start' as detailed here?

Switch_ 2011-04-06 14:17
Re: Battery Dies too Quickly
 
ok HW wakeups s'ok. Too many IRQ's. Far too many IRQ's. Are you online and connected to WiFi?

Do me a favour;

1. Go to Offline Mode
2. Power down
3. Remove battery
4. Replace battery
5. Power up
6. Ensure you are in Offline Mode
7. Wait ~4 minutes - do nothing with the device during this time
8. Run powertop again - lock screen directly after keying in powertop <enter>
9. Do not touch the phone while it's running
10. Post output.

/EDIT couldn't be arsed to find the post vi_

stlpaul 2011-04-06 15:17
Re: Battery Dies too Quickly
 
Quote:
Originally Posted by maxppc (Post 982945)
Can I consider normal to drain battery after 5 hours considering I'm always online (Skype, Jabber, GTalk, SIP/Voip), always in HSDPA, surfing on the web from time to time, sending about ten sms, and some days listening to music for 2-3hrs?

I never thought it strange but this thread makes me think I should have more time from one charge to another.

What do you think? Should I worry?

i think that usage, 5 hours is normal. I get the same.

Using autodisconnect, GSM instead of 3G, disabling email checks, my phone can last a full workday. Of course it is far less useful since I'm not using it... but it lasts.

maxppc 2011-04-06 15:47
Re: Battery Dies too Quickly
 
I also have backlight at max for most of the time so I think it can't last longer.
But it's not useful if you don't listen to music, stick with 2g and keep low light, despite it would last whole day.

Anyway, since Switch_ kindly offered to check powertop, I'll post the output here as soon as I can.

maxppc 2011-04-06 17:02
Re: Battery Dies too Quickly
 
Here is my Powertop output after fresh start as explained before

Code:
Powertop 1.13.3
Sleeping for 11 seconds before sampling
Collecting data for 30 seconds
Sample interval was 00m 30s 32684us

C#      | Ratio  | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
    C0 |  0.7% |          |  600 MHz |  3.1% |
    C1 |  0.0% |    0.3ms |  550 MHz |  0.0% |
    C2 |  2.4% |    4.4ms |  500 MHz |  4.3% |
    C3 |  4.4% |  89.0ms |  250 MHz |  92.7% |
    C4 |  92.5% | 1389.0ms |

IRQ#    | Activity  | Type          | Name
--------+------------+----------------+---------------------------
    56 |        365 |          INTC | i2c_omap
    57 |        260 |          INTC | i2c_omap
    11 |        142 |          INTC | prcm
    86 |        89 |          INTC | mmc1
    37 |        56 |          INTC | gp
    12 |        19 |          INTC | DMA
    61 |          5 |          INTC | i2c_omap

PID#    | Activity  | Name          | Function Entry (Expire)
--------+------------+----------------+---------------------------
      0 |        23 |  <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
    37 |        16D|            awk | cpufreq_governor_dbs (delayed_work_timer_fn)
    704 |        10 |      bme_RX-51 | sys_timer_settime (posix_timer_fn)
      0 |          9 |  <kernel core> | hrtimer_start (tick_sched_timer)
    704 |          6 |      bme_RX-51 | sys_timer_settime (posix_timer_fn)
    704 |          6 |      bme_RX-51 | schedule_timeout (process_timeout)
    615 |          4 |          mmcqd | queue_delayed_work (delayed_work_timer_fn)
      1 |          3D|  <kernel core> | queue_delayed_work (delayed_work_timer_fn)
    771 |          2 |            mce | queue_delayed_work (delayed_work_timer_fn)
    704 |          2 |      bme_RX-51 | do_nanosleep (hrtimer_wakeup)
    675 |          2 |          dsme | do_nanosleep (hrtimer_wakeup)
    675 |          2 |          dsme | __enqueue_rt_entity (sched_rt_period_timer)
    818 |          1 |    pulseaudio | queue_delayed_work (delayed_work_timer_fn)
    748 |          1 |    pulseaudio | schedule_hrtimeout_range (hrtimer_wakeup)
    29 |          1 |          mount | setup_wb_timer (wb_timer_fn)
    14 |          1 |        pdflush | journal_get_write_access (commit_timeout)
    884 |          1 | hald-addon-bme | schedule_hrtimeout_range (hrtimer_wakeup)
  1098 |          1 |          iphbd | schedule_hrtimeout_range (hrtimer_wakeup)
  1602 |          1 |      powertop | do_nanosleep (hrtimer_wakeup)

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

Total wakeups  1028,  34.3/s | IRQ  936,  31.2/s | Timers  92,  3.1/s
HW wakeups      142,  4.7/s |    Real gp_timers expired  56,  1.9/s
Is here anything I should care about?

Thanks

fatcobrah 2011-04-06 17:18
Re: Battery Dies too Quickly
 
simply flash ur n900 and everything will be ok :D

woody14619 2011-04-06 17:27
Re: Battery Dies too Quickly
 
Quote:
Originally Posted by stlpaul (Post 982802)
Try to put the phone into offline mode and see if the battery draining continues. If it does, at least you know it is not a network drain.
There are lots of scripts that let you turn off one thing at a time too (like only wifi). So if going into offline mode works, you can try to turn them off one at a time to see which is causing it.

Quote:
Originally Posted by xweirdow23 (Post 983067)
Power domain activity breakdown
Domain | % of time spent in states
--------+---------+---------+---------+---------+----------
dss |OFF: 0%|RET: 0%|INA: 0%| ON: 100%| now (ON)
Woah! dss is on 100% of the time? That doesn't seem right at all.

And you have 125 listed as a frequency? Is this phone "new" or "new to you"? Have you attempted a reflash to get to PR1.3 base? It may be worth doing if you didn't do it when you got the device. It looks like there's a lot of residual stuff going on here.


All times are GMT. The time now is 05:00.
Page 3 of 5 12 3 45
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8