- All notifications about a post include action buttons
- Added #accessible #TalkBack descriptions and actions for notifications
- Read quotes with #TalkBack
A full-featured Android Mastodon client, developed under cooperative principles.
A full-featured Android Mastodon client, developed under cooperative principles.
- Show hidden hashtags at the end of the content
- Support searching for posts that quote others
- Trust new intermediate certificates from Sectigo
- Don’t crash if a poll has a missing vote count
- Many improvements to quotes, see the blog post for details
- Media playback fixes, see blog post for details
- Database fixes, see blog post for details
📺 https://peer.adalta.social/w/r4PGo9ndUngpNLpahkAJJ7 🔗 🇩🇪🇺🇸🇫🇷 🔗 ℹ️
La dernière vague de mises à jour alpha et stable consolide la plateforme Android pour l’ère de l’informatique ambiante.
📺 https://peer.adalta.social/w/61gKuiCi9rZSmokewxYgLu 🔗 🇩🇪🇺🇸🇫🇷 🔗 ℹ️
The February 2025 release signals a multi-platform consolidation, moving beyond mobile to define Google’s unified developer ecosystem.
Mobile Developer, focused on Android, taking a liking to 🦀 too. Working at element.io.
Mobile Developer, focused on Android, taking a liking to 🦀 too. Working at element.io.
#androiddev is there any place where I could ask some Google dev about WorkManager’s behaviour on Android 15+? We’re having some issues related to background network access (https://developer.android.com/about/versions/15/behavior-changes-all#background-network-access) that are still happening when using WorkManager for fetching the data associated with push notifications (the context is an encrypted IM that only sends minimal data in the pushes).
I understand what we should do is probably schedule the tasks using some NetworkType or NetworkRequest constraint, but using NetworkType.CONNECTED won’t work for customers that are behind a VPN or in an air-gapped environment since it performs a request to gen_204 google URL that may not be available, and I’m not sure if NetworkType.UNMETERED or NetworkRequest with NET_CAPABILITY_INTERNET would be enough to have WorkManager temporarily grant our app internet connectivity and prevent those UnknownHostExceptions we’re seeing.
This seems to be poorly documented, so we’re not sure what the right behavior is, to be honest.
You've seen all posts