this post was submitted on 23 Sep 2023
6 points (100.0% liked)

Ask Android

2200 readers
3 users here now

A place to ask your questions and seek help related to your Android device and the Android ecosystem.

Whether you're looking for app recommendations, phone buying advice, or want to explore rooting and tutorials, this is the place for you!

Rules
  1. Be descriptive: Help us help you by providing as many details as you can.
  2. Be patient: You're getting free help from Internet strangers, so you may have to wait for an answer.
  3. Be helpful: If someone asks you for more information, tell us what you can. If someone asks you for a screenshot, please provide one!
  4. Be nice: Treat others with respect, even if you don't agree with their advice. Accordingly, you should expect others to be nice to you as well. Report intentionally rude answers.
  5. No piracy: Sharing or discussing pirated content is strictly prohibited. Do not ask others for a paid app or about how to acquire one.
  6. No affiliate/marketing links: Posting affiliate links is not allowed.
  7. No URL shorteners: These can hide the true location of the page and lead people to malicious places.
  8. No lockscreen bypasses: Please do not comment, link, or assist with bypassing lock screens or factory reset protection.
  9. No cross-posting: Please take the time to make a proper post instead of cross-posting.
Other Communities

founded 1 year ago
MODERATORS
 

My device is Redmi Note 10 Pro running Crdroid 7.19 (Android 11). I have always had problems with Bluetooth randomly disconnecting, but this used to happen like once a couple weeks.

But today my device went crazy. For the last 8 or so hours it's been repeatedly turning bluetooth on and off and every so often showing a "bluetooth keeps stopping" error.

  • I tried clearing cache and data for the Bluetooth app.
  • I cleared cache and dalvik in TWRP.
  • I rebooted plenty of times.
  • I tried changing AVRCP and MAP versions in Developer options

Nothing helped

This is the error log

What can I do?

you are viewing a single comment's thread
view the rest of the comments
[–] nudnyekscentryk@szmer.info 1 points 1 year ago* (last edited 1 year ago) (1 children)

I did, they were unable to replicate the issue and noone ever reported this. This didn't occur in other roms though.

also, I never used the stock rom. Unlocked and re-flashed the day I bought the device.

edit: the only similar reports were for Pixel 3a's running stock rom

[–] limerod@reddthat.com 1 points 1 year ago (1 children)

I see. Then, there's not much we can do. This is one of those difficult to reproduce bugs, I guess. Relevant xkcd: https://xkcd.com/583/

[–] nudnyekscentryk@szmer.info 1 points 1 year ago

lol, good one.

anyway, it's irreproducability was why I was hoping to ask wider audience than users of this particular rom