yashsingh1/xdaforums huggingface dataset:
[Raspberry Pi Original Development] SuperPi911:
i git clonned all this repos with these commands

git clone https://github.com/lineage-rpi/android_device_brcm_rpi4.git -b linege-17.1 device/brcm/rpi4

git clone https://github.com/lineage-rpi/android_device_brcm_rpi4.git device/brcm/rpi4

gir clone https://github.com/lineage-rpi/android_device_brcm_rpi-common.git -b lineage-17.1 device/brcm/rpi-common

git clone https://github.com/lineage-rpi/android_device_brcm_rpi-common.git -b lineage-17.1 device/brcm/rpi-common

git clone https://github.com/lineage-rpi/android_kernel_brcm_rpi.git -b lineage-18.1 kernel/brcm/rpi

git clone https://github.com/lineage-rpi/proprietary_vendor_brcm.git - b lineage-18.1 vendor/brcm

git clone https://github.com/lineage-rpi/proprietary_vendor_brcm.git -b lineage-18.1 vendor/brcm

git clone https://github.com/lineage-rpi/android_external_drm_hwcomposer.git -b lineage-18.1 external/drm_hwcomposer

git clone https://github.com/lineage-rpi/android_external_gbm_gralloc.git -b lineage-18.1 external/gbm_gralloc

git clone https://github.com/lineage-rpi/android_external_libdrm.git -b lineage-17.1 external/libdrm

git clone https://github.com/lineage-rpi/android_external_mesa3d.git -b lineage-18.1 external/mesa3d

git clone https://github.com/lineage-rpi/android_external_minigbm.git -b lineage-18.1 external/minigbm

git clone https://github.com/lineage-rpi/android_external_ir-keytable.git -b lineage-18.1 external/ir-keytable

git clone https://github.com/lineage-rpi/android_hardware_gps.git -b lineage-18.1 hardware/gps
[Raspberry Pi Original Development] KonstaT:
There's a lineage-18.1 branch to go with the rest of the graphics stuff.

Also a recent discussion you might find useful. https://github.com/lineage-rpi/android_local_manifest/issues/14
[Raspberry Pi Original Development] Van31415:
oh, tnx

The settihg 'hdmi-force_hotplug=1' in /boot/config.txt not working
[Raspberry Pi Original Development] KonstaT:
No. hdmi_* options in config.txt don't do anything with KMS driver that is used with hw accelerated graphics on Android builds.
[Raspberry Pi Original Development] SuperPi911:
could you post the manifest on the lineage-rpi github repo for ineage os 18.1 and 19?
[Raspberry Pi Original Development] KonstaT:
Not sure what you'd do with the manifest alone (and you probably already have that part figured out anyway).

It's still under consideration if I'll make some minimal device configuration available for people who are interested in contributing to actual development work on various parts that may still need it (hw video dec/enc, camera, etc). I'm not sure if there's anything to benefit from just having a build of every AOSP based ROM if it doesn't offer anything new regarding to the hw that is working.
[Raspberry Pi Original Development] SuperPi911:
Or could you post here the git clone commands for lineage 18.1, I think I git clonned something wrong on my havoc os build
[Raspberry Pi Original Development] BAZ_:
Just wanted to say thanks for this image, I've been running this (32bit ATV version, I don't fancy reinstalling all the apps just yet!) for a few weeks now on my TV and it's been working well with my gyro mouse. I've had a few rare crashes but as a daily use it's been great!

Looking forward to getting hardware decoding, sometimes there can be a delay in audio decoding and certain 1080p+ content struggles but it's replaced LibreElec for me now. Good job!
[Raspberry Pi Original Development] rabbited:
Assuming that the going theory that ANQP/Hotspot 2.0 is the culprit causing the WiFi related bootloop, how difficult would it be to modify Lineage OS for RPi to use a specific WiFi dongle alternative?

Obviously, this may just be software related and any WiFi signal could be causing the bootloop, but assuming that it's specific to the WiFi module being used, it's easy to get a CM4 without built in WiFi. Lineage runs well over ethernet for all of my Pi's, both 4B and CM4 but causes immediate bootloop for all of them over WiFi.
[Raspberry Pi Original Development] KonstaT:
Are you saying https://github.com/lineage-rpi/android_kernel_brcm_rpi/issues/6 is still an issue with the latest Android 11/12 builds? There was some mixed reports to begin with and I haven't received any reports in a long time (at some point it was several every week). I was never able to reproduce it myself.

