yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] allmightyones:
Sorry to ask, what is an FC?

Cheers

Enviado do meu Aquaris E5 FHD atravÃ©s de Tapatalk
[Nexus 7 Android Development] Ahkah:
In this context it means something like "force close", i.e. an application is terminated because of a fatal error. A better description would be "application crash", but it's less politically correct.
[Nexus 7 Android Development] allmightyones:
Oh ok, thats clear to me now.

Thank you fellow

Enviado do meu Aquaris E5 FHD através de Tapatalk
[Nexus 7 Android Development] abhifx:
fantastic... all credit to [MENTION=2188693]AndDiSa[/MENTION] that we now have grouper where 1) its fast 2) functional 3) less buggy.

cant believe but tablet is almost stable and function as a daily driver.

i cant test the latest build as of now but soon i shall fix my tab get on with the latest android OS
[Nexus 7 Android Development] 239:
Wiped system/dalvik/cache and installed 7.1.1_r4 but could not get Play Store to run since Play Services were missing, tried it with different OGApps versions without success.

What finally worked was restoring the backup and dirty flashing without system wipe, so it's probably better not to erase system before update if you don't also wipe data.

Everything looks good so far, music app doesn't crash anymore! Still getting MTP host FC when opening the built-in file explorer from Settings/Storage.

So satisfying having Nougat running smoothly on a device from 2012, while the market share for 7.x is still below 1% at the end of 2016.
[Nexus 7 Android Development] ski522:
Has the world really come down to that :confused:

Asked in a prior post but saw no response, is speech to text working?

Having no luck getting it to go, check everything setting I could think of. Download Google's Keyboard that says it's there, but no go even thought he microphone shows up on the keyboard.
[Nexus 7 Android Development] AndDiSa:
You can re-lock, but be aware that unlocking is doing a factory reset again.

In addition one warning: if the bootloader is locked your possibilities are quite limited and you cannot even be sure that locking the bootloder will fix your issue with Sky Q
[Nexus 7 Android Development] StevePritchard:
What possibilities will be limited to me if I unlock?
[Nexus 7 Android Development] AndDiSa:
If you 'lock' you'll have no longer fastboot, recovery functionality will be limited (if it even works) ...
[Nexus 7 Android Development] Johan132:
[MENTION=272153]StevePritchard[/MENTION] Maybe a silly suggestion, but could installing Magisk, and using Magisk Hide, actually help in solving your problem?

FWIW, SafetyNet Check tests green here, so the unlocked bootloader is not reported.
[Nexus 7 Android Development] StevePritchard:
I'm not sure - using Root Check, it reports that my Nexus 7 is "Not Rooted", however, the SafetyNet check is "Failed" :

Safety Net Request : fail (SafetyNetApi.AttestationResult success == false or empty payload)

Will Magisk Hide help with that?
[Nexus 7 Android Development] Johan132:
Well ... my Nexus 7 with Magisk Hide passes, while my Samsung S6 (unrooted) without Magisk fails. That's not evidence, since I didn't test the N7 without Magisk, but worth a try, IMHO.
[Nexus 7 Android Development] BaldaX42:
This rom support F2FS?
[Nexus 7 Android Development] Johan132:
[ROM][NZH54D][2018/08/05][Grouper|Tilapia][F2FS/EXT4]Android 7.x AOSP
[Nexus 7 Android Development] :
Yes, I realise that. I just prefer to do a clean install. I've sometimes had strange things happen after using the dirty flash method.

Anyways, I think I found the problem.... *I think*.

I think I inadvertantly restored supersu with the app restore (via Titanium backup) and the version restored was different to the version I flashed. I'm not sure how these things work but I reckon that might well have caused problems.

I'm now up and running without problem (touch wood) on the latest version of the ROM, after doing the clean flash, boot boot boot method that I usually used (and described above by Portgas)
[Nexus 7 Android Development] BaldaX42:
Sorry, i'm a pirla
[Nexus 7 Android Development] Johan132:
Well, if you read my message a few posts back; I tried both with this ROM, and I saw no real advantage of F2FS, so I have switched back.

