After Oreo update AOD stopped working - Samsung Galaxy S8 Questions and Answers

How do I fix this? After updating to Oreo yesterday. My AOD stopped working. I have to restart my phone to make it work and after a few hours it will stop displaying in the screen again.
Anyone experiencing the same issue?
Any workaround for this?
Sent from my SM-G950F using Tapatalk

anyone experiencing the same issue?

I had the same issue. I shutdown and restarted the phone and AOD started displaying so far.

I have the same issue. Have not found a solution anywhere yet.
If I restart AOD works for some time(1-2hrs) and stops working again. Very weird

Just wanted to clarify this with you guys, does AOD consume more batt then switch it off? Sorry if this is a stupid question.

It's so irritating that I have to restart my phone everytime AOD stops displaying. I'm a busy person and I find AOD a very useful feature, i dont have to touch my phone to check the time and notifications.
I will do a factory reset later. I will let you know if the problem still exist.
Sent from my SM-G950F using Tapatalk

My AOD worked all day after I did a shutdown and restart. However overnight it seemed to stop working, when I woke up this morning it was not working. I rebooted and it did not resume. I shutdown and restarted, it did not seem to work right away but after about thirty minutes is started working again.

i have done factory reset and so fat it is working, no issues.. I guess i'll give it a week and see if it will still have issues.

Just found out the cause of this issue.
AOD stops working after I take screenshots using bixby button. (Yep, I remapped my bixby to take a screenshot via bxActions)
Sad I have to disable it. Actually just the single press, i still use the long press as flashlight and AOD seems to be working fine.
Sent from my SM-G950F using Tapatalk

I had the same issue. A reboot fixed it though.

A word to the wise ...
funkybone said:
Just found out the cause of this issue.
AOD stops working after I take screenshots using bixby button. (Yep, I remapped my bixby to take a screenshot via bxActions)
Sad I have to disable it. Actually just the single press, i still use the long press as flashlight and AOD seems to be working fine.
Sent from my SM-G950F using Tapatalk
Click to expand...
Click to collapse
It is always a good idea to do a factory reset after you either do a major OS update (like Nougat to Oreo) or switch carriers to take care of any funky issues like this. It may help you out on this. Just paying it forward.
Cindy

cindylike24 said:
It is always a good idea to do a factory reset after you either do a major OS update (like Nougat to Oreo) or switch carriers to take care of any funky issues like this. It may help you out on this. Just paying it forward.
Cindy
Click to expand...
Click to collapse
Yes I just realzed that. Did a factory reset and my device works like charm. [emoji1303]
Sent from my SM-G950F using Tapatalk

funkybone said:
Yes I just realzed that. Did a factory reset and my device works like charm. [emoji1303]
Click to expand...
Click to collapse
Well that's great!
Cindy

Same problems with my J5 2017 + AOD Installed separately
So yeah, after installing the oreo update I got yesterday, the AOD stopped working. And yeah, the AOD did not come with my j5, but I wanted it so badly. Now, the only worry is that it doesn't work and cannot install the latest version of that. Please help ?

AOD Problem after update
So i found that my AOD isn't showing after the Oreo Update, so i kept on searching for the cause in my Settings and gladly i found the solution.
Go to your Settings- Lock Screen- AOD Settings - Display Mode, switch to Show always.
It was set on "Tap Display " which requires you to tap your screen then shows for 30 seconds, after the update.
Try it! Hoping that this would help some
-Rey

Related

Experiencing Major Reboot Issues

