yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] Mostafa Wael:
Master,

I think you should think of another solution rather than flashing the ROM again if i want to change kernel.

ROMs like this one "team-ub.co.uk" and omnirom use OpenDelta which only downloads the .update files and merge them. So it will be hard to get a .zip file for the ROM. I think you got my point...

I would think a cleaning script will be extremely helpful.

It is just an idea..

I will be very pleased to have a solution for this...

Thx!
[Galaxy S III Original Android Development] DerTeufel1980:
I'll look into it when I don't have anything else to do.

Btw there's always the full rom at the homepage of ie omnirom.

And why should you want to flash another kernel? :p are you looking for one with less options, or has mine just been too fast? :D

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] Mostafa Wael:
Not at all bro, i just wanted you to update this theory for changing kernels. :D

I am loving your kernel so much!!!! Most responsive kernel ever
[Galaxy S III Original Android Development] DerTeufel1980:
If everything goes well, the next one is going to make your device fly. I am almost done with adding true support for f2fs Filesystem (Which makes The moto g as fast as the s4)

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] coolhof:
Could it be faster?

My phone is almost flying. :D

Great job.:thumbup:
[Galaxy S III Original Android Development] Scarface1991:
Yeah I also have problems with Bluetooth and my Car Radio. Bluetooth service just crashes when I try to connect to my radio.

Never had those problems with cm10.2

Using temaseks V30 with latest devil kernel.

I hope that they will fix this soon since I don't want to use ancient technology and burn cd's anymore

:D

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Original Android Development] ric69:
Yes hope too, I tried this morning SlimKat 4.4.2 on 2nd rom, BT is working fine in my car :silly: didn't try about settings lost after a switch, I will :)

Édit : no more problem
[Galaxy S III Original Android Development] DerTeufel1980:
Yes, it can. Just Google for f2fs benchmark. In some cases it's twice as fast as ext4, if not twice as fast, it's still faster

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] DualJoe:
How exactly will it work? Will the recovery patch the roms appropriately (fstab)? Can we migrate via nandroid backup?
[Galaxy S III Original Android Development] DerTeufel1980:
I have modified my recovery to mount either ext4 or f2fs, and you can also use it format to either of the file systems. Unfortunately, if you format data partition, it formats so card, too, because sdcard is just a link to data/media.

Once formatted you can use every recovery feature as before (including nandroid create/restore).

Mounting partitions is done by kernel, no need to modify any rom files.

You just won't be able to use another kernel or recovery, because none can handle f2fs

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] drgreenth:
Is there any f2fs tools to convert existing ext4 to f2fs? And if there is can u add them to your recovery?
[Galaxy S III Original Android Development] DualJoe:
Both fs use POSIX permissions so I guess a simple high-level nandroid backup should do the job.
[Galaxy S III Original Android Development] cba1986:
Can't wait to try. I don't mind formatting the entire phone if it means that the phone can go twice as fast.
[Galaxy S III Original Android Development] drgreenth:
Same here. This makes me completely stick with devil.
[Galaxy S III Original Android Development] DerTeufel1980:
Yes, there is, and I have added it to recovery.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] drgreenth:
It would be nice if you would pick latest philz commits up to version 6.08.9 to your recovery. Is it possible?

Edit: or even 6.09..

Edit: ment 6.07.9 or higher :)
[Galaxy S III Original Android Development] cheese458:
Does f2fs make EVERYTHING faster? :D
[Galaxy S III Original Android Development] cba1986:
We will have to wait to find out.
[Galaxy S III Original Android Development] shaarky:
Sorry for OT, but if its true what you are saying (and I'm sure you are), you should come for last time to I9000 to save this old device :) :) Just kidding.
[Galaxy S III Original Android Development] JustArchi:
Devil, f2fs does not always ensure that data is syncing to the disk as with the ext4, which could potentially put data at risk in case of a kernel issue or power loss.

Also I'm not sure but last time I was checking f2fs it didn't have working fsck (repair option) and capabilities support, capabilities were added recently afaik.

I'd think twice before moving from ext4 to f2fs, even if f2fs indeed offers performance boost. It's not so stable in my opinion and could make more harm than good. ext4 is proven to be as stable as possible and it's still the best choice out of box.

But of course it's up to you.
[Galaxy S III Original Android Development] drgreenth:
Its up to users will they choose f2fs or not. Its great that somebody makes this possible even in this f2fs "unstable" state.. Warning texts would be in place.
[Galaxy S III Original Android Development] JustArchi:
Well, I just don't want to think about all incompatibility possibilities around recoveries/roms/kernels. It's not usual backport :).

