-
Notifications
You must be signed in to change notification settings - Fork 11.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bluetooth keeps stopping #6389
Comments
Same here :/ |
Please also provide kmsg. |
For me it's alternating between stopping "Dolby Atmos" and Bluetooth. |
I had this issue on my Xiaomi Redmi 8 aswell. For some reason, when i reset my phone it started working again. Absolutely no idea as to whats going wrong. |
same problem here, Alcatel 3X 5048Y 2019 |
Close because there is no response to my request for kmsg. |
I'm sorry, how can I provide the kmsg? |
I don't have that phone with me anymore. |
We can't fix it, PR welcome. |
I wanted to capture kmsg. But since yesterday, bluetooth is working just fine on my phone (with magisk installed) for some reason :/ Mi 8 - Evolution x - A13 |
Apparently, it's not a bug in magisk, but in TWRP. Didn't work for me, maybe you will have better luck |
Not so sure about that: I had to reinstall my phone since uninstalling Magisk didn't help, but now I'm running on the latest TWRP with the "older" Magisk 23.0 just fine. |
@Joghurt to me after formatting this problem re-appear the first time I reboot into TWRP, before even installing Magisk |
@lorenzoPrimi Not sure if by formatting you mean the whole thing or just back to factory settings - I completely re-installed the whole firmware from scratch with the factory tool "MsmDownloadTool V4.0.exe". |
Here is what worked for me.. and what didn't work. I am on a OnePlus 7 Pro (GM1915) with stock OOS 11 and using TWRP recovery. Right now, I am on TWRP 3.6_11-0 and using Magisk 25.2. What doesn't work: Wipe (factory reset), boot system and run setup. Reboot recovery, flash Magisk, reboot system. Bluetooth (and keychain, and Atmos...) is broken. Constant message coming up about these stopping. What worked: boot recovery, wipe (factory reset), now flash Magisk <-- this is the difference because the Android one-time setup has not run yet, reboot system, go through setup. I did not see Magisk app, so I installed Magisk 25.2 APK via File Manager. Upon opening, it says additional setup needed and reboots device. Once rebooted, device is rooted, bluetooth works. |
it works, thks! |
So the reason why this works is that the TWRP bug takes hold the moment it is booted into and the only way to fix it is to factory reset. Hence why flashing Magisk without leaving and coming back for it is what is working. Similarly, if you EVER re-enter TWRP again, the bug will reappear. I learned this the hard way by following your steps, got absolutely everything set up and working and needed to go back to TWRP for something unrelated. I booted to it, realised I hadn't removed my lock pattern so I rebooted system. The bug returned. Very upsetting haha. From what I can see, it's a TWRP 3.7_XX-X bug as rolling back to 3.6_XX-X allows me to enter and leave TWRP all I want. I'm actually on a completely different handset too, an Asus ROG Phone II. Looks like this bug is certainly making its way around. |
hurt ,it's so hurt! (痛,太痛了!) here's what I suffered : https://www.cnblogs.com/sillage/p/17317928.html , it is so odd. |
Please any working help to resolve to 100% this bug? After installing Magisk, everytime when booting up the device (or rebooting), in less two minutes a message saids: I only solved it with wipe data/factory reset. But after install Magisk the problem begins again. |
Redmi Note 8 here. |
Hi all. |
TeamWin/android_bootable_recovery#332 (comment)
It works. |
F*** ME !!! |
I have a problem with the Bluetooth that stops working as soon as I install Magisk from TWRP.
Steps to reproduce:
Crash Log https://pastebin.com/h0zSZHw7
Magisk Log
magisk_log_2022-11-13T19.10.51.log
I tried creating the folder
/data/user_de/0/com.xiaomi.bluetooth/databases/
chowning to bluetooth:bluetooth and chmod to 777 but didn't change the situationEnvironments:
Device: Redmi Note 8
Android version: Android 10
Magisk version name: cf9957c
Magisk version code: 25205
The text was updated successfully, but these errors were encountered: