yashsingh1/xdaforums huggingface dataset:
[Shield Android TV Android Development] FigliDiGP:
It's right. Images was retired obviously. Maybe 19.0 is on our way :)

If you find files in another source, i can provide checksums.
[Shield Android TV Android Development] FigliDiGP:
Is someone find the way to have the game controller working wireless ? I can only use it with the wire.
[Shield Android TV Android Development] hugospacep:
Deleted
[Shield Android TV Android Development] anonymous-bot:
Try this page instead:

LineageOS Downloads

download.lineageos.org
[Shield Android TV Android Development] SgtBean0:
Thank you!
[Shield Android TV Android Development] Steel01:
Foster_tab is the tablet/mobile build, fwiw. Probably not what you want.

In other news, as of today, Lineage 18.1 releases are available. Of note, mdarcy builds have been merged with foster. Unfortunately that means upgrading from 17.1 to 18.1 on mdarcy will require wiping data. Upgrading from 17.1 to 18.1 on any other device can do an inline update.

Edit:

I should also mention that if you use the MTG option for gapps, it will not install the google ad launcher. So the play store and apps that require play services will be usable without ads being plastered all over the launcher.
[Shield Android TV Android Development] anonymous-bot:
Good catch. My mistake. Also I noticed the page for foster seem to be available again?

LineageOS Downloads

download.lineageos.org
[Shield Android TV Android Development] Danjel4u:
Good morning,

great praise to LineageOS have it also on my phone drauf. When I saw that there is an update to 18.1 for the Shield, I have played it immediately. And tried through I use for my channel list the APP Tivimate. Unfortunately, this no longer works stable, as soon as I have a TV picture in the background and am in the menu to search for another channel, the picture flickers every 3-5 seconds. As if an AFR would run and constantly adjust. AFR in Tivimate is off and also none installed.

Previous version reloaded there is all good. Does anyone have the same problem?
[Shield Android TV Android Development] Steel01:
@Danjel4u I don't have any subscriptions to test tivimate with. I have extensively tested kodi and smarttubenext with afr, though. I use them daily on my main avr/tv setup. And afr is the explicit and only reason I'm shipping 18.1 instead of 19.1. Because afr on S causes kodi and smarttubenext to hang. Can't even force disable afr support from the system to at least keep the builds stable.

Two questions, I suppose:

1) Can you reproduce this with any free app and video sources?

The only paid video subscription I have currently is Netflix, and that's only because Netflix is rediculously stupid with their drm protections, so when it works, it's virtually guarenteed that everything else drm related works.

2) Has this been tested on stock SHIELD Experience 9.x.x?

If it doesn't work with stock, it's unlikely I'll be able to make it work on Lineage. If it does work, then... #magic. Finding what the magic is could be troublesome, though.

A log from right after the issue occurs would be helpful too. Not as helpful as me being able to reproduce it locally, but it still might show something useful.
[Shield Android TV Android Development] PlutoDelic:
@Steel01 @Danjel4u

I can confirm no issues with Tivimate on 9.0.x stable, hotfixes, and the new eBeta's with 9.1.x.
[Shield Android TV Android Development] Danjel4u:
@Steel01 @PlutoDelic

Thank you for your feedback. I reinstalled the original Nvidia ROM 9.0.2 and it worked again. I'll stay with the original ROM for now
[Shield Android TV Android Development] Minth:
First, thanks for maintaining this ROM, awesome work!

I have an issue where Android cannot mount my external SSD, be it in ext4, exFAT or NTFS, the device in the "storage" settings stays on "disk is safely ejected".

If I format the drive via the Android TV itself, it'll force FAT32, which is not viable for my use (4Gb limit and all).

After checking out the logcat, it seems ext4 isn't supported/enabled on the device, isn't it built into the LOS kernel?

Logcat available below;

LOS logcat - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

pastebin.com
[Shield Android TV Android Development] Steel01:
@qane Exfat will never be supported on the shield devices on Lineage because Nvidia didn't license support. Ext4 and ntfs sdcard support is pending on Lineage 18.1. Those are not supported on Lineage device on 18.1 or 19.1 currently.

https://review.lineageos.org/q/topic:eleven-vold+branch:lineage-18.1
[Shield Android TV Android Development] YobDest:
Hello, thank you a million times for officially supporting the Shield TV. It really sucked in that period after ads on my home screen. You're a hero to me always, and I shall offer hecatombs to Hephaestus in your honor.

That being said, I understand that DocumentsUI doesn't come with the new image. Is there a way that either this, or another file-picker of some sort, can be shoe-horned in? As it is right now, many apps crash because they can't find a file picker.

EDIT: After using the new Lineage build a bit more, I've found a few small bugs and quirks, I'll just report them here.

1: Volume controls don't work, either with the shield controller or with my usb air-mouse keyboard. I don't see any way to adjust volume in android itself

2: HDMI CEC support doesn't seem to be available, so you have to manually turn on and turn off the TV.

3: More of a low-priority feature request than a bug, but there isn't any way to adjust the DPI for the home screen/launcher.

Otherwise, I gotta say, I love that this is available. Netflix and Crunchyroll seem to work. I'm running without any GAPPS, so it's possible some of the functions that aren't there are in the GAPPS package. Very happy with it so far!
[Shield Android TV Android Development] Steel01:
Alright, let me answer these separately.

DocumentsUI:

This is being discussed again. It's an atv platform issue, not a shield specific issue. By default Android TV does not have a docui impl. Like the adt3 or dynalink box don't ship it. The only implementation available is the phone/tablet version which requires touch or a mouse to use. Which... is not ideal for a controller driven 10 ft interface. I really don't like shipping an app that would require a user to pull out a mouse or connect to scrcpy to use it. If it was able to be installed as an addon, maybe, because then it would be user choice. Ideally, someone would write in leanback ui support, but unfortunately I don't have that skill.

Volume Control:

This is probably related to a bug I haven't been able to track down. And no one else has cared to investigate it. If you're not connected to cec and cec volume is enabled, then volume will work, but the popup will not show. If you go to settings->device->input and disable cec volume, then the popup will show.

CEC Power Control:

It does work. Normally. When it wants to... >< This is another bug I haven't been able to track down yet. Sometimes on reboot, cec will get into a broken state. If you go to settings->device->input and toggle the main cec setting off and back on, then power control will start working again.

Launcher DPI:

I'm curious the use case here. Google mandates that the Android TV ui be rendered at 1920x1080@320 for every version up to R. And even on S where the cts requirement is gone, google still forces the resolution and dpi on the adt-3. This affects all the java based ui's, which includes the launcher. Any native rendering (like a video or say the retroarch or kodi ui) will use the native resolution, however. Changing the dpi of the java ui does... weird stuff. If it's scaled properly, for example 3840x2160@640 or 1280x720@213, stuff works as expected, but changing the dpi to a different scaling factor like 1920x1080@240 causes rendering issues. It seems that there is font scaling options in the os, they're just not available in tvsettings. Thanks, google.
[Shield Android TV Android Development] YobDest:
DocumentsUI:

Understandable. A way to install it as an addon would be nice, I've tried random APKs from phones I have lying around and they didn't seem to fix the issue. I use an air mouse with the shield so even if it isn't 100 percent user-friendly, that's ok for my use case because I'm likely only doing something small and quick. You're right, a leanback option would be nice.

CEC Power Control:

Oh, ok, yeah that did fix it. :P

Volume Control:

Hooray! This works for me. I'm okay with hdmi cec not working if I have volume controls. It'd be great to have both but volume control is much more important, thank you for this work around. Good luck chasing down the bug.

Launcher DPI:

The use case here is simply that my screen is 1920x1080 on a 42 inch screen that's kinda far away. I can still see well enough to find stuff and select it, but I would like the option to make it larger. This isn't a super big deal, just a "nice to have" feature.

Thanks for the response, this helps out a lot.
[Shield Android TV Android Development] Steel01:
I should state that cec volume does work. My main daily driver setup is a mdarcy connected to a sony str-dn1080 connected to a samsung q90t. Having cec operational is very important for me. Changing volume using the shield remote does change volume on the avr. Pressing power on the remote turns off the avr and tv (and all back on).

Is cec volume not working on your setup? If so, did it work on stock? I know I've had some issues because the tv had cec input disabled by default. Also had settings on my avr cause headaches when it decided to change my speaker layout and kill stuff like truehd and atmos.
[Shield Android TV Android Development] YobDest:
To clarify, I was trying to use the software volume control, not HDMI CEC volume control. I don't know where my TV remote is.
[Shield Android TV Android Development] Steel01:
@YobDest

re DocsUI: Try the following addon zip. The concept is still in testing, but it worked in my preliminary tests. What I don't know is if it'll work without wiping data.

addon-docsui-18.1-signed.zip | by webgeek1234 for Generic Device/Other

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

www.androidfilehost.com

Note to anyone else finding this link: This is specifically for Lineage 18.1 official builds. The apk is platform signed, so it won't work on unofficial builds or any other rom.
[Shield Android TV Android Development] Kladderadatsch:
Thanks a lot @Steel01! Installed the addon zip and it works. I can now select a location for the games in Dolphin Emulator for example.
[Shield Android TV Android Development] YobDest:
Thank you! It works great. I see it definitely doesn't work with a controller or remote, but I have an air mouse so it works fantastic for me. Thank you for the speedy workaround, I really appreciate all the work you have put into this rom. If there's any information I can give you to make your life easier, let me know.

EDIT: OK system went haywire shortly after install, not sure exact cause. Seemed like the home app was just constantly crashing, re-crashing, over and over again. I formatted all images, re-installed the image, and re-installed the addon and it seems to be working again. No clue what caused it, could potentially be totally unrelated to the addon. Others would need to confirm.
[Shield Android TV Android Development] joed1ver:
Hello,

Lineage 18.1 is working great on my Shield_2017 except for one odd issue. I have installed it on more than one device, but they both end up with the same Wifi mac (00:90:4C:16:70:01) and the same Device mac (00:90:4C:11:22:33), neither or which are the original values. The ethernet mac and bluetooth mac retain their original values. I've re-flashed them both several times with the same results.

Is anyone else having this problem?

Thanks
[Shield Android TV Android Development] Steel01:
Blast, I fixed that once already. >< I'll try to have that re-fixed before the weekly build rolls next week.
[Shield Android TV Android Development] Sp4rkR4t:
Flashed this on an old SHIELD TV I found in the attic, checked it over beforehand and all was working fine but after I installed lineage a hardwired controller works but when I go to pair in bluetooth settings the controller is listed but nothing happens, if I plug it back in the pairing light goes off and I'm back to just hard wired. It's a darcy emmc box.

Anyone got any ideas?
[Shield Android TV Android Development] Steel01:
Which controller? Thunderstrike, the shield bluetooth game controller, should allow you to put it into pairing mode while plugged in. Unfortunately, my thunderstrike has a completely dead battery, so I can only use it while plugged in. Makes it difficult to test all that. Though, ideally you'd have an already working remote or controller to control the interface while pairing a different wireless controller.
[Shield Android TV Android Development] Steel01:
The mac address issue has been fixed, will be correct in the next official build.

Something to note: The wifi mac address displayed in settings->device->about->status is incorrect. This has been a problem since 17.1, if not earlier. It affects all Lineage devices, not only shield. Which is unfortunate, because when a real problem like was just reported shows up, you can't use tvsettings to verify. Running ifconfig via adb will show the mac address in use, fwiw. But that's not as easy to check.
[Shield Android TV Android Development] xdaborderpatrol:
Hi @Steel01 Thanks for all your hard work on this, I'm glad the Shield is still receiving LineageOS updates thanks to your efforts.

I've recently upgraded to the latest nightly on mdarcy and have been getting a few different issues out of which two I'd consider major:

Unable to wake from sleep. My Shield remote and my Harmony Remote are both unable to get the Shield up. Once it's sleeping for a while the only way to use it again is to unplug and reinsert the power cable. On the official remote, the lights on the remote don't even light up whilst the Shield is sleeping

