yashsingh1/xdaforums huggingface dataset:
[Shield Tablet Android Development] Steel01:
It still happens on 12.1, but not terribly often. I'm still running 12.1 because I use LTE. When I play Netflix videos, I'll get the hiccup every half hour or so. Probably less when fewer programs are running in the background. However, I don't think the problem exists on 13.0. I've played videos with my test tablet and don't think I've run into the issue. But, I don't think I've really stress tested it. Perhaps others could chime in on that.
[Shield Tablet Android Development] Steel01:
Alright, finally made a new build. This is not changed much from the last release, except for upstream CM. Still has the two major outstanding bugs of no cell and no hdmi audio. As always, post any problems you find.

cm-13.0-20160716-UNOFFICIAL-shieldtablet.zip

I tried to do some more work on lte support, but drowned in the log again. I can see the radio getting enabled, but something still isn't meshing correctly. One of these years...
[Shield Tablet Android Development] chispas117:
What Gapps do I use with this?
[Shield Tablet Android Development] :
OpenGapps (Nano) or Banks Dynamic Gapps
[Shield Tablet Android Development] Steel01:
Alright, another test update. This one has a change that should make the Shield Hub (Geforce Now and local gamestream), various benchmark apps, and possibly some exclusive games happier. I've also switched selinux to enforcing. As always, please report any problems you notice.

cm-13.0-20160815-UNOFFICIAL-shieldtablet.zip

And now for the bigger news. I've finally narrowed down the LTE problem. I can do some hardcode hackery to get it working on a personal build (had to hardcode a number specific to my sim card into the android framework and no, I'm not doing more builds for anyone else). I've talked to one of the CM devs about how to further debug the issue and have those pointers in hand. Hopefully over the next few days, I'll be able to come up with a fix. And once I fix that, I'll be flipping the switches to get cm13 nightlies rolling.
[Shield Tablet Android Development] john_matrix:
Hi Steel!

Thanks for your build but it bootloop on my EU Wifi only :(

I have tried:

- Upgrade from LP

- Clean install by erasing everything

- Clean install + OpenGApp

Everytime the same...
[Shield Tablet Android Development] Steel01:
You need to update the bootloader. There are guides around on how to do that. Sometime soon, I'll upload a flashable zip to make it easier.
[Shield Tablet Android Development] john_matrix:
Thanks for the information ;)

I was wondering if the issue was coming from thé bootloader and you have confirmed.

I will report to you soon.

Envoyé de mon SM-G930F en utilisant Tapatalk
[Shield Tablet Android Development] teachmeluv:
Build is running nice. After your announcement I decided to switch from CM 12 to this here again. I took the blob from the latest official recovery (4.2) and flashed it. Everything is running nice after one day of testing.

Just two things to mention:

- battery still is inaccurate on my device. Sometimes it just drains 2% at once. Bitobsession has written something about a dtb file. My tablet is the one with Y01 battery. Is there anything I have to do to have an accurate battery?

- launcher scrolling is not smooth in my opinion. Tried Nova and Nexus Launcher. I can live with that.
[Shield Tablet Android Development] john_matrix:
I have updated the bootloader on my Shield and now it's running very well with your new build (upgraded from CM12) Everything is smooth (with Nova launcher).

I don't have noticed any issue withe battery indicator but I will take a look more deeply this point ;)

Envoyé de mon SM-G930F en utilisant Tapatalk
[Shield Tablet Android Development] Steel01:
*drowning in hex dumps*

Anyways, I was thinking something was off with the battery indicator, but that might just be me using my old first gen lte test tablet. It seems to drain a lot faster than my replacement running 12.1. But I'll regauge that once I actually load this all on my daily driver. I've not noticed it skipping numbers. That'd be *really* fast draining... I use the stock dtb, though. Never messed with any custom kernel (my cm kernel is 99.9% stock).

Not noticed any lag either. Using Trebuchet, cm's default launcher. The only problem I've had is the low mem tracker being over aggressive. I recall that from early testing too. Listening to Pandora in the background; doing other tasks like irc, ssh, firefox, etc; and suddenly poof, no more Pandora. Not more than an annoyance atm since other persistent apps like Juicessh seem to survive fine.
[Shield Tablet Android Development] teachmeluv:
I had a custom kernel some weeks ago and even flashed a custom dtb file. Where to get the stock one? Also included in the recovery image from Nvidia?

