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

[ROM][NZH54D][2021/09/05][Asus Nexus 7 2012 WiFi/3G][F2FS/EXT4]Android 7.x AOSP

Search This thread

dan20385

New member
Sep 23, 2021
3
1
@dan20385 probably the device is still compiling / optimizing the applications and services in background. Wait a bit until compilation is finished then the device should be much more responsive. I noticed, too, that Gapps and Google services became bigger and bigger over the last time and especially on the first boot it takes a while until everything is compiled.
Thank you - I will let it rest for a while and see how it goes!
 
  • Like
Reactions: AndDiSa

Flounderist

Senior Member
Jan 7, 2016
848
410
Cork
I finally found the time to upgrade from April build and I tried to flash the ROM only, no Micro-G, no GApps.
I use the device like a monitor for my USB inspection camera so I don't need the G framework at all.
I added 3 apps from apkpure (Endoscope, Nova 6 and Pixel icon pack) and...they work! :)

The tablet is very fast and responsive. No more lags at all on the UI.
Of course I would recommend this solution for those who have a very specific use of the device, like me.

@AndDiSa do you think that resizing the System partition may help in keeping the device snappy using GApps? How could the difference between GApps and no-GApps be so dramatic?
 

AndDiSa

Senior Member
Dec 2, 2009
3,539
4,715
Heidelberg
@Flounderist I don't think that resizing the system partition does really help to keep the device snappier when having GApps installed as all applications (independently whether they are installed on /system or installed on /data) are compiled and optimized and the result is stored in dalvik-cache

Resizing /system only helps to get more Google services / applications pre-installed ...
Google services and applications became bigger and bigger over the time and in addition Google is removing more and more functionality from the prebuild ROM into updateable services they have under their control. That is the main reason why older devices having GApps installed are slowing down over the time.
 

Portgas D. Ace

Recognized Contributor
Jun 12, 2014
4,345
3,143
Bergisches Land
If you really need Google services, go for microG. It doesn't slow down the tablet into oblivion like the "original" GApps do, yet still provides nearly the same functionality. But keep in mind that Google can block your Google account at their will, if you decide to use your account with microG.
 
  • Like
Reactions: ruydevorde

LesGirauds

Senior Member
Jul 27, 2013
310
145
France
Nexus 7
OnePlus X
...and to add to the above, there is no need to use your google acount with microg. If you want to access your google account content (mail, calendar, whatever) there are often workarounds.

You can even use some google apps (calendar, maps) on microg - you just don't log them in.

There are some apps that need google to run but you can often find google-free alternatives.The only thing you will loose (ime) is any apps that you have purchased through google - you cannot activate paid-for apps without gplay (and so the entire google framework)
 

Portgas D. Ace

Recognized Contributor
Jun 12, 2014
4,345
3,143
Bergisches Land
...The only thing you will loose (ime) is any apps that you have purchased through google - you cannot activate paid-for apps without gplay (and so the entire google framework)
You can use Aurora Store to download paid apps if you log in via the same account that you have used to purchase those apps.

If this is too much of a risk for you, there is a somewhat inconvenient workaround for apps that you have purchased via Play Store (not for all apps, but for some). Only thing you need is root plus a root file manager to grab those paid apk's from your /data directory and sideload them to your Google-free device.

As said before, it works for some apps, but most of the paid apps are tied to your Google credentials and will check if Google services are available and if the correct account is logged in.
 

LesGirauds

Senior Member
Jul 27, 2013
310
145
France
Nexus 7
OnePlus X
You can use Aurora Store to download paid apps if you log in via the same account that you have used to purchase those apps.

If this is too much of a risk for you, there is a somewhat inconvenient workaround for apps that you have purchased via Play Store (not for all apps, but for some). Only thing you need is root plus a root file manager to grab those paid apk's from your /data directory and sideload them to your Google-free device.

As said before, it works for some apps, but most of the paid apps are tied to your Google credentials and will check if Google services are available and if the correct account is logged in.
Thanks for the info, I didn't know that.

I'd (taken a risk and) tried the Aurora store method with one app I've purchased and it didn't work - so perhaps I just got unlucky and it was an app it wouldn't work with. I didn't try it on any other apps and, as didn't want to risk google account suspension (or whatever), I logged microg out of google.

The sideload trick though, I knew nothing about, I might give it a go (though it means retrieving the paid apks from a 'gapped' ROM backup!)
 

Portgas D. Ace

Recognized Contributor
Jun 12, 2014
4,345
3,143
Bergisches Land
Thanks for the info, I didn't know that.

I'd (taken a risk and) tried the Aurora store method with one app I've purchased and it didn't work - so perhaps I just got unlucky and it was an app it wouldn't work with. I didn't try it on any other apps and, as didn't want to risk google account suspension (or whatever), I logged microg out of google.

The sideload trick though, I knew nothing about, I might give it a go (though it means retrieving the paid apks from a 'gapped' ROM backup!)
For further reference, here is the Aurora Store FAQ:

https://auroraoss.com/faq/#accounts

Seems that downloading paid apps which you have purchased before via Google Play Store "should" be able to be downloaded via Aurora. If this doesn't work, you might want to try the sideload trick in combination with being logged in with your account (risky, risky :sneaky: )
 
  • Like
Reactions: AndDiSa

Sir Charles82

Senior Member
Sep 7, 2015
51
11
Vienna
Concerning the speed of the N7 (grouper), I have the app "Trimmer (fstrim)" installed and have it trim with every bootup (so it was recommended some years ago). I think this makes the N7 snappier.
 

AndDiSa

Senior Member
Dec 2, 2009
3,539
4,715
Heidelberg
New Versions 7.1.2 (2021-10) are available

Hi guys, a new release but only a few changes, i.e. the security paches for October 2021.
The full list of changes, as always, you can find in my Github repos

The "standard" versions for Grouper / Tilapia are available for download:
aosp_grouper-7.1.2-ota-20211006.eng.ds.zip (MD5: b57ddee37bad03f59e2eff562076b027)
aosp_tilapia-7.1.2-ota-20211006.eng.ds.zip (MD5: 65ea4ea189a41ec7792fb13a876157da)

as well as the MicroG-Patched images:
aosp_grouper-7.1.2-mg-ota-20211006.eng.ds.zip (MD5: d5d788b3fa735c3e57d9f0fb562e15f6)
aosp_tilapia-7.1.2-mg-ota-20211006.eng.ds.zip (MD5: 643f8fdf2195c2395f788611578c108e)

I quickly tested the ROM and didn't find issues, nevertheless I will wait for feedback from the community before I'll add the new version to the OP.

If you report a successful (or unsuccessful :)) installation, please note which version (Grouper / Tilapia, with or without MicroG-patch) you have installed and tested. Thank you very much!
Stay safe!
 

AndDiSa

Senior Member
Dec 2, 2009
3,539
4,715
Heidelberg
@Sir Charles82 thanks for the hint. Trim should run every three days automatically (if I remember well :)), but running ftrim manually / more frequently doesn't harm and might improve performance in some circumstances, epecially when you have many write operations on your device.
 
  • Like
Reactions: Sir Charles82

marty_bebop

Member
Oct 23, 2016
33
15
New Versions 7.1.2 (2021-10) are available

Hi guys, a new release but only a few changes, i.e. the security paches for October 2021.
The full list of changes, as always, you can find in my Github repos

The "standard" versions for Grouper / Tilapia are available for download:
aosp_grouper-7.1.2-ota-20211006.eng.ds.zip (MD5: b57ddee37bad03f59e2eff562076b027)
aosp_tilapia-7.1.2-ota-20211006.eng.ds.zip (MD5: 65ea4ea189a41ec7792fb13a876157da)

