shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

293
active users

#aosp

1 post1 participant0 posts today

#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.
Replied in thread

@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

@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.

"Exclusive: Google will develop the Android OS fully in private..."

Looking again at androidauthority.com/google-an I really think that was a PR piece, e.g. #Google's PR firm put together the story for #Android Authority. Its got all the markings, the "Exclusive" part, the uncritical eye "Google is simply consolidating its development efforts into a single branch", minimizing harm to custom ROMs, "custom ROMs will largely also see little change" etc

Android Authority · Exclusive: Google will develop the Android OS fully in private, and here's whyGoogle has confirmed it will move development of the Android OS to behind closed doors. Here's why it's doing it.

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.

whoa, #Android #AOSP no longer to be developed in the open -- source code will be made available in large releases instead arstechnica.com/gadgets/2025/0

so much for the android "open" source project; this puts it firmly in google's hands as google android (where previously their strategy was to make google-exclusive versions of the stock aosp apps like clock calendar calculator etc, they now just straight-up won't let you see what's going on in between ~yearly releases)

Android 15 on Pixel screen
Ars Technica · Google makes Android development private, will continue open source releasesBy Ryan Whitwam

This is some bs. If AOSP development is made less publicly accessible it does NOT " simplify things for developers" but rather it hinders it for de-googled privacy respecting ROMs and their device ports. The need for continued and ramped up efforts developing alternative mobile OS's, like Ubuntu Touch, Sailfish OS, Droidian, Mobian, Postmarket, etc. is even more apparent with this move by Google.
#linuxmobile #degoogled #android #aosp #ubuntutouch #sailfishos #mobian

arstechnica.com/gadgets/2025/0

Android 15 on Pixel screen
Ars Technica · Google makes Android development private, will continue open source releasesBy Ryan Whitwam

@drose

I don't remember it being as annoying on #iPhone, TBH. The phone call would always be at the very top of the notification shade (IIRC), and would be highlighted green or something.

At least on the #Android build I'm on, the phone call is either tiny, or just not listed in the notification shade at all. When you're on the lockscreen, you must get out of the notification shade to answer the phone.

When your phone is unlocked, you have to use the notification shade to get to the call (and it's not prominent!!), because opening the phone app JUST OPENS THE PHONE APP, and doesn't take you to your call at all.

It might just be an #AOSP thing or possibly just a #CalyxOS thing, I don't know.

I'll have to test it now, I'm curious.

Installing a new OS on a phone has always been a daunting task! I've done it a few times, but always dreaded it.

So I'm really happy that @e_mydata has created an installer that seems like it could actually be used by most people!

It looks like a simple step-by-step GUI process. Except there's a warning at the start stating "Before proceeding with the installation, verify if the latest Android firmware is available for your device." and I don't know what that means or how to check

I now have Android 15 on my Fairphone 4! Thank you, @calyxos!

People who don't flash a new OS on their Fairphone 4 (and I can't blame them, it's not fun) are still on Android 13! I don't really understand why @Fairphone spends resources developing their own tiny tweaked Android and never being able to keep it up to date, instead of collaborating with Calyx or some other OS developer who are able to get out the latest releases.

Replied in thread

@marcoarment
1/3

I've read many, though not all, of the interesting responses focused on #ethics #moral & #business and appreciate the thought put into each.

I'd like to consider another aspect though. From a practical and technical point of view, where does the typical person turn?

I used to be, and after retirement will be again, a contributor to #AOSP derived custom #ROMs and I currently use #GrapheneOS. My laptop runs a #Linux variant.

...more...

So, will the UK government's proposed digital wallet be open source software?

bbc.co.uk/news/articles/cgkjjk

I really hope so, as governments have been talking for years about "open source first" as part of its Technology Code of Practice (gov.uk/guidance/be-open-and-us). The wallet would cost taxpayers a significant sum of money to develop/procure and to maintain, so it should be open code to support this initiative.

Call me cynical though; I will not be surprised if this gets outsourced to a proprietary software vendor and is only available to Apple devices and unrooted Android devices. Ideally it would be available not just via Apple Store and Play Store, but to all AOSP-based devices via other distribution methods such as FDroid, as well as Linux devices via their own packaging tools.

BBC NewsDigital driving licences to be introduced this yearThe government says technology should "make people's lives easier" but any system won't be mandatory.