Not normal, no. Something else must be going on here. I'm using Chevy's LV @ 1200 right now and I was at 70% battery last night after 14 hours. Have you checked your battery usage to see what's draining it?
__________________ The following statement is true The previous statement is false
The Following User Says Thank You to vincentp For This Useful Post:
I flashed the 800mhz kernel last night with my root of petes 2.2 ota
but 2 o clock my battery was dead
it was even the low voltage one too.
any body know if thats normal?
I'm using his 1GHz kernel at 900MHz with Pete's FRG01B 2.2 release (what you're using) and getting excellent battery life.
Not all Droid's react the same way to kernels. Try a few different ones and see what happens. Make backups first and make sure 'set on boot' is unchecked in SetCPU while you do your testing. You can check it when your phone is running the way you want it.
The Following User Says Thank You to AndroidsOfTara For This Useful Post:
I'm having problems with battery life to. Tried many different roms. Need to try new kernels. Would switching from ULV to meV make a difference? Since all phones are different.
__________________
ROM:BB v 0.4 with Blue Energy theme switched to
Kangerade 5.0.9
Kernel: p3 at 1.0ghz switched to Chevys 1.1 LV
Now on Chevys 1.1 ULV
FINALLY!!! Success with Lithium Mod with jdlfg Kernel 1.1 with blue launcher pro theme.
Droid-Life reported today that the facebook app is sucking down batteries. I am gonna turn off sync or uninstall tonight. I use the mobile site more often anyway
^^^ lol, people are looking at me funny at work because i really just did start laughing upon reading that...
diff phones react differently to roms and kernels, right now pete's bbv0.4 running chevy's ulv 1gig kernel is hitting my droids sweet spot. runs smooth, quick, battery life = great.
Increasing the voltage should never have a positive impact on battery life. By definition the phone is using more power.
Mostly true, but it is definitely possible to have a higher voltage use less battery if the voltage conversion from the battery to the voltage used by the OMAP processor is really inefficient at the low voltage and more efficient at the higher voltage..
Generally as the voltage goes down, so does efficiency, so there is a point where lowering the voltage consumes more battery power..
Check widgets and hours between refreshes that use data. Even battery widgets can drain if it's putting up numbers ever 30 seconds - the widget needs to use resources to get a reading.
Try JuiceDefender as well - awesome battery saver and now working for CDMA
__________________ SHOT CALLER
RIP 2K1 Caddy STS - Hello 2K11 Chevy Cruze...25mpg vs 8mpg. WOOT
I am a MasterDebator "Eat Me" on Yelp--also make sure to QuagMyTwitr
op in setcpu are you set to performance all the time? once I set it to ondemand and made some profiles battery life seems to be way better for me on 1.2 low voltage.
I heard there were some issues with Chevy's kernels if you downloaded them between 8/1 and 8/3, but he fixed the issue, so if you are having issues then you might want to download and flash the new ones.
op in setcpu are you set to performance all the time? once I set it to ondemand and made some profiles battery life seems to be way better for me on 1.2 low voltage.
I bet even money it was not the kernel, but the fact that the Facebook app was sucking your battery down - it had an issue that had it continuously synchronizing events or notifications or something.
The new update fixes that - but in the meantime a lot of people probably thought it was something *else* that was causing the battery discharge issues.
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 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.
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.
I did change the settings. Always do. Usually Chevy's work well for me. This is the first kernel to do this.
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.
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.
Last edited by johnlgalt; August 7th, 2010 at 05:09 PM.
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
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.
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....
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....
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.
Last edited by johnlgalt; August 8th, 2010 at 03:08 PM.
The Motorola Droid - the first ever Verizon Android Phone - exploded onto the mobile market with an incredibly successful ad campaign that brough Android to the masses. With a huge and vibrant touchscreen, solid metal body, full QWERTY keyboard, 5M... Read More
ChevyNO1 killed my battery...
