yashsingh1/xdaforums huggingface dataset:
[Shield Tablet Android Development] boswelja:
Bootlooping? And it was fixed by flashing the stick recovery?? That's really weird
[Shield Tablet Android Development] xanthrax:
Yes it is, could be related to what tweaking kernel application he was using before flashing
[Shield Tablet Android Development] :
Yes. I turned on the tablet -> nvidia logo shows up -> stayed like this for a while. did not show any sign of life -> device turned itself off -> turned itself on again -> and it went on and on like this.

This is what a bootloop is, isnt it?

To fix it I flashed the 4.3 recovery image from nvidia image via fastboot.
[Shield Tablet Android Development] boswelja:
I think I had that problem a while ago with another device, somehow twrp got corrupted :/
[Shield Tablet Android Development] xanthrax:
Panama papers issue is world wide open, some people just want to be rich... Corruption

Sent from my Darkside of Oneplus 3
[Shield Tablet Android Development] mirrin:
my k1 just started that was sitting there then suddenly it rebooted stayed at the nvidia logo then rebooted again and came bac to lockscreen.
[Shield Tablet Android Development] drewski_1:
the "recovery image" is not just recovery partition. it's like the full Nexus Factory Image - bootloader, radio, system, etc
[Shield Tablet Android Development] boswelja:
Ohhh, the stock OTA images. I thought it was just the recovery like twrp XD
[Shield Tablet Android Development] hacktrix2006:
Since using K7-006 on my K1 and the DTB that is with said kernel, i haven't had a single reboot at all. Still working lovely and PCMark battery test from 97% - 20% took 3 Hours 45 minutes which is fantastic. Nice work there OP nice work.

Just one question if i use the Nvidia Dev images to restore the tablet will this override the custom DTB?
[Shield Tablet Android Development] BitOBSessiOn:
AFAIK no DTB explicitly flashed in latest OTAs (maybe via any blob). You shouldn't need to flash any DTB except in case you use KX (OC) version... or you come from older bootloader, blobs, etc...

TBH... In my tests... I've tested KX7 with NO DTB flashing... (after flash stock full OTA 4.3), and no RR, etc... (but back to K7 in a short time...). So my recommendation is: Don't flash DTB except you get any weird behaviour (USB, charging, RR, etc... beause your personal flash history...). Anyway... latest K7 should be equivalent to latest stock 4.3 (Not KX7).

Maybe [MENTION=1416222]Steel01[/MENTION] can give more info about this point.
[Shield Tablet Android Development] Both Barrelz:
[MENTION=6411851]BitOBSessiOn[/MENTION] Can I just ask. How comes the kernel reports to Cpu managing software that it has higher then stock overclocks?

I realise that this is something you no longer support as a feature, I recently changed to the k7 version from the kx and I have noticed that the Cpu managers still report higher available clocks, even though both kernels only actually support stock 540mhz. Just wondering.
[Shield Tablet Android Development] BitOBSessiOn:
Did you flash KX7 DTB...? Have you flashed K7 DTB again after going back to K7...?
[Shield Tablet Android Development] Both Barrelz:
I have never flashed any of the DTBs, so it's safe to say that it is currently stock DTB. Is that the reason it gives false clock increments? It's not really a problem to be honest.
[Shield Tablet Android Development] hacktrix2006:
The only wierd behavoir i was getting before flashing the DTB was very slow charging with the Charger for the Shield Tablet (World one) i mean like 10+ hours, after flashing yours its like 2-3 hours tops or even quicker. I have the full recovery image that comes with the blob file which is flashed to staging partition should i need it.

Currently now messing getting the tablet set back up after wiping the tablet back to stock with said images just to get adoptable storage to work (Nothing to do with your kernel) more on how adaptable storage is stored on the data partition. So its now rocking 128GB of SDXC with 35% of that as adaptable storage with 90mb/s and 30mb/s Read/Write speeds.
[Shield Tablet Android Development] m0nt3s:
Your F2FS Support works!

Sorry I've been away for a minute, I started taking night classes to help me become more like you devs lol. Any ways I did an ugly, ugly hack job using your Z-image as twrp's Z-image and borrowing the f2fs binaries from a google nexus, and mickey mousing the fstab's. I got it to sorta work but I have to troubleshoot why and how. I was able to get the /cache and /data partitions converted over but I lost my external_sd card, I think it's becuase /dev/block/mmcblk0p23 is the same for data and the sdcard. I'll keep playing with it but if you or any one else wants to try it or help troubleshoot it, i have the hacked up boot and twrp .img. So the good news is that with only the /data and /cache converted on the OTA 4.3 it benchmarks almost as high as Bos's noguat, I think the sabermod and linaro toolchains make up the difference. I'll be on more often and would appreciate any kind of advice or tips to get f2fs-all working but your awesome Z-image made it happen, thanks Bit and every one else, keep up the good work, we're almost there!
[Shield Tablet Android Development] Both Barrelz:
[MENTION=7002998]m0nt3s[/MENTION] That is a pretty awesome score. I wish I could be of some help to you, but half of what you were talking about went completely over my head (by a few miles). Good luck.
[Shield Tablet Android Development] m0nt3s:
[MENTION=6284095]Both Barrelz[/MENTION] , it's easier than you might think. I'll upload what i've managed to piece together with TWRP, thats the last obsticle. I used Assyyad's kitchen to swap out whatever, http://xdaforums.com/chef-central/android/best-android-roms-editor-assayyedkitchen-t3410545 I've gotten it narrowed down to just switching out or finding the right recovery.fstab or combination, if you have some time and a windows computer it's just trying the different combinations.
[Shield Tablet Android Development] :
I have now tested different versions of this kernel, k and kx with and without the dtb. Still the same major performance loss
[Shield Tablet Android Development] m0nt3s:
Take it from a guy who soft bricks his shield daily, make a decent backup with twrp, download the nv-recovery from nvidia and your good to go. As long as you can get to the bootloader which is just power + vol down, you can use nvidia's recovery which overwrites any and all changes if worst comes to worst. 95% of the times I bootloop, i can get back to recovery and restore... so don't be afriad, flash that dtb, download kernel auditor, or 3c toolbox and change some settings. Here's a copy of my build prop to get you started. I'll post the additional here.

#

# ADDITIONAL_BUILD_PROPERTIES

#

ro.carrier=unknown

ro.config.notification_sound=OnTheHunt.ogg

ro.config.alarm_alert=Alarm_Classic.ogg

dalvik.vm.heapstartsize=12m

dalvik.vm.heapgrowthlimit=157m

dalvik.vm.heapsize=628m

drm.service.enabled=true

ro.build.version.ota=4.3(24.23.69.16)

ro.config.wallpaper=/system/media/wallpaper/default_wallpaper.jpg

ro.settings.sdwarning=false

ro.nvidia.collect_data_enabled=false

persist.nvidia.power_off_delay=6000

ro.sf.lcd_density=320

ro.tegra.tz3.sorting=1

ro.nvidia.no_default_homepage=1

ro.setupwizard.mode=OPTIONAL

ro.com.google.gmsversion=6.0_r6

ro.com.google.clientidbase=android-nvidia

ro.factory.wifi.lbs=true

ro.radio.noril=true

ro.hardware.sensors=default.mpl520.nvs

persist.sys.dalvik.vm.lib.2=libart

dalvik.vm.isa.arm.variant=cortex-a15

dalvik.vm.isa.arm.features=default

net.bt.name=Android

dalvik.vm.stack-trace-file=/data/anr/traces.txt

ro.expect.recovery_id=0x4fdf288575894a82abd29445a5b106da77625c61000000000000000000000000

# flag_tuner

ENFORCE_PROCESS_LIMIT=false

MAX_SERVICE_INACTIVITY=false

MIN_HIDDEN_APPS=false

MAX_HIDDEN_APPS=false

CONTENT_APP_IDLE_OFFSET=false

EMPTY_APP_IDLE_OFFSET=false

MAX_ACTIVITIES=false

ACTIVITY_INACTIVITY_RESET_TIME=false

