Related
I loaded the Blades 2 kernel on my TF along side the Revolver ROM.
How can I tell if the OC is safe and working? I am not sure if you stress test it or anything like you do on a Windows PC type device..
acdcking12345 said:
I loaded the Blades 2 kernel on my TF along side the Revolver ROM.
How can I tell if the OC is safe and working? I am not sure if you stress test it or anything like you do on a Windows PC type device..
Click to expand...
Click to collapse
I've found that, in overclocking several Android devices, more often than not if you have an unstable OC, the device will either fail to boot, or will crash constantly. If it's not doing that, you're likely fine.
Um, you're not OCed yet. You need to install setcpu or cpu master and crank up the clock. Clemsyn or Blades gives you the option to OC. It doesn't just OC for you.
lol, and learn from my mistake: when overclocking, don't check the option of "set on boot" untill you have tried overclocking at the Ghz level that you want to use. Believe me, you don't want a bootloop that can only be solved by flashing or restoring from a backup.
acdcking12345 said:
I loaded the Blades 2 kernel on my TF along side the Revolver ROM.
How can I tell if the OC is safe and working? I am not sure if you stress test it or anything like you do on a Windows PC type device..
Click to expand...
Click to collapse
I have done extensive overclocking and undervolting.
Set your OC and voltage settings. Then use setcpu or pimpmycpu min and max to your highest OC MHz.
Then play 1 round of Dungon Defenders. If you make it through that then open the camera.
Repeat this on every MHz from top to bottom. If you are unstable at a frequency then increase your voltage slightly (like 10 - 20 mV) and try again.
If you are stable and want to get a little bit better battery do the same thing but lower the mV until dungeon defenders crashes.
Then start to increase it until you are stable.
If your tablet reboots your way low on mV
If it freezes your low on mV
If the widgets act funny, and/ or disapear every once in awhile your in the right ball park
If everything works except your camera freezes you are very close
Some kernels have more aggressive GPU timings which you can't really change so you might want to try another's kernel if you can't get stable.
Well, it seems that I can't go higher than the 1.2 GHZ. If I go any higher, I get some weird freezes and reboots.
Now I saw the post above but I dont see where I can adjust the different voltages, etc..Maybe I am not using the right program?
acdcking12345 said:
Well, it seems that I can't go higher than the 1.2 GHZ. If I go any higher, I get some weird freezes and reboots.
Now I saw the post above but I dont see where I can adjust the different voltages, etc..Maybe I am not using the right program?
Click to expand...
Click to collapse
What program are you using? Try SetCpu or Pimpmycpu
baseballfanz said:
What program are you using? Try SetCpu or Pimpmycpu
Click to expand...
Click to collapse
SetCPU is what I loaded
acdcking12345 said:
I loaded the Blades 2 kernel on my TF along side the Revolver ROM.
How can I tell if the OC is safe and working? I am not sure if you stress test it or anything like you do on a Windows PC type device..
Click to expand...
Click to collapse
Are you referring to this kernel?
I'm wondering because I have never heard about a "Blades 2" kernel.
EDIT: Nevermind, I figured it out. This is what Revolver Parts calls Blades' 10-01-2011 kernel.
Blades uses some aggressive GPU timings in some of his kernels. You may want to try Clemsyn 22 if you want to try and go above 1.2 GHz.
I am using Tsugi 2.3.4 with the Oyasumi 0.1 UV kernal I want to overclock to 1500 but what settings should I undervolt it to that is stable thanks in advance for the info.
DirtyPISTOLA said:
I am using Tsugi 2.3.4 with the Oyasumi 0.1 UV kernal I want to overclock to 1500 but what settings should I undervolt it to that is stable thanks in advance for the info.
Click to expand...
Click to collapse
We can't tell you not all phones are the same, uv a little (10 or 25) run it for a day or two see how it acts, if its steady, uv a little more, when it starts acting up thats your limit go back to previous settings.
NVIDIA NEVER AGAIN!
fcisco13 said:
We can't tell you not all phones are the same, uv a little (10 or 25) run it for a day or two see how it acts, if its steady, uv a little more, when it starts acting up thats your limit go back to previous settings.
NVIDIA NEVER AGAIN!
Click to expand...
Click to collapse
Alright thanks will try
Sent from my LG-P999 using Tapatalk
I've seen some general advice not to UV for anything over 1ghz speeds as well, but it may not hurt to try if you want and adjust as needed for stability.
I'm running on a -75mv at 1.5Ghz faux kernel 0.4.7..
Perfectly stable, benchmarked AnTuTu, Quadrant, and all those other good stuff.
I have not tried -100mv yet, I doubt it will be stable.
Every phone is different, but I run mine at -20 up to 1 G, and -10 for the rest.
Mine I cant undervolt shoot I have to keep my minimum frequency at 500 to be stable, course I can also run at 1.5 all day (I keep it at 1.2).
Well I guess I can't say I cant UV since I use pimp my cpu and it only gives you options in 25 increments, maybe I would be stable at like -10. But coming from my galaxy s 4g where I could UV over -150 and still be stable, that just doesnt even sound worth doing.
Edit: I just thought about it and maybe the reason I cant UV (more) is because I'm using fauxs pre UV/OC kernel, so I dont even know what stock voltage is. But comparing to my sgs4g at stock voltage I am running considerably lower voltages on the g2x.
The faux thread says it's pre uv at -50 across the board.
Beekersguy said:
The faux thread says it's pre uv at -50 across the board.
Click to expand...
Click to collapse
I been running it so long and flashed so many friends phones I can't even remember details anymore!
Sent from my LG-P999 using xda premium
It happens once each 3~5 day, and a nandroid backup then restore immediately solves the problem. but after a few days they go crashing again....
anybody any idea how this happens?
both CyberGR & AOKPCB have this problem on my phone, clean installed of course, but it never happens to my fella's phones (all Nexus S) running the same ROM, same kernel...
Totally confused.
cdljl2005 said:
It happens once each 3~5 day, and a nandroid backup then restore immediately solves the problem. but after a few days they go crashing again....
anybody any idea how this happens?
both CyberGR & AOKPCB have this problem on my phone, clean installed of course, but it never happens to my fella's phones (all Nexus S) running the same ROM, same kernel...
Totally confused.
Click to expand...
Click to collapse
Matr1x is undervolted. Run the kernel that comes with CyberGR or AOKPCB instead of flashing it.
It's fine that your friend Nexus S runs it, but you're not like your friend, are you? Well your Nexus S isn't like your friend Nexus S either.
cdljl2005 said:
It happens once each 3~5 day, and a nandroid backup then restore immediately solves the problem. but after a few days they go crashing again....
anybody any idea how this happens?
both CyberGR & AOKPCB have this problem on my phone, clean installed of course, but it never happens to my fella's phones (all Nexus S) running the same ROM, same kernel...
Totally confused.
Click to expand...
Click to collapse
Same thing happens to me, had to gave up Matr1x kernel because of that, despite i enjoyed it so much.
Hmm.. try v21.0 or raise voltages
Sent from my Nexus S using XDA
mathkid95 said:
Yeah that's not a kernel issue. Sorry to ruin your day
If you want, though, try v21.0 or raise voltages
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
I had voltages raised +30 across the board. It wasn't a issue with booting or nothing like that, just out of the blue all apps would crash for no reason. Rebooting wouldn't fix it, fix permissions wouldn't fix it, only way to fix it was to reflash and kernel. And it only happened with your kernel in 5 or 6 builds of AOKP, any other kernel would not give that issue, but i enjoyed Matr1x the most.
I will try v21 and if the issue happens again i'll try to capture a logcat and forward it to you.
No I understand you're not bashing my work... forgive my rudeness
Yes, try to flash v21.0 and then if that doesn't work I will look into it
Sent from my Nexus S using XDA
polobunny said:
Matr1x is undervolted. Run the kernel that comes with CyberGR or AOKPCB instead of flashing it.
It's fine that your friend Nexus S runs it, but you're not like your friend, are you? Well your Nexus S isn't like your friend Nexus S either.
Click to expand...
Click to collapse
Thanks for replying. I raised voltage long ago, the problem happens... and now I left the voltage alone as its default, the problem still happens...
as for anything different using the kernel is that I'm using BLX, setting charging limit to 80%. dunno if that would lead to the problem.
DeuXGod said:
I had voltages raised +30 across the board. It wasn't a issue with booting or nothing like that, just out of the blue all apps would crash for no reason. Rebooting wouldn't fix it, fix permissions wouldn't fix it, only way to fix it was to reflash and kernel. And it only happened with your kernel in 5 or 6 builds of AOKP, any other kernel would not give that issue, but i enjoyed Matr1x the most.
I will try v21 and if the issue happens again i'll try to capture a logcat and forward it to you.
Click to expand...
Click to collapse
Yeah my problems are exactly the same! Moreover, I noticed that the crashing processes are more or less system, or requesting root, typically android.process.acore (that's Contacts I suppose?), Google maps, and third party apps like System Tuner, Rom Manager, etc.
As for whether it is a problem with the kernel, I'm not quite sure - I had changed ROM and kernel at the same time before undergoing the problem. And it's really strange of the stability in the first few days - if it is a undervolt problem, it should be happening from the beginning, shouldn't it? Or the problem may not be caused DIRECTLY by undervolt.
but I don't reflash to solve it... nandroid backup and restore will do.
and thanks for your reply DeuXGod! I thought it was only me who get this problem.
mathkid95 said:
Hmm.. try v21.0 or raise voltages
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
Will definitely try 21.0! Raising voltage doesn't seem to help, as one month ago I was using the kernel with raised voltage... the problem happened all the same.
If there's anything different in using the phone to my fellas using theirs, it's that I use BLX limiting charging up to 80%... don't know if it can cause the problem.
Anyway, I'll flash 21.0 first; if it doesn't help, I personally think one restore in each 3~5 days is also acceptable. Thanks mathkid! I'll be on matr1x.
p.s. more details about the problem are in the reply above... just FYI, hope it can help.
cdljl2005 said:
Thanks for replying. I raised voltage long ago, the problem happens... and now I left the voltage alone as its default, the problem still happens...
as for anything different using the kernel is that I'm using BLX, setting charging limit to 80%. dunno if that would lead to the problem.
Yeah my problems are exactly the same! Moreover, I noticed that the crashing processes are more or less system, or requesting root, typically android.process.acore (that's Contacts I suppose?), Google maps, and third party apps like System Tuner, Rom Manager, etc.
As for whether it is a problem with the kernel, I'm not quite sure - I had changed ROM and kernel at the same time before undergoing the problem. And it's really strange of the stability in the first few days - if it is a undervolt problem, it should be happening from the beginning, shouldn't it? Or the problem may not be caused DIRECTLY by undervolt.
but I don't reflash to solve it... nandroid backup and restore will do.
and thanks for your reply DeuXGod! I thought it was only me who get this problem.
Will definitely try 21.0! Raising voltage doesn't seem to help, as one month ago I was using the kernel with raised voltage... the problem happened all the same.
If there's anything different in using the phone to my fellas using theirs, it's that I use BLX limiting charging up to 80%... don't know if it can cause the problem.
Anyway, I'll flash 21.0 first; if it doesn't help, I personally think one restore in each 3~5 days is also acceptable. Thanks mathkid! I'll be on matr1x.
p.s. more details about the problem are in the reply above... just FYI, hope it can help.
Click to expand...
Click to collapse
Return to STOCK voltages. Stock volts aren't just 25mV across the board. This will likely sort out your issue. Have a search in the NS forums, i don't have a handy list on me.
Not looking forward for a fight, but once again, reflash the rom and don't flash another kernel this time. I'm sure you'll live without BLX 80% for a day or two.
Then if the reboots and/or crashes are gone, we can say it's the kernel or the settings and work from there. If not, then we at least eliminated a possibility.
Either way, the stock voltages are:
100MHz 950mv
200MHz 950mv
400MHz 1050mv
800MHz 1200mv
1000MHz 1250mv
Cheers.
Harbb said:
Return to STOCK voltages. Stock volts aren't just 25mV across the board. This will likely sort out your issue. Have a search in the NS forums, i don't have a handy list on me.
Click to expand...
Click to collapse
I've experienced the problem under both stock & +2mV voltage ;P
I have no developing experience though, I don't quite believe it's caused by uv.
thanks for suggestion and your search anyway, you guys are really kind!
polobunny said:
Not looking forward for a fight, but once again, reflash the rom and don't flash another kernel this time. I'm sure you'll live without BLX 80% for a day or two.
Then if the reboots and/or crashes are gone, we can say it's the kernel or the settings and work from there. If not, then we at least eliminated a possibility.
Either way, the stock voltages are:
100MHz 950mv
200MHz 950mv
400MHz 1050mv
800MHz 1200mv
1000MHz 1250mv
Cheers.
Click to expand...
Click to collapse
thanks! As I've already flashed Matr1x V21.0 before reading your post, I'm gonna give the new version a try - let's see how it will do!
In the next few days I should be flashing AOKPCB R2.1, if issue continues I would definitely do what you have posted.
Thanks again!
polobunny said:
Not looking forward for a fight, but once again, reflash the rom and don't flash another kernel this time. I'm sure you'll live without BLX 80% for a day or two.
Then if the reboots and/or crashes are gone, we can say it's the kernel or the settings and work from there. If not, then we at least eliminated a possibility.
Either way, the stock voltages are:
100MHz 950mv
200MHz 950mv
400MHz 1050mv
800MHz 1200mv
1000MHz 1250mv
Cheers.
Click to expand...
Click to collapse
Those are stock ARM voltages. Matr1x (and others, like TEUV) are also UVed with INT (GPU) voltages which can cause the same problems.
The following are stock INT voltages which you can change with NSTools:
100MHz 1000mV
200MHz 1100mV
400MHz 1100mV
800MHz 1100mV
1000MHz 1100mV
edit: thanks to polobunny for correcting me
Harbb said:
Those are stock ARM voltages. Matr1x (and others, like TEUV) are also UVed with INT (GPU) voltages which can cause the same problems.
The following are stock INT voltages which you can change with NSTools:
100MHz 900mV
200MHz 950mV
400MHz 1000mV
800MHz 1050mV
1000MHz 1100mV
Click to expand...
Click to collapse
You are right, but those aren't the stock INT voltages.
However, those are:
100MHz 1000mV
200MHz 1100mV
400MHz 1100mV
800MHz 1100mV
1000MHz 1100mV
Cheers!
Ah, stupid mistake there. Thanks polo, clearly my mind was elsewhere.
mathkid95 said:
Hmm.. try v21.0 or raise voltages
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
Matter continues in V21.0 pal...
Harbb said:
Those are stock ARM voltages. Matr1x (and others, like TEUV) are also UVed with INT (GPU) voltages which can cause the same problems.
The following are stock INT voltages which you can change with NSTools:
100MHz 1000mV
200MHz 1100mV
400MHz 1100mV
800MHz 1100mV
1000MHz 1100mV
edit: thanks to polobunny for correcting me
Click to expand...
Click to collapse
polobunny said:
You are right, but those aren't the stock INT voltages.
However, those are:
100MHz 1000mV
200MHz 1100mV
400MHz 1100mV
800MHz 1100mV
1000MHz 1100mV
Cheers!
Click to expand...
Click to collapse
Ah I just found that I forgot to say thanks to you guys...
Sorry for my absent of mind! And a lot of thanks!
mathkid95 said:
No I understand you're not bashing my work... forgive my rudeness
Yes, try to flash v21.0 and then if that doesn't work I will look into it
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
flashed V22 & raised voltage, still no use.
pm'ed you more details yesterday or earlier.
please tell me if logcat is needed.
cheers!
It Could Be Just A Hardware Issue ,I Had The Same Thing Happen With My Epic
MichaelCampos said:
It Could Be Just A Hardware Issue ,I Had The Same Thing Happen With My Epic
Click to expand...
Click to collapse
well this happens only when I'm on Matr1x kernel.... a great work it is though...
Same thing happens to me with Matr1x kernels, regardless of the rom (CM9 Kang, AOKP, or Kangyultra).
Everything returns to normal if I reflash just the kernel. Seems like a directory or file gets corrupted after a period of time.
Sent from my Nexus S 4G using Tapatalk 2
Hello
I am new to this forum and am a long time CM user which I am using on my phone at the moment. However, having discovered the aggressive thermal throttling on this phone (CPU-intensive tasks seem to throttle the max CPU speed down to 1190 MHz very very quickly, before the phone even gets warm), I'm trying to find a custom kernel that will work with CM. I don't care about any fancy features such as S2W or DT2W and if the kernel allows these to be disabled then that would be even better. Basically looking for a reliable, stable kernel that can be configured to be as close to stock as possible, but which would stop the aggressive thermal throttling.
Thanks
Hi, and Welcome!
I'm afraid that your post likely will be considered a "Best ROM or kernel" thread which is not allowed. It's usually suggested that you go over to the development forum and try out kernels for yourself because everybody's needs are different, and so on.
djsubtronic said:
Hello
I am new to this forum and am a long time CM user which I am using on my phone at the moment. However, having discovered the aggressive thermal throttling on this phone (CPU-intensive tasks seem to throttle the max CPU speed down to 1190 MHz very very quickly, before the phone even gets warm), I'm trying to find a custom kernel that will work with CM. I don't care about any fancy features such as S2W or DT2W and if the kernel allows these to be disabled then that would be even better. Basically looking for a reliable, stable kernel that can be configured to be as close to stock as possible, but which would stop the aggressive thermal throttling.
Thanks
Click to expand...
Click to collapse
Only Chaos kernel is compatiblewith CM atm afaik because its a CAF based kernel.
PhilipTD said:
Hi, and Welcome!
I'm afraid that your post likely will be considered a "Best ROM or kernel" thread which is not allowed. It's usually suggested that you go over to the development forum and try out kernels for yourself because everybody's needs are different, and so on.
Click to expand...
Click to collapse
I probably will do that, but I thought this might not fall in the realm of "best kernel" because I have listed some specific criteria...
gee2012 said:
Only Chaos kernel is compatiblewith CM atm afaik because its a CAF based kernel.
Click to expand...
Click to collapse
I'll give that a try. From browsing earlier I noticed that n30Hammer and ElementalX have separate links for CM11, I figured they would be compatible.
djsubtronic said:
I probably will do that, but I thought this might not fall in the realm of "best kernel" because I have listed some specific criteria...
Click to expand...
Click to collapse
Oh, believe me, I think your post is fine. I just wanted to give you a polite heads-up before the more zealous members started chiming in.
djsubtronic said:
I'll give that a try. From browsing earlier I noticed that n30Hammer and ElementalX have separate links for CM11, I figured they would be compatible.
Click to expand...
Click to collapse
Hi,
Yes they are compatible too, for ElementalX choose the right version. Both have thermal settings.
There is also: http://forum.xda-developers.com/showthread.php?t=2649458 and http://forum.xda-developers.com/showthread.php?t=2633955 (almost the same kernels apart the Toolchain), compatible with CM/CM based rom with thermal control too.
djsubtronic said:
I thought this might not fall in the realm of "best kernel" because I have listed some specific criteria...
Click to expand...
Click to collapse
All you do is make it "best kernel for specific criteria" then. Mods see it all as the same thing.
I'm giving ElementalX a try for now. The mods can feel free to close this thread if they see fit.
Thanks for all the replies.
before this gets locked you need a CAF kernel, Chaos kernel comes to mind, they do nice work. Comes with NXT tweaks which allows you to customize almost everything including temp.
I tried all possible CM11 kernels and Chaos kernel has in my opinion a very nice CPU load management.
Other kernels will stay for several seconds in max frequency after a power demand which result in higher CPU battery drain.
Bricked kernel was also excellent in that field and super responsive but the developer takes a break at the moment so the kernel is not usable for the CAF Version of CM after 25.01.14 without further modding and the AOSP mod for CM CAF is producing some weird behavior on my phone so I go for Chaos and CM at the moment.
I found Elemental would keep upping the minimum CPU to 1267 instead of 300, so at the moment I'm trying out NexXxt as @viking37 linked above, and using Trickster to configure the temps it seems to be working pretty good.
djsubtronic said:
I found Elemental would keep upping the minimum CPU to 1267 instead of 300
Click to expand...
Click to collapse
It's normal, it's how Mpdecision from Qualcomm works (for smoothness purpose). Each time you touch the screen the min CPU freq is increased to 1,26 Ghz. In fact the apps reads this at the min CPU freq because you touch the screen to open it. When you stop to touch the screen the min CPU freq will go back to 300 Mhz, the app needs to update the reading of the min CPU freq too but with Trickser Mod it seems it stuck at 1.26 Ghz all the time (for the reading only) but your min CPU freq is 300 Mhz when you don't touch the screen. You will see better this behavior with an app with "live reading CPU freq" like PerfMon or System Monitor.
You can use the "lock frequency" setting in Trickster Mod after set your min CPU freq to 300Mhz, if you want.
viking37 said:
You can use the "lock frequency" setting in Trickster Mod after set your min CPU freq to 300Mhz, if you want.
Click to expand...
Click to collapse
Not good option. Only locks core 0. Core 1 still affected.
Only full workaround is delete /system/lib/hw/power.msm8974.so
Sent from my Nexus 5 using Tapatalk
rootSU said:
Not good option. Only locks core 0. Core 1 still affected.
Only full workaround is delete /system/lib/hw/power.msm8974.so
Click to expand...
Click to collapse
Hi,
Yep, right
Old thinking that is income , sorry for the mistake. I edited my post
Just thought I'd report back, been using NexXxt with custom thermal config using Trickster, and have had no problems at all, great battery life and no more throttling.
viking37 said:
Hi,
Yep, right
Old thinking that is income , sorry for the mistake. I edited my post
Click to expand...
Click to collapse
Ah no problem
hello
I have a problem with OC on my nexus 5 d821 32 gb. I have this rom [ROM][N5][UNOFFICIAL] ♦ OptiPurity ♦ Now w/ CM11 Themes [9/20/14] + Uber KERNEL and when trying to raise Voltages about 25 or more on 2576 Mhz I have always restarts in benchmark like antutu. I tried to not give more than 2576 MHz bcs its no sens when its resets. On stock Voltages its this same problem ofc only in benchamrks. Soryy for my English. Its not the best.
Kassa92 said:
hello
I have a problem with OC on my nexus 5 d821 32 gb. I have this rom [ROM][N5][UNOFFICIAL] ♦ OptiPurity ♦ Now w/ CM11 Themes [9/20/14] + Uber KERNEL and when trying to raise Voltages about 25 or more on 2576 Mhz I have always restarts in benchmark like antutu. I tried to not give more than 2576 MHz bcs its no sens when its resets. On stock Voltages its this same problem ofc only in benchamrks. Soryy for my English. Its not the best.
Click to expand...
Click to collapse
when you oc, you dont just raise the cpu speed, but you have to adjust the voltages up or down as well, to get it stable. above 2265mhz, there isnt such a thing as "stock voltage", as stock doesnt oc. you meant the roms/kernels "stock" voltages.
simms22 said:
when you oc, you dont just raise the cpu speed, but you have to adjust the voltages up or down as well, to get it stable. above 2265mhz, there isnt such a thing as "stock voltage", as stock doesnt oc. you meant the roms/kernels "stock" voltages.
Click to expand...
Click to collapse
I know about that, so I tried rise voltages +25mv on 2572 Mhz and still get reset in antutu so tried more 50,75 and its this same when I down -25mv phone just freez. Hmm i think its something wrong with phone or im doing some wrong?
Kassa92 said:
I know about that, so I tried rise voltages +25mv on 2572 Mhz and still get reset in antutu so tried more 50,75 and its this same when I down -25mv phone just freez. Hmm i think its something wrong with phone or im doing some wrong?
Click to expand...
Click to collapse
25mV is to large of a jump to try. try raising or lowering the voltage 5-10mV at a time, not 25mV.
simms22 said:
25mV is to large of a jump to try. try raising or lowering the voltage 5-10mV at a time, not 25mV.
Click to expand...
Click to collapse
oki I understand.I'll try now to do as you say and write has achieved results.