yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] agonzalez1010:
What I meant was a version of this ROM on a Nexus 6,…

---------- Post added at 04:55 PM ---------- Previous post was at 04:46 PM ----------

Your right. This appears to be a Galaxy only ROM
[Samsung Galaxy Nexus] sagara.sandaru:
Me too.. flashing SuperSU fixed it!
[Samsung Galaxy Nexus] piterdemon:
Because that superuser app SUCKS in every android version... With that app only really few apps have root access
[Samsung Galaxy Nexus] chilli_pepper:
New build is impressively quick. The extra ram had made a huge difference too. It multi-tasks relatively well.

I couldn't get it to flash over the previous build and work with either gapps package. Ended up doing a full wipe, flash of the new build then pa gapps. Selective restore and we're back!

Location still isn't working either on WiFi or mobile data. GPS is. The settings for location seem to get confused, but it seems to be on and set to high accuracy.

Manual APN required but that's a minor issue.

Great work MW! Get well soon.
[Samsung Galaxy Nexus] AbhishekS:
So has it arrived? :D
[Samsung Galaxy Nexus] MWisBest:
Actually got here on the 1st! Was just the mainboard that fried, eMMC was fine so I was able to save all my data thankfully. Lesson learned though: Don't count on the eMMC to store backups!! Bad habit I had from my days of having a device with a micro SD card...

Been working on getting the new build out pretty much non-stop since I got my phone fixed. I had a little beta test for toro users to check if there were any bugs with F2FS support (which there were/are) as I'm currently still on EXT4 and will be for a little while longer. Currently waiting to hear back on if the 2nd beta test I tossed up fixes it, but I've got a maguro build running now anyway so if 1. I hear that the toro build works with F2FS, I'm ready to throw up a maguro build to match, or 2. I hear nothing about the toro build, I'll throw up the maguro build as a little beta as well.
[Samsung Galaxy Nexus] AbhishekS:
Great to hear that. Can't wait to try out F2FS with your Dalvik optimizations. Take your time. The longer the wait, the sweeter the fruit! :P :D

BTW one OT question I have out of curiosity - Can I replace my maguro's 16GB chip with 32GB?!
[Samsung Galaxy Nexus] MWisBest:
Thanks!

As for the maguro eMMC replacement: no, not really. Theoretically it might be possible to desolder the existing eMMC and solder a pin-compatible 32GB eMMC (if one exists) in its place, but that's some really intricate stuff where 1. Chances of success are slim to nil, and 2. Even if you get the new eMMC on there correctly you will probably damage something else in the process.

Here's a picture of the maguro board, courtesy of iFixit: https://d3nevzfk7ii3be.cloudfront.net/igi/noJObJXR2ZSfniZV

The orange-outlined chip is the eMMC, as you can see it's directly attached to the mainboard.

Here's a picture that shows the toro board, again courtesy of iFixit (note: this picture shows the board as seen from the back of the device e.x. rear cover, the maguro picture shows the board as seen from the front of the device e.x. the screen): https://d3nevzfk7ii3be.cloudfront.net/igi/euSNI2bKQtmmsDQG

See the big chip above the battery pins that looks like it has an " f " (or maybe a " 4 ") on it? That's the eMMC. To the left of it is the SIM slot, and to the left of that is a ribbon cable of sorts that attaches both the eMMC and the SIM slot to the mainboard.

The reason it was replaceable separately for me is:

1. It's on its own board obviously, independent of the mainboard.

2. The Verizon Galaxy Nexus was originally sold with 32GB of storage, which ended up getting cut in half to 16GB toward the end of its production, so there was already a separate, made-for-the-device 32GB eMMC+SIM board. With maguro, it was only ever sold as a 16GB device (to my knowledge at least), so you can't simply get a mainboard with a 32GB eMMC for it.
[Samsung Galaxy Nexus] MWisBest:
Test build for you maguro users here. I'm just looking to see if F2FS works properly.

NOTE: The stock kernel doesn't support F2FS right now, you will have to use a different kernel that supports F2FS like usual.

Here are some details of how this works (or is supposed to work, anyway):

1. Rather than format /system when flashing the ROM, it instead just runs rm -rf, so it just leaves it as whatever you have it formatted to already.

2. When it mounts the /system partition, it doesn't explicitly specify exactly what type the file system is, it instead leaves it up to the mount program to figure it out.

With this way of doing things, there are no "conversions" or anything required, and the ROM is essentially indifferent to whatever you have your device formatted to. You could format everything to exFAT as far as its concerned!

omni-4.4.4-20140703-maguro-FML.zip (159.00 MB)

By the way, I'm also looking into whether or not it's feasible to do #2 above but for everything, everywhere, meaning even just booting Android. That would result in completely seamless support for any filesystem, on any ROM (that uses these fairly small changes), with any kernel (so long as it supports the filesystem you've formatted to in recovery)! Oh, that would also allow you to use whatever combination of filesystems you want, for example only format /data to F2FS and leave /system and /cache as EXT4.
[Samsung Galaxy Nexus] qtoo941:
So this last build is F2FS? Because i still haven't formated my partitions to F2FS, can we get normal build (not f2fs)?

also, what's the changelog?
[Samsung Galaxy Nexus] Gingerbread1611:
Thanks for the new build! :)

btw: How well does Xposed work with your rom? I haven't used xposed in a while and wonder how big the performance loss is. (I don't plan using that big modules.)
[Samsung Galaxy Nexus] MWisBest:
It's not a finalized build yet so there's no official changelog. Right now I'm just making sure the work I put into supporting F2FS is bug-free.

The point of the work I put into F2FS was to make supporting both F2FS and EXT4 ("not f2fs") seamless...

Don't want to use F2FS? No problem! You won't notice anything different.

Want to switch to F2FS? No problem! The ROM should work just fine with F2FS too!

Want to use... exFAT? FAT32? Whatever!! I don't think that's a great idea, but the ROM should work with just about anything!

I honestly have no idea. I don't really think Xposed can cause a performance loss, but the good news is that Dalvik in FML is faster than ART, so you won't have to sacrifice speed to use Xposed at all. Seriously! You know how awesome ART felt after first trying it with KitKat? With FML the tables are completely turned: ART isn't any slower, but Dalvik has gone from like, twice as slow as ART to twice as fast as ART!
[Samsung Galaxy Nexus] AbhishekS:
What do you recommend personally? F2FS or EXT4.
[Samsung Galaxy Nexus] pianistaPL:
Wait, wait, you mean this is first ROM which can be installed on ext4 and f2fs without converting? :)
[Samsung Galaxy Nexus] MWisBest:
I can't say, I haven't tried F2FS yet!!

...that'd be a first? :eek: I guess so then!

EDIT: Well the sun is rising now so I guess I should sleep finally... see you in like, 12 hours...
[Samsung Galaxy Nexus] pianistaPL:
That's right, first :)

I will install test version in few hours.
[Samsung Galaxy Nexus] Sletmo:
Just flashed the test build on my device, and everything seems to be working properly!

Steps to reproduce:

1. Make sure the phone has been converted to f2fs

2. Format everything but internal storage

3. Flash ROM

4. Flash kernel (I used DirtyV-URSR from 6/28)

5. Reboot
[Samsung Galaxy Nexus] AbhishekS:
So you mean to say I can use F2FS without having to back up my personal files (images, videos, etc.)?
[Samsung Galaxy Nexus] pianistaPL:
No, no... I mean you have to convert your phone to f2fs first and then you can install f2fs ROM.
[Samsung Galaxy Nexus] NARDO86:
Just installed new version whitout formatting /system in order to test if rm -rf works aaaaaaaand.. it seems to works!

This morning i converted your last version (the one in op) with poo706's converter then i formatted and installed everything following instructions in Dirty_V kernel post so now i just updated without reformatting following those step:

1) boot in recovery

2) installed new version (nothing was formattes)

3) wipe cache / dalvik

4) installed mini gapps

5) installed dirty kernel

6) reboot
[Samsung Galaxy Nexus] jesan9:
Really nice and fast the f2fs build, but can i ask you to add lockscreen notifications? i love that :D
[Samsung Galaxy Nexus] MWisBest:
News:

1. I'm close to having a completely filesystem-agnostic ROM. F2FS support has been added to the FML kernel, and TWRP automatically mounts /data, /cache, and /system properly, regardless of whether they're EXT4 or F2FS or whatever. Android is giving me fits with it but I'm already whipping up code to fix that.

2. I'm now the maintainer for all Galaxy Nexus devices for OmniROM. I already have a number of fixes that are in FML that can be merged into OmniROM for it, however OmniROM's device trees are based off of Cyanogen Inc.'s whereas FML's are based off of AOSP, so I have a little bit of porting to do.
[Samsung Galaxy Nexus] V_tunes:
good job buddy, galaxy nexus is alive again since omni give up supporting.
[Samsung Galaxy Nexus] pianistaPL:
Wow, that's amazing!!!
[Samsung Galaxy Nexus] flip360:
Must say i agree with chilli_pepper on all the points made in his post apart from gapps part, i always do a clean install :)

Great work, well worth the wait and as always hats off to the dev team! Get well soon [MENTION=3390093]MWisBest[/MENTION]!
[Samsung Galaxy Nexus] aditseng:
Thanks [MENTION=3390093]MWisBest[/MENTION]. Great work in spite of your illness. All of us are hoping you get well soon (and not only because of new builds!).

Here's what I found:

- No issues while installing. CWM + full wipe + PA gapps worked fine

- On first boot Google Text-to-Speech crashed more than once

- First boot went perfectly

- On opening Maps again Text-to-Speech crashed multiple times. Oddly enough this didn't prevent the spoken instructions in navigation from working

- Location took a long time to load. I think WiFi location is not working properly.

- Torch/Camera crashed. (I know it's a known issue) just putting it in for completeness

- Charging bug -- shows charging even when not charging!

I'll update it further as I find out more stuff. But otherwise it's really great work thanks to all these guys working tirelessly through sickness and work!
[Samsung Galaxy Nexus] Loureiro:
[MENTION=3390093]MWisBest[/MENTION] could you change the last boot.img filename? It is replacing the old boot.img meant to fix kitkat beta ROM that jerks network.
[Samsung Galaxy Nexus] idrather:
In the process of doing this, I downloaded the hotfix boot.img. However, when checking the md5 has, I got d22ff75ca01d9bc9bbde9b7261357326, instead of 22fff910143c4561f2f66dc163a82c47. After four downloads, it's the same result. Am I doing something wrong? Thank you.
[Samsung Galaxy Nexus] Loureiro:
Read the reply above yours and you'll understand what's happening.
[Samsung Galaxy Nexus] royzlife:
Update-2

Hi

I got error 'cannot connect to camera' on both camera 360 and camera zoom fx. anything else may be i should try?

btw, does installing SuperSU fix the issue with failed restoration with Titanium Backup?

Again :good: to the devs!
[Samsung Galaxy Nexus] kinleyd:
Initially just dirty flashed 12/07 fml rom. It had only three problems - G+ app disappeared and wouldn't reinstall from backed up apk; Google Play Services kept crashing; supersu wouldn't work even though it's baked in the rom. Problems with camera, chrome/firefox, youtube, lag, all gone at this stage.

Then dirty flashed 11/09 fml gapps. The 3 problems mentioned above went away.

So all good on my maguro. Thank you MWisBest!
[Samsung Galaxy Nexus] aliesz:
I updated google play services and text to speech and their related errors or notification has been solved. the only problem now is camera issue which is known for gnex lollipop roms.
[Samsung Galaxy Nexus] dehein:
Yes installing SuperSU fixes titanium restoration.
[Samsung Galaxy Nexus] dpunx:
Really great this new build!

Bugs in this version:

- Mobile Freeze (Charging with mobile power off)(Remove Battery)

- Google Now Launcher Lag-Restart (Seems like Google NL consumes a lot of RAM, with nova launcher all runs smoothly!)

- Camera (All knows)

- Sound (Sometimes sound glitches audio when not playing)

- Torch (Not work and when press... Fade out xD)

Thanks @ MWisBest
[Samsung Galaxy Nexus] aliesz:
please wipe system, cache and dalvik cache then flash fml latest build again,install camera zoom fx again it works... which version of supersu have you installed? i flashed 2.37 supersu zip file but none of titanium or super backup apps doesn't work properly.
[Samsung Galaxy Nexus] DevH:
Till now as pointed but others, i didnt notice any such lagginess. No Playstore crash or problem with audio quality, infact the audio quality seems enhanced while using headphones but the overall loudness of the speaker seems to be on the lower side, it could bother noticing an incoming call ring in crowded places.

I am not into clicking pictures every now n then, so can live without camera.

One thing thats intriguing is the ambient notification display which seems to get triggered while shaking the phone a little or may be a gentle tapping push. I hope that feature could be enhanced somehow and would be great to see the notification by just picking the phone up which uses the gyroscope sensor n thanks to the AMOLED panel on this phone. Hope developers figure it out. I did manage to notice it everytime but coulnt make it out what possible right way was triggering lighting up the ambient dark display showing just the incoming notifications.

Again thanking all the developers behind the project for their sincere work n make this happen
[MENTION=3390093]MWisBest[/MENTION] thanks brother for all the hardwork behind making this happen.
[Samsung Galaxy Nexus] royzlife:
May be [MENTION=4700434]dehein[/MENTION] can confirm which version of SuperSU works with TB. Will try out the build once again today. thanks.

Another short q for all - I tried with PA 5.0 gapps yesterday. The FML gapps in OP - did any one try that and share experience.
[Samsung Galaxy Nexus] aliesz:
I tried PA 5.0 gapps and after updating google play services and google text to speech from play store no error appeared and everything works good. :good:
[Samsung Galaxy Nexus] lo97:
I don't know if is a hardware problem but my phone keeps saying it's charging even if it's unplugged. Not a problem if battery is >15% then it keeps saying to activate energy saving mode so it's annoying. I saw it happened to another user, so is hardware or software problem? How to fix it?
[Samsung Galaxy Nexus] dehein:
Well i just used the 2.37 beta. Nothing else. Superuser integrated into the rom had even on Kitkat sometimes problems with TitaniumBackup on some Roms. But thats just my opinion.
[Samsung Galaxy Nexus] CYoung234:
Great work MWisBest! One problem I am seeing is that my Phone and MMS are not working. I Factory Reset, installed the ROM and FML Gapps, downloaded all my apps, etc. The APNs are configured. Data is working, but phone and MMS are not. I am trying to reboot the phone now, but if I cannot get calls and mms working, I will have to go back to my nandroid. I will save a nandroid of my configuration before I do that, though.
[Samsung Galaxy Nexus] Ma7moud90:
Great improvement over the last build, but the ROM is still completely ignoring at least 180MB of free RAM, I mean when the LMK kills the foreground app i'm typing in with 184 MB of ram still free then i don't think this is a good thing.
[Samsung Galaxy Nexus] what9000:
Very nice build. Great work, thank you to everyone involved for all of your efforts.

I'll echo some comments so far that Nova launcher is much, much quicker than google now. More fluid and less lag between button presses.

As for bugs, all I have noticed is an audible "pop" every now and then, not finding location on WiFi (haven't tried GPS lock outside yet) and of course the obligatory camera. Later today I'll try calls/MMS/GPS, so far SMS and data works.

This is great to see a 3 year old phone coming close to what my wife's nexus 5 feels like.
[Samsung Galaxy Nexus] agonzalez1010:
Thank You for understanding what I meant
[Samsung Galaxy Nexus] aditseng:
Thanks again [MENTION=3390093]MWisBest[/MENTION]. I can guess what you're planning next!! But lips are sealed.

If you need a logcat for anything don't hesitate. Just a few more updates:

- battery life is much better than KK

- location only works on GPS. mobile/wifi locations don't work

- torch works only if I've just rebooted and then never works again (till next reboot)
[Samsung Galaxy Nexus] denis4o:
Does anyone else have problems with the 4.4.4 ROM and Candy Crush Saga? The game just flashes the screen and then exits. I tried it on two of my Samsung Galaxy Nexus'es and they both behave in the same way. With other ROMs the game works fine.

Thanks in advance.
[Samsung Galaxy Nexus] billyx1:
Which version did you install?
[Samsung Galaxy Nexus] CoDe LaZaRuS:
guys are the fml 5.0 builds stable to use as a daily driver yet. I am waiting patiently for a stable build so I can move on to lollypop
[Samsung Galaxy Nexus] CYoung234:
I would suggest making a habit of reading the last 10 pages or so of any thread rather than asking questions like this first. In terms of daily driver status, a lot depends on what you need to have working. If you need the google camera, for example, there are still some problems. If you need a lot of the KitKat FML features, again, some of the user interface stuff has not been added yet. So, please go back and read about what is working and what is not in order to make up your mind.
[Samsung Galaxy Nexus] CoDe LaZaRuS:
Yea sorry was busy at the time so I thought it more convenient to ask.

Camera dosent matter I just want speed and battery life. I dont mind a few hiccups as long as it dosent ruin the user experiance
[Samsung Galaxy Nexus] aliesz:
6.5.87 version of google play services.
[Samsung Galaxy Nexus] alboz83:
I'm try the new FML and i can say that it's awasome. Now i'm waiting for the camera fix because i need it, and also because other camera app how camera zoom fx not works always and i must reboot for to use. Anyway thank you very much MWisBest, great work :)
[Samsung Galaxy Nexus] aliesz:
You can use camera zoom fx app instead of google stock camera app.
[Samsung Galaxy Nexus] alen_gh:
I think Fml 5.0 builds are not yet totally stable . Thanks to Developer who is working on. We have just to wait :). Report bugs or may be coding ;)
[Samsung Galaxy Nexus] NetBender:
My stock(and Google too) camera works so, maybe, the bug has been solved, i flashed ROM and GApps after wiping system+data+cache.

Wi-Fi/Data Location, instead, keeps doesn't working.
[Samsung Galaxy Nexus] alboz83:
I use camera zoom FX, but after a few time not works, i get error and i must reboot to use it again.
[Samsung Galaxy Nexus] aliesz:
For me 5.3.7 premium version of zoom fx works properly and without crash.
[Samsung Galaxy Nexus] CYoung234:
I decided to give this one more try, so I tried a complete factory reset and install of the latest FML and FML GAPPS, and texting was working at first, but it quit sometime during me updating my apps via the Play Store. Attached is a logcat. I zipped it, as the logcat.txt exceeds the allowable size here on xda for some reason.
[Samsung Galaxy Nexus] demlv:
Do you mean that WiFi does not work at all, or is it that WiFi-location (non-GPS location) is not working?
[Samsung Galaxy Nexus] NetBender:
WiFi-location
[Samsung Galaxy Nexus] BestBrd:
The ROM is extremely fast but I have this play store bug that makes me crazy...I'm running latest FML+FML gapps,and upgraded from the 16/09 build wiping system, cache and dalvik and reinstalling gapps+rom
[Samsung Galaxy Nexus] billyx1:
Just for information: I tried installing this version of play services several times without success (installation failed).

Finally I had to made a factory reset. Now the play services are working.
[Samsung Galaxy Nexus] dpunx:
Try this:

Go Settings > Aplications > Playstore (Clean Data)

