• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][5.0.2/LRX22G][AOSP][LINARO/OPTIMIZED] FML: Fork My Life (2015/01/08)

Search This thread

MWisBest

Inactive Recognized Developer
Dec 26, 2010
934
5,816
Green Bay, WI
github.com
[#Intro]
Oh, and now there's these Lollipops I'm handing out. They are free as always, and they are very very delicious.


[#Why]


[#Info]

I need people testing and finding bugs if anything is going to be fixed. I might not have the Bluetooth devices you have, I might not use the camera as much as you, I might not use mobile data as much as you; you get the idea. :)
NOTE: FML is built and tested on the Verizon Galaxy Nexus variant, also known as toro. The GSM Galaxy Nexus variant (the one pertaining to the forum section you're currently in), also known as maguro, is extremely similar in hardware to the Verizon Galaxy Nexus, however I'm not able to test these builds personally. There aren't any code changes between builds for toro and maguro so that I know there shouldn't be any huge issues, but things specific to maguro I'll need feedback on to make sure they're working OK.


[#HowTo]


Latest Build
KitKat/ROM Stable: omni-4.4.4-20140705-maguro-FML.zip (159.07 MB)
KitKat/TWRP Stable: fml-twrp-2.7.1.0-20140705-maguro.img (8.58 MB)
KitKat/ROM Beta: omni-4.4.4-20141015-maguro-FML.zip (160.13 MB)
KitKat/ROM Beta Hotfix: boot.img (4.83MB)
Hotfix Info: The latest beta had a bug on maguro causing the radio to be a jerk and not work. Flashing this boot.img will resolve that issue. If you'd rather not flash it with fastboot like is normally done for .img files, you can use the Flashify app for it, or you can open up the ROM zip and replace the boot.img in there with the hotfix.
Lollipop/ROM Beta: FML-AOSP-5.0-20150108-maguro.zip (194.45 MB)

LOLLIPOP INFO:
USE THESE GAPPS: FML-GApps-5.0.x-20150101-tuna.zip (167.81 MB)
They are based on PA's GApps, huge thank you to them!
Known Issues:
- Camera can be a little touchy, but it generally works.
- Long SMS messages fail to send, fix is on-the-way though.
Lollipop Changelogs can be found in the post below!

(KitKat) BETA INFO:
Beta builds are using updated GPU drivers (and an updated kernel to go with them) courtesy of @Ziyan, as well as being up to date with the latest stuff from OmniROM. NOTE: YOU CANNOT FLASH A DIFFERENT KERNEL WITH THESE BUILDS.
Currently broken with the new GPU drivers:
- Hardware Video Decoding FIXED 2014/10/06
- Hardware Video Encoding(?) FIXED 2014/10/08
- Camera (PARTIALLY) FIXED 2014/10/08
- The stock camera app (as well as Google Camera) has this weird quirk of crashing when pressing the shutter button to take a picture, however many different camera apps on the Play Store (in particular Camera ZOOM FX) work flawlessly. Video recording is generally OK, however I've been getting some reports of the audio and video being a little out of sync, so your mileage may vary...
See the Changelog post below for..... well..... changelogs.


[#GApps]


Known Issues
- The screenrecord command does not work directly, however it does work via the Power menu.
- There can be a slight (noticeable, but not huge) delay when pressing the Recents or Home button.


[#Thanks]


[#Donations]

XDA:DevDB Information
FML: Fork My Life, ROM for the Samsung Galaxy Nexus

Contributors
MWisBest
Source Code: https://github.com/MWisBest/

ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP

Version Information
Status: Beta
Stable Release Date: 2014-07-05
Beta Release Date: 2015-01-08

Created 2014-05-27
Last Updated 2015-01-08
 

Attachments

  • Screenshot_2014-05-26-16-57-43.png
    Screenshot_2014-05-26-16-57-43.png
    243.2 KB · Views: 181,307
  • Screenshot_2014-05-26-17-07-41.png
    Screenshot_2014-05-26-17-07-41.png
    76.5 KB · Views: 178,877
  • Screenshot_2014-05-26-17-08-20.png
    Screenshot_2014-05-26-17-08-20.png
    68.5 KB · Views: 170,888
  • Screenshot_2014-05-26-17-08-29.png
    Screenshot_2014-05-26-17-08-29.png
    81.5 KB · Views: 167,346
  • Screenshot_2014-05-26-17-08-38.png
    Screenshot_2014-05-26-17-08-38.png
    79.8 KB · Views: 165,397
  • Screenshot_2014-05-26-17-09-04.png
    Screenshot_2014-05-26-17-09-04.png
    97.9 KB · Views: 167,852
  • Screenshot_2014-11-06-01-39-55.png
    Screenshot_2014-11-06-01-39-55.png
    90.4 KB · Views: 163,400

MWisBest

Inactive Recognized Developer
Dec 26, 2010
934
5,816
Green Bay, WI
github.com
Changelog, News, Etc.

Lollipop Beta Changelogs:
2015/01/08
- Updated the camera HAL.
This is going to be a little... fragile, at first, but in the long run it's needed. Stock camera app saves pictures now at least.
You may also notice that there's a 5.1MP resolution now (clear your camera app's data if you don't see it), despite our camera supposedly being 5.0MP all these years. Turns out the sensor's native resolution is indeed a whopping 16 pixels taller and 16 pixels wider than we've been using.

2015/01/04
- Added back some of the classic FML optimizations and more.
Built with -fstrict-aliasing flag, C++11, and the Linaro GCC 4.9 toolchain.
- Updated to AOSP "android-5.0.2_r1" tag.
As usual, the only real change was them bumping the version number.
- Improved flashing.
The speed of flashing the ROM zip is now much faster.
- Superuser is now built-in.
There's no need to flash SuperSU. You can find Superuser in the Settings app. You may have to enable the "Development Settings" menu to see it.
Some apps are a little sketchy with this Superuser though, most notably Titanium Backup. If you have issues, try flashing SuperSU.
- Video playback should be fixed.
YouTube in particular seems OK. If you have some weird format you're playing back locally I cannot make any guarantees though.
- The camera situation has improved and also regressed.
The stock camera is kinda back to the point of where it was with the KitKat Beta builds:
---- Preview works. Saving photos does not work. Video recording kinda works.
--- However:
---- The camera calibration is a little messed up. Long story, but it'll be fixed soon. So your white balance may look kinda funky, among other things.
- Audio quality is improved, with support for 192kHz FLAC as well.
This is possible thanks to a new audio resampler, which doesn't impose the same sample rate restrictions of the stock Android ones. It also has far better quality than the stock Android resamplers.
- WiiMotes can now be paired via Bluetooth.
I used to be a bit of a Wii hacking enthusiast... I think I still need to add some more stuff to make it useable as a gamepad or something, but yeah.
- Fixed location services issues.
- (toro) Fixed switching between 4G/LTE and 3G/CDMA network settings.
- Kernel changes:
Reclaimed 38MB of RAM from the carveout stuff.
Removed HDMI's framebuffer, saving an additional ~16MB of RAM. With Lollipop, MHL/HDMI out isn't working with our old HWComposer, so might as well save some RAM in the mean time.
Added overclocking support, as well as adjusted the stock frequencies a little.
Added the GPU kernel driver back into the kernel, rather than building it as a separate module.
Switched to LZO compression for the kernel. It results in a slightly larger size to the kernel, but it boots faster.
Added the "purple tint fix".
Added compiler flag to tune code for Cortex-A9 CPU.
Built with Linaro GCC 4.9 toolchain.
(v3): Fixed VYL00M eMMC bootlooping.

Older Builds:
2014/11/16
- Fixed the RIL.
There were a few things that went into this, and I can't really take much credit for it other than being persistent in trying to fix it.
1. rild needed a little fix-up to somewhat return it to pre-Lollipop form. Basically Google is forcing Qualcomm's junk upon the world. @dhiru1602 pointed me in the direction of some commits from rmcc to hardware/ril that fixed this part of the problem.
2. The kernel needed a commit to support some new junk related to networking in Lollipop. @Ziyan linked me to the change in question.
- Updated to AOSP "android-5.0.0_r6" tag.
Really the only change is that the build number is bumped to LRX21T.
- Switched out a couple small proprietary binaries with a reverse-engineered open-source version.
Thanks to @stargo who has really been killin' it for the Motorola OMAP devices recently, we now have a reverse-engineered pvrsrvinit binary (the executable that fires up the GPU drivers on boot-up). This is especially important because the proprietary pvrsrvinit wasn't compiled as PIE (position-independent executable). With Lollipop, they're forcing everything to be PIE, which is good because PIE is better from a security stand-point. Previously I had been adding a workaround to enable support for non-PIE, which I now don't need.
- Built the ROM with "WITH_DEXPREOPT" set to true.
This basically just adds the ".odex" files to /system. With ART this is important because it cuts down on those lengthy boot-up times because instead of compiling the apps' code on the device, it now compiles it on my computer when I build the ROM instead.
- Changed the "Android is upgrading..." screen to prevent burn-in.
Rather than use Lollipop's eye-hurting bright white theme on this screen, I've switched it back to the classic, darker theme.

2014/11/09
- Switched back to the old OTA package format.
With Lollipop they're now, by default, flashing something similar to a system.img. I switched back to the old format. THIS IS CAUSING VERY LENGTHY FLASH TIMES NOW HOWEVER, I HOPE TO FIX THESE SOON.
- Changed the kernel to build with GCC 4.7.
With Lollipop, Google switched to GCC 4.8. GCC 4.8 has never been kind to the Galaxy Nexus kernel, I'm surprised it was booting at all in the first place... or not, for some people. I'm fairly confident this should fix the VYL00M eMMC issue.
- Added "Ambient Display".
Apparently I need to add a "pick-up" or "significant motion" sensor for it though, so it displays something when the phone is picked up.
- Fixed chromium crashing.
This fixes Browser crashing upon open, among other things. This fix has been in chromium itself for nearly 4 months now, I don't know what the heck Google is doing to AOSP to make it so FUBAR lately...
- Fixed lag in Recents menu.
Now it's smoother than KitKat's, in my opinion.
- Added back F2FS support.
F2FS is now supported again, HOWEVER, it is NOT supported on the /system partition. It really didn't do any good for /system anyway.
- Updated various icons.
The Dialer icon in particular was bothering me. Other things that aren't visible in the launcher, e.g. SettingsProvider, have been fixed as well.
- Fixed FLAC playback, among other media decoding issues.
Just needed a sync-up in the device tree with one thing that I think Google DID do a nice job of with Lollipop actually.


KitKat Beta Changelogs:
2014/10/15
- Cleaned up the kernel.
Ziyan went over all his work not long ago and cleaned up the commit history and whatnot. He's letting me do the task of merging in the GPU driver stuff, so I'm currently just getting the kernel to a "clean slate" of sorts for other kernel devs to fork and build off of. Basically this should hopefully be the new "stock" or "Google" kernel. As a result, there's some bells and whistles missing from this build. It does however include some new audio updates that weren't in the previous kernel, which leads me to this...
- Changed audio sampling rate to 48kHz.
Previously the sampling rate has been 44.1kHz. The Galaxy Nexus supports 48kHz though! Here's what mainly sparked this change: since KitKat, the UI audio effects (e.x. touch sounds) have been switching over to 48kHz. With the Galaxy Nexus still using 44.1kHz, UI sound playback became kinda sluggish, and this was a big contributor to it. The UI sounds use the "fast track" audio path (where it tries to do as little processing as it can to the audio in order to play it with a minimum amount of latency), however a requirement of using this is that no resampling (e.g. converting 48kHz to 44.1kHz, like it has been doing currently with KitKat) can be required on the audio being played. Therefore the UI sounds were taking the "deep buffer" audio path, which has a delay to it. In switching to 48kHz, the "fast track" path is actually even faster now than it has ever been previously, and the Galaxy Nexus was already TOP OF THE LINE when it comes to audio latency believe it or not!
Another thing about this is that there is now support for playback of 96kHz audio files.
- Some updates to the camera HAL.
This hasn't fixed the situation of stock and stock-based camera apps crashing when taking a picture, but it's a start on it though.

NOTICE: Poweramp (and probably most other media players that use their own native code for audio playback rather than straight-up using the built-in Android APIs) is being pissy about the sampling rate change. If you experience issues with music playing, especially things like popping or crackling, please try Play Music or Apollo and see if your issue is still present. I know the UIs for Play Music and Apollo are pretty awful, but I can't write my own media player because I'm dealing with this camera stuff! :(

KitKat Stable Changelogs:
2014/07/05 (Operation: Streamline)
ROM: Synced with OmniROM's latest changes as of around 6:30 AM 2014/07/05 UTC.
ROM/Build: Fully updated to AOSP 4.4.4 (specifically, the android-4.4.4_r1 tag), which really doesn't change much though...
ROM/Build: Stopped including the unused (as far as I can tell) dock.png in /system/vendor/res/images/dock/
ROM/Build: Leveraged a feature added to updater-script creation by OmniROM which coincidentally makes the ROM flashable on any format of /system partition, beit F2FS, EXT4, exFAT, whatever.
ROM/Build: Stopped including Voice Dialer. Voice Dialer is just an unpolished piece of junk which really isn't used ever since Google Now.
ROM/Build: Stopped including 0xBenchmark.
ROM/Core: A number of changes added for completely seamless and simultaneous F2FS and EXT4 support.
ROM/General: Switched to the Android KitKat boot animation, which takes up nearly 4MB less space than OmniROM's boot animation.
ROM/General: Used OptiPNG heavily on numerous things in an effort to save space.
ROM/Kernel: Added F2FS support, nearly 500 commits were merged in for this.
ROM/Kernel: Relaxed BIGMEM a bit to hopefully fix Camera crashing for some users. (Only a 4MB difference BTW)
ROM/Kernel: Optimized CPU L2 cache settings slightly.
TWRP: Added support for seamless and simultaneous F2FS and EXT4.

I'm forgetting a number of things and I'm not going into as much detail on some of this as I'd like to. Frankly, I'm exhausted. Maybe I'll expand on this tomorrow. Maybe.
Oh I also submitted 8 things to the OmniROM Gerrit. One has been merged so far, the others probably will probably be merged in the next day or two.


Older Builds:
2014/06/05 v2 (Operation: Chocoholic)
ROM: Synced with OmniROM's latest changes as of around 10:00 PM 2014/06/05 UTC.

V2 just fixes a bug where Dialer would crash upon entering the Call Log.

2014/06/05 (Operation: Chocoholic)
ROM: Synced with OmniROM's latest changes as of around 7:00 AM 2014/06/05 UTC.
ROM: Fully updated to AOSP 4.4.3 (specifically, the android-4.4.3_r1.1 tag).
ROM/Build: Removed some duplicate alarm and notification sounds in my never-ending effort to slim down the build size.
ROM/General: A few things were added to accommodate building for the Kindle Fire HD 7" that might spill over into the Galaxy Nexus builds (no harm, if anything an improvement).

Wanted to get an Android 4.4.3 build out ASAP, so this build doesn't have much in terms of changes/fixes from myself. This weekend I'll be going on vacation, and after I get back I'm planning on adding F2FS support finally. :good:
BTW, you might want to make sure you have the 4.4.3 GApps.

2014/05/31 (Operation: Jackpot)
ROM: Synced with OmniROM's latest changes as of around 11:30 PM 2014/05/31 UTC.
ROM/ART: Pulled in some things from AOSP's master branch to hopefully decrease initial boot-up time for ART.
ROM/Build: Fixed some more instances of code being compiled/optimized for a generic ARM CPU instead of the Cortex-A9 specifically.
ROM/Build: Included some requested translations.
ROM/Build: Found a fix by PrimeDirective to build frameworks/base/core with -fstrict-aliasing.
ROM/Dalvik: Pulled in some things from AOSP's master branch to increase overall speed for Dalvik.
ROM/General: Fixed a bug where overclocking would revert when the screen was turned off.
ROM/General: Added battery charging LED support.
ROM/General: Fixed notification LED flash interval being way too long by default.
ROM/General: Experimental improvements for GPS. (See: GitHub Commit)
ROM/Kernel: Added the "purple tint fix" commit.
ROM/Settings: Fixed Settings not being translated.

Quite the changelog here! ART is feeling a little snappier in this build but Dalvik might still be faster! :eek:

2014/05/26 (Operation: Maguro)
ROM: Initial maguro build.

After the great number of improvements I made in the most recent build I did for toro, I figured it was perfect timing to get maguro up and running.
If you'd like to have a look at the toro stuff, it's here: http://forum.xda-developers.com/devdb/project/?id=1098
Let me know if there's any issues!

To-Do.
Slim down the build by putting less used stock applications into a separate flashable .zip, such as Browser.


Experiments I'm Looking Into
Creating Black Holes with my phone's ridiculously awesome speed.
 
Last edited:

MWisBest

Inactive Recognized Developer
Dec 26, 2010
934
5,816
Green Bay, WI
github.com
Developer Info
This is a little section I'm gonna set up explaining things in more technicalish and "down-and-dirty" details of sorts for developers interested in this project and potentially incorporating it into their projects.

The only thing I ask is to make a little "Thank You" section in your main post like I have here and credit at least me and Linaro, and also credit anybody else's work I have used if you use it as well. I'd also appreciate it if you could maybe link my name to this thread or my user profile here on XDA, but that part isn't a requirement.


All of my work can be found on my GitHub. Please note that any commits on my GitHub that are after the most recent build of FML should be considered experimental and potentially not working at all. I develop on the fly and often times things on my GitHub aren't finished and fully tested unless they have made their way into an official build of FML.
Please pay no attention to where it says a repository was forked from. Often times I'll have forks that I just re-use to avoid duplicate and unnecessary extra repos. For example, in repos forked from CyanogenMod you might notice the default branch is actually something like "omni-4.4" indicating that branch is based from OmniROM and not CyanogenMod.
The best place to keep track of what parts of the Android source code that needs patches is the manifest.


All About Strict Aliasing!
One of the big things Linaro does with improving Android's performance is fixing violations of what's known as "the strict aliasing rule."
A pointer is said to alias another pointer when they both refer to the same location of memory. This is OK and not an uncommon thing to do. The strict aliasing rule is that pointers of different types should never refer to the same location of memory (aka alias each other). Things like this are just fine and dandy:
Code:
void pointlessFunction( uint32_t foo )
{
    uint32_t* const bar = (uint32_t*)&foo;
}
That's alright, as foo and bar are the same type. Note that it's also OK if the only difference between foo and bar is signedness (e.x. uint32_t and int32_t).
Now this...
Code:
void anotherPointlessFunction( uint32_t foo )
{
    uint16_t* const bar = (uint16_t*)&foo;
}
...this is a problem. foo and bar are NOT the same type. This is a violation of strict aliasing.
Strict aliasing allows a compiler to make some assumptions when compiling and optimizing code that it otherwise couldn't. This is a good read about the benefits of it.
Here's a few examples of fixing strict aliasing violations:
DSPManager
frameworks/av
bionic
Note that not everything is fixable, or worth fixing. Sometimes you'll just have to add -fno-strict-aliasing to the problematic section and call it a day:
frameworks/base


Of Unicorns and Compilers...
This section will delve into compilers and flags for them. The "Of Unicorns" part is in reference to the amount of false information, misconceptions, and mythical beliefs regarding these things. One thing in particular is the common belief that throwing every flag possible at the compiler results in better/faster binaries. That couldn't be further from the truth, and is something that actually took me quite some time to properly understand myself (in part because the misconceptions are more common than the actual truth!). In this section I will mainly be referencing the GCC compiler, as that's what is currently used for the majority of Android and most Linux systems as a whole. The other compiler that is making quite a run at GCC is Clang, so first I will talk about GCC vs Clang quickly:

GCC vs. Clang
GCC is currently (~May 2014) the most common compiler used for Linux and Linux-based systems (which includes Android). GCC was first released in 1987, as the "GNU C Compiler." Not long after its release, it was extended to support C++ as well, and over time many different languages and platforms became supported by GCC so it is now called the "GNU Compiler Collection." Over all this time, GCC became more and more difficult to maintain. As time passes on, fewer and fewer people have been able to get their foot in the door to work on GCC as it just became so... bloated.
Eventually, somebody finally got the guts (or resources, rather) to take on GCC and make a competing compiler. Clang was born.
Clang is a front-end for LLVM. Initially, LLVM was going to make use of GCC's front-end for making a C/C++/etc. compiler using LLVM's back-end, however this was just too cumbersome of a task due to GCC's difficult-to-work-with codebase, which was what sparked Clang instead.
Fun fact: Clang 1.0 was released in 2009. It was first open-sourced in 2007. That's 20 years after GCC's inception, but yet Clang has managed to tear GCC's usage apart. However to be fair, LLVM's initial release was 2003, but that's still a decade and a half head-start given to GCC!

As of GCC 4.8 vs. LLVM/Clang 3.4, it's kind of a toss-up between the two. In some cases GCC has better binary results and in other cases Clang has better binary results, however Clang outshines GCC in areas other than the resulting compiled code:
1. Clang is faster and uses fewer resources than GCC when compiling. It's usually a safe bet that Clang is going to be at least 50% (1.5x) faster than GCC when compiling, whilst also somehow using less RAM and disk space than GCC. For those of you that like being eco-friendly, just imagine the amount of energy this saves!
2. Clang has generally been ahead-of-the-game when it comes to supporting C++ standards. Current example: Clang has been C++14 feature-complete since the end of 2013, while GCC (even in 4.9!) is not.

Thanks to the competition from Clang, GCC has also been stepping up its game as well too. All-in-all this has been a win-win for everybody so far.


Flags.
Aaand here we go on compiler flags. For this I'll be referencing the GCC documentation on "GCC command options", here: https://gcc.gnu.org/onlinedocs/gcc/index.html#toc_Invoking-GCC
Of particular interest in this section will be "Options That Control Optimization", but other sections are often overlooked which can be of use, I'll explain those later though.

The first thing you'll see in the "Options That Control Optimization" section are the -O options. These are general optimization levels that give you a sensible default to work with.
First off is -O0. This is the default, and doesn't turn on any optimization options. This is generally only used for debugging code, as some optimizations can interfere with that.
Next would be -O1. This enables some optimizations to reduce code size and improve speed, without increasing the time it takes to compile code significantly.
After that is -O2. This is what is generally used for most program compiling, as it enables plenty of optimizations and these ones generally don't cause problems/bugs with the resulting binaries whilst greatly improving speed.
Then there are some non-numbered ones which I'll go over:
-Os is somewhere between -O1 and -O2. It enables most of -O2's options, but disables some that can increase the size of the resulting binaries. This can be of great use when dealing with smaller embedded systems where space is generally preferred over speed. It's closer to -O2 than -O1...
-Og is useful for debugging purposes. It enables a few optimizations that generally don't effect ability to debug code, so devs don't have to deal with the slowness of -O0 as much as usual.
And then there's the almighty -O3...
-O3 enables some extra optimizations that -O2 does not. The drawbacks are increased compile time, increased binary size, and the possibility for some bugs. In many cases, -O3 might not improve speed over -O2 whatsoever. In other cases it can be helpful, but it is nothing compared to the differences between -O1 and -O2.
Android generally uses -O2 by default. It's safe and fast enough for most cases. -Os is also used for any Thumb instruction-set code for ARM, as Thumb is generally meant for reduced size and complexity from what I can tell.
There's also a flag kinda above -O3, which is -Ofast. The problem with -Ofast is that it can cause huge problems for any code that makes the (correct!) assumption about some math stuff, so it is generally avoided.

Then there are some flags that aren't enabled by any optimization level. This is not without reason: these flags are, generally, useless. They increase compile time by a ridiculous amount, and their effects on the resulting binaries might be absolutely nothing. Zilch. Nadda. Even for something as large as Android, these flags can still do nothing. If these flags can have a speed-up, it's generally not without risk, and they should be kept to specific use-cases rather than used on every single thing.
These flags can be considered about the equivalent of using the "placebo" profile for h264 video encoding. It has a less-than 1% improvement in the resulting quality, yet can take twice as long to render (or, in this case, compile). And they are pretty much exactly what the placebo profile for h264 encoding is, a placebo effect. You will not find a measurable increase in speed, and the risks associated with it are generally not worth it!

There is an exception to that though: -flto. This enables Link-Time Optimization, and can have huge impacts on both the speed of the binaries as well as even a reduction in their size! LTO can be viewed as this: when the compiler is truckin along compiling things, it generally only sees bits and pieces of the project at hand. LTO allows the compiler to view how everything works together rather than just each individual part, and in doing so it can find HUGE improvements! When LTO was in its infancy with GCC, it was pretty unstable, but with GCC 4.8 and above it can be used reliably. It's also advised to use the -fuse-linker-plugin flag when using LTO as well (read the docs on that).
Here is my work on using LTO with Android, it's more involved than simply adding it with all the other flags which is why you'll generally hear the people that are making use of the "unicorn flags" say it doesn't work...
https://github.com/MWisBest/android_build/commit/c1b041c32572b6ee1bbb17b1fa8c038c5e9fde1f
https://github.com/MWisBest/android_build/commit/95bb49b613424b70af3e820748724fb92ef35b5e
https://github.com/MWisBest/android_build/commit/d2c13f1c35cfa9c114a69c74cfb1c2631643eebc
Ignore the things in the last couple commits there that aren't related to LTO...
But like I said, it's more involved than just throwing the flags blindly at the compiler, there are a few other fixes required to get a successful build with LTO:
https://github.com/MWisBest/android_bionic/commit/3b3f59a173a7cc4ff3a1cec4456a99108ce08092
And then it also has to be disabled in ART, that fix courtesy of @metalspring : https://github.com/MWisBest/android_art/commit/9ed3774fcba75077e098720406d261b79bd9baa9

// To be continued.



Small but Helpful Things
I thought I'd put some simple little things here that can be immensely helpful to devs. Most of these they'll probably know already, but some won't and when I learned these things they had a profound impact on development. At the very least it can be a helpful reminder/reference sort of thing.
Properly Logging Builds
This is something I finally figured out not long ago that has had a huge impact on debugging problems...
I'm not all that great with bash but I generally understood redirecting the output of a program to a file. However, when I tried the usual:
Code:
make -jX otapackage > buildlog.txt
, not everything was going to the file. Eventually I learned that just using ">" only redirects stdout, and not stderr which was where all the warnings and errors went to. To get around that, there's a couple options. One, you can redirect stdout and stderr to separate files, like so:
Code:
make -jX otapackage 1> buildstdout.txt 2> buildstderr.txt
, or the other option is to just lump them all into a single file using:
Code:
make -jX otapackage > buildlog.txt 2>&1


This post is a WIP...
 
Last edited:

MWisBest

Inactive Recognized Developer
Dec 26, 2010
934
5,816
Green Bay, WI
github.com
As you may or may not have read in the OP, this ROM was built and tested on the Verizon Galaxy Nexus only for about 9 months. I don't own a GSM Galaxy Nexus, so I'm not able to fully test these GSM builds, however the differences between the two are minimal and everything should work OK.

As the Verizon Galaxy Nexus is pretty much only in the USA, one thing I did to reduce the size of the ROM was to cut back on some of the translations. I've kept what I thought were fairly common languages (including outside the USA). Since I've now expanded to the GSM Galaxy Nexus, which is more international, there's a chance that a language you need might be missing. Please just let me know what you need and I'll be more than happy to include it.
 
Last edited:

pvkiniyan95

Senior Member
Jun 21, 2012
669
429
Chennai
Downloading....perfect timing...i am rom hopping for a while and excited to try this, skimmed last few pages of your toro thread :good:
why not take a look at the recent thumb flag optimisation commits that claimed 6x speeds recently...
 
Last edited:
  • Like
Reactions: MWisBest

qtoo941

Senior Member
Jun 27, 2013
681
180
Sofia
You have written that you have built CM 10.2 FML version. Is it compatible with maguro? Where can I find it and flash it over my phone just to see it?
 
  • Like
Reactions: aljwad68

MWisBest

Inactive Recognized Developer
Dec 26, 2010
934
5,816
Green Bay, WI
github.com
Downloading....perfect timing...i am rom hopping for a while and excited to try this, skimmed last few pages of your toro thread :good:
why not take a look at the recent thumb flag optimisation commits that claimed 6x speeds recently...

Yeah I replied to that thread... it's bogus, unsafe, and unprofessional. FML was far beyond that stuff since its inception and it has only gotten better since.


You have written that you have built CM 10.2 FML version. Is it compatible with maguro? Where can I find it and flash it over my phone just to see it?

This right here is the first build I've done that's maguro compatible, and there's been lots of improvements since when this ROM was based off of CM so even if it'd work on maguro it's not really worth trying at this point. Sorry!
 

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
14,855
33,594
Halifax
GT-i9250
Nexus 7 (2013)
Downloading!
What do you recommend guys, Dalvik or ART?
I've been always using ART before and then I read replies in toro thread, most likely chooses Dalvik eh?

Thank you :)

Only ART! :) Feel the smoothness :)

Dalvik! MWis pimped it the **** out! :D

I'm extremely impressed with ART and I know it's Android's future. They will not be including Dalvik in 4.5 based on what I'm seeing in AOSP's master branch currently. I don't think ART will be the default in 4.4.3, there's a number of changes they'd need for that to happen and at this point in 4.4's lifecycle I think it's too late for a major change such as that, but 4.5 and onwards it will be the go-to thing yes.

I'm also extremely happy with how fast Dalvik is in this last build though... here's my observations on it:
Going from a previous build to the new build (after running Dalvik on both), it feels as if I switched from Dalvik to ART but with a 10x faster bootup due to not going through all the ART compilation, not to mention the space saved over ART too.
After that experience, I think this whole ART thing might've been unnecessary or at least would've been delayed if Android wasn't compiled like it's the stone age.


Funny you mention the dalvik-cache thing, it's actually multi-threaded so it is indeed about a 2x speed improvement, nice observation. ;)
 
  • Like
Reactions: pianistaPL

pianistaPL

Senior Member
Feb 15, 2012
2,301
1,249
Poznań - Poland
Ok, end of speaking, phone charged, let's try this ROM! :D

Wysłane z mojego Galaxy Nexus przy użyciu Tapatalka
@MWisBest Can i let set DexOpt to /cache if i use Banks Core Gapps and i want change to ART?

---------- Post added at 03:29 PM ---------- Previous post was at 03:10 PM ----------

OK, i guess i can't, after boot with ART i get pernamently SystemUI FC :p So this is a good reason to try this super fast dalvik :)
 
Last edited:
  • Like
Reactions: pvkiniyan95

pvkiniyan95

Senior Member
Jun 21, 2012
669
429
Chennai
Ok, end of speaking, phone charged, let's try this ROM! :D

Wysłane z mojego Galaxy Nexus przy użyciu Tapatalka
@MWisBest Can i let set DexOpt to /cache if i use Banks Core Gapps and i want change to ART?

---------- Post added at 03:29 PM ---------- Previous post was at 03:10 PM ----------

OK, i guess i can't, after boot with ART i get pernamently SystemUI FC :p So this is a good reason to try this super fast dalvik :)

thanks for that...u saved my time
 

gautam_nexus

Senior Member
Jun 19, 2012
995
520
Dubai
gonna flash this B*tch tonite! the changelog looks impressive. one question though do i need to flash the twrp recovery in the OP as well before flashing the ROM. Thanks!
 
  • Like
Reactions: MWisBest

pianistaPL

Senior Member
Feb 15, 2012
2,301
1,249
Poznań - Poland
Very fast on dalvik but phone gets mini freeze when i tap recent apps button and when i tap home button (when i have some app opened)
I haven't recent apps buttom freeze/lag only when i am on home screen.
Wysłane z mojego Galaxy Nexus przy użyciu Tapatalka
 
Last edited:
  • Like
Reactions: MWisBest

MWisBest

Inactive Recognized Developer
Dec 26, 2010
934
5,816
Green Bay, WI
github.com
Downloading!
What do you recommend guys, Dalvik or ART?
I've been always using ART before and then I read replies in toro thread, most likely chooses Dalvik eh?

Thank you :)
Only ART! :) Feel the smoothness :)

Dalvik! MWis pimped it the **** out! :D
^What he said. At the very least give Dalvik a try.


Ok, end of speaking, phone charged, let's try this ROM! :D

Wysłane z mojego Galaxy Nexus przy użyciu Tapatalka
@MWisBest Can i let set DexOpt to /cache if i use Banks Core Gapps and i want change to ART?

---------- Post added at 03:29 PM ---------- Previous post was at 03:10 PM ----------

OK, i guess i can't, after boot with ART i get pernamently SystemUI FC :p So this is a good reason to try this super fast dalvik :)

That sounds like the issue you'd run into with a GApps package that's too large, if you want to use a GApps package that large with ART you'll have to disable the DexOpt to /cache thing before switching to ART.

thanks for that...u saved my time

See above.


gonna flash this B*tch tonite! the changelog looks impressive. one question though do i need to flash the twrp recovery in the OP as well before flashing the ROM. Thanks!

The recovery build is not required, I just figured I'd start uploading them as 1. It's built automatically, and 2. I use it myself.


Very fast on dalvik but phone gets mini freeze when i tap recent apps button and when i tap home button (when i have some app opened)
I haven't recent apps buttom freeze/lag only when i am on home screen.

I'll certainly have a look at that and see what's causing it. The Recents issue might be due to the code regarding if OmniSwitch should be opened instead of the usual Recents, as I'm not getting that lag with OmniSwitch enabled as Recents.


Hi MWisBest, could you please add Spanish language support for this ROM? I'm very impressed with your work, and I'd like to have it translated.

Thank you very much in advance!.

Crap! I do have Spanish included, but the furthest I had gone with testing that stuff was to simply make sure they were listed in "Settings --> Language & input --> Language", which does have Español listed, however I clicked on it now after your post and there are some things that are missing translations, most notably: Settings!!
The good news is that I recently figured out how to properly log my builds, and sure enough I've found some warnings about translations not being included, so I should be able to track down what's causing this and have it fixed for the next build.
 

pianistaPL

Senior Member
Feb 15, 2012
2,301
1,249
Poznań - Poland
^What he said. At the very least give Dalvik a try.




That sounds like the issue you'd run into with a GApps package that's too large, if you want to use a GApps package that large with ART you'll have to disable the DexOpt to /cache thing before switching to ART.



See above.




The recovery build is not required, I just figured I'd start uploading them as 1. It's built automatically, and 2. I use it myself.




I'll certainly have a look at that and see what's causing it. The Recents issue might be due to the code regarding if OmniSwitch should be opened instead of the usual Recents, as I'm not getting that lag with OmniSwitch enabled as Recents.




Crap! I do have Spanish included, but the furthest I had gone with testing that stuff was to simply make sure they were listed in "Settings --> Language & input --> Language", which does have Español listed, however I clicked on it now after your post and there are some things that are missing translations, most notably: Settings!!
The good news is that I recently figured out how to properly log my builds, and sure enough I've found some warnings about translations not being included, so I should be able to track down what's causing this and have it fixed for the next build.

Polish language doesn't have translated settings too :) So i'm waiting for new version, thanks :)
 
  • Like
Reactions: mosca_ and MWisBest

Top Liked Posts

  • There are no posts matching your filters.
  • 227
    [#Intro]
    Oh, and now there's these Lollipops I'm handing out. They are free as always, and they are very very delicious.


    [#Why]


    [#Info]

    I need people testing and finding bugs if anything is going to be fixed. I might not have the Bluetooth devices you have, I might not use the camera as much as you, I might not use mobile data as much as you; you get the idea. :)
    NOTE: FML is built and tested on the Verizon Galaxy Nexus variant, also known as toro. The GSM Galaxy Nexus variant (the one pertaining to the forum section you're currently in), also known as maguro, is extremely similar in hardware to the Verizon Galaxy Nexus, however I'm not able to test these builds personally. There aren't any code changes between builds for toro and maguro so that I know there shouldn't be any huge issues, but things specific to maguro I'll need feedback on to make sure they're working OK.


    [#HowTo]


    Latest Build
    KitKat/ROM Stable: omni-4.4.4-20140705-maguro-FML.zip (159.07 MB)
    KitKat/TWRP Stable: fml-twrp-2.7.1.0-20140705-maguro.img (8.58 MB)
    KitKat/ROM Beta: omni-4.4.4-20141015-maguro-FML.zip (160.13 MB)
    KitKat/ROM Beta Hotfix: boot.img (4.83MB)
    Hotfix Info: The latest beta had a bug on maguro causing the radio to be a jerk and not work. Flashing this boot.img will resolve that issue. If you'd rather not flash it with fastboot like is normally done for .img files, you can use the Flashify app for it, or you can open up the ROM zip and replace the boot.img in there with the hotfix.
    Lollipop/ROM Beta: FML-AOSP-5.0-20150108-maguro.zip (194.45 MB)

    LOLLIPOP INFO:
    USE THESE GAPPS: FML-GApps-5.0.x-20150101-tuna.zip (167.81 MB)
    They are based on PA's GApps, huge thank you to them!
    Known Issues:
    - Camera can be a little touchy, but it generally works.
    - Long SMS messages fail to send, fix is on-the-way though.
    Lollipop Changelogs can be found in the post below!

    (KitKat) BETA INFO:
    Beta builds are using updated GPU drivers (and an updated kernel to go with them) courtesy of @Ziyan, as well as being up to date with the latest stuff from OmniROM. NOTE: YOU CANNOT FLASH A DIFFERENT KERNEL WITH THESE BUILDS.
    Currently broken with the new GPU drivers:
    - Hardware Video Decoding FIXED 2014/10/06
    - Hardware Video Encoding(?) FIXED 2014/10/08
    - Camera (PARTIALLY) FIXED 2014/10/08
    - The stock camera app (as well as Google Camera) has this weird quirk of crashing when pressing the shutter button to take a picture, however many different camera apps on the Play Store (in particular Camera ZOOM FX) work flawlessly. Video recording is generally OK, however I've been getting some reports of the audio and video being a little out of sync, so your mileage may vary...
    See the Changelog post below for..... well..... changelogs.


    [#GApps]


    Known Issues
    - The screenrecord command does not work directly, however it does work via the Power menu.
    - There can be a slight (noticeable, but not huge) delay when pressing the Recents or Home button.


    [#Thanks]


    [#Donations]

    XDA:DevDB Information
    FML: Fork My Life, ROM for the Samsung Galaxy Nexus

    Contributors
    MWisBest
    Source Code: https://github.com/MWisBest/

    ROM OS Version: 5.0.x Lollipop
    ROM Kernel: Linux 3.0.x
    Based On: AOSP

    Version Information
    Status: Beta
    Stable Release Date: 2014-07-05
    Beta Release Date: 2015-01-08

    Created 2014-05-27
    Last Updated 2015-01-08
    97
    New build should be out either Monday or Tuesday. There will be a plethora of fixes and improvements. Sorry about being away from XDA for a while, just been really busy with school and any time I have for FML has been spent on dev stuff rather than the XDA threads!
    96
    I'm feeling terrible. I don't have the energy to update the thread, but the new build is uploaded here:
    FML-AOSP-5.0-20141207-maguro.zip (199.24MB)
    I see some people have already downloaded it...

    A new GApps package isn't quite ready yet. I believe PA has a Lollipop GApps package up that may work as-is and would be better than the one I'm currently linking to, so give that a try if you're impatient.
    I also have a new TWRP build on the way as well.

    Short changelog on the new build:
    - Superuser is now built-in, no need to flash SuperSU. It's in the Settings app. You may have to enable the "Development Settings" menu to see it...
    - Video playback should be fixed. YouTube in particular seems OK. If you have some weird format you're playing back locally I cannot make any guarantees though.
    - The camera situation has improved and also regressed. The stock camera is back to the point of where it was with the KitKat Beta builds:
    ---- Preview works. Saving photos does not work. Video recording works.
    --- However:
    ---- The camera calibration is a little messed up. Long story, but it'll be fixed soon. So your white balance may look kinda funky, among other things.
    - Audio quality is improved, and 192kHz FLAC files will now play:
    ---- This is possible thanks to a new audio resampler, which doesn't impose the same sample rate restrictions of the stock Android ones.
    ---- It also has far better quality than the stock Android resamplers.
    - Kernel changes:
    ---- Reclaimed 38MB of RAM from the carveout stuff.
    ---- Removed HDMI's framebuffer, saving another ~16MB of RAM. With Lollipop, MHL/HDMI out isn't working with our old hwc, so might as well save some RAM in the mean time.
    ---- Added overclocking support, as well as adjusted the stock frequencies a little.
    84
    I see there have been some bugs discovered with the recent build, so I'm planning on doing a new build fixing what I can and then updating the OP with that build instead. I also have something special planned for the next build as well... for those of you who follow my GitHub, please don't spoil it! It might not be ready in time, but it's coming along quicker than I thought...

    I'd like to thank those of who you have been patient waiting for the new build and not asking when it'll be out etc. I do know it's frustrating for you guys when I give a timeframe on when a new build will be ready and I don't deliver though, however lately the pestering for when a new build will be out has gotten out of hand. I'm usually pretty good with handling things like that which would cause most other devs to basically yell and scream at their users... for example, when people report bugs I'm not one to say "logcat or it didn't happen". At least 90% of the bugs reported are something I can reproduce myself! Why the hell should I need the user to get the logcat when I can get one myself? But anyway, I hope those of you who have been pestering for ETAs can be a little more patient from now on.

    I'd also like to thank those of you who have donated to me lately. I usually try to send out thank yous to them when I update the FML thread, but I'm sad to admit that lately I've fallen behind with that. My problem is that I like each thank you to be different and not just a copy and paste generic BS sorta thing, but I'm running out of things to say because there have been so many donations since the GPU driver updating and Lollipop release. Before I update the FML thread next, I will be sure that everybody has been thanked personally.
    The donation money has been so helpful lately with me being sick too; I've been able to get food and drinks that are easier for me to digest and keep down.
    67
    Thanks to everyone who helped, I've got my maguro running again :victory::victory: One can't imagine how much I appreciate the help of the community :) so it looks like I'm getting back to the business ;)