Ok, I have a question which probably wasn't asked for a while, as aerlink wasn't updated for a while, but maybe someone can still help me.
My wife has an android tab, an iPhone and a zenwatch 3. Android wear 2 standalone apps don't really cut it, so I tried to connect the watch via the old aerlink way, so she can have apps via the tab and her messages from the phone.
This solution doesn't work and I was ready to blame it on aerlink not being supported on aw 2. Out of fun, I still tried the same with my huawei watch 2 and here it works perfectly. Why is that the case?
For the facts: Tablet is on Android 6, iPhone 7 on 11.1. Huawei and Zen watch are both on 2.7 or Android 7.1.1 and the only difference is the security patch (Huawei is newer). Aerlink fails to connect to the iPhone from the zenwatch (constantly changes from connecting to disconnected) , while with Huawei it works directly.
Does anyone have an idea what could be the reason why it works on one aw2 watch and on the second not? Is there any alternative to use, which has the same effect? Thanks in advance.
My Samsung Gear S3 does not connect with my Mi 8 device. When I try it with Gear manager, it was connected well but suddenly it was disconnected. I think, there is a bluetooth issue.
Are there any people have this issue?
Same problem Samsung S3 Frontier and Xiaomi Mi 8 won't connect
I'm having the same problem with my Xiaomi Mi 8. The moment I try to synch the watch with Samsung Gear S3 Frontier, the app crashes and I can't reopen it.
I have tried uninstalling and reinstalling. Also have tried activating all permissions in the app settings, even tried the same for Samsung Gear Plugin and Samsung Accessory Service.
and did you deactivate any battery saver functionality in miui?
MarkKZN said:
I'm having the same problem with my Xiaomi Mi 8. The moment I try to synch the watch with Samsung Gear S3 Frontier, the app crashes and I can't reopen it.
I have tried uninstalling and reinstalling. Also have tried activating all permissions in the app settings, even tried the same for Samsung Gear Plugin and Samsung Accessory Service.
Click to expand...
Click to collapse
Did you reset your s3 to factory?
After you reset, unpair,reboot phone and gear
Now it will show up again.
I had the same issue, if it still doesnt open, you have to give more permissions to gear s..
That did the trick for me, and yes you also need to do for samsung accessoir services
Good luck
Im having tje same problem but with my Mi 8 se. When it attempts to pair and connect at setup, the app just closes....
Ive tried all the solutions above but not success. Im not sure if im missing swthing here. I
same problems here, with Mi max 3 and Gear S3 - Miui 10 (8.8.23)
Gear S PlugIn crash at startup
Samsung wearables app does not appear in Xiaomi mi8
Apart from the Bluetooth connection problems, the Samsung wearables app is not downloading from the Google play store displaying the message "version not compatible with this device". Guys, "ok Google" command does not work, Netflix app does not work, and now Samsung wearables app is not working either. I am putting my Mi8 for sale right now. If this is a strategy from Xiaomi, I can assure it is suicidal!
Problem Solved - Can connect my gear S2 to my Mi 8 lite again
I have updated all three applications to latest version.
1. Galaxy wearble 2. Gear S2 plugin and 3. Samsung accessory service
I give all android permissions in the setting menu of these three apps.
And, I set the battery optimization to "no restrictions" for all three apps.
And, boom. I can now connect my phone again to my Gear S2.
My android version is 9 pie and my MIUI is 10.3.5 global and my phone is not rooted.
Welcome back my galaxy.
PS. You need to update the galaxy wearable first and then Galaxy wearable will automatically download the suitable gear s plug in for the watch.
thanks for solution... its work (set the battery optimization to "no restrictions" for all three apps)
now i can use gear s3 on my Mi 9
Make sure Galaxy Wearable is installed too
Way Lyan said:
I have updated all three applications to latest version.
1. Galaxy wearble 2. Gear S2 plugin and 3. Samsung accessory service
I give all android permissions in the setting menu of these three apps.
And, I set the battery optimization to "no restrictions" for all three apps.
And, boom. I can now connect my phone again to my Gear S2.
My android version is 9 pie and my MIUI is 10.3.5 global and my phone is not rooted.
Welcome back my galaxy.
PS. You need to update the galaxy wearable first and then Galaxy wearable will automatically download the suitable gear s plug in for the watch.
Click to expand...
Click to collapse
I have a Redmi 8 running Android 10 MIUI Global 11.0.2 and a Samsung Watch. I gave the apps all permissions but it still didn't detect from Samsung Health -> Settings -> Accessories. I think the BT actually did pair but Samsung Health did not take it further. I went into BT settings and told it to unpair.
In my case, Galaxy Wearable (used to be call Samsung Gear) is somehow missing from the Google Play Store. The Galaxy Watch Plugin is available though but after installing, it would hide so I cannot run it. The same happens with Samsung Accessories Service. Looking into Settings -> App Settings, the apps show up as installed.
I ended up extracting the Galaxy Wearable APK from my old phone (a SONY) using APK Extractor, selecting it from ES Explorer, and then sending it through Bluetooth to my Redmi 8, installing it from APK. Then I ran Galaxy Wearable and was able to pair it with the watch. I lost my downloaded watch faces in the process though. Good luck.
So I originally thought something was going on with my Gear S3, but now that I have my Galaxy Watch, I'm having the same issue. I have a Note 8 paired to my Galaxy Watch and I just recently bought a new 2018 Nissan Rogue with Android Auto.
The phone is paired to the Nissan Connect System vi Bluetooth, but if I want to use Android Auto I also have the plug it in with a USB cable. About 3 out of 4 times when I get in the car I lose the connect between the Watch and the Phone. So oddly enough its not every time. And it doesn't seem to be specific to if I use Android Auto or not.
Now what is really weird is I had no issues when I had my Ford and my Gear S3 paired to the Note. So I'm guessing its related to the Nissan Rogue. Anyone have any suggestions because Contacting Nissan would be a waste. I'm assuming the Note 8 can easily support 2 Bluetooth connections at the same time.
Hi, I’ve got a Galaxy Note 9, a Surface Pro 3 and PC with a Bluetooth dongle. I’m trying to use Samsung Flow with my computers.
Between my Surface Pro 3 and my Note 9 everything works great. Instead, when I try to use Samsung Flow with my PC, I can login through my smartphone but then the Note 9 is immediately disconnected.
Is it possible that it happens because my PC does not have a wi-fi dongle (I use ethernet)? Can I solve the problem buying a wi-fi dongle?
It’s odd, but before I had a Galaxy S7 Edge and everything worked fine with Samsung Flow and my PC.
Thanks!
I hope someone recognizes this problem.
I have an Opel Astra K (2016) with an Opel Intellilink Radio 4.0 system. By connecting the phone with USB to the system, Android Auto should start on the car's system.
I've tried connecting 3 different phones, a Samsung Galaxy S8+ with Android 9, Galaxy S9+ with Android 10 and Galaxy S20+ with android 10.
The Android Auto on the S9 and S20 are preinstalled, the phones are updated. The S8+ doesnt have it pre-installed so ive downloaded the APK,
Android Auto - Google Maps, Media & Messaging 5.3.5016 (28th may 2020).
Ive used 3 different cables. Original samsung cables and a unbranded cable. None of the attempts worked. Android Auto wont show up on the car display, but it starts on the 3 phones.
After almost giving up, i made a call with one of the phones while being connected with the USB. After the call, android auto started to show up on the car screen. It looks likes it got triggered by something. When i turn of the car, but keeping the cable connected, Android auto keeps working after starting the car again. The connection goes away after disconnecting the phone (pulling out the cable). After making a call again, it starts to work again. I have no idea how this happens and what the reason could be.
The "trick" by making a phone call works on all phones and with all cables.
Anyone got an idea?