|
2010-06-09
, 06:55
|
Posts: 23 |
Thanked: 3 times |
Joined on Jun 2010
@ Switzerland
|
#22
|
The Following User Says Thank You to skccs32 For This Useful Post: | ||
|
2010-06-09
, 08:21
|
Posts: 385 |
Thanked: 426 times |
Joined on Dec 2009
@ Gothenburg, Sweden
|
#23
|
Eating a full battery within 1-2 hours... that's highly unusual.
May I ask what usage your device is put through during that time?
Also, widgets usually eat away at battery life and combined with constant web browsing, can shorten it drastically.
I'm not an expert within this area, so I'll leave that for the more experienced that may (hopefully) pass by later today, but I'm sure it's not a problem that can't be fixed.
I'm currently on a N900 as well, and my battery life, even with 3G running is generally a little less than a day with moderate web browsing and calling/texting. With no or little internet connection but moderate calling/texting, I get up to two days.
Best of luck to you though Christian, and make sure you keep checking back!
|
2010-06-09
, 18:01
|
Posts: 23 |
Thanked: 3 times |
Joined on Jun 2010
@ Switzerland
|
#24
|
Hi Andrew, I am starting to suspect that one thing that perhaps could be a huge battery eater is the 3g connection. I'm not sure if this is related to PR1.2 at all (probably not), but at my workplace I notice that the 3g signal is kind of weak and battery drain goes quick during working hours but slows down to a minimum when I'm elsewhere, so I suspect that the device increase the signal strength and of course eat more battery. The question is whether the radio module/software has some glitches or is in the need for optimization. Maybe I need some more info about other phones and with the same mobile network in the area to see if the N900 stands out with the signal strength.
1-2 hours though sound a little bit too much to me. I get like 7-8 hours to reach like 15-20% of battery left at the office place (but that's a little bit high too if you ask me).
The Following User Says Thank You to skccs32 For This Useful Post: | ||
|
2010-06-09
, 23:50
|
Posts: 2 |
Thanked: 0 times |
Joined on Feb 2010
|
#25
|
|
2010-06-10
, 00:21
|
Posts: 172 |
Thanked: 170 times |
Joined on Jan 2010
@ Sweden
|
#26
|
|
2010-06-10
, 00:38
|
Posts: 150 |
Thanked: 80 times |
Joined on Dec 2009
|
#27
|
|
2010-06-10
, 02:10
|
|
Posts: 355 |
Thanked: 245 times |
Joined on Jul 2009
@ Northern VA
|
#28
|
Speaking of widgets that eat battery life. FMtransmitter and personal countdown can be major hogs. FMtransmitter seems to poll the state of the device to see if fm is on and update the icon. It does this often and I have gotten much better life after removing it.
Personal countdown - its important to change the update period so something realistic.
I can also agree with the emmc flashing option. Originally for 1.2 I didnt flash everything - just the fiasco - had major issues. Since flashing emmc as well as fiasco - much improved.
|
2010-06-10
, 06:19
|
Posts: 2,829 |
Thanked: 1,459 times |
Joined on Dec 2009
@ Finland
|
#29
|
|
2010-06-10
, 07:56
|
Posts: 23 |
Thanked: 3 times |
Joined on Jun 2010
@ Switzerland
|
#30
|
I recently did an OTA update to PR1.2 and got similar battery problems (dead in 2-3 hours). In my case, Conky showed me that the CPU clock-rate never goes below 500MHz (even when only at 5%-10% CPU load). I don't have the overclocking kernel installed, so that is not the root of the problem. But, as others have suggested, the easiest way to solve a problem like this is simply to reflash:
1) Run the backup-app and do an internal backup in N900
2) Plug your N900 into a computer and copy all files to your PC (the reflash will delete EVERYTHING, including photos, music, etc)
3) Reflash everything, both standard flash and eMMC flash. Howto at:
http://wiki.maemo.org/Updating_the_tablet_firmware
4) Copy all your files back to your N900 (make sure you place the backup directory where it was before)
5) Run the backup-app again to restore everything.
if i did help you, just click "Thanks" on the lower right of my post. thanks!
"The best way to break a Spell is to prevent it from being cast in the first place"
N900: 1000/1150mhz; sampling_rate 15; up_threshold 150000;