N900 battery drain - maemo.org

Active Topics

The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 1 day, 1 hr ago
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 1 day, 20 hrs ago
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 4 days, 5 hrs ago
more...

Page 1 of 6

Next >

Last »

Thread Tools

codelad	2014-07-12 , 08:26
Posts: 25 \| Thanked: 19 times \| Joined on Apr 2014	#1

I have a serious battery drain issue with my N900. The charge runs out in 4~5 hours, from fully charged. Facing this issue ever since I had left my N900 lie unused (and with the battery in it) for 6~8 weeks. I have tried the following possible solutions gathered from older posts here, and none work:

- flashed the stock firmware, CSSU (stable, devel and thumb).

- with and without the kernel-power mod.

- in offline mode and with brightness turned down low.

- cleaned the sim and battery contacts, and with the SD card removed.

- with a third-party battery.

The batteries charge fine (both the Nokia and the third-party one). And the phone appears to work fine, except for the bluetooth which doesn't work (and which I happened to notice along with the battery issue).

As a last resort, I'm about to dissassemble the phone and attempt to clean and tighten the contacts. Is there anything else I'd be advised to try, before I take it apart? I'd dearly hate to lose my N900 (even if I suspect a severe hardware issue).

Thank you.

Quote & Reply |

gianko	2014-07-12 , 09:13
Posts: 445 \| Thanked: 367 times \| Joined on Nov 2010 @ Italy	#2

have you tried to use conky or top in xterm to monitor if there's some process using lot of cpu?
or else is probable an hardware issue

__________________
Flickr photos taken with N900 https://www.flickr.com/cameras/nokia/n900/
"Closed source software tells you what you can do. With open source, you decide what software can do for you" Richard Stallman

Quote & Reply |

myname24	2014-07-12 , 09:35
Posts: 545 \| Thanked: 560 times \| Joined on Dec 2011 @ lebanon	#3

your battery is more likely dead . A new one should resolve your problem

Quote & Reply |

	Estel	2014-07-12 , 10:21
	Posts: 5,028 \| Thanked: 8,613 times \| Joined on Mar 2011	#4

Without more detailed informations (powertop output) we won't be able to help. Install powertop, disable all radios etc, then run "powertop" from terminal, and immediately lock device and lay it flat. After 42 seconds (or more

just not less) unlock screen, and copy whole output, then paste it in this thread.

/Estel

__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!

Quote & Reply |

The Following User Says Thank You to Estel For This Useful Post:
codelad

codelad	2014-07-12 , 11:26
Posts: 25 \| Thanked: 19 times \| Joined on Apr 2014	#5

@gianko: I did monitor the top output for anomalies, and nothing came up odd (browserd was active for most of the time, but not consuming too much cpu or mem).

@myname24: Tried two different batteries since, and both drain equally quick. FYI, they are both third-party batteries, and one of them very cheap.

@Estel: Afraid I couldn't locate the package for powertop, but found something called zzztop that claimed to be something similar. It came with a parameter to set running time (which I set to 45s). Here are the results:

Code:

/home/user # zzztop -t=45 > zzz.txt
WARNING: Only low accuracy timing available.

/home/user # cat zzz.txt
Detected 1 cpus
Detected 4 cpuidle states (3)
Sleeping for 10 seconds before collecting data for 45 seconds
Actually slept for 45.010s
C-state Information
===================
    |      CPU#0      |
 C# |  time  | avg/ms |
----+--------+--------+
 C0 |   0.9% |        |
 C1 |   0.0% |      0 |
 C2 |   3.3% |     25 |
 C3 |  24.8% |    856 |
 C4 |  71.0% |   2130 |

CPUfreq statistics
==================
Frequency |  CPU#0 |
----------+--------+
  250 MHz |  91.5% |
  600 MHz |   8.5% |

Interrupt statistics
====================
 INT | CPU#0 |
-----+-------+
  56 |   351 | INTC  i2c_omap
  37 |    99 | INTC  gp timer
  57 |    60 | INTC  i2c_omap
  11 |    48 | INTC  prcm
  86 |    12 | INTC  mmc1
  12 |     3 | INTC  DMA
Summary: 12.7 interrupts/s total

