yashsingh1/xdaforums huggingface dataset:
[Shield Tablet Android Development] skooter32:
Done everything u said and i go to run the script and it comes back as /data#
[Shield Tablet Android Development] m0nt3s:
Once it runs and you get back to data, just reboot the system

---------- Post added at 03:38 PM ---------- Previous post was at 03:37 PM ----------

Once you see that it ran in terminal, and you know that its done, just reboot the system and you should be able to feel the difference right away
[Shield Tablet Android Development] skooter32:
Cheers

---------- Post added at 03:53 PM ---------- Previous post was at 03:43 PM ----------

Definitely feels quicker opening apps etc smoother as well
[Shield Tablet Android Development] minhgi:
Was there a new update for 9/23.? Download said 404 file not found.
[Shield Tablet Android Development] boswelja:
Should be fixed now, try the download button again
[Shield Tablet Android Development] Nachitoo:
For me it still doesn't work, and i followed your second method exactly the way you wrote it, and it told me that there was "no such file or directory".
[Shield Tablet Android Development] m0nt3s:
sorry, I misread the post. So the problem is that the sh command isn't finding the script to execute. I moved the script to the /data partition after i unmounted it becuase it was easy to type cd /data for me. since it's not finding it for you, you can leave it on your external sd card and just change directories to your sd card by typing cd /external_sd i believe. try that, if it goes to /external_sd# then type sh godlike and you should see it exectue. if not then from your computer you can always run cmd and then adb shell and do it from the shell. let me know

---------- Post added at 01:52 AM ---------- Previous post was at 01:49 AM ----------

you should have %5 more space too, the /sbin/tune2fs -m 0 /dev/block/mmcblk0p13 command deletes the reserve inodes which I have never once seem to hit so instead of having 1.89gigs of memory it should boost that and a little more internal hardrive space aswell.
[Shield Tablet Android Development] Nachitoo:
Alright so it didn't work so how do you do it from the adb shell?
[Shield Tablet Android Development] m0nt3s:
A new begining?

[MENTION=5227356]boswelja[/MENTION] [MENTION=1416222]Steel01[/MENTION] , [MENTION=6411851]BitOBSessiOn[/MENTION] , Between the three of you awesome devs I believe that you could create a new os and kernel that can rival an IPAD Pro. I was able to use bit's newest kernel to get the data and cache partitions of the 4.3 OTA formatted and successfully changed over to f2fs. To be able to have the system partition you would have to edit the fstab before you compile a new one which you guys seem to have down like the back of your hands. If you could make me a test kernel I would test it for sure. this is the mount pount

-/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/APP

and if you'd be so kind, could you change it to

+/dev/block/platform/sdhci-tegra.3/by-name/APP /system f2fs noatime,nosuid,nodev,discard,nodiratime,inline_xattr,errors=recover wait,nonremovable,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/APP

in the FSTAB for me?

I've tested it on sdk23 but what I think would blow everything away is if you guys could compile it for the nougat preview that boswelja create. It already benchmarks off the charts in ext4 format, I can't image what f2fs can do. And yes, I tried using bits newest kernel for the preview, sdk23 and sdk24 won't play nice together, i had to find that out the hard way while i'm sure you guys are laughing lol. I attached the stock f2fs benchmark pics, stock interactive settings 2 cores.
[Shield Tablet Android Development] drewski_1:
Sounds like you should join the team? :D
[Shield Tablet Android Development] skooter32:
Would this script work on any phone?
[Shield Tablet Android Development] m0nt3s:
So yeah, the adb shell way is going to be easy if you have adb setup. Do you have a windows computer? if so check this link out for automatic adb setup,

http://xdaforums.com/showthread.php?p=48915118#post48915118

if you don't have a windows computer then thats where my knowledge of adb ends
[Shield Tablet Android Development] Nachitoo:
Well i do have one, and do have adb as well.
[Shield Tablet Android Development] m0nt3s:
It would work on any phone if you changed the /dev/block/mmcblk0p13 to what your phones system folder is, once you adb setup and you type adb shell, type "cat /proc/mounts" and it will give you a list of showing you all the mounts like this, mmcblk0p13 /system

mmcblk0p14 /cache

its different on every phone but you can easily edit it to work

---------- Post added at 03:39 AM ---------- Previous post was at 03:27 AM ----------

alright, so this should work like this.

Boot your shield into twrp recovery mode and unmount all the partitions with twrp, then connect it to your computer through usb then

click on the windows start orb, then type cmd into search, open up a cmd window or if adb is installed, i installed mine to c:\adb you can hold down shift and right click in the adb home folder and it should have an option open command menu here.

