• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[DEV][ROM][UNOFFICIAL] LineageOS 18.1 (Android 11) for Raspberry Pi 4 B

Search This thread

Neogx

Member
Jan 25, 2014
38
4
san
I'm not aware of any way you could configure it server side. You can do this on the client depending on the app your using. I only tested VNC with Remmina which comes bundled with Ubuntu and it seems to work fine with that.

General advice is to use proper sdcard (at least class 10) and power source (3A in case of Pi 4). Impossible to say what could be the issue without seeing any logs anyway.

There's also https://github.com/lineage-rpi/android_kernel_brcm_rpi/issues/6 but there's been some mixed reports whether this is fixed in Android 11 (or there's two similar separate issues).
I got the whole starter kit from canakit on Amazon I think there a official resaler with a power supply and memory card included . it seem like everything was right in what is required.


Where can i find the logs to see whats going on?


Update 1 Tried adding dtoverlay=disable-wifi in the config file and it worked i guess there's a issue with wifi?
 
Last edited:

Linhx

Member
Dec 19, 2015
14
0
You can on LineageOS 17.

Support for NTFS drives is not included in LineageOS 18 for some reason. http://disq.us/p/2fr6xj1
Can’t find the reason under this link and also no facts regarding this issue on other sites. Maybe you can add this topic to the questions because this problem makes it impossible to watch videos that are stored on ntfs-hdds. Is there no way to bypass this restriction (drivers etc.)?
 

attacker

Senior Member
May 21, 2007
59
5
I'm not aware of any way you could configure it server side. You can do this on the client depending on the app your using. I only tested VNC with Remmina which comes bundled with Ubuntu and it seems to work fine with that.
May I get the guide / QA for the config to vnc server side? E.g. password protect.
Thanks
 

KonstaT

Senior Member
Jan 20, 2016
428
288
KonstaKANG.com
any chance to fix the camera for video-conferencing systems (skype, zoom etc. )?
You would need to be a lot more specific how it's broken in the first place.
May I get the guide / QA for the config to vnc server side? E.g. password protect.
Thanks
There's currently no way to use password protection.

Enable the VNC server from Pi specific settings (Settings -> System -> Advanced settings -> VNC), get you Pi's IP address (e.g.Settings -> About tablet -> IP address), and use VNC client to connect to Pi's VNC port (5900).
 

kiai.72

Member
Apr 24, 2021
14
1
You would need to be a lot more specific how it's broken in the first place.
all videoconference-apps behave the same on this ROMS (i tried 16/17/18 with skype, skype lite and zoom):
When you start the app -> the camera even works! You see your own camera picture - it's even moving.
So far everything looks fine.

But when you start a real video-call -> your own camera picture will not be transfered to the other people. They just don't get your video - like you turned camera off.
 

KonstaT

Senior Member
Jan 20, 2016
428
288
KonstaKANG.com
all videoconference-apps behave the same on this ROMS (i tried 16/17/18 with skype, skype lite and zoom):
When you start the app -> the camera even works! You see your own camera picture - it's even moving.
So far everything looks fine.

But when you start a real video-call -> your own camera picture will not be transfered to the other people. They just don't get your video - like you turned camera off.
I don't think that's accurate description at all. LineageOS 16 build for Pi even uses entirely different graphics drivers so it doesn't have the same camera issues as 17 & 18. This is also not the case for all video conferencing apps. There was a pretty thorough test using various apps (https://www.raspberrypi.org/forums/viewtopic.php?f=73&t=284462).

Camera on Zoom is reported to work once starting the application but you need to reboot your device or kill the camera server (http://disq.us/p/2g62t68) for it to work again.
 

kiai.72

Member
Apr 24, 2021
14
1
I don't think that's accurate description at all. LineageOS 16 build for Pi even uses entirely different graphics drivers so it doesn't have the same camera issues as 17 & 18. This is also not the case for all video conferencing apps. There was a pretty thorough test using various apps (https://www.raspberrypi.org/forums/viewtopic.php?f=73&t=284462).

Camera on Zoom is reported to work once starting the application but you need to reboot your device or kill the camera server (http://disq.us/p/2g62t68) for it to work again.
sorry, you're right. since i've seen this - i started from scratch - checked everything, and since i moved to IPV6 a lot more works - not everthing but:
zoom + jitsi: camera works (picture is transfered to the chat-partners) - but i cant use my microphone yet.
skype + skype lite: still like i described before: does not work: the picture will not be transfered to the chat-partners.

this is a great step forward. Would like to have skype as well - but more important for the moment is the microphone.
Do you have any idea? I tried the microphone in my USB-camera + a separate USB microphone - both do not work.
Is there some kind of "choose input device" - option somewhere ?

thank you veray much!
 

kiai.72

Member
Apr 24, 2021
14
1
sorry, you're right. since i've seen this - i started from scratch - checked everything, and since i moved to IPV6 a lot more works - not everthing but:
zoom + jitsi: camera works (picture is transfered to the chat-partners) - but i cant use my microphone yet.
skype + skype lite: still like i described before: does not work: the picture will not be transfered to the chat-partners.

this is a great step forward. Would like to have skype as well - but more important for the moment is the microphone.
Do you have any idea? I tried the microphone in my USB-camera + a separate USB microphone - both do not work.
Is there some kind of "choose input device" - option somewhere ?

thank you veray much!
i did more tests today: lineageOS recorder works! But zoom and jitsi not: when you speak to the RPI-microphone->you hear yourself on the RPI! - but your conference-partner does not hear you at all.

Maybe it depends on what kind of audio the app uses. Maybe when "speakerphone"-audio is used at the same time we have that audio problem?

In the meanwhile i also connected a bluetooth headset -> same problem, not only with USB.
 

matthuo

New member
May 2, 2021
4
0
After burning the img to the SD card, I found that there is a partition named “_ ” Is this a partition of the file system? If not, where is the file system? I need to make img.xz for PINN to guide and generate dual systems.
 

KonstaT

Senior Member
Jan 20, 2016
428
288
KonstaKANG.com
i did more tests today: lineageOS recorder works! But zoom and jitsi not: when you speak to the RPI-microphone->you hear yourself on the RPI! - but your conference-partner does not hear you at all.

Maybe it depends on what kind of audio the app uses. Maybe when "speakerphone"-audio is used at the same time we have that audio problem?

In the meanwhile i also connected a bluetooth headset -> same problem, not only with USB.
Have you tested this on LineageOS 17? This could be because of how Android handles USB audio. Raspberry Pi hardware doesn't have any built-in audio input so this is just something that needs to dealt with.

Last I've tested bluetooth headset mic is not working at all.
After burning the img to the SD card, I found that there is a partition named “_ ” Is this a partition of the file system? If not, where is the file system? I need to make img.xz for PINN to guide and generate dual systems.
It's actually named "/" (as in root) but that's not a valid character for filenames so your OS changes it to something else. It's the system partition (or system-as-root to be precise).

It's quite involved to make this image compatible with PINN. We've been through this with PINN developer procount and I think he's managed to automate the process. You should be in contact with him and ask to add support for the latest builds.
 

matthuo

New member
May 2, 2021
4
0
Have you tested this on LineageOS 17? This could be because of how Android handles USB audio. Raspberry Pi hardware doesn't have any built-in audio input so this is just something that needs to dealt with.

Last I've tested bluetooth headset mic is not working at all.

It's actually named "/" (as in root) but that's not a valid character for filenames so your OS changes it to something else. It's the system partition (or system-as-root to be precise).

It's quite involved to make this image compatible with PINN. We've been through this with PINN developer procount and I think he's managed to automate the process. You should be in contact with him and ask to add support for the latest builds.
I have successfully installed it through PINN. But now we have a new problem:
When performing WIFI static IP configuration, click Enter and you cannot proceed to the next step.
This problem should be no problem with the installation of PINN.
 

kiai.72

Member
Apr 24, 2021
14
1
Have you tested this on LineageOS 17? This could be because of how Android handles USB audio. Raspberry Pi hardware doesn't have any built-in audio input so this is just something that needs to dealt with.

Last I've tested bluetooth headset mic is not working at all.

no - in the meanwhile i'm on 18.1 again. So do you think 17 might work ? should i try ?
By the way: i noticed that when i use raspbian it also shows me a "Monitor microphone" - like there would be one from HDMI-TV - but there's isn't.
Maybe i just have to many input devices. Is it possible to list them somehow - and disable all i don't need ?
 

KonstaT

Senior Member
Jan 20, 2016
428
288
KonstaKANG.com
Why can't I set static IP for a network in Settings? After setting the static IP, click Next, nothing happens
Logcat is pretty useful what comes to answering questions like why. Setting static IP seems to work fine on the regular tablet UI build. Also worth pointing out if you're talking about Android TV.
no - in the meanwhile i'm on 18.1 again. So do you think 17 might work ? should i try ?
By the way: i noticed that when i use raspbian it also shows me a "Monitor microphone" - like there would be one from HDMI-TV - but there's isn't.
Maybe i just have to many input devices. Is it possible to list them somehow - and disable all i don't need ?
There's no sound input built into the Pi hardware. Not possible via HDMI or the 3.5mm jack.

I don't think there's been any previous reports of such mic issue with e.g. Zoom.
 

matthuo

New member
May 2, 2021
4
0
Logcat is pretty useful what comes to answering questions like why. Setting static IP seems to work fine on the regular tablet UI build. Also worth pointing out if you're talking about Android TV.
Yes, this issue is from Android TV (RPi4). I haven’t used Logcat, but I’ll try to provide it later. However, by the way, this phenomenon is easy to reproduce on RPi4.
 

kiai.72

Member
Apr 24, 2021
14
1
There's no sound input built into the Pi hardware. Not possible via HDMI or the 3.5mm jack.

I don't think there's been any previous reports of such mic issue with e.g. Zoom.
Thank you. i wonder how to proceed? Hardware is ok - everything works with raspbian.
I did more tests today. Like i said: LineageOs voice-recorder works. But none of my tested videchat-programs work.

So i decided to try the browser instead: chrome dev! For example: https://online-voice-recorder.com/ - this does not work either.
I can even choose microphone type - and i can start recording. but there is NO sound / no Input - like microphone is muted.
But it is not muted, otherwise it wouldnt work LineageOs voice-recorder either)

There's not much in logcat - here's logcat from browser-test.
Any idea ?


05-07 19:44:42.446 382 449 E LightsService: Light requested not available on this device. 2
05-07 19:44:48.266 382 417 E LightsService: Light requested not available on this device. 2
05-07 19:44:51.568 382 449 E LightsService: Light requested not available on this device. 2
05-07 19:44:51.792 2591 2616 E chromium: [ERROR:android_image_reader_utils.cc(19)] Failed to create android native fence sync object.
05-07 19:44:51.809 2511 2587 I libOpenSLES: Emulating old channel mask behavior (ignoring positional mask 0x1, using default mask 0x10 based on channel count of 1)
05-07 19:44:51.818 235 4774 I AudioFlinger: AudioFlinger's thread 0xaaa98030 tid=4774 ready to run
05-07 19:44:51.819 235 336 W AudioFlinger: createRecordTrack_l(): mismatch between requested flags (00000005) and input flags (00000001)
05-07 19:44:51.825 382 3173 I system_server: oneway function results will be dropped but finished with status OK and parcel size 4
05-07 19:44:51.825 382 3173 I system_server: oneway function results will be dropped but finished with status OK and parcel size 4
05-07 19:44:51.826 382 2083 I system_server: oneway function results will be dropped but finished with status OK and parcel size 4
05-07 19:44:51.827 382 2083 I chatty : uid=1000(system) Binder:382_B identical 1 line
05-07 19:44:51.828 382 2083 I system_server: oneway function results will be dropped but finished with status OK and parcel size 4
05-07 19:44:51.828 382 3173 I SoundTriggerMiddlewareLogging: setCaptureState[this=com.an[email protected]4f7a762, caller=1041/235](false)
05-07 19:44:51.831 382 2083 I system_server: oneway function results will be dropped but finished with status OK and parcel size 4
05-07 19:44:51.836 235 4776 I AudioFlinger: AudioFlinger's thread 0xaaa98030 tid=4776 ready to run
05-07 19:44:51.844 382 3173 I system_server: oneway function results will be dropped but finished with status OK and parcel size 4
05-07 19:44:51.846 382 3173 I system_server: oneway function results will be dropped but finished with status OK and parcel size 4
05-07 19:44:51.848 382 3274 I system_server: oneway function results will be dropped but finished with status OK and parcel size 4
05-07 19:44:51.852 382 2083 I system_server: oneway function results will be dropped but finished with status OK and parcel size 4
05-07 19:44:51.852 382 2083 I system_server: oneway function results will be dropped but finished with status OK and parcel size 4
05-07 19:44:51.860 382 3173 I SoundTriggerMiddlewareLogging: setCaptureState[this=com.an[email protected]4f7a762, caller=1041/235](true)
05-07 19:44:51.861 209 4654 E FMQ : grantorIdx must be less than 3
05-07 19:44:51.861 209 4654 E FMQ : grantorIdx must be less than 3
05-07 19:44:51.862 235 4776 E FMQ : grantorIdx must be less than 3
05-07 19:44:51.862 235 4776 E FMQ : grantorIdx must be less than 3
05-07 19:44:51.908 4656 4675 I chromium: [INFO:audio_latency.cc(145)] audioHardwareBufferSize = 4104
05-07 19:44:51.921 2511 2587 I AAudio : AAudioStreamBuilder_openStream() called ----------------------------------------
05-07 19:44:51.921 2511 2587 I AudioStreamBuilder: rate = 48000, channels = 2, format = 5, sharing = SH, dir = OUTPUT
05-07 19:44:51.921 2511 2587 I AudioStreamBuilder: device = 0, sessionId = -1, perfMode = 10, callback: ON with frames = 4104
05-07 19:44:51.921 2511 2587 I AudioStreamBuilder: usage = 1, contentType = 0, inputPreset = 0, allowedCapturePolicy = 0
05-07 19:44:51.921 2511 2587 I AudioStreamBuilder: privacy sensitive = false
05-07 19:44:51.922 2511 2587 D AudioStreamBuilder: build() MMAP not used because AAUDIO_PERFORMANCE_MODE_LOW_LATENCY not requested.
05-07 19:44:51.922 2511 2587 D com.chrome.dev: PlayerBase::playerBase()
05-07 19:44:51.924 2511 2587 D AudioStreamTrack: open(), request notificationFrames = 4104, frameCount = 4104
05-07 19:44:51.926 235 4706 W AudioFlinger: Client adjusted notificationFrames from 4104 to 2052 for frameCount 4104
05-07 19:44:51.928 235 4706 D AF::TrackHandle: OpPlayAudio: track:94 usage:1 not muted
05-07 19:44:51.930 2511 2587 D AAudioStream: setState(s#13) from 0 to 2
05-07 19:44:51.931 382 3173 I system_server: oneway function results will be dropped but finished with status OK and parcel size 4
05-07 19:44:51.931 2511 2587 I AAudio : AAudioStreamBuilder_openStream() returns 0 = AAUDIO_OK for s#13 ----------------
05-07 19:44:51.931 382 3173 I system_server: oneway function results will be dropped but finished with status OK and parcel size 4
05-07 19:44:51.933 2511 2587 D AAudio : AAudioStream_requestStart(s#13) called --------------
05-07 19:44:51.933 2511 2587 D AAudioStream: setState(s#13) from 2 to 3
05-07 19:44:51.978 235 4706 W APM::AudioPolicyEngine: getDevicesForStrategy() unknown strategy: -1
05-07 19:44:51.978 235 4706 W APM::AudioPolicyEngine: getDevicesForStrategy() unknown strategy: -1
05-07 19:44:51.978 2511 2587 D com.chrome.dev: PlayerBase::start() from IPlayer
05-07 19:44:51.978 2511 3053 D AudioStreamLegacy: onAudioDeviceUpdate(deviceId = 2)
05-07 19:44:51.979 2511 2587 D AAudio : AAudioStream_requestStart(s#13) returned 0 ---------
05-07 19:44:51.979 209 916 W StreamHAL: Error from HAL stream in function get_presentation_position: Operation not permitted
05-07 19:44:51.979 382 3173 I system_server: oneway function results will be dropped but finished with status OK and parcel size 4
05-07 19:44:51.980 2511 2511 V MediaRouter: Selecting route: RouteInfo{ name=Tablet, description=null, status=null, category=RouteCategory{ name=System types=ROUTE_TYPE_LIVE_AUDIO ROUTE_TYPE_LIVE_VIDEO groupable=false }, supportedTypes=ROUTE_TYPE_LIVE_AUDIO ROUTE_TYPE_LIVE_VIDEO , presentationDisplay=null }
05-07 19:44:51.984 209 4654 I EffectsFactory: EffectCreate() create_effect
05-07 19:44:51.990 209 916 W StreamHAL: Error from HAL stream in function get_presentation_position: Operation not permitted
05-07 19:44:51.995 209 4654 I EffectsFactory: EffectCreate() create_effect
05-07 19:44:51.997 209 4654 I chatty : uid=1041(audioserver) HwBinder:209_4 identical 1 line
05-07 19:44:52.000 209 4654 I EffectsFactory: EffectCreate() create_effect
05-07 19:44:52.002 209 916 W StreamHAL: Error from HAL stream in function get_presentation_position: Operation not permitted
05-07 19:44:52.003 2511 4779 D AAudioStream: setState(s#13) from 3 to 4
05-07 19:44:52.038 235 344 D AudioFlinger: mixer(0xaaae6030) throttle end: throttle time(27)
05-07 19:43:17.889 2511 2511 I chatty : uid=10142(com.chrome.dev) identical 15 lines
05-07 19:43:17.905 2511 2511 D ViewRootImpl[Main]: updatePointerIcon called with position out of bounds
05-07 19:44:52.075 382 382 D NotificationService: 0|com.chrome.dev|9|MediaCaptureNotificationService|10142: granting content://settings/system/notification_sound
05-07 19:44:52.077 382 382 I chatty : uid=1000 system_server identical 1 line
05-07 19:44:52.078 382 382 D NotificationService: 0|com.chrome.dev|9|MediaCaptureNotificationService|10142: granting content://settings/system/notification_sound
05-07 19:44:52.082 382 382 W NotificationHistory: Attempted to add notif for locked/gone/disabled user 0
05-07 19:44:52.110 2591 2616 E chromium: [ERROR:android_image_reader_utils.cc(19)] Failed to create android native fence sync object.
05-07 19:44:56.787 2591 2616 I chatty : uid=10142(com.chrome.dev) CrGpuMain identical 64 lines
05-07 19:44:56.881 2591 2616 E chromium: [ERROR:android_image_reader_utils.cc(19)] Failed to create android native fence sync object.
05-07 19:44:56.935 382 417 E LightsService: Light requested not available on this device. 2
05-07 19:44:56.962 2591 2616 E chromium: [ERROR:android_image_reader_utils.cc(19)] Failed to create android native fence sync object.
05-07 19:44:59.860 2591 2616 I chatty : uid=10142(com.chrome.dev) CrGpuMain identical 36 lines
05-07 19:44:59.947 2591 2616 E chromium: [ERROR:android_image_reader_utils.cc(19)] Failed to create android native fence sync object.
05-07 19:45:00.003 516 516 D KeyguardClockSwitch: Updating clock: 19:45
05-07 19:45:00.036 2591 2616 E chromium: [ERROR:android_image_reader_utils.cc(19)] Failed to create android native fence sync object.
 
Last edited:

dylerb

Member
Mar 21, 2013
18
5
Here’s my build of LineageOS 18.1 for Raspberry Pi 4 Model B, Pi 400, and Compute Module 4. It is unofficial and unsupported by the LineageOS team. It’s for advanced users only. Pi 4 model with at least 2GB of RAM is required to run this build.

Important! This image includes parts that are licensed under non-commercial license (Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International). You may use this build freely in personal/educational/etc use. Commercial use is not allowed with this build!

Screenshot_20210104-104810_Settings.png


https://konstakang.com/devices/rpi4/LineageOS18/

There is also Android TV version available.
Screenshot_20210306-163341_Settings.png


https://konstakang.com/devices/rpi4/LineageOS18-ATV/
Thank you very much. I'm using your AndroidTV ROM for Raspi 4B.
 
  • Like
Reactions: KonstaT

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    New build.

    -switch to using HDMI-CEC HAL
    -update to Mesa 21.1.5
    -update to Linux 5.4.132 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
    -Android security patch level: 5 July 2021 (merged)

    ---

    Also a new Android TV build.

    -add support for HDMI-CEC
    -add built-in VNC server
    -update to Mesa 21.1.5
    -update to Linux 5.4.132 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
    -Android security patch level: 5 July 2021 (merged)
  • 14
    Here’s my build of LineageOS 18.1 for Raspberry Pi 4 Model B, Pi 400, and Compute Module 4. It is unofficial and unsupported by the LineageOS team. It’s for advanced users only. Pi 4 model with at least 2GB of RAM is required to run this build.

    Important! This image includes parts that are licensed under non-commercial license (Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International). You may use this build freely in personal/educational/etc use. Commercial use is not allowed with this build!

    Screenshot_20210104-104810_Settings.png


    https://konstakang.com/devices/rpi4/LineageOS18/

    There is also Android TV version available.
    Screenshot_20210306-163341_Settings.png


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

    Working:
    • Audio (HDMI, 3.5mm jack, USB microphones, bluetooth speakers/headsets, etc)
    • Audio DAC (using GPIO DACs e.g. Hifiberry DAC+)
    • Bluetooth
    • Camera (using official Pi camera modules & UVC USB webcams)
    • GPIO
    • GPS (using external USB modules e.g. U-Blox 7)
    • Ethernet
    • Hardware accelerated graphics (V3D)
    • HDMI display
    • I2C
    • IR remotes (using external GPIO IR modules e.g. TSOP4838)
    • RTC (using external GPIO I2C modules e.g. DS3231)
    • Sensors (using external GPIO I2C modules e.g. MPU6050, LSM6DS3 & LSM303DLHC accelerometer/gyroscope/magnetometer)
    • Serial console (using external GPIO serial console adapters e.g. PL2303)
    • SPI
    • Touchscreen/multi-touch (USB touchscreens, Waveshare SPI touchscreens)
    • USB (mouse, keyboard, storage, etc)
    • USB-C (ADB, MTP, PTP, USB-tethering)
    • Wifi
    • Wifi tethering

    Not working:
    • Hardware video decoding & encoding (software decoding & encoding works)

    Issues:
    • Stock camera app is not working - many third party camera apps seem to work
    • SELinux is in permissive mode
    • and more…

    Sources:

    Thanks:
    • Peter Yoon and everyone who has contributed to android-rpi
    • Roman Stratiienko and GloDroid project for graphics fixes
    • brobwind for bluetooth fixes
    • Eric Anholt for V3D graphics driver
    • Maxime Ripard for Pi 4 KMS driver
    • Android-x86 project
    • LineageOS team & everyone who has contributed to LineageOS 18.1
    5
    New build.

    -add support for LSM303DLHC accelerometer & magnetometer sensor
    -add separate TWRP flashable su add-on (see FAQ)
    -allow switching display off with power button
    -add support for USB-C (ADB, MTP, PTP, USB-tethering)
    -enable bluetooth tethering
    -add settings option for mouse back button feature
    -update to TWRP 3.5.0_9-0-KonstaKANG
    -update to Mesa 20.3.4
    -update to Linux 5.4.98 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
    -Android security patch level: 5 February 2021 (merged)
    4
    How to install:
    1. Follow the official Raspberry Pi instructions for writing the image to the SD card (Linux, Mac, Windows).

    FAQ:

    FAQ is getting quite long and difficult to maintain in several different places. You can find the always up-to-date FAQs here:
    https://konstakang.com/devices/rpi4/LineageOS18/
    https://konstakang.com/devices/rpi4/LineageOS18-ATV/
    4
    New build.

    -add initial support for HDMI-CEC
    -add built-in VNC server
    -update to Mesa 21.0.2
    -update to Linux 5.4.111 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
    -Android security patch level: 5 April 2021 (merged)
    3
    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.
    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.

    @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.
    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.