yashsingh1/xdaforums huggingface dataset:
[Shield Tablet Android Development] Pariahnoble:
Had really bad audio bug on ota 3. Like before on 2.2.1 but much worse. Viper doesn't even help. And I had noticed that when multitasking, if I switch do a different t app. It would kill the previous one nearly everytime..... No matter what apps they were. Stock kernel wasn't doing this.... Flashed back and forth a couple times to be sure. Thought I'd let ya know how it was going. (wifi, primary, internal, no multirom)
[Shield Tablet Android Development] Sarge29490:
I agree as well, there's audio stuttering (at this point i am wondering audio stuttering can't be fixed with software), but having no problems with previous apps closing while switching... (lte, no multirom)
[Shield Tablet Android Development] BitOBSessiOn:
OK, we'll try some adjustments in 031... Thnx
[Shield Tablet Android Development] BitOBSessiOn:
With same tool you used before? It should work in the same way. Which app?
[Shield Tablet Android Development] wawyed:
Yes same app but I was using a different kernel. The app is cifs mountmanager.
[Shield Tablet Android Development] drewski_1:
Are you using Xposed? I saw the "Optimizing" after each boot when I had APM+ installed & activated. I uninstalled and booting went back to normal.

If Xposed, try deactivating all modules and adding back 1 at a time. YMMV
[Shield Tablet Android Development] jayandvic:
Quick question. I was wondering what the difference was in the KU folder between 024 and 030? I am running the 024 now but was not sure if I should be on the 030. I am running the 16G wifi usa stock ota 3.0

thanks!
[Shield Tablet Android Development] koop1955:
KU 030 was compiled using the OTA 3.0 source. Have you updated?
[Shield Tablet Android Development] jayandvic:
Yes, just did the other day. So go ahead with 030 then?
[Shield Tablet Android Development] koop1955:
I would suggest so. I took a while to flash it myself. After flashing I wiped caches (might not be necessary, but what the heck...) and as expected took a bit for first boot and then the optimizing apps wait. But seems smooth and working.

Cheers.
[Shield Tablet Android Development] jayandvic:
Cool thanks.

---------- Post added at 12:35 PM ---------- Previous post was at 12:24 PM ----------

Wiped cache first and after. Flashed like a champ. running great. Thanks again!
[Shield Tablet Android Development] RedFuryJr5:
oh my gawd.

I dont know what is going on. Since 11.7 I have been having a ton of issues with Temasek. I have clean flashed the rom and kernel multiple times and it passes. I have used minimal gapps and zero gapps. However I consistently have apps crashing. Specifically Chrome and Google Play Store crash frequently even after flashing the rom again on clean wipe. I have also tried clearing the cache and data of those apps with no luck! PLEASE I LOVE temasek and have it on my note 3, dying to get this working right on my shield tablet. Thanks in advance for you help and big thanks for all your work!
[Shield Tablet Android Development] BitOBSessiOn:
Let's see if v12.x better... working adapting OTA 3.0 sources.
[Shield Tablet Android Development] RedFuryJr5:
thanks for the reply and I will have my eyes peeled sir. You are the man.
[Shield Tablet Android Development] slxar:
After flashing KU-030 on stock OTA 3.0, when hdmi cable connected, it cannot enter console mode. Clicking the console mode is just the same as mirror mode.

Furthermore, volume btn and track pad don't work after flashing KU-030
[Shield Tablet Android Development] duanim:
Hey Bitob I am back KU30 with stock nice,but I having some problems with the WiFi does not connect itself,manually turning on and off.

Where are the chance for the OC version .

The tablet looks good with new video calibration,thanks God that I did mention in feature request in nvidia forums

Gracias por resucitar esta tablet. beastiality
[Shield Tablet Android Development] Pariahnoble:
It's a gapps issue. I use the delta gapps. You can find it in the main gapps thread here on xda. There's been issues with play services. Flashing a gapps package from 5/15 or older. Booting up, rebooting and flashing current gapps package solves it.

