yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] AndDiSa:
[MENTION=9196199]Vincenzo1994[/MENTION] what is the issue you would like to report? In the logs I do not see any strange behavior. Latest request was:

...
06-05 09:41:42.780 524 2569 I ShutdownThread: Rebooting, reason: userrequested
...

If your device is not re-booting / switching off completely, press the power button for about 20sec then it should restart unless the battery is empty ...
[Nexus 7 Android Development] AndDiSa:
[MENTION=6255472]N4b0[/MENTION] I am wondering how you can use your device because the log is full of Fatal-crashlog messages ... that's most likely also the reason why you have such a bad battery live time. Unfortunately I was not able to identify the reason for those crashes, but I saw one interesting thing: your are using device encryption don't you?
[Nexus 7 Android Development] Vincenzo1994:
My device continue to reboot automatic and the reboot is too slow, the general performance and usage too with your last build and fresh install without any app installed and i don't know what can i do...
[Nexus 7 Android Development] AndDiSa:
...
06-05 09:34:34.259 524 579 W PackageManager: Not granting permission android.permission.GET_ACCOUNTS to package com.instagram.android because it was previously installed without
...
06-05 09:34:34.260 524 579 W PackageManager: Not granting permission android.permission.READ_PHONE_STATE to package com.tohsoft.weather.radar.widget.live.pro because it was previously installed without
...
06-05 09:35:00.244 1913 1913 E b : Skipping ANR Detector for process: com.instagram.android:mqtt
...
06-05 09:35:00.354 1941 1941 E b : Skipping ANR Detector for process: com.instagram.android:videoplayer
...

It's not a clean system and I saw also some messages about encryption. Enabling encryption on the Nexus 7 is not a very good idea, it's slowing down everything.

