[TESTING] SCBS: Improved battery meter system

[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

[iiinycboi]

is it possible to remap the call button to be the home button on your roofts.img file? or can i use this fix 3 times to get a good battery model and put the F22 rootfs to have remapping capabilities?

BTW, thanks for awesome work!

thank you

[natemcnutty]

Originally Posted by iiinycboi

is it possible to remap the call button to be the home button on your roofts.img file? or can i use this fix 3 times to get a good battery model and put the F22 rootfs to have remapping capabilities?

BTW, thanks for awesome work!

thank you

Just grab the navipad.kl for your device from F22's rootfs and put it in this one.

[ndno]

Originally Posted by natemcnutty

Just grab the navipad.kl for your device from F22's rootfs and put it in this one.

I think he doesn't know how to "do" so, especially if he doesn't know Linux; he probably wants the rootfs.img updated with it

@iiinycboi, do you know Linux? If so, you can mount jonpry's rootfs.img under Linux (Ubuntu, Fedora, etc), and copy the navipad.kl from F22's rootfs over as Nate suggested.

If not, you can try this:

1. Boot into android, using F22's rootfs
2. Use a file explorer and navigate to /init.etc/keymaps and copy the navipad.kl file to your /sdcard directory
3. Boot back to WinMo and use a text editor to edit /conf/froyo.user.conf to add the following line in the custom_shells section at the bottom:
   

   mount --bind /sdcard/navipad.kl /init.etc/keymaps/navipad.kl

4. Replace F22's rootfs.img with jonpry's rootfs.img and you should get the button mapping the next time you boot into android; you should have SCBS feature working as well as the F22's button mapping.

I haven't tried this myself but it should work.

[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!

[iiinycboi]

Yeah i didnt know how to do it cause i wasn't familiar with linux. I'll give this a try sounds like it should work lol. Thanks in advance!

Originally Posted by ndno

I think he doesn't know how to "do" so, especially if he doesn't know Linux; he probably wants the rootfs.img updated with it

@iiinycboi, do you know Linux? If so, you can mount jonpry's rootfs.img under Linux (Ubuntu, Fedora, etc), and copy the navipad.kl from F22's rootfs over as Nate suggested.

If not, you can try this:

1. Boot into android, using F22's rootfs
2. Use a file explorer and navigate to /init.etc/keymaps and copy the navipad.kl file to your /sdcard directory
3. Boot back to WinMo and use a text editor to edit /conf/froyo.user.conf to add the following line in the custom_shells section at the bottom:
4. Replace F22's rootfs.img with jonpry's rootfs.img and you should get the button mapping the next time you boot into android; you should have SCBS feature working as well as the F22's button mapping.

I haven't tried this myself but it should work.

[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?