yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] Teura:
I seem to have a bit of problems with the new kernel / recovery combo. Using Omnirom, nightly from 29th.

First steps on what I did:

Both 2.4.7 kernel and latest recovery to external SD.

Reboot recovery (Still PhilZ 6.07.9 at this point).

Flash the new kernel.

Reboot system to verify everything working.

Reboot recovery

Flash Devil recovery

Reboot recovery

Nandroid to external

Format /system, /cache and /data, /sdcard and secondrom to f2fs (at this stage, recovery rebooted itself on the last option)

Format /data, /sdcard and secondrom again just in case (no reboot this time)

Restore backup -> reboot

And I never got past Omnirom logo. After trying a few times, I decided to reformat everything back to Ext4 and restore -> still stuck at Omni logo. Reflash Philz, format everything again just to be sure and restore -> working normally.

I'll try to get some logcats from the boot process now that I know that it's not the backup that is causing hangs.

E: Nope, no logcats. The boot never advances far enough for ADB to recognize it.
[Galaxy S III Original Android Development] ariadnejro:
Everything seems to be working fine with the new filesystem. AndroBench app shows the new amazing file speeds. However, my favourite mod CrossBreeder is refusing to install, it fails while trying to set permissions. Any ideas?
[Galaxy S III Original Android Development] DerTeufel1980:
After restore, flash my kernel again. No other can boot up

What rom?

Gesendet von meinem Note II mit Tapatalk 2
[Galaxy S III Original Android Development] vegaman:
After the post above I'm thinking there's a compatibility issue with OmniROM.

I tried again with a new backup and everything but still got stuck at the boot animation. This time the recovery didn't have problems mounting data and it looks like everything restored properly, it just wouldn't boot.

Is anyone using an AOSP ROM with f2fs without problems?
[Galaxy S III Original Android Development] ariadnejro:
I'm on latest Temasek rom. But the issue about CrossBreeder isn't rom related, the installer fails in recovery with a message about set_perm.
[Galaxy S III Original Android Development] Teura:
I know that. And from the steps I posted, I flashed 2.4.7 before doing nandroid and it still didn't boot after restoring it. Though I think I tried reflashing it once after restore, but I'll try again just to make sure it's not that.

E: Nope, not working.
[Galaxy S III Original Android Development] drgreenth:
It was super easy to upgrade temasek latest (probably whatever rom) with f2fs still on at /system.

Before proceed take FULL nandroid if you are not wearing a folio hat.

What I did

1. Just dirty flash latest temasek or whatever nightly

2. FLASH devil f2fs kernel - IMPORTANT!

3. Reboot and make sure everything works (now /system is formatted to ext4)

4. Reboot to recovery

5. Make custom backup only for /system

6. Format /system as f2fs

7. Restore normally your nandroid of /system custom backup (i did not use custom restore just normal because it only contains /system so everything else gets skipped)

8. Reboot and enjoy your f2fs /system

This took like 5 minutes extra time.

I would still love ArchiDroids way to support it out of the box.

Lähetetty minun GT-I9300 laitteesta Tapatalkilla
[Galaxy S III Original Android Development] _Beni_:
Same here, i tried Kitkat: omni, cm11, slimkat, nothing worked.

Im now using Slimbean, cm10 also works.

EDIT:

I successfully formatted Cache and System to f2fs, but data:

- formated to f2fs (without crash)

- restored data: bootloop

- formated back to ext4

- restore data: error

- format data

-> reboot -> recovery doesn't boot only the touch keys then reboot. endlessloop

Lets turn on Odin :/
[Galaxy S III Original Android Development] xeizo:
A small bug: PA Gapps can't be installed to second rom, it says it can't detect a 4.4.* rom. Banks Gapps works just fine.(could as well be a PA bug that has surfaced)

Also reboot to second rom from first rom doesn't work, but that can be some misconfiguration on my end as the new recovery is a tad more powerful than the old ie lots of more options :good:

Haven't got around to testing the filesystem part as of yet, but that will come :)
[Galaxy S III Original Android Development] Mostafa Wael:
So now i ended with a dead phone with stock recovery and no ROM is on device, what should i do now? Reflash Stock ROM with ODIN?

will reflashing the stock ROM wit ODIN help me get my phone back?

I am living a nightmare here :( :( :crying:
[Galaxy S III Original Android Development] sktjdgns1189:
Dude, leaving it on commits and not to users is not cool at all.

f2fs, slub, adb root has been all done by arter97 and users should be aware of that.

Not the githubbers.
[Galaxy S III Original Android Development] _Beni_:
no flash the latest twrp http://techerrata.com/browse/twrp2/i9300 with odin.

then flash with twrp devil recovery and format all partitions and restore/install your rom.

i did it tomorrow 6 times :D
[Galaxy S III Original Android Development] DerTeufel1980:
This is a test release, and my credits are in the op. I'll add arter97 there, when the kernel gets official.

Btw it's a giving and taking between us, and I don't know why you think you have to say anything about it.

I am sure he had written me an email if he would see a problem.

Last but not least, I took his initial f2fs patches and committed all others myself from Linux 3.13

I took his (faux123 really patched it) slub which is Linux 3.3 and pushed it to 3.8

Gesendet von meinem Note II mit Tapatalk 2
[Galaxy S III Original Android Development] mhb92:
okay i tried this kernel for first time with cm11 temasek's rom and i have to say u have done a very good work...!!

and compare to all other kernels gives best performance !! thanks !! ! :)
[Galaxy S III Original Android Development] Mostafa Wael:
what about omnirom support?

if you are stuck and can't decide which one to support, i suggest to make a poll "omnirom vs CM11"
[Galaxy S III Original Android Development] lovleshgarg:
CM11 Temasek V6 - Primary ROM

Samsung 4.3 - Secondary ROM

Result - WORKING :)

THANKS A LOT FOR THIS WONDERFUL KERNEL..
[Galaxy S III Original Android Development] DerTeufel1980:
Could you upload the omnirom kernel for me please. Then I can diff the initramfs

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] coolhof:
Here is the omnirom kernel.

But I seen this by the omnirom treat.

Don't no if it's important for your recovery?

http://www.mediafire.com/?heq6nci4lji37yl
[Galaxy S III Original Android Development] Mostafa Wael:
what you mean by uploading the omnirom kernel?? how to extract it from the rom? i am a newbie in these things :o :(.... i mean i never done these things before. i am a normal root user, a flash-holic one. i am one of your big fans. You can tell me what you want exactly and i will help you as soon as possible. Or else, i hope somebody could help you with bringing the omnirom support here. it is definitely your choice.:D

thanks...

sorry for being a noob :( :crying:

Mostafa Wael, a devilish fan........
[Galaxy S III Original Android Development] mrjoy:
Have anyone confirmed dualboot supporting ??
[Galaxy S III Original Android Development] Mostafa Wael:
great to see somebody posted the omnirom kernel.. thanks man

looking for omnirom support Derteufel1980
[Galaxy S III Original Android Development] DerTeufel1980:
Yes, for 4.4 and 4.3 sammy roms. No one reported about aosp 4.3, but I guess it is working as well

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] serkaon:
I'm looking for omnirom support too dear Derteufel1980. Thankss ??

GT-I9300 cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy S III Original Android Development] mrjoy:
Thanx for confirm. Could u plz tell the procedure to install zip file to second rom without spaces??
[Galaxy S III Original Android Development] DerTeufel1980:
if there are spaces in the filename, like: superrom 4.3.zip, just remove the space, to be superrom4.3.zip

same goes for the install folder. things like: download of roms

isn't a valid folder name :) it should be: download_of_roms
[Galaxy S III Original Android Development] davi_ssilva:
And how about adding boeffla sound engine? IMHO it sounds better than the voodoo engine and it has the boeffla sound control app, which anyone can get from play store (and it contains those presets that some guys are missing)
[Galaxy S III Original Android Development] NOSTALGIA:
sound control pls.. pls pls pls...
[Galaxy S III Original Android Development] Zocker Tko:
Dualboot between omnirom and cm11rom would be nice, maybe it will be possible?

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Original Android Development] DerTeufel1980:
Sound control already changed to latest boeffla for the next build.

Omnirom doesn't work as of now.

Btw: i did compare the initramfs of Cm11 and omni, and I didn't see anything obvious which prevents omni from booting.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] DerTeufel1980:
New kernel uploaded.

Deviltools also updated

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] armude:
Can anyone try or confirm dualboot with sammy 4.3 and aokp 4.3? Please. Thanks

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Original Android Development] jimbo77:
I just tested the latest version and I'm really pleased and surprised with its performance (Being the first time I use your work) ... I'm using Temasek version 7 as primary and Sammy 4.3 as secondary and the only downside is that when using Boeffla sound app, Advanced settings, Dac Direct and Hardware equalizer option reset themselves each time I scroll through the app.

Is anyone else having this issue, is it Kernel Related or should we bring this to Andip attention?

Thanks in advance
[Galaxy S III Original Android Development] Prowler:
Dualboot work great with latest CM10.2 + Temasek v7!

View attachment 2409517View attachment 2409519

The only dislike thing for me is the app icon, so i change that

View attachment 2409565

A lot of thanks Dominik!
[Galaxy S III Original Android Development] Mostafa Wael:
Will try after a couple of hours, i am already downloading a Stock ROM from Sammobile... hope it helps...
[Galaxy S III Original Android Development] drgreenth:
Just flash philz recovery with odin and then push devil recovery with adb or external sd and then go on? No need for stock. If you have your daily rom as zip somewhere. If not push it as well. Next time make full nandroid before proceeding..

Lähetetty minun GT-I9300 laitteesta Tapatalkilla
[Galaxy S III Original Android Development] arter97:
I'm sorry but I do see there's bit of a problem.

Your kernel's title and first post has been updated for f2fs and all the people, including JustArchi are excited about those stuffs. It's that major.

And I helped you with all the cares including creating a special patch that's applicable to Devil right away and sending and receiving about 100 emails.

This may sound weird but I was kind enough to let yours to be the first XDA-posted kernel to sport f2fs even though I wanted the honor so bad(My kernel is a bit weak to post it on xda for now I guess).

And it's a bit sad and disappointing to see I'm nowhere mentioned on the entire thread even if it's a test-drive.

Sorry if I'm the only one here being so cocky..

Absolutely no offense in anyways..
[Galaxy S III Original Android Development] JustArchi:
All my ArchiDroid components are open source, you can grab them at https://github.com/JustArchi/ArchiDroid. The point is that it's very ArchiDroid-specific, so it won't work right out of box without porting.

https://github.com/JustArchi/ArchiD...gle/android/aroma/exec/archidroid_check_fs.sh

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

+ Hook https://github.com/JustArchi/ArchiD...META-INF/com/google/android/aroma-config#L329

If somebody wants to, feel free to make standalone aroma app from these commits. As for now I'm busy finishing this implementation, it's not yet finished.
[Galaxy S III Original Android Development] JustArchi:
My rom supports it as well ;). Above you can see interactive reformatting, not actual f2fs support. F2FS support is limited only to mount -t auto and delete_recursive("/system") instead of format command. It's easy.
[Galaxy S III Original Android Development] arter97:
See

http://xdaforums.com/showthread.php?t=2450497

Maybe not the best, but my rom supports f2fs installation if recovery supports it.

Damn auto login.. duplicate post sorry :(

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

Formatting would be more clean wouldn't it?

mkfs.f2fs is also developing and it discards(fstrim) upon formatting
[Galaxy S III Original Android Development] DerTeufel1980:
I am sorry that you feel not considered enough by mentioning you in my github.

I am sure justarchi had already seen my comment there.

Anyway, I'll update the post with you mentioned explicitly there.

Why do you think your kernel is too weak? I just thought you only publish it for your device in a Korean forum.

Anyway, after updating block to Linux 3.4 last time, I almost finished porting mm to 3.4 today. Maybe you really want to take a look at updating filesystem drivers. We would nearly have a 3.4 kernel then.

Gesendet von meinem Note II mit Tapatalk 2
[Galaxy S III Original Android Development] JustArchi:
In reformatting you need to specify filesystem. I wanted to make my rom compatible both with ext4 and f2fs. Of course I can detect if mkfs.f2fs exists and then decide based on that, but what if somebody has f2fs support but wants to use ext4?

That's why I'm implementing repartition wizard ;). If user wants to use other filesystem, he can reformat with just one button.

In general, when I'm looking at my ArchiDroid right now... Holy ****, this thing is complex :eek:
[Galaxy S III Original Android Development] arter97:
Thanks :D

Some devices are superbly stable, others are freezing, and causing random reboots....

And music stuttering is the biggest obstacle for my kernel.. :(

(Also never tested on GT-I9300 ha!)

I'm a bit conservative approach on these Linux backports... I've seen to much wrong things gone with those crazy backporting...

Still a very interesting, good things when done properly :)

I'm not seeing your git updated for slub 3.8 and these new 3.4 stuffs yet :P

---------- Post added at 11:47 PM ---------- Previous post was at 11:46 PM ----------

I encourage you to take a look at my rom.

It detects on

mount | grep mmcblk0p9

Shouldn't it be enough? :)
[Galaxy S III Original Android Development] JustArchi:
https://github.com/JustArchi/ArchiD...ndroid/aroma/exec/archidroid_check_fs.sh#L138

;)
[Galaxy S III Original Android Development] arter97:
:confused::silly::confused::silly::confused::silly::confused::silly::confused::silly:

---------- Post added at 11:52 PM ---------- Previous post was at 11:50 PM ----------

Experimental as ****

That's nice :laugh:
[Galaxy S III Original Android Development] DerTeufel1980:
I can give you access to my bitbucket account when I get home. Then you can see it.

I didn't backport the drivers. I have committed each commit by hand from kernel.org and fixed compile errors by also picking the missing parts (for example 8 commits to cgroup just to fix one mm commit)

Gesendet von meinem Note II mit Tapatalk 2
[Galaxy S III Original Android Development] arter97:
Those 'missing parts' commits are so scary :(
[Galaxy S III Original Android Development] GR0S:
Freshly installed omnirom can't boot on F2FS
[Galaxy S III Original Android Development] DerTeufel1980:
In the end, there shouldn't be much of a difference to stock 3.4 kernel.... But let's see if I get mm finished today

Gesendet von meinem Note II mit Tapatalk 2
[Galaxy S III Original Android Development] arter97:
:)

Btw, does your newly ported 3.4's block means we can have a proper 'bfq for 3.4'?

My newly ported bfq v7 seems to be causing some freezes.
[Galaxy S III Original Android Development] cba1986:
That backport is for the SGS3 or for another device?
[Galaxy S III Original Android Development] DerTeufel1980:
I didn't try it, but I had to apply some cfq commits to the "old" bfq to make it compile again.

Most probably 3.4 bfq should be fine. Besides the row commits, my block is the same as 3.4

Pushed the block branch to bitbucket and added you. Don't have time for more right now. My daughter got ill and my girlfriend is on the way to the doctor with her. I am babysitting my son now till he's going to bed

Gesendet von meinem Note II mit Tapatalk 2
[Galaxy S III Original Android Development] shaarky:
Quick question,data and sdcard doesn't offer f2fs type format in recovery,is it fine?
[Galaxy S III Original Android Development] JustArchi:
ArchiDroid 2.X based on OmniROM works perfectly fine with /system formatted as f2fs, didn't try other partitions yet.
[Galaxy S III Original Android Development] _Beni_:
Did you flash the latest recovery?
[Galaxy S III Original Android Development] shaarky:
Yes...naturally latest flashed.

I'm slightly lost, /data doesn't offer f2fs, but "format /data, /sdcard and secondrom" offers f2fs ... anyway, after that this is my current layout.

mount | grep f2
/dev/block/mmcblk0p12 on /.secondrom type f2fs (rw,seclabel,relatime,background_gc=on,user_xattr,active_logs=6)
/dev/block/mmcblk0p12 on /data/media type f2fs (rw,seclabel,relatime,background_gc=on,user_xattr,active_logs=6)
/dev/block/mmcblk0p8 on /cache type f2fs (rw,seclabel,relatime,background_gc=on,user_xattr,active_logs=6)
/dev/block/mmcblk0p12 on /data type f2fs (rw,seclabel,relatime,background_gc=on,user_xattr,active_logs=6)
/dev/block/mmcblk0p9 on /system type f2fs (rw,seclabel,nodev,noatime,nodiratime,background_gc=on,user_xattr,active_logs=6)

sdcard1 (external sdcard) mounted as vfat, but I don't see anywhere sdcard (internal...), is it due to mountpoints ?

mount | grep sdca
/dev/block/vold/179:17 on /storage/sdcard1 type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
[Galaxy S III Original Android Development] _Beni_:
lol mine is shorter :eek:

mount | grep f2
/dev/block/mmcblk0p9 /system f2fs ....
/dev/block/mmcblk0p12 /data f2fs .....
/dev/block/mmcblk0p8 /cache f2fs ......

i read that /data/media is the internal card ;)
[Galaxy S III Original Android Development] ariadnejro:
About CrossBreeder mod and the new f2fs kernel and recovery:

-CrossBreeder installer fails on the new recovery if /system is formatted in fsf2, it seems to be permissions related.

-As a workaround, I could install CrossBreeder on TWRP converting /system previously to ext4. But if I convert again /system to f2fs the phone boots normally but the adblock features don't work.

Long story short, CrossBreeder can't be installed nor run properly if /system is formatted in fsf2. It runs ok with the help of TWRP if /system is formatted in ext4.
[Galaxy S III Original Android Development] Erik1805:
Hi

I am in Temasek v42. Does these steps work?

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[Galaxy S III Original Android Development] drgreenth:
Those steps are for situation if you have already done f2fs conversion and want to upgrade your current temasek to newer version.

If you want to start using f2fs with temasek this is what I did:

- Rebooted to recovery

- Flashed new kernel and new recovery

- Rebooted recovery itself

- Made FULL nandroid backup to EXTERNAL sdcard without repartitioning (I assume this is used when want to revert partitions back)

- Rebooted back to Android

- Made backup of all important data to computer from internal sd card (including nandroid backups)

- Rebooted to recovery

- Formatted EVERYTHING (except sdcard1) /data /system and /cache as f2fs

- Restored nandroid backup from external sdcard

- Reflashed kernel (just to be sure - e eventho it was already included in nandroid)

- Booted back to Android and checked with "mount | grep f2fs" in terminal that every partition is as wished

- Restored data from computer

- Rebooted back to recovery

- Made new FULL nandroid backup

- Rebooted to Android

- Enjoyed lightning speed of f2fs

Lähetetty minun GT-I9300 laitteesta Tapatalkilla
[Galaxy S III Original Android Development] Teura:
I can now confirm this.

I downloaded Omnirom 0203 nightly just to test it. Booted recovery, made nandroid of my current setup and then wiped partitions (the default way, still ext4). Then I installed Omnirom and booted into it to verify. All was good. Back to recovery and then I installed this kernel (2.4.7 which is the f2fs version). Again reboot, everything was still working and phone status showed correct kernel was in. Then again back to recovery to make nandroid of the test system to external SD. After that I formatted /system, /data and /cache to f2fs and restored my testing nandroid. And it won't boot past the omnirom logo.

Guess I could also test with not every partition formatted and see where it fails.
[Galaxy S III Original Android Development] DerTeufel1980:
Are you able to connect to your device with adb while bootlooping?

Gesendet von meinem Note II mit Tapatalk 2
[Galaxy S III Original Android Development] Teura:
You'll have to wait a while, while trying to troubleshoot it I managed to do as _Beni_ did in http://xdaforums.com/showpost.php?p=50004909&postcount=1175, which is recovery bootloop while I had no working ROM installed. Only the touch keys are visible and then it reboots. It happened when I choose to format /data /sdcard and secondrom to ext4. Recovery rebooted and now it's looping. So it's Odin time.

E: Weird, flashing PhilZ from Odin also causes a recovery bootloop, but even before touch keys are visible. TWRP works ok. Does the format corrupt something both PhilZ and Devil recovery use outside of recovery partition?
[Galaxy S III Original Android Development] francescozanghetta:
thanks for your great work!!!

This is my feedback regarding the full system partition with f2fs.

I use the same backup first with ext4 and later with f2fs and these are the results. As you can see with the same backup I get full system partition wheb I use f2fs.

Do you know why?
[Galaxy S III Original Android Development] _Beni_:
Both are based on cwm and i think cwm try to mount partitions at start up. i often had "error while mouting /data" when i have started devils recovery.
[Galaxy S III Original Android Development] JustArchi:
You're right, automatically mounted partitions are specified in /etc/fstab, along with filesystem which is being used.
[Galaxy S III Original Android Development] Teura:
Here we go. It's not exactly a loop, as it just stays on omnirom logo doing nothing, which the logcat also supports as it seems to be stuck on creating the mount directories. So I cut the log from random point where it seemed to repeat the process.
[Galaxy S III Original Android Development] DerTeufel1980:
This is your primary rom? Try this in adb shell please:

su

touch /data/.selinux_disable

Then reboot

Gesendet von meinem Note II mit Tapatalk 2
[Galaxy S III Original Android Development] Teura:
Yes, this is primary (and only) rom on the phone. I haven't even set up filesystem for 2nd rom.

Just in case to verify no mistakes from my part

shell@i9300:/ $ su
su
shell@i9300:/ # touch /data/.selinux_disable
touch /data/.selinux_disable
255|shell@i9300:/ # exit
exit
255|shell@i9300:/ $ exit
exit

And the new logcat after reboot, though to me it seems nothing has changed.
[Galaxy S III Original Android Development] DerTeufel1980:
Please get me the boot.log file. Again using adb

su

cat /boot.txt

Also, the output of "mount" would be interesting

Gesendet von meinem Note II mit Tapatalk 2