I have a rooted OnePlus 2 running LineageOS 14 latest. How can I enable the Do Not Disturb feature for just my personal SIM card, without also enabling it for my work SIM card? Specifically, I'd like to be able to have my personal SIM on Priority mode, if possible, which allows starred/favourited contacts to still ring. I plan to upgrade to LineageOS 15 soon, but I can do this right away if it is a prerequisite.

I am using Lineageos 17.1 on the FP3 (the phone is not rooted). I do know my screen pattern code (it is a 6x6 pattern), but I am not able to enter it correctly, because I disabled that the pattern is shown and that the sequence is visible. In the recovery mode I can enable adb and I tried to delete the file adb shell rm /data/system/gesture.key which worked in the past, but now this file does not exist anymore on Lineageos 17.1. ADB unfortunately does not work when the screen is locked. Is there another way to bypass the screen pattern? Doing a factory reset is the last option I want to do. Making the pattern visible should be enough in principle.

Moto G7 power, LineageOS 22.2 In the APN edition config page, there is a list of APN. The first 14 are selectable (radio button on the right). Some can be edited, some can't. The 13 below are not selectable (no radio button), all are editable. All 27 have a toggle button at the bottom to activate/deactivate. The button is greyed out in what seems to be the activate position. Questions : - How come all APN are not selectable? - How come some are not editable? I understand default ones can't be edited but I didn't add all the editable ones. - My carrier says two APN should be configured: internet and MMS. However, due to the radio button, I can only select one. Is this normal? I do have mobile data. MMS kinda work but not that good ([other question](https://android.stackexchange.com/questions/262105/)) . **Edit**: I switched to another APN (ACCESS DATA / websfr), the first of the list, not editable, and it seems everything works correctly. My questions about the APN config UI still stand. Details: - Country : France - Carriel : Prixtel/SFR - Help page : https://assistance.prixtel.com/questions/900239-configurer-internet-mms-smartphone

When I send a picture via MMS, it sometimes gets stuck sending until it times out. This may not be a surprise if the picture is a bit large. Until the timeout, I can't even send any SMS, the whole queue is stuck. As a user, I probably shouldn't be sending huge files by MMS, but that's how it is. Besides, it sometimes work. Overall, pretty bad user experience. Any idea how to address this and who to blame? Should it work in the first place and this is a MMS issue? What size should be considered too large? Should the SMS/MMS app attempt to resize pictures or warn when the file is larger than a given size? Should the SMS/MMS app at least provide a cancel button to avoid having to wait the whole timeout (maybe 30 minutes, I don't know exactly)? Should the gallery app resize the picture before sharing by MMS? LineageOS 22.2 / Android 15 ----------------------------------------------------------- **Edit** It seems the problem is not related to the picture size. The same happened with a simple SMS with a smiley (is this sent as SMS or MMS ?). The message wouldn't send. It even blocked sending another SMS. I switched off the wifi and the messages were sent. It appears when on wifi, the phone switches to 2G or perhaps no data at all and MMS don't get sent. I just tested and couldn't reproduce, though (I could send a smiley to myself with the wifi on), so it might be a little bit more complicated than this. Is there a setting to let the phone switch to 3G/4G while sending MMS even when on wifi?

I have a Samsung Galaxy Tab S2 stuck on Android 5.0.2. I wanted to upgrade the software to LineageOS. There is a lot of information out there, but nothing that can help me. A few things first that I need to share. I'm using a Mac. I once unlocked my device and Knox is now void, so it must be unlocked. I can't tell if the bootloader is unlocked. I tried to check using an app, but came back with an error of "Sorry! root access is not properly installed on this device". The tablet is in developer mode, there is no OEM mode or anything like that, and USB debugging is turned on. I have tried several things using Terminal but they didn't work with homebrew and ADB services. These are installed on my Mac. I got as far as trying to add fastboot devices, and it was denied on the terminal, but that probably makes sense if the bootloader is locked. Most instructions imply that you know what to do and don't explain much. Can anyone please assist with step-by-step instructions so I can complete the process of installing LineageOS?

I’m using a variant of LineageOS, and I keep my phone in silent mode almost all the time because I don’t like ringing phones. For work reasons, I need certain contacts to be able to bypass silent mode so that their calls actually ring (so I don’t miss them). I know that Android’s *Do Not Disturb* mode allows exceptions, and if I enable DnD, it works — but I avoid DnD because it also blocks all other notifications and vibrations, which I still want to receive. **My question:** - Is there a way to make the phone behave like silent mode (still vibrate and show all notifications) while letting selected contacts ring through? - Alternatively, is there a way to bypass silent mode for specific contacts without using DnD? I’m surprised this isn’t simpler, since it seems like something many people would want to do.

