yashsingh1/xdaforums huggingface dataset:
[Raspberry Pi Original Development] ndkone:
Anyone know if there is a way to add DVD/BD driver to the build so a USB BD drive can be attached to RPi to play disks with mp4 or vob files with VLC?

Does it need a special USB driver and/or ISO9660 FS layer in the kernel?
[Raspberry Pi Original Development] KonstaT:
If it's not exposed as regular USB storage device unlike you could that working natively in Android. There seems to be specific third party apps for the purpose/to support specific drives, though.
[Raspberry Pi Original Development] rabbited:
Are you still performing updates on Lineage 18.1? Lineage 19 doesn't appear to be operating properly yet on the CM4 and it would be great to have the same wifi fix on this in the meantime until those issues are ironed out.
[Raspberry Pi Original Development] KonstaT:
I have at least one more LineageOS 18 release planned sometime next year. It depends if/when things with LineageOS 19 get to point there is no reason to maintain older versions. Might take a little longer this time around.

I don't have any CM4 hardware so I don't plan to "support" it with LineageOS 18 anyway. It was just recently brought to my attention that CM4 doesn't have built-in audio which causes problems with my builds (slightly less with LineageOS 19). Wifi is also broken on CM4 with the latest LineageOS 18 build (works with builds from previous dates) in any case and that info also took quite some time to get to me.
[Raspberry Pi Original Development] Petikeje:
Hi All, I installed lineageos 18.1 Android tv version to a raspberry pi 4. It is connected to the network via ethernet cable. Based on the "Working features" list from the original homepage the wifi tethering should work, but I can't find the option to it. Could you please help me how can I activate the wifi hotspot? THX!
[Raspberry Pi Original Development] rabbited:
Sounds good, I guess I will stick to Lineage 18.1 over ethernet for CM4 use for now.
[Raspberry Pi Original Development] masscream:
Hello, not sure where to report this, using LOS 18.1 (lineage_rpi4-userdebug 11 RQ2A.210405.005 eng.tuomas.20210411.100134 dev-keys) with TWRP 3.5.0_9-0-KonstaKANG via PINN OS (I know it's not supported, but this one looks like ROM/TWRP issue). I wanted to flash Magisk but I always got ERROR: 7. The install log contained only "Couldn't find ramdisk!" error. After checking the rpi-magisk.sh install script, I purely found out that sys partitions (boot, system, vendor) were not mounted, despite their right setup in fstab file. Therefore after mount -a, I could get all of their contents via File browser / cmd but not via sh script installation. However in the TWRP Main Menu => Mount, I could mark whatever partitions I wanted, but there was no Swipe bar to mount them. It was missing. I solved this problem by putting the "mount -a" command into the rpi-magisk.sh before ramdisk checking and it was flashed immediately. However isn't it possibly a bug to be removed? Maybe in TWRP... Thank you
[Raspberry Pi Original Development] KonstaT:
Yeah, the working/not working hw list is just a copy-paste of the regular tablet UI Android build. Android TV doesn't have options for any tethering (wifi, bluetooth, USB) and IIRC location access either. There should be third party apps you can use for tethering, though.

I'm not supporting any multi-boot solutions. This is an issue with PINN and there was similar report with my LineageOS 19 build as well (looked it up it was you, https://xdaforums.com/t/dev-rom-uno...raspberry-pi-4-b.4356891/page-4#post-86090251 & https://github.com/procount/pinn/issues/598).

20210411 build is also ancient if you ask me and there's been various new LineageOS 18 builds since that.
[Raspberry Pi Original Development] masscream:
OK, sorry. I remember that issue, and the conditions were a little bit different - because of PINN os config the fstab file was misconfigured and therefore the sys & boot partition could not be mounted and there was a twrp bootloop...... And it was LOS19, this is 18.1 and its fstab is correct as far as I checked it. In comparison with that issue, its TWRP mount tool was able to mount partitions (which were misconfigured). In this issue the partitions are not misconfigured but TWRP GUI button is just missing for uknown reason. But if you say so, I will open an issue on the procount's GH page. At least for the version update.
[Raspberry Pi Original Development] KonstaT:
There is no swipe bars in mount menu in any TWRP version - there's only checkboxes to mount each partition so not exactly sure what you mean by this. There's also going to be trouble using new add-ons with old TWRP recovery or vice versa. Always use the latest downloads from the links you find on my site.

And like said, 20210411 build is ancient. Latest LineageOS 18 builds have TWRP 3.6.0_11-0-KonstaKANG which is the same as the one with my LineageOS 19 builds. So maybe if there was some issue it's also possible it's been already fixed ages ago.
[Raspberry Pi Original Development] Petikeje:
Hi, Thank you for your answer and for your work also! I'm searching for a necessary app but unfortunatelly I can't find any for AndroidTV :-( if you (or somebody) have any suggestion please do not hesitate to share it, I'm still investigating also...
[Raspberry Pi Original Development] misterti:
Late reply. I tested cec, it works on newer LG TV model, but it doesn't work on older model. That's why it looked like it didn't work, cause i was first testing it there. What's interesting is, that cec works fine with LibreElec on older LG TV model. What can we do, to make it work on older tv?
[Raspberry Pi Original Development] nfivez:
Hi there,

I can't seem to get ethernet working on my pi 400, I searched around here and it seems plug and play. I've tried this on android 10, 11, 12 of your builds.

The other thing was accessibility setting(for auto click, screen cast etc). I was able to get it to auto click with android 10 and previously android 11. Now neither 11 or 12 worked. The app is called smart autoclicker on fdroid, and I have also tried other autoclicker on the playstore on android 11 and 12 which did not work.
[Raspberry Pi Original Development] Transform:
I'm running the Android TV version of this build on a 2GB RPi4. I saw that 2 GB is the minimum memory required to run it but I'm running into issues with stuttering video and slow overall performance. Top command shows that there is only 200-300 MB of memory when running any app.

Most of the branded Android TV boxes on the market seem to have 2 GB memory but I wouldn't have thought they would run into this problem. Just wondering if anyone else has successfully run this build on the same hardware as me without memory issues?
[Raspberry Pi Original Development] KonstaT:
Does your TV have CEC menu where to select the device? You can also try uplugging other CEC devices on your TV or using the TV's primary HDMI port for the Pi.

Logcat? Should work just plugging in the ethernet cable so something strange with your network setup.

Logcat? Which LineageOS 18 builds (build dates) are working/not working with the AutoClicker apps?

I only have 4GB model to test but unlikely there is much difference in general performance to the 2GB one (mostly affects multi-tasking performance). Android is capable of doing the memory management and killing old processes when it needs memory. Free memory is wasted memory in this sense.

H.264 1080p videos should play just fine without dropped frames. As software video decoders are used it's very CPU intensive and it can generate quite a bit of heat so your CPU might throttle because of this. Make sure to take care of cooling or at least don't use a case that keeps the heat in.
[Raspberry Pi Original Development] Transform:
I ran a video for 30 minutes to get the CPU load and temperature details:

The temperature initially started out around 55-60c but slowly increased to 80c after 30 minutes of playback. The video was stuttering all the way through - I should mention that it is overclocked to 2GHz

I purchased an Argon Neo case which is supposed to be good at dissipating the heat away from the CPU throughout the case. I do see people recommend getting a fan to help with the cooling and there is an Argon Fan HAT which I could get. However I'm not sure if it is compatible with LineageOS - I tested it via an SSH session and it appears to require sudo access which doesn't exist in LineageOS.

Are you able to confirm whether installing the script would be possible?
[Raspberry Pi Original Development] KonstaT:
Wow, so the device overheats when you overclock it to the max without taking care of any cooling. Who would have guessed. /s :P

You don't need to overclock for smooth H.264 1080p video playback. You most definitely shouldn't overclock if you don't know what you're doing. You most definitely shouldn't overclock if you don't take care of proper cooling. Just because you're given the option to overclock the CPU doesn't still mean that you should. LOL, kind of feels like 2012 again when overclocking Android devices was still a thing.

You can't use drivers/scripts intended for regular Linux distros with Android. Someone shared a script for Argon case that changes the fan speed according to CPU temperature (http://disq.us/p/2guifm1).
[Raspberry Pi Original Development] Transform:
I have installed a fan now and everything is running much smoother. Many thanks!
[Raspberry Pi Original Development] misterti:
Tried all variants, it doesn't work on older LG TV. Must be something protocol version specific. I guess i'll need to get the log. I think logcat should hold all the info?

There are also 2 things on 18.1 tablet version:

- hdmi goes black screen and never returns, if hdmi cable is unplugged and then replugged.

- after a few days of using the tablet version (did not notice on tv version), the sound and picture on all video apps goes out of sync. Only a reboot can fix it.
[Raspberry Pi Original Development] KonstaT:
I doubt logcat will show much about CEC if your TV is non-existing as far as Android is concerned. My builds include 'cec-ctl' tool that might show something (e.g. 'cec-ctl -S' to show the CEC topology).

It's a requirement that you need to have display connected or there's nothing for the graphics drivers to draw on. Last I tested on LineageOS 19 you can unplug the HDMI if you switch display off on Android first and plug it back in before turning it back on again (short press on the power button like on Android devices in general). Haven't checked if this is different on LineageOS 18 (there's other display hotplugging related changes on Android 12 as well). If you want to run without actual display connected you can buy a HDMI dummy adapter that still reports EDID information.
[Raspberry Pi Original Development] KonstaT:
New builds. Things are moving forward with LineageOS 19 so these can possibly be the final LineageOS 18 builds. Same changelog on both.

LineageOS 18.1 (Android 11)

for Raspberry Pi 4

konstakang.com

LineageOS 18.1 Android TV (Android 11)

for Raspberry Pi 4

konstakang.com

-fix reboots related to Hotspot 2.0 networks/ANQP requests (see issue #6)

-Vulkan 1.1 (thanks to people at Igalia for Vulkan 1.1 conformance and Roman Stratiienko for latest Mesa fixes)

-add new options to Raspberry Pi settings (force rotation & CPU governor)

-prepare for OTAs

-update to TWRP 3.6.0_11-1-KonstaKANG

-update to Mesa 21.3.4

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

-Android security patch level: 5 January 2022 (merged)
[Raspberry Pi Original Development] rabbited:
The new build works perfectly so far. No problem on CM4 with WiFi (ANQP or otherwise) with fix and no issue with permissions that I am experiencing with the new Lineage 19 builds. Excellent work, thanks!!
[Raspberry Pi Original Development] Micka41:
Hello,

I also tried with your Android 10 build, same problems.

What solution do you recommend?

My hardware : Raspi4 8Gb, SD or USB Key (I prefer), HD Touch Screen.

Thanks
[Raspberry Pi Original Development] KonstaT:
You would need to contact the app developers for support. I wouldn't know without seeing any logs (logcat in this case) anyway. USB microphones in general should work (and work with other apps). There was a report about some mic issue with WhatsApp on Android 11 (works with Android 10) so there's still something either with app support or the OS as well.

This is not a phone build (it's configured for a non-telephony tablet) so it doesn't have a ringtone option. What would you need it for?
[Raspberry Pi Original Development] cem_ari:
Woow. I just saw your new work. Thank you very much.

I'm in your previous work LineageOS 17.1. Do you think this is better in car usage? Or should i stay in 17.1?
[Raspberry Pi Original Development] KonstaT:
It's for you to decide if it brings something that you need in that environment.

The copy-paste answer.
[Raspberry Pi Original Development] tomixx00420:
Hello!

I just install this OS to my RPi4 (4GB RAM, bootloader c3052221a SEP 3 2020) and I install also the Gapps (BiTGApps-arm-11.0.0-R19_signed).

Without Gapps it works perfectly, but when I install Gapps - When I click on anything, I have a black screen for a few seconds.

Is there any solution for this problem?

I want to use this RPi with touchscreen (Waveshare LCD H 1024*600) in my car. I also tried to install older Android 10, but that's super slow.

Thanks! ;)

Btw, awesome work!
[Raspberry Pi Original Development] tomixx00420:
Okay, looks like that problem is solved 😅

I just changed Audio output from HDMI to 3.5mm jack in Advanced settings.
[Raspberry Pi Original Development] KonstaT:
I don't see how gapps or switching audio device would have any effect on that. Something strange at your end. Logs are usually more helpful that videos.

There is no notable difference in performance between Android 10 (LineageOS 17) and Android 11 (LineageOS 18) builds.

Also FYI to everyone, OpenGApps also has Android 11 arm test builds available.

OpenGApps - Browse /arm/test at SourceForge.net

OpenGApps daily releases

sourceforge.net
[Raspberry Pi Original Development] Vailskier:
Does somebody know if there is a noticible performance difference using the 4gb or 8gb ram version? I want do get a RPI4 and attach it to an USB touch screen.
[Raspberry Pi Original Development] card13:
@KonstaT Been wondering about this and I'm sure there's a simple answer, I just haven't found it yet, many OS Builds for this device are 32bit (including this ROM) is there a reason why the 64bit Builds haven't shown up yet (esp in regards to LOS)? I'm assuming it has something to do with too new of device with too new of OS (recompile/upstream/backport changes, etc) slowing down releases, but I could be wrong.
[Raspberry Pi Original Development] KonstaT:
I only have the 4 gb model so I don't have anything for comparison. I'd say 4 gb is sufficient for running Android on the Pi. What permance gains do you expect to see by having more RAM? It would mostly affect multi-tasking perfomance (i.e. how many apps you can have open at the same time or how many browser tabs you can keep in memory before reloading). It's CPU/GPU/storage speed that matter for the general performance more than going 4 gb -> 8 gb. If the price difference is minimal the more the better of course for future proofing your device.

Generally speaking I guess it's mostly because Raspberry Pi Foundation is moving slowly with 64-bit. Raspberry Pi OS is still 32-bit and I think this because they want to support the older Pi models with the same OS. Pi 4 is the first Pi model where it actually makes any sense to have an 64-bit OS. Pi 3 had 64-bit capable hardware but only 1 gb of RAM so that quickly defeats any architectural advantage (64-bit OS uses more memory).

I've had 64-bit LineageOS builds running on the Pi 4 over a year so there's nothing too special about it. I've also maintained the 64-bit Android kernel for quite some time (https://github.com/lineage-rpi/android_kernel_brcm_rpi). Why I haven't relased any 64-bit LineageOS builds is because I've chosen a feature set that I want to support and I also have some internal quality standards I like to meet. There's still various things that are broken on 64-bit builds so not much point in releasing to public when you can also have builds where everything is basically working.

It's still under consideration if there's any point in making some 'bleeding edge' release for people who are just interested in testing.
[Raspberry Pi Original Development] card13:
@KonstaT Thank you for the explanation it makes perfect sense now.
[Raspberry Pi Original Development] vj4:
Got this up and running using the latest gapps tests.

super snappy and responsive.

where's best to put python scripts for GPIO control? Any tips for resizing system partition or will just doing the usual do?
[Raspberry Pi Original Development] KonstaT:
Android doesn't have python so I guess nowhere. There's apps like Termux that have their own environment where you can install things like python. IDK if it works with recent Android versions or how it would handle the libraries you need for GPIO access. You can already control the GPIO directly using sysfs.

FAQ has a section on resizing the data partition (there's really no need to resize the system partition).
[Raspberry Pi Original Development] lordloki77:
Hey @KonstaT

First, thanks for this awesome work. Secondly, I seem to be having a problem with my setup where every time I come back the screen is black and unresponsive unless I unplug the rpi and plug it back in. I don't yet have a hardware button set up, so I'm not sure if hitting the power button would work.

I've got a touch screen attached that worked without setup and seemingly has no issues.

Any idea what the problem might be?
[Raspberry Pi Original Development] KonstaT:
You can't currently switch off the display because of http://disq.us/p/2ebq60b. This will be working again if/when there's another release.
[Raspberry Pi Original Development] vj4:
For anyone running a Geekworm x728 ups i've got this together for shutdown. The first code shuts down the PI once android has shutdown. This is needed for boot on power as without it the UPS wont shut down and cant boot on power.

config.txt:

dtoverlay=gpio-poweroff,gpiopin=13

I've also customised KonstaT shutdown script to wait for X (WAITTIMER) seconds. This is going in my car and I don't want it to always have to boot if I pop in the shop etc. I'll develop this to turn off radios etc to conserve power as I learn what I'm doing.

This is a shell that sits in /system/etc/init.d/30gpioshutdown

#!/system/bin/sh

##Edit below the amount of seconds you want to wait until shutdown in seconds
WAITTIMER=300

GPIO=6
echo $GPIO > /sys/class/gpio/export
echo in > /sys/class/gpio/gpio$GPIO/direction
echo 1 > /sys/class/gpio/gpio$GPIO/value

while [ 1 ]
do
## power is on, set timer for state change
if [ $(cat /sys/class/gpio/gpio$GPIO/value) == 0 ]; then
GPIO_CURRENT_TIME="$(date -u +%s)"
fi
## power is off check state, gpio 6 high and time now and state change timer. once higher than WAITTIMER poweroff
if [ $(cat /sys/class/gpio/gpio$GPIO/value) == 1 ] && [ $(($(date -u +%s)-$GPIO_CURRENT_TIME)) -ge $WAITTIMER ]; then

reboot -p

fi
done

Thanks for the help @KonstaT
[Raspberry Pi Original Development] megalore:
Hello,

Is it possible to implement Bluetooth HFP client profile (A2DP sink)?

The objective is to use this in car, as handsfree device, like a standard radio.

Thanks.
[Raspberry Pi Original Development] KonstaT:
Cool, maybe add some delay (sleep 1) inside the infinite loop so you're not constantly polling the sysfs.

Bluetooth app would need to be recompiled to enable this feature (https://github.com/LineageOS/androi...h/blob/lineage-18.1/res/values/config.xml#L17). No idea if it would even after that. There's no current plans to enable this feature at least.
[Raspberry Pi Original Development] SEXCAVATOR:
I can't seem to find "root" priviledges. I followed FAQ and enabled the features in Developer Settings as it pointed out. I am trying to edit "config.txt", no success. I can only access sysfs using TWRP. Can't do it under OS running. I am missing something here but what?
[Raspberry Pi Original Development] KonstaT:
Thanks for the report. I can finally close that issue. :)
[Raspberry Pi Original Development] kocerh:
Hi, i am new into this. And trying to install LineageOS 18.1 (Android 11) to mine RPI 4. I have follwed the instuctions. But i do not get the settings app! I can only go into the wifi settings. Maybe this is alrady discussed on the forum. But can someone thell me where to find the solution? Thanks and regards,
[Raspberry Pi Original Development] KonstaT:
Android TV is not intended to be used with a mouse or a touchscreen. You need to have a remote to navigate the system (USB remote, Bluetooth remote, IR remote, TV's remote using HDMI-CEC, arrow keys on your keyboard, etc).

Clicking anywhere in the settings with a mouse selects the first option (as it's somehow already 'selected').
[Raspberry Pi Original Development] rabbited:
I know you aren't planning to do many (or any?) more releases of LOS18, but I do want to say that it is working very well on the CM4 while LOS19 is not yet. For those of us interested in the CM4 to reduce overall size of the device, being able to ditch the HDMI dummy plug is huge and if there is a way to achieve this feature on LOS18, that would be a huge help in the interim until LOS19 is more functional with CM4.
[Raspberry Pi Original Development] KonstaT:
You can copy hwcomposer.drm.so (one in both /vendor/lib64/hw/ and /vendor/lib/hw/) from the latest LineageOS 19 build.

Dual-HDMI doesn't work with KMS driver in 5.4 kernel but headless mode works fine.
[Raspberry Pi Original Development] denbon:
Hi Konsta. Tell me if there is a solution at the moment with a non-working Bluetooth, when you turn on the GPS via UART
[Raspberry Pi Original Development] dzingreen:
First just to thank you on your great work :)

Installation is well explained and everything is working OK.

There is just one annoying thing regarding switching audio source.

As I have HifiBerry card and sometime I want to listen music using my old stereo amplifier I need to to go to Settings->Raspberry Pi 4 Settings->Audio to change it to whether HiFiBerry, HDMI or 3.5mm

My questions are:

1. Is it possible that audio output goes to both audio lines (HDMI and HiFiBerry)?

2. Is there any way to put shortcuts of setting on the Home Screen (shortcut to turn on HDMI output or HiFiBerry output)

Tnx
[Raspberry Pi Original Development] KonstaT:
There's https://xdaforums.com/t/dev-rom-uno...droid-11-for-raspberry-pi-4-b.4212945/page-20 but I'm not sure if that still works with the latest builds (switched to another bluetooth implementation in 20211011 build).

1. No, current audio HAL implementation can open one ALSA device at a time.

2. No shortcut to the setting option but you could add a shortcut to script, etc that does what the setting essentially does ('setprop persist.audio.pcm.card {ALSA device number}', 0 = HDMI, 2 = DAC).
[Raspberry Pi Original Development] dzingreen:
Any Hint how to do that? Or just what to Google? :)

How to put shortcut on HomeScreen of Android TV?

Tnx again
[Raspberry Pi Original Development] KonstaT:
Tasker(-like) and terminal applications should have options to add shortcuts like that.

You can't add any widgets/shortcuts with Android TV launcher. Maybe if you install some third party launcher first.
[Raspberry Pi Original Development] Sinnedan:
Raspberry Pi Model B 4GB, KK 18.1 ATV

Hi,

I had already asked some time ago and there was no solution!

Therefore I would like to ask again currently:

Is there a tutorial how Kodi or VLC can play video files from an external USB hard drive?

Cheers
[Raspberry Pi Original Development] KonstaT:
Then it was probably also discussed before. Apps having limited access to external storage is by design in Android. You would need to ask the app developers to update their apps to use more recent storage APIs. VLC/Kodi/etc access to external storage has been discussed e.g. https://xdaforums.com/t/dev-rom-uno...raspberry-pi-4-b.4139059/page-5#post-83816985