Sorry for the inconvenience, but it's a known issue in this version (20200812). Please install the new kernel provided in the release page (mirror) to fix this problem.
Last edited:
I cannot get WJXXBSH's LineageOS ROM to work for me. It shows the word Android on a black background and does not go any further. I have done a format, installed the new kernel, installed TWRP-20190528-3.3.1.0-libra.img, and have an unlocked bootloader. Havoc ROM and other Lineage ROMs install and work fine. Is there anything else I can try? Thanks.
Did you install GAPPs or something else into "/system"? Also, did the device get too hot (eg. more than 75℃) or has low battery (eg. less than 10%) during the boot process? Both the latest rom and kernel works properly on my device, no boot issue happened.
Thanks so much for getting back to me. I did a complete format. No GApps/magisk/anything else installed. The device did not get hot. Battery was over 50% during the boot process. Install of the latest ROM does not work. I've currently installed Mokee, which seems to be fine for my purposes, but I would really like to understand what I've done wrong. I've read through every post in this thread and it seems like I'm the only one having these issues. I've now updated the firmware, I'll try installing again and see if that helps.
Updated firmware to fw_libra_miui_MI4c_V10.1.1.0.NXKCNFI_13b9b312d0_7.0, wiped everything except for Internal Storage partition, and installed lineage-17.1-20200812-UNOFFICIAL-libra. After 10 minutes, still on the black screen that says "android". Device does not feel hot. No adb available. Any other ideas?
I've tested most of WJXXBSH's ROMs 15.1 - 17.1 without installing any firmware. Before each installation (talking about updating different Android based version) I wiped Dalvik, System, Data, Internal mem., cache and haven't encountered any boot issues with his ROMs. TWRP ver. 3.3.1.0, as well
Maybe you can do a full backup and wipe everything including internal data?
Maybe you can do a full backup and wipe everything including internal data?
Thanks for the suggestion, but wiping everything made no difference.
---------- Post added at 07:23 PM ---------- Previous post was at 06:26 PM ----------
Okay, I finally got it working. For anyone else that is having this problem I solved it by installing the TWRP version from repartition thread here. I then formatted the cust and vendor partitions (when were not previously visible). After reinstalling the ROM it was able to boot successfully.
Thanks again to WJXXBSH for making this ROM possible.
Thank you for allowing users of libra to continue using with their devices without feeling abandoned. :good:
I had to delete "NotoSansCJK.ttc" to get GApps pico installed on LineageOS 17.1/mi4c. But to be able to read CJK it is possible to kinda "roll-back" to limited set.
(note that you will need developer mode enabled and ADB debugging over USB with root rights for it)
To roll-back it should be enough (didn't tested):
(normal boot)
(boot in TeamWin recovery, TWRP)
Based on resources:
- Complain about Android 7.0 having only one weight for CJK that includes quote from fonts.xml (can't post links yet)
- Locally found old CyanogenMod for hushan with fonts.xml that references OTF font and thus confirms we can use them.
I had to delete "NotoSansCJK.ttc" to get GApps pico installed on LineageOS 17.1/mi4c. But to be able to read CJK it is possible to kinda "roll-back" to limited set.
(note that you will need developer mode enabled and ADB debugging over USB with root rights for it)
- Download from Google (google for "NotoSansCJK fonts") "Region-specific Subset" NotoSans* (e.g. NotoSansJP-[weight].otf) ZIP-files.
- You'll need only Regular files (e.g. "NotoSansJP-Regular.otf"). In total should occupy ~23M for all 4 languages.
- Download original "fonts.xml" (apparently contains mapping of which font file to use) from device:
Code:adb pull /system/etc/fonts.xml - Backup it somewhere safe
- Apply next patch "fonts.xml" either manually or using "patch" to remove all references to "NotoSansCJK.ttc" and replace weight 400 with corresponding OTF files
Code:--- fonts.xml.orig 2020-09-27 22:17:31.037798504 +0200 +++ fonts.xml 2020-09-27 21:43:11.947398843 +0200 @@ -546,52 +546,28 @@ <font weight="400" style="normal">NotoSansSymbols-Regular-Subsetted.ttf</font> </family> <family lang="zh-Hans"> - <font weight="100" style="normal" index="2">NotoSansCJK.ttc</font> - <font weight="300" style="normal" index="7">NotoSansCJK.ttc</font> - <font weight="350" style="normal" index="12">NotoSansCJK.ttc</font> - <font weight="400" style="normal" index="17">NotoSansCJK.ttc</font> - <font weight="500" style="normal" index="27">NotoSansCJK.ttc</font> - <font weight="700" style="normal" index="32">NotoSansCJK.ttc</font> - <font weight="900" style="normal" index="42">NotoSansCJK.ttc</font> + <font weight="400" style="normal">NotoSansSC-Regular.otf</font> <font weight="400" style="normal" fallbackFor="serif">NotoSerif-Regular.ttf</font> <font weight="700" style="normal" fallbackFor="serif">NotoSerif-Bold.ttf</font> <font weight="400" style="italic" fallbackFor="serif">NotoSerif-Italic.ttf</font> <font weight="700" style="italic" fallbackFor="serif">NotoSerif-BoldItalic.ttf</font> </family> <family lang="zh-Hant zh-Bopo"> - <font weight="100" style="normal" index="3">NotoSansCJK.ttc</font> - <font weight="300" style="normal" index="8">NotoSansCJK.ttc</font> - <font weight="350" style="normal" index="13">NotoSansCJK.ttc</font> - <font weight="400" style="normal" index="18">NotoSansCJK.ttc</font> - <font weight="500" style="normal" index="28">NotoSansCJK.ttc</font> - <font weight="700" style="normal" index="33">NotoSansCJK.ttc</font> - <font weight="900" style="normal" index="43">NotoSansCJK.ttc</font> + <font weight="400" style="normal">NotoSansTC-Regular.otf</font> <font weight="400" style="normal" fallbackFor="serif">NotoSerif-Regular.ttf</font> <font weight="700" style="normal" fallbackFor="serif">NotoSerif-Bold.ttf</font> <font weight="400" style="italic" fallbackFor="serif">NotoSerif-Italic.ttf</font> <font weight="700" style="italic" fallbackFor="serif">NotoSerif-BoldItalic.ttf</font> </family> <family lang="ja"> - <font weight="100" style="normal" index="0">NotoSansCJK.ttc</font> - <font weight="300" style="normal" index="5">NotoSansCJK.ttc</font> - <font weight="350" style="normal" index="10">NotoSansCJK.ttc</font> - <font weight="400" style="normal" index="15">NotoSansCJK.ttc</font> - <font weight="500" style="normal" index="25">NotoSansCJK.ttc</font> - <font weight="700" style="normal" index="30">NotoSansCJK.ttc</font> - <font weight="900" style="normal" index="40">NotoSansCJK.ttc</font> + <font weight="400" style="normal">NotoSansJP-Regular.otf</font> <font weight="400" style="normal" fallbackFor="serif">NotoSerif-Regular.ttf</font> <font weight="700" style="normal" fallbackFor="serif">NotoSerif-Bold.ttf</font> <font weight="400" style="italic" fallbackFor="serif">NotoSerif-Italic.ttf</font> <font weight="700" style="italic" fallbackFor="serif">NotoSerif-BoldItalic.ttf</font> </family> <family lang="ko"> - <font weight="100" style="normal" index="1">NotoSansCJK.ttc</font> - <font weight="300" style="normal" index="6">NotoSansCJK.ttc</font> - <font weight="350" style="normal" index="11">NotoSansCJK.ttc</font> - <font weight="400" style="normal" index="16">NotoSansCJK.ttc</font> - <font weight="500" style="normal" index="26">NotoSansCJK.ttc</font> - <font weight="700" style="normal" index="31">NotoSansCJK.ttc</font> - <font weight="900" style="normal" index="41">NotoSansCJK.ttc</font> + <font weight="400" style="normal">NotoSansKR-Regular.otf</font> <font weight="400" style="normal" fallbackFor="serif">NotoSerif-Regular.ttf</font> <font weight="700" style="normal" fallbackFor="serif">NotoSerif-Bold.ttf</font> <font weight="400" style="italic" fallbackFor="serif">NotoSerif-Italic.ttf</font> - Place OTF files in "/system/fonts" and "fonts.xml" in its "/system/etc/fonts.xml" (instruction for normally booted device):
Code:# upload all files we prepared previously to sdcard adb push NotoSans*-Regular.otf fonts.xml /sdcard # connect to device adb shell # after this line you supposed to be in the shell and see in prompt something like "[email protected]:/" # obtain root rights (prompt probably will change to "[email protected]" after this command) su # enable modification of /system/fonts and /system/etc mount -o remount,rw / # backup fonts.xml cp /system/etc/fonts.xml{,.orig} # put files in their corresponding places cp /sdcard/NotoSans*-Regular.otf /system/fonts/ cp /sdcard/fonts.xml /system/etc/fonts.xml # resotre read-only state on system partition (just in case) mount -o remount,ro / - You may need to re-boot phone (don't remember if I did).
To roll-back it should be enough (didn't tested):
(normal boot)
Code:
adb shell
su
mount -o remount,rw /
cp /system/etc/fonts.xml{.orig,}
Code:
# ensure you mounted system as read-write from menu
adb shell
cp /system/etc/fonts.xml{.orig,}- Complain about Android 7.0 having only one weight for CJK that includes quote from fonts.xml (can't post links yet)
- Locally found old CyanogenMod for hushan with fonts.xml that references OTF font and thus confirms we can use them.
Last edited:
@WJXXBSH Thank you very much for your work and all you have done to improve this ROM.
Anyway, I want to ask you some questions about what I have to do. The ROM is fantastic and smooth but my device tends to overheting very easly (90°C), also building the last kernel or trying to downscale the maximum clock frequency, reading the stats I've noticed that the CPU works always at the higher frequency possible, the battery discharge very quickly in a few hours and sometimes it random reboots.
The second problem regards GPS, the device is able to retreive the live position and also the movement, but when I use a navigation app or I try to register my jogging trips with my fitness app it freaks out. In Google Maps the navigation system cursor doesn't move even if I'm walking or driving around, while in the fitness app when I'm running it jumps from a point to another corrupting all the stats and registrating a false trip.
Do you think there is any way to resolve this problem, I am a young electronic engineer but I've never build an android ROM even if I can try to help if you know where is the problem.
PS: After I build your last kernel I don't even know how can I restore an older version to install older ROM builds lol
Anyway, I want to ask you some questions about what I have to do. The ROM is fantastic and smooth but my device tends to overheting very easly (90°C), also building the last kernel or trying to downscale the maximum clock frequency, reading the stats I've noticed that the CPU works always at the higher frequency possible, the battery discharge very quickly in a few hours and sometimes it random reboots.
The second problem regards GPS, the device is able to retreive the live position and also the movement, but when I use a navigation app or I try to register my jogging trips with my fitness app it freaks out. In Google Maps the navigation system cursor doesn't move even if I'm walking or driving around, while in the fitness app when I'm running it jumps from a point to another corrupting all the stats and registrating a false trip.
Do you think there is any way to resolve this problem, I am a young electronic engineer but I've never build an android ROM even if I can try to help if you know where is the problem.
PS: After I build your last kernel I don't even know how can I restore an older version to install older ROM builds lol
For problem #1
The CPU shouldn't be always at the highest frequency, as the scheduler will choose a proper one dynamically. Also, up to 4 cores will be offlined when the device is too hot, working as a thermal control method (there are some problems about "cpufreq" in kernel, so frequency limit couldn't be used for thermal control, that's why core control exists here as a fallback method).
Did you do some changes to "/system" or kernel parameters? Besides, make sure the value of "/sys/devices/system/cpu/cpuX/cpufreq/scaling_governor" (X = 0, 4) is "sched" but not "performance".
After all, MSM8992/8994 is much easier to generate more heat than other SoC, that's why only a few devices choose to use these modules.
For problem #2
Though it usually takes more than 1 minute to do a "3D GPS Fix" after a cold launch, the GPS module works properly on my own device. I have confirmed that GPS works well for maps/navigation/speed monitor/fitness apps/etc... in mainland China, it should also work in other countries as no hardware/software is changed.
For PS
If you want to go back to the original kernel in lineage roms, please go to this Release Page and download the boot image. By the way, which toolchain are you using to build the kernel (my choice is gcc-10)?
Last edited:
Hey there!
So I encountered a couple problems while using your 17.x ROM on this device:
First one: Settings>Security>Screen Lock (gear)>Lock after screen timeout doesn't seem to be doing anything.
Whichever unlocking method you choose (PIN/password/pattern) this setting is ignored and device locks immediately after screen goes black.
The second one is more interesting.
There is no right audio channel. At all.
For example, if you play this youtube video M05w0gIDQVM (put id in youtube search video should appear first in results) you can hear something when it plays both channels and left audio channel but not when right is playing.
Also you can check this if you set Settings>Accessibility>Audio balance all the way to the right, there will be no sound at all coming from device.
This also happens when playing audio through wired headphones, both earphones playing left channel audio.
Only workaround I found was setting sound to mono in accessibility settings. This way right channel is at least present, but in both ears, which is far from perfect.
Don't know if wireless devices are affected, don't have any to test.
Both problems aren't present on 16.0, audio playback is fine, device locks after set time after screen goes black.
Fun part is that I first encountered both problems on MoKee, when they updated ROM to android 10, same happened there.
So yeah, if anyone could at least confirm that this isn't problem on my end, that would be cool.
Device is libra 3/32GB btw.
So I encountered a couple problems while using your 17.x ROM on this device:
First one: Settings>Security>Screen Lock (gear)>Lock after screen timeout doesn't seem to be doing anything.
Whichever unlocking method you choose (PIN/password/pattern) this setting is ignored and device locks immediately after screen goes black.
The second one is more interesting.
There is no right audio channel. At all.
For example, if you play this youtube video M05w0gIDQVM (put id in youtube search video should appear first in results) you can hear something when it plays both channels and left audio channel but not when right is playing.
Also you can check this if you set Settings>Accessibility>Audio balance all the way to the right, there will be no sound at all coming from device.
This also happens when playing audio through wired headphones, both earphones playing left channel audio.
Only workaround I found was setting sound to mono in accessibility settings. This way right channel is at least present, but in both ears, which is far from perfect.
Don't know if wireless devices are affected, don't have any to test.
Both problems aren't present on 16.0, audio playback is fine, device locks after set time after screen goes black.
Fun part is that I first encountered both problems on MoKee, when they updated ROM to android 10, same happened there.
So yeah, if anyone could at least confirm that this isn't problem on my end, that would be cool.
Device is libra 3/32GB btw.
For problem #1
Thanks for your feedback, or I won't know this bug after all. It seems like a bug from LineageOS itself, as the device configuration or the kernel shouldn't cause this problem.
I think this issue is caused by the way (on Android 10) that handles power button events. Press the power button when screen on will lock the screen immediately, which is the default and correct behavior of Android. When screen is off, press the power button will just turn it on. However, press the power button may trigger "lock the screen immediately" regardless of the screen status (on/off) on Android 10. That's how the problem happened.
As a simple solution, disable "Power button instantly locks" in Settings to get rid of this bug. I don't know if this bug also happens to other device with lineage-17.1 roms. If so, you may report this issue to LineageOS teams as a final solution.
For problem #2
It's a known issue of Android 10 roms on Mi-4c, as the call/media volume may not be as expected in some conditions. I have changed the acdb channels to avoid a serious problem which makes media volume lost control (always highest), but also led to some other bugs just as you said. Set audio output to mono mode will fix it in software layer, but it's not the right solution.
For a test, you may try to replace "/system/vendor/etc/audio_platform_info.xml" with the one from Mokee roms to see what will happen (I don't have a wireless earphone, so couldn't do such tests).
BTW, my device configuration for lineage-16.0 is a fork from Mokee (Android 9 = lineage-16.0 = Mokee 90.0), then made changes related to lineage-17.1 (Android 10) manually. That's why some files are similar to the ones from Mokee sources (or even Oneplus 2).
Last edited:
Thanks for answering.
Issues #1970, #2464, #2430 on their gitlab.
Sorry for that one.
On a somewhat related note, I've read through your volume issue on git. You mentioned that your changes to this file cause new issues:
But on MoKee itself I've never encountered this issues.
And after flashing their latest nightly build MK100.0-libra-202010130850-NIGHTLY both recorder and local media playback work just fine.
Though no right channel audio and no call volume control (never noticed that it didn't work).
Indeed it is, users with other devices did found this issue.
Issues #1970, #2464, #2430 on their gitlab.
Sorry for that one.
Nothing has changed. Behaves the same.
On a somewhat related note, I've read through your volume issue on git. You mentioned that your changes to this file cause new issues:
They're still there even after reverting to audio_platform_info.xml from MoKee you linked.
But on MoKee itself I've never encountered this issues.
And after flashing their latest nightly build MK100.0-libra-202010130850-NIGHTLY both recorder and local media playback work just fine.
Though no right channel audio and no call volume control (never noticed that it didn't work).
I have just flashed the last build and I notice the same problems. With bluetooth external devices right and left channels work fine.
The microphone instead doesn't work for recording (Whatsapp, Telegram and also built-in recorder).
Hi,
Trying to upgrade my wife's Mi 4c from Teamsuperluminal 7.1.2 to this new and optimized rom. Since I found no install instructions in this thread whatsoever, I followed what I normally do when installing different android version:
1. Rebooted to TWRP (it is 3.0.2 from Teamsuperluminal)
2. Wiped cache, dalvik cache, data and system
3. Tried to install rom
Upon starting the install I immediately get an error E3004: This package is for device 4c,libra; this device is . It is the 2 Gb version, not the 3 Gb, could that be the problem?
I tried searching for this error but no luck. Can't believe I am the first one hitting it. HELP pls!
P.S. Yes I am sure the device is Xiaomi Mi 4c. It has been unlocked years ago to install the teamsuperluminal and is also using their TWRP.
UPDATE 1: I deleted the phone model check from updater-script and flashed the rom successfully. Unfortunately upon device reboot from TWRP, it never goes beyond the MI logo. Ideas?
UPDATE 2: I booted into recovery, flashed twrp-20180106-1033.img (TWRP 3.1.1) and booted back into the new recovery. Tried the original non-modified lineage-17.1-20201014-UNOFFICIAL-libra.zip but it still throws the same error. So definitely not a problem with old TWRP.
UPDATE 3: Installed the TWRP OrangeFox https://orangefox.download/en/device/libra (TWRP 3.3.1) and was able to install the non-modified lineage-17.1-20201014-UNOFFICIAL-libra.zip, but upon reboot it never goes beyond the MI logo again. I waited for around 10 mins, nothing changes.
UPDATE 4: I tried to install an older version of the rom lineage-17.1-20200914-UNOFFICIAL-libra.zip and it would not install. ERROR: Comparing TZ version TZ.BF.3.0.1-00067 to TZ.BF.3.0.1-00033 assert failed: msm8994.verify_trustzone == "1". What the F .. isn't falling back to older version allowed?
I think the only thing I haven't tried is repartitioning like @Soupbean (installing the TWRP version from repartition thread here. I then formatted the cust and vendor partitions). Is this issue related to partitioning or something else?
Trying to upgrade my wife's Mi 4c from Teamsuperluminal 7.1.2 to this new and optimized rom. Since I found no install instructions in this thread whatsoever, I followed what I normally do when installing different android version:
1. Rebooted to TWRP (it is 3.0.2 from Teamsuperluminal)
2. Wiped cache, dalvik cache, data and system
3. Tried to install rom
Upon starting the install I immediately get an error E3004: This package is for device 4c,libra; this device is . It is the 2 Gb version, not the 3 Gb, could that be the problem?
I tried searching for this error but no luck. Can't believe I am the first one hitting it. HELP pls!
P.S. Yes I am sure the device is Xiaomi Mi 4c. It has been unlocked years ago to install the teamsuperluminal and is also using their TWRP.
UPDATE 1: I deleted the phone model check from updater-script and flashed the rom successfully. Unfortunately upon device reboot from TWRP, it never goes beyond the MI logo. Ideas?
UPDATE 2: I booted into recovery, flashed twrp-20180106-1033.img (TWRP 3.1.1) and booted back into the new recovery. Tried the original non-modified lineage-17.1-20201014-UNOFFICIAL-libra.zip but it still throws the same error. So definitely not a problem with old TWRP.
UPDATE 3: Installed the TWRP OrangeFox https://orangefox.download/en/device/libra (TWRP 3.3.1) and was able to install the non-modified lineage-17.1-20201014-UNOFFICIAL-libra.zip, but upon reboot it never goes beyond the MI logo again. I waited for around 10 mins, nothing changes.
UPDATE 4: I tried to install an older version of the rom lineage-17.1-20200914-UNOFFICIAL-libra.zip and it would not install. ERROR: Comparing TZ version TZ.BF.3.0.1-00067 to TZ.BF.3.0.1-00033 assert failed: msm8994.verify_trustzone == "1". What the F .. isn't falling back to older version allowed?
I think the only thing I haven't tried is repartitioning like @Soupbean (installing the TWRP version from repartition thread here. I then formatted the cust and vendor partitions). Is this issue related to partitioning or something else?
Last edited:
In brief, the firmware on your device is too old to install roms which need new bootloader to work. You have mentioned that your device was officially unlocked, so the most simple way is to install new firmware as well as new recovery. Also, it's no need to repartition your device to install my roms.
What you need
- New firmware: https://androidfilehost.com/?fid=11410963190603841673
- New TWRP recovery: https://www.androidfilehost.com/?fid=8889791610682882451
Instructions
- Boot into recovery mode, and install the firmware (no need to reboot, just go to the next step).
- Install the new recovery image (go to next step only if your recovery doesn't support to install a image file), then reboot into recovery again.
- Boot into fastboot mode (bootloader), then connect your device to PC. If you have ADB (platform-tools) installed, run "fastboot flash recovery xxx.img" and reboot the device to recovery.
- If the new recovery image boots up, try installing my latest rom and see what will happen.
Last edited:
The microphone problem is a side effect caused by fixing media volume issue (because the "pcm_ids" or "acdb_ids" might be wrong).
To fix the microphone issue, replace "/system/vendor/etc/audio_platform_info.xml" with this one and reboot. However, media volume may lost control when playing audio files with some specific codecs. Other Android 10 roms with that file (which should be the right one) doesn't have such issues, but it still happens to lineage-17.1 even with the same audio configs.
@WJXXBSH Thank you for the quick apply and steps. Actually all that was needed was for me to boot into recovery and flash the fw_libra_miui_MI4c_V10.1.1.0.NXKCNFI_13b9b312d0_7.0.zip and reboot. Then your rom booted just fine. However next steps are unclear to me, usually I flash superSU provided by the rom dev to get root and also flash gapps. I read in this thread there is not enough space to flash even pico version, so I need to delete some system fonts. But how do I delete them when I am not yet root. The built-in file manager with Android 10 does not see system files such as ""/system/fonts/".
Thanks!
Thanks!
SuperSU is not support after Android 9 (I remember?), a better choice is to use the built-in addon-su (which could be enabled in "Developer options - Root access", no need to flash anything else), or use Magisk instead. If you want to install GAPPs, there might not be enough space left in "/system". It's a common choice to delete "NotoSansCJK.ttc" (saves about 105MB), but you should try to install the GAPPs first to see if there is really no space.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone