Comment 9 for bug 1879582

Revision history for this message
FelipeAF (felipealexandref) wrote :

well, i had done both tests (redmi in other laptop and same laptop with another phone), and the result was quite confusing. Seems the bug occurs with the combination of ubuntu+redmi

1 - Testing Redmi In an old laptop Lenovo G470, autoconnection (after turn phone on again) not works at all (just as in my acer, on status blinks when i turn phone on, but it immediately change to off again). Manual connection fails kind of 50% of times, in a different way than in my acer (here it keeps loading for some seconds and then fail, while in acer it just become of immediactly).
2 - In MS Windows, in the same lenovo laptop (i had tested just for discard a hardware problem), redmi works fine both, manual and auto connection (also in my android tablet and android phone).
3 - With an old and cheap bluetooth phone, called "fitphone", in my acer, works both, auto-connection after turn phone on and manual connection in gnome.

I had noticed that when i try to manual connect in my acer, i get in btmon a status "bluetoothd: connect error: Device or resource busy", while in lenovo, the fails status are
When lenovo auto-connection blinks, it printed in btmon: "= bluetoothd: connect error: Operation already in progress" (while it's not)