Indian Motorcycle Forum banner
Cancel
Create thread New Forums

Android Auto working

Tags
android auto challenger ride command
2 reading
Jump to Latest
21 - 40 of 169 Posts
#21 ·
i just bought the --- OTTOCAST MX Wireless CarPlay & Android Auto Adapter with AirPlay,2024's Newest,3-in-1 Car Play Dongle Wried to Wireless,Plug & Play,OTA-Upgrade,Quick Change Mode

hope it works the same, i have the icarlink or whatever its called and it was terrible constantly overheated and was a mess keeping connected

those who dont have a sena (i have one i jist dont always wear my helmet) what do you all do to keep the headaet connection going? and not be a battle getting on the bike and going that was always my other main issue took forever for everything to connect sync up.

ill have my ottocast Saturday any insight is appreciated

thanks
 
#22 ·
Well with this 2024 Version of the Ottocast MX I cant get it to connect to CarPlay on the Bike however I know something is working I can BT to the device from my phone, and it connects the wifi right up, And then If i press and hold the button 3 seconds it switched to android auto mode on my phone but no display at all across to the RC screen even off a boot up with no phone connected or any buttons pressed. So I think I may have a paperweight , Got it through amazon gonna see if i can exchange it with the model mentioned above in first thread. Gonna play with it a bit more but if its gonna be this wonky to use every time then this isn't the model for me. But Ill report back whatever I find out - BTW this is on a 2021 Challenger, with a S24 Ultra.
 
#24 · (Edited)
Ok, so as I understand it, IF you have RideCommand+ in the newest update (November 2023) you can use Carplay and have access to jumping through the Ottocast device to get Android Auto. RideCommand+ as I understand it is the "subscription" bullshit.... So, no RideCommand+(subscription) no access to Carplay and thus Android Auto.

Is there an older update that doesn't require the RideCommand+ subscription?

edit: I have a 2021 Challenger Limited...S22 phone.

I'll hang up and listen to the answer over the air, great show by the way....
 
#26 ·
SS7 said:
Also, the Ottocast U2X Pro is discontinued, seemingly. Good because it sucked on '23/'24 models.
Click to expand...
My unproven theory is the issue is the connection at the cable coming from the bike. I plan to try to cut the end off of it and splice in a cable with the usb c connection to plug straight into the ottocast and eliminate that extra, seemingly loose, usb connection. Fingers crossed
 
Discussion starter · #27 ·
The USB disconnects from road vibrations are a real thing. I'm trying some Southern ingenuity to secure the connection. I have a 500 mile round trip this weekend and will test to see how well it holds.

Zip tying the USB cable running to the OttoCast to the weatherproofing cap to prevent side to side wiggle.

Image


Zip tying the jacket of the USB cable of the Ottocast to the jacket of the bike's USB port to prevent in and out movement.

Image
 
#28 ·
MattTheMingus said:
The USB disconnects from road vibrations are a real thing. I'm trying some Southern ingenuity to secure the connection. I have a 500 mile round trip this weekend and will test to see how well it holds.

Zip tying the USB cable running to the OttoCast to the weatherproofing cap to prevent side to side wiggle.

View attachment 821964

Zip tying the jacket of the USB cable of the Ottocast to the jacket of the bike's USB port to prevent in and out movement.

View attachment 821965
Click to expand...
Let us know how it works out 🤞
 
#31 ·
MattTheMingus said:
I was disappointed to learn that RideCommand was Apple Carplay only. But not being willing to accept no for an answer, I was going to make it work one way or another. Here is everything I've learned and how I got Android Auto running on my base model 2021 Challenger. All the gotchas (along with my color commentary).

To start, what I have:
  • 2021 Challenger base model. (yay base model brokie)
  • RIDE COMMAND+ Navigation with Apple CarPlay Upgrade module (You can find it on the Indian site)
    • I picked up my Challenger used with the module already installed by the previous owner. (the sale manager said he was surprised to see the nav working on my unit because I think they agreed to move the module from the trade in to the new unit. Whoopsie in my favor. Too late for them, no takesies-backsies)
    • I do not have the RideCommand+ subscription service, so it is offline maps only. (What a way to bleed your customers further)
    • This module is included from the factory in Dark Horse and Limited trims, so if you have one of these you're good to go.
  • RideCommand software version MHS7AB.M32343A
    • My understanding is that this is the latest version available, released November 2023.
    • I'm also given to understand that this version disables Apple CarPlay unless you have the previously mentioned RIDE COMMAND+ Navigation with Apple CarPlay Upgrade module hardware. It may be possible to rollback the software version to restore CarPlay functionality without the Nav module but I cannot confirm.
    • If I get really bored one day I may unplug the module and rollback the software to see if I can get it working but no plans to do that any time soon. If anyone else wants to attempt and confirm, please feel free. I'll give credit to whoever comes up with an answer.
    • I don't know if Android Auto was ever natively supported by Ride Command. I may have read that it was previously supported but removed after licensing agreement changes by Google but I cannot confirm that. Whomp whomp.
  • A Sena 50S mesh communicator
    • Apple CarPlay built into Ride Command is looking for any headset so any Sena/Cardo or any other Bluetooth communicator with microphone capabilities should work.
    • You don't have to be actively using the communicator. You can turn it on, pair it to the bike, and throw in in the saddlebags for all it cares. Just has to be on, paired and running.
    • No headset? RideCommand will just sit there glaring at you with a red notification until you make it happy. Is this stupid? Yes. Is that just how it is? Yes.
    • "But I don't wanna have to have a headset running, this is dumb." I agree. Why, Indian, why? middle fingers
What I bought:
  • OTTOCAST Play2Video Pro Wireless CarPlay Android Auto Adapter Built-in YouTube/Netflix/Spotify/IPTV from Amazon but you can also buy it straight from Ottocast on their website.
    • I've seen several people in this forum posting that the Ottocast U2-X Pro was the only unit that works. This is obviously not the case.
    • I think the U2-X Pro model is out of production and isn't available any longer on the Ottocast website.
    • I think what really matters is that the wireless adapter you purchase supports both CarPlay and Android Auto. This is probably what is hanging up a lot of people when they only buy a aftermarket smart dongle to piggy back. Just my conjecture. I'm open to being proven wrong.
    • The Play2Video Pro does more than just those two things. It has it's own media center capabilities, including apps like Netflix and YouTube and the ability to play media attached via USB memory sticks. It all works with the Challenger. More on that later.
