yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] sepp.:
I did have a look at dmesg. I seems to me quite ok till ~ 12secs. Then there are strange blind spots. 31secs nothing then

shutdown_enable_set bq27541_device->shutdown_disable = 0

and again 23 secs later (no message) there is a block of bq27541 and smb347 related messages (related to battery and charging I think)

bq27541_get_psp status: Charging ret= 0x0181
[ 66.312131] bq27541_get_psp voltage_now= 4033000 uV
[ 66.312772] bq27541_get_capacity = 87% ret= 86
[ 66.313418] bq27541_get_psp temperature= 270 (0.1�XC)
[ 66.314675] bq27541_get_psp current = -56 mA
[ 66.451162] smb347_charger: [smb347_config_thermal_charging] temp=27
[ 66.451794] smb347_charger: [smb347_config_thermal_charging] Bypass charger e
nable

and again 3secs break

nct1008_get_temp: ret temp=42C

now 58 secs break and again the same block

[ 127.301915] bq27541_get_psp status: Charging ret= 0x0181
.....
[ 127.452120] smb347_charger: [smb347_config_thermal_charging] Bypass charger e

two more at ~188 secs (61 secs later) and ~249 secs (61 secs later).

And then suddenly at ~ 300 secs

[ 300.338809] init: Starting service 'logd-reinit'...
[ 300.363044] logd.daemon: reinit
[ 300.555278] init: Service 'logd-reinit' (pid 151) exited with status 0
[ 300.737873] init: cannot find '/system/bin/update_verifier' (No such file or
directory), disabling 'exec 2 (/system/bin/update_verifier)'
.....[ 300.742049] adb_open
[ 300.742120] adb_open(usb open)
[ 300.742181] adb_bind_config
[ 300.750747] init: Starting service 'gpsd'...
....

While looking at the screen while booting (Google logo), I noticed some flickeringand then the google logo again. ? Is there some boot-loop going on that finally somehow resolves itself? - strange

Hopefully You can make more sense of it
[Nexus 7 Android Development] AndDiSa:
[MENTION=5055387]sepp.[/MENTION] Thank you for the hint. The blocking parts I noticed, too, as if there is a process blocking everything for a while and waiting for a time out. Especially those 60sec blocks are strange ... as 5 * 60sec -> 300sec and from there it looks quite good.
[Nexus 7 Android Development] OlliWi:
No issue with the january build. Boots very fast.

With february and april builds my tilapia is stuck at the google logo for about 4-5 minutes (just like other users report it) before proceeding with the "android" animation.

---------- Post added at 06:46 PM ---------- Previous post was at 06:20 PM ----------

I noticed that too:

https://xdaforums.com/showpost.php?p=76324382&postcount=2496
[Nexus 7 Android Development] BobCat78:
Looking forward to the new build after some internal maintenance on my 7. Charging port failed spectacularly after dropping the tablet with a cable plugged in.

Is anything replacing the performance control app? Or is it all managed "in-house" now?
[Nexus 7 Android Development] AndDiSa:
New Version with May 2018 security patches is available

Only a quick post to keep you up to date:

I've uploaded the latest version with the latest security fixes from May 2018. No other changes beside the security fixes. The OP is already updated and you can download from there.

Tilapia: I suppose I've found also the reason for the slow tilapia boot (init.tilapia.rc was not in sync with init.grouper.rc, i.e. some settings were not updated and were conflicting with the new power management introduced with the February version). Please check whether it's improved now as I do not have a Tilapia device where I was able to check before.

Gapps: Annother thing I noticed while playing around with old versions / updating from old versions: The issue regarding Google services being killed / restarted again and again is most likely related to old Gapps which are no longer supported. I noticed this as I was using the old Beans Gapps version when updating to the lastest ROM. I had those issues, too. When instead I was using one of the latests Open Gapps versions everything was running fine. So I suggest you to use Open Gapps Pico from March 2018 or newer even if you were using Beans Gapps before. There should be no problem in changing the Gapps version beside you probably need to install some Gapps from the store as they are not included in the Open-Gapps-Pico.
[Nexus 7 Android Development] jolinnard:
One note: I had long boot with tilapia, but also when I clean flashed grouper version (as I don't need 3G anymore). I have to flash february grouper ROM to workaround that. I will make a backup and try new version.

Thank you for your continued support
[Nexus 7 Android Development] LeSpark:
I updated my Tilapia from the April version, but the long boot problem is still there.

(Did the update according to the instructions on page 1.)
[Nexus 7 Android Development] sealex_cz:
I have tilapia with build from 9.2.2018 and boot time is OK (around 2 minutes).

Thanks for this awesome project.

Odesláno z mého Nexus 7 3G pomocí Tapatalk
[Nexus 7 Android Development] juliaiksdea:
Agreed. My tilapia on February build for tilapia. Booting around two minutes.

And I don't have any gapps, sim card in the slot.

[MENTION=2188693]AndDiSa[/MENTION], why is the Clock app stopping when I tap on the world icon? It happens on every your build. I just want to add some world times.
[Nexus 7 Android Development] AndDiSa:
Thank you very much for the info [MENTION=8682239]juliaiksdea[/MENTION] [MENTION=5044724]sealex_cz[/MENTION]

around two minutes is the boot time i've here on my grouper, too, on a first boot even much longer as the system apps need to be compiled and optimized. As other guys are repoting that the Google screen stays for more than 5 minues probably there are different hardware versions out in the field which behave differently ... ?
[Nexus 7 Android Development] LeSpark:
The problem appeared in the latest versions (April, May) for me, not the February ones mentioned by sealex_cz and juliaiksdea.
[Nexus 7 Android Development] mafarric0:
Since the boot problems started in April I reverted to February version and it's been working very well since.

I haven't tested the May version and I will have no time in the next 2 weeks as I'm travelling.

Thank you [MENTION=2188693]AndDiSa[/MENTION] for keeping our beloved devices away from the e-waste.
[Nexus 7 Android Development] AndDiSa:
[MENTION=5407521]mafarric0[/MENTION] ... your statement is a bit contradictionary as people stating the problem started with the February build. I am a bit confused now ...
[Nexus 7 Android Development] mafarric0:
[MENTION=2188693]AndDiSa[/MENTION] Tomorrow morning I will check and post here my version, but I'm 99% confident I have the "Tilapia OTA-Package 20180209". It's been working perfectly fine.
[Nexus 7 Android Development] simonchpl:
I'm on 20180209 Tilapia and everything works great too. Boot time relative short, no reboots. On April version I had a lot of random reboots and nexus stuck on Google logo for very long time.

Wysłane z mojego SM-G950F przy użyciu Tapatalka
[Nexus 7 Android Development] AndDiSa:
[MENTION=5545834]simonchpl[/MENTION] [MENTION=5407521]mafarric0[/MENTION] so the problem started with the April version, not with the February version. Good to know, so I can concentrate on the changes whoch were introduced in February/March ...
[Nexus 7 Android Development] brewer75:
I have a grouper and I can say, without any doubt, that my random rebooting problems started with the February build and continued in the subsequent builds. I have flashed the May build and I am cautiously optimistic that it is better but I need to continue watching it for a few days.
[Nexus 7 Android Development] AndDiSa:
[MENTION=5125613]brewer75[/MENTION] sorry, but we were discussing the long boot time for Tilapia.
[Nexus 7 Android Development] brewer75:
I understand that, but this has also been somewhat of an issue on the grouper as well as the random reboots. I just wanted to let you know that the May build seems better than the last few in that regard.
[Nexus 7 Android Development] AndDiSa:
[MENTION=5125613]brewer75[/MENTION] I had another look at the logfile you've provided and the issues you have are definitively not related to the ROM itself, but more to the applications you have installed and which are running in parallel.
[Nexus 7 Android Development] brewer75:
[MENTION=2188693]AndDiSa[/MENTION], thanks for your response. I'm not sure which apps you are referring to but I had deleted Facebook and Messenger as well as disabling several other apps at startup. However, even after doing that I still had random reboots on the April build (however I didn't re-flash that build after the steps mentioned above). The May build is working great so I appreciate your continued work and even if it is not rom related, something worked to correct my problems.
[Nexus 7 Android Development] shibadoo:
I was on 20180209 on my tilapia (which works great) and tried the update to 20180512. Unfortunately I got the same long boot times where it is stuck at the Google logo for about 5 minutes. Went back to 20180209 which again works fine.
[Nexus 7 Android Development] cnterr:
Same issue here with release 20180512 after a full wipe of every partition.
[Nexus 7 Android Development] AndDiSa:
Which 'same' issue?

If you would like to log an issue please describe in detail what's not working as expected. Best would be to provide with a log ...
[Nexus 7 Android Development] cnterr:
Sorry, it was referring to the long boot speech.
[Nexus 7 Android Development] ginfreak:
great work, runs smooth haven't had any bugs yet ive used the 01/ 2018 build on tilapia based on what others said that its the most stable... thanks:fingers-crossed::good:
[Nexus 7 Android Development] FLONE:
I'm sorry if it has been discussed, yet I didn't find these discussions; there is a problem with the "cast" function? The TV accepts the connection but disconnects immediately after.

I have tested with the last 4 versions and I encountered the same problem.

N7 3G with 12/01/2018 build.

Thank you
[Nexus 7 Android Development] AndDiSa:
[MENTION=6261775]FLONE[/MENTION] I didn't notice yet. To what do you cast? Chromecast?
[Nexus 7 Android Development] ChristoSnake:
I can comfirm the same behaviour on my Tilapia...

In both cases I used a "dirty" flash (no wiping of System, Data or Internal Storage, but wiping of Dalvik & ART Cache and Cache), then flashing open_gapps-arm-7.1-pico-20180510.

Build 20180512 spent 5 minutes on booting, whereas 20180209 was normal.
[Nexus 7 Android Development] AndDiSa:
[MENTION=1680944]ChristoSnake[/MENTION] booting until you can use the device? This is a quite normal behaviour as there is going on the optimization for the system apps / libraried and for all installed apps at the first boot after installing the new ROM. Later boots should take less time ... even if there is still a validation of libraries / apps taking place.

I think there is a difference in some of the Google apps / libs which causes the re-compilation of all apps. In my opinion that's also the reason why you cannot use any longer Beans-Gapps.
[Nexus 7 Android Development] mafarric0:
[MENTION=2188693]AndDiSa[/MENTION] Just to clarify, I hope everyone is aware that the first boot after a ROM install always takes longer, due to you explanation. The problem is that every single time it boot it takes a lot of time. That already happened to me in a version from end of 2016 or early 2017.
[Nexus 7 Android Development] LeSpark:
The long boot problem still exists after the first boot and both with the April and May versions.

At least for me.
[Nexus 7 Android Development] AndDiSa:
I am never using nandroid because it's easily leading to issues, especially when the application id's are changing ...
[Nexus 7 Android Development] shaggyskunk:
Yes I agree with you - But at the time it was looking like I was stuck and I was a little pressed for time - So a Nandroid restore would have been simpler - In the end the Clean Flash worked for me but I had to Flash the Rom - Reboot and then Flash Gapps separately....no big deal :)

