All articles tagged with #custom roms
The era of custom Android ROMs is declining due to hardware restrictions, Google's evolving security measures, and corporate policies from manufacturers like Samsung and Google, with CalyxOS pausing development and GrapheneOS remaining the last major privacy-focused Android OS.
Samsung appears to be disabling the ability to unlock bootloaders on more devices with the One UI 8 update, including international models, by removing the OEM Unlock toggle and adding a configuration line that locks the bootloader, which could restrict customization and rooting options for users.
Samsung's upcoming One UI 8 update appears to remove the option to unlock the bootloader on Galaxy devices globally, including the 'OEM Unlocking' setting, which will impact enthusiasts who enjoy customizing their devices. While the ability to unlock the bootloader will still exist for Samsung, it will no longer be accessible to users, marking a shift towards more restricted device modifications. This change is part of a broader trend among Android manufacturers to limit user access to advanced device features.
Google clarified that the Android Open Source Project (AOSP) is not being discontinued despite the absence of Pixel device trees in the Android 16 release, which has caused concern among custom ROM developers. While Google remains committed to AOSP updates, the removal of Pixel-specific hardware repos suggests a shift towards a hardware-independent reference target, potentially complicating custom ROM development and security research.
Google is reportedly blocking RCS messaging on rooted Android phones and custom ROMs without providing clear error messages, leading to messages not being sent even though RCS shows as connected. The company claims it's to prevent spam and abuse, but users are questioning the move, especially given Google's previous advocacy for RCS. Users have found ways to bypass the checks, but the situation raises concerns about Google's approach to messaging on Android devices.