Of course thumbs up all the way for awesome development Devil.
[Galaxy S III Original Android Development] drgreenth:
Could not agree more but if its well advanced/hidden option then it should be semi safe side ;)
[Galaxy S III Original Android Development] DerTeufel1980:
I don't know about fsck, but I'll check this. Besides this, there have been many improvements in Linux 3.13 which I have added till the last commit yesterday. Also, moto x is using f2fs as default, and I don't think any manufacturer would sell a device with a filesystem which is completely unstable.

Anyway, as others said, it's up to the user to format to f2fs, the kernel just tries mounting each partition as ext4 first and if it fails it tries f2fs.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] cheese458:
does anyone else experience slight lag when opening the app drawer? I mean it is really miniscule but it is strange considering how no other kernels do this and the rest of the experience is so smooth...Im using the default config, are there any recommendations to change to make things smoother or generally better?
[Galaxy S III Original Android Development] JustArchi:
Devil, are you able to extract needed binaries for creating f2fs filesystem? Like make_f2fs. I just don't want to change recovery.

I'd be able to implement it as an option to ArchiDroid, so actually instead of formatting system partition as ext4, I'd format it as f2fs with also flashing your kernel. I just need some tips about needed commands + binaries. So everyone would be able to test it out regardless of recovery.

(Of course if it's possible)
[Galaxy S III Original Android Development] DerTeufel1980:
I actually don't change system partition, because it would require to modify the each rom zip. Instead I only give the option to format data and cache to f2fs (probably I'll create f2fs for secondary system, because I need to modify the zip anyway) .

The f2fs binaries created during compiling are just symlinked to recovery binary, but I guess placing recovery binary along with the symlinks somewhere should be enough for formatting.

Meanwhile I successfully formatted my /data partition to f2fs and restored my previous nandroid. All is working well :)

Tomorrow I need to patch some fstabs for devices different from my note2, then it should be ready for release.

Btw: do you know why /cache isn't used for dalvik cache of system apps? I just noticed it and was irritated by this

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] DualJoe:
By design it shouldn't be less safe than ext4 or any other fs with write cache. Journaling should keep integrity intact (but doesn't protect against data loss). But yes, its experimental... expect everything.
[Galaxy S III Original Android Development] JustArchi:
It's only being used for dex2oat conversion afaik.

I asked for binaries because I could include f2fs support in my ROM, along with your kernel and we could test how it performs under load. Formatting only /data and /cache won't be enough, as system relies mostly on reading/calling system binaries, therefore it would increase overall android speed as well.

Keep me informed Devil, we can make use of that ;).
[Galaxy S III Original Android Development] drgreenth:
And if we modify fstab after rom flash to f2fs there should be option to format /system to f2fs as well..
[Galaxy S III Original Android Development] DerTeufel1980:
When I am done with adding it (during this week), I can upload the recovery binary and symlinks. Place it in the rom zip and extract it to tmp. Then call a script to format system, instead of the usual edify format. In the script it's just: tmp/make.f2fs -l system $blockdevice.

But one wouldn't be able to flash gapps etc, unless using my recovery.

You don't need to modify fstab. You would need to modify the updater script, and replace the format ext4 with f2fs (when you are using my recovery). You would need to do this every time you install a new rom

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] drgreenth:
Yes but if you install rom and modify fstab after install? Or just format system to f2fs and restore nandroid and then modify fstab (within recovery) and when installing new rom zip it just formats it to ext4 anyway? Convert, modify.. ? I mean this is quite hassle but makes system usage for f2fs possible for power users? Or have I misunderstood something?
[Galaxy S III Original Android Development] DerTeufel1980:
There's really no need to modify anything besides updater script.

Don't ask me why updater scripts for roms are the way they are... Maybe the person who made the first did not think about it, and all the others just copied it... I don't see any reason to force reformat to ext4 on every rom flash, but this is how it is.

There's also no point in mounting partitions by calling the underlying block device, instead of relying on the recovery fstab, but roms do this (no other zip does this).

These are the reasons my recovery needs to modify every rom zip, when installing to secondary fs.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] DualJoe:
Can't you do it on the fly by replacing 'format' command that checks on a case basis what to do?

Or provide a persistent option to disable (dummy) the 'format' command?
[Galaxy S III Original Android Development] DerTeufel1980:
I am not sure how updater script and updater binary work together, but I think they are independent of the used recovery. And then I can't do anything against it

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] JustArchi:
Just mention me when you're ready with sample script and binaries, I'll implement it in ArchiDroid and everyone will be able to flash rom using f2fs as /system partition, then we can go further and I can implement a full f2fs reformat (/data etc) if needed. This way we can have a nice playground for f2fs.

https://github.com/JustArchi/ArchiD...NTAL/META-INF/com/google/android/aroma-config

https://github.com/JustArchi/ArchiD...AL/META-INF/com/google/android/updater-script

My updater-script is far more advanced ;).
[Galaxy S III Original Android Development] DerTeufel1980:
Of course I know about aroma, but you are also using mount mmcblk... And format ext4...

Why not sbin/mount /system and rm -rf system/*

Of course, if only one changes it, it doesn't matter ;)

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] JustArchi:
Good question, but on the other hand even CM/Omni and other ROMs use absolute path to block device ;).

https://github.com/JustArchi/ArchiD.../google/android/aroma/exec/archidroid_init.sh

shh :D.
[Galaxy S III Original Android Development] DerTeufel1980:
Yes, everyone does. I just don't know why. Since it's not going to be changed for every rom, you are good to keep it as is

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] JustArchi:
The thing is, I can easily change that if needed (for f2fs for example). My ROM is really flexible in terms of implementing stuff.

You have no idea how much time I've spent to make it so :D.

Can't wait to try your f2fs magic.
[Galaxy S III Original Android Development] DerTeufel1980:
For f2fs, you could run a script from aroma which tries mounting system as f2fs, then check proc/mounts if system got mounted, and if yes return true to aroma. Then add an option to use f2fs for system. If previous test already was true, set default to use f2fs, otherwise uncheck it by default.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] JustArchi:
That shouldn't be needed, as my mount script should handle f2fs even now through automatic filesystem. As long as it can be mounted from recovery.

I only need to change formatting :).
[Galaxy S III Original Android Development] DerTeufel1980:
I meant for formatting, to give users the choice, but without the risk of wrong selection, because default would always be the current one

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] cba1986:
I like what is cooking here. Hope we can test it soon....
[Galaxy S III Original Android Development] JustArchi:
I replaced all generic mount/umounts commands with my new improved mounter.

https://github.com/JustArchi/ArchiD...-INF/com/google/android/aroma/exec/admount.sh

https://github.com/JustArchi/ArchiD...INF/com/google/android/aroma/exec/adumount.sh

This should be the only thing left:

https://github.com/JustArchi/ArchiD...ETA-INF/com/google/android/updater-script#L43

Devil, will cwm recovery be able to mount /system as f2fs when using either busybox mount or mount with -t auto filesystem? Or will it require your own recovery?
[Galaxy S III Original Android Development] DerTeufel1980:
I was getting into a bootloop with f2fs on system... Need to try again...

Please just keep the mount and format stuff in updater script (or maybe replace just format with rm -rf), otherwise your rom wouldn't be flash able as secondrom anymore.

I am using sed to replace the mount command in updater script with the one needed for secondrom. With your script, sed would fail. :(

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] JustArchi:
My rom is not flashable as second one anyway because of aroma, so it's not big deal :p.

---------- Post added at 10:25 PM ---------- Previous post was at 10:23 PM ----------

I think that better aproach would be to mount /system before flashing zip and ignoring all unmount commands, this way /system would be mounted whole the time, my mount script will try to mount system only if it's not mounted yet. And then we can replace format with rm -rf.

Yeeeah!

This will be the proper way :).
[Galaxy S III Original Android Development] DerTeufel1980:
Does it really fail? Did you try it? Many Aroma zip files are working. :)

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] JustArchi:
https://github.com/JustArchi/ArchiDroid/commit/9ff8de8b2215af9823cd0fa349f29f19f3a888af

Well, I realized your idea. My rom should be able to be flashed on top of f2fs /system partition. It mounts /system only if not mounted already and then executes rm -rf instead of formatting. Also I got rid of every remount, so eventual f2fs won't be remounted during installation.

Now it's OK I think :). If you mount /system as f2fs before start of flashing, it won't be even remounted during it. If you don't, my script will try to mount it using automatic filesystem, then if it fails doing so using busybox mount and mount, it will mount it through ext4.

Perfect, bring it on Devil :D.
[Galaxy S III Original Android Development] DerTeufel1980:
Great solution :)

I also managed to fix f2fs formatted system to boot. Now I have system, data and cache set to f2fs :)

Formatting system to f2fs doesn't work by using edify script, because the updater binary can't handle it. Calling a script which formats should be working fine. I just formatted system to f2fs from recovery and then restored my nandroid of system (I have added an option to keep current partition type during nandroid instead of repartition to ext4).

Until more roms are going to follow archidroids way, you'll always need to perform these steps if you want to use f2fs on system, too.

Btw: what's the size of cache partition of s3? Is it 1.3 GB? I am still worried about the wasted space in there.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] JustArchi:
That's not a problem. The question I'm still asking is if I'm able to format & mount f2fs through any recovery, even using scripts. Is f.e. CWM recovery able to properly format partitions as f2fs and then mount them or does it require your specific modified recovery?

Because if it's obtainable with scripts and custom binaries like mkfs.f2fs without throwing away other recoveries, then it'd be beautiful.
[Galaxy S III Original Android Development] DerTeufel1980:
Devil2

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] devarajreddy4ever:
hi

plz reply.

hi,, now I am using neat rom android 4.3 sammy...

now can I flash this kernel and

can I install temesek rom android 4.4 aosp based as the 2nd rom
[Galaxy S III Original Android Development] riso123:
Anyone else get battery drain on this kernel?
[Galaxy S III Original Android Development] DerTeufel1980:
No, currently only dualboot with aosp 4.3 roms is possible in theory. But even this could be not working properly

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] RohanAJoshi:
is this kernel compatible with latest temasek's v6 ? i.e latest mali kernel.
[Galaxy S III Original Android Development] DerTeufel1980:
What's up? Do you want me to add some bugs :P if got the feeling you need something to complain about :D

I have added a new gpu control to mali3rp2 for the next version. Hopefully it doesn't work correctly :D

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] jeebspawnshop:
LoL, Teufel, you're a crazy one :)
[Galaxy S III Original Android Development] riso123:
I'm damn bored. Can you release a new kernel for me to flash with lots more features to tweak around with please.

Kthnxbai :p
[Galaxy S III Original Android Development] DerTeufel1980:
new version uploaded :)
[Galaxy S III Original Android Development] lucascm08:
your kernel is amazing man!! can you please implement MDNIE controls (chroma saturation and digital edge enhancement) and some equalizer presets?? if its possible, Googy Max preset is the best for me =D
[Galaxy S III Original Android Development] DerTeufel1980:
It already has mdnie control.

What's a googy max preset? Leave everything on Samsung stock? He does not have mdnie control

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] coolhof:
Yes you did it again.:D:thumbup:

Dualboot is working now with two 4.3 Sammy roms for me.

It's fast with booting and very snappy.

Very good job.

Going to test it this evening further.

Thanks maat you make my day.:thumbup::D
[Galaxy S III Original Android Development] DerTeufel1980:
Thanks for your feedback :) I hope other combinations of roms are also working. Let's wait for others to try :)

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] DerTeufel1980:
uploaded a new recovery. it's compatible to android 4.4 now
[Galaxy S III Original Android Development] morenoro:
YES....YES....AND YES!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

DUAL BOOT WITH SAMMY (1st Rom) AND KITKAT CM11 (2nd Rom)........

WORKING!!!!!!!!

THANKS, THANKS AND OTHER THOUSAND THANKS

(Sorry for capitals, I´m very excited :D
[Galaxy S III Original Android Development] coolhof:
Looks like Christmas today:D

No enough time today to test everything......;)

Great job.:thumbup:
[Galaxy S III Original Android Development] lucascm08:
I was talking about the audio preset configuration... And chroma settings are important for me, without this function, the colors in my screen are not vivid. Sorry for my bad English
[Galaxy S III Original Android Development] DerTeufel1980:
Ah, I missed the audio thing. I don't think I'll add some presets to it, sorry.

Mdnie control has all the features it had before the merge of update12. Did you try trickstermod to configure it

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] lucascm08:
No, but i will try that, thanks =D
[Galaxy S III Original Android Development] cba1986:
Congrats for making f2fs working. It bring the perfomance boost as expected?
[Galaxy S III Original Android Development] DerTeufel1980:
I can't tell. You need to try it yourself.

Formatting wouldn't be an issue I guess, but mounting in recovery could be one. Maybe you could use open recovery script to mount system and data at recovery boot, but nandroid would be broken in any way.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] drgreenth:
[MENTION=5161352]JustArchi[/MENTION] what we need to point to tema to get f2fs system support for his rom as well?
[Galaxy S III Original Android Development] DerTeufel1980:
Could one please tell me, what's the cache partition size for primary and secondary rom. And how much space is free. Thanks

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] JustArchi:
Well, if you could try to write such scripts, it would be awesome. Don't get me wrong, I'm just trying to make it as compatible as possible :).
[Galaxy S III Original Android Development] DualJoe:
Primary:

/dev/block/mmcblk0p8 1007.9M 95.7M 912.2M 9% /cache

Secondary:

551.2M 9.3M 541.9M 2% /cache

Edit: My primary cache still holds some obsolete dalvik-cache data (~77MB). Have to wipe it one day...
[Galaxy S III Original Android Development] DerTeufel1980:
Where is your dalvik cache data coming from? There's no data for me (not using art)

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] ric69:
Here is what I have

Envoyé de mon GT-I9300
[Galaxy S III Original Android Development] DualJoe:
Temasek's ROM experiments... He revoked it due to (3rd party) kernel incompatibilities and to keep it CM compliant if I remember correctly...

What about a kernel object? Shouldn't that work for other kernels too? I'm not sure about cifs.. They swapped it like crazy between kernels..
[Galaxy S III Original Android Development] DerTeufel1980:
Kernel Objekt would only ensure, the recovery could use it to mount, it still wouldn't know about the existence of a f2fs Filesystem. Also, ko can only be loaded to a kernel which is built with f2fs option enabled, because the module needs kind of an interface to interact.
[Galaxy S III Original Android Development] JustArchi:
Can't we mount it with third-party standalone mount binary? Same as standalone mkfs.f2fs?

Well, you're the head developer here Devil :).
[Galaxy S III Original Android Development] DerTeufel1980:
Yes, you just can use mount -t f2fs.... If the underlying kernel supports f2fs (didn't try without). But still, how should the recovery know about using this mount flag when you want to flash gapps for example.

I have told my recovery to try f2fs Filesystem, when ext4 fails.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] JustArchi:
Well, my mount script for example uses (busybox) mount -t auto /system, so if kernel knows how to handle that, everything should work.