• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root ClockWorkMod

landonh12 said:
Yes, please. It seems that I have to reboot to get the battery to change it's percentage.
I tried the app battery drain and let it run for 10 minutes, still at 100% I need the stock, this didn't happen until after the custom kernel
Click to expand...

This may be related to something else you did
 
DsyMnapTic said:
This may be related to something else you did
Click to expand...

Can't be. I haven't done anything with root permissions to my phone after i flashed that kernel. I checked my superuser logs. nothing different than before i flashed it. so it has to be the kernel
 
I can reproduce the "always 100% battery meter" issue here. I just never noticed it before because I never really look at the battery meter.

I removed a bunch of messages from the kernel debug spew from the battery driver. Usually these messages are just used for debugging. It looks like LG decided they would use that spew to determine the battery drain and crap like that. To make it work like stock again, I can toss that debug crap from the battery back in.

I'll try that and then create a new thread about the kernel to keep from cluttering this one up.
 
giantpune said:
I can reproduce the "always 100% battery meter" issue here. I just never noticed it before because I never really look at the battery meter.

I removed a bunch of messages from the kernel debug spew from the battery driver. Usually these messages are just used for debugging. It looks like LG decided they would use that spew to determine the battery drain and crap like that. To make it work like stock again, I can toss that debug crap from the battery back in.

I'll try that and then create a new thread about the kernel to keep from cluttering this one up.
Click to expand...

Why didn't this effect my phone and cause my battery reading to get screwed up?
 
DsyMnapTic said:
Why didn't this effect my phone and cause my battery reading to get screwed up?
Click to expand...

I can only think of three possibilities:

1. You're on a different firmware version (either ZV4 for Virgin Mobile, or working on the Sprint/Ting ZV9). CWM was built for VM's ZV5 OEs.

2. The build was slightly corrupted upon download in such a lucky way that the battery status weirdness wasn't caused.

3. You're on an older version of CWM prior to his update of removing the dmesgs.
 
Hmmm.. something wierd just happened again giantpune. All of a sudden I'm getting correct readings from the battery status now. I have no idea why it went from not working to working like that. What could have caused this? I think if this continues to show correct readings im not going to revert back to the stock kernel.

Also.. simple question. Do you forsee an overclocking kernel by you in the near future? this phone will be a powerhouse if I can get this thing oc'd to 1.5ghz.. really
 
landonh12 said:
Hmmm.. something wierd just happened again giantpune. All of a sudden I'm getting correct readings from the battery status now. I have no idea why it went from not working to working like that. What could have caused this? I think if this continues to show correct readings im not going to revert back to the stock kernel.

Also.. simple question. Do you forsee an overclocking kernel by you in the near future? this phone will be a powerhouse if I can get this thing oc'd to 1.5ghz.. really
Click to expand...

It is stock overclocked as far as I know. It is normally supposed to be at 800MHz, and by default is overclocked to 1GHz. I wouldn't push it much farther.

Also, some process from the phone may have called for an update to whatever was causing an issue in the first place, causing it to correct itself and display appropriately.
 
Artine said:
I can only think of three possibilities:

...

3. You're on an older version of CWM prior to his update of removing the dmesgs.
Click to expand...

This isn't specifically related to CWM, the kernel in discussion is located on the boot partition. CWM has its own kernel and is on the recovery partition. That said, I believe both CWM and the custom boot partition are using the same/similar custom kernel (they just each have their own copy of it).

When booted normally, you're running off the boot kernel.

I wonder if it has anything to do with battery stats. I believe they are supposed to reset every time the phone is charged to 100%. They can also be reset in CWM, though I haven't tried that option yet.
 
Artine said:
It is stock overclocked as far as I know. It is normally supposed to be at 800MHz, and by default is overclocked to 1GHz. I wouldn't push it much farther.

Also, some process from the phone may have called for an update to whatever was causing an issue in the first place, causing it to correct itself and display appropriately.
Click to expand...

From reading around basically what I understand about kernal clock speed is that the kernal talks to the cpu and chooses a variable from several different outputs and selects the speed at which it thinks the processor best handles
 
DsyMnapTic said:
From reading around basically what I understand about kernal clock speed is that the kernal talks to the cpu and chooses a variable from several different outputs and selects the speed at which it thinks the processor best handles
Click to expand...

Hmm.. could there be a way to intercept this communication and set a value that would set a higher clock speed, or would that cause the kernel to panic requiring a battery pull? Just a thought.
 
Once everything's finalized with CWM, and we have working ROMs, why not shoot for CM7? It is a good idea - and, if anyone can do it, it'd be giantpune.
 
MStreeter said:
CM7? I just want Jelly Bean. This phone could run JB, correct?
Click to expand...

I want Harmonia, CM7 and Jelly Bean. :D

Yes, it should be capable of running Jelly Bean. I'm almost surprised it wasn't shipped with ICS, as Gingerbread is almost too low-end for the OE.
 
You must log in or register to reply here.
Back
Top Bottom