yashsingh1/xdaforums huggingface dataset:
[Shield Tablet Android Development] C0BRA01:
Not sure why, but the tablet zips right along right up until I open Chrome, and then it drops to a crawl.

Anyone else noticed this?
[Shield Tablet Android Development] albertorodast2007:
Not only here, in any 5.0 LP ROM Chrome and Facebook apps make this beast lag like h*ll. Was trying with older versions with no luck. Ended up uninstalling FB and using stock browser, don't care about FB but Chrome is a deal breaker. :(

Guess is the men leak all LP ROMs are having! Even though on my old LG G2 with RenderBroken kernel its not that sluggish.
[Shield Tablet Android Development] Keithn:
I remember seeing that on some other 5.0 ROMs. I can't immediately find any real fix. Try setting off merge tabs and apps in chrome settings, may need a cache wipe, but some people reported that to help.
[Shield Tablet Android Development] albertorodast2007:
I am testing some OOM and LMK settings on Pikachu's 1.6 kernel right now, maybe they'll help with this men leak but I need to be pretty shure they are stable before advising anyone to use them, maybe steel can confirm I'm not doing something stupid with them. :sly:
[Shield Tablet Android Development] albertorodast2007:
This are the settings and I really feel the tablet a lot faster.
[Shield Tablet Android Development] albertorodast2007:
Making some benchs... Before that I was getting ≈51,100 on antutu.
[Shield Tablet Android Development] C0BRA01:
I don't see anything in the play store called Low Memory Kill? is that the exact name?

So this looks like a LP 5.01 issue, and not specific to this tablet? Makes me want 5.1 even more. LP looks OK, but has not been very impressive to me so far.

I still long for the days where the navigation buttons were on the left.

Katkiss implimented this on his Asus transformer ROM running 5.1 SO much better there, than right in the middle.
[Shield Tablet Android Development] Pariahnoble:
I honestly haven't had the lag issue at all. Though I use chrome beta. Dunno if that makes a difference but I have this rom loaded down, viper audio, xposed. And it's way faster than stock on cm.
[Shield Tablet Android Development] BitOBSessiOn:
I think [MENTION=3038260]albertorodast2007[/MENTION] is usig FauxClock? Is it?

---------- Post added at 07:22 PM ---------- Previous post was at 07:17 PM ----------

I've just compiled first full cm12.1 and data works (SIM detection ok), but wifi problem persists. Assistant ok without google apps... So looking for appropriate 5.1 gapps package.

Hard to test without MultiROM working properly :(
[Shield Tablet Android Development] albertorodast2007:
Yep, sorry not to mention that. And superpichu's 1.6 kernel because 1.7 seems to be less responsive on my tablet.
[Shield Tablet Android Development] C0BRA01:
I think your on to something. I installed Chrome beta, and went to a few websites, and it's still running zippy. Sweet.
[Shield Tablet Android Development] albertorodast2007:
I'll try that also and report later.

Reporting back: Lag still exists but yes! Is less frequent. Now I just have to figure out why Gmail sometimes freezes, I guess Nvidia and Google are just like my ex's, they don't do pretty well together.
[Shield Tablet Android Development] C0BRA01:
Uninstalled Chrome, and sticking with the beta. Seems much smoother.
[Shield Tablet Android Development] Keithn:
On my M8 I had to boot once without gapps flashed to get through the setup. After I rebooted and flashed gapps it seemed to work and I had wifi connect. I just finished a build for my shield but haven't tried that yet. Maybe we do need a 5.1 gapps but I didn't see one anywhere to try.
[Shield Tablet Android Development] grv00711:
http://fitsnugly.euroskank.com/?rom=banks&device=gapps
[Shield Tablet Android Development] Steel01:
Sorry I missed this in my last response. I've had trouble pairing it when the wifi was on. So best I can recommend is a fresh boot, wifi not connected, start the controller app and pair right away. *Should* connect. But if it disconnects for any reason, you will have to re-pair. I had it working poking around the launcher and iirc a bit in Retroarch, but didn't try to use it to any great extent. Failure to re-pair is one of the bigger problems with normal wifi interference being a close second.

To everyone else: Wow, I'm getting left behind now... So, personally I don't care about Chrome, but good info for those that do. For 12.1, like I said earlier, I'll wait on CM to start nightlies for other devices before putting much time into switching over. But if someone wants to link a build, please do.
[Shield Tablet Android Development] albertorodast2007:
Just curiosity. What is the exact combination of recovery, root method, nightly, gapps and kernel you are using?
[Shield Tablet Android Development] Pariahnoble:
Unlocked bl then adb flashed recovery, Bogdacutu's multirom twrp,this cm nightly, PA gapps modular nano, stock kernel.

After gapps I flash a viper audio test flash for the nexus 5 that removes audio fx, sets selinux to permissive, and adds some libs for viper. I guess it's not needed anymore as viper has updated. But the new viper apk borks off the notification icon, and only updates some headphone specific ddc profiles. So I use that.

As for kernels, are there any that do a any good on this rom? I'd love to be able to throttle back the cpu to get battery but nothing sticks on this...
[Shield Tablet Android Development] BitOBSessiOn:
I've tried this one and another packs but no luck. [MENTION=2777334]TKruzze[/MENTION] has discontinued their PA GApps compilations, for me best one, so I must look for an a solid alternative (Does anybody know where to find sources?).

It would be fine if each one os us report experience about this.

---------- Post added at 06:53 AM ---------- Previous post was at 06:45 AM ----------

I'm trying from [MENTION=1416222]Steel01[/MENTION] work merging last Nvidia source and perhaps a little modification on kernel params. As he says, cm12.1 is still very alfa, but I've read info about "painless" transition from cm12 on other devices/branches, so I suspect we can advance some work thinkinf of future... I hope we will get good results when we have first nightlies, I have good feelings about... ;)
[Shield Tablet Android Development] Keithn:
It runs smooth but there are a couple major issues I had. WiFi will not save/connect (m8 restored from my Google account so I got WiFi) and if I turn on debugging my PC instantly stops recognizing it (my m8 doesn't do this).

I built it mainly to see if I could and to see if it would even work. I agree 12 is the better option with 12.1 still in "staging" and needing work. Do you know if there is anything more that the tablet needs before it would be possible to get nightlies?

Sent from my One M8
[Shield Tablet Android Development] Steel01:
Nightlies as in official cm nightlies? I don't know what it takes to submit for that. But the WiFi issue seems like a showstopper. I haven't enabled selinux enforcing yet, but have had it in permissive for several builds now. It may be safe to enable. That's all that's coming to mind right now.

To those flashing stock boot images: I'm surprised those are usable. CM init scripts are fairly different from stock, like several stock services don't exist in cm and vice-versa. What you all probably want to do is convince the those maintainers to release builds of their patches against the cm kernel and tree. Or one of you could try.
[Shield Tablet Android Development] kickassdave:
To those mentioning laggyness....

I'm not finding this laggy at all. And I can guarantee you I am normally extremely picky when it comes to the UI smoothness.

I am on US WiFi only variant.

Latest CM version

On multi boot twrp/patch but using only CM (primary) at the moment.

Unlocked bootloader via official method and wiped data/system/cache/dalvik before flashing the ROM.

My only gripe is the controller not working as if we had that too, I'd never go back to stock. Ever.
[Shield Tablet Android Development] BitOBSessiOn:
I suppose that "nightlies" source will be accesible to everyone once they finish staging 12.1 (we are compiling preliminar source). We can only wait for that. AFAIK Official nightlies ROMs will not exist before Shield Tablet get official support in cyanogenmod project, and this can happen never... Please, somebody correct me if I'm wrong.

Sorry if I haven't understood your question.

---------- Post added at 02:58 PM ---------- Previous post was at 02:56 PM ----------

Please, report if you can boot a second ROM without problem ;)

+1
[Shield Tablet Android Development] MiePx3:
Hey guys! I got a quick question:

How do I update to a newer version if I use CM12 as a secondery ROM with multi rom?

I tried to flash it via advanced/multirom/ROM List/CM/flash zip but the settings still shows me a old build number.
[Shield Tablet Android Development] BitOBSessiOn:
You have a prior option (up left, I think...) "ADD ROM", with a wizard, in Multi ROM menu...
[Shield Tablet Android Development] Keithn:
Why could it never get official status? Cm11 was pretty close but had some issues. I was just curious what else this needs before it meets the requirements to be merged and get official nightlies for 12 (if someone is interested and is going to try). It wasn't specifically a question to you, more to whoever knows the status on that.

