[DEV] LineageOS 20 (Android 13) for Raspberry Pi 4 B

[werimail]

Here the Logcat...
Greetings Werimail

[Konsta]

@werimail
Thanks for the logs.

I don't see anything wrong with the audio in that log. Yes, I can reproduce these errors if I select audio to HDMI1 while only having display connected in HDMI0 (or vice versa or running headless without any display connected).

Code: Select all

I audio_hw_rpi_hdmi: start_output_stream: default:CARD=vc4hdmi1
E audio_hw_rpi_hdmi: cannot open pcm_out driver: Operation not permitted
E audio_hw_rpi_hdmi: out_write err: No such device

I guess this could cause some slowing down since whenever sound is played, audio HAL tries to constantly open a device that is not available. Easy solution would be simply not to set HDMI audio to a port where you don't have any display connected.

My builds currently have four different H.264 decoders (V4L2 hardware decoder using AOSP v4l2_codec2, V4L2 hardware decoder using FFmpeg h264_v4l2m2m, FFmpeg's software decoder, and Android's native software decoder). Logs indicate that both hardware decoders have some issue with the H.264 buffers with that app (pixel format, buffer size).

Code: Select all

03-30 13:45:12.307   245  3339 E V4L2Device: (CAPTURE_MPLANE)Failed to set format (format_fourcc=0x3231564e)
03-30 13:45:12.307   245  3339 E V4L2Decoder: Failed to find supported pixel format
03-30 13:45:12.307   245  3339 I V4L2Decoder: Set state Decoding => Error
03-30 13:45:12.307   245  3339 E V4L2DecodeComponent: reportError(error=14)
03-30 13:45:12.307  2774  3330 D CCodec  : Component "c2.v4l2.avc.decoder" returned error: 0xe

Code: Select all

03-30 13:28:42.672   248  3074 I FFMPEG  : [h264_v4l2m2m @ 0xb400007d21106290] --- capture VIDIOC_QBUF: index 0 FAIL err 22 (Invalid argument)
01-01 01:02:19.459     0     0 E         : bcm2835-codec bcm2835-codec: bcm2835_codec_buf_prepare data will not fit into plane (55296 < 884736)

[werimail]

@werimail
Thanks for the logs.

I don't see anything wrong with the audio in that log. Yes, I can reproduce these errors if I select audio to HDMI1 while only having display connected in HDMI0 (or vice versa or running headless without any display connected).

Code: Select all

I audio_hw_rpi_hdmi: start_output_stream: default:CARD=vc4hdmi1
E audio_hw_rpi_hdmi: cannot open pcm_out driver: Operation not permitted
E audio_hw_rpi_hdmi: out_write err: No such device

I guess this could cause some slowing down since whenever sound is played, audio HAL tries to constantly open a device that is not available. Easy solution would be simply not to set HDMI audio to a port where you don't have any display connected.

Hi @Konsta, thanks for your analysis. I now believe that it is no longer an audio problem. I frequently get the logcat error:

Code: Select all