If I were you I would format everything and set up everything freshly. Just my 2 cents.
[Nexus 7 Android Development] Vincenzo1994:
I have installed only instagram but the system is already formatted (wipe all + format data) and install your build :(
[Nexus 7 Android Development] N4b0:
Well I don't know my Nexus seems to be a Zombie x-D,

I don't have any encryption enabled and never had as far as I remember.

3G also failed since yesterday and a reboot didn't solve that.

What was your partition suggestion? All ext4 and data F2FS?

bg N4b0
[Nexus 7 Android Development] AndDiSa:
[MENTION=6255472]N4b0[/MENTION] after some tests with f2fs I switched back to ext4 again, but this is a personal decision. Others reported a slightly better performance with f2fs ...
[Nexus 7 Android Development] Vincenzo1994:
I performed a clean installation with your last build (20180512)

1. Format Data

2. Advance Wipe -> dalvik, system and cache

3. Copy ROM+GAPPS zips

4. Install ROM.zip

5. Install Gapps.zip

6. Reboot system
[Nexus 7 Android Development] N4b0:
Well after Full wipe and changing to F2FS the battery problematic seems to be solved. Nontheless i made a new logcat and theare are also a lot of errors if i read this correctly.
[Nexus 7 Android Development] AndDiSa:
Yes, you are right, there were still some issues, but I suppose the device now after having finished the boot and having compiled the base library should work quite well.

I'll try to analyze the root cause of the issue, but it will be not quite easy, I suppose.
[Nexus 7 Android Development] FLONE:
How to do that? Do you have a tutorial? Thank you in advance
[Nexus 7 Android Development] Sam Nakamura:
Please check the forums or your favorite sear engines, there're several results to be found, this question has no relation to this ROM thread other than compatibility and is rather "off topic" here...

Hint:

Even though the screenshots are from an older version of TWRP the guide itself is still valid, TWRP still offers the same functionality

https://xdaforums.com/nexus-4/help/guide-detailed-f2fs-manual-format-guide-t3264185/page1

And another remark, when changing to f2fs you need to make sure that every kernel / ROM you flash in future supports it, flashing non f2fs compatible software on your f2fs formated device leads to serious problems as partitions won't mount properly, be prepared to lose all your data, I find myself little to no difference with f2fs over ext4 but maybe you do, so feel free to give it a try!
[Nexus 7 Android Development] lkjsoiuew:
I just installed aosp_tilapia-7.1.2-ota-eng-20180512.ds.zip over the 20170811 version via twrp-3.2.1-0 and now it hangs on the "Google" screen

.... after several minutes(!) and randomly pressing the power button, it is starting ... is that normal?
[Nexus 7 Android Development] OlliWi:
This is a known issue with the april and may builds. I had that too.

The last build which runs without any major problems is - in my case - the January build.

---------- Post added at 04:47 PM ---------- Previous post was at 04:37 PM ----------

Performance can be tweaked a little bit by changing the read-ahead value. Standard is 128 kB which gives a uncached read-performance of about 23 MB/s. Setting to 512 kB increases the value to ~31 MB/s. (Measured with hdparm -tT /dev/block/mmcblk0p5).

There are some recommendations for tuning the I/O scheduler here:

https://androidmodguide.blogspot.com/p/io-schedulers.html
[Nexus 7 Android Development] AndDiSa:
New version with June security patches uploaded

I've just uploaded the new version of the ROM for Grouper and Tilapia with the latest security patches applied to it. Links for downloading are avilable on the OP.

Unfortunately I was not able to figure out the root cause of the boot issues reported by some users on Tilapia. Because of that I've built a special version for Tilapia with the latest AOSP-patches, but with the kernel / governor / power management settings based on the version released in January. If you would like to test this version, you can install aosp_tilapia-7.1.2-ota-eng-20180608-ok.ds.zip with the old (January) kernel. I didn't link this version in the OP yet, as I would like to get your feedback and comments first.

... and as always: take a backup of your device and flash on your own risk!
[Nexus 7 Android Development] OlliWi:
I have a general question about the init.rc files.

How or when are these created?

I found some entries that do not work at all, for example this (marked in red)

# some additional performance tweaks (to be tested)

setprop dalvik.vm.heapgrowthlimit 128m

setprop dalvik.vm.heapsize 174m

write /sys/module/lowmemorykiller/parameters/adj "0,1,2,4,9,12"

write /sys/module/lowmemorykiller/parameters/minfree "8192,10240,12288,14336,16384,20480"

write /sys/module/lowmemorykiller/parameters/cost 48

These OOM levels (0,1,2,4,9,12) do not exist on the tilapia device, they are not created by this write command

Run "dumpsys activity oom" and you see OOM levels -900, -800, -700, 0, 100, 200, ...up to.... 900, 906

Whatever is written to the minfree file is ignored too.

Also kernel tweak utilities like kernel adiutor - which propably does nothing else than write to the minfree file - have no effect on the lowmemorykiller.
[Nexus 7 Android Development] lkjsoiuew:
Ok, but where can I get the January build?

... I just saw the oldkernel zip above, will try it ...
[Nexus 7 Android Development] OlliWi:
Go to the first posting in this thread -> Downloads -> click to show content. There you find all the builds.
[Nexus 7 Android Development] lkjsoiuew:
Yes it seems to solve the google screen problem.

Btw. is there a way to get completely rid of the Google search bar which comes back on every update?

... and I have to reinstall gapps because the play store is gone? ...

... and now my play store account is gone ...
[Nexus 7 Android Development] OlliWi:
You have to flash gapps after flashing a new ROM. The procedure is described in the first psoting.
[Nexus 7 Android Development] lkjsoiuew:
Why? I never have to do this with other ROMs

---------- Post added at 12:11 PM ---------- Previous post was at 12:09 PM ----------

I reinstalled gapps, logged into play store but the account is not saved. Play Store crashes just after I agree to the terms of service
[Nexus 7 Android Development] OlliWi:
Both, ROM and gapps use the /system partition. Flashing the ROM formats that partition, that´s why Gapps are gone after flashing the ROM.

It only depends on the update procedure that is used for flashing the ROM.

Other ROMS may not format /system but only copy files to the existing partition.
[Nexus 7 Android Development] dark0shark:
What a pleasure, thx a lot [MENTION=2188693]AndDiSa[/MENTION]!
[Nexus 7 Android Development] Charles IV:
I noticed a dt2w commit in your device tree, does your latest build have it and did it work?

The reason I ask is I cherry picked it and build lineage os, using your kernel, and while the switch is there in settings, it doesn't work.
[Nexus 7 Android Development] AndDiSa:
[MENTION=7211583]Charles IV[/MENTION] yes, DTW2 is working, but you need to enable it manually. I don't know why, but configuring it in the initialization phase doesn't work. Try to do a

echo 1 > /sys/android_touch/doubletap_wake

in a root shell and after a few moments it should be initialized and useable. But really speaking during my tests it was e.g. not working well when the device was dozing.
[Nexus 7 Android Development] OlliWi:
is it possible to replace the kernel of one build by those of another build?

I can´t use the february build because of the WIFI issue. I want to find out whether it´s a kernel or an Android issue.

Long booting time on tilapia with the newest standard build and also the WIFI issue (android rebooting loops). With WIFI disabled it´s not doing rebooting loops.
[Nexus 7 Android Development] AndDiSa:
[MENTION=8559165]OlliWi[/MENTION] also with this version ? Other people reported already that the long boot time is fixed with this version.

Btw. if you messed up with booting the device after an update without having gapps installed, there is a big chance, that if you install gapps later you will get permission issues which lead to force closes. In this case it's better to restore a backup and re-do the update.
[Nexus 7 Android Development] OlliWi:
Have not yet tried this version.

Yes, I noticed that. Is the kernel of this version indentical to the January build? If so, i will just replace the kernel.

In do not boot without Gapps installed. Boot recoevry -> flash ROM -> boot recovery -> flash Gapps is what I do. Then boot the system and then boot recovery and install Magisk.
[Nexus 7 Android Development] AndDiSa:
[MENTION=8559165]OlliWi[/MENTION] the vesion linked is the version having the june patches for the AOSP-part, but kernel and power management settings from January, so no need to extract another kernel and apply it manually.
[Nexus 7 Android Development] Charles IV:
Yup, this made it work, but it still works when I disable it in settings, so something's not connected, but otherwise, it's great, but it would be nice to be and to disable it as battery life on these devices isn't great in the first place.
[Nexus 7 Android Development] OlliWi:
[MENTION=2188693]AndDiSa[/MENTION]

I will try the alternative build later. Currently still investigating the WIFI issue.

If disconnecting from my WLAN, i can´t reconnect (WIFI symbol marked with 'x' saying connected but no internet) but the strange thing is, that WLAN is working while Android still attempts to re-connect. I found out that disabling WIFI completely does not discard the IP address of wlan0 interface.

logcat is attached
[Nexus 7 Android Development] OlliWi:
The january kernel works. I only flashed the boot.img -> short boot time, no WIFI isssue.
[Nexus 7 Android Development] Sam Nakamura:
Terminal says path not found, checking it via mixplorer but no such path exists?

I'm I doing something wrong or is it meant for some specific build, im running on May's build...
[Nexus 7 Android Development] AndDiSa:
It's only on the June build ... and even not on the experimental Tilapia build.
[Nexus 7 Android Development] Sam Nakamura:
Alright, I missed there's a June build (internal updater says I'm up-to-date), thanks for clarification!

