These are the Pixel 10 family's new camera-related AI features
We've had a ton of Pixel 10-related leaks recently, but most were all about the hardware and specs - the design, the innards, even the prices. Now it's looking like the leaks are turning their attention to the software side of things, and so today we get some information about a couple of new camera-related AI features that will be launching with the Pixel 10 family on August 20.
First off, Camera Coach. As the name implies, this will use Gemini to 'coach' you into improving your photography skills - in real time. It will suggest things like adjusting the angle, lighting, "and more". This will all take place by having Camera Coach read the scene and offer up its expertise based on what it 'sees'.
Next up, Conversational Photo Editing. This too is pretty self-explanatory. You'll be able to make edits to photos by simply asking Gemini to perform whatever modifications you want - whether by voice or text prompts.
This will cover changing backgrounds, brightening images, and removing objects. Obviously, the idea is to help you improve your shots even if you're not good at editing - Gemini will do it for you, just ask.
These features will launch on the Pixel 10 devices, and will be available to all four of them. They could very well make it to older Pixels through a Pixel Feature Drop at some later point, but at launch they will be exclusive to the Pixel 10 line. Of course, Google could even bring the Conversational Photo Editing to Google Photos regardless of what smartphone you're using, but the functionality in such a scenario might be limited (at least initially) to those who are paying for a Google AI plan.
Source 1 | Source 2
Hashtags
Try Our AI Features
Explore what Daily8 AI can do for you:
Comments
No comments yet...
Related Articles
GSM Arena
3 hours ago
- GSM Arena
We now know the dessert codename for Android 17
Victor, 09 August 2025 We won't keep you in suspense: Android 17 has the internal codename 'Cinnamon Bun'. The information comes from a trusted source within Google and was originally reported by Android Authority. Here's a convenient table breaking down all the previous dessert codenames for you to check out. Version number Codename Year of release 1.0 No codename 2008 1.1 Petit Four (internal) 2009 1.5 Cupcake 2009 1.6 Donut 2009 2.0, 2.1 Éclair 2009 2.2 Froyo 2010 2.3 Gingerbread 2010 3 Honeycomb 2011 4 Ice Cream Sandwich 2011 4.1, 4.2, 4.3 Jelly Bean 2012 4.4 KitKat 2013 5.0, 5.1 Lollipop 2014 6 Marshmallow 2015 7.0, 7.1 Nougat 2016 8.0, 8.1 Oreo 2017 9 Pie 2018 10 Quince Tart (internal) 2019 11 Red Velvet Cake (internal) 2020 12, 12L Snow Cone (internal) 2021 13 Tiramisu (internal) 2022 14 Upside Down Cake (internal) 2023 15 Vanilla Ice Cream (internal) 2024 16 Baklava (internal) 2025 But, we see you scratching your heads through the screen, wondering how and why Cinnamon Bun. Why not something with 'W' to follow Android 16 'Baklava'? Wait, Android 16 'Baklava'? It actually makes perfect sense. You can head on over to the source link for a more in-depth explanation, but here's the gist of it. Google relatively recently switched Android development from the old branch-based model to a new 'Trunk Stable' model. Instead of merging new release branches back into the stable one like before, the new model has a constantly ideally stable single main code branch with all new features, fixes and APIs developed behind 'feature flags' to keep them disabled until they are ready. You still with us? Good. The important bit here is that Google completed the migration to the new trunk-based dev model with Android 14 QPR2, and to mark the change, the build ID scheme was reset, so Android 14 QPR2 became build ID AP1A and QPR3 got build ID AP2A. The first time Google released a trunk stable build was in 2024, hence the use of the letter 'A' to preface the build ID. However, presumably by that time Android 14 already had its 'Upside Down Cake' name and Android 15 its 'Vanilla Ice Cream' moniker, so it was too late to 'restart' the names and call Android 15 something with 'A'. Once the year turned over to 2025, however, the build IDs started coming out with the letter 'B' and Google decided to call Android 16: 'Baklava'. The next letter for build IDs is 'C' and hence a dessert with 'C' – enter 'Cinnamon Bun', presumably since 'Cupcake' was already taken. Of course, ultimately, the dessert name doesn't really matter that much, especially since Google decided to move away from it as a public branding. Nowadays, it is a remnant on the development side of things. Still, it is interesting to see what sweets the Google team chooses now that it is essentially the second time around for each letter. As for Android 17, we expect it to land around June 2026. Source
GSM Arena
4 hours ago
- GSM Arena
We now know the dessert codename for Android 17
We won't keep you in suspense: Android 17 has the internal codename 'Cinnamon Bun'. The information comes from a trusted source within Google and was originally reported by Android Authority. Here's a convenient table breaking down all the previous dessert codenames for you to check out. Version number Codename Year of release 1.0 No codename 2008 1.1 Petit Four (internal) 2009 1.5 Cupcake 2009 1.6 Donut 2009 2.0, 2.1 Éclair 2009 2.2 Froyo 2010 2.3 Gingerbread 2010 3 Honeycomb 2011 4 Ice Cream Sandwich 2011 4.1, 4.2, 4.3 Jelly Bean 2012 4.4 KitKat 2013 5.0, 5.1 Lollipop 2014 6 Marshmallow 2015 7.0, 7.1 Nougat 2016 8.0, 8.1 Oreo 2017 9 Pie 2018 10 Quince Tart (internal) 2019 11 Red Velvet Cake (internal) 2020 12, 12L Snow Cone (internal) 2021 13 Tiramisu (internal) 2022 14 Upside Down Cake (internal) 2023 15 Vanilla Ice Cream (internal) 2024 16 Baklava (internal) 2025 But, we see you scratching your heads through the screen, wondering how and why Cinnamon Bun. Why not something with 'W' to follow Android 16 'Baklava'? Wait, Android 16 'Baklava'? It actually makes perfect sense. You can head on over to the source link for a more in-depth explanation, but here's the gist of it. Google relatively recently switched Android development from the old branch-based model to a new 'Trunk Stable' model. Instead of merging new release branches back into the stable one like before, the new model has a constantly ideally stable single main code branch with all new features, fixes and APIs developed behind 'feature flags' to keep them disabled until they are ready. You still with us? Good. The important bit here is that Google completed the migration to the new trunk-based dev model with Android 14 QPR2, and to mark the change, the build ID scheme was reset, so Android 14 QPR2 became build ID AP1A and QPR3 got build ID AP2A. The first time Google released a trunk stable build was in 2024, hence the use of the letter 'A' to preface the build ID. However, presumably by that time Android 14 already had its 'Upside Down Cake' name and Android 15 its 'Vanilla Ice Cream' moniker, so it was too late to 'restart' the names and call Android 15 something with 'A'. Once the year turned over to 2025, however, the build IDs started coming out with the letter 'B' and Google decided to call Android 16: 'Baklava'. The next letter for build IDs is 'C' and hence a dessert with 'C' – enter 'Cinnamon Bun', presumably since 'Cupcake' was already taken. Of course, ultimately, the dessert name doesn't really matter that much, especially since Google decided to move away from it as a public branding. Nowadays, it is a remnant on the development side of things. Still, it is interesting to see what sweets the Google team chooses now that it is essentially the second time around for each letter. As for Android 17, we expect it to land around June 2026. Source
GSM Arena
9 hours ago
- GSM Arena
Google Pixel Buds 2a specs leak
Google is unveiling the Pixel 10, Pixel 10 Pro, Pixel 10 Pro XL, Pixel 10 Pro Fold, and Pixel Watch 4 on August 20, and alongside them the Pixel Buds 2a should also become official. Last week an image leaked showing them in their case, and today their main specs have been outed by none other than Evan Blass, aka @evleaks. He shared the comparison you can see below, between the upcoming Pixel Buds 2a and the already available Pixel Buds Pro 2. Obviously, the Pro buds have more features, as the Pixel Buds 2a are expected to be cheaper, being the successors to the Pixel Buds A-Series from all the way back in 2021. They've certainly been a long time coming. As you can see, the Pixel Buds 2a will be advertised to have a 7-hour battery life (20 hours with the charging case). They will support Spatial audio, but without head tracking. The case won't have wireless charging, but the Buds 2a will have ANC (though without "Silent Seal 2.0", so expect its performance to be inferior to the Pixel Buds Pro 2's ANC). The Pixel Buds 2a will only be offered in two colors which resemble black (or dark gray) and white, but which Google will undoubtedly call something else like Obsidian and Porcelain. Source
