Hello,
I have a samsung galaxy s2. I'm having a problem as stated in the title. Here is what i did to my phone :
- Android 2.3.6 KI5
- Rom RevoHD 4
- Kernel Siyah 2.5.1
- SetCPU Screen Off profile : 200-500 conservative.
- i haven't installed many apps.
I also undervolted a bit :
1200MHz - 1200mV
1000MHz - 1100mV
800MHz - 1000mV
500MHz - 900mV
200MHz - 850mV
Apparently if i leave the wi-fi on and let the screen turn off for about 1 hour, the phone will not wake up. I can just soft restart it by holding the power button. but i don't have such problem if i turn off wi-fi first. it is really annoying. does anyone have any idea how to fix this?. Thanl you.
dullahan263 said:
Hello,
I have a samsung galaxy s2. I'm having a problem as stated in the title. Here is what i did to my phone :
- Android 2.3.6 KI5
- Rom RevoHD 4
- Kernel Siyah 2.5.1
- SetCPU Screen Off profile : 200-500 conservative.
- i haven't installed many apps.
I also undervolted a bit :
1200MHz - 1200mV
1000MHz - 1100mV
800MHz - 1000mV
500MHz - 900mV
200MHz - 850mV
Apparently if i leave the wi-fi on and let the screen turn off for about 1 hour, the phone will not wake up. I can just soft restart it by holding the power button. but i don't have such problem if i turn off wi-fi first. it is really annoying. does anyone have any idea how to fix this?. Thanl you.
Click to expand...
Click to collapse
Remove the UV settings and try it again
zelendel said:
Remove the UV settings and try it again
Click to expand...
Click to collapse
And the screen off profile. If your phone needs to do something when the screen is off, let it do it.
Related
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
I have a Samsung Galaxy Gio and when I turn on the display again to send a text message to my girlfriend everything feels very slow etc... Then after 3-4 seconds everything feels very snappy and stuff...
I have no special profiles set with setcpu...
Does anyone know what I can do?
Should I change the memory management settings? Or is the problem that the phone needs to jump from 128mhz to 800mhz. Maybe my phone responds slow because of the slow sampler speed?
Do you have setcpu to throttle down your cpu when the screen turns off?
You could try setting your scaling to "Performance".
---------- Post added at 03:05 PM ---------- Previous post was at 03:05 PM ----------
otnos said:
Do you have setcpu to throttle down your cpu when the screen turns off?
Click to expand...
Click to collapse
He did say that he doesn't have any special profiles set.
I tried this:
ondemand 148 - 800 = LAG[/B]
- throttleUp = 80
- powersavebias = 0
- ignore nice load = 0
performance 800 = ok
conservative 148 - 800 = ok
- throttleUp = 80
- throttleDown = 20
- Sampling rate = 200000us
- Ignore nice load = 0
So far conservative might be my best best... But the issue is that the stock firmware uses 248-800 ondemand by default... I have the lag on that setting as well... I am now testing conservative. I hope I am doing a good thing changing the governor.
djjonastybe said:
So far conservative might be my best best... But the issue is that the stock firmware uses 248-800 ondemand by default... I have the lag on that setting as well... I am now testing conservative. I hope I am doing a good thing changing the governor.
Click to expand...
Click to collapse
You have more lag on "on demand" because the system has to do a check everytime for the frequency. On "performance" the cpu stays at the max (which you allow) eliminating those checks and using time more wisely. Also, keeping it on "performance" also uses less battery life (in a way) compared to "on demand". Conservative will keep the cpu at its lowest, causing far greater lag. So your best bet, would be "performance".
hello to everyone. I have a problem with my device. When I am running apps such as facebook, after 5 minutes of usage or after 10 15 minutes, the screen freezes, I cant press anything and after 8-10 seconds the phone reboots by itself:-(. I cant find the reason. Here are my device settings
CPU Settings:
Governors: ONDEMAND
Min CPU Freq: 122 MHz
Max CPU Freq: 691 MHz (i was using 729 I thought reducing this one, would fix my problem.)
About my phone:
Kernel Version: 2. 6. 29. [email protected] 1
Mod Version: Froyo MiniCM/CMv6 Hybrid by slade87 and owain94. v6.0
Where is the problem???
any background apps running?
you are using really outdated rom, probably you will have better overclocking possibilities with newer roms and kernels.
and try returning to default cpu values and see if it reboots.
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.
MIUI 9 & 10 - VDD restriction turns on by itself and set the min. CPU freq. at 1.6GHz
Hi All,
May someone shed the light and tell me how come that even though I disable CPU VDD restriction (and it's disabled by default..) it just turns on "by itself"? If I change some governor parameter I observed that for instance I disconnect the charger then VDD restriction is turned on immediately and increased the min. CPU to 1.6GHz. I don't even understand this behavior anyway: VDD restriction's action (when it's turned on) should kick in when the CPU reaches a certain temperature (70°C afaik) and should "turn off" when temperature goes below a threashold (69°C afaik) and I thought that when it kicks in it throttles the CPU freq. so decreases the max and not increasing(?) the min(?), this is totally not what I expected from the VDD restriction kernel function..
I already tried to:
- disable perfd
- disable perfd then rewrite /data/system/perfd/default_values and restart perfd
- rename/delete /system/bin/perfd
..but the system still does the above explained behavior.
I'm out of ideas at the moment. Can someone point me to the right direction?
Everything is "stock vanilla" MIUI ROM with Magisk, tried a lot of MIUI ROMs actually (several ROM versions from global stable and developer, chinese stable and developer and forks like Xiaomi.EU, Mi-Globe..) and - at least on my phone - all ROMs were doing this..
Thank you!
Bump - anyone?