yashsingh1/xdaforums huggingface dataset:
[Raspberry Pi Original Development] flyingbaloon:
thanks for your response , It would be great if you could include support for these wifi adapters , they are supported

by raspbian out of the box , and are supported in almost all android sbc ,

TL-WN725N -- chipset : RTL8188EUS

Edimax Nano USB EW-7811Un --- chipset : RTL8188CUS

2) I have one more request , In the compute module 4, the usb is disabled by default ,and the keyboard and mouse are not working, so to enable it am adding to config.txt

dtoverlay=dwc2,dr_mode=host ,

this works for once , but after reboot , the config.txt changes back into the original state . could you please guide me about this

The build is stable and works great on the compute module 4 emmc version also

Thanks
[Raspberry Pi Original Development] maxwen:
You did not read the README!

(line 45 AND again 110)

Do it now then its clear what you do wrong -> success

BTW: if you change USB mode you disable USB adb - just saying
[Raspberry Pi Original Development] maxwen:
Well - I can really use that info - and I am too lazy to read up myself

I need the CONFIG_xxx changes that you need in defconfig

Get me a list of those please
[Raspberry Pi Original Development] BradolanBucks:
Hello,

I need local root for automated UI tests (using a shell and the input command) for an application with alien widgets which I wrote as an app, because in an App I already have MLKit and can read texts from the screen without much effort.

Also how do I enable wireless adb permanently on this device if on device root was abandoned completely? I don't have a male USB to male USB cable (would be nonconformant), neither do I know if the USB port of my computer would burn if I would attach the Pi's powering USB-C to it. I mean the Pi already needs a special power source, I doubt my USB3 ports will power the Pi alone, or will they?

Kind regards,

Bradolan
[Raspberry Pi Original Development] flyingbaloon:
Thanks .. its cleared
[Raspberry Pi Original Development] flyingbaloon:
I will read it and update you, still new to the kernal stuff , will figure it out and post, thanks
[Raspberry Pi Original Development] maxwen:
To repeat - with my builds and Omni in general there will NEVER be root

on the device without an adb root shell. You can switch to Konstas LOST

builds if you rely on that

It will boot from a 500mA USB but you can run into issues since it can draw more

So the REAL solution is to use a powered USB hub which I HIGHLY recommend to use

if you plan to do any serious android dev work on a pi

Regarding wireless adb I already mentioned here before

Old style wireless adb using the port property still works

so you can google up for that or read back in this thread

Allthough google has plans to remove that and only allow

the new style handshake pair method
[Raspberry Pi Original Development] KarlS08:
I want to know how i can use my rpi touchscreen becuse its only getting a black scrren when i am booting the device and no omni logo appears
[Raspberry Pi Original Development] BradolanBucks:
Hello,

Thank you for your fast answer. I will connect it using an USB hub then to enable wireless adb. :)

Kind regards,

Bradolan
[Raspberry Pi Original Development] ujagaga:
Hi! I installed OmniROM to RPI4. It seems to boot but then I just get a black screen. I am using a new 24 inch HP monitor vid HDMI. I would really wish to try the Android on RPI4 but all versions I tried do this same thing, just black screen.
[Raspberry Pi Original Development] maxwen:
SPI screens are unsupported cause I cant test those
[Raspberry Pi Original Development] johnpeng:
Good day, Would like to add some driver, can we follow the instruction at

GitHub - android-rpi/local_manifests at arpi-11

Android on Raspberry Pi : Entry-Point. Contribute to android-rpi/local_manifests development by creating an account on GitHub.

github.com

to build your source at ?

GitHub - maxwen/android_kernel_brcm_arpi

Contribute to maxwen/android_kernel_brcm_arpi development by creating an account on GitHub.

github.com

Thanks !
[Raspberry Pi Original Development] Swatmorpheus:
Salut à tous, nouveau sur le forum. je suis domoticien , je ne suis pas un pro d'android mais je peux comprendre rapidement les choses.

J'ai un lineageOS 14 sur un odroid Xu4 dédié pour une interface domotique branché sur un grand ecran tactile, vu qu'il avait un peu de mal par manque de ram avec certaines apps qui tournaient (ds cam, fullkiosk) je suis partie sur un rpi4 8go. J'ai la version 17 Installé opengapp Avec mais je ne ai jamais réussi à installer le play store.

J'ai découvert après ce projet à l'air Qui tout aussi bien Que lineoageOs, j'aiversion la Fait microG Installé.

L'os se lance bien, j'ai bien f-droid etc mais comment installer le play store? j'ai lu qu'il fallait des signature maintenant. Comment faire ?? ous commentaire l'usurpatrice ??

j'ai essayé de télécharger directement les apk via le navigateur mais impossible de les installer, j'ai aussi essayé de télécharger via mon nas et je suis connecté au ds files pour les télécharger mais il me les transforme en .bin alors que c « est bien des .apk.

ps: au pire dans un premier temps j'aurai besoin des apk yeelight , fullkiosk, DS cam, maison Xiaomi

merci d'avance

--------------------------------------------------------------------------------------------------------------------------------------

Hi everyone, new to the forum. I am a home automation specialist, I am not an android pro but I can quickly understand things.

I have a lineageOS 14 on a dedicated Xu4 odroid for a home automation interface connected to a large touch screen, since it was having a bit of trouble due to lack of ram with some apps that were running (ds cam, fullkiosk) I went to an 8gb rpi4. I have version 17 Installed opengapp With but I never managed to install the play store.

I discovered after this project to look which just as well as lineoageOs, I have the fact microG Installed.

The bone is launching well, I have f-droid etc but how do I install the play store? I read that it was necessary to sign now. How to do ?? Do you comment on the usurper ??

I tried to download the apk directly through the browser but could not install them, I also tried to download through my nas and I am connected to ds files to download them but it turns them into .bin while c " is indeed .apk.

ps: at worst at first I will need the apk yeelight, fullkiosk, DS cam, home Xiaomi
[Raspberry Pi Original Development] maxwen:
Stop trying to run PlayStore - it will not work
[Raspberry Pi Original Development] maxwen:
If you can you can

Building Android is not an easy thing so I wont even try to start trying to help you here

unlessI can get the feeling you can find your own nose without telling me how :)
[Raspberry Pi Original Development] maxwen:
Contact me at @maxwen on telegram - easier to discuss over there and we already have a pi group that you then can join
[Raspberry Pi Original Development] KonstaT:
LineageOS. Many people use Lineage for short. Never seen anyone else use LOST (that only seems like some childish petty name calling to me at least).

Maybe remove

from the OP then?

On another note on the OP. As for Raspberry Pi 4 device specific parts this is a build off of lineage-rpi (https://github.com/lineage-rpi) and android-rpi (https://github.com/android-rpi) sources, why is not that information available anywhere here? Actually I've only seen you remove any acknowledgement that this uses e.g. lineage-rpi sources (https://github.com/maxwen/android_d...aa313ea6e9da6424804240aa8ad891fdfe0900L19-L21). You have marked yourself as the sole contributor (twice to be sure apparently) which is totally inaccurate of course. May I kindly remind you that you joined this party at a point when basically everything was already working because other people had put in years of effort to get Android on Raspberry Pi to where it is today.

For someone who has been in the open source Android scene for that long the importance of giving appropriate credit shouldn't come as any news. Even the fact that it's necessary to point this out to you makes this very disappointing.
[Raspberry Pi Original Development] maxwen:
LOST ist a well known term - but if you cant get the joke I cant help you

Dont start the blame game here - this leads to norhing

You dont even share your device tree so nobody knows what you are doing anyway

So you are just pissed that now everyone can build on its own

You even said once was that you dont share cause you dont want others

to make money out of your work - So stop acting as if you are the holy

ghost here
[Raspberry Pi Original Development] KonstaT:
Please enlighten me. I've never been part of your XDA bubble.

I've shared plenty of source code. You should know because you're using the kernel and graphics drivers from lineage-rpi sources. You should also know that building any AOSP-based ROM for Raspberry Pi takes a lot more than just a device tree. There's a long list people who have contributed to get where we are today so me not sharing something isn't any excuse for you to take the credit.

Just something I wanted to point out and not how I would manage things but you do you. Good luck with everything. :)
[Raspberry Pi Original Development] htc_Tomi:
So here's the thing.

Maybe the attribution stuff wasn't right. Not something I want to put energy into writing about because it ain't my thing to be in the middle of.

