yashsingh1/xdaforums huggingface dataset:
[Shield Android TV Android Development] Steel01:
[MENTION=2533677]reflog@gmail.com[/MENTION]: Kodi is of great interest to me as well, so I'll work to make sure works well.

[MENTION=5097551]aniel300[/MENTION]: No, it's pure CM. I plan to make the TV stuff accessible, but it won't be there by default.

I finally got a bootable build, but it does show more problems. The launcher and some programs lag terribly. Not locking up, but slow enough to trigger ANRs. Netflix does still crash when loading a video, hopefully that won't be hard to fix once I can read the logs. The interface still flickers, but only the interface, not videos or games or such. I'll do some more testing this afternoon and unless an even worse problem shows up, I'll release.
[Shield Android TV Android Development] Steel01:
New build is up. It appears the netflix bug affects others things too, like youtube. Appears to be audio related, but I don't have time right away to try and track down the root cause. So, consider this another bug hunting build and not truly usable.
[Shield Android TV Android Development] Steel01:
I've fixed an audio problem, so sound and YouTube and all that works again. Netflix is still confusing me a bit, though. It appears to be a problem with the OMX libs, but not one seen on any other Shield device. Haven't spent too much time looking the last few days.

I'm in the process of restructuring the build setup on my dev machine. Like moving the build trees to a faster spinny disk and ccache to a ssd. That should get builds going a lot faster. 4 hours per build gets old real fast. And 45 minutes for a one package change. I plan to release a new build once I get that all sorted out.
[Shield Android TV Android Development] aniel300:
what about you try to port android m tv developer preview instead or at least cm but with all the good stuff from android tv.
[Shield Android TV Android Development] patt2k:
It seems Forge has unlockable bootloader they posted instructions also for home images so it's a start it should be easy to flash recovery if there was one. Sorry for going little off topic but this seems more active here :D
[Shield Android TV Android Development] Steel01:
New build up. Seems the OMX libs are only partially working. Youtube works, but mxplayer and kodi fall back to their software decoders. Wireless appears to finally work, but logcat messages lead me to believe it's still not completely there. Oh, and the UI flickering is still there.

So, I loaded this build up and promptly installed HALauncher and Kodi. With the controller wired in, this seems to be a pretty usable setup. As things begin to stabalize, I'll probably start to recommend that launcher as a replacement for leanback. Now if only I can find a replacement for the leanback keyboard, I won't have to include any Google blobs... Suggestions are welcome for a free and preferably open source dpad enabled keyboard.
[Shield Android TV Android Development] Steel01:
Really good progress tonight. Barring something patentably bad happening, I should be releasing a new build tomorrow. List of progress:

1. Interface flickering is way down. Don't know if it was something I did or if upstream CM tweaked stuff. Either way, it's bearable now. I only notice it on some transitions, whereas before it was all the time on builtin android interface stuff.

2. OMX libs work. Hardware accelerated video and movies, plus game streaming and grid works now.

3. Leanback IME (controller enabled keyboard) is part of the build. It's smaller than on stock, but still usable.

Some things still need work, though:

1. Netflix still fails to play a video. At least it doesn't crash to desktop anymore...

2. Wireless controller pairing fails. The app runs and it tries to set stuff up, but seems to hit the same problem the Portable does most times. I have got the Portable to pair once or twice, though, so some people might be more lucky than me and it'll actually work.

All in all, this looks like a very usable test build, if not a daily driver for some use cases.
[Shield Android TV Android Development] duanim:
Hi steel01

I am planning to buy this device, pro version, but its true that the SSD storage drive has some problems about performance and response, speed, looking all around for a good review about this and nothing found yet,unbelievable, I want to be sure the 16 GB or pro version.

Counting on you,like you doing on the shield tablet,interesting approach with CM,look forward, when I get it I will install the Zulu99 full android ROM first and them....cm

Good luck on this, thank for you hard work
[Shield Android TV Android Development] Steel01:
I haven't had any lag problem with the Pro edition, but I also haven't done anything IO intensive. So, I'm not really a good yardstick for that. However, the pro edition does have the 16GB hardware, just needs some tweaking to be able to access it. Probably could do some boot image trickery to get /system on that device. Haven't looked at that yet since CM and multirom are higher priority in that order.

Other stuff came up today, so I didn't get to test the new build. As soon as I drag it back across the house to reflash it, I'll verify the build and upload. Maybe tomorrow afternoon.
[Shield Android TV Android Development] duanim:
I am just a thinker, its possible to use all the best feature of CM and put it in android tv or viceversa.

I dont own yet a android tv device, but is like no to manny peoples like it, may restrictions from google, its entirely new or old UI, developers needs to port their apps to android tv platform, maybe we like the custom launcher or just the regular launcher, well its until everybodys decision.

Multirom sound good, but i like the basic and fast, what about if we can have two launcher in the GUI or UI, can be possible, there is a really need an apps to be ported to android tv platform, why google put restriction, we can sideload to get what we want, i think this is confusing android OS is android.

I think the best thing to do its going back to the basic.
[Shield Android TV Android Development] Steel01:
Well, I didn't get to testing today either. I think I'll run another build tonight and try to get to a test tomorrow night.

[MENTION=6433553]duanim[/MENTION]: That is my end goal for my device. The Shield TV running CM with a 10 foot launcher (that isn't leanback) and everything accessible from the controller. The current build isn't too bad for that, but not all the way there. CM and HALauncher works pretty well. But the controller still needs help wirelessly.

There's one major problem with running android and android tv simultaneously. It seems the play stores are different. You either get the TV apps or the normal apps, not both. If someone knows different or a way to work around this, I'd love to hear it.
[Shield Android TV Android Development] Steel01:
Still can't get the dumb wireless controller libs to package the way I want. So the latest build is missing some, causing the app to continuously force close, making the build unusable. I'll split it like I didn't want to and should have a releasable build tomorrow.
[Shield Android TV Android Development] 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.
[Shield Android TV Android Development] reflog@gmail.com:
any news?
[Shield Android TV Android Development] 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.
[Shield Android TV Android Development] 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.
[Shield Android TV Android Development] 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!
[Shield Android TV Android Development] kdb424:
Any progress on this rom?
[Shield Android TV Android Development] 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.
[Shield Android TV Android Development] baileyjr:
I know that feeling mate God forbid I break the Kodi installation I set up for the mrs :D
[Shield Android TV Android Development] tailslol:
Default google keyboard and go keyboard works OK with dpad on any language.

With some work this rom could be amazing!
[Shield Android TV Android Development] 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.
[Shield Android TV Android Development] 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.
[Shield Android TV Android Development] 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.
[Shield Android TV Android Development] plokm:
Nice
[Shield Android TV Android Development] 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.
[Shield Android TV Android Development] tailslol:
twrp on 2.x firmwares are instant bricks. dont try ,this just suck.
[Shield Android TV Android Development] Steel01:
Say what? My latest build worked just fine for me. And wrong thread, anyways.
[Shield Android TV Android Development] tailslol:
The pixel c binaries are available with tons of infos about the tegra x1 it can be used for a cyanogen 13.
[Shield Android TV Android Development] Steel01:
Oh sure, *now* they release it when I'm going to be afk for two weeks. :p

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.
[Shield Android TV Android Development] tailslol:
Yep ryu and dragon.

https://developers.google.com/android/nexus/drivers#dragon
[Shield Android TV Android Development] 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.
[Shield Android TV Android Development] g90814:
Happy new year.

any updates on this?
[Shield Android TV Android Development] Steel01:
No, not yet. I'm pretty much waiting on Nvidia to release M before I work on CM-13.0. I tried once to get 13 booting, but it just hung at the Nvidia logo. I'll post more info when I start merging the new blobs and source.
[Shield Android TV Android Development] g01851:
Ok cool, thanks for speedy reply (I'm g90814 too, wasn't logged in to right account when I posted!).
[Shield Android TV Android Development] digimancer:
[MENTION=1416222]Steel01[/MENTION]

Any chance you can use [MENTION=1469500]zulu99[/MENTION] http://xdaforums.com/shield-tv/development/rom-t3138575 [Full Android for Shield TV][v.2.2] and add in the Cyanogenmod apps/tweaks to get a more stable and usable mod? [MENTION=1469500]zulu99[/MENTION] has made a VERY stable mod and I think it would make a good starting point for a CM build.
[Shield Android TV Android Development] Steel01:
There's actually not much similarity between the two. Zulu's is a hybrid of stock and aosp. CM is full aosp, with as much built from source as possible. So unfortunately, I can't just pull stuff from there.
[Shield Android TV Android Development] digimancer:
I was hoping for more of an add to his build, rather than pulling from it.
[Shield Android TV Android Development] Steel01:
Oh, well personally I'm not much interested in a hybrid build. I'm much more on the GPL side of things. So, I put my time into things that are as open source as possible. In this case, CyanogenMod. Nothing against other projects, it's just something I'm not interested in working on.
[Shield Android TV Android Development] digimancer:
Bummer, but I understand your motives. Hopefully this device drops in sale price enough to where it becomes more appealing for other modders to take a crack at it. Anyways, I wish you much success on this, hopefully you get that graphics glitch sorted, as that is by far the biggest "Nope" to flashing your build as an end user. :good:
[Shield Android TV Android Development] tailslol:
well marshmallow is now about to come out on shield,cyanogenmod 13 port could become a solution with some of the sources of the pixel c comming too.
[Shield Android TV Android Development] Steel01:
Yes, I agree my cm-12.1 builds are not truly usable for three reasons. First is the kaleidoscopic interface. Second is a good number of video codecs just giving blacks screens (same on stock, but still...). Last is lack of wireless controller support.

I have high hopes for cm-13.0 once Nvidia releases M for the TV. Hopefully the newer video libs won't cause such problems. I'll try to keep a progress log here once that happens as I import everything and start builds again.
[Shield Android TV Android Development] tailslol:
Yes,humm things are moving in aosp.

Pixel c tegra x1 support.

https://android.googlesource.com/device/google/dragon/+/android-6.0.1_r5
[Shield Android TV Android Development] redgabber:
i encourage you... give us CM 13 mate :)
[Shield Android TV Android Development] tailslol:
here we go,the marshmallow update is avaliable,and the pixel c code is complete,and there too aosp for the pixel c.

so i guess it will give a lots of infos for cyanogen 13 port.
[Shield Android TV Android Development] Steel01:
Yes, I've started working on cm13 again. Got it to boot and hallelujah, no flickering... Had to do a couple manual hacks to get that far, though. I'm in the process of making that automated. There's also a problem with sound, it doesn't initialize. But, it's already looking better than what I had from 12.1. Given a little bit of time, I should be able to get a solid release out.
[Shield Android TV Android Development] tailslol:
yay ,great to hear !

here some random sources i found that could help you.

this

https://developers.google.com/android/nexus/drivers

this

https://developer.nvidia.com/shield-open-source

and this

https://android.googlesource.com/device/google/dragon/

https://android.googlesource.com/device/google/dragon-kernel/
[Shield Android TV Android Development] Steel01:
Well, this build just barely made my cut for experimental release. Keep in mind that it's like day three of development, with precious little time to put into it. Running really smooth for me. Using the controller wired (haven't even looked at the pairing app yet) and a mouse atm. Ran into a few things I can't get to via controller. This only has the leanback keyboard, so the controller or a keyboard is required, unless another is loaded. So, known problem list:

1. I have somehow got this thing stuck in the worst possible place between android tv and normal android according to the play store. None of the android tv apps show up in the play store loaded by opengapps and neither do ones that blacklist android tv. So, no netflix, no youtube, etc. But Kodi shows up. I'll play with the android permissions list (list of things the play store filters on) to find the balance. Ideally, there will be a way to switch between them. Will need to see what the Nexus Player and such ports do.

2. Sound doesn't work. Well, technically it does, but it doesn't go anywhere. I think this is the same problem the tablet has where audio won't route over hdmi. I know, I know, it's a media device, got to have audio. But hey, it's a bug testing build.

That's all I know of right now. If anyone's brave enough to give it a spin, let me know if you find other problems. That is, if the lack of sound doesn't drive you nuts first. :nervous:

WARNING: You need to have updated to stock 3.0 BEFORE flashing this. It requires the new bootloader, dtb, partition layout, etc, etc.

cm-13.0-20160224-UNOFFICIAL-foster.zip
[Shield Android TV Android Development] tailslol:
good now lets see where the bugs could be and how to fix them.

the market

you can try to change the build.prop this can help.(look at the pixel c or nexus and shields tab build.prop for example)

market helper app can help again with the problem.

you can test in and out sound with soundabout app.

one last thing.

you should look this,it is cool.

http://www.ibtimes.co.uk/how-enable-multi-window-mode-android-6-0-marshmallow-1524479
[Shield Android TV Android Development] Steel01:
Well, been working on splitting out the common code between the shield tv and tablet (and future devices). Should make updates and maintenance easier in the long run.

Haven't got time to do testing and debugging yet due to that. Hoping to have time Saturday to dive into it. Will probably debug the hdmi audio issue on the tablet since I can plug/unplug the cable while retaining use of the device. I expect the problem here and there to be identical.
[Shield Android TV Android Development] Klanac89:
CM13 on shield TV... This will be more than great!
[Shield Android TV Android Development] ahoslc:
Any Progress?
[Shield Android TV Android Development] Steel01:
Unfortunately not. I tried to track the HDMI audio issue down, but got nothing. Then, I'm also waiting on opengapps to finish their leanback variant.

Yes, I know, I know, it's taking forever. But I'm still really the only lead dev on Nvidia devices (in regard to cm/aosp ports) and I only have a few hours a week to work on these. I've got the portable up to par finally, and now I'm bouncing between the show stopping bugs on the tablet and TV, but neither are budging atm...
[Shield Android TV Android Development] Steel01:
Well, another two months and not much progress. I'm poking at another angle to fix the audio problem, though. Trying to use the audio lib from L. That was working before. If I can get it to load, in theory, audio will work. Haven't quite got there yet, though. Running another build overnight and will be back at it tomorrow night.

Everything else still seems to work fine. Running builds in tablet mode atm though, since opengapps still hasn't finished up their leanback version.
[Shield Android TV Android Development] tailslol:
Good,from what I know Zulu was able to build a stable image by using part of the stock image he decompiled. To fill the blanks.

Then he recompiled the new image.

Hope it help
[Shield Android TV Android Development] Steel01:
Yeah, all of Zulu's builds are stock rebuilds, I'm building pure cm with as few blobs as possible.

Finally got the audio blob to load correctly. Problem is, that was remote, so I can't actually test it yet. Running a new build now, and I'll test tonight. If it does work as intended, I'll release that tonight. Pending user tests, I can finally push it all in for official cm nightlies. Still in tablet mode until the TV gapps and all stabilize. Ideally, a user could choose which mode to use by flashing normal or TV gapps. But we'll see how that goes.
[Shield Android TV Android Development] Hazeno:
Steel01 so glad to see you back in action on the shield tv

One question are you hoping to have WiFi direct working so controllers will pair? If so this rom will be nabbed by too many users I know.
[Shield Android TV Android Development] Steel01:
No, unfortunately not yet. I've tinkered with the new pairing app on the tablet, but it fails when it doesn't find the nvinput service. And I can't find what provides it. That's one of the questions I have out to one of my Nvidia contacts. Unfortunately, he's been sick for a while and hasn't been able to get back to me yet. So for the time being, the shield controller has to be used wired. I wish I could figure out the pairing sequence so it could be reimplemented as open source (and for Linux). But no luck there yet either. Those with Bluetooth controllers should be able to use them, however.
[Shield Android TV Android Development] Hazeno:
Hopefully he makes a recovery. And hopefully some insight could be shed on this predicament. At least you have the plans to try and get wireless functionality. Any reasons why nvidia seem closed off about this device? As zulu didn't get WiFi to work? Or am I wrong and he didn't want to not couldn't?

I'll test this rom out for you though and keep my eye on the thread. This has very very much peaked my interest. I shared it in a telegram chat and a few others are also keen to see your progress. Good luck Steel01.