[KERNEL] BitO-K12 / KU: Kernel for Nvidia Shield Tablet [Stock / Custom / N]

[Jz5678910]

Anyone know how to undervolt this thing? Worked wonders on my Nexus 9, figured I'd try it on this too.

 

[dizgustipated]

Dear OP
Congratulations on the new device! Appreciate your work.
Now that it's here, any chance of convincing you to implement a double tap to wake feature?

 

[Afanasii]

Tablet Shield ext usb wifi dongle Intel 3160 (iwlwifi)

Hi,
I've been trying to get Intel 3160 to work for several weeks as an external wifi dongle. I already reassembled 100 cores, But I just can’t force iwlwifi to determine my device and create an interface in "ifconfig" like wlan1 or some.
Please help me to get my target.

P.S. Intel Dual Bend Wireless-AC 3160
Model:3160HMW
Attached by OTG cable trough USB->miniPCI
Kernel 3.10.40
Target: have wifi interface with Monitor mode

image https://ibb.co/Chy0K5x"]https://ibb.co/Chy0K5x
image https://ibb.co/PhWxvhr"]https://ibb.co/PhWxvhr

------------ dmesg | grep Intel ----------------
[ 12.678207] Intel(R) Wireless WiFi driver for Linux, in-tree:d
[ 12.678210] Copyright(c) 2003-2013 Intel Corporation
------------- lsusb ------------------------------
Bus 001 Device 002: ID 8087:07dc Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
------------- lsmod -----------------------------
Module Size Used by
iwlmvm 106254 0
iwlwifi 132865 1 iwlmvm
mac80211 349920 1 iwlmvm
bcmdhd 523896 0
cfg80211 319095 4 iwlwifi,mac80211,bcmdhd,iwlmvm

 

[fukowski]

Lineage OS 15.1

Hi there, anyone using lineageOS 15.1 and any of these kernels?
If so, which one and what is needed (dtb, blobs)
Thanks

 

[BitOBSessiOn]

Dear OP
Congratulations on the new device! Appreciate your work.
Now that it's here, any chance of convincing you to implement a double tap to wake feature?

No more support to this device, sorry. Long ago not used by me.

Enviado desde mi ONEPLUS A5010 mediante Tapatalk

 

[dizgustipated]

Dear OP
Congratulations on the new device! Appreciate your work.
Now that it's here, any chance of convincing you to implement a double tap to wake feature?

No more support to this device, sorry. Long ago not used by me.

I know the troubles supporting a device you don't have any more. I appreciate your efforts, as I love this device more than my others.

If you could kindly tell me which branch on your github is the most current K1 with cpu/gpu oc AND which defconfig file to use to build with, I'd like to try and add it.
Is it branch "BitO-kx10" and the defconfig "lineageos_shieldtablet_defconfig"?
apparently it's not possible to add this feature without major rewrite according to twistedumbrella and SuperPichu. Too bad, it's a feature sorely needed.
Guess I'll just be adding some stuff for personal use/play.
Thanks again for your kernel.
& your proper git repo. It was a pleasure to not have to fix a bunch of stuff to get it to build and boot properly.

EDIT: Curious about the other branches and which defconfig to use. Guessing its omni tab one.
Much thanks again!

 

[Stickman89]

Why is it that 'BitO-KU-002-shieldtablet.zip' doesn't follow the normal naming convention? Is it the latest Nvidia source code with Linux upstream changes? Or is 'BitO-KU-uda-r1.4-v3.10.108-shieldtablet.zip' the latest?

Sorry to ask, they've all got the same date stamp at androidfilehost.

If 'BitO-KU-002-shieldtablet.zip' and 'BitO-KU-uda-r1.4-v3.10.108-shieldtablet.zip' are somehow different, and it isn't that one is built from newer sources, what is the difference?

Edit: I've just applied 'BitO-KU-uda-r1.4-v3.10.108-shieldtablet.zip' (until someone can get back to me regarding the above) against Nvidia's stock 5.4 firmware and the kernel apparently altered my 360 controller mapping.
The 360 controller 'Guide' (Central ORB) button used to act as the home button prior to the kernel update. I was using Nvidia's 5.4 stock kernel. Now it does nothing, and I can't go home. Is there a solution for this issue before I revert back to stock kernel?

Edit edit: I've solved the controller issue myself. This kernel detected my wireless 360 controller as a different product id. Which is quite perculiar, but wasn't to problematic to fix. If there is anyone else with a similar issue with their 360 controller then just say so here... I'll provide a short write up on how to solve the problem.