Vibration feedback keeps turning off

Jan 30, 2018
21
0
0
I've had the phone for a few weeks but only started noticing this today. The switch under Sound and Vibration settings keeps reverting back to the "off" position, and thus turning off Vibration Feedback, which I want and keep having to manually turn back on. Any fix for this?
 
Perhaps it's in power saving mode? if you have a low battery it'll turn off "unnecessary" features like vibration.
 
It's definitely not that. Power Saving mode hasn't been on since I got the phone. I did drive a lot today, so maybe there's something with either google maps or AT&T DriveMode? But even then I just turned DriveMode on and off and it didn't affect it. It seems thus far to be random.
 
It's definitely not that. Power Saving mode hasn't been on since I got the phone. I did drive a lot today, so maybe there's something with either google maps or AT&T DriveMode? But even then I just turned DriveMode on and off and it didn't affect it. It seems thus far to be random.

Is your phone exhibiting this issue continuously, or is it intermittent/seemingly random?
 
No 3rd party volume control app, and default launcher. I'm new to android and have only previously had windows phones before this, so I'm just trying to get used to the new system before too much messing around.
 
The only thing that would make sense to me would be if you use power saver mode sometimes. It's a known cause from previous issues exactly like this, where the problem seems intermittent. This is because the user would manually use power saver (or it would kick in when the battery was low) which switched off vibration feedback - which is normal.. however what wasn't expected was that when power saver was turned off (whether automatically shutting off after charging or turned off manually) it did not restore vibration feedback to the "on" setting. Thus they would have to turn vibration feedback on again in the settings. If this isn't the case with you, I'd say your situation is fairly unique and booting into recovery, wiping cache to see if the problem persists would be step 1. If that fails then it might be factory reset time.
 
Last edited: