Reply
Thread Tools
Posts: 32 | Thanked: 17 times | Joined on Oct 2010
#1
Hello, I know there are some other posts on this topic, but I wanted this to be separate as I'm not sure if it's hardware, software or charger fault related.

To keep it short - After I updated from 1.2 to 1.3 my wall charger didn't load my n900 battery, meanwhile usb charger performed as usual. So I started to think that there is some app or something that uses too much power - that wall charger cannot handle it. So I reflashed my device to 1.3 and installed battery graph to see what's wrong.



URL to Picture

At the begining it charged from wall charger (see 19.12.2010 11:30 to 12:00) and power consumption was quite low (10% drop in approximately 10 h), but then in 2012.2010 some background app or something kicked in power consumption doubled. and wall charger wasn't able to charge anything overnight. Then USB charging worked well but still some cpu usage can be observed (I didn't use my device almost at all) and now in 22.12.2010 power consumption returned to previous level.

Here is printout from charging monitor:

Wall charger:
~ $ lshal -m

Start monitoring devicelist:
-------------------------------------------------
17:33:34.325: usb_device_1d6b_2_musb_hdrc property usb_device.vbus = 1 (0x1)
17:33:34.506: bme property maemo.charger.connection_status = 'connected'
17:33:34.540: bme property maemo.charger.type = 'unknown'
17:33:34.619: bme property maemo.rechargeable.positive_rate = true
17:33:35.141: bme property battery.rechargeable.is_discharging = false
17:33:35.162: bme property battery.rechargeable.is_charging = true
17:33:35.176: bme property battery.remaining_time = 7200 (0x1c20)
17:33:35.187: bme property maemo.rechargeable.charging_status = 'on'
17:33:35.242: bme property maemo.charger.type = 'wall charger'
17:34:21.306: bme property battery.reporting.current = 601 (0x259)
17:34:24.421: platform_kb_lock property button.state.value = true
17:34:24.430: platform_kb_lock condition ButtonPressed = cover
17:34:24.569: platform_kb_lock property button.state.value = false
17:34:24.577: platform_kb_lock condition ButtonPressed = cover
17:34:24.797: bme property battery.voltage.current = 3815 (0xee7)
USB charging
~ $ lshal -m

Start monitoring devicelist:
-------------------------------------------------
18:18:30.601: platform_cam_focus property button.state.value = true
18:18:30.623: platform_cam_focus condition ButtonPressed = activity
18:18:30.736: usb_device_1d6b_2_musb_hdrc property usb_device.vbus = 1 (0x1)
18:18:30.752: platform_cam_focus property button.state.value = false
18:18:30.761: platform_cam_focus condition ButtonPressed = activity
18:18:31.201: usb_device_1d6b_2_musb_hdrc property button.state.value = true
18:18:31.219: usb_device_1d6b_2_musb_hdrc property usb_device.cable_type = 'Mini-B'
18:18:31.279: usb_device_1d6b_2_musb_hdrc property usb_device.mode = 'b_peripheral'
18:18:31.367: usb_device_1d6b_2_musb_hdrc condition ButtonPressed = usb.cable
18:18:31.394: bme property maemo.charger.connection_status = 'connected'
18:18:31.427: bme property maemo.charger.type = 'unknown'
18:18:31.504: bme property maemo.rechargeable.positive_rate = true
18:18:31.560: bme property battery.rechargeable.is_discharging = false
18:18:31.616: bme property battery.rechargeable.is_charging = true
18:18:31.623: bme property maemo.rechargeable.charging_status = 'on'
18:18:31.683: bme property maemo.charger.type = 'host 100 mA'
18:18:32.039: bme property maemo.charger.type = 'host 500 mA'
18:18:36.334: volume_uuid_4ACD_9F4D property volume.mount_point = ''
18:18:36.359: volume_uuid_4ACD_9F4D property volume.is_mounted = false
18:18:42.316: bme property battery.voltage.current = 3879 (0xf27)
18:18:47.334: platform_slide property button.state.value = true
18:18:47.353: platform_slide condition ButtonPressed = cover
18:18:50.788: platform_kb_lock property button.state.value = true
18:18:50.798: platform_kb_lock condition ButtonPressed = cover
18:18:51.067: platform_kb_lock property button.state.value = false
18:18:51.075: platform_kb_lock condition ButtonPressed = cover
18:19:42.307: bme property battery.voltage.current = 3914 (0xf4a)
18:21:00.038: platform_kb_lock property button.state.value = true
18:21:00.047: platform_kb_lock condition ButtonPressed = cover
18:21:00.207: platform_kb_lock property button.state.value = false
18:21:00.215: platform_kb_lock condition ButtonPressed = cover
18:21:00.368: bme property battery.voltage.current = 3920 (0xf50)
So my question are:
Can someone suggest some other tests I could do to track down this problem?
Does anyone knows how to fix this issue?

