yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] ryanexec:
Only because this was asked publicly: To keep our still-capable flo/deb devices alive on the latest Android version; if he's patching it, then I don't think it can be called unmaintained. This seems to have become the go-to stock-ish Nougat ROM for the Nexus 7 2013 devices, unless there's another I'm unaware of.

Aside from some pretty significant security patches, what else is needed to maintain a ROM that's working very well as-is?
[Nexus 7 (2013) Android Development] vbaros:
Is there a way to patch the system for night light?
[Nexus 7 (2013) Android Development] philseven:
any one have copy of gapps 7.1 can't steam to get them downloaded from oppen gapps
[Nexus 7 (2013) Android Development] ATSPerson:
GAPPS 7.1 Micro

open_gapps-arm-7.1-micro-20161030.zip

HTH
[Nexus 7 (2013) Android Development] nigelhealy:
This is the link that gapps gives me which works just fine 32bit ARM 7.1 nano
[Nexus 7 (2013) Android Development] foxdog66:
Google camera wont install for me either, same with pixel launcher. Using 7.1 aroma installer
[Nexus 7 (2013) Android Development] philseven:
Thanks
[Nexus 7 (2013) Android Development] mcollini:
Excellent Work Running V08 / Open Gapps Micro / Viper for Android / Glitch Kernal and SU 278 for root. Loaded right up restored all my Apps I'm liking it, Did I mention substratum is working fine as well. Very nice rom indeed.
[Nexus 7 (2013) Android Development] nbehary:
It is a fork of an un-maintained, basically straight AOSP Rom. All that really should be going in are security patches and point releases, someday O. I am going to put in a few things I'd like to see that are small enough to still consider it straight AOSP, but that's it.
[Nexus 7 (2013) Android Development] delawaredrew:
Figured I'd try this ROM out due to wifi issues on the AOSP Nougat ROM. I'm super stoked to find the Nexus 7 being pushed on to Nougat by the devs here. Thank you!!

I wanted to see N and I knew I'd be waiting a while for it to get installed on my Samsung AT&T devices.

Anyone get an abnormally long wait for reboot? It happened also on the other N ROM I'd been using. Both times it was the 1st reboot after rooting. It rooted and booted fine immediately after; the oddness happened on the next reboot.

I usually reboot into recovery after boot to make a backup once I am happy it installed fine and is rooted, but before adding much else to a ROM. On both N ROMs I've tried I got a long enough totally blank screen that I was concerned. By blank I mean nothing, not lit up black or anything.

It has successfully rebooted now but it took 10+ minutes of sitting. Subsequent boots seem to be normal but I'm curious if anyone else has seen this?
[Nexus 7 (2013) Android Development] nbehary:
I haven't seen that and from the description that's before boot even starts if the screen is just blank, it probably isn't software. (checking, this is before the Android animation, right? After could be a Rom issue.) Can't be sure, but I'd suspect hardware. Not sure what would cause that though.
[Nexus 7 (2013) Android Development] bd177:
I've noticed on N , the first boot after flash, takes from 5 to 10 minutes. That's at the boot animation not a blank screen.
[Nexus 7 (2013) Android Development] delawaredrew:
Yes it is before any animation at all. If I understand the boot order right it is prior to whatever process the bootloader goes through when the "Google" screen is displayed. As a long time Linux user I've been an Android fan for a long time (since Donut) but have never learned the details. I've always meant to but others can already do it so there's never been a reason.

If it was hardware I can't easily explain why it only happened once during both Nougat installs and after several successful boots. I think I was manually entering recovery by holding the buttons both times so maybe a button is wonky after being pressed for a few seconds? I may try to install the Screwd Marshmallow ROM I had a few weeks ago later this week and see if it repeats.

Whatever happened it recovered so no big deal.

I do like the ROM and appreciate your work on it.
[Nexus 7 (2013) Android Development] nbehary:
I haven't seen that long. It does take a while, and will more if flashing SuperSu. That I'm not worried about, it is probably normal enough.
[Nexus 7 (2013) Android Development] atifsh:
yeah it's very little space left in 7.1 system. plus camera issue i think is the version available in 7.1 gapps, you can't use anything but the old gui version which is 2.5i think.

---------- Post added at 01:32 PM ---------- Previous post was at 01:29 PM ----------

just guessing, long boot times might be because of older bootloader. check your bootloader versions.
[Nexus 7 (2013) Android Development] jisoo:
It's doing that "optimizing apps", but the dialog is not shown. Google factory images already have the apps "optimized" in the userdata part of the image, and other AOSP ROMs usually modify the code so that the dialog is visible.

In "pure" AOSP, the dialog is not there, hence it seems like the first boot takes ages without anything happening. If you follow the log on logcat, you can see the system is actually quite busy working through the APKs in the /system partition.
[Nexus 7 (2013) Android Development] sweenish:
Still no word on Play Movies?

I believe the DRM libraries are not included, or something like that. The app won't work if you're rooted, but it should work if you decide not to root. It's one of the main reasons I'm keeping my N7 on marshmallow right now.

I imagine magisk with the auto-hider would also work.
[Nexus 7 (2013) Android Development] utfluc:
It doesn't have anything to do with root, it's all about Google's widevine drm binaries not being included. I have many rooted devices with functioning play movies.
[Nexus 7 (2013) Android Development] muschiu35bv:
Hello Guys!i made clean install of the FLO_AOSP_7.1.0_r4-v0.8.1.zip and open gapps 7.1 nano using multirom with no problem.the only problem i have is when i tried to open developer option the screen get black and i get pop up settings has stop.Anybody has this issue?
[Nexus 7 (2013) Android Development] jimbob_sf:
Hopefully this can help someone. I just tried camera, gps, and Bluetooth and they all appear to be working.

* Google camera 2.0.002. Don't know if it was baked in the rom or from open gapps 7.1 micro.

* GPS locked in seconds. I always use Faster GPS to set the servers, so I don't have a test without using it first.

* Bluetooth connected to my Pebble Steel. This is my most problematic device because it uses LE (low energy) as well as the normal BT connection (My G3 won't connect unless I'm on a stock rom).

A note for the poster with potential hardware issue with long boot. I've got a drawer of flo parts. If you've never opened your device, it would seem odd that hardware is the cause (never say never though). Hardware, for me, hits with weak touch areas (lower right is a typical area) and poor charging or connectivity to computer (usb daughter card has a few versions that need to be aligned with the motherboard - could be wrong but the stack of them I have says there is something there).
[Nexus 7 (2013) Android Development] drewski_1:
2.0.002 is the AOSP camera included in the ROM. Open GApps only has Google Camera in Stock & Super packages
[Nexus 7 (2013) Android Development] sweenish:
So, that isolates the issue.

Just need the solution implemented.
[Nexus 7 (2013) Android Development] mick3lson:
I've the same issue in developer options with crash and black screen.

My setup is FLO_AOSP_7.1.0_r4-v0.8.1.zip installed using multirom v33b, gapps 7.1 micro and rooted with SR2-SuperSU-v2.78-SR2 and finally I installed Glitch-kernel v.5.30.

Another small issue is when I install pixel-launcher I loose the 3D Touch-like launcher shortcuts, there is a version for nexus 7.
[Nexus 7 (2013) Android Development] Ja_som:
Hi, I just changed that super shiny white Google Pixel bootanimation to black...

Preview:

http://xdaforums.com/nexus-7-2013/themes-apps/bootanimation-black-google-pixel-t3491335

