Need urgent help with Titanium Backup - Android Q&A, Help & Troubleshooting

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.

Related

[Q] Potential issue with Webtop mod for 4.5.91 - com.android.phone FC

Too new to post in the dev forums, but i wanted to post my experience with the Webtop Mod (http://forum.xda-developers.com/showthread.php?t=980193) specifically using the 4.5.91 files downloaded from (http://forum.xda-developers.com/showpost.php?p=15881436&postcount=834) in case any others are having this issue, and maybe to get some feedback from the mod devs, as I'd like to use this mod on my phone.
I noticed after replacing the stock APKs i started getting FC's when making and receiving phone calls, after pulling a logcat log from my phone, it seems the modded PortalApp.apk is at fault (log snippet below) i reverted to the stock PortalApp.apk and phone calls started working again.
Code:
09-07 18:42:15.665 1672 3590 I ActivityManager: Starting: Intent { act=android.intent.action.CALL dat=tel:xxx-xxx-xxxx flg=0x10000000 cmp=com.android.phone/.InCallScreen (has extras) } from pid 8281
09-07 18:42:16.615 3086 3086 D StatusBarService: enter playAnimationStatusBar, enable = false
09-07 18:42:16.635 1672 3007 D InputManager: phone state:2
09-07 18:42:16.995 8281 8281 E AndroidRuntime: FATAL EXCEPTION: main
09-07 18:42:16.995 8281 8281 E AndroidRuntime: java.lang.RuntimeException: Unable to instantiate receiver com.android.portal.IntentProxyReceiverForCallState: java.lang.ClassNotFoundException: com.android.portal.IntentProxyReceiverForCallState in loader dalvik.system.PathClassLoader[/system/framework/com.motorola.android.iextdispservice.jar:/system/framework/com.motorola.android.imirrorservice.jar:/system/app/PortalApp.apk]
09-07 18:42:16.995 8281 8281 E AndroidRuntime: at android.app.ActivityThread.handleReceiver(ActivityThread.java:1826)
09-07 18:42:16.995 8281 8281 E AndroidRuntime: at android.app.ActivityThread.access$2400(ActivityThread.java:124)
09-07 18:42:16.995 8281 8281 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1018)
09-07 18:42:16.995 8281 8281 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
09-07 18:42:16.995 8281 8281 E AndroidRuntime: at android.os.Looper.loop(Looper.java:130)
09-07 18:42:16.995 8281 8281 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:3806)
09-07 18:42:16.995 8281 8281 E AndroidRuntime: at java.lang.reflect.Method.invokeNative(Native Method)
09-07 18:42:16.995 8281 8281 E AndroidRuntime: at java.lang.reflect.Method.invoke(Method.java:507)
09-07 18:42:16.995 8281 8281 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:839)
09-07 18:42:16.995 8281 8281 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
09-07 18:42:16.995 8281 8281 E AndroidRuntime: at dalvik.system.NativeStart.main(Native Method)
09-07 18:42:16.995 8281 8281 E AndroidRuntime: Caused by: java.lang.ClassNotFoundException: com.android.portal.IntentProxyReceiverForCallState in loader dalvik.system.PathClassLoader[/system/framework/com.motorola.android.iextdispservice.jar:/system/framework/com.motorola.android.imirrorservice.jar:/system/app/PortalApp.apk]
09-07 18:42:16.995 8281 8281 E AndroidRuntime: at dalvik.system.PathClassLoader.findClass(PathClassLoader.java:240)
09-07 18:42:16.995 8281 8281 E AndroidRuntime: at java.lang.ClassLoader.loadClass(ClassLoader.java:551)
09-07 18:42:16.995 8281 8281 E AndroidRuntime: at java.lang.ClassLoader.loadClass(ClassLoader.java:511)
09-07 18:42:16.995 8281 8281 E AndroidRuntime: at android.app.ActivityThread.handleReceiver(ActivityThread.java:1817)
09-07 18:42:16.995 8281 8281 E AndroidRuntime: ... 10 more
09-07 18:42:17.015 1672 3590 W ActivityManager: Process com.android.phone has crashed too many times: killing!

