Google Pixel 11 Pro XL buyers expecting a lightning-fast morning routine will face a delay. Independent testing reveals a software bug that prevents the phone from reaching its maximum charging speed. This issue adds five minutes to the time required to charge the device to 75 percent. Users relying on the advertised 30-minute benchmark for quick top-ups should adjust their expectations.
Software bug delays extreme charging mode activation
The device lists for $1,299 USD (around $1,299) and supports up to 45 watts of USB-C charging. Google claims this speed matches the previous Pixel 10 Pro XL on paper. However, real-world performance diverges from the marketing materials due to the activation delay of the extreme charging mode. The phone requires a specific USB-C Power Delivery charger capable of 21 volts and 2 amps to unlock this capability.
- Max Charging Power: 45 watts
- Tested Initial Power: 40.7 watts
- Full Charge Time: 69 minutes
- Charger Requirement: USB-C Power Delivery at 21 volts and 2 amps
Tests by Android Authority show the phone charges at 40.7 watts at the start of the process. This initial power level drops after nine minutes as the software issue interferes with the extreme charging mode. The widespread bug delays the activation of this high-speed feature, causing the charging curve to flatten earlier than intended. This technical limitation explains the discrepancy between the theoretical maximum and the observed performance.
A full charge took 69 minutes in the test environment. This duration is 12 minutes faster than the previous Pixel 10 Pro XL model. Despite the software hiccup, the Pixel 11 Pro XL still offers a meaningful speed improvement over its predecessor. We looked at Pixel 11 Pro XL Ties earlier while tracking Google launches.
The confirmed specifications highlight a faster baseline charge time despite the current software constraint. The extreme charging mode remains dependent on specific hardware and a pending software fix. Buyers should anticipate the 69-minute full charge time until the bug is resolved.
Source: NotebookCheck

Discussion
0 comments