File Manager crashes when opening folder on desktop - Remix OS for PC

As the title says, whenever I open a folder on the desktop File Manager crashes. Remix OS version is 2.0.102, build 5.1.1-B2016030106. Has anyone else experienced this?
Error message:
Code:
exceptionClassName: java.lang.NullPointerException
exceptionMessage: Attempt to invoke virtual method 'boolean java.lang.String.equals(java.lang.Object)' on a null object reference
throwFileName: DocumentsActivity.java
throwClassName: com.jide.filemanager.DocumentsActivity
throwMethodName: getParentDirectory
throwLineNumber: 1571
stackTrace: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.equals(java.lang.Object)' on a null object reference
at com.jide.filemanager.DocumentsActivity.getParentDirectory(DocumentsActivity.java:1571)
at com.jide.filemanager.DirectoryFragment.onCreateView(DirectoryFragment.java:379)
at android.app.Fragment.performCreateView(Fragment.java:2053)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:894)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1067)
at android.app.BackStackRecord.run(BackStackRecord.java:834)
at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1452)
at android.app.FragmentManagerImpl$1.run(FragmentManager.java:447)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5401)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)

How do you get anything to open from the desktop? I have to use the toolbar to do anything.

putr4s said:
As the title says, whenever I open a folder on the desktop File Manager crashes. Remix OS version is 2.0.102, build 5.1.1-B2016030106. Has anyone else experienced this?
Error message:
Code:
exceptionClassName: java.lang.NullPointerException
exceptionMessage: Attempt to invoke virtual method 'boolean java.lang.String.equals(java.lang.Object)' on a null object reference
throwFileName: DocumentsActivity.java
throwClassName: com.jide.filemanager.DocumentsActivity
throwMethodName: getParentDirectory
throwLineNumber: 1571
stackTrace: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.equals(java.lang.Object)' on a null object reference
at com.jide.filemanager.DocumentsActivity.getParentDirectory(DocumentsActivity.java:1571)
at com.jide.filemanager.DirectoryFragment.onCreateView(DirectoryFragment.java:379)
at android.app.Fragment.performCreateView(Fragment.java:2053)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:894)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1067)
at android.app.BackStackRecord.run(BackStackRecord.java:834)
at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1452)
at android.app.FragmentManagerImpl$1.run(FragmentManager.java:447)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5401)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
Click to expand...
Click to collapse
hi,
I created a folder and placed some apps in it on desktop, afterwards tried to open folder, but it did not respon.d I had to delete folder eventually.
So, yes, i agree the folders are buggy.,
(Not working.?)
good luck
---------- Post added at 03:17 PM ---------- Previous post was at 03:15 PM ----------
fsuinnc said:
How do you get anything to open from the desktop? I have to use the toolbar to do anything.
Click to expand...
Click to collapse
hi,
i double click on the app icon (desktop) and it launches /open.
Good luck

Related

[Solved] Compiling Apps Problem

I've been trying to compile AOSP apps individually and that doesn't seem to work. These are the steps I took:
1. Install GCC and Java
2. The repo commands (sync from android git etc)
3. make Gallery3D
4. push Gallery3D.apk /system/app/
So as you can see, compilation went on fine. And pushing to my phone also went fine (CM 5.0.4.1). However, when I try to run Gallery3D, I got FC. Here's my logcat:
I/ActivityManager( 93): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.cooliris.media/.Gallery }
V/RenderScript_jni( 6329): surfaceDestroyed
V/RenderScript( 6329): setSurface 0 0 0x0
D/ViewFlipper( 6329): updateRunning() mVisible=false, mStarted=true, mUserPresent=true, mRunning=false
D/LocationManager( 6198): removeUpdates: listener = [email protected]
D/NetworkLocationProvider( 93): removeListener(): wallpaper
D/NetworkLocationProvider( 93): enableLocationTracking(): false
E/NetworkLocationProvider( 93): releaseCheckLocationLock: wake lock has already been released
D/SensorManager(18699): found sensor: BMA150 3-axis Accelerometer, handle=0
D/SensorManager(18699): found sensor: AK8973 3-axis Magnetic field sensor, handle=1
D/SensorManager(18699): found sensor: AK8973 Orientation sensor, handle=2
D/SensorManager(18699): found sensor: CM3602 Proximity sensor, handle=4
D/SensorManager(18699): found sensor: CM3602 Light sensor, handle=5
W/ResourceType(18699): Failure getting entry for 0x7f02003a (t=1 e=58) in package 0: 0xffffffb5
D/AndroidRuntime(18699): Shutting down VM
W/dalvikvm(18699): threadid=3: thread exiting with uncaught exception (group=0x4001b178)
E/AndroidRuntime(18699): Uncaught handler: thread main exiting due to uncaught exception
E/AndroidRuntime(18699): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.cooliris.media/com.cooliris.media.Gallery}: android.content.res.Resources$NotFoundException: Resource ID #0x7f02003a
E/AndroidRuntime(18699): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2496)
E/AndroidRuntime(18699): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2512)
E/AndroidRuntime(18699): at android.app.ActivityThread.access$2200(ActivityThread.java:119)
E/AndroidRuntime(18699): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1863)
E/AndroidRuntime(18699): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(18699): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime(18699): at android.app.ActivityThread.main(ActivityThread.java:4363)
E/AndroidRuntime(18699): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(18699): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime(18699): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
E/AndroidRuntime(18699): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
E/AndroidRuntime(18699): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime(18699): Caused by: android.content.res.Resources$NotFoundException: Resource ID #0x7f02003a
E/AndroidRuntime(18699): at android.content.res.Resources.getValue(Resources.java:891)
E/AndroidRuntime(18699): at android.content.res.Resources.getDrawable(Resources.java:579)
E/AndroidRuntime(18699): at com.cooliris.media.HudLayer.<init>(HudLayer.java:121)
E/AndroidRuntime(18699): at com.cooliris.media.GridLayer.<init>(GridLayer.java:134)
E/AndroidRuntime(18699): at com.cooliris.media.Gallery.onCreate(Gallery.java:78)
E/AndroidRuntime(18699): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
E/AndroidRuntime(18699): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2459)
E/AndroidRuntime(18699): ... 11 more
I/Process ( 93): Sending signal. PID: 18699 SIG: 3
I/dalvikvm(18699): threadid=7: reacting to signal 3
I/dalvikvm(18699): Wrote stack trace to '/data/anr/traces.txt'
I/DumpStateReceiver( 93): Added state dump to 1 crashes
Click to expand...
Click to collapse
Besides this, I noticed that my Gallery3D.apk is smaller size(~500kb) than the one which comes with CM (~700kb).
Any help guys? Been trying to figure this out and googling. What did I miss?
arctu said:
I've been trying to compile AOSP apps individually and that doesn't seem to work. These are the steps I took:
1. Install GCC and Java
2. The repo commands (sync from android git etc)
3. make Gallery3D
4. push Gallery3D.apk /system/app/
So as you can see, compilation went on fine. And pushing to my phone also went fine (CM 5.0.4.1). However, when I try to run Gallery3D, I got FC. Here's my logcat:
Besides this, I noticed that my Gallery3D.apk is smaller size(~500kb) than the one which comes with CM (~700kb).
Any help guys? Been trying to figure this out and googling. What did I miss?
Click to expand...
Click to collapse
Q&A section ma man
I believe this is the right section, it's a question on compiling/development. I believe Gallery3D might be lacking mdpi images, and you're compiling for mdpi devices (may be wrong, not able to check now).
What you can do is to do a search for "PRODUCT_LOCALES", within all your files, I think it's in build.mk or product.mk. You will see that the default is mdpi, follow by <something> (can't remember now) += nodpi. Add a <something> += hdpi after the nodpi line, and compile and push again. I had a similar issue and was able to fix it this way, with advice from cyanogen.
Thanks Wysie. That helps!
To those facing the same problem here are the exact steps I took (using terminal and nano):
1. Open/Edit build/core/product_config.mk:
nano build/core/product_config.mk
Click to expand...
Click to collapse
2. Find:
PRODUCT_LOCALES += nodpi
Click to expand...
Click to collapse
3. Add in after that line:
PRODUCT_LOCALES += hdpi
Click to expand...
Click to collapse
4. Save and Exit: Ctrl+X
5. Run make again:
make Gallery3D
Click to expand...
Click to collapse
If you did everything correctly, and have compiled before, the compiler should write this at the beginning:
*** Build configuration changed: "generic-eng-{mdpi,nodpi}" -> "generic-eng-{mdpi,nodpi,hdpi}"
*** Forcing "make installclean"...
*** Done with the cleaning, now starting the real build.
Click to expand...
Click to collapse
It works now. Hope this helps the others.
arctu said:
Thanks Wysie. That helps!
To those facing the same problem here are the exact steps I took (using terminal and nano):
1. Open/Edit build/core/product_config.mk:
2. Find:
3. Add in after that line:
4. Save and Exit: Ctrl+X
5. Run make again:
If you did everything correctly, and have compiled before, the compiler should write this at the beginning:
It works now. Hope this helps the others.
Click to expand...
Click to collapse
cheers, helped me out
after quick grep to confirm I used sed
Code:
sed s/PRODUCT_LOCALES\ \+\=\ nodpi/PRODUCT_LOCALES\ \+\=\ hdpi/ build/core/product_config.mk -i

