Error "unable to change the state"

[utack]

I am getting a Error "unable to change the state", on Cyanogenmod 13.
The log however does indicate the command succeeds:
https://paste.ubuntu.com/15610524/
Maybe you can have a look at it

[uvok]

Here's an example logcat, same problem here

05-31 07:08:08.268 D/Autostarts(11366): Added org.liberty.android.fantastischmemo/org.liberty.android.fantastischmemo.SetAlarmReceiver to service queue, now size: 1
05-31 07:08:08.268 D/Autostarts(11366): Processing org.liberty.android.fantastischmemo/org.liberty.android.fantastischmemo.SetAlarmReceiver, remaining items in queue: 0
05-31 07:08:08.273 I/Autostarts(11366): Asking package manger to change component state to disabled
05-31 07:08:08.273 I/Autostarts(11366): Changing state by employing root access
05-31 07:08:08.273 I/Autostarts(11366): Switching ADB on for the root call
05-31 07:08:08.274 I/Autostarts(11366): Using setprop call to touch ADB setting
05-31 07:08:08.274 D/RootTools v3.6(11366): Starting shell: su
05-31 07:08:08.317 D/su      (12737): su invoked.
05-31 07:08:08.317 D/su      (12737): starting daemon client 10076 10076
05-31 07:08:08.320 D/su      (12739): remote pid: 12737
05-31 07:08:08.320 D/su      (12739): remote pts_slave: 
05-31 07:08:08.321 D/su      (12739): waiting for child exit
05-31 07:08:08.322 D/su      (12741): su invoked.
05-31 07:08:08.322 E/su      (12741): SU from: u0_a76
05-31 07:08:08.323 D/su      (12741): Checking whether app [uid:10076, pkgName: com.elsdoerfer.android.autostarts] is allowed to be root
05-31 07:08:08.327 I/SuControllerImpl( 3098): Got change
05-31 07:08:08.327 D/su      (12741): Privilege elevation allowed by appops
05-31 07:08:08.327 D/su      (12741): Allowing via appops.
05-31 07:08:08.328 D/su      (12741): 10076 /system/bin/app_process64_xposed executing 0 /system/bin/sh using binary /system/bin/sh : sh
05-31 07:08:08.329 D/su      (12741): Waiting for pid 12742.
05-31 07:08:09.482 D/su      (12751): su invoked.
05-31 07:08:09.621 D/su      (12756): su invoked.
05-31 07:08:09.760 D/su      (12761): su invoked.
05-31 07:08:09.899 D/su      (12766): su invoked.
05-31 07:08:10.002 I/Autostarts(11366): Switching ADB off again
05-31 07:08:10.003 I/Autostarts(11366): Using setprop call to touch ADB setting
05-31 07:08:15.109 D/Autostarts(11366): Processing org.liberty.android.fantastischmemo/org.liberty.android.fantastischmemo.SetAlarmReceiver done
05-31 07:08:15.109 D/Autostarts(11366): ToggleService mQueue empty, shutting down
05-31 07:08:15.110 D/Autostarts(11366): Closing all root shells
05-31 07:08:15.113 D/su      (12741): Finishing su operation for app [uid:10076, pkgName: com.elsdoerfer.android.autostarts]
05-31 07:08:15.116 I/SuControllerImpl( 3098): Got change
05-31 07:08:15.118 D/su      (12739): sending code
05-31 07:08:15.118 D/su      (12739): child exited
05-31 07:08:15.119 D/su      (12737): client exited 0
05-31 07:08:15.817 I/NotificationService( 1399): cancelToast pkg=com.elsdoerfer.android.autostarts callback=android.app.ITransientNotification$Stub$Proxy@8f03b9
05-31 07:08:15.817 W/NotificationService( 1399): Toast already cancelled. pkg=com.elsdoerfer.android.autostarts callback=android.app.ITransientNotification$Stub$Proxy@8f03b9

[anonimou0]

@utack and @uvok
i'm having the same problem as well (asus Z00L, here).. i'm thinking that it is because this is a 64-bit processor and OS (CM13, here)
can you confirm that the problems you mentioned above are caused in 64-bit devices?

[anonimou0]

yep.. as i thought, it is because it was running on 64-bit architecture.
made the changed and commited now. let's see if miracle2k will merge.

here is a working version:

autostarts_x86_64.zip