I have to do it manually for some reason. I have no problems connecting automatically with my Huawei watch.
I have the current Global rom. If I remember correctly, there were no problems prior to the last security update. I've tried repairing, deleting cache and data from bluetooth share and rebooting and soft resetting.
I do not want to hard reset.
Mi Mix with 2013 VW GTI.
I have the same problem.
Have the same and I think most of us using MIUI based Rom deal with this issue (I'm on Epic Rom, Marshmallow or Nougat the problem still remaining)
Related
My phone is a T-Mobile branded HTC One M7 with Android 5.0.2. A few days ago, I received an OTA Android update and since then, WiFi has been unusable.
When WiFi is turned on, the phone sees and connects to the WiFi access point, but a error message pops up, "Internet Connection Unstable" with the SSID of the access point displayed below.
I contacted HTC support and was advised to wipe the cache partition. This did not work, and the next bit of advice was to do a factory reset on the phone. I'd like to avoid that if possible... has anyone else encountered this issue?
Thanks.
Earl
UPDATE: this turned out to be not a problem with the phone. I found a rogue DHCP server on the network that was causing the instability.
they might be right, a full reset is quite useful after a ota update (for HTC phones). After upgrading to lollipop I did have a couple of bugs (tho none as major as the one you're describing) and I had to do a factory reset to get everything working flawlessly.
And after trying to upgrade from stock 7.19.401.102 to 7.19.401.121 my m7 stopped working altogether, it got stuck in a bootloop at HTC's logo. I had to flash a nandroid backup I made when I was on KitKat and then upgrade to 7.19.401.102 lollipop, do a full reset, upgrade to 7.19.401.121, and then another reset. That fixed everything for me (maybe the factory resets weren't necessary in that case tho). But I no longer care about htc's stock roms to go through such trouble again.
HTC's ota update seem to have lots of bells and whistle (and annoyances) going about them, which is why I'm on 6.0.1 crdroid ROM.
try clearing the settings app data (from settings>apps) or the WiFi app data. There's no guarantee it'll work but it's better than having to do a full reset.
It seems whenever i reboot my phone, bluetooth would be off when the phone turns back on.
Currently running stock OOS 4.0.3 rooted , I dont recall having this issue when I first got this device, it started happening recently.
Is it a bug with 4.0.3 or is it just me?
This happened to me a while back too. It started after I updated Nova Launcher though the Play Store for some reason. Dirty flashing OOS 4.0.3 fixed it.
I have the same issue. I'm unfortunately a noob and a fiddler and have had to restart my phone a few times in the last week. I only realise that the Bluetooth is off when i don't receive notifications on my watch.
I'm currently downloading OOS 4.1.0 and hope this solves​the issue.
I've been installing the upgrades to the stock OOS and today I installed the beta 4. My bluetooth still turns off after restarting. Any solutions?
I am currently on 4.1.0 , seems the issue is resolved for me
Open Beta 4 does the same thing.
I'm still facing this issue on latest OP3T OTA update
I had the problem coming back after updating to OOS 4.1.3
I cleared the cache and it seems to be fixed, tried rebooting several times and bluetooth remains on
Hello, i'm experiencing issue with wifi.
The AP's are detected, but system is not auto connecting to them.
I must click on connect, then phone associates with AP and everything is OK.
I tried forget network, but it did not help.
My ROM is AospExtended-v4.4-OFFICIAL, Android 7.1.2 (I tried latest LineageOS, but the issue persisted).
Phone Lenovo A7000-a.
In Lenovo stock ROM (Android 6) phone auto connected within a few seconds.
How should i fix this?
MagickNode said:
Hello, i'm experiencing issue with wifi.
The AP's are detected, but system is not auto connecting to them.
I must click on connect, then phone associates with AP and everything is OK.
I tried forget network, but it did not help.
My ROM is AospExtended-v4.4-OFFICIAL, Android 7.1.2 (I tried latest LineageOS, but the issue persisted).
Phone Lenovo A7000-a.
In Lenovo stock ROM (Android 6) phone auto connected within a few seconds.
How should i fix this?
Click to expand...
Click to collapse
You think it's you who is supposed to fix it?
It's a ROM bug. How are you supposed to fix it on your own?
We devs need to do it. And currently we don't plan to.
By providing custom roms to you guys for free, and wasting our time, we are already doing so much for you. If you enjoy so many things in a custom rom like that, then you should also prepare for facing bugs. That one is very very minor.
Also, comparing custom roms to stock roms is a cyber crime.
I have a Verizon Note 9 that recently received the Pie update. Bluetooth has always been flawless while on Oreo with this device. Now after updating with the Verizon OTA Pie update, my bluetooth pairing disappears every time I reboot or shut down and restart. I have cleared the cache partition. I also cleared the bluetooth cache for good measure but this was unsuccessful. I have seen some rumblings about this on Android Central but I have not seen any solutions. Anyone else seeing this here? Has anyone found any workarounds to this bug? I have not factory reset my device yet.
Thanks in advance.
crizyal said:
I have a Verizon Note 9 that recently received the Pie update. Bluetooth has always been flawless while on Oreo with this device. Now after updating with the Verizon OTA Pie update, my bluetooth pairing disappears every time I reboot or shut down and restart. I have cleared the cache partition. I also cleared the bluetooth cache for good measure but this was unsuccessful. I have seen some rumblings about this on Android Central but I have not seen any solutions. Anyone else seeing this here? Has anyone found any workarounds to this bug? I have not factory reset my device yet.
Thanks in advance.
Click to expand...
Click to collapse
Over on reddit someone replied to a similar post with a recommendation to reset network connections. This wipes out all Bluetooth and Wi-Fi settings. I did this and it seems to have helped for now.
Edit: The auto restart was scheduled for the weekend and my bluetooth devices were wiped out again after the restart.
Hello I had the same issues with Bluetooth devices being removed from pairings. I did the network reset and manually restarted phone with no issues but with Auto Restart it was back with the same issues.
From what I think it is, the auto Restart might be the issue for this problem.
Sent from my SM-N960U1 using Tapatalk
Same issue with me. Im rooted with magisk I downloaded libsecure_companion and it worked. Notsure if your rooted ir not
s.lanso said:
Hello I had the same issues with Bluetooth devices being removed from pairings. I did the network reset and manually restarted phone with no issues but with Auto Restart it was back with the same issues.
From what I think it is, the auto Restart might be the issue for this problem.
Sent from my SM-N960U1 using Tapatalk
Click to expand...
Click to collapse
I have never used the auto-restart feature before. All my bluetooth devices are gone after EVERY reboot. So very frustrating. I have even factory reset the entire device and set up from scratch 2x now. Problem persisted
Tonight after the CSC2 update (March 1st security patch) it finally seems to be fixed! :good:
Bluetooth pairings wiped after reboot
Hi, I have a Note 9 N960N Korean model rooted with magisk and EdXposed framework installed, and I had the same issue, after each reboot my Bluetooth pairings are all wipes out... Like Blackout, I installed the libsecure_storage from Magisk repo and it worked ?.
Thanks!
But i Tried to install with magisk module manager, but says failed not a magisk module.
This is the file I downloaded this from gethub
libsecure_storage-libsecure_storage-v2.0.zip
First of all, I'm running MSM Xtended v9 dirty flashed from v5 which was clean flashed after Havoc OS Pie rom some time ago.
Okay so here is the problem as specific as possible.
At first, after doing an online call using headphones (Either via Whatsapp, Messanger, Discord) the mic would suddenly stop working, no voice input would be detected whether its Voice Notes, regular calls, google assistant or any other app that detects voice input. This was back on MSM Xtended v5, which was Clean flashed. The problem then persisted and turned into the mic doing the same thing even without the headphones, then onto doing it again for regular calls too, not just the online ones (so that means I have to reboot after every call). I thought it was a problem with my android version so I upgraded to v9, dirty flashed. I wanted to opt for a clean flash but I had some data on apps that couldn't be backed up at the time. Problem still remained and now the mic suddenly stops working after reboot for no reason without making any calls.
Obviously, as every developer recommends I thought to clean flash the rom again, and prepared myself to backup everything and lose that which I can't back up. Then while looking for a different rom, I noticed multiple people having the same problem for different ROMs, though all were Android 10 ROMs.
So I wanted to ask, is there any solution to this problem? It makes the device basically unusable without any mic, and I do understand that not everyone has the same problem but when I saw others having it I realized it might not be specific to my unit.
Anyone trying other Android 10 ROMs without this problem? Should I downgrade to Pie? Any help would be appreciated, please.
If you recommend downgrading please tell me how, as I seem to have forgotten and can't find the method online (it may be there but I haven't seen, I apologize if that's the case).
Thank you in advance.
Known issue on Android 10, most probably it is Gapps issue, so try Weeb Gapps if you don't need 'Hey Google' thing. Downgrading is not that hard on OnePlus 3T, just download OOS 9.0.6, backup your data to PC or OTG, wipe all and format data and flash OOS, that's it.