The built-in "Files" app is obviously not support root operations (because it's developed by Google). As a solution, install some other file manager app (Solid Explorer, Mixplorer, Root Explorer...) you prefer, or just reboot into recovery and use "Advanced - File manager" to delete any files you want (remember to mount "/system" in "Mount" first). A factory reset (wipe "/data" except "/data/media") might be needed to make GAPPs work properly.
is need to flash the new kernel provided in few previous comments to solve this issue ?Do you mean you had updated the rom from an ancient version (at the beginning of this year) to the latest one? If true, try a factory reset (wipe "/data" without "/data/media" + wipe "/system") and reinstall the latest rom again. Please also tell me if you had GAPPs or some Magisk modules installed.the last update flashed on my phone and get multiple reboot a day. But the screen responses is better than the build at begin of the year
The update bootloop the android startup image. juste wipe all and install it (remove some font files to have enough room to install gapp pico). then added what'sapp, facebook ,gphoto and messenger app from store.
Most Mi-4c roms should also work on Mi-4s, but I'm not sure if fingerprint or external sdcard works properly. For TWRP recovery, just use the same one for Mi-4c. Please note that your device needs to be unlocked before installing custom roms or recovery.
I've seen there's already version 18.1 in github (https://github.com/WJXXBSH/android_device_xiaomi_libra/tree/lineage-18.1)
Not yet, there are still some issues need to be resolved currently. I'm kind of busy this month, so my work about Lineage roms might be slower to leave more time for myself.
First, i would like to thank you for your fast response.
Converting system apps to user ones is certainly a solution (if there is a "classes.dex" inside APK). I once seen someone installed GAPPs as user apps and it worked properly, you could also try this way. As Google is blocked in China, I don't install GAPPs to my device so I could keep all necessary apps as well as the fonts in system partition. I think just removing the webview (then install Google Webview as user app) should provide enough space for GAPPs, even without deleting other apps.
I will write some documents about how to build Lineage ROMs on Mi-4c (with my device/kernel/vendor) later, wait me for some time (maybe days later).
./xxx/xiaomi/libra), it should work when you are trying to execute . build/envsetup.sh && lunch lineage_libra-userdebug in the root directory of your lineage-17.1 repos. However, a few build errors may happen due to some hacks in my device configs (eg. dex2oat). If you meet these errors, please refer to repo_17.diff and take the necessary changes in project build/make/ (not all of them is needed unless you want to build a rom like my releases with "user" build variant).<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="WJXXBSH/android_device_xiaomi_libra" path="device/xiaomi/libra" remote="github" revision="lineage-17.1" />
<project name="WJXXBSH/android_kernel_xiaomi_libra" path="kernel/xiaomi/libra" remote="github" revision="master" />
<project name="WJXXBSH/android_vendor_xiaomi_libra" path="vendor/xiaomi/libra" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" remote="github" revision="lineage-17.1" />
<project name="LineageOS/android_hardware_xiaomi" path="hardware/xiaomi" remote="github" revision="lineage-17.1" />
</manifest>Hi,
repo init -u https://github.com/LineageOS/android.git -b lineage-17.1ccache: error: Could not find compiler "clang" in PATH
make[3]: *** [/android/lineage/kernel/xiaomi/libra/scripts/Makefile.build:286: scripts/mod/empty.o] Error 1
make[3]: *** Waiting for unfinished jobs....
Using /android/lineage/kernel/xiaomi/libra as source for kernel
make[2]: *** [/android/lineage/kernel/xiaomi/libra/scripts/Makefile.build:527: scripts/mod] Error 2
make[1]: *** [/android/lineage/kernel/xiaomi/libra/Makefile:525: scripts] Error 2
make: *** [Makefile:126: sub-make] Error 2
make: Leaving directory '/android/lineage/kernel/xiaomi/libra'
19:11:24 ninja failed with: exit status 1My kernel is set to build with clang by default, so you should install
clang package in your system (depend on which Linux distribution you are using). I can only confirm that clang-11 is able to build a kernel without issues, higher version should also work. The kernel sources are compiled by clang, but will be linked by ld (inside gcc toolchains) with llvm plugin (provides by clang).TARGET_KERNEL_CLANG_PATH to the real path in your system if needed.# Kernel
BOARD_KERNEL_BASE := 0x00000000
BOARD_KERNEL_CMDLINE := androidboot.hardware=qcom androidboot.selinux=permissive ehci-hcd.park=3 msm_rtb.filter=0x37
BOARD_KERNEL_IMAGE_NAME := Image.gz-dtb
BOARD_KERNEL_PAGESIZE := 4096
TARGET_KERNEL_ARCH := arm64
TARGET_KERNEL_CLANG_COMPILE := true
TARGET_KERNEL_CLANG_PATH := /lib/llvm-11
TARGET_KERNEL_CLANG_VERSION := 11.0
TARGET_KERNEL_CONFIG := libra_defconfig
TARGET_KERNEL_CROSS_COMPILE_PREFIX := aarch64-linux-gnu-
TARGET_KERNEL_HEADER_ARCH := arm64
TARGET_KERNEL_SOURCE := kernel/xiaomi/librabrunch lineage_libra-userdebug instead. If you want to test kernel building more efficiently, try make bootimage instead of making all targets.I am on 20.04 so the available clange is v10. I did: "sudo apt install clang gcc-aarch64-linux-gnu gcc-arm-linux-gnueabi llvm-dev" (llvm-dev is needed because of LLVMgold.so).
In /android/lineage/device/xiaomi/libra/BoardConfig.mk I had to replace CLANG_PATH and CLANG_VERSION:
TARGET_KERNEL_CLANG_PATH := /lib/llvm-10 TARGET_KERNEL_CLANG_VERSION := 10.0 brunch lineage_libra-userdebug).If you also installed gcc-aarch64 and gcc-arm on your computer, it's recommended to set
TARGET_KERNEL_CROSS_COMPILE_PREFIX to /bin/aarch64-linux-gnu- to make use of it (you can use shell command which -a aarch64-linux-gnu-gcc to get its real path).setprop persist.sys.cpu_overclock false in adb shell and reboot your device to disable overclock.Yup, I confirm "setprop" solves the reboot issue (I performed cpu throttling over the night).
Usually, "user" build variant has less debug stuffs and more strict limits than "userdebug" variant. It also makes the system image smaller and may provide better performance (eg. proguard optimization is enabled for most apps). My ROMs on AFH or GitHub Releases are all "user" builds, but I also make "userdebug" builds for testing purpose (usually for myself).
androidboot.selinux=permissive in kernel cmdline). The "user" builds sets selinux to "enforcing" mode by default, which will result in a bootloop (that's why there are two necessary patches about "permissive"). I tried to collect the selinux audit logs before, but found nothing suspicious at last, then the selinux status in my ROMs has been "permissive" until now.