MAX_RECENT_TASKS=false

MIN_RECENT_TASKS=false

APP_SWITCH_DELAY_TIME=false

MAX_PROCESSES=false

PROC_START_TIMEOUT=false

CPU_MIN_CHECK_DURATION=false

GC_TIMEOUT=false

SERVICE_TIMEOUT=false

MIN_CRASH_INTERVAL=false

persist.service.adb.enable=1

persist.service.debuggable=1

persist.sys.usb.config=mtp,adb

ro.zygote.disable_gl_preload=false

windowsmgr.max_events_per_sec=80

debug.sf.hw=1

debug.composition.type=gpu

persist.cust.tel.eons=1

debug.hwui.render_dirty_regions=true

persist.sys.ui.hw=1

persist.sys.composition.type=gpu

debug.performance.tuning=1

ro.hwui.texture_cache_size=54

ro.hwui.layer_cache_size=44

ro.hwui.gradient_cache_size=0.8

ro.hwui.path_cache_size=18

touch.pressure.scale=0.3

view.touch_slop=2

view.scroll_friction=1.5

ro.min_pointer_dur=8

touch.size.calibration=geometric

touch.size.scale=100

touch.size.bias=70

touch.pressure.calibration=amplitude

view.minimum_fling_velocity=25

ro.max.fling_velocity=12000

ro.min.fling_velocity=8000

ro.use_data_netmgrd=true

persist.data_netmgrd_nint=8

persist.data_netmgrd_mtu=1482

wifi.supplicant_scan_interval=180

pm.sleep_mode=1

ro.ril.disable.power.collapse=0

dalvik.vm.heaptargetutilization=0.75

persist.sys.vm.heapsize=157m
[Shield Tablet Android Development] Friedensfurz:
This is my score, totally happy with it
[Shield Tablet Android Development] supertory:
kernel auditor config and how's your battery life please?
[Shield Tablet Android Development] xanthrax:
The battery is awesome, has been 4 days since I charged it last with a moderate usage, on standby is great

Sent from my Darkside of Oneplus 3
[Shield Tablet Android Development] :
Thanks alot. Will update you guys as soon as I get around to test this... probably this weekend
[Shield Tablet Android Development] Zephyr918:
Awesome kernel. Kicking butt on my tab!
[Shield Tablet Android Development] m0nt3s:
here's a quick how to on using Bit's kernel to its full extent to raise your AnTuTu score

here are the shell commands,

to manually set your GPU rate:

cat /sys/kernel/debug/clock/gbus/possible_rates

echo 852000000 > /sys/kernel/debug/clock/override.gbus/rate

echo 1 > /sys/kernel/debug/clock/override.gbus/state

cat /sys/kernel/debug/clock/gbus/rate

To Maximize EMC (Memory Controller)

cat /sys/kernel/debug/clock/override.emc/max > /sys/kernel/debug/clock/override.emc/rate

echo 1 > /sys/kernel/debug/clock/override.emc/state

cat /sys/kernel/debug/clock/emc/rate

example of adb shell it on windows

Microsoft Windows [Version 6.1.7601]

Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\m0nt3s>cd c:\adb

c:\adb>adb shell

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

root@shieldtablet:/ # su

su

root@shieldtablet:/ # cat /sys/kernel/debug/clock/gbus/possible_rates

cat /sys/kernel/debug/clock/gbus/possible_rates

72000 108000 180000 252000 324000 396000 468000 540000 612000 648000 684000 7080

00 756000 804000 852000 900000 924000 960000 984000 1008000 (kHz)

root@shieldtablet:/ # echo 852000000 > /sys/kernel/debug/clock/override.gbus/rat

e

o 852000000 > /sys/kernel/debug/clock/override.gbus/rate <

root@shieldtablet:/ # echo 1 > /sys/kernel/debug/clock/override.gbus/state

echo 1 > /sys/kernel/debug/clock/override.gbus/state

root@shieldtablet:/ # cat /sys/kernel/debug/clock/gbus/rate

cat /sys/kernel/debug/clock/gbus/rate

852000000

root@shieldtablet:/ # cat /sys/kernel/debug/clock/override.emc/max > /sys/kernel

/debug/clock/override.emc/rate

override.emc/max > /sys/kernel/debug/clock/override.emc/rate <

root@shieldtablet:/ # echo 1 > /sys/kernel/debug/clock/override.emc/state

echo 1 > /sys/kernel/debug/clock/override.emc/state

1|root@shieldtablet:/ # cat /sys/kernel/debug/clock/emc/rate

cat /sys/kernel/debug/clock/emc/rate

924000000

root@shieldtablet:/ #
[Shield Tablet Android Development] simonsy:
Hi guys i have installed the k7 version of the kernel and everything work great. I have also tried to modify the min cpu frequency using kernel auditor app, but it seems that the nvidia power manager (I have a stock rom) interfere with it. There is a way to override the cpu frequency settings on a stock rom? Thanks in advance

Inviato dal mio SHIELD Tablet K1 utilizzando Tapatalk
[Shield Tablet Android Development] BitOBSessiOn:
Which governor do you use? Nvidia power options...?
[Shield Tablet Android Development] simonsy:
Hi, I have tried with ondemand and interactive. Also changing the setting of Nvidia power control doesn't seem to make any difference.

Inviato dal mio MI 5 utilizzando Tapatalk
[Shield Tablet Android Development] BitOBSessiOn:
Good points... [MENTION=7002998]m0nt3s[/MENTION] , thx for your contributions.

Btw... I think that maybe noatime parameter in mounting options can do more than changing FS to F2FS... Have you tested this...? What's your experience about...?
[Shield Tablet Android Development] primaleph:
F2FS question

I'm going to try formatting /data to F2FS using the new version of TWRP soon.

Am I right in assuming that I shouldn't try this with /system or my adopted "internal" microSD card?
[Shield Tablet Android Development] BitOBSessiOn:
Theorically you'd need a boot partition with F2FS fstab file compatible... Lets see why data part not recognized by TWRP after F2FS formatted and then get messed with system...
[Shield Tablet Android Development] BitOBSessiOn:
Maybe you want keep an eye here.
[Shield Tablet Android Development] tinybilbo:
*Edit* Misread the Post! Ignore what I said below.... The system partition is not working on F2FS at this time AFAIK

I have just setup a fresh install of a stock rom with data and cache on F2FS, and then adopted a 128gb card without issue... However it only migrated a small amount of data since it was a fresh install. It certainly boots without issue..

if I run into any issues I'll post back here.

On a side note... What would be optimal settings for stock rom with this kernel and data & cache partitions on F2FS? (I only ask since there are a lot of pages to read through in this thread!)

*Edit 2* I've installed the KX version since I'm using F2FS, Do I need to install the DTB zip? I don't appear to be having battery issues (I don't really know what to look for though... the tablet is new) and I don't really need OC...
[Shield Tablet Android Development] XPS3Johann:
Incredible !!:victory:

What GPU changes have you made to reach this result? i made 39060 only
[Shield Tablet Android Development] primaleph:
Is it safe to use the K7-006 kernel with an original Shield running 4.4 stock?

I'm asking mainly because I'm not sure whether there were any important kernel changes between 4.3 and 4.4 . Thanks.
[Shield Tablet Android Development] daeymon:
I'm using it with 4.4 stock without issue.
[Shield Tablet Android Development] primaleph:
I made a backup and tried it. working well for me also. my problem in the past seems to have been that I tried to reinstall supersu after installing the kernel, but I hadn't unrooted first. it would boot, optimize apps, sit at a black screen with a few notification icons, and then reboot. fixed now though.
[Shield Tablet Android Development] BitOBSessiOn:
BitO-K8-001 available for testing:

https://www.androidfilehost.com/?w=files&flid=130561

Latest Nvidia sources (OTA 4.4)

Full F2FS support

BitO-K tweak pack

KExec hardboot patch

Tested on stock 4.4

F2FS fstab injector (replaces fstab.tn8 in your boot.img):

