LightBlog

mardi 5 avril 2022

How to download Android 12 and 12L for Google Pixel and other Android devices

The wait is finally over — Android 12L is here as Google has officially kicked off the update rollout via stable channel. If you’re the lucky owner of a Google Pixel 6, Pixel 6 Pro, Pixel 5a, Pixel 5, Pixel 4a 5G, Pixel 4a, Pixel 4, Pixel 4 XL, Pixel 3a, or the Pixel 3a XL, then you can have the opportunity to try out the latest iteration of Android right now. During the beta phase, Generic System Images (GSI) are also available, which means the early builds can be booted on non-Google Project Treble compatible devices as well.

Alongside the supported Google Pixel devices, Android 12 as a major version is also available on a wide range of devices from different OEMs — either in the form of beta or stable builds. In case you’re looking for the answer to the question “when will my phone get Android 12?“, take a look at the following OEM-specific trackers to find out:

This page will serve as a one-stop download index for all the Android 12/12L stable, Beta, and Developer Preview releases. We will keep the page updated with the latest OTAs and factory images for the supported Pixel series of devices. You can learn how to install the Android 12/12L on Google Pixel smartphones by visiting our dedicated guide here.

Navigate this page:


Download Android 12 QPR Beta for Google Pixel devices

QPR3 Beta 1.1 (S3B1.220218.006)

For the Google Pixel 6 series, you can download the Android 12 QPR3 1.1 from the index below:


QPR3 Beta 1 (S3B1.220218.004)

For eligible Google Pixel devices, you can download the first beta build of Android 12 QPR3 from the index below:

You can also download the official Generic System Image (GSI) packages from the index below:

GSI Downloads

Architecture GSI Package
x86_64+GMS Download Link
ARM64+GMS Download Link
x86_64 Download Link
ARM64 Download Link

Download Android 12 and 12L Stable for Google Pixel devices

April 2022 release (SP2A.220405.003 || SP2A.220405.004 for the Google Pixel 6 series)

For eligible Google Pixel devices, you can download the latest stable Android 12L build with the April 2022 security patches from the index below::


March 2022 release (SP2A.220305.012 || SP2A.220305.013.A3 for the Google Pixel 6 series)

For eligible Google Pixel devices, you can download the first stable build of Android 12L with the March 2022 security patches from the index below:


Mid-February 2022 release (SQ1D.220205.004)

The Google Pixel 6 series has received a special mid-February build that brings along some smaller, under-the-hood changes.

Device OTA Factory Image
Google Pixel 6 Download Link: Download Link:
Google Pixel 6 Pro Download Link: Download Link:

February 2022 release

For Google Pixel devices, you can download the stable Android 12 build with the February 2022 security patches from the index below:

Device OTA Factory Image
Google Pixel 3a Download Link: Download Link:
Google Pixel 3a XL Download Link: Download Link:
Google Pixel 4 Download Link: Download Link:
Google Pixel 4 XL Download Link: Download Link:
Google Pixel 4a Download Link: Download Link:
Google Pixel 4a 5G Download Link: Download Link:
Google Pixel 5 Download Link: Download Link:
Google Pixel 5a Download Link: Download Link:
Google Pixel 6 Download Link: Download Link:
Google Pixel 6 Pro Download Link: Download Link:

Additionally, the Google Pixel 3 and Pixel 3 XL have also received their final update in February. The new build is still on the October 2021 security patch level.


January 2022 release

For Google Pixel devices, you can download the stable Android 12 build with the January 2022 security patches from the index below:

Device OTA Factory Image
Google Pixel 3a Download Link: Download Link:
Google Pixel 3a XL Download Link: Download Link:
Google Pixel 4 Download Link: Download Link:
Google Pixel 4 XL Download Link: Download Link:
Google Pixel 4a Download Link: Download Link:
Google Pixel 4a 5G Download Link: Download Link:
Google Pixel 5 Download Link: Download Link:
Google Pixel 5a Download Link: Download Link:
Google Pixel 6 Download Link: Download Link:
Google Pixel 6 Pro Download Link: Download Link:

Additionally, the Google Pixel 3 and Pixel 3 XL have also received a bug fix update in January. It doesn’t bump up the security patch level, though.

Device OTA Factory Image
Google Pixel 3 Download Link: Download Link:
Google Pixel 3 XL Download Link: Download Link:

Older builds from 2021

December 2021 release

For Google Pixel devices, you can download the stable Android 12 build with the December 2021 security patches from the links below:

Device OTA Factory Image
Google Pixel 3a Download Link: Download Link:
Google Pixel 3a XL Download Link: Download Link:
Google Pixel 4 Download Link: Download Link:
Google Pixel 4 XL Download Link: Download Link:
Google Pixel 4a Download Link: Download Link:
Google Pixel 4a 5G Download Link: Download Link:
Google Pixel 5 Download Link: Download Link:
Google Pixel 5a Download Link: Download Link:
Google Pixel 6 Download Link: Download Link:
Google Pixel 6 Pro Download Link: Download Link:

Keep in mind that Google doesn’t offer the Pixel 6/6 Pro’s December 2021 builds anymore due to the buggy nature of them. Although you can still download the packages using the aforementioned links, it is highly recommended to stay away from this release.


Mid-November 2021 release

The Google Pixel 6 series has received a special mid-November build to improve the fingerprint sensor’s performance.

Device OTA Factory Image
Google Pixel 6 Download Link: Download Link:
Google Pixel 6 Pro Download Link: Download Link:

November 2021 release

For Google Pixel devices, you can download the stable Android 12 build with the November 2021 security patches from the links below:


October 2021 release

For Google Pixel devices, you can download the first stable Android 12 build with the October 2021 security patches from the links below:



Android 12/12L Beta and Developer Preview builds

If you need to download older beta and/or Developer Preview builds, you can found them listed below:

Beta and Developer Preview builds

It is worth mentioning that the beta/preview builds don’t have all the new software features you can associate with the final release of Android 12 and 12L. To be precise, Google gave developers the chance to test their apps against new Android platform APIs months before the new Android version became available for the general public. Hence, the builds mentioned below are aimed at the developer community only and are not intended to be used by end-users.

Navigate this section:

Android 12L Beta 3

Google Pixel

GSI Downloads

Architecture GSI Package
x86_64+GMS Download Link
ARM64+GMS Download Link
x86_64 Download Link
ARM64 Download Link

Android 12L Beta 2

Google Pixel

GSI Downloads

Architecture GSI Package
x86_64+GMS Download Link
ARM64+GMS Download Link
x86_64 Download Link
ARM64 Download Link

Android 12L Beta 1

Google Pixel

GSI Downloads

Architecture GSI Package
x86_64+GMS Download Link
ARM64+GMS Download Link
x86_64 Download Link
ARM64 Download Link

Download Android 12 Beta 5

Google Pixel

GSI Downloads

Architecture GSI Package
x86_64+GMS Download Link
ARM64+GMS Download Link
x86_64 Download Link
ARM64 Download Link

Download Android 12 Beta 4.1

Google Pixel

GSI Downloads

Architecture GSI Package
x86_64+GMS Download Link
ARM64+GMS Download Link
x86_64 Download Link
ARM64 Download Link

Download Android 12 Beta 4

Google Pixel

GSI Downloads

Architecture GSI Package
x86_64+GMS Download Link
ARM64+GMS Download Link
x86_64 Download Link
ARM64 Download Link

Download Android 12 Beta 3.1

Google Pixel

GSI Downloads

Architecture GSI Package
x86_64+GMS Download Link
ARM64+GMS Download Link
x86_64 Download Link
ARM64 Download Link

Download Android 12 Beta 3

Google Pixel

GSI Downloads

Architecture GSI Package
x86_64+GMS Download Link
ARM64+GMS Download Link
x86_64 Download Link
ARM64 Download Link

Download Android 12 Beta 2.1

Google Pixel

GSI Downloads

Architecture GSI Package
x86_64+GMS Download Link
ARM64+GMS Download Link
x86_64 Download Link
ARM64 Download Link

Download Android 12 Beta 2

Google Pixel

GSI Downloads

Architecture GSI Package
x86_64+GMS Download Link
ARM64+GMS Download Link
x86_64 Download Link
ARM64 Download Link

Download Android 12 Beta 1

Google Pixel

GSI Downloads

Architecture GSI Package
x86_64+GMS Download Link
ARM64+GMS Download Link
x86_64 Download Link
ARM64 Download Link

Download Android 12 Developer Preview 3


Download Android 12 Developer Preview 2.2


Download Android 12 Developer Preview 2.1


Download Android 12 Developer Preview 2


Download Android 12 Developer Preview 1.1


Download Android 12 Developer Preview 1

The post How to download Android 12 and 12L for Google Pixel and other Android devices appeared first on xda-developers.



from xda-developers https://ift.tt/k6GxhQM
via IFTTT

How to Root your Android smartphone: Google, OnePlus, Samsung, Xiaomi, and others too!

Welcome to the XDA-Developers Root Directory. Here, you can find root tutorials for most devices that are on the XDA Forums. Learn how to root any Android device, even the best Android phones! If you don’t see your device listed or you see a misplaced link, send a message to Skanda Hazarika (SkandaH on the forums) with the device details.

Table of Contents:

What is Root?

For those new to the world of rooting, acquiring root access essentially grants you elevated permissions. With root access, you are able to alter or replace system applications and settings, run specialized apps that require administrator-level permissions or perform other operations that are otherwise inaccessible to a normal Android user. And by proxy, you may also be able to access certain “hidden” device features or use existing features in new ways.

DISCLAIMER: Rooting a device may void the warranty on the device. It may also make the device unstable or if not done properly, may completely brick the device. XDA-Developers or the author does not take any responsibility for your device. Root at your own risk and only if you understand what you are doing!


How to root a popular Android smartphone

We can go on about the virtues of root access ad infinitum, but we’ll stop for now because we can sense you’re salivating at the prospect of root access and what you can do with your device once root is achieved. Head to the following section to begin the journey. You should find device-specific root guides for latest flagship models from every major OEM below.

ASUS

For other ASUS devices, kindly check out the ASUS section of our forums. You should be able to find similar fine-tuned guides for your device under the device sub-forums. You can also follow the generic rooting guide from this tutorial.

Google

For other Google devices, kindly check out the Google section of our forums. You should be able to find similar fine-tuned guides for your device under the device sub-forums. You can also follow the generic rooting guide from this tutorial.

Motorola

Sr. No. Device Codename and Device Forum Root Guide
1. Motorola G100/Edge S nio Click Here
2. Motorola Edge 20 Pro/Edge S Pro pstar Click Here

For other Motorola devices, kindly check out the Motorola section of our forums. You should be able to find similar fine-tuned guides for your device under the device sub-forums. You can also follow the generic rooting guide from this tutorial.

OnePlus

For other OnePlus devices, kindly check out the OnePlus section of our forums. You should be able to find similar fine-tuned guides for your device under the device sub-forums. You can also follow the generic rooting guide from this tutorial.

Samsung

For other Samsung devices, kindly check out the Samsung section of our forums. You should be able to find similar fine-tuned guides for your device under the device sub-forums. You can also follow the generic rooting guide from this tutorial.

Sony

Sr. No. Device Codename and Device Forum Root Guide
1. Sony Xperia 1 III pdx215 Click Here
2. Sony Xperia 5 III pdx214 Click Here
3. Sony Xperia 10 III pdx213 Click Here

For other Sony Xperia devices, kindly check out the Sony section of our forums. You should be able to find similar fine-tuned guides for your device under the device sub-forums. You can also follow the generic rooting guide from this tutorial.

Xiaomi

For other Mi, Redmi, and POCO branded devices, kindly check out the Xiaomi section of our forums. You should be able to find similar fine-tuned guides for your device under the device sub-forums. You can also follow the generic rooting guide from this tutorial.


How to root any Android device

Nowadays, Magisk is the de-facto rooting solution that lets you have root access by leaving the system partition untouched and modifying the boot partition. This is why it’s referred to as a “systemless” root method.

Before getting started with Magisk, make sure that:

  • You have access to a PC/Mac with adb and fastboot installed.
  • The bootloader of the target Android device is unlocked.
    • For Samsung devices, unlocking the bootloader will trip KNOX.

Step 1: Identifying the type of the boot image

Download the latest version of the Magisk app from the project’s GitHub repository. Since the APK of Magisk is hosted outside of the Google Play Store, you may need to allow sideloading apps from unknown sources first and then manually install the downloaded package.

After installing, open the Magisk app. You should see a screen like this:

Magisk main app window

Now, we need to note down the values of the following parameters:

  • Ramdisk
  • A/B
  • SAR

Step 2: Locating the boot image

In order to patch the boot image for your device, you need to extract it from the official firmware packages. In case you’re using a custom ROM like LineageOS, then the flashable ZIP file contains the boot image.

Case I: You have access to the recovery-flashable ZIP file

If you have a device that still uses the A-only partition scheme, then you can find the boot.img right inside the recovery-flashable ZIP file. Just extract it using a suitable archiver program.

POCO M3 boot.img inside recovery ZIP

Notice the boot.img file inside POCO M3’s recovery ZIP

However, if your device utilizes the A/B partition scheme, then the boot image and other partition images are further packed inside a file named payload.bin as shown below.

Google Pixel 5 payload.bin inside recovery ZIP

The recovery ZIP of the Google Pixel 5 contains a payload.bin file

In that case, you have to extract the payload.bin file first, then use one of the community-developed payload.bin unpackers to get the boot.img out of it. We strongly suggest you opt for the extractor written in Go as it is cross-platform and has been actively developed.

Known as “payload-dumper-go”, this fork even allows end-users to extract a single partition image without unpacking the whole payload.bin, which is particularly useful for this usage scenario.

  • First, use the -l parameter to list the partition images inside the payload.bin.
    payload-dumper-go -l payload.bin
  • Then use the -p parameter with the name of the boot image (commonly stored as “boot”) to extract it.
    payload-dumper-go -p boot payload.bin
ASUS ROG Phone 5 boot.img from payload.bin

Extracting the boot.img of the ASUS ROG Phone 5 from its payload.bin

Case II: You have access to the Fastboot-flashable image

A handful of OEMs like Google and Xiaomi provide Fastboot-flashable factory images for their devices. If you managed to grab such a package, then the raw boot.img can easily be extracted from the archive.

Google Pixel 5 boot.img from Fastboot package

The location of the boot.img inside the Google Pixel 5’s Fastboot firmware

Special Case: Samsung

Samsung Galaxy devices don’t a traditional Fastboot interface, hence their factory images are packed differently.

  • Use Samsung Firmware Downloader to download the factory image for your model.
  • Unzip the decrypted package and locate the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5.

Step 3: Patching the boot image

Now that we have the boot image in hand, we should proceed with the patching part.

Case I: The value of the “Ramdisk” parameter is “Yes”

  • Copy the boot image to your device. In fact, you can patch it on a different Android device than the target one, but you need to install the Magisk app on the secondary device as well.
  • Press the Install button in the Magisk card.
  • Choose Select and Patch a File in Method, and select the stock boot image.

Magisk select and patch image

  • The Magisk app will patch the image to [Internal Storage]/Download/magisk_patched_[random_strings].img.

Magisk is patching a boot image

  • Copy the patched image to your PC with ADB:
    adb pull /sdcard/Download/magisk_patched_[random_strings].img
  • Flash the patched boot image to your device. For most devices, reboot into Fastboot mode and flash with the following command:
    fastboot flash boot /path/to/magisk_patched.img
  • Reboot and enjoy root access!

Keep in mind that it is possible to patch the boot image on the fly on legacy devices having boot ramdisk through a custom recovery like TWRP, but the method is no longer recommended on modern devices. Having said that, if you have an old phone and want to stick with the custom recovery route, the steps are as follows:

  • Download the Magisk APK.
  • Rename the .APK file extension to .ZIP (e.g. Magisk-v23.0.APK → Magisk-v23.0.ZIP).
  • Flash the ZIP file just like any other ordinary flashable ZIP.

Magisk flashing via TWRP

  • Note that the sepolicy.rule file of modules may be stored in the cache partition, so don’t clear it.
  • Check whether the Magisk app is installed. If it isn’t installed automatically, manually install the APK.

Case II: The value of the “Ramdisk” parameter is “No”

In this case, you need to locate the recovery.img file from the factory image of your device instead of boot.img file. This is because Magisk needs to be installed in the recovery partition, which means you will have to reboot to the recovery mode every time you want root access.

  • Copy the recovery image to your device (or a secondary device with the Magisk app installed).
  • Press the Install button on the Magisk card.
  • Choose “Select and Patch a File” in method, and select the stock recovery image.
  • The Magisk app will patch the image to [Internal Storage]/Download/magisk_patched_[random_strings].img.
  • Copy the patched image to your PC with ADB:
    adb pull /sdcard/Download/magisk_patched_[random_strings].img
  • Flash the patched recovery image to your device. For most devices, reboot into Fastboot mode and flash with the following command:
    fastboot flash recovery /path/to/magisk_patched.img
  • Reboot.

At this stage, there are three possible scenarios:

  • Power up normally: You’ll end up with no Magisk, i.e. no root access.
  • Recovery Key Combo → Splash screen → Release all buttons: The system should boot with Magisk and full root access.
  • Recovery Key Combo → Splash screen → Keep pressing volume up: To access the stock recovery mode.

Special Case: Samsung

  • Copy the extracted AP tar file to your device.
  • Press the Install button on the Magisk card.
  • If your device doesn’t have boot ramdisk, make sure Recovery Mode is checked in options.
  • Choose Select and Patch a File in Method, and select the AP tar file.
  • The Magisk app will patch the whole firmware file to [Internal Storage]/Download/magisk_patched_[random_strings].tar
  • Copy the patched tar file to your PC with ADB:
    adb pull /sdcard/Download/magisk_patched_[random_strings].tar
    • Don’t try to copy over the MTP interface as it is known to corrupt large files.
  • Reboot to download mode. Open Odin on your PC, and flash magisk_patched.tar as AP, together with BL, CP, and CSC from the original firmware.
    • Don’t choose HOME_CSC because we want to wipe data.
  • Your device should reboot automatically once Odin finished flashing. Agree to do a factory reset if asked.
  • If your device doesn’t have boot ramdisk, reboot to recovery now to enable Magisk.
  • Install the latest Magisk app and launch the app. It should show a dialog asking for additional setup. Let it do its job and the app will automatically reboot your device.
  • Reboot and enjoy root access!

Step 4: Verification

The last step is to verify that everything is working properly. Locate the newly installed Magisk app and open it. We want to see a version number beside the “Installed” parameter. This means you have successfully obtained root. Great job!

A successful installation of Magisk


One-Click Root Methods in 2021: Kingroot, KingoRoot, and others

A few years back, several generic root methods like Kingroot, KingoRoot, and others gained popularity as “one-click root” methods, promising root and related benefits with minimal steps and knowledge needed by the user. However, as Android has matured, these one-click root methods are no longer valid for modern smartphones and Android devices in 2021.

We strongly dissuade against the use of these generic root methods as they are either ineffective or worse, pack in malware that can greatly compromise your device and cause you losses. Practically all of these methods are no longer recommended. You should follow the steps listed above for an effective root solution for most Android devices.


We hope this guide not only points you to the right threads for rooting your device but also provides general rooting instructions that can be applied for a large majority of Android devices generally. We’ll be updating this guide with links to further guides for specific phones, so check back again in the future.

The post How to Root your Android smartphone: Google, OnePlus, Samsung, Xiaomi, and others too! appeared first on xda-developers.



from xda-developers https://ift.tt/wLxGDk8
via IFTTT

At a Glance widget on Pixel phones receives “Earthquake alert” and “Saftey check” countdown

The At a Glance widget on Pixel phones can do much more than just show weather and day/date info. It can display your upcoming events, flight boarding pass, Nest doorbell alerts, workout stats, and much more. The widget recently started showing Connected device info for your Bluetooth devices on the home screen and lock screen. And now it’s getting two more capabilities.

As spotted by 9to5Google, Google has started rolling out earthquake alert warnings and “Safety check” to At a Glance. These features were announced as part of the March Feature Drop last month, but it’s only now that they’re making their way to users. When an earthquake larger than magnitude 4.5 is detected in your area, At a Glance will display an alert on the home screen and lock screen. It should be noted that Android already has a built-in earthquake detection and alerts system. The system, developed in partnership with the United States Geological Survey (USGS,) uses sensors on your Android phone to detect earthquakes around the world and provides automatic early warnings to users.

At a Glance earchquake toggle At a Glance saftey check toggel Pixel

Screenshot credit: 9to5Google

In addition, At a Glance can now also display the Safety check countdown from the Personal Safety app. When you enable safety check, you’ll see the countdown timer appear in the At a Glance widget. This allows users to quickly glance at the timer from the home screen or lockscreen without having to keep the Personal Safety app open all the time.

Earthquake alert and Safety check features are rolling out to At a Glance on Pixel devices. To see if they’re available for you, long-press on the home screen, select “Home settings” from the pop-up menu, and tap on the gear icon.

Have you received “Earthquake alert” and “Safety check” toggles on your Pixel phone? Let us know in the comments below.


Source: 9to5Google

The post At a Glance widget on Pixel phones receives “Earthquake alert” and “Saftey check” countdown appeared first on xda-developers.



from xda-developers https://ift.tt/vsL4tol
via IFTTT

Redmi Note 11 Pro Plus 5G Unboxing: What’s in the box?

Xiaomi has an extensive portfolio in key Asian markets like India, China, Indonesia, and beyond. Thanks to its insane value, the Redmi Note series is one of the most popular mobile lineups globally. For 2022, Xiaomi has a full refresh for its Redmi Note lineup, with devices like the Redmi Note 11 Pro Plus 5G occupying the top-end within this branding. Xiaomi launched the Redmi Note 11 Pro Plus 5G in India in March, and the company launched another device with the same name for the global market as well. If you are wondering what do you get inside the box for the Indian Redmi Note 11 Pro Plus 5G, we’re here to answer that question for you.

What’s inside the Redmi Note 11 Pro Plus 5G (India) retail box?

Box contents from the retail packaging of the Xiaomi Redmi Note 11 Pro Plus 5G (Indian version)

The box of the Redmi Note 11 Pro Plus 5G (India) [device codename: peux] includes the following content:

  • Redmi Note 11 Pro Plus 5G (in the color you’ve chosen)
  • Mi 67W SonicCharge 3.0 Charger
  • USB-A to USB-C cable
  • Basic TPU/silicon case
  • SIM ejection tool
  • Region-specific documentation, including Quick Start Guide

Xiaomi packs in a fair bit when it comes to its retail phone boxes. Unlike other OEMs who have adopted a charger-less packaging for even their mid-range devices, Redmi is including a charger in the box, at least so far. And you don’t just get any ordinary charger with the Redmi Note 11 Pro Plus 5G — you get the 67W Mi SonicCharge 3.0 charger, which is a Qualcomm Quick Charge 3.0 charger that you can use to charge devices beyond your smartphone as well. Xiaomi also includes a fairly basic case for the device too, and the phone comes with a basic screen protector applied.

    Redmi Note 11 Pro Plus 5G (India)
    The Redmi Note 11 Pro Plus 5G is one of Xiaomi's mid-range offerings for the Indian market. Featuring well rounded specifications, the phone has everything that most average users would require.

All in all, you have everything in the box to get you started with using the device properly, though we do recommend switching out the case for something a bit more protective or fashionable a few months down the line.

The post Redmi Note 11 Pro Plus 5G Unboxing: What’s in the box? appeared first on xda-developers.



from xda-developers https://ift.tt/2rUeq3C
via IFTTT

Realme Pad Mini packs an 8.7-inch display and a 6,400mAh battery in a slim body

Realme joined the Android tablet bandwagon with the Realme Pad last year. Now the Chinese company has released a brand new tablet called the Realme Pad Mini. The latest tablet focuses on portability and affordability and offers a decent hardware package, including an 8.7-inch display, a slim design, and a large battery.

