Battery Dies too Quickly
 

Basically, I'm just looking for some ideas on troubleshooting and fixing my crazy battery consumption. I tried searching through the forums but couldn't find any good hits on this topic. A lot of people have reported really awesome power consumption and I'd be happy if I could even get a whole 16 hours in.

I'm thinking about just flashing my phone to the vanilla install but I am worried about my warranty, in case it is a hardware/battery issue.

The Problem
For some reason I am unable to keep a charge for longer than (estimated) 6 hours. If I actually use the phone for a consistent amount of time, it's considerably less. If I let the phone charge over night while I sleep, it's dead in about 4-6 hours after unplugging it.

My Setup
The Phone is practically brand new (less than a month old). I bought it new from Amazon. I am using the AC Charger that came with it because USB charging would never reach a full battery (within a reasonable time, anyways)

I am only using a single desktop. I don't have any widgets open -- Just a few shortcuts on my desktop. I am using the plastic theme but it doesn't seem to make a difference which theme I use. I do not use 3G Data Transfer (Voice and Texts only). I do not have email or any other message polling on (as far as I can tell). Running 'top' reports that I am using very little CPU.

It is not over-clocked. I did install the Advanced Kernel stuff from the repository.

I tried to use the battery monitor program but the results didn't make a whole lot of sense to me. It ran in the background (which I didn't assume it would) so I didn't keep track of what I was running during which period of time.

Packages
advanced-power 0.4.2-4 user/desktop 188
advanced-power-monitor 0.5.3-3 user/utilities 216
amazon-installer 1.0.1.1+0m5 user/other 96
angrybirds 1.4.2 user/hidden 37300
ap-installer 1.0.1.1+0m5 user/other 88
appdownloader 0.2-12 user/system 700
autodisconnect 0.4.7 user/network 240
battery-eye 0.7.7-1 user/utilities 196
batterygraph 0.3.2 user/utilities 356
black-plastic-theme 2.400 user/system 29044
buddy 0.2-4 user/utilities 3044
docstogo 2.001.346 user/hidden 10512
dtg-installer 1.0-4.2+0m5 user/other 92
espeak 1.44.03 user/multimedia 48
facebook-installer 1.0-4.1.1+0m5 user/other 88
facebook-services 0.5.5 user/hidden 52
feedservice-plugin-fb 0.5.5 user/hidden 264
feedservice-plugin-fb-common 0.5.2 user/hidden 60
feedservice2 0.5.9 user/hidden 212
flashlight-applet 0.4-5 user/desktop 284
fm-boost 0.2-2fremantle1 user/system 120
fmradio 2010.03.20 user/multimedia 2172
foreca-installer 1.0.1.1+0m5 user/other 88
foreca-weather-applet 0.9.5 user/desktop 816
healthcheck 1.2.0-3 user/utilities 248
humanity-theme 0.5 user/desktop 32
kernel-power-flasher 2.6.28-maemo42 user/system 240
kernel-power-settings 0.11 user/system 140
libqtm-bearer 1:1.0.2-maemo4+0m5 user/libs 300
libqtm-contacts 1:1.0.2-maemo4+0m5 user/libs 1012
libqtm-location 1:1.0.2-maemo4+0m5 user/libs 256
libqtm-messaging 1:1.0.2-maemo4+0m5 user/libs 848
libqtm-multimedia 1:1.0.2-maemo4+0m5 user/libs 1544
libqtm-publishsubscribe 1:1.0.2-maemo4+0m5 user/libs 244
libqtm-sensors 1:1.0.2-maemo4+0m5 user/libs 336
libqtm-serviceframework 1:1.0.2-maemo4+0m5 user/libs 392
libqtm-systeminfo 1:1.0.2-maemo4+0m5 user/libs 420
libqtm-versit 1:1.0.2-maemo4+0m5 user/libs 468
liquid 0.6.4-ovi1-1 user/graphics 560
maemo-mapper 3.2 user/navigation 1480
maxcpu 0.1.6-2 user/system 72
mirror 2.1-1 user/multimedia 188
mp-fremantle-002-pr 20.2010.36-2.002 user/system
mypaint 0.8.2-2maemo0 user/graphics 10476
n900-fmrx-enabler 1.5-4+0m5 user/libs 92
offscr-airport 1.0.4 user/hidden 1300
ogg-support 1.0.5 user/multimedia 136
opendune 0.3-1maemo7 user/games 2684
openssh-server 1:5.1p1-6.maemo5 user/network 456
openttd 0.7.4-1maemo3 user/games 2464
opera-mobile 10.1beta1-6~fremantle0 user/network 15056
plastic-icon-pack 1.0-2 user/system 680
prboom 2:2.5.0-svn20091231-0maemo2 user/games 1296
pygtkeditor 3.0.19-1 user/development 608
qcpufreq 0.4.1-1 user/system 308
quake2 0.3-3 user/games 1176
rootsh 1.5 user/system 32
sharing-service-facebook 0.5.1 user/hidden 184
tar-gnu 1.22-2maemo5 user/system 2360
theme-customizer 0.9-65 user/system 916
ttf-droid 1.01-dfsg0maemo3 user/graphics 4392
tutorial-home-applet 0.6.16+0m5 user/support 1292

