yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] bl3nd3d:
Hey, thank you for the great Project.

I tested your fresh Tilapia Image. Unfortunately it still takes around 5 min to boot. I booted the device 5 times. No improvent so far.

When I start the device the google logo flushes one time. Looks like the device reboots. Then it stays 4-5min. When finally the "android" logo appears its loading fast.

New image didnt solve the problem with the boottime for me...:(

PS: I have to apply the crush patch everytime I do a clean install of 7.x AOSP on my Tilapia device.
[Nexus 7 Android Development] AndDiSa:
[MENTION=9167097]bl3nd3d[/MENTION] thank you for your feedback. I found a hint in the logs that there was a thread waiting for about 5 Minutes befor the initialization continued and I supposed it was related to a commit introduced in December last year. Unfortunately this was not the reason ... :(

Probably there are some permission issues with Tilapia which cause the initialization of the device to hang. Strange thing is that later on everything works fine. Most likely something related to the rild ...
[Nexus 7 Android Development] bl3nd3d:
Dou you have an idea for a fix? I want to flash a rom for my young nephew to play games on the nexus 7 because stock 5.1 got unusable. :(

Your release is perfect but the boottime :( Is there a chance to get a fixed version next days or shall I take another rom for the Tilapia device? Maybe 4.4.4?
[Nexus 7 Android Development] Sam Nakamura:
If you don't care about latest android features or security patches but only focus on performance (which is maybe a reasonable trade off in your specific case) just flash some cyanogenmod 12.1 / 13 with parrot mod, this should allow enough performance and compatibility for gaming... But the question remains how much fun one will have with gaming on the OG N7, this will at least teach him patience :) lol

Or you just flash the grouper version and trade off phone functionality!
[Nexus 7 Android Development] hteles:
Hi,is it safe and reversible to flash this grouper ROM over a tilapia device? This tilpia doesn't have a SIM for at least three years now ?
[Nexus 7 Android Development] Darkniki777:
Long boot

Here is new log from tilapia.

dropbox. com/s/4v9uq8l55aja20y/2018-05-19-13-03-60.txt?dl=0

Thank you for your work) my nexus work like new
[Nexus 7 Android Development] bl3nd3d:
Did you try the release from yesterday? Did it fix the long boot time on your tilapia device?
[Nexus 7 Android Development] Darkniki777:
This log is from yesterday release, but is doesn’t fix long boot time. Log shows that it stacks on the same error
[Nexus 7 Android Development] adstraylight:
[MENTION=2188693]AndDiSa[/MENTION], since the only thing the surfaceflinger can be trying to display is the boot animation, it sounds to me like the display panel is not completely initialised when the request is made. Has the hardware startup sequence been changed by a patch? Could it be re arranged so the panel is initialised first? Maybe something in init.tilapia.rc?

Just speculation based on the error and some googling...
[Nexus 7 Android Development] Sam Nakamura:
According to several reports it is working flawlessly, you'll need to use TWRP for grouper though, however you sacrifice phone / mobile data functionality...

You can do a quick search on this thread for more information, you should find a few posts about it and it should also be reversible by fastboot flashing tilapia TWRP and ROM...
[Nexus 7 Android Development] AndDiSa:
[MENTION=2583740]adstraylight[/MENTION] Hmm, I don't think so ... strange thing is, that in the second log [MENTION=9165007]Darkniki777[/MENTION] provided I there is no longer the repeating entries about " Timed out waiting for hw vsync; faking it" but nevertheless the almost last entry before the 5 Minutes "sleep" it was again exactly that message. But probably you are right it might be something with the display initialization ...
[Nexus 7 Android Development] OlliWi:
For me it´s still unclear in which build the long booting time issue was introduced.

January works fine for me, i´m currently updating to the february build, this time not using NRT but booting TWRP recovery and following the (update) procedure of page 1.

Also i´m using Gapps pico now instaed of Beans Mini.
[Nexus 7 Android Development] Eliastik:
Reboot issue when activating Wi-Fi

I have a very annoying issue: when activating Wi-Fi, my Nexus 7 2012 (Grouper) start to become slow and a few time after it reboot directly to the Android screen. When I enable the Wi-Fi and the tablet connect to my Wi-Fi network I can see "Connected, but no Internet" and a cross on the Wi-Fi sign in the status bar. This issue started to occur in the March build (now my tablet run the May build). Before, I didn't have any issue related to reboot.

This issue also occur when booting in Safe Mode. I tried to reset my network setting and to re-setup my Wi-Fi network settings but the issue still occur.

Sometimes enabling Wi-Fi works after some reboots and I can use my tablet, but most of the time the issue occur.

I already posted about this issue in this thread, and I posted a log file of the crash: https://drive.google.com/file/d/1PJ8Nb2OXrAEHWcxGgiVnECtay6yOJKDp/view?usp=sharing

Thanks in advance for your help.
[Nexus 7 Android Development] AndDiSa:
[MENTION=8074969]Eliastik[/MENTION] I do many issues in the log, but those are not related to WiFi as far as I can see. How did you do the update? Because I saw some uid mismatch messages in the log you provided.

(Btw. your log is from 11th of April ... which version did you have installed?)
[Nexus 7 Android Development] Eliastik:
This log is a log from the April build. I have attached a log of the issue with the May build (I reproduced the issue).
[Nexus 7 Android Development] AndDiSa:
[MENTION=8074969]Eliastik[/MENTION] I doubt that the problem is related to WiFi I think it's more related to Plex. I also would like to know which Gapps you are using.
[Nexus 7 Android Development] OlliWi:
I have

exactly

the same issue with my tilapia on the february build (there is no March build) that i installed today. Everything worked perfect after installation until i rebooted it for the first time. :(

edit: no boot time issue with the february release. From google logo to UI about 80 seconds

logfile:

(but unfortunately it booted properly this time with Wifi working)
[Nexus 7 Android Development] adstraylight:
I've been having some wifi issues lately, random disconnects etc. I found that disabling fast reauthentification in /system/etc/wifi/wpa_supplicant.conf solved most of my problems.

I just changed the line:

fast_reauth=1

to:

fast_reauth=0

The other problem I was having turned out to be that my router was channel switching due to interference from a wifi extender I use, this was solved by assigning a channel, rather than leaving it set to auto

Just thought this info may be of some use to you guys☺
[Nexus 7 Android Development] OlliWi:
I will give it a try.

btw. i made a video of the reboot issue when you have a cross on the Wi-Fi sign in the status bar.

https://drive.google.com/file/d/1JtE6cbzvD6ftCtYENNRMOC4Tzut-jKUz/view?usp=sharing

First reboot is at 2:12. Note that the cross an the Wifi sign disappears just before the reboot (at 2:11).
[Nexus 7 Android Development] adstraylight:
I think you will need to reboot for the setting to take effect btw. Also, you will need a root file manager (I use Root Explorer) to edit the file as the system partition is read only, RE has a handy built in text editor too...
[Nexus 7 Android Development] Eliastik:
I use the OpenGapps Pico. I will try to uninstall Plex app.
[Nexus 7 Android Development] OlliWi:
I rebooted it 40 minutes ago and it is still in the rebooting-loop. About every 5 minutes it is rebooting.

---------- Post added at 01:02 AM ---------- Previous post was at 01:01 AM ----------

I bet this won´t help you. I have the same issues and no Plex installed.
[Nexus 7 Android Development] adstraylight:
When you say rebooting loop, do you mean like your video? In that it boots, there's no wifi connection, and then five minutes later it reboots?

Or are you saying that it never gets as far as the homescreen?
[Nexus 7 Android Development] adstraylight:
Well I hope it helps, I was just noticing that the disconnects were occurring not entirely randomly, but mostly pretty soon after waking the device. This suggested to me that something was happening during wifi dormancy. So I just went digging in the system until I found something that could be relevant.

I then googled the setting, apparently it is a way of re establishing the connection without going through the whole device/router handshake, this made me think that maybe my router didn't support it, or it caused the device to partially disconnect to save power. Either way, I guessed that the link was getting stuck in limbo.

TLDR: It was a total shot in the dark that worked out well?

I too have had wifi instability since Google decided to remove the option of using legacy DHCP with nougat, but interestingly only on the N7, my N4 seems unaffected, so perhaps it's something to do with the devices' wifi chipsets...
[Nexus 7 Android Development] adstraylight:
[MENTION=8559165]OlliWi[/MENTION], are you using encryption? If so try disabling it. I'm no expert but what I'm seeing in your log is a whole bunch of processes not being able to access data. There are also references to cryptfs...

If not then I suggest a complete clean flash, with a newly downloaded copy of the ROM, and no data restored from anything like titanium backup.
[Nexus 7 Android Development] OlliWi:
I do not use file encryption and never used titanium backup.

Meanwhile I found out that

all

(at least 4 out of 4) boot processes are successful (and the device will not reboot automatically) when WIFI is disabled OR WIFI is enabled but not connecting (because i removed my AP from the WLAN list).

A log file with WIFI enabled but not connecting is attached.

One question arose when i checked this log.

As you can see the WifiConfigManager is loading "wpa_supplicant.conf" which is located in /data/misc/wifi

There is another "wpa_supplicant.conf" (with different content) located in /system/etc/wifi (see the hint earlier in this thread)

Could that indicate some leftover from older installation(s) and cause the issues I have?

05-20 13:00:18.165 481 533 D WifiConfigManager: Loading config and enabling all networks

05-20 13:00:18.180 481 533 D WifiConfigManager: loaded 0 passpoint configs

05-20 13:00:18.183 481 533 D WifiConfigManager: --- Begin /data/misc/wifi/wpa_supplicant.conf ---

05-20 13:00:18.185 481 533 D WifiConfigManager: disable_scan_offload=1

05-20 13:00:18.185 481 533 D WifiConfigManager: update_config=1

05-20 13:00:18.185 481 533 D WifiConfigManager: device_name=aosp_tilapia

05-20 13:00:18.185 481 533 D WifiConfigManager: manufacturer=Asus

05-20 13:00:18.185 481 533 D WifiConfigManager: model_name=Nexus 7 3G

05-20 13:00:18.185 481 533 D WifiConfigManager: model_number=Nexus 7 3G

05-20 13:00:18.185 481 533 D WifiConfigManager: serial_number=0166160e2c0be80e

05-20 13:00:18.185 481 533 D WifiConfigManager: device_type=1-0050F204-1

05-20 13:00:18.185 481 533 D WifiConfigManager: config_methods=physical_display virtual_push_button

05-20 13:00:18.185 481 533 D WifiConfigManager: p2p_disabled=1

05-20 13:00:18.185 481 533 D WifiConfigManager: pmf=1

05-20 13:00:18.185 481 533 D WifiConfigManager: external_sim=1

05-20 13:00:18.185 481 533 D WifiConfigManager: wowlan_triggers=any

05-20 13:00:18.185 481 533 D WifiConfigManager: --- End /data/misc/wifi/wpa_supplicant.conf Contents ---

05-20 13:00:18.185 481 533 D WifiConfigManager: --- Begin /data/misc/wifi/wpa_supplicant.conf.tmp ---

05-20 13:00:18.186 481 533 W WifiConfigManager: Could not open /data/misc/wifi/wpa_supplicant.conf.tmp, java.io.FileNotFoundException: /data/misc/wifi/wpa_supplicant.conf.tmp (No such file or directory)

05-20 13:00:18.186 481 533 D WifiConfigManager: --- End /data/misc/wifi/wpa_supplicant.conf.tmp Contents ---

05-20 13:00:18.186 481 533 D WifiConfigManager: --- Begin /data/misc/wifi/networkHistory.txt ---

05-20 13:00:18.186 481 533 D WifiConfigManager: --- End /data/misc/wifi/networkHistory.txt Contents ---
[Nexus 7 Android Development] adstraylight:
Thanks AndDiSa, I was wondering whether to suggest just deleting the /data copy, and letting the system rebuild it, but wasn't sure if this might lead to more issues. I agree that a totally new installation is probably the most expedient way forward☺
[Nexus 7 Android Development] OlliWi:
In my opinion the package com.android.phone is part of the android ROM, its version is 7.1.2 (25).

Its name as shown under apps is "Mobilfunkdaten" (in german). I guess it´s related to the 3G functionality of tilapia.

Total new installation means booting into TWRP, wiping /system and /data and then install the zips, right?
[Nexus 7 Android Development] OlliWi:
New installation done.

Device is currently unusable as the setup wizard already fails. ("Setup wizard keeps stopping") :crying:

logfile attached

/edit: ok, forget my posting, im remembered that this problem is known. Will try the patch.

/edit2: patch worked
[Nexus 7 Android Development] Torgar:
7.1.2 Tilapia (Build 20180512)

Here are some logs.

-Logcat tilapia

-dmesg

-last_kmsg
[Nexus 7 Android Development] AndDiSa:
[MENTION=7904680]Torgar[/MENTION] thank you, but unfortunately almost unreadable ... suddenly there are some strage chinese characters. Probably you have an issue with your EMMC?
[Nexus 7 Android Development] Eliastik:
Tried uninstalling Plex. Didn't fixed the Wi-Fi issue entirely, but helped a bit. Tried also the fast_reauth fix.

Edit: Again a reboot, after connecting to Wi-Fi with "Connected, but no Internet" and a cross on the Wi-Fi sign.
[Nexus 7 Android Development] adstraylight:
Do you have other android devices that have no problem connecting, or is the N7 the only one using your router?

Next question, have you tried accessing the internet despite the what the system ui says?

Also, what happens if you take the following out of battery optimization?:

Intent filter verification Service

Android Shared Library

Android Services Library

Settings
[Nexus 7 Android Development] Torgar:
What you say is that the txt-files is not readable? That is strange. I have opened the files on multiple devices without registering any Chinese characters!

The only problem I've registered is the long (google) boot, and it is not registered in catlog. Catlog starts first at the "android" screen.
[Nexus 7 Android Development] OlliWi:
I can confirm that your logfiles are readable and there are no chinese characters.

/update: after clean install the February build runs better (only one unexpexted reboot during installation of apps) but there is still a problem with the UI or WIFI.

I disabled WIFI and when enabling it again it does not show the WIFI symbol again. Under settings it permanently states "getting IP address" ("IP-Adresse beziehen" in german).

But in fact it has gotten an IP adress (i checked with "ifconfig" from a terminal emulation) and network is working.
[Nexus 7 Android Development] AndDiSa:
[MENTION=7904680]Torgar[/MENTION] I was able to decode your logs, they were UTF-16 encoded ...

I found an very interesting log entry:

[ 10.909261] init: property_set("ro.debuggable", "1") failed
[ 10.921294] init: (Loading properties from /system/build.prop took 0.03s.)
[ 10.921459] init: (Loading properties from /vendor/build.prop took 0.00s.)
[ 10.921637] init: (Loading properties from /factory/factory.prop took 0.00s.)
[ 36.247679] BUG: soft lockup - CPU#2 stuck for 22s! [init:1]
[ 36.247815]
[ 36.247885] Pid: 1, comm: init
[ 36.247960] CPU: 2 Not tainted (3.1.10-nougat-00846-g66c074f #3)
[ 36.248107] PC is at smp_call_function_many+0x23c/0x2b8
[ 36.248185] LR is at arch_send_call_function_ipi_mask+0x18/0x1c
[ 36.248318] pc : [<c009fef8>] lr : [<c0013ae0>] psr: 20000013
[ 36.248322] sp : d7829ed8 ip : 00000000 fp : c073add0
[ 36.248518] r10: c09ddae0 r9 : 00000001 r8 : 00000000
[ 36.248590] r7 : c1a53af8 r6 : 00000003 r5 : c09e00e0 r4 : c1a53ae0
[ 36.248722] r3 : 00000001 r2 : 0000000b r1 : 000b0004 r0 : c1a53af8
[ 36.248854] Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
[ 36.248927] Control: 10c5387d Table: 96b7004a DAC: 00000015
[Nexus 7 Android Development] Torgar:
Yes, I noticed it.

soft lockup - CPU # 2 stuck for 22s
[Nexus 7 Android Development] Eliastik:
Internet works when "Connected, but no Internet" is displayed. My others Android devices (3 smartphones) doesn't have issue with Wi-Fi. Randomly on my Nexus 7, the connexion to the router is stuck with "Connected, but no Internet" in the UI and a few seconds after my N7 become slow and after a few minutes it reboot. It seems that in this case just disabling and re-enabling the Wi-Fi fix the problem (when displaying only "Connected"). It seems also better after uninstalling Plex as it use much RAM and run in background for some reason (in the logs, there are references to a local server).

Thanks for the list of apps to take out of battery optimization.
[Nexus 7 Android Development] adstraylight:
You could try using Kernel Auditor to set the CPU Quiet governor to 'runnable' instead of 'balanced', I have found that this helps to stop the lockups and reboots.
[Nexus 7 Android Development] OlliWi:
After testing the ROM releases of may and april which both show the long booting time issue and the february release which has an issue with the UI (maybe related to WIFI/network settings) that can result in unexpected reboots, i am back to the january release. It´s working without any issue.
[Nexus 7 Android Development] Darkniki777:
here is 2 logs with diffirent errors about long boot on tilapia

dropbox. com/s/xcxwgzfx4oc2o3n/2018-05-22-19-17-29.txt?dl=0

dropbox. com/s/4ofrhljmiap968r/2018-05-23-11-18-23.txt?dl=0
[Nexus 7 Android Development] Sam Nakamura:
I stumped upon a custom GApps package (android go edition), maybe someone likes to try, I however don't have information if universal or not or what's actually included, a clean flash is probably required, if anyone likes to try, I'll check next time I have a chance on my N7...

https://androidfilehost.com/?w=files&flid=270259
[Nexus 7 Android Development] AndDiSa:
[MENTION=9165007]Darkniki777[/MENTION] finally I was able to have a deeper look at your log files. In both logs you can see a time gap of about 4 minutes as I was able to see in other logs, too. Unfortunately I didn't find any hint for the reason of this behaviour ... it's stange that this happens on tilapia only, so I suppose it must have something to do with initialization of the ril / sim / ...
[Nexus 7 Android Development] AndDiSa:
[MENTION=7125933]Sam Nakamura[/MENTION] I didn't try yet, but as they are for Oreo there is a big chance that they will not install on Nougat
[Nexus 7 Android Development] Sam Nakamura:
Yeah, that's my doubt too but as all android go stuff is targeting Oreo but actually also work on lower versions there might be a chance - I however didn't even had time to check the installer script, maybe someone has an idea about it as having a flashable "android go GApps" packages would be definitely a benefit for our devices...
[Nexus 7 Android Development] outofusernames:
Removing my account. Not feeling welcome here.
[Nexus 7 Android Development] adstraylight:
With respect, this really doesn't help anyone, as you're not giving any detail, ie which device, what didn't work, maybe a log of the specific failure etc.

You'll find in general that posts like this on XDA are simply ignored. Indeed, there used to be a commonly used phrase round here: "Logcat or it didn't happen"☺

Apologies if you think I'm being rude, or acting like one of those self appointed XDA police, but I just think this forum works best when everybody helps and contributes as much as they can for mutual benefit.
[Nexus 7 Android Development] Promez:
am i wrong or the date in the changelogs is wrong? :p
[Nexus 7 Android Development] AndDiSa:
Corrected ... ;)

Grazie mille.
[Nexus 7 Android Development] Promez:
Thank you for keeping alive and updated our N7! :D
[Nexus 7 Android Development] Vincenzo1994:
Hi, thanks in andvance for your nexus 7 project =)

Yesterday i try to installed "(Build 20180512)" on my Tilapia model but the tablet has continued freeze and insane lag without any apps installed, only fresh ROM and pico GApps...and boot logo it takes a long time....i don't know what can i do with this build but April build works well instead...

What can i do? Thanks a lot for your support =)
[Nexus 7 Android Development] wiichoo:
For a long long time ago i subscribed to this thread, i never did a comment because also a long time ago i have had my Nexus broken; recently i decided to purchase the replacements, time to time i charge my Nexus and upgrade with this amazing rom, the rom that encourage me(is that the correct word? anyway...) to make that purchase because if i did not see life for this device i would never have made it, so thanks for the effort to anyone who helped to build this rom, anyone! to contributed even a little and.... i know the thread apparently dying slowly but i have hope that maybe some day, someone, take the challenge and create something more powerful and amazing, as powerful and amazing like our iconic and legendary Nexus would to be, the first Nexus tablet!

Long live the Nexus 7!

And thanks again for all
[Nexus 7 Android Development] brewer75:
Deleted
[Nexus 7 Android Development] bullet25:
Does anybody else have an issue with this ROM causing the Nexus to boot back up after doing a power off?
[Nexus 7 Android Development] Ahkah:
Yes I have.

I tested three specimen, and all show the same symptom.

The misbehaviour started with the Beanstalk variant of Android 6 and continued with AOSP Android 7.

Sometimes I need three attempts to shut off the device which is really annoying because of the extremely long boot time.
[Nexus 7 Android Development] shonkin:
-deleted until I can correct it.
[Nexus 7 Android Development] OlliWi:
First off all you need to support the developer. These means you need to create logfiles.
[Nexus 7 Android Development] shonkin:
I'm reposting this solution for those who, like me, install this rom and then find the setup wizard keeps crashing. Rather than drive yourself bonkers, just do the above. Make sure to get *all* of the command line (part of it is hidden unless you scroll right in the text box). Worked like a charm.
[Nexus 7 Android Development] Vincenzo1994:
Can you tell me how to do it? I want to help the developer in some way

I have nexus 7 3g tilapia model
[Nexus 7 Android Development] sepp.:
how to get logs

https://xdaforums.com/showpost.php?p=76459371&postcount=2570
[Nexus 7 Android Development] OlliWi:
You need the android platform tools from here:

https://developer.android.com/studio/releases/platform-tools

Just download and unzip, then enable developer options on your Nexus 7 and activate "usb debugging" there.

Connect your Nexus to your PC, open a command prompt from the folder where the adb.exe is located and type "adb logcat > logcat.txt". This will create a file named "logcat.txt" in the current folder.

To stop this process, press "ctrl-c"
[Nexus 7 Android Development] N4b0:
Hi,

subjectivly the boot times got better on the newest build on my tilapia after the second or third cold start.

But battery life semms to be a problem for me. Normally i could let this tab lie around for a couple of days but now its empty after 20h or so of idling.

Could be the battery but in Settings --> Battery --> "Andorid OS" has a high on time as if it wakes the tab on regular basis.

I made a logcat and hopefully this will help.

bg N4b0
[Nexus 7 Android Development] Vincenzo1994:
Actually, my nexus 7 3G 2012 is dead...

LOGCAT.TXT HERE I HOPE THIS HELP THE DEVELOPER :D

pastebin.com/wMw7FdBQ