Sehr geehrte Damen und Herren, mein Handy hat die Fenix 5x Plus einfach rausgeworfen. Ich habe mittlerweile alles mögliche probiert und bin genau nach den Hinweisen vorgegangen. Ich kann die Uhr nicht mehr auf dem Handy installieren.

Hi, 

Mir hat diese 'Anleitung' geholfen, bei meiner Garmin 935 & Android 8.X!

Hier die ursprüngliche Adresse, geht aber nicht mehr.

forums.garmin.com/.../1271446-unable-to-pair-fenix-3-with-android-7-0-phone

# Android 7.0; P8 Lite non rooted, Garmin Fenix 3 8.5 firmware, Garmin Connect 4.0.7

OK, so bit of background, I had this same issue c1 year ago on my Nexus6p (also made by Huwawei) that was running Android 7.0 at the time. I did not notice the issue as I had upgraded the OS, and device already connected, so only when I wiped the OS, did I get the error. I didn't think too much on it as by timing 7.1 update landed from google that fixed the issue. The error tbc is not with Garmin dev team. (by the way the P8 is not on the bluetooth tested list... https://static.garmin.com/gcm/BLE_Android.pdf )

So... I connected the device above to android studio there and captured a list of the errors from the moment you click Add a device to when the passkey prompt on the watch disappears, after too short a timeframe, c3 seconds. It is shown below, the items relating to this issue.

11-10 09:59:21.618 22846-22846/? E/Bth: BigDataReceiver:intent or context is null.
11-10 09:59:21.637 22846-25516/? E/bt_btm: btm_ble_scan_pf_cmpl_cback: unknown operation: 0
11-10 09:59:23.259 22846-22846/? E/Bth: BigDataReceiver:intent or context is null.
11-10 09:59:23.269 22846-25539/? E/Bth: BtExceptionProcessor:deviceType unknown.
11-10 09:59:23.281 22846-25516/? E/bt_l2cap: BLE connect is NOT magiclink

[ 11-10 09:59:23.281 22846:25516 I/ ]
stop ble scan for create connection
11-10 09:59:23.499 22846-25516/? E/bt_btif: bta_gattc_cache_load: can't open GATT cache file /data/misc/bluetooth/gatt_cache_e3eb472c8152 for reading, error: Permission denied
11-10 09:59:23.502 25531-25531/? E/iConnect: ConnectService:cannot get cachedDevice,return
11-10 09:59:23.502 22846-25503/? E/Bth: BtExceptionProcessor:deviceType unknown.
11-10 09:59:23.541 3923-3923/? E/Bluetooth_stlib: BluetoothEventManager:Got bonding state changed for E3:EB:47:2C:81:52, but we have no record of that device.
11-10 09:59:23.554 470-470/? E/ServiceManager: try to find service failed, not allowed access from isolated processes.

Now you might not know whats going on above, but the multiple wireless services are clashing with each other, admittedly this is in some way due to the request order below...

A: Location services set to on;

B: Wireless on; 

C: Bluetooth on; 

D: Mobile data on

2: Garmin checks for A+B+C at various points, and if A+B+C are on when you click add device your doomed/ DOA

Anyway, to get round this is actually quite simple, but yes annoying...

...

1 A+B+C+D on
2 open garmin on phone, no other apps open as seems sensible as a given as well
3 in the welcome visual of connect app, click add
4 the graphics will appear for fenix 3 hr ect, this is connect app using your internet connection to get the list of JPEG images, and it also checks for location on, if not will error.
5: don't do the last step in blue yet that you would now do on the app... where it initiates the process
6: switch off wireless, and location services, and mobile data (A+B+D)
- at this point what matters is nothing mess up Bluetooth connection
7: on fenix3, start pair new device
8: now - silly but tricky bit, click the blue bar on connect app to start the pairing
9: enter passkey
10: immediately switch on again (A+B+D)
11: tbc your not a script but a person so you will end up doing it >1000ms, so enough time to let the initial Bluetooth process be successful
12: it does need those services (A+B) after the third green icon on the connection journey, hence why we switched them back on
13: if interested what you should notice is the passkey is now staying on the watch for c10 seconds, service not stopped
14: if should all work now

For reference I wiped my watch ect in frustration until realised wtf, I am just going to fix this or change firmware so I appreaciate the frustration. My view is that Garmin Devs if listening your really going a bit overboard here with using so many services accessed in a short time, when Bluetooth is flaky. I actually use oreo (8.1 beta) now on my nexus6p all works great for garmin software, just changing phones for a month before my pixel xl2 arrives, hence why I ended up with a p8 lite...

I hope this helps.

Oh, switching off GPS once all setup, for a few mins, will allow any reconnecting issues to self resolve. 

Gruß PW