yashsingh1/xdaforums huggingface dataset:
[Shield Tablet Android Development] Steel01:
I wish I knew why. Most of the time, I don't have any lag at all. Like right now, posting using Firefox with several tabs open. Been switching back and forth between gmail and hangouts as well. No lag at all. But at seemingly random times, things will almost grind to a halt.

Some reports point to out of memory problems. The logs spam a bunch of stuff about not being able to access nvmap files (which incidently actually are there). But I haven't been able to track down why yet. Bumping the minimum CPU frequency seems to help a lot and has been in all my recent builds. I'm about to go ahead and push that officially. If anyone sees a pattern in the slowdowns, please mention it.

As for official CM, I'm still waiting on a response. I sent another email to ciwrl last week, but haven't got a response to that either. No idea what's going on.
[Shield Tablet Android Development] supertory:
what minimum Cpu value did you use ?
[Shield Tablet Android Development] Steel01:
That was in my post a couple weeks ago.
[Shield Tablet Android Development] Steel01:
New build up in the first post. I tweaked a couple audio settings that might have actually solved the audio problems. I've run a couple videos that used to always give me problems and haven't had a glitch yet, even when the input stream lagged enough for the video to skip. But that's still a very low test count. I need people to stress test this build and see if anyone can get the audio to screech or any of the other bad stuff that was happening. If this works well, I might be able to drop the cpu min freq patch.
[Shield Tablet Android Development] grv00711:
Multiple Network Fibers are down in the QC Data Center causing a major outage. This will cause the site to be slow or not load. A fix is underway. This outage effects all 5 QC servers including the one that hosts the site. We are running on a backup fiber now. We apologize for any bad downloads that were caused by this outage. Some files may show no mirrors found during this outage. Unfortunately this is beyond our control. any other links for cm-12.1-20151031-UNOFFICIAL-shieldtablet.zip and shieldtablet-firmware-311-update.zip ..have the gapps
[Shield Tablet Android Development] Steel01:
Oh, lovely. No, I don't have any mirrors at the moment. If AFH is still showing no mirrors by the time I get back to my dev machine tonight, I'll look at putting the build up somewhere else until AFH is back.
[Shield Tablet Android Development] Peccoskaify:
Using BlissPop now, same problem i think ever worse.
[Shield Tablet Android Development] Steel01:
Looks like AFH is getting things back online. Whew, glad to see that. I really don't want to go to the trouble of mirroring everything I've currently got hosted there.
[Shield Tablet Android Development] grv00711:
nice work on audio problems!! i use the tablet as audio playback device with [Audio Mod] eXtremeBeats..and other mods ..newest build elimated the audio issues when having pandora or other music app open ..thanks ..!
[Shield Tablet Android Development] Steel01:
New build up in the OP. This build has an experimental powerhal implementation. I *think* some of the lag issues might come from mis-interaction between CyanogenMod and the stock powerhal lib. But the more I look at it, I'm not so sure. It does seem that battery life should be better once I get this finished. However, I haven't implemented low-power mode yet. But I'd still like to get some stress testing of this build to see if the lags are still as bad. I don't expect the out of memory problem to be any different, unfortunately. Still don't know what to do about that, unless I can magically come up with memtrack code to tweak and compile.
[Shield Tablet Android Development] Steel01:
Alright, final pieces just went in. The official nightlies should start rolling tonight.

These builds have the new powerhal, so I'd appreciate some feedback on that. They will not have any of the Nvidia apps built in, namely console mode and wireless controller support. However, there is a change in review that should let me ship console mode soon. I doubt the controller will ever be supported due to the invasive framework changes needed. Hence, I'll periodically release unofficial builds here with that support.
[Shield Tablet Android Development] sabret00the:
Brilliant work, can't wait to flash an official build
[Shield Tablet Android Development] Steel01:
Alright, first nightly is done. Hasn't quite propagated to the website yet, but check the link in the OP in a few minutes and it should be there. CM recovery will be there, but note that it will be upside down (dunno how to fix that). Otherwise, it works fine.
[Shield Tablet Android Development] Trafalgar Square:
Very cool

Thank you for Official Nightlys. Will flash Nightly every day :D
[Shield Tablet Android Development] BenjiHansell:
Questions, questions, questions!

I've never seen an unofficial CyanogenMod project suddenly get accepted as official before. It's great that it's happening, but it leaves me with loads of questions:

1. How was this work was upgraded from unofficial to official?

2. Did someone at CyanogenMOD contact you or the other way around?

3. Did they insist on you modifying the code to fit their guidelines?

4. Will there be snapshot builds in the foreseeable future?

5. Are there more developers at CyanogenMOD contributing to the Shield-specific code now?

6. Do you still get the final say on which commits are accepted?

7. It looks like both your Shield Portable CM and Shield Tablet CM projects have been officialised. Is this going to happen to the Shield Android TV CM project too?

I understand that you're probably very busy right now migrating at least two projects. Keep up the good work.
[Shield Tablet Android Development] Trafalgar Square:
Very good nightly

Gesendet von meinem wx_un_do mit Tapatalk
[Shield Tablet Android Development] sabret00the:
Surely this thread should be moved to Original Android Development now?

Also are these steps https://wiki.cyanogenmod.org/w/Install_CM_for_shieldtablet actually correct?
[Shield Tablet Android Development] aceclift:
I agree, it should be since he is now maintaining the nightlies on cyanogenmods website

And yes those are the correct steps shown on cyanogenmods page, just ignore the step about unlocking the bootloader in the developer settings.
[Shield Tablet Android Development] ToHellWithGA:
The audio glitch problem has returned in the first nightly. The only app running other than AdAway and OpenGApps is PBS Kids streaming videos. I'll download some Amazon videos later and determine in the coming days if the same behavior is present with local files.

Should concerns still be mentioned here or would you prefer CM bug reports?
[Shield Tablet Android Development] Steel01:
As far as I know, the bug reporting system is only for builds marked as stable. I don't have any of those, so please just report problems here.

The audio problems came back?! I'll have to look at that and try to replicate it. I haven't heard it yet.

I honestly don't care where the thread is. It isn't much original with me, most of it is the main CM devs, I just make it run on this device.

[MENTION=1095532]benjih[/MENTION]ansel:

Technically speaking, there isn't any difference between an unofficial and official cm build. If stuff was changed in a downstream project like mine was, it wouldn't be CM anymore, it would be a derivative.

1/2. Once I was certain my ports were stable enough, I requested for the ports to become official. CM has a page on their site about that.

3. Of course. Any project has to keep standards or it's chaos. That said, it's pretty loose. No two device maintainers keep their trees exactly the same.

4. Snapshot? As in what passes for stable now? I personally don't see a need for them. They are opt-in by each maintainer. I'm not going to unless there's overwhelming feedback requesting them.

5. No, still just me. There are other tegra devs, but no one else specifically for these. I'd love some competent help, though...

6. Any of the Adkins could push code to the device tree, but I don't think they ever do. So, realisticly speaking, yes. However, all the general code (init, zygote, surfaceflinger, etc, etc, are all maintained by other people.

7. Hopefully? But I don't even see that an unofficial status yet, it's still an experiment. Hopefully in the next week or so, I'll have more time to get back to that. But right now, it's still a fairly broken mess.
[Shield Tablet Android Development] C0BRA01:
Just wanted to say congrats on official status! :)
[Shield Tablet Android Development] Khamhui:
Hi, I have a question. If I install this ROM on my Nvidia Shield, will it avoid the dactivation thing because I just received the new one. I want to offer it to a friend of mine for Christmas so that would be great. Thank you and keep up the good work ! I was looking for an official build of this one :)
[Shield Tablet Android Development] Steel01:
That is correct. To be safe, do not boot into stock on the old one again. Boot directly to recovery and sideload (or external SD or whatever) CM. The 'kill switch' is triggered by part of the stock OTA utility.
[Shield Tablet Android Development] Khamhui:
I don't get this part. From what I know so far, If I install a new rom, as I do with my OPO, the previous one will disappear, isn't that the case ? When I boot my OPO, it has always gone to my new rom. I don't use MultiRom.

Thank you for your quick response !
[Shield Tablet Android Development] Steel01:
It was just a warning to not use stock again before installing CM. Sorry for not being clear.

More detailed: It would probably be safe to use stock up to the point the new one is first turned on and connected to the internet. However, some people have had the kill switch deployed early. There's more info on that in the threads in general discussion. But once CM is installed, you're safe. Just don't go back to stock later without installing Bogdacutu's kill switch killer.
[Shield Tablet Android Development] Khamhui:
Okay, I get it now !

I won't go back to the Nvidia Rom ever ahah

My friend doesn't mind not playing games. He just needs a tablet for work and do casual stuff!

Thank you for your assistance ! Have a good day/evening/night! :)
[Shield Tablet Android Development] nielsscholte:
I can't get the Shield controller to work with the Unofficial CM build... The Nvidia logo keeps flashing but nothing happens... Can anyone help me?
[Shield Tablet Android Development] Khamhui:
Okay. So on another post, I said that I was unable to unlock the bootloader but I did it after a very long time.

Now, I want to install the rom. First, I need to do a Factory Reset but I have a problem. It's all red, it cannot mount /data apparently.

This what I get :

E: Could not mount /data and unable to find crypto footer

E: Unable to mount '/data'

E: unable to recreate /data/media folder.

E: unable to mount storage

E: unable to mount /data/media during GUI startup

E: unable to mount /data/media/TWRP/.twrps when trying to rad settings file.

E: unknown MTP message type: 1

And the list goes on!

Any ideas on how to fix this ?
[Shield Tablet Android Development] Steel01:
The controller support is very finicky unfortunately. More information on that is in the shield apps thread. Once the controller pairing has started to fail, the only way I've gotten it to start working again is a full wipe and reinstall. But that's not even a guarantee. I hear mutterings that the situation regarding that will improve semi-shortly, but I'll believe that when I see the code.

[MENTION=7008418]Khamhui[/MENTION]: That's a twrp issue, not a CM one. One thing that might help is to boot into your ROM once, then reboot to twrp. I've seen some oddities with booting directly to recovery immediately after fastboot erasing (which happens during unlock) partitions.
[Shield Tablet Android Development] Khamhui:
Hi ! The problem is that I don't have a ROM now as I tried to install CM over the stock ROM (I thought that it would fix the issue ... don't know why). So now, I have a bootloop. I have the Nvidia screen and it launches TWRP, it tries to run OpenRecoveryScript, fails and reboots again. I should have wait for an answer ahah
[Shield Tablet Android Development] Steel01:
If you trigger recovery manually now, can you wipe all partitions and reflash?

If all else fails, you can boot to the bootloader and flash the stock recovery image, then start over. I wouldn't think you'd have to, though...
[Shield Tablet Android Development] Khamhui:
I can go to Recovery but I can't wipe and reflash as I get error messages.

Should I flash using flashboot mode ? or adb ? But I don't know the code to write..
[Shield Tablet Android Development] Steel01:
Download the latest version for your tablet edition from here. Flash everything via fastboot. Boot it up, but don't connect to WiFi (in case of kill switch). Presuming that worked fine, reboot to bootloader and flash twrp back, then boot to recovery and continue as normal (wipe everything, flash cm and gapps).
[Shield Tablet Android Development] Khamhui:
Okay so I found a solution. I went to "'wipe" and instead of doing "Factory reset" I chosed "Fortmat Data". Now, "Data" is mount and I am trying to flash CM so I will edit this post if it works.

Question; what kind of gapps should I choose? ARM or ARM64?
[Shield Tablet Android Development] Steel01:
Good, that sounds better. And this is arm. There's only a few arm64 devices out like the shield console or the nexus 9.
[Shield Tablet Android Development] Khamhui:
Okay I see. I thought it was ARM64 as the Tegra K1 is a 64bit processor (I think). Thank you so much for your help !
[Shield Tablet Android Development] Steel01:
You talking about the K1 or the K1? :P There's two versions, actually. This is a t124 device, which is a cortex-a15, 32-bit. Then there's... I think it's the t132, aka Denver, which is in the nexus 9, 64-bit.
[Shield Tablet Android Development] nielsscholte:
Okay well let's hope it'll work soon because I love CyanogenMod ;)
[Shield Tablet Android Development] grv00711:
so after flashing latest nightly ..back to the audio stutter ?
[Shield Tablet Android Development] Steel01:
That doesn't make any sense... The only difference between the nightlies and my last unofficial should be dropping the minimum frequency hack which shouldn't be needed anymore. But with two people reporting it...

This shouldn't make a difference, but have either of you done a fresh install or factory reset? Wouldn't think anything from the unofficial builds would interfere, but I suppose it's remotely possible.

To those wondering why there's only been one nightly build, it's because CM was pushing stable builds. Should be a new nightly today, like within a two or three hours.
[Shield Tablet Android Development] grv00711:
i will check my audio mods ..proplem could be there ..most likely ..thanx
[Shield Tablet Android Development] Brigadir120370:
Thank you for your work! Your build works great! We are waiting for new builds !!!:)
[Shield Tablet Android Development] Khamhui:
I have some touch issues. Sometimes, it is not very responsive and rarely, it lags for a few seconds on certain apps. Do you have any ideas ? Should I flash the ROM again or it will fix itself after a few reboot?
[Shield Tablet Android Development] pjim:
It could be placebo, but the nightlies are really zippy! I don't remember this tablet ever working so fast. No audio issues for me. And battery life is much better.
[Shield Tablet Android Development] da_reeseboy:
Thank you for your work! I just flashed the latest official nightly and noticed I can't turn the sound off. I can adjust the volume sliders all over, but it makes no difference on the actual sound. Where do I need to post a log - here or cm's jira? And what would you like a log of?

Just to be clear, I'm referring to the system sounds - as you click around in the UI, notifications, etc. Media volume seems to work fine.
[Shield Tablet Android Development] Khamhui:
Do you guys recommend a custom kernel ? Mostly to improve battery life while keeping the tablet smooth
[Shield Tablet Android Development] Steel01:
Really light to check this thread more often... Even if I don't get a notification for some reason.

The only touch lag I've seen is when the tablet is plugged in. And only sometimes then. The various devs did some testing a while back and we were able to replicate the problem on stock. So we don't think there's anything we can do to fix it and assume it's a hardware problem.

System sounds. Yes, that is annoying. But as far as I know, this is a lollipop design change. Two things can be done. One, disable priority notifications (none on the volume popup). No idea why that affects it. Second, you can go to settings->sound->other and disable them there. Also, under input, there's a preference to disable keyboard clicks. I do both of those as soon as I'm through initial setup of every fresh install...

I don't recommend any custom kernels. I try to keep the kernel as close to stock as possible to prevent issues. That said, I don't recommend against either, just don't report problems here after it's installed. The only compatible one is BitO's in this forum.
[Shield Tablet Android Development] Khamhui:
No more touch issues. I update to the last nightly by flashing it. I guess the ROM had a slightly problem when I flashed it but now it is fixed.

Thanks for the feedback about the kernel. I'll keep the original one then :)

In case, because I like to try things. Do you recommend another ROM?
[Shield Tablet Android Development] da_reeseboy:
I think we might be talking about 2 different things. I understand that vibrate only and silent modes were removed in LP, but the volume slider should still adjust the volume (like it does in stock and zombi-pop, which are both 5.1.1 ROMs). If I turn the notification volume all the way down I should not hear a sound when a new email shows up, but I do.
[Shield Tablet Android Development] Steel01:
You still get email notification noise with notification volume all the way down? That is odd, I've never had a problem with that. I'd expect that is in code I don't control, however. Does the problem still happen on newer nightlies?
[Shield Tablet Android Development] da_reeseboy:
Exactly what I thought too. I haven't checked since the 11/19 nightly, so I'll try it again tonight and post here.
[Shield Tablet Android Development] da_reeseboy:
[MENTION=1416222]Steel01[/MENTION]: it's still doing it the the 11/21 nightly :/
[Shield Tablet Android Development] Steel01:
That is weird. What is your priority notification setting? If it's priority or all, can you set it to off and see if you still get notification noise? I always have mine off, and haven't had any sound out of mine.
[Shield Tablet Android Development] da_reeseboy:
Setting interruptions to priority or none seems to work.
[Shield Tablet Android Development] Kisko1998:
I have the sound problem too. It seems like the notification volume control does not work properly. Seems to work fine for notification volume (even muting completely), but the keyboard sounds and the touch sounds are not affected by the volume as they should be and are always at max volume. Using the "none" volume setting works.

I am also occasionally unable to properly dismiss a notification. After swiping it away the "No notifications" text does not appear and I can swipe the opposite way where the notification was and the notification comes back. This may have been fixed already in a recent nightly, not sure. Can't seem to make it happen again.
[Shield Tablet Android Development] ibriysraylite:
Good evening to all. I am looking to root my Shield LTE and have no clue how to do so. I am searching, but with so much information here, I honestly feel lost. Will someone please point me in the right direction? I have rootedd before, but that was with the HTC EVO from Sprint, which was, what, 4, 5 years ago?

Thank you all in advance for any guidance given.
[Shield Tablet Android Development] Steel01:
For the first part, that seems to be a lollipop design decision. I haven't found any way to change that. But I could be wrong. You can turn them off completly in sound settings and input settings, though. On the second part, I have no idea... I'll play with it next time I get a notification.

[MENTION=4132130]ibriysraylite[/MENTION]: Look in the questions section, this isn't the place to ask.
[Shield Tablet Android Development] saintirish:
I have followed directions in OP to install CWM 12.1, and so far I like it. There is just one thing missing I would like to get back, and that is the ability to record the screen. If I install the Nvidia apps found in the OP, will I get the ability to record the screen??
[Shield Tablet Android Development] Steel01:
That functionality was pretty integrated into the stock ROM. I haven't looked a whole lot into porting it over since it's a feature I would personally never use, so it's not worth the large amount of effort it would take. There are generic screen recorders on the Play Store, but I haven't heard of one that works well yet. Someone please correct me if they know of one on par with gamecast.
[Shield Tablet Android Development] Steel01:
New unofficial build in the OP. Accidentally trashed my main CM install when doing some multirom experiments, so I figured I might as well update.
[Shield Tablet Android Development] chispas117:
[ROM] [OFFICIAL/UNOFFICIAL] Cyanogenmod 12.1 for Shield Tablet

Does KODI work on this rom? I really want to try out CM but I hate to lose Kodi as this is my main source of entertainment thanks

Update: nevermind OP says it don't haha I'm slow
[Shield Tablet Android Development] Steel01:
This is an issue listed in the opening post...

Touch won't work, and no one has been able to figure out why. Something with the touch driver/libs is missynced and some apps detect the touch panel incorrectly. All other forms of input work. Like the wireless controller (on the lucky days it works...). I had my tablet plugged into my TV in console mode and ran Kodi without a hitch. For the mobile case... Well, that's one of the few reasons I still have stock in my multirom setup.
[Shield Tablet Android Development] ToHellWithGA:
Will the same breakage occur in the next nightly, or is that issue specific to the current unofficial build?
[Shield Tablet Android Development] Techamazon:
Heya, I recently flashed over the latest twrp avail on my K1. My only issue is that I get "error executing updater binary in zip... " on Nightly/Unofficial (1125). Corrupt files perhaps? I've re-downloaded just to be on the safe side but to no avail.
[Shield Tablet Android Development] Steel01:
Maybe... Is there any other error in the log? Like maybe something along the lines of wx_na_wf != shieldtablet?

This has been a problem with every aosp based shieldtablet rom ever. Kodi has never worked right. Just found out today that Talos Principle is affected as well.
[Shield Tablet Android Development] Techamazon:
http://pastebin.com/4mUHQ4gY full log here in case that helps.

edit: err.. should be noted that I'm using a TWRP theme, but it didn't work before either so yeah.
[Shield Tablet Android Development] Steel01:
"script aborted: This package is for device: shieldtablet; this device is ."

Wow, for once my initial guess was right. I assume this is the recently released official TWRP, yes? Looks like I need to get with [MENTION=5123642]lj50036[/MENTION] and iron a bug out.

Edit: Oops, forgot to mention a solution. Use the unofficial TWRP build in the TWRP thread or my multirom TWRP in the multirom thread. Either should work for now until the official build is fixed.

Edit 2: (how many of these can I make in under five minutes...?) Can you paste a copy of your /proc/cmdline? It's possible something changed with the K1 rerelease that broke my init code that's used in TWRP and the roms.
[Shield Tablet Android Development] Techamazon:
Aye it is.
[Shield Tablet Android Development] Steel01:
Gah, quick reply. :P Please see edits above.