Database Info

Going out of Bluetooth range and back again?

Ive had my Smartwatch 2 for 3 months and it and my Samsung Galaxy S3 are running up to date software on Smart Connect and Smartwatch 2.
The problem I have is that because of the shape of my house (long and thin) when i'm at home my watch will often lose its bluetooth link with the phone and simply reconnect when I come back in to range. At least it does MOST of the time.
But randomly I get the message "Pairing with device will clear data from previously paired device". It then requires a reset on the watch and unpairing the watch and repairing on the phone.
There seems to be no logic to these "lock-ups". Sometimes I can go in and out of range once and it locks...sometimes I get no lock-ups all day. Sometimes i'm out of range for a few seconds, sometimes minutes. It seems as though something prevents the automatic repairing on some occassions and not others. And sometimes you have no idea the watch has failed to repair because that message sometimes also fails to appear.
Everything else about the watch I like...but this is driving me nuts.
Are there any rules to how the watch handles bluetooth. As nobody else on here seems to have mentioned this maybe its something i'm doing wrong.
Any advice would be appreciated.

ruggs1234 said:
Ive had my Smartwatch 2 for 3 months and it and my Samsung Galaxy S3 are running up to date software on Smart Connect and Smartwatch 2.
The problem I have is that because of the shape of my house (long and thin) when i'm at home my watch will often lose its bluetooth link with the phone and simply reconnect when I come back in to range. At least it does MOST of the time.
But randomly I get the message "Pairing with device will clear data from previously paired device". It then requires a reset on the watch and unpairing the watch and repairing on the phone.
There seems to be no logic to these "lock-ups". Sometimes I can go in and out of range once and it locks...sometimes I get no lock-ups all day. Sometimes i'm out of range for a few seconds, sometimes minutes. It seems as though something prevents the automatic repairing on some occassions and not others. And sometimes you have no idea the watch has failed to repair because that message sometimes also fails to appear.
Everything else about the watch I like...but this is driving me nuts.
Are there any rules to how the watch handles bluetooth. As nobody else on here seems to have mentioned this maybe its something i'm doing wrong.
Any advice would be appreciated.
Click to expand...
Click to collapse
I have the same phone and watch combo and mine connects back up again without any problems. Is your S3 rooted and if so, with which ROM? I am guessing your watch is on the latest firmware.
I am using a 4.1.2 ROM called BoneStock, but will flash one of the new 4.3 ROMs (now leaning towards MOAR TW 4.3).

ruggs1234 said:
Ive had my Smartwatch 2 for 3 months and it and my Samsung Galaxy S3 are running up to date software on Smart Connect and Smartwatch 2.
The problem I have is that because of the shape of my house (long and thin) when i'm at home my watch will often lose its bluetooth link with the phone and simply reconnect when I come back in to range. At least it does MOST of the time.
But randomly I get the message "Pairing with device will clear data from previously paired device". It then requires a reset on the watch and unpairing the watch and repairing on the phone.
There seems to be no logic to these "lock-ups". Sometimes I can go in and out of range once and it locks...sometimes I get no lock-ups all day. Sometimes i'm out of range for a few seconds, sometimes minutes. It seems as though something prevents the automatic repairing on some occassions and not others. And sometimes you have no idea the watch has failed to repair because that message sometimes also fails to appear.
Everything else about the watch I like...but this is driving me nuts.
Are there any rules to how the watch handles bluetooth. As nobody else on here seems to have mentioned this maybe its something i'm doing wrong.
Any advice would be appreciated.
Click to expand...
Click to collapse
I have a different phone, htc one sv on stock Rom and I have never experienced the issue you described. Always reconnects without an issue.
Sent from my HTC One SV using Tapatalk

Thankyou very much for your replies.
I am now more confused as it does seem there is some sort of problem with my set-up between the watch and my Samsung S3.
The firmware on the watch is up to date as is the Smart Connect app and the Smartwatch 2 app.
My S3 is running stock 4.1.2 (and not rooted) and I have no desire to update it with all the problems that might bring.
It doesn't seem as though there are any further settings on the watch I could try adjusting. There doesn't seem to be any further Bluetooth settings on my S3 but I would love to be corrected if i'm wrong.
Any ideas?

I have an S4 and mine has locked up and refused to reconnect again. the first few times i had to reset the watch to get it going again but i figured out how to fix it without having to reset.
if they are refusing to reconnect i just goto my phone and unpair the watch, then do a scan for bluetooth devices and it should find the watch ... pair and everything should be fine. no resets or uninstalls needed.

Danny-B- said:
I have an S4 and mine has locked up and refused to reconnect again. the first few times i had to reset the watch to get it going again but i figured out how to fix it without having to reset.
if they are refusing to reconnect i just goto my phone and unpair the watch, then do a scan for bluetooth devices and it should find the watch ... pair and everything should be fine. no resets or uninstalls needed.
Click to expand...
Click to collapse
Thankyou for the suggestion. This will make the re-pairing process a little simpler and I will try it.
But I am hoping to work out why the phone and watch sometimes lock up when they they should reconnect automatically.

I go out of range often and lose the connection, it then often won't reconnect. I've found the fastest way to get it to reconnect is to turn the Bluetooth off on the watch and then back on again. As long as the smart connect app is running on the phone it will then reconnect, most of the time. This is using an s3 and omnirom.
Sent from my GT-I9300 using Tapatalk

I use a HTC One (4.3) and I´ve never experienced this problem.

Wifi connection troubles after update to 6.0

I'm not sure if this is a Nexus 5 problem or a 6.0 Marshmallow problem but the problem occurred after the update to 6.0 on both Nexus 5s for me and my wife.
There seems to be some bug with my phone while it is asleep (screen is off but phone is on). When it is in this mode, it will not stay connected to wifi. For example, when I enter an area that has wifi, my phone will not connect. It will only connect when I wake the phone. And this isn't just a matter of the phone taking a while to connect. It NEVER connects. Before the update, my phone used to make a connection with my home router before I even walked inside. Now, I can be inside for hours and the phone never connects, until I wake it up. As soon as I wake the phone, the phone makes the connection with no problem. After a few minutes of the phone being asleep, I will wake the phone and the wifi connection will be gone. Now that it is awake again, it connects again with no problem.
I have tried forgetting the network and creating a new one, I have tried different routers, I have tried wiping the cache partition. I haven't tried a full factory reset, and I'd prefer not to, but I guess I will if I have to.
Just thought I would check here first and see if anyone had other thoughts.

Settings - wifi - menu - advanced - Second choice down from the top - choose how to keep WiFi depending on your battery charge %. Regards. Alessandro
Alessandro

vn800art said:
Settings - wifi - menu - advanced - Second choice down from the top - choose how to keep WiFi depending on your battery charge %. Regards. Alessandro
Alessandro
Click to expand...
Click to collapse
Thanks for the reply. Yes, that is what I thought at first also. I meant to say in my original post that my wifi settings are set to "Always On" during sleep. I've tried toggling that between the settings but still have the trouble.

Sorry, my Nex 5 has not this issue on Android 6 build MRA58K.
Alessandro

Yup, have the same issue. When the phone goes to sleep, it seems to disconnects from the wifi and never connects after I wake the phone. When I go into the wifi settings, I see "WIFI Connection Failure". I have to reconnect manually. Like the OP, have it set to always on as well. I also know it's not a router issue because I've tried this on four different routers (two linksys, one Dlink, one TPLink) All same results.
Wonder if this is a phone issue?

Please go here and click on the star to vote for this issue.
https://code.google.com/p/android/issues/detail?id=190667
Google upped this to a high priority Friday morning (Nov 6). The bad news is I think there a couple different WiFi symptoms being discussed here. Most of what is being discussed is the issue being discussed here (not reconnecting when the screen is off).
No idea when this will be fixed, so I build a Tasker profile to toggle WiFi every 15 minutes when not already connected to force a reconnect. I’ve observed it getting disconnected on its own overnight. This should avoid unnecessarily using cellular data.
I’m perpetually waiting for the next release of Android to fix annoying bugs.

vn800art said:
Settings - wifi - menu - advanced - Second choice down from the top - choose how to keep WiFi depending on your battery charge %. Regards. Alessandro
Alessandro
Click to expand...
Click to collapse
GaryP2 said:
Please go here and click on the star to vote for this issue.
https://code.google.com/p/android/issues/detail?id=190667
Google upped this to a high priority Friday morning (Nov 6). The bad news is I think there a couple different WiFi symptoms being discussed here. Most of what is being discussed is the issue being discussed here (not reconnecting when the screen is off).
No idea when this will be fixed, so I build a Tasker profile to toggle WiFi every 15 minutes when not already connected to force a reconnect. I’ve observed it getting disconnected on its own overnight. This should avoid unnecessarily using cellular data.
I’m perpetually waiting for the next release of Android to fix annoying bugs.
Click to expand...
Click to collapse
Thanks for the update Gary. The comment #6 describes my situation exactly. In doing some troubleshooting of my own, I find the disconnection trouble to happen less while on a 5Ghz network vs 2.5. I still have the trouble of it not connecting initially when I come into range, but I find that it is able to hold the connection while asleep.

I am also experiencing this on my Nexus 5 and also found and starred the thread above.
I just listened to 20min of streaming with Spotify to then realize that it had gone into Doze and used the mobile data!
This is more than annoying...
Maybe by disabling Doze for some specific connectivity-related system app? Anyone tried that?

Yes, I moved virtually all of the services type of apps (the ones with the green generic Android icon) to the battery not optimized list. It didn't make any difference for me.
In some ways it seems like it might be a Doze problem, and in other ways it doesn't. Doze shouldn't be affecting anything when the phone is in my pocket and I walk in the house to my WiFi. It also shouldn't be affecting anything when the phone is being charged, which is when I see frequent WiFi disconnects.
It will be real disappointing if this isn't fixed with 6.0.1.

This is still an issue with 6.0.1. Nexus 5 (2013) 6.0.1 MMB29K updated through OTA ZIP pushed with ADB.
Things work properly for a while right after a reboot and then WiFi never connects until the screen is turned on.
Google Connectivity Services C.1.6.7 (2466695) update didn’t make a difference either.

Same problem as the thread starter. HTC A9 anroid 6.0. (newest available OS)

Same problem here with a Nexus 5 .
Please star the problem if you have it.
https://code.google.com/p/android/issues/detail?id=170078

Has anyone tested with a non-stock kernel ?
I'm asking because the problem seems +/- resolved on CM13 (non caf).
No counting CM13, do you know of a more stable rom with the problem resolved?

Does anyone here have Wemo devices? I am reading that wemos, and possibly other devices that emit their own wireless network, may cause problems. I have several of these devices around the house, and wonder if that might be contributing. However, that only would solve the dropped connection bug I have, not the failing to connect while asleep but I have.

Hi mates, my Nexus 5 (android 6.0.1,M8974A-2.0.50.2.29) gets the same troubles with wifi connection but today I tried to put some apps in non optimized list of Doze and seems workig fine.
Thats my non optimized Doze list:
-Google Play Services
-System UI
Try it and let me know if it works properly.

frontomix said:
Hi mates, my Nexus 5 (android 6.0.1,M8974A-2.0.50.2.29) gets the same troubles with wifi connection but today I tried to put some apps in non optimized list of Doze and seems workig fine.
Thats my non optimized Doze list:
-Google Play Services
-System UI
Try it and let me know if it works properly.
Click to expand...
Click to collapse
I had Google Play Services already set to not optimize, but hadn't tried System UI. I will try that out and see what happens.

whitenack said:
I had Google Play Services already set to not optimize, but hadn't tried System UI. I will try that out and see what happens.
Click to expand...
Click to collapse
Welp, that didn't work. Still have the error after not optimizing System UI in addition to Google Play Services.

I don't know if the issue is resolved, but at least for me, it never worked fine so many days after testing some new workaround.
So, this was what I did in my Nexus 5 (latest build, MOB30H).
Uninstall or deactivate Google Connectivity Services, reset your network settings (you will lose your Wifi networks and BT pairings), reboot.
My Nexus 5 has been connecting to the wifi networks even with the screen off for the last 6 days.

