V5.0.0v - Crash starting Network DataSource

[jones139]

Some sort of security issue with network data source on Android 16 - I thought we had fixed this though:

***** UCE HANDLER Library
***** by Rohit Surwase

***** DEVICE INFO
Brand: samsung
Device: gta9wifi
Model: SM-X110
Manufacturer: samsung
Product: gta9wifieea
SDK: 36
Release: 16

***** APP INFO
Version: 5.0.0v
Installed On: 2024-03-22 09:54:22
Updated On: 2026-03-24 02:12:54
Current Date: 2026-03-24 20:54:04

***** ERROR LOG
java.lang.RuntimeException: Unable to create service uk.org.openseizuredetector.SdServer: java.lang.SecurityException: Starting FGS with type connectedDevice callerApp=ProcessRecord{3e00a60 18843:uk.org.openseizuredetector/u0a239} targetSDK=35 requires permissions: all of the permissions allOf=true [android.permission.FOREGROUND_SERVICE_CONNECTED_DEVICE] any of the permissions allOf=false [android.permission.BLUETOOTH_ADVERTISE, android.permission.BLUETOOTH_CONNECT, android.permission.BLUETOOTH_SCAN, android.permission.CHANGE_NETWORK_STATE, android.permission.CHANGE_WIFI_STATE, android.permission.CHANGE_WIFI_MULTICAST_STATE, android.permission.NFC, android.permission.TRANSMIT_IR, android.permission.UWB_RANGING, android.permission.RANGING, USB Device, USB Accessory]
at android.app.ActivityThread.handleCreateService(ActivityThread.java:5929)
at android.app.ActivityThread.-$$Nest$mhandleCreateService(Unknown Source:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2924)
at android.os.Handler.dispatchMessage(Handler.java:110)
at android.os.Looper.loopOnce(Looper.java:273)
at android.os.Looper.loop(Looper.java:363)
at android.app.ActivityThread.main(ActivityThread.java:10060)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:632)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:975)
Caused by: java.lang.SecurityException: Starting FGS with type connectedDevice callerApp=ProcessRecord{3e00a60 18843:uk.org.openseizuredetector/u0a239} targetSDK=35 requires permissions: all of the permissions allOf=true [android.permission.FOREGROUND_SERVICE_CONNECTED_DEVICE] any of the permissions allOf=false [android.permission.BLUETOOTH_ADVERTISE, android.permission.BLUETOOTH_CONNECT, android.permission.BLUETOOTH_SCAN, android.permission.CHANGE_NETWORK_STATE, android.permission.CHANGE_WIFI_STATE, android.permission.CHANGE_WIFI_MULTICAST_STATE, android.permission.NFC, android.permission.TRANSMIT_IR, android.permission.UWB_RANGING, android.permission.RANGING, USB Device, USB Accessory]
at android.os.Parcel.createExceptionOrNull(Parcel.java:3354)
at android.os.Parcel.createException(Parcel.java:3338)
at android.os.Parcel.readException(Parcel.java:3321)
at android.os.Parcel.readException(Parcel.java:3263)
at android.app.IActivityManager$Stub$Proxy.setServiceForeground(IActivityManager.java:7539)
at android.app.Service.startForeground(Service.java:863)
at uk.org.openseizuredetector.SdServer.onCreate(SdServer.java:315)
at android.app.ActivityThread.handleCreateService(ActivityThread.java:5916)
... 9 more
Caused by: android.os.RemoteException: Remote stack trace:
at com.android.server.am.ActiveServices.validateForegroundServiceType(qb/106577968 09baa10e40e373cdd2eac3bac31aec5a3f244b22f2e3a768ec56a7f547f4d38a:126)
at com.android.server.am.ActiveServices.setServiceForegroundInnerLocked(qb/106577968 09baa10e40e373cdd2eac3bac31aec5a3f244b22f2e3a768ec56a7f547f4d38a:120)
at com.android.server.am.ActiveServices.setServiceForegroundLocked(qb/106577968 09baa10e40e373cdd2eac3bac31aec5a3f244b22f2e3a768ec56a7f547f4d38a:51)
at com.android.server.am.ActivityManagerService.setServiceForeground(qb/106577968 09baa10e40e373cdd2eac3bac31aec5a3f244b22f2e3a768ec56a7f547f4d38a:13)
at android.app.IActivityManager$Stub.onTransact$setServiceForeground$(IActivityManager.java:12817)

***** END OF LOG *****

[jones139]

should be fixed in V5.0.0w (b41f7db)

[jones139]

....when Google approve it for publication - the last few updates have been approved in a couple of hours, but this is over 20 hours now for some reason - maybe it is flagged for needing a human to check it because it was a permissions change.....