Also tkruzze official gapps are back called tkgapps now

---------- Post added at 12:45 PM ---------- Previous post was at 12:42 PM ----------

In settings, wifi, set "wifi always scan" to on.

It will auto connect now

Also, if you DO NOT have a 5ghz router, set wireless band to 2.4 instead of auto, it will connect faster and run quicker (slightly) by not looking to try 5ghz. By default the shield looks for 5ghz over 2.4 for gamestreaming
[Shield Tablet Android Development] duanim:
Pariahnoble thanks did everything that you said same results, maybe a software issues from last OTA for the wifi on LTE model tablet according to the shield forum.

So maybe Bitob can do something about it
[Shield Tablet Android Development] Sarge29490:
I have LTE model and there are no issues with the wifi here, after the last update, for me, there are no problems except the audio stuttering...
[Shield Tablet Android Development] BitOBSessiOn:
BitO-KS-033 available

Compiled with Sabermod 5.1 Toolchain and other optimizations.

Audio seems to go better.. almost on my system compared with older configurations... Deep test needed to confirm.

This time we have only one flashable zip to all models (OTA 3.0), tested with TWRP 2.8.6. You have to see confirmation of kernel is flashed for your ST model.

As always, feedback welcome. Thnx!
[Shield Tablet Android Development] Pariahnoble:
So far so good on ku33 ota 3.0, installed easy as pie (that unified installer is gonna be a blessing!) definatly has that snap back to it again, compared to stock.

No reboot at first boot, haven't had the optimizing thing come up more than once. Wifi connected just fine. (although I do have "scanning always available" turned on, I found I needed it on to auto connect, stock stock) (I'll try with out it to see if it auto connects fine) no multirom primary

Edit: auto connected fine with "scanning always available" turned OFF. It took a little longer but connected just fine.
[Shield Tablet Android Development] RedFuryJr5:
hey so I installed 12.1 with a clean install. Wiped everything then installed 12.1 and the recommended gapps. Havent been able to test the FCs but more importantly now my battery is not detected charging. I know the charger is working (tried other devices) and the charging LED on the shield turns on but the rom does not show it is charging on the battery indicator and if it is low it still spams power warnings. Also I have the WiFi version and it has a sort of annoying indicator saying I have no sim. Thanks again for all of your help!
[Shield Tablet Android Development] duanim:
So far so good thanks BitoB again.the problem with the WiFi resolved.

Antutu: with KU030=58387 and with KS033=58489 . Booting 26 second .

Cuando la version de OC. I think it doesn't hurt.

Aqui desde la Florida USA un venezolano agradecido por tu trabajo de collaboration.

LTE model ok
[Shield Tablet Android Development] NaminatoR1254jaime.sier:
Which is the latest working version of the kernel for stock 221?
[Shield Tablet Android Development] Sarge29490:
OTA 3.0 and KS-033 best coupling so far, automatically detected and installed kernel for LTE-EU, everything is smooth and for the most part couldn't reproduce audio stuttering in the usual cases...
[Shield Tablet Android Development] MarceloSiciliano:
Im having problems with ks33. I'm having RR and the screen is flashing very fast!

Edit: tablet reboot when i was writing this post lol
[Shield Tablet Android Development] Pariahnoble:
Do you by chance know what antutu score the stock STOCK ota 3 gets?
[Shield Tablet Android Development] xperia64:
Whoa. KS-033 appears to have fixed the 48000Hz audio issue I was having with MXPlayer. On stock kernel and KU-030, the audio would crackle and eventually cut out on the whole tablet for 10 seconds. Can't reproduce it with the same files. I didn't think it could be fixed with a kernel update.
[Shield Tablet Android Development] riganta:
Hi Guys,

Come back after a few weeks of testing a couple of rom. I have settle on Temasek 11.7. I see this morning that kernel 33 has come out. Thanks. I will be testing that this evening after work. All is sweet and the shield is working perfectly hardware wise. I have one issue with 'google play services' that now keeps crashing basically all the time; to a point where it has become unusable.

