yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] Nexus7_tilapia:
yea, just pico package gapps

---------- Post added at 06:28 PM ---------- Previous post was at 06:24 PM ----------

i did not have up untill a week ago, but since then it occured! i flashed build 05 right the day when Mr [MENTION=6754437]millosr[/MENTION] released it. :(
[Nexus 7 Android Development] Nexus7_tilapia:
Hi all

i need help :(

what happens if we accidentally remove 'boot' partition from recovery? how can i fix that?

thanks
[Nexus 7 Android Development] millosr:
Do you have some custom launcher?

Post your adb log here.
[Nexus 7 Android Development] PGTechTips:
I am Confused

I am a big supporter of yours. Have had this on my tablet for a while. I am not understanding the issue with android 7.1.2 that made you switch back to 7.1.1. Can you please explain further. Is there a possibility on you working on android Oreo for this tablet? Mostly curious not trying to come across rude.
[Nexus 7 Android Development] mausbock:
First I also was surprised about this decission. But the I took a look at the AOSP source and it seems that Google does not make any update for 7.1.2 since august but is still updating the 7.1.1 branch.

I updated to the b05 and there was a factory reset required. Before I did backups of my most important app data using Titanium and restored after the wipe. The b05 runs very well on my tilapia.

BTW, in the last months I realized a slowdown after a couple of days on every 7.1.x ROM here on XDA, but instead of rebooting every day, like other users suggest, I installed Greenify now. I added all non system apps except launcher and Gboard and until now the system does not become slower without rebooting anymore.
[Nexus 7 Android Development] Nexus7_tilapia:
Hi,

unfortunately Media Transfer Protocol does not work correctly! only it works while I'm on recovery.:crying::crying:
[Nexus 7 Android Development] mausbock:
I tested MTP on my tilapia and it works perfectly. First I opened a PDF from the tablet on my PC connected via USB and there are no issues.

Then I copied a text file from PC to the tablet an opened it successfully on the tablet.
[Nexus 7 Android Development] Nexus7_tilapia:
Hi again

I need help [PLEASE]

MPT does not work:crying:

does it need to change anything in developer options?
[Nexus 7 Android Development] noleng:
hey everyone.. will there be upcoming updates or support for this?
[Nexus 7 Android Development] MacLeod100:
Read the OP is write clear there why 7.1.2 is abandoned ( some other users explain that too a little more up on thread ) and not only on this ROM in many others too . Many dev they release so called " updates " but actually are just small fixes and secutity patches ported from 7.1.1 to 7.1.2 . Now you know :) and do some carefull reading before asking ;) About Oreo ...... just hold your horses :D maybe some dev will make it possible
[Nexus 7 Android Development] shorinjin:
Ok. I've hit a dead end. I'm going through the steps I located in another thread with instructions for installing nAOSP 6.0 (https://xdaforums.com/nexus-7/development/rom-naosprom-google-nexus-7-t3331116). I presumed the steps are the same as for 7.1. Here are the steps:

Flashing Procedure

Clean flash

1 Backup everything

2 Reboot into recovery

3 Convert data / cache to F2FS

3.1 Backup /sdcard - adb pull /sdcard/ sdcard/

3.2 Change data to F2FS - in twrp go to Wipe, advanced wipe, select Data, Repair or Change File System, Change File System, F2FS

3.3 Change cache to F2FS - same as for data

3.4 restore sdcard data - adb push sdcard /sdcard/

5 Wipe everything except sdcard

6 Unmount /system

7 Flash nAOSProm

8 Flash gapps - I recommend open gapps

9 Reboot

I went through step 3.3, changing the file system to F2FS. Once I did that, my ROM file was no longer on the Nexus, of course, and I am unable to get the Nexus to talk with my laptop. It was communicating immediately prior, so MTP was working. I can reboot into Recovery Mode (I'm using TWRP).

Any suggestions on how I proceed now?
[Nexus 7 Android Development] ffejy462:
Invest in an otg drive. Great for backups and this situation.

Reinstall driver for windows.

Update adb/fastboot on pc.

Make sure you're on the latest twrp.

F2fs just isn't worth the trouble. Imo. For all the extra work you're causing yourself, the gains are minimal.
[Nexus 7 Android Development] shorinjin:
I have an OTG cable and drive. I guess in all the excitement at the prospect of having my Nexus working again, I forgot all about it!

Thanks for the suggestion, [MENTION=5073488]ffejy462[/MENTION]. It worked! :good::cowboy:
[Nexus 7 Android Development] Vlad9ck:
Fixed MTP issue on grouper by choosing correct driver in device manager: just choose "select driver manually" and select Composite USB device instead of ABD driver, after that both MTP and ADB drivers will be installed correctly.

Also found a way to fix issue with System UI crash on home button press: it happens because of some issue in navbar config, just go to System UI tuner and made some changes to navbar (add some button), save new config then you can change settings back and home button will work correctly.

But found another annoying issue: can not install some apk using file manager, install button is disabled and this is not connected with screen filtering software, cause I tried on clean ROM after hard reset. Looks like the issue has appeared because of October security patch: it adds restriction to allow installs only for chosen apps, but on Android 7.x there is no settings item to define those apps, only Android 8.x has it. Found temporary solution: upload apk to Google Drive and install using Google Drive app.

Anyway, ROM looks great: battery life is good and performance is awesome for such hardware.
[Nexus 7 Android Development] mausbock:
Regarding the disabled install button: this also occurred on my devices. Try to tap on multi tasking button, switch to another app, tap the multi tasking again and switch back to install screen. The install button will be enabled after that.
[Nexus 7 Android Development] Vlad9ck:
Yep, multi task button also solves the issue. Thanks!
[Nexus 7 Android Development] Saad Shaikh01:
I don't understand the F2FS part, it's my first time trying to use nAOSP

Can I just clean flash it like any other ROM?

Also, which gapps do y'all suggest?
[Nexus 7 Android Development] Vlad9ck:
Yes, you can. I use opengapps.
[Nexus 7 Android Development] fidoedidoe:
I can see there haven't been any updates published for a little while (I'm not asking for eta, etc). I was simply wondering if anyone is building from source (independently of [MENTION=6754437]millosr[/MENTION] published builds) to pick up newer/latest android security patches? If not then I'm tempted to attempt (big caveat) to build from source myself (not knowing if this pickup more recent security patches), has anyone any objections to this approach and/or advice on the build process?
[Nexus 7 Android Development] neeraj02saini:
Oreo?

Ant idea guys when naosp android 8 rom will be available for nexus 7 2012
[Nexus 7 Android Development] travelbug:
[MENTION=3865771]fidoedidoe[/MENTION]

Thanks a lot for taking the ball! From my understanding 7.1.1 is supposed having all new patches included when you sync, whereas patches for 7.1.2 (see the ROM from AndDiSa) have to be cherry-picked.
[Nexus 7 Android Development] AndDiSa:
[MENTION=6104152]travelbug[/MENTION] as far as I've seen security patches for February are pushed to AOSP for 8.x only but I might be wrong
[Nexus 7 Android Development] millosr:
I'm not sure I will work on nAOSP 8 for N7.

I tried to build it for Sony Xperia S, but it has several issues like camcorder failure, cell data connection failure, occasional google apps force stops, ...

I would have to switch to 3.4 kernel for android 8 because some kernel features are required for it, so I might have some issues with kernel also.

nAOSP 7 works well for me so I don't have plans for now to build the 8.

Actually patches are published only for 8.1. It seems that google has decided not to publish source for other android versions any more.

That's why I didn't build the nAOSP since October.
[Nexus 7 Android Development] DunKzz:
Hi [MENTION=6754437]millosr[/MENTION] thank you for all the great work, my N7 Tilapia is running very good.

Do you plan to update the security patches? Well I see a lot of ROMs but not so stable and light like this one.

If not, can you provide the link of some ROM really stable like this and worth to replace?

PS: Can I lock the bootloader again after all done?
[Nexus 7 Android Development] SeanBlader:
For a while now I've had the old 1012 Nexus 7 laying around. I had gotten Cyanogenmod (11 or 12?) onto it a while ago, but I'd set it down since the gapps never connected and caused all sorts of crashes. Tonight I had something I wanted to do with it, so I brushed it off, plugged it in, and turned it on. Same effect. Good news is, ages ago when I replaced it with the 2013 model, I'd gotten ClockworkMod Recovery installed. So once I got in there, and found this thread, after trying crDroid to no avail, I was able to install the nAOSP zip file through a microUSB microSD reader, and got pico gApps installed, and boom, it was working again.

My plan was to set it up as a second system monitor screen for my new PC I'm building later this week when the parts came in, but I wanted to try getting it working in advance. Didn't take much more than an hour to get the tablet working and another to get it setup as a second screen with all the monitors I wanted on there, neat.
[Nexus 7 Android Development] Cocalarix:
Was trying to install Youtube Vanced and then just wipe dalvik/cache before rebooting. It all worked properly, but between all normal text there were some weird errors:

https://i.imgur.com/W1ZEAw0.jpg

Any idea what this could be? It didn't break anything, the ROM works wonderfully.

Also, as a random tip for anyone wanting beter performance: Xposed + Prevent Running module (set it up to stop all the apps, except the ones that need to wake up from time to time, like Gmail, Messenger, etc)
[Nexus 7 Android Development] Sam Nakamura:
It's a good idea to share the recovery log (TWRP -> advanced -> log) by uploading (i.e. G-drive) and posting the link to get it analyzed....
[Nexus 7 Android Development] Nexus7_tilapia:
Dear [MENTION=6754437]millosr[/MENTION]

we all r waiting for a new update :crying:
[Nexus 7 Android Development] mausbock:
No, I am not waiting for an update. [emoji6]

The current version is running very well and stable. In my opinion it is still the best ROM for tilapia.
[Nexus 7 Android Development] Nexus7_tilapia:
:(

we all [except u] r waiting for a new update.:laugh:
[Nexus 7 Android Development] ffejy462:
It's a 6 year old device. Be thankful that anybody has been working on it for the last three. It's poor manners asking for and asking when regarding updates.
[Nexus 7 Android Development] HeikoE:
I absolutely agree!
[Nexus 7 Android Development] Nexus7_tilapia:
what do u mean by using exclamation mark ?
[Nexus 7 Android Development] millosr:
Google hasn't published any updates for the nougat source and current version works very well for me also.

There are some updates on the lineage repos, but I don't have time/motivation to merge them to my sources.

I had some issue with the app on my work with older androids, so I installed temporarily SlimKat (kitkat, 4.4) and CM 12.1 (lolipop 5.1). I could compare the roms and the nAOSP works best.

SlimKat runs smoothly, but I don't like the interface, and CM 12.1 have performance issues, occasional freezes.

I might try to build oreo for the grouper/tilapia, but I'm not very optimistic, since it requires some kernel features form newer versions and this this rom is using 3.1.

I have tried to build nAOSP 7.1 with the 3.4 kernel and it is not very stable, so I will stick to 3.1.
[Nexus 7 Android Development] sirrobzeroone:
Question on how to use, am I on the right track?

Hi all Noobie questions as I tried to locate some instructions but couldn't find much on the thread and this will be only my second time flashing android and first using these tools so appreciate any help

~ I've unlocked the Nexus 7 okay

~ I've installed and confirmed I have TWRP running and ready to go

~ Downloaded nAOSProm-7.1.1-grouper -b05.zip (wifi only N7)

now I'm a little unclear as to next assume I should:

~ Use TWRP to backup current working stock 5.1.1 image

~ Copy zip across to N7 using fast disk similar to when copying twrp over

~ TWRP Clean Wipe?

~ TWRP install?

~ TWRP Reboot and cross fingers?

~ Done N7 hopefully running Android 7

Just want to check I've got that all straight before I stuff something up so thanks for any help and replies
[Nexus 7 Android Development] 239:
Use TWRP to backup current working stock 5.1.1 image

:good:

Copy zip across to N7 using fast disk similar to when copying twrp over

You can just copy files over USB as usual when in TWRP, don't forget to also copy md5 files over so that TWRP can check integrity

TWRP Clean Wipe?

:good: factory reset is needed since you are going to flash a different ROM

TWRP install?

:good:

TWRP Reboot and cross fingers?

I'm rebooting to recovery after flashing system, then I flash open_gapps-arm-7.1-pico-... and reboot to recovery again before rebooting to system

Done N7 hopefully running Android 7

:cool:

I'm using AOSP by AndDiSa which is updated frequently and includes latest security patches :good:
[Nexus 7 Android Development] Nexus7_tilapia:
:svetius:
[Nexus 7 Android Development] noleng:
So whats the update on the latest rom I should use.
[Nexus 7 Android Development] HeikoE:
No news in this thread for quite a while. Is there still a chance for getting updates/security patches for this nice Rom?
[Nexus 7 Android Development] frov:
Again reply to myself: I now flashed the newer ROM by Daniel_HK (Sept23 version), as I pointed out above, and now video works :good:

BTW, flashing that ROM was a fight to get Gapps to work, but in the end that ran and I could test the video apps I pointed out before in this thread. All work: kodi / nos / horizon go.

So now looking forward to nAOSP to include this video fix ;)
[Nexus 7 Android Development] harrymcqueen:
Not Working for Tilapia - Installation from TWRP stops
[Nexus 7 Android Development] millosr:
For me it is working on tilapia.

Which version of TWRP you have? Is it twrp for tilapia? Grouper twrp can be also installed on tilapia and you can only flash grouper roms then.

What are you getting in the log when you try to install it?
[Nexus 7 Android Development] harrymcqueen:
Hi. I used that twrp Version:

twrp-3.0.2-0-tilapia.img	9.3M	2016-04-05 04:44:11 EDT

Installation of ROM stops and tells that i tried to install a grouper Version.

---------- Post added at 10:38 PM ---------- Previous post was at 10:28 PM ----------

E3004: this package is for grouper devices. This is a tilapia.

But i used tilapia b01.zip
[Nexus 7 Android Development] millosr:
It's impossible.

Download zip file again and check md5sum.
[Nexus 7 Android Development] zerbey:
So far so good, running on F2FS as well. Do I need to install ParrotMod on this or should it already be tuned enough as is?
[Nexus 7 Android Development] frov:
I would say that adding parrotmod is not a bad idea. I asked the same question in the thread for nAOSP Android 6 and there the answer was that those optimizations were not included.

So back then (few weeks back) I just flashed parrotmod in TWRP over the installed nAOSP_Nexus7_Grouper (b07 I reckon) and that worked fine.

The ultimate answer needs to come from [MENTION=6754437]millosr[/MENTION], of course.
[Nexus 7 Android Development] zerbey:
Ontzettend bedankt! :) I put it on there and got the usual speed boost I get with my 6.0.1 images.
[Nexus 7 Android Development] millosr:
b02 released

