yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] HTCDreamOn:
My 16GB grouper bit the dust (digitizer tore off the glass so no touch :( ) so of course I promptly replaced it with a mint 32GB tilapia for almost £nothing and installed this fantastic ROM!

- All partitions are f2fs

- Flashing with TWRP 3.3.1 is fine

- After installing OpenGapps (I succumbed as I want chromecast) I had the blank settings problem reported earlier in this thread, but it resolved itself within a few minutes and is fine on consecutive reboots (I'm guessing it has something to do with Play Store Protect getting up and running)

- Getting HSDPA signal so data seems perfectly functioning too! although I won't be using this

- Battery seems fine and not experiencing battery drain whilst charging

Tip for people who want to start off without GApps, Play Store, or anything, you can download F-Droid on your computer and use adb to install it:

adb install F-Droid.apk

;)

Amazing work!
[Nexus 7 Android Development] impact79:
I just flashed the rom and the gapps onto my device. How long will it need to boot for the first time? Mine is stuck showing "android" for about 2 hours now...
[Nexus 7 Android Development] AndDiSa:
[MENTION=1109354]impact79[/MENTION] ... then you did something wrong. Normally after 10/15 Minutes at most the device is booted even if there might be some optimization work going on in background.
[Nexus 7 Android Development] breaktheblock:
This happens all the time just hard reset after a few minutes instead of two hours and it should then go into Android.
[Nexus 7 Android Development] HTCDreamOn:
Try booting after flashing just the ROM first as well... then once you can confirm everything works you can try flashing gapps.
[Nexus 7 Android Development] mikeataol:
In addition to the other responses. I have found the best results with almost every rom on several devices, including this one is to

wipe system and caches cache/davlik

install the rom

REBOOT to recovery

install GAPPS

REBOOT to recovery

Install SU or magisk whichever root tool you are using
[Nexus 7 Android Development] impact79:
Jep, you guys are right. Rebooting (into rom) between the installations of the rom and gapps seems to solve that problem.

Thanks [MENTION=9350973]All[/MENTION] for help!
[Nexus 7 Android Development] j8a:
Hi, I successfully follow the instructions.

wipe system and caches cache/davlik

install the rom

REBOOT to recovery

install GAPPS

REBOOT to recovery

and now I am dowloading the Play Store updates for my apps.

Thanks, in advance.
[Nexus 7 Android Development] eustachy:
Hi,

I'm stuck in the TWRP 3.4 relase - cannot mount data partition via usb to copy zip files. I have formated data and it doesnt work. Data/cache/system are ext4 file systems.

If I click select storage I have two options 1. internal storage (28049MB) and 2. USB OTG (0MB) - can't select the second one.

Any help would be appreciated. I have done factory reset (going from AOSP from 2015 - dont remember relase no.).

Cheers
[Nexus 7 Android Development] mantichora:
Installed build 20200708 on my trusty grouper today and just wanted to share that this the snappiest installation I have ever seen on a legacy device. :good:

I was not expecting a lot after replacing a dying battery prompted me to try a new installation. Previous CM roms at least had made it usable again after Google punished us with the Lollipop update, but this rom is running rings around all previous installations. Setup was a breeze as well and all HW is operational so far, USB devices too, even NFC.

Great work, thanks a lot :highfive:
[Nexus 7 Android Development] AndDiSa:
New version with security patches for August 2020 available

eight years old and still getting updates ... :)

just a few minutes ago I've added the security patches for August 2020 and pushed all the changes to the Github repos, too.

Here are the links for the new builds:

Grouper OTA-Package (Build 20200805) (md5: f5d3448d6839ab716c0a084f0125b388)

Tilapia OTA-Package (Build 20200805) (md5: 061be519e6de60583d5a2a5192052717)

The builds are untested yet and as always I'll wait a few days to collect feedback from the community before I will add them to the OP.

Stay healthy!
[Nexus 7 Android Development] metterschling:
A big THANK YOU from my wife, still very happy with her Grouper thanks to your efforts!
[Nexus 7 Android Development] Sam Nakamura:
It feels so good overwhelming, you really made it a legendary device!

if someone told me back in 2012 that I'll get AOSP updates until 2020+, I'd probably asked have same person about his opinion on flying cars in 2020... insane in the membrane!

thanks for your dedication time and time again, this is the spirit of our future, overcome that planned obsolescence ****!!
[Nexus 7 Android Development] BLewis4050:
TWRP 3.4 works after Sys part wipe and extra reboot!

Thanks so much -- your solution of the extra reboot after wiping the System partition worked!
[Nexus 7 Android Development] :
August ROM clean flashed no problems. All is good :D Many thanks to [MENTION=2188693]AndDiSa[/MENTION] (and [MENTION=5463045]metterschling[/MENTION] for the tip! :good: )

Btw, I found out what was creating the .$Trash$ folder I mentioned before - it was the TWRP backup process. It happened again when I backed up before flashing the ROM. So I deleted the folder and took the opportunity to flash to the TWRP 3.4.0. All's working purrfectly. :D
[Nexus 7 Android Development] laugeek57:
Always the same pleasure to use this Rom :D

Thanks AndDisa :highfive:
[Nexus 7 Android Development] rori1977:
Update went fine on grouper to August release.

Comming from previous month release. Wiped Dalvik&Cache using TWPR 3.3.1.0 as usual.

Hoewever I have problems signing in to Google Play this time.

Used:

https://kumisystems.dl.sourceforge....20200809/open_gapps-arm-7.1-pico-20200809.zip

Problem:

After entering username / password (and reconfirming on my other device that this is an intended login activity to Google Play) I am always being asked to log in again.

Tried reflashing recovery to latest TWPR 3.4.0.0 and repeated to install openGApps.

Same result for now.

Looks like I can not sign in to Google Play at the moment, will keep trying later.
[Nexus 7 Android Development] dabanhfreak:
Holy smokes.

So long story short my mum needs a new tablet to join Zoom calls and remain active in her religious community. Instead of buying her a new one I started off my old Nexus 7 and checked the forums not expecting much. Not only is it still active, but there are no less than 4 separate thread with new build within the last 60 days. I have to say I'm blown away... Especially since I think I contributed to this thread back in 2017.
[Nexus 7 Android Development] few__:
deleted
[Nexus 7 Android Development] few__:
I will ask a question.

How do I add Face unlock?

I couldn't add to it;(
[Nexus 7 Android Development] ticpu:
Adding more zram

Hi and thanks for the up-to-date OS, works perfectly!

The zram on this config is set to 256MB which is a bit on the small size for my use, here's a script for those who would like to tune this as well.

The default zram configuration only uses only 1 stream to compress, so, when the processor is waiting for more memory, it waits on one core to compress instead of using all of them.

I made the zram 1GB to get a bit more memory out of this since my MMC is so slow, I prefer swapping more instead of reading from the MMC.

Since I don't know where to set the zram parameters, as it seems to appear even before Magisk starts, I did add a post-fs-data script to set it up how I want.

/data/adb/post-fs-data.d/zram.sh :

#!/system/xbin/sh

/system/bin/swapoff /dev/block/zram0
cd /sys/block/zram0
echo 1 > reset
echo 4 > max_comp_streams
echo lz4 > comp_algorithm
echo 400M > disksize
/system/bin/mkswap /dev/block/zram0
/system/bin/swapon -p 10 /dev/block/zram0

exit 0
[Nexus 7 Android Development] AndDiSa:
Thank you very much for the script! Should work without issues ... even if 1GB is probably a bit too much, I would not use more than 512MB as otherwise the system may become very slow in certain situations.
[Nexus 7 Android Development] ticpu:
I'll edit the script up there to make sure no one uses 1GB as it is indeed too much, I'm still experimenting to find a good balance and wanted to encourage the system to swap as much as it could. I got the swap up to 340MB which was compressed to 107MB. It still felt more responsive than before the modification.

I'll probably tune it down between 400MB and 512MB in the end.

I'm also trying to build a patched kernel with zstd compression for use in zram, it took 5 patches from the mainline which applied quite well. It is my first time building the kernel for Android, repo sync took quite a while and I need to install the Sun JDK it seems, so I'll check that a bit later.
[Nexus 7 Android Development] AndDiSa:
[MENTION=5964337]ticpu[/MENTION] when I did my last tests on that 340MB was the maximum which was acceptable for my usage ... but this depends much on which apps you have installed, how many memory these apps are using when running, whether you are switching frequently between several applications, ...

256MB is a compromise most of the people can live with, but better to have some options to select from :)
[Nexus 7 Android Development] ticpu:
I probably didn't read enough documentation yet, however, I tried building a kernel with Zstd compiled in, it seems to work and compile, however, when I fastboot boot it, it downloads, start the process and when I check with uname -a, it is still the old kernel. Is that tablet okay with booting images directly?

Here are some of the outputs that show that it *should* work, but it's hard to debug without kernel output on the screen :/

make: Leaving directory '/usr/src/git/android-grouper-build/kernel/asus/grouper'
[100% 6/6] Target boot image: out/target/product/grouper/boot.img

file out/target/product/grouper/boot.img
out/target/product/grouper/boot.img: Android bootimg, kernel (0x10008000), ramdisk (0x11000000), page size: 2048, cmdline (androidboot.hardware=grouper buildvariant=userdebug)

$ find . -name "*zstd*.o"
./out/target/product/grouper/obj/KERNEL_OBJ/drivers/block/zram/zcomp_zstd.o
./out/target/product/grouper/obj/KERNEL_OBJ/lib/zstd/zstd_common.o
./out/target/product/grouper/obj/KERNEL_OBJ/lib/zstd/zstd_compress.o
./out/target/product/grouper/obj/KERNEL_OBJ/lib/zstd/zstd_decompress.o

Here are my 3 commits backported from mainline https://github.com/ticpu/android_kernel_asus_grouper/commits/ads-7.1.0
[Nexus 7 Android Development] IHaveNoIdeaWhatIAmDoing:
"Device is not certified" in Play Store

Thank you for a great ROM! My Nexus 7 tilapia is finally usable after sitting in a drawer for half a decade. BUT... on my device, Play Store shows "Device is not certified". Also, Magisk's SafetyNet ctsProfile check fails (basicintegrity passes).

I hacked AOSP build.prop with some fingerprint stuff from Lineage 14.1 and now Play Store and SafetyNet work fine. (No Certification message is displayed at all but things seem to work.)

I just wanted to mention this to see if it's an issue for anyone else. I don't *think* I did anything wrong...

(Using TWRP 3.4.0-0, AOSP 7.1.2 20200805 NZH54D, Open GApps arm/7.1/nano (or pico--so many installs, I forget), Magisk 20.4)
[Nexus 7 Android Development] Swanee123:
If having play store showing as certified on your tilapia is important and if you want to pass safety net simply install the stock AndDiSa ROM, Gapps., Magisk and a Magisk module called MagiskHide props config. Instructions are on line

Should all be fine then
[Nexus 7 Android Development] IHaveNoIdeaWhatIAmDoing:
Thanks. I don't care if Play Store shows "Certified", I care if Play Store thinks it is certified so I can find apps like Netflix.

As you might guess from my username, I need more help. Google only finds this thread when I search for "stock anddisa rom" so perhaps you could provide a link to where the "Instructions are on line"? I installed the ROM from this thread, Open GApps, Magisk, and I thought I played with MagiskHide (but maybe not), and always not certified.

Hacking fingerprint makes everything work, but I appear to be the only person on earth who has this problem.
[Nexus 7 Android Development] Swanee123:
Entering MagiskHide Props Config into google brings up this link which looks like a great resource on getting a better understanding

https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228
[Nexus 7 Android Development] ra_van:
Nexus 7 (2013) ROM Recommendations

Dear colleagues,

In an unhappy incident I broke the screen of my trusty Nexus 7.

I know that a lot of you have the skills to replace the screen but I chose to get the next generation of Nexus 7, the one from 2013.

Now I'm going to be a little bit off topic but I hope there is someone that could answer my question:

what ROM can you recommend to use for the Nexus 7 (2013) that is comparable in performance and stability of [MENTION=2188693]AndDiSa[/MENTION]'s ROM and is kept up to date with security patches.

Thank you in advance for your answer and thank you to AndDiSa's extraordinary work.
[Nexus 7 Android Development] ticpu:
After checking a little more, it's just like the initramfs isn't being included, even if my boot.img has 6.3MB, quite close to the original at 6.4MB.

Any idea what I might be missing? Also, since the kernel is compiled without module support, I can't really unload zram and load the new version :(

[ 0.000000] Linux version 3.1.10-zstd-g1bca90f8977 (root@p4) (gcc version 4.8 (GCC) ) #4 SMP PREEMPT Thu Aug 27 04:09:30 UTC 2020
...
[ 0.000000] Kernel command line: tegra_wdt.heartbeat=30 androidboot.hardware=grouper tegraid=30.1.3.0.0 mem=1022M@2048M android.commchip=0 vmalloc=128M androidboot.serialno=015d483bd548200c video=tegrafb no_console_suspend=1 console=none debug_uartport=hsport usbcore.old_scheme_first=1 lp0_vec=8192@0xbddf9000 tegra_fbmem=8195200@0xabe01000 core_edp_mv=0 audio_codec=rt5640 board_info=f41:a00:1:44:2 tegraboot=sdmmc gpt gpt_sector=30785535 androidboot.bootloader=4.13 androidboot.hardware=grouper buildvariant=userdebug
...
[ 4.955415] Warning: unable to open an initial console.
[ 4.955616] RAMDISK: Couldn't find valid RAM disk image starting at 0.
[ 4.956458] Root-NFS: no NFS server address
[ 4.956533] VFS: Unable to mount root fs via NFS, trying floppy.
[ 4.956794] VFS: Cannot open root device "(null)" or unknown-block(2,0)
[ 4.956869] Please append a correct "root=" boot option; here are the available partitions:
[ 4.957027] b300 15392768 mmcblk0 driver: mmcblk
[ 4.957233] b301 12288 mmcblk0p1 6bec44b6-d069-4a8c-3dc3-86881cd89c36
[ 4.957377] b302 8192 mmcblk0p2 bbee8abc-590a-57fb-252e-fffe5b528f2e
[ 4.957579] b303 665600 mmcblk0p3 42bf1b09-5e79-6ae2-1b1b-cae0e5342192
[ 4.957829] b304 453632 mmcblk0p4 555df303-74f8-53d8-77a2-b2a4f8da2bb6
[ 4.957973] b305 512 mmcblk0p5 c70bd7aa-ecf4-ead7-8cd5-43d7f5fff6e4
[ 4.958175] b306 10240 mmcblk0p6 656dbdcc-bda3-3728-8c2f-193efd950e09
[ 4.958377] b307 5120 mmcblk0p7 de6b6db4-917c-cc76-4c6a-0136bed24b8d
[ 4.958520] b308 512 mmcblk0p8 08b864a2-b83c-414c-e886-bf650bf370b5
[ 4.958722] b309 14228480 mmcblk0p9 697b2c19-14a9-7987-f9ab-828a45f93178
[ 4.958926] b320 2048 mmcblk0boot1 (driver?)
[ 4.959068] b310 2048 mmcblk0boot0 (driver?)
[ 4.959209] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
[Nexus 7 Android Development] IHaveNoIdeaWhatIAmDoing:
This was great info, thank you! It explains a lot about changing the fingerprint (which is what I had done).

I need to learn to write better. What I thought my first post said is that I had to change the fingerprint to pass SafetyNet (I used a text editor on build.prop). My question was whether the ROM could include a fingerprint that worked so I didn't need to change it, and why does it work for others and not me? But apparently none of that came thru in the post.

Anyway, since I'm up and running I will just be happy and quiet. You guys are awesome, this ROM is awesome and I am thrilled to have it!
[Nexus 7 Android Development] AndDiSa:
New version with security patches for September 2020 available

