yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] fsw_informatrix:
A quick "me too" here, just dirty flashed February ROM yesterday with TWRP 3.5.0, OpenGapps Pico and Magisk 21.4, so far so good, everything works as intended.

Thanks a lot!
[Nexus 7 Android Development] MacLeod100:
Hi all ! I update my beloved Nexus with latest update ( february ) and have a small problem It disconnects from wify randomly :( I remember that someone post a fix for that in this forum but after 2 hours of searching no luck :(

Anyone have ( by accident ) than fix saved and want to share ?
[Nexus 7 Android Development] BeeJ1109:
Hi AndDiSa,

Just downloaded Tilapia Feb 21 version on my Nexus 7 3g Tablet.

Dirty flashed after wiping cache & dalvik. Using TWRP v3.4.0

Boot up OK. Again as per previous build Google Play Services fails on almost 30 apps. So will require Nano or Pico Gapps to be installed again. Also Magisk is required to installed again to retain ROOT.

Noted only 4 partitions are being backed. Boot partition is being wiped and restored with Stock that has not retained Magisk mod to retain Root. No backup of Recovery partition. That is always available for every version of TWRP I have for multiple devices.

Modem and ETS Partitions is not backed, therefore cannot be restored if needed, If crashes occur.

Also noted Persist partition has been renamed. Persist is required to allow TWRP Helper to allow backup of Internal data to add external memory, that included downloads and photo files to be saved and then restored within the data backup.

Therefore not a full Nandroid of all partitions is provided in your version of TWRP, but a limited version.

If you get a crash, boot loop, etc, it is more efficient to be able to backup and then restore all or selected for the user to use all functions possible to get back to a working version, especially whilst experimenting with new or different ROMs.

Instead of having to re-flash back to Stock ROM, then update to new Custom ROM, to reinstall Root and Gapps each time you flash the latest or roll back to previous working version including all apps.

So may I suggest, you rework your TWRP, to allow all partitions to be available to backup or restore as required. More is better than less in my experience.

Still failing to perform like earlier. Needing download Gapps again. Google apps multiple failures. Device was working well. Now extremely average.

The ROM and TWRP needs lots of work. Because a dirty flash does not require apps to be fixed like this. Sorry for the bad news.

I have added logs. For you to view.

Cheers BeeJ1109.
[Nexus 7 Android Development] AndDiSa:
@BeeJ1109 I suppose you are mixing up several things. As I already wrote I do not own/maintain any TWRP-Version. TWRP is fully independent from the ROM and is maintained by the TeamWinRecoveryProject.

Regarding your issues related to Gapps and Magisk: please read carefully the OP. I suppose you are running into issues because you are not following the update instructions. You need always to re-flash gapps and Magisk after updating to a new version of the ROM. There is no backup functionality when updating to a new version and this is intended behaviour.
[Nexus 7 Android Development] AndDiSa:
@MacLeod100 try to have a look at

/data/misc/wifi/wpa_supplicant.conf

and replace pmf=1 by pmf=0

btw. I have also troubles to find the post where somebody even provided a flashable zip to fix this issue.
[Nexus 7 Android Development] MacLeod100:
Thank you for quick response

I will look at that

Same as me can't find the zip file
[Nexus 7 Android Development] BeeJ1109:
Hi AndDiSa ,

Firstly I have about 6 other devices all Samsung Tablets and phones.

I use TWRP on all. They are all supported by different Devs. whom use TeamWinRecoveryProject , for source code. As I have sent you lots of logs today. For you to view.

As for Gapps and Magisk when I flash a brand new ROM build. I do a clean install, as I mentioned. But doing a security update, I do dirty flash, as the ROM is only a system update, that is wiped and then flashed to that partition. Data partition is not touched, that has all the existing apps, that are restored to the OS update. Icons on all home screens are preserved in same location. Most devices have between 30-100 apps. That I do not want to reinstall again each update.

I always do a full nandroid, before every flash. Saves a lot of grief.

From years of experience working on PCs and Communications, as well as, mobile devices.

So maybe you, now understand my comments.

I just find the TWRP, available for this device, is very limited. Compared to several other Samsung TWRPs, I have been using, for more than a year ago.

Where I do not have to reinstall Magisk, as Root is preserved.

Same Gapps and needing to fix Google play services, and all apps crashing. Needing me to setup google login each time I flash. All apps were up to date, prior on previous build being Jan 21, then I updated Feb build, lots of issues.

Nandroid backup and restore is very useful, when experimenting with different ROM builds by different devs. ie switching between LOS 16 & 17.1, RR 5.8, LFR 17.1 and future Android 11, back to Stock. Back and Forth.

That is my thoughts

Cheers BeeJ1109
[Nexus 7 Android Development] few__:
https://xdaforums.com/t/rom-nzh54d-...s-ext4-android-7-x-aosp.3467514/post-83546153

Try using the PMF disabler
[Nexus 7 Android Development] AndDiSa:
@BeeJ1109 a dirty update will not clean your data and/or apps installed on the device. Flash the ROM on top of the existing one, flash Gapps, flash Magisk and everything is fine.

You are free to do nandroid backups / restore nandroid backups as much as you want, but as I already told you, this has nothing to do with the ROM. The ROM neither defines the partition layout of the device nor touches other partitions than /system and /boot
[Nexus 7 Android Development] username one:
How do I set signature spoofing?

Edit: This is what I'm looking for: https://xdaforums.com/t/rom-nzh54d-...s-ext4-android-7-x-aosp.3467514/post-84121871
[Nexus 7 Android Development] BeeJ1109:
Hi AndDiSa,

I understand the difference between Clean start afresh, & Dirty Flash retains apps and their data. I already mentioned, I did not want to reinstall all apps again, take hours, even if I use apps backed up, in Google Cloud.

I already did the clean install, wiped data, system, cache, dalvik, when I went from Stock to your ROM. Installed Magisk and Gapps pico, as even nano, would not fit into System partition. Still had crashes with Google Play Services. Required a fix, to be Stable.

Is not about the TWRP, it's is your ROM that has issues.

Did you Bother to check the attachment. l Had Provided many Catlogs, including TWRP recovery logs to show you issues. On Feb 17.

There are problems with ROM builds.

No Camera included, which other Devs, include in their ROMs.

I also understand what TWRP does, It allows backup or restore partitions, as selected, before proceeding. It is that Simple. With additional options, to wipe partitions, use internal file manager, to copy, move, delete, rename files, and directories on internal and external devices like OTG flash drives.

You provided the links for each device, So who is the Dev "Jenkins" whom

compiled these TWRPs for these devices, so I can contact them directly, to discuss issues with TWRP version, available for NEXUS7 3G Tilapia tablet.

I am thoroughly familiar with TWRP, as I have been using versions, on my multiple devices over many years, also used CWM and other Recovery methods.

My first Smartphone was a Nokia N8 Symbian OS. Then Android Samsung S3 , S4 mini, HTC XL one, when 4G was started. I installed and commissioned Mobile Base Stations in Australia, using all these devices from 1987 with CMTS Analogue, CDMA, then 3G, 4G Networks, as Test phones.

So I am just providing feedback, on my experience, using your ROM.

Cheers BeeJ1109
[Nexus 7 Android Development] AndDiSa:
@BeeJ1109 Sorry, I suppose you do not want to understand that you are the only one who has issues with the ROM. Probably it's better if you choose a different one for your device.
[Nexus 7 Android Development] marty_bebop:
When I install a new ROM, I transfer the ROM, Gapps & Magisk to device (Grouper) from Windows, then install via TWRP, following instructions.

I have never had a problem. Not once.

Whilst I've never tried it, I reckon I could do it with my eyes shut.

It's fantastic that these devices are being kept alive.
[Nexus 7 Android Development] akillenb:
@BeeJ1109

You obviously did not read the first part of this thread. It is stated plainly that to update, you need to install the ROM, reboot to recovery, then install gapps. That Works.

There are only a couple of camera apps that work on the Nexus 7, since it only has a forward facing camera. The stock android camera app, and most others assume/require the device to have both forward and back cameras.
[Nexus 7 Android Development] marty_bebop:
"A Better Camera v3.54" app works on my Grouper device - not that I use it. I was determined to find something that works - and it does.
[Nexus 7 Android Development] tbusse:
THANK YOU!!! I brought my N7 back to life and run into trouble with the wifi pmf feature. I had to switch it off until I found the solution here. And besides I got a tablet with decent speed back. I already had LOS on it but ASOP seems to be faster and the sec lvl is up-to-date.

So thank you very much for your work!!!
[Nexus 7 Android Development] momentoid:
Just here to say thank you @AndDiSa. Installed February update with GApps, still on Twrp 3.4.0.0, and everything works great.

Is it just me, or this version seems to run better than the December version?
[Nexus 7 Android Development] :
Ime, I find clean flashing always makes a new ROM seem faster than the previous. I don't think it's necessarily because the new version is better/faster/smoother than the previous (although, of course, it could be) I just think you haven't noticed how your old install slows down after a while. Like it's clogging up or something (not very technical, I know!) Think of a clean flash as being like a 'declogging' and perhaps worth doing from time to time (even if there's no new ROM to flash) simply to freshen things up! Just my thoughts...
[Nexus 7 Android Development] pratikxdagarwal:
Hi sorry I'm a bit of a noob. So I installed this using the old twrp (official one). Then I read somewhere that u can speed up the Nexus 7 by using a modded version of twrp. After installing the modded version I installed this rom using adb sideload. Now my file system still shows ext4 using diskinfo app. How do I change it to f2fs using the modded twrp?
[Nexus 7 Android Development] AndDiSa:
@pratikxdagarwal there is no need for using a modded TWRP version. I suppose you wanted to use f2fsf for /cache and /data partitions instead of ext4. Well this can be done but you will lose your data as you need to reformat those partitions when you have booted into TWRP ... but really speaking: in my experience there is not much difference at all and I am not sure whether it's worth to do so.
[Nexus 7 Android Development] pratikxdagarwal:
Got it. Thanks! Love you work man.
[Nexus 7 Android Development] KainRaziel:
Hello everyone. First of all I would like to thank Anddisa for his amazing work. I installed the latest rom and gapps with TWRP 3.3.1. The tablet works perfectly: only in the initial configuration, after entering the language and wifi password, the nexus remained in the "check for updates" screen. I finished the configuration without a network and only after it started I entered the google account.

I wanted to know if that's okay or if I have to enter the account at the beginning of the tablet configuration? (maybe this fact may depend on the TWRP version? The installation was done perfectly without errors). I thank in advance those who want to answer.
[Nexus 7 Android Development] AndDiSa:
@KainRaziel there should be no problem setting up the device without network and entering the Google account data after the initialization is finished.
[Nexus 7 Android Development] KainRaziel:
Thanks again for everything, Anddisa.
[Nexus 7 Android Development] Miglkein:
[Mod Edit] Added automated translation:

Подскажите. Почему вылетает ошибка 7. TWRP получилось поставить только 3.4.0.0. если ставить выше то висит на надписи Google
[Nexus 7 Android Development] AndDiSa:
@Miglkein post in English please ...

Nevertheless Error 7 most of the times indicates that your device does not match the requirements for installing the zip file, but ther might be different reasons, too.
[Nexus 7 Android Development] momentoid:
I experienced Error 7, too.

I was trying to install from a .zip file that was located in /sdcard/Downloads/ directory.

Resolution:

1. I used TWRP's File Manager to move the .zip file to /sdcard/ directory

2. Rebooted to Recovery mode

3. Install-ed successfully. I have TWRP 3.4.0.0.

Hope this helps.
[Nexus 7 Android Development] BeeJ1109:
Hi All,

Can someone, please tell me, who is Jenkins, and how can I PM him.

Thank you.

I did a lot of research on TWRP.ME website.

Found that Jenkins, is the name of the Server, where all TWRP Versions are located.

Search on Developers. Jenkins appears and involved on many TWRP for many devices. Lots of commits, especially on Tilapia, which is Asus Nexus 7 3G (2012). Which this thread is for this device.

I have issues with the TWRP version 3.4.0-0-tilapia.img and latest 3.5.0_9.0- Tilapia.img

NEW FUNCTION ADDED

In TWRP after version 3.4.0-0, internal storage can be now backed up, as part of data partition, by renaming /data/media to now include personal data files , ie photos, videos, downloads to change backup and restore to include internal storage instead of presently being data (exclude external storage), meaning excluding /data/media or emulated storage.

This change can be included permanently by modifying fstab.grouper file. That is used to configure, what partitions are available, to be backed up and then restored, as a true Nandroid Backup.

In other Device's TWRP builds there are 8 or more partitions.

But for some unknown reason, only 4 partitions have been made available, for user to select from, in Tilapia and Grouper TWRP by JENKINS, as the Dev.

Missing partitions are "Recovery", "Persist", renamed to "Staging", very unique to this device. "Radio" normally "Firmware or Modem", "EFS"

All these are referenced in "fstab.grouper" file.

That is normally in ALL other TWRP Versions, is called "Recovery.fstab" file stored in Root, that lists ALL Partitions, Mount points, Type (is emmc, ext4, f2fs, vfat, which are format types, used in Android OS.) Lastly Flags, that sets what function within each partition, can be performed, ( ie wiped, backed up, is present, overwritten during flash process, restored, etc).

Also Mount options are limited, to 4 Partitions, compared to other TWRP builds on numerous devices.

To discuss these issues the Dev needs to be contacted.

Jenkins is that Developer. On TWRP.me WebSite. DEVELOPERS are listed, of which, Jenkins is listed as a Dev. for multiple Device's TWRP builds, including multiple versions, available from original to present. Info lists released, or published dates, testing, stable or failed, for each and every Release, all there, to view for every build, and every device,

that a TWRP build exists. Check it out!!!!

https://jenkins.twrp.me/job/tilapia/18/consoleText This is the latest release for TWRP 3.5.0_9-0-tilapia. There lots of devices listed. Interesting reading. It appears, but not sure, includes Samsung, LG, Motorola, OPPO, seem to use same TWRP, code possible same hardware, architecture, used by different manufacturers. Therefore listed under Tilapia, same as Grouper, versions of Asus Nexus 7 2012 Tablets.

So after that long explanation. WHO IS JENKINS ???. What is his User Name on XDA or Telegram, so I can communicate with him.

Thank you to anyone whom can help.

Cheers. BeeJ1109
[Nexus 7 Android Development] AndDiSa:
@BeeJ1109 sorry guy, you are going completely out of topic here. This thread is about the Android AOSP 7.x ROM, not about TWRP, Jenkins or anything else. Please respect the forum rules.

P.S.: Some additional hint fo you: CI/CD with Jenkins
[Nexus 7 Android Development] BeeJ1109:
[

Not much use to me. Way above my Knowledge CI/CD with Jenkins.

I already mentioned "Jenkins" is a Server. So "Jenkins the Dev" is just some automated process that updates, 1000s of published, TWRP versions, updates Sources that Devs, use to compile their ROMs.

Please tell me, whom is the TWRP for Tilapia device DEV. SIMPLE QUESTION, requires a simple answer.

My post, It's also about your Restrictive ROM, how it is Built, Examples -

1. Very small System Partition. 638 MB, norm is at least 1 GB on 32GB device.

2. "Internal Memory" not recognised in some apps, seems to be Internal Storage.

3. "Staging" partition, different FSTAB configuration, compared to Android AOSP standards, used by Most other Manufacturers, Please explain what is "Staging" partition function. I am assuming, same as "Persist". Maybe "Preload", but not normal for Custom, only Stock ROMs.

4. as well as, TWRP.

So it is NOT OFF TOPIC, That's is only in your opinion.

You Do Not Write The Rules. Anyone can ask Questions, Especially if they are TECHNICAL in nature.

These Forums are NOT Exclusive to Developers. Users have Rights, as well. Otherwise, we could not be Members of XDA.

XDA Moderators and Senior Admin, write the Rules, not OPs or DEVs.

I did lots of searches on XDA, most responses were relating to old ROM builds, Android 6 or earlier, with one other on 7.1.2 from 2017, nothing being updated.

Only your ROM is presently being the one and only, that is current.

Nothing is mentioned, about TWRP, other than how to flash it from start. Unlock then sideload, same as your page 1. So support for this old device has stopped by all others, lost interest,etc.

So congrats, for your ongoing effort, on updating security, on your ROM.

Big Thank You, from ALL Nexus 7 users for last 4 years.

Have a nice day,

Cheers
[Nexus 7 Android Development] Timmmmaaahh!:
Good morning everyone!

@BeeJ1109 TWRP talk in a ROM topic is indeed not entirely off-topic. However! Elaborating to this extent (eg. about TWRP's build server) isn't relevant to this ROM. More importantly; when the author of a ROM thread (usually its developer) request to change the topic, we will support that. He or she delivers the work, therefore he or she determines the do's and don't of the conversation. I believe that's a fair tradeoff for the amazing work they deliver. I could quote a bunch of rules but in the end it's simply a matter of mutual respect. Let's honour that and move on.

Please don't discuss this any further in the thread. All comments and/or questions are most welcome in my PM box.

Have a great day and keep it safe folks!

Timmy
[Nexus 7 Android Development] Flounderist:
WHO IS JENKINS :ROFLMAO:
[Nexus 7 Android Development] KainRaziel:
After a few days of use, I confirm that the rom looks great on my Nexus. Only the browser on some sites crashes and the clock does not switch to analog from the settings, but remains on digital after restarting by itself. Thanks Anddisa for the amazing work.
[Nexus 7 Android Development] rahimali:
@AndDiSa can we have some fun with Jenkins if you have no major objections? :cowboy:
[Nexus 7 Android Development] Coldblackice:
Which filesystems are you guys using for your partitions, f2fs or ext4?

I've just dusted off the N7 after years of unuse, and see that I last used this tablet back when f2fs was "new", and it was suggested to switch N7's partitions over to f2fs to overcome the horrific sluggishness that was creeping up on people. Is this still the case now?

My Data and Cache partitions are the only ones currently on f2fs, and I'm willing to switch them over to ext4 before flashing this ROM, if recommended. I'm excited to be able to have a functional tablet again!
[Nexus 7 Android Development] AndDiSa:
you can keep /cache and /data on f2f2 if you want, the ROM supports it. /system will be ext4 always (it is read-only, so f2fs does not provide any advantages). Personally I didn't see much differences between ext4 and f2fs on /data and/or /cache but other people probably have different experiences.
[Nexus 7 Android Development] Coldblackice:
Thanks AndDiSa. So to clarify, you're using ext4 for all your partitions then?
[Nexus 7 Android Development] AndDiSa:
@Coldblackice Well, I was using ext4 for all partitions ... ;-)

Unfortunately my device doesn't work any longer.
[Nexus 7 Android Development] johndaog:
I'm sorry to hear that Andisa. Your android build for the Grouper device is light years better than stock android 5.1.1. the stock software made me pull out my hair it was so slow. It's given me hours of pleasure flashing roms on the Grouper. Yours is the best though. I'm sad to hear your tablet is tired. Your community involvement is much appreciated.
[Nexus 7 Android Development] AndDiSa:
New versions with security patches for March 2021 are available for testing

Hi guys,

new month ... new patches are arriving :)

I've just updated my Github-repos to the latest version of the ROM having the security patches for March 2021 applied to it. Here are the OTA-packages for Grouper and Tilapia:

7.1.2 Grouper OTA-Package 20210305 md5: c0a1f205254c49355cca1d350b65e33b

7.1.2 Tilapia OTA-Package 20210305 md5: 0801569114aa0531d992f1004c90dc11

As always, please note, that these versions are untested. I'll wait for some feedback from the community before I'll update the OP.

Have fun and stay healthy!
[Nexus 7 Android Development] 123x:
Hi, is this ROM faster than CM12.1 nightly with Parrotmod? Thanks!
[Nexus 7 Android Development] BLewis4050:
Wow! I just replaced Pure Nexus 6.x and my N7 is like a new tablet yet again!

Thank you.
[Nexus 7 Android Development] adstraylight:
Sorry to keep banging on about this, but I am trying to help, honestly ?

I'm still getting the now very occasional crash that comes with a webview dump in the logs, so few now that it's barely worth mentioning. The 12/15 open gapps seem to have helped with this btw.

Slightly more often, an app will simply quit without a fc message, and the logs will show an error such as this:

12-30 08:21:23.145 F/libc (24940): Fatal signal 11 (SIGSEGV), code 2, fault addr 0x65500000 in tid 25041 (RenderThread)

Reading around about this suggests that it may be due to a bug in the adreno drivers that was introduced around rhe time of Marshmallow, and is triggered by having too many layers to render at once.

Edit: Now experimenting by disabling HW overlays, going well so far....
[Nexus 7 Android Development] rafasc:
Gave this ROM a try but had to revert due 2 issues:

1: Facebook messenger app crashes on start. Log mentioned something about io.POSIX.

2: Was trying to turn the brightness down and it turned the LCD off. I could still interact with the tablet to some extent (could hear keyboard clicks) but was unable to restore brightness. The screen was black across reboots, only lit during the booting phase.

I'll give it a try sometime on the next few days. Unfortunally, right now, I have no machine with me to provide logs for those issues.
[Nexus 7 Android Development] danielsf:
May I ask, does this ROM support CPU and GPU clock and voltage control please? Been running 1.6ghz CPU and 600mhz GPU for years :)
[Nexus 7 Android Development] psiphi:
Use Facebook Lite instead of messenger as a work around.
[Nexus 7 Android Development] Dawscaus:
Just flashed this rom and I can confirm problem #2. I was fortunately able to get the screen back by sliding the slider as if I could see it. will report other findings as well.

secondly can this be installed to an \system formatted to f2fs?
[Nexus 7 Android Development] cdx47:
The problem is Adaptive Brightness. If you turn it off the issue goes away.

---------- Post added at 08:56 AM ---------- Previous post was at 08:50 AM ----------

Same here.
[Nexus 7 Android Development] AndDiSa:
For those people having problems with the adaptive brightness: most likely the min. value is not set correctly. You can change the range by using e.g. trickstermod.
[Nexus 7 Android Development] Portgas D. Ace:
Yes, use Performance Control or Kernel Adiutor for kernel tweaks.