Realme Pad Mini: Specifications

Specification Realme Pad Mini
Dimensions and Weight
  • 211.8 x 124.5 x 7.6mm
  • 372g
Display
  • 8.7-inch LCD
  • 1340 x 800
  • 60Hz screen refresh rate
  • Sunlight mode
SoC
  • Unisoc T616 octa-core chipset
    • Up to 2.0GHz
    • Arm Mali G57 GPU
RAM and Storage
  • 3GB/4GB RAM
  • 32/64GB flash storage
  • MicroSD card support
Battery & Charging
  • 6,400 mAh battery
  • 18W fast charger (inside the box)
Rear Camera
  • 8MP primary shooter
Front Camera
  • 5MP front-facing camera
Ports
  • USB Type-C port
  • 3.5mm headphone jack
Connectivity
  • 4G LTE
  • Bluetooth 5.0
  • Type-C port
  • WiFi 802.11.b/g/n/ac (2.4GHz + 5GHz)
Other features
  • Dual stereo speakers
Software
  • Android 11 with Realme UI for Pad

If you’re looking for a cheap Android tablet with an iPad Mini-like form factor, the Realme Pad Mini certainly fits the bill. It features a slim design with narrow side bezels and rounded corners. The front of the tablet is dominated by an 8.7-inch LCD, offering a 1340 x 800 screen resolution and sunlight mode support.

Realme Pad Mini blue

On the inside, the Realme Pad Mini is powered by a Unisoc T616 octa-core chipset, paired with 3GB/4GB RAM and 32GB/64GB flash storage. In terms of cameras, there’s a single 8MP shooter on the back housed in a rectangular island and a 5MP front-facing camera embedded into the top bezel.

Realme Pad Mini features

The Realme Pad Mini packs a 6,400mAh battery and supports fast charging via an 18W charger. Other highlights of the tablet include 4G LTE support, dual stereo speakers, Bluetooth 5.0, dual-band Wi-Fi, and microSD card support. The Realme Pad Mini runs Android 11 out of the box with Realme UI for Pad on top.

Pricing & Availability

The Realme Pad Mini is available for pre-order in the Philippines starting today. Available in Gray and Blue colors, the tablet is priced at PHP9,990 (~$195) for the base model and PHP11,990 (~$235) for the top variant. Realme hasn’t shared any details about the international availability of the tablet.


Source: Lazada
Via: GSMArena

The post Realme Pad Mini packs an 8.7-inch display and a 6,400mAh battery in a slim body appeared first on xda-developers.



from xda-developers https://ift.tt/fDCF6mX
via IFTTT

lundi 4 avril 2022

Download and install the latest GApps: Open GApps, NikGApps, FlameGApps, and more!

GApps (short for Google Apps) packages are essential in the Android aftermarket development community. They are specially crafted optional add-ons for custom ROMs that can be used to get Google apps such as Google Play Services and the Play Store on your device. If you’re wondering how to pick and install the right GApps package on your device or on one of the best Android phones, this guide should help you with that.
Table of Contents:

In case you don’t see your favorite GApps distribution mentioned here, send a message to Skanda Hazarika (SkandaH on the forums) with the necessary details.

Why GApps?

Google requires every Android device maker to follow the Compatibility Definition Document (CDD) to pass the Compatibility Test Suite (CTS) so they can be allowed to pre-load their devices with Google apps and services. Custom ROM developers however can’t easily bundle these Google apps and services with their builds. As these apps are not using the Apache or GPLv2 license, bundling them within the ROM presents legal challenges.

This is exactly where the GApps packages come in. The GApps maintainers rely on build scripts that allow for the automated creation of new updated packages at regular intervals. ROM developers, on the other hand, usually build the custom ROMs in such a way that an end-user can flash a third-party GApps distribution on top of their builds and seamlessly gain the ability to use the Google Play Store or any other applications that require Google Play Services.

Keep in mind Google apps are not required to boot or run most custom ROMs. However, many users find them beneficial to take full advantage of the Android ecosystem.


Variants of GApps

For a regular user, a bunch of first-party Google applications have gradually become integral to Android’s functionality or look and feel. Then come those who prefer an absolute minimalistic setup and consider virtually everything as bloatware.

Since it’s really hard to come up with a common solution for all, the GApps maintainers usually offer several variants of their builds. That’s the reason you can find GApps packages with “pico”, “basic”, “full”, and similar tags. Of course, the Play Store, along with obligatory Play Services and related libraries, are the common components between them, but the number of bundled first-party Google applications is the key differentiating factor out there.

Compatibility with older Android versions is another interesting aspect of the GApps scene. Not all devices can run the latest and greatest version of Android even with the help of custom ROMs, which is why it’s necessary to maintain support for older releases. Moreover, some low-level libraries are dependent on the CPU architecture, so mainstream maintainers sometimes offer architecture-specific builds as well.


Popular GApps Distributions

Throughout the years, many different GApps distributions have gained popularity. Below you can find some of the most well-liked and actively maintained GApps offerings from the aftermarket development community.

Open GApps

Perhaps the most popular choice to download Google Apps on custom ROMs, the Open GApps project started its journey back in 2015 as the spiritual successor to the ParanoidAndroid GApps. The codebase of this distribution has been forked numerous times, all thanks to the project’s versatility, extensive documentation, and rich support for legacy Android builds.

Download Open GApps

XDA Discussion Thread on Open GApps

  • Android Version Support: Android 4.4 KitKat to Android 11. The maintainers also offer test packages for Android 12 and Android 12L.
  • Platform Support: ARM, ARM64, x86, and x86_64.
  • Variants:
    • Pico: This package is designed for users who want the absolute minimum GApps installation available.
    • Nano: This package is designed for users who want the smallest Google footprint possible while still enjoying native “Okay Google” and Google Search support.
    • Micro: This package is designed for users of legacy devices with small system partitions or those who prefer a minimalistic approach.
    • Mini: This package is designed for those who use limited Google apps or prefer to install apps on their own.
    • Full: If you prefer the option to use stock/AOSP apps, this package is designed for you.
    • Stock: This package includes all the Google Apps that come standard on the Pixel smartphones.
    • Super: This package is for those who want to have all Google Applications. It includes all Google Apps that were ever shipped on a Google device.
    • Aroma: The Aroma package is a special version of the regular ‘Super’ package, but with a graphical front-end that will allow you to select which specific applications to install (or not) without having to manually write a gapps-config file.
    • TVStock: This package is for Android TV devices. It includes all the Google Apps that come standard on the Nexus Player.
    • TVMini: A smaller set of Google Apps for Android TV devices, similar to what Mini has compared to the Stock variant.

NikGApps

NikGApps is another feature-rich GApps distribution that offers extensive customization options for power users. Created by XDA senior member Nikhil, one of the most distinguishing features of this GApps project is it comes with a dedicated Android Go package for low end devices. Unlike other distributions, it also allows you to dirty flash the package anytime you want.

Download NikGApps

XDA Discussion Thread on NikGApps

Last but not least, users can upload their custom configurations to the project’s repository to create a personalized build.

  • Android Version Support: Android 10 to Android 12. There is no official support for Android 12L yet.
  • Platform Support: ARM64.
  • Variants:
    • Core: The minimum Google Apps set required to run Play Store.
    • Basic: Everything from Core, plus Google Carrier Services, Google Dialer (Replaces AOSP Dialer), Google Messages (Replaces AOSP Messages), Google Contacts (Replaces AOSP Contacts), etc.
    • Omni: Everything from Basic, plus Gmail (Replaces AOSP Email), Google/Pixel Setup Wizard, Google Photos (Replaces AOSP Gallery), etc.
    • Stock: Everything from Omni, plus Google Sound Recorder, Google Markup, Google Sounds, Google Wallpaper, etc.
    • Full: Everything from Stock, plus Google Chrome (Replaces AOSP Browser), Google Assistant, Android Auto, etc.
    • Go: Meant for low-end devices. A slightly enhanced version of the Core variant.

FlameGApps

Formerly known as “ExLiteGApps”, the FlameGApps project is the brainchild of XDA senior member ayandebnath. Thanks to the modular design of the distribution, end users can install various components like Pixel Launcher with Device Personalization Services, Google Search with Assistant, and Device Personalization Services using official add-on packages.

Download FlameGApps

XDA Discussion Thread on FlameGApps

  • Android Version Support: Android 10 to Android 12. For Android 12L, you need to modify the latest Android 12 release before flashing until official support arrives.
  • Platform Support: ARM64.
  • Variants:
    • Basic: Includes the core GApps like Google Play Services (GMS), Google Services Framework (GSF), Google Play Store, and other essentials.
    • Full: Includes all the necessary core apps with more useful ones like Google Dialer, Google Contacts, Google Messages, etc.

BiTGApps

With less than 90MB size, BiTGApps from XDA senior member TheHitMan is a distinctive minimalistic distribution. Besides the minimalism, it also offers a handful of unique features, such as enabling battery optimization for all Google apps, the ability to install directly from a booted system, and installing in a systemless manner as a Magisk module.

Download BiTGApps

XDA Discussion Thread on BiTGApps

  • Android Version Support: Android Nougat (7.1.2 and 7.1.1) to Android 12. There is no official support for Android 12L yet.
  • Platform Support: ARM, ARM64.
  • Variants:
      • Minimal: The goal is to stick with a minimal setup that can provide proper Google Services functionality. There are no other variants.

MindTheGapps

Maintained by LineageOS contributor Alessandro Astone, AKA XDA senior member aleasto, MindTheGapps is yet another compact GApps distribution. This one is particularly known in the community for being the officially recommended GApps solution by the LineageOS team for its custom ROM.

Download MindTheGapps (Mirror)

  • Android Version Support: Android 10 to Android 12L. The official mirror also hosts legacy packages for Android 9 Pie and Android 8.1 Oreo.
  • Platform Support: ARM, ARM64, x86.
  • Variants: None. There’s only a single variant with no customization options. It provides everything required to make use of Google systems and no more.

How to Install GApps

Download and Preparation

Before installing a GApps package, you need to pick the version that matches the CPU architecture of the target device and the Android base of your desired custom ROM. Keep in mind some OEMs deliberately ship ARM32 firmware on ARM64 devices, so consult with the custom ROM maintainer to determine platform compatibility. In case you’re going to flash a custom ROM that ships with integrated Google apps, then you don’t need to install a standalone GApps package.

To know the CPU architecture, run the following command using a terminal emulator app on your device:

getprop ro.product.cpu.abi

Crudely speaking, if you have a smartphone that’s fairly recent and you’re planning to install a custom ROM based on Android 12, download one of the ARM64 GApps for Android 12 from the aforementioned list.

For the actual flashing process, we’ll assume you have a custom recovery like TWRP installed and (optionally) have root access. If not, we have guides on how to root your Android device and how to install TWRP.

Flashing GApps from TWRP

Warning:  In most cases, the GApps package must be flashed before booting into the custom ROM for the first time! It’s always recommended to factory reset and format data to clear out any possible residue of a previously installed GApps distribution.

  • Make sure your computer has ADB and Fastboot. Setup instructions can be found here.
  • Download both the custom ROM package and the matching GApps package on your computer.
  • Reboot the target device into recovery mode using the appropriate key-combo or using ADB:
adb reboot recovery

TWRP main menu

  • Now tap on Wipe, Factory Reset, and finally Format Data to continue with the cleanup process. This will remove encryption and delete all files stored in the internal storage.
  • Return to the main menu.
  • Sideload the custom ROM ZIP package:
      • On the target device, select Advanced, then ADB Sideload to begin sideload.
  • TWRP ADB Sideload
  • On the host machine, sideload the package using:
adb sideload filename.zip
  • Without rebooting, tap on the back button, then repeat the same process for the GApps package.
adb sideload gaaps.zip

macOS terminal adb sideload gapps

  • The TWRP screen on the target device should show the installation progress.

TWRP adb sideload gapps

  • Once you have installed everything successfully, tap on the Reboot System button.
  • Voila!

Validation

If everything goes right, you should get the Google apps and services ready to use once you reboot.

LineageOS 18.1 with NikGApps

LineageOS 18.1 with GApps

Most GApps distributions and custom ROMs support OTA survival, which means it’s not necessary to re-flash a GApps package when you install a ROM update. A major version update is another story though, as you have to locate the appropriate GApps package for the new Android base and if necessary, make a clean install.


What is your preferred GApps package of choice? Let us know in the comments below!

The post Download and install the latest GApps: Open GApps, NikGApps, FlameGApps, and more! appeared first on xda-developers.



from xda-developers https://ift.tt/lgEp1Sw
via IFTTT

Weird Android Auto bug causes the Assistant to switch between regional variants of some languages

One of the handy features of Android Auto is its ability to read out notifications, allowing you to stay up to date with your work emails and messages while driving. But it appears the feature is not working as intended for some users due to a newly discovered bug.

According to recent user reports, Google Assistant on Android Auto is unable to differentiate between regional variants of some languages. As Android Auto user Renato M. Coimbra writes:

I live in Brazil and I speak Portuguese from here, but out of the blue the assistant started reading the messages from WhatsApp in Portuguese from Portugal.

Another Android Auto user, also from Brazil, commented on the thread stating that he too was facing the same issue, with Google Assitant reading WhatsApp and messages and SMS in Portuguese (Portugal) instead of Portuguese (Brazil). Both users mention that the issue only happens with select apps, WhatsApp and SMS apps in particular. Other app notifications are seemingly working fine.

The issue is not limited to just one language, either. A Canadian user reports that he has run into a similar issue on his Android Auto device, with Google Assistant reading Messenger and SMS notifications in French (France) rather than Canadian French, the default Assistant language.

The Assistant speaks French from Canada but messages (Messenger & SMS) are read in French from France instead. Not happening with all notifications, emails from Gmail seem fine for example.

It’s not immediately clear how widespread this issue is and whether it affects other mutually intelligible languages.

A member from the Android Auto team confirmed that they’re currently looking into the issue. We’ll keep an eye out and let you know if and when we get more details from Google on the matter.

Android Auto recently rolled out a new USB diagnostics tool that makes it easier to identify bad USB cables by running a quick test.


Source: Android Auto Help
Via: Auto Evolution

The post Weird Android Auto bug causes the Assistant to switch between regional variants of some languages appeared first on xda-developers.



from xda-developers https://ift.tt/8SQMKV1
via IFTTT