Google is finally adding a native translate capability to Gmail for Android and iOS after long supporting it on the web client.
Update 8/21: Gmail’s translate feature is rolling out via a server-side update. We’re seeing it with version 2023.07.23.x. It’s not yet widely available, but one way to check is by tapping the second overflow menu in the message body for “Translate.”
That option brings up a banner with the settings gear letting you select something other than “Detect language.”
Before the message body, Gmail will show a “Translate to” banner. Tapping updates what appears below with the ability to “Show original” again and “Automatically translate” a specific language going forward.
Press the settings gear to pick another output language, with over 100 supported. This prompt appears when the contents of an email doesn’t match your “Gmail display language,” which is the first dropdown menu in web app settings.
You can manually translate a language by going into the three-dot overflow menu in the top-right corner if an email was not recognized. The feature can also be disabled for a specific language by clicking ‘x’ on the banner and then “Don’t translate [language] again.”
Translations in Gmail for Android are rolling out from today onwards, while it will come to iOS in the coming weeks. This is a much-needed integration as users previously had to open an email on their computer, or taking a screenshot on mobile and send it to Google Lens or Translate.
Available to all Google Workspace customers and users with personal Google Accounts
Gmail encouraging users to enable Enhanced Safe Browsing
Over the past few days, Google has been prominently promoting Enhanced Safe Browsing in the Gmail apps.
Appearing just above your inbox on Android and the web, getting “additional protection against phishing” is the main benefit for Gmail users: “Turn on Enhanced Safe Browsing to get additional protection against dangerous emails.”
We first saw this message on Friday, and it’s seeing a wide rollout. Google touts:
Provide real-time security scanning to warn you about or block dangerous websites, downloads, and extensions.
Improve Google’s ability to detect and protect against phishing and malware for you and everyone on the web.
Give you better protection from dangerous links across Google apps.
In other security news, Google shared today that “70% of Google Accounts, owned by people regularly using our products, automatically benefit from second factor authentication that confirms their identity when a suspicious sign-in is detected.” The company is looking forward to wider passkey adoption.
What is Enhanced Safe Browsing
First introduced three years ago in Chrome, Enhanced Safe Browsing provides real-time web protections. The standard, non-enhanced version works by checking the URL of sites you visit against a local list that is downloaded/refreshed every 30 minutes (as of 2020). This list is widely used by many other apps and browsers.
Google created Enhanced Safe Browsing because “sophisticated phishing sites” got around the update period. “Uncommon URLs” are sent in real time to determine whether you’re about to visit a phishing site, with Chrome also sending a “small sample of pages and suspicious download,” while Gmail, Google Drive, and other apps you’re signed in to contribute data.
Later on, Enhanced Safe Browsing expanded to provide warnings about Chrome extensions, conduct in-depth file analysis, leverage ML models, and is now also available in Chrome for iOS.
It’s also accessible in Chrome settings: chrome://settings/security.
New Gmail ‘Offer times you’re free’ tool streamlines calendar scheduling
Google is rolling out a new Calendar tool in the Gmail web client that makes it easier and faster to schedule meetings.
When composing an email on the web, the toolbar will feature a new Calendar icon at the right with two options:
Create an event: This functionality was previously accessed from the “three dot menu on top of the email conversation view.” Event title and recipients are pre-filled from the email. Gmail will also automatically insert an event summary into the email body for easy sharing.
Offer times you’re free: This new option opens the Calendar side panel, where you can “select and insert proposed meeting times” by highlighting what’s free in your primary calendar across multiple days. Recipients will be able to select one of the proposed times via an interactive email reply, and this will automatically generate a Calendar invite after confirming their name and email address.
At the moment, Offer times you’re free only works for 1:1 meetings: “If multiple people are included in the recipient list, only the first person to book an appointment will be added to the event automatically.”
Google hopes to make “scheduling much easier by reducing the back-and-forth in lengthy email threads when negotiating or scheduling meeting times.” This is rolling out over the coming weeks:
Available to all Google Workspace customers and users with personal Google Accounts
With the Pixel 7 and 7 Pro last October 2022, Google reintroduced Face Unlock to its phones after abandoning the Pixel 4’s approach.
At the launch event, it was announced as such:
And the front camera has another role to play. Pixel 7 and 7 Pro’s front camera uses our advanced machine learning models for face recognition, to power Face Unlock. So you have the faster, more secure under-display fingerprint reader, and now you have the convenience of unlocking your phone with a glance.
Instead of using a dot projector, flood illuminator, and IR cameras in conjunction with the Soli radar, Google turned to a front-facing camera that supports DPAF (dual-pixel auto-focus) to presumably create a depth map to be used with the aforementioned ML models. I find it slightly weird that Google has yet to detail the technology behind this Face Unlock approach in an AI/Research blog post, like it did before.
For the most part, the experience has been fine. It’s not better than the dedicated hardware of the Pixel 4 or Face ID on the iPhone. That approach lets face recognition operate in all lighting conditions, including the absence of any. My usage of the fingerprint sensor definitely picks up at night, resulting in a two-tiered security experience throughout the day.
Of course, the more stark tiering is how face recognition is not considered a secure unlock method by Android for things related to payments, passwords, and passkeys. In that regard, today’s Face Unlock is less secure than what came before in an unfortunate and uncharacteristic step backward. Assuming Google decided to continue the Pixel 4 lineage rather than reorienting, the Pixel 5 would have probably not had a hole punch and instead opted for an iPhone-esque cutout in order to avoid a thick upper bezel. The design would have presumably shrunk by now. That’s one big shame with the Pixel restart.
Going back to reality, the Face Unlock we do have today on the Pixel 7, 7 Pro, 7a, and Fold is best summarized as a convenience. I’ve been using it a bit more with the Pixel Fold as a way to transition from an under-display to a side-mounted fingerprint sensor. Having used the former for two generations now, I’ve come to like how you’re literally interacting with the UI for unlocking. I’m amused at the hardware/software synergy.
In optimal conditions, Face Unlock on the Fold works quite fast and lets you start doing things on your phone pretty quickly, which is arguably what’s most important.
That said, the security and environmental conditions will always stop it from becoming ubiquitous. I wonder whether the primarily software-driven approach to Face Unlock is something that has a future. The roadmap behind the IR approach that Apple uses is more straightforward in that ideally all those components can be placed and work underneath the display.
Namely, for Google, will the recognition algorithms get foolproof enough that it cannot be tricked and gets elevated to a secure unlock method? Does this require a front-facing camera upgrade, more on-device processing, or another innovation entirely?
Or will the future of Face Unlock on the Pixel be a return to IR? That would be great from a security and convenience perspective but would make the current feature feel one-off.
Following the last update just over a week ago that did not introduce any new features, Google is rolling out Android 14 Beta 5.1 as another bug fixer.
While Beta 5 was said to be the “last scheduled update” and that the “official release is next,” Google does not consider .1 patches to be milestones. A similar thing happened during last year’s preview cycle.
There are just four fixes with UPB5.230623.005 for Pixel phones and UPB5.230623.005.A1 on the Pixel Fold and Tablet. Notably, Google has disabled the trademark live wallpaper on the Pixel Fold for performance reasons.
Fixed an issue that caused the system to stop detecting a SIM card if Fixed Dialing Number (FDN) features were enabled.
Fixed an issue that caused connectivity interruptions for devices with carriers using 5G standalone (SA) mode.
Fixed an issue for some devices where a blank home screen displayed after unlocking the device.
Fixed a performance issue by temporarily disabling feather-styled live wallpaper on Pixel Fold. The live wallpaper version will be re-enabled after the other underlying issues are fixed.
Android 14 Beta 5.1 with the August 2023 security patch is available for the Pixel 4a 5G, Pixel 5, Pixel 5a, Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel Tablet, and Pixel Fold, as well as the Android Emulator.
Ahead of the public launch, Android 14 is getting a Beta 5 for Pixel phones, the Tablet, and Fold. It comes a month after the last major release and is the final scheduled update.
With the official release of Android 14 only weeks away, today we’re bringing you Beta 5, the last scheduled update in our Android 14 beta program. It’s the last chance to make sure your apps are ready and provide feedback before non-beta users start getting Android 14.
GOOGLE
This is the third Platform Stable Android 14 release for final app testing and addresses a number of issues:
Fixed an issue where after unlocking a device using a PIN, TalkBack provides incorrect audio.
Fixed an issue where Wi-Fi scanning was consuming too much battery.
Fixed an issue where some pictures would glitch with extra shadow blocks.
Fixed an issue where in some cases, the fingerprint sensor icon wouldn’t appear as expected.
Fixed an issue where voice over Wi-Fi wasn’t enabled by default.
Fixed an issue on Pixel Fold devices where the device loses antenna ranging session information and cannot recover it.
Fixed an issue where an extraneous white bar would appear in some apps.
Fixed a background color issue with the UI used to add a shortcut to the home screen.
Fixed a launcher issue that was causing frequent crashes and other quality issues.
Fixed an issue on Pixel tablets where user interaction during the transition from screen saver to low-light clock causes a SysUI crash.
Fixed a Pixel Fold issue where tapping would fail to wake the device.
Fixed a Pixel Fold issue where the system buttons would have inconsistent positions after folding and unfolding.
Fixed an issue causing SysUI crashes when removing an app pair in landscape.
Fixed an issue the launcher doesn’t fully render after setup.
Fixed an issue where the system displayed an incorrect mobile connection type.
Fixed an issue where navigating back to exit an app leads to users no longer being able to open the app.
Fixed an issue where wallpaper previews were sometimes blank.
Fixed an issue where the system theme changes from yellow to pink after rebooting.
Fixed an overscroll issue with ScrollView.
Fixed an issue where certain color palettes were difficult to see when the lock screen was activated.
Fixed an issue where users couldn’t enable battery sharing if a work profile exists on the device.
Fixed an issue where a tablet screen inappropriately turns off when docked.
Fixed an issue where the device policy manager was preventing notifications from appearing.
Fixed an issue where group notifications couldn’t be expanded.
Fixed an issue where the lockscreen didn’t properly display the clock.
Fixed various camera issues that were causing crashes and reductions in quality.
Fixed an issue with power consumption during video playback.
Fixed a Weather clock rendering issue.
Fixed an issue where the lock screen customization preview didn’t match the end result.
Fixed an issue that was causing the wallpaper selection screen to crash.
Fixed an issue where Pixel devices weren’t connecting with some routers.
Fixed a toast search result issue where the color was too similar with the background color.
Fixed an issue where tapping a notification before using facial unlock does not open the notification.
Fixed an issue on Pixel Fold where two clocks were displayed at the same time when in widescreen.
Fixed an issue where widgets would overlap and stack incorrectly.
Fixed an issue where closing the PiP window doesn’t stop YouTube playback.
Fixed an issue with switching call audio sources.
Fixed an issue where after unlocking a device, only the background appears.
Fixed an issue with dragging folders to remove them.
Users can submit problems via Android Beta Feedback on Pixel devices. Access it from the app drawer or via Quick Settings to file bugs in the Google issue tracker. There’s also the Android Beta community on Reddit.
Android 14 Beta 5 (UPB5.230623.003) with the August 2023 security patch is available for the Pixel 4a 5G, Pixel 5, Pixel 5a, Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel Tablet, and Pixel Fold, as well as the Android Emulator.
Most people will be installing via the Android Beta Program, but you can also flash or sideload. If you need help, here’s our full guide on installing Android 14.
After years of being the lone option, Samsung finally has some foldable competition in the US, and that partially takes the form of Google’s Pixel Fold, which comes in at the same price as Samsung’s brand-new Galaxy Z Fold 5. But after using both devices, there’s a clear better option.
Galaxy Z Fold 5 vs. Pixel Fold: How they compare on paper
When you look at the spec sheet alone, Google’s Pixel Fold and Samsung’s Galaxy Z Fold 5 are rather similar. Both have 7.6-inch inner displays, plenty of RAM and storage and hinges that are rated for at least 200,000 folds.
The differences really come down to the details. The Pixel Fold has a wider aspect ratio to both of its displays. The 17.4:9 ratio of the outer display is short and wide compared to the Fold 5’s 23.1:9 ratio, which is extremely tall and narrow. The Pixel is also considerably thinner at 12.1mm to the Fold 5’s 13.4mm. Despite that, Pixel Fold also has a bigger battery at 4,821 mAh.
Google Pixel Fold
Galaxy Z Fold 5
Outer display
5.8 inch, 17.4:9 ratio
6.2 inch 23.1:9 ratio
Inner display
7.6 inch, 6:5 ratio
7.6 inch, 21.6:18 ratio
Processor
Google Tensor G2
Snapdragon 8 Gen 2 for Galaxy
Storage/RAM
256GB/512GB UFS 3.1 + 12GB RAM
256/512GB/1TB UFS 4.0 + 12GB RAM
Hinge rating
200,000 open/close
200,000 open/close
Thickness
12.1mm folded/5.8mm unfolded
13.4mm folded/6.1mm unfolded
Battery
4,821 mAh
4,400 mAh
Cameras (rear)
48MP/10.8MP 5x/10.8MP UW
50MP/10MP 3x/12MP UW
Price
$1,799
$1,799
How the two compare, though, really comes down to actually using them.
The Galaxy Z Fold 5 is boring in the best way
If you’ve looked into a foldable before now, you’ve likely looked at the Galaxy Z Fold series. And through that eye, the Galaxy Z Fold 5 doesn’t seem all that new, and that’s because it isn’t. The design of the device hasn’t really changed much at all over the past three years, and compared to the Galaxy Z Fold 4 before it, the Fold 5 really only has a new hinge, and that’s about it.
But the lack of major upgrades in Samsung’s flagship foldable has led to something perhaps more important.
Samsung’s foldable tech has just gotten really, really polished over the past couple of generations. The company has spent its time addressing the little problems, like improving the screen brightness, extending battery life, and improving the hinge, rather than hitting bigger issues like the display crease and cameras. In Samsung’s eyes, it seems, those aspects are “good enough,” where others still need work. And after using the Fold 5 for a few weeks, I mostly agree. The Galaxy Z Fold 5 really just feels like it’s as good as this particular form factor can get without bigger changes. And if you like this overall package, it’s really just a great refined product.
Beyond that, another strength of the Galaxy Z Fold 5 is its software. While One UI is a heavy skin on top of Android, it’s packed with features that are useful on the Fold 5’s bigger display and ones that Google’s cleaner Android build just doesn’t have.
Of course, none of this is to say the Galaxy Z Fold 5 isn’t without its flaws. The tall and narrow outer display isn’t great for typing and doesn’t play very well with some apps. The inner display’s taller nature also means that a lot of apps never trigger a tablet interface, which makes some apps feel less optimized for the form factor.
Pixel Fold is undeniably good – it’s just not as good
That’s why the Pixel Fold falls – death by a thousand cuts.
The Pixel Fold’s downsides really just outweigh the good. The Tensor chip inside is plenty powerful, but it’s prone to overheating very easily, which is a really hard pill to swallow at this price point.
The screens also aren’t nearly as bright as Samsung’s, and Google’s crease isn’t any better either. Samsung’s crease still isn’t good, and it’s very noticeable, but Google’s is wider and thus felt more often.
There’s also the hinge. While I stand by the opinion that the Pixel’s hinge not easily sitting at 180 degrees isn’t a problem, I’ve much enjoyed not having to apply the bit of extra pressure on the hinge when using the Fold 5. It’s just a much more consistent feel. Similarly, the Fold 5’s inner display is much easier to type on because Google’s phone is just way too wide.
Battery life is also another sore point for the Google device. Whereas Samsung’s latest generation has pulled off some kind of miracle by upping endurance significantly compared to the last model, the Pixel Fold suffers from mediocre battery life. Often I find the device struggling to make it through a long day, whereas the Galaxy just seems to keep on chugging along.
Really, the perks of Pixel Fold come down to just two aspects.
Firstly, there’s the aspect ratio. Google’s device has a short and wide outer display that makes way for a very wide inner display. This means that the outside is far more usable than Samsung’s, and the inner display triggers more tablet apps. I still think this leads to too many poor app experiences (like Instagram, Reddit, and so on), but when it works, it just works really nicely.
Google Weather on the Pixel Fold
The other point is, of course, the camera. Google’s Pixel line has built its entire legacy on the camera, and that translates wonderfully to the Fold. The 48MP primary camera takes shots that look great and that, more importantly, I can trust. The Galaxy Z Fold 5 will pump out a good shot now and then, but it’s not consistent enough. Two shots taken back to back can look drastically different, for example. Plus, the Pixel Fold has a much better 5x telephoto camera that absolutely destroys the Galaxy Z Fold 5’s camera setup at range. There’s just no competition there: Google has the way better camera.
Tensor is a real problem in a pricey foldable
Google’s Tensor processor is unique to Pixel phones, and it’s not a terrible chip. It has plenty of power, and Google uses its AI strengths to optimize a few features and the camera experience too. However, Tensor is just not as good as a modern Snapdragon chip.
Tensor tends to overheat quickly and struggles with battery efficiency when on a cellular network, especially if signal is spotty. The Snapdragon 8 Gen 2 in the Galaxy Z Fold 5, though, is as good as it gets in an Android phone. It’s exceptionally powerful and extremely efficient, which leads to great battery life on the Fold 5.
Personally, I’m usually willing to put up with Tensor’s deficiencies because Pixel phones are usually a lot cheaper than the competition, but that’s not the case with the Pixel Fold. Google’s foldable costs $1,799, the same as Samsung’s device, and Google doesn’t offer the same discounts and trade-ins to go with that. Tensor shouldn’t be a deal-breaker for a normal Pixel phone, but it is absolutely a valid killer on the Fold.
Galaxy Z Fold 5 is the better foldable
Where the Pixel’s aspect ratio and cameras are genuine improvements in many ways, the Galaxy Z Fold 5 makes strides where it counts. The screen is brighter and better. The hinge is smoother and tougher. The chip inside is stronger and much less prone to overheating. And there are perks Google just can’t match, like stylus support and a much more fleshed-out accessories ecosystem.
Don’t think it can be argued. Objectively, the Galaxy Z Fold 5 is the better foldable.
But…
Why some still using the Pixel Fold
Despite the Pixel Fold’s many shortcomings, it’s the one some going to keep using. Why? It really boils down to one thing – the camera.
Samsung’s Galaxy Z Fold 5 gets a whole lot right, but its camera is a deal-breaker for me. It’s too unreliable, and as such, I’ve always dual-wielded a Pixel phone alongside a Galaxy Z Fold device for the past three years. But now that I have the option to get a foldable Pixel, that’s what I choose to carry because, most of the time, I only want to carry one device.
According to a new rumor today, the Pixel 8 and 8 Pro will both get five case colors each in a continuation of the trend introduced by the Pixel 7a.
SnoopyTech shared the following lineup this morning on Reddit (the account appears to have been removed from Twitter):
Pixel 8: Carbon – Haze – Jade – Peony – Real Red
Pixel 8 Pro: Carbon – Jade – Porcelain – Real Red – Sky
Carbon should be black or gray, while Jade (green) and Real Red (coral) are shared between both sizes. Haze on the Pixel 8 could be a light blue, while Peony sounds like a pink. Porcelain should be something light, while Sky is likely blue on the Pixel 8 Pro.
Google Pixel 7 case vs Google Pixel 7a case
Google’s previous high was four with the Pixel 6 Pro before going back to three apiece last year. With the Pixel 8 case colors out of the way, the big question is whether Google is going for soft-touch silicone — like the 7a, Fold, and Tablet — or a harder plastic again. The trend is certainly toward the former.
Pixel 8 Pro leaks in live images
Following renders in March and the short video in the temperature sensor leak this May, we now have an even better “in hand” look at the Pixel 8 Pro.
Somebody on Reddit (via Droid-Life) shared a Pixel 8 Pro prototype yesterday, as evidenced by the identifying pattern in place of the “G” logo. They apparently got it “from the device team in Google for testing.”
The bootloader screen confirms the “husky” code name and “ripcurrent” bootloader, while there’s a “Zuma” sticker, which is the Tensor G3 code name, on the back. Other specs on this particular unit include 12GB Samsung LPDDR5 RAM and 128GB SKHynix storage.
We see the increased corner radius in this leak, while the Pixel 8 Pro camera is what really stands out. The unified pill housing all three cameras takes up more of the bar compared to last year. It certainly looks taller with less space to the edge of the bar. The microphone cutout is in-between the first and second cameras, with other sensors below it. You then see the flash and IR temperature sensor.
The image of the front screen shows the Pixel 8 Pro in a case, but we do see the flat screen.
Pixel 8 Pro will apparently still start at 128GB of storage as 256GB becomes the norm
The Google Pixel 8 series is just a couple of months away from its debut, and a new leak is now detailing storage options and more.
WinFuture reports that Google Pixel 8 Pro will offer three total storage options, starting at 128GB. Beyond that buyers could select from 256GB and 512GB options.
That’s unchanged from last year’s Pixel 7 series and the Pixel 6 before it, but it comes at a notable time. Over the past year, more and more flagship devices have moved over to 256GB as the minimum storage tier. Samsung’s Galaxy S23+ and S23 Ultra, the OnePlus 11, and many others have made the switch, often for the same price as the previous 128GB models. Of course, a big part of that is the new UFS 4.0 storage class supported with the Snapdragon 8 Gen 2 processor, which currently isn’t widely available in 128GB sizes. The Pixel 8 series would be powered by Tensor G3, which does reportedly support that newer storage option, but it seems Google may not be using it fully. Samsung also uses UFS 3.1 on the base Galaxy S23 to offer a lower-cost 128GB model.
Notably, a previous Pixel 8 Pro leak showed 128GB of storage on that device.
Whether or not this lower storage offering comes as a problem is unclear, but it certainly makes the Pixel stick out. With rumored price increases, too, it only makes the gap between Google’s device and competitors smaller.
Beyond that, this latest report also reiterates color options, with “Licorice,” “Porcelain,” and “Sky” on the Pixel 8 Pro, and “Licorice,” “Peony,” and “Haze” on the regular Pixel 8.
Chrome’s most recent change leaves the bottom download bar out of the fray completely, opting for a new tay next to the address bar. Here’s how you can revert back and get the familiar downloads bar back.
You’ve likely noticed that Chrome has a slightly new UI in place. When an image or file is downloaded, rather than the traditional bottom downloads bar appearing and showcasing your most recent file, nothing happens. If you look keenly, a download icon near the address bar’s right end will light up blue. Clicking it opens a new tray deemed the “downloads tray.”
The new UI element is an approach to user concerns on several fronts. One of the most compelling is that the new tray has no effect on whatever webpage you’re visiting. The downloads bar in Chrome had the potential of squeezing an active website. That wasn’t ideal, especially for laptop users.
Google also noted that the old look was no longer modern and was deemed inconsistent with the overall improved look of Chrome.
Whatever the case, some will inevitably prefer the old look, and if that includes you, it can be changed on Windows, ChromeOS, and macOS.
How to revert to the downloads bar
To change Google Chrome’s new downloads system, you’ll have to disable one of Chrome’s settings flags. While this isn’t a perfect solution, it’s the only one currently available to all users.
Flags have the potential to change other aspects of Chrome for the worse, so doing so may cause issues. While we haven’t had issues completing the following process, doing so is at your own risk.
In Google Chrome’s search bar, enter chrome://flags/#download-bubble.
A highlighted option will appear. Change from Default to Disabled.
Relaunch Chrome, and you’ll no longer see the downloads tray introduced recently. Rather, you’ll get the downloads bar that appears at the bottom of the Chrome window when something is saved to your computer.
Chrome ‘Tap to Search’ on Android picks up Material Theme tweaks
One underrated Chrome feature on Android performs a subtle Google lookup when you highlight anything on the web. Chrome’s Tap to Search has now gained some Material Theme tweaks.
Tap to Search — originally Touch to Search — dates back to 2015 and activates when you select any text on a page. This surfaces a bar at the bottom of your screen that loads Search results for the highlighted query. For quick lookups, you don’t have to switch away from what you’re originally viewing, while there’s the option to “open in new tab.”
Learn about topics on websites without leaving the page. Tap to Search sends a word and its surrounding context to Google Search, returning definitions, pictures, search results, and other details.
A quiet update in recent days has redesigned Tap to Search with Material Theme tweaks. For starters, the bar is now a sheet with rounded corners. It’s more obvious that you can drag to open instead of just clicking.
There’s now a button in the top-right corner that lets you open the full result in another tab, while Tap to Search no longer takes up the entire screen when expanded. It’s a minor change, but one that continues to modernize the look of Chrome for Android.
The feature — available in both the browser and Chrome Custom Tabs — can be enabled/disabled from Settings > Sync and Google services > Tap to Search. This new look (chrome://flags/#overlay-new-layout) is widely rolled out with the latest version of Chrome 79.
For years, files you download would appear in a bar at the bottom of Chrome, but Google is now changing the desktop browser’s UI so you get a download tray instead.
Having talked to users, Google says it identified three issues with the legacy download bar:
“Occupied precious pixels at the bottom of the screen which squeezed the web content area, and was limited by screen width in how many files it could show at once”
“Didn’t go away automatically, and only offered actions such as pause/resume and open in folder from a fixed overflow menu”
“Was no longer modern, interactive, and consistent with the look and feel of other browser UI or the browser ecosystem at large”
That first issue was particularly annoying, especially on a laptop, making the bar something I would quickly close out every time. As such, desktop Chrome is rolling out what Google calls the download tray.
Appearing to the right of the address bar (Omnibox), Google believes the new location “helps create a clearer separation of trusted browser UI from web content.” You’ll get an animated ring to note progress and a small pop-up when something completes, though this can be disabled from Settings > Downloads > “Show downloads when they’re done.”
Tapping presents a list of “all your downloads from the past 24 hours in any browser window, not just the one in which you originally downloaded a file.” Buttons let you open the folder a download is in, as well as pause/resume, cancel, and retry.
You can still drag downloaded files to “another folder, program, or website.” “Show all downloads” appears at the bottom of the tray with chrome://downloads and “Downloads” in the overflow menu remaining.
Chrome is using this new download tray to provide better malware and virus warnings, as well as context. For example, Google will note when a dangerous download has been blocked.
For extension developers, it is worth noting changes to chrome.downloads extensions APIs in case you need to update your extensions – specifically, setShelfEnabled has been replaced by setUiOptions which lets you show or hide the new downloads experience.
Chrome’s new download tray is rolling out now for Mac, Windows, Linux, and ChromeOS. Make sure your browser is fully updated, and it should be fully available over the coming weeks.
Meanwhile, the Chrome Omnibox on Android and iOS will show “Related to this page” search suggestions on certain sites. If you’re on the New Tab Page, opening the address bar will show trending searches, while Chrome now shows 10 (instead of six) suggestions as you enter a query. Lastly, the Touch to Search bar that appears at the bottom of your screen when you highlight something will now offer a “carousel of related searches.”
Google at I/O 2023 announced that it would leverage the over 1 billion Android devices in use to find your lost items. The Find My Device (FMD) network was originally supposed to launch this summer, but Google is now delaying it.
Back in May, Google said Bluetooth trackers from Tile, Pebblebee, and Chipolo would be compatible with the Find My Device network. The two latter brands already opened pre-orders, but Chipolo communicated a delay two weeks ago.
Google announced today that it’s delaying the launch of the Find My Device network. It comes down to unknown tracker alerts that automatically warn you if somebody is monitoring your location with a nefariously placed tag. While Google already said that all Bluetooth tags compatible with the FMD network will support Android’s unknown tracker alerts, the iPhone does not have similar detection capabilities.
Google is not launching the Find My Device network “until Apple has implemented protections for iOS.” By making sure iPhone owners can find FMD-compatible trackers, this should hopefully reduce and help prevent the Google network from being used to track Apple devices without awareness from their owners. That would reflect badly on the FMD network and associated products, which is an ongoing occurrence for AirTags.
Notably, Google confirmed to us that the unwanted AirTag tracker alerts that Android is rolling out starting today are based on a custom implementation that is different from the upcoming spec. Android is implementing the alerts now to allay customer concerns since the Apple tracker is widely available.
In terms of when the Find My Device network will launch, Google only mentions the expected end of 2023 finalization of the spec. There will presumably be another waiting period for Apple to update iOS.
What is the Find My Device network
Today, Find My Device can locate lost phones and watches that are connected to the internet. (There’s also support for some Bluetooth headphones based on their last known connection to your phone/tablet.)
The new Find My Device network can “locate devices that are offline or that don’t have location capabilities.” This works by having the 1+ billion Android devices in the world periodically check for nearby devices to crowdsource the location of missing ones.
Behind the scenes, Google says “location data crowdsourced from the network is end-to-end encrypted, and that it “can’t see or use it for any other purposes.” The Find My Device network can locate phones and tracker tags, as well as headphones, including Pixel Buds, as well as those from Sony and JBL.
Android 14’s latest beta paves the way for a full launch sometime next month, but it’s still hinting at more features to come. One of those upcoming changes might be a warning when you try to sideload Google apps on Android 14.
Android Police reports that Android 14 adds the ability for app stores on your device to claim “update ownership” over select apps. This essentially just adds another step to sideloading, as a warning message will appear that states where updates normally come from, and reiterates the risk of sideloading. You can simply ignore the warning and continue on.
Apparently, Google apps are where we’ll see this first. A brief demo seen below shows Android 14’s new sideloading warning which says that updates are “normally” from the Play Store. In this case, Google Play Services was having an update installed via APK Mirror’s Installer app.
This app normally receives updates from Google Play Store. By updating from a different source, you may receive future updates from any source on your phone. App functionality may change.
This isn’t the only example of Google cracking down somewhat on apps in Android 14. Earlier this year, our Kyle Bradshaw and Dylan Roussel reported that Android 14 would also block the installation of “outdated” Android apps, whether they come from sideloading or an app store.
Android 14 set to block certain outdated apps from being installed
To help reduce the potential for malware, Android 14 will begin fully blocking the installation of apps that target outdated versions of Android.
For years now, the guidelines for the Google Play Store have ensured that Android developers keep their apps updated to use the latest features and safety measures of the Android platform. Just this month, the guidelines were updated, requiring newly listed Play Store apps to target Android 12 at a minimum.
Up to this point, these minimum API level requirements have only applied to apps that are intended for the Google Play Store. Should a developer wish to create an app for an older version, they can do so and simply ask their users to sideload the APK file manually. Similarly, if an Android app hasn’t been updated since the guidelines changed, the Play Store will continue serving the app to those who have installed it once before.
According to a newly posted code change, Android 14 is set to make API requirements stricter, entirely blocking the installation of outdated apps. This change would block users from sideloading specific APK files and also block app stores from installing those same apps.
Initially, Android 14 devices will only block apps that target especially old Android versions. Over time though, the plan is to increase the threshold to Android 6.0 (Marshmallow), with Google having a mechanism to “progressively ramp [it] up.” That said, it will likely still be up to each device maker to decide the threshold for outdated apps or whether to enable it at all.
If the minimum installable SDK version enforcement is enabled, block the install of apps using a lower target SDK version than required. This helps improve security and privacy as malware can target older SDK versions to avoid enforcement of new API behavior.
By blocking these outdated apps, Google intends to curb the spread of malware apps on Android. The developer responsible for the change notes that some malware apps have intentionally targeted older versions of Android to bypass certain protections only enforced on newer apps.
That said, if for whatever reason you want or need to install an outdated application, it will still be possible through a command shell, by using a new flag. Given the extra steps required, it’s less likely that someone would do this by mistake and inadvertently install malware.
How to install the Android 14 Beta on Google Pixel
After a few early developer previews, the Android 14 Beta program has officially arrived. Here’s how to get Android 14 on your Google Pixel smartphone.
What Pixel devices can install the Android 14 Beta?
Android 14 will drop another set of Pixel smartphones out of active support, but several will still be eligible. The following Pixel devices will be eligible for the Android 14 Beta program.
Pixel 4a 5G
Pixel 5
Pixel 5a
Pixel 6
Pixel 6 Pro
Pixel 6a
Pixel 7
Pixel 7 Pro
Pixel 7a
Pixel Fold
Pixel Tablet
While Pixel 7a, Pixel Fold, and Pixel Tablet joined the party late, they’re all eligible to test out Android 14 at this point.
What’s the latest Android 14 Beta build?
As of July 11, 2023, Google has just opened the fourth beta release of Android 14, one of the last big releases before the final release.
Google has scheduled a total of five beta releases through May, June, and July, with the final release likely to arrive in August.
Beta 1 (April): Initial beta-quality release, over-the-air update to early adopters who enroll in Android Beta.
Beta 2 (May): Incremental Beta-quality release.
Beta 3 (June): First Platform Stability milestone, including final APIs and behaviors. Play publishing also opens.
Beta 4 (July): Near-final builds for final testing.
Beta 5 (July): Near-final builds for final testing.
Final release: Android 14 release to AOSP and ecosystem.
This adds one additional beta compared to Android 13’s release schedule, which only had four beta releases.
Notably, some users have noticed that the first two beta releases of Android 14 have been a bit more erratic compared to previous years. We’d certainly advise caution if you plan to try the beta on a daily device. As usual, proceed at your own risk.
How to get Android 14 with the Android Beta Program
The easiest way to get Android 14 on your Google Pixel device today is through the Android Beta Program.
This automated program allows you to “opt-in” to Android beta updates and install them as you would a normal system update. There’s no computer or fancy tools required, and you can roll back to Android 13 any time you’d like by simply opting out.
How to sideload Android 14 Beta on Google Pixel
By far, the fastest way to get a new version of Android on your Pixel is to sideload it. It’s a relatively easy process, but you’ll need to get set up to do it. Here’s how.
Download the needed files.
Boot into Recovery mode.
Navigate to ADB sideload.
Connect the handset to a computer with ADB tools installed.
Enter the sideload command.
Reboot your phone.
1. Download Android 14 Beta files
To get started, you’ll first need to download the files needed to actually put the Android 14 Beta on your Pixel. There are two ways to do so. First, you can install a Factory Image, which wipes your phone and starts everything from scratch. Alternatively, and the way we’ll detail here, there’s an OTA file, which installs over your current version of Android without wiping your phone.
You can download the beta OTA file from Google’s Full OTA Image hosting site. That site contains OTA downloads for sideloading different updates, including the Android 14 Beta, on every Pixel and Nexus device, so you’ll need to scroll down to ensure you are downloading the file that associates with your device. OTA downloads are available here.
For the Android 14 Beta, only Pixel 4a 5G, Pixel 5a, Pixel 5, Pixel 6/Pro, Pixel 6a, Pixel 7/Pro, Pixel 7a, Pixel Fold, and Pixel Tablet are available.
You won’t be able to install it on the original Pixel/XL, Pixel 2/XL, Pixel 3/XL, Pixel 3a/XL, Pixel 4/XL, or Pixel 4a.
Note: This process (using OTA) won’t wipe your device, but it’s good practice to back up any irreplaceable data in case something goes wrong.
2. Boot into Recovery mode
Next, you’ll boot your Pixel into Recovery mode. To do this, fully power down your handset. Then hold down on the Power button and the Volume down button at the same time until you get to the Bootloader page. You will know you’re in the right place when you see an Android figure lying down on the screen.
Using your volume buttons, scroll down to Recovery mode. Select this by clicking the power button. Alternatively, if you’re already connected to a computer with ADB, you can use the reboot recovery command.
Now, you should see a smaller Android lying down with an exclamation mark over it. From here, press the Power button and the Volume up button for about a second to fully enter Recovery mode. Releasing the Volume up button will send you into Recovery.
3. Navigate to ADB sideload
Using the volume buttons, scroll down to Apply update from ADB and select it with the power button. This will launch a mostly blank screen with text near the bottom directing you on how to sideload an OTA, such as this one for the Android 12L Beta.
4. Connect the handset to a computer with ADB tools installed
This step is important as it’s the only way to transfer the downloaded OTA file to your handset. You’ll need to have ADB and Fastboot tools in a handy place. You can download ADB tools from the Android Developers website. You can also use the Universal ADB Drivers from ClockWorkMod, which can make the process a bit easier on Windows devices.
5. Enter the sideload command
As long as everything is in place, you can now sideload the OTA file. On Windows, ensure your Command Prompt is directed to the ADB tools folder and type in adb sideload. If you’re on macOS or Linux, do the same thing in Terminal (use “cd” and “ls” commands to make sure your Terminal is pointed at the right folder – Google it if you need help) but type in ./adb sideload. You’ll then need to insert the file name of the .zip folder you downloaded from Google and hit enter to start the process.
If everything is working properly, you should see some dialog on your computer and handset that shows the process of the sideload and installation process.
6. Reboot your phone
Once the OTA is done installing, you will be taken back to Recovery Mode. The last step to jump into the new update is to select the Reboot now option with your power button.
Android 14 Beta tweaks and widens the share sheet
In recent weeks, the Android 14 Beta has steadily tweaked the share sheet to look cleaner and show more options.
Despite being a central component of Android, the share sheet has long been one of the weaker points of Google’s mobile operating system. The share sheet has gone through numerous iterations over the years, each one aiming to make it faster or better in some way, though sharing on Android still remains surprisingly slow.
Over the course of the Android 14 Beta, Google has made some changes to the share sheet. One more noticeable change, arriving with Beta 3, is that the share sheet is now five icons wide (up from four) on typical phones. This makes more options visible on screen at a time and is a shift toward more density rather than the extra blank space that some Material You designs have opted to take. As always, you can scroll the sheet to view the full list of available share targets.
Meanwhile, another tweak arrived with this week’s Android 14 Beta 4 release. The sheet now also includes a title that explains what you’d actually be doing. For example, if you choose to share a website from Chrome, you’ll see “Sharing a link” with the actual URL below it.
If you’re sharing any text, a shortcut to copy it to your clipboard will appear on the right-hand side. Similarly, when sharing an image, you’ll be offered an option (pencil icon) to first edit it in Markup.
Android 14 Beta 4 changes ‘Muted’ status icon design
Android 14 Beta 4 is here and small tidbits and changes are surfacing as we dig through the new OS version. One such change is a completely new design for the “Muted” status, leaving behind the familiar bell icon for a more modern look.
Most Android devices have three sound states: sound on, vibrate, and silent. While each person has their preference as to which they leave their phone set to, only one of those displays a status icon in the top bar, next to the WiFi and battery readouts.
In Android 14 Beta 4, a Pixel phone or other device set to silent or “muted” will now display a small yet very familiar speaker icon. This switch replaces the bell icon we’ve seen in past Android builds. The change makes a little bit of sense, as the bell could be seen as confusing to some, though it’s a very small adjustment.
In Android 14 Beta 4, no other sound states offer a status icon. The “muted” state remains the only one to reflect in the status bar, though a status icon for vibrate and sound on would be nice.
Another spot the icon is updated with the speaker silhouette is in the slider that appears when pressing the volume rockers. Instead of a ball icon and another with a slash through it, there is now one speaker icon and another with a slash, representing mute.
This change to the mute icon in Android 14 is anything but huge, but it’s notable nonetheless and offers a little insight into the changes being made between versions. Be sure to stay tuned for more Android 14 news as it’s uncovered.
Don’t get a Pixel 7 – pick the Pixel 7a instead. That more or less summarized our thoughts from our initial encounter with Google‘s latest a-series smartphone, and we’re here now with the full review to establish how correct that early assessment was.
It’s a pretty natural conclusion that anyone can arrive at, really, even by simply looking at the specsheet – and, simultaneously, at the pricelist. The Pixel 7a gets closer to the ‘high-end’ models than any previous offering with an ‘a’ in its name, and comes in at a not-insignificant $100/€100 less (or thereabout, depending on who you ask and at what time) – what’s not to like? But let’s not put the verdict before the review.
The Pixel 7a improves on some key areas that held the 6a back. Perhaps most importantly, you now get a 90Hz display in place of the old model’s dated 60Hz unit. Yes, the bulk of the competition is at 120Hz already, but the jump from 60 to 90 is the most noticeable from a usability perspective, so maybe we can give the 7a a pass.
The camera system gets a boost too. A new 64MP Quad Bayer main unit replaces the basic 12.2MP one of the 6a – those are more pixels than you’d get with a Pixel 7 (50MP), even though it’s a smaller sensor. Similarly, the 13MP ultrawide is also higher-res (if only just) than the one on the 6a and the 7, albeit with a smaller sensor. There’s no AF on this one, but then it’s only the 7 Pro that has an autofocusing ultrawide, so the 7a doesn’t really lose points here against the 7. The selfie camera is another 13MP affair, that one too being nominally superior to its brethren’s setups.
A noteworthy addition to the a-series feature set is wireless charging. You may scoff at the 7.5W throughput, but you’re unlikely to be in a hurry when sleeping. And it’s not like Pixels are known for fast charging to begin with.
You get the same Tensor G2 chipset on the Pixel 7a that the 7 comes with. While it’s somewhat underpowered compared to other high-end SoCs that the 7 is fighting against, it looks a lot better in the 7a’s context.
Battery capacity is essentially the same between the two models, and the 7a may eke out a few extra minutes of battery life thanks to its slightly smaller display and lower max refresh rate – we’ll see in due time if less ends up being more in this respect.
Less is less in the 7a’s IP rating, but the IP67 should be as good as the 7’s IP68 for that one-time accidental bathroom dunk. The lack of a storage option other than 128GB isn’t as easy to dismiss, though – maybe the 256GB version remains the key thing the 7 has going for it in this head-to-head.
Disclaimer. We can not guarantee that the information on this page is 100% correct.
Google Pixel 7a unboxing
We’ve come to expect minimal bundles from certain companies, and Google is one of them. It’s no surprise then, that the Pixel 7a ships in a box that’s barely larger than the handset itself. The two-piece white cardboard package has a likeness of the phone on lid, color-matched to the actual unit inside.
The contents include a USB-C cable and USB-C male to USB-A female adapter – standard Google stuff. There’s no charger inside, but on some markets you may get Google’s 30W adapter (in its own separate retail packaging) included in the price – that was the case with our German review unit. We did get ours from a third-party retailer, as opposed to the Google online store, and not all retailers appear to be running the same promo. Chances are you’ll be needing to come up with your own charger, is what we’re saying.
Now, while the charger situation is not exclusive to the Pixel 7a, a lot of competitors in the segment do come with adapters in the box. A bundled protective case is also not unheard of. Perhaps a value-oriented consumer like the ones eyeing a 7a would appreciate getting a bit more for their money.
Competition
The Pixel 7a comes in at $500/€510 and that’s quite a heavily contested market segment. Google doesn’t like to sell its phones in more than a handful of markets though, so if you’re outside the select few countries with Pixel presence, things will be easily settled for you. But if Pixels are on the table, there will be some thinking to do.
For starters, you’ll need to consider the Pixel 7a’s in-house competition – an easy enough task. While it remains on sale, the 6a comes with a dated 60Hz display, previous-gen chipset, inferior camera and no wireless charging – we reckon the extra $100/€100 for the 7a are well worth spending. That said, we’re seeing $350/€350 promotional price tags on the 6a, and that calls for some more serious cost/benefit analysis.
It’s probably easier against the Pixel 7 – basically, if you don’t need more on-board storage than the 128GB 7a gives you, the 7 doesn’t really have much to justify the $100/€100 premium. And, technically, if you do insist on the 256GB of storage, you’d be looking at a $200/€200 extra over the 7a, which seems like a lot of money to pay for a storage upgrade.
The 7 Pro has gotten some heavy discounts, particularly in Europe, but it’s still a good deal more expensive than the 7a, so it doesn’t feel right to consider it an alternative to the 7a.
Google Pixel 6a • Google Pixel 7
Outside of Google‘s own roster, the very recent Motorola Edge 40 sounds like a very enticing alternative to the Pixel 7a. Sort of a ‘stock’ Android experience, but with Motorola’s own proprietary additions, the Edge 40 is similar, yet different enough to attract its own crowd thanks in part to the PC-like ‘Ready For’ functionality. It’s not really worse at anything, while being at least as good and often better than the Pixel in key areas – AF-enabled ultrawide, proper fast charging, way higher refresh rate display, actually good selfies, 256GB of storage. The Edge 40 is also as close as you can get to a capable midranger that’s also compact – something the Pixel ‘a’ can no longer claim.
The Moto does have a higher MSRP at launch, and it could be argued it’s worth the added cost. But we feel like its price is going to come down to Pixel 7a levels soon enough, and, unless you’re dead-set on having Pixel software, the Edge 40 sounds like the overall better package.
There’s no need to wait for a price drop with the Galaxy A54 – that’s already going for $100/€100 below Pixel 7a’s price. The biggest concession with the Galaxy would be performance – its mid-tier Exynos can’t quite match the Pixel’s kinda-flagship Tensor. The Galaxy does score a few small victories, like having expandable storage and longer battery life. We’d pick the Pixel for its cameraphone prowess, and the Galaxy if you’re after more of generally good smartphone.
The Nothing Phone (1) is another alternative that runs cheaper than the Pixel – at about the A54’s level. Alongside the savings, the blinky LED back of the Phone (1) is a major selling point, irrational as it may sound, but Nothing’s first… phone is not without objective merits. While we wouldn’t say it’s dramatically better than the 7a at anything, it’s a little better here and there – refresh rate, battery life, charging speed. The Pixel is again the better cameraphone, generally speaking, is bound to get way better software support, and has superior weather sealing (IP67 vs. IP53).
The appeal of Pixel phones tends to be pretty niche, often not entirely well-founded in reason, and difficult to explain with just numbers and test results. It’s somewhat of a similar story with the Pixel 7a here, as a quick look at the pros and cons lists below will show you.
Google hasn’t been quick to adopt a high refresh rate display on its ‘midrange’ model and even when it finally has, it’s a 90Hz panel in a sea of higher RR competitors. Battery life is unremarkable, charging speed is downright unacceptable, the lack of storage options is limiting, and the Tensor G2 runs hot and throttles. There are also missteps in what should be any Pixel’s forte – camera performance.
Attempting to counter all of the above, we have an Android experience tailored to Google’s own vision with a clutter-free interface, Pixel-only features, and an update policy that’s hard to rival. An otherwise meh flagship chipset does make for a pretty great midrange one, prone to throttling as it may be. And so long as you avoid people shots in most of their incarnations, the Pixel 7a’s camera’s system will deliver image quality that wouldn’t be out of place on an actual flagship.
In summary, with the 7a, Google appears to have simply created a more affordable Pixel 7, making the latest a-series model the go-to option for someone just looking for a Pixel. If the ‘G’ logo on the back is not part of your requirements, perhaps there are better deals out there. Perhaps you’ll be missing out though.
