Skip to content
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

Closed
lorenzoPrimi opened this issue Nov 13, 2022 · 23 comments
Closed

Bluetooth keeps stopping #6389

lorenzoPrimi opened this issue Nov 13, 2022 · 23 comments
Labels
not our issue This issue is caused by third-party like customized rom or module wontfix Not going to fix it

Comments

@lorenzoPrimi
Copy link

I have a problem with the Bluetooth that stops working as soon as I install Magisk from TWRP.

Steps to reproduce:

  • Wipe the phone
  • Restart the phone, add the google account, do basic configuration (both restoring from backup or setting brand new phone causes this issue)
  • Flash Magisk from TWRP
  • As soon as you restart the phone you get the message "Bluetooth keeps stopping" Even after installing the Magisk app

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 situation

Environments:
Device: Redmi Note 8
Android version: Android 10
Magisk version name: cf9957c
Magisk version code: 25205

@omariyassinee
Copy link

Same here :/
Mi 8 - Evolution x - A13

@yujincheng08
Copy link
Collaborator

Please also provide kmsg.

@Joghurt
Copy link

Joghurt commented Nov 27, 2022

For me it's alternating between stopping "Dolby Atmos" and Bluetooth.
Going back to Magisk 22.0 doesn't fix the problem.
OnePlus 7 Pro (A11)

@Arc157
Copy link

Arc157 commented Nov 27, 2022

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.

@Klairm
Copy link

Klairm commented Nov 27, 2022

same problem here, Alcatel 3X 5048Y 2019

@yujincheng08
Copy link
Collaborator

Close because there is no response to my request for kmsg.

@yujincheng08 yujincheng08 closed this as not planned Won't fix, can't repro, duplicate, stale Nov 30, 2022
@yujincheng08 yujincheng08 added the stale No response for a long time label Nov 30, 2022
@Klairm
Copy link

Klairm commented Nov 30, 2022

Close because there is no response to my request for kmsg.

I'm sorry, how can I provide the kmsg?

@lorenzoPrimi
Copy link
Author

For me it's alternating between stopping "Dolby Atmos" and Bluetooth. Going back to Magisk 22.0 doesn't fix the problem. OnePlus 7 Pro (A11)

I don't have that phone with me anymore.
But it would be good if anybody can provide the kmesg, as this is a bug that many people have and needs to be fixed. Closing the issue doesn't solve the problem, just hides it.

@vvb2060 vvb2060 added the not enough info Not enough info to fix label Nov 30, 2022
@vvb2060
Copy link
Collaborator

vvb2060 commented Nov 30, 2022

We can't fix it, PR welcome.

@omariyassinee
Copy link

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

@lorenzoPrimi
Copy link
Author

Apparently, it's not a bug in magisk, but in TWRP.
Here is the problem: https://www.reddit.com/r/PixelExperience/comments/hmhwxa/xiaomi_redmi_note_8_bluetooth_keeps_stoping/
And here is a backup link for the fix: https://dosya.co/065850v69htp/BT-fix-for-PE-20190618.zip.html

Didn't work for me, maybe you will have better luck

@Joghurt
Copy link

Joghurt commented Dec 21, 2022

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.

@lorenzoPrimi
Copy link
Author

@Joghurt to me after formatting this problem re-appear the first time I reboot into TWRP, before even installing Magisk

@Joghurt
Copy link

Joghurt commented Dec 21, 2022

@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".

@AlphaGeek1
Copy link

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.

@hyw0810
Copy link

hyw0810 commented Mar 23, 2023

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!

@Avsynthe
Copy link

Avsynthe commented Apr 14, 2023

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.

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.

@vvb2060 vvb2060 added wontfix Not going to fix it not our issue This issue is caused by third-party like customized rom or module and removed not enough info Not enough info to fix stale No response for a long time labels Apr 14, 2023
@xiaofengjue
Copy link

hurt ,it's so hurt! (痛,太痛了!) here's what I suffered : https://www.cnblogs.com/sillage/p/17317928.html , it is so odd.

@Qleses
Copy link

Qleses commented Jul 28, 2023

Please any working help to resolve to 100% this bug?
I have Samsung Galaxy A22 5G, I don't have TWRP but I root and flash Magisk with Odin, I follow this steps:
https://forum.xda-developers.com/t/guide-to-root-galaxy-a22-5g-unlock-bootloader-and-flash-official-firmware-noob-friendly.4404371/

After installing Magisk, everytime when booting up the device (or rebooting), in less two minutes a message saids:
Bluetooth Agent Keeps Stopping
-App info
-Close app
Image: (https://i.ibb.co/8gf003n/1111111111111111111.jpg)

I only solved it with wipe data/factory reset. But after install Magisk the problem begins again.
Other solution like Seetings>Aplications, Show System apps>Bluetooth Agent, press Force stop aplication, and clear data and cache don't work for me.

@darkon12
Copy link

darkon12 commented Sep 30, 2023

Redmi Note 8 here.
What worked:
Boot TWRP 3.7.0
Wipe everything, format data.
Install rom.
Install magisk.zip
Setup OS
Install magisk.apk
Magisk working, blutooth working.
Reboot TWRP blutooth not working again (no issues with 3.6.2)

@Danstiv
Copy link

Danstiv commented Dec 21, 2023

Hi all.
I'm planning to switch to another firmware at the beginning of 2024, and I want to try to find the reason for the Bluetooth not working.
Does anyone have any initial ideas on where to look and if anyone would be interested in this?

@Danstiv
Copy link

Danstiv commented Jan 3, 2024

and I want to try to find the reason for the Bluetooth not working.

TeamWin/android_bootable_recovery#332 (comment)

su -> restorecon -R -F /data

It works.

@darkon12
Copy link

darkon12 commented Jan 4, 2024

F*** ME !!!
It worked !
Also works in adb shell BTW.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
not our issue This issue is caused by third-party like customized rom or module wontfix Not going to fix it
Projects
None yet
Development

No branches or pull requests