Miguun said:
I don't know if the issue is resolved, but at least for me, it never worked fine so many days after testing some new workaround.
So, this was what I did in my Nexus 5 (latest build, MOB30H).
Uninstall or deactivate Google Connectivity Services, reset your network settings (you will lose your Wifi networks and BT pairings), reboot.
My Nexus 5 has been connecting to the wifi networks even with the screen off for the last 6 days.
Click to expand...
Click to collapse
Miguun, has the error returned, or still fixed? I just got the May update, so fingers crossed that fixes it. Otherwise, I guess I'll try your fix. I don't look forward to entering the wifi network information again.

Yup, it is still working !!

[Q] wifi switches on and off

Hi,
since yesterday I have problem with wifi in my S7 (SM-G930F). It keeps turning on and off every second or two. I cannot switch it off because it keeps switching. I have rebooted my device, but it didn't help me. My phone is not rooted, it has stock 6.0.1 firmware. How to fix it? Despite it's impossible to use wifi now, it keeps draining my battery.
edit:
logs attached here: logs

duchian said:
Hi,
since yesterday I have problem with wifi in my S7 (SM-G930F). It keeps turning on and off every second or two. I cannot switch it off because it keeps switching. I have rebooted my device, but it didn't help me. My phone is not rooted, it has stock 6.0.1 firmware. How to fix it? Despite it's impossible to use wifi now, it keeps draining my battery.
edit:
logs attached here: logs
Click to expand...
Click to collapse
Boot to recovery and clear caches, reboot and see how it is then

done. Sadly, it didn't help me.
edit: I've just used this app but it also failed. If nothing help me I will wait till Monday to show it to my coleagues from Customer Support. Maybe they will find solution

duchian said:
done. Sadly, it didn't help me.
edit: I've just used this app but it also failed. If nothing help me I will wait till Monday to show it to my coleagues from Customer Support. Maybe they will find solution
Click to expand...
Click to collapse
I'd backup with smart switch, and factory reset the phone
Or flash the latest stock ROM over the top with ODIN

*Detection* said:
I'd backup with smart switch, and factory reset the phone
Or flash the latest stock ROM over the top with ODIN
Click to expand...
Click to collapse
I think it may be related with some strange wifi:
11-11 11:20:11.682 3462 3896 I WifiConfigStore: " Social WiFi" is a captive portal!
11-11 11:20:11.682 3462 3896 I WifiConfigStore: not authenticated yet
11-11 11:20:11.682 3462 3896 I WifiConfigStore: login url: "https://accounts.google.com/ServiceLogin?passive=1209600&continue=https://accounts.google.com/o/oauth2/auth?scope%3Dopenid%2Bemail%2Bprofile%26response_type%3Dcode%26state%3Dp6Vwdj6Gibz9wS9yez6dSfomZT3WiPZC%26redirect_uri%3Dhttps://socialwifi.com/social-auth/complete/google-oauth2/%26client_id%3D240279395513.apps.googleusercontent.com%26from_login%3D1%26as%3D-1601b637b91f0d80&oauth=1&sarp=1&scc=1#identifier"
Click to expand...
Click to collapse
I saw it yesterday at work, but not authenticated. Now it is remembered in list. Sadly S7 has no option to forget networks out of range. Todays we have national holidays, but on Monday I will be at work and try to forget this network. I do not want to change rom because rom from my operator has wifi calling enabled and it is awesome.

Is there any chance that WiFi scanning is turned on? I recently saw that WiFi scanning will briefly turn my WiFi on then off repeatedly (shows with an indicator on top and I hadn't noticed that before). This first showed up when I installed Android Auto since it turned on my WiFi scanning option by default. As soon as I turned WiFi scanning off, the WiFi worked as it had before. It may be worth a look.

I've run into the same issue. Started yesterday, which may have come with the latest PJG update... Not sure.
But it's rendered my phone pretty much useless. The constant toast message popping up, saying "Network connectivity is available" gets in the way of the keyboard and I can't type a damn thing!
Like you, I've found it's stuck with reboots and a factory reset, which makes me think it could be the firmware or modem.
Edit: Disabling WiFi Scanning stopped the errors. Root cause is still unknown, though. I've never had to disable that before...

crizyal said:
Is there any chance that WiFi scanning is turned on? I recently saw that WiFi scanning will briefly turn my WiFi on then off repeatedly (shows with an indicator on top and I hadn't noticed that before). This first showed up when I installed Android Auto since it turned on my WiFi scanning option by default. As soon as I turned WiFi scanning off, the WiFi worked as it had before. It may be worth a look.
Click to expand...
Click to collapse
Yep. It was turned on, but I have it enabled since I bought this phone. Turning off neutralized my problem, but why it was broken for last few days when I haven't done anything with my phone? I rely on this feature because of localization accuracy and disabling it is just temporary fix.
edit:
Guys, one more thing:
do you have "Samsung Gear" app installed? I think this app is forcing to enable and disable wifi. Under localization it shows battery usage as high and it was updated last week

duchian said:
Guys, one more thing:
do you have "Samsung Gear" app installed? I think this app is forcing to enable and disable wifi. Under localization it shows battery usage as high and it was updated last week
Click to expand...
Click to collapse
My phone does not have the Samsung Gear app installed. I do use Samsung Pay regularly and that was also updated (engine and app). I don't know how that would relate to WiFi though.

jimmy-bish said:
I've run into the same issue. Started yesterday, which may have come with the latest PJG update... Not sure.
But it's rendered my phone pretty much useless. The constant toast message popping up, saying "Network connectivity is available" gets in the way of the keyboard and I can't type a damn thing!
Like you, I've found it's stuck with reboots and a factory reset, which makes me think it could be the firmware or modem.
Edit: Disabling WiFi Scanning stopped the errors. Root cause is still unknown, though. I've never had to disable that before...
Click to expand...
Click to collapse
Turning off WiFi scanning stops the constant switching of WiFi. I tried removing the system settings permission from all the apps that had it (even the Google app) but it doesn't seem to have any effect.

I am seeing the same issue, I did not touch my screen in the following video
Video on Dropbox
disabling "Wi-Fi scanning" in location helps.

Hi,
I had the same issue before.
What I did was(Not sure how its displayed in english):
-Settings;
-Backup and Reset
-Reset network settings
I was having constant disconnections from wifi and it solved it.
Give it a try

DiogoCDS said:
Hi,
I had the same issue before.
What I did was(Not sure how its displayed in english):
-Settings;
-Backup and Reset
-Reset network settings
I was having constant disconnections from wifi and it solved it.
Give it a try
Click to expand...
Click to collapse
Did the above solve the problem?

I am using G930F in US on ATT and encountered the same problem in past few days, where wifi kept turning on and off. Was searching this post, and found out that if i turn off wifi scanning i can get wifi to stay off (when i switched off ) and wifi on (when switched to on) and not flip back and forth.
go to settings.
- click on search
- type in improve accuracy
- select from choice
- turn off wifi scanning
Try that and hope that helps.

I have the same problem. The side effect is that it will drain the battery really fast.
As others have mentioned, after I have turned off the WiFi scanning in the location setting the problem is temporarily gone. However it should not be the solution as I really need the WiFi location to work. I don't know what is causing the bug.
P. S. I only see this problem starting from the last week or so. I leave the WiFi scanning location function on since I have bought the phone in May. Mine is Exynos version.

several Samsung devices have this issue.
I and several others have it on a note 4, and some people have also reported having this problem on S6 variants.

The problem is Google Play Services 10.0.84 version. Another cell phones with this version of Google Play Services have the same problem (ej. Google Pixel phone) but not all.

The problem is the Android Wear App. Deinstall the app and wifi works perfekt.
This issue starts with the last update of the wear app.
Hope i could help you.

Gerry65 said:
The problem is the Android Wear App. Deinstall the app and wifi works perfekt.
This issue starts with the last update of the wear app.
Hope i could help you.
Click to expand...
Click to collapse
I tried uninstalling Android Wear but it didn't make a difference. The wifi kept switching on and off.

As mentioned above, it's Google Play Services 10.0.84. Just disable wifi scanning until there is an update. Hopefully google won't take too long to push a fix.

Bluetooth Disconnects and Reconnects Randomly dozens of times a day

My Gear S2 has recently started disconnecting, then reconnecting a few seconds later. The S2 and my phone both vibrate - when I check my mssages, nothing new but the phone says disconnected. I have a stock (non-rooted) Verizon S7 Edge.
Here's what I've done so far:
1. Powered both off and back on - didn't work
2. Reset the watch and app - didn't help
3. Disconnected the watch from my phone and connected it to my son's S7 (verizon) - HAD NO DISCONNECTS
4. Did a factory reset on both the phone and the watch and reinstalled to my S7 edge....disconnects resumed.
My next logical assumption would be since it happens on mine but not his phone, it must be my phone. But it never disconnects from my Ford Sync or my BT radio.
Anyone had this issue - or better yet, figured out this issue?

No one else has this issue?

I am in the Nougat beta for s7 and have had this happen frequently. They have said to wait for the final update and see if it's fixed then. It did not happen as often to me as you are describing

Same here, but I suspect more my S7E to be the issue since it happened also with my Pebble Time.

(also posted in another thread on disconnects) After working with three different S7's (2 edge's and one regular) as well as a Droid Maxx, I found that the phones would regularly disconnect when I had High Accuracy GPS set to on (with disconnects occurring multiple times per hour). If I switched the phones to power-saving GPS, disconnects would never occur.
Not sure why this would be but I don't recall it happening before the latest S2 update. I have always used High Accuracy GPS because I use the Tile app which requires it....HOWEVER, the disconnects were SO irritating, I guess I'd rather lose my keys and/or wallet because I turned the GPS to power saving to eliminate the disconnects because it was SOOOOO annoying.

Anyone else have crippling BT disconnect issues?

Hey guys, I'm currently in possession of two Gear S3 watches (one European and one U.S.) and two different phones (GS7 and Pixel, both 5 in versions). I am having a horrendous time trying to get a stable connection between my watch and the phones via bluetooth. I basically can't use the watch because of how frequently it disconnects from my phone.
On my GS7, the watch would not hold a BT connection long enough out of the box to be set up properly for about an hour. It would always disconnect during setup and kick me back to the beginning. Ultimately I lucked out and managed to get it to set up after trying over and over by resetting, clearing data/cache, reinstalling app, etc. Used it for the last week or so and I definitely had a number of random BT disconnects but overall it seemed to get the job done without being too much of a distraction.
Now I have a pixel I'm trying to set up with and it's been a nightmare. I just can't get the watch to connect long enough to the pixel software to actually get going. The same message always pops up about the connection failing. "Please try again." When I look at the watch, I notice that the watch's BT radio is actually what appears to be fluctuating. It will frequently turn itself on and off in a matter of seconds. After enough connects/disconnects, the watch remains in standalone mode and manually toggling BT will not enable it anymore. A reset temporarily solves the toggle issue but not the frequent disconnect issue. I've disabled battery optimizations on the Samsung software and plugins but again the watch seems to be the bigger culprit. I can still pair to my GS7 albeit now with more frequent disconnects though not as bad as the pixel. I've tried factory resetting a bazillion times and also re flashed the software images through net odin from these forums. Nothing seems to solve this issue.
The European model was having similar quality connection with my pixel but I haven't tried it with the S7 yet. Is anyone else having these major BT issues with this watch or did I just get a few stinkers? Thanks!

I've had my watch about a month now and I've had zero Bluetooth problems.
Sent from my SM-T530NU using Tapatalk

zero.... mate 9

Guess it's time for an exchange then. Thanks!

A Friend of mine had the same issue. It seems hardware related. He exchanged it for a new one. Problem solved.
Verstuurd vanaf mijn SM-G930F met Tapatalk

Sounds like a problem with your watch. Are your phones rooted or modded in any ways? My friend was having that issue and realized it's because he was closing the Gear app instead of leaving it open in the background (non Samsung phone)...

I have a similar problem but is the phone's fault. When too many apps are open, the bluetooth disconnects and then reconnects (resets?). My device has only 2Gb of RAM, I think it's closing apps to free up memory because when I'm not using the device it never disconnects, but as soon as I'm playing a game or using a Navigation app, it disconnects randomly.
Check if this is your case. How many apps have you installed/running in the background? I've disabled a lot of apps that start on boot.
Also when pairing it for the first time I couldn't do it on a certain custom ROM (LG phone). Looking at the logcat it was due to some missing libraries. After changing the ROM it paired successfully.