Here’s how Google is making it easier to move from ChatGPT to Gemini


The Gemini logo on an Android phone.

Joe Maring / Android Authority

TL;DR

  • Google is making it easier to switch from a competing chatbot to Gemini in two ways.
  • You’ll be able to transfer user information from the other chatbot to Gemini by using a prompt and following a few extra steps.
  • Chats can also be imported, but they’ll need to be saved in a zip file that’s no larger than 5GB.

The more a chatbot knows about you, the better it gets at offering relevant responses. However, the more you use one AI service, the less likely you are to try out the other options. Who wants to spend all of that time training multiple chatbots? We learned back in February that Google is working on a solution that should make switching to Gemini from a competing chatbot less of a headache. Now we have more information on how the solution will work.

Our investigation into the Google app (version 17.11.54.sa.arm64) has revealed that there are two parts to this solution: import memory and import chats. Starting with the import memory option, you’ll be able to transfer user information from other platforms to Gemini.

When selecting the “Import memory to Gemini” option, you’ll be asked to copy a prompt and paste it into the input box of the other provider. The other provider will then give you a response with whatever it knows about you. You can then copy that response and paste it in the “Paste the response here” box within the Import memory to Gemini page. Tapping the “Add memory” button will tell Gemini to remember the following about you.

In the screenshots above, you can see an example of this process. The prompt provided by Gemini is pasted into ChatGPT and the response from ChatGPT is copied and pasted into paste here box on the Import memory to Gemini page. After tapping on Add memory, you’ll see the following response confirming that Gemini has stored the information into its own memory.

Don’t want to miss the best from Android Authority?

google preferred source badge light@2xgoogle preferred source badge dark@2x

As reported last month, Google is making it possible to import chats from other platforms to Gemini. This will require you to download your conversations from the other AI client and upload them to Google’s service.

Through our APK teardown, we’ve learned that you’ll need to store those chats in a zip file before uploading. You’ll also need to make sure the file isn’t too big, as there will be a 5GB limit.

⚠️ An APK teardown helps predict features that may arrive on a service in the future based on work-in-progress code. However, it is possible that such predicted features may not make it to a public release.

Thank you for being part of our community. Read our Comment Policy before posting.

New Google Photos RAW backup workflow looks ready to go


Google Pixel RAW and JPEG capture option

Hadlee Simons / Android Authority

TL;DR

  • Google Photos backs up RAW images alongside JPGs, which takes a lot of cloud storage.
  • Earlier this year we found evidence for a new system that would store RAW images separately and not back them up.
  • We’re now finally able to see this in action, and there’s even a toggle to opt in to backing up RAWs if you’ve got the space.

If you care even a little about photography, you probably know all about RAW images. While JPGs are convenient to post and share due to their relatively small file sizes, RAW files don’t just capture an image without lots of lossy compression, but they store camera sensor data before things like white balance are corrected, giving you tons of power to control what your final output will look like, even with the photo already taken. Despite all that potential, though, they’re not without their problems, and we’ve been keeping an eye on one in particular concerning how Android handles them.

One of the biggest consequences of storing RAW photos is their large file size, and that was a problem if you were shooting in both RAW + JPG and wanted to back up your pics in the cloud — Photos would try to store the huge RAW files alongside your JPGs, eating up tons of storage space. Back in March, though, we uncovered evidence that Google was finally working to change how RAW backups worked, possibly storing RAW images in a separate folder and no longer backing them up by default.

Don’t want to miss the best from Android Authority?

google preferred source badge light@2xgoogle preferred source badge dark@2x

That certainly sounded good… we just never saw it actually happen. But now, months and months later, we’re finally starting to see some more progress.

None of this is still publicly available, but with version 7.52.0.825653635 of Google Photos for Android, we’re now able to get the app to support RAW photos in a different directory. Once this is working for everyone, your JPGs will continue to show up in the same /DCIM/Camera directory where they’ve always been saved. But with this enabled, RAW pics are saved in /Pictures/Raw instead.

You won’t see those at all when normally browsing your photos, and to specifically look at your RAW pics you’ll have to navigate over to the Collection that includes them. When you do, you’ll find a special option for letting you still choose to back these up (if you’ve got space to spare):

photos raw backup

AssembleDebug / Android Authority

That all makes us think that we could finally be getting close to the point where Google flips the switch and makes this functionality available to everyone. Certainly, the major pieces appear to now be in place, and it’s really up to Google to push “go” on this long-overdue feature.

That’s the big progress we’ve spotted in this update, but we’ve also identified a small UI tweak that Google appears to be working on for Photos:

Rather than these big animated pics showing off all the Create tools, we’ve been able to call up a much more compact UI that replaces those with some more low-key iconography. Like the new RAW changes, it’s anyone’s guess when Google might push this one live, too.

⚠️ An APK teardown helps predict features that may arrive on a service in the future based on work-in-progress code. However, it is possible that such predicted features may not make it to a public release.

Thank you for being part of our community. Read our Comment Policy before posting.

Is the Galaxy XR really an Apple Vision Pro killer?


00:00 – Mishaal Rahman: We may have finally figured out why the Pixel 10 has bad battery life, at least for some users.

00:04 – C. Scott Brown: And we finally have an Android alternative to the Apple Vision Pro.

00:08 – Mishaal Rahman: I’m Mishaal Rahman.

00:10 – C. Scott Brown: And I’m C. Scott Brown and this is the Authority Insights Podcast where we break down the latest news and leaks surrounding the Android operating system.

00:18 – Mishaal Rahman: Google announced Android XR, its XR focused operating system way back in December of last year and they promised at the time that we would get some real hardware from Samsung by the end of this year.

And finally, after many months of waiting, we finally have the official launch of the Project Moohan headset now known as Galaxy XR from Samsung. And you can now finally buy it. You can literally walk into a Samsung store or order it online from Samsung. But should you buy it?

00:46 – C. Scott Brown: And should you buy the Pixel 10 given the battery problems that some people are having?

We have seen some erratic reports of battery life as far as the Pixel 10 goes, but we finally got some data from testing that we did here at Android Authority and found out that the battery issues that people are facing might be hardware related, which of course is not great because that means you’re not going to see it get better and better as software goes or software updates come in.

01:13 – C. Scott Brown: But to Google’s credit, their hardware decisions have proven advantageous in other areas. Besides all the unique AI features that you only find on Pixel phones, it turns out that Pixels are actually the best phones for running desktop Linux apps.

01:29 – Mishaal Rahman: That’s pretty exciting, but we’re still years away from actually realizing those efforts of running desktop Linux apps on Android phones in an actually performant way and actually turning our Android phones into proper PCs.

But today right now, we are also seeing the promise of XR coming to Android devices become a reality.
Google finally and Samsung and Qualcomm, they all came together, made this big splash last year, but now they have finally unveiled the feature, the hardware they’ve been teasing for many months now, the Project Moohan, Samsung Galaxy XR device.

02:05 – Mishaal Rahman: And Scott, you got to use it for a more than extended period of time two weeks ago at the time of this recording, but it was a week before the launch. I only briefly got it for about five minutes at Google IO, so I did not get the full experience of what you can do with the Samsung Galaxy XR.

