Active Topics
-
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 2 days, 12 hrs ago -
TLS 1.2 for N9 is ready (28)
to MeeGo / Harmattan by smartblu9 - 2 days, 13 hrs ago -
Maemo repository (3)
to Community by torsen - 3 days, 5 hrs ago -
Error after installing Leste on sdcard (11)
to Maemo 7 / Leste by Maemish - 4 days, 2 hrs ago -
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 5 days, 9 hrs ago - more...
| The Following User Says Thank You to artishox For This Useful Post: | ||
|
2010-12-22
, 17:13
|
|
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.
Complete reflashing might also fix it.
__________________
All I want is 40 acres, a mule, and Xterm.
All I want is 40 acres, a mule, and Xterm.
|
|
2010-12-22
, 17:58
|
|
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.
|
|
2010-12-23
, 11:04
|
|
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?
 |
|
2010-12-23
, 16:20
|
|
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/
--
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/
|
|
2010-12-23
, 16:42
|
|
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.
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: | ||
|
|
2010-12-24
, 07:27
|
|
Posts: 32 |
Thanked: 17 times |
Joined on Oct 2010
|
#7
|
Originally Posted by cjp
As far as I can tell - it works fine. It outputs ~6V and ~500mA with no load.
And to make sure: we do know that the wall charger simply isn't broken?
|
|
2011-01-17
, 12:34
|
|
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:
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
~ $
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:
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)