Database Info

Connection Problems After Update

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

PSA: Android Auto and GS8 don't play nice together - causes UI slowdown

So there seems to be some type of weird bug with Android Auto and the GS8. Everything works perfectly fine but basically after 1-2 uses of Android Auto I always notice the UI will start stuttering and slowing down like crazy. At first I thought it was the launcher but it happens when you pull down notification shade and the multitasking view as well which is OS level. I also noticed that changing resolutions (FHD to WQHD or vice versa) would "fix" the issue until it happened again. Doing this resolution switch I believe kills all processes and clears memory/VRAM.etc.
So anyway, after days of trying to find the culprit I uninstalled Android Auto and did a reboot. Been over 24 hours now and phone is still as smooth as after a clean restart - I've used Maps to navigate and all the usual stuff I do in 24 hours without using Android Auto and it's still perfectly fine.
I really am upset with this because I loved using Android Auto - it worked perfectly. I'm going to wait a bit and see if they update either Android Auto and/or after the next GS8 software update. I doubt it's anything to do with Android Auto and more to do with whatever changes Samsung made to Nougat on GS8. Oh well.

mobilehavoc said:
So there seems to be some type of weird bug with Android Auto and the GS8. Everything works perfectly fine but basically after 1-2 uses of Android Auto I always notice the UI will start stuttering and slowing down like crazy. At first I thought it was the launcher but it happens when you pull down notification shade and the multitasking view as well which is OS level. I also noticed that changing resolutions (FHD to WQHD or vice versa) would "fix" the issue until it happened again. Doing this resolution switch I believe kills all processes and clears memory/VRAM.etc.
So anyway, after days of trying to find the culprit I uninstalled Android Auto and did a reboot. Been over 24 hours now and phone is still as smooth as after a clean restart - I've used Maps to navigate and all the usual stuff I do in 24 hours without using Android Auto and it's still perfectly fine.
I really am upset with this because I loved using Android Auto - it worked perfectly. I'm going to wait a bit and see if they update either Android Auto and/or after the next GS8 software update. I doubt it's anything to do with Android Auto and more to do with whatever changes Samsung made to Nougat on GS8. Oh well.
Click to expand...
Click to collapse
Works fine and connects faster to my car than s7 edge.
Sent from my SM-G950U using Tapatalk

What receiver are you using? I'm shopping for one and I have it in mind but I know the stereo companies don't really make firmware a big priority. Android Auto isn't a deal breaker, but it'd be good to know.

I have 0 issue with mine

I also have no issue with android auto, and I use it every day.

Yeah I had the weird UI slowdown 2 days after uninstalling Android Auto. I'm getting irritated now.

patthe said:
I have 0 issue with mine
Click to expand...
Click to collapse
^^^^^
This.
Did you use SmartSwitch or another automated method to restore your phone? Android Auto doesn't like to be moved vs. installed and all the apps available for use in AA have to be installed after AA and not before. Try uninstalling AA and all the apps accessible to it and then reinstall starting with AA.

I'm having weird issue not able to connect my S8+. I don't see android auto on stock unit. ( Hyundai Elantra )

BarryH_GEG said:
^^^^^
This.
Did you use SmartSwitch or another automated method to restore your phone? Android Auto doesn't like to be moved vs. installed and all the apps available for use in AA have to be installed after AA and not before. Try uninstalling AA and all the apps accessible to it and then reinstall starting with AA.
Click to expand...
Click to collapse
I'm using Android Auto just on the device with BT connection to my BMW which does't support Android Auto in the car. The app itself works well but after using it causes what appears to be UI slowdown with the notification shade and application switcher . I uninstalled it again and again the performance on my phone is better so far. I'm not sure it is causing some issue because it launches itself over the lock screen and whatnot. It functions fine but I haven't found anything else that helps with my phones performance than removing Auto. Will keep testing

I just got a Kenwood DDX9703S installed and Android Auto plays great with the S8.

mobilehavoc said:
I'm using Android Auto just on the device with BT connection to my BMW.
Click to expand...
Click to collapse
Does your BMW support Mirror Link? If so, if you have a unlocked S8, it supports Mirror Link too. I haven't used Mirror Link in years and my car natively supports Android Auto but it might be a better solution.

using android auto on a kenwood receiver here, works fine to me no slowdowns

Y does Android Auto need Bluetooth ? Cant we use only with usb like CarPlay ?

vickysud said:
Y does Android Auto need Bluetooth ? Cant we use only with usb like CarPlay ?
Click to expand...
Click to collapse
Yes and I prefer to since my receiver has quick charge.

I have the DDX9703s and galaxy S8 as well. Everything is working fine but I'm not getting my text messages through the head unit. Did you ever have that problem?

CRooks40601 said:
I have the DDX9703s and galaxy S8 as well. Everything is working fine but I'm not getting my text messages through the head unit. Did you ever have that problem?
Click to expand...
Click to collapse
Yes, though I'm sure there's a setting that's the culprit because I do get them sometimes.

Unbelievable. Oneplus claims that a bug is now a feature.

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

problem with bluetooth

hi i love my op6 but there is one annoying thing Bluetooth auto connect ..my phone is connected to my tic watch pro with no problems but when i get in my car that has a alpine halo 9 i have to connect it manually ,also my company car is continually searching for my phone..i have never had this problem with any of the phones i have had [i have had every flagship phone that has come out .IOS or android.] any body shed some light on this for me thanks

nobody got the same problem then

Relax, someone will come eventually... And no, I don't have.

westentertainer said:
hi i love my op6 but there is one annoying thing Bluetooth auto connect ..my phone is connected to my tic watch pro with no problems but when i get in my car that has a alpine halo 9 i have to connect it manually ,also my company car is continually searching for my phone..i have never had this problem with any of the phones i have had [i have had every flagship phone that has come out .IOS or android.] any body shed some light on this for me thanks
Click to expand...
Click to collapse
Everyone who has a smart watch that can make BT phone calls has this problem.
The car kit connects as "Connected (no phone)."
This bug was introduced by Google with Pixel XL after 7.0.2 update, and they never fixed it.
Individual manufacturers fix this in their own Android skins except Google, Xaiomi and now Oneplus.
BTW, the bug was not present in 5.1.5. OOS, and was introduced in 5.1.6 or 5.1.7 (I skipped the 5.1.6 update.) So, it's likely that OP simply and lazily copied Google code at that point.
If you want to get rid of this annoyance, one possible way is to disable Phone Audio option in the watch BT properties on the phone.
Of course, you could also flash 5.1.5.

nabbed said:
Everyone who has a smart watch that can make BT phone calls has this problem.
The car kit connects as "Connected (no phone)."
This bug was introduced by Google with Pixel XL after 7.0.2 update, and they never fixed it.
Individual manufacturers fix this in their own Android skins except Google, Xaiomi and now Oneplus.
BTW, the bug was not present in 5.1.5. OOS, and was introduced in 5.1.6 or 5.1.7 (I skipped the 5.1.6 update.) So, it's likely that OP simply and lazily copied Google code at that point.
If you want to get rid of this annoyance, one possible way is to disable Phone Audio option in the watch BT properties on the phone.
Of course, you could also flash 5.1.5.
Click to expand...
Click to collapse
Thank you. What would I loose disabling phone audio on watch ?

westentertainer said:
Thank you. What would I loose disabling phone audio on watch ?
Click to expand...
Click to collapse
Then you couldn't talk and listen to phone calls on the watch. You could initiate and receive the phone calls on the watch, but the audio would automatically go to the phone instead.

nabbed said:
Then you couldn't talk and listen to phone calls on the watch. You could initiate and receive the phone calls on the watch, but the audio would automatically go to the phone instead.
Click to expand...
Click to collapse
Thank you

Android Auto + Android 10 = broken ?

Hi guys,
my android auto (in a certified compatible car AA) it's fully broken from Oneplus Android 10 versions.
Tried the beta3, beta4, and "official" android 10, always same problems.
Connections in not stable, sometimes audio glitch and interface (of my car) forced to reboot.
Almost always, the buttons from above interface disappear (in every app, like spotify, maps, waze, etc...) becoming fully unusable.
The vocal commands works only with navigator and music, no more google assistance questions (like what's the weather tomorrow) --> This seems confirmed that is broken in google side.
Now, I'm trying to understand if it's fully broken android 10 + android auto (the system AA level, not anymore an app to be lauched) OR it's only with these oxygen's roms, still broken in some way.
Please, someone have real feedbacks to give me ? I'm very disappointed, thinking to go back to Android 9 just for this, but i will loose every update (included the security monthly fix) because OPO is supporting already just Android 10.
What can I do ?
Tried all the throubleshoot I've found around of course, like wipe cache, delete app, use "new" AA interface, cables, etc...
Car: Mazda CX3 (it seems that Mazda + OPO7Pro is the devil match)

avid_droid said:
What I've learned from this phone and Android auto is that if you have USB debugging enabled, Android Auto will give you the worst experience.... EVER!
If you have it off, o don't know what to tell you honestly. If its on, TURN IT OFF! I have a 2017 Chevy RS Cruze and have no issues except when I have debugging enabled
Click to expand...
Click to collapse
Thanks for the tip, but unfortunately it was one of the things I've tried... Disabled the usb debug and also fully disable the dev. Mode...
BUT, are you on android 10 ? Really it's stable to you ?

Guys, some more feedbacks ?
My opo7pro with latest stable 10.0.2 it's still unstable with android auto (mazda).
Main selector icon disappear (becoming unusable), random crash/reboot, audio glitch...
Ufff

I've had my op7p for about a week. I have a Kenwood dmx 905 with wireless Android auto. Phone came with Android 9. Had no problems connecting without using the USB cord. Did the local update to Android 10. Now it won't connect unless I use the USB cord. Then I can disconnect the cord and go wireless. I have to do this every time now. Want to know to go back to Android 9.

m4ssnet said:
Guys, some more feedbacks ?
My opo7pro with latest stable 10.0.2 it's still unstable with android auto (mazda).
Main selector icon disappear (becoming unusable), random crash/reboot, audio glitch...
Ufff
Click to expand...
Click to collapse
Got the same with OOS in my Mazda. Switched to custom ROM, no more issues.

I can confirm the debugging issue making AA go weird. If I have it enabled it has a spastic, if I disable it, AA works flawlessly.

aoaleman said:
Got the same with OOS in my Mazda. Switched to custom ROM, no more issues.
Click to expand...
Click to collapse
man... I'm without hope
Really with custom's no problem at all ? I investigated more... I really think it's a problem also in Mazda side + OPO7Pro Android 10.
I didn't want this time go custom, I'm fully stock without root (for security reason etc...)
Ufff... very disappointed, 10.0.3 still has the same problem :crying:

Having huge problems with my 2016 Skoda Octavia Amundsen. I will try debugging mode off and report. Thx everybody.
-tapola
PS. As AA is not supported in Finland yet, how can I edit the power saving option of this App?