USB_transfer error

[Zoonie81]

First of all, big thanks for all your time and effort spent on this project @MaKi983!

Updating to 2.4.1 I'm getting black screen followed by USB_transfer error. Tried all USB settings on phone/restarted both phone and HU/cleared cache etc etc. Phone is an Xperia 1 mk2 running Android 12. Before updating I was running 1.0 and there were no issues connecting, just the normal stuff.

Did a deep web crawl yesterday and it seems like there are more people with this problem who had no problems with the handshake on 1.0.

Would you like me to get you a log?

Best regards,
Z

[MaKi983]

Most of the time, the USB errors are due to the usb cable, you can try another one and test it.

You can collect the log and send it to me to do a check.
Here how to collect the log:

• attach a USB pen drive with a ODA folder in its root (make sure to have an ODA folder inside the drive, create it)
• set the correct usb path in advanced settings of ODA app
• set verbose log level
• enable external log
• run the app until crash
• if everything is done correctly you should find one or more files in ODA folder of USB drive, send them to me in a private message

Some considerations:

• Don't enable log protocol, it will slow down the app and it's not necessary.
• In verbose level the app will log many many information, so it's not the case to keep this level for long travel
• At the end disabile external log and set log level at INFO from same settings.

[spyram]

Hi @Zoonie81 and @MaKi983,

If I may add, I usually get that USB transfer error. Tried with different cables and it happens from time to time.

Another one I get is an SSL Error. Usually after taking a call.

Both are solved with disconnecting the USB cable and reconnecting it again and eventually terminating the AA process.

Is it possible to do some try/catch mechanism to avoid the application crashing and then ask the unit OS to reset the USB connection from inside the code? or is that operation reservered at OS level and we have no choice but to do the manual unplug/plug of the cable?

Side question: Do you know it the software would work with a Wireless AA dongle and if it could improve the app stability since we would eliminate the cable issue?

Thanks.
Ricardo

[Oxize]

Ive have this problem also with my FK2 Facelift Sport Honda Civic from 2016 (2017 first owner).

Well i tried 3 cables today. All give the same error to me aswell.

Ive installed everything (honda permission with the it.smg.hu process and your Android Auto apk)

When i connected my S10 i see it in the USB list as device.

But when i press start, i get the same error as @Zoonie81

How to fix this?

Ive tried 3 cables. A cheap plastic one, and 2 thick braided premium ones with 10gbps and USB3.2 Gen2 data/transfer rates. All 3 cables giving me the same error.

I tried so manny things to get something working so that i could use Google Maps. From connecting 2 Chromecasts (yes Honda has HDMI input), Mirrorlink, Mirrorcast adapters. Chromecast get stucked when connecting to my phone hotspot, and the Mirrorlink and Mirrorcast adapters are giving me Headunit an "unsupported device" warning.

My options are running out, and i am seeing other Honda Civic owners with an FK2 Facelift running your app no problem. :(

Me sad panda....

[Fudo7sei]

Hi there !
@Oxize : For me the app works really nice (Civic 9th 1.8L facelift 2016) but I also have this error sometime, juste clicking again on « start » multiple time make it work.

[Zoonie81]

@MaKi983 thanks for the reply. I don't think the cables are the problem, like mentioned, it works with 1.0 and different cables haven't helped. I'll get you the logs during this week and hopefully it'll help you solve the issue. Thanks again!

Best regards,
Z

[MaKi983]

In the app I use libusb to manage usb connection, the main difference from v1 and the current one is that, in current version, I use a more recent version of this lib. I can check if there is a newer one and test it. On my HRV I don't have any issue about usb connection. Just to know, did you tried a different usb port or different smartphone?

Side question: Do you know it the software would work with a Wireless AA dongle and if it could improve the app stability since we would eliminate the cable issue?

I never tested such dongle. You can search on xda thread, someone did it (maybe non AAWireless but a different one)

[RoiLago]

I'm using Tbox Lite S and for me it's more stable than using cable and now I'm only getting random crashes when there's a lot of things going on in Android Auto, but it has been a while since I last got a USB transfer error although my experience might be anecdotic

[Oxize]

Just to know, did you tried a different usb port or different smartphone?

Ye i tried like 7 cables now and also different ports (and my moms S23FE and mine S10), also spamming start over again (or killing the app and trying again) again what that other user say, but i keep getting the transfer error.

I will try to put log on my stick also for you. Just need to make a ODA map in the root of the stick and if i enable logs it should write to it when the error happens?

[MaKi983]

I will try to put log on my stick also for you. Just need to make a ODA map in the root of the stick and if i enable logs it should write to it when the error happens?

yes, in the pen drive create a folder with name ODA. Than be sure that the usb path under advanced settings is correct, set log level to verbose and start external log. When you finish set the log level to INFO and disable external log. The log will log everything and I hope to understand when the error happens

[Oxize]

I dont know the path. Tried: /mnt/sdcard/usbdrive1/ODA/ /mnt/sdcard/usbdrive2/ODA/

[Oxize]

Well i gave up with my Samsung S10 phone (Android 12). It keeps giving errors. When i tried some other phone S25 from my friend, that one started up with Android Auto in my car, but without Google Maps (he have google maps installed).

My headunit doesnt have Android Auto as Native. Only Gen 10 and higher have Android Auto on the Honda's. So somebody told me to buy the AAWireless 2 Adapter. I recieved that today and tried it out. First time i got some crash of your app, but when my S10 phone was connected to the AAWireless, i could start your App with no problems and getting Android Auto info through that AAWireless Adapter. And ofcourse Google Maps!

Me happy now. I will save your apk on my stick with folder with several version numbers. If a new version doesnt work, i can always go back.

[Oxize]

The only thing is, when somebody calls me, the app crashed of goes back to home screen. Can i avoid this to remove BT from telephone part in the HeadUnit? Because AAWireless got a Caller also. Or cant i use that one?

[Zoonie81]

Good evening @MaKi983, I have some logs for you. How would you like to receive them?

Best regards,
Z

[MaKi983]

Good evening @MaKi983, I have some logs for you. How would you like to receive them?

Best regards, Z

Send them to me as PM on xda, thanks