I use battery saver all-day and I ddon't want dark-mode in day so I want to use battery saver without dark-mode. What stuff sshould I do? (I have ROOT). I can also use Termux if needed to change system files with root.

Sir I Have I installed lineage os 21 android 14 in my samsung a73 5g but my IMS Service is not Working Can you please Help me and that's the reason I need to go back to my stock rom overall lineage is great and best OS

After reading all reddit post and scouring pages on Internet, I finally made the jump and Installed LineageOS on my Oneplus 8. I knew that moving to LineageOS will leave my device uncertified by playstore due to SafetyNet and play integrity issue.
TBH, I am happy that my phone feels snappier, clean, lag free and longer lasting than OxygenOS. It feels like a brand-new phone to be honest, maybe even better.
After couple days of use, I am feeling the pain of not having Google Wallet and many other apps not working due to SafetyNet issue and unlocked bootloader. I have been trying to find a solution out there in wild but cannot seem to find one that works. Is there a solution for Safetynet fix and get GPay working and other apps working again. TIA

Following the official LineageOS guidelines, I successfully compiled lineage sdk_phone_x86_64 on Ubuntu and managed to boot the system using the emulator. Using adb, I checked that the current kernel version running on the emulator is 6.6.9-android15-0-g515a956763d8-ab11275718.

6.6.9-android15-0-g515a956763d8-ab11275718

I then downloaded the kernel source from AOSP, version common-android15-6.6, and compiled it using bazel, which was successful. However, when I tried to launch the emulator with the custom kernel, the emulator failed to start, although it did not report any significant errors.

I would like to ask: is this issue due to kernel version incompatibility, or could there be an error in my process?

Phone: Xiaomi Redmi Note 9

System version: LOS20-20241105-NIGHTLY-merlinx (but it happens since I first installed LOS, so at least August)

My phone is rooted, but the exact same problem was present while not rooted.

For some reason, my phone doesn't detect Bluetooth keyboards (tried with two different brands). To be precise, when I enable Bluetooth and tap "Pair a new device", the keyboards simply never show up as an available device.

It properly detects, connects and works with any other Bluetooth devices. The keyboards worked on this phone with MIUI 12.5 (A11), they are also properly detected by a Lenovo tablet with A14.

One of the keyboards can also connect through WiFi and this method works with no problems whatsoever, but I'm still curious if it's possible to find a reason for this behavior.

Thanks for any suggestions!

And if so, how do I do it in lineage please? I can't seem to find it. I read somewhere that you can.

Fairphone 4.

Thanks.

PLEASE PLEASE NEED help to install lineage os on my pro1x phone

So, there is one good thing on stock OOS that I actually love, and that's the "Games" app. It makes your notifications unobtrusive (transparent and such), locks the brightness without turning off auto brightness at a system level, and has Discord and Spotify access from its little drop down that doesn't interrupt my games by making me switch apps. And a few other nifty little things.

I was running CarbonROM for a while, and nothing I tried would make it work right at all. And that's even if I got the actual OnePlus one installed.

Has anyone on Lineage tried this at all? It's the only thing that makes me use stock right now.

I've been running LOS on a Xiaomi Mi Mix 2S for for several years, upgrading through several major versions and many minor ones. Recently, the latest upgrades failed to install, displaying several lines of cryptic error messages. I searched the LOS issue tracker, and found several reports of identical or similar problems with other devices: here, here, and here. Various comments in those discussions indicated that the problem is that recent LOS builds require an updated recovery, and sure enough, updating the recovery solved the problem.

My questions:

• The LOS wiki states: "Please do not ... Comment your device as affected on a report for a different device - different devices have different maintainers, and different reasons for bugs to exist." Does that mean that I should file a bug report against my device?

• The upgrade instructions for my device do not mention this problem or solution. Should I file an infrastructure bug about this?

I want to know if I install the ROM with Android 13, will Warzone run normally because it requires Android 13 or higher? My phone not support the game because is android 12 this link for not supported devices https://support.activision.com/servlet/servlet.FileDownload?file=00PKe000001vv0a My hardware is enough to run the game. The problem in software miui 14 just android 12 I need 13 I have all the hardware requirements to run it, the only problem is with Android

LineageOS, support APK's and Normal Android Apps? I know it's a stupid question, but it feels like trying to use a Linux app on FreeBSD or another Unix. Are normal Android apps compatible with LineageOS? Can I install an APK normally? and either directly or something like F-Droid

This is my first attempt at installing a custom ROM on a phone. I have a Moto X4 and was following the instructions to install the latest LineageOS using a Linux PC. Are the builds supposed to be located in a particular directory on my Linux (Mint) machine? I have adb and fastboot on my machine. Thanks.

Is there a lineage os rom for honor 10 lite

I've flawlessly been running beyond0lte on a s10e for years. Bought a used device for a friend and LTE connection randomly turns off (roughly once per week). Only restarting solves the issue.

Ring any bells?

I am attempting to build the complete AOSP with Android 14 (revision 27) and Linux kernel version 5.10.107, and I am encountering an issue where the Zygote process is crashing during startup.

The key details are:

The build process gets stuck in the Zygote process, specifically in the Android runtime initialization.
The crash is caused by a failure to initialize the java.net.Inet6Address class, resulting in an ArrayIndexOutOfBoundsException and an ExceptionInInitializerError.
This causes the Zygote process to abort and restart repeatedly, preventing the build from completing successfully.

Ensured I'm using the latest available version of the AOSP source code.
Attempted to build with different Linux kernel versions, such as 6.1.95 and 5.15.x, but the issue persists.
Searched the AOSP issue tracker and forums for any known problems related to Inet6Address initialization on Android 14, but did not find any relevant information.

This issue is blocking my ability to successfully build and test the AOSP on the target platform. Any assistance in identifying the root cause and a potential solution would be greatly appreciated.
Steps to Reproduce:

Download the AOSP source code for Android 14 (revision 27)
Build the AOSP using Linux kernel version 5.10.107
Observe the Zygote process crashing during runtime initialization due to the Inet6Address issue

Environment:
AOSP version: Android 14 (revision 27)
Linux kernel version: 5.10.107
Build platform: [QEMU-based ARM Cortex-A53/A72/A720/A710 emulator]

Please let me know if you need any additional information or have any suggestions on how I can further investigate and resolve this issue.

01-01 00:00:05.608   514   514 W zygote64: Ljava/net/Inet6Address; failed initialization: java.lang.ArrayIndexOutOfBoundsException: failed FILL_ARRAY_DATA; length=0, index=16
01-01 00:00:05.608   514   514 W zygote64: (Throwable with no stack trace)
01-01 00:00:05.612   514   514 F zygote64: thread.cc:2517] No pending exception expected: java.lang.ExceptionInInitializerError:
01-01 00:00:05.612   514   514 F zygote64: thread.cc:2517] (Throwable with no stack trace)
01-01 00:00:05.612   514   514 F zygote64: thread.cc:2517]

Revision: '0'
ABI: 'arm64'
Timestamp: 1970-01-01 00:00:07.559970800+0000
Process uptime: 1s
Cmdline: zygote64
pid: 531, tid: 531, name: main  >>> zygote64 <<<
uid: 0
tagged_addr_ctrl: 0000000000000001 (PR_TAGGED_ADDR_ENABLE)
signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
Abort message: 'No pending exception expected: java.lang.ExceptionInInitializerError:
(Throwable with no stack trace)'
    x0  0000000000000000  x1  0000000000000213  x2  0000000000000006  x3  0000007ff5f25240
    x4  6f646277641f666d  x5  6f646277641f666d  x6  6f646277641f666d  x7  7f7f7f7f7f7f7f7f
    x8  00000000000000f0  x9  0000006fd669e090  x10 0000000000000001  x11 0000006fd66e4058
    x12 0000000000003d96  x13 0000000000000098  x14 0000007ff5f24040  x15 0000000000000000
    x16 0000006fd6748d08  x17 0000006fd6725e90  x18 0000006ff19dc000  x19 0000000000000213
    x20 0000000000000213  x21 00000000ffffffff  x22 0000000000000002  x23 0000006d328bc184
    x24 0000006d328c8e3a  x25 0000006d328a96d4  x26 000000005a000000  x27 0000006ff0980000
    x28 0000006ff0980000  x29 0000007ff5f252c0
    lr  0000006fd66d59b8  sp  0000007ff5f25220  pc  0000006fd66d59e4  pst 0000000000000000

18 total frames
backtrace:
      #00 pc 00000000000599e4  /apex/com.android.runtime/lib64/bionic/libc.so (abort+164) (BuildId: c74277f481a383c87215b672f6465e24)
      #01 pc 00000000006230fc  /apex/com.android.art/lib64/libart.so (art::Runtime::Abort(char const*)+1472) (BuildId: 55b9536b61b755b7bae82e95aa498dab)
      #02 pc 00000000000357d0  /apex/com.android.art/lib64/libbase.so (android::base::SetAborter(std::__1::function<void (char const*)>&&)::$_0::__invoke(char const*)+80) (BuildId: 6f67f69ff36b970d0b831cfdab3b578d)
      #03 pc 0000000000034d58  /apex/com.android.art/lib64/libbase.so (android::base::LogMessage::~LogMessage()+352) (BuildId: 6f67f69ff36b970d0b831cfdab3b578d)
      #04 pc 000000000067c790  /apex/com.android.art/lib64/libart.so (art::Thread::AssertNoPendingException() const+1564) (BuildId: 55b9536b61b755b7bae82e95aa498dab)
      #05 pc 000000000027a380  /apex/com.android.art/lib64/libart.so (art::ClassLinker::FindClass(art::Thread*, char const*, art::Handle<art::mirror::ClassLoader>)+64) (BuildId: 55b9536b61b755b7bae82e95aa498dab)
      #06 pc 00000000004b859c  /apex/com.android.art/lib64/libart.so (art::JNI<true>::FindClass(_JNIEnv*, char const*)+1156) (BuildId: 55b9536b61b755b7bae82e95aa498dab)
      #07 pc 000000000002d124  /apex/com.android.art/lib64/libopenjdk.so (register_java_net_Inet4Address+32) (BuildId: fc4c0ac2dde70b1afe348b962a85a634)
      #08 pc 0000000000030ae4  /apex/com.android.art/lib64/libopenjdk.so (JNI_OnLoad+452) (BuildId: fc4c0ac2dde70b1afe348b962a85a634)
      #09 pc 000000000044b270  /apex/com.android.art/lib64/libart.so (art::JavaVMExt::LoadNativeLibrary(_JNIEnv*, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, _jobject*, _jclass*, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >*)+3196) (BuildId: 55b9536b61b755b7bae82e95aa498dab)
      #10 pc 000000000062ddcc  /apex/com.android.art/lib64/libart.so (art::Runtime::InitNativeMethods()+1824) (BuildId: 55b9536b61b755b7bae82e95aa498dab)
      #11 pc 000000000062b904  /apex/com.android.art/lib64/libart.so (art::Runtime::Start()+372) (BuildId: 55b9536b61b755b7bae82e95aa498dab)
      #12 pc 000000000044dacc  /apex/com.android.art/lib64/libart.so (JNI_CreateJavaVM+696) (BuildId: 55b9536b61b755b7bae82e95aa498dab)
      #13 pc 00000000002181d0  /system/lib64/libandroid_runtime.so (JNI_CreateJavaVM+68) (BuildId: fdeaf5903aa89939955ff8f6c3171c86)
      #14 pc 00000000000e5f4c  /system/lib64/libandroid_runtime.so (android::AndroidRuntime::startVm(_JavaVM**, _JNIEnv**, bool, bool)+9500) (BuildId: fdeaf5903aa89939955ff8f6c3171c86)
      #15 pc 00000000000e6650  /system/lib64/libandroid_runtime.so (android::AndroidRuntime::start(char const*, android::Vector<android::String8> const&, bool)+468) (BuildId: fdeaf5903aa89939955ff8f6c3171c86)
      #16 pc 000000000000252c  /system/bin/app_process64 (main+1240) (BuildId: 7e05d205b18a0fc3f7544b2773370e07)
      #17 pc 0000000000052610  /apex/com.android.runtime/lib64/bionic/libc.so (__libc_init+104) (BuildId: c74277f481a383c87215b672f6465e24)

Good afternoon all, I am running LineageOS on my Pixel 7 Pro for a year already and I'm very happy with it. I decided today that I was going to replace my physical SIM card with an eSIM, and thus have 2 active eSIM's. However, it does not let me have 2 eSIM's active at the same time. Even though I read that MEP (multiple enabled profiles) is supported since the Pixel 7 and beyond and android 13 and beyond. Is there a setting I'm missing, or is it outright just not supported by LineageOS?

Pixel 3. Official build of LOS.

The battery in this thing is original, so it's rather... spent. It's my secondary device that I'll use while lying in bed or something. It spends most of its time facedown on my nightstand. I don't have a sim card in it, and haven't for years.

I keep it face down so the aod doesn't drain the battery. But I've noticed that no matter what, the battery still seems to drain like mad when I'm not using it. I figured it was just an old battery being old, but upon checking the usage stats, the mobile network was taking a lot of juice. On a hunch, I turned on airplane mode (and reenabled Wi-Fi and Bluetooth).

Zero battery drain today. None.

It appears that even though there isn't a sim card, it's still doing something that's using quite a lot of power related to the mobile network, and it definitely shouldn't.

I’m looking for some guidance on which version of LineageOS (or another custom ROM) would be best suited for my Airtel Xstream Smart Set-Top Box. For context, the Airtel Xstream is an Android-based set-top box from Airtel, one of the largest telecom providers in India. It allows users to stream content, run apps, and access OTT services like Netflix, Amazon Prime, and more, all on their TV, and it runs on android os 13. I’ve seen mentions of LineageOS for Android TV, but I’m not sure if it's compatible with my specific model. Any tips, suggestions, or guidance on whether this ROM or something else could work would be really helpful.

Thanks in advance!

Flashing redmi note 9 pro global.Firmware is is 14.0.5.0(sjzeuxm).Linageos states it requires 14.0.3.0(SJZMIXM).

Should i downgrade to flash Lineage OS?

I'm on a Pixel 7 running the official Lineage build with MicroG installed through F-Droid (which to my understanding is fine to ask about on this forum since it wasn't flashed from the boot-loader. If I'm wrong, let me know and I'll delete the post). Aurora store wants to update a few apps and I don't know if they are part of android and OK to update or if they are part of the spoofing MicroG does (causing Aurora store to misidentify) and should blacklist these updates in Aurora. The apps are:

• Android System Intelligence
• Pixel Camera Services
• Private Compute Services

Previously flashed Openplus 6 with no issues, but stuck with this one.

It's stuck at Sending recovery. Sits that way for hours and nothing happens.

There is also this message:

Warning: skip copying recovery image avb footer (recovery partition size: 0, recovery image size: 37201196).

Could someone please help? Thank you.

I just do an ota update and Google service is not working anymore. So, i just want to completely remove it and get mindthegapps which is also recommended by LOS anyway (I am a noob with these things)

after the update lineage-21.0-20241029-nightly-haydn-signed.zip google pay saying custom rom installed cant use google pay but phonepe and other banking apps working fine

Mi Unlock says "The place where the account is registered does not match the place where the phone is sold" and fails.

Anyone solved this?

I bought the phone on a uk ebay account but i am not living in the UK and it was shiped to my home adress. Could the place where the phone is sold be the uk? I have not tried to register a mi account in the uk.

I'm using a Motorola moto g 5G with LineageOS 21-20241103-NIGHTLY-kiev.

I've noticed that unlike previous major LineageOS versions, WebRTC audio doesn't appear to work reliably for me in the base system (SystemWebView) anymore, but I don't know if it's only broken for me, or for other people using the same/different devices as well.

WebRTC audio can be used by Android apps (e.g. SimpleX Chat) or websites like Jitsi Meet.

If you go to Jitsi Meet in Chrome/Chromium, press 'Start Meeting' and 'Join in browser', does the microphone symbol stay active or does it immediately return to 'You need to enable microphone and camera access' with a line through the microphone? (Yes, I enabled access to camera and microphone for both the website and my browsers. WebRTC audio also doesn't work in the SimpleX app anymore.)

Does Jitsi work for you in Chrome/Chromium? What device/LineageOS version do you use? Firefox seems to use different codecs and works around the issue - but that doesn't help when other apps still seem to make use of the SystemWebView from LineageOS.

adb logcat '*:V' | grep -i audio returns format errors such as:

11-05 07:33:44.426  1363  1363 D APM_AudioPolicyManager: checkAndSetVolume if deviceTypes is change from none to device 0x4, need get index 5
11-05 07:33:44.434  1261  2374 E audio_hw_primary: check_input_parameters: unsupported AUDIO FORMAT (5) 
11-05 07:33:44.435  1261  2374 E audio_hw_primary: check_input_parameters: unsupported AUDIO FORMAT (5) 
11-05 07:33:44.435  1363 27132 W APM_AudioPolicyManager: getInputForAttr() failed opening input: sampling rate 48000, format 0x5, channel mask 0x10
11-05 07:33:44.435  1363 27132 E AudioFlinger: createRecord() getInputForAttr return error -38
11-05 07:33:44.436 29461 29528 E AudioRecord: createRecord_l(1): AudioFlinger could not create record track, status: -38
11-05 07:33:44.436 29461 29528 W AudioRecord: removeAudioDeviceCallback(1): removing different callback!
11-05 07:33:44.437 29461 29528 D AAudioStream: setState(s#9) from 0 to 11
11-05 07:33:44.437 29461 29528 D AAudioStream: setState(s#9) from 11 to 12
11-05 07:33:44.437 29461 29528 E AudioStreamRecord: open(), initCheck() returned -38
11-05 07:33:44.437 29461 29528 D AAudioStream: ~AudioStream(s#9) mPlayerBase strongCount = 1
11-05 07:33:44.437 29461 29528 I AAudio  : AAudioStreamBuilder_openStream() returns -895 = AAUDIO_ERROR_INVALID_STATE for s#0 ----------------
11-05 07:33:44.466  1699  2609 W AS.AudioService: setLeAudioVolumeOnModeUpdate ignoring invalid device=2, mode=3, index=30 maxIndex=50 streamType=0
11-05 07:33:44.466  1699  2606 I AS.AudioDeviceBroker: setCommunicationRouteForClient for uid: 10221 device: null isPrivileged: false from API: clearCommunicationDevice() from u/pid:10221/29461
11-05 07:33:44.600  1261  2374 D audio_hw_primary: out_set_parameters: enter: usecase(1: low-latency-playback) kvpairs: routing=1
11-05 07:33:44.600  1261  2374 D audio_hw_primary: out_set_parameters: exit: code(0) takes 0.06 ms
11-05 07:33:44.606  1363 26286 D APM_AudioPolicyManager: checkAndSetVolume if deviceTypes is change from none to device 0x4, need get index 5

I had an ancient Galaxy S4 mini that I installed LineageOS on about 2 years ago. Worked great right up until a couple of days ago when the hardware finally quit. Thanks everyone that got me a ton of extra use out of a phone that would have been recycled a long time ago.

I'm currently trying to install LineageOS on my galaxy s9. I've made it to the point when you install the OS. The problem is that the ADB can't find the files needed. I have also scrolled through all files and it still can't find the files. Is there any solutions to this?

Mobile Phone Model: Pixel 6 Pro
Current LineageOS Version: 21.0
Last Installed Update: November 4th 2024

As the title says, I want to fix Google Play Services from crashing. How did it happen? An LOS OTA update got installed while Magisk, LSPosed, Zygisk, and other Sys-mods were already flashed. Update was installed and now i need to repair Google Play Services from constantly crashing every 10 seconds without losing the user data of mine.

Another thing the title mentions is that I am looking for alternatives of MindTheGapps. What kind? the most debloated ones - Ones with little to no software bundling and just straight up Core Google Services, stripped enough for no software, but enough to have google services running for banking software, Discord, Aurora and other Google Service dependent software to just work without any extra google bloatware.

Quick extra questions:
is it possible to backup the boot_a and boot_b partitions without the use of external device (like via a magisk addon - much like how TWRP can backup the boot partition just in case)?

How possible is it to go to Lineage Recovery and flash the file straight up? or is it not possible, given how it works and the device software structure?

Hi all - I recently had to let go of a pixel 8 so I'm back to Moto for a few weeks. I use LOS on my OP3T now and was wondering if anyone had personal experience, or vid review, of LOS 21 on this Motorola G Power 2021. Long shot, I know but thought I'd take it. Thanks for your time.