yashsingh1/xdaforums huggingface dataset:
[Raspberry Pi Original Development] KonstaT:
It's not enabled in any of my current kernels. It will be enabled if/when there are any builds released after today.

You have missed the step in the instructions that's tells to modify the firmware path according to where you've saved them.
[Raspberry Pi Original Development] LPCA:
here's my results so far with LOS 18.1 Android TV on Raspberry Pi 4 2GB, on Argon V2 case...

Does not boots via PINN LOS 18.1 2021-11-23 without modified startelf files (https://github.com/procount/pinn , https://github.com/procount/pinn-os/blob/master/os/os_lineage.json), had to push these from KANG repo / LOS 19.1 zip archive.

Boots with latest lineage-18.1-20220512-UNOFFICIAL-KonstaKANG-rpi4-atv.zip (

https://konstakang.com/devices/rpi4/LineageOS18-ATV/)

Can not install Magisk zip in TWRP recovery when installed with PINN.

But can install Magisk zip in TWRP recovery when installed without PINN and Magisk works.

Also can't reflash LOS image via TWRP recovery when installed with PINN.

Suspect issues with backup/restore with PINN but need to test more.

OTA updates fail with PINN, both via LOS UI and TWRP recovery.

Did not try OTA updates without PINN.

Google Apps from MindTheGapps-11.0.0-arm64-20220217_100228.zip (https://androidfilehost.com/?w=files&flid=322935 )worked, though not listed in instructions. We get the great stock AOSP ATV Home launcher, without google crap or filtered/hidden apps.

Google Apps from work-in-progress open_gapps-arm64-11.0-tvstock-xxxxxxxx.zip worked as per instructions, but this is bloated, should not be used, you get loads of google crap.

4K resolution did not work for my TV in any of the 2 options (it scales 80% of the screen out of boundaries).

Overclock to 2000 MHz ondemand worked.

Has issues with left-clicking on certain buttons on certain apps.

Back button on Minix Remote does not work always.

Back button on right mouse works almost always.

Interface is usually super fast until you fill your install with lots of apps.

HDMI audio worked perfectly fine.

There is no LOS/RPI OS Hardware accelerated video.

Stream results without LOS/RPI OS Hardware accelerated video:

NewPipe (YouTube) worked, super fast.

HBO Max worked, but too slow, even at SD quality.

Disney+ worked, but drags a bit. If opened via Streamio with tunneled playback + HW acceleration, it almost does not drag.

Amazon Prime Video does not work.

Plex stream for Euronews/TED worked, and fast/good.

ARTE worked, and fast/good.

TED worked, and medium-fast speed.

Euronews worked, and fast/good.

RTP Play worked, but too slow.

Can't install Netflix app. If forcing it into the system apps, complains does not have required components.

DRM reports ClearKey CDM 1.2 and Widevine CDM 16.0 (L3, no HD/4K).

No problems with Streamio links to other apps.

Can't install zips in Magisk, reports "unzip error" (just as in https://github.com/stylemessiah/SQLite3UniversalBinaries/issues/1)
[Raspberry Pi Original Development] KonstaT:
Replied at https://xdaforums.com/t/dev-rom-uno...aspberry-pi-4-b.4356891/page-22#post-87507801 so not much point in repeating the same things here.
[Raspberry Pi Original Development] SerdarARIKAN:
Hi KonstaT. Thank you for everything.

I have tried almost all versions and versions. But I couldn't find a way to wirelessly my clone DualShock3 Sixaxis gamepads.

First of all, if I install gapps pico, the internal bluetooth was not working. I solved this with the help of gapps-config.txt file. And I tried to install DualShock with the help of SixaxisController1.1.2.apk and SixaxisPairToolSetup-0.3.1.exe, which I provided albeit difficult. But SixaxisController1.1.2 cannot detect the internal bluetooth address no matter what I do. I can view the bluetooth address from the android menus. However, the address I found does not work for me. I think this issue is related to SElinux. I'm sure you're aware of all this.

My question is, is there anything I should know? Is it possible to run my clone DualShock3 Sixaxis gamepads wirelessly with any hacks/tricks or I don't know if it gives a specific LineageOS or an external bluetooth dongle?
[Raspberry Pi Original Development] KonstaT:
I'm not aware of any issues with bluetooth not working in general after installing gapps. There's a known issues with pairing some bluetooth remotes but that's with Android TV gapps (https://github.com/opengapps/opengapps/issues/915). There's also alternative gapps releases. Gapps are not part of my builds in any case.

Impossible for me to say what is the issue without seeing logs (logcat?) or having the hardware to test myself.
[Raspberry Pi Original Development] audioPrandan:
Hi KonstaT,

Hi KonstaT

Does the lineage 20 series support hifiberry digi sound card drivers?
[Raspberry Pi Original Development] KonstaT:
Any build that has been released since that post (Sep 6, 2022) has that missing driver enabled. I don't have hardware to test myself, though.
[Raspberry Pi Original Development] audioPrandan:
Thank you KonstaT, I Installed 20 series as mentioned in the portal, then enabled the hifiberry digi dac from raspberry settings. Didn't not make any Manual changes to config file. But still audio is not working.
[Raspberry Pi Original Development] KonstaT:
Please provide output of 'cat /proc/asound/cards' and/or 'dmesg' after booting the device to see if the audio card is detected as an ALSA device.
[Raspberry Pi Original Development] audioPrandan:
Attached are the screenshot of cat /proc/asound/cards and dmesg
[Raspberry Pi Original Development] KonstaT:
You're missing the HDMI audio devices. This is what it should look like (on Android 12/13) and DAC is expected to be ALSA device #4.

console:/ # cat /proc/asound/cards
0 [Headphones ]: bcm2835_headpho - bcm2835 Headphones
bcm2835 Headphones
1 [Loopback ]: Loopback - Loopback
Loopback 1
2 [vc4hdmi0 ]: vc4-hdmi - vc4-hdmi-0
vc4-hdmi-0
3 [vc4hdmi1 ]: vc4-hdmi - vc4-hdmi-1
vc4-hdmi-1

Are you using DSI display or how did that happen?

To get audio out of the DAC with your ALSA device configuration you would need to

setprop persist.audio.pcm.card 2

in shell.
[Raspberry Pi Original Development] audioPrandan:
I have a rpi touch screen and also a hdmi adapter to connect to an external screen, is it bcoz of the adapter that it's showing a different configuration? Will run the shell command and let you know the outcome.

Thank for the quick response KonstaT!
[Raspberry Pi Original Development] audioPrandan:
Ran the setprop command. But no difference. No audio during playback.
[Raspberry Pi Original Development] KonstaT:
Did you reboot the device? Is the DAC still ALSA device #2?
[Raspberry Pi Original Development] audioPrandan:
Yes, rebooted , but still showing up as #2
[Raspberry Pi Original Development] KonstaT:
Ah, that's not even Android. You're booted to TWRP which is entirely separate OS on its own. TWRP doesn't use hardware accelerated graphics (i.e. 'dtoverlay=vc4-kms-v3d' is not enabled) which also explains why you don't have the VC4 HDMI audio devices.

Actually check the information I asked when booted to Android.
[Raspberry Pi Original Development] audioPrandan:
Thank you KonstaT for the patience and the input, Yes! it's fixed now after I ran the setprompt in android. Attached the screenshots for your reference and and yes you are right. I can see the alsa listing accurately . Thanks Again.
[Raspberry Pi Original Development] KonstaT:
Good to know you got it working. :)

It's strange why some DACs appear in the ALSA device list before the HDMI audio devices and some after. Since my audio implementation just select the ALSA device to use by the device number this doesn't work in all cases.
[Raspberry Pi Original Development] KonstaT:
No.
[Raspberry Pi Original Development] sinasolar:
Is your streaming problem fixed?

I am facing this issue almost in every straming platform that i have tested.

Is there any hardware decoding build for LineageOS ATV on Rpi4B? Or how can i install propper codec on LOS ATV 18.1
[Raspberry Pi Original Development] KonstaT:
This build is seriously outdated and has been discontinued for nearly two years. Please use the latest Android 13/14 builds instead.

H.264/H.265 hardware video decoding is implemented on LineageOS 19/20/21 releases.
[Raspberry Pi Original Development] SEXCAVATOR:
That's what I did. I installed SSH terminal and tried to use "su" locally. I also tried embedded SSH. No success.

Does that mean I can have root access only connecting from outside? Like from PC?
[Raspberry Pi Original Development] OdeMix:
To be honest, I have never been able to use this myself. I tried to connect using a PC and ADB shell. But it didn't work. Therefore, I returned to LineageOS 17. I don't see any difference between 17 and 18, but in version 17 the full root works.
[Raspberry Pi Original Development] KonstaT:
There's no su binary included in the latest release. Different ways to have root access are described in the FAQ. Yes, you need to connect to your device from outside (adb/ssh/serial console).

If/when there's another release I'll add a separate TWRP flashable su add-on and settings option for root access.

You can also just mount the sdcard on your computer to edit /boot/config.txt.
[Raspberry Pi Original Development] SEXCAVATOR:
Thanks for the info. I couldn't even install "nano" editor on local terminal. No package manager whatsoever. I was thinking popping sd card in to pc to edit "config.txt". But I thought I shouldn't be lazy, there must be a local way. Now I see thats the right way.

To develop shell script (to use "sysfs") I need root access. I guess I am not alone. If and when there will be another release, we will be waiting.
[Raspberry Pi Original Development] KonstaT:
Well, this is Android so it doesn't have any Linux package management. LineageOS already comes with nano (and vim) text editor(s) so you wouldn't need to install it separately anyway.

Actually having root access via adb/ssh is more than enough for developing script. Since you're probably familiar with command line and shell scripting this shouldn't be much of a problem. For adb see https://developer.android.com/studio/command-line/adb and FAQ has instructions for SSH.
[Raspberry Pi Original Development] SEXCAVATOR:
A developer keeping up with his thread, great effort!

I don't have "nano" command available in local SSH client (enabled in developer settings). I'll try using SSH client over ADB. Also give it a shot at "vim".

I was always thinking this OS is a variant like Debian or Ubuntu. It seems it is far relative in linux family. I'll use ADB for developing scripts.
[Raspberry Pi Original Development] KonstaT:
New build.

LineageOS 18.1 (Android 11)

for Raspberry Pi 4

konstakang.com

-add support for LSM303DLHC accelerometer & magnetometer sensor

-add separate TWRP flashable su add-on (see FAQ)

-allow switching display off with power button

-add support for USB-C (ADB, MTP, PTP, USB-tethering)

-enable bluetooth tethering

-add settings option for mouse back button feature

-update to TWRP 3.5.0_9-0-KonstaKANG

-update to Mesa 20.3.4

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

-Android security patch level: 5 February 2021 (merged)
[Raspberry Pi Original Development] kannaiah:
Hi,

I tied to this on 64GB sdcard and I couldn't get past twrp recovery, reboot to system also booting into twrp.

I also tried 17.1 but it's same.

I have few leads connected to gpio to drive a small fan but not sure if that is the issue.
[Raspberry Pi Original Development] SEXCAVATOR:
Pin21 is power button for build 18.1. Maybe thats tha case.
[Raspberry Pi Original Development] kannaiah:
Thanks. I have changed pins used for fan and can not into Android (y)
[Raspberry Pi Original Development] kannaiah:
I know if has been asked before about HW support of video decoding/encoding. Is it possible to get that support on Android. I tried Youtube to play @1080P and it was not playing smoothly.
[Raspberry Pi Original Development] hiderto:
Hi,

First of all, congrats for this rom and the effort to provide such service to all of us ;)

I have successfully installed this rom into my Raspberry Pi4 without any issues.....except one. While using my Pi4 on a normal FullHD external pc monitor everything is perfect in terms of resolution but the same does not apply to my TV.

I am really keen on using my (already) old TV https://www.cnet.com/products/samsung-le26r72b-26-lcd-tv/ with the Pi, however, no matter how many settings I put on config.txt or resolution.txt, the result is always the same.

The tv has a max resolution of 1360x768, however, Lineage always looks the resolution on 1920x1080.

I tried adding 1360x768 and 1280x720 inside resolution.txt, but the option inside Raspberry Pi menu is always Preferred, nothing more.

Do you have any suggestion?

Best Regards,
[Raspberry Pi Original Development] KonstaT:
YouTube at 1080p should work just fine without any dropped frames. There's known to be problems with 1080p60 videos.

V4L2 codec support for Android is being worked on by various companies (including Google) so I'm sure we'll get there eventually (though it still might take an Android version or few). I'm not going invest hundreds/thousands of hours of free work into this. If/when it's eventually ready I'll look into implementing it with bcm2835-codec as well. As for some (old) ideas how to implement see https://xdaforums.com/t/dev-rom-uno...rry-pi-3-b-and-b.3943678/page-6#post-81930725.

Options that you see in Settings -> System -> Advanced settings -> Display resolution depend on what your connected display reports it supports. Your display doesn't report anything.

Resolution is fine, you just need to adjust the overscan. Look into various overscan options in /boot/config.txt (https://www.raspberrypi.org/documentation/configuration/config-txt/video.md). Removing/commenting out 'disable_overscan=1' is the first thing to try.
[Raspberry Pi Original Development] hiderto:
What is interesting is, while using these setting for my config.txt (among others)

# Display
[HDMI:0]
[HDMI:1]
hdmi_force_hotplug=1
hdmi_ignore_edid=0xa5000080
hdmi_drive=2
hdmi_group=1
hdmi_mode=4
# disable_overscan=1
hdmi_cvt=1360 768 60 3 1 0 0

the TRWP menu is as perfect as I would like to be, however, the end result is even worse:
[Raspberry Pi Original Development] KonstaT:
hdmi_* options in /boot/config.txt have no effect with KMS driver which is used with hw accelerated graphics on Android. They do have an effect on TWRP, though.

Adjusting overscan options should still work like documented. I'd also recommend changing Settings -> Display -> Display size if you're using a resolution smaller than 1080p.
[Raspberry Pi Original Development] KonstaT:
There's also Android TV version available.

LineageOS 18.1 Android TV (Android 11)

for Raspberry Pi 4

konstakang.com

-initial Android TV build

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

-Android security patch level: 5 March 2021 (merged)
[Raspberry Pi Original Development] mrgou:
I just flashed the Android TV image to an SD card. On first boot, I get a blank Android TV screen.

However, the Android TV Remote app does not detect the device (which is wired to my router), so I can't control the device

Is there something more I need to do?
[Raspberry Pi Original Development] KonstaT:
Yes, you need to install Google application (see FAQ) to use the official Android TV remote app.
[Raspberry Pi Original Development] mrgou:
OK, I didn't think this had to be done before using the remote app.
[Raspberry Pi Original Development] KonstaT:
It also need Android TV remote service running on the Android TV device. This is only included in gapps.
[Raspberry Pi Original Development] hp420:
How does this run on the 2gb model? is it enough, or should i just get the 4gb?
[Raspberry Pi Original Development] RoM_Addict:
Am I the only one having issues with Androidfilehost and No Mirrors found??
[Raspberry Pi Original Development] KonstaT:
Just tested and works fine for me. AndroidFIleHost has issues sometimes. Try refreshing the download page or try again later.
[Raspberry Pi Original Development] cpedregal:
Hi all,

I have a raspberry pi 4 (4 giga Ram) device and I have a problem during first set up after installing rom. Just after setting up my wifi network, my device shut down, always at that point.

I've tried several times and I always get the same problem.

Am I the only one having this problem?
[Raspberry Pi Original Development] RoM_Addict:
Thanks Konsta. It did work later into the night.

Congratulations for the amazing work, it performs really well and I believe it's perfect for the Android touchscreen mirror I'm working on.

Again, thanks for the great work!!
[Raspberry Pi Original Development] RoM_Addict:
Also have a PI 4. My setup went flawless, it seems very stable. Even the second time around after flashing Gapps it was very solid without any notable errors.

Did you update the PI to the latest firmware through Raspbian first?

If you did then maybe the flashing corrupted some files, have you tried doing a clean flash from a newly formatted card?
[Raspberry Pi Original Development] cpedregal:
I didn’t update the firmware, maybe the reason. I will try that. Thanks!
[Raspberry Pi Original Development] KonstaT:
General advice is to use proper sdcard (at least class 10) and power source (3A in case of Pi 4).

There's also a know issue related to wifi (https://github.com/lineage-rpi/android_kernel_brcm_rpi/issues/6) but there's been some mixed reports whether this is fixed on LineageOS 18 (or there's two separate issues).
[Raspberry Pi Original Development] Supernova76:
Will you make a Pi 3b+ version or is there not enough ram?
[Raspberry Pi Original Development] hp420:
ram is a big issue with pi 3b. running los17 is a fairly aggregating experience for me, personally...it is VERY slow. los16 works great on pi 3b, though!!
[Raspberry Pi Original Development] Saftpresse99:
I hope there will be a last Pi3 Version. I look everyday in the forum.
[Raspberry Pi Original Development] KonstaT:
I've already mentioned few times that I've retired my Pi 3 so I won't be providing any public updates anymore.

There's no technical reason why Pi 3 wouldn't run Android 11 as well. Lack of RAM is of course a problem but it's a problem for previous Android versions, too.
[Raspberry Pi Original Development] rabbited:
KonstaT.. have you considered releasing NOOBS/PINN image files of new releases as well? The creator of PINN has created versions up to Lineage 17, but if you created a NOOBS compatible version we could start using it as soon as the release comes out rather than waiting for him to update PINN.
[Raspberry Pi Original Development] KonstaT:
No, I don't plan to support any multi-boot solutions. There's already enough for me to maintain two versions (regular tablet UI & Android TV) for each Android version.

And it's not even that simple to get everything working (Android & TWRP both sdcard & USB boot) with how the partitions are mounted in multi-boot environment. We've been through this with PINN developer procount and it actually requires quite a bit of changes to the image to make it work. I think he has managed to automate this process now which should help making newer builds available easier.
[Raspberry Pi Original Development] Bingoig11:
Just ordered my Pi4 and get this rom installed, what a job, congrats.

Didn't found the ethernet connection, only wifi, any hint?

Thanks
[Raspberry Pi Original Development] Supernova76:
Plug in ethernet and see if it works?
[Raspberry Pi Original Development] KonstaT:
Regular tablet UI Android builds don't have any settings options for ethernet connection. You'll only see an icon in the status bar when you're connected using ethernet.

There's some settings options for ethernet connection in Android TV builds.
[Raspberry Pi Original Development] kawayan22:
Hi, i have been using Lineage OS 17 for a while. I have problems with my wifi signal it keeps dropping. But i have no problems with using the ethernet (im sharing my laptop's wifi connection to ethernet) i restarted my raspi and then got stuck on bootloop and i dont know the reason. So what i did is i downloaded the Lineage 18 and installed gapps tv stock now my computer cant detect the ethernet connection, and im currently connected to my laptops hotspot i wanted the ethernet port to work. Checked eth0 via if config it says that its Up,broadcasting,running,multicast but on my laptop network adapter settings there is no device that is connected on my laptops ethernet port. Anu thoughts on how to fix this?

And any updates on the hardware video decoding? Videos stutter when its decoding 1080p videos. Thank you so much. Love your works
[Raspberry Pi Original Development] escknx:
Following manual and looking for a way to boot in TWRP I am unable to find Advanced Restart entry in Developer options

edit

Found in under "Gestures" settings, not in Developer Options
[Raspberry Pi Original Development] KonstaT:
New build.

LineageOS 18.1 (Android 11)

for Raspberry Pi 4

konstakang.com

-add initial support for HDMI-CEC

-add built-in VNC server

-update to Mesa 21.0.2

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

-Android security patch level: 5 April 2021 (merged)
[Raspberry Pi Original Development] scottial:
Hi, do you have planned to use 5.10 kernel?
[Raspberry Pi Original Development] KonstaT:
Difficult to say what could be the issue with ethernet. Could be a lot of things including your computer (rebooting everything is of course the first thing to try).

http://disq.us/p/2flzmq1 is the latest discussion on hw video dec/enc with relevant links.

Yes, this was moved in LineageOS 18. FAQ does point you to the right place, though.

Yes, I've had it running all the way from 5.10.0 version. ;) 5.10 also brings supports for DSI display with KMS driver used with hw accelerated graphics (among various other improvements to KMS support) so I'm looking forward to this as well.

There's no sdcardfs for 5.10 which means using the new quota storage. There's a strange storage issue with this after installing gapps. Some apps don't have access to internal emulated sdcard after installing gapps. It's fine without gapps, I think it's fine with gapps after formatting /data in TWRP (vs. just doing a normal factory reset). Not sure what is the issue exactly and haven't really had time to look into it more closely.

5.4 is the newest kernel version Android supports for R. 5.10 is actually S (Android 12) kernel so there's that, too.
[Raspberry Pi Original Development] escknx:
I use Pi4 as I car head unit with USB DAC, Topping D10S in particular as USB-Optical converter going further to DSP. And what I noticed is that Lineage OS outputs sound as 96khz by default, that is different from all other Androids I used. Is this normal behavior? I'm getting pretty rough jitter, I wonder if this something to do with 96khz upsampling? I plan to try Hifiberry Digi to get that optical out, hopefully it will solve the jitter.
[Raspberry Pi Original Development] KonstaT:
I haven't made any changes to USB audio. It's a common HAL across all Android devices.

Pi device specific audio HAL supports 16-bit PCM at 44100 & 48000 Hz for audio output. This also applies if you use a GPIO audio DAC.
[Raspberry Pi Original Development] scottial:
Anyone have "Ok google" hotword working? I've installed nano Opengapps, but won't work.
[Raspberry Pi Original Development] Supernova76:
You need the Google app and maybe also the Google assistant app.
[Raspberry Pi Original Development] scottial:
I've installed and updated all google stuff, but the hotword detection won't work.
[Raspberry Pi Original Development] Supernova76:
You need a microphone.
[Raspberry Pi Original Development] vacardozo:
Hi, the versions 17.1 and 16.0 always reboot after loading the boot image over and over again, and never boot. In version 18.1 cannot change the time zone, the rest works fine.
[Raspberry Pi Original Development] escknx:
I assume it does not apply to Hifiberry Digi+? Trying to get pure optical out but Digi+ does not seem to work.