Good morning guys, I'm with the following problem:
After replacing the touch of my cell, he began to present a problem in touch. Apparently when the phone goes into deep sleep it disables the touch and can not activate it again.
Have I changed Rom several times and nothing, I've tried various procedures and nothing.
I installed the "Free SoftLocker" he theoretically was to force the phone to never enter deep sleep mode, but even then he often enters and catches it again.
My phone is a MB860 Atrix from Motorola. I used the 4.2.2 of Epinter, she spent up to 1 day without going into deep sleep with the application cited above, but the battery did not last even six hours, then moved to the Neutrino v3.02 (2.3.7), but despite the installed application, it crashes often.
Thank you in advance for help.
Related
Hi,
I've been experiencing some 'overnight' problems with the HTC Touch Pro lately.
The Pro is switched on for like 24/7 and works fine.
The thing is that it now and then happens that in the morning (so after a night standby time) the Touch Pro is all messed up.
Things that I have seen now:
- Device is turned off completely and needs to be turned on again (like the battery is down, but it's NOT).
- Device seems to have had a soft reset, since it shows the 'ENTER PIN' screen when I switch it on.
- TouchFLO 3D is all scrambled (see attached pictures for examples)
I think (read: hope) that it's all software and that it'll be fixed by a future ROM upgrade, since I've never had such problems with the Touch Diamond before. It's quite frustrating since the first two problems cause the fact that the phone is offline.
Do the problems sound familiar to you? I didn't find other topics concerning my experiences...
I think it may help if people also listed what apps they have installed. Up until last night, i had not had any issues with the device overnight. However after installing battery status last night, this morning the device had soft reset in the night. This is the first time in 3weeks.
The battery indicator is another issue which i think most people have. The indicator seems to get stuck and then when it updates it looks like a lot of battery has been used in a small amount of time. FOr instance my battery was reading 100% for over 4 hours then suddenly jumped to 95%. Also when charging i have had the TP stop charging at 87% and looking at the current level - only 80mA was being drawn, indicating that the battery was not charging. A soft reset later, corrected this. I am just wondering whether this is what is causing the soft resets in the night - ie the device detects that it has been charging for a long time with no battery level change and therefore resets. Just a hunch..........
- Device is turned off completely and needs to be turned on again (like the battery is down, but it's NOT).
I've had this a couple of times but hitting the power button doesnt work, I have to use the soft reset to get the phone back.
- Device seems to have had a soft reset, since it shows the 'ENTER PIN' screen when I switch it on.
Had the same thing a couple of times too.
- TouchFLO 3D is all scrambled (see attached pictures for examples)
Again, had this a few times
Not had TF3D scrambled, but had the other two. I'm pretty sure it has happened to me only when charging (other people report similar problems resuming from standby when charging). Perhaps, like me, you mainly charge the device at night?
I'm currently running with TF3D off (Settings, Today, Items, un-tick TouchFLO3D, tick some standard today items instead), and I haven't seen this problem since.
Cheers,
Graham.
hmmm...I'm very curious how this is coming...
Maby it are the installed programs that doesn't work correctly..
I'm curious if ya let the phone 'standard' so without installing all kinds of programs if the phone still has these problems.
Had read a few suggestions for fixing this "sleep of death" issue on the G tabs... doesn't seem anyone has posted this
I've tried multiple ROMS, multiple apps like Regpon Wifi stay awake etc. and multiple GTabs...
The only thing that repeatedly seems to completely fix the not waking after sleep issue is an app called "Captivate Keep Alive"
Instead of tying wake to WiFi or CPU, it lets you tie it to battery %.
Try it, let me know if it works on your ROM.
Tested working 100% for Vegan 5.1.1 and CM 7 Harmony.
Tablet used to require boot after leaving it, now it will always wake up, after 1 hour, 20 hours, etc. Plugged in or not.
Completly agree. I tried all ROMs, and Kernals(up to .40). Nothing helps, but Captivate Keep Alive.
I had a similar, but not same issue. My WiFi would turn off completely when teh screen went blank. I could not ping it. Turns out that I had to update my kernel to pershoot's 2.something.39. That fixed it. I do find it every now and then totally unresponsive but pressing the power button patiently 3-4 times wakes it up. I'm running CM7.
App works
So glad I found this thread. I was having this same issue using TNT Lite and installed Captivate Keep Alive. I have been able to turn on from sleep without the reboot.
Hello !
for a month or so, my phone is sometimes shutting down suddenly without any reason (and it is random, I can't provoke it...)
I called HTC Customer service, and they told me it could be caused by some apps. The problem is I only have extremely popular apps (as SoundHound, Doodle Jump, Angry Birds...)
They told me to turn on the Safe Mode, and... Two hours later, my phone turned off.
I tried several times to get the logcat, but it appears that logs are deleted when the phone turn off.
I saw that I am not the only person with this problem, so if you have any suggestions/ideas...
And also, when the phone turn off, when I turn it on, the battery level drop down (example : 80% before the turn off - 20% after reboot)
Thanks !
Hi,
I'm having the same problem. I've fixed it setting the network mode to 3G only.
Does anyone know if this problem has been reported/investigated?
Thanks.
sorry, ive been looking around and I see in the Liquid Rom thread that it has a SOD problem. I looked around for a bit and i couldn't manage to find what it stands for. I think i might have it because sometimes when i turn my screen on, the touch response doesn't respond. I have to turn off my screen and turn it on again to make it work. I'm unsure if its a aosp problem cause i don't remember getting this problem in Sense
It stands for sleep of death, so it is a deep sleep problem.
Its not an AOSP problem, Ive never had it on Dark Jelly CM10 at least.
SOD stands for Sleep Of Death like the above poster said, and can result in a number of things.
The TF101 was plauged by SOD, and on that device sometimes the screen wouldnt turn on after a deep sleep. It also did random reboots during deep sleep and hanged at the boot sequence - draining the battery in no time at all. That was very frustrating.
A workaround for the TF was to use an app that woke the device up every now and then, so it didnt deep sleep for long periods of time. It drained the battery a bit faster, but it was quite ok.
Personally I worked around it by never letting wifi turn off - even during deep sleep, then set up some task that used wifi such as weather updates every 30min, msn, rss feeds etc.
Basically, SOD is commonly used when you wake a device up and it doesnt act as it should and forces you to reboot/remove battery/wait for battery to drain/etc
I'm trying to help my mother revive her TF300T. She was running the stock 4.2.1 ROM and it was borderline unusable. Task switching was horrible and upon waking from sleep, when that worked, it would be several minutes before it would work smoothly - it definitely wouldn't work when background sync was going on. More often, once it went to into deep sleep, it would have to be manually rebooted since it would not wake. She also had an issue where the volume turns itself up.
I installed CM11 on there and much of the usability problems have been taken care of. It is much, much speedier. However, it appears it still will not wake from deep sleep, at least sometimes. The volume issue persists as well. The latter is probably a hardware issue. I'm wondering if the inability to wake is also a hardware problem. Any ideas?