Timer statistics
================
   PID | Activity |     task's comm | function
-------+----------+-----------------+---------
     0 |       70 |         swapper | tick_nohz_restart_sched_tick (tick_sched_timer)
    38 |       18D|             awk | cpufreq_governor_dbs (delayed_work_timer_fn)
   782 |        5 |       bme_RX-51 | schedule_timeout (process_timeout)
   782 |        4 |       bme_RX-51 | sys_timer_settime (posix_timer_fn)
   747 |        4 |            dsme | do_nanosleep (hrtimer_wakeup)
   747 |        4 |            dsme | __enqueue_rt_entity (sched_rt_period_timer)
     0 |        4 |         swapper | hrtimer_start (tick_sched_timer)
   782 |        3 |       bme_RX-51 | sys_timer_settime (posix_timer_fn)
   782 |        3 |       bme_RX-51 | sys_timer_settime (posix_timer_fn)
   782 |        3 |       bme_RX-51 | sys_timer_settime (posix_timer_fn)
   782 |        3 |       bme_RX-51 | do_nanosleep (hrtimer_wakeup)
   616 |        3 |           mmcqd | queue_delayed_work (delayed_work_timer_fn)
   836 |        2 |            hald | schedule_hrtimeout_range (hrtimer_wakeup)
   773 |        2D|        modprobe | queue_delayed_work (delayed_work_timer_fn)
     1 |        2D|         swapper | queue_delayed_work (delayed_work_timer_fn)
  1872 |        1 |          zzztop | do_nanosleep (hrtimer_wakeup)
  1659 |        1 |        browserd | futex_wait (hrtimer_wakeup)
  1204 |        1 | hildon-status-m | schedule_hrtimeout_range (hrtimer_wakeup)
  1139 |        1 |           iphbd | schedule_hrtimeout_range (hrtimer_wakeup)
  1069 |        1 |     dbus-daemon | schedule_hrtimeout_range (hrtimer_wakeup)
   982 |        1 |  hald-addon-bme | schedule_hrtimeout_range (hrtimer_wakeup)
   858 |        1 |             mce | schedule_hrtimeout_range (hrtimer_wakeup)
   782 |        1 |       bme_RX-51 | sys_timer_settime (posix_timer_fn)
    30 |        1 |           mount | setup_wb_timer (wb_timer_fn)
     1 |        1 |         swapper | inet_initpeers (peer_check_expire)

Context switches per task
=========================
  PID  | vol'try | non-vol | Cmdline
-------+---------+---------+--------
  1872 |       1 |       2 | /usr/bin/perl -w /usr/bin/zzztop -t=45 
  1656 |       1 |       0 | /usr/sbin/browserd -s 1656 -n browserui 
  1652 |       1 |       0 | /usr/bin/image-viewer                                                      
  1649 |       1 |       0 | /usr/bin/browser                                                           
  1645 |       1 |       1 | /usr/sbin/browserd -s 1645 -n RTComMessagingServer 
  1644 |       1 |       0 | /usr/bin/rtcom-messaging-ui                                                
  1639 |       1 |       0 | /usr/bin/rtcom-call-ui                                                     
  1630 |       1 |       0 | /usr/bin/osso-addressbook                                                  
  1297 |       1 |       0 | /usr/sbin/wlancond 
  1291 |       1 |       0 | /usr/bin/hildon-input-method 
  1270 |       3 |       0 | /usr/lib/tracker/trackerd 
  1204 |      38 |       5 | /usr/bin/hildon-status-menu                                                
  1161 |       1 |       0 | /usr/bin/mission-control 
  1139 |       1 |       0 | /usr/bin/iphbd 
  1107 |       1 |       0 | /usr/bin/systemui 
  1069 |       1 |       0 | /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session 
  1044 |       2 |       0 | /usr/sbin/bluetoothd -n 
   982 |      12 |       0 | /usr/lib/hal/hald-addon-bme 
   858 |       4 |       4 | /sbin/mce --force-syslog 
   844 |       1 |       0 | /usr/sbin/csd -m -p call -p gprs -p info -p net -p sim -p simpb -p sms -p ss 
   838 |       5 |       0 | /usr/sbin/ohmd --no-daemon 
   836 |      95 |      14 | /usr/sbin/hald --verbose=no --daemon=no --use-syslog 
   796 |      23 |      56 | /usr/bin/dbus-daemon --system --nofork 
   782 |     131 |       7 | /usr/sbin/bme_RX-51 
   759 |      15 |       0 | /sbin/dsme-server -p /usr/lib/dsme/libstartup.so 
   747 |       8 |       0 | /sbin/dsme -p /usr/lib/dsme/libstartup.so 
   616 |       3 |       0 | <mmcqd>
   512 |      15 |       0 | <kmmcd>
    27 |      18 |       0 | <kondemand/0>
    14 |       1 |       0 | <pdflush>
     6 |       1 |       0 | <kblockd/0>
     4 |       2 |       0 | <events/0>
     3 |       4 |       0 | <ksoftirqd/0>

