yashsingh1/xdaforums huggingface dataset:
[Raspberry Pi Original Development] rabbited:
Would it be possible to add a feature to add a toggle slider that can fully disable Passpoint? The moment I turn on WiFi OmniRom immediately crashes and logcat seems to point to PasspointManager as the cause. I'm researching a way to shut off Passpoint on the OS level but having a UI feature would make life much easier. I don't think that Passpoint was properly implemented in the android-rpi source code as this issue occurs on all related distros (Lineage, android-rpi, Emteria, Omnirom) and on both of my CM4s as well as my 4B. This does not appear to be an issue in all regions as it does not occur when I'm using the RPi in a location where no Hotspot 2.0 networks show up in network search. Unless it can somehow be proven that someone on the forum is able to connect to a Hotspot 2.0 network and that this feature is functional a slider may not be necessary and simply fully disabling Passpoint until the source is working correctly would be an even better option.

AOSP offers this instruction but I have no idea where to edit it:

"Conversely if device implementations do not include support for Wi-Fi Passpoint:

[C-2-1] The implementation of the Passpoint related WifiManager APIs MUST throw an UnsupportedOperationException."

If you know how to make this change I am glad to test it out and report back.
[Raspberry Pi Original Development] maxwen:
logcat?
[Raspberry Pi Original Development] maxwen:
Dont expect me to do your work for free :)

Especially not since it sounds like you will make money from it.

But if you are really working for a company you can contact me to figure

out a deal where both of us can profit
[Raspberry Pi Original Development] mosfet:
Is it compatible with anbox (android on linux)

Hi,

Thanks a lot for your work.

I am currently trying to compile anbox on rasperry pi 4 8Gb running raspbian os 32 bits (GNU/linux 10 (buster)) and I would like to know if it would be possible to use this image with it ?

What I want to do is to have the best (or the worst I don't know yet :D) of the two world, the linux part where I can install all usual packages, server, ... and

on the other hand be able to develop some android applications and have access to existing android apps.

https://github.com/anbox/anbox

At one point I am supposed to use an android.img and this is where I would like to know if what you are providing could work:

https://github.com/anbox/anbox/blob/master/docs/build-android.md

Maybe I could also tried the new ubuntu release for raspberry pi in 64 bits, maybe it would be easier to install or compile anbox...
[Raspberry Pi Original Development] dahuman:
Generic 7 Inch Touch Screen Works

Confirmed to work with a generic 7 inch 1024x600 touch screen from amazon

My issue is since I actually know nothing about this load of OmniROM, I have to idea how to get to the bootloader to flash anything lol. Any tips?
[Raspberry Pi Original Development] godkingofcanada:
Let me know if I can be of any assistance with this image, I have been around here for a number of years, But I am also the owner of Tech Toy Tinker and Retro Arena, we make Linux and Android based emulation and media OSes for a number of single board computers and PC.
[Raspberry Pi Original Development] maxwen:
Yeah most decent HDMI/USB based touchscreen should work out of the box

Allthough I have reports from someone with a "thing" from Aliexpress that has issues

I am currently working to get a somewhat working TWRP out with the next release

until that stay tuned and have fun :)
[Raspberry Pi Original Development] maxwen:
Related to that - I have to bite the bullet and disable userdata encryption for TWRP backups to work

for now - I dont plan this to be permanent but for now I have to do it

For any decent OTA update strategy to work its essential that this works else

you will get mad trying to update to newer versions without loosing all data

Unfortunately the first update will be exactly like that meaning we all

must to wipe userdata (mkfs in raspi terms) once when installing the

next update. But after that you can use TWP to create backups of userdata

on an USB stick to allow easy update without loosing data between.

I will provide in detail desscription on how to do all of that when its time
[Raspberry Pi Original Development] Crypto hacker312:
Is anyone going to answer this issue?
[Raspberry Pi Original Development] maxwen:
You sound like someone has the obligation to answer ...

Wont help - can tell you that much right now

