yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Ben.suffolk:
Had a couple of 45 min drives today with wireless and using waze. No issues with disconnect so I’m pretty happy with the latest release it seems to have solved the problems I was having.

I have noticed if your listening to audio from the head. It (dab in my case) and waze (CarPlay) speaks, it reduces the volume of the other audio, and never increases it again. So that’s a little big that could do with fixing.

I’m also a bit worried when it comes to ios13 upgrade based on whats bee said, I hope they do a fix for that before it rolls out for real.
[Android Head-Units] gene3489:
does anybody have a solution for the delays?

it's like having a international call in the 90's
[Android Head-Units] brettf:
Same here. Stopped working last week. No Android Auto update, but I did install the latest Autokit.apk and I think that broke it.
[Android Head-Units] Bradsr12:
To be perfectly honest, I have had no major problems with the new firmware, I travel a couple of hours a day, it connects perfectly, and plays audio perfectly on iOS 12.. the only thing I have done is to modify the aerials to external..

and the only problem I have is with iOS 13 is the music stutters.. (I haven’t tested beta 3 yet)

But none of the other problems people have reported have effected me at this time..
[Android Head-Units] techo91:
Would you like to try the beta 3?
[Android Head-Units] Bradsr12:
I have it already to download on my phone and install, however I have just not got round to doing it yet, but many thanks! I will report back any problems if I find them!!
[Android Head-Units] merewood bebox:
ive tried rolling back, no luck
[Android Head-Units] mrsco:
I can also confirm. iOS 12 audio sounds perfect wireless. ios13 beta 3, the audio stutters intermittently from some type of interference (maybe cellular or bluetooth? airplane mode seems to help) ... ios13 beta 3 works perfect on wired though.

I attached some wired vs wireless audio test examples on ios13 beta3 using a 1khz test tone

I also maybe noticed that setting the Advanced Settings->Charging Mode to weak helps eliminate some of the interference.
[Android Head-Units] Ben.suffolk:
Has anybody fed back the ios13 issue to the manufacturer?

It seems like it should come from somebody with it installed though.

Ben
[Android Head-Units] mrsco:
I've been going back and forth with CarlinKit Support on their whatsapp ... +86 139 2830 5879

but after going round and round with disabling wifi and bluetooth on radio, cellular and bluetooth on phone, etc... nothing actually seems to fix the issue other then just using iOS12. And thats what support ends up saying "iOS 13 isn't supported" and they don't say whether it will be fixed in a future firmware/software update of the auto box.
[Android Head-Units] slunat:
It's going to be super annoying if they can't get it working right with this hardware on iOS 13, a massive slap in the face to everyone who bought it as a "1st gen" product, but I honestly wouldn't be surprised if that the route they take just because its easier. I will definitely be wanting a refund or at least a discount towards a future product
[Android Head-Units] mrsco:
yea its a shame because its so close to working perfectly. Hopefully a software tweak in the ios 13 beta or the auto box software can get past the interference issues.
[Android Head-Units] techo91:
I highly doubt Apple will change iOS according to some Chinese dongle manufacturer because they don’t want to adapt the firmware to a OS that is around the corner. If it was the iOS 13 it wold work bad wired as well.
[Android Head-Units] slunat:
I think it's a bandwidth issue personally, iOS 13 just might be more demanding and maybe too much data needs to be transferred, more than the dongles can handle wirelessly. Using a cable, you've got a lot more room for data transfer which explains why it's flawless over wired. At least that's my theory, in which case we are most likely screwed.
[Android Head-Units] mrsco:
I think this or maybe interference.. it sounds like interference since it comes and goes and isn’t t constant. The iOS 13 beta might have something going on with the cell modem firmware or Bluetooth firmware that has changed and isn’t filtered since it’s logging extra stuff for beta. Fingers crossed anyway
[Android Head-Units] Bradsr12:
One thing I have been told by a friend, and I am hoping this is the case, he has this problem with his alpine wireless CarPlay in iOS 12 beta... and in final release it was all ok! So let’s hope it’s the same with this....
[Android Head-Units] techo91:
Bandwidth doesn’t make a lot of sense to me as it would constantly change the way it stutters. Bluetooth also has nothing to do as it is used only to establish the connection. Signal strength also seams to not be the reason as we have all tried to put our phones next to the dongle with no improvement.
[Android Head-Units] xandr115:
Saw this thread re: carplay instability back during iOS 12 betas

