yashsingh1/xdaforums huggingface dataset:
[Shield Android Development] Steel01:
All the hardware works, yes. Some of the software features aren't ported like touch mapping for the gamepad, wireless controller support, gamestream, etc. But for the normal use cases I have of retroarch, a handful of controller enabled native games, and kodi, everything works beautifully. So, depends on your use cases.
[Shield Android Development] fr500:
Is this full android or ATV like the one you built for me?
[Shield Android Development] Steel01:
This is a normal build. Probably won't do atv for officials unless the userbase really asks for it. Need to fix gapps before that would even be considered, though. Only 32 installs atm, and half of them are probably me testing.

So, haven't had a bootloop on the new build myself. Anyone having any troubles at all? Seeming really solid to me finally.
[Shield Android Development] stuken:
When using snes9x ex the performance is way down in comparison to nvidia update 110. The screen refresh rate as reported in the emulator is 48.85hz. If that's correct its far too low.

In addition there appears to be another bug where ui animations stutter and loop back a few frames on themselves. Not sure if this is related to the apparent refresh rate issue.

I would also like to chime in on the possibility of an atv build. Without the right stick mouse functionality of the stock firmware the tv interface makes a whole lot more sense.

Thanks for the build and the work you've put in on this and fixing nvidia messes over the years.
[Shield Android Development] Diego9000:
That's great to know!! :D

Once they manage to port the touchmapper and some other software from this device to it, I'm pretty sure to stick with it forever.

I'm using lineage at my MotoG3 and i'm lovng git!!
[Shield Android Development] JazzMartian:
Thanks for this. I just installed it. I had been running your 12.1 CM ROM the last week. I decided to try it out after had enough of the buggy stock ROM. I would install apps, and they would (seemingly) randomly disappear. I would install them over and over again. Anyways, your custom builds of CM/Lineage have been working beautifully.

The only thing that I'm really missing is the gamepad touch mapper. I know you've said that you don't use it, but it seriously hurts not having it, because you can so quickly and easily make most touchpad only games work so quickly and easily.
[Shield Android Development] Steel01:
The problem is that Nvidia's touch mapper is mostly in the stock framework. That's code I don't have access to and even if I was interested in trying, I don't have near the time needed to try and recreate it. And tincore is still an option. I know it's a major pain to set up, but it does work.
[Shield Android Development] JazzMartian:
Gotcha. What a shame. I guess Tincore Mapper it is. It seems like something that probably is really awesome, once you invest the time into learning it. There's probably way more in depth options and things you can do with it, than Nvidia's mapper (but I'll still miss the ease and convenience lol).
[Shield Android Development] igrik1986:
Hello,

Are there any plans to get Noughat on board of Nvidia Shield Portable?

thank you
[Shield Android Development] Steel01:
Well, good news. I actually got the portable to boot N / 14.1. Bad news. It's a jerky mess. I took the advice of one of the other Tegra 4 devs and stuffed the blobs from the Jide Ultratablet in there. Flipped a couple flags, and voila, it boots. No sound, no touch, and quite jerky. But at least I finally found a graphics stack that works. I can work with that, find out which specific pieces I need to pull of the graphics stack and leave the other Roth stuff in place. Should be able to make it usable. No guarentees on when, but I'll keep working on it.
[Shield Android Development] painkiller_93:
Is it somehow possible in this rom tu use nvidia's shield hub app to use gamestream and geforce now? When you install and run the app those options dissapear from the app. I know I can use moonlight to stream, just curious why it doesn't work on this rom, maybe the app detects that it's not an official firmware and disables it or some libraries missing?
[Shield Android Development] fr500:
Try installing nvidia games from google play.
[Shield Android Development] fr500:
Yeah tincore mapper is a pita :p the stock nvidia mapper is way easier.
[Shield Android Development] danny_boi:
For the these two platform, which do I download? Cause last time I tried to update, the device was bricked and somehow magically started up today and went back to thinkering with my shield lol

i'm currently on android 6.0.1 with CyanogenMod Version 13.0 Nightly build

Root addon : https://download.lineageos.org/extras

Google Apps : http://opengapps.org/
[Shield Android Development] 50up3r9uy:
What's different between this and CM13?
[Shield Android Development] Steel01:
Lineage is the continuation of CM. No one is working on CM anymore.

[MENTION=5752780]danny_boi[/MENTION]: Unfortunately flashing from CM to Lineage official builds will require a wipe due to a change in signing keys. Then you want the 13.0 arm su zip and one of the arm 6.0 opengapps packages. I personally use micro, which I also believe is the largest that will fit on this devices small system partition.
[Shield Android Development] marvi0:
Hello about to flash this rom and wanted to findout if the shield hub works as this is not mentioned when I searched. Does installing nvidia games from Google play work please?
[Shield Android Development] painkiller_93:
You can install the app from the play store but it won't show you the options to use gamestream or geforce now. If you want to use gamestream you can install moonlight app.
[Shield Android Development] Blash85:
I just flashed latest TWRP (3.1.0) and touchscreen doesn't work, wtf.. do I have to go with the old version?
[Shield Android Development] ManiacDC:
I had the same problem, I had to use 3.0.0.0 from the multirom. I think 3.0.2.0 worked too.

Also, I just installed the latest nightly (4/9) yesterday (boy was that an exercise), I'm having a few issues:

1. So I set up a pin on my Shield... the lockscreen doesn't show 0 or the icon to accept your input. I had to hook up an external keyboard to get back into my Shield.

2. Installing SuperSU kept my device from booting. Certain root programs require SuperSU specifically. Is there a version of SuperSU that works?

Thanks!
[Shield Android Development] Steel01:
I haven't really tested encryption on this device. Shouldn't be any reason for it not to work, though. If there's a aspect ratio problem on the pin entry screen, I'll try to look into it. But honestly? Why would you want encryption and pin entry on a clamshell gaming device?

SuperSU is not supported by LineageOS. We cannot control external projects and will not attempt to support them. Raise the issue on the SuperSU side. However, we do have a su add-on zip that works in all cases I've ever needed. If that doesn't work, then an issue can be reported.

TWRP issues should be talked about in the appropriate thread.
[Shield Android Development] ManiacDC:
I didn't use encryption, just a pin lock. I do have my google account on there - gmail, hangouts, etc. If it ever gets lost, I'd rather that information not be easily accessible.

Regarding SuperSU - OK thanks! I worked around the issues I had anyway.

I posted about TWRP in the TWRP thread, thanks!
[Shield Android Development] ManiacDC:
Another thing I've noticed is that there doesn't seem to be any support for the GPS in this LineageOS build? I tried a few GPS apps and they said there is no GPS present in the device (with location set to device only and location access granted). Thanks!
[Shield Android Development] fr500:
IIRC the shield portable doesn't have a GPS
[Shield Android Development] ManiacDC:
It does, you can find several threads referencing it:

https://xdaforums.com/showthread.php?t=2436482

https://forums.geforce.com/default/...ps-acquisition-seems-slower-after-59-update-/

https://forums.geforce.com/default/topic/572488/gps-software/
[Shield Android Development] Blash85:
I personally used it as navigator once (Google Maps navigation), when my phone was broken. It took some minutes (yes, minutes) to lock, but worked beautifully.
[Shield Android Development] marvi0:
Hmm everything else working fine apart from geforce. Strangely on my nvidia shield tablet, running a build by Bitobsession on a 6.0.1 rom geforce works fine. Any future chances at all of trying to get geforce working please?
[Shield Android Development] ManiacDC:
From what I recall, the problem is that the Shield Portable support was removed from the Marshmallow version of the Geforce app.

Steel01, I ran into another issue. The HDHomeRun TV app has no sound when used on the Shield Portable with this LineageOS build. It does have sound with the stock rom. Video works fine. Do you think this is an issue on your end or HDHomeRun's end (I don't see reports of this anywhere else)?

Also, I cannot seem to wake up the Shield with an external keyboard hooked up via the OTG adapter. I always have to walk up to it and hit the button (I'm using it in console mode).

Thanks!
[Shield Android Development] ancapgamer:
Just chiming in, I'm enjoying the build quite nicely, it generally works fine for what I mainly used my SHIELD for (emulation 99% of the time), but it DOES seem to have one small issue for me where, when I wake the system up from being suspended, the framerate for the entire system seems to drop significantly, to where every game I play on it just looks flitchy. It's not emulator-specific, as I'm still experiencing it even when browsing system setting or using the internet, and it's not that the device is processing slowly, because all games still run at full speed, it's just the screen is having trouble displaying enough frames per second to show them off. Restarting seems to fix it, but it only lasts until the next time I close the lid and suspend it again - after that I have to restart her again to get her running at full speed again.

Not a deal breaker, I can work with it, I just wanted the issue reported.
[Shield Android Development] fr500:
yeah I have experienced that too
[Shield Android Development] ancapgamer:
Addendum: after some tinkering, I managed to find a solution, though for the life of me I don't know why it would work this way. Apparently the latest version of TWRP (3.1.0-0) was causing it, because flashing to 3.0.2-0 seems to have fixed it. No idea why it would be like that, but I'm happy to have my emulation machine back at full performance.

Thanks for all your hard work, guys, there's lots of little guys like me that really appreciate it.
[Shield Android Development] ancapgamer:
Further addendum: apparently "fixed" is the less accurate term, it's more like "diminished." I still have it pop up every now and then, but it's infrequent now, and when it does occur it's not as severe. Sorry for the excess posting, I didn't mean to use up so much page space when I started out to report this issue, I've just been discovering it as I go along.
[Shield Android Development] DucaConte81:
Can i use the nvidia controller with this rom?
[Shield Android Development] 1amon_:
Hey, wassup? And what's good with the 14.1 version? Let us know. About that nougat support thank you for your rom and work :svetius:
[Shield Android Development] Steel01:
The controller can be used wired no problem. There's a post on the tablet forums that I believe I referenced here already that explains a command line method to pair a wireless controller. Just haven't made an app to handle that in a user friendly manner yet. So the answer is technically yes, but not usably.

14.1 is dead in the water as it stands right now. egl_bad_alloc on home screen display. I had something work once, but I haven't been able to reproduce since. I honestly have no clue what it's doing. So, I wouldn't hold much hope for the Portable getting any support past M. I'll probably take a shot at O, but if N wasn't happy, I seriously doubt O will be any better.
[Shield Android Development] danny_boi:
how would I do a complete wipe? at the moment, CM is just booting and just Optimizing apps on and on and I can get into TWRP and thats about it
[Shield Android Development] danny_boi:
never mind, I got it back to stock using this site. Back to square one lol

http://nvidiashieldzone.com/the-nvidia-shield-portable/tutorial-restore-to-stock-image-port/
[Shield Android Development] npjohnson:
Hey man! So, I work on Molly (the ADT-1), which is one of the only other Tegra 4 devices. We may be able to help each other.

We had to hack up EGL to make it work with MM, and I've heard the hack we used applies to N as well. I may be able to help you with that. We use dmitrygr's gl hex edit to get our GL blobs to work on MM.

Feel free to take a look at Molly's device tree if you think that'd be applicable to you. Its in the git organization below (we called it libmhax).

But, I also pose a separate question, if you would, would you take a look at our kernel repo? Our kernel source (https://github.com/adt1-dev/android_kernel_google_molly on branch cm-13.0) builds/boots with 6.0.y ROM's, but as for 7.0+ it refuses to boot (Continual services being killed, which I have a hunch is SE Linux related). I am at an utter loss why our services refuse to start correctly.
[Shield Android Development] fr500:
I reinstalled the rom, but I still get that half speed issue all the time, not sure how to overcome it.

Hope everything is good with you [MENTION=1416222]Steel01[/MENTION]
[Shield Android Development] Steel01:
Half speed issue? Remind what that is again? I haven't used my portable much lately. All I've seen is the boot loop issue where dexopt seems to corrupt the graphics stack. Really wish I could fix that...

The last nightly should have included my change that reenables geforce now and game stream in the nvidia games app. However, some of the libs still won't load correctly, so it doesn't work. Or at least, now doesn't, can't test local. But I presume it'll have the same issue.
[Shield Android Development] fr500:
Sometimes after letting it idle for a while, it becomes slooooow. As if it was running at 30hz.

Have you never seen this?
[Shield Android Development] Steel01:
Oh, that. Hmmm... I haven't run into that, no. But my recent use cases has just been video playback, so I might not have noticed. I do have an idea what might be happening, though. When I ported to M, I forced a few things around to use the unified powerhal (with the tablet and console). It's possible I broke something there in the update/back port. Like, it may go to sleep, then never go back to performance or interactive. Or something like that. Do you use any performance monitor? I'd like to know what the CPU clock rate is when you run into the issue. And the CPU governor. I bought that tegra one way back in the day, I'll see about digging that back up and monitoring mine.
[Shield Android Development] mllora81:
I have installed the latest nightly about 6 times. It works fine initially but after I start installing apps I am getting boot loops with optimizing apps. Not sure why. I see danny_boi had the same issue. Anyone have a solution?
[Shield Android Development] danny_boi:
I gave up on using Cm since its unsupported, went back to stock and been working great since. Might stick with stock rom till Lineage gets most of its kinks sorted out.
[Shield Android Development] ancapgamer:
Yeah, I'm still dealing with the boot loop issue, crashing and looping on the "starting apps" screen. If I leave it to work long enough, it'll eventually sort itself out, but that could be anywhere from 5 minutes to 48 hours, during which it's completely useless.

It doesn't happen consistently, but when it does I might as well leave it in a closet and forget I have it.

Recently, whenever it finally does boot, it gives me an error about how Trebuchet has crashed.
[Shield Android Development] astuermer:
How to get Leanback Launcher working on this ROM? I am gonna flash this ROM now to bring back some fun to my Shield :)
[Shield Android Development] Steel01:
Funny you should ask about leanback. I started poking at ATV on here again this week. Have it running fairly well, but there's a couple things that need resolved before I release a build. A) Opengapps tvstock for M is horribly broken atm. Trying to get ahold of the maintainer to sort that out. B) The volume buttons don't work. That's... Kinda important. But for some reason, I can't even get a keycode reading from the built-in one or off the external controllers. I'll have to tinker with it some more. But in general, it seems to be running rather well. And no bootloops yet, though I'm pretty sure they'll still happen on these builds intermittently.
[Shield Android Development] astuermer:
The LineageOS build for the Shield Portable ran quite well for me... I had no bootloops.

It seemed a bit more fluid for me too... I use TV Launcher on it since 4.4 - on official 5.1 (v110) it has some minor stutter, but on Lineage it was quite fluid.

I accidently flashed the StockTV Gapps ZIP the first time and had Leanback launcher :)

It started, but wasn't configurable. Just 6 apps and thats it. Also the recommendations at the top (PlayStore and co.) only included movies - no games or apps.

Great work anyway :)
[Shield Android Development] ancapgamer:
Is there a method or app that I can use to create a log of the boot process? I'd be happy to do it, I'm just not sure how.
[Shield Android Development] ancapgamer:
Never mind - I figured out how to do it. Here's a link to the logcat file - 2 bootloop sequences, each taking multiple loops to finally boot all the way up, plus a crash between the two when trying to open X-Plore file manager after successful boot.

https://drive.google.com/open?id=0BxHs73AGoFpveVNFR0FYdEg3YWs

Edit: after playing with it a bit this morning, I've determined that in my case specifically there were 2 things that were causing my problems, but not specifically what they were doing or why - the stock Lineage zip works fine normally, but when Open GApps is installed, it causes Trebuchet to crash - and also, for some reason I can't fathom - the app "X-Plore File Manager" causes the system to crash immediately, with or without Open GApps, either on installation, or if it does install it will crash the system immediately into bootloop upon being opened.
[Shield Android Development] OneOfaKindDPC:
Hey all,

Has anyone been able to GameStream working? Every time I press play to start a game, mine errors out even though the game starts up on the PC with the Lineage nightlies. If I go back to update 110, it works just fine. I'm reloading Lineage to get the error code (it's 80084194). But when I google it, there is very little information. The best I could find was potentially a slow WIFI connection error code, but I don't see that being the case if it works on 110.

Thanks in advance
[Shield Android Development] Steel01:
I try from time to time to get a workaround going for game stream on M. But still haven't got there. Best I can tell, nvidia removed support for this device in the M libs. The intro videos play fine, but as soon as it tries to load the libs to sync input and audio/video, it all blows up. So no, no official game stream support still. Moonlight works just fine from what I hear, though.
[Shield Android Development] life02:
LineageOS version: I have tried lineage-13.0-20170916-nightly-roth-signed.zip, lineage-13.0-20170909-nightly-roth-signed.zip, lineage-13.0-20170826-nightly-roth-signed.zip with the same results

LineageOS Download url: https://download.lineageos.org/roth

Gapps version: open_gapps-arm-6.0-nano-20170921.zip

Wipe: Yes

restore with titanium backup: No

reboot after having the issue: Yes

Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed: Fresh boot - Apps start crashing (trebuchet, google play services, etc...). Some apps like Moonlight cause a soft-reboot instead of launching. Bootlooping with Preparing apps (sometimes just a few loops, sometimes more).

Is there a more stable version I should be using? Any ideas on what could be wrong? I've done a full wipe each time.

Possibly something to do with Google Play Services update since ManiacDC is having the same issue.
[Shield Android Development] ManiacDC:
I had the same issue, and it just randomly started happening without even updating. I tried updating to no avail. I ended up putting the stock firmware back on.
[Shield Android Development] life02:
Same issues with newest rom: 0923.
[Shield Android Development] life02:
Moved back to CM13 and having the same issues. I think it has to be the Gapps version: open_gapps-arm-6.0-nano-20170921.zip
[Shield Android Development] OneOfaKindDPC:
Same issues here as well, has anyone been able to resolve this?
[Shield Android Development] Steel01:
So, the bootloops don't happen without gapps? Well, I suppose that still lines up. The device bootloops during the dexopt process. Best I can tell, dalvik and the graphics somehow have memory conflicts, so many times when dexopt is working on a large app such as google services, the graphics stack gets corrupted and bootloop. I've spent a long time trying to find a fix, but still keep coming up blank. I'll probably try a few more times to fix this issue, but if I can't get 14.1 or 15.0 to boot, I'm probably going to drop support completely when Lineage stops shipping 13.0 builds.
[Shield Android Development] wwjoshdew:
I also have insane bootloops with latest nightly and nano. Was about to flash back to stock and say screw it, but I might try the Pico gapps and see if it can boot up. Let it sit all day, and it appeared to stop boot looping when I got home. Went to launch an app, then it kept boot looping again. Maybe wait for a new gapps or nightly that stops boot looping?
[Shield Android Development] Steel01:
Okay, so some news finally. Got N booting, and actually stable. Like no bootloops so far. I could probably backport that to M, but I think I'm going to continue focusing on getting N to run better. A ways to go still, like no touch and other issues, but I can fix those. Thanks to the guys working on the adt-1 who finally pointed me in the right direction to get things working.

About to try an atv build and see how well it runs. Considering switching the official builds to atv. What do y'all think? Do you use the normal android stuff on this handheld gaming device or mainly the controller based stuff that works on atv?
[Shield Android Development] fr500:
If it works I think atv may be nicer because of the TV interface and simplified settings.

Does that mean it would work as a chromecast receiver?
[Shield Android Development] Steel01:
I honestly don't know right now. I don't think so, due to needing additional keys. The ATV builds I ran for shieldtablet wasn't working as a cast receiver. I'll try once I get OMX and such working.
[Shield Android Development] 1amon_:
Sorry bro but when you think the next update will be ready I mean the nougat update :angel: or maybe some experimental build?
[Shield Android Development] Steel01:
I couldn't say right now. What I have atm isn't usable for normal use cases yet. Like the hardware video acceleration isn't working among other things. And I've got a lot of cleanup to do to bring Roth in line with my other shield devices, so future updates are easier. This weekend is pretty busy for me unfortunately, so I'd say I won't be able to get a test build out until later next week at best. Can't guarantee even that.
[Shield Android Development] Steel01:
So, I got a tad further than I expected tonight before the weekend goes crazy. These still aren't what I'd consider really usable, but they're at least testable. The main issue I know of is that hardware video decoding still doesn't work. The interface is also rather skippy still, though the atv build seems better than the tablet build. Also, on the atv build, there's no way to turn the volume back up after turning it down with the one volume button we have without using adb or an external controller. But if anyone is interested, here's a couple builds to play with.

lineage-14.1-20171013-UNOFFICIAL-roth-atv.zip

lineage-14.1-20171013-UNOFFICIAL-roth-tablet.zip