yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S10+ Questions & Answers] GearCEO:
Hi xda, I am fedup now, I have rooted my S10+ with Magisk and TWRP as recovery. I have done the passcode and FP. But the problem is if I only press power off and restart without pressing 3 magic buttons and enter the passcode then it shows black screen for 2-3 secs and it ask me again to enter passcode. Keeps repeating. Anyone you guys face the same issue?

Thanks and Regards
[Samsung Galaxy S10+ Questions & Answers] SonicFlare:
Yep, i have the same issue with ASF3.

The only semi-working workaround i found, is to not type the pin for few minutes, and then open quick menu, hit settings (enter pin), the settings will be empty, and then quickly hit Search and pray. Most often it will "unbug" itself, and allow the ui to load/continue.

My bet its probably combination of versions of everything.

I have even more interesting followup, after a while, the webview component completly gets broken, and all apps that relly on it, stops working or lag. Google Chrome just cant open any pages, including chrome:// ones.
[Samsung Galaxy S10+ Questions & Answers] GearCEO:
Mine fixed with ASF3, just do a clean flash with the latest TWRP. This works for me. :)
[Android Q&A, Help & Troubleshooting] Skilledfire43:
Hey, so recently I got an LG M153 Fortune, and it seems as though there is no way to access fastboot. I'm sure all devices must have it, so I assume it's just not accessible through normal means? I mean, so far no adb commands have worked, although I can get into stock recovery, there is not much to do with that And no combination of buttons seems to work, either, but of course it is LG, so you never know how much security they might put.
[Android Q&A, Help & Troubleshooting] jwrezz:
It's LG, so they are scumbags that want you to buy a new device twice a year. They don't upgrade and don't allow bootloader unlock on any US devices. Some countries have laws protecting the consumer but not USA. So LG gets away with it. I have a not quite one year old V35 that is on 8.0.0 November security patch. Was told 9 would be q4 2018, then q1, q2 2019. It's now about q3. LG sucks.
[Huawei Mate 20 X Questions & Answers] eyz:
HW removed this feature from the one handed mode, which is very useful for such a big phone.

it's so annoying to stretch my thumb to make phone call now!
[LineageOS Questions & Answers] pompeyrodney:
Morning everybody, I have above phone and have no issues with it, other than the OS. I would like to install a vanilla Android ROM, or Lineage. Can anybody tell me if there is a custom ROM available?
[LineageOS Questions & Answers] Ibuprophen:
I don't have this device myself but, if there's any, it'll be listed within the following area of the forum that's specific to your device.

https://xdaforums.com/huawei-p20-lite

Good Luck!

~~~~~~~~~~~~~~~

Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
[Xiaomi Mi A2 / 6X Questions & Answers] sclip:
I have a fully updated stock A2 (4/64) with the stock back cover and no screen protector. Intermittently, the touchscreen stops responding a few seconds at a time. I have the Show taps - Show visual feedback for taps Developer Setting ON, and when the issue arises, the touchscreen does not seem to register the missed taps at all.

Sometimes, this problem disappears within a minute or two, at other times, I have seen this issue persist for 2-3 hours. A phone reboot does not help to resolve the issue.

I have seen a few threads on other sites where A2 users are experiencing this bug:

1. [url]https://reddit.com/r/Xiaomi/comments/apokxc/mi_a2_global_version_touchscreen_not_registering/[/url]
2. [url]https://reddit.com/r/Xiaomi/comments/ad0slq/xiaomi_mi_a2_touch_screen_sensibility_problem/[/url]

Can someone tell me if this is a hardware issue or whether it is somehow related to the Slow Sequential Write Speed eMMC bug? Thanks in advance!
[Xiaomi Mi A2 / 6X Questions & Answers] sclip:
Bumping; is no one else facing this issue?
[Xiaomi Mi A2 / 6X Questions & Answers] matisern:
I have the same problem
[Raspberry Pi Original Development] KonstaT:
Here’s my build of LineageOS 16.0 for Raspberry Pi 3 Model B and Model B+. It is unofficial and unsupported by the LineageOS team. It’s for advanced users only.

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/rpi3/LineageOS16.0/

lineage-16.0-20200713-UNOFFICIAL-KonstaKANG-rpi3.zip

https://www.androidfilehost.com/?fid=8889791610682891697

md5:3689e767c41858bb53db20190b6542a5

Working:

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