https://www.reddit.com/r/CarPlay/comments/8umckn/ios_12_public_beta_carplay_issues/

That being said... How stable is the carlinkit adapter and autokit?

I've got a dasaita px5 and a dasaita branded carplay adapter using autoplaybox APK. The combination has not been stable whatsoever... Regularly have trouble establishing a connection (and sometimes maintaining one) even using wired.

When connected the iPhone also occasionally displays "accessory not supported" messages which usually interrupt the use of some carplay apps... Am I alone in this? Strongly considering buying the carlinkit wireless version (also think the autokit GUI for connecting looks better)
[Android Head-Units] kavi_nash:
Any suggestions between below three wireless dongles? Why is a price difference b/w same Aliexpress products?

<Please replace dot with . in below URLs>

$78 - Amazon - amazondotcom/Carlinkit-Wireless-carplay-Navigation-mirroring/dp/B07S1M8C34/ref=sr_1_1?crid=2S4M891ZYQOZ3&keywords=carlinkit+wireless&qid=1562386112&s=gateway&sprefix=carlinkit+wir%2Caps%2C207&sr=8-1

$59 - Aliexpress 1 - aliexpressdotcom/item/33049732233.html?spm=2114.search0104.3.9.7c3963a3e986VK&ws_ab_test=searchweb0_0%2Csearchweb201602_2_10065_10130_10068_10547_319_10546_317_10548_10545_10696_10084_453_454_10083_10618_10307_537_536_10059_10884_10887_321_322_10103%2Csearchweb201603_52%2CppcSwitch_0&algo_expid=e59c0bb9-68c9-42c2-9c2f-6aeb660aef04-1&algo_pvid=e59c0bb9-68c9-42c2-9c2f-6aeb660aef04

$80 - Aliexpress 2 - aliexpressdotcom/item/32983926178.html?spm=2114.search0104.3.2.7c3963a3e986VK&ws_ab_test=searchweb0_0%2Csearchweb201602_2_10065_10130_10068_10547_319_10546_317_10548_10545_10696_10084_453_454_10083_10618_10307_537_536_10059_10884_10887_321_322_10103%2Csearchweb201603_52%2CppcSwitch_0&algo_expid=e59c0bb9-68c9-42c2-9c2f-6aeb660aef04-0&algo_pvid=e59c0bb9-68c9-42c2-9c2f-6aeb660aef04
[Android Head-Units] mjones73:
Mine up and died on me, seen a few other people complaining too.. the mapping looks to be working to the software, something upstream isn't right. I'm guessing the latest app/box firmware might have something to do with it.
[Android Head-Units] Xcaptain:
Along with the dongle, this is as close as to an OEM CarPlay experience can be. Especially when wireless mode works perfectly.
[Android Head-Units] Xcaptain:
This maybe a cable issue. Use an mFI, or original lightning cable.
[Android Head-Units] merewood bebox:
I think its to do with the AA app, Steering works fine on my iphone when using carplay. working fine on a fresh huawei phone with just AA but after a day or so, gives up.
[Android Head-Units] kelvinnn:
Hi guys, I've been struggling with the wireless dongle from the day I received it - and it's been quite a long while (I ordered the domestic China version way before it was on AliExpress). Anyway, I'm using it with a Merryway Android 7.1 head unit which I got directly from Merryway.

I've been trying to narrow the instability (Please insert product/Please connect phone) and random disconnect issues and then I discovered several stuff while snooping around the logs on the Android head unit:

1) The dongle appears to be some sort of mini-computer running Linux with tftp capability

2) The app is designed to "upload" some sort of config file as per your settings into the dongle

3) The dongle then "reboots?" to apply the new config as per uploaded

4) The dongle establishes connection with your phone (??)

That said, once I realized it was some sort of mini-computer/android device, I got to work with my USB voltage tester. I noticed that any working below 0.20A has no issues, no lag, no disconnects. But once it gets above 0.20 to 0.25A or so, the disconnects and random reboots happen.

This got me thinking.. what if I could boost the maximum power drawn? I took a standard USB hub which allowed a second micro USB input for additional power to boost the range to 0.25A to 0.5A and supplemented the USB hub, and I connected the dongle to the hub... Lo and behold. It's been 5 days now, no disconnects and fast connect!

Some other tests I am doing now are:

