* 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
i just checked all translations from Signal,
they all use `+NUM` or very few `+ NUM`
(the latter might be a typo as transifex makes it easy to mess up with spaces).
also, the string would be hard to explain to translators
and would probably result in quite some questions.
if a language pops up that need sth. different,
we can still iterate.
the system camera has usually more features (flash, physical zoom, filter)
and is less buggy than the mostly unmaintained built-in one.
also, the system camera seems to be more supported
(isDeviceSupported() is not needed) and does not require to ask for permission.
there is still a switch in "advanced settings" to use the old built-in camera,
however, at some point we may remove the old code completely.
main reason is, that these annotations cover the code,
making it hard to follow what is going on.
maybe opionionated, however,
in general, .ts is not needed in small projects,
and an additional burden for devs.
- meet.jit.si is no longer usable without registration,
so does not work smoothly for ad-hoc calls
- basicwebrtc: protocol is no longer build-in in any app,
so that example does not make sense as well
this is an intermediate step,
we want to get rid of the example string completely
and instead show the URLs of the predefined settings.
closes https://github.com/deltachat/deltachat-android/issues/2642