Related
Since the update, my SW2 seems to be incapable of playing nicely with any other Bluetooth-enabled devices. If I am in an area where it is just my phone (LG G2 running KK) and the watch, everything works just fine. But if my phone connects to something else via BT, for example my car stereo or BT headphones), the watch will immediately disconnect and the only way to reestablish a connection is to power cycle the watch.
I'm trying to determine if this is a problem with the firmware update or simply a matter of a problem between phone's BT firmware and the watch. Anyone else have the same issue?
I don't face this problem. I've used 2 BT headphones models without any issue.
Sent from my SM-N9005 using Tapatalk
Before the update I had zero connection problems. After the update my SW2 constantly disconnects and sometimes reconnects, other times I have reconnect by going through smart connect and un-pairing/re-pairing to power cycle the watch. I have tried disabling apps and even removing all apps and resetting all to no avail. This is extremely frustrating because my fancy new expensive piece of tech is 99% useless . Also I have ZERO bluetooth devices on in the area besides the SW2.
Any help would be greatly appreciated. Is there a way to flash and/or format the SW2? I tried SUS(sony update service) which USED to have the SW2 in it with a repair option but they have since removed the SW2 in the latest version 2.14.6.2014170858.
help
Pirate_Freder said:
Before the update I had zero connection problems. After the update my SW2 constantly disconnects and sometimes reconnects, other times I have reconnect by going through smart connect and un-pairing/re-pairing to power cycle the watch. I have tried disabling apps and even removing all apps and resetting all to no avail. This is extremely frustrating because my fancy new expensive piece of tech is 99% useless . Also I have ZERO bluetooth devices on in the area besides the SW2.
Any help would be greatly appreciated. Is there a way to flash and/or format the SW2? I tried SUS(sony update service) which USED to have the SW2 in it with a repair option but they have since removed the SW2 in the latest version 2.14.6.2014170858.
Click to expand...
Click to collapse
helo
I have the same problem with my new sw2 firm: 1.0.B.4.154 and my sgs4 standard ROM .If You find some solutions for this problem please wright how make this.
Question: does any of you guys use the 'watchwidgets' app?
I had disconnection problems too only while using the clock widgets from this app.
As soon as I removed it all went back to normal.
I'd strongly suggest a connectivity test without the use of any 3rd party screen candy, at least for a day, maybe it'll help you find the culprit.
Sent from my Xperia V using Tapatalk
vrl13 said:
Question: does any of you guys use the 'watchwidgets' app?
I had disconnection problems too only while using the clock widgets from this app.
As soon as I removed it all went back to normal.
I'd strongly suggest a connectivity test without the use of any 3rd party screen candy, at least for a day, maybe it'll help you find the culprit.
Sent from my Xperia V using Tapatalk
Click to expand...
Click to collapse
I think the problem is on te watch because i try for four different phone with only 1 aplication for smw2 is smart watch connection
i think about loading Rom for watch but i don't now how.
It sounds like a watch problem indeed... can't you go to Sony with it? If you're still under warranty maybe they'll change it...
As for a watch ROM...there isn't any, as far as I am aware.
Sent from my Xperia V using Tapatalk
Same issues here. Mix of roms. With some roms all seams fine for a while. It always ends up with disconnects. I'm trying to find a reason. Mix of software and hardware. Coudl you post the HW version of your SW?
I have the same problem after update ... GT I8530
I have the same problem after update ... GT I8530
Hi,
I have a strange issue that only seems to affect my Gear 2 - everything else on Lollipop seems OK.
I am running the leaked stock ROM N9005XXUGBNL8 - rooted. I have also loaded the latest Gear Manager - 2.2.14112899.
When I turn on the watch or Phone, the devices connect correctly, and everything seems to work well. My problem is when I move out of range. The watch shows that the Bluetooth disconnects, but the phone still thinks that it is connected. When i move back into range, the phone and watch remain disconnected unless I manually reconnect by turning the phones Bluetooth off and then on again.
I have reloaded both the phone and watch, but still have the same issue. Sine the Lollipop ROM has not yet been formally released, I cannot ask Samsung for help, so if anyone can suggest a solution, I would be very grateful.
Thanks in advance, Richard
Hello,
I have the same problem with note 3 lollipop and gear 2.
I hope there will be a fix when lollipop arrives officially.
Best regards
Sent from my SM-N9005 using XDA Free mobile app
Blainstorm said:
Hello,
I have the same problem with note 3 lollipop and gear 2.
I hope there will be a fix when lollipop arrives officially.
Best regards
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the reply - at least I am not alone in this and that I am not imagining he issue
I also similar issue. Sometimes it reconnects automatically and other times I should manually reconnect from the Gear Manager.
Lets wait for the final Lollipop release
I am also facing the same problem. I reloaded the gear application twice and also flashed the ROM again after factory resetting the Note 3 but no change. Hope will get the solution soon.
Facing similar problem. After latest update of Note4 (still 4.4.4) watches not reconnect and bluetooth switches off. To manually reconnect i need to press "connect" in watches AND in gear manager. If i just turn on bluetooth watches connects and instantly disconnects turning bluetooth off.
The Gear Manager today updated to 2.2.15011799.
I do not know if this has improved matters yet, but will post if it does.
Update,
Seems to disconnect OK, but will not reconnect automatically. I don't know what is wrong with Samsung, but this really hampers the use of the watch.
After the update today, it works perfectly now!
It seems, the gear manager was the bad guy!
Best regards
Sent from my SM-N9005 using XDA Free mobile app
Still does not really work for me. I need to toggle bluetooth on the phone after a disconnect, but not every time.
Next day the same problems. But the gear is now faster connecting and transferring data. Before the update the gear taken 20 or 30 seconds to sync the calendar app. Now it's open Instantly.
Sent from my SM-N9005 using XDA Free mobile app
RDHoworth said:
Still does not really work for me. I need to toggle bluetooth on the phone after a disconnect, but not every time.
Click to expand...
Click to collapse
Had the same problem as well but downloaded "bluetooth auto connect" from the Play Store https://play.google.com/store/apps/details?id=org.myklos.btautoconnect&hl=en and this seems to have resolved the bluetooth connectvity problem. My gear 2 connects everytime.
Good luck
---------- Post added at 04:05 PM ---------- Previous post was at 03:59 PM ----------
I recently updated Gear Manager on my Note 3 running the leaked Lollipop 5.0. ALthough my gear 2 and manager works I have noticied that the Gear (watch) Icon which normally appears on the top left of the screen is no longer there. The gear notification messgae is still there. Anybody with a similiar issue?
Same here.
Also tried the Bluetooth auto connect, but this does not seem to work. Can you share the settings you used?
Thanks
Sent from my iPad using Tapatalk
I have noticed some more detail:
When i go out of range, the watch disconnect but often, the phone still seems to think the watch is connected. However, when I check the phones bluetooth setting, the watch is connected, but the Phone Audio is disabled. Occasionally, only a reboot will cure this.
I have also spotted several other issues relating to Bluetooth and Lollipop on the XDA forums, such as intermittent connection to Car phone systems, which I have also noticed. I am beginning to suspect that the main problem here is with the Lollipop bluetooth rather than specifically with the Gear. The ensd result is the same - a system that does not work correctly that should be supported and fixed by Samsung.
I have just upgraded the room to the Polish ROM released yesterday and carried out a factory reset.
I still have the same issues. It seems fairly clear that the phone does not recognise that the phone goes out of range and so status connected.
Given Up
I have given up and reverted to the Stock KitKat ROM. Guess what? everything now works.
I don't think that Android 5 is ready yet - will now wait for 5.1
Search for S6 apps (it is on in xda-developers forum as well). There is a version of the Gear Manager that solves the reconnect issue. I tested it shortly and it works on official lollipop for Note3.
EDIT: After some reboots, recconects are not working properly again.
Any news on how to solve this guys? Same problem here...
Enviado de meu SM-N910F usando Tapatalk
Hello every body,
I've the same problem with my N9005 under Lollipop.
Problem with bluetooth reconnection of my Gear S.
And for me I've another problem, my phone reboot several time per day, maybe due of this problem.
Do you face this problem too?
Hi!
This is the problem with me too! Not reconnecting. Do you have any solutions?
Hey guys,
2 days ago I updated my German z5 due pcc to Android 6.0. Since that I'm facing issues with my smartwatch. Directly after the update, I didn't get any connection to my watch again. I tried do reset the watch and installed android wear app new. Luckily the first connection is always possible, but after first setup I´m not able to connect again. Does anyone has another hint, then reset my z5 like the support of Sony did? I don´t have the feeling, that a reset would, because it is obviously a Bluetooth issue. Thanks for any help and see the screenshot attached. The screenshot shows, how android wear is always stopping when trying to get a connection.
Update:
Yesterday something strange happened. I settled my watch the whole day in it's loading station and in the evening I saw, that my watch was muted like my phone was. When I opened up android wear, I saw my watch was connected, also every app was synced. So I started to install some new wear app and the all get synced. But when I pulled up my watch from the loading station, the connection immediately got lost and until now, I'm not able to connect again. Now I'm pretty sure it is an Bluetooth bug, coming with the android 6.0 update of my z5.
z0rn said:
Update:
Yesterday something strange happened. I settled my watch the whole day in it's loading station and in the evening I saw, that my watch was muted like my phone was. When I opened up android wear, I saw my watch was connected, also every app was synced. So I started to install some new wear app and the all get synced. But when I pulled up my watch from the loading station, the connection immediately got lost and until now, I'm not able to connect again. Now I'm pretty sure it is an Bluetooth bug, coming with the android 6.0 update of my z5.
Click to expand...
Click to collapse
Completely remove the device, then re-add it and set as trusted device
danw_oz said:
Completely remove the device, then re-add it and set as trusted device
Click to expand...
Click to collapse
No changes. Sometimes it randomly connects and sometimes it is loosing the connection. :/
z0rn said:
No changes. Sometimes it randomly connects and sometimes it is loosing the connection. :/
Click to expand...
Click to collapse
So I have been reading about and there are loads of bluetooth issues with Marshmallow even with googles own Nexus devices I know it's not going to help you... http://ausdroid.net/2015/11/17/google-working-fix-nexus-6p-bluetooth-issues/ so I think google need to understand what the problem is a provide a fix for the other manufacturers to include.
My best guess is bluetooth is not behaving nicely in the new google ART cache which is supposed to fully replace delvik in Marshmallow.
Hi All,
Im using my gear S2 with a Samsung galaxy A3 phone. I seem to be having a lot of issues with the watch reverting back to standalone mode and not connecting over BT. Anyone experiencing similar issues? I've tried all the usual things - restarting both devices, toggling BT etc. Every once in a while it syncs properly via BT but then drops out again within a day or two.
I had a search through the forums but couldn't find note of a similar issue. I'd be pretty happy with the watch if I could sort this issue out. Any help would be appreciated. cheers
Brett
Hey all, this issue still happens. Occasionally restarting my phone works to resolve the issue. Another quirk is that smart lock still keeps working even though the watch is apparently in standalone mode...When I use the gear app it says the watch is disconnected and then fails on attempt to reconnect.
So now I have to restart my phone every day to keep the two synced when it drops out.
Any ideas, perhaps there is a secondary app I could use to do an auto restart on the BT or the like?
Similar issue as well.
Mine is a bit different. Any time I go outside of BT range, and come by my Gear S2 doesn't automatically reconnect. It will stay in remote mode until I manually go into the Gear App, disconnect and then reconnect.
Same thing happens if I do it again as well.
I suspect something is going on with the re-activation lock feature. I did not have this issue prior to setting it up. I do need to do a bit more investigating before I point out the cause.
Chiming in that I'm experiencing similar issues after the most recent software update running version R730VVRU1BPC1. I have it paired with a Galaxy S7 and there does not seem to be any rhyme or reason to when it drops. I just get a little vibration notification.
Same issue after last update on Note4.
Same issue aflter last update for S2 - Classic
So i hoped the update for the watch my change anything... it doesn't... by Bluetooth from phone is either turning off or disconnects from watch like every 5 minutes
Sent from my SM-N910F using Tapatalk
Diaconescu_Tiberiu said:
Same issue after last update on Note4.
Same issue aflter last update for S2 - Classic
So i hoped the update for the watch my change anything... it doesn't... by Bluetooth from phone is either turning off or disconnects from watch like every 5 minutes
Sent from my SM-N910F using Tapatalk
Click to expand...
Click to collapse
I have the exact same problem : Bluetooth turns off by itself every 5 minutes
Envoyé de mon LG-H850 en utilisant Tapatalk
I had the same issue. I dont use my watch extensively away from my phone but around te house it will get out of BT range and go into remote mode. once i return to near the phone, it wont reconnect to BT.
I solved this on the watch. Under settings-connections-mobile networks i set it to automatic.
this seems to have solved the reconnect to bluetooth issue. im not sure about how all the functionality works when away from the phone but it seems something you might want to experiment with.
Is anybody having issues with Gear S3 classic disconnecting very frequently? Any fix for this? I'm using Galaxy S4 GOC1 (5.0.1) ROOTED Verizon.
Mine has never disconnected from my Moto G4. You say you're rooted, are you still using the stock rom?
Sent from my SM-T530NU using Tapatalk
eddyo1993 said:
Is anybody having issues with Gear S3 classic disconnecting very frequently? Any fix for this? I'm using Galaxy S4 GOC1 (5.0.1) ROOTED Verizon.
Click to expand...
Click to collapse
Same for me with Gear S2 on my Galaxy S4 Android 5.0.1 rooted not frequently but happen too often for me
Seem bad/old BT on S4 ?
Most of time the S2 do not reconnect automatically. I'm trying workaround to reconnect auto..... (trigger app)
Tel864 said:
Mine has never disconnected from my Moto G4. You say you're rooted, are you still using the stock rom?
Sent from my SM-T530NU using Tapatalk
Click to expand...
Click to collapse
Yes I am currently running the stock rom. Its modified a little bit to keep the KK bootloader from updating to LP's bootloader
dersie said:
Same for me with Gear S2 on my Galaxy S4 Android 5.0.1 rooted not frequently but happen too often for me
Seem bad/old BT on S4 ?
Most of time the S2 do not reconnect automatically. I'm trying workaround to reconnect auto..... (trigger app)
Click to expand...
Click to collapse
Maybe, there is time that it doesn't disconnect at all for awhile then randomly starts doing it and continues right after the other .
My workaround with "Trigger" app works fine. Each time the watch is disconnected my script reconnect the watch after 3min disconnected. Worked every time this last days.
dersie said:
My workaround with "Trigger" app works fine. Each time the watch is disconnected my script reconnect the watch after 3min disconnected. Worked every time this last days.
Click to expand...
Click to collapse
Hi, can you please walk me through which settings you set up for this matter.
Also are you running pro version? Thanks
I not use the pro version.
You can select a trigger -> bluetooth and select wich device supervice for disconnect, so select the Gear in the list.
Then you can select action after this disconnection -> so for example : wait 10s or 3 min , turn off BT, wait 10s, kill Gear Manager, turn ON BT, select connect the Gear device, launch the Gear Manager.
Can confirm, Trigger is the answer
I used the Trigger suggestion posted above and have experienced zero issues since setting that up. The free version works fine for this so no need to get the pro subscription.
KILLDOGG said:
I used the Trigger suggestion posted above and have experienced zero issues since setting that up. The free version works fine for this so no need to get the pro subscription.
Click to expand...
Click to collapse
I can't wait to give this a shot. My Gear Frontier disconnects from my Galaxy S8 almost every time I use AndroidAuto (odd since that's USB), and i have to go back to the Gear app and press Connect to get it connected again. It must have 4 times a day, nearly every time I'm in my car. It's frustrating.
I suspect it's because Android Auto uses bluetooth for call audio or such, and I tried removing the bluetooth connection to my car, but Android Auto sets it up again every time you use it. And that seems to be the issue: Auto connects to the phone advertising the same capabilities (call audio) and so the phone drops the watch connection off. I'm not positive on the cause, but I'm positive that I'm tired of this experience.
skeene85 said:
I can't wait to give this a shot. My Gear Frontier disconnects from my Galaxy S8 almost every time I use AndroidAuto (odd since that's USB), and i have to go back to the Gear app and press Connect to get it connected again. It must have 4 times a day, nearly every time I'm in my car. It's frustrating.
I suspect it's because Android Auto uses bluetooth for call audio or such, and I tried removing the bluetooth connection to my car, but Android Auto sets it up again every time you use it. And that seems to be the issue: Auto connects to the phone advertising the same capabilities (call audio) and so the phone drops the watch connection off. I'm not positive on the cause, but I'm positive that I'm tired of this experience.
Click to expand...
Click to collapse
My Gear 3 disconnects when Android Auto connects as well. I have a Samsung S8+ which was just updated to Oreo. I am going to try the trigger app.
I buy samsung products from retail upgrades and over stocks. I got some classics and some frontiers. The watches are on the older firmware. I kept one for myself. After a few days of everything working great, including the battery, I decided to update the watch which is 2 days ago. Since then, my watch keeps disconnecting constantly, and the range is much shorter