maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Nokia N900 (https://talk.maemo.org/forumdisplay.php?f=44)
-   -   [HELP] 50% CPU Use When "Off", Constant CPU Use ~10% (https://talk.maemo.org/showthread.php?t=69219)

Switch_ 2011-02-01 12:33

[HELP] 50% CPU Use When "Off", Constant CPU Use ~10%
 
I have searched as I recall seeing recently a thread where someone else had the same 50% CPU Use when device is off reported through Battery Graph but I can't find the bloody thread..... As a last resort I am positing this new thread with the clue in the title, so that future searches may throw it up faster.

Please see the attached "Battery Graph snapshot;

http://i208.photobucket.com/albums/b...0201112454.png

Ok, so for the past week you can see constant CPU usage - not massively bothered about this, probably got some daemons and widgets constantly churning through the proc, and used to it at this point. Would be nice to resolve, but that's very much secondary.

However, when you scroll to the right hand side of the graph and check out the time period between 12am and 6am this morning you see a rapid reduction in mAh, caused by having the bleeding edge WiFi drivers still running in the background - but at 4am when my phone was complaining of low battery I got up, got the charger, switched it off and plugged it in next to my bed. From the moment I switched it off, I had 50% processor usage until the moment I switched it back on.....

Now that's wierd. Any comments, explanations, things to try out, or iser people out there who can explain this....? TIA.....

ndi 2011-02-01 14:59

Re: [HELP] 50% CPU Use When "Off", Constant CPU Use ~10%
 
Try searching forums for Conky, top and tracker.

E.g., searching for "conky battery" got me 3 threads about the issue in the first page (I have large pages).

I'm a bait clumsy now, I'm mobile, but search works.

vi_ 2011-02-01 15:19

Re: [HELP] 50% CPU Use When "Off", Constant CPU Use ~10%
 
also grap powertop from development repos and post output. That will give us a clear output of what is going on. Also run 'top' as root, organise by cpu and write down the process you see chewing up power the most.

Further to this what kernel are you using?

We need hard info bro!

Switch_ 2011-02-01 15:33

Re: [HELP] 50% CPU Use When "Off", Constant CPU Use ~10%
 
Thanks lads for the replies, although I fail to see what goodness either powertop, htop or top would be able to deliver considering the damn thing was switched off, ie; hard off, not soft off, loooong press of power button!!! I'll get the apps down and give you some more info.

@ndi, I'm like you mate, I like to keep the forums clean, but the booleans I looked for were more along the lines of "50% CPU when switched off", 50% CPU Use charging, %0% CPU use idle" etc as I know I saw a thread with that in it but I couldn't find it for the life of me. 40 minutes searching TALK is enough for anyone I would say.....

Running on Titans kernel-power 46 from extras-devel, modified with the bleeding edge WiFi driver mods from lxp.

top from root output:

Code:

Mem: 234408K used, 11004K free, 0K shrd, 1936K buff, 76744K
CPU: 15.3% usr 10.0% sys  0.0% nice 74.6% idle  0.0% io  0.
Load average: 1.27 0.68 0.90
  PID  PPID USER    STAT  RSS %MEM %CPU COMMAND
 1297  1189 user    R    13244  5.3  7.0 /usr/bin/hildon-ho
 1035  701 root    S <  15324  6.2  5.1 /usr/bin/Xorg -log
 1300  1189 user    S    9792  3.9  3.5 /usr/bin/hildon-de
 1291  1189 user    S    12148  4.9  2.1 /usr/bin/hildon-st
  944    1 pulse    S <  3200  1.3  1.9 /usr/bin/pulseaudi
 8759  1189 user    S    10240  4.1  1.3 /usr/bin/osso-xter
 8864  8840 root    R      740  0.3  0.9 top
  968  701 root    S <  2312  0.9  0.7 /sbin/mce --force-
 8766    1 root    S    2880  1.1  0.5 /usr/sbin/fmtxd
  765    1 messageb S <  2032  0.8  0.3 /usr/bin/dbus-daem

powertop from root output:
Code:

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 16510us

C#      | Ratio  | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
    C0 |  21.1% |          |  1150 MHz |  nan% |
    C1 |  0.5% |    0.5ms |
    C2 |  78.3% |    4.0ms |
    C3 |  0.0% |    2.1ms |
    C4 |  0.0% |          |

IRQ#    | Activity  | Type          | Name
--------+------------+----------------+---------------------------
    61 |      11953 |          INTC | i2c_omap
    37 |      5036 |          INTC | gp
    11 |      4211 |          INTC | prcm
    56 |      2911 |          INTC | i2c_omap
    57 |        257 |          INTC | i2c_omap
    21 |        196 |          INTC | SGX
    12 |        65 |          INTC | DMA
    86 |        64 |          INTC | mmc1
    225 |        11 |          GPIO | omap2-onenand
    67 |          5 |          INTC | ssi_p1_mpu_irq0
    71 |          4 |          INTC | ssi_gdd
    202 |          3 |          GPIO | wl1251
    311 |          2 |          GPIO | ssi_p1_cawake_gpio

PID#    | Activity  | Name          | Function Entry (Expire)
--------+------------+----------------+---------------------------
      0 |      3726 |  <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
  1297 |      1146 |    hildon-home | schedule_hrtimeout_range (hrtimer_wakeup)
    38 |        192D|            awk | cpufreq_governor_dbs (delayed_work_timer_fn)
    968 |        138 |            mce | schedule_hrtimeout_range (hrtimer_wakeup)
  1291 |        60 |hildon-status-m | schedule_hrtimeout_range (hrtimer_wakeup)
    740 |        33 |      bme_RX-51 | sys_timer_settime (posix_timer_fn)
  8759 |        18 |    osso-xterm | schedule_hrtimeout_range (hrtimer_wakeup)
    740 |        18 |      bme_RX-51 | schedule_timeout (process_timeout)
  1260 |        15 |          iphbd | schedule_hrtimeout_range (hrtimer_wakeup)
    591 |        13 |          mmcqd | schedule_timeout (process_timeout)
    591 |          6 |          mmcqd | queue_delayed_work (delayed_work_timer_fn)
  1035 |          4 |          Xorg | queue_delayed_work (delayed_work_timer_fn)
    968 |          4 |            mce | tsc2005_start_scan (tsc2005_esd_timer_handler)
  8873 |          4 |      browserd | futex_wait (hrtimer_wakeup)
  1035 |          3 |          Xorg | hrtimer_start (it_real_fn)
    992 |          3 |      sgx_perf | queue_delayed_work (delayed_work_timer_fn)
    689 |          3 |          dsme | do_nanosleep (hrtimer_wakeup)
  8605 |          3 |        wl12xx | queue_delayed_work (delayed_work_timer_fn)
    689 |          3 |          dsme | __enqueue_rt_entity (sched_rt_period_timer)
      1 |          3D|  <kernel core> | queue_delayed_work (delayed_work_timer_fn)
  8605 |          2 |        wl12xx | schedule_timeout (process_timeout)
    740 |          2 |      bme_RX-51 | do_nanosleep (hrtimer_wakeup)
      0 |          2 |  <kernel core> | queue_delayed_work (delayed_work_timer_fn)
    716 |          2D|<kernel module> | queue_delayed_work (delayed_work_timer_fn)
    30 |          2 |          mount | setup_wb_timer (wb_timer_fn)
  1349 |          1 |      wlancond | ieee80211_ioctl_siwpower (ieee80211_dynamic_ps_timer)
  1073 |          1 | hald-addon-bme | schedule_hrtimeout_range (hrtimer_wakeup)
  1367 |          1 |  BatteryGraphd | schedule_timeout (process_timeout)
    591 |          1 |          mmcqd | schedule_timeout (process_timeout)
  1367 |          1 |  BatteryGraphd | ubifs_wbuf_write_nolock (wbuf_timer_callback_nolock)
    14 |          1 |        pdflush | blk_plug_device (blk_unplug_timeout)
  8897 |          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:  81%|RET:  0%|INA:  0%| ON:  18%| now:(OFF)
    per |OFF:  0%|RET:  76%|INA:  0%| ON:  23%| 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:  61%| ON:  38%| now:(ON)
  neon |OFF:  0%|RET:  0%|INA:  76%| ON:  23%| now:(ON)
    mpu |OFF:  0%|RET:  0%|INA:  76%| ON:  23%| 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
        |
  ckgen |          CORE |          PERI |          96M
        |          48M |          12M |          54M
        |      EMU_CORE |
    dss |      DSS_IDLE
    per |        GPIO2 |        GPIO3 |        GPIO4
        |        GPIO5 |        GPIO6 |

Total wakeups  30130, 1004.3/s | IRQ 24718, 823.9/s | Timers 5412, 180.4/s
HW wakeups      115,  3.8/s |    Real gp_timers expired  172,  5.7/s
Nokia-N900:~#

Do you want to see these outputs with as many other processes killed as possible, as these wefre taken just now with WiFi connected, web open, FAM open etc...?

Switch_ 2011-02-01 18:49

Re: [HELP] 50% CPU Use When "Off", Constant CPU Use ~10%
 
unethical I know but buuuump!

vi_ 2011-02-01 19:11

Re: [HELP] 50% CPU Use When "Off", Constant CPU Use ~10%
 
oops, should have seen that. does it really matter if your cpu is running while charging? mine says that somtimes too. perhaps it is a bug in batterygraph...

I think a more serious damage is you frankly unbelievable 30000 wake ups a second on powertop! do you have a battery life of about 15 minutes?

Switch_ 2011-02-02 07:50

Re: [HELP] 50% CPU Use When "Off", Constant CPU Use ~10%
 
I do have a relatively poor battery life - some people say that they can get 36 hours out of their phone but mine, lucky to get 24 hours to be honest.

Any ideas what could be causing it....?

vi_ 2011-02-02 08:11

Re: [HELP] 50% CPU Use When "Off", Constant CPU Use ~10%
 
I can get a full day, connected to the net all day (albeit through wifi with touches of 3G when I am outta range).

As I dont know your particular setup this could be tough however I do have a penchant for battery life extension.

This is a radical approach but can you give me the powertop output from about 3 minutes after a fresh reboot? I want you to ONLY load xterm, start powertop then quickly press the screen lock key and leave it for 41 seconds. Do this with wifi disconnected and on 2G mode.

The reason I ask for this is I am familiar with what the device should show when idiling with nothing.

From the above PT there are some bad things a-foot. The fact your CPU never reaches C4 sleep and you have over 15000 wakeups on the I2C bus means you phone is never going to sleep. This in turn is face r*ping your battery life.

Also I checked 'charging while turned off' on my phone last night and the CPU was also being used 50% so I wouldnt worry about that so much.

Switch_ 2011-02-02 08:52

Re: [HELP] 50% CPU Use When "Off", Constant CPU Use ~10%
 
Nice one fella. Here's the powertop output (bearing in mind I have lots of widgets like pedometer / digital clock that are updating every n milliseconds on my desktop(s), three minutes after boot once system has settled in straight GSM without WiFi or any other tethered connections. Bleeding edge drivers are not loaded either. Standard O/C, 250Mhz lower and 1Ghz higher clock speeds on CPU. Switch to N900 for ouput, will update post in about 5 minutes...............

EDIT: Powertop output from device;

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 28839us

C#      | Ratio  | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
    C0 |  0.8% |          |  1150 MHz |  nan% |
    C1 |  0.0% |    0.2ms |
    C2 |  3.7% |    7.7ms |
    C3 |  27.4% |  191.4ms |
    C4 |  68.1% |  817.6ms |

IRQ#    | Activity  | Type          | Name
--------+------------+----------------+---------------------------
    37 |        211 |          INTC | gp
    11 |        203 |          INTC | prcm
    56 |        125 |          INTC | i2c_omap
    57 |        34 |          INTC | i2c_omap
    21 |        10 |          INTC | SGX
    12 |          5 |          INTC | DMA
    225 |          4 |          GPIO | omap2-onenand

PID#    | Activity  | Name          | Function Entry (Expire)
--------+------------+----------------+---------------------------
      0 |        116 |  <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
    38 |        48D|            awk | cpufreq_governor_dbs (delayed_work_timer_fn)
  1274 |        30 | hildon-desktop | schedule_hrtimeout_range (hrtimer_wakeup)
  1406 |        29 |          fmtxd | schedule_hrtimeout_range (hrtimer_wakeup)
  1588 |        19 |    osso-xterm | schedule_hrtimeout_range (hrtimer_wakeup)
    732 |          8 |      bme_RX-51 | sys_timer_settime (posix_timer_fn)
      0 |          5 |  <kernel core> | hrtimer_start (tick_sched_timer)
    732 |          3 |      bme_RX-51 | schedule_timeout (process_timeout)
      1 |          3D|  <kernel core> | queue_delayed_work (delayed_work_timer_fn)
    690 |          3 |          dsme | __enqueue_rt_entity (sched_rt_period_timer)
  1021 |          2 |          Xorg | queue_delayed_work (delayed_work_timer_fn)
    991 |          2 |      sgx_perf | queue_delayed_work (delayed_work_timer_fn)
    732 |          2 |      bme_RX-51 | do_nanosleep (hrtimer_wakeup)
    690 |          2 |          dsme | do_nanosleep (hrtimer_wakeup)
    718 |          2D|<kernel module> | queue_delayed_work (delayed_work_timer_fn)
  1021 |          1 |          Xorg | hrtimer_start (it_real_fn)
    30 |          1 |          mount | setup_wb_timer (wb_timer_fn)
    936 |          1 |          ohmd | schedule_hrtimeout_range (hrtimer_wakeup)
    14 |          1 |        pdflush | ubifs_wbuf_write_nolock (wbuf_timer_callback_nolock)
    14 |          1 |        pdflush | ubifs_wbuf_write_nolock (wbuf_timer_callback_nolock)
  1231 |          1 |mission-control | schedule_hrtimeout_range (hrtimer_wakeup)
  1426 |          1 |    gconftool-2 | queue_delayed_work (delayed_work_timer_fn)
    968 |          1 |            csd | schedule_hrtimeout_range (hrtimer_wakeup)
  1266 |          1 |hildon-status-m | schedule_hrtimeout_range (hrtimer_wakeup)
  1611 |          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:  95%|RET:  3%|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:  68%|RET:  26%|INA:  2%| ON:  2%| now:(ON)
  neon |OFF:  68%|RET:  27%|INA:  3%| ON:  0%| now:(ON)
    mpu |OFF:  68%|RET:  27%|INA:  3%| 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
        |
  ckgen |          CORE |          PERI |          96M
        |          48M |          12M |          54M
        |      EMU_CORE |
    per |        GPIO2 |        GPIO3 |        GPIO4
        |        GPIO5 |        GPIO6 |

Total wakeups  876,  29.2/s | IRQ  592,  19.7/s | Timers  284,  9.5/s
HW wakeups      203,  6.8/s |    Real gp_timers expired  211,  7.0/s

As I suspected it looks a helluva lot cleaner from fresh boot, so something is chewing up the system when programs are run and then close - guess it's just not a clean close. I'm no linux buff so the question is, is there anything like "Windo$e Task Manager" that I can kill processes and process trees with intergrated in this OS, or an equivalent app?

Switch_ 2011-02-02 09:22

Re: [HELP] 50% CPU Use When "Off", Constant CPU Use ~10%
 
After turning on the pedometer and having a 5 minute blast on Angry Birds I'm back to 22,400 wakeups and 0.8% time in C4 sleep mode.

Turning off the pedometer without a reboot inbetween returns the wakeups down to 852, with 82.8% time spent in C4 sleep for the CPU.

Therefore, the unusual number of wakeups is down to the pedometer. I'll leave it off for a while and see what happens to the battery life.

Thanks for the info on the 50% CPU use when charging vi_, nice one :D

ndi 2011-02-02 11:20

Re: [HELP] 50% CPU Use When "Off", Constant CPU Use ~10%
 
I don't have high CPU while charging. I'm leaning towards a daemon.

Also, pedometer, if it's the one counting steps, is running a loop and monitoring accelero several times a second. That can't be good.

If you need to kill stuff, ps from terminal gets you processes and kill kills them. Killall is better.

Frankly, you should not be there. Killing a drain is last resort. It shouldn't be there in the first place.

Also, yes, TMO search vacuums. I have used Google on many occasions.

Switch_ 2011-02-02 11:31

Re: [HELP] 50% CPU Use When "Off", Constant CPU Use ~10%
 
I don't have high CPU usage whilst charging and the device is ON, but it's one of the very times that I have switched it OFF and charged it, and hence noticing this 50% use scenario. Thanks for the info on killall and ps, I'll give them a shot but currently am monitoring battery without the pedometer switched on.

TMO search vacuums. I like it!

artishox 2011-02-02 12:18

Re: [HELP] 50% CPU Use When "Off", Constant CPU Use ~10%
 
I had similar problem some time ago - this is what worked for me:
1) reflashing to clean 1.3
2) Installing apps I need one at the time and monitoring battery life and cpu after each new app.
This way I managed to optimize my battery life to 5 days (I do not use wifi and 3g, and I have only 2 desktops enabled with minimum of widgets I use).

ascag 2011-02-02 12:47

Re: [HELP] 50% CPU Use When "Off", Constant CPU Use ~10%
 
Some months ago, there was a discussion thread about a bug in Hildon-Desktop causing high CPU usage:

http://talk.maemo.org/showthread.php?t=54462

As far as I understood, to use certain programs triggered this bug, which caused a constant CPU usage by some sub-process in the hildon desktop. It seems that this bug is still present in 1.3.

One of the programs which triggered this bug seems to be Catorize (http://maemo.org/downloads/product/Maemo5/catorise/)

Should have have Catorize installed, you might check whether the CPU usage becomes normal after rebooting, while not launching any application over the application menu.

I had this problem of ~10% CPU during idle, deinstalling Catorize and rebooting solved the issue for me.

Switch_ 2011-02-02 13:04

Re: [HELP] 50% CPU Use When "Off", Constant CPU Use ~10%
 
No, no catorize on mine mate, but thanks for the heads up. The process that continually chews my CPU is hildon-home, not hildon-desktop, but that may well be linked to the pedometer mentioned earlier.

Monitoring battery life currently with pedometer switched off, see what happens, I'll report back if that was the case.

rm53 2011-02-02 13:21

Re: [HELP] 50% CPU Use When "Off", Constant CPU Use ~10%
 
@Switch_ didn't you say you had 50% CPU while N900 is hard off? This is ridiculous, when phone is OFF nothing is running, no CPU. I assume your Battery Graph is simply showing nonsense. How would Battery Graph know what is going on in CPU when system is OFF?

If your battery drains while phone is off, either the phone hardware has a hard failure (N900 -> Nokia Service) or the battery is dead (easy to replace).

Switch_ 2011-02-02 13:39

Re: [HELP] 50% CPU Use When "Off", Constant CPU Use ~10%
 
@rm53, Yes mate, 50% use shown in Batterygraph when phone is HARD OFF.... I was gobsmacked by it myself, hence the initial reason for the post. Guess it may simply be a bug in batterygraph, as vi_ reported the same from his system......

ndi 2011-02-02 14:57

Re: [HELP] 50% CPU Use When "Off", Constant CPU Use ~10%
 
Nothing runs when phone is hard off, not the OS not batterygraph.

My guess is that either

a) Batterygraph has no data so it draws the last known value for the off period (likely)

b) You didn't off it.

To exclude b) just power it off, count to 20 and hold the power button for a little while. You should see the white LED fading in. DO NOT LET IT FINISH. This is just to make sure it's off, because after it appears off it still does stuff for a few seconds and pulling battery can corrupt root.

Once you know it's off, pull the battery. See how that shows after a while.

Note, however, that the phone is NOT off if it has power via USB, be it charging or connected to a PC or whatever. It boots to a minimal stage, where daemons like BME start but no user login (IIRC). If it is charging and "off" then the CPU might as well be at 50% for what I know but it's likely that in that stage data about load is not available.

Also, IIRC the Catorize bug was fixed? It had to do with the fact that the menu always scrolled in the original. Once Catorize or any folder thing kicked in and there was no scrolling, the code that did the elastic band thing never finished, bouncing one pixel forever and eating CPU.

That can be fixed by either using ApMeFo to make folders (but no to few) or not scrolling (which is hard) or killing the Hildon thing. I do distinctly remember them fixing that in 1.3 - I no longer have the bug. I use ApMeFo for 10 folders or so with zero issues.

Anyhow, back to the point. There is no CPU when phone is off. Also, please use either batterygraph or the commandline to see voltage of battery when charged completely. (x-term command is "lshal | grep battery").

You might have a feeble battery, as suggested. Oh, and, get cpumem-applet. It offers insight on CPU load all the time. Once it seems to not go down, use top or conky to see the troublemaker.

Also, how many images, videos, sounds do you have? A bad/lot of media can have the tracker track for hours.

Switch_ 2011-02-02 16:11

Re: [HELP] 50% CPU Use When "Off", Constant CPU Use ~10%
 
Quote:

Originally Posted by ndi (Post 934257)
Nothing runs when phone is hard off, not the OS not batterygraph.

Absolutely, that is precisely what I was most confused about - hard off = all systems, services and processes are dead; defunkt; killed; not running; unloaded from RAM; to all extents and purposes DO NOT EXIST! That's what had me so confused about the phone being hard off and yet still data somehow being sent to batterygraph. As you also state, takes data from the last known point and extrapolates it until next data point is taken would explain it.

Quote:

Originally Posted by ndi (Post 934257)
Note, however, that the phone is NOT off if it has power via USB, be it charging or connected to a PC or whatever. It boots to a minimal stage, where daemons like BME start but no user login (IIRC). If it is charging and "off" then the CPU might as well be at 50% for what I know but it's likely that in that stage data about load is not available.

Ah, now, you make a very good point there, one that I hadn't considered. BME must be running to charge the battery therefore there is minimal OS activity albeit background. Based on that you could potentially say that data can be passed to batterygraph as I would imagine that BME is one of the services that it pulls data from. From this you could also say that the processor is going to running threads, it's just a question of how many and how intensively.

Quote:

Originally Posted by ndi (Post 934257)
Anyhow, back to the point. There is no CPU when phone is off. Also, please use either batterygraph or the commandline to see voltage of battery when charged completely. (x-term command is "lshal | grep battery").

Potentially - see above.....? I'll take a look at mAh / V on full charge and let you know.

Quote:

Originally Posted by ndi (Post 934257)
You might have a feeble battery, as suggested. Oh, and, get cpumem-applet. It offers insight on CPU load all the time. Once it seems to not go down, use top or conky to see the troublemaker.

I use CPU-MEM Applet and have done for a loooooong time, it never reports considerable and sustained CPU activity or load unless I am performing a task that calls for it.

Quote:

Originally Posted by ndi (Post 934257)
Also, how many images, videos, sounds do you have? A bad/lot of media can have the tracker track for hours.

An absolute sh*tload - about 4.5Gb videos, 16Gb Music and about 2Gb images. Although I don't believe any of them are "bad". tracker never seems to rate highly in the list of running processes in conky.

Thanks for all the replies lads :D

ndi 2011-02-02 18:57

Re: [HELP] 50% CPU Use When "Off", Constant CPU Use ~10%
 
Well, Conky is more unstable than cpumem for some reason. e.g., I have seen Conky report 20% load while cpuem said 100 and since it was running apt--

Sorry, Fennec interpreted a space as send.

Where was I?

Ah, Conky isn't the most reliable out there. If cpumem says it's cool, it's cool.

Let us know how lshal claims the battery has been (ab) used and see how it's faring. Frankly, locking the CPU at 50% should give you about 2 hours autonomy (or so) and warm the device.

If you don't see cpumem show you 50%, it's probably an artifact from batterygraph or another program that gets tricked like Conky.

From experience, background CPU is noticeable. Leaving MC do a copy over wifi depleted my battery in 1.5 hours (wasn't full). Now, the CPU was not 50%, granted, but it's not like load is a direct indication of consumption. I overclock as a matter of life and I know this to be true.

So, AFAICT, your CPU is not locked to 50%. Besides, it's reasonably hard to lock a single core to 50%.

How much do you get out of your battery, full to empty, on light and heavy usage? (light: say 20 minutes call, 1 hour browse via wifi, 2/5 backlight, 2G, plus a little fiddle).

Also, if you charge at night to 95+, how much is left in the morning? My 8 hour standby eats between 10 and 15% (connected to wifi via WPA, BT, 3G).

Switch_ 2011-02-03 08:53

Re: [HELP] 50% CPU Use When "Off", Constant CPU Use ~10%
 
Ok, ran a full charge last night (which took forever compared to normal btw) and the phone was still showing FULL BATTERY this morning after being disconnected from the wall at 2200 last night.

The results from lshal | grep battery are as follows:

Code:

battery.charge_level.capacity_state = 'full'  (string)
  battery.charge_level.current = 8  (0x8)  (int)
  battery.charge_level.design = 8  (0x8)  (int)
  battery.charge_level.last_full = 8  (0x8)  (int)
  battery.charge_level.percentage = 96  (0x60)  (int)
  battery.charge_level.unit = 'bars'  (string)
  battery.is_rechargeable = true  (bool)
  battery.present = true  (bool)
  battery.rechargeable.is_charging = false  (bool)
  battery.rechargeable.is_discharging = true  (bool)
  battery.remaining_time = 21600  (0x5460)  (int)
  battery.remaining_time.calculate_per_time = false  (bool)
  battery.reporting.current = 1222  (0x4c6)  (int)
  battery.reporting.design = 1262  (0x4ee)  (int)
  battery.reporting.last_full = 1222  (0x4c6)  (int)
  battery.reporting.unit = 'mAh'  (string)
  battery.type = 'pda'  (string)
  battery.voltage.current = 4153  (0x1039)  (int)
  battery.voltage.design = 4200  (0x1068)  (int)
  battery.voltage.unit = 'mV'  (string)
  info.capabilities = {'battery'} (string list)
  info.category = 'battery'  (string)

So no, battery is not a dodgy one I don't believe.....

ndi 2011-02-03 13:32

Re: [HELP] 50% CPU Use When "Off", Constant CPU Use ~10%
 
Allright, seems fine. Let's see how it fares today. Please report back with another lshal output and aproximate usage.


All times are GMT. The time now is 18:06.

vBulletin® Version 3.8.8