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

[KonstaT]

So in my case wich format do i use for my 1TB HDD ?

I will use it for multimedia , kodi and plex
can you help me choosing the right format ?

Out of these two you'd probably want to use exFAT for a storage device this size. Simple Google search would have been a lot quicker, though.

 

[mohamedbk]

Out of these two you'd probably want to use exFAT for a storage device this size. Simple Google search would have been a lot quicker, though.

Dear my friend,
Your build have some problems :

1) you can't format external usb or hdd in setting them storage , you can't use it as external storage , it's just a media drive only .

2) The media servers apps ( kodi , emby , plex media want detect external storage .
That's why i contacted you , i tried to config my rp4 android tv as a media server and it didn't work because of this

 

[KonstaT]

Dear my friend,
Your build have some problems :

1) you can't format external usb or hdd in setting them storage , you can't use it as external storage , it's just a media drive only .

2) The media servers apps ( kodi , emby , plex media want detect external storage .
That's why i contacted you , i tried to config my rp4 android tv as a media server and it didn't work because of this

Neither of these have anything to do with my build. There is nothing out of the ordinary here to how external storage devices are managed in Android in general. With recent Android versions storage access for apps is limited to the apps' own directory for security reasons.

Apps having limited access to external storage is by design in Android. VLC/Kodi/etc access to external storage has been discussed e.g. https://forum.xda-developers.com/t/...raspberry-pi-4-b.4139059/page-5#post-83816985

 

[Xenox003]

Hi guys, i might need some help getting LineageOS 20 running on the official 7" Touchscreen.

As mentioned in the "docs" there is an option in Settings: --> System --> RPI Settings --> Touchscreen, which is supposed to config the OS to properly run with the official 7" >Touchscreen.

When applying this setting and rebooting the PI i end up with
1. A Blackscreen on the Touchscreen (backlight on obviously)
2. A Blackscreen on the HDMI0 output (previously worked fine, probably its not supposed to work cause the touchscreen config is active, i don't need it anyways once i get the touchscreen running)

After taking a look at the boot/config.txt and resolution.txt i noticed the dtoverlay=vc4-kms-dsi-7inch line is uncommented and the resolution is set to 800x480, which seems right to me.

After a little bit more fiddling around i found out that if it boots into TWRP it displays fine on the Touchscreen, although the touch input does not work (which could also be a general thing wor TWRP, idk)

Am i missing something here? I don't seem to be getting, why its not properly booting into android/displaying the actual image.

if i should include some more info or whatever else, feel free to ask me

Thanks in advance for the help.

 

[KonstaT]

Hi guys, i might need some help getting LineageOS 20 running on the official 7" Touchscreen.

As mentioned in the "docs" there is an option in Settings: --> System --> RPI Settings --> Touchscreen, which is supposed to config the OS to properly run with the official 7" >Touchscreen.

When applying this setting and rebooting the PI i end up with
1. A Blackscreen on the Touchscreen (backlight on obviously)
2. A Blackscreen on the HDMI0 output (previously worked fine, probably its not supposed to work cause the touchscreen config is active, i don't need it anyways once i get the touchscreen running)

After taking a look at the boot/config.txt and resolution.txt i noticed the dtoverlay=vc4-kms-dsi-7inch line is uncommented and the resolution is set to 800x480, which seems right to me.

After a little bit more fiddling around i found out that if it boots into TWRP it displays fine on the Touchscreen, although the touch input does not work (which could also be a general thing wor TWRP, idk)

Am i missing something here? I don't seem to be getting, why its not properly booting into android/displaying the actual image.

if i should include some more info or whatever else, feel free to ask me

Thanks in advance for the help.

You need to disconnect any HDMI display when you're using the DSI display.

Touch also works in TWRP if boot to recovery through the Android power menu (touchscreen driver gets enabled separately as TWRP doesn't use hw accelerated graphics).

 

[Xenox003]

You need to disconnect any HDMI display when you're using the DSI display.

Touch also works in TWRP if boot to recovery through the Android power menu (touchscreen driver gets enabled separately as TWRP doesn't use hw accelerated graphics).

Seems like disconnecting the HDMI Monitor woked fine, Touchscreen is displaying an Image, Touch input also works fine.

I really tried a lot of stuff before like changing the boot/config.txt to load additional/fewer drivers and whatever else. I guess i overcomplicated my view to the problem a bit, causing me not to try the most simple things like "Hey, how about i remove my HDMI cable and see if it works".

Thanks for creating this awesome custom kernel, prob helps out a lotta ppl.

 

[KonstaT]

Seems like disconnecting the HDMI Monitor woked fine, Touchscreen is displaying an Image, Touch input also works fine.

I really tried a lot of stuff before like changing the boot/config.txt to load additional/fewer drivers and whatever else. I guess i overcomplicated my view to the problem a bit, causing me not to try the most simple things like "Hey, how about i remove my HDMI cable and see if it works".

Thanks for creating this awesome custom kernel, prob helps out a lotta ppl.

Yes, could be worth pointing it out in the FAQ that you need to disconnect HDMI displays in this case.

This is an entire custom Android OS, but yes, it also contains a custom Linux kernel.

 

[haruka-k]

Hey, thanks for your amazing work, everything works wonderfully.

Is there a way to turn off/on the HDMI output from a shell? The screen I use does not support CEC, so the only way would be turning off the actual output so the screen goes into "no signal" and shuts off; something like tvservice --off etc., but none of the commands I can find around on the internet seem to work.
Is any special command available for this here?

What I've tried:

rpi4:/ # tvservice --off
tvservice is not supported when using the vc4-kms-v3d driver.
Similar features are available with standard linux tools
such as modetest from libdrm-tests.
rpi4:/ # vcgencmd display_power 0
display_power=1
rpi4:/ # setterm --powersave off
/system/bin/sh: setterm: inaccessible or not found
127|rpi4:/ # vbetool dpms off
/system/bin/sh: vbetool: inaccessible or not found
127|rpi4:/ # cd /sys/b
block/  bus/
127|rpi4:/ # cd /sys/class/backlight/
rpi4:/sys/class/backlight # ls
rpi4:/sys/class/backlight #

 

[KonstaT]

Hey, thanks for your amazing work, everything works wonderfully.

Is there a way to turn off/on the HDMI output from a shell? The screen I use does not support CEC, so the only way would be turning off the actual output so the screen goes into "no signal" and shuts off; something like tvservice --off etc., but none of the commands I can find around on the internet seem to work.
Is any special command available for this here?

What I've tried:

rpi4:/ # tvservice --off
tvservice is not supported when using the vc4-kms-v3d driver.
Similar features are available with standard linux tools
such as modetest from libdrm-tests.
rpi4:/ # vcgencmd display_power 0
display_power=1
rpi4:/ # setterm --powersave off
/system/bin/sh: setterm: inaccessible or not found
127|rpi4:/ # vbetool dpms off
/system/bin/sh: vbetool: inaccessible or not found
127|rpi4:/ # cd /sys/b
block/  bus/
127|rpi4:/ # cd /sys/class/backlight/
rpi4:/sys/class/backlight # ls
rpi4:/sys/class/backlight #

Short press on the power button will switch the display on/off like on any other Android device. If you want to do this in shell:

input keyevent KEYCODE_POWER

There's currently an issue with display blanking so the display is not switched off entirely. It looks like this is now fixed on upstream drm_hwcomposer so this should work again if/when there's another release.

 

[Yoshikage_Kira]

What gapps should I use? I have tried several but no luck so far. And the wifi connects but I get no internet.

Ok, I installed the Lineage OS 19 and gapps issue is solved but the internet issue is still present.

 

[Yoshikage_Kira]

The internet does not work on the Android TV version which is unfortunate.

 

[jeff862]

What is the workaound choppy video for mkv file?

 

[KonstaT]

New builds. H.264 hardware video decoding & encoding.

LineageOS 20 (Android 13)

for Raspberry Pi 4

konstakang.com

LineageOS 20 Android TV (Android 13)

for Raspberry Pi 4

konstakang.com

-Android 13 QPR1
-fix pixel format on H.264 hardware video decoding
-enable H.264 hardware video encoding
-update to Mesa 22.3.2
-update to Linux 5.15.78 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
-Android security patch level: 5 January 2023 (merged)

 

[KonstaT]

https://twitter.com/i/web/status/1616054277629218819

 

[Xenox003]

Hi guys, i just discovered a new problem regarding to the Raspberry PI Build of LineageOS 20

Let me take it a little short here: Bluetooth Low Energy does not appear to work
Let me give a little more context here:

I use my Behringer Flow 8 Digital Mixer together with the FLOW Mix app in order to do live audio processing, i want to run the FLOW Mix app on my raspberry PI running with this build here.
Once i tried to connect i noticed some strange behaviour when attempting to establish the BLE connection.

See the attached Video: https://streamable.com/678a2d

It seems to be activating and deactivating bluetooth all the time, when trying to connect to the Mixer with my Phone it works fine.

After diving a little bit deeper into the problem i could also exclude the FLOW Mix app itself. I tested the BLE connection with some BLE tester app, again on my phone it worked fine, on the raspberry it could not connect.

Phone:

Raspberry:

Anyone ever had simmilar issues? Do yall have a working fix for that?

 

[KonstaT]

Hi guys, i just discovered a new problem regarding to the Raspberry PI Build of LineageOS 20

Let me take it a little short here: Bluetooth Low Energy does not appear to work
Let me give a little more context here:

I use my Behringer Flow 8 Digital Mixer together with the FLOW Mix app in order to do live audio processing, i want to run the FLOW Mix app on my raspberry PI running with this build here.
Once i tried to connect i noticed some strange behaviour when attempting to establish the BLE connection.

See the attached Video: https://streamable.com/678a2d

It seems to be activating and deactivating bluetooth all the time, when trying to connect to the Mixer with my Phone it works fine.

After diving a little bit deeper into the problem i could also exclude the FLOW Mix app itself. I tested the BLE connection with some BLE tester app, again on my phone it worked fine, on the raspberry it could not connect.

Phone: View attachment 5814627

Raspberry:
View attachment 5814629


Anyone ever had simmilar issues? Do yall have a working fix for that?

Android 13 switched to new gabeldorsche bluetooth stack so I'm not sure if everything is configured correctly just yet (see https://github.com/raspberry-vanilla/android_device_brcm_rpi4/blob/android-13.0/vendor.prop#L8-L32). Logcat would likely help to figure out the issue.

I've tested BLE on some previous Android version and it was working then at least.

 

[Xenox003]

Android 13 switched to new gabeldorsche bluetooth stack so I'm not sure if everything is configured correctly just yet (see https://github.com/raspberry-vanilla/android_device_brcm_rpi4/blob/android-13.0/vendor.prop#L8-L32). Logcat would likely help to figure out the issue.

I've tested BLE on some previous Android version and it was working then at least.

Here is a Logcat dump of the point in time i tried to connect to the device with BLE: https://pastebin.com/WE7Pt3HE

Just from looking at it it seems the bluetooth service dies quite often like this:

Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 5353 (bt_stack_manage), pid 5307 (droid.bluetooth)

...

Abort message: 'assertion 'status == HidlStatus::SUCCESS' failed'

 

[KonstaT]

Here is a Logcat dump of the point in time i tried to connect to the device with BLE: https://pastebin.com/WE7Pt3HE

Just from looking at it it seems the bluetooth service dies quite often like this:

Yes, I was able to reproduce this with my BLE heart rate monitor as well. I don't have any quick fix for this, though.

I know BLE has worked in some older version because I've tested this before. You can try some of the older versions if you need BLE support or dig into the Raspberry Vanilla sources (https://github.com/raspberry-vanilla) and try to fix it with Android 13.

 

[vecchifede01]

It seems Gapps 13 for Android TV are available:

Codefire - Listing of ATV

BTW, has anybody tried using Geforce Now?

 

[KonstaT]

It seems Gapps 13 for Android TV are available:

Codefire - Listing of ATV

BTW, has anybody tried using Geforce Now?

I tested this but it seems to be broken as it fails to copy the files.

This is because https://gitlab.com/MindTheGapps/vendor_gapps_tv/-/commit/6c102b26b149076b482ea9c18e39cafa654c7653 and if you revert that change (edit update-binary that's inside the zip) it seems to work. I don't know why that change was made and why it doesn't work with TWRP included in my builds.