yashsingh1/xdaforums huggingface dataset:
[LG V20 Questions & Answers] ElBeaner:
This is my B&O headphones, did a reboot and on the second unplug/plug I got high mode
[LG V20 Questions & Answers] Oyeve:
The DAC on the v20 is a joke. The V10 worked much better. I'm glad I went back to my Note 7.
[LG V20 Questions & Answers] ben cherian:
And the note 7 just exploded!!! :laugh:
[LG V20 Questions & Answers] Oyeve:
You're so funny! not.
[LG V20 Questions & Answers] cpete2112:
You can go in the mixer path file on phone and make it recognize low ohm headphones as high. All you guys are doing is pumping more voltage and volume to a device that doesn't need it. Would you push 500 hundred watts of power to a little tiny bt speaker and put the volume on 1? You guys should do some dac research. You're missing the point. And headphones don't have to have a lot of resistance to be good, my shure se846-cl's are only 9 ohms and they do some serious work. I can't even make em clip or sound bad barely they just pump out high spl's.
[LG V20 Questions & Answers] HD2FORNICK:
LOLOL! Seriously? I am sure the V10 is a pretty good audio device but I have had the V10 before the V20 and IMHO, the V20 is a far superior DAP than the V10. I am also comparing this to my FIIO and Xduo DAPS and the V20 blows them away. This bad boy can handle anything you throw at it.
[Shield Tablet General] skooter32:
The touchscreen improvement is that adb shell or what not good with scripts sorry
[Shield Tablet General] Deleted member 2943498:
Learn to quote.
[Shield Tablet General] skooter32:
Eh? I ask a simple question and get stupidityin return cheers oh u do realise that this is xda ?
[Shield Tablet General] m0nt3s:
[MENTION=6938147]skooter32[/MENTION] For the toucscreen I use fx file explorer, it has a built in text editor and it has easy root navigation
[Shield Tablet General] m0nt3s:
I attached some files to the original post, the boot img is userdebug with true SU, although I would reflash supersu-sr-1 after installing the new boot.img
[Shield Tablet General] skooter32:
So am adding this to build.prop? Because a cant find it on build.prop

---------- Post added at 11:22 PM ---------- Previous post was at 11:20 PM ----------

Edit found it
[Shield Tablet General] m0nt3s:
Sadly editing the build prop doesn't change touchscreen sensitivity. Install the apk I've attached, grant it root permission, then from in the apk, go to system(root) system, then usr, then idc, once your in the idc folder you'll see touch.idc which you need to open with fx text editor and delete the # infront of

touch.pressure.calibration = amplitude

touch.pressure.source = default

touch.pressure.scale = 0.01

save your changes and then back out to the same idc folder and editsensor00fn11.idc the same by deleting the the #

you only have to do this once, since I've already changed it i might be mistaken but the stock sensitivty is #0.0125, change it to 0.001 and save in both
[Shield Tablet General] m0nt3s:
proof of concept

[MENTION=5227356]boswelja[/MENTION], [MENTION=6411851]BitOBSessiOn[/MENTION], [MENTION=1416222]Steel01[/MENTION],[/MENTION], [MENTION=4937137]Bogdacutu[/MENTION],

So I need some help and you guys are the best of the best. The problem I'm having is that I've gutted the OTA 4.3 rom so much that when I try to build the replicate of my rom it errors out after booting with "setup wizard has failed" and just loops after booting. If I were to give you a TWRP backup of my current rom with settings do you think you could get it to work? I'm currently full f2fs, with a probably more than i should of gutted OTA 4.3. This is my lowest benchmark that I'm confident with your help we could make it universal. any input is apprciated.
[Shield Tablet General] skooter32:
Sorted????
[Shield Tablet General] boswelja:
Err.. the best I could do is get a logcat and tell u what's causing the problem
[Shield Tablet General] BitOBSessiOn:
Although I was working at the beginning in a OC kernel, all latest OC work must be thanked to [MENTION=4716493]laufersteppenwolf[/MENTION] . Basically I've only merged his work in latest BitO-KX series.

Correct merits should be put in OP, please.

Thx!
[Shield Tablet General] Crayphish:
Touch tweaks; latency or sensitivity?

