yashsingh1/xdaforums huggingface dataset:
[Shield Tablet Android Development] Pender666:
Excellent work. This ROM is rock solid!!!!

But I have a problem. If I flash nvservices.zip of the second post my wifi will not connect anymore, my Mac address will be 02:00:00:00:00. If I flash only the ROM and gapps everything is perfect.

32g Nvidia shield tablet row LTE here.

Any tips in how to fix that? I really want to use my controller.

I gave up on the stock ROM because I always get a black screen with only clock, wifi and data icons on the status bar using my card as adopted storage and infinite reboot. After I fill it like 50% I always get that. But works ok with CM and Bliss Roms.

Thanks in advance
[Shield Tablet Android Development] Steel01:
Don't use the services zip, that's ancient and never worked right anyways. I got the controller working in the unnofficial 12.1 builds. Well 'working'. I never got the app to stop crashing in 13. One of the months, I may get back to it again. But the HDMI audio issue has priority, especially since that's critical on the console (same issue on both devices).
[Shield Tablet Android Development] Yoyoa:
Hello, I have the k1 shield tablet, i have to flash firmware 420 or 311 to have the MM bootloader?
[Shield Tablet Android Development] :
Is it so hard to read?

https://developer.nvidia.com/gameworksdownload

4.2.0 and 3.1.1 are for the orginal Shield Tablet. Now guess what you need...
[Shield Tablet Android Development] Yoyoa:
Thank you, ok, and if i want the new bootloader for my k1 tab, i have to take the same BLob.img?
[Shield Tablet Android Development] :
The easiest and safest way would be to flash 1.3.0 completely (which erases your userdata). (Optional: Then use cf-autoroot to root.) Flash TWRP then CM13 and Gapps.
[Shield Tablet Android Development] Steel01:
There's no known difference between the original and K1 bootloaders. Just use the 4.2 zip from the OP for M.
[Shield Tablet Android Development] Pender666:
Shield Controller working great here using OTG cable and plugging the controller via USB!!!! ?
[Shield Tablet Android Development] boswelja:
[MENTION=1416222]Steel01[/MENTION] I got it booting past the boot logo, now it hangs on a black screen just after the boot logo.. It appears to be trying to boot the system
[Shield Tablet Android Development] Sjamaan:
After a few days of use, I have to say I'm very happy with this nightly builds.

I didn't even needed to reformat SD coming from stock and adopted storage, as wiping didn't erased the key.

Performance wise, as good if not better than stock. No big lags, multitasking sucks but as always with this tablet. Battery wise? Slightly more draining than stock, but still bearable.

Thank you so much [MENTION=1416222]Steel01[/MENTION] for your work, without you, this tablet and all its scene would suck badly.

Enviado desde mi ALE-L21 mediante Tapatalk
[Shield Tablet Android Development] Steel01:
I surprised you're getting that much. My builds won't display anything at all. Something in the caf merge broke all non-qcom devices. Still trying to figure out all the things that need fixed. Other devs found a couple things, but still not enough to fix our hwcomposer.
[Shield Tablet Android Development] boswelja:
Oh, more waiting I guess :(

I'd help, but I've no idea where to start

BTW the staging/cm-14.0 manifest is working perfectly :)

I also no longer need to edit init_tn8.cpp

