I "think" I found the culprit. http://bazaar.launchpad.net/~phablet-team/platform-api/trunk/view/331/src/ubuntu/application/common/application/sensors/service.cpp#L84
It seems the old feedback plugin was async (see https://code.launchpad.net/~kalikiana/qtubuntu-sensors/feedback/+merge/183456 with https://code.launchpad.net/~kalikiana/qtubuntu-sensors/feedback/+merge/183456/comments/431467 and the reply https://code.launchpad.net/~kalikiana/qtubuntu-sensors/feedback/+merge/183456/comments/431975 )
while the new one is using synchronous dbus calls. http://bazaar.launchpad.net/~phablet-team/platform-api/trunk/view/331/src/ubuntu/application/common/application/sensors/service.cpp#L84
For some reason it seems the dbus service in my case stopped responding to the requests to enable the vibrator, and that was causing the UI thread to block waiting on a reply on dbus.
I "think" I found the culprit. bazaar. launchpad. net/~phablet- team/platform- api/trunk/ view/331/ src/ubuntu/ application/ common/ application/ sensors/ service. cpp#L84
http://
It seems the old feedback plugin was async (see https:/ /code.launchpad .net/~kalikiana /qtubuntu- sensors/ feedback/ +merge/ 183456 with https:/ /code.launchpad .net/~kalikiana /qtubuntu- sensors/ feedback/ +merge/ 183456/ comments/ 431467 and the reply https:/ /code.launchpad .net/~kalikiana /qtubuntu- sensors/ feedback/ +merge/ 183456/ comments/ 431975 )
while the new one is using synchronous dbus calls. bazaar. launchpad. net/~phablet- team/platform- api/trunk/ view/331/ src/ubuntu/ application/ common/ application/ sensors/ service. cpp#L84
http://
For some reason it seems the dbus service in my case stopped responding to the requests to enable the vibrator, and that was causing the UI thread to block waiting on a reply on dbus.