all 11 comments

sorted by: hot top controversial new old
[–] 8 points 1 year ago* (6 children)

Although it pains me to install from Google as opposed to F-Droid, it's the only way to have Android Auto.

  • source
  • hideshow 6 child comments
  • [–] 9 points 1 year ago* (4 children)

    In GrapheneOS you can install Android Auto through their own "app store" (just a handful off apps, but pretty much the essential ones)

  • source
  • parent
  • hideshow 4 child comments
  • [–] 10 points 1 year ago

    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.

  • source
  • parent
  • [–] 5 points 1 year ago (2 children)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 8 points 1 year ago (2 children)

    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.

  • source
  • hideshow 2 child comments
  • [–] 3 points 1 year ago

    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.

  • source