yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] aditya.jazzmaster:
Sorry for asking same question in different topic. Cause I'm afraid if my phone get some serious trouble, I need it for my work & this is my only one phone. LOL

Does f2fs is safe & stable enough for daily use?

Thanks
[Samsung Galaxy Nexus] PlusOne3k:
Aloha,

i've got following problem, i flashed TWRP F2FS and flashed CARBON-KK-NIGHTLY-20140610-0436-maguro-f2fs.zip.

All is working properly, but i got some apps like Adaway or Busybox Installer which are not working.

System is R/O

Data R/O

Any suggestion how i can change permissions? chmod 777?

Best regards, Alex.
[Samsung Galaxy Nexus] osm0sis:
Actually I just double checked and official TWRP for the GN doesn't have to mkfs.f2fs busybox applet for formatting either, so don't use it. I guess use Smitty's TWRP to format then use his PhilZ?

And yeah, it's fine, it's the default on the Moto X.
[Samsung Galaxy Nexus] d0ge01:
theres a anykernel version of last release ?

the new one cant boot in encrypted device ( i think its new ramdisk hybrid )
[Samsung Galaxy Nexus] Oehr:
i dont get the new update: shouldn't it remain compatible with ext4 partitions? So is it the kernels or the roms fault when resurrection remix and the new dirty 14-6-9 dont go well together?

P.S. you should maybe switch to a new naming scheme for the releases: mm-dd-yy doesnt make sense:

I recommend the logical and sortable yy-mm-dd date structure :D

youll love it once you ring in 2015 :laugh:
[Samsung Galaxy Nexus] Nephilim:
Running the new 6/9 SmittyV on a nice fresh test build of LiquidSmooth 4.4.3 with Hover merged. This rom is amazing!!!! Kernel is running epic as usual!
[Samsung Galaxy Nexus] poo706:
I've seen this pyramid demonstrating why America's date format is illogical. But what's the logic in assigning "day" to the top of the pyramid and "month" to the middle of the pyramid? Seems arbitrary to me. If anything, "month" should be at the top because there are only 12 months, "day" should be in the middle because there are at most 31 days in a month, a "year" should be on the bottom because there are an infinite amount of years.

[poo]
[Samsung Galaxy Nexus] KiD3991:
I'm using LiquidSmooth 4.4.3 as well but the F2FS version. Running the kernel that came with it and pegasusq as per your settings. Is there any need to modify the settings more if i wanted to run on 1.6/1.65 Ghz?
[Samsung Galaxy Nexus] Nephilim:
Honestly, I don't see any point in going above 1.5ghz, I tried out 1.6ghz before and saw very minimal improvement on performance, but I did see a much larger chunk of battery loss. However, if you do choose to ramp up your cpu frequency that high, just make sure you are at 65 or 70 for your temperature.

As for LiquidSmooth 4.4.3, just wait, I'm using the freshest of the fresh right now, built this morning with Hover fulling merged and working flawlessly. ;)
[Samsung Galaxy Nexus] bsmitty83:
what's not to "get" ? , ext clearly works or everyone would be telling me so .

I've never used resurrection ROM , is it cm based ? if so I blame the ROM [emoji39]

as for the dates . I live in America , so I use our standards , sorry . if it bothers you that much you can rename it yourself .

Hack The Tuna
[Samsung Galaxy Nexus] Nephilim:
I seem to remember just posting two posts back that I am running a test build of Liquidsmooth on your latest 6/9 SmittyV build, that would mean I am running your kernel on ext4 lol. Sometimes reading helps. ;)

Sent from my Android 4.4.3 Galaxy Nexus
[Samsung Galaxy Nexus] Oehr:
yep, resurrection rom is CM based and includes features PA, Omni and a few plus some exclusive ones.

your kernel worked flawlessly with RR till the inclusion of F2FS, so i figured that there is something new the kernel requires to work with any rom?

ill try all three kernel types now (only tried Dirty-UR so far). doubt thatll change anything though, meaning ill be stuck at 5-3-14 (14-5-3), which is the latest non-F2FS kernel if im correct :)

P.S. i figured youre from the US ^^
[Samsung Galaxy Nexus] bsmitty83:
its because it dosent work for ROM "x" , that means it doesn't include ext support .......? smh , then give me a PS on why my kernel names should be changed ? [emoji19]

of all the problems and feedback I could get with a kernel I never thought a name would be one lol

Hack The Tuna
[Samsung Galaxy Nexus] Nephilim:
Dude, seriously, I just said for a second time, I am running SmittyV UR 6/9 on ext4 LiquidSmooth 4.4.3 built this morning and it works fine. The kernel is NOT the problem.

Sent from my Android 4.4.3 Galaxy Nexus
[Samsung Galaxy Nexus] Oehr:
I just checked all three types and none got me beyond the Google splash screen... damn.

Is it maybe also related with still being on 4.4.2? I'm also using encryption (if that info of any relevance).

[MENTION=2853378]Nephilim[/MENTION],

I know it works for you and many more users without any issues. It doesn't for me though, so if someone has an idea on why exactly and on how to solve it, im up for it. i also posted the same info in RRs thread.

Its just strange that it stopped working from one version to another... it just shouldnt have happened like that...

P.S. I see your dates as something like version numbers, so if the numbers bigger, it should newer. right now it is still true, but once we go into 2015, it wont be. also, for simple sorting and basic logic (size of day, month and year), ordering them like yy-mm-dd is far superior to any other format.
[Samsung Galaxy Nexus] Nephilim:
Dude, please just accept it's the rom you are using that is the problem with the kernel, the kernel is 4.4.2 based but works on 4.4.3 roms as well so the Android Build has no relevance. As for your Date query, just please deal with it, you are the first person ever to have issue with how the dates of the kernel releases look. No one cares, we all follow this thread and we all see Smitty post a new comment when another kernel update is added to the OP, we are not grade-schoolers, we can decipher what the date is. I don't mean to be rude but it just appears that you are completely ignoring our replies and saying the same thing over and over.
[Samsung Galaxy Nexus] bsmitty83:
I think someone also said that it doesn't work on an encrypted phone . ive never used that feature so idk . chances are that is the issue . you can try extracting the zimage and fast booting it , if it works it probaby is ramdisk issues , if not its probably kernel related

Hack The Tuna
[Samsung Galaxy Nexus] Oehr:
calm down Nephilim, youll explode otherwise.

the date thing was a suggestion. why go nuts about it like that?

I also edited my previous post before you finished quoting me so give it another read.

Neither am I ignoring replies. they just didnt get me any further nor did I get anywhere on the RR support front yet either. I guess ill just wait for the next update of it or something and hope for the best.

the strangest thing is, that im not even getting a bootloop animation, but am stuck before that. havent had that before on my nexus...
[Samsung Galaxy Nexus] osm0sis:
I'm not sure why encryption would be affected, all that's happening is the fstab gets moved in a little later. Maybe it reads the fstab before that to look for the encryptable partition? I'll look into it.

I do agree, actually, that from a versioning standpoint yy.mm.dd would make more sense. 14.6.9; where the year is like the major revision, etc. etc. But hey, it's Smitty's kernel, he can do what he wants, and it's not a big deal to anyone who isn't OCD. ;)
[Samsung Galaxy Nexus] bsmitty83:
it sounds like encryption isn't letting the system mount maybe ? and I never disagreed that your dating suggestion isn't the most logical , I just use what my country uses lol , its the same with metrics , I love it and it's so much simpler than the crazy American way .

[MENTION=4544860]osm0sis[/MENTION] , half the time I dont even KNOW what date it is lol........ That's what a newborn and a 3 year old kid will do to you

Hack The Tuna
[Samsung Galaxy Nexus] Oehr:
mhhh damn encryption biting me in the ass. I can't give up on encryption though. price too high :(

any way i can help fix or debug it?

EDIT: apparently, RR stopped being developed (dev no longer interested or something)... guess ill migrate to something else in due time.
[Samsung Galaxy Nexus] Nephilim:
I suggest you migrate to LiquidSmooth rom, new build should be posted tonite if all goes well.
[Samsung Galaxy Nexus] Fatsodonkey:
Anyone got cm11 m7 f2fs rom?

E: I can`t use anything other than cm because of the perfect finnish language. :D I get annoyed if there is english in the os. :D
[Samsung Galaxy Nexus] KiD3991:
I'll try it out. Do test it out and see if there could be any room for more improvements. 1.2Ghz was too slow for me. (sez teh guy dat caem frum Nexus 5). 1.5Ghz was much more acceptable. pegasusq. zen.
[Samsung Galaxy Nexus] wisefreakz:
VAI BRASIL!!!!

HACK THE TUNA
[Samsung Galaxy Nexus] seriousia:
Day is at the top bcz its the smallest among all, then comes month n in the last year.
[Samsung Galaxy Nexus] jcooler:
[MENTION=2853378]Nephilim[/MENTION] or [MENTION=4015637]rkpeterson[/MENTION],

Is there going to be a F2FS version on LS released as well? I'm running 6/9 4.4.3 F2FS version right now, and it runs flawlessly. Haven't even rebooted since I flashed it a a few days ago.

But I'm really interested in the Hover feature. Looks like something I would really like.

Now that I've converted to F2FS, I don't see me going back again. Runs too well. :laugh:
[Samsung Galaxy Nexus] Nephilim:
I figure Bob will build an f2fs when he has time since the ext4 version is running great as well as he has his gnex setup for f2fs. ;)

Sent from my Android 4.4.3 Galaxy Nexus
[Samsung Galaxy Nexus] rkpeterson:
Hoping to build the f2fs versions of Liquid tonight. So they may be posted in the morning.
[Samsung Galaxy Nexus] poo706:
Oooooo, darn your logic that's more logical than my logic.

[poo]
[Samsung Galaxy Nexus] namtombout:
May I have a hit of whatever you're smoking [emoji18]

I BELIEVE

I BELIEVE THAT
[Samsung Galaxy Nexus] bsmitty83:
I should have a new philz recovery up tomorrow , all 3 tuna variants , latest source

I tested the toro version , adb push/pull and sideload both work , just have to build toro+ , and make some flashable zips .

I will start working on twrp next , I'll let the ROM dudes build the ROMs .

Also as for the reboot issues people are having with the last kernels , I have zero issues , reboot works fine , also reboot to recovery works as well . it must be something else like a script or something messing with the boot cycle .idk , I can't reproduce the problem and some users have had that issue on older versions of my kernel so I just don't know what's causing it

Hack The Tuna
[Samsung Galaxy Nexus] Marco618:
I just flash DirtyV-SR, what changes will that bring to my gnex maguro running PA 4.4 RC1?
[Samsung Galaxy Nexus] oman0123:
I think it's gonna get up in the morning and make you pancakes.

That and hopefully it will bring a smoother, lag free Gnex for you :)

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] cujo6801:
<br />

<br />

I think it's gonna get up in the morning and make you pancakes. <br />

<br />

That and hopefully it will bring a smoother, lag free Gnex for you :) <br />

<br />

<br />

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2[/QUOTE]

Mine makes me Belgian waffles

Sent from the "DOG" pound
[Samsung Galaxy Nexus] DR3W5K1:
Mine makes me Belgian waffles

Sent from the "DOG" pound[/QUOTE]

The dirty v always makes my pee burn the next morning
[Samsung Galaxy Nexus] cujo6801:
I forgot how good these icons look..

Sent from the "DOG" pound
[Samsung Galaxy Nexus] DR3W5K1:
Those are boss.

Free?
[Samsung Galaxy Nexus] AbhishekS:
Haven't had time to keep a track of this thread. Is there any progress on the Xposed Wake Gestures compatibility?
[Samsung Galaxy Nexus] paarthdesai:
nope, nothing till date

Sent from my Ğäłãxý Ńęxűš
[Samsung Galaxy Nexus] cujo6801:
Yeppers....

Free in the Play Store

Sent from the "DOG" pound

---------- Post added at 09:59 PM ---------- Previous post was at 09:57 PM ----------

I made sure the name of the icons was in the pic so people can find it

Sent from the "DOG" pound
[Samsung Galaxy Nexus] shatteringlass:
Guys, sorry in advance for the mild OT, but I was investigating a strange omap issue and possibly find a solution, but I need devs' help, so I thought to gain visibility by posting on this very active, sublime kernel by [MENTION=4608636]bsmitty83[/MENTION] .

LINK to thread: http://xdaforums.com/galaxy-nexus/general/random-reboots-omapi2c-omapi2c-4-rrdy-t2666919

In the last post, I linked to a commit who nobody had merged yet, which possibly solves the issue for those who were suffering from it.

LFTL: https://gitorious.org/linux-omap4-d...mmit/eb72a26e12ff8a86db4588af5f269a350bb33975

Hope devs can look into it. Thanks.
[Samsung Galaxy Nexus] bsmitty83:
does this happen on any kernel you are using ? , ive never seen anything in my dmesg that's i2c related , especially that message you said gets repeated over and over

Hack The Tuna
[Samsung Galaxy Nexus] shatteringlass:
Any kernel, any ROM, just not every day. Lately, it's happening every night, while I'm sleeping and phone is charging and idling, in airplane mode. During the daytime, all is normal. Well, mostly.
[Samsung Galaxy Nexus] bsmitty83:
OK , I can try to make a kernel for you to test out with that commit you found to see if that will help , but if its on any kernel , any ROM , it really sounds like a hardware issue .

Hack The Tuna
[Samsung Galaxy Nexus] Marco618:
Lol, it did make it faster but I'm still waiting on them pancakes xD
[Samsung Galaxy Nexus] shatteringlass:
I am afraid it is indeed hardware related. Also, from what I can understand, the issue could be something completely unrelated, and the dmesg output could be just the effect. Something could be wrong with memory, a faulty interrupt occurs, i2c panics, prints that message and at last watchdog reboots the hardware. I just don't know. AFAIK, that commit applies to android-omap4-3_4, so your merging to out 3.0.101 would be a backport, am I right? Can you still do this? Thanks, whatever the ending to this story.
[Samsung Galaxy Nexus] bsmitty83:
I should be able to , ive back ported a lot from 3.4 [emoji106]

Hack The Tuna
[Samsung Galaxy Nexus] AutomaticFailure27:
You should still be able to use TC if you still have it installed. I have been able to redownload the modules ever since the app was removed. Unless, you know, it doesn't work with Dirty anymore (wouldn't know)
[Samsung Galaxy Nexus] AbhishekS:
But eventually we gotta move ahead of TC as its deprecated, so better to dump it now and look for alternatives.
[Samsung Galaxy Nexus] poo706:
Heh heh, it's funny because it's true.

[poo]
[Samsung Galaxy Nexus] boonz19:
Hi, I would like to seek help converting my phone to f2fs. After flashing the TWRP-TUNA-F2FSALL.img recovery in bootloader, i went on to convert the file system to f2fs. If i immediately adb push files into /sdcard/, the transfer would seem to complete but it would disappear upon reboot. I also tried flashing the official twrp 2.7.1.0 after conversion to f2fs to adb push my rom files into the sdcard. However, these files also disappear after a reboot. I suspect that there is something wrong with my read-write permissions after conversion to f2fs but i'm not sure how to remedy this... my only option was to convert back to ext4 and load up my good old omnimetal rom (i need the phone to work as it is my main phone). Would appreciate if anyone knows what actually happened. Thank you.
[Samsung Galaxy Nexus] dbh369:
I had a similar problem. Instead of rebooting, just flash right away once rom gapps, and kernel are visible on sd card.

Ps, I got omni metal to work by changing out the update script as explained earlier however isn't completely f2fs since i can not merge other changes....

sent from my GNex rockin omnimetal with f2fs on dirtyV
[Samsung Galaxy Nexus] boonz19:
Thanks for the quick reply! If this is the case, does it affect the ability to flash over with other roms in the future?
[Samsung Galaxy Nexus] dbh369:
Didn't cause me that problem. originally had Commotio on it as that was the only ROM, then made my mods and flashed my Omnimetal-F2FS normally.
[Samsung Galaxy Nexus] boonz19:
Just want to clarify, did you manage to push the files on TWRP-TUNA-F2FSALL.img or twrp-2.7.1.0? Now i can't seem to detect ADB while in TWRP-TUNA-F2FSALL.img...
[Samsung Galaxy Nexus] dbh369:
I'm still on Smitty's F2FS version of TWRP. I think a page or 2 back, the 2.7.1.0 version doesn't completely support F2FS yet. And not sure if it has anything else that might be useful; certainly Smitty's version has done all I need.:good:
[Samsung Galaxy Nexus] bsmitty83:
I updated the op with a new philz recovery , to use f2fs just enable f2fs/ext switch under mounts , then when you choose which partition you want to format , you will then have the choice of either filesystems . enjoy and hope they work [emoji6]

Hack The Tuna
[Samsung Galaxy Nexus] boonz19:
Yes, I just saw this when dbh369 mentioned about your recovery..!! Testing it out now, and yeah, adb push works :)

Edit: Finally booted into the rom! I think it was the rom's problem though, cuz it didn't work again until I changed the rom. Thanks smitty! :)
[Samsung Galaxy Nexus] aditya.jazzmaster:
[MENTION=4608636]bsmitty83[/MENTION]

it's just my opinion. It would be better if you can write down yours step by step complete instruction to migrate to f2fs.

and also you can add some link instruction from another person (just another way to rome if there is some cases).

BTW your latest kernel works very well on my device, my phone not getting hot. if it's getting hot it will be cooling faster than before. thanks

CMIIW
[Samsung Galaxy Nexus] alfiemenace:
New version okay with vanir 4.4.3 nightlife? Ext4?
[Samsung Galaxy Nexus] Rushead:
Check the 2nd post... And then thank [MENTION=4278473]Hetalk[/MENTION]

Sent from a flashead cracker.
[Samsung Galaxy Nexus] aditya.jazzmaster:
yes I know it and I have read it.

i mean that bsmitty83 can add his own way instruction to migrate to f2fs.

So that would be better i think.

It just my opinion.

Btw why i can't choose install file from sdcard using latest bsmitty philz touch?

And also there is alot log that show can't mount bla bla bla...

CMIW
[Samsung Galaxy Nexus] bsmitty83:
not sure why its still not able to read /data in ext , everything other partition mounts and reads OK , so I guess for now stick to the twrp recovery , until it gets straightened out .

Hack The Tuna
[Samsung Galaxy Nexus] Oehr:
For all those running into issues with TWRP and encrypted phones:

TWRP 2.7.0.0 is unable to handle encrypted phones, so if you plan on migrating to F2FS, you need to use 2.7.1.0 or 2.6.3.0 to back things up first and then convert through the patched TWRP with F2FS (which is based on 2.7.0.0).
[Samsung Galaxy Nexus] qu4nd:
Hell yeah! Running awesome!
[Samsung Galaxy Nexus] Ziyan:
I think it would be wise to remove the "format /factory" option, which is very dangerous :confused:
[Samsung Galaxy Nexus] creeve4:
Or TWRP 2.7.1.0 built with support for F2FS *wink* *wink* [MENTION=4608636]bsmitty83[/MENTION]
[Samsung Galaxy Nexus] Charmacas:
Maybe these steps I wrote in the paranoid thread helps people to migrate.

Not on F2FS:

1. Backup apps via Titanium Backup

2. Adb pull every file from the SD which is important to you to a backup location

3. Flash new recovery from [MENTION=4608636]bsmitty83[/MENTION] from bootloader

4. Format everything with that recovery to F2FS

5. Flash PhilZ recovery from bootloader

6. Adb push installation files and every file from your backup location back to the SD card

7. Flash smittys recovery back from bootloader

8. Install ROM, gapps and unified DirtyV kernel

9. Boot into ROM and make the initial setup

10. Let Google restore your applications

11. Install Titanium Backup

12. Restore the data from your fresh installed apps with Titanium backup

On F2FS:

1. Boot into recovery

2. Flash modified ROM, your favorite gapps and a compatible F2FS kernel

3. Restart

That's how I do it. ☺

Sent from my Galaxy Nexus with Tapatalk

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] demlv:
Most people don't use ADB or flash recoveries from bootloader very often, let alone flash multiple recoveries or reformat partitions in a single session......so I think that what aditya.jazzmaster probably wanted was detailed instructions for each step you listed, including these ones......

2. Adb pull every file from the SD which is important to you to a backup location

3. Flash new recovery from [MENTION=4608636]bsmitty83[/MENTION] from bootloader

4. Format everything with that recovery to F2FS

5. Flash PhilZ recovery from bootloader

6. Adb push installation files and every file from your backup location back to the SD card

7. Flash smittys recovery back from bootloader

;)
[Samsung Galaxy Nexus] aditya.jazzmaster:
Wow nice guide.

thanks for this guide.

about adb & flash recovery from bootloader I very often used that method. wkwkwkwkwk

[MENTION=4608636]bsmitty83[/MENTION] please add this one to OP.

thanks all :)
[Samsung Galaxy Nexus] bsmitty83:
If I can get a twrp recovery to build how I want it , it will be OK on ext and f2fs . still not sure why cwm won't recognize ext sdcard partition

[MENTION=2838735]aosp[/MENTION] ?

Hack The Tuna
[Samsung Galaxy Nexus] osm0sis:
We don't have sdcard-ext (external sdcard). It's a stupid CWM info/warning message and can be safely ignored. :)

That su permissions warning when rebooting from CWM (since SELinux started changing them) is stupid too. The permissions don't even matter now that su is a daemon. The daemon, when run, sets the correct permissions itself on each boot.
[Samsung Galaxy Nexus] bsmitty83:
really ? are you messing with me ? lol

I didn't even think about that , I didn't try to actually push anything in ext to the sdcard so if anyone wants to confirm that I'd be grateful . not that I don't absolutely take your work for it , I just can't believe that . I haven't used cwm since ICS

Edit , you know I was talking about sdcard in ext4 right ? , not sd-ext

I probably should have wrote that more clearly

Hack The Tuna
[Samsung Galaxy Nexus] aditya.jazzmaster:
I have ask the dev to help us build it 2 days ago, and also I have sent PM too.

still no response yet. hehehehe

btw which is recomended after migrate to f2fs?

download/restore all apps through playstore then only restore data from titanium backup

or restore all apps with data from titanium backup?

[emoji16]
[Samsung Galaxy Nexus] bsmitty83:
I can get twrp to build , I'm just trying to build it with vanir source . twrp is normally built with omni , so if I can't get around these strict-alaising problems I'll have to use omni source .

Hack The Tuna
[Samsung Galaxy Nexus] dbh369:
[MENTION=2853378]Nephilim[/MENTION], does that LS build need a change to use f2fs?
[Samsung Galaxy Nexus] aeroxr1:
Does The miracast app included in vanir functions with dirty kernel ? :)

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] osm0sis:
Haha ohhh sh*t. Sorry. I thought you meant that sd-ext thing CWM's been displaying since forever. :p

So pushing to sdcard is broken when it's ext4? Weird. I think the sdcard is vold or something?
[Samsung Galaxy Nexus] midnightdevil66:
Oh by the way the LA Kings won the Stanley Cup! I'm glad they did (Devils fan).

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Unb0rn:
What's the point of formatting every partition in f2fs? F2FS is only efficient when many read/write operations occur(am I wrong?), which is only possible on /data and /data/media. One more thing, Philz recovery from the first post won't work with ext4 or it's my fault? Thanks.
[Samsung Galaxy Nexus] bsmitty83:
so the cache doesn't get many read/write operations ? , don't you like it smoother and faster ? , system doesn't get wrote to that often , but its faster when it does

I'm also aware that philz currently won't read ext4 , use the twrp recovery that is floating around , I'll a add it to the op soon

Hack The Tuna