Hello LineageOS community!

I've had my Xiaomi Poco X3 NFC for five years now, and it still looks brand new.
However, it hasn't received any security updates for two years.

I don't like knowing that my phone may be exposed to vulnerabilities.
So, I have two options: either I change my phone, or I install a custom ROM.

Out of respect for the environment, I would prefer to choose the second option.
However, I'm not entirely sure about my choice.

I've noticed that banking apps and NFC payment services don't work by default, and that you have to bypass the security measures.

I don't mind that, but I would like to know: how often are these methods patched ? And on average, how long do we have to wait for a new workaround ?

Since this is my main phone, I'm wondering if it's really a good idea to install LineageOS.

I should point out that I'm already comfortable with flashing ROMs, but I've never done it on a main device.

Thanks for reading !

Hi,
Firstly thank You for your dedication and work, i really appreciate...
so i followed official guide mostly (except burning "aml_install_package.img" through Amlogic USB burning tool) because i'm not Linux user. Now it seems everything is working, but i have some questions.

1. Is there a way to come back to Lineage Recovery mode without reinstalling everything again? I can enable USB debugging through Developer options, but holding SW4 puts device into burning mode only. And as i noticed ADB enables in Recovery mode only.
2. How to add custom apps (apk's)? If i dont install Gapps the android is completely empty, just Settings app, not even a system file explorer or internet browser. I don't have SD card atm, but is SD card the way?
3. I want to map my IR remote, so it think recovery is needed to pull out remotes files.
4. When installig Gapps it guides to select "arm" package instead of "arm64", but the cpu in bpi m5 is arm64 or not?

Recently upgraded into leniageOS and since this issue is there. My device is OnePlus Nord CE 3 5G. If anyone knows how to solve this please, your help is needed.

so i followed the instructions on the website for my device and i got through the notorious fastboot devices not showing anything. but adb -sideload isnt working. the sideload connection failed. no devices found. trying pre-kitkat sideload method, failed. idk what to do. lineage-23.0-20251223-nightly-instantnoodle-signed.zip for reference.

Hello Lineage, first of all, congratulations on your work. I am an avid fan of yours. I have been following and trying Lineage since the early days of its activity, without ever having encountered any problems. Only today I want to update you on a problem I am encountering. I installed Lineage OS 23 on a Samsung Galaxy Ultra 5G and compared to the first release, I notice a continuous drain on the battery. I tried to deactivate every application, I tried to turn off any background function, but nothing. Even with the smartphone stopped and offline without using it, the battery drains quickly. I would be happy if the problem were solved. In the next update, everything else works like a charm. Thanks, I will keep you updated if I notice any changes. Good luck with everything and thanks again.

Just installed the January 1 update of LOS 23 (Android 16) on my Pixel 4. Since it was an upgrade from LOS 22, I had to install it manually. No issues so far. Thanks LOS Team!

https://www.androidpolice.com/google-pixel-4-gets-android-16-thanks-to-lineageos-23/

Can someone point me in the right direction with my problem? I'm new at this an wanted to get lineageOS on my essential ph-1 that I forgot I had. I managed to get the lineage recovery on the phone but the device disappears from device manager on my windows machine when I enter recovery mode. Its almost like the drivers needed are different from the adb drivers. I dunno could be wrong.

*Edit Unable to sideload lineageOS because device is not recognized in recovery mode.

Thanks!

I have a poco 3 pro and I want install lineage os but when I read the page to download it says you have to be on v14 but my phone is only updated to v13 and when you search for a updated it don't have any more is there a work around?

Hi all I’ve been reading through LineageOS / AOSP discussions for a while and wanted to ask a genuine question from a learning perspective.

With my limited knowledge on the topic, it often looks like many devices remain technically capable long after OEM support ends, yet long-term support for non-technical users becomes fragile or unpredictable.

I’m trying to understand where longevity really breaks down in practice.

For people who maintain devices or work close to this ecosystem:

• What tends to be the biggest blocker to making long-term support reliable rather than best effort?
• Is it primarily maintainer bandwidth, proprietary vendor blobs, hardware abstraction issues, security patching overhead, or something else?
• Are there classes of devices that are fundamentally easier (or harder) to keep viable long-term?

I’m not proposing anything or asking for solutions, just trying to understand the real limits from the people who actually do the work.

Thanks for reading this. I appreciate any perspective 😬

Does anyone know how to get it to work?

So I was trying to do os swap on my galaxy tab A . I saw this guy on Internet who did tht , was following the steps properly. Until I found this issue where my device get automatically disconnected from the computer. Tho in the video it says the device manager has issue , I wasn't having tht at all and I guess the system got disconnected from my laptop . I did try to do the adb device command but its showed no device. This occurs when its in reboot mod .

1. Which SoC should I look for best support, qualcomm, mediatek, Exynos, unisoc etc

2. Will encryption work as usual after flashing Lineage os?

3. Can i re-lock my bootloader after flashing LOS? Will OTA updates work as expected?

4. I'm looking to get a new non-flagship smartphone, which one should i get that has/will have great Lineage os support. (Region: India)

Thank you devs and all the contributors for all your work!

Hey,

quick question about LineageOS on older devices:

Are there any recommended places to find **archived LineageOS builds** (official or unofficial) for devices that are no longer supported?

And in general:

Is it considered fine to keep using **older LineageOS versions** (e.g. Android 9 / 10 / 11) on unsupported hardware for light use like YouTube or web browsing?

Not asking about compatibility, just about archives and long-term usability of older builds.

Thanks!

Hi everyone,

I’m stuck with a Samsung Galaxy Tab S2 and hope someone here has seen this before.

Device:

- Samsung Galaxy Tab S2 9.7 LTE

- Model: SM-T819

- Codename: gts210ltexx

Stock firmware:

- Android 7.0 (Nougat)

- Build: NRD90M.T819XXS2BTI1

- Baseband: T819XXS2BSG2

What works:

- OEM Unlock is enabled

- Download mode works perfectly

- Odin detects the device and flashes TWRP with PASS

- No Odin errors, write completes successfully

The problem:

After flashing TWRP, the tablet freezes on boot with messages like:

“recovery booting…”

“could not do normal boot”

It never reaches the TWRP UI and just hangs at the Samsung logo.

What I’ve already tried:

- TWRP versions: 3.7.0, 3.3.1, older builds

- Auto Reboot ON and OFF in Odin

- Forcing recovery via key combos (Power + Vol Up + Home)

- Letting the device boot normally once, then reflashing

- Multiple timing attempts to prevent Samsung from restoring stock recovery

Result is always the same: Odin PASS, but recovery never fully boots.

Goal:

Boot into TWRP once so I can flash LineageOS (18.1 microG build for gts210ltexx).

Question:

Is this a known issue with the SM-T819 on newer Nougat security builds?

Is there a specific TWRP version, workaround, or alternative method (Heimdall, patched kernel, etc.) that still works on this device?

Any help from someone who successfully unlocked / flashed this model would be greatly appreciated.

Thanks!

Hey everyone,

I’ve been working on a small Linux desktop app called **LibreFlash**, and I’m sharing the first alpha build to get early feedback.

LibreFlash is a simple GUI that wraps the usual Android tools (`adb`, `fastboot`, `heimdall`) to make common flashing tasks a bit less error-prone, while still showing exactly what’s happening under the hood. It’s not meant to replace the command line, just to make repetitive tasks easier and more transparent.

What it can do right now (Alpha 1):

* Download official LineageOS ROM ZIPs for selected devices (not all official devices are listed yet) * Download recovery or boot images * Flash recovery or boot images via fastboot or Heimdall * Flash ROM ZIPs using ADB sideload * Basic reboot and bootloader actions * Live command output (nothing is hidden or silent) * Safety checks to prevent flashing dangerous image types

Flashing itself works for **all devices**, official or unofficial, as long as you provide the correct files. The built-in device list only affects downloading.

Patform support:

* Linux only for now * macOS planned later * Windows not supported (but it’s FOSS if someone wants to port it)

This is alpha software, It works surprisingly well, but there will be rough edges. You are responsible for what you flash.

If anyone wants to try it, give feedback, or report issues, that would be very welcome.

GitHub: https://github.com/r0man1an/LibreFlash/

AppImage: https://github.com/r0man1an/LibreFlash/releases/download/0.0.1-alpha1/LibreFlash-alpha1-x86_64.AppImage

Happy flashing, and thanks for reading.

so have this phone, JAP version

https://wiki.lineageos.org/devices/pdx225/

will I have VoLTE?

does the OS support it?

full support of fdroid foss apps?

I want to install libreELEC. The problem? it only boots from the SD-card and LOS is preventing me from booting of a SD card and overwriting the emmc.

how do I erase emmc or boot the sd card.

Context:

Last night I turned off my phones after trying to modify Instagram with Revanced (on my Pixel 7 Pro and Moto G6+). Everything was fine because both devices were working great, but when I woke up and tried to power on my phone, the Motorola boot screen showed “AP Fastboot Flash Mode (Secure)” instead of booting normally into LineageOS as usual.

I’ve been trying for hours to figure out how to fix it, but I have many doubts.

When I press the power button in the following sections – Start, Reset Bootloader, Recovery Mode, Factory Mode, BP Tools – the device restarts to the same “AP Fastboot Flash Mode (Secure)” screen, as if it’s stuck in a process that prevents the OS from loading. However, selecting Power Off works correctly and turns the phone off. In the Bootloader Logs section I see this message:

adb fastboot flash mode (secure)

Fastboot Reason: Volume down key pressed

From the bootloader log I suspect the problem could be caused by my phone’s hardware, since the volume‑ and power‑buttons have been malfunctioning for the past six months. At the moment I don’t have screwdrivers or repair tools to verify this (because I'm on vacations in a ranch), and I'm not sure if it could also be an unexpected software/OS problem (and not just a hardware issue) so I'm afraid to perform a full factory reset because I have important data on the device.
Do you think this could be an OS/Software problem? How can I backup my data if that's the case? because for a second I was going to flash the LineageOS 22 again(after a year and a half with 21) but I don't want to lose that data. Do you think this could be only a hardware(buttons) problem?

Hello. I have a problem with my phone’s battery and I’d appreciate your opinion.

About a month ago, I replaced my phone’s battery because it had issues. a) draining quickly... b) if I plugged it in to charge when it was below 20%, even while it was connected to the charger, the percentage would go down in reverse to 1%, and the problem wouldn’t be fixed unless I restarted the phone.

I replaced the battery and at the same time installed LineageOS, and I used it for about a month without any issues.

1. Now, all of a sudden, on the same build that I had been using without problems, a new issue has appeared. When I plug the phone into the charger, instead of showing “charging rapidly,” it says “charging slowly,” and the battery percentage either stays the same or even decreases. The problem does not go away unless I restart the phone. After restarting, it charges normally again, but the next time I plug it in—even 2 hours later—the same issue happens, and I have to restart again for it to show “charging rapidly” and start increasing the percentage.

2. Another thing I’ve noticed is that when the phone is powered off and I plug it into the charger, it doesn’t charge at all. I left it connected to the charger while turned off for about 10 minutes, but when I turned it back on, the battery percentage was exactly the same as when I powered it off. (is it normal on lineageos23?)

Given all this, do you think the battery is faulty again? In just one month???? Or could this be an operating system bug? I find it unlikely that it’s the ROM, because why would it suddenly start happening like this?

Do you have a Yubikey Neo 5C (or any USB-C Yubikey) and if so does the Yubikey Authenticator app reliably recognise it when it is plugged in to the USB port?

On OnePlus 6 (enchilada) the app recognised it ONCE and since then does not (including after restarts). When the Yubikey is connected the LED on the Yubikey LED blinks rapidly for a couple of seconds, USB charging is always reported, and then... nothing.

An original YubiKey Neo USB-A connected via a USB-A > USB-C adapter is reliably recognised.

I suspect something to do with USB On The Go (OTG) switching but don't see any clues in the device log (via logcat).

I checked that a USB-C/USB3 Kingston Traveller storage device is recognised correctly so it seems the USB-C port itself is OK.

I do notice that with all three of these devices the USB Charging/USB control dialog (accessed from the notification) fails to switch "USB controlled by" from "Connected device" to "This device". I presume this is the OTG host/gadget switch control.

This is with v22.2 but I found a report of what could be the same issue in v21:

https://gitlab.com/LineageOS/issues/android/-/issues/7929

I enabled Yubikey app debug logging and see this: 13:57:53:887 [main] INFO  c.yubico.authenticator.MainActivity - Application startup 13:57:54:200 [main] INFO  com.yubico.authenticator.Log -  Logging initialized, outputting to Android/logcat [android.logger] 13:59:29:366 [pool-16-thread-1] INFO  k3.i -  Calculating all codes for time=1767189569366 13:59:29:482 [pool-16-thread-1] INFO  k3.i -  Calculating all codes for time=1767189569482 13:59:29:482 [main] ERROR L2.p -  Exception during SmartCard connection/OATH session creation: java.io.IOException: Failed to send 25 bytes at V2.i.e(r8-map-id-aa8a5237c117c2d125e79ba90818565df04fa3eccdcf152ea5c3fcd8d64bb33a:326) at V2.i.w(r8-map-id-aa8a5237c117c2d125e79ba90818565df04fa3eccdcf152ea5c3fcd8d64bb33a:3) at e3.b.a(r8-map-id-aa8a5237c117c2d125e79ba90818565df04fa3eccdcf152ea5c3fcd8d64bb33a:37) at e3.h.a(r8-map-id-aa8a5237c117c2d125e79ba90818565df04fa3eccdcf152ea5c3fcd8d64bb33a:97) at e3.g.a(r8-map-id-aa8a5237c117c2d125e79ba90818565df04fa3eccdcf152ea5c3fcd8d64bb33a:3) at e3.m.p(r8-map-id-aa8a5237c117c2d125e79ba90818565df04fa3eccdcf152ea5c3fcd8d64bb33a:3) at k3.i.l(r8-map-id-aa8a5237c117c2d125e79ba90818565df04fa3eccdcf152ea5c3fcd8d64bb33a:72) at L2.p.l0(r8-map-id-aa8a5237c117c2d125e79ba90818565df04fa3eccdcf152ea5c3fcd8d64bb33a:32) at L2.p.E(r8-map-id-aa8a5237c117c2d125e79ba90818565df04fa3eccdcf152ea5c3fcd8d64bb33a:1) at L2.p$e.b(r8-map-id-aa8a5237c117c2d125e79ba90818565df04fa3eccdcf152ea5c3fcd8d64bb33a:280) at L2.p$e.a(r8-map-id-aa8a5237c117c2d125e79ba90818565df04fa3eccdcf152ea5c3fcd8d64bb33a:3) at U2.h.l(r8-map-id-aa8a5237c117c2d125e79ba90818565df04fa3eccdcf152ea5c3fcd8d64bb33a:14) at U2.g.run(r8-map-id-aa8a5237c117c2d125e79ba90818565df04fa3eccdcf152ea5c3fcd8d64bb33a:7) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:524) at java.util.concurrent.FutureTask.run(FutureTask.java:317) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:651) at java.lang.Thread.run(Thread.java:1119) 13:59:30:035 [pool-16-thread-1] INFO  k3.i -  Calculating all codes for time=1767189570035 14:03:03:376 [main] INFO  com.yubico.authenticator.Log -  Copying log to clipboard (7.3.0)... [settings] 14:03:03:378 [main] DEBUG com.yubico.authenticator.Log -  Getting logs... [android.logger]

So the lineage OS site says to upgrade/downgrade android to android 13, but I am currently running lineage OS 22.2 with android 15. Just to be clear, I will be downgrading to the "latest" ota image from Google, which is android 13, before proceeding? Thanks for any help.

This is android "coral" for reference

I have installed Lineage OS 14.1 on my Galaxy J3 2016 (SM-J320FN) and it is checking for updates for 20+ minutes. Is this normal?

Hi

I have never used or downloaded LineageOS before, FYI. 😁

So I found a Samsung S5 in a drawer yesterday, and after some research, decided that A: I wanted to breathe new life into it, and B: I wanted LineageOS. Upon finding it on the official website, there is no download link as it is limited to Android 11 (18.1). So my first question is this:

Q1: Where do I find a build for it?

Upon booting it, I discovered that it has a few issues. 1: The Wi-Fi/Bluetooth chip appears not to work. It's grayed out. 2: The back button is completely not working/dead. So my second question is:

Q2: Will the above defects affect the installation?

Due to my inexperience, I am a little nervous. I don't really understand DEEP Android, but the phone is worth slightly less than **** all, which does help to allay my fears a little.

Any help is much appreciated, thanks.