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

I'm trying to sideload a Magisk patched rom. It's failing. I would like to extract that log. Where is it stored?

I installed Lineage OS 16.0 on my Moto x4 using TWRP. I reboot and installed GApps. While installing there were no errors. But then after restart the Phone it stays in start sequence and after ca. 10 min it goes back to TWRP. When I only install Lineage OS it works fine, but without GApps. So I tried a few variations of combine these versions: TWRP: twrp-3.3.1-0-payton, twrp-3.3.0-1-payton Lineage OS: lineage-16.0-20200219-nightly-payton-signed, lineage-16.0-20200223-nightly-payton-signed GApps: open_gapps-arm64-9.0-pico-2020019, open_gapps-arm64-9.0-pico-2020028, open_gapps-arm64-9.0-pico-20191017 Can you please help me? Did someone know what I am missing or doing wrong? Edit: I found that I start in Slot A and installed Lineage there, but after reboot I am in Slot B but installing GApps works without shown error beside that main problem. When I go back to slot A and install GApps there it breaks with error code 64.

I'm running LineageOS 14 (Android 7) and my SD card was formatted as adoptable storage. I want to revert it to portable storage, without losing apps, so I need to move those apps back to internal storage beforehand. However I don't know which apps are stored on the SD card just now, and checking them manually, one after the other, using the Settings menu, is quite slow and error-prone. How do I get a list of apps that are stored on the SD card?

I have a OnePlus 6, running LineageOS 22.1 (Android 15). In December when I still was on LOS 21 (Android 14), out of nowhere my phone's camera & torch have stopped working. It just shows "Camera in use" message under the Torch button in the notification area, the LOS camera app just closes itself, or other apps display "can't open camera". I've revoked camera permissions to see if anything is using it, but no change. Initially after a few reboots the torch was working, but later on even that stopped working & after many reboots & upgrades I can't get that back to work either. LOS support said to flash back the original OxygenOS, but I don't want to do that, as it will log me out of loads of apps which don't survive TWRP/OrangeFox restore. So what I'm looking for is a way of confirming that the camera is physically broken, so to see I'd need to try to replace it (if possible, didn't look at it), or there's some software issue only (I don't want to open the phone if not necessary). Does anyone know a way to do that, eg. from a recovery/fastboot boot/ADB or anything else? Or is there a possibility to boot to OxygenOS without flashing it in? Thank you

