• If you are experiencing issues logging in, we moved to a new and more secure software and older account passwords were not able to be migrated. We recommend trying to reset your password, then contacting us if there are issues.
  • Nearly done! Migration cleanup is mostly done. There are a small number of issues left that we continue to work on, but all the heavy lifting is done. We still would love to hear feedback over at this thread and also check out the new XDA app! Thanks and we hope you enjoy the new forums, and thanks for your support of XDA <3

[ROM][AOSP][6.0/7.1/8.1 RC/9.0 BETA] Unlegacy Android Project

amaces

Senior Member
Feb 2, 2012
478
2,751
0
The Unlegacy Android Project​
Introduction
Unlegacy-Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy Android was born. In our opinion, these ROMs are how the official updates would look.

On top of AOSP, we only include changes which are necessary to support the hardware, be secure, and get acceptable performance. Current features for hammerhead include:
  • BFQ IO scheduler (official kernel 3.4 release), set up so GUI processes have the highest priority
  • Volume button wakeup (setprop persist.wm.volume_wake_screen 1)
  • Last upstream (kernel/msm) hammerhead kernel tag merged
  • Charging LED control (setprop persist.sys.led_on_charger 0)
  • Enhanced backlight map for lower min brightness
  • Night display blue light filter (GLES-based)
  • KCAL & PCC color temperature interfaces
  • Other security patches & minor bug fixes
  • F2FS support from K4.4 backports
  • SELinux in Enforcing mode
Installation
It's important that /system needs to be unmounted before installing the ROM - some recoveries tend to leave it mounted after performing operations on it.

If you're planning to install GApps, be sure to read the second post.

Aside from these, installation and upgrading is no different than on other ROMs.

Problems
  • No known issues on Nougat builds
  • See post #3 for Oreo/Pie notes
If you notice anything, be sure to report it in this thread. Stability is our main concern. While it may takes some time, I usually read the thread and acknowledge the bug reports, even if I don't reply directly to them.

Downloads
See: http://builds.unlegacy-android.org. Our automated builds ensure that we always have the latest Android security patches merged in, without having to manually start and upload builds :)
Also, we'll have a built-in OTA updater (just like stock) soon (it's a work in progress).

Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices (see second post). The aim of this project is to create a fast and stable ROM, as close to AOSP as possible without diminishing usability. Occasionally, small non-AOSP features may be implemented, provided there is a clear need and they make sense on hammerhead.

XDA:DevDB Information
Unlegacy Android Project, ROM for the Google Nexus 5

Contributors
amaces, Ziyan
Source Code: https://github.com/Unlegacy-Android

ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
Based On: AOSP

Version Information
Status: Stable
Current Stable Version: 7.1.2
Stable Release Date: 2017-04-18
Current Beta Version: 9.0.0
Beta Release Date: 2017-10-02

Created 2017-04-21
Last Updated 2018-10-30
 
Last edited:

amaces

Senior Member
Feb 2, 2012
478
2,751
0
GApps
If you want to install GApps, we recommend micro packages on N builds (e.g., Open GApps), and pico otherwise.

An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. If you experience any issues with the Google applications, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.

Stock-like setup
Disable the following built-in (AOSP) apps:
- Android keyboard (once you installed Gboard)
- Browser
- Calculator
- Camera
- Clock
- Email
- Gallery

Install the following apps from the Play store:
- Google Photos (https://play.google.com/store/apps/details?id=com.google.android.apps.photos)
- Calculator (https://play.google.com/store/apps/details?id=com.google.android.calculator)
- Chrome (https://play.google.com/store/apps/details?id=com.android.chrome)
- Clock (https://play.google.com/store/apps/details?id=com.google.android.deskclock)
- Gboard (https://play.google.com/store/apps/details?id=com.google.android.inputmethod.latin)
- Gmail (https://play.google.com/store/apps/details?id=com.google.android.gm)
- Google Calendar (https://play.google.com/store/apps/details?id=com.google.android.calendar)
- Google Camera (https://play.google.com/store/apps/details?id=com.google.android.GoogleCamera)
- Google Now Launcher (https://play.google.com/store/apps/details?id=com.google.android.launcher)

Rooting
You can flash the latest SuperUser (phh's open source fork), Chainfire's SuperSU, or Magisk to get rooted.
 
Last edited:

amaces

Senior Member
Feb 2, 2012
478
2,751
0
Oreo/Pie Status & CAF Notes

Oreo 8.1 builds are almost bug-free at this point, but still tagged as experimental. While last issues are sorted out, I will trigger manual builds, also published at https://builds.unlegacy-android.org/aosp-8.1/hammerhead.
To my knowledge, these are the remaining issues:
  • Bluetooth HFP speaker (mono/SCO) output is garbled. This seems related to a more general issue with audio effect/ACDB blobs.
Once all visible issues are fixed, and stability is comparable to Nougat builds, I'll switch on official builds on our Jenkins server.

Pie 9.0 builds are also becoming fully usable. Current builds have the same one remaining HFP bug described above.

Beyond "official" experimental builds, I post personal builds (including CAF experiments) in the hammerhead folder here.

Regarding sources for the WIP CAF kernel-based builds, see https://github.com/airend/android_kernel_lge_hammerhead/commits/tmp/caf+113+common. Corresponding device tree is still in rough shape and not uploaded yet, but assuming everything goes well, it'll replace current device tree when it's ready.
 
Last edited:

Nexive

Senior Member
Feb 12, 2012
317
199
43
Brussels
I've used the 05/04 build for 2 days a few weeks ago and it was a great rom.
The only issue I came across back then was that it has the green flickering when recording videos.

It's nice that the project has a XDA thread now and I gonna test this rom asap.
Thanks for keeping our good old Nexus 5 up to date. :)
 
  • Like
Reactions: RoxAbout and amaces

alessio89g

Senior Member
Mar 22, 2014
445
99
28
Does it have issues with network location (Battery saver location)?
Some AOSP-based ROMs have this issue, so many apps (Chronus, Google Fit, f.lux, Instagram) can't get location.
 

alessio89g

Senior Member
Mar 22, 2014
445
99
28
I've flashed it for about half a day, and it's very promising, it seems a great ROM!

I've noticed only three defects:

- The blue light filter (Night mode) is missing;
- With stock kernel, SuperSU will be in system mode;
- The Clock app crashes if you try to add another Time zone in the main screen.

Everything else works fine.
 
  • Like
Reactions: bricemx
Nov 29, 2012
10
2
3
Belo Horizonte
Thanks for the ROM guys!

When I flash Open Gapps this message appears:

"This Gapps pkg is for Android 7.1.x ONLY
Please download the correct version for you ROM: 5.1.1 (SDK 22)"

I've flashed build ua_hammerhead-7.1.2-20170423031839 before gapps
 
Last edited: