calimoto Is Now Compatible With Android Auto 🎉
Hooray, the wait is over: calimoto is now compatible with Android Auto!
Android Auto is a Google system that connects your Android smartphone to your car’s infotainment system. This way, you can easily display calimoto on any Android Auto compatible screen.
Your benefits with Android Auto
- Less distraction while riding
- A larger and clearer view on your display
- Easier and safer controls
- Less strain on your smartphone
More about Android Auto
You can find more information on how to set up and use Android Auto in the Google Support.
Information regarding the launch
Since this is our first version with Android Auto, you may still encounter some bugs or display issues.
If you notice anything or have specific feedback, please reach out to our Support team with as much detail as possible, including screenshots or screen recordings.
Thank you for your support and patience 🙌.
Ride safe and enjoy the road. Now with Android Auto! 🏍️
Comments
Hey everyone,
We appreciate the exchange of thoughts and feedback, but we'd like to keep this space focused on direct support and user questions. Discussions that aren’t related to troubleshooting or that promote other apps are best suited for our Facebook page rather than the Help Center. Please keep in mind that such comments may be removed here.
If you need any specific support, feel free to reach out to us directly—we're happy to help!
Thanks for your understanding, and ride safe! 🚀🏍️
Hey, let's keep it cool, let us wait the result in a couple of month.... I'm for sure looking forward to it! And if they need any Beta-Testers, let me know😉
@Lina (Calimoto), will a development roadmap be shared with the community? Is there an ETA?
Right now, it feels like we’re staring into a black void of uncertainty. When I contact support with questions about Android Auto, I usually receive a standard response. This makes it seem as though Android users are being kept in limbo. I used to be confident that your tech team would implement Android Auto, but the prolonged silence is making me doubt that.
Looking at other app providers, most of them prioritize Android Auto before CarPlay. As an IT consultant and web developer, I know that Android apps generally have fewer restrictions and are easier to develop than iOS apps. That’s why it feels off to hear repeated claims that Android Auto is particularly difficult to implement.
Please provide an update for the community. What are the plans? Where does Android Auto stand on the development roadmap? What is the estimated timeline?
@Herre – Thanks for your patience and for sharing your perspective. As we’ve mentioned in the Help Center article, we want to be proactive rather than reactive in this case, meaning that we’ll share a more definite timeline once we reach a stage where we can do so with confidence. Our developers are actively working on it, but Android Auto integration isn’t just about adapting an existing app—it’s essentially creating a new application within a highly regulated ecosystem.
Unlike standard Android apps, Android Auto requires a completely different UI framework and interaction model. It operates under strict performance and safety guidelines set by Google, which means that even features that work flawlessly in the main app often need to be reengineered from the ground up to comply with these requirements. This includes adapting the routing engine, refining data transfer efficiency, and ensuring that all interactions meet Google's safety and usability standards for in-vehicle use.
We understand the demand and absolutely recognize the frustration of waiting. The goal is to ensure a smooth and reliable experience rather than rushing out a solution that doesn’t meet our expectations—or yours. We’ll provide an update when we have a solid timeline in place. Thanks again for your patience! 🚀
Yeah, sure - Android Auto integration wouldn't hurt; however, I just don't see this as a big issue as you can just mount your phone. Why would you want to be messing about with your phone and getting hounded by notifications when you're out on a ride? Which, is what Android Auto is about if we're honest, right?
When riding, the fewer distractions the better.
Set the route up, mount your phone, done!
Calimoto enhances my rides as is - I've discovered loads of awesome roads and routes really local to me that I didn't even know existed.
So for me, it's a fantastic app and I don't think adding this latest feature would really enhance that for me. All Android Auto compatibility would do, is give me the option of spending more money on more pointless tech that I don't need. And for what? The same app on a slightly larger screen.
What would be more helpful, is the ability to plan loop routes on the webapp.
Well, whether you mount your phone, or leave your phone in your pocket and use an Android Auto screen, the issue with notifications is the same. To stop that, using either method, you just set Do Not Disturb.
I find the larger screen makes it easier to map-read without taking my eyes off the road for too long, plus there is some integration with the BMW scroll wheel.
Also, for us living in warmer climates, it's not uncommon to overheat the phone during long rides.
So, keeping the expensive phone in your pocket or tank bag, away from the sun, certainly helps with stuff like battery longevity.
For reference, securing the phone with a Quadlock or PeakDesign mount nowadays costs the same as ordering a dedicated AA screen from Ali.
Specific phone cases for those mounts are also expensive and, most of the time, ugly.
Some phones experience camera damage from being attached to motorcycles due to vibrations.
There's also the argument that in a crash, it's better to have your phone in your jacket pocket than away from you on the bike when you need to call for help.
And so on... and on...
Hi Nicholas,
It's not really the same though, is it? If you have a screen that won't work with gloves, or your phone is in your pocket, the bleeping or whatever isn't really such a distraction as you can't interact with it.
As to the point about map reading on the move, well, this shouldn't really be happening. You should look at the route before you set off ideally and have an idea where you're going - again to save from distraction. If that's not possible then you have the voice prompts.
Hi Alex,
All fair points tbf. It's not changed my personal opinion though. I knew I'd get some backlash from this post as everyone nowadays can't seem to be without the latest gadget. haha.
Heh heh, the notion that I'm going to plan a route on Calimoto, where the whole idea is to have a random wriggly route, and then learn the whole thing before I set off, is ludicrous.
As I said, with Do Not Disturb set, I don't get bleeps and squeaks from the screen. So there's nothing to interact with anyway.
If you think you are somehow at an advantage using your phone screen over a Chigee embedded device, then that's great, we are all very happy for you. Ride safe and have fun. I think the rest of us will continue to use our Android Auto devices and either hope Calimoto get an Android Auto app developed, or find something else that works for us (I use Calimoto to plan the route, then export it to OSMand, which works really well).
Stupid reply routes can get intricate when they go through towns or busy junctions. Are you supposed to memorise the next 2 - 3 hours of riding.
Nicholas / Desmond,
It's not a stupid reply, it's been misinterpreted and I caveated with the voice prompts. I'm not expecting anyone, myself included, to memorise a route end to end. That's not what I said at all. However, you should have an idea (I say again 'an idea') where you're going so you're not riding blind and causing issues to other road users. I used to be a professional driver and I've seen this countless times with people being in the wrong lane etc etc and there is always a satnav or phone involved and it's clear they've not looked at their route and with that satnav taken away they would have no idea at all how to get home.
And Desmond - I once rode from Cambridgeshire to Munich without a satnav and during the ride I only looked at my map once to clarify the route in Germany. That journey was two full days so I'm sure a 3-hour ride is manageable to get an idea where you're rolling off to. I.e, I'm looking for signs to Frankfurt, then Munich.
So yes, I do feel it's advantageous to use a mounted device so it can be removed when not in use. If you don't want to mount it, put it in your pocket and listen to voice prompts.
As I initially said, for me (I say again 'for me') Calimoto has enhanced my riding experience 'as is' and that's what tech is supposed to do.
@Mark the reason I've chosen to buy an Android Auto device, is the fact that mounting a phone to the bike already did cost me two phones. And yes I've been using expensive mounts with vibration dampers.
The phone gives me more distraction than the Android Auto device. The screen interacts great with gloves.
I do love calimoto due to its curvy round trips, but already found multiple apps with the same option supporting AA. I do like calimoto and therefore still have my subscription. Also as a supporter in the hope they further develop the app and start supporting AA.
And I agree with large A to B trips you should have an idea where you are driving. But for me the fun calimoto should bring is the curvey round trips on small bumpy back roads I normally would never ride. This way I discovered great routes nearby my home I would never ride on my own decision. It also helped me discovered wonderful places when being on a holiday on the bike. And like I said at the start, not with my phone mounted anymore.
For me AA isn't another tech gadget. It's a replacement of my phone, giving better overview instead of the glittering phone screen. With less app notifications then the phone gives.
@Herre I hear your points, and I'm sorry to hear that you've lost two phones owing to mounting them. I'm just talking from my own experiences and preference. I'm not against AA integration per se - which I tried to get across in my initial post. They're just not for me and I just don't think it's the dealbreaker than some on this thread are making out. I'm using the Oxford CLIQR mount w/ universal case (i.e., the case is mounted with the phone inside) on my V-Strom and had no issues thus far with phone security; I simply mount behind the screen and go. Hopefully, this configuration will continue working for me without the issues you have faced.
Out of interest, going from your past experiences, are you not worried about your AA device dislodging? Or is the mount more permanent?
@mark the phones I've lost was on naked bikes (Vmax and a triumph bobber). So for sure not only vibrations from the bike, but also vibrations due to also catching up wind.
The AA device is a Chigee AI0 Lite. A permanent mounted device, build for motorbikes. Chosen it as it also has dashcam which also offers blind spot detection which comes in handy in heavy highway traffic. I have it mounted on my Triumph Tiger behind my screen. I ride the whole year round. The bike is my dedicated way of transportation for commuting, to the office, visiting clients, riding to training locations. Also during winter etc. That is also one off the reasons to get the phone off the bike. Phone discharged very quickly below zero, although it's water resistant it time from time started nagging having water in the charging port etc.
Mark : Reason why i don'T want to mount my phone on my handle bar... simple .. I lost one when attached with a RAM mount.. on the highway... So Pixel gone + Ram mount..
In my pocket, the only way to loose the phone is if a 6 wheels hit me, and pass over me.. but in that case, loosing my phone will be my last issue...
I change my bike for a new one, mostly because it came with Android Auto.. so i was suprise at that moment to discover that Calimoto were not complatible at all ..,, So i past my last year manually build my ryde on the web app of Harley, and push the map on my Infosystem after.... Not that different they what i was doing with Calimoto.. that was using Caliweb to build my map, and select it on the phone... I never used the auto-mal feature that came with premium, but purchase the premium just to encourage their business...
Hello everyone! Wow, we step away for one weekend, and it looks like you’ve all had quite the exchange! 😄 Thanks for keeping the discussion lively and (mostly) friendly, even with different opinions in the mix.
We see (and appreciate!) your enthusiasm for Android Auto—it’s definitely still a hot topic in the office, too. As soon as we move into the Beta phase, you’ll be the first to know. And before you ask—nope, I still don’t have a timeplan to share. 😉
Thanks for sticking with us!
Hi Calimoto team,
Thanks for the updates and for continuing to communicate with the community. I really hope Android Auto support will be available soon. It's a feature many of us are waiting for, and it would really help make Calimoto even more useful out on the road.
Looking forward to seeing it implemented – and hoping for good news in the near future.
New motorcycle season is starting in fiew weeks here (winter is leaving !!! ) ..
It's sad, one interesting option i see in Calimito that just went out, is the ability to add motorcycle in a "following" pool.. so if someone get lost be cause we turn somewhere.. he can find us.
But.. not yet on Android Auto.
So i'm testing a new app this summer (for motorcycle, Android Auto compatible), unless a Beta android auto version is availble from Calimoto. Will see, but i don't think it will see day light this year...
So wich you all, a great summer ride !
Hi @Thomas, hi @Erik!
Thanks a lot for your messages and your support – we really appreciate you being part of the calimoto community!
We totally understand the interest in Android Auto and know it's a feature many riders are hoping for. While we can’t share specific news at the moment, please know that we’re listening and taking all your feedback seriously.
Wishing you both an amazing start to the new season – and lots of great, safe, and curvy rides ahead! 🏍️🌞
I saw something weird...
I was browsing the Chigee Kickstarter page ( not gonna share links ) and noticed that they are bundling 1yr of Calimoto premium.
That felt odd. Given that we continue to receive the same message over the months, there is no news to share regarding this topic.
Either Calimoto is hiding its game, or soon enough, there will be an avalanche of Chigee buyers flooding this support thread, complaining that they can't use Calimoto with their newly acquired device ( again, sold in a bundle with Calimoto )
That's... weird.
Hi, is there a "roadmap" for AA integration? Or when should we expect first version. I was just about to pay for the app, but no AA support is huge no-go for me. Thank you
I just received my Google notification for Calimoto Premium renewal (in May 2025). I cancel it, and for reason : no Android Auto support.
I can without fee, use the stock planning app, that allow me to draw my ryde on my PC, and upload them to my AndroidAuto device. I would have prefer Calimoto, but lack of Android Auto support last summer, direct me to re-draw all of my ryde on my stock app device.
I will probably test another option running from a phone with Android Auto support this summer.. same pricing scheme as Calimoto, but support for AA !
Hey @Alex – thanks for bringing this up — we totally get how that might seem a bit confusing at first glance.
Just to clarify: calimoto does not currently support Android Auto, and that hasn’t changed. We’re exploring a potential collaboration with Chigee, but nothing has been finalized or officially launched yet.
The 1-year Premium bundle included in their Kickstarter is completely independent of Android Auto. It’s simply meant to give new users access to all the features calimoto already offers — just not via Android Auto (∫).
We really appreciate your patience and attention to detail here. And yes, if anything changes, you can count on us to communicate it clearly and directly.
Ride safe!
Hello @Martin – We get it; Android Auto is a big one for many riders. Right now, we’re working on a major technical step behind the scenes: integrating Mapbox, which is essential before we can move forward with Android Auto.
That said, we don’t have a public roadmap or timeline to share just yet. Once the groundwork is done and we’re closer to release, we’ll let everyone know — you won’t miss it.
Appreciate your interest, and we hope we’ll have the chance to welcome you onboard when the time comes!
Hi @Erik Gaudin – thanks for sharing your experience. We understand your decision, especially if Android Auto is a key part of your riding setup.
We’re currently working on the technical foundation that’s needed before Android Auto can be implemented, and we’re hoping to make real progress soon. That said, we know that doesn’t help you right now, and we respect your choice to explore other options in the meantime.
If things change down the road, we’d love to welcome you back. Until then, ride safe and enjoy the season ahead! 🏍️
So rather than excuses and fobbing off, why dont you give your customers, remember that, customers, a time frame when you are going to complete AA compatability? No long winded excuses no complex answers. Just a date your aiming for. I would never have bought if I knew its not compatable. Remember talk straight to your customers. Very disappointed, in your service.
@Nigel - I've been saying the same for the past 2 years if you look back. Don't hold your breath!
Hello @Nigel Allison,
Thank you for your message — we’re genuinely sorry to read that you're this disappointed.
We understand that the lack of Android Auto support is frustrating, especially when it’s something you expected from the start. That said, rather than offering vague promises or arbitrary dates, we prefer to be honest — and the truth is: we’re not yet in a position to share a reliable timeline. Anything else would risk setting false expectations, which we’re keen to avoid.
The technical groundwork (as you’re aware, including the Mapbox integration) is actively underway. Once we’ve reached the point where a release window is realistic, you’ll hear it from us directly — no fluff, no fobbing off.
In the meantime, we’re still here to support you as best we can.
Well, apparently at least a year further after start of this discussion. Still words about the "ground work" and still no compatibility. This season's premium is already been paid for, but this summer i will get my carpuride as well. If after this riding season your developers still did not succeed, i will cancel my subscription as well. Would these developers have been working in my company, they would not be my developers for very long anymore.
Please sign in to leave a comment.