Start your journey into the Fediverse by subscribing to our starter communities. We're actively working with subreddit communities and moderators on their transition over.
Our Mission
Lemdro.id strives to be a fully open source instance with incredible transparency. Visit our GitHub for the nuts and bolts that go into making this instance soar and our Matrix Space to chat with our team and access the read-only backroom admin chat.
Are you interested in exploring options to migrate your tech subreddit to the Fediverse in a way that supports decentralization or are you an experienced moderator who is interested in joining one of our mod teams? Get in touch!
A Fediverse home for developers
Are you developing a Lemmy app and looking for a home community for your project? Get in touch!
To drive faster innovation in apps and devices, Android will have a major release in Q2 to include behavior changes, and a minor release in Q4.
Two Android releases in 2025
> Next year, weāll have a major release in Q2 and a minor release in Q4, both of which will include new developer APIs. The Q2 major release will be the only release in 2025 to include behavior changes that can affect apps. Weāre planning the major release for Q2 rather than Q3 to better align with the schedule of device launches across our ecosystem, so more devices can get the major release of Android sooner.
> The Q4 minor release will pick up feature updates, optimizations, and bug fixes since the major release. It will also include new developer APIs, but will not include any app-impacting behavior changes.
> Outside of the major and minor Android releases, our Q1 and Q3 releases will provide incremental updates to help ensure continuous quality. Weāre actively working with our device partners to bring the Q2 release to as many devices as possible.
What this means for your apps
> With the major release coming in Q2, youāll need to do your annual compatibility testing a few months earlier than in previous years to make sure your apps are ready. Major releases are just like the SDK releases we have today, and can include behavior changes along with new developer APIs ā and to help you get started, weāll soon begin the developer preview and beta program for the Q2 major release.
> The minor release in Q4 will include new APIs, but, like the incremental quarterly releases we have today, will have no planned behavior changes, minimizing the need for compatibility testing. To differentiate major releases (which may contain planned behavior changes) from minor releases, minor releases will not increment the API level. Instead, they'll increment a new minor API level value, which will be accessed through a constant that captures both major and minor API levels. A new manifest attribute will allow you to specify a minor API level as the minimum required SDK release for your app. Weāll have an initial version of support for minor API levels in the upcoming Q2 developer preview, so please try building against the SDK and let us know how this works for you.
> When planning your targeting for 2026, thereās no change to the target API level requirements and the associated dates for apps in Google Play; our plans are for one annual requirement each year, and that will be tied to the major API level only.
Two mobile operating systems currently comprise nearly 100% of the global smartphone market. Building one is hard, and for most phone makers, there are
I've recently gotten a new (used) Pixel 7aāupgraded from an iPhone X.
Problem:
I must have short thumbs or something because on my new Android phone, I'm constantly having to swipe multiple times for a gesture to "take." For example, swiping up to unlock or get to home, swiping left/right to cycle through image carousels in the app storeāin all use cases, the screen starts sliding over, but when I lift my thumb off the screen, about 50% of the time, the screen slides back to its original position instead of sliding the rest of the way to the next screen.
I understand the need for a threshold to prevent accidental swipes; however, the native swipe lengths are just a wee bit too long for me, and the constant need to swipe multiple times to do what I want is significantly affecting my overall experience. I never had this problem on any of my iPhones.
What I've tried so far:
I've poked around in the Settings and done a few internet searches. Came across this Google forums thread from 2018, to which the only reply was essentially tough rocks.
In another post, I received the advice that I donāt need long gestures if I make them faster, and I have noticed different results depending on the speed of my flicks, but still find myself having to make multiple flicks to get it to do what I want. Somebody else suggested reducing the āWindow Animationā or the āTransition Animationā speed (in developer settings), but alas, there are no such settings in GrapheneOS (I tried the search bar).
I've installed an alternate app launcher (PieLauncher), but this is only a partial band-aid solution. I still have the issue w/ left/right swipes on image carousels.
I'll keep exploring apps that allow me to customize gestures, but has anyone else had this problem, and how did you solve it? Or if anyone has any suggestions for apps available in the F-Droid store that might help with this problem, I'd appreciate it. Thank you!