[MENTION=2188693]AndDiSa[/MENTION] just for feedback, it's "doubletap" not "doubletab"... :)

And it works! Fantastic job :highfive:
[Nexus 7 Android Development] majorfigjam:
Thanks AndDiSa, that worked. Dirty flashed the latest image on an encrypted Tilapia over April image, together with OpenGapps Pica,and Magisk; then wipe dalvik and cache. First boot a bit slow, but then around 1:30 from power off to fully restarted.

You're a legend!
[Nexus 7 Android Development] brewer75:
20180608 Grouper Build Problem?

[MENTION=2188693]AndDiSa[/MENTION], the work you do is fantastic and I am very appreciative of your dedication and patience. I have enjoyed using this rom on my grouper for quite a while but the last build that really worked flawlessly for me was the January build. I have tried every build since January and each one causes random reboots to the Android screen and if the screen goes black it usually will not wake up when I press the power button but eventually displays the Android screen in a reboot. I have provided logs and you said there were some conflicting apps but none of those were added after January. My wifi icon shows an x on the bottom and it states that I am connected but have no internet during the random reboots. I have found that if I disable my wifi, my tablet works perfectly with no reboots and even wakes up promptly from sleep when the screen blackens, but I do not have any wifi since I have disabled it. I know you altered the kernel after the January build and that you are evaluating a reversion to the January kernel and power management for tilapia devices, is it possible to try this for grouper as well or can you provide just the revision for flashing on grouper? I can't help but think the changes after January are causing my problem because as I stated, my grouper worked great before those changes. Thanks for any consideration.
[Nexus 7 Android Development] dookie23:
I have not tried the June build yet but I did experience the same issue this week. From my experience, this issue seems to happen only on certain WiFi hotspots. I haven't had any issue at home but I ran into the same issue this week while travelling.
[Nexus 7 Android Development] tpuserhp:
The code works in the boot/initialization script. I had the same problem as yours and found out the file name should be doubletap_wake, as mentioned by another person earlier. So it could be a typo of the file name in your init script. Thanks.
[Nexus 7 Android Development] gouchouya:
DT2W work for few second from screen off

