Can someone please explain to me why none of the kernel's have OC ability?// I think it's due to quad core overheating but I'm not sure and would really love an actual explanation.. Thanks
Sent from my Nexus 4 using xda premium
they all started with OC ability right at the beginning, then .. a good few number of people had HARDWARE bricked devices, that had a fault with the battery no longer being connected or something
they all had overclocking in common, since then , its been removed on most or all kernels
I'm sure that as time progresses it will be made available again. What's the need to clock anyway its fast enough as it is
Sent from my Nexus 4 using xda premium
zephiK said:
I'm sure that as time progresses it will be made available again. What's the need to clock anyway its fast enough as it is
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
This is true, its a 1.5ghz quad core lol why do we need more ?
Also what was happening in some kernels was that mpdecision (which is qualcomms code that says when the cores should be on and offline, i.e hotplug) was using the hardware maxs of each kernel, so if the kernel was capable of going to 1.8ghz, even if you set the max to 1.4ghz ( using software) , mpdecison would override the software and use the hardware max.. therefore.. .it would ramp all cores up to 1.8.. which caused a major cluster ****..
italia0101 said:
This is true, its a 1.5ghz quad core lol why do we need more ?
Also what was happening in some kernels was that mpdecision (which is qualcomms code that says when the cores should be on and offline, i.e hotplug) was using the hardware maxs of each kernel, so if the kernel was capable of going to 1.8ghz, even if you set the max to 1.4ghz ( using software) , mpdecison would override the software and use the hardware max.. therefore.. .it would ramp all cores up to 1.8.. which caused a major cluster ****..
Click to expand...
Click to collapse
Will I certainly don't need it. Would it be nice to have? Yeah but it isn't on the top of my priority list.
What he's saying about mpdecision is true. If you read the change log for Franco kernel he removed mpdecision and is working towards a open platform for kernels. So we should hopefully be seeing more goodies.
Sent from my Nexus 4 using xda premium
Related
"Stumbled" across this article
In my opinion one of the most informative!
http://www.acsyndicate.net/which-cpu-governor-should-you-go-with/
good read. thanks.
Shameless.
Sent from my SPH-D700 using xda premium
squshy 7 said:
Shameless.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Lol. Troublemaker!
Sent from my SPH-D700 using xda premium
squshy 7 said:
Shameless.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
What does that mean? lol
qbking77 said:
What does that mean? lol
Click to expand...
Click to collapse
i think because it was a team page it links to. that was my impression.
Sent from my SPH-D700 using xda premium
I was gonna post about this actually very informative. Now I'm using voltage control. What should I set for the I/o scheduler? I tried interactive governor and my phone almost locked up lol. Was using conservative. Just started using ondemand.
Sent from my SPH-D700 using XDA Premium App
Bump
Sent from my SPH-D700 using XDA Premium App
For your reading enjoyment.
There are actually a few things Samsung have done that contrast these docs, the biggest of which is that Samsung's conservative governor is more like a transitional governor, in that it simply uses the "transition_states" array to do it's scaling (rather than the calculation conservative uses to determine the next frequency).
nubecoder said:
For your reading enjoyment.
There are actually a few things Samsung have done that contrast these docs, the biggest of which is that Samsung's conservative governor is more like a transitional governor, in that it simply uses the "transition_states" array to do it's scaling (rather than the calculation conservative uses to determine the next frequency).
Click to expand...
Click to collapse
So Nubecoder, is using "on demand" on our phones bad or not? I haven't had any problems running 1400/100 on demand with no,undervolting for months without issue but I still wanted to know. Thanks.
Sent from my SPH-D700 using xda premium
JohnCorleone said:
So Nubecoder, is using "on demand" on our phones bad or not? I haven't had any problems running 1400/100 on demand with no,undervolting for months without issue but I still wanted to know. Thanks.
Click to expand...
Click to collapse
[The short answer]
If it's working for you, then it's not "bad". ;]
[The much longer than I had expected it to be, other info / opinions on Epic governor related issues, answer]
It's just that the Samsung phones don't have anywhere near the amount of steps as other devices do, and their handling of which step to jump to when asked for freq X is not that great (and becomes more of a problem when frequencies are disabled with tools like setCPU and Voltage Control).
The other big thing is that (in Samsung's code) there isn't any compliance to the cpufreq "scaling_min" setting, it simply uses a clip to make sure it's not below the lowest available freq (ie 100MHz) and doesn't care if it's below the scaling_min. Some phones handle the 100MHz better than others (and the original 100MHz is possibly "broken" when you look at it's divisors).
Note that some do kernels have some changes in place to force the compliance of the scaling_min setting. (I know Genocide does anyway.) (And mine does but it has yet to be released to the wild.)
There's some other things in play as well, like the DVFS lock that can be applied to force the frequency to be a "fixed" freq (as in won't change) or a "high_lock" which is basically "no lower than X".
For example, there is a DVFS lock used any time you touch the touch screen that will not allow the CPU to scale below 800MHz (lock token 6 IIRC). (The lock is lifted when you let go). And Samsung's conservative (IMO transitional) governor uses a fixed lock of 800MHz during sleep (suspend).
I've spent a lot of time trying to figure all of this out and to determine why Samsung's devices (specifically the Epic) simply don't play well with most governors.
I have worked out most of the bugs in my kernel (I wrote a function to handle getting the nearest requested frequency with disabled freqs in mind). But it's still not perfect.
I've considered going full force and adding tons of freqs to see how that works out, but that's a crap-ton of work, and my current goal is to release my kernel before official GB drops.
Hopefully will be over the next few days (but I've been saying that to myself for weeks now it seems).
=]
Hi all,
I am using a rooted n7.
I have over clocked my galaxy s2 to 1.5ghz before, but I am not sure what is a safe level to over clock the n7 to.
What is a is is for battery life and performance?
And which kernel do u guys recommend
?
Thanks in advance
Cheers
Corey
Sent from my GT-I9100 using xda premium
fishingfon said:
Hi all,
I am using a rooted n7.
I have over clocked my galaxy s2 to 1.5ghz before, but I am not sure what is a safe level to over clock the n7 to.
What is a is is for battery life and performance?
And which kernel do u guys recommend
?
Thanks in advance
Cheers
Corey
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I run trinity kernel on my Gnex and N7 and on my N7 I keep it stock speeds because I've seen no reason to realistically OC it. Most of the improvements I see are from the kernel software changes over stock. You can OC to 1.6 safely but I'm not sure of the power usage difference but I'm pretty sure the loss in power isn't worth the gain from OCing.
Sent from my Galaxy Nexus using xda app-developers app
I have mine at 1.6 just for the hell of it, I get a good 4 or 5 hours of continuous usage out of it.
brando56894 said:
I have mine at 1.6 just for the hell of it, I get a good 4 or 5 hours of continuous usage out of it.
Click to expand...
Click to collapse
For the benefit of the community, can you tell us any major changes at 1.6 GHz?
Is there anything noticeably faster?
Hi, I have a related question but can't post since I'm new.
Using the glazed rom which i like but it apparently has gpu overclock. I would like to know how to adjust that back to stock setting or at least see what it currently is. I found the CPU section but there is no gpu I can see.
Is there a tool I can use?
Sorry for the hijack...at least its sort of on topic
IMO over clocking is a gimmick, its the kernel build
Sent from my Nexus 7 using xda app-developers app
Harry GT-S5830 said:
IMO over clocking is a gimmick, its the kernel build
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
My thoughts exactly. I play some light games and web browse on my Nexus 7.
For those purposes, my Nexus 7 is already extremely fast, so I don't think I would be able to notice if it was over clocked.
But I guess it depends, maybe there's a big difference when running GPU heavy games.
I have OC mine upto 1640 MHz for bench marking alone for half and hour or probably more and it went fine although the tablet was getting warmer more than usual.
Sent from my Nexus 7 using xda premium
Hi,
I decided to flash trinity kernel.
I am currently OC to 1.5yghz, is that a safe level to keep it at full time? Or can that burn the cpu out?
Thanks again
Cheers
Corey
Edit,
I over clocked my galaxy s2 ages ago, and I noticed a huge difference in performance.
So that is why I want to over clock my n7 too lol
Corey
Sent from my GT-I9100 using xda premium
there is no such thing as a safe overclock. overclocking, by nature, carries some risk. that said, i havent seen anyone brick their device from overclocking.
fishingfon said:
Hi all,
I am using a rooted n7.
I have over clocked my galaxy s2 to 1.5ghz before, but I am not sure what is a safe level to over clock the n7 to.
What is a is is for battery life and performance?
And which kernel do u guys recommend
?
Thanks in advance
Cheers
Corey
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Just wondering
Why do you feel the need to OC?
I go to 1.6 but use the Trinity App to go back to stock when OC not needed
Sent from my GT-I9300 using xda app-developers app
I have not over clocked the Nexus 7 yet but one way to test your devices max is to use setcpu. Make sure you do not have "set on boot" option selected. Then step up your cpu. If your cpu can not handle the over clock it will force restart. If you do not have the set at boot selected it will revert back to the last good state on restart.
Each device is different on what it can handle for over clock.
Sent from my Nexus 7 using xda app-developers app
fishingfon said:
Hi,
I decided to flash trinity kernel.
I am currently OC to 1.5yghz, is that a safe level to keep it at full time? Or can that burn the cpu out?
Click to expand...
Click to collapse
To be honest I doubt you'll notice much increase from oc the CPU since the CPU already is so powerful nothing pushes it to max really.
Only thing worth overclocking is GPU really. And at that, your not going to notice a difference unless your playing some intense games.
Hello,I oc my phone to 2Ghz,but its very slow.
I dont know why it is slow?
Sent from my MB526 using xda premium
yes OMAP 3630 are found to be stable at 1300mhz , but not more than that ,,
btw , for how much time u were able to get it working on 2ghz , without actually getting any kind of hotboot or freeze ??
I only set frequent and voltage in bootmenu.
My rom is lastest cm10.(20121205)
300hz 20v
600hz 34v
800hz 46v
2000hz 86v
Sent from my MB526 using xda premium
There are hundreds of reasons that could cause a slowdown. You have to be more specific. Other than that, it's very risky to set the CPU clock to 2ghz on a device that's meant to work at 800mhz. This means that you could cause the slowdown by setting the cpu clock to 2ghz.
Sometimes I see posts an just think: This person is that sort of man, who rotates the square in tetris....
2 GHz? What are you smoking?
I can max out oc to 1.4GHz, but after that it slows down.
At 2Ghz you need at least 102mv. Btw, can we somehow oc GPU?
Sent from my MB526 using xda app-developers app
Posse666 said:
At 2Ghz you need at least 102mv. Btw, can we somehow oc GPU?
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
That's not too advisable yet... custom kernel not stable enough...
And the BL is still locked, so GPU OC is more trouble than it's worth...
Dude.... Don't be sooo evil on the cpu.... U are only gonna fry it... And lose ur phone permanently... Bring it down to 1300...above that.. Don't expect any help for any mess ups...
sent from my awesome DEFY+
current ROM: Cm10(JB4.1.2)
Kernel: latest Blechdose custom kernel
Ive been getting smoother results underclocking the G2 at either 1.7 or 1.9 and knock on seems more quick to response, but when I tried video recording the 60 fps isn't smooth when you are clocked at the regular speed.. beware...I ran a benchmark on quadrant standard and got 17,250 constantly so it is underclocked per core... I want to hear your opinion on this and do you plan to underclock or already are. I feel like the ability to be more smooth within the UI helps a lot more now..let me know your thoughts!
bencozzy said:
From using trickster mod and setcpu to underclock they only underclock cpu0 the other three still use the full frequency range.
What app are you using?
Click to expand...
Click to collapse
No frills CPU control :0
At 1.9 my Antutu was the same add the One and oddly the graphics test dropped 15-20 frames even though we are not under clocking the GPU.
Sent from my VS980 4G using XDA Premium 4 mobile app
That's really odd tbh o.o did you try quadrent as well? :0
jrgilbert79 said:
At 1.9 my Antutu was the same add the One and oddly the graphics test dropped 15-20 frames even though we are not under clocking the GPU.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I got way higher even at 1.7ghz :0
jrgilbert79 said:
At 1.9 my Antutu was the same add the One and oddly the graphics test dropped 15-20 frames even though we are not under clocking the GPU.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
HeXaLox said:
I got way higher even at 1.7ghz :0
Click to expand...
Click to collapse
You're saying that by underclocking, you're getting a smoother UI but lower benchmarks?
No i got a higher benchmark than the guy who replied on my post. I did get a smoother UI and everything is less laggy. Ill post a pic of 2.3ghz idk if its actually at 1.7ghz or 2.3ghz ill do another test
whittikins said:
You're saying that by underclocking, you're getting a smoother UI but lower benchmarks?
Click to expand...
Click to collapse
All this is true. Just tried. It might be a TINY bit slower ui THOUGH
Sent from my LG-D800 using Tapatalk 4
What settings did toy use? Deadline? Noop? Interactive gov?
Sent from my VS980 4G using XDA Premium 4 mobile app
I am using the app called No-frills CPU Control and for 1.7ghz I am using row and Ondemand as the I/O governor and same settings for the regular clock as well..
jrgilbert79 said:
What settings did toy use? Deadline? Noop? Interactive gov?
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Underclocked at 1.7ghz first then regular clock at 2.27ghz
jrgilbert79 said:
What settings did toy use? Deadline? Noop? Interactive gov?
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am tending to believe that the regular clock speed is actually overclocked...just like how the galaxy s4 is overclocked 200mhz more than normal...however I could be wrong..
If you really want to see if this odd issue is actually happening download an app called Multicore CPU Control (the only app of its kind that seems to work with the LG G2). I use this to save battery by turning off all but one core, but it allows you full control over all your cores.
Download it, create a profile, and set each core to what you want. I had to save the profile first, then go back in to edit the latter 3 cores' frequencies.
I would suggest setting the min and max to the same and choosing Performance for the governor. Use a different app to set the scheduler.
Be sure to have something like Kernel Tuner to ensure that all your cores are running as you intended. If not, go back into Multicore CPU Control and re-save your profile again.
Would love to hear the results afterwards!
I used Multicore CPU Control.
The only way to set clock to CPU 1,2,3 is let them always active. If I leave dynamic for these cores, they still go up to 2,26 GHZ. I think this the reason why HeXaLox have a little decrement when underclock because it only did for one core.
So I have a very thought out question now I have a 4 core phone right? Well my battery life is below average and I was wondering if I had all my cores running at once would it balance out battery life? I just need some help from someone who knows about all this and are all cores mandatory?
Sent From My Liberated E970
You can select how many active cores are activated with trickster mod and (necessary!) a kernel that supports this.
Sent from my Nexus 7 using Tapatalk 4
I know how to and can with my kernel but I need to know if more cores are activated if the battery life will be better or worse
Sent from my Optimus G using XDA Premium HD app
I would definitely take a look in to what my batter usage is and how to control that before I worry about the cores. Just my two cents.
P.S. I am sorry but I believe the Multi-core in the title is spelled wrong.
mr turtle droid said:
I know how to and can with my kernel but I need to know if more cores are activated if the battery life will be better or worse
Sent from my Optimus G using XDA Premium HD app
Click to expand...
Click to collapse
More cores active would mean more processing power, and more processing power requires more energy(atleast on the same cpu), so disabling most of your cores would result in better battery life, maybe by a little bit though.
Hahaha I didn't realize it said mulit
Sent from my Optimus G using XDA Premium HD app
useful topic
It seems to me that by disabling cores wont make a difference to your battery life, only to your performance. It doesn't matter if 2 cores work for 5 seconds or 1 core works for 10 seconds, it is practically the same power consumption
Play around
I would say download CPU-Z from the Play Store and look how much Cores are active and which clock they're at.
Then flash a custom Kernel, which lets you control the clock, govenor and how much cores are active, undervolting may increase your battery life too.
Play with the settings (PLEASE DO NOT RAMP UP THE CLOCKS or set the voltage to the lowest point you can, it may break your phone, stay reasonable, it's not my fault if your phone bricks) and look what's best for you.
Pro Tip: Take a look at the different govenors and look what they do. Google them!
Greetz Leevee33
I hope I could help you a little
Im using trickster mod and I know about all of this I studied up and have undervolted by 200 MV stable but I'm using the hotplug settings to 1:2 so not all 4 cores are active and I get almost two days on one charge!so I guess that does mean less cores use less power
Sent from my Optimus G using XDA Premium HD app