Just started using it on my OnePlus 15 man is it good but God I wish it hadRCS chat. That's about the only thing missing. I use emojis a lot in my text messages and without RCS can't do it

Need a good paid camera app for my Oneplus 15 running LineageOS 24. I've heard the stock one sucks. And I don't want a modded GCAM one, that might or might not work 100%. Which one in the play store is generally all around the best?

Re-Engineering the Custom Android Ecosystem: Dual-Partition Isolation, SoC Management, and Transparent Attestation Architectures

Abstract

The contemporary mobile software landscape is characterized by an escalating conflict between commercial device security verification and open-source platform ownership. While commercial platforms enforce strict binary attestation to secure applications, the custom ROM ecosystem relies on a fragile cat-and-mouse paradigm of kernel hooks, root-hiding utilities, and static hardware keybox duplication to circumvent integrity restrictions. This proposal outlines a systematic refactoring of the custom Android distribution model. By establishing secure, cryptographically signed ecosystems for trustworthy distributions such as LineageOS, crDroid, Evolution X, and GrapheneOS, alongside dual-data partition isolation, runtime-safe system SoC management, and honest software-level attestation reporting, Android can achieve a sustainable operational balance between power-user freedom and platform compliance.

The Structural Inefficiencies of Contemporary Verification

Current mobile security architectures dictate an all-or-nothing model where unlocking a device's bootloader to run custom software revokes hardware-backed platform trust. To restore access to routine commercial applications, users routinely deploy root-hiding toolchains and injected hardware keyboxes. However, this approach creates severe systemic vulnerabilities. Publicly shared keyboxes inevitably suffer from volume-based collision anomalies on server-side validation networks, leading to immediate certificate revocation and systemic integrity failure. Relying on continuous evasion modules introduces instability, security risks, and an unsustainable maintenance cycle. Rather than treating the operating system as a deceptive wrapper attempting to bypass verification, the custom ROM ecosystem requires an intentional structural evolution that separates daily-driver execution environments from power-user developer workspaces.

Cryptographically Signed Trust Frameworks for Custom Distributions

A mature custom operating system framework must rely on official, cryptographically signed builds distributed by established maintainer communities, including LineageOS, crDroid, Evolution X, and GrapheneOS. Rather than forcing these distributions to emulate closed-source factory environments, the platform framework should support verified maintainer keys. Google Mobile Services (GMS) and associated core frameworks should remain modular—provided as optional, flashable add-on packages to accommodate users seeking a purely open-source software stack. When a device executes an officially signed, unmodified build from a verified maintainer collective, the underlying system architecture maintains cryptographic validity.

Dual-Data Partition Isolation and Sandbox Workflows

To satisfy the operational demands of developers and power users without compromising daily-driver security, the storage topology can be structured around an on-demand, dual-environment layout. Upon initial deployment, the device utilizes a single resizable Ext4-formatted data partition designated as Environment A (data_a). This primary partition remains strictly sealed, encrypted, and dedicated to daily operations, financial tools, and attestation-sensitive workloads.

Secondary workspace provisioning is handled via custom recovery modules, where an optional toggle allows the system to shrink data_a and initialize an unallocated secondary partition designated as Environment B (data_b). Until explicitly initiated by the user, data_b remains non-existent. Once initialized, Environment B functions as an isolated developer sandbox. Here, advanced users can deploy custom binaries, containerized runtimes, and administrative tools with full system privileges. Because storage mounts are strictly isolated, modifications within Environment B cannot compromise the cryptographic or operational integrity of Environment A.

Runtime-Safe SoC Management

Hardware performance tuning—including CPU scheduling profiles, governor selection, and thermal parameter adjustments—has historically required destructive third-party root toolchains that modify immutable partition nodes. To eliminate this friction, trusted custom distributions should integrate a native, system-level SoC Manager built directly into the signed OS image. Rather than altering file systems or flashing arbitrary kernel binaries, this service operates entirely within volatile memory. It communicates dynamically with runtime-permitted kernel interfaces via standard virtual file systems such as sysfs and proc nodes. This approach provides users with granular hardware control while preserving the cryptographic seal of the system partition.

Transparent Attestation Reporting and Keybox Supervision

The practice of masking security state through globally shared, static keyboxes remains a vulnerability point across modern ROM deployments. A sustainable architecture must transition toward transparent, state-aware attestation behavior. When Environment A remains pristine and unmodified, the custom distribution accurately validates system software parameters. Conversely, the moment an administrative tool alters protected system boundaries or the user boots into the developer sandbox (data_b), the ROM logic transitions to an honest attestation state, reporting validation failure to security-sensitive services. This eliminates reliance on fragile spoofing mechanisms for everyday use while containing administrative testing strictly within designated boundaries.

The Long-Term Horizon: Open-Source Bootloaders

While software-level attestation management provides an immediate solution for legacy and contemporary silicon, long-term ecosystem health requires hardware-level evolution. The custom software community must advocate for open-source bootloader standards and extensible firmware architectures (such as U-Boot or EDK2 equivalents on mobile hardware). Universal support for open bootloader standards will enable future silicon generations to natively accommodate user-enrolled cryptographic public keys within hardware-backed trust anchors, permanently reconciling open-source development freedom with hardware-verified security.

Hey everyone!

Running LineageOS or another custom ROM on a Motorola phone and missing your stock camera features (ultra-wide, macro, and Motorola image tuning)?

This tool extracts the official **Moto Camera 4 app, AI services, HAL daemons, and calibration blobs** directly from your phone's official stock firmware and packages them into a recovery-sideloadable ZIP. It even includes LineageOS `addon.d` survival so it persists across weekly ROM updates without Magisk.

**Important Disclaimers:**
- **AI-Written:** This project was developed with AI assistance (Google DeepMind Gemini).
- **Windows Script Untested:** The Linux compilation script is tested and verified working. A Windows PowerShell script and Batchfile are included, but have not yet been thoroughly tested.

**Testers Needed:**
- **Verified Working:** Moto G Stylus 5G 2023 (`genevn`).
- **Looking For:** **ANY Motorola device that originally ran official stock Android 13 or 14** (Edge series, Razr series, Moto G series, ThinkPhone, etc.) running an A13+ custom ROM.

Detailed requirements, dependencies, and step-by-step instructions are available on the repository:
**GitHub:** https://github.com/vrwindsor1/Universal_MotCamera4Suite_Installer

If you try it out, please drop a comment with your **device model**, **ROM/Android version**, and whether your camera/lenses work properly!

I really enjoy using Lineage on my Pixel 4a. However, it isn't my daily. Lately, I've been looking for a tab, but I like Lineage so much, and of course I'd like to save money, that I thought maybe I could buy one used and install Lineage on it. That said, I'm kinda worried about performance - even though I don't plan to do much on the tab. Just reading, maybe taking notes, watching sports, and other general use. I chose S7 because that seemed to me a good balance of price, performance, build quality etc on the Devices page of the website. What do you guys think?

Edit SOLVED (?) So I tried unlocking the phone again when I got home from work (everything transpired while in my car as I'm always on the road and in parking lots) and the lighting was more dim. Like before, the always-on-display was working just fine. This time however, I could faintly make out the unlock pattern screen, and then my home screen. The brightness was all the way down. Turning back to a usable brightness and everything seems back to normal. I'm guessing this was all that was the issue, and last-nights update was just a coincidence. Still unsure how the brightness was essentially turned to zero. Great reminder to check the simple and mundane when troubleshooting!

My Sony Xperia 1 III prompted me with the October LineageOS update last night

I installed the update, it rebooted, and everything seemed fine.

Randomly today during use, I could no longer unlock and access the phone, the screen is just blank

I know the screen still works fine, the always-on display works, displaying the correct time.

Using the volume and power buttons, I rebooted the phone several times, was able to get into the custom fastboot menu as well, trying both the reboot and power off options there.

On powerup/reboot I get the Sony logo, LineageOS logo, and my lock screen - but when I swipe up to get to the unlock code, it's totally blank.

Is there a known issue with the new update?

If I use the custom fastboot menu to manually flash an update, will it wipe everything on my phone?

Any help will be grately appreciated

I REALLY like Lineage OS, as I was able to install it and root it with magisk, so I could finally change firewall POLICIES for input, forward and output and fix it for my use. I can also share my setup on cloudflare zero trust, that has a DNS server I can control with many rules, VPN with strong security protocols, filtering proxy, gateway with firewall, tls inspection and virus scanning even inside secure connections and all devices using tethering can fully benefit from it. I still cannot do it using my other Samsung devices which is a shame ! Installed on a Samsung Galaxy s20+, runs smooth like a baby seal in the summer sea. Thank you so much for this incredible Android distro. Amazing work !

For a week now, sound sent to my car via Android Auto will have very loud crack/thump noise. To be honest, the first few times it happened, I thought people sent a rock to my car. It's really startling, and it really endangers my driving.

Does anyone else have this ? I saw on Google that it happened to other car owners over the years, but I couldn't find a working fix.

trying to install, got to the command "fastboot flash boot boot.img" but it cant find boot.img (i did install it) so the command failed, what can i do?

well, forget about it, OEM is still locked, motorola support site doesen't work and i will have to try later

Is it possible to install Lineage OS on the OP15 US version? I read somewhere that it is not possible for the US version, just want to confirm.

I'm using Osmand (maps and GPS navigation) to record my trips and need it to always stay on and running at all times. Is there a way to give it higher priority over VLC and other apps that may be running concurrently, so that when RAM is low they close first before Osmand does?

Is there either an option in the settings somewhere, or perhaps a FOSS memory management app which allows this?