[Samsung Galaxy S 5 Unified Development] ttesty:
Seems like some API breakage below (related to argument handling) - note a sequence number is getting passed at the beginning of a bandwidth control command and the sub-command (addrestrictappsondata) is bad:

command '54 bandwidth addrestrictappsondata rmnet0 10045' failed with '500 54 Unknown bandwidth cmd'

So I reverted by re-flashing my latest stock RR 7.0.2 release and removed my keystore data in order to recover from this error in your ROM.

12-15 22:48:29.493 5896 5896 D AndroidRuntime: Shutting down VM

12-15 22:48:29.494 5896 5896 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main

12-15 22:48:29.494 5896 5896 E AndroidRuntime: java.lang.RuntimeException: Error receiving broadcast Intent { act=android.net.conn.CONNECTIVITY_CHANGE flg=0x4200010 (has extras) } in com.android.server.NetworkManagementService$1@9bc9 ab2

12-15 22:48:29.494 5896 5896 E AndroidRuntime: at android.app.LoadedApk$ReceiverDispatcher$Args.lamb da$getRunnable$0(LoadedApk.java:1401)

12-15 22:48:29.494 5896 5896 E AndroidRuntime: at android.app.-$$Lambda$LoadedApk$ReceiverDispatcher$Args$_BumDX2 UKsnxLVrE6UJsJZkotuA.run(Unknown Source:2)

12-15 22:48:29.494 5896 5896 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:873 )

12-15 22:48:29.494 5896 5896 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99 )

12-15 22:48:29.494 5896 5896 E AndroidRuntime: at android.os.Looper.loop(Looper.java:193)

12-15 22:48:29.494 5896 5896 E AndroidRuntime: at com.android.server.SystemServer.run(SystemServer.j ava:487)

12-15 22:48:29.494 5896 5896 E AndroidRuntime: at com.android.server.SystemServer.main(SystemServer. java:309)

12-15 22:48:29.494 5896 5896 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)

12-15 22:48:29.494 5896 5896 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsC aller.run(RuntimeInit.java:495)

12-15 22:48:29.494 5896 5896 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit .java:838)

12-15 22:48:29.494 5896 5896 E AndroidRuntime: Caused by: java.lang.IllegalArgumentException: command '54 bandwidth addrestrictappsondata rmnet0 10045' failed with '500 54 Unknown bandwidth cmd'

12-15 22:48:29.494 5896 5896 E AndroidRuntime: at com.android.server.NetworkManagementService.restri ctAppOnData(NetworkManagementService.java:1861)

12-15 22:48:29.494 5896 5896 E AndroidRuntime: at com.android.server.NetworkManagementService.proces sPendingDataRestrictRequests(NetworkManagementServ ice.java:1929)

12-15 22:48:29.494 5896 5896 E AndroidRuntime: at com.android.server.NetworkManagementService.access $200(NetworkManagementService.java:142)

12-15 22:48:29.494 5896 5896 E AndroidRuntime: at com.android.server.NetworkManagementService$1.onRe ceive(NetworkManagementService.java:437)

12-15 22:48:29.494 5896 5896 E AndroidRuntime: at android.app.LoadedApk$ReceiverDispatcher$Args.lamb da$getRunnable$0(LoadedApk.java:1391)

12-15 22:48:29.494 5896 5896 E AndroidRuntime: ... 9 more

12-15 22:48:29.494 5896 5896 E AndroidRuntime: Caused by: com.android.server.NativeDaemonConnector$NativeDae monArgumentException: command '54 bandwidth addrestrictappsondata rmnet0 10045' failed with '500 54 Unknown bandwidth cmd'

12-15 22:48:29.494 5896 5896 E AndroidRuntime: at com.android.server.NativeDaemonConnector.executeFo rList(NativeDaemonConnector.java:512)

12-15 22:48:29.494 5896 5896 E AndroidRuntime: at com.android.server.NativeDaemonConnector.execute(N ativeDaemonConnector.java:411)

