Sounds like a great idea....

However, one thing to consider is whether it's feasible to ship 'homemade battery setups' overseas given the world we live in now...

I bring this up as some time ago, another person on these forums offered up a dual battery he put together. I bought it and had him ship it to me here in USA from his country overseas. Long story short, after waiting about 2 months or so for package to arrive in the mail, it never did, and I had to request a refund, which I got. But was unfortunate situation all the way around.

Maybe it was just a fluke that package got lost or maybe as I suspect, customs people decided to intercept package thinking it was some other type of object, that gets people nervous about these days....

Hope you get what I'm trying to say...

Don't know if it would have been better to ship package via DHL or FedEx, etc...instead of relying on mail system.....

Anyway, just thought I'd mention it....

Ok PM me if you want it in the first posts.


Always considered that and also other battery's like the 18650's

Have you manage to source any good quality and fairly cheap 18650s yet?

Not really no, lately everything has just been a blur, so much going on + stupid holidays and such, getting hold of some proper 18650 seems to be a pain, almost everywhere you look in china you get a VERY high % of fake battery's.

Hi there!

dr_frost_dk, how can I contact you in private?

skype or gtalk, info is in my contact info
http://talk.maemo.org/member.php?u=46995

Hi to all,before one week,i bought one battery from ebay http://www.ebay.co.uk/itm/PolarCell-...item5ae5cc9046
but till to day i can't see any difference than orginal battery,although the new battery is have capacity 1500mAh.Here my output from powertop:
home/user # 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 14313us

C# | Ratio | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
C0 | 49.7% | | 1150 MHz | nan% |
C1 | 0.2% | 0.7ms |
C2 | 16.1% | 12.1ms |
C3 | 21.1% | 87.8ms |
C4 | 12.9% | 555.2ms |

IRQ# | Activity | Type | Name
--------+------------+----------------+---------------------------
12 | 7095 | INTC | DMA
37 | 2166 | INTC | gp
86 | 850 | INTC | mmc1
67 | 413 | INTC | ssi_p1_mpu_irq0
56 | 392 | INTC | i2c_omap
11 | 251 | INTC | prcm
57 | 186 | INTC | i2c_omap
71 | 163 | INTC | ssi_gdd
311 | 162 | GPIO | ssi_p1_cawake_gpio
21 | 50 | INTC | SGX
225 | 7 | GPIO | omap2-onenand
25 | 1 | INTC | OMAP

