yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] Expell93:
Hi, does this ROM still have got problems with charging? I'm not able to reach more than 800mA, which with my usage of Nexus (constantly powered on screen) finishes with total baterry drain after few hours. I've got two tablets, and both are behaving the same
[Nexus 7 Android Development] crannachan:
Hi, I was looking solution for a long time with no luck. My BT headset xiaomi connects always just as "Media audio" on this grouper rom, while it connects properly (with mic symbol and more active profiles) on my other Nougat tab. I'm sure it has to do with codec, but there is nothing to be changed in developer options. Any hints? Maybe magisk module?
[Nexus 7 Android Development] majorfigjam:
Mine charges fine. Have you changed the battery? After 11 or more years, they will likely need replacing.

It's easy to do, if you can find a replacement nowadays, but beware of getting old stock that's been lying on someone's shelf for years.
[Nexus 7 Android Development] js-xda:
Stopping by out of curiosity and amazed to see this being still very actively maintained! Congratulations and all the best to keep it running another few years!
[Nexus 7 Android Development] AndDiSa:
New releases with 2024/07/05 security fixes are out!

Hi guys,

here a (delayed) quarterly update of the ROMs.

I just updated the ROM files for Grouper and Tilapia having all the security updates applied to them up to July 2024. Even the kernel got further security fixes which I magpied from the DivestOS project ... ;-)

In the OP you can find the links to the Gapps- and MicroG-versions.

Please note: I didn't upload to AndroidFilehost as the servers had/still have issues. You can download directly from my webspace though ... but probably the download speed will not be as good as you are expecting.

The repositories on Github are updated, too.
[Nexus 7 Android Development] colt2x:
Great! I have given the Nexus7 to a friend, but this is awesome, specially knowing the new requirements of Google (why the Lineage dropped so many devices now), so you do an amazing work :)
[Nexus 7 Android Development] dizzymon:
This rom doesn't run stable on my nexus 7. I found the lineageOS 14.1 runs snappy and most stable. I had used AOSP for years but it got really slow and crashed a lot.
[Nexus 7 Android Development] dark0shark:
Dear @AndDiSa , thanks a lot for providing updated ROM, it installs seamlessly. As Open GApps pico edition is too big to install, I switched to the much smaller BiTGApps edition, see https://bitgapps.io/ (Download: https://dl.bitgapps.io/release/BiTGApps-arm-7.1.2-v3.5-CORE.zip), works great.

See also https://xdaforums.com/t/android-14-gapps-bitgapps-for-android.4012165/
[Nexus 7 Android Development] gwanbear:
I've returned here from a test spell on Lineage, which I eventually found too laggy/hangy. So. I restored a previous AOSP backup and dirty flashed the latest ROM. Perfect. It's good to be home :)
[Nexus 7 Android Development] jsomething:
hi, i just wanted to make sure this is the correct rom for my 7. its the very old first one. i got the 2nd one with lte right after and never really used this one. found it in a drawer, plugged it in and it seemed to work, just super laggy. i reset it to factory and let do some updates and now is dead. stuck on the little guy with his belly open saying no command.

i'm pretty sure its at least unlocked or rooted, i don't remember. it has the TWRP as i saw it during one of the reboots. but i can't get into it now its just dead, i can get it to the screen asking to send the file you want to adb to side load.

i haven't flashed a rom in atleast 10 years and don't remember much of it.

would this rom work to get this back booting up? i mainly just want to watch youtube on it at work. i have a very boring job sometimes haha. if this rom will work on it, can someone refresh my memory as to what i need to do?
[Nexus 7 Android Development] AndDiSa:
@jsomething you need to get at least into your bootloader to install a new ROM on the device, i.e. pressing vol- + power buttons at the same time when switching on the device. From there you can install TWRP and at the next step you can install a new ROM.
[Nexus 7 Android Development] jsomething:
thanks for the reply. so here's what I've tried so far. I'm at this on the tablet. (see Pic)

I downloaded the sdk and opened a cmd in windows, did adb devices and something showed up, figured it was the phone.

so I downloaded twrp-3.7.0_9-0-grouper from your first post and did the adb side load and showed it the path. it looked like it loaded and tried to install but failed verification I think it said, I should taken a pic. so then I tried side loading the aosp_grouper-7.1.2-ota-20240703.eng.ds.zip.

same thing, it looked like it sent it. tried to installed but failed.

I'm sure I missed a step in there somewhere. Hopefully it's oblivious. uploaded a Pic of the back to confirm I have the correct year 7.

thanks again for looking.
[Nexus 7 Android Development] jsomething:
this is the error I get trying to side load twrp
[Nexus 7 Android Development] AndDiSa:
@jsomething it's the correct device as far as I can see, but you are on the "offical" recovery which doesn't accept a selfsigned installation package. You first need to install TWRP on the device. I would suggest to use the fastboot method as described at TWRP installation for Nexus 2012

After booting into TWRP the sideload of the ROM package should install fine.
[Nexus 7 Android Development] jsomething:
i pushed the twrp file at the like to it using side load. it gives the same error. wrong footer or something.

reboot into fast boot doesn't seem to do anything but error : closed.

is it possible the recovery died? I can't get into anything really but it boot loops if I hit reboot. I have the option to adb side load. wipe data and cash but those don't do anything.

is there a factory recovery I need to push to get into fast boot so it will install twrp?
[Nexus 7 Android Development] AndDiSa:
@jsomething you should go into fastboot mode by pressing "vol-" and "power" at the same time. If you are in fastboot mode (no need to select anything else on that screen), you need to

fastboot flash recovery <twrp.img>

having connected your device to your PC.
[Nexus 7 Android Development] jsomething:
ha.. I didn't realize fast boot was that page. I was going further.

got twrp to work and your rim flashed. gapps did error 20.

i didn't see anything about error 20 in the first 2 posts just 7 and 70. any thoughts?

thanks for your help
[Nexus 7 Android Development] jsomething:
it's kinda embarrassing how bad I am at remembering this stuff haha.

OK. I was downloading the wrong gapps, it defaulted to 9.0 not 7.1. I think got the right ones and now got the error 70. I tried putting the text doc on the SD card and install gapps and failed again. tried putting both in the platform tools and pushing gapps using adb sideload.

i see something about deleting system partition before applying Ota package. I'm not sure what this means.
[Nexus 7 Android Development] AndDiSa:
@jsomething you need to get the correct gapps as even the tiniest ones are too big for Grouper, but please have a look at this post from some days ago The Gapps linked there should work for you.
[Nexus 7 Android Development] timbuctoo:
I got a Nexus 7 tablet (model number: ME370T) of Asus make for free. There seem to be many variants of the Nexus 7, so I don't know if I can go about flashing this ROM. Else, what other custom ROM options does this model have? Can anyone please help and confirm?

Thanks in advance.

Cheers.
[Nexus 7 Android Development] majorfigjam:
ME370T = Grouper = Asus Nexus 7 2012 WiFi model.

So yes, you can flash this ROM.

Read the OP instructions very carefully, and note issues with GAPPS which were recently addressed and solved here https://xdaforums.com/t/rom-nzh54d-...s-ext4-android-7-x-aosp.3467514/post-89593942
[Nexus 7 Android Development] timbuctoo:
Many thanks for the swift confirmation. Whew! So I can still put the tablet to good use :)

Btw, for future reference, where is this mapping documented?
[Nexus 7 Android Development] timbuctoo:
Not to stir a controversy here, but has anyone tried the Resurrection Remix ROM as well? RR is renowned for its extensive customization, while AOSP for simplicity and performance. Merely checking to know which one is better suited to be a daily driver with fewer issues.
[Nexus 7 Android Development] gwanbear:
Ime, the best performance was going google free, on whichever ROM. I tried out a lineage version (with google) and found it annoying slow. Without google, it was ok but of lesser use to me. There was no microg version. My own feeling is that it's the device's memory limitation that's the bigger consideration on performance, difference between ROMs less so.

