yashsingh1/xdaforums huggingface dataset:
[Raspberry Pi Original Development] KonstaT:
Please stick with one medium when posting. I removed your comments from my site because I see you've made the same comment here as well. This is very hard to follow anyway.

You can boot directly to recovery by using a DIY hardware power button (see FAQ). No, you still can't boot to any 'safe mode'. Is that even a thing on AOSP Android? I've done a thing or two with Android but I've never booted to any safe mode.

Not sure what booting to some other OS or keyboard combinations have to do with Android. Just reflash the sdcard if nothing else helps. Always a good advice to keep your device backed up before doing experiments.
[Raspberry Pi Original Development] KonstaT:
If you want to test the actual composite output you can do it now with the new LineageOS 18.1 build (https://xdaforums.com/t/dev-rom-unofficial-lineageos-18-1-android-11-for-raspberry-pi-4-b.4212945/).

In /boot/config.txt you would need to have:

dtoverlay=vc4-kms-v3d-pi4,noaudio,composite

enable_tvout=1

Enabling enable_tvout=1 changes the clocks on Pi 4 which also seems to mess up serial console on UART so I'm not getting any logs. The composite connector is at least available after adding 'composite' parameter to dtoverlay=vc4-kms-v3d-pi4,noaudio.

I suppose composite output should work with KMS as well because they've given the option to enable it. There's bunch of Pi 4 KMS improvements in newer kernel versions, though.
[Raspberry Pi Original Development] cnico7:
Hi,

I use a custom keyboard with the rpi ( a wechip air mouse one) and the back key does not a back action while in the menus : it does nothing. I tested with a usb classic keyboard and the F2 key does a back action correctly.

As my wechip does not have a F2 key, do you know if it is possible to configure some sort of keymap in order to force one key of my wechip to do a back action ?

What are the tools to do this type of think on Android ?

Perhaps, there exist some custom keyboards that I could install, how ?

Thanks for your help,
[Raspberry Pi Original Development] imprezakd:
Hi，how to setting fixed IP on LAN ?

Thanks for your help
[Raspberry Pi Original Development] KonstaT:
You can edit /vendor/usr/keylayout/Generic.kl. E.g. these are the changes that were made to change the mappings on F-keys (https://github.com/lineage-rpi/andr...001-rpi3-modify-generic-keyboard-layout.patch). Correct way would be to add a separate specific keylayout file for that remote (https://source.android.com/devices/input/key-layout-files).

You would of course need to know what key event the back button on your remote send to edit the right key. You could use e.g. 'getevent' tool in command line for this.

I think Android TV has settings option for static IP for ethernet connection but the regular one doesn't.

Someone posted this (http://disq.us/p/2cev0c8 ) but I'm not sure if that actually works. I haven't looked into this myself.

Most routers let you assign IP addresses based on the device's MAC. That's at least what I've done for all the devices in my network.
[Raspberry Pi Original Development] foobar2605:
Hi, thanks for all the effort you have put into this.

I installed exactly as you mentioned. For the initial boot without the Gapps package all works fine. As soon as I install the Gapps the system boots up, I can see the remote control on the screen for a few seconds and then the device reboots.

Could this be a heating issue, because I recognized that the CPU gets quite hot?

Thanks,

Foo

-- Edit

I now started from a cool system and this is still happening. Now I even don't see the remote of Android TV any longer.
[Raspberry Pi Original Development] KonstaT:
Impossible to say without seeing any logs. General advice is to use a proper sdcard (class 10 at least) and power source (3A in case of Pi 4).

There's https://github.com/lineage-rpi/android_kernel_brcm_rpi/issues/6 but doesn't sound like that because gapps have nothing to do with that.
[Raspberry Pi Original Development] foobar2605:
Thanks for the quick reply. Seems like the power adapter wasn't strong enough. Thanks again for the hint!
[Raspberry Pi Original Development] Saftpresse99:
Hi,

is it possible to create a rpi3 android 11 build? I ask, because this problem: https://xdaforums.com/t/dev-rom-uno...raspberry-pi-4-b.4139059/page-4#post-83709215 seems to be fixed with android 11
[Raspberry Pi Original Development] KonstaT:
My plan has been to retire Pi 3 from development and only focus on Pi 4 moving forward. The hardware on the Pi 3 doesn't really meet the standards for modern Android devices. But yes, it would be possible and it would run Android 11 just as good/badly as previous Android version.

Also https://github.com/lineage-rpi/android_kernel_brcm_rpi/issues/6 seems to fixed in Android 11 so it would nice to have that on Pi 3 as well.
[Raspberry Pi Original Development] foobar2605:
Hi,

I'm experiencing 5.1 audio isn't working via HDMI. Tried with a libreelec build and it works there, but if I try Kodi on Android (or Emby or VLC...) I can only get stereo sound working.

I was playing around with the sound options and enabled / disabled some or all, but no effect.

Any idea what could be the reason? Any changes to the config.txt needed to get this working?

Best,

Foo

-- Edit

Also tried with LineageOS 16 release. Same result. It's always stereo output.
[Raspberry Pi Original Development] KonstaT:
There is no support for multi-channel audio output. I have no plans to support such feature either because it's really not that simple thing to do and II don't even have any hardware I could use to test.
[Raspberry Pi Original Development] Falcon_X:
I am thinking to buy a Raspberry Pi 4 and to try out "LineageOS 17.1 Android TV" or the Android build from this thread here.

Looking really good how far KonstaKANG got with this one on the Pi.

My only concern, as already mentioned in August by "pbanj": hardware decoding is needed for videos in x265 format(?)

Is this still the case or maybe in a newer build from november software decoding is strong enough to play x265 without stuttering?

Would someone be so kind to try this out in KODI with 1080p x265 mkv video files?
[Raspberry Pi Original Development] foobar2605:
Ok, thanks for clarifying.

Sad to hear, because the box is not really a good media station if surround sound is not available. My hope was that something from libreelec could be transferred to your build.

Apart from this your solution is perfect to make an old TV smart.
[Raspberry Pi Original Development] cem_ari:
My car setup almost done. I'm testing before install to car nowadays.

I need connect device with my phone in order to make phone call via bluetooth. Pairing is successful but can't connect them.

Is it a known problem? Or am i doing something wrong?

Edit: I have connected BT speaker without any problem. Is there any method about connect to Android phone for call?
[Raspberry Pi Original Development] KonstaT:
Android has a software decoder for H.265. Can't really comment on the performance with full HD videos because I'm not sure if I've even tested it. It would be nice to have some source for test clips that use different codecs that could be used for testing.

I'm honestly not sure if it's worth buying if media device usage is your only use case. There's also other more specialized operating systems for the Pi that might do that better. It's still nice to have Android as an option among various other things that are available for the Pi.

Android and LibreELEC are two completely different operating systems that share nothing (well, both use Linux kernel underneath but even that is very different).

We've come pretty far if things like missing surround sound is currently the main concern. :)

Sorry, don't quite understand what you're asking here. Can you generally connect two Android devices (phones/tablets) to make calls from the other?

I can pair my phone and send files via bluetooth between them (well, I recently tested this on LineageOS 18, but did on LineageOS 17 at some point as well). That's usually one of things I test at some point in development. I think there's something like 'Phone calls' option for some paired devices in the bluetooth settings so maybe try enabling that.
[Raspberry Pi Original Development] jaba_cz:
Another maybe stupid question. Is there way to put RPi into sleep? Or make graceful shutdown?
[Raspberry Pi Original Development] KonstaT:
Kernel on Raspberry Pi doesn't support suspend so it doesn't "sleep" like your regular Android device (it's also AC powered so it doesn't need to save power).

You can switch the display off/on by short pressing the power button. You can invoke the Android power menu to shutdown the device by long pressing the power button. Works exactly like on any Android device in general. FAQ has quite a lot of information related to this.
[Raspberry Pi Original Development] jaba_cz:
I know this. I have external circuit sending LOW to pin 21 a minute after turning off the ignition in the car.

I want graceful shutdown unattended. The power-off menu is not the solution.

Cutting the power directly sometimes makes data corrupt.
[Raspberry Pi Original Development] KonstaT:
And I'm supposed to know you know?

That's a completely different scenario and already discussed in this topic.

...
[Raspberry Pi Original Development] jaba_cz:
Thanks, will look into.
[Raspberry Pi Original Development] cremers100:
I've tried to install this today and I was really looking forward using this. But unfortunately I can't get passed the wifi screen when running the setup. Even with ethernet connected it asks me to set-up wifi. I tried disabling wifi in the boot.txt but no look either. I've searched this whole thread for answers already and even tried google. No luck.

Anyone that could help me out here?
[Raspberry Pi Original Development] sevenoverthree:
Hi there- I'm new to this device but so far things are off to a great start. I have Pinn OS running this and a few distros off of an ssd and I am just amazed at how well everything works. I happened to have bought a 15" USB touchscreen recently. I can't believe it works perfectly right on the first boot! This is the best tablet experience I have ever had! But to get to the point, I have a couple of quick questions:

1 Bluetooth seems to be working but I can't get a microphone to pick up. I have root, I've set permissions with the relevant apps, but so far nothing. Any suggestions? I've tried two different BT speaker/mics and behavior is the same.

2 I am planning to set up a USB GPS antenna in my car. Do I also need the rtc?

3 You probably get this question a lot, but I didn't see a clear answer- will hardware rendering come for this project? Is it just a matter of needing time to develop?

Thanks for this great OS. I will definitely be sending you a donation!
[Raspberry Pi Original Development] KonstaT:
Might be worth pointing out that you're probably talking about the Android TV build. Yes, it requires wifi during setup. I don't remember what's the setup like with gapps (e.g. if you boot directly to TWRP using DIY power button and install gapps before the first boot to Android). If https://github.com/lineage-rpi/android_kernel_brcm_rpi/issues/6 is the reason for not using wifi, I unfortunately don't have any solution for you with Android TV.

You can use the regular the LineageOS 17 build and set it up using ethernet. Or use the latest LineageOS 18 build which should no longer have https://github.com/lineage-rpi/android_kernel_brcm_rpi/issues/6.

1. Yep, bluetooth microphone is not working currently. It's on my list of things to look into with few other bluetooth related issues that have been reported.

2. Do you? If you plan to connect the Pi to network somehow it picks up the right time from time server. Actually I'm not sure what happens with calculating GPS position if your system time is not correct.

3. This build already has "hardware rendering" working i.e. hardware accelerated graphics. What is missing is hardware video decoding/encoding i.e. offloading dec/enc of e.g. h.264 video streams to the hardware.
[Raspberry Pi Original Development] cem_ari:
Hi.

I just want to connect RPI that working your ROM to my Android phone to make/get calls. Pairing process is OK but when i click connect looks connected for a few seconds then disconnects. I tried with two different Andorid phone.

Also there is only internet access and contact sharing options in RPI and phone both.
[Raspberry Pi Original Development] KonstaT:
Again impossible to say what could be the problem without seeing any logs. My phone stays paired just fine last time I tested.

I've never tried anything like this. Can you do this between those two other phones?
[Raspberry Pi Original Development] cem_ari:
Actually i started doubt it's possibility:unsure: Because two devices are same type. It's working with Windows pc and Android phone.

I know that some members are using your ROM in their car just like me. Can they share their experience about make/get phone call please? How can we get it work?

Edit: May be some third party app?

Edit2: RPI must has Bluetooth A2DP and headset service. I googled it and many people needs it. But no way.

I have an idea. Using a USB bluetooth dongle that has A2DP and headset service would fix the problem?
[Raspberry Pi Original Development] foobar2605:
Just another question for clarification:

Currently audio is only working if I connect the HDMI cable to the second port (not the one close to the power port).

Can this be changed by some config.txt modification so that audio is on first HDMI port?

Thanks in advance for your reply!
[Raspberry Pi Original Development] KonstaT:
That shouldn't be the case of course so something strange at your end. Make sure you're using the latest image. Also make sure you haven't made any modifications to /boot/config.txt that might affect this.

HDMI audio should work using both HDMI ports (HDMI:0 is the primary so I'd still recommend using it). I just fixed this a while back as it was previously only working with the primary port. All audio/video options are currently applied to both ports the same way. You can dig through the documentation (https://www.raspberrypi.org/documentation/configuration/config-txt/) if you find something but I'm not aware of any reason for this.
[Raspberry Pi Original Development] foobar2605:
You are right, just tested it once again and it works! Sorry for bothering you about this.
[Raspberry Pi Original Development] Bea de Val:
Question 1: Android TV 17.1 - HDMI Audio - Multichannel Support implemented ?

i've tried to use the Passtrough options to have 5.1 DTS / Dolby Digital Audio to my AV Receiver.

I have anytime only 2 channel Stereo Sound.

Is there an additional implementation in LineageOS needed ?. no changes to the config.txt

at this point.

Question 2: Amazon Prime Video didn't work.. Anytime... "Something went wrong" while trying to start streaming. It works fine with my other devices (Smartphones) with LineageOS 17.1

Question 3: Joyn APP shows only 2/3 page.. the rest is greyed in the bottom..

used build = lineage-17.1-20201121-UNOFFICIAL-KonstaKANG-rpi4-atv.zip
[Raspberry Pi Original Development] KonstaT:
If you read through the last couple of pages you'll find your questions 1 & 2 already answered.

As for question 3, sorry, never even heard of Joyn APP before. You would also need to be a lot specific in describing the issue.
[Raspberry Pi Original Development] elemental-prince:
Is there any way to remove the "Tablet is starting" text after boot?
[Raspberry Pi Original Development] KonstaT:
Why would you even need to?
[Raspberry Pi Original Development] elemental-prince:
Very minor really, but I'm using it as a kiosk to open a dedicated app, and the "Tablet is starting" text makes it feel like a generic tablet rather than a dedicated device. I thought I'd ask in case there was a config for it.
[Raspberry Pi Original Development] KonstaT:
May I kindly remind you that
[Raspberry Pi Original Development] tb2668:
Take a look at this.
[Raspberry Pi Original Development] KonstaT:
New builds (regular & Android TV).

LineageOS 17.1 (Android 10)

for Raspberry Pi 4

konstakang.com

LineageOS 17.1 Android TV (Android 10)

for Raspberry Pi 4

konstakang.com

-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)
[Raspberry Pi Original Development] vj4:
Just tried to flash this and it only boots into TWRP. Tried with SD and USB. Any ideas?
[Raspberry Pi Original Development] KonstaT:
If you've connected GPIO21 to ground (or there's something drawing power from it or you have a hardware failure) your device will always boot to TWRP.

Check /boot/config.txt. It should be easy enough to edit out the gpio21 logic.
[Raspberry Pi Original Development] d3viou5:
Hi All,

So when I use this with the Mesa driver, everything works very well. But I'm using an official raspberry pi 7 inch touchscreen with the swiftshader and all the apps I use that work fine with the Mesa driver, make the device do a soft reboot with swiftshader. Even basic apps like "PowerMenu" make it restart.

Anyone else experience this?

Edit: Lineage 16.0 doesn't have this issue so I'll stick with that for now.
[Raspberry Pi Original Development] KonstaT:
Yeah, there's some issues with SwiftShader. If you must use SwiftShader for some reason I'd recommend using LineageOS 16.0 build instead. It uses SwiftShader by default and it's much more stable there. Never really bothered to look into what's the problem with it in LineageOS 17.1 and I've already dropped it moving forward (LineageOS 18).
[Raspberry Pi Original Development] Raspberry pi fixer:
Hi what ever i do the rpi4 keeps rebooting after showing "System UI is not responding". i tried 40 times and also saw ur page so many times and even with suggestions like "change this ramdisk" and many it still didn't work. U should tell me the permanet fix so i dont need to buy a new rpi4. Plz help. also none of ur builds work and it boots still fine in other os. also dont ban again i will never spam. just tell a fix that works
[Raspberry Pi Original Development] Shijune:
Hi and thank you for your work. Is there HDMI CEC support in the ATV rom? I can't seem to find it. If not is there a way to enable it?
[Raspberry Pi Original Development] KonstaT:
General advice is to use a proper sdcard (class 10 at least) and power source (3A in case of Pi 4). Impossible to say what is exactly the problem without seeing any logs.

I haven't received any other reports with SystemUI freezing or reboots related to this ("System UI is not responding"). There's also this known issue related to wifi you might want to look into https://github.com/lineage-rpi/android_kernel_brcm_rpi/issues/6

I'm pretty sure I've repeated the above dozens of times on different platforms already so that information should be very easily available to you.

There is no support for HDMI-CEC. I don't have any TV/display I could test this with so I have no current plans for this feature.
[Raspberry Pi Original Development] Francesco.fdd5:
The problem is related to the mouse, if for example I check the raspberry via teamviewer or adb the problem disappears.

The problem also seems to be related to the frame that moves using the TAB in the keyboard, which appears only if you attach a mouse / keyboard
[Raspberry Pi Original Development] beppuz:
Did you solve this problem?
[Raspberry Pi Original Development] vj4:
I have tested the GPIO and it shows a fault on the pin 21 pullup. I amended the confix.txt to edit out the gpio logic and it still wont boot.

# Ramdisk

#gpio=21=ip,pu

#[gpio21=1]

initramfs ramdisk.img followkernel

#[gpio21=0]

#initramfs ramdisk-recovery.img followkernel

#[all]

I can load omni and raspberry Pi Desktop with no issues. I've tried on my 7" monitor and my TV (samsung). I get the rasp boot image then the rainbow screen then darkness and nothing happens if I leave it for 10 mins.

Any ideas?

Also tried

# Ramdisk

gpio=18=ip,pu

[gpio18=1]

initramfs ramdisk.img followkernel

[gpio18=0]

initramfs ramdisk-recovery.img followkernel

[all]

Tried it on an 256gb SSD, 128gb SD, 32gb sd and a 4gb sd
[Raspberry Pi Original Development] KonstaT:
That's not all of it. Please see 'Graphics acceleration' section as well.
[Raspberry Pi Original Development] TheKenz:
Have you tried pinch and zooming?

Blue Screen tint on Sky Go app

I have suddenly had a blue screen overlay as soon as I play a video on the app and cant remove it. If I hold the space bar it removes it while held. Any idea how to remove?

helpforum.sky.com
[Raspberry Pi Original Development] beppuz:
Thanks a lot for the tip
[Raspberry Pi Original Development] OdeMix:
Hello. I am trying to use my RPi4 with a 120GB SSD drive. Unfortunately, the script for resizing the disk partition does not work. I want to use an alternative extension method for the Data partition, but there is very little information in the FAQ. Could you describe this chapter in a little more detail?

"Alternative option is to use e.g. GParted and extend / data partition (/ dev / block / mmcblk0p4) to cover the unallocated space. Resizing the partition manually will break support for encrypting / data. Format / data in TWRP recovery (Wipe -> Format data) after resizing to leave required space for crypto footer. "

I increased the size of the userdada partition with GParted and then wiped it with TWRP. Unfortunately the system is not stable. I boot into the system and it reboots for a while.
[Raspberry Pi Original Development] MadJawa:
Hey! I am too using this build for a car project. Thank you for your work!

I was wondering how could I reduce the boot time to the minimum. I have a delay (~15/20 sec) before seeing the Lineage OS boot animation, is there some kind of bootloader delay I could reduce here?

Is there some stuff I could disable to speed up booting? I only need to run an app with an USB dongle (for CarPlay)

Thanks!
[Raspberry Pi Original Development] OdeMix:
[QUOTE = "MadJawa, message: 84462427, member: 11440743"]

... reduce the boot time to the minimum ....

[/ QUOTE]

I also use RPi4 for car radio. The total boot time, from turning on the ignition, until the system is ready for operation, is 15 seconds. You need to use USB 3.0 flash drive or SSD to improve startup speed.
[Raspberry Pi Original Development] MadJawa:
That's weird, I tried with a USB SSD, it's better but still slower than you. How much time do you have between turning the ignition and seeing the LineageOS boot animation?
[Raspberry Pi Original Development] OdeMix:
I can't answer now because my firmware died after trying to expand the userdata partition.

in any case, the USB flash will be faster than the SD card
[Raspberry Pi Original Development] KonstaT:
You would need to a bit more specific than "doesn't work". The resize.zip is the easiest way to resize the data partition. It points you to a log file if flashing it fails somehow.

There's really nothing too special about resizing using GParted either. You only need to format the data partition in TWRP if you plan to enable encryption at some point.

Either way this shouldn't affect stability in any way. It's impossible to say what could be the issue without seeing any logs. For any stability issues, general advice is to use proper sdcard (at least class 10) and power source (3A in case of Pi 4).

IIRC there was some report about delayed boot time after updating EEPROM. Latest EEPROM for stable channel should be fine (https://www.raspberrypi.org/documentation/hardware/raspberrypi/booteeprom.md).

I think I also have a delay of ~10 seconds before seeing boot animation when booting from sdcard. I think 15/20s total boottime is unrealistic even if you used an USB 3.0 device.