Hello! I have an a32 5g and when I run intensive apps like emulators such as dolphin mmj and aethersx2, I can clearly see a drastic increase in performance when my finger are on the touchscreen. How can I ensure that my phone is running this fast all the time?
It's caused by "input booster", likely forcing CPU Freq at max_freq.
Try to tune CPU governor, e.g. set lower value for up_threshold.
Or you can use performance governor, but this will use max_freq all the time, draining battery very fast, except in deep sleep state of course.
I found Franco Kernel Manager and already have per app profiles set up to change when aether or dolphin launches. Thanks again!
*Completely fixed the problem btw!
Related
Hello,
I am wondering what the best Setcpu profiles are for SGSII when you want performance while awake and save as much as possible in Idle.
Can I put it all the way down to 500mHz while screen off and still be able to run background processes properly?
I don't really see why this shouldn't work. I had it set like that, but I also have it set to 500MHz when active quite often, as this is enough for many applications. Still, that might not be necessary, as it resides in this state quite much of the time anyway.
Since I have undervolted my phone recently, I had to set the "screen off" profile to 800MHz so that the screen comes up (otherwise, it wouldn't). But in the end, it probably doesn't matter too much what you have set for that profile, as the phone should be sleeping most of the time anyway, shouldn't it?
jeo1996 said:
Hello,
I am wondering what the best Setcpu profiles are for SGSII when you want performance while awake and save as much as possible in Idle.
Can I put it all the way down to 500mHz while screen off and still be able to run background processes properly?
Click to expand...
Click to collapse
Profiles are useless, the ondemand governor should scale down your cpu by default when not in use, that' s the whole point of this governor!
I am starting to believe that the ICS kernel scales properly although some people may claim it only scales from min to max.
I noticed on the stock GB kernel, the exact same thing happens when trying to use CPU controlling apps such as setcpu. However, for BOTH GB and ICS without using CPU controlling app, I can see the in between frequencies being used. When I try adjusting the slider THEN it starts the freaking out in terms of min/max. (Rom toolbox)
I even notice the battery life worsen tremendously when trying to use setcpu, antutu, etc on STOCK frequencies. Perhaps it has to do with people trying to use CPU apps on a kernel with the perflock enabled?
With the absence of a CPU controlling app on ICS , my battery can last the SAME (not worse, for sure) as it on GB.
Perhaps this can help those who complain about bad battery life on ICS
Sent from my ADR6425LVW using XDA
You don't need to wonder anymore! Its a function built into HTC kernels called "perflock" and its function is to continually reset the values for the min and max frequencies in order to prevent other applications such as setCPU from taking control over the CPU frequencies.
I've been using SEbastianFM's ICS OC kernel with setCPU. You are correct, that it does scale properly even though the min/max frequencies hop around. If you take notice of the current frequency, its usually appropriate for the current load level.
Furthermore, if use setCPU profiles to control the CPU speed, I've noticed it prevents the kernel from periodically reverting back to its default speed and governor settings. setCPU occasionally crashes (FC's) about once a day on me, but since I have the widget on my homescreen I notice it starts right back up again within a second or two and starts controlling the CPU speed again.
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.
Hello everybody, today I present my guide or actually the procedure of modifications presently installed on my Xperia U.
1. Grab your Xperia U (I presume it is bootloader unlocked, rooted and installed Stock ICS based firmware)
2. Battery Supercharging-
a. Let your battery charge to 100%
b. Unplug charger and Reboot into CWM and wipe battery stats
c. Reboot into system and use phone as normal until battery is exhausted. (Now your battery is calibrated)
d. For maintenance of life of battery pack thereafter, let battery drain to not below 10%
e. Always charge battery short of 100% i.e. 85-95%
f. Once in a month, shut down your phone at 30-60% charge, remove your battery, and just leave it outside the phone for an hour or so.
Be compassionate, as Gandhiji had said
g. If you want to recalibrate your battery, follow steps 2a-2c. Recalibration for Li-poly is not that essential, since it has no memory but you can do it once a month or after flashing a new ROM.
h. Never leave your battery discharged for very long. Your Li-Poly battery will suffer a deep discharge.
3. CPU Control
a. Download BrainsKernel or Munjeni's Kernel
b. Install it using flashtool or fastboot (i presume you know how to do so)
c. Download your favourite CPU Control App (setCPU, noFrills CPU Control etc.)
I recommend CPU Tweaks as it gives you info on both cores at the same time and also has the time graph for when CPU is asleep (setCPU lacks that)
d. My recommended governor setup-
[Try to use a governor with inbuilt hotplug technology (hotplug means ability to control cores i.e. turn of second core when not required and turn it on when required) Eg. Hotplug, Lulzactive, PegasusQ, Hotplug etc.]
For normal use-
LulzactiveQ 800/200 MHz
For Music(Screen Off)
OndemandAX 800/200 MHz
For Gaming(Dead Trigger etc.)
Ondemand/Hotplug 1000/200 MHz
TIPS-
Remember that most governors with a screen off profile(Smartass, LulzactiveQ, OndemandAX) built in have a wake frequency (CPU immediately jumps to that frequency when screen on) is around 500-700 MHz, so try too keep your Max CPU limit at 800 MHz to prevent screen on delay. This is required as Xperia U has no 600 MHz intermediate CPU step, it has only 400 and 800. 400 is below the wake frequency so capping CPU at 400 MHz will cause lag during wakeup.
For me, using LulzactiveQ saves more power than SmartassV2 or Powersave. This is due to the fact that LulzactiveQ shuts off my second core much faster and much more dynamically than SmartassV2 of Powersave.
LulzactiveQ has a screen off profile of setting CPU speed to around 200-400 MHz while OndemandAX caps it at 500 MHz.
So OndemandAX is better for music as there is no tearing in playback when screen is turned off.
e. If you want to forcibly keep one core off (NOT RECOMMENDED. USE A HOTPLUGGING GOVERNOR INSTEAD) use XCore. It works on Xperia U and Xperia P. Check out the Play Store for further details.
4. RAM Management (Android does this on its own, usually. But you can help it)
a. NEVER use a Task Killer. Android kills tasks much more dynamically than your brain does
b. Delete all bloatware you do not need. This will prevent some background processes from being run and it will save some RAM.
c. Do not use a separate app for Facebook unless absolutely needed. (XDA App is fine )
d. That widget, sitting on your homescreen, which hasn't been touched for the past 1 week can be trashed.
5. GPS Superiority (You'll never use AGPS anymore)
a. Download an app called FasterGPS from the Play Store.(needs root)
b. Open the app and choose you continent and region. If your region isn't there, choose the closest region.
c. Get your ass out in the open and get a lock in less than a minute only on pure integrated GPS.
6. General Tweaks
a. Go to developer options in settings and set Animation Scale to 0.5x
b. Get a good statusbar mod (I recommend Xperia Tab n Grid Jelly Bean).
Why? So that you turn off the WiFi and BT and Packet Data when not required. I wouldn't do that earlier as I was too lazy to go all the way to settings to do so. Now I use the notification toggles and save some power
c. Turn OFF your phone and then charge it.
d. Use Lux Dash, an app to control your brightness. At night, set it to sub-zero to save power.
7. Physical Tips
a. Get a case for your phone. Incase you drop it, it will protect your phone.
b. I know you're tempted to take your phone to the pot and have fun but NO. People have lost phones like that.
c. Every week, clean your phone with a spectacle cloth.
d. Do not overstress your phone, or else you risk your hardware. I know they are designed to face all this but as Gandhiji said, compassion.
Hope these tips help you and your phone
I have a rooted honor 5x with cm13. When I go to kernel adiutor and make sure all cores are running the phone is fast. after being idle it starts to be unresponsive but than gets better I think. I use interactive governor for both types of cores but can not change governor settings on little. How can I eliminate the lagging after idle? I have default governor settings. Is there a bnchmarking app which can set optimal settings?