Android Archive

After many leaks, official teases, and months of waiting, Google has finally given its latest Pixel phones a formal launch. The new Pixel 6 and Pixel 6 Pro are the latest high-end phones from the company that hasn’t traditionally been able to make much of a dent in the high-end phone market. Both are available for preorder starting today, October 19th, and will begin shipping on October 28th. Google says all the major US carriers, plus retailers such as the Google Store, Best Buy, Amazon, Walmart, Costco, and others, will be selling the phones. There are a lot of things to cover with the new Pixels, but the most important place to start is this: $599 and $899. Those are the starting prices for the Pixel 6 and 6 Pro, respectively. That pricing is aggressive compared to similar iPhones, Samsungs, or even OnePlus phones, especially when you consider that Google is providing 128GB of storage in both base models. (The 6 can be equipped with up to 256GB, the 6 Pro has options up to 512GB.) Ars Technica has more on the new Tensor SoC by Google that powers these new Pixels. I’d love to say more about these new Pixels, but Google refuses to actually sell them anywhere, so I’m not even sure Pixel phones even exist in the first place. I’m not into conspiracy theories, but until Google sells these things in more than like 3 countries, I’ll just keep calling them an elaborate hoax.

Today we’re pushing the source to the Android Open Source Project (AOSP) and officially releasing the latest version of Android. Keep an eye out for Android 12 coming to a device near you starting with Pixel in the next few weeks and Samsung Galaxy, OnePlus, Oppo, Realme, Tecno, Vivo, and Xiaomi devices later this year. The first Android 12 reviews have rolled out too, and the conclusion seems to be that this new release focuses heavily on overhauling the look and feel of Android, without disrupting how you actually use your phone all that much. Android 12 isn’t an update that’s trying to change how you use your phone — not that it needed to be. Instead of just tacking on dozens of new features, Google just wanted to shake things up in the design department for the sake of it. It’s an upheaval of some of Android’s smallest details. It amounts to a more customizable experience, which in turn lets your phone look and feel more unique. If that gets you excited, you probably won’t regret installing. But I wouldn’t buy a Pixel just to experience Android 12. And if you can’t get the update today, I wouldn’t fret too much until more features are added. I’m definitely excited to experience the new look and feel, but it will be a while before any of my devices gets the update.

Like the good (and quickly abandoned) Android tablet interfaces of yore, Android 12.1 sees Google return to dual-pane layouts for various bits of the OS interface. The settings screen is back to a dual-pane configuration, which has the top-level settings list on the left and each individual page of settings on the right. The notification panel takes a similar approach, with the quick settings on the left and the normal list of notifications on the right. Google’s leaked dock interface is here, too. The screenshots all have a pinned black bar at the bottom of the screen, making for a hybrid of the iPad’s new dock UI and the old Honeycomb bar. Of course, everything could change eventually, but for now, the icons at the bottom just seem to be your recent apps. Being able to pin apps to this bar would be nice, too. The dock, assuming it doesn’t auto-hide, will cut into the vertical real-estate apps have access to. Vertical space is currently a big problem for apps on foldables, especially when you aren’t in side-by-side app mode. Some interesting changes here, which are definitely sorely needed for Android tablets and tablet-like devices.

The Linux Plumbers Conference is this week, and since Android is one of the biggest distributors of the Linux kernel in the world, Google software engineer Todd Kjos stopped by for a progress report from the Android team. Android 12—which will be out any day now—promises to bring Android closer than ever to mainline Linux by shipping Google’s “Generic Kernel Image” (GKI) to end-users. This is a big issue, and I’m glad Google and the Android team are addressing it. Hopefully, we will eventually end up in a situation where the Android kernel and the mainline Linux kernel are far, far closer to each other than they are now.

Android 12 Beta 5 is here. For those that haven’t been following along at home, this is the last expected release before it hits stable and is ready for the masses — a so-called “release candidate” version that should be almost good to go. This latest version also picks up support for the brand new Pixel 5a, and it’s your last chance to get those beta-testing toes wet before Android 12 is released. On that note, Google also gives us a hint about its schedule, promising that Android 12 is “just a few weeks away.” Well, a few weeks away for a very small number of phones. For most users, this release is months away, at best, and infinity away, at worst.

