Reply
Thread Tools
Posts: 1,417 | Thanked: 2,619 times | Joined on Jan 2011 @ Touring
#691
My issue is that even with brand new Scud batteries arrived today I still loose about 15% an hour with or without all radios (gsm, wifi, bluetooth, gps, FM tx) turned off and running in standby mode.
Is there a particular daemon or app that really slurps power?
I think xorg may be what is pushing the CPU to 500mhz several times a minute but that is while conky is running.
I had thought it was toasted batteries causing my 5-6 hour battery life but even with bluetooth and GSM running all day seem to have little effect on shortening my battery life. Big transfers on HEN or running webos games can drain the battery in about an hour.
I have all maemo repos active and up to date and CSSU installed.

One thing strange beside the power drain, the right side of my keyboard is lit like when in R&D mode but not the left from the time I insert the battery and even when the N900 is slid closed.

Last edited by biketool; 2012-03-14 at 06:15.
 
Posts: 2 | Thanked: 0 times | Joined on Mar 2012
#692
Hi, I have some useful info that helps increase N900 battery life more than twice

As is the case with many users, the USB port came out along with charger cable on one fine day. And, the Nokia care center in India is asking for Rs 9000/- to fix it where as a new phone is available at 14000/- as on today.

To continue using this phone, I have got 2 additional original batteries and an external charger (China made) available @ just Rs 100/-. The idea is to carry additional battery along with me and replace it as and when the battery gets discharged completely.

You know what. Shocking me, with the battery that is charged externally, it is lasting for more than 50 hours without any difference in my usage. Earlier it used to last a maximum of 24 hours (where I tend to use the phone sparingly to ensure that it lasts until I reach home).

I am not sure about where am I getting this additional charge from. The batteries are same and the usage is a bit aggressive now (as I am now holding a spare battery ). Those people who are struggling with battery life can give it a try.
 
knuthf's Avatar
Posts: 74 | Thanked: 42 times | Joined on Apr 2011 @ Oslo - around
#693
The external charger may charge the China-made battery mre than 1300mA - the N900 stops charging here.
 
knuthf's Avatar
Posts: 74 | Thanked: 42 times | Joined on Apr 2011 @ Oslo - around
#694
Originally Posted by IzzehO View Post
So is there any conclusion to this thread as to what can cause random massive increases in battery drain?

A week ago I was easily getting 10 hours with VoIP and other things connected. Now I'm suddenly getting 3 hours and it dies. BatteryGraph (and conky) never record more than 5% CPU usage (xorg does occasionally jump to 10-15%) and it happens on 3G and wireless. Any battery grapher that tracks network usage? I'm skeptical its my network that is draining the power. I'll trial by running in offline mode once I charge up the battery (its at 0% after coming off a full night charge 4 hours ago).
1. The battery is like a capacitor, a small dent, impurity can get it to discharge very quickly - seconds.
2. There are performance issues I can see related to some "widgets" that makes the device consume an enormous amount of power. One frequent "sinner" is the media player. It seems like the widgets do not receive events and spin around waiting for things to happen. I also see that some make comments that power consumption have raised with PR1.2. - which I relate to the Hildon desktop and events not being done correctly. The file system is used to signal events, so re-flashing may help.
 
Posts: 863 | Thanked: 213 times | Joined on Feb 2012 @ Goa
#695
any new tweaks for increasing battery life? my batt shows 1245 mah and it just shows that it can last for 6 hours. is that normal?
 
Posts: 9 | Thanked: 0 times | Joined on May 2014
#696
I got a question about the power consumption because I managed to reflash the phone 3 times ^^

1. First time I flashed both:
RX-51_2009SE_21.2011.38-1_PR_COMBINED_MR0_ARM.bin
RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM.bin
to achieve condition as from the box. Then after a few days I realized that the power consumption was big enough: about 20% discharge over the nigt.

2. after some reserch of forums I decided to install CSSU testing, so after that the consumption of battery power normalised and the phone was able to work few days with normal usage.

The next thing was to install usbmode, but it requires kernel power. I don't know why, but kernel power v52 does not wanted to install on top of CSSU.

3.Therefore I re-flashed my phone again, installed kp52 and then CSSU. Straight after installed usbmode. Day later I noticed that power consumption became higher again..

Log from powertop with wifi/bluetooth OFF, 2G network ON :
Code:
~ $ root 

BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso31+0cssu0) built-in shell (ash) 
Enter 'help' for a list of built-in commands. 

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

C# | Ratio | Avg/dura | Frequency | Ratio 
--------+--------+----------+-----------+--------+ 
C0 | 14.2% | | 1150 MHz | nan% | 
C1 | 0.5% | 2.5ms | 
C2 | 52.7% | 14.3ms | 
C3 | 13.4% | 103.1ms | 
C4 | 19.2% | 821.0ms | 

IRQ# | Activity | Type | Name 
--------+------------+----------------+--------------------------- 
37 | 1100 | INTC | gp 
61 | 974 | INTC | i2c_omap 
11 | 634 | INTC | prcm 
56 | 437 | INTC | i2c_omap 
57 | 270 | INTC | i2c_omap 
86 | 85 | INTC | mmc1 
21 | 52 | INTC | SGX 
12 | 23 | INTC | DMA 
25 | 1 | INTC | OMAP 

PID# | Activity | Name | Function Entry (Expire) 
--------+------------+----------------+--------------------------- 
0 | 878 | <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer) 
782 | 141 | mce | schedule_hrtimeout_range (hrtimer_wakeup) 
38 | 81D| awk | cpufreq_governor_dbs (delayed_work_timer_fn) 
0 | 24 | <kernel core> | hrtimer_start (tick_sched_timer) 
15231 | 19 | osso-xterm | schedule_hrtimeout_range (hrtimer_wakeup) 
679 | 18 | dsme | __enqueue_rt_entity (sched_rt_period_timer) 
590 | 8 | mmcqd | queue_delayed_work (delayed_work_timer_fn) 
709 | 6 | bme_RX-51 | sys_timer_settime (posix_timer_fn) 
847 | 5 | Xorg | hrtimer_start (it_real_fn) 
847 | 5 | Xorg | queue_delayed_work (delayed_work_timer_fn) 
590 | 5 | mmcqd | schedule_timeout (process_timeout) 
782 | 4 | mce | tsc2005_start_scan (tsc2005_esd_timer_handler) 
1190 | 3 | location-proxy | queue_delayed_work (delayed_work_timer_fn) 
679 | 3 | dsme | do_nanosleep (hrtimer_wakeup) 
1 | 3D| <kernel core> | queue_delayed_work (delayed_work_timer_fn) 
782 | 3 | mce | queue_delayed_work (delayed_work_timer_fn) 
809 | 2 | sgx_perf | queue_delayed_work (delayed_work_timer_fn) 
29675 | 2D|<kernel module> | queue_delayed_work (delayed_work_timer_fn) 
709 | 2 | bme_RX-51 | sys_timer_settime (posix_timer_fn) 
709 | 2 | bme_RX-51 | do_nanosleep (hrtimer_wakeup) 
709 | 2 | bme_RX-51 | schedule_timeout (process_timeout) 
1106 | 2 |hildon-status-m | schedule_hrtimeout_range (hrtimer_wakeup) 
18455 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 
6223 | 1 | apt-worker | addrconf_verify (addrconf_verify) 
18481 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 
1113 | 1 | hildon-home | schedule_hrtimeout_range (hrtimer_wakeup) 
18507 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 
18533 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 
758 | 1 | hald | schedule_hrtimeout_range (hrtimer_wakeup) 
18559 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 
18585 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 
1 | 1 | <kernel core> | inet_initpeers (peer_check_expire) 
18611 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 
18637 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 
590 | 1 | mmcqd | schedule_timeout (process_timeout) 
18663 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 
18689 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 
590 | 1 | mmcqd | cfq_completed_request (cfq_idle_slice_timer) 
1115 | 1 | hildon-desktop | queue_delayed_work (delayed_work_timer_fn) 
23608 | 1 | browserd | futex_wait (hrtimer_wakeup) 
782 | 1 | mce | schedule_timeout (process_timeout) 
18715 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 
18759 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 
1082 | 1 | iphbd | schedule_hrtimeout_range (hrtimer_wakeup) 
30 | 1 | mount | setup_wb_timer (wb_timer_fn) 
18785 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 
18321 | 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: 96%|RET: 0%|INA: 0%| ON: 3%| now:(OFF) 
per |OFF: 32%|RET: 52%|INA: 0%| ON: 15%| now:(ON) 
dss |OFF: 23%|RET: 0%|INA: 0%| ON: 76%| now:(OFF) 
cam |OFF: 100%|RET: 0%|INA: 0%| ON: 0%| now:(OFF) 
core |OFF: 14%|RET: 4%|INA: 62%| ON: 19%| now:(ON) 
neon |OFF: 19%|RET: 13%|INA: 52%| ON: 15%| now:(ON) 
mpu |OFF: 19%|RET: 13%|INA: 52%| ON: 15%| 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 
| WDT1 | SR1 | SR2 
| 
ckgen | CORE | PERI | 96M 
| 48M | 12M | 54M 
| EMU_CORE | 
per | GPIO2 | GPIO3 | GPIO4 
| GPIO5 | GPIO6 | 

