yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] daniil1410:
F2FS on every possible partition.
[Samsung Galaxy Nexus] Gingerbread1611:
RC with SmittyV and F2FS.

Revision file says "Maguro 8th Sample (0x09)"
[Samsung Galaxy Nexus] daniil1410:
Does it boot with the normal kernel?
[Samsung Galaxy Nexus] Gingerbread1611:
No, only with custom ones.
[Samsung Galaxy Nexus] SoftWord:
This Rom have Bluetooth LE enabled?

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] CYoung234:
I just had a lockup with the 7-05 FML, running Franco kernel. First time for this in about a month. Log attached.
[Samsung Galaxy Nexus] dirtyreturn:
If this is answerable, could someone help me out? I've been enjoying OmniRom for a little over a week and I recently found out that there is a multi window function. Does the nexus have that included? If it does, where is it?
[Samsung Galaxy Nexus] SoftWord:
any news about this?

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] sergialess:
Hey, have a nice vacation and forget technology for a while ;)

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] qtoo941:
Don't worry about FML, bro. Family always takes first place! Have a nice vacantion with a lot of memories :)
[Samsung Galaxy Nexus] AbhishekS:
Have a great time man! Cheers. ?
[Samsung Galaxy Nexus] cabalio83:
Have fun!!! Current FML stable is good enough
[Samsung Galaxy Nexus] morfances:
You can add this?

Congratulations for your work xD
[Samsung Galaxy Nexus] AbhishekS:
Downloading this now. Seems exciting! :D
[Samsung Galaxy Nexus] AbhishekS:
This is smooth, super smooth. I don't know whether the smoothness is due to the ROM or the included kernel, but whatever it is, is heavenly.

Just one minor request, in the included kernel can you please add the purple tint fix commit?
[Samsung Galaxy Nexus] GamaX320:
May I know this ROM included theme manager?
[Samsung Galaxy Nexus] Hetalk:
Nope!
[Samsung Galaxy Nexus] AbhishekS:
And I hope Theme Manager is never included. It's an overhyped thing which takes a huge toll on the resources.
[Samsung Galaxy Nexus] Gingerbread1611:
The rom feels pretty smooth, but if the the screen stays on for a while (ca. 30 seconds) i get a weird graphic glitch which turns my screen green. (I've never seen that before). I can't take a screenshot becauser as soon as the phone detects an input (Touch or hardware keys) it will turn back to the normal colors.

Beside that weird glitch its a great ROM, keep it up. PS: Please also add German to the settings. :)
[Samsung Galaxy Nexus] MWisBest:
It'll be in the next build! I've been eyeballing it for a while but I usually let OmniROM decide when things like that are ready rather than jump the gun on it.

I highly doubt the speed is from the kernel, me and kernels go together like... dogs and catnip. I don't really understand what it is so I just pee on it and walk away hoping I did the right thing. :laugh:

I will check on the purple tint thing. The kernel does have color control though, so you might be able to improve it enough to hold ya over til the next build.

The theme engine is something that has been on OmniROM's Gerrit Code Review for quite a while now. I generally wait for OmniROM to merge in changes and after looking over the theme engine myself I won't be making any exceptions for it. It seems like it still has some Cyanogen Inc. (I'm not even going to call it CyanogenMod anymore...) junk tied into it which is a major problem to me. When FML was based on Cyanogen Inc. it was absolute hell for me. Lots of my builds ended up requiring me to fix something Cyanogen Inc. broke, which looking back on it just completely stifled me innovating anymore. Pretty much only once with OmniROM have I had something they merged require fixing from myself, and that was simply due to FML's optimizations requiring fixes to what would otherwise be perfectly valid code under normal AOSP build flags... wanna know where that thing they merged came from?: Cyanogen Inc. :p

Could you by chance see if you can get a logcat of that happening? If you need help with doing that I can do so.

Thank you! Don't worry bout the translations to Settings, all of them will be fixed for the next build!
[Samsung Galaxy Nexus] Gingerbread1611:
Sure, i will post it in a few minutes.

/Edit: Here you go:

Pastebin Link (Scroll all the way down, i made a wordwrap where it begins.)

The glitch always happens shortly before the screen goes off.

Thanks for looking into it.
[Samsung Galaxy Nexus] AbhishekS:
Haha! I loved that dogs and catnip example. :lol:

And yes, I saw that color control is there. But purple tint fix is another thing. A lot of tuna devices have a screen glitch (bug) that makes the screen looks purple-ish on low brightness. Mpokang kernel was the first one to have it, and now almost every kernel (Dirty_V, ASKP, CM Kernel, etc.) have it.

So I'll be glad if you can implement it. :)
[Samsung Galaxy Nexus] jesan9:
Can you add lockscreen notification to the next release plz? :3
[Samsung Galaxy Nexus] pianistaPL:
+1 :)
[Samsung Galaxy Nexus] osm0sis:
It's your color settings. This happens when you have a borderline green value. Normal brightness it's okay, but when it dims before screen-off it triggers. I made a post about the relationship of the different settings in the GN color thread way back, I'll see if I can dig it up for you.
[Samsung Galaxy Nexus] Gingerbread1611:
Ok thank you. Still weird because im using this color settings since a long time. (Im using Nephilms settings: http://xdaforums.com/galaxy-nexus/general/nephilims-custom-kernel-settings-thread-t2401653 )
[Samsung Galaxy Nexus] osm0sis:
If you are using the included FML kernel, and it doesn't happen on others it's probably because it doesn't have the purple tint fix, so everything's slightly different.

Bring the green gamma offset up from Neph's -3. Since it's borderline for you, -2 might work. If not then -1 or 0 definitely should.
[Samsung Galaxy Nexus] Gingerbread1611:
Haven't thinked about that, you're probably right. Thanks.
[Samsung Galaxy Nexus] osm0sis:
Thought I'd written something a bit more definitive, but here's what I've found:
[Samsung Galaxy Nexus] mieru:
Really awesome rom, thank you! It runs flawlessy also with dirtyv. Can you add german translation in settings? This would be great.
[Samsung Galaxy Nexus] MWisBest:
I've been doing a lot of work for the upcoming build! What led to the huge speed-ups in the most recent build was simply me reviewing all the stuff I did over the past 9 months, so I decided to stick with that again and I found quite a few things to improve upon!! Once I get everything all tested out and am sure it's working properly I'll get a new build uploaded, most important being that I fixed the translations in Settings. I also included the purple tint fix by the way.

For those with issues regarding the screen color configuration, here's some info on what might be behind your issues other than the purple tint fix thing:

1. In "arch/arm/mach-omap2/board-tuna-display.c" in the kernel source tree, some kernels change the default color multiplier values. This is (from what I can tell), independent of the "Color Multiplier" settings that you can modify yourself with the color control. The FML kernel (currently) does not modify these from the stock values. Therefore, color settings that you use on other kernels are not directly transferable to the FML kernel. I will see what tweaks can be made here to find at least a middle-ground between the common custom values and the stock values.

2. The contrast is not modified from the stock kernel either. Most kernels seem to have this set to a negative value of some kind, FML just leaves it at 0. This is something that I believe is just adjusted by the user and does not stack like the color multiplier settings. Just thought it was worth pointing this out to make sure you aren't missing it.

Tomorrow I'll be going out of town to this introduction thingy for the college I'm planning on attending, so a new build probably won't be out until late tomorrow night. :fingers-crossed:
[Samsung Galaxy Nexus] AbhishekS:
You are the man! :D :angel: :good:
[Samsung Galaxy Nexus] motorazrv3:
Enjoy your vacation with your father and forget about technology a while.

---------- Post added at 08:39 AM ---------- Previous post was at 08:34 AM ----------

Omni rom should work on our nexus. My wife had a omni rom installed on her nexus and multi window was working.

Try it out.
[Samsung Galaxy Nexus] osm0sis:
ui_print("Formatting /system");
run_program("/sbin/rm", "-rf", "/system");

Kinda cheating. :p :laugh:

Would a true format be preferable in your opinion? I came up with a decent method for that as well:

ifelse(run_program("/sbin/sh", "-c", "test `blkid /dev/block/platform/omap/omap_hsmmc.0/by-name/system | cut -d\\\" -f4` == 'ext4'") == 0,
( format("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.0/by-name/system", "0", "/system");
ui_print("Mounting ext4 System...");
),
( run_program("/sbin/mkfs.f2fs", "/dev/block/platform/omap/omap_hsmmc.0/by-name/system");
ui_print("Mounting f2fs System...");
)
);
run_program("/sbin/busybox", "mount", "/system");

Once the busybox included with all the recoveries is v1.22.1+ then you could export the partition type and run the correct command based on that as well (to support exFAT, ext3, etc.). :D
[Samsung Galaxy Nexus] MWisBest:
Hey guys! I got back to civilization Thursday night but didn't get home until Saturday night. Been catching up on some stuff since then.

My first day in the Boundary Waters I came closer to dying than I ever have in my entire life: we capsized! :eek: We hadn't even been on the water for more than a few hours yet! If we weren't wearing life jackets, we probably wouldn't have survived. My dad lost all his fishing tackle and one of the three fishing poles we brought, as well as various other things like his camera and some flashlights and whatnot. All totaled up it was probably $400 worth of stuff, at least. :( Long story short, we persevered and stayed out there 4 of the 5 days we had originally planned on. I don't think many people would've kept going and not just gotten the hell out of there, not sure if it's because we're tough, stubborn, crazy, or a combination of the three! :laugh: I'm planning on typing out the whole story and submitting it to some websites for the Boundary Waters and stuff like that.

In regards to FML:

I'm going to try and get this kernel issue fixed ASAP. I really don't want to scrap using the updated kernel altogether, so I'm going to try updating it in chunks and having you guys test various kernel builds until we find where it breaks. I'll just upload the boot images instead of a full ROM zip so it's just like, 5MB to download instead of 170MB...

Actually I prefer it not being an actual format. From what I understand, doing a format of /system in recovery does what's called a "secure erase", which, if I'm understanding correctly, puts more wear-and-tear on the eMMC. For flashaholics (or devs who are constantly flashing new ROM builds ;)) that's not a great idea to do then.
[Samsung Galaxy Nexus] osm0sis:
Welcome back! Glad you survived! :eek: :cowboy:

I just wanted to point this your way again since I think you were already away when I mentioned you in it (and baldwin sounds like he's winding things down):

http://xdaforums.com/galaxy-nexus/d...y-rom-ota-stock-android-t2642375/post54613527

NFC HCE for NXP could be within reach finally. :good:

Also wanted to let you know that I pushed Unified v2 f2fs/ext4 ramdisk support which should allow DirtyV to work on FML again like we were talking about. It swaps out the fstab entries on-the-fly for the appropriate format so should be the best solution for custom kernels not wanting to give up their ramdisks. I'm running data+cache f2fs, system ext4 right now, myself. :)
[Samsung Galaxy Nexus] Qafix:
Everytime I open busybox app or try to install new binaries my phone would be forced reboot. Is that intended?

Edit: Nvm, after how many times trying it somehow managed to not reboot when installing. I'll report if it happens again.
[Samsung Galaxy Nexus] MWisBest:
For those who haven't been looking at the toro FML thread, my phone is dead... again...

Motherboard died just like it did in early July, so there's some other part in there that seems to have a short or something and is attempting to draw too much current. I examined both motherboards closely and found that the TWL6030 chip had some very strange bubbles on it, presumably from excess heat, and to my knowledge the TWL6030 does most of the power management, so yeah...

I could just get another motherboard, however that'd probably fry just like the last ones did so I'm better off just getting either a new Galaxy Nexus or enough new parts so I replace everything that could be causing this issue. A new (to me...) Galaxy Nexus would run me $80, however:

I've determined that $60 in parts will be what I need to get things going again. Somebody was nice enough to send a $30 donation already, and I could probably come up with $10 to $20 myself. If a couple people are willing to donate $5 I'd be good to go, if needed I could repay them whenever my finances get in better shape. :(

Here's a list of all the different parts in the phone and an approximate price on them if I need them or an explanation as to why I wouldn't need them.

- Motherboard: needed, ~$15

- Rear Camera: not needed, an extra was included with the motherboard I got a month ago.

- Front Camera and Sensors: not needed, an extra was included with the motherboard I got a month ago.

- Screen (includes the glass, AMOLED screen, and touch digitizer): needed, ~$40 for a near-flawless screen or ~$30 for a screen with a bit of wear and tear

- Earpiece Speaker: not needed, an extra was included with the motherboard I got a month ago.

- Vibrator+Speakerphone+HeadphoneJack housing thingamajig: needed, ~$10

- MicroUSB+Microphone: needed, ~$5

- SIM Tray+eMMC: not needed, I have a 16GB eMMC and a 32GB eMMC as well, the 16 was in the original motherboard when that fried and the 32 was in the new one when that fried so this part can't be the problem.

- Rear Housing: not needed, however it'd be nice to have which is about ~$8. There's some contacts on there, three of which are for the pogo/dock pins, however these are all in pristine condition and just to be certain I'll be cleaning mine with isopropyl alcohol (92%, I've used this on computer processors to clean off thermal paste, it's fantastic stuff for electronics cleaning!).

- Battery: not needed, I have the official stock battery and the official extended battery and the stock battery was in when the motherboard fried this time and the extended one was in when the original motherboard fried so that can't be the issue.

- Power and Volume Buttons: not needed, how the hell could these fry anything, it's not like they really draw power!

^That's a list of (nearly?) every part by the way.
[Samsung Galaxy Nexus] qtoo941:
Congratz, dude. I hope third time will be lucky. So i wish u luck and success! And also - please don't forget for my personal asking to add vibration feedback in quicktiles. Please ;d
[Samsung Galaxy Nexus] MWisBest:
Thanks!

I haven't forgotten about the vibration feedback in quick tiles, and I have looked into it extensively. I noticed that long-pressing on tiles had vibration feedback so I tried to look into how that's done to see if I could sort of apply the same thing to regular presses but that didn't turn out so I'm trying to find another way of doing it.
[Samsung Galaxy Nexus] Qafix:
I asked this question in the generals section but it didn't pick up so I hope it's ok for me to ask here since nobody seemed to have brought up this issue to my knowledge and search prowess.

My phone always gets super laggy anytime I copy in big sized files (be it one big file or an assortment of files) and while I was on ext4 I could always just use lagfix to cure the slowdown. Since I started using f2fs a couple of days ago however, I can't use lagfix thus it leaves me with the lag problem. I thought when converted to f2fs the write ups would not be a problem (it was blazing fast at first), but like mentioned, I had to put back all my files on my phone after converting and now my phone will not stop being laggy. Is there something similar to lagfix that I can do on f2fs? Any help would be appreciated. I'm on latest FML and Fancy kernel (and different kernels doesn't affect this). It's a write up lag.

Also, when I choose to repair /data partition in fml twrp, it comes up with an error (/system and /cache is fine).

Note: I found a small solution where once I've put back my files on /sdcard I do the following:

1. Swipe to factory reset

2. Advanced swipe and ticked /cache + /dalvik cache + /system and swiped away

3. Individually (/system, /cache, /data) repair or change format and press f2fs again (assumed already on f2fs) and swipe

4. Install rom and gapps as normal (meaning a new fresh install)

BUT, if I ever write up or copy a big file (eg. nandroid backup) it'll start being laggy again and I can't really afford to be clean installing so many times.

Any help would be much appreciated.
[Samsung Galaxy Nexus] Bazzu:
Damn wrong thread! Sorry guys!
[Samsung Galaxy Nexus] MWisBest:
I've got a new (to me) Galaxy Nexus on the way! Snagged one off of eBay for $60 that was just factory refurbished / replaced under extended warranty, the thing looks MINT!

Thanks to the deal I was able to get on the Galaxy Nexus, I'm also getting...

An official car dock (the non-pogo pin one) and an audio cable with in line microphone and media controls. This will allow me to safely use my phone in the car. I can't stand Bluetooth headsets, so to be safe I never talk on the phone when I'm driving as I'd have to have it up next to my ear with my shoulder etc. etc. its just really unsafe, and I also love playing music in my car with my phone, so rather than having to fumble around to find wherever my phone has slid off to and press the volume buttons for next/prev track (or now reach up to the dock and press the volume buttons on there!) I can just do it with the controls on the cable, which also happens to be where the microphone is of course. The cable plugs into the phone at a right angle as well which is nice, and goes into the aux jack I soldered into my car stereo straightly (no angle), exactly what I need!

I'm also getting a new case and a new screen protector. My old case was the XDA one from Cruzerlite, however over the past... 20 months, the entire front of it has worn off and changed color from the original dark gray to what is now white. My dad keeps making fun of it! Also, my existing screen protector is still in good shape, but I highly doubt I can transfer it over to the new screen without wrecking it...

THANKS AGAIN GUYS!

I'm completely stumped as to what is causing this. What is your internal storage usage like (e.x. how many GB do you have of free space)? And really there shouldn't be any need to run fstrim ("lagfix") on F2FS at all, and neither should there be on EXT4, FML mounts them both with the discard option, meaning it issues TRIM commands on the fly rather than all at once like with fstrim.
[Samsung Galaxy Nexus] Qafix:
I understand FML is awesome like that ;):good: My internal storage is normal (about 13GB usable) so there's no issue there. I started experiencing these lags due to write ups since before FML and while on EXT4. Just that now on F2FS I'm not sure what I can do to workaround this situation.

-----------------------------------------------------------------------------------------------------

.

Does anyone know the adb shell command to repair partition for GNex? On Nexus 5 it's ‘e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata’

Edit: Ok, so fsck command for F2FS is fsck.f2fs. When I ran the repair option in TWRP it came with "E:Unable to repair (/data or /cache)" "E:Error repairing file system"

Is there a way I can manually force fsck.f2fs on my /cache and /data partition? I tried fiddling around in the command terminal but I'm kinda flying blind here.
[Samsung Galaxy Nexus] Bazzu:
I'm here with you now :D! So courious to try this rom! I flashed fml a few hours ago. The first hour after the flash everything was really slow and laggy.. but i think after all syncro have finished, things went better. Now i've finished to restore my apps with titanium and i can say that this rom seems really good! Not so fast but good :)

(flashed fancy r54)

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] AbhishekS:
Plenty of times it happens for me that when the phone is locked and I try to wake it up, it just doesn't respond. And each time I press the power button, the phone vibrates, Eventually it reboots within 20 seconds.

Anyone else facing the same issue? Any solution?
[Samsung Galaxy Nexus] GilGameshn1:
Hmm

It is Kernel sided i think ... try to change Kernel ... and see what is happened ... DirtyV possibly ... And try to clear Dalvik/Cache ... Turn off CAB ( Content Adaptive Brightness ) and MCPS ,,, In TricksterMod App ... Could help also
[Samsung Galaxy Nexus] Jar3112:
I had this problem too, and tried various kernels. I think it's rom related, though I didn't try the most recent build.

I switched to cm11 m9 and I don't have the problem anymore

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] AbhishekS:
Even I feel its ROM related.... Would love to have a solution for it.
[Samsung Galaxy Nexus] Bazzu:
It's omg...how is it possible :eek:

Spoiler content hidden.

Guys what kernel do you have?

All with fancy?

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] rjshrjndrn:
I've a wiered issue with this rom.

when ever i am in a call , it disconnects automatically after a few seconds. I think this happens with the xposed framework. is there any solution or work around for this?

I Have no problem with pa or carbon or so
[Samsung Galaxy Nexus] MWisBest:
Hey look at this thing!

Yep, somehow the post office got everything here 4 days ahead of schedule (except the new case and screen protector, which is coming via UPS)! Already found multiple uses for the car dock while not in the car. First, (pictured), on the dev laptop, so I don't have to use two hands to test stuff on the phone etc., and its right there in my view always too. Second, on the back of my tablet LOL.

One little issue: Since I didn't think this stuff was going to be here for a while, I figured I'd take the time to do a fresh install of Linux and just generally get things cleaned up on this laptop. So it'll be another day before I'm at 100% here!

[MENTION=3679738]AbhishekS[/MENTION], what kernel are you using? The issue you're reporting is something I had an issue with long long ago in FML, and the issue was something in Fancy Kernel, which was what I had used for the FML kernel for quite some time. Even if it's not Fancy Kernel, whatever kernel you're using (even maybe FML's!) could've pulled in whatever caused that issue with Fancy Kernel and it'd be interesting to see what it is specifically.
[Samsung Galaxy Nexus] sagara.sandaru:
I love LP too[emoji3]
[Samsung Galaxy Nexus] MWisBest:
I don't even know if I would've noticed the background on the phone if I didn't already know it was there! :eek:
[Samsung Galaxy Nexus] AbhishekS:
Well I have never used any other kernel with FML, it has always been the one you have provided with the ROM.

How can I help you to sort out this issue? You want any particular details/logcats?
[Samsung Galaxy Nexus] Loureiro:
I got one time a soft reboot (I guess it what is called when it reboots instantly to bootanimation) after pressing power button and screen just lit, all black.

While using an app that records sleep noises and monitor the sleep states, every morning the phone was just on SOD mode, no response from power button, not even a reboot.

Never happened again since I disabled CAB and MCPS on fancy's.

It worth a try AbhishekS
[Samsung Galaxy Nexus] MWisBest:
First off, try what Loureiro mentioned.

Second, do you by chance use Bluetooth? I had a very very strange thing happen today when testing Bluetooth that was similar to what happens to you.