https://www.androidfilehost.com/?fid=529152257862683316

*Needed if you want to use F2FS and it's your very first time.
[Shield Tablet Android Development] nowforever:
Can I flash this kernel over N ROM?
[Shield Tablet Android Development] BitOBSessiOn:
I think so, but not tested. Please, give feedback if you try... but remember, TWRP backup tool is your friend... ;) Thnx!
[Shield Tablet Android Development] GuyInDogSuit:
Yay, now I can flash this on my tablet again! (I'm on 4.4)
[Shield Tablet Android Development] Son-j:
So far so good.

I flashed this and initially after device would always go back to nvidia logo and reboot endlessly. I decided to turn the device off after 10 repetitive reboots and voila, the device continued the proper boot sequence and went to "optimizing app" part

Now my device doesn't lag as much as before especially after waking up from deep sleep and connecting it right away online. I wish Nvidia will discover ultimately what causes the occassional lags on the original ROM.

Thank you so much for this development!!!
[Shield Tablet Android Development] m0nt3s:
[MENTION=6411851]BitOBSessiOn[/MENTION] you're still my hero bit! I don't know if I messed up some where or if nvidia patched it but I keep getting "Segmentation fault" errors after flashing K8-001. but even when I fully go back to 4.3 stock recovery and root with SR4-SuperSU-v2.78-SR4-20161115184928. I'm okay on SR4-2016 but then superSU asks to update binaries and after I update through normal all **** hits the fan. I don't it due to the kernel or the fstab but it errors out saying that it can't find /etc/fstab which to the best of my knowledge is on the "/" which is now locked out at 0bytes free. Do you still have a successful root? Do you have mksh in your boot.img after root? Are you sytemless or system SU would be the easiest question. I appreciate everything that you've done along with way more devs that have brought us here. let me know if you have any advice or opinion on keeping a stable root. I managed to get full f2fs but from all the b*ll**** that follows, only formatting your /cache partition seems to have the best benchmark/performance.
[Shield Tablet Android Development] BitOBSessiOn:
Have you tried with SR4 supersu + fstab injector after flashing 08-001?
[Shield Tablet Android Development] tykoon:
Just got a K1 and I have installed the latest version of this kernel. I am running a rooted stock rom also the latest version 1.5 from Nvidia. I am just trying to fully understand the DTB file. Do I only need to flash it if I have problems with charging or does it have other significance? Thanks in advance and thanks for the work on the kernel!
[Shield Tablet Android Development] BitOBSessiOn:
Yes, that's right. Initially you shouldn't need it.
[Shield Tablet Android Development] tykoon:
Ok, great thanks!
[Shield Tablet Android Development] lmulli:
I've tried to install this on the latest AICP Nougat builds but although it appears to install okay in your latest version of TWRP, the AICP kernel remains in place. I've tried unticking the multirom option but same result.
[Shield Tablet Android Development] KentuckyGuy447:
Is the Dirty Cow Exploit patched in this build?
[Shield Tablet Android Development] BitOBSessiOn:
I would bet that not yet. Google's November security patch doesn't seem to properly fix it.
[Shield Tablet Android Development] coowkeee:
edit 4: After few minutes, my sdcard is not detectable again on my k1 :( did i really miss something? Thanks

flashed the stable build BitO-K7-006-shieldtablet and now my k1 can't recognize my sdcard.. did i miss anything? Thanks

edit: I can still see my sdcard on twrp

edit 2: since i downloaded the beta build as well, I flashed it and my sdcard is detectable again

weird. lol ill be testing this. thanks
[Shield Tablet Android Development] m0nt3s:
So after debugging the problem we all are facing is that after installing supersu, if you flash any other busybox than (i'm uploading it) all other busyboxes overwrite su and supolicy in xbin with incorrect permissions. flash this supersu with this busybox to fix. systemless mode seems to be the only working root.
[Shield Tablet Android Development] Chris189:
I'm installed all of them , but your script is, still not working for me , but its shows less error than previous time. ( i had to modify the script to search busybox in /su/xbin ) I'm using Shield K1, Strock 1.5 ROM with F2FS and K8-001 kernel and systemless SU. Sorry for bad english. :)
[Shield Tablet Android Development] hacktrix2006:
[MENTION=7002998]m0nt3s[/MENTION] Just flashed the files you mention and it results in my K1 not booting into android is there a set order in which i have to flash these files ?

Lucky i did a friendly TWRP backup before hand LOL.
[Shield Tablet Android Development] winesh:
I just ordered a K1, a bit late I admit :p The main reason I got this tab is because of the great work you guys are delivering. The development section is very active, for a few years old tablet.

As soon as I receive the tablet I will root it and flash this kernel. Thanks for your great work [MENTION=6411851]BitOBSessiOn[/MENTION].

Short question; if I will use this kernel as is, without adjusting settings with kernel auditor for example, is the stock use of this kernel performance oriented or batterysaving oriented?
[Shield Tablet Android Development] BitOBSessiOn:
K is aimed for stability, battery friendly, KX for performance, more experimental, OC, etc...
[Shield Tablet Android Development] coowkeee:
Why is this killing my SD card? Did i miss something? I just flashed it and it's working, but the sd card cant be detected.
[Shield Tablet Android Development] tikizondo94:
Just a note. Your work on the shield tablet is absoluetly amazing. Your work has put new life into my tablet. Latest K-008 with F2FS/data/cache running like a dream on my shield. Many thanks and your work is much appreciated!
[Shield Tablet Android Development] Son-j:
I've got once in a while permanent freezing experience with k-008 and needs reset . Other than that, the device is fluid. There might be occasional lagging, but I normally leave the tablet be until it stabilizes. This is better than the stock version. I wish the occasional lagging will be removed permanently in the next developments. I've never experienced lagging in snapdragon and mediate devices.

PS: anyone know why this lagging problem occurs with the Nvidia device?
[Shield Tablet Android Development] tikizondo94:
Any idea on why i cannot get supersu to work once im on f2fs/data/cache? It flashes but always says the boot image is already patched during the flashing process. Any then the system will never boot back up. Just hangs on the nvidia logo. Any ideas??? "Stock Rom" 4.4
[Shield Tablet Android Development] tikizondo94:
Nevermind.. Figured it out. As said before. Use SuperSU SR4, then flash f2fs inject fstab zip... AFTER you've flashed BitO kernel. Works like a charm :)
[Shield Tablet Android Development] BitOBSessiOn:
BitO-KX8-001 available

Available for testing here.

This is basically K8-001 + OC.
[Shield Tablet Android Development] f0xG3:
Adoptive Storage using this Kernel

Hi Guys,

May I know if using this Kernel will affect Marshmallow's Adoptive Storage feature? I want to make use of the F2FS of the Kernel but I also need to know if it will do the same if I "adopt" an SD card.

Thanks :D
[Shield Tablet Android Development] Sjamaan:
The moment you "adopt" SD card, it would get reformatted, so you loose F2FS on data partition as far as I know.

But you can still get F2FS on cache partition I guess.
[Shield Tablet Android Development] f0xG3:
How do I take advantage of the different I/O schedulers that are present in this Kernel? Any app that I can use to change em'?
[Shield Tablet Android Development] BitOBSessiOn:
You can use Kernel Adiutor for tweaking
[Shield Tablet Android Development] Son-j:
Just installed kx8 on my stock 4.4... Super fluid. So far no lagging experience. What sorcery! Thanks for the amazing update, definitely better than k8 :)
[Shield Tablet Android Development] f0xG3:
Is it safe to switch between the K8 and KX8 by simply flashing the Kernel over?

Also, as far as I read, the KX8 offers OC. Is this just CPU or even the GPU? Can this be changed via Kernel Adiutor or it's slightly clocked higher by default (say. 2.5 from 2.2Ghz)?
[Shield Tablet Android Development] BitOBSessiOn:
Yes, you can flash KX8 over K8, but keep in mind that if you OC, you'd need to flash also DTB because stability and proper OC tweaking for CPU and GPU (you can use Kernel Adiutor).