yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] DerTeufel1980:
Yes, but the recovery tries mounting with the fs specified in the recovery.fstab, which is ext4 for us, if this fails, it just tries using mount binary (which could work like your implementation, but I am unsure about this).

Anyway we can try soon, and I also asked phil to add my f2fs patch to his recovery

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] JustArchi:
Well, if Phil adds f2fs to his awesome recovery then I don't care about recovery incompatibility anymore :D.
[Galaxy S III Original Android Development] shaarky:
DerTeufel1980,please,dont skip TWRP recovery... :) It would be really pity...
[Galaxy S III Original Android Development] DerTeufel1980:
If you don't use f2fs you still can use twrp. They also can add the changes needed to support it for our device. I just can't submit the patch, because I never coded twrp.

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

I know this is sort of off topic, but I just wanted to say how awesome it is to see the dev of my favourite ROMs working so closely with the dev of the best kernel. Thanks to both DerTeufel and Archi for all of your hard work!
[Galaxy S III Original Android Development] dyval:
Will there be an update for the recovery? Not an ETA..just wondering.. Thanks
[Galaxy S III Original Android Development] -MaD-:
I just understand 50 to 70% but also this sounds great! Thanks to the glorious devs here!

Edit: 1000th post in this thread is a thank you post :)

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Original Android Development] Moster2:
No, of course not. He is doing the patch just for himself :P

You could have answered that question on your own.
[Galaxy S III Original Android Development] zodiaxe66:
You just made my day after a hard day's work:highfive:
[Galaxy S III Original Android Development] cba1986:
[MENTION=4196889]DerTeufel1980[/MENTION] Any update on f2fs?
[Galaxy S III Original Android Development] DerTeufel1980:
Yes, I finally managed to install Sammy as secondrom with all partitions set to f2fs

Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
[Galaxy S III Original Android Development] cba1986:
Excellent!!

Do you notice a perfomance boost or is the same as ext4?
[Galaxy S III Original Android Development] xeizo:
Great news! I wonder how well it performs, and of course looking forward for a reasonably easy method to try it for myself. It do sound a little complicated to be able to keep the filesystem intact over rom upgrades, very interesting stuff anyway :laugh: :good:
[Galaxy S III Original Android Development] Hesham_3del:
[MENTION=4196889]DerTeufel1980[/MENTION]

A quick question please, I want to use your kernel and I'm coming from Googy-max.

I'm using Omega rom v54, so I just 1) flash your kernel and 2) re-flash without wipe my rom ?!

Am I right ?
[Galaxy S III Original Android Development] JustArchi:
It depends on ROM compatibility. For example ArchiDroid from version 2.3.4 and 1.7.7 onwards will support F2FS-friendly method of flashing.
[Galaxy S III Original Android Development] DerTeufel1980:
Second rom system is going to be formatted to f2fs automatically.

Primary rom would need to implement the fix by justarchi .

Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
[Galaxy S III Original Android Development] :
Hi Everyone! Just a quick question about dual booting. I have managed to dual boot my i9300 archi (1) and omni (2) using devil kernel. Do you think there is any danger in the long term of damaging my phone using dual boot as obviously this isn't a standard Samsung or Android device thing to do? Any advice welcome. :)
[Galaxy S III Original Android Development] DerTeufel1980:
No, you can't damage your device by using dualboot

Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
[Galaxy S III Original Android Development] DerTeufel1980:
Just Flash the kernel

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] cheese458:
Does anyone have any recommendations for kernel settings on temasek's v36? Thanks
[Galaxy S III Original Android Development] jesterpaul:
I'm using the devil recovery and kernel for a long time without issues. I run Temasek version of CM11 and Omni. For my device it's the best kernel. So smooth it's unbelievable.

That said I have never dual booted (just use Nandroid backups).

I've been reading quite a bit, but can't seem to solve an issue.

When I select dual boot menu and try to create second ROM partition I get an error: it says something along the lines that it failed to create it and to check temp log (which I can never actually find when I search for it with a file explorer).

Any ideas what causes this?