Samsung has confirmed that it will stop showing ads in default apps including Samsung Weather, Samsung Pay, and Samsung Theme. It follows comments made by its mobile chief TM Roh in an internal town hall meeting reported by Yonhap. “Samsung has made a decision to cease the advertisement on proprietary apps including Samsung Weather, Samsung Pay, and Samsung Theme,” the company said in a statement given to The Verge. “The update will be ready by later this year.” I never got any of these ads on my Samsung Galaxy Note 10+, but I’d be absolutely livid if I did. I’m not going to commend Samsung for doing the absolutely bare minimum here and not show ads on €1000 devices. Dear lord.

Google is announcing the Pixel 6 and Pixel 6 Pro today, though it might be better to call it a preview or a tease. Rather than releasing all the details on its new Android phones, Google is instead putting the focus on the new system on a chip (SoC) that will be inside the new Pixels. It’s called the Tensor SoC, named after the Tensor Processing Units (TPU) Google uses in its data centers. Tensor is an SoC, not a single processor. And so while it’s fair to call it Google-designed, it’s also still unclear which components are Google-made and which are licensed from others. Two things are definitely coming from Google: a mobile TPU for AI operations and a new Titan M2 chip for security. The rest, including the CPU, GPU, and 5G modem, are all still a mystery. Less mysterious: the phones themselves. I spent about an hour at Google’s Mountain View campus last week looking at the phone hardware and talking with Google’s hardware chief Rick Osterloh about Tensor. After all that, my main takeaway about the new Pixel 6 phones is simple. Google is actually, finally trying to make a competitive flagship phone. This looks like a really premium product, and it will most definitely have a price to match. Google finally switching over to its own SoC, after years of relying on Qualcomm, which is technically great for competition, but much as with Apple’s chips, it’s not like anyone else is really going to benefit from this. Assuming Google plans on selling this new Pixel in more than three countries, and assuming the claims about the cameras are backed up my real-world reviews, this will definitely be my next phone, since my current smartphone is ready for replacement. And what a surprise – smartphone camera quality suddenly matters now that I have a kid.

Today, we’re announcing additional details for the upcoming safety section in Google Play. At Google, we know that feeling safe online comes from using products that are secure by default, private by design, and give users control over their data. This new safety section will provide developers a simple way to showcase their app’s overall safety. Developers will be able to give users deeper insight into their privacy and security practices, as well as explain the data the app may collect and why — all before users install the app. Ultimately, all Google Play store apps will be required to share information in the safety section. We want to give developers plenty of time to adapt to these changes, so we’re sharing more information about the data type definitions, user journey, and policy requirements of this new feature. This basically means Android and the Play Store are getting the same kind of privacy labels as Apple introduced in iOS and the App Store. This is competition at work, and it’s great that both platforms will soon offer this feature.

After announcing that OnePlus and Oppo would be merging more teams behind the scenes, the inevitable has happened. OnePlus has just announced that OxygenOS and ColorOS will come closer together, though with the benefit of OnePlus devices getting three years or more of Android updates. In a forum post today, OnePlus explains that the sub-brand of Oppo is “working on integrating the codebase of OxygenOS and ColorOS.” Apparently, the change will go unnoticed because it is happening behind the scenes. OnePlus’ OxygenOS has always been the darling among Android fans, because not only is it very close to stock Android, it also has great performance and (usually) a good update schedule. Oppo’s ColorOS, on the other hand, is none of that. I’m very skeptical of this merger turning out for the better for OnePlus users.

