Because of quirks with cell radios and how Android was previously set up, custom ROM support for Galaxy S phones has been sparse these past few years. It's been almost nonexistent for US customers, while international users would see some ROMs. Thanks to Android Oreo's Project Treble, this will all be changing soon.
One of the biggest complaints with Samsung devices has been TouchWiz or Samsung Experience and how far off it is from AOSP. While some customers like Samsung's customization, a dream of many has been to combine the cleanness of stock Android with the great hardware of Galaxy S phones. This might finally become a reality as a side effect of Project Treble, which was designed to solve another problem, fragmentation.
Currently, Samsung Galaxy S series phones have limited custom ROM support, but for reasons specific to each variant. For US customers, all Galaxy S series devices use Qualcomm's Snapdragon chipset to ensure compatibility with Sprint and Verizon's CDMA networks. In another move to appease US carriers, Samsung has locked the bootloader on all Snapdragon variants of their flagships.
This means the only way to flash any kind of unofficial firmware on a Snapdragon Galaxy is by using an exploit that unlocks the bootloader, which is extremely rare. So far, no exploit we've come across has offered a way to fully unlock the bootloader thanks to Samsung Knox, the enterprise-level security platform. In other words, you might find a way to flash custom firmware on the system partition, but not the boot or recovery partitions, for example.
Furthermore, because an exploit is the only way to unlock the bootloader, Samsung is constantly patching these vulnerabilities. Therefore, any exploit that worked previously may not work later, leaving users with a dilemma — update to the latest version and keep your phone secure, or forgo the update to keep your unlocked bootloader.
For the rest of the world (and those who choose to import), Galaxy S series devices use Samsung's own Exynos chipset. These devices come with an unlocked bootloader, so you'd think flashing custom ROMs wouldn't be a problem. However, Samsung doesn't publish any documentation for their Exynos processors, making the development of ROMs extremely difficult. Essentially, developers must use trial and error to enable functionality for their ROMs. But that isn't the only problem.
Samsung doesn't publish driver binaries for this variant. By default, the driver binaries only work with TouchWiz. Without publication, developers are left to TouchWiz-based ROMs since the driver binaries can't be altered for AOSP-based ROMs. In short, while you're able to install a custom ROM on many Exynos Galaxy models, it's typically just a slimmed down version of the stock firmware — not really custom. This is where Project Treble comes in.
With Project Treble, Google has attempted to fix the problem of fragmentation in Android. For years, Android users have been plagued with forgotten phones that receive one or two updates in their entire lifespan. Even worse, these updates would typically just be bug fixes, with only the top flagship phones receiving full version updates.
One of the main causes of this issue was the new Android version being incompatible with certain hardware components. The way Android was set up before, there was no separation between the hardware code and the OS framework. Therefore, when a new version came out, the hardware vendor had to alter a significant portion of code to make it compatible with the new software.
With Project Treble, these two elements are now separated. The vendor implementation contains all the hardware-level code provided by the vendors. Google is working with partners, such as Qualcomm, Samsung, and MediaTek, to provide them with a "Vendor Test Suite" (VTS) that ensures forward compatibility. Therefore, vendors who are compliant with VTS can now deliver the latest version of Android by simply updating the framework.
For Project Treble-enabled devices, once Google releases a new version of Android, an uncompromised AOSP ROM will be able to run on the device without any issue, as long as the bootloader is unlocked. This is why Exynos users (and only Exynos users) have cause for celebration.
Google is requiring that all devices shipping with Android Oreo implement Project Treble, and the 2018 Galaxy S lineup will ship with Oreo. Therefore, as long as Samsung doesn't completely drop the ball somehow, the Galaxy S9 and S9+ will be fully compliant and reap the benefits of Treble. This requirement is not extended to phones that update to Oreo, which is why S8 users (even those with Exynos chipsets) still have limited ROM support.
With the new Exynos Galaxy S9 models and their unlocked bootloaders, custom ROM developers can leverage Project Treble to effectively erase TouchWiz and create an AOSP-based ROM without worry of compatibility, since all the hardware should already be compatible.
For US customers, all isn't lost. Project Treble's actual goal of reducing fragmentation should still be achieved, leading to faster version updates for S9 devices. I do stress should, as it's still largely dependent on OEMs and carriers who can take their sweet time adjusting and testing their skin and pushing out the update. Are you excited about the Galaxy S9? Do you currently use a custom ROM? Let us know in the comments below.
Want to help support Gadget Hacks and get a great deal on some sweet new tech? Check out all the deals on the new Gadget Hacks Shop.