Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 2ab08551 authored by Achim Thesmann's avatar Achim Thesmann
Browse files

Log not impacted cases

While cases that are not impacted by BAL hardening are not critical for
us right now, it is important to log these to see future impact.

This does not change the behavior, just logging, as `mBalAllowedByPiCreatorWithHardening` implies `mBalAllowedByPiCreator` and both result in `allowBasedOnCaller`.

Test: atest BackgroundActivityStartController
Bug: 296478951
Change-Id: Ic26ae6967ccbbc781091ac4a64e9b13a5bff5da9
parent ff26a560
Loading
Loading
Loading
Loading
+0 −8
Original line number Diff line number Diff line
@@ -719,14 +719,6 @@ public class BackgroundActivityStartController {
                && !state.realCallerExplicitOptOut();
        if (callerCanAllow) {
            // Allowed before V by creator
            if (state.mBalAllowedByPiCreatorWithHardening.allowsBackgroundActivityStarts()) {
                // Will be allowed even with BAL hardening.
                if (DEBUG_ACTIVITY_STARTS) {
                    Slog.d(TAG, "Activity start allowed by caller. "
                            + state.dump());
                }
                return allowBasedOnCaller(state);
            }
            if (state.mBalAllowedByPiCreator.allowsBackgroundActivityStarts()) {
                Slog.wtf(TAG, "With Android 15 BAL hardening this activity start may be blocked"
                                + " if the PI creator upgrades target_sdk to 35+! "