Total wakeups 4819, 160.6/s | IRQ 3576, 119.2/s | Timers 1243, 41.4/s 
HW wakeups 122, 4.1/s | Real gp_timers expired 76, 2.5/s 
Nokia-N900:~#
I made logs when the phone was in Offline mode i.e. all radios turned OFF
Over the night in offline mode battery drained by 10%
log from powertop :
Code:
BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso31+0cssu0) built-in shell (ash) 
Enter 'help' for a list of built-in commands. 

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

C# | Ratio | Avg/dura | Frequency | Ratio 
--------+--------+----------+-----------+--------+ 
C0 | 19.5% |            | 1150 MHz | nan% |
C1 | 0.0% | 0.1ms | 
C2 | 3.5% | 7.2ms | 
C3 | 10.0% | 130.1ms | 
C4 | 67.0% | 958.8ms | 

IRQ# | Activity | Type | Name 
--------+------------+----------------+--------------------------- 
37 | 882 | INTC | gp 
56 | 276 | INTC | i2c_omap 
11 | 135 | INTC | prcm 
86 | 34 | INTC | mmc1 
57 | 22 | INTC | i2c_omap 
21 | 9 | INTC | SGX 
12 | 4 | INTC | DMA 

PID# | Activity | Name | Function Entry (Expire) 
--------+------------+----------------+--------------------------- 
0 | 806 | <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer) 
38 | 46D| awk | cpufreq_governor_dbs (delayed_work_timer_fn) 
679 | 21 | dsme | __enqueue_rt_entity (sched_rt_period_timer) 
10407 | 19 | osso-xterm | schedule_hrtimeout_range (hrtimer_wakeup) 
0 | 17 | <kernel core> | hrtimer_start (tick_sched_timer) 
590 | 6 | mmcqd | schedule_timeout (process_timeout) 
590 | 4 | mmcqd | queue_delayed_work (delayed_work_timer_fn) 
709 | 4 | bme_RX-51 | sys_timer_settime (posix_timer_fn) 
809 | 3 | sgx_perf | queue_delayed_work (delayed_work_timer_fn) 
679 | 3 | dsme | do_nanosleep (hrtimer_wakeup) 
1 | 3 | <kernel core> | queue_delayed_work (delayed_work_timer_fn) 
18785 | 3 | sh | queue_delayed_work (delayed_work_timer_fn) 
27 | 2 | kondemand/0 | queue_delayed_work (delayed_work_timer_fn) 
709 | 2 | bme_RX-51 | sys_timer_settime (posix_timer_fn) 
709 | 2 | bme_RX-51 | do_nanosleep (hrtimer_wakeup) 
709 | 2 | bme_RX-51 | schedule_timeout (process_timeout) 
29675 | 2D|<kernel module> | queue_delayed_work (delayed_work_timer_fn) 
23608 | 2 | browserd | futex_wait (hrtimer_wakeup) 
847 | 1 | Xorg | hrtimer_start (it_real_fn) 
1106 | 1 |hildon-status-m | schedule_hrtimeout_range (hrtimer_wakeup) 
10855 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 
847 | 1 | Xorg | queue_delayed_work (delayed_work_timer_fn) 
30 | 1 | mount | setup_wb_timer (wb_timer_fn) 
13 | 1 | pdflush | blk_plug_device (blk_unplug_timeout) 
590 | 1 | mmcqd | schedule_timeout (process_timeout) 
10883 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 
10909 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 
10935 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 
10961 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 
10987 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 
11013 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 
758 | 1 | hald | schedule_hrtimeout_range (hrtimer_wakeup) 
11039 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 
11065 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 
782 | 1 | mce | schedule_hrtimeout_range (hrtimer_wakeup) 
11091 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 
11119 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 
11145 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 
11171 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 
10542 | 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: 76%|RET: 3%|INA: 0%| ON: 19%| 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: 66%|RET: 8%|INA: 1%| ON: 22%| now:(ON) 
neon |OFF: 66%|RET: 9%|INA: 3%| ON: 19%| now:(ON) 
mpu |OFF: 66%|RET: 9%|INA: 3%| ON: 19%| 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 
| WDT1 | SR1 | SR2 
| 
ckgen | CORE | PERI | 96M 
| 48M | 12M | 54M 
| EMU_CORE | 
per | GPIO2 | GPIO3 | GPIO4 
| GPIO5 | GPIO6 | 

