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
My testing: I have also given this feedback via the Google playstore (Beta send feedback to developer)
Route loaded fine from my S24, however the map stayed still and I saw the route line slowly disappearing when riding. Audio instructions carried on though. Looks like a map sync issue fro the phone.Â
My wifes S25 was a little better but intermittantly had the same issue.
Hi everyone,
First of all, a big thank you to all of you who have already joined the beta program and taken the time to test Android Auto on real rides. We really appreciate the detailed feedback you’ve been sharing here 🎉🙏🏼!
This is a group reply, but please know that all the individual points you’ve mentioned are being collected and reviewed by the team.
As you’ve noticed, the current version is still quite basic. That is very much intentional. After such a long wait, it was important for us to finally get a first working version out there rather than holding everything back until it’s feature complete. This allows us to see how it performs in real conditions and, just as importantly, what you’re missing most.
A quick note on expectations: for both Android Auto and CarPlay, all third party navigation apps are limited in what can be shown on the screen. Google and Apple enforce fairly strict guidelines to keep the interface clean and reduce distractions while riding or driving. So some elements from the phone app cannot be transferred one to one.
That said, there are definitely improvements coming. Some of the points you’ve raised, like behavior around reconnecting, route handling, and general usability, are exactly the kind of things we’re focusing on now.
We already have an update ready on our side and are currently waiting for Google’s approval. So it’s worth keeping an eye out over the next days and weeks as new versions roll out.
We’re really happy to finally have something in your hands and to be able to build this together with your feedback. Thanks again for your support and for riding with us.
Ride safe!
Let's just make sure the road speed limit is transferred. Google maps is doing that, so I would assume Android Auto allows to do that.
Â
However, Google maps do hide current speed on Android Auto which I hate. But I guess it is what it is and makes sense if Calmoto won't be display the current speed either.
Waze, which is also owned by Google, displays the road's speed limit plus your current speed, so both are available in Android Auto.
Same goes for Flitsmeister, is also displaying current speed and speedlimit next to each other in AA.Â
It is good to read Calimoto is making progress now with AA. I've switched a while ago to a different app... if Calimoto has everything up and running I will do some tests, but they really need to do their best to get me onboard again. We've been neglected way too long, which for sure makes me doubt for future upgrade / changes and so on.
Same observations as previously mentioned regarding Beta issues. One point I find odd regards to Google approval in that AA has screen restrictions yet if you use a phone or a true mirror device these don't apply in any case. I'm currently using an alternative app but trialing Calimoto on 30 day offer. Subject to this still not being 100% finished are additional trial periods available for Beta users?
Calimoto popped up when I connected my Samsung S24 to the Aoocci screen and it seems to load everything as supposed to, but the indicator for my location doesn't move. It calculates the distance to the next junction and counts down, but the map isn't moving. If I open another app and go back the location is updated. Then it freezes again.
I tried the Android version on the weekend. It seemed to perform okay, but when I stopped for a coffee, it ended my ride. On the Carpuride screen, it asked me if I enjoyed my ride. It didn't ask if I wanted to pause or end the ride as it normally does.
I note a new version is now installed, are there any release notes? 2026.4.1
Hi everyone (and @dicky68) - thanks again for all the feedback you’ve been sharing. We’re collecting everything on our side in Support and passing it along to the product team and developers. It really does make a difference.
As some of you have already noticed, we’ve released one update since the beta started. Another one was actually planned for release today, but it looks like Google is holding it back for the moment. That can happen during the approval process, but we’re hopeful it will be available soon.
Regarding the question about extending the trial period for beta users: unfortunately, that’s not something we can offer. That current 30-day trial is already amazing (14 days is the usual). Once it ends, it might be worth trying the weekly subscription option, or reaching out to Support directly so we can see if there’s anything we can do on a case-by-case basis.
On release notes: the most relevant changes are always included in the update notes in the Google Play Store. Internally, we track a lot more changes, but many of those are technical improvements in the background, things like data handling, stability, or smaller adjustments that aren’t always directly visible in the app.
Thanks again for testing, for your patience, and for helping us shape this step by step.
Ran Calimoto on a Carpuride W702S Pro with a Pixel 9a today. Ran flawlessly. Route popped up as soon as it was started on the phone and jumped back in after every stop. Running Calimoto and radio app for over 4 hours and used 46% of the battery, so should be good for a full days tour.
Graphics were better than I expected but need to investigate Group Ride feature - not sure if it was the setup or something we did wrong but other riders not showing.
Well done Team and thank you. Just in time for my Spain tour.
Tried first time S23 and Carpuride W702 Pro. It doesn't really work if my phone is locked. Also, when running both on the phone and on Android Auto, I can see that Android Auto doesn't properly update the arrival time. Also, the next turn is delayed and/or often not updated compared to what I see on phone screen,
Calimoto app doesn't have permission to be given for all the time, instead of "when using the app". Something is wrong, that the option doesn't appear. That might explain why it doesn't work if the phone is locked.
Left beta program, uninstalled. Will try the latest non beta version tomorrow. I hope will work better.
I did run it today the latest not beta version. And the issue persists. The phone must be unlocked. Otherwise it stops tracking almost immediately on Android Auto screen. Something is surely off. Other apps work fine.
Battery use is unrestricted, the only thing as I mentioned before is the location setting is set to "when using the app". Unlike other apps, the setting "always" doesn't exist for Calimoto.
And even if running both on phone and Android Auto, Android auto still doesn't update final arrival time and distance and the next turn stop being updated after a bit of time too.
Mine is set to "when using the app" and "Precise Location" but my phone is set to stay unlocked when attached to my headset. Screen is turned off.
Thank you, SteveMat. I tried to set screen auto off at 15 seconds and to always be unlocked when connected to my Carpuride.
When having breakfast the screen would switch off, but when running Calimoto it wouldn't. Not sure if Calimoto is preventing it or because I've set up Carpuride as to keep phone unlocked.
Will try again tomorrow after removing Carpuride. But this shouldn't be needed. With phone locked Android Auto screen should keep updating.
Beth, is there a plan to put a speed limit on Android Auto screen like Google Maps do?
Hi everyone,
thanks again for the additional testing and feedback 🙌
It’s great to see that for some of you, like SteveMat, Android Auto is already running smoothly. At the same time, reports about things like arrival time / next turn not updating, issues when the phone is locked, and requests for more information on the display are very helpful for us as well.
Regarding the question about showing the speed limit on the Android Auto screen like Google Maps: that’s a great suggestion. It’s not available at the moment, but we’re happy to take this on board and pass it along to the team.
We’re continuing to collect all of this feedback and share it internally. Thanks again for your testing, patience, and detailed reports — it really helps us improve Android Auto step by step 👍
I'm currently on a European tour with everyone in the group using Calimoto. Most are using iPhone's and a few using Android. Of those on Android, one is using Android Auto. To summarise: only the Android Auto guy is struggling.
1) As others have said - no information on speed or speed limit is shown.
2) The routing is sometimes different to those using iPhone. This has also been the case with one other Android user who is NOT using Android Auto.
3) When Calimoto is running (Android Auto) and you stop the bike (engine off) you find that when you start again Calimoto does restart, the next turn indication works and the voice instruction works but the map freezes. The route is still running on the phone but you seem to have to touch the phone screen for the map, on the AA, to 'wake up' and unfreeze.
4) I am experiencing routing issues (algorithm?) with different turn instructions compared to my iPhone colleagues; their routing in invariably correct. This is a route that was 'built' on iPhone and shared with the group including AA users. It was the same route!
I do like Calimoto but it's currently unusable with AA especially if you are riding in a group with iPhone users; you simply can't trust that it will work or, when it is working, that's it's giving you the correct routing. Keep working on it guys.
I turned on the data saver mode in Calimoto. And selected screen off mode. Whenever the turn is approaching the phone screen activates. Otherwise it stays off, but phone is unlocked. This way the Android Auto screen keeps updating the map and directions.
Hearing about differnces between Android and iPhone is quite unsettling, because this part should be the same on both platform. The algorithm in theory should be agnostic.
However, I also know that iPhone users get 4 things on the phone while Android only 3 (like elevation, next point. etc).
And yes, the speed limit is really an important missing peace.
Hi everyone - first of all, thanks a lot for all the detailed feedback, testing, and reports over the last weeks. Even when we don’t reply to every single comment directly, the Android Auto team is actively collecting and reviewing this feedback to better understand what’s working well, what still needs improvement, and which features are currently missing.
As many of you have probably already noticed, updates are coming out very regularly at the moment because Android Auto is still quite new for calimoto. The most recent version is 2026.04.6, released on May 5th, and more updates are already on the way.
A few quick notes on the topics mentioned here:
• Speed limits:
We’ve heard this request a lot and the feedback has definitely been passed on to the developers. Right now, the main focus is still stable navigation and overall reliability, but the team is aware that speed limit information is something many riders would like to see in the future.
• Map freezing after stops:
This is one of the points currently being investigated more intensively. Thanks as well for sharing workarounds and settings that helped in specific situations, that kind of information is genuinely useful.
• Different routing / turn instructions between Android and iPhone:
In some situations, shared routes can still behave slightly differently depending on factors like map data updates, local traffic or road conditions, recalculations, avoidances, device settings, or platform-specific behavior between Android Auto and CarPlay. The developers are already working on improving route consistency across platforms.
If you regularly ride together in a group, we’d currently recommend using the Group Ride feature instead of simply sharing routes. That way everyone follows the exact same route, and you can also see each other live on the map, which makes regrouping much easier if someone stops along the way.
One important difference at the moment is simply that Apple CarPlay has been available in calimoto for quite a while already, so many early issues there have already been ironed out over time. Android Auto is still in a much earlier phase, and that’s why your ongoing feedback is especially valuable right now.
Thanks again for the patience, the testing, and the honest reports so far. Please keep an eye out for future updates đź‘€
Ride safe!
One more thing to add to my feedback. I found that whilst following a Calimoto route you either receive or make a phone call (via Android Auto) when the call ends the map freezes. As with other instances, all though the map freezes the voice instructions and 'next turn' function still function.
Ainso, et al,
It would help both us as interested parties and the developers if you stated your phone type and Android version. You may be on a really old unsupported phone or a really new phone running the beta of v17. Or it may be a particular phone type, e.g. Samsung phones have different issues to Pixels.
Further to my last post, I have now been running AA for 2 weeks on my tour of Spain (solo bike) and have not had any of these issues.
The differences between Apple and Android have always been there. I usually ride with 2 Apple users and there can be differences between the newer and older Apple phones, as well as with the Android.
Current phone is a Samsung Fold 5 running Android 16 and One UI version 8 with the latest version on Calimoto. Happy to provide any other information that may help.
Howdy - thanks again for the additional reports and also for helping each other out here in the comments, that kind of information is genuinely useful for both us (in Support) and the Android team đź‘Ť.
The issue Ainso described regarding the map freezing after a phone call (or another app interrupting) is indeed a known bug that currently seems to affect only certain users and device combinations. The Android team is already aware of it and actively investigating it.
The additional device details are especially helpful here, since they help narrow down which Android versions, manufacturers, and device types are being affected. So thanks as well for sharing those details!
As SteveMat already mentioned, Android devices can sometimes behave quite differently depending on manufacturer software, Android version, beta versions, battery optimizations, and system overlays like One UI, which makes these kinds of issues a bit more complex to track down.
Please keep your eyes open for upcoming updates, and thanks again for all the testing and patience so far đź‘€.
Keep it shiny side up!
Hi Beth, Many thanks for taking the points on board and providing the update. Cheers
Hi Beth, just got the latest version. Huge step up, thank you. I know you are working on the actual speed v speed limit but is there any chance of getting routing options on the AA screen as well?
Heya @Ainso - great to read the latest version already feels like a big step forward, thanks for the feedback!
You may actually have noticed that the update released on May 18 already added a few new Android Auto features, including:
• opening planned routes directly in Android Auto
• dialogs for joining routes or handling blocked roads directly in AA
• destination search in AA
• the option to start recording directly from AA
So step by step, more functionality is definitely making its way over to Android Auto.
I’ll gladly pass on your feedback regarding additional routing options on the AA screen as well. Requests around speed limits and current speed are still actively being discussed and worked on.
Cheers!
Please sign in to leave a comment.