[TESTING] SCBS: Improved battery meter system

[jonpry]

Ndno,

Your new model looks good. There is a new kernel and rootfs.img i have uploaded. Need both at the same time, neither are backwards compatible. It will make some attempt to determine se=. right now it is just at the default. I think this will improve sleep accuracy, se should be within 0 - .008

Did you download the modules .tar.gz from the first post? That will be necessary to get working wifi. If its still not working post a dmesg from when you try to enable wifi. Works on my phone, just a module problem one way or another.

[ndno]

Originally Posted by jonpry

Ndno,

Your new model looks good. There is a new kernel and rootfs.img i have uploaded. Need both at the same time, neither are backwards compatible. It will make some attempt to determine se=. right now it is just at the default. I think this will improve sleep accuracy, se should be within 0 - .008

Did you download the modules .tar.gz from the first post? That will be necessary to get working wifi. If its still not working post a dmesg from when you try to enable wifi. Works on my phone, just a module problem one way or another.

OK, I just downloaded the files from your first post and they are the same as before (I mean the same as the time you first started this thread). So I already have the latest. You mentioned a "new kernel and rootfs.img" but they look the same as those from the time this thread started. When were these uploaded?

I'm going to test the wifi now and post the dmesg for you.

EDIT: OK, it looks like the kernel you have in the first post has a different "version" than the modules you posted. I ran the "lsmod" command and it shows no modules loaded, meaning the broadcom module for the wifi hardware is not loaded. I did some further investigation:

# uname -a
uname -a
Linux localhost 2.6.27.46-01301-g595725b-dirty #167 PREEMPT Wed Apr 6 11:36:31 AST 2011 armv6l GNU/Linux

However the modules you have in the first post is modules-2.6.27.46-01300-g78e70e3-dirty.tar.gz, which has build 1300, not 1301. Will the broadcom module load if the kernel has a different build than the modules?

I tried to force the wifi hardware load as follows:

# cd /lib/modules/2.6.27.46-01300-g356b733-dirty # it goes to /data/modules
# insmod bcm4329.ko
insmod bcm4329.ko
insmod: can't insert 'bcm4329.ko': invalid module format

The dmesg has the follow error:

[ 6778.379180] bcm4329: version magic '2.6.27.46-01300-g356b733-dirty preempt mod_unload ARMv6 ' should be '2.6.27.46-01301-g595725b-dirty preempt mod_unload ARMv6 '

So it seems like the modules and zImage in the first post don't play nice with either other due to the different build number. Can you post the modules*.tar.gz file for build 1301? Thanks.

[jonpry]

How are you checking that the files are the same as they used to be? Definitely uploaded new stuff. When you run the app it should say scbs version 0.4.a. I will upload a new modules tar shortly and update this post. I thought it would work as long as the git commit was the same id.

[ndno]

Originally Posted by jonpry

Ndno,

Your new model looks good. There is a new kernel and rootfs.img i have uploaded. Need both at the same time, neither are backwards compatible. It will make some attempt to determine se=. right now it is just at the default. I think this will improve sleep accuracy, se should be within 0 - .008

Did you download the modules .tar.gz from the first post? That will be necessary to get working wifi. If its still not working post a dmesg from when you try to enable wifi. Works on my phone, just a module problem one way or another.

Thanks. I will update the kernel and rootfs.img from the first post; I didnt't realize you updated them since you started the thread. I'm using the modules*.tar.gz from your first post. I will make sure when I get back; I will post the error from dmesg for you.

Had a charge lockup this morning. I went to sleep having my phone hooked up to the charger. When I woke up this morning, the led was blinking green but I couldn't get it to wake up; pulled the battery and rebooted to winmo, which showed a 100% charge; booted back to android and it showed a 98% charge. This is with the 1.103 to one of values in sbcs.conf you recommended because my phone would stop charging at the 95-98% range.

Sent from my FRX06-ized TP2 using Tapatalk

[arrrghhh]

Originally Posted by ndno

Had a charge lockup this morning. I went to sleep having my phone hooked up to the charger. When I woke up this morning, the led was blinking green but I couldn't get it to wake up; pulled the battery and rebooted to winmo, which showed a 100% charge; booted back to android and it showed a 98% charge. This is with the 1.103 to one of values in sbcs.conf you recommended because my phone would stop charging at the 95-98% range

I had a lockup condition exactly like this today as well - phone wasn't hot, LED blinking green... all the lights worked (4-button lights & kbd lights) so kernel was *somewhat*awake... But nothing would get the phone to actually turn on. Phone was on the charger all night.

Very weird condition... I wonder if there's some way to have logs going at all times, that rotate when they need to? Probably won't be able to rotate them when they need to... but maybe we can at least get some logging going with the hope that it catches this crap.

[jonpry]

I haven't seen this charge lock up thing before. I'll have my phone spend more time on the charger in hopes of catching it.

[ndno]

Originally Posted by arrrghhh

I had a lockup condition exactly like this today as well - phone wasn't hot, LED blinking green... all the lights worked (4-button lights & kbd lights) so kernel was *somewhat*awake... But nothing would get the phone to actually turn on. Phone was on the charger all night.

Yep, exactly like yours. Buttons and keys continue to work. That's the only problem I've seen so far (and maybe the wifi, I need to double check). Been running this kernel for the last 4 days without any SOD or reboot to WinMo.

[ndno]

Originally Posted by jonpry

How are you checking that the files are the same as they used to be? Definitely uploaded new stuff. When you run the app it should say scbs version 0.4.a. I will upload a new modules tar shortly and update this post. I thought it would work as long as the git commit was the same id.

Sorry if I'm incorrectly downloading the files. I just use "diff" under Ubuntu to check if they are the same files as the ones I already have on my SD card and they are. I'll try again.

Edit: OK, I have 0.3.d as the version which is old. Is this from the kernel, modules, or rootfs? I will replace the ones on my SD card with the new ones downloaded from the first post.

Sent from my FRX06-ized TP2 using Tapatalk

Edit2: Ok, my rootfs.img was old so I replaced it and now the version is 0.4.a (the only difference was the scbs binary executable). My zImage and modules I have on my SD card are exactly from the first post; the broadcom module won't load as I stated in my last post, even if I forced it via the insmod command.

[jonpry]

I spent like an hour trying to edit the first post and it just won't commit for me. Urgh. Here is a link to the new modules.

http://prymfg.com/kernel/modules-2.6...b-dirty.tar.gz

[arrrghhh]

Originally Posted by jonpry

I spent like an hour trying to edit the first post and it just won't commit for me. Urgh. Here is a link to the new modules.

http://prymfg.com/kernel/modules-2.6...b-dirty.tar.gz

I'm not sure what's up with ppcg, but "Quick Edit" doesn't work. Hit "Go Advanced", make your edit, "Save Changes" -> should be good .