I have galaxy J7 and lineageOS 17.1. When I send a file with KDE connect from my phone to another device (another phone or a laptop) I am successfull, but in reverse not. For example when I try to send a file with KDE connect from my laptop to my phone a notification appears saying "failed receiving file from ...".

This is not duplicate of other questions. I've been struggling with this issue for last 3 weeks and have contacted Google over chat, forums and other avenues too without any luck. I moved from USA to India and now some of the apps can't be downloaded due to payments profile being in USA with an active Google Domains subscription. So far I've tried following steps - - Went to payments.google.com and created another profile with India as country. Now I can see two payment profiles as USA and India. - Added credit cards etc so that it's a valid one - Went to Apps > Play Store and cleared cache and data. Removed my google account and restarted my phone to add Google account again. - Can't delete my cc info from USA payments profile due to active Google Domains subscription. Tried cancelling it, but it takes me to Domains billing page which again asks me to go back to payments page to cancel. So kind of catch 22 situation here. - Unless I cancel Google Domains subscription, can't close my USA payments profile. - Went to Google play to purchase something and it doesn't allow me to buy anything with India card, so other solution to at least reach 'Accept & Buy' stage can't be done. I'm stuck with USA google play store now and would appreciate any help to change country so as to get to useful apps.

When iOS support ends for my iPhone, I would like to replace it with a Pixel phone and go with GrapheneOS. But I am wondering: (How) can I transfer my contacts, photos etc.? (without proprietary cloud solutions) It looks like there's the possibility to [transfer those data by Lightning2USB-C cable](https://support.google.com/pixelphone/answer/7129740?hl=en#zippy=%2Ccopy-data-from-your-old-phone-with-a-cable-recommended) . But this only works on StockROM and LineageOS, right? Not on GrapheneOS!? My idea was to buy the phone, flash Lineage (with GApps) on it, transfer the data from my iPhone, perform a SeedVault backup on an external drive, flash GrapheneOS and restore that backup on the device. Would this work? Has anyone tried? My two main uncertainties: 1. Does the cable transfer from iOS work with LineageOS? 1. Does restoring SeedVault backup between ROMs (Lineage, Calyx, Graphene etc.) work?

I am trying to install latest Lineageos for mata on Essential ph-1. It is stuck at fastboot flash boot boot.img with the warning about avb, boot partition size of 0. Boot image size: 33673216 and fastboot getvar partition-size:boot returns partition-size:boot: 0201d000. The boot image is larger than the partition. The boot image (33673216 bytes) is larger than the reported boot partition size (33671168 bytes, which appears as '0' in the fastboot warning due to an error). How do I fix this and get lineage OS installed on Essential ph-1?

The menu appears to have been hidden on the more recent Android releases — currently on Android 14 the only per-app toggle the users are given is 'allow background usage' (app info → app battery usage). On my Oneplus 8T device the OS is actively stopping some apps designed to be running on the background at all times, such as Shizuku . On AOSP-based ROMs three settings used to be available for each app, the most permissive being 'unrestricted'. SystemUI Tuner didn't expose the menu. --- Using ADB is an acceptable answer as well.

Android can install to an A or a B partition. This seems to be a default these days. How can I tell which one I am booted into using adb? I am using LineageOS 17.1.

I have a backup of my old phone I can see in my Google Drive app on my new phone. How do I backup/restore all the apps from this backup? From searching, it looks like this should have been an option when first starting my phone but it wasn't. Android version: 7.1.2 LineageOS version: 14.1

I have a OnePlus 7 Pro. I had LineageOS 17 (Android 10) with microG, magisk, and vanced on it running just fine for almost a year. I upgraded the Android version to 11 first (which LineageOS documentation says is a pre-requirement) then I upgraded to LineageOS 18, and everything seemed to work just fine. I can confirm that my recovery and wifi worked. A few days later I wanted to open Vanced YT, but it was no longer installed, then I noticed that magisk was no longer installed. So I installed it according to it's instructions which was basically using the app to patch the boot.img I got from the extracted files (from a payload-dumper) and then installed the produced magisk_patched-24200_Y0Qmv.img. Ever since then is my problem. I can no longer turn on my wifi, I no longer have recovery mode, and every time I turn on/reboot the device I am greeted with a "System UI Crashed" error message. I can hit ok and everything else seems to work as expected. With the exception to my wifi not being able to turn on What I've tried: - re-flashed the original boot.img - re-flashed the recovery image - uninstalled magisk - I tried re-flashing other images from the payload dump (modem.img, etc) the same way the LineageOS documentation said to upgrade and I get the following error

