yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] qu4nd:
So you don't have this under "specific"?
[Samsung Galaxy Nexus] payas0:
i flashed the latest one on my MIUIv5 (4.2.2). everything was great except it doesn't mount my Internal Storage !? Why is that ?
[Samsung Galaxy Nexus] infectedorganism:
Try deleting fstab.tuna from the zip prior to flashing.
[Samsung Galaxy Nexus] DR3W5K1:
Anyone running this on 4.4 how's your OST?

I'm thinking about changing kernels to see if it helps.

(I'm not getting anywhere near the battery life I got on 4.3)
[Samsung Galaxy Nexus] payas0:
just the fstab?
[Samsung Galaxy Nexus] infectedorganism:
Yes, just the fstab file. Just make a nandroid beforehand and give it a try.
[Samsung Galaxy Nexus] :
Pardon me for going off-topic but how did you get your action overflow button to look like that?
[Samsung Galaxy Nexus] qu4nd:
It's a theme for the new cm theme engine called 'fi'...
[Samsung Galaxy Nexus] :
I know, I already have the theme installed, but my action overflow icon doesn't look like yours :/
[Samsung Galaxy Nexus] qu4nd:
Are you taking about the trickster mod icon in the upper left corner? That's an icon pack called 'shapes and shades'...
[Samsung Galaxy Nexus] :
I'm talking about the menu icon on the top right.
[Samsung Galaxy Nexus] andreas__:
it's vanir ROM. they themed it like this by default
[Samsung Galaxy Nexus] qu4nd:
gotcha :)

This:
[Samsung Galaxy Nexus] rjshrjndrn:
Try stock PA it's just amazing.
[Samsung Galaxy Nexus] chinarobin:
it wont work.
[Samsung Galaxy Nexus] Ashtrix:
Thanks man, will test and report asap !!

EDIT : It works !!
[Samsung Galaxy Nexus] Charmacas:
[MENTION=4615478]boype[/MENTION] any news on your work? It seems that you actually have a lot to do in real life. Hope you're fine.

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] boype:
[MENTION=4562296]antonio8297[/MENTION] Can you post a link with the source of this? I'd like to cherry-pick the f2fs integration. It would save me a lot of trouble.

I'm good, but really busy. I'm not following the scene very much at the moment (except for icepeda's 3.4 development progress), but I'm very interested in implementing f2fs into this kernel.
[Samsung Galaxy Nexus] antonio8297:
i can give to you the commit,because i cloned your repo and added this commit.

the commit are four that i applied the first time and are this(implement it in the order that i say now):

https://github.com/arter97/f2fs-backport/commit/eb157565c01866eafbde4583ed2ef63b0e90e72f

https://github.com/arter97/f2fs-backport/commit/7981d6eafe15d7e88df6178705fd9c7302c24679

https://github.com/arter97/f2fs-backport/commit/d435e97829133a8cf6f852eda0fe0ae7dd787d6f

https://github.com/arter97/f2fs-backport/commit/24dc8487232c1b9d19ad58149570534dea5066bc

in arter git there are other new commit that need to be included:

https://github.com/arter97/f2fs-backport/commit/f28e275bd0978343c0b4a431d198853f0e6576a2

https://github.com/arter97/f2fs-backport/commit/ed30b0a9ec63af34935785f7c3c1103900e21c7f

this are only for implement it,for bugfix and other need to cherry-pick over 400 commits from bsmitty83 git.

in the defconfig you need to add this lines,into pseudo filesystems:

CONFIG_F2FS_FS=y

CONFIG_F2FS_STAT_FS=y

CONFIG_F2FS_FS_XATTR=y

CONFIG_F2FS_FS_POSIX_ACL=y

CONFIG_F2FS_FS_SECURITY=y

CONFIG_F2FS_CHECK_FS=y
[Samsung Galaxy Nexus] Ashtrix:
Except for the CAB (seems to be broken) everything works on the r50 f2fs build, no reboots or instablity :good: .
[Samsung Galaxy Nexus] tejaswi.rohit:
Is root working fine after flashing Fancy r50 F2FS ? The last time I tried I had no luck :( I was on Shiny ROM
[Samsung Galaxy Nexus] Ashtrix:
Yes it works:) .

I'm on Slim 4.4.4 build 6, the latest one plus slim has inbult Su, so it works w/o any issue. Though while i was converting from EXT4 to F2FS the root on carbon was not at all working i.e the SuperSU. Dunno if i had made any mistake ppl are running carbon F2FS now, tried to flash/normal method of SuperSU nothing was working at all, finally i tried my old frnd the slim and it had root under dev settings which was working great since then.:good:
[Samsung Galaxy Nexus] Charmacas:
This version does not work for me. I think because I do something wrong because it works for many others.

After flashing it passes the Google boot logo but then stays at the system boot animation.

I am on Paranoid 4.41 with newest DirtyV and flashed it just on top. It should not make any trouble because both kernel using the same ramdisk. Hmm...

[MENTION=4615478]boype[/MENTION] did you see this thread also? http://xdaforums.com/showthread.php?t=2801072

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] L-ViZ:
just wanted to say thx for this kernel :)

using slimkat atm on my maguro. tested it with stock kernel and fancy´s. it´s a different world ;)

even i got a nexus5 i still love my maguro, especially because of this kernel :)

thx [MENTION=4615478]boype[/MENTION] and the rest of the maguro community :)
[Samsung Galaxy Nexus] Ashtrix:
First my device running F2fs was on SmittyV+Slim though i had the fancy f2fs one flashed on top of that w/o any issues :good:.

Maybe that could be the PA ROM that's causing any issues..:confused:
[Samsung Galaxy Nexus] Nautilus74:
Could you convert Fancy pre51 to f2fs ?
[Samsung Galaxy Nexus] jean15paul:
For the kernel noobs. What is f2fs?
[Samsung Galaxy Nexus] cujo6801:
Actually it's the ROM side system management conversion

For the kernel just been altered to work with it

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Ashtrix:
Here ;)
[Samsung Galaxy Nexus] boype:
I have already picked those several hundred commits. I couldn't compile, but now I figured out what was wrong and it compiled. I'll be testing f2fs in the following days and will release r51 when everything is bug-free.

I'm quite excited f2fs has been ported to GNex!

Not yet, but thanks. I may check it out when I find the time

I appreciate your words :)

I have been noticing reduced battery-times for myself and figured it was time to order a new battery. I still love the maguro!
[Samsung Galaxy Nexus] boype:
Update: success! f2fs working. will most likely post r51 this weekend.
[Samsung Galaxy Nexus] agritux:
i hope you are OK with your own life.

thanks for update. i will wait r51

have a nice day

(if you will order a new phone, please tell me which phone it will be :) )
[Samsung Galaxy Nexus] _hz:
I have a problem with this kernel and known WiFi won't connect automatically until i disconnect or open WiFi settings...

I didn't have this issue with dirtyv or smittyv...

I'm on slimkat 6.2 f2fs.

Any ideas?
[Samsung Galaxy Nexus] STELKER:
Is there normal r50 (EXT4) version for 4.4.4 ? Or can I use normal version of r50?
[Samsung Galaxy Nexus] Nautilus74:
I can not wait! :fingers-crossed:
[Samsung Galaxy Nexus] boype:
r51 (f2fs+ext4 support)

Hi all,

...here we go:

r50 >> r51

add f2fs support (picked from bsmitty's repo; necessary ramdisk script by osm0sis)

ramdisk: add static ramdisk rather than anykernel2. this should help with f2fs support. ramdisk taken from 14-07-07 CM11 nightly. -> Android 4.3/4.2 compatibility is questionable at least.

drop hammerhead lowmemorykiller (caused many problems for many users)

OMAP4 NAND updates (flash memory performance improvements; squashed series of commits from bsmitty's repo)

readahead: make context readahead more conservative (may improve performance on flash memory drives)

ARM: 7805/1: mm: change max*pfn to include the physical offset of memory

Revert: dynamic suspend/resume vfs_cache_pressure & dirty intervals (Don't let suspend mode drain the block cache, also: disable periodic dirty writeback alltogether and let the dirty(_background) limits handle writeback.)

defconfig: vmalloc=192

defconfig: re-add CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y

Have fun, take care, and tell your friends :P
[Samsung Galaxy Nexus] aliesz:
Is it compatible with the ROMs are not f2fs?!
[Samsung Galaxy Nexus] thomstrack:
I can flash this version (r51) over r45 only clean cache/dalvik?!

Sent from my Galaxy Nexus 4.4.4 ShinyROM + FrancyKernel
[Samsung Galaxy Nexus] Ashtrix:
Flashed over the older r50 F2Fs and works perfectly :good:, though the CAB option still seems to be not working on the r51 rel.

Did any one got CAB working on F2Fs / Ext4 ROM ?

---------- Post added at 08:00 PM ---------- Previous post was at 07:57 PM ----------

Yes, as it says it works on both Ext4 and F2fs similar to DirtyV which has both filesystems support :good:
[Samsung Galaxy Nexus] boype:
I've been running cab ever since
[Samsung Galaxy Nexus] djtutis:
I use dirty v kernel. Can I flash it on top?
[Samsung Galaxy Nexus] Ashtrix:
Dunno why but my CAB setting on/off toggle doesn't change the display like it used to be, maybe i need to clean flash the whole as the transition from smitty to fancy could be a reason....:confused:.

Except this everything works fine from the RAB to the Undervolt/Overclocking thanks again for the update [MENTION=4615478]boype[/MENTION] :good: !

Edit : A big mistake, the CAB works fine !!
[Samsung Galaxy Nexus] massoudsh:
Is r51 compatible with the touchcontrol v 2.2.1?!
[Samsung Galaxy Nexus] RevengeFNF:
Does the phone really feels faster with F2FS or is just placebo?
[Samsung Galaxy Nexus] JuanG:
+1

I would like to see a video with galaxy nexus running f2fs rom.
[Samsung Galaxy Nexus] Ashtrix:
I'd say the F2Fs only improves the I/O performance of the whole system making it a bit snappier and smooth UX, The benches do say the SQlite perf & market installs are quite boosted though they are not the perfect scale to conclude anything as it mostly depends on user params, better try it out for yourself. I'm happy with mine, adding to this don't compare this to MotoX as the hardware is diff plus it comes stock on F2Fs ;)

P.S : Anyways here are my screens of the Androbench on EXT4 and F2FS.
[Samsung Galaxy Nexus] mangusZen:
Hey [MENTION=4615478]boype[/MENTION], any chance to have a hardcore version with mpokang ram speed commits?

With desclaimer and for kamikaze users :p
[Samsung Galaxy Nexus] motorazrv3:
Just flashed r51.

But I don't use touch control 2.2.1. Using 1.8.5 and cm11 module is working with r51.
[Samsung Galaxy Nexus] Nautilus74:
Latest TC works perfectly on this Fancy51 :)
[Samsung Galaxy Nexus] massoudsh:
which module must be selected & which version of TC?!!
[Samsung Galaxy Nexus] Ashtrix:
Yeah the Mpo's used to have speed but his src of RAM speed commits was never released and so his kernel died (Though It still works on EXT4) with that closed thread violating the XDA and GPL rules. Adding to this the latest r51's ram management is good around 60%+ but the older r50 uses only 50-58%, I've used to run Mpo back in june but the ram usage was quite high always like ~70%.

Btw Sorry, here are the snaps of the Fancy r51 F2Fs , jst taken :good::good: plus these are a bit even faster (the Seq rw), those were a bit old.
[Samsung Galaxy Nexus] Nautilus74:
"bponury stock mod"
[Samsung Galaxy Nexus] boype:
Try f2fs with fsync off and you will know the answer. (It feels great).

Keep in mind that f2fs will not magically pimp the hardware limitations. but an improvement in responsiveness is noticeable.

There are those in other threads who doubt f2fs is actually working (they think only the theoretical capability has been added to the kernel but it is in fact not being used). It is working. The f2fs recoveries floating around have the necessary tools for formatting included. The partitions are mounted as f2fs. Period. Also, there are those who say that the native android trim will not work any more. That does not matter, since f2fs has native garbage collecting. It keeps record of to-be-trimmed blocks and simply does it when the file system is idle.

Long story short: the benefits indicated by the tech specs and the real-usage feeling tell me that f2fs is definitely an improvement.
[Samsung Galaxy Nexus] RevengeFNF:
Thanks ;)

Just for curiosity, what f2fs rom are you using?
[Samsung Galaxy Nexus] motorazrv3:
As I wrote some post before, I am using touch control 1.8.5 in combination with cm11 module. Working perfect.
[Samsung Galaxy Nexus] mangusZen:
If I intended well mpok commits were released some time ago, but considered dangerous for the devices though noone reported problems of fried devices using mpok old kernels
[Samsung Galaxy Nexus] xmaciek82x:
Ok, noob question. I want to give tc a try. Where can I get 1.8.5 from? I have no problem paying for it but it's no longer available on play store.

Also, I waited 3 months for r51. Well worth it, thank you.
[Samsung Galaxy Nexus] manolone:
Hello I've flashed r51 on ShinyRom.. and I lost root access... therefore I went back to recovery, wiped dalvik and cache, flashed supersu 2.01 flashable zip, rebooted system, opened supersu app ang got message that supersu binaries are not installed, so no root access can be granted.

any idea how to get back root access after installing r51 on ShinyRom? thx for the replies

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] RW-1:
Seconded on latest shiny ROM, root lost. No other issues noted but can't really check due to loss.

We have notified bwg in case its something that needs to be changed there however I had no root loss on pre51.

Will patiently await outcome :)
[Samsung Galaxy Nexus] Ashtrix:
-deleted-
[Samsung Galaxy Nexus] aliesz:
There is the same problem here for my gnex. I tried the rule is described in shiny rom thread but root access is denied even I wiped the system and installed the rom again. I returned to fixed franco r396 kernel.
[Samsung Galaxy Nexus] thomstrack:
I have the same problem. I have other problem too. My screen never turn off. The power button works for power menu but NEVER turns screen off with latest fancy (r51).

I back to r45 and have no issues. :)

Sent from my Galaxy Nexus 4.4.4 ShinyROM + FrancyKernel
[Samsung Galaxy Nexus] Ashtrix:
How is that possible ??

It's been 16+ hrs up and rock stable here :confused:
[Samsung Galaxy Nexus] aliesz:
We don't say it is unstable. The root access denies after flashing this kernel. This problem probably is there for shiny rom
[Samsung Galaxy Nexus] RW-1:
I just tried flashing the SU.zip I originally used to root my GNex as well, that failed.

Considering that pre-r51 worked okay, I don't believe it to be the ROM, however I can only go by that nothing was posted to not flash mainstream r51 for non F2FS roms (I can't confirm that shiny uses F2FS at this time).

Could that be it?

Still playing around with it patiently, we have great dev's here and on the ROM end, it will get figured out in time.
[Samsung Galaxy Nexus] boype:
I'll take a look at that
[Samsung Galaxy Nexus] mangusZen:
Is synapse usable with last fancy? I got no uci support detected.. Is a problem on my side or ramdisk?
[Samsung Galaxy Nexus] aliesz:
For me the flashing of su.zip is not failed. It is flashed successfully but when my system is restarted the su app in my menu doesn't work and my root access is denied.
[Samsung Galaxy Nexus] antonio8297:
ramdisk doesn't have synapse support.
[Samsung Galaxy Nexus] motorazrv3:
Seems so. So far only shiny rom users have reported probs with loosing root.

I am on crdroid rom and never had probs with any fancy kernel version I used.
[Samsung Galaxy Nexus] Ashtrix:
This had already happened to me on while i was trying out F2Fs at first on carbon, As it doesn't come pre-rooted like PA or Slim and i was exhausted trying all things to get SU work but it fails over and over. Atlast i got slim flashed it was fine. This happens when the Su wont push to xbin under system partition due to permissions...

Back when i was flashing KK in the post beta days the same issue happened to me b4, SU binary wont get installed. Though there's an opt to push SU through ADB try that and if it still wont install try this method. I used to fix the KK SUbinary issue --> Use PhilZ CWM Advanced recovery it has a root option and clean option, try to clean then first use Busybox on rails to install the binaries and then from SU app re-root it. ATM i only know these alternatives...

Hope this helps :) , Thanks !!
[Samsung Galaxy Nexus] RW-1:
It's appreciated.

Just a roundup for you - I have no mods on shiny, just the latest version.

Dirty flashed from pre-r51. Root lost. Trickster reports not rooted, super SU cant detect or install binaries.

I haven't gone back to try re-flashing the pre-51, though I did try both a reflash of superSU, trying to reflash an SU zip fails.

Again, May I have made a mistake in flashing R51 on Shiny? I'm not sure if it is F2FS to begin with.
[Samsung Galaxy Nexus] crazyeats:
Shiny ROM is only f2fs if you used poo's tool to convert it. Don't believe its being released as an f2fs ROM at this time. I could be wrong.
[Samsung Galaxy Nexus] aliesz:
That is correct, shiny rom f2fs has not been released by its developer yet.
[Samsung Galaxy Nexus] pianistaPL:
R51 supports ext4&f2fs.
[Samsung Galaxy Nexus] RW-1:
I'm back on r50 for now, with root.

I dirty flashed the ROM again then r50 and SuperSU with no issues.

I'm sure boype will figure it out, no worries.
[Samsung Galaxy Nexus] furb3t:
R51 with official omnirom is ok also root. This kernel is awesome as usually and my smartphone likes it; it seems that with it all work flawless. Thanks boype ;)
[Samsung Galaxy Nexus] mick.li:
I can confirm hat you loose root on Shiny ROM with r51. Not even flashing the latest SuperSU helped.

Mick
[Samsung Galaxy Nexus] thoiloidainhan:
Are u sure u got the latest supersu? V 2.0.something is the latest one I believe. The reason I ask is because Google search has a strange passion for supersu v 0.98 and always return this when I google for supersu. I experienced this before and wrongly blamed ROM/kernel
[Samsung Galaxy Nexus] hp13:
i am using r51 without any issues. its the best release in my opinion. Its super smooth and no lag on notification bar. keep up the good work dev :good::laugh:
[Samsung Galaxy Nexus] chinarobin:
cannot find any sd file with r49-50 on my miui v5, any way to solve it? thanks!!
[Samsung Galaxy Nexus] mick.li:
Yes I'm sure, since I'm always using the following link:

http://download.chainfire.eu/supersu

Mick
[Samsung Galaxy Nexus] aliesz:
It seems that problem is commonly occurred for everyone has shiny ROM. I am using the 2.01 SuperSU with Franco r396 kernel on this ROM without any problem.
[Samsung Galaxy Nexus] renzs:
It happened to me too. On shiny rom and kernel with root. Flashed r51 and lost root. Tried flashing supersu.2.01.zip no change. Tried latest koush superuser and still no root.

How do I revert without needing to wipe. Since I lost root, can't use tibu to backup my app data.

Thanks in advance
[Samsung Galaxy Nexus] RW-1:
Reflash (dirty) shiny and super SU, boot up, then can go back to reflash r50, for example, or pre r51, on which I had no root issues.
[Samsung Galaxy Nexus] aliesz:
Just Turn the system off,Go to recovery mode manually by pressing volume up and down and power button simultaneously and flash your previous kernel or other one you already had no problem with it.
[Samsung Galaxy Nexus] RW-1:
Unfortunately that doesnt correct the issue with shiny users, I had tried that, going back to pre-r51 and r50,

To regain root I dirty flashed shiny again, and supersu, and booted, with root back then reflashed kernel of choice, with the exception being the current r51.

I'm back on r50 with root with all my stuff intact.
[Samsung Galaxy Nexus] renzs:
One more question before I start [emoji4] will I lose xposed fw after I reflash shiny? [emoji16]
[Samsung Galaxy Nexus] RW-1:
LIf xposed was something that you flashed to mod the rom itself, then yes, you would need to reflash that as well.

Any type of data for it though, should remain, as it is a dirty flash of the ROM, so once you place it back on, it should imo run ok, but since I don't use that, I cant be 100%.
[Samsung Galaxy Nexus] poo706:
[MENTION=4615478]boype[/MENTION], would you mind if I start including the boot.img from your r51 with my F2FS converter tool (http://xdaforums.com/galaxy-nexus/development/tool-galaxy-nexus-ext4-to-f2fs-rom-t2794702). I had been including SmittyV 6/28, but it seems to be causing problems for people where as I've heard nothing but successes with your kernel.

And looking at your flashable, it's just the boot.img and nothing else fancy (no pun intended) going on, right?

[poo]
[Samsung Galaxy Nexus] boype:
I have just taken a quick look to find the problem, but could not find it immediately. Can you (and all with shiny) give me more input? Like: Can you run other custom kernels without losing root? If yes, which kernel(s) are these?

go ahead :)
[Samsung Galaxy Nexus] RW-1:
Boype, was on r49, r50 and pre-51 without issues.

I do a dalvik and cache wipe, flash r51 via twrp (latest) and no errors, but on boot complete root is gone.

If I go back to recovery and flash r49 50 or pre r51 then reboot, root was still gone.

SuperSU will say binaries not installed and it can't do so.

Trickster won't even open.

I reflashed shiny (latest) to replace with included kernel, flash SuperSU and boot and found I had it back.

I then reflashed r50 and I'm still good.

So I could say the included kernel works, but haven't tried any others than yours at this time. I'm willing to try with a recommendation and will check the thread in the am.
[Samsung Galaxy Nexus] manolone:
Boype i'm on ShinyRom latest dirtyV kernel and Ido not lose root

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] mick.li:
I'm running Shiny and DirtyV-UR { 6/28 } without any root-problems.

Mick
[Samsung Galaxy Nexus] thecoolkid:
Boype, I bet it's the new ramdisk that's causing problems since CM is now very different than stock AOSP that Shiny is based on. There are no troubles with your previous fancy kernel versions (since they had good ramdisk or was anykernel universal builds) and so there are no with other kernels. That's also the reason why dirty flashing r48-pre51 won't give you root access back, and flashing r45 will. Could you maybe make an anykernel version just to confirm that? :)
[Samsung Galaxy Nexus] RW-1:
I believe tck may have hit it, but you guys know way more than I on the kernel end. :)
[Samsung Galaxy Nexus] boype:
That's what I was thinking too. However, the superuser init is the same in r51 as in r45:

r51

r45

Also, r51 init.superuser.rc is the same as in dirtyv.

So that's why I'm wondering what the problem is
[Samsung Galaxy Nexus] _hz:
i'm now on r51 f2fs and still have this issue.

had this issue since Android 4.2, but when bsmitty released his kernels it was gone. now with fancy it's back, but fancy works better for me, and i would like to get rid of the wifi issue...:fingers-crossed:

help help help ;) or how can i help?
[Samsung Galaxy Nexus] boype:
I wouldn't know why this occurs, but wifi in general is very buggy on the gnex. i suppose bsmitty updated the wifi driver, which i didn't, since there were people complaining about the lack of WEP encryption compatibility. However, WEP is old (and insecure) as hell anyway, so I might as well update. Whether this fixes the problem or not - I don't know!
[Samsung Galaxy Nexus] _hz:
if you have a test-build let me know... :) :good:
[Samsung Galaxy Nexus] motorazrv3:
Yup a test build could be a base to test. Let's hope boype has got some free time for us to compile a build.
[Samsung Galaxy Nexus] saprer:
im testing this kernel with PA now these days and will give you feedback about bugs.
[Samsung Galaxy Nexus] hp13:
i tried it on PA 4.42 and no issues. supersu working fine!
[Samsung Galaxy Nexus] RW-1:
Just of note, I've had no issues with wifi reconnects (not using any WEP based networks anyways) with shiny rom on the GNex with any of your kernels since r48 ...
[Samsung Galaxy Nexus] saprer:
yes i can confirm everything working :good:
[Samsung Galaxy Nexus] aliesz:
Is there any relation between kernel version and recovery version? Can any mismatch between them affect on SU root losing?!
[Samsung Galaxy Nexus] boype:
pre52_1

Hi,

here's pre52_1. It has the updated wifi drivers we were talking about earlier. Download available from the OP.

Best regards
[Samsung Galaxy Nexus] Nautilus74:
f2fs compatibility?
[Samsung Galaxy Nexus] playenball:
Working fine for me on CM-remix using f2fs.