Problem with camera

Hello all,
I just started having a problem with my camera on the RazR today. I tried doing a full reset of the phone, but I still cant get it to open. I ran a logcat on the phone when I tried opening the camera again. This is what I got.
Code:
08-17 22:11:15.884 6585 6585 D MotoCamSettingBack: setCurrentAppMode CamSettingBack
08-17 22:11:15.884 6585 6585 D MotoCamSettingFront: setCurrentAppMode CamSettingFront
08-17 22:11:15.884 6585 7193 D CameraHolder: open camera 0 mCameraDevice: null mCameraId: -1
08-17 22:11:15.884 6585 7193 D CameraHolder: open camera 0
08-17 22:11:15.884 166 524 E CameraService: CameraService::connect X (pid 6585) rejected (invalid cameraId 0).
08-17 22:11:15.892 6585 7193 E CameraHolder: fail to connect Camera
08-17 22:11:15.892 6585 7193 E CameraHolder: java.lang.RuntimeException: Fail to connect to camera service
08-17 22:11:15.892 6585 7193 E CameraHolder: at android.hardware.Camera.native_setup(Native Method)
08-17 22:11:15.892 6585 7193 E CameraHolder: at android.hardware.Camera.<init>(Camera.java:317)
08-17 22:11:15.892 6585 7193 E CameraHolder: at android.hardware.Camera.open(Camera.java:274)
08-17 22:11:15.892 6585 7193 E CameraHolder: at com.motorola.Camera.CameraHolder.open(CameraHolder.java:131)
08-17 22:11:15.892 6585 7193 E CameraHolder: at com.motorola.Camera.Camera.openCamera(Camera.java:449)
08-17 22:11:15.892 6585 7193 E CameraHolder: at com.motorola.Camera.Camera.startDevice(Camera.java:411)
08-17 22:11:15.892 6585 7193 E CameraHolder: at com.motorola.Camera.Camera.access$900(Camera.java:144)
08-17 22:11:15.892 6585 7193 E CameraHolder: at com.motorola.Camera.Camera$1.run(Camera.java:1110)
08-17 22:11:15.892 6585 7193 E CameraHolder: at java.lang.Thread.run(Thread.java:856)
08-17 22:11:15.892 6585 7193 E MotoCamera: openCamera() - failed to open camera
I'm hoping that this isn't a problem with the camera itself, but it looks like it could be. Any input is appreciated.
Go
config / aplications / all apps / camera
Then clear cache / data.
Done.
Cheers
Edit.
You have probably a corrupted pic causing the issue. The above procedure will probably fix it. Let me know what you get.
Sent from my XT910 using xda premium
Thanks bro, that got it working again.
theintrepid1 said:
Thanks bro, that got it working again.
Click to expand...
Click to collapse
I have exactly the same problem.
Did you clear the cache in settings, applications, all apps and camera to make it work again ?
I have done that but my camera is still not working
I too cleared cache/data and closed camera to no avail.
here i have problem too, but with Razr i

SDCard corrupted, wont format, slow to read

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.

Calender app does not work after de-bloating Xiaomi Mi 9

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

WfdService Fix for all AOSP ROMS

Hi there,
add these proprietrary files to your device tree :
/system/lib/libFileMux.so
/system/lib64/libFileMux.so
/product/lib/[email protected]
/product/lib64/[email protected]
janhammer504 said:
Hi there,
add these proprietrary files to your device tree :
/system/lib/libFileMux.so
/system/lib64/libFileMux.so
/product/lib/[email protected]
/product/lib64/[email protected]
Click to expand...
Click to collapse
Is this for broadcast ?
Wtf is that
noskojv said:
Is this for broadcast ?
Click to expand...
Click to collapse
for wifidisplay ... this is for ROM devs not for final users !
janhammer504 said:
for wifidisplay ... this is for ROM devs not for final users !
Click to expand...
Click to collapse
nitrogenos I don't have such files in the system but wifidisplay works.
Module for magisk
noskojv said:
Module for magisk
Click to expand...
Click to collapse
Quick question: is your module an end-user fix for anyone on an AOSP-based ROM which doesn't already include the fix?
noskojv said:
Module for magisk
Click to expand...
Click to collapse
Thanks for this!
on arrow os didnt work wdf service error again i go back to my pixel 10 rom works fine without trics but its android 10
nikolas60 said:
on arrow os didnt work wdf service error again i go back to my pixel 10 rom works fine without trics but its android 10
Click to expand...
Click to collapse
Did you use the magisk module provided on this thread?
yes man of course i have poco x3 nfc
arrow android 11
nikolas60 said:
arrow android 11
Click to expand...
Click to collapse
Maybe it does not work with Android 11 at all?
Just tested with crDroid 7.2 (Android 11) and its not working.
Does it work on eu rom or elite rom?
Or only for Aosp
The magisk module is not working in my case.
Helppp
janhammer504 said:
Hi there,
add these proprietrary files to your device tree :
Click to expand...
Click to collapse
I
I have them right but no way to make wft work.
heartbr said:
I
I have them right but no way to make wft work.
Click to expand...
Click to collapse
check the symlink for the lib in the wfd apk folder
Good afternoon everyone! As for the screen broadcast (Miracast), when connected to the TV, it gives an error, "The Wfd Service application crashed again." Does anyone know a solution to these problems? I have root access. Motorola Moto G6 ali, ROM: Pixel Experience 11. Many thanks to everyone!
Do you have a fix for this?
Razer Phone 2 (aura) on LineageOS for MicroG 19.1
Tried finding this missing library but no luck so far.
During a short stint on /e/OS, this worked fine. The only hint I found is that it might be a proprietary (vendor) file.
Help appreciated
Code:
06-20 17:31:13.941 1532 1532 E LightsService: Light requested not available on this device. 2
06-20 17:31:14.223 941 2915 E msm8974_platform: platform_check_backends_match: Invalid snd_device =
06-20 17:31:14.227 941 2915 E ACDB-LOADER: Error: ACDB_CMD_GET_AFE_COMMON_TABLE_SIZE Returned = -19
06-20 17:31:14.227 941 2915 E ACDB-LOADER: Error: ACDB AFE returned = -19
06-20 17:31:14.319 6443 6443 E ice:wfd_servic: Not starting debugger since process cannot load the jdwp agent.
06-20 17:31:14.404 6443 6458 E JavaBinder: *** Uncaught remote exception! (Exceptions are not yet supported across processes.)
06-20 17:31:14.404 6443 6458 E JavaBinder: java.lang.UnsatisfiedLinkError: dlopen failed: library "libmmosal.so" not found: needed by /system/system_ext/lib64/libwfdclient.so in namespace classloader-namespace-shared
06-20 17:31:14.404 6443 6458 E JavaBinder: at java.lang.Runtime.loadLibrary0(Runtime.java:1077)
06-20 17:31:14.404 6443 6458 E JavaBinder: at java.lang.Runtime.loadLibrary0(Runtime.java:998)
06-20 17:31:14.404 6443 6458 E JavaBinder: at java.lang.System.loadLibrary(System.java:1656)
06-20 17:31:14.404 6443 6458 E JavaBinder: at com.qualcomm.wfd.WFDSession.<clinit>(WFDSession.java:56)
06-20 17:31:14.404 6443 6458 E JavaBinder: at com.qualcomm.wfd.WFDSession.createWFDSession(WFDSession.java:403)
06-20 17:31:14.404 6443 6458 E JavaBinder: at com.qualcomm.wfd.service.SessionManagerService.setDeviceType(SessionManagerService.java:175)
06-20 17:31:14.404 6443 6458 E JavaBinder: at com.qualcomm.wfd.service.ISessionManagerService$Stub.onTransact(ISessionManagerService.java:655)
06-20 17:31:14.404 6443 6458 E JavaBinder: at android.os.Binder.execTransactInternal(Binder.java:1184)
06-20 17:31:14.404 6443 6458 E JavaBinder: at android.os.Binder.execTransact(Binder.java:1143)
06-20 17:31:14.404 6443 6458 E AndroidRuntime: FATAL EXCEPTION: Binder:6443_2
06-20 17:31:14.404 6443 6458 E AndroidRuntime: Process: com.qualcomm.wfd.service:wfd_service, PID: 6443
06-20 17:31:14.404 6443 6458 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: library "libmmosal.so" not found: needed by /system/system_ext/lib64/libwfdclient.so in namespace classloader-namespace-shared
06-20 17:31:14.404 6443 6458 E AndroidRuntime: at java.lang.Runtime.loadLibrary0(Runtime.java:1077)
06-20 17:31:14.404 6443 6458 E AndroidRuntime: at java.lang.Runtime.loadLibrary0(Runtime.java:998)
06-20 17:31:14.404 6443 6458 E AndroidRuntime: at java.lang.System.loadLibrary(System.java:1656)
06-20 17:31:14.404 6443 6458 E AndroidRuntime: at com.qualcomm.wfd.WFDSession.<clinit>(WFDSession.java:56)
06-20 17:31:14.404 6443 6458 E AndroidRuntime: at com.qualcomm.wfd.WFDSession.createWFDSession(WFDSession.java:403)
06-20 17:31:14.404 6443 6458 E AndroidRuntime: at com.qualcomm.wfd.service.SessionManagerService.setDeviceType(SessionManagerService.java:175)
06-20 17:31:14.404 6443 6458 E AndroidRuntime: at com.qualcomm.wfd.service.ISessionManagerService$Stub.onTransact(ISessionManagerService.java:655)
06-20 17:31:14.404 6443 6458 E AndroidRuntime: at android.os.Binder.execTransactInternal(Binder.java:1184)
06-20 17:31:14.404 6443 6458 E AndroidRuntime: at android.os.Binder.execTransact(Binder.java:1143)
06-20 17:31:14.419 6464 6464 F linker : CANNOT LINK EXECUTABLE "/system_ext/bin/wfdservice": library "libmmosal.so" not found: needed by main executable
06-20 17:31:14.425 1532 6442 E ExtendedRemoteDisplay: WfdService init() failed
06-20 17:31:14.425 1532 6442 E ExtendedRemoteDisplay: android.os.DeadObjectException
06-20 17:31:14.425 1532 6442 E ExtendedRemoteDisplay: at android.os.BinderProxy.transactNative(Native Method)
06-20 17:31:14.425 1532 6442 E ExtendedRemoteDisplay: at android.os.BinderProxy.transact(BinderProxy.java:571)
06-20 17:31:14.425 1532 6442 E ExtendedRemoteDisplay: at com.qualcomm.wfd.service.ISessionManagerService$Stub$Proxy.setDeviceType(ISessionManagerService.java:1210)
06-20 17:31:14.425 1532 6442 E ExtendedRemoteDisplay: at com.qualcomm.wfd.ExtendedRemoteDisplay$ExtendedRemoteDisplayHandler.handleMessage(ExtendedRemoteDisplay.java:770)
06-20 17:31:14.425 1532 6442 E ExtendedRemoteDisplay: at android.os.Handler.dispatchMessage(Handler.java:106)
06-20 17:31:14.425 1532 6442 E ExtendedRemoteDisplay: at android.os.Looper.loopOnce(Looper.java:201)
06-20 17:31:14.425 1532 6442 E ExtendedRemoteDisplay: at android.os.Looper.loop(Looper.java:288)
06-20 17:31:14.425 1532 6442 E ExtendedRemoteDisplay: at android.os.HandlerThread.run(HandlerThread.java:67)
06-20 17:31:14.425 1532 6442 E ExtendedRemoteDisplay: Why on earth is surface null??
06-20 17:31:14.486 3465 3465 E .ss.squarehome: Invalid ID 0x00000000.
06-20 17:31:14.487 3465 3465 E .ss.squarehome: Invalid ID 0x00000000.
06-20 17:31:14.489 3465 3465 E .ss.squarehome: Invalid ID 0x00000000.
06-20 17:31:14.490 3465 3465 E .ss.squarehome: Invalid ID 0x00000000.
06-20 17:31:14.491 3465 3465 E .ss.squarehome: Invalid ID 0x00000000.
06-20 17:31:15.590 6466 6466 E ice:wfd_servic: Not starting debugger since process cannot load the jdwp agent.
06-20 17:31:15.639 6466 6481 E JavaBinder: *** Uncaught remote exception! (Exceptions are not yet supported across processes.)
06-20 17:31:15.639 6466 6481 E JavaBinder: java.lang.UnsatisfiedLinkError: dlopen failed: library "libmmosal.so" not found: needed by /system/system_ext/lib64/libwfdclient.so in namespace classloader-namespace-shared
06-20 17:31:15.639 6466 6481 E JavaBinder: at java.lang.Runtime.loadLibrary0(Runtime.java:1077)
06-20 17:31:15.639 6466 6481 E JavaBinder: at java.lang.Runtime.loadLibrary0(Runtime.java:998)
06-20 17:31:15.639 6466 6481 E JavaBinder: at java.lang.System.loadLibrary(System.java:1656)
06-20 17:31:15.639 6466 6481 E JavaBinder: at com.qualcomm.wfd.WFDSession.<clinit>(WFDSession.java:56)
06-20 17:31:15.639 6466 6481 E JavaBinder: at com.qualcomm.wfd.WFDSession.createWFDSession(WFDSession.java:403)
06-20 17:31:15.639 6466 6481 E JavaBinder: at com.qualcomm.wfd.service.SessionManagerService.setDeviceType(SessionManagerService.java:175)
06-20 17:31:15.639 6466 6481 E JavaBinder: at com.qualcomm.wfd.service.ISessionManagerService$Stub.onTransact(ISessionManagerService.java:655)
06-20 17:31:15.639 6466 6481 E JavaBinder: at android.os.Binder.execTransactInternal(Binder.java:1184)
06-20 17:31:15.639 6466 6481 E JavaBinder: at android.os.Binder.execTransact(Binder.java:1143)
06-20 17:31:15.640 6466 6481 E AndroidRuntime: FATAL EXCEPTION: Binder:6466_3
06-20 17:31:15.640 6466 6481 E AndroidRuntime: Process: com.qualcomm.wfd.service:wfd_service, PID: 6466
06-20 17:31:15.640 6466 6481 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: library "libmmosal.so" not found: needed by /system/system_ext/lib64/libwfdclient.so in namespace classloader-namespace-shared
06-20 17:31:15.640 6466 6481 E AndroidRuntime: at java.lang.Runtime.loadLibrary0(Runtime.java:1077)
06-20 17:31:15.640 6466 6481 E AndroidRuntime: at java.lang.Runtime.loadLibrary0(Runtime.java:998)
06-20 17:31:15.640 6466 6481 E AndroidRuntime: at java.lang.System.loadLibrary(System.java:1656)
06-20 17:31:15.640 6466 6481 E AndroidRuntime: at com.qualcomm.wfd.WFDSession.<clinit>(WFDSession.java:56)
06-20 17:31:15.640 6466 6481 E AndroidRuntime: at com.qualcomm.wfd.WFDSession.createWFDSession(WFDSession.java:403)
06-20 17:31:15.640 6466 6481 E AndroidRuntime: at com.qualcomm.wfd.service.SessionManagerService.setDeviceType(SessionManagerService.java:175)
06-20 17:31:15.640 6466 6481 E AndroidRuntime: at com.qualcomm.wfd.service.ISessionManagerService$Stub.onTransact(ISessionManagerService.java:655)
06-20 17:31:15.640 6466 6481 E AndroidRuntime: at android.os.Binder.execTransactInternal(Binder.java:1184)
06-20 17:31:15.640 6466 6481 E AndroidRuntime: at android.os.Binder.execTransact(Binder.java:1143)
06-20 17:31:15.649 6485 6485 F linker : CANNOT LINK EXECUTABLE "/system_ext/bin/wfdservice": library "libmmosal.so" not found: needed by main executable

Categories

Resources