Hi everyone, i just flashed Devoid franco kernel v17 (i am using Devoid froyo final), every things are fine, but why i used No-frills cpu to set max 480Mhz - min 235 Mhz then Phone is crashed and it entered to Emergency mode. I force to remove the battery to turn-off and re-boot phone.
Have anyone help me to solve this.
Many thanks for support.
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.
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.
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.
Just wondering if anyone knows how I can change the i/o scheduler on my OP8T running stock android 12(the default is noop, which I hate). I use ex kernel manager....tried changing it with the app and tried every 'apply on boot delay' under settings in the app but for some reason it just wont stick. also tried franco kernel manager app and doesnt work either. Is there some kind of command prompt line to use that does the trick? My only options are noop, cfq, and deadline...which Im trying for deadline.
fosgate24360 said:
Just wondering if anyone knows how I can change the i/o scheduler on my OP8T running stock android 12(the default is noop, which I hate). I use ex kernel manager....tried changing it with the app and tried every 'apply on boot delay' under settings in the app but for some reason it just wont stick. also tried franco kernel manager app and doesnt work either. Is there some kind of command prompt line to use that does the trick? My only options are noop, cfq, and deadline...which Im trying for deadline.
Click to expand...
Click to collapse
Did you try kernel adiutor app?
Rootk1t said:
Did you try kernel adiutor app?
Click to expand...
Click to collapse
no but I will give it a try and see thank you
that app isnt working either
Smth in stock OOS12 prevents settings to be applied at startup in stock kernel.
Did you try custom kernels?
Rootk1t said:
Smth in stock OOS12 prevents settings to be applied at startup in stock kernel.
Did you try custom kernels?
Click to expand...
Click to collapse
I tried that last bluspark kernel and the phone took forever to boot up and when it did i lost touch ability on the screen. i thought all the other custom kernels were for oos11 base. if you know of any custom that will work please share