yashsingh1/xdaforums huggingface dataset:
[Shield Tablet Android Development] Steel01:
There are no differences in the firmware blobs between wx_na_wf, wx_na_do, and wx_un_do. A couple of us did some comparisons and [MENTION=4937137]Bogdacutu[/MENTION] did a hex dump and read through part of it. Runs on any model. Then for CM itself, there's no working difference between na_do and un_do, so I just use the un_do blobs and call both do models un_do. Haven't had any problem with that.

On 12.1 audio: Oh yeah, I do remember something about that now. But I never have encountered the problem myself, so I don't know what to do about it. If you try again and get the problem, I can try to follow exact steps to try and reproduce it. Maybe you could load up multirom and get the best of both: stock and CM. That's what I have, though I haven't booted stock in some time now. Only kept that for Kodi and now that 16b4 fixed the touch issue, I don't need stock except for development reference.

On Netflix: I loaded it up, tried to play a video, and got the crash. It's in the omx libs. Le sigh. That will require some research I don't have time for today and possibly not this week.

On bluetooth: Finding a proper fix is somewhat more involved than expected. But I want to find a solution that is acceptable in upstream CM. So, it might take a bit of time.

On random: Boooting the new kernel with an appended dtb on the 3.1.1 bootloader has interesting results... Like flashy screen and fade to black. So much for that idea. The state the bootloader leaves the graphics device in probably changed from L to M, which means there isn't likely to be a workaround. At least, not with the amount of work I'm willing to put into it. This will probably apply for 5.1 based ROMs on the new bootloader as well.
[Shield Tablet Android Development] philipp21897:
When will the cm13 nightlies go Official?
[Shield Tablet Android Development] Vartom:
Found. In my compilation CM 13. It does not work record video in the Camera application.

[MENTION=1416222]Steel01[/MENTION] in your compilation cameras record video?
[Shield Tablet Android Development] Steel01:
No clue. Still too many moving parts. Bluetooth isn't relsoved, OMX libs apparently have a partial problem, lte support is most likely waiting on Nvidias update for the original tablets, etc. The last one is likely to be the longest out.
[Shield Tablet Android Development] LONGXF:
If you record 4K video,It will not work.Set 1080p or 720p

从我的 NX510J 上通过 XDA Forums 发送
[Shield Tablet Android Development] Steel01:
I can't test right now, it's loaded on my test tablet. But I'd expect a problem with the OMX encoding libs. Got a log snippet of the failure?
[Shield Tablet Android Development] Vartom:
Exactly! Checked, works in 1080 and 720. Do not think that can be the problem.
[Shield Tablet Android Development] Steel01:
The camera and libs don't support 4k. So, we need to find the overlay or permission or whatnot to disable the 4k option in the camera.
[Shield Tablet Android Development] BitOBSessiOn:
[MENTION=6556709]Vartom[/MENTION] [MENTION=1416222]Steel01[/MENTION] do you have touch screen issues (no more touch input) in your build after getting standby... ?

Thnx.
[Shield Tablet Android Development] Vartom:
I do not have this problem.

ps A similar problem was when I used power.tegra.so from nvidia AOSP.
[Shield Tablet Android Development] BitOBSessiOn:
Ok, I will try changing the powerhal module... I understand that is necessary comment a few undeclared POWER_HINT_* variables... Have you faced this prob... ?

Thnx!
[Shield Tablet Android Development] hankovsky.david:
Hi, guys, I am experiencing some lags connected with kworker processes. When shield lags, one of kworker processes is on top of the list of running processes and then it falls down in the list of processes (so it seemes that it will not consume so much from CPU).

Is my idea correct?

If so, do you have any ideas how to dig deeper to find the reason?
[Shield Tablet Android Development] Vartom:
Power hal can look at my tree. https://github.com/vartom/device_nvidia_shieldtablet/tree/master/drivers

Extra variables power_hint can be removed from it. But you can go the other way by adding them to power.h(cm13/hardware/libhardware/include/hardware/power.h)

I followed the path of adding variables. But I'm not sure which way is better.
[Shield Tablet Android Development] Steel01:
If you add them, nothing will use them. But I've already reworked the powerhal for 12.1. And I didn't see any real changes to 13's versus what I had already merged from foster.

