MIUI 10.0/10.1/10.2/10.3/10.4 STABLE RELEASE


Status
Not open for further replies.
Need some help here. I flashed the latest stable 10.3.16 for the K20 Pro , all is fine but when I open the Google app and search for something the moment that I press the search button it crashes.

Crash log :

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'Xiaomi/davinci_eea/davinci:9/PKQ1.190302.001/V10.3.7.0.PFJEUXM:user/release-keys'
Revision: '0'
ABI: 'arm64'
pid: 10566, tid: 10601, name: UserFacing3 >>> com.google.android.googlequicksearchbox:search <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
x0 0000000000000000 x1 0000000000002969 x2 0000000000000006 x3 0000000000000008
x4 fefeff6eff6d6860 x5 fefeff6eff6d6860 x6 fefeff6eff6d6860 x7 7f7f7f7f7f7f7f7f
x8 0000000000000083 x9 d53a114b8723dcf9 x10 0000000000000000 x11 fffffffc7ffffbdf
x12 0000000000000001 x13 ffffffffffffffff x14 ffffffffff000000 x15 ffffffffffffffff
x16 00000070004902b8 x17 00000070003afee0 x18 0000000000000010 x19 0000000000002946
x20 0000000000002969 x21 0000000000000000 x22 0000006f7ef82e48 x23 00000056ffcdf3e8
x24 0000000000000040 x25 0000006f602f9588 x26 00000056ffce06c0 x27 000000000000000b
x28 00000056ffcdf008 x29 0000006f7ef82d00
sp 0000006f7ef82cc0 lr 00000070003a3354 pc 00000070003a337c

