Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
flipboard.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Welcome to Flipboard on Mastodon. A place for our community of curators and enthusiasts to inform and inspire each other. If you'd like to join please request an invitation via the sign-up page.

Administered by:

Server stats:

1.2K
active users

flipboard.social: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#aosp

2 posts2 participants0 posts today
Public
Al Sutton

The latest #Android #AOSP security patch marks the end of public Android #12 and #12L security patch support.

There are a number of #Automotive #Infotainment systems based on #Android12 or #Android12L, so it'll be interesting to see whether companies provide updates to #Android13 (or, more likely, #Android14), or whether we see head-units left vulnerable to issues discovered in the coming months and years.

source.android.com/docs/securi

Android Open Source ProjectAndroid Security Bulletin—April 2025  |  Android Open Source Project
Public
R.L. Dane :Debian: :OpenBSD: 🍵

#PSA: the #QUIK #SMS [app] has been updated, and it's way better than before.

I used to have problems with it because the pictures it sent via #MMS were of far poorer quality than the other programs I tried (including the #AOSP default Messaging app), but they seem to have fixed that.

They also have added a nice big button to trigger your phone's native dictation service (you can turn that off if you don't want it, or don't have one).

It has successfully replaced the proprietary SMS program I was using before, which makes me quite glad.

f-droid.orgQUIK SMS | F-Droid - Free and Open Source Android App RepositoryOpen source replacement to the stock SMS app on Android. A revival of QKSMS.
#Android#FOSS
Replied in thread
Public
R.L. Dane :Debian: :OpenBSD: 🍵

@ojocle_olonam

Not an (Android) developer, but I'm guessing that since those features aren't baked into #AOSP, they probably won't ever find their way into #FOSS #Android OSes (I hate calling them "ROMs," but I digress), because it's probably a lot easier to just write and manage an app that provides that feature than to work together to bake it into the OS in a way that's agreeable to all.

Replied in thread
Public
Hans-Christoph Steiner

@1br0wn Yes indeed, it would be great to have a community controlled version of #AOSP. The hard part is that Google still is the largest contributor to Android by a large margin. The ROM projects have started to work together, but not enough to get community control. The #CalyxOS team has put quite a bit of effort into trying to get this idea going. The key would be to get companies to switch to a community-controlled version, e.g. Samsung, Xiaomi, Huawei, Oppo, etc.

Replied in thread
Public
Keith Böhler

@cienmilojos @killminusnine @thenewoil

I see it as a bit of a "boiling frog" moment. You take baby steps to reduce the push back on unpopular moves. Making the development behind closed doors means it is harder for objections to happen (and be on time to reverse course)

I really like #opensource from a #philosophy point, so this kind of sours things for me.

Granted the article still says that #aosp will still be open source; I do imagine that they might try and fork later to make it fully closed.

Public
Privacy Promo

Google's Move on Android AOSP Development

Google has moved the development of Android to a private repository, aiming to streamline the development process and reduce complexity. Despite this, the Android Open Source Project (AOSP) will continue to be released at regular intervals, ensuring it remains open-source and accessible.

However, this change has raised concerns among developers:
- **Transparency**: Developers are worried about the reduced visibility into ongoing development.
- **Contribution**: Some fear it may limit their ability to contribute and influence the project.
- **Community Reaction**: While some support the move for potential efficiency gains, others are skeptical and call for more transparency and assurances from Google.

#Android#AOSP#Google
ExploreLive feeds
About