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
Related
Hi guys i have a tiny problem i need clarifying please.
Before anyone says anything i already asked this question and no one seemed to be able to answer it to me. So here it goes.
My question is can we combine the two. What i mean is use Voltage Control to set cpu Voltages and use No Frills to adjust Cpu clock speeds. Voltage Control on my latest rom that i am on Hyperdroid latest version does not save my overclocking and reverts back to stock frequencies 1200Mhz-200Mhz even after i save it on boot. I leave it to reboot for a few minutes till the phone settles and go to check it and governor and i/o schedulers are saved and my voltages also but the only thing that reverts back is the cpu clock frequencies. When using No -Frills though it saves my overclocking.
So my question can i use one app to overclock and the other to undervolt and use them both at the same time?
I know stupid question and i am pretty sure that i know the answer already but if i can get a few opinions regarding the matter i would appreciate it..Also why on the latest firmware it reverts back to stock frequencies even when we save it on Voltage Control is it a bug or something and does anyone if it will get fixed as i really like that app since it does everything i need it to.
Thanks again
you can use both, but I don't see why, VC has also CPU sliders so you can set both parameters from one app
maranello69 said:
you can use both, but I don't see why, VC has also CPU sliders so you can set both parameters from one app
Click to expand...
Click to collapse
Yes i know that. But see the whole point of asking this question is that Voltage Control reverts my frequencies back to stock..So say i try to set my cpu clock frequencies to 1600max-200min and then save it and set on boot once i reboot my phone it reverts it back to stock frequencies...Hence why i am currently using only No frills at the moment till this issue is fixed...And hence why i was wondering if i can undervolt with one app and overclock with the other
I recently switched my kernal from incredikernal beta 4 to anthrax. I made sure to wipe cache and dalvik before flashing anthrax. Everything seems to have worked perfectly but I noticed that when I try to lower my max from 1836, it never sticks even though I have it to set on boot. If I reboot my phone the bar is still set to my preference but above it says 1836. The min sticks, I just can't seem to get the max to stick. Is there anything that I can do to get my changes to stick?
rellomar said:
I recently switched my kernal from incredikernal beta 4 to anthrax. I made sure to wipe cache and dalvik before flashing anthrax. Everything seems to have worked perfectly but I noticed that when I try to lower my max from 1836, it never sticks even though I have it to set on boot. If I reboot my phone the bar is still set to my preference but above it says 1836. The min sticks, I just can't seem to get the max to stick. Is there anything that I can do to get my changes to stick?
Click to expand...
Click to collapse
If you're using SetCPU, try taking off perflock (There maybe the same setting in other CPU apps)
ο χάκερ said:
If you're using SetCPU, try taking off perflock (There maybe the same setting in other CPU apps)
Click to expand...
Click to collapse
Same with CPU Master. If you have problems they say to turn off perflock.
Thanks for the replies! I'm using setcpu and it turns out the perflock must have been the problem because it's been keeping the frequencies correctly since I disabled.
Do we have to turn off perflock on kernels like the ones on Joel's ICS rom?
Just a question, i am using the Phenomenal kernel (normal version) on my S3 and has tried to set the CPU speed using "setcpu" app to have the CPU running at 800-400Mhz, but no matter how many times i set or clear the data and reset, the CPU will still go to 1Ghz, is this a default setting by Samsung to have the setting set at least 1Ghz or is due to the Kernel that i am using now?
mrlow81 said:
Just a question, i am using the Phenomenal kernel (normal version) on my S3 and has tried to set the CPU speed using "setcpu" app to have the CPU running at 800-400Mhz, but no matter how many times i set or clear the data and reset, the CPU will still go to 1Ghz, is this a default setting by Samsung to have the setting set at least 1Ghz or is due to the Kernel that i am using now?
Click to expand...
Click to collapse
phenomenal kernel dosent supports OV/UV, that might be the reason. try nstools from market if you get the same result then its the feature of that kernel
Thanks... have tried it and still stay the same... guess its the kernel...
Hi all,
I couldn't find the relevant information anywhere else, so thought I should ask if someone has experienced this.
Well I'm using setcpu on my razr and it is quite a brilliant app to be honest, helps me save battery quite alot by setting up profiles.
But recently I've been having crashing problems with the phone whenever i set the scaling to hotplug.
Previously, i was just using the default scaling, I guess Interactive it was, and was working quite happily. And, then i read about advantages of using Hotplug scaling, that it enables/disables cores depending on the amount of load on the cpu, which is really good for saving battery.
And before how I was using the phone, was to set a profile for screen off to drop the cpu down to 300MHz, using the default scaling.
But as soon as I changed from default scaling to Hotplug, it starts crashing randomly, and I've to restart the phone using keys.
Scenarios tried:
- Main scaling: Hotplug -- Screen off scaling: Interactive, Ondemand, Performance, Hotplug -- Processor Max: 300MHz
Result: crashing as soon as u turn the screen on, or sometimes while the screen is off.
- Main scaling: Hotplug -- Screen off scaling: Interactive, Ondemand, Performance, Hotplug -- Processor Max: 600MHz
Result: crashing as soon as u turn the screen on, or sometimes while the screen is off.
- Main scaling: Interactive -- Screen off scaling: Hotplug -- Processor Max: 300MHz
Result: In process of checking, hasn't crashed yet for more than an hour. :fingers-crossed:
Can someone kindly point out the obvious mistake I'm making here?
I really want to use hotplug, both as main and screen off.
FYI: I haven't done anything else to the phone apart from gaining root access.
i had issues with setcpu, i recommend no frills cpu control, and setting it down that low more then likely is also an issue, the second core i couldn't see turning off at a low clock and also i think it would max out easily causing instability (especially ICS) and above id say. uninstall setcpu give no frills a try and let me know would be glad to help with what i can!
Thanks for ur reply, yes I'll try no frills, but
mr4r4n said:
setting it down that low more then likely is also an issue
Click to expand...
Click to collapse
I thought the same, but while i was using interactive scaling, it worked perfectly, no issues at all. Probably because both cores were active by default, so both on 300MHz when screen was off.
mr4r4n said:
the second core i couldn't see turning off at a low clock and also i think it would max out easily causing instability (especially ICS)
Click to expand...
Click to collapse
No, I've checked cpu usage visa adb shell, and if the screen off is in hotplug, like what it is right now, the phone stays at 300MHz with the second core turned off, most of the time. And the phone has been running now for more than 3hrs with screen off profile set to Scaling: hotplug -- Max: 300MHz, and the main scaling set to Interactive.
The problem I've seen is, when main scaling is set to hotplug. Doesn't matter whatever u set in screen off profile, it crashes if the main scaling is set to hotplug. But, if no screen off profile is set then, hotplug in main works flawlessly.
That's weird. I've been using SetCPU for a year or so on my RAZR GB/ICS and never encountered any crashes with hotplug or the default ICS's interactive.
I have even tried unofficial governers like smartass2, boostedassv2 and etc, no crashes.
I personally set my phone to use u/c 200-200 for screen off and I find it really saves a lot of battery, and even o/c to 200-1300 when it's on.
Are you using the setcpu from xda or from playstore? I'm using the one from playstore with Razr asia ICS.
Nikorasu said:
That's weird. I've been using SetCPU for a year or so on my RAZR GB/ICS and never encountered any crashes with hotplug or the default ICS's interactive.
I have even tried unofficial governers like smartass2, boostedassv2 and etc, no crashes.
I personally set my phone to use u/c 200-200 for screen off and I find it really saves a lot of battery, and even o/c to 200-1300 when it's on.
Are you using the setcpu from xda or from playstore? I'm using the one from playstore with Razr asia ICS.
Click to expand...
Click to collapse
I think I downloaded it from here.
But I think, they both are the same, from same developer
hsyasin said:
I think I downloaded it from here.
But I think, they both are the same, from same developer
Click to expand...
Click to collapse
This means that you're using an old July 2011 version.
Do make use of playstore's 15 min return policy to test the newer ver. Maybe it will solve your problem.
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?