yashsingh1/xdaforums huggingface dataset:
[Raspberry Pi Original Development] KonstaT:
I've retired my Pi 3 from development and I'm not aware of anyone still doing any Android development on Pi 3/CM3. The hardware doesn't quite meet today's requirements. Things are now moving forward with Pi 4.

Sorry, I'm entirely sure what is the status of DPI display with KMS driver used with hw accelerated graphics on Android builds. Raspberry Pi OS (and other Linux distros) usually use the firmware/fake KMS (FKMS). Unfortunately this kind of information is not easily available but you'd need to dig the relevant pieces of info from Pi Foundation engineers' random forum post or their GitHub issue tracker.

It's possible that Android graphics HALs also don't know to configure the DPI display. Pretty sure you would need to remove /boot/resolution.txt for start. Generally speaking Roman from GloDroid would know about the Android graphics HAL side of things (hwcomposer/gralloc) but they haven't done any Pi 3 releases.
[Raspberry Pi Original Development] antonio.galea:
Too bad - I will need to figure it out myself then 🤷‍♂️ 😁

As you write, 17.1 feels quite slow on RPi3 devices: but with some optimizing it might prove responsive enough for making a decent head up display. Worst case, I'll try an older LineageOS version.

In any event, thanks a bunch for your answer - and most of all for you brilliant work!
[Raspberry Pi Original Development] lxkarthi:
@KonstaT,

Which Lineage OS version will be fastest on Raspberry pi 3 B ?

17.1 or 16.0 or 15.1 or 14.1 ?

I want to use it as Android TV. So, I will install aptoide and install few applications like TV launcher, VLC.
[Raspberry Pi Original Development] KonstaT:
LineageOS 14 & 15 builds are seriously outdated you shouldn't use for anything anymore.

LineageOS 16 probably performs the best on Pi 3. LineageOS 17 seems a bit more memory hungry and Pi 3 lacks enough RAM for modern Android versions.
[Raspberry Pi Original Development] brownie_nku:
Hello,

I am willing to install Android TV on my Raspberry Pi 3, unfortunately androidfilehost.com seems to be down from some times.

Do you know where I can get the ROM elsewhere ?

I searched for a while, and every website redirect me to androidfilehost.com

Thanks !
[Raspberry Pi Original Development] KonstaT:
AndroidFileHost has random issues sometimes. Try refreshing the download page, try using different browser, or try again later.
[Xiaomi Mi A2 Lite Questions & Answers] TeoXSD:
Today I experienced my first "random" reboot since I owned this phone.

Came home from work, checked the notifications on the device and saw I have 2 app updates I have to make: Google calendar and Facebook messenger. Let play store update the apps and opened them, but when I opened Google Calendar, the screen went black and then it started to roll that color line and I was back on the lock screen. This is the first time something like this happened, so is there a way to check and see what went wrong and what was the cause of that system crash? Also is there a way to reflash via recovery 11.0.7 if I'm already on 11.0.7?
[Xiaomi Mi A2 Lite Questions & Answers] a1291762:
adb logcat from a PC (redirect to a file).

Mattlog or similar from the device.

The logcat is not very big. Capture it quick or you'll lose it.
[Android Auto General] Kitty1233:
hi, my Samsung s20 ultra was working until a few days ago but through mirror link, im trying to connect through android auto but I keep getting a message on my car computer screen saying to connect a compatible USB device, I know AA is built into my fone, It mostly for navigation I need it thanks
[Android Auto General] HdeB:
Your car needs to be able to handle Android Auto. You say you used Mirrorlink. This is a different system. Check if your car is compatible with Android Auto. My guess is, it is not.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] nabril15:
Hello

I need to sell my S4, and it is rooted. I'd like to do a factory reset on it, but I ask if doing so will lose root. I rooted it back in 2017, so I don't remember what I did to it, but I assume that I unlocked the bootloader so that I could root.

I can erase all data and pictures and apps manually, and leave it clean AND rooted, but I might prefer to do a factory reset. If I lose root, it won't be a big deal since any potential buyer of this phone might not even know what root is.

