yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] Nexus7_tilapia:
Hey all!

Congratulations!!!!!!!

Dear [MENTION=2188693]AndDiSa[/MENTION] your last ROM for nexus 7 tilapia is the best ROM ALL OVER THE WORLD.....

Almost more than a year I've tested all the ROM here ( I mean all XDA forums for nexus 7) and also all over the net, I can say SURELY SURELY SURELY this 18 Jun 2018 version of the ROM here is the BEST.

EVERYTHING in this ROM ( I've tested tilapia version) works very well!

THANKS A LOT [MENTION=2188693]AndDiSa[/MENTION]
[Nexus 7 Android Development] mkoyskip:
Just when I was out, they pulled me back in...

Totally NOT trying to hijack this thread after my excitement last night getting this awesome ROM to work. The very few that recognize me might know that I love pints.. and sometimes get very talkative so to speak..

And then a new update! Whew..

-> Android logo around 18 seconds

-> Home screen in like 47 seconds

I do have some questions that haven't really been answered by search:

-> f2fs

-> data/cache only? some suggest NOT system?

-> various ROMS support this differently from what I gather

-> I really only care [for this instance, tablet as GPS] for read speed/access

OK, g'night. Again thanks for this AndDiSa and all other devs & members.
[Nexus 7 Android Development] juliaiksdea:
Hi!

DT2W are not working after 20 seconds. Tilapia, 32gb.

WiFi are working okay on every your rom. But I always block ipv6 in build.prop due to the fact that I don't like it.

And could you publish sha256 instead of md5? md5 and sha1 are broken. They are completely unsafe. I think noone wants to use a rom with a trojan horse from National Security Agency. Thanks a lot for a new build!
[Nexus 7 Android Development] kaveh ahangar:
hi [MENTION=2188693]AndDiSa[/MENTION]

thanks for your rom and updates:)

please run sms on tilapia
[Nexus 7 Android Development] Nexus7_tilapia:
Yea [MENTION=8185402]andsi[/MENTION]Sa; DT2W doesn't work after few seconds.
[Nexus 7 Android Development] AndDiSa:
Hmm ... I am not sure whether you understood the intention of the md5 checksum correctly. It's *not* for securing the binary that there are no later modifications (for that you need to sign the whole package) but to find out whether the package was downloaded correctly and for that md5 is more than sufficent.

(only as an remark: it would be much easier to hack my XDA account and to change the checksum for the binary than to create a new binary having the same md5 checksum but having a trojan horse inserted)
[Nexus 7 Android Development] AndDiSa:
[MENTION=8618734]Nexus7_tilapia[/MENTION] [MENTION=8682239]juliaiksdea[/MENTION] yes, I already stated this issue in another post some days ago and it's a known behaviour. It's working as long as the processor is not in deep sleep mode. Somtimes it helps to try it again or to tap a bit more slowly, but currently it's not working always as intended.
[Nexus 7 Android Development] AndDiSa:
[MENTION=3798831]mkoyskip[/MENTION] to answer your questions:

