yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] nbehary:
The next two days, ignoring a meeting tomorrow morning, are my weekend. I'm starting to work on 7.1.1 now. Fingers crossed, I can get it up and running in the next 2 days. (The kernel changes that correspond to the Dec Security Update will wait for CM to release one. Just piggybacking off them is much better than me doing it, since I'm not super kernel savvy).

I'm going to reset to AOSP since this is a point release (and 7.1 was weird.) Hopefully doing that, I can catch what I did to break GPS, which it looks like I did during the 7.1 update.

I'm ditching doing an actual release for the Nov patch. The "test" one I posted the other day is it.
[Nexus 7 (2013) Android Development] nbehary:
The last build, after 0.8.999, fixed that. I've updated the OP to include download links for that so you don't need to search comments. (0.8.9999)
[Nexus 7 (2013) Android Development] nbehary:
Uneducated guess, but 7.1.1 may take a bit. It builds, even with the full patches for this Rom, but hangs on boot in ways that are new and maybe beyond me, even with a straight as possible AOSP build. (for now. Fun project. It is probably more like bringing it up to N from M than a simple point release. New to me recently. I did it, without releasing or thinking about it from 4.3 to 4.4 on flo. That was cake though. This is more from the looks of it.)
[Nexus 7 (2013) Android Development] nbehary:
Well, progress. The issue was SELinux (which I should have guessed sooner.) I'm now sure I'll get a build out today. It may be a bit broken, and have SeLinux set to permissive. We'll see. (This shot is from straight as possible AOSP, is actually 7.1.1_r1 instead of 4 so the build id is wrong, and missing most of the Rom specific patches. I'll see how those do after my thing this morning)
[Nexus 7 (2013) Android Development] nbehary:
v0.10.0, 7.1.1_r4.....

Is on the OP and below.

Went with a "don't be a perfectionist" approach. GPS and Wildvine are still broken, but it otherwise seems as "working" as 0.8.x. This went far quicker than I thought, mostly because I made some good decisions in the 7.1 update to make things easier (and then promptly forgot them in Nov....whoops). Will tackle the remaining issues (and new ones, I doubt there isn't more I've missed), tonight and tomorrow.

