Skip to main content

Google’s animation for ‘Battery Share’ in Android 11 DP3 tells us nothing new

We first told you about a new Settings pane called “Battery Share” in Android 11 back in mid-February. Today, in the 3rd Developer Preview of Android 11, Google added a nice animation to go along with the feature. It’s a nice animation. But it tells us nothing new of substance about Google’s plans for device-to-device wireless charging…

In February, we found a pretty clear description of what Battery Share is intended to do in the Settings app code, along with an accompanying image in Google’s usual four-color design. As it mentions, the feature is directly related to some future ability to “Charge other devices by placing them on the back of your Pixel”.

Charge other devices by placing them on the back of your Pixel

Your phone’s battery will run out faster when using battery share. Battery share works with compatible ear buds, watches, phones, and more.

Pretty straightforward. Clearly, Pixel 4 doesn’t support this feature despite supporting wireless charging, and it seems pretty unlikely that a feature like this would come to a phone many months after launch — even if it could. Also, hate to break it to you, but the Pixel 4a doesn’t have wireless charging at all. You won’t be Qi charging your Pixel 4a, much less charging other devices with it. I detailed that and everything else you need to know about Pixel 4a in my story earlier this month.

Enter the new animation that Google added with Developer Preview 3 today:

“So odd! That definitely looks like a Pixel 4, but there’s a fingerprint sensor! This must be a Pixel 4a then,” you might read on the internet. So is Pixel 4a going to support wireless charging after all? No, no it’s not.

Look, these animations do indeed tend to vaguely represent first-party Google products. We’ve seen this style art before, and that — plus the code that Kyle dug up a couple months ago — would strongly suggest that a future Google phone is going to support this “Battery Share” feature. But as we mentioned, the only evidence we have as to what device that might be goes by the codename “redfin”. That’s not the Pixel 4a’s codename — but it might be the Pixel 5’s.

So this animation, while a neat look at this future feature, tells us nothing new. These are generified (is that a word?) versions of existing Google phones. It’s a Pixel 4 design with a fingerprint sensor. That doesn’t exist. It will never exist. And the other phone, which doesn’t have a bezel, dates way back to an Android P beta from 2018. It doesn’t exist either. Even the Pixel Buds thing… yes, it’s meant to vaguely represent Google’s headphones. That’s it.

Moving on.

Thanks to JEB Decompiler, which this post and some APK Insight teardowns benefit from.

Dylan Roussel contributed to this article

FTC: We use income earning auto affiliate links. More.

You’re reading 9to5Google — experts who break news about Google and its surrounding ecosystem, day after day. Be sure to check out our homepage for all the latest news, and follow 9to5Google on Twitter, Facebook, and LinkedIn to stay in the loop. Don’t know where to start? Check out our exclusive stories, reviews, how-tos, and subscribe to our YouTube channel

Comments

Author

Avatar for Stephen Hall Stephen Hall

Stephen is Growth Director at 9to5. If you want to get in touch, follow me on Twitter. Or, email at stephen (at) 9to5mac (dot) com, or an encrypted email at hallstephenj (at) protonmail (dot) com.