RitZz
October 12, 2023, 10:15pm
1
Looking for a possible version of Xiaomi MI 10 5G, codename: Umi, that was released on February 14, 2020.
Device specifications
Basic
Spec Sheet
CPU
Octa-core (1x2.84 GHz Cortex-A77 & 3x2.42 GHz Cortex-A77 & 4x1.80 GHz Cortex-A55)
Chipset
Qualcomm SM8250 Snapdragon 865 5G (7 nm+)
GPU
Adreno 650
Memory
6/8/12 GB
Shipped Android Version
10
Latest Android Version
13
Storage
128/256 GB
MicroSD
N/A
Battery
4780 mAh (non-removable)
Dimensions
162.5 x 74.8 x 9 mm (6.40 x 2.94 x 0.35 in)
Display
1080 x 2340 pixels, 19.5:9 ratio (~386 ppi density)
Rear Camera
4
Camera 1
108 MP, f/1.7, (wide), 1/1.33", 0.8”m, PDAF, OIS
Camera 2
13 MP, f/2.4, 12mm (ultrawide), 1/3.06", 1.12”m
Camera 3
2 MP, f/2.4, (macro)
Camera 4
2 MP, f/2.4, (depth)
Front Camera
20 MP, f/2.0, (wide), 1/3", 0.9”m
Release Date
February 2020
Resources
Xiaomi Mi 10 | XDA Forums
Regain your privacy! Adopt /e/ the unGoogled mobile OS and online services
Nice request formatting, dude !
Then I rise-up with lineage-umi-microg : it would be great to establish some kind of collaboration with them !
1 Like
aibd
October 14, 2023, 8:00am
4
1 Like
yes I saw it but there seems only to include a prebuild kernel for Umi which I donât know to build. Do you have experience with prebuild kernels?
1 Like
aibd
October 14, 2023, 8:23am
6
No, I donât ⊠only a very quick look ⊠but I did notice that the Lineage-19.1 kernel version is not default. Am I wrong to assume that âprebuilt kernel filesâ are âready to goâ â I guess that is what you are finding ?
1 Like
ronnz98
October 14, 2023, 12:07pm
7
I tried now both sources for LOS20 with 3 kernels in total and could not successfully buildâŠsorry
1 Like
RitZz
October 15, 2023, 6:40pm
8
So, is there no possibility of getting /e for this phone?
Yes there is! I will try when sources are updatedâŠ
Or maybe someone with more build experience than me make a try
RitZz
October 16, 2023, 9:57pm
10
sounds good.
fingers crossed
Thank you for your efforts!
ronnz98
October 27, 2023, 5:47am
11
I tried now again to build but got this error:
[ 76% 123656/162513] Copy init script: out/target/product/umi/system/etc/init/heapprofd.rc
FAILED: out/target/product/umi/system/etc/init/heapprofd.rc
/bin/bash -c â(out/host/linux-x86/bin/host_init_verifier -p out/target/product/umi/obj/ETC/passwd_system_intermediates/passwd_system -p out/target/product/umi/obj/ETC/passwd_system_ext_intermediates/passwd_system_ext -p out/target/product/umi/obj/ETC/passwd_vendor_intermediates/passwd_vendor -p out/target/product/umi/obj/ETC/passwd_odm_intermediates/passwd_odm -p out/target/produ
ct/umi/obj/ETC/passwd_product_intermediates/passwd_product --property-contexts=out/target/product/umi/obj/ETC/plat_property_contexts_intermediates/plat_property_contexts --property-contexts=out/target/product/umi/obj/ETC/system_ext_property_contexts_intermediates/system_ext_property_contexts --property-contexts=out/target/product/umi/obj/ETC/product_property_contexts_intermediate
s/product_property_contexts --property-contexts=out/target/product/umi/obj/ETC/vendor_property_contexts_intermediates/vendor_property_contexts --property-contexts=out/target/product/umi/obj/ETC/odm_property_contexts_intermediates/odm_property_contexts external/perfetto/heapprofd.rc ) && (mkdir -p out/target/product/umi/system/etc/init/ ) && (rm -f out/target/product/umi/system/et
c/init/heapprofd.rc ) && (cp "external/perfetto/heapprofd.rc" "out/target/product/umi/system/etc/init/heapprofd.rc" )â
host_init_verifier: Could not read line from âout/target/product/umi/obj/ETC/vendor_property_contexts_intermediates/vendor_property_contextsâ: Match operation âu:object_r:vendor_fingerprint_prop:s0â is not valid: must be either âprefixâ or âexactâ
17:12:55 ninja failed with: exit status 1
Any ideas how this can be addressed?
aibd
November 2, 2023, 8:19am
12
I was considering if the subject here seems to be about
#
ro.build.fingerprint is either set in /system/build.prop, or is
#
set at runtime by system_server.
ro.build.fingerprint u:object_r:fingerprint_prop:s0 exact string
Could not read line from
âout/target/product/umi/obj/ETC/vendor_property_contexts_intermediates/vendor_property_contexts`
You could go back up files in the trace to investigate what is missing / corrupted.
Fingerprints demystified
Maybe useful â for a different subject I had this bookmarked https://stackoverflow.com/questions/28776970/android-build-error-ro-build-fingerprint-cannot-exceed-91-bytes .
You might consider an updated variation of this suggestion
You could experiment with specify the build fingerprint string as command line argument to make
using:
make -j5 BUILD_FINGERPRINT="....."
.
ronnz98
November 8, 2023, 7:53pm
13
I did a stupid mistake on my first try, but now could successfully build for /e/OS-S
system
Closed
October 11, 2024, 10:16pm
14
This topic was automatically closed after 365 days. New replies are no longer allowed.