But this ROM has the most customization I've seen. It's light, and a lot going for it in terms of scripting I don't see elsewhere. Omni has always had that. As I already pointed out, ADB on boot is unique and I tried adding persistance settings to other ROMs to see if I could get it working, but no go. The way you switch between recovery and ROM is more user friendly for blind folks as well because we can just do that from the command line, but the GUI option is still there.

I just ordered a 5-inch touch screen off Amazon. My big problem is still that this can't run headless. I'm exploring to see if there's a way to force an HDMI display to look connected either through config.txt or cmdline.txt. I'm not sure, this always worked in Raspian to force a display connected state and setting a resolution. This build will still not boot without one connected and this limits it being from a portable set up as i need to tether it to a screen at all times. Once I've got speech going, a screen is not needed for me. So this about is the only thing I'm disappointed a bit by.

Otherwise, I think it takes some good effort to get the build environment going, gather sources, make sure it all fits together, debugging stuff through logcat, ETC. I don't think you can say everyone can do that so easily. Again, not saying prior points are invalid, just that it's still possible to appreciate the ROM, what it does and how it works, + that someone is trying to put effort into fixing issues and maintaining releases for the Pi. In my experience Android Pi builds can quickly become out of date once they're a few months of security patches behind. And without a reliable weekly or monthly ROM, which has not really existed up until now, people will forget that it's an opensource board that can't run an opensource OS. Some of that clearly lies with the Pi foundation not acknowledging it and on Broadcom, but at least a four-year effort by dozens of community members with advanced hardware knowledge got us to where we are now. And now a developer is building this semi-frequently. At least I can get behind the idea!
[Raspberry Pi Original Development] Yahnatan.nazir:
Hi everyone, I hope this is the right place to post this issue.

I've got a stock OmniROM running on my Pi4 from an SD card, connected to my tv via HDMI, and I cannot figure out how to fix this issue, where the screen is split at a 45 degree angle with the left and right sides centered and touching each other (photo attached)

This doesn't happen with either Raspberry Pi OS or Kali Linux, but trying to use HDMI settings from either of those systems results in no signal to my screen.

I've spent days searching the web and this forum for an answer to no avail, not sure if anyone else has experienced this.
[Raspberry Pi Original Development] coffeemoney:
Hi Maxwen,

Sorry for the late reply. I was busy on my realife work lately. I got it solved by adding more entries into init.rpi4.usb.rc file with adb root command in the vendor partition.

The problem with the kernel panic is when omni try to switch to accessory mode, it try to look for the vendor code but it is not found, so an exception is thrown.

Here is my file incase you would like to fix it.

Really appreciate for the telegram invite, I will send an request now.

Thanks.

Regards,

Jia
[Raspberry Pi Original Development] maxwen:
I you mean with "HDMI settings" those lines in config.txt then I can tell you that they dont work with drm mode

Can you try on any other monitor if this behaviour is specific to that monitor
[Raspberry Pi Original Development] maxwen:
Thanks for this
[Raspberry Pi Original Development] maxwen:
The device tree is the most important part - and you dont share that

You must share kernel - so you dont have any choices there :)

And I do Android longer then LOST even exists - so nice try but dont try to educate me about that :)

And I will always give credit where credit is due - but its my decision what is worth to credit

because its unique and what is common knowledge
[Raspberry Pi Original Development] KonstaT:
This probably had more context but that seems like a very reasonable thing someone could want.

You seem a bit LOST (pun intended, see that joke is actually funny ;)) about the origin and history of your own project. AFAIK OmniROM was formed because bunch of developers left CyanogenMod because they didn't want someone else (cyngn inc) to financially profit off of their free and open source efforts. I know because I was there at the time (https://konstakang.com/devices/atlas40/OmniROM/) but it was quickly obvious OmniROM is not worth spending any effort on.

Me not sharing something is no excuse for you take credit for other people's work!

I see the way you've acted in this thread so it's totally obvious you need a quite a bit of schooling. Also probably not the best option to play the "I've done this a long time" -card with someone who has done this even longer than you...

You clearly don't because this is a build off of lineage-rpi (https://github.com/lineage-rpi) and android-rpi (https://github.com/android-rpi) sources and it's not mentioned anywhere. In fact you are not giving any credit to anyone and have marked yourself as the sole contributor. No, it's not your decision because giving appropriate credits is also part of XDA forum rules.
[Raspberry Pi Original Development] Wednesday:
I tried it with the dell screen and it worked great!

So far i've only stumbled across 3 caveats.

The interface is abit sluggish but definetely managable.

I can't get the "turn off screen" setting to work, is that not ported over yet to work with external displays?

VNC Server with wired ethernet is a no go for me, wifi only? It doesn't list the ip.

Otherwise, Great job!
[Raspberry Pi Original Development] flyingbaloon:
Hi , sorry for the delay , I am scared of the kernel stuff . these are the config options that i found in https://github.com/maxwen/android_k...85857f43a1949c16/drivers/net/wireless/realtek

config RTL8192CU

tristate "Realtek 8192C USB WiFi"

depends on MAC80211 && USB

select CFG80211_WEXT

select WIRELESS_EXT

select WEXT_PRIV

....

config RTL8XXXU_UNTESTED

bool "Include support for untested Realtek 8xxx USB devices (EXPERIMENTAL)"

depends on RTL8XXXU

....

and for all realtek usb wifi modules :

config WLAN_VENDOR_REALTEK

bool "Realtek devices"

default y

---help---

If you have a wireless card belonging to this class, say Y.

Note that the answer to this question doesn't directly affect the

kernel: saying N will just cause the configurator to skip all the

questions about these cards. If you say Y, you will be asked for

your specific card in the following questions.

if WLAN_VENDOR_REALTEK

source "drivers/net/wireless/realtek/rtl818x/Kconfig"

source "drivers/net/wireless/realtek/rtlwifi/Kconfig"

source "drivers/net/wireless/realtek/rtl8192cu/Kconfig"

source "drivers/net/wireless/realtek/rtl8xxxu/Kconfig"

source "drivers/net/wireless/realtek/rtw88/Kconfig"

endif # WLAN_VENDOR_REALTEK

please include support for these if possible , many thanks to you
[Raspberry Pi Original Development] maxwen:
There is no turn off screen - it will just blank

VNC is WiFi only
[Raspberry Pi Original Development] maxwen:
#boring and not worth my time

but you seem to have more then enough time so just go on and educate us

And then share your device tree so we can see if you did credits there correctly
[Raspberry Pi Original Development] maxwen:
BTW please drop me a note once you pushed your actual sources cause I am busy helping and educating folks here how they can build on their own.

Cause THIS embraces the power of XDA way more then what you do
[Raspberry Pi Original Development] KonstaT:
Boo-hoo, I have no obligation to share my device tree so get over it. Me not sharing something is no excuse for you to take credit for other people's work!

But since you want to talk about device trees. I've only mentioned lineage-rpi and android-rpi sources so far. How about brobwind (https://github.com/brobwind) and GloDroid (https://github.com/GloDroid) and their contribution that you're not crediting.

You think the fact you wouldn't even have basic thing like bluetooth working without brobwind isn't worth giving credit? Here you have literally stolen brobwind's bluetooth HAL. No commit authorship, no source of origin!

https://github.com/omnirom/android_device_brcm_rpi4/commit/032ae8e093f30b5bbf85a7fe9383d3295c258f07

Yeah, try explaining direct copy of 2200+ lines of code as "common knowledge". So https://github.com/omnirom/android#maintaining-authorship just doesn't apply to you?

And that was just one example. Since you are the lead developer (only developer left?)/project leader/whatever at OmniROM your actions represent the whole project. You're taking credit for other people's work in this thread presenting this project in a completely dishonest way. You're taking credit for other people's work in your source trees. This is certainly something everyone needs to be aware of OmniROM.

But since you want to see how this is done properly here's my Pi 3 LineageOS 15.1 device tree on top of the original android-rpi tree with full commit history and appropriate authorship.

https://github.com/lineage-rpi/android_device_brcm_rpi3/commits/lineage-15.1
[Raspberry Pi Original Development] maxwen:
Nice - thanks - buit thats not 17.1 and 18.0 and also not rpi4

So still nobody can see what you actually include in the builds you share

So why you refuse to help people educate themselves and allowing them to create their own

builds to empower the developer base. Cause this is what we all want - right?
[Raspberry Pi Original Development] maxwen:
Will look - thanks
[Raspberry Pi Original Development] KonstaT:
I've found that acknowledging people's efforts is the best way to encourage development...
[Raspberry Pi Original Development] maxwen:
So I can only assume why you even have a thread on XDA then

