Bluetooth issue


M

mateevici

Members
Apr 13, 2014
31
20
Hi everyone,

I've just noticed that the thread on the persistent Bluetooth issues (it doesn't reactivate once you disable it) has disappeared.
Does anyone know what happened there?
Did we get the moderators that mad at us that they erased it?
Or did the user that initiated it just erase it?

By the way, THE PROBLEM STILL EXISTS, even if you erase the thread.
 
I still have the bluetooth bug as well, since many versions back. Even erased everything and clean installed but nothing changed. When i disable bluetooth i cannot reactivate it until I reboot the phone. Always running xiaomi.eu stable since a year ago.
 
  • Like
Reactions: VinPe
mariosm1cy said:
I still have the bluetooth bug as well, since many versions back. Even erased everything and clean installed but nothing changed. When i disable bluetooth i cannot reactivate it until I reboot the phone. Always running xiaomi.eu stable since a year ago.
Click to expand...

I've had it since owning the phone...
On all stable versions of MIUI 10.
 
  • Like
Reactions: mariosm1cy
mateevici said:
I've had it since owning the phone...
On all stable versions of MIUI 10.
Click to expand...

yep, me too! No problems with Chinese versions of MIUI 10, on the other hand. Too bad the devs here resort to deleting the bug reports rather than trying to find the problem...
 
  • Like
Reactions: mariosm1cy
If you guys are really really desperate with the issue, and none of developers can reproduce given the steps (of course it's possible to happen, it doesn't happen to me as well), then give them a logcat containing logs when this issue happens. Otherwise, it's a valid move for the developers to consider the bug doesn't exist.
 
leledumbo said:
If you guys are really really desperate with the issue, and none of developers can reproduce given the steps (of course it's possible to happen, it doesn't happen to me as well), then give them a logcat containing logs when this issue happens. Otherwise, it's a valid move for the developers to consider the bug doesn't exist.
Click to expand...

A bug report is not a sign of desperation. And what if the error does occur with 100% reproducibility and it shows nothing in the logcat? In your logic this makes the bug disappear. Not in mine.
 
frofa said:
And what if the error does occur with 100% reproducibility and it shows nothing in the logcat? In your logic this makes the bug disappear. Not in mine.
Click to expand...
Rather than coming back to this useless debate again, how about generating that logcat? No logcat, no bug. It's a common rule in custom ROM world, by the way, if you haven't known already. Go check xda-developers custom ROM threads. You haven't even tried, how do you it won't show anything? I know it will log every single action that you (and every other entities inside) do, no exceptions. But if you prefer keep doing the same thing and get ignored forever (if the thread is not deleted again), go ahead. I'm just telling you an alternative way, knowing that yours is useless, the choice is fully yours.
 
leledumbo said:
Rather than coming back to this useless debate again, how about generating that logcat? No logcat, no bug. It's a common rule in custom ROM world, by the way, if you haven't known already. Go check xda-developers custom ROM threads. You haven't even tried, how do you it won't show anything? I know it will log every single action that you (and every other entities inside) do, no exceptions. But if you prefer keep doing the same thing and get ignored forever (if the thread is not deleted again), go ahead. I'm just telling you an alternative way, knowing that yours is useless, the choice is fully yours.
Click to expand...

Instead of extending this totally useless debate, why don't you just read what I said: the bug does not show up in the logcat. And now?
 
leledumbo said:
If you guys are really really desperate with the issue, and none of developers can reproduce given the steps (of course it's possible to happen, it doesn't happen to me as well), then give them a logcat containing logs when this issue happens. Otherwise, it's a valid move for the developers to consider the bug doesn't exist.
Click to expand...

Well, go and figure that I actually asked the developers whether they need a logcat.
Or, indeed what do they need.
And the answer that I got was: we don't have time to hold your hand and guide you to do anything.
So, there you go.
They don't seem to care enough to investigate nor to make a way to get the information they would need.
 
frofa said:
It is such a pain to discuss with people who have no clue what they're talking about. Then "goodbye" is actually the best option.
Click to expand...

This is, in a way, the same kind of reaction I got from the dev on the main thread...
 
no need, i dirty flashed from last xiaomi.eu oreo rom to the new pie version without any issues.
I only cleared dalvik and cache after flashing
 
Werner99 said:
no need, i dirty flashed from last xiaomi.eu oreo rom to the new pie version without any issues.
I only cleared dalvik and cache after flashing
Click to expand...
Thanks! I'll still wait for y'all to try it and give more feedback
 
You must log in or register to reply here.

Similar threads

D
Mi 10 pro - bluetooth problem
Replies
1
Views
2K
Xiaomi Mi 10/Pro /10Lite/Ultra/10T/Pro/Lite/10S
Doush_504
D
mnshawaty
  • Locked
Invalid Issue with System App Updates on HyperOs with Android 14
Replies
1
Views
8K
Bugs
gogocar62
gogocar62
J
Xiaomi 12S Pro Lock Screen Notifications Issue
Replies
1
Views
2K
Xiaomi 12 / 12X / Pro / 12S / Pro / Ultra / Lite
ChessMasher
C
L
New YouTube Video Lag Issue on Xiaomi 12x in Mobile Networks
Replies
2
Views
1K
Bugs
Likrante
L
K
New Face ID Attempt Counter Issue on Mi 11 Ultra Hyper OS 1.05
Replies
0
Views
530
Bugs
krstf98
K
Top Bottom
Back