[TESTING] SCBS: Improved battery meter system

[arrrghhh]

Originally Posted by ndno

CWM should allow us, the users, to create an update.zip to patch any distribution with this and share it with the other users.

Yes, assuming they are also running cwm

[jonpry]

The code for scbs is here scbs in scbs - Gitorious

There is just a stupid build script for making it under ubuntu assuming you already have meschach installed. I'm sure it could be built for win32, but I haven't tried. I have a feeling the code could be made several times faster by removing meschach. At least it would be several times faster on x86, on arm novfp its not clear how much time is wasted with memory allocation because the math is just oh so slow anyways.

I have limited data on the consistency of the numbers. From my own experience, the numbers i get all "work", ie my battery meter is always accurate enough that I cannot prove it to be wrong. But there is a great deal of variation in them. Say +/- 25%. That may seem like a lot but its really only -6dB of noise.

It would be nice to get them more consistent, and i have some ideas on how to do it. But none of it is easy, and I wonder what the purpose of getting battery readings accurate to 6 decimal places really is.

[manekineko]

Yikes, got hit by the bug again, only this time I didn't catch it in time and it drained the battery flat to the point it couldn't boot or charge normally anymore.

Twice in two days is a lot even for me, hopefully it's a coincidence to when I started to use the improved battery meter.

[teemo]

Before this SCBS, I used voltage as health indicator: 4.25V=100%
Now my Battery Monitor can't read Voltage, a fully charged battery return 0.100V
What happened ?

FRX06 + arrrghhh's 4/15/11 SCBS

[jonpry]

wateverweber,

you haven't generated a model yet, so there is no conf file. Also 99% might be more correct than not. Thing is that charging starts to get exponentially slower after 80%. Afaict it can literally take days to get the last 1%,

toadlife,

Is there any particular reason you want to run it as a service? Atm scbs cannot be killed reliably, very bad thing can happen. For restarting we use killall -HUP scbs which just sends a signal to scbs to manage its own restart. Also for those trying to cookup a rootfs, there is a script in /sbin that you will need. Its called updatescbs or something.

teemo,

That is a known bug, still working on it.

[toadlife]

Originally Posted by jonpry

toadlife,

Is there any particular reason you want to run it as a service? Atm scbs cannot be killed reliably, very bad thing can happen. For restarting we use killall -HUP scbs which just sends a signal to scbs to manage its own restart. Also for those trying to cookup a rootfs, there is a script in /sbin that you will need. Its called updatescbs or something.

Yeah, I posted a few posts back. I've been launching logcat from /init and whenever I would launch scbs logcat would die.

http://forum.ppcgeeks.com/android-tp...ml#post2089505

The service I created only runs once and all it does it launch scbs.

killall -HUP still works AFAIK.

[manekineko]

Just checking, but once scbs.conf has been generated and placed in the root of the SD card, that's all that must be done to install a battery configuration, right?

I'm starting from a clean data.img, and I see in the boot text that the SCBS battery daemon is starting, just wanted to make sure I didn't have to do anything like run BABS again to get it to use the conf file.

[steveholtam]

Another question for you Jon. At what point do we have enough data to stop running SCBS? After a few weeks your software should have a pretty good model correct? Why would we want to continue running the software, which uses the phones resources and memory?

[jonpry]

manekineko,

you don't need to run the app once you are happy with the model and have the conf. the daemon will startup with the phone and will take care of everything else.

steveholtam,

i suppose you can log to /dev/null as others have suggested, but the daemon still needs to run as it does all the battery calculations. I don't think it takes significant cpu to figure out the battery stuff, maybe a fraction of a percent. Imho the sdcard writes are not a big deal either. After all I use sd card as swap space. Others will tell you this is not sane. Its a matter of preference i suppose. Its probably a good idea to set the priority of scbs to absolute minimum. Its rarely going to be critical that the battery meter update right on the timer tick.

[manekineko]

If you just don't want the logs anymore after you've setup SCBS, an easy way is to add a line like this to your conf file at the end:
rm -f /sdcard/scbs.log*