yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] shaggyskunk:
If you restored using TB - uninstall and reinstall from the store - Same thing was happening with Google Drive until I did the above m

Sent From My SM-N910W8 ??
[Nexus 7 Android Development] AndDiSa:
It's already for years that I didn't use TB ... there is almost no need for it. When updating to a newer version of the ROM the data partition is not touched and all apps / data remain installed. Probably when switching between differen ROMs it may be useful, but after restoring you often have FCs or wrong settings ... :(
[Nexus 7 Android Development] shaggyskunk:
Yes - However when I Flash a Rom - I almost always: Factory Reset - Advanced in TWRP 3.0.2-0 - Manually Wipe System - Data and Caches - Flash Rom and Gapps - Flash SuperSU - Reboot and set up.

For me using TB to restore USER apps ONLY is very useful.

Sent From My SM-N910W8 ??
[Nexus 7 Android Development] AndDiSa:
... if you renounce on factory reset and only wipe system / cache / dalvik-cache everything should work in the same way and you can skip the apps restore step :)
[Nexus 7 Android Development] Portgas D. Ace:
Only if it is the same ROM. Switching ROMs without wiping data partition causes instability, such as FC's.
[Nexus 7 Android Development] sephren:
I didn't restore anything and wiped caches etc, but i have those crashs nevertheless. Any idea how to improve the situation here? I'm totally clueless regarding those ROMs, but it seems like mem-free is too aggressive or something like that.

---------- Post added at 02:04 PM ---------- Previous post was at 01:54 PM ----------

Oh, is wiping data partition not included in TWRPs default factory reset? Then this would explain all problems i see :D
[Nexus 7 Android Development] Portgas D. Ace:
A factory reset with TWRP should wipe the data partition as intended (see here).
[Nexus 7 Android Development] Codster314:
Me as well, on latest Jan 5, 2017 build. I've seemed to have it on all the old Andriod 6/7 roms I tried as well for my Nexus 7 (grouper) - perhaps a kernel issue? It's very slight. And you can't tell it's happening all the time. But for example while playing "Clash of Clans" in a battle the wifi will disconnect and connect quickly, and then it will kick you from the Battle and say you lost connection. You will be connected right back (but kicked out of the battle). This happens almost every 2 or 3 battles.

Most apps just see the disconnect and reconnect and do not do anything, so you do not even realise wifi is connecting and disconnecting. It's only some "sensitive" apps you notice it where it'll kick you out of something cuz of the temporary internet disconnect. Like I said I only notice it on Clash of Clans, and then only notice it when I am in a battle on Clash of Clans (as the app is fine with intermittent internet/wifi in the "lobby" or other parts of the game). And of course Chrome and everything you do not even notice internet cutting for half a sec.

I believe people who think they do not have "wifi disconnect issues" are just people who do not realise it's happening as the apps they use are fine with intermittent internet (like web browsing or such).

I've had this for a while with my Andriod 6/7 roms, then I moved to SlimKat (4.4.4) for a couple months and there were no wifi problems. Then with all the positive reviews about 7.1.1 I thought I would try this to see if it was fixed... it's not though. Any ideas what I can do to fix it? or help I can give to solve it? It never happened with Andriod 5, I believe started happening later in Andriod 6, and all of the Andriod 7 roms I've tried.
[Nexus 7 Android Development] AndDiSa:
I do see from time to time those re-connection issues, too, but I've currently no idea what might be the reason. Probably it's related to old binary drivers or firmware. On startup you can find some error messages regarding WiFi within the logs but nothing really to concern about. If I find some time, I'll try to have a deeper look at it.
[Nexus 7 Android Development] spark001uk:
My issue and how I resolved it!

OK I thought I would share my experience to help anyone that may be running into a similar problem to mine, and how I fixed it.

I have a Wifi N7 (grouper) that updated itself to 5.1.1 (stock) a while back, and started running like a dog, so I thought time for a ROM.

I chose the 7.1.1 ROM from this thread as I was recommended it.

So, here's what I did first time round (which gave me problems):

- Using NRT, unlocked bootloader, and installed root/TWRP 3.0.2

- Placed 7.1.1 OTA, and dynamic gapps, onto internal storage

- Rebooted into TWRP, advanced wipe, wiped everything except internal storage.

- Installed the 7.1.1 OTA, then wiped Dalvik.

- I then rebooted and let it boot fully into android. THIS is where the problems started.

It booted straight to a home screen with a clock and a few icons. It didn't go through new device setup. I then rebooted into TWRP, and installed dynamic gapps. When I rebooted back into android, I started repeatedly getting a "Google Play Services keeps stopping" message, and nothing I did seemed to help, I tried all sorts of suggestions, such as clearing play services data, allowing all its permissions etc, nothing worked. So I had to start again and reflash the ROM.

Here's the procedure I did which worked fine:

- Rebooted into TWRP, advanced wipe, wiped everything except internal storage.

- Installed the 7.1.1 OTA, then wiped Dalvik.

- Rebooted, but immediately held pwr/vol- to get straight back into TWRP. **DON'T let it boot normally into android.!**

- Installed the dynamic gapps

- Rebooted again, this time letting it boot normally (1st boot will take a while)

- On boot, it enters setup and you can just take it from there (I always setup as new device, to avoid any possible issues)

Only thing I'm facing now is it seems to be charging rather slowly, my USB tester stick is showing the charge rate settles out at 0.6A which is quite low, it used to charge at more like 1.5A before. However this is a known issue with this ROM, so I'm sure a fix will come along. However I can confirm that disconnecting/reconnecting the charger as stated does seem to increase it a bit.

Anyway aside from that it seems to be running really well, nice and smooth, a darn sight better than the official 5.1.1 update which messed it right up! I expect Google won't be doing any more for this model either.

Thanks very much for all the hard work AndDiSa.!

Hope this helps

.
[Nexus 7 Android Development] shaggyskunk:
[MENTION=2288749]spark001uk[/MENTION]

Yes it's actually in the OP - And posted a number of times throughout the Thread ;)

Sent From My SM-N930W8 ??
[Nexus 7 Android Development] Codster314:
Ah thanks. Yea like I said, it's not a huge issue as most people don't even notice it. But I must admit for a small number of Apps, it's a very annoying thing. hehe
[Nexus 7 Android Development] pehlm:
Hi! Just installed this smooth ROM on my 2012 Nexus 7. It's like a new tablet, and I haven't used it for over two years. Thanks! :) Have some questions though. If we later have a new version of this ROM, is it secure to just dirty flash it over the current ROM or must I wipe system partition as mentioned in the OP? In the OP it is also talked about a updater script which must be updated, is this a delta updater or something? If I must wipe the system partition I must reflash Gapps and Supersu (systemless), right? I understand though that the apps and data is left, because it is no need to wipe Data upgrading to a newer version of this ROM. Grateful for some clarification on that. Thanks alot for the ROM!
[Nexus 7 Android Development] AndDiSa:
Even if a dirty flash would be sufficient I would suggest to wipe /system in TRWP before flashing the ROM. It as no impact on the following steps as the updater script which is installing the ROM does not backup gapps, so you need to reflash gapps in either way. The same is valid for SuperSU, as it should be systemless and flashin a new boot partition is removing the SuperSU installation you need to reflash SuperSU, too. Nevertheless dirty flashing is fine, though I am suggesting to do the following steps for updating:

- boot into TWRP

- wipe system, cache, dalvik-cache

- install android-aosp-xxx.zip

- reboot into recovery

- flash gapps (and SuperSU)

- reboot system

If I am not flashing directly the img-files by using fastboot, I am doing it in to way described above and I never had issues.
[Nexus 7 Android Development] pehlm:
Thank you for the quick answer! Then I understand. And either way I must reflash Gapps and Supersu. Also thanks for the quick steps to flash!

Pehlm
[Nexus 7 Android Development] G_Bot:
That happens on some older devices, when you turn on magisk hide feature in magisk. And because some file explorers dont support systemless root. But the older versions of ES file explorer works, and Fx file explorer works too when you open Fx swipe down to refresh and it will Automatically mount the Sd partiton.
[Nexus 7 Android Development] Luckz27:
Opera works wonderfully but even Fennec F-Droid does its job efficiently.
[Nexus 7 Android Development] dark0shark:
Apropos Magisk: the app offered today updating from version 23.0 to 24.1, after that patching boot image. Both update procedures worked flawlessly.
[Nexus 7 Android Development] dude1337:
I was really surprised that this is still updated, wow. Great job!

Question: Can I somehow install it without gapps? I keep getting service "has stopped" errors.
[Nexus 7 Android Development] willymoto:
Thanks for the advice. I confirmed this method works fine and got my Nexus 7 working with MicroG.
[Nexus 7 Android Development] AndDiSa:
@dude1337 yes for sure. Which service stopped? Probably you didn't wipe your data after you decided to install a non-gapps version?
[Nexus 7 Android Development] Chralu:
Thanks for that rom @AndDiSa.

My Nexus 7 runs smoothly thanks to you 👍

For now, almost everything seems to work fine.

What works : GPS, audio playback and record

What does not work : Camera (system says there is no camera). For your information, the screen has been replaced.
[Nexus 7 Android Development] AndDiSa:
New Versions 7.1.2 (2022-05) are available

Hi guys, after skipping the builds last month today I upoaded a new release with updated security, i.e. the security paches for January 2022 and February 2022.

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-20220212.eng.ds.zip (MD5: eccab1d8cfdca35a6643f65256d04fa9)

aosp_tilapia-7.1.2-ota-20220212.eng.ds.zip (MD5: 25030575f28b8d52595b59b8d88743ec)

as well as the MicroG-Patched images:

aosp_grouper-7.1.2-mg-ota-20220212.eng.ds.zip (MD5: c930aabcda55a514baf3f0ef5a6e4cb9)

aosp_tilapia-7.1.2-mg-ota-20220212.eng.ds.zip (MD5: 65a1f6ab0648db2505a56ef8c4e11144)

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!
[Nexus 7 Android Development] AndDiSa:
@Chralu you need to find an app which supports the Nexus 7 (2012) device. It's a bit specific as it has a front cam only which is not supported by all applications but e.g. HD camera is working fine.
[Nexus 7 Android Development] Chralu:
Oh thanks for the information. I’ll try some other apps 👍
[Nexus 7 Android Development] brewer75:
Both of the MicroG downloads are for tilapia, there isn't one for grouper.
[Nexus 7 Android Development] AndDiSa:
Oh, sorry ... I copied the wrong link. I'll correct it as soon as I am on my PC.

Edit: Liink is corrected.
[Nexus 7 Android Development] momentoid:
Installed this 2022-02 ROM for Grouper, 2022-02-11 GApps, confirmed my regular apps work. Everything good 👍 Thank you @AndDiSa.
[Nexus 7 Android Development] Diego_992:
Good night sorry Sir Andisa. But i am not able to start the one with microG a lot of apps crash and can´t start rom properly. Will perform a couple of wipes and hope i can start the rom. I have updated TWRP, does it affect?

EDIT 1: I think the proble is with f2fs partitions, reconverted /cahe and /system to ext4 and now it booted with out any issues.
[Nexus 7 Android Development] Konstantin Zh:
Hello! Thank you for supporting the old machine.

A small bug report: the screenshot has black bars on the sides in the standard image viewer. The screenshot will not stretch to the full width of the screen. Some image viewers from GP do not have this problem. Only standart imgViewer.

Please add battery percentage everywhere. Now it is only available on the lockscreen.

Thanks!

I have ver.20211208 Nexus7(2012)3G
[Nexus 7 Android Development] dude1337:
I just flashed it on top of the previous version (December) without any wipe and it works fine for me! Thanks.
[Nexus 7 Android Development] :
Grouper, microg. I did a complete wipe and rebuild; clean flash and reinstallation of apps.

All is good (y)(y)
[Nexus 7 Android Development] BeeJ1109:
Hi ALL, Installed latest version Tilapia ROM, having heaps of Google Store stopping.

Restored old backup, as well as re-installed latest Gapps pico again.

Still got issues. Latest TWRP v3.5.0-9 with Magisk v24102 canary for Root.

