Question Is there a way to observe whether Intel Bridge Technology works and how it works? I want to find out why a game fails to start on WSA. - Windows 11

I have a surface pro X running Windows 11 ARM64 version but it only has 8GB of RAM. I tried to install a game and play it. After the game is started, it always crashes because there isn't enough memory.
Now I'm trying to install it on my desktop PC and I find it is worse than my surface pro X. It crashed when trying to start!
I read the log from both sides and find out what was happening.
On my SPX, it has something like this so it successfully started up:
Code:
12-17 10:27:12.583 2150 2150 I da1vikvn: ** find native path :/data/app/~~R-xigkqQf-lfITZnwn6meQ==/com.netease.pes-ScXe4Q0r9zt9zNpkgow-tw==/lib/arm64
12-17 10:27:12.584 2150 2150 I da1vikvn: try path /data/app/~~R-xigkqQf-lfITZnwn6meQ==/com.netease.pes-ScXe4Q0r9zt9zNpkgow-tw==/lib/arm/libunisec2.so
12-17 10:27:12.584 2150 2150 I da1vikvn: try path /data/app/~~R-xigkqQf-lfITZnwn6meQ==/com.netease.pes-ScXe4Q0r9zt9zNpkgow-tw==/lib/arm64/libunisec2.so
12-17 10:27:12.585 2150 2150 I da1vikvn: try path /data/user/0/com.netease.pes/app_ntp0/libunisec2.so
12-17 10:27:12.585 2150 2150 I da1vikvn: opt so path /data/user/0/com.netease.pes/app_ntp0/libunisec2.so
12-17 10:27:12.588 2150 2150 I OpenGLRendor: =====>init Native start!!!
On my desktop PC, it has something like this so it failed to start up:
Code:
12-17 02:42:06.745 2035 2035 I da1vikvn: ** find native path :/data/app/~~jyuD0007qWrH6coCzhhp4g==/com.netease.pes--f5miRm7o3vziki2QlCirw==/lib/arm64
12-17 02:42:06.745 2035 2035 I da1vikvn: ** find native path :/data/app/~~jyuD0007qWrH6coCzhhp4g==/com.netease.pes--f5miRm7o3vziki2QlCirw==/lib/arm64
12-17 02:42:06.745 2035 2035 I da1vikvn: running on x86 platform, loading /data/user/0/com.netease.pes/app_ntp0/libunisec_x86.so
12-17 02:42:06.745 2035 2035 I da1vikvn: run on x86 platform, load x86 so!
12-17 02:42:06.757 533 533 I ShellRedirectionHandler: onTaskAppeared taskId: 46
--------- beginning of crash
12-17 02:42:06.757 2035 2035 E AndroidRuntime: FATAL EXCEPTION: main
12-17 02:42:06.757 2035 2035 E AndroidRuntime: Process: com.netease.pes, PID: 2035
12-17 02:42:06.757 2035 2035 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: "/data/user/0/com.netease.pes/app_ntp0/libunisec_x86.so" has unexpected e_machine: 3
Obviously, the reason for the crash is that it detects the WSA on my desktop PC is x86 so it tries to load the x86 version of libunisec and failed.
So why is Intel Bridge Technology not working? Does it mean IBT can only work if a loader loads ARM64 libraries and fail to work if the loader tries to load x86 libraries?
Is there a way to trick da1vikvn so it no longer tries to load x86 so? (By the way, I have no experience in Android App development. I know there is a Dalvik VM. Is this da1vikvn the Dalvik VM or just a similar name thing that the app developer uses?)

If computer's OS architecture is ARM64 then WSA runs ARM64 apps natively: HOUDINI - the ARM-To_Intel-Translator - then isn't used at all.
Take note that WSA is gonna crash as soon as it launches since it reserves 4 GB of RAM for the VM. If you have less than 12 GB RAM then WSA will not flawlessly work.

jwoegerbauer said:
If computer's OS architecture is ARM64 then WSA runs ARM64 apps natively: HOUDINI - the ARM-To_Intel-Translator - then isn't used at all.
Take note that WSA is gonna crash as soon as it launches since it reserves 4 GB of RAM for the VM. If you have less than 12 GB RAM then WSA will not flawlessly work.
Click to expand...
Click to collapse
Thank you.
My desktop PC has 24GB RAM so it should be enough. (I have four 8GB RAMs. Using 3 of them is not a perfect dual-channel RAM solution but I have to use the other one to build another PC)
I'm just wondering whether IBT is designed only for those ARM apps that will never dynamically load libraries based on OS architecture. Or maybe this game is developed too weirdly so IBT failed to handle it?

As I already mentioned: HOUDINI is used to translate ARM64 code to X86_64 code.

Related

[Q] How to get Boot2Gecko working on 2ndROM?

Hi all,
First-time poster and fairly new to rooting...
I have a Samsung Galaxy SII (GT-I9100, originally LBP firmware on Orange UK) which I successfully managed to flash with Odin/Heimdall to give:
CF-Root
CyanogenMod 9 RC1
Siyah 3.3.2
I then thought I'd give Boot2Gecko a try so I followed gokhanmoral's post and managed to get a page not found screen booting to the second rom.
So I checked out the B2G source code and performed a
make install-gaia
Click to expand...
Click to collapse
ensuring
adb devices
Click to expand...
Click to collapse
found my phone connected over usb - This gave me a lock screen which wouldn't respond to touch events.
After quite a bit of reading I then decided to attempt pusler new 6th July Build performing:
simg2img userdata.img data.img
heimdall detect
heimdall flash --hidden system.img
(cleared 2ndROM data and cache through CWM)
adb push data.img /sdcard/.secondrom/data.img
Click to expand...
Click to collapse
However, when I booted to the 2ndROM I gott a black screen - I tried looking through the
adb shell logcat
Click to expand...
Click to collapse
output and saw several errors similar to:
I/GeckoDump( 9894): Opened socket on 9999
E/GeckoConsole( 9894): [JavaScript Error: "NS_ERROR_UNEXPECTED: Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getCharPref]" {file: "chrome://browser/content/shell.js" line: 80}]
I/Gecko ( 9894): Logging GL tracing output to /system/b2g/firefox.trace
I/Gecko ( 9894): Attempting load of /data/local/egltrace.so
F/libc ( 9894): Fatal signal 11 (SIGSEGV) at 0x00000068 (code=1)
I/Gecko ( 9894): Attempting load of libEGL.so
D/libEGL ( 9894): egl.cfg not found, using default config
D/libEGL ( 9894): loaded /system/lib/egl/libGLES_android.so
I/Gecko ( 9894): Failed to create EGL config!
F/libc ( 9894): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1)
I/DEBUG ( 9891): debuggerd committing suicide to free the zombie!
F/libc ( 9847): Fatal signal 13 (SIGPIPE) at 0x00002677 (code=0)
I/DEBUG ( 9978): debuggerd: Jul 6 2012 04:08:21
I/ ( 9979): ServiceManager: 0xf958
V/yamaha::media::CManager( 9979): constructor
Click to expand...
Click to collapse
Seems like a Gecko Chrome error but I can't be sure. As a last ditch effort I tried to follow gokhanmoral's method of extracting/mounting pusler's images, creating tar files and placing them into a CWM flashable zip but Siyah wouldn't recognise the 2ndROM after installing so now I'm all out of ideas.
Has anyone managed to successfully install the 6th July build as a 2ndROM? Any help/info would be appreciated.
Cheers

[Q] Qt4 apps are not working properly (linux chroot), possible shared memory problem?

I'm trying to install linux (Fedora) ARM packages into chroot environment on Android table (rooted). Everything seems to work fine except all of Qt4 applications. Their GUI windows are not displayed properly being luck of most of elements no matter I use android X server or linux VNC server.
Terminal output shows following error messages
Code:
QNativeImage: Unable to attach to shared memory segment.
X Error: BadPixmap (invalid Pixmap parameter) 4
Major opcode: 56 (X_ChangeGC)
Resource id: 0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x0
(and so on).
I suppose the problem is shared memory segment. Either android doesn't support request for it or this segment is too small for Qt4. Is there any solution to enable shared memory?

suspicious shared libs in /system/lib

device is:
ST70208-1
Android Version: 4.1.1
Kernel Version: 3.0.8+
Build: ST70208-1_20130808_INT
aka Trekstor Surftab Ventos 7.0 HD
As Chrome crashes at start even after factory reset and all known measures did not help,
i installed root/su/bussybox/ssh-server and did a logcat.
...
/ActivityManager( 3603): Start proc com.android.chrome:sandboxed_process0 for service com.android.chrome/org.chromium.content.app.SandboxedProcessService0: pid=24769 uid=99001 gids={}
I/LibraryLoader(24750): loading: chromeview
E/Main (24750): Failed to load native library.
E/Main (24750): org.chromium.content.common.ProcessInitException
E/Main (24750): at org.chromium.content.app.LibraryLoader.loadNow(Unknown Source)
E/Main (24750): at com.google.android.apps.chrome.Main$InitializerContinuation.loadLibraryNow(Unknown Source)
E/Main (24750): at com.google.android.apps.chrome.Main$InitializerContinuation.access$400(Unknown Source)
E/Main (24750): at com.google.android.apps.chrome.Main$InitializerContinuation$2.run(Unknown Source)
E/Main (24750): at android.os.Handler.handleCallback(Handler.java:615)
E/Main (24750): at android.os.Handler.dispatchMessage(Handler.java:92)
E/Main (24750): at android.os.Looper.loop(Looper.java:137)
E/Main (24750): at android.os.HandlerThread.run(HandlerThread.java:60)
E/Main (24750): Caused by: java.lang.UnsatisfiedLinkError: Cannot load library: link_image[1891]: 2487 could not load needed library 'libjnigraphics.so' for 'libchromeview.so' (load_library[1093]: Library 'libjnigraphics.so' not found)
E/Main (24750): at java.lang.Runtime.loadLibrary(Runtime.java:370)
E/Main (24750): at java.lang.System.loadLibrary(System.java:535)
E/Main (24750): ... 8 more
E/Trace (24769): error opening trace file: No such file or directory (2)
D/OpenGLRenderer(24750): Enabling debug mode 0
I/SandboxedProcessService(24769): Creating new SandboxedProcessService pid=24769
I/LibraryLoader(24769): loading: chromeview
E/SandboxedProcessService(24769): Failed to load native library, exiting sandboxed process
E/SandboxedProcessService(24769): org.chromium.content.common.ProcessInitException
E/SandboxedProcessService(24769): at org.chromium.content.app.LibraryLoader.loadNow(Unknown Source)
E/SandboxedProcessService(24769): at org.chromium.content.app.SandboxedProcessService$2.run(Unknown Source)
E/SandboxedProcessService(24769): at java.lang.Thread.run(Thread.java:856)
E/SandboxedProcessService(24769): Caused by: java.lang.UnsatisfiedLinkError: Cannot load library: link_image[1891]: 2487 could not load needed library 'libjnigraphics.so' for 'libchromeview.so' (load_library[1093]: Library 'libjnigraphics.so' not found)
E/SandboxedProcessService(24769): at java.lang.Runtime.loadLibrary(Runtime.java:370)
E/SandboxedProcessService(24769): at java.lang.System.loadLibrary(System.java:535)
E/SandboxedProcessService(24769): ... 3 more
..
"ls -al" in /system/lib showed amongst others 4 suspicious shared native libraries:
-rw------- 1 0 0 59996 Mar 17 18:50 libjnigraphics.so
-rw------- 1 0 0 10017928 Mar 17 18:18 libmsrmsdk.so
-rw------- 1 0 0 8577120 Mar 17 18:50 libreader.so
-rw------- 1 0 0 135864 Mar 17 18:51 librss.so
all other libs here look like that:
-rw-r--r-- 1 0 0 31363328 Aug 1 2008 libchromeview.so
The 4 suspects have a date 03/17/2016 and no read permission for group/other but the rest all are 8/1/2008 and have the permissions.
I did "chmod 644" to them.
But i had to remount /system as readwrite.
Seams it is normaly readonly!
And i had to do "su"!
How/Who can change anything here in /system/lib?
Chrom still crashes but logcat shows it is not because it does not find the libjnigraphics.so.
Now it crashes with a dump.
I think it is because libchromeview.so loads the dependency libjnigraphics.so,
but that is an newer version than that it was linked against.
After i left the device in the morning on the day this **** happend, it was working ok.
In the evening (my wife had used it) there was tones of error msg at starting of many apps (Contacts, Playstore, ...).
So i did a factory reset, but the Chrome problem persists (Google+ and Maps where *****y too but worked after update).
I did not switch of auto update.
So i think some update messed it up, or my wife had switched it hard off during something important/longer lasting, as it was not responsive to her.
But how can a normal apk do something to /system?!
Any ideas why Chrome still uses these old native shared libraries?
Please can somebody who is having the same device, send me a "ls -al" of /system/lib.
Any ideas how to fix Chrome (PlayStore)?
Greetings
Michael
PS: This was the 3rd factory reset i had to make because some update managed to screwed it. But the two before worked, ok.
The stock "firmware" of this device looks as if it was the 5th test build a new greenhorn system builder.
And ADB does not work. The device announces itself only in recovery mode to USB (of course "USB debugging" is on).

NoSuchMethodError when running recompiled app

Hi,
Ive decompiled the miui camera (miui 12, Redmi Note 8 Pro) and have recompiled it and included some libs, I have renamed the package and a few permissions (is this the cause of the error?) so as not to cause conflicts with the system camera app. I run into a problem with registerMarshalQueryable.. which from what I can tell is a camera2 method/class, so really it should just be there in the system, unless its looking in the wrong place?
Below is the error
2020-09-06 16:11:26.182 2694-2694/? E/AndroidRuntime: FATAL EXCEPTION: main
Process: com.android.newcamera, PID: 2694
java.lang.NoSuchMethodError: No static method registerMarshalQueryable(Landroid/hardware/camera2/marshal/MarshalQueryableV in class Landroid/hardware/camera2/marshal/MarshalRegistry; or its super classes (declaration of 'android.hardware.camera2.marshal.MarshalRegistry' appears in /system/framework/framework.jar)
at com.android.camera2.vendortag.struct.MarshalQueryableRegister.preload(MarshalQueryableRegister.java:1)
at com.android.camera.CameraAppImpl.onCreateApplicationDelegate(CameraAppImpl.java:11)
at com.android.camera.CameraAppImpl.onCreateApplicationDelegate(CameraAppImpl.java:1)
at miui.external.Application.attachBaseContext(Application.java:4)
at android.app.Application.attach(Application.java:376)
at android.app.Instrumentation.newApplication(Instrumentation.java:1156)
at android.app.LoadedApk.makeApplication(LoadedApk.java:1222)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6562)
at android.app.ActivityThread.access$1500(ActivityThread.java:230)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1911)
at android.os.Handler.dispatchMessage(Handler.java:107)
at android.os.Looper.loop(Looper.java:224)
at android.app.ActivityThread.main(ActivityThread.java:7551)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:539)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:995)
Click to expand...
Click to collapse

Question Official miui camera app

I've installed Lineage OS on the Mi MIX 4 and I cannot be happier after getting rid of MIUI, but now I'm left without a proper camera app. I installed GCAM but not everything works at the moment.
I would like to try to install the official MIUI camera app and see if by any chance it works, but I forgot to extract the apk before flashing Lineage OS.
Can someone who has MIUI installed upload the apk in this thread, or know where I can get it? For example using an extractor like this one:
Apk Extractor - Apps on Google Play
Extracts installed applications on your device and places them on your SD card.
play.google.com
Thanks a lot!
You can find the Xiaomi Camera apk on apkmirror.
Let us know if this works!
Aleksanderbjorn said:
You can find the Xiaomi Camera apk on apkmirror.
Let us know if this works!
Click to expand...
Click to collapse
Thanks for the suggestion! Unfortunately, it crashes on launch (I installed this one).
Stacktrace:
Spoiler: Stacktrace
Code:
2022-03-17 08:03:05.314 31800-31800/? D/MiCameraAlgo: init: E
2022-03-17 08:03:05.314 31800-31800/? D/MiCameraAlgo: init: application file path to algorithm lib: /data/user/0/com.android.camera/files
2022-03-17 08:03:05.314 31800-31800/? E/MiCamAlgoInterfaceJNI: start loading camera_algoup_jni.xiaomi
2022-03-17 08:03:05.316 31800-31800/? E/MiCamAlgoInterfaceJNI: can not load library:camera_algoup_jni.xiaomi : java.lang.UnsatisfiedLinkError: dlopen failed: library "libcamera_algoup_jni.xiaomi.so" not found
at java.lang.Runtime.loadLibrary0(Runtime.java:1087)
at java.lang.Runtime.loadLibrary0(Runtime.java:1008)
at java.lang.System.loadLibrary(System.java:1664)
at com.xiaomi.engine.MiCamAlgoInterfaceJNI.<clinit>(MiCamAlgoInterfaceJNI.java:3)
at com.xiaomi.engine.MiCamAlgoInterfaceJNI.init(Native Method)
at com.xiaomi.engine.MiCameraAlgo.init(MiCameraAlgo.java:4)
at com.android.camera.LocalParallelService$LocalBinder.initMiviEngine(LocalParallelService.java:4)
at com.android.camera.LocalParallelService$LocalBinder.<init>(LocalParallelService.java:9)
at com.android.camera.LocalParallelService.onCreate(LocalParallelService.java:5)
at android.app.ActivityThread.handleCreateService(ActivityThread.java:4186)
at android.app.ActivityThread.access$1500(ActivityThread.java:237)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1932)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:223)
at android.app.ActivityThread.main(ActivityThread.java:7664)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
2022-03-17 08:03:05.316 31800-31800/? E/.android.camer: No implementation found for int com.xiaomi.engine.MiCamAlgoInterfaceJNI.init(java.lang.String) (tried Java_com_xiaomi_engine_MiCamAlgoInterfaceJNI_init and Java_com_xiaomi_engine_MiCamAlgoInterfaceJNI_init__Ljava_lang_String_2)
2022-03-17 08:03:05.316 31800-31800/? D/AndroidRuntime: Shutting down VM
2022-03-17 08:03:05.316 813-31855/? E/CamX: [ERROR][SENSOR ] camximagesensordata.cpp:1635 GetI2CCmdSizeForEarlySetting() EarlySettingFunc total size = 536
2022-03-17 08:03:05.316 31800-31800/? E/AndroidRuntime: FATAL EXCEPTION: main
Process: com.android.camera, PID: 31800
java.lang.UnsatisfiedLinkError: No implementation found for int com.xiaomi.engine.MiCamAlgoInterfaceJNI.init(java.lang.String) (tried Java_com_xiaomi_engine_MiCamAlgoInterfaceJNI_init and Java_com_xiaomi_engine_MiCamAlgoInterfaceJNI_init__Ljava_lang_String_2)
at com.xiaomi.engine.MiCamAlgoInterfaceJNI.init(Native Method)
at com.xiaomi.engine.MiCameraAlgo.init(MiCameraAlgo.java:4)
at com.android.camera.LocalParallelService$LocalBinder.initMiviEngine(LocalParallelService.java:4)
at com.android.camera.LocalParallelService$LocalBinder.<init>(LocalParallelService.java:9)
at com.android.camera.LocalParallelService.onCreate(LocalParallelService.java:5)
at android.app.ActivityThread.handleCreateService(ActivityThread.java:4186)
at android.app.ActivityThread.access$1500(ActivityThread.java:237)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1932)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:223)
at android.app.ActivityThread.main(ActivityThread.java:7664)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
2022-03-17 08:03:05.317 31800-31800/? E/CAM_CameraFCHandler: Camera FC, @Module = 163 And @CameraId = 0
2022-03-17 08:03:05.317 31800-31800/? E/CAM_MqsHelper: [K_PROCESS]: Error occur the reason is that CameraApp Mode:Photo[163] CameraId:0 Error:Java Crash
2022-03-17 08:03:05.318 31800-31800/? D/CAM_AfterSales: aftersales record not enable in this device
2022-03-17 08:03:05.318 31800-31800/? E/CAM_CameraFCHandler: Camera FC, msg=No implementation found for int com.xiaomi.engine.MiCamAlgoInterfaceJNI.init(java.lang.String) (tried Java_com_xiaomi_engine_MiCamAlgoInterfaceJNI_init and Java_com_xiaomi_engine_MiCamAlgoInterfaceJNI_init__Ljava_lang_String_2)
java.lang.UnsatisfiedLinkError: No implementation found for int com.xiaomi.engine.MiCamAlgoInterfaceJNI.init(java.lang.String) (tried Java_com_xiaomi_engine_MiCamAlgoInterfaceJNI_init and Java_com_xiaomi_engine_MiCamAlgoInterfaceJNI_init__Ljava_lang_String_2)
at com.xiaomi.engine.MiCamAlgoInterfaceJNI.init(Native Method)
at com.xiaomi.engine.MiCameraAlgo.init(MiCameraAlgo.java:4)
at com.android.camera.LocalParallelService$LocalBinder.initMiviEngine(LocalParallelService.java:4)
at com.android.camera.LocalParallelService$LocalBinder.<init>(LocalParallelService.java:9)
at com.android.camera.LocalParallelService.onCreate(LocalParallelService.java:5)
at android.app.ActivityThread.handleCreateService(ActivityThread.java:4186)
at android.app.ActivityThread.access$1500(ActivityThread.java:237)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1932)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:223)
at android.app.ActivityThread.main(ActivityThread.java:7664)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
Looks like the apk only works on MIUI... Try ANXCamera, must be installed through Magisk or TWRP.
Aleksanderbjorn said:
Looks like the apk only works on MIUI... Try ANXCamera, must be installed through Magisk or TWRP.
Click to expand...
Click to collapse
Nice suggestion, thanks again.
I've tried the different builds for Android 11 via TWRP and all of them hang during installation, the phone is also not yet listed as officially supported.
If I manage to make it work somehow I will post it in this thread (also if I find any other good alternative).
At the moment only GCAM works, but not fully.
xatok said:
Nice suggestion, thanks again.
I've tried the different builds for Android 11 via TWRP and all of them hang during installation, the phone is also not yet listed as officially supported.
If I manage to make it work somehow I will post it in this thread (also if I find any other good alternative).
At the moment only GCAM works, but not fully.
Click to expand...
Click to collapse
I have also tried with multiple ANXCamera combinations - none work :/ It installs OK but the camera view is black

Categories

Resources