Mastodon

Al SuttonThe latest <a href="https://snapp.social/tags/Android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Android</a> <a href="https://snapp.social/tags/AOSP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AOSP</a> security patch marks the end of public Android #12 and <a href="https://snapp.social/tags/12L" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#12L</a> security patch support.There are a number of <a href="https://snapp.social/tags/Automotive" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Automotive</a> <a href="https://snapp.social/tags/Infotainment" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Infotainment</a> systems based on <a href="https://snapp.social/tags/Android12" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Android12</a> or <a href="https://snapp.social/tags/Android12L" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Android12L</a>, so it'll be interesting to see whether companies provide updates to <a href="https://snapp.social/tags/Android13" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Android13</a> (or, more likely, <a href="https://snapp.social/tags/Android14" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Android14</a>), or whether we see head-units left vulnerable to issues discovered in the coming months and years.<a href="https://source.android.com/docs/security/bulletin/2025-04-01" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://source.android.com/docs/security/bulletin/2025-04-01</a>

R.L. Dane :Debian: :OpenBSD: 🍵<a href="https://polymaths.social/tags/psa" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PSA</a>: the <a href="https://polymaths.social/tags/quik" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#QUIK</a> <a href="https://polymaths.social/tags/sms" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SMS</a> [<a href="https://f-droid.org/packages/dev.octoshrimpy.quik/" rel="nofollow noopener noreferrer" target="_blank">app</a>] has been updated, and it's way better than before.I used to have problems with it because the pictures it sent via <a href="https://polymaths.social/tags/mms" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MMS</a> were of far poorer quality than the other programs I tried (including the <a href="https://polymaths.social/tags/aosp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AOSP</a> 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.<a href="https://polymaths.social/tags/android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Android</a> <a href="https://polymaths.social/tags/foss" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FOSS</a>

Kuravelliä VillasukkaanElämme jännittäviä aikoja.<a href="https://mastodontti.fi/tags/eOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#eOS</a> <a href="https://mastodontti.fi/tags/AOSP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AOSP</a> <a href="https://mastodontti.fi/tags/DeGoogle" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DeGoogle</a> <a href="https://mastodontti.fi/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a>

R.L. Dane :Debian: :OpenBSD: 🍵<a href="https://mastodon.social/@ojocle_olonam" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ojocle_olonam</a>Not an (Android) developer, but I'm guessing that since those features aren't baked into <a href="https://polymaths.social/tags/aosp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AOSP</a>, they probably won't ever find their way into <a href="https://polymaths.social/tags/foss" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FOSS</a> <a href="https://polymaths.social/tags/android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Android</a> 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.

Silmathoron ⁂<a href="https://mastodon.social/@gael" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@gael</a> I would be curious to know what are the expected consequences for <a href="https://mastodon.social/@e_mydata" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@e_mydata</a> of the plan by Google to move to a source-available model for <a href="https://floss.social/tags/AOSP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AOSP</a>. How much of an impact do you anticipate and are there plans to explore alternatives closer to linux (e.g. like furiOS)?<a href="https://floss.social/tags/murena" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#murena</a> <a href="https://floss.social/tags/eOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#eOS</a>

R.L. Dane :Debian: :OpenBSD: 🍵<a href="https://polymaths.social/tags/til" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TIL</a> the stock <a href="https://polymaths.social/tags/aosp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AOSP</a> / <a href="https://polymaths.social/tags/lineageos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LineageOS</a> / <a href="https://polymaths.social/tags/calyxos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CalyxOS</a> keyboard actually has an <a href="https://polymaths.social/tags/emoji" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#emoji</a> mode!Its in settings (long press the comma!)

R.L. Dane :Debian: :OpenBSD: 🍵I kind of wish there was a simple emoji-only keyboard with search in f-droid so I could pair it with the stock <a href="https://polymaths.social/tags/aosp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AOSP</a> keyboard, which, while not as good as GBoard, is surprisingly good.

BluelupoDie Entwicklung von Android OS wird künftig vollständig hinter verschlossenen Türen stattfinden! - LinuxNews.de<a href="https://linuxnews.de/die-entwicklung-von-android-os-wird-kuenftig-vollstaendig-hinter-verschlossenen-tueren-stattfinden/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://linuxnews.de/die-entwicklung-von-android-os-wird-kuenftig-vollstaendig-hinter-verschlossenen-tueren-stattfinden/</a><a href="https://social.tchncs.de/tags/android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#android</a> <a href="https://social.tchncs.de/tags/aosp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aosp</a> <a href="https://social.tchncs.de/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://social.tchncs.de/tags/closedsource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#closedsource</a>

LinuxNews.deFuriPhone FLX1 <a href="https://linuxnews.de/furiphone-flx1/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://linuxnews.de/furiphone-flx1/</a> <a href="https://social.anoxinon.de/tags/AOSP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AOSP</a> <a href="https://social.anoxinon.de/tags/android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#android</a> <a href="https://social.anoxinon.de/tags/droidian" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#droidian</a>

Maxi 10x 💉Das klingt glaube ich erstmal schlimmer, als es ist. Ich bezweifle eh, dass bisher Außenstehende Einfluss auf die <a href="https://chaos.social/tags/AOSP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AOSP</a>-Entwicklung gehabt haben. Selbst Custom-ROM-Entwickler scheinen keinen Nachteil zu haben, falls Google wie bisher schon die Alphas und Betas im Code bereitstellt.Google entwickelt <a href="https://chaos.social/tags/Android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Android</a> künftig nur intern weiter und beendet damit die bisherige öffentliche Mitwirkung am Betriebssystem<a href="https://www.golem.de/news/google-android-entwicklung-vor-radikalen-umbruch-2503-194726.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.golem.de/news/google-android-entwicklung-vor-radikalen-umbruch-2503-194726.html</a>

Hans-Christoph Steiner<a href="https://eupolicy.social/@1br0wn" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@1br0wn</a> Yes indeed, it would be great to have a community controlled version of <a href="https://social.librem.one/tags/AOSP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AOSP</a>. 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 <a href="https://social.librem.one/tags/CalyxOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CalyxOS</a> 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.

Yauheni SlizhI think it is attempting to create a six-month gap between Google <a href="https://androiddev.social/tags/Pixels" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Pixels</a> and other phone vendors, especially <a href="https://androiddev.social/tags/Huawei" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Huawei</a>. <a href="https://www.androidauthority.com/google-android-development-aosp-3538503/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.androidauthority.com/google-android-development-aosp-3538503/</a> <a href="https://androiddev.social/tags/Android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Android</a> <a href="https://androiddev.social/tags/Google" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Google</a> <a href="https://androiddev.social/tags/Mobile" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mobile</a> <a href="https://androiddev.social/tags/AOSP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AOSP</a> <a href="https://androiddev.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a>

Hans-Christoph Steiner"Exclusive: Google will develop the Android OS fully in private..."Looking again at <a href="https://www.androidauthority.com/google-android-development-aosp-3538503/" rel="nofollow noopener noreferrer" target="_blank">https://www.androidauthority.com/google-android-development-aosp-3538503/</a> I really think that was a PR piece, e.g. <a href="https://social.librem.one/tags/Google" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Google</a>'s PR firm put together the story for <a href="https://social.librem.one/tags/Android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Android</a> 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<a href="https://social.librem.one/tags/AOSP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AOSP</a> <a href="https://social.librem.one/tags/PublicRelations" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PublicRelations</a> <a href="https://social.librem.one/tags/FreeSoftware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeSoftware</a> <a href="https://social.librem.one/tags/ClosedSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ClosedSource</a>

Privacy PromoGoogle's Move on Android AOSP DevelopmentGoogle 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.<a href="https://infosec.exchange/tags/Android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Android</a> <a href="https://infosec.exchange/tags/AOSP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AOSP</a> <a href="https://infosec.exchange/tags/Google" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Google</a> <a href="https://infosec.exchange/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> <a href="https://infosec.exchange/tags/DeveloperCommunity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DeveloperCommunity</a>

Mac<a href="https://mastodon.social/tags/Google" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Google</a>: <a href="https://mastodon.social/tags/Android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Android</a>-Entwicklung vor radikalen Umbruch <a href="https://www.golem.de/news/google-android-entwicklung-vor-radikalen-umbruch-2503-194726.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.golem.de/news/google-android-entwicklung-vor-radikalen-umbruch-2503-194726.html</a><a href="https://mastodon.social/tags/AOSP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AOSP</a>

DansLeRuSH ᴱᶰI may be wrong (no), but this increased opacity isn't a good sign : « <a href="https://floss.social/tags/Google" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Google</a> will develop the <a href="https://floss.social/tags/Android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Android</a> OS fully in private, and here's why » 🤔› <a href="https://www.androidauthority.com/google-android-development-aosp-3538503/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.androidauthority.com/google-android-development-aosp-3538503/</a><a href="https://floss.social/tags/AOSP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AOSP</a> <a href="https://floss.social/tags/Privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Privacy</a> <a href="https://floss.social/tags/Mobile" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mobile</a>

ComputerBaseAOSP: Google entwickelt Android fortan hinter verschlossenen Türen <a href="https://www.computerbase.de/news/betriebssysteme/aosp-google-entwickelt-android-fortan-hinter-verschlossenen-tueren.91942/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.computerbase.de/news/betriebssysteme/aosp-google-entwickelt-android-fortan-hinter-verschlossenen-tueren.91942/</a> <a href="https://mastodon.social/tags/google" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#google</a> <a href="https://mastodon.social/tags/android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#android</a> <a href="https://mastodon.social/tags/aosp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aosp</a>

infinite love ⴳwhoa, <a href="https://mastodon.social/tags/Android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Android</a> <a href="https://mastodon.social/tags/AOSP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AOSP</a> no longer to be developed in the open -- source code will be made available in large releases instead <a href="https://arstechnica.com/gadgets/2025/03/google-makes-android-development-private-will-continue-open-source-releases/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://arstechnica.com/gadgets/2025/03/google-makes-android-development-private-will-continue-open-source-releases/</a>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)

Ge0rG> While the shift to trunk-based development reduced this discrepancy, it persists and continues to pose challenges for Google. > This discrepancy forces Google to spend time and effort merging patches between the public AOSP branch and its internal branch.Poor little Google can't afford to keep AOSP public, and for sure they can't cope with the deluge of PRs from third-party contributors.Maybe somebody should set up a Ko-Fi for them?<a href="https://www.androidauthority.com/google-android-development-aosp-3538503/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.androidauthority.com/google-android-development-aosp-3538503/</a><a href="https://chaos.social/tags/Google" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Google</a> <a href="https://chaos.social/tags/Android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Android</a> <a href="https://chaos.social/tags/AOSP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AOSP</a>

Total Sonic MediaThis 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. <a href="https://mastodon.social/tags/linuxmobile" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linuxmobile</a> <a href="https://mastodon.social/tags/degoogled" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#degoogled</a> <a href="https://mastodon.social/tags/android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#android</a> <a href="https://mastodon.social/tags/aosp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aosp</a> <a href="https://mastodon.social/tags/ubuntutouch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ubuntutouch</a> <a href="https://mastodon.social/tags/sailfishos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sailfishos</a> <a href="https://mastodon.social/tags/mobian" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mobian</a><a href="https://arstechnica.com/gadgets/2025/03/google-makes-android-development-private-will-continue-open-source-releases/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://arstechnica.com/gadgets/2025/03/google-makes-android-development-private-will-continue-open-source-releases/</a>

Recent searches

Search options

Administered by:

Server stats:

#aosp