Step One: Wiped out the entire tablet

Step 2: Installed fresh Temasek 11.7

Step 3: Google play service start crashing. In the middle of a game (Modern Combat 5), watching a movie (Netflix), installing an app, and plugging and unplugging the charge cable.

I tried to upgrade Google play services - No go. In the middle I had wiped dalvik and cache.

Downgrade Google play services via uninstall updates - No go. Again wiped dalvik and cache.

I do not have that on stock. I can't get myself to leave Temasek build and would like to be able to fix the issue.

Anyone has had that issue? If yes, could you fix it and how?

Thanks
[Shield Tablet Android Development] xanthrax:
Google services should have nothing to do with the kernel

Check the dpi, revert it to stock

Sent from my Darkside of 1+1
[Shield Tablet Android Development] BitOBSessiOn:
Try with Delta GApps and/or new Temasek v12.1. Anyway, Temasek questions, in ROM thread, please ;) Thnx!
[Shield Tablet Android Development] BitOBSessiOn:
Have you used TWRP to flash it ?
[Shield Tablet Android Development] xanthrax:
is he using ks33 on RR (whatever is that)?

I flashed through twrp multirom , no issues, the only thing is that the multirom must be flashed again, though not a kernel issue I guess, testing, looks great so far, keep it up pal!

ohh... figured out, RR could be... random reboots

sent from my Darkside of SHIELD Tablet
[Shield Tablet Android Development] BitOBSessiOn:
I think Random Reboots occur when some kind of conflict happen between governor selection. Nvidia provides its own performance control tool, based on userspace governor... I suspect that if you change userspace by ondemand, conservative, etc... depending on tool used (Kernel Adiutor, Faux control, ....) some RR can occurs.

I've tested that with Interactive governor and there is no problem (ondemand sometimes RR)s. The same with userspace. I don't know what Nvidia own controls tool does, but possibly, depending on which option you have selected (User own energy control, Performance, Balanced...) and what you are tweaking with third party tool (Adiutor, Faux...) RR's can occur. Or perhaps, it's simply a bad implementation of some governors in Nvidia code...
[Shield Tablet Android Development] BitOBSessiOn:
You don't need to reflash Multirom.zip after kernel zip if you flashed multirom before. Yo can simply go to advanced options > Multirom and inject boot sector again ;)
[Shield Tablet Android Development] xanthrax:
Meh... I thought that option was automatically... But it wasn't [emoji41]

Sent from my Darkside of 1+1
[Shield Tablet Android Development] wawyed:
Did you find out if there is a problem with cifs/smb mounting or is it something in my end?

Anyone else having problems with cifs/smb?
[Shield Tablet Android Development] BitOBSessiOn:
Have you tried with KS-033 ?. CIFS module is included in unified flashable zip
[Shield Tablet Android Development] wawyed:
Same problem.

I also found this in the app thread that I'm using:

"No such device".

A: Your current kernel or rom lacks the necessary CIFS support. Try to find a matching kernel module (cifs.ko) or use a rom with explicit CIFS support.

http://xdaforums.com/showthread.php?t=756158
[Shield Tablet Android Development] MarceloSiciliano:
Yeah i did, but now I flashed Temasek and everything seems to be normal again
[Shield Tablet Android Development] lupick:
I've tried to install latest 0.33 to its twrp on my wx_un_do but even if installation was successful after the reboot kernel was stock one.
[Shield Tablet Android Development] BitOBSessiOn:
CIFS.ko (module) is integrated in kernel. Have you flashed with latest TWRP ? Have you tried with another app ? (I can't download CIFS manager you refer)
[Shield Tablet Android Development] BitOBSessiOn:
Have you used latest TWRP 2.8.6 ? I suggest you using the one from MultiROM thread.
[Shield Tablet Android Development] Sjamaan:
The same happened to me with TWRP 2.8.6 not multirom patched.

I will try again with latest TWRP sometime later
[Shield Tablet Android Development] xanthrax:
yes, that one works fine [emoji6]

sent from my Darkside of SHIELD Tablet
[Shield Tablet Android Development] wawyed:
I just flashed KS-033 with TWRP since it wasn't working with the other recovery, unfortunately the problem persists. I tried a different app but no results. I also tried mounting through command line but same error. I can see that the module is in the lib/modules folder but for some reason is not working.

EDIT:

With a bit more digging I think I've found out what the problem is. It appears to be that the kernel is missing fscache support which is required by the module.

<3>[ 1170.274428] cifs: version magic '3.10.33BitO-KU-033-g05df338 SMP preempt mod_unload ARMv7 p2v8 ' should be '3.10.33-BitO-KS-033-ge48eb68 SMP preempt mod_unload ARMv7 p2v8 '

<4>[ 1170.274915] cifs: Unknown symbol __fscache_read_or_alloc_pages (err 0)

<4>[ 1170.275013] cifs: Unknown symbol __fscache_relinquish_cookie (err 0)

<4>[ 1170.275085] cifs: Unknown symbol __fscache_unregister_netfs (err 0)

<4>[ 1170.275199] cifs: Unknown symbol __fscache_maybe_release_page (err 0)

<4>[ 1170.275240] cifs: Unknown symbol __fscache_uncache_all_inode_pages (err 0)

<4>[ 1170.275254] cifs: Unknown symbol __fscache_read_or_alloc_page (err 0)

<4>[ 1170.275283] cifs: Unknown symbol __fscache_uncache_page (err 0)

<4>[ 1170.275319] cifs: Unknown symbol __fscache_register_netfs (err 0)

<4>[ 1170.275347] cifs: Unknown symbol __fscache_write_page (err 0)

<4>[ 1170.275690] cifs: Unknown symbol __fscache_wait_on_page_write (err 0)

<4>[ 1170.275730] cifs: Unknown symbol __fscache_acquire_cookie (err 0)

EDIT2:

I've managed to get it working by manually loading all 3 modules:

insmod fscache.ko

insmod md4.ko

insmod cifs.ko
[Shield Tablet Android Development] BitOBSessiOn:
Yes, this is INFO... I will revise module configuration and dependencies. Thnx.

I suggest you using one of tested apps, like ES Explorer:

https://play.google.com/store/apps/details?id=com.estrongs.android.pop

Or FX Explorer:

https://play.google.com/store/apps/details?id=nextapp.fx
[Shield Tablet Android Development] wawyed:
Check my edit I've just got it working by manually loading the modules:

insmod fscache.ko

insmod md4.ko

insmod cifs.ko

There must be a way of loading those modules at boot time.
[Shield Tablet Android Development] BitOBSessiOn:
modprobe command is looking for /lib/modules, not for /system/lib/modules...
[Shield Tablet Android Development] wawyed:
Easy fix hopefully :D
[Shield Tablet Android Development] duanim:
No I didn't do it.
[Shield Tablet Android Development] estanenmi:
hi bito.... i have issues on last 3.0 ota.. and stock kernel... my speakers come hot and smell burn... any idea?

Enviado desde mi SHIELD Tablet usando Tapatalk 2
[Shield Tablet Android Development] Pariahnoble:
It's a known issue with ota 3. Something nvidia did is causing that in some cases. The only thing they (nvidia) has said on the issue, is to keep the volume low or revert back to ota 2.2.1 until they issue a hot fix, because it was known to nvidia to actually damage units..... (this was posted by nvidia on their GeForce forums)

I know I use viper audio and haven't had the issue myself. Or any audio popping, very little distortion. It may help.

But again be careful to keep the volume low, because nvidia themselves knows it will physically damage the speakers (there is one posted case of some melting) (thanks nvidia!)
[Shield Tablet Android Development] BitOBSessiOn:
KS-034 available

Increased HD Audio buffer and revised compilation parameters for Sabermod TC and better Cortex A15 support.

Unified OTA3 and CM12.1 flashable ZIP versions. Revised installation scripts to run on older TWRP and probably other custom recoveries. Testing needed.

Thnx.
[Shield Tablet Android Development] dsapac:
I am on Temasek build 11.7 I tested 0.33 and 034 CM build but tablet is bootloop-ing. I have changed TWRP recovery to TWRP recovery from multirom. At the I am dirty flashing back 11.7. It shows script success but in the [ ] it doesn't shows nothing. Example if I flash rom when it's successful it shows [ /system ] If this helps you. Or maybe it's just me. Maybe should some users which are on CM test this build. Thanks again for your development.
[Shield Tablet Android Development] michiillo:
can i install it in ota ROM?

I'm interested in this kernel but I don't use cm ROM :confused:
[Shield Tablet Android Development] BitOBSessiOn:
Not tested by me, I think so, but it's easy to try... If it does not work, flash stock boot.img again from fastboot.

Perhaps, any fellow can confirm.

I'm preparing a new versión. It will be ready soon.
[Shield Tablet Android Development] BitOBSessiOn:
It may be possible, but not yet. Working in MultiROM and SDFix (no kernel stuff) for app2SD, and then... OC.

We add the petition to the list ;)
[Shield Tablet Android Development] michiillo:
A new version?

It will have overclock? :o

And may be we can turn on all four cores at time? ;)

Last night I installed the cm12 and this kernel but I got a surprise :(

It can't put all cores to work :crying:

Any ways this ROM with this kernel are pretty nice

Good job friend.

I'm sorry if I wrote something bad, I don't speak full English :p
[Shield Tablet Android Development] MarceloSiciliano:
Can you implement voltage control BitOB?
[Shield Tablet Android Development] BitOBSessiOn:
I have focused in Battery life and multicore scheduling optimizations in 005 release. Any new feature like L2TP VPN protocol. MultiROM code has been patched, but not yet successful tested... Preparing the path for future features like OC/VC... I've reviewed code, but I have to learn how to...

Feedback welcome, thnx ! ;)
[Shield Tablet Android Development] MarceloSiciliano:
Thank you! Im gonna flash it as soon as i get home! Thank you for developing for the shield tablet!
[Shield Tablet Android Development] drewski_1:
i tried on rooted stock ROM and it hung on the Nvidia boot screen. flashed back to SuperPichu's modded stock kernel.
[Shield Tablet Android Development] BitOBSessiOn:
Ok, thnx I will try to see what's necessary to boot stock :good:
[Shield Tablet Android Development] BitOBSessiOn:
This kernel has CPU_HOTPLUG enabled, so... what do you mean with "all cores to work"...? Do you want to force 4 cores permanently working ?
[Shield Tablet Android Development] 2me3:
Plz plz plz implement headset media button support. This is a major limitation of stock kernel. Then we can use pressy headphone jack buttons instead of the awful stock power button
[Shield Tablet Android Development] JuaanGarza:
Yes friend please force 4 cores permanently working :)
[Shield Tablet Android Development] michiillo:
Yeah!

I want to active 4 cores while playing but it only can active 3 cores, don't care which app do you use.
[Shield Tablet Android Development] BitOBSessiOn:
AFAIK, you can only control second, third and fourth core (three ones you see), because first one is always on. You cannot disable first one, because it's technically impossible... If no CPUs... we have nothing to do... :p
[Shield Tablet Android Development] michiillo:
I want ton turn on all cores at time and record while playing and three cores are not enough.

I want four cores at same time while I playing and no ome shoud to turn off.

Can i do with this kernel?
[Shield Tablet Android Development] MiePx3:
Yes.

All cores are working. One of them is always one. This one is invisible.

The other 3 are working.

I hope I got this right. Please correct me, if im wrong!

/edit

I just tried BitO-K 4 and 5. But both crash with CM12.1 with "android system has stopped working".