But yes, it works fine with F2FS.
[Nexus 7 Android Development] AndDiSa:
I suppose the biggest problem in your previous installation method is restoring apps / settings by Titanium. You cannot guarantee that apps keep their previous id and this might cause permission issues and also force closing.
[Nexus 7 Android Development] bovirus:
[MENTION=2188693]AndDiSa[/MENTION]

Thanks for the new ROM (August 2018).

It seems that there are some problem on the hosting site (always search for mirrors but nothing happen and it's impossible to download the ROM file).

This problem is only for August 2018 ROM. For previous ROM version no problem.

Could you please load only latest ROM in other host like Meg?

Thanks.
[Nexus 7 Android Development] AndDiSa:
[MENTION=637263]bovirus[/MENTION] sorry, no Mega. If there are still issues with AndroidFileHost I'll see whether I can find an alternative.
[Nexus 7 Android Development] bovirus:
[MENTION=2188693]AndDiSa[/MENTION]

I tried 6 times with androidfilehost and now after a long time appear a list of server and I got the file. Thanks.
[Nexus 7 Android Development] 239:
I just downloaded both builds at full speed from US mirrors, EU mirrors were too slow, though.
[Nexus 7 Android Development] bovirus:
[MENTION=6076637]239[/MENTION]

The problem is not the server speed. I didn't see the list of servers (mirrors).

Only now I can download the file after see the server list.

I tried with different browser.

Was a problem of identification about mirror server (on androidfilehost).

[MENTION=2188693]AndDiSa[/MENTION]

Is there a way to enable by default in the ROM the battery status (as %) in upper right?
[Nexus 7 Android Development] StevePritchard:
I tried Magisk and hid Sky Q, but unfortunately it hasn't made any difference.
[Nexus 7 Android Development] grotesque02:
I have SOD problem with this rom, nexus 7 wifi only.

Clean install, I just block screen at startup setup and device death :(

Last rom build, pico gapps, no root.

How to fix?
[Nexus 7 Android Development] AndDiSa:
Further information available, e.g. logcat?
[Nexus 7 Android Development] section_94:
I finally got access to a pc and was able to run logcat (files below).

Like I said in previous posts, only the Januray build seems to work on my Tilapia without reboots. On the August build the tablet reboots in a matter of minutes when I run mtorrent and also randomly reboots when browsing with chrome.

My install method is always the same: Wipe EVERYTHING, install rom, reboot to TWRP (latest),install pico gapps, boot into rom, reboot to recovery and flash Magisk (latest) and back to the OS. But I also tried flashing over a previous ROM and nothing changes.

Mtorrent is pretty much the surefire way to make it crash but since it also started crashing on browsing I no longer think it's an application specific problem.

Also this is the first time I made a logcat so if I screwed sth up let me know. Both logs are up until the time of crash. Thanks in advance!

Logs:

https://www.dropbox.com/s/bi1csgclbucuchn/rreboot.txt?dl=0

https://www.dropbox.com/s/31roty56zfjiqhb/rr2.txt?dl=0
[Nexus 7 Android Development] grotesque02:
Yes I can.

How to capture a log?

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
[Nexus 7 Android Development] AndDiSa:
I do see e.g.

08-28 12:36:43.829 969 982 E SQLiteLog: (1) near "%": syntax error
08-28 12:36:43.831 969 982 E DatabaseUtils: Writing exception to parcel
08-28 12:36:43.831 969 982 E DatabaseUtils: android.database.sqlite.SQLiteException: near "%": syntax error (code 1): , while compiling: SELECT _id, title, mime_type, _data FROM files WHERE ((mime_type LIKE %audio/%) AND ((_data LIKE %com.utorrent.client%) OR (_data LIKE %Download%) OR (_data LIKE %Music%))) ORDER BY title COLLATE NOCASE ASC
08-28 12:36:43.831 969 982 E DatabaseUtils:	at android.database.sqlite.SQLiteConnection.nativePrepareStatement(Native Method)
08-28 12:36:43.831 969 982 E DatabaseUtils:	at android.database.sqlite.SQLiteConnection.acquirePreparedStatement(SQLiteConnection.java:889)
08-28 12:36:43.831 969 982 E DatabaseUtils:	at android.database.sqlite.SQLiteConnection.prepare(SQLiteConnection.java:500)
08-28 12:36:43.831 969 982 E DatabaseUtils:	at android.database.sqlite.SQLiteSession.prepare(SQLiteSession.java:588)
08-28 12:36:43.831 969 982 E DatabaseUtils:	at android.database.sqlite.SQLiteProgram.<init>(SQLiteProgram.java:58)
08-28 12:36:43.831 969 982 E DatabaseUtils:	at android.database.sqlite.SQLiteQuery.<init>(SQLiteQuery.java:37)
08-28 12:36:43.831 969 982 E DatabaseUtils:	at android.database.sqlite.SQLiteDirectCursorDriver.query(SQLiteDirectCursorDriver.java:44)
08-28 12:36:43.831 969 982 E DatabaseUtils:	at android.database.sqlite.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1318)
08-28 12:36:43.831 969 982 E DatabaseUtils:	at android.database.sqlite.SQLiteQueryBuilder.query(SQLiteQueryBuilder.java:399)
08-28 12:36:43.831 969 982 E DatabaseUtils:	at android.database.sqlite.SQLiteQueryBuilder.query(SQLiteQueryBuilder.java:333)
08-28 12:36:43.831 969 982 E DatabaseUtils:	at com.android.providers.media.MediaProvider.query(MediaProvider.java:2698)
08-28 12:36:43.831 969 982 E DatabaseUtils:	at android.content.ContentProvider.query(ContentProvider.java:1020)
08-28 12:36:43.831 969 982 E DatabaseUtils:	at android.content.ContentProvider$Transport.query(ContentProvider.java:239)
08-28 12:36:43.831 969 982 E DatabaseUtils:	at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:112)
08-28 12:36:43.831 969 982 E DatabaseUtils:	at android.os.Binder.execTransact(Binder.java:565)
08-28 12:36:43.835 530 550 I ActivityManager: Displayed com.utorrent.client/com.bittorrent.client.Main: +4s552ms

