Android Archive

Google’s biggest announcement today, at least as it pertains to Android, is that the Vulkan graphics API is now the official graphics API for Android. Vulkan is a modern, low-overhead, cross-platform 3D graphics and compute API that provides developers with more direct control over the GPU than older APIs like OpenGL. This increased control allows for significantly improved performance, especially in multi-threaded applications, by reducing CPU overhead. In contrast, OpenGL is an older, higher-level API that abstracts away many of the low-level details of the GPU, making it easier to use but potentially less efficient. Essentially, Vulkan prioritizes performance and explicit hardware control, while OpenGL emphasizes ease of use and cross-platform compatibility. ↫ Mishaal Rahman at Android Authority Android has supported Vulkan since Android 7.0, released in 2016, so it’s not like we’re looking at something earth-shattering here. The issue has been, as always with Android, fragmentation: it’s taken this long for about 85% of Android devices currently in use to support Vulkan in the first place. In other words, Google might’ve wanted to standardise on Vulkan much sooner, but if only a relatively small number of Android devices support it, that’s going to be a hard sell. In any event, from here on out, every application or game that wants to use the GPU on Android will have to do so through Vulkan, including everything inside Android. It’s still going to be a long process, though, as the requirement to use Vulkan will not fully come into effect until Android 17, and even then there will be exceptions for certain applications. Android tends to implement changes like this in phases, and the move to Vulkan is no different. All of this does mean that older devices with GPUs that do not support Vulkan, or at least not properly, will not be able to be updated to the Vulkan-only releases of Android, but let’s be real here – those kinds of devices were never going to be updated anyway.

Starting with Android smartphones running on the Snapdragon 8 Elite Mobile Platform, Qualcomm Technologies now offers device manufacturers the ability to provide support for up to eight consecutive years of Android software and security updates. Smartphones launching on new Snapdragon 8 and 7-series mobile platforms will also be eligible to receive this extended support. ↫ Mike Genewich I mean, good news of course, but Qualcomm has a history of making empty promises, so I’ll see it when I believe it. Also note that this news doesn’t mean every Snapdragon 8 Elite Android device will get eight years of updates – it just means OEMs are able to offer such support now, not that they’ll actually do it. Considering it’s usually the OEMs refusing to offer updates, I wonder just how big the actual impact of this news will be. In any event, this includes both regular Android updates as well as two Android Common Kernel upgrades, which are required to meet this eight year window. If you want to get into the nitty-gritty about Android and the Android Common Kernels, the official Android documentation has more details.

Regardless, the fact that Android’s Linux Terminal can run graphical apps like Doom now is good news. Hopefully we’ll be able to run more complex desktop-class Linux programs in the future. I tried running GIMP, for example, but it didn’t work. Eventually, Android should be able to run Linux apps as well as Chromebooks can, as I believe one of the goals of this project is to help the transition of Chrome OS to an Android base. ↫ Mishaal Rahman at Android Authority It was of course inevitable that someone would run Doom on Android’s new Debian container, and it’s pretty cool to see it work without much issue already, even if the new terminal and container setup are still in such heavy development. Like many other people, I love the idea of my smartphone being both my, well, smartphone, as well as a full desktop PC once you connect it to a display and some input devices. As wireless technology keeps advancing, we soon might not even need to plug anything into the phone at all, and just having it in our pocket is good enough, which would be amazing. That being said, I would want such functionality to come from a traditional Linux setup, not Android’s idea of a Linux setup. Running a Debian virtual machine on top of Android is probably preferable for a lot of people for a variety of reasons, but I’m a Linux user and want plain, regular Linux running directly on my smartphone, not some virtual machine on Android, which, while being a Linux distribution, is not the most pleasant variant of Linux to run and use.

Basically, this seems to mean applications will no longer be allowed to limit themselves to phone size when running on devices with larger screens, like tablets. Other tidbits in this first beta include predictive back support for 3-button navigation, support for the Advanced Professional Video codec from Samsung, among other things. It’s still quite early in the release process, so more is sure to come, and some things might not make it to the final release at all.

LineageOS, the Debian of the custom Android ROM world, released version 22 – or, 22.1 to be more exact – today. On the verge of the new year, they managed to complete the rebase to Android 15, released in September, making this one of their fastest rebases ever. We’ve been hard at work since Android 15’s release in September, adapting our unique features to this new version of Android. Android 15 introduced several complex changes under the hood, but due to our previous efforts adapting to Google’s UI-centric adjustments in Android 12 through 14, we were able to rebase onto Android 15’s code-base faster than anticipated. Additionally, this is far-and-away the easiest bringup cycle from a device perspective we have seen in years. This means that many more devices are ready on day one that we’d typically expect to have up this early in the cycle! ↫ Nolen Johnson LineageOS is also changing its versioning scheme to better match that of Google’s new quarterly Android releases, and that’s why this new release is 22.1: it’s based on Android 15 QPR1. In other words, the 22 aligns with the major Android version number, and the .1 with the QPR it’s based on. LineageOS 22.1 brings all the same new features as Android 15 and QPR1, as well as two brand new applications: Twelve, a replacement for LineageOS’ aging music player application, and Camelot, a new PDF reader. The list of supported devices is pretty good for a new LineageOS release, and adds the Pixel 9 series of devices right off the bat. LineageOS 22.1 ships with the November Android security patches, and also comes with a few low-level changes, like completely new extract utilities written in Python, which massively improve extracting performance, virtIO support, and much more.

What if you have an Android phone, but consider the Apple Watch superior to other smartwatches? Well, you could switch to iOS, or, you know, you could hack your way into making an Apple Watch work with Android, like Abishek Muthian did. So I decided to make Apple Watch work with my Android phone using open-source applications, interoperable protocols and 3rd party services. If you just want to use my code and techniques and not read my commentary on it then feel free to checkout my GitHub for sources. ↫ Abishek Muthian Getting notifications to work, so that notifications from the Android phone would show up on the Apple Watch, was the hardest part. Muthian had to write a Python script to read the notifications on the Android device using Termux, and then use Pushover to send them to the Apple Watch. For things like contacts and calendar, he relied on *DAV, which isn’t exactly difficult to set up, so pretty much anyone who’s reading this can do that. Sadly, initial setup of the watch did require the use of an iPhone, using the same SIM as is in the Android phone. This way, it’s possible to set up mobile data as well as calling, and with the SIM back in the Android phone, a call will show up on both the Apple Watch and the Android device. Of course, this initial setup makes the process a bit more cumbersome than just buying a used Apple Watch off eBay or whatever, but I’m honestly surprised everything’s working as well as it does. This goes to show that the Apple Watch is not nearly as “deeply integrated” with the iPhone as Apple so loves to claim, and making the Apple Watch work with Android in a more official manner certainly doesn’t look to be as impossible as Apple makes it out to be when dealing with antitrust regulators. Of course, any official support would be much more involved, especially in the testing department, but it would be absolute peanuts, financially, for a company with Apple’s disgusting level of wealth. Anyway, if you want to setup an Apple Watch with Android, Muthian has put the code on GitHub.

