Hello everyone
How do I undervolt my phone which is running JVT Rom with Dark Core kernel 4.1 for JVT? I tried using voltage control but the tab for setting voltages is missing. I have tried a lot of other kernels but Dark Core seems the best overall, however the lack of undervolt is really putting me off.
Any help would be appreciated.
Just use TalonDEV or Semaphore with Thunderbolt tweaks and never look back just mentioning it as it seems your after battery life? Thunderbolt is great for that! With either of the above.. Plus both have great support here.
As for Darkcore could try Control Freak or Pimp My CPU or the Darky forums for better support.
Sent from my GT-I9000 using XDA App
Hey I am currently using Adrenaline Shot with Dark Core Kernel, and I have already tried semaphore and TalonDev before. Those are great kernels but nothing beats Dark Core's performance when combined with Adrenaline shot. Now I know that this comes with a hefty cost of your battery life, so I was wondering if I could undervolt to squeeze some extra juice out of battery when it is sleeping. I will try Control Freak and see if it works. Also, can you link me to Thunderbolt and is it a CWM flashable package? Also can it be mixed with Adrenaline Shot?
EDIT: Nope Control Freak is a no-go. Doesn't work. Man this is really difficult for me. I love the incredible stability and performance of Dark Core Kernel but the absence of undervolting is a hit.
get setcpu and then put the maximum slider back to watever you want
Hi, I'm tempted to push CPU beyond current 1200MHz, no Undervolting. I want to do a survey on what CPU frequency settings and UV hold you for daily use. :silly:
I'm currently using 1.3GHz/368MHz with smartassV2 governor. Good performance and good battery life on IceColdSandwich 8.2. At 1.4GHz or higher, it's unstable and the phone freezes while the screen is powered off sometimes.
I'm currently running 1420MHz with Ondemand governor, no UV, with no problems.
ZaySk said:
I'm currently using 1.3GHz/368MHz with smartassV2 governor. Good performance and good battery life on IceColdSandwich 8.2. At 1.4GHz or higher, it's unstable and the phone freezes while the screen is powered off sometimes.
Click to expand...
Click to collapse
I thought the phone will start freezing when max freq is set to 1.5GHz?
Sent from my potato chips using xda boost
I have my inc2 ocd to 1.5ghz on a daily basis , used to run cm at 1.8ghz daily with little overheating (nothing high enough to worry about), and I've also ran quadrant tests on cm7 at 2ghz.right now I'm running cm10 at 1.3ghz very stable.although sometimes in set CPU transitioning to a high freq like above 1.6 my phone would lock up but it seems like it happened only in ICS ROMs .idk hope this helps.BTW I never under or over volt
Sent from my Incredible 2 using xda premium
Should this not be under Q&A or general. Not really a developers topic
[GUIDE] *19/8 UPDATE!* 4.3 RESULTS! N7 'Best' Kernel (Performance & Battery Tests)
A lot of people have been posting in these forums, "Which kernel is the best"?
I was intrigued and decided to work this out for myself and share it with the rest of the community.
This is not meant to hurt the makers of these kernels.
But FIRST, it is not a fact that there is a 'best' kernel. 'Best' is an opinion and everyone has a different opinion.
On the Nexus 7, I personally believe there is no 'bad' kernel and none of these kernels I have tested perform badly or lag heaps.
People still like to push their N7's as hard as they can though.
The Main 2 Features people look for in a kernel are:
Performance & Battery Life
Some people prefer performance over Battery, or vice versa, or an all-round kernel.
NEXUS 7
8GB
Paranoid Android AOSPAL 3.97
KERNELS
Kernel[022]JB4.3(1.60Ghz Quad)UV,CIFS+UTF-8,PowerHAL,Linux-3.x Hybrid]
by faux123
Ultimate Edition 22
[KERNEL][GPL][N7] franco.Kernel - r75
by franciscofranco
r75
[KERNEL] [ANDROID 4.3] LeanKernel: Minimalistic Kernel [V2.0, 8/2/13]
by azoller1
Version 2
[Kernel][4.2.2] M-Kernel - a61[WiFi/3G]
by Metallice
a61
[KERNEL] [3.1.10] [JB 4.3/4.2.2] [Purified Kernel r130] [Linaro] [07-08-2013]
by eng.stk
r130
[KERNEL] [GROUPER/TILAPIA] [4.2.2/4.3] OXYDO [3.2.49] [Linaro]
by sgt. meow
v7
[KERNEL][Grouper][JB 4.3] 3.1.12-XPerience-04 [12/08/13]
by TeamMex
v4
[KERNEL] Bricked-Kernel Grouper/Tilapia
by show-p1984
4.3 Stock Kernel
I will test another kernel if someone requests me too. I will not post other's results because they most likely have a different setup and therefore different results making it inaccurate.
NEW! 4.3 RESULTS
19/8 UPDATE
PERFORMANCE
Performance was tested with Antutu. Tested three times and averaged.
1.3 RESULTS
Kernels set to 1.3GHz max and used the default governor for the test.
1. M-Kernel: 13489
2. Franco: 13440
3. LeanKernel: 13298
4. Bricked: 13194
5. Oxydo: 13179
6. Xperience: 13139
7. Faux: 13122
8. Purified: 13102
9. Stock: 12903
MAX RESULTS
Kernels set to highest clockspeed, performance governor.
1. Bricked (1.6): 15339
2. Oxydo (1.6): 14938
3. M-Kernel (1.7): 14463
4. LeanKernel (1.5): 14343
5. Faux (1.7): 14155
6. Xperience (1.6):14147
7. Franco (1.3): 13440
8. Purified (1.3): 13102
9, Stock (1.3): 12903
BATTERY LIFE
Default Governor, 100% Brightness
Watching HD 720p Video on a Loop (MX Player Software Decoding) in a 10% range. The reason for this is not to kill my battery lifetime.
Max Freq at stock speed (1.3GHz)
1. M-Kernel:7 hours 5 minutes
2. Oxydo: 7 hours
3. LeanKernel: 6 hours 20 minutes
4. Franco: 5 hours 50 minutes
5. Purified: 5 hours 35 minutes
6. Xperience: 5 hours 30 minutes
7. Faux: 5 hours 10 minutes
8. Bricked: 5 hours 5 minutes
9. Stock: 5 hours
Max Freq set as high as it can go.
1. LeanKernel (1.5): 6 hours
2. Franco (1.3): 5 hours 50 minutes
3. Purified (1.3): 5 hours 35 minutes
4. M-Kernel (1.7):5 hours 25 minutes
5. Oxydo (1.6): 5 hours 10 minutes
6. Stock (1.3): 5 hours
7. Bricked (1.6): 4 hours 55 minutes
8. Xperience (1.6): 4 hours 45 minutes
9. Faux (1.6): 4 hours 40 minutes
OVERALL
Best Performance:
[KERNEL] Bricked-Kernel Grouper/Tilapia
by show-p1984
[Kernel][4.2.2] M-Kernel - a61[WiFi/3G]
by Metallice
a61
Best Battery Life:
[KERNEL] [ANDROID 4.3] LeanKernel: Minimalistic Kernel [V2.0, 8/2/13]
by azoller1
Version 2
Best Overall:
[Kernel][4.2.2] M-Kernel - a61[WiFi/3G]
by Metallice
a61
[URL="http://forum.xda-developers.com/showthread.php?t=1950858"][KERNEL] [ANDROID 4.3] LeanKernel: Minimalistic Kernel [V2.0, 8/2/13]
by azoller1
Version 2
[/URL]
4.3 Results
Nice! This should be a sticky to help reduce unnecessary threads about kernels. My only suggestion would be to run Quadrant 3 times and take the average number. Only because 3 runs will have different results every time
Sent from my Atrix 4.1.1
Best battery life can't really be determined since everyone uses their tablet differently i wouldn't even waste my time.
Sent From My Toro+ via White Tapatalk
I am testing several kernels here. The fastest for me so far is trinity, but the battery is draining really fast. I then tried the 1400 MHz trinity and things got a little better with a good performance in quadrant.
I am testing motley now and seems good but a little slower than trinity. Home screen doesn't look as buttery as in trinity. I will keep testing a little longer.
Sent from my Nexus 7 using xda premium
---------- Post added at 06:19 PM ---------- Previous post was at 05:54 PM ----------
Crap...i just had a reboot while using motley and started playing dead trigger. I returned to trinity 111 and it is definitely smoother than the others for me. Maybe it is because it is the first one i flashed and now when i try others, even wiping, something remains and the other kernels don't work right. Who knows....
Sent from my Nexus 7 using xda premium
ÜBER™ said:
Best battery life can't really be determined since everyone uses their tablet differently i wouldn't even waste my time.
Sent From My Toro+ via White Tapatalk
Click to expand...
Click to collapse
I was going to do a HD video playback test. See how long it lasts on each.
Sent from my Nexus 7 using xda premium
Can't wait for the battery life results!
Sent from my Nexus 7 using xda premium
I posted about the so called battery life screen shot thread in there thread.
the only way to really test battery life is to start with ful ly charged battery each day. 1 TEST PER DAY or charge cycle.
you will have to get a mathematical equation figured out first .it would have to be something like
cpu cycles x screen brightness x memory usage and s on divided by then another equation to determined battery pull watts im guessing
you would have to keep the first exact on each test device to determine the battery life ..
ok while typing this i have decided its way over my head and quite honestly not sure it can be done ..
HELP My brain now hurts ..
The best way to test CPU performance would be to make sure that all kernels are at the same exact core frequency max, and all cores enabled, on performance governor. Performance governor alone doesn't enable all cores, and benchmarks sometimes don't trigger all 4 cores as on either (it can, but not always, and that can lead to totally different numbers on different kernels).
Some kernels have higher max frequencies then others, some use the new CPU quiet driver and some don't (although this wouldn't really matter if all cores are forced on for testing).
Some kernels have higher GPU clocks then others, some have higher refresh rates then others, some have both higher refresh rates and clocks, etc.
Personally, the best way to judge a kernel is by what features are implemented in it for example, is it linaro compiled? Does it use the old hotplug method for CPU cores, or the new quiet driver? Updated WiFi driver? fsync toggle? Was it built with RNDIS drivers?
Quadrant isn't a stable means of benchmarking (run it 3 times in a row and watch those numbers change), but generally speaking, if the same kernel is compiled with linaro, vs no linaro, the linaro build would be faster (don't quote me on this). Not all those kernels are linaro that I'm aware of.
Also, Jay's buttery smooth tweaks, his fsync doesn't work on franco.Kernel. That kernel specifically uses a different command to toggle fsync, and unless that method was used, any I/O results would be void (basically comparing fsync kernels to non-fsync, where fsync would obviously dominate). And there is even the possibility the ROM you were using may interfere with CPU clocks and voltages unknowingly.
So with all that said, trying to find the "best" kernel, is going to take a bit more effort then just benching with Quadrant
And for my own personal opinion (no hard-testing done) I like franco.Kernel Stock clocks and voltage, fsync toggle, new CPU quiet driver and WiFi driver, works awesomely faux's kernel would be my second preferred kernel, only because lack of fsync control, and getting rid of the CPU quiet driver.
espionage724 said:
The best way to test CPU performance would be to make sure that all kernels are at the same exact core frequency max, and all cores enabled, on performance governor. Performance governor alone doesn't enable all cores, and benchmarks sometimes don't trigger all 4 cores as on either (it can, but not always, and that can lead to totally different numbers on different kernels).
Some kernels have higher max frequencies then others, some use the new CPU quiet driver and some don't (although this wouldn't really matter if all cores are forced on for testing).
Some kernels have higher GPU clocks then others, some have higher refresh rates then others, some have both higher refresh rated,
Personally, the best way to judge a kernel is by what features are implemented in it for example, is it linaro compiled? Does it use the old hotplug method for CPU cores, or the new quiet driver? Updated WiFi driver? fsync toggle? Was it built with RNDIS drivers?
Quadrant isn't a stable means of benchmarking (run it 3 times in a row and watch those numbers change), but generally speaking, if the same kernel is compiled with linaro, vs no linaro, the linaro build would be faster (don't quote me on this). Not all those kernels are linaro that I'm aware of.
Also, Jay's buttery smooth tweaks, his fsync doesn't work on franco.Kernel. That kernel specifically uses a different command to toggle fsync, and unless that method was used, any I/O results would be void (basically comparing fsync kernels to non-fsync, where fsync would obviously dominate). And there is even the possibility the ROM you were using may interfere with CPU clocks and voltages unknowingly.
So with all that said, trying to find the "best" kernel, is going to take a bit more effort then just benching with Quadrant
And for my own personal opinion (no hard-testing done) I like franco.Kernel Stock clocks and voltage, fsync toggle, new CPU quiet driver and WiFi driver, works awesomely faux's kernel would be my second preferred kernel, only because lack of fsync control, and getting rid of the CPU quiet driver.
Click to expand...
Click to collapse
Yeah. I know. I'm going to add a other features section. If someone else could do it that would be good. If not, I'll do it later.
Sent from my Nexus 7 using xda premium
bcvictory said:
I was going to do a HD video playback test. See how long it lasts on each.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Who JUST watches video... would be as effective as leaving it on a white screen for hours. Like I said there is no point and would just give false hope.
Sent From My Toro+ via White Tapatalk
Used Motleys 520 at first, probably still my favorite. Used trinity and both of clemsyns latest. Clemsyns elite 1.8 got too hot for my liking, I'm using the 1.5 UV right now and batteries not too great, but its very smooth. Trinity is smooth as well but Motleys 520 seemed to both perform better and give better battery life at comparable clock speeds to the rest.
So Motleys will be my daily, but I refuse to stop flashing!
this is very helpfully
thanx
Hey Guys! I have been running some battery tests over the last week. I'm finishing the results now. Show you guys soon!
Battery Tests are in the OP! Check them out, give your own opinion!
bcvictory said:
Battery Tests are in the OP! Check them out, give your own opinion!
Click to expand...
Click to collapse
Interesting... not what I expected.
They varied so much did you use all the same governor? Stock is interactive. All the same I/O? That is quite a difference a shocking one at that.
Sent From My N7 via White Tapatalk
ÜBER™ said:
Interesting... not what I expected.
They varied so much did you use all the same governor? Stock is interactive. All the same I/O? That is quite a difference a shocking one at that.
Sent From My N7 via White Tapatalk
Click to expand...
Click to collapse
Yeah. I used interactive on all of them. Set the minimum at the lowest it could go and the max as high as it could go on each kernel.
bcvictory said:
Yeah. I used interactive on all of them. Set the minimum at the lowest it could go and the max as high as it could go on each kernel.
Click to expand...
Click to collapse
-_- that's not fair.... nobody uses the absolute high... redo... at stock frequency.
You can't tell which is best if they are not under the same circumstances. Obviously Franco is top because his only goes to 1.3 which is stock. While others are over clocked... thats unreliable.
Sent From My Toro+ via White Tapatalk
ÜBER™ said:
-_- that's not fair.... nobody uses the absolute high... redo... at stock frequency.
Sent From My Toro+ via White Tapatalk
Click to expand...
Click to collapse
All of them at 1.3GHz Max? Whats the point of overclocking then?
bcvictory said:
All of them at 1.3GHz Max? Whats the point of overclocking then?
Click to expand...
Click to collapse
For benchmarks... not battery performance.
So your telling me the benchmarks where at different frequencies too? Wow have you never done a science expierenment? You don't test under different variables... that's inconsistent.
That's like frying an egg at 100F and comparing it to frying it at 120F. Obviously the 120F will fry faster. Cmon man.
Sent From My N7 via White Tapatalk
ÜBER™ said:
For benchmarks... not battery performance.
Sent From My N7 via White Tapatalk
Click to expand...
Click to collapse
Yeah. I guess... I was going to try Motley at 1.3 for fun anyway. See how I do...
What kind of success/failure are people having with overclocking and undervolting?
I'm doing this through ROM Toolbox Pro. Is there a better way? I'm a n00b with some of this stuff.
I have the phone overclocked to 1200mhz and all cpu levels are undervolted by 100mV.
Im doing so to get more performance, and better battery life. Just wondering what settings everyone else is using.
Also I'm using CM 10.1, with the BlueMint Theme.
Sent from my Samsung Captivate/JB CM 10.1 via Tapatalk.
DR650SE said:
Just wondering what settings everyone else is using.
Click to expand...
Click to collapse
Every phone has different limits. It's just like PC overclocking, no two CPU/MB/RAM combos are exactly the same. In general most of Captivates will handle 1200 step OC with default voltages. Not too many will handle 120% live OC though. It doesn't matter what tool you use to OC. All tools try to play with the same kernel settings. In my experience UV saves very little battery but increases significantly the chances to get stability issues. This is why I never play with UV. My particular phone can do 1400 step OC or 1200 live OC with 1350mV. I run it on 1200 step OC @ default. Also, keep in mind that different ROMs/kernels give different OC results.
RE: undervolt
I agree with Val D that undervolting will not show any significant benefits. Overvolting has helped me with stability while overclocking. I use the free Voltage Control app for voltages, or the free NStools app. Rom Toolbox is a great app too- I use it for many other things- stick with what works for you. Currently I am running at 1200Mhz step, at 120% Live OverClock to get CPU up to 1440Mhz, and ARM voltage of 1350mV at that 1200Mhz step. Rock solid. Battery life suffers a bit, but I run this way for gaming. Day-to-day regular usage I just set to 1400Mhz step and no Live OC, default voltages. I have run fine in the past at 1500Mhz, no Live OC. Overclocking the CPU tends to make my phone a bit snappier and more responsive. A big battery drain that affects my phone is an app such as Gmail running in the background, or leaving wifi enabled when not in use. Setting the phone to Airplane mode has been a big battery helper too (I do not make any voice calls on this phone anymore). Governor and scheduler setting can also have a big effect on battery life. I searched for this post I made a while back that linked to two great articles on studies of battery life and voltages, and ended up reading through them again:
http://forum.xda-developers.com/showpost.php?p=28141250&postcount=1194
Great information. Edit: just figured out how to link articles in my signature.
Thanks guys. I know each one over clocks differently. Just looking for some rough outlines. Thanks for the links. I'll be reading up on those. I have extensive computer over clocking experience, but on e phone its a whole new ball game. Basically trying to make this phone last longer.
I'll have to learn what live OCing is vs step OCing.
Thanks again!
Sent from my GT-P3113 using Tapatalk HD
I just do 1200mhz OC using CyanogenMod 10.1 - the option is in the performance menu. So far no problems.
PxGold said:
I just do 1200mhz OC using CyanogenMod 10.1 - the option is in the performance menu. So far no problems.
Click to expand...
Click to collapse
Awesome. Didn't even realize that as there. I've been using ROM Toolbox to OC to 1200MHz.
Sent from my Samsung Captivate/JB CM 10.1 via Tapatalk.
overclocking to 1200 mhz will made any difference ?
Klitoni said:
overclocking to 1200 mhz will made any difference ?
Click to expand...
Click to collapse
I really didn't notice much of a difference in speed or responsiveness using CM 10.1.
Please suggest a way to maximize battery life while sacrificing performance(not too much of course).
I tried out various roms, one is problemish over another.
Kernels as well.
I'm on my 3rd full charge on my 3rd day of phone purchase so the battery should have regulated a little.
I tried AOSP by cile and the experience is great but not the battery, overnight 7 hours I dropped 27% of battery.
(greenify on + underclock to 1000mhz + pm.sleep_mode = 1)
Do recommend me a combo best for battery life.
(one needs a stable platform to stand on before moving on to development right?)
Ararargi CM 20130707 + Iodak v6 Kernel.
Trickstermod: CPU Quiet: Userspace
Max CPU Clock:760Mhz
Min CPU Clock: 102Mhz
Scheudler: SIO
FSYNC: Disable
Intelligence Dimmer: Enable
Fast Charge: OFF
Multi Prozessor Engery Saving: Disable
Here my Under volt Values:
The charge insane Fast. In 10 Min 10-15%.
The Phone drain is 1% pro 3Min (less us)
2 % pro 3Min (heavy use)
LG 4X HD - Better than a Smartphone
KiD3991 said:
Please suggest a way to maximize battery life while sacrificing performance(not too much of course).
I tried out various roms, one is problemish over another.
Kernels as well.
I'm on my 3rd full charge on my 3rd day of phone purchase so the battery should have regulated a little.
I tried AOSP by cile and the experience is great but not the battery, overnight 7 hours I dropped 27% of battery.
(greenify on + underclock to 1000mhz + pm.sleep_mode = 1)
Do recommend me a combo best for battery life.
(one needs a stable platform to stand on before moving on to development right?)
Click to expand...
Click to collapse
Cm 10.1 and eternitys kernel, underclocked to 1,3ghz. Really good performance and battery, i do recommend using nova launcher to, because cms stock trebuchet launcher is kinda laggy
Sent from my LG-P880 using xda app-developers app
Nemeziz 56th said:
Ararargi CM 20130707 + Iodak v6 Kernel.
Trickstermod: CPU Quiet: Userspace
Max CPU Clock:760Mhz
Min CPU Clock: 102Mhz
Scheudler: SIO
FSYNC: Disable
Intelligence Dimmer: Enable
Fast Charge: OFF
Multi Prozessor Engery Saving: Disable
Here my Under volt Values:
The charge insane Fast. In 10 Min 10-15%.
The Phone drain is 1% pro 3Min (less us)
2 % pro 3Min (heavy use)
LG 4X HD - Better than a Smartphone
Click to expand...
Click to collapse
jonteftw1 said:
Cm 10.1 and eternitys kernel, underclocked to 1,3ghz. Really good performance and battery, i do recommend using nova launcher to, because cms stock trebuchet launcher is kinda laggy
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
Thanks you two.
I will test both out and compare! Then will report the best out of which.
I use SuperXE ROM with iodakv6 - heavily undervolted using TricksterMod.
Governor: Interactive
IO Scheduler: SIO or ROW
stock rom and iodak kernel. Using systemcleanup I converted maps, weather, lg keyboard etc to user apps and then greenify almost everything. Also a little undervolting and I see great battery life and performance.