Konstantin

No installed it right from the file explorer using the default packet installer.

I uninstalled the secure folder and now the READ_LOGS and SYSTEM_ALERT_WINDOW permissions have no exception. Still no background sync from Android to Windows but it works the other way around.

``` android.app.action.SCHEDULE_EXACT_ALARM_PERMISSION_STATE_CHANGED: dcd654 com.clipcascade/app.notifee.core.AlarmPermissionBroadcastReceiver filter 4d09fd Action: "android.app.action.SCHEDULE_EXACT_ALARM_PERMISSION_STATE_CHANGED" Permissions: Permission [com.clipcascade.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION] (25facad): perm=PermissionInfo{e700eb2 com.clipcascade.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION} installPermissionsFixed=true declared permissions: com.clipcascade.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION: prot=signature requested permissions: android.permission.INTERNET android.permission.POST_NOTIFICATIONS android.permission.FOREGROUND_SERVICE android.permission.FOREGROUND_SERVICE_REMOTE_MESSAGING android.permission.REQUEST_IGNORE_BATTERY_OPTIMIZATIONS android.permission.SYSTEM_ALERT_WINDOW android.permission.READ_LOGS android.permission.WAKE_LOCK android.permission.ACCESS_NETWORK_STATE...

I see this in logcat: `I ActivityManager: Background started FGS: Allowed [callingPackage: com.clipcascade; callingUid: 10700; uidState: TOP ; uidBFSL: [BFSL]; intent: Intent { act=app.notifee.core.ForegroundService.START cmp=com.clipcascade/app.notifee.core.ForegroundService (has extras) }; code:PROC_STATE_TOP; tempAllowListReason:;...

Yes the app can draw over other apps but didn't find it in the log

Ok thanks could also setup a remote session if needed.

I somehow can't login to RTL. Did you do the steps in this order? Or anything that I didn't? I am going to test it on my Tablet. https://github.com/Sathvik-Rao/ClipCascade/issues/6#issuecomment-2395407325

I am so sorry. My Tablet worked first try. I rebooted my phone again for a security patch and now it is working.

I am currently on 12.0.2 and everything is working will test version 11

The problem exists up to including v 11.4.6 and is fixed in 11.5.0. The source problem is that the custom Field Editors get undefined as props