backtrace:
#00 pc 000000000002237c /system/lib64/libc.so (abort+116)
#01 pc 00000000000032cc /system/bin/app_process64 (art::SignalChain::Handler(int, siginfo*, void*)+1076)
#02 pc 0000000000000638 [vdso:0000007004e98000]
#03 pc 000000000001e81c /system/lib64/libc.so (strlen+12)
#04 pc 000000000062b668 /system/priv-app/Velvet/lib/arm64/libgoogle_speech_jni.so (Java_com_google_speech_grammar_pumpkin_UserValidators_nativeAddGoldmineValidator+244)
#05 pc 0000000000240824 /data/dalvik-cache/arm64/system@priv-app@Velvet@Velvet.apk@classes.dex (offset 0x23a000) (com.google.speech.grammar.pumpkin.UserValidators.nativeAddGoldmineValidator+196)
#06 pc 0000000000557388 /system/lib64/libart.so (art_quick_invoke_stub+584)
#07 pc 00000000000cfcf4 /system/lib64/libart.so (art::ArtMethod::Invoke(art::Thread*, unsigned int*, unsigned int, art::JValue*, char const*)+200)
#08 pc 0000000000280374 /system/lib64/libart.so (art::interpreter::ArtInterpreterToCompiledCodeBridge(art::Thread*, art::ArtMethod*, art::ShadowFrame*, unsigned short, art::JValue*)+344)
#09 pc 000000000027b4a8 /system/lib64/libart.so (bool art::interpreter::DoCall<true, false>(art::ArtMethod*, art::Thread*, art::ShadowFrame&, art::Instruction const*, unsigned short, art::JValue*)+748)
#10 pc 000000000052913c /system/lib64/libart.so (MterpInvokeDirectRange+244)
#11 pc 0000000000549e94 /system/lib64/libart.so (ExecuteMterpImpl+15252)
#12 pc 000000000046b1c2 /system/priv-app/Velvet/Velvet.apk (offset 0x6e76000) (com.google.speech.grammar.pumpkin.UserValidators.addGoldmineUserValidator+14)
#13 pc 000000000025408c /system/lib64/libart.so (_ZN3art11interpreterL7ExecuteEPNS_6ThreadERKNS_20CodeItemDataAccessorERNS_11ShadowFrameENS_6JValueEb.llvm.806176459+488)
#14 pc 0000000000259b80 /system/lib64/libart.so (art::interpreter::ArtInterpreterToInterpreterBridge(art::Thread*, art::CodeItemDataAccessor const&, art::ShadowFrame*, art::JValue*)+216)
#15 pc 000000000027a36c /system/lib64/libart.so (bool art::interpreter::DoCall<false, false>(art::ArtMethod*, art::Thread*, art::ShadowFrame&, art::Instruction const*, unsigned short, art::JValue*)+940)
#16 pc 00000000005265c8 /system/lib64/libart.so (MterpInvokeVirtual+588)
#17 pc 0000000000549a94 /system/lib64/libart.so (ExecuteMterpImpl+14228)
#18 pc 00000000002726e6 /system/priv-app/Velvet/Velvet.apk (offset 0x5bce000) (com.google.android.apps.gsa.staticplugins.cx.a.cHD+34)
#19 pc 000000000025408c /system/lib64/libart.so (_ZN3art11interpreterL7ExecuteEPNS_6ThreadERKNS_20CodeItemDataAccessorERNS_11ShadowFrameENS_6JValueEb.llvm.806176459+488)
#20 pc 0000000000259b80 /system/lib64/libart.so (art::interpreter::ArtInterpreterToInterpreterBridge(art::Thread*, art::CodeItemDataAccessor const&, art::ShadowFrame*, art::JValue*)+216)
#21 pc 000000000027a36c /system/lib64/libart.so (bool art::interpreter::DoCall<false, false>(art::ArtMethod*, art::Thread*, art::ShadowFrame&, art::Instruction const*, unsigned short, art::JValue*)+940)
#22 pc 00000000005265c8 /system/lib64/libart.so (MterpInvokeVirtual+588)
#23 pc 0000000000549a94 /system/lib64/libart.so (ExecuteMterpImpl+14228)
#24 pc 0000000000272104 /system/priv-app/Velvet/Velvet.apk (offset 0x5bce000) (com.google.android.apps.gsa.staticplugins.cx.ar.call+72)
#25 pc 000000000025408c /system/lib64/libart.so (_ZN3art11interpreterL7ExecuteEPNS_6ThreadERKNS_20CodeItemDataAccessorERNS_11ShadowFrameENS_6JValueEb.llvm.806176459+488)
#26 pc 0000000000516e7c /system/lib64/libart.so (artQuickToInterpreterBridge+1020)
#27 pc 00000000005604fc /system/lib64/libart.so (art_quick_to_interpreter_bridge+92)
#28 pc 0000000001905bec /data/dalvik-cache/arm64/system@framework@boot.oat (offset 0x12c2000)

EDIT - Just to clarify when I was on stable 10.3.15 or on the 9.8.1 developer it was working fine. It only occured when I clean flashed the 10.3.16, I was on the 9.8.1 before.
 
Last edited:
I can't set unlock by fingerprint reader. In the past, everything was OK and the reader acted. I don't know what the reason is, I suspect a strange system update.

Is it possible for the MIUI version to completely disable the fingerprint sensor?

Model: Remi 4X
Android version: 7.1.2.N2G47H
MIUI version: MIUI Global 10.3 | Stable 10.3.1.0 (NAMMIXM)
Kernel version: 3.18.31-perf-g6507e5c

Co ciekawe po 5-cio krotnym naciśnięciu na wersję jądra wyświetla się Engineering Mode w którym można co prawda testować wiele elementów telefonu (ekran, radio itp.itd.) jednak nie ma możliwości testowania czytnika linii.

Interestingly, after pressing5 times: "Phone information" -> "kernel version" Engineering Mode is displayed in which you can test many phone elements (screen, radio, etc.), but you cannot test the line reader. Fingerprint sensor just doesnt exist there.
 
Recieved a Phone Call and earpiece + mic was not working for calls. Same issue for WhatsApp calls as well. If loudspeaker is turned for calls then we can hear other persons voice.

Logs

Temporary Workaround for this issue is freezing/disabling the Google Search App.
This helps for me as well few other from K20 Group. 4 Days uptime and no issue yet.
 
  • Like
Reactions: hiroptera
A question: if a device actually supported by Beta programm, in a few months will lose this support, the Stable Rom Will continue to be released, so also here with stable Xiaomi EU?
 
[QUOTE = "Igor Eisberg, publicación: 498590, miembro: 161498"]
ROM global? Probablemente nunca. Está destinado al mercado chino.
En cuanto a la ROM de Xiaomi.eu: no tenemos planes de soportarlo.
[/CITAR]

So because in the list of the roms of the miui 10.3, the version my cc9 comes out or is for another model.View attachment 25762
I don't understand your question, but that ROM is for Mi CC9 (pyxis), not Mi CC9mt / Meitu Edition (vela).

A question: if a device actually supported by Beta programm, in a few months will lose this support, the Stable Rom Will continue to be released, so also here with stable Xiaomi EU?
Yes, mostly, unless the Android base version is so old that we choose to drop support for it. Makes our patch development so much easier.
 
Hi @Igor Eisberg in latest stable pie rom 10.4.1 on Mi Note 3 PiP mode is not working correctly - like in previous betas can`t pause, resume etc. Can you patch it and reupload the rom or we have to wait for next stable?
Thanks!
 
Hi @Igor Eisberg in latest stable pie rom 10.4.1 on Mi Note 3 PiP mode is not working correctly - like in previous betas can`t pause, resume etc. Can you patch it and reupload the rom or we have to wait for next stable?
Thanks!
Can't patch something we did not cause, and I don't know what causes this.
 
  • Like
Reactions: werty
greetings
sorry for another poco f1 question just need someone to confirm this
my installed version is 9.2.27 and i noticed and read here that this is the last one for the device (weekly)
my question is i m required to move to a stable to upgrade it to a new stable if or when it comes out?
or i can just forget about that and keep on using the device since i have no issues

thank you for your time
 
Hi, I'm using the .EU stable 10.3.14 on the MI9T (also rooted), the only problem I have is, my Amazon Apps can't be installed, in the original Miui Global Stable is in the Dev-Options the switch 'Miui Optimizations', this switch has to be turned off and the Amazon Apps could be installed, unfortunately this switch is missing in xiaomi.eu 10.3.14. Will this switch be there again in the next Stables?
 
Hi, how is rom 10.3.1.0. for MI8SE?
Right now i am on 10.2.2.0.
And is it possible to make update with TWRP 3.2.3-1217?

Thnx a lot.
 
If I flash this ROM on Mi 9,
Will I still get OTA update? or for every update I have to download and flash that big file?
 
Hi, how is rom 10.3.1.0. for MI8SE?
Right now i am on 10.2.2.0.
And is it possible to make update with TWRP 3.2.3-1217?

Thnx a lot.
You can flash with your twrp version. It is fine in general but is laggy with full screen gestures.

MI 8 SE cihazımdan Tapatalk kullanılarak gönderildi
 
  • Like
Reactions: ToWaRR
I have a Mi Note 3 and I dont understand how come the latest Chinese rom is version V10.3.2.0, and here is 10.4.1.0?
 
Has disappearing status bar icons been fixed in Mi9 10.2 stable release? I'm planning going to stable from beta, but I don't want notification icons to disappear again like they do in latest latest official Xiaomi stable rom. I didn't find anything about this in what's different -list, so I assume that it works like in official rom but just wanted to make sure.
 
Status
Not open for further replies.

Similar threads

  • Locked
HyperOS 1.0 24.3.25
Replies
169
Views
63K
  • Locked
HyperOS 1.0 24.3.18
Replies
115
Views
42K
  • Locked
HyperOS 1.0 24.3.11
Replies
128
Views
44K
  • Locked
HyperOS 1.0 24.3.4
Replies
150
Views
46K