ok, it's not Android 11 but a new update for our beloved Nexus 7 :)

just a few minutes ago I've added the security patches for September 2020 and pushed all the changes to the Github repos, too.

Here are the links for the new builds:

Grouper OTA-Package (Build 20200911) (md5: 52f18e13b97653d6cbd8e2f1cacbecab)

Tilapia OTA-Package (Build 20200911) (md5: 2211dba98d9debb5b8eb848106f8b73e)

The builds are untested yet and as always I'll wait a few days to collect feedback from the community before I will add them to the OP.

Stay healthy!
[Nexus 7 Android Development] Chinmay2006:
I am thinking of compile my own ota from your source. Can you please tell me what is the size of your source.
[Nexus 7 Android Development] AndDiSa:
[MENTION=11053187]Chinmay2006[/MENTION] I have no idea, but I would expect around 80GB if you do a repo sync
[Nexus 7 Android Development] iqnas:
Hello, i messed up big time..

I skipped the Factory Reset part. And I have installed the twrp-grouper.img. Now it's stuck in the loading screen.

What steps should i take to resolve this issue?

Hope it does not start with buying another tablet

#HELP
[Nexus 7 Android Development] ticpu:
Once compiled, it amounts to around 160GB on my side.
[Nexus 7 Android Development] fsw_informatrix:
Have you tried the bootloop hints that are in the second post of this thread?

Considering that you are coming from another ROM or maybe even stock (don't be shy to give a bit more details next time), because that's the only reason to do a Factory Reset, I will strongly suggest you to read at least (and more carefully perhaps) the first few posts / pages (for instructions, warnings and troubleshooting) and also the last few posts / pages (so that you known what is going on now) of the corresponding thread, the next time you want to try to flash a new ROM ;)
[Nexus 7 Android Development] fsw_informatrix:
[MENTION=9374170]iqnas[/MENTION] : This thread ("Nexus 7 Button Combinations") could be useful with your problem too :

https://xdaforums.com/showthread.php?t=2133986
[Nexus 7 Android Development] iqnas:
Hello it's me again.

Yes I am coming from a stock rom.

I do agree that it was a rookie mistake from my part..

What should i do now?

I can go into the fastboot mode. But when trying to go into recovery or start the device, it wont load.

I was thinking about installing old rom to try and restart the whole process again, but I cannot go into the debug mode without turning on the device. (or maybe i don't know something).
[Nexus 7 Android Development] AndDiSa:
[MENTION=9374170]iqnas[/MENTION] not sure if I understood your problem completely, but what's about booting into bootloader mode, from there you can go into recovery and wipe everything.

If you cannot start recovery from bootloader mode, you probably flashed a wrong recovery image or the flashing of the recovery image failed.
[Nexus 7 Android Development] iqnas:
[MENTION=2188693]AndDiSa[/MENTION]

Thanks for your replies, but i think you will get tired of my questions...

The steps i took:

0. I took my stock Nexus 7 with android 4.something

1.Updated TWRP 3.4.0-0 Grouper

2.Did not boot into recovery or factory reseted (I think this was the problem)

3.Installed 7.1.2 Grouper OTA-Package (Build 20200805)

The problem:

When trying to go into recovery - stuck on Google white text with lock icon.

Questions:

What should i do now?

Is it possible to flash stock rom onece again to try and redo everything?

(adb bootloader can't find device, i think it's because i can't enable debuging mode without starting the tablet).
[Nexus 7 Android Development] AndDiSa:
[MENTION=9374170]iqnas[/MENTION] did you unlock your bootloader before trying to flash the rom? (Is the lock closed or open?)

"adb bootloader" does not exist, you need to do "adb reboot bootloader", but this works only for a running ROM.

Try to to the following: press both the "power" + "vol-" in parallel for round about 20 sec. then the device should be in booloader mode. If you have managed it we can discuss the next steps.
[Nexus 7 Android Development] iqnas:
Thanks for your reply

Yes the bootloader is unlocked. I used „fastboot oem unlock“ command before i messed everything up...
[Nexus 7 Android Development] fsw_informatrix:
[MENTION=9374170]iqnas[/MENTION]: If you can get back to fastboot mode, follow the instructions here to flash again TWRP https://twrp.me/asus/asusnexus72012wifi.html i.e. the part after "You should now be in fastboot mode.".

Once you are in TWRP, wipe everything, reboot to TWRP, flash the ROM, reboot to TWRP, flash the Gapps (if you want to use the Play Store easily, you will need them, so for OpenGapps, take "Pico"), reboot to TWRP again to flash Magisk if you need root and finally, you can reboot to system and be good to go...

Be aware that you really need those multiple reboots to TWRP between steps, it's the best way to avoid weird errors and glitches...

Good luck to you!
[Nexus 7 Android Development] beppemila:
Hi [MENTION=2188693]AndDiSa[/MENTION] I just installed the ROM for Grouper (latest available version in the first post). it boots flawlessly but I cannot connect to my wifi anymore.

I insert the wifi password but my nexus tries to connect, cycles between connect/saved status and then stays on 'saved' wifi connection status with no connection...

I was on slimkat 4.4.4 and no issues with wifi.

Wiped everything except data, twrp 3.4.0.

how to solve this?

Thank you!
[Nexus 7 Android Development] AndDiSa:
[MENTION=4793590]beppemila[/MENTION] did you try whether a fixed IP is working for you?

Otherwise you could also try to edit your WiFi configuration as described here
[Nexus 7 Android Development] beppemila:
Thank you a lot for your answer.

Actually it seems that my grouper wifi has the same behavior with all 7.1.2. roms.

I tried to switch to a static IP bu no success (while my laptop can successfully connect).

One question, I'm on windows... how do I find the txt files to be edited as shown by the linked post?

Thanks again :)

---------- Post added at 06:16 PM ---------- Previous post was at 05:48 PM ----------

Hi [MENTION=3777227]TureX[/MENTION] I have a wifi issue that may require your solution.

I see you connected via linux (to the best of my knowledge). As I'm connecting to my Grouper via windows, can you advise how I can apply the same changes you did?

I've copied the file via TWRP and applied the pmf=0.

I just don't know how to go on with the other commands. I see that TWRP allow me chmod or chmod 755. I hope this helps.

Thank you.

Giuseppe
[Nexus 7 Android Development] TureX:
Hi! if you are rooted you can do with apps like termux or trought adb.

Cheers

EDIT: i made a script that help to disable pmf, if [MENTION=2188693]AndDiSa[/MENTION] give me permission i will post there.

Cheers
[Nexus 7 Android Development] AndDiSa:
Yes, for sure. No need to ask for permission, you are welcome.
[Nexus 7 Android Development] TureX:
Hi! this is a script for disabling pmf to avoid wifi connection problems.

Download PMF disabler

INSTRUCTION:

copy pmf.sh on /sdcard

boot in twrp

Open a terminal and type adb shell

type this commands :

cd /sdcard

chmod +x pmf.sh

sh pmf.sh

reboot

----------------------------

Enjoy!
[Nexus 7 Android Development] grininja:
Hi there.

Trying to revive my Nexus 7 and I'm stuck. These are my problems:

1. Recovery: Flashing either twrp-3.4.0-0-grouper.img or twrp-3.4.0-0-tilapia.img results in freeze at google logo. But if I flash the unmodified twrp-3.4.0-0-flo.img it boots ok into recovery.

2. OTA-Package: Because I can not boot into grouper or tilapia recovery I tried to install the package from the unmodified recovery but I get Error 7. I tried witp twrp 3.4.0-0 and also with 3.3.1-0. (Wipeing system and rebooting again into recovery didn't help)

Any thoughts?
[Nexus 7 Android Development] AndDiSa:
[MENTION=6075126]grininja[/MENTION] flo is Nexus 7 (2013), this thread is about Nexus 7 (2012) ... i.e. your device is incompatible to this ROM.
[Nexus 7 Android Development] grininja:
Sh..t. Rookie mistake. My apologies.