Garmin Connect on Android buggy - prevents parallel usage of BT and WLAN!

See my thread on Bluetooth generally. The last two versions of Connect, and particularly the one on Google Play now, does horrid things to the network stack on Android phones.

I've isolated it and it's definitely Connect's fault. Android sucks in this regard as there is no formal means to revert to the previous version when you find something like this, which means that unless your phone is rooted and you saved it (e.g. using Titanium Backup or similar) you're just plain hosed.

Garmin needs[/b] to fix this; I had to uninstall Connect, as it was doing critical damage to battery life, Wifi connectivity and the ability to do basic things like use my Handsfree and Bluetooth headphones!

That's not nice. Did you report the issues to Garmin?

Was there any response?

I mean, I can easily reproduce what I stated in my first message and I reported the issue this morning to Garmin directly. So far without any feedback, but we'll see.

Anyone else with similar experience? Any idea of how to fix the issue easily or how to handle the issue in the most convenient way?

I have emailed them, no response thus far.

The inability to revert versions via Google Play is a MAJOR issue when things like this occur.... it's basically destroyed the ability to integrate my Fenix 3 with my smartphone for both announcements while running (e.g. per-lap times in my headphones) as well as mobile upload of data and download of courses from the app rather than plugging the watch into my computer.

Garmin really needs to provide an archive of the older APK versions so when this sort of thing happens you can roll back manually. You'd have to uninstall and then sideload the older APK, but at least there'd be a way to do it. Right now the only option I had was to remove the app entirely since it starts on boot and as soon as it starts it trashes communications.

You can try to force stop the app. That is at least something which works for me . Not very convenient but at least it works. So I can have BT and WLAN activated all time and only when I want to sync my Vivifit, which is the reason that I use Garmin Connect Mobile, the I deactivate WLAN and connect through 3G/LTE.

Previous versions available here -- I rolled back one rev and I can use my headphones again.....

https://apkpure.com/garmin-connect%E2%84%A2-mobile/com.garmin.android.apps.connectmobile

Force-stop does NOT solve the problem. Once you get hosed even uninstalling by itself won't fix it -- you have to uninstall and then reboot.

To go back you have to uninstall and then download and "sideload" the older revision; you cannot directly load over the top of an existing newer rev as the phone will reject it.

Make sure you shut off auto-updates in Play if you do this or the next morning you will probably find that it automatically put the bad version back!

Previous versions available here -- I rolled back one rev and I can use my headphones again.....

https://apkpure.com/garmin-connect%E2%84%A2-mobile/com.garmin.android.apps.connectmobile

That's a sketchy-looking site. Agree with others that some sort of verifiable archive of previous versions would be a tremendous benefit (android and ios are equally bad in this regard.

FWIW, I have an Xperia Z5 dual, and have had terrible BT stability (though not obviously related to WLAN as described above) with my Vivoactive for months - to the point where I need to reboot my phone a couple times a day. Not sure if it's a Sony or a Garmin problem (Xperia forums have shown a lot of similar BT issues, and supposedly they get better in a newer build [.200] that they've not yet released for my exact phone model), and it's very frustrating.

The certificate on that version is not a private one, it verifies as valid (known because Play then offers to upgrade it.) I wouldn't have posted it if not.

For the uninitiated all Android apps have to be cryptographically signed; Android devices will not load an unsigned application. That prevents changes to the archive. A "bad guy" CAN modify an app and then sign it with his own (self-generated even!) key but if you do that then the certificate doesn't match the one from the Play Store and Play will consider it a DIFFERENT app and refuse to update it (because it is, from Play's point of view.)

I agree that publishers SHOULD maintain an archive of their app versions so you can manually downgrade, but virtually NONE of the publishers do, Garmin included. They also have not responded to my email about their "latest" blowing up the network stack, so the options are either find the back rev somewhere or throw Connect out entirely until Garmin gets its act together.

Garmin has a new version of the GC app for Android on the Play Store this morning. No notification here of what was fixed, and of course the description is "bug fixes" (along with a note about people being able to sign in.)

As is the usual (and disgusting) practice with Android apps there is no change log of material value available so you can make an EDUCATED decision on whether to upgrade or not. However, it does (at first blush) appear to fix the interference with both my Bluetooth headphones and Wifi signals.

The last version that came yesterday did not solve the problem. Had the phone on during the night (updated yesterday afternoon and rebooted). In the morning BT had taken 60% of battery and phone was almost dead. WIFI still working really bad... if at all.

Seriously, do they never test anything at Garmin before release? As of now the Garmin Connect app is unusable and the all "connected" functionality is useless. Must sync via cable and can't use notifications.

It still has battery drain issues if Bluetooth is left on BUT the destruction of your Wifi and other bluetooth connectivity (e.g. trashing your headphone connection) is in fact fixed.