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.
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
Aside from being able to Wirelessly Tether my 3G connection from my Vibrant, I wanted to also control my CPU speeds. But with SET CPU, I tend to come across a particular problem. I would underclock to 100000 (min&max) with the screen off, but as a result, the screen won't turn back on and I would have to take the battery off and restart my phone. Clocking it to 400000 (both min and max) screen off leads to the same problem. Is anyone else going through the same situation? If not, what are you setting your CPU to, in regards to both screen on and off?
I have it set to 400MHz max/100MHz min for screen off, and it wakes up just fine so far.
What is your Governor setting? I was told to put it in "Conservative" for Vibrant.
lqaddict said:
I have it set to 400MHz max/100MHz min for screen off, and it wakes up just fine so far.
What is your Governor setting? I was told to put it in "Conservative" for Vibrant.
Click to expand...
Click to collapse
Yeah I have all my profiles set to conservative. Do you guys think it has to do with the priorities, cause I have all of them set to 100.
It could, since there is no telling how to prioritize the settings, hardware/software might get confused.
you know I just noticed I got the same issue, sort of.
I have multiple profiles setup, and one is for charging via USB 800max/100min.
If the screen is off (400max/100min), and I connect the USB cable, guess what happens, three finger salute gets it back, hmmm.
OK I got it working for those who are having the same problem as I. All I did was I made my screen off frequency 200max/100min. For both charging and battery use, I have my cpu set at 1000max/800 min. It works flawlessly and I am noticing an increaSe in battery life...
Sent from my SGH-T959 using XDA App
OverClock?
I used SET CPU on my G1 and really loved the new life it gave my old hardware. I would like to open it up and see what my Sammy Vibe can really do. Is there a way to get some real OVER clocking?
Battery life is really not an issue for me so far.
Halieus said:
I used SET CPU on my G1 and really loved the new life it gave my old hardware. I would like to open it up and see what my Sammy Vibe can really do. Is there a way to get some real OVER clocking?
Battery life is really not an issue for me so far.
Click to expand...
Click to collapse
we need a kernel that will enable it. its apparently not possible on the stock kernel...
I have been having the exact same freezing issue when the screen times out, I'm unable to revive the phone without pulling the battery. I have tried many different setting in Setcpu including those posted here. I finally just uninstalled it and everythings right again. Best to avoid this app for now.
Hey man i did that and i still did not work any other way to set it up.
Vibrant wont come out of Blank Screen
I used Set CPU and put it to the max 1000 and then the max on the other readings it forced closed and after the tmobile and Galaxy animations it goes to a blank screen.
Yeah, I uninstalled it after a week because it was just too unstable. I was getting freezes several times a day, which is unacceptable. Other people might have better luck, but my phone did not like it at all.
So far the only way I can get the program to work 100% is to not have any screen off profile. If I just set it to 1200 max - 200 min / conservative it works fine. Yet once I use profiles and screen off at 100, 200 or 400 it won't turn back on. Every morning it's the same thing, battery pull.
I have similar problem. As long as I am not using "Profiles" at all it is fine. Playing with profiles setting for a while, but not being able to make them 100% stable.
Another thing, if your screen does not come on, you don't have to pull the battery out. Just keep holding on/off button for 5-7 seconds, it'll reboot. It's not a complete freeze, I believe only display system (whatever it is) fails.
Stuck at Recovery Mode
Guyz,
I have firetrap sugar on Spice Mi300. Installed Set CPU.
Tried entering the recovery mode, the phone gets stuck at 1st screen with a line "Enter recovery Mode" displayed on top.
Please help.
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.
I'm running the twilight zone v1.1.1 kernel and recently my phone has gone to a "death sleep" repeatedly when not plugged in. (when plugged in via usb on computer or wall wart its fine). I end up having to remove the battery and putting it back in to get it to work again (till the next time it falls asleep).
Is this possibly a kernel issue? a kernel controlling voltage issue? (under volting on battery?). A hardware issue? I've been running this kernel for a while now and its only started happening in the past few days.
I figure I'll try out stock soon to see if its a problem (and if it is, as I pay for TEP, I'll just take it into a store), but wanted to check here first
thanks.
thetoady said:
I'm running the twilight zone v1.1.1 kernel and recently my phone has gone to a "death sleep" repeatedly when not plugged in. (when plugged in via usb on computer or wall wart its fine). I end up having to remove the battery and putting it back in to get it to work again (till the next time it falls asleep).
Is this possibly a kernel issue? a kernel controlling voltage issue? (under volting on battery?). A hardware issue? I've been running this kernel for a while now and its only started happening in the past few days.
I figure I'll try out stock soon to see if its a problem (and if it is, as I pay for TEP, I'll just take it into a store), but wanted to check here first
thanks.
Click to expand...
Click to collapse
If I remember correctly, there were a lot of people having this issue with SFR and you shoudl check that thread for more info. However, long story short, this can definitely be related to underclocking and/or undervolting.
Are you using SetCPU to underclock? If so, set your minimum speed to 200 MhZ as I think that resolved it for most people.
ok, set to 200mhz (was at 100mhz) will see if that fixes it. thanks.
I'm having the same issue since flashing Emotionless Beast. Used Voltage Control to set to 200. Is there a way to keep the settings through a reboot?
ok, setting to 200mhz didn't seem to fix my issue, will probably try another kernel.
thetoady said:
I'm running the twilight zone v1.1.1 kernel and recently my phone has gone to a "death sleep" repeatedly when not plugged in. (when plugged in via usb on computer or wall wart its fine). I end up having to remove the battery and putting it back in to get it to work again (till the next time it falls asleep).
Is this possibly a kernel issue? a kernel controlling voltage issue? (under volting on battery?). A hardware issue? I've been running this kernel for a while now and its only started happening in the past few days.
I figure I'll try out stock soon to see if its a problem (and if it is, as I pay for TEP, I'll just take it into a store), but wanted to check here first
thanks.
Click to expand...
Click to collapse
Same thing happen to me a few time on twilight but since I'm been on genocide 2.0 kernel no problem for me genocide is the best for my phone
Try it out with jornaling on
Sent from my SPH-D700 using xda premium
I know this might sound stupid, but I had a problem similar to this the other day. It was only the screen was blank, but would still accept inputs on it. I could unlock the phone (using the TW lockscreen) and then, I was able to hold the power key and select reboot (on-screen location pressed from memory).
Is it just the screen, or the entire phone?
thetoady said:
ok, setting to 200mhz didn't seem to fix my issue, will probably try another kernel.
Click to expand...
Click to collapse
Hmm... Is it also undervolted? Might try changing that. FYI, I have also been using Genocide with no problems for a while now...
Pretty sure its the entire phone. tried dialing it from my desk phone and it didnt ring.
also, the epic's version of ctrl-alt-del doesn't seem to work either (just happened again). will be trying genocide when I get home.
thetoady said:
Pretty sure its the entire phone. tried dialing it from my desk phone and it didnt ring.
also, the epic's version of ctrl-alt-del doesn't seem to work either (just happened again). will be trying genocide when I get home.
Click to expand...
Click to collapse
Try genocide 2.0 kernel & when you use titanium backup don't re install the app &data just install the apps hit the thank you button if I helped you in anyway!
Sent from my SPH-D700 using xda premium
Until you figure out what works for your phone avoid all voltage changes and set minimum frequency to 200 Mhz and to set on boot. There are not enough advantages to over and undervolting to not have a working phone.
Sent from my SPH-D700 using XDA App
kennyglass123 said:
Until you figure out what works for your phone avoid all voltage changes and set minimum frequency to 200 Mhz and to set on boot. There are not enough advantages to over and undervolting to not have a working phone.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
That's good advice. Didn't UV and OV cause some bricks once? My phone does that death sleep thing when I was at 100 Mhz on Genocide. Set it to 200 and no more problems.
uSo things were a bit more involved.
My phone died totally (major FC avalanch on startup), so I reimaged it, installed genocide and restored from backup (over an hour! w/ data) and its behaving well now.
though I do hate the spam genocide puts in the boot image.
from what i've noticed
it happens when closing the keyboard under certain circumstances
possibly only during sms messaging
i was able to duplicate a reboot sending/receiving a couple messages today
i had just received messages and then closed the keyboard
immediately i noticed the samsung logo
just seeing if this strikes anyone else's memory as being the point of occurrence
this was with eh17 and mkasick kernel
i have also seen one random reboot with my phone just sitting there
that was eh17 with eh17plus kernel from chris41g
but i also got the sms keyboard close reboot then as well at least once
i posted a kmsg for mkasick but he didn't see anything
just hoping to document the occurrences to help narrow in on the exact issue.
save the whining for another thread...thanks
i have a lot of bloat removed.
launcher pro
no animations
2 minute screen timeout with keyboard set to same as screen
auto rotate off in both settings and launcherpro
stock sms app
Sounds more like you have a loose battery. Random reboots occur in GB leaks when phone is sitting idle. It was found to be a voltage and deep sleep transition during partial wakes that was causing it. The fix was posted in this forum using Tegrak and SetCPU combination.
kennyglass123 said:
Sounds more like you have a loose battery. Random reboots occur in GB leaks when phone is sitting idle. It was found to be a voltage and deep sleep transition during partial wakes that was causing it. The fix was posted in this forum using Tegrak and SetCPU combination.
Click to expand...
Click to collapse
+1
Here's what works for my phone:
SetCPU
OnDemand 100mhz/1000mhz
Screen Off: 100mhz/200mhz
Tegrak (Make sure you buy it for the newest version.)
OnDemand 100mhz/1000mhz
100mhz @ 1000mV
200mhz @ 1025mV
Edit:
If it is a loose battery, you can always jam some cardboard back there to make sure. I can't remember where the link is to the SetCPU/Tegrak, so I just posted my own settings for ease. It does seem to vary per phone, just like overclocking/undervolting, so a bit more reading/tinkering might be required.
my reboot issues happened a lil over 2 minutes into a phone call on every rom I tried so I went back to eg22
The fix for reboots is a page or 2 down here in General called "Possible fix for random reboots"
Sent from my SPH-D700 using XDA App
eigerzoom said:
from what i've noticed
it happens when closing the keyboard under certain circumstances
possibly only during sms messaging
i was able to duplicate a reboot sending/receiving a couple messages today
i had just received messages and then closed the keyboard
immediately i noticed the samsung logo
just seeing if this strikes anyone else's memory as being the point of occurrence
this was with eh17 and mkasick kernel
Click to expand...
Click to collapse
Also running "stock" EH17 with the mkasick compiled kernel, and haven't had any reboots in the last 4 days. I use the keyboard to send sms many times without problem. Sounds like a mechanical problem to me. I've heard other people with loose batteries or worn battery contacts have exactly the same issue. Try wedging a thin piece of cardboard into the space along the bottom of the battery and see if the problem goes away.
definitely a loose battery
i'm dumb
i'm running the 3000mah with extended door
i just set it down with a bit of extra force and yep reboot
thanks people
didnt know there was a fix for the random reboot.. i have 2 try that out its funny that it doesnt happen while plugged in
makipsee said:
didnt know there was a fix for the random reboot.. i have 2 try that out its funny that it doesnt happen while plugged in
Click to expand...
Click to collapse
It doesn't happen while plugged in because it runs constantly at 100 Mhz and does not go into deep sleep. That is how we narrowed down the issue in that other thread and added the screen off profile to SetCPU.
Here is the thread:
http://forum.xda-developers.com/showthread.php?t=1276417
kennyglass123 said:
It doesn't happen while plugged in because it runs constantly at 100 Mhz and does not go into deep sleep. That is how we narrowed down the issue in that other thread and added the screen off profile to SetCPU.
Here is the thread:
http://forum.xda-developers.com/showthread.php?t=1276417
Click to expand...
Click to collapse
ahhh ok... yea i was looking in that thread before thanks
I fixed my loose battery by sliding a half credit card ... Actually an old Kroger card... In the back of the phone. Tighter and zero reboots. Specific to the battery anyway. Cm7 does not reboot.
Sent from my SPH-D700 using XDA App
For me at least, the mkasick compiled kernel on EH17 doesn't reboot either. With the standard kernel it rebooted within a half hour of install.