yashsingh1/xdaforums huggingface dataset:
[Raspberry Pi Original Development] kakekeke:
How the ADB should be used in RPi enviroment? All the guides are for USB connection. adb connect rpi-ip:5555 results: "failed to connect to 'xx.x.x.xx:5555': Operation timed out"
[Raspberry Pi Original Development] KonstaT:
ADB over network works the same as any other device. You need to enable Android debugging on developer options of course. Connect your Pi and your computer to the same network by either wifi or ethernet. Run 'adb connect ip-address' on your computer (you can see the Pi's IP address e.g. on 'About tablet' screen in the settings).
[Raspberry Pi Original Development] pbanj:
just a question, not trying to nag. is the hardware decode not working because of a limitation or is it just something that needs to be worked on?
[Raspberry Pi Original Development] KonstaT:
Raspberry Pi is not an Android device to begin with so there's no Android specific drivers for hardware video decoding/encoding. Plan forward is to utilize V4L2 M2M interface that is available on recent Linux kernels for video hw dec/enc. This has been previously discussed e.g. here (https://xdaforums.com/showpost.php?p=81930725&postcount=108).
[Raspberry Pi Original Development] pbanj:
Awesome, thank you for the info. I can't wait to replace my fire tvs lol
[Raspberry Pi Original Development] 3RMD:
I did it. Replaced my FireTv (Tank) with LineageOS with the RPi4 and Konstakangs 17.1 Android TV build using the FireTv remote. Everything works beautiful, mainly using NewPipe for YouTube and official Spotify TV client via Aurora store.

Only found one issue which I haven't resolved myself:

On the FireTv with Lineage build I used Kodi with Netflix addon (https://github.com/CastagnaIT/plugin.video.netflix) which worked flawlessly. On this RPi4 build only the first frame of the stream is displayed with working audio. Maybe this has something to do with HW acceleration? Already tried some Kodi settings regarding acceleration but nothing worked. Local videos in kodi are working.

Any suggestions?

Thanks for this great build. It's so much faster than those FireTv sticks...
[Raspberry Pi Original Development] Wednesday:
I'm thinking of running this with a hp/dell 24" touchscreen for a "smart display" with home assistant, but i have concerns about the multi touch function, anyone tried this with touch screens other than the standard 7i pi screen?
[Raspberry Pi Original Development] pbanj:
i rip all my movies from bluray to x265 so hardware decode is needed for smooth playback
[Raspberry Pi Original Development] KonstaT:
Native Netflix app is reported working. Video decoding performance depends on which video format is being used.

Official 7" touchscreen only works with SwiftShader software renderer because the KMS driver that is used for hw accelerated graphics doesn't support DSI connector.

Waveshare touchscreens that use HDMI for display and SPI for touch input work apart from some minor calibration issues.

There's been some mixed results with USB touchscreens. Some seem to work fine while there's been some issues with e.g. Waveshare touchscreens that use USB for touch input. I haven't received any reports with HP/Dell displays so I can't guarantee it will work out-of-the box. It shouldn't be too difficult to add support if it works with other Linux distros on the Pi.
[Raspberry Pi Original Development] Winderea:
Hello,

First of all congratulations for your great work, I'm currently working with your OS on my raspberry Pi.

But I'm encountering an issue concerning the free form option. Whenever I try to resize manually an activity, the OS crashes and reboots the pi, do you have any feedback on this issue ?

Thank you very much,

Best regards.
[Raspberry Pi Original Development] shoulih:
FireTv remote

Are you using FireTv remote app or FireTv remote that comes with FireTV stick to control LineageOS with the RPi4 and Konstakangs 17.1 Android TV build ?
[Raspberry Pi Original Development] peestandingup:
I've almost got it running perfectly. Only thing is I can't seem to browse any external hard drives. I can see they're attached under the storage menu, but no apps can access or see them. Some file explorer apps when I try to click on to list USB drives I get "this device does not appear to support the android storage access framework" (meaning the Pi).

Is there a trick to using external drives with the system, media players, etc?? Its the only thing holding me back.
[Raspberry Pi Original Development] Shabutie:
Running pretty well so far.

* Working

- 7" Official Display

- Wifi/Ethernet

- 3.5MM audio

I am having a slight issue when I open any app and let it run for a few minutes then try to switch to another application, the device will soft reboot. Is there any specific logging I can do or provide to do some additional troubleshooting?
[Raspberry Pi Original Development] 3RMD:
Thank's! Official Netflix app works well!

I'm using first generation FireTV remote (the small one, without microphone)

Another question:

Any option to change keyboard layout of connected USB-Keyboard? The other lineage build (not AndroidTV) has an option for this. Which config file deals with this?

Thanks!
[Raspberry Pi Original Development] risant:
My logcat
[Raspberry Pi Original Development] KonstaT:
Log from where doing what? Just dumping some logs without any information doesn't help. Please provide logs (dmesg, logcat) plugging in the device. Was this hardware working with some other OS on the Pi?
[Raspberry Pi Original Development] Wednesday:
Great build, however i have some troubles with wifi, it connects and then it disconnect, anyone had any wifi issues?

I'm starting to think it might have something to do with heat because the chip gets very hot, thougts?
[Raspberry Pi Original Development] KonstaT:
Wifi on Pi 4 seems to be pretty sensitive and it easily affects network performance if you're using e.g. a very crowded wifi channel. Something like https://play.google.com/store/apps/details?id=abdelrahman.wifianalyzerpro is pretty handy figuring out if your network is on the same as channel as some neighboring network.
[Raspberry Pi Original Development] Wednesday:
Inreresting, i will give it a shot.

I also disovered that it might have someting to do with my other rpi, because when both are connected both are acting up,very strange because the other one is running raspian and they have different Mac addresses and hostnames.
[Raspberry Pi Original Development] zLeqitEclipse:
Hello, i hope this thread is still active because i have a problem.

When i try to connect my fire tv remote to my Raspberry (On the Stock Android ROM without GApps) it works fine.

But after flashing the GApps it always says something like "Paring failed"

Does anybody knows how to fix that because i really want to use my Fire Remote but i also want the GApps.

Thanks.
[Raspberry Pi Original Development] KonstaT:
TBH, I have no idea why installing gapps would have any effect on bluetooth pairing. There's an open issue of this on OpenGapps issue tracker (https://github.com/opengapps/opengapps/issues/915) where you can post the appropriate logs (logcat).

There's also other gapps alternatives you can try.
[Raspberry Pi Original Development] chewy74:
Nevermind
[Raspberry Pi Original Development] oOHiggsOo:
Hello,

I have the RemotePi Board for Pi 4. You write one should "You can place a keymap for your remote as / boot / rc_keymap to be automatically loaded on boot (see available keymaps for reference)." Where can I find / boot? I mounted the SD card in Ubuntu and added the file to no avail.

Furthermore you write "Android doesn't have user accounts with passwords so key based authentication is used with SSH instead. Necessary keys are generated on the first boot and you need to pull the private key to your computer" where I can find the SSH key ?
[Raspberry Pi Original Development] ZionX50:
Does it support UEFI and ACPI??
[Raspberry Pi Original Development] KonstaT:
Boot is the first partition on the image/sdcard. Yes, you can mount it in Linux (or even Windows as it's FAT partition).

/data/ssh/ssh_host_rsa_key as stated in the FAQ.

Does any OS on the Pi? I haven't done anything to support it at least.
[Raspberry Pi Original Development] charliemopps:
I've got this mostly working but I only seem to have specific issues with Youtube. Youtube voice search is missing, and Youtube 1080p@60 will play a few frames and then the video just freezes but the audio keeps playing. 1080p@60 works in other applications just fine. If I change the playback to 720p@60 in youtube, playback works as expected. Has anyone else run into either of these issues?
[Raspberry Pi Original Development] KonstaT:
1080p30 videos work fine without any dropped frames. Software video decoder can't quite keep up with 1080p60.
[Raspberry Pi Original Development] charliemopps:
I don't have 1080p30 as an option in Youtube. I've tried setting the raspberrypi settings themselves to 1080@30, and this does take, my TV switches over to 30... and I would prefer this, I hate high refresh rates in moves and such... but I'm given no option for that in youtube and as soon as I open youtube it switches back to 60 when I open a 1080p video. Is there any way to absolutely disable 60hz permanently system wide? I do not want it at all.
[Raspberry Pi Original Development] KonstaT:
In YouTube regular 1080p option is at 30Hz.

Display refresh rate and video frame rate are two different things.
[Raspberry Pi Original Development] charliemopps:
Yea, I don't have a "Regular 1080p" option.

My options are:

1080p60

720p60

480p

360p

240p

144p

What I have installed is:

open_gapps-arm-10.0-tvstock-20210910

One thing I've noticed is that after install, I do not have gboard installed, or Google speech services. So I can't type anywhere. I have to install both just to be able to use the remote to type into anything. Even then, the voice search wont work at all, I get "Not found Speech recognizer" and nothing seems to fix it but installing the Google assistant application. But this doesn't restore voice search to Youtube. I'm not sure if this is normal or at all related. :-/ I'm untinstalled and reinstalled a dozen times with different versions of open gapps, as well as with Android 11 and get the same result every time. My only option for 1080p content is @60, and the video just freezes. If I go down to 720 it'll play. If the video is in 1080p30, it'll play just fine. But if it's in 1080p60, there is no option for 1080p30 and I can only watch it in 720p60. It's weird.
[Raspberry Pi Original Development] stason.s7:
I've installed this build on my RPi +5" non-hdmi display. It works with Swiftshader, but sometimes experiencing little freezes for a split second. BTW, raspberry heats up pretty much in passive cooling shell. I even had reboot due to overheating. (meanwhile I've experienced no temperature issues with no even passive cooling in Raspbian, while compiling 1 thing with latest firmware).

Anyway, I've installed gapps pico from TWRP like in your guide and successfully logined to my google account and play market. Noticed that I'm unable to switch to portrait mode (1 game, that always automatically runs in portrait mode, runs now in center of landscape mode with 2/3 of unused black screen). Is there any workaround?

In the rest, the game is completely playable.
[Raspberry Pi Original Development] KonstaT:
This build forces the orientation so it doesn't rotate (add/uncomment 'config.override_forced_orient=true' to /system/build.prop to change this). Or you can rotate the whole UI from Settings -> Device Preferences -> Raspberry Pi settings -> Display rotation.
[Raspberry Pi Original Development] stason.s7:
It worked for main UI and I performed reboot to correctly rotate the desktop with wallpaper too. (Correct reboot via holding F5 button and pressing there). And got infinite bootloop :(

Update: after editing build.prop, rotating and few automatic reboots, I've changed to 270degrees, it rebooted and nothing happened; I've rotated to 90. The home screen is still in landscape mode and game and few other apps run in portrait mode (as it intended to be). Good.
[Raspberry Pi Original Development] locness3:
Hi, thanks to everyone involved in this build for their amazing work.

Now, I'd like to install NanoDroid and specifically its patcher script to add signature spoofing support and install microG. I have attached the particular zip file. When I try to install it in TWRP, it just fails with `failed to mount /system (unsupported A/B device?)`.

I tried disabling the option to unmount system before installing zips, mounting it then installing the zip but the script seems to try to mount it anyways. I assume this a problem with the partitioning scheme? What could I do to get the install to work? Thanks in advance to anyone who might help me with this.
[Raspberry Pi Original Development] KonstaT:
This build is discontinued and you should use the latest LineageOS 18 images instead (https://xdaforums.com/t/dev-rom-unofficial-lineageos-18-1-android-11-for-raspberry-pi-4-b.4212945/).

Without further looking into I can't say why it would fail. There is nothing non-standard about system partition on this device (only boot partition is different from regular Android devices) so it shouldn't fail if the installer is done properly.

Would this be something that can be done with Magisk? I just recently added a Magisk patcher for my builds so you can use that now.
[Raspberry Pi Original Development] locness3:
> This build is discontinued and you should use the latest LineageOS 18 images instead

They're not stable enough for me.

> Would this be something that can be done with Magisk?

I think it can.

I'll stay with degoogled los17. Thanks for your response.
[Raspberry Pi Original Development] KonstaT:
Care to specify what exactly makes them "not stable enough"? Difference in kernel is just one line in configuration. All the graphics drivers are much newer/better in later versions. I can't see any reason not to update which is why there's also no point in keeping this version maintained. Basically you're just missing out on all the latest features and updates by using an almost a year old build but your choice of course.

There never was any Google services included to begin with so you can't remove anything (and Android being Google OS you can't escape that in any case).
[Raspberry Pi Original Development] locness3:
That's what I'm saying.

> Care to specify what exactly makes them "not stable enough"?

Some small problems around, like the scrolling text in the quick settings slowing down everything (maybe this only happens with the french locale), or some crashes with video playback in certain cases - I wasn't aware that the los17 build wasn't updated anymore, so I'll consider making detailed bug reports for the newer builds.
[Raspberry Pi Original Development] locness3:
It seems like most of my issues with the los18 builds are gone since the last time I tried (aside from quick settings), thank you. I appreciate it being 64-bit now too :p
[Raspberry Pi Original Development] lesleylemmens:
Hi, i changed config.txt to 03 but somehow it is not working, any suggestions?
[Raspberry Pi Original Development] lesleylemmens:
Hi, i did change config.txt to 03 but it is not working. Any suggestions?
[Raspberry Pi Original Development] KonstaT:
This build is seriously outdated and has been discontinued for over two years. Please use the latest Android 12/13 builds instead.

Also probably already elsewhere.

LineageOS 18.1 (Android 11)

for Raspberry Pi 4

disq.us
[Raspberry Pi Original Development] eagledipesh:
Hello Dev, would it possible to create a generic script (Should independently work on various platforms AMLOGIC,, ARM etc...) to covert Normal ROM to ATV ROM.
[Raspberry Pi Original Development] shoulih:
I assumed that is a bluetooth remote. How did you pair it with the Rpi4 running Konstakangs 17.1 ?
[Raspberry Pi Original Development] 3RMD:
Yes, it is a bluetooth remote.

Navigate to Settings --> Remote & Accessories --> Add accessory

Long press HomeButton on FireTV Remote

FireTV Remote added
[Raspberry Pi Original Development] shoulih:
Can't seem to get my amazon echo voice remote paired for some reason.
[Raspberry Pi Original Development] 3RMD:
I think this kind of remotes are using Wi-Fi....
[Raspberry Pi Original Development] velopl:
Hi

I have 7" model and touch is all over the place on Waveshare. You say there is a minor calibration issue. Please would you be able to tell me how can I fix it?

swapxy=1 doesn't really seem to work (my touch input is inverted)
[Raspberry Pi Original Development] KonstaT:
External USB storage devices work fine AFAIK. If you are talking about the Android TV build see http://disq.us/p/2bdq066.

Have you changed /boot/resolution.txt to match the resolution of your display? Have you uncommented line in /boot/config.txt under 'Waveshare touchscreen' to enable the touchscreen driver? What other modifications have you made?
[Raspberry Pi Original Development] velopl:
I have changed resolution.txt to 1024x600

my config.txt looks as this

# Kernel
kernel=zImage

# Ramdisk
gpio=21=ip,pu
[gpio21=1]
initramfs ramdisk.img followkernel
[gpio21=0]
initramfs ramdisk-recovery.img followkernel
[all]

# Audio
dtparam=audio=on
hdmi_force_edid_audio=1

# Audio DAC
#dtoverlay=hifiberry-dacplus

# Camera
gpu_mem=128
start_x=1

# Display
hdmi_force_hotplug=1
hdmi_drive=2
max_usb_current=1
hdmi_group=2
hdmi_mode=87
hdmi_cvt 1024 600 60 6 0 0 0
disable_overscan=1

# Graphics acceleration
[gpio21=1]
dtoverlay=vc4-kms-v3d-pi4,noaudio
[all]

# I2C
dtparam=i2c_arm=on

# I2S
#dtparam=i2s=on

# IR
#dtoverlay=gpio-ir,gpio_pin=18

# Keys
#dtoverlay=gpio-key,gpio=21,keycode=116,label="POWER"

# RPI display/touchscreen
dtoverlay=rpi-backlight
dtoverlay=rpi-ft5406

# RTC
#dtoverlay=i2c-rtc,ds3231

# Serial console
enable_uart=1

# SPI
dtparam=spi=on

# Waveshare touchscreen
dtoverlay=ads7846,cs=1,penirq=25,penirq_pull=2,speed=50000,keep_vref_on=0,swapxy=1,pmax=255,xohms=150,xmin=200,xmax=3900,ymin=200,ymax=3900

this is the model I have

https://www.waveshare.com/wiki/7inch_HDMI_LCD#Image

This is what I have at the moment

https://photos.app.goo.gl/2dADseAZ2kWPiMCF6
[Raspberry Pi Original Development] kbhuvi:
[MENTION=594001]konstant[/MENTION]

Good effort. Is it possible to mount a hdd on one usb and audio out through usb in your next build?

It will make rpi4 one hell of a music player.

Regards
[Raspberry Pi Original Development] KonstaT:
But why have you enabled swapxy if that's exactly the problem? Just test by uncommenting the original line under 'Waveshare touchscreen' section.

You can already do that with the current build.
[Raspberry Pi Original Development] velopl:
This is exactly what I said I did in my first post. With swapxy=0 was wrong so I've changed to swapxy=1 and it did NOTHING

Changing between 0 and 1 has no effect whatsoever

swapxy=0

https://photos.app.goo.gl/CtM7Ltig6cZRPG2d6
[Raspberry Pi Original Development] KonstaT:
According to this (https://github.com/waveshare/LCD-show/blob/master/boot/config-7-1024x600.txt#L61) uncommenting the line under 'Waveshare touchscreen' is correct for your display.

Have you tested it with no additional modifications to config.txt (just uncomment the line for touchscreen driver and change /boot/resolution.txt)? Have you tested this with LineageOS 16.0 build or using SwiftShader with this build?

I don't have any of these Waveshare displays I could test with.
[Raspberry Pi Original Development] RaghavTeck:
i have tried a lot but i cant get any android build to boot. tv builds keep crashing on bluetooth setup screen normal builds crash on setup. hdmi 0 works only on v16 but not works on v17. please help me as im really looking to using this with my TV

raspberry pi 4b 16gb c10 sd card
[Raspberry Pi Original Development] peestandingup:
Thank you. I nuked the build, but will try the external drive fix on the next flash. Yeah, it was the Android TV version.

BTW, you mentioned changing resolutions. Does it some way support 3840x2160 (my TV's native res) while keeping the UI at 1080p like the Shield & others do??
[Raspberry Pi Original Development] kakekeke:
Hey, how can i access the serial port on GPIO? I tried looking from /dev vut could not see anything relatable to serial.

Do i need to enable it somehow?
[Raspberry Pi Original Development] KonstaT:
/dev/ttyS0

https://www.raspberrypi.org/documentation/configuration/uart.md
[Raspberry Pi Original Development] trngw:
Hi

Really great work with this!!! :good:

How do I SSH into the RPI, I don't seem to get any connection, wired or WiFi?

I only have the 7" official touchscreen to use as a screen, and so need to SSH into the device to change to SwiftShader.

Thanks!
[Raspberry Pi Original Development] KonstaT:
It's best to use ADB which you can use over network (wifi or ethernet). There's also initial support for SSH but you'd still need to use ADB first to setup ssh keys, etc that it requires.

You need to have a HDMI display connected so you can enable root access and Android debugging in the settings that are required to make changes to the system.
[Raspberry Pi Original Development] trngw:
Wow, this is awesome!

My intention is to run Android on RPI4 with Navionics boat navigation app from Google store, using external GPS, and then maybe some extra features and apps and a large touch screen.

So, I am up and running, have installed google play and the Navionics app and charts (3 days trial for free to test) and so far things works fine. I haven't got any gps yet but saw that U-Blox 7 will work, and according to a quick google on that they are available with usb which is good because then I can fit the gps antenna in a good position.

Now, the whole idea with this is to use a large touch screen, because I need to be able to see it from some distance in the cockpit in my sailing boat. So I am looking at a 27" Acer, or if it was an Asus. Never mind. The thing is, it uses USB for the touch screen, and I wonder if that will work with the RPI and Android system? Will it work out of the box, will I need some special software, or will it not work at all. Or, if the last alternative, what would be needed to get it going. I understand the official 7" touchscreen will work if the graphics driver is changed for the display part. And that one uses I2C I believe. So I2C works, right, will USB touch screen work too? :fingers-crossed:

This is the screen I am thinking of using

Acer T272HLBMJJZ 27" FHD VA 16:9 10-Point Touchwin10

---------- Post added at 03:41 AM ---------- Previous post was at 02:42 AM ----------

Did you try this, how did it work out?
[Raspberry Pi Original Development] mickib1:
Hi

I have a question regaring burn the image to SD card; I used balenaEtcher or Win32DiskImager;

I have an SD card of 16G and after I burn the image it's re-arrange the SD so I shrank to 4G and when trying to install GAPP he said no space;

I tried to create a new pararion (10.6 Spare space) and faield; (Used Administraive tool in windows)

My question is how I burn the image and still have 10.6 Disk Spave
[Raspberry Pi Original Development] KonstaT:
Official 7" touchscreen works with SwiftShader. HDMI displays that use SPI for touch input (ADS7846 driver) should work as well.

Many USB touchscreens have been reported working just fine. There's been issues reported with at least ones that use eGalax driver which is not enabled at the moment (will probably enable support for more USB composite touchscreen drivers if/when there's another build).

Please read the FAQ. There's sections on both how to extend the data partition and how to install gapps.

Gapps are installed on the system partition so having unallocated space on the sdcard has no effect on that. There's few hundred megabytes of free space on the system partition which is more than plenty for most gapps variants (pico package still recommended).