I have an issue that I need some help. I've been searching in the forum and internet and didn't find anything that applies. I'm not sure if this is a problem with my phone, with S9+ or Android 10. If this post is placed incorrectly, I would like to ask any mod to change it to the correct location.
I have a new S9+ phone, upgraded to official Android 10 OneUI 2.5, and then rooted with Magisk. I have much of the crapware Samsung shoved in the equipment either removed or disabled, but nothing is related with Bluetooth, AFAIK.
This phone have a very odd and annoying behaviour. It looses the Bluetooth pared devices list every time I turn off BT, and I'm forced to pair it again with any device previously paired. This happens with any other BT device - another phone, an earphone, speakers, etc. If I turn the other device BT off, and keep the phone BT on, it shows the disconnected device in the list, and when I turn it on again, it's still in the list of paired devices. Therefore, it only happens if I switch off the phone BT.
I usually have the "nearby devices BLE" crap disabled, but if I turn it on, this behaviour doesn't show - it doesn't loose the devices list. I think that might be because that "nearby devices" keeps part of Bluetooth always on, even when I switch BT off.
Please note that I don't have any other issue to operate or pair a BT device. It pairs without issues and it keeps the connection normally. My old S7 Android 8 phone still works like a charm with same devices.
I already tried the only 2 possible solutions I found for somewhat related issues; I dumped the cache and data of the Bluetooth service, and I reset all connections (WiFi+BT+Mobile) in the Settings. Nothing have solved the issue. I would do a complete factory reset, but the phone is completely configured and all apps installed and it would be a major pain if I had to start over!
Anyone can help?
When you repare what does it do?
Just a pop up asking if you want to connect?
Or it doesn't recognize the previously registered bt device?
Are you using the Wearables app?
I don't repair. I just switch off BT and it immediately forgets the previously paired devices.
In my old phone(s), each time I turn BT on, it shows a list with the paired devices, and if I connect the BT on any of these, it automatically connects. If I turn off BT in the phone and on again, it will show the paired devices list and they are still there.
That doesn't happen with the new phone. I switch BT on, it shows an empty list of paired or available devices. It start to scan for new devices. If I switch on my BT earphone (for example), it finds it, I can pair them and use the earphone perfectly. If I switch off and on again the earphone, the device is still listed. If I switch BT off and on again IN THE PHONE, the list of paired and available devices is empty. I have to scan, find and pair the earphone (or any other device) to use them again. Every time.
I don't have any smart watch or similar. My earphone is a Jabra 25 but that happens with another phone or device. I have the Samsung wearables apps freezed. I will unfreeze them to see if it changes anything.
BTW... I found this post (https://forum.xda-developers.com/t/bluetooth-pairing-gone-adter-reboot-phone.4004833/) and I tried to install Magisk libsecure_storage, but it said "installation failed" and it still doesn't work.
Wearable Manager Installer was not (and is not) frozen.
I defrosted ANT+ and ANT Radio stuff and Device Services, but it didn't work. I also have SmartThings crap frozen, but I don't think it's related with this issue.
On the other hand, Magisk is 23.0 and I have BusyBox, MagiskHide Props Config and Systemless Hosts Modules installed, if that's relevant.
phoenix.pt said:
Wearable Manager Installer was not (and is not) frozen.
I defrosted ANT+ and ANT Radio stuff and Device Services, but it didn't work. I also have SmartThings crap frozen, but I don't think it's related with this issue.
On the other hand, Magisk is 23.0 and I have BusyBox, MagiskHide Props Config and Systemless Hosts Modules installed, if that's relevant.
Click to expand...
Click to collapse
Was Wearables updated recently?
The last update broke mine and it was behaving similar to yours. I had to reinstall a copy of a previous version and then firewall block it's updating IP. It's a handful.
Galaxy Buds, Buds+ Set up
Install the Galaxy Wearable and Galaxy Buds software. Update software and Buds firmware, this is important because the old versions sound sucks. Turn on/go to Developer Options in Settings and on the Bluetooth Codec setting toggle on Samsung's...
forum.xda-developers.com
I really don't know... I have been updating most apps and services in the last week or two, to prepare my new phone, so probably yes. What is exactly the wearables app you talk about? "Wearable Manager Installer"? That's the only "wear" app I have.
Both. Had to reinstall both of them or at least I did. The new Galaxy Wearables interface sucked.
Galaxy Wearables:
Known good versions:
Wearables Manager Installer, Version 1.1.15.13054
Galaxy Wearables, Version 2.2.33.20082161
I suppose I don't need Galaxy Wearables at all, because I don't have gear from Samsung, right? Only the installer?
Indeed my version of Installer is 2.1.01.19006
phoenix.pt said:
I suppose I don't need Galaxy Wearables at all, because I don't have gear from Samsung, right? Only the installer?
Indeed my version of Installer is 2.1.01.19006
Click to expand...
Click to collapse
Yeah, you need the Installer as it loads the drivers I think.
Wearables is intended for the Buds and such. It also provides firmware flash updates for them
I don't know the buggy installer or Wearables version numbers.
I had multiple problems including connectivity and bad audio quality except for phone calls
I keep installable backup copies via ApkExport so I was able uninstall then reinstall the old versions. Otherwise I been more boned... more than I was already. I was pissed.
Try this...
Uninstall the newer version first. You'll may need to block the IP address* I gave in my Buds+ thread to prevent an auto update.
Firewall's log: (UID 10339) [18.203.4.139]
Related
I just switched to a Galaxy S3 from an Desire HD. Overall I'm not very happy.
One issue that is turning into a deal breaker is the BT connection with the car. I have been unable to make the S3 connect automatically with my Nissan Connect and it is a laborious process to establish a full phone and media connection.
This is what happens,
The pairing process goes well I get a a full media and phone connection. After about 30 secs the connection is dropped.
I reestablish the connection manually and I only get media audio no phone. I cancel the connection manually and reestablish the connection and there I get both media and phone audio.
If I turn off the car and turn it on again I have to go through the whole manual connection sequence again, without the pairing.
I have installed A2DP Volume app but it did not fix the problem.
This is very frustrating since my Desire HD worked flawlessly when connecting to the car.
Anyone have any tips or experiencing similar problems?
this exactly happens to me as well. i was on the stock XALE8, but upgraded to ALF5 and nothing new. this is frustrating because it happens to my car, and multiple bluetooth headsets.
Bluetooth working fine for me and my Fiat
Sent from my GT-I9300 using Tapatalk 2
Right I might know the answer to this as I had the same problem as few weeks ago.
If you have Facebook, twitter, whatsapp or anything like this best thing is to get rid of them if you don't want to, go to your accounts and sync on your phone and untick the sync with contacts on any of the apps you have installed.
Then go to call log and clear your call history.
Delete the bluetooth pairing turn the phone off and back on, repair with the car, mine has worked perfectly since I did this.
Sent from my GT-I9300 using XDA
So from what you describe the problem lies in the syncing of the phone contacts with the car contacts. Maybe since it also tries to sync the FB contacts there is something in the format there that it does not recognize and it gets hung up.
Will need to try different sync configurations to see what happens.
Help
Motogp1 said:
Right I might know the answer to this as I had the same problem as few weeks ago.
If you have Facebook, twitter, whatsapp or anything like this best thing is to get rid of them if you don't want to, go to your accounts and sync on your phone and untick the sync with contacts on any of the apps you have installed.
Then go to call log and clear your call history.
Delete the bluetooth pairing turn the phone off and back on, repair with the car, mine has worked perfectly since I did this.
Sent from my GT-I9300 using XDA
Click to expand...
Click to collapse
I've got the same problem with my S3 not syncing with my car kit. The bluetooth is all paired but the car still says no phone. Tried unpairing and just about everything else with no luck at all. Any other thoughts please?
Mine works fine with the Toyota Touch & Go thingy. I only sync contacts from my Google account to the phone though, I don't bother with the ones from FB, etc
Sent from my GT-I9300 using xda premium
Hi there. Following up on this thread, I've had a similar issue with the miss's Galaxy S3 mini (android 4.1) and the Nissan Connect System on her Juke. It also happened with a HTC Status (ChaCha, android 2.3), so I can't narrow it down to a particular Android version or phone manufacturer. What happened was, both devices paired well with Nissan Connect, but after a short while, the system crashed completely (the cars, not the phone) :s. It would restart automatically, but just to crash again after re-pairing. With older devices, this issue never occurred.
After reading Motogp1s answer, I decided to give it a shot. Unpaired all devices, cleared the system on the nissan. On the S3 mini cleared the call history, and disabled all contact sync from facebook, google, etc. Re-paired the device, disabling the multimedia functions (she just wants the phone features) on the paired device settings (NISSAN CONNECT on the S3). Refused to give permission tho the car to retrieve call and contact information. At this point, the bluetooth connection would work without a glitch, never had a crash or problem again.
Like RaulTT said, the problem seems to be in the amount of information Android devices keep on their contact list (and can also be related to the amount of contacts, or the multimedia features in the case of Android 4). But given the sweetness of having your contacts also on the car, I think the best approach is to keep a short list of your most important contacts on the SIM card, and try to sync only that list. If you must go with the phone's list, you should indeed disable all contact sync from 3rd apps, plus limit the size of your contact list, and also be aware for special characters on the contacts names (in case of latin languages, p.e).
Thanks for the help.
Hi All,
I experience a Bluetooth trouble for some weeks: by the past I kept BT always active as it connected automatically upon entering in my cars. I was alerted because I no longer saw the “Connected …” message on the dashboard. I discovered that now, when I activate BT, it starts normally but it stops if it doesn't find any device to connect in the following 2 minutes. I have tried everything I know, even installing some software starting BT and keeping active when the phone is plugged. Nothing to do, it is always the same thing. Fortunately if it finds a device to connect it stays active as long as it is connected.
I have to say that I don't use any battery saver, I don't use the Android option "Energy saving" and I don't use any system program that could be linked to Bluetooth management.
Can anyone help me on this to recover a standard comportment?
BR.
Daniel.
So, I've had my Gear S now for about a week, and LOVE it. The connection stuff has me a bit confused though. I have it paired with an AT&T Note 4. There are a few things I have questions about...
If I reboot the phone, the watch will only connect to Gear Manager remotely. Shouldn't it connect to Bluetooth first? I have to go into Gear Manager and disconnect the remote connection, then it will reconnect via Bluetooth.
Under what circumstances does the phone forward calls/sms to the watch? For example, on purpose, I left my phone at home one day, and went out for a drive. Calls and SMS that were made came from the watch's number. I can't say about the receiving end because I didn't receive anything LOL.
Sometimes, if I go out of Bluetooth range at home, the home wifi will kick in, but repeatedly get a message on the watch that the forwarding function failed.
I'm definitely keeping this baby, but just need a little help in understanding it fully.
diehardbattery said:
So, I've had my Gear S now for about a week, and LOVE it. The connection stuff has me a bit confused though. I have it paired with an AT&T Note 4. There are a few things I have questions about...
If I reboot the phone, the watch will only connect to Gear Manager remotely. Shouldn't it connect to Bluetooth first? I have to go into Gear Manager and disconnect the remote connection, then it will reconnect via Bluetooth.
Under what circumstances does the phone forward calls/sms to the watch? For example, on purpose, I left my phone at home one day, and went out for a drive. Calls and SMS that were made came from the watch's number. I can't say about the receiving end because I didn't receive anything LOL.
Sometimes, if I go out of Bluetooth range at home, the home wifi will kick in, but repeatedly get a message on the watch that the forwarding function failed.
I'm definitely keeping this baby, but just need a little help in understanding it fully.
Click to expand...
Click to collapse
With my S5 initially, Remote Connection would kick in after a few minutes out of Bluetooth range. But, when I was back in Bluetooth range, I would have to do what you are doing to drop RC. I had a Gear 2 Neo prior to Gear S, don't know if that was any issue. .I did a factory rest on S5 ( to get rid of root and some other things) , and now watch connects and disconnects to RC by itself and rather quickly. BTW, when in RC, all texts and calls to S5 do come to Gear S. If I were in your shoes, I might try to reinstall Gear on phone before wiping phone. IF you do wipe phone, Gear S will be reset during the pairing process, so you may want to back up your Gear S data prior.
Op. Under settings-connections-mobile network, do you have it set to auto connect? On the phone side of things for Bluetooth settings, gear s contented to phone audio?
jerrycycle said:
Op. Under settings-connections-mobile network, do you have it set to auto connect? On the phone side of things for Bluetooth settings, gear s contented to phone audio?
Click to expand...
Click to collapse
Yeah, all that was set, but I ended up wiping both the phone and the watch and everything seems fine now... Still loving the watch... wondering how they'll make the next one better..
Has anybody got Cloud Sync to work?
I want notifications to go to my watch without a bluetooth connection.
I can connect the watch to wifi but I can't get any updates from my watch.
I have the same problem. I am using a Note 4.
I already did a reset without a result .
The asus support could not help me.
It seems that not many owners tries to use this feature. Would be interesting if any zwatch 2 works with wifi.
I know mine does not respond to 'OK Google' when I am out of BT range, even if it says it is connected to WiFi. I do seem to be able to get notifications though, and I have always been able to execute Tasker Tasks from Wear Tasker.
But Android Wear docs say "OK Google" should work. I have seen similar reports from others using different watches so I am guessin this is just some typical broken Google goodness we'll have to wait for them to straighten out.
I used to have tons of sync issues with my Zenwatch (both first, second gen), and this trick solved all my issues - have no idea how and why, but it worked:
Just let my Zenwatch battery go empty, did not charge it for 4-5 days, than recharging. It connected my phone (mate 7) again normally, and all syncs (in my case weather, notifications, step counts) worked fine again - permanently. NO idea how it works (emptying cache watch?), but it worked for me.
All other suggestions of forums (re-installing, reconnecting): not..
Jus my 2c
After a bit of research and some common sense troubleshooting, I have my watch working as expected on my local Wi-Fi network.
I read something somewhere that Wear has had some issues on higher Wi-Fi channels. I also downloaded WiFi Analyzer to check used channels in my area. All APs were in the neighborhood of ch 6-11.
I forced my router to ch 1 and bingo. Phone is now upstairs at the other end of the house and everything is working great, including 'OK Google' (knock on wood).
My ZW 2 has a working wifi connection (2.4Ghz Port1). I know that because google maps on the watch is working even when the phone is switched off.
My problem ist, that no notification appears on the phone and no "ok google" command works, when phone and watch are only connected via wifi and bluetooth is switched off.
The asus support told me, that i am the only person with this problem who contacted them.
Seems to be a problem with my galaxy note 4.
I will give it a try with a xperia z3 compact the next days.
I can´t believe this is a hardware problem.
roboterente
I've seen other threads in passing mention issues with bluetooth but no detailed responses as to whether it's likely to be hardware issues common to Huawei, or something that has been fixed in later updates.
The symptoms: Not every time, but regularly enough to be annoying, bluetooth audio will revert to phone loud speaker, even with bluetooth shown as enabled and the device connected. correctly. This has happened with headphones and car receiver (both cheap and cheerful Chinese stuff). Often if I toggle bluetooth off and on again audio will switch to the headphones for a second or two, then back to speaker. If I go into bluetooth settings and disable media audio and then re-enable, it usually then works for the remaining time I have the bluetooth device connected.
When it's in this state, the play/pause button on the bluetooth device still works, showing that there is still a connection - so the issue seems to be audio routing.
Has anyone had this problem in the past and now found that it doesn't happen after an update? (Change log for one of the newer updates not yet available on my model C782 ,mention bluetooth).
Or has anyone who switched to a treble ROM found that the problem is gone (suggesting software) or remains (suggesting hardware or chipset issues).
Considering a rebrand to C432 to get the more recent updates, but would be good to know if that's likely to solve the bluetooth issues.
Thanks
Do you have development settings enabled? Found out that having it disabled solved my problems with fallback to phone speaker. If i enable it, the problem comes back. Even with not changing any parameters in the settings. I'm now on c432 137 and the problem has been there from the release...
L.R.G. said:
Do you have development settings enabled? Found out that having it disabled solved my problems with fallback to phone speaker. If i enable it, the problem comes back. Even with not changing any parameters in the settings. I'm now on c432 137 and the problem has been there from the release...
Click to expand...
Click to collapse
Actually yes I do! (for adb access while trying to get HiSuite to work). I'll try turning it off and see if that fixes it - thanks
gonzo99 said:
Actually yes I do! (for adb access while trying to get HiSuite to work). I'll try turning it off and see if that fixes it - thanks
Click to expand...
Click to collapse
Any update on this - did disabling developer settings help?
I have same issue too. Does it help to disable the mode?
bkakus said:
I have same issue too. Does it help to disable the mode?
Click to expand...
Click to collapse
It did seem to help but hasn't solved it entirely. Neither have the two major updates I've had in 6 months....
It happens intermittently so I've learnt to live with it, but it's still annoying when it happens.
I think that is more a PIE problem.
I was using the Essential PH-1 for the past 3 months (reverted back to my Mate 9 on Oreo) and my Essential would once in a while
do that. I typically wear a BT headset, plantronics 5200 series, and once in a while, I would hear the beep beep as it reverted back
to the phone, requiring me to press the speaker icon to put it back on the headset. It SHOWS the headset connected to BT, but would
just switch from the BT headset to the speaker.
I also wear a Samsung G3 Frontier watch, and once in a while, it would switch from the Essential, to the watch, requiring the same
process of pressing the on screen speaker to switch it back to the headset.
NEVER had that problem on my Mate9, running Oreo.
Hope that helps, that it might not be the phone, but the OS.
Not a Pie problem, because mine isn't on Pie yet.
I have had the exact same problem for a longer period of time. Huawei contacted me saying it was solved, but it wasn't. The latest contact with huawei official said that I should send my phone in for repair. Annoying when I know that several others have the same exact problem.
Maybe it's coincidence, but mine seems to disconnect at similar locations. Maybe that's just a function of me having a boring routine, but it happens almost like clockwork on my drive home from work.
I've seen in other threads that freezing the app (via root) Power Genius solves this problem.
Bobomo said:
Maybe it's coincidence, but mine seems to disconnect at similar locations. Maybe that's just a function of me having a boring routine, but it happens almost like clockwork on my drive home from work.
Click to expand...
Click to collapse
I've noticed the same thing. It seems to be more likely to disconnect at certain locations on my drive. I wonder if being near other bluetooth or wifi networks has anything to do with it.
This happens (I think) because EMUI kills off background processes needed for bluetooth music playback (in the name of battery optimization). It happens when your music player is in the background (or your screen is off), and the more apps/processes running, the more likely EMUI is to kill something off.
If rooted, use either Titanium Backup or Service Disabler to get rid of Power Genius, which is the app responsible for Huawei's battery optimization. There are zero negative consequences in my experience with the MediaPad M5.
If you aren't rooted, there's a way to uninstall system apps via ADB, but I don't think it works for this.
I've disabled Power Genius via adb and it has not helped.
yurkyurk said:
I've disabled Power Genius via adb and it has not helped.
Click to expand...
Click to collapse
Try rebooting, after disabling it.
But also, I haven't personally seen someone claim to successfully disable it via adb.