tl;dr it was a system tts problem not a kurviger problem
I’m not sure exactly when I noticed this, but I think sometime in mid-December my voice prompts stopped playing. I thought it was weird bluetooth issues or a setting I’d changed accidentally but I have now cleared storage/cleared cache/reinstalled the whole app and still no audio
What I did
- delete Kurviger app
- reinstall from Play Store
- choose to refuse cookies (don’t know if this is relevant)
- change “Address service provider” to OpenRouteService
- create a route from my house to a short distance away
- login as me with Tourer+ credentials to enable navigation
- turn the volume up on my phone
- start navigating by pressing the arrow icon and then “Start navigation” on the menu that pops up at the bottom
What I expected to happen
- to hear a prompt such as “let’s go” or “in 150 metres turn right”
What happened
- (sometimes, not every time) the default android notification chime
- no other sound prompts
I have tried:
- that the bluetooth helmet speaker works ok with other apps (it plays music just fine)
- with bluetooth disabled so audio should go to the phone speaker
- all three Voice Output Channels
- disabling and re-enabling “Speak voice instructions” in settings
- disabling and re-enabling “Unmuted” in the three-dots popup during navigation
- unchecking and checking “Speak voice instructions” checkbox in the pull-out tray thing that contains “Start Navigation” and “Simulate navigation” and other options
I’m stuck for ideas. I can capture a logcat if that helps? It’s so full of noise I can’t tell what’s important or relevant though
[ Secondary question: are voice prompts supposed to be played in simulation? It doesn’t work there either but I don’t know if it’s intended to. It’s cold and dark outside, it would be great if they did ]
OSM date stamp: 18/02/2025
Version: 3.5.4
Device: OnePlus - ONEPLUS A6013 - Android 13 - WebView 119.0.6045.134
App-Version: 3.5.4-4515
Screen: 384 x 823 px - 2.8125ppx
Solution: After writing the followup post about Lineageos’s (lack of) harsh battery management I realised I hadn’t checked that the system-level text-to-speech was working, and indeed it wasn’t. For posterity:
- I went to System → Languages and inputs → Speech → Text-to-speech output and the “Play” button was greyed out,
- I clicked the settings cog next to “Preferred engine: espeak” and then on “Import eSpeak dictionary”
- there were no dictionaries listed to install in the dropdown, but I pressed OK anyway
- pressed back button to return to “Text-to-speech output” page
- now the formerly greyed-out options are enabled and I can hear speech when I press Play
It used to work, I don’t know why it stopped, but now it works again and I can stop looking down all the time to see the route while riding along at 100km/h 