OmniROM Android R (11) for Pi 4

[maxwen]

OmniROM

Download

Images taged with MICROG contain a pre-installed ready to use
microG setup https://microg.org/

Images tagged with WEEKLY can be used to setup
official Google gapps

• 64bit build
• Tablet mode configuration (not Android TV)
• At least 4GB model recommened
• No HW accelerated video playback
• Mesa support for V3D is WIP so expect some graphic issues (especially on higher resolutions - HD 1920x1080 in general should be fine)
• Support of booting from SD or USB by just changing config.txt (check README below)
• GPIO support - monitor and set README.gpio
• chrome (ium) is broken use alternative browser (firefox, edge)
• for screen issues check https://www.raspberrypi.org/documentation/configuration/cmdline-txt.md
• if you experience black bars connect to HDM1 or add disable_fw_kms_setup=1 to config.txt files
• how to do updates? - check README.update

Adjust screen resolution:
To force a different screen resolution edit in /system/build.prop the line
#debug.drm.mode.force=1280x800

Remove the leading # comment and adjust to the screen resolution you want e.g.
debug.drm.mode.force=1280x720

Make sure to also check the README.txt in there
For questions please also use our official Telegram channel
https://t.me/OmniROM_Community

For current progress and how to build yourself check
README.build

XDA:DevDB Information
OmniROM, ROM for the Raspberry Pi 4

Contributors
maxwen, maxwen
Source Code: https://github.com/omnirom/android_kernel_brcm_arpi/

ROM OS Version: Android 11
ROM Firmware Required: 64bit
Based On: AOSP

Version Information
Status: Stable

Created 2020-10-28
Last Updated 2020-10-28

 

[maxwen]

Builds
https://dl.omnirom.org/tmp/rpi4/
The plan is to have about weekly builds - at some point it will be part of all the other OmniROM devices with regular weekly builds
once the Android 11 cycle starts

20201016

• Just a snapshot of the current state
• Non microG builds will come later

20201028

• WEEKLY and MICROG build

20201105

• TWRP included
  IMPORTANT
  Check new recovery section in README for all the details
  
  EVEN MORE IMPORTANT as posted before to get a working TWRP I had to disable userdata encryption for the moment
  that means IF you try to boot this with your old userdata you will get an unpleasent surprise. You must start with
  a fresh userdata partition (mkfs + tune2fs). You CAN (if you know what you do) create an backup BEFORE
  updating by using adb shell and e.g. create a copy of userdata on an external USB device and copy that back afterwards.
  
  But after all of that hassle from now on updating will be much easier since with TWRP you can create
  userdata backups on an external USB device very easy
  
  So going from this release an update could work like this.
  1) boot your current install into TWRP
  2) create an userdata backup on an external USB device
  3) flash the new build - you dont need to care about userdata
  just do whatever you always do with it e.g. resize
  4) boot new build
  5) go into Advanced settings and switch boot mode to recovery and restart
  6) in TWRP restore the backup you created before from external USB device
  7) flash switch_boot_rom.zip and reboot system
  8) enjoy
• add boot mode switch in Advanced settings
• add audio output switch in Advanced settings
• whatever has been done since the last build

20201115

• fixed 5GHz WiFi AP
• fixed Fondar USB touch screen
• actual development

20201122

• switch to new kernel base - big thanks to Konsta - with update to 5.4.77
• update mesa to v20.2
• initial work to support pi camera - not yet working but close
• initial work to support gpio - IF you want to use gpio please contact me on tg cause I was too lazy to create a README for this yet
• all core system updates and fixes

20201128

• performance tuning
• November security update
• gpio support update
• all core system updates and fixes

20201206

• added gpioi-fan
• cpufreq config in advancded settings
• all core system updates and fixes

20201214

• property persist.debug.drm.mode.force to adjust screen resolution
• all core system updates and fixes

20201224

• added disable_fw_kms_setup=1 to config.txt files. This should remove unneeded black bars for some screen when connected on HDM1. I did not see any problems on screens that have no issue with that anyway so I enabled by default. If you face issues remove line and report back please
• enabled showing BT device battery level if applicable
• all core system updates and fixes
• Best Xmas wishes for those who care about it and looking forward to 2021

20201231

• add WiFi firmware for p400
• kernel update 5.4.85
• add userdata resize and project quota enable script in TWRP
• reduce dB of max media volume
• all core system updates and fixes

 

[elhennig]

Does this build support the original RPI 7" touch screen?

 

[maxwen]

Does this build support the original RPI 7" touch screen?

Not out of the box since I dont have one of those to test myself
BUT it should contain the needed overlays so if you know your way around
give it a try and report back if there is something missing.

 

[ich_mind]

Regarding "No HW accelerated video playback", is there a chance this is coming anytime soon?
Thinking about using this for MS xCloud gaming.

 

[elhennig]

Not out of the box since I dont have one of those to test myself
BUT it should contain the needed overlays so if you know your way around
give it a try and report back if there is something missing.

