Problems with Android 10 - Samsung Gear Sport

Need help. Recently updated to MIUI Global 11.0.1 on my Mi 9 Lite and now 2 problems with my Gear Sport.
It keeps losing the Bluetooth connection and no notifications are coming through.
I set no restrictions for battery saver for:
- Galaxy Wearable
- Gear S plugin
- Samsung Accessory Service
And permanent notifications allowed. Cleared cache.. Don't know what else to do.

Hi.
Go to developer settings and switch bluetooth profile to AVRCP 1. 3
It help me a lot.

On my Pocophone F1 MIUI, I must set anew "no restriction" for Gear plugin and "accesory service" every time the phone is rebooted. The phone do not keep this setup for battery other reboot

Jochman14 said:
Hi.
Go to developer settings and switch bluetooth profile to AVRCP 1. 3
It help me a lot.
Click to expand...
Click to collapse
had a same problem,thanx 4 advise)

Related

gear s2 classic no option to answer calls ,.only reject

hi guys
im not getting any option to answer calls..
only option to reject from the watch
i know the watch has no speaker.but i thought it woudl allow me to answer like android wear..and then i speak on my phone
i tried googling..some said it worked before an update..does anyone know which version of the gear app allowed this?
or is there a way to fix it
i've checked and all permissions are given to the app
Mayur
mayurh said:
hi guys
im not getting any option to answer calls..
only option to reject from the watch
i know the watch has no speaker.but i thought it woudl allow me to answer like android wear..and then i speak on my phone
i tried googling..some said it worked before an update..does anyone know which version of the gear app allowed this?
or is there a way to fix it
i've checked and all permissions are given to the app
Mayur
Click to expand...
Click to collapse
This thread suggests that the option to answer calls on BT-only watches works only with Samsung phones: http://forum.xda-developers.com/gear-s2/help/question-answering-call-watch-t3251133
tstreete said:
This thread suggests that the option to answer calls on BT-only watches works only with Samsung phones: http://forum.xda-developers.com/gear-s2/help/question-answering-call-watch-t3251133
Click to expand...
Click to collapse
thanks for your reply and help. i did read that..but some people said it used to work..was wondering which version worked..
silly of samsung to disable this feature.
I still have an option to answer a call on my s2 classic. I hope it wouldn't just disappear like the messaging on the 4 app shortcut widget.
I recently went between an s7 edge and a pixel with my gear s2. I noticed I was no longer able to take calls on the watch when I went over to my pixel, but it was not a problem when using my s7 edge.
I figured it out. I don't know why, but I can say for certain that when a gear watch connects to a samsung phone, it defaults to the connection being a media and phone device (rather than the low-powered mode that, say, android wear watches do). Automatically. Always. On my pixel, the connection as a media and phone device must be initiated manually.
On my pixel I went to bluetooth devices and connected to my gear s2, which connected as a media and phone device. After that, the watch will answer phone calls on the watch directly. This all makes sense. The only difference is that on my pixel (anything other than my samsung phone actually), it does not default to connecting to the watch as a media/phone device (only low-powered peripheral).
Hope that helps.
I know this is old, but I wanted to offer a solution to the same problem I faced with a ZTE Blade Max. Goto bluetooth settings and click S2 in paired items then settings or options, then tick the option for phone audio. Problem solved!
cellfonepimp said:
I know this is old, but I wanted to offer a solution to the same problem I faced with a ZTE Blade Max. Goto bluetooth settings and click S2 in paired items then settings or options, then tick the option for phone audio. Problem solved!
Click to expand...
Click to collapse
Hi there! I've tried to use this solution but I can't find any kind of option as the one you suggest. I have a Xiaomi Redmi note 7. Is there any other option you can offer? Thank you so much for your time!
you have to change your build.prop to show a samsung device. cent remember where it is in the build.prop, but im fairly certain that this is the issue. This popped up pretty frequently back when the watches first came out and i had to do this myself as i was running an AOSP ROM on my old S5 when i got my first smartwatch (Gear 2 Neo) until i flashed android wear on it and no longer had the option to answer calls at all on my watch

Watchmaker (App) Issues

Hey guys,
So I recently downloaded the new Watchmaker app that was released for Tizen (finally), but I'm running into some issues and was wondering if you guys were experiencing the same problems or have any fixes.
The problems are basically to do with the sensors.. So for all of the watch faces, my steps are showing as 0, the weather is showing as default (something like 6 degrees with 95% POP), and heart rate doesn't update as it should. For the heart rate, if I reload the watch face, it updates with the newest heart rate (I think), but the steps and weather are stuck at default (0 for steps).
Mostly everything else works (battery, stop watch, time, etc...), but for some reason the steps and weather won't update. I have checked to see that the scripts were correct..
For heart rate it's {shr}, for steps it's {ssc}, weather is {wtd}.
So, anyone experiencing these issues or have any fixes? I'm definitely out of ideas.
Thanks
Wait for an update. It's still new and buggy for now.
Sensors don't work reliably for me either, it's an app issue as noted, steps are way off.
Sent from my SM-G935V using Tapatalk
There's an update due out this week to fix these issues.
Lakota said:
There's an update due out this week to fix these issues.
Click to expand...
Click to collapse
Where did you see that...I'm running the newest beta of the watch WM app, and steps still don't work.
Sent from my SM-G935V using Tapatalk
I read something about it over on the developers Google+ page.
It mentioned being updated and submitted to Google for approval so should be due about Wednesday.
Lakota said:
I read something about it over on the developers Google+ page.
It mentioned being updated and submitted to Google for approval so should be due about Wednesday.
Click to expand...
Click to collapse
Thanks, I hang out over there and all I've seen from Alex Curran (WM team) on things addressed in updates is below, which doesn't include a fix for reading sensors/getting accurate step data. However (some good news here) Alex did said today in a post on G+ that Tizen 3.0 (not released yet) will provide access to the watch sensors from native Tizen 3rd party apps. For some reason (known only so Samsung), currently only web apps (like the Facer app) have access to the step sensor, and WM (being a native Tizen app) can't access the watch's step sensor (at least not until Tizen 3.0 is released).
So hopefully Samsung will release Tizen 3.0 soon!
WM watch up stuff in progress...Have you seen anything else?
Two days ago, from Alex:
New Samsung Gear Companion App in Beta :
http://androidslide.com/watchmaker_tizen.tpk
- Fix for spaces in curved text
- Fix for some watchfaces showing black in AOD
- Fix for incorrect vibrations
Four days ago from Alex:
New Samsung Gear Companion App in Beta :
- Support for Tizen-based tap actions on watch, e.g. launch Alarm, S Health, etc
- Weekdays / month names localized to correct language
- Fixed {awname}
Watchmaker doesn't seem to like custom roms on rooted Samsung devices (KLTEDV with custom Nougat rom). I can get it on the phone but when trying to install the companion app to the watch (Gear S3) the phone crashes. All my other companion apps install without issue from phone to watch, it's just Watchmaker that doesn't want to play the game? Yes I do know that I can always go back to a stock rom but it just seems a bit unusual that this app is the odd one out amongst the rest?
I was able to install Watchmaker on my Gear S2 with a Samsung Note 3 on custom Kitkat rom (SlimROM). My issues so far are that I can't update the app on the Gear S2 (even though it states "installed" in the notification, I only see the installation icon looping indefinitely on the Gear Store on my phone) and Watchmaker can't update weather status anymore...
I'm having similar issues with my Gear S3 and Watchmaker.
I can build faces and scripts that run and update great in the app, but then don't function properly once loaded on the S3.
Examples: Temperature units are always displayed as C regardless of setting in both app and watch.
Temps and weather info don't udate on the watch. They just display whatever value they had when I pushed the face from my phone to the S3.
Timezone handling is off, even on my phone. Trying to set something as simple as UTC is horrific. And having a clock that displays the time at home when I'm traveling doesn't work no matter how I've defined the time zones. Very frustrating.
Ok...most of my issues seem to be resolved now. One problem was my phone somehow got stuck in a manual time zone mode. Fixed now. Took a couple of sending the eatch face to my watch but suddenly started displaying other timezones properly.
Ditto for weather status.
Only remaining problem was temps are still in Celcius, but some trivial math worked around that.
Sent from my SM-N910T3 using XDA-Developers Legacy app
My watch maker can't seem to find my gear s3. even after i reboot and do all the suggestions.
Hello guys! I've changed my smartphone and I've re-installed watchmaker, and now, I can't find a way to make the phone's battery level more frequent refresh.. I don't remember.. Thanks
WM S3 gear step counter
Dear friends,
WM obviously can not show steps from gear S3, using the sensor built in. Nevertheless there is a workaround using data from S-Health app. Now my question : step value on my gear shows 9012 steps, counter on s-health app shows equal value of 9012 steps,
but on watchface from WM it shows 14827 steps. Using {ssc} command for this value.
Does anybody has an idea where this value comes from, or how to setup that both values are equal.
By the way, setting for
Settings: Watch
Steps source for Gear S2/S3 (Samsung Health on Phone (Strategy 1)
Thanks for support
Peter
peter_mars said:
Dear friends,
WM obviously can not show steps from gear S3, using the sensor built in. Nevertheless there is a workaround using data from S-Health app. Now my question : step value on my gear shows 9012 steps, counter on s-health app shows equal value of 9012 steps,
but on watchface from WM it shows 14827 steps. Using {ssc} command for this value.
Does anybody has an idea where this value comes from, or how to setup that both values are equal.
By the way, setting for
Settings: Watch
Steps source for Gear S2/S3 (Samsung Health on Phone (Strategy 1)
Thanks for support
Peter
Click to expand...
Click to collapse
It's the S-Health app on your phone since it's showing your combined steps from both phone and S3. I tried changing this in the S-Health app to stop counting steps on the phone and that did work, but now it seems to have stopped the S-Health auto-sync of getting the steps from the S3. When I launch the S-Health app on my phone, then it syncs them. I tried changing it back to combined and turned the phones step count back on to try and get auto-sync back, but it didn't fix it. Anyway, I'm now stuck with no autosync of steps from the S3 for my troubles.
If you want to try this as your, pardon the pun, mileage may vary, here we go, but note that this could put you in the same no auto-sync between S-Health and the S3 situation that I'm in now.
Open the S-Health app on your phone, select Steps to get to the steps main screen, select the hamburger menu and then select View your Step Count Data, select the mobile phone, now select the hamburger menu and you'll see how to stop the phone from counting steps. Then select the hamburger menu and select View your Step Count Data and set it to the S3 or All Steps since it's the phones S-Health step count is disabled.
Sent from my SM-T800 using XDA-Developers Legacy app
Sad... since this thread started.. this app STILL has problems..for me at least
I had a similar problem with the steps recorded by phone and gear. After I managed to filter only the steps from gear (in a custom app) I found out that the synchronization between the phone and gear is very bad. Even the steps count changes in the gear, the SHealth on my phone still displays the old value. If I disconnect and reconnect the gear it updates the value. Not reliable for a company app.
Thoughts?
Can't install companion app on Gear S3
Strange
I have Watchmaker on my Galaxy S8+ but when I try to install the companion app on my Gear S3 I receive an error msg saying that this app is not available any longer for purchase, or that it's not supported in my country or device.
I purchased the full version and have it installed on my phone.
please advise how to install .tpk in gear s3 frontier?
please advise how to install .tpk in gear s3 frontier?
farooqrehmani said:
please advise how to install .tpk in gear s3 frontier?
Click to expand...
Click to collapse
Use SDB (Smart Development Bridge) from your computer to install the tpk file.
1) To use the SDB in a target device, set the device to the SDB mode by going to Settings > More system settings > Developer options > USB debugging in the device menu.
2) Turn on wifi (not auto) on your watch and make sure the watch is connected to the same wifi as your pc.
3) Use sdb connect and sdb install commands to perform the install. More details about SDB here: https://developer.tizen.org/dev-guide/2.4/org.tizen.devtools/html/common_tools/smart_dev_bridge.htm