That was my point about 12.1, it has issues and isn't out of staging yet so the choice Steel made to stay focusing on 12 instead of 12.1 makes sense. And I was just posting my experience with it in it's current form.
[Shield Tablet Android Development] BitOBSessiOn:
Good question... Are there official requirements to be official device in CM... ?? I don't know... I suppose that first step is that it must be a compromised maintainer and a sufficiently mature code... but I do not really know details...
[Shield Tablet Android Development] MiePx3:
So there is now way to update my existing ROM? I have to set up a new one?
[Shield Tablet Android Development] BitOBSessiOn:
In "LIST ROMs", select it, and go into more options to wipe, istall zip, etc...
[Shield Tablet Android Development] Steel01:
I could probably ask [MENTION=4911249]Unjustified Dev[/MENTION] what it takes to go official, I think he's been through it before. I'm not certain I would want to be the official maintainer, though, even if I somehow qualified. I tend to hop around projects and don't really want to be tied down to one. If it's just basic maintainance to keep it running on the latest releases, that might not be too bad.

I run my cm on a multirom secondary. And I didn't notice that updates weren't taking. That's bad... I'm going to go bug [MENTION=4937137]Bogdacutu[/MENTION] now. That explains why some of my testing was completely bogus. Looks like for now, you'll have to keep Titanium Backups of everything and restore them to a newly installed ROM (flashed twice to make it boot).
[Shield Tablet Android Development] timgt:
I just wanted to give thanks to all involved with this ROM. After trying numerous ROMS and every single one of them having stuttering and unresponsive screen issues including stock, I switched to the 3/24 build of this ROM and all my issues are gone!! This tablet is finally amazing. The only issue I have (and honestly I don't even care) is that I have to manually connect to WiFi on first boot but after that it never disconnects when the screen is off like some other ROMs were doing and stays connected until I reboot which is awesome.

I even had screen and lag issues with the build of this ROM prior to the 3/24 build. I believe 3/19 was the date but I'm not positive.

I did flash this kinda strange if that made a difference at all. I used multirom and added it as a new ROM then cleared cache and dalvic and then flashed it over itself then cleared cache and dalvic again and then flashed it over itself one final time and cleared cache and dalvic again before finally booting. So I basically flashed it 3 times and have yet to see even the smallest of hiccups in the way this thing runs.

Anyway thanks again for the rock solid perfectly stable ROM, I won't be switching to anything else from here on out.
[Shield Tablet Android Development] MiePx3:
Thats what I did, but the build number stays the same.
[Shield Tablet Android Development] Steel01:
I just reported this to Bogdacutu. He's going to look into it later today. I have a feeling it's a twrp/multirom problem, but I don't know enough of what it's doing under the hood to debug and prove that.
[Shield Tablet Android Development] BitOBSessiOn:
If I don't missunderstand and you see the same number in ROM LIST this is because that's just the ROM name... taken from the first one you flashed... you can change it... Can it be ? You can confirm build number in Settings / Device Info into running ROM.
[Shield Tablet Android Development] Steel01:
The build number I'm referring to (and the one I think MiePx3 is seeing) is in settings->about->CyanogenMod version. I know I flashed 03/24 a few days ago, but mine still reads 03/19. Time to reflash, I guess.

Edit: in case people wonder: yes, I did test the new build on primary and on a new secondary before releasing.
[Shield Tablet Android Development] MiePx3:
Yeah, still the same.

After setting it up as a new ROM it shows the lates build number in the settings app.
[Shield Tablet Android Development] albertorodast2007:
OMG! You are so right [MENTION=5558549]Pariahnoble[/MENTION]!

Made a clean install using this gapps http://xdaforums.com/android/software/gapps-google-apps-minimal-edition-t2943330 and it's day and night diff. No lag, no freezes, no struggle, and hopefully no Google Service wakelock, (I'll report on that later). [MENTION=1416222]Steel01[/MENTION] could you please add them in the op, if there's no problem with that.
[Shield Tablet Android Development] Keithn:
Yeah almost did for 11. Doesn't really make a huge difference if there are working builds in the end. Didn't know if you were going to try.

Also with multirom you can swap Roms around okay it just doesn't seem to like flashing into anything other than the internal so you should be able to swap and flash. Would be nicer if it worked properly but that might be an immediate work around until for right now of you need to.

Sent from my HTC6525LVW
[Shield Tablet Android Development] C0BRA01:
The Chrome tweak is well worth it too. I used it on the beta, and it sped way up.

http://lifehacker.com/speed-up-chrome-for-android-with-this-settings-tweak-1555623190

---------- Post added at 10:30 PM ---------- Previous post was at 10:26 PM ----------

Did the same thing,and wow, it really is faster. That, and the tweak to Chrome Beta, and I would almost swear that it's faster on my tablet, than my desktop. This tablet is flying now. :) I wonder if that tweak works on the desktop version.

Answer; Yep. :)
[Shield Tablet Android Development] albertorodast2007:
Reporting back. Now tablet sleeps like a baby.
[Shield Tablet Android Development] C0BRA01:
Yeah, mine is running nice and fast now.