Any clues. Cheers. BJ
[Nexus 7 Android Development] Portgas D. Ace:
In case you got issues, please do a clean flash (wipe system, data, dalvik&cache, then flash ROM&Gapps) and try to reproduce the issue. If it still persists, please provide a proper log file (search for "how to logcat" in case you aren't familiar with grabbing a log file).
[Nexus 7 Android Development] BeeJ1109:
Hi Portgas D Ace,

Thanks for the hint.

I do lots of wipes, as suggested, normally, if updating version of existing ROM, updates can be dirty flashed over existing.

If issues have wiped system, cache & dalvik. Usually fixes any issues.

Wiping Data partition - means lots of work to restore all apps & settings. Normally only required, if changing ROM, ie 10 to 11, or back to 10, as an example.

But this ROM is still 7.1.2. No issues reported with Grouper.

Previously had no issues with previous Tilapia version.

I have Nandroid Backup to restore. Then I can try again.

I changed TWRP was previously v3.4.0. Was not necessary to Update, only did it to try to the problem.

One of the Real Problems with these Nexus 7 Tablet. Is the very limited size of the System Partition, being 700 MB.

Most Samsumg devices are at least 1.2 GB.

These Tablets are 32GB, therefore plenty of room to expand the System Partition a bit larger.

Causes problems with Flashing Gapps even pico version, has to be modified to get over fault code 7 or 70, needing a modified Gapps. When first Flashing this ROM build.

See hints on Page 1-2 of the OP, by the Dev. @AndDiSa.

Noted I used the latest OpenGapps pico 7.1. Updated successfully at full size. So latest 2022 version is smaller, than previous Nov. 2021 versions.

So flash was error free.

I have asked @AndDiSa if the System partition can be modified to increase size. Have not received any response yet.

As mentioned l will continue to Restore and update again.

See how it goes. Without having to do a Full Wipe, inc. data.

Just to update.

Nexus 7 2012 Tabs are more temperamental compared to ALL my (2012 - 2015) Samsung Tablets & Phones ALL now on LOS Android 11, working great. There is now an Android 12 ROM for S3 LTE (2012) phone.

Pity Nexus 7 has not progressed beyond Android 7.1.2. Probably due to System partition size restriction.

Yes, I can produce a logcat file, if I do not resolve Google issue, of continuously stopping. Otherwise the ROM works well.

Thanks @AndDiSa for your efforts.

Cheers BJ.
[Nexus 7 Android Development] sbasstik:
@AndDiSa The normal tilapia version links to the microg Version
[Nexus 7 Android Development] AndDiSa:
Thank you very much! I don't know what happened and why the links were messed. Nevertheless should be fine now and also the md5 sums were already the correct ones. So checking the md5 is always suggested 😉
[Nexus 7 Android Development] brewer75:
I have tried flashing MicroG on my grouper with the MicroG rom build but I cannot get the Play Store to even appear in my app list even though I tried the patched version. I have tried various MicroG installers and when doing the self-check all the boxes are checked. Obviously, I'm doing something wrong so any help would be appreciated.

Update...I followed your instructions and Play Store is functioning. I can install Google apps but I can't activate and run them. Non-Google download and install without any problem. Thanks!

Update...I just followed the instructions and flashed micro g on a Samsung Tab 4 and the Play Store works for Google and non-Google apps so I'll redo this grouper and see if I can get the same results.
[Nexus 7 Android Development] :
@brewer75 maybe I'm misunderstanding you but with microg you won't have play store. You replace it with aurora store, f-droid or foxy droid... there may even be other Play store replacements out there.

If you've flashed the microg grouper ROM and microg then all you need to do is install the replacement apk of your choice (I'd recommend Aurora Store to start with) and you'll be good to go.
[Nexus 7 Android Development] brewer75:
Reference post #5000 I have used the Aurora store and was interested to see if I could do Google Play instead. I followed the instructions and Play Store is functioning. I can install Google apps but I can't activate and run them. Non-Google download and install without any problem.
[Nexus 7 Android Development] BeeJ1109:
HI, @AndSiDa,

Sorry you replied that these links for Tilapia Feb build are fixed on AFH.

I downloaded both, from links provided. microg version is linked to both.

Downloaded previously, and flashed on my Tilapia Nexus 7. Caused issues with Google apps, stopping all time.

I posted a long explanation of my issues with this ROM earlier.

Yesterday I redid the install of saved backup of previous Nandroid backup, of last working Tilapia ROM. WORKED PERFECTLY, as per previous post.

Then flashed latest version, of what I thought was "non MicroG" version.

I had both versions downloaded. I thought I was using the correct version.

Now I tried to download the "non MicroG" version again, to find you have NOT fixed the link, as both links, download the same "MicroG" ROM.

Consequently, that explains why I am still having, Google Play Services & Play Store failures again, after flashing over "existing working Dec. build" ROM.

Therefore checking the md5, shows both files are "MicroG" versions.

Therefore, can I ask you to check your files, prior to uploading to AFH, so users can download the correct files, to install either version, as the links are incorrect, still, as of Saturday your reply post # 5209. "So called fixed"

Today Monday, AFH links still incorrect.

I will check my previous downloaded ROM files with md5.

Maybe File labelling was wrong, but your sources, that you upload from, are mixed up, or labelled incorrectly.

Please acknowledge my feedback, as you have requested on testing your published updates.

Either way, now I have reason for ongoing Google issues. Not my procedures as listed in previous posts.

I will now re install the working version, until the latest Tilapia "Standard OTA" ROM is available.

Have a Good Day, hope you can fix the mix up soon.

Cheers BJ
[Nexus 7 Android Development] AndDiSa:
@BeeJ1109 I just checked the links again ... and they are correct.

In addition: please do not post wrong/misleading information. GApps will not work with the MicroG- version and will lead to issues.

One additional hint: you should probably reflect on your communication style. If you would kindly ask for help if you have issues with your device / installation everybody here in the thread will help you to fix them.
[Nexus 7 Android Development] :
I don't think you can do what you are trying to do. As I understand it, you need Google Service Framework to run some apps so you can't use the microg (de-googled) version of the ROM if you want those apps. It's one or the other and I think you are trying to mix and match.
[Nexus 7 Android Development] brewer75:
It works as I stated in my previous post. It's a personal preference whether one wants to use the Play Store or the Aurora Store and I wanted to see if I could use the Play Store. It does work if all the instructions are followed.
[Nexus 7 Android Development] :
Now you have got me confused! If it works as you want then what is the problem?

You said in your post...

...and that is what I would expect. Some Google apps will not run without the GSF.

But if you are happy and all is good then I am happy too :)

Edit: okay, I understand you now (I think) You were simply reporting that you'd got Play Store to work on microg (as an experiment or whatever) (y)
[Nexus 7 Android Development] brewer75:
I can report that I installed micro g on a Samsung Tab 4 and following the instructions referenced in previous posts, the Play Store works perfectly for Google and non-Google apps. As an example, I just installed Gmail from the Play Store and it is totally functional. I am now going to again try this process on my grouper to see if I can have a totally functional Play Store instead of the partially functioning one I currently have.
[Nexus 7 Android Development] loveandmarriage:
Hi AndDiSa

Just want to say thank you for this beautiful rom. I am using your rom for many years now and currently the mg version without any problem on tilapia. This is so amazing compared to the many other obsolete devices caused by missing support by their manufactor in the first place.

🤗😀🤗😀🤗
[Nexus 7 Android Development] Baonks81:
new mg version and pico gapps worked for tilapia 32Gb. Thanks for support
[Nexus 7 Android Development] Baonks81:
I had a script sysctl.conf from Linux and ktweak to make device running better. Because ktweak crash when Magisk up-to-date 24.1

sysctl

MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.

www.mediafire.com

Install Magisk

In TWRP, mount System. Copy sysctl.conf to /system/etc

In Android, install busybox and termux, grant superuser. Open termux, type su, then type sysctl -p
[Nexus 7 Android Development] AndDiSa:
New Versions 7.1.2 (2022-03-05) are available

Hi guys, I upoaded a new release with updated security, i.e. the security paches for March 2022 and some fixes for potential security issues within the kernel.

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-20220311.eng.ds.zip (MD5: b7c8081fd48398befbef1384e83eb509)

aosp_tilapia-7.1.2-ota-20220311.eng.ds.zip (MD5: c930aabcda55a514baf3f0ef5a6e4cb9)

as well as the MicroG-Patched images:

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)

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!
[Nexus 7 Android Development] notnoelchannel:
hello I'm not here to advertise but I made a TWRP 3.6.1-9.0 recovery, you can use it for installing this ROM :)
[Nexus 7 Android Development] AndDiSa:
It's already linked in the OP ... ;)
[Nexus 7 Android Development] :
I'm having a few problems though nothing related to the ROM. Grouper mg has installed perfectly (y)

magisk won't update to 24.3 and failed with "unable to detect target image". Seems I have to patch the boot image and reflash rather than use the 'direct install' method... so I might just leave it for now! :)