Changes:

AOSP android-7.0.0_r11 - October security patch (*)

Video: fixed hw decoding (thanks [MENTION=4948627]daniel_hk[/MENTION])

Selinux: switched to Enforcing

Stability: fixed reboots when playing media

Ui: fixed widget placing on home screen

Ui: fixed gaps in recent list

Apps: added PerformanceControl (thanks daniel_hk)

AOSP android-7.0.0-r11

Google release yesterday new code on its aosp repositories and latest tag on nougat-release branch was android-7.0.0-r11.

We have merged that tag with nAOSP forked projects and build using it. Today google removed tags r8-r11, so the latest tag on nougat release is android-7.0.0-r7. They also created new branch naosp-bugfix-release with tags r12-r14. Since I have already merge/build/test b02 with r11, I'm releasing it with that tag. I have compared r7 and r11 and there are no difference except in build (build number) and packages/apps/CellBroadcastReceiver (r11 contains fix for japanese emergency messages).

Video playing

Now video works in every application thanks to daniel_hk fix. Problem with previous version was Media Framework Hardening which introduces constraints that are not satisfied with N7 old codec implementations. Luckily there is a way to by pass those constraints.

Video playing works very smooth. There are no more reboots from internal Video Player and other media apps.

Selinux, Stability

New version uses selinux enforcing, and it's much more stable that b01. I didn't experienced any FCs or reboots.

Download:

Nexus 7 (2012) WIFI: nAOSProm-7.0-grouper-b02.zip

md5: c112e884387c33c6c2255eeca1c478c7

Nexus 7 (2012) WIFI+3G: nAOSProm-7.0-tilapia-b02.zip

md5: 5b0b5716eab710f4956470437723b75c
[Nexus 7 Android Development] noleng:
Great work. My system is very stable, and alot faster than 6.0.

For now I am re flashing gapps along with the update, but must we still do this in order to obtain the currently installed apps, or can we just update the rom.

Also.. Is there a wat to access any sort of shortcut to the stock installed superuser app. Or do I only get to use the app ops.
[Nexus 7 Android Development] frov:
I use Titanium Backup to restore all my additional apps after clean flash.

The superuser setting is just another 'app permission': Settings --> Apps --> Yourapp --> Permissions.
[Nexus 7 Android Development] millosr:
These ROM builds are full OTA packages, so they wipe system partition and reinstall all system. Gapps on system partition are wiped so they need to be flashed together right after flashing the rom, before reboot. Since rom size is bigger for 7.0 and open gapps are also bigger, I recommend using Open Gapps pico variant.

It is not necessary to do clean flash for every rom update. It's recommended for major OS version upgrades (6.0 to 7.0), when coming from other ROMs, or when system becomes unstable (because of installed apps for example). I'm doing dirty flash for almost every update and never had any problems.

For the superuser - Settings > Apps > Setting icon (Configure Apps) > App permissions > Superuser opens list with the apps with superuser permissions

You can also do it with Settings > search icon > 'perm' > App permissions ...

For the individual app you can also open launcher drawer, long press on the app and then drop app on App Info.

Superuser permission is integrated in the system like any other app permission so for controlling it you have to use standard app permissions settings.
[Nexus 7 Android Development] millosr:
I'm not using ParrotMod. I have tried it with nAOSP-6.0, there was some improvement, but I didn't like hassle of flashing supersu and it. I prefer clean rom with basic gapps (open gapps pico) and embedded su.

For me the rom is working sufficiently smooth so I don't have to add additional stuff.
[Nexus 7 Android Development] frov:
Yes, clear. I would say that Y/N applying parrotmod is also dependent on how bad the flash chip is in your N7_2012: that mileage varies and for the really bad ones using parrotmod will have more (positive) impact.
[Nexus 7 Android Development] noleng:
I liked having the option of loading the SU interface. I was playing around with installing superuser from the playstore and manually via the apk once or twice, as each time I would have issues after updating the binary via twrp or other methods. always would have the google loader continuous and never fully booting. Once though I did have the # logo in the nAOSProm options menu directly under the Settings Shortcut title. This allowed me to get into some sort of su app. I am not sure if this was due to me trying to install a superuser app from the playstore. But after restoring a backup of the same rom, and the shortcut is not there any longer. and I am scared to try to install another su over the stock one as it always gives me problems. Also I assume that I do not need to install busybox as it is already installed correct.

Having the su interface just seemed easy to use as a reference for logs, etc.. easier way to reference if I did or didnt give permission for root or not..
[Nexus 7 Android Development] frov:
B02: wauw, runs like a charm! Video now works fine in all the apps that failed before (NOS / kodi / Horizon Go). I am happy :)

Many many thanks!
[Nexus 7 Android Development] Ammar_Hamdan:
Smooth and stable ROM..
[Nexus 7 Android Development] 239:
Well done, thanks for your efforts!

It works fine overall, had only small issues but nothing deal breaking so far. Music app failed to play MP3 files, didn't try other apps yet.
[Nexus 7 Android Development] abhifx:
Does the tablet charging works fine on this rom?
[Nexus 7 Android Development] frov:
Yes, works fine here. Never had any issues with charging.
[Nexus 7 Android Development] millosr:
There is permission issue in music app. If it doesn't have storage permission it will ask for it, but for some reason it won't play music until restarted.

So after giving it storage permission you have to close it, swipe it from recent list and start again.

You can also try give it Storage Permission from App Info settings and do Force Stop.

Once you give it storage permission it should work properly. If you do dirty flash upgrades it will keep the permission.
[Nexus 7 Android Development] jpmaster:
I'm a user of nAOSProm 6.0.1-b07 and b08. It works very well, very stable and fluid, especially with Parrotmod.

When [MENTION=6754437]millosr[/MENTION] announced the nAOSProm 7 and the intention of stopping development of 6.0.1, I've tried moving to nAOSProm 7.0-b02, skipping b01 because it seemed too alpha, with opengapps pico and it booted well without any problems.

When I opened the SuperSU interface, I noticed that it had upgraded to v.2.78 and asked to update the su binary, to which I agreed.

After that, the tablet never booted again, staying on boot animation endlessly.

The same happens if I flash SuperSU via TWRP, when flashing nAOSProm and opengapps.

By the way, flashing Parrotmod caused the same behaviour.

Also the swipe up of the initial lockscreen only works after 3 or 4 tries.

The general behaviour is acceptable, a little more laggy than nAOSProm 6.0.1-b08 with Parrotmod.

Going to wait for b03 to see what changes...

Thank you for this nice rom for our old Nexus.
[Nexus 7 Android Development] frov:
Question: do you mean to say that flashing B02 + Parrotmod will result in boot-continuous?

If so, I would first flash & run B02 and after that flash in Parrotmod.

Oh, and on SuperSU: I tried SuperSU for the XperiaS (almost same Rom acc to [MENTION=6754437]millosr[/MENTION]) and there it became clear that SuperSU can not be flashed in the present nAOSP roms. I reckon the same is true for nAOSP for Nexus 7.
[Nexus 7 Android Development] zard:
The same for CM 14 Nouget roms for OnePlus 2. Use the built in root for now.
[Nexus 7 Android Development] GreyCelt:
Hi. Just pulled my N7 2012 out of a drawer and thought I'd see if there was anything new happening for it. I found this thread and when about flashing as soon as I could. Unfortunately, I ran into an error when flashing. Please see attached and help if you have a solution.

Previous to flashing this ROM I did a complete wipe of everything.

Thanks!