yashsingh1/xdaforums huggingface dataset:
[Shield Android TV Android Development] slutexpress:
So I just realized there are no more downloads for the 14.1 or 15.1 on Lineage OS website.

However I was able to find that LineageOS with MicroG still has builds: https://download.lineage.microg.org/foster/

Upon installation I'm getting stuck at the 'Checking for updates' and it just keeps swirling the download circle.

I cannot install MicroG LineageOS 15.1 due to my boot version (I was on Developer Rom 7.0.1 to be able to get TWRP to boot correctly) as I get error 7 in TWRP.

Then when I install MicroG LineageOS 14.1 installation goes through fine, and upon getting to the Setup Wizard I get stuck. I looked around on how to delete the SetupWraith.apk in /priv-app/ which worked great but I cannot access Developer Options.

Does anyone have any tips on how to proceed, and does anyone still have an old LineageOS 14.1 download?

EDIT::

So I went ahead and updated my 2015 Shield TV with Android 8.0 and now the bootloader shows 0.0.2018xxxxx and it does not downgrade when I go back to Android 7.0.1

Did I completely screw over my Shield TV? Is there a way to downgrade the bootloader when updating to newer Androids? I really wanted to just keep this on LineageOS and move on with my life, I like the simplicity LineageOS brings, and I only use a few apps on it.
[Shield Android TV Android Development] mrhamed:
I bought this: https://www.nvidia.com/en-gb/shield/shield-tv-pro/

Can I install TWRP and LOS16 on it? does your release compatible with it?
[Shield Android TV Android Development] K3rm1t4:
[MENTION=1416222]Steel01[/MENTION]:

Any chance that you'll find time to release a new experimental build soon?

Peaking at your repo activity it seems like you've been hard at work fixing and adding things the last couple of months ... for which I can't thank you enough :good:
[Shield Android TV Android Development] slutexpress:
Interested in seeing a new release too! Do you have any idea how to add a File Manager to the new Lineage 16 he released? I can't even get USB Debugging to work so I can't even push any APKs. Not sure how buggy it is for others, but I would love for this to be a daily driver.
[Shield Android TV Android Development] Mogster2K:
Sorry, AFAIK there is no way to go back after flashing 7.2 or higher. I killed my Shield trying.
[Shield Android TV Android Development] slutexpress:
Damn, I figured, it's crazy I actually had found a brand new, sealed Nvidia shield on ebay a few months ago, purchased it, and was having trouble getting TWRP to show up.

Fast forward to when I posted this I just had the motiviation to try again, got TWRP to show, flashed 14.1 and couldnt get past the setup wizard. I forgot that I shouldnt flash past 8.0 and I did.

So pissed at myself, it's just such a sketchy thing that these preloaded bloatware from Nvidia has a permanent bootloader upgrade. WTF

---------- Post added at 05:06 PM ---------- Previous post was at 05:04 PM ----------

My next device might be a ODROID N2 with 4GB Ram. The devs have a lineage ATV ready to go, and the performance of the board looks impressive. I just want something that cant be phased out, and it was nice that I could still use my old Nvidia Shield and still kicks most android tv boxes asses to this day.
[Shield Android TV Android Development] mrhamed:
[MENTION=1416222]Steel01[/MENTION]:

I've NVIDIA SHIELD TV PRO 2019, Can I safely install TWRP and LOS16 on it?
[Shield Android TV Android Development] ravenchalk:
lemme see

can you post screenshots?
[Shield Android TV Android Development] K3rm1t4:
Unfortunately, my device (Mdarcy, 2019 Pro) gets stuck in a loop after flashing this build:

LineageOS boots up, starts the search process for BT accessories and after about 60 seconds the progress bar just freezes and the device reboots itself without notice. In case the stock remote control pairing has succeeded in time (which doesn't always happen) or has been established already, I can navigate through the first few initial set-up menus but not past the "Date & Time" settings.

Has anybody experienced this issue before?

[MENTION=1416222]Steel01[/MENTION]: Do have any ideas or a different build to test?
[Shield Android TV Android Development] I_did_it_just_tmrrow:
[MENTION=1416222]Steel01[/MENTION] some little tiny tiny updates on this would be nice. Just to get sure we do not stop hoping :D

THX a ot for your work. I run your last PIE build since released and it is awesome! No google anymore.
[Shield Android TV Android Development] peestandingup:
Hey, guys. Its been a while since I've tinkered with my 2017 16gb (Darcy) Shield. Bootloader is still unlocked & its running the official Nougat (rooted) build.

Is there anything special I need to do to get this Lineage build going or things to be aware of? I assume I just need to at least update twrp to the official one (its running unofficial one now I believe), backup, wipe then flash??

I wasn't sure if remaining on nougat would have some adverse effect. Thanks!
[Shield Android TV Android Development] cHECKjAM:
Hey all..

I just bought a 2019 shield Pro. I love Lineage but this project looks dead? I mean scrolling back a few pages it seems that the developer is not answering to messages anymore or pushing updates since many months..

Are there any alternatives for us? I would love to run my shield google free either with lineage or being able to just bypass the requirement to login with google account, as I do not own a google account and can not even create a throwaway one because of sms requirements..

If anyone knows the status of this project please let me know..
[Shield Android TV Android Development] elliwigy:
you can always try to develop los on your own.. it seems you answered your own question.. it is what it is currently and what you already determined ?
[Shield Android TV Android Development] peestandingup:
Was anyone ever able to figure this out? The screensaver never auto triggers for me no matter what I do on 2017 16gb Darcy (last 15.1 official release).

Its more than cosmetic because if a screensaver never triggers, burn in will occur. I'm rooted so can try whatever. Thanks!
[Shield Android TV Android Development] Steel01:
re secreensaver: Did you go to settings -> screensaver and set the type and timeout? I think older builds had no timeout, so daydream never kicks in. New builds have the opposite problem, it defaults to 30 seconds which is far too fast. ><

re updated experimental builds: There's not really anything new atm. Minor adjustments as I continue work, but none of the remaining major issues has been fixed. Such as the gamma calibration problem that causes washed out colors on overlays. I did pull in the updates from stock 8.2, which may be worth a new 'release'. I'll try to look at a release build. I haven't done more than cursory tests on foster for a while. Have to run a basic set of tests before I'll upload something.
[Shield Android TV Android Development] peestandingup:
I did yes. It never triggers no matter the timing settings or screensaver choice. I even installed Aerial to see if that would kick in but never does. Coincidentally if I untick the "screen will never sleep while charging" option in dev options, the screen will go to sleep after the allotted screensaver time I give it. So the timing works, manually playing the screensaver in that screensaver options panel works, it just won't start on its own at rest. I'm not running any gapps btw, just the pure ROM.

I'm thinking of running some type of automation app to trigger a slideshow or something (so at least burn in won't occur) but I'm open to testing. Can always reflash if I bork something.
[Shield Android TV Android Development] peestandingup:
Ended up solving it using Macrodroid. For anyone curious, side load the app & give it usage access via the app settings menu & display over other apps access using the appropriate ADB command (this option isn't avail in the TV interface). Use a screen rotation app or else it'll be sideways. Use a mouse & set a new macro, giving it a timed interval of 15 minutes for the trigger (or whatever u want), activating daydream for the action & only when the launcher is in the foreground for the constraint (or else it would keep activating no matter what). Works well.

BTW, [MENTION=1416222]Steel01[/MENTION] Do you know of a way I can make the onscreen volume indicator display when changing volume (or at least what controls that in the root)? That's pretty much all I'm missing now.
[Shield Android TV Android Development] Steel01:
Finally decided to get around to running upload-able builds. Make sure to use the latest experimental twrp build available here. If desired, gapps are available via opengapps tvstock.

There are still a few known issues and notes:

Gamma problems. During hardware overlays like app launch, the leanback keyboard, or the volume indicator the colors will be washed out.

Make sure as soon as the device boots to launcher, after the setup wizard is complete, go to settings and set the screensaver options (select some type, typically backdrop, with sleep to never). Because:

If the device goes to sleep, like the display turns off, audio will die. At that point the only way to get it back is to reboot the device. I have a way to 'fix' that, but it's more involved than I'm comfortable merging to my kernel. Eventually I'll get to finding a better fix. But for now, just setting the screensaver to 'never sleep' works around the issue.

lineage-16.0-20200926-UNOFFICIAL-foster.zip

In other news, I'm throwing up a 17.1 build as well. This is very much a "beware of dragons" release, enter at your own risk. This has all the issues mentioned above plus a few I'm probably not even remembering atm. Decidedly less polished than P/16.0. But if you're really adventurous, you can poke around this. If you also want gapps, use opengapps tvmini. The webview in tvstock is causing issues right now. I did have netflix up and running on an mdarcy, so there's a fair chunk of stuff working right.

lineage-17.1-20200927-UNOFFICIAL-foster.zip
[Shield Android TV Android Development] cHECKjAM:
Hey dude, thanks or posting updates and showing life to this project.

I am sure Im not alone to say that we really would want more development in to lineageOS for Shield TV. And AFAIK you are the only active developer for this project. So if you dont do it then there are no alternatives for a google-free ShieldTV experience.

So I would kindly ask you to consider running a patreon, or other solution, and let us know some kind of donation goal for your time and effort to develop this project further. I am sure we are a few people here that would love to donate for this cause and solution..

Thanks

Oh and also.. Just a quick easy question, will the above (TWRP and LineageOS 16 build) work for the newest 2019 pro shield?
[Shield Android TV Android Development] mrhamed:
Does this LOS build and TWRP work for the newest 2019 pro 16GB shield?
[Shield Android TV Android Development] Steel01:
I already answered that... My builds support all commercial satv variants.
[Shield Android TV Android Development] I_did_it_just_tmrrow:
Awesome! I guess with the current android security patches...

I you had some time. I think it would be a good time update the first post of this thread. Not a lot people looking more into such an old thread.

Is there any chance to get an one-device-updater? Do you can provide monthly's? Getting regulary android security updates on a daily driven device would be awesome.

I would give some euro too, like mentioned by @cHECKjAM. I would prefer IBAN if you live within EU and otherwise Patreon or Librepay.
[Shield Android TV Android Development] PlutoDelic:
Great to see progress. Thanks a lot.
[Shield Android TV Android Development] TheUndertaker21:
You said this is working in 2019 too?
[Shield Android TV Android Development] Mogster2K:
Scroll up.

https://xdaforums.com/showpost.php?p=83598515&postcount=461
[Shield Android TV Android Development] TheUndertaker21:
I saw
[Shield Android TV Android Development] Adromir:
So why the question?
[Shield Android TV Android Development] Steel01:
re: donations. I'm not particularly interested in donations. The only time I even considered it was when I couldn't afford some of the new devices. Then nvidia sourced them to me directly. So I really have no need for it. At one point, someone gifted me ad-free here. That was appreciated. But in general, this is a spare time project I do for fun. Offers of cash or lack thereof isn't going to affect the amount of time I spend on it.
[Shield Android TV Android Development] cHECKjAM:
Maybe because it is very unclear for us newbies.. The post you refer to does not say "yes" or "no" but simply that it runs on all SATV something... No idea what that it is even..

At this point Im ready to pay someone bitcoins for help. I find nobody to talk to in my normal channels about this.. None on reddit or IRC ..

This forum is slow, very slow, to answer and most answers assumes you should know android programming yourself.

Again Im stating this and anyone who is capable is free to PM me:

I offer payment in bitcoin for anyone that can offer me help and information on my questions

They are this:

I have a older 2017 Pro device and a new 2019 device.

I want to run them without google. I have no google account even.

I want to be able to flash them with something that can either uninstall all google crap or run some kind of firewall like AFWALL. and yes I want to be able to login the first login without google account also, heard something about a developer version can allow this?

I have a Lineage phone and I love it. I have no google whatsoever on it. I use only Fdroid for my apps. And the few apps are like newpipe for youtube and twire for twitch, then jellyfin/kodi for movies and music.

If this is possible on the shield in any way I want to know and ready to pay for the knowledge!

On the 2019 version I want to be able to use the dolby vision features. So maybe its not the best to put this unmaintained lineage version on?

Please if you have time and knowledge PM me.
[Shield Android TV Android Development] Steel01:
It should also be pointed out that the builds I posted a few days ago are listed as EXPERIMENTAL. They're for people to test and report issues with. Not for daily driver usage. Those that need step by step wiki instructions are not the intended audience of those builds. Wait for officials to start releasing again.
[Shield Android TV Android Development] cHECKjAM:
I see.. Too bad..

With regards to how slow this project have been going I guess "official" builds are far far away...

Is there any reason why this is not a more popular thing? I mean Lineage for phones are super popular and maintained by several active developers.. Nvidia shield is really popular too but I guess its not as much as a single phone..?

Dont know what I could do to get this situation if I cant even pay for it.. Imagine a perfect lineage shield device just like a lineage phone.. ahhhhhh
[Shield Android TV Android Development] Steel01:
I'm working on it. Development is transitioning to Lineage 17.1. Some of the blocking issues that plaque 16.0 are not present on 17.1. But there may be other problems I don't know about yet. But I have to finish up 16.0 before things move forward. Main issue atm is sepolicy. I can't give any timelines. At any point, some problem may pop up that blocks everything. Or my day job or other things may take priority for a while. All I can say is that things are progressing and I'm trying to get official builds going again.
[Shield Android TV Android Development] elliwigy:
so u use same tree for 17.1 that u have for 16 that is linked in op for device tree?
[Shield Android TV Android Development] Steel01:
The last official Lineage build for foster was 15.1, actually. That's all that's on the github LineageOS org atm. The 16.0 trees are in the process of being merged on gerrit, to use as a baseline for 17.1. That's taking a fair amount of time. Once those are all merged, development focus will be on 17.1. Some stuff may show up on gerrit, but all my wip in progress stuff will show up on cm-shield.

Nothing on cm-shield is considered stable. I link it there a fair amount, but I don't give detailed instructions on how to use it. Someone familiar with android os development can use that to replicate my exact builds. Some people on the shield tablet side do that and support unofficial builds. I personally only support the official builds. But all the sources for everything I've ever done for android are available either on the Lineage gerrit or on cm-shield. Fwiw, I'm fairly Stallmanite when it come to source. I make available everything I possible can, and build everything I can from source (ala, the Fedora mantra).
[Shield Android TV Android Development] BenG7:
updated below (mods may delete this post - sorry for the mess)
[Shield Android TV Android Development] BenG7:
Hi

==> I take it I should not upgrade to any stock rom at this stage!

I have a Nvidia Shield Android TV Pro (500Gb) from 2015 (ro.product.device = foster / ro.product.name = full_foster_e).

I'm currently on full android Nougat and I just upgraded to the latest official TWRP, twrp-3.2.3-0-foster.img; I just tried flashing lineage-15.1-20200930-UNOFFICIAL-microG-foster and I got an error 7:

Warning: No file_contexts
This package supports bootloader(s): 24.00.2015.42-t210-39c6cadc, 24.00.2015.42-t210-4b5a7280, 24.00.2015.42-t210-9ad9891e; this device has bootloader unknown.
[COLOR="Red"]Updater process ended with ERROR: 7
Error installing zip file '/sdcard/lineageos/lineage-15.1-20200930-UNOFFICIAL-microG-foster.zip'[/COLOR]
updating partition details...
...done

My bootloader is reported as "unknown" which is normal as I cannot find a ro.bootloader entry in my build.prop.

I found my bootloader version to be "24.00.2015.42-t210-fcf112d9" (I found it at the top of the screen after rebooting to bootloader (adb reboot-bootloader).

Maybe I could just:

remove the asserts from the updater-script:

assert(getprop("ro.bootloader") == "24.00.2015.42-t210-39c6cadc" ||
getprop("ro.bootloader") == "24.00.2015.42-t210-4b5a7280" ||
getprop("ro.bootloader") == "24.00.2015.42-t210-9ad9891e" || abort("This package supports bootloader(s): 24.00.2015.42-t210-39c6cadc, 24.00.2015.42-t210-4b5a7280, 24.00.2015.42-t210-9ad9891e; this device has bootloader " + getprop("ro.bootloader") + "."););

Or alternatively, add my version of the bootloader to the assert

...
getprop("ro.bootloader") == "24.00.2015.42-t210-fcf112d9" || abort("This package supports bootloader(s): 24.00.2015.42-t210-39c6cadc, 24.00.2015.42-t210-4b5a7280, 24.00.2015.42-t210-9ad9891e, 24.00.2015.42-t210-fcf112d9; this device has bootloader " + getprop("ro.bootloader") + "."););

and update my build.prop with a ro.bootloader entry with value = "24.00.2015.42-t210-fcf112d9"?

How safe would that be? :eek::confused::eek:

Any other suggestions anyone please?

Do we have an historical list of the Shield's bootloader versions?

Thanks in advance
[Shield Android TV Android Development] peestandingup:
Is there a specific reason you don't continue work on 15.1? I'm running that last official release on my 2017 16gb Shield and its VERY close to being totally stable/bug-free. It pretty much is, just a few odds & ends already mentioned that needs cleaned up/fixed.

It would seem that would be easier & introducing 17.1 sounds like its gonna be quite an undertaking, which overall won't add much extra functionality & will break more things.
[Shield Android TV Android Development] Adromir:
Because it is a waste of time spending on a Rom (version) which is EOL?
[Shield Android TV Android Development] Mogster2K:
Not necessarily. However, if the stock ROM has been updated to 7.2 or later then LOS 15.1 will no longer boot. (I think. It's been a couple years since I worked with it.)
[Shield Android TV Android Development] Adromir:
Since Nougat, nvidia made quite a lot of changes to the bootloader and partitioning of the shield. So newest twrp won't work with this old builds
[Shield Android TV Android Development] peestandingup:
Sure. But the choice it would seem is old & stable, or new & broken. Neither is a good choice, but at least one of those is functional.

Plus I'd argue its a TV OS, basically only used for launching apps & a couple common bells & whistles inside of the OS itself. So the "newness" isn't the same as say with a phone. Am I really missing anything running 15.1 vs 17.1 in a basic TV environment?? I doubt it.
[Shield Android TV Android Development] Adromir:
But the changes overtime in the Shield had been pretty significant, plus app developers are also moving forward targeting newer Android versions. So why spend time in "bugfixing" an "abandoned" Android version, while you can spend bugfixing a recent android version and bringing that to a stable state?
[Shield Android TV Android Development] mrhamed:
Can anybody confirm: Does v17.1 works on NVIDIA SHIELD TV Pro 2019 16GB ?

Does it boot normally without change build.prop for each reboot on NVIDIA SHIELD TV Pro 2019 ?
[Shield Android TV Android Development] cHECKjAM:
I also Wanna know what the status is on newest Pro 2019 .. Really want to run lineage 17.1 on this..
[Shield Android TV Android Development] ericfav:
only have safe mode

I am able to run lineage-17.1-20200927-UNOFFICIAL-foster in SAFE MODE only.

In normal mode, I get black screen each time after the logo NVDIA

I tried older version and getting the same.

Does someone can provide an idea to fix this please?
[Shield Android TV Android Development] mrhamed:
Did you test on nstv 2019 pro?
[Shield Android TV Android Development] ericfav:
I have tested on Nvidia Shield 2017
[Shield Android TV Android Development] mrhamed:
Did you test another build "lineage-16.0-20200926-UNOFFICIAL-foster.zip" too? if yes, what about it?
[Shield Android TV Android Development] ericfav:
2 weeks ago, I had the issue to reboot in safe mode each time even with older version.

Today, I was able to start normally with the latest version lineage-17.1-20200927-UNOFFICIAL.

Arte apllication is running ok.

However, some applications are not able to launch videos: Plex, LBRY-->too bad

Newpipe is dumping when I start to play a video

F-Droid is finding no application.

So for not, this is usless: I will wait some app upgrade and I hope these bugs will be resolved
[Shield Android TV Android Development] MuadDib6:
Newpipe is currently not working becouse of some changes in YouTube. They will fix it in new version.

For the rest I don't know.
[Shield Android TV Android Development] ericfav:
Correct, latest version of Newpipe is working.

Since I was no able to start with old version of TRWP, I was not able to install lineage OS 15 and older.

With lineageOS version 16 or 17, I am not able to play video with Plex and LBRY.

I reintalled the original ROM and was able to play video with Plex and LBRY (newpipe as well).

When there is question to login to the google account, I use this key on the remote: Top, then Right, then Down, then left which allow me to bypass this step.

I also changed the launcher in order to have shortcut for LBRY which is not designed for Android TV.
[Shield Android TV Android Development] Zacharybinx34:
What's the advantage of running full android instead of Android TV?

Is there a way to make the controls work better and more like android tv?

Also, does this include the Shield OS's functions like mapping an external network drive? etc.?
[Shield Android TV Android Development] I_did_it_just_tmrrow:
Is there a chance to get a fresh build with current android security fixes. It would be awesome!

Isn't there a chance to build an UNOFFICIAL 17.1 or 16 microG rom with Steel01 sources? I feel a bit unsure if I am able to handle this...

The first microG and thus google free AndroidTV operating system will certainly find some hearing on the net.
[Shield Android TV Android Development] Steel01:
Microg doesn't support android tv. You can run Lineage without google apps, though. All microg does is lie about being google so apps that use google resources will run without play services.