[SCRIPT] Build LineageOS EASY - Google Pixel 3a ROMs, Kernels, Recoveries, & Other

[SCRIPT] Build LineageOS EASY - Google Pixel 3a ROMs, Kernels, Recoveries, & Other

If you are interested in building LineageOS for Bonito or Sargo you can use my script on Github to compile for either device. The script I link in this post will build my daily driver ROM. To consider running this script you will need the following:
- A PC running Ubuntu 18.04 or a distro based off Ubuntu 18.04 (I use ZorinOS)
- This PC needs at least 8gb RAM, a quad core processor and 300GB of available space on a drive (preferably SSD)
- Patience
* These are the instructions for running the script:
Open a terminal and run the following commands
git clone https://github.com/stevn4127/scripts
(This clones my scripts to a directory called scripts)
cd scripts
(This navigates you to the scripts directory)
bash lineage.sh
(This runs the script)
You will need to enter your root password to update the OS and install build tools. You may also need to run the following command with your Github credentials following the text:
git config --global user.email
git config --global user.name
Here is a direct link to my scripts repository on Github:
https://github.com/stevn4127/scripts
Join my Telegram chat for help: NugTowers HQ
Test builds and a ton of OT. We are mainly Pixel/Pixel 3a users but everyone is welcome! Just don't be a POS Please... No nudity. DONT be a pervert. (Mod Edit: Certain descriptions removed)
https://t.me/nugtowers
Good Luck!

Since I cloned your scripts, I have added Lineage to my "skinny build box" project; primarily due to the VoLTE and VoWifi support it shares with Bliss 12.x. Yes; I know that T-Mobile is kicking phones that don't support VoLTE and VoWifi off their network; however, that won't apply to any phone that runs AOSP - as VoLTE is par for the course for any phone that runs a recent AOSP firmware (Pie or later in practically all cases; in the case of Lineage, as far back as Oreo). I changed tower providers because T-Mobile doesn't care what firmware you run on your phone. (Since then, it turns out that my infusion center (and my current cardiologist - which is in the same building) are in a hole in the UnCarrier's tower network - which makes hotspot support - and therefore VoLTE and VoWifi support - all the MORE critical.)

PGHammer said:
Since I cloned your scripts, I have added Lineage to my "skinny build box" project; primarily due to the VoLTE and VoWifi support it shares with Bliss 12.x. Yes; I know that T-Mobile is kicking phones that don't support VoLTE and VoWifi off their network; however, that won't apply to any phone that runs AOSP - as VoLTE is par for the course for any phone that runs a recent AOSP firmware (Pie or later in practically all cases; in the case of Lineage, as far back as Oreo). I changed tower providers because T-Mobile doesn't care what firmware you run on your phone. (Since then, it turns out that my infusion center (and my current cardiologist - which is in the same building) are in a hole in the UnCarrier's tower network - which makes hotspot support - and therefore VoLTE and VoWifi support - all the MORE critical.)
Click to expand...
Click to collapse
Google may be trying to kill custom development, but we have developers like you to thank for continuing to help advance this field. Keep at it!

blksith0 said:
Google may be trying to kill custom development, but we have developers like you to thank for continuing to help advance this field. Keep at it!
Click to expand...
Click to collapse
I am not a developer. This is just my hobby. Lol. Thank you though. I'll be doing this stuff for as long as it's still possible. Long live the custom community!

PGHammer said:
Since I cloned your scripts, I have added Lineage to my "skinny build box" project;
Click to expand...
Click to collapse
Is this skinny build box project available?

tvoneicken said:
Is this skinny build box project available?
Click to expand...
Click to collapse
The skinny build-box project is designed to be as low a specification that can build a standard-spec AOSP-based ROM.
My target is a two-core PC with 8 GB of ROM and 250 GB of storage space used - as either a virtual machine OR a WSL2-bsed spec.
The very reasons FOR the skinniness is so the PC used for it can be doing other things while build operations are going on - which is also why I am concentrating heavily on WSL2-based specs - because it has such operating in mind.
As opposed to most build-boxes - which have lots of both storage and cores - I'm going the other way - with as few cores and storage as can be gotten away with - to keep costs for builders down (hence "skinny") - not every builder is rich.
Once I get things ironed out, I will, naturally, publish exactly HOW "skinny" the final spec is - and I'll do so publicly ALA Nathan Chancellor.

A followup
PGHammer said:
The skinny build-box project is designed to be as low a specification that can build a standard-spec AOSP-based ROM.
My target is a two-core PC with 8 GB of ROM and 250 GB of storage space used - as either a virtual machine OR a WSL2-bsed spec.
The very reasons FOR the skinniness is so the PC used for it can be doing other things while build operations are going on - which is also why I am concentrating heavily on WSL2-based specs - because it has such operating in mind.
As opposed to most build-boxes - which have lots of both storage and cores - I'm going the other way - with as few cores and storage as can be gotten away with - to keep costs for builders down (hence "skinny") - not every builder is rich.
Once I get things ironed out, I will, naturally, publish exactly HOW "skinny" the final spec is - and I'll do so publicly ALA Nathan Chancellor.
Click to expand...
Click to collapse
I'm still shooting for the two-core target; however, as a backup, I'm doing a slightly-beefier four-core version based on the stebomurkn scripts - for the honest reason that I find them personally extremely useful.
CPU - Intel Core i5 (Socket 1151 or later)
Motherboard - any H or Z chipset that can take the same
RAM - 16 GB
HDD - 4 TB or larger
SSD - optional
GPU - optional
I'm doing a rebuild of my current system based on this spec. While my current system is G3258-based, I actually have a bigger budget than I did when I built "Baby Beastie" - my current '58 PC. The GPU will be the same GTX 1050Ti that drives "Baby Beastie" currently, as I have no need to upgrade it based on my gaming drivers. The HDD will be larger, because pricing for such has dropped dramatically. The PSU - like the GPU - is carryover (Corsair CX550M) - why replace what isn't broke? Same with the case - a full-size ATX. An SSD is an option - as my gaming needs don't require one. (My motherboard choices support both traditional SSDs and the M.2 sorts.) I'm still trying to stay under $1000USD - and I'll be purchasing everything via Amazon.com - which I did with "Baby Beastie".

ADDENDUM - Can you use both stebomurkn's scripts AND the scripts referenced in Nathan Chancellor's AOSP build guide? Absolutely - you simply need two script directories - ~/scripts and ~/scripts2; they can be in either order. (The reason why you need two directories is that you can't simply add them to the existing ~/scripts directory because it's not empty - hence you need a new place to put them - ~/scripts2.)

ADDENDUM - the core of the "skinny box" has been acquired - and it's the platter drive.
First off - why a platter drive? Platter drives are not pricey, and have gobs of capacity; further, thanks to onboard cache, they need not be snails. In my case, I went with the midrange Seagate 4 TB Barracuda Compute - which has been on sale at Amazon (AKA "Smiley's") for a mere $80USD (Prime). The Compute series is in three ranges - 2.5-inch for portables - 3.5-inch for desktops - and Compute Pro for workstations. The Compute I chose - for that $80USD - is from the 3.5-inch formfactor desktop range - which makes it physically no larger than the 1 TB previous-generation Barracuda it replaced, despite the four times larger storage capacity AND fifty percent faster (according to Windows 10) I/O performance - so much for making snap judgements! You don't need speed from a build box storage medium; what you DO need, though, is capaciousness - and 4 TB is plenty.
With the new core acquired, next came moving the data from the old drive to the new. Normally, I would use old-friend Acronis True Image; however, it has grown unwieldy in its age - so I wound up replacing it with Macrium Reflect 7. It has all the features that the older version of Acronis did - operates natively in Windows - and costs nothing.
Once you have the old data moved to the new home, re-sync your repos - remember, you have a LOT more space than you used to! (If you had a 1 TB (or smaller) platter drive, you may find yourself KICKING yourself, thinking "I was that silly in terms of lack of storage space?" Not exactly fun. Don't overeat - but don't skimp, either.)

Due to issues starting a new thread with a new post, I am making this one here; could someone with the proper access move it where it should go once I am finished? The subject involves running GSI (Generic System Image) ROMs on the Pixel 3a.
Why would anyone do so? The reasons are - unfortunately - twofold; it is getting harder and harder to find - or build, in fact - ROMs based on Android 10 and later for THE utility-infielder phone for Android 10 - the Pixel 3a. The second I have uncovered in my own running of Android 10-based GSI Havoc OS 3.8 for the past week - it is, in fact, better than the purpose-built Havoc ROM for the same hardware based on the same code - which makes not a lick of sense, but there it is.
There are two differences - Pixel Launcher is missing; instead, it uses Havoc's Shady Launcher - also, it cannot use Google Camera. Still, that is, in fact, all.
Now comes the $0.64 USD (sixty-four cents in US dollars) question - how does it run, and especially compared to purpose-built? Here's the scary part - for the most part, it actually runs BETTER than purpose-built based on the same code. The display is better. The performance is also better for the most part. As I said earlier, it makes not a lick of sense for "generic" to be better than "name-brand" - even when it comes to ROMs - yet here it is.
I have run it for the last week, and am STILL running it; either tomorrow or Monday, I will replace it with Havoc OS v. 4.1 (also GSI) for additional thrashing.

My BlissROM script is up to date if anyone is interested in building for this device still. I will be updating my Lineage script in the following days to make this thread relevant.

stebomurkn420 said:
My BlissROM script is up to date if anyone is interested in building for this device still. I will be updating my Lineage script in the following days to make this thread relevant.
Click to expand...
Click to collapse
Hi, I've tried to build Bliss using your script, and it failed at Building Kernel Image (Image.lz4) :-(
Most likely I'm the problem - I have no clue how android and Linux works nor any clue what scripts do and how they work, but since everything seemed to be working fine for a couple of hours, I hope it wasn't me (=fixable) this time. I can provide you with the log, just let me know where can I find it... Thank You!

ADDENDUM/FOLLOWUP - Can this be used with Windows 11? Yes - and with no changes whatever.

Related

[PROJECT][KERNEL] Join your efforts for HOX kernel development

I already saw a lot of kernel developers here, each of them posting their own version.
I don't think that "download sources / fix them / apply patches" by every one of them is ok.
If all could focus on a single source-tree and fix / apply patches to that we would get to a stable/improved version a lot faster.
I can provide a linux machine for the developers interested by this project.
Hardware: 2 x Xeon X7550, 16GB RAM (can be extended to about 60GB), 300GB of storage (can be extended) - RAID6, FC dedicated storage.
Example:
$ time make ARCH=arm clean
[...]
real 0m2.479s
user 0m0.953s
sys 0m1.151s
$ time make -j32 ARCH=arm CROSS_COMPILE=arm-eabi-
[...]
real 1m4.720s
user 19m11.694s
sys 3m23.190s
Click to expand...
Click to collapse
Software:
Slackware 64bit 13.37, gcc 4.5.2, gcc-arm 4.6.1
OS can be changed if you have good enough arguments.
SSH access, no root.
If any developer is interested by an account, pm me with the desired username.
Have fun!

Ok, if no one is interested, I have to start this alone...
BETA
First release - ALiCE Kernel - with patches/tweaks from eternity/franco/bricked kernels and some of my own. Everything seems to work on my HOX.
- Sweep2wake included
- modules built in kernel, no need to flash anything else but boot.img
Attached:
zImage - for including into your own boot.img
boot.img - InsertCoin 5.3.0 boot.img with this kernel.
DELETED ATTACHMENTS - Kernel was virtually unusable.
You can use zImage injector ( http://forum.xda-developers.com/showthread.php?t=1647398 ) to update your own boot.img

I like the idea of this collaboration of kernels.
And I like how the modules are integrated into the kernel.
I'll be testing this out more tomorrow with a battery test for a work day
Keep up the good work
EDIT:
3G Does not work.
As in it shows 3G/H on the top, but no network connectivity.
WiFi does however work.

Great
I'm not a kernel dev, but this seems like a good idea.
Kernel devs working together to create a solid/stable base kernel.
If they want to add specifics they can always release one aside of this.
Also good to integrate modules into boot.img
Keep up the good work.

+1
Good idea, and go on
Good work.

Well I build kernel in 1 minute on i7 920 @4.2 ghz, no need for you machine ;-)
But common git would be nice.. I have zero time to maintain a kernel for HOX
Sent from my HTC One X

It will be nice if we can have a common github repository for the OneX sense kernel with all the patch applies by the devs.
AliceXES, do you have a git link of your repo ?
Because I currently compiling the franco's repo with some config tweek for my own need. And I would like to compiling yours just for testing.
Anyways, thanks for starting your project

Please send me your twitter account it's for helping you

The biggest problems ain't hosting or building times, just version-control. A common Git would be nice, although it seems most changes get picked by eachothers at github.

What about a GitHub organisation? You can have free ones where everyone is admin if you leave the source open. But then that requires a certain level of trust I suppose, heh.

The problem was with modules - for some strange reason, 3G doesn't work with them built-in the kernel.
Also my laptop crashed. The 2nd HP 4520s dead in my hands.
I will probably won't work on this anymore until it's repaired.
Still, if anyone needs access to the compile-server, the offer is still open.

AliceXES said:
The problem was with modules - for some strange reason, 3G doesn't work with them built-in the kernel.
Also my laptop crashed. The 2nd HP 4520s dead in my hands.
I will probably won't work on this anymore until it's repaired.
Still, if anyone needs access to the compile-server, the offer is still open.
Click to expand...
Click to collapse
Sad happenings. Hopefully it'll be fixed soon so you'll be back on track!

1: 3G problem indeed lies in the modules (linked to one of the binary baseband module)
2: getting collaborators won't be easy; many (apart from a select few) of today's "chefs" (dare not call them devs) prefer to act alone, get the credits, instead of working together, where the progress would've been much faster. This has been discussed too many a time on xda.
It is so much easier to rip someone's work & claim it as your own... Which is why many a dev resorted to "protecting" their roms (for example, from dumping).
Another reason why not many would like to join you, is that then it would come apparent that they don't have any real skills, since they won't be contributing any patches. ;]

Why compare ROMs with Kernels though? Maybe I'm unique at this, I don't know but, I never really cared about moving files around at ROM level or building AOSP ROMs. I prefer the kernel-space just a bit more
If people are afraid that their commits get stolen (which unintently happened just a few days ago, it seems) they should sign-off it properly.
Ányway I'm always interested in collaborating. Atm I'm just foring Franco's kernel and fixing a few compiling warnings.. I think what we really need is one main-maintainer which holds the master-branch, then the rest of our bunch just can push commits to him for reviewing. Who this lad is going to be, is also a tricky one.

I don't think I will have any success with this project
I started my own kernel thread (here: http://forum.xda-developers.com/showthread.php?t=1662781 ), sorry.
Anyway, the invitation is still open.

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

[ROM][5.0.2/LRX22G][AOSP][LINARO/OPTIMIZED] FML: Fork My Life (2015/01/08)
[#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 4G LTE (or mobile data in general really) as much as you; you get the idea.
[#HowTo]
Latest BuildKitKat/ROM Stable: omni-4.4.4-20140705-toro-FML.zip (158.92 MB)
KitKat/TWRP Stable: fml-twrp-2.7.1.0-20140705-toro.img (8.58 MB)
KitKat/ROM Beta: omni-4.4.4-20141014-toro-FML.zip (160.87 MB)
Lollipop/ROM Beta: FML-AOSP-5.0-20150108-toro.zip (195.43 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.
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 Verizon 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 2013-10-11
Last Updated 2015-01-08

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.
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.
3. toro's RIL was trying to add a route to the table with a netmask of 255.255.255.255, which isn't correct and won't fly with Lollipop anymore I guess. @Hashcode was the one to point out that this was an issue and helped me figure out that the netmask was a string in the RIL blob that I could edit freely, and after some brainstorming with dhiru1602 I was able to stick in the right netmask of 255.255.255.000.
- 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.
- 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!
2014/05/26 (Operation: Speed Racer)
ROM: Synced with OmniROM's latest changes as of around 7:00 AM 2014/05/26 UTC.
ROM/Build: Improvements to LTO.
ROM/Build: Fixed a potential issue where LTO wouldn't provide any benefits.
ROM/Build: Fixed a bug where the compiler was optimizing towards a generic ARMv7 CPU instead of a Cortex-A9 CPU.
ROM/Build: Fixed a couple small things that were overriding the -O3 flag with -O2.
Uhh... this build is ****ing fast. I noticed the speed improvement before even flashing the ROM: decryption in the TWRP build was at least 5x faster. After flashing and rebooting, I saw the same improvements in decryption... there's a little animation that plays when decryption is running, and it's so fast that the animation isn't even animated, it's just a quick little still image. It's just ridiculous how fast this build is.
2014/05/10 (Operation: Preparation)
ROM: Synced with OmniROM's latest changes as of around 11:00 PM 2014/05/10 UTC.
ROM: Updated (mk)sh to R48. (Small thing most people won't notice)
ROM: Small bugfix/update for oprofile. (Small thing most people won't notice)
ROM: Some behind-the-scenes stuff to help make sure the next (overly ambitious) FML build goes smooth.
Nothing much here, just figured I'd get a synced up build out now before I end up not being able to because I'm working on some bigger changes for FML.
2014/04/29 (Operation: Exterminator)
ROM: Synced with OmniROM's latest changes as of around 4:00 PM 2014/04/29 UTC.
ROM/ScreenRecord: Fixed ScreenRecord crashing instantly.
ROM: Tried tweaking things to reduce battery consumption regression that popped up in the 2014/04/12 build.
ROM/Audio: Thanks to syncing with OmniROM, the distortion that sometimes occurred in audio playback is fixed.
ROM/GPS: Blind attempt at improving GPS lock-on speed, probably didn't work but I can't tell yet.
ROM: Miscellaneous improvements and bug fixes that will probably go unnoticed.
Not a lot of exciting stuff here, but I figured I'd get this build out with the various bug fixes that accumulated since the last one.
BTW, the issue with ScreenRecord was that it attempted to record the phone's audio directly (the audio it outputs through headphones/speaker), which has issues with at the very least the Galaxy Nexus if not all non-Qualcomm hardware. I had to switch it so that it records the phone's microphone instead.
2014/04/12 (Operation: Flyswatter)
ROM: Synced with OmniROM's latest changes as of around 7:00 AM 2014/04/12 UTC.
ROM: Re-added multi-core DexOpting (speeds up the first boot after a dalvik-cache wipe), OmniROM removed this as it caused problems for some people it seems, but it's working just fine over here on FML.
ROM/OmniTorch: Fixed FC when attempting to create a Torch widget.
ROM/DSPManager: Fixed an aliasing violation (due to a recent change to DSPManager which was courtesy of CyanogenMod -.-).
ROM/ART+Dalvik+Settings Added an option in Development Settings to toggle the "DexOpt /system to /cache" feature due to it having a few possible but rare issues.
Blaaahhh. Sorry this build took so long, it's just after I noticed OmniROM removed the multi-core DexOpting I had to add it back due to how long an initial bootup with ART and 150 apps was taking (it seemed like an entire hour honestly), and then once I figured that all out I ended up having one last bug to fix with the new toggle I added for DexOpt /system to /cache. I didn't want to release something that I didn't feel was good enough!
2014/04/02 (Operation: Buzzkill)
ROM: Synced with OmniROM's latest changes as of around 11:00 PM 2014/04/02 UTC.
ROM: Removed some stuff I didn't feel was necessary to include (some ugly live wallpapers, the video editor, the "Dev Tools" app).
ROM: Removed OpenDelta (OmniROM's updater).
ROM/RIL: Fixed issues when using the Quick Settings tile to switch between 4G/LTE and 3G/CDMA. For the past 4 or 5 builds, using this toggle would make mobile data not work whatsoever. Also, the toggle used to think there was 3 different data settings ("2G Only", "2G/3G Preferred", "4G/LTE"), now it's only 2 and correctly described ("3G/CDMA, "4G/LTE").
ROM/ART: Merged in some stuff from AOSP's master branch of ART. This is kind of experimental, there might be some issues with some apps, if so let me know.
ROM/ART+Dalvik: Make apps in /system store their dalvik-cache on the /cache partition. Previously the /cache partition just sat there, all ~500MB of it empty. A side-effect of this is that when using ART, you have to use a smaller GApps package, as when using ART the dalvik-cache takes up more space, and with the full GApps packages it's too much. If you're using the larger GApps because you're concerned about saving space on the /data partition, if you just install the full GApps stuff via the Play Store (therefore storing the apk on /data), you're still saving space due to all the space freed up via making using the /cache partition.
TWRP-Recovery: Now building and uploading TWRP recovery images as well. Current improvements over official TWRP builds: Added backlight control, fixed decryption of encrypted /data partition.
ROM/Recovery: Fixed MTP (access to internal storage via USB) and ADB not working in TWRP (shouldn't require usage of my TWRP build, just the ROM should be sufficient).
Please make sure to read the note about ART and GApps. This build is part of "Operation: Buzzkill", attempting to find and squash as many bugs as possible.
2014/03/22
ROM: Synced with OmniROM's latest changes as of around 7:30 AM 2014/03/22 UTC.
ROM: Added 0xBenchmark. Details below.
ROM/OmniTorch: Fixed "Bright" option showing up even though it isn't available. Known Issue: OmniTorch widgets are broken.
ROM/PhaseBeam: Fixed PhaseBeam Live Wallpaper causing extreme lag.
ROM/RIL: Merged in more fixes courtesy of @DevVorteX
Since I wasn't able to do the big stuff I wanted I figured I'd do a bunch of small stuff so it feels like I got a decent amount of things accomplished.
As for 0xBench, this is something I stumbled across in Linaro's git repo. Figured I'd give it a shot. Play around with it, feel free to share what results you're getting with it and at what kernel settings (overclock, specific kernel if non-stock, etc).
2014/03/10
ROM: Synced with OmniROM's latest changes as of around 12:30 AM 2014/03/10 UTC.
No changes other than the sync with this build, the next build should have some cool new stuff though.
2014/02/26
ROM: Synced with OmniROM's latest changes as of around 12:00 AM 2014/02/26 UTC.
ROM/RIL: Added code from @DevVorteX to improve mobile data stability.
Well I'm about a day late with this one, better than weeks though.
BTW today is my birthday ^.^
2014/02/22
ROM: Synced with OmniROM's latest changes as of around 12:30 AM 2014/02/22 UTC.
Build: Re-enabled LTO.
Build/Toolchain: Linaro toolchains updated.
Didn't do huge changes with this build since I want to make sure that if there's any issues, I can know that it's probably due to LTO and then just simply disable LTO in problem areas.
2014/02/01
ROM: Synced with OmniROM's latest changes as of around 6:00 PM 2014/02/01 UTC.
Build: Fixed issues with repo after git updated to 1.9.rc1 (apparently repo wasn't fond of having rc1 in the git version number!)
Navbar customization is in this build, along with OmniSwitch!
I'm still busy with school unfortunately.
The reason I had more time for FML before the holidays was that I didn't really have my priorities straight. School had began taking a back seat to things like FML and video games etc. Since then I've rectified that, as school should really be my #1 priority, but now dev work has ended up where schoolwork was before. It's not easy finding a balance between work and fun, but I think I'm getting there!
2014/01/25
ROM: Synced with OmniROM's latest changes as of around 4:00 AM 2014/01/25 UTC.
ROM: Miscellaneous fixes to get it building after some of OmniROM's latest changes.
Build: Linaro toolchain was updated, I think.
Not a lot of stuff with this build, I've been pretty busy lately and haven't had a lot of time to devote to FML. Things are looking better now, so hopefully I'll have the time to do more frequent builds and such. I'm looking into possibly having a computer running 24/7 that'll do nightly or bi-nightly builds of FML, I just need to see if it'll have trouble with the specs of the computer I'd have to use for it and figure out how to manage automatically merging in OmniROM's changes.
2014/01/15
ROM: Synced with OmniROM's latest changes as of around 12:00 AM 2014/01/15 UTC.
Kernel: Redid all the work done for the New Year's build in hopes of fixing the screen freezing problem.
Put a lot of time into this. Please let me know if the screen still freezes.
Voltages are a bit higher than they were with the New Year's kernel, so battery life will probably be slightly worse, but that can be tweaked for the next build. The priority was fixing the lock-ups.
2014/01/09
ROM: Synced with OmniROM's latest changes as of around 4:15 AM 2014/01/09 UTC.
Just synced up with the latest OmniROM code in this build, and also the toolchains were updated since the last build. There were some reverts of things in OmniROM that required me to use a bit of tinkering with git to get everything merged correctly.
Apologies for the lack of updates lately, I've been busy with life and -40*F/-40*C (-40 is where the two scales intersect lmao) wind chills.
2014/01/01
ROM: Synced with OmniROM's latest changes as of around 6:00 PM 2014/01/01 UTC.
ROM/Settings: Fixed force closing when attempting to use WiFi Tethering.
ROM/Settings: Fixed not being able to turn LTE on again after turning it off.
ROM/Keyboard: Added the necessary lib to support gesture typing out-of-the-box.
Kernel: Pulled in a lot of bells and whistles. You can view lots of them by going into Settings --> Performance.
I'd appreciate it if you'd give the kernel a try before flashing a different one, I put a lot of work into this last night. I'll try and leave more details as to what's all there soon.
2013/12/30
ROM: Switched to OmniROM as the ROM base.
ROM/Build: Didn't build with Link-Time Optimization just yet, and a few other miscellaneous FML sprinkles are still missing.
ROM/Settings: Added built-in Superuser as OmniROM didn't have it, so flashing SuperSU is not required nor recommended.
You'll need to wipe /data before flashing this build, it's basically like flashing a new ROM. Back up everything of course.
2013/12/21
ROM: Selectively synced with CM's latest changes as of around 4:30 AM 2013/12/21 UTC.
ROM/Build: Enabled Link-Time Optimization.
ROM/Build: Fixed every aliasing violation except in frameworks/opt/net/voip and external/openssh, allowing for further optimizing.
Make sure you wipe /system too before flashing this one, regardless of which FML build you're coming from. This is a little experimental still, but it seems good enough to release now considering I still don't endorse this ROM as a major daily driver lol.
2013/12/15
ROM: Synced with CM's latest changes as of around 4:30 AM 2013/12/15 UTC.
ROM/RIL: SMS/MMS should be fixed on new flashes. (via CM sync)
ROM/RIL: Fixed connection to 3G after turning off WiFi. (via CM sync, slightly "expedited" if you get what I'm saying...)
ROM/Hardware: Small possible speed-up brought back from the previous CM-10.2 FML Linaro/Optimized builds.
If you're having issues with SMS/MMS still, go to Apps and clear the data of Phone/Messaging Storage, then reboot. If that still doesn't fix it, please let me know.
I didn't get a chance to look closer at the Handcent FCing issue, but it might be fixed via the CM sync, so don't be afraid to give it another try.
To-Do.Slim down the build by putting less used stock applications into a separate flashable .zip, such as Browser.
Experiments I'm Looking IntoCreating Black Holes with my phone's ridiculously awesome speed.

Developer InfoThis 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 ThingsI 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...

Reserved
Reserved.

Screens?

Enter The Nexus said:
Screens?
Click to expand...
Click to collapse
I plan on finishing up the thread when I wake up. I've pretty much pulled an all-nighter and need to get some rest, especially after the night I had at work (I was literally doing the jobs of 2 other people and nearly quit!). It really doesn't look any different than just a stock CM 10.2 build, I don't think I've really changed anything with the interface (yet, anyway).
So, expect screens in maybe 10 hours or so.

Flashing this now! It looks pretty awesome!

Multisupermono said:
Flashing this now! It looks pretty awesome!
Click to expand...
Click to collapse
Thanks! I appreciate your interest in my ROM.
I'm going to be doing a fresh build right now and then I'll get up some screenshots. Should be a couple hours or so.

Looks cool, I'm must wondering if the MMS/no phone # bug is fixed yet.

nitsua98 said:
Looks cool, I'm must wondering if the MMS/no phone # bug is fixed yet.
Click to expand...
Click to collapse
I'm not quite sure what you mean by that. MMS has worked fine for me and so have phone calls. Was this pertaining to my ROM or another one?
EDIT: By the way, build is taking a little longer than I thought it would, not quite sure where it's at yet. I'll give an update on the progress in the next hour or so. Also, I have to wait 2 minutes to make and/or edit a post, it says I need a "reasonable post count" before that timer goes down; I also had wanted to post this on the DevDB as when I posted the topic it told me I should, however I couldn't find where to do that. I presume I have to be a "Recognized Developer" or something before it'll let me. If anybody knows the post count I need to remove the 2 minute timer and/or how to be a Recognized Developer, please let me know!

MWisBest said:
I'm not quite sure what you mean by that. MMS has worked fine for me and so have phone calls. Was this pertaining to my ROM or another one?
Click to expand...
Click to collapse
CyanogrnMod has had a bug recently where your phone number says 'unknown' and something is messed with the prl. I guess in your build it's already merged. Could you check to see if you're phone number is down in About Phone>Status? Thanks

nitsua98 said:
CyanogrnMod has had a bug recently where your phone number says 'unknown' and something is messed with the prl. I guess in your build it's already merged. Could you check to see if you're phone number is down in About Phone>Status? Thanks
Click to expand...
Click to collapse
Last night I did have to reboot my phone as it was stuck on "Searching For Service" for some odd reason and it said I was "Out of Service" in About Phone, but my phone number was still there and still is. I'm guessing I either already merged in the fix or maybe I just merged in the bug, I'll have to check! Thanks for the heads up.
EDIT: It looks like it's related to the most recent 3 commits merged here: http://review.cyanogenmod.org/#/q/s...nogenMod/android_frameworks_opt_telephony,n,z
I do a repo sync before I do a build, so it looks like I pulled those in before I did the build last night. Should be good to go!
EDIT2: Today's build should be finishing up shortly. Most future builds should be faster than this one, once in a while (once per week maybe?) I like to start with a fresh build rather than just an incremental one. Incremental builds just rebuild what's needed based on what code has changed, however it isn't perfect; a fresh build ends up rebuilding everything from scratch. Once the build finishes I'll give it a quick test and then upload it along with some screenshots.

New build looks good, check out the 2nd post for the changelog. Currently uploading the build and screenshots and will update the 1st post accordingly.
EDIT: Alright, uploaded and good-to-go! I'm heading off to work but I'll try to drop in on the thread for any support during my break.
EDIT2: I got a (mobile network) connectivity issue I found that I'm attempting to debug right now, it doesn't happen often and I don't know what triggers it but a reboot seems to fix it until it happens again. So, if you're having a connectivity issue try rebooting to fix it for now.
EDIT3: It looks like there's some changes to AOSP's master (latest) branch that may help not only fix this issue but data connectivity issues as a whole (handoff delays, etc.) I'll be experimenting with them and will post an update if something works out.

New build will be up shortly, mobile network connectivity appears to be much improved! I'm still going to look more into this as I, correct me if I'm wrong, believe it's something not only affecting FML but also other 4.3 ROMs for the Verizon Galaxy Nexus (toro).
EDIT: 1st and 2nd posts updated with new build and changelog for said build, give it a whirl while I get some much needed sleep! I appreciate everybody's interest and feedback, honestly I was just expecting nobody to even look at it and for it to just fall back to the last page of the forum really. I suppose if you set your expectations that low, anything is a win!

Running this now. So far so good.
Sent from my Galaxy Nexus using Tapatalk 4

modernbummer said:
Running this now. So far so good.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Me as well. MMS works as supposed.Data seems to be working better than regular CM builds.

modernbummer said:
Running this now. So far so good.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
christianpeso said:
Me as well. MMS works as supposed.Data seems to be working better than regular CM builds.
Click to expand...
Click to collapse
Great! Glad to hear everything is working OK, thanks for the feedback.
EDIT: Quick update on mobile connectivity here... it looks like what might have been causing the data issue where I had to reboot the other night was tracked down in CM. This is the change proposed to revert a change that was apparently causing issues on the Verizon Galaxy S3 similar to what I described: http://review.cyanogenmod.org/#/c/48873/
I'm going to wait to see if this happens again, and if so incorporate that change to see if it fixes it, just in case I might have fixed it with that AOSP merge last night.
EDIT2: Hit the issue again, had to reboot to fix it. I'm going to be reverting that change that supposedly caused this issue and upload a new build with it, however I have to head off to work shortly so it won't be until later tonight unfortunately. Sorry for the inconvenience! If a reboot doesn't fix it a reflash supposedly does, it would only require wiping /system, /cache, and dalvik-cache, so you could leave the /data folder alone to keep your apps and settings and whatnot, just simply reflashing the ROM then (and GApps too, as /system is wiped!).

Love it so far. An option to center status bar clock would be nice. Also I love custom carrier labels because I hate Verizon haha so I wouldn't mind seeing that available
Also, is there a reason you can't just wipe the two caches when updating? I just ask because most ROMs are that way.

swarlesbarkely said:
Love it so far. An option to center status bar clock would be nice. Also I love custom carrier labels because I hate Verizon haha so I wouldn't mind seeing that available
Also, is there a reason you can't just wipe the two caches when updating? I just ask because most ROMs are that way.
Click to expand...
Click to collapse
Thanks! I appreciate the feedback and will look into adding the centered status bar clock and custom carrier label. I remember those from previous CM versions and liked it as well.
While wiping the two caches would probably work, I just prefer a full /system wipe because if any files are renamed/moved/deleted they'll still have the old crust left behind which could lead to problems. The /system partition shouldn't really have to be messed with anyways; if there is something you customize in there yourself you can let me know and I'll see what I can do about incorporating it.
In short, you can wipe just the 2 caches and flash, however if you run into an issue after doing that I'd prefer that you test it again with a /system wipe as well.
BTW, I just got home from work, very long night... I'm gonna get a build with the hopeful fix for mobile data issues up and then probably call it a night.

New build is up! Check out the changelog and flash away.
I also made a note in the OP of the only wiping the 2 caches thing that swarles mentioned above.
EDIT: Yikes, looks like I just ran into yet another issue with mobile data. I'll keep a link in the OP to the build from yesterday in-case others have the same issue while I try to sort it out.
EDIT2: I may have discovered a big reason for why we Verizon Galaxy Nexus users have had mobile data issues with 4.3, I'll do some more investigating and if what I've discovered is correct I will share what I can with the community here. :fingers-crossed:

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

[#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 BuildKitKat/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

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!
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 IntoCreating Black Holes with my phone's ridiculously awesome speed.

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.

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...

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?

pvkiniyan95 said:
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...
Click to expand...
Click to collapse
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.
qtoo941 said:
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?
Click to expand...
Click to collapse
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!

Wow, amazing, i was waiting for this! OmniMetal is a wonderful ROM but we can't except that metalspring will be doing regulary updates since he has a new phone.

This might be the quickest ROM my maguro has ever seen. I can't even believe how fast Chrome opens.

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

ahmadairfan said:
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
Click to expand...
Click to collapse
Only ART! Feel the smoothness

ahmadairfan said:
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
Click to expand...
Click to collapse
pianistaPL said:
Only ART! Feel the smoothness
Click to expand...
Click to collapse
Dalvik! MWis pimped it the **** out!
MWisBest said:
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.
Click to expand...
Click to collapse

Ok, end of speaking, phone charged, let's try this ROM!
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 So this is a good reason to try this super fast dalvik

pianistaPL said:
Ok, end of speaking, phone charged, let's try this ROM!
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 So this is a good reason to try this super fast dalvik
Click to expand...
Click to collapse
thanks for that...u saved my time

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!

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

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!.
Enviado desde mi Nexus 7 mediante Tapatalk

ahmadairfan said:
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
Click to expand...
Click to collapse
pianistaPL said:
Only ART! Feel the smoothness
Click to expand...
Click to collapse
osm0sis said:
Dalvik! MWis pimped it the **** out!
Click to expand...
Click to collapse
^What he said. At the very least give Dalvik a try.
pianistaPL said:
Ok, end of speaking, phone charged, let's try this ROM!
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 So this is a good reason to try this super fast dalvik
Click to expand...
Click to collapse
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.
pvkiniyan95 said:
thanks for that...u saved my time
Click to expand...
Click to collapse
See above.
gautam_nexus said:
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!
Click to expand...
Click to collapse
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.
pianistaPL said:
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.
Click to expand...
Click to collapse
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.
mosca_ said:
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!.
Click to expand...
Click to collapse
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.

MWisBest said:
^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.
Click to expand...
Click to collapse
Polish language doesn't have translated settings too So i'm waiting for new version, thanks

pianistaPL said:
Polish language doesn't have translated settings too So i'm waiting for new version, thanks
Click to expand...
Click to collapse
Thanks for the heads-up, looks like it's ALL the translations for Settings, dang!

Project treble?

Is this project treble?

No

halleyrokz said:
Is this project treble?
Click to expand...
Click to collapse
That is the security patch level of android. You can get more info about project treble here.

For everyone getting excited over Treble should keep this in mind
"Project Treble doesn’t necessarily mean that all handsets will see updates instantaneously, as Google is not handling them directly. OEMs are still free to tweak and skin the OS, as well as embed their own software into the Android OS release. So there’s still going to be some time taken for OEMs to build and test their own particular take on Android."

zelendel said:
For everyone getting excited over Treble should keep this in mind
"Project Treble doesn’t necessarily mean that all handsets will see updates instantaneously, as Google is not handling them directly. OEMs are still free to tweak and skin the OS, as well as embed their own software into the Android OS release. So there’s still going to be some time taken for OEMs to build and test their own particular take on Android."
Click to expand...
Click to collapse
Spot on. Treble just eliminates the need for new drivers, so OEMs don't need to wait for part manufacturers (like Qualcomm). But OEMs (Samsung, LG,...) are still the main culprit when it comes to wait times or not getting updates at all.
If community can make a custom ROM for a 5+ year old device, so can an OEM. Drivers are obviously there, they're just not interested in updating anything for more than 2 years (even less in case of low and mid range devices). Treble can't change that.
The only real solution would be "one size fits all" system, that gets pushed directly by Google to ALL devices - like desktop systems. But that would probably be way to big for available storage on phones ...
Sent from my OnePlus 3 using Tapatalk

Explorer23 said:
The only real solution would be "one size fits all" system, that gets pushed directly by Google to ALL devices - like desktop systems. But that would probably be way to big for available storage on phones ...
Click to expand...
Click to collapse
We're going very offtopic here, but the topic interests me so, eh.
If we're talking about size here, we can follow a method that has been used in Linux live systems for a while now: a tarred (.tar) or squashed (squashfs) images. These provide a small yet ”fast enough” images that can be smaller than their uncompressed counterpart. Size is not of the constraint nowadays with these at developers disposal.
Alternatively, you can have a system that Treble tries to achieve: a base image (AOSP), OEM-specific changes and drivers, and abstraction for said drivers and changes. This system still relies on OEMs (and SoC manufacturers to an extent) to actively update their changes to the base system (and we know how lazy some OEMs can be with their updates).
But this is very offtopic, so let me offset the talk a little.
------------
To OP: No, that is not Treble. Treble isn't something you can quite see in user space (i.e Settings app). What you're pointing out is the security patch level, that is, how "updated" your current system are to the security patches Google are providing.
The level is laid out in date, so "November 1 2017" would be a fairly recent update. These patches get updated monthly, and seeing that you're using OxygenOS, means that you'll have to wait for OnePlus to push the security update after Google pushes them.

F4uzan said:
We're going very offtopic here, but the topic interests me so, eh.
If we're talking about size here, we can follow a method that has been used in Linux live systems for a while now: a tarred (.tar) or squashed (squashfs) images. These provide a small yet ”fast enough” images that can be smaller than their uncompressed counterpart. Size is not of the constraint nowadays with these at developers disposal.
Alternatively, you can have a system that Treble tries to achieve: a base image (AOSP), OEM-specific changes and drivers, and abstraction for said drivers and changes. This system still relies on OEMs (and SoC manufacturers to an extent) to actively update their changes to the base system (and we know how lazy some OEMs can be with their updates).
But this is very offtopic, so let me offset the talk a little.
------------
To OP: No, that is not Treble. Treble isn't something you can quite see in user space (i.e Settings app). What you're pointing out is the security patch level, that is, how "updated" your current system are to the security patches Google are providing.
The level is laid out in date, so "November 1 2017" would be a fairly recent update. These patches get updated monthly, and seeing that you're using OxygenOS, means that you'll have to wait for OnePlus to push the security update after Google pushes them.
Click to expand...
Click to collapse
There never can be a one size fits all OS. Even Linux can't really pull that off for every device.
See this is another thing that will never happen. Oems will never upload their code changes to aosp as Google intends. Most of the time due to the fact that they don't write the code for the different parts like BT, Wifi chips etc. This code comes others which is closed sourced and paid for.
Treble will most likely never become much. Already too many people misunderstand what it does. That i can't blame people for. Things like the xda portal that are giving out bad info is gonna cause a huge amount of drama over it.

Why are you running a custom rom?

I wanted to GTFO Google and (ONE) single ROM has been developed for this phone on XDA without Gapps and it's not even maintained any more. I tried out Lineage with Micro G and I was pretty happy. I asked if anyone here would be interested in GrapheneOS and got no reply. I built it for myself and was happier with the spoofing in Lineage so I went back. But that brings me to the OP question...I guess I just don't understand why anyone would build a custom ROM that allows Google to spy on you completely unchecked. I thought I must have been insane since literally nobody here seemed to agree. Then I found this write up......I immediately decided to post it. Not because I want to piss people off. Not because I'm unappreciative. But because WTF ARE WE DOING??Why are we even running custom ROMS? Xposed came out and Google screwed us with SafetyNet. Then you had Substratum that got checked from Google but it's being "allowed" right now even though they tried to patch it out. Then Magisk comes and Google buys him out. This has always been a "cat vs mouse" game until recently. Now it's just a "cat vs customizable cat" game. Did we lose? Or is it that people would rather trade their privacy for convenience? The direction we are headed as a community is allowing Google to slowly close off and become Apple pt2 and nobody seems to mind much. But this is XDA! How will it exist without people caring about this?Here is part of the write up that applies specifically to the OnePlus7T. Hopefully I'm not alone. Hopefully we can get this train back off the tracks where it belongs. Barreling through the unknown in defiance of these huge entities trying to control you. Link is at the bottom of the write up.crDroidLineageOS-based custom ROM designed to increase performance and reliability over stock Android for your device while also attempting to bring many of the best features existing today, according to their intro & how I think its grammar should be.
Personal remarks: A very good heavyweight ROM (and the best Limbo ROM at the moment), burdened with a soydev website (at least there's no BlockAdBlock unlike Arrow) & lack of Vanilla/GApps enforcement in a way similar to Bootleggers - no Vanilla/GApps branding
Advantages:
Per-app data restriction (Pie, A10, A11)
Signature spoofing (A10 & A11: no toggle)
Inbuilt App Lock
Disadvantages:
No signature spoofing (Pie-only; forgiven & redacted starting with A10, 12/4/2020 build)
If you look at the official site, there's a screenshot that shows this feature, on a toggle. Should have been available at Settings > crDroid Settings > Miscellaneous; but it's not there.
Tested the 12/4/2020 build & found out that microG support is enabled without toggle. This anti-feature is redacted.
Poco X3(N) only (confirmed on 23/3/2021 build) - USB debugging enables itself on boot (redacted per 22/4/2021 7.5 build)
28/4/2021 Update : With inbuilt vendor on 22/4/2021 7.5 X3N build, USB debugging no longer self-enables on boot (it's enabled at 1st boot, but can be disabled without enabling itself on subsequent boots). Welp, guess it's like the F1's Pie era all over again, where most builds (especially userdebug ones) enable USB debugging on boot until developers starts to include vendor partition in their builds.
Poco F1 (A11) : No force encryption
No Vanilla/GApps enforcement, in addition to lack of Vanilla/GApps labeling
List of GApps-infested builds :
OnePlus 7T & 7T "Pro"
Not having an active TWRP development for a device does not excuse the maintainers for releasing GApps-only releases, unless they also make a Vanilla variant. And, since there is an active TWRP development, there shouldn't be any more reason to tolerate a lack of Vanilla build (other than the maintainer being too lazy / unwilling to develop a Vanilla build, in which case per should be replaced).
Poco F3 (switched to Vanilla builds as of 9/7/2021 builds, but still listed for reference)
Redmi K20 / Mi 9T (davinci) (Vanilla build available on GDrive, FWIW.)
OnePlus 9 "Pro"
When its non-"Pro" (the vanilla OnePlus 9) variant gets a Vanilla build (despite a lack of functional TWRP for either) there is no excuse to be lazy & provide GApps-only builds
Custom ROM List

Definitely. Yaap microG by John Galt is very good also. Omni microG is also good

I read through your entire post and while most of the things you have said could be attributed to a subjective basis depending on person to person basis but the overall idea has a couple of inconveniences that I would like to add some insight of my own and would like to explain without sounding too brash
This is just my own personal impression that I have witnessed being part of the greater Android ecosystem in general starting from the early days to where we are now
In my opinion, the lack of interest by developers that originally gave their time and effort into working hard and fixing things has generally not kept up with the pace of Google's development efforts to curb these "hacks". The cat and mouse game what the post you quoted said is nearly at an end. I think Google is winning with everything in broader terms and despite the conveniences offered by microG and custom roms using that implementation, it doesn't come close to what Google offers.
The hassle of finding workarounds to make even the basic of functionality to work on Android requires time and effort which as I have already said earlier, it's something no one can commit to these days. The "enthusiast" aspect of custom rom development has really taken a dive over the past few years as manufacturers generally offer good enough functionality (at least for my use case as I am heavily reliant on my phone for work and general personal use) and Android has come a long way since the early days.
All of what I said boils down to the cost of convenience vs concern for issues that are really issues for a specialist segment of users within the entire community. People de-google their phones to focus on privacy and prevent data mining from these data hungry corporations and I for one for wish I could have something that would decrease my overreliance on Google's services but it is just not possible as the majority of people just use their phones and expect things to work just like that. So, the long lived idea of if it ain't broke, don't fix it plays very well into this. The trouble is generally not worth the inconveniences that come with it. Lack of interest of users therefore means lack of options and thus a lack of development.
Here's my 2 cents

I think for devs or hobby-coders who do this for free, time is more valuable than the luxury of "privacy" (which doesn't really exist if you're using any form of social media, like XDA).
Things changed. Android is more polished now than the Nexus days.

Develop Bugs

welcome