the screen-lock functionality was removed in
https://github.com/deltachat/deltachat-android/pull/1942 ;
the getters/setters were in use a little longer for a migration device messsage,
however, meanwhile this migration is removed as well.
as `isTouchExplorationEnabled()` is called more often now,
this avoids tens of calls per chat view.
/me also wanted to commit to the good-last-issue pr :)
use only one `audioFocusChangeListener`
as otherwise the "old" will immediately pause
when we restart playing.
moreover, this pr switches to the new `requestAudioFocus()` api
if we do not stay in the appearance page,
it makes more sense to quit the settings completely.
also, this removes potential other issues with the language change
as there is really only the chatlist that needs an update
this applies changed immediately,
so esp. right-to-left-changes are correct -
but also weird issues wrt wrong language in the title bar on some api should be fixed.
little downside is that after changing the language,
you're back to the "main settings page"
and do not stay in the "appearance page";
but you can regard this also as a feature, one tap less.
(reason is that the activity is resumed on language changes
and the underlying intent does not track fragments currently)
* set targetSdkVersion to 33
* api33 requires permission NEARBY_WIFI_DEVICES to access wifi
not sure, if this affects getSystemService(Context.WIFI_SERVICE),
however, we anyway do not ask for permissions here but just try/catch -
if things do not work, we just cannot get the wifi name
(we're not asking for permission as this would require LOCATION in the past -
and that would scare users that just installed Delta Chat
and select "Add Second Devive".
this is the exact reason why NEARBY_WIFI_DEVICES was introduced, btw.
so in case getting the Wifi name does not work on api33,
we can consider asking for a permission - would still be on startup, however)
* update storage permissions in manifest
according to https://developer.android.com/training/data-storage/shared/media#storage-permission
* also update compileSdkVersion
* api33: adapt audio permission request
* api33: adapt gallery permission request
* request correct permissions for the 'photo rail'
* request correct permissions for avatar selection
* api33: storage and audio permission not needed
* add comment wrt 'camera roll'
* add POST_NOTIFICATIONS to the manifest, this already allows to enable notifications in the system settings
* ask for POST_NOTIFICATIONS permission on startup
* explain how to re-enable notifications if initially disabled
* prefer a device message over an alert
* show in settings if notifications are system-disabled
B. Petersen