For as long as Android has been around, Android apps have been launched in the APK format (which stands for Android Package). However, in 2018, Google introduced a new format called Android App Bundles, or AAB (with the filename *.aab). Google touted that this new format would result in smaller app file sizes and easier ways to control various aspects of apps. Of the millions of apps on the Google Play Store, thousands of them already use the AAB system. Today, Google announced that the AAB format will now officially replace Android APKs. This means that starting in August of this year, all new apps submitted to the Google Play Store must come in the AAB format. Apps that are currently APKs can stay that way — at least for now. Alright, where’s the catch? There’s going to be a catch, right? Unlike APKs, Android App Bundles cannot exist outside of Google Play and cannot be distributed outside of it. This means that developers switching from APK to App Bundles can no longer provide the exact same package or experience on other app sources unless they opt to maintain a separate APK version. This naturally puts third-party app stores at a disadvantage, but Google will most likely play up the Play Store’s security as a major reason to avoid those sources anyway. There it is! Of course any technological step forward in the modern monopolised world of technology has to come with anti-consumer features or limitations that take control away from users. It’s like a law.

So to recap: yesterday, Huawei was shipping smartwatches using LiteOS, and today, it’s shipping smartwatches with “HarmonyOS,” which is based on LiteOS. Yesterday, it was shipping phones and tablets using a forked version of Android without Google services. Today, Huawei is shipping “HarmonyOS” on phones and tablets, which is forked Android without Google services. Did anything actually change here? That about sums it up. We were promised a brand new operating system, but in reality, all they gave us is yet another Android fork, of which there are countless.

At Google I/O today, Google unveiled more about Android 12, and the biggest change is a complete visual overhaul of the operating system. It’s called Material You, and it’s radically different from what Android looks and feels like today. Every visual and animated aspect of the operating system seems to have been changed. Some examples: Wallpaper-based theming — or “color extraction” as Google calls it — brings bold color combinations to every corner of the OS. It automatically decides which hues in your wallpaper are good for the dominant and complementary colors and applies them in all of Android’s screens, menus, and even first-party apps. Apple likely lit a fire under Google when it added widgets to iOS, and the Mountain View company has responded with a much-needed refresh of its first-party widget designs. Expect to see new clocks, new weather widgets, new shortcuts to oft-used contacts, and easier access to your favorite chats. As well as a refresh of the static design elements, Material You will also breathe new life into animations. We’re going to get more fluid motion, better feedback, and generally much smoother performance. Google says that its work under the hood will reduce the CPU time taken up by core system services by up to 22%, which will be reflected in the user experience. I think it definitely looks new and fresh, and less edgy and harsh than the current Material Design sometimes feels. Of course, everyone will hate these changes at first – as is tradition – but I’m very curious to see this in action on my own phone, and something like this is sure to get me to take a serious look at the next crop of Pixel phones as my possible next phone, just to get my hands on the new look and feel. Aside from the massive visual overhaul, Google is also continuing its improvements on the privacy front, but Android being a Google product, I always feel a tad bit skeptical about this particular effort. We’ll see how long it will take for OEMs to actually ship Android 12 – and how badly they will butcher Material You – and as always, that wait may be long.

The next version of Android remains focussed on developers until the first beta launches next month. With that in mind, we’re diving into today’s release of Android 12 DP3 to find all the new features. Mostly small changes, still, and many of them seem specific to Google’s own devices.

Correctness of code in the Android platform is a top priority for the security, stability, and quality of each Android release. Memory safety bugs in C and C++ continue to be the most-difficult-to-address source of incorrectness. We invest a great deal of effort and resources into detecting, fixing, and mitigating this class of bugs, and these efforts are effective in preventing a large number of bugs from making it into Android releases. Yet in spite of these efforts, memory safety bugs continue to be a top contributor of stability issues, and consistently represent ~70% of Android’s high severity security vulnerabilities. In addition to ongoing and upcoming efforts to improve detection of memory bugs, we are ramping up efforts to prevent them in the first place. Memory-safe languages are the most cost-effective means for preventing memory bugs. In addition to memory-safe languages like Kotlin and Java, we’re excited to announce that the Android Open Source Project (AOSP) now supports the Rust programming language for developing the OS itself. Rust is popping up everywhere.