EDIT: And so is F-AOSP, its a shame they dont boot :(
[Shield Tablet Android Development] Steel01:
[MENTION=5227356]boswelja[/MENTION]:

http://review.cyanogenmod.org/#/c/161553/

That fixes the surfaceflinger crash and allows it to boot. I'm still working with selinux permissive, so no clue what would happen if booted enforcing.
[Shield Tablet Android Development] boswelja:
Just looked at the recent changes to the repos, do I still need the extra sepolicy changes?
[Shield Tablet Android Development] Steel01:
Not sepolicy, no. But still want selinux permissive and quail star (dunno about the latter, but I'm still using it atm). I'm trying to nail down sane sepolicy changes for the non compile error problems.
[Shield Tablet Android Development] boswelja:
[MENTION=1416222]Steel01[/MENTION] just did a booting aosp build, but WiFi doesn't work :(
[Shield Tablet Android Development] Steel01:
Did you add selinux permissive to the boot image kernel command line? WiFi was working fine for me on aosp. I just haven't finished up the policies needed for it to work when enforcing.
[Shield Tablet Android Development] boswelja:
Oh lol nope, any way I can do that while I'm running the build?
[Shield Tablet Android Development] Steel01:
Modify the boot image? Or fastboot boot it with a -c to add the argument.
[Shield Tablet Android Development] boswelja:
Oh.. So I guess setting the sepolicy value to 1 i n the build prop won't work.
[Shield Tablet Android Development] boswelja:
[MENTION=1416222]Steel01[/MENTION] I've got an almost fully working build! Other than the camera, eveything works :D

I'll make a new thread tomorrow and give credits to you for 98% of the work, all I really had to do was make a few changes for it to work with AOSP and build it
[Shield Tablet Android Development] radekbugaj:
Hello,

I have a problem with the update to cm13 . I'm currently using version CM12 . The update runs properly - but after reboot the system does not start. Hangs on the screen nVidia . Resets do not give anything .

The same effect is when Loading a cm13 in accordance with the instruction from the page wiki.cyanogenmod.org/w/Install_CM_for_shieldtablet.

Any ideas what to do ?
[Shield Tablet Android Development] john_matrix:
You have to update te bootloader.

Check on the first page, everything is provided ;)
[Shield Tablet Android Development] radekbugaj:
Thanks.

I understand that I have before installing cm13 install the new firmware ? And which of the two to choose :

-3.1.1 (L)

-4.2.0 (M) ?

Sorry for the stupid question - but I do not know the android system .
[Shield Tablet Android Development] john_matrix:
This is not a firmware, its only the bootloader.

You have to use the "M" version as CM13 is based on "M"arshmallow ;)

Nothing is stupid, and more particularly if you are not used to make this kind of manipulation ;)
[Shield Tablet Android Development] radekbugaj:
Or installation of the M version will solve the problem ?

And if it installs just like cm13 - that is, for the help TWRP ?
[Shield Tablet Android Development] Steel01:
I think you'll find that hardware media acceleration doesn't work either. And that would be the root cause of why the camera doesn't work. Also, GPS at the very least won't be fully accurate, if it doesn't just fail completely. I haven't shimmed the gpsd yet, so it's crashing.
[Shield Tablet Android Development] boswelja:
Yea I figured out there aren't any ffmpeg codecs too
[Shield Tablet Android Development] amnguerreiro:
Sorry for asking, but i searched the topic and can't find anything about this.

If i flash CM 13,will stylus work?

What steps do i have to follow to install CM13 coming from lollipop stock?

Thanks in advance
[Shield Tablet Android Development] tt33oo:
I'm looking for the right version cwm for nvidia shield with android 6.0.1 .

I installed it on sdb and then I could boot into recovery and install CM13 , then I wanted to reinstall the recovery to the google apps and as he shows me very briefly the recovery and then start right again. many thanks for the help
[Shield Tablet Android Development] mossief1965:
Flashed the ROM and the 4.2 bootloader zip. It's now on the blue android boot screen for 15 minutes. Any ideas?
[Shield Tablet Android Development] john_matrix:
Try to wipe cache/dalvik from recovery
[Shield Tablet Android Development] mossief1965:
Did not help, trying full wipe now.

EDIT Full wipe had no effect
[Shield Tablet Android Development] Ollebro:
Just got this device, do you people recommend Cyan on this or am I better off with Nvidias own rom?
[Shield Tablet Android Development] :
They are both good and stable. CM has more setup options and themes.
[Shield Tablet Android Development] Isira:
It is important to note that there were some nightly builds that were quite unstable (high battery drain, random reboots), so it is important to backup and keep note of which builds were stable.

With a good stable build, I do find the battery life to be a little shorter compared to the stock ROM. Functionally, CM13 is about as smooth as stock with hardly any lag.

There are also a few bugs in CM13 which may be a deal breaker. There is no audio when using HDMI output, and touch does not work with RetroArch.
[Shield Tablet Android Development] Steel01:
That HDMI audio issue is gonna drive me nuts. Well, the rest of the way there that the LTE issue didn't already drive me... Maybe one of these days.

As for retroarch, I really don't know what's different from stock there. But I have talked with the devs about it:

https://github.com/libretro/RetroArch/issues/3003
[Shield Tablet Android Development] davidplz:
Does anyone have problems with 5Ghz wifi AP? I can't see mine even forcing it just at 5Ghz....

The other small annoyance is not having the lockscreen rotate :confused: I've been testing every option but I had no luck...

Anyway, impresive work [MENTION=1416222]Steel01[/MENTION] :good:
[Shield Tablet Android Development] Steel01:
I've not seen trouble with 5 GHz, but the topic keeps coming up from time to time. Don't know if I can do anything if I can't reproduce it, though. My router is a tp-link running openwrt. For the extra data point for those keeping track.

Lock screen rotate option is under display->rotation.
[Shield Tablet Android Development] Isira:
No problems here either. Router is Asus RT-AC68U.
[Shield Tablet Android Development] Sjamaan:
Try to change the channel in you router to another way higher or lower than your current one. That worked for me in the past with other devices.
[Shield Tablet Android Development] davidplz:
Ok

I'll try changing the channel... I think there was an option to let the router choose it automatically...

Ty :good:
[Shield Tablet Android Development] Bitcloud30:
My NSTK1 is on its way now. And i was reading some comments, so hdmi audio is not working at all?
[Shield Tablet Android Development] boswelja:
Not since I last checked :(
[Shield Tablet Android Development] Elpatii:
Hi,

Is there a way to adjust screen coloration, contrast and saturation? Like in the stock ROM in fact.
[Shield Tablet Android Development] valdeinsamkeit:
Is there anywhere I can go to get the last 12.1 build (before hdmi audio stopped working, but after controller pairing was "supported")?

Alternatively, If there's anything I can do to help diagnose or test the hdmi audio issue please let me know.

------------------------------------------------------------

Nevermind the download question, I just figured out the build. Still happy to help w/ the audio thing in 13 though, I just don't know where to start.
[Shield Tablet Android Development] Hsebaer:
HDMI no Audio.
[Shield Tablet Android Development] Steel01:
Alright CM14 status update. I've found fixes or workarounds for the majority of problems I was having. GPS works, hardware video acceleration works, camera works (using unmerged cm patches), etc, etc. Only problem left (that's new to N) is wvm. Aka no Netflix yet. That and I need to fix some more sepolicies. And of course the HDMI audio issue persists. No builds yet, though. Upstream cm is still in a lot of flux.
[Shield Tablet Android Development] hectoralexgarcia:
So I take it that the hdmi audio issue has been resolved? I don't mind hdmi audio too much since I use google chrome to watch on the tv... but when I travel and stay at hotels, the chrome is useless since the hotels usually firewall/isolate each device connected on wifi. I've been itching to try 14 ;)
[Shield Tablet Android Development] simonsy:
Hi, I'm also interested in trying the latest version of this rom for the nvidia shield k1, but before starting to install everything it would be great to see a list of the current open bugs and the fixed ones.
[Shield Tablet Android Development] Steel01:
CM 14.1 is still undergoing a lot of work. Not ready for any releases yet. I've only had time to run a couple test builds, but I do know it boots. The same problems listed in my last post still apply since I haven't had time to fix them yet. And there's no need for a K1 specific build, this works on all variants.

[MENTION=1400682]simonsy[/MENTION]: The only issue I know of is HDMI audio not working.
[Shield Tablet Android Development] Tenacious--M:
Does this ROM add a phone dialer for the LTE version so it can be used for calls?
[Shield Tablet Android Development] Steel01:
You can set a property to put put the device in voice call mode, which will enable the dialer. However, calls cannot be made without modifying the firmware. Which we cannot do because the firmware images are signed and we don't have the key.

If you want to see the dialer anyways, run the following in a root terminal and reboot:

setprop persist.cm.shield.model wx_un_mo
[Shield Tablet Android Development] Tenacious--M:
Thank you for the explanation... Makes total sense.

Does the international version work for calling by chance? Or are they all the same?
[Shield Tablet Android Development] Steel01:
US and international are the exact same hardware. The only difference is in fact the modem firmware. However, it doesn't support voice either. Just a different set of 3G and LTE bands.
[Shield Tablet Android Development] kristofpetho:
Is it just me, or does the latest (Nov13) nightly not boot? I tried the official build as well as compiling on my own...
[Shield Tablet Android Development] mushikipt:
Same here, rolling back to previous i guess
[Shield Tablet Android Development] kristofpetho:
Good to confirm, thanks :)

On a side note, the speed and fluidity of CM13 on the Shield Tablet is incredible compared to the stock ROM. :)
[Shield Tablet Android Development] ManderZander:
I encountered the same problem:

cm-13.0-20161113-NIGHTLY-shieldtablet.zip hangs during boot. The screen shows a frozen image from the Cyanogenmod animated logo.

Reverting to cm-13.0-20161106-NIGHTLY-shieldtablet.zip works.
[Shield Tablet Android Development] Steel01:
I've confirmed the issue. Appears that google added some extra 'security' to zygote (in both M and N), which is causing the boot to fail. I'm trying to track down what exactly is triggering the problem. Will try to get it in by the next nightly, but no guarantees since I don't even know which piece is the issue yet.
[Shield Tablet Android Development] kristofpetho:
Excellent news, let me know if I can help!
[Shield Tablet Android Development] kristofpetho:
[MENTION=1416222]Steel01[/MENTION] - could it be that headset buttons don't work at all? I've tried Android and iPhone headsets but buttons don't work from either one. Neither volume nor pause/play works...
[Shield Tablet Android Development] Steel01:
The kernel doesn't have support for headset buttons. I looked into what it would take to fix that and got lost right fast... I'd love to get it working, though.

Alright, I found a 'fix' for the recent boot problem. But it may not be the best way to handle it. There's still some discussion going on around the main code maintainers. My pending change is here if anyone is interested in following it.
[Shield Tablet Android Development] kristofpetho:
Thanks - bummer about the headset buttons, but then again no biggie. The sound quality is not that great on this tablet though (stock ROM also). Bass is terrible and the noise is terrible if I turn on any equalizer.

On the zygote error - saw the discussion. Interesting that no other device had this issue...

Other - do you think adding the sio I/O scheduler could help with battery life in general? I now throttled the CPU to 1.5Ghz and the GPU to 524Mhz with Kernel Adiutor, and SOT should hold around 7-7.5 hours (with browsing, tons of syncs and light gaming (Alto's Adventure)), but I want MOAR :)
[Shield Tablet Android Development] :
Maybe I'm deaf but on my tablet the sound quality is decent and the bass is okay. And if I turn on the built in equalizer I don't hear any noise. But that's ot.
[Shield Tablet Android Development] kufor:
Installed cm-13.0-20161106-NIGHTLY-shieldtablet.zip, running great with BitO-K7 kernel. ;)

Thx to devs.

Just a hint for anyone having WIFI authentication issues as I had...

Disable Protected Frames in your router's wireless settings.

It took me several hours to find out, why is the Shield K1 not connecting to my wifi network (all other devices work just fine).
[Shield Tablet Android Development] kristofpetho:
Quick piece of info for anyone who wants to try CM13 on the Shield Tablet: the newest nightly known to be working fine is from November 6. Be sure to flash that and do NOT upgrade to anything newer until the fix is merged!
[Shield Tablet Android Development] kristofpetho:
[MENTION=1416222]Steel01[/MENTION], I see on Gerrit that there is no movement on the two commits... Who do we need to nudge to get them merged? :)
[Shield Tablet Android Development] Steel01:
Finally got it shipped. Pushed my change in as well. So tonights run should be good to go.
[Shield Tablet Android Development] Kssadd:
Thanks a lot! one thing, could you merge the fix in the CM14.1 branch too? Please :)
[Shield Tablet Android Development] kristofpetho:
Awesome! Time to build at home then!
[Shield Tablet Android Development] Steel01:
Once the main patch gets pushed to 14.1. Right now it wouldn't do anything.

14.1 is still mostly a mess, though. Broken camera, no widevine, missing upstream features like theme support. No one should be using builds based off my device tree yet. It isn't ready.
[Shield Tablet Android Development] kristofpetho:
I meant CM13. :) Heck, CM14.1 is still a mess on the OnePlus3 even...
[Shield Tablet Android Development] Steel01:
Alright, the latest nightly is good to go. Back to my regularly scheduled bashing head into a brick wall trying to get the camera working properly on N...
[Shield Tablet Android Development] Natebluehooves:
help please? :3

Hey quick question... I installed a nightly and it just gets stuck at the "NVidia" screen forever. this now goes for every rom I try. i'm using twrp and have tried wiping every partition, doing a fresh install, etc. this also happens if I try to flash stock roms via fastboot. just gets stuck forever.

does anyone know how to fix this? thanks!

I'm hoping that I'm just missing a step :P
[Shield Tablet Android Development] DutchPlayer:
Dude I have the same problem, I fixed it with going back to CM 12.1 .

But the main question still is why does CM13 hangs after upgrading on the shield tablet?
[Shield Tablet Android Development] Natebluehooves:
seems like for some reason all of the cm12.1 builds are gone. all I can find in get.cm is four early builds of 13...
[Shield Tablet Android Development] Steel01:
If cm13 doesn't boot, it's likely because you need to update the bootloader. Use the latest flashable zip in the opening post. And the cm13 builds aren't 'early', they're completely stable with only only known issue being that HDMI audio doesn't work.
[Shield Tablet Android Development] keelsonkeelson:
Does this mean the problems have been fixed?
[Shield Tablet Android Development] flatratte82:
Yes. Exactly.
[Shield Tablet Android Development] MySpleen:
Hey, [MENTION=1416222]Steel01[/MENTION], just letting you know that the latest full OTA is 4.3, and 4.4 is a patch, not a full

Edit: Successfully flashed Tesla N to try it out. Wiped and tried flashing Full OTA 4.3 but it was having issues. Testing flashing Full OTA 4.2 to see if there's an issue with downgrading from N to MM or if it's Full OTA 4.3

Edit2: It's an issue with Full OTA. Booting now so I get to see if it works or I bootloop.

Edit 3: It works. Lesson learned, Full OTA 4.3 doesn't like flashing except as a patch for 4.2

Updated Nov 24, 12:57 PM
[Shield Tablet Android Development] keelsonkeelson:
Well,I just flashed 20161122 and ended up in a bootloop.
[Shield Tablet Android Development] flatratte82:
I'm still in 11/18 and it runs fine.
[Shield Tablet Android Development] mg515:
Camera problems

I installed CM13 on my K1 yesterday (latest nightly from get.cm, cm-13.0-20161122) and the camera apps crash when I start them. Is this something normal, somehow fixable or should I use some other nightly build?

Other than that I can say I'm pretty happy with CM13. Bought the tablet yesterday and the official ROM lagged as hell, so I gave the tablet one more try with CM, which works flawlessly apart from camera problems. It's not that big of a deal anyway, but I want to use Skype.
[Shield Tablet Android Development] keelsonkeelson:
11/18 seems to be fine, I just flashed it and didn't notice any problems

[MENTION=7433454]mg515[/MENTION] camera is fine on 11/18, I own the tablet for about 3 months now and never used the stock rom. Installed cm13 and never had any problems, just some of the latest builds had problems.
[Shield Tablet Android Development] grandomegabosses:
Nevermind, sorted it out. Firmware.
[Shield Tablet Android Development] abdabbs:
[EDIT] nvm, answered my own quesiton by digging a little deeper... [\EDIT]

I'm new to CyanogenMod. With these nightlies do I just dirty flash in recovery? On 13.0 from 11-18 presently. I have TWRP for my recovery and is probably why the update isn't going automatically when in ABOUT TABLEY<CYAN UPDATES.

Thanks
[Shield Tablet Android Development] jeremy803:
any news on getting audio working over hdmi ??

Currently running cm-13.0-20161118-NIGHTLY-shieldtablet, was wondering if there has been any progress getting audio working over HDMI ?? I'd really like to have this feature. Thanks.
[Shield Tablet Android Development] brandon88tube:
I'm looking for the latest, most stable, version of Cyanogenmod for the original wifi version. Can anyone help me out?
[Shield Tablet Android Development] Steel01:
[MENTION=7915353]jeremy803[/MENTION]: Wouldn't we all... I've fought with it off and on for a year or so now. Still haven't cracked why it doesn't work.

[MENTION=4711677]brandon88tube[/MENTION]: The latest cm-13.0 nightly. Afaik there's only minor issues for most people. Like just mentioned, hdmi audio is the biggest. The second issue I'm tinkering with is persistent apps (like Pandora or holoirc) getting killed if you use too much ram in another app (like huge javascripted webpages in Firefox). Under normal usage, that's not a problem, though. The nightlies are linked in the opening post.
[Shield Tablet Android Development] brandon88tube:
I was going off of [MENTION=1795993]kristofpetho[/MENTION]'s post about not upgrading past the November 6th release. The reason I'm looking for the most stable version, is that I plan on giving this tablet to my mother for Christmas who is not tech savvy at all and wanted to avoid as many headaches as possible after I give it to her.
[Shield Tablet Android Development] :
[MENTION=1416222]Steel01[/MENTION] BTW: Any news about CM 14.1...
[Shield Tablet Android Development] BitOBSessiOn:
Stock recovery images:

https://developer.nvidia.com/gameworksdownload
[Shield Tablet Android Development] _Fidor_:
Hi,

Additional info regarding the battery usage:

After doing some Googling, I've found multiple reports of this behavior from few days ago.

It seems that the latest Google Play update is broken:

http://xdaforums.com/general/genera...e-wakelock-t3060548/post59617146#post59617146

Unfortunetely the fix presented in above link, does not work for me.
[Shield Tablet Android Development] terrigan:
Still have the problem. Doesn't look like AudioFX had anything to do with it.