yashsingh1/xdaforums huggingface dataset:
[Shield Tablet Android Development] Pariahnoble:
OK I had a nice long post to reply but xda ate it when I tried to post it. So I guess this will be quick in case it does it again.

Clean flash, the cm 12 with kernel included. Gapps minimal with search addon

Also confirm the app 2 SD card on 12 says not enough storage space.

Just the search crashes from the mic but tried on a couple apps, and no mic.

Could u possibly toss me some suggestions for cpu and kernel control apps, Synapse and trickster I'm sure are outdated since I had my Galaxy Nexus

Thanks alot for all ur hard work on this stuff [MENTION=1416222]Steel01[/MENTION] and [MENTION=6411851]BitOBSessiOn[/MENTION] finally feels like this device is going somewhere, with all the potential of the platform I cant wait to see where this goes!
[Shield Tablet Android Development] BitOBSessiOn:
Ummmhhh... I'm on 12.1 and mic and google search works fine... Can't tell now about 12.0... I use FauxClock for cpu and mem tunning. Thnx!
[Shield Tablet Android Development] C0BRA01:
I don't know how I missed it earlier. Thanks.
[Shield Tablet Android Development] C0BRA01:
Sticking with this ROM. Most everything works.

I have tried everything I can think of to get Cellular to work.

Flashed this dirty over stock, an didn't work. flashed it over stock,

and factory reset, flashed it clean, played with the APN's, compared

them to stock, and they are the same.

I have backs ups of everything, and mixed up for a little but which was stock, and not, and got all excited when I saw cellular working, and THEN realized I was on stock again. (I named the backup wrong) Sigh.

Jumping back and forth though, you can really tell the difference speed wise.BitOBSessiOn's CM12.1 is insanely fast, but has a few too many bugs.
[Shield Tablet Android Development] Keithn:
12.1 has all sorts of weird bugs right now. I've built it for both this and my M8 and I've seen issues across both . It did just come out of staging so I'm not too surprised. I've also noticed different bugs between different device trees for my M8 on 12.1 so that's been fun.
[Shield Tablet Android Development] C0BRA01:
Does Verizon lock the boot loaders? I understand that HTC phones have a way to unlock them, but I thought I saw a Samsung phone unlocked on Verizon.
[Shield Tablet Android Development] duanim:
loved --but

Definitely this is the best so far,but, can't move nothing to the sdcard and everything else work.

When back to stock with shaky156 kernel and everything work like us to be before, I'll tell no problems like others have,I just want to try cm12.

Today I try antutu and I got 61226 and before 60868, just for reference and performance,the battery still the same but I don't care,I'm not a big gamer,everything run smooth.

The only wantthing, is that I don't know how to install the latest version of the shaky156 kernel v1.1, I am not a developer,just follow communities and search and watch videos, if somebody want to help to install I will be appreciated. So many peoples said that shaky156 kernel is bad maybe for the OC and GPL,but for me works ok.

So right now waiting for bitosisson kernel with OC and SD fix to try out.

My ST is LTE model

Thanks to all in this community
[Shield Tablet Android Development] albertorodast2007:
Shaky's attitude of not sharing his source is a shame, but aside that I got artifacts and screen flickering using his kernel, I wouldn't recomend it.
[Shield Tablet Android Development] duanim:
Beside for his attitude, artifacts and the screen flickering that I only notice in home screen, playing games, watching video,and browsing Internet you don't even notice, so beto,I wouldn't recommended either, but I like to try something new and everything dependent in performance, stability and what peoples thinks.

Like I said CM12 perfect for me in features, but looking for performance.
[Shield Tablet Android Development] Keithn:
Yeah anything that that isn't a Nexus or a "Developer edition" they make the manufacturer lock or not allow them to unlock it. I had to use an exploit to unlock mine, the Verizon model was blocked from htc's unlock system. We are getting a little of topic though.

Which probably means the gpu needs a voltage increase, or is getting too hot. It gets good performance as is so I wouldn't risk pushing it anyway.
[Shield Tablet Android Development] john_matrix:
Hello!

I have installed CM12 (02.04.2015) on my SHIELD Tablet, everything seems to works properly and there are no more screen "blinking" and less coil whining :D

