mtts0
mtts0
Same exact problem here using a Samsung device—Android 11 with OneUI 3.1. The problem happens using either the stable version of the app or the beta. When I bring the...
> We are working on it. We had a fix that was hopeful to go out into the next beta but it required us to target Android 12 directly which...
Ok, @greyson-signal. It is not respectful and polite to supporters and donors that such a simple issue takes more than 6 months to be solved. Seems that no one cares.
Ok @greyson-signal, I hope the issue gets solved. All the best for you and the team. And I am sorry if I was too aggressive.
> I really hope your are joking. "Sometimes we prioritize things differently than you". This bug is there for more than 4,5 years! Check: https://github.com/signalapp/Signal-Android/issues/7576 But hey! Now we have...
> Hi, one of our devs just got their hands on an A51 and is able to reproduce, and will be looking into this issue. Looks like the issue is...
> downloaded the latest beta (6.2.1) I updated earlier today to 6.2.0 and it is still working. I just checked and now there is this 6.2.1 available and I will...
> I updated earlier today to 6.2.0 and it is still working. Updated to version 6.2.1 (Beta) on a Samsung Galaxy device (Android 12, OneUI 4.1) and listening to voice...
> But while it is playing noiseless and the earpiece is triggered, it will start playing from the main speaker again. Either for a short period of time or completely....