Files
brnQuanFW/app
Juan Antonio 6f1cabc807 Simplify gSchedulePowerSave logic
There was quite convoluted logic there, and what I believe, was a bug.

Rationale:

Both,
- gBatterySaveCountdown_10ms = battery_save_count_10ms;, and
- gSchedulePowerSave = false
are always executed inside FUNCTION_Select().

So the code is equivalent to:

if (any of those OR'd) {
	gBatterySaveCountdown_10ms = battery_save_count_10ms;
	gSchedulePowerSave = false; (but only if we have NOAA disabled)
} else {
	[other stuff from FUNCTION_Select()]
	gBatterySaveCountdown_10ms = battery_save_count_10ms;
	gSchedulePowerSave = false; (regarless of having NOAA or not)
}

So:
- OR is true, have NOAA-> don't clear gSchedulePowerSave
	-> implies we will enter here, again, until the OR is false, but only if we have NOAA.
- OR is False -> clear gSchedulePowerSave.

Moreover, checking with DualTachyon code at
6f8afac886/app/app.c (L747)
gSchedulePowerSave is always set to false if it was true.
2023-12-24 13:34:05 +01:00
..
2023-12-08 01:43:12 +01:00
2023-12-24 13:34:05 +01:00
2023-12-05 00:22:30 +01:00
2023-12-19 18:25:45 +01:00
2023-12-19 18:25:45 +01:00
2023-11-28 20:13:02 +01:00
2023-12-24 13:34:05 +01:00
2023-12-24 13:34:05 +01:00
2023-12-07 00:46:59 +01:00
2023-12-07 00:46:59 +01:00
2023-12-08 23:18:19 +01:00
2023-09-09 08:03:56 +01:00
2023-12-19 18:25:45 +01:00
2023-09-09 08:03:56 +01:00
2023-12-15 18:08:40 +01:00
2023-11-09 10:33:28 +01:00
2023-12-19 18:25:45 +01:00
2023-12-13 16:07:07 +01:00
2023-09-09 08:03:56 +01:00