1) Tracing lag/stutter in music when phone is at low battery

2) Tracing optimal settings (Compatible mode is garbage... unusable!) given sufficient power supply to USB ports

3) Attempting to gain more insights to reverse engineer the dongle a little ;)
[Android Head-Units] mrsco:
interesting finds! does the wireless intereference go away on ios 13 using the usb powered hub?
[Android Head-Units] kelvinnn:
Unfortunately, I don't have the guts to upgrade to iOS 13 on my main device yet. Let me find an alternate device and I will attempt...
[Android Head-Units] Belo83:
I appreciate all the users and posts in this thread. It helped me realize my first unit was a counterfit and troubleshoot issues with my newest. I have a few quick questions and greatly appreciate any help.

I have a black gen4 with mic.

1. The unit is a few weeks old. Software loaded fine from website onto my headunit. But audio drop and distortion was horrible while using waze. I realized that despite just downloading the software that it wasn't the latest, updated the software and box firmware last night and it's still happening. Switched to fluency mode and maybe that helped on the last 10 minutes of my commute, but not sure. Does anyone know what the modes mean/do? There are no descriptions.

2. Before I return the gen4 and spend $80 on the new one, can anyone confirm the wireless unit (using it plugged in so i can charge) resolves the audio issues while using waze?

3. When I make calls, I would prefer to use my headunit bluetooth, but it automatically connects my phone audio to autokit. Cant seem to find an option to disable/change this. Does anyone know if this can be done? Very frustrating and dangerous to change source when receiving or making calls.
[Android Head-Units] brettf:
I just downgraded mine to a version from 2018 and the steering wheel controls still don't work. :confused:
[Android Head-Units] brettf:
I tried rolling back the app to an earlier version from apkmirror. Doesn't work.

I've rolled back Autokit.apk, the Auto box firmware and Android Auto. Still no luck.
[Android Head-Units] merewood bebox:
As I thought. This is something so do with the app and his it processes commands. I've seen reports that steering wheel has stopped working for even name brand units like Sony xav
[Android Head-Units] looxonline:
I spent quite a while reverse engineering the code to figure this out. The firmware does indeed send out an implicit media intent which "should" be sent to all processes that have subscribed to it. Unfortunately there was a change made in later builds of Android 8 where, in order to reduce process churn, implicit broadcasts were disabled for apps that do not specifically have system privileges (hint, zlink app does not). See the links below for more info...

https://developer.android.com/guide/components/intents-common

https://developer.android.com/about/versions/oreo/android-8.0-changes

I tried to disable this and change the permissions for the zlink/zbox apk using the xposed framework and while it is possible it was too challenging for me given my very limited knowledge of Android/Xposed. The next best solution was to try and find an intent that the autobox/zlink/zbox apk could still receive and then intercept the implicit intent and change it to that type. Turns out that the apk can still receive intents that are sent out as a result of an external USB button press so the trick is to intercept the SWC button and then convert that into a "fake" external USB input. I wrote an xposed module that does this for Android 8 FYT units and it works like a charm on my unit but because it has been designed to intercept inputs on a specific firmware type it only works with FYT and only with Android 8. I suppose if I had time and access to other mainserver.apk files from other units I could figure out which functions to hook but currently I have neither :)
[Android Head-Units] merewood bebox:
while i believe this is part of the issue it does not explain everything. my head unit is android 6, and like i said it does work on a fresh huawei phone but doesnt work on my daily driver. further more the app works flawlessly with my iphone when wired
[Android Head-Units] looxonline:
Could be the same root cause. The apk is not what presents the UI from the phone. There are other services running in the background. It is possible (actually likely) that there are different services running for different devices and connection methods. Maybe some services are still able to receive the media intents.
[Android Head-Units] merewood bebox:
is using xposed the only way to fix is or is this something we can give to the developer of the app?
[Android Head-Units] looxonline:
It would require the developer of the app to get access to the key that is used to compile the build which I doubt that FYT or Joying are going to provide so unlikely that it can be fixed by them. If they could have fixed it by now then they would have.
[Android Head-Units] brettf:
That's awesome. Would you mind sharing the details of the intent that the Autokit apk receives? I could then use MTCDTools to fire that intent when I press the specific button on my steering wheel.

(I guess I could also just decompile the Autokit apk)
[Android Head-Units] looxonline:
Exactly. Decompile your particular one and then have a look at the manifest.

