Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.
I can't even... Can you imagine describing this one to their engineers directly? "So, I took one, of each down stream brand adapter, then..."

Brawny, StLou! Just, brawny. I love this. Good stuff. I'm confident, that with all y'all looking after this baby, it will walk. Then, it will run!

Beta? R&D, QA?
 
Good to hear guys! Is the Carplay2Air dongle USB-C based? Or is that the CarLinkIt model?

Which is the recommended one to purchase out of the two, is there a consensus here?

Also, has the ~5min audio garbling issue been quashed yet?
 
Good to hear guys! Is the Carplay2Air dongle USB-C based? Or is that the CarLinkIt model?

Which is the recommended one to purchase out of the two, is there a consensus here?

Also, has the ~5min audio garbling issue been quashed yet?

CARPLAY2air isnt (unless they have caught up) the USB-C version. As the USB-C version is the newest model i would go with that one.
 
Good to hear guys! Is the Carplay2Air dongle USB-C based? Or is that the CarLinkIt model?

Which is the recommended one to purchase out of the two, is there a consensus here?

Also, has the ~5min audio garbling issue been quashed yet?
~5min audio still garbled. No fix yet.
 
I can't even... Can you imagine describing this one to their engineers directly? "So, I took one, of each down stream brand adapter, then..."

Brawny, StLou! Just, brawny. I love this. Good stuff. I'm confident, that with all y'all looking after this baby, it will walk. Then, it will run!

Beta? R&D, QA?

Actually, I did send it almost exactly that way. Still waiting for a reply.
 
  • Like
Reactions: BUXjr
2018 Denali...help please or anyone else?

Hi, I still couldn't get my Cplay2air to work in my 2019 Silverado....it does in my Vette, so I tried updating it, now I'm not even getting any red lights. Is this now bricked and no good? If so, how do I get it to work again, if we can?
Thanks, Jerry
 
Last edited:
2018 Denali...help please or anyone else?

Hi, I still couldn't get my Cplay2air to work in my 2019 Silverado....it does in my Vette, so I tried updating it, now I'm not even getting any red lights. Is this now bricked and no good? If so, how do I get it to work again, if we can?
Thanks, Jerry

Is your Vette MyLink 2 or 3? is your Silverado Mylink 2 or 3?
 
I believe my 2016 Vette in a 2......my 2019 should be a 3...tried it again, no lights at all. Not sure how to tell, Im guessing.
Thanks

As far as I know/understand, Mylink 3 support is still a MAJOR work in progress.
 
Last edited:
  • Like
Reactions: Lyons00
~5min audio still garbled. No fix yet.
Not only is it NOT fixed yet, but brand new Carlinkit adapters are shipping now with 2020.06.17.0549 preinstalled. I just got mine, yesterday (from Amazon). So what I had hoped to be a path backwards, is just a clone of my already non-functioning unit. Ugh. But at least this one is USB-C? Yay?
 
Not only is it NOT fixed yet, but brand new Carlinkit adapters are shipping now with 2020.06.17.0549 preinstalled. I just got mine, yesterday (from Amazon). So what I had hoped to be a path backwards, is just a clone of my already non-functioning unit. Ugh. But at least this one is USB-C? Yay?
Not to state the obvious, but this company has no rhyme or reason for what shipping firmware's it installs before shipping. They really don't have development path. Sadly it has gotten worse over the last 8 months. On top of preinstalled beta firmware and I use the term beta loosely because every firmware is beta, they really don't have the ability to downgrade or swap out firmware without the high risk of ending up with a brick.

It's really too bad, they have a great hardware base of a product and a hamster on wheel developing or not developing.
 
Just an FYI that the 07.08 firmware does not work properly on my Ford SYNC3 system. CarPlay connects, and audio comes through the car speakers but the screen stays on the "Connecting" screen and never displays the CarPlay interface. I already tried the usual steps of rebooting both devices, deleting BT and WiFi connections and re-pairing, etc. No dice.

Hopefully I will be able to flash backwards to one of the June firmwares--will try that today. I really wish I could just go back to 03.04. In retrospect that was the most stable and reliable firmware for my vehicle.
 
Just an FYI that the 07.08 firmware does not work properly on my Ford SYNC3 system. CarPlay connects, and audio comes through the car speakers but the screen stays on the "Connecting" screen and never displays the CarPlay interface. I already tried the usual steps of rebooting both devices, deleting BT and WiFi connections and re-pairing, etc. No dice.

Does your iPhone show that it is connected to CarPlay? Sounds like it's just sending the audio over Bluetooth to your car. In that case you might want to delete the phone from the car and the car from the phones bluetooth settings.
 
Just an FYI that the 07.08 firmware does not work properly on my Ford SYNC3 system. CarPlay connects, and audio comes through the car speakers but the screen stays on the "Connecting" screen and never displays the CarPlay interface. I already tried the usual steps of rebooting both devices, deleting BT and WiFi connections and re-pairing, etc. No dice.

Hopefully I will be able to flash backwards to one of the June firmwares--will try that today. I really wish I could just go back to 03.04. In retrospect that was the most stable and reliable firmware for my vehicle.

I'm in the same boat. Running Sync 3.4 and after installing the 07.08 firmware on CPlay2Air, I get a connecting screen, then a flash to the Sync3 home screen, and immediately back to connecting...where it stays.

I was unable to flash backwards to 06.17.

I had deleted all signs of the previous setup, from Sync and the iPhone.
 
Does your iPhone show that it is connected to CarPlay? Sounds like it's just sending the audio over Bluetooth to your car. In that case you might want to delete the phone from the car and the car from the phones bluetooth settings.

Yes it does show as connected. And I cannot press the Cancel button that shows at the bottom of the "Connecting" screen on the head unit. I had already tried deleting all the pairing info on both ends.

I'm in the same boat. Running Sync 3.4 and after installing the 07.08 firmware on CPlay2Air, I get a connecting screen, then a flash to the Sync3 home screen, and immediately back to connecting...where it stays.

I was unable to flash backwards to 06.17.

I had deleted all signs of the previous setup, from Sync and the iPhone.

🤬 Ughhhh. I was afraid of that. I don't know why they are blocking people from reverting--especially because their firmware updates seem to always break something for someone.

Not a happy camper. I wish I had just stayed on 03.04. Not willing to buy another adapter at this point, so I guess I will just send them a log file and hope they fix it eventually.
 
Yes it does show as connected. And I cannot press the Cancel button that shows at the bottom of the "Connecting" screen on the head unit. I had already tried deleting all the pairing info on both ends.



🤬 Ughhhh. I was afraid of that. I don't know why they are blocking people from reverting--especially because their firmware updates seem to always break something for someone.

Not a happy camper. I wish I had just stayed on 03.04. Not willing to buy another adapter at this point, so I guess I will just send them a log file and hope they fix it eventually.
Agreed, blocking us from backward firmware flashing is Draconian and just plain silly. We paid for, and own, the hardware. Let us run whichever version of the software we want! I too would be WAY better off with 2020.03.04.xxxx firmware. It's positively aggravating that I can't go back to it.
[automerge]1594750464[/automerge]
There is a new OTA version! 2020.07.01.1234, in the 2020-07-07 folder. Just downloaded it. Anyone tried it yet?

JSON string: ${"filePath":".\/download\/2020-07-07\/U2W_Update.img","fileSize":"717332","fileName":"U2W_Update.img","version":"2020.07.01.1234","updateTime":"2020-07-14 20:59:29","updateLog":"Resolve problem of upgrade failure"}

What do we suppose, "Resolve problem of upgrade failure" means? Intriguing.
 
Last edited:
There is an update file from 2020-07-08. Not sure whether that’s really a new build.
Yes, a few users here have USB flashed that one. Purportedly, it's 2020.07.08.1306. However, there was no discernable difference between this and 2020.06.17.0549. Still has the 5min audio glitch for most GM owners (most meaning, some, not all, as StLou has pointed out).

In the words of John Mayer, "that's why were waiting, waiting on the...firmware to change." ;)
 
I'm in the same boat. Running Sync 3.4 and after installing the 07.08 firmware on CPlay2Air, I get a connecting screen, then a flash to the Sync3 home screen, and immediately back to connecting...where it stays.

I was unable to flash backwards to 06.17.

I had deleted all signs of the previous setup, from Sync and the iPhone.

Happy to say I was able to flash back to 06.19 (didn't try .17 as I didn't have it readily available).

Do you have the older style adapter, or the newer USB-C based one? Mine is the former--not sure if that is why I was able to flash backwards. But you may want to try 06.19 if you haven't already tried it. It's not as good as 03.04 for me (I sometimes get a black screen, whereas that never happened with the March firmware), but at least it resurrected my adapter!

Learned my lesson on the firmware updates. Probably will wait a month or so (or for reports from other Ford owners) before taking the plunge.
 
  • Like
Reactions: BUXjr
Happy to say I was able to flash back to 06.19 (didn't try .17 as I didn't have it readily available).

Do you have the older style adapter, or the newer USB-C based one? Mine is the former--not sure if that is why I was able to flash backwards. But you may want to try 06.19 if you haven't already tried it. It's not as good as 03.04 for me (I sometimes get a black screen, whereas that never happened with the March firmware), but at least it resurrected my adapter!

Learned my lesson on the firmware updates. Probably will wait a month or so (or for reports from other Ford owners) before taking the plunge.

I wonder if today’s OTA update to fix problem of upgrade failure allows us to downgrade now? Maybe downgrade to 3-4-20 again?
 
I wonder if today’s OTA update to fix problem of upgrade failure allows us to downgrade now? Maybe downgrade to 3-4-20 again?
Bro, Denali, I like what you are laying down there. I'm not totally convinced that the 100% successful OTA update that I did, actually did anything. It seemed like it worked, but then, after reboot, and a visit to 192.168.50.2, I was presented with the option to "Discover a new version (2020.07.01.1234 | Size: 0.68MB)", again. So I did it again. Twice total. Both times, 100% successful and caused a reboot.

A quick drive around the neighborhood revealed the audio glitch, but I be a blue nosed gopher if it didn't take a little bit longer to occur. Maybe 8 minutes? I really wasn't watching too closely, but it was certainly MORE than the usual 5 minutes. Maybe progress?

Do you think the OTA updates are capable of doing a partial firmware update? Or do you think it just replaces some files in the Linux system? Is that even possible?

I guess I've got nothing to lose trying...I'll have to see if I have 2020.03.04 laying around. Did you try?
 
Bro, Denali, I like what you are laying down there. I'm not totally convinced that the 100% successful OTA update that I did, actually did anything. It seemed like it worked, but then, after reboot, and a visit to 192.168.50.2, I was presented with the option to "Discover a new version (2020.07.01.1234 | Size: 0.68MB)", again. So I did it again. Twice total. Both times, 100% successful and caused a reboot.

A quick drive around the neighborhood revealed the audio glitch, but I be a blue nosed gopher if it didn't take a little bit longer to occur. Maybe 8 minutes? I really wasn't watching too closely, but it was certainly MORE than the usual 5 minutes. Maybe progress?

Do you think the OTA updates are capable of doing a partial firmware update? Or do you think it just replaces some files in the Linux system? Is that even possible?

I guess I've got nothing to lose trying...I'll have to see if I have 2020.03.04 laying around. Did you try?

I feel they can update some files within the firmware with minor updates like the one we just saw. If you hang tight I can test it when I get home in 4 hours. I have a Carlinkit USB-c on 7-8-20 I have nothing to lose on that one. I agree with you also. With today’s minor firmware OTA update it seems to take 7 to 8 minutes now for the glitching to start on GM.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.