But it can't when CPU freq deep sleep

any idea ?_?
[Nexus 7 Android Development] dhananjay2015:
Kernel auditor is not able to set minimum CPU freq, it always stays at 1000 MHz which drains battery quickly, how can I change it? Thanks btw for supporting this device
[Nexus 7 Android Development] AndDiSa:
... no, in the init script it's ok, the typo is only here in the post.
[Nexus 7 Android Development] Sam Nakamura:
Can confirm that, putting the (correct) line of code into kernel adiutor's init.d tab activates dt2w automatically after reboot... and again thanks for adding one of Android's most convenient features! Nice :)
[Nexus 7 Android Development] AirOne70:
Hey AndDiSa !

What about this commit: https://github.com/danielhk/android...759c4f3#diff-6b5df4d6dd7fd500f298fb1e4abc0e7a

( https://github.com/AndDiSa/android_device_asus_grouper/blob/ads-7.1.0/power/tegra3_power.cpp#L51 )

And I saw some reports about crashes of MTP-Host if I remember correctly.

You can check this out: https://github.com/AirOne70/android...8786142f7dd9/patchs/frameworks_base.patch#L37
[Nexus 7 Android Development] OlliWi:
Exactly the same issue here with my tilapia device since the february build. See my postings above.

It would be worth a try using a different hotspot to see if that "fixes" the problem, but as my Wifi hotspot hasn´t ever changed, the source of the issue is the february kernel.
[Nexus 7 Android Development] brewer75:
I'm having problems with my grouper and my home wifi and it has not changed for several years. I use this Nexus 7 infrequently since I also have a 2013 Nexus 7 that works flawlessly running Oreo so I guess my grouper may just have to go in a drawer someplace if I can't use wifi!
[Nexus 7 Android Development] AndDiSa:
Here is another boot image for Tilapia more or less based on the february release. If anybody would like to test and report whether it's booting normally or if it already shows the long boot time. I am trying to find the commit(s) which are causing the long boot time and as the January build runs fine here is another one to check.
[Nexus 7 Android Development] AndDiSa:
Thank you very mcuh for the hint. The initialization part for DT2W is really missing in my branch, I'll add and test it. The other commit's are already included in the sources, so not need to add them again. Nevertheless thanks for reviewing and supporting me with your really appreciated hints.
[Nexus 7 Android Development] AirOne70:
You're welcome ! I'm using your device tree and kernel for building DirtyUnicorns, and it wouldn't be possible without your work.

On my side, D2TW is now working correctly with a little modification of the linked file in the previous post. :fingers-crossed:
[Nexus 7 Android Development] OlliWi:
The original february release does not have long boot times, but this strange Wifi issue.
[Nexus 7 Android Development] AndDiSa:
[MENTION=8559165]OlliWi[/MENTION] did you try to install the boot image I've linked with the current ROM from June? How does it behave? It's booting fast or do just notice the long boot time issue?
[Nexus 7 Android Development] OlliWi:
Cannot confirm this. Flashed the february kernel.

Tested on my own Wifi, first disconnect -> connect successful, second one not -> device went into "android" bootloop

Went out of reach of my Wifi to another hotspot, where my device had not been connected before.

Entered WPA-PSK key -> device connected, internet working. Could three times disconnect and successfully re-connect to that Wifi. Fourth attempt ended in the "android" bootloop.

The problem could be related to hotspots, where you have been connected in the past. New hotspots may work until you disable Wifi.

Testing right now. Stay tuned.

/result: boot time is fine (as with the old february kernel) but the "Wifi-android-reboot-issue" is also present.

logfile from first boot after flashing the kernel until device reboots "android" is attached.
[Nexus 7 Android Development] OlliWi:
These entries from the logcat may related to the Wifi issue:

I already noticed that the IP adresses are not cleared after disabling Wifi (see https://xdaforums.com/showpost.php?p=76766491&postcount=2718 )

And here is where the watchdog kicks in:

Hope this helps investigating the Wifi issue.
[Nexus 7 Android Development] AndDiSa:
[MENTION=8559165]OlliWi[/MENTION] between the January and the February build there are two commits related to WiFi. I've reverted them and this is the resulting boot image. Could you please check whether it improves the WiFi behaviour? Thank you very much for your help!
[Nexus 7 Android Development] Swanee123:
This image does appear to cure the long boot time on tilapia

Well done.! Haven't noticed any negative effects on Wifi but still testing
[Nexus 7 Android Development] OlliWi:
The new kernel did not fix the Wifi issue.

First boot -> connected but no internet -> crash - android reboot , then Wifi connected and working.

see logfile attached

Disabled Wifi but could not connect again (says connected, but no internet). Disabled and enabled Wifi again, now it´s stuck in "aquiring IP-address".
[Nexus 7 Android Development] OlliWi:
I never had that long booting time issue with the february build, only this Wifi issue.

For testing, disable Wifi and enable ist again. Try this several times.
[Nexus 7 Android Development] brewer75:
Today, I reverted back to the January grouper build and my tablet is working great. I have no problems with wifi or random reboots and everything seems to function as it should. It would be great to have the most recent android security updates and the screen swipe fix, but I'll gladly trade those to regain a functioning tablet once again.
[Nexus 7 Android Development] AndDiSa:
[MENTION=8559165]OlliWi[/MENTION] so most likely those commits are not related to that issue, but probably it's more related to

Pixel 2 XL: WIFI issues after updating to Feb security patch
[Nexus 7 Android Development] OlliWi:
Those issue may be different from ours, but i found the reason for the issue - or at least some workaround.

I checked again the logfiles, finding these:

E Nat464Xlat: Error stopping clatd: java.lang.IllegalStateException: command '48 clatd stop wlan0' failed with 'null'

I googled and found:

https://github.com/toreanderson/clatd

My guess: the issue has to do with the IPv6 to IPv4 translation.

Now i disabled iPv6 on my router and that fixed the issue. I can now disable and enable Wifi and it´s working perfect. NO reboots - NO "connected but no internet"....
[Nexus 7 Android Development] AndDiSa:
I saw that message, too, but I am still wondering why IPv6 is provocating a reboot ...

But it's fine that we've found at least a workaround.
[Nexus 7 Android Development] OlliWi:
The reboot is triggered by the watchdog because if a blocked UI.

As i mentioned in an earlier posting, the Wifi state as shown by the android status bar is not correct.

Although the Wifi state is shown as "connected, but no internet" (after enabling Wifi), the connection is working. I can ping servers and browse the internet. Until the reboot occurs...

In some very rare occasions, the status was correctly shown as "connected" and then it worked fine for more than 24 hours - until i disabled Wifi and enabled it again (tested with the february build).
[Nexus 7 Android Development] BLewis4050:
I just upgraded to the June release (grouper) yesterday, and I've just noticed today that I cannot turn on Bluetooth. Is anyone else experiencing similar?

Everything else, so far, seems to be working as expected.
[Nexus 7 Android Development] AndDiSa:
[MENTION=8559165]OlliWi[/MENTION] as the WiFi issue is identified and we have a workaround we can concentrate on the slow boot issue again :)

This boot image for tilapia contains some further commits regarding rt-mutex, etc. which might cause the long boot on Tilapia. If anybody would like to volonteer and to test this image ... ;)

