yashsingh1/xdaforums huggingface dataset:
[Raspberry Pi Original Development] OdeMix:
As you can check my post, I am using an SSD disk. Therefore, the choice of the SD card cannot affect the stability of the system. As a power source, there is a DC-DC converter 12 to 5 Volts at 15 amperes. Unfortunately, I was unable to save the error log while I can show a couple of photos.

Before resizing of the partition "userdata" there were no reboots or freezes. The battery in the car has run out while I was playing with the disk partitions, maybe more information tomorrow. If you need.

Spoiler content hidden.
[Raspberry Pi Original Development] KonstaT:
You can e.g. 'cat /tmp/resize.log' in TWRP terminal to check what went wrong.

There shouldn't be any unallocated space on the disk after resizing.

I still don't see how this would have any effect on system stability.
[Raspberry Pi Original Development] OdeMix:
I was wrong. Resizing of disk partition is not cause of reboots and freezes. I did it again. Only this time I did not try to use the script, but immediately increased the userdata partition using GParted. After that, everything worked stably. Problems started after installing Gaps.

I will continue to observe and try to fix it.
[Raspberry Pi Original Development] aliabadi97:
Hi, I downloaded the source by adding manifest to lineage manifest and after I try to build rom. But build system raise below error and I have no idea about it. what is wrong?

Also I send my instructions for build below.

my instructions:

lunch lineage_rpi4-userdebug
make installclean -j$(nproc --all)
rm -rf out/target/product/rpi4/lineage*.zip
rm -rf out/target/product/rpi4/system
rm -rf out/target/product/rpi4/obj/PACKAGING/target_files_intermediates/*
make bacon -j$(nproc --all)

And here is error of build system:

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=10
LINEAGE_VERSION=17.1-20210217-UNOFFICIAL-rpi4
TARGET_PRODUCT=lineage_rpi4
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm
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-65-generic-x86_64-Ubuntu-20.04.2-LTS
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=QQ3A.200805.001
OUT_DIR=out
PRODUCT_SOONG_NAMESPACES=device/brcm/rpi4 vendor/brcm/rpi4 device/brcm/rpi-common vendor/brcm/rpi-common
============================================
ninja: no work to do.
[ 0% 1/545] glob CertInstaller.prof
.
.
.
Starting ninja...
[100% 1053/1053] build bacon
FAILED: bacon
/bin/bash -c "(ln -f out/target/product/rpi4/lineage-17.1-20210217-UNOFFICIAL-rpi4.zip ) && (md5sum out/target/product/rpi4/lineage-17.1-20210217-UNOFFICIAL-rpi4.zip | sed \"s|out/target/product/rpi4/||\" > out/target/product/rpi4/lineage-17.1-20210217-UNOFFICIAL-rpi4.zip.md5sum ) && (echo \"Package Complete: out/target/product/rpi4/lineage-17.1-20210217-UNOFFICIAL-rpi4.zip\" >&2 )"
ln: cannot create hard link from 'out/target/product/rpi4/lineage-17.1-20210217-UNOFFICIAL-rpi4.zip' to './lineage-17.1-20210217-UNOFFICIAL-rpi4.zip': No such file or directory
ninja: build stopped: subcommand failed.
13:22:49 ninja failed with: exit status 1
[Raspberry Pi Original Development] KonstaT:
You can use the sources I've provided to build Linux kernel, other GPL licensed parts, graphics drivers, etc. Here's instructions on how to build the kernel: https://github.com/lineage-rpi/android_kernel_brcm_rpi/issues/10

Raspberry Pi is not an Android device to begin with so things are structured a bit differently. There's currently no TWRP flashable otapackages (i.e. 'make bacon''). You'd need to compile images for different partition separately and create an image with appropriate partition structure that you can write to sdcard/USB device. There's full source code with build instructions available for some LineageOS Pi 3 builds (e.g. https://github.com/lineage-rpi/android_local_manifest/tree/lineage-15.1).
[Raspberry Pi Original Development] sourabh.joshi:
I am unable to use WiFi Direct. Any help to get it started on the PI would be really appreciated.
[Raspberry Pi Original Development] risant:
can i use innomaker pi hat pcm5122 dac board on pi 4B android 10 system.. please help
[Raspberry Pi Original Development] KonstaT:
There is currently no support for wifi direct.

Yes, I'd expect that to work just fine. In addition to selecting Hifiberry DAC+ from Settings -> System -> Advanced settings -> Audio DAC, you would need to manually edit /boot/config.txt to enable the driver for your hardware (under Audio DAC section change 'dtoverlay=hifiberry-dacplus' -> 'dtoverlay=allo-boss-dac-pcm512x-audio').
[Raspberry Pi Original Development] risant:
thanks.. iam planning to buy innomaker pi hat dac PCM 5122.. will this sound better than USB spdif optical?
[Raspberry Pi Original Development] KonstaT:
Audio HAL supports 16-bit PCM audio with 44.1/48 kHz sampling rates.

I don't have any of the hardware you're talking about but I wouldn't expect there to be any difference.
[Raspberry Pi Original Development] aliabadi97:
Thanks!

now I have error in boot. After creating img file with your "mkimg" file, I create bootable sd-card from image and run rpi4 but it can't boot. it shows black screen and after some seconds reboots. But it works with your rom.

I downloaded your rom and after extraction I see there is some difference between "cmdline" and "config" files of my rom and yours. I have mentioned it below. Also kernel and ramdisk images show difference.

I also put your config.txt and cmdline instead of my files in bootable sd-card rom and no difference except now I see rainbow screen. And after some second it reboots!

do you have any idea?
[Raspberry Pi Original Development] lordloki77:
Hi konstat,

I'm having trouble where when audio comes on when a timer completes it causes the screen to go on and off and the system to go unresponsive. The audio is going hdmi out, if that matters.
[Raspberry Pi Original Development] lordloki77:
And to be clear, audio works generally. And both the standard clock app and another timer app have the same problem.
[Raspberry Pi Original Development] KonstaT:
Impossible to say what could be the issue without seeing any logs.

I tested alarms and timers with the stock clock app on LineageOS 18 (couldn't bother to flash LineageOS 17). Both work as expected even when the alarm/time is set off both the display on and display off.
[Raspberry Pi Original Development] stu.cz:
Hi.

Is there any chance to make composite output worked? I tried everything you wrote. Added "sdtv_mode=2" line, changed resoluton, deleted all HDMI lines. No screen at composite output.

When I started the rpi4 with enabled tvout it shows colored square at start and then just gray screen. But the TWRP recovery works with composite out very well.

Some idea?

Thank you very much.

Stu
[Raspberry Pi Original Development] KonstaT:
In that case (TWRP works) it will likely also work in Android if you switch to SwiftShader.

There could be issues with kernel KMS driver that is used with hardware accelerated graphics. I'm not sure what's the status of KMS with composite output or if there's any improvements on 5.10 kernel. Or hwcomposer doesn't know how to configure the composite output. Impossible to say what could be the issue without seeing any logs.

I ordered myself a composite video cable a while back. We'll see if/when it arrives.
[Raspberry Pi Original Development] MadJawa:
Hi, it's me again. I am trying to make a CarPlay screen for my car, it's working but I'm struggling with a few issues :

How can I entirely disable screen dimming? I'm using the raspberry 7in touch screen, and after a few minutes of inactivity, the screen dims. I didn't find any setting to disable it entirely

The audio volume resets to ~20% on boot. How can I set the setting and have it always at the same value? (I'd like to set it to 80%)

I'm using a USB soundcard, the audio output works, but not the microphone. Is there something to enable somewhere to enable the mic?

Thanks in advance.
[Raspberry Pi Original Development] KonstaT:
I think there's no specific setting for screen dimming. Screen dims some seconds before it's set to timeout (even if you've selected never sleep from developer options). Recent Android versions don't have 'Never' option for screen timeout either. You can still the increase timeout in Settings -> Display -> Sleep which also affects when the screen will dim.

You need to power off your device properly via the power menu instead of just pulling the power for the changes in Android volume levels to stick. If you mean USB audio, volume levels for external devices are reset on boot by design in Android. You can use some Tasker-like application to automate things like increasing volume on boot.

USB mic volume is quite low. Are you sure this isn't the case? Mic input on USB soundcards should work just fine at least mine does.
[Raspberry Pi Original Development] scottial:
Hi, i've installed latest OpenGapps, the voice search works, but Ok Google wont' work. I'm using an external USB audio card.
[Raspberry Pi Original Development] MadJawa:
Thanks for the answers. I was using a USB device indeed. Finally I ended up going the Raspbian way directly haha, Android is not that flexible for my carputer project.
[Raspberry Pi Original Development] KonstaT:
Have you enabled the feature in Google Assistant's settings?
[Raspberry Pi Original Development] scottial:
Do you means "Hey Google" slider? Yes, of course.
[Raspberry Pi Original Development] KonstaT:
Which gapps package have you installed? Google assistant is not included in the pico package.

IDK, could be some gapps issue otherwise. I think it's worked before at least. It's been reported working, I've seen it some YouTube video or something.
[Raspberry Pi Original Development] 2free:
All systems work for me normally

But Android 9.10.11 not boot

Raspberry pi 4b 8g + argon one case

is there a solution

thank you
[Raspberry Pi Original Development] KonstaT:
Quite impossible to say what could be the problem with the information you've provided ("not boot").

FAQ is usually a good place to start reading.
[Raspberry Pi Original Development] 2free:
This is what I meant

It stays like this black screen
[Raspberry Pi Original Development] scottial:
I've installed micro package
[Raspberry Pi Original Development] KonstaT:
There's a FAQ section about display issues. Have you read it? Have you tried what is instructed there?
[Raspberry Pi Original Development] andrewfblack:
So I have a PI 4 with 8GB ram and started this this version because I might use official screen. Any one have recommended for a 7-10 inch touch screen that has a vase the entire pi can fit in. I want to basically mount it in my car. I found some nice cases for this but they all work with the official screen using screen connector and I know that’s not best for this rom.
[Raspberry Pi Original Development] OdeMix:
Hello. I am trying to connect RTC Ds3231 to my Raspberry Pi. I connected the RTC module in the settings and in the config.txt file, using the command "su hwclock -w -f / dev / rtc0 I write the system time to the 3231 module, but after the device reboots, the time shows 1 hour more than it was. Maybe there are some solutions to this problem?
[Raspberry Pi Original Development] OdeMix:
I used a 7 "screen in my car with a special driver. It connects using HDMI. The touchscreen is connected to the Raspberi Pi using USB. The screen was ordered in China.

Spoiler content hidden.
[Raspberry Pi Original Development] KonstaT:
That's the day light saving hour (summer time) that Android handles somewhere else.

Check 'hwclock --help' for options how to read/write the time in different formats. Script that reads the time during boot is located at /system/etc/init.d/01rtc in case you need to modify something there as well.
[Raspberry Pi Original Development] OdeMix:
Hello. Could you tell me how I can add a GPS device myself?

I have a GPS USB receiver VK-162, but it doesn't work.

Spoiler content hidden.

I found several ways to add my device, but they are for android devices. Android works a little differently on raspberry pi.

One time it worked a little. Then it stopped working and more I can't turn it on.

Installed system - lineageos-17.1 from 01/22/21
[Raspberry Pi Original Development] KonstaT:
U-Blox 7 devices should work out-of-the-box. You need to have the device connected when booting the device for the Android GPS HAL to detect it.

Grab a 'dmesg' output plugging in the device. It should also appear as /dev/ttyACM0 (if your GPS dongle uses some other driver there's a system property you need to change to use the right device https://github.com/lineage-rpi/android_hardware_gps/blob/lineage-18.1/README.md)
[Raspberry Pi Original Development] Balnafasae:
Hey, Konstakang. You have done a great job with android 10 and 11 for pi 4.

I tried using my DPI display panel and it doesnt seem to work.

I tried removing any device tree overlay/params that uses gpio pins

still it doesnt seem to work.

I see you have mentioned that this build only supports HDMI, is it related to the kernal?

Also

uncommnting

# Touchscreen

#dtoverlay=rpi-backlight

keeps the android stuck in booting animation.

could there be a link with dpi overlay and rpi-backlight overlay? and is preventing it from working?
[Raspberry Pi Original Development] KonstaT:
Don't comment out/remove the rpi-backlight line. Your device won't boot because Android lights HAL needs to have the backlight path accessible. It doesn't affect DPI display or anything else.

I'm entirely sure what is the status of DPI display with KMS driver used with hw accelerated graphics on Android builds. Raspberry Pi OS (and other Linux distros) usually use the firmware/fake KMS (FKMS). Unfortunately this kind of information is not easily available but you'd need to dig the relevant pieces of info from Pi Foundation engineers' random forum post or their GitHub issue tracker.

It's possible that Android graphics HALs also don't know to configure the DPI display. Pretty sure you would need to remove /boot/resolution.txt for start at least. Impossible to say what is the exact issue with DPI display without seeing any logs. Testing my older LineageOS builds (16/17) that use/have support SwiftShader software rendederer is also an option.

Also please try to stick with one medium instead of making the same post on various different places (removed your post from my site).
[Raspberry Pi Original Development] Balnafasae:
i tried with my 18.5, 15.6 inch non touch DPI_LVDS monitor. DPI displays doesnt seem to work in these builds..ill work on that with help from konstakang and will update once it works
[Raspberry Pi Original Development] Balnafasae:
Hello, konstakang. Thanks for a swift response.

1. I will keep the rpi-backlight toverlay uncommented.

2. I get the splash screen but no display afterwards ( which i think the splash screen is from the rpi firmware)

3.For now, could you tell me how /boot /resolution.txt does affect the android from outputting dpi?

4. i will try removing resolution.txt and running older builds to see swift shader helps.

ill keep you posted

Im also posting on rpi forum about the dpi firmware appraoch and android hal to learn more about them. thanks agai
[Raspberry Pi Original Development] KonstaT:
Display connection technology != display size.

I know people have used these Android builds on displays ranging from 4" to as big TVs get these days. If you use a display with resolution other than the default 1080p you also need to change Settings -> Display -> Display size to adjust the pixel density.

If by splash screen you mean the rainbow screen, it's a Raspberry Pi firmware level thing.

/boot /resolution.txt is used in my Android builds to force a certain resolution that the connected (HDMI) display reports as supported via EDID. I highly doubt DPI display is reporting anything or if you're even getting that far for this to make any difference.

You really need to have proper ways to get logs if you want to debug this.
[Raspberry Pi Original Development] Balnafasae:
You are right.

I had changed the display size under settings to 1360x768

Could you let me know how to get a proper log for you to look into?

im running 18.1 now.
[Raspberry Pi Original Development] KonstaT:
Having a serial console adapter is the best option to get logs from that early in the boot process. I don't know if that works with the DPI display if it also uses some of the same pins as UART.

Regular USB ports on the Pi are host mode only so you can't use those for ADB. You can use ADB over the USB-C port on Pi 4 but you need a powered USB-C hub or an USB Y-cable and outside power source for this (or power over ethernet/GPIO). ADB over network is not possible this early in the boot.

IMO the first step for you is to get your display working Raspberry Pi OS with KMS (instead of FKMS is uses by default). We can look into how Android handles things after that.
[Raspberry Pi Original Development] Balnafasae:
on pi forum, i was told , using KMS, i need to create a DTOVERLAY for the panel usinf the timings from SIMPLE-PANEL.C

TO test RPI OS with KMS i just need to mention

dtoverlay=vc4-kms-v3d

dtoverlay=cma,cma-384

in config.txt?

also is "M" needed to be added with memory allocation like "cma-384M"

?

ill try to make the display work with RPI os / ubuntu with KMS and revert back to you with updates.
[Raspberry Pi Original Development] KonstaT:
Just changing dtoverlay=vc4-fkms-v3d -> dtoverlay=vc4-kms-v3d in config.txt should be enough for Raspberry Pi OS.

I think there should also be an option for this in 'raspi-config' (or at least there was in some versions, I haven't checked with recent releases).

Increasing CMA is only needed for Android. No 'M' (https://github.com/lineage-rpi/andr...1/arch/arm/boot/dts/overlays/README#L628-L642).

My Android kernel also needs to have the DRM_PANEL_SIMPLE built-in for your dtoverlay to work but we'll get to that later if you get it working with Raspberry Pi OS first.

Also putting a link to the Pi forum discussion here because it has relevant information. https://www.raspberrypi.org/forums/viewtopic.php?f=73&t=310125&sid=6cd9e98bb3a0fe4ba438e6ba4cce09ba
[Raspberry Pi Original Development] OdeMix:
I don't understand why GPS works like that.

Yesterday was cloudy weather, rain. The system has found all the satellites. I have not made any changes to the settings. It's sunny today, no clouds. GPS found only one satellite. What ideas do you have?

P.S. And after I asked the last question, I haven't made any changes to the settings. GPS itself started to work yesterday.

Spoiler content hidden.
[Raspberry Pi Original Development] KonstaT:
I can only comment that the antenna on my U-Blox 7 unit is really bad I can't get a fix when I'm inside either. I don't think this is a software issue.
[Raspberry Pi Original Development] albertd52:
Just installed the version 17.1 20210122 on the Pi4 with 8gB and a 64 gB SD.

After booting I reach screen "Restore Apps and Data" and want to Skip. There I get stuck, nothing is happening. Pressing Restore from Backup (which I do not have) shows a short flash of the "Searching for Accessories" screen and then the menu flips back to Time and Date.

What could be the issue. I am really eager to get this working. Thanks.

I use Lineage on my phones and it is really the best.
[Raspberry Pi Original Development] KonstaT:
It would be worth pointing out if you're discussing the Android TV or the regular tablet UI build especially as both latest releases were on the same day. I assume you mean the Android TV build.

Have you installed gapps? Have you changed display resolution from the default? In any case difficult to say what could be the problem without seeing any logs.
[Raspberry Pi Original Development] albertd52:
Hi Konstakang, thanks for the reply. Sorry for not pointing out that it is Android TV build. I have not yet installed GAPPS because the install procedure hangs at the "Restore Apps and Data" screen. Hence I cannot change the screen resolution other then on the TV which I put on HD (1920x1080). Other settings I cannot make because the install procedure hangs unfortunately. Where could I find the install log on the SD card?

Forgot to mention that pressing "Skip" in the "Restore Apps and Data" screen the monitor/TV turns black.
[Raspberry Pi Original Development] KonstaT:
You would need to have a serial console adapter to get logs at this point.

You can boot to TWRP directly to install gapps using a hardware DIY power button (see FAQ). You can also change resolution by editing /boot/resolution.txt (also see FAQ).

The setup wizard is extremely memory hungry for some reason and graphics can run out of CMA allocation with higher resolutions. This shouldn't be a problem with 1080p.
[Raspberry Pi Original Development] albertd52:
Yesterday I tried again and left the RPi on after the screen got black (at the point I mentioned before. After som 10 minutes suddenly the ATV startup screen came up and I could do the rest, including GAPS install. STrange but perhaps this is related to the memory hunger (...?). Thanks for your kind help. I now have it working an it works very well. Super work you have done.
[Raspberry Pi Original Development] risant:
How could u make soundblaster usb dac soundcard work on pi 4b ? please help
[Raspberry Pi Original Development] KonstaT:
How would you use it on some other Linux distro e.g. Raspberry Pi OS?

If Android detects it as an USB sound card then just simply plug it in.
[Raspberry Pi Original Development] risant:
onkyo hifi player detects it as hifi soundlaster usb sound card still no sound from digital out toslink of soundblaster even spotify no sound i used it on lineage 17.1 rpi.. developer's option usb configuration no audio device option.. what will i do to make it work?
[Raspberry Pi Original Development] KonstaT:
There shouldn't be any difference how USB audio devices are handled between LineageOS 17 & 18. My USB soundcard works on both at least. There's no USB audio device option in developer options. Both have option to disable USB audio routing, though.

You'd need to provide logs (logcat, dmesg) on both where you have this working (LineageOS 17) and where it's not (LineageOS 18).
[Raspberry Pi Original Development] KonstaT:
Did you have a specific display in mind? Waveshare HDMI touchscreens work apart from minor calibrations issues and official 7" touchscreen is supported when using a software renderer. People have reported mixed results with USB touchscreen.

Display size is hardly a problem. People have used displays ranging from 4" to TVs as large as it can get. There's settings options to change the display and font sizes.
[Raspberry Pi Original Development] major payne:
https://www.waveshare.com/product/displays/lcd-oled/lcd-oled-1/15.6inch-fhd-monitor.htm or

https://www.waveshare.com/product/displays/lcd-oled/lcd-oled-1/13.3inch-hdmi-lcd-h-with-case-v2.htm

https://www.waveshare.com/product/displays/lcd-oled/lcd-oled-1/12.5inch-fhd-monitor.htm

Since you gave me a brand you use I'll use those too. Only going to be using this to read books and listen to audio books while in bed
[Raspberry Pi Original Development] nirav100:
System reboot issue

The system reboots after few click, it is hardly passing the setup few screens. is there anything i am doing wrong.

i have PI4 , RF based keyboad. used BalenaEtcher to flash 16 GB card.
[Raspberry Pi Original Development] KonstaT:
Waveshare displays that use SPI for touch input should work. There's been mixed results with different USB touchscreen. I haven't received any reports from anyone with one of those displays so can't guarantee any of these will work out-of-the-box.

General advice is to use a proper sdcard (class 10) and power source (3A in case of Pi 4).

Also see http://disq.us/p/2ax3vmu
[Raspberry Pi Original Development] major payne:
That makes it tough as no screen above 10.1 supports SPI
[Raspberry Pi Original Development] KonstaT:
There's now also an Android TV build:

https://konstakang.com/devices/rpi4/LineageOS17.1-ATV/