[DEV][ROM][UNOFFICIAL] LineageOS 19 (Android 12L) for Raspberry Pi 4 B

[KonstaT]

Great, sorry for noising down the wrong thread. I also have a question to you if you create builds that can run on Asus Tinker Board. If not, forget about that.

It will also be interesting to know, for RPI4, if Audiophonics hat DACs are supported. See link: https://www.audiophonics.fr/en/dac-...spdif-pcm-dsd-usb-c-power-supply-p-12795.html
Hope so, since I have several of those.

RPI4 with more than 2Gb RAM is hard to find on the market just now. Will 2Gb be sufficient for your builds?

And also, reading about Android on hifiberry forums, they seem to be unaware of your builds and their compliance to hifiberry? I am interested in more people using Android builds for audio, so why not notify them that you have the solution. What I read, is that they are pointing to Google builds using a different Linux kernel and therefore, too much work, etc

No, I don't have Asus Tinkerboard so I can't provide any builds for it either.

Drivers for that DAC are not enabled on my current builds. I can have them enabled for future LineageOS 18/19 builds for the Pi 4. For other builds you're on your own. E.g. for LineageOS 17 on Pi 3 you would need to compile the kernel (build steps: https://github.com/lineage-rpi/android_kernel_brcm_rpi/issues/10#issuecomment-739346981) with the drivers enabled (https://github.com/lineage-rpi/andr...ch/arm/configs/lineageos_rpi3_defconfig#L3391 & https://github.com/lineage-rpi/andr...ch/arm/configs/lineageos_rpi3_defconfig#L3561), set audio device to DAC in settings, and modify config.txt (dtoverlay=i-sabre-q2m instead of dtoverlay=hifiberry-dacplus).

I only have 4GB model to test but unlikely there is much difference in general performance to the 2GB one (mostly affects multi-tasking performance).

