yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] PainFly23:
I see what you mean, but it's essentially the same rom and just an unofficial build. Didn't want to clutter the kernel thread with rom-specific posts anyway.

Unfortunately our problem is a bit different. SELinux is set to permissive by default. The problem most of us seem to be having is a bootloop immediately after installation from recovery.

Also, it seems I'm able to reproduce the flashlight/camera problem by using the flashlight quick toggle from the lock screen. Can anybody else confirm?
[Samsung Galaxy Nexus] wmarcin:
That's what I ran into, as well. Neverending boot.

Are you saying that if the SELinux wasn't set to permissive, we wouldn't have the boot loop?

... moto x vzw ...
[Samsung Galaxy Nexus] PainFly23:
No, sorry if that wasn't clear. That workaround is recommending to switch to permissive, but that's already default for us, so that's probably not the problem.

Glancing through the xposed discussion thread, I've seen a few cases of people with nexus devices on stock roms having bootloops as well. I wonder if it could be a similar issue? Anyhow, I think it's worth waiting to see if this is something rovo is going to address before we worry too much about it. This is only the first public alpha release after all, issues like this are to be expected.

But darn, how I miss gravitybox...
[Samsung Galaxy Nexus] wmarcin:
Gravitybox and Greenify for me. As well as the adblocking modules.

Thanks for clarifying.
[Samsung Galaxy Nexus] MWisBest:
New build will be coming soon. I've been very busy with school and haven't had much time for FML...

I will try and go back over the posts made here sometime soon.

As for the Xposed issue:

1. I have a few changes in ART. Xposed isn't going to play nicely with those, as it tries to outright replace ART, but those changes I made in ART are relied upon elsewhere.

2. Xposed forces ART to do the "long boot-up" where it compiles all the system app code on the device instead of using the pre-compiled system app code (the ".odex" files generated when the ROM is built with "WITH_DEXPREOPT" set like I do). With FML's optimizations, this causes the ART compiler to crash. I never bothered to figure out why since it made more sense to do the first ROM boot-up on the device like 10x faster at the expense of having my builds take 15 minutes longer.

I hate how Xposed was done for ART. But I don't know if there's really a "better" way it could've been done either. It's likely the only way Xposed will work with FML is if I build the "Xposed ART" myself...

(P.S. Did anybody see my orange username? :D)
[Samsung Galaxy Nexus] arigr:
orange is uber you know.. cool..and well deserved..
[Samsung Galaxy Nexus] RW-1:
Naah, it's blue :)
[Samsung Galaxy Nexus] wmarcin:
Are you planning to built your very own xposed ART? [emoji106] [emoji106] [emoji3]

... moto x vzw ...
[Samsung Galaxy Nexus] MWisBest:
Maybe not for a little while actually... AOSP 5.1 is rolling out
[Samsung Galaxy Nexus] wmarcin:
That's understandable. Thank you for responding. And this awesome ROM.

... moto x vzw ...
[Samsung Galaxy Nexus] MWisBest:
Looks like I managed to beat some of the devices that have "official" support this time around.

Galaxy Nexus is immortal!

Few little things to fix up yet.
[Samsung Galaxy Nexus] Christopher8989:
Anxiously awaits! Good work!
[Samsung Galaxy Nexus] KShion619:
May i ask what was/is broken in between 5.0.2 and 5.1.0? looks like RIL is borked, or you have no SIM
[Samsung Galaxy Nexus] Alton (Halo 2):
You're amazing <3 always one step ahead.

sent from my HTC One m8 that's better than nexus 6
[Samsung Galaxy Nexus] MWisBest:
It's pretty much down to just the RIL at this point. I'm not sure what changed to throw it off so badly.
[Samsung Galaxy Nexus] KShion619:
Well, Dual Sim support may have got ya there, thats my only guess, maybe look in SIM slot code, as the RIL loads, hence the baseband showing in your screenshot
[Samsung Galaxy Nexus] Shadow Death:
Guess who's back... back again... I'm on my Gnex for a few days. Man I forgot just how bad the battery life was on mine. Actually, I think the battery itself is bad. :mad:
[Samsung Galaxy Nexus] MWisBest:
RIL is fixed, it's all pretty solid now. I'd even go as far as saying it's more stable than 5.0 already.

Toro build should be ready in about an hour, maguro build might be done tonight, toroplus will be done tomorrow.
[Samsung Galaxy Nexus] Alton (Halo 2):
Pretty sad my Galaxy nexus is going to have 5.1 before my M8.
[Samsung Galaxy Nexus] Shadow Death:
What's pretty sad is that they're doing great work with the M8 and I have to ship mine back to HTC because of a bad sim slot. What's really sad is that my old Gnex was there for a rescue. :)

I refuse to get rid of it. :D
[Samsung Galaxy Nexus] Alton (Halo 2):
Are you going to s-off your returning m8 again?
[Samsung Galaxy Nexus] Shadow Death:
Yes. I'm going to restore my current m8 back to factory settings and software. Then when I get my new one I will s-off again. :)
[Samsung Galaxy Nexus] Alton (Halo 2):
Nice :) hopefully they won't pull a Verizon and update your android version to the latest. Like Verizon did me. Now I'm sitting here waiting for sunshine 3.0 while I could be flashing sense 7 right now.
[Samsung Galaxy Nexus] Shadow Death:
Well from the looks of things 3.0 isn't that far off.

So... MWisBest... bout that m8 support. lol :p
[Samsung Galaxy Nexus] MWisBest:
Aaand here we are.

ROM: FML-AOSP-5.1-20150311v2-toro.zip (200.62 MB)

GApps: FML-PA-GApps-Micro-5.1-20150310-UNOFFICIAL.zip (149.31 MB)

What Doesn't Work (Yet):

- Video Playback (Fixed With v2 Build)

- Flashlight Tile

What Does Work:

- Everything Else(?)

It's pretty solid and stable so far for me, but I'd prefer if it gets tested out by some other people before I 'promote it' to the main post.

EDIT: BTW, Superuser isn't baked in just yet, so you'll have to flash SuperSU or something for it.

Also, I'm going to be dropping support for 4.4 and 5.0 now. Due to 5.0's suckiness, I had planned on going back to 4.4 to do a build with all the latest stuff that's been done for the Galaxy Nexus, but 5.1 is good enough to not make doing that worth it anymore.
[Samsung Galaxy Nexus] MWisBest:
Fix for video decoding might be ready to go tonight.

If you've already flashed this 5.1 build, you'll be able to flash the next one without wiping dalvik-cache.

And flashing 5.1 on top of 5.0 without a /data wipe should be OK by the way!
[Samsung Galaxy Nexus] RW-1:
Awesome!

downloading and may try if I have time, if not hopefully your update with working video playback might be the one to flash.

since some of us went to smitty's 5.0, another clean flash may be necessary though in that situation ,,,
[Samsung Galaxy Nexus] MWisBest:
New build with fixed video decoding is up, I've updated the link in the little "5.1 post" above. Added bonus: Play Movies & TV works, and Netflix should work now too.

I was under the impression that Brian's builds were of FML. As long as it's not something like CM you should be fine.
[Samsung Galaxy Nexus] cujo6801:
Thanks..

DL'ING Now.....

Sent from the "DOG" pound
[Samsung Galaxy Nexus] RW-1:
Totally terrific answer!

Was busy this morning so far, will grab the revised build and get to it later this afternoon/evening.

The T-mobile 5.1 release mentions fix for multiple SMS sends, I've had this as well on VZ, I'm hoping that fixes that as well. But mainly I'm looking forward to all the commits to fixing the memory leaks ...

Anyone who's flashed already care to chime in on performance?

MW, you are "The Best" :)
[Samsung Galaxy Nexus] bsmitty83:
I flashed the 5.1 build dirty over my builds to check it out and it was fine .

Of course they are FML [emoji1]
[Samsung Galaxy Nexus] Shadow Death:
Flashed 5.1 and SMS didn't work for some odd reason.
[Samsung Galaxy Nexus] MWisBest:
I've been using the Verizon messaging app, but it is sending and receiving SMS messages without being on WiFi so I'm not sure.

Were you by chance sending a long SMS message (>150 characters or so)? And did you give a reboot a try as well?
[Samsung Galaxy Nexus] Shadow Death:
I tried sending short SMS. I didn't think to reboot the phone though. I will give it a shot later. 5.1 runs faster than any of the 4.4.4 Roms I've ran on this thing.
[Samsung Galaxy Nexus] RW-1:
Hehehe, you beat me to it!

I did as well.

Verrry nice!

Do we need to do the VZ mms fix in this one? I held off and so far it seems ok ...

So smitty, can any of the R series work on this (I assume yes, but nicer to ask, especially because I was wondering about R11 for it which hasn't yet happened, or am I incorrect)?
[Samsung Galaxy Nexus] bsmitty83:
Yea r11 should work fine , the audio changes should be there AFAIK
[Samsung Galaxy Nexus] RW-1:
UPDATE: Ok my cal is back, really weird, I did two reboots for that and it just didnt have my account, nor the calendar sync option under my google account settings.

All's well there.

Interesting smitty, I went from 340Mb free on your 3.15 back down to 110 .... :(

Weill load an R series kernel shortly.

Tried SMS, those were ok, but it hangs trying to send a picture (not a FC or anything, just sits on sending) should I flash the VZ MMS fix?

UPDATE: I flashed that and rebooted, good to go sending photos....
[Samsung Galaxy Nexus] pkgnex:
RW-1:

What did you flash to get cal and photo-send working? (SMS fix or smitty's kernel)?

Also, can you confirm the Gapps you used and if SMS works?

Thx.
[Samsung Galaxy Nexus] Shadow Death:
Reflashed right before lunch. Its working great now. I remembered something about TWRP not formatting correctly sometimes so unused the -rf option and it worked. So I'm assuming that some chunk of 4.4.4 was left over.
[Samsung Galaxy Nexus] RW-1:
I believe it was linked to from here,called "vzw-lollipop-mms-fix.zip" (If I can find I'll edit and link to it)

UPDATE: It was ZZ's, http://xdaforums.com/showpost.php?p=58148948&postcount=3023

I used the GAPPs MW linked to on the same post as the ROM.
[Samsung Galaxy Nexus] RW-1:
Anytime!

Ok, first trip out of wifi, got on 4G ok, but appears to have difficulty going to 3G, haven't yet seen it on 3G.

I'll evaluate tomorrow on way out to work...
[Samsung Galaxy Nexus] jguerdat:
I guess I'm just blessed with the world's weirdest Verizon GNex ever. I've had nothing but trouble with these ROMs and web browsers absolutely killing performance regardless of how stripped down they are. However, I can live with that even if it should somehow be fixed since it's just my bedside clock.

The 5.1 ROMs have really bitten me hard. CPU is high at all times, causing Daydream to start and then kick out. Screen is on all the time as a result (turning off Daydream at least allows the screen to blank). I clean flashed, wiping cache, Dalvik, /system and /data. How can anything go so wrong?
[Samsung Galaxy Nexus] KShion619:
You stated you have no sim? remove

/system/app/BIP
/system/app/IMSFramework
/system/app/RTN
/system/app/SDM
/system/app/SPG
/system/app/SyncMLSvc
/system/app/VZWAPNLib
/system/app/VZWAPNService
/system/lib/lib_gsd4t.so
/system/lib/libsecril-client.so
/system/lib/libsyncml…….anything
/system/vendor/lib/libims.so
/system/vendor/lib/libims_jni.so
/system/vendor/lib/libims-ril_lte.so

and it will at least keep your device from being awake all the time, CPU should also cool down a bit, essentially the system is asking for a sim over and over
[Samsung Galaxy Nexus] jguerdat:
Didn't say no SIM. I do have one installed. No problem on 5.0x. I don't have any cell access since it was replaced by an S5. Now what?
[Samsung Galaxy Nexus] KShion619:
If its not being used I'd still try it, i dont have two SIMs to test that theory out sadly, try removing the SIM and running those deletes, oh and If the file doesnt exist, skip it, thats adapted off my old 4.0-4.4 deletelist i made to avoid wakelocks without sims
[Samsung Galaxy Nexus] jguerdat:
I removed the SIM but no deletes yet. All seems fine. Perhaps related to this and [MENTION=3390093]MWisBest[/MENTION]'s phone display is that I only have one. AFAIK, Verizon always only had one - there's no second slot for another.

Edit: Oh, yeah, I was getting a "No SIM" icon/notification before I removed anything. FWIW...
[Samsung Galaxy Nexus] Mach3te:
I am having an issue when I reboot FML 5.1 with the google apps. When I do the first reboot after installs, many of the google apps (Hangouts, Google Music, Youtube, and Messenger) are force closing on boot. Not sure whats causing this, but any help would be appreciated. FWIW, I did a dirty install with a wipe of cache, dalvik, and system as well.
[Samsung Galaxy Nexus] KShion619:
Sounds like a dirty flash, try erasing Dalvik/Art cache, i havent seen any issue, but i clean flashed
[Samsung Galaxy Nexus] arigr:
well then i must be the guy that got the best one :P this is probably the rom i was waiting for ..no problems at all..factory wipe on twrp..recommended g apps...weird that i couldn't skip google log-in but once i did all cool...rebooted and checked playstore..updated a dozen apps and reinstalled verizon messenger..mms sms photos all working..battery after 10 hrs with light use still at 56% after install..location off so still need to test gps and maps..winner winner chicken dinner
[Samsung Galaxy Nexus] EAK128:
Everything working great here also. Clean flash with the mms fix. Multitasking, sms/mms, gps, camera are all working great! Only thing left is the green lines on the video recording. Thanks MW!
[Samsung Galaxy Nexus] jcpowell:
Anyone else having issues installing the Google Keyboard?
[Samsung Galaxy Nexus] dj-bilbo:
Had to leave 5.0 because honestly too laggy on my GN and I use my phone for work, especially apps like online banking deposits (requires camera), google voice & hangout, & hangout dialer etc.... 4.4 worked fine enough, but not quite as fun as Lollipop.

So decided to give 5.1 a try.

from 4.4 to 5.1 (using CWM still):

reset/wipe dalvick ;

flashed 5.1 rom, FML.GA.Apps & vrz fix (just in case).

stock kernel (for now)

flying dots/Boot-up screen lasted between 5 & 10mn. Usual google login phase with auto login etc.

Updated all google apps (hangout, voice, cal, etc...)

All works :D. Seems much smoother than 5.0. :good:

Will continue to play with it for next few days and maybe try r11 later on :)

Thanks MWisBest!!
[Samsung Galaxy Nexus] RW-1:
So far, I've not been able to open any utube videos, I know MW mentioned video issues, but was this one, or just recording?

Still looking at mobile connectivity, it held 4G better this am, but in reference to my last post, I'm awaiting a downshift to 3G to see how that goes, last night it didn't want to go to 3G at all.
[Samsung Galaxy Nexus] 67jeffh:
I just checked to see and it is working ok on mine (YouTube that is).. I'm using the V2 FML version..
[Samsung Galaxy Nexus] RW-1:
Hmmm ... everything else on my dirty flash is ok, I'll try clearing cache and data on the utube app and a reboot sometime today and see if that clears it.
[Samsung Galaxy Nexus] 67jeffh:
I did do a clean install though. I was coming from the CM 12 1.9 DDK rom...

Let me clarify that, clean install for the original 5.1 then a dirty for the V2 version..
[Samsung Galaxy Nexus] RW-1:
I did a dirty from smitty's last released 5.0, which is FML, to the 5.1, originally I clean flashed as well.

Well, Force stop, clear cache and data didn't work. Really not sure why it doesnt open anything for me, but, now it just gives me the loading circle, where before it announced almost right away that there was a problem loading the video, tap again to retry.

I tried on mobile as well. And I may go clean flash and then R11 again, because I believe I'm not getting any connectivity to 3G, when I went off wifi here, it should have gone to 4G, but us stayed with an "!", until I cycled MD off/on, then 4G came right up on me. I didn't lose 4G on my way into the office, so I couldn't verify that is connects outside to 3G when I lose a good 4G signal, but I suspect I will. :(

Crap, I cant play local videos as well (thru gallery or photos selecting them), was fine on previous 5.0, anyone have thoughts? R11 installed, audio is ok ... no mods. Tried R10, got no sound anywhere, flashing back to R11 ...

Darn annoying me now....

UPDATE: Ok, reflahing R11 and it's back, that is weird .....

On separate note, MW, possible that you could post a zip of the included kernel for 5.1 that you used? I'm not saying my issues are kernel related, but having just the included kernel to flash back would be nicer then re-flashing the whole ROM if one needs to troubleshoot ... thanks beforehand if possible.
[Samsung Galaxy Nexus] 67jeffh:
No, It installed without an issue on mine.
[Samsung Galaxy Nexus] jcpowell:
It must be my dirty flashing habits. I'll try again later when I've got time to do so.
[Samsung Galaxy Nexus] cowsquad:
Youtube wasnt working for me. Links on SMS app force closes the app. Setting in stock browser force closes the app. I was on clean flash. I just went back to fml 5.0
[Samsung Galaxy Nexus] vladimirhtg:
WOW. v2 is killing it! Truly in love. Awesome. Great work. Donation in order.
[Samsung Galaxy Nexus] RW-1:
Yeah, you know I was thinking ...

If I didn't have the data connectivity issues on handoffs, etc. I wouldn't really have a reason to move off the the GNex to something else, but that said, getting a new phone that's larger more powerful and has more RAM ... it is time in that aspect. It's too bad samsung couldn't do another one like this with current HW ... I know there are GNex detractors, but it had no HW buttons, a slightly curved screen (before any of them did) and looks awesome, etc .... N6 comes close...
[Samsung Galaxy Nexus] Shadow Death:
Ended up having the same issue with my second flash. It seems to be random too. SMS will work great then suddenly stop working for no apparent reason.
[Samsung Galaxy Nexus] dbt816:
Anyone else notice that busybox is missing from the 5.1 build? I only noticed when I tried to run Trickster.
[Samsung Galaxy Nexus] RW-1:
Yeah, but just run your favorite installer.

Can one use the latest with Trickster? I used to just load 1.20
[Samsung Galaxy Nexus] dbt816:
Trickster offered to install 1.22.1 and that seems to work fine :)
[Samsung Galaxy Nexus] RW-1:
Wow, that's higher then jrummys installer app even shows ... :)

Trickster runs fine, just wondering what I get if I move up in busybox itself ...
[Samsung Galaxy Nexus] dbt816:
Here's the changelog for Trickster's "Busybox On Rails":

https://code.google.com/p/busyboxonrails/source/list

Looks like he's up to 1.23.1 now... must not be on the Play Store yet.
[Samsung Galaxy Nexus] KillerVamp09:
How exactly can I root this on 5.1? I used the last methods with the SU zip but it's not exactly working.
[Samsung Galaxy Nexus] MWisBest:
Great news: Fixed offline charging. :) Will be in the next build for sure.

What recovery are you using? The GApps package uses info in the recovery to determine which version of Google Play Services to install. What you're describing sounds like it had to use the older generic Play Services (because it didn't determine the newer specific one was compatible), and until it gets updated (should happen on its own?, trying to open the Play Store may speed along that process, or it may need to be updated through the Play Store somehow...) those apps may FC like that.

Not sure what's up with YouTube for you, the v2 build is working just dandy with it for me.

There's an improvement for handoffs I have to merge still, should be in the next build.

Browser settings crash is a known issue with AOSP for quite some time now, I haven't bothered to fix it yet. I will look into what's up with the Messaging app.

Thanks!

I'll be getting an N6 eventually at some point too, however I will continue my work on the Galaxy Nexus for a long time, regardless of whether or not I upgrade to something else.

Busybox and Superuser should be ready for the next build.

Installing the latest version of SuperSU via recovery (2.46 I think?) should work.
[Samsung Galaxy Nexus] cowsquad:
Off topic. I just played with the nexus 6 today at att&t and I didn't like the huge phone :+(
[Samsung Galaxy Nexus] RW-1:
Mw, response much appreciated, but my utube issue resolved itself, it was weird though, I'm good to go.

Looking forward to your next build release to carry me to the N6 :)

(for those who may not know, I've been on my GNex as my only phone since release, it's time for new HW like I was saying, but the GNex will more than likely make me retire my OG Droid from the Bedroom, where it had faithfully serves as a clock/radio since I acquired the GNex ....)

Awesome work, as always.

QS, I know, it's huge, but it grows on you, I'll still be playing with the N6 for at least an hour in store before making that decision, though I'm kidding myself, I'll be getting it :)
[Samsung Galaxy Nexus] pkgnex:
That's what she said!

(sorry, had to)
[Samsung Galaxy Nexus] cell2011:
I have an att htc one m7 how come noone can get 5.1 build out but youve been able to this for Gnex? Is this all pretty easy jjust use N6 dump and files? I see someone did this for the N4 too already
[Samsung Galaxy Nexus] RW-1:
Because we're not waiting for HW sources for that phone most likely, while 5.1 has dropped into AOSP, your dev cant compile until they have HW sources (I'm just being general overall).

The GNex is done as far as sources are concerned, but we already have what we need to port it and compile a ROM.

If I'm incorrect in this conjecture, someone will come in and correct me ...

PKGNEX :)
[Samsung Galaxy Nexus] cell2011:
Yea reason i asked cause it looks like 5.1 can be done by taken from N6 files or N5. I have a hd kindle 7 someone has done omni rom 5.1 on and its great smooth with latest micro gapps
[Samsung Galaxy Nexus] RW-1:
Yeah, you can do 5.1 now, AOSP has it, but you have to have specific files for the specific device HW to complete it. Did anyone have a 5.0 at all for it? If so they should be able to re-compile for 5.1...
[Samsung Galaxy Nexus] cell2011:
Yes if you went to one development youll see 5.0 5.0.1 and 5.0.2 roms all the ones from beanstalk to eurphoria etc. But no 5.1 yet im sure its being worked on
[Samsung Galaxy Nexus] jcpowell:
[MENTION=3390093]MWisBest[/MENTION] running great! I'm so much appreciative of your work. I was forced to use my Gnex after dropping my M8 from atop a cell phone tower (2nd time the first was my DNA) and I've actually been very happy to use this phone because of you. Not sure how long I'll be on it as my daily it looks indefinitely so far so I'll be staying on on top of your build.
[Samsung Galaxy Nexus] RW-1:
A tower dog! Nice! I have a few friends that do that work...

Cell2011, more than likely they are then ...
[Samsung Galaxy Nexus] jcpowell:
I love it!
[Samsung Galaxy Nexus] RW-1:
Here's a question ... ok, the VZAPN APK in /system on the N6 that has the whole freaking internet in a frackus. I'm sure with root one could delete these <sarcasm>precious Kb's of RAM,/sarcasm> ....

But relating to the data issues we've (or I've) had with the GNex on VZ since KK (handoffs taking up to 30 seconds, or not going back to 3G at all, etc.), would the inclusion of the VZAPN apk they are talking about assist us? I know half of our issue was no new radios since KK, and I suppose APN's are handled differently in the AOSP build of 5.1.

But heck, if you don't ask, you don't learn :)
[Samsung Galaxy Nexus] christianpeso:
Fantastic to see 5.1 so soon. Thank you!

Is the 5.1 ROM F2FS compatible?

EDIT:

Yes it is!

Did a complete Wipe of everything. Installed 5.1v2, the new beta GAPPS 5.1 from PA, http://xdaforums.com/showpost.php?p=59403724&postcount=2445

and R11 kernel from BSmitty. Booting up now and optimizing apps.