Thanks and be safe
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] StoneyJSG:
Rooting the S4 has nothing to do with the bootloader, if you have a custom recovery installed then you're on the MDL or MDB bootloader which is a rare exploited bootloader. If you want to reset the phone, I would use Odin to do it by flashing the stock firmware you're currently on.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] nabril15:
Thanks Stoney.. Might you know where I can find the latest stock odin file?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] StoneyJSG:
That depends on your current bootloader. You can flash the one you're on or flash a newer one. You can't flash an older one after a newer one though. Check your bootloader, if you're on MDL then you need the MDL firmware. If you're on anything else aside MDL then you will need other firmware.

Try here:

https://xdaforums.com/showthread.php?t=2616221

And

https://xdaforums.com/galaxy-s4/general/s4-unified-guides-collection-t3966126
[Raspberry Pi Original Development] KonstaT:
Here’s my build of LineageOS 17.1 for Raspberry Pi 4 Model B and Pi 400. 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!

https://konstakang.com/devices/rpi4/LineageOS17.1/

There is also Android TV version available.

https://konstakang.com/devices/rpi4/LineageOS17.1-ATV/

Working:

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

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

Bluetooth

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)

HDMI display

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 accelerometer/gyroscope/magnetometer)

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

SPI

Touchscreen/multi-touch (USB touchscreens, Waveshare SPI touchscreens, official 7" touchscreen using SwiftShader software renderer)

USB (mouse, keyboard, storage, etc)

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

Wifi

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 everyone who has contributed to android-rpi

brobwind for bluetooth fixes

Roman Stratiienko and GloDroid project for graphics fixes

Eric Anholt for V3D graphics driver

Maxime Ripard for Pi 4 KMS driver

Google for Android Things platform

Android-x86 project

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

Follow the official Raspberry Pi instructions for writing the image to the SD card (Linux, Mac, Windows).

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/LineageOS17.1/

https://konstakang.com/devices/rpi4/LineageOS17.1-ATV/
[Raspberry Pi Original Development] KonstaT:
Merged commits not mentioned in the changelog.

22.1. 2021 changelog:

add support for sensors (MPU6050, LSM6DS3 & LSM303DLHC accelerometer/gyroscope/magnetometer on I2C)

add support for more serial GPS devices

add support for USB-C (ADB, MTP, PTP, USB-tethering)

enable bluetooth tethering

add settings option for mouse back button feature

update to TWRP 3.5.0_9.0-KonstaKANG

update to Mesa 20.3.3

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

Android security patch level: 5 January 2021 (merged)

20.11. changelog:

device settings improvements

fix audio device option

add CPU overclock option (make sure to take care of cooling if you decide to overclock!)

add SSH option and improve support for built-in SSH server (see FAQ)

fix wifi & bluetooth on Pi 400, should be fully functional now (Compute Module 4 support still untested)

support using HDMI:1 (fix HDMI audio in Android & fix display in TWRP)

fix touch input on Fondar USB touchscreen (thanks to maxwen)

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

8.11. changelog:

initial device settings for various Raspberry Pi specific options (Settings -> System -> Advanced settings)

audio device option (HDMI/3.5mm jack/audio DAC)

display options (graphics drivers, display resolution, display rotation)

options for IR remote, hardware keys, and RTC

fix wrong color format used in some games (thanks to Roman Stratiienko)

simplify booting to/out of TWRP recovery (see FAQ)

improve support for booting from USB devices (see FAQ, thanks to maxwen)

improve support for RTC & IR remotes (see FAQ)

add more options for rotating touch input on Waveshare SPI (ADS7846) touchscreens (thanks to mikenon)

allow switching display off with power button

map right mouse button to back key

initial support for Pi Compute Module 4 & Pi 400 (untested)

update to TWRP 3.4.0-1

update to Mesa 20.2.2 and latest upstream version of drm_hwcomposer

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

Android security patch level: 5 November 2020 (merged)

13.8. changelog:

bring back forced landscape orientation for portrait apps

bring back support for running scripts from /system/etc/init.d/

read resolution from /boot/resolution.txt

fix issue with color format in fullscreen 1080p videos

fix issue with drm video playback

initial support for SSH server

update Mesa to 20.1.5

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

Android security patch level: 5 August 2020 (merged)

27.7. changelog:

initial LineageOS 17.1 build

hardware accelerated graphics

V3D using Mesa 20.1.4 with drm_hwcomposer & gbm gralloc

1920x1080 resolution

update TWRP to 3.4.0-0

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

Android security patch level: 5 July 2020 (merged)

Previous builds:

AndroidFileHost
[Raspberry Pi Original Development] spyrou007:
Thank you mate for the hard work. Keep on improving that beast.
[Raspberry Pi Original Development] depace83:
:good: :good:
[Raspberry Pi Original Development] depace83:
Thank you for your hard work but i'm having a problem my tv hdmi is constantly connecting and disconnecting over and over again while trying this build. I'm using micro usb to hdmi adapter for viewing.
[Raspberry Pi Original Development] CaptainGoodware:
Flashing display

I am having trouble with this build and it’s display abilities, as it makes my display “flash” as the screen goes black for half a second and it comes back.
[Raspberry Pi Original Development] rs13885:
Mic Volume low using Logitech C525

This is working great! The only issue I found is that when using a Logitech C525 webcam, the built-in mic level is really low. Do you know if there is any option to increase it? Thanks!
[Raspberry Pi Original Development] dgershko:
Hello, I installed the newest build, ran the recovery booting script and rebooted. It's now stuck at the rainbow like screen that's shown during boot and I don't see a way to fix this except reinstalling from scratch. Is there a quick fix for this?
[Raspberry Pi Original Development] kakekeke:
Any possibility to get the TV out working? I'm building accessory box that runs Carplay for my car, and i can only weed analog signal to the OEM screen. On previous lineageOS the TV-out was functional, but i was unable to get the carplay usb-dongle to work. Now the system feels super snappy, the USB dongle works... But the TV-out wount work...
[Raspberry Pi Original Development] rs13885:
I had this same issue but fixed it by using a different HDMI port (the one closest to the USB-C port). Hope this helps!
[Raspberry Pi Original Development] CaptainGoodware:
Try switching the Display from HDMI 1 to HDMI 0. They are the ports on the PI.
[Raspberry Pi Original Development] ScorpionKing24:
Couldn't boot in twrp recovery

When I try to go into recovery it stuck at boot screen ! I am using raspberry pi 4, so I use "rpi4-recovery.sh" then try to reboot and then it stuck at boot screen ( color full screen which come while we boot raspbian or any other os for raspberry pi).
[Raspberry Pi Original Development] gandhimaulik:
Any specific reason for this version does not have bootable usb option? i see lineage os 16 version have way to boot from usb
[Raspberry Pi Original Development] Articunos:
I'm unable to connect to any WiFi network. I'm using this on the 4GB model, and it always shows me connecting but never connects. Can anyone help me?
[Raspberry Pi Original Development] KonstaT:
Please read the FAQ on how to switch to SwiftShader that is used in LineageOS 16.0 build by default. I doubt there will be support for analog video with hw accelerated graphics drivers.

Please read the two posts above yours. If that doesn't work see http://disq.us/p/2avnosx

Android 10 uses system as root as default which complicates USB boot because there's two fstabs that you need to edit. I'm not sure if I can come up with some clever solution that will be easy enough for average user. Meanwhile you can do this to boot from USB ( http://disq.us/p/2ayc760).
[Raspberry Pi Original Development] kakekeke:
Is there any way i can enable this in headless setup without serial connection? Any way to create script or something similar to sdcard that will make it work?
[Raspberry Pi Original Development] KonstaT:
ADB or built in terminal. You still need to reach Android UI to enable root access that is needed to make these changes to system. You can also ready the script and make the same changes manually after mounting the sdcard on your (Linux) computer.
[Raspberry Pi Original Development] KonstaT:
New build.

https://konstakang.com/devices/rpi4/LineageOS17.1/

-bring back forced landscape orientation for portrait apps

-bring back support for running scripts from /system/etc/init.d/

-read resolution from /boot/resolution.txt

-fix issue with color format in fullscreen 1080p videos

-fix issue with drm video playback

-initial support for SSH server

-update Mesa to 20.1.5

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

-Android security patch level: 5 August 2020 (merged)
[Raspberry Pi Original Development] major payne:
How well would this work with a 13" -15" screen? I'm looking to make a home made tablet due to the fact as I get old seeing is not as easy as it used to be in bed.
[Raspberry Pi Original Development] duff91:
Any ETA? Just to avoid to do double update one after another..
[Raspberry Pi Original Development] KonstaT:
I'm not going to give any ETA and you're not even supposed to ask for one. If/when it's ready and I feel like it or could be never, too.

Most likely not going to happen before LineageOS team considers 18.0 feature ready and starts rolling out builds for officially supported devices.
[Raspberry Pi Original Development] volfyd:
4k support?

Great project!

I see in the changelog that 1920x1080 is accelerated. I wanted to try to run at 4K, but when I do it's unbearably slow and the OS seems to partially crash back to the lineage OS logo. I don't know if there are any config files I could hand edit to make this better.

Thanks for any tips.
[Raspberry Pi Original Development] KonstaT:
There's been a report that 4k didn't work with some previous builds so that's certainly something if it works at all. There's four times more pixels to render so it's totally understandable that it will affect graphics performance.

You would need to grab appropriate logs (dmesg, logcat) to see why it's crashing. From the previous report I already know it's likely crash due running out of CMA memory. You can increase CMA allocation by editing dtoverlay=cma... line in /boot/config.txt (try 512 instead of 384). There's also 'hdmi_enable_4kp60=1' that you can add to config.txt to increase core/gpu clocks.
[Raspberry Pi Original Development] attacker:
In case I use the argon one case for my pi, can the passive fan being enable with this rom?:)
[Raspberry Pi Original Development] KonstaT:
I don't know about Argon case but in general this build has gpio-fan driver that you can use by enabling an overlay in /boot.config.txt (https://github.com/lineage-rpi/andr...1/arch/arm/boot/dts/overlays/README#L808-L813).
[Raspberry Pi Original Development] volfyd:
[ 781.135227] [drm:vc4_bo_create] *ERROR* Failed to allocate from CMA:
[ 781.141716] vc4-drm gpu: [drm] dumb: 423024kb BOs (44)

Well it does seem a bit better with the changes (not crashing all the way to the logo) but applications still crash and when they do I get messages like this from dmesg.
[Raspberry Pi Original Development] KonstaT:
That's the CMA running out. Did you increase it because that's still at 400mb something? If you need to go further than 512mb you need to use cma-size parameter (https://github.com/lineage-rpi/andr...1/arch/arm/boot/dts/overlays/README#L590-L604).

You can use 'cat /proc/meminfo | grep Cma' to verify that you've managed to increase it and check usage.
[Raspberry Pi Original Development] evilol:
Hi sir, im trying to open jitsi on your rom and Im not able to get my camera to work more than one time:

In the first time that I open jitsi my camera does work, but if I end a call and trying to call someone else I cant see anything with my camera, it is like it doesn't work at all.

Any suggestion for how to fix it?

Thanks ahead!
[Raspberry Pi Original Development] KonstaT:
What camera hardware? Logcat?

Have you tried closing the app from the multi-tasking view in between? Can any other camera apps access the camera after that?
[Raspberry Pi Original Development] Methuselah663:
camera's company is Gold Touch, I tried to do that and sometimes it works and sometimes it doesn't. Im looking for a "stable" rom that will make my camera work all the time without any problems,

do you know what can i do?
[Raspberry Pi Original Development] duff91:
anyone that can help me with the script for the Fan Shim?

i know how to install it on raspbian, but on android i don't have an idea.. or no idea if the install.sh is correct

https://github.com/pimoroni/fanshim-python

P.S. the fan run even without script, but is always on
[Raspberry Pi Original Development] maxwen:
There is no answer you would like to here on that ?
[Raspberry Pi Original Development] risant:
wifi dropout difficult to connect ,, no hdmi audio.. any remedy please help
[Raspberry Pi Original Development] KonstaT:
That's probably just something that you need to deal with for now at least. Raspberry Pi is not an Android device to begin with so there's many limitations due to this fact.

No, in general you can use stuff that's meant for Raspberry Pi OS or other Linux distros. Android doesn't have things like Linux package management, python, systemd, etc.

As discussed on the previous page this build has gpio-fan driver that you can look into.

Sorry, I can't reproduce any "wifi dropout difficult to connect" and I'm not quite sure I even understand what that means. Logcat?

HDMI audio is used by default and should work as long as your display reports it supports audio.
[Raspberry Pi Original Development] duff91:
Everything works perfectly, no wii dropout audio trough hdmi working
[Raspberry Pi Original Development] cem_ari:
I will use Raspberry as carputer just like you. I tried connect GPIO3 to GND with a button but nothing happens. How did you done? Also i would want to know your setup details. I'm sure a lot of person who want to use Raspberry as carputer, just like me, can get help from your experience.

[MENTION=7223862]KonstaT[/MENTION] I'm sorry but where is your script about power on-off. I can't find it.
[Raspberry Pi Original Development] tb2668:
That is all I have done. Maybe you mixed up GPIO3 with pin 3?

However, I don't even need that any more for my project as I have found more convenient solutions.

But I think this does not belong in this topic.

PM me or open another topic dedicated to Raspberry Pi car projects maybe.

If you do so, please send me the link.

Cheers!
[Raspberry Pi Original Development] risant:
sometimes there is an hdmi audio and wifi after restart no audio , no wifi... how to maintain.. hdmi -audio and wifi all throughout?please help.. any modification in configtext
[Raspberry Pi Original Development] cem_ari:
Works perfect. Thank you very much.

[MENTION=5164010]tb2668[/MENTION] Thank you also.
[Raspberry Pi Original Development] cem_ari:
I'v installed Gapps according to FAQ but only blank page in Chrome. Actually pages loaded. There is something If i move the cursor and if i click, loads but nothing on the screen. Default browser and Firefox works without problem.
[Raspberry Pi Original Development] KonstaT:
I'm aware of the issue with Chrome browser.

08-10 13:33:47.080 8525 8550 E chromium: [ERROR:gles2_cmd_decoder.cc(5995)] Error: 4 for Command kCreateGpuFenceINTERNAL
08-10 13:33:47.090 8525 8550 E chromium: [ERROR:android_image_reader_utils.cc(19)] Failed to create android native fence sync object.
08-10 13:33:47.113 8525 8550 E chromium: [ERROR:gles2_cmd_decoder.cc(19006)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : DoBeginBatchReadAccessSharedImageCHROMIUM: shared image begin batch read access failed

Built-in browser and many other third party browsers work fine.
[Raspberry Pi Original Development] cem_ari:
OK, thanks. I thought that i did some mistake :)
[Raspberry Pi Original Development] tb2668:
Hi everyone.

So today I installed the Raspberry Pi with this Android ROM into my car.

Here is a picture if anyone is interested.

However, when I active overscan graphics artifacts show up.

Is this a known issue?

Here is the display section from /boot/config.txt

# Display
[HDMI:0]
[HDMI:1]
hdmi_force_hotplug=1
hdmi_drive=2
hdmi_group=1
hdmi_mode=4
disable_overscan=0
overscan_left=15
overscan_right=15
overscan_top=15
overscan_buttom=15
[all]

Cheers!
[Raspberry Pi Original Development] KonstaT:
What kind of artifacts? Logs?

I haven't received any previous reports about issues with overscan but it's disabled by default in my builds so I don't know if that many people use it.

You could try e.g. disabling hw overlays from Settings -> Developer options -> Disable HW overlays (or add 'vendor.hwc.drm.use_overlay_planes=0' to /system/build.prop for more permanent solution). This will of course decrease graphics performance slightly.
[Raspberry Pi Original Development] tb2668:
So now I am trying to recreate the issue, but nothing is happening.

No black blanks on the screen edges, no artifacts ...

Theoretically, what would be the correct /boot/config.txt configuration to adjust overscan?

Some background information: I connected the Pi to a HDMI --> Composite converter in order to hook it up with my ancient car screen.

Sure, I could have used the composite jack directly, but I want to keep using Mesa.

Thank you. :o
[Raspberry Pi Original Development] jweaks:
Touchscreen question - Flashing this was so easy, and it works! I connected it to an old HP Slate21 Pro via HDMI. The Slate has an IPS touchscreen. Is there any chance I can get the touchscreen working? Is it even compatible? If not, has anyone had success with a particular type of touchscreen, 20" or larger?
[Raspberry Pi Original Development] jweaks:
Not Pi related, but the new forum is buggy. Doesn't navigate properly
[Raspberry Pi Original Development] NTGDeveloper:
Can't wait to try this out!