Thank you all for your support, otherwise I would have already abandoned the Tilapia device.
[Nexus 7 Android Development] Swanee123:
Installed it. Good so far. The first of the three tilapia boot images cured my slow boot issues on the latest tilapia rom. This third boot image boots fine. Will test further and post if I find problems.
[Nexus 7 Android Development] OlliWi:
I agree.

Is this image based on the february build? I never had the long boot time issue with the the february build.

To sort the issues we should agree that everyone, who is posting an issue, includes his device and the build (and/or kernel) that is used.

For example, in my case:

tilapia device

Wifi issue on february build (workaround by disabling IPv6 on router) and all later builds

Slow boot issue on April build and all later builds
[Nexus 7 Android Development] Swanee123:
To give some idea of current tilapia boot times

Google screen approx 30 seconds then Android screen approx 60 seconds then usable

Setup=Latest tilapia rom most recent boot image, open Gapps, magisk

Huge improvement over 5+ minutes.!
[Nexus 7 Android Development] AndDiSa:
[MENTION=5078210]Swanee123[/MENTION] thanks for your feedback. [MENTION=8559165]OlliWi[/MENTION] the boot images I am posting currently are all based on some commits between the February release and the April release. As we found out it's related to the kernel (or the power managerment) I would like to check the kernel first. It's not a 100% proof as ther are also some changes in the power management but as the blocking is very early in the boot stage the probability that it is kernel related and not power management related is very high.