yashsingh1/xdaforums huggingface dataset:
[Shield Tablet Android Development] kongha:
Happy to see the update. Will give a feedback of how it works out from multirom in this post.

Have a nice weekend :)

edit: I didnt run into anything that had a screeching noise. Then again I probably didnt let my cpu to clock down during a 5 min youtube video. When I did flash "SHIELD Apps for Cyanogenmod 12" the program that should connect the controller with the tablet stop to work completly. Maybe this is a issue that has already been talked about.
[Shield Tablet Android Development] Plac3b0:
Hey guy's,

is someone here in the forum who can tell me in german how to root and flash my shield tablet ?

Is it possible that the old tablet after the recall works? Maybe with an custom rom?

Sorry for my bad englisch and my missing know how :D

Thanks a lot guy's, Plac3b0
[Shield Tablet Android Development] Steel01:
Well, in testing, I've found how to mitigate the sound screeching at least. I pulled one of the free cpu tuner programs, switched the governor to on-demand and set the limits to 1.5-2.2 GHz. No more screeching. Seems the default settings allow the CPU to clock down so far during video playback that the audio buffers can't keep up and bad things happen. That's really annoying, but I don't know if I can 'fix' it or not.
[Shield Tablet Android Development] BitOBSessiOn:
I have also set bigger audio buffers in KSX trying to avoid these audio issues.
[Shield Tablet Android Development] tt33oo:
Hello XDA team

This is Rom for the LTE version?

can allow the automatic shutdown of the shields are prevented by nvidia?
[Shield Tablet Android Development] imneveral0ne:
Does HDMI out work with cm?
[Shield Tablet Android Development] BitOBSessiOn:
It should. If it does not, you can try KS-037... it's reported to work fine.
[Shield Tablet Android Development] Steel01:
Got my replacement tablet today and loaded up my latest CM build. Seems to be running okay. Decided to play around with the controller a bit. First, I disabled USB audio auto routing as described here. Then I paired the controller (running from the menu works now, but after the pairing light stopped blinking, I still had to manually back out of the pairing app). And everything has worked great so far. Poked around grid, let the controller go to sleep, rebooted the tablet, etc. So far, it's always reconnected without intervention and worked as expected. I still wouldn't call it 100% reliable, especially with the headphone jack not working, but it seems to be very usable on the tablet. Wish I could say the same for the portable and console...
[Shield Tablet Android Development] Moz007:
I just flash the lastest nightly on my Shield and get a freeze on cm start animation... :(

Edit : it worked when i unplug my usb cable from my computer...
[Shield Tablet Android Development] techwiz24:
WiFi stability

Are the problems with WiFi stability known? It seems like a similar issue to the one I have with the Intel AC 3160 in my laptop: Signal strength remains fine, but performance tanks and stuff stops responding. Switching off and on the wifi sometimes fixes it, but not for long...
[Shield Tablet Android Development] Keithn:
I found that if you add "ro.radio.noril=true" to the build.prop it will remove the mobile network and sim stuff for anyone wanting to remove that
[Shield Tablet Android Development] pjim:
Now that's a great tip! Thanks! Works on the stock and AOSP ROMs.
[Shield Tablet Android Development] kongha:
Thank you, thats great.

There is also a module for Xposed called nosim (or something with sim in it) that removes it.
[Shield Tablet Android Development] DaRiP:
.patch files

Hi folks,

When i try and run the patch files I get iwifip2pmanger.aidl not found, just running in terminal emulator, can someone post a quick how to for running the patch scripts? Sorry android newbie-itis :p

Ta much!
[Shield Tablet Android Development] Steel01:
Noril? It's that easy? Great, thanks. I'll try and test that tonight and add it to the na_wf part of the custom boot code. That should be the last thing wf users complain about. Then the unified build should have no problems specific to model.

[MENTION=5383682]techwiz24[/MENTION]: That sounds more like a router problem than a tablet problem. I don't have any WiFi trouble myself. Has anyone else seen this?

[MENTION=5655167]DaRiP[/MENTION]: I presume you're trying to get the wireless controller to work. You don't have to apply patches unless you're trying to compile a new copy of the ROM. Just run Shield Controller from the menu. And reference the shield apps thread post #4 before trying.
[Shield Tablet Android Development] Keithn:
That's how nvidia did it. I dug through the stock build.prop, saw that and it seemed like the most obvious thing I could find in there to deal with the sim related stuff.

I added it to the build.prop on cm and it worked for me.

Sent from my m8wl
[Shield Tablet Android Development] Steel01:
Yeah, I cloned my cm secondary and added the line. Disabled it all even on my lte model. Tweaked the code, pushed the commit, and I'm running a build now. Pending a basic install and check out, I should have it uploaded and released tonight. This will only affect the WiFi only model. If you want to disable the lte stuff on an lte model, you'll still need to do this manually.
[Shield Tablet Android Development] Steel01:
Alright, the new build is up in the opening post. Wifi users should now have no extra settings or icons.

I'm looking at adding a manual override for the model detection. Like setting persist.cm.shield.model = wx_na_wf to force detection as a wifi model for those that want 32GB, but no cell radio. I'll have a new build once that's tested.
[Shield Tablet Android Development] Steel01:
Ummm... Who said? ;)