Meanwhile I'm thinking to reflash back to 1.2 (not shure if it will help)
 

The Following User Says Thank You to artishox For This Useful Post:
Posts: 5,795 | Thanked: 3,151 times | Joined on Feb 2007 @ Agoura Hills Calif
#2
Going back to 1.2 will probably fix it, for the same reason that if you have a squeaky door, you can get rid of it by burning down your house.

Complete reflashing might also fix it.
__________________
All I want is 40 acres, a mule, and Xterm.
 
Posts: 20 | Thanked: 2 times | Joined on Jun 2010
#3
Same problem, was thinking of sending the phone back as I recently got it back from the USB port coming off.
 
Posts: 32 | Thanked: 17 times | Joined on Oct 2010
#4
Does anyone knows some app that would create log what processes are up and how long they stay up and what was average cpu usage?
 
cjp's Avatar
Posts: 762 | Thanked: 395 times | Joined on Jan 2010 @ Helsinki
#5
And to make sure: we do know that the wall charger simply isn't broken?
__________________
--
Find me on Twitter: @creip

Please read my blog: "PeakMobility", which deals with MeeGo/Maemo, Windows Phone and mobile technology in general from a hedonistic user point-of-view: http://peakmob.blogspot.com/
 
Posts: 8 | Thanked: 5 times | Joined on Dec 2010
#6
From the picture you can easily tell that the cpu was constantly busy doing something. Best tools to diagnose what's going on under the hood is top/htop and powertop.

In perfect conditions using powertop you should see that most of the time (ie: 95%) cpu is doing "nothing" in C4. If this number is lower this app should tell what process is most often waking up cpu.

Also I'd check if all unneeded radio's are off (gps, bluetooth, wifi etc..), and maybe reboot the device. Last time I was using GPS and ovi-maps I noticed that after ovi-maps switched on GPS it did not shut it down on exit. Also after closing maps were still running in the background... Reboot helped.

For wall charger issue as cjp said - first I'd check if charger is not broken. Then try to reflash to 1.3, then to 1.2 and finally ask for nokia service.
 

The Following User Says Thank You to kudlatygosc For This Useful Post:
Posts: 32 | Thanked: 17 times | Joined on Oct 2010
#7
Originally Posted by cjp View Post
And to make sure: we do know that the wall charger simply isn't broken?
As far as I can tell - it works fine. It outputs ~6V and ~500mA with no load.
 
Posts: 32 | Thanked: 17 times | Joined on Oct 2010
#8
I reflashed to 1.3 and everything was great (5 days battery life) up till yesterday. I installed flashlight-extra after that cpu went up to 20% all the time so I uninstalled flashlight-extra but nothing changed. I used powertop to see whats wrong - but I cannot figure out what to make out of it.

So could anyone tell where is the problem:
BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso30+0m5) built-in shell (ash)
Enter 'help' for a list of built-in commands.

~ $ powertop
Powertop 1.13.3
sh: status: not found
Sleeping for 11 seconds before sampling
Collecting data for 30 seconds
Sample interval was 00m 30s 9918us

C# | Ratio | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
C0 | 8.9% | | 600 MHz | 84.8% |
C1 | 0.4% | 2.6ms | 550 MHz | 0.0% |
C2 | 2.3% | 6.0ms | 500 MHz | 4.0% |
C3 | 44.0% | 287.3ms | 250 MHz | 11.2% |
C4 | 44.4% | 605.5ms |

IRQ# | Activity | Type | Name
--------+------------+----------------+---------------------------
37 | 487 | INTC | gp
11 | 157 | INTC | prcm
56 | 155 | INTC | i2c_omap
57 | 37 | INTC | i2c_omap
86 | 26 | INTC | mmc1
12 | 22 | INTC | DMA
21 | 2 | INTC | SGX
225 | 1 | GPIO | omap2-onenand
Segmentation fault
~ $
 
Reply


 
Forum Jump


All times are GMT. The time now is 22:08.