yashsingh1/xdaforums huggingface dataset:
[Raspberry Pi Original Development] rabbited:
Right! What I was trying to say was that the test would only be useful if Passpoint DID work on RPOS because that would prove that the hardware can potentially work (ie the chip itself supports Passpoint). Outside of that, any other outcome doesn't provide useful info. I will try this now and edit my post with results! Thanks again!

Edit: Unfortunately, I'm not seeing any difference with the new version. I will check the two logcats to see if there's any difference.

Just to confirm, I go the the install tab in TWRP, install the provided file, wipe Dalvik and reboot and there are no other required steps?

logcat3.txt

drive.google.com
[Raspberry Pi Original Development] KonstaT:
Most definitely something wrong getting this to your device now. The code block where you get the 'ANQP initiated on ...' log is commented out so you couldn't possibly see that. I can leave this to next build for testing (doesn't seem to break anything for me) but not sure if there's any point in providing patches to test. Exactly why I don't like to deal with issues I can't reproduce myself.

Yes, just the flash the zip in TWRP. You can e.g. 'ls -l /system/apex/com.android.wifi/javalib/' before/after to see that the file date/size have changed.

On the subject of wiping dalvik cache, I have probably never in my life wiped dalvik cache. Android is perfectly capable of rebuilding the Dalvik/ART executables whenever something is changed. IMO that option should have been removed from recoveries years ago (and it's also been years since Android moved to using ART).
[Raspberry Pi Original Development] masscream:
Thank you, with the info you gave me I was able to move forward. procount is now working on the permanent fix.
[Raspberry Pi Original Development] rabbited:
Thanks again! I will try to sort out what it is I'm doing wrong and get back to you after trying each patch once sorted out. Would you recommend just sticking to trying to solve it with the second patch?
[Raspberry Pi Original Development] rabbited:
SUCCESS! I manually replaced the service-wifi.jar file via ADB and for the first time in a year of trying to figure out a way to get WiFi to work on my RPi I am finally able to use it without issue! Thank you so much for your amazing work!

I'm not sure why the flashable zip didn't work but is replacing the service-wifi.jar file the only change that needed to be made? Do I need to replace META-INF? I'm new to the inner workings of the Android file system so I'm just starting to research what this is for.
[Raspberry Pi Original Development] KonstaT:
That's great news! Thanks for testing. :)

At least there's now a little better understanding what the issue actually is (automatic ANQP requests). Still needs some figuring out what is the best way to handle this on a device that doesn't support that.

Yeah, IDK what went wrong with that zip, seems to replace the file just fine for me. service-wifi.jar is the only file that gets replaced in the system. I'll include this change in the next build anyway.
[Raspberry Pi Original Development] KonstaT:
New build.

LineageOS 19 (Android 12L)

for Raspberry Pi 4

konstakang.com

-switch to Linux 5.10 kernel by default

-fix VC4 HDMI audio with 5.10 kernel (3.5mm jack is now used by default so select the right HDMI device from the settings)

-add support for the official 7" touchscreen display with hw accelerated graphics (enable configurations for the touchscreen from the settings)

-minor brightness fixes for the official 7" display

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

-fix UVC USB webcams that use external camera HAL (camera needs to support MJPG format - preview, photos & camcorder works)

-add option to enable currently very WIP H.264 hardware video decoding using v4l2_codec2 (enable experimental feature from the settings)

-fix reboots related to Hotspot 2.0 networks/ANQP requests (see issue #6)

-Vulkan 1.1 (thanks to people at Igalia for Vulkan 1.1 conformance and Roman Stratiienko for latest Mesa fixes)

-update to Mesa 21.3.1

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

-Android security patch level: 5 December 2021 (merged)
[Raspberry Pi Original Development] EthanRIP:
Downloaded new build, flashed to 32gb sd card (using belena etcher). Plugged into 7" official rpi touchscreen. Got rainbow splashscreen - white animation - then blank screen (still lit up) with faint grey lines and nothing else. I tried changing the resolution.txt to 800x480 and deleting resolution.txt completely. Both resulted in the same issue. Anything i'm missing here?
[Raspberry Pi Original Development] KonstaT:
At least you missed reading the FAQ, reading my reply when you asked the last time, reading the link I gave in that reply, and so on.

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).
[Raspberry Pi Original Development] rabbited:
After the wifi fix I installed Lineage19 on my CM4 for the first time and noticed that there are a few core issues. Opening the browser leads to a white screen with a search bar but no "webpage not available" message as expected if it was simply lack of ethernet or wifi (testing on 4B by turning off wifi shows a "webpage not available" message). When trying to add a new user in Settings the button is unresponsive. I will try to make some logcats later tonight. I reverted to the first build of Lineage19 to see if this has been a problem since then and experienced the same issues.
[Raspberry Pi Original Development] KonstaT:
Logcat on the browser issue? Seems strange that this would be something CM4 specific.
[Raspberry Pi Original Development] rabbited:
The browser issue appears to be graphics related. This is clear in the logcat but I also realized it when the search bar would autofill with different search options as I typed (the search bar being the only part of the browser that shows up, the rest is a white screen). Here is the logcat:

browser.rtf

drive.google.com

I'm using an HDMI dummy plug here but the behavior was the same when plugged into my monitor as it is over VNC w/dummy plug. I will still try to get another logcat when hooked up to my monitor in case theres any variation in messages.
[Raspberry Pi Original Development] MystKid:
what gapps to install with this release?
[Raspberry Pi Original Development] KonstaT:
Thanks. What resolution are you using? It's hard to think this could be something CM4 specific. There's nothing in the log that would give exact clue why this is happening. I can see some USB related issues there that are CM4 specific (and also I know audio is an issue with CM4). I probably need to stop advertising any CM4 support (again). Probably not much I can do without having the hardware myself (and couldn't really get it either as it's out of stock everywhere).
[Raspberry Pi Original Development] EthanRIP:
This is a very early release so it was challenging for me to find gapps, but I found them here https://www.pling.com/p/1462970/ It does slow it down a bit, and crashes at times. I found that this alternative works great, and has a lot of the same apps including youtube https://en.aptoide.com/ Just download the .zip and flash in TWRP
[Raspberry Pi Original Development] EthanRIP:
I got it working on the touchscreen, no issues. Thank you for the help. I dont know if it is just me, but when I installed google chrome, it kept on crashing or at least just minimizing whenever I opened it. I installed within app store and tried the apk from a flash drive, both resulting in the same thing. Is there anything I can do to fix this?
[Raspberry Pi Original Development] KonstaT:
Logcat? There's no point in guessing.

Have you tested it with a proper display (1080p)? E.g. could be something gapps related or display/resolution related (with 160 dpi density used with 800x480 resolution apps need to have mdpi drawables).
[Raspberry Pi Original Development] EthanRIP:
Thats what I was thinking, havent gotten time to try it yet, but I figured that the resolution could be an issue. Will try that today.
[Raspberry Pi Original Development] MarekDev:
Maybe I have overlooked something, where can I find manifest and vendor repos for that port?
[Raspberry Pi Original Development] rabbited:
Separate logcats using both 4B and CM4 and the same monitor on same WiFi network when trying to run the browser. No issues with 4B, which is just here for reference/comparison. Basically just running the logcat again with monitor instead of dummy plug:

logcat_browser_cm4.rtf

drive.google.com

logcat_browser_4B.rtf

drive.google.com
[Raspberry Pi Original Development] KonstaT:
Thanks for the longer log that actually showed the issue. Please try 'chmod 666 /sys/kernel/debug/tracing/trace_marker' in rooted shell and launching the browser (or any app that uses system's built-in webview). There was a known issue related to this a while back. No idea why this would be now needed for CM4 but not for Pi 4/400. '222' permissions should be enough but lets try this first.
[Raspberry Pi Original Development] rabbited:
I have no idea why I was unable to find and enable "Local Terminal" under developer options, I looked at least ten times, but I performed this command first with:

"adb root"

"adb shell chmod 666 /sys/kernel/debug/tracing/trace_marker"

then tried again:

"adb root"

"adb shell"

(within adb shell): "chmod 666 /sys/kernel/debug/tracing/trace_marker"

Rebooting each time, I don't see any changes. Thanks again for your persistence.

I've also started to have an issue that I didn't notice before where the screen goes black and I need to reboot. This was both before this attempted fix and after. I'm going to try to get another logcat that is active when the screen goes black.
[Raspberry Pi Original Development] KonstaT:
There is no built-in terminal in this build and I doubt there ever will be. There's several third party alternatives, though. Built-in terminal was also dropped from LineageOS 18 (https://review.lineageos.org/q/topic:eleven-kill-terminal) but I reverted it there. I'm not going to maintain it for 19.

No, don't reboot your device. This does not persist over reboot. Just close any app that uses webview and relaunch the app after setting the permission.

Also 'ls -l /sys/kernel/debug/tracing/trace_marker' before/after to check the permissions.

In some previous builds there was

on post-fs
# Allow writing to the kernel trace log.
chmod 0222 /sys/kernel/debug/tracing/trace_marker

in /vendor/etc/init/hw/init.rpi4.rc to set this permission on each boot.
[Raspberry Pi Original Development] rabbited:
I changed permissions (first few lines in file) but the logcat still shows the same error related to those permissions. The logcat starts with me opening the browser and having the same issue and soon after the screen goes black. I was wondering if it was possibly a VNC issue but it is happening on the monitor without VNC running as well (using scrcpy to control). The screen goes black when not opening the browser as well and requires reboot. I will probably stick with the 4B for now, but am glad to run any tests if you have any ideas. I may reinstall on CM4 as the black screen issue wasn't happening when I initially installed.

browser_screen.rtf

drive.google.com
[Raspberry Pi Original Development] KonstaT:
Still pretty sure this will work. Try modifying the init.rpi4.rc if you can.

I'll include this if/when there's another release but that's going to be a while in any case.
[Raspberry Pi Original Development] noritano:
Hi, I am stuck in TWRP recovery mode with RPI4B 2GB during first boot. Rebooting in system does not work. No issues with the 4GB model. Is anyone having the same issue?
[Raspberry Pi Original Development] chjanson:
Unfortunately, I have only Raspberry PI 3 Model B with 1G byte RAM. Is anyone aware of a recommended Android build available for RP3? Android 10 or later...
[Raspberry Pi Original Development] KonstaT:
If you have GPIO21 connected to ground (or if you have something drawing power from it) your device will always boot to TWRP.

Edit. Added to the FAQ.

Pi 3 Android builds are available at https://konstakang.com/devices/rpi3/.

I've retired my Pi 3 from development so all the builds are discontinued. Choice is yours.
[Raspberry Pi Original Development] chjanson:
Thanks for swift info. Yes, I will get a RPI4, but can practice on RPI3 to learn the process.

One question: I am going to need USB audio in and out. At least 4 channels for the output. Is USB Audio fully working in all or any of your builds?
[Raspberry Pi Original Development] KonstaT:
There is nothing Raspberry Pi specific in the USB audio implementation so it works just like in Android in general (https://source.android.com/devices/audio/usb). Max supported channel count is 2 (stereo).
[Raspberry Pi Original Development] chjanson:
I installed on RPI3B with Google play. As you warn: Superslow and unusable, but with patience I could install "my apps", e.g. Tidal and UAPP, etc. After that, I disabled everything Google play, and then Tidal runs just fine as long as it is the only app running, albeit somewhat slow. Playback is perfect even if the 3.5mm out is of the lowest quality I have heard in years. My anticipation is that Google Play consumes too much memory for this old RPI so things go awry then.

MY PROBLEM: I have an Audiophonics HAT DAC to connect to the GPIO, which normally works just fine when fed with I2S, similar to the RPI3 GPIO. However, the DAC is not fed anything after setting the "hifiberry DAC" in the advanced settings. Tried restart, no joy. Thus, I must find the cause. First step: Is the "hifiberry DAC" as system audio out explicitly verified in LineageOs and/or in any of your custom builds? If not the A10 for RPI3, in any other for RPI4? I ask because it is not mentioned in your FAQ. By the way, impressing job you have done with all these variants!
[Raspberry Pi Original Development] KonstaT:
Sorry, this is not the right place for this discussion. Topic for LineageOS 17 on Pi 3 is here (https://xdaforums.com/t/dev-rom-uno...ndroid-10-for-raspberry-pi-3-b-and-b.4139051/).

Kernel in my builds has support for Hifiberry DACs. Everything you find in Settings -> System -> Advanced settings is device specific i.e. "my" features. Latest builds have option to select one of the supported DACs from the settings menu (old Pi 3 builds don't). You would need to modify /boot/config.txt and set dtoverlay to load the driver for your hardware (which I'm not sure is supported without compiling the kernel as it depends on the hardware).

Yes, Hifiberry DAC+ works just fine on Pi 3/4 builds and various other DACs (that I don't have myself) are reported working as well.
[Raspberry Pi Original Development] chjanson:
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
[Raspberry Pi Original Development] KonstaT:
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.
[Raspberry Pi Original Development] chjanson:
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.
[Raspberry Pi Original Development] 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
[Raspberry Pi Original Development] KonstaT:
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).
[Raspberry Pi Original Development] KonstaT:
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.
[Raspberry Pi Original Development] 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.
[Raspberry Pi Original Development] KonstaT:
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.
[Raspberry Pi Original Development] amalgamat:
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.
[Raspberry Pi Original Development] 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.
[Raspberry Pi Original Development] KonstaT:
Are you sure you've tested the latest release (20211216) which is the first one that comes with Linux 5.10 kernel by default?
[Raspberry Pi Original Development] Ozi1100:
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 :D ..
[Raspberry Pi Original Development] KonstaT:
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.
[Raspberry Pi Original Development] kevinygod:
Same error for me
[Raspberry Pi Original Development] Ozi1100:
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.
[Raspberry Pi Original Development] KonstaT:
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.
[Raspberry Pi Original Development] 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.