yashsingh1/xdaforums huggingface dataset:
[Shield Android TV Android Development] leasing:
thanks to you, for your work , can you add the mouse special function to the rom , like RemixOS ,mouse can click as touch to working in all game&app
[Shield Android TV Android Development] Steel01:
I wouldn't say Nvidia is 'closed off' on the device, at least no more than they are for any other shield device. All the code required to be released is released and then some. The bootloader has unlocking built in. They don't prevent any employees from aiding open source projects using knowledge gained by working there (see gnurou and all his tegra nouveau support). Really the only thing they don't do is actively hire people to work on open source projects. And make sure their aosp releases actually work... That's my only gripe against Nvidias shield department. All the code is always released, but most times it doesn't work as is first release.

The stock ROM is really, really close to aosp. There are extensions to allow proprietary additions, but rarely does that change aosp functionality. That makes it pretty easy to port and maintain ROMs for their devices. But when there is a discrepency, yeesh... Like the HDMI audio bug. Happens on the M libs for both the tablet and console, even on their aosp builds. Same with lte on the tablet. A black box no one can crack. Yet, at least.

My recent builds are pure cm tablet mode. It acts just like a tablet. So yeah, mouse works fine. And for some of the touch interface that isn't gamepad friendly, it's required.
[Shield Android TV Android Development] Steel01:
Well, got part of the way there. The module loads, but it crashes any time it tries to play a sound. More debugging and poking around needed. Time is still an issue, though. So, I'll be working on it as I have time, which isn't much for the next four or five days.
[Shield Android TV Android Development] banderos101:
"Still in tablet mode"

If tablet mode means what i think it means, assuming no ill side effect reasons, then you can at least count this one user who would not mind it

So, to recap, to me, its like your saying,

"sorry for gving you a bazzilion gazillion dollars :D

Ahhhhhh, shucks steel, thats okay (off to buy my island)
[Shield Android TV Android Development] Steel01:
Tablet mode as in acts just like a CM build on the shield tablet or any other tablet. No side affects other than you need a mouse to efficiently navigate the system.

I know there's a lot of y'all that want that. But I want my cake and to eat it too. *shock* I'm hoping to build in TV mode and when gapps are flashed, it switches between the modes based on which package is flashed. I don't know how complicated that will be, but that's my ideal. So those that want the 10 foot interface with the flexibility of CM and those that want the normal interface and play store can both use the same ROM.
[Shield Android TV Android Development] tailslol:
Good idea this will need a DPI change between the 2 modes . And an overscan control app.
[Shield Android TV Android Development] BenjiHansell:
I like the idea of the leanback launcher with full CM running in the background. You could, for example, set up a VPN using the full android settings but then go back to the nice simple clean 10-foot UI.
[Shield Android TV Android Development] banderos101:
As someone who already uses a mouse device, thats music to my ears.........respectful nod to leanback supporters

As to your approach, i think its a good one, having a base which everyone starts from(easier debugging perhaps), then users can install/flash, or not, based on their preferences (assuming im understanding correctly)

Offcourse, were getting ahead of ourselves

Gd luck steel, iregardless of outcome............hearing about some of your detailed explanations on what you've observed with our shield tv's, is almost as good as you having released a 99.9% fully funtional CM rom............well.........almost :D

Edit

" 99.9% fully funtional CM rom".......replace that sentence with a more reasonable goal perhaps
[Shield Android TV Android Development] tailslol:
I know this is not the place but jide the maker of remix os made a shield tv rom desktop style based on lollipop. It is on their site in other device category.

It still have video decoding issues but

I find it interesting there are finally new roms coming to the shield tv.
[Shield Android TV Android Development] Steel01:
Huh. I wonder how they got that working. I had video acceleration working on 5.1, but couldn't stop the interface from flickering. Jide doesn't appear to release their device trees, so I can't even look to see what they did... This is why I like GPL over BSD based licenses. :sigh:

Anyways, if there's interest, I can release another cm13 build. Maybe someone can tinker with audio routing and get it to work. *shrugs* I expect a USB audio card would work, but I haven't tried that myself.
[Shield Android TV Android Development] tailslol:
yea not sure too but I will say

full time Chinese workers heh

they ported to tons of devices it seems ...

but yes,closed sources.

for the video issue I'm sure it is because the internal firmware not matching with lollipop.

I saw this issue multiple times.

it will be fixed when they will use same version of Android as nvidia does.

http://www.jide.com/remixos/devices
[Shield Android TV Android Development] leasing:
http://www.jide.com/remixos/devices/shieldtv

I will try
[Shield Android TV Android Development] jewbugles:
How did it turn out? Very excited to get off stock android, would love Cyanogenmod, or Remix with F-droid apps with MicroG, google
[Shield Android TV Android Development] tailslol:
any feedback yet?
[Shield Android TV Android Development] leasing:
nvidia remove the any lollipop OS image

https://developer.nvidia.com/gameworksdownload#?tx=$additional,shield

I can't downgrade to 2.X, so

........:(
[Shield Android TV Android Development] Steel01:
Okay, okay, this is a thread for CM. There's a thread for remix now.

And no, I still haven't made any progress on sound. :( It's pretty frustrating.
[Shield Android TV Android Development] jewbugles:
So you're having an issue on CM with sound so far? Is that the only blatant bug with your build so far? I would love to run CM as I think the stock OS on this shield is crap loaded with so much bloatware, it's slowing Kodi down for me.
[Shield Android TV Android Development] Steel01:
Well, if you consider wireless pairing with the official controller not working a bug, there's that too. But yeah, hdmi audio is the only major bug I know of. Which for this device is pretty show stopping. Same bug happens on the tablet. But until I or someone else finds a fix, this can't go official. In theory, a usb audio card would work, but I haven't tried yet.
[Shield Android TV Android Development] jewbugles:
Damn, yeah the hdmi audio would probably be the more important feature for it. Well I'll be tuning in, and I'm sure many others are very interested in this as well, since Cyanogenmod blows stock out the water. If you need a little motivation I would be happy to tip you some BTC for your efforts.
[Shield Android TV Android Development] tailslol:
Strange ,you said the shield tablet had the same hdmi sound issue.

But in known issue I do not see it here.

http://download.cyanogenmod.org/?device=shieldtablet

Did they just fix it?
[Shield Android TV Android Development] Steel01:
Side note: I'm the CM maintainer for all the shield devices.

The tablet is only on cm-12.1 officially due to a couple bugs: lte and HDMI audio. Both work on L. Also, that bug list doesn't seem to get used much for any device. Though, I probably should update it from time to time... I any case the audio bug is only on the M kernel and blobs which are now shared between the tablet and console.
[Shield Android TV Android Development] tailslol:
Ho i see,heh sorry.
[Shield Android TV Android Development] curufinwe:
If there would/will be cyanogenmod on this device, I would buy it immediately! I hope you get this to work, looking forward to it ;)

Is there any kind of progress you can share?
[Shield Android TV Android Development] j-m-s:
What is the problem with the audio libs?

I have the full android M, generally audio works, but not in messengers like Skype, Facebook, Hangouts or LINE.

Now I made an interesting discovery: in Skype for Android there is an option to switch audio-out between loudspeaker and earphone. The default is loudspeaker, in this mode you not hear any sound. Switching to earphone, everything is fine.

I wonder what this is....
[Shield Android TV Android Development] Steel01:
Zulu's ROMs are stock based which means everything from stock will work, but anything past that is hit or miss. And honestly, stock remasters are hacks at best. Not to knock anything Zulu has done, it seems to work fine, it's just not something I want to use or work on. CM is aosp based where everything is built from source except for a few things from the vendor required to make the machine boot. Unfortunately, I don't know what the problem with HDMI is. If I did, I could do some debugging. It doesn't log anything useful, it just doesn't work. I'm hoping to take another shot at it soon once I finish reworking some source trees.
[Shield Android TV Android Development] Hazeno:
I check this post daily. Just to see if any progress is made. Goodo luck steel01
[Shield Android TV Android Development] Steel01:
No, nothing yet. I haven't had a whole lot of motivation to work on any of the outstanding problems on my devices lately because I can't seem to make headway on any of them.
[Shield Android TV Android Development] efegue:
Does this kernel allow for overclocking? Can you make a kernel for stock rom that allows OC? :)
[Shield Android TV Android Development] Magissia:
Is it possible to get leanback launcher and all Android TV specific packages working on this one ? (I know I can have them on stock, but stock android tv is too much restricted on lots of points)

Anyway, i'm putting 25$ bounty on stable cm13 (or any aosp based, if skipping a version and getting this with the next Android major version it's okay too) that doesn't have abusive performance loss and that is able to run whatever currently runs on stock system. I don't care about shortcuts such as using non-open source drivers, most important is getting it working. That's not much, but I hope others will follow as Steel01 seems to be alone on this.

In case someone provide major code contribution to resolve nasty bugs, I will add more (wouldn't be fair otherwise, but don't expect mountain of donations too)

It feels like most that has the knowledge for these tasks just overwritten android with L4T or ArchLinux already.

(Feel free to send a private message or mention me to redeem bounty as i'm not visiting XDA regularly to generate a mail alert)
[Shield Android TV Android Development] Steel01:
Sure, running leanback and all in android tv mode works just fine. That's the way I have the device tree set up already. I just don't include the launcher itself, though that would be simple enough to do. It's just that one sound bug that makes it unusable. Well, that and lack of TV gapps. One of these days, opengapps will get to it. Well, I might go poke at the sound bug some more. Not really holding my breath that I'll find the problem this time, however.

Side note: The Linux's that are booting aren't really proper ports. They're using the android kernel, which to me is only half a port. However, without being able to pass the bootloader a different dtb, mainline won't work either. So, rock and hard place. :sigh:
[Shield Android TV Android Development] Magissia:
Is the sound bug present because of the usage of the cyanogenmod provided kernel source, or is there problems with sound while compiling nvidia's provided kernel source ?

Would cyanogenmod 13 work with the nvidia's kernel ?
[Shield Android TV Android Development] Steel01:
I've tried booting with the stock kernel. Didn't make any difference. Nvidia has been pretty good about releasing the exact kernel source they use in their stock roms. I've wondered a few times, but every other time, I've found some dumb I did putting together the device and/or vendor trees. So no, not the kernel in this case. Quite possibly framework difference, though. This close to N; however, I'm probably just going to get everything booting on N and wait for blob updates and hope whatever broke for M doesn't apply to N...
[Shield Android TV Android Development] Magissia:
Seems fair, i know nvidia update their products for a long time but I don't recall them doing it quickly, will have to be patient I guess.
[Shield Android TV Android Development] Steel01:
Whew, I can *finally* make an 'about freaking time' teaser announcement.

The audio problem is actually fixed.

How long has it been since android 6 was released for this device? I've been fighting this the whole time since then...

Anywho... It's currently more of a workaround than a true fix. And involves shoehorning a couple shieldtablet libraries in. Currently, I'm holding out trying to get a proper code fix from one of my contacts. But if that doesn't happen, I'll do some cleanup, a bit more testing, and release an experminetal build lineage13 build later this week when I have more time.

Now, I'm not going to push this official, unfortunately. With Nvidia releasing official N in less than two weeks, it'd be better to merge in those updates and push directly to lineage 14.1. But I'm fairly confident I can make that work in short order once the Nvidia code drop happens.

P.S. Did I mention that there wasn't just one one teaser?

Edit: Guess I should mention that my current stuff won't likely boot on the new emmc model since it has a different name (darcy), but AFAIK, the new pro model has the same name as the old one. However, my prep work for 14.1 already has patches that work on darcy. And twrp should work as is. I'm looking to buy the new emmc model to test this and get the new controller and a remote in the process. Nvidia just seems to release stuff when my bank account is having issues... Oh well.
[Shield Android TV Android Development] slutexpress:
Doing God's work haha! I just got a used one last night and these nVidia shields still hold their value like crazy. On ebay you can barely find anything below $200! This will be a very prized ROM once you're all finished with it! Looking forward to this like crazy my friend.
[Shield Android TV Android Development] Steel01:
And here we go with the experimental release. Few things of note.

1. This is a lineageos build. However, some stuff is still in transition, so not all of the rebranding may be done yet. However, the core is still the same as cm-13.0, so that all should work the same.

2. This is a tablet style build, not android tv. Use normal opengapps, not tvstock.

3. Wireless controller support has not been worked on and controller support in standard android isn't so great, so expect to need a mouse. Leanback keyboard is installed, so a controller will need plugged in wired to use that. Currently, there's not an easily available keyboard that has both touch/mouse and controller support.

4. I only did basic tests. Netflix and Geforce NOW both work, so the majority of media related tasks should be fine. It was running a bit slow, though. Haven't looked too far into that yet.

5. This is an engineering build, adb insecure is enabled for debugging purposes.

6. Don't try to boot this on the new emmc model. It has a new code name and will probably just boot loop. The 'new' hdd model sounds like there were no changes, so it should be fine.

So yeah, I don't know of any outright bugs right now, but I won't be surprised to hear there are some. Like I mentioned before, I won't be pushing this to official since the code drop for N is supposed to come next week. But a lot of bugs still carry over, so I want to know if anyone finds some.

lineage-13.0-20170113-UNOFFICIAL-foster.zip
[Shield Android TV Android Development] Klanac89:
Nice! I think the project was dead...

Gesendet von meinem MI MAX mit Tapatalk
[Shield Android TV Android Development] ahoslc:
Any luck bringing to to Android 7 now?
[Shield Android TV Android Development] Steel01:
Working on it. It half boots... Trying to reorganize a bunch of stuff, so I keep running into little problems. I'm making progress, but it's slow cause I don't have a lot of time to work on this during the work week right now. But I'm pretty confident that I'll finally be able to get it to release quality. Eventually...
[Shield Android TV Android Development] Steel01:
Okay, got a decent status update quicker than expected. It boots, sound works out of the box, no hacks (hallelujah...). Got bluetooth initializing (haven't actually paired anything yet). Wifi works. Interface seems smooth. Still got a ways to go, though. The hardware keystore is blowing up all over the place. That's required for the HD secure video streams like Netflix. Don't think hardware accelerated video playback is working yet either. But yeah, enough pieces finally fell together tonight that I went from not booting at all to a three quarters working system. That's a major boost for my confidence...
[Shield Android TV Android Development] ahoslc:
I am excited !
[Shield Android TV Android Development] Steel01:
I'm currently stuck on the hardware accelerated video stuff. Got the keystore working and I think widevine too. But can't truly test that without accelerated video. Previously I think I used the shieldtablet libs to fix that. So, this may be on hold until the shieldtablet code drop. I'll continue poking, but I'm not terribly confident in making it work with what's currently available. Shouldn't be that long of a wait, though.

The fun part is going to be making the wireless controllers work. For those that want a full android build instead of atv, you probably don't care. But I like the atv interface, so I want to get that working. I can make the controller pair by doing some command line stuff. But I have to do more manual stuff to reconnect it after it goes to sleep or the box reboots. Not terribly viable for the average user.

I guess I should ask, though. What type of builds do y'all want? I can run both for unofficial, but it's probably not a good idea to ask Lineage to do both for nightlies. So yeah, post here which one you'd want to use and I'll see if the opinion leans more one way than the other.
[Shield Android TV Android Development] BenjiHansell:
By "type of build" do you mean Leanback UI vs full Android launcher? Personally my preference would be to have the leanback UI.
[Shield Android TV Android Development] banderos101:
If this indeed, is whats being asked, then heres one vote for "full" android
[Shield Android TV Android Development] techjunky90:
For anyone interested there's full nougat android for all model shields already available
[Shield Android TV Android Development] pack21:
Sorry

where, I can't find? I only see stock nougat version.
[Shield Android TV Android Development] KokkoM:
http://www.videomap.it/forum/viewtopic.php?f=25&t=1646
[Shield Android TV Android Development] crnkoj:
I'm for full/normal builds. Naturally working controllers would be awesome, as well as voice commands like on stock. At least for searching.
[Shield Android TV Android Development] Steel01:
So, kinda split so far. Yes, that is what the question meant. leanback/atv or 'full' interface. The same core will be the same either way. If I count myself (leaning toward atv), then with those posting it's an even 2/2 split. But right now, there's a bug in lineage preventing the leanback gapps from working. They work on nvidia's aosp, but not on lineage. And so far, it's way over my head as to why. And since no other atv device is supported, I'm on my own for fixing it... So that by itself may dictate tablet style builds. At least until that gets fixed.

Got a darcy in today. Thanks to Nvidia for supporting my work on these custom aosp based ROMs through hardware sourcing. Had a couple small, but showstopping bugs in lineage that are now fixed. Darcy boots to feature equivalence with foster now. The adb usb port defaults to adb mode, so computer connections work out of the box. I'll eventually tie that to the adb debugging toggle like stock does, just haven't got there yet. The bluetooth controller paired out of the box. In atv mode, the first screen on boot is pairing a bluetooth device. Worked beautifully. So, things are looking pretty good in this section.

Still waiting on shieldtablet sources to be released. Once I get the omx libs from there, the last showstopping problem here (lack of hardware video acceleration) should be fixed and I should be able to do final cleanup and push a testing build out.
[Shield Android TV Android Development] crnkoj:
exciting news!

I have a question, if its possible?... Could you add support for DVBAPI and USB receivers (DVB-S/S2/T/C) into the stock kernel that you will bundle with, or perhaps just make a second kernel with the support. That would be really awesome. Eventually everyone can build it themselves from your sources too, if its too inconvenient to put it in by default.

Thanks

Edit:

hey Steel01, you seem like the ultimate tinkerer/developer for Tegra devices. I was looking through the kernel code for the Tegra/Shield Tv to find how or where to change the maximum allowed frequencies for gpu and cpu, but couldnt really find much, just:

arch/arm64/boot/dts/tegra210-platforms/tegra210-foster-cpufreq.dtsi where the cpu frequency is suspiciously low and thers no gpu freq, emc is there though,

Documentation/devicetree/bindings/cpufreq/nvidia,cpufreq-tegra.txt the documentation here, which is rather scarce.

drivers/platform/tegra/dvfs.c dvfs but kind of limited as well

drivers/cpuidle/cpuidle-tegra210.c

drivers/platform/tegra/cpu-tegra21.c

I know this is way over the top now, a lot about basics too, but if you might have any suggestions/good docs about this topic, so taht i could read about it id really appreciate it.

As far as i understand it, the max frequencies and freq/voltage table is in the devicetree that is built together with the kernel (from the .dtsi files no?) and than depending on the devicetree the cpu-governor/scaling can scale the frequency as allowed by devicetree.
[Shield Android TV Android Development] BenG7:
Hi Steel

Sorry, just found out about cyaniogenmod ported to SATV; jumping on the band wagon here

in the lats post you are saying issue #2 "No audio over hdmi (so, no audio at all)" is now sorted?

Also, just FYI, it looks like the with the latest 5.0.2 stock ROM release for the 2015 model https://developer.nvidia.com/gameworksdownload, wireless controller can be enabled as demonstrated here http://www.videomap.it/forum/viewtopic.php?f=25&t=1646...

Thanks
[Shield Android TV Android Development] Steel01:
Status update: I think I've got everything working except for the keystore/tlk. Having troubles getting everything in line to enable L1 widevine. Works on the tablet, but not on the satv. If I don't figure it out within a couple more days, I'm going to release a test build anyways.

So yeah, audio, video acceleration, Bluetooth pairing, etc, etc all works. If you have the new controller, it should work as is. I've run into some issues pairing, but once it's paired, it appears to work just fine. Audio fails, though. Going to have to experiment with that some later.
[Shield Android TV Android Development] sinekm1:
Can you release a test built, I want to have lineage os on shield TV. I don't care bugs. I hate other hybrid roms, I want to test pure android.
[Shield Android TV Android Development] Steel01:
I tried to get a test build out last night, but it failed to display properly on my new 4k monitors. That might be because I have them in sRGB mode, but I didn't have time to test on my old monitor or poke around much. I'll try more Friday night and Saturday.
[Shield Android TV Android Development] slutexpress:
Just wanted to thank you again Steel, very patiently waiting for Lineage on this, as I can't stand stock bloated crap from nvidia.
[Shield Android TV Android Development] sinekm1:
Thanks a lot. I hope u release a test build.
[Shield Android TV Android Development] sinekm1:
Is there any progress, I am still peacefully waiting a test build. I hope you make it soon. Thanks a lot