[ROM] [OFFICIAL] LineageOS for the Shield Android TV - Shield Android TV Android Development

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Instructions :
Download the latest build and gapps
Reboot to recovery
Flash the latest build and gapps
Reboot
Downloads :
Builds : foster / mdarcy
Google Apps : http://opengapps.org/
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed or Magisk
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console_ramoops. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
LineageOS for the Shield Android TV, ROM for the nVidia Shield Android TV
Contributors
Steel01
Source Code: https://github.com/LineageOS/android_device_nvidia_foster
ROM OS Version: 10.0 Q
ROM Kernel: Linux 4.9.x
Version Information
Status: Stable
Current Stable Version: 17.1
Created 2017-07-06
Last Updated 2021-10-15

---

Couple notes.
1. I don't have firmware update zips yet. Unfortunately, I think the different models will need different firmwares. Though, I may still be able to make that one larger zip. Not going to happen real real soon because:
2. I soft bricked my darcy (2017 emmc model). The official build didn't boot for some reason. And using the controller to get to fastboot isn't working. I have a message out to one of my contacts seeing what can be done. The official build works fine on my sata model, and my side builds worked on both. So, I expect it was just a fluke, but if you're on the newer emmc model, might be a good idea to make sure the controller works in fastboot before flashing.

---

Steel01 said:
Couple notes.
1. I don't have firmware update zips yet. Unfortunately, I think the different models will need different firmwares. Though, I may still be able to make that one larger zip. Not going to happen real real soon because:
2. I soft bricked my darcy (2017 emmc model). The official build didn't boot for some reason. And using the controller to get to fastboot isn't working. I have a message out to one of my contacts seeing what can be done. The official build works fine on my sata model, and my side builds worked on both. So, I expect it was just a fluke, but if you're on the newer emmc model, might be a good idea to make sure the controller works in fastboot before flashing.
Click to expand...
Click to collapse
So this does work on the Shield Pro 2017? I already have unlocked bootloader and I can boot TWRP. Also have Supersu installed. Also is it rooted? Sorry if this was already answered in the thread.
thanks

---

Any big bugs?

---

It works on all models, and there is no difference between the old and new pro models. Su is not included, same as other Lineage releases. But there is the official su addon zip on the download site.
Big bugs? Guess I didn't copy those from the old thread. Only thing I know of is Netflix. Having so much trouble making it happy... Finally gave up and pushed official anyways. Won't even run on most models, and while it does run on the new emmc model, the video stops playing after a few seconds. The only other thing I know of is the annoyance of pairing: have to have a controller hard wired on first boot. Then after the setup wizard you can pair a Bluetooth controller and everything works fine.

---

Steel01 said:
It works on all models, and there is no difference between the old and new pro models. Su is not included, same as other Lineage releases. But there is the official su addon zip on the download site.
Big bugs? Guess I didn't copy those from the old thread. Only thing I know of is Netflix. Having so much trouble making it happy... Finally gave up and pushed official anyways. Won't even run on most models, and while it does run on the new emmc model, the video stops playing after a few seconds. The only other thing I know of is the annoyance of pairing: have to have a controller hard wired on first boot. Then after the setup wizard you can pair a Bluetooth controller and everything works fine.
Click to expand...
Click to collapse
thanks for the reply. and I take it Su is flashed in TWRP? Do i do a factory wipe in TWRP before flashing Lineage?

---

Yes, Lineage, su, and gapps are all flashed in twrp. You will need to wipe data and caches when flashing Lineage for the first time. Internal sd can be persistent, though.

---

Steel01 said:
Yes, Lineage, su, and gapps are all flashed in twrp. You will need to wipe data and caches when flashing Lineage for the first time. Internal sd can be persistent, though.
Click to expand...
Click to collapse
great thanks. Will report back how it goes when I try it out.

---

Is it full play store and what interface?

---

But is gamestreaming present in this?

---

This is Android TV and uses the ATV store. I will make an unofficial build of tablet mode sometime in the future.
Game stream works fine. I test with Geforce Now, but game stream uses the same thing. Just install nvidia games and it will work.

---

dk1keith said:
great thanks. Will report back how it goes when I try it out.
Click to expand...
Click to collapse
Gave this a try. It flashed fine. Flashed Lineage, gapps and Su. All seemed to flash without issue. Only problem was user error. I flashed the wrong gapps. Should have flashed X64. after reboot couldn't see Google Play Store. I was able to pair the remote and the controller with very little problem since I already had a wireless keyboard attached. I went back into TWRP to flash the correct gapps and that is where things went south. TWRP for some reason was having a problem with mounting partitions. I couldn't even restore backups I had in TWRP. All this I'm certain was a result of something I did. I was able to finally get back in and restore a previous backup. Scary stuff though. Gonna have to pay closer attention when I try this again. At one point TWRP even said no OS installed. Everything seemed to work as it should other than my few fumbles. Looks really promising. Great work
thanks again.

---

The only other thing I know of is the annoyance of pairing: have to have a controller hard wired on first boot. Then after the setup wizard you can pair a Bluetooth controller and everything works fine.
Click to expand...
Click to collapse
@Steel01 so the original Shield Controller is working? I'm asking this because I was not able to pair my shield controller with my shield tablet (I'm using your official LOS on shield tablet too).

---

Luca-91 said:
@Steel01 so the original Shield Controller is working? I'm asking this because I was not able to pair my shield controller with my shield tablet (I'm using your official LOS on shield tablet too).
Click to expand...
Click to collapse
No it doesn't. The old controller is wifi direct, not bluetooth. There is a way to manually pair the controller using adb or a terminal emulator, but it's not at all user friendly. The new blocky controllers are bluetooth.
I'm still working from time to time to try and get the official pairing app to work for the old controllers, but there's some hook loading code that Nvidia hasn't released yet and I haven't quite reverse engineered either.

---

Steel01 said:
No it doesn't. The old controller is wifi direct, not bluetooth. There is a way to manually pair the controller using adb or a terminal emulator, but it's not at all user friendly. The new blocky controllers are bluetooth.
I'm still working from time to time to try and get the official pairing app to work for the old controllers, but there's some hook loading code that Nvidia hasn't released yet and I haven't quite reverse engineered either.
Click to expand...
Click to collapse
Thanks for the reply. Ah then this is a show stopper for me I've only the original shield controller, and I need it in order to use my shield tv
Is root required to manually pair the controller? thanks

---

Steel01 said:
This is Android TV and uses the ATV store. I will make an unofficial build of tablet mode sometime in the future.
Game stream works fine. I test with Geforce Now, but game stream uses the same thing. Just install nvidia games and it will work.
Click to expand...
Click to collapse
any ETA on tablet build?
thanks for your work here

---

I made the build Saturday night, but didn't get around to testing it. Still fighting with my darcy. It boots unofficial builds, but croaks on the official one. And fastboot is acting extremely flaky. I may get to testing a tablet build tomorrow night, but no guarantees.

---

Amazing! I think a lot did't know about this!

---

Steel01 said:
No it doesn't. The old controller is wifi direct, not bluetooth. There is a way to manually pair the controller using adb or a terminal emulator, but it's not at all user friendly. The new blocky controllers are bluetooth.
Click to expand...
Click to collapse
Is there a link anywhere to a description/guide of this manual way? I might be willing to give it a try. Also, is the link procedure needed only once, or every time?

---

Can this be flashed straight from Marshmallow or do I need to upgrade to official Nougat first?