I thought about this on the way home, I reckon this bug occurs because maybe that is more than one layer of code that determines the setting,
on the first layer the toggle turns it on or off, but the second layer goes thru an if else statement, via a reboot script or something, the toggle state is on, u toggle it off it didn’t write anything , you toggle it back on again it didn’t write anything because the original state is already on , so it doesn’t write to the second layer of configs, but when you toggle it off, and reboot the phone, it writes those data thru as the state actually changed from boot perspective, so after boot, it then detects that change this time and writes it down the second or more layers to the off state thus overwriting the restored state it was in which is off and then when u toggle it back on this time it continue to detect the change and that fixed the problem. But I could be soo wrong.
Topic:
App & System Services
SubTopic:
Core OS
Tags: