Since yesterday my phone has been shutting down randomly whenever the screen turned off. Coincidentally, yesterday I also created a profile to underclock the processor to 200mhz when the screen is off. However I forgot about that and assumed it the random shut downs were a problem with Villain Rom or the kernel I was running so I tried every kernel I could find and change ROM, but to no avail, it kept shutting down.
I just had the thought about SetCPU, removed the underclock and alas, it is fine! no random shut downs at all...
Has anyone else had a problem like this?
Yes, that's likely causing the problem. Why would you underclock to 200mhz in the first place? The benefit (if there is any) is minimal. 200mhz is a to low value for most devices.
If you under volt too much it can have trouble turnibg back on from standby. What voltages you set?
Sent from my GT-I9100 using XDA App
Yeah I didn't realise that, I used to underclock to 200mhz when my screen was turned off on my Desire as to preserve battery life which is why I didn't think it was an issue, clearly the Galaxy does not like it hence random shut downs.
I was running at 1200mhz when battery is between 50 and 100% then at 800mhz <50%.
Removed all profiles now and have just set it as on demand
Related
I'm having the problem that my X10 was slow when using it after a longer period of idle. I installed SystemPanel to check out which app was causing this. There I found out that it wasn't a particular app (although FaceRecognition does pop out sometimes), but the CPU is used for 100%, staying at 245MHz. The time it takes to get to 1000MHz is total arbitrary, and it's usually staggers around between this range instead of staying at 1000MHz.
Is it allright that the CPU speed keeps changing within this range ? And does anyone have an idea whats causing the CPU to stay at 245 MHz for too long after being idle ?
Default battery plan is set to "ondemand", which means the cpu will automatically adjusts itself regarding usage. But it's weird indeed it stays at 245MHz, as on mine it often goes to 998MHz just for few things
You can force/restore it with setcpu (maybe) ?
Altough your phone is lagging, your battery should stand for weeks with this clock
Does SetCPU need to add support for the GS2 to work for this?
Or are there any apps that can adjust CPU settings?
Mr setcpu has made an overclock kernal that is in the dev section. Use that for full setcpu support
Sent from my GT-I9100 using XDA Premium App
Actually I wanted to underclock.
I installed SetCPU anyway and it seems to be working
Set from 200mhz to 1000mhz
i tried to use setcpu for power button turn off profile, it failed to turn back on each time. so have gotten rid of it now.
Smith2001 said:
i tried to use setcpu for power button turn off profile, it failed to turn back on each time. so have gotten rid of it now.
Click to expand...
Click to collapse
You need to include 800mhz for screen-off profile
As with galaxy s and nexus s, the device needs 800mhz for turning back on
I have charging profile on top, screen off prof as 200-800 right below, and 200-500 for regular use at the bottom.
No freeze issue so far for the past 8 hours, and I'm going strong at 72% (which includes 30 min of gaming, 40 min of movie, one reboot, and total of 1hr and 45min display on time).
Damn i'm looking forward to this phone. I've had a Hero for the last 18mths and battery life has been a pile of manure. Now to hear people talking about underclocking and still having a fast phone, can't wait.
The phone takes like two seconds when waking up. I mean the screen doesn't wake up right after pressing the wake_drop buttons (home and power). It makes delay like about two seconds. Anybody got any clear explanation of this?
Custom or stock ROM? Lots of app running in the background?
Sent from my WT19i using xda premium
stock rom and I don't have a lot of apps running in the background. Maybe it's a kernel problem..
Its called CPU Scaling. Even if you don't have a CPU scaling/monitoring app, the CPU drops to 245Mhz when sleeping. So these 2 seconds happen because it takes a lot more time to start everything @245Mhz than it does @1024Mhz
If phone is stock, it should not have any problems with CPU scaling. Stock kernel can regulate CPU speed quite fast and should not have problems.
My CPU minimal is 122 MHz(max is 1 GHz), governor is ondemand and never had lag.
Also, CPU apps require root, in some cases also custom kernel.
Sent from my WT19i using xda premium
It's not a problem. It's how it works. The OP see's it as a problem from his perspective...
I am not seeing it as a problem. It's just my other android phones like hd2 take about 500ms to wake up. This phone takes about 1.5 seconds.
dumraden said:
ts called CPU Scaling. Even if you don't have a CPU scaling/monitoring app, the CPU drops to 245Mhz when sleeping. So these 2 seconds happen because it takes a lot more time to start everything @245Mhz than it does @1024Mhz.
Click to expand...
Click to collapse
[URL="http://forum.xda-developers.com/member.php?u=4473694" said:
Someguyfromhell [/URL];4473694]If phone is stock, it should not have any problems with CPU scaling. Stock kernel can regulate CPU speed quite fast and should not have problems.
My CPU minimal is 122 MHz(max is 1 GHz), governor is ondemand and never had lag.
Also, CPU apps require root, in some cases also custom kernel.
Click to expand...
Click to collapse
Thanks guys. You gave a clear explanation.
Oh, just to mention, I get wakeup lag sometimes also, why, I haven't found cause yet.
Since I got my phone last year, I've noticed that once in awhile it'll turn off while it's sleeping. Maybe once a week. I've seen it happen a couple times, while it's asleep the buttons will light up briefly and go out, and then when I hit power it starts up from the LG logo. It's been doing this over three different ROMs, stock, Mik's CM7, and now CM9.
I found the solution for it a couple months ago actually, as long as I set the lowest clock speed to 480Mhz instead of the default 320Mhz it never turns off on its own.
I'd completely forgotten about the issue until today. I installed CM9 the other day and it set the CPU clocks back to default, and this morning my phone turned off during sleep again.
Some questions if anyone could answer:
1) Does anyone have this same issue with their phone and have found an alternate solution?
2) Is this a hardware fault that I should have had fixed while I was under warranty, making me an idiot now for not doing so when I had the chance?
3) The dev thread for hephappy's CM9 ROM says not to change the CPU. Should I be concerned or does that warning generally refer to overclocking?
Thanks in advance.
if i remembered correctly, setting cpu to below 480Mhz sometimes causes the problem your encountering. i have always set minimum 480mhz eversince and i never had that wakeup-problem anymore...
Dunno. I have cranked mine down to the 122mHz minimum on stock 2.2, CyanogenMod, and now on a stock GB ROM. No problems. Maybe it's similar to overclocking where some CPUs just don't like certain freqs.
I assumed "certain CPUs" meant certain models or manufacturers, not individual CPUs. Unless some of our phones got different processors from different manufacturers?
I tried underclocking my CPU so my battery wouldn't die (even when it's plugged in it still slowly dies while I'm using it if I don't underclock a bunch) and every now and then (random intervals), the max cpu frequency would increase to something random (often 918 MHz, often 1188 MHz, and other values too). I've tried setting with AnTuTu as well as No-Frills, and completely removed every app from my superuser allow list, but nothing seems to prevent this from happening. After some research the only thing I can come up with is something about mpdecision/thermald, but I'm not sure if/how I should disable this or if I would need to replace this. I'm also not sure that this is the root of my issues. I'm running Eclipse ROM with leankernel.
Thanks,
Steve