Just as I turned everything off, I noticed that the GPS was on. Something I've never bothered to notice, before. I doubt it, but could GPS have been the cause?

Thank you!

Quote & Reply |

The Following 2 Users Say Thank You to codelad For This Useful Post:
Estel, peterleinchen

	pichlo	2014-07-12 , 11:41
	Posts: 6,447 \| Thanked: 20,981 times \| Joined on Sep 2012 @ UK	#6

Originally Posted by codelad

could GPS have been the cause?

Oh yes, absolutely! Besides, it is easy to check. Just turn it off and see.

Quote & Reply |

The Following 2 Users Say Thank You to pichlo For This Useful Post:
codelad, Estel

codelad	2014-07-12 , 17:38
Posts: 25 \| Thanked: 19 times \| Joined on Apr 2014	#7

Afraid the battery drains just as quickly, with GPS off. Just did a quick test with GPS turned off, and the battery went from 30% to empty in 2 hours flat. I'll test again more thoroughly, with a fully charged battery.

Also, the problem persists when I tested with both the SIM and the SD card removed.

Quote & Reply |

	peterleinchen	2014-07-12 , 17:57
	Posts: 4,118 \| Thanked: 8,901 times \| Joined on Aug 2010 @ Ruhrgebiet, Germany	#8

Originally Posted by codelad

... except for the bluetooth which doesn't work (and which I happened to notice along with the battery issue).

... (even if I suspect a severe hardware issue).

Powertop does not reveal anything. It could/should (clean reflashed state) be a bit more time in C4 state, but mine is about the same.

So please do in terminal:
dmesg
and check for BT and/or FM (as BT and FM share a chip) errors. You may post here as txt attachment (better gz).
If that does not show anything please install sysklogd, reboot and check the file /var/log/syslog same way as above.

But I am afraid of an HW issue ...

__________________
SIM-Switcher, automated SIM switching with a Double (Dual) SIM adapter
--
Thank you all for voting me into the Community Council 2014-2016!

Please consider your membership / supporting Maemo e.V. and help to spread this by following/copying this link to your TMO signature:
[MC eV] Maemo Community eV membership application, http://talk.maemo.org/showthread.php?t=94257

editsignature, http://talk.maemo.org/profile.php?do=editsignature

Quote & Reply |

The Following User Says Thank You to peterleinchen For This Useful Post:
codelad

codelad	2014-07-12 , 18:39
Posts: 25 \| Thanked: 19 times \| Joined on Apr 2014	#9

Here's my dmesg output. At first glance, these lines bother me. They may be harmless, though:

Code:

...
[ 2290.354095] smc91x: not found (-19).
...
[ 2381.567657] Driver 'sd' needs updating - please use bus_type methods
...

Thank you.

Attached Files

dmesg.txt.gz (4.9 KB, 67 views)

Quote & Reply |

	peterleinchen	2014-07-12 , 18:54
	Posts: 4,118 \| Thanked: 8,901 times \| Joined on Aug 2010 @ Ruhrgebiet, Germany	#10

Nope, I do have those messages also, but way earlier:
[QUOE]~ $ dmesg | grep smc
[ 12.148284] smc91x: not found (-19).
~ $ dmesg | grep 'needs updating'
[ 101.257507] Driver 'sd' needs updating - please use bus_type methods[/QUOTE]...