There are so many ecological, environmental, and climate problems and disasters taking place all over the world that it’s sometimes hard to see the burning forests through the charred tree stumps. As at best middle-income individuals living in this corporate line-must-go-up hellscape, there’s only so much we can do turn the rising tides of fascism and leave at least a semblance of a livable world for our children and grandchildren. Of course, the most elementary thing we can do is not vote for science-denying death cults who believe everything is some non-existent entity’s grand plan, but other than that, what’s really our impact if we drive a little less or use paper straws, when some wealthy robber baron flying his private jet to Florida to kiss the gaudy gold ring to signal his obedience does more damage to our world in one flight than we do in a year of driving to our underpaid, expendable job? Income, financial, health, and other circumstances allowing, all we can do are the little things to make ourselves feel better, usually in areas in which we are knowledgeable. In technology, it might seem like there’s not a whole lot we can do, but actually there’s quite a few steps we can take. One of the biggest things you, as an individual knowledgeable about and interested in tech, can do to give the elite and ruling class the finger is to move away from big tech, their products, and their services – no more Apple, Amazon, Microsoft, Google, or Amazon. This is often a long, tedious, and difficult process, as most of us will discover that we rely on a lot more big tech products than we initially thought. It’s like an onion that looks shiny and tasty on the outside, but is rotting from the inside – the more layers you peel away, the dirtier and nastier it gets. Also you start crying. I’ve been in the process of eradicating as much of big tech out of my life for a long time now. Since four or five years ago, all my desktop and laptop PCs run Linux, from my dual-Xeon workstation to my high-end gaming PC (ignore that spare parts PC that runs Windows just for League of Legends. That stupid game is my guilty pleasure and I will not give it up), from my XPS 13 laptop to my little Home Assistant thin client. I’ve never ordered a single thing from Amazon and have no Prime subscription or whatever it is, so that one was a freebie. Apple I banished from my life long ago, so that’s another freebie. Sadly, that other device most of us carry with us remained solidly in the big tech camp, as I’ve been using an Android phone for a long time, filled to the brim with Google products, applications, and services. There really isn’t a viable alternative to the Android and iOS duopoly. Or is there? Well, in a roundabout way, there is an alternative to iOS and Google’s Android. You can’t do much to take the Apple out of an iPhone, but there’s a lot you can do to take the Google out of an Android phone. Unless or until an independent third platform ever manages to take serious hold – godspeed, our saviour – de-Googled Android, as it’s called, is your best bet at having a fully functional, modern smartphone that’s as free from big tech as you want it to be, without leaving you with a barely usable, barebones experience. While you can install a de-Googled ROM yourself, as there’s countless to choose from, this is not an option for everyone, since not everyone has the skills, time, and/or supported devices to do so. Murena, Fairphone, and sustainable mining This is where Murena comes in. Murena is a French company – founded by Gaël Duval, of Mandrake Linux fame – that develops /e/OS, a de-Googled Android using microG (which Murena also supports financially), which it makes available for anyone to install on supported devices, while also selling various devices with /e/OS preinstalled. Murena goes one step further, however, by also offering something called Murena Workspace – a branded Nextcloud offering that works seamlessly with /e/OS. In other words, if you buy an /e/OS smartphone from Murena, you get the complete package of smartphone, mobile operating system, and cloud services that’s very similar to buying a regular Android phone or an iPhone. To help me test this complete package of smartphone, de-Googled Android, and cloud services, Murena loaned me a Fairphone 5 with /e/OS preinstalled, and while this article mostly focuses on the /e/OS experience, we should first talk a little bit about the relationship between Murena and Fairphone. Murena and Fairphone are partners, and Murena has been selling /e/OS Fairphones for a while now. Most of us will be familiar with Fairphone – it’s a Dutch company focused on designing and selling smartphones and related accessories that are are user-repairable and long-lasting, while also trying everything within their power to give full insight into their supply chain. This is important, because every smartphone contains quite a few materials that are unsustainably mined. Many mines are destructive to the environment, have horrible working conditions, or even sink as low as employing children. Even companies priding themselves on being environmentally responsible and sustainable, like Apple, are guilty of partaking in and propping up such mining endeavours. As consumers, there isn’t much we can do – the network of supply chains involved in making a smartphone is incredibly complex and opaque, and there’s basically nothing normal people can do to really fully know on whose underpaid or even underage shoulders their smartphone is built. This holiday season, Murena and Fairphone are collaborating on exactly this issue of the conditions in mines used to acquire the metals and minerals in our phones. Instead of offering big discounts (that barely eat into margins and often follow sharp price increases right before the holidays), Murena and Fairphone will donate

