Related
I just got a One S last week, and everything worked great with my 2009 A3 until yesterday, when bluetooth started getting disconnected by itself literally every minute. After it cuts off it immediately reconnects, which would have been fine but the A3 makes a "ding" sound every time the phone is connected. I have tried to unpair and pair again and again, and to no avail.
Despite this issue, the connection is actually fine when in a call. It's only when it's idle. Also my Nexus S working fine with the car, and the phone works fine with my BT speakers....
Does anyone else have this problem? I'm going to call my local dealership and ask if they have any sort of update for the A3 since the One S is BT 4.0....
[SOLUTION/WORK AROUND]
Just unpair the phone, then when you pair it again, do not allow the car to access your contacts, and make sure to choose the "do not ask again" option. This is the only consistent solution I've seen so far.
Try to update software... Maybe there is the fix. Settings about phone system update
Sent from my HTC VLE_U using Tapatalk 2
I have the same issue with my One S, it will connect and disconnect from my Cadillac SRX, my Galaxy S2 had no issues. What is up with this phone.
Yeah tell me about it....my Lamborghini Aventador is doing the same thing
cuoreesitante said:
I just got a One S last week, and everything worked great with my 2009 A3 until yesterday, when bluetooth started getting disconnected by itself literally every minute. After it cuts off it immediately reconnects, which would have been fine but the A3 makes a "ding" sound every time the phone is connected. I have tried to unpair and pair again and again, and to no avail.
Despite this issue, the connection is actually fine when in a call. It's only when it's idle. Also my Nexus S working fine with the car, and the phone works fine with my BT speakers....
Does anyone else have this problem? I'm going to call my local dealership and ask if they have any sort of update for the A3 since the One S is BT 4.0....
Click to expand...
Click to collapse
That's weird, my 2012 A3 doesn't have this issue. Do you have the nav system or the base console?
cuoreesitante said:
I just got a One S last week, and everything worked great with my 2009 A3 until yesterday, when bluetooth started getting disconnected by itself literally every minute. After it cuts off it immediately reconnects, which would have been fine but the A3 makes a "ding" sound every time the phone is connected. I have tried to unpair and pair again and again, and to no avail.
Despite this issue, the connection is actually fine when in a call. It's only when it's idle. Also my Nexus S working fine with the car, and the phone works fine with my BT speakers....
Does anyone else have this problem? I'm going to call my local dealership and ask if they have any sort of update for the A3 since the One S is BT 4.0....
Click to expand...
Click to collapse
i had the same problem with my arc s and my '11 rs5 last year.the audi guy couldn't find any problem at the multimedia console. he offered me to change the whole console but the problem was still there. same problem on my girlfriends tts...don't know what audi was doing back there.
now on my new facelift rs5 bluetooth works like a charm
Maybe if you didn't have such a badass car your phone wouldn't hyperventilate and drop your bt con every 60 seconds.
I had this issue with SEAT Altea. It was in fact due to contacts syncronization.
To know if it is the case: unpair your phone and pair it again without accepting to share your contacts. then if the connexion is stable you will know that it's linked to sync.
I solved the issue by deactivating some phonebooks sources. I had 140 google contacts and 160 Exchange ones. Probably too many. By activating only the google ones the issue was solved.
hope it helps...
ocswing said:
That's weird, my 2012 A3 doesn't have this issue. Do you have the nav system or the base console?
Click to expand...
Click to collapse
I have a base console.
pierre.grand said:
I had this issue with SEAT Altea. It was in fact due to contacts syncronization.
To know if it is the case: unpair your phone and pair it again without accepting to share your contacts. then if the connexion is stable you will know that it's linked to sync.
I solved the issue by deactivating some phonebooks sources. I had 140 google contacts and 160 Exchange ones. Probably too many. By activating only the google ones the issue was solved.
hope it helps...
Click to expand...
Click to collapse
Yep I saw this on another forum and it worked like a charm. I dont really need to use the phone book anyway, as long as it can let me pick up phone calls im golden.
So, what was the actual change that solved the issues for you? We might want to take this into the FAQ. Did you disable the phonebook sync completely or did you just limit it to Google Contacts?
psych0t1c said:
So, what was the actual change that solved the issues for you? We might want to take this into the FAQ. Did you disable the phonebook sync completely or did you just limit it to Google Contacts?
Click to expand...
Click to collapse
It was the phonebook sync. When you pair the phone to your car you should get a prompt on the phone that the car is asking for permission to access your contacts, just check the "don't ask again" button and decline it.
I also have a problem downloading contacts. I drive 2011 Subaru Outback with OEM Nav/Bluetooth. How do you select which contacts to sync? Where is the option for selecting/deselecting Google, phone...etc?
Thank you
Hi,
when not syncing your contacts is not an option: If you keep your android running with the navigation app (preventing standby) do you still experience disconnects? If this helps you can try my app "BluetoothKeepalive" from the market, it automatically prevents android standby when being connected via bluetooth.
Regards
...Alex
I previously had a Samsung Galaxy S3 that ran Android 4.1.2. Push notifications would come through pretty much instantly.
Now that I have my Nexus 5, I'm noticing that push notificiations are delayed. For example, I might receive an email on my PC saying that someone has posted on my Facebook timeline, but a notification doesn't pop up on my phone for 10-15 minutes later. Sometimes I get no notifications for a while because they're delayed, then the notification sound on my phone will go off 3 or 4 times in a row as a bunch of notifications from different apps have all arrived at once.
Also, sometimes I got no notification at all. For instance, I sold an item on eBay and usually I would get a notification that it has sold. On this particular occasion, no notification appeared. The same has happened with Facebook. Sometimes I will go to Facebook and find that a friend has written on my timeline, yet I didn't receive a notification about it on the phone.
I Googled this issue and found it was a problem that plagued the Nexus 4, so I'm wondering if it also affects the Nexus 5 too. Does anyone else have this issue with the Nexus 5? Is there any fix for it?
I get this too, but not very often. Most of the time I find my phone gets notifications before my PC or other phone does. But there are occasions, particularly when I'm not on WiFi, when I either get delayed notifications, or I won't get them at all, until I reconnect to WiFi.
It's been happening to me, including when I was running totally stock w/ locked bootloader. I'm on Sprint. Not sure if it's a data issue or phone issue.
Turning off wifi optimization solved my delayed corporate email (outlook) notification.
Thanks for the replies.
I'm having this issue while connected to Wi-Fi, although I haven't tested to see if the issue occurs via my mobile network as well. I have tried 2 factory resets, but that didn't fix it.
It's almost like, when the screen is off and the phone sleeps, it loses the ability to receive push notifications, but then after a while it suddenly regains it and that causes a bunch of notifications to arrive at once.
I've contacted Google support about it, so I'll see what they say.
funksoulbrother said:
Thanks for the replies.
I'm having this issue while connected to Wi-Fi, although I haven't tested to see if the issue occurs via my mobile network as well. I have tried 2 factory resets, but that didn't fix it.
It's almost like, when the screen is off and the phone sleeps, it loses the ability to receive push notifications, but then after a while it suddenly regains it and that causes a bunch of notifications to arrive at once.
I've contacted Google support about it, so I'll see what they say.
Click to expand...
Click to collapse
Any update on this? What did they say? I have the same problem and it's driving me crazy.. I came from GS3 and notifications were instantaneous... on this one I have to open lets say Whatsapp every other minute to check if someone sent me a message... and even sometimes I open the app and it takes some time for the internet to "wake up" and finally refresh the app... it sucks... I would return my phone if this can't be fixed easily..
So any update or solution on this would be gratly appreciated. Thanks
fireboypr said:
Any update on this? What did they say? I have the same problem and it's driving me crazy.. I came from GS3 and notifications were instantaneous... on this one I have to open lets say Whatsapp every other minute to check if someone sent me a message... and even sometimes I open the app and it takes some time for the internet to "wake up" and finally refresh the app... it sucks... I would return my phone if this can't be fixed easily..
So any update or solution on this would be gratly appreciated. Thanks
Click to expand...
Click to collapse
Google ended up offering me a replacement phone, but that didn't go too well. The new phone they sent wouldn't connect to my Wi-Fi network, so I contacted them to return it but they told me I had to return my original phone, get another replacement, and only then could I return the second one. Obviously, each time they sent out a phone they were putting holds on my credit card for £xxx so in the end I phoned up and complained. To cut a long story short, I still have the original phone and I haven't decided what to do yet.
jbdan said:
Turning off wifi optimization solved my delayed corporate email (outlook) notification.
Click to expand...
Click to collapse
Interesting, I have just turned this off on mine too to see.
I only get delays when I am connected to my home wifi (2.4 or 5GHz). Maybe it is because I only have a 4mb ADSL connection ...
I will check tonight if that fixes it and/or also try the PNF app.
any update or fix on this yet? this is driving me mad, every time I get a notification on twitter or my email my idol picks it up first and my phone gets it 8-9 minutes later even if I'm using it at that moment, anybody else get the delay even while using the device?
All of a sudden I have started facing this problem since the past few days
Yeah..same here
rahulparekh said:
All of a sudden I have started facing this problem since the past few days
Click to expand...
Click to collapse
I am using Moto g and I think its an issue with KitKat rather than with the hardware or the network. My push notifications are being delayed and that wasnt the case with JB 4.2 on my earlier phones.
Very frustrating
I've not been getting google hangouts messages until 20-30 mins later. sometimes i never get a notification, but if i check hangouts i see a new message. Another times i only get the message on the computer, but never on the phone. if i go and clear the app data new messages show up
My push notifications were coming through very quickly up until 2 weeks ago. I have not changed devices, carriers, or installed any new apps. One day they were coming through fine, now they are delayed by up to 30 minutes. My phone has not installed any OS updates either.
I have factory reset my phone, once restoring from cloud, the other not restoring at all and setting up the phone from scratch. This is really irritating. It does it on mobile networks or wifi.
Moto G is frustrating
It's frustrating.
I searched google without obtaining a solution. Moto G and sometimes I get delayed notifications and not others.
Facebook does not even make the notifications. In Whatsapp I have to open it every 2 minutes to see if someone has written. What not to do. I'm bored with this phone.
No solution or google and motorola solve it. Cursed kitkat!
Anything new? This problem is old and comes from the Nexus 4. I really am very sad about it, not PNF solving this.
I've been pulling my hair out trying to figure this out. It definitely started after i upgraded my s2 to kitkat rom back in december. At first i thought it had to do with the PM sleep modes but none of them make a bit of difference. Ive goggled it to death and this thread is the only one ive found.
Currently im going to try the suggestion on the first page to turn off wifi optimization as my phone only does this on wifi. when i use mobile data everything works as expected
EDIT: WIFI optimization makes no difference
Push Notifications
I have faced this problem on both my S4 and S5 on sprint. I think it has to do with sprint closing open tcp connections prematurely, which causes push notifications to fail.
Running the app Root-Push Notifications Fixer, or Unrooted version has worked for me. The root version seems to be more reliable.
Developer's thread
tempest64 said:
I have faced this problem on both my S4 and S5 on sprint. I think it has to do with sprint closing open tcp connections prematurely, which causes push notifications to fail.
Running the app Root-Push Notifications Fixer, or Unrooted version has worked for me. The root version seems to be more reliable.
Developer's thread
Click to expand...
Click to collapse
Hey man I'm just wondering, does your problem persist on Wi-Fi and mobile data? I have a thread over in i777 thread about this issue. Here http://forum.xda-developers.com/showthread.php?t=2717998
razen_kain said:
Hey man I'm just wondering, does your problem persist on Wi-Fi and mobile data? I have a thread over in i777 thread about this issue. Here http://forum.xda-developers.com/showthread.php?t=2717998
Click to expand...
Click to collapse
I only experienced the problem over sprint's network.
Are you experiencing the following Kernel wakelocks on your phone?
msm_serial_hs_dma
BTLowPower
It hapepns both with an LG G Watch R (5.0.2) and a regular BT headset.
If we take the second device, I do expect a Kernel wakelock while speaking or streaming music. The phone is active any way while performing this task.
What is strange is that even if there is no activity the wakelocks avoid deep sleep.
What is strange is that if I move away from the headset (and the BT icon goes the "non connected" status), the wakelocks are always there.
The effect is that my phone (both on 4.4.4 and 5.0.2) almost never ever sleeps, and sometimes get warm.
If I switch BT off, everything goes back to normal.
Any solution?
I'm rooted, so I can do further tests researches (I'm using BBS to spot the wakelock).
Is it possible that this is an hardware problem? I'm asking as it looks like I'm the only one with this issue!
Thanks.
I can imagine Android Wear as an issue but the Bluetooth headset is mind boggling.... I have a Sony SRS X7 Bluetooth speaker and that never causes this issue as far as I am aware.
abhinav.tella said:
I can imagine Android Wear as an issue but the Bluetooth headset is mind boggling.... I have a Sony SRS X7 Bluetooth speaker and that never causes this issue as far as I am aware.
Click to expand...
Click to collapse
I was pointing to Wear as well.
Then I noticed it just connecting to a BT headset.
Can you please connect to the speaker and play music for a minute or so. Then stop but keep the Z3 connected and report if you notice the wakelocks (provided you are rooted)? 10 minutes will be enough.
Could it be an hardware problem?
Thanks a lot.
Yeah, I checked again as you asked, still have not noticed any impact on battery life. Mind you I am still on KitKAt and I noticed you are on Lollipop. Have you tried restarting? Maybe it's like the old camera big on Nexus Kitkat release where camera app sometimes ran in the background till restarted.
I thought im the only one having this bluetooth issues..
If you are rooted, can you please check if you have the same wakelock as myself? Tx.
Inviato dal mio Nexus 10 utilizzando Tapatalk
abhinav.tella said:
Yeah, I checked again as you asked, still have not noticed any impact on battery life. Mind you I am still on KitKAt and I noticed you are on Lollipop. Have you tried restarting? Maybe it's like the old camera big on Nexus Kitkat release where camera app sometimes ran in the background till restarted.
Click to expand...
Click to collapse
Thanks for it.
Did you check wakelocks via Battery stats? It could be that a direct impact on battery life is not visible.
I did a test pairing my watch with a 5.1 Nexus 10. The wakelocks are there (with a slightly different name) but they are way less intrusive. They wake the phone up only when needed and the counted 4 minutes over a usage of 10 hours.
My conclusion is that the BT implementation on Z3 (regardless 4.4.4 or 5.0.2) is defective, from a wakelocks and battery perspective.
The fact that I'm one of the few noticing it, could also lead to an hw defect.
What's the expert view?
I have the same problem. Took me a while to figure out it is BT. Since turning off BT did not work (turns out it takes a restart of BT). Odd thing is it does not always happen. Over the past few days I have experimented on different apps (Beyondpod, Audible, Kugou), stopping at different situation (from app, stop from device then turn off, turn off device without first stopping), and on different BT devices (Plantronic Backbeat 903, Nissan Leaf, some no-name car kit (amazon.com/dp/B00L1VT5KS). So far I've ruled out the apps and Plantronic. But between the car and car kit I am not certain. Sometime I connects to both and it would have no problem. Some days (e.g. today) BT will keep the phone awake). Am I'm running more or less the same apps.
In all cases, reboot will fix the issue. But I don't always have luck with simply restarting BT.
I'm able to locate a few threads on the topic. looks like it is not limited to Z3. Z1/s and compact suffer from the same
community.o2.co.uk/t5/Android-Devices-Samsung-HTC-Sony/Z1-Compact-doesn-t-go-to-Deep-Sleep/td-p/648801/page/3
talk.sonymobile.com/t5/Xperia-Z1-Z1s/KitKat-757-Bluetooth-draining-the-battery/m-p/652237#U652237
Both referencing this link for the "workaround":
talk.sonymobile.com/t5/Xperia-Z1-Z1s/Z1-KitKat-687-Toyota-Touch-amp-Go-No-Deep-Sleep/m-p/640793#M22841
(I can't post link, so sorry about the non-linked text)
colonelheero said:
I have the same problem. Took me a while to figure out it is BT. Since turning off BT did not work (turns out it takes a restart of BT). Odd thing is it does not always happen. Over the past few days I have experimented on different apps (Beyondpod, Audible, Kugou), stopping at different situation (from app, stop from device then turn off, turn off device without first stopping), and on different BT devices (Plantronic Backbeat 903, Nissan Leaf, some no-name car kit (amazon.com/dp/B00L1VT5KS). So far I've ruled out the apps and Plantronic. But between the car and car kit I am not certain. Sometime I connects to both and it would have no problem. Some days (e.g. today) BT will keep the phone awake). Am I'm running more or less the same apps.
In all cases, reboot will fix the issue. But I don't always have luck with simply restarting BT.
I'm able to locate a few threads on the topic. looks like it is not limited to Z3. Z1/s and compact suffer from the same
community.o2.co.uk/t5/Android-Devices-Samsung-HTC-Sony/Z1-Compact-doesn-t-go-to-Deep-Sleep/td-p/648801/page/3
talk.sonymobile.com/t5/Xperia-Z1-Z1s/KitKat-757-Bluetooth-draining-the-battery/m-p/652237#U652237
Both referencing this link for the "workaround":
talk.sonymobile.com/t5/Xperia-Z1-Z1s/Z1-KitKat-687-Toyota-Touch-amp-Go-No-Deep-Sleep/m-p/640793#M22841
(I can't post link, so sorry about the non-linked text)
Click to expand...
Click to collapse
Thanks a lot for reporting your experience.
The main difference is that if I disconnect the BT device the drain and wakelocks continue, but if I switch BT off they stop.
Then I do not have BT listed in battery stats as a drain.
Here are your links in a click friendly form!
http://talk.sonymobile.com/t5/Xperi...tooth-draining-the-battery/m-p/652237#U652237
http://talk.sonymobile.com/t5/Xperi...-Touch-amp-Go-No-Deep-Sleep/m-p/640793#M22841
Unfortunately the workaround of turning off + wait + on BT is not a usable solution in a scenario where you use a smartwatch, that has to be connected the all day!!
I'm tempted to try an AOSP based rom to see if the problem is HW related or just SW.
I'll keep you posted.
Thanks.
I did a further test, in the below sequence:
- BT ON + connected to a Plantronics headset => wakelock + device always on
- BT ON + disconnected to a Plantronics headset => wakelock + device always on
- BT OFF + disconnected to a Plantronics headset => no wakelock + device sleep
- BT ON + disconnected to a Plantronics headset => wakelock + device always on
This thing is driving me crazy!!!!!
vittogn said:
Are you experiencing the following Kernel wakelocks on your phone?
msm_serial_hs_dma
BTLowPower
It hapepns both with an LG G Watch R (5.0.2) and a regular BT headset.
If we take the second device, I do expect a Kernel wakelock while speaking or streaming music. The phone is active any way while performing this task.
What is strange is that even if there is no activity the wakelocks avoid deep sleep.
What is strange is that if I move away from the headset (and the BT icon goes the "non connected" status), the wakelocks are always there.
The effect is that my phone (both on 4.4.4 and 5.0.2) almost never ever sleeps, and sometimes get warm.
If I switch BT off, everything goes back to normal.
Any solution?
I'm rooted, so I can do further tests researches (I'm using BBS to spot the wakelock).
Is it possible that this is an hardware problem? I'm asking as it looks like I'm the only one with this issue!
Thanks.
Click to expand...
Click to collapse
I've NEVER seen this happen on stock. I've only seen it happen on Sony AOSP, which currently has a broken BT LPM config.
Entropy512 said:
I've NEVER seen this happen on stock. I've only seen it happen on Sony AOSP, which currently has a broken BT LPM config.
Click to expand...
Click to collapse
Hi Andrew, that's great to have @Entropy512 input for what appears to be a very "personal" problem!!
I had some further investigation and discovered that:
In wakelock detector under kernel wakelocks I can notice that:
ipc000000ef_sensors.qcom has the highest number (7387 in 3h).
ipc0000008c_sensors.qcom (649 in 3h).
Under CPU WL I have UID [Type: System (Bluetooth) - bluedroid_timer] is the biggest WL. This looks to be a Lollipop general issue, as I had the same in KK I'm not pretty sure it is related.
In Sony talk forum I got a reply from a moderator: "That item you listed is known to prevent sleep from back in 2012 and to fix you need to decompile and rebuild the item with amended code - However you still could have an app hence why I mentioned the app to check."
It's strange to me to be asked, as a customer, to decompile and rebuild system stuff!!
Any chance there is an app causing my issue? Any suggestion on how I can root cause it?
Is there a chance it is an hw problem?
Thanks a lot.
vittogn said:
This looks to be a Lollipop general issue, as I had the same in KK I'm not pretty sure it is related.
Click to expand...
Click to collapse
By the way, I'm on Sony Store stock Kit Kat 23.0.1.A.5.77.
colonelheero said:
By the way, I'm on Sony Store stock Kit Kat 23.0.1.A.5.77.
Click to expand...
Click to collapse
Hi, my reference to Lollipop was only related to UID [Type: System (Bluetooth) - bluedroid_timer] CPU WakeLock.
All the rest of my findings where exactly the same in KK.
I got to Sony support forum and a very kind Sony guy promised to look after this issue.
I provided some system dump log taken via PC C after recreating the issue.
I'll keep you updated about the progress.
vittogn said:
Hi Andrew, that's great to have @Entropy512 input for what appears to be a very "personal" problem!!
I had some further investigation and discovered that:
In wakelock detector under kernel wakelocks I can notice that:
ipc000000ef_sensors.qcom has the highest number (7387 in 3h).
ipc0000008c_sensors.qcom (649 in 3h).
Under CPU WL I have UID [Type: System (Bluetooth) - bluedroid_timer] is the biggest WL. This looks to be a Lollipop general issue, as I had the same in KK I'm not pretty sure it is related.
In Sony talk forum I got a reply from a moderator: "That item you listed is known to prevent sleep from back in 2012 and to fix you need to decompile and rebuild the item with amended code - However you still could have an app hence why I mentioned the app to check."
It's strange to me to be asked, as a customer, to decompile and rebuild system stuff!!
Any chance there is an app causing my issue? Any suggestion on how I can root cause it?
Is there a chance it is an hw problem?
Thanks a lot.
Click to expand...
Click to collapse
That moderator had no clue... Something that happened on a 2012 device is of no relevance to a device released in late 2014. He's probably talking about the Xperia S which was a totally different device.
I'm not sure what's causing your problem - as I said, I've never seen it on stock, and only saw it on sony AOSP where the current Bluetooth LPM configuration is completely broken. (Planning on pushing patches for that tonight - but sony AOSP is pretty much independent from production builds right now.)
Entropy512 said:
That moderator had no clue... Something that happened on a 2012 device is of no relevance to a device released in late 2014. He's probably talking about the Xperia S which was a totally different device.
I'm not sure what's causing your problem - as I said, I've never seen it on stock, and only saw it on sony AOSP where the current Bluetooth LPM configuration is completely broken. (Planning on pushing patches for that tonight - but sony AOSP is pretty much independent from production builds right now.)
Click to expand...
Click to collapse
Thanks.
Any advice on how to discover if this a system/rom issue or caused by an app? Any system log I can take?
Entropy512 said:
That moderator had no clue... Something that happened on a 2012 device is of no relevance to a device released in late 2014. He's probably talking about the Xperia S which was a totally different device.
I'm not sure what's causing your problem - as I said, I've never seen it on stock, and only saw it on sony AOSP where the current Bluetooth LPM configuration is completely broken. (Planning on pushing patches for that tonight - but sony AOSP is pretty much independent from production builds right now.)
Click to expand...
Click to collapse
Hi Andrew, did Sony fix it in their recent AOSP 5.1?
OT ON: are u working on Omni for the Z3? OT OFF
Here a self explanatory comparison in between two very simalar days.
The first is with a BT device connected (just connected not streaming or talking).
The second (NO BT - ....) is without. The deep sleep attitude is very different!!
I was on KK yes, but the situation with 5.0.2 is exactly the same.
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.
Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!
I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie
MJFox78 said:
I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie
Click to expand...
Click to collapse
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.
nabbed said:
Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!
Click to expand...
Click to collapse
if Google's code is garbage, I suggest you stop using android and start making your own good code!
nabbed said:
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.
Click to expand...
Click to collapse
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all
kewlest22 said:
if Google's code is garbage, I suggest you stop using android and start making your own good code!
Click to expand...
Click to collapse
I had a Pixel XL for over a year. Only kept it for Project FI. Bug ridden POS.
Sold it for half going price just so I could feel clean again.
Even if Samsung *used* to have sluggish Touchwiz in the past, at least it didn't have deal breaking bugs.
Don't even have to make my own code - some XDA roms had fixed this bug, as opposed to Google.
MJFox78 said:
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all
Click to expand...
Click to collapse
I am almost positive that if you had a somewhat similar problem on a Note 8, it's probably Google's fault.
I don't really use the 2 BT phone functionality for more than 30 min on average, but I've never had any problems on Note 7, GS6 or GS9, or even on a Pixel pre 7.0.2 android, when this bug was first introduced.
After 7.0.2, bluetooth stuff just broke everywhere. This bug, constant disconnects and reconnects, for some people music skips, for some doesn't even work, BT UI in Settings just crashing etc.
It's like Google replaced their BT programmer with a monkey at that point, or even a monkey's nephew.
So just because you cannot use 2 Bluetooth devices simultaneously to make phone calls, it's a deal breaker??? Lmao please please please go back to Samsung so we don't have to hear the whining anymore. Good luck with those bootloaders