Everyone talks about the Pixel 5 as Google’s “smart” pivot away from spec wars. I see a phone that nails software but quietly underdelivers on the hardware fans were promised for years.
Battery Share: A Flagship Trick on a Non-Flagship Phone
Android 11’s first developer preview hid a pretty telling menu: a Pixel-branded Battery Share screen for reverse wireless charging. The activity name, com.google.android.settings.fuelgauge.batteryshare.BatteryShareTrampoline, wasn’t some generic AOSP stub — this was clearly built with Google hardware in mind.
The description was blunt: sharing your phone’s battery with “compatible ear buds, watches, phones, and more” would drain it faster. In other words, Samsung-style wireless power sharing, baked into Google’s own settings stack. That’s exactly what shipped on the Pixel 5: reverse wireless charging on a phone with a 4,080 mAh battery and 18W wired charging.
So yes, Google finally caught up to Samsung’s Wireless PowerShare and Huawei’s similar implementations. The problem is that when the rest of your hardware story is this conservative, Battery Share feels like a gimmick sprinkled on top of a phone that doesn’t really push anywhere else.
Android 11 on Pixel 5: Polished, Familiar, and Safely Boring
Where the Pixel 5 still earns its keep is software. It launches with Android 11 out of the box, straight from Google, no carrier bottlenecks. You get at least three years of major OS updates and security patches, which is still more than most Android OEMs reliably commit to.
The basics are what you’d expect from Pixel: the Google feed on the left-most home screen, app drawer via swipe up, and now App Suggestions bleeding into the dock. Clear a slot in the dock and Android 11 will drop in context-aware suggestions based on time, location, and usage. Handy, but not exactly significant.
The system UI tweaks are incremental but practical. The multitasking view loses app suggestions but adds quick Screenshot and Select buttons, letting you grab text or images for Google Lens directly from recent apps. The long-press power menu turns into a mini control hub, bundling power controls, Google Pay cards, an emergency shortcut, and quick access to smart home devices.
Notifications get a hierarchical clean-up: Conversations at the top, then general notifications, then Silent stuff like weather. Bubbles bring Messenger-style floating chats system-wide, though support is still spotty and buggy because developers need to opt in.
Media controls now live in a persistent Now Playing area at the top of the shade, with horizontal swiping between recent players and easy audio output switching. There’s also a Notification History page, off by default, for undoing those overzealous swipes.
Privacy is where Android 11 actually moves forward: permissions that expire if apps stay unused, and an “Ask every time” mode so you can stop giving blanket access forever. Plus, a built-in screen recorder, even if it’s barebones with no frame rate or resolution toggles.
Pixel-specific extras like the on-device Recorder app are still solid. You get automatic transcription without an internet connection and the ability to cut audio simply by deleting text blocks. It’s genuinely useful for students and journalists and still annoyingly Pixel-exclusive.
All of this is good. None of it justifies the corners cut elsewhere.
Snapdragon 765G: Tuned Down Until It Feels Like a 4a
This is where the Pixel 5 story falls apart. Google dropped Qualcomm’s 8-series entirely and went with the Snapdragon 765G, positioning the phone as a “well-rounded” upper-midrange 5G device instead of a raw performance flagship.
On paper, the 765G is fine: two Cortex-A76 performance cores at 2.4 GHz and 2.2 GHz, six Cortex-A55 efficiency cores at up to 1.8 GHz, and an Adreno 620 GPU that should be around 20% faster than the Pixel 4a’s Snapdragon 730G (Adreno 618). It brings the integrated X52 modem with both sub-6 GHz and, in some regions, mmWave 5G on a 7 nm node. Paired with 8 GB of LPDDR4X RAM, that should be more than enough to make Android 11 fly.
Except the Pixel 5 doesn’t perform like other 765G phones — it performs worse. In CPU-heavy Geekbench tests, single-core scores are where you’d expect, but multi-core results are weirdly low, sitting closer to the cheaper Pixel 4a with its 730G. AnTuTu, which looks at CPU, GPU, RAM, and storage, lands the Pixel 5 somewhere between the 4a and other 765G competitors.
Graphics benchmarks are even more embarrassing. Despite sharing the same resolution as the Pixel 4a, the Pixel 5 scores significantly lower in almost every on-screen and off-screen test. The only exception is a single 1440p off-screen Vulkan run in 3DMark Slingshot Extreme, where it merely ties the 4a. That’s not what you buy a 765G for.
We’re effectively looking at a chip that’s been detuned to behave closer to Snapdragon 720-class performance. The suspicion is obvious: Google wanted 5G and 7 nm efficiency but didn’t want the thermal and battery trade-offs of running the 765G at full tilt, so it quietly dialed it back.
Google later pushed an update that brings “performance optimizations in graphic intensive apps and games” to the Pixel 5 and Pixel 4a 5G, plus some camera improvements, VPN fixes, and UI tweaks. That’s welcome, but this should have shipped optimized from day one. Pixel phones have never chased benchmark crowns, but they’ve also never been this far behind similar silicon.
Camera: Ultrawide In, Telephoto Out, Software Still Doing Heavy Lifting
The other controversial shift is the camera loadout. The Pixel 4’s telephoto is gone, replaced by a 16 MP ultrawide with f/2.2 aperture and 1.0µm pixels. The main camera remains a 12.2 MP sensor with 1.4µm pixels and an f/1.7 lens plus OIS.
So instead of giving you a high-res main sensor that can crop cleanly for zoom, or a big sensor for better low light, Google is again leaning on software — computational photography to handle both zoom and night shots from relatively modest hardware. The 765G still can’t do 8K, but these Pixels finally support 4K60 video recording for the first time.
On the software side, Google Camera 8.0 debuted with the Pixel 5 and 4a 5G, bringing features like Storage Saver, Cinematic Pan, and Audio Zoom. Those later rolled out to older Pixels with version 8.1. Unsurprisingly, the modding community immediately pulled those features into non-Pixel devices.
PX Mod v8.1, based on Google Camera 8.1.008, crams a long list of tuning options into a single APK: color transforms for phones with washed-out saturation, toggles for tracking focus and motion photos, OPModes to fix EIS behavior, quick AWB buttons, and per-sensor AWB profiles (Pixel 2, Pixel 3, IMX586, IMX686). It even offers switches to disable Synthetic Fill Flash and auto Night Sight in portrait and photo modes. Arnova8G2’s newer build, based on GCam 8.1.101, extends support to more phones.
The catch: the devs openly say it may not work on some Samsung, OnePlus, and Snapdragon 845 devices. You can’t pretend this is some universal camera upgrade. It’s another example of Google’s best ideas leaking out via community workarounds rather than a coherent multi-device camera strategy.
Hardware Choices: 5G, Bigger Battery, and a Long List of Asterisks
On the surface, the Pixel 5 hardware story looks fine. A 6.0-inch 1080p+ OLED with 90 Hz refresh slots right between the old Pixel 4 and 4 XL sizes. The 4,080 mAh battery is a huge jump over the 4 XL’s 3,700 mAh pack, and together with the 7 nm 765G, endurance should be comfortably better.
The body is IP68-rated, made from recycled aluminum with a textured finish for grip and fewer fingerprints. Somehow, Google still managed to integrate both wireless charging and reverse wireless charging into that shell. Pixel Imprint — the rear fingerprint reader — is back, which makes more sense than face unlock in a world full of masks.
5G support is provided via the 765G’s X52 modem, with sub-6 GHz on all variants and mmWave reserved for certain markets. You do lose Wi‑Fi 6; the Pixel 5 is stuck on Wi‑Fi 5 (802.11ac), which is a strange omission for a $700 phone.
Storage is another mixed bag. Officially, you get 128 GB of UFS 2.1 with no expansion, and that’s it. Informal testing via Androbench suggests the underlying storage might actually behave like UFS 3.0 or 3.1, with sequential reads around 930 MB/s and writes around 408 MB/s, plus solid random IO numbers. That’s great in practice, but Google hasn’t confirmed anything, and 128 GB with no microSD is still limiting for a lot of users in 2026 standards.
Then there’s pricing: $700 / €630 / £599 with perks like free Bose QC 35 II headphones in select European markets for early pre-orders. That’s not ridiculous, but when the performance story is this compromised and Wi‑Fi 6 is missing, you’re not exactly getting flagship silicon for that money.
Meanwhile, the Pixel 4a 5G exists as a cheaper, bigger, slightly cut-down sibling with the same 765G, 6 GB of RAM instead of 8 GB, a 6.2-inch OLED at 60 Hz, and the same dual-camera combo. It keeps the 3.5 mm headphone jack the Pixel 5 dropped but skips wireless charging and IP rating, with a polycarbonate shell and a slightly smaller 3,885 mAh battery.
Google’s Pixel Strategy: Software First, Hardware Eventually?
Pull it all together and the pattern is obvious. Android 11 on the Pixel 5 is polished, the camera software remains ahead of most OEMs, and tiny touches like Recorder’s offline transcription and power menu device controls are genuinely useful.
But the compromises are piling up: a detuned Snapdragon 765G that can’t keep up with its own spec sheet, a camera hardware story that hasn’t meaningfully evolved in sensor tech, missing features like Wi‑Fi 6, and a storage configuration that feels stingy in 2026. Google is delivering a nice experience for casual users while quietly disappointing the enthusiasts who kept the Pixel brand relevant in the first place.
Yes, the April update helps with graphics-heavy apps and games. Yes, modded Google Camera ports keep spreading Pixel magic to other phones. None of that changes the fact that Google shipped a $700 phone that often performs like a cheaper midranger.
If this is Google’s new hardware direction — software first, performance later — it needs to start explaining that honestly instead of letting benchmarks and hidden menus tell the story.
Check back soon as this story develops.