[ROM][AOSP][6.0/7.1][K3.4] Unlegacy Android Project - Nexus 7 Original Development

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 the Nexus 7 (2012) include:
- Linux kernel 3.4.y (currently 3.4.113)
- BFQ IO scheduler (official kernel 3.4 release), set up so GUI processes have the highest priority
- F2FS support from kernel 4.9 (for /data only! no point of f2fs on /cache)
- 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
- We received some RIL bug reports on 3G variants - other than that, there are no known issues.
If you notice anything, be sure to report it in this thread. Stability is our main concern. While we're kind of busy, we usually read the thread and acknowledge the bug reports, even if we 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
We will 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 the second post). The aim of this project is to create a fast and stable ROM - although, one could use Xposed (or similar) to add extra features.
As usual, feedback is appreciated
XDA:DevDB Information
Unlegacy Android Project, ROM for the Nexus 7
Contributors
Ziyan, sheffzor
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 7.x Nougat
Version Information
Status: Stable
Created 2015-06-07
Last Updated 2017-12-23

---

Reserved
GApps
If you want to install GApps, we recommend Open GApps Pico.
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.
SafetyNet
The ROM should pass SafetyNet after installing GApps, without anything else. Keep in mind that installing extra stuff (SU, ...) might make it fail!
Rooting
You can flash the latest Magisk to get rooted.

---

Yesss is it snappy?

---

I was able to workaround the panel errors in the kernel - PWM control isn't working for some reason, so I had to use an alternative method to enable backlight, meaning it's using a fixed brightness. This isn't important right now (I want the core functionality to work before making stuff bug-free). I also forward-ported the touchscreen driver, so it's mostly working now - it still needs some fixups for 3.4. My next goal: audio and video decoding.
View attachment 3350098
anzi2001 said:
Yesss is it snappy?
Click to expand...
Click to collapse
Kernel/common android-3.4 branch could be merged into the kernel after it's fixed up, which will surely make it more efficient.

---

great, i wish you very much success :fingers-crossed:

---

While I try to do my best to keep myself from working on this 24/7, I couldn't resist... and fixed camera, video encoding and decoding, and audio (party, just the rear speaker works yet) also works now :silly: what this means? Blobs won't stop us, as they work fine on 3.4 as well.

---

Man you really are doing the job man any way i can help? i want to help

---

I'm so subscribing to this
I never thought we will get to
3.4

---

Subbed for sure. Very good news here.

---

Will definitely be keeping my eye on this one.

---

Today, I fixed sensors and panel PWM control (meaning brightness can be changed, auto-brightness works fine as well), and Bluetooth. Doing this alone requires a huge amount of time and work, as there's still a zillion thing to do, like merging in android-3.4, fixing up touchscreen (there are ghost touches and packet spams slowing down the kernel), fixing up suspend (need to press power button multiple times to wake up), audio, otg, etc...

---

No one else has tried building this then?? I thought this thread would boom after all the excitement for 3.4 on the 3.1 bringup thread. Anyway, Ziyanns just helped me fix this booting for both pcbs now so it should boot for everyone.

---

HTCDreamOn said:
No one else has tried building this then?? I thought this thread would boom after all the excitement for 3.4 on the 3.1 bringup thread. Anyway, Ziyanns just helped me fix this booting for both pcbs now so it should boot for everyone.
Click to expand...
Click to collapse
do you happen to have an img for testing?

---

Ophidian_DarkCore said:
do you happen to have an img for testing?
Click to expand...
Click to collapse
No, you need to hardcode your pcbid and projectid into board-grouper-misc.c atm which you can get from last kmsg (just grep for those things when catting a kmsg in adb shell).

---

Can i help somehow? i want to help lol

---

I want to help too !

---

HTCDreamOn said:
No one else has tried building this then?? I thought this thread would boom after all the excitement for 3.4 on the 3.1 bringup thread. Anyway, Ziyanns just helped me fix this booting for both pcbs now so it should boot for everyone.
Click to expand...
Click to collapse
I tried to build (img) but without success...As you said on a recent post you cannot build .img but you need to to hardcode your pcbid and projectid into board-grouper-misc.c but i dont know how to do it :S

---

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

---

i will subscribe to this thread, just to see how it goes...

---

It was a long time since i was not so excited in xda