I want to ask you, what are your initial thoughts on it? Starting with the comfort aspect. How did it feel to actually wear the Moohan?

02:31 – C. Scott Brown: It was very comfortable, much more comfortable than other XR headsets that I’ve worn in the past. A big part of that is because of probably one of the more controversial aspects of it, which is that the battery pack is attached to a cable, which is then you can just hold the battery pack.
Like the Vision Pro from Apple, you can put the battery pack in your pocket, you can rest it on the chair next to you while you’re using the headset, but the battery pack being separate from the headset reduces the weight considerably.

02:59 – C. Scott Brown: The weight on my head was much more comfortable than other headsets that I’ve used including the Meta Quest, which the battery pack is built into the headset itself.

03:10 – Mishaal Rahman: Do you think that’s still the right trade-off? Cause it is 150 grams lighter than the Apple Vision Pro. Do you think they could have gotten away with stuffing a battery onto the headset itself or do you think this is an acceptable trade-off?

03:23 – C. Scott Brown: I think it’s an acceptable trade-off. The one thing that’s weird to me is that since the battery pack is separate from the headset, the battery pack could be literally any capacity that they want. Within limits, you wouldn’t want it to be this massive boulder in your house, but the battery pack is basically the size of a smartphone. It’s about that big and maybe that thick, but they could have made it that thick and that big, and then made it so the battery lasted longer.

As of right now, according to what Samsung is telling us, you can get about two hours of use out of one single charge. And they’re positioning this as being a device that you can use to consume immersive content which would include feature length films. I don’t know if you’ve been to the movies recently, but there are lots of movies out there that are much longer than two hours.

It being separate from the headset doesn’t weird me out at all. The fact that the battery pack is as small as it is, that’s what weirds me out because you could have made this any size you wanted. And there’s no ability to buy extra battery packs, at least nothing that we’ve seen yet. That might be something that comes down the road, but you get the one battery pack in the headset box and then that’s it. So you’re in the middle of your movie, getting towards the end of the third act, battery runs out, you got to pause and charge it up and then finish your movie and that just makes no sense to me. Even three hours, very few movies break the three-hour mark by this point. If they pushed it just a little bit to get you those three hours, I feel it would have been much better, but I don’t know.

05:01 – Mishaal Rahman: If they could push it to three hours, that would be nice. But what will you actually be doing for those three hours, besides watching movies? Watching movies is a great use case, but I don’t think anyone wants to spend $1800 for the Galaxy XR or $3500 for an Apple Vision Pro just to watch movies on it. I think they want to do a lot more than that.

So what are some of the killer features that you’ve seen personally while you were using the headset?

05:21 – C. Scott Brown: The coolest feature, the feature that made me be, whoa, is Google Maps. Most people listening to this know about Street View. You can navigate through a city or pretty much any location from a street level view. And you can walk around, quote-unquote, walk around with the headset on in Street View. It’s like using Street View on your phone except that it’s immersive. It’s all around you.
So you really feel you are in whatever location that you’ve gone to.

At the same time, you can pull back and you can see the city or the town or wherever you are from a bird’s eye view and soar over it like a superhero, getting a real lay of the land. It would be really beneficial, I think for people who are traveling to a place and want to see what does this city layout look like and they can just see it. All around you, you just turn your head and you’re just, oh yeah, there’s this and there’s that. But then you can get even further in and you can actually explore the interiors of locations.

And the way Google does this is it uses AI to stitch together various bits of media that’s created by the public and then uploaded to Google Maps. For example, you can take a picture in a restaurant and then they’ll take that photo and then hundreds or possibly even thousands of other photos for those locations and stitch together a 3D model of what it would look like to actually be in that restaurant. So there are thousands of places around the world that support this already and a thousand of them are already in New York. You could just go and check out a restaurant. It could be beneficial in a lot of ways. You could go inside a restaurant, quote-unquote and see that there’s only 10 tables in this restaurant. I better make a reservation here because those 10 tables are probably going to fill up fast. Or they have this really beautiful outdoor patio space. When I make my reservation, I want to make sure I get one of those seats.
I’m going to ask for those specifically. Lots of cool things that you could do that would be you could do in Google Maps on the web or on your phone or whatever, but it’s just going to be so much easier and more immersive to do it on the headset.

That was the one feature that I walked away from being, this is really cool. This is something that’s very different, something that I’ve never seen before on a headset. Everything else though was pretty much stuff that I had already done on a headset.

07:50 – Mishaal Rahman: One thing that Google says differentiates Galaxy XR and the underlying XR platform from other platforms we’ve seen before is that they say that Android XR is the first version of Android that was built from the ground up with generative AI in the fold. They included Gemini throughout the operating system.

So did you actually get that feeling when you were using it? Did you feel this is really they’re actually making full use of Gemini. It’s not just a tacked on chatbot, but it’s actually integrated throughout and there’s actually some unique things you can do with it. What are some of the things you can do that you can’t do without XR plus Gemini?

08:26 – C. Scott Brown: The one thing that they showed us that showed that Gemini was actually integrated into the operating system was organizing your windows. If you have your Chrome browser and your Instagram feed or whatever, a bunch of windows open in your virtual environment and it’s all messy, you can just ask Gemini to organize them for you and all of a sudden it’ll just flip all the, it’ll grid it all and make it all look all organized. This is something that’s operating system level. This is not something that you can do in Android. You couldn’t ask Gemini to rearrange the icons on your home screen. It won’t do that.

Everything else I saw though were things that you can pretty much do with your phone or tablet such as tell me about what I’m looking at using what would be Gemini Live. You’d be sharing your screen with Gemini and you’d be looking at a YouTube video or whatever and Gemini would be able to tell you, you’re looking at such and such a thing. Those were all things that I’ve done before. But it did prove, Google did prove that it is baked into the operating system itself.

How much more you can do besides just organizing windows, I don’t know. I only had 20 to 30 minutes with the device. I wasn’t able to do all the testing that I’d want to do, but it is baked into the operating system deeper than it is on a phone, but how far that goes, I won’t know until we actually get a review unit and I get to spend multiple hours with it.

09:55 – Mishaal Rahman: Hopefully Android Authority will be getting a review unit. I don’t know if that’s been confirmed yet, but at the moment, would you consider paying $1800 for this headset? Has it been something that has crossed your mind at the moment?

10:12 – C. Scott Brown: I don’t think so. And the core reason why is because the controllers don’t come with it. It’s $250 more to get the controllers. So you break the $2,000 mark by including the controllers with it. And that’s just a lot of money for that particular device. And the reason why I would want the controllers is because I would want a do-it-all headset. I would want the headset that I use to play my VR games that I already own through Steam or wherever. And I want to use it for the games that would be better suited to having controllers within the VR world, such as if I decide I want to play a 2D game, a game that was designed for the 2D world, but in my VR headset blown up to epic proportions, that 2D game is going to rely on a controller.

Yes, I could connect my existing controllers. I could grab an Xbox controller or a DualSense controller and hook it up that way, but the VR experience, you want the VR controllers. The fact that it doesn’t come with those means that this is not out of the box a do-it-all device. You have to buy those controllers if you want to play all the games that already exist. And there wasn’t enough shown to me that made me think that $1800 for not playing all the VR games would be enough.

Now, granted, once again, I had let’s say 30 minutes with this device. Maybe there’s killer features in there. Maybe there’s really cool things coming down the pipeline that are going to make it so that $1800 would be worth it. But right now, having used it as much as I have, having seen it and worn it, no, I would not spend $1800 on it.

11:55 – Mishaal Rahman: Me personally, there was a brief moment the night it came out where I was tempted to actually pull the plug and buy it because one of my friends, he’s a big VR guy. He immediately bought it. He buys all the VR stuff. He still has the Apple Vision Pro. I don’t think he uses it that often, but he has it. He has the Meta Quest. He has the Ray-Bans, he has everything. But I was considering buying it, but then I stopped to think, what made me pull the plug on that idea was initially when I went to go buy prescription inserts, I kept getting an error with the checkout.

First of all, I couldn’t even find the link to buy the prescription inserts from Samsung’s website. They just told you to go to this third-party website and then buy from there, but it was nowhere on the website.
But eventually someone found a direct link to the product listing. I tried to check it out, but it kept telling me my prescription was invalid. To keep re-entering it. So then I just gave up from there.

And then, I later spent some time thinking about it some more and then I thought, what is the thing I would use this the most for? And I would say probably working in a virtual space, productivity purposes, working with an infinite canvas. But the thing is, I do most of my work on a Windows PC. Android is still not where I think it should be when it comes to actually doing proper desktop-like computing.

You do have a bigger canvas, of course with this XR device. You can run Chrome in a desktop-like interface, but it’s not the desktop version of Chrome with extensions and all the desktop kind of behaviors that you come to expect. I would bet our CMS, our content management system at Android Authority just would not work very well just it didn’t really work very well the last time I tried it on Android tablet, so I wouldn’t expect it to work well on this blown up version of Chrome on an XR device. When I was looking at the list of apps that are available for Android XR, the one I was most excited by was Virtual Desktop.
And the reason being because I can use my Windows PC. I can extend my Windows computer to my XR headset. And that made me stop to think why am I getting this thing? If I’m just going to use it as an extension for my Windows PC, what is the point of that?

14:03 – C. Scott Brown: And remember, you only have two hours because you got one battery pack, you have two hours. That’s not a full work day. That’s a quarter of a work day. Or for you, that’s probably an eighth of a work day. For everyone listening, Mishaal is a very hard worker. He works a lot.

14:24 – Mishaal Rahman: I don’t game. I haven’t really played games as often as I used to. I mostly play on the Switch. So I don’t really have any VR I don’t have a catalog of VR games to try. I would love to try some VR games. I know there’s I’ve seen a lot of good demos of Horizon for the PS5. Resident Evil 7 and 8. Those looked amazing. I tried them at my friend’s place. I would love to play Half-Life: Alyx, but how many of these games there’s already so few VR games that are available. There’s not that many VR games that you can actually play. How many of them are even available of that limited set would work on the Android XR headset and that is another concern that I had.

15:05 – C. Scott Brown: You can connect your Steam, you can connect Steam to the headset.
So anything that’s on Steam will work. But you’re going to face other things. You mentioned the Horizon game. I’m a huge Horizon fan. Horizon’s probably my favorite video game franchise. You cannot play that without the PS headset. That’s an exclusive to the PlayStation headset. And then, you mentioned Resident Evil. There’s a Resident Evil 4 remake, the original Resident Evil 4 that was remade for VR environments and that’s exclusive to Meta Quest. There’s a lot of exclusives out there that you’re still not going to be able to play without owning the specific headsets.

It’s just like the console wars. If you decide you want to go with a PlayStation instead of a PC, you’re going to miss out on a lot of stuff. And if you decide to go to a PC without a PlayStation, you’re going to miss out on a lot of stuff there. The idea of having to own two headsets or technically three headsets to play all the games that you just talked about is nuts.

I think that the headset has a promising future. The real question is, and this is something that we’ve talked about quite a few times already, is will Google stick with this? The Apple Vision Pro without a doubt is a sales dud. Apple couldn’t sell a million of them. And this is Apple we’re talking about. Apple’s bread and butter is coming into existing markets, disrupting it, and claiming that they invented it. It’s a meme at this point that’s what Apple does. Apple’s claiming, we invented VR.

That’s a joke that we’ve said a million times over the past 20 years. And even Apple couldn’t do that with the VR or XR, let’s call it XR space. Google and Samsung are now trying coming in second fiddle to Apple. Is it going to work? And if it doesn’t work, what’s Google going to do? Is it going to pull a Stadia and just say, see you guys, we’re done or is it going to stick with it? I don’t know.

17:15 – Mishaal Rahman: I think there’s a lot of disadvantages that Google is playing on the back foot as you mentioned, Meta and Apple especially have had a head start compared to Google. But I think one key difference between Meta Horizon and Apple Vision Pro and Android XR is that Android is starting out as a platform, not an ecosystem. Sure, it’s a platform and an ecosystem, but Meta’s Quest was just an ecosystem, not a platform. It later evolved to become a platform with Meta opening up Horizon the Horizon operating system to other manufacturers, but it didn’t start out that way.

And the same thing with Apple Vision Pro. Apple is not giving away Vision OS to other manufacturers, right? It’s just the Apple ecosystem. But Google is coming out the gate offering Android XR as a platform that other companies can build off of, right? It’s not just Samsung that is making XR products. We’ve already heard Xreal, for example, is one big name that’s said that they confirmed they’re working on devices. Albeit they’re working on glasses, not actual full on VR headsets.

But it’s a platform, which means potentially imagine in the future if Nintendo decided to make a dedicated VR, just imagine. It’s not going to happen, but just imagine if they did. And imagine if they put the amount of production value that the folks at the people that the team behind that new Digimon game put into their new Pokemon game. And imagine if they released that new VR Pokemon game for a Nintendo Android XR powered headset. Just imagine. That thing will fly off the shelves. I would buy one in a heartbeat. What about you?

18:49 – C. Scott Brown: So the headline of my hands-on is just the opening act, a Galaxy XR just the opening act. And the reason that I said that is that they Samsung and Google and Qualcomm partnered together on this, but they didn’t want to talk about this. The keynote made it clear that they are not as excited about the Galaxy XR as they are about what comes after the Galaxy XR. They were already hyping that they have partnerships with Warby Parker and Gentle Monster to make smart glasses. They were already hyping the demos that they’ve done for smart glasses in general based on the Android XR operating system. They know that the Apple Vision Pro was a sales failure. They know that the Meta Ray-Bans are getting more successful every year. Google can see the writing on the wall and know that the success of the Android XR platform is not going to be based around headsets, but it’s going to be based around smart glasses.

The whole launch was just so weird feeling because it was the only launch I think I’ve ever been to where the companies on stage were, this is just the beginning. This is only going to get better with the next products that we’re coming down with. It’s just so weird. It’s even they didn’t want to say, you should buy this. They were basically, you should wait until the next cool thing comes along. It was a very strange, very strange experience, but I think that we’re just going to have to wait and see how this all plays out. I hope you’re right and I hope that Google sticks with this because this could be the next future. Everybody’s saying that wearables are going to be the next big smartphone, the best next big smartphone replacement. Maybe not replacement, but augmentation.

And if Google can make it so that it’s at the forefront of that, that would be awesome, but Google also has a really short attention span, if things don’t immediately work, it just moves on to the next thing. So, let’s see how this goes.

21:03 – Mishaal Rahman: One thing I would like to point out is you actually wrote an article titled “Samsung’s new XR headset is secretly a Pixel” because as you pointed out, it doesn’t even say Samsung anywhere on the headset itself. When I read this I thought –

21:18 – C. Scott Brown: It says it on the battery pack. That’s the only place you can see Samsung.

21:21 – Mishaal Rahman: It says it on the battery pack. So there is Samsung somewhere on it. But when I was reading this article that you wrote, I was thinking the Galaxy XR sounds like it’s a Nexus device. It has Google everything, Google software, Google applications, basically the stock version of Android XR, but it’s made by Samsung, manufactured by Samsung, designed by them.

That was exactly basically what the Nexus program was. You had a whole bunch of Nexus devices. None of them were designed or manufactured by Google, but Google made the software for them. And it sounds like what this device is to me. If this particular device doesn’t succeed, maybe some other manufacturer down the line will release a $500 Meta Quest killer that runs Android XR, maybe that one will succeed.
Hopefully Google hasn’t invested too much on the success of this particular device and if a future Android XR device happens to kick off, then that’ll actually kick start the excitement around Android XR.

22:16 – C. Scott Brown: That would be exciting to me. I would be very into that, but I don’t even know… but Google, but history. I just don’t know what’s going to happen. I don’t see this being a success. I do not see the Galaxy XR as being successful. I see it as being something like the Vision Pro. People are going to buy it, they’re going to be super excited about it for a week or two, and then they’re going to return it in droves or it’s going to go into a drawer and collect dust. That’s what I see happening here. And I just hope that that sudden drop in excitement and interest doesn’t kill Google’s momentum. Hopefully the smart glasses are going to be enough to keep Google riding that wave, but I just don’t know. I don’t know.

23:12 – Mishaal Rahman: Hopefully they stick to it long enough to see the long-term benefits of it because the same thing, a lot was said, a lot of similar things to when Google switched to its own custom designed Tensor chipsets in its Pixel phone. For a long time they were using Qualcomm Snapdragon chips and then with the Pixel 6, they switched to its own custom silicon, the Tensor G1 chipset. And at the time, there was a lot said about it, long-term, this is going to be good for Google. It’s going to be good for Google Pixel smartphones.

But in the short term, people were complaining about the modem not being very good, performance not being very good. And we still have those complaints, but I think have died down recently. They’re not as bad, things are not as bad as they used to be in terms of performance and connectivity.

23:52 – C. Scott Brown: Not on my channel.

23:56 – Mishaal Rahman: There are still people complaining about these issues on Pixel smartphones and with the Pixel 10 in particular, we’ve heard a lot of complaints about battery life on the Pixel 10 series.

24:06 – Mishaal Rahman: Our Rob Triggs, he’s one of our smartest analysts. He did a deep dive into trying to understand why the Pixel 10 seems to have bad battery life in particular. And you actually recently published a video that basically recapped it. So why don’t I just ask you what exactly did Rob find in his research?

24:26 – C. Scott Brown: Rob found that he compared the Pixel 9 Pro XL, the Pixel 10 Pro XL, and the Galaxy S25 Ultra and he did it across a variety of testing, including low performance tasks, mid-performance tasks, and heavy tasks.

And for the low tasks, he noticed that the three phones were pretty much the same. If you just have your phone idling with the screen on or screen off and you have it connected to Wi-Fi or connected to cellular, they all pretty much performed the same as far as the power consumption of the phones in that state.

When he upped it to mid-level tasks such as web browsing or being on a zoom call, he did notice that the Pixels both consumed more power than the Galaxy, but the difference between how much they consumed on Wi-Fi and how much they consumed on cellular were pretty comparable. Even though the Pixels were higher, the difference between those two scenarios was the same across all three phones.

But when he did high level tasks such as downloading a huge file or buffering a 1080p YouTube video, that’s when he noticed that Tensor did really poorly. Not only did Tensor do really poorly, but there were huge differences when on Wi-Fi and when on cellular.

The most confusing thing was that the Pixel 10 did worse than the Pixel 9 in those scenarios. It’s a multi-front problem. You have a huge disparity between the amount of power draw a Pixel uses when it’s on Wi-Fi compared to when it’s on cellular. The heavier the task, the worse it gets and the Pixel 10 is actually worse than the Pixel 9. Google has a real problem here as far as making sure battery life really doesn’t become a huge problem on the Pixel 10 series.

26:32 – Mishaal Rahman: It feels like we’ve been hearing again and again about a variety of battery problems on Pixel phones. We’ve had the unfortunate battery swelling issues on the 6A, the 7A and I think the 4A also it seems an A series specific problem where you have these batteries having issues keeping their health long-term. They start to swell up and become spicy pillows.

And now we have these battery draining problems on Tensor Pixels. And mostly not due to the batteries themselves, but just because of the inefficiency of the chipset itself. I’m surprised to see that the Pixel 10 is performing worse than the Pixel 9 from what I can tell, the modem didn’t really change, right? Doesn’t it have the same modem?

27:14 – C. Scott Brown: It has the exact same modem. So, it comes down to the efficiency of the chipset or possibly software, but the software should be pretty much the same across the devices, so I really don’t understand why the Pixel 10 would be worse than the Pixel 9 when it comes to the battery life efficiency of the modem.

27:33 – C. Scott Brown: And to be clear, we reached out to Google with this data. Rob reached out and said, here’s all this data. He emailed them, he showed them the data and said, what do you have to say about this? And we waited a few days, we got zero response. So we don’t really know. We have no real idea why this is happening. We know what is happening and we know directly when it happens poorly and when it doesn’t.

The low-level tasks are pretty much fine, but it’s only when you start doing that high-level stuff that things start being problematic. But it is good to know because if you do own a Pixel device, whether that’s a Pixel 9 or a Pixel 10, if you’re concerned about conserving your battery life, try to prevent doing high-level tasks on a cellular connection while you’re on battery. If you have a big file to download, try and wait until you get to Wi-Fi to do it and you’re going to make your battery last longer than it would if you download that over cellular.

28:42 – C. Scott Brown: I know that’s not ideal. Most people would just ask, why do I have to do that?
And also to be clear, this problem happens on the Galaxy S25 Ultra as well. It’s just not as bad. So if you have a Galaxy S25 Ultra and you start watching YouTube or start downloading a big file, you’re going to see a much bigger battery drain than you would if you did it on Wi-Fi. This is not something that’s just a Pixel problem. It’s just that it’s worse on Pixels and it’s worse on the Pixel 10 than it was on the Pixel 9. So I just want to make sure that’s clear for anybody listening.

29:12 – Mishaal Rahman: If it’s true that it is worse on Tensor-powered Pixel phones, why should Pixel fans put up with it? Why should Pixel fans continue to use Pixel devices when they have worse processors? And this is the frustration we’re seeing from Pixel fans who are asking, is it worth getting Google’s software and in exchange having to deal with the inefficiencies and the poor performance and poor emulation performance, poor Windows gaming performance, just poor gaming performance in general compared to Snapdragon-powered devices, is it worth having those trade-offs?

And we see a lot of people very vocal about it saying, no, it’s not worth a tradeoff. I think Google should switch back to Snapdragon products for the future devices. But you argue that actually Google shouldn’t, they should continue to use their own custom Tensor chipsets and want to ask you, you wrote this article last month and it got a lot of engagement, a lot of people were upset with your take on this. So I want you to defend why you think Google should continue going the path they’re going right now with the Tensor chipset?

30:20 – C. Scott Brown: I’ll address that question, but I want to point something out, which is that the article on Android Authority got 130 comments or something like that. And almost all of them were profoundly negative. Some of them were actually attacks. They were, you’re an idiot.

On my channel, on my YouTube channel, I published the video which makes the same argument and in the same way and gives the same defenses, and I got a lot of positive comments. A lot of people saying benchmarks don’t matter. I have no need for a Snapdragon processor in my Pixel. I’m totally happy with my Pixel as it is, etc. So always remember that the Android Authority audience is very, very passionate about these specific things. And the general user isn’t.

And that’s the core idea of why I think Tensor should stick around. Why I think Google should stick with Tensor is because it presents a different choice that most people will be fine with. Even going back to the data we were just talking about with the Pixel 10 series, most people are not downloading a gigabyte file on cellular. My dad has never done that before in his life because there’s no reason for him to do that. That’s just not something he does.

You mentioned emulation. 90% of people who own smartphones have never emulated a game ever. We tend to think that the Android Authority audience is the world, but it’s not, it’s the niche. And I think that’s the core argument that I tried to make in the video and in the article is that for most people and when I say most, I mean 90% of smartphone users, Tensor is great. It does everything they need it to do. The battery life is good, the amount of cool features that you can do on Tensor that you can’t do on other phones makes it a worthwhile expenditure for most people.

It’s the Android Authority audience that forgets that they are the niche. And I think that that’s number one, the ability to do these things and that makes it good for just your regular average smartphone user. And the second thing that I really think is important for Google to stick with Tensor is because it presents a choice, it presents competition. Think about it right now, of all the phones that come out in the United States, how many of them are running a Qualcomm Snapdragon processor of some kind. I have no idea what the number is, but it wouldn’t surprise me if it’s 95% of Android smartphones. That’s not good.

That gives Qualcomm tons of power over the market. The Snapdragon 8 Elite Gen 5, I have no idea how much it costs for a company to use it, but I do know for a fact that it is the most expensive mobile processor that you can buy to put into your phone.

That’s a ton of power in Qualcomm’s hands over the smartphone prices that you are going to pay for your phone. Not having competition, not having Tensor, not having MediaTek, not having phones that don’t use the Snapdragon 8 Elite Gen 5, makes that worse.

I think Tensor should stick around. Yes, it’s not as good as the Snapdragon 8 Elite Gen 5. You will hear no argument from me saying that it is better. By all metrics, it is worse, by all, battery life, power, everything.

33:59 – Mishaal Rahman: Not all metrics because this is a perfect segue to our next story because there is one particular area right now where Qualcomm Snapdragon chipsets completely fail at and that’s Linux emulation because as I’ve talked about before on the show, Google’s been working on this new Linux Terminal feature that allows you to basically run full desktop Linux apps on your Android phone.
And we’ve shown you can run apps GIMP, LibreOffice and other and even the desktop version of Chromium in a virtual machine on your Android phone.

But I say Android phone, but in reality, I mean specifically Android phones that support the Android Virtualization Framework for one and support unprotected virtual machines, which is a requirement to use the Linux Terminal feature.

And unfortunately, there’s not a single Qualcomm Snapdragon chip that supports this feature. Every Snapdragon chip including the new 8 Elite Gen 5 does not support the Linux Terminal because they do not support the unprotected or the non-protected virtual machine feature, which is a requirement.

And when I verified this and I reached out to Qualcomm, they said their “priority is to deliver technology that meets the evolving needs of our OEM partners and their end consumers, and as the Android ecosystem continues to expand its virtualization use cases we remain poised to support emerging requirements including non-secure use cases like the Linux Terminal, should market demand arise.”

35:18 – Mishaal Rahman: Basically they’re saying that they think this feature is not important enough right now to support when every other chipset manufacturer supports it. You have Tensor supports it, MediaTek supports it, Samsung Exynos supports it. It’s only Qualcomm that doesn’t support it. And it is a niche feature right now. It’s true that there’s really not much you can do with the Linux Terminal right now. But will that be the case five, six years from now when Android on PCs has hopefully long been launched by then and you have powerful Android PCs with next-generation chipsets capable of running full-fledged Linux apps in a virtual machine.

I’m guessing the Linux virtualization will be significantly more advanced by then and you’ll be able to run apps with near native if not entirely native levels of performance. And at that point, there’ll be a lot of things you can do with a non-Snapdragon chipset that you can’t do with a Snapdragon chipset and it’s because of this decision not to support the Linux terminal feature.

And I see this is disappointing because sure, something is niche right now. It’s not very good right now, but many manufacturers are selling phones with promises of supporting devices for seven years now, right?
If you don’t support display output, for example, on a smartphone, it’s not a big deal right now because Android desktop mode sucks right now. It’s still a work in progress. But six years from now, will it still be as bad as it is right now? I don’t think so, especially because Google’s putting so much effort into building up its desktop experience.

I think this is a disappointment and I think this is one of the rare cases where the Tensor chipset actually has a dub over Snapdragon chipsets and take that in stride Pixel fans. You’ve got a W right there.

37:01 – C. Scott Brown: I have a question for you. Is this something that could be fixed? Is this something that Qualcomm could just give a software patch to OEMs and those OEMs can push out that software patch that would enable this feature or is this hardware locked?

37:15 – Mishaal Rahman: They could fix it because Qualcomm chips do support the Android Virtualization Framework and they do support protected virtual machines.

They just don’t support the non-protected version of it, which if you support virtualization in general, you support all the requirements to support AVF and you support protected VMs, I don’t see any reason why Qualcomm couldn’t push out a firmware update to add support for the non-protected version of it.

It would just be something that they would have to work with OEMs to actually get the update out to users.
I don’t know how long it would take for them to push out an update and how long it would take for that update to actually arrive on consumer devices, but it should be possible for them to do.

37:56 – C. Scott Brown: I agree that it’s weird that they didn’t just include this because you said, all their competitors do. I’m assuming it’s a security thing. Qualcomm probably is, well, there’s no need for this to be available and it could potentially present a security risk at some point. So we’re just going to shut it down.