Leagoo z5, mt6735, o mt6737?

If you ask me what I am saying, well I do not know, the matter is that this smartphone, Chinese, of medium to low quality and economic is known as LEAGOO Z5 LTE 37m, but here comes the strange issue, it is its processor , that on the internet, it is like mt6735, but the same device seen in flashtool is mt6737, and here the confusion begins, which is why not, for such echo with so many doubts take out the status of the aforementioned device in the context of recovery, and this is what I get,
petName=Z5
Lte
versionName=6.0-1488765164
resolution=854 * 480
versionCode=23
SDK_VERSION=23
RELEASE=6.0
Globe.REQUEST_HEADER_IMSI=748070103222388
Globe.REQUEST_HEADER_IMEI=352478081946651
BOARD=Android
BOOTLOADER=unknown
BRAND=LEAGOO
CPU_ABI=armeabi-v7a
CPU_ABI2=armeabi
DEVICE=Z5
DISPLAY=LEAGOO Z5 Lte(37m)_OS2.0_A_20170306
FINGERPRINT=alps/full_bd6737m_35g_a_m0/bd6737m_35g_a_m0:6.0/MRA58K/1488765164:user/dev-keys
HARDWARE=mt6735
HOST=jyunspl2-PowerEdge-R720
ID=MRA58
K
IS_DEBUGGABLE=false
MANUFACTURER=LEAGOO
MODEL=Z5 Lte
PRODUCT=Z5
RADIO=unknown
SERIAL=0123456789
ABCDEF
SUPPORTED_32_BIT_ABIS=[Ljava.lang.String;@758aea8
SUPPORTED_64_BIT_ABIS=[Ljava.lang.String;@3e9bdc
1
SUPPORTED_ABIS=[Ljava.lang.String;@69cc966
TAG=Build
TAGS=dev-keys
TIME=1488765741000
TYPE=user
UNKNOWN=unknown
USER=huchao
crashTime=2018-02-07_14-33-44
STACK_TRACE=java.lang.RuntimeException:
Unable to start activity ComponentInfo{com.android.settings/com.android.settings.Settings$NotificationAccessSettingsActivity}: android.app.Fragment$Instantiation
Exception: Unable to instantiate fragment com.android.settings.notification.ManagedServiceSettings$ScaryWarning
DialogFragment: make sure class name exists, is public, and has an empty constructor that is public
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2576)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2658)
at android.app.ActivityThread.handleRelaunchActivity(ActivityThread.java:4321)
at android.app.ActivityThread.-wrap15(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1498)
at android.os.Handler.dispatchMessage(Handler.java:111)
at android.os.Looper.loop(Looper.java:207)
at android.app.ActivityThread.main(ActivityThread.java:5737)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:679)
Caused by: android.app.Fragment$Instantiation
Exception: Unable to instantiate fragment com.android.settings.notification.ManagedServiceSettings$ScaryWarning
DialogFragment: make sure class name exists, is public, and has an empty constructor that is public
at android.app.Fragment.instantiate(Fragment.java:635)
at android.app.FragmentState.instantiate(Fragment.java:111)
at android.app.FragmentManagerImpl.restoreAllState(FragmentManager.java:1885)
at android.app.FragmentController.restoreAllState(FragmentController.java:122)
at android.app.Activity.onCreate(Activity.java:927)
at com.android.settings.SettingsActivity.onCreate(SettingsActivity.java:648)
at android.app.Activity.performCreate(Activity.java:6390)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1113)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2523)
... 10 more
Caused by: java.lang.Instantiation
Exception: java.lang.Class<com.android.settings.notification.ManagedServiceSettings$ScaryWarningDialogFragment>
has no zero argument constructor
at java.lang.Class.newInstance(Native Method)
at android.app.Fragment.instantiate(Fragment.java:624)
... 18 more
android.app.Fragment$Instantiation
Exception: Unable to instantiate fragment com.android.settings.notification.ManagedServiceSettings$ScaryWarning
DialogFragment: make sure class name exists, is public, and has an empty constructor that is public
at android.app.Fragment.instantiate(Fragment.java:635)
at android.app.FragmentState.instantiate(Fragment.java:111)
at android.app.FragmentManagerImpl.restoreAllState(FragmentManager.java:1885)
at android.app.FragmentController.restoreAllState(FragmentController.java:122)
at android.app.Activity.onCreate(Activity.java:927)
at com.android.settings.SettingsActivity.onCreate(SettingsActivity.java:648)
at android.app.Activity.performCreate(Activity.java:6390)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1113)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2523)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2658)
at android.app.ActivityThread.handleRelaunchActivity(ActivityThread.java:4321)
at android.app.ActivityThread.-wrap15(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1498)
at android.os.Handler.dispatchMessage(Handler.java:111)
at android.os.Looper.loop(Looper.java:207)
at android.app.ActivityThread.main(ActivityThread.java:5737)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:679)
Caused by: java.lang.
InstantiationException: java.lang.Class<com.android.settings.notification.ManagedServiceSettings$ScaryWarningDialogFragment>
has no zero argument constructor
at java.lang.Class.newInstance(Native Method)
at android.app.Fragment.instantiate(Fragment.java:624)
... 18 more
java.lang.Instantiation
Exception: java.lang.Class<com.android.settings.notification.ManagedServiceSettings$ScaryWarningDialogFragment>
has no zero argument constructor
at java.lang.Class.newInstance(Native Method)
at android.app.Fragment.instantiate(Fragment.java:624)
at android.app.FragmentState.instantiate(Fragment.java:111)
at android.app.FragmentManagerImpl.restoreAllState(FragmentManager.java:1885)
at android.app.FragmentController.restoreAllState(FragmentController.java:122)
at android.app.Activity.onCreate(Activity.java:927)
at com.android.settings.SettingsActivity.onCreate(SettingsActivity.java:648)
at android.app.Activity.performCreate(Activity.java:6390)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1113)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2523)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2658)
at android.app.ActivityThread.handleRelaunchActivity(ActivityThread.java:4321)
at android.app.ActivityThread.-wrap15(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1498)
at android.os.Handler.dispatchMessage(Handler.java:111)
at android.os.Looper.loop(Looper.java:207)
at android.app.ActivityThread.main(ActivityThread.java:5737)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:679)
the issue is, according to this info, if we go to the information collected on the internet, there is only one leagoo z5 lte 37, and this is mtk6735, therefore this device in my possession is a clone? or is it original ?, although deadly and even so the PC sometimes detects it, I do not know how to recover it with so many doubts,
with flashtool the skatter is 6737, because the skater of the 6735 gives me incorrect, although I also have an error in the 6737 when I want to flash it,
the mistake is:
ERROR: S-DL-GET-DRAM-SETTING-FAIL (0x13be)
[EMI]: Obtain DRAM Failed!
[HINT]lease check your load matches to your target which is to be downloade
I hope I have been as specific as possible to the respect
good to the geniuses of this forum I appreciate I can advise the respect, to at least recover it and know that diantres is really an abraso to all

Titanium Backup don't work

Hi,
I need an alternate for it, I search.
Help please and thanks
joke19 said:
Hi,
I need an alternate for it, I search.
Help please and thanks
Click to expand...
Click to collapse
If u have patched it wrong just delete odex file it will more fine
Thanks , to patch help. :angel: The odex was not the problem.
Just clean installed AOSP Extended 6.2 and titanium backup hasn't worked from the start.
Anyone know how to fix?
Below is the crash report:
time: 1548402717610
msg: android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 14 SQLITE_CANTOPEN): Could not open database
stacktrace: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.keramidas.TitaniumBackup/com.keramidas.TitaniumBackup.MainActivity}: android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 14 SQLITE_CANTOPEN): Could not open database
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2953)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3088)
at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:78)
at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:108)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:68)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1818)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:193)
at android.app.ActivityThread.main(ActivityThread.java:6744)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:495)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
Caused by: android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 14 SQLITE_CANTOPEN): Could not open database
at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method)
at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:211)
at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:195)
at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java:503)
at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:204)
at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:196)
at android.database.sqlite.SQLiteDatabase.openInner(SQLiteDatabase.java:889)
at android.database.sqlite.SQLiteDatabase.open(SQLiteDatabase.java:874)
at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:748)
at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:738)
at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:365)
at android.database.sqlite.SQLiteOpenHelper.getReadableDatabase(SQLiteOpenHelper.java:322)
at o.dj.ˊ(Source:192)
at com.keramidas.TitaniumBackup.MainActivity.onCreate(Source:391)
at android.app.Activity.performCreate(Activity.java:7144)
at android.app.Activity.performCreate(Activity.java:7135)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1272)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2933)
... 11 more

[curtana] xiaomi.eu 12.0.2 - Dialler apps keep giving me this error when making/receiving calls

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

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