http://www.javadecompilers.com/apk
[Android Head-Units] brettf:
Will take a look. Thanks!
[Android Head-Units] looxonline:
Very likely that Android will still block this BTW. That was the first method I used when I started writing my module. In the end I had to create a virtual USB keyboard using some hackery and simulate button presses in C.
[Android Head-Units] merewood bebox:
Don't get why android is suddenly blocking it
[Android Head-Units] dchuraman:
What is the latest apk and box versions out there? Has anything been improved recently?
[Android Head-Units] merewood bebox:
this is the directory of the system http://112.74.112.110/download/, .img are the box versions. do you know how to install the .img files?
[Android Head-Units] dchuraman:
I do, that's great thanks, I couldn't remember the link for that directory
[Android Head-Units] merewood bebox:
no on found a fix for the steering wheel control issue? even the skip button on the head unit themselves dont work anymore
[Android Head-Units] Belo83:
tested the newest wireless version with most recent software and box firmware on the way to work this morning and i honestly think it's worse than gen4 with respects to losing audio while waze is also running. Haven't tried wireless yet, but very disappointed.
[Android Head-Units] xandr115:
Thanks, but my cable is MFI (tried multiple cables). Since installing it in December, I performed several in-app updates for both the APK and box software. I removed the updated apk, and installed the one I was given back in December and the connection issues appeared to be resolved... however I now have an audio hiss that I don't remember having before. Going to try updating again...

Re: the carlinkit version, what's the difference between the model with mic and without? Is there a benefit to one or the other (audio input performance improvement?)
[Android Head-Units] brettf:
I've reverted to using Head Unit Reloaded. Steering wheel controls work fine with it.

I kind of had to because I think I messed up my dongle while trying to downgrade the firmware. It crashes after about 5 mins while my phone is connected.
[Android Head-Units] starfarer:
Need help pls. I've almost read whole thread and tried suggested solutions/apps but having error of "can't find phone". I bought generic chinese HU off ebay which came with white dongle. The HU has zBox version 4.5.9 with probably fake 8.1 android version. But as it was bundled with zBox dongle, I was not concerned and my main usages would've been AA. For the price I'm very happy. The HU and app detects zBox dongle which shows zBox FW 4.2.0 and APK version 4.5.9-cp_cl_at but only charges the phone once connected. I've tried few versions of autokit and all shows counterfeit msg. I've ordered Y usb cable just in case to feed extra power off cig adapter. But in mean time until the cable arrives, is there anything else I can try? Where can I find zBox firmwares?

Just to note the white dongle has no label or sticker and not sure of make/model. When connected to computer, it identifies as Gadget iap2, Hardware ID: USB\VID_0525&PID_A4A5&REV_0216 , USB\VID_0525&PID_A4A5.

Thanks in advance.
[Android Head-Units] Bradsr12:
To my very limited knowledge, ZBox only uses “ZBox” apk, I thinks it’s called “ZLink” and in the unit that I have used in the pass you have to open the ZLink software and select “AA” in the settings..

you also need to download the “AA” apk onto your phone from the play store..

I can’t promise that this helps but I hope it does for you ?

---------- Post added at 04:02 PM ---------- Previous post was at 03:58 PM ----------

Some dongles have a built in mic, so you can then select the built in mic, others do not..

from my understand the models that have a built in much are not much good for using the mic unless you have the dongle close to you when your talking!
[Android Head-Units] tinooo123:
I've an odd finding. With the latest AutoKit version, there is the option (beta) to define buttons for different actions, such as skip, pause, siri, forward, home, ...

Trying this feature, none of the buttons on my Radio (Witson PX5 i bleaeave, Andorid8), is beeing recognized. Neither are the buttons on the Steering wheel with one exception: the two telephoen buttons on the steeringwheel are the only ones being recognized.

So I've remapped them, being able now to skip and repeat a track in AppleCarplay. For me a quite acceptable work arround, since the few times i get a call, i can use my touchscreen.

Is there any kind of documentation/wiki/comparison of all dongles out, also explaing shortly the different settings? This would be such a great help i guess!
[Android Head-Units] looxonline:
Your unit will be compatible with my xposed mod which will enable all of the SWC buttons. Search the forum for Carplay, Zlink and SWC and you will find the mod. Note that you need to be rooted with the xposed framework installed.
[Android Head-Units] merewood bebox:
sadly, just bought Headunit reloaded and get black screen or loop using mate 20 pro
[Android Head-Units] mrsco:
I just updated to ios 13 Beta 4 and the wireless carplay still has interference.

