Hello,
I tried to search on this and didn't find much help, so I hope this thread isn't an asked and answered topic already.
Lately, since the most recent Omni update (Xoom stingray), I have had to force reboot my Xoom after charging overnight. The tablet becomes unresponsive and the screen doesn't come on after I unplug it. I have the processor clocked to 456/1200, so I don't think it's the same symptom as the low speed freeze issue that's been discussed in detail.
Is anyone else having this problem? If so, has there been a solution or is it currently a known issue without a solution?
Thanks in advance. Everything else about Omni has been great and I appreciate having some KitKat love.
Related
I have a completely stock Nexus S. Whenever I answer or place a phone call the screen goes black and never comes back on. I have to remove the battery and reboot the phone. Anyone have any ideas as to the cause of this?
I think it may have something to do with the proximity sensor not being sensitive enough.
Thanks
Sorry for the thread necromancy but it's either that or creating another redundant thread for the same issue. I'm suffering from the same problem as the op (nonrooted Nexus S everything stock) and so are the people who have responded to the informal bug report in the Google mobile help forums you'll get as the first hit if you google "Nexus S back screen after call" (sorry, first post so no links).
I've been unable to remedy it despite quite a bit of research and it's getting quite frustrating, especially since the problem is still present after the update to ICS.
I've gathered this has been an issue with a multitude of handsets and that the problem is on the kernel level and seems to be the result of the proximity sensor being miscalibrated.
Now I don't know how the calibration data is handled on the Nexus S so if anyone is sitting on info related to this I'd love to hear it. Also if there is any way to recalibrate the proximity sensor via ADB or some MMI code that would be great.
Otherwise, has anyone suffered from this problem and managed to solve it by changing kernels? If so which kernel did you use?
Cheers.
Sometimes it won't find any networks, and sometimes it'll just find one particular distant network briefly that I have no relation to. Often plugging it into the mains will solve the problem. USB power will not. Usually the problem occurs with a low or high charged battery and rarely in between. Manual connection does not help.
I know that there's not much to go on really, but I wondered if anyone who knew more about this stuff than I do could offer suggestions for a fix? The ROM is Xuantunt's 7.8 ROM v5.5. A newer version is out but I can't flash it as I'm away. The problem has been persistent on all releases that I've tried.
Thanks
The speaker was really working really well before the Kitkat update. I am not 100% sure if that was the cause since the phone was updated shortly after I got it. After the update, every now and then the speaker will become really low volume. Sometimes it can be fixed by restarting the phone, but the problem has been happening more and more often. I have the phone for about a month now.
Is anyone else experiencing this problem? Any suggestion in fixing it? Thank you.
Ailin said:
The speaker was really working really well before the Kitkat update. I am not 100% sure if that was the cause since the phone was updated shortly after I got it. After the update, every now and then the speaker will become really low volume. Sometimes it can be fixed by restarting the phone, but the problem has been happening more and more often. I have the phone for about a month now.
Is anyone else experiencing this problem? Any suggestion in fixing it? Thank you.
Click to expand...
Click to collapse
Search xda, its reported already in other threads.
I did not find an answer for this so i wanted to know if the battery bug also happen in cm11?
if not i will just change the rom to cm11 and not wait for a stable release.
There is no such bug, it's a problem caused by usage of charger with one-step charging only, which cause the electronics on the battery to go nuts.
Same goes for using a lousy/bad USB port on your computer, especially if it can't reach 500mAh output for some reason.
so if there is not any problem why motorola said they are checking it and there is a 30 pages thread here with people who complains about this problem?
st379 said:
so if there is not any problem why motorola said they are checking it and there is a 30 pages thread here with people who complains about this problem?
Click to expand...
Click to collapse
Read again what I've written.
I had over 30 moto g passed in my hands in the post 3-4 months and not even 1 have had this issue.
Either I've been extremely lucky and np one ever complained or I dunno.
http://forum.xda-developers.com/showthread.php?t=2545553&page=30
like you can see it is a very strange problem but maybe it is a charger problem.
I just wanted to know if maybe the rom is the blame in this problem.
Hey guys,
Posting here because I am at my wits end with this issue and nobody else has seemed to have this issue. So anyways I am using a Tencent Rog 5 (I know I know) running the latest WW firmware but it didn't seem to matter what firmware I use.
Here is the issue, the phone runs awesome when I am using it but when I leave my phone and it goes idle (screen shuts off etc) the phone will just randomly reboot, I have looked through the logs I got from before and after the phone rebooted on its own but I am not sure what sort of error I should be looking for. Has anyone else had this same issue and solved it? I can't find any posts about this issue.
I can sit here and play high graphics FPS games for hours and no issues it just seems to be when the phone goes idle.
If anyone has some spare time and willing to help me out that would be greatly appreciated.
In case anyone wanted to try and help me figure this out, I really don't know what I would be looking for as I am no tech guy for phones.