-
merrycachemiss authored
Target API 33 on both mobile and Wear. Reworked all separate processes and intentservices into the main service, as only the main service will start on modern Android (via bootup or mainactivity) when targeting 32+. Noticed that some (likely 3rd party OEM) devices that are granted Device Admin are not actually allowing this app to launch stuff in the background, received crash reports of background launch of foreground service prevention. On Pixel and emulator, all battery exemptions are applied when device admin is granted. So, mitigating this by following the normal rules, even though it's not actually needed. It was nice having separate services and processes that only lived when they were necessary, but now the main service constantly wakes up even when a particular event is not relevant at the time. Also, separation of app crashes that didn't affect other parts of the app. Worked in Wear OS API node detection, for the rare-but-common-enough instance that the Wear device is disconnected, with the strikethrough cloud icon, but Bluetooth APIs erroneously still think the device is connected (no ACL disconnected event is received). So it just acts as a secondary disconnect detection method. Foolishly, it seems that the app must also be installed on the watch for this node part to work. Improved WIFI disconnection code in hopes to handle mesh WIFI.
e1adaaccmerrycachemiss authoredTarget API 33 on both mobile and Wear. Reworked all separate processes and intentservices into the main service, as only the main service will start on modern Android (via bootup or mainactivity) when targeting 32+. Noticed that some (likely 3rd party OEM) devices that are granted Device Admin are not actually allowing this app to launch stuff in the background, received crash reports of background launch of foreground service prevention. On Pixel and emulator, all battery exemptions are applied when device admin is granted. So, mitigating this by following the normal rules, even though it's not actually needed. It was nice having separate services and processes that only lived when they were necessary, but now the main service constantly wakes up even when a particular event is not relevant at the time. Also, separation of app crashes that didn't affect other parts of the app. Worked in Wear OS API node detection, for the rare-but-common-enough instance that the Wear device is disconnected, with the strikethrough cloud icon, but Bluetooth APIs erroneously still think the device is connected (no ACL disconnected event is received). So it just acts as a secondary disconnect detection method. Foolishly, it seems that the app must also be installed on the watch for this node part to work. Improved WIFI disconnection code in hopes to handle mesh WIFI.
Loading