[ROM] [UNOFFICIAL] Cyanogenmod 13.0 for Shield TV (all variants)

[Steel01]

For me, it'd be Dr. Pepper. But nah, I don't need any donations or such. The only reason I'd considered it before was for new hardware, but that's finally covered thanks to an Nvidia developer program.

*finally* got the major atv bug squashed and gapps work fine now. There's a couple minor problems that should get cleared up sometime this week when the other devs get their Nexus Players. Then I'll be able to release experimental builds and hopefully shortly thereafter, official builds.

There's nothing special about flashing procedures. TWRP works like expected except that you need a mouse plugged in.

 

[dot64]

For me, it'd be Dr. Pepper. But nah, I don't need any donations or such. The only reason I'd considered it before was for new hardware, but that's finally covered thanks to an Nvidia developer program.

*finally* got the major atv bug squashed and gapps work fine now. There's a couple minor problems that should get cleared up sometime this week when the other devs get their Nexus Players. Then I'll be able to release experimental builds and hopefully shortly thereafter, official builds.

There's nothing special about flashing procedures. TWRP works like expected except that you need a mouse plugged in.

Sounds good!

Just want to be extra sure of a few things before I move forward. Would hate to brick my devices

- Flash Official TWRP from https://twrp.me/devices/nvidiahshieldandroidtv.html (Will this work for both foster & darcy?)
- Do a factory reset wipe
- Install zip & reboot

Am I missing anything? Thanks!

Oh and also, I assume it will be possible to revert back to the stock NVIDIA firmware via booting to the bootloader/fastboot to flash stock rom?

 

[Steel01]

I merged part of the darcy support for the latest twrp build. I didn't put all the new kernel stuff in, so I don't know if it will actually boot properly. It's not hard to test with fastboot boot, though. If the official one doesn't work, that unofficial one in this section will. And one of these days, I'll get everything merged upstream and get it all available there.

You don't have to do a full factory reset unless you haven't unlocked the bootloader yet. You only have to wipe cache and data, internal sd is fine as is.

And restoring to stock is even easier than that. Just make a twrp backup. You can restore it whenever. But if something goes horribly wrong and there's no backup available, then yes, fastboot flashing a factory image works fine.

 

[ahoslc]

Is Netflix still a no go?

 

[dot64]

I merged part of the darcy support for the latest twrp build. I didn't put all the new kernel stuff in, so I don't know if it will actually boot properly. It's not hard to test with fastboot boot, though. If the official one doesn't work, that unofficial one in this section will. And one of these days, I'll get everything merged upstream and get it all available there.

You don't have to do a full factory reset unless you haven't unlocked the bootloader yet. You only have to wipe cache and data, internal sd is fine as is.

And restoring to stock is even easier than that. Just make a twrp backup. You can restore it whenever. But if something goes horribly wrong and there's no backup available, then yes, fastboot flashing a factory image works fine.

I was successfully able to flash my darcy (NVIDIA Shield TV 2017 16GB) though noticed that the Google Play Store does not work properly. I flashed the latest gapps nano ARM64 7.1. Every time I go to install an app it hangs after I press install. Any thoughts?

Thanks!

 

[Steel01]

Sorry again for the long delays, I've been quite distracted with others things recently. The major holdup here is still trying to get the ATV stuff working correctly. I think I'm pretty close, like the only thing I know I need to do is get the setup wizard pointing to the leanback stuff. But with the precious little free time I have right now, I don't know when I'll be able to crunch through that and get the official builds rolling.

 

[gabrielgagz]

Hi @Steel01 i'm building LOS 14.1 for Razer Forge TV, completely different hardware, but the same platform.
I'm also facing some weird and "hard to solve" bugs...maybe we can exchange some opinions

Cheers

 

[Steel01]

Hi @Steel01 i'm building LOS 14.1 for Razer Forge TV, completely different hardware, but the same platform.
I'm also facing some weird and "hard to solve" bugs...maybe we can exchange some opinions

Shoot me a pm. I'm almost ready to ship this device, got workarounds for all known ATV problems available.

So, I think I'm about ready to upload another atv testing build this weekend. Going to do some more thorough testing myself before that, though. But sans wireless pairing for the old controllers, I think it's good to go. And bt pairing won't work I'm the wizard either... Will need to step through wired, then pair a bt controller after the wizard.

In semi-random news, I picked up a Jetson TX1 this last week. And I've got it booting Lineage as well. Unified with the shield android tv builds. And having a truly open bootloader and serial debut has already helped me fix a couple bugs I didn't know about. Hopefully it'll help more as time goes forward.

I may also push a tablet mode test build, but I'm not going to be much focused on it until ATV is stable and the weekly builds rolling.

 

[Steel01]

Well, it finally happened. Took almost two years. But I finally flipped the switches to get official foster builds rolling. Like mentioned before, these are ATV builds. If you've got the new Bluetooth controller, virtually everything works smoothly and as expected. Still haven't got stuff together for the WiFi direct controller yet, though. So, I'll be making a new thread hopefully sometime today. The first build will run on Tuesday night relative to the US. Few things to note:

1. Bluetooth pairing doesn't pop up on first boot. You'll need something wired to do initial setup. Once you go into settings and pair something, it will work as expected, though. This is related to a Lineage setup wizard bug that I couldn't fix, so I had to just disable pairing in the wizard.
2. Googles setup wizard caused some issues of its own, so I had to force disable it as well. However, the first time you run something needing a google login, it'll step through the process correctly.
3. Netflix. Love / hate relationship here. Got widevine level 1 working or at least it claims to be. On Darcy, I got Netflix ATV running, but the stream hangs less than a minute into anything. On foster_e_hdd, it won't even run. Complains about device not compatible and I haven't figured out what it's looking for. Oh, and because Netflix flipped the safety net switch on the store, we can't install it from the play store, have to side load it anyways. Le sigh. This'll be something I'll continue working on over time.

 

[Steel01]

https://forum.xda-developers.com/shield-tv/development/rom-lineageos-shield-android-tv-t3632652

Official Lineage thread finally. Going to run tablet mode builds eventually, but things are busy again for a bit.

 

[eried1]

I'm interested in this ROM because of Marshmallow which apparently is a no go if you want stock and have updated to Nougat.
@Steel01, did you solve the wireless pairing issue? Can I use controller and/or remote?