WhatsApp Audio STOPS at 30 seconds

[usereo7WBB12pT]

I have a Galaxy S23. For some time now, at least with the last two updates, I have noticed that when I listen to WhatsApp voice messages that are longer than 30 seconds and put the phone to my ear, the screen turns on and the audio stops after 30 seconds.

I have also tried in Galaxy S24 and same issue.

I am not the only one with this problem.

Will Samsung fix this issue?

[Takirega]

Same exact problem here with my Samsung Galaxy s23 ultra. Come on Samsung! We need support here. It isnt so difficult to fix.

[danpfaria]

I had the same problem with galaxy M52 and now with s24 ultra.

[eas4u]

Hi All,

I'm using a Note 10+ phone, and its updates stopped a while ago. I'm also facing the same issue on my phone. After checking online, I found that mostly Samsung users are encountering this problem. However, I don’t think this issue is related to the OS update since updates for my phone model stopped a while ago. Like many other Samsung users have complained, Samsung needs to work with WhatsApp to resolve this, as it is already clear that only Samsung users are facing this issue.

[bazzofelipe]

Exactly the same here. S23 Ultra. Very annoying 🤦🏻

[Shahnawaz Siddiqui]

I'm experiencing the same issue on my S24 Ultra after the UI update. I'm not sure who is responsible for fixing this problem, Samsung or WhatsApp, but it needs to be resolved as soon as possible. It's really frustrating to have the audio messages keep stopping repeatedly.

[KABarnard]

press the power button to lock the screen while you're listening and it works. it is not a Samsung issue but a whatsapp issue that is not compatible with certain android phones due to Meta update.

[usereo7WBB12pT]

No, it does not happen in any other mobile phones, except Samsung. Its clearly a Samsung error.

Embarrassing error, I would say

[JL01]

Once I lock the screen, the whatsapp audio stopped playing. Is there some other settings which I need to enable? S24 user here

[c3k]

In last WhatsApp beta the problem is finally fixed

[usereo7WBB12pT]

Anyone else can confirm this?