Whilst Google announced a ton of AI powered features for Android 14 at Google I/O, it seems like most of them will be Pixel exclusive…

Hoping Samsung does more with OneUI 6 since Google’s really pushing for Pixel exclusivity on Android now 🙄

  • AlmostDachshund
    link
    fedilink
    English
    81 year ago

    Android 14 is the most underwhelming updated yet. Google didn’t even promote it well on I/O. About OneUI 6, I just wish Samsung updates the control center. It’s too outdated. I know it’s simple and working well, but I would love some visual tweaks.

  • Joe B
    link
    English
    31 year ago

    I hope one UI gets a face lift. It’s so Samsung lol

    • @lka1988
      link
      English
      61 year ago

      Not a bad thing, honestly. Free RAM is wasted RAM.

      • @[email protected]
        link
        fedilink
        English
        21 year ago

        Exactly. The way Android manages RAM is not the same as Windows, ie. full memory utilisation ≠ out-of-memory scenario.

      • @haxasaur
        link
        English
        11 year ago

        Depends how much free RAM we talking but yeah.

    • @DevgardOP
      link
      English
      11 year ago

      this I’m excited for! Also a more useful share sheet!

  • @[email protected]
    link
    fedilink
    English
    21 year ago

    But of course the restriction to sideloading older apps exists for all Android 14 phones…

    • @DevgardOP
      link
      English
      11 year ago

      what restrictions?

      • @[email protected]
        link
        fedilink
        English
        41 year ago

        You now can’t even sideload an app with a target SDK level that is too low. This locks you out of a bunch of older abandoned FOSS apps that often are very lightweight on storage.

        • @DevgardOP
          link
          English
          11 year ago

          sidenote: what is the purpose of the target SDK? why do both minimum and target SDKs have to exist?

          • @henfredemars
            link
            English
            31 year ago

            The purpose is backward and forward compatibility respectively.

            The minimum version is the easiest to explain: any older, and your app just won’t run. Don’t even try. I (app) don’t have the compatibility code to work with you if you are older than my minimum version because I didn’t choose to include it, and you (Android) don’t know the changes that were made in the future platform versions, so you can’t help me.

            Target version is a little more complex. This is the version of the API that I am designed to run with. You can use this information to set compatibility parameters for forward compatibility. For example, if I try to use API that doesn’t exist in your version or that would have had different behavior, you would know what I’m expecting because I declared to you what it was designed for at the time. This allows the system to tolerate your outdatedness better.

            However, that compatibility feature sometimes leads to security issues because the new API tends to be more restricted or improved in ways that enhance security and privacy, hence the argument why there should be a minimum target version to express that you cannot use the less secure API even for the sake of compatibility.

  • @TheYang
    link
    English
    21 year ago

    having only just moved to android 13, it seems a bit weird

    but as someone without google apps… Android updates don’t seem to change a lot anymore

  • Balder
    link
    English
    2
    edit-2
    1 year ago

    deleted by creator

  • @vividspecter
    link
    English
    11 year ago

    I’m hoping for opus Bluetooth support in AOSP and not just for Pixel. Better yet if it was the pipewire version (which is more extensive) but I doubt that.