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.any updates on this?
Ok cool, thanks for speedy reply (I'm g90814 too, wasn't logged in to right account when I posted!).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.
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.@Steel01
Any chance you can use @zulu99 http://forum.xda-developers.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? @zulu99 has made a VERY stable mod and I think it would make a good starting point for a CM build.
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.I was hoping for more of an add to his build, rather than pulling from it.
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: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.
Yes,humm things are moving in aosp.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.
yay ,great to hear !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.
good now lets see where the bugs could be and how to fix them.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
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