You just use this as a PR platform but not as a way to support developers

and help others to gain the same knowledge that you have

"XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality."
[Raspberry Pi Original Development] Whyliloo:
Hi. I finished to install the img 'OmniRom Android R (11) for Pi 4' successfully.

I want to connect internet with ethernet. But I can't find the setting menu for setting ethernet ip.

1. Is this AOSP image having only wifi mode?

2. Can I use it for commercial?
[Raspberry Pi Original Development] maxwen:
1) There is no UI for ethernet in Android

Just use DHCP or Google how to configure

2) It's AOSP license and some parts are GPL so it's pretty clear
[Raspberry Pi Original Development] Whyliloo:
Thank you for your comment !
[Raspberry Pi Original Development] KonstaT:
E.g. Pi 3 & Pi 4 specific device trees for LineageOS 17.1 have been out for months.

https://github.com/lineage-rpi/android_device_brcm_rpi3/tree/lineage-17.1

https://github.com/lineage-rpi/android_device_brcm_rpi4/tree/lineage-17.1

Yeah, that is actually it. Rest of it is common between all Pi's.

OmniROM is not open source (https://github.com/omnirom/android#private-repositories) so you can't use that as any argument either.

Yeah, I know leaving out the acknowledgement was part of your PR plan trying to get name for yourself and your project. Sorry it didn't work out and backfired on you. Don't try to spin it on me.

At least you got your XDA news article which was again spread to other tech news outlets. If you ask me probably ended up doing more harm than favors to public awareness about Android on the Raspberry Pi. Hope that was a very proud moment for you knowing it was all based on presenting your project in a completely dishonest way.

Just add the appropriate acknowledgement to people who have made this possible in the first place. I'd hate to have to bring up this discussion every time I see OmniROM mentioned somewhere.
[Raspberry Pi Original Development] Barbara83:
Good to all, does anyone know that Google gapps use is that I can't use any of the ones I know. Thanks
[Raspberry Pi Original Development] maxwen:
I can provide you a kernel Image for testing if you like

Hit me up on TG for faster message turnaround
[Raspberry Pi Original Development] maxwen:
I can only highly recommend that you simply stick with microG

Google PlayStore will simply not work at the moment
[Raspberry Pi Original Development] flyingbaloon:
that would be great ! thanks , i will contact on tg
[Raspberry Pi Original Development] tripLr:
Not trying to start or solve a war between you two.

Here is my my 2 cents.

1. @whoeverbuildsarom.. If you build a rom and others contribute to your rom post a credit.

2. If @propritarychipsetmaker doesn't produce open source drivers ,

And @somehacker figures out how to make device trees , blobs, wrappers, etc to get it to boot, he is entitled to props ( yay look what I did ) and doesn't release his method ( or teach others ) then he is not a dev, he is a hacker. Both have places in this world.

But then your closed source device depends solely on the hacker to maintain it.

by posting sources and methods under the proper open source / shared licence ( not gnu )

He can keep credit, open the device up for other devs ( ie broadcom wifi, bluetooth and network has always been buggy from the factory )

And maybe by pushing the code, the hardware manufacturing will open source it's code. .

Or people will switch to SBC computers with open hardware like riscV and openGL gpu and open AI hardware.

It sucks that the chipset manufacturers close source their hardware. But it's all about $

However the rest of both your arguments are about pride and jealousy.

Which is why I'm starting

github.com/open-roms

Open source trees with the correct licence and recognition built into the code.

I have seen this argument too many times to count.

Developers not getting thanks, recognition etc.

As a rpi4 owner, it's super frustrating to rely on the RPi foundation and chipset for drivers.

Sorry for OT.

But I actually am passionate about both sides of your arguments.

Because so far, no one posts how too's on how to even make a wrapper .
[Raspberry Pi Original Development] cafe.:
Hey, it appears the host you are using for the downloads is down. Did you change the location or is this just temporary?
[Raspberry Pi Original Development] thedelta154:
Same for me, would love to try it but Site is down
[Raspberry Pi Original Development] Andrzej_Ch:
Same for me. i was download a bad version of android, now i can't download a correct version.
[Raspberry Pi Original Development] g33k1:
Can somebody reupload so we can download I would like to try this ROM on my pi
[Raspberry Pi Original Development] cafe.:
Downloads are back up.