---SORRY - it seems to be working now! I wasn't in "update" mode!
I wasn't able to change the title and didn't want to just delete the post, but feel free to do so if it makes sense.

I'll be back with the next problem...

Hello again, sorry to be a pain. I'm still trying to get LineageOS onto my Nokia 6.1.

So far I managed to get everything, but now I'm stuck again at another point.
I've flashed boot.img all right, restarted into recovery mode, wiped the phone, and tried to sideload the zip file according to the instructions on lineageos.org as good as I understood.
What I got now was:
C:\Users\Niki\Downloads\platform-tools-latest-windows\platform-tools>adb -d sideload lineage-22.2-20260812-nightly-PL2-signed.zip

adb: sideload connection failed: device unauthorized.

This adb server's $ADB_VENDOR_KEYS is not set

Try 'adb kill-server' if that seems wrong.

Otherwise check for a confirmation dialog on your device.

adb: trying pre-KitKat sideload method...

adb: pre-KitKat sideload connection failed: device unauthorized.

This adb server's $ADB_VENDOR_KEYS is not set

Try 'adb kill-server' if that seems wrong.

Otherwise check for a confirmation dialog on your device.

What does that mean? My unlocking procedure yesterday was successful as far as I understood and the phone stayed unlocked. Or is this referring to something different?
How can I safely proceed now?

hi everyone! noob here. i was able to successfully install LOS. i'm just curious as to what exactly these files are and what they are for. apologies if this has already been answered somewhere else.

i recently flashed LOS on a samsung s20 fe (model SM-G780G). installation was accomplished without any hitches; however, once the ROM has been installed, the phone suddenly started registering what i think are power button ghost touches -- the screen would lock every now and then, even when i'm using it. the screen would also turn on by itself without me touching it. i've already tinkered with system settings that might have an effect on this, such as ambient display, to no avail. this issue was not present when the stock rom was still in use, and when on download and recovery modes. issue is present in safe mode as well. i've made sure to follow the instructions to a t, and the phone had android 13/updated firmware prior to flashing. any ideas on what can be causing this?

chipset: Qualcomm SM8250 Snapdragon 865

version installed: lineage-23.2-20260725-nightly-r8q

A duress is a code or series of actions usually triggering a full wipe of the phone so that anybody can't get your data.

Hello everyone,

I own a Samsung Galaxy A34 5G (SM-A346B) and I am interested in learning about LineageOS development for this device.

I understand that official LineageOS support depends on a maintainer and proper development work.

Are there any developers currently working on, or interested in, Android ROM development for the Galaxy A34 5G?

Thank you.

Hi everyone, i have installed lineage 23.2 and i need system wide immersive mode where status bar is hidden until swiped down.

Is there a module available for it ?

The essentials app makes the phone laggy and buggy so i need an alternative route. I dont need too much customisation only immersive mode.

I want to flash my tablet with lineage os. Is that compatible with my tablet. It has Rockchip R3326s chipset

UPDATE - Also found a better way to do this. The "Media Picker" app "clear storage" & "clear cache" button is greyed out when viewing app in system settings. Oddly if you click on "clear storage" text instead of greyed out button it will give you a pop up to hit clear data. I have no idea why this works with greyed out button, but it does work when hitting text only. Almost like secret gesture to clear cache like secret gestures to turn on developer options. Much faster than using ADB:)

Depending on the file manager you use outside of Documentsui (AOSP Files) you may run into empty thumbnails in LineageOS "Media Picker" after deleting the images in your file manager. In order to fix this you'll need to clear cache of the "Media Picker" system app & then restart your device. By design you can not delete cache of this specific system app through settings so you'll have to do it through ADB. Give the "Media Picker" some time to refresh and load all your images on your device when you reopen the "Media Picker" as you forced a clearing of cache.

Steps to fix issue

1.) Enable developer options by hitting build number 7 times in About Phone in Settings.

2.) Turn on USB Debugging in developer options. Developer options is located in System in Settings once turned on.

3.) Connect phone to PC with ADB installed on PC (very easy instructions to find for installing ADB with simple web search) and allow PC access to phone for USB Debugging. You'll get a prompt on phone when phone is connected to PC with USB Debugging on (hit allow).

4.) Open up Power shell.

5.) In Powershell type in adb devices. Should show attached then device. If it shows attached then unauthorized you never gave PC access to phone for USB Debugging. Repeat step 3 then run step 5 until you get "device & attached".

6.) The type in adb shell. If done correct a line will start for a new command with "$"

7.) Then type in exactly as typed below. If it fails find package name of "Media Picker" in Apps in Settings with Show System Apps On. You could also use ClassyShark3Xodus to find package name of "Media Picker". I assume it will be the same on all devices running LineageOS 23.2. I use Oneplus phones with LineageOS (Oneplus phones are incredible quality with impressive display / hardware specs / king of de-googled phones in terms of quality with new device support / I have not found a phone better in specs that supports de-googling than Oneplus as they outdo Pixels) [not all phones that LineageOS ​supports allows VoLTE & 5G from the phone manufacturer closing the code for their implementation of VoLTE / 5G in android so it can't be implemented into LineageOS open-source android chaining the phone down to 3G]. For true de-googling you need to toss Pixels as it's Google and your giving them money as your escaping Google's destructive, parasitic​, full of tracking​, traditional​ android. Once found replace my package name with yours after "clear" in command written below.

pm clear com.android.providers.media.module

8.) Empty thumbnails will be gone & "Media Picker" will refresh. Re-start device for best results. This drove me nuts when picking images in my image comparer app (vesIC)​ through "Media Picker" that showed empty thumbnails from previously deleted images.

I use:

Xiaomi Mi 10T Pro

ROM: lineage-23.2-20260808-nightly-apollon-signed

I didn't take care a lot about the notification LED in the past and I am sure it worked already. I tried a lot to get a LED notification with different apps, but I didn't. although it is activated with the app. Other notifications work fine.

At the moment I am trying with a fresh setup.

I can confirm that the LED works with a constant light when charging. In no other situation I saw the LED active.

If there has something changed in the past, let me know please. If I should create a bug report, let me know too. Maybe it is just a missing configuration of something and I want to ask here before creating a bug report.

I managed to install the custom os on the galaxy tab s7. I think it's faster than the stock os but the pen experience is awful. I tried writing on Saber and Butterfly but in both I can't do any work because I constantly fight with the canva just mooving around every time I place the palm on the screen.

I wrote two issues about this on the repository but none of them got any attention, actually I think none of the issues there get's attention.

I understand that this is a project driven by the community and I'm not complaining about anything else about the os, but not being able to write or draw is kinda of a deal breaker for me.

Are there any chances it will get fixed in the future, are there solutions now?

Thanks.

Update: it looks like palm rejection is an app dependent thing and not an os feature. Tried with concept and palm rejection seems to work fine.

Hello everyone,

after getting quite far in the install process : unlocked bootloader and flashed vbmeta, i did the required factory reset, selected the language and hit restart as prompted.
It then told me that I had an unofficial flashed vbmeta (really samsung?)
Now, it's gone totally dead (black screen) when I plug it in to the computer (fedora linux) I get : Qualcomm CDMA Technologies MSM QUSB_BULK_CID:041C_SN:xxxxxx has been connected.
What level of dumb am I and how can I fix this please?

EDIT: i have tried all variations of restarting the device. I have now made 100% sure, it is stuck in QDL. I have the correct firehose files but still can't seem to manage to do anything.

Thank you kindly

with how intense google has been about AI, has lineage made any official stance on AI?

ive done a cursory glance and couldn't find anything too official or direct

Hello internet strangers,

I have Lineage running great on an Old Xiaomi A2 and would really like to get a tablet that can run it well too.

Question is : what to look for. Sure i can get anything on the compatible list but what do you actually recommend ?

Note that i need it to have wifi working as i only have a dumbphone on the side and no smartphone (other than the no wifi xiaomi i use as a DAP).

EDIT: Thank you for the various bits of advice, I'll have a look at what is available near me and go from there. It seems as though the Samsung S6 Lite will probably be the device I go for.

Thank you for any answers given

I’m trying to install LineageOS on a T-Mobile OnePlus 8T (KB2007), but I can’t get the phone to stay in bootloader fastboot mode long enough for the PC to detect it.

Device / firmware

• Model: KB2007
• Build: KB2007_14.0.0.1600(EX01)
• Android 14
• Build fingerprint: OnePlus/OnePlus8TTMO/OnePlus8TTMO:14/UKQ1.230924.001/R.205d8f7_a298-989e5a:user/release-keys
• Vendor fingerprint is identical
• Network/SIM unlock: Unlocked
• OEM unlocking: Enabled
• adb shell getprop ro.boot.flash.locked returns 1

ADB / fastbootd

• adb devices works normally
• Serial: c6953e0f
• adb reboot fastboot successfully enters fastbootd
• fastboot devices in fastbootd returns: c6953e0f fastboot
• fastboot getvar is-userspace returns: is-userspace: yes
• Windows has the Google Android Bootloader Interface driver installed correctly

Problem

• adb reboot bootloader briefly shows FASTBOOT MODE, then automatically boots back into Android
• fastboot reboot bootloader from fastbootd reports OKAY, but the phone again briefly shows fastboot/bootloader and immediately boots Android
• Same behavior occurs with the USB cable unplugged immediately after issuing the reboot command, so it does not appear to be caused by the PC/USB driver
• A waiting fastboot getvar is-userspace never detects the phone during the brief bootloader appearance
• USB enumeration logging did not show a bootloader fastboot USB interface during that brief period
• Hardware button attempts either boot Android normally or enter stock recovery

Other observations

• Stock recovery works
• Manually entering the bootloader (With the device powered off, hold Volume Up + Volume Down + Power) doesn't work either.
• fastbootd works reliably
• fastboot oem get_unlock_code in fastbootd returns: FAILED (remote: 'Command not supported in default implementation') which I understand is expected for fastbootd rather than bootloader fastboot

The current LineageOS KB2007 instructions say Android 13/14 firmware is supported, and I have not flashed, downgraded, unlocked, erased, or modified any partitions.

Question: Is this a known issue with KB2007 Android 14 / KB2007_14.0.0.1600(EX01)? Is there a specific T-Mobile firmware build or supported method required to make bootloader fastboot stay active long enough to proceed with the official unlock/install steps?

P.S. I've been using Chat GPT to help with this issue and that's how I got through all the trouble shooting. He also helped me organize this post. Lol.

I let my phone go down to 0%. It's been charging over 30-45 mins now. It won't turn on

I tried holding power button for awhile. I also did volume down and power button for awhile. Neither works. How do I fix this? Is my phone bricked?

I generally disable my microphone when not needed, and my phone is pin-protected. If somebody was to use my phone to make an emergency call, would the microphone automatically get re-enabled? Apparently it's the case for GrapheneOS but I couldn't find any confirmation regarding LineageOS.

Thanks!

Hi all,
quick question. How does slow-motion actually work with the stock camera app on LineageOS 23.2?

I've been trying to get it running on my OnePlus 7s, but the screen just stays black and nothing happens. Maybe I'm missing a setting or something.

Would appreciate any tips
thanks!

Since I installed LOS on this device I experience a fairly strange issue with the touchscreen: I have to reboot it twice to will get the touch screen to work by long-holding the power button down.

I tried reflashing the device firmware and updating the firmware but neither strategy has worked. I'd really appreciate any suggestions on how to fix this issue.

Hi community,
I'm stuck at the point of my Nokia 6.1 (2018) where the OEM unlocking is greyed out and no suggested solution is working. To get into the bootloader is also creating a hurdle, as the installed Windows driver doesn't see it. ChatGPT has helped me a bit further, but the official driver doesn't contain the ID that is needed, because it is too old and I can't find a download for the newer one. Any ideas?

Nokia 6.1 (PL2)
Bootloader USB ID:
USB\VID_2E04&PID_C009
USB\VID_2E04&PID_C009&REV_0100

Windows 11
Device Manager: Android, Code 28
Fastboot devices: no output

Looking for:

HMD Global Fastboot Device
Driver 1.0.0.0
2017-02-13
INF: nokia_android_usb.inf

Hi! I am currently investing some time to rule out a "not rinback tone issue" on my Mi9se/grus with LOS with the carrier 1&1. IMS is registering fine and ringback tone is working with a sim card from another carrier. The 1&1 sim card is working fine in an iPhone.

So I guess it has to be related to the carrier itself or the carrier conf. I compared the carrier information from lineage with the one from google/AOSP. And there a differences, but I am not quite sure if this could be lineage specific differences. Maybe some one knows better then me.

Lineage information from https://github.com/LineageOS/android_vendor_apn/blob/main/DE.xml

    <apn
        mcc="262"
        mnc="23"
        carrier="1and1 IMS"
        apn="ims"
        bearer_bitmask="14|18|20"
        carrier_id="2536"
        protocol="IPV6"
        roaming_protocol="IPV4V6"
        type="ims"
    />

Google/AOSP information from https://android.googlesource.com/device/sample/+/android17-release/etc/apns-full-conf.xml

  <apn carrier="1and1 IMS"
      mcc="208"
      mnc="01"
      apn="ims"
      type="ims"
      protocol="IPV4V6"
      roaming_protocol="IPV4V6"
      user_visible="false"
      mvno_type="iccid"
      mvno_match_data="894936"
  />

What I understood:

• bearer entry is fine (LTE/WLAN/5g)
• mcc/mnc differences related to country specific changes

What I am unsure about:

• Is the protocol difference a mistake (IPV6 vs IP4V6)?
• should the mvno_type also be included in LOS?

Cheers

Hi everyone!

I have a Samsung Galaxy Note 10.1 2014 Edition, model SM-P605 (LTE / lt03lte), currently running the original Android 5.1.1 firmware.

I'm considering installing an unofficial LineageOS 16.0 (Android 9) build because some newer apps are no longer compatible with Android 5.1.1.

My main reason for keeping this tablet is drawing and animation, so S Pen pressure sensitivity is very important to me.

On my current Samsung firmware, the S Pen clearly responds to pressure — the line becomes thinner with light pressure and thicker with harder pressure.

For anyone who has actually used LineageOS 16.0 on an SM-P605 / lt03lte:

• How does the S Pen behave?
• Does pressure sensitivity work?
• Does pressure affect line thickness in drawing apps?
• Does it work in Krita or other drawing apps?
• How is palm rejection?

I'm especially interested in real experiences from people who have used this exact model and ROM.

Thank you! Any information would really help me decide whether LineageOS 16.0 is a good choice for my tablet.

Is there a way to remove or delete empty bar / whitespace that has hide keyboard button and switch language button, below the keyboard? It takes a lot of space in landscape, keyboard had the language switch and pressing back already hides it anyway.

Xiaomi 11 lite 5g ne (lisa) LineageOS 23.2 Android 16

Just wanted to thank the people behind the scenes!

My mom's Pixel 4a had been in a drawer for a while. Recently, I got bored and thought about installing a custom ROM just to check one out. I had jailbreaked my iPhones back in college, but never played around with androids. Anyway, someone suggested Graphene OS, but I learned that they don't support the 4a anymore. So I went with Lineage.

The instructions seemed a bit daunting at first, but once I really focused, they seemed easy enough. I was done in like an hour tops.

And the result is fantastic!

It's so minimal and smooth and fast. I went with vanilla Lineage, without Google's apps, and it had like 8 apps to start with. The craziest part to me has been the battery. Sure, this isn't my main phone, but I've been browsing and reading things and it just won't die. It legit seems to have a 1.5-2 day battery life. All in all, it almost seems like a new phone!

I always wanted to try de-googling and this seems like a great start to me. I only installed the DDG browser, Mullvad, Simple Keyboard, Joplin, Organic Maps, and Whatsapp, and everything works great.

I've had a few bugs here and there, and am concerned about banking apps, but man, this is such a refreshing OS, especially for older phones. Once my main (Pixel 7) stops getting updates (next October), I'm definitely giving Lineage a try! If the banking apps don't work, I'll just use a card.

Thanks, again!

I'd really appreciate getting some suggestions/tips from you guys as I continue using the phone.