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

Search This thread

camp0s

Senior Member
Jun 13, 2011
84
7
Please note:
..cut..
  • 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.
..cut..

Just a little note from my experience: it did happen to me, always used the Pico version and when I updated during the holydays (from maybe this spring) this time this solution worked for me (y)(y)(y)
 

BeeJ1109

Senior Member
Sep 26, 2015
176
49
Adelaide
Hi campOs,
Please read the info on Page 1. Latest Pico Gapps is too large that is error 70 means,
Download the modified version, smaller will then work.
After bootup, you can add any Google apps to update to latest version.
Worked for me on my Tilapia Tab.
Cheers BJ
 
  • Like
Reactions: dark0shark

breaktheblock

Senior Member
Oct 31, 2015
62
2
Hi All,

A general question how are people finding battery life?
I have previously use this ROM on grouper and used to get around 20 days in standby if not used with battery saver on, now it is a lot less, is this due to all of the patches that have been added or maybe my grouper battery is dying?
 

AndDiSa

Senior Member
Dec 2, 2009
3,641
4,886
Heidelberg
@breaktheblock I noticed that battery live depends on Google Services (not sure whether you have installed them or not), but if for example syncing calendar / contacts / ... are stuck (for what ever reason) battery is running out very fast.
I from my side did not notice a big change in power consumption within the last weeks / months ... but I also need to say that I also did not really test that behaviour, as my device is frequently connected to the PC and so it's automatically re-charging.
 

breaktheblock

Senior Member
Oct 31, 2015
62
2
@breaktheblock I noticed that battery live depends on Google Services (not sure whether you have installed them or not), but if for example syncing calendar / contacts / ... are stuck (for what ever reason) battery is running out very fast.
I from my side did not notice a big change in power consumption within the last weeks / months ... but I also need to say that I also did not really test that behaviour, as my device is frequently connected to the PC and so it's automatically re-charging.
@AndDiSa I only use the Rom with fdroid so no Google services. I run the fstrim app with SU from Magisk, the only other apps I have are red moon and Spotify. So I'm unsure why battery is so quick to run down (less than one day), previous builds the same so this is making me wonder if it is my battery.
 
Last edited:

breaktheblock

Senior Member
Oct 31, 2015
62
2
The latest after 1 day and 10 hours in battery saver mode the tablet estimates I have 6 days left. This is reduced from previous roms from this thread, as I have previous observed 18-20 days but still the battery is better than I thought at least at this moment.
When doing a wipe with TWRP does this wipe the "memory" of battery stats?
 

D F

Senior Member
Jan 21, 2012
408
30
I come from a Cyanogenmod version. I have installed it a few years ago. Battery life was awful with that version. It may have been I broke something during installation. This was the reason I haven't used the tablet too much. Now, it came back to life. With screen of, I can see an obvious improvement but that is because I had a defective installation, I guess. Now, with screen off, the battery stayed at 100% for a day and then, went to 99% after a day which is pretty normal for me.
So, I love this software version, I installed Spotify, Youtube and Youtube Music and I am thinking of using the tablet as an audio source for parties with friends,only provided battery life is good, because I need at least 4 hours of SOT. Good thing about my Grouper is that you can charge it while listening to music without other improvisation.

I found an issue though: bluetooth won't receive files and I can't connect the tablet to a bluetooth player. Is this something particular to my configuration, or a general bug?
 
  • Like
Reactions: AndDiSa

D F

Senior Member
Jan 21, 2012
408
30
I didn't, but today I managed to send and receive a picture. Problem is I still can't connect it to my player. It asks for a PIN code, despite the fact that the player is in pairing mode.
Where can I find the logs?
Also, what browser do you use with it? Brave is too slow.
 

Stephco03

Member
Aug 22, 2018
11
2
Hello,
The ROM installs without problem.
But I want install Opengapps, I have a error :
"Insufficient storage space avaible in system partition"
I took open gapps arm 7.1 pico 20220202
What should I do ? I am blocked :,(
Thanks you in advance for help me
 

D F

Senior Member
Jan 21, 2012
408
30
Hello,
The ROM installs without problem.
But I want install Opengapps, I have a error :
"Insufficient storage space avaible in system partition"
I took open gapps arm 7.1 pico 20220202
What should I do ? I am blocked :,(
Thanks you in advance for help me
Copy in the same folder with Gapps, the file in this post.
I had the exact same issue.
 

G_Bot

Member
Jul 4, 2020
29
12
Im using gapps with the microg package. I installed microg through magisk and im using nanolx patched playstore from github. Everything works, Gps Works, and all gapps and paid apps. and it has good battery life. Its easy to install through magisk microg installer zip. It is a great rom i use it daily. Thanx for this development. 👍
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    So I redid the install with the following steps:
    1. rebooted into bootloader, flashed twrp
    2. wiped all partitions
    3. mounted the data partition and then flashed AOSP only.
    4. rebooted and AOSP loads.

    But unfortunately now I get another error "Launcher keeps stopping". Closing the error message merely brings back the same error message.

    Any thoughts?

    Edit:
    I followed through and installed the gapps package as well. I reproduced the same "google framework keeps stopping" error.
    I tried different ways, but the only solution for a clean install is to install the very first firmware version 20170105. Then the latest one as an update. Then gapps.
    3
    I tried different ways, but the only solution for a clean install is to install the very first firmware version 20170105. Then the latest one as an update. Then gapps.
    Thank you very much. That worked.

    Here is what I did:

    1. I did a full wipe.
    2. I flashed grouper image dated 20170105.
    3. booted up the nexus 7 to check all is well.
    4. rebooted and flashed the latest image from 20220311
    5. rebooted to recovery and flashed gapps (with workaround for Error 70 file)
    6. rebooted into Android and voila all is great.

    remains to be seen how snappy or slow this ageing tablet is.
    2
    Yes, I installed them both in one shot, as thats what I have done on other devices like my oneplus and essential phones.

    I will try installing one at a time and update this thread.
    1
    Firstly thanks @AndDiSa for maintaining this ROM. I see latest build is dated 20220311. Thats pretty impressive.

    I have a grouper that was running stock 5.1.1. Slow, slow, slow. So I decided to flash your rom.

    I flashed TWRP via fastboot recovery twrp.img. Then installed the AOSP ROM and gaps pico version along with the error 70 workaround in your second post. Installation went smoothly. So far so good.

    I rebooted. It popped the google logo and then android. after a couple of minutes it came up with the setup screen. Then I get the message that "clock has stopped" and then "Google Services Framework has stopped". I hit close and then i get this recurring message "Google services framework keep stopping".

    Due to the recurring message, that pops immediately after closing the error notification, I can't even complete the set up step.

    Any steps I missed in my installation ? I did not read through all the comments on this thread. Any guidance anyone can provide?
    1
    Did you flash ROM and apps together, i.e.without booting? If so, trying flashing the ROM only* then boot, allow that bit of set up to complete, connect to WiFi etc THEN reboot to recovery and flash Gapps.

    *wipe again before reflashing
  • 318
    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.6.1-9 for Grouper resp. TWRP 3.6.1-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 20220311) (MD5: b7c8081fd48398befbef1384e83eb509)
    5. Install 7.1.2 Tilapia OTA-Package (Build 20220311) (MD5: c930aabcda55a514baf3f0ef5a6e4cb9)
    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 (V23.0) which can be flashed by TWRP, too. Probably you'll need to rename Magisk-v23.0.apk to Magisk-v23.0.zip
    I was not able to flash Magisk 24.x by TWRP / direct install, nevertheless the patching boot.img method worked. For that you need to extract the boot.img from the OTA and transfer it to your devies. Then you need to patch the boot.img and transfer it back to your PC. Finally you can flash the patched boot.img using fastboot.
    For detailed instructions please consult the Magisk threads here in XDA.

    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 20220311) (MD5: b7c8081fd48398befbef1384e83eb509)
        or
      • Install 7.1.2 Tilapia OTA-Package (Build 20220311) (MD5: c930aabcda55a514baf3f0ef5a6e4cb9)
      • Reboot into recovery
      • Install Open GApps (arm/7.1/pico)
        (if you have issues regarding the size of the GApps please refer to the next post)
      • 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
    • 20220212(AOSP 7.1.2)
      • I applied the security fixes for January 2022 and February 2022

    Latest version with MicroG-patch applied to them:
    aosp_grouper-7.1.2-mg-ota-20220311.eng.ds.zip (MD5: 66d9cb4b09cdd886c9387a16933771e9)
    aosp_tilapia-7.1.2-mg-ota-20220311.eng.ds.zip (MD5: 48f0d0d60131afaae0d777b7798f2e13)



    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-12-09
    71
    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!