Mishaal Rahman, who has a history of being right about Google and Android-related matters, is reporting that Google is intending to standardise its consumer operating system efforts onto a single platform: Android. To better compete with the iPad as well as manage engineering resources more effectively, Google wants to unify its operating system efforts. Instead of merging Android and Chrome OS into a new operating system like rumors suggested in the past, however, a source told me that Google is instead working on fully migrating Chrome OS over to Android. While we don’t know what this means for the Chrome OS or Chromebook brands, we did hear that Google wants future “Chromebooks” to ship with the Android OS in the future. That’s why I believe that Google’s rumored new Pixel Laptop will run a new version of desktop Android as opposed to the Chrome OS that you’re likely familiar with. ↫ Mishaal Rahman at Android Authority The fact both Chrome OS and Android exist, and are competing with each other in some segments – most notably tablets – hasn’t done either operating system any favours. I doubt many people even know Chrome OS tablets are a thing, and I doubt many people would say Android tablets are an objectively better choice than an iPad. I personally definitely prefer Android on tablets over iOS on tablets, but I fully recognise that for 95% of tablet buyers, the iPad is the better, and often also more affordable, choice. Google has been struggling with Android on tablets for about as long as they’ve existed, and now it seems that the company is going to focus all of its efforts on just Android, leaving Chrome OS to slowly be consumed and replaced by it. In June, Google already announced it was going to replace both the kernel and several subsystems in Chrome OS with their Android counterparts, and now they’re also building a new version of Chrome for Android with extensions supports – to match Chrome on Chrome OS – as well as a terminal application for Android that gives access to a local Linux virtual machine, much like is available on Chrome OS. As mentioned, laptops running Android will also be making an entrance, including a Pixel laptop straight from Google. The next big update for Android 15 contains a ton of new proper windowing features, and there’s more coming: improved keyboard and mouse support, as well as external monitors, virtual desktops, and a lot more. As anyone who has ever attempted to run Android on a desktop or laptop knows, there’s definitely a ton of work Google needs to do to make Android palatable to consumers on that front. Of course, this being Google, any of these rumours or plans could change at any time without any sense of logic behind it, as managers fulfill their quotas, get promoted, or leave the company.

In a major shift of its release cycle, Google has revealed that Android 16 will be released in Q2 of 2025, confirming my report from late last month. Android 16 is the name of the next major release of the Android operating system, and its release in Q2 marks a significant departure from the norm. Google typically pushes out a new major release of Android in Q3 or Q4, but the company has decided to move next year’s major release up by a few months so more devices will get the update sooner. ↫ Mishaal Rahman at Android Authority That’s a considerable shake-up of Android’s long-lasting release cadence. The change includes more than just moving up the major Android release, as Google also intends to ship more minor releases of Android throughout the year. The company has already unveiled a rough schedule for Android 16, only weeks after releasing Android 15, with the major Android 16 release coming in the second quarter of 2025, followed by a minor release in the fourth quarter of 2025. There are two reasons Google is doing this. First, this new release schedule better aligns with when new flagship Android devices are released, so that from next year onwards, they can ship with the latest version of Android of that year preinstalled, instead of last year’s release. This should help bump up the number of users using the latest release. Second, this will allow Google to push out SDK releases more often, allowing for faster bug fixing. I honestly feel like most users will barely notice this change. Not only is the Android update situation still quite messy compared to its main rival iOS, the smartphone operating system market has also matured quite a bit, and the changes between releases are no longer even remotely as massive as they used to be. Other than Pixel users, I don’t think most people will even realise they’re on a faster release schedule.

Android 15 started rolling out to Pixel devices Tuesday and will arrive, through various third-party efforts, on other Android devices at some point. There is always a bunch of little changes to discover in an Android release, whether by reading, poking around, or letting your phone show you 25 new things after it restarts. In Android 15, some of the most notable involve making your device less appealing to snoops and thieves and more secure against the kids to whom you hand your phone to keep them quiet at dinner. There are also smart fixes for screen sharing, OTP codes, and cellular hacking prevention, but details about them are spread across Google’s own docs and blogs and various news site’s reports. ↫ Kevin Purdy at Ars Technica It’s a welcome collection of changes and features to better align Android’ theft and personal privacy protection with how thieves steal phones in this day and age. I’m not sure I understand all of them, though – the Private Space, where you can drop applications to lock them behind an additional pin code, confuses me, since everyone can see it’s there. I assumed Private Space would also give people in vulnerable positions – victims of abuse, journalists, dissidents, etc. – the option to truly hide parts of their life to protect their safety, but it doesn’t seem to work that way. Android 15 will also use “AI” to recognise when a device is yanked out of your hands and lock it instantly, which is a great use case for “AI” that actually benefits people. Of course, it will be even more useful once thieves are aware this feature exists, so that they won’t even try to steal your phone in the first place, but since this is Android, it’ll be a while before Android 15 makes its way to enough users for it to matter.

The push towards memory safe programming languages is strong, and for good reason. However, especially for bigger projects with a lot of code that potentially needs to be rewritten or replaced, you might question if all the effort is even worth it, particularly if all the main contributors would also need to be retrained. Well, it turns out that merely just focusing on writing new code in a memory safe language will drastically reduce the number of memory safety issues in a project as a whole. Memory safety vulnerabilities remain a pervasive threat to software security. At Google, we believe the path to eliminating this class of vulnerabilities at scale and building high-assurance software lies in Safe Coding, a secure-by-design approach that prioritizes transitioning to memory-safe languages. This post demonstrates why focusing on Safe Coding for new code quickly and counterintuitively reduces the overall security risk of a codebase, finally breaking through the stubbornly high plateau of memory safety vulnerabilities and starting an exponential decline, all while being scalable and cost-effective. ↫ Jeff Vander Stoep and Alex Rebert at the Google Security Blog In this blog post, Google highlights that even if you only write new code in a memory-safe language, while only applying bug fixes to old code, the number of memory safety issues will decreases rapidly, even when the total amount of code written in unsafe languages increases. This is because vulnerabilities decay exponentially – in other words, the older the code, the fewer vulnerabilities it’ll have. In Android, for instance, using this approach, the percentage of memory safety vulnerabilities dropped from 76% to 24% over 6 years, which is a great result and something quite tangible. Despite the majority of code still being unsafe (but, crucially, getting progressively older), we’re seeing a large and continued decline in memory safety vulnerabilities. The results align with what we simulated above, and are even better, potentially as a result of our parallel efforts to improve the safety of our memory unsafe code. We first reported this decline in 2022, and we continue to see the total number of memory safety vulnerabilities dropping. ↫ Jeff Vander Stoep and Alex Rebert at the Google Security Blog What this shows is that a large project, like, say, the Linux kernel, for no particular reason whatsoever, doesn’t need to replace all of its code with, say, Rust, again, for no particular reason whatsoever, to reap the benefits of a modern, memory-safe language. Even by focusing on memory-safe languages only for new code, you will still exponentially reduce the number of memory safety vulnerabilities. This is not a new discovery, as it’s something observed and confirmed many times before, and it makes intuitive sense, too; older code has had more time to mature.

To empower tablet users to get more done, we’re enhancing freeform windowing, allowing them to run multiple apps simultaneously and resize windows for optimal multitasking. Today, we’re excited to share that desktop windowing on Android tablets is available in developer preview. For app developers, the concept of Android apps running in freeform windows has already existed with solutions like Samsung DeX and ChromeOS. Updating your apps to support adaptive layouts, more robust multitasking, and adaptive inputs will ensure your apps work well on large screens across the Android ecosystem. ↫ Francesco Romano on the Android Developers Blog The long-running saga of Google trying to develop proper freeform windowing support for Android seems to finally be bearing fruit. Countless attempts came and went, usually in developer releases, hidden behind flags, rarely, if ever talked about, but now it’s finally not only part of an Android beta release anyone with a Pixel Tablet can install and try out, Google is also openly talking about and touting it as a feature, so we might actually perhaps maybe see this in a non-beta release at some point. The way it works is both surprising and rather unsurprising. Instead of the Apple approach, which seems to entail a deep disdain for traditional windowing, Google is pretty much embracing the things we expect a windowing system to have, from window titlebars with close and maximise widgets, to a traditional dock-like taskbar permanently available at the bottom of the screen. If you click or tap on a little downward arrow on the titlebar, you can choose options like displaying windows side-by-side, much like on Windows. A very welcome ‘feature’ is the ability to tear off Chrome tabs and turn them into their own windows, just like in a traditional desktop environment. Google also opted for an interesting approach that reminds me somewhat of the “desktop” mode on Windows RT. Since Windows RT was ARM-based and entirely locked-down, the only classic Win32 applications you could run were those bundled with Windows as well as Microsoft Office. To access these, Windows RT would launch a full-screen tablet application that contained the entire traditional Windows desktop, and you’d run your classic Win32 applications in there. Android’s new windowing system seems to be doing something similar: once you enter the freeform windowing mode, all future applications will also launch as windows. In the task switcher, however, they’re all contained within a single “desktop” entry that you can close if you want to. That desktop entry seems to take the shape of a live view of the “desktop”, including the various windows you have opened. This way, you can have a dedicated “desktop” with freeform windows alongside any fullscreen tablet applications you also happen to be running. It’s perhaps not the most integrated or elegant approach, but it’s dead-simple and easy to grasp. This new windowing environment also provides application developers with the option of allowing multiple instances of a single application to be launched, say launching two text editor windows side-by-side. This seems to be a specific property developers need to enable, though, and considering Android’s tablet adoption history, that’s anything but a given at this point. Of course, it shouldn’t come as a surprise that applications need to be able to resize gracefully, too. If you want to play with it, you’ll need a Pixel Tablet running Android 15 QPR1 Beta 2, or just use the simulator. I really hope this takes off and developers support the various APIs for optimal integration (I’m not getting my hopes up), since proper freeform windowing that doesn’t feel like an ugly, barely functional hack is something I’ve been wanting on Android for a long time.

Today we’re releasing Android 15 and making the source code available at the Android Open Source Project (AOSP). Android 15 will be available on supported Pixel devices in the coming weeks, as well as on select devices from Samsung, Honor, iQOO, Lenovo, Motorola, Nothing, OnePlus, Oppo, realme, Sharp, Sony, Tecno, vivo, and Xiaomi in the coming months. We’re proud to continue our work in open source through the AOSP. Open source allows anyone to build upon and contribute to Android, resulting in devices that are more diverse and innovative. You can leverage your app development skills in Android Studio with Jetpack Compose to create applications that thrive across the entire ecosystem. You can even examine the source code for a deeper understanding of how Android works. ↫ Matthew McCullough at the Android Developers blog While it’s great that we’re still getting open source Android releases, the reality of it is that Google has eroded so much away from the Android Open Source Project that AOSP has become effectively useless. Back in the olden days, AOSP was a complete mobile operating system, but those days are long behind us. Google has moved so much from AOSP over to proprietary frameworks, applications, and cloud services that running that it’s no longer a complete package, which is a huge shame. Still, AOSP plays an important role for the custom ROM community and the various companies and communities making privacy-first, de-Googled Android versions, and for that reason alone it’s good that it still exists, even in its gutted state. Android 15’s AOSP release will surely find its way to LineageOS, /e/OS, GrapheneOS, and the countless other alternatives to butchered Android OEM versions and people seeking a more private smartphone experience. As for when Android 15 will hit Pixels – that’s going to be a few weeks from now, later than usual after the source release.

On the whole, I’m satisfied that Lineage OS, as I use it, is preventing nearly all of Google’s data collection. I don’t install or use any Google services, I don’t enable A-GPS, I don’t use Chromium or the built-in browser. I could eliminate more arcane aspects of data collection – like the Internet connectivity check – if I wanted to take the trouble. I don’t think that taking reasonable precautions to avoid becoming part of Google’s data collection economy makes me a tinfoil-hatter. Nevertheless, I would probably use GrapheneOS instead, if I had devices that supported it. Ironically, if I wanted to use GrapheneOS, I’d have to buy Google-branded mobile devices, which is an irony that really stings. ↫ Kevin Boone The existence of Android versions like LineageOS, GrapheneOS, /e/OS, and similar, other de-Googled mobile operating systems is absolutely vital. The market is dominated by Google Android and iOS, and since full alternatives that aren’t Android or iOS are effectively impossible, de-Googled Android is the best we’re going to get. Regulators must ensure that banks, government ID applications, popular messaging platforms, and similarly crucial applications work 100% reliably on de-Googled Android, and do not require Google Play Services in any way, shape, or form. In The Netherlands, there are basically three banks that control the market, and there’s really just one messaging application that rules the country – WhatsApp – and their use is effectively required to participate in society. Consequently, these applications and platforms should be accessible by as many people as possible, and that definitely includes de-Googled Android devices. Being alive should not be taxed by Apple or Google.