This allows you to use the touch wheel for quick playback control: - bottom quadrant for play/pause - left and right quadrant for track skip back / forward - top quadrant to seek back 25 seconds (handy when listening to a podcast)
Splits the control scheme into separate schemes for the side buttons and touchwheel, allowing them to be configured independently of each other. At least one input must be used for navigation, and there are guards to prevent locking oneself out of any input. If the input scheme is invalid, a pop up will show alerting the user. Different behaviours can be bound to the side buttons for when the device is locked or unlocked. This PR also adds a mode for these buttons that controls media playback (prev/next on up/down, pressing both buttons toggles play/pause). There are some changes to the way inputs handle locking. Rather than the input devices tracking the current locked mode, different input devices are created on lock depending on the mode that is configured. Reviewed-on: https://codeberg.org/cool-tech-zone/tangara-fw/pulls/264 Co-authored-by: ailurux <ailurux@noreply.codeberg.org> Co-committed-by: ailurux <ailurux@noreply.codeberg.org>
Reviewed-on: https://codeberg.org/cool-tech-zone/tangara-fw/pulls/302
Prior to this change, the UI thread was consuming approx. 10-14% CPU in the idle state, and appeared to be running in an endless loop. After this change, the UI thread is measured at about 0.1% CPU. I'm not sure what the current consumption impact is, but it's gotta be a power saving, even if slim? Following manual testing with the device after flashing this change, the UI responsiveness and music playback does not appear to be negatively affected. The UI actions that were tested were: - Scrolling through items on the root menu - Scrolling through settings - Scrolling through All Tracks with long-press on the bottom of the scroll wheel (Page Down) on a device with ~20k songs - Repeatedly hitting 'next track' - Forcing a DB update, and scrolling through All Tracks while updating the database. The device was configured with the following settings when tested: - TTS enabled - Wired headphones - Bluetooth enabled but not connected - No DB auto-update - Playing music Prior to this change, the UI thread was consuming approx. 10-14% CPU in the idle state, and appeared to be running in an endless loop. On a stock (v1.2.2) build, `tasks` reported: ``` → tasks name core free stack run time IDLE1 1 1.0 KiB 99.6% IDLE0 0 1.1 KiB 86.5% ui any 10.1 KiB 13.7% console_repl 1 5.6 KiB 0.5% Tmr Svc any 1.4 KiB 0.0% audio_dec any 19.4 KiB 0.0% main 0 2.0 KiB 0.0% lvglDraw any 2.9 KiB 0.0% btController 0 2.1 KiB 0.0% esp_timer 0 3.4 KiB 0.0% BTC_TASK 1 2.6 KiB 0.0% worker_1 any 30.1 KiB 0.0% worker_3 any 5.7 KiB 0.0% worker_2 any 29.5 KiB 0.0% worker_0 any 25.7 KiB 0.0% BTU_TASK 1 3.2 KiB 0.0% hciT 1 1.5 KiB 0.0% ipc0 0 1.0 KiB 0.0% ipc1 1 1.0 KiB 0.0% audio_conv any 3.4 KiB 0.0% ``` Following this change, the UI thread decreased from 13% in idle to 0.1% usage, as reported by `tasks`: ``` → tasks name core free stack run time IDLE1 1 1.0 KiB 99.8% IDLE0 0 1.1 KiB 99.4% console_repl any 6.4 KiB 0.5% ui any 10.1 KiB 0.1% btController 0 2.1 KiB 0.0% Tmr Svc any 1.4 KiB 0.0% esp_timer 0 3.4 KiB 0.0% audio_dec any 19.4 KiB 0.0% ipc1 1 1.0 KiB 0.0% ipc0 0 1.0 KiB 0.0% hciT 1 1.5 KiB 0.0% BTU_TASK 1 3.2 KiB 0.0% worker_3 any 20.7 KiB 0.0% worker_2 any 29.4 KiB 0.0% BTC_TASK 1 2.5 KiB 0.0% worker_1 any 30.1 KiB 0.0% worker_0 any 5.7 KiB 0.0% lvglDraw any 2.9 KiB 0.0% main 0 2.0 KiB 0.0% audio_conv any 3.4 KiB 0.0% ```
This change introduces the ability to enable or disable the spoken interface/TTS from the on-device settings, either via the UI or the Lua console. This closes out the implementation of issue #245. The TTS setting is only visible in Display settings if voice samples are present in `/.tangara-tts/` on the SD card. Playback of new TTS voice samples is inhibited when TTS is disabled. By default, the setting is enabled, as the device will only play back TTS voices if samples are present on disk. If you need samples to test TTS on your device, feel free to grab the voice samples I have at https://codeberg.org/tursiae/tangara-tts-samples. There's about 80-85% coverage of the UI, with the remainder to be added soonish. Reviewed-on: https://codeberg.org/cool-tech-zone/tangara-fw/pulls/251 Co-authored-by: Tursiae <git@tursiae.org> Co-committed-by: Tursiae <git@tursiae.org>
This adds a way for feedback devices to respond to events from outside of LVGL's event system, being passed from input device to feedback device through a vector. This was done so that touch events and long-press triggers can now give feedback through haptics. This PR also adds haptic modes, saved in nvs similarly to input and locked input modes, to disable or change the haptic effect behaviour based on which mode is selected. Finally, this also fixes a bug in which some click events would not trigger haptics, at the expense of re-introducing the (undesired?) behaviour of clicking a button that transitions to a new screen causing a double click. Relevant issues this should close: #195, #233, and (partially?) #120 Reviewed-on: https://codeberg.org/cool-tech-zone/tangara-fw/pulls/246 Co-authored-by: ailurux <ailuruxx@gmail.com> Co-committed-by: ailurux <ailuruxx@gmail.com>
This adds a new Controls setting for adjusting the behavior when locked, and an option for allowing volume control.