From my trials (and they are not exhaustive by any means) the microg version of this AOSP ROM is about as good as it gets (for my purposes)
[Nexus 7 Android Development] majorfigjam:
Google Nexus 7 ME370T 32GB (Asus Grouper) | Device Specs | PhoneDB

Specs: 2012 Nov, Android, NVIDIA Tegra 3 T30L (Kal-El), 2011, 32 bit, penta-core, 32 Kbyte I-Cache, 32 Kbyte D-Cache, 1024 Kbyte L2, 40 nm, NVIDIA GeForce ULP MP12 GPU, 1 GiB RAM, 32 GB ROM, 7 inch, 1280x800, Color IPS TFT LCD display, NFC: Yes, GPS, 1.2 MP camera, L sensor

phonedb.net
[Nexus 7 Android Development] timbuctoo:
Thanks. I found it reports grouper as well when rebooting to the bootloader (fastboot).
[Nexus 7 Android Development] MalkiYahu:
I have one problém with this ROM "Acore has stopped" pls help
[Nexus 7 Android Development] Paddy's:
Thank you, so do you think the values showed by the ampere app are fake?

I know the 2012 N7 doesn't support quick charge, but i tested the chargers and the aukey quick charger 2.0 has better performances, the N7 reaches 100% charge faster with it.
[Nexus 7 Android Development] adstraylight:
The charging controller in the tablet will cut the charge rate if it senses a dip in the supply voltage, to prevent damage to the charger. So it sounds like the faster unit just has more variability in its supply.

Charging through the pogo pins is more reliable, as there is more of a constant contact between the charger and the battery. This is because there's a flaw in the N7's design, in that the usb port connects to the​ mainboard via a very flimsy internal ribbon connector, which in turn causes an inconsistent voltage to get through to the battery.

This is why I bought a dock several years ago.

It was also generally thought that Google had made some slight change to the charging perameters that made the issue worse, back around the time of KK iirc, but I'm not sure if this was ever resolved as the discussion always ended up with some people saying it was HW, and others SW. In truth I think it is both, but people don't like complex answers.
[Nexus 7 Android Development] shibadoo:
OK, obviously SuperSu does not install in systemless mode on my tilapia, but why?

