If I have the hardware keyboard out and the phone goes into sleep mode and I close the phone, when I hit the power button, I get the issues shown in the attached images. It won't respond to anything unless I open out the keyboard and close it again or, tap on the notification area and close the notification screen. No issues if the phone is not allowed to sleep.
Don't want to hard reset if I can avoid it, anyone else had this issue?
I have never seen my device do this, but I don't think I have ever let my device go to sleep while in landscape.
To avoid this, why don't you just change your backlight settings? While on battery power, set the backlight to turn off if idle for 5 minutes or something. This way you'll never have it fall asleep on you. Unless of course you read extremely slow and a page takes 5 minutes.
Was thinking about increasing the backlight settings for a bit longer. I had that situation by chance last night and tried various things, uninstalling software, bluetooth head set, changed radio, hard reset and even task29 and a new flash, still same issue.
Just starting to get fed up with these little annoyances, would be nice if it just worked, lol.
Wow that's rather odd that you did a hard reset and still had the issue. That would suggest that it is most definitely device specific. Maybe you can call your carrier, and if it's your lucky day they can replace your phone. ??
Why no try Energe ROM, It has no such problem.
Related
I've been running Black 1.2 for some time. Love it. Never soft reset. Only hard reset it once. I'm using a Cingular 8525. What's weird is that it powers itself off randomly lately. 3 times in a row. It was pretty hot outside when it happened, so don't know if the heat caused it, but the screen would just die and turn off. Anyone have this happen? Any ideas as to what causes this powering down? The battery is full. It was just super hot out? Hmmm.
I would suggest you upgrade to a newer rom dude
take a look in my guide thread which has the latest ROMs listed.
mrvanx said:
I would suggest you upgrade to a newer rom dude
take a look in my guide thread which has the latest ROMs listed.
Click to expand...
Click to collapse
I considered it, but since Black 1.2 was released, I never had a problem with it. Very stable. Could it now after all this time just all-of-a-sudden cause random power-offs? Also, I noticed the device likes to power-off when I slide the qwerty keyboard out and lock it in place. Not every time I open it, but it has happened a few times now. ROM related? Let me know. I'll probably up to a newer ROM tonight.
Thanks.
-fin
Ok, update: Seems that EVERY time I slide out and lock the qwerty the device shuts off when I go to reply in a messgae using Palm SMS Threader. Is it the device or the app?
I had the same problem with my old JAMin (Prophet). I would keep the phone in a case and then wonder why I wasn't receiving any calls, then check and see the phone having turned itself off. Reloaded it with a different ROM and the problem went away.
Yeah, that's happened a bunch of times now. Just recently did I hard reset my device, and all was running great like before. Just all of a sudden am I having this issue with power offs and the qwerty kicking the phone off when I open it.
I have the same problem and I have come to one conclusion because I can repeat it.
If you are closing or opening the keyboard, but you do it quickly (like slamming the keyboard shut or open), it will turn off. Also, if you squeeze it while it is closed, it turns off. And I have made sure im not hitting the power button.
Try it and see what happens.
Yeah, it does it when you slide it out really fast. Noticed that. Haven't been able to repeat it every time, but the times it does shut-off, its from sliding it open fast. Now to understand why this happens, since it didn't do this in the past.
Hi folks, I've lurked here for quite a while and gotten some invaluable info; so first off thanks for all of the contributions from the gurus here!
Now, I have a pretty strange issue that I haven't been able to find an answer on anywhere. I'm hoping that someone can help me sort this.
The background story:
My wife has a MyTouch 3G Slide that I bought for her back in July. Last week she managed to drop it in some water. It DID NOT get fully submerged since the water was very shallow. However, it did get a slight amount of intrusion. She pulled the battery in a relatively quick amount of time and we let it sit in a bowl of rice to dry out for a couple days.
The current deal:
When I felt the phone was sufficiently dried after a few days, I fired it up. It took a very long time to get out of the MyTouch splash screen and loaded noticeably slower than normal. Once in, the phone functioned perfectly normal. Absolutely no issues at all with any functionality once you get past the security pattern.
However, whenever you put the phone to sleep, it does some funky stuff. The screen goes black for a second and then comes back on, ready for you to swipe down and then enter the security pattern again. Then it will go black again. Then it comes back on. It just continues to do this, never stopping. Sometimes it will go to the security pattern screen too.
So I figured this may have been some hardware issue since it was acting like someone was just repeatedly pressing the power button. First I wanted to try a simple reboot though. Upon rebooting, the phone would not get past the splash screen. It just froze there.
I pulled the phone apart to see if maybe there was some corrosion on the PCB from the water intrusion. Everything looked fine, but while I was in I did a little wipe-down with some alcohol, then I put it back together. After multiple attempts, I was able to get it to boot again. But the boot process was still VERY slow. Occasionally, it would boot into safe mode as well. But when it booted normally, everything would always function great once logged into the phone. This convinced me that it wasn't a hardware problem since the phone would not cut into sleep mode or anything when logged in. It worked perfectly fine. So I figured that maybe there was some sort of corruption that occurred in the software.
So I tried a hard reset. Didn't fix it.
Then I figured that maybe I needed to do a reflash. So I rooted the phone since the water plunge voided the warranty anyways. Once rooted, I flashed TeamFenix 1.7.1 successfully.
But the phone still only fully boots intermittently, and the boot process is still slow. It also has the same problem in sleep mode which is killing the battery fast since the screen is pretty much constantly on. But once in, the flashed ROM works perfectly just like the stock ROM.
Video of the condition:
Since I'm new, I'm not allowed to put any links in my post. But if you type in the string below after the YouTube url, you'll see a quick video I posted of the condition.
watch?v=dX55URtaRHo
So it seems that there is some crazy issue only upon bootup and when the phone is put to sleep. Can anything be done to fix this? Is there a way to locate and fix corrupted software? Any and all help is appreciated!
Sorry for the self bump. Any devs out there have any suggestions? I gotta get this thing sorted.
If its happening on both stock and teamfenix, I'm pretty sure it's a hardware issue. Flashing a rom completely replaces the software, so it doesn't sound like its that.
Sent from my T-Mobile myTouch 3G Slide using XDA App
It actually seems like a problem in the power button. Did you check the contacts for the power button? Repeatedly pressing the power button will first lock it initially and dim the screen. Press again, then it gives you the chance to unlock. Press again and it goes back to sleep. Wash rinse repeat...
Yes, I understand. But if it were an issue with the power button, when you logged into the phone, it would randomly put itself to sleep. It doesn't do that, it functions perfectly normal with no errors whatsoever when you are logged into the phone. This problem is only exhibited in sleep mode which would rule out a hardware issue with the power button.
Ok, I was having some software issues with my Tilt 2 (TP2) and I talked to Tech @ AT&T, cause I wanted to get it exchanged. So they had me go and check to see if my ROM was outdated, which it was. I bileive it was on 1.59-ish, and now its on the most current one direct from HTC's Support site. My main problem right now is that the phone is 99% unuseable at the moment. AT&T has already agreed to send a replacement after talking with them a few hours ago, but its going to take about a week to get here, and it'll most likely have the same ROM and the same problems, so here I am posting to let people know whats going on, and see if anyone else knows what causes this/has this issue.
Right now the phone is completely stock, only installed app is MS My Phone so I could sync my contacts. I can let the phone sit till the screen shuts off from idle, but if I need to turn on the screen once it turns off, it requires the battery to be taken out. Right now my phone is sitting in front of my keyboard, with its screen black and off, while the keyboard is lit up. Something to note - the keys on the bottom of the screen are NOT lit up. Pushing buttons on the keyboard does nothing. Caps Lock and FN do NOT light up their coresponding indicator lights. If I am lucky, I can get the phone to come out of this state by having someone call me, but aside from that, taking out the battery has been the only way to reset it. Only way to keep the screen from freezing is to constantly use the phone. Using the phone is slow as balls. I thought TF3D was slow, Sense is just as bad. It worked perfectly fine at first, right after it was updated, it was nice and fast, but now that its been used for a few hours, its sluggish.
Anyone ever had this issue with this ROM?
And does anyone know how to possibly fix this issue, or at least get it so the screen will show that its on? I can deal with it being slow, so long as I can use the screen
Thanks guys
null_x86 said:
Ok, I was having some software issues with my Tilt 2 (TP2) and I talked to Tech @ AT&T, cause I wanted to get it exchanged. So they had me go and check to see if my ROM was outdated, which it was. I bileive it was on 1.59-ish, and now its on the most current one direct from HTC's Support site. My main problem right now is that the phone is 99% unuseable at the moment. AT&T has already agreed to send a replacement after talking with them a few hours ago, but its going to take about a week to get here, and it'll most likely have the same ROM and the same problems, so here I am posting to let people know whats going on, and see if anyone else knows what causes this/has this issue.
Right now the phone is completely stock, only installed app is MS My Phone so I could sync my contacts. I can let the phone sit till the screen shuts off from idle, but if I need to turn on the screen once it turns off, it requires the battery to be taken out. Right now my phone is sitting in front of my keyboard, with its screen black and off, while the keyboard is lit up. Something to note - the keys on the bottom of the screen are NOT lit up. Pushing buttons on the keyboard does nothing. Caps Lock and FN do NOT light up their coresponding indicator lights. If I am lucky, I can get the phone to come out of this state by having someone call me, but aside from that, taking out the battery has been the only way to reset it. Only way to keep the screen from freezing is to constantly use the phone. Using the phone is slow as balls. I thought TF3D was slow, Sense is just as bad. It worked perfectly fine at first, right after it was updated, it was nice and fast, but now that its been used for a few hours, its sluggish.
Anyone ever had this issue with this ROM?
And does anyone know how to possibly fix this issue, or at least get it so the screen will show that its on? I can deal with it being slow, so long as I can use the screen
Thanks guys
Click to expand...
Click to collapse
You already ruled out a software issue by flashing another stock ROM. This is something hardware related. Sense on the AT&T ROM is dreadfully slow. Use a custom ROM if you want the features of Sense, but in a faster iteration.
Hi everyone,
I have been having a very annoying problem with my Galaxy Nexus during the past few days. When it enters to sleep mode (after 15 seconds without activity or when I push the power button) it wakes up itself again after 2 to 10 seconds and does not stay into sleep mode: the lock screen is displayed during 15 seconds before a new sleep mode/'wake up state' loop starts again.
It doesn't happen all the time but it does often enough to waste around 8% of battery every hour without me touching my phone.
I searched the forum for solutions and found in other threads that an application could be the source of the problem. I uninstalled every apps but the problem remained. I did a factory reset without installing any app or update after but the problem also remained. I also tried using only Wi-Fi or only 3G for data or switching to flight mode, but it didn't change anything.
Other solutions suggested on other threads, to disable GPS. It did it too, without more success.
I noticed that the problem only occurs when the phone is unplugged. It never happens during loading.
Have you any ideas that could help me to solve the problem?
Thanks a lot in advance,
Julien
Don't know if it helps but I made some screenshoot of BetterBattery Stats results.
Galaxy Nexus - The 'Waking Up' Problem
I love my Galaxy Nexus (I would like to thank Google for giving them away during the I/O 2012). Jelly Bean (the last version of Android) is simply a blast: it is smoother, snappier, sexier, you name it.
As much as I love JB, I still need to play with my devices, and what a better way to play with an Android phone than to root it. After testing a few ROMs, I ended up using Codename Android in combination with Lean Kernel. I advise you guys to have a look at it, it packages an insane number of customization and parameters that will make your phone even better!
The drawback when you hack around with your phone, is that your start feeling guilty when it starts doing random stuff, such as waking up randomly : I would put it in sleep mode (using the power button), and a few seconds (minutes if I happened to be lucky), the phone would wake up on its own, sometimes indicating it was charging when obviously no cable was plugged…
From there started the usual bug chase that many of us know: backup, factory reset, and a complete reinstallation. Unfortunately, in that particular case it would not change a thing and the problem was occuring even more often. It was becoming obvious that my problem came from the hardware…
The usb connector at the bottom of the Galaxy Nexus has a bad habit of bending downward after some time (it varies, depending of your usage). The solution is thus to take a small knife and pushing it upward so it does not touch the bottom metallic plate. Et voila! Your phone will stop waking up by itself, and your frustration will go away with it.
I guess if a lesson can be learned from that experience, it is that the obvious answer is not often the right one; you should also keep a small knife not too far from your Galaxy Nexus.
It´s work fine to me...
Hi guys
looking for some advice here please as this is slowly driving me crazy.
Bought a tab s 8.4 about a week ago, along with the folio cover.
When I either close the cover or press the power button to put into sleep mode, it'll wake up providing I either open the cover or press power button within about 8 seconds. Anything longer than this and it requires a soft reset to get it to turn back on. From reading this sounds like the sleep of death. I've looked around for solutions to this, installed an app to stop it entering deep sleep but this didn't work, granted I may have the settings wrong on the app but I had it waking up the device every 9 seconds which is the lowest setting, and this still didn't prevent it having to be reset.
Thought it may have been due to apps I'm installing but now done 2 hard resets back to factory conditions, then not connected to the WiFi so it doesn't download my associated apps, and it's still getting the Sleep of death.
As I see it at the moment it's going into the sleep of death straight from factory settings. FYI is does the same with out the case on also.
Any advice, comments or potential apps that's may help would be appreciated as at the moment it's pretty much unusable and will soon to be flying out of the window.
Thanks guys
Kieran
I would suggest going for a ROM update. Either from another country. Or some custom one.
I would update/reinstall the firmware or try a different kernel. This sort of problem usually points to the kernel synaptics touch driver. Maybe you have a kernel problem.
Thanks guys I'll give that a go