See these posts - you’ll have likely already see some of them - I have removed superfluous comments from the quotes. Also I haven’t compiled a detailed chart of the issues, but if you go through those posts you’ll see I’ve covered a pretty comprehensive spread of all the standard things you’d want to use and functions you’d want available. But as I have said previously I’m not an expert with Android, so there might be some settings or such I am missing at a deep level in the OS - but I do think that’s unlikely.
25 September 2025 (from BraxTech Forum)
2 October 2025
So I thought I’d follow up her on my Android Auto install, as I’m continuing to have issues and while in theory it works it isn’t fully usable. My suspicion is its something to do with permissions and settings, and/or possibly some FOSS apps just don’t like it?
- Car is 2018 Mazda (and Car Play with iPhone worked perfectly in it FWIW)
- I have got hold of a reasonable stock android (Samsung) to test it with over weekend - as I have never used android with it previously just to verify it works as expected in that scenario - and to then compare any settings that are user accessible.
- I can play podcasts (Antennapod) and also do basic map navigation (Organic Maps and to some degree OsmAnd) and some basic navigation round the other Apps on AA screen.
However issues are:
- Anytime a SMS message arrives the overlay pops up, playing media pauses, but whole screen locks up and doesn’t respond to nav controls from car (e.g. main selector when pressed to ‘play message’). Maybe it’s permission to overlay other apps issue or something to do with Serpa TTS?
- When i try to initiate an SMS the SMS icon in AA implies there is no SMS Message app (for some reason it doesn’t show Fossify Messages, just a generic SMS app).
- I managed to get into a new message screen once but again it immediately locked up the screen and stopped responding.
- Opening the phone app to make a call works but then it’s just either empty (no contacts) or it locks up.
- It also doesn’t respond to a couple of the basic nav control buttons even when working okay (e.g. the ‘back’ button to return to previous screen).
And others… (I haven’t got to trying out a music player yet).
But the majority of them seem to me like it’s permissions or settings and/or it doesn’t like certain apps perhaps? But I have trawled through them several times to try and find anything that might be related.
e.g. Messages seem to lock it up when the overlay pops up (which happens whenever there is a notification), but messages app has no setting for being allowed to overlay over another app. However Android Auto does and it’s on, and when a message alert arrives it doesn’t play the messages unique notification sound, it plays the Android Auto general notification sound.
…At this stage I plan to try and fully test a stock android as mentioned to verify the unit behaves as you would actually expect and there are no idiosyncrasies because it’s a Mazda, etc… and then spend the weekend trying to work through all the settings in AA, then anything related (incl. the key apps) to try and see if changing anything that looks vaguely related makes a difference…
3 October 2025
…Further to the above with regard to SMS:
- Fossify Messages (default app) is now showing some received messages in Android Auto SMS function - however it reports no voice services available to read message, or when you try and create a new message.
- I had temporarily set Android Auto to Always On in Start Android Auto automatically a few days ago to see if that helped, but I changed it back to the default setting of Default (Set by Vehicle) today and so I presume that has allowed SMS to work better connecting with Fossify Messages. I had originally changed it to test if there were some hidden permissions behind this setting, …so might help with [some of] the original issues I had.
- However new message notifications that appear still freeze the screen - I presume because of the same can’t find voice services error?
- I have SherpaTTS installed, but obviously it can’t see that or doesn’t like it. So is that suggesting you HAVE to install the Google Voice Services instead of the stub for it to work?
- I am also not sure if its due to having no digital assistant installed? What functions does the “Digital Assistant” actually provide - that aren’t covered by having TTS / STT engines/apps? Will AA not be fully functional without one?
I was going to try a different messages app but am now pretty sure it’s AA and settings related not app. Can AA not manage SMS and similar tasks without the proprietary Google Voice Services installed?
EDIT: I have successfully completed basic voice calling tests both in and out. Generally worked okay other than audio quality through car speakers (phone connected by USB) was pretty average at best [EDIT: with BraX3].
Still need to test OsmAnd maps more thoroughly and there are some other quirks and bugginess navigating apps and functions to be resolved (on top of the SMS issue above).
P.S.
It also doesn’t respond to a couple of the basic nav control buttons…
This has improved with reverting back to the Default (Set by Vehicle) option mentioned above.
4 October 2025 (from BraxTech Forum)
Have you tried installing FUTO Voice Input?
I am about to try this out because…
what about trying out RHVoice, SherpaTTS
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 test for STT to find contact for phone call, etc. Until I resolve these I haven’t tried [in detail] 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.
4 October 2025
So I have installed FUTO Voice (but not FUTO Keyboard) to see if that helps - but have been unsuccessful - that too seems to be unable to operate inside Android Auto.
- Fossify Messages (default app) is now showing some received messages in Android Auto SMS function - however it reports no voice services available to read message, or when you try and create a new message.
No change with FUTO Voice. Still can’t initiate a new message via SMS app in Android Auto.
Also via Molly (Signal) in Android Auto there isn’t even an option for initiating new messages.
- However new message notifications that appear still freeze the screen - I presume because of the same can’t find voice services error?
This still happens.
- I am also not sure if its due to having no digital assistant installed? What functions does the “Digital Assistant” actually provide - that aren’t covered by having TTS / STT engines/apps? Will AA not be fully functional without one?
AA steadfastly continues to not recognise anything as the Digital Assistant, even FUTO Voice [EDIT: so clearly TTS/STT app is not what it’s looking for here].
- I have SherpaTTS installed, but obviously it can’t see that or doesn’t like it. So is that suggesting you HAVE to install the Google Voice Services instead of the stub for it to work?
Looking very unfortunately like I am going to have to install Google Speech Recognition & Synthesis and just lock it down as tight as possible. Hopefully I can retain the other 2 stubs to minimise the G apps on device… Will try a few more tweaks and things but if no joy will go this route tomorrow…
![]()
Still need to test OsmAnd maps more thoroughly and there are some other quirks and bugginess…
OsmAnd still proving slightly buggy; and there’s some other odd issues with navigation around AA locking up still…
On a positive note Musicolet works really well, and in AA as well as on phone [EDIT: but still subject to the freezes caused by notifications and SMS].
7 October 2025
oldguychuck:
Does this mean you can tap the microphone icon in your display and execute a command? Like “Call xxxx”. And In apps as you tap on a search field, see a microphone icon so you can use voice entry?
Yes - although you can’t tap the screen literally as that’s disabled in moving vehicles for safety - but yep, via the car nav controls (in my case in the Mazda it’s a large dial know that also does 4-way tilts, and push to ‘enter’ to navigate the system screen).
…Android Auto in iodéOS with stubs …constantly crashes or stops working for no reason, I unplugged and replugged in something like 7 times on my way to work this morning before I got a stable connection that kept the AntennaPod app podcast playing for the remainder of my journey…
My car’s Android Auto has this annoying thing that the phone must connect to the car via Bluetooth as well as USB for AA to work - it won’t run on USB if you don’t have a BT connection…
Am getting close to putting G Voice App in instead of Stub, but really don’t want to… and no point if AA is unstable for other reasons.
9 October 2025
@rik just in no particular order - here are some findings I did on my car this morning (as I had some time to play around for a little bit):
Devices
This is what I used for testing:
- 2018 model Mazda 6 (‘Atenza’ if outside ANZ).
- iPhone 12 Pro Max (my daily phone for 4½+ years until 2-3 weeks ago - no SIM, but connected to Wi-Fi),
- Samsung Galaxy A34 5G stock android (so a 2023 model - unit is a company phone from recent employee who left so was in daily use up until a few weeks ago - tested with no SIM & no Wi-Fi),
- BraX3 Privacy Phone (2 SIMs & Wi-Fi connected).
- Standard official Apple USB-A to Lightning Cable as supplied with previous Apple devices (from one of my prior iPhone’s, have used same cable in car for 5 years - in as new condition),
- BraX USB-A to USB-C cable supplied with the phone (essentially new - this is what I have been using to connect BraX3 to car),
- Momax (supposedly) High Quality USB-A to USB-C cable (this is what I regularly use to connect devices to my PC, including the BraX3. Not sure of official spec but think it’s USB 3.1 otherwise 3.0 - gets limited to use so in as new condition).
Bluetooth
My Mazda happily connects with my iPhone 12 Pro Max via USB for Car Play, with the Bluetooth disabled in the car unit. You have full functionality of everything and it all works. I connected via the usual cable I have used for the last 5+ years.However the car will not allow an Android Auto connection to USB without Bluetooth enabled and the phone paired to Bluetooth, along with the USB connection. It does this for any connection regardless of the device. So I can only assume this is standard behaviour …for an Android Auto unit.
Functionality
As an aside I noted Organic Maps does not work with Siri on iPhone, so no voice input in Car Play - I had forgotten about this.On the Samsung Galaxy A34 phone I found it reported errors with some functions - particularly when trying to get things ‘read out’ by the digital assistant. My best guess is it is because of no internet connection, so it can’t phone home to G so has no way to do anything? Maybe? As soon as I can I will connect it to wi-fi and quickly retest. You could browse message histories, and other things you can’t on BraX3 with iodé.
BraX3 continued to show all the usual functionality issues I have previously raised - and this didn’t change regardless of which USB-A to USB-C cable I used. AA repeatably locks up and comes unresponsive - often as soon as you start media playing, or if you manage to manually initiate a phone call from your contacts. Won’t show any SMS or similar (e.g. Molly or Signal) message history (so screen blank) and won’t initiate a new message when you click on that function’s icon…
Cables
So no problem with iPhone and the USB-A to Lightning Cable, as expected - as I have used this for several years.Also no problem connectivity wise with BraX3 - it worked fine with both USB-A to USB-C cables (the BraX one and the Momax one).
9 October 2025
[quote=“mycenius, post:22, topic:6860, full:true”]
On the Samsung Galaxy A34 phone I found it reported errors with some functions - particularly when trying to get things ‘read out’ by the digital assistant. My best guess is it is because of no internet connection, so it can’t phone home to G so has no way to do anything? Maybe? As soon as I can I will connect it to wi-fi and quickly retest.
@rik a further update. Bear in mind with what I say here this is just what I found and I may have missed something that changes things - but anyway… Connected A34 to wi-fi and tested - partial functionality (e.g. it would read out the weather). So definitely needed internet to for digital assistant to work at all, HOWEVER…
…it still wouldn’t work for reading out SMS messages, nor could I get any STT working. In fact for the former (just to read out text messages) it said you needed to go into Digital Assistant Settings and allow personal items, but when I tried to do that on the phone (in settings) it said no connection available - despite having an active connection to the internet. It was clearly trying to launch something (plain grey/silver page - my suspicion is a webpage with the frame/border disabled) - presumably from Google server. So…
My conclusion is it’s trying to access something in your Google Account online where the Digital Assistant Settings and Permissions, and possible dictionary and similar, are stored. Forcing you to have an active signed in connection to use it. Or at least to set it up. BUT that still leaves me stumped over people who say they have used the Google Apps, but not signed in and locked them down with no internet access - including [Google] maps - so I can only assume they are not using any TTS (except perhaps for map directions) and especially no STT at all?
So at this stage my summary is (and probably needs more testing by someone else with a more technical knowledge of Android than I do to confirm these assumptions) that for Google Digital Assistant (incl. Google Speech Recognition & Synthesis app) to work it needs:
- An active internet connection (it may do some things offline, but initial set up and some functions, like some TTS and especially all STT, will always need it, it seems) - this is probably due to both the device alone won’t have the processor grunt to do all the speech processing work, but also #2 below,
- It would seem it needs you to be actively logged into a Google Account on the device (or something akin to this) - otherwise it can’t access key things like your personal settings and permissions, and language dictionaries and whatever… While some of this may be for valid technical reasons it’s likely also a hook to ensure you can never use it offline, and without being connected to G, for tracking purposes. I can’t see any other reason for the result I repeatedly saw this afternoon with it trying to open a page and saying no connection available.
- It needs some unique features that some apps (FOSS, etc) will probably never have so won’t work with it regardless. Likely because they don’t have the necessary included functionality; and/or lack some sort of proprietary code or connectivity built in - similar to how Organic Maps in iOS has no option for STT input. Most map apps have some TTS support it seems, even if via third party TTS, but that’s all you will get (I’d suspect like iOS in Android G DA just won’t work regardless as TTS with open source maps apps).
![]()
So, in conclusion, basically you won’t get STT functionality, so no voice search functions in maps, phone contacts and similar, no sending SMS messages by voice (or reading them), etc. I think in all reality it may require someone backwards engineering the whole thing and how it works, and fully developing something to talk to the AA units in vehicles - and that may be a challenge if there is some proprietary stuff in there (let alone the time and effort involved).
![]()
My last thing will be to remove the voice stub(s) and try Google Speech Recognition & Synthesis - mostly to see if I can get FOSS maps working better, and possibly installing base Google App (I believe it’s got G Search built in as part of the functionality for AA) makes basic phone calls work and other apps work and the apps and screen navigation more stable - if not then it’s likely FOSS type apps just aren’t going to work with it full stop.
![]()
=============================================
EDIT: Adding this here as I am currently at my 3 consecutive posts limit on this thread.
@rik just a further quick update - continue to have ongoing problems with AA with just basic stuff (playing music or podcasts). Intermittently get errors on connection, probably about a third of the time and sometimes requires 3 or more connection attempts (with USB cable) for AA to start correctly - some of the failed attempts result in a red AA Connection Failure warning screen on the phone. When it does connect about another third of the times it starts playing media for a couple of seconds then freezes and locks up, again resulting in a failure and need to disconnect then reconnect. This is without even doing anything special (like phone calls or text messages in or out), or using maps - just basic navigation or playing maps.
So overall I am finding 50% of times you connect it fails, completely, because of one error or another - so it’s highly unstable running on only the stubs and FOSS type apps. At least in my vehicle and phone combination.
18 October 2025
…anyway here’s a summary of what I spent a couple of hours or so doing today a week ago as I recall them:
(1) Google Speech Recognition & Synthesis
I added this in, removing the stub first. It had no meaningful impact on how Android Auto performed, and I couldn’t get it to initiate for anything. In cases where there was normally the microphone button to initiate STT input you couldn’t get to the microphone option (due to the other system navigation issues) nor did it trigger properly (when you could). So overall effect was no change.
Note at this time I had
SherpaTTSandFUTO Voice (STT)both installed - these were installed on the phone and I kept them installed the whole time I did these tests to see if I could get them to work once I had the Google stuff working…P.S. I had checked everywhere I could find by searching settings to make sure Google Speech Synthesis was set as the default app for any TTS and STT.
(2) Google Voice Access
Next thing was I added this - keeping above installed. Thought it might help with STT but no… basically there was no apparent benefit having this.(3) Google (Search) App and Google Maps
Next step I removed the remaining 2 stubs and installed these 2 apps. It was interesting to note this did slightly improve system navigation in the car - the system froze less often and some functions were accessible that previously weren’t. Also SMS messages now showed in the SMS app/utility screen - although you still couldn’t read them (i.e. clicking on them did nothing) - or use TTS to reply (for same reason); nor did create/initiate a new message work (as previous, clicking on it caused it to briefly change colour showing it triggered the action state or whatever, so presumably tried to initiate something - but nothing happened).Also when a new SMS arrived it’s notification appeared on screen like before in a pop up, and you could click it to play aloud (unlike previous which did nothing), but it would just then say an error occurred (so I’d speculate tried to call the digital assistant or the voice synthesis to process the contents of the message and failed). It would then lock up after that - so basically it sort of could go one step further than it did previously but still ended up not playing the message and locking up the AA screen; so you had to disconnect and reconnect to restart…
Everything above was still installed too, so:
Google Speech Recognition & Synthesis,Google Voice Access,SherpaTTSandFUTO Voice (STT).(4) Google Assistant
As a last resort I installed this - it’s a concern if you need it long-term because looks like it’s being superseded with full on Gemini shortly - so essentially enforced full AI use. However oddly either this current version of the app (or perhaps it was theGoogle (Search) Appabove - can’t recall which it was) required zero permissions or external access - meaning it might be (or would have been) fairly safe to use withiodélocking it down further as extra security?Firstly it did not show up as a digital assistant (in the manage digital assistant option in settings for AA). Nor could I get anything to show there the whole time. So that was also weird and suggested something was fundamentally broken or not right in how that integrated with the FOSS Android (iodéOS) versus stock Google Android? But maybe I just missed something with permissions and such…?
Anyway all of that didn’t matter in the end, because it made zero difference again. No further improvement, a portion of functions or menu options unusable in AA in the car, it still randomly froze when doing things. And couldn’t get any STT input to work with things like
OsmAnd(or evenGoogle Maps).So by this stage I had
Google (Search) App,Google Maps,Google Speech Recognition & Synthesis,Google Voice Access,Google Assistant,SherpaTTSandFUTO Voice (STT)all installed. And it still wouldn’t work.The only things I didn’t do - as I forgot/didn’t think of it at the time - was to (a) fully uninstall
SherpaTTSandFUTO Voice (STT)just in case there was some weird conflict - but I think this is unlikely, and (b) fully test every test I tried in the car also just on the phone (without the car and AA) - I did a couple but not everything.So I can’t verify for certain if everything that failed in AA also would have failed on the phone regardless - some definitely did.… …it’s both that some of these don’t quite integrate with the OS the same way they do on Google stock Android (maybe missing some proprietary hook), but also that there’s also a problem with AA and that’s something that’s a significant difference from stock Android (my earlier musing about some sort of proprietary connectivity required in AA lacking from FOSS android systems).
So that was about it. There were some more minor things I tried to dig into (e.g. media control, etc) but basically I could not get Phone, SMS/Messages, any Maps, or other media or apps (e.g. Molly) to work consistently and with full functionality, or in some cases at all, regardless of how much Google stuff I installed…
![]()
![]()
21 October 2025
Rik Shaw:
Wondering if iodé app (blocker) was possibly at play too: possibly going full “no privacy here” mode (just fully disable iodé blocker) for testing would get things working then we pare back from there…
Sorry - forgot to mention I did that too. Had tried as final step zero restrictions on all the G apps above incl. AA - so 6 apps with unrestricted access (and permissions) in my main profile…
25 October 2025
@rik a further update - I have since purchased a mint Google Pixel 8 Pro as a second device to try iodéOS on (that is a stock mainstream model); and that can later be my temporary daily driver so as to allow me to then use my BraX3 for potentially being a beta tester of UBT. I also thought I could revisit AA with iodé on that device. Anyway…
I am about to do the iodéOS install on it, and before I did I hooked it up to my car (Mazda) to double check the stock default (‘factory reset’) Google Android connectivity and performance:
- When I connected to my car the phone immediately identified there was a valid AA system present and available to connect to - it them pushed me immediately to a
Google Play Serviceslog in screen, and required me to log in to go any further. I could not proceed any further with enabling AA without logging into an account at this point.- I had not connected Wi-Fi up to this point so I did do that and tried again. When it pushed me to the
Google Play Serviceslog in screen, and required me to log in to go any further, I found going back to prior screen just enabled the AA Update anyway, without a log in. I also could separately go into the Google Play Store > Updates (without logging in) and enable updates for any pre-installed or system features. So I could update voice recognition, Google (search) app, etc, as well as AA to latest version. Once AA had updated this got me to the final screen shot below:
- I then got Android Auto connected and working. And everything worked as expected that I could see, including voice. But again, as I found with the Samsung A34 to do anything with voice I needed to log into a Google Account and enable personal recommendations and other settings… So it would not function without a Google Account log in.
So I can only come to the conclusion that my earlier gut feel that something proprietary is at play - whether it’s in the app software & hardware combination, or more likely it’s in the G account log in part and stuff on the servers.
So I am pretty sceptical now it can made to work as is with degoogled hardware…
…at least without a Google Account active on the device - the odd app may work in it’s basic form, like maps and media players, but not everything nor full functions.