once you have the command window open type adb devices, which should bring up a menu like this

Microsoft Windows [Version 6.1.7601]

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

C:\adb

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

* daemon started successfully *

List of devices attached

HT0APRM01399 recovery

once you see that type in adb shell

if it works which it should your command window is going to change to maybe some random characters and then # where you can enter in commands

just copy the first line and paste it into the command window, hit enter, copy the second line, enter, and so on untill your finshed, then type exit, exit again and reboot your tab

/sbin/busybox umount -l /dev/block/mmcblk0p13

/sbin/busybox umount -l /dev/block/mmcblk0p14

/sbin/busybox umount -l /dev/block/mmcblk0p23

/sbin/tune2fs -m 0 /dev/block/mmcblk0p13

/sbin/tune2fs -m 0 /dev/block/mmcblk0p14

/sbin/tune2fs -m 0 /dev/block/mmcblk0p23

/sbin/e2fsck -yf /dev/block/mmcblk0p13

/sbin/e2fsck -yf /dev/block/mmcblk0p14

/sbin/e2fsck -yf /dev/block/mmcblk0p23

/sbin/tune2fs -o journal_data_writeback -c 1 -i 1d -m 0 /dev/block/mmcblk0p13

/sbin/tune2fs -o journal_data_writeback -c 1 -i 1d -m 0 /dev/block/mmcblk0p14

/sbin/tune2fs -o journal_data_writeback -c 1 -i 1d -m 0 /dev/block/mmcblk0p23

/sbin/tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk0p13

/sbin/tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk0p14

/sbin/tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk0p23

/sbin/e2fsck -Dfy /dev/block/mmcblk0p13

/sbin/e2fsck -Dfy /dev/block/mmcblk0p14

/sbin/e2fsck -Dfy /dev/block/mmcblk0p23
[Shield Tablet Android Development] Nachitoo:
Thanks Man, it finally worked.. :)
[Shield Tablet Android Development] boswelja:
But I thought our shield tab already had the iPad pro beat XD. As for the kernel tweak, have you tested for errors?
[Shield Tablet Android Development] skooter32:
See am not much of a code writer or anything am good with instructions etc but what u just said blew me mind lol a hav new g4 athene xt1622 and it could use a boost on stock rom but as a said rooting etc following instructions etc all good
[Shield Tablet Android Development] yohanevindra:
Thanks boswelja! Installed the ROM onto my Shield K1 and after a few tries it works! Looks good!

However, on the download site there was version 20160918, is there a newer one up?
[Shield Tablet Android Development] boswelja:
None yet, but when there is, substratum will be fixed and well have a decent browser
[Shield Tablet Android Development] m0nt3s:
It does in theory beat it but if we create a flashable rom that will make every single shield stomp on the ipad with a single flash, thats the dream lol
[Shield Tablet Android Development] boswelja:
That would be hilarious, until apple found some way to sue us for all our worth
[Shield Tablet Android Development] m0nt3s:
I found fstab for android_device_motorola_athene here

https://github.com/ashwinr64/android_device_motorola_athene/blob/cm-13.0/ramdisk/fstab.qcom

I rewrote the script to where it should work for you

/sbin/busybox umount -l /dev/block/bootdevice/by-name/system

/sbin/busybox umount -l /dev/block/bootdevice/by-name/userdata

/sbin/busybox umount -l /dev/block/bootdevice/by-name/cache

/sbin/tune2fs -m 0 /dev/block/bootdevice/by-name/system

/sbin/tune2fs -m 0 /dev/block/bootdevice/by-name/userdata

/sbin/tune2fs -m 0 /dev/block/bootdevice/by-name/cache

/sbin/e2fsck -yf /dev/block/bootdevice/by-name/system

/sbin/e2fsck -yf /dev/block/bootdevice/by-name/userdata

/sbin/e2fsck -yf /dev/block/bootdevice/by-name/cache

/sbin/tune2fs -o journal_data_writeback -c 1 -i 1d -m 0 /dev/block/bootdevice/by-name/system

/sbin/tune2fs -o journal_data_writeback -c 1 -i 1d -m 0 /dev/block/bootdevice/by-name/userdata

/sbin/tune2fs -o journal_data_writeback -c 1 -i 1d -m 0 /dev/block/bootdevice/by-name/cache

/sbin/tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/bootdevice/by-name/system

/sbin/tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/bootdevice/by-name/userdata

/sbin/tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/bootdevice/by-name/cache

/sbin/e2fsck -Dfy /dev/block/bootdevice/by-name/system

/sbin/e2fsck -Dfy /dev/block/bootdevice/by-name/userdata

