Google Messages gains two new features and one new problem
First, as spotted by Android Authority , RCS business messaging (RBM), or the business-to-consumer version of the Rich Communication Services messaging protocol, now supports PDF files. While RCS largely solved the issues that plagued the traditional SMS protocol by making the messaging experience richer and more interactive, it didn't let users send PDF files. This necessitated the use of email or other messaging apps to send PDF files, and added an extra step.This hindered communication involving flight tickets, passes, and documents in the PDF format.
That has changed now, with Google enabling support for sending PDF files for RBM users. For now, the feature is only available in India, and the file size cannot exceed 100MiB.
Google Messages will show a preview of the first page when a PDF file is sent if it's not password-protected. | Image Credit - Google
A preview image based on the first page of the file is shown when a PDF file is sent. Clicking on it opens the file in a PDF viewer. For password-protected files or other instances when previews aren't available, a default icon or thumbnail image is displayed instead.
—Google, July 2025 Google is also fixing the truncation issue that plagues rich card carousels. This RBM feature allows businesses to combine media, text, and buttons in one message.Previously, in the full-screen view, texts or suggestions on a rich card carousel were sometimes cut off. To indicate that more content is available, a More button is now displayed on truncated carousel cards. It isn't necessary to click on the button to view the message, as tapping anywhere in the text will expand the into a swipeable, full-screen view. This will ensure that users don't miss out on crucial details.
Messages will no longer end abruptly. | Image Credit - Google This feature is in beta right now, and a public rollout is expected by the end of the third quarter.
These two features will result in a better experience for users as they will neither have to go through the hassle of using another app to receive PDFs from a business nor have to worry about skipping over important parts of a message.
Google Messages is crashing after a new update but reinstalling it might help. | Image Credit - 9to5Google
As Google works to improve the messaging experience, a bug has made it to the app. The latest beta version, which was released yesterday, appears to be glitching, with Pixel and Samsung users complaining that it crashes within a few seconds of launch.This only happens when the homepage or messages list is launched, leaving notifications and chat bubbles as the only way to carry on conversations.
While some users were able to fix the problem by navigating to App info and uninstalling updates from the three-dot menu, the only reliable recourse is reinstalling the update. Rest assured that this will not delete your message history.
Hashtags
Try Our AI Features
Explore what Daily8 AI can do for you:
Comments
No comments yet...
Related Articles
GSM Arena
an hour 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
an hour ago
- GSM Arena
Oppo K13 Turbo Pro live photos and specs leak
Oppo's K13 Turbo family is fast approaching with an India announcement date already set for August 11. As far as we currently know, the lineup will include the K13 Turbo and the K13 Turbo Pro. Oppo hasn't officially confirmed any specs for the devices yet, but it seems that there are already units floating out there. Oppo K13 Turbo Pro An industry insider shared a couple of photos of the K13 Turbo Pro and particularly its back and side, highlighting the built-in cooling fan vent on the right-hand side of the phone as well as the RGB accent ring. The latter seems to be circling a 'dummy camera' module as opposed to an actual one. However, to the right of the main camera, we can see something else that looks like a lens. We have to wonder whether it is an ultrawide or the K13 Turbo Pro just has a single camera. Anyway, the source also offers some alleged specs for the K13 Turbo Pro, including the Snapdragon 8s Gen 4, which was previously hinted at in leaks. Apparently, the phone will also have a 1.5K, 120Hz flat AMOLED display, a large 7,000 mAh battery with 80W charging, IPX9 ingress protection and a large 7000mm² vapor chamber for cooling. Source
GSM Arena
an hour 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