The Dec Security Patches for the kernel are not there. Soon. (it does have Nov's though)

I did a factory reset while diagnosing the SELinux problem. You can probably, maybe, dirty flash, but I'm not sure.

Flo

Deb
[Nexus 7 (2013) Android Development] nbehary:
See a few posts above you for the Keep issue. You just have to enable permissions. Which I thought I checked in my initial triage of the reported bugs yesterday. (and you shouldn't have to anyway. Not sure why it is doing that. Other Apps I install through Play get them on their own just fine)

[MENTION=4364774]vince2008[/MENTION], The 2012 thing will be fixed shortly. I left out part of [MENTION=4318865]DevSwift1[/MENTION]'s fix for that when merging things together for my build.

Still looking into the Camera issue.
[Nexus 7 (2013) Android Development] nbehary:
Not sure why you need that. I can only tell you for sure that zImage in boot.img changed for the kernel update. system.new.dat is the whole system image which has, basically, all the changes between r6 and r14 in AOSP.
[Nexus 7 (2013) Android Development] firepower9966:
tried setting permissions on other google apps, still force close on start. Looking at permissions shows they have all been turned off.

no non google apps seem to be affected.
[Nexus 7 (2013) Android Development] nbehary:
I'm seeing the "need to reinstall any gapps that you installed from Play" issue again in what will probably be v0.7.1.

I'm not sure, but I think changing the device name (which both v0.7 and v0.7.1 do since 0.7 was missing the fix in v0.6, and the latest has that again), may be screwing with things. Can't say for sure, but I know I didn't need to between my r14 test build and 0.7, but both of those id'd as the 2012 N7. (and cant remember if I needed to for the test. I bet I did)

Still testing that a bit before I post it, but you may want to wait and flash it before you go through and re-install things. (don't know that you won't need to anyway, but I'm almost sure you will again with v0.7.1, if you do it on v0.7)

Keep needs permissions granted manually no matter what, even after re-installing it. I'm not at all sure why. Nothing else seems to need that.
[Nexus 7 (2013) Android Development] firepower9966:
I did change device name in 0.6 Nexus 7 > Pixel to get Google assist to work, had no problem with google apps. changed it back before installing rom.

are you able to upload 0.6 to android file host? can not DL from mega site.
[Nexus 7 (2013) Android Development] gangrenius:
Cast screen to Chromecast doesn't work. Won't connect. But watching YouTube videos through YouTube on Chromecast does work .just not the native built in screen cast!
[Nexus 7 (2013) Android Development] nbehary:
v0.6

boot.img

Flash them both! v0.6 doesn't include the full Sept Security update w/o the boot.img.
[Nexus 7 (2013) Android Development] nbehary:
V0.7.1 is up on the OP, or here. The only change is the device correctly reporting itself as being the 2013 N7. Doesn't seem to effect anything really.

I'm going to actually recommend a wipe before flashing this, especially if you came from v0.6 without doing one. You may be fine without, but it is probably a good idea. (no hard reason, but I think I did for my v14 test build, and that would explain some things with gapps that aren't the Keep and Play Games issue, which seems universal)
[Nexus 7 (2013) Android Development] firepower9966:
Thanks, I try 0.7.1 first, if still having trouble with google apps i revert back to 0.6
[Nexus 7 (2013) Android Development] Bull_PT:
Any chance of a deb version? :o :fingers-crossed: :good:
[Nexus 7 (2013) Android Development] nigelhealy:
(noob type question)

Does this have the capability (addon.d ?) where you can dirty flash the ROM by itself and not need to flash gapps again?
[Nexus 7 (2013) Android Development] nbehary:
The Keep issue is weird, and I'm going to chalk it up to the app itself. It targets API 23, so should use the new permissions model, so Play doesn't ask, but it also doesn't tell you about Permissions in Android 6.0 when you install through Play, which anything else that targets 6.0 does. It never asks for permissions, but on my phone, it works fine with none granted. (which it shouldn't).

I'm submitting feedback to G about that.
[Nexus 7 (2013) Android Development] nbehary:
Was just thinking about this. Yes. I'll build it for deb. I won't be able to support any issues exclusive to deb though.

I'll have that up shortly. (on this post. I'm not maintaining 2 threads)
[Nexus 7 (2013) Android Development] nbehary:
On a whim, I decided to play with using the qcom/media repo from SAOSP since there are no reports of video not working there. It fixes that.....

So, v0.7.2 is on the OP, and here with working video recording.

Thanks to [MENTION=6284619]simplyme2908[/MENTION] for that (and [MENTION=4217103]zaclimon[/MENTION] for the commits the changes came from.) I'm not sure if those also effect the video quality issue. I know zac has improved that on mako, but not sure this stuff is all of the fix. (or any of it). I can't tell if things are better.

Let me know if it seems better.

(A deb version of this will be up later today.)
[Nexus 7 (2013) Android Development] Link_of_Hyrule:
Thanks I'll probably flash once it's at 0.8 if not I'll wait for Android 7.1 I guess.
[Nexus 7 (2013) Android Development] RazGame:
Someone can check one thing ? On DevSwift1's rom i can't download Google Camera from playstore (not aviliable) What about this rom ?
[Nexus 7 (2013) Android Development] zaclimon:
I didn't even know that flo was using camera source based Metadata for its recording. (Probably in it's HAL1 implementation) In theory, it shouldn't change anything quality related AFAIK.

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 7 (2013) Android Development] biontx:
I am using v0.6. I want to make a zip flash of the files that are changed. I don't want to flash the full system again. So could you make a reference list with the names of the files that are changed with each update? Could this be possible?

