[HN Gopher] Android 12 is live in AOSP
___________________________________________________________________
Android 12 is live in AOSP
Author : skiman10
Score : 147 points
Date : 2021-10-04 17:05 UTC (5 hours ago)
(HTM) web link (android-developers.googleblog.com)
(TXT) w3m dump (android-developers.googleblog.com)
| schmorptron wrote:
| Material You is just gorgeous. I love the pastel color schemes it
| makes, and the shapes are very refreshing compared to what has
| been "in" for the last few years IMO
| Andrew_nenakhov wrote:
| YMMV but my gmail and dialer just recently got much uglier with
| blueish tones. Feels like Material UI was great looking around
| android 5.0 and goes downhill ever since.
| jeroenhd wrote:
| IMO Material only became good around Android 7. When Android
| 5 was still around, the boilerplate components were all way
| too big and the information density was incredibly low
| compared to Holo. Apps were tweaked and around Android 7 did
| I find them to be actually usable again.
|
| Google Calendar had this issue the worst if I recall. There
| were these gaudy, colourful images everywhere with cards
| sliding around and big, friendly buttons all over the place.
| The design looked pretty great during a quick presentation,
| but in practice I found it very hard to use the "stream" view
| calendar properly when I could see two or three events at
| most without scrolling.
| Andrew_nenakhov wrote:
| Sure, they did have a shortage of components, but the
| existing components were simple, clear, attractive. No ugly
| oval floating buttons or chiseled navbars hugging the FAB.
|
| Currently, the notes app is a good example of such
| uglyfication: what was previously a simple attractive app
| now sports a horrendous navbar with ugly squarerounded plus
| button of unclear color. Phew.
| tjoff wrote:
| For every new release of android there is only one thing I care
| about, how will this affect termux?
|
| So I did a google and looks promising (
| https://www.reddit.com/r/termux/comments/nyayhq/comment/h1j9...
| ).
| NotPractical wrote:
| Me too, haha. I like the new UI and privacy controls, but this
| is always the most important consideration.
|
| By the way, as far as I know, Termux (at least as we know it)
| is for sure eventually doomed, which is really sad. Here's a
| brief explanation for those uninitiated:
|
| * Android 10 introduced a restriction that apps targeting API
| version 29+ can no longer invoke exec() on files within the
| app's home directory, which breaks Termux [1].
|
| * An app can target any API version. There is a hardcoded
| "min_supported_target_sdk" in the Android source code (23 as of
| Android 12) [2], but as of now targeting a lower version only
| produces a warning, and it will likely take quite a long time
| before it reaches 29 anyway [3]. The main problem is that the
| Play Store won't allow new app updates targeting <29. For now,
| the Play Store Termux build is very out of date and it's
| recommended to get Termux from F-Droid. But for some reason,
| the developer of Termux has decided that they want to make
| Termux API 29 compatible [4]. (Perhaps to ensure long-term
| compatibility if the "min_supported_target_sdk" ever increases
| past 28 AND starts to actually be enforced, or maybe just
| because they want to distribute Termux in the Play Store, even
| though most of its users would be perfectly comfortable getting
| it from F-Droid?)
|
| * Making Termux API 29 compatible will make it a lot less fun
| and a lot less practical to use. All executables will have to
| be distributed inside separate APK files which must be
| individually installed, since exec() can now only be called on
| files in the read-only /data/app directory [5]. Say goodbye to
| `apt install <name>`.
|
| * Google continues to further restrict the OS in ways that
| break certain functionality within Termux.
|
| * Termux still works mostly normally for now in Android 10 and
| 11 (and 12, it seems), but its developer is already at work on
| the weird APK packaging system.
|
| [1] https://github.com/termux/termux-packages/wiki/Termux-and-
| An...
|
| [2]
| https://android.googlesource.com/platform/prebuilts/fullsdk/...
|
| [3] https://github.com/termux/termux-
| app/issues/1072#issuecommen...
|
| [4] https://github.com/termux/termux-
| app/issues/1072#issuecommen...
|
| [5] https://github.com/termux/termux-
| app/issues/1072#issuecommen...
|
| === EDIT ===
|
| According to the README, the current plan is actually to
| continue targeting API 28 for now:
|
| > There is currently no work being done to solve android 10
| issues and working updates will not be resumed on Google Play
| Store any time soon. We will continue targeting sdk 28 for now.
|
| They are looking for contributors to help make an API 29
| compatible version though:
|
| > @termux is looking for Termux Application maintainers for
| implementing new features, fixing bugs and reviewing pull
| requests since the current one (@fornwall) is inactive. Issue
| https://github.com/termux/termux-app/issues/1072 needs extra
| attention.
|
| https://github.com/termux/termux-app/blob/master/README.md#g...
| smusamashah wrote:
| I don't like Android 12 because of bigger zoomed in 'everything'.
| I don't like Windows 11 for kind of similar reason, less items in
| context menu, less customizable taskbar, bigger zoomed in start
| menu.
|
| Don't know what the f* is going on with "Modern" UIs.
| smusamashah wrote:
| I don't like Android 12 because of bigger zoomed in 'everything'.
| I don't like Windows 11 for kind of similar reason, less items in
| context menu, less customizable taskbar, bigger zoomed in start
| menu.
|
| Don't know what the f is going on with "Modern" UIs.
| danudey wrote:
| > Don't know what the f is going on with "Modern" UIs.
|
| I see this as a confluence of a few different things:
|
| 1. Monitors are getting higher and higher resolutions; a 4K
| display that's less than 27" is going to feel awfully tiny
| unless you start scaling things up.
|
| 2. Things have gotten more complicated over time, and the more
| complicated they get the more chances that something will mess
| up. At some point my gaming PC decided that it was going to
| take 30-90 seconds for the right-click context menu in Explorer
| to come up, and while it was waiting it would lock up Explorer.
| Simplification can be a good thing.
|
| 3. People designing software are getting older and have worse
| eyes, so larger, clearer, less noisy UIs are a godsend.
|
| Probably some other stuff.
| mschuster91 wrote:
| > 3. People designing software are getting older and have
| worse eyes, so larger, clearer, less noisy UIs are a godsend.
|
| "Modern" UIs most often are anything _but_ clear and less
| noisy. Part of what made the Windows 95 design so strong was
| that UI elements were separated by visible lines, you exactly
| knew what the touchbox of any element was, the behavior and
| look of UI elements, menus and icons were generally
| consistent across applications...
| mminer237 wrote:
| I think that's the worst part of the new Firefox UI.
| Firefox got rid of the defined, rectangular tabs using a
| colored background with lines between them. Now it's white
| rounded rectangles floating in a light-gray background with
| no other visible distinction. Even with perfect eyes, it
| was hard to tell what was going on without taking a moment
| to really focus on it.
| bserge wrote:
| Desktop? Miss me with that shit, I still stubbornly click
| "not now" whenever I unlock my laptop :D
| Le_Dook wrote:
| It clashes heavily with the container tabs add on as
| well. The new UI adds a coloured bar on top of a
| container tab, which I always mistake as an open tab
| since it's far more visible than the actual open tab
| indicator
| drusepth wrote:
| >Monitors are getting higher and higher resolutions; a 4K
| display that's less than 27" is going to feel awfully tiny
| unless you start scaling things up.
|
| Does this mean people who _don't_ buy 4K displays at those
| resolutions are going to be disadvantaged with strangely-huge
| UIs? (Side note: every OS I use already has display options
| to scale up UI 100-200+%, but not scale down less than a
| "normal" 100%.)
|
| It reminds me a little bit of when Apple's retina displays
| first came out and nobody knew how to handle widely-different
| resolutions, which resulted in huge UI/icons on normal-
| resolution monitors and fuzzy UI/icons on high-resolution
| ones, for the longest time.
| officeplant wrote:
| It's getting bad again on MacOS. Big Sur made window title
| bars vastly bigger. Using my new mini on a 1080P monitor is
| pain. I really hate that no one implements a 75% scaling
| option for MacOS or Windows.
|
| Saddest part is I have a replacement 1440P monitor showing
| up later in the week since I had to drag mine to work and
| it doesn't even help all that much. Macs in stores all have
| 2-5K resolution screens now ruining things for budget
| monitor folks with cheap Mac Minis.
| smusamashah wrote:
| If you account for the screen size only, even now we have
| more resolution the scale of elements on screen is bigger
| than what screen size allows for comfortable reading.
|
| To me these UIs improvements look like "dumbing down" of UI
| instead. Everything UX now suggests you the action it
| thinks you want to perform and hide all other options. Take
| context menu, start menu or taskbar in Windows 11 or in
| Android see the drop down from top bar which use to have
| more options visible at the same time in previous versions.
|
| This will surely work for anyone who is using these systems
| at very basic level (new users, people with accessibility
| needs?). For everyone else who spend their lives in these
| for work or hobby this dumbing is frustrating.
| e3bc54b2 wrote:
| As someone who used 768p 15" laptop until late 2019, yes,
| everyone else has to deal with bs huge menus. Oh the number
| of webpages that would have you scroll horizontally, often
| with white bar on both sides... The day I upgraded to 1080p
| I could feel a sense of joy in being able to see the web as
| it was designed. And now every web developer is beginning
| to develop on 27" (or less) 4K displays and the target is
| shifting for less fortunate yet again.
| spiffytech wrote:
| I asked a Googler about this years ago when Material Design was
| new. They told me that the general population has a harder time
| processing dense information views compared with computer
| geeks. Many folks find devices easier to use when there's less
| "going on" on-screen at once. If you bump up padding and
| margins, you not only reduce total visible information, but
| also spread out your UI elements, making it easier to visually
| identify which part of the screen holds the information you're
| looking for.
| jeroenhd wrote:
| For Android there's a setting that can scale down the modern
| UIs to render more on your screens. The "display size" setting
| seems to fix everything for me, even the UI for some games!
|
| If you configure the setting to be small enough many apps will
| detect your phone as a tablet, though, leading to some funky
| tablet layouts. Your mileage may vary, but for me everything
| works out great.
| progbits wrote:
| I tried going one size down in settings and while it does
| make the system UI better (more space for notifications etc)
| the majority of apps get unusable - everything is too small
| and hard to read, plus UI elements are closely packed to be
| clickable with fat fingers.
|
| I'm hoping that some apps adjust and start responding to the
| lower scale in a way that still makes it usable but maybe
| that can't be done and I'm stuck with the ridiculous UI.
| david_allison wrote:
| Likely due to accessibility: Standard guidelines for Android is
| that all touch targets should have a 48x48dp minimum size + 8dp
| spacing.
|
| https://www.bbc.co.uk/accessibility/forproducts/guides/mobil...
|
| https://material.io/design/usability/accessibility.html#layo...
| jeroenhd wrote:
| In my experience this is actually a good thing. Many
| application developers designing their own UI standards often
| leave buttons and touch targets that are way too small to
| accurately touch and it annoys the hell out of me. This often
| happens on the web as well!
|
| That said, I use Android's built-in UI scaling to reduce the
| size of icons and such that seem to have grown as phone
| screens became larger.
| barrkel wrote:
| Turn down the UI scaling. That works well enough for me. I also
| run Nova7 as my launcher, so I can control icon and text sizes
| independent of the UI scaling.
| smusamashah wrote:
| Scaling UI doesn't increase the number of buttons in the top
| at drop down visible at the same time. They use to be 9
| before Android 10 I think. In Android 12 they are even
| bigger. Scaling down won't fix it. I already use it scaled
| BTW.
| suyash wrote:
| Is there any decent Android (non Chinese) device that is free of
| Google privacy invading software ?
| johnasmith wrote:
| You can buy a pixel device and flash it to AOSP here:
| https://flash.android.com/
|
| Install a launcher of your choice and be on your way:
| https://www.tomsguide.com/uk/round-up/best-android-launchers
| suyash wrote:
| brilliant!
| throwaway78981 wrote:
| There is GrapheneOS too:
|
| https://nitter.mailstation.de/DanielMicay
| mdoms wrote:
| > Notification UI updates - We also refreshed notification
| designs to make them more modern and useful.
|
| Please.... please just for a couple of years can we stop doing
| this? Why does my notification UI have to change so frequently?
| IceWreck wrote:
| Google keeps on stripping down AOSP more and more. Its so
| barebones that nothing is usable out of the box anymore. It
| doesn't even have a web browser these days.
|
| All the default apps, contacts, calendar, etc haven't been
| updated in 8+ years.
|
| Any new feature doesn't come to AOSP, it comes to Google Play
| Services.
| anderskaseorg wrote:
| The browser is an extremely fast-moving security-critical
| attack surface, so it's for the best that Android WebView is
| maintained separately in the Chromium repository, and doesn't
| need to be held back by the AOSP release schedule. It's still
| open source.
|
| https://chromium.googlesource.com/chromium/src/+/HEAD/androi...
| phh wrote:
| It's fun that you should mention that, because assuming it is
| true that webview is best upgraded out-of-aosp (which I guess
| I kinda agree with), then why does AOSP ship with a webview?
|
| AOSP is lacking a browser, not a webview.
| mathfailure wrote:
| Why not just release AOSP as frequently? Then it'd be easier
| to push other small updates.
| jayd16 wrote:
| App store updates vs OS updates.
| xorcist wrote:
| This distinction is not definitive. None of the normal
| Linux distributions makes it.
| Lammy wrote:
| Relevant: https://arstechnica.com/gadgets/2018/07/googles-iron-
| grip-on...
| atatatat wrote:
| GrapheneOS ships a hardened Chromium fork.
|
| Worth looking into.
| danudey wrote:
| Optimism: This lets Google provide updates to users without
| carriers/manufacturers having to go through the process of
| approving Android updates for every model/carrier combination.
|
| Cynicism: The more that Google moves into Google Play Services,
| the harder it is for anyone to make a usable Android device
| without agreeing to Google's terms.
| lern_too_spel wrote:
| There are many open source contacts, calendar, etc. apps.
| Google is so caught up maintaining its own apps that talk to
| its services that I don't know why anybody would want Google's
| own half-assed open source implementations. Even if you wanted
| Google to maintain open source versions of those apps, why
| would you want them to be updated at the cadence that AOSP is
| and have them be developed in AOSP's non-collaborative manner?
| oehtXRwMkIs wrote:
| Sounds good to me. The less default apps the better. At this
| point they probably don't go further since it might cause
| system issues.
| tarkin2 wrote:
| From an app developer's point of view, the stuff shipped with
| AOSP is a mess that changes from version to version and from
| carrier to carrier and is almost impossible to develop against
| completely; and that's all solved with updates from google play
| services and external libraries.
| neodymiumphish wrote:
| It kind of makes sense, though. First, there are plenty of open
| source browsers available, why should Google maintain one when
| the vast majority are going to opt for Chrome anyway?
|
| Second, very few people want a contact or calendar app that
| exists solely on their phone. They want the synchronization
| they get from any alternative app, whether that's from
| Facebook, Google, Microsoft, or some other third party.
|
| If you're capable of installing AOSP on a daily driver, you
| likely already know enough about F-Droid or other open source
| projects to find and install a better alternative anyway.
|
| Lastly, I totally agree about your concern with GPS being the
| default for any new feature implementation. I think that
| allowing Google to push alternative OS builders out of the game
| or forcing them to implement a GPS alternative from scratch,
| which sucks.
| IshKebab wrote:
| > Second, very few people want a contact or calendar app that
| exists solely on their phone. They want the synchronization
| they get from any alternative app, whether that's from
| Facebook, Google, Microsoft, or some other third party.
|
| AOSP calendar supports syncing with online calendars.
| anderskaseorg wrote:
| Android WebView is embedded in zillions of apps, not just the
| standalone browser, so it would indeed suck if Google stopped
| maintaining it and forced apps to embed Chrome instead.
| Fortunately, that is not what happened--they just moved
| Android WebView from AOSP to the (arguably _more_ open)
| Chromium repository.
| kevincox wrote:
| > To help protect private app data, Android 12 changes the
| default behavior of the adb backup command. For apps that target
| Android 12 (API level 31) or higher, when a user runs the adb
| backup command, app data is excluded from any other system data
| that is exported from the device.
|
| It isn't "app data", it is my data! This is the straw that made
| me switch to LineageOS, my phone shouldn't prevent me from
| accessing my data!
| 2OEH8eoCRo0 wrote:
| Devil's advocate- that is one interface the feds will be trying
| to exploit in order to extract evidence but this change makes
| it a little harder.
| summm wrote:
| The feds will just subpoena Google or the app author.
| JoshTriplett wrote:
| If your device is fully encrypted, nobody can run an adb
| backup without authorization. This change does not protect
| the user; it "protects" apps.
| Someone1234 wrote:
| So now to "help protect private app data" they've gone from a
| terrible backup experience (running adb backup) to essentially
| no backup experience.
|
| Unless of course you want to pay Google money and even then
| arguably get a subpar backup experience.
|
| Keep in mind that you have to unlock the device AND authorize
| USB debugging just to get adb backup to run.
| White_Wolf wrote:
| I was actually waiting for 12 rollout before installing TWRP on
| the 9Pro. Now I'm not so sure it's a good idea... I'm having
| trouble as is is making changes to system apps and Priv-App,
| don't need more headaches.
|
| Looks like you are right dude. Might as well start getting used
| to Lineage. I'll miss the oneplus camera apps though.
| shadilay wrote:
| "You will own nothing and be happy."
| https://www.forbes.com/sites/worldeconomicforum/2016/11/10/s...
| summm wrote:
| https://www.xda-developers.com/lineageos-seedvault-open-sour...
|
| >LineageOS adopts SeedVault as its open source backup solution
| [...] >For those not familiar with SeedVault, it is an open-
| source backup app that uses the same internal APIs as adb
| backup.
|
| I hope the SeedVault people are able to circumvent that. And I
| hope they are _willing_ to try, as some open source developers
| for some reason consider Google 's user-hostile security model
| decisions as sacrosanct.
| bserge wrote:
| Since this is LineageOS, I assume everyone is running a
| custom recovery. Why not use Nand backups then?
|
| I just wonder because that's all I ever used. Just straight
| up bypasses any BS the OS would throw... on the same device
| at least.
| summm wrote:
| The advantage of app backup is that you can restore the
| apps to _other_ devices. And you can selectively backup and
| restore subsets of apps. Nand backups do not offer that.
| Furthermore your assumption might not be true in the first
| place: LineageOS brings its own default recovery that
| offers more convenient OTA updates, but does not offer Nand
| backups. Also, "custom" recoveries such as TWRP might not
| even support some phones that are supported by LineageOS.
| bserge wrote:
| Yeah, I figured. I think I tried "normal" backups a few
| times with garbage results and gave up on it.
|
| Just straight up reinstall everything on new machines or
| major OS version updates like I've been doing for nearly
| two decades.
|
| Good time to reconsider a lot of apps, too.
| adamch wrote:
| Very happy about the speed and privacy improvements. I'm excited
| to install this.
| ehsankia wrote:
| Gonna predict some of the more controversial changes:
|
| - Removing GPay/DeviceControls from power menu
|
| - The new overscroll stretch animation
|
| - The new lockscreen clock (very hit and miss)
|
| - The new Material You widgets
|
| Any I missed?
| izacus wrote:
| Web intent resolution change is probably going to create a lot
| of drama when someone actually notices it.
| MonaroVXR wrote:
| What do you mean by that?
| rickdeckard wrote:
| I don't know how to feel about the introduction of splash screens
| for all apps.
|
| I imagine they were needed to disguise some initial rendering of
| the app, but as a user I really _really_ don 't want to see
| splash screens when opening an app on a mobile device...
| gerash wrote:
| It used to be against UX guidelines in Android but if the app
| startup cannot be any faster I don't mind a splash screen.
| Basically anything that indicates the phone has not frozen up
| even if it ends up taking a quarter second longer.
|
| What I find truly jarring is when I tap on a UI element and it
| responds after 2 seconds. I'd take splash screen and slow
| animation over that anyday.
| jeroenhd wrote:
| My theory is that this is because of Flutter apps that
| sometimes struggle to initialize quickly from a cold start.
| They had (have?) this issue on iOS and I've seen some of them
| have the problem on Android too, something to do with shaders
| if I recall correctly.
|
| I hate seeing splash screens. When I encounter them, I see that
| as a sign that the developers weren't capable enough or didn't
| care enough to make their app start up quickly. I'm fine with
| games showing splash screens as they unpack resources and load
| shaders, but a chat app or a calendar shouldn't have to show me
| a "look at me I'm loading" screen.
| MonaroVXR wrote:
| I hate this when in visiting "Outlook.com" and especially
| when I go from mail to calendar.
| ruined wrote:
| Windows 11
|
| macOS 11
|
| Debian 11
|
| Android 11
|
| this is the only reason android 12 was released
| rustyminnow wrote:
| Android 8.0 Oreo
|
| Android 9 Pie
|
| Android 10
|
| Android 11
|
| ... Are probably the reasons android 12 was released
| NullPrefix wrote:
| This could all be an elaborate set up for android 13.
| yathern wrote:
| I'm pretty sure a new version of Android comes out every year.
| If Windows 11 wasn't announced, do you think they'd hold off
| for a while?
|
| https://en.m.wikipedia.org/wiki/Android_version_history#Over...
| yjftsjthsd-h wrote:
| iOS 15
|
| Ubuntu 21.04
|
| Opensuse 15.3
|
| FreeBSD 13
|
| Be careful you don't cherry pick your data points
| ruined wrote:
| iphone 11. checkmate
| synergy20 wrote:
| As an embedded linux developer, what Android brings is an unified
| UI(after all those x-windows variants plus Qt GUI). As long as
| the below list remains to be OSS, Android can be used in many
| non-realtime devices that need a GUI(with/without touchscreen):
|
| * the linux kernel * the ART(java jvm) which most GUI apps
| depending on * base code to support the multimedia
| stack(video/audio) * NDK(c/c++)
|
| There are many devices can use Android for applications that have
| no need for google play store apps at all.
| poisonborz wrote:
| In addition to other regressions mentioned here, Android 12 also
| removes the ability to set a custom "share" screen (akin to
| Sharedr).
| nemacol wrote:
| This is only tangentially related but... Anyone else cringe /
| feel and overwhelming desire to turn off any video like the first
| one in this article (#AndroidDevSummit: tune in October 27-28!)
| where someone speaks in that excessively excited and optimistic
| voice? It is as cliche and gag inducing to me as the infomercial
| voiceover guy explaining how something simple thing is a disaster
| and how they have now solved it.
|
| I can't turn that shit off fast enough.
|
| Also, I really like Keri Byron from Myth busters, etc. This is
| not a complaint about a personality or whatever. Just this
| delivery that seems to be everywhere in tech sales pitches and
| time shares.
| PKop wrote:
| Agree and feel the same way with presentations like this. Also,
| I dislike how so many tech presentations have such a childish
| tone or silliness to them all the time, instead of just
| presenting information to adults as adults in a normal way.
| It's very distracting in my opinion.
| comeonseriously wrote:
| I agree. I also like Kari so it's not her. I dig tech stuff, I
| just don't need a cheerleader.
| dyingkneepad wrote:
| For _years and years_ I watched Kari Byron dubbed in my native
| language. And the dubbers are mostly really good over there,
| great actors. Today I got to hear her real voice for the first
| time, and it was... weird. I feel some kind of immersion has
| been broken. There are quite a few shows I can 't watch in
| English due to the real actors (or English dubbers) being worse
| than the dubbers of my countries. I'll add Kari to the list.
|
| Other than that, she's great! I'm a huge fan.
|
| Edit: it's Kari.
| [deleted]
| chronogram wrote:
| I didn't think it was at all excessively excited and
| optimistic. Just presented with a smile like any host I expect
| to do. I thought it was fine. Maybe it's cultural.
| silviot wrote:
| I also find that style annoying, to the point that I wonder why
| it's even in use. I always thought it was an American thing,
| given it's barely present in my country, and when it's used it
| sounds ridiculous to most people.
| Andrew_nenakhov wrote:
| Previously, I used to be excited about new OS versions coming
| out. Nowadays, I'm only looking for what did they break or block
| this time, and how much problems would it cause.
| dimeatree wrote:
| Yes, I am in the same boat here. It feels like there is always
| a new iOS or Android version being released which always
| manages to break a feature on my app and sheds months off of my
| life.
| bserge wrote:
| Because a new night mode or yet another needless redesign is
| not an update. They seem to have a quota of "updates" to fill
| tbh.
| myko wrote:
| Same.
|
| I was thinking about this when I first saw this announcement
| and realized that if AOSP was developed in the open it probably
| wouldn't change anything. Releasing big updates of the open
| source code like this feels pointless.
| Andrew_nenakhov wrote:
| AOSP is practically dead, all important parts replaced by
| proprietary Play Services. I think it is only a matter of
| time before google replaces Android and Linux with Fuchsia.
| kllrnohj wrote:
| This isn't remotely true. Nearly all the advertised Android
| 12 features are in AOSP, not Play Services. People _vastly_
| overestimate how much stuff is in Play Services.
| yjftsjthsd-h wrote:
| > Releasing big updates of the open source code like this
| feels pointless.
|
| Custom ROMs still benefit
| Frenchgeek wrote:
| It's not like you can easily update the OS in a smartphone, to
| begin with...
| fsflover wrote:
| Unless it's made with a user in mind, like Librem 5 or
| Pinephone.
| atatatat wrote:
| Or a Pixel
|
| _ducks_
|
| that lets you unlock and, wait for it, _re_ lock the
| bootloader after installing Graphene.
| summm wrote:
| But graphene does not let you do anything more than AOSP,
| specifically it does not trust you enough to let you have
| root while using a locked bootloader.
| marcelnita wrote:
| Sadly, the update to Pixel phones comes in the next few weeks
| they say.
|
| https://9to5google.com/2021/10/04/android-12-aosp/
| rcMgD2BwE72F wrote:
| Are you sad that you can review the source code _before_ the OS
| gets installed on your device?
| sodality2 wrote:
| Can't verify the compiled source is what gets delivered to
| your Pixel device, though.
| encryptluks2 wrote:
| Still better than what Apple offers.
| [deleted]
___________________________________________________________________
(page generated 2021-10-04 23:01 UTC)