unable to open MTP device / couldn't find matching udev device

[KreAch3R]

Setup:

Headunit: Raspberry Pi 4: Raspbian 10 buster
Dongle: Raspberry Pi Zero 2W: latest release
Android Auto headunit: OpenAuto-Pro (A fork of Crankshaft).

Issue:
The dongle works. When Android Auto is connected and the image is projected successfully to the Headunit RPI4, an error popup shows up with:
unable to open MTP device "001,012"
or
couldn't find matching udev device

It happens every time. It doesn't affect the functionality.

I suspect it is because of this: #3 and the MTP implementation somehow is conflicting with Raspbian. Maybe because it expects a rw device and gets a ro?

@BluemediaDev @nisargjhaveri I hope I get your views on this on how to fix it / bypass it.

[manio]

Maybe it is because switching dongle modes (accessory <-> default) or switching too fast. You can see if it is working without it (aa-proxy-rs doesn't have that switching by default but you can enable it with a "legacy" command line switch if it doesn't work).

[KreAch3R]

Thanks @manio I will give aa-proxy-rs a try, by manually installing it onto the image and get back to you. Can you check my other issue #226?

[KreAch3R]

Well I gave your image a try, it does appear that the MTP error is not thrown, but the connection doesn't stay on, it goes into a loop of connecting for a couple of seconds, then dropping the connection, then successfully reconnecting etc. It's not usable as is, I'll go back for the moment. Any suggestions?

[manio]

Any suggestions?

Hard to tell anything without a logs.

Can you check my other issue #226?

I know - you want it on the same raspberry Pi as OpenAuto to get rid of one board. Very clever. I am also using the same Pi for LoRa as well ;)