Hello all,
Got SUPER pissed off at skype support because they give me canned responses and do not read what I spent the time to write. I have an HTC Sensation running Revolution HD newest version.
I have had the problem on EVERY android device I have ever owned and skype. After I install it, the screen never sleeps. I made sure I logged out, exited, and also did "force stop" to see if it would make my screen sleep. No good.
After I uninstall the application, my screen sleeps normally. wtf workaround?
Never noticed this myself, how do you know it's not sleeping? Or do you mean the screen won't even turn off??
I'm not sure what you mean either. Mine will turn its screen off and apparently sleep with skype running just fine. At least it's not having any serious battery drain, etc. (2 days without a charge and I'm at 50% or so)
Related
Random shut down solution! At least for me.
My phone shuts down pretty much 2-5 times a day since i got it. No matter what I do to it. But I tried the app, load monitor and enabled WAKE LOCK and my phone hasnt rebooted in 4 days!
Anyone else had similar experience.
Sent from my SAMSUNG-SGH-I897 using XDA App
Umm, not meant in an asshat way at all man, but your real solution is to take that sucker back. I wouldn't put up with that at all. Bad phone. Just my opinion.
From a phone on an app
I have to agree with the post above mine. I believe it's a hardware issue and that you should return it for another one. I have two captivates and neither I've of them have ever had the random shutdown issue.
Truth is, the phone is bad. Ask for a warranty replacement. I went through 2 phones until I got a good one with no issues. A perfectly good working phone should never randomly shut off as mine were doing before (4-10 times a day) Even setting Set-CPU to 1000mhz 100% of the time didn't fix the other phones I had. Hell, even leaving the screen on the entire time one of them still shut off once.
Others have found that the "wake lock fix" has not worked (although it initially seemed promising). If your shutdowns recur, exchange the unit. That's been the only remedy to date.
Did you have set cpu installed? That's what happened to me after installing set cpu. Sometimes it would lock up after the screen went off & sometimes it would just reboot randomly. I got around this by setting the min clock speed to 200mhz. I think set cpu sometimes undervolts the cpu when scaling especially at 100mhz & at 1000mhz when the screen is off. If it did that stock then I would definitely return that pos! Wake lock will kill your battery life.
Sent from my SAMSUNG-SGH-I897 using XDA App
Well we will see. I was in the process of a rma and just got the phone last night.
I see if the new one has any issues. By the way this will be my 4 th phone(3 through the first month, this one through rma). So the get another phone idea kind of sucks.
Just a curser glance at the back of the rma phone and I can see its different. So maybe I'll get lucky on it.
Sent from my SAMSUNG-SGH-I897 using XDA App
. .
Same here, I'm in Australia, I bought the phone from the US, It used to shutdown 3 - 5 times a day, especially when it's fully charged. Wiped the phone (Internal and external) and now it's solid stable. no special apps or settings or whatsoever. It's a little bit weird though.
I think the problem may be from the phones overcharging. Mine was brand new and I left it on the charger overnight then took it off the charger in the morning and when I came home from work it was powered off. It may be a safety feature built into the phone and not a defect. I had it happen to me twice when I didn't take it to work with me after charging it all night the night before.
Sent from my SAMSUNG-SGH-I897 using XDA App
I leave mine plugged in all the time overnight and it has Never booted off
Sent from my SAMSUNG-SGH-I897 using Tapatalk
galaxyjeff said:
I think the problem may be from the phones overcharging. Mine was brand new and I left it on the charger overnight then took it off the charger in the morning and when I came home from work it was powered off. It may be a safety feature built into the phone and not a defect. I had it happen to me twice when I didn't take it to work with me after charging it all night the night before.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I thought the same, but last night I forgot it on the charger with no problems at all, No shutdowns... Strange...
It happens to my Samsung S Vibrant and I *think* I can reliably reproduce the issue, at least on my phone.
Steps:
1. Go to a spot where you know it has failed, for me this is my office because it has bad reception and it seems to only shutdown for me when there is bad reception.
2. Make sure 3G is turned on and open an application that uses data.
3. Wait for the phone to sleep, do not hit the power button or anything to make it sleep (not sure if this step matters)
4. Wait ~30 mins without touching the phone (You can play music with it while this is happening if you want, the music will stop to let you know it's failed)
5. Try to wake up your phone, it is now dead.
I'm not sure this will work for everyone but last night I could reproduce 3 shutdowns in an hour and a half. And reproduced about 7 shutdowns yesterday when my phone only usually shuts down ~2 times a day.
I'm testing out all kinds of software permutations (disabling stuff, installing things like Captivate Keep Alive). Nothing has worked so far, my guess right now is that the problem lies in the Pattern Unlock feature so I have disabled it, I read that on a forum somewhere.
My guess is that if you have too much running in the background it might take up too much cpu or ram so that when the phone tries to come out of sleep it can't get enough CPU power to come out of sleep and therefore gets stuck in a kind of limbo. This theory could then be releated to the SetCPU problem when you set the CPU too low when it sleeps the issue occurs.
Moral of the storey is I have no idea what's going on, but please post if this works or doesn't work. Maybe it will shed some light on the issue, or you can tell me I'm wrong so I can give up. Let me know if you have Pattern Unlock enabled...
Luckily I'm not past the 30 day mark and I'm exchanging for a new Vibrant tonight. Wish me luck!
UPDATE: It's not the fault of Pattern Unlock, just reproduced the issue with it turned off.
UPDATE #2: Got my second Vibrant, just reproduced the issue within 30 mins of getting into work in the morning.
My Captivate used to shut off once every 2 weeks. Now it's doing it 4 times a day. However, I just found this app:
http://uk.androlib.com/android.application.org-bluesteel-cka-qxnim.aspx
Looks promising. I hope this works.
My wife's stock Captivate has been doing this for a week or two (our phones are about 6 weeks old). My rooted Captivate has -not- been doing it. We both have the same "plug it in all night" charging pattern. Hers will be going back shortly.
Jack45 said:
Others have found that the "wake lock fix" has not worked (although it initially seemed promising). If your shutdowns recur, exchange the unit. That's been the only remedy to date.
Click to expand...
Click to collapse
Tha'ts not true.
My phone was working fine. Then I rooted it. Then I started sideloading bunch of apps. Randon shutdown started to happen. I started tracing back and deleted apps one by one. Didn't work. Replacing the phone was out of the question because I live in Canada and bought the AT&T phone cash off a seller.
SOLUTION:
if you have had SetCPU (or overclock app) and had it to anything to your phone, this is what you got to do.
Run the SetCPu again, and make sure that you do Max 200mhz and Min 200mhz.
Reboot the phone.
Then go into SetCPU, disable autodetect. Then uninstall app.
No more random shutdowns.
It is NOT a hardware issue.
I can confirm that the App stops my phone from shutting down.. unfortunately I have to set it to 65% charge for it to work (whereas others can leave it on default 80%).
Found my issue, it was happening when my phone was jumping between the 850 mhz band and the 1900 mhz band. It would freeze and only happen in areas of bad signal. Locked it on to the 850 mhz band and havent had a freeze since.
100 hours of uptime and counting
http://forum.xda-developers.com/showpost.php?p=8612667&postcount=386
I have also heard that some phones experience the issue when fully charged and that putting a wake lock on your phone with captivate keep alive will solve the problem. These are two independant issues.
i'm not really that knowledgeable about how the phone interacts with different bands, but i'm trying to fix this problem as well and i'll try anything. are there any side/adverse affects to locking it onto a single band?
Has anyone tried removing the sim? to see if it still turns off?
The problem im having is when its near full and goes to sleep i need to turn it back on (like it shuts off) but i tried removing the sim and has not had this problem
I've had the phone for a week without this happening, but yesterday when I went to check out the locations app it gave me some GPS error which I fixed up, but then decided I didn't want to use the app so I disabled the GPS satellite and dock feature when plugging in the phone for charging. Last night I realised this was happening a few times so I shrugged it off and just reset the phone which seemed to work for a bit, but then after leaving the phone on lock all night with no wi-fi, bluetooth, GPS or anything, I wake up to see the phone, after 8 hours of standby, to be at about 10% battery. Right now it's on charge, and a couple of minutes ago without touching it the screen turned on for exactly 1 minute.
At first I thought it was because of the locations app, but this doesn't seem to be the case since I force stopped it and it's still doing this.
What could be causing this? It's not that big of a hinderance, but when the phone quickly drains itself of battery because of it gets a bit annoying. Should I just wait it out for the android 2.4 update and hope it fixes itself? I was thinking of rooting the phone and going on from there to see if there's a method that'll fix it, but with the update coming in a couple of months I'd rather refrain from it (even though I have no idea what rooting would do in this situation).
e: locations seemed to have started itself up again. I think it IS the application doing this.
Boomey said:
I've had the phone.
Click to expand...
Click to collapse
Oh magic all knowing 8ball, what phone does he have?
*shakes magic 8ball*
*8ball glows and shows letters*
Plug your Moto RAZR into your computer, install android sdk, use adb logcat to read out the log files.
When your screen turns on again there will be some indication who requested your phone to wake up.
Sorry disregard that post. The Moto RAZR doesn't run android, so this can't be the solution...
I posted that in the HTC Desire HD Q&A forum, no idea why it was moved when it's a question about the phone. :\
But yeah, HTC Desire HD. I half expect no solution but I can still be hopeful.
In that case my suggested approach with adb logcat would work .
seems to be really very complicated and understand how to use the method. sorry im newbie
Not really there is a ****load of tutorial on the net how to install the android sdk.
Just use google.
Hii im new to this forum... Just joined as i wanted to see if this has happened to anyone elses sensation.
The other day i had my phone in my pocket at work and i felt it was getting really hot on my leg! Opened up the task killer thinking i must of left something running... But nope, everything was normal! My battery had gone from full to 66% in under a hour and i hadnt even used it!! So knowing that i still had 13hrs left on my shift and no charger with me, i turned it off and put it in my locker.
Couple of hours later i go back to get my phone and im shocked to feel that it was red hot even though it was turned off. My battery was now at 13%.... Whats that about?!
This hasent happened since and hopefully wont again. Anyone else has this problem?
Im also abit worried about the heat my screen gives off when im doing simple things like browsing the web for over half an hour.
Anyway... Essay over
Turn "fasboot" off. Your phone wasn't off...just in "sleep mode". I assume.
This same exact thing happened with my G2X when I downloaded the NFL app during draft day. I closed the app and put the phone in my pocket. Ten minutes later I felt my leg getting hot and my phone was burning up. I deleted the NFL app and everything went back to normal. Most of the time it's a poorly written app that causes this issue so I suggest you delete any recently installed apps and see if it happens again.
have a look at this.. maybe it helps
http://forum.xda-developers.com/showthread.php?t=1135455
Hi all. Since updating to 2.3.5 my screen randomly lights up. The phone will be just sitting on the table, next to bed etc and the screen will light up for a few seconds and the turn off.
Not been on a stock ROM in a while, but I do remember hearing about this problem when the update rolled out. Just can’t remember if the problem was solved. Had a quick search and no joy. I'll keep looking. I have a theory though...
I had this problem once, and it was down to an app and the WiFi sleep policy. The WiFi sleep policy was set to ’15 minutes’ so the app was occasionally forcing a wake-lock to stop the WiFi from shutting off. This would also cause the screen to come on briefly. Could it be something like that? Sorry I can’t remember what the app was. Try leaving WiFi off and see if that stops it. If not successful try leaving auto-sync off. It will at least rule out or confirm something trying to force a wake-lock to sync something.
Edit: Does this do it only when on charge? Try opening up Car Dock Mode, and turning off 'Auto Launch'.
wnp_79 said:
Not been on a stock ROM in a while, but I do remember hearing about this problem when the update rolled out. Just can’t remember if the problem was solved. Had a quick search and no joy. I'll keep looking. I have a theory though...
I had this problem once, and it was down to an app and the WiFi sleep policy. The WiFi sleep policy was set to ’15 minutes’ so the app was occasionally forcing a wake-lock to stop the WiFi from shutting off. This would also cause the screen to come on briefly. Could it be something like that? Sorry I can’t remember what the app was. Try leaving WiFi off and see if that stops it. If not successful try leaving auto-sync off. It will at least rule out or confirm something trying to force a wake-lock to sync something.
Edit: Does this do it only when on charge? Try opening up Car Dock Mode, and turning off 'Auto Launch'.
Click to expand...
Click to collapse
thanx for the answer friend.i ll try it.
efialtis1971 said:
Hi all. Since updating to 2.3.5 my screen randomly lights up. The phone will be just sitting on the table, next to bed etc and the screen will light up for a few seconds and the turn off.
Click to expand...
Click to collapse
I noticed this too, but only on a Sense 3.5 ROM...Endymion (because, frankly, i didn't care much about any other Sense ROM to stay on it long enough to notice anything) ...but for me, the screen only lit up like a camera flash, just for a fraction of a second! not for a couple of seonds as you have experienced. Been on ICS betas, and RCs and currently on Reaper, but this issue never repeated itself. So far, this has happened to me only on a Sense 3.5 ROM...and my setup, sync frequency, installed apps hardly ever varies from ROM to ROM...I'm pretty consistent about how i like to use my phone.
And frankly, even when this was happening, i didn't bother much because it wasn't affecting performance or battery life... Sense is quirky, to say the least, but i've learnt to tolerate it like you would a sexy girlfriend. If it's sexy enough, it can get away with anything!!
I had this issue on the stock 2.3.3 ROM.
-------------------------------
Sent from my HTC Desire S
I can confirm that issue, like enigmaamit described it. I'm on endy 3.4. Weird...
Sent from my HTC Desire S using XDA App
I had the same issue but just one time few minutes after i pluged my phone .
Same here with MIUI... Just for a 1/10 of a second...
...via Tapatalk
I get this on ICS (virtuos quattro) when screen is off and charging, like half a second on and off again...
i've had this issue with pretty much every ROM, actually had it since i've had the phone. The phone lights up for a quick second. Enough for you to realise when your eyes are closed. i don't pay much attention to it anymore. But i don't think mine lasts seconds like yours. Mine was just a blank screen flashing
dan-fish said:
i've had this issue with pretty much every ROM, actually had it since i've had the phone. The phone lights up for a quick second. Enough for you to realise when your eyes are closed. i don't pay much attention to it anymore. But i don't think mine lasts seconds like yours. Mine was just a blank screen flashing
Click to expand...
Click to collapse
Hmm I think I'm only one but I gess not. It flash for like 0,1-0.2 sec. Just a little bit and I have seen it only in night when room is dark but I'd you don't motivated hardline to see. Flash is low light with blank screen
Sent from my HTC Desire S using xda premium
Hello to everyone,
I have a problem that makes me angry every day regarding my Motorola Droid 2 Global, even if I love very much this phone. My phone`s display is turning on solely. This fact makes my phone`s battery to drain very fast. Thus, my phone lasts one day and some hours. My phone`s display is every time at 45%-55% as consumption. I mention that I have 2.3.4 Android Version and 4.5.629 System Version. So, from all I know, this Android version doesn`t have in pocket detection. I saw already that a lot of people have this problem.
Thank you very much for your help!
All the best!
Any idea ???
not sure what you mean, solely?
It won't turn off?
I would wipe cache and/or data, start over
Hello,
Yes...I am locking my phone (my display turns off) and after a time my dispay is turning on without any action from me and after that it turns off. Unfortunately this fact happens not a single time. Thus my battery is drainning very fast.
The D2G does in fact have in-pocket detection, but in my experience it does not work very well.
Is it possible that the keyboard is sliding open, even just a few millimeters, inside your pocket? I find that happens with mine occasionally, and it doesn't have to open very far at all to turn the screen on.
Hello,
I did a Factory Data Reset. Now I maintain my D2G under observation. Apparently, now, all seems to be ok. On the other hand, my phone display is at 30% as consumption.