I am afraid I have no idea how to build my own ROM or configure overlays respectively. I guess you just notice from my answer that this is the sad truth

 

[maxwen]

Regarding "No HW accelerated video playback", is there a chance this is coming anytime soon?
Thinking about using this for MS xCloud gaming.

Depends mostly on mesa development - but nothing I would hold my breath for

 

[maxwen]

I am afraid I have no idea how to build my own ROM or configure overlays respectively. I guess you just notice from my answer that this is the sad truth

well - the thing is that this does not have anything to do with building ROMs
should all be possible by modifying config.txt

Looking at the LOST OS builds might give some hints since I think he supports it

 

[maxwen]

Just one word of wisdom here from me since I saw in some reports as something negative
"It’s stuck in “tablet mode” instead of Android TV mode"

I really dont think a raspi is a well equipped device to be used for ATV when you get
a ATV USB stick from e.g. Xiaomi for about 40E that simply works without issues and
has official google support.

So while everyone feel free to use our repostories to create an ATV build dont ask me for it cause I wont do it.

 

[Growking99]

please help after propper flash to my sd card all i get is the no input screen as if nothing is connected to my tvs hdmi port

 

[lernfaehig]

Thanks a lot for the work you put into this.
I'm really looking forward to how this project will develop.

If I may I have a stupid question - is there a way foreseen to safely shutdown the pi? I mean I know how to setup a safe shutdown in e.g. raspbian but I doubt it's the same in android.

 

[maxwen]

please help after propper flash to my sd card all i get is the no input screen as if nothing is connected to my tvs hdmi port

I think you hit me already in TG - but just to reiterate here again - as it is in also the README
Using latest firmware is MANDATORY - 64bit support has been added a few months ago
without you will get the described no boot

Best is to flash latest firmware (which also includes USB boot even if you dont need it)
There are a long list of pages describing how to update. Just linking one here for reference

https://www.tomshardware.com/how-to/boot-raspberry-pi-4-usb

You MUST do that in e.g. Raspberry OS so best do it before even starting with Android

 

[maxwen]

Thanks a lot for the work you put into this.
I'm really looking forward to how this project will develop.

If I may I have a stupid question - is there a way foreseen to safely shutdown the pi? I mean I know how to setup a safe shutdown in e.g. raspbian but I doubt it's the same in android.

Long press the power button in the navigation bar -> shut down

 

[flyl0]

That's pretty cool, thanks for hard work.
But it's still not usable for daily use as a media center since there is no HW accelerated video playback.
All Android builds on raspberry pi have the same issue .. :/
I think that these builds are just proof that you can have Android on raspberry pi than anything else.

 

[maxwen]

That's pretty cool, thanks for hard work.
But it's still not usable for daily use as a media center since there is no HW accelerated video playback.
All Android builds on raspberry pi have the same issue .. :/
I think that these builds are just proof that you can have Android on raspberry pi than anything else.

Welcome captain obvious - tell us something new...

 

[flyl0]

Welcome captain obvious - tell us something new...

It's just an observation lol what I don't understand is that there are almost no differences between Android 9, 10 or 11 for pi, they are all the same.
I wonder what's the real point to make all these builds which all lack the same features.. No disrespect, I'm just wondering.

Captain obvious

 

[maxwen]

It's just an observation lol what I don't understand is that there are almost no differences between Android 9, 10 or 11 for pi, they are all the same.
I wonder what's the real point to make all these builds which all lack the same features.. No disrespect, I'm just wondering.

Captain obvious

You are just too focused on what you want to do with the device

 

[vedforeal]

does it have google apps out of the box

 

[maxwen]

does it have google apps out of the box

of course not - this would be illegal
We are not in China here ...

PS: I did not find any android-11 gapps out there that would work currently
So the only way is anyway microG for now - which is enough for most people

 

[Crypto hacker312]

i tried to boot off 32gb usb and it wont work

and first thing before you say anything about my bootloader being out of date its not here is the bootloader output BCM2711 detected
Dedicated VL805 EEPROM detected
BOOTFS /boot
BOOTLOADER: up-to-date
CURRENT: chu 03 set 2020 12:11:43 UTC (1599135103)
LATEST: chu 16 abr 2020 17:11:26 UTC (1587057086)
FW DIR: /lib/firmware/raspberrypi/bootloader/critical
VL805: up-to-date
CURRENT: 000138a1
LATEST: 000137ad
when i try to boot the build (from the website i didnt compile it) with either the microg or the weekly build after flashing the pi just simply wont start and the green and red light just keeps flashing and nothing happens i was able boot twisterOS just fine off this same usb so its this build i dont know if i did something wrong but the file system was present in gparted and i tried booting it without expanding the partition and with doing so. also i tried to "fix" all the partitions using gparted and that did nothing also i noticed that the /boot directory in this build seems a bit empty compared to my manjaro build i know your working hard on this but this might be a bug in your build and id be willing to help you fix it