but I do not see any crash in the logs
[Nexus 7 Android Development] section_94:
The log stops when the crash/reboot occurs. Sorry if this is totally stupid but I was wondering that myself actually: How can the crash be recorded since the crash itself stops the logging process?
[Nexus 7 Android Development] AndDiSa:
Generally the reason for the crash is logged before the the log stops.
[Nexus 7 Android Development] section_94:
I tried many times also using Catlog (logcat app) within adnroid. In all logs, the highest level of log is always E - not once a crash is recorded when the reboot occurs. What can I do? :(
[Nexus 7 Android Development] AndDiSa:
You could use the search function ... Some weeks ago [MENTION=8559165]OlliWi[/MENTION] answered already the same question.
[Nexus 7 Android Development] OlliWi:
[MENTION=9127008]section_94[/MENTION]

Do you talk about a crash of the linux kernel or a crash of the android system? These are two different things.

If the kernel crashes then you will see the "google" logo during reboot, if android crashes (while the kernel stays alive) you will see the "android" logo.
[Nexus 7 Android Development] section_94:
Its a crash of the linux kernel. Its a a full restart with the google logo and everything. What is this search function Andisa mentioned?
[Nexus 7 Android Development] OlliWi:
I really don´t know, maybe using the forum´s search function?

Do you have a sim card installed? There are some log records I have never seen on my tilapia device, i do not use a sim card.

Maybe the kernel crash is related to the 3G functionality.

08-28 12:32:36.060 530 530 D WifiService: resetting networks because SIM was removed

08-28 12:32:36.060 530 530 D WifiService: resetting country code because SIM is removed

08-28 12:32:36.337 530 581 D WifiStateMachine: resetting EAP-SIM/AKA/AKA' networks since SIM was changed

Maybe you should try without a sim card to check if it´s stable then.

kernel crashes cannot be logged by logcat.
[Nexus 7 Android Development] section_94:
I am not using a sim card. I dont know why that line is there.

All I know for sure is that on that on the August build the kernel crashes when using mtorrent and Chrome which are two of my main uses of the tablet. The january build works fine. No crash when watching stuff on VLC or playing games though.
[Nexus 7 Android Development] AndDiSa:
Yes, I was referring to the forum search functionality. But even a kernel crash should be logged in the logcat unless it's a hard crash which is tearing down everything immediately ... but this is very unlikely.

The last entry I saw in the logs was an entering dozing message. I suppose the device is going into SOD (Sleep Of Death) ... and to wake it up he has to press for more then 10 sec. the power button which causes a reboot. There are some devices models out in the field who have this bug. Probably keeping WiFi switched on during suspend might help.
[Nexus 7 Android Development] AndDiSa:
[MENTION=9127008]section_94[/MENTION] are you restoring apps / settings via Titanium?
[Nexus 7 Android Development] section_94:
No I am not using Titanium. Wifi is set to always on in the settings.
[Nexus 7 Android Development] OlliWi:
Do you have a terminal emulator installed?

The you can try to log the kernel messages into a file using cat /proc/kmsg > /sdcard/download/kmsg.txt

[MENTION=2188693]AndDiSa[/MENTION]

I think the logfiles are re-created each time the kernel boots and you won´t see any past crash in the current logfile.
[Nexus 7 Android Development] AndDiSa:
I just saw in your logs that you are using Kernel-Adiutor to modify the standard settings, e.g. switching off swap / zram. This might lead to reboots, too. Please disable / remove Kernel-Adiutor and try whether this improves your situation. Switching off zram while the system is running may exactly lead to an immediate reboot.
[Nexus 7 Android Development] section_94:
I will try that tomorrow and report back.
[Nexus 7 Android Development] AndDiSa:
I thought the logs are reflecting the time period where the crash succeeded.
[Nexus 7 Android Development] section_94:
The reason I used KA was to try and find a way to stop the reboots in the first place :) they happened before I touched any settings there.