And then, you said, if a need arises and they decide there is a very good reason now and there’s a public demand for this feature, we’ll figure out a way to issue it later on. I could see where Qualcomm’s coming from there, but I also see that it seems like an excessive amount of restrictiveness for no real reason.

38:42 – Mishaal Rahman: I think it is a little short sighted considering Google is placing such importance on this feature. They think this is one of the features, this is one of the most important features for the Android on PC transition because right now, if you have a Chromebook, if you want to, for example, run Android Studio on it, you want to develop Android apps on it as a developer, you want to access a lot of development tools.

They’re not natively available for Chrome OS, but they are available for a variety of Linux distributions.
So on Chrome OS, you can just boot up a Linux virtual machine and then install whatever application you want from there, including Android Studio, which is how Google officially offers its development environment to Chromebook users.

And Steam, for example, that’s also another big feature that’s enabled through the Linux virtualization environment on Chromebooks. If you want to play Steam games, you have to install Linux and that’s only made possible because Chrome OS has this Linux environment. But right now there’s no such capability on the Android side of things to run Steam games, but who’s to say that won’t be a possibility down the line?

Google even did hint that they want to work with partners to enable gaming through the Linux VM on Android devices. And that would be I think a big deal, if they’re able to bring, for example, work with Valve on bringing Proton, which is a compatibility layer that the Steam Deck uses because the Steam deck is also Linux based. It doesn’t run Windows. But it does have the advantage that it has an x86 processor, not an ARM processor. So there’s less work involved in getting a lot of those games to run.

But if Valve, for example, wants to switch to a future Steam Deck with an arm chip, then maybe they might improve compatibility for that translation layer with ARM processors, which in turn would theoretically benefit Android devices in the future because Google is working on improving Linux compatibility. And then if you are able to port that Proton to the Linux VM, then Android games, Android phones in the future could theoretically run Steam games, which I think would be a big deal.

And that’s why I see Qualcomm’s decision is disappointing because this feature is basically just future proofing devices. Right now, there’s not many phones you could take, hook up to a PC and actually use it as a proper PC. But five years down the line with Android on PCs becoming a much more mature platform and the Linux feature becoming much more powerful, I could see that happening.

41:01 – C. Scott Brown: And it’s also a little incongruous because at Snapdragon Summit this year, Rick Osterloh came out on stage with with Cristiano Amon and they talked directly about the future of Android on PCs and Cristiano said something along the lines of, I’ve seen it and it’s amazing, get excited or something like that.

And for the company then to launch their chip without the ability to do these things, it does seem a little incongruous, but I don’t know. Qualcomm also named its processor the Snapdragon 8 Elite Gen 5. So, sometimes they just make silly decisions.

41:42 – Mishaal Rahman: And that’s everything we’ve got for you this week. You can find links to all the stories mentioned in this episode down in the show notes and you can find more amazing stories to read over on androidauthority.com.

41:52 – C. Scott Brown: Thanks for listening to the Authority Insights Podcast. We publish every week on YouTube, Spotify, and other podcast platforms. You can follow us everywhere on social media @AndroidAuthority and you can follow me personally on Instagram, Bluesky and at my own YouTube channel @CScottBrown.

42:08 – Mishaal Rahman: As for me, I’m on most social media platforms posting day in and day out about Android. If you want to keep up with the latest news on Android, follow me on X, Threads, Mastodon or Telegram @MishaalRahman.

One UI 8.5 all but confirms S26 Ultra’s new Private Display feature


A side view of someone holding the Samsung Galaxy S25 Ultra.

Joe Maring / Android Authority

TL;DR

  • Code within leaked One UI 8.5 build suggests Samsung is developing a new “Private Display” or “Privacy Display” feature.
  • This feature will limit screen visibility from side angles, protecting privacy in crowded public places.
  • It’s likely to debut on the Galaxy S26 Ultra, which is rumored to have the necessary screen hardware.

Per previous leaks, the Galaxy S26 Ultra is rumored to sport “Flex Magic Pixel” technology on its screen. Samsung Display had previously announced this tech, which uses AI to “adjust” a screen’s pixels to control viewing angles so that the screen is not easily visible to the person next to you.

We’ve now spotted code within the alleged One UI 8.5 builds that sheds some more light on this feature. It could be branded as “Private Display” or “Privacy Display,” as both terms have been used interchangeably.

Code

<string name="sec_privacy_display_title">Privacy display</string>
<string name="sec_privacy_display_summary">Limits screen visibility from side angles to protect your privacy in public.</string>

As the feature description notes, the Privacy Display/Private Display feature will limit screen visiblity from side angles to protect user privacy in public.

Code

<string name="sec_privacy_display_auto_privacy_summary">Automatically use Private display when you use sensitive apps and when you’re in crowed places.</string>

Ignoring the spelling errors in the various strings, we learn from the strings that when the setting is enabled, the Private Display feature will automatically kick in when users use sensitive apps in crowded places.

Code

<string name="sec_privacy_display_manual_settings">Manual settings</string>
<string name="sec_privacy_display_maximum_privacy">Maximum privacy</string>
<string name="sec_privacy_display_maximum_privacy_summary">For even stronger privacy protection, make the screen dimmer than usual while Private dislay is on.</string>

Code also suggests that there could be two types of privacy levels that users can choose from:

  • Maximum Privacy: For even stronger privacy protection, make the screen dimmer than usual while Private display is on
  • Manual Settings

It’s not immediately clear what settings will come under manual settings.

Don’t want to miss the best from Android Authority?

We’ve spotted code for custom conditions, too, and these may be included in manual settings to give users more control over when the feature works.

Code

<string name="sec_privacy_display_custom_conditions">Custom conditions</string>
<string name="sec_privacy_display_custom_conditions_apps_summary">Choose specific apps where you want to use Private display.</string>
<string name="sec_privacy_display_custom_conditions_apps_title">Apps</string>
<string name="sec_privacy_display_custom_conditions_schedule_summary">Set a schedule when you want to use Private display.</string>
<string name="sec_privacy_display_custom_conditions_schedule_add_button">Add schedule</string>

These strings suggest that users can set up custom conditions for the Private Display feature. They will be able to choose specific apps that the feature would activate on (like your specific banking or messaging apps), and even set a schedule for it.

Samsung has not yet announced the Private Display feature, nor has it mentioned or given any details about the next One UI 8.5 release. Given that the Private Display feature does have some hardware requirements, namely Samsung Display’s Flex Magic Pixel technology, it may remain limited to newer devices, like the Galaxy S26 Ultra, as per leaks.

Leaks also suggest that One UI x.5 updates will debut with Galaxy S-series flagships, where they will likely debut new UI/UX, AI features, and software enhancements, so it’s fair to presume that we will get One UI 8.5 with the Galaxy S26 series in early 2026. We’ll keep you updated when we learn more.

⚠️ An APK teardown helps predict features that may arrive on a service in the future based on work-in-progress code. However, it is possible that such predicted features may not make it to a public release.

Thank you for being part of our community. Read our Comment Policy before posting.

Android 16 QPR1’s source code is nowhere to be found, but Google swears it’s coming


Android figures standing around Pixel phone with AOSP home page showing