I have a 32GB class 10 SD card.
[Galaxy S III Original Android Development] maxq1:
^ make sure you have at least 1.5gb free on internal storage. ext sd doesn't matter. it's on the dual boot faqs, btw
[Galaxy S III Original Android Development] ashok:
same thing for me. I am running Omega rom on primary OS. and want to install Temasek unofficial CM in the secondary. But unable to create secondayr rom parition as said before. Have more than 6 gb in phone memory.any help please
[Galaxy S III Original Android Development] jesterpaul:
I should add. On internal storage I have way more than that free. Hence I'm asking in the forum
[Galaxy S III Original Android Development] DerTeufel1980:
Did you both have dualboot running on googymax before? Then just boot your primary rom and delete data/media/.secondrom/

If you didn't have, use aroma filemanager to copy the log file from /tmp/recovery.log to your sdcard to post it here

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] jesterpaul:
Went to aroma file manager but not there.

So I reinstalled devil recovery. Strangest thing happened.

I went to reboot recovery and it starts loading Omni like a clean install. I swear I didn't select install ROM to secondary partition, but it booted as a secondary ROM. I can now dual boot just fine.

I have never even successfully completed dual boot set up in recovery.

Strangest thing ever.
[Galaxy S III Original Android Development] Jejebond:
Hi !

Seems like ZRAM isn't working for me.When i apply and left the app, the phone freeze, and restart in boot loop.

"ZRAM Status" app show me an error when i open it.

So i guess something is wrong with last version. it worked on 25.12.2013 version (Can i have a link to download too plz)

ROM: Pac man nightly 01/11/2014
[Galaxy S III Original Android Development] DerTeufel1980:
It's because zram is outdated and I am using zswap now.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] JustArchi:
Okay Devil. Just released AD 2.3.4 with f2fs-friendly method of flashing. Everybody is waiting for you now :laugh:.
[Galaxy S III Original Android Development] enr88:
Great!! But just one question..maybe stupid... Before the flash of the new AD2.3.4 with the new Devil kernel when it will be released, i need to backup all my data of internal sdcard?

Inviato dal mio GT-I9300 con Tapatalk 4
[Galaxy S III Original Android Development] JustArchi:
If you reformat /data to f2fs, you will obviously lose your internal sd card content. But if you just format /system as f2fs (standard flashing without wipe), this is not needed. Up to you.
[Galaxy S III Original Android Development] enr88:
Ok, but if i want the all the boost performance that will do f2fs, i need full wipe? And i need the new recovery from Devil to do this, is correct? :cyclops:
[Galaxy S III Original Android Development] JustArchi:
Yes.
[Galaxy S III Original Android Development] Undermyoath:
So if I'm not wrong:

It isn't flashable on other roms, next to yours? (which is an excellent rom nonetheless, I thank you for that one!)

And we need to use the special recovery made by DerTeufel1980? (Which isn't a bad thing either, just wanna know)

I'm really curious about the actual speed difference in total so :D
[Galaxy S III Original Android Development] JustArchi:
1. You need to reformat all partitions, including /system /data /cache (/preload?) to f2fs to gain real improvement over ext4.

2. By reformatting you're obviously losing all data.

3. You can reformat and mount f2fs only in the recoveries, which support this function. As for now obviously devil's recovery but for example Phil, developer of PhilZ Touch Recovery is also looking at this.

4. The ROM you're flashing must be compatible with f2fs. Otherwise /system will be reformatted as ext4. This is easy but requires some additional work, I already proposed a sample solution used in ArchiDroid.

5. Similar with recovery, rom's kernel must support f2fs in order to mount partitions.
[Galaxy S III Original Android Development] DerTeufel1980:
Good explanation :)

Unfortunately I could not get f2fs work properly with secondrom. It seems to be caused by selinux, but I am not very familiar with this....

For now you'll be able to use f2fs on all partitions of primary rom (I am going to reinstall everything from scratch tomorrow to be sure it is working fine).

If you format data partition to f2fs (what you should do, to get the most out of it), you have to use sammy rom as primary and aosp as secondary, because of the selinux issue.

Also, system of secondary rom stays as ext4, because set_metadata fails for secondary f2fs system partition (I don't know why yet) on installing the rom.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] JustArchi:
Feel free to experiment with newest ArchiDroid 2.X if you want Devil. I want to be sure that my ROM is fully compatible with your f2fs :).
[Galaxy S III Original Android Development] DerTeufel1980:
I think I can't... Your rom isn't available for note2, is it?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] JustArchi:
True, only for i9300 :rolleyes:

But I ported ArchiDroid to Nexus 4 today in less than 10 minutes :D.
[Galaxy S III Original Android Development] cba1986:
My finger is itching :D

I will only use CM11 so dual boot is not a concern to me.
[Galaxy S III Original Android Development] tsubus:
great kernel, was looking to port perseus' features to work on 4.4.x, and I was glad someone else already did. Quick question: on perseus I was able to modify the files in /data/.perseus to change kernel configuration even at first boot. Is there such an option with this kernel? I've used deviltools but it only seems to be able to save and load from a specific file. Is there a location that is read by default by the kernel?

edit: nvm, I can just copy the saved configuration file into /etc/init.d to have the same effect. not an ideal solution, but it should do the job. thanks again for the great kernel!
[Galaxy S III Original Android Development] DerTeufel1980:
Great news, it seems like me was able to solve many second rom issues in recovery today :) there shouldn't be the need for modifying the zip anymore, and it also fixes the meta_data issues with f2fs

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] shaarky:
Just forgot to mention, on Temasek V36 + Devil kernel, I just spent 10 hours driving with navigation + recording video and no single crash, problem or overheating occurred, battery charged as well, excellent work [MENTION=2332422]temasek[/MENTION] and [MENTION=4196889]DerTeufel1980[/MENTION].

Looking forward for f2fs first tests, time to reformat everything :)
[Galaxy S III Original Android Development] nkirk:
Anandtech review of MOTO X which uses f2fs for user-data partition. posting just for reference:good:

http://www.anandtech.com/show/7235/moto-x-review/9

Benchmark numbers are very promising. Eagerly waiting for some good news from DerTeufel1980.

//nkirk
[Galaxy S III Original Android Development] JustArchi:
How did you manage to do so?

Ignoring format or mount options by updater-script is not the best way, imho roms should adapt and not recovery itself.
[Galaxy S III Original Android Development] DerTeufel1980:
System and data get mounted before the installing actually starts.

If it is an install to secondrom, the extracted update-binary gets replaced with a custom one. This binary accepts the format command, but uses rm -rf if the target is system.

It also ignores all mount and unmount commands which are pointing to data or system (because they are already mounted and there is no point in unmounting and remounting them from updater-script).

Finally, if the underlying Filesystem does not support set_metadata, it only applies the permissions, without returning an error

Primary rom isn't affected by this in any way

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] JustArchi:
Well I was guessing that you made something like that :).

But if for example I'd like to implement reformatting in my aroma, then your recovery will ignore my format and mount/umount options. This is not good I think. IMHO we shouldn't change core update-binary commands only to support f2fs and non-compatible roms. Rom developers should take care of that. By implementing such option you're limiting ArchiDroid :(.

I'm fine with integrating f2fs and support for non-compatible ROMs but not for that cost. If a ROM/Kernel developer wants to make use of f2fs, then he should implement/port it.
[Galaxy S III Original Android Development] DerTeufel1980:
As I said, it only affects installing to secondary rom. Till now I need to extract the updater script, modify it and place it back. Basically it's the same, but replacing the binary is just faster.

Gokhanmoral was doing it similar, by just removing the device nodes... There's just no other possibility if one wants to ensure secondary rom does not overwrite primary one :(

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] JustArchi:
And that's really sad.

You could take /system block path and then provide a fake path (/dev/block/mmcblk0p9), pointing to your secondary rom filesystem, this way update-binary would format and mount *fake* system partition. But that's just an idea. This way if rom is compatible with f2fs, it doesn't matter, but if ArchiDroid will like to force reformat to ext4, it will work, for primary and secondary.

Anyway, you implement it as you want. ArchiDroid is now fine with any implementation ;).
[Galaxy S III Original Android Development] DerTeufel1980:
You still could just run a script to format, if you really would need to force it.

