yashsingh1/xdaforums huggingface dataset:
[Raspberry Pi Original Development] trngw:
Hi

I connected a U-Blox GPS unit via USB, and can see it when I do lsusb, but no apps seems to get in contact with it. Not even U-Blox BLE.

Is there some specific driver I need to install or activate? Like perhaps the Github U-Blox?

EDIT: I did a chmod on /dev/ttyACM0 and then I could do cat /dev/ttyACM0 and see some info sent from the U-Blox GPS, but the apps does still not recognize it. As far as I can understand I need to make the U-Blox GPS appear as the native Android GPS.

Thanks
[Raspberry Pi Original Development] KonstaT:
You need the have the USB GPS dongle connected when you boot the Pi for the Android GPS HAL to detect it.
[Raspberry Pi Original Development] Growking99:
Hello! Sorry if this is a dumb question but is there a boot.img for this build? I am wanting to install magisk and use mods. Thanks!
[Raspberry Pi Original Development] KonstaT:
No, there's no boot.img. As Raspberry Pi is not an Android device to begin with things are structured a bit differently. You can find kernel (zImage) and ramdisk from the boot partition.

This still worked for LineageOS 16.0 but as Android 10 uses system as root it complicates things even further.
[Raspberry Pi Original Development] pepperspray:
Hello,

Just loaded up the build and installed as per the instructions listed. When I boot my RPI 4 (4gb), I see the rainbow screen, followed by the Lineage loading screen. After the Lineage loading screen, my screen freezes (on the screen that says 'Emergency' and 'Next' at the bottom) - and then simply reboots. What did I miss? :confused:

Thanks for any assistance you may feel would be helpful. Cheers.
[Raspberry Pi Original Development] KonstaT:
Could be the same issue that's been discussed e.g. http://disq.us/p/2ax3vmu, https://github.com/lineage-rpi/android_kernel_brcm_rpi/issues/6 & https://github.com/android-rpi/device_arpi_rpi4/issues/39.
[Raspberry Pi Original Development] tsnakes:
I run Pi 4 with 17.1 also with the german SkyGo app. When the streams start, there is a blue cast. The stream runs perfect without errors and also smooth. Only when I press "Enter" or "Spacebar" and keep it pressed, the blue cast disappears.

with swiftshader there is no blue cast but the stream runs with errors and not smoothly.

with mesa there was a blue cast but the stream runs smoothly and without dropouts.
[Raspberry Pi Original Development] KapriQ:
I have 2 Q.

1) Will be HW acceleration supported soon?

2) How Can I overclock cpu / gpu ?

Thanks
[Raspberry Pi Original Development] KonstaT:
1) Things that are working and not working are listed in the first post. Hardware accelerated graphics is already working. There is no any ETAs for anything besides when it's ready.

2) Exactly the same way as any other OS for the Pi. https://www.raspberrypi.org/documentation/configuration/config-txt/overclocking.md
[Raspberry Pi Original Development] KapriQ:
Thanks KonstaT for your reply, appreciate,