[MENTION=6411851]BitOBSessiOn[/MENTION]:

I've seen some mention that na and row run on each other, but have no hard evidence to prove that yet. I know the firmware files for both modems are in the build and in the stock *_do builds. Another thing on my list to do is to compare nvidias aosp device build files to see what the differences are. I don't expect to see much if any difference. And check the vendor repo on my github account, there are newer blobs there.
[Shield Tablet Android Development] FoxyDrew:
You know what's funny, is, I looked at it afterwards, and knew it was wrong. But wasn't 100% sure, so I just kept it xD.
[Shield Tablet Android Development] BitOBSessiOn:
I've flashed this wx_na_do on wx_un_do, and everything seems to work ok.

It's amazing how the community reach better performance and using experience than the proprietary enterprise...

I'll try also to check differences between nvidia sources of wx_na_do and wx_un_do.

One interesting thing is that I can install Whatsapp in market... ¿would it be possible making voice calls in this rom...?

In one experimental compilation I was able to get Phone Dialer with nvidia sources, but when I tried to make a call, the call failed (something pending about modem activation....?).

Thnx!.
[Shield Tablet Android Development] Steel01:
So all data stuff works for you? Not too surprised. As for voice, it seems the firmware files are different. I'm currently downloading the one stock build of wx_un_no I could find and I'm going to see what I can do with the firmware files. Don't know when I'll have the time to devote to it, though.
[Shield Tablet Android Development] BitOBSessiOn:
I can confirm all data works fine for wx_un_do (pending to test LTE, but 3G and H+ ok).

I've compiled wx_un_mo (forcing Dialer apk to be included) and flashing with no problems on wx_un_do, expecting voice calls to work, with no success.
[Shield Tablet Android Development] joethc:
I will be flashing this tonight to see how much better the battery will fare ....anyone have initial impression? good work on the controller file too!!! I bet that was holding a few people back from flashing custom roms!!! I was wondering when someone was gonna build cm or shield tab and actually post it.... anyways for people that can't build atm thank you very much
[Shield Tablet Android Development] BitOBSessiOn:
wx_na_do (US LTE) and wx_un_do (RoW LTE) configurations files in nvidia sources are identical (or equivalent) except that wx_na_do adds:

## common apps for all skus
$(call inherit-product-if-exists, $(_product_private_path)/wx_common_user.mk)

Differences between wx_na_do and wx_un_do in patch format.:

--- /opt/sc/nvidia/shieldtablet-open-source/device/nvidia/platform/shieldtablet/products/wx_na_do.mk
+++ /opt/sc/nvidia/shieldtablet-open-source/device/nvidia/platform/shieldtablet/products/wx_un_do.mk
@@ -1,6 +1,6 @@
# NVIDIA Tegra5 "Ardbeg" development system
#
-# Copyright (c) 2013-2014, NVIDIA Corporation. All rights reserved.
+# Copyright (c) 2013, NVIDIA Corporation. All rights reserved.
#
# AndroidProducts.mk is included before BoardConfig.mk, variable essential at
# start of build and used in here should always be intialized in this file
@@ -18,10 +18,10 @@
PRODUCT_PACKAGES += icera-config

## Thse are default settings, it gets changed as per sku manifest properties
-PRODUCT_NAME := wx_na_do
-PRODUCT_MODEL := wx_na_do
+PRODUCT_NAME := wx_un_do
+PRODUCT_MODEL := wx_un_do

-## Values of PRODUCT_NAME is mangeled before it can be
+## Value of PRODUCT_NAME is mangeled before it can be
## used because of call to inherits, store their values to
## use later in this file below
_product_name := $(strip $(PRODUCT_NAME))
@@ -56,9 +56,6 @@
## common settings for all sku except for diag
include $(LOCAL_PATH)/wx_common_user.mk

-## common apps for all skus
-$(call inherit-product-if-exists, $(_product_private_path)/wx_common_user.mk)
-
## nvidia apps for this sku
$(call inherit-product-if-exists, $(_product_private_path)/$(_product_name).mk)
[Shield Tablet Android Development] Steel01:
I'm about to start uploading new builds. Nothing new except for upstream cm stuff, however. Slow upload here, so it will be a bit.

In the little testing I did of the builds I noticed something weird. The do build installs and boots off multirom as expected. The wf installs, but is missing build.prop and thus won't boot. ?? Say what? I don't think that would boot as a normal internal install if that was really true. But I don't want to overwrite my internal right now. I might try that later tonight. Might have to bug Bogdacutu if that really only happens on multirom. For those on wf that want multirom, an ugly workaround could be to install to internal, then use swap ROM to get it as a secondary.

Edit: Builds are up and title will be changed to reflect that this is no longer limited to LTE builds.
[Shield Tablet Android Development] matlear:
1st Impressions WiFi Build:

Boot time is very fast (compared to stock nvidia).

HDMI out working great with sound.

Stylus Working as per stock.

System seems pretty lag free (well see what happens once I have all my apps isntalled).

Will report back after a couple of day's usage..

Big Thanks to:

Steel01, Unjustified Dev :good: :good: :good:

Edit.....

I can't get any video to play in any apps, I have tried disabling nuplayer to see if this helps but no luck there... Any ideas??
[Shield Tablet Android Development] Steel01:
Hmmm... So I see. It appears that the hardware decoder stuff is bombing out. I can get mxplayer to play stuff with software, but not with hardware. I'm looking into it.

Steel01
[Shield Tablet Android Development] KindleFireGuy:
This may be stupid of me, put how would I apply a ".patch" file?
[Shield Tablet Android Development] matlear:
A quick workaround for the video problem is to use Dolphin Browser and MX player in SW mode...

Is there anyway I can disable HW encoding for apps like YouTube and the stock video player temporarily until a fix is made?
[Shield Tablet Android Development] BitOBSessiOn:
From terminal:

$ patch --help

From Google:

The basic syntax is as follows:

$ patch < patch.file
$ patch source.code.file < patch.file
$ patch -p LEVEL < {/path/to/patch/file}

To apply a patch, one could run the following command in a shell:

$ patch < /path/to/file

In this example, patch foo.c with patch.diff file:

$ patch foo.c < patch.diff

Patches can be undone, or reversed, with the '-R' option:

$ patch -R < /path/to/file

---------- Post added at 08:10 AM ---------- Previous post was at 08:06 AM ----------

@Steel01, I've compiled CM12 from your sources and everything seems to work except modem... no modem data, only wifi... (PIN is not asked), Have you any idea about it...?

Thnx !
[Shield Tablet Android Development] Steel01:
I'm in communication with Unjustified Dev about the video acceleration problem. OMX is spitting all kinds of errors on boot, but I don't know why yet, the log isn't terribly helpful. I don't know about workarounds, maybe Firefox or Chrome to use YouTube's html5 player. I haven't tested, so I don't know if that will be smooth if it will run at all.

[MENTION=6411851]BitOBSessiOn[/MENTION]:

The only thing I can think of offhand is that you don't have my commit that enables rild. I've moved my repos over to CM-Shield, so all my Shield related work will be together. If you already have this commit, I don't know offhand.
[Shield Tablet Android Development] BitOBSessiOn:
I've just compiled last CM12 (20150316) with your source (before change to cm-shield) and I've been able to play youtube and mp4 videos directly....

I'll try from this, but... is it necessary to extract manually licensed bins from the tablet or are the files included in your repository (proprietary_vendor_nvidia)

Thnx!
[Shield Tablet Android Development] Steel01:
I haven't changed much (if anything) yet from when I had the repos on my personal github account, I just moved ownership over to the organization.

The blobs in the vendor tree are what I've been using to compile the ROM. They're at least enough to make it boot and have cell connectivity. I'm beginning to wonder if some aren't working as intended (OMX libs)

Wait, you say you have hardware acceleration on your build? Like, the hw or hw+ options in mxplayer work?
[Shield Tablet Android Development] BitOBSessiOn:
I've noticed some little difference between your blobs and the ones I've extracted from my LTE RoW. Are yours extracted from OTA 2.2.1 ? In my next compilation I'will try mine.

