Hi all,
I Have a x10 mini pro U20i with Floyo Final, Surface dithering Disabled, JIT Enabled, VM Heap size: 24.
I can't put more clock in my x10... I see many users putting 768, 748, and i only works up to 710Mhz. Other configurations my x10 reboot and reboot again after load all applications and again, and again....
In my cyanogen was max speed cpu 710, and not set "load at start"
In setcpu, is load at start, and sped cpu max is setup in 710, if ai put 729, for sample, after some seconds, my cell phone reboot.
Have any configuration wich i making wrong ?
ty a lot and sorry for my english.
moahrs said:
Hi all,
I Have a x10 mini pro U20i with Floyo Final, Surface dithering Disabled, JIT Enabled, VM Heap size: 24.
I can't put more clock in my x10... I see many users putting 768, 748, and i only works up to 710Mhz. Other configurations my x10 reboot and reboot again after load all applications and again, and again....
In my cyanogen was max speed cpu 710, and not set "load at start"
In setcpu, is load at start, and sped cpu max is setup in 710, if ai put 729, for sample, after some seconds, my cell phone reboot.
Have any configuration wich i making wrong ?
ty a lot and sorry for my english.
Click to expand...
Click to collapse
Some people have it on 768, some on 749, I have it on 729, if i put on 749 works like 5 mins then reboot, and there is Nothing you can do, cuz it's processor dependent
Yes, undertand.
But, for example, i only change in set cpu, or change too in cyanogem, putting the max cpu at 729 and not setting "load at startup" ?
ty a lot
moacir jr.
moahrs said:
Yes, undertand.
But, for example, i only change in set cpu, or change too in cyanogem, putting the max cpu at 729 and not setting "load at startup" ?
ty a lot
moacir jr.
Click to expand...
Click to collapse
Just do it on setcpu with a stable speed
have u try the tweaks for our mini pro yet?
I don't try tweks... What is this ? I will search in forum.
Related
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
Could anyone please tell me the settings and profiles that will give my x10 mini the best battery save? thanks
actually there is already a preset for that ..the "powersave" one..
Easy, just put both bars in 122880MHz..
Your phone are going to be rrrrreeeaaaallllyyy slow, but you save lots of milliamps
Use ondemand only. And set min to 122 and max to 600.
I use a profile when screen is off that set min to 128 and max to 320, ondemand too.
Step 1: Once the app has downloaded from the market open it.
Step 2: Hit auto recommend speeds on the first boot up of the app.
Step 3: Click the profile tab at the top.
Step 4: Hit Add Profile.
Step 5: The profile button selects what happens for the CPU to under clock or over clock. The max is the max the CPU will reach; the min is the minimum the CPU will reach.
Step 6: Profile: Screen off. Max: set to minimum. Min: set to minimum. Scaling: set to Conservative. Priority: set to 100. Press okay, and hit Enable.
Thanks to Ultralinks
Has anyone had problems with random freezes and reboots with SetCPU installed? I've had a couple random reboots, so for now I've uninstalled SetCPU to see if the problem goes away. I also have Advanced Task Killer installed but it wasn't set to kill tasks automatically.
raiderkilo said:
Step 1: Once the app has downloaded from the market open it.
Step 2: Hit auto recommend speeds on the first boot up of the app.
Step 3: Click the profile tab at the top.
Step 4: Hit Add Profile.
Step 5: The profile button selects what happens for the CPU to under clock or over clock. The max is the max the CPU will reach; the min is the minimum the CPU will reach.
Step 6: Profile: Screen off. Max: set to minimum. Min: set to minimum. Scaling: set to Conservative. Priority: set to 100. Press okay, and hit Enable.
Thanks to Ultralinks
Click to expand...
Click to collapse
Setting SetCPU like that is not very smart. For example, You have Your screen off, someone is calling You, what happens? You get the call ringer after few seconds (sometimes even 10-15!). Reminds of old Symbian versions? But just this. Next example - You have Your screen off, and You receive sms. What happens if You are using Handcent, and have to go to the app manually after phone wakes up? It takes ages... But if You have more than 1000 massages in Your inbox, and a new one come, and You get it after screen wakes up it can even lead to a reboot.
Lets add some random weird situations if You are listening to Your player while the screen is off... using some third party apps, etc...
Setting the minimum CPU for the screen off is not a good idea. Don't do that, or the phone will fail You in most unwanted cases.
so what are you guys using?
I am 122-600 on normal ondemand
and screen off on 122-256 ondemand
Anyone with better profiles?
just dont overclock!!!
why not? I see you are running 729/600.
WHY is your min 600?
Use smartass governor - auto profile, just upgrade to gingerbread.. best profile yet..
Set normal use 122Mhz-729Mhz 100% Priority
Set for charging: 122Mhz-245Mhz (or similar) - 100% Priority
Set for screen off 122-245 (or similar) - 100% Priority
^ this saved me battery when I used my phone for so much else besides calling and texting.
for good batter backup....set the minimum as 122Mhz and the max as 480 Mhz....anything above 748 and below 480 will get u into "restart & restore"...however, there is a overclock module allowing you to overclock to 825 Mhz (but dats juss fr "testin"...u'll lose battery like a freak and will get awfully hot readings)
achyut said:
for good batter backup....set the minimum as 122Mhz and the max as 480 Mhz....anything above 748 and below 480 will get u into "restart & restore"...however, there is a overclock module allowing you to overclock to 825 Mhz (but dats juss fr "testin"...u'll lose battery like a freak and will get awfully hot readings)
Click to expand...
Click to collapse
Only a handful devices supports being clocked to 825Mhz but it's very dangerous.
I doubt you can raise the clock speed to 825Mhz without the phone freezing up.
ruifung said:
I doubt you can raise the clock speed to 825Mhz without the phone freezing up.
Click to expand...
Click to collapse
Some have succeeded, but I doubt their phones lasted very long after that.
Just wondering, is the phones processor under the right side of the keyboard? cause after a few minutes @ 710Mhz, that area is hot. Since I switched to the smartass governor, it rarely is hot anymore (due to the fact it mostly spends time @ 245/320Mhz
Um... question?
Shouldn't the phone go into deep sleep when the screen is off with no cpu activity?
Also install cpu spy and see what the cpu is doing for how long.
https://market.android.com/details?id=com.bvalosek.cpuspy
1. The cpu does not make the most heat... it's the 3G radio.
2. Cpu should deep sleep automatically.
My OC prifile for mini pro:
Standard profile- 122 - 825mhz
If Battery < 15% then 122 - 600 "this gets rid of crashes due to low power OC"
Also.. i asked some of the developers that made the modules for overclocking and undervolting.
It's undervolting there is no upward voltage bump so it can't really nuke a cpu.
But you can nuke the power circuits if you use heavy internet on 3G and charge at the same time.
How can I put over 600 Mhz?
My SetCPU makes 600 Mhz the max. I want to put just on 700, but I can't. What is the problem?
@Felimenta97:
You don't have any overclock-enabler module installed/insmodded or if using any CM-based ROM, the corresponding setting is disabled.
I'm using smartass with 122-320 for screen off and ondemand with 320-729 for normal, no problems so far
The max MHz I could get was 729MHz, 748MHz worked but after some time the CPU got 'pegged' as said in the logcat
Tried the 825MHz setting that only caused a freeze and boot loop, forcing me to do some fast adb commands to get rid of the overclock
Hi Guys,
I need a real problem solver here.
I'm having some issues with with SetCPU on my newly rooted Motorola Atrix (2.2.2 Froyo). It's an Australian model with Telstra branded firmware.
I recently rooted it using this guide.
My SetCPU profiles are as follows:
>90% - 750 max 200 minimum 90 priority
Screen off - 216 max 200 min 85 priority
>75% 600 max 200 min 80 priority
>50% 500 max 200 min 75 priority
>20% 300 max 200 min 60 priority
The problem?
As my battery decreases, SetCPU does not change to the appropriate profile. The "Scaling" option is also greyed out.
I hope someone can shed some light in this for me.
Thank you in advance.
Edit: My friend has an Atrix which is nearly an exact copy of mine without any issues what so ever. I find this bizarre.
Solved.
For anyone who wants to know how, simply reverse the priorities.
i.e Make it so higher profiles have lower priorities, and lower profiles have higher priorities.
Scale Drop-down button greyed out
Did you also find a solution to your scaling button being unavailable?
I'm running HOME BASE MEGA 3.1 - EXT4 1.3GHZ DEBLURRED with 4.5 UPDATE and I the scale button is greyed out.
Any ideas?
marhodges said:
Did you also find a solution to your scaling button being unavailable?
I'm running HOME BASE MEGA 3.1 - EXT4 1.3GHZ DEBLURRED with 4.5 UPDATE and I the scale button is greyed out.
Any ideas?
Click to expand...
Click to collapse
I have the same problem. I searched around a bit and didn't find any answers.
Anyone?
Thanks.
jaideepn said:
I have the same problem. I searched around a bit and didn't find any answers.
Anyone?
Thanks.
Click to expand...
Click to collapse
Scaling requires a scaling governor to be compiled into the kernel. I assume you're using faux's kernel in that rom, and I don't think he has any scaling governers in his kernel.
Hi!
Is there an app that can change the CPU governor according to useage? I mean, I'd like to have the governor on "ondemand" setting, while I'm not using the phone (the screen is black), but it would be cool if an app would set the governor to "performance" as soon as the screen lights up. It could be done with Tasker perhaps, but Tasker doesn't want run on my phone, doesn't even want to install...
Is there an app for this? Thanks for the answer!
koko008 said:
Hi!
Is there an app that can change the CPU governor according to useage? I mean, I'd like to have the governor on "ondemand" setting, while I'm not using the phone (the screen is black), but it would be cool if an app would set the governor to "performance" as soon as the screen lights up. It could be done with Tasker perhaps, but Tasker doesn't want run on my phone, doesn't even want to install...
Is there an app for this? Thanks for the answer!
Click to expand...
Click to collapse
Yyyyy, SetCPU ....
Sent from my GT-I5800 using XDA Premium App
cop1976 said:
Yyyyy, SetCPU ....
Sent from my GT-I5800 using XDA Premium App
Click to expand...
Click to collapse
Such a dumb, I am... Of course SetCPU! I've been using NoFrills for some time, I'm changing that. Thanks!!!
Use Set CPU, go the 2nd page in that and there you can select profiles.
For example suppose your kernel allows you upto 667 MHZ, then you can select in the profile something like :
When in call, max 300 Mhz.....or Screen Off, Max 200 MHz.
in the 3rd page of Set CPU, it also allows you to undervolt, you may try with -50 in the values.
umangsagar said:
Use Set CPU, go the 2nd page in that and there you can select profiles.
For example suppose your kernel allows you upto 667 MHZ, then you can select in the profile something like :
When in call, max 300 Mhz.....or Screen Off, Max 200 MHz.
in the 3rd page of Set CPU, it also allows you to undervolt, you may try with -50 in the values.
Click to expand...
Click to collapse
My default profile is 390-1170 MHz with performance scaling, and I've set up a profile for screen off with 390-780 MHz with ondemand scaling. I suppose I can set it to lower frequencies as you suggested.
How does undervolting affect CPU usage? I don't know much about these things
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?