Total wakeups 2331, 77.7/s | IRQ 1362, 45.4/s | Timers 969, 32.3/s 
HW wakeups 135, 4.5/s | Real gp_timers expired 114, 3.8/s 
Nokia-N900:~#
And yes, I did all tests with closed keyboard and blank screen.
Now I am not sure, whether usbmode or kernel power itself eats the battery.
what about 1150 MHz frequency? is it kp52 settings or just lag?

If you need any additional info from conky, or Htop I will give it, but I dont know how to make log from these programs.)
 
Posts: 1,378 | Thanked: 1,604 times | Joined on Jun 2010 @ Göteborg, Sweden
#697
Originally Posted by evropean View Post
what about 1150 MHz frequency? is it kp52 settings or just lag?
That is not right but is a bug with powertop and kp52. You can try another version of powertop, called zzztop that will provide the correct info but lacks some of the detail (very nice output tho').

You are spending way too much time in state C2. There is high IRQ activity. This and following posts look at a very similar situation.

I wonder about this as a solution?

Last edited by handaxe; 2014-05-18 at 15:07.
 
Posts: 9 | Thanked: 0 times | Joined on May 2014
#698
Yes, I thought it myself as well. But if I just uninstall kernel power, I will not be able to use nor usb host mode or aircrack-ng? what will be the solution then?

Last edited by evropean; 2014-05-18 at 15:41.
 
Posts: 1,378 | Thanked: 1,604 times | Joined on Jun 2010 @ Göteborg, Sweden
#699
Are you sure about the requirements? Kernel-cssu is to some extent kernel-power (- overclocking???) see the debian control file here.

That appears to provide the kernel modules for usbmode.
 
Alecsandru's Avatar
Posts: 439 | Thanked: 282 times | Joined on Oct 2012
#700
Log from powertop with wifi/bluetooth OFF, 2G network ON with kp53
code :
~ $ root


BusyBox v1.22.1 (Debian 1.22.1power1+thumb0) built-in shell (ash)
Enter 'help' for a list of built-in commands.

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

C# | Ratio | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
C0 | 3.1% | | 1150 MHz | nan% |
C1 | 0.4% | 1.0ms |
C2 | 2.0% | 2.8ms |
C3 | 14.6% | 125.1ms |
C4 | 79.8% | 826.2ms |

IRQ# | Activity | Type | Name
--------+------------+----------------+---------------------------
56 | 570 | INTC | i2c_omap
57 | 475 | INTC | i2c_omap
11 | 216 | INTC | prcm
37 | 171 | INTC | gp
86 | 88 | INTC | mmc1
12 | 49 | INTC | DMA
67 | 17 | INTC | ssi_p1_mpu_irq0
71 | 11 | INTC | ssi_gdd
225 | 8 | GPIO | omap2-onenand
311 | 4 | GPIO | ssi_p1_cawake_gpio
21 | 2 | INTC | SGX

PID# | Activity | Name | Function Entry (Expire)
--------+------------+----------------+---------------------------
0 | 128 | <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
38 | 28D| awk | cpufreq_governor_dbs (delayed_work_timer_fn)
0 | 18 | <kernel core> | hrtimer_start (tick_sched_timer)
633 | 10 | mmcqd | queue_delayed_work (delayed_work_timer_fn)
736 | 5 | dsme | __enqueue_rt_entity (sched_rt_period_timer)
7846 | 3 | osso-xterm | schedule_hrtimeout_range (hrtimer_wakeup)
788 | 3 |<kernel module> | queue_delayed_work (delayed_work_timer_fn)
30 | 3 | mount | setup_wb_timer (wb_timer_fn)
736 | 3 | dsme | do_nanosleep (hrtimer_wakeup)
1 | 3D| <kernel core> | queue_delayed_work (delayed_work_timer_fn)
772 | 2D|<kernel module> | queue_delayed_work (delayed_work_timer_fn)
89 | 2 | cifsdnotifyd | schedule_timeout (process_timeout)
1774 | 2 | icd2 | schedule_hrtimeout_range (hrtimer_wakeup)
7395 | 2 | browserd | futex_wait (hrtimer_wakeup)
1514 | 1 | hildon-home | schedule_hrtimeout_range (hrtimer_wakeup)
842 | 1 | hald | schedule_hrtimeout_range (hrtimer_wakeup)
1 | 1 | <kernel core> | inet_initpeers (peer_check_expire)
998 | 1 | hald-addon-bme | schedule_hrtimeout_range (hrtimer_wakeup)
1617 | 1 | BatteryGraphd | schedule_timeout (process_timeout)
775 | 1 | dbus-daemon | schedule_hrtimeout_range (hrtimer_wakeup)
1617 | 1 | BatteryGraphd | jbd2_journal_get_write_access (commit_timeout)
0 | 1 | <kernel core> | queue_delayed_work (delayed_work_timer_fn)
1617 | 1 | BatteryGraphd | ubifs_wbuf_write_nolock (wbuf_timer_callback_nolock)
14 | 1 | pdflush | blk_plug_device (blk_unplug_timeout)
863 | 1 | mce | schedule_hrtimeout_range (hrtimer_wakeup)
88 | 1 | cifsoplockd | schedule_timeout (process_timeout)
7861 | 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%| nowOFF)
sgx |OFF: 99%|RET: 0%|INA: 0%| ON: 0%| nowOFF)
per |OFF: 93%|RET: 2%|INA: 0%| ON: 3%| nowON)
dss |OFF: 100%|RET: 0%|INA: 0%| ON: 0%| nowOFF)
cam |OFF: 100%|RET: 0%|INA: 0%| ON: 0%| nowOFF)
core |OFF: 79%|RET: 13%|INA: 0%| ON: 6%| nowON)
neon |OFF: 79%|RET: 14%|INA: 1%| ON: 3%| nowON)
mpu |OFF: 79%|RET: 14%|INA: 1%| ON: 3%| nowON)
iva2 |OFF: 100%|RET: 0%|INA: 0%| ON: 0%| nowOFF)

Clock activity breakdown at end of period
Domain | Active clocks
--------+---------------+---------------+------------------
core | SDRC | HSOTGUSB_IDLE | OMAPCTRL
| MAILBOXES |
wkup | GPT1 | 32KSYNC | GPIO1
| WDT1 | SR2 |
ckgen | CORE | PERI | 96M
| 48M | 12M | 54M
| EMU_CORE |
per | GPIO2 | GPIO3 | GPIO4
| GPIO5 | GPIO6 |

Total wakeups 1836, 61.2/s | IRQ 1611, 53.7/s | Timers 225, 7.5/s
HW wakeups 216, 7.2/s | Real gp_timers expired 171, 5.7/s
__________________
N900 Beast featuring :
8GB OPTFS@ext4(*performance mount options)
overclock: cpu[125 - 1,150(*VDD1)+Dsp overclock
CSSU-T latest version
 

The Following User Says Thank You to Alecsandru For This Useful Post:
Reply

Tags
n900 battery, n900 v. power war, piss poor

Thread Tools

 
Forum Jump


All times are GMT. The time now is 13:11.