Moto X Pure Home, Multitasking, Back Button Not Working - X Style (Pure) Q&A, Help & Troubleshooting

Hey guys! I've seen a few threads on this exact issue, but I haven't been able to find any real advice. So a few days ago I updated my Moto X Pure to the newest security patch. A day later the nav keys started to not respond to touch. Occasionally they work but most times they don't. Is anyone having this same problem? Do you know a fix? Thanks!

nexusmoto said:
Hey guys! I've seen a few threads on this exact issue, but I haven't been able to find any real advice. So a few days ago I updated my Moto X Pure to the newest security patch. A day later the nav keys started to not respond to touch. Occasionally they work but most times they don't. Is anyone having this same problem? Do you know a fix? Thanks!
Click to expand...
Click to collapse
Did you factory reset? It is not the optimal solution as it takes time, but a reset dues fix the majority of issues phones have after an OTA. If you still have problems after this report back. I did the factory reset immediately after the latest OTA and had no issues. Android practically restored nearly everything app wise. All I had to do was wait it out.

FR does not work
I have the same problem, just did a factory reset but still not working, is weird to find out that is not a touch "hardware" fault, since I got into the configuration I am able to tap the next and backs buttons also the mic icon and camera works in the locked screen, the problem is only in the "Home bar" or soft key bar i don`t know the name. If someone had a solution please share.

I am also having same problem in my moto x style..
---------- Post added at 09:26 AM ---------- Previous post was at 09:14 AM ----------
nexusmoto said:
Hey guys! I've seen a few threads on this exact issue, but I haven't been able to find any real advice. So a few days ago I updated my Moto X Pure to the newest security patch. A day later the nav keys started to not respond to touch. Occasionally they work but most times they don't. Is anyone having this same problem? Do you know a fix? Thanks!
Click to expand...
Click to collapse
I am also having same problem. So I take my phone to moto services centre but they are also failed to resolve this problem..

Hey! So, give this a try:
Install Nova launcher, then on the home screen long press and click widgets. In the widgets section, at the top there should be an option called "Activites" long press and put that on the home screen, then it should ask you which activity. scroll to the "S" section, and select "Setup wizard" and then select "SetupWizardTestActivity".
Once that wizard is set as a widget, click the widget and go through the wizard again, and see if that does it. It did it for me, on many occasions haha

Hi, I am also facing this issue. I did the Nova launcher steps, and it worked for couple of days. Then, the same issue happened. I did factory reset of my phone and now i can't configure the phone as I can't get past the wifi selection screen. Stuck with this.

Robin6029 said:
Hi, I am also facing this issue. I did the Nova launcher steps, and it worked for couple of days. Then, the same issue happened. I did factory reset of my phone and now i can't configure the phone as I can't get past the wifi selection screen. Stuck with this.
Click to expand...
Click to collapse
As in you're stuck in the setup wizard? Do you have root by chance?

I'm having the same problem, nothing works :crying:
So it is not just me, wow!

2 days ago my touchscreen started acting out, now I have a deadzone at the navigation bar. I've been using my phone upside down, if anyone has been through this and fixed it please let me know.

Guess what!
I just did a downgrade using ADT so I flashed my Moto X Pure to Lolipop to validate my theory but no success.
I can said that the touching problem is a hardware issue and not a software like I was thinking.
Why is this happening, IDK but let me ask you if you did the same "ordinary behaviour" like me.
The day my Moto X starts to get like crazy getting ghost touchings and ghost slidings I was having my cellphone in my back pocket and driving my motorcycle mid trip 3-4 hours.
When I took my phone out to take some pictures I got a hot phone and the touchy doing crazy ghosty responses.
I turned the phone off but when I restarted like a minute after the ghosty touching was persistent, turned off the phone again and like an hour latter turned on, no more ghosty touches but the softkeys ( back, home, tasks) stopped working.
I read before that for some tablets this is caused by the protection case and they removed the case and worked again, well is not my case since I have not any case attached to my phone, but seems to be some bad pressure in some part that damage the touch area.
Please share your comments if you applied some pressure like me sitting in the phone, for me is a "ordinary behavior" (having my phone in my levi's rear pocket) but for Motorola seems too much.

this happened to my phone as well "After a Security Patch Update thru OTA" and navbar stopped working the Other Day and I guess we shall wait for the Next update to by MOTO "ANDROID NAUGAT 7". but for Now I use simple Control navbar from Play store Until The OTA update fix the problem.
on Lock screen mic and Camera shortcut works Properly so is the software issue....

I'm trying help my friend with her Moto X Style. It has the same problem and I could test the screen with a screen tester. And works fine all touchscreen. Apears that programing for buttons was missing.

Marcel_16V said:
I'm trying help my friend with her Moto X Style. It has the same problem and I could test the screen with a screen tester. And works fine all touchscreen. Apears that programing for buttons was missing.
Click to expand...
Click to collapse
Just happened to me as well with a Moto X Pure - was driving in my car, security updated...buttons stopped working and have found zero way to get them back. They work when you flip the phone upside down, also work when the phone is locked to drag the camera or microphone shortcuts up, they just dont work on the 200x1080 pixel bar across the bottom.
-Uninstalled all "Screen Overlay" apps - nothing
-Boot to recovery and wiped cache partition - nothing
-Factory Reset the phone with Auto Restore - nothing
-Factory Reset with NO Auto Restore - nothing
-Factory Reset and 100% setup as a new device - nothing.
I cant believe there is no fix for this yet? How can a company rollout a security update that for the most part makes the phone very unuseable, cant even seem to see that they have addressed this.

No issues with mine and I am running the Dec patch.

Almost sounds like it was a corrupted OTA release. It could have been a server issue or whatnot. Call Lenovo/Moto support of the touchscreen is working in the navbar area but the navbar itself isn't. It is worth a try even if out of warranty. The worst they can say is they can't help.

TheRealMrTrueX said:
Just happened to me as well with a Moto X Pure - was driving in my car, security updated...buttons stopped working and have found zero way to get them back. They work when you flip the phone upside down, also work when the phone is locked to drag the camera or microphone shortcuts up, they just dont work on the 200x1080 pixel bar across the bottom.
-Uninstalled all "Screen Overlay" apps - nothing
-Boot to recovery and wiped cache partition - nothing
-Factory Reset the phone with Auto Restore - nothing
-Factory Reset with NO Auto Restore - nothing
-Factory Reset and 100% setup as a new device - nothing.
I cant believe there is no fix for this yet? How can a company rollout a security update that for the most part makes the phone very unuseable, cant even seem to see that they have addressed this.
Click to expand...
Click to collapse
I installed a custom ROM with your OWN buttons and saved that device.
I Installed a Resurrection Remix on her Moto X Style, the battery sucks, but the device is working.
http://www.resurrectionremix.com/

is there a solution to this yet?
back button home button not working?

twinskenny said:
back button home button not working?
Click to expand...
Click to collapse
Nope, so far there is no video you youtube, no actual fix on any forums or no actual working solution whatsoever. This is ****ing pathetic, Motorola a Fortune 100 company released a security patch that clearly effected a small percentage of their phones. They have not addressed it or even offered to rush another patch that ADDS BACK IN THE PROGRAMMING for the 200x1080 bottom bar.
That is the problem, someone on a thread I found had dissected the patch, and the line for "Program; TouchPoints x200x1080 were just missing"
With this being more than just a few hundred phones, one would think they would actually try to assist. NOPE
Currently using a SoftKey App on the side of my screen, never buying motorola again after this type of blatant disregard for customer support.

TheRealMrTrueX said:
Nope, so far there is no video you youtube, no actual fix on any forums or no actual working solution whatsoever. This is ****ing pathetic, Motorola a Fortune 100 company released a security patch that clearly effected a small percentage of their phones. They have not addressed it or even offered to rush another patch that ADDS BACK IN THE PROGRAMMING for the 200x1080 bottom bar.
That is the problem, someone on a thread I found had dissected the patch, and the line for "Program; TouchPoints x200x1080 were just missing"
With this being more than just a few hundred phones, one would think they would actually try to assist. NOPE
Currently using a SoftKey App on the side of my screen, never buying motorola again after this type of blatant disregard for customer support.
Click to expand...
Click to collapse
Same problem here. Today morning, my 2015 Moto X Style just stopped working (the buttons). I did not do any update or install anything. So I do not really understand what you talk about here - it was an automatic whatever from Motorola that broke all the phones? That's ridiculous! Like a virus
I'm using the old Android Lollipop BTW - anyone knows if this issue remains on the new system? I never update due to serious slow down after it. Both Google and Apple are complete assholes when it comes to updates. So I've just been ignoring their "brand new awesome cool all is gonna work releases"
I've been a proud Moto user for years now. This is just unacceptable. They're gonna loose big with this one.

If you would do a factory reset after flashing the newest major rom releases it would be plenty fast.

Related

[Q] Verizon G2 buggy touch screen?

Is anyone else having issues with the touch screen triggering at different places when touched, or randomly knocking off the phone when you're not even touching the phone? I turned off my knockon feature, but I would see my notification bar be highlighted without me touching it. Just wondering if i'm the only one with this problem.
No issues at all.
Sent from my VS980 4G using XDA Premium 4 mobile app
I just picked mine up yesterday and have not had any problems with it.
I've had since launch and For the first time today I had a glitch. Touched a link in the browser and it clicked a link 3 links down. Clicked back button and it went back.tried to click the link again and it clicked several links down. I exited the browser and restarted.Clicked the link and it worked perfectly. The only time I've had an (issue?) At all.the phone is practically perfect in every way to me. My favorites smart phone and I've been phone jumping since the HTC touch Windows mobile
Sent from my VS980 4G using Tapatalk 4
I have had issues when typing, some times the letter is entered in like 3 tines. I have also had some other very strange issues but I still love this phone!
Sent from my VS980 4G
dru06 said:
I have had issues when typing, some times the letter is entered in like 3 tines. I have also had some other very strange issues but I still love this phone!
Sent from my VS980 4G
Click to expand...
Click to collapse
this glitch is kinda what happened with mine, and i confirmed what it was doing
in swiftkey, you know how tehre's the option to change the long press delay? well i was holding down that little bar to drag it down, and i noticed while holding it inplace, the numbers were going crazy..it was going up/donw/up/down incredibly fast, instead of just staying stationary..i was like, wtf? so i went to dev options, turned on show touch points and the trace so i could see the axis, and i noticed it was freaking out. holding my finger in place, it was as if it was moving around like crazy.
so i did a factory reset and flashed the clean verizon rom scott posted, and it hasn't done it since. no idea wtf was going on. i realized it was messing up bc my typing became really bad, and it would enter things i didn't type.
Touch Screen has a mind of its own - bad digitizer??
I woke up today to find my screen on, showing the lock screen which I found odd. Now most of the time the screen has a mind of its own where basically its like an invisible finger is randomly touching the screen at a frantic place. This opens up apps, moves icons around, calls people if the phone app manages to get opened, etc. After struggling to override the "invisible finger" I've done a reboot from the power menu, powered off from the power menu and left it off for 10 minutes before turning off and held down the power and volume down button to reboot. None of these methods fixed the problem0
Please note I did accept the Verizon update but was good on it for a day prior to this issue. I have installed minimal 3rd party apps and can't attribute the problem to starting right after installing something. I do use the Ghost 100 wireless charger but have been using this from day 1 without issues so I don't think that'a problem either. The Verizon store sold me this charger and although its not listed as being compatible on Verizon's website I have a feeling that's cause the phone is so new. The charger is WPC certified. Being that this problem is intermittent (happens way more often than not) I think it may be a software issue and I'm about to do a hard factory reset. If that doesn't work then I'm convinced its a hardware issue and probably a bad digitizer. I've been very gentle with the phone - haven't dropped it, no moisture or water exposure, not rooted, etc. I'll report back if the factory reset works. Anyone else having the same or a similar issue?
Super buggy lockscreen!!!
prophecy408 said:
Is anyone else having issues with the touch screen triggering at different places when touched, or randomly knocking off the phone when you're not even touching the phone? I turned off my knockon feature, but I would see my notification bar be highlighted without me touching it. Just wondering if i'm the only one with this problem.
Click to expand...
Click to collapse
You're not alone! My G2 has been driving me crazy the last couple of days when trying to use the lockscreen. It'll spaz out and either skip a connection of display a whole different pattern than I drew. It will also shut off the screen and reset the "wrong password" counter. I love this phone but this is super aggravating!
Hard reset didn't help at all. I went to a Verizon store and they exchanged for a new one and determined I had a hardware failure.

Random issues on separate days (SM-935FD)

Hi all,
I have a black S7 Edge International version (Dual Sim version). The phone as a whole has been working great. I have been having certain issues though, they don't happen very often. So I'm not sure if its related to certain apps I have or if it's an issue with the phone.
Each issue happened on a separate day.
First problem: The phone froze when I was editing a photo on Adobe Lightroom. This was the first time I was using the app, so I launched after installing it. I tweaked a photo and noticed the phone lagging. They it froze, and I couldn't do anything on the screen. Nothing worked until I did a hard reset. Afterwards, the problem didn't occur again, although I haven't tried Lightroom since, so maybe I should, to see if the problem is with the app. Does this happen often with lightroom? Or could this be a phone issue?
Second Problem: On another day I had my phone randomly start vibrating, like it was receiving a call. I had just made three calls to my wife, and thought she was calling back. However, there was no call notification, and nothing on the drop down menu. There was also no ringtone. The phone kept vibrating, and wouldn't stop. I pressed the power button and reset, then the problem stopped.
Final problem: Today, I've been using the phone fine. However I was playing angry birds and then pressed the home button, so the game was still on it's memory, and being multitasked. I used the phone again a few times, then I noticed on the bottom that the game launcher circle (was on the bottom of my homescreen), even though the game was not open (still in the multitask window - I assumed) I tried to click the multitask window, and the button lit up, but nothing happened. The multitask window had frozen. Again it required a restart, and now it's working.
Given that I'm having these three issues (none have repeated themselves though), is this just the phone needing an OTA update, early phone bugs, specific 3rd party app issues, or is it a more serious problem?
Should I take the phone to Samsung and ask for a replacement, or should I wait it out?
Would love some advice from people, and would also like to hear if you've had similar problems.
Current firmware I'm on: G935FXXU1APB6
Thanks!
Does anyone have any feedback on this? Thanks!
I have the first problem on my phone.
But I didn't use adobe lightroom
and I've seen many user reported this problem in many different threads. it seen a known issue.
Thanks for that stone... Hopefully it's a bug... Would love to hear if anyone thinks that it requires a replacement... Also, i just found a dead pixel on the top corner of my phone... it's completely black...
Is that grounds for replacing the phone, or is samsung wishy washy about the whole thing?
I have the second problem; sudden vibrations with no reason, no app pending or anything else; I start to think it is associated with the Smart Alarm being activated (in Advanced settings).....
Anyway, really a bug, in fact the Smart Alarm and Smart Stay are known for having made other problems previously, but seems they didn't correct all the bugs.....
eyeatoma said:
Thanks for that stone... Hopefully it's a bug... Would love to hear if anyone thinks that it requires a replacement... Also, i just found a dead pixel on the top corner of my phone... it's completely black...
Is that grounds for replacing the phone, or is samsung wishy washy about the whole thing?
Click to expand...
Click to collapse
If there's a dead pixel I would return it.... There has been alot of people talking about freezing and rebooting... I've experienced too.... Most likely a software issue.... When I got the S6 last year my phone would reboot 3-5 times a day until a software update came out.... The continuous vibration I haven't heard anyone talk about... But if your still in you grace period I would get another phone for the pixels alone... Too nice and new to have to deal with that
Galaxy S7 edge
Hey, I have the same phone with the same firmware. I experienced the freezing right after I opened the camera from the lock-screen, it lasted for a few minutes and then went away. I'm waiting till Sunday to get the OTA and if I don't, I'm just going to update using Odin, considering how the firmware for the SM-G935FD and SM-G935F is the same.
Sounds good, thanks for the advice guys... I went to Samsung, and they said they would replace the phone for the dead pixel... Will take a week to arrive, but I'm just glad it's getting replaced...
I would return it immediately while it is within your return period.
eyeatoma said:
Hi all,
I have a black S7 Edge International version (Dual Sim version). The phone as a whole has been working great. I have been having certain issues though, they don't happen very often. So I'm not sure if its related to certain apps I have or if it's an issue with the phone.
Each issue happened on a separate day.
First problem: The phone froze when I was editing a photo on Adobe Lightroom. This was the first time I was using the app, so I launched after installing it. I tweaked a photo and noticed the phone lagging. They it froze, and I couldn't do anything on the screen. Nothing worked until I did a hard reset. Afterwards, the problem didn't occur again, although I haven't tried Lightroom since, so maybe I should, to see if the problem is with the app. Does this happen often with lightroom? Or could this be a phone issue?
Second Problem: On another day I had my phone randomly start vibrating, like it was receiving a call. I had just made three calls to my wife, and thought she was calling back. However, there was no call notification, and nothing on the drop down menu. There was also no ringtone. The phone kept vibrating, and wouldn't stop. I pressed the power button and reset, then the problem stopped.
Final problem: Today, I've been using the phone fine. However I was playing angry birds and then pressed the home button, so the game was still on it's memory, and being multitasked. I used the phone again a few times, then I noticed on the bottom that the game launcher circle (was on the bottom of my homescreen), even though the game was not open (still in the multitask window - I assumed) I tried to click the multitask window, and the button lit up, but nothing happened. The multitask window had frozen. Again it required a restart, and now it's working.
Given that I'm having these three issues (none have repeated themselves though), is this just the phone needing an OTA update, early phone bugs, specific 3rd party app issues, or is it a more serious problem?
Should I take the phone to Samsung and ask for a replacement, or should I wait it out?
Would love some advice from people, and would also like to hear if you've had similar problems.
Current firmware I'm on: G935FXXU1APB6
Thanks!
Click to expand...
Click to collapse
None of the issues mentioned above, using since 2 weeks now, Adobe lightroom works great here,SM-G935FD:
BTW:you should have been on G935FXXU1APB8 by now:
http://www.sammobile.com/firmwares/database/SM-G935F/CAC/
Double post
hagba said:
None of the issues mentioned above, using since 2 weeks now, Adobe lightroom works great here,SM-G935FD:
BTW:you should have been on G935FXXU1APB8 by now:
http://www.sammobile.com/firmwares/database/SM-G935F/CAC/
Click to expand...
Click to collapse
Thanks Yerevan... I wanted to wait to see if I'd get an OTA update... Do you have the changelog for this firmware? What are the updates/improvements. THanks!
i mostly had camera freezes from lock screen and random reboots.... hopefully a software update will fix it

[HelpNavigation Bar Unresponsive

Just got a Moto X Pure (Style XT15752) (Dual SIM India variant) a few weeks ago to replace a OnePlus that refused to charge.
Running on TruePureX MM ROM at the moment with Frankenclark kernel.
Had a few issues with ghost touches on the navigation bar early on but I always assumed it was due to moisture on the screen or something because it would always disappear in a few seconds (and in the meantime I'd give the screen a wipe with a cloth or such)
But now the nav bar completely refuses to accept touch input. When I enable show touches (in developer options), touches on the navigation bar area are not registered whatsoever.
Saw a couple threads with similar if not exactly the same issue but no solution as such.
The weird thing is that this part of the screen works perfectly in TWRP suggesting a software issue.
Tried wiping system and reflashing the ROM already with no success.
Any suggestions guys? Trying to fix this without going to service as that will take a while and I don't have a spare phone to use in the meantime. (My work seems to revolve around being connected 24/7)
P.S. Also using Button Savior to use the phone at the moment. Only the Home button works, not back and multitasking.
VikramK123 said:
Just got a Moto X Pure (Style XT15752) (Dual SIM India variant) a few weeks ago to replace a OnePlus that refused to charge.
Running on TruePureX MM ROM at the moment with Frankenclark kernel.
Had a few issues with ghost touches on the navigation bar early on but I always assumed it was due to moisture on the screen or something because it would always disappear in a few seconds (and in the meantime I'd give the screen a wipe with a cloth or such)
But now the nav bar completely refuses to accept touch input. When I enable show touches (in developer options), touches on the navigation bar area are not registered whatsoever.
Saw a couple threads with similar if not exactly the same issue but no solution as such.
The weird thing is that this part of the screen works perfectly in TWRP suggesting a software issue.
Tried wiping system and reflashing the ROM already with no success.
Any suggestions guys? Trying to fix this without going to service as that will take a while and I don't have a spare phone to use in the meantime. (My work seems to revolve around being connected 24/7)
P.S. Also using Button Savior to use the phone at the moment. Only the Home button works, not back and multitasking.
Click to expand...
Click to collapse
Go here: http://forum.xda-developers.com/moto-x-style/help/navigation-buttons-issue-t3497985

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...

Fingerprint hardware not available and screen locks itself immediately!

Hi everyone!
I have a OP 2 for more than one and a half years now and never had any issues with it(stayed stock...) until recently. I didnt update the phone to the latest version and was putting it off, and today in the afternoon when I tried to unlock my phone it said the 'Fingerprint hardware is not available' and after unlocking the phone with the pattern, it IMMEDIATELY LOCKS ITSELF BACK !!! after split second it just locks the screen while everything is working like connection, wifi, messages, notifications, etc. but due to this I cannot access anything on the phone, can't go to settings and switch to onscreen nav bar buttons, can't force stop/wipe cache the com.fingerprints.serviceext either, tried restarting it several times, downloaded the update but can't even install it because the phone just locks!:crying: I have no idea what would fix it and I am avoiding a full reset and wipe on the phone(also based on all i have read, dont think it would fix it anyways)
If anyone knows whats the problem or has dealt with it or knows someone who has, please help me out here on how to fix this and what to do. I did not root it or flash custom ROM's on it yet and never had a flip cover or any sort of case so literally don't know why it happened.
Thanks in advance,
Max
Hi
I had the exact same issue with mine, I was on LineageOS and could access the logs so I was able to determine it was an hardware failure.
Went to a repair shop to replace the home button, and Bam it worked again.
If you didn't flash a custom ROM it is likely an hardware issue just like I had.

Categories

Resources