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
I don't know what happened this problem just started 2 days ago. I've tried reinstalling rom. Installing a new one, and every time. Data wipe factory reset.
The problem is after about 15-20 seconds of phone being woke up it works perfect no problems. Then for so reason when I try to touch the screen I have to push a little harder than normal and tap a couple times. Only on the sides of the screen never in the middle, but that is not even the real problem. When the phone starts acting up, and I try to touch the any where on the screen every time I touch the screen my status bar comes down. Likes its over lapping. Especially when I'm trying to text. I go to press the "P" and right when I touch it the status bar drops. I don't know how to fix this. Like I said I reinstalled and downloaded a new rom. Is there a better and more efficient way to reset my phone? Please any help much appreciated.
Interesting, I have seen this as well, but only on OverClocked roms. If yours is over clocked, get one of the OC apps and set it to 528 or what ever ours are set to by default and see if it helps.
Usually goes away on its own for me. Haven't had it at all with DD or FroYo
Yes. please forgive spelling, but it started with the Pure Hero rom. I do believe it was OC'ed. Then I switched to the one I have been using for about 3 months. Alloyius*spelling*. That is oc'ed also and it didn't do the status bar thing for about 2 hours. I was excited I had my phone back. Then BOOOOM. Fuggin up again. Downloading set cpu now. Sure 528 is what it should be set or should I try some other #'s? Thanks for the help.
Damn the only set cpu app I know of is "Set Cpu" lol, and it will not accept my debit card for the 1.99$. Is there another generic cheap one I can use for about 10 secs to see if problem is fixed?
hyps87 said:
Damn the only set cpu app I know of is "Set Cpu" lol, and it will not accept my debit card for the 1.99$. Is there another generic cheap one I can use for about 10 secs to see if problem is fixed?
Click to expand...
Click to collapse
overclock
i think there is a free try one...
SETCpu is available somewhere here on XDA for free i think, unless the dev took it down.
Ok gaining some ground. Found the set cpu here on forums. going to try it thanks!
ok got the set cpu and did the preset for cdma hero. still doing it. is there anything else I can try to tweak? Any ideas appreciated
Mayb recalibrate ur screen Idk if it'll work but its worth a shot
Sent from my HERO200 using XDA App
would deleting the nandroid file do this? The phone still does this bs after reinstalling a rom.
Id run the ruu n if it does it on Stock return it and get a new 1
Sent from my HERO200 using XDA App
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.
Im having some issues with my vibrant and since today, everytime I lock the screen, then i try to unlock it, it stays black and nothing comes up or anything i just can seem to unlock it without holding the power button which causes the vibrant to restart. is anyone having this problem? Any solution to it other than formating maybe? Its rooted and I have a lag fix on it.
I'm assuming you've rebooted?
no i didnt. i didnt try to do that because i didnt want to lose everything. i was hoping its some app and i tried uninstalling some apps but still got the same problem. It keeps happing to me everytime since earlier today. you think that would work?
s15274n said:
I'm assuming you've rebooted?
Click to expand...
Click to collapse
I thought the same thing.
Ok. Something must be in the air. Exact same thing happening to me today.
Each time the screen times out the phone becomes unresponsive. Blank screen, soft keys don't light up. If I hold the power button too long it just reboots.
Rooted
Flashed lag fix
Clockwork recovery
Set CPU
Ya know what, as soon as I posted the details on my phones configuration it dawned on me that it could be a setcpu problem... Looking into it.
Set CPU was my problem. When I looked at the min/max they were both set at 19 out something ridiculously low like that. NO MORE SET ON BOOT!
I bought SetCPU but have not installed it on the Galaxy... I really don't see the point right now unless you want to underclock, and yes, it has been reported (perhaps fixed now?) that set on boot could cause issues.
I would just uninstall till we have a kernel we can OC.
OP, what would you lose by rebooting? Yes... I do believe that would work (and uninstalling SetCPU if you have it or change the aforementioned)
Set CPU profiles cause the phone to reboot and or freeze. See this thread forum.xda-developerscom/showthread.php?p=7808723#post 7808723
lagginess
Just to clear the setcpu is useless without a proper kernel i had it everything bogged down badly like reported went down to 19 from 10000. I would just take off the setcpu and wait for a kernel my phone def sped up after but thats my own experience.
I have a T-Mobile G2 that's been rooted and flashed several times (cm6, virtuous, supervillainz, senseginger, cm7) and through I think all of them I noticed an issue with coming out of sleep where the screen doesn't turn on
it still reacts to touch (ie I can slide to unlock), and the bototm touch keys light up, but there's no backlight or picture on the actual screen
sometimes it takes several off-on cycles to get it to work... I've recently noticed (and may be just imagining it) that the trackpad wakes it up with a much better success rate
details:
HTC Vision (G2)
Android 2.3.3
Baseband 12.28b.60.140eU_26.03.02.26_M
Kernel 2.6.32.28-cyanogenmod-g58d929e [email protected] #1
CyanogenMod-7.0.0-RC2-vision
any ideas would be welcome before I lose it and start poking at the kernel, radio and whatnot
thanks,
L
happens to me in virtuous, never happened to me on CM (i havent tried cm7 yet)
i believe its a problem with the cpu scaling, ie when the screen is off, processor drops to 245mhz and when the screen turns on, speed doesnt scale up fast enough
i usually underclock my g2 to 599mhz (governer set to on demand) but if i go any lower than that, getting the screen to come on becomes a frustrating project lol
I have the same problem, its so annoying especially when someone calls. Its been mentioned in other threads and I'm sure its a known problem but like u I need a fix. Stock ain't so bad as long as u can see who's calling and what time it is without trying to wake the phone 20 times. Please will someone finally answer this question? Or do we all need to revert to cm 6.1 or stock????? Small problem but big outcry.
Sent from my HTC Vision using XDA Premium App
thanks, I downclock to 200mhz on screen off
I'll up it and see if it makes a difference
Are you using the screen off animations in CM7?
Sent from my HTC Glacier using XDA App
screen off yes, screen on no
Try disabling the animations all together and see if it helps. Also are you OC'd above around 1.2ghz?
Sent from my HTC Glacier using XDA App
I've disabled them for now, gonna see if it helps...
yeah OC to 1516MHz, do you think this affects it?
There was a known issue with CM7 not too long ago where if you had the screen off/on animations activated in conjunction with being OC'd at around 1.2 or above it would cause the sleep wake issues. Took 3 or 4 on/off cycles with the sleep button on order to get the screen to come back on.
The solution was either to disable the screen animations or not to OC very high.
The other remedy recommended earlier is also legit. Set your screen off CPU profile to around 300 or 400mhz. Your problem should be solved by tinkering with all 3 variables. Failing that I would recommend a wipe/reflash and/or hitting up some folks in the CM7 thread to see if anyone else has that issue after tinkering with the above solutions.
Good luck man, I know those little bugs can be frustrating.
Sent from my HTC Glacier using XDA App
thanks for the tips...
I've now upped the minimum clock to 400 across all profiles and turned off the screen off animation... if that doesn't do it, I'll turn down the maximum clock, and if that still fails disable setcpu completely
I will report back any findings
allixsenos said:
thanks for the tips...
I've now upped the minimum clock to 400 across all profiles and turned off the screen off animation... if that doesn't do it, I'll turn down the maximum clock, and if that still fails disable setcpu completely
I will report back any findings
Click to expand...
Click to collapse
I see you have a strange problem.
I use 275mhz when sccreen is off and about 476 mhz when screen is on and nothing like this has happened to me.
Sent from Mars
Seems like nature of the beast. I get it too. Are yall using setcpu? I think its an issue with it. U might try cputuner and see what happens. But it rarely happens now that i set my setcpu to conservative or smartass.
Sent from my HTC Vision using XDA Premium App
this is indeed an issue with downclocking the phone on screen off profile... as soon as I set the screen off profile to anything below the stock 806 mhz, the issue appears
I've reenabled both screen off and on animations, the issue still hasn't reappeared... so it's the downclock :/
I have seen it on Sense ROMs but not CM7, doesn't clocking your phone at 800 when display off eat up a lot of battery also?
I am, unfortunately, not that techno-savvy when it comes to cellphones. But I am having the same problem.
The most I get is a bit of back light, but everything else about the phone seems to be working. Is there anyone who could possibly help me figure out how the hell to fix this?