I can't figure out what's causing it. I don't have very many apps installed that didn't come with the phone, and any I did install were from the Play Store. I haven't done any modifications such as root to the device.
In order to bring it back to life, I have to either hold the power button down for 30 seconds to shut it down (or take out the battery) and power it back on.
Interestingly, if I have notifications waiting and the LED is flashing, that continues to flash even if the phone won't wake up.
I did 'disable' several of the bloatware apps in the app management area in Settings. I'm starting to think that must be what's causing it. Is there a particular bloatware app that should never be disabled? One that would cause this issue?
Other apps I've installed are things like Netflix, eBay, the app for my bank, and a TV-listings app. Pretty basic stuff. I don't think any of those would be the problem, would they?
Remaining battery doesn't appear to have an effect. It's happened with full battery and somewhat low battery.
'Services' that I use are Exchange push email and Gmail. I also have it Bluetooth synched to my car's hands-free thing.
Any help would be appreciated. Taking my phone out of my pocket to use it just to find that it's not responsive is very troublesome.
Thanks.
EDIT: For clarification, this is an AT&T version of the S4A.
EvilTelephone said:
I can't figure out what's causing it. I don't have very many apps installed that didn't come with the phone, and any I did install were from the Play Store. I haven't done any modifications such as root to the device.
In order to bring it back to life, I have to either hold the power button down for 30 seconds to shut it down (or take out the battery) and power it back on.
Interestingly, if I have notifications waiting and the LED is flashing, that continues to flash even if the phone won't wake up.
I did 'disable' several of the bloatware apps in the app management area in Settings. I'm starting to think that must be what's causing it. Is there a particular bloatware app that should never be disabled? One that would cause this issue?
Other apps I've installed are things like Netflix, eBay, the app for my bank, and a TV-listings app. Pretty basic stuff. I don't think any of those would be the problem, would they?
Remaining battery doesn't appear to have an effect. It's happened with full battery and somewhat low battery.
'Services' that I use are Exchange push email and Gmail. I also have it Bluetooth synched to my car's hands-free thing.
Any help would be appreciated. Taking my phone out of my pocket to use it just to find that it's not responsive is very troublesome.
Thanks.
EDIT: For clarification, this is an AT&T version of the S4A.
Click to expand...
Click to collapse
maybe u can enable back all the apps that u have disabled and see if it happens anymore.
u mentioned "the phone won't wake up" and "not responsive". do u mean that the screen stayed off and u are unable to get the screen to be on?
cfchong said:
u mentioned "the phone won't wake up" and "not responsive". do u mean that the screen stayed off and u are unable to get the screen to be on?
Click to expand...
Click to collapse
That's right. None of the buttons wake the phone up or turn on the screen. I can tell the phone is still 'on' though. It's not like it got powered off in my pocket.
The advice you've got is sound - if you think it might be because of disabled apps, re-enable them all and see if it keeps happening. If it doesn't... well then you disable them one at a time until it starts happening again.
Then you come back to the forum again and let everyone know which app never to disable.
If it doesn't stop happening after re-enabling all the apps... well then my guess would be a faulty device. Can't think of any other logical reason for it to behave like that. So try the apps first, if that doesn't help, "return to sender".
EvilTelephone said:
That's right. None of the buttons wake the phone up or turn on the screen. I can tell the phone is still 'on' though. It's not like it got powered off in my pocket.
Click to expand...
Click to collapse
if enabling back all system apps do not resolve the problem, try disabling all user apps to test. one of your downloaded app may be the cause.
Alright, over the past month I've done a bunch of testing. Here are my results.
1. Re-enabling all the system apps didn't help.
2. I uninstalled all my user apps. Didn't help.
3. I completely reset the phone to stock settings and formatted all storage. That didn't help.
4. I figured maybe it was something with bluetooth since it seemed to happen after I used bluetooth devices. I disabled bluetooth completely. It didn't help.
I'm out of ideas for the moment. Could the phone just be bad? I would wonder why the issue only happens occasionally.
Thanks.
Start a chat with Samsung. They have always been good to me.
GT-i9295(i537) running SafeStrap
I have the same problem, is there any solution, thanks
ogbeate said:
I have the same problem, is there any solution, thanks
Click to expand...
Click to collapse
Solved, rom change and ready, do not turn off more
I have the same problem in i9500. I now live in China and have purchased an s2, s3 and now the s4 from China Unicom. I have successfully rooted and flashed new ROMS (latest HK stock firmware) on the S2 and S3. When I bought the s4, it worked fine. I immediately flashed the latest stock HK ROM using Odin 3.07, After flashing, the phone is unresponsive after going into deep sleep meaning that nothing happens when I press the power button. After a long press of the power button, the phone will re-boot. Sometimes I have to pull the battery. Again, this phone is totally stock. I haven't added any applications. I re-flashed the stock China Unicom formware and I took the phone to the Samsung Service facility and they did a new flash. Phone worked great. I take it home, flash the HK ROM with Odin...same results; phone is unresponsive after going into deep sleep. I return to the Samsung service store and they again flash the phone. Phone works fine. What are they doing that I'm not doing? Could the partition table get corrupted during my flash processes. Should I try another version of Odin? Should I try a PIT file and try that? I'm downloading the ROM's from SamMobile. Thanks in advance for any suggestions.
Edit: I fixed this problem by upgrading to 4.3 which brought it's own set of problems.
Related
[FIX][08.04.2011]Patch for "Screen won't come on after device wakes" (RHO_S2_00895)
Problem: Device doesn't come back from suspended mode. Pressing the power button, sliding out the keyboard or taking out the stylus does nothing.
Occurrence: Random.
Quick fix: None known.
Request: Kinda all over the Rhod forums.
Affected ROMs: HTC Stock S2 2.07, all custom roms based on 2.07 drivers. Probably 2.10 drivers are partly affected too.
Patch:
For stock roms (standard HTC patch package, .exe)
For custom roms (download this if you're unsure, works for stock roms too)
For cooks (extract and put into OEMDrivers)
Thanks!
Let's see (in time) if the SOD's are finished for us.
HRQ.SLV said:
Thanks!
Let's see (in time) if the SOD's are finished for us.
Click to expand...
Click to collapse
It must be a matter of settings or hardware, I never suffered from SoD.
Jackos said:
It must be a matter of settings or hardware, I never suffered from SoD.
Click to expand...
Click to collapse
That's because youre a great cook!
This thread should be sticky...
HRQ.SLV said:
That's because youre a great cook!
This thread should be sticky...
Click to expand...
Click to collapse
Not only this one should be sticky...
.......Done
Installed. Didn't work . I think the flex cable is crapping out. Also had the problem where if the screen was fully slid, it'd black out. Now it's been like that every postion.
Although, the power button works to turn the screen off, it won't turn it back on.
It doesn't work for me either
The only thing that I was able to install on my Tilt 2 (latest stock ROM) was this file Jackos RHO_S2_00895.cab
Nothing changed.
The screen goes on but what stays off is the backlight and the only way to get the backlight to stay on in a reboot. Then try to adjust the brightness from the settings menu and moving the slides doesn't do anything. The brightness stays to the max no matter what.
Is it the light sensor? can it be disabled or checked somehow?
Thanks anyway I hope your fix helps others,
G
Jackos said:
It must be a matter of settings or hardware, I never suffered from SoD.
Click to expand...
Click to collapse
Thanks for sharing...I have had SOD only with certain builds...its been a while since I had one...
KnightmareCS said:
Installed. Didn't work . I think the flex cable is crapping out. Also had the problem where if the screen was fully slid, it'd black out. Now it's been like that every postion.
Although, the power button works to turn the screen off, it won't turn it back on.
Click to expand...
Click to collapse
Does it sometimes don't come back or always?
SoD, Sleep Of Death, so called the hangup issue does happen only after the device is suspended for a long time. It does occur kinda often, but not always if you turn off the screen. If your device never comes back from standby it isn't a problem with SoD for sure.
That would be my [email protected] cable....
KnightmareCS said:
Installed. Didn't work . I think the flex cable is crapping out. Also had the problem where if the screen was fully slid, it'd black out. Now it's been like that every postion.
Although, the power button works to turn the screen off, it won't turn it back on.
Click to expand...
Click to collapse
bisanti said:
The only thing that I was able to install on my Tilt 2 (latest stock ROM) was this file Jackos RHO_S2_00895.cab
Nothing changed.
The screen goes on but what stays off is the backlight and the only way to get the backlight to stay on in a reboot. Then try to adjust the brightness from the settings menu and moving the slides doesn't do anything. The brightness stays to the max no matter what.
Is it the light sensor? can it be disabled or checked somehow?
Thanks anyway I hope your fix helps others,
G
Click to expand...
Click to collapse
The exe file (for stock roms) is intended to work on Europe roms. I have no knowledge of HTC releasing this patch for other regions.
It's no fix for any problem with the phone The patch doesn't even touch the backlight thing.
Jackos said:
Does it sometimes don't come back or always?
SoD, Sleep Of Death, so called the hangup issue does happen only after the device is suspended for a long time. It does occur kinda often, but not always if you turn off the screen. If your device never comes back from standby it isn't a problem with SoD for sure.
Click to expand...
Click to collapse
It happens all the time. I turn the phone on via the power button. Boots up. Let it sit till backlight goes off. Press power button, nothing happens.
I can turn the phone on, press the power button to turn the backlight off and when I press it again, nothing happens.
Wild Child said:
That would be my [email protected] cable....
Click to expand...
Click to collapse
I do not think it's a flexcable problem. If I can turn the screen off and power on the device with the 'power button', it has to be something software.
I have to check again if the device comes back on, but with really really low backlight.
It's annoying, I have to restart to see a text, missed call, etc.
Thanks for your help so far.
Won't wake up
I tried loading this patch after doing yet another hard reset to try to recover from these outages. It doesn't work. Within an hour of installing it, the problem came back. My specific problem is the system goes to sleep after a minute, and it usually comes back with the power button. But after normal usage for awhile (sometimes hours, sometimes weeks without a problem), it goes to sleep and needs a red-button-reset to turn back on. Then as soon as it goes to sleep again after powering up, it's off forever. The only real recover after reaching this "cycle of death" is a hard reset (full memory erase, back to factory settings). Then it will work normally again for awhile.
I'm not sure if this is exactly the problem the other submitters were seeing, but it is surely related.
I'm off to do yet another factory reset. WM 6.5 is not worth a tinker's damn.
(AT&T Tilt 2 with ROM 2.10.502.4)
pbarschall said:
I tried loading this patch after doing yet another hard reset to try to recover from these outages. It doesn't work. Within an hour of installing it, the problem came back. My specific problem is the system goes to sleep after a minute, and it usually comes back with the power button. But after normal usage for awhile (sometimes hours, sometimes weeks without a problem), it goes to sleep and needs a red-button-reset to turn back on. Then as soon as it goes to sleep again after powering up, it's off forever. The only real recover after reaching this "cycle of death" is a hard reset (full memory erase, back to factory settings). Then it will work normally again for awhile.
I'm not sure if this is exactly the problem the other submitters were seeing, but it is surely related.
I'm off to do yet another factory reset. WM 6.5 is not worth a tinker's damn.
(AT&T Tilt 2 with ROM 2.10.502.4)
Click to expand...
Click to collapse
It's a pity that it doesn't work for you. This is a patch for Europe branded devices, I don't even see the fix at any other region-based HTC support site.
Personally I never experienced SoD, so I cannot guarantee that it does work. All I know is that this fix is supposed to help with "constant hang". Whatever it is. It's a official fix and I didn't encounter any problems with running it on my Europe branded Rhod.
Jackos is this in your ROM? I have found several times my TP2 needs a reset as the power button does not bring it life. If I take the stylus out (when this happens) the row of keys light up, but still the display is blank. I assume it's already in your ROM (Jackos S3 1.1.2 SleekBASIC) otherwise I would have installed it.
It's going to be included from version 1.1.3 and up.
Jackos said:
It's a pity that it doesn't work for you. This is a patch for Europe branded devices, I don't even see the fix at any other region-based HTC support site.
Personally I never experienced SoD, so I cannot guarantee that it does work. All I know is that this fix is supposed to help with "constant hang". Whatever it is. It's a official fix and I didn't encounter any problems with running it on my Europe branded Rhod.
Click to expand...
Click to collapse
So...how do I uninstall it? I am on sprint in the US and have the latest official win 6.5 ROM and downloaded this update on my phone through a tech website and after installing it none of my keys works except for the power button. Apparently being for Europe it has corrupted my phone and none of the talk, end, windows, back or keyboard buttons work now. I need to revert this update, is there a way without doing a hard reset. I don't want to reconfigure all my settings that aren't backed up.
scottandmo said:
So...how do I uninstall it? I am on sprint in the US and have the latest official win 6.5 ROM and downloaded this update on my phone through a tech website and after installing it none of my keys works except for the power button. No talk, end, windows, back or keyboard buttons work now. I need to revert this update, is there a way without doing a hard reset. I don't want to reconfigure all my settings that aren't backed up.
Click to expand...
Click to collapse
If anything really fails, navigate into /Windows/ directory using your favorite file manager and "delete" those two files:
Code:
debuglog.dll
HtcPm.dll
Probably deleting the second file should fix your keyboard issues.
Jackos said:
If anything really fails, navigate into /Windows/ directory using your favorite file manager and "delete" those two files:
Code:
debuglog.dll
HtcPm.dll
Probably deleting the second file should fix your keyboard issues.
Click to expand...
Click to collapse
Deleting the HtcPm.dll and rebooting fixed it, Thanks! I'm assuming that won't have any other side effects...
I am hoping someone has dealt with either of the following problems, and come up with a way to effectively diagnose and fix either.
The phone - 1101 build; running AT&T Stock KK4; rooted via kernel swap method (using stock KK4 kernel after swap, i.e., do not have clockwork recovery); some AT&T bloatware frozen with TiBu, otherwise stock with root
Problem #1 - roughly once a day, the phone will freeze when in sleep mode; I have had this happen with both the slide to unlock and Exchange PIN lock screen up; when I hit power to wake the phone, the screen wakes up but is unresponsive and then the screen won't shot off again; live wallpaper is frozen in place, but if the phone was plugged in, the battery icon continues with the animation loop. And if the phone is not plugged in, battery power drops rapidly in this state.
The phone isn't completely dead, because if I connect/disconnect it via USB (set to debug mode) to my laptop, the computer recognizes the phone is connected, but it is dead enough that if I call the phone, it does not recognize the missed call. The only way I can restore the phone is a battery pull. Usually it takes several minutes for the phone to come back after this, acting like it would if I had flushed the dalvik cache or installed an update.zip from recovery.
Problem #2 -also roughly once a day, at random times the screen will wake up momentarily, then clear, and I will hear the AT&T boot up sound, after a short while, the phone will run through the media scanner and any other startup launches, acting as though it had been turned on, but the battery stats show continuous uptime throughout. I have had this happen when using the phone, including when on a phone call (and the call did not drop).
I have seen problem #2 on virtually all of the AT&T GB leaks, and it seems to get more frequent the more apps that are installed. I had not seen problem #1 until recently.
The phone is out of warranty, and owned by my employer. I am not due for a new phone from them until July. I've done more master clear/reflash stock cycles than I care to admit, tried replacing/testing for disk errors the external SD card, etc..., and am afraid of doing that and having the problems come up again.
Any thoughts on how to diagnose either of these problems?
Hmm... I don't really think there is an exact diagnosis for any of these issues. Some phones are just problematic like that. The only thing I can suggest is trying a different ROM or kernel, and that might help your stability.
I have the exact same problems. Hope someone comes up with a fix. The only help I can give you is that when the phone freezes, instead of pulling the battery, you can hold the vol up & power buttons for 10 seconds and the phone will restart. Easier than pulling your phone apart, especially if you have it in a case, like I do.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
korockinout13 said:
Hmm... I don't really think there is an exact diagnosis for any of these issues. Some phones are just problematic like that. The only thing I can suggest is trying a different ROM or kernel, and that might help your stability.
Click to expand...
Click to collapse
So, the way I see it, unfortunately these problems could be a function of:
Bad hardware
Misbehaving app
ROM issue
Kernel issue
I tried pretty much every leaked AT&T GB ROM and had random reboots with all of them. Seems to track with the number of apps installed, but can't prove that. I have not tried any custom ROMs or kernels.
Since this is technically not my phone, I am trying to avoid doing anything that can't really be undone if I need to turn the phone back in at some point. And I need something that can be a daily driver for work calls and Exchange email, and rely heavily on tethering when I am on the road.
Anyone with ideas on what to test, or how to capture enough log information to figure out where the problem is, would be a big help. Otherwise, I am stuck riding this out until July when I can get a new phone from my employer.
Nothing you do can't be undone, it's just a simple Odin flash away.
Be sure to back up your efs folder before flashing too much
studacris said:
Nothing you do can't be undone, it's just a simple Odin flash away.
Be sure to back up your efs folder before flashing too much
Click to expand...
Click to collapse
I've used Odin with the various GB leaks; if I go further afield (heck, performance is dicey already, how many more problems could I have with one of the ICS alphas), is it still a straight shot back to stock KK4, or are there other steps to do first?
And before I go down that road, any suggestions on diagnostics (other than yet again pulling apps off of the Captivate to see if one of them is the culprit...?)
stoobie-doo said:
I've used Odin with the various GB leaks; if I go further afield (heck, performance is dicey already, how many more problems could I have with one of the ICS alphas), is it still a straight shot back to stock KK4, or are there other steps to do first?
And before I go down that road, any suggestions on diagnostics (other than yet again pulling apps off of the Captivate to see if one of them is the culprit...?)
Click to expand...
Click to collapse
You actually might have less problems on ICS. But it all depends. You can always get back to stock with one, bootloader-free, safe flash. Diagnostics wise, there isn't really much you can do besides removing apps. I would only worry about the ones that are constantly running in the background, as they could possibly be screwing with the phone while in sleep. I think it's unlikely that this sort of testing would actually help though. I still say try something different.
stoobie-doo said:
Anyone with ideas on what to test, or how to capture enough log information to figure out where the problem is, would be a big help. Otherwise, I am stuck riding this out until July when I can get a new phone from my employer.
Click to expand...
Click to collapse
I am having the same issues except in my case I have tried to recreate the conditions and check memory and I am close to maxing it out. Part of my problem is that I come from a Palm background and I have found that Android, or at least the Cappy, is not as responsive (I was really spoiled by Cards on my Pre) I was thinking that my Android noobness is causing me to push the phone too hard and locking it up. FWIW, you might want to check memory issues
So i've been experiencing this issue for months now. I've had the issue since i've gotten the phone but its the past few months that its really gotten bad. So before anyone jumps the gun, i've done quite a bit of research on this and cannot find anything worthwhile, more on that soon.
So as usual, i'll pickup my phone and press the power button or the home button to turn on the screen, but at completely random times the screen will not come on at all. Sometimes the capacitive buttons will light up (maybe 15-20% of the time), but not always.
In my searches I found the following solutions to this problem:
Get a new sim card
Dont use an SD card
Get a new battery
Check the leads on the battery and phone for cleanliness
Factory reset
Remove 1 app at a time and test until it stops happening
Dont freeze any apps
Restore stock firmware
Dont use SetCPU
Turn off animations
Get rid of the lock screen
Remove custom message from lock screen
Clear cache through Recovery
Dont restore data with Titanium Backup when restoring apps
Turn off WiFi and/or Bluetooth and/or GPS
Dont use GreenPower or Greenify
Avoid stock launcher
I have tried all of the above except for removing 1 app at a time (and those that dont apply). I'm deep into that one and only have a few apps left to try. This is something that happens at least once a day, but typically 3-5 times in a day. I used to think i could make it happen by pressing the power button to turn on the screen and immediately hit it again to turn it off. It would sometimes work but that doesnt trigger it anymore.
My phone used to be rooted, but being on AT&T there was no "normal" way to flash a good recovery like CWM or TWRP and install roms, you have to use some other thing which i dont use. So i've always had stock recovery, im fully updated to the newest stock rom that is out, update came OTA which was after i removed root and used odin to flash an older stock rom back. My wife's Note 3 also has the same issue and it has never been rooted, we have gone through all of the above and still it continues to happen.
Also on a side note, my phone was swapped out because of an issue it had 3 months after i purchased the phone. I was able to get a brand new one, not refurbished. The issue had occured once or twice before the swap and an incredibly frustrating amount of times since then.
Reading through most of the other threads, everyone seems to have to remove their battery and re-insert it to get back into their phone. The ones that dont have to do that have found that removing their SD Card, getting a new one, sending the phone in, or one of the other options have worked. However for me, nothing has worked.
Does anyone have any other ideas? Is this common on the Note 3 (I've had it since release)? 70% of the time i can hold the power button for a few seconds to try and bring up the power menu and it works, but not always.. I usually just have to wait up to a minute or two (never actually counted, i use my phone for that stuff...which.. isnt..working...)
I've had wake lock lag on a few android phones. Even iPhones.
I would highly recommend rooting it on att and flash a mod that reduces it on the note 3. I talked about it here.
http://forum.xda-developers.com/showthread.php?t=2628716
Rebooting the phone always helps.
wudien said:
I've had wake lock lag on a few android phones. Even iPhones.
I would highly recommend rooting it on att and flash a mod that reduces it on the note 3. I talked about it here.
http://forum.xda-developers.com/showthread.php?t=2628716
Rebooting the phone always helps.
Click to expand...
Click to collapse
Unfortunately I cannot root my phone. I have to have my company email on my phone, and for Android devices they use Air Watch. I tried for weeks to get it working while rooted, and even used Root Cloak or something like that (with Wanam Xposed) to hide root from specific apps. Air Watch was specifically tested to work with that app but it still for some reason didn't work (new version of Air Watch perhaps with no update to Root Cloak? Just my guess). I had to remove root, factory reset and re-flash stock from Odin (that was a dual purpose flash) to remove all traces of Root so I could use Air Watch for my company email/calendar/contacts/etc again, even after unrooting and using all the cleanup tools, triangle away, and everything, it still detected my phone as rooted...
However, I don't think that's really a viable solution to the problem, that's more of a band aid. Looking at that thread and looking around, it seems to work well but I still haven't found anyone with my same issue where they used it and it worked. I would like to narrow this down to what the issue is exactly, the root cause. I think its a problem with KitKat, or at least all of 4.4.x (not sure about 4.4.4 yet).
Ok, so I bought a brand new in box Moto X from an acquaintance. After a month or two it started randomly rebooting, and after a couple of weeks of rebooting once or more per day, it died. Wouldn't power on (not even recovery). I sent it in for repair>got it back>3 days and it died again>sent it in again>got it back>1 day and it died again>sent it in again>got replacement>2-3 months later the new phone is starting the cycle again. Every time I pull it out of my pocket, the lock button doesn't work, and it's locked up on Active Display. I hold the power button and reboot it, only to have it happen again in an hour. I am doing a factory reset now--does anyone have any idea what the problem may be? what i should avoid when setting it up again?
This phone is 100% untampered with. No root, no nothing.
Please help me out. Thanks!
quaxer said:
Ok, so I bought a brand new in box Moto X from an acquaintance. After a month or two it started randomly rebooting, and after a couple of weeks of rebooting once or more per day, it died. Wouldn't power on (not even recovery). I sent it in for repair>got it back>3 days and it died again>sent it in again>got it back>1 day and it died again>sent it in again>got replacement>2-3 months later the new phone is starting the cycle again. Every time I pull it out of my pocket, the lock button doesn't work, and it's locked up on Active Display. I hold the power button and reboot it, only to have it happen again in an hour. I am doing a factory reset now--does anyone have any idea what the problem may be? what i should avoid when setting it up again?
This phone is 100% untampered with. No root, no nothing.
Please help me out. Thanks!
Click to expand...
Click to collapse
That sounds like a headache.
When were both phones manufactured? What version of KK were you running? Did you upgrade software OTA, if so what did it upgrade to?
Are you saying you never downloaded any apps? never installed anything on the phone? What services did you use? (apps.. anything, what were they?) Were there any other things you noticed out of the ordinary? What were Motorola's responses the first time they replaced the phone? What are their responses now that you are having the same issues with this replacement device?
Otherwise I'd advise you let us know what modifications (apps installed, anything) you had done and continue to do, that will give a variable context to the issue, at least. Other wise we a have an issue with no variables on the actual phone. The more information you give the higher quality the responses you can receive
bothgoodandbad said:
That sounds like a headache.
When were both phones manufactured? What version of KK were you running? Did you upgrade software OTA, if so what did it upgrade to?
Are you saying you never downloaded any apps? never installed anything on the phone? What services did you use? (apps.. anything, what were they?) Were there any other things you noticed out of the ordinary? What were Motorola's responses the first time they replaced the phone? What are their responses now that you are having the same issues with this replacement device?
Otherwise I'd advise you let us know what modifications (apps installed, anything) you had done and continue to do, that will give a variable context to the issue, at least. Other wise we a have an issue with no variables on the actual phone. The more information you give the higher quality the responses you can receive
Click to expand...
Click to collapse
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
quaxer said:
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
Click to expand...
Click to collapse
Thanks, hopefully your info helps someone help you better or hopefully it can help/spark someone truly seasoned in android/moto x etc to chime in
To check your manufacture date boot into your fastboot menu, check image to verify you're there.
Then choose BP Tools and then once that menu loads choose the option for UPC/Manufacture date read out, check for the date when it appears on the screen, maybe you are on a batch that has specific issues.
I've never heard of this issue, yuk sounds terrible. Goodluck! If you do end up finding answers somewhere else can you please come back here and post the resolution?
When I hit BP Tools it just reboots the phone... I don't know what's wrong???
maybe static electricity?
or do you use any cases?
maybe wrong charger?
Multiple devices, different Android versions, Sounds like an app issue to me.
If it happens frequently, then that is good in a way... You could factory reset and don't install a single app. If it doesn't act up for a couple days ..... Install about 5 apps. Go a couple days.... Install 5 more, etc... Etc. When it starts to act up, you know it's an app you recently installed, so it'll be easier to narrow down.
A logcat could help too. Search on that for how. It would likely show what happened at the time of the reboot /shutdown.
quaxer said:
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
Click to expand...
Click to collapse
quaxer said:
When I hit BP Tools it just reboots the phone... I don't know what's wrong???
Click to expand...
Click to collapse
use the volume +up button (once BP Tools is highlighted) and not the power button to select BP Tools I'm assuming that's what's happening, hmm
I would send it back to Motorola again. If the issues continue, tell them you want it replaced with something else like the 2014 Moto X.
Ok -- so the issues stopped completely over Christmas vacation, but I went back to work this morning (I work in a dusty woodworking plant) with my phone in my pocket, and bang, they were back. Every time I pulled my phone out of my pocket it had powered off, and finally it didn't want to power back on. I called Moto, and this time actually got a competent rep on the line. He blamed the issues on static electricity, and I second his opinion, because the machinery I work with tends to create some static, and the dust in my pocket may exacerbate the problem (?)
Anyway, he recommended that I plug the phone in and hold the power button for 2 minutes to drain the static. Voila! It seems to have worked.
Solved for the time being. Thanks everyone for your input.
quaxer said:
Ok -- so the issues stopped completely over Christmas vacation, but I went back to work this morning (I work in a dusty woodworking plant) with my phone in my pocket, and bang, they were back. Every time I pulled my phone out of my pocket it had powered off, and finally it didn't want to power back on. I called Moto, and this time actually got a competent rep on the line. He blamed the issues on static electricity, and I second his opinion, because the machinery I work with tends to create some static, and the dust in my pocket may exacerbate the problem (?)
Anyway, he recommended that I plug the phone in and hold the power button for 2 minutes to drain the static. Voila! It seems to have worked.
Solved for the time being. Thanks everyone for your input.
Click to expand...
Click to collapse
This thread is awesome.
Also, I recommend leaving your phone on your desk/home/car when you work
Or maybe a full-body armor case or something.
Statics & electronics = bad idea. Even if you can drain it and it works, it's still hurting the components inside.
So, it's been a bit, but I just came back to this phone. I never did send it in to Moto, though it seemed to have died completely. It sat in the drawer for a couple of weeks, and now on a whim I plugged it into my computer, and it started up! I had never tried plugging it into a computer, just chargers...
BUT,
In the last 10 minutes it's been sitting here rebooting itself every 2 minutes... I guess I'll try wiping it again (It didn't do the trick last time), but this phone has serious problems.
Hi, this happend already to me few times so I decided to put it on here.
Sometimes when I pick up my phone and try to unlock it nothing happens, fingerprint and button all the same it looks like it completely Off. Then i have to press few times a button to actually start it and it's booting. There is huge battery loss after it boot up. See image.
I am in Stock 4.0.2 no root just few standard apps installed. Nothing fancy. This happend already few times to me. I left the phone locked and when I want to unlock its dead. Also it is behaving weirdly, when I turn it off manually I just need to press longer a button and it's turning on, but here I need to press it few times to work.
Does it happen to anyone else?
terragady said:
Hi, this happend already to me few times so I decided to put it on here.
Sometimes when I pick up my phone and try to unlock it nothing happens, fingerprint and button all the same it looks like it completely Off. Then i have to press few times a button to actually start it and it's booting. There is huge battery loss after it boot up. See image.
I am in Stock 4.0.2 no root just few standard apps installed. Nothing fancy. This happend already few times to me. I left the phone locked and when I want to unlock its dead. Also it is behaving weirdly, when I turn it off manually I just need to press longer a button and it's turning on, but here I need to press it few times to work.
Does it happen to anyone else?
Click to expand...
Click to collapse
Honestly, there's not enough information to understand exactly why it's happening. You need to get a logcat in the time before the reboot; unfortunately, logcats get erased during a reboot so it might be a little tricky getting it if the reboot is seemingly random. Someone had posted this as a possible way of getting the log:
"Retrieving the logs is tricky, since the log cache gets erased on reboot. If the phone reboots even while sitting on a charger, try running adb logcat continuously (you will need Android SDK and USB drivers installed and configured on your PC.) When the phone reboots, look at the last several pages in the command prompt window for any errors or abnormalities."
Click to expand...
Click to collapse
Otherwise, it's hard for anyone to help. I'm not much help in actually figuring out the issue, but I know if you can get the log, someone else probably can help.
For more information on logcats: Logcat Tutorial
Yeah I was trying to connect it to PC but nothing, so it is turned off. I will try next time to run command when turning on, maybe there will be something but I do not see it working before it gets erased. I was hoping that anyone else is having this problem so it might be rom related. It is completely random so you can;t guess when it happens.
I had it only few times so it's not super annoying but still it is not normal behavior. In addition it is weird that battery went from 55% to 33%, just phone reboot will not drain that much... I hope there is nothing wrong with the phone itself.
terragady said:
Yeah I was trying to connect it to PC but nothing, so it is turned off. I will try next time to run command when turning on, maybe there will be something but I do not see it working before it gets erased. I was hoping that anyone else is having this problem so it might be rom related. It is completely random so you can;t guess when it happens.
I had it only few times so it's not super annoying but still it is not normal behavior. In addition it is weird that battery went from 55% to 33%, just phone reboot will not drain that much... I hope there is nothing wrong with the phone itself.
Click to expand...
Click to collapse
Check in advanced to see if schedule off is on
Nope it's off
Happened to me to on 4.0.2. Rebooted twice a day.
Solution to me was Qualcomm flash back to stock 3.5.1 and uodate from internal to 3.5.4. OTA 4.0.2.
The theard "how to unbrick".
Not one reboot until now in days.
I think I found a culprit responsible for it. It is Hill Climb 2 game which doesn't close properly sometimes and I think it causes some kind of crash in the system. Is it possible?
terragady said:
I think I found a culprit responsible for it. It is Hill Climb 2 game which doesn't close properly sometimes and I think it causes some kind of crash in the system. Is it possible?
Click to expand...
Click to collapse
It's possible. Not necessarily the reason, but it might be. Either uninstall the app or freeze it using Titanium. Greenify might also work, but that allows the app to start itself up and potentially continue the issue. See if that stops the crashes for a couple of days.
The problem is that it doesn't happen often and only when I quit the game and lock the phone immediately after that. I am not sure if that's a reason though, just guessing because it happens after this last time. I will uninstall this game anyway, it's just time eater