The latest beta of Android 16 was supposed to fix a battery problem, but it seems to have made it worse. Several users are experiencing excessive energy consumption on their smartphones. Some even have to charge their device twice a day.
Beta versions of operating systems allow users to get early access to new features, but they are not without their flaws. Google recently rolled out Android 16 beta 2.1, which is supposed to fix several bugs, including a battery life issue introduced by the previous version. However, many testers report that this update has made the situation worse, with the battery draining even faster.
Since February 27, the release date of this update, reports have been multiplying on specialized forums. The problem would affect all Pixel smartphones compatible with the Android 16 beta. Some users claim that their battery life has dropped alarmingly, to the point where they have to charge their phone twice a day, even with moderate usage. For many, this situation makes daily use of their smartphone much more restrictive.
Android 16 beta 2.1 causes loss of battery life on Pixel
Feedback from testers confirms abnormal battery behavior. One user reports that his phone, unplugged at 9 a.m., only showed 63% battery after barely an hour and a half of screen time. Others experience rapid battery drain even in standby, meaning the smartphone continues to consume excessive energy even when not in use. This is particularly problematic for those who rely on their phone to last a full day without recharging.
This bug is all the more surprising since Android 16 is supposed to improve energy management. Google has adopted a new development approach, called "Trunk Stable", to stabilize its system more quickly and reduce bugs from the first versions. However, the beta 2.1 shows that adjustments are still necessary before the official release scheduled for June. While some users have noticed an improvement in autonomy with this update, update, others are still experiencing high battery drain.
Google will likely have to roll out a fix soon to resolve this issue before the stable release of Android 16. Similar issues have been fixed in the past via minor updates, which gives hope for a quick fix for affected users.
Source: android authority
0 Comments