yashsingh1/xdaforums huggingface dataset:
[Raspberry Pi Original Development] KonstaT:
You don't, taskbar is part of Android 12L/13 tablet UI. LineageOS 19 build has custom option to use navigation bar instead of taskbar but this is not part of AOSP.

There's some issues due to how wifi region is managed on Android. You can e.g. 'iw reg set US' in rooted shell after which you should see 5 GHz networks. Wifi country code is 00 (DFS-UNSET) by default until you connect to a network. Then it changes to the region your AP uses. Changing region on your router's settings might also make some difference.
[Raspberry Pi Original Development] KonstaT:
I have recently started new open source project for Android on Raspberry Pi. Raspberry Vanilla AOSP.

Raspberry Vanilla

AOSP for Raspberry Pi. Raspberry Vanilla has 32 repositories available. Follow their code on GitHub.

github.com

Goal of the project is to provide fairly minimal Android device configuration that supports all the built-in hardware on Raspberry Pi and provide stable ground for any further development. My personal builds (such as this one) still offer various features/enhancements over that.
[Raspberry Pi Original Development] azraelcelt:
does this build allow one to use a argon one case, mainly just want the power button and fan to run ?
[Raspberry Pi Original Development] KonstaT:
Same answer about the fan I already gave you on the LineageOS 19 topic (https://xdaforums.com/t/dev-rom-uno...aspberry-pi-4-b.4356891/page-23#post-87638591). Power button is likely just a matter of changing one line in /boot/config.txt (see under 'Keys' section) to the GPIO pin the case uses.

I don't have the hardware myself so this is something you need to figure out yourself.
[Raspberry Pi Original Development] azraelcelt:
oh ok I dont recall asking this about the lineage OS 19 as I couldnt seem to sort the BT out, pretty much have AOSP 13 running decently (besides getting hot fairly fast) in the argon one case booting off a kingston 120GB SSD, pretty sure the power button was easy, just curious when you say you don't have the hardware yourself do you mean the Pi 4 and/or the Argon ONE M.2 Case ?

Dismantled my Pi & Case to take pictures incase its able to help another to come to a solution,

setting up my Pi with a raspberian OS was fun and interesting ( no one else in the house will try a new OS unfortunetly ), same with android on a android device, trying to run android on a Pi without android apps that allow one the means of getting certain Pi functions has been quite a pain tbh unless I change to a more stock Pi case with a beefy af cooling,

any case suggestions would be appreciated especially if it can contain a m.2 drive
[Raspberry Pi Original Development] KonstaT:
Of course I have a Pi 4 since developing something like this would be impossible otherwise. I don't have any Argon case so that's the part you need to figure out yourself.

As also already discussed in the LineageOS 19 topic (https://xdaforums.com/t/dev-rom-uno...aspberry-pi-4-b.4356891/page-23#post-87638591) yes, you can boot from the M.2 SSD just like from any other USB device (since the case uses USB adapter for this).
[Raspberry Pi Original Development] dorkshoei:
@KonstaT

Really impressive. Thank you!

My use case is for a desk side PDF reader. I'm using this uPerfect 15" display.

I'm having two problems, one self-inflicted.

1: If the screensaver turns on, the touchscreen won't wake the unit. I need to use a mouse.

The touchscreen works perfectly (it uses a usb connection from uPerfect display to Pi USB3 port) without needing to enable "Enable configuration for official Raspberry Pi 7" touchscreen". Enabling this option doesn't solve the waking issue.

2: Somehow I managed to change something in the config and the screen is partially mirrored.

The top bar is "[battery icon] [wifi icon] ............ [clock]" and the bottom navigation bar is "[square] [circle] [forward arrow]". If I go into settings, the list of sections are now at the right side and the entries for each section on the left. I can't figure out what option I changed.
[Raspberry Pi Original Development] KonstaT:
1. There's been similar reports with Android 12 as well. This still worked with Android 11 but I suppose something changed how (external) touchscreens are managed in Android after that. I haven't gotten around to track down exactly what. I've suggested trying adding IDC file for the input device as documentation says 'device.internal' property "determines default policy decisions regarding wake events" (https://source.android.com/docs/cor...put-device-configuration-files#deviceinternal). External input devices should wake the device by default in any case so not sure what's up.

2. No idea TBH. Some right-to-left language option? https://m2.material.io/design/usability/bidirectionality.html#mirroring-layout
[Raspberry Pi Original Development] dorkshoei:
RTL clued me in. Developer Options; Force RTL Layout direction.

If you have a chance to figure out the screen wake that would be great, until then I'll reenable Developer Options; Stay Awake

Thank you!
[Raspberry Pi Original Development] KonstaT:
And you though the right approach would be to spam this is in six different places instead of just reading the FAQ first?

https://xdaforums.com/t/dev-rom-uno...3-for-raspberry-pi-4-b.4516545/#post-87726473

https://xdaforums.com/t/dev-rom-aosp-android-13-for-raspberry-pi-4-b.4481977/page-2#post-87726267

Rpi doesn’t boot. Creates grey flashing screen. Already tried changing edid. · Issue #9 · lineage-rpi/android_device_brcm_rpi4

Creates grey flashing screen. Already tried changing edid. How do I get it to boot to lineage os. Rpi 4b 8gb ram. Latest lineage os.

github.com

+ two comments on my site that I've now deleted as spam & a private message!

If you have issues with your display, please read the FAQ.

If you want to boot from an USB device, please read the FAQ.
[Raspberry Pi Original Development] KonstaT:
And in one of these six messages you also mentioned that you're trying to boot from an USB device.

It's a requirement that you use a HDMI display that reports resolutions it supports via EDID. Try with another display/HDMI cable/micro-HDMI to HDMI adapter or come back with appropriate logs because it's impossible to know otherwise.
[Raspberry Pi Original Development] KonstaT:
Please stop spamming. You can edit your posts if you have something to add. I probably don't have anything more to add to this discussion at this point.

You can get logs using serial console or ADB over USB-C. Changing displays is not going to make any difference either if your issue is with USB boot.
[Raspberry Pi Original Development] Augustin.Nodle:
when i start rpi4 the screen remain back and my lights from pyi4 turn off , i don't know what have
[Raspberry Pi Original Development] KonstaT:
Why make the same post in several places?

https://xdaforums.com/t/dev-rom-uno...aspberry-pi-4-b.4356891/page-23#post-87633437
[Raspberry Pi Original Development] dorkshoei:
@KonstaT a bit off-topic.

None of my PC ports will provide sufficient power for the rPi4 which makes using adb over USB hard. Right now I'm using adb over wireless; ok but a bit harder to setup. I suspect a powered USB hub can do it but other than this task I have no need for one. Any other inexpensive methods?
[Raspberry Pi Original Development] KonstaT:
5V on the GPIO (e.g. if you already have a some display with power input that can output to GPIO, PoE adapter, etc). Or USB Y-cable. You can even make one yourself by cutting/connecting data and power lines on two existing cables. IMO it's pretty easy use the older TCP-based ADB over network that is still supported on my builds (under Raspberry Pi settings, not the one in Developer options).

Depending on what you want do in the shell, serial console adapter is also a good option.
[Raspberry Pi Original Development] KonstaT:
https://twitter.com/i/web/status/1609137384448204800
[Raspberry Pi Original Development] 0xsharkboy:
Hey, I flashed it and my sd card is now write protected. How to fix this ?
[Raspberry Pi Original Development] KonstaT:
New build. Added optional Linux 6.1 kernel add-on for testing purposes.

AOSP (Android 13)

for Raspberry Pi 4

konstakang.com

update to latest AOSP release (Android 13 QPR1 - android-13.0.0_r24)

enable multi-gen LRU

update to TWRP 3.7.0_11-0-KonstaKANG

update to Mesa 22.3.2

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

Android security patch level: 5 January 2023

Linux 6.1 kernel: (optional add-on)

new Raspberry Pi Android kernel bring-up based on AOSP android14-6.1

update to Linux 6.1.1 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
[Raspberry Pi Original Development] twangmods:
Hi @KonstaT, I'm using your vanilla aosp build. I want to connect a HUAWEI modem via USB and need to dial it with AT Command. the modem looks detected when queried with 'lsusb' but not listed as ttyUSB2 in /dev. As comparison when I plug the modem into my UBUNTU 20.04 laptop it successfully detected with 'lsusb' and Also listed as ttyUSB0/1/2 in /dev. my question is is this happen due to the kernel linux vs android, I checked both this android and ubuntu using the same kernel version 5.15.

Thank You

here is some pics

rpi vanilla aosp

ubuntu machine
[Raspberry Pi Original Development] KonstaT:
What is exactly the end goal you want to acheive with this hardware?

Cellular data on some 3G/LTE USB dongles have been reported working using third party apps (e.g. https://play.google.com/store/apps/details?id=de.draisberghof.pppwidget3).

'dmesg' output plugging in the USB on Ubuntu (or whatever Linux distribution you have this working) would better indicate what drivers it uses. Linux kernel on my Android builds doesn't have drivers enabled for every possible external piece of hardware you throw at it. According to https://linux-hardware.org/index.php?id=usb:12d1-1506 you'd at least need to compile the kernel (https://github.com/raspberry-vanilla/android_kernel_manifest/tree/android-13.0) with USB_SERIAL_OPTION (https://github.com/raspberry-vanill.../arm64/configs/lineageos_rpi4_defconfig#L4665) enabled. USB_SERIAL_WWAN and USB_NET_HUAWEI_CDC_NCM also something to look into?
[Raspberry Pi Original Development] fly_eye:
Hi @KonstaT, I'm struggling to understand why when I rebuild the kernel following this https://github.com/raspberry-vanilla/android_kernel_manifest/tree/android-13.0

I can boot from SDCard but not when I move the same kernel Image to a working (after a working fresh install on the USB disk) USB device. I have the same issue on your lineage 19, 20 and AOSP 12, I guess I'm missing a basic step/configuration.

SD Card process (AOSP 12, compiling now on AOSP 13 and I did the same on lineage 19):

- Fresh install: working

- Kernel build with no config changes then I copy only Image into the boot partition: working

- Update kernel config to add some needed drivers then I copy only Image into the boot partition: working

- Update kernel config for heavy optimization then I copy only Image into the boot partition: working

USB Disk process (AOSP 12, compiling now on AOSP 13 and I did the same on lineage 19):

- Fresh install: working and it's super quick

- Kernel build with no config changes then I copy only Image into the boot partition: boot loop with the console message: android partition(s) not found after polling timeout: sda1, sda2, sda3

what am I missing ?
[Raspberry Pi Original Development] KonstaT:
I can't see any reason why that wouldn't work.

As stated in the FAQ there's a config.txt change to boot from the USB. Or you've messed something with the relevant overlays (android-sdcard.dtbo/android-usb.dtbo)?
[Raspberry Pi Original Development] fly_eye:
Me too. The only thing I see it's the boot command in the kernel config

BUILD_CONFIG=common/build.config.rpi4.defconfig SKIP_MRPROPER=1 build/config.sh

Boot options->CONFIG_CMDLINE containing "root=/dev/mmcblk0p2"

I'm pretty sure it's not this because it can read the kernel so the disk is available but there's clearly something I don't see. I'm tryng to re-compile the kernel with root=/dev/ram0 and/or root=/dev/sda2

@KonstaT would be possible to enable in the future build kernels:

- CONFIG_CAN + CONFIG_CAN_GS_USB: it's a canbus USB dongle really useful when using lineageOS as car head unit, the simplest to be found

- CONFIG_GNSS + CONFIG_GNSS_UBX_SERIAL: gps USB dongle, the driver it's compatible with the cheap Chinese versions too.

- CONFIG_JOYSTICK_MAGELLAN: there's no a general reason to do that but I'm using this as remote mouse and the current workaround is a custom low level serial reader I wrote but a kernel included version would be great

This modules has been successfully tested on lineage 19 and AOSP 12, perfectly working out of the box.
[Raspberry Pi Original Development] twangmods:
Thanks for pointing me to https://linux-hardware.org/?view=search, I've successfully compiled the the kernel. enabled these:

CONFIG_USB_SERIAL_OPTION=y

.

CONFIG_USB_NET_QMI_WWAN=y

.

CONFIG_USB_NET_HUAWEI_CDC_NCM=y

couldn't find USB_SERIAL_WWAN though

My goal is able to dial this modem with AT via USB connection (from Kotlin app or QT)

now my kernel version is 5.10.157-xxxxx-dirty

still not detected as ttyUSBx

based on this https://linux-hardware.org/?id=usb:12d1-15ca, it's a Mass storage device

same result with dmesg

[ 5295.579273] usb 1-1.2: new high-speed USB device number 9 using xhci_hcd

[ 5295.684737] usb 1-1.2: New USB device found, idVendor=12d1, idProduct=15ca, bcdDevice= 1.02

[ 5295.693348] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[ 5295.700801] usb 1-1.2: Product: HUAWEI Mobile

[ 5295.705246] usb 1-1.2: Manufacturer: HUAWEI

[ 5295.709519] usb 1-1.2: SerialNumber: FFFFFFFFFFFFFFFF

[ 5295.720820] usb-storage 1-1.2:1.0: USB Mass Storage device detected

[ 5295.728170] scsi host0: usb-storage 1-1.2:1.0

[ 5296.736343] scsi 0:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2

[ 5296.748214] scsi 0:0:0:1: Direct-Access HUAWEI TF CARD Storage 2.31 PQ: 0 ANSI: 2

I wonder if any config needed to make this modem accessible via USB.
[Raspberry Pi Original Development] KonstaT:
There really isn't anything on the kernel related to sdcard/usb boot than https://github.com/raspberry-vanill...mmit/6f89bbc83992a089fb985cb33e8bd0e73c0135fe and the line in config.txt to enable one of the two overlays. The kernel cmdline config doesn't make any difference here.

I'd like to keep drivers disabled that have no specific use in Android. E.g. there's nothing on Android to support any CAN hardware (only automotive builds have CAN HAL and I'm not providing any Android automotive builds). Same for the GPS. If the Android GPS HAL included in my builds doesn't work with devices that use that kernel driver, there's not much point in having it enabled.

IIRC USB_SERIAL_WWAN should come available after enabling USB_SERIAL_OPTION (https://github.com/raspberry-vanill...oid-13.0/drivers/usb/serial/Kconfig#L542-L562). Check regenerated defconfig.

If the device is in the wrong mode, you probably need to look into using usb_modeswitch. It's not included in Android but you can probably find some binary somewhere (or build it yourself).
[Raspberry Pi Original Development] Robbel2005:
Thanks for your work! I installed it on my PI4 with the gapps because I wanted to test the tv apps.

Found out it's important to flash at once the image and the gapps in one row followed by factory reset in twrp.

First time I prepaired the sd card and after first normal boot, I booted in twrp and flashed gapps but playstore couldn't connect to internet that way.

So I booted again to twrp and flashed the ota followed by the gapps and factory reset, and this was succesfull.

My second problem was during videos purple colours and stuttering, tried all the resolutions from the settings without getting it right. So I deleted on the boot partition /boot/resolution.txt and this solved my problem, now fluent videos play. I noticed it was now in 1920 X 1080@60 and changed that in the resolution txt and this also works.

I added to my gpio 21 and ground a power button like described and this also works. Now I have to search where my old infrared receiver and remote control is stored that I used with windows mediacenter, to add this.
[Raspberry Pi Original Development] fly_eye:
@KonstaT finally I found the issue, I didn't copy the out/dist/bcm2711-rpi-* files. Uploading Image and these files solved the issue. New kernel is booting in ~35sec on Lineage 20 and ~30sec on AOSP 13 . Now I can play a little bit
[Raspberry Pi Original Development] KonstaT:
New build. H.265 hardware video decoding, H.264 hardware video decoding and encoding!

AOSP (Android 13)

for Raspberry Pi 4

konstakang.com

H.265 hardware video decoding, H.264 hardware video decoding and encoding

FFmpeg 5.1.2 (thanks to John Cox for Raspberry Pi hw codecs support and Android-x86 for AOSP build patches)

implement codec2 plugin to integrate FFmpeg into Android multimedia framework (thanks to Michael Goffioul)

FFmpeg hevc_v4l2request hwaccel H.265 hw decoding (default), h264_v4l2m2m H.264 hw decoding (optional)

v4l2_codec2 H.264 hardware video decoding and encoding (default)

FFmpeg software decoders support

update to Mesa 22.3.4

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

Linux 6.1 kernel: (optional add-on)

forward port ion memory allocator

update to Linux 6.1.8 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
[Raspberry Pi Original Development] KonstaT:
Some good sources for test clips to try H.264/H.265/VP8/VP9 hardware/software video decoding.

MP4 ( H.264 ) | Test Videos

Download test videos and sample videos for any purpose. Completely free videos of different formats, file types and sizes.

test-videos.co.uk

MP4 ( H.265 ) | Test Videos

Download test videos and sample videos for any purpose. Completely free videos of different formats, file types and sizes.

test-videos.co.uk

WEBM ( VP8 ) | Test Videos

Download test videos and sample videos for any purpose. Completely free videos of different formats, file types and sizes.

test-videos.co.uk

WEBM ( VP9 ) | Test Videos

Download test videos and sample videos for any purpose. Completely free videos of different formats, file types and sizes.

test-videos.co.uk

AOSP doesn't seem to support .mkv file extension (but still supports matroska container) so rename to .mp4 first. HEVC 10-bit i.e. 'H.265 Main 10 Profile' doesn't seem to play currently. Edit. Main 10 Profile fixed so also this will be working if/when there's new releases.

Jellyfish Bitrate Test Files

A collection of .mkv video clips encoded at various bitrates; useful for testing the network streaming and playback performance of media streamers & HTPCs.

www.larmoire.info
[Raspberry Pi Original Development] duckdown:
Is there any Raspberry Pi 400 owners out there who have encountered the HDMI audio problem where the sound stops working system wide ? It seems to be affecting me really bad. I didn't think the system was over heating or super maxed out, this can happen just by navigation

If there's any logs needed I can certainly try to provide them, just let me know how

Secondly. Assuming this is no easy fix, what is the next best way to provide audio to a modern Sony TV ? How do you use the 3.5mm output that supposedly is not affected on a TV set?

Thanks very much!

Edit - guess I didn't look before posting. No audio jack on Pi 400

I have set this SD card aside and am going to go back to Raspberry Pi OS for now. I absolutely love the idea of running Android on it and will be the first one back as soon as the issue is resolved. But I'd mark this as not working on Raspberry Pi 400 as I'd consider HDMI audio to be mandatory functionality

I will anxiously be watching for a fix
[Raspberry Pi Original Development] KonstaT:
You're welcome to fix this anytime. :)

Raspberry Vanilla

AOSP for Raspberry Pi. Raspberry Vanilla has 32 repositories available. Follow their code on GitHub.

github.com

There's been one similar report on Sony Bravia TV (https://konstakang.com/devices/rpi4/LineageOS19-ATV/#comment-6080895434) so try with a different TV/display. I don't have any hardware I could use to reproduce such issue, whatever that may be, and you haven't provided any useful information (logcat, dmesg) to even figure that part out.
[Raspberry Pi Original Development] duckdown:
I am a novice user, my apologies since you seem offended in some way!

I do not think it's related to Sony Bravia, I'm back on Raspberry Pi OS and it's working perfectly, I can't imagine Sony Bravia being the root cause of anything but I am happy to confirm the issue on another TV. I am quite positive it would happen regardless of device!

Regarding the logs, I already mentioned I would be happy to provide them. I don't know how!

I sincerely appreciate your work and your assistance, my apologies if it seemed like anything otherwise. Once your build has working audio as good as Raspberry Pi OS, I would never use anything else again. I definitely want this fixed. The difference in sound is instantly evident, though. Even just from clicking around - there's not a single "lost click" in movement anywhere, I never noticed how severe it was in the Android build until going back to Raspberry Pi OS and hearing the difference
[Raspberry Pi Original Development] KonstaT:
I wasn't offended. :)

As it was explained to you elsewhere, the way HDMI audio is implemented on builds with Linux kernel >=5.10 (i.e. Android 12 and above) is because Pi Foundation chose to use IEC958 format for HDMI audio which is not supported on Android. Raspberry Pi is not an Android device to begin with and Android is not your regular Linux distribution. This discussion would also be easier for everyone else to follow if you hadn't spread it to several different topics on several different forums (my site, here at XDA, and Raspberry Pi forum). You don't get any more attention by doing that, it's actually the total opposite. So for future reference, make one single structured post where you properly describe the issue you're having and attach appropriate logs that might help to figure out the cause of the issue.

You can capture logs by e.g. typing in 'logcat' and 'dmesg' in shell (ADB/SSH/serial console/some third party terminal app/etc).
[Raspberry Pi Original Development] leonardopires:
Hi Konsta. I installed the latest aosp version for rpi4. install nikgapps and everything is ok.

i have a xbox cloud account and installed the Game Pass App from google play store.

My problem is xbox original controller is not sync with bluetooth ...

When i try to pair a new device, the xbox controller appears on android screen, i click to sync but something happens that the android refreshs the screen and nothing happens...
[Raspberry Pi Original Development] KonstaT:
logcat?

I don't have any hardware to test. Android 13 switched to new gabeldorsche bluetooth stack and there's reports of some other bluetooth issues as well. You could also try if this is any different on Android 12 builds.
[Raspberry Pi Original Development] leonardopires:
@KonstaT , i attached a logcat debug.

While the logcat was enabled on adb, i tried to sync the Xbox S Controller (Bluetooth)
[Raspberry Pi Original Development] leonardopires:
The next step is try android 12....
[Raspberry Pi Original Development] leonardopires:
@KonstaT , the Xbox S Controller is pairing with android aosp 12L....
[Raspberry Pi Original Development] KonstaT:
This looks similar to what I've seen before. Will see if I have some bluetooth device I can reproduce this with.

Yes, like said, most likely something related to the new bluetooth stack introduced in Android 13.
[Raspberry Pi Original Development] danielbryan:
Hi @KonstaT

I installed AOSP13-20230130-KonstaKANG-rpi4.zip

How do I get remote access VNC Mac? What is the default password?

ADB and SSH worked easily.

Thank you!!
[Raspberry Pi Original Development] danielbryan:
Its worked in VNC Viewer App. No password. Disable encryption.
[Raspberry Pi Original Development] adioph:
I would like to thank for this great project. I got my rpi4 yesterday, installed AOSP 13, but bluetooth gamepad wont connect, any fix for this? thanks