yashsingh1/xdaforums huggingface dataset:
[Raspberry Pi Original Development] KonstaT:
v24.3 works just fine and there's no reason why you would need newer Magisk for this. Updating it to the latest version is somewhere in my TODO but there's no immediate plans.

Raspberry Pi doesn't have boot.img (as it's not an Android device to begin with).

If you must have this now, you can create boot.img from kernel (Image) and ramdisk.img (both on the boot partition) using 'mkbootimg' tool -> patch boot.img with Magisk -> split patched boot.img using 'unpackbootimg' -> replace ramdisk.img on the boot partition with the Magisk patched one.
[Raspberry Pi Original Development] juniorhero:
thanks

i need to remove TWRP completely. it is causing root detection in android.

i could not find /twrp directory. where is it location

need help
[Raspberry Pi Original Development] KonstaT:
It's not. There's no way any app would know what recovery you have. There's other means to check device integrity but that's not one of them.

TWRP is /boot/ramdisk-recovery.img.
[Raspberry Pi Original Development] juniorhero:
ok

I am getting following issues in the rom

selinux permissive

data not encrypted, mount parameters are modified

seccomp is disabled

debugging mode is enabled

Is there anyway to fix the ROM ?

i am curious to also know if rom is released as such with all security features disabled
[Raspberry Pi Original Development] KonstaT:
Sorry but you're mistaken if you think that custom AOSP builds are about security. Even your "regular" Android device is compromised the moment you unlock the bootloader. If security is something that you're interested in, you might want to look into GrapheneOS or CalyxOS that allow you to relock the bootloader. AFAIK this option is currently only available on Pixel devices, though.

Raspberry Pi is completely different animal as it's not even Android device to begin with. My goal is to keep the device customizable/hackable for the end user as well. Android has four major security features from device perspective. On Raspberry Pi these would only prevent all the things that are fun. :)

1. Bootloader

Unlocking the bootloader allows to boot unsigned boot/recovery images. Raspberry Pi is not an Android device to begin with so my builds don't have Android bootloader or even traditional Android boot/recovery images. This is the main security feature as unlocked bootloader allows to boot any boot/recovery image (e.g. TWRP) where you'll have root access i.e. basically full access on the device.

2. dm-verity / Android Verified Boot (AVB)

Verifies that system/vendor partitions are unmodified. dm-verity is disabled on all custom ROMs (excluding the two mentioned above) as you wouldn't be able to install gapps or make any other modifications to system/vendor partitions.

3. SELinux

Enforces access control for system processes. Like noted under 'Issues' SELinux is in permissive mode in my builds so it only logs any denials. There wouldn't too much work for SELinux enforcing but it easily gets away e.g. whenever trying to add support for a new piece of external hardware.

4. data encryption

Contents of userdata can't be read without decrypting the partition with the right pin/password/etc from the user. Not enabled by default on my builds but userdata can be encrypted from Settings -> Security > Encryption and credentials -> Encrypt tablet. Prevents e.g. mounting the sdcard on your Linux machine and making changes on data partition which is something I want to do on occasions.

And USB debugging can be disabled from developer options of course (there's was upstream issue on AOSP/LineageOS which left this enabled by default https://review.lineageos.org/c/LineageOS/android_build/+/330448).
[Raspberry Pi Original Development] juniorhero:
ok

I am getting following issues in the rom

selinux permissive

data not encrypted, mount parameters are modified

seccomp is disabled

debugging mode is enabled

Is there anyway to fix the ROM ?

i am curious to also know if rom is released as such with all security features disabled

cool

thanks for explanation.

i have observed that flashing MindTheGapps zip with twrp is causing root detection in apps. I did not install magisk nor rooted my devices

i am trying to avoid root detection

any other Gapps or alternative way to do this
[Raspberry Pi Original Development] KonstaT:
I doubt that would be the case either. SafetyNet API is part of Google Play services of course (i.e. only available after installing gapps) but in that case I doubt such apps would work without Play services to begin with.

Ironically you would install Magisk and use whatever is currently the best method it offers for hiding root (you would need to check Magisk forums/discussion about that because I'm not keeping up). I updated my Magisk installer to v25.1 today BTW.
[Raspberry Pi Original Development] juniorhero:
ok

i have magisk v25.1 running fine now

so i need to run Shamiko a magisk module best method to hide root https://github.com/LSPosed/LSPosed.github.io/releases

i tried but i am getting sepolicy error on magisk module installation. i tried it on other devices with latest magisk, everywhere else no sepolicy error

please help me out
[Raspberry Pi Original Development] KonstaT:
Thanks for the report. There was some sepolicy changes in Magisk v25.x.

You can try using an older version. https://androidfilehost.com/?w=files&flid=329389

You can't patch the ramdisk again with the installer. If you don't want to start with a clean installation again you need to restore the original unpatched ramdisk (copy /boot/ramdisk-orig.img as /boot/ramdisk.img).
[Raspberry Pi Original Development] juniorhero:
i tried older versions of magisk, i got same error

do you have zip for magisk v23?

how to generate magisk zip for same?
[Raspberry Pi Original Development] KonstaT:
In the same folder (lineage-19.0-rpi-magisk-v23.0.zip). These are the same even between different Android versions so the tagged LineageOS version doesn't matter.
[Raspberry Pi Original Development] LVSasquatch:
Hi there, I'm having an issue getting it to load at all. I have the 2gb Res Pi 4 module B. I'm using the Ras Pi 7" touchscreen. I've tried flashing from windows 10 and for the pi itself using twister os on a thumb drive and have the same problem. I've also tried different versions of 19 and 18 of your build. what happens is when I go to boot it up I get a screen that transition from black to white then back to black. It's like it's trying to displaying a splash screen but it's just white. Then nothing else happens. I can see that the screen is no but it's not displaying anything. What sort of stupid thing am I missing to make this work?
[Raspberry Pi Original Development] juniorhero:
why Hardware video decoding & encoding not working?
[Raspberry Pi Original Development] LVSasquatch:
How did you get the 800x480 screen to work? I can't only get it to work if it's hook via HDMI to my 1080p monitor. I tried moding the resolution file to 800x480 and deleting all together that didn't work. Did you have to make changed to the config.txt file?
[Raspberry Pi Original Development] KonstaT:
Please read the FAQ on how to use the official 7" DSI display. There's a settings option that you need to enable to make the required changes to configs.

There's already support for very experimental H.264 hw video decoding. Current issue with it is that hw codecs on Pi don't produce linear buffers but use their on own tiling modifier instead.

Raspberry Pi has a stateless H.265 hw decoder so that's currently not in the scope with v4l2_codec2 that is used on Android.
[Raspberry Pi Original Development] heist82:
This is my config file:

the main bot to get it working was this i beleive:

# Display panel

[gpio21=1]

#dtoverlay=cutiepi-panel

dtoverlay=vc4-kms-dsi-7inch

#dtoverlay=vc4-kms-dsi-lt070me05000

#dtoverlay=vc4-kms-dsi-lt070me05000-v2

[all]

dtoverlay=rpi-backlight

# 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]

# Display panel
[gpio21=1]
#dtoverlay=cutiepi-panel
dtoverlay=vc4-kms-dsi-7inch
#dtoverlay=vc4-kms-dsi-lt070me05000
#dtoverlay=vc4-kms-dsi-lt070me05000-v2
[all]
dtoverlay=rpi-backlight

# Fan
#dtoverlay=gpio-fan
#dtoverlay=rpi-poe
#dtoverlay=rpi-poe-plus

# Graphics acceleration
[gpio21=1]
dtoverlay=vc4-kms-v3d
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=edt-ft5406
#dtoverlay=goodix

# USB
dtoverlay=dwc2,dr_mode=peripheral
[cm4]
dtoverlay=dwc2,dr_mode=otg
[all]

# V4L2
#dtoverlay=rpivid-v4l2
[Raspberry Pi Original Development] KonstaT:
Which is exactly what you'd have after enabling Settings -> System -> Raspberry Pi settings -> Touchscreen. In addition this will change /boot/resolution.txt to 800x400.

So, it's just best use a HDMI display first and enable the option for the official display. This way these config changes are also persisted over OTA updates.
[Raspberry Pi Original Development] KonstaT:
Yes, still stuck with Linux 5.4 kernel (which by all means is not old if you consider Android devices in general). Would love to switch to 5.10 but having no HDMI audio is a pretty big show stopper. Recent developments with hw video dec/enc and libcamera also require 5.10 kernel so we'll see if it would make sense to make some more bleeding edge release at some point.

Having recent logs would be very useful if this is even the same issue as previously.

Disabling wifi scanning is not the correct way to address this issue in any case.

There's an option for display rotation in Settings -> System -> Advanced settings -> Display rotation. Landscape is by default anyway so it should be just as easy as before. LineageOS 19 doesn't yet have any power menu options.

LineageOS 19 doesn't yet have setup wizard so the image boots directly to home screen.
[Raspberry Pi Original Development] Sinedan:
Hello,

I would like to connect a hard disk with the file system NTFS. Unfortunately it is not recognized!

What do I have to do so that the hard drive is recognized?

Cheers
[Raspberry Pi Original Development] KonstaT:
You need to reformat your drive. NTFS is a proprietary WIndows file system and Android doesn't have native support for it.

Only FAT32 external drives are currently supported with this build (exFAT support was added to LineageOS 19 after this build so it will be supported if/when there's another build). You can use both FAT32 and exFAT drives on current LineageOS 18 builds.
[Raspberry Pi Original Development] rabbited:
I can try to get a logcat sometime in the next week, but it's definitely the same issue. Behavior is identical to previous versions and boot loop goes away when disabling wifi in the config file at which point Lineage works without issue.
[Raspberry Pi Original Development] Sinnedan:
Hello KonstaT and thank you very much.

I would like to create an Android TV with a multimedia hard drive (movies, series,...).

This hard drive unfortunately has NTFS because files over 4GB can be used there, but if I'm not mistaken, exFAT can do that too.

Before I change the file system, I decided to use "NTSF for Android" from Paragon. I also use that on my MacBook Pro.

But since I also had problems with NordVPN with the 19.0 Built, I will take another version. Due to the regular updates, it should then be the 18.1 ATV, since the last update there was on 26.10.21.

See you soon in the 18.1 thread... ;)

Cheers
[Raspberry Pi Original Development] KonstaT:
New build. Added optional Linux 5.10 kernel add-on to test a lot of WIP stuff.

LineageOS 19 (Android 12L)

for Raspberry Pi 4

konstakang.com

-add option to show virtual volume down, volume up, and power keys on navigation bar (requires reboot)

-add option for old TCP-based ADB over network

-show IP address and port for ADB/SSH/VNC options

-update to TWRP 3.6.0_11-0-KonstaKANG

-update to Mesa 21.3.0

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

-Android security patch level: 5 November 2021 (merged)

Linux 5.10 kernel: (optional add-on)

-various KMS driver improvements (DSI panel support, etc)

-support for Pi camera modules using libcamera, preview & photos work - camcorder doesn’t (thanks to Roman Stratiienko)

-option to test currently very WIP H.264 hardware video decoding using v4l2_codec2 (Settings -> System -> Advanced settings -> Hardware video decoding)

-HDMI audio is not supported! (see issue #4651 & issue #4654)

-new Raspberry Pi Android kernel bring-up based on AOSP android12-5.10-lts

-update to Linux 5.10.81 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
[Raspberry Pi Original Development] Dark98:
Is auto rotate working with the use of an MPU6050 sensor?
[Raspberry Pi Original Development] KonstaT:
Yes, seems to work fine with 5.4 kernel that comes by default with the image.

Already noticed that MPU6050 temperature reading is not working with 5.10 kernel but also the accelerometer and gyroscope seem to stop working after a while. Something to look into. Most likely just needs some tuning with with the sensor HAL (https://github.com/lineage-rpi/android_hardware_intel_sensors-iio/blob/lineage-19.0/README#L205-L228).
[Raspberry Pi Original Development] EpicLPer:
Trying to use the official touchscreen with the 5.10 Kernel addon but it doesn't seem to want to use it as an output. Anything I need to do still after flashing it?
[Raspberry Pi Original Development] KonstaT:
Yes, uncommenting 'dtoverlay=vc4-kms-dsi-7inch' in /boot/config.txt is the bare minimum at least. You also need to change display density to adjust to the smaller display resolution and I can't recall if it is absolutely necessary to do something with /boot/resolution.txt.

There is also a script included that takes care of all of this (and I'll add settings option for this if/when this is confirmed working).

su
rpi4-touchscreen.sh raspberry

I broke my official 7" display a while back so I'd appreciate if someone could test it and report back. It was working before with 5.10 kernel so everything should be there. There's a list of things to test like does booting into/out of TWRP also work, does touch work in TWRP, and does adjusting brightness work in both Android & TWRP.
[Raspberry Pi Original Development] EpicLPer:
Yeah sure, I can test this :) But where is that script located exactly? I can't seem to find it.

EDIT: Ah, found it in /vendor ! Ran that now, lets see if it worked.
[Raspberry Pi Original Development] EpicLPer:
Official Touchscreen - Found Issues:​

Once the Pie went into Standby (locked) and then woken up by a keyboard the touch inputs are not registered anymore. actually it does seem to register touch in this state still, cause when the screen starts dimming and I touch the screen it'll go full bright again, however it doesn't "touch" anything on screen anymore.

That said you also can't wake up the Pi anymore via the touchscreen once the screen locks/goes black, you have to use a keyboard or presumably the GPIO button (which I didn't test).

----------

TWRP on the touchscreen works without any detectable issues whatsoever :) Touch works, brightness works and it even correctly uses the 800x480 resolution and DPI scale from the build.prop!
[Raspberry Pi Original Development] KonstaT:
Great, thanks for testing! :)

There was a similar report on my site with an USB touchscreen so it seems more general issue. I have an USB touchscreen I can use to test so I'll look into this when I get around.
[Raspberry Pi Original Development] SuperPi911:
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$
[Raspberry Pi Original Development] EpicLPer:
Think I found another issue with the official touchscreen.

When booting up into TWRP by attaching a power button and holding it the touch doesn't seem to work. You do get an output, but none of the touch inputs seem to work.

UPDATE: Tested this a bit more. Touch-Inputs only work when you set the TWRP-Reboot-Option inside Android first. It doesn't matter if you simply reboot or shut the Pi down fully and then enter TWRP, touch still works that way. It only stops working when you use the power button method which seems weird...

Also the brightness in Android can go way too low to a point where you'll not be able to see anything on screen anymore at around the 1/8 mark. Should probably be capped out to not accidentally "lock yourself out". In TWRP the lowest brightness is still okay and you can see enough.
[Raspberry Pi Original Development] KonstaT:
Thanks.

Yep, 'dtoverlay=edt-ft5406' in /boot/config.txt doesn't get enabled if you boot into TWRP with the power button. It's only needed to enable the touchscreen driver if 'dtoverlay=vc4-kms-dsi-7inch' is not already set (TWRP doesn't use hw accelerated graphics so it needs to be enable there). I also use it to check if you're using the 7" display and re-enable 'dtoverlay=vc4-kms-dsi-7inch' when booting out of recovery so not sure how I would handle this.

I've already set reasonable values for the minimum brightness but for some reason they are not respected. Brightness shouldn't go below '20' but for some reason it does (you can use 'cat /sys/class/backlight/rpi_backlight/brightness' to check). Values that the slider write are also far from linear. I'll look into this when I get around.
[Raspberry Pi Original Development] jeff862:
no audio for spotify , deezeer etc using usb dac .lineage 19 please help
[Raspberry Pi Original Development] jeff862:
How to uninstall kernel 5.10?
[Raspberry Pi Original Development] Dark98:
Are multiple I2C Devices supported at once? I'm using a PiSugar Pro 2 & I tried An MPU6050 but the pi doesn't seem to detect the MPU6050
[Raspberry Pi Original Development] KonstaT:
Why would you expect to get any different response than the last time you posted the exact same thing?

Sorry, don't even bother if your only input is "doesn't work" without any additional information.

By restoring a backup you made in TWRP before you started modifying your system or by reflashing the image (or by looking what the 5.10 kernel patch does and figuring it out).

Yes, you can use various I2C devices at the same time (as long as each have individual address - I2C address space is 2^7 minus some reserved addresses so theoretically little over 100 devices).

You need to enable MPU6050 from Settings -> System -> Raspberry Pi settings -> Sensors first to use it of course.

Use this to check what I2C devices are detected and at which address.

su
i2cdetect -y 1
[Raspberry Pi Original Development] uukelele:
Hi there,

I installed Lineage on my pi with an sd card that has 64GB of storage. But in the settings app it only shows 8GB of storage available. Is there anything I have to do to use the full 64GB?
[Raspberry Pi Original Development] iroiroiro:
What Widevine Security Level has this ROM?
[Raspberry Pi Original Development] KonstaT:
Yes. Please read the FAQ on how to extend the data partition.

L3.
[Raspberry Pi Original Development] uukelele:
I'm using Waveshare touchscreen model B and I see the rainbow screen then black. I know the hdmi cable is fine with EDID, and the touchscreen works fine on non-EDID operating systems. So, is there any way to use Lineage without an EDID display? Maybe editing something in config.txt...
[Raspberry Pi Original Development] KonstaT:
You can add custom EDID firmware to the kernel by appending /boot/cmdline.txt with 'drm_kms_helper.edid_firmware=edid/{your_edid_firmware}.bin'. In some cases this would require creating a custom EDID firmware for your display and compiling the kernel. See https://github.com/lineage-rpi/android_device_brcm_rpi4/issues/4
[Raspberry Pi Original Development] M10360:
Is it possible to use this 4G sim hat: Waveshare SIM7600X which accepts standard AT commands via UART on GPIO pins 8 & 10? Can the RIL be configured to talk on these pins?
[Raspberry Pi Original Development] KonstaT:
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. I have builds that have support 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.

Some 3G/LTE USB dongles have been reported working using third party apps (e.g. https://play.google.com/store/apps/details?id=de.draisberghof.pppwidget3).
[Raspberry Pi Original Development] KonstaT:
New build.

LineageOS 19 (Android 12L)

for Raspberry Pi 4

konstakang.com

add option to restrict new USB connections

add option for left-handed mouse

include Raspberry Pi userland tools (vcgencmd, etc) and libdrm modetest

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

Android security patch level: 5 August 2022 (merged)
[Raspberry Pi Original Development] Starfoxfs:
Hi,

simple Question, can your build Passthrough Dolby TrueHD or DTS-HD MA over HDMI if Kodi or Plex TV is installed on top ?

What Widevine DRM Level can this decode ?
[Raspberry Pi Original Development] KonstaT:
Simple answer, no.

L3 as already answered previously on this page.
[Raspberry Pi Original Development] Starfoxfs:
Ok thanks