yashsingh1/xdaforums huggingface dataset:
[Shield Android TV Android Development] I_did_it_just_tmrrow:
oh i didn't know that the microg developers explicitly excluded Android TV devices. That's a shame, because as soon as one of the big streaming apps requires Google services, it would be over with a Google-free Shield device.

EDIT:

I see LOS Unofficial build are still published there.

For example: lineage-15.1-20210113-UNOFFICIAL-microG-foster.zip
[Shield Android TV Android Development] Steel01:
It's not anything to do with the devices. It's that there's api differences between mobile gms and atv gms. Several of the core google services apps are completely different. And microg doesn't handle any of the atv specific stuff.
[Shield Android TV Android Development] Hodgdon:
Excuse my ignorance, but I'm having difficulty installing the LOS16 unofficial foster image onto my shield 2019.

I have bootloader unlocked and I fastboot booted into twrp, and had my LOS image on a USB drive. I performed the wipe within twrp, and then attempted to install the LOS image zip file...

But got an "improper zip file format" error.

So despite no OS installed on the device, I rebooted into fastboot mode, booted into twrp, and attempted to install the LOS16 image again...this time it appeared to complete the flash process...but when I tried to boot the device, it got stuck on the "NVIDIA" splash screen.

Unsure what I've done wrong; some help in getting this image to flash would be very helpful! Thanks in advance!

UPDATE:

Got it to work; and didn't have to change much. Here is what I did, hopefully it helps another amateur (like myself), and sorry if this is obnoxious to you techie types that are way more advanced than me...

I flashed the 8.1 developer image from Nvidia (don't know if this is required, but I soft bricked device and couldn't find the latest 8.2 image... later, I did find the newer image but it doesn't have the vbmeta_skip.img file that Steel01 mentions on page ~20). Don't forget to "fastboot flash vbmeta vbemta_skip.img" when flashing the development image.

Next, "fastboot boot twrp-3.4.0-0-20200926-UNOFFICIAL-foster.img" This will reboot device into twrp recovery

Next, I did a wipe: factory reset Then I did an advanced wipe of everything but internal storage and sd.

Next I went to "Advanced" and selected "ADB Sideload". This put device into adb mode where it is awaiting a command from PC to sideload a file to the device. I had the zipped lineage image in the same folder as my adb/fastboot platform tools folder, so I keyed in the command "adb sideload lineage-16.0-20200926-UNOFFICIAL-foster.zip" This sent the lineage image over to the device.

Next I went to "Install" and chose the lineage image. The device went through flashing process succesfully, and all I had to do was reboot into Lineage.

Hope that helps somebody else as clueless as me.
[Shield Android TV Android Development] Adromir:
Did you update the bootloader/firmware using an official zip before?
[Shield Android TV Android Development] Hodgdon:
I didn't, and I don't believe that was the problem.

I think source of my issue was either not properly wiping prior to LOS installation, or the way I had the LOS image stored prior to flash. As my update above indicates, I ADB sideloaded the LOS image to the device, immediately after wiping.
[Shield Android TV Android Development] Hodgdon:
Can anyone recommend a good youtube client APK that runs on LOS16 on the Shield TV?

Youtube apk runs fine, youtube works fine in the Bromite browser, but no version of Newpipe or Skytube that I tried worked. Both give a video playback error when trying to play videos.

Perhaps I'm doing something else wrong?

If it makes any diff, I don't have Gapps or MicroG - for me, the whole point of LOS is the ability to be google-free.
[Shield Android TV Android Development] I_did_it_just_tmrrow:
You should open a ticket if your newpipe does not work. I love NewPipe on my foster. It is not perfect (dpad is not 100% cool) but ad-free and google does not know a lot about free (useraccount-less subscriptions).

Issues · TeamNewPipe/NewPipe

A libre lightweight streaming front-end for Android. - Issues · TeamNewPipe/NewPipe

github.com
[Shield Android TV Android Development] mrhamed:
can you share more info about your experiences using LOS on NSTV-2019-Pro ? can you test official LOS15 with microG too and share your experiences please?

https://download.lineage.microg.org/foster/lineage-15.1-20210113-UNOFFICIAL-microG-foster.zip
[Shield Android TV Android Development] peestandingup:
Been running the last Official release on my Foster for some months great, but it rebooted out of the blue now is stuck on the Lineage splash screen. Anything I can try?
[Shield Android TV Android Development] peestandingup:
That says unofficial. I tried it with my 16gb 2017 model. Setup went fine, but would never display the home screen (just blank). I reflashed the last official nightly (15.1 from 2020) and that one works fine.

My model is still on the old bootloader & official twrp 3.2.3-0 if it matters.
[Shield Android TV Android Development] K-mart Shopper:
I am having issues getting this flashed to my new 2019 Pro model. I don't flash Android devices often so maybe I am missing something obvious.

When I try to flash lineage-16.0-20200926-UNOFFICIAL-foster or lineage-17.1-20200927-UNOFFICIAL-foster, TWRP installation fails because my box has bootloader 32.00.2019.50-t210-79558a05.

I tried installing the developer image for 8.1.0 and it has an older version bootloader but was failing with the same error (I do not have the version it loaded, but believe it started with 24.00.XX). I flashed a few versions in-between but still ran into this issue. Is there a specific stock image I need to be using for this to work?
[Shield Android TV Android Development] Don_Pachuco:
Why when clicking on the link to builds in post #1 does it say that there are no builds available?
[Shield Android TV Android Development] polar74:
Pag. 23 😎👍
[Shield Android TV Android Development] Don_Pachuco:
Thank you! So, just cuz I'm stupid, there's 3 different files from 04/08/2021 on the 15.1 build page. One is large, the other two small. Is one the ROM and the other 2 updates, or must I download all 3? Thanks in advance, if anyone can answer that.
[Shield Android TV Android Development] BenG7:
@Don_Pachuco: see below
[Shield Android TV Android Development] BenG7:
Hi

the rom is the largest zip file;

md5sum file extension

sha256sum file extension

(you should check the zip file authenticity...)
[Shield Android TV Android Development] eadmaster:
could this be ported to run on a Nvidia Jetson Nano? (similar SoC but much cheaper)
[Shield Android TV Android Development] Mogster2K:
Probably. It comes in 2GB and 4GB RAM versions and has half the Maxwell cores that the Shield does (128 vs 256.) I found a product name (porg) but I don't know which version it refers to.
[Shield Android TV Android Development] dfpp56:
I have a Nvidia Shield TV 2017, which is currently on Shield Android TV SW Version 8.2.1(32.8.435.31).

There is also a part in the "About" page that said "Version: 9".

Can I install the LineageOS Micro G build without bricking it like the guy on page 23 did? Are there any risks I would need to be aware of?
[Shield Android TV Android Development] FASAR:
Hi all! I have a P2897 nvidia shield.

Could not load any os on it,tried many versions.

I am able to acces fastboot, via an usb keyboard.

Question is: do i need twrp to install this lineage os?

If yes, how can i start twrp? I pushed the twrp.img, but what combo should i use on the keyboard/what steps should i do,to boot from twrp (cannot use adb, since i cannot enable dev options..no os)
[Shield Android TV Android Development] Neuken6969:
Hello all, I have a question. Currently I have the Nvidia shield tv (tube) just purchased it. I am using a few movie/tv apps and they both .... Stall. Screen goes black and I have to reboot the tube. I even reset it and damnit took nearly 3 hours. Model is P3430 Version 9 kernel is 4.9.140-tegra-g19e7acaac93b #4 build PPR1.180610.011.4079180_2740.7638 .... FINALLY my question is can I rom this beech and make it smoother??

Well seems like a dead thread BUT I did some research and I have an 8 gb tube android tv aka mdarcy. Anyone root and rom the tube??
[Shield Android TV Android Development] zionad:
Has any more progress been done on the 17.1 build? Since the most recent update to the shield, alot of us are looking to de-google fast. Big flashings ads on the homescreen are not what I signed up for.
[Shield Android TV Android Development] Neuken6969:
Steel01, i see your a dev and thanks for your work. Do you know anything about the shield tv (tube) codenamed sif. I would love to root this device if possble.
[Shield Android TV Android Development] Big Dumb Object:
Fresh unofficial LineageOS 17.1 build from recently distinguished guys:

[URL removed: these builds are too raw still]
[Shield Android TV Android Development] fxz:
Hi guys, I wanted to ask two questions.

A. Does this have a TV interface? Like easy to use with the official trianglular TV remote?

B. Is widevine still L1 after flashing / unlocking? Netflix 4k etc needed.
[Shield Android TV Android Development] KeepingItCuttingEdge:
Are both nVidia Shield TVs (2019 & 2015) "foster" -- the 2019 Pro version and the 2019 cylinder?

I know they have the same hardware other than RAM and a "+" Tegra chip in the 2019.

THANKS
[Shield Android TV Android Development] Mogster2K:
Foster only refers to the original 2015 model. I'm not sure what the codenames are for the 2019 models.
[Shield Android TV Android Development] BenG7:
Hi

Is this unofficial for the nvidia shield / which models? Has this been tested by anyone yet?

@npjohnson & @Stricted: please where I can find the changelog / indications on what is working / what is not working?

Thanks
[Shield Android TV Android Development] npjohnson:
Not sure why you tagged Stricted - he has nothing to do with any of these devices.

These are development builds. Theres a reason I don't post links to them, they're all varying states of broken.

Don't share that link please, and there's no warranty/changelog/info, because again, they aren't ready.
[Shield Android TV Android Development] BenG7:
@npjohnson Thanks for your answers

I also tagged Stricted because, from the links provided by Big Dumb Object and the articles they took me to, I was under the impression both of you were responsible for these builds.

you are answering my questions: these are development builds.

I shall keep an eye on the board to see if any official build or working unofficial build eventually turns up :)

Thanks for your work
[Shield Android TV Android Development] npjohnson:
Stricted helped me on the Sabrina exploit - he isn't related to Tegra.
[Shield Android TV Android Development] Narpq:
the build download link does not seem to exist
[Shield Android TV Android Development] Steel01:
Well, for the first time in... close to three years, probably... The SHIELD Android TV has official builds running again. See the OP for links to the lineage download site. Foster builds for the 2015 and 2017 models ran yesterday. Mdarcy builds for the 2019 models won't run until next Tuesday unfortunately, but it is on the roster.
[Shield Android TV Android Development] dk1keith:
I really want to try this but I still can't make a TWRP Backup from my 2017 Shield Pro. Shield still doesn't recognize USB or SDCARD in TWRP....tried many things to get it to see usb or sdcard but have no idea why it still won't..ugghhh
[Shield Android TV Android Development] Steel01:
Neither do I. I looked at it some when I launched the last round of official twrp support and it was working for me. I'll try to take a look again, but I don't expect much.
[Shield Android TV Android Development] dk1keith:
Yeah you tried to help me out quite a bit on the TWRP thread. It was working for you but not for me. Thanks again btw.
[Shield Android TV Android Development] dk1keith:
Is the recovery image on the foster download page the TWRP recovery?
[Shield Android TV Android Development] Steel01:
No, that's lineage recovery. The lineage wiki instructions use that. For official support from lineage, only lineage recovery is supported. From a project perspective, it's impossible to support something not under your umbrella, which in this case is TWRP. I still support twrp and use it most of the time personally. But if you need to open a bug report on the lineage issue tracker related to recovery or inline updates, it needs to be with lineage recovery. Anything mentioning twrp will be closed as out of scope.
[Shield Android TV Android Development] dsa13dsa:
Hi all! Yesterday I installed the firmware lineage-17.1-20211021-nightly-foster-signed.zip, have you tried to install it? It worked fine for me, everything seems to be working, but I cannot find some items in the settings: there is no screen setting, there is also no item for the network settings of the storage. Does everyone have a crooked firmware or have it?

By the way, the recovery image lineage-17.1-20211021-recovery-foster.img is not working, if you decide to flash, put another lineage-17.1-20211014-recovery-foster.img
[Shield Android TV Android Development] mr.wrinw:
I installed lineage17 a few days back but it seems one USB port is set to USB debug mode only even if I deselect it in the developer menu.

So I can't use that USB port for my external hard disk. Another USB port for me must be used for a wireless keyboard.

Anyone has this issue or a way to fix this problem?
[Shield Android TV Android Development] dsa13dsa:
yes, my 1usb port does not work either
[Shield Android TV Android Development] Steel01:
I assume by "screen setting" you mean the display resolution, refresh rate, and colorspace settings. We do have the ability to access that, but the UI isn't atv friendly atm. And we don't have anyone with tegra hardware plus GUI programming capabilities atm. I can ask around, but dunno if we can get that sanely integrated or not. Do you have issues with the default settings? Autodetect should be sane for the vast majority of setups.

As for the samba server stuff... Yeah, I'm not touching that with a ten foot pole. What nvidia did there is a painful mess of modifications. If someone else wanted to do the work to pull it together, I'd review it, but I'm not doing it myself.

That's bad. When I've got hands back on devices, I'll test that. I don't know of anything that changed between last week and this, though.

I'd kinda hoped most people wouldn't care too much about leaving that port in device mode. I personally have adb connected perpetually. But then again, I'm not most people. It's on the todo/research list now.

Edit: Fwiw, usb hubs do work, but I know that's not the ideal solution.
[Shield Android TV Android Development] dsa13dsa:
Thanks for your work!

No, everything is fine with the default settings, I just thought the firmware might have gotten up incorrectly.

I also noticed such a problem with the remote control (hdmi cec is on): when the set-top box is turned on, the remote control does not work, but if you switch the TV to another xdmi port and then go back, it starts working normally.
[Shield Android TV Android Development] Steel01:
The bluetooth remote or a tv remote via hdmi-cec? I've had issues with the bluetooth remote taking a while to connect after boot even on stock. It might be worse on these Lineage builds, but I don't know of anything I can do to improve that. I've done very little testing of remotes over cec. I was honestly surprised it worked at all the one time I did test.

Googles support of cec has been... limited. Nvidia pretty much rewrote the cec stack on P. AOSP Q was... less bad? But still not good. I had to backport a fair amount from R just to get volume control working at all. I got a fancy avr and 7.1 setup semi-recently, so I made sure my setup works at least. Satv->avr->tv. Using one of the shield remotes, volume control handles the avr, pressing power turns off and on all three devices, etc. In theory, cec will work a lot better on R and S, but I'm not doing serious work on that until Nvidia officially releases R.
[Shield Android TV Android Development] dsa13dsa:
both remote control stops working even after 15 minutes of inactivity
[Shield Android TV Android Development] soljin:
I'm running into a weird error installing lineage-17.1-20211027-nightly-mdarcy-signed.zip. I am using twrp-3.5.2_9-0-mdarcy.img. I wiped the cache and do an adb side load and I get this error:

E3004: This package is for device: mdarcy,sif; this device is darcy.

I tried using the lineage recovery lineage-17.1-20211027-recovery-mdarcy.img but get all kinds of errors about partitions and when I try to activate adb the whole system freezes.

Am I trying to install the wrong version? Is mdarcy not darcy?
[Shield Android TV Android Development] Steel01:
@soljin Do you have a 2017 or 2019 device? darcy is the 2017 model, mdarcy is the 2019 one.
[Shield Android TV Android Development] soljin:
@Steel01 my model number in the menus is P2897 which I guess is the 2017 darcy. Is there no Lineage build for my model?
[Shield Android TV Android Development] Steel01:
Nvidia made things a bit difficult with the 2017/2019 emmc models. They're *both* p2897, but different sku's.

The 2017 darcy is supported by the foster Lineage builds. See the supported models section on the foster wiki entry:

Info about foster variants | LineageOS Wiki

wiki.lineageos.org
[Shield Android TV Android Development] soljin:
Ahh I see now. I'll go grab all the foster files and try again. Thank you very much.
[Shield Android TV Android Development] soljin:
@Steel01 Was able to complete the install but, doesn't seem to be starting. Just the start up logo animation for like 10+ minutes.

I rebooted into the bootloader and did a factory reset there (the slow one).

Used fastboot to push `twrp-3.5.2_9-0-foster.img` (the lineage recovery was erroring even with the foster image)

Booted into TWRP wiped data/factory reset (saw errors with mounting)

ADB side loaded `lineage-17.1-20211028-nightly-foster-signed.zip`

ADB side loaded `open_gapps-arm64-10.0-nano-20211029.zip`

Installed TWPR app

Rebooted

Should I not install the google apps right after?
[Shield Android TV Android Development] Steel01:
Wait a sec... It let you do that...? 0o It shouldn't have let you do that. Opengapps tvstock or tvmini is the atv gapps. Nano is for mobile/tablet and is not valid for atv installs.
[Shield Android TV Android Development] soljin:
Had to flash back to stock to un-break things. But once I had that sorted everything installed like a dream.
[Shield Android TV Android Development] KeepingItCuttingEdge:
To be 100% clear the cylindrical 2019 Shield TV is the mdarcy?
[Shield Android TV Android Development] Steel01:
No, the cylinder is sif, the larger 2019 model is mdarcy. Sif is technically supported in the mdarcy Lineage builds, but since there's no way to actually install it (even after tearing open the device and soldering down a usb header), it's not officially supported.
[Shield Android TV Android Development] FigliDiGP:
First of all, thanks to maintainers for their work. Very useful for us, you're not wasting your time.

Anyone know if is it possible to go back on the official stock rom if something going wrong ?

I have a foster pro model with the 8.2.1 image, based on Android 9 and LineageOS 17.1 is Android 10 if i am correct. Downgrading is possible ?
[Shield Android TV Android Development] mr.wrinw:
Downgrading is possible. Just use guidelines from Nivida's official website.
[Shield Android TV Android Development] FigliDiGP:
Those instructions ?
[Shield Android TV Android Development] Steel01:
foster_tab and mdarcy_tab builds are now available. Not linking those in the OP, but people that want them can find them easily enough.

These builds are not tested as much as the atv builds. They're also significantly less polished, cause... how do you polish a touch targeted ui for a device without touch? But enough people begged for tablet builds over my time here that I am releasing them.
[Shield Android TV Android Development] Adromir:
@Steel01 yesterday i installed the latest LineageOS Build for foster on my 2017 Shield. Can it be that the Shield Remote is Broken? I was able to pair it but then it just.. Didnt work at all so no Input was detected
[Shield Android TV Android Development] Steel01:
Which remote? At different points, I've tested jarvis (2015 remote, rechargeable variant), pepper (2017 remote, takes cr2032 batteries), and friday (2019 triangle remote). Been a bit since I've tested jarvis or pepper, but I don't see why they'd fail. I can specifically test again once I know which one.
[Shield Android TV Android Development] mr.wrinw:
Yes.
[Shield Android TV Android Development] Adromir:
SHould be pepper then, since it is the one with cr2032 batteries
[Shield Android TV Android Development] cHECKjAM:
Will any type of AI enhancer or special Dolby funcctions work with this lineage build?

I have both the 2017 pro and 2019 pro shields. Currently running on rooted 8.2, with "skip google login" trick.

I dont want any type of gapps in my devices at all, no amazon, no nvidia, no bull**** at all. Just a straight up media device running Kodi for local movies, and f-droid to get things like twire (for twitch), and newpipe (for youtube) . Will this lineage be good for me?
[Shield Android TV Android Development] Adromir:
@Steel01 i just went through the lineage repository for your builds. Am I assuming correctly that they use a prebuilt kernel? Because I can see nothing else than *.dts files on there
[Shield Android TV Android Development] Steel01:
The ai upscaling stuff is tied to the same security check that dolby vision is. Neither work with an unlocked bootloader. The dolby audio passthrough stuff works, though. I've got a fancy avr with atmos support and all that works fine in kodi and netflix. If you just want non-google media playback, this should work great.

GitHub - LineageOS/android_kernel_nvidia_linux-4.9_kernel_kernel-4.9

Contribute to LineageOS/android_kernel_nvidia_linux-4.9_kernel_kernel-4.9 development by creating an account on GitHub.

github.com

This is the main kernel repo. There's a few more that get pulled in, though. kernel/nvidia, kernel/nvpgpu, cypress-fmac, all the dt repos, etc, etc. It's kinda weird if you don't know what you're looking for, but the modularity nvidia was looking for does make sense to me. Even if the they only made it partway to that goal...

If you want to trace what repos are involved in a build, you can look at the lineage.dependencies file in a repo. Like, starting with android_device_nvidia_foster, you can that that among many others it depends on the kernel repo linked above. The that kernel repo itself has a deps file that pulls in all the dt repos and the out of tree module repos.
[Shield Android TV Android Development] Knuxyl:
I'm confused is this an Android TV build or just Android?

I remember seeing a lot of "atv" in the changelogs recently, is this android tv?
[Shield Android TV Android Development] Adromir:
This linked in Thread is Android TV
[Shield Android TV Android Development] Reigningfear:
Hello,

I flashed the foster_tab version of lineage from 11-10. It is mostly working great from what I have used it for thus far. 2 issues I've encountered which may be related are:

When using external storage and formatting it as internal storage, the Shield reboots and puts itself into a boot loop. This is fixed by simply removing the storage.

My internal storage is inaccessible. I am unable to download anything from web browsers and using multiple file explorers, I see nothing in internal storage.

I went as far back as 2018 in this thread and saw mention of my second bullet as a 'bug to be hunted down' but no mention since so I'm wondering if its just me? FWIW, I encountered the first bulleted issue on the ATV build dated 11-13.