Im not familiar with logs, does android make them if it crashes?
[Shield Tablet Android Development] albertorodast2007:
Did you wiped dalvik + cache after flashing kernel? I am currently using Bit's kernel under cm 12.1 and have no issues.
[Shield Tablet Android Development] MiePx3:
Yeah, I always wipe both after flashing something.

I tought maybe Xposed for 5.1 could be interfering, so I flashed the latest CM12.1 again, to make sure the framework isnt causing issues.

But same result.
[Shield Tablet Android Development] albertorodast2007:
Hmmm now I remember, I didnt have this kernel installed, I was experimenting with CM 12.1 and restored stock kernel, you are right [MENTION=6510665]MiePx3[/MENTION], it F/C as soon at it boots and randomly soft reboots.

What are the changes from the kernel included in your experimental CM 12.1 and this versions [MENTION=6411851]BitOBSessiOn[/MENTION]?
[Shield Tablet Android Development] BitOBSessiOn:
BitO-K is compiled for 12.0. My CM 12.1 has its own BitO-K version...

I'm preparing new full 12.1 builds...
[Shield Tablet Android Development] BitOBSessiOn:
Perhaps somebody in Steel01's CM 12.1 build can try out... I will try to test by myself in Temasek 12.1... but I have to do some adjustments before... Thnx
[Shield Tablet Android Development] dsapac:
OK thanks again. I will be at home tomorrow and I will try other roms with your kernel. I only have OTA 2.2.1 and 3.0 and Temasek build on sd card. I didn't test OTA 3.0 because of strange bugs that ate reported on official forum. And I like CM more. I run it on all my Android devices.
[Shield Tablet Android Development] BitOBSessiOn:
It's needed to use insmod instead modprobe. Perhaps in a script in /etc/init...
[Shield Tablet Android Development] BitOBSessiOn:
I will prepare separate zips if unified CM one does not work. If it does not work then it would be a problem related to OTA 3.0 sources update.
[Shield Tablet Android Development] BitOBSessiOn:
Individual zips for each CM model available to download. Tested wx_na_do on Temasek v12.1, flashed ok and it works ok.

EDIT: CM unified zip file deleted because script problems.
[Shield Tablet Android Development] xanthrax:
KS 34 successfully flashed on blisspop, more testing will follow

sent from my Darkside of SHIELD Tablet
[Shield Tablet Android Development] duanim:
Flashed in stock

Antutu:KS34#57867-KS33#58489-stock#58889. IWill test again

Change settings to performance and full mode in power control.

I was testing in low battery 9% and plugged, not charging, playing MK X,gets pretty hot and reboot, I will test again with full charge.

HD audio OK sound more powerful .WiFi connection faster at booting.

LTE model
[Shield Tablet Android Development] duanim:
Test again full charge Antutu:#58927 good

I think the wire cable from Nvidia is not good, I did charged with lg g pad wire cable and it charge pretty fast.

So far so good thanks BitoB again .
[Shield Tablet Android Development] Shorty88jr:
KS-34 and KS-33 Kernel not flashing

Since the kernel files were unified I have not been able to flash them. The last kernel I was able to flash was the KU-30 wx_na_wf kernel. When I flash the 33 or 34 kernel it says install completed please reboot script succeeded: result was [ ] but it doesn't actually flash. When it boots up it says the name of the kernel I had before not the updated one it says I flashed. I have tried the new TWRP 2.8.6.0 and the modified version from the multirom thread but I am not running multi rom I had it at one point but flashed over it because I stopped using it. I have the WiFi model shield tablet with 3.0 OTA any help would be appreciated thanks.
[Shield Tablet Android Development] BitOBSessiOn:
Before Success message you must see a prior message informing about your specific model (WiFi), indicating that it has been properly detected. If you don't see this message about your WiFi model some error is occurring. Do you see this message?
[Shield Tablet Android Development] Shorty88jr:
I do not see any message about the model. I am attaching a google drive link for a picture of what happens maybe it can help: drive.google.com/file/d/0Bwhcnn8OcgeIU0J4SzVyRUxPNUk/view?usp=sharing