Audio DAC (using PCM512x 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 (VC4)

HDMI display

I2C

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

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

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

SPI

Touchscreen/multi-touch (using official 7” display with SwiftShafer software renderer)

USB (mouse, keyboard, storage, etc)

Wifi

Wifi tethering

Not working:

Hardware video decoding & encoding

Issues:

SELinux is in permissive mode

and more…

Sources:

kernel

Thanks:

peyo-hd and everyone who has contributed to android-rpi

brobwind for graphics and bluetooth fixes

Eric Anholt for VC4 graphics driver

Google for Android Things platform

Android-x86 project

LineageOS team & everyone who has contributed to LineageOS 16.0
[Raspberry Pi Original Development] KonstaT:
Merged commits not mentioned in the changelog.

13.7. changelog:

add ir-keytable tool to configure IR remotes

enable USB gadget support & fix adb toggle in developer options

add support for storage devices with exFAT filesystem

hide su binary when root access is not enabled in developer options

add support for PCM512x audio DACs (tested with Hifiberry DAC+)

improve support for Waveshare HDMI touchscreens

fix recording videos with camcorder

add TWRP flashable zip to resize data partition (see FAQ)

update TWRP to 3.3.1-1

update to MESA 20.1.3 and latest upstream versions of minigbm gralloc, drm_hwcomposer, and libdrm

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

Android security patch level: 5 July 2020 (merged)

7.2. 2020 changelog:

add camera HAL to support Pi camera modules and USB webcams (thanks to Android-x86)

update to MESA 19.3.3 and latest upstream versions of minigbm gralloc, drm_hwcomposer, and libdrm

enable hardware overlays (improves graphics performance)

add option to switch to SwiftShader software renderer e.g. to use official 7” touchscreen or to boot without any display connected (see FAQ)

fix portrait apps on forced landscape orientation (thanks to Ladehunter)

update GPS HAL

option to use DIY hardware power button to boot to TWRP recovery (see FAQ)

initial support for IR modules and remotes (tested with TSOP4838)

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

Android security patch level: 5 January 2020 (merged)

22.12. changelog:

update to MESA 19.3.1 and latest upstream versions of minigbm gralloc, drm_hwcomposer, and libdrm

set default resolution using a configuration file (see FAQ)

add vendor init library to set serial number, revision, and resolution properties

add health HAL to fake battery/charging

add script to enable audio through 3.5mm jack (see FAQ)

add initial support for RTC hardware (tested with DS3231)

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

Android security patch level: 5 December 2019 (merged)

27.6. changelog:

initial LineageOS 16.0 build

hardware accelerated graphics (thanks to brobwind for putting the final pieces together)

VC4 using Mesa 19.1 with drm_hwcomposer & minigbm gralloc

fix bluetooth on Pi 3 B+ (thanks to brobwind)

add initial support for booting from USB devices (see FAQ)

add support for DIY hardware power button (see FAQ)

update TWRP to 3.3.1-0

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

Android security patch level: 5 June 2019 (merged)

Previous builds:

AndroidFileHost
[Raspberry Pi Original Development] sabaatworld:
Thanks for the build. Going to try this out today. Is there any way to connect this to a PC as an android device (like someone would connect a phone to PC)?
[Raspberry Pi Original Development] KonstaT:
Not using an USB cable if that's what you're asking.

ADB works over wifi and ethernet and you can use adb push/pull to transfer files to/from the device (or use an external thumb drive).
[Raspberry Pi Original Development] sabaatworld:
Sad to hear that. Was hoping I could use this RPi as a cheap android device.
[Raspberry Pi Original Development] che0033:
感謝 有個問題 有些APP會在開啟時改變螢幕的方向和尺寸 同時發送出權限請求 系統UI崩潰 配置config有辦法強制禁止對顯示器做任何更改嗎?

Thanks! There is a problem. Some apps will change the orientation and size of the screen when they are turned on. Send a permission request at the same time. System UI crashes. Is there a way to configure Config to forcibly disable any changes to the display?
[Raspberry Pi Original Development] KonstaT:
What app are you using? Steps to reproduce the issue? Logcat?
[Raspberry Pi Original Development] darkchmatak:
Hi I wanted to ask if you plan to add support for USB? I mean to raspberry act like phone when connected though USB to PC. It would make it perfect as phone replacement for using with android auto/AAgateway. Thanks for answer :)
[Raspberry Pi Original Development] turtleletortue:
Nice! I like seeing stuff like this for the pi. I remember having so much fun tinkering with building the oreo lineage15.1 rpi3 stuff a bit ago. Also, I heard something about someone trying to sell your builds of lineage for pie, so will the lineage-16.0 branch for some of the files on the github page for this not be released to the public? Either way, I appreciate your work a lot and hope you can continue as these are amazing!
[Raspberry Pi Original Development] KonstaT:
No current plans.

My LineageOS 14.1 and 15.1 builds are fully open source so there's nothing stopping you/someone else doing this yourself. Shouldn't be any problem adding it here after that (I'll credit the author of course as always :)).
[Raspberry Pi Original Development] KonstaT:
Wasn't trying - was and still is selling builds for $9! Nothing but builds from lineage-rpi sources with some apps bundled in. It was even promoted on Pi Foundation's own MagPi Magazine as his work and the article was brought to my attention. I spent _a lot_ of time on this last fall but couldn't really get anywhere. You can read about it e.g. here and here.

What makes this very problematic for Exton is that he is not complying with GPLv2 that Linux kernel is licensed under. GPLv2 obligates anyone distributing a binary to release a complete corresponding source code. Even if the only modification you make is stick your own name on other people's work...

That is exactly why I haven't published lineage-16.0 branches apart from the Linux kernel (https://github.com/lineage-rpi/android_kernel_brcm_rpi3/tree/lineage-16.0) as that is naturally also my legal obligation. You can't do Android with just the Linux kernel source, though. I was thinking about putting up a private GitLab project where I could share the source code with reputable developers who actually have some ideas how they want to improve what is already available. I know some companies are you using my previous LineageOS builds which is why I've licensed some stuff under non-commercial license in this one. They've been asking for private tech support but I still can't get as much as a donation even when promised. :(
[Raspberry Pi Original Development] turtleletortue:
Wow that's really horrible! I can't believe that it still is happening. I love building stuff on my own(in fact, I was considering trying get any device I have laying around to work for a custom rom someone I semi-know started) and that really makes me sick that you have to deal with that. Hopefully you can get that situation resolved, because I'm sure that's a huge hit in the stomach for that to happen. Really sours the whole open-source nature of things when someone takes advantage of the community.
[Raspberry Pi Original Development] BarryHavenga:
Hi. I am not capable in this kind of development. What would be involved in making the build detect a wired ethernet connection?
[Raspberry Pi Original Development] KonstaT:
Nothing. Ethernet works just fine the last time I checked.

Edit. Tested again and it works fine on Pi 3 B at least. Android has no settings options for ethernet but a small statusbar icon appears when you're connected using ethernet.
[Raspberry Pi Original Development] reversegear:
This is the best implementation of Android on pi till date. Super smooth no more random force close and app not responding.

Note : I have not installed gapps.

[MENTION=304575]konsta[/MENTION] Any chance of running the Android in 1080p instead of 720p

Can some one suggest a remote control Android app which controls raspberry pi. I know lot of wireless mouse available in the market.

Right now Im using a wired mouse I have to go near to tv every time for controlling
[Raspberry Pi Original Development] KonstaT:
You can try editing debug.drm.mode.force property in /system/build.prop and see how it goes (also change display density property or display size from display settings). Already struggling with the limited amount of RAM so this is likely going to affect performance.
[Raspberry Pi Original Development] anthony24x:
Hi [MENTION=7223862]KonstaT[/MENTION], is it possible to dual boot your build using PINN (Noobs)?.

Thanks for your efforts!
[Raspberry Pi Original Development] KonstaT:
You need to contact procount who is developing PINN and ask him. Some time ago he said that he had some problem with adding LineageOS 16.0 support but I don't know about the current status.

Generally speaking I don't recommend using anything else than the latest build from my site. There was PINN support for some previous LineageOS versions but they were never updated and quickly fell out of date. Not that there's currently any plans for any LineageOS 16.0 updates, though...
[Raspberry Pi Original Development] anthony24x:
Okay I see, thanks anyway.

Kind regards
[Raspberry Pi Original Development] freakalad:
nice one; thanks for the effort.

Having trouble getting it to boot well:

Getting via UART console:

[ 25.362997] init: starting service 'zygote'...
[ 25.370050] init: starting service 'netd'...
[ 25.370327] init: Created socket '/dev/socket/zygote', mode 660, user 0, group 1000
[ 25.377921] init: Created socket '/dev/socket/netd', mode 660, user 0, group 1000
[ 25.390606] init: Created socket '/dev/socket/dnsproxyd', mode 660, user 0, group 3003
[ 25.399382] init: Created socket '/dev/socket/mdns', mode 660, user 0, group 1000
[ 25.407649] init: Created socket '/dev/socket/fwmarkd', mode 660, user 0, group 3003
[ 25.491303] init: starting service 'vendor.audio-hal-2-0'...
[ 25.600425] init: starting service 'light-hal-2-0'...
[ 25.634279] init: Service 'light-hal-2-0' (pid 508) exited with status 254
[ 26.575633] binder: release 510:510 transaction 1773 in, still active
[ 26.582181] binder: release 510:510 transaction 1770 out, still active
[ 26.588838] binder: send failed reply for transaction 1773 to 163:278
[ 26.595785] binder: 163:278 transaction failed 29189/0, size 4-0 line 2950
[ 26.602798] binder: send failed reply for transaction 1770, target dead
[Raspberry Pi Original Development] freakalad:
Looks like it ming the an SELinux issue ("avc: denied"), even though it's disabled/permissive in the kernel line (cmdline.txt: "androidboot.selinux=permissive") & in shell `getenforce` returns "permissive".

Out of my depth here, so unsure how to resolve.

[ 1213.339166] init: starting service 'zygote'...
[ 1213.346401] init: starting service 'netd'...
[ 1213.346726] init: Created socket '/dev/socket/zygote', mode 660, user 0, group 1000
[ 1213.353878] init: Created socket '/dev/socket/netd', mode 660, user 0, group 1000
[ 1213.367475] init: Created socket '/dev/socket/dnsproxyd', mode 660, user 0, group 3003
[ 1213.376574] init: Created socket '/dev/socket/mdns', mode 660, user 0, group 1000
[ 1213.385239] init: Created socket '/dev/socket/fwmarkd', mode 660, user 0, group 3003
[ 1213.388209] init: starting service 'light-hal-2-0'...
[ 1213.400649] init: starting service 'audioserver'...
[ 1213.407863] init: starting service 'cameraserver'...

[ 1213.964276] type=1400 audit(1208.439:583): avc: denied { dac_read_search } for pid=1 comm="init" capability=2 scontext=u:r:init:s0 tcontext=u:r:init:s0 tclass=capability permissive=1
[ 1213.981396] type=1400 audit(1213.949:584): avc: denied { read } for pid=15603 comm="surfaceflinger" name="uevent" dev="sysfs" ino=2830 scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:sysfs_gpu:s0 tclass=file permissive=1
[ 1214.005651] type=1400 audit(1213.949:584): avc: denied { read } for pid=15603 comm="surfaceflinger" name="uevent" dev="sysfs" ino=2830 scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:sysfs_gpu:s0 tclass=file permissive=1
[ 1214.025985] type=1400 audit(1213.949:585): avc: denied { open } for pid=15603 comm="surfaceflinger" path="/sys/devices/platform/soc/soc:gpu/uevent" dev="sysfs" ino=2830 scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:sysfs_gpu:s0 tclass=file permissive=1
[ 1214.049478] type=1400 audit(1213.949:585): avc: denied { open } for pid=15603 comm="surfaceflinger" path="/sys/devices/platform/soc/soc:gpu/uevent" dev="sysfs" ino=2830 scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:sysfs_gpu:s0 tclass=file permissive=1
[ 1214.072880] type=1400 audit(1213.949:586): avc: denied { getattr } for pid=15603 comm="surfaceflinger" path="/sys/devices/platform/soc/soc:gpu/uevent" dev="sysfs" ino=2830 scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:sysfs_gpu:s0 tclass=file permissive=1

[ 1214.284596] binder: release 15603:15603 transaction 70725 in, still active
[ 1214.291596] binder: release 15603:15603 transaction 70722 out, still active
[ 1214.298729] binder: send failed reply for transaction 70725 to 163:281
[ 1214.305792] binder: 163:281 transaction failed 29189/0, size 4-0 line 2950
[ 1214.312782] binder: send failed reply for transaction 70722, target dead
[Raspberry Pi Original Development] KonstaT:
Grab a logcat instead and e.g. pastebin it as the kernel log doesn't tell much. You can input commands in serial console as well if you have correct settings in your terminal app (I'm using minicom and IIRC flow control needs to be disabled).