Sent From My SM-N910W8 ðŸ‡¨ðŸ‡¦
[Nexus 7 Android Development] n3kf:
Great work. Thank you. Greatly cut down the FCs. Even many of my Maildroid FCs. Can't say thanks enough!!! Plus it is running great.
[Nexus 7 Android Development] AndDiSa:
Sorry, but yesterday I was in a hurry and I mixed up Titanium-backup and nandroid ... :(

Rethinking your issues, I can imagine that there was the following situation: you restored a 7.0 ROM with gapps installed in /system. As in 7.0 there was more space available more gapps were installed on /system which occupied space. When applying the new ota /system is not erased (I need to investigate ...) but only overwritten and as 7.1 is much bigger then 7.0 the available space exceeded ...

Probably it's better to erase /system before applying the ota to not run into this situation.

Thanks for pointing out this issue, I suppose you are not the only one ...
[Nexus 7 Android Development] adstraylight:
I have got into the habit of wiping /system when dirty flashing, as I think it gives the least chance of errors whilst keeping /data intact.
[Nexus 7 Android Development] shaggyskunk:
Actually I was already running your previous 7.1 Rom for Grouper - And I always Wipe System and Caches on a Dirty Flash - But this was a Clean Flash - Factory Reset - Advanced in TWRP 3.0.2-0 - Manually Wipe System - Data and Caches - Flash Rom and Gapps 7.1 Pico - Flash SuperSU v2.78.. First couple of times There was no Initial Setup Screen & I was getting Play Services errors and Play Store was there but not responding - The Rom that I tried to Restore was a Nandroid of your 7.1 Rom (I suspect that there is a large amount of Photos and Music in the Nandroid which resulted in the error 255 [not enough space]).

After two attempts to Clean Flash with Full Wipes of System - Caches and Data - What ultimately worked for me was (as previously posted) Flash Rom - Boot - Reboot into TWRP 3.0.2-0 - Flash Gapps 7.1 Pico - Flash SuperSU v2.78 - and setup.

Running great on your latest Build ?

Sent From My SM-N910W8 ??
[Nexus 7 Android Development] abhifx:
seems you have not restored /data from nandroid this time which seems to be main culprit
[Nexus 7 Android Development] paasoares:
Woking like a charm in TILAPIA with DATA & CACHE in F2FS.

Great ROM !!!

This is how i did it :

- reboot to TWRP

- advance wipe - for data & cache change partition type to Ext4 and then change it back to F2FS (otherwise got an error about not being able to format it in F2FS),

- Format System in EXT4

- Install ROM

- Restart system and let the rom load completely

- reboot to twrp again

- install GAPPS

- install SUPERSU in systemless mode

- restart System

Everything is working. didn´t have a single FC yet
[Nexus 7 Android Development] shaggyskunk:
??

I think that you missed the original post from me.

First attempt at Flashing the update: Boot into TWRP 3.0.2-0 Factory Reset - Advanced in TWRP 3.0.2-0 - Manually Wipe System - Data and Caches - Flash Rom and Gapps 7.1 Pico - Flash SuperSU v2.78 - Reboot..

No Setup Screen - Play Services fc - Play Store inaccessible - Gapps were not properly installed - I didn't attempt to restore anything on the First Two Full Wipe Clean Flashes.

And as previously posted - What DID work for me on the Grouper Build was:

Factory Reset - Advanced in TWRP 3.0.2-0 - Manually Wipe System Data and Caches - Flash Rom ONLY - Wipe Caches - Boot - Reboot into Recovery - Flash Gapps 7.1 Pico - Flash SuperSU v2.78 - Wipe Caches and Reboot. No Play Services errors and Play Store working with Flashed Gapps now installed.

Sent From My SM-N910W8 ??
[Nexus 7 Android Development] abhifx:
woops, misread that. i haven't faced that issue but then i am not flashing SuperSU
[Nexus 7 Android Development] shaggyskunk:
Yeah it wasn't related to SuperSU - I'm thinking that it was a space issue - Even though there was no error when I Flashed Gapps - For some reason Gapps didn't seem to install properly for me when I Flashed both the Rom & Gapps in the same Recovery session.

Sent From My SM-N910W8 ??
[Nexus 7 Android Development] kwsam9:
I had exactly the same problem and solution is as you mentioned. Happened to both of my N7s when I flashed 20161028 version. Again when I tried to dirty flash 20161109 version and all my Google apps such as calendar, gmail, etc. all crashed. Have to reinstall every Google apps.
[Nexus 7 Android Development] mafarric0:
Excelent work AndDiSa! My Tilapia rejoices with happiness :D
[Nexus 7 Android Development] akillenb:
Okay - wiped system, dalvik/cache, installed rom, opengapps nano and supersu.

Works well, can now use CameraMX - no launcher for default camera app, and the old camera launcher in the play store hasn't been updated for newer permissions model, I think. It installed, started to launch, then "could not access camera" - Curious what other camera apps folks have used.

Default Music app still won't run for me, but Play Music and Rocket Player both appear to work fine.
[Nexus 7 Android Development] AndDiSa:
Try to delete data for music app ...
[Nexus 7 Android Development] dooderooni:
Fantastic update to an already excellent ROM.

I did a clean install using the Nexus Root Toolkit.

I flashed the ROM, GApps and SuperSU separately then wiped the Dalvik and Cache after that.

I then reinstalled my apps from the Play Store rather than a backup.

I've also installed the Pixel Launcher and the Google Assistant too.

I can also confirm that the camera works using the HD Camera app from the store.

:good:
[Nexus 7 Android Development] AndDiSa:
[MENTION=7258623]akillenb[/MENTION] you need to grant storage permission to the app. There are two ways you can do that:

- first place: app permission management

if you have granted the permission there already (or the app does not offer you the change to set the permission) you can go to the developer options and enable generally external storage access for all apps
[Nexus 7 Android Development] akillenb:
Still no luck, after clearing data, flushing cache(s) and granting storage in both app settings and dev options.

latest logcat info:

11-30 13:18:06.612 520 7915 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.music/.MusicBrowserActivity (has extras)} from uid 10044 on display 0

11-30 13:18:06.684 520 7976 I ActivityManager: Start proc 12280:com.android.music/u0a109 for activity com.android.music/.MusicBrowserActivity

11-30 13:18:06.805 12280 12280 I art : Starting a blocking GC AddRemoveAppImageSpace

11-30 13:18:06.812 12280 12280 W System : ClassLoader referenced unknown path: /system/app/Music/lib/arm

11-30 13:18:06.937 520 2114 I ActivityManager: START u0 {act=android.intent.action.PICK dat= typ=vnd.android.cursor.dir/track flg=0x4000000 cmp=com.android.music/.TrackBrowserActivity (has extras)} from uid 10109 on display 0

11-30 13:18:07.051 12280 12291 I art : Background sticky concurrent mark sweep GC freed 12898(750KB) AllocSpace objects, 2(40KB) LOS objects, 59% free, 1973KB/4MB, paused 10.574ms total 69.070ms

11-30 13:18:07.168 12280 12280 D AndroidRuntime: Shutting down VM

11-30 13:18:07.170 12280 12280 E AndroidRuntime: FATAL EXCEPTION: main

11-30 13:18:07.170 12280 12280 E AndroidRuntime: Process: com.android.music, PID: 12280

11-30 13:18:07.170 12280 12280 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.music/com.android.music.TrackBrowserActivity}: android.view.InflateException: Binary XML file line #27: Binary XML file line #27: Error inflating class com.android.music.TouchInterceptor

11-30 13:18:07.170 12280 12280 E AndroidRuntime:	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2649)

11-30 13:18:07.170 12280 12280 E AndroidRuntime:	at

....

lots more java error stuff