Generally speaking you can consider Android as an OS for embedded devices and it's not designed to support every possible hardware at the same time. It only needs to support the specific hardware you have on the device. Is it possible to make a build that supports some specific wifi hardware? Yes. Is it possible to make a build that supports every USB wifi dongle you throw at it? Likely not with any reasonable effort at least.
[Raspberry Pi Original Development] Spielmops:
In an earlier post I wrote that I had built a head unit (infotainment system) for my mobile home, i.e. a productive system (has since been published by the German magazine Make from heise.de).

My problem: it is very time-consuming to install an update because I have to restore a lot of data and settings.

To make my work easier, I have two identical 64GB SD cards. One card contains the system that is currently working. From that I make a backup of the "data" partition. Then I copy the data from / data / media (this is the internal SD card) together with the backup to a USB stick. I write the new image on the other card and change the resolution.txt. After that I have to insert the card into my device and start the system completely. Then change the settings specifically for the Raspberry Pi and then reboot and check. Then reboot again with TWRP, install the SU add-on, also the resize add-on, then copy the backup of the "data" partition and the files from / data / media to the new card. Reboot and hopefully everything will work again and I haven't made a mistake.

I wish I could install an update just as easily or almost as easily as you normally would with a smartphone and tablet.

Spielmops
[Raspberry Pi Original Development] KonstaT:
FAQ already has steps how to update from previous build without losing data. It doesn't take care of files on your 'Android's internal sdcard' (i.e. /data/media), changes you've made to files on boot partition (config.txt, resolution.txt, etc), or store the settings you've selected from Settings -> System -> Advanced settings (which also make changes to files on boot partition and /vendor/build.prop) so it's far from perfect.

I've considered creating TWRP flashable system images like on 'normal' Android devices. Because everything is structured a bit differently here it's difficult to get the Android build system to spit out such package (but surely that would be manageable with some effort). Main problem with this is that there still needs to be an image for the first time installers to create the necessary partition structure, etc on the storage device. This would mean maintaining the image in two formats which is not something I want to do (already maintaining regular tablet UI and Android TV versions so I see exponential growth in number of images to maintain). One option would be to have some base image for everyone that you write normally to sdcard that boots directly to TWRP. There you would flash a separate zip with the OS itself. This would require having a sdcard and an USB stick and I'm sure it would be way too difficult for some people.
[Raspberry Pi Original Development] Spielmops:
Would it be possible in my case to write a new version normally to another sdcard, boot to TWRP, do a backup of /system and "restore" that via USB-Stick to the working system? Are all changes within that partition? (I don't speak of an upgrade.)

Spielmops
[Raspberry Pi Original Development] KonstaT:
System partition alone is not enough so you would need to do this with boot and vendor as well. End result is exactly same no matter which way around you'd do this.
[Raspberry Pi Original Development] Spielmops:
I already thought so, that's why I haven't tried it ...

Spielmops
[Raspberry Pi Original Development] Azumimuo:
​

KonstaT,​

Is there any guide for me to get my "Sixfab 3G/4G& LTE Base HAT" and "SIM7600E or Quectel EC25" working in LineageOS 18.1 ATV?

Thank you in advance
[Raspberry Pi Original Development] mynameisnafe:
Hey LineageOS community :)

I'm trying the 26.10 build on my RPi4 4GB with the x64 pico 20211109 gapps..

I'm booting up, going through the wizard, enabling pin 21 power, enabling advanced reboot options, rebooting into twrp, flashing the x64 gapps, and then in TWRP, going to Wipe, then doing a factory reset.

When I reboot after this reset, I get to the arc-and-circle boot animation, but it goes on forever.. or at least feels like it does. I haven't been able to boot after flashing these gapps and factory resetting yet. I must be missing a step, right? Do I need to wipe more stuff? I've no user data really, I'm totally happy to scorch the earth if it gets the thing to boot.

Last time this happened to me, it was because I was installing the x86 gapps. The result of that was a bootloop into TWRP.. that isn't what happened this time.

Many thanks in advance
[Raspberry Pi Original Development] KonstaT:
It needs a separate build entirely. Android TV is meant for TVs obviously so I don't think you can get the telephony working on it anyway.

OpenGApps builds are automated untested builds and they tend to get broken sometimes. There was some report that latest pico package was recently fixed but tvstock is probably still broken. Packages from 20211021 are the latest ones I've tested working myself. You need to use the right package for the build of course (tablet UI & pico vs. Android TV & tvstock).

