This is one hell of a issue that I've never read about online but somehow I'm experiencing.
To make a long story short, a few months ago I bought a OnePlus 6T, after some heavy modding something went wrong and had to hard reset. For some reason, haptic feedback stopped working and never turned back one. Since I was still within the two months that Amazon warrants during christmas season, I asked for a refund and bought another OnePlus 6T of a different colour from a different store (for a much lesser price). Even the new OnePlus 6T had an issue with haptic feedback, when I first turned the phone on, during the setup, the haptic was there, but then after logging in in my Google account (which of course happens pretty early in the setup) again it stopped working.
It is NOT an hardware issue, becuase the feedback works when I receive notifications or a call, but it doesn't work when typing on the keyboard or while navigating the system (or even when I move the slider to vibration which should emit a light feedback).
Since I was tired of asking for a refund, I just kept the phone as is.
Fast forward a few months and today I pick up my new, beautiful and amazing, OnePlus 7 Pro and guess what... THE ISSUE IS STILL THERE.
The haptic was working fine while first setting up the phone, but after the Google log-in, now once again it only works with notifications and not with the keyboard (I tried both Google Keyboard and Swift key) or the alert slider.
YES, vibration is turned ON in the setting.
NO, the phone is not in battery saving mode.
YES, i've tried rebooting a few times
Anyone has any idea why the hell this keeps happening to me and how I could fix it?
Did you try turning on haptic feedback in the Gboard settings?
Dr. Krieger said:
This is one hell of a issue that I've never read about online but somehow I'm experiencing.
To make a long story short, a few months ago I bought a OnePlus 6T, after some heavy modding something went wrong and had to hard reset. For some reason, haptic feedback stopped working and never turned back one. Since I was still within the two months that Amazon warrants during christmas season, I asked for a refund and bought another OnePlus 6T of a different colour from a different store (for a much lesser price). Even the new OnePlus 6T had an issue with haptic feedback, when I first turned the phone on, during the setup, the haptic was there, but then after logging in in my Google account (which of course happens pretty early in the setup) again it stopped working.
It is NOT an hardware issue, becuase the feedback works when I receive notifications or a call, but it doesn't work when typing on the keyboard or while navigating the system (or even when I move the slider to vibration which should emit a light feedback).
Since I was tired of asking for a refund, I just kept the phone as is.
Fast forward a few months and today I pick up my new, beautiful and amazing, OnePlus 7 Pro and guess what... THE ISSUE IS STILL THERE.
The haptic was working fine while first setting up the phone, but after the Google log-in, now once again it only works with notifications and not with the keyboard (I tried both Google Keyboard and Swift key) or the alert slider.
YES, vibration is turned ON in the setting.
NO, the phone is not in battery saving mode.
YES, i've tried rebooting a few times
Anyone has any idea why the hell this keeps happening to me and how I could fix it?
Click to expand...
Click to collapse
Settings, System, Accessibility, Vibration, Touch Vibration [On]
dynospectrum said:
Settings, System, Accessibility, Vibration, Touch Vibration [On]
Click to expand...
Click to collapse
I had a haptic feedback issue with my Huawei P30. Haptic feedback setting was switched on in Gboard settings but it wasn't providing any haptic feedback in the actual keyboard. Turns out I had to go to Settings-->Sounds-->More sound settings and turn "Vibrate on touch" on. I think you might have already tried something like this but it seems like there's a system-level switch that overrides app-level haptic feedback settings.
If it doesn't work, try using a different launcher like Nova and see if it works. It might be able to override some system-level haptic feedback setting on your phone.
Galaxy note 10+ 5g here, tried all suggestions I found with the keywords I searched. If anyone has fixed this or has any insight, I'd appreciate hearing your experience.
My solution was to disable accessibility feature "Select to read". After I disabled it haptic feedback was working again.
Try to disable any of your accessibility features.
Related
As the title says, about 30 minutes ago, haptic feedback stopped working.
So far, I've toggled "vibrate on touch" off/on in both DISPLAY and LANGUAGE & INPUT, moved the slider for "KEYPRESS VIBRATION DURATION", done a handful of restarts to no avail.
I imagine I could do -adb fastboot reboot to get back to stock, but wanted to see if anyone else is having issues and/or fixes.
Thanks in advance for any help.
mtoomey79 said:
As the title says, about 30 minutes ago, haptic feedback stopped working.
So far, I've toggled "vibrate on touch" off/on in both DISPLAY and LANGUAGE & INPUT, moved the slider for "KEYPRESS VIBRATION DURATION", done a handful of restarts to no avail.
I imagine I could do -adb fastboot reboot to get back to stock, but wanted to see if anyone else is having issues and/or fixes.
Thanks in advance for any help.
Click to expand...
Click to collapse
Ended up doing a complete wipe and reinstall stock - still no haptic feedback to be had.
Again, any help would be appreciated.
I had to do a RMA due to the defective vibrator motor in my N5. Maybe yours has died?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Might be a stupid question... but did you happen to install another keyboard?
I installed Swype and lost haptic, even though it was enabled. I cant remember if I unchecked/checked it or if I checked/unchecked haptic in the "stock" keyboard but one or the other fixed my issue.
Thought I'd throw it out there.
jbdan said:
I had to do a RMA due to the defective vibrator motor in my N5. Maybe yours has died?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
@jbdan I'm wondering if I will have to. Just checked and it doesn't vibrate when ringing nor receiving messages (the settings indicate that it should be)
trendiggity said:
Might be a stupid question... but did you happen to install another keyboard?
I installed Swype and lost haptic, even though it was enabled. I cant remember if I unchecked/checked it or if I checked/unchecked haptic in the "stock" keyboard but one or the other fixed my issue.
Thought I'd throw it out there.
Click to expand...
Click to collapse
@trendiggity no keyboards installed and I just checked, the N5 doesn't vibrate when it rings/messaged.
No problem doing an RMA for my N5. Already shipped.
Hey,
A little back story-the S7 i bought in April 1 was all nice, then the buttons would not respond so i took it to samsung's shop and they updated it. The google keyboard vibration intensity decreased noticeably.
Then I did another system update recently, it decreased once again.
Overnight i did the mistake of connecting it to the WiFi and it updated the google keyboard app, completely removing any feel of vibration for the keyboard. Samsung keyboard vibration and other vibration stuff works, just not google keyboard (even though it is checked in the app's settings and seemingly allowed in permissions)...
does anyone know how to fix this? I reinstalled hte app but no go...
+1 for this issue.
I am having this problem also, do you mind to share the software version of your SGS7 with us? I have got Super-Man ROM V1.4.
I have tried Gkey on my M9(MM) and Haptic feedback works, so I think it is reasonable to conclude that this is some kinda compatibility issue.
And we can do nothing to do about it other than installing old version.
Don't know if it relates to this issue, but, I am using Google Japanese Input also, and that haptic feedback doesn't work also.
What vibration strength on keypress do you have set?
CenteaOSD said:
+1 for this issue.
I am having this problem also, do you mind to share the software version of your SGS7 with us? I have got Super-Man ROM V1.4.
I have tried Gkey on my M9(MM) and Haptic feedback works, so I think it is reasonable to conclude that this is some kinda compatibility issue.
And we can do nothing to do about it other than installing old version.
Don't know if it relates to this issue, but, I am using Google Japanese Input also, and that haptic feedback doesn't work also.
Click to expand...
Click to collapse
I'm using the latest updated stock everything, so much so the update check i did moments ago said i was up to date (hope this helps).
Oddly enough the stock keyboard haptic works, so it has to be a google keyboard issue too.
jarayn said:
What vibration strength on keypress do you have set?
Click to expand...
Click to collapse
System default, but changing it doesnt do anything
update! I solved it, rather annoyingly however.
In the system settings, under vibration, notifications vibration is the one that should NOT be zero for google keyboard to vibrate. I have no clue why they combined it with that, but changing the notification vibration settings seemed to bring back the vibration for google keyboard. However this also means my phone vibrates whenever i get a text
Since I purchased the S8+, I've been getting random vibrations when it's in my pocket or when it's in my hand (when muted), and random notification sounds (when not muted). It's up to date, notification reminder and smart alert are both off. I've read that other people are experiencing the same problem but no solution has been found.
Samy Hamdallah said:
Since I purchased the S8+, I've been getting random vibrations when it's in my pocket or when it's in my hand (when muted), and random notification sounds (when not muted). It's up to date, notification reminder and smart alert are both off. I've read that other people are experiencing the same problem but no solution has been found.
Click to expand...
Click to collapse
Ya I've gotten a few random vibrations too
Sent from my SM-G955U using XDA-Developers Legacy app
No sounds here but definitely vibrations at least once a day randomly..
I wonder what it is..
I get them too, I think it might be something to do with the weather app/widget updating
That's been driving me crazy I'll pick up my phone and it'll vibrate for who knows what reason.
I disabled my weather app and widget, but everything is still the same. This is very frustrating, I hope Samsung fixes it ASAP.
I can confirm this problem. Random vibrations. Sound on, vibration on. I thought was only my phone. Exynox version
Is NFC on and it's getting close to what it thinks is a tag? Is it in a case with your bank cards in?
wnp_79 said:
Is NFC on and it's getting close to what it thinks is a tag? Is it in a case with your bank cards in?
Click to expand...
Click to collapse
Nope, NFC is off and it's not close to any credit card or NFC device. I'm clueless.
I believe it's a bug with the fingerprint sensor.
Had this on my other phone. It was yahoo mail app.
It would go off whrn i git emails from people i repy to or updates on orders.
Took a while to find it
My wife also had this problem but tyrn out to be another app.
I have the same issue too.
More times a day i feel single short vibrations, but without any notification.
I tried to ask samsung customer care, but they do not know the problem.
They told me to try using the phone in safe mode to see if the problem was gone.
So to understand if it was a phone problem or of a third party application.
guiduz said:
I have the same issue too.
More times a day i feel single short vibrations, but without any notification.
I tried to ask samsung customer care, but they do not know the problem.
They told me to try using the phone in safe mode to see if the problem was gone.
So to understand if it was a phone problem or of a third party application.
Click to expand...
Click to collapse
Phantom vibrations, look it up.
Do i have to look for phantom vibrations?
I did, but i can't find any solution
This is Dave4777, I just spent over an hour on the phone with AT&T and Samsung turned off almost every app I have that has a Notifier except the ones that I want which make a different notification than my default one period and I'm still getting the random sounds and vibration together or if it's muted I get vibration only. Random no idea why neither does Samsung have any clue. Very frustrating especially for such a high end phone
Figured out what it was on my s8+. My notification reminder was on. I assume the weather app triggered it. Turning it off fixed the issue.
SOLUTION:
Settings>accessibility>notification reminder>off
S8 random notification sound SOLVED!
In notifications settings i switched off notification reminder. The sound is gone by me.Try that
It's either NFC, the finger printer scanner, GPS location services or the commonly forgotten S-Pen (is it loose or missing?)
Go to settings menu, then accessibility, then turn off notification reminder.
On my pixel 2 tap inputs occasionally don't register, I've had it happen in the android system menu, the android back/home buttons, chrome, etc. Is anyone else experiencing this?
My phone's basically on stock default settings, nothing unusual running. Not sure if it's only tap inputs getting dropped or the whole system locking up temporarily. Turning on "Show taps" in Developer options I can see there's no visual effect when a missed tap occurs.
Yes, this is me too exactly. Same thing with the dev option too. Not sure if I should wait for 8.1 or if it's hardware and RMA it. Frustrating because I like this phone.
I noticed this on my phone, clicking around in the settings and on the back and home buttons. I then did a factory reset (because of a separate issue where the location icon was always displaying in the notification area, even when not in use). After that the issue seems to have gone away. So it would seem to be software issue. I suggest trying a factory reset (though beware that this wipes everything on your device).
P.S. nonexistent, I'm impressed that you joined the XDA forums in Dec 2010 and never posted a comment until now. Of course, you might need to change your screen name to "existent," now that you're out in the open.
I have definitely noticed this as well, happy to know it wasn't just me
cb474 said:
I noticed this on my phone, clicking around in the settings and on the back and home buttons. I then did a factory reset (because of a separate issue where the location icon was always displaying in the notification area, even when not in use). After that the issue seems to have gone away. So it would seem to be software issue. I suggest trying a factory reset (though beware that this wipes everything on your device).
P.S. nonexistent, I'm impressed that you joined the XDA forums in Dec 2010 and never posted a comment until now. Of course, you might need to change your screen name to "existent," now that you're out in the open.
Click to expand...
Click to collapse
I tried a reset but the issue still showed up. In fact it happened twice on the first time setup stuff afterwards. I called Google and we went through the motions and reset it from recovery mode but it was still there when I was testing it the next couple hours. Anyway, we're doing the RMA thing. I'll let you guys know how it works out when I get my new phone.
Got my replacement and the problem still exists. It even happens just a couple screens into the initial setup after a factory reset from recovery mode.
I find that it occurs when I'm in a small room with the heat turned up. The sensitivity of the touch screen seems to depend a lot on moisture. If I keep my fingers moist (or wear a touch sensitive glove) it works a heck of a lot better.
ritzack said:
Got my replacement and the problem still exists. It even happens just a couple screens into the initial setup after a factory reset from recovery mode.
Click to expand...
Click to collapse
That's good and bad news I guess, hopefully just needs a software update. I have a replacement coming Monday, but I kind of expect no improvement and that this is just a common thing that a lot of people aren't noticing
I noticed that for a while in Google Play Books, in which I tap the screen frequently to turn pages. I tried a factory reset, which didn't help. I tried running in safe mode and testing on Maps and still had a problem, although less frequently (a higher percentage of taps worked). Then it started to work better. We'll see if that lasts.
I tried flicking as opposed to tapping and flicking always works.
I'd suggest posting on the Pixel product forum or calling support, so that Google becomes more aware of the issue. There are some threads on the subject on reddit and the product forum.
Out of interest are you noticing it any particular parts of the screen?
I've noticed it a few times but it's been on areas of the screen near the edges.
I assumed it was some sort of palm rejection thing going on it the background with it thinking I'm accidently mashing the display.
With me it was the right edge toward the middle, as that's where you tap to turn the page in Play Books.
I get it on the back button frequently, but it happened just now in the middle of the screen when I typed the text input box to start writing this
I think this is the whole OS hanging/freezing briefly actually, not a touchscreen input issue
- Pressing the hardware unlock button can get ignored (both locking/unlocking)
- Scrolling from a quick flick + release can suddenly stop (no additional inputs)
So most likely this is a software issue, hopefully fixed in an upcoming update? It's kinda annoying
Did you change the DPI or font size? I go back to default and it seems that everything is good now.
---
update: no it happens again…
nonexistent said:
On my pixel 2 tap inputs occasionally don't register, I've had it happen in the android system menu, the android back/home buttons, chrome, etc. Is anyone else experiencing this?
My phone's basically on stock default settings, nothing unusual running. Not sure if it's only tap inputs getting dropped or the whole system locking up temporarily. Turning on "Show taps" in Developer options I can see there's no visual effect when a missed tap occurs.
Click to expand...
Click to collapse
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Haven't changed the DPI or font size
LimitsX said:
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Click to expand...
Click to collapse
I can trigger the system hang/"missed input" most reliably by visiting m.reddit in chrome (any thread w/ comments) and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Haven't changed the DPI or font size
LimitsX said:
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Click to expand...
Click to collapse
I can trigger the system hang/"missed input" most reliably by visiting any m.reddit thread in chrome and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
nonexistent said:
Haven't changed the DPI or font size
I can trigger the system hang/"missed input" most reliably by visiting m.reddit in chrome (any thread w/ comments) and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Click to expand...
Click to collapse
So, I replicated what you told me, 3x. I didn't miss any taps, and no system hang/missed input..
hmm
Got my replacement and it has been much better so far. Still a few dropped inputs but I think those may be false positives because I am hyperfocused on it. Pretty sure I have always had to double click occasionally on all phones at various times.
nonexistent said:
Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Click to expand...
Click to collapse
Yeah, sometimes I see a tap register visually on the screen, but the intended action doesn't happen.
redandblack1287 said:
Got my replacement and it has been much better so far. Still a few dropped inputs but I think those may be false positives because I am hyperfocused on it. Pretty sure I have always had to double click occasionally on all phones at various times.
Click to expand...
Click to collapse
It's funny. I had the issue. Did a factory reset. Felt like it was better. But now that I'm thinking about it more I notice it a lot. So I can't tell if it's really different. Before I figured I'd made a mistake. Now I think it's the phone. Damn you phone!
Anyway, I notice that the issue tends to happen more or less randomly, at any position on the screen. Also, sometimes the same tap fails to register twice in a row, but once it's starts working all subsequent taps that come in a row work (say I'm clicking through a lot of menu items in some settings). So maybe that lends some credence to the idea that there is a system for registering the taps that is not waking up and once it does it works fine.
Perhaps related, I have my ambient display set to wake on double tap. Before the Nov update it hardly worked. Now it seems to be working reliably.
About three months ago my Pixel 2 (purchased new from Google) began having an issue where it becomes unresponsive or extraordinarily delayed on responding. It almost always happens when I'm waking the phone up from being locked. When it happens, the phone will eventually unlock but everything reacts several seconds after contact (power button, taps, swipes). A reboot or power down fixes the problem, but is always necessary.
I switched to Project Fi around that time and thought it had something to do with the switching between CDMA and GSM (Sprint/US Cellular vs T-Moble) towers, but I've switched to T-Mobile (a solely GSM provider) since and the problem persists.
I am running Android Pie (stock). My bootloader is unlocked and I do have Magisk installed. No TWRP. I don't have any obvious troublemakers installed (like Xposed, for example) and only a few apps that even use root (Cerberus, Adaway, and Nova Launcher).
I have heard about the Pixel 2 XL having a hardware issue that results in unresponsiveness and that ultimately requires sending in the device for a replacement. Is this the same thing?
Any advice would be much appreciated. If it would be helpful, I can produce logs, but I'll have to wait until it happens again to offer logs that might contain clear indications of what might be happening.
- Computerslayer
computerslayer said:
About three months ago my Pixel 2 (purchased new from Google) began having an issue where it becomes unresponsive or extraordinarily delayed on responding. It almost always happens when I'm waking the phone up from being locked. When it happens, the phone will eventually unlock but everything reacts several seconds after contact (power button, taps, swipes). A reboot or power down fixes the problem, but is always necessary.
I switched to Project Fi around that time and thought it had something to do with the switching between CDMA and GSM (Sprint/US Cellular vs T-Moble) towers, but I've switched to T-Mobile (a solely GSM provider) since and the problem persists.
I am running Android Pie (stock). My bootloader is unlocked and I do have Magisk installed. No TWRP. I don't have any obvious troublemakers installed (like Xposed, for example) and only a few apps that even use root (Cerberus, Adaway, and Nova Launcher).
I have heard about the Pixel 2 XL having a hardware issue that results in unresponsiveness and that ultimately requires sending in the device for a replacement. Is this the same thing?
Any advice would be much appreciated. If it would be helpful, I can produce logs, but I'll have to wait until it happens again to offer logs that might contain clear indications of what might be happening.
- Computerslayer
Click to expand...
Click to collapse
Do you have the navbar hidden by any chance
crixley said:
Do you have the navbar hidden by any chance
Click to expand...
Click to collapse
Well, I have Nova set up to hide the dock unless I swipe up (or down) on it. I can't seem to find a setting about hiding the navbar. Where should I be looking to check?
computerslayer said:
Well, I have Nova set up to hide the dock unless I swipe up (or down) on it. I can't seem to find a setting about hiding the navbar. Where should I be looking to check?
Click to expand...
Click to collapse
Did you install any apps to hide your navigation bar? Is it always visible? Immersive mode apps for example
crixley said:
Did you install any apps to hide your navigation bar? Is it always visible? Immersive mode apps for example
Click to expand...
Click to collapse
We're talking about the back button and the new pill gesture button, right? If so, then no I haven't installed anything to hide those: they are always visible.
Well, after 24 hours, I had the issue resurface. Unfortunately, the logging app I was using (matlog) froze up with the phone and produced a blank text file. While rebooting restored normal function of the phone, I can't produce a log as a result.
It occurs to me that while I am not disabling the navbar, I do use a function of the Cerberus anti-theft app to disable the notification bar while locked. Could this be the source of my issue? If so, is there any way to confirm this?
In the meantime, I've disabled that function and will see if the lock-up occurs again.
I'm curious where you were going with the question about the navbar. Could you tell me more about what you were thinking it might have been?
I went ahead and disabled the 'block status bar' function of the Cerberus app and the problem has not resurfaced in over two days (it was occurring several times daily). Although I can't definitively prove it, I think the culprit was the app.
Thanks for the time and assistance!
computerslayer said:
I went ahead and disabled the 'block status bar' function of the Cerberus app and the problem has not resurfaced in over two days (it was occurring several times daily). Although I can't definitively prove it, I think the culprit was the app.
Thanks for the time and assistance!
Click to expand...
Click to collapse
Sorry I didn't get back to you I read this a while back and totally thought I responded. Yeah anything that hides the status bar or navbar from the system UI at all times is known to cause wake issues. On my essential phone it would require me to restart it to actually get the screen to come back on. It's called the deep sleep of death or something haha
crixley said:
Sorry I didn't get back to you I read this a while back and totally thought I responded. Yeah anything that hides the status bar or navbar from the system UI at all times is known to cause wake issues. On my essential phone it would require me to restart it to actually get the screen to come back on. It's called the deep sleep of death or something haha
Click to expand...
Click to collapse
Hello Crixley,
No worries at all - I'm always grateful when anyone responds around here because I know that we're all balancing regular life and our hobby time!
I'm relieved to hear that it is a known issue, though I'm going to miss the functionality! I wish Google would build some kind of equivalent security measure so that the network state can't be changed while the phone is locked. I'm guessing that this issue is exactly why they haven't gotten to it (yet?).
Thanks for your time & support, both here with my issue and across the forums.
Peace,
Computerslayer
computerslayer said:
Hello Crixley,
No worries at all - I'm always grateful when anyone responds around here because I know that we're all balancing regular life and our hobby time!
I'm relieved to hear that it is a known issue, though I'm going to miss the functionality! I wish Google would build some kind of equivalent security measure so that the network state can't be changed while the phone is locked. I'm guessing that this issue is exactly why they haven't gotten to it (yet?).
Thanks for your time & support, both here with my issue and across the forums.
Peace,
Computerslayer
Click to expand...
Click to collapse
I'm glad to hear it's fixed for you!
I try to help as much possible, I remember how good it was to have people help me when I needed it and sometimes I need a hand as well.