This would be really devastating. Dear mudita team / @urszula: these are really the things that make me distance myself from the brand. The story I make up is that the company prioritizes shiny marketable features over providing users with actually usable things or alternatively that the team is just lacking sufficient technical expertise to fix this - both scenarios that make me look long term for another company for such an important device as a phone. I just hope that this is somehow a misunderstanding and also that the same does not apply for the even worse pocket dialing and pocket settings bugs.
Iām shocked if they really didnāt fix this after ~3 months. Hoping thatās not the case, because itās really frustrating to see them tinkering with chess and meditation apps (?!?) while there are such significant issues with basic functionality and commonly used apps like SMS, keyboard, calendar etc
@brendxn & @tilmanbergt Thank you so much for your feedback. I have passed it on to our team. Weāre sorry that this wasnāt fixed in this update & that youāre disappointed, however, our team has confirmed that it will be included in the 1.3.0 update.
@urszula Iām hoping this doesnāt mean weāll have to wait until September update for such a basic bug to be fixed.
Overall Iāve been able to solve my issues with other software. Iāve been able to solve this too, but itās very annoying to have to go to a different app connect my earphones then be able to listen to something.
I gotta ask, are any of your devs using this phone daily? The change logs is filled with vague fixes like āenhancedā and āimprovedā, but a super bug that was reported since the first days of this device release is not fixed.
This shouldnāt have been a bug at all, the dialog to manage previously connected devices is part of AOSP by default, why itās been removed and not caught during testing before the device release or during testing of this update Iāll never know.
I will ask the team to give me some approximations, and if anything has changed when it comes to the timeline, but I think it might be September.
yes, please do: and also bring it into the discussion to differentiate between feature releases and bug fix releases. It feels not right to have quite serious bugs to sit there for (another) 2 months, but I would fully understand to just do a small bug fix release in august with the most serious problems addressed.
I only learned of this workaround just yesterday. Yes, a bit disappointed that BT wasnāt a highest priority fix for this SW release, but I am happy to have BT headphones working again.
This definitely is the most frustrating one out of the remaining bugs. In my case even the suggested workaround doesnāt seem to work. Simply having the option to āforget deviceā would allow me to re-pair the headphones every time, which would still be annoying, but at least it would work. Now Iād basically have to factory reset the phone to get my headphones connectedā¦
I donāt know if this helps, in case you have brand name headphones/earphones they should have a companion app thatās available in AuroraStore.
That way I am able to connect mine. Itās very annoying, I have to enter the Nothing app everytime I want to listen something.
Oh yeah thatās a great point, Iāll try that. Thanks @gezimos!
Our team has assured me that this is getting fixed & will be included in the next update- 1.3.0
@urszula : I really respect the work you are doing and the team is doing. But to be direct: how can I take such a statement to mean anything. It was exactly what you reported earlier before this very release. Also it is unclear what exactly you mean with āthisā and with āfixā. It might mean: somehow something will change around bluetooth. Again: this really is not meant to deprecate your work or the teams work, but is meant to give you a very concrete example of where I see the current communication to users as leading naturally to misunderstanding and disappointment down the road. What I would expect is: a concrete statement, e.g.: the team plans to make available a list of connected devices on screen x and give users the option to delete them etc. This would be meaningful and would allow us to tell, if this would remove the pain we are having. As mentioned elsewhere such statements would be collected in a concrete list of planned bugfixes.
@urszula
I am also very disappointed that the bug was not fixed! Bluetooth connectivity is very important for a lot of people and it exists over 25 years now. So whatever the issue is, there must be a common solution already existing. Ideally there would have been a hot-fix for this issue soon after it popped up. It should not come with version 1.3.0 but with 1.2.1.
Honestly I do not care about the Mudita apps and their updates. I would like that the features of the OS are stable. If an app, e.g. maps or whatever, is not running smoothly I may get an alternative for it.
I agree, this was intended to be fixed in 1.2.0.
The fact that is wasnāt and prevents a basic functionality should mean it alone gets a hotfix in 1.2.1.
So we will have to wait until September to use our headphones?
Can there be some clarification as to why we canāt get a hot fix before then?
I wonder if something was indeed done to the bug since after a new connection my headphones do connect quite consistently. Will keep testing!
@tilmanbergt Iām sorry to read about your disappointment, however, as you know, I pass on the info which is given to me. Itās unfortunate that the team was not able to fit in this fix into this update, and I really apologize for this. I always try to ask for as much info as I can from our team, but as you see, I donāt always get the info you are looking for or expecting.
yes, I fully get it and I do not blame you. And as I have worked on many software projects and software companies as agile coach I fully understand how hard it is paticularly when just launching a new product to keep all threads together. So while I may sound a bit harsh I really hope you understand it menat to support you. What I make up about the situation is that the company and the development team might not realize how important your role is and how much customers value having you as a well informed partner. And while keeping you well informed and trying to explain seeming technicalities to you seems taking time away from developing actual solution it might often be very well invested times. So that is my fantasy about Mudita :-). Anyway I pray you keep up the engaged work with us and your team!
Is there a software fix for this? can i enter a command line into my phoneās terminal?
No fix with commands I tried to find the bluetooth dialog history with adb, not able to access it. They have removed it, I couldnāt find it with activity launcher either.
What you can do is:
- Use that bluetooth viewer app somebody linked above (users reported it works)
- Use bluetooth widget app from aurora store (users reported it works).
Or do what I do, install the companion app of my earphones in this case Nothing app. And that way Iām able to reconnect.