yashsingh1/xdaforums huggingface dataset:
[Shield Tablet Android Development] adampdx:
I'm using the 5/20 build. I, too, suffered from poor service on stock. But the LTE was stronger than any WIFI connection I could get more than ten feet away from a router. And a question about the WIFI. I read that you have to use a back up configuration file for WIFI, but I found that if I sign into a network with no security I don't have a problem. When I have to enter a password I get the "Failed to Connect" notice. I guess my question is, is the config back up only for secured networks?
[Shield Tablet Android Development] Steel01:
Okay, I'm doing more looking into the wifi problem. BitObsessions builds work, mine doesn't. In theory, the only remotely applicable difference between his base build and mine is the kernel config. I'm pulling his defconfig changes and running a build tonight. I'll see if I can connect to wifi then. Either way, this is still a weird bug.

[MENTION=4414036]julien30dusud[/MENTION]: You might want to hold off on the long chore of getting all that set up and compiled. This might be an easier path to finding a fix.
[Shield Tablet Android Development] Steel01:
Well, if I pull BitObsessions kernel defconfig changes, WiFi works. I'm in the process of narrowing down which flags 'fix' the problem. I'm thinking it's using hardware encryption and key storage. Which means there's a bug in software key storage and this just masks it. But once it get the code straightened out, I'll push the changes and run a full build. Should be out later today or sometime tomorrow.
[Shield Tablet Android Development] Steel01:
Singling out the config change is more difficult than I expected. Then update 3.0 dropped. All in all, it's going to be a bit more time before I get it merged in. I'll try to get back to it tomorrow afternoon or Monday. I'll probably release an experimental build with 3.0 vendor libs around the same time.
[Shield Tablet Android Development] MaddMaxx636:
Very minor and very big issues

I flashed the newest "nightly" on the my Shield tablet and it works really well except these issues.

1. Touch sometimes goes out or requires a harder press on display

2. Phantom touches (very RARE but still happen)

3. Crashes very often

4. WiFi didn't work right away. I had to connect to a unsecured network

5. CPU MAX/min settings do not stick (example: I set the min CPU speed to 50MHz and it kept putting it to either 1GHz or 1.5GHz. Was doing the same thing for max speed. Installed SetCPU and still didn't work 100%) (also the governor interactive kept firing up to the MAX set speed and staying there)

5. kept overheating. Had to shut down many times to let it cool down (I think the reason it kept overheating is the reason above)

6. Internet was really slow (Might be due to my internet speed)

I understand that some users may post things like this but i was just putting my issue report in to see if anyone else is having any of the same problems so they can get fixed.
[Shield Tablet Android Development] chispas117:
At first I had troubles connecting to WiFi but it worked immediately after I restored my WiFi networks via titanium backup

---------- Post added at 08:57 AM ---------- Previous post was at 08:56 AM ----------

This ROM kind of makes me want to get the LTE version of the shield
[Shield Tablet Android Development] Steel01:
Bug reports are good to see. Always good to have more information.

For 1 and 2: Have you ever seen this when your tablet was not plugged in? We've talked among the devs a bit about a problem we've seen on the hardware on any rom (or not even booted). Basically that the device can't handle 2 amps of power during operation. All kinds of odd things like making it difficult to move the bootloader selection, random sleeps of death, touchscreen going flaky, etc. But only when plugged in. Unplug the tablet and everything works great again.

3: Can you elaborate? I use this as my daily driver and the only thing I see crashing is Firefox and I didn't think that was a rom problem.

4: Working on it right now. Should have a fix released today or tomorrow.

5 and 5: Ya know, that makes sense. I've run into the overheating problem a few times and had to reboot to get it to reset whatever went wrong. It also tends to overheat while charging in use, but I think that happens on stock as well and is related to 1 and 2. I'll have to look into this more when I get a chance. If you have time, can you try one of BitObsessions builds (non-overclocking, then overclocking enabled [don't have to actually push it that far, though]) and see if clock settings stick? If the non-overclocking one sticks, no need to load the overclocking build.

6: I've had no problem with this. My 2.5 MBps download comes through just fine. I'd have to run iperf again to get exact numbers, but I've pushed at least 5 MBps over wireless and I believe 25 MBps over wired on it. Wired might be capped by USB2 as well.
[Shield Tablet Android Development] MaddMaxx636:
Bug reports reply

1 and 2. Happens while unplugged and plugged in (charging)

3. When i say crashing. I mean that the device will reboot and as if the kernel voltage controls are set to low

4. When i say the Max/min speeds dont stick i mean like them i try to set the max and min speeds they either dont set or they set but dont stick and reset to kernel default max/min speeds
[Shield Tablet Android Development] Steel01:
Well, nevermind. The build works. WiFi still doesn't always connect the first time, but it hasn't taken more than three tries for me on this build.

The changes involve cpu scheduler and object allocator changes. Which seems to indicate to me that there's a race problem somewhere. This isn't truly a fix, it's a mitigation. I'm hoping once Nvidia releases the 5.1 aosp sources, I'll be able to start over and not have this problem in the first place. I'm uploading the build now and will have the OP updated shortly.

Edit:

Okay, well I built wrong. I meant to do this later, but I guess it's reversed. This is a build with the new libs from Nvidias OTA 3.0. It's marked experimental because I can't be sure nothing broke. The little I played with it before seems to be smoother, though. I wouldn't recommend installing this over an old build. Wipe data or use a new multirom secondary. I'm currently working on a build with the old libs to release as official.

Edit 2:

New build up in the opening post. It also doesn't always connect the first post, but try a time or two more and it should then.

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

Well, I thought I had the wifi problem figured out. Ran a full build overnight. And it won't even boot... Back to square one. This shouldn't be this difficult. :sigh:

Edit: Hold that thought. Nothing boots via multirom now. What did I do?
[Shield Tablet Android Development] Steel01:
Alright, another test build with stuff from ota 3.0. This one should have the wifi problem really fixed. Problem is that I fixed it with a sledgehammer (importing the entire frameworks/opt/net/wifi from nvidias l-r4 and tweaking 'til it compiled). I'm in the process of trying to narrow down the differences between nvidias aosp and cm 12.1 to what actually broke wifi. But I need some other testers to tell me if this actually works or if I'm wasting my time looking here.

Edit: [MENTION=4602366]MaddMaxx636[/MENTION]: Have you seen a reboot when you haven't tried to change the min/max cpu clock? I'm trying to narrow down what the problem might be since I've never experienced the problem myself. But if this isn't an isolated problem, it's a very high priority one.
[Shield Tablet Android Development] kegsys:
Will test when able

Still awaiting my tablet, will test it when I'm able.

Thanks for the diligent work Steel01.
[Shield Tablet Android Development] MaddMaxx636:
Are you asking if it reboots after i change the min/max CPU speeds? If so no! After i try/attempt to change the min/max i does not stick or set and resets to kernel defaults. I haven't had any reboots lately just overheating and touchscreen problems.
[Shield Tablet Android Development] Sidonicus:
150527 Build

First off.... cracking Rom ! For mine almost there. I've just flashed the latest update and now showing build date of Wed May 27 14:36:33 .

Build #: cm_shieldtablet-userdebud 5.1 1 LMY48B 48ce3414f1

I'm calling the WiFi problem as being still current. Connected OK but after first reboot all settings cleared out. When your running a static IP LAN a real pain in the ass.

Being in AUS (yup I imported this from US- not for sale in AUS) I have the LTE data icons up but am happy to live with this on my WiFi only device. Happy to wait for a unified build or OTA to sort that out.

Else I've not been able to trip up the build, very good stuff !!!

onya Steel !
[Shield Tablet Android Development] Steel01:
That's odd. But probably due to my sledgehammer approach to the problem, I don't think that happens on the normal cm builds. Can you try the one in the opening post (after a data wipe or in a new multirom secondary, I had problems switching between the experimental and normal builds)?

And yeah, I'm still trying to figure out how to hide the lte data stuff on the wf models. There shouldn't be any extra data programs running in the background for you, though. I think I got all that turned off on boot.

Edit:

Well, that massive patch brought back the WiFi doesn't auto connect on reboot bug as well. Yeah, I really need to prune it down. I'm pretty convinced the problem I'm looking for is in this part of the framework now.
[Shield Tablet Android Development] Sidonicus:
Wiped and installed the 150525 build from front page.

Can pin down the issue more now. Can configure WiFi on static IP and connect no problems but without rebooting if you toggle the WiFi off and then back on all the settings (IP/Gateway/DNS1&2) are cleared out and have to be re-entered.
[Shield Tablet Android Development] Sidonicus:
Confirmed WiFi is fixed in current build. Static IP settings wont stick but got around that with DHCP. Had slight problem with installing .apks fix by:

Settings > Apps > Click on the menu and then select Preferred install location.

changed that from "Let the system decide" to "Internal device storage"

Else..... rockin CM on the Shield!
[Shield Tablet Android Development] bosou:
well im thinking of changing my mood into something like this..

going to try. but may i know any know bugs?

using the LTE variant USA.. flashed with ROW version for now.
[Shield Tablet Android Development] Steel01:
The known problems are in the opening post. Really, the only major problem is some WiFi flakiness. And I have a 'fix', I just need to narrow it down. Been working on the initial Shield TV support mostly the last couple days, so I haven't taken time to finish this up yet. Also, this is a unified build. Only one zip for all variants. And there is no difference between row and na, so the build identifies all lte devices as row. It works as expected.

[MENTION=3010509]sonid[/MENTION]icus: Static IPs don't stick on the build in the opening post or the one a few posts up? That's interesting... I'll have to look into that once I finalize the encrypted network connection fix.
[Shield Tablet Android Development] Steel01:
I probably should have posted this before, but here is the full wifi patch I made. It appears to completely fix connecting to encrypted networks, but it breaks auto connect (remember that bug?). I might have time later this week to finally get to breaking it down, but if someone else is interested in taking a shot at finding the necessary fix in there, be my guest. Once that's straightened out, I'll release a new build. And it should be pretty nice too, the newer libs from OTA 3.0 seems to smooth things out a lot.

Yes, most of my time has still been on setting things up for Shield TV builds. I think I just about have things whipped into shape, though I think I have another revision of my build scripts I want to make. But hopefully once a board opens up here, I can spit out builds real quick. Unfortunately, I can't test until my pro edition ships next week.
[Shield Tablet Android Development] Steel01:
Well, I'm starting to poke at that patch again. Not getting very far very fast, though.

On another note, someone on the portable side reminded me about prism and some of the settings I want to expose. So I'm starting to research how to add a new menu to settings and allow switching it on and off there. I see how to do translations via overlay, but not how to add new functionality (like echoing 0 or 1 to the /sys entry). Anyone around here happen to know how to do that?
[Shield Tablet Android Development] Steel01:
I think I finally solved the blasted wifi problem. I'm running another build overnight to pull in another couple fixes for other stuff. If that passes a basic checkout, I'll upload it tomorrow and link it in the opening post.

Also, of interest in this build will be my progress mentioned here. Unfortunately no progress further than that, but I'm sure some people will want to try it as is. Next step after my brain cools off after fighting that stupid wifi bug for months will be to actually start work on that control app I've been talking about for several posts now...
[Shield Tablet Android Development] Steel01:
Alright, new build is up in the opening post. I've also updated the known issues list. If I'm missing something there, please let me know. I'm going to update my posts in the shield apps thread to explain how to use the wireless controller stuff in this build. Well, as much as it does work anyways...
[Shield Tablet Android Development] Zuzuitu:
I flash it like 2 times but now i cant charge my tablet.

First time i leave it over night and it charged till 90% and after that it didnt charge at all. Now, second time i flash it doesnt charge at all, what is wrong ?

The led is on, means the power enters, right ?
[Shield Tablet Android Development] Lltp:
Same for me. The previous release worked just fine. I also have the problem with Temasek's.
[Shield Tablet Android Development] bluejay2345:
I seem to be having the same problem. The LED light is on but the tablet doesn't appear to charge.
[Shield Tablet Android Development] Steel01:
Weird... I just checked mine and it was 3 minutes 'til full and charging. Okay, something to try for those with the charging problem. Take note of the battery percentage when you plug it in (settings->battery for those without the numbers in the notification bar). Then let it sit for several minutes. After that, reboot to recovery (twrp preferably, don't know if cwm has this) and check the percentage in the header there. If it's higher, the device really is charging, but cm doesn't realize it. I expect this is the case.

Sorry for not getting another build out already. My Shield TV came in and I've been working on the twrp and cm port for it. Once that calms down a bit, I'll finish verifying the wireless controller stuff and run a release build. Newer upstream stuff may fix the charging stuff too.
[Shield Tablet Android Development] bluejay2345:
I let it sit for a while as you suggested and the battery does seem to be charging. The only problem seems to be that the OS is not aware that it is charging. There is no charging indicator in the notifications section and the battery report indicates that no charging has been taking place.
[Shield Tablet Android Development] Lltp:
I've just seen the percentage decrease while "charging". That never happened before even with games or films, let alone just sitting on my desk doing nothing but displaying the screen (now it has lost 4%). TWRP confirms that. If the screen is off, as I did earlier, it does charge but at a rate nowhere the usual one (with stock or the prevous CM ROM).

There is also another weird effect that occurs while charging: the UI becomes sluggish. If I unplug the power cord, the UI becomes responsive again. This could be due to charge accumulation one the capacitive screen.

Please also note that I had the exact same problem (no charge, sluggish UI) with Bito custom kernels (I tried all of them, except Bito-K).

I have the RoW LTE version of the tablet, here the power outlets are at 220V. I know that nowadays, electronic devices are able to stop the charging from software to avoid overcharging the battery (which is really important to keep a good capacity over time). The circuits responsible for that are more or less efficient, which could explain the slight charge. But that's only just guessing.

I can try flashing whatever you want to help to solve this issue.

---------- Post added at 11:14 AM ---------- Previous post was at 10:20 AM ----------

I'm not sure I was clear about the kernels: CM 05252015 is working very well but if I flash any of the Bito kernels on top of it, I see the very slow charging behavior that was described and the UI slugginess.
[Shield Tablet Android Development] Steel01:
Problems when the device is plugged in seem to abound on whatever rom you're on. I've seen it on stock too. The best theory I've heard is that the traces aren't all shielded against 2A. When it's plugged in, those traces get jitter and cause various problems.

New build up in the opening post. I saw in BitObsessions thread that newer builds don't have the charging problem. So I'm hoping this build will fix that for all of you. And I'll echo his statement that if it doesn't, try clearing caches, and maybe data to see if it corrects itself (backups are your friend to restore if it doesn't help). I did a basic wireless controller pairing test and it worked fine, but unfortunately only as root. I can run the pairing app as non-root, but the pairing didn't complete. Will have to investigate that later. Basic info has been updated in the appropriate thread.

And like I've said in all my other threads, I'm taking a couple weeks off. Life caught up and I need some time away. If any problems come up, BitO and most of the other rom maintainers can get ahold of me.
[Shield Tablet Android Development] lostboykev:
I have installed the 6/16 build. First time tester on this rom. There seems to be a problem with charging the device. It does not want to charge using the full available amps of the power brick. I'm using a meter which shows me getting about .46 amps. When you plug in the device it goes to approx full amperage capacity then dips down and stays at .46 amps. So far I have not been able to circumvent this. This is a big issue and hopefully will be fixed soon. If you need me to cat any logs I am willing upon request.

As for the experience. There seems to be noticeable lag on browsers. Walmart, XDA, hhgregg are sites I visited recently with lag like a mofo. Then again I experience this same lag on stock. I can't believe this is still an issue considering the power this device is capable off. I've tried a couple of kernels that are supposed to help with adjusting cache but nothing improved in real world performance scenario. If somebody can refer me to a post or your own explanation on what causes this; please do!

Edit: charging issue was apparent on stock kernel and custom kernels.
[Shield Tablet Android Development] Lltp:
Same problem unfortunately: slow charging and no charging animation. It is so smlow that it is actually discharging while in use.
[Shield Tablet Android Development] iamnotkurtcobain:
I gave my Shield Tablet to my mother (with official 5.1 update). I couldn't stand the jankiness and the bad battery (and weight) of the device. Such a powerful Hardware and such bad software/drivers.. Never a nvidia device again.
[Shield Tablet Android Development] jtorress:
Thank you for showing this nice tablet some love! I just bought one used and was happy to see its getting support from some devs here.
[Shield Tablet Android Development] Steel01:
New build uploaded. This might be a placebo effect, but I thought I noticed my most recent portable build running smoother. Then I think I'm noticing that on my tablet build as well. We'll see after a couple days of usage.

Well, I'm trying to ramp my development stuff back up again. So, please report any problems you find. I've been using this as a daily driver for months now. But I don't gamestream much or use the wireless controller for this device.

One problem to not report: Slow charging. This was due to a DTB change Nvidia made for their 3.0 ota. This file is not controlled or changed by any custom rom. If you want the old behavior back, you'll have to flash an older official dtb back. That being said, I've not had much of a problem. For my normal browsing or video watching usage, my tablet charges faster than it drains. I've only seen a couple times where heavy gaming usage drains it faster than the charger can supply.
[Shield Tablet Android Development] imdogdream:
hi, is there any way to installl cm and use controller?

thanks
[Shield Tablet Android Development] BitOBSessiOn:
You need a DTB and compatible kernel. If you have never updated to OTA 3.0, you need an older kernel (not updated from OTA 3.0 sources). If you are using any modern custom kernel (like BitO-K) then you need to upgrade your DTB (with stock one or provided one on BitO-K thread).

If DTB and kernel are incompatibles you get charging problems (no charging notificaction, no connection to PC, etc...).

More info here.
[Shield Tablet Android Development] jtorress:
Battery life is way better than blisspop. This is a nice rom. Thank you.
[Shield Tablet Android Development] kongha:
Great rom (20150720) that works well with my tablet (16gb/wifi).

I do wonder if I can disable the sim card function in someway? I ve now a notification in my status bar that says that I dont have any sim card installed.

Keep up the great work.
[Shield Tablet Android Development] Steel01:
I've tried to find a way to dynamically disable the sim card settings, but haven't been able to yet. They're there because I only release one build for all variants. Under the hood, none of the cell data functionality should be running on your WiFi only model, though. It's just extra setting option and the notification icon that I can't make go away.
[Shield Tablet Android Development] Kekskruemeltorte:
Does the Rom have nvidia code into it ?

Nvidia added a killswitch in ota 3.0 to deactivate devices after the rma regarding the battery problem.

Looks like users are not needed to send back the old device, but nvidia deactivate the old one if the new one connects to the internet.

So want to use this rom on the tablet if it haven't included the nvidia killswitch.

Thx & Greetings
[Shield Tablet Android Development] Steel01:
3.1 has the kill switch. This is using 3.0 blobs currently, so it should be safe. In theory, updating to the 3.1 blobs should be safe too, but I'm going to careful about that.

The custom ROM devs are looking into what the kill switch really is and will be working around it. It might be possible to keep stock on the old one at your on risk as well. But I expect at the very least, running custom ROMs will be safe.
[Shield Tablet Android Development] Kekskruemeltorte:
Thx for the info, ignore my PM ;)
[Shield Tablet Android Development] Steel01:
So far, testing of my latest internal build is going well. I pulled in the blobs from 3.1 and a couple init script changes. Several minutes of video didn't cause the high pitched screeches like it used to. I can't say for certain that it's completely fixed, but it at least doesn't seem as often as it used to be. Also, to the guy asking about D3 BFG, it shows up on the store for me on this build. Don't know if that was from something I changed or if Nvidia relaxed the store checks on it a bit.

I'll continue testing this weekend and likely will release tomorrow or Sunday.
[Shield Tablet Android Development] Steel01:
Okay, I'm a few days late, but it's out. Using the 3.1 libs. The controller pairing app is the one from the new portable update. I did notice the audio screeching if I just upgraded my current install. But the few minutes I tested a clean install, I didn't hear it. Now, that's not a thorough test, but if you have audio problems, try a factory reset or a new multirom install and see if it still happens.