Processes Running (After Restart)
PID USER VSZ STAT COMMAND
1 root 1728 S /sbin/init
2 root 0 SW [kthreadd]
3 root 0 SW [ksoftirqd/0]
4 root 0 SW [events/0]
5 root 0 SW [khelper]
6 root 0 SW [kblockd/0]
7 root 0 SW [cqueue]
8 root 0 SW [twl4030-irqchip]
9 root 0 SW [twl4030-irq]
10 root 0 SW [omap2_mcspi]
11 root 0 SW [ksuspend_usbd]
12 root 0 SW [khubd]
13 root 0 SW [pdflush]
14 root 0 SW [pdflush]
15 root 0 SW [kswapd0]
16 root 0 SW [aio/0]
26 root 0 SW [ubi_bgt0d]
27 root 0 SW [kondemand/0]
28 root 0 SW [ubifs_bgt0_0]
106 root 1664 S /sbin/udevd --daemon
293 root 0 SW [vibra]
467 root 0 SW [bluetooth]
491 root 0 SW [kmmcd]
519 root 0 SW [nokia-av]
542 root 0 SW [wl12xx]
589 root 0 SW [mmcqd]
667 root 1776 S < /sbin/dsme -p /usr/lib/dsme/libstartup.so
673 root 3844 S /usr/sbin/sshd -D
681 root 8212 S /sbin/dsme-server -p /usr/lib/dsme/libstartup.so
696 root 0 SW [file-storage-ga]
713 root 3380 S /usr/sbin/bme_RX-51
723 messageb 3172 S < /usr/bin/dbus-daemon --system --nofork
728 root 3372 S /usr/libexec/n900-fmrx-enabler --nodaemon
730 root 2428 S /usr/sbin/sscd -f
734 root 4716 S /usr/sbin/alsaped -p 4 -f /usr/share/policy/etc/curre
749 root 15216 S /usr/sbin/omap3camd -d /dev/video0 -f /tmp/omap3camd0
757 root 3412 S /usr/sbin/sms-manager
759 haldaemo 4564 S /usr/sbin/hald --verbose=no --daemon=no --use-syslog
761 root 8100 S /usr/sbin/ohmd --no-daemon
764 root 3396 S /usr/sbin/csd -m -p call -p gprs -p info -p net -p si
767 pulse 81944 S < /usr/bin/pulseaudio --system --high-priority
775 root 3476 S /usr/sbin/sysinfod --system
780 root 5568 S < /sbin/mce --force-syslog
782 root 3636 S /usr/sbin/wappushd -b
785 root 3984 S /usr/lib/gconf2/gconfd-2
789 root 3328 S hald-runner
790 root 0 SW [bridge_work-que]
801 root 0 SW [sgx_perf]
803 root 0 SW [kjournald]
812 root 1528 S /usr/sbin/dsp-manager
819 haldaemo 3492 S hald-addon-gpio: listening on /sys/devices/platform/g
820 root 0 SW [SGXOSTimer/0]
824 root 0 SW [sgx_misr]
832 root 14972 S /usr/sbin/omap3camd -d /dev/video1
834 root 14236 S < /usr/bin/Xorg -logfile /tmp/Xorg.0.log -logverbose 1
847 haldaemo 3088 S hald-addon-usb-cable: listening on /sys/devices/platf
864 root 3624 S /usr/bin/clockd
865 root 3420 S /usr/lib/hal/hald-addon-generic-backlight
866 root 3424 S hald-addon-input: Listening on /dev/input/event3 /dev
868 haldaemo 3084 S hald-addon-mmc: listening on /sys/class/mmc_host/mmc0
874 root 3416 S /usr/lib/hal/hald-addon-als
875 root 3476 S /usr/lib/hal/hald-addon-bme
877 root 3432 S /usr/lib/hal/hald-addon-cpufreq
888 root 31960 S /usr/bin/signond
906 root 3408 S /usr/sbin/bluetoothd -n
908 user 2088 S /bin/ash /opt/autodisconnect/autodisconnect-bluetooth
953 user 2832 S dbus-launch --exit-with-session
955 user 1952 S sleep 600
957 user 2668 S < /usr/bin/dbus-daemon --fork --print-pid 5 --print-add
973 user 42928 S /usr/bin/maemo-xinput-sounds
976 root 0 SW< [krfcommd]
981 user 3320 S /usr/bin/ohm-session-agent
982 user 3344 S /usr/bin/profiled
1007 user 9268 S python /opt/battery-eye/beyed.py
1009 user 23164 S /usr/bin/maemo-launcher --send-app-died --booster gtk
1015 user 3848 S /usr/sbin/alarmd
1018 user 12500 S /usr/lib/sapwood/sapwood-server
1020 user 26100 S /usr/bin/systemui
1036 user 6516 S /usr/lib/gvfs/gvfs-hal-volume-monitor
1048 root 1972 S /usr/bin/iphbd
1051 user 6016 S /usr/lib/gvfs/gvfsd
1077 user 5540 S /usr/bin/mission-control
1084 user 23316 S < /usr/bin/hildon-sv-notification-daemon
1088 user 4676 S /usr/lib/telepathy/telepathy-ring
1120 user 3932 S /usr/bin/hildon-status-menu
1122 user 104m S /usr/bin/hildon-status-menu
1123 user 3932 S /usr/bin/camera-ui
1125 user 57720 S /usr/bin/camera-ui
1126 user 3932 S /usr/bin/hildon-home
1128 user 3932 S /usr/bin/hildon-desktop
1130 user 35156 S /usr/bin/hildon-home
1131 user 54816 S /usr/bin/hildon-desktop
1135 user 8364 S /usr/libexec/gnome-vfs-daemon
1147 user 11944 S /usr/lib/evolution-data-server/e-addressbook-factory
1159 user 4616 S /usr/bin/clipboard-manager
1160 user 34000 S N /usr/lib/tracker/trackerd
1162 user 3932 S /usr/bin/osso-connectivity-ui-conndlgs
1164 user 27260 S /usr/bin/osso-connectivity-ui-conndlgs
1165 user 16656 S /usr/bin/hildon-input-method
1167 user 40476 S /usr/sbin/browserd -d
1171 root 4132 S /usr/sbin/wlancond
1173 root 7984 S /usr/bin/location-proxy --no-detach
1174 root 20808 S < /usr/bin/tonegend -s ansi -b 100 -r 20 -D module-stre
1175 user 2084 S sh -c /opt/BatteryGraph/bin/BatteryGraphd
1177 root 27552 S python -OO /opt/maemo/usr/lib/advanced-power-monitor/
1180 root 2624 S /usr/bin/app-detect -p 1
1183 nobody 2164 S /usr/sbin/dnsmasq -k -i lo -a 127.0.0.1 -z
1190 user 3208 S /usr/lib/obex/obexd --nodaemon --opp --ftp --pcsuite
1198 user 24212 S /opt/BatteryGraph/bin/BatteryGraphd
1215 root 4528 S /usr/sbin/icd2 -l2
1259 user 39400 S < /usr/bin/mafw-dbus-wrapper mafw-gst-renderer
1260 root 5616 S /usr/sbin/hulda
1268 root 5616 S /usr/sbin/hulda
1270 user 7916 S /usr/bin/mafw-dbus-wrapper mafw-iradio-source
1275 user 16912 S /usr/bin/mafw-dbus-wrapper mafw-tracker-source
1283 user 9256 S /usr/bin/mafw-dbus-wrapper mafw-upnp-source
1285 user 1392 S /usr/sbin/temp-reaper
1301 user 4908 S /usr/sbin/maesync_controller
1314 user 16844 S /usr/bin/syncd
1317 user 24596 S /usr/bin/osso-abook-home-applet
1332 root 16016 S /usr/bin/eapd
1345 root 8240 S /usr/sbin/ke-recv
1377 user 14244 S /usr/libexec/hildon-thumbnailerd
1400 user 11528 S N /usr/lib/tracker/tracker-indexer
1406 root 1624 S /sbin/udhcpc -i wlan0 -s /etc/udhcpc/libicd_network_i
1476 root 2088 S /bin/ash /opt/autodisconnect/autodisconnect-network-c
1548 user 19932 S /usr/libexec/gst-video-thumbnailerd
1555 root 6452 S sshd: root@pts/0
1566 root 1952 S sleep 300
1567 root 2160 S -sh
1578 root 2160 R ps -aux