Not worth a lot of effort if it's working for others, ok
[Nexus 7 Android Development] AndDiSa:
[MENTION=7258623]akillenb[/MENTION] you are right, I am getting now the same exceptions. I can open the app when I clean storage, but if I change tab it's crashing. I'll investigate this issue.
[Nexus 7 Android Development] ChristoSnake:
Sadly, the 5 minute boot happens during every subsequent boot (I did about 5 of them to be sure), not only the first boot after flashing when app optimisation occurs :crying:
[Nexus 7 Android Development] shibadoo:
Same goes for me. I did not mention that explicitely in my previous post because I considered it general knowledge that the first boot after flashing a new ROM takes longer as usual. But with this new version EVERY boot takes much longer on my tilapia as before (the notorious 5 minutes).
[Nexus 7 Android Development] AndDiSa:
[MENTION=980259]shibadoo[/MENTION] [MENTION=1680944]ChristoSnake[/MENTION] [MENTION=8223593]LeSpark[/MENTION] ... without logcat I cannot analyze anything. My Grouper takes round about 5 MInutes after an udate (having round abount 80 Apps installed), consecutive boots take round about 2 Minutes. As I do not have a Tilapia device I need your help ...
[Nexus 7 Android Development] FLONE:
Tablet screen on TV. I usually do it with a Nexus 5, and I had no problems. Now after I installed a newer android version on my tablet, I tested to see if it worked.

I do not know if it worked on android 5.1. It's not important, I just want to know if there were any problems.
[Nexus 7 Android Development] nexus 7 2012 user:
with may release no sound with private tv apps like sat1, pro7, sixx

After flashing the May release on my grouper there is no sound on private tv app (sat1, sixx, pro7,...). ARD and ZDF app have no problem.

This is the only problem I have found yet.

I only wondered, because you have written that only security update has been done with May release.
[Nexus 7 Android Development] AndDiSa:
... oh, I forgot to mention that I've introduced a noise canceling function which eliminates nonsense on TV channels ... ;)
[Nexus 7 Android Development] Sam Nakamura:
God bless you! :)
[Nexus 7 Android Development] Torgar:
Long startup Tilapia

Just the same for my Tilapia!
[Nexus 7 Android Development] adstraylight:
Why are none of you with booting issues posting logs?
[Nexus 7 Android Development] Darkniki777:
how to post here log file? or give me email to send it

tilapia long boot

this is from log file, it last for 5 min

05-18 11:33:52.478 W/SurfaceFlinger(176): Timed out waiting for hw vsync; faking it
05-18 11:33:53.480 W/SurfaceFlinger(176): Timed out waiting for hw vsync; faking it
05-18 11:33:54.482 W/SurfaceFlinger(176): Timed out waiting for hw vsync; faking it
05-18 11:33:55.484 W/SurfaceFlinger(176): Timed out waiting for hw vsync; faking it
05-18 11:33:56.486 W/SurfaceFlinger(176): Timed out waiting for hw vsync; faking it
05-18 11:33:57.488 W/SurfaceFlinger(176): Timed out waiting for hw vsync; faking it

sorry fo my english :)

[edit]

here is full log

4 s h a r e d . c o m / s/fi8SxYybjfi
[Nexus 7 Android Development] AndDiSa:
[MENTION=9165007]Darkniki777[/MENTION] sorry, but I will not register for 4shared to get the log file ... :(

Nevertheless the hwsync thing might be a good hint where to look
[Nexus 7 Android Development] Darkniki777:
try this

dropbox. com/s/nczjgiba71qqjua/2018-05-18-11-38-43.txt?dl=0
[Nexus 7 Android Development] AndDiSa:
[MENTION=9165007]Darkniki777[/MENTION] thank you very much, the log file shows that there is almost a 5 minutes period where almost nothing is going on. I am not 100% sure what's the reason for this, but I got an idea what might be the reason.
[Nexus 7 Android Development] AndDiSa:
<< deleted >>
[Nexus 7 Android Development] AndDiSa:
New Tilapia Version

I just uploded a new version for Tilapia. As I do not have a Tilapia I was not able to test whether the issue with the long boot time is really fixed. Please report your findings / provide with a logcat if you find still issues.

Android AOSP - Tilapia 20170518