App Version
3.3.1
Platform
How you installed it
Google Play
What happened?
When Conduit is configured as the default Android digital assistant with the setting to trigger a "Voice Call" upon activation, the behavior differs depending on whether the app is already running in the background:
- App already running (Warm Start): Triggering the assistant correctly and immediately starts the Voice Call overlay.
- App completely closed (Cold Start): Triggering the assistant fails to start the Voice Call. Instead, Conduit falls back to opening the standard Text Chat interface.
This seems to be a timing/initialization race condition. During a cold start, the app is busy initializing (loading secure credentials, establishing the WebSocket connection to Open WebUI), causing the voice-call intent to fail or time out before the connection is ready, leading to the text-chat fallback.
Additional Context:
- Device: Samsung Galaxy S26 Ultra.
- Manual voice calls from within the active app work flawlessly.
- Giving Conduit "Unrestricted" battery usage permissions did not resolve the cold start issue.
What should have happened?
The digital assistant should consistently trigger the Voice Call interface, even during a cold start (perhaps by showing a brief loading/connecting state until the WebSocket/session is established, instead of immediately falling back to text chat).
How to reproduce
- In Conduit Android digital assistant settings, enable "Start a voice call".
- Set Conduit as the default Digital Assistant app in Android system settings.
- Close Conduit completely (swipe it away from the recent apps / force stop).
- Trigger the digital assistant (e.g., via power button long-press or swipe shortcut).
- Observed Behavior: The app starts up but only opens the regular Text Chat.
- Now, leave the app running in the background (press Home button).
- Trigger the assistant again.
- Observed Behavior: The Voice Call interface opens successfully.
Does this happen every time?
Yes.
When did this start?
I noticed it today.
Screenshots
No response
Logs
No response
App Version
3.3.1
Platform
How you installed it
Google Play
What happened?
When Conduit is configured as the default Android digital assistant with the setting to trigger a "Voice Call" upon activation, the behavior differs depending on whether the app is already running in the background:
This seems to be a timing/initialization race condition. During a cold start, the app is busy initializing (loading secure credentials, establishing the WebSocket connection to Open WebUI), causing the voice-call intent to fail or time out before the connection is ready, leading to the text-chat fallback.
Additional Context:
What should have happened?
The digital assistant should consistently trigger the Voice Call interface, even during a cold start (perhaps by showing a brief loading/connecting state until the WebSocket/session is established, instead of immediately falling back to text chat).
How to reproduce
Does this happen every time?
Yes.
When did this start?
I noticed it today.
Screenshots
No response
Logs
No response