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

[duanim]

What are you doing so far steel01. Still having problems with the controller,forget for now and move forward,maybe the best way now it's using droidmote,from zulu99.
Question what about using different home screen,one like full pure android and the other android tv launcher of course controller with air mouse or gamepad. So if somebody wants the android tv experience should change the buildpro to get the benefits of the play store tv,or vice versa or the other way for full android,the regular play store.,.I don't if this can be done.

 

[[email protected]]

any news?

 

[Steel01]

Sorry, got busy with other stuff.

I've been running CM on my console for several days now, using it to run Kodi. The controller still has to be wired, though. It works okay, but video playback isn't smooth. That might be the Kodi renderers fault, though. Also, the touchpad on the controller still doesn't work. Haven't tracked down whether that was disabled on the controller level or if the pairing app is disabling it even when wired. I'll run a build tonight and try and get that released tomorrow morning. Likely won't be tested, but nothing has changed on my side since the build I'm running now.

Edit: Well, I started it uploading this morning, but it hasn't finished yet. Something must have hiccuped. So, it'll be tonight before I'm able to see what happened and fix it.

 

[Steel01]

Okay, new build up in the OP. Not specifically tested, but should be quite similar to the build I was testing from earlier this week.

1. Interface flickers some, but no where near as bad as before.
2. Wireless controller pairing didn't work for me. Seems similar to the problems I have with the Portable, which means it is possible to get it to work, just no where near consistently. YMMV
3. That's all that's coming to mind right now. Please report anything and everything. I think this is out of the early alpha stage, but it isn't anywhere near the stable release I want.

 

[machx1111]

Thanks for all my your work on this Steel!

I am still waiting for things to become more stable before adopting as daily driver due to my Shield being a family device (if things don't work I'm in big trouble!)

Looking forward to this!

 

[kdb424]

Any progress on this rom?

 

[Steel01]

This is pretty much the same status as the multirom port. Working on the tablet and portable ports to get them pushed upstream. Until that's done, I'm not spending much time on this. All the code is in the cm-shield org on github if anyone wants to contribute.

 

[baileyjr]

Thanks for all my your work on this Steel!

I am still waiting for things to become more stable before adopting as daily driver due to my Shield being a family device (if things don't work I'm in big trouble!)

Looking forward to this!

I know that feeling mate God forbid I break the Kodi installation I set up for the mrs

 

[tailslol]

Default google keyboard and go keyboard works OK with dpad on any language.
With some work this rom could be amazing!

 

[Steel01]

Status update. I'm running CTS scans this week,trying to figure out what all is so flaky. Found a few things, but still a ways to go. Tried enabling some of the leanback flags and broke CM horribly. It was kinda humorous, actually. Guess their TV stuff isn't ready, so I'll be commenting those back out. Anyways, I'm going to try and have a new build out later this week.

 

[duanim]

waiting for good news
one step at the time.
i guest you has to look from nexus player ways,just thinking
steel01 there is an application on the market for android tv to make or add a shortcut to the home screen.

 

[Steel01]

Update on what's going on here. My device got bricked a couple weeks ago trying to update to 2.1, so I haven't been able to do any development for a while. The RMA was finally approved and I'll be shipping it out tomorrow, but who knows how long the turnaround will be.

Before all that, I ran the CTS against my builds, but was running into loads of audio/video decoding issues that I couldn't get a handle on. There were also multiuser problems, but I think I tracked that one down (just can't test yet). But all in all, I don't think L is going to run well on this device. But with M development ramping up, I'm hoping it will work better (merger of android TV and normal android). So, I'm probably going to try one more 12.1 build to see what the multiuser change does, but after that I'm going to shift to only working on 13.

 

[plokm]

Nice

 

[Steel01]

*Finally* got my rma in. Thought I bricked it again four hours later... Seriously, this bootloader is garbage. Anyways, back on the bootloader from 1.3, so I can actually get to fastboot ifwhen I flash something that doesn't boot.

First attempt at CM13 didn't boot at all. Probably because the bootloader ignores kernel parameters in the boot image. Running another build today to disable selinux at the kernel level to see if it'll boot to adb at least.

The change to enable multi-user in CM 12.1 did work. Yay. Running another CTS scan (probably 20-22 hours...) to see how many problems that clears up. Should be a bunch of them. Which leaves video acceleration and the interface flickering as the major remaining problems. But like I said before, the video problems probably aren't going to be fixable, so I'll probably release this build for those interested in tinkering, then move on to 13 only.

 

[tailslol]

*Finally* got my rma in. Thought I bricked it again four hours later... Seriously, this bootloader is garbage. Anyways, back on the bootloader from 1.3, so I can actually get to fastboot ifwhen I flash something that doesn't boot.

First attempt at CM13 didn't boot at all. Probably because the bootloader ignores kernel parameters in the boot image. Running another build today to disable selinux at the kernel level to see if it'll boot to adb at least.

The change to enable multi-user in CM 12.1 did work. Yay. Running another CTS scan (probably 20-22 hours...) to see how many problems that clears up. Should be a bunch of them. Which leaves video acceleration and the interface flickering as the major remaining problems. But like I said before, the video problems probably aren't going to be fixable, so I'll probably release this build for those interested in tinkering, then move on to 13 only.

twrp on 2.x firmwares are instant bricks. dont try ,this just suck.

 

[Steel01]

twrp on 2.x firmwares are instant bricks. dont try ,this just suck.

Say what? My latest build worked just fine for me. And wrong thread, anyways.

 

[tailslol]

The pixel c binaries are available with tons of infos about the tegra x1 it can be used for a cyanogen 13.

 

[Steel01]

Oh sure, *now* they release it when I'm going to be afk for two weeks.

But yes, there's lots of stuff I want to see from that code drop. One major part is the nouveau code in the video driver stack. I'm hoping it can be ported over.

Edit: Found the factory images, but no source code. Someone please link it when it's found. Appears the device name is dragon, with alternate names of ryu and smaug.

 

[tailslol]

Oh sure, *now* they release it when I'm going to be afk for two weeks.

But yes, there's lots of stuff I want to see from that code drop. One major part is the nouveau code in the video driver stack. I'm hoping it can be ported over.

Edit: Found the factory images, but no source code. Someone please link it when it's found. Appears the device name is dragon, with alternate names of ryu and smaug.

Yep ryu and dragon.
https://developers.google.com/android/nexus/drivers#dragon

 

[Steel01]

Yeah, that's what I've found so far, that and the full factory images further up. But those are just blobs, no source. So not terribly helpful yet, especially as the video blobs use an entirely different stack that foster currently does.