the touchscreen responsiveness on head unit carplay gui is improved tho. here's hoping beta 5 does magic!
[Android Head-Units] starfarer:
the dongle works with iphone and carplay as tested briefly yesterday. So looks like it's the compatible issue with android as in another thread there's mention of zbox not supporing above oreo. Still waiting for Y splitter usb cable as someone in this thread had success. If I use with powered OTG USB hub, I can see phone connecting on msg HU and AA connected to car on phone but nothing comes on HU. Has anyone using zbox with oreo/pie on their HU?
[Android Head-Units] merewood bebox:
the box has to be as close as possible to the phone in the chain of wires to your head unit. p
[Android Head-Units] Andy Alias:
I bought the cheaper Carlinkit wireless dongle, worked well with my iPhone 7 running iOS 12, then updated to iOS 13 Public Beta and Music got jittery (micro gaps). Looking back seems to be iOS beta being the culprit. Wired USB connection is smooth.

Dongle

Light Mode

Dark Mode
[Android Head-Units] xandr115:
Starting getting an audible electronic hum coming from the radio when playing audio through the carplay dongle (dasaita dongle and dasaita px5 radio). It wasn't happening before... combined w/ the weird issues with connectivity unless I used the APK from 2018 November... finally decided to try the carlinkit wireless adapter (wired if wireless doesn't work well). Hope that comes in soon.

Anyone else hear an electronic hum from their carplay dongles?
[Android Head-Units] AppleIron:
Check the audio volume of the Android head. Sometimes CarPlay go out with a limited volume, if you Android head is going out with a 50% of volume is normal heard the signal hum.
[Android Head-Units] Andy Alias:
I believe it was a regular usb hub not a powered one.

Edit - Sorry I misread his post. disregard.
[Android Head-Units] Andy Alias:
I’m in the process of making a cable that will supply up to 2.1A while passing through the usb data. I’m doing this by dismantling a 12v to 5v 2.1A usb charger adapter and feeding that to the usb cable.

Am I right in thinking that the dongle will take as much or as little power as it requires and that this won’t damage it? It would be the equivalent of plugging it into a car usb charger.

Some other questions, how are the disconnects/reconnects? Still none existent?

How far are you getting reverse engineering? Would this be to modify your own unit or make an app that would replace AutoKit?

Thanks in advance
[Android Head-Units] Fgarcor:
This is a quite common mechanism called bootstrapping. The image of the dongle exists in the APK and when plugged the dongle downloads it automatically via tftp server from the APK. And it boots it up.

It makes sense that also means that the APK opens a port in the headunit.
[Android Head-Units] Andy Alias:
I messaged CarLinKit and they gave me an updated Apk to try, time will tell. The date on it is 2019.07.19
[Android Head-Units] Bradsr12:
Would you mind sharing please??
[Android Head-Units] Andy Alias:
[/COLOR]

link

This is the link they sent me, if it stops working I will upload it somewhere else. (click the blue button).

Also you need to rename the file to take off the .1 after .apk

Google Drive Link
[Android Head-Units] Bradsr12:
Bless you! Thank you so much! Dry much appreciated!!

Many thanks! And kind regards!
[Android Head-Units] Andy Alias:
You're welcome. My commute is quite short so it could take a while to discover if it fixes anything, let us know how you get on.
[Android Head-Units] dpgc213:
Has anyone had issues with resolution, I can connect to it fine however I sometimes get a blank screen when connected or I get the CarPlay interface which is completely out of resolution.

Anyone got a fix for this?

Thanks
[Android Head-Units] Bullet_King1996:
I have this issue and I'm losing it trying to find solutions! Same exact thing, after coming out of reverse, screen goes white, if I interact with it some stuff gets rerendered but it still looks glitchy. Reconnecting the cable and restarting the app doesn't really work.. my screen just remains white while driving, the head unit itself functions fine though..

Dongle: CPC200-CMAP

AutoKit version: 2019.05.20.1041

Dongle (Box) version: 2019.05.17.1321

Android version: 9

Does anyone else run into this issue? Any suggestions for a fix?

https://imgur.com/a/d8y3eP2