yashsingh1/xdaforums huggingface dataset:
[Raspberry Pi Original Development] anton2k:
Thanks for getting back to me, whilst I get your point about composit being an old technology, it is still used in many applications, car sterios for example of retro projects. I would be interested to see if I can get it working my self, the fact that it's an available output on every pi today tells you that it's still a very much used video output for allot of folk, would love to see it on lineage.

For the tv tuners, they will work as long as I am using the correct apps that support the hardware?

Thanks again
[Raspberry Pi Original Development] KonstaT:
I don't see any reason why LineageOS 19 build wouldn't boot if LineageOS 18 build does. Most likely just something went wrong at your flashing the image, etc.

There's been some reports of the opposite as there's apparently a new Pi 4 hardware revision which requires newer boot firmware than what is included in my LineageOS 18 builds.

It still would be pretty terrible as the resolution is about what we had on Android devices ~10 years ago (can say the same about the official 7" display). You would need to ask Roman who is maintaining mainline drm_hwcomposer if supporting the composite connector is in the scope of that project.

I don't have any TV tuner hardware so I wouldn't know. You would need to ask the developers of those apps.
[Raspberry Pi Original Development] maraukk0:
Hello!

I can´t get this waveshare 7" 1080p touchsreen "link" working. I have added those lines in my config.txt that waveshare wiki shows, but screen stays black.

This is my config.txt:

# Kernel
arm_64bit=1
kernel=Image

# Ramdisk
gpio=21=ip,pu
[gpio21=1]
initramfs ramdisk.img followkernel
[gpio21=0]
initramfs ramdisk-recovery.img followkernel
[all]

# Audio
dtparam=audio=on

# Audio DAC
#dtoverlay=hifiberry-dacplus

# Boot device
#dtoverlay=android-sdcard
dtoverlay=android-usb

# Camera
camera_auto_detect=1
start_x=1

# Display
[HDMI:0]
[HDMI:1]
hdmi_force_hotplug=1
hdmi_drive=2
hdmi_group=1
hdmi_mode=4
disable_overscan=1
[all]

# Graphics acceleration
[gpio21=1]
dtoverlay=vc4-kms-v3d
#dtoverlay=vc4-kms-dsi-7inch
dtoverlay=cma,cma-384
[all]

# I2C
dtparam=i2c_arm=on

# I2S
#dtparam=i2s=on

# IR
#dtoverlay=gpio-ir,gpio_pin=18

# Keys
#dtoverlay=gpio-key,gpio=21,keycode=116,label="POWER"
#dtoverlay=gpio-key,gpio=26,keycode=115,label="VOLUME_UP"
#dtoverlay=gpio-key,gpio=20,keycode=114,label="VOLUME_DOWN"

# Overclock
over_voltage=0
arm_freq=1500

# RTC
#dtoverlay=i2c-rtc,ds3231

# Sensors
#dtoverlay=android-i2c-sensor,mpu6050

# Serial console
enable_uart=1

# SPI
dtparam=spi=on

# Touchscreen
#dtoverlay=ads7846,cs=1,penirq=25,penirq_pull=2,speed=50000,keep_vref_on=0,swapxy=0,pmax=255,xohms=150,xmin=200,xmax=3900,ymin=200,ymax=3900
#dtoverlay=goodix
dtoverlay=rpi-backlight
#dtoverlay=edt-ft5406

# USB-C
dtoverlay=dwc2,dr_mode=peripheral
[cm4]
dtoverlay=dwc2,dr_mode=host
[all]

# V4L2
#dtoverlay=rpivid-v4l2

max_framebuffer_height=1920
max_usb_current=1
hdmi_group=2
hdmi_mode=87
hdmi_timings=1080 0 112 16 160 1920 0 4 10 10 0 0 0 60 0 140000000 3
extra_transpose_buffer=2
gpu_mem=512
[Raspberry Pi Original Development] KonstaT:
hdmi_* options in config.txt have no effect with KMS driver used with hw accelerated graphics on Android builds (also Raspberry Pi OS Bullseye has moved to using KMS by default). Please read the FAQ section about issues with display.

If your display's native resolution is 1080x1920 that's also what you should set in /boot/resolution.txt. This has at least worked with the portrait 5.5" displays.
[Raspberry Pi Original Development] maraukk0:
I've read FAQ, reso.txt is 1080x1920
[Raspberry Pi Original Development] KonstaT:
Did you try this with clean installation without any modifications to confix.txt? Did you try just removing resolution.txt as in the FAQ? Does that display work with Pi OS Bullseye (KMS)?

You need to use a display that reports resolutions it supports via EDID. One of the supported resolutions is selected using /boot/resolution.txt. If your display doesn't report any EDID one last resort is to create a kernel that includes custom EDID firmware for your display.
[Raspberry Pi Original Development] maraukk0:
Yes I tried without mods to config.txt. I haven't tried removing resolution.txt. I haven't tried with Pi OS, but I tried with win10 laptop, and screen is working.

How I know if my screen reports EDID or not?
[Raspberry Pi Original Development] KonstaT:
Did you actually change resolution.txt to '1080x1920' (it's '1920x1080' by default)?

On Raspberry Pi OS https://www.raspberrypi.com/documen...ration.html#what-modes-does-my-device-support

You can also 'cat /sys/devices/platform/gpu/drm/card0/card0-HDMI-A-1/modes' on Android as well (with display connected to the primary HDMI0 port).
[Raspberry Pi Original Development] maraukk0:
Okay thanks.

I'm actually not sure which way numbers are in resolution.txt. I chech later today, when I go home.
[Raspberry Pi Original Development] maraukk0:
I have modified resolution.txt several times, because I have used few different displays.
[Raspberry Pi Original Development] maraukk0:
My resolution.txt was 1920x1080. I deleted it and restored config.txt to original, didn´t work. I installed Monitor Asset Manager to my laptop and this is what it shows about that display:

Monitor
Model name............... WaveShare
Manufacturer............. HOT
Plug and Play ID......... HOT4F4C
Serial number............ 1
Manufacture date......... 2019, ISO week 31
Filter driver............ None
-------------------------
EDID revision............ 1.3
Input signal type........ Digital
Color bit depth.......... Undefined
Display type............. RGB color
Screen size.............. 180 x 270 mm (12,8 in)
Power management......... Not supported
Extension blocs.......... 1 (CEA/CTA-EXT)
-------------------------
DDC/CI................... Not supported

Color characteristics
Default color space...... Non-sRGB
Display gamma............ 2,20
Red chromaticity......... Rx 0,597 - Ry 0,343
Green chromaticity....... Gx 0,316 - Gy 0,566
Blue chromaticity........ Bx 0,153 - By 0,131
White point (default).... Wx 0,313 - Wy 0,329
Additional descriptors... None

Timing characteristics
Range limits............. Not available
GTF standard............. Not supported
Additional descriptors... None
Preferred timing......... Yes
Native/preferred timing.. 1080x1920p at 61Hz
Modeline............... "1080x1920" 150,000 1080 1192 1208 1240 1920 1952 1962 1972 +hsync +vsync

Standard timings supported

EIA/CEA/CTA-861 Information
Revision number.......... 3
IT underscan............. Not supported
Basic audio.............. Supported
YCbCr 4:4:4.............. Supported
YCbCr 4:2:2.............. Supported
Native formats........... 4
Detailed timing #1....... 1080x1920p at 61Hz
Modeline............... "1080x1920" 150,000 1080 1192 1208 1240 1920 1952 1962 1972 +hsync +vsync

CE video identifiers (VICs) - timing/formats supported
"1080x1920" 150,000 1080 1192 1208 1240 1920 1952 1962 1972 +hsync +vsync
"1080x1920" 150,000 1080 1192 1208 1240 1920 1952 1962 1972 +hsync +vsync
"1080x1920" 150,000 1080 1192 1208 1240 1920 1952 1962 1972 +hsync +vsync
"1080x1920" 150,000 1080 1192 1208 1240 1920 1952 1962 1972 +hsync +vsync
"1080x1920" 150,000 1080 1192 1208 1240 1920 1952 1962 1972 +hsync +vsync
"1080x1920" 150,000 1080 1192 1208 1240 1920 1952 1962 1972 +hsync +vsync
"1080x1920" 150,000 1080 1192 1208 1240 1920 1952 1962 1972 +hsync +vsync
NB: NTSC refresh rate = (Hz*1000)/1001

CE audio data (formats supported)
LPCM 2-channel, 16-bit at 32/44/48 kHz

CE speaker allocation data
Channel configuration.... 2.0
Front left/right......... Yes
Front LFE................ No
Front center............. No
Rear left/right.......... No
Rear center.............. No
Front left/right center.. No
Rear left/right center... No
Rear LFE................. No

CE vendor specific data (VSDB)
IEEE registration number. 0x000C03
CEC physical address..... 1.0.0.0
Maximum TMDS clock....... 165MHz

Report information
Date generated........... 2.2.2022
Software revision........ 2.91.0.1043
Data source.............. Real-time 0x0092
Operating system......... 10.0.19044.2
[Raspberry Pi Original Development] KonstaT:
And...

1920x1080 = landscape , 1080x1920 = portrait - these are two different things.
[Raspberry Pi Original Development] maraukk0:
Don't work with resolution.txt 1080x1920
[Raspberry Pi Original Development] KonstaT:
Still going in the same circle.Then your display likely doesn't report resolutions it supports via EDID.

You would need to ask Waveshare for support i.e. how to use that display with the latest Raspberry Pi OS Bullseye with KMS as I doubt it works there either.
[Raspberry Pi Original Development] maraukk0:
Did you read that wiki site about that screen? There are such instructions:
[Raspberry Pi Original Development] KonstaT:
Have you read me replies?

Raspberry Pi OS Bullseye uses KMS vs. fake/firmware KMS (FKMS) used with older versions.
[Raspberry Pi Original Development] maraukk0:
Yes, I have read. But I don't speak native english, so I may misunderstand something. And I'm not very technical guy, so many things and terms really doesn't mean anything to me (i.e KMS vs FKMS)

So, you mean, that those instructions in waveshare wiki for rpi os, does not work anymore with latest version of Rpi os? Yes, that is what you said earlier. I must try that.
[Raspberry Pi Original Development] risant:
no fix yet android 12 usb external dac?
[Raspberry Pi Original Development] maraukk0:
Screen works perfectly with bullseye.
[Raspberry Pi Original Development] KonstaT:
No logcat yet?

Out-of-the-box without any changes to config.txt (i.e. you haven't switched to FKMS)? In that case I'd expect it to work on Android as well (at least with the right modification to /boot/resolution.txt).

If it doesn't for some reason there's not much you can do about that. If you're familiar with compiling kernels and EDID firmwares you could try adding one for your display. I don't have the hardware so I'm not going to bother with that.
[Raspberry Pi Original Development] maraukk0:
I have added those lines in config.txt that are in wiki. No more modifications. I don't know what those lines do.
[Raspberry Pi Original Development] KonstaT:
Nothing if you're using KMS (dtoverlay=vc4-kms-v3d).
[Raspberry Pi Original Development] maraukk0:
Removed those lines and screen works still
[Raspberry Pi Original Development] maraukk0:
It took little longer to show anything, and touch feels little unaccurate, but it works
[Raspberry Pi Original Development] Spielmops:
I have two identical SD cards with the same operating system for my Raspberry Pi 4b: LineageOS 19. One card has the system version from 11/4/2021 and the second the version from 01/14/2022. Both Androids are set up the same and the settings are essentially the same. It's always the same Pi and the same monitor. But with the new version there are dropouts in the sound with HDMI. On average every 30 seconds for 3 seconds. Hardware decoding is turned off, which doesn't really work.

What could be the cause for this?

Spielmops
[Raspberry Pi Original Development] KonstaT:
I'm aware HDMI audio is not exactly great with 5.10 kernel but I can't reproduce such behavior either (see http://disq.us/p/2lgvcmt). If you find this to be too big of an issue you can use builds with 5.4 kernel.
[Raspberry Pi Original Development] Spielmops:
No Problem, I will use the older version. I only wanted to give feedback.

One funny thing: could not change anything with the Trebuchet-launcher. I worked hard! Until yesterday, when I tried the switch "lock statcreen": this switch works the other way round ...

Spielmops
[Raspberry Pi Original Development] KonstaT:
Already fixed upstream.
[Raspberry Pi Original Development] Spielmops:
HDMI-Dropouts? Or Lock of Trebuchet?
[Raspberry Pi Original Development] KonstaT:
Maybe the quoted comment with a link to the actual fix would give some clue?

Nothing Raspberry Pi specific issues will be fixed LineageOS upstream as it has nothing to do with the Raspberry Pi device specific implementation.
[Raspberry Pi Original Development] Spielmops:
Ok, I got it now.

Is it possible to bring compass-modules like GY-271 or MPU9265 get working? Entry in config.txt?

Spielmops
[Raspberry Pi Original Development] KonstaT:
There is already support for LSM303DLHC magnetometer sensor (=compass).

Adding support for new sensors has been discussed e.g. at https://github.com/lineage-rpi/android_kernel_brcm_rpi/issues/28.
[Raspberry Pi Original Development] rabbited:
I'm trying to experiment with pcie boot and was wondering if there is an option to set "CONFIG_NVMEM_RMEM=m" (to give pcie bootloader access) in the 5.10 kernel. It may only be available after 5.12.
[Raspberry Pi Original Development] KonstaT:
https://github.com/lineage-rpi/android_kernel_brcm_rpi/blob/lineage-19.0/arch/arm64/configs/lineageos_rpi4_defconfig#L5725

I'm not building any drivers as modules so just build the driver into the kernel instead (=y).

There's only support for booting from sdcard (/dev/block/mmcblk0*) and usb (/dev/block/sda*). I assume PCIe would be something else (/dev/block/nvme0n1*). You would need to make some pretty drastic changes to Android fstab to make this work (not possible to use the dtoverlay that is used for sdcard/usb booting due to those device names being hardcoded in init). TWRP is another story as well.
[Raspberry Pi Original Development] KonstaT:
New build. Also available as OTA package. Please see 'how to install' for more details. I still didn't push this through the built-in Updater app but might after a while if no issues are reported flashing it manually. There's also initial multi-display support. If you want to try the Android desktop mode on the secondary display, enable 'Enable freeform windows' & 'Force desktop mode' under Developer options.

LineageOS 19 (Android 12L)

for Raspberry Pi 4

konstakang.com

-also available as OTA package

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

-update to Mesa 21.3.6

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

-Android security patch level: 5 February 2022 (merged)
[Raspberry Pi Original Development] chjanson:
I tried this version on RPI4:

1. Confirmative that response is much better than rpi3. Mouse driver is NOT good enough, but OK for a testing procedure like this. Ideally, there should be a way for this version to autodetect the HDMI screen resolution, but I found the solution in your FAQ. My HDMI connected TV is 4k (3840x...)

2. The DAC that houses the RPI4 (audiophonics evo sabre) has a remote, but as it seems, it is not compliant with GPIO18. I am looking into that. It could be I need this to work to finish this test because the DAC probably relies on that remote to switch input etc. I have just mounted it (a DIY version), so still a little ignorant and AudioPhonics user manual could be more clear. If I am lucky I can do that switch using another opsys, and hope that the setting (to i2s) is persistent in the DAC. Dont know yet.

3. The native LineageOs Music player does not find music I put on the SD card. Seems as it does not survey the disk for music like we are used to on a normal Android? Is there a setting to make that happen? It says "connect a pc to usb to copy music", but there are no further instructions so I am stuck on that one.

4. There is no way to install Gapps yet. It means I cannot install other music players, like e.g. Tidal. Other app playstore alternatives are mentioned in your FAQ, but looks like an investigation to make it happen?

In consequence, I am at the moment not able to verify the new AudioPhonics DAC settings. I hope this will evidentally work, because it will be a very interesting solution to use android (in an embedded variant that does not noise down the system with the normal Google play activities etc). The reason would be ease of install and more importantly, to have the various mediaplayers available side by side in a GUI. Volumio, moodAudio, roon, UAPP, etc are examples on mediaplayers that are fighting for attention in the RPI market. To have them all, would make Android a serious alternative for this community. I also see that Magisk has a way of enhancing the normal Android USB audio limitations. So Magisk with a script for that that autoruns, would be highly interesting, I think.

Worst case, I must wait to test this further until you have GAPP working.

This as a prelimenary update. Your comments welcome.
[Raspberry Pi Original Development] KonstaT:
1. Well, it already detects screen resolution as everything depends on what the connected display reports as supported (and these resolutions are also listed in Settings -> System -> Raspberry Pi settings -> Display resolution). 1080p resolution is forced by default to provide consistent UX because using different resolutions also requires using different screen densities, etc. I certainly wouldn't recommend using 4k resolution as performance is obviously going to be degraded (there's four times more pixels to render than on 1080p).

There's nothing wrong/to be done with mouse drivers, it works just as on Linux in general.

2. Did you do as instructed in https://xdaforums.com/t/dev-rom-uno...raspberry-pi-4-b.4356891/page-7#post-86255361? Is the DAC recognized as an ALSA device ('cat /proc/asound/cards' or 'dmesg' output after booting the device)? Remote controller is totally irrelevant at this point.

3. Works fine for me. You might need to reboot your device to invoke the media scanner (there also used to be an option for this in developer options but it looks like it's gone in recent Android versions). It's never been instant in any case.

4. Please read the FAQ on how to install gapps. Yes, there's alternative gapps packages you can use though OpenGApps are not available yet. You don't need Play Store to install apps in any case. You can sideload apps from .apk files just like on any other Android device. You can do this e.g. by using the built-in file manager or 'adb install'. The same way you can also install some alternative application store (F-Droid, Aurora, etc) and use it to install other apps.
[Raspberry Pi Original Development] rabbited:
The headless feature is working very well! WiFi is working well on the CM4 but unfortunately the browser is still suffering from the same permissions issues. I assume this issue effects other apps within the system but I haven't invested too much time in Lineage 19 yet because I'm waiting for the official OpenGapps release. However, if there are any ideas or info I can provide to fix the issue in the meantime, I would be glad to help in any way I can. I know that the CM4 isn't officially supported, but I will say that it is working pretty much flawlessly on Lineage 18.1, so the issues here may be easily resolved.
[Raspberry Pi Original Development] KonstaT:
Still haven't received anything on
[Raspberry Pi Original Development] Spielmops:
Update via TWRP: Wow! Thanks a lot!
[Raspberry Pi Original Development] Lowder:
Hello! I'm trying to start up my JDI lt070me05000 panel (1200x1920) on Raspberry Pi Compute Module 4. I had success running it on official x64 os. As this panel is supported in the kernel, the only thing I did was to add

dtoverlay=vc4-kms-dsi-lt070me05000

to the /boot/config.txt file. But unfortunately, it didn't work for the first time. It was spamming HDMI audio errors in the serial console, so I added this to the config.txt

dtoverlay=vc4-kms-v3d,noaudio

and then it continued to boot up. And now the problem is that the display stays off and there are no errors (or mentions of the panel driver) in the console. Here is the console output https://paste.gg/p/anonymous/d15c160bed06482eba3a4febfb62021c

Thanks!
[Raspberry Pi Original Development] KonstaT:
CM4 is not supported as there's been some mixed reports and I don't have any hardware to test myself. Audio is expected to be an issue as CM4 doesn't have built-in audio jack (that is supposed to be used by default). It should still have HDMI audio (right?) so I don't know why disabling HDMI audio devices makes any difference. Can you provide 'dmesg' and/or 'cat /proc/asound/cards' without adding the 'noaudio' to config.txt? Android system logs are at 'logcat' which is generally much more useful that kernel logs.

Driver for your display is not enabled on the kernel (https://github.com/lineage-rpi/andr.../arm64/configs/lineageos_rpi4_defconfig#L3629) so you would need to compile the kernel with that enabled. Otherwise DSI displays should work (the official 7" one does at least). You'd need to remove/modify /boot/resolution.txt to adjust to your display's resolution as well.
[Raspberry Pi Original Development] rabbited:
I modified the init.rpi4.rc and changed permissions to 666 around December 27 without success which is when I gave up. I will try to edit the init.rpi4.rc one more time on the new build and report back.
[Raspberry Pi Original Development] rabbited:
My first step was to edit the line in init.rpi4.rc to:

chmod 0666 /sys/kernel/debug/tracing/trace_marker

Then on reboot I tested that permissions had changed on the trace_marker file:

>adb root

restarting adbd as root

>sudo adb shell ls -l /sys/kernel/tracing/trace_marker

-rw-rw-rw- 1 root root 0 1969-12-31 19:00 /sys/kernel/tracing/trace_marker

adb logcat result:

02-16 17:19:12.043 1815 1815 F DEBUG : Abort message: 'JNI FatalError called: (zygote) Failed open(/sys/kernel/tracing/trace_marker, 1): Permission denied'

Let me know if any of the steps I've performed above are incorrect. The "ls -l" command reported --w--w--w before I edited init.rpi4.rc so permissions seem to have changed successfully.
[Raspberry Pi Original Development] KonstaT:
Looks fine. IDK what's the problem with CM4 and I don't have the hardware myself.

I don't have any battery pack/UPS hardware so there's no plans to support any.

Raspberry Pi kernel doesn't suspend so your device won't enter 'deep sleep' like your regular Android device in any case.

I've provided a script that powers down the device when you connect GPIO pin to ground (https://xdaforums.com/t/dev-rom-uno...raspberry-pi-4-b.4139059/page-6#post-83822011). That flashable zip won't work with the new TWRP version that is included in the latest builds. I've also moved init.d scripts from system partition to vendor (/vendor/etc/init.d/) in LineageOS 19.
[Raspberry Pi Original Development] NonStickAtom785:
After extracting the Google TV 12 adt3 images I see some differences between aosp and lineage os roms. I have the system directory pulled from it, but from there I don't know what I should actually use for Gapps. I know that the dependencies need to match(framework, permissions, and library files. Any ideas?
[Raspberry Pi Original Development] KonstaT:
Look for existing gapps packages for example.

I haven't dealt with gapps in ages so I wouldn't know.
[Raspberry Pi Original Development] NonStickAtom785:
Yeah I ended up reverting to that. Even tried looking for existing scripts that could pull information like that. I started doing some small modification to the local gapps page. But at the moment I want to switch to the Regular non TV build and install FlameGapps.

I also want time ask if the ATV builds are built like non-atv build but with modified system apps.
[Raspberry Pi Original Development] KonstaT:
Yes, Android TV and regular tablet UI builds are built the same way but just configured for different device types (TV vs. tablet). There leanback (TV) versions of various system application, nothing is "modified" in that sense.
[Raspberry Pi Original Development] NonStickAtom785:
Ah. So it's essentially the same thing. I guess the only problem with getting Android 12L UI is that LineageOS hasn't added support yet. Android 12 in general took a giant leap in overall system design and structure.

What are the chances that Treble support might be applicable on the Raspberry? It seems counter productive to continuously rebuild full installation images for one hardware type.