I meant -> Hardware video decoding & encoding, because Kodi is not working well :(. (I know that for kodi i should use LibreElec,) There are vertical tearing due to missing hw encoding i think.

I am using cheap android tv box, where is everything working as should, and i am disappointed for now with rpi4 :(. Maybe i have expected too much from that mini pc. Extreme tearing in raspbian etc... Can´t even play 1080p60fps video without lags. Too low power.

I have tried many OS, but i think i will stick to my Amlogic s905x3 for now (I can play smooth 1080p in 60 FPS also in HRD.)
[Raspberry Pi Original Development] GizmoTheGreen:
Has anyone tried Genshin impact on the pi 4? how's performance? xD

edit: oh, it can't install, their APK only has 64bit libs so any 32bit android builds are no dice :(
[Raspberry Pi Original Development] RaghavTeck:
Please help me someone , I'm really looking forward to use this
[Raspberry Pi Original Development] Amao_Three:
Great work! :good:

Could I suggest to add the option to remove the navigation bar in the setting>system>button?
[Raspberry Pi Original Development] Saftpresse99:
I have the same problem. [MENTION=7223862]KonstaT[/MENTION] . Do you have an idea what this could be?
[Raspberry Pi Original Development] KonstaT:
No idea. Logcat? Have you tried the suggested workaround under 'Issues' for wrong color format used in some occasions?
[Raspberry Pi Original Development] tsnakes:
HW overlays are disabled!
[Raspberry Pi Original Development] Saftpresse99:
I tried the workaround. But without luck.

Here is a logcat..
[Raspberry Pi Original Development] KonstaT:
Sorry, don't see in the log what could be the problem. Useful bit of information is that this apparently happens on both Pi 3 (log is from Pi 3?) & Pi 4 because there's some difference between the devices how the graphics drivers are used. And since this wasn't reproducible with SwiftShader, it's an issue with the graphics drivers that are used by default.
[Raspberry Pi Original Development] Saftpresse99:
Yes, it is from Pi3 and swiftshader works with pi 3 too. No blue frame, but stuttering.

Perhabs [MENTION=11152335]tsnakes[/MENTION] could create a logcat from pi 4. Hopefully with more informations.

Thank you
[Raspberry Pi Original Development] sdeep159:
Screen timeout causes power off

Making use of screen timeout after x amount of time using this image switches off the Raspberry Pi 4 for me - complete power off, no lights on the pi.

Any thoughts on what the issue may be or of a fix?

I plan to use this with a touchscreen and I do want the screen to time out.

I am using the official pi power supply and have tried a new rev 1.2 board as I thought it may be a power issue but the behaviour is the same.
[Raspberry Pi Original Development] KonstaT:
Android 10 requires suspend which doesn't work on Raspberry Pi. If you switch display off, device will try to enter suspend and crash. That's why I've disabled any easy to switch off display for now (i.e. short power press).

LineageOS 16.0 build has suspend disabled on kernel so it doesn't have this issue.
[Raspberry Pi Original Development] sdeep159:
Thank you, I will use your 16.0 build.

Appreciate the help.
[Raspberry Pi Original Development] m k scott:
Hello,

I’m making a sort of magic mirror out of this build using Nova Launcher and the Alexa app as voice input and output to the screen via the Microsoft ToDo app. Working pretty well so far. Except, the launcher and/or the ToDO app seem to be causing some instability/crashes.

I want to try installing them as a system apps to see if that helps, but I believe this ROM handles things a differently to a phone ROM.

And here’s the newb question. Is that even possible on this ROM, if so, how should I go about it? I’ve used Titanium Backup to do similar on phones.

Thank you!
[Raspberry Pi Original Development] KonstaT:
What kind of instability/crashes? Logs?

I highly doubt it's going to make any difference whether you convert something into a "system app" (i.e. copy it to system partition what you likely mean here). There's really no need for it either unless your app was to use system level permission for which you'd need it to be signed with platform keys.

There's obviously some differences because of the hardware so this not what you'd consider a normal Android device (HDMI display, OS is on external storage device such as sdcard, use external input devices though touchscreen is also possible, etc). From Android OS side of things it's really not that different. Only the boot partition structure is different to what you'd find normally but otherwise this is just a regular Android build you'd find on phones/tablets.
[Raspberry Pi Original Development] m k scott:
Thank you very much for your clear reply. Most helpful! apologies for using the terms (instability/crashes) it was inaccurate and Ill thought though.

I believe I have narrowed the issue down to Nova Launcher and their implementation of Widget selection. I am unable to press- hold and drag any to the Homescreen using a (Logitech K400 Keyboard) the same result when trying with a USB mouse. I can scroll through and highlight them, but that’s all. However, there is no problem moving Widgets to the Homescreen using the Pixel or Microsoft Launchers.

So, as far as any instability/crashes, this seems to be totally down to Nova failing and defaulting to Pixel.

I’ll tinker some more with Nova settings or maybe try making Nova system at some point but I’m just enjoying using your ROM on the Rpi4 atm. If I have any success, I’ll post in case it’s of use to others.

Thank you again.
[Raspberry Pi Original Development] KonstaT:
Yeah, that's related to input devices that are not commonly used with Android. It's been reported that e.g. mouse long press doesn't work with some launchers (Nova has been brought up before) and web browsers to drag icons/widgets or open context menus, etc. Android handles mouse presses and touch events differently and many app developers haven't likely considered this. I think that this is something that should be fixed with the app and if you can reproduce this on other devices as well (you can also use external mouse/keyboard with most modern Android phones/tablets) you should report it to the app developer.

You can select the default launcher from Settings -> Apps -> Default apps -> Home app. Anything crashing isn't normal of course but it shouldn't launch a non-default launcher at least.
[Raspberry Pi Original Development] ayaromenok:
Mesa master repository now include Vulkan 1.0 driver for RPi4 - it would be nice to see it in some builds in future.

Maybe not switched On by default (since Android 10 required Vulkan 1.1(and may use it for UI) and driver itself can have some crititical bugs)
[Raspberry Pi Original Development] DushyantC1:
Facing the same issue

I am facing the same issue with my TV an d Projector. Did you find any resolution.
[Raspberry Pi Original Development] DushyantC1:
Need help, as not working on TV & Projector HDMI. Restarts

Hi,

I have Raspberry Pi 4 8GB with official Raspberry Pi 3A Power supply adapter.

I have tried burning both 16 and 17.1 build for normal Android as well as ATV. I am having the same issue with all 4 builds. It first shows Rainbow screen and then shows Lineage OS boot animation and then Lineage wallpaper after that it restarts. It makes a loop of restart. For ATV builds, it reaches Bluetooth Nexus player remote screen where I think we need to press F2 to go ahead, but it keeps the screen for a second and restarts and makes a loop of restart from there. I have tried lowering the resolution in resolution.txt file. I have gone through the HDMI Group and HDMI mode option on raspberry website as suggested by you on your website. I ran Raspberry OS and find out the modes supported by my screen using the command on terminal for DMT and CEA. I tried most of them in config.txt file. My screen supports 1,2,3,4,5,7,16,17,18,19,20,22,31,32,34 for CEA mode and 4,9,16,35,39,47 for DMT. I am not able to find the reason of restart.

I also tried Libre OS for KODI, it works fine. Raspberry OS is working fine.

I have used 40 inches TV HDMI and Full HD projector HDMI which supports 1920x1080 resolution. It is behaving same on both.

Also want to add that CPU is not over heating. I can touch it with fingers.

Please help.

Regards

Dushyant
[Raspberry Pi Original Development] DushyantC1:
Now Stuck on Wifi network selection screen

I disabled the wifi, It successfully boot up but it now stuck on Select your Wifi Network. It is not allowing me to skip the wifi connection screen. I have inserted the LAN cable, still it is not connecting to internet, I mean still it is not allowing me to bypass the wifi connection screen
[Raspberry Pi Original Development] Longturd:
I had a little problem with WIFI at first. There is an option to not have WIFI turn off, enable that then give it a minute. Maybe try to force it a few times.
[Raspberry Pi Original Development] sdeep159:
No HDMI Audio

I have moved back to your 17.1 build from 16.0 as I found 16.0 much slower.

The 17.1 build works great apart from no HDMI audio for me even with a clean install.

I am using an Elo 2002 touchscreen and HDMI audio worked fine with the same setup using the 16.0 build.

I have tried changing things in config.txt with edid_audio, audio param, hdmi_group but no luck.

Any advice on this please? Could it be the Hardware Acceleration parameter?
[Raspberry Pi Original Development] KonstaT:
HDMI audio should work if you have a display that reports it supported. You could try removing/commenting out 'hdmi_force_edid_audio=1' from /boot/config.txt. There's been some mixed reports about its necessity with different displays and I'm not sure if it's required with the latest kernel at all. hdmi_* options have no effect when using KMS driver that is used for hw accelerated graphics in this build.

Audio drivers are a bit different with 5.4 kernel (LineageOS 16.0 build still uses 4.19). Paremeter in the vc4-kms-v3d line is to disable the separate VC4/V3D audio interface (not working) and expose the bcm2835 card that we want to use.
[Raspberry Pi Original Development] sdeep159:
Thank you.

Commenting out 'hdmi_force_edid_audio=1' did not work for me.

I also did try another device - a Sony TV and changed HDMI cable but no luck.

I also tried adding 'snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_compat_alsa=0' to cmdline.txt file in /boot as per the Rpi forum.

I will take the greater speed and live with no hdmi audio out.

Thanks again for this ROM :good:
[Raspberry Pi Original Development] tb2668:
Hi. First of all: Great ROM!

I am using it for my car computer project and it works great so far.

Since I am fairly new to coding, maybe someone can point me in the right direction.

I am trying to write a script that monitors a switch using GPIO.

However, I can not find the path to the GPIO "values".

The goal is that the monitored switch is wired to the car ignition.

Once the ignition is turned off the Pi should shut down after a few seconds.

Thanks.
[Raspberry Pi Original Development] ffcastro:
Hi,

I have problems with mx player and VLC and an external hard drive. With kodi, I have changed the file /data/system/packages.xml and add WRITE_MEDIA_STORAGE to kodi section, and in this way Kodi is able to access to the external drive. But it doesnt work with mx player nor VLC.

---------- Post added at 03:29 PM ---------- Previous post was at 02:41 PM ----------

I have changed in init.rc file the creation of /mnt/media_rw folder, increasing the permission to 0777; but my external drive is mounted with 0770 permisions (media_rw user and group) and it's impossible for VLC or MX Player to access it.
[Raspberry Pi Original Development] KonstaT:
Actually I already have a script that I wrote for this purpose and it does exactly what you're asking. I'm not sure if I want to spoil all the fun for you, though. ;)

See e.g. https://www.raspberrypi.org/forums/viewtopic.php?f=73&t=220613#p1404555 on how to access GPIO using sysfs. If you want to use a script you can place it inside /system/etc/init.d/ to be executed on boot (set permissions 755 to make your file executable).

This has been discussed on my site few times already and you can find related discussion on Kodi forums as well. Basically Android limits app access to certain directory on external storage unless you format your external storage device as adopted storage. Google also keeps changing how external storage devices are handled in pretty much every Android version so it's been a bit difficult for app developers to keep up as well (Android 11 has full access again? https://developer.android.com/training/data-storage#permissions).

There is nothing special in how this build handles external storage. Limited access is by a design so it's not a bug. App developers should keep up with API changes how external storage devices are accessed between different Android versions.
[Raspberry Pi Original Development] tb2668:
Awesome, thank you.

And yes, please spoil and provide your script. :D
[Raspberry Pi Original Development] KonstaT:
Here's a script that powers down the device when you connect GPIO pin to ground.

This is a TWRP flashable zip so you don't have to worry about permission or where to copy it.

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

It should be easy enough to edit if you want to change which GPIO pin you want to use or the delays.
[Raspberry Pi Original Development] tb2668:
Thank you!

The script works perfectly.
[Raspberry Pi Original Development] skoar:
Hey good work.

Sound wasn't working initially but I got it to work. Google remote keeps getting disconnected whenever I press a button. Everything else is great.

BTW prime video also doesn't work. It gets installed but I can't play anything. Has anyone else got it to work.

The only thing I waana know is if I can I boot it up from an usb since sd card is real slow.
[Raspberry Pi Original Development] KonstaT:
It would be worth pointing out that you're likely talking about the Android TV version (https://konstakang.com/devices/rpi4/LineageOS17.1-ATV/).

Google remote control app is known not to work. It's listed under issues.

There's been reports that video playback is not working with Amazon Prime Video. Most likely a decoding or a DRM issue but I'm yet to see proper logs (logcat?).

Booting from USB is possible but it's not 'supported' at the moment. Android 10 uses system-as-root which complicated this a bit. In addition to steps described in the LineageOS 16.0 FAQ to boot from USB you'd need to edit /vendor/etc/fstab.rpi4 as well (mmcblk0p* -> sda*). We'll see if there's some easier way to boot from USB if/when there's another release.
[Raspberry Pi Original Development] mandoras:
Root removal

Congrats KonstaT for the great job.

I have installed LineageOs 17 with AndroidTV 10 on my Raspeberry Pi 4 (4GB) and everything works smoothly. However I want to run an application which apparently detects the root access of the device and is blocked.

How can I "unroot" the device? I have found some su removal flashable zips online but they are applicable up to LineageOs 16 version.

Thanks again for your assistance and support:good:
[Raspberry Pi Original Development] srgrusso:
Thanks for the rom. I'm running your android tv version and liking it so far. I have the same issue with Amazon Prime and also have an issue with Youtube TV. I just ordered a usb A to A cable and will grab some logs as soon as I can.
[Raspberry Pi Original Development] KonstaT:
Official LineageOS 17.1 no longer has su (only adb root) so they don't provide option to remove it either. Did you try flashing the lineage-16.0 version (addonsu-remove-16.0-arm-signed.zip)?

This build has a kernel side patch that hides su binary when root access is not enabled in the settings. I'm not sure if removing the su binary is going to make any difference. Many secure apps (banking, protected video content, etc) check the status of Google's SafetyNet API which this device doesn't pass or run other checks to decide whether your device is to be 'trusted'.

You can't use the regular USB ports on the Pi for Android debugging (host mode only). ADB is only supported over network (wifi or ethernet).

Youtube TV was already discussed and it's not working due to Widevine L1 not being available on this device.
[Raspberry Pi Original Development] mandoras:
No I haven't tried flashing the addonsu-remove-16.0-arm-signed.zip. I will give it a try.

I have tried disabling the root access in the settings, uninstall and re install the app but still same problem comes up. The app is indeed a cable TV application. Apart from flashing the su remove for lineageos 16, is there any other trick of "bypassing" the root check of the provider?

Thanx once more for your continuous support.
[Raspberry Pi Original Development] risant:
Is it possible to playback video in 4k 60 hz i android 10 lineage 17,1 without any lag using software encoding and decoding since hardware acceleration is not possible
[Raspberry Pi Original Development] risant:
When they are going to fix hardware video decoding and encoding?
[Raspberry Pi Original Development] KonstaT:
Maximum supported display resolution is currently 1080p so much better question is why would you even need to play 4k video?

Yes, AFAICT Google's H.265/H.264 software decoders support resolutions up to 4k. This build plays H.264 1080p video with software decoder just fine without any issue.

Here is the full list of hardware video decoders/encoders that are even theoretically possible on the Pi 4 so you can consider what you're missing:

-H.265 (4kp60 decode)

-H.264 (1080p60 decode, 1080p30 encode)

Ah, the mysterious they. Have you asked them?

Answer is still most likely when it's ready. It might take an Android version or few but I'm pretty sure we'll get there eventually. I think Google already provided some code for the V4L2 codecs and I believe that's what many different types of devices are going to utilize in the future.
[Raspberry Pi Original Development] KonstaT:
I highly doubt removing su is going to make any difference because there's likely other checks in place. It shouldn't make a difference vs. root access disabled from settings and su binary hidden.

Magisk is known to spoof all kinds of SafetyNet and security checks but there's been problems getting it running because boot partition structure on Pi is not like you find on Android devices.

You can also do what the su removal zip does from terminal:

su
mount -o rw,remount /
rm /system/bin/su
rm /system/etc/init/superuser.rc
rm /system/xbin/su

Ironically you need root to do this. ;)
[Raspberry Pi Original Development] srgrusso:
I assume there is no workaround for widevine like using a browser hack?
[Raspberry Pi Original Development] KonstaT:
No, I'm not aware of any "browser hack" whatever that means. Widevide L1 on Android requires use of Trusted Execution Environment (TEE) which is not implemented on the Pi. Certification is also an issue. You don't have Widevide L1 even on many retail Android devices.
[Raspberry Pi Original Development] $u R Ya:
hi my pi4 keeps restarting at the searching for accessories screen
[Raspberry Pi Original Development] KonstaT:
It would be worth pointing out that you're likely talking about the Android TV version (https://konstakang.com/devices/rpi4/LineageOS17.1-ATV/).

You would need to be a lot more precise than that. It could be the same issue that's been already discussed (http://disq.us/p/2cxu3bn & https://github.com/lineage-rpi/android_kernel_brcm_rpi/issues/6) or it could be a separate issue. I'm yet to see any logs.
[Raspberry Pi Original Development] dmoreljr:
I flashed this rom on my rpi4 B and it's running near perfect. The only issue I'm having I cannot seem to find anyone else having the same issue. I tried installing a few games from google play and when I run them, they run fine but I have no keyboard or mouse input. Mouse works fine with apps but it seems to be an issue with games only. Any ideas?
[Raspberry Pi Original Development] KonstaT:
You would need to be much more precise than that. I highly doubt that's the case for everything that counts as a "game".

Android handles touchscreen input and mouse events differently. Mouses are not that commonly used with Android so many app/game developers likely haven't considered this. You can plug in a mouse/keyboard on most modern Android devices and see if your game behaves any differently.
[Raspberry Pi Original Development] $u R Ya:
is there or will there be support for hdmi cec
[Raspberry Pi Original Development] KonstaT:
No and there's no current plans for it. I don't have any hardware to test with.