USB drives no longer detected with car version 2.0 / Android Automotive 11

[MoleMan1024]

by e-mail from two users: USB drives are no longer detected with Volvo/Polestar version 2.0 (Android Automotive 11).

---

Please see info on this on the homepage

[MoleMan1024]

Cannot reproduce this yet since I don't have that version in my car.
Will try to compile AAOS 12 for phone and try if reproducible there, but might behave differently than in the car.
Added hidden TextView to show logfile on screen to maybe see what is going on.
If this was intentional by Volvo/Polestar this might mean the end of the app but let'see first...

[lvitalis]

Please tell me it's an april fools joke ?

[agdejager]

Please tell me it's an april fools joke ? Is It????

[MoleMan1024]

Sadly, not a joke.

[MoleMan1024]

Tried AAOS 12 on Pixel 3 XL: GUI scale is messed up, changing density in BoardConfig.mk does not help, cannot click on anything properly, will try a AAOS 11 build instead.
...
AAOS 11 (RQ3A.211001.001) does not boot properly, going back to AAOS 12, need to fix or provide PRODUCT_ADB_KEYS
...
Could get logcat logs for AAOS 12 on Pixel 3 XL, lots of repeating errors and GUI does not show properly:

04-03 15:41:19.994   653  4996 I hwservicemanager: Tried to start android.hardware.automotive.vehicle@2.0::IVehicle/default as a lazy service, but was unable to. Usually this happens when a service is not installed, but if the service is intended to be used as a lazy service, then it may be configured incorrectly.
04-03 15:41:19.994     0     0 E         : c0      1 init: Control message: Could not find 'android.hardware.automotive.vehicle@2.0::IVehicle/default' for ctl.interface_start from pid: 653 (/system/bin/hwservicemanager)

[MoleMan1024]

Released a version 1.5.6 that allows to show the logfile on screen via AudioWagon Settings > tap on "Version" field (because log files can't be written to USB when USB does not work). Maybe there is an error message in there...

[TomKario]

I just sent some photos. I desperately hope he's able to fix it.

[Feinhessisch]

Please have a look at https://www.motor-talk.de/forum/software-aktualisierung-android-automotive-fahrzeug-ab-mj22-updates-aktuelle-version-2-0-t7169750.html?page=39#post63558057 :( . The contributor who wrote the forum message is a Volvo dealer.

[TomKario]

What 'Feinhessisch' wants to say is that Volvo cut off the data connection of the USB bus. If this is intentionally or a bug ist not known. Maybe we have to wait until June, then the new release will come which should support carplay and such things.

[agdejager]

What 'Feinhessisch' wants to say is that Volvo cut off the data connection of the USB bus. If this is intentionally or a bug ist not known. Maybe we have to wait until June, then the new release will come which should support carplay and such things.

Not acceptable!!!

[TomKario]

What 'Feinhessisch' wants to say is that Volvo cut off the data connection of the USB bus. If this is intentionally or a bug ist not known. Maybe we have to wait until June, then the new release will come which should support carplay and such things.

Not acceptable!!!

So what... if acceptable or not you can't change this! This sucks, you're right, so don't get a Volvo or polestar and deal with other model problems.

[IcyT]

So what... if acceptable or not you can't change this! This sucks, you're right, so don't get a Volvo or polestar and deal with other model problems.

That was a useless comment. What about the people who have a Volvo or Polestar already?
And in my opinion we can change this. If we're loud enough together, they will change it. If AudioWagon would not have existed, I would not have bought a PS2 indeed. So for me this makes all of the difference and I will complain. Many times. And so should everybody who wants to have that back.

[TomKario]

@IcyT Jepp, unfortunately you're right, mine was the second useless comment here. Sorry for that.
But this is not the right place to complain. Complaining here does not reach Volvo.
I'm one of two who reported the problem and I'm in contact with MoleMan by mail and sent him pics of the log to investigate what's going on. Also I'm in contact with Volvo because my XC60 T6 Recharge Model 22 got V2.0 with Android11 about two weeks ago. So let's stop crying here, shout out loud on more useful platforms. Let's concentrate on the solution if there is any.

[micksmothers]

Once I get 2.0 OTA I'll check as well.

[Dream-Rider]

Annoyed at the disabling of the only way we could playback 16bit audio, not to mention other audio formats...its astonishing really, particularly with such a great hifi system! I have written to Volvo about this and would encourage all the others this effects to write in too please.

[lvitalis]

I complained on Facebook and Polestar answered after a couple of days (they probably did not know the answer and had to ask Google)

The latest update (P2.0) introduces the latest Android Automotive OS to Polestar 2 (Android R). This has temporarily limited the functionality available from the USB-C port in preparation for future functionality. This change is expected to be updated in the next software update (P2.1) and we apologise for the inconvenience in the interim.

Notice the words "temporarily" and "interim". At least there is hope.

[MoleMan1024]

This has been fixed by Volvo/Polestar with car version 2.2.