12-15 22:48:29.494 5896 5896 E AndroidRuntime: at com.android.server.NativeDaemonConnector.execute(N ativeDaemonConnector.java:406)

12-15 22:48:29.494 5896 5896 E AndroidRuntime: at com.android.server.NetworkManagementService.restri ctAppOnData(NetworkManagementService.java:1859)

12-15 22:48:29.494 5896 5896 E AndroidRuntime: ... 13 more

- Hack: you could compile the kernel without bandwidth control (i.e. without /proc/net/xt_qtaguid/ctrl ).

- Hack: chmod 0 /proc/net/xt_qtaguid

- You could fix the naming of the bandwidth subcommand and rebuild the build framework

Another issue you'll then find:

12-17 00:17:45.891 11163 11178 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: android.ui

12-17 00:17:45.891 11163 11178 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean android.app.usage.UsageStatsManagerInternal.isAppI dle(java.lang.String, int, int)' on a null object reference

12-17 00:17:45.891 11163 11178 E AndroidRuntime: at com.android.server.net.NetworkPolicyManagerService .isUidIdle(NetworkPolicyManagerService.java:3862)

12-17 00:17:45.891 11163 11178 E AndroidRuntime: at com.android.server.net.NetworkPolicyManagerService .updateRulesForPowerRestrictionsULInner(NetworkPol icyManagerService.java:4155)

12-17 00:17:45.891 11163 11178 E AndroidRuntime: at com.android.server.net.NetworkPolicyManagerService .updateRulesForPowerRestrictionsUL(NetworkPolicyMa nagerService.java:4143)

12-17 00:17:45.891 11163 11178 E AndroidRuntime: at com.android.server.net.NetworkPolicyManagerService .updateRulesForPowerRestrictionsUL(NetworkPolicyMa nagerService.java:4118)

12-17 00:17:45.891 11163 11178 E AndroidRuntime: at com.android.server.net.NetworkPolicyManagerService .updateRulesForTempWhitelistChangeUL(NetworkPolicy ManagerService.java:3836)

12-17 00:17:45.891 11163 11178 E AndroidRuntime: at com.android.server.net.NetworkPolicyManagerService .access$3800(NetworkPolicyManagerService.java:294)

12-17 00:17:45.891 11163 11178 E AndroidRuntime: at com.android.server.net.NetworkPolicyManagerService $NetworkPolicyManagerInternalImpl.onTempPowerSaveW hitelistChange(NetworkPolicyManagerService.java:49 01)

12-17 00:17:45.891 11163 11178 E AndroidRuntime: at com.android.server.DeviceIdleController.addPowerSa veTempWhitelistAppDirectInternal(DeviceIdleControl ler.java:1982)

12-17 00:17:45.891 11163 11178 E AndroidRuntime: at com.android.server.DeviceIdleController$LocalServi ce.addPowerSaveTempWhitelistAppDirect(DeviceIdleCo ntroller.java:1417)

12-17 00:17:45.891 11163 11178 E AndroidRuntime: at com.android.server.am.ActivityManagerService.pushT empWhitelist(ActivityManagerService.java:26082)

12-17 00:17:45.891 11163 11178 E AndroidRuntime: at com.android.server.am.ActivityManagerService$UiHan dler.handleMessage(ActivityManagerService.java:220 2)

12-17 00:17:45.891 11163 11178 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:10 6)

12-17 00:17:45.891 11163 11178 E AndroidRuntime: at android.os.Looper.loop(Looper.java:193)

12-17 00:17:45.891 11163 11178 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:65 )

12-17 00:17:45.891 11163 11178 E AndroidRuntime: at com.android.server.ServiceThread.run(ServiceThread .java:44)

12-17 00:17:45.891 11163 11178 E AndroidRuntime: at com.android.server.UiThread.run(UiThread.java:43)

These issues began at the last official RR release. The one before it was legit.