I have /e/ v1.5 on a Teracube 2e 2021 (“Emerald”) and some things weren’t working correctly until I did a wipe / install with this latest version. Since my original installation with v1.2 I haven’t been able to get haptic feedback in any version.
I’m sure the vibrator is working because it vibrates when the alarm goes off. The only place I’ve had vibration from screen presses in the UI has been when moving the minute hand while setting the alarm timer. It doesn’t vibrate at all for keyboard button presses, nor anything else in the UI: no setting switch selections, no menu or back button, etc.
I can confirm I have these exact settings (I don’t know any others that could be relevant):
Sound (top level setting) > other sounds and vibrations > Touch vibration (Haptic feedback for tap, keyboard and more) = On (boolean slider)
Accessibility (top level setting) > interaction controls > Vibration and haptic strength > Touch feedback = On (radio button with 2 choices, On or Off)
Is there a known issue with haptic feedback on the Teracube or /e/ in general? This is a common phone for /e/ so I’ve waited a long time for this to be reported. I wanted to check here before finding somewhere to submit a bug report and deciding, based on whether this is fixable, whether to revert to LineageOS. I hope this is something that has a fix or settings change I’ve missed
In /e/ v1.5 (dev version) on the Teracube there is no “Input” menu under Settings > System.
There is a “Languages and input” menu which does have some relevant keyboard settings: although as I said, my phone has no haptic feedback for most non-keyboard UI elements either. In any case my phone has:
System > Languages and input > On-screen keyboard > Android Keyboard (AOSP) [my only keyboard installed] > Preferences > Vibrate on keypress = On (the default)
I posted this here in hope either a developer or at least someone with relevant experience could respond with how this might be troubleshooted.
I’ll also check if there’s a GitHub issue queue for /e/ with certain devices, but in the meantime please I still need to determine if there are known issues, or drivers / other software missing in the standard builds for this phone.
I believe I found it. In the Advanced settings for the AOSP keyboard there is A “Keypress volume duration” setting which, by default, was 0 (set with a slider up to 100 ms). I’d set this to a significant nonzero value, kind of at random (29ms) which still could not be felt or heard at all. I just tried setting it to 100ms, and close to 100, and suddenly it can be felt. So this setting is:
System > Languages and input > On-screen keyboard > Android Keyboard (AOSP) > Advanced > Keypress vibration duration (default 0)
I would still suggest to interested developers that the default settings for this phone could be improved: probably by setting the vibration duration at 50ms which can be felt. I’ll follow up on this if someone can recommend the best way to file an issue.
Also compared to other “vibrators” in phones, the Teracube 2e “Emerald” feels relatively weak (I still haven’t tested the vibrating ringer yet because the phone isn’t in active use). If there is any other observations along these lines I would be happy to hear them.