Re: Battery Dies too Quickly
 

Wow dude , you have tons of bloatware and useless battery eating apps :D

Remove those things

tutorial-home-applet
facebook-installer 1.0-4.1.1+0m5 user/other 88
facebook-services 0.5.5 user/hidden 52
foreca-installer 1.0.1.1+0m5 user/other 88
amazon-installer 1.0.1.1+0m5 user/other 96
battery-eye 0.7.7-1 user/utilities 196
batterygraph 0.3.2 user/utilities 356

There might be others , those are the ones that I noticed

Re: Battery Dies too Quickly
 

Hi Kurtis,

You'd like to try uninstalling advanced-power* to see if the problem persists. You may install it back later.

Also, would you tell me which options have you turned on in qcpufreq?

Re: Battery Dies too Quickly
 

Cool, thanks a lot for looking through that huge list :) I went ahead and got rid of those. It actually helped remove some other useless dependencies which is awesome.

Thanks! I deleted the advanced-power stuff. Although, maemo-list-user-packages still shows them installed, I'm not sure why. Apt shows them as removed.

As far as the QCPUFreq goes, here's what I can see. (I couldn't find a config file anywhere to copy and paste)

Settings
Enable auto-rotation - Checked
Enable overclocking - Not Checked
Load bq27x00_battery module - Not Checked

