Vendor image mismatch? - Xiaomi Mi 6 Questions & Answers

Hey guys,I have compiled Resurrection Remix Oreo from their source.Now i get "Vendor image mismatch" every boot.I have checked fingerprint property among system ,vendor and boot, they are all same.Although the rom works fines,the popup is too annoying for me.Is there a way to workaround this?Or Will there be a source patch to hide this popup?

Well,i finally found the case with on boot logcat.....It's caused by "Vendor interface is incompatible".I think android found that sagit roms is built with non-standard treble.....So the following is my fix,but that's need to edit the android source.
file>>SOURCE_TOP/frameworks/base/core/java/android/os/Build.java
Found those pattern and edit to ,see attached image.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Developers known what to do next.
Remember to add ro.vendor.ignoremismatch=true in your vendor prop.

Related

[BOOTANIMATION] Circular Slim by radioflyer

ok, so i've been working on a new animation (yeah...it's not quite done yet, but i'm a bit stuck) and i wanted to share the process with you guys so far.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
here is the problem: i've tried making both a bootanimation.zip to copy to system/media/ and a flashable zip for cmw but both attempts have been complete fails.
i've attached both files so that if anyone wants to check them out to see what i'm doing wrong and can help out, is welcome to do so.
NOTE: yes, both files are zipped as "store" and i used my previous boot animation as base for this one.
NOTE 2: I'm on the latest (slim bean 2.7) slim rom and using the devil/hellybean kernel if anyone is wondering

[Q] [ROM]MIUI v5 for LGL24 need help

I have no idea haw to root,can someone help me
I have edit boot.img
I change ro.secure=1 to ro.secure=0. but when I flash it, it will be ro.secure=1.
bug list
1.messages cant receive text messages, require to install the third party soft such as GOSMS or evolveSMS
2.nfc
3.no root ,I have no idea ,can someone help me ???
4.more any little bugs
if you are flash this rom fist ,plese
1.add apn by youself
2.please make a folder form sdcard/DCIM/Screenshots,then the screenshot can be saved.
download:
https://mega.co.nz/#!PZwCmZLA!YvmiHk42iskzqQKsTjrhoHrICSQVAAr2zSGudUsoKvQ
plese do not flash supersu .it will cause MIUi desktop cant use
screenshoot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

AusweisApp2 (German eID) does not work with NFC on LOS 18.1

The German eID App does not seem to work properly for me on the OnePlus 5T with LineageOS 18.1. I did update to the newest build today (Build: lineage_dumpling-userdebug 11 RQ3A.211001.001 10038769) but the problem persists.
Usually I would just assume the NFC is too weak but the app is supposed to function with the phone according to the AusweisApp2 website.
I also know that the NFC sensor is in the camera on the OnePlus 5T and have adapted accordingly but it doesn't change the outcome. Anything other than just the preliminary check does not work. (s. Screenshots below) Did anyone get this to work recently and what can I try?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Cheers,
goldsteal

can anyone help me with this error? - custom rom compilation

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Building CrDroid 8.8
Moto G 5G Plus (nairo)
what should i do to get the error resolved?
Those are warnings, turned into errors due to the "-Werror" flag used in compilation, making the compilation fail. The underlying issues outlined by the warnings are basically "code linting" issues ("unused but set" variables; linters are programs that go over code and can say "huh, why did you even write that? Lemme put a warning on it for you to assess."). Those variables should be of no consequence when running the program/ROM, and be optimized out by the compiler. You can safely remove the flag and try recompiling again.

Question [How to create files in root partition on android 12]

How can i create a directory in the root/sys/module path ? I have tried many ways but still no success, even though the device is rooted
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
duongtulap said:
How can i create a directory in the root/sys/module path ? I have tried many ways but still no success, even though the device is rootedView attachment 5859329
Click to expand...
Click to collapse
You can't. It becomes protected after boot which is why you use magisk modules to do modifications in root prior to a full boot. I think this change happened in Android 10? Don't quote me on that.

Categories

Resources