You wrote something about booting from USB?

If yes did you adjust the overlay in config.txt to support USB boot as described in the README?
[Raspberry Pi Original Development] Crypto hacker312:
Yes I uncommented the usb boot line

And commented the sd card line
[Raspberry Pi Original Development] rubencg:
Could you add GPIO interface support to simulate a gamepad/game-control? This could be great for handheld/portable game console applications using the raspberry pi 4 and android with DIY buttons/joysticks.
[Raspberry Pi Original Development] Crypto hacker312:
How do you use root

I notice that selinux is in permissive mode but apps don't detect root how do you fix this?
[Raspberry Pi Original Development] maxwen:
only way is using adb root

So there is no way to use root (su) on the device since this would be too insecure

also selinux permissive is only for the moment - the end goal is to become enforcing
[Raspberry Pi Original Development] maxwen:
from the kernel side gpio should be enabled - I personally did not test so try and report back if something is missing or not working

no - I wont do anything for that since I dont have any need for it
[Raspberry Pi Original Development] BlitzteR:
Good Work

Hi, nice rom for RPI4 (USB BOOT).

Few observations...

Only runs with usb3 ports

was boot looping continuously with my 27" 1440p monitor

working well with waveshare 7inch capacitive touch

The touch is not that good and takes many touches to do anything

Smooth with a wireless mouse

Will be testing with gappps next
[Raspberry Pi Original Development] maxwen:
There is nothing I am influencing here - USB boot is bootloader only

using anything above 1080p is questionable IMHO - 1440p or even full 4k does not work

(I suspect some memory issues there) - thats why its mentioned in the op :)

you can get me a logcat but I suspect some issue with drm_hwcomposer and hdmi

Good luck finding a gapps package out there that works :)

But please report back if you do ...
[Raspberry Pi Original Development] Macbook386:
Hello, first thank you very much for your work.

I am thinking about buying a 5inch screen to build a portable device. My question is is the dsi port working or should i prefer hdmi? Thanks in advance
[Raspberry Pi Original Development] Crypto hacker312:
Good work on the build

There is only one more thing that I've had issues with in the build. It was in usb boot and games such as minecraft or among us wouldn't load up but roblox does pretty well and I also got this notification saying that something was enabled and performance is impacted and it said to disable check the bootloader
[Raspberry Pi Original Development] 100Tomer:
how to connect 2k Screen ?

Hi. First, thank you so much for you work. This is really great, I tried for months to get android work on my raspberry pi with no success.

Second, somebody knows how to make it work with LS055R1SX04 ?

its a 5.5 inch 2k display.
[Raspberry Pi Original Development] maxwen:
I can only say that hdmi works - I know from the LOS builds that other screens might only

work using swiftshader so the sw renderer (which I dont support at the moment).

SO if you want to be on the safe side always choose hdmi/usb

BUT dsi is enabled in kernel and the needed overlays are present.

I know from some waveshare screens that work using dsi allthough

some issues with touch calibration are present

So again - safe side - hdmi/usb :)
[Raspberry Pi Original Development] maxwen:
the warning notification comes from serial console - check kernel cmdline.txt - the warning is harmless and you can disable the notification in the next build
[Raspberry Pi Original Development] Incineroar:
I've been really looking forward to seeing something like this. Only thing I'd want to know is if there's any 4G/LTE radios I could purchase that would be compatible with this. It'd be a great building block to making a custom cellular device if there's a complete OS already.
[Raspberry Pi Original Development] rabbited:
I am not a developer and am using Raspberry Pi as a hobby device. This was meant to be a bug report as I live in NYC which has a population of 9 million and I can't use OmniRom WiFi anywhere in the city so far due to public Hotspot 2.0, so I assume that no one here can. I assume this will be a problem in other cities and since there is very little discussion on the topic and none of the developers of different flavors of Android for RPi seem to experience this in their locale I would say that most people either blame the bootloop on something else or have no idea what causes the problem and give up on any Android on RPi. Here is a thread in another group showing a few logcats where the device reboots immediately following a Passpoint query:

Device reboots when wifi is enabled · Issue #6 · lineage-rpi/android_kernel_brcm_rpi

Hi,sir! When I use you 20200813 rom for pi4,it keep rebooting and rebooting, i catch the debug messages from USB ,please take a look at it,thanks! [ 35.187724] type=1400 audit(1597320517.289:101): ...

github.com

This is not an OmniRom specific issue but the developer of Android-rpi is not responding to questions on his github.

I'll keep working on trying to figure out how to edit device.mk or another file to disable Passpoint to share with the community, I just figured you may have an interest in shutting off a potentially broken feature. One common thread is that every user seems to have an Altice WiFi query right before reboot, so perhaps it's not Passpoint overall but something about Altice's network that causes the issue? If that's the case it only effects users in NY, NJ, CT and the other two states this company serves.

If you'd still like a logcat I'm glad to generate my own. I'll keep trying to sort out how to edit the proper files and share if I figure anything out.
[Raspberry Pi Original Development] rabbited:
I added two logcats. One I did over adb which shows the messages I'm referring to. The other is through Matlog and doesn't contain the same info so I'm not sure it retained the pre-reboot log but can try again tomorrow if Matlog is necessary.

Archive.zip

drive.google.com
[Raspberry Pi Original Development] maxwen:
Don't write essays - get me a logcat

Ofc created with the provided matlog app
[Raspberry Pi Original Development] jigblaz:
omni 12 twrp not opening after setting boot mode to recovery, now i cant do anything

i even tried formatting and reflashing multiple times but same thing happens every time
[Raspberry Pi Original Development] maxwen:
well - after stating the obvious - it works for me

SD or USB boot?

Do you still get adb connection?

BTW: just mount on PC and copy the config.txt.rom to config.txt then it will

be again boot the ROM
[Raspberry Pi Original Development] maxwen:
Dont change logs - use Matlog and save as zip - I want that and nothing else please
[Raspberry Pi Original Development] rabbited:
No logs were edited, MatLog seemed not to be saving the pre-crash info in the log. I'm using an edited service-wifi.jar file that removes the ANQP query code and Wi-Fi now works fine.

I'm now having issues with "Start on Boot" in OmniRemote. I am unable to connect via VNC until I toggle the connect button. The status shows as Running but my laptop reports that the connection was refused until i toggle the switch off and back on.
[Raspberry Pi Original Development] maxwen:
Well - you clearly are unable to follow instructions I gave how to create the log so what do you expect me to think of it

Most prolly your network is not up fast enough after boot

Another Matlog zip - made correctly - would help

Wait about 30s after boot before creating
[Raspberry Pi Original Development] Quantalou:
Hello maxwen.

Thank for your great job.

We are using Android11/RPi4 as internal cheap tool for demonstrator and development purposes (not included in a product)

Some modifications have been done to meet our needs:

-configuration as automotive unit (In Vehicle Infotainment) with a new device derived from your RPi4 support

-management of our specific hardware through a HAL and an App dedicated

To be up to date, I started migration to Android12.

I tried to compile our new version based on Android12. I follow similar instruction from Android11.

But, in resulting build, I don't find kernel image and related stuff.

Do I miss something ?

Android12 version is complete and usable ?
[Raspberry Pi Original Development] maxwen:
Build command is

m; m kernel

Kernel is not built as part of the main build command

12 is as usable as 11 ever was :)
[Raspberry Pi Original Development] Quantalou:
Hello maxwen

Compilation successful, flashing sdcard ok, run OK: thank you very much

It seems that Android12 is faster than 11. (on RPi4B 8 GiB).

(y)

:D

Question: in device/brcm/rpi4/BoardConfig.mk

TARGET_ARCH := arm64

TARGET_ARCH_VARIANT := armv8-a

TARGET_CPU_ABI := arm64-v8a

TARGET_CPU_VARIANT := cortex-a53

