Google unlocks secret pixelsnap firmware for non-pixel phones

Google just admitted its magnetic Pixelsnap Charger ages like milk if you don’t feed it code, and until yesterday everyone without a Pixel was left holding the bottle.

The company slipped a web updater into mobile Chrome that lets any android 16+ phone push firmware to the puck over USB-C, ending an exclusivity that quietly stranded Galaxy and iPhone users on slower, less-efficient charge cycles.

Qi2 moves fast; accessories have to sprint

Qi2, the open MagSafe clone that Google bet on last fall, is still a moving target. Each revision tightens the magnetic alignment algorithm, trims heat output and negotiates higher sustained wattage. The Pixelsnap ships on version 1.51.0 today, but engineers inside the android Partner Track say three more drops are already in dog-food testing, including one that unlocks 18 W for foldables.

Pixels have been swallowing those patches transparently; the handset pulls the blob in the background and flashes the charger during the next bedside dock. Non-Pixel Qi2 phones never got that pipeline, so their Pixelsnap units have been stuck on whatever firmware left the factory. The delta is not cosmetic: early adopters on Reddit measured 2.4 W lower average output and a 7 °C hotter coil after three months of skipped updates.

A web app that refuses desktops

A web app that refuses desktops

The fix lives at g.co/pixelsnap/update, but Google crippled it on purpose: the page throws a 403 unless the user-agent string screams “mobile Chrome”. Plug the puck into a MacBook and you get a terse “use your phone”. The restriction is classic Google—half pragmatism, half petulance. On one hand, forcing USB-C sideload dodges the firmware-crypto hell that desktop browsers impose; on the other, it reeks of a company that still sees the open web as a Pixel marketing funnel.

Once the cable handshake passes, the site surfaces a single button: “Update to 1.51.0”. Tap it and the phone reboots the charger into EDL mode, flashes 1.3 MB of binary in 14 seconds, then spits you back to the home screen. No progress bar, no checksum, no changelog beyond a cryptic “stability improvements” line that has already spawned a 200-post XDA thread.

Google’s accessory empire steps outside the pixel garden

Google’s accessory empire steps outside the pixel garden

The quiet release signals a strategic pivot. Inside Alphabet, hardware margins live or die on scale; locking the coolest Qi2 puck to 3 % of the android base was a recipe for shelf-warmers. By opening the firmware tap, Google turns every Pixelsnap into a Trojan horse inside Samsung and Apple households, harvesting nightly telemetry on charge curves, battery health and thermal budgets from rivals’ flagships.

That data feed feeds directly into the next-gen Nest Hub wireless-charging base, sources tell TechBloom, a 30 W coil array that will launch alongside the rumored Tensor G5 foldable this winter. The message is clear: Google no longer wants to sell you a phone first and an accessory second. It wants the charger on your nightstand before you even pick an ecosystem.

Still, the rollout is vintage Google—equal parts generosity and afterthought. No push notification nudged users, no Play service pop-up warned that their coils were obsolete. Most owners will never know the page exists, and the mobile-only hurdle guarantees that. But for the tinkerers who caught the Reddit whisper, the Pixelsnap just became the first Google gadget that doesn’t care whose logo glows on the back of your phone. And in a walled-garden industry, that tiny crack in the fence feels almost radical.