Bug 12723 - status-area-applet-battery ignores gconf key /apps/osso/status-area-applet-battery/use_design_capacity
: status-area-applet-battery ignores gconf key /apps/osso/status-area-applet-ba...
Status: NEW
Product: Maemo 5 Community SSU
general
: testing
: N900 Maemo
: Unspecified major with 3 votes (vote)
: ---
Assigned To: Pali Rohár
: general
:
:
:
:
  Show dependency tree
 
Reported: 2014-01-16 19:27 UTC by Piotr Jawidzyk
Modified: 2014-07-03 15:28 UTC (History)
1 user (show)

See Also:


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description Piotr Jawidzyk (reporter) maemo.org 2014-01-16 19:27:51 UTC
SOFTWARE VERSION: 
21.2011.38-1Tmaemo9.1+thumb0

status-area-applet-battery=1.0-8

EXACT STEPS LEADING TO PROBLEM: 
1. set gconf key:

/apps/osso/status-area-applet-battery/use_design_capacity

...to 0 (int)

2. reboot device
3. Open hildon-status-menu 
4. look at battery status readings

EXPECTED OUTCOME:
Actual and maximum capacity should be real ones, took from calibrated
bq27x00_battery module sysfs entries.

ACTUAL OUTCOME: 
Actual capacity is properly read from bq27x00_battery, but maximum capacity is
still rx51_battery's "design capacity". This result in sums that doesn't add
up, and often, are total absurd - like, 3200 mAh available, out of 1236 mAh.

REPRODUCIBILITY: 
always

EXTRA SOFTWARE INSTALLED: 
kernel-power=1:2.6.28-10power52
bme-rx-51=1.0-1

...and all dependencies of the above.

OTHER COMMENTS:
bq27200 is calibrated, less than 32 cycles ago (thus no calibration required
flag set by any means.
Comment 1 Piotr Jawidzyk (reporter) maemo.org 2014-05-16 09:14:18 UTC
The bug is still present as for version 1.0-9
Comment 2 Piotr Jawidzyk (reporter) maemo.org 2014-07-03 15:28:13 UTC
Just FYI, this bug is still present using all latest BME Replacement bits from
new BME repository:
http://maemo.merlin1991.at/cssu/bme-replacement/

...and status-area-applet-battery from CSSU Testing (1.0-8) OR Devel _1.0-9).
It manifest itself with or without calibrated chip, on both regular batteries
and increased capacity ones.

I see that this bug is still unassigned - is this an overlook, or no one is
able to work on it ATM?