I'm having problems with poor battery life, i've got another one on the way as my present one is over a year old. But i was wondering if it was something other than battery age. I've installed conky and been looking @ the processors running and tbh i aint got a clue. i've been through the forum looking for solutions but still no joy.

On one thread a member suggested typing 'ps lax' and posting the result so i put ps lax into xterm and it came up with this.....what does it mean?? and does it explain my battery issue???

978 user 2832 S dbus-launch --exit-with-session
979 user 2924 S < /usr/bin/dbus-daemon --fork --print-pid 5 --print-add
989 user 42928 S /usr/bin/maemo-xinput-sounds
993 root 0 SW< [krfcommd]
996 user 3344 S /usr/bin/profiled
1002 user 3320 S /usr/bin/ohm-session-agent
1040 user 9416 S python /opt/battery-eye/beyed.py
1049 user 23148 S /usr/bin/maemo-launcher --send-app-died --booster gtk
1064 user 3848 S /usr/sbin/alarmd
1067 root 1972 S /usr/bin/iphbd
1068 user 12500 S /usr/lib/sapwood/sapwood-server
1070 user 26100 S /usr/bin/systemui
1082 user 6516 S /usr/lib/gvfs/gvfs-hal-volume-monitor
1084 user 6016 S /usr/lib/gvfs/gvfsd
1174 user 5592 S /usr/bin/mission-control
1180 user 23316 S < /usr/bin/hildon-sv-notification-daemon
1184 user 4676 S /usr/lib/telepathy/telepathy-ring
1186 user 3932 S /usr/bin/hildon-status-menu
1187 user 87776 S /usr/bin/hildon-status-menu
1190 user 3932 S /usr/bin/camera-ui
1192 user 54300 S /usr/bin/camera-ui
1193 user 3932 S /usr/bin/hildon-home
1195 user 3932 S /usr/bin/hildon-desktop
1197 user 77284 S /usr/bin/hildon-desktop
1198 user 52668 S /usr/bin/hildon-home
1201 user 8364 S /usr/libexec/gnome-vfs-daemon
1209 user 21984 S /usr/lib/evolution-data-server/e-addressbook-factory
1223 user 4616 S /usr/bin/clipboard-manager
1224 user 33616 S N /usr/lib/tracker/trackerd
1226 user 3932 S /usr/bin/osso-connectivity-ui-conndlgs
1228 user 17228 S /usr/bin/hildon-input-method
1230 user 27508 S /usr/bin/osso-connectivity-ui-conndlgs
1231 user 42728 S /usr/sbin/browserd -d
1233 root 3648 S /usr/bin/espeaktimed
1238 root 4132 S /usr/sbin/wlancond
1241 root 7984 S /usr/bin/location-proxy --no-detach
1243 root 20808 S < /usr/bin/tonegend -b 100 -r 20 -D module-stream-resto
1246 root 2084 S /bin/sh -e -c while [ ! -e /opt/smscon ]; do slee
1251 root 2624 S /usr/bin/app-detect -p 1
1254 nobody 2164 S /usr/sbin/dnsmasq -k -i lo -a 127.0.0.1 -z
1269 root 3748 S /usr/sbin/headphoned
1323 user 3208 S /usr/lib/obex/obexd --nodaemon --opp --ftp --pcsuite
1375 root 4528 S /usr/sbin/icd2 -l2
1376 root 5616 S /usr/sbin/hulda
1384 user 2088 S /bin/sh /usr/bin/ringtonedctl startwait
1397 user 42140 S /usr/bin/ringtoned
1430 user 28444 S /usr/bin/sp360d
1447 user 39796 S < /usr/bin/mafw-dbus-wrapper mafw-gst-renderer
1448 root 5616 S /usr/sbin/hulda
1453 user 8048 S /usr/bin/mafw-dbus-wrapper mafw-iradio-source
1460 user 16912 S /usr/bin/mafw-dbus-wrapper mafw-tracker-source
1464 user 9256 S /usr/bin/mafw-dbus-wrapper mafw-upnp-source
1466 user 1392 S /usr/sbin/temp-reaper
1481 user 4908 S /usr/sbin/maesync_controller
1494 user 16844 S /usr/bin/syncd
1497 user 27048 S /usr/bin/osso-abook-home-applet
1512 root 8240 S /usr/sbin/ke-recv
1551 user 14240 S /usr/libexec/hildon-thumbnailerd
1577 user 13724 S /usr/share/foreca-weather/control
1697 user 3932 S /usr/bin/browser
1698 user 42520 S /usr/bin/browser
1753 user 107m S /usr/sbin/browserd -s 1753 -n browserui
1804 user 34164 S /usr/bin/conky -d -c /etc/conky/conky.conf
1821 user 3932 S /usr/bin/osso-addressbook
1822 user 30972 S /usr/bin/osso-addressbook
1826 user 3932 S /usr/bin/rtcom-call-ui
1827 user 32464 S /usr/bin/rtcom-call-ui
1830 user 3932 S /usr/bin/rtcom-messaging-ui
1831 user 32508 S /usr/bin/rtcom-messaging-ui
1841 user 65984 S /usr/sbin/browserd -s 1841 -n RTComMessagingServer
1866 user 3932 S /usr/bin/image-viewer
1868 user 34200 S /usr/bin/image-viewer
1870 user 3932 S /usr/bin/Calendar
1871 user 29848 S /usr/bin/Calendar
1880 root 1624 S /sbin/udhcpc -i wlan0 -s /etc/udhcpc/libicd_network_i
1965 user 3932 S /usr/bin/modest
1966 user 63404 S /usr/bin/modest
2117 user 3932 S /usr/bin/osso-xterm
2118 user 31612 S /usr/bin/osso-xterm
2120 user 2788 S gnome-pty-helper
2121 user 2160 S -sh
2124 user 2160 R ps lax
2125 root 1952 S sleep 3

i would prefer to get my hands dirty (and pick up some know how) and sort this out rather than re-installing, hopefully someone can make head and tails about the above list???

on the battery side, check my battery test thread for a good replacement.

cheers i already have and i settled on the Japod ordered yesterday after consulting your thread

Anyone?? lol

bit quiet in here tonight..........

TBH, I'm not too sure about diagnosing what is causing battery drainage, but a process list generally isn't very useful (although it might allow a knowledgeable user to spot a problem app). However you can start by running top and seeing what is using CPU, and you can also run powertop (it's in extras-devel) when it is idling to see which processes are waking it up from idle, stopping it being in it's lowest power state.

Ended up taking plunge and reflashed emmc and root now battery life back to normal again :-D

Do you have BatteryGraph installed? From it, after restarting the device and letting it charging without opening anything while you go sleep or whatever that can take 4h+, you can see if there's something taking your phone's battery. It won't say what, but will say yes or no.

From that, I can say for "sure" that flashlight-extra AND dbus-switchboard are two applications that do that. If you have any of them installed, check them out of your phone (flashlight-extra has an worst time because you need to remove more files like here:
http://talk.maemo.org/showpost.php?p...3&postcount=19

And I guess that's all. Are there any threads about "bad" applications (in this sense)? I'm trying to take a closer look of what I put on the phone, but I'm being lucky to not step in any bad ones after taking closer care...

Tbh it all went wrong when i installed flashlight extra which i uninstalled not knowing that was'nt the final step. having reflashed i'm now more careful on what i install and how i install them. this forum is brilliant and the answers are usually all there, you've just got to take the time to look for them, lesson learned. At least i've got a spare battery on the way now since my battery life has now returned.

Actually, the correct way to remove flashlight-extra is "apt-get purge flashlight-extra" as root in the terminal. The files are left behind because apt sees them as configuration files and apt leaves configuration files in case you want to reinstall the program and keep your old configuration, that is unless you explicitly tell apt to remove them with the purge command.