Android Auto in Private Space

beppi

Hey guys,

I hate to create another AA thread, please nuke this if it's just too much noise on the forum.

Here are some related AA discussions I've read:

https://discuss.grapheneos.org/d/16971-isolating-android-auto-private-space-work-profile-or-separate-user-profile/6
https://discuss.grapheneos.org/d/18402-private-space-android-auto/4
https://discuss.grapheneos.org/d/22042-android-auto-in-private-space
https://discuss.grapheneos.org/d/17262-private-space-android-auto-phone-calls
https://discuss.grapheneos.org/d/18414-android-auto-in-private-space

My main problem is step 3 below: The fact that I can only get AA working in PS if I set default USB config to file transfer (and I can't get wireless AA working).

I'm using the latest experimental Pixel 10 Pro release, so my issues could be due to that. I'd love if someone with a P9/8 who is using AA in a PS could chime in.

I can get wired AA working in a PS by doing the following:

Settings > Security and Privacy > Private space > Sandboxed Google Play > Android Auto > set the 4 AA toggles.
From the 4 toggle menu > Android Auto app info > Permissions > allow Nearby Devices
PROBLEM ALERT: Developer options > Default USB configuration > Set default to "File transfer"

This works, but I feel really bad about setting the default USB config to File transfer. Is this normal?

For wireless AA, I don't even know where to begin. I just can't seem to get it working, but I am using a Motorola MA1 since my car doesn't have wireless AA support so that extra layer could be causing issues. I have been using it successfully on my P7P though.

Thanks everyone for any input you have!

Novalissoide

beppi Would it change anything if in

Settings> Security and privacy > Exploit protection > Usb-C

the toggle at bottom, labeled 'On', gets selected?

beppi

Novalissoide Dang I didn't notice that, I've set it to "charging only when locked", and the default permissions to "no data transfer" and its working. Feels much better!

Novalissoide

beppi that's great. The best case is if the much safer 'Charging-only when locked', also works.

beppi

Seems to work perfectly. Now i just have to understand whats stopping wireless AA

beppi

It's not solved. I just updated AA, and the gapps and it no longer worked. I had to re-set "File transfer" as the default USB option to allow it to work, and then change it back to "charging only when locked".

Novalissoide

beppi did you update Auto through the GrapheneOS Apps Store? And did it work after the setting?

beppi

Yeah updated through the GOS app store, Alpha channel for: AA, GPlay Store, GPlay services, GmsCompatConfig and AppCompatConfig. Just to be clear, it is working again, but I don't know if its a full solution if I have to adjust the default USB permissions each time AA updates.

I don't remember having to do this when I was running AA in a user profile, so I'm not exactly sure how the logic works with USB trust levels when trying to go from USB -> Normal GOS -> Private space.

Usually (In the owner profile) it must assign the default USB perms, but the 4 AA toggles must allow USB connections to AA with less restrictions. But then if AA is in a private space, since the toggles are set in the PS rather than the Owner space, the Owner doesn't assign permissions that the toggles usually handle and thus doesn't connect the USB to the private space. Or that's how I'm rationalising it at least, I basically have no real idea.

Doesn't explain why updating the Gsuite apps resets the perms though

KonyakCarl

I have a similar problem as well. I bought a pixel 10 pro XL, and changed my setup from having a blank owner profile, non google app profile, and a google profile, to a single profile with non google apps on the main, and google apps on my private space.

The first time I connected to my car with (private space) android auto, it seemed to have worked. however, every other time my car doesn't recognize my phone is connected. After reading this thread, the only solution to make it connect is by having the developer settings enabled and going into the Default USB configuration and changing it to something other than no data transfer. As soon as I change it, my vehicle instantly recognizes it and I am able to change it back to no data transfer and it continues working until I turn off my car.

Oddly enough, I noticed when its connected to my car, I don't think any setting is selected in the USB section when connected to my vehicle , once I change a setting it crashes back to the developer settings and I have to reselect Default USB configuration. Once I reopen it, no option is selected again and I can select any option and itll crash back to developer settings.

The setup I have is a wired connection to my car on a Pixel 10 Pro XL with android auto in private space, I have play services and the play store too in the private space. I do not have any google apps in my main profile. I hope we can figure something out as I rather not be having the developer settings enabled to change one setting every time i drive my car.

Love this OS, been using it for years at this point.