PID# | Activity | Name | Function Entry (Expire)
--------+------------+----------------+---------------------------
0 | 2001 | <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
1 | 80D| preinit | cpufreq_governor_dbs (delayed_work_timer_fn)
927 | 38 | mce | schedule_hrtimeout_range (hrtimer_wakeup)
44 | 33 | mmcqd | queue_delayed_work (delayed_work_timer_fn)
44 | 33 | mmcqd | cfq_completed_request (cfq_idle_slice_timer)
1262 | 28 | hildon-desktop | schedule_hrtimeout_range (hrtimer_wakeup)
1523 | 19 | osso-xterm | schedule_hrtimeout_range (hrtimer_wakeup)
820 | 19 | dsme | __enqueue_rt_entity (sched_rt_period_timer)
0 | 15 | <kernel core> | hrtimer_start (tick_sched_timer)
1563 | 11 | browserd | futex_wait (hrtimer_wakeup)
44 | 8 | mmcqd | schedule_timeout (process_timeout)
15 | 8 | kswapd0 | schedule_timeout (process_timeout)
856 | 7 | bme_RX-51 | sys_timer_settime (posix_timer_fn)
1576 | 7 | browser | do_nanosleep (hrtimer_wakeup)
1576 | 7 | browser | schedule_hrtimeout_range (hrtimer_wakeup)
905 | 6 | ohmd | schedule_hrtimeout_range (hrtimer_wakeup)
1567 | 6 | browserd | futex_wait (hrtimer_wakeup)
995 | 5 | Xorg | queue_delayed_work (delayed_work_timer_fn)
949 | 4 | sgx_perf | queue_delayed_work (delayed_work_timer_fn)
652 | 4 |<kernel module> | tsc2005_probe (tsc2005_esd_timer_handler)
995 | 3 | Xorg | hrtimer_start (it_real_fn)
820 | 3 | dsme | do_nanosleep (hrtimer_wakeup)
29 | 3 | mv | setup_wb_timer (wb_timer_fn)
1582 | 3 | browserd | futex_wait (hrtimer_wakeup)
15 | 3 | kswapd0 | blk_plug_device (blk_unplug_timeout)
856 | 2 | bme_RX-51 | sys_timer_settime (posix_timer_fn)
856 | 2 | bme_RX-51 | do_nanosleep (hrtimer_wakeup)
856 | 2 | bme_RX-51 | schedule_timeout (process_timeout)
1558 | 2 | browserd | journal_get_write_access (commit_timeout)
852 | 2D|<kernel module> | queue_delayed_work (delayed_work_timer_fn)
1 | 2D| <kernel core> | queue_delayed_work (delayed_work_timer_fn)
938 | 2 | gconfd-2 | ubifs_wbuf_write_nolock (wbuf_timer_callback_nolock)
1262 | 2 | hildon-desktop | queue_delayed_work (delayed_work_timer_fn)
927 | 2 | mce | queue_delayed_work (delayed_work_timer_fn)
1585 | 2 | Calendar | schedule_timeout (process_timeout)
1585 | 2 | Calendar | blk_plug_device (blk_unplug_timeout)
44 | 1 | mmcqd | schedule_timeout (process_timeout)
1540 | 1 |e-addressbook-f | blk_plug_device (blk_unplug_timeout)
1540 | 1 |e-addressbook-f | schedule_timeout (process_timeout)
1540 | 1 |e-addressbook-f | futex_wait (hrtimer_wakeup)
1545 | 1 |e-addressbook-f | futex_wait (hrtimer_wakeup)
1547 | 1 |e-addressbook-f | futex_wait (hrtimer_wakeup)
921 | 1 | csd | schedule_hrtimeout_range (hrtimer_wakeup)
1552 | 1 |e-addressbook-f | futex_wait (hrtimer_wakeup)
1551 | 1 |e-addressbook-f | futex_wait (hrtimer_wakeup)
1553 | 1 |e-addressbook-f | futex_wait (hrtimer_wakeup)
1555 | 1 |e-addressbook-f | futex_wait (hrtimer_wakeup)
1554 | 1 |e-addressbook-f | futex_wait (hrtimer_wakeup)
1556 | 1 |e-addressbook-f | futex_wait (hrtimer_wakeup)
1560 | 1 |e-addressbook-f | futex_wait (hrtimer_wakeup)
1558 | 1 | browserd | schedule_timeout (process_timeout)
938 | 1 | gconfd-2 | schedule_hrtimeout_range (hrtimer_wakeup)
927 | 1 | mce | schedule_timeout (process_timeout)
927 | 1 | mce | schedule_timeout (process_timeout)
1211 | 1 | signond | schedule_hrtimeout_range (hrtimer_wakeup)
1150 | 1 | sapwood-server | schedule_hrtimeout_range (hrtimer_wakeup)
1580 | 1 | browserd | schedule_timeout (process_timeout)
1580 | 1 | browserd | schedule_timeout (process_timeout)
1096 | 1 | dbus-daemon | schedule_timeout (process_timeout)
1579 | 1 | image-viewer | schedule_timeout (process_timeout)
1580 | 1 | browserd | journal_get_write_access (commit_timeout)
834 | 1 | dsme-server | schedule_timeout (process_timeout)
995 | 1 | Xorg | schedule_timeout (process_timeout)
1534 | 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: 95%|RET: 0%|INA: 0%| ON: 4%| nowON)
per |OFF: 33%|RET: 16%|INA: 0%| ON: 50%| nowON)
dss |OFF: 23%|RET: 0%|INA: 0%| ON: 76%| nowOFF)
cam |OFF: 100%|RET: 0%|INA: 0%| ON: 0%| nowOFF)
core |OFF: 4%|RET: 0%|INA: 39%| ON: 55%| nowON)
neon |OFF: 12%|RET: 21%|INA: 15%| ON: 50%| nowON)
mpu |OFF: 12%|RET: 21%|INA: 15%| ON: 50%| 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 | MMC2 |
core3 | USBTLL
sgx | SGX
wkup | GPT1 | 32KSYNC | GPIO1
| WDT1 |
ckgen | CORE | PERI | 96M
| 48M | 12M | 54M
| EMU_CORE |
per | GPIO2 | GPIO3 | GPIO4
| GPIO5 | GPIO6 |

Total wakeups 14140, 471.3/s | IRQ 11736, 391.2/s | Timers 2404, 80.1/s
HW wakeups 251, 8.4/s | Real gp_timers expired 118, 3.9/s
/home/user #
edit:I am with kp50,multiboot+backmenu+droid 2.3.4 and libglib2.26

@ disappear: (unless I musunderstand you) the simple benefit of a polarcell (or any battery) with a proven capacity higher than the stock Nokia one ca. 1350mAh is that you have more juice and thus longer usage.

Powertop will not show this per se, as it records the phones energy consumption due to various processes and components and best allows one to see what you might stop running or change how it runs.

What about using a watt meter and an tenergy b6+ multi chemistry charger balance charger to test the charge/discharge mah ratings? You want to be careful, but i think with a arduio pin headers, and female female pinleads to a balance port, inline with the wattmeter you could get a very accurate battery health reading. Can set discharge/charge mah ratings as well.

Might just try this on my n810's 1500mah lipo to see how it works.

is it possible to set VDQ to 0 by script (without restart/connecting - disconnecting the charger)?

I want to run it in order to always avoid recalibration of the battery power.