Develop Bugs

How do you over clock?

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.

[Q] Sound skipping during playback - BlackIce ROM

Hi. I'm using BlackICE ROM and I came across one, major for me, issue. I mean, sound skipping during unlocking device, turning on the screen, opening maps. It happens randomly. Other roms are fine.
I'm using PowerAmp Beta3. But it happens also with MusicMod, GoogleMusic and many others.
Any sollutions yet? I really want to stick with this rom, cause it's the best so far for me.

The only time I have ever experienced similar issues is when I had the screen-off CPU frequency set too low. Increasing it a little stopped the skipping and made the device fast and snappy on wake / unlocking again.
What kernel and governor do you use, and do you use any scripts like Killersloth etc?

I used LordModUE V8 kernel and interactiveX governor. I used setCPU and set CPU to 1.5 ghz
Too bad, that music skipping was happening with screen-on, during normal use. I mean, reading text msgs, browsing. And it happened randomly. On hydrogenmod i haven't experienced anything like this. only on blackice.

Oops, I just hit thanks instead of quote so make sure you do something nice for someone today
Back to your issue... in that case I'm not sure. It shouldn't be happening with screen on that's for sure. Sometimes a full wipe and reflash of the ROM can fix any problems, so that would be my first suggestion. If that doesn't fix it then maybe try some different kernels... like older versions of LordMod or whatever other kernels are popular for CM7 based ROMs (I'm not really familiar myself as I use Sense based ROMs).
Edit to say you could also try Ondemand governor, I find that has best results

Tried many different governors. But the problem was swill there. But the problem is over since i started using unity rom thanx for help! and for thanks ;p

No problem! Glad you got it sorted

Overclocking Instability

Hey I just bought a 32 GB Gnex and got it yesterday but it seems to be unstable at anything above the stock max frequency of 1230 MHz. I've tried Paranoid Android and last night's CM10 nightly and they would both freeze and immediately reboot upon setting it to 1305 MHz. I then flashed the Zen kernel on top of CM10 and I like that it can go up to 1.8 GHz but whenever I set anything beyond 1.23 GHz it starts to lag for about 1-3 seconds. When I knock it back down to 1.23 GHz everything is fine again.
This is the first OMAP device I have since I had the OG Droid back in 09, I loved how they were extremely overclockable and I'm going to be pretty sad if mine has to stay at stock speeds. I've tried using JRummy's ROM Toolbox Pro and the built in Performance settings to try and set the frequencies but it doesn't seem to make a difference on which one I use. I've been using the OnDemand and Interactive(x) Governors.
Is this a known problem or am I alone on this?

some CPUs have a higher tolerance than others for overclocking. looks like you got one of the super low tolerance ones.

I hope that's not the case :-/

brando56894 said:
Hey I just bought a 32 GB Gnex and got it yesterday but it seems to be unstable at anything above the stock max frequency of 1230 MHz. I've tried Paranoid Android and last night's CM10 nightly and they would both freeze and immediately reboot upon setting it to 1305 MHz. I then flashed the Zen kernel on top of CM10 and I like that it can go up to 1.8 GHz but whenever I set anything beyond 1.23 GHz it starts to lag for about 1-3 seconds. When I knock it back down to 1.23 GHz everything is fine again.
This is the first OMAP device I have since I had the OG Droid back in 09, I loved how they were extremely overclockable and I'm going to be pretty sad if mine has to stay at stock speeds. I've tried using JRummy's ROM Toolbox Pro and the built in Performance settings to try and set the frequencies but it doesn't seem to make a difference on which one I use. I've been using the OnDemand and Interactive(x) Governors.
Is this a known problem or am I alone on this?
Click to expand...
Click to collapse
you need to disable smart reflex mpu if you want to overclock. smart reflex doesnt know overclocking, so it sets your voltages to low for an overclocked cpu. thus, instant instability.
to disable smart reflex manually, use a terminal emulator. type su(press enter) then type these 3 lines and press enter after each..
*
echo "0" > /sys/kernel/debug/smartreflex/sr_mpu/autocomp
0 to disable, 1 to enable.
btw, some cpu control apps give you options to disable/enable smart reflex.

What three lines? I only see one...
I echo'd a value of "0" to the file but it was still unstable at 1.8 GHz, haven't tried lower frequencies yet, I don't have to reboot after setting the value, correct?
edit: still unstable at 1.42 GHz, also what apps would those be that allow this? Antutu CPU Master Pro only has an option to disable PerfLock.

the way to overclock is to keep moving in small increments upward and burn testing them to check for stability. Don't go straight for a 50% overclock. move up and find your threashold, and when you do start tweaking to see if you can slowly creep beyond that

brando56894 said:
What three lines? I only see one...
I echo'd a value of "0" to the file but it was still unstable at 1.8 GHz, haven't tried lower frequencies yet, I don't have to reboot after setting the value, correct?
Click to expand...
Click to collapse
The 3 lines would be:
Code:
echo "0" > /sys/kernel/debug/smartreflex/sr_mpu/autocomp
echo "0" > /sys/kernel/debug/smartreflex/sr_core/autocomp
echo "0" > /sys/kernel/debug/smartreflex/sr_iva/autocomp
Frankly, though, don't expect 1.8GHz to be stable.

Your particular device's components might not hold it together with that oc.
Sent from my i9250

Darunion said:
the way to overclock is to keep moving in small increments upward and burn testing them to check for stability. Don't go straight for a 50% overclock. move up and find your threashold, and when you do start tweaking to see if you can slowly creep beyond that
Click to expand...
Click to collapse
Yea I know (I used to OC the CPU on my PC), I just wanted to go for something big to see if it could handle it.
Edit: seems to be stable at 1.4 GHz, I'm going to keep increasing it to see what the limit is. I'm assuming i'd have to turn off smartreflex on each boot so I should probably put it in a script in /etc/init.d correct?

brando56894 said:
What three lines? I only see one...
I echo'd a value of "0" to the file but it was still unstable at 1.8 GHz, haven't tried lower frequencies yet, I don't have to reboot after setting the value, correct?
edit: still unstable at 1.42 GHz, also what apps would those be that allow this? Antutu CPU Master Pro only has an option to disable PerfLock.
Click to expand...
Click to collapse
the trinity kernel toolbox lets you disable/enable smart reflex. plus, extremely few gnex will oc to 1.8ghz. and on top of that, to oc even to 1.4 or 1.5ghz, youll need to adjust your voltages to get yourself stable. every device likes different voltages.

I had it stable at 1.4, 1.5, 1.6, 1.7 and told my GF that I could OC it now (because I told her before that I didn't think I could) ...and then it froze rock solid lol

brando56894 said:
I had it stable at 1.4, 1.5, 1.6, 1.7 and told my GF that I could OC it now (because I told her before that I didn't think I could) ...and then it froze rock solid lol
Click to expand...
Click to collapse
i can oc my gnex(using trinity kernel) to 1.803ghz.. but to use stable for every day, 1.689ghz is a good speed for my device. a majority of devices wont even oc that high and stable. stable being the key word.

brando56894 said:
I had it stable at 1.4, 1.5, 1.6, 1.7 and told my GF that I could OC it now (because I told her before that I didn't think I could) ...and then it froze rock solid lol
Click to expand...
Click to collapse
I'd find it surprising that you got 4 different overclock levels stable in 30 minutes. There's a difference between "it boots", "it boots and runs some apps", and "stable".

brando56894 said:
I had it stable at 1.4, 1.5, 1.6, 1.7 and told my GF that I could OC it now (because I told her before that I didn't think I could) ...and then it froze rock solid lol
Click to expand...
Click to collapse
Is she impressed by your turbo-nerd status?! :silly:

Haha she was an iSheep but I made her get an SGS3 and I turned her into an Android geek, now she flashes ROMs on her own lol
Cilraaz said:
I'd find it surprising that you got 4 different overclock levels stable in 30 minutes. There's a difference between "it boots", "it boots and runs some apps", and "stable".
Click to expand...
Click to collapse
Yea it wasn't stable in the true sense of the word, I meant it just didn't freeze every minute or so.
Sent from my Galaxy Nexus using Tapatalk 2

I'm running the 11/4 build of Paranoid Android with v3.0.51-ZenSeries v4 Tuna and I having problems setting CPU frequencies via Trinity Kernel Toolbox. The frequency will stick until I switch to another app, then when I come back to the app it will be at the stock max frequency. I am also unable to use the built in frequency tuner when using TKT.
I've tried stress testing it with stability test and even when the frequencies will stick in TKT (ex. 1.4 GHz) Stability Test will report that its at 1.1 GHz. WTF is going on here? I have all three of the smart reflex values disabled.

brando56894 said:
I'm running the 11/4 build of Paranoid Android with v3.0.51-ZenSeries v4 Tuna and I having problems setting CPU frequencies via Trinity Kernel Toolbox. The frequency will stick until I switch to another app, then when I come back to the app it will be at the stock max frequency. I am also unable to use the built in frequency tuner when using TKT.
I've tried stress testing it with stability test and even when the frequencies will stick in TKT (ex. 1.4 GHz) Stability Test will report that its at 1.1 GHz. WTF is going on here? I have all three of the smart reflex values disabled.
Click to expand...
Click to collapse
dont use PA cpu settings. do you have any other cpu control apps installed? make sure theres nothing enabled in PA cpu settings, nothing. then reboot. wait 2-3 after bootup then open tkt and try using it. is the problem still there?

It seems to be sticking now for the moment, but I haven't had anything in PA CPU settings before I rebooted anyway. I do not have any other CPU OC apps installed either. Stability test is reporting the correct frequency also. Thanks.

brando56894 said:
It seems to be sticking now for the moment, but I haven't had anything in PA CPU settings before I rebooted anyway. I do not have any other CPU OC apps installed either. Stability test is reporting the correct frequency also. Thanks.
Click to expand...
Click to collapse
sweet.
if you were checking before 3 minutes after bootup, then that was the issue. whatever it was, lets hope it doesnt come back.

I was setting the values after the phone had been up for hours, idk what the problem was :-\q

[Q] GNex Reboots when running certain apps

I'm currently running PA 3.6 and the AK Diamond kernel. 99% of the time, everything works fine, however when I start running Puzzle & Dragons, the phone gets really hot and more often than not will reboot before I finish playing. I have also tried using the AK Kubo (stable) kernel, and it does the same. I'm kind of a noob so I don't tweak the kernel settings very much, and I don't really know how to go about fixing this. One thing to note is that on the stock PA 3.6 kernel the phone still gets really hot but it won't reboot. I'd like to keep using the AK kernel as it makes my phone run really smoothly but I would also like to try and fix this problem.

The sole common point to that whole story is Puzzle and Dragons.
a manta wrote this.

beekay201 said:
The sole common point to that whole story is Puzzle and Dragons.
a manta wrote this.
Click to expand...
Click to collapse
Are you saying that AK kernel and P&D just don't get along? Because although it gets hot, on PA 3.6 with its stock kernel it won't forcibly reboot my phone like it does with AK. I've found a temporary workaround which is to switch the governor to powersave while playing...but that doesn't really fix the issue...

AkutsuX said:
Are you saying that AK kernel and P&D just don't get along? Because although it gets hot, on PA 3.6 with its stock kernel it won't forcibly reboot my phone like it does with AK. I've found a temporary workaround which is to switch the governor to powersave while playing...but that doesn't really fix the issue...
Click to expand...
Click to collapse
No, it's just the kernel that doesn't "like" your cpu.

beekay201 said:
No, it's just the kernel that doesn't "like" your cpu.
Click to expand...
Click to collapse
Sorry I'm kind of a noob but...is my cpu not like other Nexuses? Why would it have a problem with mine in particular?

AkutsuX said:
Sorry I'm kind of a noob but...is my cpu not like other Nexuses? Why would it have a problem with mine in particular?
Click to expand...
Click to collapse
lol
there's this thing called quality of the components used; the chinese can make the best and the worst.
every chip handles the tasks that are required of them yes, but that's why you see devices that can OC to 1.6, 1.7 even 1.8ghz stable, or UV like a boss, and others that can't handle even 1.6ghz oc or huge UVs.
for example, mine can UV like a boss, but not so good at OC'ing.
thermal throttling of the cpu might be more agressive with some kernels.

Question. Why does my s4 keep overlooking itself?

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!