[Q] Problems coming out of sleep mode - Captivate Q&A, Help & Troubleshooting

So within the last two days I have been having problems with my phone coming out of sleep mode, just to give a little more information when i hit the power button to turn the screen on and go to unlock it, the screen doesn't respond and fades back out. The task bar stays on at the top for about 10 seconds as well. SOMEONE please help lol. I've only had this phone for about a week and this is very frustrating. (phone is rooted btw)
Thanks in advance

If you're having touchscreen malfunctions, then you should exchange it. You've had it one week, you can do that. I will say though, the screen timeout for the lock screen is 5 seconds long. As in, when I wake my phone if I don't touch it, five seconds later it fades out again. It sounds like you're having more serious issues however mentioning the notification bar staying on the screen like that. I recommend you look into exchanging it. Make sure you restore it and unroot it before you do that.
Unroot thread

I was just wondering if anyone had these issues, it didn't appear to do it the first couple days I had it, and I've installed a ton of apps since then. I un-installed some things today and it seems to have subsided, i'm still wondering if anyone else has had problems like this. It may have had to do with a task manager, but i can't be sure. Any insight is appreciated.

Related

[Q] Can you help me figure out this weird screen crash?

I've got a Captivate running base Andromeda 3. I believe I had this issue prior to that, but I cannot be sure. Here's the behavior:
I use the Google Desk Clock overnight while I charge my phone. In the Morning, when I unplug it, everything works fine, regardless of whether I let the screen time out or press the power button to turn it off. Somewhere in the next hour, it may be 3 minutes it may be closer to an hour, the screen decides it WILL NOT turn back on.
The phone is still on, the softkeys still light up, the phone still rings and receives messages. I can even answer the call and talk, just based on knowing where the answer slider is.
Interestingly, if I wait for the call to STOP, the screen will come back ON, but then won't really work. It wants to hang and/or freeze on whatever given home screen you come back to.
Holding volume up plus power to force reboot fixes the issue until the next morning.
I had other issues a long time ago on another rom with LauncherPro, and had switched to ADW. When I mentioned this issue in the Andromeda thread, it was suggested I switch to Zeam. The problem persists and interestingly, about 50% of the time when the phone turns back on, Zeam has decided I only need 3 instead of 5 home screens. Editing the setting brings back the home screens and their setup, weird.
I thought maybe it was Clockr, not clockr.
Using BattStat, SiMi Clock, GVoice, and Keyring widgets. I can't imagine any of my installed apps would make a difference, I'll list them if necessary.
I believe Andromeda (Froyo?) does some weird things with shutting down apps, I'm wondering if it possibly has something to do with that. The problem never happens again during the day, so clearly it either has to do with charging or with the GDesk Clock, or both. Happy to hear any thoughts. Please?
One more thing: While the screen is off but the phone is on, it DESTROYS my battery. Seriously, it'll eat 15% in 20 minutes.
TomMelee said:
I've got a Captivate running base Andromeda 3. I believe I had this issue prior to that, but I cannot be sure. Here's the behavior:
I use the Google Desk Clock overnight while I charge my phone. In the Morning, when I unplug it, everything works fine, regardless of whether I let the screen time out or press the power button to turn it off. Somewhere in the next hour, it may be 3 minutes it may be closer to an hour, the screen decides it WILL NOT turn back on.
The phone is still on, the softkeys still light up, the phone still rings and receives messages. I can even answer the call and talk, just based on knowing where the answer slider is.
Interestingly, if I wait for the call to STOP, the screen will come back ON, but then won't really work. It wants to hang and/or freeze on whatever given home screen you come back to.
Holding volume up plus power to force reboot fixes the issue until the next morning.
I had other issues a long time ago on another rom with LauncherPro, and had switched to ADW. When I mentioned this issue in the Andromeda thread, it was suggested I switch to Zeam. The problem persists and interestingly, about 50% of the time when the phone turns back on, Zeam has decided I only need 3 instead of 5 home screens. Editing the setting brings back the home screens and their setup, weird.
I thought maybe it was Clockr, not clockr.
Using BattStat, SiMi Clock, GVoice, and Keyring widgets. I can't imagine any of my installed apps would make a difference, I'll list them if necessary.
I believe Andromeda (Froyo?) does some weird things with shutting down apps, I'm wondering if it possibly has something to do with that. The problem never happens again during the day, so clearly it either has to do with charging or with the GDesk Clock, or both. Happy to hear any thoughts. Please?
One more thing: While the screen is off but the phone is on, it DESTROYS my battery. Seriously, it'll eat 15% in 20 minutes.
Click to expand...
Click to collapse
I've read something about that couple days ago. If you do a little search, I'm sure you'll find it (can't remember what the thread was called)
Also, black screen usually happens with UV. which brings me to ask.. Do you OC/UV?
Andromeda doesnt do anything differently than any other rom including stock when shutting down apps. there was nothing changed that would change that behavior from any version of 2.2
Unless andromeda does onboard OC/UV, then no, I don't.
Seriously nothing that I can find has changed. I've scoured the boards looking for similar threads, but I suppose I'll start over.
Oc/uv is not available in andromeda without flashing a different kernel
Sent from my atrix

