Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
It was actually delivered today to my home in California. I ordered it this Tuesday 5/5/20.

great job to Carlinkit and DHL total 3 days from when I ordered it to when it was delivered.





it came with Firmware 3-18-20

I paid 20.00 extra for fast shipping.


Weird. I got mine same way as you 5 days ago (DHL to FL in like 3 days) from same link and mine had 1-22-20 firmware.
 
Arghhhhhhh .... just updated to IOS 13.5 Beta 5 Beta 4 (sorry, typo) and it killed my 100% working fine device. Beta 4 was fine. Now I just get a blank screen after connecting.
 
Last edited:
My usb c version came with the 1.22 firmware version. What’s the difference between the 3.18 and 1.22? Does anyone knowV
 
My usb c version came with the 1.22 firmware version. What’s the difference between the 3.18 and 1.22? Does anyone knowV

Nope, it's not like Carlink provides release notes. Maybe somebody from Carlink will post or send them email. It's not available for download.
 
Nope, it's not like Carlink provides release notes. Maybe somebody from Carlink will post or send them email. It's not available for download.
I emailed them regarding my USB-C issue and asked about the firmware. Their reply was:

From: sales@carlinkit.com <sales@carlinkit.com>
Sent: Friday, May 8, 2020 4:17 AM
To: me

Subject: Re: RE: Other USB C cables or adapters will not fit

Hi, friend, sorry, the latest firmware is indeed the 2020.01.22, because of the COVID-19, we haven't released any new firmwares since 2020.01.22 version. So when you check updates, it will shows that it is up to date.

Where did you see that there is a 2020.-3.18 version? And I also need to inform you that if the product works normally in your car, you don't have to update it to the latest firmware, because the new firmwares usually updated to resolve the issues that occurs in some car models, not update new functions.
 
Arghhhhhhh .... just updated to IOS 13.5 Beta 5 and it killed my 100% working fine device. Beta 4 was fine. Now I just get a blank screen after connecting.
Nope, it's not like Carlink provides release notes. Maybe somebody from Carlink will post or send them email. It's not available for download.
I emailed them regarding my USB-C issue and asked about the firmware. Their reply was:

From: sales@carlinkit.com <sales@carlinkit.com>
Sent: Friday, May 8, 2020 4:17 AM
To: me

Subject: Re: RE: Other USB C cables or adapters will not fit

Hi, friend, sorry, the latest firmware is indeed the 2020.01.22, because of the COVID-19, we haven't released any new firmwares since 2020.01.22 version. So when you check updates, it will shows that it is up to date.

Where did you see that there is a 2020.-3.18 version? And I also need to inform you that if the product works normally in your car, you don't have to update it to the latest firmware, because the new firmwares usually updated to resolve the issues that occurs in some car models, not update new functions.

My takeaways:

1 - they don't even know that 3.18 is loaded on shipping units or what it is? What's up with that?
2 - RE:iOS 13.5: After all of our diligence and money invested in these products, we literally are an iOS update away from pulling that lightening cable out while they are "Hi friend, we are working on it and we have a major update coming soon" Soon will = months
3 - Related to 2., or that will be it for product development and hacking Apple's code.

Hey we all knew what we were getting into. It's just the irony that's gonna suck.
 
Arghhhhhhh .... just updated to IOS 13.5 Beta 5 and it killed my 100% working fine device. Beta 4 was fine. Now I just get a blank screen after connecting.

Could very well just be a bug that will be fixed in Beta 6. Have you tried deleting the CarPlay pairing (and BT and WiFi connections) and setting it up again from scratch? Does CarPlay continue to work fine plugged in?

Worse comes to worst, at least you can downgrade.

And yes, all of us Carlinkit owners will need to be very cautious about iOS updates on our iPhones. Fortunately, usually downgrading is possible in the first few days after Apple releases a new version. But yeah, we are 100% at the mercy of Apple here.
 
Could very well just be a bug that will be fixed in Beta 6. Have you tried deleting the CarPlay pairing (and BT and WiFi connections) and setting it up again from scratch? Does CarPlay continue to work fine plugged in?

Worse comes to worst, at least you can downgrade.

And yes, all of us Carlinkit owners will need to be very cautious about iOS updates on our iPhones. Fortunately, usually downgrading is possible in the first few days after Apple releases a new version. But yeah, we are 100% at the mercy of Apple here.

No, not yet. Been wanting to do that but have just been too lazy. I'll try later tonight.
 
Update: when the usb-c version with fw 2020.03.18.1455 is used with a compatible aftermarket headunit in a US Gen 1 Cruze (probably any/all US GM vehicles from 2010 to 2015/16 except the Sonic which used a different radio and wiring), the steering wheel controls will stick when skipping tracks backwards/forwards until the opposite direction is pressed. Then it eventually will fix itself. Does not occur when touchscreen controls are used instead or when using wired CarPlay. Tested with both Metra and idatalink maestro wiring adapters with same results - definitely the Carlinkit adapter.

