yashsingh1/xdaforums huggingface dataset:
[Raspberry Pi Original Development] KonstaT:
12L is still in beta and Google hasn't pushed source code to AOSP (due in Q1 https://developer.android.com/about/versions/12/12L/overview#timeline).

Latest builds already have full Treble & VNDK support (there's Treble test apps available). I haven't tested but it should be already be possible to run GSI's (if you can find A-only GSI and somehow flash it without fastboot).

Android builds are (and most likely always will be) entirely device/hardware specific. GSI's are intended as a developer tool - not something for general public. Here's a recent article from former XDA chief editor. https://blog.esper.io/android-dessert-bites-6-project-treble-retrospective-3195734/
[Raspberry Pi Original Development] 28akshit:
i have tried adding (dtoverlay=iqaudio-dacplus) in config.txt but my iqaudio DAC pro sound card is not working with it when i go to settings a list of hifiberry sound card comes when i select DAC i am using android 12 with rpi4 8gb ram
[Raspberry Pi Original Development] KonstaT:
Spamming this same thing across various different forums and topics doesn't help.

Already discussed on the Pi forum. https://forums.raspberrypi.com/viewtopic.php?t=323020&start=25#p1976711
[Raspberry Pi Original Development] risant:
Is there a patch for usb external dac to work on android 12?
[Raspberry Pi Original Development] NonStickAtom785:
No? Not one that anyone has made I don't think. I'll do a bit of research and update my post accordingly in a bit.

Here's a Magisk article

And here's KonstaT's answer to someone else in the past.

Edit the build prop

Also thanks for this. I just remember breaking my new Arch Linux build trying to compile Pitch Black Recovery Project which supports GSI's. And on that note I thought Google already released a 12L binary. It was a GSI for the pixel devices hey... It might still work on a Pi with the right modification.

Also I was just messing around with Termux and Tasker today, and I happened to stumble upon `android-tools` for Termux. It supports adb and fastboot commands directly from Termux apparently. Although I couldn't test the Fastboot commands with my non-rooted Motorola I think this is worth investigating.
[Raspberry Pi Original Development] risant:
Is it possible to connect two monitor thru micro hdmi .?. but use it one at a time with lineage os
[Raspberry Pi Original Development] KonstaT:
It's not. There's no Android bootloader in my builds so you can't do anything with fastboot.

Yes, latest build has initial support for dual-HDMI displays. Please read the changelog.
[Raspberry Pi Original Development] daniel302021:
Anyone know if Snapchat works on this?

Trying to find a solution to run Snapchat with an actual keyboard... Android x86 won't let you sign in or register. Would prefer not to use Windows at all. Was thinking of running ESXi ARM on my Raspberry Pi and then installing this as a VM, that way I could access it remotely.

Will test myself, but I'm waiting on some flash drives... and thanks to COVID, Walmart closes at 11pm.
[Raspberry Pi Original Development] rabbited:
As it turns out, with a minor fstab change I am able to boot into Lineage over nvme0n1p* and haven't run into any issues yet with that. I'm compiling the kernel for 18.1 to test it on that now, as that system is more stable. I will report back if there are any bugs.
[Raspberry Pi Original Development] KonstaT:
I've pushed the latest LineageOS 19.0 release (20220211) through OTA. If you're still on 20220114 release you can download the update from Settings -> System -> Updater (or if you're already on the latest build and want to test you can 'setprop lineage.updater.allow_downgrading true' in shell first). After downloading the update you need to manually boot to TWRP and install the update from /data/lineageos_updates/.
[Raspberry Pi Original Development] scottial:
What about "Ok Google" hotword? How make it working?
[Raspberry Pi Original Development] KonstaT:
With recent Android versions (Android 11+) you need to have specific proprieatry drivers for hotword enrollment. These are device/platform specific so it's not going to happen on the Pi (as it's not an Android device to begin with and it has never passed certification for Google services). Some reference for the blobs e.g. https://github.com/LineageOS/androi...ob/lineage-18.1/proprietary-files.txt#L37-L41 & https://github.com/LineageOS/androi.../lineage-18.1/proprietary-files.txt#L655-L659.

With older Android versions hotword detection should work after installing larger gapps package (OpenGApps nano or bigger).
[Raspberry Pi Original Development] NonStickAtom785:
@KonstaT Why can't the resize script be added to a "firstrun" file on first boot? It would remove the need of several reboots and unexperienced users not understanding why the device is not being fully utilized.

Android 12L source code was resalesed March 5th "SP2A.220305.012" but Google is announcing it as Android 12.1

I've got more to say but I'll just edit it in, in a min.
[Raspberry Pi Original Development] KonstaT:
Data partition can't be mounted when resizing the partition & file system. From technical perspective it's not so simple to interfere the Android boot process to resize the partition. While on the other hand it's very straight forward to do it in recovery mode.

I think it's still called Android 12L but the source release is tagged as android-12.1.0_r*. Looks like there will be LineageOS 19.1 eventually.
[Raspberry Pi Original Development] KonstaT:
Hmm, not entirely sure how I feel about this.

https://twitter.com/i/web/status/1503070780757880838
[Raspberry Pi Original Development] NonStickAtom785:
Mixed emotions about this XD

However theming is just one thing that isn't that great on Lineage. In my opinion. Also Prime OS was just released on the raspberry pi as well.
[Raspberry Pi Original Development] KonstaT:
New build. This is very early Android 12L / LineageOS 19.1 release.

LineageOS 19 (Android 12L)

for Raspberry Pi 4

konstakang.com

-Android 12L / LineageOS 19.1

-update to TWRP 3.6.0_11-2-KonstaKANG

-update to Mesa 22.0.0

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

-Android security patch level: 5 March 2022 (merged)
[Raspberry Pi Original Development] myweb:
Hello,

I would like to report an issue with Bluetooth Keyboard (tried two models of logitech). Right after entering pairing code Bluetooth gets turned off/on and final connection is not established.

Is it correct that multi-display support is supported in LineageOS 19.1 only? Just mirroring screen to both HDMIs of Raspberry PIs?
[Raspberry Pi Original Development] KonstaT:
Logcat on the bluetooth pairing issue? Impossible to say otherwise. Have you installed gapps? There's been some reports of pairing issues with some remotes/keyboards after installing gapps.

Please read the changelog. Support for dual-HDMI displays was added in LineageOS 19.0 20220211 build. It mirrors the displays by default but you can enable desktop mode for the secondary display from developer options. As commented then

Freeform windows seem to be completely broken on Android 12L / LineageOS 19.1 (resizing/moving windows doesn't work) so if you want to try the desktop mode you probably want to do it on the 20220211 build.
[Raspberry Pi Original Development] NonStickAtom785:
If you have a logitech unifying receiver try pairing the keyboard to it. Otherwise I tried pairing my logitech mouse straight to the hardware and got some issues as well. I had to connect reconnect it to my receiver.

As far as hardware decoding goes how can the community help in getting support for it. The sooner we get full support the better the raspberry pi will get. :D
[Raspberry Pi Original Development] hugoBOSS1981:
Hey KonstaT, I love your build. I was wondering if you could tell me how or point me in the direction so that I could take a swing at making an unofficial iso for Lineage os 19.1 for android x86. I know there are other existing x86 os's like Bliss, Phoenix, etc but I haven't found anything official or otherwise under Lineage os beyond 14.1.Don't get me wrong, Android 7.1.1 works fine on the devices I have it on,but bumping it up to android 11/12 would be so sweet with Lineage. It just runs so smooth. I greatly appreciate all the help you can give me on this.
[Raspberry Pi Original Development] myweb:
I have no gapps installed.

Please find the logs attached: full cycle from boot to failed pairing.
[Raspberry Pi Original Development] pi_saab:
Hello

also has problems connecting to bluetooth but it pairs the phone then disconnects it

is it possible to connect a usb bluetooth adapter like asus usb-bt400?
[Raspberry Pi Original Development] KonstaT:
Question would be better aimed to someone who is more familiar with Android-x86/Bliss OS.

Generally speaking if you have AOSP device configuration for a device it's pretty trivial to compile any AOSP-based ROM for that device. Projects like Android-x86 require quite a few forked projects/several patches over Android sources in addition to your traditional device specific sources (device-, kernel- & vendor trees). You would need to track down those changes from the existing sources and rebase them on LineageOS sources. Sorry, I don't have any guide/documentation I could link because there isn't any. Available source code is the only reference.
[Raspberry Pi Original Development] KonstaT:
Thanks. Bluetooth certainly crashes but need to look into further why. Have you tried this on older builds (LineageOS 19.0 & 18.1)?

Logcat? Tested pairing my phones and it works fine for me.

There's no support for any external USB bluetooth dongles.
[Raspberry Pi Original Development] myweb:
LineageOS 18.1 works fine with the Bluetooth keyboard.

LineageOS 19.0 also has the issue with Bluetooth keyboard.
[Raspberry Pi Original Development] KonstaT:
Interesting, thanks. There's no difference in device specific bluetooth implementation between my LineageOS 18 & 19 builds so something else.
[Raspberry Pi Original Development] Fodor Gábor:
Hi.

I can not installing gapps. Installation failed error 1 massage in TRWP

Thans for reply.
[Raspberry Pi Original Development] KonstaT:
Most likely you've chosen wrong gapps package (which one was it?).

Please read the FAQ on how to install gapps.
[Raspberry Pi Original Development] Fodor Gábor:
I have bitgaps arm64 12 r45 signed zip
[Raspberry Pi Original Development] KonstaT:
You would need to ask where you got the gapps if it's supposed to be compatible with Android 12L. I've tested BitGapps on older Android 12 / LineageOS 19.0 builds, only tested another gapps release on Android 12L / LineageOS 19.1.

I don't have anything to do with any gapps release. They are just linked here for your convenience.
[Raspberry Pi Original Development] aaron.guajardo:
Hello KonstaT,

Your work is impressive! I was wondering if you could help me, I am using a rfid sensor that works with i2c but I gave up on using the sensor in this mode (i2c) since I haven't found libraries that use sysfs calls directly, so I've change the sensor to work with serial transfer.

I've added dtovverlay=uart2 to the file config.txt to enable this serial port to use this sensor and in my program, I've made a c++ file (in android studio) to work directly with /dev/ttyAMA1 but I got two problems:

The first one is that the program itself can't open the device if I don't do chmod 666 /dev/ttyAMA1 directly in a ssh connection, second (when I do the chmod), I got these messages in the logs afterwards:

avc: denied { read write } for name="ttyAMA1" dev="tmpfs" ino=318 scontext=u:r:untrusted_app:s0:c98,c256,c512,c768 tcontext=u:object_r:device:s0 tclass=chr_file permissive=1 app=...
avc: denied { open } for path="/dev/ttyAMA1" dev="tmpfs" ino=318 scontext=u:r:untrusted_app:s0:c98,c256,c512,c768 tcontext=u:object_r:device:s0 tclass=chr_file permissive=1 app=...
avc: denied { ioctl } for path="/dev/ttyAMA1" dev="tmpfs" ino=318 ioctlcmd=0x5401 scontext=u:r:untrusted_app:s0:c98,c256,c512,c768 tcontext=u:object_r:device:s0 tclass=chr_file permissive=1 app=...

Can you please help me? Do you need more information? Thanks!
[Raspberry Pi Original Development] KonstaT:
You can set permission for /dev/ttyAMA1 node in /vendor/etc/ueventd.rc. You need to mount the vendor partition writable to make any changes ('mount -o rw,remount /vendor' in rooted shell).

SELinux is in permissive mode so it just logs any denials. It doesn't prevent anything from working so you can just ignore that.
[Raspberry Pi Original Development] Fodor Gábor:
Thank you.I wil try to search.
[Raspberry Pi Original Development] hugoBOSS1981:
HeyKonstaT,

Thanks for that tid-bit of info. It definitely clarified some things. I appreciate you taking the time to respond. Very informative even if it wasn't the answer I'd hoped for.
[Raspberry Pi Original Development] Bird39:
How to turn off automatic resolution, I cannot find that function in setting
[Raspberry Pi Original Development] KonstaT:
There is no "automatic resolution switching" thus no settings option for it. Never even heard of something like this before. Something else wrong with that app.
[Raspberry Pi Original Development] LFact:
For me, I cannot make OTA update flashing work. I tried it at least twice, and whenever I flash OTA update and reboot, the machine... all I can see is (seemingly)endless bootloop. I ended up flashing new rom on the SD card via Raspberry pi imager.

- BiTGApps R45 failed to install when I flashed it on 19.1. NikGApps works.
[Raspberry Pi Original Development] KonstaT:
Impossible to say what could be the problem without seeing any logs. I haven't received any other reports of such issue installing OTA packages.

There's a list of what is/is not backed up/restored during installing OTAs in the instructions. If/how gapps are backed up might depend on the gapps release. I'd still probably recommend flashing all the add-ons (gapps, magisk, etc) you had previously installed after flashing the OTA.

I don't have anything to do with any gapps release so you would need to ask where you got the gapps if it's supposed to be compatible with Android 12L
[Raspberry Pi Original Development] LFact:
Sorry, can't provide any logs for I already formatted my SD card. But I'll try again next time when I'm going to flash new version.
[Raspberry Pi Original Development] risant:
Usb dac still not working on 12L lineage 19
[Raspberry Pi Original Development] KonstaT:
Ah yes, one day it will just magically fix itself.

You've been asked about a half a dozen times to provide logs. Since you apparently don't have anything to contribute to solving the issue you can just as well stop asking/commenting on the matter.
[Raspberry Pi Original Development] KostyaInvisible:
Wow, please port on raspberry pi 3🙂
[Raspberry Pi Original Development] KonstaT:
Pi 3 builds are available at

Raspberry

Pi 3

konstakang.com

1gb of RAM on Pi 3 is nowhere near enough for recent Android versions. And generally the hw specs match low-end Android devices from ~7 years ago. It's no fun so I've retired my Pi 3 from development.
[Raspberry Pi Original Development] pi_saab:
here comes my log when I try to connect to bluetooth
[Raspberry Pi Original Development] Ranomez:
Any hope this can run in 4k60?

Tried the config edit 2 versions back and unfortunately only the boot animation shows then the desktop for a second and then black screen.
[Raspberry Pi Original Development] KonstaT:
I don't have any 4k displays so I haven't tested. Impossible to say what is the problem without seeing any logs.

It's been discussed before that if you use a higher display resolution you might run out of CMA memory allocation. You can try increasing it in config.txt ('dtoverlay=cma,cma-384' -> e.g. 'dtoverlay=cma,cma-512'). Display density is also going to be way off for that resolution so you'd need to adjust value of 'ro.sf.lcd_density' property.

The GPU on Raspberry Pi is not that powerful and there's four times more pixels to render on 4k than on 1080p. This is naturally going to affect graphics performance.
[Raspberry Pi Original Development] maxmaschine:
Hello,

I have a problem with my Pi4-8GB.

I would like to use Android 11 (18.1).

After flashing and inserting it into the Pi, I get a message on the display that there is a newer version and that an update should be carried out.

But when I flash Android 12 (19.0) there is no OpenGapps tvStock...

what can I do to get Android 11 working???

Thanks in advance for the support

Greetings Max
[Raspberry Pi Original Development] NonStickAtom785:
Simple. There are no TV Stock Apps from OpenGAPPs packaged for Android 12. However if you really want those apps you can always check out the ATV-3 Android TV build on Google and extract them for use in your own version. Other than that I know the pain of no available TV Stock Apps.

And as a smaller thought that's nagging at me.... Are any and all of your previous apps just gone?
[Raspberry Pi Original Development] maxmaschine:
well, that's exactly why I wanted to use Android 11 and thus avoid the problem!

Can you tell me why I can't boot the A11 on the Pi4?

or what I have to do to get A11 to run on the Pi4?
[Raspberry Pi Original Development] NonStickAtom785:
A11 would have issues if you're USB booting and you haven't changed your /boot/config.txt to use USB boot. Can you tell me anything about what your doing with A11?
[Raspberry Pi Original Development] maxmaschine:
I would like to set up a TV box and boot from SD...possibly. later make recordings on an SSD, which is then connected to the USB. But this doesn't have to be the case...would be perfect (TV recorder).

...for A11 there is OpenGapps to install Playstore and apps, so that I can install media libraries and Prime or AppleTV apps!?!

...of course I could also use A12, but then I have the problem that when I install NIKgapps or BitGapps, the display remains black afterwards... only the mouse pointer is shown when you move the mouse... maybe there there is a way to fix this error and I can continue with A12...?!

Maybe there is also a guide to fix the problem with the black display?
[Raspberry Pi Original Development] KonstaT:
Topic for LineageOS 18 dicussion is https://xdaforums.com/t/dev-rom-unofficial-lineageos-18-1-android-11-for-raspberry-pi-4-b.4212945/

As for the solution, please see http://disq.us/p/2mhag47
[Raspberry Pi Original Development] maxmaschine:
Hey Master himself... I bow!

Since I don't speak English very well, I have to translate everything. Unfortunately, this always takes some time to understand everything correctly. So please bear with me...

..thank you for your answer and the links. I will then try to understand and implement this.
[Raspberry Pi Original Development] maxmaschine:
Hello Konsta,

as in the description, I have now loaded the files fixup4.dat, fixup4x.dat, start4.elf, and start4x.elf from GitHub and replaced them on the boot part, but unfortunately had no success...

the Pi4 wants it still a new version and doesn't want to boot A11.

Is there still a possibility to retune the Pi so that A11 runs?

Greetings Max
[Raspberry Pi Original Development] KonstaT:
Please use the LineageOS 18 topic I linked to discuss any issues with that release. At least there's some chance the next person facing the same issue will find the discussion/solution there. No one is going to find here.

Updating the boot firmware has been reported working fine on the newer hardware revision. There isn't any newer version available of the firmware so most likely something went wrong at your end copying it.

Flash the Android image to a sdcard -> mount the sdcard on your computer (even Windows manages to mount the boot partition) -> copy the four firmware files you downloaded to the boot partition to replace the old ones -> put the sdcard to your Pi and boot.
[Raspberry Pi Original Development] maxmaschine:
Thanks for the description, but exactly as described I did it. I will repeat it later step by step and of course put it in forum A18.1
[Raspberry Pi Original Development] maxmaschine:
Hello everyone,

I have now tried again to install version 19ATV (lineage-19.0-20220114-UNOFFICIAL-KonstaKANG-rpi4-atv.zip).

Here I have proceeded according to the instructions of Konsta and can also start A12 on the Pi4 8GB.

After that, I started in recovery mode as described in the instructions and installed the BitGApp (BiTGApps-arm64-12.0.0-R45_signed.zip) and rebooted it as described.

After that, unfortunately, I only get a black display (see picture).

Apparently, however, the system is running, as I can change the volume e.B. with F11/F12.

How do I get to see a normal screen to install apps with the Playstore?

I have already tried the same with NikGApps (NikGapps-AlokNewS-arm64-12-20220331-signed.zip). Unfortunately I also get the black screen here...

So I assume that I am making a mistake here and do not yet fully understand where or how I can fix it. Maybe someone here knows what could be the reason or what I'm doing wrong???

Greeting Max
[Raspberry Pi Original Development] KonstaT:
Please read the FAQ.

There's no Android TV gapps for Android 12 that I'm aware of. You can't install regular gapps to Android TV builds or vice versa.
[Raspberry Pi Original Development] eguitian54:
Hello guys, I am embarking on a project of my own but I am having difficulty editing my flashable script file to work on TWRP. I have the latest Lineage OS installed and it works perfectly. What I am trying to accomplish is install the shutdown script. I have the original script which I know works because by mistake I fried that pin testing the project :'D.

Now I am trying to change the script from GPIO pin 27 to GPIO pin 17 but everything I compress the file, no matter what I do I get the error Invalid zip file format.

Is there some sort of special compression settings that I need?

my steps usually are:

* download original file (pin 27)

* extract the downloaded file

* open with visual studio code

* edit shutdown script (change 27 to 17 on line "GPIO = 27")

* save the file

* the use 7zip to create the zip folder

(I have tried normal compression and storage compression)

any pointers on how to edit this file and compress it again and have it work when flashed on TWRP?
[Raspberry Pi Original Development] KonstaT:
New builds.

LineageOS 19 (Android 12L)

for Raspberry Pi 4

konstakang.com

-automatically set density based on display resolution (use ‘ro.sf.force_lcd_density’ property if you want to force specific density)

-add option to disable tablet taskbar and show traditional navigation bar instead

-update to TWRP 3.6.1_11-0-KonstaKANG

-update to Mesa 22.0.1

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

-Android security patch level: 5 April 2022 (merged)

---

LineageOS 19 Android TV (Android 12L)

for Raspberry Pi 4

konstakang.com

-Android 12L / LineageOS 19.1

-also available as OTA package

-automatically set density based on display resolution (use ‘ro.sf.force_lcd_density’ property if you want to force specific density)

-various drm_hwcomposer updates e.g. support for dual-HDMI displays and headless mode (thanks to Roman Stratiienko)

-switch to codec2 software decoders/encoders

-add option to enable currently very WIP H.264 hardware video decoding using v4l2_codec2 (enable experimental feature from the settings)

-update to TWRP 3.6.1_11-0-KonstaKANG

-update to Mesa 22.0.1

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

-Android security patch level: 5 April 2022 (merged)
[Raspberry Pi Original Development] duckredbeard:
Now we need someone to write a Tasker plugin that will use GPIOs as profiles. Think "button" event for an input. And LED on/off for tasks. LED on state can actually power a relay for control of other things. Think garage door opener, entry door state, smart doorbell, etc. This could be the gateway for a really customizable home security system. All Tasker based.