So I have this problem I think many of you have had before.. I put SetCPU at 768mhz out of curiosity and voila it doesnt work. Is there any trick that I could pull to modify the value back to 710 (or default) without doing a full wipe ?
Help much appreciated.
Ps. I need my cell in about 1.5 hours.. :S
problem solved:
I installed a different kernel with default clocks ftw
I was trying to use set cpu,im completely stock but rooted, but every time i use it the phone itself just reboots or doesn tturn on until a battery pull, is it the app? the phone? the kernel?
i came from a vzw droid 1 and 2 and i knew that it had to do with the kernels but i was wondering if people know about this or know a fix
thank you
Set CPU can only be set on conservative for the vibrant.
also when setting profiles, min 200 any lower = sleep of death.
or some vibrants can't handle overclock.
Hello
My galaxy s2 doesnt wake up after put in to sleep mode, back n menu keys light up but no haptic feedback, while screen is on, no problems at all. please help me as ive tried wiping, reflashing different roms, trying multiple kernels and setting clock frequencies to always be on 1,2 ghz.
You must have something installed, like SetCPU and the phone goes below 200 MHz in powersave mode.
To all,
Please don't play with underclock/undervolt/overclock stuffs too much, it can damage the device big time. This is a phone for gods sake, keep playing with Sandy Bridge CPU's, they will take your tortures.
Regards.
I do have SetCPU installed, though i haven't touched the frequencies or voltages until after this problem which was when I put the frequencies to 1,2 gHz as lowest and highest. I have discovered another problem where TW launcher gets FC as soon as I touch the screen. Will try to uninstall SetCPU if I get the oppertunity.
wipe and then install cognition s2, its a modem rom and kernel all in one so you'll have no problems. then once its installed don't install setcpu
Sent from my GT-I9100 using XDA Premium App
Thank for your reply and all your help, I was insecure about custom roms so i installed stock rom amd it turned out great
Just wondered if anyone can help me with this.
If I have an app open, ie messages and the screen times out, the phone locks and I have to take out the battery to reset. This dones not happen if I am on the home screen though.
I have root and I'm running Foxhound 2.7 I have also tried different ROMs and the same thing happens. I have done a megawipe are reinstalled several times.
Any idea what is going on?
syztemlord said:
Just wondered if anyone can help me with this.
If I have an app open, ie messages and the screen times out, the phone locks and I have to take out the battery to reset. This dones not happen if I am on the home screen though.
I have root and I'm running Foxhound 2.7 I have also tried different ROMs and the same thing happens. I have done a megawipe are reinstalled several times.
Any idea what is going on?
Click to expand...
Click to collapse
try changing the kernel.
Governor Setting
1-) Which governor are you using. I got similar problems with "zzmove battery" governor.
2-) If you are using undervolt (UV) values dont make any change for 200mHz step. (or using standar -50mV, -75mV UV options try lower values)
Now using Googy Max Kernel and pegasusq governor and got no problem again.
kadiremrah said:
1-) Which governor are you using. I got similar problems with "zzmove battery" governor.
2-) If you are using undervolt (UV) values dont make any change for 200mHz step. (or using standar -50mV, -75mV UV options try lower values)
Now using Googy Max Kernel and pegasusq governor and got no problem again.
Click to expand...
Click to collapse
Not undervolting but I'll give that kernel a try as I am using zzmoove at the moment with Boeffla.
Thanks
So I installed the Lollipop stock rom via the dload folder in the official manner by rebooting and holding vol up + power. Rom installed just fine and everything works but the CPU frequencies are driving me up the wall. This rom/kernel seems to ignore SetCpu's or No Frill Cpu's settings.
Here is what I did and what I see:
1) Yes I've commented out the build.prop entry where it says min=787 and rebooted several times.
2) On boot up I see via Setp CPU min frequency is 787. Draging the min value to any value below 787 doesn't work.
3) Sometimes after turning on the device I'll go into SetCpu and see min set to 300. However several times in the day I'll check out of paranoia and it's back to 787.
4) I've used both Set Cpu and No frils cpu app and set "Set on boot" and that does nothing. I'll often catch the min value floating @ 787Mhz. This is also confirmed by checking time in state and even when turning off the screen, I'll see the 787 usage jump but not the 300 or 384 speeds.
5) Sometimes I see really whacky ****. Like I had Set Cpu open, and the Max was changing from 1593, to 1497, to 1400, to 1100 and then back to 1497.
6) Powersaving is set to normal, not smart, or ultra.
Has anyone gotten the kernel to follow the min/max settings for CPU freq? Anyone have a solution?
Have you checked to see if CPU hotplugging is turned on? If it is then it will make changing the min almost impossible.
Netrunner157 said:
So I installed the Lollipop stock rom via the dload folder in the official manner by rebooting and holding vol up + power. Rom installed just fine and everything works but the CPU frequencies are driving me up the wall. This rom/kernel seems to ignore SetCpu's or No Frill Cpu's settings.
Here is what I did and what I see:
1) Yes I've commented out the build.prop entry where it says min=787 and rebooted several times.
2) On boot up I see via Setp CPU min frequency is 787. Draging the min value to any value below 787 doesn't work.
3) Sometimes after turning on the device I'll go into SetCpu and see min set to 300. However several times in the day I'll check out of paranoia and it's back to 787.
4) I've used both Set Cpu and No frils cpu app and set "Set on boot" and that does nothing. I'll often catch the min value floating @ 787Mhz. This is also confirmed by checking time in state and even when turning off the screen, I'll see the 787 usage jump but not the 300 or 384 speeds.
5) Sometimes I see really whacky ****. Like I had Set Cpu open, and the Max was changing from 1593, to 1497, to 1400, to 1100 and then back to 1497.
6) Powersaving is set to normal, not smart, or ultra.
Has anyone gotten the kernel to follow the min/max settings for CPU freq? Anyone have a solution?
Click to expand...
Click to collapse
Mpdecision.. Qualcomm closed source. Hate it.
> Have you checked to see if CPU hotplugging is turned on? If it is then it will make changing the min almost impossible.
How do I do this?
> Mpdecision.. Qualcomm closed source. Hate it.
Is this a tool that fixes this?
So many people have upgraded to Lollipop and yet how is it that I'm the only one bringing up this 787 issue?
https://www.google.com/search?q=Mpd...ome..69i57&sourceid=chrome&es_sm=122&ie=UTF-8
This is from the program kernel adiutor program you can find here( http://forum.xda-developers.com/android/apps-games/app-kernel-adiutor-t2986129) If you turn hotplugging off you might have better luck setting the min. It will be listed as CPU hotplug in the menu.
Davinci50 said:
https://www.google.com/search?q=Mpd...ome..69i57&sourceid=chrome&es_sm=122&ie=UTF-8
Click to expand...
Click to collapse
Oh man I did not know how to use google. You opened my eyes. /s
> kernel adiutor
kernel auditor did not help, even after two reboots. i still see min stuck at 787. Is this issue perhaps solved in the lollipop pacman rom?
CM drops to 300.. Turn off mpdecision.
OK so I definitely turned off mp decision both via the app and by renaming /system/bin/mpdecision --> /system/bin/mpdecision-lolololol
Rebooted and checked setcpu and my min is still stuck at 787. Granted I check in a few times a day and sometimes I catch the min at 300 yet sometimes I catch it at 787. What else am I missing?
Moody66 said:
CM drops to 300.. Turn off mpdecision.
Click to expand...
Click to collapse
Is it a stable rom? How many reboots do you get, wifi issues, force closes etc? I'm not a fan of rom's not based off of stock rom, because of instability. I left those behind with the Note 1, Motorola Atrix.
Its in snapshot phase. Of course its stable.
Moody66 said:
Its in snapshot phase. Of course its stable.
Click to expand...
Click to collapse
Yes it might be a stable version of CM but is it stable on the Mate 2. I know the difference between stable and nightly.
Its fine. Read the cm forum thread.
@Moody66
No probably like most of the rest he wants to be spoon fed, I was able to determine what you meant in your first post about mp desicsion and determine the appropriate course of action that I wanted to take and also referenced your thread about battery life.
Make a backup, load the rom ,and test drive it like we all do.
God I love Google NO /s
I found a governor that replaces mpdecision. Going to add it to a build. Last two attempts I had issues. Nothing related to governor though. Soon. Pilled a nub mistake with boot.IMG. lol three year old distracting me. So all good. Should help tremendously with cpu. A couple of builds floating around with another governor that does help quite a bit.
Moody66 said:
Its in snapshot phase. Of course its stable.
Click to expand...
Click to collapse
Moody66 said:
I found a governor that replaces mpdecision. Going to add it to a build. Last two attempts I had issues. Nothing related to governor though. Soon. Pilled a nub mistake with boot.IMG. lol three year old distracting me. So all good. Should help tremendously with cpu. A couple of builds floating around with another governor that does help quite a bit.
Click to expand...
Click to collapse
So the general consensus is that Lolipop stock rom cannot have the 787min freq fixed and the solution is to switch rom's altogether? Like I said I disabled mpdecision and even renamed the binary and commented out the entry in build.prop. What else is left?
Isn't that easy. It will always default of there isn't something to takes its place.
Moody66 said:
Isn't that easy. It will always default of there isn't something to takes its place.
Click to expand...
Click to collapse
Isn't that easy. It will always default of there isn't something to takes its place.
Click to expand...
Click to collapse
what is easy? You mean to tell me stock lollipop will default to 787 until what takes it's place? No one knows?
It's stock ROM. If you want to make changes flash a ROM. Huawei isn't going to give you that customization.
Noone has made a custom kernel for it. Obviously since it has emui.
Is 787 hardcoded somewhere in this rom that it's usually defaulted to?