/sbin/e2fsck -Dfy /dev/block/bootdevice/by-name/cache

---------- Post added at 06:48 AM ---------- Previous post was at 06:44 AM ----------

Do you compile everything your self? and and set your own toolchains? my current computer blows and takes a day or two to compile anything. As for the kernel tweak, I have the logcats for /data and /cache with no errors, but init.rc will always override me settings for /system :( I would need to recompile the kernel with the fstab changes and like line 343 in init.rc to reflect f2fs instead of ext4. If you'd be so kind or have any extra time, If you could compile an f2fs test kernel I will fully test it and debug it if it needs it.
[Shield Tablet Android Development] skooter32:
Awesome just ran it but getting no such directory again any ideas
[Shield Tablet Android Development] boswelja:
You're trying to run a script for another device
[Shield Tablet Android Development] skooter32:
Yes same method would it not which I have done
[Shield Tablet Android Development] boswelja:
New build coming soon that fixes all substratum bugs (but it may also introduce some app theming bugs) and has a decent browser
[Shield Tablet Android Development] skooter32:
An f2fs kernel would be class on the k1
[Shield Tablet Android Development] boswelja:
That's [MENTION=6411851]BitOBSessiOn[/MENTION]s area :P
[Shield Tablet Android Development] BitOBSessiOn:
Hi, [MENTION=7002998]m0nt3s[/MENTION] , could you test this, and see what about performance or any other difference...?

This version implements security in F2FS, and any other code update.
[Shield Tablet Android Development] m0nt3s:
Will do, silly question and I'll test both but Kx7-002 kernel is for the nougat preview or OTA 4.3?

---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------

this will work on any device for another little quick boost and should be run from terminal while rom is booted.

busybox mount -o remount,noatime,nodiratime,remount,rw,barrier=0,data=writeback /data;

busybox mount -o remount,noatime,nodiratime,remount,rw,barrier=0,data=writeback /cache;

busybox mount -o remount,noatime,nodiratime /dev;

busybox mount -o remount,noatime,nodiratime /proc;

busybox mount -o remount,noatime,nodiratime /sys;

busybox mount -o remount,noatime,nodiratime /system;

busybox mount -o remount,rw,noatime,noauto_da_alloc,nodiratime,barrier=0,nobh /system

busybox mount -o remount,noatime,noauto_da_alloc,nodiratime,nodev,barrier=0,nobh /data

busybox mount -o remount,noatime,noauto_da_alloc,nodiratime,nodev,barrier=0,nobh /cache

---------- Post added at 11:13 PM ---------- Previous post was at 10:55 PM ----------

This script is edited for the Athene, is that the device you're trying to use it on? the shield script is a couple back, the difference is the shield has tegra in it. The easiest way or which way has worked for others would be to run it from adb shell, check a couple posts back and you'll find out how to do it step by step
[Shield Tablet Android Development] m0nt3s:
Good news and bad news, Bits test kernel does support f2fs, bad news is that we need it to support f2fs-all. I can reformat to f2fs but then the partition isn't able to mount. Bit if you could compile this f2fs binary or take a look at it for me I think this might solve some of our problems.

https://github.com/CyanogenMod/android_external_f2fs-tools
[Shield Tablet Android Development] boswelja:
I'll pull it in and build it as soon as I've got working builds again :)
[Shield Tablet Android Development] m0nt3s:
You're awesome Bos, I've been able to get it to mount by pushing an edited fstab but our problem is that twrp also needs to be compiled with the new fsck.f2fs. I've found an experimental multirom that has f2fs but the binaries are old and it don't work. when manually formating to f2fs through abd shell it formats and with the switched kernel fstab the kernel see it but twrp doesn't. I think if we're going to have to recompile both the kernel and twrp with the new f2fs binaries and edited fstab and recovery fstab. I'll attach the recovery.fstab that can also be renamed to fstab.tn8 which supports f2fs for the data and cache partitions. If it stays past reboot then it can easily be edited to support /system and we should be good. Thank you guys for all your hard work and effort, we'll figure this out.
[Shield Tablet Android Development] boswelja:
[MENTION=7002998]m0nt3s[/MENTION]

We'd better find someone that knows what they're doing with building recoveries then, and I might be a while trying to get the builds working again
[Shield Tablet Android Development] drewski_1:
[MENTION=1416222]Steel01[/MENTION] ¿
[Shield Tablet Android Development] BitOBSessiOn:
BitO-K7/KX7 should work with both MM and N ROMs.

I have a CM-13 device tree in my github for TWRP MultiROM... If I have time, I will try to update, but don't know if it will be enough for N... (Because any change in bootloader, etc...) Maybe [MENTION=1416222]Steel01[/MENTION] can commemt about.