Things I modified in KA (all with no avail):

Zram to 350, read ahead to 1024, enabling KSM, turn off hotplugging. Did not touch governors, I/O schedulers or minimum free RAM.

But for the heck of it I will try to default everything again and see.
[Nexus 7 Android Development] OlliWi:
Just found out that these entries exist on my tilapia too. Maybe those came with one of the latest builds.

At least that´s not the source of your issues.

The default value is already 350MB since the august release.
[Nexus 7 Android Development] blast1987:
Hello guys! just a question

is the kernel included in this ROM wifi monitor mode enabled?
[Nexus 7 Android Development] kblade29m:
Tilapia rom

First attempt - Install Rom + opengapps (pico) + Supersu together and reboot. Booted properly but stuck at "Set up as new" - the application crashed. Cannot proceed.

Second attempt - Install Rom + Supersu and reboot. Booted up properly . Restart to TWRP and install opengapps (pico). Didn't ask me the "Set up as new" question. Got my playstore :good:.

Tested working - 3G (sim), Hotspot, WiFi, GPS, Bluetooth, Mic, Video, Music and Camera (with Camera MX app).

Adjusted CPU (min cpu) and ZRam.

Great job [MENTION=2188693]AndDiSa[/MENTION].
[Nexus 7 Android Development] section_94:
I could not run those commands from windows adb. I used the syslog app to get dmesg and ksmg but the logs are a bit of mess (hard to read). If those dont help much I will try again with a terminal emulator when I get back home.
[Nexus 7 Android Development] AndDiSa:
Thank you very much for the log files, those seem to contain a bit more information. I do need to analyze them a bit more deeply to see whether I can find a reason for your crashes.

Edit: I saw a page fault as the reason for the kernel reboot ...
[Nexus 7 Android Development] section_94:
I noticed a line by the end of the kmsg reading "Rebooting in 10 seconds..". This is probably the bad reboot right?

I then made a normal reboot, took a new kmsg and it read "Restarting system with command 'userrequested'. So this is a regular reboot.

