Roadstr 0.4.15
No Google code left in the app. None.
Roadstr was built to run on phones with no Google services, and it did. But the APK still carried Google Play Services code — fifteen classes it could never execute on the very devices this app exists for. Nobody put them there on purpose: they arrived as a dependency of the location plugin.
They are now gone.
com.google.android.gms.* 0 classes
com.google.android.play.* 0 classes
Google components in manifest none
What was there, and why it survived so long
Roadstr has always read your position through Android's own LocationManager — every single call site asks for it explicitly, which is what makes the app work on GrapheneOS, /e/OS and LineageOS without Google apps. The Play Services code was never called.
It shipped anyway because geolocator decides at runtime whether to use Google's fused provider or Android's own, so both remain reachable to the compiler. Excluding the library at the build level simply broke the build: the Google client will not compile without it.
What changed
geolocator_android 5.0.3 (MIT) is now vendored in the repository with the proprietary path removed — one file deleted, three lines changed, one dependency dropped. The Dart API is untouched.
Also removed: Google Play Store split-install and deferred-delivery classes, which Flutter links for apps that download parts of themselves from the Play Store. Roadstr does not.
What does not change
Nothing about how location works. Same provider, same accuracy, same behaviour on de-Googled phones — there is simply nothing else left beside it now. Location permissions are unchanged.
Get it on
@Zapstore or directly from Github (via Obtanium) at

GitHub
Release roadstrapp.0.4.15.apk · roadstrapp/roadstr-app
Roadstr 0.4.15
No Google code left in the app. None.
Roadstr was built to run on phones with no Google services, and it did. But the APK still
carr...
F-Droid repo incoming as soon as it's approved.
As always #FuckGoogle
#Roadstr #GrowNostr #OtherStuff #Navigation