Main Screen
Min CPU Speed: 250MHz
Max CPU Speed: 600MHz
Scaling governor: ondemand
CPU Temp: 39' C
SmartReflex - Not Checked

Re: Battery Dies too Quickly
 

Hi Kurtis

Could you please tell me why would it make a difference if removed the following

tutorial-home-applet: doesnt not run in the background, it just a video which will run once started

these are just installers
foreca-installer 1.0.1.1+0m5 user/other 88
amazon-installer 1.0.1.1+0m5 user/other 96

thanks

Re: Battery Dies too Quickly
 

Umm, I'm sure it wouldn't make a difference in terms of discharging the battery. But I do appreciate the suggestion from HellFlyer. It helps keep my system clean and reduce the # of possible problem-apps :)

Re: Battery Dies too Quickly
 

also Check your email, if it has been kept on referesh every 15 mins it will drain the battery. Keep it something like an hour or so.

you can always go back and refresh the email if you are expecting any that instance.

Re: Battery Dies too Quickly
 

Hi kurtis. Do you know what is the parent process in your list that run sleep 300?

Re: Battery Dies too Quickly
 

I had he same issue with my N900 but after I flashed it, i noticed that the battery life was increased by 1/3th of what it was before. i think poor battery life is also a software problem.

Re: Battery Dies too Quickly
 

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.

Disable any desktop widgets (not including program shortccuts, those are harmless) and see if that helps. If it does, add them 1 at a time uintil you find the bad one.

Re: Battery Dies too Quickly
 

install and run powertop. when it starts, lock your phone. it runs for ~30 seconds. then post the output here.

also, reinstall batterygraph, and let it run for a day or so, then export the graph and post it here.

Re: Battery Dies too Quickly
 

Switch_! get on in here! You need to install powertop from developers repo.

You say the phone was from amazon. Was it BRAND SPANKING NEW or just new to you?

Which kernel are you running?

Such a low run time generally implies the CPU is not reaching C4 to sleep.

1. remove all widgets form desktop.
2. put phone into offline mode.
3. switch off and pull battery for 10s.
4. switch on and maintain offline mode.
5. let settle for ~4 minutes
6. run powertop and post output.

Re: Battery Dies too Quickly
 

I'm having same battery life but I considered it normal since I'm always online with jabber, gtalk, skype and sip.
Without them I remember I used to reach 8hrs

isn't it normal?

Re: Battery Dies too Quickly
 

vi_ ! Here I am! Another wonderful battery consumption thread. We love these. :D

Lets have a butchers at this powertop output then..... And just going back to review installed appz....

Re: Battery Dies too Quickly
 

what are the battery killer

Re: Battery Dies too Quickly
 

Okay, remove as follows:

Where <name of app> = ;

amazon-installer
appdownloader
autodisconnect
battery-eye
buddy
espeak
maxcpu
tutorial-home-applet

I have a feeling it may well be a conflict between either battery-eye and batterygraph or alternatively maxcpu and qcpufreq

Also, is it normal to have hildon-home, hildon-desktop, and hildon-status-menu running twice each....?

Sorted by *user* wildcard;

908 user 2088 S /bin/ash /opt/autodisconnect/autodisconnect-bluetooth
953 user 2832 S dbus-launch --exit-with-session
955 user 1952 S sleep 600
957 user 2668 S < /usr/bin/dbus-daemon --fork --print-pid 5 --print-add
973 user 42928 S /usr/bin/maemo-xinput-sounds
981 user 3320 S /usr/bin/ohm-session-agent
982 user 3344 S /usr/bin/profiled
1007 user 9268 S python /opt/battery-eye/beyed.py
1009 user 23164 S /usr/bin/maemo-launcher --send-app-died --booster gtk
1015 user 3848 S /usr/sbin/alarmd
1018 user 12500 S /usr/lib/sapwood/sapwood-server
1020 user 26100 S /usr/bin/systemui
1036 user 6516 S /usr/lib/gvfs/gvfs-hal-volume-monitor
1051 user 6016 S /usr/lib/gvfs/gvfsd
1077 user 5540 S /usr/bin/mission-control
1084 user 23316 S < /usr/bin/hildon-sv-notification-daemon
1088 user 4676 S /usr/lib/telepathy/telepathy-ring
1120 user 3932 S /usr/bin/hildon-status-menu
1122 user 104m S /usr/bin/hildon-status-menu
1123 user 3932 S /usr/bin/camera-ui
1125 user 57720 S /usr/bin/camera-ui
1126 user 3932 S /usr/bin/hildon-home
1128 user 3932 S /usr/bin/hildon-desktop
1130 user 35156 S /usr/bin/hildon-home
1131 user 54816 S /usr/bin/hildon-desktop
1135 user 8364 S /usr/libexec/gnome-vfs-daemon
1147 user 11944 S /usr/lib/evolution-data-server/e-addressbook-factory
1159 user 4616 S /usr/bin/clipboard-manager
1160 user 34000 S N /usr/lib/tracker/trackerd
1162 user 3932 S /usr/bin/osso-connectivity-ui-conndlgs
1164 user 27260 S /usr/bin/osso-connectivity-ui-conndlgs
1165 user 16656 S /usr/bin/hildon-input-method
1167 user 40476 S /usr/sbin/browserd -d
1175 user 2084 S sh -c /opt/BatteryGraph/bin/BatteryGraphd
1190 user 3208 S /usr/lib/obex/obexd --nodaemon --opp --ftp --pcsuite
1198 user 24212 S /opt/BatteryGraph/bin/BatteryGraphd
1259 user 39400 S < /usr/bin/mafw-dbus-wrapper mafw-gst-renderer
1270 user 7916 S /usr/bin/mafw-dbus-wrapper mafw-iradio-source
1275 user 16912 S /usr/bin/mafw-dbus-wrapper mafw-tracker-source
1283 user 9256 S /usr/bin/mafw-dbus-wrapper mafw-upnp-source
1285 user 1392 S /usr/sbin/temp-reaper
1301 user 4908 S /usr/sbin/maesync_controller
1314 user 16844 S /usr/bin/syncd
1317 user 24596 S /usr/bin/osso-abook-home-applet
1377 user 14244 S /usr/libexec/hildon-thumbnailerd
1400 user 11528 S N /usr/lib/tracker/tracker-indexer
1548 user 19932 S /usr/libexec/gst-video-thumbnailerd