Thanks for these details. I understand the objective of these tweaks are for hardware performance, but I'd like to ask if these modifications to the touch IDC improve touch latency on the Shield? I recently purchased one when stock became available and find that it's touch response is significantly slower than my Nexus 9 (same K1, but dual core 64-bit) when not plugged into any power source (so far my power sources introduce MORE latency...). I'd like to identify any measures I can take to reduce touch latency if possible.

This is apparent in any scrolling app, using debug 'show touches', or testing apps such as Yet Another Multi Touch Tester, where any visual indication lags behind the finger significantly when dragging and swiping. It also results in diminished response in rhythm games which already have enough trouble with the state of Android audio latency.

This tweak looks like it adjusts touch sensitivity (finger distance from screen before registering a touch), which I don't have any problem with. Can anyone using these tweaks confirm or deny if they improve latency as well?
[Shield Tablet General] Crayphish:
[MENTION=7002998]m0nt3s[/MENTION]

Thanks for the help. I've just put TWRP on the device and setup [MENTION=6411851]BitOBSessiOn[/MENTION] 's experimental F2FS kernel with good success so far. I will try your sysctl and build.prop changes as well and see if I can get any improvements. :good:
[Shield Tablet General] m0nt3s:
Kernel auditor is also a very useful app that I think is a must have
[Shield Tablet General] KariArisu:
Can you or anyone else point me in a direction for everything to make the sensitivity consistent?

I literally bought the Shield K1 tablet to play a rhythm game (Love Live, specifically) and whenever I'm playing a very difficult song, I easily drop my combo due to touches not being input. I'm certain there's some way of fixing this...

What rom should I use, should I change the kernel, what else should I try? I don't have any external cooling sources and I'm pretty new/bad at this stuff overall.

Not even sure what to do with a sysctl.

I've tried a bunch of things, and so far my tablet feels worse than when I started from the stock rom with just root.
[Shield Tablet General] m0nt3s:
[MENTION=7639944]KariArisu[/MENTION]

Go to settings, about tablet, and tap on Model number six times to open the built in touch calibrator.

The biggest performance impactor would be Google. Go to settings accounts, google, and uncheck Sync and every other google feature. if you do need to use a feature you can always do it manually or turn the feature back on when you need it, googles background sync eats %23 - %29 memory when activated. if you're not using cloudprint turn that off under settings printing, you can also go to about tablet, tap on build number 7 times, enabled developer options go down to the drawing section, change Window, Transition, and Animatorr scale to .5 or .25 if you have gravity box installed. also in about tablet uncheck help nvidia improve shield, ot's another background sync app but Nvidia is sneaky in that in the build prop they still have this enabled stock

ro.nvidia.collect_data_enabled=true, use FX editor, navigate to system(root) system, click the little lock to unlock or remount as r/w and then edit your build prop lines

ro.nvidia.collect_data_enabled=false

ro.input.noresample=0

you can also go back to settings, developer options, hardware accelerated rendering, check force use of GPU for 2d drawing, disable HW overlays, and then go maximize system memory scroll down to the bottom of developer options, apps, background process limit and change it to either 1 or none.
[Shield Tablet General] KariArisu:
Did all of this now, and it's better but still not great. Whenever I have to rapidly tap for long periods of time, it will eventually cause taps to lag behind or just not happen at all. It's really weird.
[Shield Tablet General] m0nt3s:
Sounds like it's time to flash Bit's OC kernel, after you flash go on the playstore and get Kernel Adiutor (ROOT)

https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor&hl=en

once you do, let me know and we can start tweaking some things
[Shield Tablet General] KariArisu:
KX7-006 right? I'll have it flashed shortly if you wanna get started
[Shield Tablet General] m0nt3s:
[MENTION=7639944]KariArisu[/MENTION]

So there's a couple of things we can tweak, kernel auditor is good a good start for figuring out which settings work best for your device. I'll go over the which settings have the most impact but before that, To make all shield users lives a little easier I wrote an init.d script that works. init.d allows you to run scripts on boot of your choosing. It can also execute your scripts at the true root level so when we change the touchscreen sensitivity, the system won't change it back after boot.

This is probably the best free user friendly script manager app

https://play.google.com/store/apps/details?id=os.tools.scriptmanager&hl=en

after thats installed I've attached my init.d.enable script, unzip it and put the init.d.enable script either on your internal sd card or external. you will only need to run it once and smanager will do it. open smanger and navigate to where you placed the script select it, and check the box run as SU and you've taken the first step in having full control of changing your system performance.

Now, if you open kernel auditor, you can view various statistics about your device but the best way to start optimizing performance is by going to the CPU tab. After flashing bit's kx-006 your new CPU maximum frequency will be 2499MHz but the shield will still set the stock 2218MHz, try setting it to 2499. Now CPUQuiet will downclock your device when it thinks its idle, turn off CPUQuiet. turn on all 4 cores but leave the governor on interactive first, you can always change it to performance top have your max and min clocks both at 2499mhz.

Next go to I/O Scheduler and the default should be CFQ with bits, click on schedule Tunable and change target_latency from 300 to 200 for now. you can also disable i/o stats to free up some more memory and if your running with all four cores on which we changed in CPU, change RQ Affinity to 2.

Try those kernel auditor settings and see if you notice a difference, let me know either way. I'll start scripting sysctl settings into an sh file init.d compatible script just incase any one wants to try personal settings.
[Shield Tablet General] tinybilbo:
Thanks for the walkthru... exactly what I needed!

I'm setting up a pad for my daughter, So I want to maximize performance without too much of a hit on stability and battery.

I've already formatted data & cache to F2FS, and set up recovery, root, and finally changed the kernel to KX-006. I already have kernel adiutor. I'm going to do the touch lag mod you mentioned earlier.

I read in the OP that with some of these tweaks the pad heats up, what settings would you recommend that doesn't kill battery and heat the pad too much...

Thanks again for a great tweaking thread!!
[Shield Tablet General] KariArisu:
[MENTION=7002998]m0nt3s[/MENTION]

I did everything, but CPU frequencies aren't really working. My Min/Max keeps changing, so whenever I try to set it to something it just changes to other values randomly. What would be causing that? CPUQuiet is off.
[Shield Tablet General] m0nt3s:
[MENTION=4232554]tinybilbo[/MENTION] you should be fine, it heats up when you start overclocking the GPU and EMC memory via

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

Here's some custom CPU governor Tunables you can change in kernel auditor, CPU governor interactive

I attached a picture, this text box and the preview box are not the same spacing

the attached picture shows the optimal setting for performance while not killing the battery in half an hour like setting the min/max performance to 24900000.

powersave works the best stock for saving the battery.

I'll working on turning it into a script right now, i'll post it soon
[Shield Tablet General] m0nt3s:
[MENTION=7639944]KariArisu[/MENTION]

It's the governor interactive scaling the frequencies. once you set the max freq to 24900000 and the min to 51, the governor will scale to the frequencies it believes it needs to be at to adapt performance as its needed while still trying to save some battery. once you set the min/max you're good to go.

You can try the ondemand governor which polls faster than interactive or if you're plugged in you can set it to performance, the go to settings, performance/power, max performance. and then turn off App Optimization.

I'm attaching a digitizer booster which I think will help you, I use it when playing vainglory and it helped me become a stutter step master.
[Shield Tablet General] tinybilbo:
Thank you for the digitizer apk and the tweaks... much appreciated

*Edit*

I flashed your modded boot.img and I lost adb whilst running the tab (USB Debug on)...

The pad is not even seen in device manager!

I reflashed Bit's OC kernel and got adb back. Tried 3 times...

Adb worked from TWRP with your boot.img but not from the Rom itself.

I'm using a K1 with stock Rom with 1.5 update, data & cache on F2FS and Bit's OC kernel...

It's not a major issue, just thought you might want to know.
[Shield Tablet General] m0nt3s:
[MENTION=4232554]tinybilbo[/MENTION]

looking into it right now, here's a one time fix for it.

So after installing adb on windows it creates a hidden folder. open start type hidden in the search and inder control panel "show hidden files and folders" should pop up, click it.

in advanced settings check show hidden files, folders, and drives.

now go to your user folder and you should now be able to see a folder named .android, inside of it should be two files, adbkey and adbkey.pub

reboot your tablet into TWRP recovery andd mount the system folder with twrp mount.

on your pc hold shift and right click in the .android folder to open command menu here.

you should have the android booted into twrp with system mounted and a command prompt window opened inside of the .android folder, type this into the command prompt.

adb push adbkey.pub /data/misc/adb/adb_keys

this will manaually push your computers RSA fingerprint to adb and you'll have SU adb access from now on.
[Shield Tablet General] m0nt3s:
[MENTION=4232554]tinybilbo[/MENTION]

Thank you for bringing that to my attention, So it turns out that nvidias newest OTA patched userdebug. If you'd be so kind, would you use fx explorer, navigate to root, and then view the defualt prop and let me know if security.harden is 1 or 0. Took some time but here's the patched OTA with debug SU. The reason you want userdebug is that you can overclock and the settings will stick and not reset. I understand why nvidia would patch it but then again **** you nvidia. unzip the boot.img and flash through fastboot, then flash SuperSu again for true root.
[Shield Tablet General] tinybilbo:
Sorry been a little busy :(

I'm not at home now, but I will do as you ask when I get home later tonight and get back to with an update to this post....

BTW thanks for all the hard work in making these tweaks....

In default.prop.... (no actual "security.harden" flag) however these might mean something :)

ro.secure=1

security.perf_harden=1

debug.atrace.tags.enableflags=0

ro.adb.secure=1
[Shield Tablet General] m0nt3s:
[MENTION=4232554]tinybilbo[/MENTION]

It's all good, no rush. It's more to see if I screwed up or if they patched it. I reflashed the old boot and got overwritten and made a new 4.4 boot and got overwritten. It wouldn't so bad but on every boot they use their fstab.tn8 which doesn't have f2fs. So worst case scenario is bootlooping after changing /cache or /data. any ways thank you for your help!
[Shield Tablet General] tinybilbo:
In default.prop.... (no actual "security.harden" flag) however these might mean something

ro.secure=1

security.perf_harden=1

debug.atrace.tags.enableflags=0

ro.adb.secure=1

Hope this helps!
[Shield Tablet General] m0nt3s:
blank
[Shield Tablet General] m0nt3s:
So I finally got around to scripting my sysctl setting and other misc performance settings into a script that every one can use. You can either throw it in your init.d folder or run it from script manager. I've attched a init.d enabler for our device as well as the performance script. Let me know if you have any problems but I've tested and it works. feedback welcomed. the zip is not flashable, extract to your sd card and run with script manager.
[Shield Tablet General] Chris189:
Thank you for you hard work , i will try, and report back.