How I installed it:
  • Plug the Ottocast into the USB port in the fairing cubby hole. It came with a USB-C to -A cable so I used that.
  • Turn the bike on and it'll go through the fancy pants, smoke clouds, "look at me, I'm an Indian" boot up screen.
  • You'll have an angry red notification saying if you want to use CarPlay, you need to have a headset. Why, Indian, why? middle fingers
  • Paired my Sena to the bike.
    • Previously I had had the Sena paired to my bike and my Android phone at the same time but that seemed to confuse the Ottocast so I unpaired the phone from the Sena. Also, don't pair the Sena to the Ottocast. You want the headset only receiving input from the bike itself. You'll still be able to toggle audio going to the speakers if that's how you roll. My Sena's speakers in my helmet work better for my use case. Also, base model speakers suck (yay being a base model brokie)
  • At this point, RideCommand will launch the built-in CarPlay. Not the one inside the Ottocast, the onboard one. This what triggers the Ottocast to take over the screen.
  • The Ottocast screen will come up and you'll be able to start launching apps.
    • I went ahead and connected the Ottocast to my home Wifi and installed the pending firmware updates OTA.
    • You'll want to hop back out of Ottocast and go back to the RideCommand interface and go to SETTINGS icon or the INDIAN MOTORCYCLE logo > VEHICLE > AUTOMATIC DISPLAY POWER DOWN and disable that before updating firmware if you haven't already done that.
      • It look longer than expected. Have the bike on a battery tender during this process. Or don't. I'm not your mother.
  • After updates and reboots, you can now pair your Android phone to the Ottocast over Bluetooth. I'm running a Samsung Galaxy Fold 5 running Android 14. (I'm not a poor when it comes to phones, only bikes)
  • Click the Android Auto icon to launch it (the tiny white arrows on a blue background)
    • Previously I had had the Android paired to my bike and my Sena, but again, that seemed to confuse the Ottocast so I unpaired the phone from the bike. Also, don't pair the bike to the Ottocast over Bluetooth (even though it will show up in available devices and let you do initially. This confuses it and you'll get Bluetooth loops where the bike will connect/disconnect over and over again, the speakers ever so slightly popping with each loop.
  • You now have functioning Android Auto running on your Indian. (even though it should be a native feature. get it? Native? Indian?)
    • The bike doesn't seem to give any run time information to Android Auto so I never see my current speed on the maps screen like I do in other vehicles running Android Auto.
  • The final and optional step is to back out of Android Auto and go into the Settings app in the Ottocast interface and tell it to automatically launch the "Multiplay" app as Startup App. This is the app that emulates and casts both Apple CarPlay and Android Auto to the headunit that the Ottocast is connected to.
    • Settings > Personalization > Choose Apps to Launch on Startup > Specify App Mode > Multiplay
    • Feel free to ignore this step or choose another option.
    • By setting this option to Multiplay my Challenger 7" screen will auto boot to Android Auto without any interaction as long as my phone and Sena are both on. The sequence of operations is as follows:
      • Power bike on
      • Smoke screen, "I'm an Indian, dammit"
      • Warning screen to not to dumb things which auto-dismisses itself. (I'll do dumb things if I darn well please, Indian)
      • By this time the Ottocast has booted up as it received power from the USB connection.
      • RideCommand recognizes my Sena and launches CarPlay, thus letting Ottocast take over.
      • Ottocast takes a second to recognize my phone's Bluetooth connection and then launches its interface.
      • Ottocast then automatically launches Android Auto and I'm ready to roll (queue Motley Crue intro)
Other things of consideration:
  • wireless Android Auto will require use of the Wifi connection on your phone.
  • Running apps inside the Ottocast interface, like Netflix or Youtube (but not AA or CarPlay) require the Ottocast to be connected to Wifi or a hotspot.
  • You cannot simultaneously be running Android Auto and using your phone as a hotspot to feed the Ottocast a data connection. One or the other but not both at the same time.
  • A lot of people have reported previously spotty connectivity of the Ottocast to the head unit. The main culprit seems to be road vibrations causing micro disconnects of the USB cable. I've only been riding around town thus far and haven't experienced any disconnects and haven't had to resort to adding cushioning to the interior of the cubby or soldering the Ottocase to the bike like some have done. The USB C physical connections seems to be pretty stout. This may change with heat cycles, weathering, age or other factors. TBD.
  • If you wish to route Ottocast audio to the speakers instead of your headset, you'll have to back out of the Ottocast interface and toggle the bike/headset output in the Ride Command interface and then relaunch Ottocast by opening 'CarPlay' again.
  • I'm not sure yet about auto-brightness adjustment or automatic night-time/day-time switch while running Ottocast/Android Auto yet. It might work. TBD.
Please ask questions and I will try my best to answer as I can. I will answer questions below as well as update this original post with Qs and As.

I'll use the first reply of this thread to post pictures and keep these instructions clean. Also I'm tired of typing for now. :rolleyes:
Click to expand...
Thanks for the write up.
 
#34 ·
Bubba102105 said:
Well I'll be god damned! Rode it a little bit last night and then 35 miles into work this morning, zero disconnections!!! Thanks so much! I had given up on it the last year probably.
Click to expand...

Yep, #1 cause of car play and android issues is nothing but the USB line connection. Doesn't matter what cable you have or buy. The vibrations of a V Twin will cause disruptions. This was an issue and still is on the older ride command units using USB flash drives with music.

Since this is a digital connection, it has to be perfect 100% all of the time. One thing that ended my car play issues was to line the cubby where the USB cable sits with 1/4-inch foam. I have ruin CarPlay on all 3 software versions with ZERO issues using a wireless CarPlay option and lining the cubby with foam to cut down on vibrations.
 
#37 ·
MattTheMingus said:
I was disappointed to learn that RideCommand was Apple Carplay only. But not being willing to accept no for an answer, I was going to make it work one way or another. Here is everything I've learned and how I got Android Auto running on my base model 2021 Challenger. All the gotchas (along with my color commentary).

To start, what I have:
  • 2021 Challenger base model. (yay base model brokie)
  • RIDE COMMAND+ Navigation with Apple CarPlay Upgrade module (You can find it on the Indian site)
    • I picked up my Challenger used with the module already installed by the previous owner. (the sale manager said he was surprised to see the nav working on my unit because I think they agreed to move the module from the trade in to the new unit. Whoopsie in my favor. Too late for them, no takesies-backsies)
    • I do not have the RideCommand+ subscription service, so it is offline maps only. (What a way to bleed your customers further)
    • This module is included from the factory in Dark Horse and Limited trims, so if you have one of these you're good to go.
  • RideCommand software version MHS7AB.M32343A
    • My understanding is that this is the latest version available, released November 2023.
    • I'm also given to understand that this version disables Apple CarPlay unless you have the previously mentioned RIDE COMMAND+ Navigation with Apple CarPlay Upgrade module hardware. It may be possible to rollback the software version to restore CarPlay functionality without the Nav module but I cannot confirm.
    • If I get really bored one day I may unplug the module and rollback the software to see if I can get it working but no plans to do that any time soon. If anyone else wants to attempt and confirm, please feel free. I'll give credit to whoever comes up with an answer.
    • I don't know if Android Auto was ever natively supported by Ride Command. I may have read that it was previously supported but removed after licensing agreement changes by Google but I cannot confirm that. Whomp whomp.
  • A Sena 50S mesh communicator
    • Apple CarPlay built into Ride Command is looking for any headset so any Sena/Cardo or any other Bluetooth communicator with microphone capabilities should work.
    • You don't have to be actively using the communicator. You can turn it on, pair it to the bike, and throw in in the saddlebags for all it cares. Just has to be on, paired and running.
    • No headset? RideCommand will just sit there glaring at you with a red notification until you make it happy. Is this stupid? Yes. Is that just how it is? Yes.
    • "But I don't wanna have to have a headset running, this is dumb." I agree. Why, Indian, why? middle fingers
What I bought:
  • OTTOCAST Play2Video Pro Wireless CarPlay Android Auto Adapter Built-in YouTube/Netflix/Spotify/IPTV from Amazon but you can also buy it straight from Ottocast on their website.
    • I've seen several people in this forum posting that the Ottocast U2-X Pro was the only unit that works. This is obviously not the case.
    • I think the U2-X Pro model is out of production and isn't available any longer on the Ottocast website.
    • I think what really matters is that the wireless adapter you purchase supports both CarPlay and Android Auto. This is probably what is hanging up a lot of people when they only buy a aftermarket smart dongle to piggy back. Just my conjecture. I'm open to being proven wrong.
    • The Play2Video Pro does more than just those two things. It has it's own media center capabilities, including apps like Netflix and YouTube and the ability to play media attached via USB memory sticks. It all works with the Challenger. More on that later.
How I installed it:
  • Plug the Ottocast into the USB port in the fairing cubby hole. It came with a USB-C to -A cable so I used that.
  • Turn the bike on and it'll go through the fancy pants, smoke clouds, "look at me, I'm an Indian" boot up screen.
  • You'll have an angry red notification saying if you want to use CarPlay, you need to have a headset. Why, Indian, why? middle fingers
  • Paired my Sena to the bike.
    • Previously I had had the Sena paired to my bike and my Android phone at the same time but that seemed to confuse the Ottocast so I unpaired the phone from the Sena. Also, don't pair the Sena to the Ottocast. You want the headset only receiving input from the bike itself. You'll still be able to toggle audio going to the speakers if that's how you roll. My Sena's speakers in my helmet work better for my use case. Also, base model speakers suck (yay being a base model brokie)
  • At this point, RideCommand will launch the built-in CarPlay. Not the one inside the Ottocast, the onboard one. This what triggers the Ottocast to take over the screen.
  • The Ottocast screen will come up and you'll be able to start launching apps.
    • I went ahead and connected the Ottocast to my home Wifi and installed the pending firmware updates OTA.
    • You'll want to hop back out of Ottocast and go back to the RideCommand interface and go to SETTINGS icon or the INDIAN MOTORCYCLE logo > VEHICLE > AUTOMATIC DISPLAY POWER DOWN and disable that before updating firmware if you haven't already done that.
      • It look longer than expected. Have the bike on a battery tender during this process. Or don't. I'm not your mother.
  • After updates and reboots, you can now pair your Android phone to the Ottocast over Bluetooth. I'm running a Samsung Galaxy Fold 5 running Android 14. (I'm not a poor when it comes to phones, only bikes)
  • Click the Android Auto icon to launch it (the tiny white arrows on a blue background)
    • Previously I had had the Android paired to my bike and my Sena, but again, that seemed to confuse the Ottocast so I unpaired the phone from the bike. Also, don't pair the bike to the Ottocast over Bluetooth (even though it will show up in available devices and let you do initially. This confuses it and you'll get Bluetooth loops where the bike will connect/disconnect over and over again, the speakers ever so slightly popping with each loop.
  • You now have functioning Android Auto running on your Indian. (even though it should be a native feature. get it? Native? Indian?)
    • The bike doesn't seem to give any run time information to Android Auto so I never see my current speed on the maps screen like I do in other vehicles running Android Auto.
  • The final and optional step is to back out of Android Auto and go into the Settings app in the Ottocast interface and tell it to automatically launch the "Multiplay" app as Startup App. This is the app that emulates and casts both Apple CarPlay and Android Auto to the headunit that the Ottocast is connected to.
    • Settings > Personalization > Choose Apps to Launch on Startup > Specify App Mode > Multiplay
    • Feel free to ignore this step or choose another option.
    • By setting this option to Multiplay my Challenger 7" screen will auto boot to Android Auto without any interaction as long as my phone and Sena are both on. The sequence of operations is as follows:
      • Power bike on
      • Smoke screen, "I'm an Indian, dammit"
      • Warning screen to not to dumb things which auto-dismisses itself. (I'll do dumb things if I darn well please, Indian)
      • By this time the Ottocast has booted up as it received power from the USB connection.
      • RideCommand recognizes my Sena and launches CarPlay, thus letting Ottocast take over.
      • Ottocast takes a second to recognize my phone's Bluetooth connection and then launches its interface.
      • Ottocast then automatically launches Android Auto and I'm ready to roll (queue Motley Crue intro)
Other things of consideration:
  • wireless Android Auto will require use of the Wifi connection on your phone.
  • Running apps inside the Ottocast interface, like Netflix or Youtube (but not AA or CarPlay) require the Ottocast to be connected to Wifi or a hotspot.
  • You cannot simultaneously be running Android Auto and using your phone as a hotspot to feed the Ottocast a data connection. One or the other but not both at the same time.
  • A lot of people have reported previously spotty connectivity of the Ottocast to the head unit. The main culprit seems to be road vibrations causing micro disconnects of the USB cable. I've only been riding around town thus far and haven't experienced any disconnects and haven't had to resort to adding cushioning to the interior of the cubby or soldering the Ottocase to the bike like some have done. The USB C physical connections seems to be pretty stout. This may change with heat cycles, weathering, age or other factors. TBD.
  • If you wish to route Ottocast audio to the speakers instead of your headset, you'll have to back out of the Ottocast interface and toggle the bike/headset output in the Ride Command interface and then relaunch Ottocast by opening 'CarPlay' again.
  • I'm not sure yet about auto-brightness adjustment or automatic night-time/day-time switch while running Ottocast/Android Auto yet. It might work. TBD.
Please ask questions and I will try my best to answer as I can. I will answer questions below as well as update this original post with Qs and As.

I'll use the first reply of this thread to post pictures and keep these instructions clean. Also I'm tired of typing for now. :rolleyes:
Click to expand...
I got my Ottocast working perfectly, but does anyone has an issue to get google Assistant to get work with the Ottocast?
 
#38 ·
Okay after following the instructions I can confidently say that I have been successful and putting Android auto on the screen of my roadmaster. Thank you for all of you who put information in this thread for me to follow I am very appreciative.
 
  • Like
Reactions: Pauly Rides and hunter56
Save
Like Like
#39 ·
MattTheMingus said:
I was disappointed to learn that RideCommand was Apple Carplay only. But not being willing to accept no for an answer, I was going to make it work one way or another. Here is everything I've learned and how I got Android Auto running on my base model 2021 Challenger. All the gotchas (along with my color commentary).

To start, what I have:
  • 2021 Challenger base model. (yay base model brokie)
  • RIDE COMMAND+ Navigation with Apple CarPlay Upgrade module (You can find it on the Indian site)
    • I picked up my Challenger used with the module already installed by the previous owner. (the sale manager said he was surprised to see the nav working on my unit because I think they agreed to move the module from the trade in to the new unit. Whoopsie in my favor. Too late for them, no takesies-backsies)
    • I do not have the RideCommand+ subscription service, so it is offline maps only. (What a way to bleed your customers further)
    • This module is included from the factory in Dark Horse and Limited trims, so if you have one of these you're good to go.
  • RideCommand software version MHS7AB.M32343A
    • My understanding is that this is the latest version available, released November 2023.
    • I'm also given to understand that this version disables Apple CarPlay unless you have the previously mentioned RIDE COMMAND+ Navigation with Apple CarPlay Upgrade module hardware. It may be possible to rollback the software version to restore CarPlay functionality without the Nav module but I cannot confirm.
    • If I get really bored one day I may unplug the module and rollback the software to see if I can get it working but no plans to do that any time soon. If anyone else wants to attempt and confirm, please feel free. I'll give credit to whoever comes up with an answer.
    • I don't know if Android Auto was ever natively supported by Ride Command. I may have read that it was previously supported but removed after licensing agreement changes by Google but I cannot confirm that. Whomp whomp.
  • A Sena 50S mesh communicator
    • Apple CarPlay built into Ride Command is looking for any headset so any Sena/Cardo or any other Bluetooth communicator with microphone capabilities should work.
    • You don't have to be actively using the communicator. You can turn it on, pair it to the bike, and throw in in the saddlebags for all it cares. Just has to be on, paired and running.
    • No headset? RideCommand will just sit there glaring at you with a red notification until you make it happy. Is this stupid? Yes. Is that just how it is? Yes.
    • "But I don't wanna have to have a headset running, this is dumb." I agree. Why, Indian, why? middle fingers
What I bought:
  • OTTOCAST Play2Video Pro Wireless CarPlay Android Auto Adapter Built-in YouTube/Netflix/Spotify/IPTV from Amazon but you can also buy it straight from Ottocast on their website.
    • I've seen several people in this forum posting that the Ottocast U2-X Pro was the only unit that works. This is obviously not the case.
    • I think the U2-X Pro model is out of production and isn't available any longer on the Ottocast website.
    • I think what really matters is that the wireless adapter you purchase supports both CarPlay and Android Auto. This is probably what is hanging up a lot of people when they only buy a aftermarket smart dongle to piggy back. Just my conjecture. I'm open to being proven wrong.
    • The Play2Video Pro does more than just those two things. It has it's own media center capabilities, including apps like Netflix and YouTube and the ability to play media attached via USB memory sticks. It all works with the Challenger. More on that later.
How I installed it:
  • Plug the Ottocast into the USB port in the fairing cubby hole. It came with a USB-C to -A cable so I used that.
  • Turn the bike on and it'll go through the fancy pants, smoke clouds, "look at me, I'm an Indian" boot up screen.
  • You'll have an angry red notification saying if you want to use CarPlay, you need to have a headset. Why, Indian, why? middle fingers
  • Paired my Sena to the bike.
    • Previously I had had the Sena paired to my bike and my Android phone at the same time but that seemed to confuse the Ottocast so I unpaired the phone from the Sena. Also, don't pair the Sena to the Ottocast. You want the headset only receiving input from the bike itself. You'll still be able to toggle audio going to the speakers if that's how you roll. My Sena's speakers in my helmet work better for my use case. Also, base model speakers suck (yay being a base model brokie)
  • At this point, RideCommand will launch the built-in CarPlay. Not the one inside the Ottocast, the onboard one. This what triggers the Ottocast to take over the screen.
  • The Ottocast screen will come up and you'll be able to start launching apps.
    • I went ahead and connected the Ottocast to my home Wifi and installed the pending firmware updates OTA.
    • You'll want to hop back out of Ottocast and go back to the RideCommand interface and go to SETTINGS icon or the INDIAN MOTORCYCLE logo > VEHICLE > AUTOMATIC DISPLAY POWER DOWN and disable that before updating firmware if you haven't already done that.
      • It look longer than expected. Have the bike on a battery tender during this process. Or don't. I'm not your mother.
  • After updates and reboots, you can now pair your Android phone to the Ottocast over Bluetooth. I'm running a Samsung Galaxy Fold 5 running Android 14. (I'm not a poor when it comes to phones, only bikes)
  • Click the Android Auto icon to launch it (the tiny white arrows on a blue background)
    • Previously I had had the Android paired to my bike and my Sena, but again, that seemed to confuse the Ottocast so I unpaired the phone from the bike. Also, don't pair the bike to the Ottocast over Bluetooth (even though it will show up in available devices and let you do initially. This confuses it and you'll get Bluetooth loops where the bike will connect/disconnect over and over again, the speakers ever so slightly popping with each loop.
  • You now have functioning Android Auto running on your Indian. (even though it should be a native feature. get it? Native? Indian?)
    • The bike doesn't seem to give any run time information to Android Auto so I never see my current speed on the maps screen like I do in other vehicles running Android Auto.
  • The final and optional step is to back out of Android Auto and go into the Settings app in the Ottocast interface and tell it to automatically launch the "Multiplay" app as Startup App. This is the app that emulates and casts both Apple CarPlay and Android Auto to the headunit that the Ottocast is connected to.
    • Settings > Personalization > Choose Apps to Launch on Startup > Specify App Mode > Multiplay
    • Feel free to ignore this step or choose another option.
    • By setting this option to Multiplay my Challenger 7" screen will auto boot to Android Auto without any interaction as long as my phone and Sena are both on. The sequence of operations is as follows:
      • Power bike on
      • Smoke screen, "I'm an Indian, dammit"
      • Warning screen to not to dumb things which auto-dismisses itself. (I'll do dumb things if I darn well please, Indian)
      • By this time the Ottocast has booted up as it received power from the USB connection.
      • RideCommand recognizes my Sena and launches CarPlay, thus letting Ottocast take over.
      • Ottocast takes a second to recognize my phone's Bluetooth connection and then launches its interface.
      • Ottocast then automatically launches Android Auto and I'm ready to roll (queue Motley Crue intro)
Other things of consideration:
  • wireless Android Auto will require use of the Wifi connection on your phone.
  • Running apps inside the Ottocast interface, like Netflix or Youtube (but not AA or CarPlay) require the Ottocast to be connected to Wifi or a hotspot.
  • You cannot simultaneously be running Android Auto and using your phone as a hotspot to feed the Ottocast a data connection. One or the other but not both at the same time.
  • A lot of people have reported previously spotty connectivity of the Ottocast to the head unit. The main culprit seems to be road vibrations causing micro disconnects of the USB cable. I've only been riding around town thus far and haven't experienced any disconnects and haven't had to resort to adding cushioning to the interior of the cubby or soldering the Ottocase to the bike like some have done. The USB C physical connections seems to be pretty stout. This may change with heat cycles, weathering, age or other factors. TBD.
  • If you wish to route Ottocast audio to the speakers instead of your headset, you'll have to back out of the Ottocast interface and toggle the bike/headset output in the Ride Command interface and then relaunch Ottocast by opening 'CarPlay' again.
  • I'm not sure yet about auto-brightness adjustment or automatic night-time/day-time switch while running Ottocast/Android Auto yet. It might work. TBD.
Please ask questions and I will try my best to answer as I can. I will answer questions below as well as update this original post with Qs and As.

I'll use the first reply of this thread to post pictures and keep these instructions clean. Also I'm tired of typing for now. :rolleyes:
Click to expand...
Do you know if this will work with the 2019?
 
21 - 40 of 169 Posts
You have insufficient privileges to reply here.
About this Discussion
168 Replies
41 Participants
Last post:
SBSSammy
Indian Motorcycle Forum
posts
1.8M
members
67K
Since
2010
A forum community dedicated to Indian Motorcycle owners and enthusiasts. Come join the discussion about performance, modifications, troubleshooting, maintenance, and builds for all Indian models.
Full Forum Listing
Explore Our Forums
Indian Motorcycle General Discussion Indian Scout New Member Introductions Indian Chieftain Indian Roadmaster