[Samsung Galaxy Nexus] MWisBest:
I don't think PA has a 5.1 GApps package out yet. They won't let you flash a 5.0 package onto a 5.1 ROM. Difference between the GApps package I uploaded and the PA 5.0 micro package?:

- Change required Android version to 5.1 instead of 5.0

- Removed versions of Play Services that aren't flashed on the Galaxy Nexus, to cut down on the zip size.

- Few small differences in the flashing script.

You can make this micro GApps package flash as if it's a pico package if you want though! See this post for information regarding that: http://xdaforums.com/showpost.php?p=56832806&postcount=4

First I've read of this! Will have to check into that, thanks for the report.

Congratulations then!

Personally, I don't like using a kernel and various other things that are years out of date, which last I checked was over 1,000 commits to the kernel alone, plus hundreds more to domx and camera and hwc and... well, you get the idea! I should tally up all the lines of code that were changed. If I remember correctly, HWC alone grew from ~2000 lines of code to not that far off of ~3000 lines of code, and it's not simply stuff being added, it's bug fixes and old cruft removed as well.

Carlos's view on these changes is that they're "hacky" and "buggy", but these new things are mostly straight from Texas Instruments, who not only authored the majority of the old stuff he's using, but designed the hardware platform (SoC, among other things) that powers the Galaxy Nexus. They know how their chips work better than pretty much anybody. The majority of the chips you'll see labeled (and some that aren't labeled) on a Galaxy Nexus motherboard? Texas Instruments. Google/Samsung threw a few curveballs at us that we've had to make a few changes to the new stuff to adapt to, and this is where some of these small issues come from; however, any bugs introduced by the new stuff far outnumbers the bugs it fixes that you just aren't seeing, and with people like the above posters letting me know of these issues, they can actually get fixed! Heck, thanks to [MENTION=3457922]stargo[/MENTION] and [MENTION=2633638]Ziyan[/MENTION] we're no longer using a single closed-source executable binary, just libs; most notably, Dreams continues to use the closed-source fRom instead of the open-source replacement from Ziyan, dumpdcc. fRom was (well, "is" for Dreams) the binary responsible for getting the camera calibration data that was causing those white balance issues FML had a while back, Ziyan was able to reverse-engineer it and write the open-source dumpdcc to replace it, which FML has been using for quite a while now. Both binaries complete the same task, however the fRom binary is somehow 10 times the size of dumpdcc (suspicious much?), and fRom even requires a patch to "linker" to run which introduces a (very slight...) security risk, and that patch won't keep working forever (that's why fRom wasn't working on FML 5.0 for a while, I didn't feel the patch's risk was worth it). If that isn't "buggy" and "hacky", I don't know what is. (NOTE: The main reason I'm bringing up fRom is to get Carlos to patch up that potential security issue. I know people are using his ROM, and that's OK, to each their own, but this is something that would be irresponsible of me or any other person who's aware of it to overlook.)

The new work done for the Galaxy Nexus here in FML and in other ROMs is what's going to keep the Galaxy Nexus running new Android versions for quite some time yet.

TL;DR: We can either be prepared for the future now, or we can hit a roadblock later and be stuck on an old version of Android. Up to you!

NOTICE: This is as tame as I could write this rant. I honestly have a lot more I'd like to say about Carlos, but I'm not going to let how I feel about him control what I write here. I pride myself in acting professional and respectful here, to

everybody

. As some other people have alluded to, the "OMAP4XXX collective" of sorts with many of us devs working together once included Carlos, but he left due to a "my way or the highway" attitude. We tried to reinvite him to the Hangout on G+, and he joined again, but then left just a couple days later due to the same stubborn, angry attitude. I think anybody can understand how that's upsetting, and understand that I am really trying hard to be professional here!