Go Settings > Aplications > Playservices (Clean Data)

Reboot

Configure again your account and try it's work
[Samsung Galaxy Nexus] BestBrd:
Tried everything..nothing :(
[Samsung Galaxy Nexus] rodinux:
You can try to use 3g not wifi, I also had this problem before, switch from wifi to 3g then OK.
[Samsung Galaxy Nexus] RoadToNever:
Anyone else getting multiple Pushbullet notifications since Lollipop?
[Samsung Galaxy Nexus] rajputrajat:
I got the same problem twice..

You have to install fml and fml gapps once again..

Happened to me, since i flashed two different version of gapps on top of each other... some kind of clash there i guess...
[Samsung Galaxy Nexus] boorce.com:
Hi,

My 2 cents for this ROM : to get APN at startup, download the apns-conf.xml from a KitKat ROM, flash Lollipop, mount system and then, still in recovery, via adb shell or with the recovery shell, copy the new file over the old one:

cp /sdcard/Downloads/apns-conf.xml /system/etc

And now you have all the needed APN!

PS : The attached file is named apns-conf.txt, you have to rename it apns-conf.xml due to upload restrictions...
[Samsung Galaxy Nexus] boorce.com:
Coffee pot remote control ? :o
[Samsung Galaxy Nexus] Djalaal:
I have had the 11/16 build since it came out, and I got the 12/07 build as soon as it came out. I'm on maguro, clean flash, PA Gapps for lollipop Alpha1.

As a heads up, I'd like to report my findings on bugs that (

may

) still be there:

-I can confirm the white balance to be off (has green/yellowish tint). Sometimes it looks fine, depending what scenery I'm photographing. I know you know this already...

-I can also confirm that charging while the phone is off makes the phone hang and needs a battery pull to fix.

-The ROM still ignores 160MB of free RAM. Killed my browser multiple times as soon as a picture-heavy site was loading, although I still had over 170MB RAM left. My launcher (it's quite RAM-heavy) got restarted many times as well.

-Flashlight is buggy. I can't find a pattern to the problem yet, but it seems that when I try using flashlight, my camera 360 app stops working. Today, the whole SystemUI crashed. It asked me to send a report, which I did, dunno if you actually get that.

-Video playback is not quite fixed for me. YouTube, and hardware decoder mode on MX Player does not work for me.

On the other hand, other good things I noticed were:

-More RAM is available, making multitasking more smooth. (Although offset a bit by aggressive app killing).

-Overclocking seems to work, although I didn't test it much.

If you need a logcat for any of the above, do let me know.

P.S. Like many others, I also experienced titanium backup not restoring, but that's only using superuser. It works with SuperSU. So I'm assuming it's a app bug.
[Samsung Galaxy Nexus] frickinjerms:
Useless knowledge time!

If you pull the status bar with two fingers it pulls the quick settings down with one swipe ?
[Samsung Galaxy Nexus] Kustaa:
I tried the rom, awesom work. Thanks for bringing us some lollipop taste to our beloved tunas. I'm not listing bugs cause I think they're pretty clear by now.

Atm I'm back to 4.3, I personally think there's nothing that can beat JB performance yet, but this rom and CM12 seems promising.

Thanks again!!
[Samsung Galaxy Nexus] NetBender:
Do you have a backup of the KitKat's one?
[Samsung Galaxy Nexus] Loureiro:
Unfortunately no.
[Samsung Galaxy Nexus] what9000:
One thing of note with cellular connectivity: it seems that my install of lollipop is unable to maintain connection to the network once I connect to WiFi. Often I would be sending SMS messages just fine, and suddenly I would have unsent messages past a certain point... After disconnecting from the WiFi, I have an exclamation mark on cellular services, it shows disconnected in the "about phone" section, and after a reboot, it is good to go again.

My workaround is to simply use google hangouts for chat instead. :)
[Samsung Galaxy Nexus] chinarobin:
cant send sms ether，here.