Only one thing, it seems that the light sensor is not working.

Is it a known non functionnality?

Thanks!

Edit: the battery drain faster than stock (with the same installed applications).
[Shield Tablet Android Development] BitOBSessiOn:
Have you tried with BitO-K v005...?
[Shield Tablet Android Development] Steel01:
Okay, are the only two main problems/complaints about the controller and app2sd? I might take a look at the latter if I ever figure out the multirom issue I'm banging my head against the wall about. The former is really a separate and shouldn't be reported here anymore, same with console mode. Was a bad idea on my part to squash both into one thread. See here for that.

Light sensor not working? As in adaptive backlight? I don't really use it, so I haven't noticed. I'll look at it when I get a chance.

I don't know that I can do much about battery drain. CM and root gives the user a lot of options, so if the user wants to under/over clock or whatever to get better battery life / performance, that's up to them. CM probably idles to a higher performance state than stock by default.

Edit: So I looked a bit into the move apps to external sd problem. I found a similar issue on another CM device and sent [MENTION=6411851]BitOBSessiOn[/MENTION] something to try. My external sd has Ubuntu on it and I don't want to destroy it, so I'm not testing it. If he says it works, I'll merge the fix and run new builds.
[Shield Tablet Android Development] BitOBSessiOn:
Trying out... cross fingers... ;)

EDIT: Now I get no errors... It seems to work ok, but destination folder in SD empty and app still in internal memory...
[Shield Tablet Android Development] john_matrix:
Sorry for the delay but I though it was preferable to make some tests about the battery draining ;)

It is a

lot

better after installing your kernel and reset the tablet (always CM12-04022015 installed)

I think I made a mistake by restoring some applications from a Titanium backup save.

Keep all of you in touch in the future ;)

Edit: if you want to use app2sd, can I suggest you to use INT2EXTV2+ ?

I had done a little script to do it for the HTC Sensation here: http://xdaforums.com/htc-sensation/help/twrp-how-to-create-script-using-sdext-t2986416

The only thing to do is to find the "disk address" of the sd-ext partition on the sdcard in the recovery.fstab and replace it in the script.

I can help if someone is interested.
[Shield Tablet Android Development] LukeMBGB:
installed a few days ago as I don't use most of the tablets gaming features, nor do I use app2sd, the only minor issues i've had is applications that used the browser(hbo go in my case) saw cookies as disabled, I just turned cookies off and on on the browser app, rebooted and it worked. another was that it kept turning the display on when it's charging, making it charge slow as ****, but I got around that by turning off the "turn on display when plugged in" in display settings. I don't know if that is how the setting is supposed to work, or if it was a bug, but that's just my feedback. thanks a lot steel001, and everyone else who develop for this device :D
[Shield Tablet Android Development] C0BRA01:
That's exactly how it is supposed to work. If you don't want the display on, the other option is to turn off Stay awake in developer options. You can also set a tone for when it is connected, so you know it is charging if you don't want the display coming on when connecting.
[Shield Tablet Android Development] michiillo:
Knows anyome why when a I turn off the tab, it turn on herself :crying:
[Shield Tablet Android Development] albertorodast2007:
When you turn off the screen or when you power it down completely? Happens to me but only when I power it down and then l plug the charger.
[Shield Tablet Android Development] Steel01:
New builds up in the OP. No changes on my side, only upstream.

CM 12.1 is out of staging, but hasn't hit nightlies yet. Still wanting to wait on that before I switch over. Reports of the WiFi bug not occurring on 12.1 builds have me hopeful for them, however.
[Shield Tablet Android Development] bkrieger674:
Where can I find the controller app? It is not in the store.
[Shield Tablet Android Development] markymark567:
In the second post... ?
[Shield Tablet Android Development] bkrieger674:
I'm having trouble installing and accessing the nvidia system services files. I install them in recovery, but I can't find where to access them when booting the shield. I see the programs in root explorer, but I only get the options to extract them. How do I get the controller app, and console on the main desktop so I can open the programs?

