[4.3] Vibration in applications (including Hardware tests) does not work

Bug Reports
, ,
#1

REPRODUCIBILITY (% or how often): 100
BUILD ID = OS VERSION (Settings > About product): 4.3.0.12 —> 4.5.0.19
HARDWARE (XA2, X10, X10 II, …): X10 II
UI LANGUAGE: Russian
REGRESSION: (compared to previous public release: Yes, No, ?): Yes

DESCRIPTION:

Vibration in applications (including Hardware tests) does not work, If Settings - Sounds, etc. - Touchscreen vibration off
There is vibration when there is an incoming call.

PRECONDITIONS:

Settings - Sounds, etc. - Touchscreen vibration off

STEPS TO REPRODUCE:

  1. Settings
  2. Sounds, etc
  3. Touchscreen vibration off

EXPECTED RESULT:

Vibration in applications (including Hardware tests) does work

ACTUAL RESULT:

Vibration in applications (including Hardware tests) does not work.

ADDITIONAL INFORMATION:

When there is an incoming call, there is vibration, there is no vibration in applications, incl. android.

4 Likes
[Release notes] Sauna 4.6.0.11
[Release notes] Sauna 4.6.0.13
#2

Yep, seeing the same. I thought it was normal that I had to re-toggle “Touchscreen vibration ON”, but glad to see this might be a bug. I would rather not have vibration on keyboard typing.

#3

Same here. I have a home automation suite of 16 buttons over 2 pages, each button has vibration settings. I didn’t realise the vibration had stopped after upgrading to 4.3. As mentioned above, I also don’t care for keyboard keys vibrating when pushed.

#4

Vibrations are still broken on SFOS 4.5.0.19 on my Xperia X.

It seems that all vibrations triggered from QML are broken with the “Touchscreen vibration” setting off. Other vibrations still work (e.g. when the phone is ringing or triggered by an alarm / calendar reminder).

For example, each key press on the keyboard spams a Sailfish invoker[26873]: WARNING: Effect failed, id 1462 in the system log (journalctl --follow shows this nicely). The same message happens for apps that trigger vibrations from QML: Sailfish harbour-minidoro[24191]: [W] unknown:0 - Effect failed, id 1 for Minidoro, and Sailfish harbour-vibration[23330]: [W] unknown:0 - Effect failed, id 4 for VibrationTest.

This is clearly a regression at least compared to SFOS <= 3.4 (I didn’t test it on 4.0 through 4.4). On SFOS 3.4, the setting disabled haptic feedback in the pulley menu and from key presses, which is what I would expect from the setting.

It should however not affect any apps that use vibrations. Especially since the QtFeedback 5.0 API with ThemeEffect is allowed in Harbour. It breaks apps that rely on vibrations for notifying the user in quiet places like a library, e.g. Minidoro.

2 Likes
#5

I can confirm that this Problem is present in 4.4.0.72/Xperia10iii as well. Journal is spammd by the messages, here triggered mainly by literm

#6

I reported this bug in Jolla Bugzilla.

2 Likes
#7

Should now work better with
[libngf-qt] Use different feedback event for non-touch haptics. JB#60638 by pvuorela · Pull Request #7 · sailfishos/libngf-qt · GitHub + configuration introducing such a new haptic event.

#8

Fixed on Sailfish OS 4.6.0. Can we close this bug report?
@zuyev @ichthyosaurus

#9

I didn’t dare to update my main phone to 4.6 yet, so I can’t confirm if it works.

#10

I had recently updated the 10iii and went looking for the configuration. My understanding had always been that there was a global disable which served me well. If I understand correctly, now one can set general system setting to off but leave it to apps to use haptic feedback? Didn’t find a setting in Sounds and Feedback.

#11

No, the first item in the sound settings page for haptics is the main switch. There’s later in the page also “touch screen feedback” which should be controlling whether user interaction, pulley menu and such, does vibra.

The bug that was fixed here was that the latter option was preventing applications from doing generic vibra while it should be just the main switch.

#12

Ok, Got it:

Vibration: Never
Touch screen vibration: On

Yields vibration only in apps that explicitly use feedback?

#13

Vibration: never is main switch turned off. You won’t get vibra anywhere.

#14

So, I don’t get it. What’s the point? If I want to turn off generic vibration foo (I don’t want phone call vibration) but allow my own apps to have haptic feedback, I can’t? That is counter intuitive to say the least. Also doesn’t make sense to show an option as enabled when a previous option disables it entirely. The option should not even be choosable at that point.

#15

We have some shortcomings like that on the current vibra settings. We should allow to control e.g. the incoming call vibra better without requiring to touch the main switch. Hope I’ll get something done there soon enough.

2 Likes
#16

Ok, thanks for clarifying.