So there's one receiver for android.intent.action.BOOT_COMPLETED: "com.keramidas.TitaniumBackup/.schedules.BootReceiver"
Autostarts displays the Titanium Backup entry in "After Startup" as "com.keramidas.TitaniumBackup" and when showing its details it displays receiver name as "(no-name)" and is also unable to work with it properly because it tries to perform any operations on "'com.keramidas.TitaniumBackup/(no-name)'" which of course doesn't exist.
When I disable this receiver manually (in shell), then the state in Autostarts still doesn't show it's disabled (even after reload, or relaunch of Autostarts)
Similar issue affects other actions where Titanium Backup appears such as "Application Installed" (android.intent.action.PACKAGE_ADDED) etc.
Hello, Titanium Backup 6.2.0 contains the following receivers:
pm dump 'com.keramidas.TitaniumBackup'
So there's one receiver for android.intent.action.BOOT_COMPLETED: "com.keramidas.TitaniumBackup/.schedules.BootReceiver"
Autostarts displays the Titanium Backup entry in "After Startup" as "com.keramidas.TitaniumBackup" and when showing its details it displays receiver name as "(no-name)" and is also unable to work with it properly because it tries to perform any operations on "'com.keramidas.TitaniumBackup/(no-name)'" which of course doesn't exist.
When I disable this receiver manually (in shell), then the state in Autostarts still doesn't show it's disabled (even after reload, or relaunch of Autostarts)
Similar issue affects other actions where Titanium Backup appears such as "Application Installed" (android.intent.action.PACKAGE_ADDED) etc.