Reply
Thread Tools
Posts: 2,153 | Thanked: 8,462 times | Joined on May 2010
#961
@toxaris:

Now I see where is problem.

First is that your battery is not calibrated. In this state applet should report "0/0" (instead some bad and uncorrect values).

Second problem is in bq27x00_battery kernel driver. It does not report capacity in % or last full capacity if CI flag is set (when battery is not calibrated). But it report current mAh also when CI flag is set which lead to total mess in status menu plugin.

How to solve first problem: (Stop bme) load drivers and discharge battery until capacity be about 7%. You can also you bq27200.sh script for monitoring EDV1/F LOW flag. After battery will be empty, charge it to full and discharge again.

Now going to fix second problem. Thanks for finding & reporting bug in kernel.
 

The Following 6 Users Say Thank You to pali For This Useful Post:
Posts: 2,153 | Thanked: 8,462 times | Joined on May 2010
#962
Second problem should be fixed in last prerelase version of kp52: http://talk.maemo.org/showpost.php?p...&postcount=261
 

The Following 6 Users Say Thank You to pali For This Useful Post:
Posts: 424 | Thanked: 196 times | Joined on Mar 2010 @ Sweden
#963
Originally Posted by pali View Post
@toxaris:

Now I see where is problem.

First is that your battery is not calibrated. In this state applet should report "0/0" (instead some bad and uncorrect values).

Second problem is in bq27x00_battery kernel driver. It does not report capacity in % or last full capacity if CI flag is set (when battery is not calibrated). But it report current mAh also when CI flag is set which lead to total mess in status menu plugin.

How to solve first problem: (Stop bme) load drivers and discharge battery until capacity be about 7%. You can also you bq27200.sh script for monitoring EDV1/F LOW flag. After battery will be empty, charge it to full and discharge again.

Now going to fix second problem. Thanks for finding & reporting bug in kernel.
Hello.

Now I think I have done what I need to do.
I discharged the battery to ca 120mh.
Charged it again to full.
And finaly discharged it to ca 120mh and did a full recharge again.
Is the output from uevent corret now?
http://toxaris.com/uevent2.txt
(I still got the same output in the bettery-meny)

btw, I tried the bq27200.sh script I found on TMO, but I only get some error messages.

Is it safe to upgrade to KP52 if Im running CSSU-T and Thumb2(based upon KP51r1)?
 
Posts: 2,153 | Thanked: 8,462 times | Joined on May 2010
#964
for bq27200.sh you need installed i2c tools and run it as root.
 

The Following 2 Users Say Thank You to pali For This Useful Post:
Posts: 424 | Thanked: 196 times | Joined on Mar 2010 @ Sweden
#965
Originally Posted by pali View Post
for bq27200.sh you need installed i2c tools and run it as root.
Ahh, I need to install i2c tools, then I misunderstood the instruction in the battery-thread.

Will try that.
 
Posts: 424 | Thanked: 196 times | Joined on Mar 2010 @ Sweden
#966
Originally Posted by toxaris View Post
Ahh, I need to install i2c tools, then I misunderstood the instruction in the battery-thread.

Will try that.
Ok, I already had i2c-tools installed.
I have put the file from this link: http://enivax.net/jk/n900/i2cget
in /usr/bin where bq27200.sh also resides.
If I then run bq27200.sh as root I get this output, is it correct?
http://toxaris.com/bq27200.sh.log
 
Posts: 1,808 | Thanked: 4,272 times | Joined on Feb 2011 @ Germany
#967
Originally Posted by toxaris View Post
Ok, I already had i2c-tools installed.
I have put the file from this link: http://enivax.net/jk/n900/i2cget
in /usr/bin where bq27200.sh also resides.
If I then run bq27200.sh as root I get this output, is it correct?
http://toxaris.com/bq27200.sh.log
Did you stop bme before running the script?
 
Posts: 424 | Thanked: 196 times | Joined on Mar 2010 @ Sweden
#968
Originally Posted by reinob View Post
Did you stop bme before running the script?
Yes.
With these commands.
Code:
stop bme
modprobe bq27x00_battery
modprobe bq2415x_charger
 
Posts: 204 | Thanked: 423 times | Joined on Jan 2011
#969
You don't need to modprobe anything.
You don't need to stop bme either.
 

The Following 4 Users Say Thank You to hxka For This Useful Post:
Posts: 424 | Thanked: 196 times | Joined on Mar 2010 @ Sweden
#970
Originally Posted by hxka View Post
You don't need to modprobe anything.
You don't need to stop bme either.
I know, now I do the calibration with bme instead.
Works sofar.

But maybe pali was interested in the problems with the script running on bq-modules.
 
Reply

Tags
cssu testing


 
Forum Jump


All times are GMT. The time now is 09:34.