My phone just keep rebooting itself. It's been sent out for "repair" a couple times now and they aren't able to fix it. They did replace the mainboard, but it's still rebooting. I was able to capture the dumpstate and see where it crashed, but I just don't know how to interpret the info. Can anyone help?
Code:
12-06 07:05:44.965 1392 2067 V AlarmManager: Triggering alarm #1: 2 when =46076699 package=com.google.android.gmsoperation =*walarm*:com.google.android.gms.gcm.ACTION_CHECK_QUEUE
12-06 07:05:44.965 1392 2067 V AlarmManager: Triggering alarm #2: 2 when =46093358 package=androidoperation = null listenTag =*job.delay*
12-06 07:05:56.722 1392 1392 I DeviceIdleController: updateChargingLocked: charging=false
12-06 07:05:59.999 1392 2067 V AlarmManager: Triggering alarm #0: 3 when =46108403 package=androidoperation =*alarm*:android.intent.action.TIME_TICK
12-06 07:06:16.323 5536 5536 E AndroidRuntime: FATAL EXCEPTION: main
12-06 07:06:16.323 5536 5536 E AndroidRuntime: Process: com.android.bluetooth, PID: 5536
12-06 07:06:16.323 5536 5536 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
12-06 07:06:18.183 12055 12055 I chatty : uid=1000 system_server expire 15 lines
12-06 07:06:18.446 12055 12145 I chatty : uid=1000(system) CpuTracker expire 1 line
12-06 07:06:18.450 12055 12090 I chatty : uid=1000(system) batterystats-sy expire 1 line
12-06 07:06:18.452 12055 12055 I chatty : uid=1000 system_server expire 1 line
What is the full name of your device ?
Teddy Lo said:
What is the full name of your device ?
Click to expand...
Click to collapse
It's the OnePlus 5.
Did you tried to restore your phone back to stock ?
https://www.thecustomdroid.com/restore-oneplus-5-stock-firmware/
or try with this steps
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
Teddy Lo said:
Did you tried to restore your phone back to stock ?
https://www.thecustomdroid.com/restore-oneplus-5-stock-firmware/
or try with this steps
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
Click to expand...
Click to collapse
Yep, multiple times. However, they approved to just replace it so it's been shipped out to get replaced. But I would still be curious to know why it kept happening in the off chance an app or something else I was doing was causing it.
Related
hi all,
I am working in reversing apk aplication. I have got with sucess normally. I got a aplication not working now. It is do with API level v14.
I have decompile, compile and sing with sucess.
For test I to use emulator with Device Nexus S.
When i to install original application run without problems but with aplication decompiled, compiled and signed not working.
I have to used java tool and apk for sign. Nothing work.
I got the follow message:
"Unfortunately, aplication name has stopped.
I have read but don´t have seen same problem.
Any suggest?
A greeting.
To help you, we really need a logcat.
Because you have an emulator, I guess you have android-sdk installed.
To get your logcat, do:
adb logcat
After doing this, let it run.
Run your application in your emulator now. When it says "force close", you stop adb logcat by doing Ctrl+C
Then you copy the text with your error in it.
Thanks in advance
Sent from my Galaxy Nexus running Android 4.2 JB
hi, i did that.
I got the follow message.
Code:
I/ActivityManager( 82): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.anite.handy/.ui.core.ResumeActivit
y} from pid 181
D/PermissionCache( 36): checking android.permission.READ_FRAME_BUFFER for uid=1000 => granted (1379 us)
W/WindowManager( 82): Failure taking screenshot for (180x300) to layer 21005
I/ActivityManager( 82): Start proc com.anite.handy for activity com.anite.hand
y/.ui.core.ResumeActivity: pid=492 uid=10040 gids={3002, 3001, 3003, 1015}
I/dalvikvm( 492): Turning on JNI app bug workarounds for target SDK version 10.
..
W/NetworkManagementSocketTagger( 82): setKernelCountSet(10040, 1) failed witherrno -2
I/Process ( 82): Sending signal. PID: 492 SIG: 3
I/dalvikvm( 492): threadid=3: reacting to signal 3
I/dalvikvm( 492): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 82): Sending signal. PID: 492 SIG: 3
I/dalvikvm( 492): threadid=3: reacting to signal 3
I/dalvikvm( 492): Wrote stack traces to '/data/anr/traces.txt'
I/Handy ( 492): HandyApp.onCreate() pid=492
I/Process ( 82): Sending signal. PID: 492 SIG: 3
I/dalvikvm( 492): threadid=3: reacting to signal 3
I/dalvikvm( 492): Wrote stack traces to '/data/anr/traces.txt'
D/AndroidRuntime( 492): Shutting down VM
W/dalvikvm( 492): threadid=1: thread exiting with uncaught exception (group=0x4
09c01f8)
E/AndroidRuntime( 492): FATAL EXCEPTION: main
E/AndroidRuntime( 492): java.lang.RuntimeException: Unable to create application com.anite.handy.app.HandyApp: java.lang.SecurityException
E/AndroidRuntime( 492): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:3957)
E/AndroidRuntime( 492): at android.app.ActivityThread.access$1300(ActivityThread.java:123)
E/AndroidRuntime( 492): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1185)
E/AndroidRuntime( 492): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 492): at android.os.Looper.loop(Looper.java:137)E/AndroidRuntime( 492): at android.app.ActivityThread.main(ActivityThread.java:4424)
E/AndroidRuntime( 492): at java.lang.reflect.Method.invokeNative(NativeMethod)
E/AndroidRuntime( 492): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 492): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:784)
E/AndroidRuntime( 492): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:551)
E/AndroidRuntime( 492): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 492): Caused by: java.lang.SecurityException
E/AndroidRuntime( 492): at com.anite.handy.app.HandyApp.onCreate(Unknown Source)
E/AndroidRuntime( 492): at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:969)
E/AndroidRuntime( 492): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:3954)
E/AndroidRuntime( 492): ... 10 more
W/ActivityManager( 82): Force finishing activity com.anite.handy/.ui.core.ResumeActivity
W/InputManagerService( 82): Window already focused, ignoring focus gain of: [email protected]
I/Process ( 82): Sending signal. PID: 492 SIG: 3
I/dalvikvm( 492): threadid=3: reacting to signal 3
I/dalvikvm( 492): Wrote stack traces to '/data/anr/traces.txt'
W/ActivityManager( 82): Activity pause timeout for ActivityRecord{4142a7e0 com.anite.handy/.ui.core.ResumeActivity}
I/Process ( 82): Sending signal. PID: 492 SIG: 3
I/dalvikvm( 492): threadid=3: reacting to signal 3
I/dalvikvm( 492): Wrote stack traces to '/data/anr/traces.txt'
W/NetworkManagementSocketTagger( 82): setKernelCountSet(10040, 0) failed with errno -2
W/ActivityManager( 82): Activity destroy timeout for ActivityRecord{4142a7e0 com.anite.handy/.ui.core.ResumeActivity}
Check your "HandyApp Application" is declared in your manifest
I suggest you take a look at this one:
http://developer.android.com/guide/topics/manifest/manifest-intro.html
If you don't understand it just reply here and I'll fix it for ya
Sent from my Galaxy Nexus running Android 4.2 JB
i have checked AndroidManifest.xml decompiled file and i can see android:name=".app.HandyApp" in code.
Full code atached here
View attachment AndroidManifest.rar
Anyone have any suggestion? I can share the target if need.
Thanks
i have the same problem
unfortunately application has stop.
i have the same problem but its worse.
i have been installed kaspersky security using apk not from manual installed by google play.
and iam forget to unistalled it before i upgrade my android software.
after the process done it show message "unfortunately......." it keep showing up even after i klik "ok" or restart
i can't do anything with my device now (can't type anything, can't touch anything, even pick up incoming call) because of the pop up n start being stressed
anyone can help? :crying:
*My Device is galaxy Note II
Hi, I am not sure if this is the right thread, but since I don't know exactly where sould I post this I will post it here and if someone knows a better thread they sould tell me to go there.
My problem is with the game called Rhythm Racer 2, I have been in to this game since 2011 when I got Galaxy S 2, and it was working even on my Galaxy Tab S (SM-T805) until I was updated to lollipop, since then it just pops "Unfotunately Rhythm Racer 2 Has Stopped", also the same problem applies in Galaxy Note 4 (N910F), only there it doesn't work even on kitkat and in lollipop either, and the problem is that this app doesn't getting any update, it's on its initial version since 2011 and discontiniued, I know it's just a game and noone can know exactly what's the problem but I think the same error applies also in other apps that doesn't work since lollipop and based on that I think there is a solution someway.
I will apreciate any feedbak and advice on what should I do, Thanks.
Exception
Please provide logs for logcat.
use below command
$ adb logcat
You can verify it by your own to see why you got crash.
Waiting for logs .
I came across this same error caused by having installed the JDK 7 instead of 6. Hope it helps some other people with this error.
please check below link
http://stackoverflow.com/questions/6161931/java-lang-securityexception-when-install-apk
This is what I get when I try to run the app:
---- Oct 15, 2015 1:50:24 AM ----
10-15 01:47:42.044 9007 9007 I Timeline: Timeline: Activity_launch_request id:com.AvatarLabs.RhythmRacerX time:75719530
10-15 01:47:42.049 3837 5012 W ActivityManager: NORMAL SET : srcAppInfo.processName = com.sec.android.app.launcher, destAppInfo.processName = com.AvatarLabs.RhythmRacerX
10-15 01:47:42.159 3837 8545 I ActivityManager: Start proc com.AvatarLabs.RhythmRacerX for activity com.AvatarLabs.RhythmRacerX/com.unity3d.MobclixPlugin.MobclixPluginActivity: pid=12571 uid=10193 gids={50193, 9997, 3003} abi=armeabi-v7a
10-15 01:47:42.489 12571 12571 E AndroidRuntime: Process: com.AvatarLabs.RhythmRacerX, PID: 12571
10-15 01:47:42.489 12571 12571 E AndroidRuntime: java.lang.UnsatisfiedLinkError: Bad JNI version returned from JNI_OnLoad in "/data/app/com.AvatarLabs.RhythmRacerX-1/lib/arm/libmono.so": 0
10-15 01:47:42.509 3837 3937 W ActivityManager: Force finishing activity com.AvatarLabs.RhythmRacerX/com.unity3d.MobclixPlugin.MobclixPluginActivity
10-15 01:47:42.859 3837 3937 I WindowManager: Screenshot max retries 4 of Token{b537e72 ActivityRecord{35dd2f7d u0 com.AvatarLabs.RhythmRacerX/com.unity3d.MobclixPlugin.MobclixPluginActivity t403 f}} appWin=Window{27d1c81f u0 Starting com.AvatarLabs.RhythmRacerX} drawState=4
10-15 01:47:43.364 3837 3959 W ActivityManager: Activity pause timeout for ActivityRecord{35dd2f7d u0 com.AvatarLabs.RhythmRacerX/com.unity3d.MobclixPlugin.MobclixPluginActivity t403 f}
10-15 01:47:44.864 3837 8850 I ActivityManager: Process com.AvatarLabs.RhythmRacerX (pid 12571)(adj 9) has died(476,758)
---- Oct 15, 2015 1:50:24 AM ----
This is the entire logcat, I know this is weird, you mean that lollipop has JDK 7 and the game uses JDK 6 and that's the problem, and do I have to install JDK 6 some way on my device or try to make the propper changes to my .apk file?
I use CM10.2, but this bug existed also on CM10.1, I don't know if this is a hard- or software problem.
When I try to use the front facing camera (in various apps, doesn't matter if it's just Camera or Instagram), the application crashes. Here's the log. The most interesting part (I think) is:
Code:
08-28 16:38:17.407 16834 17189 E AndroidRuntime: FATAL EXCEPTION: Camera Handler Thread
08-28 16:38:17.407 16834 17189 E AndroidRuntime: java.lang.RuntimeException: startPreview failed
08-28 16:38:17.407 16834 17189 E AndroidRuntime: at android.hardware.Camera.startPreview(Native Method)
08-28 16:38:17.407 16834 17189 E AndroidRuntime: at com.android.camera.CameraManager$CameraHandler.handleMessage(CameraManager.java:181)
08-28 16:38:17.407 16834 17189 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
08-28 16:38:17.407 16834 17189 E AndroidRuntime: at android.os.Looper.loop(Looper.java:137)
08-28 16:38:17.407 16834 17189 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:61)
Bump.
r7s said:
I use CM10.2, but this bug existed also on CM10.1, I don't know if this is a hard- or software problem.
When I try to use the front facing camera (in various apps, doesn't matter if it's just Camera or Instagram), the application crashes. Here's the log. The most interesting part (I think) is:
Code:
08-28 16:38:17.407 16834 17189 E AndroidRuntime: FATAL EXCEPTION: Camera Handler Thread
08-28 16:38:17.407 16834 17189 E AndroidRuntime: java.lang.RuntimeException: startPreview failed
08-28 16:38:17.407 16834 17189 E AndroidRuntime: at android.hardware.Camera.startPreview(Native Method)
08-28 16:38:17.407 16834 17189 E AndroidRuntime: at com.android.camera.CameraManager$CameraHandler.handleMessage(CameraManager.java:181)
08-28 16:38:17.407 16834 17189 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
08-28 16:38:17.407 16834 17189 E AndroidRuntime: at android.os.Looper.loop(Looper.java:137)
08-28 16:38:17.407 16834 17189 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:61)
Click to expand...
Click to collapse
It definitely a Software problem as CM 10.1 & CM 10.2 are in Nightly state. Problem has been reported in known issues section in CM 10.2 thread here at XDA. It says "Front-facing Camera buggy".
Problem has been reported in known issues section in CM 10.2 thread here at XDA. It says "Front-facing Camera buggy".
Click to expand...
Click to collapse
Thanks, didn't know about it. The thing I've been experiencing this problem under 10.1, too, but I haven't seen anybody complaining about it in the 10.1 thread.
I just flashed another ROM (Chameleon 3.0.3) and I still have the same problem. I think it might be a hardware issue.
Bumpity bump.
Have you tried flashing full stock ROM? Non point in concluding it's a hardware fault unless you've eliminated the software side of things. So far you haven't.
Sent from a galaxy far, far away
Hi,
I'm bulding android for my single board computer with connected 7 inch lcd touch screen. It's working like a charm, but one issue. SystemUI.apk is crashing all the time with following error log:
Code:
I/ActivityManager( 368): Start proc com.android.systemui for restart com.android.systemui: pid=1883 uid=10001 gids={50001, 1028, 1015, 3002, 3001}
D/SystemUIService( 1883): loading: class com.android.systemui.statusbar.tablet.TabletStatusBar
D/SystemUIService( 1883): running: [email protected]
I/StatusBarManagerService( 368): registerStatusBar [email protected]0
W/ResourceType( 1883): Failure getting entry for 0x7f0200db (t=1 e=219) in package 0 (error -75)
D/AndroidRuntime( 1883): Shutting down VM
W/dalvikvm( 1883): threadid=1: thread exiting with uncaught exception (group=0x40d30930)
E/AndroidRuntime( 1883): FATAL EXCEPTION: main
E/AndroidRuntime( 1883): java.lang.RuntimeException: Unable to create service com.android.systemui.SystemUIService: android.view.InflateException: Binary XML file line #48: Error inflating class com.android.systemui.statusbar.policy.CompatModeButton
Does anyone know how to fix this or what's the reason for the crash?
Thank you very much in advance.
Update
rotowsky said:
Hi,
I'm bulding android for my single board computer with connected 7 inch lcd touch screen. It's working like a charm, but one issue. SystemUI.apk is crashing all the time with following error log:
Code:
I/ActivityManager( 368): Start proc com.android.systemui for restart com.android.systemui: pid=1883 uid=10001 gids={50001, 1028, 1015, 3002, 3001}
D/SystemUIService( 1883): loading: class com.android.systemui.statusbar.tablet.TabletStatusBar
D/SystemUIService( 1883): running: [email protected]
I/StatusBarManagerService( 368): registerStatusBar [email protected]0
W/ResourceType( 1883): Failure getting entry for 0x7f0200db (t=1 e=219) in package 0 (error -75)
D/AndroidRuntime( 1883): Shutting down VM
W/dalvikvm( 1883): threadid=1: thread exiting with uncaught exception (group=0x40d30930)
E/AndroidRuntime( 1883): FATAL EXCEPTION: main
E/AndroidRuntime( 1883): java.lang.RuntimeException: Unable to create service com.android.systemui.SystemUIService: android.view.InflateException: Binary XML file line #48: Error inflating class com.android.systemui.statusbar.policy.CompatModeButton
Does anyone know how to fix this or what's the reason for the crash?
Thank you very much in advance.
Click to expand...
Click to collapse
Hope for an Update , and that it works , ( I think so )
Mmh?
I am trying to create a second, covert version of Snapchat on my phone by changing the package name (to com.nisk.arcticfrolfing). I found a tutorial here and followed it. After signing the recompiled APK and installing it on my phone, the app crashes on launch. Here is what appears to be the relevant output from logcat:
Code:
I/ActivityManager(12510): Start proc com.nisk.arcticfrolfing for activity com.nisk.arcticfrolfing/.LandingPageActivity: pid=26929 uid=10146 gids={50146, 9997, 3003, 1028, 1015} abi=armeabi-v7a
D/AndroidRuntime(26929): Shutting down VM
E/AndroidRuntime(26929): FATAL EXCEPTION: main
E/AndroidRuntime(26929): Process: com.nisk.arcticfrolfing, PID: 26929
E/AndroidRuntime(26929): java.lang.RuntimeException: Unable to create application com.nisk.arcticfrolfing.SnapchatApplication: java.lang.IllegalArgumentException: No inject registered for members/com.nisk.arcticfrolfing.SnapchatApplication. You must explicitly add it to the 'injects' option in one of your modules.
E/AndroidRuntime(26929): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4521)
E/AndroidRuntime(26929): at android.app.ActivityThread.access$1500(ActivityThread.java:144)
E/AndroidRuntime(26929): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1339)
E/AndroidRuntime(26929): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime(26929): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime(26929): at android.app.ActivityThread.main(ActivityThread.java:5221)
E/AndroidRuntime(26929): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime(26929): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime(26929): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:899)
E/AndroidRuntime(26929): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:694)
E/AndroidRuntime(26929): Caused by: java.lang.IllegalArgumentException: No inject registered for members/com.nisk.arcticfrolfing.SnapchatApplication. You must explicitly add it to the 'injects' option in one of your modules.
E/AndroidRuntime(26929): at dagger.ObjectGraph$DaggerObjectGraph.a(SourceFile:302)
E/AndroidRuntime(26929): at dagger.ObjectGraph$DaggerObjectGraph.a(SourceFile:279)
E/AndroidRuntime(26929): at com.nisk.arcticfrolfing.SnapchatApplication.onCreate(SourceFile:57)
E/AndroidRuntime(26929): at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1011)
E/AndroidRuntime(26929): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4518)
E/AndroidRuntime(26929): ... 9 more
W/ActivityManager(12510): Force finishing activity com.nisk.arcticfrolfing/.LandingPageActivity
I/OpenGLRenderer(12510): Initialized EGL, version 1.4
W/ActivityManager(12510): Activity pause timeout for ActivityRecord{2ef8f42b u0 com.nisk.arcticfrolfing/.LandingPageActivity t306 f}
I/Process (26929): Sending signal. PID: 26929 SIG: 9
D/audio_hw_primary(12289): out_set_parameters: enter: usecase(1: low-latency-playback) kvpairs: routing=2
W/InputMethodManagerService(12510): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
I/ActivityManager(12510): Process com.nisk.arcticfrolfing (pid 26929) has died
The problem seems to be the line "You must explicitly add it to the 'injects' option in one of your modules." What does this mean? Can I fix this using just apktool or do I need access to the original source code?
Hello everyone,
I hope thats the correct forum to post this question. I tried to find something through google search but it seems that there are only some stackoverflow development questions on that topic, which do not help a lot.
I have a MI9 (MIUI Global 10.2.30 stable) without root. Now I wanted to remove some default system apps and found this tool here: github.com/Saki-EU/XiaomiADBFastbootTools/releases/tag/6.6.2
I followed this list (and tailored it to my own needs): gist.github.com/Biswa96/81fe477079fa5279f7cfd7b98d5519c7
After finishing my de-bloating I realized that Google Calender (and also system calender) does not start any more. All I get is the error message "Failed to find provider com.android.calendar for user 0; expected to find a valid ContentProvider for this authority"
I tried to reinstall Google Calendar (and also all the removed bloat apps) but it doesn't help. Here is also the log file from adb logcat:
Code:
09-24 17:07:29.395 1441 2654 I ActivityManager: Start proc 29460:com.google.android.calendar/u0a99 for service com.google.android.calendar/com.google.android.syncadapters.calendar.CalendarSyncAdapterService caller=android
09-24 17:07:29.396 4352 4472 D PowerKeeper.Event: notifyAMProcStart processName: 10099 reason: com.google.android.calendar, pid:0
09-24 17:07:29.397 28323 28323 D Cal:D:AllInOne: onStart()
09-24 17:07:29.397 28323 28323 D Cal:D:AllInOne: onResume()
09-24 17:07:29.398 28323 29459 I Cal:D:Utils: setGoogleAccountsSyncable(): NOT syncable before, set it syncable
09-24 17:07:29.400 28323 28323 D AndroidRuntime: Shutting down VM
09-24 17:07:29.400 28323 29465 I FA : Tag Manager is not found and thus will not be used
09-24 17:07:29.400 28323 28323 E AndroidRuntime: FATAL EXCEPTION: main
09-24 17:07:29.400 28323 28323 E AndroidRuntime: Process: com.android.calendar, PID: 28323
09-24 17:07:29.400 28323 28323 E AndroidRuntime: java.lang.RuntimeException: Unable to resume activity {com.android.calendar/com.android.calendar.homepage.AllInOneActivity}: java.lang.SecurityException: Failed to find provider com.android.calendar for user 0; expected to find a valid ContentProvider for this authority
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3828)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3860)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:51)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:145)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:70)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1831)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.os.Looper.loop(Looper.java:201)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6815)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:547)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:873)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: Caused by: java.lang.SecurityException: Failed to find provider com.android.calendar for user 0; expected to find a valid ContentProvider for this authority
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.os.Parcel.createException(Parcel.java:1950)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1918)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1868)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.content.IContentService$Stub$Proxy.registerContentObserver(IContentService.java:779)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.content.ContentResolver.registerContentObserver(ContentResolver.java:1988)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.content.ContentResolver.registerContentObserver(ContentResolver.java:1977)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at com.android.calendar.homepage.AllInOneActivity.onResume(AllInOneActivity.java:571)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1413)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.app.Activity.performResume(Activity.java:7400)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3820)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: ... 11 more
09-24 17:07:29.400 28323 28323 E AndroidRuntime: Caused by: android.os.RemoteException: Remote stack trace:
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at com.android.server.content.ContentService.registerContentObserver(ContentService.java:340)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.content.IContentService$Stub.onTransact(IContentService.java:76)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at com.android.server.content.ContentService.onTransact(ContentService.java:262)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.os.Binder.execTransact(Binder.java:733)
09-24 17:07:29.400 28323 28323 E AndroidRuntime:
09-24 17:07:29.401 28323 29459 I Cal:D:Utils: setGoogleAccountsSyncable(): NOT syncable before, set it syncable
09-24 17:07:29.402 589 589 E SELinux : avc: denied { find } for service=miui.mqsas.MQSService pid=28323 uid=10024 scontext=u:r:priv_app:s0:c512,c768 tcontext=u:object_r:mqs_service:s0 tclass=service_manager permissive=0
09-24 17:07:29.402 28323 28323 E MQSEventManagerDelegate: failed to get MQSService.
09-24 17:07:29.403 4352 4472 D PowerKeeper.Event: notifyAMCrash packageName: 0, pid:28323
09-24 17:07:29.403 29460 29460 E ndroid.calenda: Not starting debugger since process cannot load the jdwp agent.
09-24 17:07:29.404 1441 3632 W ActivityManager: Force finishing activity com.android.calendar/.homepage.AllInOneActivity
09-24 17:07:29.405 1441 3632 D ActivityTrigger: ActivityTrigger activityPauseTrigger
09-24 17:07:29.407 28323 28323 I Process : Sending signal. PID: 28323 SIG: 9
09-24 17:07:29.407 1441 3527 D ActivityManager: report kill process: killerPid is:28323, killedPid is:28323
Does anyone has an idea how to fix it?
I had the same issue... I managed to solve it.
Code:
pm install-existing com.android.providers.calendar