Correct place to report issues with gapps with appropriate logs would be https://github.com/opengapps/opengapps/issues.

There's also some related discussion going on with LineageOS folks (https://review.lineageos.org/c/LineageOS/lineage_wiki/+/318857).
[Raspberry Pi Original Development] rabbited:
Yes, definitely still an issue. I started with RPi on a CM4 and Lineage 17 was the version available at the time. I have tried all versions since then on both my CM4s and my 4B and get boot loop almost immediately. I think that one issue is that many users don't realize WiFi is the culprit without enough research, as there really isn't much time to experiment with the software or any notification to imply the source of the problem before reboot occurs. I wasn't thinking along the lines of universal WiFi dongle support but rather a test of an accessible/affordable single model that could be universally used as an alternative. Obviously, that's assuming that the WiFi module in the RPi is the issue rather than a general software issue with the Android-Rpi build.

Alternatively, if network scan could be disabled and WiFi network entered manually that may also solve the problem.
[Raspberry Pi Original Development] Sinnedan:
Hello again,

i have problems with the WLAN.

For information

My location is in Germany.

Raspberry Pi 4 Model B

lineage-18.1-20211026-UNOFFICIAL-KonstaKANG-rpi4-atv.img

SD card created with Raspberry Pi Imager v1.6.2.

1920x1080 with HDMI

WLAN works with your versions 16.0 ATV, 17.1 ATV, 19.0.

Only with 18.1 ATV no WLAN works.

I do not want to take the version 17.1 because the last update is from 2021.01.22.

With version 18.1 ATV the last update is from 2021.10.26.

https://disqus.com/home/discussion/..._android_tv_android_11_16/#comment-5556898933

I edited the raspi-config according to the defaults, but with the Raspberry Pi OS lite.

I also didn't know how to open the raspi-config with version 18.1 ATV!?!

I have also changed the WLAN channel.

It didn't help either unfortunately.

https://disqus.com/home/discussion/..._android_tv_android_11_16/#comment-5371779003

Here you suggested that one enter the command "iw reg set XX".

So with version 18.1 ATV in developer mode, I unlocked the terminal.

Then I wanted to enter "iw reg set DE", but there came the error message "command failed: Operation not permitted (-1)"!

In addition, no IP address is entered for "About the tablet".

Can anyone help me here?

I will also post an excerpt of the logfile if you want.

Cheers

Maik
[Raspberry Pi Original Development] risant:
Is there a solution for cracking distorted noise bluetooth audio?
[Raspberry Pi Original Development] KonstaT:
I really can't see any reason why wifi wouldn't work on LineageOS 18 if it works on 17/19. Also you would need to be bit more precise than "doesn't work" (doesn't turn on, doesn't connect to network, etc).

My comment on the resolution & wifi discussion you linked (http://disq.us/p/2jwm95r).

This is not Raspberry Pi OS so there is no raspi-config. Device specific settings are under Settings -> System -> Advanced settings.

You need to have root access (see FAQ) if you want to do anything remotely interesting in the shell.

There is no IP address if there is no network connection.

Workaround has always been to disable location access when setting up gapps. There's also https://xdaforums.com/t/dev-rom-uno...aspberry-pi-4-b.4212945/page-14#post-85769441

Or is this some other issues I've never heard of?
[Raspberry Pi Original Development] risant:
Is there a solution for cracking distorted noise bluetooth audio? sometimes difficult to connect to wifi..please help
[Raspberry Pi Original Development] risant:
Wifi diificult to connect... even rpi4 is near my router any solution? Bluetooth audio distorted ir crackling sound any solution? Please help
[Raspberry Pi Original Development] KonstaT:
Did you try simply rebooting your device? There's also a skip option in the wifi setup.

You don't need raspi-config to update EEPROM but you do need to use Raspberry Pi OS for this in any case.

Already replied to your "command failed: Operation not permitted (-1)". You need root access (see FAQ).

Please stop spamming if you have nothing new to add. I already replied to one of your previous post anyway.
[Raspberry Pi Original Development] misterti:
I installed 18.1 latest update to test hdmi-cec, but unfortunately it doesn't work. Not on TV version, nor on tablet version. Now, i suspect there might be a problem with hdmi cables. I have tested with direct big to small cable and a big to big cable with adapter, big to small (naturally, because pi4 has small hdmi connectors). None worked. I used the big to big cable that works on LibreElec. I tried both hdmi outputs on Pi4, both provide screen, but none has hdmi-cec functionality. Maybe something needs to be enabled in pi config?
[Raspberry Pi Original Development] KonstaT:
http://disq.us/p/2kens2y

Edit. 20211123 builds have settings option to select HDMI-CEC device for HDMI0/HDMI1.
[Raspberry Pi Original Development] KonstaT:
New builds. Add-ons have also been updated for the new TWRP so download the latest ones on those as well.

LineageOS 18.1 (Android 11)

for Raspberry Pi 4

konstakang.com

-add support for BME280/BMP280 temperature/pressure/humidity sensors

-add option to select HDMI-CEC device

-add option to show virtual volume down, volume up, and power keys on navigation bar

-add option for old TCP-based ADB over network

-show IP address and port for ADB/SSH/VNC options

-fix resizing data partition that broke with previous build

-update to TWRP 3.6.0_11-0-KonstaKANG

-update to Mesa 21.3.0

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

-Android security patch level: 5 November 2021 (merged)

---

LineageOS 18.1 Android TV (Android 11)

for Raspberry Pi 4

konstakang.com

-add support for BME280/BMP280 temperature/pressure/humidity sensors

-add option to select HDMI-CEC device

-show IP address and port for SSH/VNC options

-setup wizard improvements for TV devices (merged)

-fix resizing data partition that broke with previous build

-update to TWRP 3.6.0_11-0-KonstaKANG

-update to Mesa 21.3.0

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

-Android security patch level: 5 November 2021 (merged)
[Raspberry Pi Original Development] The4anoni:
Is there any hope for HW Video decoding support?
[Raspberry Pi Original Development] KonstaT:
Not on this build. It requires using newer stuff that are not available for Android 11.

Latest LineageOS 19 (Android 12) build already has proof of concept level support for H.264 hardware video decoding. It's 1080p only due to hardcoded buffer sizes and something gets still messed up somewhere in the pipeline because colors are not correct. Still proves the point that it can work but it's still going to take a lot of time and work (not just on this hardware but in general).
[Raspberry Pi Original Development] kaveras:
Hi !

I've came across very annoying 'bugs'

- 1st accurses in some applications that are using 'fullscreen' feature I believe. While starting for example gmaps screen turns black for ~1s, same thing is happening while going back to main screen. It happens every time while using yt,gmap. Please see videos in attachents to better understand this problem.

- 2nd playing music via bluetooth is not working very good, there are many stutters, everything works fine with 3.5jack playback.

Besides of that everything is working flawlessly.
[Raspberry Pi Original Development] KonstaT:
-Recent Android versions can request to use different display refresh rate so this depends on your display. You can force a refresh rate from Settings -> System -> Raspberry Pi settings -> Display resolution (set e.g. 1920x1080@60).

-Already discussed even on this topic many times. Only happens with gapps installed and if you've enabled location access during the gapps setup. Google location services scan nearby bluetooth devices to determine the device location which doesn't work great when your using bluetooth audio at the same time. There's also https://xdaforums.com/t/dev-rom-uno...aspberry-pi-4-b.4212945/page-14#post-85769441
[Raspberry Pi Original Development] kaveras:
- Works like a charm :) edited resolution txt file in boot and set 720p@60.
[Raspberry Pi Original Development] kaveras:
One more annoying thing that I discovered today is that SOMETIMES touchscreen bugs and reads that I keep touching it, which results strange behaviours, after disconnecting and connecting touchscreen (usb) it works fine. See attachments for video.
[Raspberry Pi Original Development] KonstaT:
Logs please as videos or screenshots don't provide anything useful unless we're talking about some visual object.

Also many other things can affect like are you using USB 2.0 or 3.0 port? Are you booting from an USB device and so on?
[Raspberry Pi Original Development] Azumimuo:
KonstaT,

I'm already switch to LineageOS 18.1 from LineageOS 18.1 ATV. Then, by following guide from sixfab website to try to setup my "Sixfab 4G/LTE Base Hat" with "Quectel EC25-E LTE Module" which recently bought separately.

Are there any step or step for me to follow?

my setup consist of Raspberry Pi 4B, Allo Boss DAC Hat, Geekworm x728 UPS Hat and Sixfab 4G/LTE Base Hat.

