This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Garmin Connect not working properly on Fairphone 6 with e/OS

Hi,

I already installed and reinstalled Garmin Connect multiple times. I can login, though thereafter the app gets stuck in the initial loading screen (with that little stick figure running). When closing the app and restarting, it gets stuck in the loading screen saying "connect powered by Garmin". I left the phone running for 10+ minutes, without any changes.

Did anybody else experience something similiar? Is there a way to fix that? Is my OS being e/OS the problem? 

Thanks in advance,

Nico

  • As of this minute, it started working for me again! Seemed to be an issue that was quickly fixed by an update...

  • Same here. Moved back to 5.16.2.

  • Same problem with LineageOS for microG 22.2 on a Samsung Galaxy S10. Downgrade to 5.16.2 (10077) fixed it for me.

  • Just updated the app to 5.17.2, but this problem still persists. I've been using the workaround mentioned in this thread of opening a GPX file with the app and navigating back to the home page, which has been working so far, but it'd be great to have this fixed sooner rather than later (and without rolling back updates).

  • Exactly same problem, FairPhone 6 running e/OS.  I contacted Support at Garmin who told me I'm unsupported because the app needs Google Play natively, not MicroG.  Really annoyed with this it's making me want to sell my Garmin stuff and move to another ecosystem tbh.  Rolled back to previous version on Aurora and using that for now.  

    Someone's raised the issue on GitHub at https://github.com/microg/GmsCore/issues/3065. 

    I'm annoyed because it's the principle of the matter, I chose to protect my privacy by using a degoogled system.  If I can access the app no matter what store, it should run unless my device was unsupported but it seems that in the latest version, code exists which isn't supported by MicroG.  So I can't actually tell if this is Garmin issue or MicroG issue (which has me worried this could happen with more apps which we all use regulalry, so even if Garmin/MicroG can't fix this, going to another ecosystem would be fine until the same line of code appears in one of their app updates.  Madness.  Surely Garmin could remove the code for now until MicroG is compatible.  But, we are a minority of users (at the moment) so I dont think that would be a priority for them, unfortunately.

  • I need to confirm that Garmin Connect 5.18.0 is woring correctly on my /e/OS phone (FairPhone 5)

  • 5.18.0 hasn't been released, yet, as far as I know? Where did you get it from?

  • The latest update (5.18) fixed it for me! Super happy I'll no longer need to use the gpx route to open the app Smile

  • I just got 5.18.0 last night (I'm in the US)

    Connect app starts now, no problems noted.

  • I can confirm the brand new update from yesterday works (5.18)