as well as the MicroG-Patched images:
aosp_grouper-7.1.2-mg-ota-20211006.eng.ds.zip (MD5: d5d788b3fa735c3e57d9f0fb562e15f6)
aosp_tilapia-7.1.2-mg-ota-20211006.eng.ds.zip (MD5: 643f8fdf2195c2395f788611578c108e)

I quickly tested the ROM and didn't find issues, nevertheless I will wait for feedback from the community before I'll add the new version to the OP.

If you report a successful (or unsuccessful :)) installation, please note which version (Grouper / Tilapia, with or without MicroG-patch) you have installed and tested. Thank you very much!
Stay safe!
Grouper: MicroG, Magisk 23, Aurora Store.
Working well.
Many thanks.
 
  • Like
Reactions: AndDiSa

LesGirauds

Senior Member
Jul 27, 2013
310
145
France
Nexus 7
OnePlus X
I installed the latest 20211006 mg build and I am having trouble patching the boot.img using Magisk. For some strange reason, the LET'S Go button in Magisk is greyed out. Has anyone have this issue? I am not sure what I have done wrong.
yes, it's happened to me too. Just flash the Magisk zip from recovery.

(Edit: I always flash the same Magisk version (21.4) when I flash a new ROM then I use the Magisk app to install the latest version)
 
  • Like
Reactions: dookie23

LesGirauds

Senior Member
Jul 27, 2013
310
145
France
Nexus 7
OnePlus X
@dookie23 @LesGirauds it's long time that I did not install Magisk on my device. There is a chance that you need to grant probably file permissions to the Magisk app. Unfortunately I cannot test as I am out for some days but I will do some tests and add some hints to the OP.
ah yes, I see that that's possible. dirty flashing the ROM would 'reset' the apps privileges. I'll look at that next time I flash (next month?)

thanks for the advice (y) (y)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 14
    New Versions 7.1.2 (2021-09) with several changes are available

    Hi guys, I picked up a bit of pace and beside adding the new security patches for September 2021 I added a bunch of kernel patches, especially CVE-patches mitigating potential security issues.
    In detail I did the following modifications / improvements:

    • I fixed the crash of the clock application reported by @momentoid
    • I added a missing patch for external/sqlite
    • I applied the security fixes for September 2021
    • I optimized the kernel config settings, especially removed some superflouus settings
    • I applied / backported a bunch of CVE-kernel patches. Please have a look at the sources in Github to see the whole list of changes
    The full list of changes you can find in my Github repos

    Regarding the wpa_supplicant.conf changes it looks to me that there is some other modification / setting needed. A few days ago I updated my router to OpenWRT 21.02 (which has the build-in possibility to enable WPA3) and I noticed connection issues when I was using WPA3 or WPA2/WPA3 in parallel. Even setting pmf=0 in /data/misc/wifi/wpa_supplicant.conf had no effect as it was overwritten immediately as soon as I was switching on WiFi. Only switching back to WPA2 only resolved the issue for me. I'll further analyze the WPA3 compatibility issue and I will see whether I can find improvements here.

    The "standard" versions for Grouper / Tilapia are available for download:
    aosp_grouper-7.1.2-ota-20210917.eng.ds.zip (MD5: e0381d56f4f1c11c095a9d0057c50699)
    aosp_tilapia-7.1.2-ota-20210917.eng.ds.zip (MD5: 7a6b6d37b2f8ee5964c8d9164305a846)

    as well as the MicroG-Patched images:
    aosp_grouper-7.1.2-mg-ota-20210917.eng.ds.zip (MD5: 9ea020054cfbe1b646e1c9cdcb11358d)
    aosp_tilapia-7.1.2-mg-ota-20210917.eng.ds.zip (MD5: 617fbfddc39174fcc0486de8081448e7)

    I quickly tested the ROM and didn't find issues, nevertheless I will wait for feedback from the community before I'll add the new version to the OP.

    If you report a successful (or unsuccessful :)) installation, please note which version (Grouper / Tilapia, with or without MicroG-patch) you have installed and tested. Thank you very much!
    Stay safe!
    6
    New Versions 7.1.2 (2021-10) are available

    Hi guys, a new release but only a few changes, i.e. the security paches for October 2021.
    The full list of changes, as always, you can find in my Github repos

    The "standard" versions for Grouper / Tilapia are available for download:
    aosp_grouper-7.1.2-ota-20211006.eng.ds.zip (MD5: b57ddee37bad03f59e2eff562076b027)
    aosp_tilapia-7.1.2-ota-20211006.eng.ds.zip (MD5: 65ea4ea189a41ec7792fb13a876157da)

    as well as the MicroG-Patched images:
    aosp_grouper-7.1.2-mg-ota-20211006.eng.ds.zip (MD5: d5d788b3fa735c3e57d9f0fb562e15f6)
    aosp_tilapia-7.1.2-mg-ota-20211006.eng.ds.zip (MD5: 643f8fdf2195c2395f788611578c108e)

    I quickly tested the ROM and didn't find issues, nevertheless I will wait for feedback from the community before I'll add the new version to the OP.

    If you report a successful (or unsuccessful :)) installation, please note which version (Grouper / Tilapia, with or without MicroG-patch) you have installed and tested. Thank you very much!
    Stay safe!
    3
    ...The only thing you will loose (ime) is any apps that you have purchased through google - you cannot activate paid-for apps without gplay (and so the entire google framework)
    You can use Aurora Store to download paid apps if you log in via the same account that you have used to purchase those apps.

    If this is too much of a risk for you, there is a somewhat inconvenient workaround for apps that you have purchased via Play Store (not for all apps, but for some). Only thing you need is root plus a root file manager to grab those paid apk's from your /data directory and sideload them to your Google-free device.

    As said before, it works for some apps, but most of the paid apps are tied to your Google credentials and will check if Google services are available and if the correct account is logged in.
    3
    Sorry to derail the thread, I literally just found my old nexus 7 tablet after who knows how many years. Is there a guide available to install the latest custom rom listed above? Appreciate any guidance, thanks!
    Welcome!
    We're on page 242 of this thread. Page 1 has detailed steps to install this awesome ROM.

    Depending on the level of your knowledge links to the latest version, Sep (2021-09) ROM are posted on Sep 19, 2021, on this page. A few posts after the ROM links, there is a post with links for a Config file posted on Sep 22, 2021.

    Hope this helps.
    3
    For those who have issues with installing latest Gapps, you can try to copy the attached gapps-config files into the same directory where the gapps installation packages is copied
    I.e. something like

    /sdcard/open_gapps-arm-7.1-pico-20210922.zip
    /sdcard/gapps-config-tilapia.txt
    /sdcard/gapps-config-grouper.txt

    and then try to start the installation again. Error 70 should be fixed.

    Edit: I just added this hint to notes / FAQ in the second post of this thread.
  • 311
    This thread is about installing and using AOSP 7.x (Nougat) ROM for the ASUS Nexus 7 Grouper / Tilapia devices.

    Asus - Model names

    Grouper = Asus Nexus 7 2012 WiFi
    Tilapia = Asus Nexus 7 2012 3G


    Initial Setup Installation

    1. Update Recovery to TWRP 3.5.2-9 for Grouper resp. TWRP 3.5.2-9 for Tilapia
    2. Boot into Recovery
    3. Factory Reset (only needed if you are not already on Android 7.x AOSP)
    4. Install 7.1.2 Grouper OTA-Package (Build 20210917) (md5 :e0381d56f4f1c11c095a9d0057c50699)
      or
    5. Install 7.1.2 Tilapia OTA-Package (Build 20210017) (md5: 7a6b6d37b2f8ee5964c8d9164305a846)
    6. Reboot into recovery
    7. Install Open GApps (arm/7.1/pico)
      (if you have issues regarding the size of the GApps please refer to the next post)

    [*]To get root access, I suggest to use either Magisk (V21.4) and Magsik Manager (V8.0.7) the "old" version of Magisk, or the new unified Magisk (V22.1)

    Do not install Magisk on initial setup as it might lead to issues. Start the ROM without having root access the first time and install Magisk in a second step.

    If you are already on Android 7.x AOSP, it's sufficient to do the follwowing steps:

    Update Installation
    • Boot into Recovery
      • Install 7.1.2 Grouper OTA-Package (Build 20210917) (md5 :e0381d56f4f1c11c095a9d0057c50699)
        or
      • Install 7.1.2 Tilapia OTA-Package (Build 20210017) (md5: 7a6b6d37b2f8ee5964c8d9164305a846)
      • Reboot into recovery
      • Install Open GApps (arm/7.1/pico)
      • Wipe cache/dalvik-cache (optional, but suggested)
      • reboot

    Important: For more detailed installation instructions please refer to the next post
    Important: First boot after upgrading will take a bit longer (stays on ANDROID) because of art optimizations

    flash and use on your own risk!


    CREDITS,
    AOSP/Google, LineageOS, Ziyann for setting up the Grouper-AOSP repository and his Unlegacy Android project, daniel_hk for some hints how to get the 3.1 kernel running with N, timduru for his work on the Asus Transformer, Timur Mehrvarz for his work on the tegra kernel, Francisco Franco for his kernel work in general

    Bugs:
    • please report

    Latest Changes
    • 20210917(AOSP 7.1.2)
      • I fixed the crash of the clock application reported by @momentoid
      • I added a missing patch for external/sqlite
      • I applied the security fixes for September 2021
      • I optimized the kernel config settings, especially removed some superflouus settings
      • I applied / backported a bunch of CVE-kernel patches. Please have a look at the sources in Github to see the whole list of changes

    Latest version with MicroG-patch applied to them:
    aosp_grouper-7.1.2-mg-ota-20210917.eng.ds.zip (MD5: 9ea020054cfbe1b646e1c9cdcb11358d)
    aosp_tilapia-7.1.2-mg-ota-20210917.eng.ds.zip (MD5: 617fbfddc39174fcc0486de8081448e7)


    Changelog
    Please refer to the changes found in the github repos

    All ota packages can be found here:
    AndDiSa ROM files repository

    Sources

    https://github.com/AndDiSa

    If you would like to build from the sources, you can do so by cloning and build from repositories:
    but please take in mind that you need to have some free space (>= 100 GB) and some time ...


    XDA:DevDB Information
    Android 7.x AOSP, ROM for the Nexus 7

    Contributors
    AndDiSa
    Source Code: https://github.com/AndDiSa?tab=repositories

    ROM OS Version: 7.x Nougat
    ROM Kernel: Linux 3.1.x
    Based On: AOSP

    Version Information
    Status:
    Stable

    Created 2016-09-23
    Last Updated 2021-03-05
    65
    Please note:
    • the system partition is already quite full which leads to the problem that gapps probably will not install correctly and that may lead to weired problems (apps closing / not showing up correctly / ...). I suggest to use the dynamic gapps package linked above. In addition I suggest you to erase the system partition completely before applying the OTA package
    • If you get "Error 7" when trying to flash the ROM directly after upgrading to TWRP 3.5.2-9, wipe the Boot, System and Cache partition and clean dalvik-cache, then re-boot to Recovery and try again (you will not loose any data as long as you do not wipe the Data partition).
    • If you get "Error 70" when installing GApps copy the attached gapps-config files into the same directory where the gapps installation packages is copiedI.e. something like

      /sdcard/open_gapps-arm-7.1-pico-20210922.zip
      /sdcard/gapps-config-tilapia.txt
      /sdcard/gapps-config-grouper.txt

      and then try to start the installation again. Error 70 should be fixed.

    Some additional hints
    • If you are in a bootloop which shows to Google logo again and again, it's sufficient to hold vol- while booting. The next bootloop will boot into bootloader.
    • If you are in a bootloop which shows the ANDROID splash screen continuusly, connect your device to your PC and enter
      Code:
      adb reboot bootloader
      After a few seconds the device should show up the bootloader screen
    62
    Hi guys,

    first of all I would like to thank all of you for your support you offered to me in the last days and I really feel honoured that so many of your would like to support / help me so that I am able to continue the development for the Nexus 7.
    I've got many offers for a "new" Nexus device from all over the world which I really didn't expect. I was really torn between continuing and stepping out. I've thought very much about pros and cons and it wasn't an easy decision especially if you get so much positive feedback. Thank you again!

    Finally I've decided to stop development for the Nexus 7 (at least for the moment). There are several other projects (not all of them related to Android) I've in mind and probably this now was a broad hint to start with something different. I've uploaded the sources of the ROMs latest version (inc. security patches for June 2019) to Github and tested together with @fidoedidoe whether all needed repos and changes are consistent and that one can build the ROM from those repos without the need of doing additional modifications or patches. The build should run smoothly after synchronizing everything. I will also support and help everybody who would like to step in and continue the builds.
    I know there are several people interested in building the ROM from sources. Probably there is someone (or probably even a group) who would like to continue ...
    Cheers,
    AndDiSa
    55
    2019/02/05 - release for Grouper and Tilapia uploaded

    I've just uploded the latest version of the ROM for Grouper and Tilapia. As always the Android security issues listed in the latest Android Security Bulletin are patched in this ROM.

    Beside that once again I've worked much on the kernel side. Some features are added (multiple binder devices, alarm timer device, ...) and some bugs have been fixed.
    I am still working together with @OlliWi on the slow charging issue which occurs from time to time. Even if I was able to get charging currents up to 1500mA while the device was connected to a charger, we still have the impression that the cable / charger detection needs to be improved. We are on it ...

    Those of you who are familiar with the installation process of the ROM can download directly from here, otherwise please first read the instructions in the OP

    7.1.2 Grouper OTA-Package (Build 20190209) (md5: 885e601a06a2104628a1e450b73f3a18)
    7.1.2 Tilapia OTA-Package (Build 20190209) (md5: 8e4c0e1955ecc0bb65a51582bb01f779)

    And finally as always: flash on your own risk ... ;)
    52
    New year ... new security fixes (2019/01/05)

    Hi guys,

    I've just uploaded a new version of the ROM for our beloved Nexus 7 (Grouper / Tilapia) having the January 2019 security fixed applied to it.

    Beside that I found a bug causing bootloops on initial install / after wiping dalvik. This was caused by zygote not having enough memory available to create the boot.jar on the fly. To fix this issue, I am doing a dex-preopt for the boot image on compile time now which leads to a slightly larger image but improves initial boot time a bit, too.

    To get more memory free on the /system partition, I debloated the ROM a bit, e.g. removed the Browser2, LegacyCamera, Music and Calendar apps as some of them even didn't work fully. There are several alternatives available in several stores which you can install if you need them. Probably most of you do not even notice that these apps were removed.

    Most changes were applied to the kernel. I tested the changes in the last 4 weeks but as I have a Grouper device only and I cannot test each functionality I cannot exclude that something doesn't work as expected. So please file a bug report (best with logcat and a meaningful bug description) if you find some unexpected behaviour and I will have a look at it.

    The most important fix here is probably the improved charging behaviour (many thanks to @OlliWi who provided with fruitful analysis and hints and pushed me to have a deeper look at this issue).
    To get a faster charging of the device, do not boot with a USB cable connected as this prevents the device to charge with more than 500mA (or at least disconnect and re-connect the cable after the device booted).

    I've updated the links in the OP, so you can download the latest version from there.

    Happy new year to all of you!