[Q] Normal for the GNote screen to warm up?

Hello,
I have had noticed this for a while but though it was normal. Till I am starting to notice that it is taking the GNote screen longer and longer to "warm up".
What is happening is when I leave the GNote in deep sleep for a while (the longer i keep it in deep sleep the longer it takes to warm up) and then wake it up, I get a green screen, but after a few seconds the green colouring will slowly fade away until it is back to normal.
If I put the note to sleep and open it back up in about 2-5 seconds, it will wake up perfectly fine but as soon as I start leaving it in sleep mode for about 5 mins, I can start noticing the green tint when waking it up. When I wake it up after 5 mins, it takes about 1 second to get back to normal, when when I leave it for a good 3 hours, it takes about 5-6 seconds before the screen return to normal.
I just want to know if this is "normal" as I can not find any thread on this forum or in google about this. None of my friends has this phone so I am unable to check theirs. Sorry about the long explanation, I just want to make sure you guys know what I am talking about.
Nope....that doesnt sound right....ive had my phone 4 a month now and cant say i saw ths issue....sounds like a faulty screen to me.
If ur on warranty....ask 4 a replacement. If not, try changing the rom.
I tried a number of things to see if it fixes the problem. I first tried using the K7 deodexed rom, then I tried changing the kernel to Abyss. Now I am running Rocket ROM with Abyss 3.5b.
But I do remember that I didn't have this problem in the first week. I think I started noticing this after I rooted my phone when it was on XKK9 but I wouldn't think rooting my phone would cause something like this unless it was just coincident.
I guess no one has any idea why this might be happening. I might send an email to Samsung and see what they think.

Milestone not entering Lockscreen

I've been having a bit of a strange problem lately - sometimes my phone won't enter the lock screen. I'll turn the screen off, or let it go to sleep, and then when I go to turn the screen back on again (could be hours later), it goes directly to the home screen, and never see the lock screen. This makes it very easy to pocket-dial, or launch apps - my pocket started blaring music one day.
A restart seems to fix it for a little while, but within a day it will start doing the same thing, and I don't think I saw the lock screen at all yesterday. Does anyone have any idea what might be causing this? It started a couple months ago, but it seems to be more frequent now.
I am currently running Motorola Milestone, CM7 (kabaldan's beta with swap enabled). It was also happening some with CM7.2.1
Thanks in advance!
Anyone have any ideas?
Another interesting point is that after NOT seeing the lockscreen, and then playing around on the phone, I'll open one of the apps (say the browser), and THEN it will drop into the lockscreen. So right in the middle of doing stuff, it will make me have to unlock the phone. Can be a little frustrating.

**HELP**Lock button permanently locks

I have a strange problem, well a few. If I lock my phone (C6903) using the physical button I can't unlock it again. I try for about 5-10 minutes sometimes and it just wont work. If I hold it down I can feel it vibrate as if it's bringing up the power menu but the screen just stays black. Eventually it will randomly wake up then I can play around as normal. If I leave it to lock itself I can unlock every time, fist time no worries. This is what pointed me to it being a SW problem rather than a hardware problem.
I also noticed that when I do have the screen turning off in the dark, I can see that the screen is still lit up! Just it is black, not completely asleep. It's really quite bright when I have it next to the bed. Also when I am outside I can't see the screen at all really, even with the brightness turned right up.
It's really strange all these happened about the same time. I figured maybe it was a ROM problem and a fresh install of stock ROM would help. Tried it and at first most of these problems went, just the fact I still couldn't really see the screen in the sun. I tried another ROM and at first was just the same but then these problems started again.
Has anyone had any or all of these problems or got any ideas what it could be? I am left thinking now that the problem is more likely hardware related as the problems are so sporadic and happen whatever I have installed.
Any help / suggestions would be appreciated but I have the feeling I will have to just admit the phone is dogged
You say that most of the problems desapararecen to install a new ROM, it is likely that installing something extra to be the cause, I was introduced me something similar with Expoxed Notifications Module.
Try a clean installation without installing test applications to determine if the problem recurs.
Thanks, yes I guess I will try that, bit of a pain having to reinstall apps after every install and restoring messages etc so I might just put up for now.
I also have realised that the screen not turning on and the screen staying on but black happen at different times. i.e. I can now randomly turn the screen on and off no problem (don't think I have installed or deleted any apps or changed anything), but the screen stays awake when off. When I was last not able to turn the screen back on after turning off the screen actually went to sleep. Very strange

Please help - screen randomly becomes nonresponsive - but only partly - please read

Now there is another long topic on freezing, but its basically about 10seconds freeze , then things normal and stuff. Mine is different so I made a new topic.
Have sprint note. On Marshmellow now but happened on Lollipop as well.
The problem is:
After several hours of use, or may even a day, the phone just freezes....partly. Let me explain. Basically if you touch anywhere on the screen, it won't register the touch. If you hit the hard recents button, it'll show recents, but you can't click any program (it doesn't register your touch). When it first happened I thought I needed a new screen, but quickly found out I probably don't: If I hit the nav bar, it will pull down full screen, and if I have it full of notifications, I can click any of the notifications, whether its near the top, middle, or bottom, and it registers the touch and sends me to the app. But then again, at that app, the screen doesn't register. Even if I touch in the same place on the screen where I clicked the notification that sent me to the app. But the nav bar still works. It recognizes the touch, and will pull down full screen, and I can click anywhere on the screen and my touch will register. Also if I hold the power button and the reboot options come up (which on mine has option from top down to bottom, I can click any option on the screen, and it will register my touch. But if I hit the home button, the whole screen is non responsive. So I have a partial freeze. The whole screen doesn't work, but then the whole screen will work when I pull the nav bar down, so im totally confused. I already tried usually differnt launchers, but same thing, after while, screen will be non responsive
If I reboot then everything works fine and normal, so I doubt its a screen issue. Because if its broke its broke. Also tried a hard reset,problem still came back. I guess it may be an app clashing problem but I have over 100 apps it could be any one of them
Has anybody experienced something similar?
I had a buddy give me an LG Lucid3 that had a similar issue... It actually got worse over time and the touchscreen totally stopped working. (He thought) I took it apart and actually the connection was good. Put it back together and just kept rebooting it multiple times in a row. Finally, the touch started to work a little an for some reason I thought to go and download an antivirus program. The phone had 11. Got rid of them and phone has been working fine for a couple weeks now. Idk if that's your problem but I figured I'd share this experience because I've never seen anything like it.
Sent from my KYOCERA-C6745 using Tapatalk

Categories

Resources