yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] OlliWi:
Hi,

can i still use the Beans gapps mini with the latest ROM or ist the open gapps (pico) mandatory?
[Nexus 7 Android Development] AndDiSa:
Probably they will work, too, I didn't check recently. But I suggest to flash the setup patch file on top of it.
[Nexus 7 Android Development] st3320620:
I have same problems with my Tilapia like [MENTION=8223593]LeSpark[/MENTION] [MENTION=8933099]13brew[/MENTION]. Fresh install and hangs on Google (sometimes reboots) and after few minutes its boots. I tried with/without pico gaps, setup-wizzard-fix or magisk. I have noticed also very fast battery drain with screen off.
[Nexus 7 Android Development] brewer75:
Beans gapps work fine with the newest build. I second the suggestion for flashing the setup patch fine.
[Nexus 7 Android Development] AndDiSa:
As I already wrote: unfortunately I do not have a Tilapia device and without any additional information, e.g. logcat, it's very difficult to analyze the issue.
[Nexus 7 Android Development] gumage:
Install

1) aosp_grouper-7.1.2-ota-eng-20180406.ds.zip

2) open_gapps-arm-7.1-pico-20180414.zip

3) SetupWizardFixCrDroidNexus7.zip

then install youtube (play market) and launched video reboot occurs.
[Nexus 7 Android Development] Sam Nakamura:
I had the Playstore not appearing issue when I flashed the most recent version of open GApps (pico) but read somewhere (search for GApps) to boot between flashing ROM and GApps and this worked, I use the device for Youtube most of the time without issues (but the magisk vanced version), no issues all good...
[Nexus 7 Android Development] AndDiSa:
... you noticed that there is a new version from 20180409 which fixed the video problem?
[Nexus 7 Android Development] gumage:
Sorry I did not notice, I will download the new firmware. Thank You!
[Nexus 7 Android Development] zikario507:
im on tilapia device, first upgrade from previous version, and then i decide to make a clean install.. but in both case im getting the same problem of freeze and reboot as other tilapia.. user..

how could be? but other than those problem.. i think it have a good perfomance! thanks you for your work friend
[Nexus 7 Android Development] loveandmarriage:
tilapia issues

I can confirm the issues regarding tilapia:

- long boot times after installation (hangs on google screen)

- erratic re-boots when using the tablet

- high energy consumption

what I have done so far

- full wipe and reinstallation (current rom, pico gapps, startupfix, no su)

- changed all partitions from f2fs to ext4 (seemed to have helped a little)

let me know if I can provide further information

Thanks a lot for the rom!!!
[Nexus 7 Android Development] AndDiSa:
[MENTION=8762190]loveandmarriage[/MENTION] sorry, without having a log file I am not able to help you ... btw. until yet I didn't get any log file reflecting the issues people are reporting here.
[Nexus 7 Android Development] mafarric0:
I second that, minus the ext4. I think f2fs is faster on the long run.

Thank you [MENTION=2188693]AndDiSa[/MENTION]
[Nexus 7 Android Development] 2x4:
the site to download TWRP is down - does anyone have it that can share it here perhaps?

https://dl.twrp.me/grouper/twrp-3.2.1-0-grouper.img.html
[Nexus 7 Android Development] Sam Nakamura:
This?

https://eu.dl.twrp.me/grouper/
[Nexus 7 Android Development] 2x4:
thanks! that one works

---------- Post added at 01:49 PM ---------- Previous post was at 01:47 PM ----------

unrelated, any recommendations for/against using parrotmod with this ROM?
[Nexus 7 Android Development] Sam Nakamura:
Well, the very first lines of ParrotMod OP says "it doesn't work on nougat (...)", so I guess it's not a good idea but you're free to try your own, just backup in TWRP and restore in case of issues...
[Nexus 7 Android Development] 2x4:
I had been using it on purenexus nougat so i was wondering if someone else had tried it and if it was helpful, but in any case i will test it out soon
[Nexus 7 Android Development] Sam Nakamura:
I use my N7 with pico GApps but only for Youtube (vanced/magisk version), browsing and little XDA labs, in addition I use LSpeed (like on all my older devices) and overall speed is absolutely satisfying for such an legacy device (even without LSpeed), can't complain at all...

But I just got one cheep off from eBay in mint condition and expected it to be Sir Lag-A-lot, what a pleasant surprise, definitely useful for my use case...
[Nexus 7 Android Development] 2x4:
i've never used Lspeed - what does it do and how does it work? i've heard very mixed comments regarding it
[Nexus 7 Android Development] Sam Nakamura:
This discussion definitely does not belong here, don't listen to what others say, check it out yourself...

https://xdaforums.com/apps/l-speed/tweak-l-speed-v1-0-02-02-2015-t3020138
[Nexus 7 Android Development] loveandmarriage:
Can you point me at an explanation on how to generate or find the respective logs? I will then provide the logs.

Thanks again
[Nexus 7 Android Development] Charles IV:
Using the

adb logcat

command. Google and lineageos wiki have done good guides.
[Nexus 7 Android Development] zikario507:
i tried to create a logcat..

idk, if this logcat could be helpful

thanks you in advance.. friend
[Nexus 7 Android Development] 2x4:
ROM works great, pretty amazed there is a current and pretty smooth ROM for the 2012 Nexus 7 in 2018

kudos to all those who worked on this project
[Nexus 7 Android Development] loveandmarriage:
logcat

I tried to create a logcat log file. The startup long waiting does happen before the logging process is started. So it is not reflected in the log, I guess. I started vlc and after a while, the nexus crashed as described.

Hope this helps to somehow find the issue ...

Thanks
[Nexus 7 Android Development] AndDiSa:
I do not see any issues related to the ROM here. Some error log entries from VLC directly, but I do not see any relation to the ROM. Looks to me as an VLC issue directly. I even cannot see a crash in the log ...
[Nexus 7 Android Development] nexus7girl:
Hi [MENTION=2188693]AndDiSa[/MENTION], Why doesn't Hall (magnetic) sensor work on every your build? What is the problem with it? Could you fix it please?
[Nexus 7 Android Development] dookie23:
Magetic sensor is working.
[Nexus 7 Android Development] loveandmarriage:
:)

That is probably because

1) the long booting pause happens before the logging process even kicks in - so it is not logged (but very much experienceable from a users point of view)

2) the crash kills the logging process and the system is down before the log was created.

=> which leads to no logged event.

I installed millosr's rom just to test and the booting is smooth and no reboot during vlc usage.

Re-installation of this rom just recreated the same behaviour.

I am very sorry to only being a rather unexperienced user - just let me know if I can provide any further information.

Thanks again for all of this - I know that it is a lot of work!
[Nexus 7 Android Development] shaggyskunk:
Just curious if anyone has tried to swap the position of the Back & Recents buttons on the Nav Bar? I searched but didn't see anything for the N7 2012
[Nexus 7 Android Development] AndDiSa:
[MENTION=8762190]loveandmarriage[/MENTION] No, I can see the log from starting until the end, but there is no entry which is indicating a crash
[Nexus 7 Android Development] Sam Nakamura:
Just opened MatLog for the first time on this ROM and saw this log spam or whatever this is. I don't think it's anything serious as the ROM run's perfectly fine, just little strange, hence the feedback...

Log

https://drive.google.com/file/d/1p3uhyUPg9RG036lgUigqf5IPj3Y-Rfot/view?usp=drivesdk
[Nexus 7 Android Development] AndDiSa:
I've never seen that in my logs and really speaking I currently have no clue from where these entries might arise.
[Nexus 7 Android Development] outofusernames:
Removing my account
[Nexus 7 Android Development] AndDiSa:
[MENTION=9108802]outofusernames[/MENTION] go optimizations are already built in ... regarding the 'slow' startup: please keep in mind that the system is not optimized after installing and that you need to give some time to the device to run optimizations. In additon: do *not* restore anything using e.g. Titanium. For sure it will cause issues.
[Nexus 7 Android Development] AndDiSa:
Well, memory is always an issue on our device, but there are no changes in memory management between the February and the April version. Probably it depends much on the background processes which are currently running. When LMK kicks in and kills the resources provider you will have some time a very bad response behaviour until memory is re-organized if in that phase you try to start other processes there is a chance, too, that the device reboots.

Btw. that the resources provider got killed you notice by not having any longer a background image ...
[Nexus 7 Android Development] OlliWi:
Hi,

i can confirm the issues with the tilapia device.

Random reboots even withour doing anything between the reboots.

Long startup time (stays at "Google" for about 4 minutes bfore the androis logo appears).

WLAN connectivity gets lost and cant be recoveres (does not change the state when enabling/disabling WLAN) .

And quite some more.....

But sometimes it´s running stable for a couple of hours without any anomalies..... that´s quit odd behaviour i guess.

I made a couple of logfiles using Catlog and alogcatroot.

But how can i attach those to my posting?

Regards.
[Nexus 7 Android Development] DumF0rGaming:
Upload them on pastebin.com
[Nexus 7 Android Development] OlliWi:
That´s too much text to be pasted.

Uploaded them on google drive, here´s the link:

drive.google.com/drive/folders/1avaQeSZjZhjvTKr-d_t7OYczkCfipH18?usp=sharing

edit: i had to remove the h t t p s : / / because a as new user i can´t include external links in my postings ;)
[Nexus 7 Android Development] brewer75:
Build 2180409 Observations

I've used these AOSP builds for some time but have had stability and unexpected reboot problems with the last 2 updates. I have cleared everything through TWRP and flashed these builds according to the OP recommendations but experience random reboots to the android screen or all the way back to the Google screen with each of these builds. I have tried eliminating apps like Facebook, Messenger, and anything else that could strain the memory but the reboots continued. I have tried rooting through Magisk or SuperSU and it didn't matter which I chose, the reboots continued, basically making the tablet unusable. Today, I cleared Dalvik, cache, system, and data and re-flashed the 2180409 build and Open gapps but I did not root. The tablet booted as expected and my apps were restored by Google backup as expected and everything seemed fine. However, I just rebooted my grouper and once again I am having the reboots to the android screen and the tablet is unusable because of the constant reboots. I've attached a logcat and hope it can shed some light on this.

UPDATE

I cleared my grouper of everything except internal storage and flashed the 20180112 build, Beans gapps, setup wizard fix and then Magisk after a reboot. I allowed Google to restore my apps from the cloud and the tablet worked great with no constant reboots. AndDiSa looked through my logcat and saw where Facebook may have been presenting problems with the 20180409 build so I decided to give that rom another try. I again cleared everything except internal storage and flashed the 20180409 build as well as Open gapps, setup wizard fix and then Magisk after rebooting per the OP suggestion. This time, instead of allowing Google to restore my apps from the cloud I did a fresh start and manually downloaded just the apps I really wanted from Google Play (no Facebook or Messenger). My grouper is working normally with no random reboots and even the boot-up process is quicker than what I had seen before. I have rebooted my tablet several times to test it and it is working great so if you are having a similar problem try a fresh start instead of an app restore. ***FYI, the logcat is from when I was having reboot problems, it is not from the newer problem-free experience I'm having now.
[Nexus 7 Android Development] OlliWi:
I had these reboot issues with the february ROM on my tilapia too, so I installed the january ROM which worked without any problems.
[Nexus 7 Android Development] brewer75:
The January rom worked fine for me as well. I've had troubles with the February and April builds but I wanted to try to keep my security patches as recent as possible so that's why I'd like to use the April build if possible.

UPDATE...I cleared Dalvik, System, Cache, and Data and reflashed the 20180112 build along with Beans gapps and Magisk. Everything is working great and no random reboots! I've done this before with similar results but I wanted to keep current and flash the most recent builds. I guess I'll stay on this build until I'm sure future builds will not cause the constant reboots.

UPDATE #2

See my UPDATE in post #2489
[Nexus 7 Android Development] iamelton:
it would be better to include the long log within a pair of "hide" tags, as just showed above..
[Nexus 7 Android Development] AndDiSa:
[MENTION=8559165]OlliWi[/MENTION] not sure what applications you are using, but if I interpret the logs correctly at least one of the apps you have installed are too big to be compiled by jit. This may also cause the other issue (even if it seems more related to the facebook app). Some process is blocking the system ui for some time and due to that the system ui process is beeing killed by the watchog which then leads to a (partial) reboot of the device.
[Nexus 7 Android Development] OlliWi:
There is no facebook installation on the device, i even don´t have a facebook account.

I noticed that there is something wrong with the UI.

I can directly tell when the bootup process did not complete successfully by looking at the WLAN icon, which will be marked with a cross, meaning "connected but no internet" - which is indeed not the case.

