yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
Still doesn't boot. I have changed it in recoverys ramdisk + kernels ramdisk + fstab.qcom that's extra in the kernel.zip But it won't boot if system is on f2fs. And if I redo system to ext4 I logically need to flash the unmodded kernel.zip from you so the kernel's fstab.qcom expects ext4 again. So there's anything deeper I think that needs to be changed. Wether in rom or kernel I have no idea. On the Nexus 7 recovery kernel and rom are modded from [MENTION=2743057]legolas93[/MENTION], maybe he can help us...

L
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
If it wont boot then I'd say the ROM is causing some kind of problem :(
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
I think that it is better to use the recovery inbuilt format options after the partitions are f2fs.

So, I have for example flashed the zip to get cache to f2fs and then made another cache format with the recovery option (wipe/advanced/cache) and checked if it get's mounted without error before rebooting...

L
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
Post up your fstab.qcom that you moded inside my kernel zip file.

Also, if you can get your phone back in the state where /system is formatted to f2fs and wont boot, do this:

Wait forever till adb finally comes online (takes 15 minutes some times) and then run the command:

mount

and post the text.
[Galaxy S 4 i9505 Original Android Development] smeroni68:
Sorry, I do not follow you... my answer was for user with problem on twrp not working...

For your information, twrp wipe do not format... it wipe only... infact the wipe under f2fs is quite faster than ext4 version.

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
If you only select one thing to wipe and have set twrp to use formatting instead of wiping it will output "formatting <partition name> using mkfs.f2fs"

L

Gesendet von meinem GT-I9505 mit Tapatalk

---------- Post added at 05:46 PM ---------- Previous post was at 05:44 PM ----------

# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/system /system f2fs ro,barrier=1,errors=panic wait
/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs noatime,flush_merge,nosuid,nodev,discard,nodiratime,inline_xattr,errors=recover wait,nonremovable
/dev/block/platform/msm_sdcc.1/by-name/apnhlos /firmware vfat ro,shortname=lower,uid=1000,gid=1000,dmask=227,fmask=337 wait
/dev/block/platform/msm_sdcc.1/by-name/mdm /firmware-mdm vfat ro,shortname=lower,uid=1000,gid=1000,dmask=227,fmask=337 wait
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 nosuid,nodev,noatime,noauto_da_alloc,journal_async_commit,errors=panic wait,check
/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs noatime,flush_merge,nosuid,nodev,discard,nodiratime,inline_xattr,errors=recover wait,nonremovable,encryptable=footer,length=-16384

/devices/platform/msm_sdcc.2/mmc_host/mmc2 auto auto defaults voldmanaged=sdcard1:auto
/devices/platform/msm_hsusb_host/usb auto auto defaults voldmanaged=usbdisk:auto

L

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
This is your problem, but will probably screw your ROM over but worth a try:

barrier=1,errors=panic

remove the 'barrier=1," (f2fs does not support that option)

and change errors=panic to errors=recover
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
Will try it later when I'm back from my grandma (y)

L

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] OmniSlyfer:
Hi guys, I've a stupid question to do. Can someone explain what block cycles are exactly? Are they a sort of operations that CPU needs to do before, for example, raise or lower frequencies?
[Galaxy S 4 i9505 Original Android Development] LuigiBull23:
It's a counter in the CPU and the values represent a time interval.

boost_hold_cycles: scans at about 45 milliseconds per cycle, which equals 22 scans per second.

block_cycles scans at about 90 milliseconds, which equals 11 scans per second. That's how 11 and 22 come about.

Super_conservative blocks out all the sudden jumps in load until the counter reaches the users' set value for "block_cycles_raise"
[Galaxy S 4 i9505 Original Android Development] qtwrk:
sadly , philz doesn't boot up on me

after samsung splash screen , it went to recovery , screen goes dark , few seconds later reboot , samsung splash screen again , and then move into boot animation where stuck forever ...
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
WOOOOHOOOOOOO!!! It's booting with a f2fs formatted system partiton

