yashsingh1/xdaforums huggingface dataset:
[Nothing Phone 2] HippoMan:
I'm using OS 2.0.3 on my Nothing 2 phone.

I am unable to remove Quicksettings tiles.

Here's what I do ...

* I pull down the notification bar and then again on the status bar, so that a little "pencil" icon shows at the lower right of the Quicksetting tiles that are displayed.

* I click on the little "pencil" icon, and the full list of Quicksettings tiles are now shown, and "Edit" appears at the upper left.

* For each Quicksetting tile that I don't want, I drag it down to the "Drag here to remove" area. Each tile I drag indeed disappears from the set of active Quicksetting tiles that are displayed.

HOWEVER (!!!) ...

After I exit "Edit" mode, all the Quicksetting tiles that I have removed now reappear in the set of Quicksetting tiles that are available.

Is there something that I'm missing that I need to do in order for Quicksetting tiles to be properly removed?

Thank you in advance for any thoughts and suggestions.
[Nothing Phone 2] HippoMan:
Oh! Never mind! I was trying out "System UI Tuner", and that program is what was causing the Quicksetting tiles to become unremovable.

After freezing "System UI Tuner", I can now remove Quicksettings tiles.

I'll leave this thread here, in case it could possibly help someone else.
[Raspberry Pi Original Development] KonstaT:
Here’s my build of AOSP (Android 14) for Raspberry Pi 4 Model B, Pi 400, and Compute Module 4. It’s for advanced users only. Pi 4 model with at least 2GB of RAM is required to run this build.

Important! Raspberry Pi hardware specific implementation in this build is based on source code released on my Raspberry Vanilla project but this build still offers various additional features and enhancements over that. This image includes parts that are licensed under non-commercial license (Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International). You may use this build freely in personal/educational/etc use. Commercial use is not allowed with this build! You can contact me by email to discuss creating customized Android builds for commercial purposes.

AOSP (Android 14)

for Raspberry Pi 4

konstakang.com

Working:

Audio (HDMI, 3.5mm jack, USB microphones, bluetooth speakers/headphones, etc)

Audio DAC (using GPIO DACs e.g. Hifiberry DAC+)

Bluetooth (and bluetooth tethering)

Camera (using official Pi camera modules & UVC USB webcams)

GPIO

GPS (using external USB modules e.g. U-Blox 7)

Ethernet

Hardware accelerated graphics (V3D, OpenGL & Vulkan)

Hardware video decoding & encoding (H.265 decoding, H.264 decoding & encoding)

HDMI display (and HDMI-CEC)

I2C

IR remotes (using external GPIO IR modules e.g. TSOP4838)

RTC (using external GPIO I2C modules e.g. DS3231)

Sensors (using external GPIO I2C modules e.g. MPU6050, LSM6DS3, LSM303DLHC, BME280/BMP280, and APDS9930 accelerometer, gyroscope, magnetometer, temperature, pressure, humidity, ambient light, and proximity)

Serial console (using external GPIO serial console adapters e.g. PL2303)

SPI

Touchscreen/multi-touch (official 7” touchscreen, USB touchscreens, Waveshare SPI touchscreens)

USB (mouse, keyboard, storage, etc)

USB-C (ADB, MTP, PTP, USB tethering)

Wifi (and wifi tethering)

Issues:

Various issues with CSI camera modules

SELinux is in permissive mode

Encrypting userdata is not supported

and more…

Sources:

Android

Linux kernel

Thanks:

Roman Stratiienko and GloDroid project

Peter Yoon and android-rpi project

AOSP reference board developers (dragonboard, hikey, yukawa)

Android-x86 project
[Raspberry Pi Original Development] KonstaT:
How to install:

Follow the official Raspberry Pi instructions for writing the image to the SD card.

You can also update to newer builds using TWRP flashable OTA packages.

Download AOSP14-xxxxxxxx-KonstaKANG-rpi4-ota.zip and save it to your device’s internal storage or use an external USB drive