Thanks Andisa for your help!
[Nexus 7 Android Development] OlliWi:
Could you please provide a logcat with your crash log.
[Nexus 7 Android Development] AndDiSa:
The log he provided contains a page fault which later caused a reboot. At the moment I still have no idea why the page fault caused a reboot ...
[Nexus 7 Android Development] section_94:
New logs including logcat, dmesg and kmsg. This time the crash came from mtorrent while the previous time it was from chrome. Does this make any difference in the logs?
[Nexus 7 Android Development] AndDiSa:
The same as before: kermel page fault ...
[Nexus 7 Android Development] Ahkah:
Had a reboot yesterday (grouper device). After I had watched some videos using NewPipe I switched to YouTube app and started a video when suddenly the device rebooted via Google screen. I will try to get some more information when I have the time.
[Nexus 7 Android Development] Nexus7_tilapia:
#report

Hi

same here;

[while watching online a video, but not on YouTube.]

regards

edit: A new sudden reboot accurred again [while disconnecting a VPN]

What is the best way of creating a log file of these sudden reboots to attach them here?
[Nexus 7 Android Development] OlliWi:
Creating logfiles:

https://xdaforums.com/showthread.php?t=1520508

If the kernel crashed we need the messages from last_kmsg (adb shell "cat /proc/last_kmsg" > kmsg.txt).

You may also provide the logcat output using (from a command prompt) adb logcat > logcat.txt
[Nexus 7 Android Development] Nexus7_tilapia:
Dear [MENTION=8559165]OlliWi[/MENTION]

Thanks a lot for your reply.
[Nexus 7 Android Development] Nexus7_tilapia:
Hi guys

Does anyone know why terminal emulator always shows me "Not Find ..." when i type there "cat/proc/last_kmsg >/sdcard/last_kmsg.txt".

ScreenShot is attached.

Best regards
[Nexus 7 Android Development] AndDiSa:
[MENTION=8618734]Nexus7_tilapia[/MENTION] After 'cat' you need to insert a blank.
[Nexus 7 Android Development] Nexus7_tilapia:
pardon me sir [MENTION=2188693]AndDiSa[/MENTION]

Now it shows me "permission denied!".

edit: my tilapia is rooted.
[Nexus 7 Android Development] Ahkah:
[/COLOR]

The logcat app I installed claimed root access for reading the kernel messages. I do not have root access to my device. That might be the problem.
[Nexus 7 Android Development] Gap23:
First Time Wizard crashes again and again

Hi,

I installed the aosp_tilapia-7.1.2-ota-eng-20180809.ds.zip and open_gapps-arm-7.1-pico-20180904.zip on my Nexus 7 2012 3G with twrp-3.2.3-0-tilapia.img (Format, install both zips and clear caches) but after reboot and selecting Germany and configure as new device the App crashes and will be restarted.

Any Idea?

UPDATE: Looks like I solved it! During the crash there is a small piece of time where you are able to enter the system configuration and after configure WLAN it is working! (I have no SIM in my Nexus)
[Nexus 7 Android Development] OlliWi:
Your console is not using root. First type su <Enter>. The terminal will then ask for root access. Then type the command.
[Nexus 7 Android Development] Nexus7_tilapia:
Thanks a lot, Now the terminal works well here.:)

I'll attach the log files here everytimes that random reboots occur.

Dear [MENTION=8559165]OlliWi[/MENTION], Do you find the optimal parameters of init.grouper.rc for tilapia devices?

Best regards
[Nexus 7 Android Development] section_94:
[MENTION=2188693]AndDiSa[/MENTION] Any luck in finding out anything about the page fault kernel panics? I tried decreasing the zram back to 200 thinking it might help but it didn't.
[Nexus 7 Android Development] AndDiSa:
Strange thing here is: page fault normally isn't really an issue as in that case the missing page is decompressed, swapped in, other pages probably swapped out to free memory and then the program should continue without any issues.
[Nexus 7 Android Development] Nexus7_tilapia:
#report

Hi guys

Settings:

1: My device sleeps after 30 seconds of inactivity.

2: DT2W is OFF.

Question:

when the screen becomes off after 30 seconds of inactivity, I use the power button to wake it up BUT SOMETIMES the screen stays OFF and It forces me to hold the power button for seconds to do a reset. After that i create last_kmsg file via terminal emulator.