Unfortunately, LTE is still not working. It acts like the data switch is turned off. I have the LTE in the upper right corner, and it shows a good signal. Just the data switch will not stay on. Toggle it on, leave that menu, and go back, and it is off again.

[MENTION=1416222]Steel01[/MENTION] have you had a chance to look at my Logcat?

Thanks.
[Shield Tablet Android Development] john_matrix:
Thanks for your CM12 Steel01!

I will install it on my stock Wifi SHIELD ;)

Do I have to install some nv apps with a package or something else as GAPPS? Or can I directly install the nvidia applications from Play Store?

Thanks!
[Shield Tablet Android Development] Steel01:
[MENTION=5347975]Cobra01[/MENTION]: Sorry, I haven't yet. And this weekend is pretty packed. I'll see if I can get to it, though. Something that came to mind: is data disabled when you reboot/reflash from stock? If it's enabled and you reboot/reflash, does it work?

To those wanting the alternate gapps in the OP: I'd rather not. I'm just linking the official ones. If people want leaner ones, that's a user decision and out of scope here.

For the tablet to work, you only need the ROM. Most people will want gapps as linked in the OP or alternatives others have talked about in the last couple pages. Some Nvidia apps are on the store like the Shield Hub and Dabbler. Console mode and the controller app are not, however. I'm doing work off and on to get those working, but it's slow going. Controller mapping also is not, but I'm personally not bothering because I don't use it and tincore seems to cover what people need. Though, if someone wants to research and implement the framework changes needed, I'd be glad to include them in my builds.
[Shield Tablet Android Development] C0BRA01:
You may want to check out post #2 for the add-on apps.

As far as GAPPS is concerned, we just found out the Cyanogen GAPPS seem to cause lag. The Minimal GAPPS work fantastic.

Check out this post. http://xdaforums.com/showpost.php?p=59708757&postcount=148

Also for any Chrome problems, use the beta instead of the regular one as it has been causing extreme lag.

Also this tweak makes Chrome Beta even faster. http://lifehacker.com/speed-up-chrome-for-android-with-this-settings-tweak-1555623190
[Shield Tablet Android Development] C0BRA01:
I thought about that. Yes, Data was probably disabled at the time with the stock ROM. I have not tried going back to stock since I got yours running. I thought when it was wiped, it was wiped. I formatted every partition from recovery before going to this ROM. I wanted it absolutely clean when I installed yours. You think that somehow the setting was maintained through all that? How about the reverse. Can you turn OFF data on yours? If you switch it off, go out of that menu, and then return to that menu, is it still off? You have me thinking about it from a different angle now. lol. Backing it up now. It occurred to me that I had reflashed it at one point, and then it was running. I will try it after I flash it back to stock, and let you know.

Update #1, Data is working in stock trim. Left turned on. and rebooted into recovery.

Update #2 Data NOT working after reflash back to Cyanogen. :(

I know what you mean about the GAPPS, but something must be wrong with those to cause such a difference. Oh well, as you said, we can go elsewhere for the GAPPS.
[Shield Tablet Android Development] BitOBSessiOn:
[MENTION=1685546]C0BRA01[/MENTION], which switch do you exactly mean?

I have no problems with mobile data/LTE, turning on/off... using same gapps you use, but I've compiled cm12 20150327 sources merging SuperPichu and last Nvidia kernel... I can upload boot.img or entire ROM to somewhere if you want to try.
[Shield Tablet Android Development] albertorodast2007:
I guess Cobra means the on/off switch. I don't think that has something to do, when you flash a ROM all settings are deleted.

Would you mind to share that kernel [MENTION=6411851]BitOBSessiOn[/MENTION]?

Though they clearly say it's not needed on CM12 and for the ones using Xposed, this module helps a lot with mem leak. AFAIK it's not the only mem leak present on our beloved OS. http://xdaforums.com/xposed/modules/xposed-fix-lollipop-memory-leak-t3065296
[Shield Tablet Android Development] BitOBSessiOn:
Attached (flash via fastboot). Nvidia update to OTA 2.2.1 and SuperPichu code for KEXEC_HARDBOOT (NON functional... testing). This is part of my local experiments... I'll update my github when I have something solid and interesting.. if this happen sometime... :P
[Shield Tablet Android Development] C0BRA01:
There is a toggle for LTE data.

---------- Post added at 07:39 AM ---------- Previous post was at 07:33 AM ----------

the LTE data on/off switch. It looks like it turns on, but you leave that menu,and come back, and it is toggled off again. I have wiped the tablet three times, and did a clean install. Formatted every partition from TWRP. LTE, 3G none of them work.

Sure I'll give it a shot. Whole ROM please.
[Shield Tablet Android Development] BitOBSessiOn:
Uploaded...

---------- Post added at 06:01 PM ---------- Previous post was at 05:28 PM ----------

Features:

Based on CM 12.0 [MENTION=1416222]Steel01[/MENTION] branch

Latest Nvidia OTA 2.2.1 source merged

Experimental

Changes in kernel configuration:

Multicore scheduling optimizations

CIFS / SMB2 FS with cache support

AES and other cyphering algs HW acceleration

Added CFQ, DEADLINE IO Schedulers (CFQ Default)

To Do / Test:

KEXEC_HARDBOOT for MultiROM support

A lot...

Download:

wx_na_do: https://mega.co.nz/#!VdcHXIrC!ad2cX058ugZ0Mz-YDfwT_pGV-zGHsWllVMTZS7SfUYc

wx_na_wf: https://mega.co.nz/#!RAdiUT4K!lf3KKONA6piSogv3YVfkNq6UafvSbKtJErOR32rc9xA

Notes:

Tested with "Mininal Edition" GApps by [MENTION=5772029]jajb[/MENTION]:
[Shield Tablet Android Development] C0BRA01:
Thank you. :) I will give it a try when I get off of work, and let you know how it went.
[Shield Tablet Android Development] Pariahnoble:
OK so I feel like a ****, but, any chance of a WiFi only version to test out?
[Shield Tablet Android Development] Pariahnoble:
No no [MENTION=5995633]FoxyDrew[/MENTION] I meant [MENTION=6411851]BitOBSessiOn[/MENTION]s build. Sorry I didn't specify.
[Shield Tablet Android Development] BitOBSessiOn:
Uploaded:

https://mega.co.nz/#!RAdiUT4K!lf3KKONA6piSogv3YVfkNq6UafvSbKtJErOR32rc9xA

*NOT Tested
[Shield Tablet Android Development] Pariahnoble:
Wow thanks man. Looking forward to it. Thanks for ur time man.
[Shield Tablet Android Development] djharris10:
I'll text it out as soon as it's done downloading, I'll keep you posted in the result
[Shield Tablet Android Development] djharris10:
I think I figured out how to auto-connect to wifi on these builds. I just flashed that cm12 build that BitOBSessiOn uploaded for the wifi only Shield Tablet, and I have enabled Scanning always enabled in the advanced settings, but I am going to insert a screenshot so you can see this for yourself. I just turned it on, and rebooted my tablet. It automatically connected to my WiFi.
[Shield Tablet Android Development] Pariahnoble:
[MENTION=5880696]djharris10[/MENTION] I can confirm that trick to work on the last cm build by [MENTION=2941722]steal01[/MENTION] as well. Auto connects no problem. I'll update whether or not it auto reconnects if it loses connection as well. My Web sucks here (I'll have 10mb a sec on the 31st =) ) so if it stays online and I don't have to keep going into the WiFi settings I'll know.
[Shield Tablet Android Development] C0BRA01:
Sorry to say, it didn't work. Tried it both dirty, and wiped clean. It had me going for a minute, as the Data toggle switch stayed on when I flipped it, and then left that menu, and came back, but nope. :(
[Shield Tablet Android Development] BitOBSessiOn:
That's correct, I've just tested it in my LTE RoW (using my last wx_na_do 20150328) and I confirm that it works. I assume that's the default setting because I've not changed it. I have kept in mind this bug when merging Nvidia source and revising kernel params, but, sincerely, I suspect that probably it can be simply an update in last CM 12.0 source. Perhaps [MENTION=1416222]Steel01[/MENTION] can confirm if he compiles again syncing repo and test it.

Good news, anyway ! ;):good:

---------- Post added at 12:17 AM ---------- Previous post was at 12:13 AM ----------

It's so weird... In stock does it work properly... ? GApps version? Using MultiROM...? What stock have you flashed before... stock 2.2.1 ?
[Shield Tablet Android Development] djharris10:
It wasn't just your build by the way. I was using the March 24th build before I flashed your version (by the way, great work in your version) and it did the same behavior for me. Auto connected to wifi after I enabled the scanning always enabled setting, so it could just be that in the stock build it's off or it's just a bug with it being off not auto-connecting, either way, it works when I enable that particular setting, it's weird but hey no complaints here!