Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Voice assistant usage causes navigation problems/lockups #695

Open
SonOfGib opened this issue Jan 4, 2025 · 6 comments
Open

Voice assistant usage causes navigation problems/lockups #695

SonOfGib opened this issue Jan 4, 2025 · 6 comments
Assignees
Labels
bug Something isn't working

Comments

@SonOfGib
Copy link
Contributor

SonOfGib commented Jan 4, 2025

Steps to reproduce the bug, if you're planning to report a bug. Please indicate whether the bug is always repoducible.

Use the voice assistant to do stuff (requesting directions seems to trigger it readily.) Then attempt to do any action that requires the control channel (such as starting navigation, or exiting AA etc.) These actions will fail or cause crankshaft to lock up.

Please provide any further information that you might find helpful if available.

This issue was originally reported by @Geekyadz and @TobiasDeBruijn
Duplicates #690

@SonOfGib SonOfGib added the bug Something isn't working label Jan 4, 2025
@SonOfGib SonOfGib self-assigned this Jan 4, 2025
@SonOfGib
Copy link
Contributor Author

SonOfGib commented Jan 4, 2025

I finally ran into this and was able to track it down, I'll make a fix for it in openauto

@SonOfGib SonOfGib linked a pull request Jan 4, 2025 that will close this issue
@SonOfGib
Copy link
Contributor Author

This should be fixed with pre-release https://github.com/opencardev/crankshaft/releases/tag/20250111

@DJFliX
Copy link

DJFliX commented Jan 21, 2025

Hey! I think I'm running into this issue on 20250111 on a Pi 4. I'm seeing both Google Maps and Tomtom navigation triggering a lock-up of crankshaft. While crankshaft is locked I do often see my phone reconnecting to AA (due to the brief black flash on my phone screen which indicates AA is starting). I recall that in old builds a crash of AA (or a disconnect for that matter) would result in me being thrown back into the crankshaft menu and the ability to reconnect after a few seconds. Should I create two separate issues?

@SonOfGib
Copy link
Contributor Author

SonOfGib commented Jan 22, 2025

Sounds like it could be a different issue to me, but if you can attach a log file I'll take a look at it. I haven't experienced any crashes while using maps personally.

@DJFliX
Copy link

DJFliX commented Jan 23, 2025

@SonOfGib I thought I had enabled debug logging but it turns out the only logs I can find on my SD card are the ones generated by me pressing the "generate logs" button. How can I generate logs when the UI is frozen? Disconnecting the phone doesn't change anything: the screen remains frozen.

@SonOfGib
Copy link
Contributor Author

SonOfGib commented Jan 24, 2025

Yeah I think in that case there probably isn't a way to get it to export the log file for you. Something we can improve hopefully. If you are able to ssh into the pi you can grab the files manually

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants