Related
i had SetCPU installed on my phone, and when the phone would shut the screen off, by timing out or being locked, it wouldnt wake up from sleep.. i know at least one other person this has happened to, but removing SetCPU got rid of that problem.. does anyone know whats up?
You're lucky. SetCPU didnt even work on my SGS. It just FC'd everytime I loaded it. I didnt have root, which probably accounts for this issue, however it should still load up - just with locked speed setting bars.
I had the exact same problem you have mentioned below. I also get this issue with the autokiller app.
soraxd said:
i had SetCPU installed on my phone, and when the phone would shut the screen off, by timing out or being locked, it wouldnt wake up from sleep.. i know at least one other person this has happened to, but removing SetCPU got rid of that problem.. does anyone know whats up?
Click to expand...
Click to collapse
Sent from my GT-I9000 using XDA App
I'm pretty sure that SetCPU won't work with the SGS as things stand, root or not, for changing the clock rate (unless that built-in thingamagig for unlocking HTC phones' clock rates works).
Did you make sure no default profiles were set up when you installed SetCPU that were set to underclock the CPU or do anything else weird when the phone goes to sleep/is idle? That would be a good place to start.
If anyone could get me a log (force close/crash) or a /proc/last_kmsg (reset) that would be great.
coolbho3000 said:
If anyone could get me a log (force close/crash) or a /proc/last_kmsg (reset) that would be great.
Click to expand...
Click to collapse
You, sir, are a credit to this forum.
coolbho3000 said:
If anyone could get me a log (force close/crash) or a /proc/last_kmsg (reset) that would be great.
Click to expand...
Click to collapse
I'm sure someone's probably told me before, but how would we do this?
I installed SetCPU, I have root, but it just FC all the time
When rooted setup works fine as long as you just use it for monitoring and don't change the profile
Sent from my GT-I9000 using XDA App
Okay, that's odd. It's worked this time, although I did nothing different.
coolbho3000, tell me what I need to do to send a logcat and I'll use profile to see if it crashes. For me, profiles are rather important, when the screen is off I want to limit it to like 200mhz or something.
i figured out why SetCPU makes my phone never wake up, the settings i was using was ondemand 100 min 1000 max. SetCPU is set to 100 in standby and this is just too slow and puts the phone completely to sleep.
ive since moved up the phone to 400 min and ive gone a day without any sleeping.
and SetCPU works fine on my phone, and a few friends who have the phone aswell, this was our only problem, and i dont believe it was a problem, its just the way the app is designed, to give full control, leaving the only room for error on our hands..
but still an fyi would be nice lol.. i read the entire huge description of SetCPU, like a half hour read
Try setting the scaling to 'ondemand' or 'performance' if it was set to 'conservative' as default (mine was).
AndyCr15 said:
Okay, that's odd. It's worked this time, although I did nothing different.
coolbho3000, tell me what I need to do to send a logcat and I'll use profile to see if it crashes. For me, profiles are rather important, when the screen is off I want to limit it to like 200mhz or something.
Click to expand...
Click to collapse
Logs can be done by getting the Log Collector app from the Android Market. Or, you can plug it into a computer with ADB and run:
adb logcat
I'm interested in the FC crash and why it works for some and not others.
Thanks
In fact, everything seems to work for me too....
I'm especially interested overclocking this thing, as it's the 45nm ARM CPU released in an Android phone en masse. I might get myself a Vibrant if it gets rooted.
The whole problem is that the default is conservative... changing it will cause phone to freeze.
Sent from my GT-I9000 using XDA App
lgkahn said:
The whole problem is that the default is conservative... changing it will cause phone to freeze.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Then change the Freq Step in Advanced to 100%, should have the same effect as ondemand.
lgkahn said:
The whole problem is that the default is conservative... changing it will cause phone to freeze.
Click to expand...
Click to collapse
Ahh, I was getting the 'not waking' issue that was mentioned before.
coolbho3000 said:
Then change the Freq Step in Advanced to 100%, should have the same effect as ondemand.
Click to expand...
Click to collapse
This will fix it not waking? Is this better than making the minumum to be 400mhz?
When it was not waking, I changed all the minimums to 200mhz, but it was still dropping to 100mhz? Why would it do this?
With my phone rooted didn't work on first install, whenever I launched it, it kept crashing so I uninstalled and installed back and it works perfect
I went through the whole resetting to factory defaults several times until I determined not coming back from sleeping was setcpu.
I do not think it is a crash problem.
I had the scaling set to ondemand.
Do we know what the minimum CPU speed is for the samsung? I had it on 200 and still had a problem. If I have min at 400 is there a point in using setcpu, because the existing OS will scale for us?
I really loved the product, but I need to feel like we have a more confident answer to this problem.
Kudos to coolbho3000 for a great product. For the avoidance of doubt, I purchased the product.
I'm having a lot of trouble with this app too...
So I'm returning it until someone can post some settings that work flawlessly
Hey evweryone,
Found a VERY strange issue, that seems to be affecting Captivate users as well. This is my second phone that has had this issue, so its not isolated.
The phone works fine when using it, but when it goes to sleep, occasionally (more and more frequently it seems) it will actually turns off. Meaning, when I pull the phone out of my pocket, its off. Has occurred 3 times today, and I'm SURE i didn't accidentally hold the power key.
First, I thought it was the OC kernel, so I reverted to JAC's non-OC kernel, still turns off. Reverted to stock kernel, still happens. I have a slight hunch maybe SetCPU may be causing it to sleep incorrectly, so I un-installed that.
Anyone else run into this issue? Its a PITA when your phone randomly turns off, cant rely on it at all. Thanks!
EDIT: Phone was ON while sitting on my desk while I was writing this, tried to wake it up....it was off
It happened to me too, and I believe it was because of Set CPU, I had it set low when it went into sleep mode and it would shut down, and i would need to remove battery and start it up again. So I just deleted the profile and it seems fine now.
Puushiki said:
It happened to me too, and I believe it was because of Set CPU, I had it set low when it went into sleep mode and it would shut down, and i would need to remove battery and start it up again. So I just deleted the profile and it seems fine now.
Click to expand...
Click to collapse
I will try that and see. Anyone else have this issue on any Galaxy S based device (Captivate, Vibrant or Generic Galaxy-S)?
Oh btw, I have the Samsung Vibrant
Puushiki said:
Oh btw, I have the Samsung Vibrant
Click to expand...
Click to collapse
Okay, confirmed by one user. There is a large number of captivate users having this same issue, and a discussion about it in a SetCPU forum (Link ).
No problems here, stock ROM + RyanZA using SetCPU since day one.
Two profiles: conversative
Battery <100%: 400 min; 1000 max
screen off: 400min; 400 max
Are you guys using SetCPU for OC'ing, or for scheduling?
I was having the same issue, wasn't sure what it was and was going to return my Vibrant, and with that in mind had wiped the phone and gone back to stock. Due to a delay in getting to the store, I did re-install things (hey, I do need my phone) and found that the issue had stopped. I did have SetCPU on originally and have not re-installed it, but it's difficult to recall if I had SetCPU on before or after the issue started. I suspected it could have been SetCPU and since I didn't really feel the need to use it, I just didn't bother to install and and wanted to see what would happen.
It did happen again yesterday, but the phone seemed to just lock up on me while I was using it (was as I was using Navigate, got to my destination, locked up, then shut off, more or less), so it might have just been another fluke due to overheating or something.
Anyway, the problem that I had was that I couldn't get the phone to come back on without having to remove and replace the battery. But fortunately, other than yesterday, the issue has not happened since the past Friday (where it happened 4 times that morning vs once per day the 3-4 days prior). The inability to turn it back on might just be an issue with my phone (and it only happens after this force shut down).
ytj87 said:
Are you guys using SetCPU for OC'ing, or for scheduling?
Click to expand...
Click to collapse
Mainly for stress testing, as the OC kernel doesnt need to be configured to OC, its already running at 100/1200. Mainly for scheduling and stress testing. Occasionally for detailed info about CPU (temp, current speed, etc). Hopefully this issue\bug can get worked out, cause SetCPU is a GREAT app.
I can almost guaruntee that it is SetCPU causing the issue. Make sure it is set to "Conservative" mode and try not to use the "Screen Off" profile.
hockeyrcks9901 said:
I can almost guaruntee that it is SetCPU causing the issue. Make sure it is set to "Conservative" mode and try not to use the "Screen Off" profile.
Click to expand...
Click to collapse
Had NO issues today, seems SetCPU was the culprit. Thanks!
Well I have SetCPU for Screen Off Conservative at 400, and haven't had a problem yet, so I'm not sure
Puushiki said:
Well I have SetCPU for Screen Off Conservative at 400, and haven't had a problem yet, so I'm not sure
Click to expand...
Click to collapse
I think it's kind of hit or miss. Some people have no issues with it and others do. My first phone would not wake from sleep if I was using the "Screen Off" profile. I haven't tried with my second phone as I've noticed it seems to be really good at lowering **** speed on it's own.
I have had the same problem and am using SetCPU. I love it, but this shutting down in sleep mode thing is driving me crazy. Gonna try to turn off notifications and move to conservative and will report what happens.
I use SetCPU regularly on my Captivate and only see issues if I change the governor or polling interval, or if I use profiles.
Sent from my SAMSUNG-SGH-I897 using XDA App
hockeyrcks9901 said:
I think it's kind of hit or miss. Some people have no issues with it and others do. My first phone would not wake from sleep if I was using the "Screen Off" profile. I haven't tried with my second phone as I've noticed it seems to be really good at lowering **** speed on it's own.
Click to expand...
Click to collapse
**** speed aye?
Don't use setcpu!!!!
Sent from my SGH-T959 using XDA App
xaisomboun said:
**** speed aye?
Click to expand...
Click to collapse
lol. That's swype for ya...
Typos and other gibberish courtesy of Swype
I have this problem several times a week. The phone is NOT rooted. What are my options for curing this problem besides rooting?
Thanks for the help.
Samsung Vibrant, Android 2.1, T-Mobile
I read somewhere that Galaxy S users should NOT use conservative and use on demand instead for this reason... not sure though.
I found a nice little work around until we can get a better solution in place.
All we need to do is grab a copy of SetCPU and set a profile.
Download SetCPU from the link above, put it on your sdcard and install thru myfiles.
On the first launch you will need to configure SetCPU.
Once it's done installing, open it up from the apps drawer.
Scroll down and tap "Autodetect Speed Recommended".
It will now ask for root permission, accept.
Do NOT set any other settings in SetCPU
Tap on the profiles tab.
Tap "Add Profile".
Set the options like this;
Condition: Charging AC/Full
Max: 1000000
Min: 100000
Scaling: Conservative
Priority: 100
Tap "Save"
Check "Enable"
Do NOT set any other settings in SetCPU
Press Home
Never open SetCPU again, use Voltage Control to setup your oc/uv settings.
Thank you.
Thank you for this.
I had a sleep death occur under those settings a while back when trying it for glitterballs... is that something that only works on the cog4 kernel?
Athailias said:
I had a sleep death occur under those settings a while back when trying it for glitterballs... is that something that only works on the cog4 kernel?
Click to expand...
Click to collapse
It's worked flawless for me for two nights in a row.
Yeah, we definitely tried this and it still happened. Athailias even did a 400 min and it still happened.
Awesome, DG
Setting the minimum frequency to 100MHz wouldn't do anything anyway because that is already the minimum frequency allowed, so this isn't an issue of the clock going below 100MHz. I know it worked for you, but there are times when I can leave my phone plugged in on the wall charger overnight and it doesn't happen, and time when it just gets to 100% on USB and it dies.
After we create the profile, do we need to click on enable??
thecellx said:
After we create the profile, do we need to click on enable??
Click to expand...
Click to collapse
ahh, yes, added to the op
How about USB charge
Hi,
I understand you wrote twice not to add any other setCPU settings.
The settings you put, do they only apply to AC charges? How about charging via USB. Should we also create a profile exactly the same as the one you listed but Full charge/USB as well?
Sorry for the noob question.
designgears said:
Never open SetCPU again, use Voltage Control to setup your oc/uv settings.
Click to expand...
Click to collapse
Does that include not using the SetCPU widget to see my current settings?
zrx12mike said:
Does that include not using the SetCPU widget to see my current settings?
Click to expand...
Click to collapse
nah, you can do that.
I too have experienced changing death with these settings enabled. So the plot thickens.... . But thank so much for the ROM.
I have to agree that this fix does not work on my cappy. Thanks anyways
Sent from my SAMSUNG-SGH-I897 using XDA App
UltimaX said:
I have to agree that this fix does not work on my cappy. Thanks anyways
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
yea DG voodoo based kernel allows the usage of setcpu ( I dotn know about yours) the usage of setcpu alone will cause sleeps of death on seti's kernel ..
DAGr8 said:
yea DG voodoo based kernel allows the usage of setcpu ( I dotn know about yours) the usage of setcpu alone will cause sleeps of death on seti's kernel ..
Click to expand...
Click to collapse
It never happened before until flasing cog b7 and after trying the fix it went out 3 times in one day so i'm just gonna move on to the next version
Guys, it actually looks like charging death isn't a software issue, and can't be fixed with software on affected units. Look at this post regarding AT&T releasing a statement listing affected models that have the "power cycling issue".
http://forum.xda-developers.com/showpost.php?p=10025031
It states that if your IMEI ends with ....5394 or lower, or was made before Nov. 6th, 2010, you MAY have the turning off issue at some point. According to the text in this statement, At&T is exchanging any affected model. Mine is in this range, and I've had charging/sleep death on every ROM/kernel I've used, from stock 2.1 to Cognition/Perception. Thank danalo1979 for posting this!
Fuuuuuuuuuuuu, like two, three weeks ago I thought about posting a poll to see if it was a hardware issue, but then I thought, 'No glitterballs, this is some **** you can figure out.' Actually, I think I'll still post my probably not a fix fix, but, hey, at least it (might) be over.
Sent from from my brain using thumbs 2.0.
Thank u for this info. Really appereciate it . I have the issue and wide like to try the exchange program. However I am a little concerned abt. my phone's imei #. I think after flashing Acura ROM ..it messed up my imei and product id. I restored the product id, but unable to restore imei. Will it be an issue if I send back my phone with bad imei?
Sent from my GT-I9000 using XDA App
I had one of the early phones ATT replaced with a new one (010) , No problems since.
Sent from my SAMSUNG-SGH-I897 using XDA App
Stock samsung fascinate rooted. When ever i set the set cpu to anything but conservative it will just power off. This dosen't happen right away. I would just go about my day and I when i'd try to use it the phone would be off. Now this will do it all day unless I set it to conservative and no problems at all. i would like any help I should recieve. Thank you.
the name is Al Usher....
Since your running stock and not an overclocked kernel I don't think theres any benefit from using set CPU.
alusher said:
Stock samsung fascinate rooted. When ever i set the set cpu to anything but conservative it will just power off. This dosen't happen right away. I would just go about my day and I when i'd try to use it the phone would be off. Now this will do it all day unless I set it to conservative and no problems at all. i would like any help I should recieve. Thank you.
the name is Al Usher....
Click to expand...
Click to collapse
Are you using profiles?
uslacson1 said:
Since your running stock and not an overclocked kernel I don't think theres any benefit from using set CPU.
Click to expand...
Click to collapse
+1. SetCPU is useless with a stock kernel. Flash a custom kernel if you want to see any results (otherwise you cannot change the governor, min/max, or set profiles).
thanks I will go with a new kernel..now i will do some homework
If I lock my phone, sometimes it won't unlock. It essentially just shuts down. I've reinstalled 2.2 once, and just went to 2.4 last night. When this happens, I have to pull the batter and restart. And yes, it does this with both versions. I wiped cache, etc upon installing the ROM as well.
jbjarko said:
If I lock my phone, sometimes it won't unlock. It essentially just shuts down. I've reinstalled 2.2 once, and just went to 2.4 last night. When this happens, I have to pull the batter and restart. And yes, it does this with both versions. I wiped cache, etc upon installing the ROM as well.
Click to expand...
Click to collapse
When you say it won't unlock...is haptic feed buggy and it seems unresponsive and sporadic?
jenisiz said:
When you say it won't unlock...is haptic feed buggy and it seems unresponsive and sporadic?
Click to expand...
Click to collapse
Not really, seems normal to me. Should I try turning it off, and see if that fixes it?
By any chance, would you happen to be using setcpu? I ask because I have noticed this happening on any rom I use, but changing my setcpu values for when the screen is off has pretty much solved it.
Sent from my SCH-I500 using XDA App
kdaz said:
By any chance, would you happen to be using setcpu? I ask because I have noticed this happening on any rom I use, but changing my setcpu values for when the screen is off has pretty much solved it.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I've been using setcpu with every setup on this device and haven't ran into any problems. Only problem I would see with this, is if you set the levels way to low...that will induce locking up the system.
Ok, downloaded setcpu, what specs should I put it at?
jenisiz said:
I've been using setcpu with every setup on this device and haven't ran into any problems. Only problem I would see with this, is if you set the levels way to low...that will induce locking up the system.
Click to expand...
Click to collapse
well thats basically why i was asking..if i set mine to 200 max and 100 min when screen is off, it sometimes doesnt come back on. i currently have it set to 400 max and 100 min when screen is off and havent noticed any problems.
kdaz said:
well thats basically why i was asking..if i set mine to 200 max and 100 min when screen is off, it sometimes doesnt come back on. i currently have it set to 400 max and 100 min when screen is off and havent noticed any problems.
Click to expand...
Click to collapse
IMHO...that's really low.
Where do I set it for screen off? All I have are two sliders?
jbjarko said:
Where do I set it for screen off? All I have are two sliders?
Click to expand...
Click to collapse
you have to go under the profiles tab and enable then you can set different profiles.
Still doing the same deal. SetCPU is at 400-800 during screen off. Haptic feedback is off.
Any ideas?
I'm not even running SetCPU and I get this happening.
Anyone have any more suggestions? It's not a huge deal, but it sucks watching my battery drop 10% every time I have to pull the battery and reboot.