CBA to sign up and comment on Hifiberry forum. It's up to people to do their own research or stay ignorant. In any case this doesn't require any effort from Hifiberry or even something that they could really do something about (without providing their own Android based OS). Kernel used in my Android builds is a merge of Raspberry Pi kernel (https://github.com/raspberrypi/linux) and AOSP reference kernel (https://android.googlesource.com/kernel/common/) so the kernel drivers for the DACs are already there as they are included in the Raspberry Pi kernel.

 

[chjanson]

No, I don't have Asus Tinkerboard so I can't provide any builds for it either.

Drivers for that DAC are not enabled on my current builds. I can have them enabled for future LineageOS 18/19 builds for the Pi 4. For other builds you're on your own. E.g. for LineageOS 17 on Pi 3 you would need to compile the kernel (build steps: https://github.com/lineage-rpi/android_kernel_brcm_rpi/issues/10#issuecomment-739346981) with the drivers enabled (https://github.com/lineage-rpi/andr...ch/arm/configs/lineageos_rpi3_defconfig#L3391 & https://github.com/lineage-rpi/andr...ch/arm/configs/lineageos_rpi3_defconfig#L3561), set audio device to DAC in settings, and modify config.txt (dtoverlay=i-sabre-q2m instead of dtoverlay=hifiberry-dacplus).

I only have 4GB model to test but unlikely there is much difference in general performance to the 2GB one (mostly affects multi-tasking performance).

CBA to sign up and comment on Hifiberry forum. It's up to people to do their own research or stay ignorant. In any case this doesn't require any effort from Hifiberry or even something that they could really do something about (without providing their own Android based OS). Kernel used in my Android builds is a merge of Raspberry Pi kernel (https://github.com/raspberrypi/linux) and AOSP reference kernel (https://android.googlesource.com/kernel/common/) so the kernel drivers for the DACs are already there as they are included in the Raspberry Pi kernel.

Thanks for info. I will order a RPI4 today. Please notify me when the AudioPhonics 9038 HAT DAC is included; (chj at hdsoundlab.com) or here. In addition to the 9038 I linked, there is a previous model 9028, probably the same driver. THey are very similar in formfactor and all except the DAC chip (check with David at support@audiophonics.fr). When things are working I will notify HifiBerry, because:

EDIT: Testing RoPieee, it has selector for HAT DACs, and all the AudioPhonics DACs are on the same selector, as "Audiophonics 90x8..."

If your Android PI4 runs like Android on a modern mobile device, it will for some (me at least) be a better choice than the alternatives; dedicated PI build images for Roon, for Volumio, etc, because Android would run them all per your preference. And then there is UAPP, the Android USB player. Excellent on my LG V50 and the most popular app for USB playback (or system audio, for example HifiBerry). I think this solution will be interesting to many audiophile users, and that the lack of focus on this solution is because your solution is not sufficiently known. I shall be the audiophile trial-rabbit. I also have my own DSP app that would be invited (soundpimp.com in android version)

One downside with RPI Android builds is the manual install of Google Play. A swifter solution would be to have a toogle: Google play ON/OFF in the Android settings. ON to download and occassional update, and OFF for purist "no noise" audio playback, i.e. most of the time for the case of audio playback. Just an idea. And as I said, when disabling Google play, RPI3 is acceptable, and it WILL work just fine for audio only. I have tested today with a Volumio-only image, and it equals any other setup I have in audio quality. Also the Audiophonics DACS (and others) are excellent. Very close to high-end audio, granting a bargain when the cost is simply RPI+DAC.

 

[rabbited]

Here is the logcat, same results as before and I've included the init.rpi4.rc file that I used as well.

logcat_init.rtf

drive.google.com

init.rpi4.rc

drive.google.com

 

[KonstaT]

Thanks for info. I will order a RPI4 today. Please notify me when the AudioPhonics 9038 HAT DAC is included; (chj at hdsoundlab.com) or here. In addition to the 9038 I linked, there is a previous model 9028, probably the same driver. THey are very similar in formfactor and all except the DAC chip (check with David at support@audiophonics.fr). When things are working I will notify HifiBerry, because:

EDIT: Testing RoPieee, it has selector for HAT DACs, and all the AudioPhonics DACs are on the same selector, as "Audiophonics 90x8..."

If your Android PI4 runs like Android on a modern mobile device, it will for some (me at least) be a better choice than the alternatives; dedicated PI build images for Roon, for Volumio, etc, because Android would run them all per your preference. And then there is UAPP, the Android USB player. Excellent on my LG V50 and the most popular app for USB playback (or system audio, for example HifiBerry). I think this solution will be interesting to many audiophile users, and that the lack of focus on this solution is because your solution is not sufficiently known. I shall be the audiophile trial-rabbit. I also have my own DSP app that would be invited (soundpimp.com in android version)

One downside with RPI Android builds is the manual install of Google Play. A swifter solution would be to have a toogle: Google play ON/OFF in the Android settings. ON to download and occassional update, and OFF for purist "no noise" audio playback, i.e. most of the time for the case of audio playback. Just an idea. And as I said, when disabling Google play, RPI3 is acceptable, and it WILL work just fine for audio only. I have tested today with a Volumio-only image, and it equals any other setup I have in audio quality. Also the Audiophonics DACS (and others) are excellent. Very close to high-end audio, granting a bargain when the cost is simply RPI+DAC.

Sure I can ping you here if/when there's another build available. It's of course always possible to compile the kernel if you don't want to wait for that.

Though we're getting audio out of the DACs not sure if it's for audiophiles. Android audio implementation used with the DACs only supports PCM 16-bit stereo audio with 44.1/48 kHz sampling rate.

It is not possible to include any Google services in my builds because of licensing. Having Google services installed is really not any problem on Pi 4. Pi 3 is just extremely limited on the memory (doesn't come even close to meeting the requirements for modern Android devices).

 

[KonstaT]

Here is the logcat, same results as before and I've included the init.rpi4.rc file that I used as well.

logcat_init.rtf

drive.google.com

init.rpi4.rc

drive.google.com

Ugh, that log is like 500 pages long. Please try to narrow it down e.g. starting from launching the browser app (and please also use regular text file format).

That init.rpi4.rc looks fine. There's no longer the trace_marker related crash in the log.

 

[amalgamat]

Hello - love these builds so thanks so much for your time on this. Quick one on the Microphone support... I've tried both the latest 19.0 and 18.1 and no matter what i do I can't get any input from the 3.5mm jack, two USB cameras with mics though camera works fine (tried a generic one and a logitech c920) , a stand alone USB microphone, a powered Snowball usb microphone. App permissions are fine. I've tried microphone recording apps, zoom, teams, chrome browser that shows the USB microphone as detected but no sound is recorded. I've installed magisk and looked for addins. Is there some toggle somewhere or line item in the config file i need to change? Any help would be appreciated.

 

[KonstaT]

Hello - love these builds so thanks so much for your time on this. Quick one on the Microphone support... I've tried both the latest 19.0 and 18.1 and no matter what i do I can't get any input from the 3.5mm jack, two USB cameras with mics though camera works fine (tried a generic one and a logitech c920) , a stand alone USB microphone, a powered Snowball usb microphone. App permissions are fine. I've tried microphone recording apps, zoom, teams, chrome browser that shows the USB microphone as detected but no sound is recorded. I've installed magisk and looked for addins. Is there some toggle somewhere or line item in the config file i need to change? Any help would be appreciated.

Raspberry Pi doesn't have any built-in hardware for audio input. 3.5mm jack doesn't have mic so that is obviously not going to work.

I've tested both my USB sound card with mic input and mic on my USB webcam and both work fine. USB audio level might be low so make sure to increase that from the settings as it also seems to affect the USB mic level.

 

[amalgamat]

Raspberry Pi doesn't have any built-in hardware for audio input. 3.5mm jack doesn't have mic so that is obviously not going to work.

I've tested both my USB sound card with mic input and mic on my USB webcam and both work fine. USB audio level might be low so make sure to increase that from the settings as it also seems to affect the USB mic level.

thanks for that, hadn't realised the 3.5mm was audio out only. all the microphones work fine with sound recorder (hadn't used that to test doh) so it might just be something to do with chrome, teams and zoom. i'll play around with it some more. ta.

 

[Ozi1100]

Hi,

i downloaded and flasehd the latest os19 to a 16gb sd card. I am using the rpi 7inch touchscreen and therefore i have changed the resolution.txt and uncommented dtoverlay=vc4-kms-dsi-7inch in config.txt. Everytime I end up with the rainbow screen and after that black screen. I tryed differend settings but the 7inch display wont work.

Is there something else I can try? I dont have a micro hdmi cable to change the resolution in the os - but if there is no other way i will buy one.

 

[KonstaT]

Hi,

i downloaded and flasehd the latest os19 to a 16gb sd card. I am using the rpi 7inch touchscreen and therefore i have changed the resolution.txt and uncommented dtoverlay=vc4-kms-dsi-7inch in config.txt. Everytime I end up with the rainbow screen and after that black screen. I tryed differend settings but the 7inch display wont work.

Is there something else I can try? I dont have a micro hdmi cable to change the resolution in the os - but if there is no other way i will buy one.

Are you sure you've tested the latest release (20211216) which is the first one that comes with Linux 5.10 kernel by default?

As stated in the FAQ there is a settings option to enable the configurations for the official 7" display so you also need to have another display. If you want to enable these configurations manually, there's two things to do - uncomment 'dtoverlay=vc4-kms-dsi-7inch' in /boot/config.txt & set 800x480 in /boot/resolution.txt (or remove the file altogether). You also need to change display density to adjust to the smaller display resolution somehow (go and enable the settings option as it also does this for you).

 

[Ozi1100]

Are you sure you've tested the latest release (20211216) which is the first one that comes with Linux 5.10 kernel by default?

Yes, I tryed now again, fresh download of os19, changed config.txt and resolution.txt. I get a rainbow and dann blackscreen (flashing once from white to black). I hoped to find a way where I dont had to buy a micro hdmi cable ..

 

[KonstaT]

Yes, I tryed now again, fresh download of os19, changed config.txt and resolution.txt. I get a rainbow and dann blackscreen (flashing once from white to black). I hoped to find a way where I dont had to buy a micro hdmi cable ..

Impossible to say without seeing any logs. I broke my official 7" display a while back so I can't test. Those are the same changes the settings option does (you can also check /vendor/bin/rpi4-touchscreen.sh) and it's been reported working by other people.

 

[kevinygod]

how cn i fix this erorr on pixel experience 12

rares@ASUS-VivoBook-X509FL:~/pixel$ make ramdisk systemimage vendorimage
build/make/core/soong_config.mk:196: warning: BOARD_PLAT_PUBLIC_SEPOLICY_DIR has been deprecated. Use SYSTEM_EXT_PUBLIC_SEPOLICY_DIRS instead.
build/make/core/soong_config.mk:197: warning: BOARD_PLAT_PRIVATE_SEPOLICY_DIR has been deprecated. Use SYSTEM_EXT_PRIVATE_SEPOLICY_DIRS instead.
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=12
TARGET_PRODUCT=rpi4
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=cortex-a72
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.4.0-90-generic-x86_64-Linux-Mint-20.2
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=SD1A.210817.036
OUT_DIR=out
PRODUCT_SOONG_NAMESPACES=external/mesa3d
============================================
[100% 1/1] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja
FAILED: out/soong/build.ninja
cd "$(dirname "out/soong/.bootstrap/bin/soong_build")" && BUILDER="$PWD/$(basename "out/soong/.bootstrap/bin/soong_build")" && cd / && env -i "$BUILDER" -
-top "$TOP" --out "out/soong" -n "out" -d "out/soong/build.ninja.d" -t -l out/.module_paths/Android.bp.list -globFile out/soong/.bootstrap/bui
ld-globs.ninja -o out/soong/build.ninja --available_env out/soong/soong.environment.available --used_env out/soong/soong.environment.used Android.bp
error: hardware/interfaces/neuralnetworks/aidl/utils/Android.bp:48:1: "neuralnetworks_utils_hal_aidl_test" depends on undefined module "neuralnetworks_utils_d
efaults"
16:05:29 soong bootstrap failed with: exit status 1

#### failed to build some targets (5 seconds) ####

rares@ASUS-VivoBook-X509FL:~/pixel$

Same error for me

 

[Ozi1100]

Impossible to say without seeing any logs. I broke my official 7" display a while back so I can't test. Those are the same changes the settings option does (you can also check /vendor/bin/rpi4-touchscreen.sh) and it's been reported working by other people.

I tryed with an nother power cable and now it works with the 7"touch.

Some apps (i.e. radio.net) have a small resolution - looks like it showing in portrait and not landscape.

 

[KonstaT]

I tryed with an nother power cable and now it works with the 7"touch.

Some apps (i.e. radio.net) have a small resolution - looks like it showing in portrait and not landscape.

This build forces default (landscape) orientation because usually we're using displays that don't rotate. If you want to change this behavior, you can set 'config.override_forced_orient=true' in /vendor/build.prop. You can also rotate the display from Settings -> System -> Advanced settings -> Display rotation.

 

[Ozi1100]

Is there a problem with audio streaming through bluetooth? I have tryed to play audio over bluetooth on my car radio and it has some cut offs.

 

[gavranpero]

Greeting. I installed Android 12 on Rpi4 and connected the Sony WH-1000XM3. When I checked which audio codec was being used, it says LDAC. So not only Rpi, but the headphones are currently working on that codec, while they are connected to Rpi. How is that possible ?

 

[SilverS4sAreFaster]

So I know to make the MPU6050 work I have to remove the # on #dtoverlay=android-i2c-sensor,mpu6050, I've done that and had my other sensor working fine however it's an MPU9265 technically and the compass on it doesn't report since the software wasn't setup for it. I want the compass to work so I got a LSM303DLHC since it was theoretically plug and play. I then tried writing a line dtoverlay=android-i2c-sensor,lsm303dlhc thinking it needed that to look for the input from the sensor. Unfortunately I've had no luck, I've even tried using the 6050 line again just to see if the accelerometer data might be there but of course that doesn't work. I got a 2nd one thinking maybe it was defective but unfortunatly it still isn't working. The one from adafruit is no longer available... I may have one that for one reason or another isn't compatible I don't really know, or maybe I have no idea what I'm doing? It says it uses the LSM303DLHC sensor but the board is calling itself a GY-511, it still has the correct pins however and I figured if the chip on board is correct then the rest of the stuff is just the power conditioning and should still connect properly over the I2C data paths.

 

[KonstaT]

Is there a problem with audio streaming through bluetooth? I have tryed to play audio over bluetooth on my car radio and it has some cut offs.

There is a know issue with bluetooth audio and Google location services after installing gapps. This 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 workaround available if disabling Google location access is not enough https://xdaforums.com/t/dev-rom-uno...aspberry-pi-4-b.4212945/page-14#post-85769441

Greeting. I installed Android 12 on Rpi4 and connected the Sony WH-1000XM3. When I checked which audio codec was being used, it says LDAC. So not only Rpi, but the headphones are currently working on that codec, while they are connected to Rpi. How is that possible ?

It means nothing. Bluetooth codec options in developer options are no-op.

Edit. LDAC should work, see https://xdaforums.com/t/dev-rom-uno...raspberry-pi-4-b.4356891/page-7#post-86219431

So I know to make the MPU6050 work I have to remove the # on #dtoverlay=android-i2c-sensor,mpu6050, I've done that and had my other sensor working fine however it's an MPU9265 technically and the compass on it doesn't report since the software wasn't setup for it. I want the compass to work so I got a LSM303DLHC since it was theoretically plug and play. I then tried writing a line dtoverlay=android-i2c-sensor,lsm303dlhc thinking it needed that to look for the input from the sensor. Unfortunately I've had no luck, I've even tried using the 6050 line again just to see if the accelerometer data might be there but of course that doesn't work. I got a 2nd one thinking maybe it was defective but unfortunatly it still isn't working. The one from adafruit is no longer available... I may have one that for one reason or another isn't compatible I don't really know, or maybe I have no idea what I'm doing? It says it uses the LSM303DLHC sensor but the board is calling itself a GY-511, it still has the correct pins however and I figured if the chip on board is correct then the rest of the stuff is just the power conditioning and should still connect properly over the I2C data paths.

There is a settings option in Settings -> System -> Advanced settings -> Sensors. You should use that for the supported sensors instead of modifying config.txt manually. Edit. Besides, it's 'dtoverlay=android-i2c-sensor,lsm303dlhca,lsm303dlhcm' for this sensor module.

Check 'dmesg' and 'i2cdetect -y 1' (in rooted shell) to see that your sensor module is detected and what I2C address is uses. If your sensor module uses different I2C address than expected (https://github.com/lineage-rpi/andr...erlays/android-i2c-sensor-overlay.dts#L43-L71) it can also be configured in the config.txt.

 

[gavranpero]

It means nothing. Bluetooth codec options in developer options are no-op.

So that's not a real LDAC?