Could you direct me to the correct conversation, if there is one on why my voice commands can’t be activated for my car. My car says its ‘unavailable at this time’ when I want it to read my messages out loud.
I went into settings and opened up Android Auto to the ‘digital assistant’ section when I click on ‘Manage your digital assistant’, it says ‘unable to open digital assistant settings’. Why and how can I fix it?
Did you search?
You also want to look on the iodé community:
Also:
Short answer is its unclear if you can get it fully functional using the stubs.
If you haven’t installed the stubs you may find this useful also:
None of them seem helpful I have already downloaded all 3 stubs, so don’t know why its still not working.
See my comments in this thread I shared above, and my previous post in same thread:
Have you tried installing FUTO Voice Input? I know that this is for speech input for the phone, but might it allow speaking voice commands into the car to be interpreted by the BraX3 via AA?
Just a wild guess here. I know nothing about AA…
Or if you want to go the other direction and have the phone talk to you through AA, what about trying out RHVoice, SherpaTTS, or Google’s Speech Recognition and Synthesis?
I am about to try this out because…
I currently have SherpaTTS installed (and previously tested RHVoice). Neither of these work reliably and fully with AA with stubs installed. I get some TTS functionality for maps but I haven’t been able to get any STT to work for them (despite SherpaTTS at least reportedly be capable of doing so - I need to test it on phone alone to validate); they seem to be incompatible with the SMS messaging function completely (I haven’t yet tested them with another messaging capability like Molly/Signal). Also haven’t created cyst for STT to find contact for phone call, etc. Until I resolve these I haven’t tried with any other AA functions, as if it can’t do maps & messaging its no use regardless.
Note they also do not show as the digital assistant when installed.
See my latest couple of posts here describing where I am at with testing AA, voice assistant, etc, this last week in more detail:
Try Speech Recognition and Synthesis. However, since it’s a Google product, be sure to lock it down to keep it from phoning home. It doesn’t require logging in in order to work.
Yes - that is my last resort plan, to replace the voice services stub with the proper Google item.
But I will only do that if nothing else works and/or I cant devise a work around. I swore when I first decided to get a degoogled phone I wouldn’t put a single Google app on it no matter what…!
EDIT: P.S. @bqyoung did you only install Google Speech Recognition and Synthesis so had 2 stubs alongside for the other apps (G App and Maps), or did you install all 3 from G?
I haven’t installed SR&S in my BraX3 yet. Installed it in my GrapheneOS phone so that HERE WeGo navigation would read directions to me. Works great for that. I made sure to deny SR&S all permissions.
As I said before, I have no knowledge with Android Auto…yet. You are making me curious about trying my hand at it. I would want to try it out on both the BraX3 and the GOS phone.
GrapheneOS makes AA available in its own app store so I’m comfortable that it is safe enough to use, from a privacy perspective. I don’t know if it is just a stub or the full package. Will just have to experiment with it, I guess
I take a pragmatic view on installing G apps on my phones (all running custom ROMs-no Google Android). If I have a need for functionality that I can’t find in a non-G app AND the G app can be locked down (no or minimal permissions granted), with no need to log into Google, then I am less concerned about installing it.
Besides SR&S, I have installed Pixel Camera and Google Gallery on my GOS phone. All three apps do what I want them to do. Pixel Camera is superb.
Oh, I also installed GBoard because I needed foreign language input that isn’t available elsewhere. But the first thing I did was to deny it network access! I won’t let it be a keylogger for Big G.
And I only switch to GBoard when I need to type in that language. Otherwise, I use a pretty sweet Heliboard configuration.
Yeah AA itself is fairly benign I believe - it doesn’t seem to try and connect to anything and other than needing the permissions to work (microphone, contacts, location, etc) there’s no obvious sign (e.g. in iodé app) that it’s doing anything else in the background. It’s those other 3; G App, Maps and Speech Recognition & Synthesis that will be the nefarious ones…
Yeah I’m comfortable, to a degree with at approach too, but it needs to be the last resort - if something else can do 90%-95% and I can work around the gap, then I don’t want to consider a G app just to avoid that 5% workaround or whatever…
I was curious if you could get PC to work on a non-Pixel handset? I have the impression you can’t - but if it’s ever doable would love to try it on a Brax3… With the usual caveats about making sure it’s not phoning home or similar…
P.S. Had a strange experience today in my Mazda - if I disable Bluetooth in the car unit, it won’t allow Android Auto to run/connect even if I’m using USB (which I always do). i.e. to run AA over USB you have to have Bluetooth on in the car head unit… Now why would that be???
In another thread, the Gcam project was mentioned. I dabbled a bit by installing one of the builds on my BraX3, but it wasn’t ready for primetime. Could get the rear camera to work but not the selfie camera. I uninstalled it and went back to OpenCamera.
You might want to check out the GOS user discussions about AA. Perhaps there are some useful insights over there.
In general, a lot of what I learned using GrapheneOS is directly applicable to using my BraX3.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.