https://github.com/CM-Shield/android_hardware_nvidia_power
[Shield Tablet Android Development] Vartom:
I still think the use of these power hint. POWER_HINT_VSYNC received minor change.
[Shield Tablet Android Development] LONGXF:
I have a problem.When play some Games,which show TouchScreen at starting.Strangely,Touching is no work.Games like Talos principle and Ring of chaos 3 both have the problem.What's more,5.1.1,6.0.1,both have the problem.

从我的 NX510J 上通过 XDA Forums 发送
[Shield Tablet Android Development] Steel01:
Yes, this is unfortunately a long time known issue on all aosp based roms. It also happens on Nvidias aosp builds. I asked [MENTION=3869474]agrabren[/MENTION] a while back, but the difference between stock and aosp wasn't clear enough for a quick fix. I presume there's a difference in the framework some where that the raydium blobs expect, but no one knows what that is. If we ever figure that out, the devs will implement the fix asap. That may never happen, unfortunately.
[Shield Tablet Android Development] Steel01:
I unfortunately don't have the time to debug this further right now. But thanks for the pointer, I'll reference it when I do have time to hunt the lag. There's also normally log messages about memtrack when the tablet lags, making out of memory a likely culprit.
[Shield Tablet Android Development] hankovsky.david:
Thank you for your quick response. Will it be helpful for you to send you any log messages when the tablet lags? If so, how can I get them? Or where could I find any information how/where to get them?

It's not so laggy after I use Greenify for most of apps which I don't use so often. But it would be nice, if I could keep them alive and have them start faster.

THX in advance.

David
[Shield Tablet Android Development] LONGXF:
I searched ,And someone told it is caused by lost layer.Ehh...Do you know layer?In Chinese it is 图层.

从我的 NX510J 上通过 XDA Forums 发送
[Shield Tablet Android Development] Steel01:
Ummm... The only thing I can think of right now is to check logcat when it lags. See if memtrack is mentioned. If it isn't, you might have found a different reason for the lag than the one we know about.

I don't think layer is the correct word. I'm terrible at languages, though. Lucky to keep my native one straight. From what I can tell, it's a mismatch in an enum, or list of constantants. Stock has some entries that aosp doesn't, so when an app tries to activate touch in a specific low-level way, the OS mismatches and thinks the touchscreen is a trackball.
[Shield Tablet Android Development] LONGXF:
OK.So it is difficult to fix .We even don't know what is the problem.

从我的 NX510J 上通过 XDA Forums 发送
[Shield Tablet Android Development] BitOBSessiOn:
Finally, touchscreen seems to be fixed... using [MENTION=6556709]Vartom[/MENTION] 's approach, commenting undeclared POWER_HINT_* values. BT also seem to work, so I will prepare a public Bliss6.0 BETA for testing.

Thnx a lot to [MENTION=1416222]Steel01[/MENTION] and [MENTION=6556709]Vartom[/MENTION] for their work.
[Shield Tablet Android Development] hankovsky.david:
You were right. When tablet lags, Logcat shows few dozens of "tegra_memtrack_hal: Error: Reading maps file failed unexpectedly." Is there any known solution?
[Shield Tablet Android Development] Steel01:
Not yet unfortunately. The path it complains about does exist and appears to have proper permissions and selinux context. We also do not have any source to the memtrack module, so we can't track down and fix it from that direction.
[Shield Tablet Android Development] Steel01:
Think I got the bluetooth bug fixed. Just need to run a new userdebug build overnight and I'll release another testing build tomorrow.

The lte modem isn't coming along as easily. rild is exiting with no logged reason and I can't figure out why right now. If I can ever get a hint, I'd hopefully be able to fix it.

Edit: Fixed Netflix as well. Well, technically anything that uses the aac codec. Restarted my build to get that in as well.

Edit 2: Well, it finished before I crashed, so here's the release. Only problem I know of is missing modem support. Any others, please report.

cm-13.0-20160109-UNOFFICIAL-shieldtablet.zip
[Shield Tablet Android Development] :
What TWRP should i use?
[Shield Tablet Android Development] Vartom:
I found on the basis of what has appeared in the Camera application range of 4K. This permission is written in the file media_profiles.xml. The value timelapse2160p and 2160p.
[Shield Tablet Android Development] hankovsky.david:
Unfortunately, it didn't boot for me.

It stayed on nVIDIA logo screen. :(
[Shield Tablet Android Development] Trafalgar Square:
Bootloader

You must upgrade you bootloader:

[UNOFFICIAL][Guide] Update Original Shield Tablet to Android M (6.0)
[Shield Tablet Android Development] hankovsky.david:
well, it seems to be more complex process to update my K1 to CM13, so I'll have to wait as it is my main tablet for dayly use :(
[Shield Tablet Android Development] Vartom:
Enough to make ->

Step 3: You will need to flash the Staging Blob downloaded from above. In a Command Prompt (or corresponding Window, type "fastboot flash staging blob.img"

And oll.
[Shield Tablet Android Development] hankovsky.david:
And will it also work with CM 12.1 after flashing it?

e.g. after restoring my dayly used ROM
[Shield Tablet Android Development] Vartom:
No. You will have to change again blob(from FW stok 5.1.1). Before going back to CM12.1.
[Shield Tablet Android Development] ilko83:
any fix for the glitching sound ven playing videos>?
[Shield Tablet Android Development] teachmeluv:
Where can I find this blob for getting back to 5.1.1?
[Shield Tablet Android Development] Steel01:
There's a flashable zip in the OP.

Alright, didn't have time last week to clean stuff up for pushing to the official repos. So, I'm hoping to get to that this week. And will need to update the install documentation to make sure people know they have to update the bootloader. I don't know if I will switch nightlies over or not, though. Missing lte support is a big problem, especially for my use case. Though, I can work around it for a little while by tethering to my phone. Those with the lte model, what do you think? Should I stick with 12.1 and lte support on official nightly builds or go to 13.0 without it? LTE support will come at the latest when Nvidia release the update for the original tablets in either case.

On the audio problem (wierd intermittent screeching noise): I actually ran into that this last week on my latest (which really isn't all that recent...) 12.1 unofficial build. So unfortunately, it seems that was not fixed. I have no idea what causes it right now. Once 13 goes stable, I will try to do more testing to see if the problem still exists there.
[Shield Tablet Android Development] gqukyo:
I would love LTE also but the official nightlies work for LTE so I'd rather have MM as stable as possible as soon as possible. Who knows when Nvidia will actually release MM for us. Don't know about others but I can tether my phone also.
[Shield Tablet Android Development] philipp21897:
Couldn't you release a final Stable cm12.1 version for the users who want to use LTE and start switching over to cm13 nightlies for the rest? I think this would be the best for everyone :)
[Shield Tablet Android Development] Steel01:
Whew, this week of work has been hectic, so I haven't been able to do much. Sorry for the delay. But the next couple weeks are probably going to be much of the same. I'll see what I can do when/if my brain isn't completely fried.

The little I have done consists of making a CM13 build with selinux enabled. It boots and seems to run fine, but parts of the CTS run I did were failing enmasse. I suspect a passing cm bug, but I haven't had time to rebuild and rerun the test yet (a full CTS run takes 10+ hours). Once I get a complete run with no fixable problems and have the chance to rebuild the tree like I want, I'll be pushing to official. I like the suggestion about making a single 12.1 stable build for those that want/need lte support, so I'll look into that. No idea if I'll be able to make the February date, however.
[Shield Tablet Android Development] teachmeluv:
Is anyone else missing the weather in the notifications bar? It's activated but I can't see it ?
[Shield Tablet Android Development] hankovsky.david:
No, I can see it. I have 12.1-20160119-NIGHTLY build.

Which one do you have?
[Shield Tablet Android Development] teachmeluv:
The latest Nightly from 23.01.2016
[Shield Tablet Android Development] Namaless:
I complete the download now, after installed i reply

With 20 and 23 not see..

---------- Post added at 02:25 AM ---------- Previous post was at 02:12 AM ----------

Damn... Now I see the 26! I download and install but nothing related to this bug so I don't this is fixed, but I will check ?
[Shield Tablet Android Development] teachmeluv:
Still not present on the newest nightly. It really is no big deal than just a hint. I can live without that.
[Shield Tablet Android Development] Namaless:
Me too, btw I see the widget with meteo not working too, so I think for this because we not see this on the notify panel, btw I can stay without :D
[Shield Tablet Android Development] Namaless:
Today I check the status bar and I see the meteo informations, so I think the problem come from the service and not from the rom, so the meteo working fine with the latest (i think working fine with prev versions) :)
[Shield Tablet Android Development] teachmeluv:
Latest nightly causes random reboots on my device (32GB version). With version from 2601 there was no problem
[Shield Tablet Android Development] gqukyo:
I gave up on the latest cm12.1 roms, for some reason or another it's lagfest most of the time. Went back to just plain old stock which wasn't speedy but at least was stable and consistent. Not sure if this is because I was on MM and went back to LP blobs...
[Shield Tablet Android Development] ToHellWithGA:
I'm bummed the first version doesn't get Marshmallow. CM13 will be a good reason to try again - hopefully without the audio glitch.
[Shield Tablet Android Development] gqukyo:
They promised q1 of this year so it'll be released eventually. I need the LTE so that's the only reason I went back to LP
[Shield Tablet Android Development] Namaless:
Its nice the LP stock but if you not use the gamepad the best are cm12.1 imho

You can try to change the kernel, I have updated to 29 release now :)
[Shield Tablet Android Development] gqukyo:
Cm been lagging for some reason so that's why I don't use it anymore and it's a higher drain than stock. Wasn't like that before for me. Not sure what happened or what changed but too lazy to troubleshoot so sticking with stock until official MM release and the inevitable release of roms that support LTE data.
[Shield Tablet Android Development] Steel01:
Okay, I've been out a while with a crunch time at my job. Still got at least another week of that too. But I'm going try and check out some of these reports. Let's see if I've got them straight:

1. Notification bar weather widget missing.

2. Random reboots on the most recent build.

I'll load up a fresh multirom bottle with the latest nightly and opengapps and try to reproduce.

Back on the audio issue: I did have the problem very obviously while playing Netflix this last week. That was on my old unofficial build. But at the same time, the video lagged. It's very possible this is related to the out of memory lag that affects everything. Now, I tried the same on my most recent cm 13 build and have not seen the problem. However, I don't have much installed or running, so that's not yet a conclusive test.

I have a CTS run going now with selinux enabled. The gles test are failing with bad window parameters just like the last time I tried. That might not be my problem. I'll try to run a game or two to see if it's truly a problem. If not, I'll release another unofficial test build.
[Shield Tablet Android Development] brandon88tube:
OK, it has been a while since I've been on the forums and really need some help here because none of my searching has helped. I'm most likely doing something wrong, but I can't seem to flash any of the CM ROM's to my tablet. I've seen the note about needing 3.1.1 firmware, but I'm not sure how I tell if I have that version or not. I also tried flashing that entire zip to my device and it gave me an error just like everything else I've tried to flash to it. I've been using twrp-2.8.7.0-shieldtablet.img for recovery because the cyanogen recovery is upside down on my tablet and seems to reboot after a short period of inactivity.
[Shield Tablet Android Development] Steel01:
[MENTION=4711677]brandon88tube[/MENTION]: Try the twrp in the official twrp thread here. The one on twrps website is broken and for some reason has not been rebuilt yet. That should work better for you.

CM recovery roots after a while? Huh, means the watchdog timeout is kicking in. That I should be able to fix. The upside screen part, I'm not so certain CM has the plugs for that to be fixed. I'll look at that if I have time.
[Shield Tablet Android Development] brandon88tube:
Thanks for the response. Hopefully it was just because I've been unknowingly using the version of TWRP that is broken; I'll keep you updated.

UPDATE: Was only able to find twrp-20151227-EXPERIMENTAL-shieldtablet-m.img and that seems to get stuck on the NVIDIA logo.
[Shield Tablet Android Development] Steel01:
http://xdaforums.com/shield-tablet/orig-development/recovery-twrp-2-8-7-0-touch-recovery-t3257172

That one. Has a link to a newer build.
[Shield Tablet Android Development] brandon88tube:
Thanks, I had to dig a little, but found the version twrp-2.8.7.3-shieldtablet.img and that seemed to work and allowed me to flash the CM ROM.
[Shield Tablet Android Development] Namaless:
1. It's working without problem on my tab WiFi only

2. No random reboot on the latest official build, so the best have the logcat and the last kernel error before you lose some time with this IMHO.

Take your time man, this is a hobby not a job :)
[Shield Tablet Android Development] Steel01:
Whew, good. If it's not across the board, then I will need some more info. Not certain what could be checked for the missing notification. But for the random reboot, if someone sees it, can you please dump the contents of /sys/fs/pstore/console_ramoops (path from memory, if that isn't exact, it's really close) and post it?
[Shield Tablet Android Development] Namaless:
I see this today with youtube app, but if this is fixed into cm13 I think the best is no lose time to check.
[Shield Tablet Android Development] Steel01:
Nvidia finally dropped the M update for the rest of the tablets. I got a link to the wx_un_do update, so I'm going to start importing the libs asap. Here's crossed-fngers that lte will work out of the box.

However, time constraints still apply, so no guarentees I'll actually get anything working this week.

Edit:

Well, that was interesting... Wifi broke. Throwing errors about couldn't load hal and driver doesn't support etc. Eh? I didn't touch anything close to that... Well, Lte is closer at least. Rild doesn't crash and the device detects sim in/out. But it unfortunately still doesn't actually connect to the network. Mine doesn't at least. I'll poke at it some more tomorrow night. Maybe by then Nvidia will have gotten the open source code released.
[Shield Tablet Android Development] Steel01:
Well, today was a particularly bad day, so I didn't do anything to cm. However, I did carry my test tablet running my latest cm-13.0 private build instead of my normal one. WiFi is fixed after I pulled the new kernel branch. LTE still doesn't connect, though. I'll probably need to hop on CM's irc and ask some questions to figure out that one. Pandora ran smooth most of the day, but it did get killed at one point. Same thing happened to Firefox later as I was listening to a live stream with the screen off. I think the oom tracker went from not aggressive enough on 12.1 to totally overzealous on 13... That being said, I haven't seen audio/video lag outside of Firefox yet, and that one probably wasn't an audio lib or CPU clock problem.

I'll try to get back to stuff tomorrow, pending brain power after work. Still need to merge the new selinux policy changes and do some memtrack digging.
[Shield Tablet Android Development] kindlefire39:
Hey everyone, don't post a lot but thought I might as well. I love cm12.1 but was having error codes from the latest opengapps so I went back about a month with fresh install of latest cm build and my Google apps are downloading. Error codes were in the 900s. Something to do with the latest opengapps I guess. This may have been posted already somewhere else but hopefully this helps someone.
[Shield Tablet Android Development] Nismo_q:
Just installed the latest nightly on my K1. Very smooth, stable, and fast. Video and bluetooth streaming are smooth. Much better than Blisspop 4.0.3 which had so much bugs, slowdowns, and audio glitches. I'm sticking with this one until CM13 is stable.

Also installed the SDFIX.ZIP and all my apps are able to write to ExternalSD. My tablet is now perfect! Thanks to all the moders that made this ROM possible.
[Shield Tablet Android Development] supertory:
where'd you get the Sdfix.zip from and do you know if its working for marshmallow?
[Shield Tablet Android Development] Nismo_q:
http://xdaforums.com/shield-tablet/general/fix-ext-sd-write-support-2-0-lollipop-t2946250
[Shield Tablet Android Development] hankovsky.david:
I believe, that you won't need it for Marshmallow – you can format SD card and your device will use it as internal memory.
[Shield Tablet Android Development] Toby4213:
I have two minor issues with this port of cyanogenmod:

1. It only save the wifi passwords in a kind of random way sometimes it saves them and sometimes not

2. Sometimes it get stuck for a few seconds and that is really annoying

If you guys have an idea how to solve the problem please let me know
[Shield Tablet Android Development] philipp21897:
[MENTION=1416222]Steel01[/MENTION] why aren't you pushing your cm13 sources to Official cm repositories? They seems to be stable enough for starting Official cm13 nightlies :)
[Shield Tablet Android Development] Steel01:
Two reasons. First, I haven't enabled selinux enforcing yet and released a test build. I could probably do that without problem right now. Second, lte doesn't work. That's a big problem for several people. I've been busy with work/life and my small amount of dev time has been focused on the portable and now shield tv. Things are starting to clear up, so I'm hoping to get back to this in a week or two.
[Shield Tablet Android Development] Paolo ponzano:
Where can i download last cm13 ?
[Shield Tablet Android Development] Trafalgar Square:
You can't. There is no CM13.
[Shield Tablet Android Development] Paolo ponzano:
So... On what are you working?
[Shield Tablet Android Development] Trafalgar Square:
Steel01 is working on CM13.
[Shield Tablet Android Development] Paolo ponzano:
:D
[Shield Tablet Android Development] Steel01:
I'm in the middle of a pretty major refactoring of the device tree right now. Splitting off common stuff between shield tv and shieldtablet (and upcoming devices) to make future updates and maintenance easier. Update one device and all benefit. I think I have it back in a usable state. Going to run a build overnight with selinux tonight. If it passes my basic tests tomorrow night, I'll release another test build.

Still haven't gotten to the lte problem yet. That's the one remaining problem before I want to push to upstream CM.