Develop
Ticket #1677 (closed enhancement: fixed)
Allow configuration of haptic feedback (vibrate)
| Reported by: | Turbo | Owned by: | hjr |
|---|---|---|---|
| Priority: | normal | Milestone: | XCSoar Manual |
| Component: | Other | Version: | 6.3 |
| Keywords: | manual | Cc: |
Description
Make the device vibration on Android configurable
Change History
comment:2 Changed 17 months ago by apf
- Summary changed from Vibration configurable to Allow configuration of haptic feedback (vibrate)
comment:4 Changed 17 months ago by Turbo
first part implemented, "default" setting not operational yet
comment:5 Changed 16 months ago by apf
- Status changed from accepted to closed
- Resolution set to fixed
Remaining part implemented with 700c42ac3c1afa83cd6bb3683e9c244776dc26a6.
comment:6 Changed 14 months ago by hjr
- Keywords manual added
- Status changed from closed to reopened
- Version set to 6.3
- Resolution fixed deleted
- Milestone changed from XCSoar 6.3 to XCSoar Manual
manual update
Note: See
TracTickets for help on using
tickets.
Result of the irc discussion is that we should implement a tri-state setting (Default/Off/On?). Default follows the OS setting (if available). The main argument for the additional ON/OFF settings is that the xcsoar use case is sufficiently different (e.g. it is operated in flight conditions) that simply following the OS configuration is not enough (e.g. a user might vibration disabled for normal apps but enabled under the conditions xcsoar is used).