HyperOS 1.0 23.11.27/30


Status
Not open for further replies.
i flashed this apk via adb and give location permission. fine now.




edit: still crashing
11:38
85
Hata Bildirimi
*** *** *** ***
*** ***
Build fingerprint: 'Xiaomi/fuxi/fuxi:13/
TKQ1.221114.001/V816.0.23.11.27.DEV:user/
release-keys'
Revision:'o'
ABl:'arm64'
Timestamp: 2023-12-08 11:37:47.571555374+0300
Process uptime: 23s
Cmdline: com.miui.gallery
pid: 16493, tid: 18574, name: algo-execute#0 >>>
com.miui.gallery <<<
uid:10123
(PR_TAGGED_ADDR_ENABLE)
pac_enabled_ keys: 000000000000000f
(PR_PAC_APIAKEY, PR_PAC_APIBKEY,
PR_PAC_APDAKEY, PR_PAC_APDBKEY)
signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault
addr Ox0000007ac97bb358
xO 0000007b0051e720 x1
0000007b0051da38 x2 0000000000000001
x3 b400007b23769860
x4 0000007b0051e720 x5 0000007afff69eec
x6 fefeffOf607c9b0a x7 7f7f7f7f7f7fff7f
×8 0000007ac97bb358 x9 275df4a469ef521c
x10 000000000000488e x11
0000007ac8fOdObO
x12 0000000000000001 x13
0000000000000001 X14 O0...0000
x15 0000000000010000
x16 0000007ac97d9538 x17
0000007d30f36bcO x18 0000000000000016
x19 0000007b0051da38
x20 0000007b0051db58 x21
0000007b00521000 x22 0000000000000002
x23 0000007b0051e720
x24 0000000000000000 x25
0000007ac97bb198 x26 0000007ac97bb2a8
×27 0000007b0051eae8
x28 0000000000000001 x29
0000007b0051da10
Ir 0000007afff6de34 sp 0000007b0051da10
pc 0000007ac97bb358 pst
0000000000001800
52 total frames
backtrace:
NOTE: Function names and Buildld information is
missing for some frames due
NOTE: to unreadable libraries. For unwinds of
apps, only shared libraries
NOTE: found under the lib/ directory are readable.
NOTE: On this device, run setenforce O to make
the libraries readable.
NOTE: Unreadable libraries:
NOTE: /data/data/com.miui.gallery/app_libs/
libSNPE.so
NOTE:Idata/data/com.miui.gallerylapp_libs/
libmerge_tag.so
NOTE: /data/data/com.miui.gallery/app_libs/
libvideo_analytic.so
#00 pc 000000000089e358 /data/datal
com.miui.gallery/app_libs/libSNPE.so
#01 pc 00000000000eae30 /data/
appl~~JfLBG48DI9m5qiml5YtnOw==/
com.miui.gallery-PDtAV8S6JK17ohsp2Hajw==/
lib/arm64/libc++_shared.so (Buildid:
df3f83af4e54f316c793c3655c4753a8851a234c)
#02 pc 00000000000eab24 /data/
app/~~JfLBG48DI9m5qiml5YtnOw==I
com.miui.gallery-PDtAV8S6JK17ohsp2Hajjw==/
lib/arm64/libc++_shared.so (Buildld:
df3f83af4e54f316c793c3655c4753a8851a234c)
#03 pc 00000000000e713c /data/
app/~~JfLBG48DI9m5qiml5YtnOw==/
com.miui.gallery-PDtAV8S6JK17ohsp2Hajjw==/
lib/arm64/libc++_shared.so (Buildld:
df3f83af4e54f316c793c3655c4753a8851a234c)
#04 pc 00000000000e6fcc Idata/app/~~JfLBG48DI9m5qiml5YtnOw==I
com.miui.gallery-PDtAV8S6JK17ohsp2Hajjw==/
lib/arm64/libc++_shared.so
(_gxx_personality_v0+224) (Buildid:
#05 pc 000000000069a0fO /data/data/
com.miui.gallerylapp_libs/libSNPE.so
#06 pc 000000000069a5f8 /data/data/
com.miui.gallerylapp_libs/libSNPE.so
#07 pc 000000000012c458 /data/data/
com.miui.gallery/app_libs/libSNPE.so
#08 pc 00000000000dOdc4 /data/data/
com.miui.gallerylapp_libs/libSNPE.so
#09 pc 0000000000095bf8 /data/data/
com.miui.gallery/app_libs/libSNPE.so
#10 pc 000000000003f5f0 Idata/data/
com.miui.gallery/app_libs/libmerge_tag.so
#11 pc 000000000003e58c /data/data/
com.miui.gallery/app_libs/libmerge_tag.so
#12 pc 000000000003d3f4 /data/data/
com.miui.gallery/app_libs/libmerge_tag.so
#14 pc 000000000001e0e8 /data/data/
com.miui.gallery/app_libs/libmerge_tag.so
#15 pc 000000000001f9c0 /data/datal
com.miui.gallery/app_libs/libvideo_analytic.so
#16 pc 00000000001cdf00 /data/app/~~JfLBG48DI9m5qiml5YtnOw==/
com.miui.gallery-PDtAV8S6JK17ohsp2Hajjw==/
oat/arm64/base.odex (art_jni_trampoline+128)
#17 pc 00000000006ce670 /
apex/com.android.art/lib64/libart.so
(nterp_helper+4016) (Buildld:
cd335317e87ebac5867205bbee33d6ce)
#18 pc 000000000158a4f0 /data/
app/~~JfLBG48DI9m5qiml5YtnOw==/
com.miui.gallery-PDtAV8S6JK17ohsp2Hajjw==/
oat/arm64/base.vdex (com.xiaomi.player.videoAnal
ytic$VideoTag.init+12)
#19 pc00000000006ce614 /
apex/com.android.art/lib64/libart.so
(nterp_helper+3924) (Buildld:
cd335317e87ebac5867205bbee33d6ce)
#20 pc 000000000158ac32 /datal
app/~~JfLBG48DI9m5qiml5YtnOw==/
com.miui.gallery-PDtAV8S6JK17ohsp2Hajw==/
oat/arm64/base.vdex
(com.xiaomi.player.videoAnalytic.init+90)
21 pc 00000000006ced18 /
apex/com.android.art/lib64/libart.so
(nterp_helper+5720) (Buildld:
cd335317e87ebac5867205bbee33d6ce)
#22 pc 000000000075be72 /data/
app/~~JfLBG48DI9m5qiml5YtnOw==I
com.miui.gallery-PDtAV8S6JK17ohsp2Hajjw==/
oat/arm64/base.vdex
(com.miui.gallery.assistant.algorithm.AnalyticFace
AndSceneAlgorithm.checklnit+306)
#23 pc 00000000006ce614 /
apex/com.android.art/lib64/libart.so
(nterp_helper+3924)(Buildld:
cd335317e87ebac5867205bbee33d6ce)
#24 pc 000000000075c050 /data/
app/~~JfLBG48DI9m5qiml5YtnOw==/
com.miui.gallery-PDtAV8S6JK17ohsp2Hajjw==/
oat/arm64/base.vdex
(com.miui.gallery.assistant.algorithm.AnalyticFace
AndSceneAlgorithm.onlnitAlgorithm+28)
#25 pc 00000000006ce614 /
apex/com.android.art/lib64/libart.so
(nterp_helper+3924) (Buildld:
cd335317e87ebac5867205bbee33d6ce)
#26 pc 000000000075b4aa /data/
app/~~JfLBG48DI9m5qiml5YtnOw==I
com.miui.gallery-PDtAV8S6JK17ohsp2Hajjw==/
oat/arm64/base.vdex (com.miui.gallery.assistant.al
gorithm.Algorithm.init+10)
#27 pc 00000000006ce614 /
apex/com.android.art/lib64/libart.so
(nterp_helper+3924) (Buildld:
cd335317e87ebac5867205bbee33d6ce)
#28 pc 000000000075b91a /datal
app/~~JfLBG48DI9m5qiml5YtnOw==I
com.miui.gallery-PDtAV8S6JK17ohsp2Hajjw==/
oat/arm64/base.vdex
(com.miui.gallery.assistant.algorithm.AlgorithmFa
ctroy.createAlgorithmByFlag+130)
#29 pc 0000000000369640 /
apex/com.android.art/lib64/libart.so
(art_quick_invoke_static_stub+640) (Buildld:
cd335317e87ebac5867205bbee33d6ce)
#30 pc 000000000031afec lapex/
com.android.art/lib64/libart.so (bool
art-:interpreter::DoCall<false>(art::ArtMethod*,
art::Thread*, art::ShadowFrame&, art::lnstruction
const*, unsigned short, bool, art::JValue*)+1016)
(Buildld: cd335317e87ebac5867205bbee33d6ce)
#31 pc 00000000005f5b8c lapex/
com.android.art/lib64/libart.so (void
art-:interpreter::ExecuteSwitchlmplCpp<false>(art
::interpreter::SwitchlmplContext*)+13524) (Buildld:
cd335317e87ebac5867205bbee33d6ce)
#32 pc 00000000003821d8 /
apex/com.android.art/lib64/libart.so
(ExecuteSwitchlmplAsm+8)(Buildld:
cd335317e87ebac5867205bbee33d6ce)
#33 pc 000000000075b98c /data/
app/~~JfLBG48DI9m5qiml5YtnOw==I
com.miui.gallery-PDtAV8S6JK17ohsp2Hajjw==/
oat/arm64/base.vdex (com.miui.gallery.assistant.al
gorithm.AlgorithmFactroy.getAlgorithmByFlag+0)
#34 pc 0000000000349e74 /
apex/com.android.art/lib64/libart.so
(art::interpreter::Execute(art::Thread*,
art::CodeltemDataAccessor const&,
art::ShadowFrame&, art::JValue, bool, bool)
(._uniq.11243541801175191679281975595673257 5238.Ilvm.14359194596130675542)+228) (Buildld:cd335317e87ebac5867205bbee33d6ce)
#35 pc 00000000003496e4 /
apex/com.android.art/lib64/libart.so
(artQuickTolnterpreterBridge+780)(Buildld:
cd335317e87ebac5867205bbee33d6ce)
#36 pc 000000000037fc98 /
apex/com.android.art/lib64/libart.so
(art_quick_to_interpreter_bridge+88) (Buildld:
cd335317e87ebac5867205bbee33d6ce)
#37 pc 00000000006cd758 lapex/
com.android.art/lib64/libart.so (nterp_helper+152)
(Buildld: cd335317e87ebac5867205bbee33d6ce)
#38 pc 0000000000bb6a54 /data/
app/~~JfLBG48DI9m5qiml5YtnOw==/
com.miui.gallery-PDtAV8S6JK17ohsp2Hajjw==/
oat/arm64/base.vdex
(com.miui.gallery.assistant.manager.request.Analy
ticFaceAndSceneRequest.process+96)
#39 pc 00000000006ce614 /
apex/com.android.art/lib64/libart.so
(nterp_helper+3924) (Buildld:
cd335317e87ebac5867205bbee33d6ce)
#40 pc 0000000000bb69d8 /data/
app/~~JfLBG48DI9m5qiml5YtnOw==I
com.miui.gallery-PDtAV8S6JK17ohsp2Hajjw==/
oat/arm64/base.vdex
(com.miui.gallery.assistant.manager.request.Analy
ticFaceAndSceneRequest.process+4)
#41 pc 00000000006ce614 /
apex/com.android.art/lib64/libart.so
(nterp_helper+3924)(Buildld:
cd335317e87ebac5867205bbee33d6ce)
#42 pc 0000000000bb479e /data/
app/~~JfLBG48DI9m5qiml5YtnOw==/
com.miui.gallery-PDtAV8S6JK17ohsp2Hajw==/
oat/arm64/base.vdex (com.miui.gallery.assistant.m
anager.AlgorithmRequest.run+94)
#43 pc 00000000003375cc /data/misc/
apexdata/com.android.art/dalvik-cachelarm64/
boot.oat (java.util.concurrent.ThreadPoolExecutor.
runWorker+716)
#44 pc 0000000000334b18 /data/misc/
apexdata/com.android.art/dalvik-cachelarm64/
boot.oat (java.util.concurrent.ThreadPoolExecutor
$Worker.run+56)
#45 pc 00000000001f7c00 /data/misc/
apexdata/com.android.art/dalvik-cachelarm64/
boot.oat (java.lang.Thread.run+64)
#46 pc 0000000000369374 1
apex/com.android.art/lib64/libart.so
(art_quick_invoke_stub+612) (Buildld:
cd335317e87ebac5867205bbee33d6ce)
#47 pc 0000000000323c10 /
apex/com.android.art/lib64/libart.so
(art::ArtMethod::Invoke(art::Thread*, unsigned
int*, unsigned int, art::JValue*, char const*)+220)
(Buildld: cd335317e87ebac5867205bbee33d6ce)
#48 pc 000000000042d1f4 /
apex/com.android.art/lib64/libart.so
(art::Thread::CreateCallback(void*)+1528)(Buildld:
cd335317e87ebac5867205bbee33d6ce)
#49 pc 000000000042cbec /
apex/com.android.art/lib64/libart.so
(art::Thread::CreateCallbackWithUffdGc(void*)+8)
(Buildld: cd335317e87ebac5867205bbee33d6ce)
#50 pc 00000000000fd134 lapex/
com.android.runtime/lib64/bionic/libc.so
(_pthread_start(void*)+208) (Buildld:
1e3ca19bcae05c01b019c85f3f422e56)
#51 pc 0000000000096ae4 lapex/
com.android.runtime/lib64/bionic/
libc.so (_start_thread+68) (Buildld:
1e3ca19bcae05c01b019c85f3f422e56)
iptal
Gönder
 
Last edited:
Which means it has nothing to do with our ROM.
It was just a reference of previous discussion about LSPosed issues.
But you as a developer are the ones who can point out where it is. As .EU user I can only state that the same test in other AOSP (EvolutionX and LineageOS) did not show any incompatibility with Play Integrity Fix or LSPosed.
Since I'm only using the xiaomi.eu APK patch with your Stable build and it still doesn't work when LSPosed is installed, I would like to how we can handle it?
 
It was just a reference of previous discussion about LSPosed issues.
But you as a developer are the ones who can point out where it is. As .EU user I can only state that the same test in other AOSP (EvolutionX and LineageOS) did not show any incompatibility with Play Integrity Fix or LSPosed.
Since I'm only using the xiaomi.eu APK patch with your Stable build and it still doesn't work when LSPosed is installed, I would like to how we can handle it?
There's absolutely zero connection between LSPosed and that APK, which does nothing except hold data that is read by a system service.
 
Hello all, as i understand with the latest weekly rom there is the issue with the Google Apps, correct?
Can someone maybe describe, how to solve the issue for people which are not so deep in the system? Thx a lot
 
There's absolutely zero connection between LSPosed and that APK, which does nothing except hold data that is read by a system service.
Okay then lets forget the LSPosed it was just my best guess.
I already have a clean install of Stable 14.0.8.0 rebuild v4 (latest) on Poco F3 (alioth), rooted + lsposed with none module enable right now.
The Play Integrity I'm currently using is your APK (Dez, 5) and nothing else. Everything works flawlessly after each reboot but after a few hours the bank apps can detect the root.
It's not the first time I rooted my device and as mentioned none issue happens with same configuration on others android AOSP blends.
It´s not working. How to address it?
 
Hello all, as i understand with the latest weekly rom there is the issue with the Google Apps, correct?
Can someone maybe describe, how to solve the issue for people which are not so deep in the system? Thx a lot
It's not an issue specifically with the Google apps, it's an issue with ART that causes random apps to crash.

Okay then lets forget the LSPosed it was just my best guess.
I already have a clean install of Stable 14.0.8.0 rebuild v4 (latest) on Poco F3 (alioth), rooted + lsposed with none module enable right now.
The Play Integrity I'm currently using is your APK (Dez, 5) and nothing else. Everything works flawlessly after each reboot but after a few hours the bank apps can detect the root.
It's not the first time I rooted my device and as mentioned none issue happens with same configuration on others android AOSP blends.
It´s not working. How to address it?
It's up to Magisk DenyList to hide your rooted state, not the ROM. I don't provide support for root.
 
today the first hyper os dev beta china for the Xiaomi 12 will be launched. Finally, I'm looking forward to using your ROM on the Xiaomi 12.
 
It's not an issue specifically with the Google apps, it's an issue with ART that causes random apps to crash.


It's up to Magisk DenyList to hide your rooted state, not the ROM. I don't provide support for root.
I'm not asking for any root support for my device, just reporting that your injected APK solution doesn't works when the device are rooted with LSPosed and asking you to check.
 
today the first hyper os dev beta china for the Xiaomi 12 will be launched. Finally, I'm looking forward to using your ROM on the Xiaomi 12.
 

Attachments

  • Screenshot_2023-12-08-11-33-09-390_org.telegram.messenger-edit.jpg
    Screenshot_2023-12-08-11-33-09-390_org.telegram.messenger-edit.jpg
    396.4 KB · Views: 290
Maybe things could be related.
Even when latest Stable.eu build installed the LSPosed seems be incompatible with xiaomi.eu - here
That's not my situation, I got K40 (alioth) with latest EU stable with version 14.0.8.0, LSPosed(1.9.2 7024) + ZygiskNext(4-0.8.1) with eu.xiaomi.moudle.inject 12.05 version work well, and my comment come from developer of LSPosed, I don't think they will make mistake with figure out why LSPosed not work with the latest weekly build.
---------------------
I see you have been clarify that is not the problem of EU ROM's. Sorry for replying without knowing what happened last hour;
Let's just expected next ROM will back to that ART one which work well with LSPosed, I already back to 11.19 about one more week.
 
Last edited:
That's not my situation, I got K40 (alioth) with latest EU stable with version 14.0.8.0, LSPosed(1.9.2 7024) + ZygiskNext(4-0.8.1) with eu.xiaomi.moudle.inject 12.05 version work well, and my comment come from developer of LSPosed, I don't think they will make mistake with figure out why LSPosed not work with the latest weekly build.
---------------------
I see you have been clarify that is not the problem of EU ROM's. Sorry for replying without knowing what happened last hour;
Let's just expected next ROM will back to that ART one which work well with LSPosed, I already back to 11.19 about one more week.
You are saying 'I got K40 (alioth) with latest EU stable'. This is not the stable thread - this is the weekly/dev/beta ROM thread.
I wonder if your queries might be better addressed in the Miui 14 Stable release thread?
 
You are saying 'I got K40 (alioth) with latest EU stable'. This is not the stable thread - this is the weekly/dev/beta ROM thread.
I wonder if your queries might be better addressed in the Miui 14 Stable release thread?
So you mean he mentioned me in this thread and I have to go to Stable thread to mention him back with a reply? The core is talking about is ONLY THIS WEEKLY BUILD CAN'T WORK WITH LSPOSED.
 
Is anyone here with Ishtar and Xiaomi Home app CAN'T add a new device?

I bought a new Mi360 Home Security Camera 2K Pro-. And I cant add the camera to my Mi Home.

I tried 30times.. restart and restart.. nothing happen.

I searched my previous phone(Mi9 MIUI12 xiaomi.eu).. and about 2 minutes and the camera is on the internet.

This is very strange. :(

Same Xiaomi Account, same everything, expect the mobile and the ROM.
 
Is anyone here with Ishtar and Xiaomi Home app CAN'T add a new device?

I bought a new Mi360 Home Security Camera 2K Pro-. And I cant add the camera to my Mi Home.

I tried 30times.. restart and restart.. nothing happen.

I searched my previous phone(Mi9 MIUI12 xiaomi.eu).. and about 2 minutes and the camera is on the internet.

This is very strange. :(

Same Xiaomi Account, same everything, expect the mobile and the ROM.
China/Europe Version of the Camera?
I have dual apps. Camera (EU) are running on german server and all other home devices are running through chinese server. No issues on ishtar.
If you connect the camera on the old phone and login on the new, they should be also available on the new one if home has the samw region settings
 
Last edited:
China/Europe Version of the Camera?
I have dual apps. Camera (EU) are running on german server and all other home devices are running through chinese server. No issues on ishtar.
If you connect the camera on the old phone and login on the new, they should be also available on the new one if home has the samw region settings

Europe version

Yes. I connected with old phone, but what could I do if I havent got an old phone?!

Now I see on ishtar the camera. So now it is working, but I dont understand why dont see the ishtar MiHome app the camera for setup...
 
China/Europe Version of the Camera?
I have dual apps. Camera (EU) are running on german server and all other home devices are running through chinese server. No issues on ishtar.
If you connect the camera on the old phone and login on the new, they should be also available on the new one if home has the samw region settings
I also must take sometimes an older phone to connect smart home products ( i run on china and eu server with dual app ) . There is an mi home app where the country server is irrelevant - there you can connect all mi home products on one server. But i do not use it because i do not want to reconnect ( reset ) my smarthome products, i am too lazy for that ☺️
 
I also must take sometimes an older phone to connect smart home products ( i run on china and eu server with dual app ) . There is an mi home app where the country server is irrelevant - there you can connect all mi home products on one server. But i do not use it because i do not want to reconnect ( reset ) my smarthome products, i am too lazy for that ☺️
The sensors are sometimes necessary to reconnect. Also the smoke detektor as the hub had a reconnect issue. Was working fine with Ishtar also strange. But good that it works this way
 
The sensors are sometimes necessary to reconnect. Also the smoke detektor as the hub had a reconnect issue. Was working fine with Ishtar also strange. But good that it works this way
Yes, the smoke detektors ( with hub ) always have a Problem with the connection.
 
Is anyone here with Ishtar and Xiaomi Home app CAN'T add a new device?

I bought a new Mi360 Home Security Camera 2K Pro-. And I cant add the camera to my Mi Home.

I tried 30times.. restart and restart.. nothing happen.

I searched my previous phone(Mi9 MIUI12 xiaomi.eu).. and about 2 minutes and the camera is on the internet.

This is very strange. :(

Same Xiaomi Account, same everything, expect the mobile and the ROM.
You have to turn on precise location for Xiaomi Home App

Settings -> privacy protection -> location -> approximate location TURN ON

After this you can set precise location for Xiaomi Home App (Permissions -> Location)

And try to connect your camera again
 
I don’t know if it can help someone but I had installed the latest version on my Xiaomi 14 Pro, but whenever the Google Play Store opened and updates or a Google app like Chrome was opened, the device would restart. I rolled back to version .17 on the advice of two users, and now everything is okay except for wallet. My 14 pro is only bootloader unlocked non-root.
 
I bought xiaomi 14, don't know if I should cancel?

Will banking apps work here in the UK? Lloyds,starling,natwest etc?? And contact less payments?

Does this xiaomi.eu global rom allow this? Or do I have to stay on China rom?
 
I have problem with app downloaded outside the Play store... it's all about Chinese app like banks, China Unicom, Starbucks, Douyin .... keeps crashing after launching . sometimes I've got message "This app isn't compatible with the latest version of Android". I made update yesterday via fastboot from fuxi V14.0.31 to OS1.0.23.11.27. In V14 my Gpay wasn't working (even with Magisk ) but since I'm in China till Christmas I did't care about it, but now after upgrade I need that essential (in China ) apps. Any idea what to do?
 
Status
Not open for further replies.

Similar threads

  • Locked
HyperOS 1.0 24.5.27
Replies
90
Views
31K
  • Locked
HyperOS 1.0 24.5.13
Replies
198
Views
47K
  • Locked
HyperOS 1.0 24.5.20/21
Replies
76
Views
31K