Ubuntu
platform-api package

platform-api shouldn't try to use vibrator if not available

Bug #1334312 reported by Ricardo Salveti
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
platform-api (Ubuntu)
Confirmed
Medium
Unassigned
usensord (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Currently on flo I get the following message every time someone calls the vibrate function:
com.canonical.usensord.Error: open /sys/class/timed_output/vibrator/enable: no such file or directory

That's basically because there's no vibrator hardware/driver available for flo. Platform-api should be smart enough to not use it if not available.

Sergio Schvezov (sergiusens)
Changed in platform-api (Ubuntu):
status: New → Confirmed
Changed in usensord (Ubuntu):
status: New → Confirmed
Changed in platform-api (Ubuntu):
importance: Undecided → Medium
Changed in usensord (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Oliver Grawert (ogra) wrote :

i think this bug should be higher prio ... it makes application logs grow quite a bit ...

Revision history for this message
Randy Olive (randy-jr-olive) wrote :

I have the same issue running Delivery Tracker on my Nexus 7.

com.canonical.usensord.Error: open /sys/class/timed_output/vibrator/enable: no such file or directory

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.