[Xenial] Some vibrations doesn't works correctly

ubports / ubuntu-touch

A simple and beautiful mobile OS for everyone! This repository is for Ubuntu Touch issue tracking. It does not contain any code used to create Ubuntu Touch.

https://ubports.com

1.28k stars 110 forks source link

[Xenial] Some vibrations doesn't works correctly #736

Open j2g2rp opened 6 years ago

j2g2rp commented 6 years ago

Some vibrations doesn't works correctly at least in M10FHD and BQE4.5

Espected: When touch on an icon of the dash or scopes apps the device should make and small vibration. It also affects to the keyboard of SIM unlock.

Real behaviour: Just vibrates the first time you touch them.

Currently using R108 of devel in M10FHD and R107 on BqE4.5

hummlbach commented 6 years ago

I can confirm that there is no (noticeable) vibration when opening apps from the app scope on mako@devel180714. (While on vivid there is.) @j2g2rp Have you notices the nice bug reporting template that you get when creating new issues? Please use it.

NeoTheThird commented 6 years ago

I'm not so sure, this might also be an intended change... I can't remember any vibration when launching apps on the FP2, bacon, hammerhead and cooler. Alzheimers on my part, or did that actually not happen on some devices?

hummlbach commented 6 years ago

So at least my mako and my turbo both vibrate when launching an app on vivid. But okay, if its intended... also i would consider it not that important in that case. Unfortunately I couldn't yet test whether there is vibration when entering the SIM PIN. In that case we should definitely have the vibration imho.

j2g2rp commented 6 years ago

The only reason that it make me take care about this is because the vibration works just the first time for each case. I thought that maybe something is getting stucked.

@hummlbach sorry. You are right I should use the template.

mymike00 commented 5 years ago

this issue has been discussed also in the forum my experience is that every app emits the haptic effect (vibrates) only for the first button/action pressed and then nothing

mymike00 commented 4 years ago

Digging a bit more into this...

Using Haptics.play() from Ubuntu.Components is affected by this issue docs, source: uchaptics_p.h and uchaptics.cpp (which calls Haptics.qml)
While using HapticsEffect {} from QtFeedback 5.0 isn't affected by this issue (which is what is used in the osk, and that's why vibration on pressing keys works, if enabled in settings ofc) docs

Note: Haptics.qml is using HapticsEffect {} from QtFeedback 5.0 so there must be something broken in the source files mentioned before

kugiigi commented 3 years ago

I can still confirm this as I was checking the camera app. It seems to affect all apps and as mentioned, controls that use Haptics.play()