PS: great work to keep this ROM up to date!!!
[Nexus 7 (2013) Android Development] ryancell:
If I jump into this ROM, once 7.1 is released if the OP maintains work and makes a 7.1 version, if I am on this 7.0.0 will I be able to apply the zip of 7.1 and retain my install/apps? Or would that require a clean install? Thanks! Looks forward to the rom/progress!
[Nexus 7 (2013) Android Development] nbehary:
Yes, it installs. I needed to use a direct link to the entry to do it since it doesn't show in search (anywhere) for me:

https://play.google.com/store/apps/details?id=com.google.android.GoogleCamera
[Nexus 7 (2013) Android Development] wavedashdoc:
Working great! Thank you for the update! Dirty flashed over 0.89999.
[Nexus 7 (2013) Android Development] mslatter:
Understood that GPS is non functional at this point. I tried to install a couple old ROMs to get GPS back and still not working. Seems if I installed one of the original versions of this that GPS would return but no go. Maybe I need to flash stock to get it back on the first version?
[Nexus 7 (2013) Android Development] nbehary:
I'm not actually sure where GPS broke. Until you mentioned it, I had never actually tested it specifically. I just took it on faith that it worked in Devswift1's builds since he said so, and I'm 99% sure nothing I did for the Oct Patch (0.7.x) would have killed it. I'm less sure about 0.8.

Here's my backup of the last version before I took over (0.6) if you haven't tried that. I am curious to know if it worked there and then broke in 0.7 or later.
[Nexus 7 (2013) Android Development] nbehary:
Hmmm. Looking way back to see where GPS was originally fixed, I did test it back in 0.1 and reported that it actually worked despite it being in the "bugs" category initially back then. (and it really did work then. I remember it now)

Which sucks. That means nothing "fixed it" possibly, it just worked. (or not. going to dig through zaclimon's early stuff now)
[Nexus 7 (2013) Android Development] mslatter:
nbehary please don't worry about it. I've tested other N builds for Flo to see if I could find one that had a working GPS and I have had no luck. I do not think it is anything you have done, it just doesn't work on N yet :) I will try your backup version and let you know how it goes as soon as I can! Thanks for posting it :)
[Nexus 7 (2013) Android Development] iminnow:
v0.10 Twrp lost
[Nexus 7 (2013) Android Development] ajsbonneville:
gps works very well as does everuthing else on .8.1
[Nexus 7 (2013) Android Development] vkk178:
Haven't really played with GPS b4 . Seems like it is working in 0.8.1 i.e. I can see satellites in high accuracy mode but lock on is very slow.i remember I had turned of gps because of battery drain due to "Cell radio" ..

Anyways great to see a new build.. [emoji111]

About the 0.8.1 build ,it's rock solid ..So far uptime of 604 hours with no major issues or lags .besides the issues already pointed out non wireless display/Miracast didn't seem to be working
[Nexus 7 (2013) Android Development] mslatter:
I installed the wrong, rebooted recovery, installed gapps and everything appears to work until I enter my Wi-Fi password during setup and then gapps keeps crashing. I guess I need to find some other gapps instead of opengapps pico. Will advise.

This is what I was afraid of. I suspect a flash somewhere along the lines broke GPS for me. I suppose I will have to flash back to stock to see if that fixes it. I appreciate people speaking up about GPS! Now I need to go and figure out how to do it! LOL
[Nexus 7 (2013) Android Development] nbehary:
Well, it bugs me. Even more now that it seems to be working for others. I want to know what happened since I know it was working (and the bits that really should affect GPS have not been touched in months). Let me know if going to stock and back works. I don't really understand why it would but.....
[Nexus 7 (2013) Android Development] nbehary:
You lost Twrp flashing 0.10? That shouldn't happen. There isn't a recovery image in the zip. (I think. I know I didn't change anything there and it didn't kill mine)
[Nexus 7 (2013) Android Development] iminnow:
0.81 flashes to 0.10 after the root twrp lost
[Nexus 7 (2013) Android Development] nbehary:
Hmm. This doesn't explain why going backwards isn't helping, but the Wildvine patch from CM I put in removed the GPS config from the vendor makefile. That can't be right. Maybe putting it back will help.

ETA: And it only did it for Flo, which would explain it working for some but not others if they are on Deb.
[Nexus 7 (2013) Android Development] nbehary:
0.10.0.1 (Flo only)

Here.

All it fixes is GPS which shouldn't have been broken on Deb (or what I changed won't matter anyway and something else is wrong).

It takes forever to get a fix for me, but I know that is an issue in this house and it is 17 degrees F outside and I like warm. But it does get a fix and GPS Status and Toolbox sees the hardware now, which it hadn't for me since at least 0.8.999 when I started looking at GPS. (the thing that broke it was introduced in 0.8.999)
[Nexus 7 (2013) Android Development] shangjiyu:
Download URL typo?
[Nexus 7 (2013) Android Development] matlala:
Wrong link. https://www.androidfilehost.com/?fid=457095661767121491
[Nexus 7 (2013) Android Development] nbehary:
Thanks. Fixed now.
[Nexus 7 (2013) Android Development] menaceinc:
I was wondering what version of Google Camera will work with the latest. The stock version 2 works, but I like the Google one.
[Nexus 7 (2013) Android Development] nbehary:
This is still the latest that fully works. (3.x only the front camera works, and 4.x crashes on start still)

Google Camera 2.7.008

ApkMirror does have a 2.7.010 from 2 days ago, but it fails to install with a signature issue for me.
[Nexus 7 (2013) Android Development] menaceinc:
Thanks! I installed it without any problem.
[Nexus 7 (2013) Android Development] miki67:
Ok!... 7.1.1r4 0.10.0.1 dirty flashed over 0.8.1 and all works very very well on my beloved Nexus 7 2013 (flo)... Thanks nbehary!

Inviato dal mio Nexus 7 2013 (AOSP Nougat 7.1.1) con Tapatalk 6
[Nexus 7 (2013) Android Development] Startrek852:
[MENTION=3286382]nbehary[/MENTION], I found how to fix Google Play Movies & TV! You have to change this line in device/asus/flo/aosp_flo.mk:

$(call inherit-product-if-exists, vendor/asus/flo/device-vendor.mk)

to this:

$(call inherit-product-if-exists, vendor/asus/flo/flo-vendor.mk)

and this line in device/asus/deb/device.mk:

$(call inherit-product-if-exists, vendor/asus/deb/device-vendor.mk)

to this:

$(call inherit-product-if-exists, vendor/asus/deb/deb-vendor.mk)

The reason is because device-vendor.mk calls the device-partial.mk's that are in vendor/asus, vendor/broadcom, and vendor/qcom which then copy the old unfixed blobs. But calling flo-vendor.mk/deb-vendor.mk will cause all the new fixed blobs to be copied. And BTW, the DRM stuff isn't called Wildvine, it's called Widevine.
[Nexus 7 (2013) Android Development] nbehary:
Thanks for the tip, trying it now. And, I know about the name. Got it stuck in my head as Wild at the start and once that happens it takes me forever to un-teach myself. I probably will now with it fixed (hopefully) and never need to type it again.
[Nexus 7 (2013) Android Development] Startrek852:
You're welcome. You should also delete both device-vendor.mk's, vendor/broadcom, and vendor/qcom because they're not needed. If you don't, you will also need to change that line in device/asus/flo/device.mk. And same thing happens with me, it takes me forever to unlearn the wrong name to something or to learn the new name of a business or something if it changes names.
[Nexus 7 (2013) Android Development] nbehary:
That's not working, but completely different errors that show widevine is there and trying to work. Thinking I should pull the version of it from the 7.1.1 release bullhead image. (trying that.)

Edit: or do what you said in the comment I hadn't seen yet. Or both.
[Nexus 7 (2013) Android Development] Startrek852:
That's the exact same thing that CM did that you pulled into your repo.
[Nexus 7 (2013) Android Development] wavedashdoc:
GPS is working for me with the latest build.
[Nexus 7 (2013) Android Development] nbehary:
But from the DP. I just pulled the ones from the NMF26F one published 2 days ago. Probably a better fit. (No idea if that will matter, but worth a first shot)
[Nexus 7 (2013) Android Development] Startrek852:
Sounds good.
[Nexus 7 (2013) Android Development] ajsbonneville:
I should have mentioned that I was on stock before updating to to .8.1

Also the gps was very quick.

Also on elemental kernel. 6.03
[Nexus 7 (2013) Android Development] wavedashdoc:
I cleaned installed 7.0 from the previous OPs work from the other thread before this dev took over. I've been dirty flashing each build. GPS was never a big issue for me but I believe it's been working for me with each build since 7.0.
[Nexus 7 (2013) Android Development] nbehary:
The way things look, GPS was probably fine up to 0.8.1, then broke in 0.8.999-0.10.0 (Flo only). I think I thought it was broken through the 0.8.x's due to quick undetailed testing and the fact that GPS in this house is just crap as I mentioned. There was a definite change in 0.8.999 that would break it. (There are artifacts from that that I still need to remove. Ninja is telling me it should still be broken now, but it isn't)

I hate to say this sort of thing, but I suspect that [MENTION=2982186]mslatter[/MENTION]'s issue may be hardware if it isn't working on any builds that aren't in that range. (or there is something that going back to stock that can fix it)
[Nexus 7 (2013) Android Development] nbehary:
Throwing this out there in case someone knows. Googling this gets fun, but totally unrelated results. Widevine's issue seems to be this in logcat:

WVCdm : Skipping submission. Submission has time travelled.Start=1481238940814915 End=1481238940900700 Tail=1481238940895726. Should be Tail<=Start<=End

Not those exact time stamps, but otherwise the same trying to play anything. Tail is always after Start. Clueless as to what would cause that. (There are lots of other errors, but that seems to be the core issue, with the others following from it)

Swapping out newer binaries didn't change anything.