Also looks good on my Nexus 5X ;)
[Nexus 7 (2013) Android Development] nbehary:
Google Camera. The last version of it that fully works on this rom is 2.7.008 which is here. That is slightly higher than the 2.5.x you get through Play (which you have to use a direct link to even get to these days, but don't bother.)

3.x all seem to "work" mostly except they will crash with can't connect to Camera for video with the back camera. (front works fine.) That may be something I can fix. Will look at it.

4.x just crashes at start up. Not surprising, there is probably more to the requirements than 7.1. (like actually being a Pixel since those are the only "real" 7.1 devices) Not going to bother trying to figure out for now.
[Nexus 7 (2013) Android Development] drewski_1:
OpenGApps does an API check (for Camera API v2+) & a device whitelist to determine if it should install Camera v3+ or fall-back to what they call "Legacy Google Camera" (aka v2.*)

i'm not a dev so not sure if ti's straightforward to add this or if there's additional hardware / camera firmware changes needed?

from the installer.sh in the OpenGApps Zip

# Check for Camera API v2 availability
cameraapi="$(get_prop "camera2.portability.force_api")"
camerahal="$(get_prop "persist.camera.HAL3.enabled")"
if ( grep -qiE '^forcenewcamera$' "$g_conf" ); then # takes precedence over any detection
newcamera_compat="true[forcenewcamera]"
else
if [ -n "$cameraapi" ]; then # we check first for the existence of this key, it takes precedence if set to any value
if [ "$cameraapi" -ge "2" ]; then
newcamera_compat="true[force_api]"
else
newcamera_compat="false[force_api]"
fi
elif [ -n "$camerahal" ] && [ "$camerahal" -ge "1" ]; then
newcamera_compat="true"
else
# If not explictly defined, check whitelist
case $device_name in
ryu|angler|bullhead|shamu|volantis*|flounder*|hammerhead*|sprout*) newcamera_compat="true[whitelist]";;
*) newcamera_compat="false";;
esac
fi
fi
[Nexus 7 (2013) Android Development] nbehary:
If you are asking if there's a way to put in what that is checking for, probably. The fact that 3.x doesn't seem to work correctly keeps me from wanting to. If the issue with that is fixable, then I can look into that. (though, strictly speaking it _is_ compatible since video and stills work fine, it is just the rear camera and video combo that doesn't.)
[Nexus 7 (2013) Android Development] drewski_1:
the old camera works for me as i rarely use the tablet camera :D

i was just mentioning that Open GApps was using the Camera API v2 compatibility check in case it helps to get it working.
[Nexus 7 (2013) Android Development] nbehary:
That is good to know. If 3.x should be install-able, knowing why opengapps isn't helps. I just need to see if that is a good idea. (meaning 3.x actually fully works.)

Thanks.
[Nexus 7 (2013) Android Development] nbehary:
Do you have more info on that? widevine seems to be something that was included way, way back. (like 2011. It isn't in the repos going back to at least KK) but can't find much other info on it.
[Nexus 7 (2013) Android Development] utfluc:
I knew something about drm and widevine when I once had to implement some web player a few years ago. I know for sure play movies requires it, but honestly I'm not much into AOSP. Anyway, I'll try to scavenge some info and come back to you. Thanks for your work by the way, you're doing an amazing job!

PS: my stock 6.0.1 Nexus 5 reports widevine being installed, so it IS actually being included in factory images
[Nexus 7 (2013) Android Development] celiorty:
Thank you for work for the loved Nexus 7!

I flashed the latest v1.81 to my Flo with full wipe ( from DevSwift1's v0.6), almost every thing works just fine! It's so nice to have this solid tablet to be updated.

However the device reported by google is still nexus 2012, which should already be fixed...

Also if I use google camera the video record was cannot connect to the camera. But there is no problem for taking photos in google camera. And the pre-installed camera works fine when recording.

Just report those minor bugs that totally don't affect using! Thanks again for all the work!
[Nexus 7 (2013) Android Development] nbehary:
Google seems to report any '13 N7 as a '12, regardless of what the Rom is from reports. (including Stock MM) I don't see anything left to fix that. (it should be identical to [MENTION=4318865]DevSwift1[/MENTION]'s 0.6 in that regard).

Google Camera 3.x can't record video with the back camera. 2.7 can (see a few posts back). Looking into that. (but video from the back camera is still terrible anyway)
[Nexus 7 (2013) Android Development] nbehary:
I only just got into AOSP really. I'm more an apps guy. Though, my becoming that started way back when I played with getting KK to run on the N7 during the N5 exclusive time. Did that, then turned to Launcher3 and tried to make that run well, then added features. That became Retribution Launcher which never sold and I stopped trying, and I may be the only person using. Still do, it is my first install always. (so I want app shortcuts working. Some of my time may turn to that for a bit)
[Nexus 7 (2013) Android Development] celiorty:
Just tried the Google camera 3 on my Sony Z5 on 6.0 (rooted, stock based). Also cannot connect to the camera in video mode. I believe it's won't be the bugs for certain (this) ROM.

Thank you for the quick response!
[Nexus 7 (2013) Android Development] nbehary:
Maybe, it is a bit odd that video works from the front camera. Makes me think the back is fixable. Haven't looked into it yet. That's a project for later this week.
[Nexus 7 (2013) Android Development] osm0sis:
Sounds like the DRM may not be in AOSP but could be extracted from the final N7 '13 Factory Image? Or possibly the binary driver blobs site Google also maintains?
[Nexus 7 (2013) Android Development] utfluc:
I think I've found some starting point, apparently the story with Widevine is that they are moving from a classic client (old standalone implementation) to a modular plugin approach (named Content Decryption Module, or CDM for short).

Check the "WIDEVINE QUARTERLY PARTNER UPDATE- Q1 2016" in https://www.widevine.com/product_news.html, there's a link to a PDF file stating the repository location as well as the build instructions.

As I suspected it's up to manufacturers to integrate the CDM module into AOSP.

Let me know if I can help you any further, and thanks again!

---------- Post added at 03:56 ---------- Previous post was at 03:46 ----------

Hi [MENTION=4544860]osm0sis[/MENTION], can you please check my previous post regarding DRM? I'm curious about if it is what we're trying to nail. Thanks!
[Nexus 7 (2013) Android Development] rudolph323:
I also noticed that there is a weird speaker noise, I researched and found out that it's somehow CPU giving out some sounds through speakers, whenever I scroll, press something, the sound is more intense

[YOUTUBE]3Bk48jtiYbs[/YOUTUBE]

I barely heard this noise on 6.0.0, on 7.0 it's increased. So I guess this is one of the cons of installing unofficial ROM on Nexus 7... Is it even possible that at the end this W.I.P will be compatible in every possible way (including 1080p camera fix)?

The developer of this should add donate button or something(paypal link?), so people can donate some cash for this work..
[Nexus 7 (2013) Android Development] nbehary:
Nope. Forgot about that discussion in the last thread. (it probably would have been a v0.8 thing regardless, it is on the todo list now, after the new bug fixes)

Speaking of bugs, I have been able to reproduce everything reported here thus far and will be looking into them. That includes:

- Camera App "can't find Camera" when attempting to record video.

- Play Game install error.

- Keep force closing.

Typing that, I lied. I haven't checked the being reported as a N7 2012 thing. I'll look at it. (can't see why that would have resurfaced, unless it wasn't completely fixed in v0.6. I hadn't seen it with that though)

The noise thing, I'll look into, but that may be something that can't be fixed from the sound of it. (I could be wrong though.)

build.prop changes to enable Google Assistant. As I said in the last thread, no. I don't see that being a good thing to add to the Rom since it is changing the device name. That fix is easy enough to do yourself if you are already installing custom Roms.

Thanks to everyone for reporting issues. If I missed something, let me know. Decent amount to work on with that stuff so far.
[Nexus 7 (2013) Android Development] nigelhealy:
So I double-checked I got the versions right.

I did a full clean wipe. Then installed the ROM FLO-7.0.0_r14-v0.7.zip, then when I tried to install the ARM (not arm64, I checked) for 7.0 (not some other) - the filename is open_gapps-arm-7.0-nano-20161015.zip, then I get incompatible version error!

It says I'm on a 5.1 ROM!

Update: weirder and weirder, in case this is a bug in v0.7 which others missed via dirty flashing over v0.6. I did a clean wipe then installed v0.6 then I see it installing a 6.0.1 target MOB30X, and now Gapps say I'm on a 6.0.1 SDK 23 and still refuses to install as this is a 7.0.x gapps.
[Nexus 7 (2013) Android Development] nbehary:
I'm wondering if that is a bug in that gapps pacakage. (specifically yesterday's nano one.) Looking into that. If it is being weird like that on both versions, I can't see how it is the Rom in either case. (but maybe, somehow.)
[Nexus 7 (2013) Android Development] nigelhealy:
I'm trialling+erroring, and I tried banks gapps 7.xx - filename banks_dynamic_gapps-7.x.x-20160921.zip and I get basically the same error, complaining.

Am I somehow not wiping properly and there's some lingering versions? Short of a fastboot erase type bootloader command first?

Attaching the TWRP recovery.log you can see all my trial+error including at end the v0.7 ROM and the banks gapps not getting along.

Going into fastboot and some erasing then TWRP.....
[Nexus 7 (2013) Android Development] nigelhealy:
Yep that fixed it. It's a bug in my specific unit I think.

TWRP's wipe wasn't wiping like it claimed it was. I went into bootloader and did a fastboot format system then userdata then cache. Then booted into recovery and then it worked.

There's something a little weird about my N7, I seemed to need to use multirom TWRP to get it to not use other than stock (been on Pure Nexus MM build the last year or so).

---------- Post added at 06:10 PM ---------- Previous post was at 05:12 PM ----------

I'm up and working!

(current v0.7 ROM, current 1015 gapps, supersu, ElementalX 5.18)
[Nexus 7 (2013) Android Development] SHABBYLEA:
Bang on...
[Nexus 7 (2013) Android Development] nbehary:
I'm hesitant to actually accept donations since others did a lot before I took this over. But, I added my paypal e-mail if people want to. I guess I am putting time into this and everything. (don't feel you need to though)
[Nexus 7 (2013) Android Development] nbehary:
Or, I can not be stupid. If you look back at the first comment on this post, I mention android_build maybe not being up to date in my repos. (I named it wrong as platform_build_core there). It is, but isn't. Has all my changes, but is missing the one from msm8690 that fixed the 2012 issue.

Not worth a new build even though it is a 2 line change. Unless it fixes something important. I'm wondering if 2 of the reported bugs may be related. I'll check tmw*. (also if you know of something important that effects, let me know. I don't think there was in v0.5 and earlier)

EDIT: *- which means building it. I'll probably just replace the download link with that if it doesn't fix anything else. (if it fixes anything else, it becomes v0.7.1). I'll post in the comments about either case.
[Nexus 7 (2013) Android Development] SHABBYLEA:
OK...I think I get it...?
[Nexus 7 (2013) Android Development] yosmokinman:
For me with v0.7 flashed over 0.6 the buzzing sound is the same as the video above but not constant, only for less than a second after audio stops then no buzzing. Keep works fine as well though I didn't uninstall and reinstall.

If I remember right the buzzing is one of the hardware problems the N7 had from day one and some people had it worse than others.

Edit: That doesn't explain it being louder on N vs M on the same device as reported (I don't have that problem) but I definitely remember reading people saying the same thing with K or L updates. Who knows?

Thanks man :good:
[Nexus 7 (2013) Android Development] utfluc:
Have you tried this? Yours seems a grounding issue, and perhaps the CPU usage in nougat is causing the symptoms. In my case I have no audio buzzing, but I had to tighten the internal ribbon to get rid of the ghost touches.

http://xdaforums.com/nexus-7-2013/general/fix-nexus-7-2013-grounding-issue-t3011140/page11
[Nexus 7 (2013) Android Development] biontx:
[MENTION=3286382]nbehary[/MENTION]

Could you list the name of the files in the boot.img and the system.new.dat that are changed in comparison with version 0.6 please? Thanks in advance.
[Nexus 7 (2013) Android Development] firepower9966:
Lot of my Google apps force close on starting, keep, maps, games, music player, device manager,seems to be anything needing Google account.

Using recommended gapps in first post.
[Nexus 7 (2013) Android Development] nbehary:
This may, and I know v0.6 and before did, need you to re-install any gapps you installed from the Play Store. I consider that a bug since I don't see it on my phone on AOSP N. Not sure what the issue is yet though. (Though, thinking about it, I don't think I needed to with this or the test. Or maybe even v0.6. I'll check on it)
[Nexus 7 (2013) Android Development] firepower9966:
I uninstalled and reinstalled keep twice and it crashes Everytime I choose my account.

Other apps like YouTube and news and weather worked OK after reinstalling.
[Nexus 7 (2013) Android Development] yosmokinman:
Is it permissions? I haven't had to reinstall any google apps since 0.5 I think which had "gapps permissions fix." I dirty flashed from 0.5 to 0.6 to 0.7 no gapps problems. Playstore installed google apps that is. I flashed opengapps after each update as well.
[Nexus 7 (2013) Android Development] vince2008:
Got the same error with Keep, enabling all keep permissions will solve it, by the way this ROM works with google assistant flawlessly.

2 issues I have.

- Camera App "can't find Camera" when attempting to record video.

- reported as Nexus 7 2012
[Nexus 7 (2013) Android Development] firepower9966:
Thanks that fixed it . Enabled all permissions in setting apps for keep, will do same for other Google apps.
[Nexus 7 (2013) Android Development] bmakk2055:
Same here
[Nexus 7 (2013) Android Development] shantam3108:
V0.8 didn't boot on deb. Was stuck on patching image unconditionally..
[Nexus 7 (2013) Android Development] vArrow:
Try V0.8.1, works perfect for me, including SuperSU install.
[Nexus 7 (2013) Android Development] nbehary:
Nope. That is for OEMs to implement it, but you need a licensing agreement with G to use the repo. I think I found what I need. (or a good lead)
[Nexus 7 (2013) Android Development] shantam3108:
Thanks it worked :)
[Nexus 7 (2013) Android Development] osm0sis:
Like I thought :):

https://developers.google.com/android/drivers#flomob30x

https://developers.google.com/android/drivers#debmob30x

These just need to be applied on the build tree. :good:
[Nexus 7 (2013) Android Development] nbehary:
Um. Those are already there. Can't really build AOSP without them. (well, you can. I think the only thing you can for is the emulator without vendor blobs).
[Nexus 7 (2013) Android Development] osm0sis:
OH whoops. Shows what I know about building ROMs. :p

Weird then, it says "DRM" in the list of Qualcomm drivers, so one would assume Widevine or whatever would work with those in place. :confused: