Related
Hi
I have another problem with HTC Touch Pro 2 regarding turning the phone on than has been posted in the forums.
Sometimes(every second day) my touch pro 2 wont turn on using the on/off button.
I will have to do a reset(on reset button) to turn the phone back on.
Any idea what can cause this?
HTC Touch Pro 2 using original Danish ROM. Both current version and also a problem first version.
it is called the sleep of death (SOD) , and afaik it has been solved, but I don't know any more about it as I never had it my self !
follow this
http://forum.xda-developers.com/showpost.php?p=5934002&postcount=10
ice_coffee said:
it is called the sleep of death (SOD) , and afaik it has been solved, but I don't know any more about it as I never had it my self !
follow this
http://forum.xda-developers.com/showpost.php?p=5934002&postcount=10
Click to expand...
Click to collapse
Not solved. Author of thread that you pointed to denies it is a SOD fix.
There could be several reasons for the SOD.
Please check out my page about SOD's and comment if you are able to fix it!
http://forum.xda-developers.com/showthread.php?t=704240
last 2 days ive had a similar issue, wont wake with power button when it's slid open
it may be an obvious troubleshooting measure, but have you guys installed any new software recently? if so uninstall...even apps from the marketplace can cause various issues...
I have been having the same problem for several weeks. my phone has been repaired twice and I now have new phone and still getting the same problem. If I disable the data connection it seems to solve the problem but that kind of defeats the object of this type of phone. Disabling the facebook sync option seems to greatly reduce the occurance. I am on t-mobile uk and using stock roms with no additional software.
My experience has been that SOD is not actually SOD but rather just a temporary thing. Put it back in your pocket and try again in few minutes.
had this the first week of ownership, in my case went into the vodafone shop and reported the problem where they swapped the battery in my phone.problem solved.
Hi...I had this same problem with my Sprint TP2. It has now been fixed, but I had to install a custom ROM. I installed the NRG Rom and since then, I have not had the SOD. I believe that Google Maps was causing the phone to enter the sleep, however, I am not positive.
The NRG Max Manila Rom is excellent. I would just install it if I were you and everything will be fine.
-Chris
Try installing LUMOS to avoid SOD
i have a couple of TP2 with the SOD problem.
I read several post recommending LUMOS, so i did a quick test and it seems that it's really solving the SOD and also giving a little more battery dimming the screen.
Give it a try and let us know your comments.
I know your post is old, but my SOD problem is new. What is LUMOS?
Patrick
vpease said:
i have a couple of TP2 with the SOD problem.
I read several post recommending LUMOS, so i did a quick test and it seems that it's really solving the SOD and also giving a little more battery dimming the screen.
Give it a try and let us know your comments.
Click to expand...
Click to collapse
phhill3 said:
I know your post is old, but my SOD problem is new. What is LUMOS?
Patrick
Click to expand...
Click to collapse
Way to thread necro indeed...
I assume he means this app.
I've seen what sounds like this problem on my TP2 and have found the way to revive the phone is to call it from another phone.
Hello,
I have an HTC Desire HD running Android 2.3.3. The device isn't rooted and I've never rooted it before.
I've checked on this site, and I've scoured Google all day but I haven't managed to find anything that matches my problem specifically, as explained below.
In the last couple of days I have been having a bizarre problem where after several minutes of normal use the phone becomes completely unresponsive or very laggy (to the point where it is unusable). This occurs whether I am using apps or simply looking at the home-screen.
The only thing that's responsive is the screen lock button, this works as normal. However when I then try to unlock the screen, the phone is still unresponsive and I'm unable to unlock it.
The only fix I've found (if you can call it a fix) is to leave the phone alone for a several minutes. If I do this I can once again unlock the screen as normal and continue using the phone, however after a few minutes of use it locks up again! This has been happening since last night now and I've found no way to break this cycle.
I did a hard reset to see if this solved the problem but it had no effect. The phone will boot as normal, and after a few minutes of normal use it will become unresponsive again.
I've also booted my phone without the SD card in just in case anything on this was causing the problem, still no improvement.
Has anyone else experienced a similar issue who could provide some insight as to what might be causing this issue? Any help you can provide would be greatly appreciated.
At first I thought this might have been a software issue, but as it persisted after the reset I'm beginning to think this might not be the case.
Thanks,
KaRsKiN
The problem is coming from the magnetometer. I have the same issue, please check this thread: http://forum.xda-developers.com/showthread.php?t=1394264
The only workaround I found is to disable screen rotation and do a couple of restarts (not switch off). Of course, no compass in the end, but at least I can use the phone.
KaRsKiN said:
Hello,
I have an HTC Desire HD running Android 2.3.3. The device isn't rooted and I've never rooted it before.
I've checked on this site, and I've scoured Google all day but I haven't managed to find anything that matches my problem specifically, as explained below.
In the last couple of days I have been having a bizarre problem where after several minutes of normal use the phone becomes completely unresponsive or very laggy (to the point where it is unusable). This occurs whether I am using apps or simply looking at the home-screen.
The only thing that's responsive is the screen lock button, this works as normal. However when I then try to unlock the screen, the phone is still unresponsive and I'm unable to unlock it.
The only fix I've found (if you can call it a fix) is to leave the phone alone for a several minutes. If I do this I can once again unlock the screen as normal and continue using the phone, however after a few minutes of use it locks up again! This has been happening since last night now and I've found no way to break this cycle.
I did a hard reset to see if this solved the problem but it had no effect. The phone will boot as normal, and after a few minutes of normal use it will become unresponsive again.
I've also booted my phone without the SD card in just in case anything on this was causing the problem, still no improvement.
Has anyone else experienced a similar issue who could provide some insight as to what might be causing this issue? Any help you can provide would be greatly appreciated.
At first I thought this might have been a software issue, but as it persisted after the reset I'm beginning to think this might not be the case.
Thanks,
KaRsKiN
Click to expand...
Click to collapse
It is possible that your battery could be failing. See if att has one they will let you exchange.
If its not the battery then it could be a hardware issue. Just send it in for warranty if that is the case. You should still be covered as the phone is not yet a year old.
Sent from my Inspire 4G using xda premium
Gizmoe said:
It is possible that your battery could be failing. See if att has one they will let you exchange.
Click to expand...
Click to collapse
How should this be connected to the battery...?
Anyway, I think that it is a software issue rather than a hardware one. Maybe something is running in the background, using 100% of the cpu. You could try CPUNotify for realtime cpu monitoring.
If that doesn't work, you should try the magnetometer way. Maybe it's a new issue. Never heard about it though
I do what i want, because I can.
Flussen said:
How should this be connected to the battery...?
Anyway, I think that it is a software issue rather than a hardware one. Maybe something is running in the background, using 100% of the cpu. You could try CPUNotify for realtime cpu monitoring.
If that doesn't work, you should try the magnetometer way. Maybe it's a new issue. Never heard about it though
I do what i want, because I can.
Click to expand...
Click to collapse
I'm not going to explain in detail about the relationship of voltages and CPU usage. The battery being bad can and has caused these exact issues. Just like if a power supply is failing it can cause a blue screen in windows. In android the phone rebooting itself or freezing is the equivalent to a blue screen. Since they have never rooted and are on a stock rom there is nothing except a hardware problem that would cause this. If the battery is not the culprit then one of the many components in the phone can cause freezes and reboots if it is failing. Android os does not allow a single task to take over the CPU. This is not a windows os. So like I said, just use your warranty and get it fixed. Stock phones should not be presenting this behavior, you would have to root it to cause these kind of problems.
Sent from my Inspire 4G using xda premium
Gizmoe said:
I'm not going to explain in detail about the relationship of voltages and CPU usage. The battery being bad can and has caused these exact issues. Just like if a power supply is failing it can cause a blue screen in windows. In android the phone rebooting itself or freezing is the equivalent to a blue screen. Since they have never rooted and are on a stock rom there is nothing except a hardware problem that would cause this. If the battery is not the culprit then one of the many components in the phone can cause freezes and reboots if it is failing. Android os does not allow a single task to take over the CPU. This is not a windows os. So like I said, just use your warranty and get it fixed. Stock phones should not be presenting this behavior, you would have to root it to cause these kind of problems.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
Thanks for your help! My dad has the same device as me so I'll try swapping out the battery to see if this solves the problem. If not I'll try calling HTC to arrange a repair.
Any news? Was it the battery issue?
Hi there,
Apologies if this may be a bit of a superficial post but the phone in Q isn't mine so I'm working on second-hand info here. A friend of mine got a G3 off ebay that's t-mobile branded and is supposedly the European model, I haven't checked. (She's using it in the UK nonetheless). Also it has "the latest software updates" (whatever those may be) installed. The phone is not rooted or otherwise tampered with.
Her problem is that occasionally, the phone restarts apparently randomly, though she noted that this happened more when she was in the countryside and the internet connection was coming and going. My guess is that this may have to do with the modem, but not sure. She did some googling and apparently the problem is relatively common but there's no good solution to it.
My two (three) questions are:
- has anyone else encountered this issue?
- any solution to the problem?
- is this a stock firmware issue, ie would installing CMod solve the problem or is this a hardware problem?
Thnx
If it's second-hand phone it's battery issue.
Rushing toward CMod isn't going to solve your problem.
I am also facing the same issue. This also occurs when I'm at my village home. Mostly happens at the same place.
So instead of installing CMod try to change battery because stock Rom is also best and therefore any problem in it means problem in hardware not in software.
But you can still try different techniques. Also tell me if you can solve it.
Installing CM brought no solution for me and still faced random reboots.
i have faced this problem, adter everything i tried then i decided it is battery issue.
i mean change your battery
imamalemdar said:
i have faced this problem, adter everything i tried then i decided it is battery issue.
i mean change your battery
Click to expand...
Click to collapse
Did it work? (Changing the battery...did it resolve the problems?)
wyco said:
Did it work? (Changing the battery...did it resolve the problems?)
Click to expand...
Click to collapse
of course it works now like a rock
I've been having the same issue. My I've used a new battery but my phone acts the same as it did before. Reboots randomly after the wifi, bluetooth, and 3g crash and attempts to recover. The reboot never succeeds and I have to physically pull the battery. Currently using the latest nightly of CM13.
I have had the same issue. I have a stock ROM, fully updated TMobile G3 phone and when i would go to europe, the phone would randomly crash. When it was in airplane mode it would not crash, so i kept it in airplane mode unless i needed to call and i used the wifi calling feature. I thought it was the battery but i have the stock battery and an anker battery and i have never had this problem in the US, it only happened abroad.
I took the plunge to Android 7.0 Nougat, however I am having some major problems. Initially I had everything stock, and every once in a while my phone would reboot when on WiFi. Sometimes it rebooted within 5 minutes of booting back up, sometimes it would reboot 1 hour after booting back up. There is a whole thread about it here (note: not the bootloop issue occasionally talked about in that thread, although it could be related I guess): https://productforums.google.com/forum/#!topic/nexus/kaMOvuf093Q
I was wondering if anyone else has run into this issue? It definitely seems to be linked to WiFi only. A bunch of users apparently narrowed down a few apps that triggered the reboots more frequently (Napster, for example), but the problem seems deeper than just a rogue app. Safe mode does seem to alleviate the issue, but this is not really an acceptable solutions to me. I tried another kernel (Franco's), but that didn't fix anything. I was wondering if anyone who had this problem had any success fixing it by changing ROMs or kernels? I also read that turning off WiFi scanning may also help--I will report back if this fixes anything.
Any suggestions welcome, thanks!
This could be part of the hardware issue that is happening, it talented to me and I finally have my phone back
Sent from my Nexus 5X using Tapatalk
Which Model of LG 5X?
Do you have H-790 or H-791 Model?
Cheesejam said:
I took the plunge to Android 7.0 Nougat, however I am having some major problems. Initially I had everything stock, and every once in a while my phone would reboot when on WiFi. Sometimes it rebooted within 5 minutes of booting back up, sometimes it would reboot 1 hour after booting back up. There is a whole thread about it here (note: not the bootloop issue occasionally talked about in that thread, although it could be related I guess): https://productforums.google.com/forum/#!topic/nexus/kaMOvuf093Q
I was wondering if anyone else has run into this issue? It definitely seems to be linked to WiFi only. A bunch of users apparently narrowed down a few apps that triggered the reboots more frequently (Napster, for example), but the problem seems deeper than just a rogue app. Safe mode does seem to alleviate the issue, but this is not really an acceptable solutions to me. I tried another kernel (Franco's), but that didn't fix anything. I was wondering if anyone who had this problem had any success fixing it by changing ROMs or kernels? I also read that turning off WiFi scanning may also help--I will report back if this fixes anything.
Any suggestions welcome, thanks!
Click to expand...
Click to collapse
sorry my bad, wrong thread
ashokabs said:
Do you have H-790 or H-791 Model?
Click to expand...
Click to collapse
I have a H-790 Nexus 5x on Verizon.
has been happening to me too -- reboots randomly about once or twice a day. (only realize it since fingerprint scanner does not work and i am forced to key my passcode at first login post reboot).
It seems that the H 790 production series are faulty
Nexus 5x reboot problems
Yes it would appear so. However, I have read one post in Google Forums that speaks of problems with H791. However, it could be related to the wifi problem. There are two problems - one is problem booting initially and finally phone does not boot into the ROM and cannot be recovered. This seems to be related to hardware problem in H-790 series. The other has been isolated to the WiFi scanning which causes a crash.
giannism13 said:
It seems that the H 790 production series are faulty
Click to expand...
Click to collapse
Yeah, I am definitely having a problem with the WiFi crash. Would a custom kernel fix this? A custom ROM would, right? Any ideas for a fix for this?
ashokabs said:
Yes it would appear so. However, I have read one post in Google Forums that speaks of problems with H791. However, it could be related to the wifi problem. There are two problems - one is problem booting initially and finally phone does not boot into the ROM and cannot be recovered. This seems to be related to hardware problem in H-790 series. The other has been isolated to the WiFi scanning which causes a crash.
Click to expand...
Click to collapse
I have read the same too, but he's the only one among the hundrends of h790 users who have the same problem.
Cheesejam said:
Yeah, I am definitely having a problem with the WiFi crash. Would a custom kernel fix this? A custom ROM would, right? Any ideas for a fix for this?
Click to expand...
Click to collapse
You could try too, but I doubt it will fix anything. Its a hardware problem
giannism13 said:
I have read the same too, but he's the only one among the hundrends of h790 users who have the same problem.
You could try too, but I doubt it will fix anything. Its a hardware problem
Click to expand...
Click to collapse
I thought the bootloop issue was hardware related, but not the random reboots issue? Ex: Safe mode fixes the problem for me.
ashokabs said:
There are two problems - one is problem booting initially and finally phone does not boot into the ROM and cannot be recovered. This seems to be related to hardware problem in H-790 series.
Click to expand...
Click to collapse
IMO opinion this is just the eMMC dying problem that people have reportedly sporadically over the past 12mo. That problem has affected both H790 and H791. It likely just became more likely to show up after the 7.0 update because that was a large update, but by no means is a large update going to cause the problem by itself. The core problem is eMMC that was waiting to fail and could have happened just when web browsing but a large update just pushed it over the edge. Some phones you can do many large updates and never see a problem, then boom, one day randomly it just reboots and bootloops, with no amount of flashing or resetting making any difference.
Cheesejam said:
I thought the bootloop issue was hardware related, but not the random reboots issue? Ex: Safe mode fixes the problem for me.
Click to expand...
Click to collapse
If safe mode fixes the problem, then I was wrong. Try to find which app conflicts with the system and uninstall it
giannism13 said:
If safe mode fixes the problem, then I was wrong. Try to find which app conflicts with the system and uninstall it
Click to expand...
Click to collapse
I really wish Google would fix this, this isn't really an acceptable solution to me. :/
I have a h790 nexus 5x and haven't seen this issue, knock on wood. However if it's linked to wifi scanning that was issued in another post you may try disabling wifi scanning to see if the issue is resolved. If not it's definitely the emmc in my opinion
Sent from my Nexus 5X using XDA-Developers mobile app
Cheesejam said:
I really wish Google would fix this, this isn't really an acceptable solution to me. :/
Click to expand...
Click to collapse
If it is indeed not a a hardware problem, then don't wait for Google to fix it overnight. Besides, it may be the case that there is no bug at all, and you flashed a corrupted firmware. Your Best bet right now is to try some custom Roms and kernels and see if it fixes the problem. If you don't want to mess with user made firmware then I would suggest you to reflash the latest stock image form Google. If both of the above fail, the you are forced to roll back to marshmallow
You can try to disable wifi scanner on sleep,.
After the Nougat upgrade, I was having random reboots on my 5X (LG-H791). It always happened when my 5X was sleeping (laying on my working desk or on my bedside table for some time). After the reboot it was working fine again for some hours, so it does not seem to be the bootloop issue. I remember that I had a few rare reboots after upgrading to Nougat 7.0, but after the last 7.1.1 upgrade the reboots occured at least every second day.
Last Friday I had enough of it. I downgraded to the last stock Marshmallow 6.0.1 (MTC20K), and it didn't crash a single time after that.
My wife's 5X is having the same random reboots. The reboots are less frequent (but still occur) when WLAN is turned off. I will downgrade her's too, if my 5X is still still stable after the next weekend.
I wonder if this is a different problem, or if this is just a first symptom of the bootloop issue. If it's a bug in Nougat, then shouldn't much more (if not all) 5X owners experience these random reboots?
Cheesejam said:
I took the plunge to Android 7.0 Nougat, however I am having some major problems. Initially I had everything stock, and every once in a while my phone would reboot when on WiFi. Sometimes it rebooted within 5 minutes of booting back up, sometimes it would reboot 1 hour after booting back up. There is a whole thread about it here (note: not the bootloop issue occasionally talked about in that thread, although it could be related I guess):
I was wondering if anyone else has run into this issue? It definitely seems to be linked to WiFi only. A bunch of users apparently narrowed down a few apps that triggered the reboots more frequently (Napster, for example), but the problem seems deeper than just a rogue app. Safe mode does seem to alleviate the issue, but this is not really an acceptable solutions to me. I tried another kernel (Franco's), but that didn't fix anything. I was wondering if anyone who had this problem had any success fixing it by changing ROMs or kernels? I also read that turning off WiFi scanning may also help--I will report back if this fixes anything.
Any suggestions welcome, thanks!
Click to expand...
Click to collapse
hi, i had the exact same problem with my nexus 5x from carphonewarehouse (uk), and when it was given in to repair i was promised money in return, however they ended up refusing to give money and gave a replacement phone instead, the only way to fix this issue is apparently to get a replacement, as it is most likely a hardware issue google haven't accounted for
I've had the random restart issue for a while now. I got a "new" replacement in November for a different issue and have been on 7.0 the whole time (until last week when I got 7.1.1 OTA). I'm going to call today about another replacement. I've just had two restarts in the last hour.
Hello guys, quick question. Anyone here who faced random reboots issue in the past actually had it fixed completely? I saw various threads on many forums about people having this kind of problem but no one claimed their phones got fixed. I bought my phone from an unauthorized retailer so repaired or replacement by OP is kinda impossible. Any helps would be much appreciated.
p/s: i contacted the OP support team and was set up with a remote session. However, all they did was downgrading my phone from 4.0.1 to 3.1.2 and things havent improved since.
JustRice said:
Hello guys, quick question. Anyone here who faced random reboots issue in the past actually had it fixed completely? I saw various threads on many forums about people having this kind of problem but no one claimed their phones got fixed. I bought my phone from an unauthorized retailer so repaired or replacement by OP is kinda impossible. Any helps would be much appreciated.
p/s: i contacted the OP support team and was set up with a remote session. However, all they did was downgrading my phone from 4.0.1 to 3.1.2 and things havent improved since.
Click to expand...
Click to collapse
Sideload your phone with an official 3.2.8 OOS and do a full wipe on it if it's a ROM problem will get fixed. If it's a hardware one it might not be fixed and you need further investigation to see what it's causing a faulty action that gets you randomly reboot.
Sent from my OnePlus3 using XDA Labs
chasemyass said:
Sideload your phone with an official 3.2.8 OOS and do a full wipe on it if it's a ROM problem will get fixed. If it's a hardware one it might not be fixed and you need further investigation to see what it's causing a faulty action that gets you randomly reboot.
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
Thanks bud. I tried it, sideloaded 3.2.8 then performed a factory reset. The phone stayed normal about 5 hours and then reboot while idling. I think this might be a hardware problem. Dont know what to do now since i bought this one from a unauthorized seller