Uploaded a log.... it took 2 minutes to go from 52% to 100%. A heck of a lot of data to sort through. Wonder what they’ll say/think when they see the “non-existent” firmware version.

There is also a momentary audio pause when the CarPlay screen(s) lose and gain focus.

In regards to the earlier discussion about wireless CarPlay and GPS, I have the following to add: aside from the VSS wiring, the WC6600NEX has zero gps functionality - forcing CarPlay and Android Auto to rely entirely on the smartphone’s own positioning system. So while GPS being built into a headunit may be in the CarPlay sdk as the recommended method, it is by no means required/mandatory for wireless operation..

(Edited to show correct model headunit being referenced.)
 
Last edited:
Arghhhhhhh .... just updated to IOS 13.5 Beta 5 and it killed my 100% working fine device. Beta 4 was fine. Now I just get a blank screen after connecting.

Not surprising since Beta 5 isn’t released yet to either developers or public beta. 😁
 
Last edited:
Sorry, TYPO. Obviously Meant 4.

Hehehe, I couldn't resist teasing. Was a looooooooooong day at work :) Although, you have to admit that it WOULD explain the issue you encountered.

Edit: I downloaded 13.5 beta 4 to my SE 2020 and my carlinkit USB-C adapter is still working fine (aside from the steering wheel control issue). If resetting your settings doesn't fix it, it might be an issue with that 2020.01.22 firmware you have.
 
Last edited:
In regards to the earlier discussion about wireless CarPlay and GPS, I have the following to add: aside from the VSS wiring, the C2550NEX has zero gps functionality - forcing CarPlay and Android Auto to rely entirely on the smartphone’s own positioning system. So while GPS being built into a headunit may be in the CarPlay sdk as the recommended method, it is by no means required/mandatory for wireless operation..

Apple's CarPlay spec states that using the car's GPS is optional (but recommended) for Wired CarPlay (which is what the C2550NEX has).

But for a manufacturer to implement Wireless CarPlay, Apple's spec requires the car to supply a GPS signal. This is not a technical requirement (as we've seen that the Carlinkit is able to use the phone's GPS signal just fine). It's a licensing requirement Apple put in place to help minimize the drain on the iPhone's battery (which is already heightened because the phone is passing large amounts of video/audio over WiFi to the car's head unit).
 
Apple's CarPlay spec states that using the car's GPS is optional (but recommended) for Wired CarPlay (which is what the C2550NEX has).

But for a manufacturer to implement Wireless CarPlay, Apple's spec requires the car to supply a GPS signal. This is not a technical requirement (as we've seen that the Carlinkit is able to use the phone's GPS signal just fine). It's a licensing requirement Apple put in place to help minimize the drain on the iPhone's battery (which is already heightened because the phone is passing large amounts of video/audio over WiFi to the car's head unit).

I mentioned the wrong model. I meant the WC6600NEX, not the C2550NEX (which I have but am still considering upgrading from). The WC6600NEX, which is Pioneer's newest modular HU, also lacks built in GPS functionality, yet provides wireless carplay and wireless android auto. Unless Pioneer was granted an exception, it is not a licensing requirement either.
 
Arghhhhhhh .... just updated to IOS 13.5 Beta 5 Beta 4 (sorry, typo) and it killed my 100% working fine device. Beta 4 was fine. Now I just get a blank screen after connecting.
Just thought it was worth mentioning. I’m on the public beta and just went out and tested it and everything works fine at the moment.
 
Ya I just bought mine from Amazon and they are quoting an August delivery lol. Hopefully iOS 14 doesn’t break functionality but I guess we should know that after the beta is released at WWDC.
Come back on June 22nd. I will have the iOS 14 Beta 1 on my phone minutes after the keynote. The very first test will be with my CarPlay2Air.
[automerge]1589028605[/automerge]
Arghhhhhhh .... just updated to IOS 13.5 Beta 5 Beta 4 (sorry, typo) and it killed my 100% working fine device. Beta 4 was fine. Now I just get a blank screen after connecting.
I'm running the same version and my CarPlay2Air works fine. I'm so glad that I am not responsible for regression testing at Apple. There are getting to be so many different combinations of hardware and software that it's not possible to know what is going to happen. I should add that I had that blank screen once in a beta with wired Carplay. Apple fixed it in the next build.
 
Last edited:
Arghhhhhhh .... just updated to IOS 13.5 Beta 5 Beta 4 (sorry, typo) and it killed my 100% working fine device. Beta 4 was fine. Now I just get a blank screen after connecting.

