Comment: Edit code style
Exception in Android N code
ActivityManager: Sending non-protected broadcast while sending Broadcast from System APP
This exception is thrown in many system app along with my application
How we can resolve this issue and what exactly the root cause and it's impact.
Reference from logs:
01-16 08:58:43.943 1213 1530 E ActivityManager: java.lang.Throwable
01-16 08:58:43.943 1213 1530 E ActivityManager: at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:17868)
01-16 08:58:43.943 1213 1530 E ActivityManager: at com.android.server.am.ActivityManagerService.broadcastIntent(ActivityManagerService.java:18434)
01-16 08:58:43.943 1213 1530 E ActivityManager: at android.app.ActivityManagerNative.onTransact(ActivityManagerNative.java:499)
01-16 08:58:43.943 1213 1530 E ActivityManager: at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:2818)
01-16 08:58:43.943 1213 1530 E ActivityManager: at android.os.Binder.execTransact(Binder.java:565)
Related
Hello, i m trying to port pac rom to zte blade.I used an 4.3 cm rom as a base and 4.3 pac as port.I got it to install but its bootlooping.The logcat gives me this error :
11-12 15:42:32.790 1263 1263 D AndroidRuntime:
11-12 15:42:32.790 1263 1263 D AndroidRuntime: >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
11-12 15:42:32.790 1263 1263 D AndroidRuntime: CheckJNI is OFF
11-12 15:42:32.870 1263 1263 D dalvikvm: Trying to load lib libjavacore.so 0x0
11-12 15:42:32.890 1263 1263 D dalvikvm: Added shared lib libjavacore.so 0x0
11-12 15:42:32.970 1263 1263 D dalvikvm: Trying to load lib libnativehelper.so 0x0
11-12 15:42:32.970 1263 1263 D dalvikvm: Added shared lib libnativehelper.so 0x0
11-12 15:42:33.090 1263 1263 W dalvikvm: PR_SET_NO_NEW_PRIVS failed. Is your kernel compiled correctly?: Invalid argument
11-12 15:42:33.100 1263 1263 E dalvikvm: ERROR: couldn't find native method
11-12 15:42:33.100 1263 1263 E dalvikvm: Requested: Landroid/content/res/AssetManager;.setConfigurationIILjava/lang/String;IIIIIIIIIIIIII)V
11-12 15:42:33.100 1263 1263 E dalvikvm: Candidate: Landroid/content/res/AssetManager;.setConfigurationIILjava/lang/String;IIIIIIIIIIIIIII)V
11-12 15:42:33.100 1263 1263 E dalvikvm: JNI posting fatal error: RegisterNatives failed for 'android/content/res/AssetManager', aborting
11-12 15:42:33.100 1263 1263 I dalvikvm: "main" prio=5 tid=1 NATIVE
11-12 15:42:33.100 1263 1263 I dalvikvm: | group="main" sCount=0 dsCount=0 obj=0x41528578 self=0x15428
11-12 15:42:33.100 1263 1263 I dalvikvm: | sysTid=1263 nice=0 sched=0/0 cgrp=default handle=1073815288
11-12 15:42:33.110 1263 1263 I dalvikvm: | state=R schedstat=( 0 0 0 ) utm=76 stm=14 core=0
11-12 15:42:33.150 1263 1263 I dalvikvm: #00 pc 0000132e /system/lib/libcorkscrew.so (unwind_backtrace_thread+25)
11-12 15:42:33.150 1263 1263 I dalvikvm: #01 pc 00060d9c /ystem/lib/libdvm.so (dvmDumpNativeStack(DebugOutputTarget const*, int)+31)
11-12 15:42:33.150 1263 1263 I dalvikvm: #02 pc 000546de /system/lib/libdvm.so (dvmDumpThreadEx(DebugOutputTarget const*, Thread*, bool)+425)
11-12 15:42:33.150 1263 1263 I dalvikvm: #03 pc 0005474a /system/lib/libdvm.so (dvmDumpThread(Thread*, bool)+25)
11-12 15:42:33.150 1263 1263 I dalvikvm: #04 pc 000491da /system/lib/libdvm.so
11-12 15:42:33.150 1263 1263 I dalvikvm: #05 pc 000491f6 /system/lib/libdvm.so
11-12 15:42:33.150 1263 1263 I dalvikvm: #06 pc 00000a38 /system/lib/libnativehelper.so (jniRegisterNativeMethods+87)
11-12 15:42:33.150 1263 1263 I dalvikvm: #07 pc 0004ceb6 /system/lib/libandroid_runtime.so (android::AndroidRuntime::registerNativeMethods(_JNIEnv*, char const*, JNINativeMethod const*, int)+1)
11-12 15:42:33.150 1263 1263 I dalvikvm: #08 pc 0007020e /system/lib/libandroid_runtime.so (android::register_android_content_AssetManager(_JNIEnv*)+281)
11-12 15:42:33.150 1263 1263 I dalvikvm: #09 pc 0004cd58 /system/lib/libandroid_runtime.so
11-12 15:42:33.150 1263 1263 I dalvikvm: #10 pc 0004d076 /system/lib/libandroid_runtime.so (android::AndroidRuntime::startReg(_JNIEnv*)+29)
11-12 15:42:33.150 1263 1263 I dalvikvm: #11 pc 0004da1a /system/lib/libandroid_runtime.so (android::AndroidRuntime::start(char const*, char const*)+209)
11-12 15:42:33.150 1263 1263 I dalvikvm: #12 pc 00001034 /system/bin/app_process
11-12 15:42:33.150 1263 1263 I dalvikvm: #13 pc 0000e0fa /system/lib/libc.so (__libc_init+49)
11-12 15:42:33.150 1263 1263 I dalvikvm: at dalvik.system.NativeStart.main(Native Method)
11-12 15:42:33.150 1263 1263 I dalvikvm: at dalvik.system.NativeStart.main(Native Method)
11-12 15:42:33.150 1263 1263 I dalvikvm:
11-12 15:42:33.150 1263 1263 E dalvikvm: VM aborting
11-12 15:42:33.150 1263 1263 F libc : Fatal signal 11 (SIGSEGV) at 0xdeadd00d (code=1), thread 1263 (zygote)
So i decompiled framework.jar/clasees.dex of base and port and tried to diff at android/content/res/AssetManager but i didnt find any missing line only few diffrences.I found at assetmanager.smali base this line:
.method public final native setConfiguration(IILjava/lang/String;IIIIIIIIIIIIII)V
.end method
and at port this:
.method public final native setConfiguration(IILjava/lang/String;IIIIIIIIIIIIIII)V
.end method
I dont know what to do or where to look so any help would be useful.
thanks in advance
I have this issue:
01-09 11:58:07.691 22967 22967 E AndroidRuntime: java.util.concurrent.RejectedExecutionException: Task [email protected] rejected from [email protected][Running, pool size = 17, active threads = 17, queued tasks = 128, completed tasks = 52]
I'm on Nougat 7.1.1, the problem fix after reset and then after two days it's on again.
I'm searching on the internet and some one says is related to background data disabled for some apps, and other says due to AsyncTask queue pool is over 128, it reject every new task to execute.
The devices affected are Google Pixel 7.1.2 7.1.1 samsungs, motorolas and others devices and versions. Some known tracked issues can be found on post similar to this: https://productforums.google.com/fo...ZFBIyW2KE;context-place=forum/phone-by-google
Some one posted the bad code causing issue and the solution to fix it but on AOSP (If I can retrieve the link I will attach to this post for furter analysis)
Trying to speak with Sony support the only thing they can do, is to send the device for repair (thankyou )
So, I wish to know if there's a solution trough ADB or some wise app that can flush Pool queue and free it to permit execution of usage data, or something else
I'll post the entire log for further info
01-09 11:37:22.687 14737 14737 E AndroidRuntime: FATAL EXCEPTION: main
01-09 11:37:22.687 14737 14737 E AndroidRuntime: Process: com.android.settings,PID: 14737
01-09 11:37:22.687 14737 14737 E AndroidRuntime: java.util.concurrent.RejectedExecutionException: Task [email protected] rejected from [email protected][Running, pool size = 17, active threads = 17, queued tasks = 128, completed tasks = 74]
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2049)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:814)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1360)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at android.os.AsyncTask.executeOnExecutor(AsyncTask.java:623)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at com.android.settings.datausage.AppDataUsagePreference$UidDetailTask.bindView(AppDataUsagePreference.j
ava:93)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at com.android.settings.datausage.AppDataUsagePreference.<init>(AppDataUsagePreference.java:49)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at com.android.settings.datausage.DataUsageList.bindStats(DataUsageList.java:483)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at com.android.settings.datausage.DataUsageList$3.onLoadFinished(DataUsageList.java:656)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at com.android.settings.datausage.DataUsageList$3.onLoadFinished(DataUsageList.java:653)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at android.app.LoaderManagerImpl$LoaderInfo.callOnLoadFinished(LoaderManager.java:489)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at android.app.LoaderManagerImpl$LoaderInfo.onLoadComplete(LoaderManager.java:457)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at android.content.Loader.deliverResult(Loader.java:144)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at android.content.AsyncTaskLoader.dispatchOnLoadComplete(AsyncTaskLoader.java:265)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at android.content.AsyncTaskLoader$LoadTask.onPostExecute(AsyncTaskLoader.java:92)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at android.os.AsyncTask.finish(AsyncTask.java:667)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at android.os.AsyncTask.-wrap1(AsyncTask.java)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:684)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at android.os.Looper.loop(Looper.java:241)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6274)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)
Hi guys,
the huawei camera app always crashes after a few seconds by itself.
Im on 9.0.0.216.
Opern Camera is working as expected.
This is the logcat:
Code:
--------- beginning of crash
05-01 20:26:08.152 9775 9775 E AndroidRuntime: FATAL EXCEPTION: main
05-01 20:26:08.152 9775 9775 E AndroidRuntime: Process: com.huawei.camera, PID: 9775
05-01 20:26:08.152 9775 9775 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'int java.lang.Integer.intValue()' on a null object reference
05-01 20:26:08.152 9775 9775 E AndroidRuntime: at com.huawei.camera2.controller.AREngine.getModeIndex(AREngine.java:628)
05-01 20:26:08.152 9775 9775 E AndroidRuntime: at com.huawei.camera2.controller.AREngine.refreshMaterailData(AREngine.java:587)
05-01 20:26:08.152 9775 9775 E AndroidRuntime: at com.huawei.camera2.controller.AREngine.access$2200(AREngine.java:53)
05-01 20:26:08.152 9775 9775 E AndroidRuntime: at com.huawei.camera2.controller.AREngine$8.run(AREngine.java:532)
05-01 20:26:08.152 9775 9775 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:891)
05-01 20:26:08.152 9775 9775 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
05-01 20:26:08.152 9775 9775 E AndroidRuntime: at android.os.Looper.loop(Looper.java:207)
05-01 20:26:08.152 9775 9775 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7470)
05-01 20:26:08.152 9775 9775 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
05-01 20:26:08.152 9775 9775 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:524)
05-01 20:26:08.152 9775 9775 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:958)
05-01 20:26:08.156 1142 6099 W ActivityManager: finishTopCrashedActivityLocked Force finishing activity com.huawei.camera/com.huawei.camera
Does anyonw know how to fix that?
Thanks!
I am sort of in a pickle right now and need help. I have P3XL with Android Q Beta 6 running. For some reason I had to factory reset the phone. I used Titanium Backup to create backups for all my apps and data and then did factory reset. After factory reset and rooting, TB is not able to run properly (can't backup or restore). I get an initial screen which is all empty (it typically shows Overview) showing "All done!" and selecting Batch Actions throws me back to empty "All done!" screen instead of showing me the screen of various action scenarios to backup and restore with count of apps.
I see this in the logcat:
Code:
08-17 21:09:50.760 1353 1507 W InputDispatcher: channel 'c98d7ae com.keramidas.TitaniumBackup/com.keramidas.TitaniumBackup.MainActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x9
08-17 21:09:50.760 1353 1507 E InputDispatcher: channel 'c98d7ae com.keramidas.TitaniumBackup/com.keramidas.TitaniumBackup.MainActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
08-17 21:09:50.761 1353 1540 I WindowManager: WIN DEATH: Window{c98d7ae u0 com.keramidas.TitaniumBackup/com.keramidas.TitaniumBackup.MainActivity}
08-17 21:09:50.761 1353 1540 W InputDispatcher: Attempted to unregister already unregistered input channel 'c98d7ae com.keramidas.TitaniumBackup/com.keramidas.TitaniumBackup.MainActivity (server)'
08-17 21:09:51.675 1353 1540 I ActivityTaskManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.keramidas.TitaniumBackup/.MainActivity bnds=[854,2457][1123,2852]} from uid 10152
08-17 21:09:51.703 1353 1381 I ActivityManager: Start proc 15741:com.keramidas.TitaniumBackup/u0a208 for activity {com.keramidas.TitaniumBackup/com.keramidas.TitaniumBackup.MainActivity}
08-17 21:09:51.808 15741 15741 I com.keramidas.TitaniumBackup.MainActivity: Main Activity is being created for the first time => scheduling next wake-up ...
08-17 21:09:51.849 1353 11536 W DevicePolicyManager: Package com.keramidas.TitaniumBackup (uid=10208, pid=15741) cannot access Device IDs
08-17 21:09:51.851 2078 2260 W TelephonyPermissions: reportAccessDeniedToReadIdentifiers:com.keramidas.TitaniumBackup:getDeviceId:isPreinstalled=false:isPrivApp=false
08-17 21:09:51.855 15741 15768 I o.co : [Licensing] No cache file: /storage/emulated/0/data/com.keramidas.TitaniumBackup/licensing-cache.xml
08-17 21:09:51.855 15741 15768 I o.co : [Licensing] Deleting non-valid cache file: /storage/emulated/0/data/com.keramidas.TitaniumBackup/licensing-cache.xml
08-17 21:09:51.859 15741 15768 W System.err: ERROR: Could not open license file: /data/user/0/com.keramidas.TitaniumBackup/files/license.txt
08-17 21:09:51.903 1353 1379 I ActivityTaskManager: Displayed com.keramidas.TitaniumBackup/.MainActivity: +222ms
08-17 21:09:52.025 1353 1540 I ActivityTaskManager: START u0 {act=android.intent.action.VIEW dat=file:///data/local/tmp/com.keramidas.TitaniumBackup-install.apk typ=application/vnd.android.package-archive} from uid 10208
08-17 21:09:52.025 15741 15741 W o.eu : [COLOR="Red"]android.content.ActivityNotFoundException: No Activity found to handle Intent[/COLOR] { act=android.intent.action.VIEW dat=file:///data/local/tmp/com.keramidas.TitaniumBackup-install.apk typ=application/vnd.android.package-archive }
08-17 21:09:52.025 15741 15741 W o.eu : at com.keramidas.TitaniumBackup.MainActivity.ᐧ(Source:1776)
08-17 21:09:52.025 15741 15741 W o.eu : at com.keramidas.TitaniumBackup.MainActivity.ˊ(Source:83)
08-17 21:09:52.025 15741 15741 W o.eu : at com.keramidas.TitaniumBackup.MainActivity.ˊ(Source:581)
08-17 21:09:52.039 1353 1540 I ActivityTaskManager: START u0 {act=com.keramidas.TitaniumBackupAddon.ASK_FOR_PERMISSIONS} from uid 10208
08-17 21:09:52.040 15741 15792 E com.keramidas.TitaniumBackup.MainActivity:[COLOR="Red"] Failed to trigger permission requests within TB add-on[/COLOR]
08-17 21:09:52.040 15741 15792 E com.keramidas.TitaniumBackup.MainActivity: android.content.ActivityNotFoundException: No Activity found to handle Intent { act=com.keramidas.TitaniumBackupAddon.ASK_FOR_PERMISSIONS }
08-17 21:09:52.040 15741 15792 E com.keramidas.TitaniumBackup.MainActivity: at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:2051)
08-17 21:09:52.040 15741 15792 E com.keramidas.TitaniumBackup.MainActivity: at android.app.Instrumentation.execStartActivity(Instrumentation.java:1709)
08-17 21:09:52.040 15741 15792 E com.keramidas.TitaniumBackup.MainActivity: at android.app.Activity.startActivityForResult(Activity.java:5173)
08-17 21:09:52.040 15741 15792 E com.keramidas.TitaniumBackup.MainActivity: at android.app.Activity.startActivityForResult(Activity.java:5131)
08-17 21:09:52.040 15741 15792 E com.keramidas.TitaniumBackup.MainActivity: at android.app.Activity.startActivity(Activity.java:5502)
08-17 21:09:52.040 15741 15792 E com.keramidas.TitaniumBackup.MainActivity: at android.app.Activity.startActivity(Activity.java:5470)
08-17 21:09:52.040 15741 15792 E com.keramidas.TitaniumBackup.MainActivity: at com.keramidas.TitaniumBackup.MainActivity.ʿ(Source:48796)
08-17 21:09:52.040 15741 15792 E com.keramidas.TitaniumBackup.MainActivity: at o.კ.run(Source:1773)
08-17 21:09:52.040 15741 15792 E com.keramidas.TitaniumBackup.MainActivity: at o.ea.run(Source:117)
08-17 21:09:52.250 642 642 E Layer : [Surface(name=AppWindowToken{dc579fc token=Token{1771aef ActivityRecord{ee5abce u0 com.keramidas.TitaniumBackup/.MainActivity t47}}})/@0x7e61fa9 - animation-leash#0] No local sync point found
08-17 21:09:55.826 1353 5660 I ActivityTaskManager: START u0 {cmp=com.keramidas.TitaniumBackup/o.ｃ} from uid 10208
I am using the latest Canary build of Magisk to get the root on Q Beta's. Magisk root is working fine in all the apps.
Any ideas why this could be happening?
If I hide Magisk from Titanium Backup, it does not get root but it shows initial screen as in the screenshot below.
It looks like the above logcat indicates that the TB has trouble with the Titanium Backup Addon. I manually installed the addon and it moved forward. Now I see all my backups and Batch Actions let me run scenarios. But as soon as I try to restore an app, I get a force close on the app with this in the logcat:
Code:
08-18 07:43:42.952 20726 20793 E AndroidRuntime: FATAL EXCEPTION: Thread-7
08-18 07:43:42.952 20726 20793 E AndroidRuntime: Process: com.keramidas.TitaniumBackup, PID: 20726
08-18 07:43:42.952 20726 20793 E AndroidRuntime: android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.intent.action.VIEW dat=file:///data/local/tmp/com.keramidas.TitaniumBackup-install.apk typ=application/vnd.android.package-archive }
08-18 07:43:42.952 20726 20793 E AndroidRuntime: at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:2051)
08-18 07:43:42.952 20726 20793 E AndroidRuntime: at android.app.Instrumentation.execStartActivity(Instrumentation.java:1709)
08-18 07:43:42.952 20726 20793 E AndroidRuntime: at android.app.Activity.startActivityForResult(Activity.java:5192)
08-18 07:43:42.952 20726 20793 E AndroidRuntime: at android.app.Activity.startActivityForResult(Activity.java:5150)
08-18 07:43:42.952 20726 20793 E AndroidRuntime: at o.dZ.ˊ(Source:236)
08-18 07:43:42.952 20726 20793 E AndroidRuntime: at o.e.ˊ(Source:462)
08-18 07:43:42.952 20726 20793 E AndroidRuntime: at o.J.run(Source:200)
08-18 07:43:42.952 20726 20793 E AndroidRuntime: at o.dD.run(Source:165)
08-18 07:43:42.952 20726 20793 E AndroidRuntime: at java.lang.Thread.run(Thread.java:919)
I still can't restore my data.
I have been having this issue with my S10 5G magisk rooted and edxposed running.
The problem is when I install a new app, my other apps fail to read any of their private data. When I chmod -R 777 /data they can read their data again.
I am not sure if this is EdXposed or what, other than its really annoying. I am begging anyone for help with this.
@elesbb
Device ID ( often refered to as Android ID ) is generated when you boot your Android phone first time and will be there forever. When you format everything and factory reset your device then this device ID is overwritten and re-generated and stored again. Similarly, if you ever install a new ROM on your Android device, then this device ID will be overwritten and re-generated when you boot the device first time.
Have never heard or read it that Magisk or EdXposed changes device's Device ID. And even then a change of Device ID is guaranteed to have nothing to do with file/folders and/or user permissions.
jwoegerbauer said:
@elesbb
Device ID ( often refered to as Android ID ) is generated when you boot your Android phone first time and will be there forever. When you format everything and factory reset your device then this device ID is overwritten and re-generated and stored again. Similarly, if you ever install a new ROM on your Android device, then this device ID will be overwritten and re-generated when you boot the device first time.
Have never heard or read it that Magisk or EdXposed changes device's Device ID. And even then a change of Device ID is guaranteed to have nothing to do with file/folders and/or user permissions.
Click to expand...
Click to collapse
Yes, this is what my exact understanding of this was as well.
What I discovered though, was each install of an application now cycles the "Device ID". And apps should not rely on the "Device ID/Android ID" as a forms of security for things like encryption, etc. This is coming from this here: https://android-developers.googleblog.com/2017/04/changes-to-device-identifiers-in.html
All I know is when I update my xposed module (being the course of debugging), I would then reboot the device. It does the "android is starting" prompt as if it was a fresh wipe of the device. All my data is still there. The system apps loose their settings though. The apps are there and all of its data. However, if I try to launch an app, it immediately force closes. Here is a logcat snippet of the Facebook, and textra app.
Facebook
Code:
11-23 14:33:40.830 14391 14391 W ContextImpl: Failed to ensure /data/user_de/0/com.facebook.lite/code_cache: mkdir failed: EACCES (Permission denied)
11-23 14:33:40.950 14391 14391 E AndroidRuntime: FATAL EXCEPTION: main
11-23 14:33:40.950 14391 14391 E AndroidRuntime: Process: com.facebook.lite, PID: 14391
11-23 14:33:40.950 14391 14391 E AndroidRuntime: java.lang.RuntimeException: Unable to instantiate application com.facebook.lite.ClientApplicationSplittedShell: java.lang.IllegalArgumentException: Optimized data directory /data/user/0/com.facebook.lite/dex is not owned by the current user. Shared storage cannot protect your application from code injection attacks.
11-23 14:33:40.950 14391 14391 E AndroidRuntime: at android.app.LoadedApk.makeApplication(LoadedApk.java:1296)
11-23 14:33:40.950 14391 14391 E AndroidRuntime: at android.app.ActivityThread.handleMakeApplication(ActivityThread.java:7152)
11-23 14:33:40.950 14391 14391 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:7134)
11-23 14:33:40.950 14391 14391 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
11-23 14:33:40.950 14391 14391 E AndroidRuntime: at com.swift.sandhook.SandHook.callOriginMethod(SandHook.java:185)
11-23 14:33:40.950 14391 14391 E AndroidRuntime: at com.swift.sandhook.xposedcompat.hookstub.HookStubManager.hookBridge(HookStubManager.java:376)
11-23 14:33:40.950 14391 14391 E AndroidRuntime: at SandHookerNew_5sm3dthec8858ee0to4kj3c1ge.hook(Unknown Source:51)
11-23 14:33:40.950 14391 14391 E AndroidRuntime: at android.app.ActivityThread.access$1600(ActivityThread.java:274)
11-23 14:33:40.950 14391 14391 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2102)
11-23 14:33:40.950 14391 14391 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:107)
11-23 14:33:40.950 14391 14391 E AndroidRuntime: at android.os.Looper.loop(Looper.java:237)
11-23 14:33:40.950 14391 14391 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:8167)
11-23 14:33:40.950 14391 14391 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
11-23 14:33:40.950 14391 14391 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:496)
11-23 14:33:40.950 14391 14391 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1100)
[COLOR="Red"]11-23 14:33:40.950 14391 14391 E AndroidRuntime: Caused by: java.lang.IllegalArgumentException: Optimized data directory /data/user/0/com.facebook.lite/dex is not owned by the current user. Shared storage cannot protect your application from code injection attacks.[/COLOR]
11-23 14:33:40.950 14391 14391 E AndroidRuntime: at dalvik.system.DexFile.<init>(DexFile.java:141)
11-23 14:33:40.950 14391 14391 E AndroidRuntime: at dalvik.system.DexFile.loadDex(DexFile.java:210)
11-23 14:33:40.950 14391 14391 E AndroidRuntime: at dalvik.system.DexFile.loadDex(DexFile.java:177)
11-23 14:33:40.950 14391 14391 E AndroidRuntime: at X.02Q.A00(:67)
11-23 14:33:40.950 14391 14391 E AndroidRuntime: at X.01U.A04(:61)
11-23 14:33:40.950 14391 14391 E AndroidRuntime: at com.facebook.lite.ClientApplicationSplittedShell.attachBaseContext(:4738)
11-23 14:33:40.950 14391 14391 E AndroidRuntime: at android.app.Application.attach(Application.java:370)
11-23 14:33:40.950 14391 14391 E AndroidRuntime: at android.app.Instrumentation.newApplication(Instrumentation.java:1157)
11-23 14:33:40.950 14391 14391 E AndroidRuntime: at android.app.LoadedApk.makeApplication(LoadedApk.java:1288)
11-23 14:33:40.950 14391 14391 E AndroidRuntime: ... 14 more
Textra
Code:
11-23 14:34:20.354 9346 9346 W ContextImpl: Failed to ensure /data/user/0/com.textra/cache: mkdir failed: EACCES (Permission denied)
11-23 14:34:20.354 9346 9346 W ContextImpl: Failed to update user.inode_cache: stat failed: EACCES (Permission denied)
11-23 14:34:20.355 9346 9346 W ContextImpl: Failed to ensure /data/user_de/0/com.textra/code_cache: mkdir failed: EACCES (Permission denied)
11-23 14:34:20.355 9346 9346 W ContextImpl: Failed to update user.inode_code_cache: stat failed: EACCES (Permission denied)
[COLOR="red"]11-23 14:34:20.432 9346 26624 E SQLiteDatabase: Failed to open database '/data/user/0/com.textra/databases/messaging.db'.
11-23 14:34:20.432 9346 26624 E SQLiteDatabase: android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 1806 SQLITE_CANTOPEN_EACCES[1806]): Could not open database[/COLOR]
11-23 14:34:20.432 9346 26624 E SQLiteDatabase: at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method)
11-23 14:34:20.432 9346 26624 E SQLiteDatabase: at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:300)
11-23 14:34:20.432 9346 26624 E SQLiteDatabase: at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:218)
11-23 14:34:20.432 9346 26624 E SQLiteDatabase: at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java:737)
11-23 14:34:20.432 9346 26624 E SQLiteDatabase: at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:284)
11-23 14:34:20.432 9346 26624 E SQLiteDatabase: at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:251)
11-23 14:34:20.432 9346 26624 E SQLiteDatabase: at android.database.sqlite.SQLiteDatabase.openInner(SQLiteDatabase.java:1394)
11-23 14:34:20.432 9346 26624 E SQLiteDatabase: at android.database.sqlite.SQLiteDatabase.open(SQLiteDatabase.java:1339)
11-23 14:34:20.432 9346 26624 E SQLiteDatabase: at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:974)
11-23 14:34:20.432 9346 26624 E SQLiteDatabase: at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:448)
11-23 14:34:20.432 9346 26624 E SQLiteDatabase: at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:391)
11-23 14:34:20.432 9346 26624 E SQLiteDatabase: at com.mplus.lib.lg1.d(SourceFile:1)
11-23 14:34:20.432 9346 26624 E SQLiteDatabase: at com.mplus.lib.mg1.<init>(SourceFile:6)
11-23 14:34:20.432 9346 26624 E SQLiteDatabase: at com.mplus.lib.mg1.j0(SourceFile:1)
11-23 14:34:20.432 9346 26624 E SQLiteDatabase: at com.mplus.lib.af1.run(Unknown Source:2)
11-23 14:34:20.432 9346 26624 E SQLiteDatabase: at java.lang.Thread.run(Thread.java:919)
So here you can see all the force closing is caused by the wrong owner/permissions. This also happens with the system apps, but the system apps just reset themselves and makes a new directory. Something is definitely changing the owner or whatever, which causes the device to think it has not been setup, prompting the "android is starting" prompt. It is EXTREMELY annoying to deal with and I am desperate for help.
Also,
running
Code:
chmod -R 777 /data
allows some apps to open (because they can now access the data), I do not know what is causing this device owner change..