With the Google Pixel 3 and Pixel 3 XL, the internet services and hardware giant has finally implemented wireless charging on its phones. Not just that, the Google Pixel 3 series was launched alongside the company’s accompanying wireless charging device, called the Pixel Stand. Priced at $79 (around Rs 5,800), the Pixel Stand also enabled fast wireless charging at 10W for the Google Pixel 3 and Pixel 3 XL. Also Read - UEFA Euro 2020: Colourful Google Doodle kicks off European Football ChampionshipAlso Read - Android 12 beta 2 rolling out: New privacy features, tweaked design and more
However, considering that the Google Pixel 3 range uses the popular Qi wireless charging standard, the phones can be charged with any compatible wireless charger. A wide variety of brands manufacture and sell these, including options from Belkin, Anker and more. Unfortunately, it now appears that while the Pixel phones can charge at 10W with the Pixel Stand, charging is limited to just 5W with third-party wireless chargers. Also Read - Sundar Pichai: 5 interesting facts about Google CEO you never heard before
Various reports suggest that while the Pixel 3 range shows ‘charging rapidly’ even with third-party wireless chargers, the actual charging is rather slow and takes much longer than would be expected. While one reason for this could be safety, it seems more likely that Google is doing this to discourage the use of other products while effectively pressuring users to buy its own Pixel Stand if they want truly fast wireless charging. Other brands including Apple and Samsung also have their own wireless charging products, but do not limit functionality on compatible third-party chargers.
WATCH: Google Pixel 3 XL Hands On
While the safety argument might be valid in many cases, a lot of brands can be trusted to build secure and safe products. Brands such as Belkin and Anker have options that allow up to 10W wireless charging, but these would be effectively curtailed in function with the new Pixel devices. It remains to be seen if Google will issue a software-based fix to this issue.