* update changelog for 1.36, core part
* update changelog for 1.36, android part
* bump version to 1.36
* add device message for 1.36
* qualify 'Add Second Device' as experimental also in device message
* apply recent suggestions to CHANGELOG
we already had a confirmation dialog for probably most security-aware users
always when the device is protected by a screen lock.
this commits adds a more on-point text -
and shows the same text in a simple alert in case a device has no screen lock.
while both devices show a progess bar,
the exact percentage is shown on receiver side only.
beside the receiver progress being more accurate,
main reason is not not confuse users by the devices showing
slightly different percentages.
more detailed text about internals,
that maybe even flashes up only for a fraction of a second
is not helpful after first user tests,
and may even scare ppl.
we're also checking for null at some other critical code positions,
so this seems reasonable also here.
this might fix a recently reported crash,
maybe caused by a race condition.
ppl try already now to set up a second device from the welcome screen.
however, end up in logging into their email account again,
creating issues with keys and more.
a dedicated "Add as Second Devies" button targets this UX issue
by offering a clear path for setting up a second device.
moreover, the string "Scan Invitation Code" is used again (as on all releases),
this string is used quite a bit in different handouts,
changing that would worsen UX as well.
the "Restore from Backup is moved down,
if you really use this path, finding the button is the smallest issue.
the different layout of the button makes clear,
that this is not the preferred way to set up a new account
(but sure, to restore a backup :)
this fixes leaving Delta Chat during backup transfer
by removing other activities that would abort BackupTransfer
by getting called with onNewIntent() otherwise.
moreover, the permantent notification is removed more reliably
and possible crashes in the permantent notification closing (races ...)
are catched.
see code + comments for details.
B. Petersen