Boot to TWRP recovery (see FAQ)

Install AOSP14-xxxxxxxx-KonstaKANG-rpi4-ota.zip from your selected storage

(Flash GApps/Magisk/Widevine/other add-ons you had previously installed)

Boot out of recovery (see FAQ)

Changes that are backed up and restored flashing OTAs:

Device specific settings changed using Settings -> System -> Raspberry Pi settings

Manual changes to /boot/resolution.txt and /boot/rc_keymap.txt

USB boot configuration in /boot/config.txt

User specific options in /boot/config_user.txt

Changes that are not backed up and restored flashing OTAs:

Manual changes to /boot/config.txt (and any other manual changes to /boot partition)

GApps

Magisk

Widevine

FAQ:

FAQ is getting quite long and difficult to maintain in several different places. You can find the always up-to-date FAQ here:

https://konstakang.com/devices/rpi4/AOSP14/
[Raspberry Pi Original Development] KonstaT:
4.7. changelog:

update to latest AOSP release (Android 14 QPR3 - android-14.0.0_r52)

update to libcamera master/v0.3.0, libpisp v1.0.6

update to FFmpeg 7.0.1, AOSP dav1d 1.4.2

update to alsa-lib/alsa-utils v1.2.12

update to Mesa 24.1.3

update to Linux 6.1.90 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)

Android security patch level: 5 July 2024

Linux 6.6 kernel: (optional add-on)

update to Linux 6.6.36 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)

8.5. changelog:

update to latest AOSP release (Android 14 QPR2 - android-14.0.0_r34)

move serial console to the UART connector

switch external camera HAL to AIDL (improves boot time)

sensor HAL fixes (thanks to Kethen)

update to libcamera master/v0.2.0, libpisp v1.0.5

update to FFmpeg 6.0.2, AOSP dav1d 1.4.1

update to alsa-lib/alsa-utils v1.2.11

update to Mesa 24.0.6

update to Linux 6.1.80 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)

Android security patch level: 5 May 2024

Linux 6.6 kernel: (optional add-on)

new Raspberry Pi Android kernel bring-up based on AOSP android15-6.6

update to Linux 6.6.29 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)

4.1. 2024 changelog:

update to latest AOSP release (Android 14 QPR1 - android-14.0.0_r20)

fix HDMI-CEC issue (affected DSI displays, displays on secondary HDMI port, and headless mode)

update to Mesa 23.3.2

update to Linux 6.1.65 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)

Android security patch level: 5 January 2024

23.11. changelog:

update to latest AOSP release (android-14.0.0_r14)

include AOSP13 wpa_supplicant to fix connecting to protected networks

add support for booting from NVME (custom CM4 I/O boards with M.2 slot)

improve audio DAC detection

improve CPU overclocking option (Pi 4B R1.4+ and Pi 400 clocked at 1800MHz by default)

fix native screen recording

update to TWRP 3.7.0_11-1-KonstaKANG

update to new Raspberry Pi utils (vcgencmd, pinctrl, etc)

update to v4l-utils master/1.25.0

update to FFmpeg 6.0.1, AOSP dav1d 1.3.0

update to libcamera master/v0.1.0

update to Mesa 23.3.0-rc4

update to Linux 6.1.61 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)

Android security patch level: 1 November 2023

11.10. changelog:

initial release (android-14.0.0_r1)

switch to btlinux bluetooth stack

update bluetooth firmware to fix connecting BLE devices

convert light and health HALs to AIDL

implement USB gadget HAL

Mesa 23.2.1

FFmpeg 6.0, dav1d 1.3.0

alsa-lib/alsa-utils v1.2.10

libcamera v0.0.5

Linux 6.1.43 kernel

Android security patch level: 5 October 2023

Previous builds:

AndroidFileHost
[Raspberry Pi Original Development] KonstaT:
https://twitter.com/i/web/status/1724851946853409149
[Raspberry Pi Original Development] mad0701:
Hi,

what is the minimum HW , which shall available during boot?

Background: I Flash the image with the imager from raspberry and try also etcher.

Boot with the default settings, I see only a black screen.

If I delete the resolution.txt, I can see the boot logo,(Android which change the brightness as animation) but nothing else. Its stuck on this screen.

The monitor is connect via the original HDMI cable. The monitor has only a DVI Input, so I use a HDMI to DVI Adapter.

For example, this combination was working with a retro Image for a test. The monitor has a solution of 1600x900 Pixel.

I have try also Lineage, but here is only a black screen visible. Also if I connect the RPI4 (8Gb) on a HDMI TV via normal HDMI connector.

Thanks in advanced
[Raspberry Pi Original Development] KonstaT:
The minimal (and very usual) setup would be Raspberry Pi 4/400/CM4 with at least 2GB of RAM, sufficient power source (3.0A), sdcard (at least class 10 - the faster the better), HMDI display that reports resolutions it supports via EDID, and some input device (e.g. USB keyboard/mouse).
[Raspberry Pi Original Development] mad0701:
Thx for replay. UNcomfortable the PI4 (8G) is in a Flirc case. If I have a new thermo material. I can extract him and connect a serial log- Device.

HW: Ri4 (8Gb), orginal Powersupply, 64G SD Ultra card, USB Keyboard (Or Mouse .. it doesn't make different) and a Monitor via DVI Adapter. I've insert as custom config:

hdmi_group=2

hdmi_mode=83 1600×900 // with Reduced blanking

hdmi_cvt 1920 1080 60 3 0 0 1 // 16:9 and activ blanking.

If I start the PI and monitor, I'm still in a boot-loop. Only "ANdroid" is visible on screen (with animation ) and after a while, the PI restarts... Nothing else.

I'm not 100% sure, if the PI supported with this resolution also 60Hz, because I have not found this information:

hdmi_mode=80 2560×1600 120 Hz Reduced blanking

hdmi_mode=81 1366×768 60 Hz

hdmi_mode=82 1080p 60 Hz

hdmi_mode=83 1600×900 Reduced blanking

hdmi_mode=84 2048×1152 Reduced blanking

hdmi_mode=85 720p 60 Hz

hdmi_mode=86 1366×768 Reduced blanking

If I start -as try- Android from Emteria, this version can start into Android after the splashscreen. Any idea, what I can try additional?
[Raspberry Pi Original Development] KonstaT:
hdmi_* options in config.txt have no effect with KMS driver that is used with hw accelerated graphics on Android builds (and recent Raspberry Pi OS versions as well). These relate to configuring the fake/firmware KMS (i.e. 'dtoverlay=vc4-fkms-v3d').

There has been reports that booting in headless mode (i.e. without any display connected) or using DSI display does not work on AOSP14 likely due to some change in HDMI-CEC handling. Could be related since you're not using an actual HDMI display.

DSI display no longer working on 14? · Issue #37 · raspberry-vanilla/android_local_manifest

Tried my own image (followed the instructions in the wiki to modify those files) and yours (set for touchscreen in Raspberry Pi settings). I just get a blank screen, or the display briefly fades to...

github.com

I'm not aware of any other Android releases on Raspberry Pi that support HDMI-CEC.
[Raspberry Pi Original Development] mad0701:
I haven't also no luck with an old HD TV. But I can give you another feedback in a few days. I've order a 15,6 HD Monitor with Touchpanel. On the PI 4 the Touchpanel must be connected to an USB port (HDMI to HDMI) because the the RPI 4 has not the capability to transfer Pictures and Sound over USB-C. So I hope, that the monitor supported CEC....
[Raspberry Pi Original Development] mad0701:
Btw: On your HP is written

"You can change value in /boot/resolution.txt to use a different resolution that your display supports"

How can I change to anotther resolution? Only change the new resolution in the resolution.txt does have no effect on my side... Maybe another thing does not work as expected, because the boot screen animation is still there, before the RP4 is restarted?
[Raspberry Pi Original Development] KonstaT:
Yes, the other thing being HDMI-CEC.

That's exactly the same behaviour as with DSI display or no display at all as discussed in the issue linked above. There's a forced reboot after a while.

You can also use Android 13 based releases where this is not an issue.
[Raspberry Pi Original Development] KonstaT:
New build.

AOSP (Android 14)

for Raspberry Pi 4

konstakang.com

update to latest AOSP release (android-14.0.0_r14)

include AOSP13 wpa_supplicant to fix connecting to protected networks

add support for booting from NVME (custom CM4 I/O boards with M.2 slot)

improve audio DAC detection

improve CPU overclocking option (Pi 4B R1.4+ and Pi 400 clocked at 1800MHz by default)

fix native screen recording

update to TWRP 3.7.0_11-1-KonstaKANG

update to new Raspberry Pi utils (vcgencmd, pinctrl, etc)

update to v4l-utils master/1.25.0

update to FFmpeg 6.0.1, AOSP dav1d 1.3.0

update to libcamera master/v0.1.0

update to Mesa 23.3.0-rc4

update to Linux 6.1.61 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)

Android security patch level: 1 November 2023
[Raspberry Pi Original Development] KonstaT:
Make sure that you have connected the display on the HDMI0 port (not the secondary HDMI1 port). This was reported to have fixed similar issue for someone else.

This could be caused by the same issue that is linked under 'Isssues' (https://github.com/raspberry-vanilla/android_local_manifest/issues/37). It's HDMI-CEC related and can be reproduced when there's no HDMI display present (using DSI display, running headless without any display connected, etc). My HDMI-CEC HAL uses HDMI0 by default so having the display in the secondary port is likely enough to trigger the issue as well.
[Raspberry Pi Original Development] DerBaLu841:
I have booted the rom with my pi4 and installed Nikgapps core via TWRP. Now i have a bootloop. Are there any gapps i should use for this rom?
[Raspberry Pi Original Development] mad0701:
I'll test it tomorrow once again.....

Btw: Is there a chance, that the GPU will be have better performance in future?

Reason: If I try to run pinball application, the ball is stottering much more as with a very old (10y) tablet
[Raspberry Pi Original Development] KonstaT:
GApps are not part of my releases so if you're having issues with some specific GApps release, you would need to ask where you got it.

MindTheGapps have been reported working. Also please read the relevant FAQ section for installation instructions (includes performing a factory reset) and to have selected the right type of package (Android 14, arm64).

There isn't any specific issue with GPU performance that I'm aware of. IMO it actually performs quite well with Mesa drivers (and Mesa is constantly updated to latest stable release in my builds). GPU hardware itself isn't going to get any better unless you update to Pi 5.

Could be due to some other issue but impossible to say without seeing any logs.
[Raspberry Pi Original Development] mad0701:
Try other packages from here (there are not so much possibilities)

Android 14 GApps Download

Android 14 GApps contains all Google Apps packages which are required after installing an Android 14 custom ROM. Visit this link to download several GApps packages.

cyanogenmods.org
[Raspberry Pi Original Development] mad0701:
It was planed to used the PI4 as standalone small little pinball machine...But it looks like so, that the GPU is to bad for this one.

Another question:

In this moment the Android Version AOSP 13 (with gapps and installed pinball applications from Google is running (On a 15,6Zoll Touch screen monitor = new one / the test with the old DVI 22" monitor is still outstanding.)

Could I update the system with the OTA Android14 packet without losing the registration on Google and also without losing the installed application?
[Raspberry Pi Original Development] KonstaT:
You would of course download the GApps package from the project's own download page rather than some spam/scam site. Rather please remove the link.

I always recommend clean installation between Android versions to avoid any issues. For most users updating between Android versions would also mean updating any possible add-ons at the same time (e.g. GApps). While it should be generally possible to update from my AOSP13 release to AOSP14, in this case that's probably not even possible due to switching to updatable APEXes in Android 14 (vs. flattened APEX in Android 13). You would need to make a clean installation in any case.
[Raspberry Pi Original Development] mad0701:
Ok, so I would extracted the Google ID and hopefully replaced in the Version 14...
[Raspberry Pi Original Development] mad0701:
deleted...Gapps on Android host are only till Android 10 ...
[Raspberry Pi Original Development] DerBaLu841:
mindinthegapps works on this rom. After restart into twrp and install Magisk i got a bootloop and break my system. i just want to use the Raspberry Pi as an alternative for my FireTV Stick. I need root, gapps and the ATV Launcher as Standard Launcher and Netflix, Disney, Amazon, Crunchyroll installed from playstore (easy update ;-) ). What would be the best practice for me? Thanks for your help
[Raspberry Pi Original Development] KonstaT:
Buying an actual Android TV device with unlockable bootloader (if you can even find one)? And you still probably can't achieve all that because of SafetyNet/Play integrity and DRM restrictions.
[Raspberry Pi Original Development] daimon68:
I have an rpi 4 8gb I can't run this AOSP 14 in any way I get stuck on the android logo and after the rpi it restarts and starts again

everything ok with the aosp 13 no problems
[Raspberry Pi Original Development] KonstaT:
Discussed on the previous page.

This issue is now sorted and will be fixed if/when there's another release.
[Raspberry Pi Original Development] daimon68:
thanks it was enough to connect in hdmi0 now AOSP 14 It's ok
[Raspberry Pi Original Development] KonstaT:
New build.

AOSP (Android 14)

for Raspberry Pi 4

konstakang.com

update to latest AOSP release (Android 14 QPR1 - android-14.0.0_r20)

fix HDMI-CEC issue (affected DSI displays, displays on secondary HDMI port, and headless mode)

update to Mesa 23.3.2

update to Linux 6.1.65 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)

Android security patch level: 5 January 2024
[Raspberry Pi Original Development] Eddy25:
Hi. I'm using a Raspberry Pi4 4GB Have followed your tutorial for Android 13 and eveything is working without issues. Now I want to install Netflix with the ability to watch videos in Full HD.

In tne playstore i haven't found it. What are the steps to have it installed (Sorry i'm not an expert). Thanks in advance.
[Raspberry Pi Original Development] KonstaT:
Please keep your posts at the appropriate topic. Replied over at https://xdaforums.com/t/dev-rom-uno...aspberry-pi-4-b.4516545/page-18#post-89366371

On Android 14 releases, you would also need to install the separate Widevine add-on.
[Raspberry Pi Original Development] KonstaT:
New build. Android 14 QPR2. Linux 6.6 kernel add-on.

AOSP (Android 14)

for Raspberry Pi 4

konstakang.com

update to latest AOSP release (Android 14 QPR2 - android-14.0.0_r34)

move serial console to the UART connector

switch external camera HAL to AIDL (improves boot time)

sensor HAL fixes (thanks to Kethen)

update to libcamera master/v0.2.0, libpisp v1.0.5

update to FFmpeg 6.0.2, AOSP dav1d 1.4.1

update to alsa-lib/alsa-utils v1.2.11

update to Mesa 24.0.6

update to Linux 6.1.80 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)

Android security patch level: 5 May 2024

Linux 6.6 kernel: (optional add-on)

new Raspberry Pi Android kernel bring-up based on AOSP android15-6.6

update to Linux 6.6.29 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
[Raspberry Pi Original Development] lee99:
I wonder. It is possible hw AV1 on pi4/5?
[Raspberry Pi Original Development] KonstaT:
No, there's no AV1 hardware decoder on Raspberry Pi.

Pi 4 has:

-H.265 hardware decoder rated at 4k@60

-H.264 hardware decoder rated at 1080p@60

-H.264 hardware encoder rated at 1080p@30

Pi 5 has:

-H.265 hardware decoder rated at 4k@60

