Hi, I am that friend that D3ggy mentioned above. I bought the CarPlay2Air after having an email conversation with a Michael. I explained that I owned a Jaguar XF that had the inbuilt CarPlay installed and I was interested in the device. He offered me the opportunity to purchase it on the basis that if it did not work then it could be returned for a full refund as they had not yet tested it on a Jaguar.
I received the item and unfortunately all I get is the red led light and nothing else, nothing shows up on the bluetooth at all.
I have not been impressed with the lack of responses via email and like you all was hoping for the promised update last week. I am contemplating contacting my credit card company however I will give it until the end of the week and go from there.
Well seems I'm not the only one stuck with the red LED and no Bluetooth.
But I got one idea that will take some effort to check. But for me it sounds like a reasonable scenario based on all that I've seen.
The behavior of the device starting/being recognized by the head unit/being dropped - and repeating, looks a lot like the port not having enough power to drive the dongle, so it will try to initialize and then drop (for example when powering the communications chip). When it drops, power comes back and recycle. Sounds very reasonable, specially since the Bluetooth and WiFi components probably share the same chip (a common setup), so powering for BT will power everything and drain more power.
Standard USB delivers by default 100mA and can go as high as 500mA if "requested". Some computers (typically desktops) will always deliver 500mA (sometimes even a little more). Either there is a problem with the protocol to request more power or the Jeep cannot provide enough juice. I've seem this on notebooks that fail to deliver even the requested 500mA. Phone are very tolerant to low power, as they use it to charge and they work even with the worst power supplies. If the makers of CarPlay2Air (and Carlinkit Unlocker that I belive is the same hardware) have "cloned" the iPhone side of the protocol when connecting to a non computer device, then it may be skipping sending the request for more power and therefore the head unit, if properly designed, is not providing enough power. Odd but reasonable.
A possible solution is to pigback 5V on the cable with more than 500mA. I have a few 5V@2A power supplies out of 12V, so I will give it a try and make a cable with a male USB-A/female USB-A that will inject 5V from an external source. Unless there is a major protocol error (that the UConnect is signalling not enough power and dropping the connection), this may work - if it's indeed a power problem.
I will post the results. Let's get fingers crossed.