Hello
I am on stock 4.2.2 non rooted
Bluetooth doesnot turns on for me..but after doing a reboot it starts
Edited (Possible Cause
I had Snapdragon Battery Guru installed and i uninstalled it and now bluetooth is fine..does not require a reboot anymore..
Same here...
Google and you will see your not the only one.
Reboot is the only solution at the moment.
Had the same issue, but only once. Also solved that by doing a reboot. It didn't happen again (until now).
If anybody knows the reason, would be great.
Schm1dt
Edit: Android 4.2.2 - built JDQ39
this happened to me as well on wednesday. i had to reboot my phone and it seemed to fix the problem.
Hello,
Am I the only one with this problem? Bluetooth loses all paired devices after every reboot...
- no problem pairing with any BT device
- after every reboot some or all previously paired devices are completely gone/missing from the list of paired devices.
- after wiping Dalvik/Cache in TWRP, they all show up again and can be paired without going through pairing (until next normal reboot).
- some device on the paired list may be lost permanently even after wiping Dalvik/Cache IF some new BT devices have been added or deleted. In this case a new pairing procedure is needed, as if the device(s) was never paired before.
It seems some devices are more "sensitive" than others. For example a BT mouse may still be on the paired list after reboot while the car BT (Toyota Venza) will always, invariably disappear from the list. In the car, as it tries to connect, the phone will keep asking for randomly generated pairing codes, which the car will not recognize until the phone gets added/paired again. On the other hand, the phone never disappears from the list of paired phones in the car's BT menu.
Just a thought: it's definitely a phone issue rather than a BT device issue (any). Whether connected or not, within or out of range, the phone will always loose the list of paired devices after a reboot.
Phone: SM-G950F (AQH3)
CSC: XEU (UK & Ireland) / Used in Canada on Virgin Mobile
Rooted with Magisk
Thanks!
Same Problems
Hello, I got the same problems. After seeing that this post is a little older, did you found a solution to this?
Need to try the dalvic/cache solutions next reboot.
Some (unknown) system modifications are the culprit! You need to reinstall the firmware (fresh install) using Odin (all sections, not just AP) and most importantly, during the installation of TWRP make sure you do NOT ALLOW SYSTEM MODIFICATIONS (do not use the slider)..
Just started having this very issue recently. Rooted Snapdragon S8+
Used to ok fine remembering all BT devices after a reboot. Just last week, started to notice I would have to start over pairing all my devices after a reboot. Ex: Car Sync, Gear S3 Frontier, Various Earbuds.
I don't have Twrp recovery due to the locked bootloader. I suspect it could be an app, however, no idea where to begin.... Any advice?
Unlikely for an app to do that, unless the app changed your system. Although I'm not sure what really causes it, I know that "some" system modifications do that. At some point I created shortcuts of some hidden settings, using Activities, which caused that to happen again. I didn't have to go through the hassle of reinstalling everything fresh through Odin since I've had a recent TWRP backup and I've restored both, the System and Data. I've lost many hours trying to figure out what exactly causes it but I didn't get any further than figuring out that: (1) some system modifications cause this to happen and (2) reflashing firmware through Odin without allowing any other system modifications during the process, is the ONLY WAY to get back the normal BT behavior.
Any fix for this
I have started getting this on my rooted S9+
Started to get annoying now.
I have stock rom, custom Kernal and magisk.
What resolved yours in the end?
It seems to be an Xposed issue: https://github.com/rovo89/Xposed/issues/294
Despite the apparency, I don't think this is caused by the XPosed framework. As I've detailed above, the problem may occur even before installing XPosed. Even with XPosed installed, everything may be running just fine indefinitely, until certain system modifications seem to be triggering this problem. Although I pointed out before that this would most certainly happen if, during the TWRP installation, system modifications are allowed (by sliding the bar), I'm almost sure that TWRP in itself is NOT the culprit. The same may be said about XPosed. While both may seem to potentially be triggering the issue, I don't think they really are the cause. My feeling is that the real cause is Samsung's native system (possibly one specific application). I've noticed, for example, that when the problem occurs, while Android loses the list of previously BT paired devices either partially or completely, Samsung's Connect still sees them all - as if nothing happened. How is that possible? It's just assumptions at this point but one thing is certain - after freezing Samsung Connect (Smart Things), I've never had the issue again.
As for permanently resolving this once it happens, there seems to be ONLY two ways:
1. Start fresh by re-flashing the stock ROM through ODIN and if TWRP is also installed, system modifications should not be allowed at this time, or.
2. If you already had TWRP installed and had a nandroid backup (System and Data) done before the problem occurred, (1) wiping system and data and then (2) restoring their respective previous versions, definitely solves the problem, without having to go through ODIN everything fresh.
I hope this helps, and I also hope that someone could eventually identify the root cause and address this once and for all. I definitely wouldn't hold my breath counting on Samsung's help!
Note 10 + sm-n975f
Rooted with Magisk
Definitely not an exposed issue because I am not using exposed, never had exposed on this device.
Same problem with 2 different phones of the same model. One was a international dual sim and the other international single sim.
2 other problems,
Sometimes incoming call notification sound can be heard but no incoming call shows up on the screen (ie. Answer /decline. No missed call notification either, only a new voicemail notification, but if they do not leave a message then you would not know who called. lol
Other issue is Sammy is putting music apps to sleep randomly even though I used an app to set screen time out to never.
Never had any of these problems on any other rooted device always used note phones. Ready to get an Exynos note 8, got the 10 because thought it was cool and I was using the note 8 previously with SamFAIL. Too many glitches though.
Man Sammy is failing big time as usual. Never had this foolishness on any other note always been using rooted notes. (exceptffor note 9) Every Sammy support agent acts like they never heard of this before. I see a bunch of note 9 users on shameful Sammy's forums having this exact Bluetooth problem, shame on Sammy's lies and ignorance!
Update :
Found this Magisk fix, This file name is
nfsinjector-956.zip
Flashed with Magisk module manager.
Update : still not working
From experience, I can confirm that a failsafe way to ALWAYS get back all previously stored BT paired devices is to wipe your Dalvik/cache in TWRP.
I'm still on a Samsung S8, rooted with Magisk + TWRP and XPosed. Once in a while I get this BT issue and the above suggested solution always worked for me. Let me know if it works for you.
As for the rest of the problems, I'm really disappointed to hear that. I was planning on buying myself a Note 10 but that makes me rethink it - it pretty much was THE REASON I held back for so long.
I always suspected this had nothing to do with the XPosed framework but every one on Earth, including the devs, swear by it. Well, you just confirmed it.
Xposed had this issue on s8 we had found a fix somewhere. It may not be present on newer versions. Modifying the libs or something. I studied into it. It's even in the github for xposed. So for me it was most definitely xposed
Thanks for the wipe cash fix, I would like to try it, but not sure if I can since I don't have twrp, can twrp be installed on a Exynos note 10?
Is Its possible that the xposed fix is actually fixing a Samsung failure and not an xposed problem to begin with in the place?
all those people on the note 9 shameful Sammy fourms I assume are unrooted users!
Xposed had always had issues on Samsung's. Until s7 or 8 it was modded by Rovo. The s8 didn't need rovos xposed.
Hello,
Coming from the CRAP build on my 955FD. The new CRB7 build is causing my car Bluetooth to suddenly stop and then resume audio but with a significant delay. It did not do this in CRAP. I am rooted and am looking for any way to fix this issue. Everything else works. I tried to downgrade but I believe we cannot downgrade galaxy phone anymore (odin stuck). Any advice would be very helpful.
What about try freshly pair your phone with car ?
Also try delete cache from stock recovery (or twrp, base on what rec. you have)
qpkqkma said:
What about try freshly pair your phone with car ?
Also try delete cache from stock recovery (or twrp, base on what rec. you have)
Click to expand...
Click to collapse
Actually formatted my cars head unit and re added the phone. Deleting the cache doesn't help either.
Because I came from ZRA5 to CRB7 with no_wipe , and I dont have any problems with car BT audio.
I dont think anyone will have other response than backup your data and do a factory reset :/
Well atleast it pairs, i cant connect to bt earbuds at all. Tried with a set of a friend aswell and the result was the same.
Atleast my usb c earbuds are finally working properly.
Actually found out my radar was causing the issue with bluetooth delay. Weird.
Hi there,
I've been using my Oneplus 5 for quite a while with the following configuration:
OOS 5.0.4, Magisk 16.3, Boeffla Kernel 2.0, AFWall+ and everything worked fine. After upgrading to OOS5.1 (and Boeffla 2.1 Beta) I'm facing network connectivity issues.
Right after a fresh boot everything works fine. But then sometimes, networking (WiFi and Cellular) stop working. I can't get any data at all. Enabling and disabling flight mode doesn't help and disabling AFWall+ doesn't help either.
The network's are connected, I get IP Addresses and DNS Servers, but just no data
To get things working again I have to reboot the phone which is quite annoying. Anybody else facing this issues? Any suggestions?
bigtreiber
bigtreiber said:
Hi there,
I've been using my Oneplus 5 for quite a while with the following configuration:
OOS 5.0.4, Magisk 16.3, Boeffla Kernel 2.0, AFWall+ and everything worked fine. After upgrading to OOS5.1 (and Boeffla 2.1 Beta) I'm facing network connectivity issues.
Right after a fresh boot everything works fine. But then sometimes, networking (WiFi and Cellular) stop working. I can't get any data at all. Enabling and disabling flight mode doesn't help and disabling AFWall+ doesn't help either.
The network's are connected, I get IP Addresses and DNS Servers, but just no data
To get things working again I have to reboot the phone which is quite annoying. Anybody else facing this issues? Any suggestions?
bigtreiber
Click to expand...
Click to collapse
It's definitely not the oos problem. Please backup and clean flash. I guess it's kernel or some of your apps like AFWall.
Reading this I felt kernel issue as well. Make sure you're not using the kernel you were using on. 5.04 (Oreo 8.0). Make sure you have a kernel from him that is made for OOS 5.1 (Oreo 8.1). Any thing from him that worked on the Open Betas should work fine
Solved it, was a problem withnAFWall+ custom script that no longer works on Oreo 8.1
I'm running stock Oreo 8.1 (unrooted, bootloader locked) and a week ago NFC stopped working for Android Pay and other apps. NFC looks switched on in settings but is randomly greyed out and or has switched itself off. I've tried a factory reset and booting in safe mode so I'm thinking it's not app related.
Can't really find this problem on researching more. Really keen to hear any ideas or suggestions. Thanks!!!
Any updates on this? Did you get it to work?