I think I know whats the problem is about. Battery icon *does* starts upgrading, but only after capacity drops below "design", and only in relation to that "design" capacity.

So, for example, if one have 1700 mAh relative capacity, and design is reported (via resistor) as 1000 mAh, battery icon will show full all the time until capacity drops below 1000 mAh, even if rest of the applet report everything (percentage, charge, capacity current and max) correctly. Then, at 500/1700 mAh, battery icon will show half the battery full (500/1000 mAh, took from design), etc.

Everything written above is unrelated to gconf entry about using design capacity - it seems that bug about using design as max capacity for calculating what icon to show is hardcoded somewhere else in the applet.

/Estel

i've noticed that "i2cget" util does not seem to work anymore. i get this error message:

"Could not set address to 0x55: Device or resource busy"

for "/usr/bin/i2cget -y 2 0x55 0x06 w" for example.

Is this related to calibration?

Use i2cget -f. It is safe for bq chips when using bq linux kernel drivers.

It is because kernel drivers bind to bq i2c chips.

pali, any progress on:
http://talk.maemo.org/showpost.php?p...0&postcount=21

...? It seems that issue is quite clearly manifested, and it's quite irritating bug, to say at least. No pressure, all understanding - just wondering, how things are looking.

/Estel

Estel, sorry but I did not have time yet... If somebody else have some free time try to hack...

I will have time to do this again and deal with any possible negative consequences in a few days, just to be sure though...
1-install(or have) up to date Kernel Power
2-add repo
3-apt-get update and upgrade
4-profit
Missing anything?

4. Be sure, that you have cssu-testing installed - or at least new battery applet and it's dependencies from cssu-testing repo.

5.
Saves lot of frustration with getting completely BS values posing as correct, when battery gauge is not calibrated (at all 0 like, lost calibration data due to battery out of device for too long and dead bupbat).

6. Reboot

7. profit

/Estel

I assume that thumb unstable will have everything I need. About CSSU=testing
I bet scrip will really help with double-scud.
edit...
Cool, it installed good this time, works. Is there a man page for the new features?

I will put the instructions to install BME replacement in the Qi how-to just need the command to enable both temporary and permanent to use unshorted data lines USB for charging.

Not sure what you mean by "temporary and permanent". This one sticks until reboot (to be precise, until module's load/unload, I think). If you want it permanent, you can put a script doing it in /etc/event.d/, but you wouldn't be able to connect to PC (or hostmode, or USB Networking, or...).

/Estel