Re: Battery Dies too Quickly
 

oh and get rid of that stupid flashlight program too, it is a known ballache.

Re: Battery Dies too Quickly
 

You're thinking of flashlight-extra which is the one that gives you the option of launching the flashlight when opening the lens cover, he only has flashlight-applet which I'm pretty sure doesn't cause any problems (it hasn't for me).

Re: Battery Dies too Quickly
 

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?

Re: Battery Dies too Quickly
 

2 - 3 hrs music is gonna frape your battery regardless. Then when you consider that you have all those IM accounts open too then I wouldn't say you got too many problems. Surfing the web aint gonna murder your phone, but powering the screen while you surf the web will. Sticking in HSDPA is less drain on the battery as it is not constantly "seeking" between 2G and 3G signals.

If you are still concerned post up the output from

Following instructions from vi_ earlier on in this thread

Re: Battery Dies too Quickly
 

i want to check if this is right

Re: Battery Dies too Quickly
 

Run it as 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.

Re: Battery Dies too Quickly
 

ops sorry here

Re: Battery Dies too Quickly
 

And you can confirm this output is from a 'fresh start' as detailed here?

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_

Re: Battery Dies too Quickly
 

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.

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.

Re: Battery Dies too Quickly
 

Here is my Powertop output after fresh start as explained before

Is here anything I should care about?

Thanks

Re: Battery Dies too Quickly
 

simply flash ur n900 and everything will be ok :D

Re: Battery Dies too Quickly
 

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.

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.

Re: Battery Dies too Quickly
 

Can we try to keep the chafe to a minimum please? Many of the programs people are suggesting for removal have NO background running components (with the possible exception of the battery monitoring programs).

Removing things like installers, or tutorials is fine for trying to recover space, but they'll have 0 impact on battery use. And CLI programs like espeak, or manually triggered scripts like flashlight? What does that have to do with battery use? Nothing. I think the author would have noted if the device were babbling constantly or emitting a bright light.

The more likely issue is there something happening with hardware being triggered, based on the high IRQ levels and dss usage. It may be a bad wifi or APN entry, or a bluetooth device asking for ID every few minutes. Or, it could be a bad chip or micro switch, maybe the device is close to a magnetic source (like a pouch magnet, or a motor) that's triggering the micro switches? Running the hardware tester app may be a good thing to try as well if you're trying to avoid a reflash.