Edit: it won't be this in any released build, the errors in those are about widevine just not being there. If you want to help, and need a current one, I can put up a newer one (that doesn't fix anything.)
[Nexus 7 (2013) Android Development] Startrek852:
Can you push the modified device trees and vendor files to GitHub?
[Nexus 7 (2013) Android Development] mslatter:
[MENTION=3286382]nbehary[/MENTION] again, thanks for all your efforts. I will let you know how it plays out. I tried your new build but Gapps kept crashing right after I entered the WiFi password during setup. Tried Older and Newer 7.1 Gapps that I had on the tablet (can't remember the dates - think it was 12/02 and 12/07 PICO)....so I gave up and flashed stock. But of course, nothing is easy....got stuck in a bootloop after flashing stock. It would come to where the launcher loads and ask me which launcher I wanted to use...and then lock up for a few seconds before flashing up some google reporting tool and then rebooting. So I've flashed TeamWin recovery, and am downloading new Pico Gapps from OpenGapps and your latest ROM to see how that works. Too many folks are using bandwidth in my neighborhood and speeds are crawling - so may only be tomorrow evening or Saturday when I can continue. Thanks again for your efforts / advice / feedback!
[Nexus 7 (2013) Android Development] davidsds:
[MENTION=3286382]nbehary[/MENTION], thanks for this great ROM. I was using the FLO_AOSP_7.1.0_r4-v0.8.1 for a week and worked stable like the best stock versions. Everything I use worked well (despite the known issues), except two things:

* A widget from play store: "Play store -> Library -> My books". I can add the widget but it stays empty, my last read books not appears in the widget.

* Goggle Maps: I can open, locate using GPS (yes, GPS works well with me in this version), but I can't login. It show a error message and say to "Try again in a few minutes".

Yesterday I did a dirty flash to FLO-AOSP_N-7.1.1_r4-0.10.0.1 and until now is so stable like v0.8.1, but the two issues above still the same to me. Anyone are have these issues or is only me?

PS.: I don't have any google apps FC issue. I can login and use play books, games, keep, store, calendar and music, and chrome, youtube, search/now, home and gmail, without any problem. I have problems only with Maps (uninstall, clean data/cache not fix the issue).
[Nexus 7 (2013) Android Development] miki67:
I confirm to have the same issue for PlayStore > My books empty widget beginning from 0.8.1.... Maps for me doesn't have any login issue [emoji57]

Inviato dal mio Nexus 7 2013 (AOSP Nougat 7.1.1) con Tapatalk 6
[Nexus 7 (2013) Android Development] MadHacker:
MAPS is a Permissions thing, goto SETTING>Apps>Maps and set Permissions. Will no longer ask for login.
[Nexus 7 (2013) Android Development] davidsds:
Thanks for the tip [MENTION=1218926]MadHacker[/MENTION]. Maps are working now (permission to access "contacts"). The strange is, if I uninstalled and installed again, it should ask me to allow the necessary permissions. The only one asked to me is "location".
[Nexus 7 (2013) Android Development] htb2050:
This kinda stuff is usually fixed by going into apps and then resetting app preferences which resets all settings for apps without any data loss and they ask for all related permissions like they are freshly installed.
[Nexus 7 (2013) Android Development] drewski_1:
deb build working fine with dirty flash. will test GPS when I get home
[Nexus 7 (2013) Android Development] drewski_1:
GPS :good:
[Nexus 7 (2013) Android Development] nbehary:
The device tree I never forked and I can't push to the original. Doing that now, but the only change I've even made in there is this commit. (for this issue)

Fixing that shortly. The updated flo binaries are up. (and the manifest is up. which I hadn't pushed yet. Though I think nothing really changed except not using S-AOSP's qcom/media which is something I just did to try. Don't remember why I pulled that in at all)
[Nexus 7 (2013) Android Development] Startrek852:
I found the problem! You need to delete liboemcrypto.so from vendor/asus/proprietary/lib and vendor/asus/proprietary/vendor/lib, deleting those files completely fixes it.
[Nexus 7 (2013) Android Development] nbehary:
Seriously? You know, I had that thought with the commit I linked above removing the reference to them, but never did. (or probably assumed they were gone from pulling in CM's stuff, but thinking, I did that by hand. Wouldn't have deleted that......oh well)
[Nexus 7 (2013) Android Development] Startrek852:
Yes, seriously.
[Nexus 7 (2013) Android Development] nbehary:
Grrr. Stupid me. Oh well. New builds shortly.
[Nexus 7 (2013) Android Development] ajsbonneville:
running 0.10.0.1 pico gapps elemental x.

no problems with anything to date. tested playstore my books. all good.

many thanks to you nbehary, for all your work
[Nexus 7 (2013) Android Development] DorianX:
Gps is working for me on 0.8.1...

Enviado desde mi Nexus 7 mediante Tapatalk
[Nexus 7 (2013) Android Development] xI mEzMeRiZe Ix:
Trying this ROM out for the first time. ROM flashes in TWRP, but when I reboot the recovery and try to install the 7.1 micro gapps, it just hangs forever when installing.

Edit: And of course, the second I post my comment, the installer starts working...

---------- Post added at 12:03 PM ---------- Previous post was at 11:37 AM ----------

Any way to get Night Light?
[Nexus 7 (2013) Android Development] DorianX:
You can try with this app: https://play.google.com/store/apps/details?id=com.nightmode

Enviado desde mi Nexus 6P mediante Tapatalk