Ive been having nightmares with a 128 GB SDCard that had been going fine till I decided I wanted to format it as mixed. I did this using adb and my Marshmallow phone. At first it all went well but then I decided I wanted to tweak the mix and put a bit more as shared (rather than adopted), this time I was using a 7.1.2 ROM (and adb) and thats when the nightmares started.
I have managed a couple of times to reformat it so the phone will accept it but the thing seems very fragile. I just have to squint at it and suddenly - its corrupted.
So Im trying to work out if there is something wrong with it or if its a software issue - here is some logcat that may be relevant - captured while im trying to partition the card with:
Code:
adb shell sm partition disk:179,64 private
Could somebody help me understand what this log is telling us?
Code:
07-31 04:05:15.754 30095 30095 D AndroidRuntime: >>>>>> START com.android.internal.os.RuntimeInit uid 2000 <<<<<<
07-31 04:05:15.763 30095 30095 D AndroidRuntime: CheckJNI is OFF
07-31 04:05:15.825 30095 30095 D ICU : No timezone override file found: /data/misc/zoneinfo/current/icu/icu_tzdata.dat
07-31 04:05:15.873 30095 30095 I Radio-JNI: register_android_hardware_Radio DONE
07-31 04:05:15.902 30095 30095 D AndroidRuntime: Calling main entry com.android.commands.sm.Sm
07-31 04:05:15.905 1928 7704 D VoldConnector: SND -> {199 volume partition disk:179,64 private}
07-31 04:05:15.905 275 281 V vold : /system/bin/sgdisk
07-31 04:05:15.905 275 281 V vold : --zap-all
07-31 04:05:15.905 275 281 V vold : /dev/block/vold/disk:179,64
07-31 04:05:15.900 7704 7704 I Binder_B: type=1400 audit(0.0:1122): avc: denied { getopt } for scontext=u:r:system_server:s0 tcontext=u:r:init:s0 tclass=unix_dgram_socket permissive=1
07-31 04:05:15.900 7704 7704 I Binder_B: type=1400 audit(0.0:1123): avc: denied { write } for path="socket:[12111]" dev="sockfs" ino=12111 scontext=u:r:system_server:s0 tcontext=u:r:init:s0 tclass=unix_dgram_socket permissive=1
........
07-31 04:06:09.184 275 281 I sgdisk : Warning: The kernel is still using the old partition table.
07-31 04:06:09.184 275 281 I sgdisk : The new table will be used at the next reboot.
07-31 04:06:09.185 275 281 I sgdisk : GPT data structures destroyed! You may now partition the disk using fdisk or
07-31 04:06:09.185 275 281 I sgdisk : other utilities.
......
07-31 04:06:15.906 1928 7704 E NativeDaemonConnector.ResponseQueue: Timeout waiting for response
07-31 04:06:15.906 1928 7704 E VoldConnector: timed-out waiting for response to 199 volume partition disk:179,64 private
07-31 04:06:15.909 30095 30095 E Sm : Error
07-31 04:06:15.909 30095 30095 E Sm : java.lang.IllegalStateException: command '199 volume partition disk:179,64 private' failed with 'null'
07-31 04:06:15.909 30095 30095 E Sm : at android.os.Parcel.readException(Parcel.java:1628)
07-31 04:06:15.909 30095 30095 E Sm : at android.os.Parcel.readException(Parcel.java:1573)
07-31 04:06:15.909 30095 30095 E Sm : at android.os.storage.IMountService$Stub$Proxy.partitionPrivate(IMountService.java:1067)
07-31 04:06:15.909 30095 30095 E Sm : at com.android.commands.sm.Sm.runPartition(Sm.java:145)
07-31 04:06:15.909 30095 30095 E Sm : at com.android.commands.sm.Sm.run(Sm.java:77)
07-31 04:06:15.909 30095 30095 E Sm : at com.android.commands.sm.Sm.main(Sm.java:40)
07-31 04:06:15.909 30095 30095 E Sm : at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
07-31 04:06:15.909 30095 30095 E Sm : at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:251)
07-31 04:06:15.912 30095 30095 I art : System.exit called, status: 1
07-31 04:06:15.912 30095 30095 I AndroidRuntime: VM exiting with result code 1.
Related
I have an Lg G5 (H850), unrooted and fully up to date.
A few months ago I began to have trouble with the Clock app. It crashes several times during use.
I've been able to deduce that this problem occurs when Android Wear is installed, and it makes no difference if my Lg G Watch R is connected to my phone or not.
Another event that seems to trigger Clock crashing is when my phone toggles between service and WiFi, but I cannot be sure if that's the cause.
Here are the failed solutions I've tried:
- Install previous version of Android Wear dating back to before the issue started
- Cleared Data/Cache from Clock app
- Tried to disable Clock, but button is grayed out
- Installed Google Clock. Made no difference
- Disconnected watch, but problem persists
- Reset the watch to manufacturer's
I should add (although I am not sure it's a bug) that every time I clear data/cash from Clock, a new alarm appears set (though tuned off) at 7:00 am January 1st. I've never set this alarm, and whether I leave it there, delete it or switch it on and off (so it changes to current date) doesn't make a difference.
I am including a copy of LogCat that shows the crash. Unfortunately I do not know what to do with the information it provides.
Thanks for any help anyone can provide.
--------- beginning of crash
07-31 10:26:09.541 10690 10690 E AndroidRuntime: FATAL EXCEPTION: main
07-31 10:26:09.541 10690 10690 E AndroidRuntime: Process: com.lge.clock, PID: 10690
07-31 10:26:09.541 10690 10690 E AndroidRuntime: java.lang.IllegalArgumentException: Receiver not registered: [email protected]
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at android.app.LoadedApk.forgetReceiverDispatcher(LoadedApk.java:1047)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at android.app.ContextImpl.unregisterReceiver(ContextImpl.java:1332)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at android.content.ContextWrapper.unregisterReceiver(ContextWrapper.java:608)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.google.android.gms.common.api.c.gM(Unknown Source)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.google.android.gms.common.api.c.gJ(Unknown Source)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.google.android.gms.common.api.c.d(Unknown Source)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.google.android.gms.common.api.c$2.onConnected(Unknown Source)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.google.android.gms.internal.jm.f(Unknown Source)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.google.android.gms.internal.jm.dU(Unknown Source)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.google.android.gms.internal.jl$h.b(Unknown Source)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.google.android.gms.internal.jl$h.g(Unknown Source)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.google.android.gms.internal.jl$b.hy(Unknown Source)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.google.android.gms.internal.jl$a.handleMessage(Unknown Source)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6247)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:872)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:762)
Unexpected solution
After months of fiddling with this problem, I accidentally came across information that lead me to solve another problem and through it; fixing this issue I described.
Kinda silly to answer my own post, but it might help people out there.
While live monitoring Logcat, I decided to toggle WiFi on and off to see what the phone did. My Lg G5 has always been pretty slow to connect.
I noticed that, upon turning WiFi on, my phone went through the whole list of "saved" networks before even attempting to connect to the available ones.
I had a LOAD of saved networks. Most of them from countries I visited.
I cleaned up the list, removing most networks I had saved et voila! Not only did my phone started connecting to WiFi instantly, but my clock app stopped crashing.
I hope this helps someone out there.
I have a tv box with s905x running android 7.1.2. When i try to use different launcher than default (droidlogic mbox launcher), it force close it.
I searce the android log and i found that the error is probably with wallpaper manager. I have found that many people with tv boxes have the same problem.
Also if i try to put a wallpaper with an wallpaper app it crashes too.
The error is that WallpaperService not running.
How can i solve that?
Code:
9-05 20:22:06.328 4371 5498 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x13200000 cmp=net.pierrox.lightning_launcher_extreme/net.pierrox.lightning_launcher.activities.Dashboard (has extras)} from uid 1000 on display 0
09-05 20:22:06.400 4371 4526 I ActivityManager: Start proc 11428:net.pierrox.lightning_launcher_extreme/u0a50 for activity net.pierrox.lightning_launcher_extreme/net.pierrox.lightning_launcher.activities.Dashboard
09-05 20:22:06.512 4371 8711 W Binder : Binder call failed.
09-05 20:22:06.512 4371 8711 W Binder : java.lang.SecurityException: Neither user 1041 nor current process has android.permission.WAKE_LOCK.
09-05 20:22:06.512 4371 8711 W Binder : at android.app.ContextImpl.enforce(ContextImpl.java:1585)
09-05 20:22:06.512 4371 8711 W Binder : at android.app.ContextImpl.enforceCallingOrSelfPermission(ContextImpl.java:1617)
09-05 20:22:06.512 4371 8711 W Binder : at com.android.server.power.PowerManagerService$BinderService.updateWakeLockWorkSource(PowerManagerService.java:3453)
09-05 20:22:06.512 4371 8711 W Binder : at com.android.server.power.PowerManagerService$BinderService.updateWakeLockUids(PowerManagerService.java:3444)
09-05 20:22:06.512 4371 8711 W Binder : at android.os.IPowerManager$Stub.onTransact(IPowerManager.java:105)
09-05 20:22:06.512 4371 8711 W Binder : at android.os.Binder.execTransact(Binder.java:565)
09-05 20:22:06.514 4371 4642 I WindowManager: mLongPressOnHomeBehavior = 0
09-05 20:22:06.585 11428 11428 I art : Starting a blocking GC AddRemoveAppImageSpace
09-05 20:22:06.586 4371 4380 I art : Background partial concurrent mark sweep GC freed 13995(815KB) AllocSpace objects, 0(0B) LOS objects, 33% free, 8MB/13MB, paused 2.095ms total 126.137ms
09-05 20:22:06.586 11428 11428 W System : ClassLoader referenced unknown path: /system/lib/LightningLauncher
09-05 20:22:06.742 11428 11444 E ActivityThread: Failed to find provider info for net.pierrox.lightning_launcher.lwp_key
09-05 20:22:06.880 11428 11428 I auncher_extreme: type=1400 audit(0.0:297): avc: denied { read write } for name="gsm" dev="tmpfs" ino=10303 scontext=u:r:priv_app:s0:c512,c768 tcontext=u:object_r:gsm_device:s0 tclass=chr_file permissive=1
09-05 20:22:06.880 11428 11428 I auncher_extreme: type=1400 audit(0.0:298): avc: denied { open } for path="/dev/gsm" dev="tmpfs" ino=10303 scontext=u:r:priv_app:s0:c512,c768 tcontext=u:object_r:gsm_device:s0 tclass=chr_file permissive=1
09-05 20:22:07.368 11428 11428 W WallpaperManager: WallpaperService not running
09-05 20:22:07.369 11428 11428 E AndroidRuntime: FATAL EXCEPTION: main
09-05 20:22:07.369 11428 11428 E AndroidRuntime: Process: net.pierrox.lightning_launcher_extreme, PID: 11428
09-05 20:22:07.369 11428 11428 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
09-05 20:22:07.373 4371 4920 W ActivityManager: Force finishing activity net.pierrox.lightning_launcher_extreme/net.pierrox.lightning_launcher.activities.Dashboard
I started android 8.1 treble and l also have a problem with droidlogic .
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.c} 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.
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
Hello,
I'm using a Moto G5s+ (sanders). For this phone, ArrowOS has been in use since Feb. 2021, and I have always been able to buy a subway ticket using the local operator's app MVG Fahrinfo[1].
This worked until at least May 15th, 2022.
In between, ArrowOs ceaded to support Android-11 (and this phone in generel), which is why I'm now updating the ArrowOS-11 code using the AOSP-Security Updates.
I know, I've updated the app in May or June, but I haven't used until June 3rd, when I noticed, that the MVG Fahrinfo crashes completely when I try to buy a ticket. I don't know, if or what they've changed. But moving my ArrowOS image back to a version that was definitely working did not help.
Using adb logcat, I get the following trace:
Code:
07-13 07:33:34.730 481 481 I qseecomd: type=1400 audit(0.0:2922): avc: denied { ioctl } for uid=1000 path="/dev/block/mmcblk0rpmb" dev="tmpfs" ino=2367 ioctlcmd=b300 scontext=u:r:init:s0 tcontext=u:object_r:block_device:s0 tclass=blk_file permissive=1
07-13 07:33:34.741 1974 9203 W keystore: Trying to serialize unknown tag 1879048895. Did you forget to add it to all_tags_t?
07-13 07:33:34.831 1974 1974 I keystore: del USRPKEY_a9fa3a48-b564-4a15-9810-ab0c00e54249 10209
07-13 07:33:34.831 1974 1974 I keystore: del USRCERT_a9fa3a48-b564-4a15-9810-ab0c00e54249 10209
07-13 07:33:34.832 1974 1974 I keystore: del CACERT_a9fa3a48-b564-4a15-9810-ab0c00e54249 10209
07-13 07:33:34.830 481 481 I qseecomd: type=1400 audit(0.0:2923): avc: denied { ioctl } for uid=1000 path="/dev/block/mmcblk0rpmb" dev="tmpfs" ino=2367 ioctlcmd=b300 scontext=u:r:init:s0 tcontext=u:object_r:block_device:s0 tclass=blk_file permissive=1
07-13 07:33:35.023 8070 8082 I hrinfo.muenche: Background young concurrent copying GC freed 235652(12MB) AllocSpace objects, 234(14MB) LOS objects, 45% free, 31MB/58MB, paused 181us total 104.730ms
07-13 07:33:35.064 8070 8092 D TransportRuntime.SQLiteEventStore: Storing event with priority=HIGHEST, name=FIREBASE_CRASHLYTICS_REPORT for destination cct
07-13 07:33:35.097 8070 8092 D TransportRuntime.JobInfoScheduler: Scheduling upload for context TransportContext(cct, HIGHEST, MSRodHRwczovL2NyYXNobHl0aWNzcmVwb3J0cy1wYS5nb29nbGVhcGlzLmNvbS92MS9maXJlbG9nL2xlZ2FjeS9iYXRjaGxvZ1xBSXphU3lCcnBTWVQ0RkZMMDlyZUhKaTZIOUZZZGVpU25VVE92Mk0=) with jobId=1899902110 in 1000ms(Backend next call timestamp 1657115477558). Attempt 1
--------- beginning of crash
07-13 07:33:35.113 8070 8070 E AndroidRuntime: FATAL EXCEPTION: main
07-13 07:33:35.113 8070 8070 E AndroidRuntime: Process: de.swm.mvgfahrinfo.muenchen, PID: 8070
07-13 07:33:35.113 8070 8070 E AndroidRuntime: java.security.ProviderException: Failed to generate attestation certificate chain
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at android.security.keystore.AndroidKeyStoreKeyPairGeneratorSpi.getAttestationChain(AndroidKeyStoreKeyPairGeneratorSpi.java:611)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at android.security.keystore.AndroidKeyStoreKeyPairGeneratorSpi.createCertificateChain(AndroidKeyStoreKeyPairGeneratorSpi.java:498)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at android.security.keystore.AndroidKeyStoreKeyPairGeneratorSpi.generateKeyPair(AndroidKeyStoreKeyPairGeneratorSpi.java:475)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at java.security.KeyPairGenerator$Delegate.generateKeyPair(KeyPairGenerator.java:727)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at b.b(Unknown Source:28)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at c$a.invokeSuspend(SourceFile:6)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(SourceFile:4)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at kotlinx.coroutines.DispatchedTask.run(SourceFile:22)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:938)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at android.os.Looper.loop(Looper.java:223)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7665)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:594)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: Caused by: android.security.KeyStoreException: Not implemented
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at android.security.KeyStore.getKeyStoreException(KeyStore.java:1306)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: ... 15 more
07-13 07:33:35.116 2534 9249 I DropBoxManagerService: add tag=data_app_crash isTagEnabled=true flags=0x2
07-13 07:33:35.117 2534 6885 W ActivityTaskManager: Force finishing activity de.swm.mvgfahrinfo.muenchen/.mobilityticketing.MobilityTicketingActivity
Therefore, it seems to me, that either
the app has changed and now requests something, that it did not before: but then, why does not work now?
my ArrowOs image (one I created myself, adding AOSP's security updates) changed/deleted something, that does not get restored switching to another image
something else?
Can you help me out? Please do not hesitate to ask, if you need anything else to debug.
Thanks a lot in advance.
kniffte
1: https://play.google.com/store/apps/details?id=de.swm.mvgfahrinfo.muenchen&hl=de&gl=US