My main prob is my Shield Tablet is dead and I can't test anything ATM...
[Shield Tablet Android Development] Steel01:
Current twrp releases are enough to flash N no problem.

Like I've stated in the official twrp thread, I'm not interested in supporting f2fs in official twrp due to extensive kernel changes that are needed. However, anyone can easily build twrp. The device and kernel trees are in the TeamWin repo. Also, I have scripts here that will build multirom twrp with just a couple commands. If someone wants to spin their own build with f2fs support, go right ahead.
[Shield Tablet Android Development] m0nt3s:
damn, compiled just to boot loop
[Shield Tablet Android Development] canelia:
09-29 17:18:47.075 13251 13251 F libc : CANNOT LINK EXECUTABLE "/system/bin/glgps_nvidiaTegra2android": cannot locate symbol "_ZNK7android13SensorManager13getSensorListEPPKPKNS_6SensorE" referenced by "/system/bin/glgps_nvidiaTegra2android"...
[Shield Tablet Android Development] Steel01:
I haven't had time to write the shim for that. Will take patches if someone else can do it.
[Shield Tablet Android Development] sonofevil77:
Oh nice! I can't wait to try this!
[Shield Tablet Android Development] :
What happenend to this? Busy?
[Shield Tablet Android Development] boswelja:
Yeah, I accidentally deleted that build, now I'm working past more build errors :(
[Shield Tablet Android Development] boswelja:
I accidentally deleted that build, now I'm working past more build errors :(
[Shield Tablet Android Development] cocoapapi:
I love the ROM. Smooth and responsive. I hope for new fixes since I'm a Facebook head (videos, etc.) Great job!! Also the battery life seems amazing!!
[Shield Tablet Android Development] KentuckyGuy447:
Knowing that all devices aren't created equally... That benchmark score has me sold on flashing this room once video playback in browsers is fixed but I have a question first. How has any gamer found the battery life to be while heavy gaming? I 85% use my shield tablet for gaming usually pulling in 2-3 hours of heavy gaming. I also know while idlly browsing the web and things of that nature tends to suck battery out of the tablet on marshmallow. Any improvements to that also?!
[Shield Tablet Android Development] canelia:
invalid time, battery and wifi info in status bar

canelia.net/image/screenshots/ShieldTablet_DominionOS.png

invalid time, battery and wifi info in status bar
[Shield Tablet Android Development] abdulhamid1978:
I have ordered the Shield Tablet K1, is this ROM compatible? Also has anyone tested HDMI audio on this ROM at all?
[Shield Tablet Android Development] boswelja:
Yes its compatible, and no, HDMI audio doesn't work
[Shield Tablet Android Development] boswelja:
That is really strange.. Are you using anything that alters the system partition?
[Shield Tablet Android Development] feelpt:
hi there

first of all, thanks for your work. I flashed the rom according to instructions and everything went smooth. Rom seems stable and no major bugs for my daily usage.

one question though... it's mentioned that no specific firmware is required. only unlocked bootloader and custom rec. After flashing your rom, can i easily go back to a MM based rom? or do i need to pay attention to firmware changes that came with flashing your rom?

thanks in advance
[Shield Tablet Android Development] boswelja:
I don't see any reason why clean flashing a mm ROM would cause any problems, it should work fine :)
[Shield Tablet Android Development] DR_HAX34:
Do you have Demo mode activated?
[Shield Tablet Android Development] damian1209:
add sustem ui tuner

---------- Post added at 11:56 AM ---------- Previous post was at 11:45 AM ----------

Ok i find it
[Shield Tablet Android Development] sirhugh15:
This was unexpected and great progress! Can't wait for the next release!
[Shield Tablet Android Development] boswelja:
I'm just testing the next release now, it should have the majority of our current bugs fixed :D
[Shield Tablet Android Development] boswelja:
It doesn't boot :(
[Shield Tablet Android Development] FoxyDrew:
Did you try shutting it off and booting it up again?
[Shield Tablet Android Development] boswelja:
I'm already working on a fix
[Shield Tablet Android Development] unadventurer:
Anyone else having issues playing embedded video in browsers? This is happening in the default browser, chrome, and Firefox.

---------- Post added at 05:34 PM ---------- Previous post was at 05:31 PM ----------

Nevermind. I should learn to read.
[Shield Tablet Android Development] boswelja:
Hey [MENTION=1416222]Steel01[/MENTION] I switched ROM bases, and now the latest builds (only for shieldtablet) arent booting.. Is there any way I can get the boot logs?
[Shield Tablet Android Development] Steel01:
Doesn't boot at all? Huh. CM14 is still booting, just has camera and widevine issues. The former needs more framework patches that are beyond my league, so I'm just watching. The former needs a shim that I haven't figured out yet and I'm being lazy since I'm not shipping a build with the first broke anyways. :P

If the device is booting enough to get adb working, here's what I do. Push adb_keys through twrp per the reference below. Then adb shell into twrp. Create the directory /data/property if it doesn't exist. Then echo (with the -n flag for no newline) mtp,adb into /data/property/persist.sys.usb.config and chmod the file to 600. The last part caught me several times, apparently android doesn't like persistent properties that aren't 600. Alternatively build eng and adb will run in insecure mode.

Reference: http://stackoverflow.com/questions/...evice-unauthorized-in-android-adb-host-device
[Shield Tablet Android Development] boswelja:
ADB doesn't show any devices, and its getting to the stage where the screen dims on boot, then brightening again and so on
[Shield Tablet Android Development] Steel01:
Yeah, that should be far enough. Device won't show in adb devices unless the persistent property is set. So, push the key, set the prop, and you should be good to go. Oh, and just read the SE page again, they do it the hard way. You can just adb push the file and it works fine. Even creates missing directories.
[Shield Tablet Android Development] boswelja:
cat /data/.android/adbkey.pub

^ Returns no such file or directory :/
[Shield Tablet Android Development] Steel01:
Try:

adb push ~/.android/adbkey.pub /data/misc/adb/adb_keys
[Shield Tablet Android Development] boswelja:
adb: error: cannot stat '~/.android/adbkey.pub': No such file or directory

On the plus side, ive got the prop set up
[Shield Tablet Android Development] Steel01:
Eh? That's odd. There should be a .android folder in your home directory with the public and private keys in it. Probably created the first time adb is run for that user. At least it is for Fedora and AFAIK the officially supported Ubuntu distros. Ummm... Search around for the file and push that if you find it. Otherwise, I dunno. Build eng instead of userdebug would be the easiest alternative to pushing the key.
[Shield Tablet Android Development] boswelja:
I found the file.. I switched to windows to do this and as soon as you said home directory, i checked in my user folder and there it was XD
[Shield Tablet Android Development] boswelja:
adb devices still shows nothing, just to confirm:

* Create persist.sys.usb.config file in /data/property with the contents 'mtp,adb'

* chmod 600 /data/property/persist.sys.usb.config

* adb push .android/adbkey.pub > /data/misc/adb/adb_keys

* reboot
[Shield Tablet Android Development] Steel01:
That's what worked for me, yes. Make sure there's no newline in the property file, that caught me a couple times. Ummm... If you're on windows, maybe the keys file has the wrong permissions when pushing, mine is 640.
[Shield Tablet Android Development] boswelja:
Fixed it, there was a newline :P

Now to spend a few hours deciphering logs XD
[Shield Tablet Android Development] boswelja:
[MENTION=1416222]Steel01[/MENTION] It all seems to die here:

[ 10-17 03:49:21.836 5508: 5508 W/Settings ]

Can't get key volume_controller_service_component from content://settings/secure

android.os.DeadObjectException

at android.os.BinderProxy.transactNative(Native Method)

at android.os.BinderProxy.transact(Binder.java:615)

at android.content.ContentProviderProxy.query(ContentProviderNative.java:419)

at android.provider.Settings$NameValueCache.getStringForUser(Settings.java:1664)

at android.provider.Settings$Secure.getStringForUser(Settings.java:4260)

at com.android.systemui.statusbar.ServiceMonitor.getComponentNameFromSetting(ServiceMonitor.java:188)

at com.android.systemui.statusbar.ServiceMonitor.startService(ServiceMonitor.java:226)

at com.android.systemui.statusbar.ServiceMonitor.-wrap5(ServiceMonitor.java)

at com.android.systemui.statusbar.ServiceMonitor$1.handleMessage(ServiceMonitor.java:73)

at android.os.Handler.dispatchMessage(Handler.java:102)

at android.os.Looper.loop(Looper.java:154)

at android.app.ActivityThread.main(ActivityThread.java:6137)

at java.lang.reflect.Method.invoke(Native Method)

at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:867)

at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:757)

But thats only a warning :/

Looking further up the log (before -----beggining of main) I think its trying to load the TelephonyExt boot jar but its not there
[Shield Tablet Android Development] Steel01:
Running something CM or caf based now? If so, TelephonyExt does need included. But that should only crash the dialer and related, not the entire boot... If it's direct caf based without cm patches, then there's at least one framework patch needed otherwise the graphics stack pukes all over the place. But I don't recall exactly which ones. I only did one, there were others as well.