Tag: Google Mobile Services

  • Android 15 Requires Minimum 32GB Storage for Phones

    Android 15 Requires Minimum 32GB Storage for Phones

    Key Takeaways

    1. Minimum storage requirement for Android 15 is now 32GB, with 75% reserved for user data and apps.
    2. Devices with less than 2GB of RAM cannot run Android 15; those with 2GB or 3GB must use low RAM optimizations.
    3. New chipsets must support Vulkan 1.3 or later and include ANGLE libraries instead of OpenGL ES drivers.
    4. Devices using the AOSP version won’t be certified and will lack access to Google services like the Play Store.
    5. Users must have the option to share contact info with Emergency Location Service, with OEMs required to provide clear notices.

    Google has updated the minimum RAM and storage needs for Android devices with version 15. These updates are specifically for Android 15 smartphones that come with Google’s Mobile Services (GMS).

    New Storage Standards

    For the first time since 2022, the minimum storage requirement has increased to at least 32GB, with 75% of that space set aside for user data and applications. Reports from Android Authority mention that devices with less than 2GB of RAM will not be able to run the new operating system.

    RAM and Chipset Requirements

    Devices boasting 2GB or 3GB of RAM must implement Android’s low RAM optimizations to achieve certification. Meanwhile, devices with 4GB of RAM or more have the option to adopt these optimizations. Furthermore, Google mandates that new chipsets must be compatible with Vulkan 1.3 or later.

    Graphics and Legacy Support

    Devices operating on Android 15 are required to include the Almost Native Graphics Layer Engine (ANGLE) libraries instead of the older OpenGL ES drivers. This change allows newer devices that lack OpenGL support to still run older applications.

    There is an alternative available: devices that utilize the Android Open Source Project (AOSP) version of the OS can still launch devices that do not meet these system requirements. However, these devices will not receive certification or access to essential Google applications like the Google Play Store.

    User Privacy and Transparency

    Alongside these new hardware standards, smartphones must give users the choice to share their contact information with Android’s Emergency Location Service (ELS). Google also requires that original equipment manufacturers (OEMs) provide clear notices regarding the information shared with this service.

    Source:
    Link

    Tags: , ,
  • Google Confirms AOSP Will Stay Open-Source Amid Private Shift

    Google Confirms AOSP Will Stay Open-Source Amid Private Shift

    Key Takeaways

    1. AOSP has provided access to mobile operating system source code for nearly 16 years.
    2. Google is merging AOSP development into a private branch, accessible only with a GMS license.
    3. The public version of AOSP has become increasingly outdated compared to the private branch.
    4. Google aims to streamline its development process with this shift.
    5. AOSP will remain open-source, but updates will come after work on the private branch is completed.

    The Android Open Source Project (AOSP) has given people access to the source code for one of the top operating systems for mobile gadgets like smartphones and tablets for almost 16 years. But now, Google is making a big change in how this works.

    Changing Development Branches

    For most of its existence, AOSP development has been managed under two main branches of its documentation: the public one, which is released under Apache 2.0, and a private one that needs a Google Mobile Services (GMS) license to access. Over the past few years, these two branches have started to differ more and more, with the public version often being outdated compared to the private one.

    Recently, Google has chosen to officially move all parts of AOSP to the private branch. When Android Authority asked for a comment on this shift, the tech giant from Mountain View said it was done to “streamline its development process.”

    Future of AOSP

    Google has promised to keep AOSP open-source by continuing to release the source code, but only after finishing work on the private branch. This means that the impact on regular users is expected to be minimal. However, some experts might view this as a sign that custom Android development is coming to an end.

    Source:
    Link

    Tags: , ,