yashsingh1/xdaforums huggingface dataset:
[Raspberry Pi Original Development] KarlOlafsson:
I am currently trying to boot LineageOS on Raspberry PI 4 over Network

as Image I use

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

and I also installed Magisk

https://www.androidfilehost.com/?fid=15664248565197202536

I booted up the PI 4 once with the image over sdcard and installed Magisk.

After that..

Spoiler content hidden.

Any help appreciated and If anyone replies I'm not angry if you dumb your answers down so a five year old could understand them.

Thx in advance.
[Raspberry Pi Original Development] KonstaT:
Network boot is not supported on Android builds and I'm not aware of any way it would be even technically feasible.

Partition structure is different on Android compared to regular Linux distributions and Android has two stage init which mounts different partitions at different points in the boot process.
[Raspberry Pi Original Development] azraelcelt:
Has anyone else had issues with Bluetooth with this rom on a raspberry pi 4B ? upon testing in another pi 4B (both had 8gb ram) I noticed the bluetooth app kept crashing and bluetooth was stuck on "turning on"
[Raspberry Pi Original Development] KonstaT:
At least I'm not able to reproduce. Logcat?
[Raspberry Pi Original Development] azraelcelt:
Sorry I ended up moving to the android 13 AOSP for my Pi4B and Bluetooth works well on both Pi's so guessing some weird bug due to the way I flashed each zip file on its own then restarted before flashing the next one, I'll try to reproduce on my smaller SD card soon and send you a logcat if I can reproduce issue,

just wondering if possible to boot android OS off of a m.2 ssd instead of a SD card like with a argon one m.2 sata raspberry pi case ?
[Raspberry Pi Original Development] KonstaT:
If you have an USB adapter for that M.2 SSD. Please read the FAQ on how to boot from USB devices.

Pi 4 doesn't have anything you could plug M.2 directly. There's some CM4 carrier boards that have M.2 connector but there's no support for booting directly from NVMe storage (as I don't have the hardware myself).
[Raspberry Pi Original Development] azraelcelt:
I have one of these that I guess would use a usb to m.2 ssd aka usb boot I guess, its not a nvme like my PCs main ssds but it can easily boot rasperian X, I was just unsure about being able to boot an android OS
[Raspberry Pi Original Development] azraelcelt:
It's a great case for keeping the pi running for around 2-3 days overclocked up to 2.3-2.4GHz on all 4 cores once I can get the fan up by the gpio pins running at 100%, as for whether I can run a stable overclock android 13 aosp I don't know but would be interesting if possible
[Raspberry Pi Original Development] azraelcelt:
Hi just wondering if you have a resizing zip where you can set the size instead of maxing it out ? Used a 128GB SD card and my m.2 drive is only 120GB lol
[Raspberry Pi Original Development] KonstaT:
You can, there's a FAQ section on how to boot from USB. It doesn't matter what USB device it is (USB thumb drive/SSD with USB adapter/sdcard in USB card reader/etc).

You can also overclock the CPU on Android just like any other OS on the Pi. There's settings options up to 2 GHz. Someone also shared a script for the fan on Argon case (http://disq.us/p/2guifm1). I've moved init.d scripts to vendor partition (/vendor/etc/init.d/) on Android 12/13.

No, the whole point of the resize zip is to use all of the unallocated space on the drive. Do a fresh install on the other drive and flash the resize zip.

Did you intend to 'dd' the image from the larger drive to the smaller one to keep your setup? You could also try shrinking the data partition using gparted, etc beforehand but IMO it's just easier to start from scratch.
[Raspberry Pi Original Development] pancapangrawit:
Thanks for the build, very exciting!

I have three observations:

- I have the bluetooth problem as well, and I can specify a bit more: I can pair a logitech mouse successfully (M590), but not the keyboard (K380). The crashing occurs, *while* I try to enter the code requested for pairing via that keyboard. This leads to my second observation:

- the keyboard driver is somehow broken. When I use a usb-keyboard (Apple keyboard recognised properly), many characters display wrongly in a chaotic way. Instead of 'n' for example it displays 'ń'. When I stay on the key to trigger character repetition the following characters entered are the proper 'n'. I get chaotic results from other keys. The keyboard works fine in other environments. So my conclusion is that the bluetooth pairing issue might have to do with the keyboard problem rather than bluetooth per se.

- a weird error I get is with Google Chrome browser. It starts loading a page and stops after about 30% of loading. I haven't gotten a single page load when typing the address in the address bar. Opera works normal.

Thanks for your considerations! This ROM looks very promising! Video playback is much more efficient than in PiOS, the "desktop" is quite snappy even in 4k. The one thing I'd love to have is being able to switch the resolution without having to reboot. The desktop and many apps are beautiful in 4k, but for playing games I need to switch to HD or even 1280x720. But I guess it's not Android philosophy to change resolution on top of a running system :(

Thanks again!

.p.
[Raspberry Pi Original Development] KonstaT:
Logcat on bluetooth issues?

USB keyboards should work just fine (if they work with Linux in general). Make sure you've selected correct keyboard layout from Languiage and keyboard options. I doubt this has anything to do with the bluetooth keyboard issue.

There's a known Issue with Chromium based browsers that is related to Vulkan which you can disable (see e.g. http://disq.us/p/2pcllli). It is also fixed on Mesa version used with Android 13 builds which you can also use instead.

It's not possible to change hardware resolution without rebooting (i.e. using actual resolutions that your HDMI display reports as supported via EDID). It's possible to change software resolution with 'wm size' (see e.g. https://stackoverflow.com/questions...to-use-adb-shell-wm-to-simulate-other-devices).
[Raspberry Pi Original Development] pancapangrawit:
I've since moved on to AOS 13 too, and find a slightly different situation: keyboard and wacom tablet pair, and and the M590 mouse doesn't. I am willing to assume that it's the mouse's problem, although the model is listed as Android compatible - it's a dual bluetooth/unified mouse though, so maybe something fishy. I'll try to produce a log, but it'll take a few days, I am new to Android.

You're right, the bluetooth keyboard pairs fine on AOS 13. The same weird problem with the Apple keyboard though... I don't mind however, als the wireless one works ;-)

Yes! (but Minecraft crashes ;-) same on PiOS with mesa 22.1)

Thank you for that instructive link, I'll try to see if I can do something!

Thanks again for your amazing work!

.p.
[Raspberry Pi Original Development] htc_Tomi:
Quick question:

Is there a way to have ADB authorize my machine when first booting?

I'm fully blind. I need ADB headless right after flashing the image. I noticed there's now config_user.txt - is this something that might help there? Anything I could add to config.txt or modify in a file pre-boot on the partition to get ADB? Or is this OS no longer blind-friendly. Would be good to know as most Gapps don't include Google TTS and Talkback and that's a huge disadvantage to folks like me.

Thanks for your hard work as always.
[Raspberry Pi Original Development] KonstaT:
You could change 'ro.adb.secure=1' to 'ro.adb.secure=0' in /system/build.prop. This will disable ADB authentication altogether.
[Raspberry Pi Original Development] htc_Tomi:
Thanks for this great info!

This worked like magic. I did run into a snag though. It appears that your TWRP recovery Ramdisk doesn't enable ADB access within the recovery. Right now I have to grab the one from the other Rom project, which is fine, and swap in that larger recovery ramdisk IMG. It's like 3 MB larger. But it gives me ADB over type C to do 'twrp remountrw system' and get things going as you said. I created a guide on my website and right now I have my readers swap out their recovery for the other Rom's, but ideally I'd like to see this be less steps for them and for me to be able to use your stock recovery.

Seeing this flurrish so well does make me want to donate to your project, which I will most likely will later :) You deserve so many fireworks for your effort and just doing this over years. I really can't thank that enough.
[Raspberry Pi Original Development] KonstaT:
ADB in TWRP isn't working due to configfs not getting enabled for some reason. Not a big deal and this will be fixed if/when there's another release.

You simple can't copy TWRP from somewhere else and expect it to do anything useful or even work in the first place with my builds. Certainly don't recommend it to anyone!

It's not like you would even need TWRP for this. You can mount the sdcard on your Linux machine and edit /system/build.prop or you can do this when booted to Android as well e.g.

adb root
adb remount
adb shell
sed -i 's/ro.adb.secure=1/ro.adb.secure=0/' /system/build.prop

Edit. Ugh, you obviously can't use ADB because that was the whole problem but e.g. in some other rooted shell:

su
mount -o rw,remount /
sed -i 's/ro.adb.secure=1/ro.adb.secure=0/' /system/build.prop
[Raspberry Pi Original Development] htc_Tomi:
Ah yes, the sed command! That does simplify it from pulling / pushing the file itself back. I wasn't sure if stream editor is included but it's basic Unix enough. I'm not sure if the TWRP environment has it but I'll check.

I agree 100% that swapping out ramdisks is not ideal and shouldn't need to be done. I don't think many of the readers (who may be a bit less technical) own Linux machines, and Gnome/ GTK accessibility has been so patchy that in our world Linux is not at all usable well outside the commandline for beyond basic tasks. Which means a lot of Windows users. Paragon makes an Ext 3/Ext 4 filesystem driver but I've found that it doesn't always write reliably either.

I'll keep monitoring the builds though for changes to the recovery. Certainly there's at least a workaround for Windows users with the ramdisk swap (and then swapping back to the Rom's 1.3 MB ramdisk.) Recovery is also needed to apply the .zip patch build of each ROM, which certainly would require working ADB in TWRP. The moment this changes I'll update the guide I wrote to be much simpler as at that point doing a config.txt edit to force initial boot into TWRP is much easier to do.

No rush on getting it in of course. We have a away that works reliably for now and I'm satisfied with it for now. Thanks for all this great info to streamline everything.

edit: I realize I never explained why we need insecure ADB entirely - since most roms don't include both Talkback nor Google TTS by default, folks with vision impairments need to install Google's Accessibility Suite to be able to use their Pi. I don't know if there's a way to run the build headless (I know folks who do VNC need this too) but right now I notice I need a dummy HDMI connection to a non-existing monitor screen for it to boot. Perhaps there's a config flag I can hunt down in these 24 pages of conversation that does that.
[Raspberry Pi Original Development] coderunner1:
Hi, I cant seem to find the touchscreen settings for the offical touchscreen, can someone direct me to where it is
[Raspberry Pi Original Development] KonstaT:
Yes, TWRP has 'sed'. I fixed the ADB over USB-C on TWRP yesterday so it will be included if/when there's any new releases.

No, it's not necessary to use any dummy HDMI plug or make any modifications. Support for headless mode was added to upstream drm_hwcomposer around February so it's also been supported in everything I've released after that (as also mentioned in the changelogs).

Settings -> System -> Raspberry Pi settings -> Touchscreen as stated in the FAQ.
[Raspberry Pi Original Development] htc_Tomi:
Great to know recovery will include ADB in next update release!

Unfortunately I need to stick with the 18.1 ROM for now. It appears that sound for Talkback is broken in 19.1 releases. I haven't pinpointed down why this is, but I'm not able to get sound over HDMI or USB soundcard. I'm using a Pi400. After Talkback gets enabled through 'ADB shell settings put' logcat shows events related to Audio and Talkback running, but no sound. Repeating the same enable step on 18.1 worked fine. Both GoogleTTS and Talkback get installed in /system/product/app as it's part of Mind the Gapps package. I'll continue investigating why this happens. 18.1 doesn't play as nice with mixed WPA2 / WPA3 networks.
[Raspberry Pi Original Development] KonstaT:
My Android 12/13 builds use 3.5 mm audio jack as default audio device vs. HDMI used by default on Android 11 and older. There's a settings option to change the audio device as mentioned in the FAQ. You can also change this manually in shell (for audio to HDMI0 port):

setprop persist.audio.pcm.card 1
setprop persist.audio.hdmi.device vc4hdmi0

There's been some reports of issues with USB audio DACs on Android 12 but my USB audio card works fine at least so I'm not able to reproduce that.
[Raspberry Pi Original Development] coderunner1:
The setting is completely missing from the menu
[Raspberry Pi Original Development] KonstaT:
It's not. Unless you're using the Android TV version (in which case you won't find it in the FAQ on that page either).

Android TV is not intended to be used with a mouse or a touchscreen. You need to have a remote to navigate the system (USB remote, Bluetooth remote, IR remote, TV's remote using HDMI-CEC, arrow keys on your keyboard, etc).
[Raspberry Pi Original Development] coderunner1:
I'm on the 12L version, I'm not on TV, the setting is just not in the menu
[Raspberry Pi Original Development] KonstaT:
Scroll down?

I'm sure it's there if you've followed the installation instructions and haven't made any changes to the image yourself. Are you missing the whole Pi settings or just that one option in that menu?
[Raspberry Pi Original Development] htc_Tomi:
Thank you. I was a bit nervous at first since I thought setprop may require root, but perhaps with the permissive Linux this is not the case. Whew. That would be harder to set and I would have had to do so at boot somehow then.

This worked on my Pi400 to get Talkback audio. As a result, I have updated the auto-batch script in my guide to ask readers whether they use a pi4 or 400. If 400, we wait once rebooting, then set these environment variables for this audio change.

I also noticed that headless does not work on Pi400. I'm not sure why. I need to have HDMI plugged in with that one, but not with Pi4. When I tried the SD in my Pi4 I got Talkback audio and headless working, which to me is a night/day difference in experience. Now that I know these tricks I got it working on my 400 also but still can't take it headless with just a USB soundcard and speakers / headphones. That's the ultimate portable Android dream machine experience, we're close though.
[Raspberry Pi Original Development] KonstaT:
3.5mm jack is used by default on Pi 4/400/CM4 though Pi 400/CM4 doesn't even actually have one. If you wan't to switch to HDMI audio, it's needed on all of these devices.

I don't see any reason why headless mode wouldn't work on Pi 400 as well since it works just fine on Pi 4. I don't have any Pi 400 hardware to test, though.
[Raspberry Pi Original Development] Keboid:
The hosting site is down, can you please upload ot to a working place?
[Raspberry Pi Original Development] KonstaT:
AndroidFileHost has random issues sometimes. Try refreshing the download page or try again later.

There's been several reports over this last week or so. This still seems to work just fine for me just now. Could be that AndroidFileHost has issues in some countries/ISPs but that's not something I can anything about. You would need to report this to them.
[Raspberry Pi Original Development] someoneislookingafterme:
Hi!, i have a rpi4 That is running

LineageOS 19 (Android 12L)​

but , when i try to start it up first time ,

NO Signal

can you help me , thank you

someoneislookingafterme
[Raspberry Pi Original Development] KonstaT:
Please read the FAQ about issues with display.
[Raspberry Pi Original Development] the_dj84:
@KonstaT hey I followed your guide for 12 and after gapps install, wipe dalvik, reboot..After reboot i dont get the remote graphic for setup, just the same homescreen but play store installed. Is that normal for mindthegapps?

Installed these with on a Pi4 with BalenaEtcher:

lineage-19.1-20220923-UNOFFICIAL-KonstaKANG-rpi4-atv

MindTheGapps-12.1.0-arm64-ATV-20220912_160414

EDIT:

nvm, i was half asleep and read instructions as saying wipe dalvik = factory reset. Did factory reset and got correct setup screen.

leaving post for others. thanks for the development!
[Raspberry Pi Original Development] Smokinimages:
Pi 4 B with a DSI Capacitive Touch Display. Once I'd cursed a bit over the screen not working, then went and actually read the faq on changing a couple of setting everything is up and running well. One issue, least so far, and a specific one but maybe someone can help or point me in the right direction. I'm trying to do a build for the car using Car launcher, an app I've used for a couple of years on a tablet, but it freezes as soon as it loads and i can't find a way around it. Any ideas?
[Raspberry Pi Original Development] KonstaT:
As always, logs (logcat) might give some clues. There's no point in guessing.
[Raspberry Pi Original Development] Smokinimages:
logcat attached from just before starting the app to it freezing and the not responding error,. First time I've grabbed logcat logs so hoping this is enough. TIA for any help. I know this is probably an app issue but nothing else comes close to Car Launcher esp for designing custom screens using Spotify album art

Just wondering what luck people have with USB cameras? I have one of these sitting from a different project but this build just complains that it is unable to communicate with the camera

8MP 1080P USB Camera Module - 1/4” CMOS IMX219 Mini UVC

An 8MP camera module for your Raspberry Pi - without the fuss of fiddly flex cables! This Arducam IMX219 camera module is an 8MP, UVC compliant, USB 2.0 camera module which works with the Raspberry Pi as well as Windows, Linux and Android (Mac OS doesn't seem to like this one!). The camera...

thepihut.com
[Raspberry Pi Original Development] KonstaT:
No log was attached. :)

USB UVC webcams should work. With the AOSP external camera HAL used in Android 12/13 builds it depends if the camera reports some resolution information properly and whether it supports MJPEG format. At least my Logitech USB webcam works fine while cheap chinese one doesn't. Logcat would likely give some idea here as well.

Android 11 (and earlier) builds use different camera HAL for USB UVC webcams.
[Raspberry Pi Original Development] Smokinimages:
Had a search and can't see anything about this

Is the allow access to app usage stats bugged? I've allowed it in tasker but it's still *****ing about it not being set. It would also explain why app lock apps are not working
[Raspberry Pi Original Development] Spielmops:
Konsta, I'm still searching for a working camera. Can you give me the model-info of the one you are using?

Can anyone else tell me about working models?

I tried 3 different devices and all 3 are working fine with Linux UVC, even with MJPEG ( two of those bad), but none is recognized with LOS 19.

Spielmops
[Raspberry Pi Original Development] KonstaT:
Sorry, can't quite understand what the issue is exactly. Steps to reproduce? Logs?

There's no battery on Pi so there's no battery usage stats either.

Various Logitech USB webcams have been reported working, mine does anyway.
[Raspberry Pi Original Development] Spielmops:
One of the three tested cameras ist a Logitech USB webcam. And it's not working. Should I buy the whole sortiment and try each one?
[Raspberry Pi Original Development] KonstaT:
That's an excellent idea since you wanted to maintain a list of working/non-working USB cameras. /s :P

I don't have any list but at least C270 & C310 have been reported working of the Logitech ones (still not an endorsement of any kind).
[Raspberry Pi Original Development] Yoshikage_Kira:
Has anyone figured out how to make the internet work with the Android TV version? There is no such setting as Mobile data & WiFi in ATV. It is present in the normal android version.

There is no issue with the intenet connectivity since the ads were loading fine somehow.
[Raspberry Pi Original Development] Yoshikage_Kira:
I was able to figure out the solution, turns out, I need to factory reset the device.
[Raspberry Pi Original Development] Spielmops:
My results with Logitech-webcams:

They are working, but with camera-api1 only with low resolution, only with camera-api2 with expected resolution.

Open-Camera can switch between the API's and gave me numbers with a Logitech C920 HD Pro

camera-API-1: up to 864x480

camera-API-2: up to Full HD

If you want to record a video with an app that can't switch API (Dashcam-App), then the result will be lousy.

Spielmops
[Raspberry Pi Original Development] KonstaT:
Thanks, that's useful information.

With H.264 hardware encoding now enabled on Android 13 (will be on Android 12 as well if/when there's another release) you can probably record pretty decent videos.
[Raspberry Pi Original Development] Smokinimages:
bit of a reach but does this build support any USB fingerprint scanners?

Thanks for a great build, made getting my second screen in the car working much easier than messing with tablets, just need to tidy the install up now
[Raspberry Pi Original Development] KonstaT:
No, there's no support for any external fingerprint readers. I don't have any hardware to develop/test.
[Raspberry Pi Original Development] KonstaT:
Final Android 12 builds. H.265 hardware video decoding, H.264 hardware video decoding and encoding! HDMI audio fixes.

LineageOS 19 (Android 12L)

for Raspberry Pi 4

konstakang.com

LineageOS 19 Android TV (Android 12L)

for Raspberry Pi 4

konstakang.com

H.265 hardware video decoding, H.264 hardware video decoding and encoding

FFmpeg 5.1.2 (thanks to John Cox for Raspberry Pi hw codecs support and Android-x86 for AOSP build patches)

implement codec2 plugin to integrate FFmpeg into Android multimedia framework (thanks to Michael Goffioul)

FFmpeg hevc_v4l2request hwaccel H.265 hw decoding (default), h264_v4l2m2m H.264 hw decoding (optional)

v4l2_codec2 H.264 hardware video decoding and encoding (default)

FFmpeg software decoders support

HDMI audio improvements

implement audio HAL that uses alsa directly to get rid off using alsa loopback for HDMI audio (thanks to nename0)

update alsa-lib and alsa-utils to v1.2.8

update to TWRP 3.7.0_11-0-KonstaKANG

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

Android security patch level: 5 February 2023 (merged)
[Raspberry Pi Original Development] KonstaT:
Some good sources for test clips to try H.264/H.265/VP8/VP9 hardware/software video decoding.

MP4 ( H.264 ) | Test Videos

Download test videos and sample videos for any purpose. Completely free videos of different formats, file types and sizes.

test-videos.co.uk

MP4 ( H.265 ) | Test Videos

Download test videos and sample videos for any purpose. Completely free videos of different formats, file types and sizes.

test-videos.co.uk

WEBM ( VP8 ) | Test Videos

Download test videos and sample videos for any purpose. Completely free videos of different formats, file types and sizes.

test-videos.co.uk

WEBM ( VP9 ) | Test Videos

Download test videos and sample videos for any purpose. Completely free videos of different formats, file types and sizes.

test-videos.co.uk

Jellyfish Bitrate Test Files

A collection of .mkv video clips encoded at various bitrates; useful for testing the network streaming and playback performance of media streamers & HTPCs.

www.larmoire.info
[Raspberry Pi Original Development] TQTech:
how did you buid it for supporing quectel EC25