Everything else (AV1/VP8/VP9/etc) uses software decoding/encoding. My builds have implemented libdav1d for AV1 decoding for quite some time.

libdav1d software decoder performs quite well and Google is opting to use it instead of their previous implementation in future Android versions.

Upcoming Android update will give AV1 videos a big boost on budget devices

Android currently ships with the libgav1 AV1 decoder, but a future update will switch that to libdav1d, which offers much better performance.

www.androidauthority.com
[Raspberry Pi Original Development] KonstaT:
New build.

AOSP (Android 14)

for Raspberry Pi 4

konstakang.com

update to latest AOSP release (Android 14 QPR3 - android-14.0.0_r52)

update to libcamera master/v0.3.0, libpisp v1.0.6

update to FFmpeg 7.0.1, AOSP dav1d 1.4.2

update to alsa-lib/alsa-utils v1.2.12

update to Mesa 24.1.3

update to Linux 6.1.90 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)

Android security patch level: 5 July 2024

Linux 6.6 kernel: (optional add-on)

update to Linux 6.6.36 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
[Raspberry Pi Original Development] Vladimir_f:
Hello Konsta, will the "30gpioshutdown" script work on AOSP (Android 14)? What if I put it in "/vendor/etc/init.d/" and make it executable? Or does it need to be edited? And another question, is it possible to use GPIO13 for this script if I only need to turn it off? Thank you in advance.
[OnePlus 6 Questions & Answers] aviseknandi:
My Op 6 first went to Qualcomm Crashdump mode. I tried to get it fixed by a local shop.

But he couldn't do anything but now I see that the phone is powering on to fasboot mode.

The device bootloader is locked with the latest Oxygen OS.

I tried the "All In One" tool and detected the device in Fastboot mode.

But when I try to switch to the system the phone just turns the screen black. Then it doesn't detect the phone anymore in the software but the device manager shows Qualcomm HS-USB QDLoader 9008(COM3).

I have to manually switch to FastBoot using the volume - and power buttons.

Even trying to reboot to Fastboot when I am in Fastboot with the software causes the same issue.

There are some very important data in my phone.

That is why I am trying to start the phone without flashing any files which will erase the data.

Please help me boot the phone without losing the data. 🙏
[OnePlus 6 Questions & Answers] Sepero:
If you want to keep your data, then I believe your only option here is to switch the boot slot. This can be done with the ADB command:

fastboot set_active b

Or: fastboot set_active a

Try both.

To find out which slot your device is currently on, you can use: fastboot getvar current-slot

There are instructions all over the internet for how to install ADB on a computer to run those commands, so I leave that as your responsibility to find. If that doesn't work, then I think you can kiss your data goodbye. My recommendation for the future, never trust your security to corporations, and always unlock your bootloader.
[OnePlus 6 Questions & Answers] aviseknandi:
Hey, Thanks for replying.

I have ADB setup and even MSM tool setup.

The command you said doesn't work for locked devices.

I have given up trying to recover data.

Now I am just trying to boot the device so I can exchange the device.

I am only able to access Fastboot mode but not recovery.

I tried Flashing the MSM tool v5.1.5 and v10.3.8.

The flashing starts normally but after the flashing gets completed, it doesn't stop but starts again.

It same with both the ver.

Please help me.
[Google Pixel 8] Gibsonflyingv:
I'm a pixel 6 owner and the fingerprint sensor has been a thorn in my side since day one. I'd love to hear your experience with the P8!
[Google Pixel 8] bobby janow:
From early reports .. flawless. The P7 I now have is darn near that too. You should be good to go. I also had problems with the P6 IIRC.
[Google Pixel 8] Gibsonflyingv:
It's (the p6) awful, especially if your finger is really dry!
[Google Pixel 8] LeoD:
It is still to early to say exactly but so far it seems very good. I just received the phone today but did notice I was able to register the thumb on my right hand which I was never able to do on the P6 or the P7. That is not entirely the phones fault as in many injuries over the years working probably messing my my imprints.