Estel: interesing find that bme charges at 1050. I never saw it use anything except 950, but I investigated it during PR1.2 times or earlier.

btw, I expect charge.sh/charge21.sh and bq27200.sh would not work if the power kernel battery module is loaded, as they try access the same hardware and conflict.

Equally, trying to restart bme with power kernel battery module loaded would fail. Both bme and charge*sh access charger chip intermittently and, depending on chance, might actually run both at the same time, but it would be messy to have two things trying to run the charger at the same time.

Quick test of my dual scud (alone) showed 2859mAh

This was a quick test, but is good enough, not going to get more then 50mAh more MAX, so in spite of this in 4 mounts my battery has lost minimum 135mAh.

It now is between 2859 - 2909mAh

Actually, I checked it now with stock Nokia wall charger, and, indeed, it uses 950 mA. Ho ever, when I use 2A 5V charger (from Virtual USB adapter, modified a little to contain USB charging port with crossed D+/D-), it uses 1050 mA for me. Using even more powerful power source (ATX power supply @ 5V) doesn't result in further increase of current, obviously.

Strange, cause all of the time I was using it with bq27x00 module loaded (i know, shame on me...), and bq27200.sh works without even smallest flaws both in normal and loop mode. It works even with module + script + bme charging combination.

Also, some time ago - when i didn't know about possible conflict - I was notoriously testing charging via charger.sh without disabling bme, and never noticed any side effects. I mean, without looking into terminal, it was just like bme is charging - You know, battery indicator going all way to up in loop, and communicates about charging when plugged popping up...

Ho ever, charge.sh output was also correct, and when I try it now with charger21.sh I can't find any errors in log.

Also, with kernel module loaded, and even with both kernel module + bq27200.sh working in loop, stopping and starting bme works for me flawlessly, if I'm *not* around ~3200 mV

I'm sure joerg_rw got really good rationale to warn us about possible conflicts with accessing same thing by bme, but i must admin that I have yet to see any bad effect of that, or anyone claimed problems with bq27x00 kernel module. And then, confirm that it is really it - except for inaccurate reading due to wrong calibration. AFAIK, every report about conflict (in kp thread) concluded in discovering different source of problems.

So I'm start to assuming - with all due care and respect to fact, that I may be totally wrong - that there is something, about how it does work, that we don't know about, despite high amount of research done already.

// Edit

Of course my problem with charge*.sh not charging, when started under 3248 mV and bme *disabled* still persist, which make it even more strange.

Hope you guys get the capacity measuring working, cool feature to have in the N900, not that i have not given enough "data" to give users a good choice on next battery

I also think that by now we can conclude the battery testing phase, not seeing any battery's stepping up to take the throne of the mighty blue scud

Also im saving up for battery upgrade and further R&D / Building and Testing of my homemade EV-Motor, if i can find a few funds im going to order more mugen covers so i have a stock if any maemo users needs them.

Also thanks goes out to you guys that send battery testing requests, without that i would probably never had found the scud battery.

Good luck! As for testing battery capacity in N900, it's working already Things we discussed here in few last post were on slightly different matter.

just made an order for the scud batteries...

*impatiently waiting

I also ordered the Scud batteries, and they arrived quickly and well packaged!

Thank you very much for the recommendations, kind battery testing people




However...

I would very much like to take this offer up!

I cannot PM though - I assume I need a minimum post count that I haven't reached yet? It doesn't specifically say on the User Guide page!
http://talk.maemo.org/faq.php?faq=vb...ivate_messages

Thanks in advance

Thanks Estel, I followed your tutorial since yesterday. I charged using the scripts you linked to reach the maximum charge level. With a single Scud battery, after discharging, its results:

Last Measured Discharge: 1585 mAh

BTW the readings prior to calibrating showed LMD over 1700 mAh and more than 30 cycles. But I've tried several different batteries and who knows how wrong it gets on its own?

@MaemoNoob

I've send PM to You, hope You'll not encounter any problems in responding... Yea, PM feature limit can be quite confusing, few days ago I was unable to PM Rebhana, where we both got dozens of messages and "Thanks" 0_o

@stlpaul

I'm glad it was useful for someone As for Your results, it seems little too high, if You haven't got a unique, ultra capacity one I would do another calibrating cycle, just to be sure - chip is much more careful, when doing from higher capacity to lower one, and it may require 2-3 cycles. Of course, You don't need to do it right now, if You don't want - doing in month or so will result in same result + compensate for a micro capacity loss in 1 month.

Maybe it is, the battery is so fat it wouldn't fit in my charger without sawing the sides of the charger off. :P

But I definitely plan to calibrate again when it gets low tomorrow, because it started with an impossibly high 1700+. I already recharged so now it's just the waiting game.