No notifications

Since I updated my Pixel to Android 8.0 Oreo about a month ago, I don't get any notifications any more. The only thing that seems to be working is phone calls which I can see on my gear.
What I've tried to do, to solve it:
- Cleared data for the Gear app
- Uninstalled and reinstalled all Samsung applications
- Factory reset the Gear
- Checked that the Gear app has permission to notifications
- Checked that the Gear has the latest firmware
- Rebooted my Pixel
- Tried to connect my Gear S3 to a Huawei phone running Android 7.0 (notifications worked)
- Contacted Google that said the issue probably is because the Samsung app doesn't support Oreo
- Contacted Samsung that said Google is "probaby right" and I'll have to wait for an firmware update for the Gear which they have no ETA for?
If Google is right, everyone with Oreo should have this problem? Or atleast someone else? Is that the case?
I have Oreo beta on my Nokia 8 and have no problems which weren't present on nougat.
No issues with notifications.
Sent from my TA-1012 using XDA-Developers Legacy app
Ok, does anyone else have any idea of what can be the issue for me?
I'm having the same issue. Also with my pixel. Tried everything you have also done. Almost at the stage I'm about to switch back to my old moto 360 until they release a patch. Not being able to receive any type of notification is a deal breaker for me.
have you tried to clean cache, stop the Bluetooth process on pixel and run it again?
Anybody got solution for this?
I upgraded OnePlus 3 to Oreo and notifications stopped showing on Gear.
Soon afterwards I upgraded Gear to Tizen 3 but that didi't solve problem.
The new software update that was released a few days ago solved the issue for me.
Exactly the same problems and frustrations
In short, have tried all the same actions as set out by yourself. No Gear 3 notifications started with Pixel upgrade to Android 8.0. Like others have stated here, makes wearing and relying on Gear watch very marginal. I bought Gear watch to pickup notifications when doing outdoors, relatively hands free sporting activities.
Everyone: please keep THIS discussion thread alive in search of eventual solution. Thanks. John, Sydney Australia
Same issues
I recently purchased a gear s3 Frontier watch, after much researching, it was the one that most fit my wants.
It is paired with my Pixel phone and for the first 3 or 4 days it worked great but now I don't receive any notifications at all except for Samsung Health... Notifications are all turned on but nothing comes through?
It seemed to have started with the Tizen 3.0 update. But could't say if it was immediately after or a day or two later. I've done multiple resets but nada.
Phone calls do come through to the watch but my phone doesn't ring anymore when the watch is connected..
No settings were changed on the watch or the phone app.. One day it worked fine, the next day, everything quit...
This is very disappointing... these notifications were the reason I wanted a smart watch in the first place.
Any idea whats going on?
The watch is SM-R760 running Tizen 3.0.0.1 version R760XXU2CQL1
Knox 2.2.0
Know Tizen 2.2.0
SE for Tizen 1.0.0
TIMA 3.0.0
Pixel Phone on Android 8.1.0
Snapdragon S8 on nougat with a similar problem. My notifications will disable themselves and the switch to turn them back on will be grayed out and unselectable. Only way to get them to work again is by rebooting the watch and the phone, but it will only work for a few hours until it's broken again.
I have a similar problem with my Oneplus 3.
Evertyhing worked fine until I updated my phone to OxygenOS 5.0.3 Android 8.0.0. Since then the Gear S3 doesn't receive any notification. The only one are phone calls.
The settings for notifications are on (in the Gear App and OS settings unchanged). Resetting the watch didn't change anything. Round about 2 times a day the gear looses the bluetooth connection for ~30 seconds which is new as well.
Resetting the phone is no option.
Any ideas or new information about this problem?
nouseeme said:
I have a similar problem with my Oneplus 3.
Evertyhing worked fine until I updated my phone to OxygenOS 5.0.3 Android 8.0.0. Since then the Gear S3 doesn't receive any notification. The only one are phone calls.
The settings for notifications are on (in the Gear App and OS settings unchanged). Resetting the watch didn't change anything. Round about 2 times a day the gear looses the bluetooth connection for ~30 seconds which is new as well.
Resetting the phone is no option.
Any ideas or new information about this problem?
Click to expand...
Click to collapse
I reinstalled the Gear app, repaired and resetted the watch which didn't change anything.
Though I forget about the Samsung Accessory Service app. After reinstalling this, rebooting the phone and repairing the watch the notifitications are working again.
In the matter of connection loss I can't tell not yet.
nouseeme said:
I reinstalled the Gear app, repaired and resetted the watch which didn't change anything.
Though I forget about the Samsung Accessory Service app. After reinstalling this, rebooting the phone and repairing the watch the notifitications are working again.
In the matter of connection loss I can't tell not yet.
Click to expand...
Click to collapse
I know this is an old thread, but I stopped getting notifications on my Oneplus 7 Pro - Android 10. I had to turn off battery optimization for the three Samsung apps - Galaxy Wear, Gear Plug in and Samsung Accessory Service. I now have notifications back.

