Create What's New mechanism using migration mechanism. This is
a first part of a fix for What's New not working if trying to
update from 2.9.0, 2.9.1 or 2.9.2.
Task relates to What’s new feature that needs to
know which version of MuditaOS was installed
before the update.
Normally What’s new uses a database to get the
previous version, but after the first run this
field will be empty.
To bypass this issue the PureRecovery needs to
save the previous version in recovery_status.json
that is generated after the update process.
* Added creation of /user/media/app/alarm
directory that will be used to store
custom alarm sounds.
* Implemented new database structure.
* Adapted Alarm, Bedtime, Pre-wake up and
Snooze to new database structure.
* Added removing custom alarm files during
factory reset.
* Added fallback alarm sound mechanism.
* Cleanups, unifications.
* Modified Lua update scripts to show simple
progress bar during update process in
Recovery.
* Fixed regression with failing factory
reset on Pure.
* Split Lua scripts per product.
* Removed doubled copyright header from 'up/down/devel.sql' when committing
databases.
* During installing, 'devel.sql' was created even if specific revisions
didn't contain one.
* Removed unnecessary product-specific .lua scripts.
* Removed old UDM-related update scripts that are no longer needed.
* Applied target update script
* Removed unneeded data folder from user partition
* Removed dummy personalization.json
Added checking if requested to restore backup
from pre-UDM version and setting db versions
to zero in such case, as version info file
(called backup.json in legacy backups) doesn't
contain info about versions.
