Earlier this week, Android 13 was released, bringing with it a variety of upgrades to Bluetooth, Material You, security and privacy, and other areas. Although everything is excellent, it looks like some users’ ability to wirelessly charge their phones has been removed with the new update.
This week, several threads on Reddit have appeared with Google Pixel owners complaining that wireless charging stopped working practically right away following the Android 13 update. The Pixel 4 and Pixel 4 XL appear to be the most affected Pixel devices, while it also appears to affect the Pixel 6 series.
Whereas the sole reason for this problem is unknown, it appears that the software that controls charging on Pixel phones is the problem. The firmware may slow down or halt charging when using wireless charging (or wired, for that matter). For instance, if a Pixel phone has been plugged in or resting on a wireless charger for several days, Google automatically restricts charging at 80%.
Users who are experiencing this issue say that their phones either don’t respond to wireless chargers at all or only do so briefly before halting and showing a “not charging” message. According to reports, the problems with wireless charging began immediately after upgrading to Android 13, which was initially made available for Pixel phones on Monday.
Those who have been affected also say that this happens no matter what charger is being used. Many people have said that there are problems with both versions of the Pixel Stand, while others have said that there are problems with more than one charger. Some people say that changing settings like Adaptive Charging or “forgetting” a Pixel Stand can fix the problem, but that doesn’t seem to be the case based on what users have said so far.
Although numerous reports have been sent via Google’s Issue Tracker, it doesn’t appear like Google has officially noticed the issue. Owners of the Pixel 4 and Pixel 5 who experience this issue can roll back to Android 12. Owners of the Pixel 6 and Pixel 6 Pro, regrettably, lack that option.
Source :