diff --git a/_vendors-content/samsung/explanation.md b/_vendors-content/samsung/explanation.md index 3a371e59..3e5cfbf4 100644 --- a/_vendors-content/samsung/explanation.md +++ b/_vendors-content/samsung/explanation.md @@ -4,10 +4,15 @@ manufacturer: samsung ---
-Despite Android team promise to enforce OEMs to be transparent about non-standard app killing, in Android 11 Samsung has introduced a new severe (default ON) restriction. Apps can no longer hold wake lock in foreground services. This breaks many use-cases, for instance health apps are now unable to gather sensoric data for their users. +Despite the Android team's promise to enforce OEMs to be transparent about non-standard app killing, in Android 11 Samsung has introduced a new severe (default ON) restriction. Apps can no longer hold wake lock in foreground services. This breaks many use-cases, for instance, health apps are now unable to gather sensoric data for their users. See details here and read below for workaround.

+UPDATE 07/2024: Samsung officially promised to drop the non-standard optimizations:
+"To strengthen the Android platform, our collaboration with Google has resulted in a unified policy that we expect will create a more consistent and reliable user experience for Galaxy users. Since One UI 6.0, foreground services of apps targeting Android 14 will be guaranteed to work as intended so long as they are developed according to Android's new foreground service API policy.”
+If anyone has information about this or experience with Android 14 on Samsung phones, please, let us know any feedback on this. +
+ UPDATE 04/2021: Is Samsung now killing even foreground services? Could this be real, or is it a chimera?
Even disabling the system battery restrictions does not save the app from being killed. Let's find out, if it is a bug or a feature... Here you can read more details