Mishaal Rahman / Android Authority

TL;DR

  • Google has delayed releasing the source code for Android 16 QPR1, worrying custom ROM developers who rely on timely AOSP (Android Open Source Project) updates.
  • While Google typically publishes source code within 48 hours of a new release, it has been a week, breaking a long-standing precedent for the community.
  • Google confirmed the code is coming “in the coming weeks,” but the situation has reignited concerns about the company’s commitment to open-sourcing Android.

Last week, Google rolled out the Android 16 QPR1 update, bringing the company’s long-awaited Material 3 Expressive design overhaul and other exciting features to Pixel users. If you want to try new Android features but don’t own a Pixel device, your best option is usually to install a custom ROM based on the open-source version of the operating system. Google typically publishes the source code for new Android versions within 1-2 days of release, allowing independent developers to quickly start porting the new changes to their custom ROMs. That hasn’t happened this time, though, leaving many developers to wonder if Google’s history of timely open source releases is over.

AOSP, short for the Android Open Source Project, is an operating system Google releases under the permissive Apache 2.0 License, which allows anyone to use, modify, and distribute their own AOSP-based operating systems without paying fees or releasing their modified source code. This licensing structure is what allowed Android to become so popular, but it’s also why the OS looks so different across devices. The software experience only feels familiar across most smartphones, tablets, watches, and TVs running Android because companies must follow certain guidelines to get access to Google Mobile Services (GMS) — Google’s suite of proprietary apps that includes the Play Store.

Even if your company doesn’t license GMS, you can still build your own operating system from AOSP. The source code is freely available under the Apache 2.0 license, and Google regularly publishes new code to AOSP shortly after releasing a new Android version. Within hours of rolling out a new quarterly or major release to its Pixel devices, Google typically begins uploading the corresponding source code to AOSP. This process usually takes 24-48 hours due to the codebase’s size and complexity.

It’s been a week since Google released Android 16 QPR1, and there are no signs that the company has even begun to upload its source code. Normally, a minor delay wouldn’t be a cause for concern; perhaps the team responsible for AOSP releases is understaffed, or maybe there’s another complication. However, given recent changes to AOSP, developers are understandably concerned this delay is intentional. They’re worried about the impact these delays could have on their projects, as users have grown accustomed to fast turnarounds following a new Android release.

We reached out to Google a few days ago for comment on whether and when it plans to release the source code for Android 16 QPR1. In a statement to Android Authority, Google confirmed it will release the source code “in the coming weeks.” The company didn’t explain the reason for the delay or offer a more specific timeline, but its statement reassures developers that the code is coming — just later than usual.

Why are developers concerned about AOSP?

LineageOS Logo (2 of 3)

C. Scott Brown / Android Authority

Although AOSP is open source, nearly all of its development happens privately, with Google contributing the bulk of the code. Google used to develop some parts of Android in public, but it fully privatized development earlier this year to simplify its workflow. Aware that this would spark concern, Google told Android Authority that it remained committed to publishing Android’s source code.

This commitment was tested when Google released Android 16 back in June. While the company did publish the operating system’s source code, it dealt a huge blow to the Pixel custom ROM community by omitting code for Pixel-specific hardware features. This omission, while not affecting the core OS, fueled speculation that Google was planning to discontinue AOSP. In response to the outcry, Google’s VP and GM of Android Platform, Seang Chau, posted on X, stating that “AOSP is NOT going away.”

Google denies discontinuing AOSP

Mishaal Rahman / Android Authority

Though some skepticism remained, that statement from Google’s VP quelled most doubts at the time. However, the delayed release of security patch backports, coupled with the lack of source code for Android 16 QPR1, has reignited concerns about the company’s commitment to AOSP. If these delays become the new norm, the custom ROM community will have to adjust its release schedules accordingly. We asked Google whether to expect delays for future releases or if this is a one-time issue, and we’ll update this article when we hear back.

Don’t want to miss the best from Android Authority?

Thank you for being part of our community. Read our Comment Policy before posting.

Google Maps may make it easier to recall the places you visited (APK teardown)


google maps go search place

Rita El Khoury / Android Authority

TL;DR

  • The You tab in Google Maps has a new section called “Your recent places.”
  • This section shows a list of all the recent places you visited.
  • You can sort through locations with various types of filters, save a location, share a location, and delete a location from your history.

Having trouble remembering the store you went to a few days ago? Or maybe you want to share the location of a restaurant you ate at the other day. Google Maps is getting a feature that will show all the places you recently visited in one place.

When you tap on the You tab in Google Maps, you’ll see a section called Your lists, which contains various lists like Friends, Favorites, Saved trips, and so on. While exploring the app’s version 25.34.00.796159725, we discovered that a new section has been added above the Your lists section. This new section is called “Your recent places.”

Don’t want to miss the best from Android Authority?

As the title suggests, the Your recent places section will show you a list of all the places you visited recently. Above that list sits a carousel of filters, including Area, Category, Saved, and Maps history. Each of these filters provides multiple ways to filter. For example, when you tap on Category, you’ll see options to filter by Food & drink, Culture, Shopping, Attractions, and Hotels.

Off to the right of each listed location, you’ll see a Bookmark icon and a three-dot menu. As you can probably guess, Bookmark allows you to save a location to a list. Meanwhile, the vertical three dots open up a menu where you can share that location, see visits and Maps history, or delete a location from your history.

This new You tab section isn’t the only new feature we found hiding in Google Maps recently. We also learned that Google is working on something to make it easier to share a list of search results with others.

⚠️ An APK teardown helps predict features that may arrive on a service in the future based on work-in-progress code. However, it is possible that such predicted features may not make it to a public release.

Thank you for being part of our community. Read our Comment Policy before posting.

The Pixel Watch 3 is the first Android device with this precise Bluetooth tracking feature


A user scrolls through their watch face options on the Google Pixel Watch 3.

Kaitlyn Cimino / Android Authority

TL;DR

  • The Google Pixel Watch 3 is the first known Android device to support Bluetooth Channel Sounding, enabling precise, centimeter-level distance tracking.
  • This feature is more accurate than traditional Bluetooth signal strength for finding items and serves as a widespread, low-cost alternative to UWB.
  • While the watch supports Channel Sounding after its Wear OS 5.1 update, the feature is not yet in use, likely in preparation for a future Find Hub app release.

Late last year, the Bluetooth Special Interest Group (SIG) announced Bluetooth 6.0, introducing a feature called Channel Sounding that enables true distance awareness by precisely calculating the distance between two devices. This new capability has exciting implications for item trackers, most of which lack precision finding. The catch? It seemed no Android devices on the market supported Bluetooth 6.0 or Channel Sounding. As it turns out, there is one device that supports Channel Sounding: the Google Pixel Watch 3.

You’re reading an Authority Insights story. Discover Authority Insights for more exclusive reports, app teardowns, leaks, and in-depth tech coverage you won’t find anywhere else. These reports reflect developments at the time of writing. Some features or details uncovered in leaks may change before official release.