I have a Redmi Note 4 (mido) Android phone with a broken screen: the screen lights up, but otherwise it stays entirely "black". I already replaced the screen, but with no luck - the cause of the error must be somewhere else. The phone has data-encryption enabled with an unlock-pattern. Now I'm trying to access the data on the phone, but did not succeed so far. Here is what I've done so far: - Connected the phone to a PC over USB. - Started the phone in fastboot-mode by pressing and holding the buttons vol-down and power simultaneously. - Booted the latest version of TWRP for mido : fastboot boot twrp-3.3.1-0-mido.img. - Opened adb shell and presumably managed to decrypt the data (found instructions in the TWRP Commandline Guide ): TWRP decrypt: ~ # twrp decrypt 41236 Attempting to decrypt data partition via command line. Data successfully decrypted, new block device: '/dev/block/dm-0' Updating partition details... ...done Unable to mount storage ~ # Unfortunately, the block device /dev/block/dm-0 cannot be mounted. This is the result of fdisk: ~ # fdisk -l /dev/block/dm-0 Disk /dev/block/dm-0: 57.0 GB, 57033580032 bytes 255 heads, 63 sectors/track, 6933 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk /dev/block/dm-0 doesn't contain a valid partition table So I pulled an Image of the block device with adb pull /dev/block/dm-0. This image has a size of 57,033,580,032 bytes. I tried to mount this image in Ubuntu 20.04, but did not succeed: # file /media/sf_U_DRIVE/Note4Data/dm-0.img /media/sf_U_DRIVE/Note4Data/dm-0.img: data # fdisk -l /media/sf_U_DRIVE/Note4Data/dm-0.img Disk /media/sf_U_DRIVE/Note4Data/dm-0.img: 53,12 GiB, 57033580032 bytes, 111393711 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes # mount -o loop /media/sf_U_DRIVE/Note4Data/dm-0.img /mnt/Note4Data mount: /mnt/Note4Data: wrong fs type, bad option, bad superblock on /dev/loop3, missing codepage or helper program, or other error. # mount -t ext4 -o loop /media/sf_U_DRIVE/Note4Data/dm-0.img /mnt/Note4Data [ 6986.649794] EXT4-fs (loop3): VFS: Can't find ext4 filesystem mount: /mnt/Note4Data: wrong fs type, bad option, bad superblock on /dev/loop3, missing codepage or helper program, or other error. # mount -t f2fs -o loop /media/sf_U_DRIVE/Note4Data/dm-0.img /mnt/Note4Data [ 7004.610412] F2FS-fs (loop3): Can't find valid F2FS filesystem in 1th superblock [ 7004.615289] F2FS-fs (loop3): Can't find valid F2FS filesystem in 2th superblock mount: /mnt/Note4Data: wrong fs type, bad option, bad superblock on /dev/loop3, missing codepage or helper program, or other error. I wonder if I need to mount the image in another way (with offsets? with LVM?) or if the decryption did not work. TWRP creates a log file in **/tmp/recovery.log**. After running the twrp decrypt command, the following lines are added: I:Command 'decrypt 41236' received I:Set page: 'singleaction_page' I:operation_start: 'TWRP CLI Command' Attempting to decrypt data partition via command line. D:crypt_ftr->fs_size = 111393711 I:starting verify_hw_fde_passwd I:Using scrypt with keymaster for cryptfs KDF I:TWRP keymaster max API: 3 I:Signing safely-padded objectkeymaster module name is Keymaster QTI HAL keymaster version is 256 Found keymaster1 module, using keymaster1 API. I:Extra parameters for dm_crypt: fde_enabled ice I:target_type = req-cryptI:real_blk_name = /dev/block/mmcblk0p49, extra_params = fde_enabled iceE:test mount returned 0 I:Found no matching fstab entry for uevent device '/devices/virtual/block/dm-0' - add I:Found no matching fstab entry for uevent device '/devices/virtual/block/dm-0' - change Data successfully decrypted, new block device: '/dev/block/dm-0' I:Can't probe device /dev/block/dm-0 I:Unable to mount '/data' I:Actual block device: '/dev/block/dm-0', current file system: 'ext4' Updating partition details... I:Can't probe device /dev/block/dm-0 I:Unable to mount '/data' I:Actual block device: '/dev/block/dm-0', current file system: 'ext4' I:Unable to mount '/sdcard1' I:Actual block device: '', current file system: 'auto' I:Unable to mount '/usb-otg' I:Actual block device: '', current file system: 'auto' ...done I:Can't probe device /dev/block/dm-0 I:Unable to mount '/data' I:Actual block device: '/dev/block/dm-0', current file system: 'ext4' Unable to mount storage /data | /dev/block/dm-0 | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Can_Be_Encrypted Is_Encrypted Is_Decrypted Has_Data_Media Can_Encrypt_Backup Use_Userdata_Encr Symlink_Path: /data/media Symlink_Mount_Point: /sdcard Primary_Block_Device: /dev/block/mmcblk0p49 Decrypted_Block_Device: /dev/block/dm-0 Crypto_Key_Location: footer Length: -16384 Display_Name: data Storage_Name: Internal Storage Backup_Path: /data Backup_Name: data Backup_Display_Name: Data Storage_Path: /data/media Current_File_System: ext4 Fstab_File_System: ext4 Backup_Method: files MTP_Storage_ID: 65539 I:Unmounting main partitions... I:Done reading ORS command from command line I:operation_end - status=0 I:Set page: 'decrypt_pattern' I:Set page: 'main' I:Set page: 'clear_vars' I:Set page: 'main2' SELinux contexts loaded from /file_contexts Full SELinux support is present. I:Can't probe device /dev/block/dm-0 I:Unable to mount '/data' I:Actual block device: '/dev/block/dm-0', current file system: 'ext4' I:Unable to mount settings storage during GUI startup. I:Copying file /cache/recovery/log to /cache/recovery/last_log I:Can't probe device /dev/block/dm-0 I:Unable to mount '/data' I:Actual block device: '/dev/block/dm-0', current file system: 'ext4' I:Can't probe device /dev/block/dm-0 I:Unable to mount '/data' I:Actual block device: '/dev/block/dm-0', current file system: 'ext4' Unable to mount /data/media/TWRP/.twrps I:Attempt to load settings from settings file... I:InfoManager file '/data/media/TWRP/.twrps' not found. I:Backup folder set to '/data/media/TWRP/BACKUPS/f707e0500604' I:Copying file /etc/recovery.fstab to /cache/recovery/recovery.fstab I:Version number saved to '/cache/recovery/.version' I:Can't probe device /dev/block/dm-0 I:Unable to mount '/data' I:Actual block device: '/dev/block/dm-0', current file system: 'ext4' I:Unable to mount '/sdcard1' I:Actual block device: '', current file system: 'auto' I:Unable to mount '/usb-otg' I:Actual block device: '', current file system: 'auto' I:TWFunc::Set_Brightness: Setting brightness control to 255 I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/en.xml' directly parsing languageFile parsing languageFile done I:Translating partition display names I:Backup folder set to '/data/media/TWRP/BACKUPS/f707e0500604' I:Starting MTP I:[MTP] Starting MTP I:Can't probe device /dev/block/dm-0 I:Unable to mount '/data' I:Actual block device: '/dev/block/dm-0', current file system: 'ext4' MTP Enabled I:Check_Lifetime_Writes result: '648837' I:Switching packages (TWRP) I:Starting Adb Backup FIFO I:Set page: 'main' I:Set page: 'clear_vars' I:Set page: 'main2' I:[MTP] created new mtpserver object I:[MTP] MtpServer::run fd: 18 I:TWFunc::Set_Brightness: Setting brightness control to 5 I:TWFunc::Set_Brightness: Setting brightness control to 0 Any ideas what I should try next or where I could find helpful information?

Pixel phones (both older Qualcomm and newer Google Tensor) are known for very good camera algorithm. What I have heard the camera chipset (hardware) is similar to other phones, but the algorithm is what makes quite significant difference. Which part of the software stack is doing that algorithms? Is it only [Pixel Camera app](https://play.google.com/store/apps/details?id=com.google.android.GoogleCamera) or is there some other firmware? I'm asking if I reinstall stock Android with [LineageOS](https://lineageos.org/) whether I loose this functionality. Also, I suppose Pixel Camera app is installable on LineageOS. I'm asking specifically about Google Pixel 5 (redfin) and 6 (oriole), but it can be considered as a general question about all Pixel phones. I also suppose this is the only functionality I could use when migrating to LineageOS (I've had good experience with LineageOS support on other phones).