Dear [MENTION=2188693]AndDiSa[/MENTION] & [MENTION=8559165]OlliWi[/MENTION] & ... , May I ask you to detect the errors?

BEST REGARDS

The last_kmsg file exceeds 512 KB [is 896 KB] therefore i upload it in google drive:

https://drive.google.com/file/d/1mOsukLS_nfUVBUs_DRI1MH6Lw6oTEEpZ/view?usp=drivesdk
[Nexus 7 Android Development] OlliWi:
It seems that you´re running a battery monitor app which is going crazy. The battery current is queried 3 times per second.

The driver itself does not update the battery status that often, so the same value is read up to three times. You should - if possible - configure those app or uninstall it.

My tilapia does not have those entries, it only shows the following entry (which is also present in your log) every 60 seconds

Your problem is a result of a communication failure between the touchpanel (elan ktf3k) and the i2c bus:

Source of a problem may be that the boot processor (CPU#0) is not responding, because it is stuck:

[31103.389507] tegra-i2c tegra-i2c.1: i2c transfer timed out, addr 0x0010, data 0x00

[31108.177870] BUG: soft lockup - CPU#0 stuck for 22s! [pool-2-thread-1:10673]

[31108.177933]

[31108.177990] Pid: 10673, comm: pool-2-thread-1

[31108.178097] CPU: 0 Tainted: G W (3.1.10-nougat-00977-g50db2ef #1)

[31108.178162] PC is at __do_softirq+0xb4/0x2dc

[31108.178267] LR is at __do_softirq+0x1c/0x2dc

[31108.178327] pc : [<c0070f5c>] lr : [<c0070ec4>] psr: 20000113

[31108.178330] sp : c721beb8 ip : 002ef4a8 fp : c0aa2160

[31108.178487] r10: 00000000 r9 : c721a000 r8 : c721a038

[31108.178592] r7 : 0000003f r6 : c721a000 r5 : 00000040 r4 : c0adbf00

[31108.178650] r3 : 00000000 r2 : 00000000 r1 : 00000000 r0 : 00000001

[31108.178755] Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user

[31108.178815] Control: 10c5387d Table: 80c4c04a DAC: 00000015

[/quote]
[Nexus 7 Android Development] Nexus7_tilapia:
Wow, GREAT!

Thank you very much [MENTION=8559165]OlliWi[/MENTION] .

May I ask you another question, OlliWi?

Do you find the optimal parameters of init.grouper.rc for tilapia devices ?

Best Regards
[Nexus 7 Android Development] slybunda:
how can i check to see if i am currently running your rom on my tablet? been a while since i flashed the tablet and cant remember what iv flashed it with lol
[Nexus 7 Android Development] Portgas D. Ace:
Settings -> About device. There you'll see the name of the ROM.
[Nexus 7 Android Development] slybunda:
says android 7.1.2
[Nexus 7 Android Development] paasoares:
See the screenshot

On Build Number you can see NZH54D :)
[Nexus 7 Android Development] Sam Nakamura:
Had a sudden reboot to the Google screen while watching YouTube and took some logs, hope they're of any use... If you need further information I'll gladly provide it!

https://drive.google.com/file/d/1MVKs8fdwJZpDnswZNEF4oOo5VQPpibsq/view?usp=drivesdk

Thanks for the ongoing support, you're ROM let's me still enjoy this device! Good job with this challenging task, this is actually quite spectacular :highfive:
[Nexus 7 Android Development] psiphi:
Happened to me too on my grouper, will do some logs too if it happens again
[Nexus 7 Android Development] Ahkah:
Noticed the first reboot without video playback: Instead of opening Firefox the device just rebooted. Reboots usually occur after some days of sporadic usage, so maybe there is some memory or whatever leak that grows over the time.
[Nexus 7 Android Development] AndDiSa:
In all the logs provided until yet I noticed the page swap issue which then led to the reboot of the system.

In the last log I saw a stacktrace related to syncing f2fs. I am wondering if the others who had the reboot issues are using f2fs, too, or whether they are using ext4.

Additionally it would be of great help to know whether you are using encryption on your filesystem or not.