I know one of the great points on Z line is the quite untouched Google ROM. MIUI is my favorite customized ROM by manufacturer.
So, why don't give a option to use both? Will you like my idea and will use it?
Thanks for your opinion.
Enviado de meu XT1650 usando Tapatalk
Totally. I don't know if I would use it as my daily since I'm a flashaholic, but will try it for days/weeks depending on how smooth/stable it is. I've had some nice experiences before, so I'm having high hopes on this.
Not bad idea, go for it, i really like MIUI
The only problem is that my Bootloader is upgraded, so I cannot test since MIUI isn't in 7.0 version. I will wait for MIUI 9 because of that, because develop a port that the developer cannot test isn't a good idea in my view
Enviado de meu XT1650 usando Tapatalk
andregarcia_1 said:
I know one of the great points on Z line is the quite untouched Google ROM. MIUI is my favorite customized ROM by manufacturer.
So, why don't give a option to use both? Will you like my idea and will use it?
Thanks for your opinion.
Enviado de meu XT1650 usando Tapatalk
Click to expand...
Click to collapse
Hey last month i started to port MIUI8.2 7.0 from Mi5 firmware to our device and i had some progress
i'm not with my PC for a month, i thought to share my work for interested devs
here's my ROM and superR kitchain Project FIles : Download Folder
it's Not Booting (Do NOT INSTALL if you are NOT Dev)
here's Error Log : Unable to open socket for UEventObserver
it Happens Because of NetLink Socket Opening. I couldn't fix this (tried netd, ipacm & iptables), someone smarter than me should take a look. i don't know what i missed (probably it's kernel side)
i really like MIUI i'll appreciate if you have look
Notes :
+ this rom has 6.0.1 moto Kernel so it's not booting on new bootloaders. and when i updated to 7.0 kernel(and dt) i got this error crashes surfaceflinger while booting:
Code:
Adreno-GSL: <ioctl_kgsl_driver_entry:562>: open(/dev/kgsl-3d0) failed: errno 5. I/O error
No idea why!
+ all blobs(except apps) taken from here and ipacm from here
+ selinux files is compiled from cm14.0 source with needed permissions on griffin device tree
+ adbd is starting on init at init.rc to debug and shell access on bootloops just replace "adb_keys" if adb needs permissions
+ i replaced all needed HALs and ETC folder files
+ if you have any Questions PM me
If someone can do the port is going to be excellent, I'm waiting.
sam564 said:
If someone can do the port is going to be excellent, I'm waiting.
Click to expand...
Click to collapse
+1
++1
+1
1+:good:
Is this project still in the works? I'd love to use this!
+1
I wan MIUI too.
Hello again guys
today i just wanted to play with treble and CLT so i decided to boot MIUI from leaked oreo 8.1 firmware : https://www.xda-developers.com/xiaomi-redmi-note-5-pro-android-oreo-stable/
and after all it's booted on griffin
i'll upload my twrp backup from system partition
bugs : very very unstable :
* for boot need to enter "wificond" in adb shell and to get adb access you need run this command on adb shell from twrp : "cd ~/.android && adb push adbkey.pub /data/misc/adb/adb_keys"
* wifi broken
* ril broken
* camera broken
whats working :
* few things like BT and sensors ...
twrp backup : https://www.androidfilehost.com/?fid=890129502657599583
flash lineage
restore backup
flash premssiver.zip
---------------------------------------------------
how is it booted?
i'm going to explain from beginning, porting it is not very hard
got leaked miui and latest lineage and started CLT on it
then i got miui with griffin vendor inside
flashed on device with clean (not magisked) boot.img from lineage
and enabled premissive selinux
edited prop.default and build.prop to remove device specific props and enabled adb + pm.dexopt (see props.zip)
build.prop for /system/
and prop.default for /system/etc/
>>> First try to boot failed by rebooting to bootloader
by generating multiple times the spammy console-remoops, finally i found out reboots because of selinux problems
i didn't want to mess with it so i directly adb pushed lineage /system/etc/selinux dir to my device
>>> booted to bootanimation
here i got huge errors as usual
/bin/keystore was looking for vendor.qti.hardware.wifi.keystore...._vendor.so and we don't have it because that miui rom is built from full CAF source and we are using aosp keystore in lineage so i replaced it with lineage /bin/keystore
wificond had missing symbol which is coming from qsap_sdk so i just replaced miui wificond with lineage one
and cameraserver is spamming here
>>> nothing much same on bootanimation
now zygote dies because can't find power_profile.xml in res/xml
actually this miui is not enabled RRO in that build so theres no framework-res__auto_generated_rro.apk in vendor, everything is on system framework-res.apk
so i removed my framework-res__auto_generated_rro.apk
need to wipe data
>>> failed again
libstagefright had some issues
i replaced it with lineage one with some other media libs (sorry i don't remember names)
>>> i guess booted this time :fingers-crossed: but soft reboots on setupwizard on trying to search for wifis with this error:
Code:
04-23 11:04:56.499 893 1505 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: WifiScanningService
04-23 11:04:56.499 893 1505 E AndroidRuntime: java.lang.IllegalArgumentException
04-23 11:04:56.499 893 1505 E AndroidRuntime: at android.os.BinderProxy.transactNative(Native Method)
04-23 11:04:56.499 893 1505 E AndroidRuntime: at android.os.BinderProxy.transact(Binder.java:767)
04-23 11:04:56.499 893 1505 E AndroidRuntime: at android.net.wifi.IWifiScannerImpl$Stub$Proxy.scan(IWifiScannerImpl.java:310)
04-23 11:04:56.499 893 1505 E AndroidRuntime: at com.android.server.wifi.WificondControl.scan(WificondControl.java:600)
04-23 11:04:56.499 893 1505 E AndroidRuntime: at com.android.server.wifi.WifiNative.scan(WifiNative.java:351)
04-23 11:04:56.499 893 1505 E AndroidRuntime: at com.android.server.wifi.scanner.WificondScannerImpl.processPendingScans(WificondScannerImpl.java:452)
04-23 11:04:56.499 893 1505 E AndroidRuntime: at com.android.server.wifi.scanner.WificondScannerImpl.startSingleScan(WificondScannerImpl.java:203)
04-23 11:04:56.499 893 1505 E AndroidRuntime: at com.android.server.wifi.scanner.HalWifiScannerImpl.startSingleScan(HalWifiScannerImpl.java:78)
04-23 11:04:56.499 893 1505 E AndroidRuntime: at com.android.server.wifi.scanner.WifiScanningServiceImpl$WifiSingleScanStateMachine.tryToStartNewScan(WifiScanningServiceImpl.java:851)
04-23 11:04:56.499 893 1505 E AndroidRuntime: at com.android.server.wifi.scanner.WifiScanningServiceImpl$WifiSingleScanStateMachine$DriverStartedState.processMessage(WifiScanningServiceImpl.java:650)
04-23 11:04:56.499 893 1505 E AndroidRuntime: at com.android.internal.util.StateMachine$SmHandler.processMsg(StateMachine.java:992)
04-23 11:04:56.499 893 1505 E AndroidRuntime: at com.android.internal.util.StateMachine$SmHandler.handleMessage(StateMachine.java:809)
04-23 11:04:56.499 893 1505 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
04-23 11:04:56.499 893 1505 E AndroidRuntime: at android.os.Looper.loop(Looper.java:164)
04-23 11:04:56.499 893 1505 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:65)
you can stop rebooting by entering "wificond" in adb shell
now setupwizard after sim detect stops with black screen
---
in logs we can see it's looking for 2 services miui.shell and miui.fdpp :silly:
they have some ramdisk scripts related to miui in boot.img but all we need is init.miui.rc
import it in your init.qcom.rc and add to /vendor/etc/init/hw/
almost done but you need to clear file_contexts of this 2 bin because we're using lineage sepolicies : /system/xbin/shelld and /system/bin/fdpp
>>> setupwizard goes further
but i couldn't finish it so simply removed it from /priv-app
booted but system is not very usable
so i took this TWRP backup and tried flashing gapps
finished setupwizard
and restored backup
>>> now miui is fully booted
i don't know any better way to bypass setupwizard
Wow,,MIUI coming.. :victory::victory:
I love you man!
@erfanoabdi,. You working on miui?
rakee said:
@erfanoabdi,. You working on miui?
Click to expand...
Click to collapse
No i just did it for my treble testing and actually fun
Maybe after release of one official miui with Android 8.1 i can start working on it
erfanoabdi said:
No i just did it for my treble testing and actually fun
Maybe after release of one official miui with Android 8.1 i can start working on it
Click to expand...
Click to collapse
MIUI from leaked oreo 8.1 firmware is already quite stable, right?
https://www.xda-developers.com/xiaomi-mi-6x-china-dual-cameras-snapdragon-660/ @erfanoabdi
Its MIUI 9.5 on top of Android 8.1 Oreo
I cannot download any files on my Le Max 2 x829 EUI 5.8.016S.
Here is the logcat. I rooted and uninstalled LeShare app (which seems like what is crashing) so I did a Nandroid restore and the problem still exists. When I wiped I removed everything besides internal storage but still have the problem.
06-30 14:48:32.885 8953-8953/? E/ActivityThread: Failed to find provider info for com.android.leShare
06-30 14:48:32.887 8953-8953/? E/ActivityThread: Failed to find provider info for com.android.leShare
--------- beginning of crash
06-30 14:48:32.889 8953-8953/? E/AndroidRuntime: FATAL EXCEPTION: main
Process: system:ui, PID: 8953
java.lang.IllegalArgumentException: Unknown URL content://com.android.leShare/leShareTable
at android.content.ContentResolver.insert(ContentResolver.java:1230)
at com.android.internal.app.ResolverActivity.insertDB(ResolverActivity.java:2581)
at com.android.internal.app.ResolverActivity.getClickCounts(ResolverActivity.java:2600)
at com.android.internal.app.ResolverActivity.insertCounts(ResolverActivity.java:2640)
at com.android.internal.app.ResolverActivity.startSelected(ResolverActivity.java:789)
at com.android.internal.app.ResolverActivity$11.onClick(ResolverActivity.java:2470)
at android.view.View.performClick(View.java:5226)
at android.view.View$PerformClick.run(View.java:21350)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:148)
at android.app.ActivityThread.main(ActivityThread.java:5571)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
Does anyone know how to fix it? Thanks.
Update your 16S rom, we are in 2017
Enviado desde mi LEX820 mediante Tapatalk
UPDATE: Solved the issue. Click here to see the solution.
I have no clue what happened, but every time I try to load the camera, the system freezes. The camera can't be opened anywhere.
I've used TWRP, etc, for a long time, no problems. I decided to try the LOS17 ROM, and now I can't get the camera to load no matter what I do. I've even reset the phone using LGUP and installing the KDZs, to no avail.
Currently, it's showing Kernel Version 4.4.78 on Software US99820a. Regardless of where I try to use the camera, it freezes the entire phone completely. About to have a panic attack. Any way I can get this back?
hellodmo said:
I have no clue what happened.
I've used TWRP, etc, for a long time, no problems. I decided to try the LOS17 ROM, and now I can't get the camera to load no matter what I do. I've even reset the phone using LGUP and installing the KDZs, to no avail.
Currently, it's showing Kernel Version 4.4.78 on Software US99820a. Regardless of where I try to use the camera, it freezes the entire phone completely. About to have a panic attack. Any way I can get this back?
Click to expand...
Click to collapse
You've Master Reset and used REFURBISH mode using the new Dev Patched LGUP?
Why 20a? Why not 20h, most recent?
ChazzMatt said:
You've Master Reset and used REFURBISH mode using the new Dev Patched LGUP?
Why 20a? Why not 20h, most recent?
Click to expand...
Click to collapse
I originally tried 20h, and it locked the phone up when trying to load the camera. Originally, I had all sorts of LG IMS has stopped errors after using the standard TWRP restore, AND the camera didn't load, so I decided to restore 20h. I tried that, and the LG IMS issue went away, but the camera didn't work. So now I'm doing 20a->20f->20h in order to see if that restores. I'll be done with that in a few minutes.
I have no idea why this would have happened, and why the TWRP restore didn't work immediately. The TWRP install of LOS17 changed something that doesn't seem to be recoverable, and I have no clue how....
Still not working. Just freezes. Every. Single. Time.
20a->20f->20h with master resets all around, etc. I'm stumped.
hellodmo said:
Still not working. Just freezes. Every. Single. Time.
20a->20f->20h with master resets all around, etc. I'm stumped.
Click to expand...
Click to collapse
You updated to Pie blobs and now are trying to downgrade back to Oreo.
Are you trying to use TWRP flashable zips?
You need to use Refurbish mode KDZ. Then Master Reset. You can use 20h.
Which dev patched LGUP are you using? Use the newer one from the Pie KDZ threads, like here:
https://forum.xda-developers.com/showpost.php?p=79971595&postcount=3
You will still have unlocked bootloader, but you'll lose TWRP. You'll need to then reinstall TWRP and the three root files. For that go by these instructions, even though you are back on Oreo. Ignore that it says you are on Pie. Use those newer encryption disabler files and the newer root check files.
https://forum.xda-developers.com/lg-v30/how-to/wtf-lg-v30-t3790500/post79972584#post79972584
Still doesnt work. Wondering if the rom somehow fried the hardware....
hellodmo said:
Still doesnt work. Wondering if the rom somehow fried the hardware....
Click to expand...
Click to collapse
Then try Partition DL with all partitions.
Please answer the question -- are you using the new Dev Patched LGUP?
Don't try to reinstall TWRP and root yet. Make sure the camera is back working on full stock firmware first.
Yes. Patched LGUP. Got some company over, but ill try the DL partitions later
hellodmo said:
Yes. Patched LGUP. Got some company over, but ill try the DL partitions later
Click to expand...
Click to collapse
Okay, did the DL Partitions (our low-maintenance friends are awesome), but it still didn't do much. I'll hook it up to ADB soon. Looks like there may be a problem accessing some SQLite Log database, and I'm wondering if it's related....
If you have any other ideas at the moment, let me know. The same behavior persisted. The camera won't open and load.
hellodmo said:
Okay, did the DL Partitions (our low-maintenance friends are awesome), but it still didn't do much. I'll hook it up to ADB soon. Looks like there may be a problem accessing some SQLite Log database, and I'm wondering if it's related....
If you have any other ideas at the moment, let me know. The same behavior persisted. The camera won't open and load.
Click to expand...
Click to collapse
Should I master reset after doing DL partitions?
@SGCMarkus Curious if you have any clue what's going on here. Did a search for one of the issues I was having and came across your github.
https://gist.github.com/SGCMarkus/baf1ee39715259489c02243c97598f9f
Noticing alot of missing libraries, it seems like. Wondering if there's a way to replace them....
HTML:
09-22 18:59:35.349 1704 1734 I CameraManagerGlobal: Connecting to camera service
09-22 18:59:35.349 1704 1734 E CameraManagerGlobal: Camera service is unavailable
09-22 18:59:35.349 25917 25917 I mm-camera: <ISP ><I> 4069: isp_resource_get_isp_hw_limit: isp hw limit 0
09-22 18:59:35.405 25917 25917 I mm-camera: <ISP ><I> 4069: isp_resource_get_isp_hw_limit: isp hw limit 0
09-22 18:59:35.435 25917 25917 I mm-camera: <ISP ><I> 960: module_isp_init: module 0xdea98a60
09-22 18:59:35.454 25917 25917 I mm-camera: <CPP ><I> 174: cpp_module_init: info: CPP module_init successful
09-22 18:59:35.465 25917 25917 E mm-camera: <IMGLIB><E> 1348: frameproc_comp_reload_lib: Error opening frameproc library libmmcamera_llvd.so error dlopen failed: library "libllvd_smore.so" not found
09-22 18:59:35.465 25917 25917 E mm-camera: <IMGLIB><E> 1214: frameproc_comp_load: frameproc_comp_load:1214] cannot load libmmcamera_llvd.so
09-22 18:59:35.465 25917 25917 E mm-camera: <IMGLIB><E> 3542: module_imgbase_init: llvd] Error rc -7
09-22 18:59:35.468 25917 25917 E mm-camera: <IMGLIB><E> 2023: multi_frameproc_core_reload_lib: Error opening multi_frameproc library libmmcamera_sac_lib.so error dlopen failed: library "libmmcamera_sac_lib.so" not found
09-22 18:59:35.468 25917 25917 E mm-camera: <IMGLIB><E> 2153: multi_frameproc_core_load: cannot load libmmcamera_sac_lib.so status -7
09-22 18:59:35.468 25917 25917 E mm-camera: <IMGLIB><E> 3542: module_imgbase_init: sat] Error rc -7
09-22 18:59:35.468 25917 25917 E mm-camera: <IMGLIB><E> 4056: module_qdc_common_init: mct module 0x0
09-22 18:59:35.469 25917 25917 E mm-camera: <IMGLIB><E> 2023: multi_frameproc_core_reload_lib: Error opening multi_frameproc library libmmcamera_bokeh_oem.so error dlopen failed: library "libmmcamera_bokeh_oem.so" not found
09-22 18:59:35.470 25917 25917 E mm-camera: <IMGLIB><E> 2153: multi_frameproc_core_load: cannot load libmmcamera_bokeh_oem.so status -7
09-22 18:59:35.470 25917 25917 E mm-camera: <IMGLIB><E> 3542: module_imgbase_init: sac] Error rc -7
09-22 18:59:35.470 25917 25917 E mm-camera: <IMGLIB><E> 4056: module_qdc_common_init: mct module 0x0
09-22 18:59:35.471 25917 25917 E mm-camera: <IMGLIB><E> 4082: module_qdc_common_init: Algo Capabilities Crop caps 0,core type 0, access mode 0, exec mode 0
09-22 18:59:35.480 25917 25917 E mm-camera: <IMGLIB><E> 4082: module_qdc_common_init: Algo Capabilities Crop caps 2,core type 1, access mode 1, exec mode 3
09-22 18:59:35.486 25917 25917 I mm-camera: <IMGLIB><I> 2157: faceproc_sw_wrapper_load: Loading faceproc library
09-22 18:59:35.491 25917 25917 W mm-camera: <IMGLIB><W> 1235: faceproc_dsp_comp_load: face detection dsp disabled , enable by set property
09-22 18:59:35.521 25917 25917 E mm-camera: <IMGLIB><E> 1348: frameproc_comp_reload_lib: Error opening frameproc library libmmcamera_ubifocus_lib.so error dlopen failed: library "libmmcamera_ubifocus_lib.so" not found
09-22 18:59:35.521 25917 25917 E mm-camera: <IMGLIB><E> 1214: frameproc_comp_load: frameproc_comp_load:1214] cannot load libmmcamera_ubifocus_lib.so
09-22 18:59:35.521 25917 25917 E mm-camera: <IMGLIB><E> 3542: module_imgbase_init: imglib_ubifocus] Error rc -7
09-22 18:59:35.522 25917 25917 W mm-camera: <IMGLIB><W> 748: module_imglib_create_topology: Can not init the module imglib_ubifocus
09-22 18:59:35.522 25917 25917 E mm-camera: <IMGLIB><E> 1348: frameproc_comp_reload_lib: Error opening frameproc library libmmcamera_ubifocus_lib.so error dlopen failed: library "libmmcamera_ubifocus_lib.so" not found
09-22 18:59:35.522 25917 25917 E mm-camera: <IMGLIB><E> 1214: frameproc_comp_load: frameproc_comp_load:1214] cannot load libmmcamera_ubifocus_lib.so
09-22 18:59:35.522 25917 25917 E mm-camera: <IMGLIB><E> 3542: module_imgbase_init: imglib_refocus] Error rc -7
09-22 18:59:35.522 25917 25917 W mm-camera: <IMGLIB><W> 748: module_imglib_create_topology: Can not init the module imglib_refocus
09-22 18:59:35.543 25917 25917 W mm-camera: <IMGLIB><W> 748: module_imglib_create_topology: Can not init the module imglib_oem1
hellodmo said:
Should I master reset after doing DL partitions?
Click to expand...
Click to collapse
Doesn't hurt, may help.
It seems like there's some kind of vendor file that might be corrupted. I may be asking for a file or two in a bit. I'll likely root it so I can access the file system properly in a non-readonly mode. Can't hurt it any worse at this point, unfortunately.
A master reset following Partition DL didn't do anything.
So it looks like I'm missing a few files.
Code:
09-22 21:12:30.213 3763 3763 E mm-camera: <IMGLIB><E> 1348: frameproc_comp_reload_lib: Error opening frameproc library libmmcamera_llvd.so error dlopen failed: library "libllvd_smore.so" not found
09-22 21:12:30.216 3763 3763 E mm-camera: <IMGLIB><E> 2023: multi_frameproc_core_reload_lib: Error opening multi_frameproc library libmmcamera_sac_lib.so error dlopen failed: library "libmmcamera_sac_lib.so" not found
09-22 21:12:30.217 3763 3763 E mm-camera: <IMGLIB><E> 2023: multi_frameproc_core_reload_lib: Error opening multi_frameproc library libmmcamera_bokeh_oem.so error dlopen failed: library "libmmcamera_bokeh_oem.so" not found
09-22 21:12:30.266 3763 3763 E mm-camera: <IMGLIB><E> 1348: frameproc_comp_reload_lib: Error opening frameproc library libmmcamera_ubifocus_lib.so error dlopen failed: library "libmmcamera_ubifocus_lib.so" not found
09-22 21:12:30.267 3763 3763 E mm-camera: <IMGLIB><E> 1348: frameproc_comp_reload_lib: Error opening frameproc library libmmcamera_ubifocus_lib.so error dlopen failed: library "libmmcamera_ubifocus_lib.so" not found
@ChazzMatt Would it be possible to extract those and attach them here? I'm thinking if I add them to the lib folder, perhaps it'll maybe, possibly, fix the underlying issue....
It looks like they're located under /system/vendor/lib....
Okay, managed to get it working again. My guess is that there's something in the Nougat KDZ that sets up the camera, that might have been affected by something in the LOS17 ROM. tldr; I had to restore the US99810c KDZ file to get the camera to work again, and then I finished the rest of the steps to get everything in order again. Here's the complete breakdown of what I did, step by step. Some of these may be redundant to fix the issue, but I'm including them anyways.
Flash US99810C through Patched LGUP. <-- This is what gave me the camera back. The camera worked in Nougat, so I started flashing the oreo roms.
Flashed US99820A through Patched LGUP. <-- Did this for unlock and TWRP install.
Boot into system. Unlock developer tools. Turn on USB Debugging, and start debugging.
adb reboot bootloader
fastboot flash recovery TWRP.img
fastboot boot TWRP.img
Swipe to allow modifications.
Wipe/Format.
Reboot to Recovery.
Restore previous working backup.
Boot to system - No sound. (I've been here before.)
Flash US99820F to fix sound.
Wipe.
Boot to system. Go through the setup. Verify sound capabilities.
Restore to previous working backup.
Clear Cache and Dalvik.
Boot into system. Verify camera and sound. Rock and Roll.
Say I'll never install another custom ROM again, but know I'm lying to myself, and I'll probably take this not as a warning, but as a confidence builder, which explains why I'm a software developer to begin with.
Happens with the stock MIUI Dialler as well as Google Dialler. I can't find anything wrong in settings, and a reflash didn't help. Never had this problem on stock global MIUI.
java.lang.NullPointerException: Attempt to invoke virtual method 'int android.os.Bundle.getInt(java.lang.String, int)' on a null object reference
at com.android.incallui.aiassistant.AiAssistantUtil.getAiVersionCode(Unknown Source:19)
at com.android.incallui.aiassistant.AiAssistantUtil.supportAi(Unknown Source:0)
at com.android.incallui.aiassistant.AiAssistantUtil.getAiStatus(Unknown Source:9)
at com.android.incallui.CallCardPresenter.updateSingleDisplayInfo(Unknown Source:238)
at com.android.incallui.CallCardPresenter.handleCallCardViewByCallCardState(Unknown Source:40)
at com.android.incallui.CallCardPresenter.updateInfoByState(Unknown Source:24)
at com.android.incallui.CallCardPresenter.onStateChange(Unknown Source:403)
at com.android.incallui.CallCardPresenter.init(Unknown Source:79)
at com.android.incallui.CallCardFragment.onActivityCreated(Unknown Source:17)
at android.app.Fragment.performActivityCreated(Unknown Source:13)
at android.app.FragmentManagerImpl.moveToState(Unknown Source:631)
at android.app.FragmentManagerImpl.addAddedFragments(Unknown Source:46)
at android.app.FragmentManagerImpl.executeOpsTogether(Unknown Source:129)
at android.app.FragmentManagerImpl.removeRedundantOperationsAndExecute(Unknown Source:99)
at android.app.FragmentManagerImpl.execPendingActions(Unknown Source:21)
at android.app.FragmentManagerImpl$1.run(Unknown Source:2)
at android.os.Handler.handleCallback(Unknown Source:2)
at android.os.Handler.dispatchMessage(Unknown Source:4)
at android.os.Looper.loop(Unknown Source:242)
at android.app.ActivityThread.main(Unknown Source:98)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(Unknown Source:11)
at com.android.internal.os.ZygoteInit.main(Unknown Source:275)
Click to expand...
Click to collapse
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