Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Yes... background mode means it skips showing you the ugly 'connecting' screen. It connects in the background and once it's connected, just launches to Apple CarPlay. It's a nice way to look more integrated.
And there are difference background modes for red UI and blue/green UI FW? How is it different? I thought FW was exactly the same except for the menu design!?
 
And there are difference background modes for red UI and blue/green UI FW? How is it different? I thought FW was exactly the same except for the menu design!?
I don't think there's a difference in the behavior of Background Modes... can anyone confirm?
 
The background mode toggle has never done anything for me, fwiw; still see the connection screen most of the time. I'm sure @VLud will be by with his custom firmware + autokit UI any day now. Patience, everyone.
 
It has the bluisch/greenish UI

For me, background mode works perfect. It does not show the connecting screen and pops up (in front) when Carplay is connected.
I wonder if this is something for specific units. For instance, I'm using Ford Sync... and it handles "Background" perfectly.
 
I wonder if this is something for specific units. For instance, I'm using Ford Sync... and it handles "Background" perfectly.
Mine is a SEAT Leon ST FR from 2019 with NAVI SYSTEM PLUS head unit (Volkswagen MIB 2 based). The "connection" screen does show up for me with Background Mode enabled, only for a very short amout of time though. Enough to cancel connection though.
 
Info on relay, but nothing on frame rate. The default is zero, what is the max?
If you remove the 0 inside the field, it will tell you min and max values. Maximum is 60fps. Sensible values are probably 30 and 60fps. It is what the adapter tells the iPhone to encode video (CarPlay UI) in. 60fps will give you a smooth experience but increase bandwidth. 0 will most probably use the frame rate proposed by the head unit.
 
You dont need a roll back option in custom firmware.

Ludwig has provided a script to roll back from March. Add the U2W.sh script + old firmware (U2W_AUTOKIT_Update.img or U2W_Update.img) + ARMimg_maker on USB and roll back.

It seems only people that are SOL are who are on the Custom FW and have a incompatible WIFI Driver

I think i found it! if you are in custom firmware yo can rollback whatever version you want. If you are in March version you have to use the Ludwig's script
 
  • Like
Reactions: chari
I am a bit shocked with respect to security. I just recognized that the adapter retains the initial and well known '12345678' passphrase. So everybody can easily connect to it, open the settings page via web browser and do harm.

IMHO the adapter should generate a secure passphrase or use some MAC address. Nobody has to manually connect to the adapter...
 
You probably can't do hell of a lot in neither, the car nor the phone. But one can initiate a firmware update for example which can go wrong if not properly applied...
 
Just got mine today (Carlinkit 2.0) for my 2021 Jeep Wrangler.

So far it's done nothing but constantly reboot, flake out, and ultimately cause CarPlay to go completely insane on the uConnect even with a hardwire connection now. It will sometimes work for up to 10 minutes before it reboots.

I am trying to update the FW to see if latest version helps, but nothing I do seems to get it to take. I've formatted multiple USB stick on Windows, FAT32, 1024K block size. Let the thing boot up to red light, then inserted USB and then - nothing happens. Any other secrets to getting the FW to update?

So far not impressed at all with this thing, was hoping that maybe a fresh FW would help it out but I can't even get it to do that.

Thanks!
 
I think i found it! if you are in custom firmware yo can rollback whatever version you want. If you are in March version you have to use the Ludwig's script
Thank you for your posting. It was very helpful.
Maybe it's my mistake, but I'll share what I did just in case.

Before updating, I confirmed by 192.168.50.2, then VER shows 2021.03.07.0001 (This is CustomFW 2021.03.06)

Then Update by USB with U2W.sh + ARMimg_maker + U2W_Update.img (CustomFW 2021.02.02), then I confirmed it again, but VER shows 2021.03.07.0001 again.

so Update again with U2W.sh + ARMimg_maker + U2W_Update.img (Official FW 2021.01.28),then confirm it.
Message show "Discover a new version" and proposed VER:2021.03.06.1413 , so I confirmed I can rollback to Official FW. then I update it with Official FW 2021.03.06 (USB is only stored U2W_Update.img). after that, it show "It is the latest version" and VER:2021.03.06.1343
 
  • Like
Reactions: Azazel1988
Thank you for your posting. It was very helpful.
Maybe it's my mistake, but I'll share what I did just in case.

Before updating, I confirmed by 192.168.50.2, then VER shows 2021.03.07.0001 (This is CustomFW 2021.03.06)

Then Update by USB with U2W.sh + ARMimg_maker + U2W_Update.img (CustomFW 2021.02.02), then I confirmed it again, but VER shows 2021.03.07.0001 again.


so Update again with U2W.sh + ARMimg_maker + U2W_Update.img (Official FW 2021.01.28),then confirm it.
Message show "Discover a new version" and proposed VER:2021.03.06.1413 , so I confirmed I can rollback to Official FW. then I update it with Official FW 2021.03.06 (USB is only stored U2W_Update.img). after that, it show "It is the latest version" and VER:2021.03.06.1343
I noticed the same, i rolledback to November 2020 official firmware, and after that upgrade to February 2021 Custom firmware and shows 2021.03.07.0001
 
  • Like
Reactions: chari
Only after update to 2021.03.06 I could install the firmware 2021.04.26. Can anyone confirm this? I think I was on 2021.01.28 before.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.