The 1st time that this happened, I thought that I may have done something wrong, but it happened again today. My phone turns itself off, requiring a long press on the power button (30 sec) to restart. When it restarted, I noticed a 10% or do drop in remaining charge in the battery (see attached, directly above the ":" in the text at the bottom). Has anyone else had a similar experience?
Sent from my LG-E970 using xda app-developers app
Personally hasnt happened to me. My brothers did something similar last night though. I wouldnt worry about it to much unless it keeps happening. Could just be an app acting up or a bug in the os. Phone is still new software bugs still exist all over the place.
whiteguypl said:
Personally hasnt happened to me. My brothers did something similar last night though. I wouldnt worry about it to much unless it keeps happening. Could just be an app acting up or a bug in the os. Phone is still new software bugs still exist all over the place.
Click to expand...
Click to collapse
The biggest concern is the prob with the restart. It almost seemed like it had bricked itself.
It was the same for my brother. Wouldn't start until he plugged into the PC. But he didn't know holding down power longer then normal does a hard reboot. If I remember right it happened to him as soon as he turn the on screen controls on in settings under PC connections.
whiteguypl said:
It was the same for my brother. Wouldn't start until he plugged into the PC. But he didn't know holding down power longer then normal does a hard reboot. If I remember right it happened to him as soon as he turn the on screen controls on in settings under PC connections.
Click to expand...
Click to collapse
I put mine down after sending a TM to my son. When I picked it back up. I had to hold do the hard reboot, which didn't work until I plugged it in (although I can't guarantee that plugging it in made the difference).
Related
I'm having a hard time turning my phone on while its charging. It is difficult otherwise, but impossible during charging. Am I the only one with this issue?
Sent from my PG86100 using XDA Premium App
I literally just experienced this, so frustrating. Especially with a case.
Sent from my PG86100 using XDA Premium App
Are you rooted and have clockwork? There are issues with it with power when off, not charging and could be result kept it.
I don't have clockwork, have the other one. Name escapes me currently.
Sent from my PG86100 using XDA Premium App
This is one of the reasons I am going for the SGS2. Most times I have to--have to--do a battery pull to get it to turn back on. Sometimes the SDcard too. Sometimes it doesn't even charge. Sometimes I charge it while on and wake up to a green light, phone locked hard off (requiring battery pull and sdcard pull), and when I boot it up (if I can) the battery is completely dead.
It's a major issue with the 3d. There have been a ton of threads. And BTW, it happens on rooted AND stock devices. My phone died last night. Took me 32 effin minutes to get it to come back on. One of the reasons I'm getting rid of it
sent from my DAMN 3D!!!
Success100 said:
It's a major issue with the 3d. There have been a ton of threads. And BTW, it happens on rooted AND stock devices. My phone died last night. Took me 32 effin minutes to get it to come back on. One of the reasons I'm getting rid of it
sent from my DAMN 3D!!!
Click to expand...
Click to collapse
2 days before release I stopped into my local Radioshack to play with the demo phone. I saw it turn on, we played with it. Powered off...and never came back on. One of my friends did that eventually too.
...can't say I'm not scared of that happening to me.
daneurysm said:
2 days before release I stopped into my local Radioshack to play with the demo phone. I saw it turn on, we played with it. Powered off...and never came back on. One of my friends did that eventually too.
...can't say I'm not scared of that happening to me.
Click to expand...
Click to collapse
I can believe it...
How the f this thing made it into production with this big of a software glitch Or whatever the he'll it is riddles me
Success100 said:
I can believe it...
How the f this thing made it into production with this big of a software glitch Or whatever the he'll it is riddles me
Click to expand...
Click to collapse
It's not a glitch. For some reason, HTC designed it that way. If the phone is off and rooted, but still connected to some sort of AC power or USB power, the phone is actually in recovery mode, however, the screen just appears black. You wouldn't even know it!! LOL.....but, if you pull the AC power or USB power from the phone, and wait like 5-10 seconds it will boot right up, no problem or issues.
Crazy, huh? It may be a bug with revolutionary root; I reported it to IMFDM or however you spell it and the above is what he told me.
If you noticed, before you were rooted, it wasn't a problem. Don't keep removing the case and pulling the battery, just wait a bit after you pull the plug, It will be good to. Trust me, I go through it regulary!!
Hope that explains it for you guys...and helps you out.
pinky059 said:
It's not a glitch. For some reason, HTC designed it that way. If the phone is off and rooted, but still connected to some sort of AC power or USB power, the phone is actually in recovery mode, however, the screen just appears black. You wouldn't even know it!! LOL.....but, if you pull the AC power or USB power from the phone, and wait like 5-10 seconds it will boot right up, no problem or issues.
Crazy, huh? It may be a bug with revolutionary root; I reported it to IMFDM or however you spell it and the above is what he told me.
If you noticed, before you were rooted, it wasn't a problem. Don't keep removing the case and pulling the battery, just wait a bit after you pull the plug, It will be good to. Trust me, I go through it regulary!!
Hope that explains it for you guys...and helps you out.
Click to expand...
Click to collapse
Actually I absolutely noticed this before rooting...but back then I barely ever powered off. Nothing to flash, no way to flash it. I'm pretty sure it was just the same except we had much much much less reason to power off and reboot.
daneurysm said:
Actually I absolutely noticed this before rooting...but back then I barely ever powered off. Nothing to flash, no way to flash it. I'm pretty sure it was just the same except we had much much much less reason to power off and reboot.
Click to expand...
Click to collapse
I never did. I could power it on no problem before rooting. Didn't flash anything (I like Sense, what can i say...)....anyways, I noticed it afterwards and maybe it is true what that guy at AlphaRev said, it is the way HTC designed it for some weird reason....
Not a big deal for me though, now that he told me that...
pinky059 said:
It's not a glitch. For some reason, HTC designed it that way. If the phone is off and rooted, but still connected to some sort of AC power or USB power, the phone is actually in recovery mode, however, the screen just appears black. You wouldn't even know it!! LOL.....but, if you pull the AC power or USB power from the phone, and wait like 5-10 seconds it will boot right up, no problem or issues.
Crazy, huh? It may be a bug with revolutionary root; I reported it to IMFDM or however you spell it and the above is what he told me.
If you noticed, before you were rooted, it wasn't a problem. Don't keep removing the case and pulling the battery, just wait a bit after you pull the plug, It will be good to. Trust me, I go through it regulary!!
Hope that explains it for you guys...and helps you out.
Click to expand...
Click to collapse
this happens to my coworker that has this phone, and she is NOT rooted. And the above method never worked for me. Ive done that a million times trying to get it back on. Thanks for the tip though..
This has happened to me as well several hundred times it seems! It also did it when the phone was new. We had gone away on vacation like the week after the 3D came out, my phone had died while we were out, I plugged it into the charger, went to power it back on a couple hours later, and NOTHING! Probably took me a good 20-25 minutes to finally get it to come back on, with me eventually pulling the battery. This was stock at the time.
My 2 biggest gripes with the 3D, signal/call quality, and the power on glitch...
So all seemed to be fine and dandy after the update, but I went to check something on my tablet and it wouldn't wake up. Pressing the power button, or even holding it didn't do anything; the screen was black. I held volume up and power and it vibrated, then I held it again and it vibrated again. The third time I did this, it finally booted up again.
Dunno what this means.
EDIT: Just happened again, although now I can't seem to get the thing back on. The screen is just off and vol. up + power only makes the thing vibrate after a few seconds. I simply left the prime on the lock screen and came back and it was stuck again.
Prime BT tether lockups
XHolyPuffX said:
So all seemed to be fine and dandy after the update, but I went to check something on my tablet and it wouldn't wake up. Pressing the power button, or even holding it didn't do anything; the screen was black. I held volume up and power and it vibrated, then I held it again and it vibrated again. The third time I did this, it finally booted up again.
Dunno what this means.
Click to expand...
Click to collapse
Mine does the exact same thing when I tether it to my Sensation with BT.
I'm still on 2.11.1 though
UPDATE
I just manually updated my pad to .13 this morning. It did NOT alleviate my problem but it didn't make it any worse. Unlike many other user who report the lockups when sleep now, mine still only occurs when I tether BT and it goes to sleep. On the upside, I've tested my wifi and do confirm an improvement ~20% increase in signal strength and quality.
According to dd-wrt on my router signal increased from about ~49% to 63%
and Wifi analyzer signal strength ~77-68dB to ~54-47dB. I have not tested GPS.
Apparently the build variance between pads are reflected by the variance in the effects of the update
nattylite said:
Mine does the exact same thing when I tether it to my Sensation with BT.
I'm still on 2.11.1 though
Click to expand...
Click to collapse
How do you get it back on? I can't seem to power it up now.
EDIT: Nevermind, I just held power and it turned back on after about 5-7 seconds. I think it might be a "Wifi off during sleep" issue..but idk.
XHolyPuffX said:
So all seemed to be fine and dandy after the update, but I went to check something on my tablet and it wouldn't wake up. Pressing the power button, or even holding it didn't do anything; the screen was black. I held volume up and power and it vibrated, then I held it again and it vibrated again. The third time I did this, it finally booted up again.
Dunno what this means.
EDIT: Just happened again, although now I can't seem to get the thing back on. The screen is just off and vol. up + power only makes the thing vibrate after a few seconds. I simply left the prime on the lock screen and came back and it was stuck again.
Click to expand...
Click to collapse
same thing is happening to me after the update. My prime never used to do that but something in the update screwed with it. is there anyway we can revert back?
Doubt this is an update issue as I haven't seen it yet or most others. Or they all would be posting about it. That is strange though. You all didn't root n go messing around with stuff did you? Lol. If anything I'd try a fresh reboot. Maybe even clear out all the caches. Something else is seeming to cause this. By any chance did you install chrome beta? Some users reporting strange things since installing it. I don't think its the app but it is strange though or coincidence.
demandarin said:
Doubt this is an update issue as I haven't seen it yet or most others. Or they all would be posting about it. That is strange though. You all didn't root n go messing around with stuff did you? Lol. If anything I'd try a fresh reboot. Maybe even clear out all the caches. Something else is seeming to cause this. By any chance did you install chrome beta? Some users reporting strange things since installing it. I don't think its the app but it is strange though or coincidence.
Click to expand...
Click to collapse
no I didn't root. I may factory reset if it keeps doing it and see if that works. I got a decent working prime and it would suck if this update is giving me problems. yes I did install chrome beta but this issue happened before I even installed it so that can't be it.
Ok, this has to do something with the update.
My perfectly fine from before prime wouldn't unlock. I couldn't get it to respond. (I thought it was dead..) I tried to unlock and pressed volume, did nothing.
I just read this thread and tried holding the power button and it vibrated and booted after the hold...
Asus needs to stop the patch roll out untill this is fixed...
Same problem for me. And after a short sleep, it wakes up, but there is a delay of about one half second that didn't used to be there.
-gary
After that one sleep, it has not yet repeated since last night for me
not only did mine do the same thing but it also killed my battery life while my Prime was sleeping... epic fail asus its time to return for a refund and never look back.
Maybe try reverting back and see if the problem goes away.
This hard-to-wake-up issue happened to me once after the update, but my Prime did finally wake up. Have not had the issue since. There was a lag in the wake up yesterday also, as others have mentioned, but even that seems to be gone now (or I'm just used to it).
Possible fixes for this situation:
1) Hard reset (stick an open small paper clip into the little hole just below the microSD) -- I'm sure most of you have tried this already...
And, if that doesn't work:
2) Hard reset, then reapply the .13 firmware update manually right after (assuming that is possible)
My tendency is to always do a hard reset just before any firmware updates -- makes me feel a little more confident. I was lazy and did not do that yesterday, but it won't happen again.
enough with this crap
Dude, you really gotta stop trolling, this is the third thread you are spewing this crap in in the last three I read.. You obviously are not returning it, you just like to *****.
PrimeTimeBro said:
not only did mine do the same thing but it also killed my battery life while my Prime was sleeping... epic fail asus its time to return for a refund and never look back.
Click to expand...
Click to collapse
unsure if this is the right thread, but mine's been acting up since the update as well. when i'm actively using it and turn off the screen, it boots up as quick as before to the unlock screen. however, after letting it sit for a few hours, it seems to have shut off where i'll have to hold the power button on for a few seconds (after 2 or 3 tries) to get it to boot up again as if i reset the tab.
Having the same issues with mine as well. I have installed Chrome Beta, but had it running for a few days pre-update without issue.
I almost always keep mine in the dock, but haven't had a chance to determine if it only happens in the dock or not.
i have seen this occur in the past ..before the update.. i thought the battery was dead but plugging in the charger didnt do much.. held the power+vol up 3 times finally woke up .. and said 36% battery left... i m on the verge of returning this after 2 weeks of use.. just cant get over these silly silly issues
Mine just did the same thing. I'm on the newest update. Had to hold power button 10+ seconds for it to come back.
Sent from my Transformer Prime TF201 using Tapatalk
Mine died over night with a charge of 36% in balanced mode. Had to hold the button down for 10 seconds to get it to turn on today after it was plugged in the charger for 20 minutes. Now when i wake it out of sleep there is a .5/1.5 second delay for the screen to come on.
Same issue
Had absolutely no issues with my tablet prior to this update - no random reboots, but now if it's off for a minute or more, I have to hold power in for 7-12 seconds to boot up the system.
Hey, just a thought.
Maybe also include the first few of your tablet's serial number to see if the problem is consistent with some batch(es) and not others? May help others that's going to update...
I'm completely at a loss here. I was running a 4.3 rom for the past week or two with no issues. Pulled my phone out of my pocket 30 min ago, hit the power button and the screen wouldn't light up. I tried it again and still no go. I tried swiping to unlock, even with the black screen and i felt it vibrate.
Ever since then my phone is non responsive. I can't get it to boot, can't hard reset it, nothing. The vibrates stop when I'm holding down power and down volume but that's about it. I timed the constant vibrates and they happen every 34 seconds according to the Win8 clock (which i've heard in inaccurate).
I'm gonna let the battery drain and hope that it will boot back up after it dies...but until then, any ideas?
Try plugging it into your computer and see what comes up. Which 4.3 ROM were you on?
Sent from my EVO using XDA Premium 4 mobile app
FinZ28 said:
Try plugging it into your computer and see what comes up. Which 4.3 ROM were you on?
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's the first thing I tried. I get nothing when i plug it into my comp. Nothing pops up in device manager. The comp doesn't detect it at all.
And I was running the 8/23 release of carbon 4.3 and I didn't have one problem with it until this happened :\
EDIT: The phone's battery finally ran out. It stopped vibrating and after a bit i plugged it in. After a few min it just starting doing it again.
I disassembled the phone and removed the battery for awhile hoping it would somehow help. Didn't do anything. It showed the flashing charge light (like when it's really low) for maybe a minute then it stop lighting up at all. Sometimes if i leave it unplugged for a bit and plug it back in it will flash the light again. That's about all I'm getting out of it now.
I'm thinking something failed internally. It happened while it was on and I was using it so there's no possibility that it was from a flash or anything like that.
Took my phone to the sprint store. The tech wasn't sure either but he thought it might be the screen that died. The vibrating could be the phone trying to boot then realizing there's no screen. They took it apart to check for moisture/damage and said I'm good to go for the $50 replacement.
So my new Evo will be here Tuesday.
BiNiaRiS said:
Took my phone to the sprint store. The tech wasn't sure either but he thought it might be the screen that died. The vibrating could be the phone trying to boot then realizing there's no screen. They took it apart to check for moisture/damage and said I'm good to go for the $50 replacement.
So my new Evo will be here Tuesday.
Click to expand...
Click to collapse
did you resolved it i'm having same had same issue as you mine is htc sensation but think is the same thing ive replacet the digitizer some day ago and it was working very good untill it start to vibrate and than died, now it flashes an orange light when i try to charge and after a while stops but i cant power it on nothing hapens when i press power button
Did you resolve the issue?
Did you ever resolve this issue? My Evo LTE started doing the exact same thing this evening and all of the Sprint stores are closed until tomorrow. I figure it's something internal that died and I can't see what it's trying to do... I guess you just got the replacement and didn't ever get it resolved with that particular phone?
BiNiaRiS said:
I'm completely at a loss here. I was running a 4.3 rom for the past week or two with no issues. Pulled my phone out of my pocket 30 min ago, hit the power button and the screen wouldn't light up. I tried it again and still no go. I tried swiping to unlock, even with the black screen and i felt it vibrate.
Ever since then my phone is non responsive. I can't get it to boot, can't hard reset it, nothing. The vibrates stop when I'm holding down power and down volume but that's about it. I timed the constant vibrates and they happen every 34 seconds according to the Win8 clock (which i've heard in inaccurate).
I'm gonna let the battery drain and hope that it will boot back up after it dies...but until then, any ideas?
Click to expand...
Click to collapse
I went to restart my TS and now it won't switch back on at all.... nothing happening and no response... I have left it on charge and it gets slightly warm but nothing happens?? Any ideas??
death_entry said:
I went to restart my TS and now it won't switch back on at all.... nothing happening and no response... I have left it on charge and it gets slightly warm but nothing happens?? Any ideas??
Click to expand...
Click to collapse
You tried holding the power button down for more than 2 seconds?
I don't think that will help. The watch arrives set in quickboot mode and it can crash in that mode and not restart right. Might be the problem here, or his display backlight might have failed. Or his power button might have failed.
Anyway, try a battery pull. A full restart after a real shutdown via battery pull will probably recover the watch to where you can go in and disable quickboot.
Instructions are in other threads.
Sent from my Nexus 5 using Tapatalk
Yeh I tried holding down every button etc for looong time... Today it's actually it's started working again clever tactics I tried....
Stop playing it with it for a day (Vital part this!)
Plug it into computer for 15mins
Hold power down.... it came on Woop
death_entry said:
Yeh I tried holding down every button etc for looong time... Today it's actually it's started working again clever tactics I tried....
Stop playing it with it for a day (Vital part this!)
Plug it into computer for 15mins
Hold power down.... it came on Woop
Click to expand...
Click to collapse
One thing that people need to be aware of--after doing a Cache and Dalvik wipe in TWRP Recovery--the phone can 'seem' like it's stuck in Boot mode--BUT, it's just taking it's time to re-align all the apps, software etc... and I mean at least 10 minutes of looking at a stationary Boot screen--it worried me first time.
Well, mines gone too. It was fully charged. I was listening to music, turned off the app, put watch on standby and when I went to check the time the thing won't turn back on. Tried connecting it to the charger but no response. I'm going to open it up and see if that works. I know I'll loose my warranty for this (doubt I have one as I got mine through Expansys.jp), If it doesn't work then I can confirm that swett, and not much of it will break your truesmart.
So one day my phone decides to not turn on. No clue what happens, pull it off the charger, then nothing. I try to flash stock hoping that would help but it would go into download mode or even acknowledge the fact that it's plugged in. After repetitively removing and putting back in the battery then plugging it in to get into download mode, I finally do it. I think the very first time I flashed to stock it just turned off halfway through. I kept flashing stock a bunch until it finally worked. I boot up, but it won't complete a full boot. I flashed stock again and here I am. It is perfectly capable of making a full boot, but tapping it with a medium amount of force immediately shuts off the phone. I checked and cleaned the battery contacts- nothing. But that was the only cause I could think of. I've tried other batteries and it's the same. I don't know what to do. I don't know why it's doing this. Any ideas? What can I do to fix it?
maybe a wire or some thing to do with you're power button has came loose.
Sent from my Half Baked Vibrant
dzee206 said:
maybe a wire or some thing to do with you're power button has came loose.
Sent from my Half Baked Vibrant
Click to expand...
Click to collapse
Power button? Why would losing connection to the power button make it turn off?
LiquidPlatinum said:
Power button? Why would losing connection to the power button make it turn off?
Click to expand...
Click to collapse
that actually happened to me a few years ago with my webos device.i'm just guessing what could be wrong, some thing had to have come loose or gone faulty...
dzee206 said:
that actually happened to me a few years ago with my webos device.i'm just guessing what could be wrong, some thing had to have come loose or gone faulty...
Click to expand...
Click to collapse
How would I check for that? I've taken it apart many times. I took it apart recently as well, and everything seemed fine
I would check to make sure everything is plugged in securely and if possible adb logcat while tapping the screen to see what the out put of the log. it may take a while to pin point the problem but honestly I don't remember how I fixed that issue its been so long I forgot.
Sent from my Half Baked Vibrant
dzee206 said:
I would check to make sure everything is plugged in securely and if possible adb logcat while tapping the screen to see what the out put of the log. it may take a while to pin point the problem but honestly I don't remember how I fixed that issue its been so long I forgot.
Sent from my Half Baked Vibrant
Click to expand...
Click to collapse
Will do. I'll let you know what I find