It stays much longer on the bootscreen before switching to the bootanimation, but it boots now. I have looked into the ramdisk of my nexus 7's f2fs rom's boot.img and simply copied all the mount flags from there. Maybe there's something in now that's not needed or what else. But it boots.

Here's a screenshot, plus the fstab.qcom I'm using now on the kernel AND the recovery

Happy easter ;)

L
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
Excellent, glad you got it going. Just add one thing to it:

,flush_merge in the same spot as the /data and /cache, it takes advantage of a nice speed jump with latest f2fs source :D :good:

I wonder if it will work on CM 11? U try it or just broad?
[Galaxy S 4 i9505 Original Android Development] tanoxxx:
wow!!!! Bravoooooo :laugh::laugh::laugh::laugh:

How is? you feel the whole system better and more smooth than ext4? worth it?

what we must to do for make that? we must format another time the internal sd? is easy to do?

can you explain it Please?

Genius can you do integrate it in your kernel?
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
No, since Broodplank ROM might be the only one that will boot, hopefully [MENTION=3320665]9Lukas5[/MENTION] will have time to try CM 11 and or a few other ROMs.
[Galaxy S 4 i9505 Original Android Development] qtwrk:
alright , i managed to convert KT's recovery into tar and so odin flashed in

but KT's recovery stuck on initial screen and repeatedly dark, light on , dark , light on , like unstoppable reboot into itself.

anyone a little help please ?

I also managed flash CWM , but it says can't mount cache/xxx/xxx and went reboot if i try anything ...
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
Does your ROM boot?
[Galaxy S 4 i9505 Original Android Development] qtwrk:
stuck on boot animation forever...
[Galaxy S 4 i9505 Original Android Development] PiggySmalls:
Why did you need to use Odin? You should have just flashed his zip in recovery, then reboot recovery. Try flashing official twrp tar file with Odin, then flash kts in recovery.

Sent from my GT-I9505

EDIT: Looks like the man has this handled
[Galaxy S 4 i9505 Original Android Development] qtwrk:
its ok ... but i can not boot into recovery now ...

something is wrong with cache partition i think
[Galaxy S 4 i9505 Original Android Development] PiggySmalls:
It may be time to Odin a factory firmware, reroot and start over.

Sent from my GT-I9505
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
I'll try that later.

For the explanation how to do it:

No you don't have to wipe your data or cache partition again. I have modified the formatting script uploaded from ktoonsez to format system to f2fs (also made one for getting back to ext4) then edited the fstab.qcom.

- flashed format system to f2fs

- flashed the modded recovery

- made a system wipe (wipe/advanced/system)

- flashed my rom (modified updater-script for system partition format)

- flashed gapps, superSU and the modded kt-kernel

- rebooted

If you want, I'll try to add the one kt said to the fstab.qcom and try that and then send kt a pn so he can share the files to you.

L

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] qtwrk:
hmmm , still downloading the firmware , i just hope the stock firmware flashing process will make cache partition into ext4 ....

could someone please confirm me this ?
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
Extract the recovery.img of the recovery you usually use and do this:

1. Install Terminal Emulator from the Play store

2. Copy the recovery.img from your good recovery to the "/data/local/tmp" folder on your phone

3. run these commands in the Terminal Emulator app:

4. su

5. cd /data/local/tmp

6. dd if=/tmp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
[Galaxy S 4 i9505 Original Android Development] PiggySmalls:
Seeing as it formats everything, I assume it will, however I don't know for sure.

Sent from my GT-I9505
[Galaxy S 4 i9505 Original Android Development] qtwrk:
negative sir , my ROM doesn't fully boot up , it stuck on boot animation forever
[Galaxy S 4 i9505 Original Android Development] tanoxxx:
Thanks, very Kind, don't seem difficult but seem to much think to do and I think I must do full wipe my actual rom or maybe change rom :(

I wish there was an a much easy and fast way to got it, like flash kernel or similar..

I hope you found, if you can, an easy way to got it :fingers-crossed::fingers-crossed:

Anyway thanks to you and KT for your time, work, and Kindness:good::good:
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
Ok, try this then:

1. Let the ROM do its bootanimation forever till you get access to adb (might take adb 10-15 minutes sometimes to come online)

2. adb push recovery.img from your good recovery to the "/data/local/tmp" folder on your phone (or some other available folder, maybe just root folder)

3. run these commands after running "adb shell":

4. su

5. cd /data/local/tmp

6. dd if=/tmp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
[Galaxy S 4 i9505 Original Android Development] qtwrk:
line 6 , /by-name/recovery , i type exact the same thing ?

by the way do you think odin full stock firmware will help ?

I got adb on PC , but i can't push file into everywhere , including root , read-only file system

when i try

adb remount , it says permission denied
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
The only thing you will change in line 6 would be this part:

dd if=/tmp/recovery.img

it depends on where you put recovery.img. Everything else is the same on line 6. Odin should most definitely work.
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
It is very simple

Flash the modified recovery, flash format system.zip, flash your rom/gapps/supersu etc again and as kernel the modified one for f2fs booting. Your data will stay as you only change the system partition ;)

L

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] qtwrk:
sorry to bother again

i can't push , it says read-only file system

i tried adb remount

adb shell , su , mount -o remount rw /system , chmod 777 /system and something i just googled out , but with no success ...
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
Guess you will have to do the odin way if you cant find a place to push. You should be able to push somewhere, maybe /external_sd folder.
[Galaxy S 4 i9505 Original Android Development] qtwrk:
but ... i odin'ed both official twrp, phliz , CWM, and 2 of yours , non of them boots up ...

even adb push to /external_sd/recovery.img gives me a permission denied ...
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
But if you flash cwm or philz the recovery starts? (With a lot errors as it's unable to mount data and cache of course)

L

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] qtwrk:
CWM: it goes into main screen , but with all kinda error like can't mount cache/xxx

Phliz , doesn't even boot up , after "rebooting recovery" it went dark , few seconds after that , goes to samsung splash screen and start normal boot up

do you think pit repartition will work ?
[Galaxy S 4 i9505 Original Android Development] tanoxxx:
ok, can you give me please the link the files needed? when i found 5 minute i will try it :good:

thanks
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
Ok, can you try if cwm boots (ignore those errors) to go to the format submenu and format cache and data partition and tell us what cwm outputs then?

L

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] qtwrk:
negative , it reboots immediately after i touch any of main menu options ...

I'm attempting pit repartition ... will that be OK ?
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
I think it should work, but as long as I can do it otherwise I don't use Odin/stock firmware/pit-repartition

L

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] qtwrk:
why is that ?
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
hm, can't tell you 100%. I think I simply don't trust Odin/usb-connection for repartiton my device^^

Ok, er. If you flash stock cwm, pull the battery for ~10sec and then reinsert and boot cwm. Does it still crash if you try to tap anything?

L
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
What if you get into CWM recovery and then flash my TWRP for ext4 and get everything formatted back to ext4?
[Galaxy S 4 i9505 Original Android Development] OmniSlyfer:
But... wouldn't be better to leave the CPU free to change frequencies immediately, in order to make the system more fluid and at the same time more battery-friendly? I'm missing something for sure :/
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
If you dont use the blocks the cpu will over react and hurt your battery life. You have to decide if you want battery or performance
[Galaxy S 4 i9505 Original Android Development] qtwrk:
that's my problem

I can NOT enter any of these recovery ...

alright , thanks for all of you , I re-partitioned and solved problem ...

---------- Post added at 10:04 PM ---------- Previous post was at 10:02 PM ----------

well , me neither ... but this time i have to try , and for lucky , seems my problem has been solved , and thanks for you help
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
Ok, so now your phone is working again?
[Galaxy S 4 i9505 Original Android Development] qtwrk:
yep , thanks for everything.
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
Are you open for a few further experiments? If yes, pm me I'll tell what I've in mind ;)

L
[Galaxy S 4 i9505 Original Android Development] OmniSlyfer:
But why does it happen? I understand that with low values of block cycles the CPU will be more sensible to little variations of work load, but shouldn't also scale down faster?

I'm sure that you are right, but I would like to understand how ktoonconservative works in order to start tweaking my own profile :D
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
nobody stops you from changing to and make your own findings. Exactly for that those values are so highly customizeable

L
[Galaxy S 4 i9505 Original Android Development] LuigiBull23:
That's what "freq_step_lower" and "sampling_rate" are for.

"block_cycles_raise" only applies to CPU scaling up. You can disable it anytime. You don't have to use it if you don't want to.
[Galaxy S 4 i9505 Original Android Development] OmniSlyfer:
You're misinterpreting. I don't know if I want to use it or not until I understand what all the parameters do.

Now if I've understood what I've read in other posts: sampling rate indicates how frequently CPU check if frequencies need to be changed. Block cycles only affect CPU scaling up, and it help to get a less aggressive behavior when CPU needs to increase frequencies.

Am I right?
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
Ok, cm11 also boots fine with system at f2fs :)

L
[Galaxy S 4 i9505 Original Android Development] dclarkg:
Nice! Do you think that GE roms will work on f2fs?
[Galaxy S 4 i9505 Original Android Development] nexuspur:
Its a little bit offtopic but I want to ask you guys if you are using the optimized dalvik patches?
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
Awesome news!!!!!!!!!!!!!!!! :good: :highfive:. I figured it would
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
They do NOT work.
[Galaxy S 4 i9505 Original Android Development] LuigiBull23:
I understood just fine. I only answered to those in which you asked about. The other parameters require some reading on your part, which you did do.

You are correct on all counts but "block_cycles_raise" is what prevents the CPU from reacting to sudden load. The other block_cycles determines when to hotplug other cores in or out.
[Galaxy S 4 i9505 Original Android Development] jakemog:
My notification led stops working when Ktweaker starts at launch with latest kernel? :/
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
Looks like I found a clean way to detect which folders r formatted to f2fs so I can keep 1 kernel zip whether people use ext4 or or f2fs for data and cache or f2fs for data and cache and system. :D :D
[Galaxy S 4 i9505 Original Android Development] qtwrk:
:p don't forget to mention carbon as well
[Galaxy S 4 i9505 Original Android Development] Tergon:
What is the programming you are using that shows which file system you are running?
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
Use partition Table from app store. Im got mine running all 3 partitions on CM, seems to have hurt performance for some reason by adding the /system partition to the f2fs format
[Galaxy S 4 i9505 Original Android Development] Tergon:
Thanks...
[Galaxy S 4 i9505 Original Android Development] vagaBond07:
As I read the thread there has been a lot of improvement s on F2FS system. [MENTION=4325945]ktoonsez[/MENTION], I want to try the F2FS system.
[Galaxy S 4 i9505 Original Android Development] Synergy510:
If you're running Ktoonsified V6 and it's between 11PM-6AM your time, that could be the reason why it's disabled. The profile disables the LED from those times. Check in the KTweaker app: Main settings > LED Settings and check if the LED isn't disabled at the bottom
[Galaxy S 4 i9505 Original Android Development] tanoxxx:
Sorry Kt, im not very good with english, but i try, do you found a way to do a kernel with all f2fs? with all 3 partition in f2fs?
[Galaxy S 4 i9505 Original Android Development] mythoc:
i've been using f2fs with a tablet of mine for about a month now, had not a single problem since, also got amazing perfomance increase! cant wait to try f2fs with my s4! I'll try search for all files needed and test today :)

Great job kt & lukas, im reading your posts now and i believe that you are close to finish f2fs proccess for all partitions!

Let me know if you need any testers, today is GameOfThrones + Flash Experimental staff day :P
[Galaxy S 4 i9505 Original Android Development] MRDOCA:
Sux I got a s5... now my wife only gets ktoonz kernel on my old s4.

Tapped on my Omega driven I9505
[Galaxy S 4 i9505 Original Android Development] Mussels84:
my note III arrives tomorrow - good thing i'm keeping one S4 on ktoonz, or i'd get lonely.
[Galaxy S 4 i9505 Original Android Development] ghira283:
hello guys, I do not know if she can depend on the kernel, but I have a touch of delay in games, home screen and drawer works fine, sul's4 with my wife rom ufnb8 prerooted problems, I hope I explained myself, my English and translated
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
Instructions for ALL-F2FS

Disclaimer: Neither I, ktoonsez nor anyone else is responsible if your phone dies, cooks your coffee or starts a zombie apocalypse

Hey all, here are the instructions for getting ALL-F2FS (means /system /data and /cache).

For those having /data and /cache on F2FS yet, only do the black and green things and your data will stay untouched.

For all others: This instructionset is meant for a fresh install. Following the instructionset means you'll loose all data stored on data, cache and internalSD. So before you start, make a backup of your internal sd and a nandroid backup to your externalSdCard!!

The black lines are for everyone

The red lines are for people having everything on ext4

The green lines are only for people having /data and /cache on f2fs but /system still on ext4

get the latest release of your used/wished aosp based rom

change the format and mount commands in your rom's updater-script like below:

(For those don't know what an updater-script is, you can find it in the folder structure in your rom zip down in META-INF folder)

run_program("/sbin/mkfs.f2fs", "/dev/block/platform/msm_sdcc.1/by-name/system");
mount("f2fs", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");

download TWRP-KT.ALL-IN-1.zip

Now put the modified rom-install.zip and the downloaded TWRP-KT.ALL-IN-1.zip on your externalSdCard

In Recovery:

Flash the TWRP-KT.ALL-IN-1.zip

Reboot recovery

Go to wipe > advanced > Format Data > type "yes" (CAUTION: This deletes all your data and internalSD!)

go to wipe > advanced and tick /system and /cache

restart recovery (answer the question about Supersu with Do not install)

Configure TWRP settings again as they got wiped, too, to force it again to F2FS

In case the recovery outputs that /system, /cache or /data can't be mounted go to wipe/advanced and select the unmountable again

flash your rom

flash gapps if you want

flash a kernel with F2FS support

OPTIONAL: you can try to restore ONLY data from your made nandroid, but have a look to the recovery's output, it has to say formatting data using mkfs.f2fs If it says make_ext4fs your /data partition is back to ext4 and you have to go to advanced/wipe and select Format data and confirm it

reboot

List of confirmed working roms:

cm11

broodplank1337's AOSP

carbon

SlimKat

BeanStalk

SOKP (Sonic Open Kang Project)

Mahdi-Rom

LiquidSmooth

anything not listed, please tell me

L
[Galaxy S 4 i9505 Original Android Development] tanoxxx:
Great!! Bravo :laugh::laugh::laugh:

One question, im now on cache and data in f2fs, i only must to convert system to f2fs..

i can do that without lose configuration, app, setting and format the internal sd? if yes how?

thanks
[Galaxy S 4 i9505 Original Android Development] smeroni68:
It is written on the post... only green steps!

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] ianczarina:
Will this work with stock TWRP?
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
no, because it hasn't the ability to format using f2fs. Theoretically it should even give you a mount error for all partitions on f2fs. Instead KT wouldn't have had to modify it ;)

L
[Galaxy S 4 i9505 Original Android Development] smeroni68:
I followed green steps... but after reflash I've checked /system partition number 16... it is still ext4...

Edit: i forgot black lines!... will try when back home... need to update updater script...

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
what rom do you want to flash?

L
[Galaxy S 4 i9505 Original Android Development] ianczarina:
Do I have to change the updater script on every nightly I would be flashing?
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
Yep, because instead the updater-script would tell the recovery to reformat the system partition back to ext4

L

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
Its kinda random the way it works, I believe the msm-thermal file was 70 stock but just has a bizarre algorithm that is not very effective obviously since it is easier to Antutu it, also it appears that the thermal code (its closed source so I am just speculating) knows when bnechmark apps are running and lets things just go higher temp wise to get a good score.