You must log in or # to comment.
I’m glad they have separate package name for fdroid and google play. Google play has been listing apps with the same package name on play store updates. They fail to update them, but with fdroid lagging in updates, it becomes annoying and people might give in.
Ah man i just installed the .apk last week ha.
Is it worth contributing to comaps? I think it’s fun but I don’t want it to be a waste of time. Especially in the middle of nowhere where im likely the only person who uses it.
When you contribute map data it will be added to osm, so even if comaps would be forked again, your contribution will remain in use by a lot other apps
It uses OpenStreetMaps, which is used by many other services, so it’s bound to get used by someone with something!
Although it pains me to install from Google as opposed to F-Droid, it’s the only way to have Android Auto.
I can’t even get Google Maps on Android Auto (Samsung S22u). On the flip side I can get OSMAnd.
In GrapheneOS you can install Android Auto through their own “app store” (just a handful off apps, but pretty much the essential ones)
GrapheneOS does install Android Auto, but Android Auto only shows apps installed from the Play Store. Even though GrapheneOS is working on spoofing that, it still won’t help as Android Auto requires closed-source libraries and thus no app from F-Droid can include it.
Either way, my Pixel 7 has a weird thing, both with OsmAnd and CoMaps, where the location updating is janky during navigation and the speed readout is stuck on 5mph. In OsmAnd I can fix this with a setting which lets me use ‘Android API’ instead of ‘Google Play Services’ for location data. Maybe I can open an issue with CoMaps to add that option.
That was already an option in OM and now CM, and google play location is off by default in comaps now :)
Are you referring to the “Google Fused Location Service” setting? I didn’t think that’d improve location update frequency but I’ll give it a try!