Your idea is great. But I don't know how to get this working (if even possible to point a device node to file or mount point)

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] JustArchi:
In my pocket debian, I made such little hack:

https://github.com/JustArchi/ArchiD...NTAL/_archidroid/auto/system/bin/adlinux#L222

But that's for bind-mounting /system with /system in pocket debian, therefore all changes are shared.

You could mount your secondary rom file/partition to I don't know /dev/loop1 for example, then move /dev/block/mmcblk0p9 to mmcblk0p9.ORIG and then use ln -s /dev/loop1 /dev/block/mmcblk0p9, this way mmcblk0p9 would point to loop and in theory all operations should be executed on /dev/loop1 instead.

Just be careful with that, as we're directly touching blocks..
[Galaxy S III Original Android Development] DerTeufel1980:
Sounds good. Did you try symlinking loop to mmcblk device already?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] JustArchi:
Nope, didn't need so far but I'm doing similar thing in my frandom implementation, just with /dev/random.

https://github.com/JustArchi/ArchiD...auto/system/etc/init.d/99ArchiDroid_Init#L120

The only difference is that it's hard link instead of symbolic link, but it shouldn't be a problem.
[Galaxy S III Original Android Development] cba1986:
I smell a beta coming on?
[Galaxy S III Original Android Development] Ligrew:
Works well with AOSB 1.2.5 (Android 4.4.2). Thanks man! ;)
[Galaxy S III Original Android Development] maxq1:
just awesome to see devs cooking in broad daylight :good:, even if i understand only a miniscule % of what's being discussed! :o WOW
[Galaxy S III Original Android Development] cba1986:
[MENTION=4196889]DerTeufel1980[/MENTION] any update on the Project? :D
[Galaxy S III Original Android Development] DerTeufel1980:
I've released a test build for my device this morning... Anyway I am still having issues with selinux and f2fs,and I have to set it to disable on Samsung rom with f2fs :(

Aosp is working fine

Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
[Galaxy S III Original Android Development] cba1986:
I offer to beta testing in Temasek Rom. :D
[Galaxy S III Original Android Development] Gold_Diesel:
Could anyone tell me what the "up_nr_CPUs" value is on the devil Governor? I couldn't find anything about it using Google.
[Galaxy S III Original Android Development] DerTeufel1980:
I got selinux stuff fixed on Samsung and omnirom as well now. I guess I can update the other devices at weekends (please don't nail me to this... But I am optimistic)

Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
[Galaxy S III Original Android Development] cba1986:
Congrats!!!

I can't wait to try it out. :laugh:
[Galaxy S III Original Android Development] -MaD-:
I cant wait for the weekend to start :victory::fingers-crossed:
[Galaxy S III Original Android Development] BradleyR2010:
20) *up_nr_cpus - Calculated as minimum of (its current value and num of possible cpus), this tunable is used by the governor to indirectly make Hotplugging decisions, but may not be useful for a 2 core CPU.

UNIT: Integer 1/2

Taken from here: http://xdaforums.com/showpost.php?p=24233103&postcount=3
[Galaxy S III Original Android Development] Mostafa Wael:
Derteufel1980

Can you explain the f2fs in details what it does? what is the advantages of f2fs, and is it compatible on all ROMs? Also is it good for a gamer or it does not make sense?

Thank You for all of your hard work and good luck with your f2fs project..

:D:highfive::victory:
[Galaxy S III Original Android Development] drgreenth:
Google for f2fs and think. F2fs is flash friendly file system.

Lähetetty minun GT-I9300 laitteesta Tapatalkilla
[Galaxy S III Original Android Development] JustArchi:
Afaik it's only compatible with flashing as secondary rom, if you're flashing as primary one, ROM must support f2fs-friendly way of flashing (ArchiDroid does since last release)
[Galaxy S III Original Android Development] FadeFx:
May i request a feature for recovery dominik? I am actually not sure if it probably is already there, but id like to keep my secondrom updated using cyandelta, is it possible if i boot to recovery and a recovery-script is found, the recovery first asks where to flash this?

