Many have worked around this by flashing an older firmware. I've got them all if you need one. I think I would try 1.22. If you try a bunch of old FW's and they don't resolve the issue, reach to Carlinkit.
Damn, that's the only one I don't have as it was released OTA. 7-29?Can you kindly provide a link or a zip file to 2020-08-10?
My car has wireless CarPlay built in, along with a wireless charging pad too.
Can you kindly provide a link or a zip file to 2020-08-10?
No worries, isn't 7-29 the same as 8-4?Damn, that's the only one I don't have as it was released OTA. 7-29?
@simps100 & @DarkEvilRivas - since you guys are the ones who saw the new interface, can you report what exact adapter you have (Carplay2Air, Carlinkit USB-A, or Carlinkit USB-C)?
There's got to be some pattern here. I will try flashing it later today and see what I get.
@simps100 & @DarkEvilRivas - since you guys are the ones who saw the new interface, can you report what exact adapter you have (Carplay2Air, Carlinkit USB-A, or Carlinkit USB-C)?
There's got to be some pattern here. I will try flashing it later today and see what I get.
Was reading through the thread again and decided to check for OTA update. There was one available and applied it. After the unit did not restart and reconnect as it had prior. Then the problems began. LOL
Long story short, the Carlinkit 2.0 dongle wouldn't connect to the head unit or phone.
A manual update seemed necessary as the thing was unusable. Just flashed it manually and am giving it a few minutes on the supply before I unplug and try again in the car.
View attachment 948412
Manual update seemed to work. It allowed me to have CarPlay connect once. After that it never connected again, almost like the BT module in Carlinkit wasn't functional.A manual update seemed necessary as the thing was unusable. Just flashed it manually and am giving it a few minutes on the supply before I unplug and try again in the car.
So much for a pattern Dano, I have the new interface on both my CarPlay2Air and USB-C Carlinkit devices.
Haha, well I got it on my USB-C Carlinkit. Haven't tried flashing my USB-A version yet.
For the record, the "Connecting to iPhone" screen looks almost identical to before. It's the initial screen before that that looks very different.
Not sure why some folks aren't seeing it.
View attachment 948416
Edit: I should add that as soon as I plugged the adapter in and started the car I was prompted to set up a new CarPlay connection. I think someone earlier in the thread said they had the same experience. Did those of you seeing the old interface have to do that?
Maybe it's car-specific. For the record my car uses Ford Sync 3.
Haha, well I got it on my USB-C Carlinkit. Haven't tried flashing my USB-A version yet.
For the record, the "Connecting to iPhone" screen looks almost identical to before. It's the initial screen before that that looks very different.
Not sure why some folks aren't seeing it.
Edit: I should add that as soon as I plugged the adapter in and started the car I was prompted to set up a new CarPlay connection. I think someone earlier in the thread said they had the same experience. Did those of you seeing the old interface have to do that?
Maybe it's car-specific. For the record my car uses Ford Sync 3.
Did you do OTA or USB?
Maybe the OTA Upgrade leaves the phones paired but updating via USB resets the adapter (paired phones) with this update?
Also, I presume there are a bunch of Mac users on here. If you are using a Mac to format media, the Mac hides files on the disks, spotlight files and a couple other hidden files. I learned this the hard way from Pioneer and their firmware update process being almost impossible. But, if they are sticky about having no other files on the media and you are using a Mac to format the stick and copy the IMG file, then you need to remove the hidden files using the Terminal.
Process I use is to:
$ cd /Volumes/UNTITLED/
- Format the disk
- Copy the firmware IMG file to the disk
- Launch Terminal
- Perform the following:
$ ls -al
total 13472
drwxrwxrwx@ 1 gymmy staff 16384 Aug 28 15:59 .
drwxr-xr-x+ 10 root wheel 320 Aug 28 15:59 ..
drwxrwxrwx 1 gymmy staff 16384 Aug 28 15:59 .Spotlight-V100
-rwxrwxrwx 1 gymmy staff 6845355 Aug 25 21:18 ._U2W_Update.img
drwxrwxrwx 1 gymmy staff 16384 Aug 28 15:59 .fseventsd
-rwxrwxrwx 1 gymmy staff 6845355 Aug 25 21:18 U2W_Update.img
$ rm -r .Spotlight-V100/ .fseventsd/ ._U2W_Update.img
Then immediately eject the media.
Not sure how you quoted a post that I had edited to be a lot different about an hour earlier... but it looks like you missed a lot more information from me. Might want to re-read it.
How did you set up your previous connection? Manually via Bluetooth? or did you go to Settings>General>CarPlay?
I updated both using USB and was not prompted by either one to make a new CarPlay connection.
I’ve never run into any issues with the macOS hidden files and trying to update either CP2A or Carlinkit device.
By manually do you mean connecting the phone to the Carlinkit via USB cable? Hard to remember for sure, but I most likely used Bluetooth to set up the CarPlay connection.
Interesting. I guess this lends credence to the theory that maybe the variations people are seeing with the same firmware come down to their particular vehicle.
A new update again with the normal size of 6.8 MB.
Is it possible with new UI to change factory default Bluetooth name of USB dongle or it still gets name automatically based on car manufacturer (Ford cars get SYNC) and four digits randomly? I.e. SYNC-1234.