Samsung Galaxy S10, S10+ users complain of battery issues after WhatsApp, Messenger callshttps://indianexpress.com/article/technology/mobile-tabs/samsung-galaxy-s10-s10-users-facing-battery-issues-after-making-whatsapp-facebook-messenger-calls-5643624/

Samsung Galaxy S10, S10+ users complain of battery issues after WhatsApp, Messenger calls

Users say that after a Galaxy S10 makes a call using any of these apps a bug prevents the device from entering deep sleep mode .

Samsung, Samsung Galaxy S10, Samsung Galaxy S10 battery issue, Samsung Galaxy S10 battery, Samsung Galaxy S10 problem, Samsung Galaxy S10 issue, Samsung Galaxy S10 bug, Samsung Galaxy S10 whatsapp call, Samsung Galaxy S10 facebook call
After using a VoIP based service to make a call, their device was found to have a severe battery drain issue when the device was in idle mode.

Samsung Galaxy S10 and Galaxy S10+ users have been complaining on XDA Developer forums and Reddit about a bug that they say is affecting handsets powered by Exynos 9820 chipsets. The users say that the issue emerges only after they use a VoIP (Voice over Internet Protocol) services via apps like WhatsApp, Facebook Messenger and Viber for the first time. The issue isn’t affecting units powered by Qualcomm Snapdragon 855 processors.

According to users, after using a VoIP based service to make a call, the battery of the device drains despite the phone idling.

The users say that the problem pops up due to a bug that prevents the device from entering deep sleep mode when the phone is on standby. This, they say, affects battery life a lot. The users claim the bug is being triggered by the proximity sensor staying on, and not allowing the phone to enter deep sleep.

Samsung launched its new Galaxy S10 lineup of smartphones including the Galaxy S10, Galaxy S10e and Galaxy S10+ earlier this month.

Advertising

Also Read: Samsung Galaxy S10 5G to be available on April 5: Report

Samsung is yet to issue a statement regarding the alleged bug, what is causing it and when they plan on pushing a fix for it.

Some users have stated on the forums that they were able to solve the issue by restarting the affected device. However, some users said the fix is not working for their handsets.