Shield K1 1.5 firmware , data, cache F2FS, and you modified KX7-006 kernel. :)
[Shield Tablet General] XPS3Johann:
I'm getting some errors in execute your "69shield" script.. here's a log on FX
[Shield Tablet General] hulkamaphone:
anyone find a stable setting?
[Shield Tablet General] m0nt3s:
It's the way SuperSU is installed. The easiest fix without changing everything is, I've attached the busy box binaries, unzip busybox, and move the busybox binary so /system/xbin , chmod it 0755 permissions, and then rerun script
[Shield Tablet General] Chris189:
Same errors :( Maybe the problem is the systemless super su sr3?
[Shield Tablet General] XPS3Johann:
Thanks ? i'm getting 104.5k on Antutu with GPU clock at 1GHz (1032MHz), but working to increase points. (^^)

PS. Sorry for the bad inglish
[Shield Tablet General] dzidexx:
"edit touch.idc by deleting the # from infront of

touch.pressure.calibration = amplitude

touch.pressure.source = default

touch.pressure.scale = 0.01"

Do you think - can this help with problem:

When I use screen protect(glass, shield) I have no touch in right up&down corners. [MENTION=7002998]m0nt3s[/MENTION]

https://drive.google.com/file/d/0B9k8W8e2YrFfSVdFLWhSNlZXVjg/view?usp=drivesdk
[Shield Tablet General] m0nt3s:
[MENTION=7065205]dzidexx[/MENTION]

The is a built in touch calibrator you can try, if you go to settings, about tablet and tap model number 4 -7 times it will bring up sensor calibration utility.

# Basic Parameters

touch.deviceType = touchScreen

touch.orientationAware = 1

# Touch Size

touch.touchSize.calibration = pressure

# Tool Size

# Driver reports tool size as an area measurement.

#

# Based on empirical measurements, we estimate the size of the tool

# using size = sqrt(22 * rawToolArea + 0) * 6 + 0.

touch.toolSize.calibration = area

touch.toolSize.areaScale = 22

touch.toolSize.areaBias = 0

touch.toolSize.linearScale = 6

touch.toolSize.linearBias = 0

touch.toolSize.isSummed = 0

# Pressure

# Driver reports signal strength as pressure.

touch.pressure.scale = 0.3

# A normal index finger touch typically registers about 80 signal strength

# units although we don't expect these values to be accurate.

touch.pressure.calibration = amplitude

touch.size.scale=100

touch.pressure.scale = 0.0001

# Size

touch.size.calibration = geometric

# Orientation

touch.orientation.calibration = none

you can try editing /system/usr/icd/touch.idc if the screen calibrator doesn't work.

try adding this to your build prop

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

Does the center of your screen work? if you go to system/vendor/app is there an apk named OverscanComp ? This link can give you some insight on different touch settings,

http://xdaforums.com/g4/general/fix-screen-issues-t3172100
[Shield Tablet General] dzidexx:
Two corners don't work only when I use any screen protector. Now I'm waiting for another(next few days). I will check yours sugestions.

Sensor calibration utility - only touch. After calibration restart, it's all?

OverscanComp is present - should I do something with it?

Touch.idc, differences:

# Size

touch.size.calibration = normalized

# Orientation

touch.orientation.calibration = vector

I have shield k1.
[Shield Tablet General] m0nt3s:
There's a trick for lessening screen sensitivity that could have an effect, go to the built in touch screen calibration, and when you run it touch your fingers on the parts of the screen that aren't reading, let it calibrate as your touching the parts of the screen and reboot. Did you have to apply liquid to attach the current screen protector or is it a reusable one?
[Shield Tablet General] dzidexx:
Today I did get new one, tomorrow I will try. Thanks.

I had problems with:

http://3mkprotection.com/fg

and matte:

http://3mkprotection.com/protectivefoils

Now I will try shield.

All by warranty exchange.
[Shield Tablet General] m0nt3s:
[MENTION=7065205]dzidexx[/MENTION]

I feel your pain,I got burned by using

https://www.amazon.com/Protector-Nearpow®-Tempered-Bubble-Free-Installation/dp/B01B2II406

what worked for me is intelliglass skin.

http://www.iqshield.com/iq22846-nvidia-shield-tablet-k1-screen-protector.html

With my first screen protector I misaligned it and when forcing it into alignment i caused micro bubbles that would register 1/2 a second later than all my other touches. The setting liquid helped me fix it so my advice would be to get a kit with at least a cleaning lubricant included. I'm sorry about my other post, I was angry and I took it out on you more than I should have, if you want any help with any thing I'll try my best to help you.
[Shield Tablet General] m0nt3s:
[MENTION=7065205]dzidexx[/MENTION]

I see we both like to try to make roms better, you every play with

http://xdaforums.com/chef-central/android/best-android-roms-editor-assayyedkitchen-t3410545

?

I have SuperR's kitchen for making the rom actually install but ASSAYYED makes tinkering on windows a little too easy. check it out, i think you'll have some fun editing your [SURNIA] rom with it.
[Shield Tablet General] dzidexx:
[MENTION=7002998]m0nt3s[/MENTION]

Hi, thank you for all help.

The last one(3mk, green) works quite good. Right now I use it and am looking for something better. In Poland I can also buy from amazon.de - nothing special with delivery costs.

Surnia - I am not creating roms - just looking and helping for the best.

F.e. surnia - three devs created ResurrectionR, now I'm testing the 2nd.
[Shield Tablet General] Sub-Negro:
Would this be able to help out with Resident Evil and Metal Gear?
[Shield Tablet General] Vipxpert:
Wow wow wow wow wow wow wow wow wow wow !! :eek:eek:O
[Shield Tablet General] MaxPowerOne:
Are the overclocking tweaks working with shield tab lte 7.0 nougat? I can't find a way to overclock my rooted device. I play games with it an I would like a bit better performance
[Shield Tablet General] MaxPowerOne:
Thank you, your setting were good. What do I have to do to overclock? Is stock nougat rom ok? Is gpu overclocking possible?
[Shield Tablet General] MaxPowerOne:
I'm now running lineageos 14 and is pretty fast with pico opengapps. Can I find a working kernel for overclocking?