Hi,
I've got yesterday sw2. It is really cool, but sometimes i have problem with bluetooth. Sw2 seems to be connected with phone, but when i start some app, it is loading, but this app don't start. I must restart my watch and then everything works fine, but then when i don't use it for a while it didn't want start against. I am using nexus 5 with custom rom. Where can be a problem?
I am having the same problem. Also a nexus 5 with custom rom. Maybe this is a nexus issue?
Which kernel are you running on the phone.
I am using latest Droidkang rom with stock cm kernel.
Some times I will clear phone's RAM to temporarily resolve this problem.
Any ideas anyone? I have the same problem on stock 4.3 on HTC One Max. It drives me nuts ^^
Stock Nexus 5 has no such issue so I'd start with the kernel /ROM bluetooth compatability. Certain apps seem to lose their state occasionally I've noticed. They generally just need to be closed and reopened though. No reboot has been necessary.
Sent via telepathy
Difficulty with MediaTek devices
I have a Wiko Stairway, which is built on MediaTek platform. Pairing is difficult but possible. I don't know whose fault it is, MediaTek or Sony or both?
Still I find it awkard that I have to install 10MB of Sony software just to establish a faulty connection.
My workaround:
Pair the devices without installing the Smart Connect suite
Install Smart Connect and restart watch
Start Smart Connect and wait a while. It should now find the watch and prompt for installing the add-on
Turn bluetooth off and on on both devices
It should now work
Problem is that every now and then the connection is dropped and you may have to toggle bluetooth on either watch or phone or both. Even sometimes a restart is required.
A work around might be to see if force closing the app 'bluetooth share' temporary resolves the issue. If that's the case you could set up a tasker task to kill bluetooth share every 8 hours or so. You might need a plug-in to properly kill bluetooth share with tasker.
Hey all. I wanted to make a little "Public Service Announcement" regarding an issue that I have had for quite some time and finally solved tonight. I'm hoping it will help someone else because the symptoms of the issue were very strange and an answer was not forthcoming through standard searching.
I have an HTC M8 (Verizon) and I have been having problems with my "Mobile Hotspot" feature for a while. I thought the issue happened after my first upgrade to Marshmallow, but as it turns out the issue was with my Windows 10 PCs (read on...).
Basically, I was able to connect to my phone's Wifi "Mobile Hotspot" without any problems from an iPad tablet or from my wife's Samsung phone. However, when I tried to connect from my Windows 10 PC I had very strange symptoms.
As per my profession, I consider myself somewhat an expert on Windows and networking in general (not "the expert" but "an expert" ). What was so strange about this issue was that the Windows 10 PCs would see the SSID from my phone without a problem. they would connect after providing the encryption key, and they would even get an IP address from the phone's DHCP server. But, after that, they failed to communicate on the network at all. Not even able to ping the phone (default gateway).
I won't go into the details of all my troubleshooting steps (everything from reboots to wireshark analysis), but honestly nothing worked. I determined it must be an issue with Windows 10 after having two different Windows 10 laptops fail to connect properly. I remembered that I didn't have these issues when my system was running Windows 7.
Even armed with this information I was unable to research to any suitable solution online, when I came across a post somewhere that hinted at a similar connectivity issue. The poster seemed to indicate that the Microsoft drivers caused some issues with their devices that was resolved using older vendor drivers.
Both my Windows 10 laptops in questions are quite old. They were never meant to run anything past Windows Vista/7. Because of this, the vendors didn't really offer complete driver packages for these systems for Windows 10. But, during the Windows 10 installation, the OS detected all the hardware in these laptops automatically and, until today the provided Microsoft drivers seemed totally functional.
I hunted down the latest drivers I could find from the vendors (HP/Dell) and using device manager forced the installation of those driver packages. Immediately upon update to those drivers I was able to connect 100% properly to the Mobile Hotspot and access the Internet.
As it turns out, it seems both laptops had Broadcom based cards - so I suspect the issue may be specifically with Microsoft's Broadcom driver.
Hopefully this comes up in a search for the next person having similar issues.
Has anyone had an issue connecting the OP7P (or any other phone) to the Windows 10 Connect app for casting? I've done this with other phones in the past and it's great, but it doesn't seem to be working now.
Everything is setup the way it should be, but when I hit cast and pick my PC, it shows (on both ends) that it connects for a second or two, but then disconnects.
Looking at a logcat, it seems to have something to do with the wifidisplayhals module, but I'm not an expert at reading these. I have the full logcat, if someone thinks they can help.
Some info:
- Windows 10 build 1909
- Current Broadcom Bluetooth drivers (phone won't stay paired to PC either)
- Current wireless drivers
- TP-Link M9 mesh WiFi
Thanks!
Did a quick search. It seems like the Miracast support in the OnePlus 7 Pro doesn't work. There are lots of users with the same issue. https://forums.oneplus.com/threads/screen-mirror-miracast-broken.1158039/
ddrager said:
Did a quick search. It seems like the Miracast support in the OnePlus 7 Pro doesn't work. There are lots of users with the same issue. https://forums.oneplus.com/threads/screen-mirror-miracast-broken.1158039/
Click to expand...
Click to collapse
Thanks for the reply. I saw some of those threads, but they were usually in reference to casting to a TV. I honestly defaulted to it being a windows issue, lol. I can't even connect to my PC via bluetooth. It does the exact same thing.
Well, hopefully the cause is related and hopefully they fix it.
Flapjack said:
Thanks for the reply. I saw some of those threads, but they were usually in reference to casting to a TV. I honestly defaulted to it being a windows issue, lol. I can't even connect to my PC via bluetooth. It does the exact same thing.
Well, hopefully the cause is related and hopefully they fix it.
Click to expand...
Click to collapse
No problem. Yeah from the quick searches I did, it used to be supported in 6T and below very well but was left out of 7 (or poorly implemented, not sure). Unfortunately it's one of those features that not too many people use, but the people who use it find it very valuable!
ddrager said:
No problem. Yeah from the quick searches I did, it used to be supported in 6T and below very well but was left out of 7 (or poorly implemented, not sure). Unfortunately it's one of those features that not too many people use, but the people who use it find it very valuable!
Click to expand...
Click to collapse
I agree. I have tried several apps to mirror my screen on the PC, as I'd like to pick up the phone as little as possible. I don't think it will be a perfect solution, as with the other apps I've tried, I couldn't interact with the phone while the screen is off. I've been using the Microsoft Your Phone app, which is actually pretty good... but seeing the screen on the PC would be amazing.
I have been experiencing issues connecting to devices over Bluetooth. Sometimes it just works, other times it doesn't work at all, and some times it kinda works but not right.
All of these issues are resolved by restarting the phone, but that isn't a solution because the issue comes back.
3 Devices I have been having issues with
1. S Pen - Sometimes it won't connect to the phone, I get an "S-Pen Missing" message and it will not connect. If I t ry to connect to it manually via nRF Connect (The Nordic Semiconductors Bluetooth App) it tells me that the BLE device has a GATT error. It happens semi-randomly but I can always make it happen by doing #2
2. Car Stereo - This is the weird one, it will connect and play music, but it will not do "calls" if I connect to Discord it won't recognise the car as a Bluetooth device it can route to.
3. Raspberry Pi - This one it appears it will connect to ONCE, and then after a disconnect it will not connect again.
Again, each of these can be fixed by restarting the device, but they happen again after a while. The pen & RPi use BLE, I don't know what the car uses for calls.
Turn off global power management completely in Device Care.
Network reset, reboot and clear system cache from the boot menu.
Ok, I've done a network reset, and cleared the cache partition. I checked Device Care for something like global power management, and I couldn't find anything. Most of the pwm settings are off except the "optomise daily" setting.
I'll let you know later if I have the same issue again.
These, this is a N10+ running on Pie.
To check if you have disabled global power go to Developer options>standby apps, all buckets should show as active otherwise power management is enable.
KindarConrath said:
I have been experiencing issues connecting to devices over Bluetooth. Sometimes it just works, other times it doesn't work at all, and some times it kinda works but not right.
All of these issues are resolved by restarting the phone, but that isn't a solution because the issue comes back.
3 Devices I have been having issues with
1. S Pen - Sometimes it won't connect to the phone, I get an "S-Pen Missing" message and it will not connect. If I t ry to connect to it manually via nRF Connect (The Nordic Semiconductors Bluetooth App) it tells me that the BLE device has a GATT error. It happens semi-randomly but I can always make it happen by doing #2
2. Car Stereo - This is the weird one, it will connect and play music, but it will not do "calls" if I connect to Discord it won't recognise the car as a Bluetooth device it can route to.
3. Raspberry Pi - This one it appears it will connect to ONCE, and then after a disconnect it will not connect again.
Again, each of these can be fixed by restarting the device, but they happen again after a while. The pen & RPi use BLE, I don't know what the car uses for calls.
Click to expand...
Click to collapse
Are those the only three devices you connect via BT? What other apps do you use that need to use BT (i.e. Galaxy Wear, Apple Music, etc.).
You mentioned "Nordic Semiconductors Bluetooth App." I looked it up. Why do you need a third party generic BLE connecting app? It seems to me that could be the problem. You shouldn't need a third-party app to connect your BLE devices. The S22U's native pairing will work with any BT device that adheres to BT standards.
Try uninstalling the nRF Connect app and see what happens.
The only other Bluetooth devices I have are other in-house hardware, running on SiliconLabs BGM13P chips or NRF52840 chips...
The NRF app isn't a replacement for your bluetooth pairing app, its a debugging app... it can connect to BLE devices and show their GATT profiles, update devices that have Nordic's OTA update code and copy a devices GATT profile to act as a BLE Server.
We use it for testing and debugging.
KindarConrath said:
The only other Bluetooth devices I have are other in-house hardware, running on SiliconLabs BGM13P chips or NRF52840 chips...
The NRF app isn't a replacement for your bluetooth pairing app, its a debugging app... it can connect to BLE devices and show their GATT profiles, update devices that have Nordic's OTA update code and copy a devices GATT profile to act as a BLE Server.
We use it for testing and debugging.
Click to expand...
Click to collapse
Ok. I recommend uninstalling nRF Connect anyway. If anything, to rule out the app. How old is your car and the Raspberry Pi? Even though BT 5.2 is backwards compatible, sometimes older BT devices won't work with newer devices. That doesn't account for the S Pen issue though.
I uninstalled nRF connect, and changed all the settings you both recommended. Exactly the same behaviour when I went to leave work. My car stereo would do music but not calls, then when I restarted my phone, it worked. Then when I got home, my S Pen would not connect to my phone, then I restarted my phone and it worked.
Its not a problem of not being compatible, its a problem of something stops working.
Please also note that these devices worked fine together in the past. I am concered that it is either a change made by an update or a Bluetooth chip that is faulty....
OP- Have you debloated at all and if so maybe you've removed something relevant that might be causing these issues?
No, stock image, no OS modification beyond the things that Samsung offers (GoodLock and Stock customisation)
I have our in-house apps for interacting with our equipment (over Bluetooth) installed, but #1 they shouldn't affect anything if they are not open and #2 they don't do this to ANY of our other test equipment.
I would just like to say, that I appreciate the assistance that you are all offering! I have used many forums over the years when looking for support on things and I rarely find a place that is more ready to try and help than XDA forums!
KindarConrath said:
I have been experiencing issues connecting to devices over Bluetooth. Sometimes it just works, other times it doesn't work at all, and some times it kinda works but not right.
All of these issues are resolved by restarting the phone, but that isn't a solution because the issue comes back.
3 Devices I have been having issues with
1. S Pen - Sometimes it won't connect to the phone, I get an "S-Pen Missing" message and it will not connect. If I t ry to connect to it manually via nRF Connect (The Nordic Semiconductors Bluetooth App) it tells me that the BLE device has a GATT error. It happens semi-randomly but I can always make it happen by doing #2
2. Car Stereo - This is the weird one, it will connect and play music, but it will not do "calls" if I connect to Discord it won't recognise the car as a Bluetooth device it can route to.
3. Raspberry Pi - This one it appears it will connect to ONCE, and then after a disconnect it will not connect again.
Again, each of these can be fixed by restarting the device, but they happen again after a while. The pen & RPi use BLE, I don't know what the car uses for calls.
Click to expand...
Click to collapse
I've seen the issue of the spen disconnecting but only a couple of times and the issue worked itself out within a couple of minutes with me not having to do anything.
I've also have had a couple of wonky issues when connecting a new Samsung phone to my car. I've narrowed down my issue to the fact that when I transfer my data & settings via Samsung smart switch, it includes the details of my Bluetooth pairings. To fix it, I have to go in and delete my Bluetooth phone settings from the car and from my phone and re-pair them.
Rubby1025 said:
I've seen the issue of the spen disconnecting but only a couple of times and the issue worked itself out within a couple of minutes with me not having to do anything.
I've also have had a couple of wonky issues when connecting a new Samsung phone to my car. I've narrowed down my issue to the fact that when I transfer my data & settings via Samsung smart switch, it includes the details of my Bluetooth pairings. To fix it, I have to go in and delete my Bluetooth phone settings from the car and from my phone and re-pair them.
Click to expand...
Click to collapse
As cool as I think Smart-Switch is as a program, I actually never use it when moving from one phone to another. The junk that Google drags with me from one phone to the next is already too much, I like to use a new device as a chance to do some housecleaning. So no old-data oddities here.
KindarConrath said:
I uninstalled nRF connect, and changed all the settings you both recommended. Exactly the same behaviour when I went to leave work. My car stereo would do music but not calls, then when I restarted my phone, it worked. Then when I got home, my S Pen would not connect to my phone, then I restarted my phone and it worked.
Its not a problem of not being compatible, its a problem of something stops working.
Please also note that these devices worked fine together in the past. I am concered that it is either a change made by an update or a Bluetooth chip that is faulty....
Click to expand...
Click to collapse
Hmmm.. Ok. You're probably right about the suspect causes. I know there is a code you can dial to get into diagnostic mode, I just don't know what it is.
The only other option you can try (as a last resort) is to factory reset it. If it is update caused, a factory reset MAY fix it. If you take it to a service center, send it in for repairs, or do a warranty replacement, they're going to factory reset it, or have you reset it.
have you tried running diagnostics in device care ?
or check with this dc
android
Bluetooth test*#*#232331#*#*
samsung
Bluetooth Test Mode*#232331#
I still haven't done a factory reset, but I continue to have the issue.
I have run the BT Test in device care, it always reports good.
I tried the codes, neither of them work as the first one is for vanilla android and the second is for older versions of Samsung firmware.
I've tried completely unpairing from the car radio and re-pairing, disconnecting and connecting from the other device to no avail.
KindarConrath said:
I still haven't done a factory reset, but I continue to have the issue.
I have run the BT Test in device care, it always reports good.
I tried the codes, neither of them work as the first one is for vanilla android and the second is for older versions of Samsung firmware.
I've tried completely unpairing from the car radio and re-pairing, disconnecting and connecting from the other device to no avail.
Click to expand...
Click to collapse
I'm not entirely sold on the idea that it is a hardware fault. It could be a hardware limitation; meaning you cannot connect to more than a certain number of devices simultaneously. I don't know how many BT devices you can connect to at once. I know at least two simultaneous connections (I've only had two simultaneous connections at a time).
You said you have other BT devices in your house other than those three your having issues with. How many are there? How many are you connected to at any given moment?
Is it possible that you have too many simultaneous connections?
When you try to connect to your car.. Did you check under BT connection (your vehicle) to make sure both audio and calls are checked..
doubledragon5 said:
When you try to connect to your car.. Did you check under BT connection (your vehicle) to make sure both audio and calls are checked..
Click to expand...
Click to collapse
Yes, and I've disconnected, reconnected and even unpaired and re-paired the phone to the car.
gernerttl said:
I'm not entirely sold on the idea that it is a hardware fault. It could be a hardware limitation; meaning you cannot connect to more than a certain number of devices simultaneously. I don't know how many BT devices you can connect to at once. I know at least two simultaneous connections (I've only had two simultaneous connections at a time).
You said you have other BT devices in your house other than those three your having issues with. How many are there? How many are you connected to at any given moment?
Is it possible that you have too many simultaneous connections?
Click to expand...
Click to collapse
Unless having multiple connections causes the BT to fail completely, no. Even after turning the car off and walking away, it still will not connect to the S Pen. The only BT devices I use with that phone regularly are:
S Pen, Car (Music & Calls)
At work I develop devices that use Bluetooth and I sometimes connect to them, but only ever one at a time.