There's enough going on here that I think your real solution is going to be to reflash to PR1.3 to eliminate possible software causes. Espeak is not a default component, nor are at lot of the packages listed. There's a lot of stuff installed, and if you didn't install it then someone else did, maybe before you got the device.

If you just got it, and didn't put all this on it, it will be a *lot* easier to backup your data, reflash, and just put the stuff you want on, vs trying to undo all the changes someone else did. Also, if your issue is settings or hardware based (which I suspect it is based on the log), a reflash will help pin point that quickly, vs lots of trial and error.

Re: Battery Dies too Quickly
 

@woody14619

i OC to 900mhz

Re: Battery Dies too Quickly
 

IMO the battery of n900 is to weak to power the phone to do all the task nokia 5800 XM same battery with n900

Re: Battery Dies too Quickly
 

Okay, obviously someone who knows what they are talking about!

Oh. Erm. Hang on one second.

Thats a direct contradiction to what you said above. Chafe? Reflash? Chafe = Reflash same as Reflash = Chafe.

We suggest that he removes things that are known to potentially cause issues - along with other apps running dbus daemons and the like and you, in contravention, suggest that the OP's only recourse is a complete reflash?

What a ballache.

I try to suggest flashing as a last resort, as these issues can be fixed in a multitude of ways that do not resort to a complete reflash and rebuild of the OS.

Either help, through analysis of posted outputs, or GTFO. Flash is last resort when everything else has failed.

Re: Battery Dies too Quickly
 

No, this is more or less perfect.

Re: Battery Dies too Quickly
 

I'm not smart enough to get my head around all the event logs posted here, but my battery was being drained by a faulty wireless router last year. I replaced the router and battery life returned to normal.

This got me thinking about the impact of wifi on battery life. After monitoring my data use for a few months, I realised that I was unlikely to exceed my 1 gig allowance anyway so I now keep wifi turned off except for specific circumstances (need more speed, big download, etc.). Running two radios instead of just one obviously uses more power. Lately, I get about two days from my battery.

Re: Battery Dies too Quickly
 

The OP said he JUST got his device a month ago in his top post. It's not clear if it's a second hand device or not, but the fact that there are multiple programs installed that he apparently doesn't recognize would indicate it's probably a second-hand device. Given that, I simply stated it would be far easier to backup what little content he's personally put on it in the past month, and re-flash it, rather than try to diagnose and undo what someone else did to it before he owned it! That's not chafe, it's common sense.

As I already noted, there's a lot of IRQ and dss activity going on, which indicate a bad setting or possibly faulty hardware. (Kudos to Andrew_b: Yes, it could be an external component, like bad wifi point, or a bluetooth device like I mentioned earlier.) I put in the post above alternate things to check for or try if he's trying to avoid doing a reflash.

At no point did I say "the ops o(sic) recourse is a complete reflash". Please don't put words in my mouth, saying I said something when clearly I said no such thing. (That's called lying in my country...) Sad that you find the need to be-little my comments to cover for your suggesting useless "fixes" like telling someone that uninstalling a tutorial video or a non-active app installer will help with their battery usage.

Re: Battery Dies too Quickly
 

I agree that removing applications that are not actively running won't do much to help the battery drain issues.

This phone is brand "spanking" new :) Also, I don't know if it makes much of a difference but it appears to have the latest firmware running on it.

I'm not sure how to check for faulty hardware. But here's my output of powertop:

Sorry for missing out on a day of this post. It looks like it stayed pretty active haha. Thanks guys :)

Re: Battery Dies too Quickly
 

It's no longer showing any of the same behavior. Dss is totally dead, and the IRQ counts look semi-sane (except for the wifi... that looks a little high still). Is it still exhibiting the drain problem?

It may in fact be an external cause, like a bad wifi router or bluetooth device pegging it. I once had a stale password in for a wifi router, and with the auto-connect attempts every 5 minutes or so it ate through half my battery in about 4 hours. Maybe something similar is happening?

Re: Battery Dies too Quickly
 

DSS is typically active whenever the screen is on. If the first measurement wasn't done with screen off, you'd get bad results.