comparison FC-handset-spec @ 57:020e6428c248

FC-handset-spec: firmware approach to vibrating alert documented
author Mychaela Falconia <falcon@freecalypso.org>
date Sun, 13 Jun 2021 02:22:25 +0000
parents a39269dddca4
children e6a1d1699ebb
comparison
equal deleted inserted replaced
56:a39269dddca4 57:020e6428c248
1218 be used for both hands-free calls and ringing, logically the two are separate 1218 be used for both hands-free calls and ringing, logically the two are separate
1219 modes, and they will be treated as separate for the Audio Service. Separate 1219 modes, and they will be treated as separate for the Audio Service. Separate
1220 logical modes will provide separate volume files, which is the correct approach: 1220 logical modes will provide separate volume files, which is the correct approach:
1221 loudspeaker volume and ringing volume should be separate, just like how ringing 1221 loudspeaker volume and ringing volume should be separate, just like how ringing
1222 volume is entirely separate when a buzzer is used. 1222 volume is entirely separate when a buzzer is used.
1223
1224 2.5. Vibrating alert
1225
1226 Our FC handset firmware will support both ringing and vibrating alert modes (as
1227 well as a ring+vibrate mode) on all targets. The vibrator will be modeled as a
1228 simple on/off control (no "analog" control of different vibration intensity
1229 levels, at least initially), and the vibrating alert code path will ultimately
1230 boil down to a driver function call for vibrator on/off. Therefore, if the
1231 vibrator does not exist on a given target, or if it exists but we don't know how
1232 to operate it, the on/off control function can be empty on that target, and the
1233 firmware will "vibrate" virtually.
1234
1235 On development boards such as FC Venus, the vibrator on/off function can turn a
1236 LED on and off to provide an indication of the UI layers making a vibrating
1237 alert.