A year after Apple Music first became available on GoogleNest and Home devices, the streaming service is now supported in five more countries.
Australia, Canada, India, Mexico, and South Korea join the US, UK, France, Germany, and Japan. To enable Apple Music, open the Google Home app (Android or iOS) > the Settings gear > (under Services at the bottom) “Music.” You can also open Google Assistant settings and scroll down to “Music.”
Tap the blue link/chain icon next to “Apple Music” and agree to “Link Account.” You’ll be sent to an Apple website where you can enter Apple ID credentials. Once complete, requests to Google Assistant for songs and albums will automatically play in Apple Music.
After it is set up, you can easily queue up your favorite playlist, artist, or any of the award-winning Apple Music Radio stations live streaming today’s hits, classics, and country to play over your connected device.
Stateside, supported streaming services include YouTube Music, Spotify, Apple Music, Pandora, Deezer, and iHeartRadio. Apple’s Android app also supports Casting, while there’s still no TV+ app to watch original content despite the presence of an Android TV client.
There was no YouTube Rewind in 2020, and the Google company announced in October that the series was coming to an end entirely. That said, YouTube is still doing various “top” video lists for 2021.
YouTube has always offered an annual list of the top trending videos to accompany the broader compilation featuring the platform’s biggest personalities and trends. The former is easier to compile and follows one from the Google Play Store earlier this week for the best Android apps and games.
The US results, along with top creators, are below. Meanwhile, there’s a separate list for the top YouTube Shorts creators (again in the US).
The Google Pixel 5a is the third iteration of Google’s Pixel “a” Series: smartphones based on the Google Pixel experience made with lower-cost entry points in mind. There’s also now more emphasis on battery life and water resistance. The latter is a welcome feature to the “a” Pixel family. The phone Is very similar to the Pixel 4a 5G in size, appearance, and specs. They aren’t identical, but pretty darn close.
Although it has the same chipset, RAM, and layout, the dimensions are slightly different, less than a millimeter difference in each dimension. The battery capacity is significantly better: about 15% more capacity than the Pixel 4a 5G. The phone’s construction is now made of a sturdier aluminum and resin unibody construction like the Pixel 5. The new build is also IP67 water resistant.
Google Pixel 5a 5G specs at a glance:
Body: 154.9×73.7×7.6mm, 183g; Glass front (Gorilla Glass 3), aluminum/plastic unibody; IP67 dust/water resistant (up to 1m for 30 mins).
The Google Pixel’s cameras are of the biggest selling points for the Pixel phones, but you’ll soon learn that its hardware is exactly the same as the 4a 5G and the Pixel 5’s, verbatim. We don’t anticipate there to be any significant difference in camera quality. Performance is also predictably decent on the Snapdragon 765G paired with 6GB of RAM.
These changes do come with a price hike. The Pixel 5a is the most expensive “a” series ever at $449, but will the improvements to the hardware retain their value in the long term? Is the Pixel 5a a solid entry into the Pixel family?
Let’s start answering that by opening the box first and see what’s inside.
Unboxing
The packaging is similar to what we’ve seen from Google for years. The box shows a photo of the Pixel 5a to actual size and the phone lays face down when you pull the lid off.
Under the plastic-wrapped Pixel 5a you’ll find a USB-C to C charging cable, an 18W USB-C charger, and a USB-C to USB-A adapter which Google calls its “Quick Switch Adapter”. This lets you transfer data from another phone to the Pixel 5a.
Competitors
For the competitors, we’ve only listed devices close to the Pixel’s price range that are only available in the US. Starting with Google’s own, the Pixel 4a makes a case for an affordable and compact smartphone with solid performance. The 4a is $100 cheaper than the 5a 5G but doesn’t support 5G and omits the ultra-wide camera.
Google Pixel 4a
Samsung’s Galaxy A52 5G is just a bit more at $499, and while we did like it for its 120Hz display solid quad-camera setup, microSD support, and 3.5mm headphone jack, it would be better suited at a discount.
Samsung Galaxy A52 5G
Apple’s closest offering is a nearly three-year-old device that’s still a nice value today. Even though the iPhone XR has no 5G support nor an ultra-wide camera, it has great battery life and a very capable single-cam setup. Besides, Apple is sure to support the XR for at least another couple of years of iOS updates. The iPhone 11 starts at $50 more and adds an ultra-wide camera.
Apple iPhone XR
Apple iPhone 11
As one reader pointed out, there’s another competitor worth mentioning here. The Sony Xperia 10 III, although not officially available from Sony in the US, can easily be purchased from Amazon. Though you’ll be looking at the International variant, so no Verizon.
The Xperia 10 III is priced around $400 and comes with the same RAM and Storage as the Pixel. It’s powered by the Snapdragon 690G, is more compact with its 6-inch display, the best dedicated zoom camera in its class, and it has IP68 water resistance. There’s also a headphone jack, microSD expansion, and 30W fast charging with impressive battery life.
Sony Xperia 10 III
The choice for alternatives in this range is slim, hence Google’s decision to limit the release to two markets.
Verdict
The Pixel 5a is an interesting price point of $449 in the US. While It’s a shame the phone isn’t available outside of the US and Japan, it doesn’t make sense for Google to launch the Pixel 5a outside of these markets since the competition and alternative devices are not as threatening as they are in other markets like the EU and India.
The Google Pixel 5a could have been a more compelling smartphone had it arrived with an LTE chipset instead of the Snapdragon 765G. Thus, it could have been sold at $349 or maybe even $399 to directly compete with the iPhone SE.
The Pixel 5a is essentially a repackaged Pixel 5 with a larger screen and significantly better battery life, but no wireless charging. It feels like Google could have released this device earlier in the year to stagger it further from the imminent launch of the Google Pixel 6 duo.
Google Chrome is an extremely powerful web browser. It becomes even more capable once you start adding extensions to make tasks easier and faster. Though, if you’re switching your default browser to Google Chrome on Windows 11, there are a few things to keep in mind.
Why use Google Chrome in the first place?
There are a few convincing features that you can find with Google’s web browser. First off, Google Chrome easily syncs across platforms. History, bookmarks, addresses, and passwords all sync between devices. This means you could securely log in to a website on a Samsung Galaxy S21 with a new password, and the next time you log in on a PC running Windows 11 with Chrome, you’ll have your password safely stored for easy access. It doesn’t matter what device Chrome is being used on; it will still have all of your data available.
Another reason – and probably the main reason for many – is the speed of Google Chrome. As long as extensions are kept in check, and generally less than 100 tabs are open, Google Chrome will maintain surprisingly quick speeds. As far as extensions go, there are thousands on the Chrome Web Store, and each has a specific use. They can range from quick shortcuts to website functions or even allow you to download a PNG or JPG from any website. The support Google Chrome has for extensions is phenomenal and makes the browser more useful.
In general, Chrome is quick to adopt new standards as well. Since what the internet has to offer and even how it offers it is constantly changing, a browser needs to be up to date and relevant. Chrome does that very well. On top of that, Google has committed itself to regular updates for security and quality of life reasons. Because of this, Chrome offers a bit more than Microsoft Edge when it comes to security.
Setting up Google Chrome in Windows 11 as the default browser
While past iterations of Windows let you set up Google Chrome as the default browser with one or two clicks, that isn’t the case anymore with Windows 11. Previously, users could select it as a default browser and any file type associated with internet browsers would automatically open in Google Chrome. In Windows 11, users need to specify what program to use for each individual file type. In theory and in practice, just changing the default program from Edge to Chrome for an .HTM file will not change it for an .HTML file type. The .HTML default app needs to be set to Google Chrome as well, otherwise, you’ll find yourself randomly opening Microsoft Edge when you thought Google Chrome was the default.
That being said, here’s where you can go to fix that:
Head into Settings in Windows 11. You can do this by clicking Start and then the gear icon on the right-hand side.
On the left side, find and click Apps. Within that section, click on Default apps.
Scroll down until you find Google Chrome – assuming it’s already installed – and click it.
This page lets you change Google Chrome to the default for each of these file types. Now, you don’t actually have to set each and every one of them to Google Chrome, and it isn’t necessarily advised. For instance, you may want to set .PDF’s to open with a PDF editor instead of Google Chrome.
The easiest way to go about setting Google Chrome as the default browser is to just change the file types that are already set to Microsoft Edge. This will ensure that instead of file types opening up Edge, Google Chrome will appear. To change a file type’s default, just click the current default app and look for Google Chrome in the windows that appear. Select it, and hit ok.
The process only takes a couple of minutes but saves a lot of time in the future. Though, we still wish it was as easy as it was in Windows 10. All in all, anytime you open up a file type associated with a web browser, it should open up your new default browser in Windows 11, Google Chrome.
Google is rolling out a trio of productivity updates to its iPhone and iPad productivity apps. Notably, Gmail will get a homescreen widget, while iOS Picture-in-Picture is now available for Google Meet.
Gmail is getting another widget on iOS after the original was quietly removed sometime in the past year. The screenshot Google shared today shows your inbox with three recent emails that note the sender and subject.
What account they originate from is highlighted in the top-left corner by your profile picture, while there’s a compose FAB at the left. Functionality-wise, it’s identical to the Android version, which is due for a Material You overhaul. The iOS widget will be available in Gmail over the “next few weeks.”
Meanwhile, Google recently added Picture-in-Picture support to Meet. It’s a fairly standard implementation with the ability to resize the window. A PiP is also coming to the integrated video calling experience in mobile Gmail over the “next few weeks.”
For example, you might want to forward an email, share a document or just look something up while you’re chatting. Simply navigate out of the Google Meet app, and your meeting will be minimized in a window that you can move around your Home Screen.
The last upcoming update will see Google Sheets add support for shortcuts — hold down the command key to see a list of available ones:
Shortcuts make it easier to complete common and advanced tasks on Google Sheets using a small keyboard — like selecting a whole row or finding and replacing certain values.
Google is all-in on Rich Communication Services (RCS) as its main consumer messaging strategy. That said, Google Messages is working on the ability to have video usually sent over MMS be sent using Google Photos instead.
About APK Insight: In this “APK Insight” post, we’ve decompiled the latest version of an application that Google uploaded to the Play Store. When we decompile these files (called APKs, in the case of Android apps), we’re able to see various lines of code within that hint at possible future features. Keep in mind that Google may or may not ever ship these features, and our interpretation of what they are may be imperfect. We’ll try to enable those that are closer to being finished, however, to show you how they’ll look in case that they do ship. With that in mind, read on.
The Google Messages 10.4 beta reveals work, which looks to just be getting underway, on this capability. We’ve enabled a new preference in Settings called “Google Photos”:
Share sharper clarity video in text (SMS/MMS)
From that brief description, it seems that users will be able to send a video over Google Photos instead of using MMS when in a text/SMS conversation. This will presumably involve the video being uploaded directly to Google Photos with the other user receiving a link, rather than the video itself going over the SMS/MMS network.
There could be some integration where the clip plays directly in the Messages app instead of taking users to Photos, or it could be the standard Photos sharing URL. Another question is how integrated this experience will be in regards to sharing permissions and avoiding duplicate uploads. For instance, will videos sent via Messages appear in the Google Photos “Sharing” tab?
With RCS adoption increasing in the future, this capability, if it launches, makes for an interesting stopgap measure. When you send images and videos as “chats,” they are uploaded to the cloud, and the recipient, behind the scenes, receives a link that automatically loads/plays in Messages. Quality is already a solved problem in RCS.
Then again, MMS video quality is quite bad, and any improvement would be a meaningful upgrade for users.
One of the best features of Google Pixel phones is Call Screen, an easy way to handle spam calls without actually picking up the phone. This week, the feature is officially expanding past the US, Canada, and Japan to seven new regions.
Flying under the radar on Pixel 6 launch day last week, Google quietly revealed that Call Screen would expand to seven more countries. These countries specifically include:
UK
France
Germany
Australia
Ireland
Italy
Spain
We’ve since found that the feature was rolling out in the UK early this week and reports have since come in from France, Australia, and Germany.
It’s worth noting that the feature is limited in these additional countries compared to how it works in the US, Canada, and Japan. Call Screen on Pixel phones in these countries will be limited to its manual form, rather than supporting the automatic screening feature that allows the phone to detect spam calls on its own and screen those on your behalf. That option was first rolled out to Pixel owners in the US at the end of 2019.
Call Screen helps users in the U.S., Canada and Japan screen 37 million calls each month, and today we’re expanding manual Call Screen to Pixel users in the U.K., France, Germany, Australia, Ireland, Italy and Spain. Our latest on-device speech models make the transcriptions more accurate than ever on Pixel 6 and Pixel 6 Pro thanks to Pixel’s new Google Tensor.
With Android 12 hitting AOSP at the start of the month, Google also released the latest Compatibility Definition Document (CDD). There are a handful of hardware and software changes that device makers have to abide by, but nothing too major.
With Android 12, Google introduced a “Performance class” standard that “defines a set of device capabilities that goes beyond Android’s baseline requirements.” This includes media, camera, and “generic” (memory, screen resolution/density).
It lets app developers determine which software features a phone or tablet is capable of running. For example, Performance class 12 (for the “highest performing devices”) could get the “most premium experience,” while class 11 would go down to “high quality experience” and everything else gets the base experience. Meanwhile, Performance classes are forward-compatible:
A device can upgrade to a newer platform version without updating its performance class. For example, a device that initially supports performance class 12 can upgrade to Android 13 and continue to report it supports class 12 if it does not meet the class 13 requirements.
The Android 12 CDD says that Performance class 11 (R) and 12 (S) “must” at least have a 12MP rear camera that supports 4K at 30FPS video capture. The latter also requires a 5MP or higher front-facer (1080p at 30FPS), while the former needs at least 4MP. Both classes require a screen resolution of 1080p (with 400DPI) or greater and a minimum RAM requirement of 6GB. Sequential and random read/write are also specified:
Meanwhile, OEMs must display the microphone and camera indicators when those two components are being used by apps, including system ones. Under “Unicode and Font,” Google added that device makers:
MUST NOT remove or modify NotoColorEmoji.tff in the system image. (It is acceptable to add a new emoji font to override emoji in NotoColorEmoji.tff)
A “strong” recommendation has been added about making sure the touchable area of an under-display fingerprint sensor (UDFPS) does not interfere with 3-button navigation, which Google reminds that “some users might require for accessibility.”
Last year, Android 11 introduced a clever privacy feature that removes permissions granted to “unused apps” that haven’t been opened in some time. Google is now bringing this auto-reset to older phones and tablets via Play services over the coming months.
Android 11 (and newer) can automatically remove permissions from “unused apps” to limit access to sensitive personal data, including location, camera, contacts, files, microphone, and phone. This does not get in the way of day-to-day usage as you have to go at least three months without using an application before Android automatically removes permissions.
Google is now bringing permission auto-reset to “billions more devices” running Android 6.0 Marshmallow to Android 10. This is made possible with Google Play services.
Once rolled out, auto-reset will be enabled by default for apps targeting Android 11 (API level 30) and later. To prevent issues and unintended experiences, resets will not apply to older applications still targeting API levels 23-29 unless manually enabled by end users. Additionally:
Some apps and permissions are automatically exempted from revocation, like active Device Administrator apps used by enterprises, and permissions fixed by enterprise policy.
Meanwhile, developers can ask users to “prevent the system from resetting their app’s permissions.”
This is useful in situations where users expect the app to work primarily in the background, even without interacting with it. The main use cases are listed here.
Next month, Google will make the cross-platform auto-reset APIs available with Jetpack Core 1.7.0, while the company today issued guidance on how developers can prepare.
Android’s auto-reset feature will begin gradually rolling out in December and be fully available in Q1 2022. Once live, users will get a new auto-reset settings page to enable/disable the behavior for specific applications. A few weeks after that, Google will start resetting permissions from unused apps.
Breaking from the recent yearly release cadence, the next version of Android to release might be a mid-cycle bump — an “Android 12.1,” if you will — rather than Android 13.
By all measures, Android 12 is a significant release for Google’s phones, among other things, revamping the design with “Material You,” which matches the system and your apps to your wallpaper’s colors. In the coming months, we should see more of how Android 12 will improve other companies’ phones, with Samsung set to beta test One UI 4.0 in the next few weeks.
Normally, this would be about the time that we should set our sights on 2022’s Android release, presumed to be Android 13. In fact, Android 13’s internal dessert name, Tiramisu, has been discovered.
However, it seems there may be another stop in the journey. As tipped to XDA by luca020400 (Director of the Lineage OS ROM), a new Android code change suggests that Tiramisu/Android 13 will be API level 33, which is two levels higher than the forthcoming Android 12, which will be API 31. 9to5Google has also discovered a newer code change that directly confirms that Android 13 will be API 33.
More than that, it’s directly stated that API level 32 will be “sc-v2.” In this instance, “sc” is shorthand for Android 12’s internal dessert name, “Snow Cone,” while “v2” implies that Snow Cone will get a “version 2.”
In almost every case over the last 13 years of Android’s history, a change to the API level has coincided with a change to Android’s version number. However, this would be the first time since 2017 that Google has felt the need to put out a second, mid-cycle upgrade for a particular Android version.
At that time, Android Oreo got a bump from 8.0 to 8.1 at the end of the year, with the update debuting on Pixel and Nexus phones. A similar mid-cycle “x.1” release schedule also occurred following Android Nougat and Lollipop. Following that pattern, it’s quite possible that this “sc-v2” update might be called “Android 12.1” when it launches.
So what can we expect from such an Android 12.1 upgrade? Whatever is changing must be both important enough to justify a mid-cycle release, and also drastic enough that Google couldn’t add it all to Android 12 while keeping the API stable for developers.
For now, there aren’t many clues to go on, especially as more parts of Android have become updatable without needing a major upgrade, thanks to Mainline modules. In a comment on another code change, we see that “sc-v2” will introduce some tweaks to the WindowManager APIs, which would definitely affect app developers.
It’s too early to say when this supposed Android 12.1 would release, but the earliest available evidence suggests Google has been preparing it since at least May. In past examples of a mid-cycle release, the new Android version bump would see release within a few months of the major version’s launch.
Another tidbit you’ll probably have noticed in the quote above is that a Googler mentions that “some of our Nest devices might not be migrated to T.” For now, we’re not too sure what to make of this, as no known Nest devices run on Android — let alone have potential to upgrade to Android 13 (T) — with the Nest Hub series using either Cast OS or Fuchsia. It’s possible this may simply be referring to the Chromecast with Google TV, which could be seen as falling under the Nest umbrella.