[31m03-31 11:23:20.032   417   533 E WifiVendorHal: getWifiLinkLayerStats_1_6_Internal(l.1199) failed {.code = ERROR_NOT_SUPPORTED, .description = }[0m
[32m03-31 11:23:23.046   248   248 I WifiHAL : Creating message to get link statistics; iface = 8[0m
[34m03-31 11:23:23.047   248   248 D WifiHAL : error code -95 mapped to -3[0m

That sounds more like a network failure, doesn't it?
Greetings Werimail

[Konsta]

Hi @Konsta, thanks for your analysis. I now believe that it is no longer an audio problem. I frequently get the logcat error:

Code: Select all

[31m03-31 11:23:20.032   417   533 E WifiVendorHal: getWifiLinkLayerStats_1_6_Internal(l.1199) failed {.code = ERROR_NOT_SUPPORTED, .description = }[0m
[32m03-31 11:23:23.046   248   248 I WifiHAL : Creating message to get link statistics; iface = 8[0m
[34m03-31 11:23:23.047   248   248 D WifiHAL : error code -95 mapped to -3[0m

That sounds more like a network failure, doesn't it?
Greetings Werimail

No, not everything you see in the logs tagged as "error" is an actual error or cause any issue. Broadcom wifi vendor HAL doesn't implement link layer stats (at least yet) and those messages have been present in the logs for past couple of Android version at least. This has been discussed https://github.com/raspberry-vanilla/an ... /issues/12

It's most definitely something related to audio if you can reproduce this by just switching audio output device between 3.5mm jack and HDMI. As I already commented above, I can see this being a problem if you've selected HDMI audio output to a port where you don't have any display connected. Are you sure this isn't the case?

[werimail]

Yes @Konsta, I currently only use the Raspi on a Samsung LED TV. The audio output via HDMI also works without problems (the sound is clear). Only the video is jerky and stuttering throughout. Even a restart hasn't helped so far. Does the latest logcat show anything along those lines?
Greetings Werimail

[Konsta]

Yes @Konsta, I currently only use the Raspi on a Samsung LED TV. The audio output via HDMI also works without problems (the sound is clear). Only the video is jerky and stuttering throughout. Even a restart hasn't helped so far. Does the latest logcat show anything along those lines?
Greetings Werimail

And if you change the audio output to 3.5mm jack (and reboot the device) there is no longer any video stuttering?

[werimail]

Yes @Konsta, I currently only use the Raspi on a Samsung LED TV. The audio output via HDMI also works without problems (the sound is clear). Only the video is jerky and stuttering throughout. Even a restart hasn't helped so far. Does the latest logcat show anything along those lines?
Greetings Werimail

And if you change the audio output to 3.5mm jack (and reboot the device) there is no longer any video stuttering?

Yes, that's how it is @Konsta, as soon as I switch to "3.5mm Jack" the video runs without jerking and stuttering (but also without any sound )
Greetings Werimail

[Konsta]

Yes, that's how it is @Konsta, as soon as I switch to "3.5mm Jack" the video runs without jerking and stuttering (but also without any sound )
Greetings Werimail

Ok. I can't reproduce that, I haven't received any other reports either, and I can't see anything in the logs that would indicate such issue.

Could be related to the fact that you've switched to H.264 software decoding (you could also test the Android's native sw decoder vs. FFmpeg sw decoder) and the IEC958 subframe conversion for HDMI audio being on the CPU, too. You could try if overclocking the CPU helps, at least increase the clocks to 1.8GHz that should be the default for Pi 400 in the first place.

[werimail]

Yes, that's how it is @Konsta, as soon as I switch to "3.5mm Jack" the video runs without jerking and stuttering (but also without any sound )
Greetings Werimail

Ok. I can't reproduce that, I haven't received any other reports either, and I can't see anything in the logs that would indicate such issue.

Could be related to the fact that you've switched to H.264 software decoding (you could also test the Android's native sw decoder vs. FFmpeg sw decoder) and the IEC958 subframe conversion for HDMI audio being on the CPU, too. You could try if overclocking the CPU helps, at least increase the clocks to 1.8GHz that should be the default for Pi 400 in the first place.

Hello @Konsta Unfortunately, using Android's native sw decoder and overclocking the CPU (frequency = 1800 MHz) did not have any effect. The video is still stuttering and jerking. Merely changing the audio device ("3.5mm Jack" setting) leads to the desired result, but no audio output. Apparently the changes to the HDMI audio output since the last version from 03/21/2023 are to blame, since there have never been any problems with the HDMI audio with my configuration to date.
At the moment I only see one solution for me: I stay with the version from 02/14/2023 without implement audio HAL or there is an option to switch back to alsa loopback for HDMI audio.
Greetings Werimail

[Konsta]

New builds.

https://konstakang.com/devices/rpi4/LineageOS20/
https://konstakang.com/devices/rpi4/LineageOS20-ATV/

-add support for AV1 software video decoding using FFmpeg and dav1d
-update to FFmpeg 6.0
-update to libcamera master/v0.0.5
-update to alsa-lib/alsa-utils v1.2.9
-update to Mesa 23.0.3
-update to Linux 5.15.106 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
-Android security patch level: 5 May 2023 (merged)

[ArSm]

Hi,

is there any way that LineageOS RP4 is detecting a USB DAC? I´ve already tried a lot of things, but in the meantime I have reached a dead end.

Thanks for your help!

ArSm

[Konsta]

Hi,

is there any way that LineageOS RP4 is detecting a USB DAC? I´ve already tried a lot of things, but in the meantime I have reached a dead end.

Thanks for your help!

ArSm

USB soundcards/DACs should work by simply pluggin in the hardware. There's been some reports of issues with some USB DACs since Android 12 but I'm not able to reproduce any issue with my USB soundcard at least. Please post appropriate logs ('dmesg', 'logcat', 'cat /proc/asound/cards') if you're having issues with this.

[ArSm]

Hi Konsta!
Thank you so much for your help! I appreciate it very much. In the meantime, my USB DAC is up and running. Now a new problem has arisen. When playing audio, whether playing video or audio only, there is a crackling sound. When the playback is finished, nothing more can be heard. What could this be related to?

[Konsta]

Hi Konsta!
Thank you so much for your help! I appreciate it very much. In the meantime, my USB DAC is up and running. Now a new problem has arisen. When playing audio, whether playing video or audio only, there is a crackling sound. When the playback is finished, nothing more can be heard. What could this be related to?

No idea, TBH. I doubt there's any quick/easy solution on the software side at least. My builds use the generic AOSP USB audio HAL for the USB audio so there's nothing Raspberry Pi specific there.

[dburckh]

Hey Kosta,

I found a bug and I'm not sure where to post it. I have a USB Camera App that draws to ANativeWindow. When performing ANativeWindow_lock(), the ANativeWindow_Buffer returns a stride of 4096. This happened for all resolutions I tested. This causes a seg fault, downstream in libyuv, because the buffer isn't that wide. The width, height, etc are correct. The format is YV12. If I force the stride to be equal to the width, everything works, so I assume the stride just isn't being set somewhere.

I went over Lineage, but they are saying I can't report bugs for non-standard builds. You can use my app (USB Camera Viewer) or I can put together a sample app, if it helps.

Build: AOSP13-20230412-KonstaKANG-rpi4

[eonpluspain]

Hi friends, I'm new here.
I have a problem that I wanted to share with you.
I use a raspberry pi 4 with the latest version of Lineage TV. I use audio and video through HDMI0, with my LG TV, but when the television is off for a while when I come back, the audio signal is lost and it forces me to restart raspberry to recover it. Do you know where the problem is? It's too slow to have to reboot every time I use it.

[friedtofu]

Hi, wonderful project! I'm using Android TV version and having so much fun with it, though I have a few questions:

1. I've put my remote controller custom binding into /boot/rc_keymap.txt, all working well, however I notice short pressing KEY_POWER turn off the display and long pressing KEY_POWER seems to shutdown Raspberry Pi directly instead of showing power menu, is this intended or is there a way to show power manu instead?

2. I have a wifi dongle that using RTL8811CU chipset, it's not natively supported by Raspberry Pi OS as well but there are drivers available and in my Raspberry Pi OS installation I managed to compile one and modprobe it, then disable the onboard wifi (USB dongle has better 5Ghz Wifi performance). I wonder is there a way to do this in LineageOS 20? Do I need to flash the compiled driver via TWRP? Just trying my luck if this is possible.

Thanks!

[Konsta]

Hey Kosta,

I found a bug and I'm not sure where to post it. I have a USB Camera App that draws to ANativeWindow. When performing ANativeWindow_lock(), the ANativeWindow_Buffer returns a stride of 4096. This happened for all resolutions I tested. This causes a seg fault, downstream in libyuv, because the buffer isn't that wide. The width, height, etc are correct. The format is YV12. If I force the stride to be equal to the width, everything works, so I assume the stride just isn't being set somewhere.

I went over Lineage, but they are saying I can't report bugs for non-standard builds. You can use my app (USB Camera Viewer) or I can put together a sample app, if it helps.

Build: AOSP13-20230412-KonstaKANG-rpi4

Do you have logcat or .apk of your app (I genereally don't have Google services installed so I can't install it from the Play Store)?

This could be due to camera constraints gralloc side (https://github.com/raspberry-vanilla/an ... #L375-L397) but that should be visible in the logs if that is the issue.

My build have AOSP external camera HAL (https://source.android.com/docs/core/ca ... sb-cameras) for UVC cameras to be available in any regular Android camera application.

Hi friends, I'm new here.
I have a problem that I wanted to share with you.
I use a raspberry pi 4 with the latest version of Lineage TV. I use audio and video through HDMI0, with my LG TV, but when the television is off for a while when I come back, the audio signal is lost and it forces me to restart raspberry to recover it. Do you know where the problem is? It's too slow to have to reboot every time I use it.

I've had at least one similar report but I'm not able to reproduce the issue. Could be somehow related to the display as well. You could try if you can reproduce this using another display.

Hi, wonderful project! I'm using Android TV version and having so much fun with it, though I have a few questions:

1. I've put my remote controller custom binding into /boot/rc_keymap.txt, all working well, however I notice short pressing KEY_POWER turn off the display and long pressing KEY_POWER seems to shutdown Raspberry Pi directly instead of showing power menu, is this intended or is there a way to show power manu instead?

2. I have a wifi dongle that using RTL8811CU chipset, it's not natively supported by Raspberry Pi OS as well but there are drivers available and in my Raspberry Pi OS installation I managed to compile one and modprobe it, then disable the onboard wifi (USB dongle has better 5Ghz Wifi performance). I wonder is there a way to do this in LineageOS 20? Do I need to flash the compiled driver via TWRP? Just trying my luck if this is possible.

Thanks!

1. That's probably not intended behavior. There used to be power menu on Android TV as well at least with previous Android versions (don't have the Android 13 version installed at the moment to check). It should be possible to change the default long press behavior to something else at least. I'll look into this.

2. There's no support for any external wifi dongle. You can consider Android as an OS for embedded devices so it's designed to support only one specific wifi hardware at a time (supporting some other wifi hardware would likely mean creating an entirely separate Android build).

[sim_tcr]

I am using latest build of lineages 20 tv os.
When I try to pair bluetooth remote control of my Hisense tv, it’s not happening.
Device is found, however is not pairing.
Same behaviour with my Xbox series x controller.

Any thoughts?

[sim_tcr]

Another issue noted is, 5g Wi-Fi network is not shown when scanning. Same issue with aosp 13 latest build.
Other devices at home don’t have this issue.
Pi 4 model b is having 5g Wi-Fi capability I guess.

[Konsta]

I am using latest build of lineages 20 tv os.
When I try to pair bluetooth remote control of my Hisense tv, it’s not happening.
Device is found, however is not pairing.
Same behaviour with my Xbox series x controller.

Any thoughts?

There's known issue pairing BLE device on Android 13 based releases. See http://disq.us/p/2tnvy2s for a "fix" or test if this is any different on Android 12.

Another issue noted is, 5g Wi-Fi network is not shown when scanning. Same issue with aosp 13 latest build.
Other devices at home don’t have this issue.
Pi 4 model b is having 5g Wi-Fi capability I guess.

There's some issues on Android with wifi region. Wifi country code is 00 (DFS-UNSET) until you connect to a network. Then it changes to the region your AP uses. You can try setting a different country (e.g. 'iw reg set US') or change the region from your router's settings.

[sim_tcr]

I am using latest build of lineages 20 tv os.
When I try to pair bluetooth remote control of my Hisense tv, it’s not happening.
Device is found, however is not pairing.
Same behaviour with my Xbox series x controller.

Any thoughts?

There's known issue pairing BLE device on Android 13 based releases. See http://disq.us/p/2tnvy2s for a "fix" or test if this is any different on Android 12.

Another issue noted is, 5g Wi-Fi network is not shown when scanning. Same issue with aosp 13 latest build.
Other devices at home don’t have this issue.
Pi 4 model b is having 5g Wi-Fi capability I guess.

There's some issues on Android with wifi region. Wifi country code is 00 (DFS-UNSET) until you connect to a network. Then it changes to the region your AP uses. You can try setting a different country (e.g. 'iw reg set US') or change the region from your router's settings.

I tried with older 12L build and same issue. Any way, its fine I bought a wireless AIR remote and fixed my issue.
In my router under advanced wireless settings page, I dont see an option to set region (TPLink Archer C1200)

[martinpetrovaj17]

Hi, I'm trying to make my rpi work with a SIMCom 4G/LTE module (SIM7600E to be exact, on this HAT by Makerfabs).

According to their installation guide (though for Raspbian) I should grab SIMCom's drivers, compile them on my rpi and install.

As a complete noob in regards to Unix systems (and OS modifications in general), what do I need to learn / how would I go about this process with this LineageOS 20 build?

For example I can't seem to find kernel headers for Lineage. Do I need to get them separately, or is such thing already a part of the build? Or would I have to build a custom image to include these drivers?
What pitfalls should I be aware of? And can I expect Lineage to automagically pick up cellular connection from this module, or do I need to go through any extra steps to integrate the two?

Thank you for your time,

[Konsta]

Hi, I'm trying to make my rpi work with a SIMCom 4G/LTE module (SIM7600E to be exact, on this HAT by Makerfabs).

According to their installation guide (though for Raspbian) I should grab SIMCom's drivers, compile them on my rpi and install.

As a complete noob in regards to Unix systems (and OS modifications in general), what do I need to learn / how would I go about this process with this LineageOS 20 build?

For example I can't seem to find kernel headers for Lineage. Do I need to get them separately, or is such thing already a part of the build? Or would I have to build a custom image to include these drivers?
What pitfalls should I be aware of? And can I expect Lineage to automagically pick up cellular connection from this module, or do I need to go through any extra steps to integrate the two?

Thank you for your time,

No, you can't use any LTE modem out-of-the-box. My builds are configured as wifi only tablet so they don't even have Android telephony framework or drivers to support any modem hardware. I have builds (of older Android versions) that have support for Sixfab modem HAT and Quectel EC25. LTE data and SMS works fine. It's also possible to make/receive calls but in-call audio is not working. It's not something that I plan to include in public releases as practically no one has the hardware. You can look into Raspberry Vanilla AOSP source code (https://github.com/raspberry-vanilla) I've released since adding support for something like this is not possible without compiling a custom build with added support for the specific hardware.

Compiling the kernel driver alone doesn't do much good as it's not hooked to Android telephony framework in any way. Android needs a hardware specific RIL implementation for this purpose. Waveshare provides some Android drivers (for older Android versions) for 7600E (https://www.waveshare.com/wiki/SIM7600E ... ccordion26). I agree with their note that it is "required to have certain Android system development experience and R&D capabilities" to make something like this work.

[martinpetrovaj17]

Thank you for the info, Konsta. I can tell when something is out of my skill bracket

This question is way out of your responsibility and perhaps knowledge, but theoretically speaking, could a virtual machine (vmware esxi running your LOS build) within raspberry pi os (or some other rpi-compatible lightweight distro which plays nicely with LTE modems) work, or would I be just running down a different rabbit hole?

Btw sorry if I'm blind, dumb or both, but I haven't noticed any donation options on your website or profile? Where do I send the XL thank you pizza?