Also the UI is not properly reacting to the power button - it is impossible to call the restart/shutdown menu by pressing the button for a couple of seconds. The device will behave like you press the power button shortly to send the device into standby. Then, there is no way to wakeup the device again from its state. You can just force a reboot by pressing "power" for 10 seconds or you have to wait a couple a minutes until the device reboots itsself (not showing the "google " logo but the "android" one - which i assume is a partial reboot).

The failure in the boot preocess seems to happen very early, because if the device is shut down and you do a cold start - it will first show the "google" logo for about 20 seconds and the the screen will go blank. Normally it should then show the "android" logo but instead this it will show again the "google" logo for about 4 minutes before the "android" logo appears. Weird.

The high battery usage - which is reported by some users - is in my opinion no seperate fault. It´s just because the continous reboot loops use very much power.
[Nexus 7 Android Development] AndDiSa:
[MENTION=8559165]OlliWi[/MENTION] sorry, the facebook related messages I saw in the logs provided by [MENTION=5125613]brewer75[/MENTION] but the overall situation is similar: a process blocking the ui and then the watchdog killing the process.
[Nexus 7 Android Development] adstraylight:
Not sure if this will help, but something that helped with the system ui crashes on the UA ROM was to set the CPU Quiet governor to 'runnable' instead of 'balanced' (you can use Kernel Auditor to do this). Also using a screen off task killer helps as for some reason having the maximum amount of free RAM seems to mitigate the issue.

I don't think this is a ROM specific problem, but that it is something in the AOSP code, or perhaps a compatibility issue with our hardware, as suggested by Clamor on the UA thread.

I'm back trying this ROM out btw, as I read good things about it, and I have to say I'm truly impressed, cheers AnDiSa!:svetius:
[Nexus 7 Android Development] DragonTome:
While looking at some of the traffic on my network, I notice with this ROM that 0.de.pool.ntp.org is being used. I live in the U.S. and wonder if there is config that I can alter to use a different NTP server pool.
[Nexus 7 Android Development] brewer75:
***It's been about 5 hours since I flashed the 20180409 build again and everything is still running smoothly with no unexpected reboots.***
[Nexus 7 Android Development] SGH-i200:
Summary: Don't install the Facebook app(s)! Try a wrapper app for the mobile Facebook website instead: https://labs.xda-developers.com/store/app/me.zeerooo.materialfb
[Nexus 7 Android Development] brewer75:
It seems like Facebook may have been the problem, but the clean start without restoration of apps from the Google cloud may have helped in my situation too.
[Nexus 7 Android Development] psiphi:
Facebook Lite is a good choice?
[Nexus 7 Android Development] wutzin:
fyi, for all the tilapia users, I posted a notice in the tilapia forum. Andy, is there no way to have the DevDB project listed in both the grouper AND the tilapia forums???

https://xdaforums.com/nexus-7/3g-development/rom-android-7-x-aosp-t3782571

---------- Post added at 03:50 AM ---------- Previous post was at 03:28 AM ----------

Error in the update installation instructions in post #1:

At least on Tilapia, installing the recommended Gapps package (nano) fails with error "insufficient storage space available in System partition" (using Tilapia 2018-04-09 build and OpenGapps Nano 2018-04-26).

I did successfully flash the pico package though.

-> So I suggest to edit the install instructions to recommend the pico package instead
[Nexus 7 Android Development] AndDiSa:
Thank you for posting the ROM in the Tilapia section, too.

Regarding your comment to Gapps: the primary suggestion was to use Beans-Gapps (which on Grouper works well), but Open-Gapps pico was always suggested as nano is too big for Grouper/Tilapia.
[Nexus 7 Android Development] wutzin:
I initially installed your ROM in February and couldn't get Beans-Gapps to work correctly on my Tilapia (can't remember exactly what the problem was - I think I kept error messages about stopped services or something). That's why I re-flashed the ROM again and tried OpenGapps instead - and that worked fine for me (as long as I used pico).

Thanks for the wonderful rom! Grüße nach Heidelberg ;)
[Nexus 7 Android Development] OlliWi:
I´m back on the january ROM which works fine for me.

I haven´t tried a clean installation with the february/april ROMs but that never has been neccessary before.

I do the update installation since september ´17 without problems. Only wiped dalvik/cache but not the data partition.