fastboot flash --slot=all modem modem.img
fastboot: error: Could not check if partition modem has slot all

I have no idea what that error means. Nothing changed. I'm still greeted with the same crash message. I still can't turn on my wifi. And I still can't boot into recovery mode. To make sure I'm clear, my question is; "Where should I go from here? What things can I tell you in order to help me get my wifi working again, and to fix this 'System UI Crashed' error message?"

I rooted my Lineage OS 14.1 but none of my apps ask for root permissions. I followed the instructions of this link and the root access option in my phone is "apps and adb". Do I miss something? I have a Moto G4 Plus and I've already tested Sixaxis and ES File Manager, none of them ask for root permissions.

I have a full phone backup of a LineageOS 21 (Android 14) install containing all partitions copied to my Linux PC. I can mount several partitions, such as /system. However, the /data partition /dev/block/sda19 is of course encrypted. I have the full phone backup. I know my Android PIN. How do I manually decrypt and mount the /data partition?

I encoded a part of a song as MP3 and I'd like to set it as ringtone on LineageOS 14. I found some instructions to move the file to a certain location - or better locations because the locations because they seem to differ based on model and version. However, it's 2018 and developers are usually educated in basic UX, so there's probably an acceptable way to do this (assuming that it's not acceptable to force a user to speculate that a configuration option might be available after moving a file to a certain unspecified location in the context of a GUI - [forum threads like this one of a German LineageOS forum not based on meritocratic swarm intelligence suggest five contradictory approaches](https://www.lineage-os-forum.de/Thread-CM-MP3-als-Klingelton)) . I'm using LineageOS 14.1 on a Moto G 2014.

## Situation I have an old phone, it's been replaced, but it still has some photos on I want to recover. From the symptoms I presume it must be a hardware fault, and I am wondering what options are available to me. I have a friend who works as an embedded engineer who is willing to help me try get the photos off of it. The current possibilities they could think of are: - Buy a cheap new screen to connect to the phone to see if we can get the UI back - Attempt to connect via the JTAG pins and execute a script to extract the data Are there other options? Or should we go with one of these? ## More information If it's relevant, the phone is a Pixel XL. A possible silver lining is I was running LineageOS, so I unlocked the bootloader and was never able to re-lock it. The symptoms at the time of death were: - Phone would randomly restart every few weeks - This got more and more frequent - One day the phone restarted and never turned back on - If I held the power button to turn it back on, the phone vibrated yet the screen never turned on - When plugged in the red light didn't appear even though it was drawing Watts - Forced resets (holding power and volume down button for 30+ seconds) sometimes caused a vibration but nothing ever appeared - Plugging it into a laptop resulted in no devices being visible to the laptop (presumably I needed to enable file transfer via the UI which wasn't possible) It's since sat in a box for 2 years and now there is no vibration whatsoever, but it does still draw current when charging. (I contacted multiple places about data recovery in the last couple of years but never received a response.)

On my Nexus 5 (LineageOS 15.1 / Android 8.1), I can't see my device when typing adb devices (Manjaro with Android SDK 3.2.1). What I tried: 1. Root access: "ADB only" 2. Android debugging: "on" 3. Revoked USB authorizations 4. USB configuration: "MIDI"/"AUDIO"/"Charging"/"MTP"/"PTP" (tried each) 5. Restarted the device, and also connected after restarting 6. Changed USB Cable 7. Inserted udev rules (like on Arch Wiki ) 8. All of this in a root shell lsusb is not listing the device if I have Android debugging on. If it's off, I see it. (As soon as I switch it on, it disappears.) I don't have Windows at the time, so would this help? **What can I try next?** My goal was to install Ubuntu Touch in dual-boot mode.

Recently I found my old Samsung S8 (SM-G950F) with a broken display. I ordered a replacement part, and it turned out to be an LCD screen, which was different from the original OLED display. Upon changing the screen, the phone enabled it. The backlight and touch screen are working, but the display is not showing anything. I can successfully connect to an external display with USB-C -> HDMI adapter, but the new screen is blank. I tried flashing the OS to "LineageOS 20" hoping to resolve potential driver issues but with no luck. Is there any firmware or particular driver that could help? Anyone had a similar issue? The exact LCD model no: AMB577MQ01 REV 7.2 BH1740 2 YX