[TESTING] SCBS: Improved battery meter system

[highlandsun]

jonpry: your app is reading Battery Voltage and reporting it as capacity. This fixes it.

diff --git a/app/src/com/prymfg/babs/HtcBattery.java b/app/src/com/prymfg/babs/HtcBattery.java
index 3a7830f..e6c4acb 100644
--- a/app/src/com/prymfg/babs/HtcBattery.java
+++ b/app/src/com/prymfg/babs/HtcBattery.java
@@ -73,7 +73,7 @@ public class HtcBattery {
         if(real_device)
         {
             try {
-                String str = readFileAsString("/sys/devices/platform/htc_battery/power_supply/
battery/batt_vol");
+                String str = readFileAsString("/sys/devices/platform/htc_battery/power_supply/
battery/capacity");
                 return str.substring(0,str.length()-1) + "%";
             } catch (IOException e) {
                 return "busted";

(I've also fixed this in your kernel code so that it doesn't highjack the batt_vol reading with capacity any more, since it's already reporting capacity in the capacity node where it belonged... http://lists.xdandroid.com/pipermail...ay/000272.html)

[ndno]

OK, another day a half of data collection, here are my new values from the attached scbs log files; the se value got down to 0.007:


cc=0.308551483
cb=151.246337531
rc=1.195478281
re=0.136412463
vf=1.103000000
cf=0.312500000
lr=0.000001000
sl=9.589367021
se=0.007547648

Gonna try another distribution over at neopeek with this SCBS-kernel system now. Thanks!

I have installed it the battery meter works Great on my TP2 Rhodium 100.
But the Kernel Blocks the use of my wifi...

For so far i can live with it...
I am fully open for any tests on this smartphone...For So Far thnx alot

[jonpry]

heck0211,

The best thing to do is just to use the wistilt2 testing kernel pack with zImage and modules. It will get wifi working for you.

[steveholtam]

Jon, attached is a large log file that I am not having any luck analyzing since it is quite large. I think its a couple of days worth of operation.

[jonpry]

Steveholtam,

Here is what i got from your log in a slightly different format:

Rc: 0.460259, Re: 0.217757, Cc: 0.425917, Cb: 106.443573 Sl: 14.180931: Se: 0.058490

[steveholtam]

Originally Posted by jonpry

Steveholtam,

Here is what i got from your log in a slightly different format:

Rc: 0.460259, Re: 0.217757, Cc: 0.425917, Cb: 106.443573 Sl: 14.180931: Se: 0.058490

Thanks Jon. My sleep error number just sucks all around... Oh well, hopefully your code will give me a better idea how much juice I actually have left at any time though.

[toadlife]

After creating a bogus conf that sent my phone in a reboot-loop, I credated another one...

cc=0.486578467
cb=86.509612234
rc=0.413599619
re=0.174350114
vf=1.098000000
cf=0.312500000
lr=0.000001000
sl=15.229616050
se=0.014369028

Even without the .conf, the meter is much better!

[manekineko]

Rhodium 400, original battery

Booted up, charged it to full, then ran it down to 7% with a mix of ~12 hours of sleeping, wifi tethering and games before charging it all the way back to full.

cc=0.069308073
cb=115.604675265
rc=0.842694823
re=0.228095166
vf=1.098000000
cf=0.312500000
lr=0.000001000
sl=16.619811388
se=0.010055974

Has anyone collect data multiple times to see how constant these numbers remain between between runs? That would seem to indicate how accurate they really are.

Does SCBS continue generating new logs so we can do that after a model has already been accepted?

[arrrghhh]

Originally Posted by manekineko

Rhodium 400, original battery

Booted up, charged it to full, then ran it down to 7% with a mix of sleeping, wifi tethering and games before charging it all the way back to full.

cc=0.069308073
cb=115.604675265
rc=0.842694823
re=0.228095166
vf=1.098000000
cf=0.312500000
lr=0.000001000
sl=16.619811388
se=0.010055974

Has anyone collect data multiple times to see how constant these numbers remain between between runs? That would seem to indicate how accurate they really are.

Does SCBS continue generating new logs so we can do that after a model has already been accepted?

Model looks fine to my untrained eyes.

Yes, it will keep generating logs to be analyzed. You can re-run it as much as you want, you can even use multiple logs in the algo.

What I'm wondering is how to stop it? Does it just perpetually take logs? I guess I'm not sure how this is going to be permanently implemented, there obviously has to be some way to automate the process...