|
2012-10-12
, 09:05
|
|
Posts: 5,028 |
Thanked: 8,613 times |
Joined on Mar 2011
|
#2
|
|
2012-10-12
, 09:19
|
Posts: 669 |
Thanked: 433 times |
Joined on May 2010
|
#3
|
|
2012-10-12
, 14:18
|
Posts: 669 |
Thanked: 433 times |
Joined on May 2010
|
#5
|
|
2012-10-12
, 14:36
|
|
Posts: 5,028 |
Thanked: 8,613 times |
Joined on Mar 2011
|
#6
|
/sys/class/power_supply/bq24150-0/
|
2012-10-12
, 14:47
|
Posts: 1,808 |
Thanked: 4,272 times |
Joined on Feb 2011
@ Germany
|
#7
|
Thanks i using it now
any suggestion for the way to make it permanent instead of BME (the way to permanently prevent BME loading at startup and starting this mod instead - would it be best to modify the bme startup script for example)?
The Following 2 Users Say Thank You to reinob For This Useful Post: | ||
|
2012-10-12
, 20:18
|
Posts: 669 |
Thanked: 433 times |
Joined on May 2010
|
#8
|
Be careful!
I actually did that a few months ago. In the end I irreversibly* bricked my N900.
(* because USB port also stopped working, and even though I had U-boot installed the SD card wasn't being recognized..)
The /etc/event.d/bme script does quite a number of things besides merely starting bme (pre-charging, actdead-dependent stuff, etc.)
Plus /etc/event/rc-default (which emits the signal to start a runlevel) has "start on started bme".
I modified the latter to say "start on started dsme" (because bme starts when dsme has started).
It worked, but there were various issues when shutting down (it would go to actdead instead of shutting down) and starting up (sometimes it would go directly to actdead). If your USB port is healthy and/or you have U-boot and your SD card works, then go ahead and try it.
Unfortunately I didn't document everything I did, so I may have fvcked up somewhere else. Please do document what you do so we can all learn from it!
Cheers and good luck.
PS: without bme your battery indicator will be just a static bitmap. You'll need i2cget to know your battery status (you can easily get the voltage, which is as good/effective/informative as any percentage value).
The Following User Says Thank You to impeham For This Useful Post: | ||
|
2012-10-12
, 20:22
|
Posts: 669 |
Thanked: 433 times |
Joined on May 2010
|
#9
|
There are also many sysfs parameters, that you can modify after loading module (for example, as part of your loading script). See content of:
Most of things there are sysfs entry that you can modify, to alter things like charging current, or diode, or low battery threshold, or...Code:/sys/class/power_supply/bq24150-0/
/Estel
|
2012-10-12
, 23:49
|
Posts: 669 |
Thanked: 433 times |
Joined on May 2010
|
#10
|
I tried to stop BME and use the "charge21.sh" script for the charging process and it works good even though it charges slowly.
I'm thinking now to completely disable BME during startup in one of the following ways:
1. Adding a script to event.d with "stop bme" and "/usr/bin/charge21.sh&" commands
2. Modifying the "event.d/bme" script itself (which I was unsuccessful in doing since the device got to an infinite loop when I did it)
Taking care of emergency shutdown when the power gets very low is not a feature I need (I can implement it myself) so it does not make me worry, but I do want - if possible to keep the behavior of the flashing yellow light during charging and the green light when charging is complete (RSOC=100 is not enough to make the green led appear so I do not know how to REALLY know if the battery is fully charged).
Any thoughts/ideas/enhancements will be very welcome.