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

Root ChevyNO1 killed my battery...

Umm, It has been updated to *not* kill you battery.

Before it was.

Still, your problem may have been the kernel itself - but I highly doubt it.

I've been rooted for well over 6 months and have used every kernel out there I can find - NO KERNEL has caused that much of a drain on the battery simply by having it installed.

It's either a) your settings, of b) an app that is continuously using the CPU.

I bet on b)
 
I think it was the kernel I was using

seeing as pandora hasn't crashed my phone all day and Im still sitting at 80%

and seeing as the facebook app wasn't updated on my phone until this morning when I woke up
 
I been using Chevy's 1200 with Pandora all week without it crashing once.

Again, the kernel itself will not cause battery drain. What will is either user settings or an app that is constantly using the CPU.

I cannot make this any clearer.

If you installed the kernel and did not test it with SetCPU to see if your phone can make use of it and remain stable, then next time be sure to do that. Not all phones can handle the same overclock.

The battery simply supplies electrical power to the phone. If there is nothing there to use that power, it won't charge down. Thus, as I said, it has to be settings or an app.

I was leaning more toward the app, but it could very well be settings, or a combination of both, that caused the drain.

It could also be that it wasn't fully charged in the first place....
 
Chevy's new 800 ulv wsn;t kind on my battery either. Running Cyanogenmod RC2 and it wouldn't save pictures after I took them and the battery was at 20% after below normal useage by 5. I switched right back to gjdlfg 800 for Cyanmod and battery went right back to "normal."
 
If you just change the kernel and leave all your settings the same, chances are it is going ot do very weird things on your phone. You have to test the kernel with your settings, and adjust them to match the kernel you just installed.

Just installing a kernel and doing nothing else falls under the first category of problems I mentioned, the settings part (which makes it basically user error.
 
johnlgalt said:
If you just change the kernel and leave all your settings the same, chances are it is going ot do very weird things on your phone. You have to test the kernel with your settings, and adjust them to match the kernel you just installed.

Just installing a kernel and doing nothing else falls under the first category of problems I mentioned, the settings part (which makes it basically user error.
Click to expand...

I did change the settings. Always do. Usually Chevy's work well for me. This is the first kernel to do this.
 
well I don't run SetCPU

so yeah

as you can see other people are having problems with chevys kernels too

everyones Droids are different and kernels work different on every phone.

I guess Chevys didn't work on mine but the P3Droid ones working amazingly
 
If you don't have SetCPU installed you really shouldn't be running OC kernels to begin with - SetCPU will prevent damage to your phone if you correctly set up a fall back profile in case it overheats.

But that still doesn't negate what I said earlier.
 
so the month running BB.4 with out setcpu I messed up my phone and over heated it

hmmm

my phone is running just fine

no over heating no battery problems until I used a new kernel other than petes custom kernel from bb .4 and the p3droid one Im using now

all the guides of rooting and after root have no mentions of making sure you have setcpu installed
 
All the guides of rooting are just for that rooting they are not Overclocking guides, which are separate.

Read some of those and you'll see why SetCPU is not only mentioned, but that it is considered the Holy Grail when it comes to Over Clocking - which is separate than rooting.

I understand that your particular experience seems to indicate that the kernel and only the kernel is at fault - but I am trying to get you to understand that *some* kernel is always necessary for the OS to boot. That particular kernel did not like your phone as you have it set up - with apps, customizations, etc.

Also, Pete's BB comes with a kernel that he tested heavily to make sure it would work with his ROM - it's why he selected it. If Chevy's would have been the best one then it would have been Chevy's in the ROM.

Kernels, by themselves, cannot cause your battery to drain. The OS and your apps are what uses power continuously.
 
honestly

I think you are missing the point

recap:

flashed chevys 800mhz 7 slot kernel

phone dead by 2 pm after been off the charger at 8 am

day 2 after doing a battery pull phone crashed 3 times with pandora running

day 3 flashed a P3Droid kernel. NO PROBLEMS!

its not any apps running. I can assure you that.

stop being a Mister Know It All. its kinda of annoying
 
I am running P3 1.2ghz over chevy's ss4.5...I get great battery life and nice speed, the 800 built in kernal didn't like my phone but as soon as I flashed the P3 its been running great ever since
 
Depends upon the theme - highly intensive graphical themes will, b/c it requires processing power to render all the graphics, which uses battery juice. Same can be said for Live WallPapers, lots of widgets, etc.
 
I can vouch that it WAS indeed Chevy's kernel that wasn't playing nice with me. I do not use the facebook app. haven't even logged in or opened it ever. I only have a handful of third party apps I use and I configure setcpu like I usually do for Chevy's kernel. When I used Chevy's kernel on BB or the rooted Froyo release it ran perfectly fine with no battery issues but when I flashed in on RC2 my phone was literally dead in 8 hours. Worst battery life I ever got. Then I flashed p3's kernel and set up setcpu to the correct values I wanted and my phone last a full day easy. btw I am not overclocking. I set the max to 600
 
johnlgalt said:
Depends upon the theme - highly intensive graphical themes will, b/c it requires processing power to render all the graphics, which uses battery juice. Same can be said for Live WallPapers, lots of widgets, etc.
Click to expand...

Mhmm, still tryin to find the culprit in my case then... Maybe its time for a new rom?
 
Or it could be your current ROM needs a new kernel.

That is the disadvantage of mixing and matching - you have to test it out for yourself. With over 100K apps in the market, it is highly unlikely that any 2 DROIDs will every be identical.

If this particular kernel doesn't work well on your phone / with your ROM, try another.

I haven't seen a ROM yet that will not work with at least one set of OC kernels....
 
johnlgalt said:
Or it could be your current ROM needs a new kernel.

That is the disadvantage of mixing and matching - you have to test it out for yourself. With over 100K apps in the market, it is highly unlikely that any 2 DROIDs will every be identical.

If this particular kernel doesn't work well on your phone / with your ROM, try another.

I haven't seen a ROM yet that will not work with at least one set of OC kernels....
Click to expand...

I have tried chevyno1's and p3's. What would you recommend I try next?
 
I stuck to jdflg's kernel the whole time I was running Pete's BB 0.4 (FroYo 2.2 leaked release based ROM - and I loved them.

But *my* recommendation means very little. Here is why.

As with all mass produced electronics, there are variations in each individual piece, which leads to a broad spectrum of inconsistencies. My phone can do 1200 MHz stable with most kernels, but some in hte past have made my phone lock up tighter than Fort Knox. Others cannot get past 1000 MHz, while others can push their phones past 1300MHz.

For me to recommend a kernel would be based upon my experience, and while that comes from a whole slew of different ROMs, it comes from a single phone - mine - which I have had since 7 Nov 2009.

Your phone may not like my recommendation at all - or it may like it better than my phone does. Your current ROM may not like my recommendation - or it may like it better. A certain app (or group of apps) that you have installed may not like my recommendation - or it may like it better.

There are so many variables involved in picking the right kernel and overclock that making a recommendation is nearly impossible for anyone with this kind of insight as to the number of variables involved.
 
You must log in or register to reply here.
Back
Top Bottom