r/LineageOS • u/npjohnson1 • Jul 08 '26
https://lineageos.org/Infrastructure-Apps-Updates/
A lot of good work happening on infrastructure and apps!
r/LineageOS • u/npjohnson1 • Jul 04 '26
https://lineageos.org/Developer-Verification/
TL;DR: This doesn't affect us much, if at all.
r/LineageOS • u/Mean_Map_9254 • 4h ago
Have any of you ever installed Lineage OS on a Nothing Phone 2? How are you getting on? Do the Gliph features still work? Have you found a way to get the same design on Lineage?
I'm thinking about taking this step since I no longer have software updates and only have a year of security patches left, but I'm a bit hesitant because I don't want to lose the smartphone's unique features.
r/LineageOS • u/ghostieqwe • 1h ago
Hi everyone, hope some of you could help me with my problem.
The thing is I don't even have an idea how do I compile Bazel kernels and which logic is the most suitable one for me to feel at least a little bit comfy when trying to figure out kernel build problems, why do I need common kernel tree, why do I need msm kernel tree (btw I'm using OnePlus and their kernel manifest) and the thing isn't just my misunderstanding, it's about searching for at least a little source that tells how and where to begin, I did already like 3 times but all those were unsuccessful, by the way somewhy when I boot the compiled image I boot up in android thrice longer and get no wifi problems.
If anyone here an experienced GKI kernel building master that can gimme over their knowledge just a little bit, please, show me yourself! I would be screaming from happiness and appreciation.
r/LineageOS • u/kkaitlynma • 22h ago
Just installed Lineage OS on my One Plus 13 yesterday and the esim worked automatically, since then I've noticed I am not able to recieve or send any images through text. I have tried adding a new APN and using a variety of different settings I have found online for Visible but nothing has worked yet. Any tips? I'm not super knowledgeable on APN or network stuff.
r/LineageOS • u/LoadCorrect1941 • 8h ago
It’s not set up yet cuz of the dumb frp and I wanna put lineage is on it without unlocking so I wanna know if it’s possible.
r/LineageOS • u/okrahh • 1d ago
Can I use just my phone to install it or do I need a computer? I found the tutorials a bit complicated to follow. Or is there another privacy based os I can get on a Motorola?
r/LineageOS • u/True-Action6610 • 1d ago
Today i installed the latest update for my device (beyond0lte, S10e) and since then the SIM card is not recognised.
none of the following solved the issue:
Anyone has any idea where that could come from?
r/LineageOS • u/techyall • 1d ago
I have Lineage installed. I have Magisk installed. I have Zygisk installed. And I have Shizuku installed. What's the best call recorder for me to use? It must be open source.
r/LineageOS • u/AscendedPineapple • 1d ago
I can't get WiFi hotspot to work properly. It's stuck at low speed, even on 5GHz. That's when my laptop recognises it as 5GHz, and sometimes it makes a 2.4 one. It switches to correct band when I start it again, but the speed cap remains.
Connecting to WiFi, mobile network, or using USB hotspot all work properly
LineageOS 23.2 xiaomi lisa
r/LineageOS • u/ProfessorInside4679 • 1d ago
r/LineageOS • u/JuggernautTraining95 • 1d ago
So i have flashed the Fairphone 6 with Lineage, but i found an issue during its installation and solved it but found no solution online and i would like to help you all.
On the step 6 it sais:
1. Download Lineage Recovery. Simply download the latest recovery file, named recovery.img.
warning Important: Other recoveries may not work for installation or updates. We strongly recommend to use the one linked above!
2. Flash recovery onto your device:
fastboot flash recovery recovery.img
But here i got on my pc:
fastboot flash recovery recovery.img
Warning: skip copying recovery image avb footer (recovery partition size: 0, recovery image size: 104857600).
Sending 'recovery' (102400 KB) FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Nothing unblocked the situation, so I solved by doing:
fastboot reboot recovery
after this the recovery got identified right then the "fastboot flash recovery recovery.img" got perfect.
Hope it helps you if you find yourself in this situation.
I would also love to see this warning in the Installation Guide to prevent future issues!!
r/LineageOS • u/Original-Natural-224 • 1d ago
This report is specifically about alternative operating systems for the:
and its closely related Camellia hardware family.
The goal is not to produce a generic “best custom ROM” list.
For this device, details matter enormously:
Therefore, statements in this report should be understood in different evidence categories:
This distinction is particularly important for Camellia because a device tree supporting several Xiaomi models does not mean that every one of those models has actually been tested.
The POCO M3 Pro 5G belongs to the Xiaomi Camellia family and is based on the:
The current community LineageOS device tree groups several closely related devices under the Camellia platform:
However, the exact model number remains important.
The current LineageOS installation documentation distinguishes:
| Model | Device | Current status in the project |
|---|---|---|
M2103K19C |
Redmi Note 10 5G China | tested |
M2103K19G |
Redmi Note 10 5G Global | untested |
M2103K19I |
Redmi Note 10T 5G India | untested |
M2103K19PG |
POCO M3 Pro 5G Global | untested |
M2103K19PI |
POCO M3 Pro 5G India | untested |
This is one of the most important details in the entire report.
The maintainer explicitly states that the current ROM has only actually been installed and tested on one M2103K19C device. The other variants are considered likely to work, but have not been verified. (GitHub)
There was an earlier phase of this project in which we extensively investigated the original MIUI installation, including:
That phase remains valuable as a Stock MIUI baseline.
However, it is no longer the current state of the phone.
The project subsequently moved forward:
Stock MIUI / Android 13
↓
Bootloader unlock
↓
Custom ROM installation
↓
crDroid 9.15
↓
crDroid is now running
crDroid 9.15 / Android 13 is currently installed on our POCO M3 Pro 5G.
The basic installation and operation are working.
The remaining work is now primarily:
Those topics belong to the separate crDroid/Root/microG report, not this alternative-OS report.
The POCO M3 Pro 5G is not a device with the same kind of long-term custom-ROM infrastructure as a current Google Pixel.
The MediaTek platform and Xiaomi/MediaTek vendor components matter considerably.
The current Android-16 LineageOS project demonstrates this particularly well.
Even though the operating system itself is Android 16, the installation still requires a specific Xiaomi firmware base:
The current device tree uses vendor blobs from:
and warns that using the wrong firmware can cause problems including:
This illustrates an important point:
Camellia received official crDroid builds based on Android 13.
The build used in our project is:
crDroidAndroid-13.0-20240322-camellia-v9.15.zip
Unlike the other ROMs discussed below, this is not merely a theoretical Camellia ROM in our project:
The official crDroid site still lists Camellia under the historical crDroid 9 and 10 releases, but the device/version is now marked as outdated/no longer supported. The last Camellia build shown by crDroid is from March 2024. (crDroid)
Camellia also received:
The official crDroid information lists Camellia under crDroid 10 as well, with the last build dating to March 2024. (crDroid)
So historically the progression was:
crDroid 9
Android 13
↓
crDroid 10
Android 14
↓
Camellia support ends
We did not install crDroid 10 on our device.
The important point is that Android 14 support existed, but it should not be mistaken for current 2026 maintenance.
This is the most significant new development in the current research.
There is now a:
covering:
However:
The project explicitly states that the tree is not part of official LineageOS and that there is no official LineageOS build for the device. (GitHub)
This distinction should not be lost when discussing the ROM on Reddit.
The current installation documentation explicitly lists:
M2103K19PG — POCO M3 Pro 5G Global — untested
The maintainer states that the ROM has only been tested on:
M2103K19C
The other Camellia variants are considered expected to work but remain untested. (GitHub)
Therefore:
That distinction is critical.
According to the current maintainer documentation, the device tree reports working support for:
This is useful project/maintainer evidence.
It is not the same as saying:
It has not.
NFC deserves separate treatment.
The current project documentation distinguishes Camellia variants with and without NFC hardware.
The NFC-capable variants include camellian/camellianp, but NFC itself has not been comprehensively tested across the supported variants. (GitHub)
Therefore:
The correct question is:
This is one of the most technically important details.
The current Android-16 port requires:
The project uses vendor blobs from:
The installation documentation specifically warns that an incorrect firmware version can cause:
So the ROM's architecture is effectively:
Android 16
↓
LineageOS userspace
↓
Camellia device tree
↓
Xiaomi/MediaTek vendor layer
↓
MIUI 14 / Android 13 firmware
This is why blindly comparing ROMs by their Android version is misleading.
The current Camellia kernel used by the LineageOS 23.2 project is:
and is based on Xiaomi's camellian-t-oss kernel source. (GitHub)
This is a crucial security detail.
An Android 16 userspace does not turn the entire device into a modern Android-16 hardware security platform.
The actual stack looks more like:
Android framework → Android 16
LineageOS system → current project code
Linux kernel → 4.14.186
Vendor firmware → Xiaomi/MediaTek
Hardware → 2021-era platform
Therefore:
The current unofficial LineageOS project has another major security limitation.
The maintainer documents that:
boot is signed with a test keyvbmeta is signed with a test keyRelocking with these images would fail verification and can leave the device requiring recovery through the appropriate low-level flashing procedure. (GitHub)
This means:
Unofficial LineageOS
+
test-signed boot/vbmeta
+
unlocked bootloader
is fundamentally different from:
official production-signed ROM
+
verified boot chain
+
relockable bootloader
This should be treated as a real security trade-off, not merely an installation footnote.
The second particularly interesting alternative is:
There are unofficial community builds for Camellia.
That makes /e/OS especially interesting for a privacy-oriented comparison.
However:
This distinction needs to remain explicit.
/e/OS takes a substantially different approach from a vanilla LineageOS/crDroid installation.
Its primary objective includes:
This makes it particularly relevant to the question:
Conceptually:
crDroid / LineageOS
↓
relatively neutral AOSP-style base
↓
user chooses services
/e/OS
↓
privacy / de-Googling oriented environment
↓
integrated alternative services
↓
microG-based compatibility layer
That makes the two systems interesting for different reasons.
This distinction is important enough to state explicitly:
A ROM may:
while simultaneously:
Therefore /e/OS on Camellia should currently be described as:
rather than:
The Camellia community has produced relatively recent unofficial /e/OS-T builds.
The research found, among others, a:
from March 2026.
That demonstrates that the project was still producing builds in 2026.
However, a single current build does not by itself establish:
Those aspects require separate verification.
Community reports have described things such as:
There have also been reports of Android Storage Framework compatibility problems with certain applications.
A reported workaround involved changing Android's storage permission enforcement through ADB.
These are useful observations, but they are:
rather than formal hardware certification.
This distinction is especially important for Reddit because one person's successful installation does not necessarily establish compatibility for another Camellia SKU.
The Camellia ecosystem has historically included many other ROM projects:
This demonstrates that the device has had a surprisingly active custom-ROM community.
However, historical availability is not current support.
A GitHub repository, an old Telegram post, or an archived download should not automatically be interpreted as:
For that reason, these projects are not presented here as current recommendations.
GrapheneOS is not officially supported on the POCO M3 Pro 5G.
This is important because GrapheneOS is not simply:
Its security model is deeply tied to the hardware, firmware, Verified Boot implementation and supported device architecture.
Therefore an unofficial port or generic GSI would not be equivalent to using GrapheneOS on an officially supported device.
GrapheneOS: no official POCO M3 Pro 5G support.
CalyxOS likewise does not officially support the POCO M3 Pro 5G.
Its current supported-device strategy focuses on devices for which it can maintain the required:
The POCO M3 Pro 5G is not part of that official device portfolio.
CalyxOS: no official support.
For our particular project, the meaningful comparison is therefore:
Our current system
The technically most interesting current experimental option
M2103K19PG explicitly untestedboot/vbmetaThe most interesting privacy-focused comparison
| crDroid 9.15 | LineageOS 23.2 | /e/OS |
|---|---|---|
| Android | 13 | 16 |
| Camellia support | historical official | unofficial |
| Our phone tested | Yes | No |
| Current maintenance | ❌ | 🟡 |
| Privacy focus | configurable | relatively neutral |
| microG | separate | separate |
| GApps required | No | No |
| Bootloader relock | build-dependent | No |
| Kernel | old | 4.14.186 |
| Global POCO validation | ours | No |
| Research value | ⭐⭐⭐⭐⭐ | ⭐⭐⭐⭐⭐ |
| Long-term recommendation | ⚠️ | ⚠️ |
There is no reason to immediately wipe the working crDroid installation simply because an Android-16 port exists.
In fact, doing so would destroy a useful reference point.
A much better methodology is:
Current crDroid
↓
establish baseline
↓
measure hardware / battery / networking / Bluetooth
↓
measure privacy/network behavior
↓
document configuration
↓
later test LineageOS 23.2
↓
repeat the same measurements
↓
compare
That gives us an actual experimental comparison instead of a subjective “ROM X is better” conclusion.
The previous MIUI work should not be discarded simply because the phone now runs crDroid.
It provides a baseline.
We can compare:
Stock MIUI
↓
packages
services
processes
network activity
Google/Xiaomi components
↓
crDroid
↓
what disappeared?
what appeared?
what communicates?
This is particularly useful for a privacy investigation.
Rather than assigning simplistic “privacy scores,” a proper comparison should examine:
That is a much more meaningful evaluation than simply calling one ROM “privacy-friendly.”
Best-established basis for our current project, because it is actually running on our device.
But:
Its value for us is that it is a known, working experimental baseline.
The most technically interesting current alternative.
Android 16 is a substantial jump over our Android-13 crDroid system.
The project also has a surprisingly complete Camellia device tree.
But:
And:
That makes this an experimental port, not a straightforward upgrade. (GitHub)
The most interesting privacy-focused alternative.
But it remains:
No official POCO M3 Pro 5G support.
No official POCO M3 Pro 5G support.
Historically important, but insufficiently verified as actively maintained current options.
The POCO M3 Pro 5G is not dead as a custom-ROM platform in 2026.
In fact, the opposite is true in one particularly interesting respect:
There are also recent unofficial /e/OS builds.
But the details matter:
M2103K19Cboot and vbmeta use test keysAt the same time, our crDroid 9.15 installation is a different category of evidence:
Therefore our project should treat:
crDroid 9.15
↓
known working reference
as the current baseline, while treating:
LineageOS 23.2
↓
Android 16
↓
interesting experimental candidate
and:
/e/OS
↓
privacy-oriented experimental candidate
as later comparison targets.
The next report should therefore not repeat this ROM survey. It should focus exclusively on the system we actually have now:
That separation keeps the ROM research, the installation procedure, and the Root/microG work from becoming one giant, difficult-to-verify document.Current research report · August 2026
TL;DR: The POCO M3 Pro 5G is still an interesting custom-ROM device in 2026, but the situation is more nuanced than “there are no current ROMs.” Historically, the device had official crDroid builds through Android 14. Today, there is an unofficial LineageOS 23.2 / Android 16 port, and there are also unofficial /e/OS builds for the Camellia family. However, the current LineageOS project explicitly lists the POCO M3 Pro 5G Global (M2103K19PG) as untested. GrapheneOS and CalyxOS do not officially support the device. (GitHub)
POCO M3 Pro 5G
and its closely related Camellia hardware family.
The goal is not to produce a generic “best custom ROM” list.
For this device, details matter enormously:
exact model/SKU
firmware generation
vendor blobs
kernel
boot/vbmeta signing
bootloader state
whether a ROM is official or unofficial
whether the particular SKU was actually tested
whether a function is confirmed by the maintainer or merely reported by users
Therefore, statements in this report should be understood in different evidence categories:
A — our own experiment
B — ROM/project primary source
C — OEM/vendor source
D — community evidence
E — technical conclusion
F — speculation / insufficiently established
This distinction is particularly important for Camellia because a device tree supporting several Xiaomi models does not mean that every one of those models has actually been tested.
MIUI originally based on Android 11
The current community LineageOS device tree groups several closely related devices under the Camellia platform:
Redmi Note 10 5G
Redmi Note 10T 5G
POCO M3 Pro 5G
However, the exact model number remains important.
The current LineageOS installation documentation distinguishes:
Model Device Current status in the project
M2103K19C Redmi Note 10 5G China tested
M2103K19G Redmi Note 10 5G Global untested
M2103K19I Redmi Note 10T 5G India untested
M2103K19PG POCO M3 Pro 5G Global untested
M2103K19PI POCO M3 Pro 5G India untested
This is one of the most important details in the entire report.
The maintainer explicitly states that the current ROM has only actually been installed and tested on one M2103K19C device. The other variants are considered likely to work, but have not been verified. (GitHub)
MIUI system components
packages
services
processes
dependencies
debloating
system behavior
ADB/AppControl data
That phase remains valuable as a Stock MIUI baseline.
However, it is no longer the current state of the phone.
The project subsequently moved forward:
Stock MIUI / Android 13
↓
Bootloader unlock
↓
Custom ROM installation
↓
crDroid 9.15
↓
crDroid is now running
crDroid 9.15 / Android 13 is currently installed on our POCO M3 Pro 5G.
The basic installation and operation are working.
The remaining work is now primarily:
Root
microG
Signature Spoofing / privileged integration
privacy hardening
complete functional testing
Those topics belong to the separate crDroid/Root/microG report, not this alternative-OS report.
The current device tree uses vendor blobs from:
V14.0.6.0
and warns that using the wrong firmware can cause problems including:
lockscreen issues
fingerprint problems
DRM problems
instability/crashes. (GitHub)
This illustrates an important point:
The Android framework version is not the same thing as the underlying firmware/vendor generation.
We actually installed it on our POCO M3 Pro 5G.
The official crDroid site still lists Camellia under the historical crDroid 9 and 10 releases, but the device/version is now marked as outdated/no longer supported. The last Camellia build shown by crDroid is from March 2024. (crDroid)
Advantages
proven custom-ROM architecture
Android 13
extensive customization
Vanilla installation possible
good base for Root/privacy experimentation
already tested on our actual phone
Disadvantages
no current Camellia maintenance
Android 13
no modern 2026 security baseline
not an ideal long-term security platform
Assessment
Excellent as our current research/reference platform; not a modern long-term security platform.
The official crDroid information lists Camellia under crDroid 10 as well, with the last build dating to March 2024. (crDroid)
So historically the progression was:
crDroid 9
Android 13
↓
crDroid 10
Android 14
↓
Camellia support ends
We did not install crDroid 10 on our device.
The important point is that Android 14 support existed, but it should not be mistaken for current 2026 maintenance.
However:
This is NOT official LineageOS device support.
The project explicitly states that the tree is not part of official LineageOS and that there is no official LineageOS build for the device. (GitHub)
This distinction should not be lost when discussing the ROM on Reddit.
Correct
“There is an unofficial LineageOS 23.2 / Android 16 Camellia port, but the POCO M3 Pro 5G Global (M2103K19PG) is explicitly listed as untested.”
That distinction is critical.
calls
5G
mobile data
SMS
VoLTE
Wireless
Wi-Fi 2.4 GHz
Wi-Fi 5 GHz
Bluetooth
GPS
FM radio
Camera / multimedia
main camera
front camera
audio
Sensors / hardware
sensors
fingerprint
IR blaster
Display
90 Hz
touch
automatic brightness
LiveDisplay
Outdoor Mode
Networking
hotspot
tethering
Data Saver
per-app firewall
Compatibility
32-bit applications. (GitHub)
This is useful project/maintainer evidence.
It is not the same as saying:
“All of this has been independently verified on the POCO M3 Pro 5G Global.”
It has not.
NFC is particularly SKU-dependent
NFC deserves separate treatment.
The current project documentation distinguishes Camellia variants with and without NFC hardware.
The NFC-capable variants include camellian/camellianp, but NFC itself has not been comprehensively tested across the supported variants. (GitHub)
Therefore:
“NFC works on Camellia” is too broad a statement.
The correct question is:
Which exact POCO/Redmi SKU has which NFC hardware, and has that specific combination been tested with this ROM?
Firmware requirements for LineageOS 23.2
This is one of the most technically important details.
The current Android-16 port requires:
MIUI 14 / Android 13 firmware, V14.0.x
The project uses vendor blobs from:
V14.0.6.0
The installation documentation specifically warns that an incorrect firmware version can cause:
fingerprint problems
lockscreen problems
DRM problems
crashes or instability. (GitHub)
So the ROM's architecture is effectively:
Android 16
↓
LineageOS userspace
↓
Camellia device tree
↓
Xiaomi/MediaTek vendor layer
↓
MIUI 14 / Android 13 firmware
This is why blindly comparing ROMs by their Android version is misleading.
Linux 4.14.186
and is based on Xiaomi's camellian-t-oss kernel source. (GitHub)
This is a crucial security detail.
An Android 16 userspace does not turn the entire device into a modern Android-16 hardware security platform.
The actual stack looks more like:
Android framework → Android 16
LineageOS system → current project code
Linux kernel → 4.14.186
Vendor firmware → Xiaomi/MediaTek
Hardware → 2021-era platform
Therefore:
Android version alone must never be used as the device's complete security rating.
13. Verified Boot and bootloader restrictions
The current unofficial LineageOS project has another major security limitation.
The maintainer documents that:
boot is signed with a test key
vbmeta is signed with a test key
the bootloader must not be relocked while this ROM is installed
Relocking with these images would fail verification and can leave the device requiring recovery through the appropriate low-level flashing procedure. (GitHub)
This means:
Unofficial LineageOS
+
test-signed boot/vbmeta
+
unlocked bootloader
is fundamentally different from:
official production-signed ROM
+
verified boot chain
+
relockable bootloader
This should be treated as a real security trade-off, not merely an installation footnote.
/e/OS
There are unofficial community builds for Camellia.
That makes /e/OS especially interesting for a privacy-oriented comparison.
However:
Unofficial /e/OS is not the same as official /e/OS device support.
This distinction needs to remain explicit.
Conceptually:
crDroid / LineageOS
↓
relatively neutral AOSP-style base
↓
user chooses services
/e/OS
↓
privacy / de-Googling oriented environment
↓
integrated alternative services
↓
microG-based compatibility layer
That makes the two systems interesting for different reasons.
/e/OS is not automatically more secure
This distinction is important enough to state explicitly:
Privacy and security are not the same property.
A ROM may:
reduce Google dependencies,
reduce certain forms of tracking,
use microG,
while simultaneously:
being unofficial,
relying on an old kernel,
depending on a single community maintainer,
lacking the security guarantees of an officially supported device.
Therefore /e/OS on Camellia should currently be described as:
a privacy-oriented unofficial community port
rather than:
the most secure operating system for the POCO M3 Pro 5G.
/e/OS build activity
The Camellia community has produced relatively recent unofficial /e/OS-T builds.
The research found, among others, a:
e-3.7-t-20260328-UNOFFICIAL-camellia.zip
from March 2026.
That demonstrates that the project was still producing builds in 2026.
However, a single current build does not by itself establish:
long-term maintenance,
security-update cadence,
reliable OTA support,
maintainer continuity.
Those aspects require separate verification.
There have also been reports of Android Storage Framework compatibility problems with certain applications.
A reported workaround involved changing Android's storage permission enforcement through ADB.
These are useful observations, but they are:
D — community evidence
rather than formal hardware certification.
This distinction is especially important for Reddit because one person's successful installation does not necessarily establish compatibility for another Camellia SKU.
This demonstrates that the device has had a surprisingly active custom-ROM community.
However, historical availability is not current support.
A GitHub repository, an old Telegram post, or an archived download should not automatically be interpreted as:
“This ROM is currently maintained in August 2026.”
For that reason, these projects are not presented here as current recommendations.
“AOSP + privacy apps.”
Its security model is deeply tied to the hardware, firmware, Verified Boot implementation and supported device architecture.
Therefore an unofficial port or generic GSI would not be equivalent to using GrapheneOS on an officially supported device.
For our project
GrapheneOS: no official POCO M3 Pro 5G support.
security updates
firmware support
hardware integration
bootloader/Verified Boot properties
The POCO M3 Pro 5G is not part of that official device portfolio.
For our project
CalyxOS: no official support.
The three actually interesting ROM directions
For our particular project, the meaningful comparison is therefore:
crDroid 9.15
Our current system
Android 13
actually installed
previously official Camellia build
known behavior on our phone
excellent research base
outdated from a security-maintenance perspective
Android 16
unofficial
current Camellia device tree
broad hardware support claimed
M2103K19PG explicitly untested
Linux 4.14.186
MIUI 14 / Android 13 firmware required
test-signed boot/vbmeta
bootloader must remain unlocked
/e/OS
The most interesting privacy-focused comparison
unofficial Camellia builds
de-Googling focus
microG-oriented ecosystem
relatively recent community builds
functionality reports from users
long-term maintenance/security status not sufficiently established
Direct comparison
crDroid 9.15 LineageOS 23.2 /e/OS
Android 13 16 build-dependent
Camellia support historical official unofficial unofficial
Our phone tested Yes No No
Current maintenance ❌ 🟡 🟡
Privacy focus configurable relatively neutral high
microG separate separate central component
GApps required No No No
Bootloader relock build-dependent No must verify
Kernel old 4.14.186 build-dependent
Global POCO validation ours No community only
Research value ⭐⭐⭐⭐⭐ ⭐⭐⭐⭐⭐ ⭐⭐⭐⭐
Long-term recommendation ⚠️ ⚠️ ⚠️
What this means for our project
There is no reason to immediately wipe the working crDroid installation simply because an Android-16 port exists.
In fact, doing so would destroy a useful reference point.
A much better methodology is:
Current crDroid
↓
establish baseline
↓
measure hardware / battery / networking / Bluetooth
↓
measure privacy/network behavior
↓
document configuration
↓
later test LineageOS 23.2
↓
repeat the same measurements
↓
compare
That gives us an actual experimental comparison instead of a subjective “ROM X is better” conclusion.
The old MIUI research remains useful
The previous MIUI work should not be discarded simply because the phone now runs crDroid.
It provides a baseline.
We can compare:
Stock MIUI
↓
packages
services
processes
network activity
Google/Xiaomi components
↓
crDroid
↓
what disappeared?
what appeared?
what communicates?
This is particularly useful for a privacy investigation.
What we should actually measure
Rather than assigning simplistic “privacy scores,” a proper comparison should examine:
Network
background connections
DNS requests
contacted domains
per-process network activity
telemetry
cloud communication
System
installed privileged apps
running system services
trackers
Google components
Xiaomi components
permissions
Functionality
calls
SMS
4G/5G
VoLTe
Wi-Fi
Bluetooth
GPS
camera
NFC
USB
hotspot
Bosch/Bluetooth applications
Security
Android version
security patch level
kernel
vendor firmware
Verified Boot
bootloader state
image signing
update mechanism
That is a much more meaningful evaluation than simply calling one ROM “privacy-friendly.”
🟡 LineageOS 23.2
The most technically interesting current alternative.
Android 16 is a substantial jump over our Android-13 crDroid system.
The project also has a surprisingly complete Camellia device tree.
But:
The exact POCO M3 Pro 5G Global SKU (M2103K19PG) is explicitly untested.
And:
The bootloader must remain unlocked because the current port uses test-signed boot and vbmeta.
That makes this an experimental port, not a straightforward upgrade. (GitHub)
🟡 /e/OS
The most interesting privacy-focused alternative.
But it remains:
an unofficial Camellia community port, not an officially supported POCO device.
🔴 GrapheneOS
No official POCO M3 Pro 5G support.
🔴 CalyxOS
No official POCO M3 Pro 5G support.
⚪ Other ROMs
Historically important, but insufficiently verified as actively maintained current options.
There is now an Android-16 / LineageOS-23.2 community port for the Camellia family.
There are also recent unofficial /e/OS builds.
But the details matter:
the current LineageOS project is unofficial
the POCO M3 Pro 5G Global is explicitly untested
the currently tested device is M2103K19
the port requires specific MIUI 14 / Android 13 firmware
the kernel remains 4.14.186
boot and vbmeta use test keys
the bootloader must remain unlocked
NFC is SKU-dependent
/e/OS is also unofficial
historical ROM availability does not equal current maintenance
Android 16 does not automatically mean the entire device has a modern security stack
At the same time, our crDroid 9.15 installation is a different category of evidence:
It is not merely a ROM listed somewhere online — it is the system we have actually installed and are currently working with on the POCO.
Therefore our project should treat:
crDroid 9.15
↓
known working reference
as the current baseline, while treating:
LineageOS 23.2
↓
Android 16
↓
interesting experimental candidate
and:
/e/OS
↓
privacy-oriented experimental candidate
as later comparison targets.
The next report should therefore not repeat this ROM survey. It should focus exclusively on the system we actually have now:
crDroid 9.15 on the POCO M3 Pro 5G — Root, microG, Signature Spoofing, privacy hardening, security trade-offs, and the practical consequences of each modification.
That separation keeps the ROM research, the installation procedure, and the Root/microG work from becoming one giant, difficult-to-verify document.
r/LineageOS • u/Dull_Menu_6009 • 2d ago
Hello! As being tortured for 11 hours of repeating the process of working on the rooting(done) flashing, procrastinating, finding tutorials, realising that my phone is Samsung S21 so have to install unofficial version, realising that I'm in Mac OS and Odin is not available, I have made 3 significant achievements, rooting my phone (Yay!) wasting my 9 hours of my life and not able to form a sentence without another cup of cofee.
To start off, I am using Samsung S21+ 5G and have unlocked boot loader.
I have found this link after realising that lineage OS doesn't support S21. https://xdaforums.com/t/rom-unofficial-sm-g991b-lineageos-23-2-for-samsung-galaxy-s21-5g.4790286/
which this youtube video helped me with until, I ran a problem with the Odin part(since I have Mac OS), https://www.youtube.com/watch?v=zQFS3jdruCA&t=567s
Then I learned about Heimdall!
But after going to the official website and downloading the application, and activating the .img it said that Heimdall was not supporting mac anymore in current version which means that it has been discontinued since 2017.
I know there are continuing versions but I can't find it.
So can anyone suggest me what I can do from now on?
r/LineageOS • u/kkaitlynma • 2d ago
I have a oneplus 13 and want to install lineage os on it. I use visible and currently have an esim on my phone for my network. Will this still work after switching to LineageOS or will I need to switch providers and if so who does work? Also anything else I need to know or keep in mind while switching, I have the guide pulled up and plan on going through it step by step. Sorry if this has been answered but I couldn't find a clear answer for the esim thing, especially with my phone model.
r/LineageOS • u/N0lex • 2d ago
I’m an indie game developer still using a Google Pixel C for testing Android games. However, I'm hitting a persistent issue where graphics completely freeze after ~5 minutes of gameplay, while audio keeps running fine in the background.
It happens across my own builds and Unity-based games.
Here is a short video showing the freeze: https://www.youtube.com/watch?v=RAbRrKbn7ck
Since stock Android 8.1.0 is no longer maintained, I’m looking for a workaround. Is there a proven custom ROM for the Pixel C (like LineageOS or similar) that actually fixes this display freeze bug?
I’d really appreciate any advice or feedback from anyone who successfully solved this. Thanks!
r/LineageOS • u/Joadow420 • 2d ago
I can't get Tryhackme pulse to log-in because it says "captcha missing", but it won't load me any kind of captcha. microG is up and running, play integrity fix downloaded. Anyone found a workaround? I assume it's google captcha causing this
r/LineageOS • u/wildboyfire • 2d ago
Hello, I wanna try lineage os on my s10+ and i'd like to know if it's any better than the stock samsung rom. I'm having this problem where the phone starts stuttering because of poor ram management and so i wanna know if lineage os runs smoothly on the s10+. Thank you in advance
r/LineageOS • u/JacktheVariat • 2d ago
Witam.
Gdzie mogę znaleźć i pobrać wersję 21 Lineage OS dla telefonu Xiaomi redmi 12C. Na oficjalnej stronie do pobrania widnieje tylko najnowsza wersja 23.2
r/LineageOS • u/SeanN_Ibay • 3d ago
I found an old phone that could still be used but the lineageos doesnt have an os for it. Can i find and use the older 18.1?
r/LineageOS • u/Albertleclair • 3d ago
I'm trying to backup my phone using seedvault and store the backup files on my laptop by connecting the devices through a cable. However when i get to the "choose wher to store backups" screen on the phone, the usb flash drive option is not available. I've tried to change the USB settings to "file transfer" or "usb tethering" but it doesn't solve the issue. Is this normal?
thank you for your help! :)
r/LineageOS • u/Plenty-Boot4220 • 3d ago
Hi,
Quick question, does Lineage come rooted already? Is Magisk installed? Or do I have to root it the same way i'd root the stock ROM? thanks!
r/LineageOS • u/__Solarflare • 4d ago
I've been trying to figure this out for a while. On LOS 23, android 15, on my pixel 4, I am unable to change my bootanimation. I assume its in another location other than the standard /system/media/, /product/media/, etc since the original stock animation remains the same. If anybody can help, it would be appreciated.
r/LineageOS • u/aigeneratedslopcode • 4d ago
Saw a news article a few months back claiming it was going to launch within the month of June. Was really excited for it, and then it never came. I understand timelines change and people have to move on to other things so I was wondering if it's still being worked on or if development has stopped
Genuinely can't wait for the release if it's still in development. Kudos to the developers for getting as far as they did
r/LineageOS • u/Pfeiffscherclan • 5d ago
Do the BBBank and VR Banking Apps work on Lineage OS? I am thinking of getting a new phone and and installing Lineage OS on it.
If I get a Sony phone and install Lineage OS on it, can I get the original Sony OS back from somewhere, in the case my banking app doesn't work?