yashsingh1/xdaforums huggingface dataset:
[8525, TyTN, MDA Vario II, JasJam ROM Development] veyka:
Does this mean, they might be testing windows update or, is it just a test build? (Sorry, didn't notice the first post update :o )
[8525, TyTN, MDA Vario II, JasJam ROM Development] zocster:
stability

will have to involve cleaning xip region someone told me :D
[8525, TyTN, MDA Vario II, JasJam ROM Development] anryl:
Nobody knows for sure what are they doing but without the complete package SYS+XIP its buggy
[8525, TyTN, MDA Vario II, JasJam ROM Development] veyka:
Good to know, so 20275's the latest "stable" build we seem to have.

I wonder if MS read XDA :D
[8525, TyTN, MDA Vario II, JasJam ROM Development] anryl:
I WONDER :D
[8525, TyTN, MDA Vario II, JasJam ROM Development] CRCinAU:
Try this 20721 XIP... I've ported it from the Vogue...

May or may not work as I haven't tried it yet...
[8525, TyTN, MDA Vario II, JasJam ROM Development] joshkoss:
Trying now man!
[8525, TyTN, MDA Vario II, JasJam ROM Development] anryl:
u can try just change u boot.reg
[8525, TyTN, MDA Vario II, JasJam ROM Development] CRCinAU:
What did you change on this? Is it from what I posted above?
[8525, TyTN, MDA Vario II, JasJam ROM Development] joshkoss:
Boots great sir, just made a few tweaks and works fine.. now need sys.. working on the dump now, it's a bit messed up.
[8525, TyTN, MDA Vario II, JasJam ROM Development] anryl:
no thats my porting m8
[8525, TyTN, MDA Vario II, JasJam ROM Development] joshkoss:
Flashing ported 20721 sys now. i'll let you know if it's a go in a few mins
[8525, TyTN, MDA Vario II, JasJam ROM Development] joshkoss:
well 20721 sys boots now

Hello,

i've ported 20721 from dump and converted. it boots but still requires some tweaking, thought i would share. ;)

Going to bed now!

Later

Sys20721

Uploading the rom for your flashing pleasures gimme 5 mins

Link Pending
[OPPO Reno4 / 4 Pro 5G Questions & Answers] Sandoitchi-san:
Hi guys !

I was just wondering if there's any project of custom ROMs, kernels, TWRP, rooting and all that stuff for the CPH2091.

I haven't seen anything about it anywhere, but I know the device came out pretty recently.

Have a nice day and Happy New Year to everyone !
[OPPO Reno4 / 4 Pro 5G Questions & Answers] Sandoitchi-san:
Still nothing and absolutely no news about any work ongoing :(
[OPPO Reno4 / 4 Pro 5G Questions & Answers] kremmit:
Yeah I'm sad about this as well.

Community needs something to work on but if OPPO hasn't made it available there is not much to be done I guess.
[OPPO Reno4 / 4 Pro 5G Questions & Answers] Sandoitchi-san:
The problem is unlocking the bootloader, it may be possible to compile our own TWRP version as sources are available on the web, but without unlocked bootloader there's nothing to do about it :(
[OPPO Reno4 / 4 Pro 5G Questions & Answers] Rise55Chrom:
I tried a few emails back and forth, asking nicely every which way and they stayed with "We will never allow the bootloader info to be unlocked" with the standard 1-7 reasons why unlocking and rooting is suggested against, blah blah. I love the phone , its too bad.
[OPPO Reno4 / 4 Pro 5G Questions & Answers] kremmit:
Yes it sure looks that this will never happen and i'm pretty sad about this. I should have gone for OnePlus.

Phone hardware is pretty good but this was my first and last OPPO.
[OPPO Reno4 / 4 Pro 5G Questions & Answers] Hamzaiyed:
J'ai un problème avec mon oppo reno 4 pro 5G quand je le mets à jour vers c58 la batterie se décharge rapidement sachant qu'il s'agit de la mise à jour android 11 et coloros 11 quand arrivera la mise à jour d' octobre
[Xiaomi Redmi Note 4 Questions & Answers] Rahuldkdhoi:
All of a sudden I'm not able to use internet on this phone(RN4{mido}) or rom , I don't know . I tried apn settings and other sim related settings , but nothing worked. Please help me out.
[Raspberry Pi Original Development] KonstaT:
Here’s my build of LineageOS 18.1 for Raspberry Pi 4 Model B, Pi 400, and Compute Module 4. It is unofficial and unsupported by the LineageOS team. It’s for advanced users only. Pi 4 model with at least 2GB of RAM is required to run this build.

Important! This image includes parts that are licensed under non-commercial license (Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International). You may use this build freely in personal/educational/etc use. Commercial use is not allowed with this build! You can contact me by email to discuss creating customized Android builds for commercial purposes.

LineageOS 18.1 (Android 11)

for Raspberry Pi 4

konstakang.com

There is also Android TV version available.

LineageOS 18.1 Android TV (Android 11)

for Raspberry Pi 4

konstakang.com

Working:

Audio (HDMI, 3.5mm jack, USB microphones, bluetooth speakers/headphones, etc)

Audio DAC (using GPIO DACs e.g. Hifiberry DAC+)

Bluetooth (and bluetooth tethering)

Camera (using official Pi camera modules & UVC USB webcams)

GPIO

GPS (using external USB modules e.g. U-Blox 7)

Ethernet

Hardware accelerated graphics (V3D, OpenGL & Vulkan)

HDMI display (and HDMI-CEC)

I2C

IR remotes (using external GPIO IR modules e.g. TSOP4838)

RTC (using external GPIO I2C modules e.g. DS3231)

Sensors (using external GPIO I2C modules e.g. MPU6050, LSM6DS3, LSM303DLHC, BME280/BMP280, and APDS9930 accelerometer, gyroscope, magnetometer, temperature, pressure, humidity, ambient light, and proximity)

Serial console (using external GPIO serial console adapters e.g. PL2303)

SPI

Touchscreen/multi-touch (USB touchscreens, Waveshare SPI touchscreens)

USB (mouse, keyboard, storage, etc)

USB-C (ADB, MTP, PTP, USB tethering)

Wifi (and wifi tethering)

Not working:

Hardware video decoding & encoding (software decoding & encoding works)

Issues:

Stock camera app is not working - many third party camera apps seem to work

SELinux is in permissive mode

and more…

Sources:

kernel

Thanks:

Peter Yoon and android-rpi project

Roman Stratiienko and GloDroid project

AOSP reference board developers (dragonboard, hikey, yukawa)

E. Anholt for V3D graphics driver

Maxime Ripard for Pi 4 KMS driver

Android-x86 project

LineageOS team and everyone who has contributed to LineageOS 18.1
[Raspberry Pi Original Development] KonstaT:
How to install:

Follow the official Raspberry Pi instructions for writing the image to the SD card.

If you’re running a recent build (20220121 or newer) you can also update to newer builds using TWRP flashable OTA packages. OTA updates pushed through the built-in Updater app are stored at /data/lineageos_updates/.

Download lineage-18.1-xxxxxxxx-UNOFFICIAL-KonstaKANG-rpi4-ota.zip and save it to your device’s internal storage or use an external USB drive

Boot to TWRP recovery (see FAQ)

Install lineage-18.1-xxxxxxxx-UNOFFICIAL-KonstaKANG-rpi4-ota.zip from your selected storage

(Flash Magisk/other add-ons you had previously installed)

Boot out of recovery (see FAQ)

Changes that are backed up and restored flashing OTAs:

Device specific settings changed using Settings -> System -> Raspberry Pi settings

Manual changes to /boot/resolution.txt and /boot/rc_keymap.txt

USB boot configuration in /boot/config.txt

GApps

Changes that are not backed up and restored flashing OTAs:

Manual changes to /boot/config.txt (and any other manual changes to /boot partition)

Magisk

FAQ:

FAQ is getting quite long and difficult to maintain in several different places. You can find the always up-to-date FAQs here:

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

https://konstakang.com/devices/rpi4/LineageOS18-ATV/
[Raspberry Pi Original Development] onukomer:
Will you share an atv variation 18.1?

Thanks for your hard work. 😊
[Raspberry Pi Original Development] KonstaT:
What does Android TV 11 offer that is not already available in the latest Android TV builds for the Pi 4 (https://konstakang.com/devices/rpi4/LineageOS17.1-ATV/)? Yeah, I know - big version number, much WOW! But besides that, what's the point?

From user perspective I highly doubt you're going have the slightest clue whether you're running Android TV based on Android 8, 9, 10, or 11 unless you go specifically into the about device settings. Android TV builds are also pretty much useless without installing Google Apps. There's currently hardly any working Android 11 gapps packages available and there's certainly no Android TV gapps for Android 11.

From technical perspective I'm currently not aware of any reason why Android TV 11 builds wouldn't work just as much as before but there's just not going to be much reason for it in a long long time.
[Raspberry Pi Original Development] dhtm15:
BITGAPPS ARM Android 11

BiTGApps-arm-11.0.0-R19_signed.zip

drive.google.com

Its portability is incredible, everything works fine, but the only problem I'm having is that version 17 and 18 doesn't work with the mouse in the GeForceNow application, the right button just doesn't work. I tested the OMNI Android 11 version and it works perfectly, however it is full of bugs and poorly optimized. Can you fix this for us? Having a Raspberry PI 4 that works GeForce Now is incredibly awesome!

Another suggestion is how to disable the physical keyboard shortcut keys like F1-F5, because when we try to play on GeForce Now they simply close the application, at least give a function to remap the buttons.
[Raspberry Pi Original Development] KonstaT:
If it helps md5sum for BiTGApps-arm-11.0.0-R19_signed.zip I've used to test is 299182a2d72b977a04360439ed06db8a. It's of course entirely your decision if you trust a download source you can find. You can find more mirrors e.g. in the BiTGApps XDA thread (https://xdaforums.com/t/custom-gapps-bitgapps-for-android.4012165/).

My recent builds map right mouse button to back key. Are you saying that there's Android apps that actually make a difference between left/right mouse clicks? I could add a setting option for that feature in future releases (that's actually already been on my endless list of TODOs).

You can revert to the default keyboard mappings by removing /vendor/usr/keylayout/Generic.kl (or edit that file to change the keymappings to whatever you want).
[Raspberry Pi Original Development] dhtm15:
I think I saw something related to this, that the function of the right mouse button when programmed to return can affect applications that use the right button, this is the case with GeForce Now, which does not recognize the right mouse button in any way, all other buttons are functional. I also tried to see how to remap the keyboard buttons and tried to change these files by adding another one, but it didn't solve the problem, I opened it to edit and I didn't find the F1 function until F5, can you show me where exactly i can edit to remove this?

I found this GApps on the 4PDA forum, I think it's safe because it was a topic dedicated to that.

edit: Correction, I had entered the / root / system / usr / keylayout folder so I hadn't seen the changes.
[Raspberry Pi Original Development] KonstaT:
Yeah, I checked the md5sum and it's the same what I have for the file I downloaded about a month ago.

I uploaded a TWRP flashable patch that will restore the default mouse button behavior and adds an option to Settings -> System -> Advanced settings to enable back key on right mouse click.

Edit. removed, not needed with latest builds anymore.

Deleting custom Generic.kl from vendor partition will use the default unmodified one from system partition. These are the changes that have been made https://github.com/lineage-rpi/andr...001-rpi3-modify-generic-keyboard-layout.patch
[Raspberry Pi Original Development] myspac:
Hello, I try to use this great rom (and others) since 3 days with my PI4 , and "Location" (with waze and maps) never works instead of version 17.

Someone knows why ?

Thank you
[Raspberry Pi Original Development] williamparker:
Enable root access, was a switch under developer options in 17.1 nowhere to be found in 18.1. Tried flashing a SU from TWRP, nothing shows up. Am I missing something here?
[Raspberry Pi Original Development] KonstaT:
You would need to be a bit more specific. Are you using actual GPS hardware or do mean e.g. Google network location (which depends on gapps being installed)?

Please read the FAQ on how to have root access. It's still under consideration if I'm going to bring back built-in su because there's no specific need for it anymore.
[Raspberry Pi Original Development] myspac:
Thank you for your answers !

Oh.. yes, I mean Google network location; so , the problem is on gapps: Ok, thank you. I use : open_gapps-arm-11.0-nano-20210104-UNOFFICIAL_TEST.zip, it was ok with open_gapps-arm-10.0-pico-20201223.zip and your "17 version". I m trying other rom (OMNI) with other gapps and I had the same specific problem: that's why I think it was a "18 rom" 's problem...

I have and need root access, but it was ok with the FAQ.
[Raspberry Pi Original Development] Micka41:
Hello,

In Linphone, Bria, ... I can't use my USB microphone (no recorded sound), but it works well in a voice recorder application.

It is also not possible to choose a ringtone.

Do you have an idea about the microphone problem?

Thank you for your work
[Raspberry Pi Original Development] myspac:
Ok, this is my last tests, all without gapps:

- I take your last rom

- connect an hardware gps by bluetooth

- install by adb the app "GPS Bluetooth" to mock the location

- install waze (by adb)

- install maps (by adb)

After:

- MAPs works

- WAZE: my location is ok but the map is not displayed: I didn't know why (if works with your rom 17).

I took an old waze version: and after re set all permission in the app setting AND by Privacy menu (not same permission when I cick on All permission of waze!!!! ???) => it was Ok too, location and map.

I re take last Waze version, but I never success to display map.

In data/wifi usage of the waze app: 0 ko !!!!

I don't understand why some applications (Android Auto too) can't access to network and why permissions are not the same by app's info and by Privacy setting menu. (It was ok with version 17 of your rom).
[Raspberry Pi Original Development] non1oson:
awesome work! i was reading your work and i have a question if you or anyone can chirp in too for ideas.

whats the benefit besides privacy using your build of lineage over raspberrys os?

if it were used offline as storage, but wake on lan when needing access using nextcloud or people recommend nextcloud alternative? also emails nextcloud isnt e2ee, but Tutanota is but i dont think its capable running on nextcloud.

some personal some work so transfering to devices its main purpose is security. maybe running a work chat system e2ee which will also be safer than online apps out there.

TL:DR: dont want to pay for storage cloud, messaging services online for work when we can do it ourselves and overall safer from uninvited guests :ROFLMAO::ROFLMAO:
[Raspberry Pi Original Development] htc_Tomi:
Thanks for this ROM! I understand a lot of stuff here is still experimental, but I look forward to trying this out. I will be getting a 5-inch touch screen next week sometime so I also plan to test performance with it (it's only 800x480, so not driving millions of pixels with the Pi either.) If I had to estimate, the Pi 4 is about as fast as a Galaxy S5 or S6 was, slightly slower than a snapdragon 820. So it's not midrange or high-end, but I think it is more in the upper parts of the low range in terms of raw performance. You can safely boost the clock to 2.2 gHZ, which works well provided you have the thermal cooling to do it without a throttle. I also use a Pi 400. The Pi 400 runs a lot cooler even at the default 1.8, and I have safely pushed it to 2.2. It makes it slightly faster but not a major boost in Android by any means.

If others have had experience getting the USB Type C working on this rom, let me know. I understand it's commented in config.txt, so I plan to uncomment it there and look in /vendor/etc/init/hw/init.rpi4.rc to change it also with my Ubuntu machine. I'm fully blind, so using ADB on this to get talkback working is essential. So far I have used the network boot to do this, installed both an APK for Google TTS and Talkback, got it working just fine after adding values to securesettings. Great news. At least for now, new users wanting ADB access should connect their Pi through ethernet and then connect to ADB over the network, I think this is easiest. I have a USB type C hub here which is powered so I'm able to hook the Pi directly to my computer and do it that way a bit easier than fiddling around in the router for this stuff, and maybe more secure as it is only over USB. But the network way is probably easier for more folks to get going as well. Ups and downs, just as everything to life, right?

I also am wondering if we can get USB ADB over TWRP. This would be a huge win but I will test this and report back on this thread. Again, my only choice is to use openrecovery scripts, not really to find a sighted pair of eyes and ask them to help out reading the TWRP screens. I actually don't have that help available at the moment as my partner and I are both blind. So everything I get to do I have to do in a commandline or speaking way. But I think even despite those odds, this is doable and the disabled need to push ahead in this space anyway if they too want to be tinkerers as it is.

Thanks for working on this and making Lineage accessible to many. It's been yours and other Pi community hardware enthusiasts' effort which got this up and running. I was actually able to get one of the Pi3 builds you posted running with Talkback but at the time I just didn't find the Pi 3 that good for running Android. Certainly not with 1 gig of ram, something the Pi 4 gives us a lot of choice with at least.
[Raspberry Pi Original Development] KonstaT:
It's still very early days for Android 11. Many apps have not yet been updated to support new features it brings. There still could be issues with integration in upstream LineageOS as well (builds are not yet rolling out for officially supported devices so I'm not sure it can be considered feature ready). Gapps are really not ready for Android 11 yet.

There are options that are more feature ready and more thoroughly tested if you're not only after the Android version number.

It's still very early days for Android 11. Many apps have not yet been updated to support new features it brings. There still could be issues with integration in upstream LineageOS as well (builds are not yet rolling out for officially supported devices so I'm not sure it can be considered feature ready). Gapps are really not ready for Android 11 yet.

There are options that are more feature ready and more thoroughly tested if you're not only after the Android version number.

I guess the main benefit is that it's a completely different operating system. It's Android - it runs Android applications.

If you/anyone wants to test ADB over USB-C there's two lines you need to uncomment for testing (both LineageOS 17 & 18 should be OK for this).

One line /boot/config.txt under 'USB-C' section:

dtoverlay=dwc2,dr_mode=peripheral

Another one in /vendor/etc/init/hw/init.rpi4.rc:

import /vendor/etc/init/hw/init.rpi4.usb.rc

I don't have any hardware that would provide enough power for the Pi to test this myself. If anyone has recommendations on powered USB-C hubs that are known to work on the Pi 4 for this purpose I'd appreciate that.

My TWRP builds don't support ADB. This is because TWRP has no network support (wifi/ethernet) and I can't test the USB-C for the above reason.
[Raspberry Pi Original Development] htc_Tomi:
I can definitely say that uncommenting those lines did get me ADB over the USB type C port. So it does work in this mode successfully. I could then do adb root and at least have some access similar to TWRP minus the flashing and back-ups.

I think the problem with some powered hubs could be the power delivery. I'm not sure if you have a type-C port already on your machine, but it may provide the full 10 GBPS/3A requirement if it's a direct type C port. The 3.0/3.1 gen1 hubs only provide 1.5A of power and 5 GBps, so while the Pi could run on it, you couldn't power any attached devices and would get the reduced lightningbolt symbol performance as well. The powered hubs have dedicated charging ports, but these wire directly to the hub and not the machine, so while providing more power at a cost.

I also tried installing Gapps (BitGapps) for Android 11 but it failed once I signed in with a Google account. Oh well. 32-bit Gapps are also harder to come by anyway. For now I can always sideload apk files which don't rely on the play stuff and use Chrome for browsing. That's a good start.

The reason I need Android 11 is mostly for accessibility. Unlike for sighted folks where lower Android versions don't make an impact on how and what you can use, for the blind, each Android version introduces changes to the accessibility API. This is important as these changes can allow for things like brand new touch gestures (completely different gestures/ swipes and touches in Android 11 with Talkback ) to actual improvements on what the screen reader "sees" in the UI. So no, I'm not doing this to just have the version number myself, but to benefit from the latest changes to Android's accessibility API. I hope this makes sense.
[Raspberry Pi Original Development] KonstaT:
Thanks for confirming that ADB over USB-C is working. This might be something that will be enabled by default in future builds.

Latest BiTGapps (BiTGApps-arm-11.0.0-R19_signed.zip) should work just fine. I haven't received any other reports with issues.

Yes, I totally understand that new Android versions bring improvements, that's the whole point. But IMO simply having a bigger version number shouldn't be any reason for doing releases if it's not otherwise feature ready or some things are broken. This is a bit of problem in this "scene" where early utterly broken stuff is being endorsed just because of the version number.
[Raspberry Pi Original Development] s4goa:
OK my Philips USB cam works nicely in VLC in Linux, but several Android cam apps do NOT recognize it on the pi4 .

seems, I jumped to a pars pro toto... :unsure:
[Raspberry Pi Original Development] s4goa:
compare https://xdaforums.com/t/usb-otb-host-uvc-webcam.2563512/post-48336026
[Raspberry Pi Original Development] rgstephe:
I am looking for some help. I am running Lineage os 18.1 PI4. I also have a CarPiHat Here:

GitHub - gecko242/CarPiHat: A place to store files and info about the CarPiHat - Raspberry Pi Car Interface PCB

A place to store files and info about the CarPiHat - Raspberry Pi Car Interface PCB - gecko242/CarPiHat

github.com

I am needing help getting the shutdown script working.
[Raspberry Pi Original Development] s4goa:
can we use this cam software ?

GitHub - android-rpi/RpCamera

Contribute to android-rpi/RpCamera development by creating an account on GitHub.

github.com