I have a BB WiFi Flyer, and just the other day I installed the latest Flyhoney ROM using the new easy HC install method. This was a first time effort and as far as I can tell, most everything is working well, except that the screen never turns off no matter what setting I have for Screen Timeout.
Coming from virgin GB, I wiped cache and data before flashing Flyhoney, as seems to be recommended.
I am not certain, but I believe that this screen timeout issue is new since flashing the Patches to remove the SIM Card Missing message and the Battery % patch. I did both at the same time, so not entirely sure if it is a ROM issue, a Patch issue or is there possibly an app that I have that is preventing the screen from turning off. I don't have any apps installed that weren't previously installed on GB, so I am assuming this is a ROM issue.
Has anyone one else experienced this issue since moving to HC and specifically the FlyHoney ROM?
Is your charging cable plugged in?
Sent from my HTC Flyer P510e using Tapatalk
Nope. Doesn't seem to matter if the charging cable is plugged in or not. The screen doesn't turn off on battery or on power.
What's worse, a calendar event will trigger the screen to wake, then it never goes back out without manual intervention, effectively killing the battery double time.
same here
looks like no way to fix it
Well, this is really strange. Suddenly the problem seems to have gone away for now.
The only thing I have done differently today than any other day since I installed FlyHoney was to put the tablet into Airplane mode for most of the day today.
I usually work from home, but today I went into my company's office, and since there is no WiFi there, I decided to put the tablet into Airplane mode as a convenient way of killing all radios and syncing attempts. Figured I'd preserve battery better.
Well, I just got home, turned Airplane mode off, now the damn thing is turning the screen off as it should have been according the the screen timeout setting all along. I've tried a couple different settings (30s and 2 min), and both work perfectly.
I just took it off the charger this morning. Didn't turn it off or reboot it or anything like that. Just Airplane mode.
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 This happened about a month ago.. Ironically same night of the week (Saturday night) So I got lucky i didn't have work the next morning so my Alarm didn't need to go off.
I was originally HTC Unlocked, Now I am S-OFF. The first time this happened is when I was HTC Unlocked, the 2nd time, S-OFF.
Phone was not turned off. Phone was at good battery life (~90%). I hit the power button, screen would not turn on. I plug it into charge, light does not come on. I have to hold down the Volume Down+Power for a while, then eventually it resets itself.
Now, I do not think this is ROM or Baseband+Radio Specific because I'm on completetly different ROM/Baseband then I was earlier. And also, this is the 2nd time it happened since I had the phone.
I'm running 1.05.11.0606 Baseband, 2.45_003 PRI, MeanRom ICS. However... I'm almost certain it's not a ROM specific issue because I was running a totally different one.
It *COULD* be an app. However I am very picky and make sure almost nothing is running in the background of my phone (just the internet browser).
Does anyone have any idea why my phone would go into this sort of... "Deep Sleep" in the middle of the night, and not wake out of it? Where it's happened only on a Saturday Night so far. There is also NO way I can think of replicating it. If I install Logcat, Will I even be able to monitor something like this?
Edit: I must note, both times it was NOT plugged in charging. Usually I have my phone charging overnight. I'm going to start charging my phone before going to sleep to keep it unplugged while sleeping to see what happens
Thanks..
Mark
Bump...
So I was at work today and was using my phone with no problem, Came back to it when I was leaving, hit the power button to turn on the screen and nothing...
Needed to hold the power + volume down button for about 20 seconds for it to boot up again.
I can't seem to narrow it down if it's a hardware, software, or kernel issue. It seems like it's hard locking up while sleeping (can't charge it at this point either). I am going to do a full wipe, reinstall apps one more time, and see what happens.
What Rom are you running?
Sent from my HTC Evo LTE
This sounds like a hardware panic, that would need specific diagnostics run, in order to identify potential root-cause issues. That might mean taking your battery out and hooking it up to a tester, etc.
Sent From My S-OFFed, R00ted, 100% Tricked-Out HTC Evo 4G LTE via XDA Premium!
Bump...
So I was at work today and was using my phone with no problem, Came back to it when I was leaving, hit the power button to turn on the screen and nothing...
Needed to hold the power + volume down button for about 20 seconds for it to boot up again.
I can't seem to narrow it down if it's a hardware, software, or kernel issue. It seems like it's hard locking up while sleeping (can't charge it at this point either). I am going to do a full wipe, reinstall apps one more time, and see what happens.
Click to expand...
Click to collapse
After it happened and you rebooted the phone, you need to get last_kmsg and send it to developer of the rom you are on. He might be able to figure out the problem.
Sent from my lair.
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.
I have two V60s on A11 and noticed for the past two nights one of them will reboot while charging. Only way I notice is because I have to use my PIN in morning to login in instead of fingerprint and one app indicates a restart. This is a replacement V60 that I have had for two days.
Any thoughts?
Are you sure that it's a reboot? I noticed that if I leave my phone idle for a couple of hours (not sure how many, maybe 4 or more?), some kind of security kicks in requiring that I enter my pattern instead of using the fingerprint reader. Pretty sure this has happened both on Android 10 and Android 11. I don't commonly leave my phone idle for 4+ hours during the day, but it has happened just enough for me to notice it. And it definitely wasn't a case of the phone just randomly rebooting itself on me in the middle of the day. THAT, I would have noticed.
Positive it is a reboot. I actually saw it happen this morning. Phone will just shut off and T-Mobile reboot splash screen comes on. I think it is not related to fingerprint reader bug as I have disabled the fingerprint reader on my lock screen/AOD.
Actually been noticing it happens now even when the phone is not charging. I wish there was a way to see which app is causing the problem or get some kind of log to know what is going on.
Hmmm, other than trying to isolate which app is causing the problem, I'd probably suggest a factory reset.
I actually removed all apps and left with factory defaults and it still rebooted during a charge. I have sent the phone back and awaiting a replacement. (This one was the 2nd year promise replacement for a dying G8)
I had to ship the phone back and get a replacement. Everything I tried did not work to stop reboot while charging.
My LG started to freeze, then reboot several times a day, while in use as well as overnight. Sometimes boot loops directly after the logo, so not OS or app related, also without SIM or SD. I had the battery changed (still in warranty), but that behavior continued. So I got a replacement phone yesterday, since it was obviously a hardware issue (I guess it is a RAM failure).
It just stopped turning on and everytime I tried, I got a toast that said to try again after reattaching the dual screen. This only temporarily fixed it and after a few times of reattaching it the phone doesn't even recognize the case anymore.
The magnetic charging still works.
Anybody encounter this or know how to fix?
Something else. I've had massive battery drain since my dual screen stopped working. At a rate of 6-7% an hour without usage. I have to recharge it twice a day once in the morning and once at night to keep it from dying on me (again without even using the phone). The battery usage only shows system as using battery.
Things I've tried.
1. Rebooting
2. Factory reset (retore with drive)
3. Factory reset (setting up from scratch)
4. Deleting LG message and installing textra. Deleting LG contacts and installing google contacts. Installing and using Google phone as default over LG.
None of these has worked. I'm wondering if it was due to the latest T-mobile update which i took a couple of weeks ago and only noticed it later.
Anybody on T-mobile having battery problem? Any suggestions?
I've had this too. Only thing I haven't tried is a hard reset (vol down + power button) but not sure if will work or not. It's annoying.
Have tried a a hard reset and it‘s still happening. I think mine is a loose connection somewhere. It will stay on and play a movie all the way through if it’s left on the table but if I’m holding the phone while using it it will turn off. No idea if it’s fixable though?
Danjen22 said:
Have tried a a hard reset and it‘s still happening. I think mine is a loose connection somewhere. It will stay on and play a movie all the way through if it’s left on the table but if I’m holding the phone while using it it will turn off. No idea if it’s fixable though?
Click to expand...
Click to collapse
So your problem didn't start after taking the latest T-mobile update then? Turning off while holding sounds bad i hope you can get it figured out.
Now I'm convinced mine had something to do with the dual screen case. It started right after my dual screen case stopped working. I'm guessing it loosened the usb connector or maybe something from the magnet charging adapter itself.
Airtioteclint said:
So your problem didn't start after taking the latest T-mobile update then? Turning off while holding sounds bad i hope you can get it figured out.
Now I'm convinced mine had something to do with the dual screen case. It started right after my dual screen case stopped working. I'm guessing it loosened the usb connector or maybe something from the magnet charging adapter itself.
Click to expand...
Click to collapse
I'm in the UK. My problems started after I upgraded to android 10. It worked flawlessly up until then. I then updated to android 11 hoping that might solve the problem but it didn't. I'm now thinking it's a fault with the screen after it played the whole of the eternals film without turning off as it was sat on the table and not touched. As soon as I try and do something with it while holding it, it turns off, but there's no specific time limit. Sometimes it's on for 20 minutes before it turns off, sometimes it's 20 seconds.