I guess that’s my next step until Indian releases another update. Which one is the go to, Nov 21 or 22?
I guess that’s my next step until Indian releases another update. Which one is the go to, Nov 21 or 22?The older version has worked for me.
I’m in the same boat. How do you roll back the update?I guess that’s my next step until Indian releases another update. Which one is the go to, Nov 21 or 22?
Go to Indians website, click “resources”, ride command, get the update, then on bottom right is the Nov 2021 link. Download to USB and follow directions. I just downloaded it to the USB drive. I’ll upload to the bike tomorrow and report backI’m in the same boat. How do you roll back the update?
I am not paired via Bluetooth on the phone and I have tried multiple apple branded cables. CarPlay does not drop only audio. I’m glad yours is working but there’s plenty of others who’s aren’t and it’s not a USB issue. Also I’m always running the waze app when in CarPlay which might have something to do with itAnytime you update the ride command software, you need to unpair your phone from Ride Command. Also the phone should not be Bluetooth connected to ride command. Thats what CarPlay is for.
As I have posted earlier, Carplay is a USB connection issue, and not a software one. I have used all the last 3 RideCommand software versions with ZERO CarPlay issues, once I fixed the USB issue
I am not paired via Bluetooth on the phone and I have tried multiple apple branded cables. CarPlay does not drop only audio. I’m glad yours is working but there’s plenty of others who’s aren’t and it’s not a USB issue. Also I’m always running the waze app when in CarPlay which might have something to do with it
I’d be a believer except when I switch the audio output to headset the audio plays fine through the headset. Headset is paired to bike not phone therefore audio/data is being transmitted via usb to bike then Bluetooth to helmet.It is a USB issue, and it's not the phone cable. The female USB connector on the bike, is the weak link. You have the same issues if you connected a USB drive.
USB is not a robust connection for high vibration environment like a motorcycle. I had the same CarPlay issues everyone else had. But I remembered on my other bike, I had USB drive that cut in and out, and when I vibration isolated it, the issues were fixed.
You need to line the "cubby" area with foam to isolate vibrations. I did so and 1000 miles later with 3 (Ride Command) software versions. ZERO and I mean 1000% Zero issues. I took the foam out to verify it was the fix. With the foam out problems came back.
Then what's you issue thenI’d be a believer except when I switch the audio output to headset the audio plays fine through the headset. Headset is paired to bike not phone therefore audio/data is being transmitted via usb to bike then Bluetooth to helmet.
I have to disagree. I have always used the usb, never bluetooth. Didn’t need to unpair because there are no phone paired (I did make sure there was no phone paired). Never had an issue until the new RC update. When I reverted back to old RC firmware it has worked flawlessly. I even reloaded the new and had the same issue in OP. When I reloaded the old firmware it works fine. Same usb cable throughout. This is a software issue.Anytime you update the ride command software, you need to unpair your phone from Ride Command. Also the phone should not be Bluetooth connected to ride command. Thats what CarPlay is for.
As I have posted earlier, Carplay is a USB connection issue, and not a software one. I have used all the last 3 RideCommand software versions with ZERO CarPlay issues, once I fixed the USB issue
I have to disagree. I have always used the usb, never bluetooth. Didn’t need to unpair because there are no phone paired (I did make sure there was no phone paired). Never had an issue until the new RC update. When I reverted back to old RC firmware it has worked flawlessly. I even reloaded the new and had the same issue in OP. When I reloaded the old firmware it works fine. Same usb cable throughout. This is a software issue.
My issue is I have no audio through the bikes speakers as originally stated. Listen bud, I’m glad yours works and you aren’t experiencing this specific issue. But you are clearly stubborn and here to argue your point of view. This however is not the solution for my specific issue so let’s just drop the back and forth. No disrespect, thank you and take careThen what's you issue then
It’s not working for me, either. I’ll try to roll back tomorrow.My issue is I have no audio through the bikes speakers as originally stated. Listen bud, I’m glad yours works and you aren’t experiencing this specific issue. But you are clearly stubborn and here to argue your point of view. This however is not the solution for my specific issue so let’s just drop the back and forth. No disrespect, thank you and take care
I did that and it didn’t help.Ok guys, this is what you need do when you update your head unit software.
When CarPlay connects to the head unit for the first time, it establishes the communication protocol with that version of software and firmware, very similar to how a Bluetooth and Wi-Fi connection establish communication protocol.
So, when you update to the latest Ride Command software, you need to delete the bike from your phone. This can be found under Settings/General/Carplay/Indian Challenger. Then select forget this car.
Then when you re-connect your phone a new CarPlay connection and protocol will be established, and things should work fine.
I have done this on 4 different Challengers (friends) who were convinced I was wrong, and now their CarPlay works just fine. And they are running the latest April Software.
BTW you should also hard re-boot your phone every week for best performance.
My bike is a 23’ and scame with the latest software already installed. Therefore the initial pairing/linking was with this software. I have tried every combination of pairing/unpairing etc as well as securing the usb connection with electrical tape followed by a felt tape covering, as well as 2 different new Apple cables. Very possible what you fixed is a separate issue/glitch that causes the same symptoms. As a 17 year BMW master technician I’m very familiar with electronics/infotainment and their protocols. I have loaded the Nov 21 software into the RC and will update this afternoon/evening on my resultsOk guys, this is what you need do when you update your head unit software.
When CarPlay connects to the head unit for the first time, it establishes the communication protocol with that version of software and firmware, very similar to how a Bluetooth and Wi-Fi connection establish communication protocol.
So, when you update to the latest Ride Command software, you need to delete the bike from your phone. This can be found under Settings/General/Carplay/Indian Challenger. Then select forget this car.
Then when you re-connect your phone a new CarPlay connection and protocol will be established, and things should work fine.
I have done this on 4 different Challengers (friends) who were convinced I was wrong, and now their CarPlay works just fine. And they are running the latest April Software.
BTW you should also hard re-boot your phone every week for best performance.
Yea me too , I’ve tried every fix there has been to only get CarPlay to work for 5-10 min then nothing music wise. A little aggravating to say the least, but I’ll continue to try things till it does work. I know Harley guys have a workaround that seems to work, using a jumper, I’d like to see that for our bikes.I did that and it didn’t help.
I updated to the 2021 software, but haven't had the chance to try it yet.Yea me too , I’ve tried every fix there has been to only get CarPlay to work for 5-10 min then nothing music wise. A little aggravating to say the least, but I’ll continue to try things till it does work. I know Harley guys have a workaround that seems to work, using a jumper, I’d like to see that for our bikes.