Thanx gerd

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] xeizo:
Since Tema has vanished, this is where the action is ;) Waiting (im)patiently for the fruit of The Devils hard work :cool:
[Galaxy S III Original Android Development] rascal0pl:
I have a small request.... in free time, could you look at foldermount app? Because it is not working on your kernel, and there is no good alternative for your dual boot kernel ;) Thanks!
[Galaxy S III Original Android Development] DerTeufel1980:
I'll take a look at it, but I don't know if this is possible. Anyway... I have to tell you (and others), that next recovery version won't be compatible for dualbooting with goodymax

anymore. You'll be able to select which rom to boot, but other dualboot options are going to be locked for devil kernel only.

Edit : do you know how cyan delta "talks" to the recovery? And what's the current behaviour? Does it just flash to primary rom?

What does this app do? Do you have a link?

Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
[Galaxy S III Original Android Development] xeizo:
I can only speak for myself, but for me that is totally ok since your kernel works extremely well for me :D

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

It's the old ln -s in the form of an app, great for newbies ...
[Galaxy S III Original Android Development] rascal0pl:
It mount folders (for example ext sd/android/obb -> internal/android/obb, or something else)

https://play.google.com/store/apps/details?id=com.devasque.fmount , @ stock CM11 kernel (temasek rom) there is no problem.
[Galaxy S III Original Android Development] DualJoe:
Just do it manually like this.
[Galaxy S III Original Android Development] xeizo:
Yes, that's exactly what it does. Thanks for reminding me. It's user friendly with an app though, I fully respect the request ....
[Galaxy S III Original Android Development] FadeFx:
Cyandelta does use the same recovery scripts like cwm manager and similar tools. Id have to look int how exactly it works and what the used syntax is.

So you change the way devil kernel dualboots, or you just lock out third party kernels?

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] tsubus:
question: is there anything in this kernel that changes the permissions of /system/xbin/su? After everytboot, the permissions get set to some screwed up permissions that include the sticky bit. I've tried flashing boeffla and with that kernel everything is fine. I love this kernel, though, so that's why I'm asking. Trying to find the root cause of this... (on latest omni nightly)
[Galaxy S III Original Android Development] BradleyR2010:
FolderMount works fine for me Im Stock 4.3 and the latest Devil Kernel

what problem do you have and what rom since its probably rom related
[Galaxy S III Original Android Development] DerTeufel1980:
I am going to use f2fs by default for secondary rom system, and it's not compatible with other kernels.

On the other hand, I am sick of reading in googy's thread things like: please make your own recovery, devil is not as good as your old. It's not googy's fault, but If people can't even respect the weeks of work I put into this, why should they benefit of it?

Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
[Galaxy S III Original Android Development] xeizo:
It's your kernel and your recovery, you can only decide for yourself what is the best solution. I will continue to use it anyway as it works just perfect for me :good:

But a general good advice is to always try to meet stupid people with a smile, it drains less energy and makes it easier to focus. But I know, sometimes it is too much :eek:
[Galaxy S III Original Android Development] zodiaxe66:
Please don't mind what ppl say, everyone have their favorite dev.

In the beginning I wasn't that keen on your cwm,because I had gotten used to GM cwm..but after a short while I got the hang of using yours and now i just won't use another cwm. Were so many ppl that respect and enjoy your work.:good::highfive:

My 2 bucks
[Galaxy S III Original Android Development] coolhof:
F**k what other people say.

I use you recovery, kernel and kernel manager.

Its the best combo for me.

Ceep up the good work.

Love it.
[Galaxy S III Original Android Development] tsubus:
[MENTION=4196889]DerTeufel1980[/MENTION] hey man, I'm wondering how your ramdisk is compressed. I've tried gz, lzo, lz4...can't seem to get the correct one to unpack. I'm trying to modify it to see if I can resolve some issues I'm having. Thanks for any help!
[Galaxy S III Original Android Development] DerTeufel1980:
Yeah, you are right. It's just annoying that people think the recovery is just a little piece to make dual boot easier.

In fact the recovery is much more work than the kernel. I could easily build a dual boot kernel based off yank or andip within one day. Getting the recovery to work properly is a work of months

Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
[Galaxy S III Original Android Development] coolhof:
No it doesn't.