Problem with cpu frequencies. - Samsung Galaxy S7 Questions and Answers

I have a sm g930v and I can't figure out why my frequencies won't stick. I set min to 307 and max to 1.5 and it sets the min to 900 and max to 1.5 and barely hits 1.2 max. This started happening a few months ago and I'm stumped on what the problem is. any suggestions or help would be very appreciated!

Rooted with custom kernel?

*Detection* said:
Rooted with custom kernel?
Click to expand...
Click to collapse
I believe so. I followed the rooting guide from max lee (highonandroid) on youtube. I dont know if its a custom kernel, but to root it i had to flash a .tar to my phone, which contained a boot.img.

I've noticed this problem with Kernel Adiutor and its modified derivatives, haven't got a clue why this occurs except perhaps for DVFS issues. Flash a kernel compatible with Synapse and see how you go.

Related

Overclocking in ICS?

I have been having issues getting my TF101 to overclock in ICS. I have tried Codename Android, CM9, TeamEOS, and Revolver, and ALL of them I could not overclock in. I have tried SetCPU, No-Frills, and (if applicable) the built in frequency control. They all show that the maximum frequency is 1000MHz. I have no clue what is going wrong here. They all were able to gain Superuser, so that isn't the problem. Any and all help would be highly appreciated. I just have no clue what I could be doing wrong.
stompysan said:
I have been having issues getting my TF101 to overclock in ICS. I have tried Codename Android, CM9, TeamEOS, and Revolver, and ALL of them I could not overclock in. I have tried SetCPU, No-Frills, and (if applicable) the built in frequency control. They all show that the maximum frequency is 1000MHz. I have no clue what is going wrong here. They all were able to gain Superuser, so that isn't the problem. Any and all help would be highly appreciated. I just have no clue what I could be doing wrong.
Click to expand...
Click to collapse
Antutu CPUMaster Free works for me on Revolver4_1.3.1 and Blades_meh kernel. You have to manually go into it after installing a OC kernel and set the min and max frequencies and choose a governor and there's a checkbox to tell it to set these at boot. After that it works all day everyday for me up to 1680MHz and deep sleep works, too.
sidneyk said:
Antutu CPUMaster Free works for me on Revolver4_1.3.1 and Blades_meh kernel. You have to manually go into it after installing a OC kernel and set the min and max frequencies and choose a governor and there's a checkbox to tell it to set these at boot. After that it works all day everyday for me up to 1680MHz and deep sleep works, too.
Click to expand...
Click to collapse
Just tried Antutu CPU Master. Same issues. It says that my max frequency is 1000MHz.
Have you manually loaded a new kernel to replace the stock one? Setcpu and the like only modify settings that a kernel exposes, and the default kernel does not allow anything higher then 1000.
Tekfrog said:
Have you manually loaded a new kernel to replace the stock one? Setcpu and the like only modify settings that a kernel exposes, and the default kernel does not allow anything higher then 1000.
Click to expand...
Click to collapse
Yes. After doing so, I also go into my settings and clear the cache and data from SetCPU, so I could set it up again. Still, I am getting max 1000MHz.
stompysan said:
Yes. After doing so, I also go into my settings and clear the cache and data from SetCPU, so I could set it up again. Still, I am getting max 1000MHz.
Click to expand...
Click to collapse
Which kernel are you running now?
Tekfrog said:
Which kernel are you running now?
Click to expand...
Click to collapse
Thanks for trying to help, but I have found my problem. My recovery was still borked from when I tried flashing the official one in Rom Manager. Wiped my recovery, installed the roach recovery, reflashed all of my files, and now I am good to go. I feel like a derp now. LOL
Same issue w/ OC...but wipe recovery?
Your issue sounds exactly like the one I am currently having.
I would like to try your fix...but I am not understanding how the "wipe recovery" process goes. Would you mind please explaining that in more detail? Im pretty sure it IS NOT as simple as just doing a complete cache/data wipe then flashing the recovery over itself is it?
I am:
ViperMOD Prime rooted
ClockworkRecoveryMOD installed (but I think I may have fubar'd it doing the same thing you did trying to recover stock recovery)
FROZN 1.0.9 rom w/ included Guevor kernel and NoFrills CPU app
...but none of the CPU apps will let me OC...wether I flash the kernel seperate from the ROM or use the one included w/ the ROM.
Hope you can help me.
UPDATE: apparently this inability to OC the kernel in any way is happening to those of us experiencing the CWM bootloop issue...so since the loader goes immediately to CWM it never runs the flashed kernel.
So in these forums is a thread to fix the CWM bootloop and if you follow the instructions carefully, you fix the bootloop and thus allowing the flashed kernels a chance to actually install. I chose the Roach method which you can install the code using Terminal Emulator pretty intuitively. I didnt choose the other method because I didnt want to mess w/ setting up an ADB terminal on my PC, which seemed MUCH more difficult.
So...now FINALLY
ViperMOD Prime rooted
ClockworkMOD Touch Recovery 5.8.8
FROZN 1.0.9 ROM (w/ built-in Guevor kernel @ 1.2 default) and am OCd @ 1.54 (np's at all so far, lightning fast, havent even tried 1.6 or 1.7).
Only issue so far is File Manager app crashes on startup...which isnt good because now the other file manager app I tried doesnt see my ext_SDcard...the stock File Manager did.
I've tried using both tastyMEH and Blades using Revolver, CM9 and Android HD, and the stock ICS ROM, using Set CPU and ROM Toolbox pro to try and overclock. I've flashed the ROM first and then the Kernel, and the Kernel and then the ROM. Nothing I've done thus far has enabled me to set the CPU sliders past 1000 mhz. I know people are running these combos and getting 1.6-1.8 clocks. What am I screwing up? I'm using Clockwork Mod recovery to flash. I couldn't even get CM9 to boot.
Thanks so much in advance
Teh Wuss
WU55 said:
I've tried using both tastyMEH and Blades using Revolver, CM9 and Android HD, and the stock ICS ROM, using Set CPU and ROM Toolbox pro to try and overclock. I've flashed the ROM first and then the Kernel, and the Kernel and then the ROM. Nothing I've done thus far has enabled me to set the CPU sliders past 1000 mhz. I know people are running these combos and getting 1.6-1.8 clocks. What am I screwing up? I'm using Clockwork Mod recovery to flash. I couldn't even get CM9 to boot.
Thanks so much in advance
Teh Wuss
Click to expand...
Click to collapse
Please see above solution...I know it seems unrelated but it is the fix for both CWM bootloop AND being able to accept and install a flashed kernel.
If you need additional help, please ask. I am willing to share my solution in more detail to help others out.
WU55 said:
I've tried using both tastyMEH and Blades using Revolver, CM9 and Android HD, and the stock ICS ROM, using Set CPU and ROM Toolbox pro to try and overclock. I've flashed the ROM first and then the Kernel, and the Kernel and then the ROM. Nothing I've done thus far has enabled me to set the CPU sliders past 1000 mhz. I know people are running these combos and getting 1.6-1.8 clocks. What am I screwing up? I'm using Clockwork Mod recovery to flash. I couldn't even get CM9 to boot.
Thanks so much in advance
Teh Wuss
Click to expand...
Click to collapse
When you flash the kernel go to the about section in android and make sure the flash was actually successful.
fwbflash said:
Please see above solution...I know it seems unrelated but it is the fix for both CWM bootloop AND being able to accept and install a flashed kernel.
If you need additional help, please ask. I am willing to share my solution in more detail to help others out.
Click to expand...
Click to collapse
Thanks, this may be a step in the right direction. However I've tried 3 times now to flash the 5.8 touch to no avail. Everytime I reboot I end up with standard 5.5.0.4. I tried flashing with CWM. What am I doing wrong? If it helps ever since I flashed CWM, if the tablet retboots for any reason it automatically boots into CWM, and I have to cold boot into Android manually using the power and volume rocker.
Thanks again-
Teh Wuss
WU55 said:
Thanks, this may be a step in the right direction. However I've tried 3 times now to flash the 5.8 touch to no avail. Everytime I reboot I end up with standard 5.5.0.4. I tried flashing with CWM. What am I doing wrong? If it helps ever since I flashed CWM, if the tablet retboots for any reason it automatically boots into CWM, and I have to cold boot into Android manually using the power and volume rocker.
Thanks again-
Teh Wuss
Click to expand...
Click to collapse
Because your version of CWM is bad. You need to read this thread: http://forum.xda-developers.com/showthread.php?t=1530337
It's on the front page of general discussion, how did you even not see it yet.
horndroid said:
Because your version of CWM is bad. You need to read this thread: http://forum.xda-developers.com/showthread.php?t=1530337
It's on the front page of general discussion, how did you even not see it yet.
Click to expand...
Click to collapse
Thanks, this was it, I didn't see it, because I was a noob and didn't look for it.

[Q] Elemental-S-JB-v2.1 Kernel and Overclocking

Hello,
I have an HTC One S with ViperS 2.0.0 rom. Few days ago, I installed Elemental-S-JB-v2.1 kernel and choosed an 1.7 overclock for the CPU. After flashing the kernel zip and update boot.img via fastboot flash boot command, I booted my phone. All seems to work but when I controlled my overclock with kernel tuner.
So I noticed that the second core was at stock frequency instead of 1.7 GHz like the first core.
Some one could me explain why ?
Just set the second core's maximum clock rate to 1.7Ghz. The Kernel allows you to do this now.
KACE321 said:
Just set the second core's maximum clock rate to 1.7Ghz. The Kernel allows you to do this now.
Click to expand...
Click to collapse
Effectively, I notice that I could with kernel tuner manualy set the frequency of the second core. But I wonder why the overclock frequency choosed during installation of the kernel doesn't affect the second core.
For me, it's perhaps a mistake, it shows that the overclok frequency is not well applied by the installer or there with an problem with frequency policy with this kernel.
Nobody can give me an answer.
I noticed too that the CPU Governor between the first core and the second is different.
Someone knows why ?
That is normal ?
Someone with a stock Rom could check with kernel tuner if the CPU gouvernors are the same ?
Stuff like that has always been picky and not much you can do about it.

[Q] Trinity Kernel Issue

Hi Guys....I'm posting here because I don't have the privileges to post on the official Trinity Kernel thread. I just flashed the kernel this morning and while I'm more than satisfied with the performance I'm a little worried that it simply won't let me choose the CPU frequency. It simply maxes out at 3.14 Ghz ...which is way more than I actually need or want...and whenever I try to go to a more safe 2.3- 2.4 Ghz it simply won't change....tried flashing older versions but it just the same. Is it safe for me to keep it like this or should I try another kernel? Thanks
Catani said:
Hi Guys....I'm posting here because I don't have the privileges to post on the official Trinity Kernel thread. I just flashed the kernel this morning and while I'm more than satisfied with the performance I'm a little worried that it simply won't let me choose the CPU frequency. It simply maxes out at 3.14 Ghz ...which is way more than I actually need or want...and whenever I try to go to a more safe 2.3- 2.4 Ghz it simply won't change....tried flashing older versions but it just the same. Is it safe for me to keep it like this or should I try another kernel? Thanks
Click to expand...
Click to collapse
what do you mean it wont let you chose cpu frequency? by default, trinity maxes at 2260mhz btw, not 3014mhz. you can set it manually to 3014mhz, but chances are that your phone will not be able to run at 3014mhz, very few can. anyways, you need to install a cpu control app to adjust your cpu speed, i use the trinity kernel toolbox, but there are others around.
Catani said:
Hi Guys....I'm posting here because I don't have the privileges to post on the official Trinity Kernel thread. I just flashed the kernel this morning and while I'm more than satisfied with the performance I'm a little worried that it simply won't let me choose the CPU frequency. It simply maxes out at 3.14 Ghz ...which is way more than I actually need or want...and whenever I try to go to a more safe 2.3- 2.4 Ghz it simply won't change....tried flashing older versions but it just the same. Is it safe for me to keep it like this or should I try another kernel? Thanks
Click to expand...
Click to collapse
When flashed, some kernels break root access. Flash the latest supersu (http://forum.xda-developers.com/showthread.php?t=1538053), and then you'll be able to use an app like TKT or trickster to adjust CPU. I use Trinity mostly, and sometimes have this issue if I forget to flash supersu,
also you need to have busybox installed if you are already using a cpu control app. the cpu control app would need busybox to work properly.
simms22 said:
what do you mean it wont let you chose cpu frequency? by default, trinity maxes at 2260mhz btw, not 3014mhz. you can set it manually to 3014mhz, but chances are that your phone will not be able to run at 3014mhz, very few can. anyways, you need to install a cpu control app to adjust your cpu speed, i use the trinity kernel toolbox, but there are others around.
Click to expand...
Click to collapse
Hi. Thanks for your quick reply. What I meant to say is that I use the trinity kernel toolbox but whatever cpu speed I choose it always goes back to 3014mhz...I even tried underclocking...just for the sake of it but nothing...I tried to go default with 2260 mhz but I still get 3014mhz in antutu and geekbench 3. Did a benchmark with antutu and I get 32460 when it should be around 24000. I don't know if I should be worried or glad. While my N5 isn't getting any hotter my past ock experiences tell me that I shouldn't push it. Am I doing something wrong?
Catani said:
Hi. Thanks for your quick reply. What I meant to say is that I use the trinity kernel toolbox but whatever cpu speed I choose it always goes back to 3014mhz...I even tried underclocking...just for the sake of it but nothing...I tried to go default with 2260 mhz but I still get 3014mhz in antutu and geekbench 3. Did a benchmark with antutu and I get 32460 when it should be around 24000. I don't know if I should be worried or glad. While my N5 isn't getting any hotter my past ock experiences tell me that I shouldn't push it. Am I doing something wrong?
Click to expand...
Click to collapse
Antutu and Geekbench 3 show you the max frequency that your phone can go up to on your Nexus 5. If the kernel is overclockable, then these benchmarks will show you the max frequency, in Trinity kernel's case, 3.1Ghz. If everything looks right in the Trinity Toolbox app, then you're good to go. Trinity doesn't come overclocked by default.
Catani said:
Hi. Thanks for your quick reply. What I meant to say is that I use the trinity kernel toolbox but whatever cpu speed I choose it always goes back to 3014mhz...I even tried underclocking...just for the sake of it but nothing...I tried to go default with 2260 mhz but I still get 3014mhz in antutu and geekbench 3. Did a benchmark with antutu and I get 32460 when it should be around 24000. I don't know if I should be worried or glad. While my N5 isn't getting any hotter my past ock experiences tell me that I shouldn't push it. Am I doing something wrong?
Click to expand...
Click to collapse
well, you are not running your phone at 3014mhz. a 32000+ in antutu is average for 2260mhz considering you are running the dalvik/bionic patches(your rom probably includes them. i getvabove 40000 at 2.5ghz, cant imagine what it woukd becat 3014mhz! btw, what rom are you running? anyways, it sounds to me as you dont have busybox installed, tkt needs it to work properly. go to the play store, find the busybox app by stericson, install it, open it, let it do its thing, then install it and reboot. that should get tkt working properly. like i said, the default trinity top cpu speed is 2260mhz and no higher.
Paradelle said:
When flashed, some kernels break root access. Flash the latest supersu (http://forum.xda-developers.com/showthread.php?t=1538053), and then you'll be able to use an app like TKT or trickster to adjust CPU. I use Trinity mostly, and sometimes have this issue if I forget to flash supersu,
Click to expand...
Click to collapse
Thanks....seems I lost root access. Re-flashed SuperSU and now everything's working great. Thanks guys for all your quick help. Have a nice one
Catani said:
Thanks....seems I lost root access. Re-flashed SuperSU and now everything's working great. Thanks guys for all your quick help. Have a nice one
Click to expand...
Click to collapse
awesome!
i flash supersu every single time i update my rom, rastakat, because it doesnt include su, and has to be flashed every time.

[Q] Can't set CPU speed on Lollipop

Hi all,
I just installed Nameless ROM and am having trouble setting the CPU speeds. I've tried with Device control (built in) and then with No Frills CPU, both with root access, and have not had any success setting my CPU speed. When I set anything on minimum, I exit the app and when I return it goes back to its original value (1574). Same thing with No Frills. I have BusyBox installed and the latest version of SuperSu. So my question is, does anyone have any idea why this is happening? Is there a workaround? Has anyone had a similar experience? I do not have a custom Kernel, but my experience in the past has been quite similar with Franco Kernel and ElementalX kernel across a number of different ROMs.
Any help would be appreciated.
Not actually a help but franco.Kernel Updater (App) doesn't work with CM12 as long as you don't install SuperSU. I did and it solved all problems. It has something to do with the internal su management I guess... but I'm not sure what's wrong with your setup since you already tried SuperSU.
Use a custom kernel.
@Lethargy: Damn, pretty simple answer! I've somehow missed that he says "no custom kernel" :S
Custom kernel
Custom kernels yield same result. Flashed Franco and the same thing is happy ING in the FKUpdater app. Forgive me if I'm wrong but the device control that's baked in to the Rom should be able to scale the kernel set in place by the same rom, right?
xkn0s said:
Custom kernels yield same result. Flashed Franco and the same thing is happy ING in the FKUpdater app. Forgive me if I'm wrong but the device control that's baked in to the Rom should be able to scale the kernel set in place by the same rom, right?
Click to expand...
Click to collapse
Whatever "device control that's baked into the ROM" makes no difference. All kernel apps/methods are the same, which is to simply echo a value (sysfs). You can do it via any kernel app, embedded kernel app, Tasker, Terminal, its the exact same thing.
What is your SELinux state?
Lethargy said:
Whatever "device control that's baked into the ROM" makes no difference. All kernel apps/methods are the same, which is to simply echo a value (sysfs). You can do it via any kernel app, embedded kernel app, Tasker, Terminal, its the exact same thing.
What is your SELinux state?
Click to expand...
Click to collapse
Did not know that. Thanks for the info!
SELinux is Enforcing.
xkn0s said:
Did not know that. Thanks for the info!
SELinux is Enforcing.
Click to expand...
Click to collapse
Try setting it to Permissive
Lethargy said:
Whatever "device control that's baked into the ROM" makes no difference. All kernel apps/methods are the same, which is to simply echo a value (sysfs). You can do it via any kernel app, embedded kernel app, Tasker, Terminal, its the exact same thing.
What is your SELinux state?
Click to expand...
Click to collapse
Lethargy said:
Try setting it to Permissive
Click to expand...
Click to collapse
Changed to permissive verified and reboot, still having the same trouble... tried flashing Franco again and went into boot loop; Same with Hellcore kernel and ElementalX kernel.
xkn0s said:
Changed to permissive verified and reboot, still having the same trouble... tried flashing Franco again and went into boot loop; Same with Hellcore kernel and ElementalX kernel.
Click to expand...
Click to collapse
Not sure why it would end up in a non-boot. Try reflashing your ROM then the kernel.
Lethargy said:
Not sure why it would end up in a non-boot. Try reflashing your ROM then the kernel.
Click to expand...
Click to collapse
Booted TWRP, Flashed Rom and ElementalX in one go, boot stuck at Google splash screen for 20 minutes. Reflashed rom and booted up. Still not able to set CPU. Tried Reflashing Franco Kernel with app again and back to Google Splash Screen.
xkn0s said:
Booted TWRP, Flashed Rom and ElementalX in one go, boot stuck at Google splash screen for 20 minutes. Reflashed rom and booted up. Still not able to set CPU. Tried Reflashing Franco Kernel with app again and back to Google Splash Screen.
Click to expand...
Click to collapse
If you reflash the ROM it'll probably go back to using it's original kernel. Have you tried with a different ROM?
Lethargy said:
If you reflash the ROM it'll probably go back to using it's original kernel. Have you tried with a different ROM?
Click to expand...
Click to collapse
Yeah I reflashed /system and it came back up.
I just flashed Terminus Rom (http://forum.xda-developers.com/google-nexus-5/development/android-5-0-0r7-lrx21v-t2950499) and set up as new device. installed Kernel Toolkit and was able to set the Clock, but after a few minutes it just went back to default.
Flashed ElementalX kernel after that and installed the corresponding app and was able to set clock without it changing back. seems to only work in ElementalX app though.
It survived a Reboot and I sat and watched it for a while and it seems to all be working now!
Thanks for your help @Lethargy
xkn0s said:
Yeah I reflashed /system and it came back up.
I just flashed Terminus Rom (http://forum.xda-developers.com/google-nexus-5/development/android-5-0-0r7-lrx21v-t2950499) and set up as new device. installed Kernel Toolkit and was able to set the Clock, but after a few minutes it just went back to default.
Flashed ElementalX kernel after that and installed the corresponding app and was able to set clock without it changing back. seems to only work in ElementalX app though.
It survived a Reboot and I sat and watched it for a while and it seems to all be working now!
Thanks for your help @Lethargy
Click to expand...
Click to collapse
ElementalX and it's app use an init.d script (as of the latest version, it uses a ramdisk script instead) to set the values upon boot, reading values from a config file.
Hi all,
For reply at first message, I think have a solution (that's worked for me). On many devices like Nexus or Xperia, a Qualcomm service can be installed and running at boot (MPDecision) and change the CPU usages when it's necessary (number of cores and frequencies).
Maybe this priority is higher than all in Lollipop, and overwrite the modifications changed in other CPU managment apps. I found this when I searched a solution to this same problem on my Xperia Z with Lollipop 5.0.2. I used lot of app and no one worked for me, and tried Kernel Adiutor to see more parameters (need install Busybox). I disabled MPDecision to the CPU Hotplug section, and the SetCPU profiles worked after.
But you can see that disable this option keep all cores enable (with MPDecision enable, many cores change status to "disconnected" when no usage) maybe it's better to use SetCPU profiles on a full day than leave MPDecision manage your CPU. Just compare.
Sorry for my bad english, and happy if this help someone.

[Kernel] [SM-T560/gtelwifi][4.4]

This is a Custom Kernel for SM-T560/gtelwifi running stock ROM.
-Added CPU Governor Ondemand
-Added CPU Governor Powersave
-Default cpu Governor is set to Ondemand
-Fixed cpu Frequency from resetting it self if lowered manually by user.
-Added Virtualization Drivers.
Flash with twrp.
Download here
drive.google.com/open?id=1G6-t7ykD6PDNoGegNAXPyAggnd_UArVO
Hi
First of all,thank you for your hard work...
Now i tried your kernel on my samsung sm-t560 only wifi,i tried it with stock ROM and "Lightning ROM" but it's stuck on bootloop(kernel splash screen).Am i doing something wrong,or this kernel isn't for my tablet?Thanks
Edit;
So i managed to flash the kernel and it works,it finally works,i was looking for this thing for so long.Thank you very much
pren22 said:
Hi
First of all,thank you for your hard work...
Now i tried your kernel on my samsung sm-t560 only wifi,i tried it with stock ROM and "Lightning ROM" but it's stuck on bootloop(kernel splash screen).Am i doing something wrong,or this kernel isn't for my tablet?Thanks
Edit;
So i managed to flash the kernel and it works,it finally works,i was looking for this thing for so long.Thank you very much
Click to expand...
Click to collapse
Same thing happened to me. How did you manage to fix it?
Here is the upload of the kernel.
GreeyChip said:
This is a Custom Kernel for SM-T560/gtelwifi running stock ROM.
-Added CPU Governor Ondemand
-Added CPU Governor Powersave
-Default cpu Governor is set to Ondemand
-Fixed cpu Frequency from resetting it self if lowered manually by user.
-Added Virtualization Drivers.
Flash with twrp.
Download here
drive.google.com/open?id=1G6-t7ykD6PDNoGegNAXPyAggnd_UArVO
Click to expand...
Click to collapse
Could i ask you to do the same thing for the latest version of t560 4.4.4. i'll upload the stock kernel and if you can do it i would really appreciate it.
I think the kernels are the same but when i try to install the modified from above, it gets stuck the first boot splash.
Thank you

Categories

Resources