SELinux is in permissive mode so it only logs denials so this is not a problem.

Most likely an issue with the display you're using. You need to use one that supports 1280x720 resolution and reports resolutions it supports via EDID.
[Raspberry Pi Original Development] freakalad:
I've tried it with an config.txt hdmi_mode=85 (720p@60 Hz; a 'safe mode' I use with other RPi projects), but persists.

Will try suggestion, thanks.
[Raspberry Pi Original Development] freakalad:
loaded on a 1080 HDTV (@ lounge) & getting boot logo, but still nothing beyond the moving boot logo non-stop (left on for hour before unplugging)
[Raspberry Pi Original Development] KonstaT:
I think config.txt options are ignored with the graphics drivers used in this build.

Flash Raspbian and execute following commands to see which resolutions your display supports.

tvservice -d edid
edidparser edid

There's a debug.drm.mode.force property in /system/build.prop that is used to select resolution from the list of supported resolutions your display reports via EDID. You can try changing this to something your display supports.

Why not grab that logcat using serial console adapter since you have one because it's impossible to say otherwise...
[Raspberry Pi Original Development] KonstaT:
Doesn't support 1280x720 resolution so you'd need to change value of debug.drm.mode.force property in /system/build.prop to something it does.

Should work AFAICT. If you can see boot animation display is probably not the issue but impossible to say without logs. Make sure you've flashed the image following installation instructions and that you're using proper sdcard and power source of course.
[Raspberry Pi Original Development] TheBinder123456:
Would this work with a CarPlay adapter and a non-OEM touch screen display?
[Raspberry Pi Original Development] KonstaT:
Sorry, I have no idea what you mean with CarPlay adapter and non-OEM touch screen display. If Carplay adapter works with Android devices in general it probably also works here but that's something you need check yourself since you have the hardware and I don't. Only HDMI displays that support 1280x720 resolution are supported out-of-the-box at the moment.
[Raspberry Pi Original Development] BrandonG777:
I tried using this to run a Plex client and video playback was horrible, lots of stuttering. Am I alone in this experience?
[Raspberry Pi Original Development] TheBinder123456:
Thanks. Would you be able to supply a link to a display that is compatible out of the box? Thanks for all you do!
[Raspberry Pi Original Development] KonstaT:
There's no support for hardware video decoding/encoding. Only software dec/enc works. Depends on the app what video formats it uses and how well it plays.

With HDMI display I meant almost any regular TV/monitor.

LineageOS 14.1 and 15.1 builds also support the official 7" touchscreen and people have managed get other touchscreen hardware working as well with some additional effort.
[Raspberry Pi Original Development] Peterlini:
Is there a possibility to use this with gapps for android tv?

I'm not a developer, so if anyone can help I appreciate it!
[Raspberry Pi Original Development] KonstaT:
You don't need to be a developer to try things out! There's instructions in the FAQ on how to install gapps and instead of the pico package, download and install the tvstock package. I think someone tried this with Nougat and it worked but IDK if anyone has tried it with Pie.

I haven't made this into an Android TV image for a reason so people don't make the mistake of thinking that this is supposed to be some media device. There's e.g. no support for hardware video decoding/encoding as this is not an Android device to begin with and Broadcom doesn't provide any Android specific drivers for it.
[Raspberry Pi Original Development] freakalad:
A little lost on the latter, but trying on a different lab monitor capable of running up to 1680x1050. Moving boot logo comes up again, but fails to complete boot process again.

Console repeats:

[ 101.748768] init: starting service 'light-hal-2-0'...
[ 101.787865] init: Service 'light-hal-2-0' (pid 358) exited with status 254
[ 101.795415] init: Sending signal 9 to service 'light-hal-2-0' (pid 358) process group...
[ 101.804666] libprocessgroup: Successfully killed process cgroup uid 1000 pid 358 in 0ms

Image was written/flashed as per site(s):

unzip -p lineage-16.0-20190627-UNOFFICIAL-KonstaKANG-rpi3.zip
| sudo dd of=/dev/sdb bs=4M conv=fsync && sync && umount /dev/sdb*

(can try via Etcher)

logcat via minicom dump: https://pastebin.com/pYUvNbuR

(please keep in mind I don't have root on this device, since I've been unable to get GUI & enable Dev mode)
[Raspberry Pi Original Development] KonstaT:
What device is this exactly? Have you modified the config.txt in any way?

I can tell from the logcat that it doesn't boot because lights HAL can't find the backlight brightness sysfs node. I'm not aware of any other reason it wasn't present unless you have removed one specific line from config.txt.

Since you're a Linux user(?) you can mount the sdcard on your computer and make whatever modifications to any of the system partitions.