Most Bluetooth devices currently rely on measuring the signal strength between them to estimate distance. While simple to implement, this method is unreliable; it’s imprecise and susceptible to interference, making it frustrating for item tracking. In contrast, Channel Sounding calculates the time it takes for a signal to travel between two devices, achieving centimeter-level accuracy.

If you’ve ever struggled to locate an item tracker using your phone, it’s likely because it was relying on that same imprecise signal strength method. This is why the rollout of UWB (Ultra-wideband) support in devices like the Moto Tag was so significant, as UWB allows for far more precise location tracking than what Bluetooth’s signal strength can offer.

Left: Locating an item tracker using Bluetooth signal strength measurements. Right: Locating an item tracker using UWB.

However, UWB adds complexity and cost to a product. It’s also only preferable for a handful of use cases, which is why so few Android phones support it. In contrast, nearly every mobile device supports Bluetooth. This ubiquity makes Channel Sounding a viable alternative to UWB, even if it’s not quite as precise.

The only catch is that most existing mobile devices don’t support Channel Sounding and likely never will, as adding the feature requires a Bluetooth firmware update. To date, no Android phone — not even Google’s latest Pixel devices — has received such an update. The Google Pixel Watch 3, however, gained this capability with its recent Wear OS 5.1 update. Following the update, the watch now reports that it supports FEATURE_BLUETOOTH_LE_CHANNEL_SOUNDING, the specific Android feature flag that confirms Channel Sounding is supported. Given that Channel Sounding is a Bluetooth 6.0 feature, we can assume this means the Pixel Watch 3 was updated to support the new standard, but that hasn’t been officially confirmed.

List of Android devices that support Bluetooth channel sounding

Mishaal Rahman / Android Authority

Even with UWB, the Pixel Watch 3 still benefits from having Channel Sounding. The problem is there’s no evidence the feature is actually being used. That’s likely because Google hasn’t released its Find Hub app for Wear OS, though evidence suggests one is in the works. Find Hub would be the prime candidate for using Channel Sounding, as it would dramatically improve locating trackers that have Bluetooth 6.0 but lack UWB, like the Chipolo POP.

Google may be waiting for Android 16 to fully implement this. The new OS version adds generic ranging APIs that will simplify how apps like Find Hub use these tracking technologies. Speaking of Android 16, its compatibility requirements mandate a clear performance minimum. Google mandates that devices with Channel Sounding must “report the range accurately to within +/- 0.5m at the 90th percentile … at a distance of 1m.” This requirement sets a minimum performance bar, ensuring the tracking experience is reliable across different devices. Of course, whether that holds up in practice remains to be seen.

Got a tip? Talk to us! Email our staff at news@androidauthority.com. You can stay anonymous or get credit for the info, it’s your choice.

Google Messages is finally fixing the cramped compose box


Google Messages SMS stock photo 2

Edgar Cervantes / Android Authority

TL;DR

  • Google Messages is finally fixing its long-standing compose box issue that limited users to just four lines of text.
  • When tinkering with the latest beta version of the app, we were able to expand the size of the compose box to 12 lines.
  • This long-awaited change could bring a major quality-of-life upgrade for Android users everywhere.

If you feel that writing a long text in Google Messages is like trying to draft an essay on a sticky note, you’re not alone. Google Messages has a tiny compose box, which has been a pain point for users for many years. Thankfully, Google finally seems to be doing something about it.

You’re reading an Authority Insights story on Android Authority. Discover Authority Insights for more exclusive reports, app teardowns, leaks, and in-depth tech coverage you won’t find anywhere else.

An APK teardown helps predict features that may arrive on a service in the future based on work-in-progress code. However, it is possible that such predicted features may not make it to a public release.

In the latest beta version of Google Messages (specifically, version messages.android_20250402_00_RC00.phone.openbeta_dynamic — yeah, it sounds like a spaceship launch code), we’ve spotted a long-overdue change that’s going to make a big difference for anyone who types more than a sentence or two in their texts.

Currently, the compose box in Google Messages stubbornly shows only four lines of text, with each line barely holding a few words. It’s fine if you’re firing off a quick “k” or an emoji, but if you want to write longer messages, it turns into a scroll-fest and you’re forced to flip up and down to review what you’ve written. But that’s about to change.

With some tinkering in the aforementioned beta version of Google Messages, we were able to unlock a new limit of 12 lines in the compose box instead of just four. That means, soon, you’ll actually be able to see what you’re writing in Google Messages without constantly swiping up and down.

In the side-by-side comparisons posted above, the difference between the new and the old Google Messages compose box is instantly noticeable. The old version crams long messages into a tiny space, while the new one gives your words a lot more breathing room. It doesn’t take over the whole screen, but it adds enough height to the compose box to feel more natural and avoid constant scrolling.

That said, the feature isn’t official just yet. While our APK teardown tells us it may be in the pipeline, we’ll have to wait and see when Google turns on the switch.

Got a tip? Talk to us! Email our staff at news@androidauthority.com. You can stay anonymous or get credit for the info, it’s your choice.

Google TV app may be getting a blue makeover and fresh features (APK teardown)


Google TV or Android TV UI on screen stock photo (8)

Edgar Cervantes / Android Authority

TL;DR

  • The Google TV app seems to be preparing some design tweaks and new functions.
  • The most noticeable update is a shift in the app’s color palette from gray to blue and darker blacks.
  • Search in Google TV is also possibly getting a useful update and a new content tab may be in the works.

Google appears to be working on some visual and functional updates for its Google TV app. Since there’s no public beta for the app, we dug into the code of an internal beta build of Google TV. This behind-the-scenes look has revealed several potential changes that could make their way to users in the near future.

You’re reading an Authority Insights story on Android Authority. Discover Authority Insights for more exclusive reports, app teardowns, leaks, and in-depth tech coverage you won’t find anywhere else.

An APK teardown helps predict features that may arrive on a service in the future based on work-in-progress code. However, it is possible that such predicted features may not make it to a public release.

The most noticeable update is a shift in the app’s color palette. Google seems to be replacing the existing dark gray accent with a brighter, modern-looking blue, similar to the Google Play Store’s redesign that came along a while back (see comparative images of current and new UI below).

The new blue accent also stands out against an updated, darker background, giving the Google TV app interface a cleaner and more contemporary look.

The upcoming visual tweaks don’t stop there. The Google TV app’s search page could also be usefully updated to include a list of recent searches, making it easier to revisit previous queries without starting a search from scratch.

A new way to discover fresh content

Our teardown also uncovered references to a new feature labeled the “Hot and New Tab”, with a corresponding internal flag titled “HotAndNewFeature__enable_hot_and_new_tab.” This suggests that Google may be working on adding a dedicated tab to highlight trending or newly released content.

While the feature seems to be in development, we couldn’t activate it yet, indicating Google may still be putting some finishing touches to it. It’s also possible Google is just testing the feature and is not ready to roll it out just yet.

For now, it looks like Google is continuing to refine the Google TV app’s design and features, hinting at more personalized, up-to-date content and an improved user experience. Stay tuned for more updates as these features potentially move closer to public release.

Got a tip? Talk to us! Email our staff at news@androidauthority.com. You can stay anonymous or get credit for the info, it’s your choice.