Why do you use cortex-a53 ? BCM2711 is a cortex-a72.

Thank again for you great job.
[Raspberry Pi Original Development] maxwen:
The arch values are not really important :)

Important is only arm64 and armv8-a

And it always feels faster if you start fresh :)

But the newer mesa version could indeed make a difference - did not really test
[Raspberry Pi Original Development] Quantalou:
Hello

On my RPi4/Android11, I am connecting a custom display on HDMI#0. 1920x720@60p

This display is not able to provide EDID so I put in /boot/config.txt.rom (and config.txt) statements to setup this display

[HDMI:0]

hdmi_group=2

hdmi_mode=87

hdmi_timings=1920 0 40 40 48 720 0 4 2 3 0 0 0 60 0 89579520 8

hdmi_force_hotplug=1

[HDMI:1]

hdmi_force_edid_audio=1

[all]

# disable kms audio path and force bcm2835 card 0 = hdmi card 1 = headphone jack

dtoverlay=vc4-kms-v3d-pi4,noaudio

disable_overscan=1

overscan_left=0

overscan_right=0

overscan_top=0

overscan_bottom=0

I tested this config with RaspiOS and it is working well.

On RPi4/Android11, kernel command line contains

video=HDMI-A-1:1920x720M@60

Framebuffer seems to be right set:

dmesg |grep -i framebuf

[ 0.323709] simple-framebuffer 3e6b4000.framebuffer: framebuffer at 0x3e6b4000, 0x546000 bytes, mapped to 0x(____ptrval____)

[ 0.323729] simple-framebuffer 3e6b4000.framebuffer: format=a8r8g8b8, mode=1920x720x32, linelength=7680

[ 0.323953] simple-framebuffer 3e6b4000.framebuffer: fb0: simplefb registered!

rpi4:/ # ls /sys/devices/platform/3e6b4000.framebuffer/of_node/

compatible format height name reg status stride width

conti_rpi4:/ # od -t x1 /sys/devices/platform/3e6b4000.framebuffer/of_node/height

0000000 00 00 02 d0

0000004

rpi4:/ # od -t x1 /sys/devices/platform/3e6b4000.framebuffer/of_node/width

0000000 00 00 07 80

0000004

rpi4:/ # echo $(( 0x780)) x $(( 0x2d0 ))

1920 x 720

logcat | grep -i surface

01-01 01:04:33.900 4786 4786 I SurfaceFlinger: Using HWComposer service: 'default'

01-01 01:04:33.901 4786 4786 I SurfaceFlinger: SurfaceFlinger is starting

01-01 01:04:33.910 4786 4786 I SurfaceFlinger: Disabling blur effects, they are not supported.

01-01 01:04:33.910 4786 4786 I SurfaceFlinger: Treble testing override: 'false'

01-01 01:04:33.912 4786 4786 W SurfaceFlinger: Unable to open libdolphin.so: dlopen failed: library "libdolphin.so" not found.

01-01 01:04:33.913 4786 4786 E SurfaceFlinger: Unable to open libframeextension.so: dlopen failed: library "libframeextension.so" not found.

01-01 01:04:33.942 4786 4786 I SurfaceFlinger: SurfaceFlinger's main thread ready to run. Initializing graphics H/W...

01-01 01:04:34.081 4786 4786 F SurfaceFlinger: Missing internal display after registering composer callback.

01-01 01:04:34.081 4786 4786 F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 4786 (surfaceflinger), pid 4786 (surfaceflinger)

01-01 01:04:34.164 4812 4812 F DEBUG : pid: 4786, tid: 4786, name: surfaceflinger >>> /system/bin/surfaceflinger <<<

01-01 01:04:34.191 4812 4812 F DEBUG : #03 pc 0000000000110ed8 /system/lib64/libsurfaceflinger.so (android::SurfaceFlinger::init()+3344) (BuildId: 2728199d2c528c4f4dbae73974da8516

)

01-01 01:04:34.191 4812 4812 F DEBUG : #04 pc 00000000000021a8 /system/bin/surfaceflinger (main+352) (BuildId: bb08dae93d29f9e39f6d8131b048a31e)

This is repeating every ~5 seconds

Any idea ?

Somethings to set into display config ?
[Raspberry Pi Original Development] Quantalou:
I forget, nothing is displayed except the rainbow splash boot screen. Only a little part of services are started.
[Raspberry Pi Original Development] maxwen:
Hdmi config options don't work in kms so all your edits have no effect at all
[Raspberry Pi Original Development] lumo76:
I have a similar issue as in #94 to get a "eGalax Inc. USB TouchController" working. The device is identified when plugin in:

rpi4:/ $ getevent -il /dev/input/event1
add device 1: /dev/input/event1
bus: 0003
vendor 0eef
product 0001
version 0100
name: "eGalax Inc. USB TouchController"
location: "usb-0000:01:00.0-1.1/input0"
id: ""
version: 1.0.1
events:
KEY (0001): BTN_TOUCH
ABS (0003): ABS_X : value 1834, min 0, max 4095, fuzz 0, flat 0, resolution 0
ABS_Y : value 2000, min 0, max 4095, fuzz 0, flat 0, resolution 0
ABS_MT_SLOT : value 0, min 0, max 0, fuzz 0, flat 0, resolution 0
ABS_MT_POSITION_X : value 0, min 0, max 4095, fuzz 0, flat 0, resolution 0
ABS_MT_POSITION_Y : value 0, min 0, max 4095, fuzz 0, flat 0, resolution 0
ABS_MT_TRACKING_ID : value 0, min 0, max 65535, fuzz 0, flat 0, resolution 0
input props:
INPUT_PROP_DIRECT

But it was not reaction correctly when taping on the screen. Thus I've copied the IDC file

cp Vendor_0483_Product_5750.idc Vendor_0eef_Product_0001.idc

This was improving a lot, however it's fare from being precise. Is there a way to calibrate the touch screen or to improve the settings?

Thanks
[Raspberry Pi Original Development] Quantalou:
Hello,

We tried to generate the SDK with command make sdk and it failed.

How to build SDK ?

Regards
[Raspberry Pi Original Development] OldGodShen:
How can I flash magisk?
[Raspberry Pi Original Development] OldGodShen:
How to flash magisk?
[Raspberry Pi Original Development] StuartRothrock:
copy the boot image to /sdcard and install the Magisk apk with adb install. When you click the install for Magisk (in the app), it will ask where he can find the boot image. He will create a patched boot.img to copy over the real boot.img. That is the best of my recall. If it doesn't work, post back here.
[Raspberry Pi Original Development] OldGodShen:
but where is the boot.img?
[Raspberry Pi Original Development] StuartRothrock:
Mount /dev/block/mmcblk0p1 and copy ramdisk.img to your /sdcard/Download directory. This is the image Magisk will patch and deposit a modified version in the /sdcard/Download directory. You will replace your original ramdisk.img you originally copied over. If you wanted to install the Magisk app via TWRP, feel free but I find the adb install of the apk from the magisk.zip we download easier than using TWRP.
[Raspberry Pi Original Development] OldGodShen:
But It failed,
[Raspberry Pi Original Development] OldGodShen:
It print

!Unsupported/Unknown image format

Installation failed
[Raspberry Pi Original Development] StuartRothrock:
I just found my notes. You need to combine the the "Image" and "Ramdisk.img" for Magisk.

apt install mkbootimg

mount partition1 somewhere

mkbootimg --kernel /<mountpoint1>/Image --ramdisk /<mountpoint1>/ramdisk.img --output boot.bin

mount partition4 somewhere

cp boot.bin /<mountpoint4>/media/0/Download/ (becomes /sdcard)
[Raspberry Pi Original Development] StuartRothrock:
The modified boot.img needs to be unpacked.

git clone https://github.com/anestisb/android-unpackbootimg.git

cd android-unpackbootimg

make

<path-to>unpackbootimg -i magisk_patched*.img

cp from new folder magisk_patched-xxxx.img-ramdisk.gz to /boot/ramdisk.img

done!
[Raspberry Pi Original Development] OldGodShen:
OK
[Raspberry Pi Original Development] Quantalou:
Hello,

We are using a display on HDMI#0 with a touch-screen.

How to add a second display on HDMI#1 (without touch-screen) for display only applications (video, presentation, demonstrations...) ?

Regards
[Raspberry Pi Original Development] rabbited:
Do you have a guide for compiling only the kernel for OmniRom that can be transferred into the already built system? Is there a way to find out the kernel config for a current build? I can't find a kernel config or config.gz or similar anywhere else.
[Raspberry Pi Original Development] scottial:
What about "Ok Google" hotword? Is it a way to make it working?
[Raspberry Pi Original Development] busterdude:
Does overclocking the gpu work? i.e. gpu_freq=750.

Also there's a persistent notification that says:
[Raspberry Pi Original Development] jigblaz:
Android 12 18/4/22 build, audio is not working
[Raspberry Pi Original Development] AsColdAsIce:
Hi all,

i'm new here and I need help, every time that I download OmniRoom for Raspberry Pi 4, when I try to burn the image with balena or with rpi imager I only get the boot 134 MB available to burn in the sd card. Where can I download an image file, or how can I fix the file downloaded?

Thanks for your help
[Raspberry Pi Original Development] pi_saab:
Hello

wondering if you can connect a bluethoot dongle to usb port

connect your mobile via it
[Raspberry Pi Original Development] buboleck:
Hello,

I tried the latest build but it seems there is no option to select HDMI as audio output, the 3.5 jack is working. How can I set the HDMI for audio?
[Raspberry Pi Original Development] GeorZ:
The AOSP build system reads the kernel defconfig from here https://github.com/omnirom/android_...fdf67be939f44b301374b62e07/BoardConfig.mk#L57

Nathanchance's Guide is still my go to for kernel compilation, but modern kernel have custom toolchains like ones used in case of rpi4 https://github.com/omnirom/android_...fdf67be939f44b301374b62e07/BoardConfig.mk#L65
[Raspberry Pi Original Development] GeorZ:
Any way to pull logs from a RPI4 stuck on bootloop? Trying to build for another project
[Raspberry Pi Original Development] Quantalou:
Hello, maxwen.

We wish to test RPi4 with latest Android versions

What is the status of Android 12 and Android 13 on Raspberry PI 4 ?
[Raspberry Pi Original Development] GeorZ:
I guess he is busy with A13, but you can find A12 builds at https://dl.omnirom.org/tmp/rpi4/
[Raspberry Pi Original Development] dvx2550:
any way to build omni android tv rom ?
[Raspberry Pi Original Development] maxwen:
I doubt you will find a reasonable way to to this unless you use a WiFi router with a USB stick :)

Android has a very special way how to handle telephony networks and is not prepared to something like this.
[Raspberry Pi Original Development] kiai72:
i have a bootloop: i see the raspberry bootloader, then the colour-screen, then blank - and a few second later it reboots.

it's a 4GB RPI4 with the latest bootloader:

pi@raspberrypi:~ $ sudo rpi-eeprom-update

BCM2711 detected

Dedicated VL805 EEPROM detected

BOOTLOADER: up-to-date

CURRENT: Thu 3 Sep 12:11:43 UTC 2020 (1599135103)

LATEST: Thu 3 Sep 12:11:43 UTC 2020 (1599135103)

FW DIR: /lib/firmware/raspberrypi/bootloader/critical

VL805: up-to-date

CURRENT: 000138a1

LATEST: 000138a1

i already tested:

- take off all USB-devices

- try another monitor

any ideas ?
[Raspberry Pi Original Development] maxwen:
sd card or usb boot?

if usb - DID YOU READ THE README? :)