I haven't been able to confirm exactly if HW accel works or not... but with your last compilation I was not able to play youtube videos, with mine was ok... FYI
[Shield Tablet Android Development] Steel01:
Hmmm... Okay. Yeah, mine are extracted directly from the wx_na_do 2.2.1 ota zip. Now I'm curious what files are different. I'm going to have to swap a few out if the OMX libs from row work better.
[Shield Tablet Android Development] BitOBSessiOn:
Mine extracted also from 2.2.1 RoW. Different files are:

[B]proprietary/etc/firmware/bcm43241.hcd [/B] (size bigger in RoW, wx_un_do)
[B]proprietary/etc/firmware/nvavp_vid_ucode.bin[/B] (does NOT exists in RoW, wx_un_do)
[B]proprietary/vendor/lib/libnvmm_camera_v3.so[/B] (size bigger in RoW, wx_un_do)
[B]proprietary/vendor/lib/libcuda.so[/B] (size bigger in RoW, wx_un_do)
[B]proprietary/vendor/lib/libglcore.so[/B] (size bigger in RoW, wx_un_do)
[B]proprietary/vendor/lib/hw/audio.primary.tegra.so[/B] (size bigger in RoW, wx_un_do)

I think there is no more...
[Shield Tablet Android Development] Steel01:
Well, I might have pulled these from the wrong directory. I have reextracted and repulled all the vendor blobs. At the very least, it put the permissions back where they should have been in the first place. I'm running a private build off shortly to see if that fixes anything. Here's hoping. *crosses fingers*

And I'm running diffs of the na and row system images. A huge number of apps and framework stuff is different. But only a couple libs show up as different. I wonder if the differences boil down to software localization and nothing hardware based. That would make things much easier.
[Shield Tablet Android Development] manelc84:
Wifi problem

Hi all this rom is great, but i have a problem.

WIFI problem. Sometimes..... randomly i lose wifi conection and i need to toggle off and toggle on wifi to reconnect.

Did alot of research and cant find how to fix this on nvidia shield tablet LTE.

Anyone is facing the same problem and know how to fix?

Thank you :)
[Shield Tablet Android Development] sanco1973:
dont see tablet in computer

Hey. I do not see the tablet in computer. A repository settings - a USB connection to a computer - reports:

"Application Settings, unfortunately stopped working."

Excuse my English - translator
[Shield Tablet Android Development] linuxct:
Very good rom, nice job [MENTION=1416222]Steel01[/MENTION]. Way better than stock.

However, I faced two bugs, the first is Wi-Fi, it's not working properly, if by any reason the tablet disconnects from the router, it won't pair up until I turn the Wi-Fi on and off. Then it works just fine.

And the second one, after having the tablet over nine hours on, I opened the cover and the tablet self-rebooted. I own a ProCase SlimSnug and it has some magnets to turn on the screen, and after a deep sleep seems waking the tablet up using it, makes it crash.

Anyways, good job, keep it going :good:
[Shield Tablet Android Development] manelc84:
someone help please with wifi issue

So there is any way to solve the wifi problem? keep losing connection all the time...
[Shield Tablet Android Development] Steel01:
I don't have any problem with WiFi and can't really do anything about it without more information. There's some talk on the Bliss thread about it that it starts happening when the gapps linked in that thread are installed. Which gapps did you install, the ones linked in the Bliss thread or the ones linked here?

[MENTION=4787101]linuxct[/MENTION]: The magnetic case problem is interesting. I don't have one, so I've never tested it. Wonder if I could fake it out with refrigerator magnets or similar. After a crash, can you boot directly into recovery (or primary rom, just don't boot to a multirom secondary) and pull /proc/last_kmsg? In theory, that log should contain all the kernel messages up to the crash.
[Shield Tablet Android Development] linuxct:
I'm using TKruzze Gapps (Complete Google package, the one of 670+mb). And about the dmesg, I'll try the next time I face that kind of crash, don't worry. :)
[Shield Tablet Android Development] gribouillees:
Hello,

I have some questions because I'm a little bit confused.

I have installed the following package in my tablet :

- [ROM] [UNOFFICIAL] Cyanogenmod 12.1 for Shield Tablet

- CM 12.1 GApps from the cyanogen wiki

- Shield Apps : nvsystemservices.zip

But I have some issues :

- The Nvidia controler App is available but when I launch it, I have a black screen and a few seconds after it closed itself

- The stylus does not work even when I install Dabbler form the Plays Store

- I don't have the Mode consol Hub

What I'm doing wrong ? I check almost all the treads, on some threads it says that the nvsystemservices.zip does not work properly on 12.1 only on 12. On some other else it says that nvsystemservices.zip is not needed on 12.1.

Everything works like a charm except the nvidia Features. I have the Wifi only version.

Please let know and one everything will be OK, I will made a tutorial for newbies like me.

Thanks

Gribouille
[Shield Tablet Android Development] Steel01:
Don't install the nvsystemservices zip. It's really old now and probably overwrote some stuff included in my newer CM 12.1 builds. Reference post #4 of the shield apps thread for current status. Since you installed the old apps zip, you'll probably want to wipe the install and start over to make sure all the right files are in place.

The stylus should work in dabbler. I just tried it on mine and palm detection and pressure sensitivity and all are working. The hub should work off the play store. Console mode is still not working, I've got kind of a hack to simulate it (also in that post in the shield apps thread), but nothing user friendly yet.

[MENTION=4787101]linuxct[/MENTION]: I'm really beginning to wonder if those gapps really are the problem. It seems really weird if it is, but the Google services service is a root level program, so it's possible. Can you try a clean install with the cm gapps and see if there's any problems?
[Shield Tablet Android Development] gribouillees:
Ok Steel01,

I f I understand well (my apoligizes because I'm French), I will install only the package [ROM] [UNOFFICIAL] Cyanogenmod 12.1 for Shield Tablet. I will test if the Controller App and Stylus, then I will install the CM 12.1 GApps from the cyanogen wiki and check again.

I will keep you infoormed on this.

Many Thanks

Gribouille
[Shield Tablet Android Development] Steel01:
Correct, you only need CyanogenMod 12.1 and Gapps. That is all I install and it works well.
[Shield Tablet Android Development] gribouillees:
Hello Steel01,

Many thanks everything works fine installing [ROM] [UNOFFICIAL] Cyanogenmod 12.1 for Shield Tablet + CM 12.1 GApps from the cyanogen wiki.

Just a few things :

1 - UI controller App is a little bit different, so for pairing you have to keep the Nvidia button on the controller until it blinks. No text on the UI saying that.

2 - I have installed Trine 2 and some packages was missing like Google Play, etc.... Once packages installed you can install Trine 2 but there is not sound on the game. So you have to delete the obb file and uninstall/reinstall the game a then it works.

3- Stylus and dabbler works fine, just one thing : When you take the pen out from the tablet there is no automatic proposal for dabbler or other app

4- As already talked, console mode is not available

5- Hub workd fine also

That it for the moment, I will do some more tests a share it.

Thank you again

Gribouille
[Shield Tablet Android Development] ToHellWithGA:
User Profiles

Steel01,

User profiles do not appear to be working properly on the Wifi model.

Even after signing into Google, the first user's name is displayed as "Owner" with a default profile image.

Adding a second user profile does not display the expected new user setup prompts.

Editing either user profile via the Users section of the Settings app is not possible.

Both users can install and run apps and modify settings.

Please advise.
[Shield Tablet Android Development] Steel01:
I don't use profiles, so I don't know much about how it's supposed to work. Comparing against my Nexus 5, things seem to match. Adding a user from the lock screen throws a warning and on accept creates and switches to the user. From user settings, adding a users asks if you want a restricted user (option not on my N5) and requires setting a lock password or pattern before adding. So it appears any differences to what you're expecting is from upstream. If I'm missing something, please point it out more explicitly. Testing was done on a build I'm about to upload, so there's a small chance the difference is there.

I've made a couple changes that got trusted little kernel to work on CM finally. From a user perspective, things might not be any different. The service handles some security stuff, as far as I can tell. So, maybe some DRM stuff might work better. Netflix already worked, so that's why I'm not certain user experience will change. I'll upload that build and update the opening post soon.

Currently in testing is a change to enable selinux enforcing mode. This is required to push this device to cm official. Also in testing is a fix for app2sd. If those two go well, I believe the only possible blocking problem will be the Kodi/Retroarch/etc touch problem. I'll be disabling the wireless controller support for official builds since that has to modify the upstream framework. I'll try to keep unofficial builds with support for it, however. If there's any other problem you all think should be blocking, let me know.

Edit: Build up.
[Shield Tablet Android Development] rusty.gh:
This ROM is really smooth, thanks for the hard work.

Hey one thing I have seen, and I'm wondering if anyone else has? The charging seems to be really slow compared to stock?