But I also remember that I have done this before after downgrading to CM12

Is the dtb file from L different to M?
[Shield Tablet Android Development] Steel01:
The newer stock dtb isn't included anywhere by itself. However, it is part of the blob you can pull from any stock update. And yes, the dtb has significant differences between L and M.

Okay, so I'm about 9 months late finding this. I really wish I knew more about the ril subsystem. Well, about most of the framework and hal systems actually. Seems that icera (the modem that this tablet has) uses a different sim io format than the vast majority of other modems. And the patch to support it still hasn't made it into CM yet. I'm going to look at fixing up the patch and getting it pushed in this weekend before getting nightlies running. The below build should be pretty close to what nightlies will be. Please report any problems you find. To my knowledge, the only remaining problem is hdmi audio, and I'm not calling that a showstopper at this point.

cm-13.0-20160820-UNOFFICIAL-shieldtablet.zip

Edit: In the likelihood that the second paragraph wasn't clear: This build has working LTE support.
[Shield Tablet Android Development] teachmeluv:
So flashing the stock blob from the official M ROM contents the dtb file? Then I think my battery is getting just weak or has damage ?
[Shield Tablet Android Development] Steel01:
Yes it will. And I just uploaded a flashable zip with the 4.2 blob. That should work on the K1 as well, should be the same as 1.3. Link is in the OP.
[Shield Tablet Android Development] teachmeluv:
Can I flash this zip via recovery? Or do I need fastboot mode?
[Shield Tablet Android Development] Steel01:
Through recovery. That's why I made those, to avoid having to use fastboot. With that out of the way, I believe everything could be flashed from the tablet without needing a computer.
[Shield Tablet Android Development] teachmeluv:
Great. Will flash your file asap and check if it will change anything.
[Shield Tablet Android Development] Steel01:
Well, I'm running into some wierd stuff where I can't get stock 4.1 or 4.2 to boot at all on my primary tablet. Let me know if the 4.2 bootloader zip works for y'all. It's not bricked by a long shot, just not booting. Odd.

I've got the TLV patch updated and pushed for review. Hopefully other CM devs/maintainers will test and approve it pretty quickly. Running the CTS on my test tab to see if any other bugs jump out. But hopefully I'll have this all done and ready for nightlies next week. Like right before N drops, go figure.

Edit: Well, stock hates my data partition on that tablet for some reason. May just have to go CM primary then. Just makes it more difficult to cross check stock if I need to for any reason.
[Shield Tablet Android Development] hectoralexgarcia:
How did the lte work for you?
[Shield Tablet Android Development] teachmeluv:
I am not using a SiM card on my shield as I have no use for that. I have it just at home as a replacement for a laptop. On the road I have my smartphone ☺️
[Shield Tablet Android Development] hectoralexgarcia:
It makes sense if you only use it at home...

If all is well with this build, and the lte is recognized... then you should see a sim symbol crossed out at the top right of the screen. Please do let me know if you see it :)
[Shield Tablet Android Development] Isira:
LTE works fine here as far as quick browsing is concerned. It's hard for me to do any speed tests since I'm on T-Mobile's free 200MB plan.

Edit:

Played with CM13 for 1.5 days now. Seems to be as stable as the stock ROM, whereas CM12 was definitely laggy at times.
[Shield Tablet Android Development] :
Used the latest cm13 build for a few days on my k1. No problems so far.

But two things make me wonder: There is a process called "3999" running all the time. What the hell is this? And there is a cm13 theme included (Hexo...) which is not included on my bullhead.

Thanks for your great work.
[Shield Tablet Android Development] Steel01:
3999? That's the name, not the id? And the theme got added recently for nightlies. It's from CyanogenOS, I believe. Don't know anything else specific about it.

Whew, the review finally got merged to enable LTE on this device. I'm running a final pure CM build tonight. If all checks out, I'll push the commit to enable nightlies. The sad part is that I'm already working on N before I got M official... Oh well.
[Shield Tablet Android Development] RichBordoni:
Hey, this might be a bit of a stupid question, but I just want to be totally sure. I just picked my tablet back up after awhile and I'm currently running the 2015-08-24 (12.1) nightly. Is it safe for me to update to the latest nightly through the updater without any problems, or do I need to update something else beforehand? Also, I see that you've already released a few CM13 builds. Are those safe to flash as well?

Thanks in advance for any help!
[Shield Tablet Android Development] hectoralexgarcia:
I updated 12 via ota 3 times already up to 8/22 with no problem whatsoever. However, I have made the change to 13 and have to report that my original shield tablet is running better and more efficient... and LTE is running just fine. Overall a happy camper with CM12 and even more now with CM13.

Edit: battery (original recall version) seams to last longer with CM13, hence the more efficient mention.
[Shield Tablet Android Development] Steel01:
You'll want to update to the latest bootloader first (can use the 4.2 zip in the OP). Otherwise, it'll bootloop or hang (actually don't recall the exact symptom anymore). The latest unofficial builds should be safe, yes. CM Jenkins has the first nightly queued now, should be up sometime tomorrow morning (relative to the USA).
[Shield Tablet Android Development] RichBordoni:
Ahaha, I got kinda impatient so I figured that out the hard way. :p It got stuck on the NVIDIA logo but I figured that that was the worst that could go wrong anyway. The section of the original post about the bootloaders was what caused me to ask the question in the first place. I kinda thought that might need an update before anything else.

Thanks for the help! :good:
[Shield Tablet Android Development] Steel01:
And the first nightly is up. Working fine for me. I've updated the OP accordingly.

Work has started on cm-14.0 like I mentioned a couple posts ago. Haven't actually got it to boot on the tablet yet, but I think I know why. Will see if I'm right tomorrow when I continue testing and tweaking. In any case, it'll be a while before upstream is settled down enough to even release an experimental build anyways.
[Shield Tablet Android Development] magicblack7:
Thanks for your work, man. Can you update the first page with a link to compatible recovery for SHIELD Tablet K1? It's the same recovery of NVIDIA SHIELD Tablet? Or we need a specific recovery for us K1?
[Shield Tablet Android Development] Steel01:
From a software perspective, the K1 has no quantifiable differences from the original wifi only tablet. So official TWRP for the Shield Tablet is recommended.
[Shield Tablet Android Development] davidplz:
I'm using it since CM12.1 and it has been just awesome, better than official firmware

Ty for your hard work

I have a doubt about the default browser included... Could it be possible to have Gello instead the AOSP browser? I have read that it is a mainteiner desition to include Gello...
[Shield Tablet Android Development] Steel01:
I did a test build with Gello and Snap out of curiosity. Looks like both would be good to include. Guess I could go ahead and make that switch. Look for them in either this next nightly or the one after.
[Shield Tablet Android Development] jason.li:
I am a newbie for this. A silly question: how to update the latest bootloader? using "fastboot" command? can you give me a example? Thanks
[Shield Tablet Android Development] Gadgetguy2005:
This happened to me too: updated to the 13.0 nightly and now I am stuck on the nvidia logo.

After doing some reading I realized, maybe I need to update the firmware to 4.2.0

So I got that file, and tried to use adb sideload ...

The sideload process starts but then the Shield tablet (original version) says something about the file not being the right one... So I tried the other file (3.1.1) but got the same message.

Any pointers would be appreciated. Thank you!
[Shield Tablet Android Development] ToHellWithGA:
Is it safe to flash the official nightly over one of your unofficial builds? Amazon does a poor job acknowledging when downloaded content is deleted and claims I've no download quota remaining for several weeks after I cleanly flash a new ROM. Not your problem, I realize, but a dirty flash if possible would be excellent.
[Shield Tablet Android Development] hectoralexgarcia:
I downloaded the 4.2 firmware, twrp 3.02-2, cm13, opengapps, and suppersu... saved to sdcard. Flashed twrp first, then flashed 4.2 using twrp and rebooted, flashed cm13 - opengapps- supersu all at the same time... Working excellent with T-Mobile sim.
[Shield Tablet Android Development] john_matrix:
SuperSU is useless as CM already contain SuperSU binaries and all the stuff ;)
[Shield Tablet Android Development] Gadgetguy2005:
Thank you. Somehow using ADB to copy files to my tablet does not work (ADB does not see the phone - fastboot does).

When I start the sideload process then ADB sees the tablet and then I can send the sideload file (the 4.2.0 update) - but I get an error message on the tablet: footer is wrong; signature verification failed...
[Shield Tablet Android Development] jason.li:
I did the same thing. However, when I flashing the firmware 4.2 or 3.11, I got the error as below. If I reboot the system, the tablet just loop the process automatically.

