yashsingh1/xdaforums huggingface dataset:
[Shield Tablet Android Development] Steel01:
Charging should match stock. If it's measurably different, there's a problem. The charging values are set in the dtb which is shared between all ROMs.

I was finally pointed in the right direction for Console Mode. I've built and tested and it works great. Only issue is if you unplug the hdmi, the display and touch orientation don't match (90 degree offset), so you have to hunt a bit for the button to switch back. If you're using a controller, this won't matter at all. I'm finalizing the patches tonight and pushing them into the repo, then I'll run a build overnight and upload in the morning. There are several more changes as well that I'll try to detail more in the release post.
[Shield Tablet Android Development] OperationNT:
I had the same charging issue and I also wasn't able to connect my tablet to a PC (nothing detected by the PC and when I try to change USB settings, the settings application was crashing).

In fact, this issue was due to the fact that I made a full OTA restore to 2.2.2 (it includes the dtb parameters). OTA 2.2.2 is made for Android 5.0.x, not 5.1.x.

So if you notice the same issue (no possible PC connexion) in addition to your slow charging issue, you have two options:

- Full restore your tablet to, at least, OTA version 3.1 then install any custom rom with Android 5.1.x (for example, Cyanogenmod 12.1); if your tablet have a Y01 battery and should die, avoid this solution at any cost...

- Full restore your tablet to OTA version 2.2.2 then install only any custom rom with Android 5.0.x (for example, Cyanogenmod 12.0)

I still have a last issue with this ROM, on some sounds played on the tablet speakers, there is an annoying "saturation" effect. I notice that this effect happens very often when AudioFX is enabled (it is not possible to play even 30 sec of any music without having it at least once). It could also happen when AudioFX is disabled if the tablet has too much things to process. Any idea to solve this issue ?

Thank you for your help !
[Shield Tablet Android Development] Michalko5896:
SELinux still in permissive mode..

EDIT: nevermind, I just found out that commit enabling SE Linux is newer than latest build. my bad, sorry.. Looking forward for new build with SE Linux enabled
[Shield Tablet Android Development] BitOBSessiOn:
If you have charging / pc connection issues, maybe you need to update your DTB partition with a DTB file compatible with your current kernel.

More info:

http://xdaforums.com/showpost.php?p=62004266&postcount=584
[Shield Tablet Android Development] rusty.gh:
Thanks, yes I did in fact use an old stock then flashed CM12.1

I have this option now, thank you.

Might try BitOBSessiOn's kernel option first though.
[Shield Tablet Android Development] Steel01:
Alright, new build up in the opening post. This is the first release with selinux enforcing, so please report any new problems. I've done testing for about a week now and have fixed the couple problem I ran across. But with trying to submit to official CM soon, I need to know quickly if I missed anything. I'm running another CTS scan today, hoping nothing new pops up. The list of changes I remember are:

Selinux enabled

App2sd fixed

H264 hardware encoding disabled (yay for the CTS, otherwise I might not have ever noticed this was crashing)

Added console mode app (this also won't be submitted to official due to the changes required, but will remain in unofficial builds)
[Shield Tablet Android Development] oneru:
Working great here! Also, Happy 6 month rom anniversary today. =)
[Shield Tablet Android Development] techwiz24:
Sorry for the extremely late response, never got a notification from TapTalk :/

Anyways, I've replaced my router with a brand new one that offers better coverage for most of the devices on my network. However, it seems the radio in the shield tablet is severely under-powered, as it's 2.4ghz performance falls off much quicker than any other device I own. While signal strength reported via Wifi Monitor is comparable or better than my HTC One M8 in the same location, I only get 0.3/0.01 on the tablet compared to around 15/2 on my phone (Yes, I've checked to see if the units are correct). I've worked around it for the moment by forcing the tablet to only use the 5ghz radio, but that band doesn't propagate throughout my house all that well, and the shield frequently disconnects.

I'm going to try flashing latest stock and then re-flashing your latest build to see if it's possibly a firmware issue (Couldn't find any stand-alone firmware files). I've been meaning to anyways because of the charging issues (from what I've read, I need to flash a dtb or get it from stock)

Thanks for the great work on the ROM btw!
[Shield Tablet Android Development] vitalinya:
Can anyone tell me, is this ROM support display mirroring? Cant find any information about it in this branch.
[Shield Tablet Android Development] Gilbot:
Flashed the latest build and I'll be checking it out how it handles in depth a bit more tomorrow. Used it tonight playing ingress while listening to play music, had nearly zero issues except one: the Facebook app freezes when it encounters video, Facebook is pretty much unusable because of this.
[Shield Tablet Android Development] Steel01:
If by mirroring, you are referring to HDMI mirroring, then yes, it is supported. If you're referring to chromecast, then it should in theory, but I don't know if anyone has tested that.

Yuck, a Facebook problem? I don't (refuse to) have an account, so I can't verify that myself. But I have a friend with a tablet and an account, I'll see if he can reproduce the problem.
[Shield Tablet Android Development] MusikMonk:
I don't have a chromecase, so I can't help there.

But regarding the Facebook issue, I can reproduce a "cannot play video" error when trying to play videos although I don't have a complete freeze. Might be because I have disabled automatic video playback.

Here's a slightly redacted logcat because there was far too much personal info leaked by Facebook for my liking: http://pastebin.com/x57GuTat

There seems to be plenty of errors about decoders.

(Side note, I understand your feelings toward Facebook. I have deleted my account 3 years ago and only just recently created a new one because it was the only way to get in contact with some old friends. It's basically a messenger as far as I'm concerned.)
[Shield Tablet Android Development] Steel01:
Yeah, don't want anything to do with a company/platform whose sole purpose is to gather and sell demographics. Personally, I have contact with people through other means, so I'm not losing much.

Found the problem. It's the aac decoder. I mixed up some changes I needed to make for the portable and tablet. The fix is already in the source tree, but I didn't upload the build since I didn't think it would break much. Oops. I'm working on uploading it now, will post an update once it's done.

For those that don't want to wait and can do a bit of file editing, comment out the eaacp decoder in /etc/media_codecs.xml like so. That should be the only change in the new build.
[Shield Tablet Android Development] MusikMonk:
Well, that was quick. I did the modification manually and I can confirm that it solved the issue on my side.
[Shield Tablet Android Development] Steel01:
And build is up. Hopefully this time, no stupidly obvious problems pop up... I should have caught that.
[Shield Tablet Android Development] Gilbot:
Thanks. I'm not the biggest fan of Facebook, but I also still maintain my account because of family.

Edit: The video play issue is resolved, thanks!
[Shield Tablet Android Development] schlehmil_me:
In latest build with clean flash my SIM pin was not requested after first boot. Finished initial setup and rebooted. Then mobile network is working fine. This behavior is reproducible and wasn't there on build 09092015.
[Shield Tablet Android Development] OperationNT:
Thank you for your help, I will try this; it will allow me to use Android 5.1 ROMs again. However, do I also need to also install the modified "BitO-K" kernel in addition to the custom DTB file or can I keep the default Cyanogenmod 12.1 kernel ?
[Shield Tablet Android Development] Michalko5896:
CM issue, not device bug
[Shield Tablet Android Development] Steel01:
Wow, I missed notifications on a few posts. I'd expect a sim pin problem to be upstream, glad to have confirmation of that. For the dtb question, you should be able to use the dtb with whatever kernel you want.
[Shield Tablet Android Development] Steel01:
Finally got a manual override for the model detection to work. Doing a bit more testing before releasing, though. Once I do, setting persist.cm.shield.model to a model (wx_na_wf, wx_na_do/wx_un_do [both will use un_do], or wx_un_mo) will force the device to come up as that. With that, people that want to use the LTE model as a glorified wifi model can do so on this release. On a related note, wx_un_mo mode (the voice model) boots and initializes on the do model, but even when I compile the dialer and all in, I can't even get the icon to show up... 3rd party dialers send an intent that gets dropped. So I have no idea if it's actually initialized voice capable or fell back to data only. I'll have to do more tinkering and testing.

One other problem/change: video recording through the camera is broken currently. Apparently even though the hardware h264 encoder is broke in some cases, it's less broke than the software encoder is crippled... I hear Android M has a better software encoder, but that doesn't help me right now... This will be fixed next release.
[Shield Tablet Android Development] schlehmil_me:
I cannot find a bug report for this issue. Do you have a link?
[Shield Tablet Android Development] Michalko5896:
I had this issue on 2 more devices.. 17. build is working fine now so I guess you have to wait for dev to update sources
[Shield Tablet Android Development] Steel01:
New build is up in OP. Includes the model override and a few other fixes. Also added in the OP is a link to the latest firmware files. Several reported problems seem to point toward not having the latest bootloader and/or dtb. So, I put together a flashable zip that will update those without having to flash the entire latest ota.

Notes on the model override:

The override is triggered by the persistent property persist.cm.shield.model. It can be set to wx_na_wf, wx_na_do, wx_un_do, and wx_un_mo. The two _do's will end up as wx_un_do since since there is no software difference and no reason to split them. wx_un_mo does boot and theoretically enables voice capability; however, the current lack of dialer support makes it no different from using _do at this time.

Notes on CM submission:

I've got the CTS scan down to 21 failures that either don't seem to be device specific or don't seem to be fixable outside of the blobs. I'm planning on typing up the submission email tomorrow and sending it tomorrow or Sunday. Life permitting, of course.
[Shield Tablet Android Development] Michalko5896:
is AOSP 5.1.1_r13 merged into your build?
[Shield Tablet Android Development] Steel01:
My builds are whatever upstream CM has. I don't specifically keep track, so I'm not certain.
[Shield Tablet Android Development] Michalko5896:
AOSP 5.1.1_r13 was merged into CM on 15.09
[Shield Tablet Android Development] Steel01:
So my latest build from the 18th should have that in it. Can someone verify that the sim lock works correctly on first boot now?

The submission to official CM is in. The wiki page says that could take up to two weeks for review before I hear back. So, back to waiting now. And theoretically there shouldn't be any bugs popping up that I have to hurry and fix. I will try to get new builds up every few days to get upstream stuff, however.
[Shield Tablet Android Development] schlehmil_me:
SIM lock on first boot is working.
[Shield Tablet Android Development] Steel01:
Build updated in opening post. Only upstream changes.
[Shield Tablet Android Development] Steel01:
Here's a fun build for some people.

20150924-EXPERIMENTAL

This build has voice support enabled in the ROM. If you set persist.cm.shield.model to wx_un_mo, the icera blobs theoretically should work with voice. But it does appear more is missing, like the voice firmware. Got some AT errors in logcat when I tried to dial out. However, I was using my data only sim. I'm throwing this up so more people can play with it. Maybe see something I didn't. I'll have the code changes up in a branch shortly. Not gonna put these in the main branch, at least not before I find a way to hide the dialer for the data only models.

On a related note, does anyone have copies of the wx_un_mo otas? I had one, but it got corrupted and now all the links are dead.
[Shield Tablet Android Development] MusikMonk:
The thread's formatting is on the unintuitive side, but I think that MidgetMob has everything mirrored here:

http://xdaforums.com/shield-tablet/general/stock-recovery-images-ota-library-guides-t2988881
[Shield Tablet Android Development] Steel01:
That was one if the threads I looked though. Just checked again, but don't see anything for the voice model (wx_un_mo).

Edit: Got a copy of 1.2 from [MENTION=4937137]Bogdacutu[/MENTION]. I've seen a newer one, if anyone has that, please let me know.
[Shield Tablet Android Development] oppodi:
Can I use it in tetra note 7?

Moderator Note: Off topic.
[Shield Tablet Android Development] ToHellWithGA:
Does anybody else experience audio glitches during video playback? On PBS Kids and Amazon Instant Video there are occasionally undesired sounds which remind me of the sounds made by Transformers transforming from vehicles to robots in the old cartoon. Is there any debug data I could provide to help resolve this non-crashing but obnoxious issue?
[Shield Tablet Android Development] techwiz24:
I've had that happen before, and I noticed it mostly happens when there are other apps running in the background. Try closing them and see if that helps.
[Shield Tablet Android Development] ToHellWithGA:
My only background app is a service - AdAway. I verified that the other profile had no open apps too.
[Shield Tablet Android Development] Steel01:
I'm looking into the audio problem some more now. It seems to be a problem with the cpu underclocking so far that the audio buffer can't keep up. I can't 100% verify that, however. But setting performance mode seems to mitigate the problem. So, I'm trying a build with the min cpu frequency bumped up a bit. We'll see how that goes.
[Shield Tablet Android Development] Steel01:
New build up in the OP. Two things I need tested:

1. Does the audio shriek / stutter / whateverelseitwasdoing still happen? It should be less, but I need to know if it's still possible for it to happen.

2. Is battery usage significantly higher? If this fixes #1, I won't care as much about a small amount of battery loss, but the ratio needs to be known.

For the technical people here, what I did was bump the minimum CPU frequency from 51 MHz to 312 MHz. This can still be changed by the user using tegra over clock or setcpu or similar. But I don't want media issues by default if at all possible.
[Shield Tablet Android Development] EmBoLa.be:
Firmware Update:

If you have not installed the latest stock ota, then some firmware files need updated. The following flashable zips will update the bootloader and the dtb corresponding with the listed stock version. Only the latest one listed here will be supported by recent CM builds.

3.1.1

So this is NOT for YO1 tablets ? or do can someone enlighten me on this. Thx in advanced
[Shield Tablet Android Development] n0credit:
The first build I'm testing is the 2909 so I can't say anything for point 2. About point 1 even if I can't compare it to any previous build I do get audio stutter and the tablet sometimes gets almost unusable / unresponsive, all this occurs fairly often. I get a lot of errors for tegra_memtrack_hal(675): Error: Reading maps file failed unexpectedly. If you need a logcat just let me know.
[Shield Tablet Android Development] Steel01:
A full logcat would be useful. I just checked my tablet and see some memtrack errors on bootup, but not those exact ones. See any context to those could be useful in tracking down what it's trying to access.

Edit: This stuff looks kernel related... So, an additional question: Are you running the stock CM kernel or one of the modified ones?
[Shield Tablet Android Development] Peccoskaify:
My tablet lags as hell after using this ROM ....any idea? :/
[Shield Tablet Android Development] Primetime_de:
Just wanted to try this ROM but as soon as the system starts I get the error that trebuchet stopped working over and over again.

Tried clear data and cache and also wipe from recovery, nothing helped.

Any ideas?

RoW LTE version, I came from 3.1.1 stock ROM rooted.

Best regards

Chris
[Shield Tablet Android Development] n0credit:
It happened to me too, I think the problem is upstream and it was already fixed. The solution in the meantime is to use another launcher.
[Shield Tablet Android Development] Primetime_de:
Hi,

I've a RoW LTE tablet but the SIM isn't detected in this ROM (get the grey "No SIM" status icon).

Stock and also Bliss Pop works fine.

What can I try?

Best regards,

Chris
[Shield Tablet Android Development] Primetime_de:
Anyone?

Any hint is welcome...
[Shield Tablet Android Development] Steel01:
Blast, someone else has seen the sim problem... I had hoped that was a random hardware issue I was seeing. I don't know what's going on, but for me it's intermittent. The sim will be there in boot, will sometimes come and go, then sometimes will disappear until reboot. A couple times it vanished for multiple reboots. But I haven't changed anything related on the device tree lately. Maybe newer builds will work better, I don't know.

I'll run a new build tonight and try to get it uploaded tomorrow. I haven't seen the launcher bug, but hopefully that will fix it for those that are. And maybe it will help the sim issues.

Also, I still haven't heard back from CM. Their website said up to two weeks. It's been over three now. So, no idea what's going on there.
[Shield Tablet Android Development] Primetime_de:
Thanks, I will wait for the new build and give it a try!

Anyway, great job mate.
[Shield Tablet Android Development] Primetime_de:
Just a short feedback:

I'd done several reboots and on the 3rd or so reboot the SIM was detected.

On the next reboot the SIM problem came back.

So it is exactly the behaviour you mentioned.

If you need more input just drop me a line.
[Shield Tablet Android Development] Steel01:
Well, I botched the build. Have been tinkering with CM13 a little and didn't quite get everything set back up for 12.1 before running the build. So, I have a new, hopefully correct, one running now. I'll try to have it tested and uploaded this afternoon, but no guarantees.
[Shield Tablet Android Development] Steel01:
New build is up, hopefully fixes the launcher problem at least. Unfortunately, I've already had a local report that the sim problem persists. That was on a dirty flash, however. Mine hasn't dropped yet, though. Does someone else with the problem have the time and patience to test a clean flash (new multirom secondary or however)? The two of us here don't right now.
[Shield Tablet Android Development] Primetime_de:
I will do a clean flash from scratch on my test tablet in the next hours. Should I use a specific kernel?
[Shield Tablet Android Development] Steel01:
Use the normal CM kernel. That's the only one I can support. Theoretically, the kernel wouldn't affect this, but the possibility cannot be ruled out.
[Shield Tablet Android Development] pjim:
If you need a crash test dummy for CM13, I am at your service!
[Shield Tablet Android Development] Steel01:
That's *if* I ever get it to compile. CM is still in the initial conversion phase. I'm mainly trying to get something compiled so I can see if the lollipop blobs will boot. But yeah, if I get anything to boot, I'll throw up an experimental build for those interested.
[Shield Tablet Android Development] ToHellWithGA:
1. I have not noticed the audio issue since installing that build.

2. I charge between each approximately one to two hour period of use and do not see a noticeable difference in battery drain.
[Shield Tablet Android Development] Steel01:
Hmmm... I think I have a couple times. But it's much less frequent, so it is an improvement.

On the sim issues: It looks like this is also a stock issue. And it sounds like it doesn't affect everyone and is difficult to track down. Nothing is coming to mind for me to be able to fix in CM. I suspect it's either a modem firmware or icera blob issue.

Over the weekend, I got CM13 to display the boot animation. This is great news since it means we don't need to wait on new blobs from Nvidia to get M running. I haven't had much time since, so that's all the further I got. Several things were crashing during boot, so it still hangs at the boot logo.
[Shield Tablet Android Development] davidplz:
CM update

I have checked CM wiki and Nvidia Shield Tablet appears now as an unofficial device with links to this thread and github (look into Devices->unofficial ports->Nvidia)
[Shield Tablet Android Development] Steel01:
Well, CM13 boots. And for the week after the aosp release, it's running pretty well. That being said, upstream is still in a major state of flux. I had to disable stagefright-plugins to get it to compile. Also, it really doesn't like the audio lib. It also won't install as a multirom secondary atm, but it will install to primary just fine (likely a twrp-multirom issue). Also, the one open-gapps release for 6.0 that I found force-closes on boot and renders the system unusable.

But for those brave souls that like playing with this kind of thing:

cm-13-20151021-EXPERIMENTAL-shieldtablet.zip

This has only been marginally tested. Wifi works, but my test tablet doesn't have a dedicated sim card, so I don't know if that works or not. If there's an obvious hardware related problem (like, sim or gps doesn't work), go ahead and report it, but outside of that, it won't do much good until upstream settles down a bit.
[Shield Tablet Android Development] lch920619x:
This is amazing work, 2 weeks after aosp drop and we have a near daily driver build.

The potential of the device is promising with great devs like you.

Now who cares if nvidia gives us the official 6.0 or not?
[Shield Tablet Android Development] Steel01:
New 12.1 build up in the OP.

For 13, I really didn't have to do much to get it to boot, just a kernel patch and a few small device changes. Most of the kudos should go to the CM team for getting stuff in order this quickly. That being said, there are a couple problems I'm seeing that could be real pains to work around. Namely, the audio and OMX libs. No sound and no hardware accelerated video (and by extension, game streaming) would be huge problems.
[Shield Tablet Android Development] lch920619x:
meaning we still need to wait for nv to release the relevant libs or drivers targeted 6.0?
[Shield Tablet Android Development] Steel01:
Quite possibly. I haven't experimented too much yet, so I don't know for certain. Once upstream CM settles down a bit, I'll poke at it some more.
[Shield Tablet Android Development] sabret00the:
Amazing news on 13. Why didn't 12.1 become an official CM release?
[Shield Tablet Android Development] schlehmil_me:
No idea but I have the same issue. Reboot fixes it for a short period. Closing all apps in the recent list too. BlissPop seems to be not having this problem.