Related
After my battery got really low, Power Saver mode turned in. I have it set to go on at 15% . Normally the settings return to normal once plugged back into a charger or the battery level goes back up. This last time I let the battery get down to 5% (I know..) . You know how when it gets that low, it will dim the screen really fast and disable tactile feedback? Well the thing is, it nwver reset itself. I even changed the power settinf and reboot the phone. I had to go into the screen and touch settings to reset them manually.
Anyone know why the settings did not return to normal?
I had the same thing happen. I don't know why it didn't reset. I had to change everything back manually too... I forgot my extra battery on Christmas...
Sent from my HTC Rezound
If anyone else gets this, please post here. If it happens again, I'd be interested to know if there is a fix...thanks.
I also just noticed background data got disabled. Market would not load . I had to manually turn that back on.
happened to me as well. the haptic feedback was disabled when my phone shut itself down. when i charged it back up, it didnt reset the settings to normal.
Same here... happened this morning... could it be due to the unlock?
Sent from my ADR6425LVW using Tapatalk
Yep, that sucks. Same thing happens here. Unlocked bootloader, though I doubt that is the reason.
Sent from my ADR6425LVW using Tapatalk
I have the same issue.
Unlocked bootloader with amon recovery and CleanRom 1.2
When economy mode kicks in due to low battery level, certain settings are not restored upon charge, namely the background data, though I found it was set to CDMA only with LTE disabled as well.
When I tried a Sense3.5 rom on my incredible it did the same thing, so I think this is an issue with Sense, not just the Rezound.
I think we need to start opening tickets with Verizon/HTC for them to address their issue.
fully stock over here, same issue!
I too am experiencing this issue, currently using cleanrom 2.2 sp1
Also have this issue. Stock everything.
yup, stock, same issue.
disabled 'power saver mode' so it never happens again.
Had it happen again. Batt was at 8% when I plugged in. Stock ROM ,no unlock performed. Anyone with a different version of Sense get this issue?
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...
Hey guys,
Last night I plugged in my LGOG right before I went to sleep. About seven hours later I woke up, woke it up to check the time, then fell back to sleep. When I woke up again a few hours later, my phone was completely dead. No lights go on when charging, nor does it go into the charging mode that happens when the phone is off but charging. The power button does nothing at all. Connecting it to a computer does nothing. I have tried two different wall chargers and a USB plug, and have tried different outlets. The phone is rooted and unlocked. I haven't put any new apps or anything on the phone recently, however I have had a slight overheating issue lately. I don't think that that's what caused the issue though, as when I woke up for the first time and woke it up, the phone was not noticeably hot, and seemed to work fine. Any ideas or suggestions?
Edit: As suddenly as it stopped working, it has started working again, about two hours later. The notification sound buzzed, my phone turned on, and usual on start things happened. However I'm still extremely worried about it. Now that it's on, I assume there's more I can do to figure out the issue- suggestions?
These phones are terribly buggy when charging/when they die, IMO. Worst Android device I've ever had in that respect.
Probably just a fluke, tbh.
Unfortunately it happened again- sent a message, put my phone away, when I tried to turn it on again nothing happened and it stopped working for five minutes.
Apologies for not mentioning this before, but I am using carbonrom, not stock. I've used it for several months with no issues, and have used the latest build for a week or two now without this issue.
miller150 said:
Unfortunately it happened again- sent a message, put my phone away, when I tried to turn it on again nothing happened and it stopped working for five minutes.
Apologies for not mentioning this before, but I am using carbonrom, not stock. I've used it for several months with no issues, and have used the latest build for a week or two now without this issue.
Click to expand...
Click to collapse
Reboot into recovery and wipe cache+dalvik
Maybe the rom needs a little cleaning
Sent from my CM10.2 OGE973
Tried wiping cache and dalvik, but didn't seem to solve the issue. Then my phone started having an issue it's had once before- it turns on for a few seconds, then the screen goes grey for about a minute, then returns to being on. After returning to being on, it acts like it's just started up- ie, there's superuser grant notifications, cpu set notifications, and all sorts of other stuff I usually see on boot. It essentially rendered my phone unusable, so I restored an earlier backup. This seems to have resolved it for now, I may have to wait before updating carbon again.
miller150 said:
Tried wiping cache and dalvik, but didn't seem to solve the issue. Then my phone started having an issue it's had once before- it turns on for a few seconds, then the screen goes grey for about a minute, then returns to being on. After returning to being on, it acts like it's just started up- ie, there's superuser grant notifications, cpu set notifications, and all sorts of other stuff I usually see on boot. It essentially rendered my phone unusable, so I restored an earlier backup. This seems to have resolved it for now, I may have to wait before updating carbon again.
Click to expand...
Click to collapse
Either you have a bad phone (possible, LG seems to have some QC issues based on some of the crazy reports Ive heard fm other people on this forum [Mine's fine]), or it's all the startup **** that you have going.
Do you usually let it discharge to below 5%?
that's a stupid idea with any device, and seems to be especially damaging to our LGOG.
OMGMatrix said:
Either you have a bad phone (possible, LG seems to have some QC issues based on some of the crazy reports Ive heard fm other people on this forum [Mine's fine]), or it's all the startup **** that you have going.
Do you usually let it discharge to below 5%?
that's a stupid idea with any device, and seems to be especially damaging to our LGOG.
Click to expand...
Click to collapse
Have mine 2months been careful not to let the battery shut down on its own but thirds past Monday my car charger weren't bad and the phone shut down. Would not except a charge after that. Went to att and they sent me to a service center. They could not charge it either. They replaced it, now making sure my external battery backup its always charged. Do not want to do that again.
Sent from my LG-E970 using xda app-developers app
That sounds like that could actually be the issue. On the previous iteration of carbon I almost never allowed it to go below about 10%. However the new update seemed to be harsher on battery life and it slipped into the 1% range several times...
same thing happened to me running root box with no tweaks or anything. I woke up and the phone was off, been that way for two days now. it wasn't on the charger so its definitely possible that it died. I actually found this thread because I could've sworn there was a report of someone who had to do a battery pull. I'm thinking that's my only option now.
Hi XDA, wondering if anyone can help me out with an annoying problem.
I have a Galaxy Note Edge. Within about 8 months I've been experiencing random shut-downs.
Thinking it was battery related, I started there. The problem persisted. Thinking it was perhaps a wake-lock issue, I did a factory reset including cache clear, still have the problem.
Basically when I'm using the device it will randomly shut down. I could be checking my email or taking a pic, out of nowhere poof, off it goes. Battery will still say an arbitrary amount, today it was at 64%. But when I plugged it in, with the device off it said 0%.
I notice this happens often. If I charge my phone overnight it will stop charging at maybe 70%. Poor/wrong calibration?
Here's the thing though, even if the phone says 0% after shutting down, if I try to turn it on it will go into a boot loop for..well infinitely. Hours. So there's clearly still power. If I try to use my battery bank to charge it, it still won't get past the boot loop until I connect it to at least a 2.1amp charger.
I'm at a loss. There doesn't seem to be any obvious hardware issues. I've been scraping the interwebs for a good year but nothing has helped and I just live with it.
Running Android 5.1.1, stock, no dumb unoptimized apps. Someone please save my sanity? Cheers! E>
I have a new v30 on verizon and the phone keeps powering off at random times. I'll set the phone down, and a minute later go to pick it up and I have to power it back on. It happens even at 100% battery, but it happens even more often when battery is below 40%. Since it shuts off even when the battery is full, I *highly* doubt this is a battery problem.
Some random articles say factory reset works but It's a pain in the ass to restore 15+ 2FA accounts into google authenticator. I did it once when I got this phone and I don't want to do it again.
Thoughts? suggestions?
I would say just go back and get it exchanged for another one.