Pairing issues with Pebble watch

Does anybody has a pairing issues with Pebble smartwatch? When it's paired, everything is OK. But if it disconnects, it does not connect again and it says that the pairing code is wrong...
Hi,
no problem with my Time Steel, latest Rebble firmware and App.
Did you disable all doze features for the app and allowed background activity?
Tried a factory reset of the watch?
die_braut said:
Hi,
no problem with my Time Steel, latest Rebble firmware and App.
Did you disable all doze features for the app and allowed background activity?
Tried a factory reset of the watch?
Click to expand...
Click to collapse
Yes, I did all that... No change...
Old thread, but I found an answer elsewhere that seems to have helped me so far. Try changing the supported version of AVRCP in the Bluetooth settings of your phone. On mine (OnePlus 7T, Android 10) I had to enable developer mode, then found the setting in there. Setting to 1.3 (default was 1.4) seems to have made things much more stable.

Couldn't connect Samsung Galaxy Watch after MIUI12 is updated

Hi, I have a Xiaomi 10 pro
just updated to MIUI12
ever since then my watch has a "watch" logo on top which means is not not connected to bluetooth.
I have reset the phone's network setting a couple of times.
the watch is also reset.
I have used the Galaxy Wearable to connect the watch. It detected the watch and seems connected (but under bluetooth menu it just saved the watch setting without indicated connected)
the it stuck at the "finishing pairing" page.
Whenever it asked me for permission i either allow it when the apps open or allow it all the time.
but it just stay in that finishing parining page over 20 minutes.
any body faced this problem after updated to MIUI 12?
I am still on Miui 11 but after last security update for June had loads of issues with constant disconnect and errors with Samsung Galaxy Active 2 watch.
Gonna get rid of this and get a Mi Band 5.
I know it's totally different device but not using all the functionality currently.
Sent from my Mi 10 Pro using Tapatalk
I want to stick to a watch instead of a sport band.
Anybody could hint me?
I have tried to connect the watch to an earbud, it works perfectly fine. quick pairing and working.
however it is just not the case with the phone.
again my phone is pairing perfectly with other devices too like my car, earbud, headset.
As i do workout quite often, all the data are store in the watch and not going to the phone. also it is not uploading to the database when it is already connected to WIFI.
I have the same problem, after MIUI 12 my galaxy gear s3 can't connect to the phone, bluetooth is trying to connect but connection failed.
Tried to factory reset phone and watch - nothing helps.
I have the global rom on my mi 10 pro. I was getting the watch not staying connected. I held down the Galaxy Wearable app, hit info, and turned on auto start, and I've been fine since. Oh, I am using Galaxy Active 1 though, not 2.
mixxxk said:
I have the global rom on my mi 10 pro. I was getting the watch not staying connected. I held down the Galaxy Wearable app, hit info, and turned on auto start, and I've been fine since. Oh, I am using Galaxy Active 1 though, not 2.
Click to expand...
Click to collapse
But it doesn't make sense when the bluetooth connection is not even staying conencted, there is not going to help with the app with auto restart. I have still gave it a try which didn't help much.
But Thank you for the input anyways.
i thought its only me but yes i have samsung watch active 2 after miui 12 update i cant connect my phone gives a pincode to connect to the watch but the watch isnt showing any pincode to pair.
xnostra said:
i thought its only me but yes i have samsung watch active 2 after miui 12 update i cant connect my phone gives a pincode to connect to the watch but the watch isnt showing any pincode to pair.
Click to expand...
Click to collapse
Hi, as you said there is no pincode popup, but can you see the device (in this case your active 2) when you open the bluetooth list from the PHONE?
rayraymond said:
Hi, as you said there is no pincode popup, but can you see the device (in this case your active 2) when you open the bluetooth list from the PHONE?
Click to expand...
Click to collapse
yes i can i tried alot of things but i guess miui 12 break the galaxy watch 2 active compatibility it was working perfect at miui 11
I don't have my watch with me, can someone check if disabling MIUI optimization helps with our problem.
https://c.mi.com/oc/thread-3251450-1-0.html?mobile=no
Disabling MIUI optimization SOLVES the issue!!!
Same with on MIUI 12 with Samsung Galaxy Watch - Got it working by putting on Developer Mode and turning off MIMUI optimization - works great but issues with WhatsApp - not reading the contact
vanaxe said:
Same with on MIUI 12 with Samsung Galaxy Watch - Got it working by putting on Developer Mode and turning off MIMUI optimization - works great but issues with WhatsApp - not reading the contact
Click to expand...
Click to collapse
Try clear WhatsApp App data, it will reset permissions and it should work again. You'll just have to backup and restore your whatsapp.
AlexDaizy said:
Try clear WhatsApp App data, it will reset permissions and it should work again. You'll just have to backup and restore your whatsapp.
Click to expand...
Click to collapse
Thank you, looks like it is work so far.
Also do you have a solution for the keyboard - when you reboot - it goes back to the default keyboard and not my preferred. Sugou Keyboard is therefore re-enabled as the default keyboard
Thanks again for your help
Brent
vanaxe said:
Thank you, looks like it is work so far.
Also do you have a solution for the keyboard - when you reboot - it goes back to the default keyboard and not my preferred. Sugou Keyboard is therefore re-enabled as the default keyboard
Thanks again for your help
Brent
Click to expand...
Click to collapse
Uninstall it https://forum.xda-developers.com/xiaomi-mi-10/how-to/guide-debloat-usable-chinese-rom-root-t4066909
Here is the link of apps you can uninstall
vanaxe said:
Same with on MIUI 12 with Samsung Galaxy Watch - Got it working by putting on Developer Mode and turning off MIMUI optimization - works great but issues with WhatsApp - not reading the contact
Click to expand...
Click to collapse
where did you find this option in developer mode, i cant find it. Are you on android 11 or....
marcel112 said:
where did you find this option in developer mode, i cant find it. Are you on android 11 or....
Click to expand...
Click to collapse
It's in developer option unless you are on eu which doesn't have it. I'm not sure about global rom
raven213 said:
It's in developer option unless you are on eu which doesn't have it. I'm not sure about global rom
Click to expand...
Click to collapse
i see thats why i cant find it, i'm on .eu:crying:

Categories

Resources