Let me preface this by saying this is my experience. I am passing this off to see if others are experiencing the same thing. I am not dissing this phone because I really like it.
I have seen more than 10 random reboots with this phone. The crazy part is when the phone reboots, I lose settings.... Like a lot of them. I recently experienced and my notification bar started malfunctioning where the settings would not pull up and I could not long press panels. I finally had to factory reset my phone.... After that, it rebooted again this morning while I was listening to the radio.
At this point I am going to have start a log to try to correlate where the problem might be.
This is very concerning. I have never experienced anything like this even with custom Roms.
Please let me know if anyone else is experiencing this.
Sent from my SM-G935T using Tapatalk
I've read that other people are experiencing this too. Hopefully mine doesn't come like this. I would recommend returning it and getting a new one. This is ridiculous that this is happening
Try removing all apps you installed and see if you cant pin it down to an app but if all said and done and phone is stock meaning you installed no additional apps and still see it happen then to me sounds like a Hardware problem and you should return it for a replacement.
anrchy666 said:
Try removing all apps you installed and see if you cant pin it down to an app but if all said and done and phone is stock meaning you installed no additional apps and still see it happen then to me sounds like a Hardware problem and you should return it for a replacement.
Click to expand...
Click to collapse
Unfortunately, I think you are right.
Sent from my SM-G935T using Tapatalk
I'm having the exact same issues. Once or twice a day, usually in USA Today or IHeartRadio, it reboots. Once I experienced that loss of settings also and had to factory reset. I'm going to return the phone.
Try wiping the cache partition
Sent from my SM-N920T using Tapatalk
rocolema said:
I'm having the exact same issues. Once or twice a day, usually in USA Today or IHeartRadio, it reboots. Once I experienced that loss of settings also and had to factory reset. I'm going to return the phone.
Click to expand...
Click to collapse
I also experienced this in iHeartRadio... Do you use bluetooth?
Sent from my SM-G935T using Tapatalk
[email protected] said:
Try wiping the cache partition
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Is there a way to do this on a non-rooted phone?
Sent from my SM-G935T using Tapatalk
Go into recovery mode with phone completely off .volume down+home button+power button.If that doesn't work factory reset and if that doesn't work return the phone or if possible reflash stock firmware through ODIN.
Sent from my SM-N920T using Tapatalk
Yes, I use bluetooth to listen to IHeartRadio. I tried clearing the cache thru recovery. It did not work.
rocolema said:
Yes, I use bluetooth to listen to IHeartRadio. I tried clearing the cache thru recovery. It did not work.
Click to expand...
Click to collapse
I have been watching watchespn for about an hour with my bluetooth headphones... No problem. I need to test iHeartRadio some more. With that said, I think there is a deeper issue here just because I've never seen settings get changed like that.
Sent from my SM-G935T using Tapatalk
My Bluetooth streaming was janky got this notification and restarted the phone. Problem gone. Dunno the relevance but this was a system notification
Just switched back to iHeartRadio on bluetooth, I was coming here to read a reply so I clicked the home button and rebooted.
Sent from my SM-G935T using Tapatalk
The beta version (6.0.0) of the IHeartRadio app seems to have fixed my reboot problem (which was happening on both bluetooth and earphone modes).
Update, it is still rebooting, even using the beta.
First reboot of the day. IHeartRadio and Bluetooth. I am already running 6.0.0 of the app.
Sent from my SM-G935T using Tapatalk
(note that I don't typically do iHeartRadio and Bluetooth on the weekends.)
Sent from my SM-G935T using Tapatalk
My experience was different. I didn't have any random reboot but I did get the phone just hang.
Before my Springbreak trip I was testing out a sport camera and downloaded an app that could remotely control the camera. Everything seemed to be working smoothly during the test. Then when I was done, I shut down the camera, turned off the phone and started packing up.
Then I needed to use the phone, so I turned it on.. it's turned on but I couldn't do anything, the screen was unresponsive.. I couldn't swipe or press anything... I attempted to reboot it... the power button still worked... the reboot menu came on but I couldn't press anything... I still could turn the screen on and off and brought up the reboot menu.. but jsut couldn't do anything with it..
Only one option was available which is to force it reboot by holding Power and Down volumne.
That was weird, especially on a brand new device.
I've seen it reboot a few times, and it is especially annoying when you are trying to show your device off and it reboots...in front of people...randomly. I am not sure if I want to return it just yet because it is a Touchwiz/android bug that I have experienced on other devices as well. It MAY be an app issue but I can't pinpoint it yet.
I was trying to launch my DJI Phantom app and it just hung/restarted - got stuck on tmobile screen and it wouldn't let me do a hard-reset! Had to wait a few mins and it recycled.
vnguyen972 said:
My experience was different. I didn't have any random reboot but I did get the phone just hang.
Before my Springbreak trip I was testing out a sport camera and downloaded an app that could remotely control the camera. Everything seemed to be working smoothly during the test. Then when I was done, I shut down the camera, turned off the phone and started packing up.
Then I needed to use the phone, so I turned it on.. it's turned on but I couldn't do anything, the screen was unresponsive.. I couldn't swipe or press anything... I attempted to reboot it... the power button still worked... the reboot menu came on but I couldn't press anything... I still could turn the screen on and off and brought up the reboot menu.. but jsut couldn't do anything with it..
Only one option was available which is to force it reboot by holding Power and Down volumne.
That was weird, especially on a brand new device.
Click to expand...
Click to collapse
This is exactly what happened to mine, I was going to return it and put it on the charger and it rebooted. Knock on wood, No problems since. I'm going to keep a close eye on this in case I need to exchange.
Yes, same here. Bluetooth headset with iHeartRadio makes the phone reboot and lose some settings. Maybe a bug with iHeartRadio and 6.0.1.

Nexus 4 screen freezes randomly, no reaction when touching.

Hi everyone!
So I just had this problem after I woke up yesterday. I googled a lot but only found similiar problems.
Let me tell you what happened chronologically:
After turning the phone on in the morning it started updating apps as if I was doing a firmware update: "updating apps 1 of 135" etc. Note that my nexus was already running on 5.1.1 and had the latest updates installed.
Now it randomly freezes the screen on whatever screen it was before it happens and it won't respond to any touch input. This can also happen when not using the phone, then it will freeze at the lockscreen (the time freezes with it so sometimes i can see at what time it froze). Also, it loses connection with Wi-Fi as i'm using Whatsapp Desktop when i'm on my laptop and it mentions me that my phone is not connected.
The only thing that "fixes" (temporarily) it is a reboot. Now sometimes, on the lockscreen, i can just hold the power button and the pop-up comes in to turn the phone of, which i can somehow just tap on an it responds by turning the phone off. But sometimes (less frequent than the latter mentioned) the pop-up doesn't come in and holding the power button for a few secs will do the trick.
I hope I informed you all enough and my end question is: does any of you know what this is? How i can fix it or what i can do to prevent it or anything as I am hopeless. (my G3 is up for reparation so this is my sisters old phone, i had a nexus 4 myself for 2 years before the G3).
Thanks in advance!!
The best way to test it is by reformat the OS.
I positively think that it will solve the problem.
Since the phone is no longer under warranty, I guess there is no harm to install custom rom on it. They are fast and stable too.
Hope this help. Good luck.
Sent from my Nexus 4
EXACT thing happened to me too. Backup your data and hard reset from recovery. This fixed it for me
Same problem here bro, but neither custom roms or factory reset helps.... Is there anyone who has successfully solved the problem ?
multimedias said:
Same problem here bro, but neither custom roms or factory reset helps.... Is there anyone who has successfully solved the problem ?
Click to expand...
Click to collapse
Then it's time to change the screen or phone. Looks like it is a hardware issue.
Nitin
nitin.chobhe said:
Then it's time to change the screen ...
Nitin
Click to expand...
Click to collapse
I agree, your screen needs to be replaced.

Screen keeps turning on during a call??

Guys I'm on the latest Nougat update on AT&T with the March update and the most annoying thing started happening out of nowhere... Wondering if y'all have ever seen this and have been able to stop?
Basically, during a call, my screen turns off after my screen timeout time, and within 5 seconds, the screen turns back on and keeps repeating ?...!
Here's what I've tried:
1. Calibrated and tested the proximity sensor.
2. Double checked with or without Smart Awake setting.
3. Cleared data of the in call UI app.
4. Rebooted.
5. Wiped OS Cache.
6. You tell me? ?
Thanks for all the help!
It's a Bug with the In-Call UI
My T-Mobile Galaxy S7 Edge has been experiencing the same issue. I tried everything including a factory reset to no avail. I believe it may have something to do with the In-Call UI system app associated with the Phone App. It only started happening after the 7.0 update and really makes using the phone to make a phone call unnecessarily frustrating. I am guessing more people have this but don't realize it because the screen will turn off if you navigate away from the In-Call UI to another app or to the home screen. It is a bug though and I hope Samsung deals with it in the next update.
Trevozneoma said:
My T-Mobile Galaxy S7 Edge has been experiencing the same issue. I tried everything including a factory reset to no avail. I believe it may have something to do with the In-Call UI system app associated with the Phone App. It only started happening after the 7.0 update and really makes using the phone to make a phone call unnecessarily frustrating. I am guessing more people have this but don't realize it because the screen will turn off if you navigate away from the In-Call UI to another app or to the home screen. It is a bug though and I hope Samsung deals with it in the next update.
Click to expand...
Click to collapse
Thank you so much for responding. Makes me feel better that I'm not crazy! ?
Can others test and confirm for us so we can maybe document and report to Samsung for a fix?
BTW for what it's worth, as a workaround, you can hit the home button to put the in call UI out of focus and then let the phone sleep, it stops the waking up. Down side of course, no proximity action and the nuisance of turning on, then bringing up UI to mute and unmute, very annoying on meetings for work! :crying:
Any others please test and report for us? Thanks you!
Trevozneoma said:
My T-Mobile Galaxy S7 Edge has been experiencing the same issue. I tried everything including a factory reset to no avail. I believe it may have something to do with the In-Call UI system app associated with the Phone App. It only started happening after the 7.0 update and really makes using the phone to make a phone call unnecessarily frustrating. I am guessing more people have this but don't realize it because the screen will turn off if you navigate away from the In-Call UI to another app or to the home screen. It is a bug though and I hope Samsung deals with it in the next update.
Click to expand...
Click to collapse
Reread, you already mentioned the workaround, sorry and thanks!
Now I am not sure if this will work for you but I've noticed that if I occasionally use the slide up gesture to launch Samsung pay (i.e. from the lock screen or home screen) and I back out of it, it keeps the problem at bay temporarily. I tried deactivating the slide up to activate feature of Samsung Pay and it didn't fix the issue. For now, this is my temporary work around. I hope it works for you too!
Trevozneoma said:
Now I am not sure if this will work for you but I've noticed that if I occasionally use the slide up gesture to launch Samsung pay (i.e. from the lock screen or home screen) and I back out of it, it keeps the problem at bay temporarily. I tried deactivating the slide up to activate feature of Samsung Pay and it didn't fix the issue. For now, this is my temporary work around. I hope it works for you too!
Click to expand...
Click to collapse
Extremely good observation and another workaround bud! You're right, it provides some relief with the Samsung Pay workaround. I can't believe we haven't heard more noise on this from others, we can't be the only two OCDs here !?
Thank you again and request to others to join us test and slay this problem, if possible!
Trevozneoma said:
Now I am not sure if this will work for you but I've noticed that if I occasionally use the slide up gesture to launch Samsung pay (i.e. from the lock screen or home screen) and I back out of it, it keeps the problem at bay temporarily. I tried deactivating the slide up to activate feature of Samsung Pay and it didn't fix the issue. For now, this is my temporary work around. I hope it works for you too!
Click to expand...
Click to collapse
@Trevozneoma - To build on your observation with Samsung Pay, I went into settings and have unchecked the option for using it via screen off. The lock screen and home screen are still checked, and this seems to have fixed my issue. It's not perfect, as I like to use the feature when using Samsung Pay, however, I will take this, over the battery drain and annoying nature of the screen on on the incall UI screen!
Thanks for your help!
@ProFragger we probably notice it because we use our phones...as phones haha. I will give the Samsung Pay work around a try. Thanks for the recommendation!
Trevozneoma said:
@ProFragger we probably notice it because we use our phones...as phones haha. I will give the Samsung Pay work around a try. Thanks for the recommendation!
Click to expand...
Click to collapse
Haha true that, brother. Please respond back with your changes and results so we can confirm a workaround solution for this . Thanks for partnering and responding with me, I am sure this thread will help others .
Hi Guys!
I too have this issue and I have a Samsung S7 Edge on Sprint.
As it was stated, this all started after the last update.
As I primarily use a BT headset with my calls, I have simply been hitting the Home Button and the phone will stay in the time out mode.
Just jumping on this band wagon in hopes that this issue will be resolved quickly!!
Thanks!!
Crystal Dragon said:
Hi Guys!
I too have this issue and I have a Samsung S7 Edge on Sprint.
As it was stated, this all started after the last update.
As I primarily use a BT headset with my calls, I have simply been hitting the Home Button and the phone will stay in the time out mode.
Just jumping on this band wagon in hopes that this issue will be resolved quickly!!
Thanks!!
Click to expand...
Click to collapse
Thanks for your report, bud... We need more of these to gain some momentum around this issue... Does the workaround for you?
The work around works, but it is just a PITA to have to keep hitting the home screen to put the call screen out of focus.
I really hope that Samsung will address this issue and fix it!!
Happens here also. Thanks for the workaround.
Sent from my SAMSUNG-SM-G935A using Tapatalk
I hate this so much. It happens while I am on the phone and it happens when an appointment reminder pops up and then the screen goes black and then turns on, over and over. THIS ONLY STARTED HAPPENING AFTER I UPDATED FROM Marshmallow to Nougat.
Here is the FIX... Guessing anyone that has the issue has Samsung Pay with a card provisioned. Was reading through some other forums and found that this was the root cause. Everyone was deleting their cards to get the screen to work as expected. However, if you go into Samsung Pay --> Settings --> Use Favorite Cards, you can just disable the Screen Off option and all will be well once more. You will still be able to use your cards but will just have to turn on the phone first.
edit: Well [email protected] Worked great last night during testing and now back to turning the screen on again this morning. Going to try disabling all the options under Use Favorite Cards. If that doesn't work, will delete all my cards and try again.
Ant word on whether that worked?
Same issue for me as well (Verizon Galaxy S7 edge, 7.01). When I am on calls (usually have a headset plugged into the phone) the screen cycles on and off repeatedly. Seems to have started when I went to 7.0. So glad others are reporting the same thing as it is very annoying and hopefully something Samsung will fix in the next update. I will try the Samsung Pay fix and report back.
Same issue here, Galaxy S7 Edge on ATT. Noticed after Nougat update. It seems to be problematic across any dialer as I did try and had the same results using the hangout dialer. It does seem to be related to the Samsung Pay application. You can force stop Samsung Pay in applications and everything seems to work correctly. I have tried removing permissions from Samsung Pay and have had no luck. Will try and report to Samsung and Google directly also. Thank ya'll for sharing your info. hopefully they will have a fix soon.
I'm having the same issue on my S8. I thought i was somehow pressing my face against the screen and accidentally activating the "home button." Then I starting blaming one of my friends because it seemed like it only happened when I talked to people with iphones lol. I don't have or use Samsung Pay, so that can't be what's causing this problem. All I know is it's absolutely frustrating and making talking on the phone a complete headache. Hopefully they'll fix this soon.
Thank you all, I have the s8 and it has done this since I got it.
I don't have Samsung Pay installed at all, I use my Bank's pay app so disabled it. It can't be that but have no idea what it is. Driving me nuts, I keen putting people on hold, hanging up on them or at the least have the annoying vibration going off from pushing buttons. Hate hate hate it...

Phone freezes from time to time

Ok, lately having some weird behaviour and wonder if anyone else is suffering this. Sometimes when I get a notificationad try to unlock the screen it just stays black.It seems to still work but the screen isn not showing anything, only thing I can do is to hard reset it by holding the pwoer button after a restart it behaves normal again... Tried factory resetting it but no change... Anythign else I could try?
micleftic said:
Ok, lately having some weird behaviour and wonder if anyone else is suffering this. Sometimes when I get a notificationad try to unlock the screen it just stays black.It seems to still work but the screen isn not showing anything, only thing I can do is to hard reset it by holding the pwoer button after a restart it behaves normal again... Tried factory resetting it but no change... Anythign else I could try?
Click to expand...
Click to collapse
That is because you have turned on the Ambien screen. But I have problems with the proximity sensor and too much time the apps stoped and some things like that
Sent from my Mi A1 using Tapatalk
Yeah, I am having similar issue too. My Mi A1 is now getting lagging now. Really disappointed, because its getting worst day by day.
True.. My ambient display is disabled and still i face regular (atleast once a day, sometimes more) freezes.. Only a reboot can recover the device.. Really irritating!
you are right, esp if you try to open within a few second upon whatsapp message arriv
vigo45 said:
That is because you have turned on the Ambien screen. But I have problems with the proximity sensor and too much time the apps stoped and some things like that
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
you are right, esp if you try to open within a few second upon whatsapp message arrives (through fingerprint), the screen becomes unresponsive but phone works on background. Happened quite a few times now, somehow I would find approx. where could be the restart button and press for restart, quite strange, don't know what to do?!!!
I experience this issue only once (when I tried enabling Ambient display). With Ambient display off, I didn't have a single freeze or app crash. I reboot phone every few days due to updated Magisk/Xposed modules, maybe it helps a bit..?
Since the November update I am also getting freezes and some lag, which is very disappointing. So you are saying that if I turn of ambient display it will take care of the random freezing?
Cheers

[FIX] If your home button stopped working

Last week, I took my phone off the charger and noticed that the home button was not working. Did multiple reboots, clean wipes and also reinstalled the stock ROM, nothing worked. Did the *#808# fingerprint test and found that the figerprint sensor was not responding which led me to believe this could be a hardware issue. I did not have the time to go to the service center so I turned on the on-screen navigation bar and used it like this for a few days.
Today, I thought I'd try to sort this out one more time before I take it to the service center. The *#808# fingerprint test still showed the sensor not available. Rebooted the phone and turned the on-screen nav bar off. Lo and behold the home key started working. I do not know how this happened, I'm just glad that it did.
Just thought I'll post here so that if anyone has issues they could try this out and it might help someone.
Cheers.:good:
I got the same problem. My OP5 Home button(with fingerprint scanner) stopped working suddenly. It got stock android since purchase. I never tried to root it. It suddenly became unresponsive. Will try to use nav bar for few days. Im getting ghost touches as well. Any Help appreciated.
Hi. I have the same issue on my op3t, looking for idfeas.
finalmoksha said:
Last week, I took my phone off the charger and noticed that the home button was not working. Did multiple reboots, clean wipes and also reinstalled the stock ROM, nothing worked. Did the *#808# fingerprint test and found that the figerprint sensor was not responding which led me to believe this could be a hardware issue. I did not have the time to go to the service center so I turned on the on-screen navigation bar and used it like this for a few days.
Today, I thought I'd try to sort this out one more time before I take it to the service center. The *#808# fingerprint test still showed the sensor not available. Rebooted the phone and turned the on-screen nav bar off. Lo and behold the home key started working. I do not know how this happened, I'm just glad that it did.
Just thought I'll post here so that if anyone has issues they could try this out and it might help someone.
Cheers.:good:
Click to expand...
Click to collapse
Hi. I have the same issue on my op3t, Oxygeos Version 9.05. My home and recents buttons do not work but fingerprint works fine. I turned on the on-screen nav bar and the home and recents buttons don't work there as well. Turning it off didn't solve anything. Any idea? Thanks
Facing exactly the same issue after upgrade to 9.0.5. home and recent buttons are not working, but fingerprint is working fine. Did you resolve this issue by any chance? if yes, please let me know as well how it was resolved. thanks. -ramesh
Try doing a factory reset, but take a backup before doing that.
Sent from my OnePlus 3T using XDA Labs
I am also facing this issue. It started off with a boot loop into the recovery every time i try to start the phone. It stopped after i cleared cache from recovery, but the default launcher doesnt work properly, no notifications in my drawer, and many other issues. the hardware buttons are responding (it lights up when i tap on it) but the OS doesn't do anything with it. I have tried with switching to the soft keys and it behaves the same way as well. the fingerprint scanner and back button works so far.
i'm having this problem too Got a OP3T, i found out a bit of info, it has to do with the screen, i'm still facing this problem so im gonna buy a replacement screen and see how it goes, ive already replaced the earphone jack board that houses most the flex cable connections and i also replaced the speaker, home button, and the usb c flex cable to no avail. what i haven't tried was to replace the battery and the main/sub flex cable inside. i'd really like a fix for this.
go to Settings -> Apps -> All Apps (ie including System apps)
look for com.android.fingerprint... or com.oneplus.fingerprint...
"Force Stop" it. and go to its storage and "Clear Cache" , "Delete Data" .
Now restart the Phone.
Worked for me on OnePlus3T running OxygenOS 9.0.5.
Phone was also on charging through out the procedure .. I doubt if it would have any significance though.
Good Luck.
I could not force stop this app.
MY SOLUTION
this is what it worked for me with OP5
I deactivated fingerprint, reboot to recovery, wipe cache+dalvik, restart (without fingerprint anymore) and it seems to be working just fine again.
I have observed this issue too in my oneplus 3 with oxygen os 9.0.6 and also in previous releases. The only thing that works for me is just to reboot the phone.
cincauhangus said:
I am also facing this issue. It started off with a boot loop into the recovery every time i try to start the phone. It stopped after i cleared cache from recovery, but the default launcher doesnt work properly, no notifications in my drawer, and many other issues. the hardware buttons are responding (it lights up when i tap on it) but the OS doesn't do anything with it. I have tried with switching to the soft keys and it behaves the same way as well. the fingerprint scanner and back button works so far.
Click to expand...
Click to collapse
I am facing the exact same problem. Have tried all the other fixes/solutions mentioned in this thread except the 'Factory Reset'.
Please let me know what did you finally do to resolve it.
Thanks
Something new? I Have flash Havoc ROM, but problem still exist :/
back button and recent button does not work on mine.
I have to turn on screen navbar..
The home button was not working.. but it started working after i enabled onscreen navbar...
The phone went to frantic vibrate the first time it boot after flashing new rom..
the light can be seen on these 2 non functional h/w key during boot , but then it turn off, then the h/w back and recent key would not function..
I don't even know what happened to this phone...
Guess i'll keep using the onscreen navbar...

Categories

Resources