What i noticed too is that some apps (mainly google apps not included in the Gapps package like youtube, maps, play games) need to be reinstalled after the update installation as they may have stored data in the system partition.
[Nexus 7 Android Development] AndDiSa:
[MENTION=8559165]OlliWi[/MENTION] Did you change the gapps packet? If you before used e.g. Beans and now you are using OpenGapps this may cause issues, too.
[Nexus 7 Android Development] OlliWi:
I´m still using the Beans gapps package. Have never tried installing the OpenGapps.
[Nexus 7 Android Development] AndDiSa:
Then you are doing something wrong because if you didn't install those apps via Gapps e.g. you've downloaded them from the store you do not need to reinstall them as they are not being touched when updating.
[Nexus 7 Android Development] OlliWi:
What can I do wrong here?

I flash the ROM - reboot the device - flash the Gapps - reboot the device - but then i have to uninstall and install some apps I downloaded from the appstore.

I guess these apps are touched when updating the ROM /system partition.
[Nexus 7 Android Development] AndDiSa:
On update you must not reboot before flashing Gapps! You need to reboot into recovery directly without booting the ROM.

If you install apps from the app store they cannot be installed on /system as /system is mounted read only. You can flash those apps only by recovery ... but this is something different as updating the ROM is erasing the /system partition. That's the reason why you need to re-flash gapps after an update.
[Nexus 7 Android Development] OlliWi:
Ok, one thing i did not mention yet ist, that I use NRT to flash the ROM and gapps. I have no custom recovery permanently installed on my device.

Then I have to flash the ROM and Gapps in a single operation with NRT, right? See attached picture.
[Nexus 7 Android Development] OlliWi:
Ok, one thing i did not mention yet ist, that I use NRT to flash the ROM and gapps. I have no custom recovery permanently installed on my device.

Then I have to flash the ROM and Gapps in a single operation with NRT, right?
[Nexus 7 Android Development] adstraylight:
I'm sure this method seems the easiest for you, but to me it introduces unnecessary variables, and so opportunities for errors. Why not install TWRP and do everything directly on the device? This way you have more flexibility in terms of rebooting to recovery between flashing packages, and making sure the /system partition is unmounted before you start. I have the facility, but can hardly remember the last time I needed to attach my tablet to the PC.

I'm not meaning to be critical, but do feel that sometimes people can overcomplicate simple things.
[Nexus 7 Android Development] OlliWi:
You may be absolutely right, but the Nexus 7 is my first android device I felt the need for a custom ROM because the stock 5.1.1 ist just crap.

So when I looked for a custom ROM I found that NRT tool and it was easy to use and always worked as expected. Therefore I never tried nor even looked for other possibilties to upgrade my ROM.

You know, never change a running system - or in this case - upgrade procedure. ;)
[Nexus 7 Android Development] :
That's true in life generally! ;)

But, yes, KISS.... I've loaded and played with so many different ROMs that the process is, for me, almost second nature now. I always clean flash these days, even on an upgrade, because it's just as simple and ensures/reduces issues. I use TWRP to flash the ROM, root and pico gapps (to give me a minimal app base) and then Titanium backup to restore the apps I use. The whole process takes very little time.... (touch wood!)
[Nexus 7 Android Development] adstraylight:
Ah, give it time, someday the temptation to play with things to try to improve them will overcome you....?
[Nexus 7 Android Development] OlliWi:
Things are always easy if you know how to do them. ;)

First step is already done, I flashed TWRP on my tilapia (using the playstore TWRP app). At least the app said it was successful - I did not yet boot into recovery afterwards.

/edit: booting into recovery (TWRP) successful :)
[Nexus 7 Android Development] adstraylight:
Here's a thing (cue AndDiSa to bang his head on the desk in despair...?), I've been pondering as to why on this and UA, sometimes system ui doesn't reflect the system's current state, such as charging and which AP it's connected to.

It's always seemed to me that it somehow misses the message until it's repeated, which led me to wonder if doze was the problem, as in there was a component that was not active when it needed to be. This would also explain the occasional slow waking of the device.

To cut a long story short, I think that by taking the Intent Filter Verification Service and System ui out of battery optimisation, things get better, but I haven't tested the theory for long enough to be sure.

Anyone else?
[Nexus 7 Android Development] black_bottom:
I get massive wakelocks with the latest version

Kernel wake lock with "PowerManagerService.WakeLocks"

Partial wakelocks with *alarm*

For the moment I don't know what to do,, there is nothing special running.