The Garmin Connect app stopped working for me today, possibly after an update. When you try to open the app, it stays at the startup screen (black screen with “Connect” logo in the middle). The app seems to be running fine in the background: it connects and syncs with connected devices, but there is no way to access the how screen and other app screens.
This seems to be a problem with all custom ROMs that are using microG in place of Gogle Play Services: te issue is reported and discussed in the /e/OS forums .
Workaround A response in the /e/OS forum thread identifies the following workaround:
I just added a simple gpx file in my documents. Then if I open it in Garmin Connect, it will open the application correctly.
I have made this more convenient by
placing a .gpx file (I use one exported from an activity on the Garmin Connect web site, but any
navigate to the file using the Files app
select the file, then from the ‘three dots’ menu, choose ‘Add launcher shortcut’, and 'Add automatically
move the shortcut to soemwhere close to the Garmin Connect icon in your launcher
clicking the icon will open the Connect app, displaying the activity contained in the .gpx file, allowing you to navigate back to the home screen
This is not a problem on my wife’s phone which is running LineageOS with GApps installed
4 Likes
Thanks for this info.
1 Like
Indeed. The issue has been escalated to MicroG’s Github:
ouvert 11:16PM - 18 Sep 25 UTC
**Affected app**
Name: Garmin Connect
Package id: com.garmin.android.apps.connec… tmobile
**Describe the bug**
Since latest Garmin Connect update 5.17.1, the app does not open. Instead, the application will simply stay forever on the startup screen (Black screen with “Connect” logo in the middle) forever on the startup screen (Black screen with “Connect” logo in the middle).
**To Reproduce**
Steps to reproduce the behavior:
1. Open Garmin Connect app, it won't open.
**Expected behavior**
The app should start normally
**Screenshots**
See below (end of the ticket)
**System**
Android Version: 15
Custom ROM: /e/OS 3.1.3-Official
**microG**
microG Core version: 0.3.8.250932-23 (b32e1cd)
microG Self-Check results: All ticked
**Workaround**
Temporary workaroud: Open any .gpx file "with Garmin Connect", and the app opens directly in the itinerary. Then use the back up-left arrow twice to go back to the main menu.
This workaround must be used each time we want to open the app...
**Additional context**
Bug has been confirmed by multiple users, including VollaOS (Micro-G) and LineageOS for Micro-G
A tread is available here:
https://community.e.foundation/t/garmin-connect-fails-to-start-with-latest-update/75199
A ticket is already opened in e-Gitlab: https://gitlab.e.foundation/e/backlog/-/issues/8920
Logs: (from another user)
```
09-18 18:01:41.103 4638 6139 W SplitInstallService: refusing to perform split installation for com.garmin.android.apps.connectmobile as the service is disabled
```
Then, the user was able to bypass warning by activating “Installation à la demande composants” option in MicroG, which gives him now:
```
09-18 18:17:26.422 10199 21676 I PlayCore: UID: [10196] PID: [10199] SplitInstallService : startInstall([gcm_on_demand_resources],[])
09-18 18:17:26.424 10199 10497 I PlayCore: UID: [10196] PID: [10199] SplitInstallService : Initiate binding to the service.
09-18 18:17:26.437 4638 4638 D SplitInstallService: onBind:
09-18 18:17:26.453 10199 10199 I PlayCore: UID: [10196] PID: [10199] SplitInstallService : ServiceConnectionImpl.onServiceConnected(ComponentInfo{com.android.vending/com.google.android.finsky.splitinstallservice.SplitInstallService})
09-18 18:17:26.456 10199 10497 I PlayCore: UID: [10196] PID: [10199] SplitInstallService : linkToDeath
09-18 18:17:26.457 4638 4658 D SplitInstallService: Method <startInstall> Called by package: com.garmin.android.apps.connectmobile
09-18 18:17:26.462 4638 4638 V SplitInstallManager: splitInstallFlow: start
09-18 18:17:26.462 4638 4638 V SplitInstallManager: splitInstallFlow will query for these packages: [gcm_on_demand_resources]
09-18 18:17:26.478 4638 4638 V SplitInstallManager: splitInstallFlow oauthToken: AuthData(email=XXXX, authToken=XXX, gsfId=XXXX, deviceCheckInConsistencyToken=XXXX, deviceConfigToken=, experimentsConfigToken=, dfeCookie=)
09-18 18:17:26.869 4638 4638 V SplitInstallManager: splitInstallFlow requestDownloadUrls returned these components: null
09-18 18:17:26.869 4638 4638 D SplitInstallService: startInstall: installStatus -> false
```
But still doesn't work.
Here's a summary of **ChatGPT** concerning this issue, after having fully analyzed all the logs and the complete description of the problem (_consider with caution!_):
"The logs show that Garmin Connect tries to use **PlayCore / SplitInstallService**, a Google component used to download and load additional modules ( the famous _Dynamic Feature Modules_ ) on demand.
Without official Google Play Services → the request fails, as Micro-G seems to has only a partial implementation of this.
When the user activates ‘On-demand component installation’ in MicroG, it goes a little further (simulated service connection), but in the end `requestDownloadUrls` returns `null` → so the app remains blocked.
In summary:
This is not just a ‘UI’ bug, Garmin Connect really needs a service that MicroG does not yet fully imitate.
The GPX workaround just bypasses the initial phase where the app looks for this module.
So it seems that MicroG would improve its support for `SplitInstallService`. In the meantime, we either stick with the GPX trick or... downgrade Garmin Connect to a version prior to this dependency."
Thank you for your attention!
stanwood
2 Likes
I deinstalled the Connect APP and installed the Version 10077. Now all is running well.
1 Like
I eventually got the same problem after a reboot, even though I haven’t updated the app.
1 Like
Garmin Connect app 5.18 (10281) is released and works for me now (iodéOS 4.25).
3 Likes
silta
October 9, 2025, 5:47pm
7
The same here. iodéOS 6.8 on FP5
2 Likes
I confirm 5.18 works, on iodé 4.x as well.
