- rename ServiceDB to ServiceDBCommon,
- create separate ServiceDB for Pure and Bell,
- move Pure-specific functionality
from `ServiceDBCommon` to Pure `ServiceDB`
The bug was introduced by EGD-6794. The bug is caused by wrong mode
selection in `ScreenLightTimer`'s definition. The current design
defines auto-turn-off only for automatic mode (EGD-6655).
This commit provides the flowing fixes in display light functionality:
- Settings-path bug causing lack of display light settings on "fresh"
image. Solved with proper paths definition
- Invalid settings after phone restart. Solved with proper handling
of enums and booleans on the Event manager side.
- No turning off light just after turning on light functionality with
manual brightness setting in ApplicationSettings bug (required
another key press to start timer that turns off the light after 5s).
Solved by starting timer explicitly on Action::turnOn
- No turning off light just after turning on the phone bug (required
--as above --). Solved by starting timer explicitly on `Settings
ValueChange` callback with Action::turnOn.
- No autoMode until user entered `AppSettings::DisplayLight` Window.
Bug caused by curve parameters being provided by the window rather
than on the functionality back-end initialization.
Commit also provides some code cleanup
added weakptr link to settings and checks
it wont crash on deinitialized setings now
Pseuto UT are passing
Added:
- deregistration on Settings destrution
- weak referencing of Service to not crash Settings on missuse
- Proxy as initialization parameter to Settings
Unused code removed
Enabled tests to be written for Settings
Removed dependency from freertos in test global file
EntryPath tests updated and compilation slimed
Added enabling screen light if there was any key pressed
and screen light controler is in the automatic mode.
Added screen light disabling after 5 seconds of timeout
without any key being pressed.
