aekit I just shared a workaround for those who feel comfortable using it. I understand that not every casual user may prefer this approach, and you’ve raised a valid point. For now, we’ll have to wait for future software updates for the Phone (2) to resolve this issue. Many users have expressed this concern, and my suggestion at this time is to continue providing feedback on a large scale to ensure it’s recognized as a top priority for the software team to address.
Our CBO, @RohitPakalapati is also aware of the concern and he would hopefully get it highlighted in the next board meeting if left unresolved.