Thank you in advance
[Raspberry Pi Original Development] KonstaT:
No, adding support for a specific modem requires building the whole Android from source. Quectel has the drivers and documentation available for their hardware on their website.
[Raspberry Pi Original Development] tholau:
Hi, I'm thinking about buying the DeskPi Pro v2 as it comes with SSD support, IR support, and a power button.

But these features can only be gained by using DeskPi's drivers (https://github.com/DeskPi-Team/deskpi).

Do you think it might be possible to transfer/adopt the divers also to be used with your Android TV for PBPi 4?
[Raspberry Pi Original Development] KonstaT:
SSD and IR receiver should work pretty much as is. Fan and power button would need some work to get them working.

You can't use the drivers they've made available for regular Linux distros with Android so you'd need to create your own implementation.
[Raspberry Pi Original Development] ndkone:
I had just tried this build, 18.1 on my pi 4 with Gapp for the TV setup. All worked but the F1-3, 11-12 key does not work. I am using a wireless Microsoft keyboard : Microsoft Wireless All-In-One Media Keyboard.

Anyone have this issue?
[Raspberry Pi Original Development] KonstaT:
You would need to be more precise what you mean by not working.

F1-F5 & F11-F12 keys are mapped to android buttons so they are not supposed to work as function keys (please read the FAQ).
[Raspberry Pi Original Development] tholau:
Ah, okay.

Well, I'm not skilled in these things (like creating drivers, etc.). I hoped that you might have an idea or even an approach on how to solve this.

But with this in mind I'll refrain from buying this case.
[Raspberry Pi Original Development] KonstaT:
Well, I don't have the hardware so it's not for me to do (why? and I wouldn't have anything to test so it would be also practically impossible).

It's for the hardware manufacturer to support (as they support other OS as well) or someone who has the hardware and wants to use it with Android.
[Raspberry Pi Original Development] ndkone:
My bad, I was referring to F1-F5 & F11-12 mapped to android remote keys but they are not working on my setup.

For example F2 is back and pressing F2 does nothing. F11-12 are volume control and that does not do anything either.

Is there something I can check why the mapping is not working?

I have installed the lineage 18.1-20211123 KonstaKANG-rpi4-atv. (installing Gapps or not have no difference).

Thanks for your help in advance.
[Raspberry Pi Original Development] KonstaT:
Isn't that basically just an USB keyboard? Do you need to also press some other buttons to get to the F-keys? I really don't see any reason why that wouldn't work. Only the home, back, and volume keys will do something with Android TV and it also of course depends where you are in the UI.

There's 'getevent' tool you can run in rooted shell the see exactly what (key)events you get from input devices.
[Raspberry Pi Original Development] Homewrecker:
For some reason I cannot get my Google TV remote to pair on my RPi 4.

When I start searching for accessories, the Google TV remote is detected but when I click on it to pair, after a few seconds it says 'Couldn't pair'.

Already did a factory reset on the remote but no success.

Remote still works with my Google TV dongle.

Any ideas on how I can fix/troubleshoot this?
[Raspberry Pi Original Development] KonstaT:
There's been similar reports with pairing some Android TV remotes after installing gapps. Pairing the remote works without gapps, though.

You can test and confirm if that is the case, grab a logcat, and contribute to discussion at https://github.com/opengapps/opengapps/issues/915.
[Raspberry Pi Original Development] ndkone:
Yeah, that is strange.

I tested some more. A WIRED keyboard works.

But when I use a WIRELESS keyboard, those F-keys do not work.

I am going to get a different media keyboard, most likely logitech instead.

During this process, I found two areas that I cannot update on the settings:

1) I cannot change the name of the device to a custom name. I can pick any of the existing name, but I cannot change to say PiTV for example. Anything custom, the change are in cycle keep asking me to change it but never save what I entered.

2) I setup a WIFI SSID at the initial setup. Afterward, I tried to change it or add another SSID. It would not like me add one. It kept going from enter the name of the wifi and enter key and enter it again in loops. The wifi SSID is hidden if that make a difference.
[Raspberry Pi Original Development] KonstaT:
Shouldn't make any difference if USB keyboard is wired or wireless (works just fine with my wireless USB keyboards). Bluetooth keyboard might different depending on the device.

Tested and I can reproduce both those issues. Added to my list of broken settings options in Android TV. These are common issues with Android TV in general, not something to do with my device specific implementation so not necessarily in my territory.