was wondering if anyone has advice on the best settings inside the app to get the best battery life and performance out of it. any advice would be awesome thanks
Franco's Kernel APP
- Thread starter mike.mercer
- Start date
I just run the kernels as they come mostly. In the app you can disable logger to help performance a tiny bit. Idk.. Just run it and tweak it. Conservative gov should theoretically give best batt life but I like ondemand or interactive. You can disable higher clocks if you want.. Such as setting max speed to 1036 or even lower if saving battery is that big a deal, obviously you sacrifice some performance tho.
Sent from my Galaxy Nexus using Tapatalk 2
Sent from my Galaxy Nexus using Tapatalk 2
If you want good battery life, you are going to want to enable hot plug for one. When you are in the app, go over to settings and check the box Generic Hotplug. This will turn off CPU1 when the screen is off to conserve battery and the CPU will reactivate when needed. Next, pick a governor. Personally I use conservative but I don't think that there is going to be huge difference between ondemand, interactive, conservative or lazy. Yea you will see maybe a slight difference between them but generally conservative or lazy I would say for max battery. I have my CPU set min of 729 and max 1228 conservative with slight undervolt. Undervolting for me goes like this an I haven't had a problem yet:
729 - 1150mV
1036 - 1200mV
1288 - 1275mV
1344 - 1325mV
Personally I prefer to use stable kernels so I am running Milestone 3, however the nightly kernels have some new features like running the CPU at a min of 149. Its all up to you which you prefer but if you are newer to kernels and tweaking, I would say stick with milestone for now. Hope this helps!
729 - 1150mV
1036 - 1200mV
1288 - 1275mV
1344 - 1325mV
Personally I prefer to use stable kernels so I am running Milestone 3, however the nightly kernels have some new features like running the CPU at a min of 149. Its all up to you which you prefer but if you are newer to kernels and tweaking, I would say stick with milestone for now. Hope this helps!
And the md5 sums are now included in the app. You're welcome 
I'm Christopher Williams, btw
*customized tapatalk signature*
I'm Christopher Williams, btw
*customized tapatalk signature*
And the md5 sums are now included in the app. You're welcome
I'm Christopher Williams, btw
Click to view quoted image
*customized tapatalk signature*
Care to explain what md5 sums are?? Noob here.. Thats like speaking a different language to me.. Blank stare.. lol I want to say thanks but im so lost on that one haaa..
it's the character string that is generated for a file, so when you download you can check the string to make sure they match.
if they match = same file, not corrupted.
if they dont match = somethings not right and dont flash it.
^ Saw that and I laughed. I flashed a ROM on my Thunderbolt way back when and I kept getting boot loops and I couldn't figure out why. After about an hour I finally checked the file I was trying to flash and it was a corrupt file (aka MD5 didn't match) and now I wont flash anything unless I check that first.
Lessons are learned the hard way lol.
MD stands for Message Digest. It is a hashing algorithm that works well on large files, but is really sucky on small files. For our purposes, it works great as a file verifier. If the MD5 values match, the file was downloaded with no errors.
Thanks for stepping in for me while I was away, fellas. I was at Chuck E. Cheese with my little homie.
I always recommend Franco's kernels, not just for their sheer performance and options, but for his unparalleled support as well. I really can't say enough good things about his work. Definitely buy his app and support him if you haven't, and definitely try his kernels if you haven't.
I asked for the md5's to be included because I auto flashed using his app and bootlooped. I was on 3G at the time. I always download them first now, and since I usually like to check the md5 of anything I flash if possible, I asked that he include them. He did. What a good dev. That's awesome.
Now I will never doubt my flash if something is off, and not bother him with erroneous bug reports. If I KNOW the kernel I flashed matches the md5 and no one else that flashed the kernel is having the same problems... look elsewhere.
It's not that big of a deal anyway, because I would usually just re-download and flash to see if the issue still existed... but now I won't have to.
This post has been brought to you by lunesta. Blurring the lines of semi-conscious reality since 2004.
*customized tapatalk signature*
I always recommend Franco's kernels, not just for their sheer performance and options, but for his unparalleled support as well. I really can't say enough good things about his work. Definitely buy his app and support him if you haven't, and definitely try his kernels if you haven't.
I asked for the md5's to be included because I auto flashed using his app and bootlooped. I was on 3G at the time. I always download them first now, and since I usually like to check the md5 of anything I flash if possible, I asked that he include them. He did. What a good dev. That's awesome.
Now I will never doubt my flash if something is off, and not bother him with erroneous bug reports. If I KNOW the kernel I flashed matches the md5 and no one else that flashed the kernel is having the same problems... look elsewhere.
It's not that big of a deal anyway, because I would usually just re-download and flash to see if the issue still existed... but now I won't have to.
This post has been brought to you by lunesta. Blurring the lines of semi-conscious reality since 2004.
*customized tapatalk signature*
Ahhhh so its what I had to check before I flashed my radios. Now that makes perfect sense.
Sent from my Galaxy Nexus using Tapatalk 2
Sent from my Galaxy Nexus using Tapatalk 2
I would check the MD5 values before flashing anything. ROMs, radios and kernels are most important since they are crucial to your phone but I usually check everything I flash just to be safe. Yea soft boots are easy to fix, but who wants to have to do that just because of a silly mistake.
Edit: Now that I did a full battery drain (down to 3%) with the settings that I posted above, I am going to try the lazy governor with everything else the same. I had 1D-1H-25m on battery, 1H 40m screen on and 30m of phone calls on that drain. I probably wont see that much of a difference but worth a test.
Crackflashers don't check MD5's
I used to check them religiously... lately I glance at it for a ROM, if the first few characters match its good, lol. I don't even bother checking them for anything else (but I should, especially for radios, I'm dumb).... but I like to live dangerously and I understand the repercussions if I screw up
Certainly it's super easy and good practice to check them and I don't want to encourage anyone against it
I used to check them religiously... lately I glance at it for a ROM, if the first few characters match its good, lol. I don't even bother checking them for anything else (but I should, especially for radios, I'm dumb).... but I like to live dangerously and I understand the repercussions if I screw up
Certainly it's super easy and good practice to check them and I don't want to encourage anyone against it
Crackflashers don't check MD5's
I used to check them religiously... lately I glance at it for a ROM, if the first few characters match its good, lol. I don't even bother checking them for anything else (but I should, especially for radios, I'm dumb).... but I like to live dangerously and I understand the repercussions if I screw up
Certainly it's super easy and good practice to check them and I don't want to encourage anyone against it
I agree that after a while (especially if you flash often) it gets to be a chore. For new flashed I would say that it is a staple process, but yea lately I have been getting into the same habit as you which I know is bad :-X
I only check for radios. I guess bootloaders on the rare occassion that those get flashed.
An update that contains radios, same thing, check it.
Roms and kernels i never check (unless i am distributing the file for you guys, then of course i check it first). For my personal use, i dont mind a boot loop bc i always have a nand to restore if i need it, or i'll reflash the thing, etc.
An update that contains radios, same thing, check it.
Roms and kernels i never check (unless i am distributing the file for you guys, then of course i check it first). For my personal use, i dont mind a boot loop bc i always have a nand to restore if i need it, or i'll reflash the thing, etc.
watchtheflames
Well-known member
- Jan 18, 2011
- 132
- 14
- 0
Me to. I just want a stable Kernel. Should I just stick with the M3, or is one of the Nightlies a lot better. Also, can you choose specific nightlies in the app, or just the latest one? I did purchase this app today and the custom options are crazy. Not sure I'll mess with too many of them, but it's a well put together app and I'm glad to support they guy.
GPU over clock speeds. Just use 384...That's what I use, I see no reason to push it, especially if you want stability. Some phones can't even boot with the higher one.
Sent from my Galaxy Nexus using Tapatalk 2
tony bag o donuts
Q&A Team
- Apr 26, 2010
- 4,339
- 263
- 83
Similar threads
Trending Posts
-
-
-
-
Question Android 14: Is there a Do Not Disturb Feature?
- Started by tinker1234
- Replies: 1
-
Facebook
Twitter
Instagram