Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
You seem knowledgeable about GM Mylink. I have a 2016 Silverado, which I assume came with Mylink 2? Anyways, I was not able to find info on whether the touch screen is restrictive or capacitive. I found this Australian company that makes a device called Mimics G4 that allows you to control the phone from the nav screen but it only works with resistive screens.

If you have CarPlay it is v2. The non-carplay model is v1. I have no idea what kind of screen is used.

Have you flashed this yet via USB? What version does it report? Work ok?

As I said, I'm not the person to ask about the performance of firmware versions. I am using the devices with an 2019 Pioneer head unit called DMH-C2550NEX, not an OEM head unit. I have some issues, but none of the ones everyone else seems to be having.... and mine might be related to my iDatalink Maestro interface not the wireless CarPlay modules.
 
Last edited:
This a link for 6-17 firmware sent to me by Cplay2air in case anyone is interested


We have the latest update manually as of June 17,2020.

Here are the steps for the update instructions:
1. Please download the firmware update file from here: https://drive.google.com/file/d/15ihcyECm8voRpNcUz4ZWZxdkITzM3pbf/view?usp=sharing
2. Please save update firmware file on USB flash drive (Flash drive format must be FAT32)
3. Plug the flash drive into the CPLAY2air adapter.
4. Plug CPLAY2air to the USB power charger/wall charger for your iPhone. Please don’t use the USB port of the car or computer!!
5. Please wait 2-3 minutes, until the the flashing light becomes solid
6. Please unplug the adapter from the USB charger and remove the USB flash drive from the adapter.
7. Please now plug the product into the USB port of the car.
8. Please wait until the new window will appear on the vehicle's screen.
9. Connect your phone to the Bluetooth network which is shown on the screen.
10. Wait for the new interface to appear on the screen.

Thank you.

--

Tiffany
CARPLAY2air.com
 
This a link for 6-17 firmware sent to me by Cplay2air in case anyone is interested


We have the latest update manually as of June 17,2020.

Here are the steps for the update instructions:
1. Please download the firmware update file from here: https://drive.google.com/file/d/15ihcyECm8voRpNcUz4ZWZxdkITzM3pbf/view?usp=sharing
2. Please save update firmware file on USB flash drive (Flash drive format must be FAT32)
3. Plug the flash drive into the CPLAY2air adapter.
4. Plug CPLAY2air to the USB power charger/wall charger for your iPhone. Please don’t use the USB port of the car or computer!!
5. Please wait 2-3 minutes, until the the flashing light becomes solid
6. Please unplug the adapter from the USB charger and remove the USB flash drive from the adapter.
7. Please now plug the product into the USB port of the car.
8. Please wait until the new window will appear on the vehicle's screen.
9. Connect your phone to the Bluetooth network which is shown on the screen.
10. Wait for the new interface to appear on the screen.

Thank you.

--

Tiffany
CARPLAY2air.com

1a. Change file extension to .img

The fact that they didn't do that before uploading the firmware or put it in the directions for the customer to do makes me really not want to trust the update.
 
Last edited:
I have the 6/17 update that carlinkit posted its actual source. Also as noted earlier in the thread there are 6/24 and 6/28 updates which are actually 6/17 (corrected info from St Louis CPhT). And of course there is the new 7/8, not sure if that is OTA yet. Generally only update if your having significant issues and while doing an OTA update itself is not a safer process. The updates posted for OTA are the ones they have most confiedence in for the largest number of cars AV systems.
 
Last edited:
  • Like
Reactions: LarryJoe33
"If I tell you boys something, you won't think I've been drinking, will ya?"

I was finally able to solve my DMH-C2550NEX's issue with my track up/down steering wheel controls “sticking” and constantly skipping songs in the last direction pressed.

The fix:

I took my Carlinkit USB-C unit and plugged it into the extra port on my Carplay2Air USB-A unit. Then tested skipping a song. Instead of constantly skipping songs over and over, it went to the next or previous song (depending on which direction I pressed) then played it all the way through.

I then tried plugging the Carplay2Air unit into the extra port on my Carlinkit unit - with the exact same results.

Firmware versions don’t seem to matter and both devices don’t have to be on the same firmware either, although that might be a good idea.

😳🤯

I never had the 5 minute audio issue so I can’t check that; anyone with that bug have 2 units to test this with?
 
Last edited:
I just received my cplay2air unit. finally...

I have not really tried it out thoroughly. So far, I tried plugging it into my Opel Astra K 2017 make (intellilink R4.0) headunit, and have my iPhone XS max (IOS 13.5) connected to it. It managed to connect without any issue. So far music plays fine, but i realised that there was a small glitch in sound, when the carplay just got started up and I tried running both google maps (nav) and spotify at the same time. But it's just a very small glitch which goes off by itself. My cplay2air comes with 6.17 firmware out right of the box.

I have not tried to see if the 5min glitch occurs. I will try it later when i drive longer distance.
 
Last edited:
I just received my cplay2air unit. finally...

I have not really tried it out thoroughly. So far, I tried plugging it into my Opel Astra K 2017 make (intellilink R4.0) headunit, and have my iPhone XS max (IOS 13.5) connected to it. It managed to connect without any issue. So far music plays fine, but i realised that there was a small glitch in sound, when the carplay just got started up and I tried running both google maps (nav) and spotify at the same time. But it's just a very small glitch which goes off by itself. My cplay2air comes with 6.17 firmware out right of the box.

I have not tried to see if the 5min glitch occurs. I will try it later when i drive longer distance.

Could you do a screenshot of you system please? and also version number, in settings.

I have a Vauxhall with Intellilink Nav 900, basically the same I think as yours, but mine has in built (rubbish!) sat nav.

Mine has never worked, just flashes up the CarPlay icon sometimes.

What version is your dongle? Is there an update available? Mine is the CarLinkIt, but just the same as your CarPlay2Air.

A video showing it working would be great as well.

Thanks
 
I've been continuing my investigation into my reconnection problems on my 2020 Hyundai Palisade.

But can you maybe publish a recent logfile of the latest firmware? Both adapters broke during upgrade to 06-17.

I recorded some log files of a successful connection, and partial connection with black screen. I'm not sure how to add them to this post though. When I try to attach files, but I just see "An error occurred". Any tips?

Some observations:

1. The CarPlay USB port powers up as soon as I approach the door of the car with the key in my pocket. However the device only boots once the Head Unit starts. Looking at the log file, it takes about 30 seconds from boot to CarPlay connection. I timed it, and this corresponds with the time I press the start button in the car. I guess some handshaking occurs which triggers the Carlinkit to start booting Linux.

2. Although the Black screen is the biggest problem, I've noticed that sometimes other services fail to connect. Occasionally the Siri or Map voice doesn't work, or CarPlay gets stuck in night mode.

3. When CarPlay connects from a cold start, connection is usually successful. The connection problems always seem to occur on reconnection - after the car is turned off for a fem minutes for a short stop. Usually when stopping to fill with Petrol. The head unit seems to keep the connection until the car has been off for about 15 minutes. I decided to try a variation on @jlhunter2008 usb mod - only without the relay delay. I wired the power lines to a different USB socket, which powers on when the car starts. This has the undesirable side-effect of a slower connection each time you restart the car (usually it's instant), but hopefully with a more reliable connection. I've not tested this yet, I'll update if it works.

I sent both log files (successful connection, partial connection) to sales@carlinkit.com four days ago. I've not had a response. Looking at a diff of the two logs, I can see a few notable differences - some iAP2 messages fail "[CiAP2Session_CarPlay] HUD Message(0x1D06) XXXX Not implement!". There are some other differences too. I don't have access to the iAP2 protocol specification. Does anyone know the meaning of 0x1D06?

I'm hope the devs can find what causes the reconnection failures. If they fix that, the device will be good enough for me. Nicer splash screen would be the icing on the cake.

[UPDATE] Looks like my hypothesis was incorrect. I just tested the car with my modified cable - from cold start, I got a black screen. I guess It just randomly fails to connect sometimes. Disappointing!
 
Last edited:
[UPDATE] Looks like my hypothesis was incorrect. I just tested the car with my modified cable - from cold start, I got a black screen. I guess It just randomly fails to connect sometimes. Disappointing!

The next time you get a black screen, do not unplug the device. Instead try doing something in your vehicle that will cause a different screen to appear (climate controls, putting in reverse to trigger the backup camera, pressing the home button (if you have one), changing to audio source, etc) then if you get something displayed switch back to CarPlay mode.
 
The next time you get a black screen, do not unplug the device. Instead try doing something in your vehicle that will cause a different screen to appear (climate controls, putting in reverse to trigger the backup camera, pressing the home button (if you have one), changing to audio source, etc) then if you get something displayed switch back to CarPlay mode.

Actually I did this yesterday. The screen does indeed reconnect, but some other services remained disconnected. Yesterday music and display were connected, but the navigation voice didn’t work. The car would lower music volume, but no guidance speech was played.
 
Actually I did this yesterday. The screen does indeed reconnect, but some other services remained disconnected. Yesterday music and display were connected, but the navigation voice didn’t work. The car would lower music volume, but no guidance speech was played.

I can't speak for the other services, but technically the screen was always connected - it just did not get a proper video enable signal from the module. Jumping back and forth like that forces the module to resend it.
 
I can't speak for the other services, but technically the screen was always connected - it just did not get a proper video enable signal from the module. Jumping back and forth like that forces the module to resend it.

Yes, I think that's right. In the log file of the failed case I see the following:

Code:
01-01 12:00:28.349013 AM [VideoSource] VideoSource_control: inCommand=startvideo
01-01 12:00:28.369422 AM [CarPlayServer] ----------- _processScreenSetup Start: 0!
01-01 12:00:28.391340 AM [CarPlayServer] respParams={
    "streams" : 
    [
        {
            "type" : 110
            "dataPort" : 41013
        }
    ]
}
 
1970-01-01 12:00:29.257567 AM [AirPlay] Is  Wifi 
1970-01-01 12:00:30.258964 AM [AirPlay] Is  Wifi 
01-01 12:00:30.414451 AM ### [ASSERT] HudiAP2Server.cpp:358 "", "ret > 0" 
01-01 12:00:30.414856 AM [CHudiAP2Server] _iAP2readHandle quit!!! err = -6738/0xFFFFE5AE kNotReadableErr, ret = 0
01-01 12:00:30.420279 AM [Theme_0_Brain] Bluetooth_DisConnect(0025)
01-01 12:00:30.421197 AM [Theme_0_Brain] 自动连接设置为 5 秒
01-01 12:00:30.422580 AM [Theme_0_Brain]     From AccessoryDaemon Get ########## CarPlayControl(8) DeviceBluetoothNotConnected(1008)
01-01 12:00:30.422897 AM [BoxProtocol] CarPlayControl DeviceBluetoothNotConnected(1008)
01-01 12:00:30.423134 AM [CarPlayServer] _OnPhoneCommand me=0x00D6EBE8
01-01 12:00:30.454617 AM [RiddleBluetoothService_Interface_Control] delete link service IAP2
01-01 12:00:30.835284 AM [CHudiAP2Server] dispatch_main Quit!!
01-01 12:00:30.835656 AM [CHudiAP2Server] StopRecvBroadCastiAP!
(_get_SeriallNumber)+611: set box serial number: 2020.03.18.145541c5

Whereas on a successful connection I see:

Code:
01-01 12:00:32.050462 AM [VideoSource] VideoSource_control: inCommand=startvideo
01-01 12:00:32.079031 AM [CarPlayServer] ----------- _processScreenSetup Start: 0!
01-01 12:00:32.100413 AM [CarPlayServer] respParams={
    "streams" : 
    [
        {
            "type" : 110
            "dataPort" : 56663
        }
    ]
    "timingPort" : 33995
}
 
01-01 12:00:32.104296 AM [VideoSource] ###VideoConfig! w=1920 h=720
01-01 12:00:32.105109 AM [ArmadbdriverClient] I frame frameCount=1
01-01 12:00:32.192990 AM [Theme_0_Brain] Bluetooth_DisConnect(0025)
01-01 12:00:32.197968 AM [Theme_0_Brain] 自动连接设置为 5 秒
01-01 12:00:32.199414 AM [mfi_auth] MFI_AUTH_COP_REG_ADDR_AUTH_CTRL_AND_STATUS get status 16
01-01 12:00:32.200336 AM [Theme_0_Brain]     From AccessoryDaemon Get ########## CarPlayControl(8) DeviceBluetoothNotConnected(1008)
01-01 12:00:32.200522 AM [BoxProtocol] CarPlayControl DeviceBluetoothNotConnected(1008)
01-01 12:00:32.200631 AM [CarPlayServer] _OnPhoneCommand me=0x0047EBD8
01-01 12:00:32.201898 AM [mfi_auth] MFI_AUTH_COP_REG_ADDR_SIGNATURE_LEN 128
01-01 12:00:32.234052 AM [mfi_auth] MFI_AUTH_COP_REG_ADDR_SIGNATURE_DATA 0
1970-01-01 12:00:32.235673 AM [AirPlay] Is  Wifi 
1970-01-01 12:00:32.237983 AM [AirPlay] Is  Wifi 
01-01 12:00:32.282640 AM [CiAP2Session_CarPlay] Message 0xAA05 AuthSuccess
01-01 12:00:32.282896 AM [CHudiAP2Server] ###### IAP2 SchedulDone stat: AuthSuccess

I've no idea if this is actually where the handshake goes wrong - the log file appears to be a bunch of async processes, and it's not 100% clear which messages are related to each other, but it does look a bit odd. I also don't know which process is asserting.

My guess is that CarPlay has started, but the video handshake fails. It seems that each stream of data has a separate handshake, which would explain why I lose navigation voice. Switching to another view and back again would seem to reinitiate the video handshake. I'd love to see the iAP2 spec to understand better what's going on. A USB analyser would also be interesting, although of limited use without the ability to actually change the source code!

My hope is that if we can clearly understand what's failing, we could inform the support team in the hope that they will be able to fix these annoying bugs!
 
No, I'd say you found the right section for the handshake error. Looks like it tries to open a data port that is not supported by your vehicle which causes a failure. I'd look at mine and see what says, but the blank screen is so rare for me that I never remember to check.

I'm glad to see that you were able to confirm my instructions for video reset without unplugging the device works for oem head units as well as aftermarket. I'd asked people to try it a while ago but no one ever replied. Although I suspect a lot of people gave up on these as the number of people posting has drastically dropped off in the last month.
 
  • Like
Reactions: SuperMegaDrive
No, I'd say you found the right section for the handshake error. Looks like it tries to open a data port that is not supported by your vehicle which causes a failure. I'd look at mine and see what says, but the blank screen is so rare for me that I never remember to check.

I'm glad to see that you were able to confirm my instructions for video reset without unplugging the device works for oem head units as well as aftermarket. I'd asked people to try it a while ago but no one ever replied. Although I suspect a lot of people gave up on these as the number of people posting has drastically dropped off in the last month.
I guess that’s a good sign? Maybe it means the bugs are gradually being fixed for more cars? Most posts currently seem to be related to Mazda and GMC cars.
 
I guess that’s a good sign? Maybe it means the bugs are gradually being fixed for more cars? Most posts currently seem to be related to Mazda and GMC cars.

I can't speak for Mazda's infotainment division, but I really believe that the cause of the GM issues is the fact that the head unit hardware & software in the US and Australia is different from what they use in the rest of the world. Any bugs we see would not necessarily occur in other country models and vice versa, making them difficult to reproduce and fix.
 
Anyone running this using iOS 14 beta software? Interested to know if the adapter is broken by Apple updates. Heavily considering it for my MY2015 Golf GTi here in Australia.
 
Anyone running this using iOS 14 beta software? Interested to know if the adapter is broken by Apple updates. Heavily considering it for my MY2015 Golf GTi here in Australia.
Hi from NZ.

I’m running iOS 14 dev beta 2 (same as the public beta) with the OTA 17/6 update. It works flawlessly in my Audi RS3. Not a single issue, always reliably connects, ymmv in the GTI but the odds are reasonable given it’s a VAG vehicle.

I used it with iOS 14 dev beta 1 from day one also, no issues there either.
 
Anyone running this using iOS 14 beta software? Interested to know if the adapter is broken by Apple updates. Heavily considering it for my MY2015 Golf GTi here in Australia.

I’m running iOS 14. Works even better than 13 in my Maserati. USB-C dongle pots faster, no delay changing tracks and touch screen super responsive.
 
I can't speak for Mazda's infotainment division, but I really believe that the cause of the GM issues is the fact that the head unit hardware & software in the US and Australia is different from what they use in the rest of the world. Any bugs we see would not necessarily occur in other country models and vice versa, making them difficult to reproduce and fix.

I have a 2016 Silverado 2500HD LT that's spec'd for Qatar (middle east) and I had the 5 minutes distortion before I updated from January to March. I don't know, maybe my vehicle has the same hardware and software as the US spec'd vehicles.
 
I have a 2016 Silverado 2500HD LT that's spec'd for Qatar (middle east) and I had the 5 minutes distortion before I updated from January to March. I don't know, maybe my vehicle has the same hardware and software as the US spec'd vehicles.

Possible. Some people in that area have said they have the same hardware and some people have said they have different hardware. TBH, I'm not sure. I've also pretty much exhausted my experience with GM's Mylink systems at this point.
 
Yeah I checked no 7/8 OTA. I might install it over OTA 06/17. Old March 4th non OTA was great for me and some others. 6/17 is about the same.
 
Okay, now for something even stranger in my situation. Plugging one of my adapters directly into my Pioneer's USB port, plugging my car's usb wiring harness into the adapter then plugging the other adapter into my console's USB port results in a consistent no black screen boot up. Does this no matter which adapter is plugged in to each end. if I don't plug one of the adapters directly into the radio first then I get random black screens at boot.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.