Related
Does anyone know how to over clock you're DI to say 1.2? Thanks for any help.
You first need to root your phone, then install a kernel that is compatible with whatever rom you are using, then you need to install an OCing app like SetCPU and adjust accordingly.
I'm rooted running the 2.2 RUU and I have set cpu. So do I just need a kernal? Which one?
i reccomend King Kernel bfs #4, best freaken kernel ever... its located... here
so when i install this kernal is it ok to just bump the cpu speed up to 1.2? are there any guides to do this?
makos101 said:
so when i install this kernal is it ok to just bump the cpu speed up to 1.2? are there any guides to do this?
Click to expand...
Click to collapse
A lot of factors come into play when you start overclocking, every rom will respond differently.
The first thing to do before anything is to do a complete nandroid back up.
When overclocking keep in mind that the more you overclock the more chances you have of making your system unstable.
I have experimented a quite a bit and I have found that the King Kernal #4 seems to work well for me and at 1.2 it seems to be pretty stable. Any higher than that and my phone will sometimes re-boot itself for no apparent reason.
Again, your rom may handle things different so experiment and see what works best for you.
And remember - Do a complete backup first!
I'm using the number 4 kernal and it only goes to 1.19 is this what you mean by 1.2? I have to keep mine at 1.1 ghz at 1.19 my di gets unstable
Ya that's as high as they can oc these chips. I can only get to 115 safely 119 just crashes. But the charging experience will be better than stock with the BFS #4.
Sent from my ADR6300 using XDA App
Could you guys please tell me what your settings for setcpu are?
I want better battery life and a faster cpu but im noticing that my phone almost needs a wake up time when i come out of screen off.
Thanks so much
makos101 said:
Could you guys please tell me what your settings for setcpu are?
I want better battery life and a faster cpu but im noticing that my phone almost needs a wake up time when i come out of screen off.
Thanks so much
Click to expand...
Click to collapse
If you are experiencing slow wake up, try increasing the min cpu speed to something around 460. Better batt life and increased speed takes a lot of experimenting. Your OC speed might differ from others due to differences in the phones cpu. For example, I have never been able to oc to 1.19 without the phone freezing or rebooting. My phone can handle 1152 but 1113 is perfect. In my opinion, ROMs have something to due with best batt-speed combo. I am running Ruby 1.1.1 with a setcpu profile of Screen off=245 without any wake lag. Other ROMs I have tried had wake up lag at that speed profile.
My set up:
(ROM-ASOP) Ruby 1.1.1
King's #1 ASOP "I told you so"- only works with ASOP
With the ROM's "Gem" performance scaling setting off, I use setcpu to OC to 1113, min is 245. I have a profile set to SCREEN OFF = 384 max/245 min.
I haven't worried about battery life since I started using King's kernals (I've tried them all with every compatible ROM on xda). I have several posts elsewhere on XDA showing 12 plus hours on a single bump charge and heavy phone use. Good enough for me. Stock cpu speed plus Sense ROM seems slow to me now.....to each his own though.
I hope to get some help because i value the opinions of those on this forum. Currently i am running virtuous 2.7 with virt. kernal v2. I am rooted, s-off, 2.15.xx radio. I want performance without draining my battery. What are the best settings to use in setcpu?
I did try king's kernal #4, but it was rebooting. switched kernals this morning.
One other app I use in conjunction with SetCPU is MinFreeManager. This will readjust your free ram to a higher standard. But with SetCPU I have it at 1113/Ondemand with no custom profiles. One other thing I really don't set is the Set on Boot option. I don't know why but I do. So with SkyRaider Vanilla 3.0 RC3/ KingX Kernel #4/ and MinFreeManager my phone fly's. I can't say for certain what settings you need for your phone but 1113-1115 is preferred by "most" phones and keep the set on boot option off. I keep a Galaxy S live wallpaper running and pandora while browsing the web and no lag what-so-ever.
CyanogenMod 6.0.2 and KingX kernel #1 with the same setup runs almost as smooth.
Hope this helps you out.
I am currently using MIUI 1.7.29 Osimood with the Tiamat 1.04 kernel, and I am wondering what the best kernel is for battery life. I am also using the V6 supercharger ram script. I am running my CPU at 960mHz at the moment, using the smartass governer. I also undervolted using vipermod, 960MHz at 950mV.
My choice consists of the latest Pershoot, UmaroKernel 1.06 or Tiamat 1.04
What differences would I see between those kernels, are they noticeable for a regular user?
Sorry man, but wehre do you find the vipermod for desire z? http://vipermod.tiamat-dev.com/faq.php it's not compatibile with desire z/g2....
Uh...what's wrong with the kernel it comes with? Can OC to 1.5GHz stock ya know. Battery life is great with it too. People always want to flash something weather it be a radio or a kernel.
Sent from my HTC Desire Z using XDA Premium App
Spastic909 said:
Uh...what's wrong with the kernel it comes with? Can OC to 1.5GHz stock ya know. Battery life is great with it too. People always want to flash something weather it be a radio or a kernel.
Sent from my HTC Desire Z using XDA Premium App
Click to expand...
Click to collapse
Isn't flashing stuff and trying new things basicly the point of this whole site?
ostinq said:
Isn't flashing stuff and trying new things basicly the point of this whole site?
Click to expand...
Click to collapse
damn straight,
1) pershoot is a sense kernel? (i am proabably wrong but i have never tried this kernel)
2) umaro kernel i found had issues with wifi, high underclock freq (leading to poorer battery life), but fun if you have the time to tweak voltages and fast!
3) tiamat kernel i found had issues with sleep of death/random reboots on wakeup couldnt test it past that. (setcpu was set to screen off was: conservative 125min -345 max and would still crash)
if you are up for another kernel, i am now using this kernel (streamline5)
no voltage tweaking (pretweaked) but it has good batt, speedy and stable cant ask for much
http://forum.androidspin.com/showthread.php/6555-Streamline5-Nightly-CM7-Test-Kernel-2.6.35.13
lalalandrus said:
damn straight,
1) pershoot is a sense kernel? (i am proabably wrong but i have never tried this kernel)
2) umaro kernel i found had issues with wifi, high underclock freq (leading to poorer battery life), but fun if you have the time to tweak voltages and fast!
3) tiamat kernel i found had issues with sleep of death/random reboots on wakeup couldnt test it past that. (setcpu was set to screen off was: conservative 125min -345 max and would still crash)
if you are up for another kernel, i am now using this kernel (streamline5)
no voltage tweaking (pretweaked) but it has good batt, speedy and stable cant ask for much
http://forum.androidspin.com/showthread.php/6555-Streamline5-Nightly-CM7-Test-Kernel-2.6.35.13
Click to expand...
Click to collapse
Pershoot is actually for non-sense roms. The downfall people have with it is lack of governors. Some don't mind, some want variety. I've had great experiences with Pershoot's kernel and it's the baseline that all others are compared to (not to mention the foundation of almost ALL G2/DZ kernels).
Umaro's just needs to have voltage tweaks done manually but on the plus side - keeping the voltages normal (not UV) allows some people to reach higher OC speeds. It keeps the processor from bottoming out due to insufficient voltage which can easily happen when you UV. The main issue is with the Greased lightening governor - it's new and still a bit buggy.
Tiamat 1.0.4 is outstanding. I can sit all day at 2+ GHz (not literally, see: Chernobyl). I personally have an issue with the interactive governor but other than that it's my favorite kernel (Umaro may take that soon, once greased lightening is perfected).
Basically you just need to try out a few and see which you like. There is no 'best'. Most kernels will work with any ROM (Sense being the only exception).
Bumping a thread that is relevant to my interests.
It's about time for me to jump ship from an outdated CM ROM and try something new like a MIUI ROM.
With that said, I'd like to read more opinions & experiences from people using the various Kernels AND how the latest radio (the one released today) is working for them. I'm just trying to get the optimal experience here
Speaking of MIUI would anyone mind telling me some differences between OsiMood's ROM compared to the official MIUI-US ROM (or even DarkSpadez ROM)?
Thanks a ton guys!
I downloaded the official rom . . .then ignored it downloaded osimood and iv been using it since. Osimood is a lighter rom, which is always a good thing, unwanted languages etc are removed for a smaller faster rom. Also he preinstalls tweaks like an adblocker and extended settings mod.
Kernal wise iv been looking for the same info as you but couldn't find it. So I eneded up trying them all:
- Eugenes streamline5 is a nice kernal, preundervolted. Only probly is its not being updated so will become redundant.
-Tiamats kernal allows over clock to 2ghz and seems to support higher overclocks stably where other kernals can't. Except battery life has decreased with recent kernals
-Umarokernal this is the kernal iv come back to twice and am still on. It allows overclock to 1.9ghz and is kept updated by umaro. Performance per frequency seems as good if not better than most and osimoods miui runs smooth with this kernal on 800ghz with scarey governer (which saves battery) Another plus for me with this kernal is the scarey governer which for me definatly provides the best performance per battery ratio.
I'm currently running MIUI 1.8.5 with Eugene-Streamline 5 Kernel with the latest radio update Vision_Radio_12.57.60.25_26.10.04.12.
SetCPU with Governor ondemand provides me with better usage, power and responsive time then Smartass or Interactive.
OC to 1.2ghz
Battery life, about 30hrs with the regular 1350mah.
Screen cap
fluxgfx said:
I'm currently running MIUI 1.8.5 with Eugene-Streamline 5 Kernel with the latest radio update Vision_Radio_12.57.60.25_26.10.04.12.
SetCPU with Governor ondemand provides me with better usage, power and responsive time then Smartass or Interactive.
OC to 1.2ghz
Battery life, about 30hrs with the regular 1350mah.
Click to expand...
Click to collapse
i just got 40 hours with similar setup but i use virtuous o/c daemon instead of setcpu
big fan of streamline5 and hope that it will get updated eventually
How do you get the virtuos o/c daemon?
maxietheboss said:
How do you get the virtuos o/c daemon?
Click to expand...
Click to collapse
Its basically like an automatic setcpu (which can't be changed on the fly) built into the rom, its in virtuous unity roms
What sleep profiles are you guys usein. I seem to have rebooting issues with any kernel I try unless I go to a sense rom. I've tried the vipermod now to see how it goes
Sent from my T-Mobile G2 using XDA App
But how do you get the virtuos O/C daemon to work on MIUI?
You can download it threw rom manager. Even with that kernel I get reboot issues. I assume its cause system ram isn't being cleard fast enough. I'm gonna try 100mv increase to see if there's a difference.
Sent from my T-Mobile G2 using XDA App
Hi guys,
I'm a bit of a noob so please bear with me. I recently rooted my phone (SGH-I747M Telus), I have CWM recovery installed. I was interested in overclocking so I installed this kernel on my stock rooted rom (I installed the "sammy" one). I also cleared the delvik cache, cache, and fixed permissions before rebooting. Now I'm having a weird problem with video playback. I get these bleep like sounds, like you might hear on a spaceship, lol. The normal audio plays in addition to these sounds. Yet, regular audio plays fine (mp3s), same with youtube. So, my question is, why? Is there any way of fixing this? I'd rather not play around the stock ROM. I made a backup before doing anything and recently tried to restore the boot, but I got an invalid md5 check.
-JC
Okay, I was able to fix my problem by flashing the stock at&t kernel... but I would still like to be able to overclock... is there another kernel that I can try or a way to fix the problem with the kernel I already tried? Thanks.
If you still want to try previous kernel your problem might be because of heavy undervolting , kernel creator posted this voltage chart.
You can experiment by increasing voltage and see if that helps.
Or you can just try this faux kernel , its pretty good also, we don't have many kernel choices for Samsung based roms at this early development cycle.
ghost77 said:
If you still want to try previous kernel your problem might be because of heavy undervolting , kernel creator posted this voltage chart.
You can experiment by increasing voltage and see if that helps.
Or you can just try this faux kernel , its pretty good also, we don't have many kernel choices for Samsung based roms at this early development cycle.
Click to expand...
Click to collapse
Thanks for the reply... but I was able to fix the problem. It was something wrong with the settings of SetCPU which I installed earlier. I changed it from on demand to performance and now all is well. Now I have a question about battery life. Will overclocking drain battery a lot faster? I imagine it would only make a difference if I was doing CPU intensive things.
JustChillin1414 said:
Thanks for the reply... but I was able to fix the problem. It was something wrong with the settings of SetCPU which I installed earlier. I changed it from on demand to performance and now all is well. Now I have a question about battery life. Will overclocking drain battery a lot faster? I imagine it would only make a difference if I was doing CPU intensive things.
Click to expand...
Click to collapse
Well.. performance setting makes it so that your CPU runs 100% all the time. I don't think that will be battery friendly . Overclock generally uses more power and battery longevity will depend on your usage.
You can try messing with setcpu settings. Try Conservative, then limit minimum speed to 384 and max to your preference. Try your movie again.
Current kernels and setcpu are a bit quirky.
I had the same issues on ktoonsez Sammy. Ended up back at stock AT&T. I've heard it's an issue with many of the kernels but a fix is on the way. Couldn't find a way to get rid of it, but that's not to say it can't be done. Don't have much time to tinker right now.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Its a known issue on ktoonsez kernel. Flash faux's kernel, it has the same features (as well as GPU OC) and doesn't have the audio issue.
So I have found that recently every kernel I try to over clock with will cause bad performance on my phone. I am judging this based on benchmarks which should improve when you over clock (I know benchmarks aren't everything, just using them to compare). Every time I over clock to 1.89 it automatically reboots no matter what kernel or rom I am running. No one else in the kernel thread has this issue. If I run benchmarks with the max clock anything above the stock 1.5Ghz makes my benchmark performance absolutely drop. I have tried:
-multiple kernels and ROM combinations
-multiple CPU managers (ROM toolbox to CM performance control)
-multiple bench markers
Did I somehow destroy my CPU on higher clocks somehow?
And I know I don't need OC for good performance, I am just wondering what's up here. It wasn't always like this.
It's not necessarily anything you did. Not all devices are created equally. Some phone can run at 2.1GHZ and get amazing battery life. You just got dealt a bad phone that doesn't over clock well.
Sent from my SAMSUNG-SGH-I747 using xda premium
Yes, if you go over 1890Mhz your phone will restart or get stuck in a bootloop. As the person above said is right. Some phones can go up to 2000MHz and some can't. My Gs3 can overclock to 1890 but I keep mine at 1809.
1. Benchmark apps have no use at all.
Its literally just numbers thrown at you. They have no reflection on real world performance.
2.No one phone is the same. Your phone maybe able to go up to 1.8 with out an issue, but other phones might not even make it past 1.7 I even know of a GS3 that runs at 2.1Ghz with out a problem.
3.OC isn't really needed on an S3 if you're having lag issues or anything Odin back to stock and start again.
I personally run my S3 at 1.1Ghz.
I use custom kernels to under clock and not over as over clocking can drain your battery. Your phone will always reboot past 1.8 regardless of the kernel. That's just how your phone works.
Galaxy S3 / AoCP / V4A / Turbocharged
I have a S4 mini running custom carbon kk unofficial 4.4.3 as it comes with the settings to set CPU's and governors but the phone keeps changing the min to around 1400 but the max stays at 1700.i don't notice until my battery is draining really fast or gets hot. anyone kno a fix to this?
matizkool said:
I have a S4 mini running custom carbon kk unofficial 4.4.3 as it comes with the settings to set CPU's and governors but the phone keeps changing the min to around 1400 but the max stays at 1700.i don't notice until my battery is draining really fast or gets hot. anyone kno a fix to this?
Click to expand...
Click to collapse
Which governor is it using to set a min of 1400? Ever likely it gets hot and eats power! I use f4k's kernel, and the 'Performance Control' app to look at and alter stuff - you don't say what you use or have tried.
There is a Carbon 4.4.4 available with f4ktion 1.5 kernel - might be an idea to flash that and the problem might go away!
xbin said:
Which governor is it using to set a min of 1400? Ever likely it gets hot and eats power! I use f4k's kernel, and the 'Performance Control' app to look at and alter stuff - you don't say what you use or have tried.
There is a Carbon 4.4.4 available with f4ktion 1.5 kernel - might be an idea to flash that and the problem might go away!
Click to expand...
Click to collapse
It's on every governor this happens but I use Wheatley. I would manually set it to around the 300s but in a couple of hours it would auto set at 1400 on its on. This causes my battery to drain my kernel version is 3.4.91 f4ktion 1.4.5 eur lte
matizkool said:
It's on every governor this happens but I use Wheatley. I would manually set it to around the 300s but in a couple of hours it would auto set at 1400 on its on. This causes my battery to drain
Click to expand...
Click to collapse
Strangely enough I've settled with Wheatley too! but it spends most of its time at 162 when not in deep sleep (a bit like me!). This really needs posting in the Carbon thread so I would post a few more things here to help or comment on stuff to get to 10 posts and then ask in there. I can't think what could be causing that behaviour, if it was me it would be bye bye 4.4.3 and hello 4.4.4
xbin said:
Strangely enough I've settled with Wheatley too! but it spends most of its time at 162 when not in deep sleep (a bit like me!). This really needs posting in the Carbon thread so I would post a few more things here to help or comment on stuff to get to 10 posts and then ask in there. I can't think what could be causing that behaviour, if it was me it would be bye bye 4.4.3 and hello 4.4.4
Click to expand...
Click to collapse
Yeah i flashed to 4.4.4 thanks though
Never mind above still happens even though I flashed 4.4.4
matizkool said:
Never mind above still happens even though I flashed 4.4.4
Click to expand...
Click to collapse
Does the actual minimum change rather than it simply running continually at 1400+ and if so which governor does it change to if any!
I read somewhere in the Carbon thread someone was having similar problems so they flashed the kernel twice, one directly after the other; seems something wasn't getting written correctly the first time but was the second, and the problem went away. Worth a go...
xbin said:
Does the actual minimum change rather than it simply running continually at 1400+ and if so which governor does it change to if any!
I read somewhere in the Carbon thread someone was having similar problems so they flashed the kernel twice, one directly after the other; seems something wasn't getting written correctly the first time but was the second, and the problem went away. Worth a go...
Click to expand...
Click to collapse
I found this : Q: CPU/GPU frequency doesn't stick?
A: If your frequency settings don’t stick, it's because on certain Qualcomm or JB and higher devices, there are certain system services (thermald/mpdecision/project butter) or kernel feature that rewrite frequency settings based on current thermal status and/or touch input. Certain custom kernels for your device should include work around for these issues.
Is this a fix?
matizkool said:
I found this : Q: CPU/GPU frequency doesn't stick?
A: If your frequency settings don’t stick, it's because on certain Qualcomm or JB and higher devices, there are certain system services (thermald/mpdecision/project butter) or kernel feature that rewrite frequency settings based on current thermal status and/or touch input. Certain custom kernels for your device should include work around for these issues.
Is this a fix?
Click to expand...
Click to collapse
It could help. Trickster is good. However, this suggests that there is something else causing or forcing the frequency setting to be changed. The question is what? and I've no idea:crying:
Haha I found the problem it was either this battery saver app or I changed to scheduler to anything besides row
matizkool said:
Haha I found the problem it was either this battery saver app or I changed to scheduler to anything besides row
Click to expand...
Click to collapse
Thats good. It was probably the battery saver because they usually do the opposite!