/data # cat .supersu
SYSTEMLESS=true
/data # mount
rootfs	on	/	type	rootfs	(rw,seclabel,relatime)
tmpfs	on	/dev	type	tmpfs	(rw,seclabel,nosuid,relatime,mode=755)
devpts	on	/dev/pts	type	devpts	(rw,seclabel,relatime,mode=600)
proc	on	/proc	type	proc	(rw,relatime)
sysfs	on	/sys	type	sysfs	(rw,seclabel,relatime)
selinuxfs	on	/sys/fs/selinux	type	selinuxfs	(rw,relatime) tmpfs	on	/tmp	type	tmpfs	(rw,seclabel,relatime)
/dev/block/mmcblkOpS	on	/cache	type	ext4	(rw,seclabel,relatim e,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p10	on	/data	type	ext4	(rw,seclabel,relatim e,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p10	on	/sdcard	type	ext4	(rw,seclabel,relat ime,user_xattr,acl,barrier=1,data=ordered)

During installation there is no hint for an error at all. It says

System-less mode, boot image support required

In recovery.log I see the following lines which are interesting:

*****************
SuperSU installer
*****************
- Mounting /system, /data and rootfs
mount: mounting /dev/block/mmcblk0p10 on /data failed: Device or resource busy
...
mkdir: can't create directory '/su/bin': File exists
mkdir: can't create directory '/su/xbin': File exists
mkdir: can't create directory '/su/lib': File exists
mkdir: can't create directory '/su/etc': File exists
mkdir: can't create directory '/su/su.d': File exists
- Removing old files
- Placing files
rm: can't remove '/su/bin/su': No such file or directory
rm: can't remove '/su/bin/daemonsu': No such file or directory
rm: can't remove '/su/bin/supolicy_wrapped': No such file or directory
rm: can't remove '/su/lib/libsupol.so': No such file or directory
rm: can't remove '/su/bin/sukernel': No such file or directory
...
- Flashing boot image
dd: writing '/dev/block/mmcblk0p2': No space left on device

Any idea what to do?
[Nexus 7 Android Development] AndDiSa:
[MENTION=980259]shibadoo[/MENTION] looks to me as if /data cannot be mounted while SuperSU is beeing installed which leads to the situation that su.img cannot be created and so installation failed.

Do you have /data formatted as f2fs? This might be a problem because of f2fs issues.

Edit: no, I see it's ext4.
[Nexus 7 Android Development] spark001uk:
I remember seeing someone writing somewhere (think it was actually chainfire come to think of it) about when flashing supersu in TWRP it decides for itself whether it needs to install systemless or not? It seemed to do so for me anyway, I remember the progress messages saying something about checking compatibility, followed by installing systemless.
[Nexus 7 Android Development] AndDiSa:
Yes, SuperSU can decide automatically, but only for supported devices. At least for me the automatic decision failed, but you can force systemless installation as I described in my second post.
[Nexus 7 Android Development] shibadoo:
I tried to root it via NRT (Nexus Root Toolkit) and voila:

tilapia:/ $ mount | grep loop0
#/dev/block/loop0 on /su type ext4 (rw,seclabel,noatime,user_xattr,acl,barrier=1,data=ordered)
tilapia:/ $ #

But "Performance Control" still claims there is no root. I deleted it from SuperSu and started again, and it seems that it does not request root from SuperSu. At least there is no message from SuperSu that Performance Control tries to get higher rights. Maybe Performance Control simply does no work anymore, there were no updates since months (years?).

So anyway thanks for your patience and for supporting the Nexus 7 2012!
[Nexus 7 Android Development] k ahangar:
becuase i downloaded last vertion of 2016 3 weeks ago, and i didnt flash that yet. but if my download speed will good i,ll download last version soon:)

thnks my freind
[Nexus 7 Android Development] Mpanco:
The HDR works?
[Nexus 7 Android Development] AndDiSa:
[MENTION=4933014]Mpanco[/MENTION] You mean High Dynamic Range photos? Are you kidding?
[Nexus 7 Android Development] Mpanco:
I'm not kidding. I take a lot of photos for work and I need HDR
[Nexus 7 Android Development] Nexive:
The Nexus 7 2012 does not have a camera on the back so how would you take pictures with your Nexus 7? :P
[Nexus 7 Android Development] Mpanco:
:eek: Wrong thread! Sorry guys
[Nexus 7 Android Development] k ahangar:
[MENTION=2188693]AndDiSa[/MENTION] hi, i download 2017 version just now:o and i try to flash it tonight...

just, i have a question. how we can to create a boot sound useable for this rom or others?

thnks
[Nexus 7 Android Development] cosmickamal:
For me everything works as it should including charging. Only problem is WiFi reconnection issues. Hope it gets solved in near future.
[Nexus 7 Android Development] shibadoo:
Found a solution, credit goes to https://dammit.nl/p/962. Open an adb shell on your computer and then:

adb shell
su
mount -o remount,rw /system
touch /sbin/su /system/bin/su /system/xbin/su
mount -o remount,ro /system
exit
reboot

First I had the problem that after "mount -o remount,rw /system" I got "device busy". So I booted into TWRP, mounted /sytstem there and again opened an adb shell on my computer. Now Perfomance Control works again (and some other older apps that look for hardcoded paths of the su binary).
[Nexus 7 Android Development] AndDiSa:
[MENTION=980259]shibadoo[/MENTION] so it looks to me as if PerformanceControl is not compatible with systemless root ... 8-0
[Nexus 7 Android Development] Bakica:
Shibadoo, where did you find a PerformanceControl in AndDiSa's AOSP?

Thanks in advance.
[Nexus 7 Android Development] AndDiSa:
[MENTION=5871663]Bakica[/MENTION] I suppose he installed it as an external application.
[Nexus 7 Android Development] pacorrop:
Great job, m8! However, idk if I'm doing anything wrong, but you state (in italic font)

However, when I boot that TWRP version and cat /proc/filesystems, I can see f2fs as supported. So it's OK!
[Nexus 7 Android Development] shibadoo:
Correct, I installed is as an external application. Is it compatible? Depends on how you define "compatible". With the aformentioned changes it works ...
[Nexus 7 Android Development] kjelderg:
Custom cling?

I installed the 7.1.1 rom and mini gapps on a fresh grouper device. It boots to what looks like android, but is not interactive and has the following message displayed: "Error: custom workspace layout passed in but custom cling was not overwritten". Any ideas?
[Nexus 7 Android Development] AndDiSa:
Sorry, but could you please describe a bit more details of your problem and how you got there? A screenshot probably could help, too.
[Nexus 7 Android Development] kjelderg:
That wasn't very clear, was it?

I installed the 7.1.1 for image with TWRP sideloading. Everything seemed as expected.

The device boots up to the home screen UI but with just the Google bar at the top and the launcher bar at the bottom. There are app icons neither on the home screen nor the launcher bar. The center icon that normally opens the app drawer is present but does not function.

The message I posted is written over the launcher bar.

I can try to get a picture of the screen this evening.

I tried reinstalling and have chosen the error cache and dalvik a couple times with the same results.
[Nexus 7 Android Development] AndDiSa:
[MENTION=7998021]kjelderg[/MENTION] Did you have a different ROM installed before? Did you wipe everything (/data, /cache,/dalvik-cache) before installing / booting the new ROM? If not, this can mess up things.
[Nexus 7 Android Development] shaggyskunk:
[MENTION=2188693]AndDiSa[/MENTION]

There's been at least one other person who got "no o/s installed with TWRP 3.0.2-0.

The o/s is actually installed - I posted the recovery log on Original Development for Dees_Troy a few days ago but didn't hear back - I posted the recovery log on TWRP 's github this morning.

But I'm not sure if it's a Rom issue or TWRP 3.0.2-0

Have a look if you have time

https://drive.google.com/file/d/0B9TbnlZl-ugWaV9lWFNJN3VDNUU/view?usp=drivesdk

Sent From My SM-N930W8 ??
[Nexus 7 Android Development] kjelderg:
I just bought the device and had the stock ROM. I will try wiping /data as well.
[Nexus 7 Android Development] AndDiSa:
In that case you probably should check whether you have already the latest bootloader and twrp installed.
[Nexus 7 Android Development] kjelderg:
I unlocked the factory loader and installed TWRP which seems to be working. It at least let's me install the ROM.
[Nexus 7 Android Development] ufa:
I'm getting lots of this on logcat:

01-15 15:34:54.962 576 603 E sdcard : *** NOTIFY FAILED *** 22

01-15 15:34:54.962 576 603 E sdcard : *** NOTIFY FAILED *** 22

01-15 15:34:54.969 576 603 E sdcard : *** NOTIFY FAILED *** 22

01-15 15:34:54.969 576 603 E sdcard : *** NOTIFY FAILED *** 22

01-15 15:34:54.976 576 603 E sdcard : *** NOTIFY FAILED *** 22

01-15 15:34:54.976 576 603 E sdcard : *** NOTIFY FAILED *** 22

01-15 15:34:54.991 576 603 E sdcard : *** NOTIFY FAILED *** 22

01-15 15:34:54.991 576 603 E sdcard : *** NOTIFY FAILED *** 22

01-15 15:34:55.008 576 603 E sdcard : *** NOTIFY FAILED *** 22

01-15 15:34:55.008 576 603 E sdcard : *** NOTIFY FAILED *** 22

Is there a way to fix this?
[Nexus 7 Android Development] cosmickamal:
Surprisingly, wifi reconnection issue is not present in [MENTION=3729448]aaopt[/MENTION] 's Lineage OS .

thanks to these two guys [MENTION=486859]andis[/MENTION]a and [MENTION=3729448]aaopt[/MENTION].
[Nexus 7 Android Development] AndDiSa:
[MENTION=4351374]shaggyskunk[/MENTION] I do have the same message when I am wiping system and flash the zip file using TWRP. I suppose it's due to the fact that TWRP is not really compatible to 7.x and so doesn't identify the flashed system as new OS, but it's only a guess.
[Nexus 7 Android Development] aaopt:
Are you sure? I definitely have wifi issues on my tablet, though they seem to come and go. Normally the connection says it is holding but download speeds drop down to sub-dialup speeds. I don't do a lot of heavy stuff on my tablet so I mainly notice it when updating apps in Google Play.

---------- Post added at 12:51 PM ---------- Previous post was at 12:49 PM ----------

I don't have that error with LineageOS. Perhaps there is some specific file TWRP is looking for that AOSP doesn't include anymore.
[Nexus 7 Android Development] AndDiSa:
[MENTION=3530008]ufa[/MENTION] there is nothing to concern about, it's more an internal error handling issue
[Nexus 7 Android Development] AndDiSa:
[MENTION=3729448]aaopt[/MENTION] did you try to wipe /system, then installing the ota zip and then trying to reboot into recovery or system? I have this message only when I wipe /system within twrp otherwise I don't have that message.
[Nexus 7 Android Development] aaopt:
I'll try when my build finishes. For lineage I always wipe system but I don't usually reboot between ROM and Gapps.

Edit: My build finished. I wiped system, cache, dalvik as usual, installed just lineageos, and went to "reboot recovery" -- no message about missing OS. Tried reboot system too, also no message. While I was building, I tried digging in TWRP source to see what they are checking for but didn't find it yet... the connection between the code and the message in the resource file is not yet clear to me.
[Nexus 7 Android Development] cosmickamal:
Yes. i didn't face any wifi reconnection issue on this ROM. Lets wait and watch. I will report if I do notice it in future.
[Nexus 7 Android Development] adstraylight:
I have a theory about this, as I only get random disconnects when bandwidth on the router is limited. I think that the tablet has a low threshold for throughput that causes it to try to re-establish the connection, some kind of packet error control maybe? This has only become a thing since using Nougat roms.
[Nexus 7 Android Development] spark001uk:
I haven't noticed any disconnects thus far, but I have done a few speed tests and the down seems to top out at around 20mbps on my Rock steady 37 fibre line. Could just be the N7 hardware though? Can't say I remember checking it before this rom.
[Nexus 7 Android Development] kjelderg:
[solved] Re: Custom cling?

Sure enough, I neglected to clear /data. The ROM is running and looks promising.
[Nexus 7 Android Development] Torgar:
Hello.

Im running the last tilapia build and the wifi reconnection issue is on my N7. speed test top out, stop at around 20mbps.
[Nexus 7 Android Development] Codster314:
I also notice this as well. I tried out the Lineage OS ROM, 4 days ago, and I haven't experienced a Wifi Disconnect yet. I notice he uses AndDiSa's kernel directly...

I'll let you know after more time has gone by, but when I was on this ROM I was disconnected almost every 2nd "Clash of Clans" battle (would notice it within a day at most, often within hours...) It's been 4 days on Lineage and many battles with no disconnect. It may be too early to tell, and maybe I've just been lucky. I'll let ya know.

That said, Lineage may still have other Wifi issues? Donno, but at least it's not cutting CoC mid-battle. Again I'll let ya know after a week of use.
[Nexus 7 Android Development] pehlm:
Hi, how is the easiest way to install Viper4Android on this ROM? I tried to install a 2.4.0.1 apk but this wasn't working, there was an I/O error when I tried to install the driver (it seems that the old Viper version is not compatible with Nougat). I'm not really willing to flash it neither, it would be best with just an apk to install. Thanks!