-> f2fs is supported (even if I didn't notice much difference in respect to ext4) for data and cache

-> f2fs for /system doesn't really make sense as it is a read only partition and f2fs only advantages over ext4 on r/w partitions
[Nexus 7 Android Development] 239:
SHA-256

F30C07781F6FD7597634DE92E13F9942E99165DFF85766CFDE3A453388C71080

SHA3-512 (for extra safety)

0041192271674264F153EEDB81E8031CDF466FD5D6761C3DB856FE603E3B60B54057744AF71B99E20016D342EC50BB19C8D87DEFC0918C59F2222F82DBA04D59

Superficial knowledge is also completely unsafe! How do we know that AndDiSa is NOT working for the NSA? :confused:
[Nexus 7 Android Development] 239:
First log was created with the newest build after enabling Wi-Fi. It doesn't crash immediately or every time, often it takes several minutes while it tries to connect and little x on Wi-Fi icon indicates no internet access. I hope the log contains some useful bits before the soft reboot.

Second log just documents Wi-Fi failing to turn on again after turning it off before it reboots. Device needs to be restarted to get it working again.
[Nexus 7 Android Development] juliaiksdea:
Thanks, but I have a Tilapia device and I am using a tilapia rom. So sha256 is 4c55476f9985f01ba4ca39a98d7f02948ce6ae41b31df7f8b8a5a6a0c8cf521d

---------- Post added at 01:20 PM ---------- Previous post was at 01:07 PM ----------

Yeah, I almost always have the same icon and Connected, no Internet. But I have no soft reboots, any crashes or so on. And Internet really is working. I don't use any gapps if it means anything.
[Nexus 7 Android Development] ptptaylor:
I'm not sure if anyone else is experiencing it, but I get high battery use [5-10% an hour] with the screen off after a clean install of the June update. I'm not sure it is related but it can take several seconds for the screen to turn on too.

I've tried a clean install twice with the sane result both times.

I'm now trying the February update to see if it behaves similarly and will report back. I have a Grouper.
[Nexus 7 Android Development] hteles:
Tilapia user here!

Did you wiped /system /data before install?

Also, BBS does report what is taking all the juice?

Sometimes it is required to format /data and internal storage too.

Regards
[Nexus 7 Android Development] chris@xda:
Thanks soo much for the latest tilapia built
[Nexus 7 Android Development] AndDiSa:
[MENTION=4098393]ptptaylor[/MENTION] ... probably the system ist still optimizing all the applications?! Did you have a look at the log? What processes are running? From where did you get the 5-10%/hour?
[Nexus 7 Android Development] dookie23:
What is the build.prop entry you are using to block ipv6? Would you mind sharing?
[Nexus 7 Android Development] mkoyskip:
Yes I've read elsewhere that system shouldn't be changed to f2fs. Really only looking for extra read speed as my GPS maps are on my device. I've been using this [Nexus 2012 3G] and a Galaxy Tab 2 7" and have experienced much lag times for both GPS software that I currently use [Sygic & TomTom]. My older TomTom USA + Canada used to work just AOK until they upgraded and began to "force" POI's, searching entire maps, etc. Previously when entering an address it would use a simple database search based on perhaps street names or such. Now when entering any search it looks for roads/streets/states/gas stations/POI's/nearby/etc - you get the drift... And no way to turn off certain features. Anyway I'm getting off topic - only looking for read speed and this is looking well so far.

Of course this was before installing your ROM so very excited to try it out during work tomorrow . I'm already happy with the notebook speed, and perhaps after tomorrow I won't care about changing to f2fs. However at the same time I plan to try both (time permitting) just for comparison & research. I did notice that my battery was down to like 26% after sitting overnight (may have been like 17-18 hours). This isn't necessarily a concern for me as it will be powered most of the time I'm using it. Previously I could let it sit for like a week before charging, but wasn't using it regularly [an older 4.4.4 build I believe, also had many mods + xposed/greenify/etc]

Also haven't yet checked out the 'battery saver' option, was thinking about installing dsbatterysaver as it's worked well in the past. Either way, my PINTS have wasted enough of your time....

Thanks again for this & what you do! Later.
[Nexus 7 Android Development] juliaiksdea:
In build.prop I used to write this entry after flashing a new build:

net.ipv6.conf.all.disable_ipv6=1

Or someone can block it with magisk:

resetprop -n net.ipv6.conf.all.disable_ipv6 1

Nowadays, I actually block it with magisk.
[Nexus 7 Android Development] OlliWi:
logfile for AndDiSa
[Nexus 7 Android Development] olegarik:
Hi, guys. Just got Nexus 7 3g and found this discussion. I'd like to install this rom to my tablet, intalled twrp, as described in the first topic, but how may I flash the ROM? spent whole night, and still without solution. Please can anybody push me to the right direction, and sorry for offtop.:confused:
[Nexus 7 Android Development] 239:
Just follow the instructions in the first post step by step.

Here are the details for flashing the ROM (but they are almost the same for all ROMs):

Install 7.1.2 Tilapia OTA-Package (Build 20180618) (md5: 873243650fe4a93a97b85486abf84cfc)

Download aosp_tilapia-7.1.2-ota-eng-20180618.ds.zip and copy it to your device

In TWRP select

Install

and choose the zip you copied

Wait until TWRP is done flashing

Return to TWRP main menu

Reboot into recovery

Reboot

Recovery

Install pico Gapps for 7.1.x (optional: needed if you want Google apps)

Downlod Open GApps (ARM, 7.1, pico) and copy it to your device (usually you download all zip files at once)

Install

open_gapps-arm-7.1-pico-2018####.zip like before

Wipe cache/dalvik-cache (doesn't hurt)

Reboot

,

System
[Nexus 7 Android Development] hteles:
Please make sure that you read the OP, YOU NEED all the files from there ( rom, links to gapps, magisk if you would like root ).

Also, I think that you are missing https://duckduckgo.com/?q=nexus+7+how-to+boot+to+TWRP

For your safety and not requiring to install ADB on your PC just copy ROM+gapps+magisk ( if you want root ) to a sdcard before wiping anything.

Regards.
[Nexus 7 Android Development] Edmontonchef:
As long as your bootloader is unlocked and twrp is installed it's easy. Make sure that the ROM and twrp matches ie Grouper/Tilapia. Download gapps config file, setup wizard fix, download gapps pico 7.1, download ROM. Reboot to recovery,(power off then hold power and volume down) wipe everything but internal storage. Flash ROM then gapps, setup wizard fix, reboot system.
[Nexus 7 Android Development] estradz21:
im having the weirdest problem my device wont wake up after or whenever i lock it or the screen turned off i tried so many roms already same problem exist i have to reboot it again to use it again normally
[Nexus 7 Android Development] olegarik:
Another problem, I know that I have tab with 3 g and sim slot, but I can't install downloaded package from tilapia, my tab detected like grouper . So I must use grouper package? May I loose 3G than?

Fault code E3004: This package is for tilapia devices, this is grouper.
[Nexus 7 Android Development] Sam Nakamura:
You need to flash tilapia TWRP to get detection right, you must have flashed grouper TWRP and yeah, if you flash the grouper build you'll "downgrade" and lose 3G connectivity...
[Nexus 7 Android Development] k ahangar:
eyval

pas sare forsat minasbam

migam az tajrobiatet az in rom bego. chanta app mizanam kheili hang mikone. masala to insta bazi vaghta...

albateh fek nakonam behtar az in rom ham chizi bashe vase nexus7.

rasti tasavor kon onaie ke mokalemeye ma ro mikhoonan che azabi mikeshan fek mikonan english miharfim:laugh:
[Nexus 7 Android Development] AndDiSa:
[MENTION=7913386]k ahangar[/MENTION] [MENTION=8618734]Nexus7_tilapia[/MENTION] please respect the forum rules, that means post in English, please. You can send private messages in a language of your choice, but public posts should be readable by everybody.
[Nexus 7 Android Development] Sam Nakamura:
Keep speaking English please, this is an international forum hence the use of language is regulated so please stick to the xda-developers rules... (at least post a English translation along with your post when using any other language) - thanks for understanding!

Edit: Oh, just saw I ninja'd you [MENTION=2188693]AndDiSa[/MENTION] - that was unintentional, sorry Boss :silly:
[Nexus 7 Android Development] Alex_Lyt:
[MENTION=2188693]AndDiSa[/MENTION] your rom is the best, but charging issue still persists. Now, after being a while on another rom (lineage based) i'm sure it is software, not hardware problem. Today was watching movie while charging and tablet charged to 3% for two hours. What i f You use lineage sources and make lineage based rom? I see it's impossible to find cause of slow charging on you rom (((
[Nexus 7 Android Development] Nexus7_tilapia:
Pardon me, you're right.:svetius:
[Nexus 7 Android Development] AndDiSa:
[MENTION=6023270]mali_[/MENTION] ... reporting an issue without a detailed description and without logcat is not said.
[Nexus 7 Android Development] Charles IV:
What ROM were you coming from. I'm pretty sure charging is a hardware problem, but software can improve it. I use LineageOS, and I get this problem, but using a fast charger (20awg and 2a adapter), it will charge fine with screen off.

Also the lineage 14 by aaopt uses anddisa's kernel, and many of his device tree commits, so any tweaks should be similar.
[Nexus 7 Android Development] olegarik:
Thank you , Android gurus for the help. Finally I've got it. Not so difficult, as I thought. First tried to flash Beans gapps (first what I found) and no luck. Than tried Wicked gapps, worked but issue with login in Play Market and overheating tablet, temp. Always more than 60°. And finally found open gapps arm 7.1 - and I have good working device! Proc temp always less than 50°. Thanx again for the help and your work.
[Nexus 7 Android Development] Alex_Lyt:
I'm using it's native charger.

On a stock rom charging was fine. Then i came to this rom and charging became as slow as charging from PC usb port, may be even slower. Here I've been persuaded, that it is a hardware problem and even changed a charging port to a new one. Nothing changed.

Then i flashed Lineage rom and charging became much more faster. At least i could use tablet and charge it simultaneously )))

Now I'm on [MENTION=2188693]AndDiSa[/MENTION] 's rom again and charging lasts like forever.

I've read everything possible about slow charging issue, but in my case it is software bug, for sure.
[Nexus 7 Android Development] Edmontonchef:
It must be software related. (slow charging). Once I flashed the 4.4.4 kitkat factory images, Charging and battery life improved noticeably.
[Nexus 7 Android Development] AndDiSa:
It may be software related but did you also think about additional features provided and additional processes running on 7.x ?
[Nexus 7 Android Development] Edmontonchef:
good point. Older hardware can struggle with new software. I appreciate your work.
[Nexus 7 Android Development] meatfest1974:
Interdasting.

Because of your suggestion to update the firmware, I updated my grouper all the way to 5.1.1 from here: https://xdaforums.com/wiki/ASUS_Nexus_7/ME370T

With this method: https://www.ngbuzz.com/index.php?topic=1764.0

I'm so used to Samsung and Odin, that the Nexus Root Toolkit feels cumbersome.

Hopefully, this irons out the kinks for me. Although, I did notice a massive slowdown after my second reboot. I reckon it's because I'm bouncing up to Nougat straight from Lollipop.

Thanks for the hard work, AnDiSa.

This ROM resurrects such a wrongfully neglected device.
[Nexus 7 Android Development] sci05:
Does gravitybox work with this ROM?
[Nexus 7 Android Development] AndDiSa:
Marshmallow is abandoned for more than a year now and I do not have any intention to change this, but you are invited to do so. The sources you can find on github.

The same is valid for additional functionality / features. The ROM is based on AOSP and will remain so, but feel free to take it as a basis for your work.

Edit: are you kidding? You want to tell me that the logfiles you provided are from a device having this rom installed?

isPrevious: true
Build: google/nakasi/grouper:5.1/LMY47D/1743759:user/release-keys
Hardware: grouper
Revision: 0
Bootloader: 4.23
Radio: unknown
Kernel: Linux version 3.4.113-g955ea3f (root@builder) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Mon Jun 11 16:05:17 UTC 2018
...
[Nexus 7 Android Development] mafarric0:
Amazing battery life

I installed the latest version in my Tilapia last weekend. Yesterday I left the tablet unplugged. This morning the battery was still 100% charged. Only dropped to 99% after 1 minute of screen on! :D

I have no complaints and unfortunately I also have no suggestions to improve the ROM. It is that good! ;)

Thank you [MENTION=2188693]AndDiSa[/MENTION].
[Nexus 7 Android Development] Nexus7_tilapia:
Here is the same.

thanks [MENTION=2188693]AndDiSa[/MENTION]
[Nexus 7 Android Development] mkoyskip:
Really enjoyed this ROM for general use (very fast) however this past week tried to use for GPS and it rebooted at least once per hour. Still thanks again for your hard work!! :D

Using TomTom/Sygic both experienced reboots within perhaps 30 minutes. Sorry cannot provide logs. Didn't think about it as I was hoping this would just work AOK. :crying:

Again, thanks much!!
[Nexus 7 Android Development] mafarric0:
Maybe it does not make sense in the scope of this ROM, but I was wondering if it is possible to add an option to auto hide the navigation buttons bar?
[Nexus 7 Android Development] Swanee123:
Don't know if it helps but I am using Here maps for navigation. Rock solid on this ROM
[Nexus 7 Android Development] psiphi:
Make sure Nexus is NOT hooked to power when booting. I seem to recall that being an issue with some roms and slow charging.
[Nexus 7 Android Development] AndDiSa:
Exactly, probably I should note somewhere: if you boot with usb / power connected charging rate is restricted to max. 500mA (which you might never see. For me max is about 260-280mA). Unplug, wait a few seconds and re-plug the power and the charging rate will increase to 1800mA at max. (depending on cable / battery quality, battery charging level, etc.)
[Nexus 7 Android Development] sergoreg:
disable auto start up apps

Thank you for this ROM

Used it for Nexus 2017 disabled by Android 5.1.1

In this ROM is there a built-in settings to disable apps from starting automatically?

If not, what is the best utility for this?

I was wondering if there is a way to adapt sources from Android Go

to keep Nexus 2012 and maybe other devices up to date with new Android versions

and security patches? I heard in Oreo there is an easier way to add patches without flashing the whole image.
[Nexus 7 Android Development] mkoyskip:
gonna leave this unit at home while charging (also while running gps) to see if this makes a difference - perhaps it's a car charger issue? not sure but will find out when i arrive home to see if it's working aok?

thanks.
[Nexus 7 Android Development] ptptaylor:
It didn't seem to settle down after several days, so presume it wasn't optimisations. I tried to change ROMS which I think fixed it, but as I wasn't a fan of the ROM I tried I reverted back to this.

After reinstalling I had the same battery issue, although installing Amplify seems to have resolved the issues which appears to be wakelock related. I had a look under BBS for what was causing it but it didn't seem very conclusive.

Very happy now that it's running normally!
[Nexus 7 Android Development] mkoyskip:
RE: my nexus rebooting while using it in my car.

Swanee123 I also have tried other maps/gps software with no better luck, don't think this is the issue. I left my device on overnight using TomTom and it was still running aok when I woke up in the morning. also the next evening I did the same using Sygic. Also Maps.Me, Scout during the next few days just in case. Definitely not an app issue as it only reboots when using the nexus in my car. When plugged into any of my alternate chargers it doesn't randomly reboot@! I just don't understand this at all! BTW not angry only confused... TOTALLY CONFUSED concerning this.. :crying: throw one of these in just in case.

Suppose I need to analyze my car chargers + also find out the exact info concerning my Ford Focus 2014's charging port info. However this shouldn't matter much as the only thing (AFAIK) should be what the chargers provide to devices and/also....

Also perhaps I missed something while reading through this thread: I generally use stuff like Amplify, Greenify, etc. Maybe I'll remove ALL of this stuff & see how it works. NOT using Xposed on this device at the moment BTW. But again only have issues while using my car chargers.

As always thanks to everybody, g'night/morning, take care.
[Nexus 7 Android Development] Swanee123:
Interesting. I have tested Here maps on multiple tilapia and groupers with this ROM and with different types of chargers. Always rock solid. I wonder if you take off some of those apps you mentioned you'll get a better result. Worth a try!
[Nexus 7 Android Development] AndDiSa:
[MENTION=3798831]mkoyskip[/MENTION] would it be possible to get a last_kmsg dump when it's rebooting? So probably one can analyse the reason of the reboot. I would say a low memory issue (either a memory leak or used memory is not freed fast enough) ...
[Nexus 7 Android Development] akashkyh:
[MENTION=2188693]AndDiSa[/MENTION] When can we expect July 2018 Security Build?

and do we see Android Go 8.1 on this amazing Nexus 7 tablet anytime soon?
[Nexus 7 Android Development] AndDiSa:
[MENTION=6581116]akashkyh[/MENTION] it will be provided when it's finished ...
[Nexus 7 Android Development] juliaiksdea:
[MENTION=2188693]AndDiSa[/MENTION], just fyi.

Tilapia folks, please, pay attention to Magisk on the new 20180618 rom. Magisk cannot mount his image sometimes after rebooting or starting the device on. Root always is okey. But if you have Systemless hosts, Scripts in Magisk folder, Modules, they won't work. Everything is fine after rebooting the device again.

I will try doing logcat. But it happens sometimes. I had two occurrences since flashing the new build. Well I really don't restart or power off on my device often.

Magisk 16.0 stable. I never had this issue on past builds of this rom and with the same Magisk.
[Nexus 7 Android Development] Sam Nakamura:
I use Magisk beta (16.4) without having seen any problems, might be worth a try as Magisk 16.0 is pretty old by now...
[Nexus 7 Android Development] noobhero:
i'm experiencing the same thing, except, even rebooting without power plugged in, i am unable to get a higher charging rate. it always drop to 200 odds.

do not remember how is it like on stock already, device has been in cold storage until a week ago when I took it out and put your rom onto it 1st thing. :(
[Nexus 7 Android Development] juliaiksdea:
It's not old. It's Latest Stable Magisk Version. I prefer stable releases, if possible. Anyway, thanks for sharing your experience.
[Nexus 7 Android Development] AndDiSa:
[MENTION=8682239]juliaiksdea[/MENTION] I am using Magisk 16.0 on a Grouper and I do not have any issues on my side. Probably other Tilapia users can report whether they notices the same on they side. Probably your /data partition needs a file system check? I noticed strange behaviours when the file system is corrupt. Not with Magisk, but settings from other applications could not be read ...

[MENTION=2434268]noobhero[/MENTION] charging the Grouper's battery was and is always not very reliable. The AICL chip which is controlling the charging rate is very sensitive on current changes and especially our batteries (which have an age of round about 6 to seven years now) have changed (capacity, internal resistence, ...). I've checked and compared almost everything related to battery and charging with "old" versions (Kitkat, Lolipop, ...) but I didn't find any difference which might cause the charging rate dropping.
[Nexus 7 Android Development] AndDiSa:
deleted
[Nexus 7 Android Development] Sam Nakamura:
"old" is relativ, of course... But there are 2 month between the releases which is significant in "magisk time", topjohnwu had rapid development going on, it now slowed down a bit as he's doing his mandatory 4 month of military service, expected to be back in the end of June, anyways in Magisk 16.4 there were massive changes done to the startup behavior (compare the changelogs here), could be that this already fixes your described problem, who knows actually but I find it worth to mention that people shouldn't be scared of the "beta batch", I see same bias against the "unofficial" batch in ROM development which is mostly non sense, sure it's everyone's own decision to make but it's always best to do a backup and test yourself - don't reject something just for it's name but rather for the experience you made...

Sorry for the OT, I'll stop now as this isn't a Magisk thread, nor is it a Q&A - just wanted to give additional information :)