Video playback - I've not had these issues before on Lineage 17 with extensive use so presumably it's ROM related but correct me if I'm wrong:

on NewPipe, on some videos if I try to go fullscreen the app just goes blackscreen for a bit and then I have to press BACK to go back to the small screen view

on Kodi playback the sound often goes out of sync or stops playing, though the video carries on

For now I'm reverting back to 17 but just thought to make you aware.
[Shield Android TV Android Development] Steel01:
@xdaborderpatrol

What is your mdarcy connected to? I have mine in a cec setup and have never seen sleep of death. Friday (the triangular remote that comes with mdarcy and sif) wakes stuff right up. No lights on that remote does indicate that bluetooth has disconnected, which certainly is bad. I've had other instability that I've yet to pin down (one of which might actually be a kodi bug), but this one is new.

I've never used newpipe, but that is one I can test. I've got smarttubenext installed and it works well.

I use kodi extensively and haven't had any desync. I'm using 19.4 with passthrough audio and framerate matching enabled. Do you have any special settings set? And is this with any and all content or something specific? If the latter, is there a video easily accessible online that I could pull to test with?
[Shield Android TV Android Development] xdaborderpatrol:
I've got everything connected to an AV Receiver - I've tried CEC enabled and disabled but no difference. I use a Logitech Harmony remote to control the Shield which is just treated as a bluetooth controller, but I keep the Shield remote handy as a backup. The Shield doesn't respond to either remote after a long sleep.

Don't worry about NewPipe, I've just had a look at SmartTubeNext and seems to be a better alternative that I wasn't aware of and I plan to switch to it.

On Kodi, I played with passthrough enabled and disabled, but the desync occured on both with no pattern that I could spot. The issue was obvious as I've never had anything like it in years on using the same setup. There wasn't anything special about the videos and I wouldn't be allowed to link to any of them on here.

I wouldn't want to send you on a wild goose chase. If you've any ideas or if there's any checks I can run, let me know but it might not be immediate as I'll have to upgrade and set it all up again. Maybe see if anyone reports something similar? For now I'm on 17.1.

I appreciate your efforts and trying to help out. It's great to see people still contributing to the ROM community.
[Shield Android TV Android Development] Steel01:
The sleep of death does worry me. I'd love to get a log out of that, like a "dmesg -w" running on adb as it dies. Would be good to know if the device outright died or if bt just disconnected. That would be easy to check with a wired controller or keyboard. To my knowledge, no one else has seen this, but history does say that most people don't report problems.

The kodi thing is weird too. I don't even know if there would be any viable logs for the issue. And the problem with development like this is that if I can't reproduce a problem, it's nigh impossible for me to try to fix it. Logs are a poor substitute, but it at least gives some insight.

So yeah, if you've got time later to do some more testing, I'd like to see some logs. Also, if anyone else sees issues like this, please report it. I've got my one cec dd setup and my test bench (monitor with a pile of devices on a switcher), that's unfortunately a very small test coverage.
[Shield Android TV Android Development] Kladderadatsch:
deleted
[Shield Android TV Android Development] zecabra:
Lineage 18.1 Tab version, crashes when using YouTube, it seems to be something related with the video and audio driver, because I can hear a loud clicking noise when the crash happens.

There is also a permanent warning in the notifications about the serial console being activated.

Video

Thanks for all the work that makes it possible for us to use this version in the Shield
[Shield Android TV Android Development] zecabra:
Today's version of Lineage Tab already lets YouTube videos play a few times but still keeps cracking other times, there is no slider to show the volume level, there is still some slowness in the system but you only notice it a few times, is on track to be a functional tab version for the first time in recent years, version 17.1 worked fine but had the problem of washed out colors that the option Disable HW overlays off did not solve.

Does anyone know how to configure static IP on network cable connection?

log:
[Shield Android TV Android Development] zecabra:
I think I did a poor job of explaining the problem with Youtube, it seems that it is not the audio or video that causes the crash, but the act of clicking the play pause or full screen buttons in the window.
[Shield Android TV Android Development] Steel01:
@zecabra : I'll re-iterate context first. I don't put a lot of work into the mobile builds for the satv, since it isn't something I'd ever use myself. About all I guarantee is that it boots and doesn't fry hardware. And that it passes all the Lineage charter requirements. If someone with more interest in the target wanted to do more thorough testing and submit fixes, the help would be welcome.

That said, I did do some poking around these reports.

1) Youtube 'crash'

I did reproduce what I think is your issue. It's not actually a crash, what's happening is the display is going to sleep and waking back up. I have no idea why, though.

2) Volume control popup

This is a known issue that affects the atv builds as well. HDMI CEC support detection is broken on 18.1. So when cec support is built in (which I do for both atv and mobile targets), the os always thinks cec is available. Hence, no volume popup. Additionally, there's no toggle for cec on mobile, so you can't turn it off except through adb. The following will tell the volume popup to show up then disable cec altogether.

settings put global hdmi_control_volume_control_enabled 0
settings put global hdmi_control_enabled 0

3) System lag

Is that intermittent or is it only on first boot or right after an update? Sometimes the app optimization that happens in the background can cause lag. That happened even on stock (it's really bad on the 500 gb model). But if it's not tied to app optimization, I dunno.

4) Ethernet static ip

That doesn't seem to be supported by aosp, not in the mobile ui. Could probably hack something up via adb, but that's beyond this threads support scope.

5) Serial console notification

Yeah, something needs done about that. It's telling the truth, but uart is supposed to be enabled on these targets. We'll do some research to see if it can be disabled.
[Shield Android TV Android Development] zecabra:
@Steel01 I'm available to help, just tell me what I have to do, is it enough to test the rom and share logs and problems, or is something else more needed?
[Shield Android TV Android Development] Steel01:
It's more on the development side. Testing is useful, but problems don't get fixed if someone isn't interested in making the fixes.
[Shield Android TV Android Development] Kladderadatsch:
Ext4 support will be included in next build.
[Shield Android TV Android Development] Steel01:
Wow, someone has eagle eyes. That was just merged yesterday. Yeah, ext4 and ntfs will be available on the next build.
[Shield Android TV Android Development] cHECKjAM:
I have a 2017 shield with unlocked bootloader. Have been running an older lineage 17.1 version on it previously.

Now looking to apply one of the new 18.1 builds but get stuck on nividia logga when trying to boot in to recovery.

Have tried flashing all 4 latest nightlies of the recovery.img found on the lineage download site.

fastboot flash command shows successful on pc within 2 secs and shield says "please wait" in red for 2 secs and then gone..

Im unsure whats wrong... thanks for help!
[Shield Android TV Android Development] Steel01:
@cHECKjAM It seems the wiki upgrade page is incorrect in this case. You need to use the 17.1 recovery to flash the 18.1 zip, which will upgrade the bootloader. After that, you need to flash the updated recovery.
[Shield Android TV Android Development] cHECKjAM:
Thank you. This worked and I was able to flash the new recovery. However when booting it starts with the lineage regular boot, the three dots finally coming together.

When it starts to search for bluetooth accessories for like 3 minutes. After that it moves to the lineage boot screen and then just gets stuck there.

I try to go back to recovery, factory reset and format data and cache, and then when I try to adb sideload the lineage nightly it gives me errors "failed to read 16777216 bytes data at offset xxxx: I/O error

then says "signature verification failed, install anyway?

when hitting yes it fails with "failed to find updare binary META-INF/com/google/android/update-binary

I tried nightly from 20220616 and 20220623 , same issue..

Thanks
[Shield Android TV Android Development] jmikepr:
Hey guys I have a few questions that I don't want to skim hours through 36 pages here and xda has a poor search function. There's also nothing on youtube in terms of walk through.

I'm thinking about picking up a 2019 shield and running this

1. How stable is it? General experience?

2. Without flashing Gapps how poor is the experience? I'd imagine you have to sideload most apps, but do apps like Netflix work with full support?

3. With G Apps flashed, does the Google TV remote work? What default launcher do you get? Do you get the one with the awful for you ads?

4..Full dolby vision, dolby atmos, 4k? etc support either way (gapps or no gapps?)