thanks
[Shield Tablet Android Development] LukeMBGB:
man I nandroid'd back to stock and my screen on time was cut in half, just goes to show how well you guys are doing on the development front :)
[Shield Tablet Android Development] Steel01:
An update for those waiting on CM 12.1. I did run some builds of 12.1, but on those builds, wifi won't connect at all. I'm focused on finishing up multirom stuff right now, so I haven't put much time into looking at the problem. I'm also working on making a unified CM build, so there will only be one ROM for all variants of the tablet. I don't know how long it will be before the next release. Things have been somewhat busy and will remain so for another couple weeks.
[Shield Tablet Android Development] Steel01:
Okay, need a brave wf tester. This is a unified Shield Tablet CM 12.1 build. It runs okay (read, wifi as broke as BitObsessions build, plus no audio [already fixed locally]) on my na_do, but I need to know how it acts on a wf build. On wf, it theoretically shouldn't have any reference to the data stuff. If it does, please link a pastebin or similar to the output of 'getprop' from adb or the terminal emulator.

Another note to everyone. This unified build will only have two variants: wx_na_wf and wx_un_do. I have found no working difference between wx_na_do and wx_un_do. People around here have flashed na on the un and vice-versa and the modems still loaded according to the hardwares locale. I picked wx_un_do instead of wx_na_do (which is what I actually have) to signify that it isn't locked to country.
[Shield Tablet Android Development] Singularity_iOS:
I have CM11 on my phone and was considering getting it (CM12 though) on my Shield. I experience major lag on my Shield and personally prefer CM over stock android. Does CM Solve all these lag and freezing i'm experiencing? The only thing that is holding me back is that I don't want to lose the modifications that nVidia has made to android. I understand I can get the apps back but does everything work? IS there a way to get things like the share menu which has the ability to record and stuff?
[Shield Tablet Android Development] albertorodast2007:
Day and night difference on lag, but not without some sacrifice. No share menu, buggy WiFi controller, no mapping option, buggy HDMI and console mode. Grid, Dabbler and third party conrtollers (PS3 + SixAxis app as an example) work great though. Also, there are alternatives such as Kino Console here http://xdaforums.com/shield-tablet/themes-apps/kino-console-game-streaming-t2962348/post60089226 and thanks to devs (such as Steel and BitO) it's just matter of time.
[Shield Tablet Android Development] Steel01:
I finally gave in and I'm releasing a CM 12.1 build. There is a big known issue in that you can't connect to a new wifi network, however there are workarounds. Upgrading from CM 12.0 will carry forward wpa_supplicant.conf and you will be able to connect just fine. If you want to edit the conf file directly, you can connect. Copy the conf file from another rom should work as well. I think this is an upstream problem. The wifi related part of the device tree has not changed since wifi last worked, plus Bit Obsessions builds based off my old device tree has/had the same bug.

Big change:

I have unified the builds. This will work on all Shield Tablet variants. However, it only differentiates the model name between wx_na_wf and wx_un_do. This is because wx_na_do and wx_un_do is the same hardware. I have verified that data works on these builds on my wx_na_do. However, no one ever volunteered to test my last build, so I don't know what it does on a wx_na_wf. I know it will boot and operate correctly, but I don't know if it will hide all the data related options. If something is not as it should be, let me know.
[Shield Tablet Android Development] C0BRA01:
Guessing that App 2 SD still doesn't work? It's not on the list in OP under known bugs, or is that working now?
[Shield Tablet Android Development] Steel01:
I haven't actively changed anything to do with it, no. I also don't have a card I'm willing to test with either. It doesn't work on Bitobsessions builds either, so I don't expect it will here. But it shouldn't hurt to test and see what happens.
[Shield Tablet Android Development] Pariahnoble:
I'm back on stock for the time being for a few more days, but I found going back to stock, apps2sd STILL doesn't work even with custom kernels, patches and zip fixes, folder mount is the only option I've found that actually works. Stock or cm, nvidia effed up someplace. I'm really hoping ota 3.0 helps but not holding my breathe. I really believe that these roms r our only hope to get this thing to live up to its potential. So far I've really not been happy with my shield but things r certainly turning a corner with all this work. Thanks for your hard hours on this
[Shield Tablet Android Development] BitOBSessiOn:
app2sd is a bit frustrating... because in theory we have the fix but it does not work well... My build includes it if you want to test. Anyway, more work needed here. It's in pending tasks, I have a 64gb card and want to use it... [emoji14]
[Shield Tablet Android Development] FriendlyZombie:
So, can you provide wx_na_wf? also is there any workaround for the wifi issue? Sorry im not very experienced

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

I did copy my wifi configs from wpa_supplicant.conf from an earlier update with my wifi saved. I still can't connect to new networks without going into it though.
[Shield Tablet Android Development] Steel01:
New unified build up in the first post. Only upstream changes, so all known problems persist.

[MENTION=5937868]FriendlyZombie[/MENTION]: It is a unified build. No separate download for wf vs. do.

So, 80 downloads and no one on wf wants to make a comment? Or should I assume that wf is working exactly as intended?

I have one more bug report that I hadn't previously considered a ROM bug. Kodi (and reportedly from other devices some touch games) misdetect the touch screen as a trackball. This makes the programs unusable as no user input is detected. Doing a bit of research, it appears this was caused by a change upstream (like all the way to Google upstream) moving touch handling from the OS to the driver. I'm guessing Nvidia handles this in their stock rom, but didn't push those changes into their aosp (broke there as well). Doing some more research, some devices fixed the problem by disabling stylus modes. I don't think that's a good solution for this device, but I might try it just to see if it makes a difference. Wonder what the chances are that the raydium drivers in OTA 3.0 fix this on their own...
[Shield Tablet Android Development] iamnotkurtcobain:
S5 had the Touchscreen issue too. It was registered as stylus input. They disabled it and Touchscreen was back to normal.
[Shield Tablet Android Development] Gilbot:
I'll give it a whirl on wf tomorrow. I need to see if it has random sluggish moments I have been experiencing with most Roms ?

Edit 1:

So far so good using _wf. Haven't had any random ROM hiccups in performance. I had to flash over a previous build to connect to WiFi (as stated in the op). Only oddity I see so far is that I have mobile networks option in settings, and while it is set to off, I see the icon in my status bar indicating 'no service'. Have yet to test Bluetooth.

Edit 2:

Running very well. Bluetooth with my moto stream works fine. Earlier in the day I set my tab aside for a few minutes and I either accidentally powered it off or it just powered off on its own, I'm not sure, but performance otherwise has been great. Chrome usually gives me the biggest issues with most Roms, but it seems to perform much better with this. Going to give it a day or two more, but I think this is a keeper.
[Shield Tablet Android Development] gomax:
"I had to flash over a previous build to connect to WiFi"

My solution on fresh install from rooted stock was to select WiFi band from Advanced settings.....
[Shield Tablet Android Development] Steel01:
Wf still has the mobile data options? Blast, I'll have to work on that more. I'm trying to hide those when it doesn't apply.

Hey, that power off issue has been noticed by a few of the devs on various ROMs, including stock, as well. Did it happen after you plugged it in? We're trying to track it down, but don't have enough data points to pinpoint the problem yet.

No update on the WiFi issue yet, unfortunately. I've been given a few pointers on where and how to debug it, but the last several days have been crazy busy, so I haven't gotten to them yet. It might be next week before I have time to start running builds and tracing this problem.
[Shield Tablet Android Development] wiQbold:
Wifi issue!? I have delete the wpa_supplicant.conf like you said in the first pst, and now I can create a connection and wifi connect automaticly!?
[Shield Tablet Android Development] imdogdream:
hi thanks for rom!

everything works fine, now i am feeling that i am using real tablet,

second day i am having some issues with touch screen problems (only twice)

it worked fine after restarting it though.

thanks
[Shield Tablet Android Development] LoCo4ChRiSt:
hi im new here

im really wanting to get a nvidia shield tablet next week...i wov cm12 and whould like to root it and put this rom but it looks like there are lil problems...if i root it can i just stay on stock till we get fixes or do i have to put a rom cause it wipes the old one? thx in advance
[Shield Tablet Android Development] Primetime_de:
Hi,

does it work on an EU LTE tablet?

Thanks,

Chris

[MENTION=682245]loco4christ[/MENTION]: Root and stay on stock ROM is no problem.
[Shield Tablet Android Development] LoCo4ChRiSt:
thx fot the help buddy....is there a rooting walkthrough you recomend?
[Shield Tablet Android Development] Primetime_de:
Here you go:

http://xdaforums.com/shield-tablet/development/root-root-nvidia-shield-tablet-lollipop-t2972316
[Shield Tablet Android Development] Steel01:
Yes, this should work on all Shield Tablet variants. I personally have the NA variant, but the hardware between the two is identical. Other people on the EU variant have used this without issues (other than those in the opening post, of course).
[Shield Tablet Android Development] Pariahnoble:
http://xdaforums.com/devdb/project/dl/?id=12450

Called kingroot. I JUST used it on ota 2.2.1!!! Worked easy. Install, run it, it should reboot, run it again, poof!!! Root!! :good:
[Shield Tablet Android Development] LoCo4ChRiSt:
queston

if i root wit kingroot and there is a new OTA is there a chance ill loos e root? also is there a chance a OTA could make where we cant root all together? just dont want to spend all this money and a few OTA from now i got a stock tablet and cant root...wht ya guys think?
[Shield Tablet Android Development] Pariahnoble:
No matter what you can always use a PC to flash a custom recovery, and from there either use nvidias otas or custom ROMs, when nvidia releases an ota, just download the FULL OTA, and flash it in twrp or cwm, then flash supersu, root should never be lost again.
[Shield Tablet Android Development] LoCo4ChRiSt:
once i root cant i use flashify to put the new recovery...can i use twrp or only cwm? im used to twrp havint used cwm in a while
[Shield Tablet Android Development] Steel01:
TWRP works fine. You will probably want to use the one out of my multirom thread as it is newer. I don't know if anyone wants upstream twrp, so I haven't made any builds of it.

I have a new build uploaded and am about to update the opening post. I've made some changes to the unified init script. A few more cell radio related things will not run on wf now. But I still haven't got the radio related things to hide in the menus. Maybe I'll figure it out someday. But for now, there shouldn't be any extra programs running on this versus an old wf build.
[Shield Tablet Android Development] Primetime_de:
Sorry for my noob question, but I might flash this ROM from scratch tomorrow.

What do I have to do to get WiFi work?
[Shield Tablet Android Development] Steel01:
You'll want to back up /data/misc/wifi/wpa_supplicant.conf and restore it after you install CM. I think someone mentioned using Titanium Backup to save and restore WiFi Access Points to accomplish the same thing. I haven't tried that myself, though. Any new networks will have to manually added to wpa_supplicant.conf.

One of these days I'll have time to put in the debugging code and track down this problem. Or if someone has interest and knows how to flash and the basics of programming, I can point you toward where the problem is and where debugging needs to be.
[Shield Tablet Android Development] julien30dusud:
I am in !!! I really want to get cyanogen to be fully working on my shield tablet !!! Feel free to send all informations you have at julien@chabanon.me. :D
[Shield Tablet Android Development] Steel01:
Okay, making it build shouldn't be too difficult now that I think I have my scripts working better. Clone scripts somewhere and don't change the name. Note that this will checkout cm (and twrp/omni) to its parent directory, so create a whole new folder for this. Then in the scripts directory, create a file named devices.txt and put shieldtablet on the first line. Then run './build.all.sh cm'. In several hours, you should have a cm build in scripts/../uploads/$DATE/shieldtablet. Make sure this runs first.

Alright, the problem. Wificonfigstore complains about not being able to set priority 0. That's here. So, logging needs added to setNetworkVariable and whatever it calls to find out what code path it's going down and why it's failing. Should be able to use loge just like the linked line and check logcat after a failed connect attempt. Yay for printf debugging, very time consuming, but it's the only way I can think of to track this down. Oh, and after the first build, you *should* be able to change this line to 'make installclean' so you don't have to wait 2+ hours for a complete rebuild. But this is changing the framework files, so that might not be true...
[Shield Tablet Android Development] adampdx:
So WIFI is iffy, how about LTE? I searched through this thread and couldn't find any information relating to LTE not working. I have an exclamation point where my signal bars should be. Using TMobile, tried reinstalling CM and removing SIM/ rebooting system with no luck.
[Shield Tablet Android Development] Steel01:
I've not had any problem with lte outside of weak signal which happens on stock too. I'm on T-Mobile as well. Which build are you trying? I'll try a clean install of that when I get a chance.