@mymike No there isn't an issue opened for it yet. If you could open it that would be great as I don't have a github account.
Posts made by pablo180
-
RE: No Haptic Feedback on 16.04
-
RE: No Haptic Feedback on 16.04
I've also noticed that when comparing it to the same phone still running 15.04, the vibrations on the keyboard, and presumably elsewhere in the UI, aren't as pronounced or 'loud' in 16.04 as they were in 15.04. Could that be the problem, that they are firing but are just too subtle? Is there a way to turn them up?
-
RE: No Haptic Feedback on 16.04
@mymike Yes, that's exactly it! I didn't really notice that before but after some experimenting I realized that it is firing on the first button or action, usually with a slight delay, then no further haptic feedback. Sometimes after a while it does seem to fire again, usually in Settings or something once more, again usually delayed, and then only the once and nothing afterwards. It is quite strange.
-
RE: No Haptic Feedback on 16.04
@advocatux Yes. It was in Settings > Sounds > Other Vibrations. However this was unfortunately already turned on, so that wasn't the problem. If I turn 'Other Vibrations' off, I basically get the same result - keyboard still vibrates but nothing else.
-
No Haptic Feedback on 16.04
I've recently been updated to 16.04 RC on my Aquaris E4.5 and there are many improvements, thank you. One major annoyance though is that haptic feedback seems to be entirely missing on the entire OS except when typing on the keyboard. Is this a feature, a bug? I know that feedback has been entirely missing on the spacebar since I started using UBPorts (and still is) but now I don't get any feedback at all. This obviously makes it difficult to tell whether a press has been registered when opening and navigating apps.
Is there a setting that I have missed or that needs to be turned back on? Thanks for the help.
BQ Aquaris E4.5 Ubuntu 16.04 (2018-W39)
-
RE: Space key vibration lost in keyboard after r9
Same for me too on both my Aquaris E4.5s but I am only on r3 and it occurred only after a recent update, presumably to r3. I've tried switching to the RC channel and the development channel and the problem is still present.