Running CP2A 3.18 and was working fine until 13.5 beta update. Now after exactly 5 minutes of streaming music the sound is all garbage. if I change to another playlist or Apple Music station it is good for another 5 minutes. :(
 
I would like to point out that as long as CarPlay2Air *IS* telling the truth and they are using the same carplay compatible chipset that Apple uses, then any issues we face "should" also be faced by all wireless CarPlay users. Obviously, take their claim with a grain of salt. I haven't seen CarLinkit claim to source the chip from Apple, but assuming the hardware is physically the same as the CP2A (I haven't heard of anyone taking both apart and physically comparing the internals yet) and not just the software, it should be the same for them.

LOL, I just had a thought. There is a blog post by Carlinkit regarding counterfeit versions of their devices. They don't specify any names, but I suspect that CP2A is one place they are "pointing"..
 
Last edited:
I would like to point out that as long as CarPlay2Air *IS* telling the truth and they are using the same carplay compatible chipset that Apple uses, then any issues we face "should" also be faced by all wireless CarPlay users. Obviously, take their claim with a grain of salt. I haven't seen CarLinkit claim to source the chip from Apple, but assuming the hardware is physically the same as the CP2A (I haven't heard of anyone taking both apart and physically comparing the internals yet) and not just the software, it should be the same for them.

LOL, I just had a thought. There is a blog post by Carlinkit regarding counterfeit versions of their devices. They don't specify any names, but I suspect that CP2A is one place they are "pointing"..

I highly doubt they are using the same
Chipset as Apple.
 
I highly doubt they are using the same
Chipset as Apple.

I don't think they are using the same chipset. I popped my open since it doesn't work. And there's not much there. The main processor is an AMTEL AT91SAM9260, flash chip, and a bluetooth/wifi processor module, plus some supporting components. I can post pictures if anybody is interested. There is a label on the board, U2W. search that on eBay and
I find pictures of the same card.

Here's the processor. I would think they are just emulating and iPhone. When you plug it into a Mac, it just says iPhone.

  • ARM926 ARM Thumb Processor running up to 210 MHz
  • 8-Kbyte Data Cache, 8-Kbyte Instruction Cache
  • Memory Management Unit
  • 8 Kbytes of SRAM, single-cycle access
  • 32 Kbytes of ROM embedding standard bootstrap
  • 32-bit External Bus Interface (EBI) supporting SDRAM, LPSDRAM, Static Memory, Burst Flash, Glueless Connection to CompactFlash® and NAND Flash/SmartMedia® with 1-bit ECC
 
It's actually a system on a chip approach so to speak (more like iPhone in a chip?). Thing is, what does Apple themselves use? Or more to the point: what do official Carplay Wireless devices use?
 
Last edited:
It's actually a system on a chip approach so to speak (more like iPhone in a chip?). Thing is, what does Apple themselves use? Or more to the point: what do official Carplay Wireless devices use?

The processor is just an off the shelf generic, will do what you program it to do. But like you said it's a system on on a chip. It's just emulating an iPhone via software. For devices that do native wireless CarPlay, the phone is joined directly to the head unit. This is more of a man in the middle type implementation.

The ARM®-based SAM9260 running up to 210 MHz embeds Full Speed USB host and device interfaces, a 10/100 Ethernet MAC and an image sensor interface, as well as standard peripherals such as a Multimedia Card Interface (MCI), I2S, USARTs, master/slave SPIs, 16-bit Timers, a TWI and four-channel 10-bit ADC. The external bus interface features controllers for SDRAM and static memories including NAND flash and CompactFlash. The SAM9260 is available in 217-ball LFBGA and 208-pin QFP packages.
 
I don't think they are using the same chipset. I popped my open since it doesn't work. And there's not much there. The main processor is an AMTEL AT91SAM9260, flash chip, and a bluetooth/wifi processor module, plus some supporting components. I can post pictures if anybody is interested. There is a label on the board, U2W. search that on eBay and
I find pictures of the same card.

Here's the processor. I would think they are just emulating and iPhone. When you plug it into a Mac, it just says iPhone.

  • ARM926 ARM Thumb Processor running up to 210 MHz
  • 8-Kbyte Data Cache, 8-Kbyte Instruction Cache
  • Memory Management Unit
  • 8 Kbytes of SRAM, single-cycle access
  • 32 Kbytes of ROM embedding standard bootstrap
  • 32-bit External Bus Interface (EBI) supporting SDRAM, LPSDRAM, Static Memory, Burst Flash, Glueless Connection to CompactFlash® and NAND Flash/SmartMedia® with 1-bit ECC

I would also guess that they aren't using the same system that wireless CarPlay would use but rather emulating a "wired USB connection" in simple terms. I'd imagine Apple could shut this down if they wanted to. Hopefully they don't care.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.