please advice. Thanks
[Shield Tablet Android Development] Steel01:
Dirty flash over the unofficial builds is fine.

That twrp error isn't an error regarding the flash. It's just saying data is bad. 4.2 is the required firmware version for cm13. Did you wipe caches at least? If caches aren't enough, data may need wiped. Internal SD should be fine as is, though.
[Shield Tablet Android Development] jason.li:
Thanks for the quick reply. I did wipe the cache before flashing.

Even though I ignore the error and continue installing cm13, once its done and reboot, the tablet still enter the recovery and then reinstsall the firmware4.2 automatically. Once its done, reboot and reinstall, no stop.

---------- Post added at 11:18 PM ---------- Previous post was at 10:21 PM ----------

I think I figure it out. In the TWRP recovery, I need to Format Data before flashing recovery. Once I its done, the error message gone, everything works. CM13 has been successfully installed.

Thanks for everyone's help.
[Shield Tablet Android Development] Sjamaan:
Guys, do SD card adopted as internal storage works in this CM13 build? Currently I'm running stock with a 64gb SD as internal and I would love to test this ROM with the same setup.
[Shield Tablet Android Development] Steel01:
Last I tested, adopted storage worked just fine. I don't personally use it, so haven't tried lately. But I don't know of any reason why it wouldn't.
[Shield Tablet Android Development] boswelja:
Can you share a link to the device trees?
[Shield Tablet Android Development] Steel01:
https://gitlab.incom.co/groups/CM-Shield

The tablet is in decent shape. Had a report of it booting on aosp, and I've got it booting on cm as well (after some under the hood tweaks). The only changes needed for compile are a few sepolicy changes that I haven't decided how I want to handle, hence haven't been pushed. Seems the default boot animations are causing trouble, so if you compile a build, you'll want to remove /system/media/bootanimation.zip from the device.

Teaser update for cm-14.0. It boots, has sound, WiFi, Bluetooth, and LTE. Haven't done further testing, so I can't say much further. GPS needs work and the hardware video acceleration likely won't ever work until Nvidia releases official N support.
[Shield Tablet Android Development] boswelja:
Thanks! I plan on building and debugging an AOSP build, because N hype :D. I'll report back here when I'm getting successful builds

EDIT: Many kernel errors that I can't work out have forced me to go to CM builds [MENTION=1416222]Steel01[/MENTION] can you upload your build?
[Shield Tablet Android Development] Steel01:
There really isn't anything to upload yet. That and I've already cleaned that build and am working on Roth currently.

The kernel errors are probably related to this. You'll need to pull in googles arm-eabi-4.8 gcc toolchain. For some reason or another, I can't get it to compile using arm-linux-androideabi-4.9 (aka, the default one for N). And good luck with cm... Internally, we're still using a custom manifest (no links). The official one isn't ready to go yet, hoping that gets fixed within a day or so.
[Shield Tablet Android Development] boswelja:
EDIT: This fixed it, onto sepolicy errors now :/
[Shield Tablet Android Development] boswelja:
[MENTION=1416222]Steel01[/MENTION] can you share your changes to sepolicy?
[Shield Tablet Android Development] Steel01:
[MENTION=5720423]OfficerJimLahey[/MENTION] has a review on Carbon with them, so I'll just link that.

http://review.carbonrom.org/#/c/151/
[Shield Tablet Android Development] OfficerJimLahey:
There is this SEpolicy one as well (the first one only gets it building, the one below allows certain things, like wifi):

http://review.carbonrom.org/#/c/158/

Both commits are a mess right now, I hope to get input on standards at some point so they are in sensible locations (in the right files, in the right areas of the file). And ultimately, get rid of the unnecessary stuff (i.e. the lines currently commented out).
[Shield Tablet Android Development] Steel01:
Yeah, that's why I haven't committed anything yet. Because I don't know what's breaking by removing those rules. Want to do a more thorough investigation of the policy once the hardware level stuff is all sorted out. Will be running the unofficial builds in permissive until then.
[Shield Tablet Android Development] boswelja:
[MENTION=1416222]Steel01[/MENTION] should I be editing init_tn8.cpp?

device/nvidia/shieldtablet/init/init_tn8.cpp:167:18: error: use of undeclared identifier 'service_find_by_name'
[Shield Tablet Android Development] Steel01:
Oh yeah, that's going to need rewritten. You can comment out that entire function. It's needed for console mode, but needs an extra init patch that I haven't even started looking at, so it's unneeded right now.
[Shield Tablet Android Development] boswelja:
[MENTION=1416222]Steel01[/MENTION]

FINAL EDIT: I got the build to work by syncing AOSPs frameworks/base and some packages too, time to test :D

Thanks for all your help :)
[Shield Tablet Android Development] ToHellWithGA:
The unofficial build automatically discovered the official nightly channel and hopped right on. That's the smoothest transition I've ever had on a custom ROM. Nice work!
[Shield Tablet Android Development] boswelja:
After deleting the boot anim, should it just hang on the boot logo until its finished starting?

EDIT: I also get unknown command: [log] twice on install
[Shield Tablet Android Development] Steel01:
No, it should fail over to the default shiny android boot anim.

Those errors prevented me from flashing a zip at all. I've been fastboot flashing the images to test. Though, my latest CM test failed to boot even after removing the boot anim. Probably due to stuff still not synced enough in CM.
[Shield Tablet Android Development] boswelja:
EDIT: running fastboot boot boot.img causes the device to hang.. So CM changed something with the boot img
[Shield Tablet Android Development] :
Any chance you could compile the August snapshot build for us?
[Shield Tablet Android Development] Steel01:
CM is still in a lot of flux. My last couple builds wouldn't even get adb. Give it some time. Software the level of CM doesn't happen overnight.

I haven't considered the device support worthy of snapshots yet. CM13 isn't too bad, but there's still some things I want to fix. Like hdmi audio and background tasks (like Pandora and HoloIRC) spontaneously closing when doing other tasks. Hopefully cm-14.0 support will come much quicker (*without* major missing features...) and I can put more time into fixing the more minor problems like that and get truly stable and feature complete snapshots out.
[Shield Tablet Android Development] Gadgetguy2005:
Hi all, I am a bit stuck here: can please someone give me some pointers?

My Shield tablet is frozen on the boot screen - and sideload does not accept the 4.2.0 update.

What do I do? I did a wipe cache / factory reset but no effect.

Thank you for any suggestions
[Shield Tablet Android Development] ashleyglassel:
Load 4.2 from download mode using Odin.
[Shield Tablet Android Development] Gadgetguy2005:
Thank you for the first pointer.

I connect the tablet - launch Odin. Odin does not see the tablet.

So I have another idea: take the update zip file, copy it (via a USB stick) to the micro SD card and then flash with the CM Recovery.

I am able to get to the flash part - I do see the file, the flash process starts, but then I get again the message I got when using sideload: "Footer is wrong. Signature verification failed".

Am I trying the wrong update file? I have a gen 1 Nvidia Shield Tablet, USA, wifi only version.

I am trying to use the 4.2 update file from the first post in this thread.

That should work, no?

So what could be the issue?

Thank you all
[Shield Tablet Android Development] ashleyglassel:
looks like the file you are trying to flash is corrupted. Can you download it again and put it on the sdcard?

What recovery and what version do you have btw? depending what you have may be causing you issues with MM.

Also if fastboot is working you can also install 4.2 that way. Look in the shield general section for the thread on OTA 4.1 or 4.2 for instructions.

People there should be able to help too if you post.
[Shield Tablet Android Development] Isira:
Odin? Download mode? This isn't the Samsung SHIELD Tablet. :confused:

Instead of using CM Recovery, flash TWRP to the recovery and then try flashing the 4.2 blob again.
[Shield Tablet Android Development] ashleyglassel:
Whoops: confused my devices... I would try fastboot with the official recovery. 4 files to flash.
[Shield Tablet Android Development] Gadgetguy2005:
Thank you all for your comments.

I was able to flash TWRP from flashboot - and I am flashing now the CM 13 nightly plus the apps.

Lets see what happens - the system seems to be booting now :)

....

Thank you all - I am back in business. I really appreciate your patient suggestions!!!
[Shield Tablet Android Development] ashleyglassel:
I would use fastboot to put on the official 4.2. ie put on all the following:

Recovery; boot; system; userdata; staging

The re-root and put on MM recovery.
[Shield Tablet Android Development] Gadgetguy2005:
Thank you. It works now.

This is what I did.

Used fastboot to flash TWRP. (had to be administrator on my PC).

Then flashed 4.2, CM, CM apps from the ZIP files which I copied by hand on my SD card.

Now I am running CM 13 .