yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] iason747:
Yeah I was on previous build with recommended PN Gapps. I updated to current build by installing the rom and wiping cache and dalvik cache (no gapps flashed). After a reboot I flashed latest magisk. I provided the link, despite it being from open Gapps, because I took a log and it showed the same errors.
[Nexus 7 (2013) Android Development] buffal0b1ll:
Interesting. I clean flashed (advanced wiped system, data, cache, and dalvik). Flashed 7/25 ROM and 7/25 beans mini gapps and have no gboard settings issues.
[Nexus 7 (2013) Android Development] buffal0b1ll:
OK. That clears things up. Clean flash (advanced wipe data, system, cache, and dalvik) is all I can recommend then.
[Nexus 7 (2013) Android Development] jimbob_sf:
This ROM is screaming fast with ElementalX! For years I've sought the most tunable ROM, but I'm finding I like the PN approach. The essential tweaks are there and the device simply works.

Question: how does one get the menu button on the nav bar as a 4th key? There is an option in the nav configuration, but it never enables. Any help is greatly appreciated.
[Nexus 7 (2013) Android Development] buffal0b1ll:
Super old apps might make that menu button show up, but I've never seen it. When apps don't detect a physical menu button on a device, they show 3 dot menus, so you'll probably never see it. If you have 2 keyboards installed and enabled you'll probably see the keyboard switcher button show down there tho.
[Nexus 7 (2013) Android Development] jimbob_sf:
Thanks for taking a look. I've seen other roms show the 3 dots all the time and if the app doesn't support it, nothing happens. I'll buy that the 3 dots may be a waste of space.

Another approach I've is a long press action on a button. How about that?

There isn't a magisk module I see for this and we don't have xposed yet. This is the only feature I truly want.

Thanks for the look.
[Nexus 7 (2013) Android Development] buffal0b1ll:
A different ROM with DU Smartbar would let you remap long press of back or recents key to menu. But the menu would still open up in the upper right where the 3 dots are, so you'd probably be disappointed with it anyway.

You could try your luck with this app https://play.google.com/store/apps/details?id=xyz.paphonb.systemuituner
[Nexus 7 (2013) Android Development] jimbob_sf:
Something isn't adding up because every rom I use across a handful of devices (current and past) all support long press menu on recents. This is the only rom that seems to speak a different language.

The app linked doesn't even offer menu as an option, so I guess I've been taking something for granted. I'll be happy with the speed and stability and say thank you for the help.
[Nexus 7 (2013) Android Development] buffal0b1ll:
Long press recents has been multiwindow on stock AOSP since nougat came out. That's what PN uses. It is what it is.
[Nexus 7 (2013) Android Development] jimbob_sf:
Now it's clicking. Forgive me if I was a little dull.
[Nexus 7 (2013) Android Development] brightjh01:
works so well

rom works so well, there nothing to say?:cowboy:
[Nexus 7 (2013) Android Development] Woody:
Hey [MENTION=4831195]buffal0b1ll[/MENTION]

Got a quick question for you. Over the last few iterations and after a recent clean flash (due to unrelated issues), I am having substantial drain for mobile connectivity. In my battery screen (plus some Android OS in BBS/GSAM), it is showing as constant with a red line. I know that there are some things in here that are ported over from the "phone" builds, but I can't figure out what is causing it to continually scan for mobile signal so I can kill that.

Any ideas?

Just to be preemptive, I have the Flo and not a Deb.
[Nexus 7 (2013) Android Development] buffal0b1ll:
I just borrow the PN dragon tablet config for the flounder and the flo. It leaves out the apps like phone and messaging, but is still bringing over some mobile stuff. I see what you mean tho. My flo loses about 15% battery per day just sitting on the shelf, perhaps it's this mobile drain. Strangely enough though, the flounder wifi tablet flat lines the battery while on the shelf for days. But the flounder has a LTE version that works with the same build (unlike the flo/deb world) so maybe it's better equipped to ignore the mobile radio on the wifi version of the tablet.

Anyhow, for now I figured I'd look and see what we can disable with root and TiBu or CCleaner (a good free alternative to TiBu that allows any apps to be frozen/disabled with root). I'll monitor and see if it makes a difference. Screenshot shows what I disabled just now...
[Nexus 7 (2013) Android Development] Woody:
I froze those right when I got home from work and just checked a little bit ago. Cellular still pinging though. I turned the Wi-Fi off while sleeping so that I could see the differences between the two bars.

Will try a few more apps and see if those have any effect. Let me know what you come up with and I'll do the same.
[Nexus 7 (2013) Android Development] iason747:
Maybe turning on airplane mode will help. If you however need WiFi you can turn airplane mode on and after that you can still activate WiFi despite being in airplane mode.
[Nexus 7 (2013) Android Development] acidspider:
I used to use an app which put my tablet into airplane mode when the screen was off to give me best battery life but think if I remember rightly it needed xposed.
[Nexus 7 (2013) Android Development] iason747:
I had a look at my battery stats as well and I also have a constant red line, but it doesn't drain my battery ( about 1-3% over night). This suggest that something else may drain your battery.
[Nexus 7 (2013) Android Development] buffal0b1ll:
On closer inspection of my battery stats I see about a 5-10 percent drop per day while idle, not 15% as I'd stated yesterday. I've got a few syncing accounts and many spots that receive push installed so I expect wakes. The 5-10% per day is consistent with what [MENTION=6295617]iason747[/MENTION] reports. Disabling the apps I screenshot yesterday didn't seem to have an affect on the idle drain or the cellular red line in battery stats for me either.

Today I installed BBS and turned on airplane mode and toggled WiFi back on. I'll shelf it and check again tomorrow.

No matter the results of these tests, I'm not anticipating any changes to the ROM. I have a hard enough time with the device and hardware trees I use to keep up with monthly security updates, let alone messing with under the hood services.
[Nexus 7 (2013) Android Development] spacemanvt:
this rom is amazing. i thought my nexus 7 was dead but now it works great!
[Nexus 7 (2013) Android Development] sirxdroid:
Just started using this ROM on my N7 and love it.

Question: when the time comes for the next update for the August security patches, what is the procedure for a dirty flash so that I don't lose any existing data? Does GApps need to be re-flashed? I assume ElementalX kernel will need a re-flash (there's a new version of it anyway)
[Nexus 7 (2013) Android Development] buffal0b1ll:
There probably won't be a August update for N. Beans has already moved all N branch source to Pure Nexus Project Legacy.

But to answer your question...

In general, ROMs that include backuptool add-on script like PN don't require reflash Gapps as long as system is not wiped before dirty flashing. The add-on script backs up Gapps before wiping and writing the new system image, then restores them. You'd wipe cache and dalvik only in this scenario.

If you wipe system, cache, and dalvik that's also dirty, but you'll need to flash ROM, GAPPS, and custom kernel in this scenario.

Not wiping data means that all your user installed apps and saved system settings will persist. Often this is problematic when ROM changes will conflict with old system settings data.

A clean flash is advanced wipe System, data, cache, and dalvik. Don't let anyone tell you that the factory reset wipe option is good enough for a clean flash (it only wipes data, cache, and dalvik).

In general, you need to reflash your custom kernel (it will usually have a monthly update you want to check for too) when dirty or clean flashing because stock boot image will overwrite it when flashing the ROM zip.

And lastly, in general it's best to clean flash so that if problems arise you can report them without being berated for dirty flashing and bringing the problems upon yourself.
[Nexus 7 (2013) Android Development] sirxdroid:
Thanks for the detailed explanation.

Clean flash is nice, except when the kids scream they lost their games :) I tried TiBu before and didn't work very well with saving game progress, perhaps I just didn't know how to use it.

So PN is moving to Oreo? Does that mean we'll see a PN Oreo for both N7 and N9?

Thanks again!

---------- Post added at 03:54 PM ---------- Previous post was at 03:33 PM ----------

How do we get the Play Store to update to the version that includes Play Protect? Do we need a new version of Gapps or does it depend on Google pushing an update?
[Nexus 7 (2013) Android Development] buffal0b1ll:
Too early to say.

Google should push. Apkmirror if you don't wanna wait.
[Nexus 7 (2013) Android Development] buffal0b1ll:
Play Protect is in Settings>Google>Security by the way.
[Nexus 7 (2013) Android Development] sirxdroid:
It is indeed, and disabled by default it seems. I'm used to being able to initiate a scan from the Play Store directly, I suppose a newer Play Store apk may be needed for that.
[Nexus 7 (2013) Android Development] buffal0b1ll:
I typically update Play Store as soon as new versions hit apkmirror. I've never seen nor heard of Play Store integrated Play Protect functionality. But I'd never enabled Play Protect or given it much notice either.

I'd start googling if I were you.
[Nexus 7 (2013) Android Development] sirxdroid:
http://www.androidpolice.com/2017/08/09/play-protects-scanning-starts-showing-users-play-store/

Needs a new Play Store apk. No big deal as long as I now know how to enable it via Settings.

Thanks for being so responsive!
[Nexus 7 (2013) Android Development] sirxdroid:
Help my kids please :)

Having a problem with the game NFS Most Wanted. On this ROM the game starts then it gets stuck in Update Check and eventually it returns error code 5003. I thought it was a temporary problem with the EA servers but it can't be that they've been down for 3 days. Something else is going on. Any ideas? Any experience with EA games? This game used to work OK on the stock ROM.

Happening on both N7 and N9, both on the same PureNexus. There must be something that I'm missing.
[Nexus 7 (2013) Android Development] Woody:
Might want to check the storage space and make sure there is enough.

Also, this: http://answers.ea.com/t5/Need-for-S...for-speed-most-wanted-error-5003/td-p/3737617

Using an AdBlocker? Might want to whitelist the site that the download is pulling from. This happened on one of my sons games and I whitelisted it in AdAway and it worked fine. If you don't want to whitelist, just turn off your ad blocker, download and then turn it back on. I've done that too.
[Nexus 7 (2013) Android Development] ThanhNguyenn:
tks team
[Nexus 7 (2013) Android Development] sirxdroid:
Unfortunately I tried all of the above without any luck. There's about 14GB free space which should be plenty. Tried with Adaway off. The answers at EA are not very useful.

It's probably that I'm missing some setting or some framework. I just run a very barebones install of PureNexus, no apps at all, just a few games for the kids. I tried installing Google Play Games but doesn't make a difference.

I also looked at "adb logcat" and don't see anything unusual, no exceptions.
[Nexus 7 (2013) Android Development] nigelhealy:
I'm on the current PN 7/25 and just now ordered a $10 ebay replacement battery as still, 4 years later, the N7 2013 is good enough to not make me go with latest tablets.

Thinking about when PN O is eventually released, do we need to do also a wipe of internal storage, then ADB push the ROM Gapps Magisk to fully wipe? I find wiping data leaves a lot behind of app data, folders that apps create under /sdcard
[Nexus 7 (2013) Android Development] L.F.B.:
Ive tried to flash viper4a.r.i.s.e. but I think this rom has no. Support. Thats right?

It would ask much to add a.r.i.s.e support?

Thanks in advance.
[Nexus 7 (2013) Android Development] buffal0b1ll:
There's probably a way to get v4a to work on this ROM, but I don't know it. My best advice is to see what viper, arise, v4a brings back in a search on LOS rom for flo. Then try whatever they're saying works. Getting viper to work is always a journey, and IMO never really worth the trouble.

No, I won't be making any changes to the ROM to help support v4a.
[Nexus 7 (2013) Android Development] OSully:
Do you intend to release this with 8.0?
[Nexus 7 (2013) Android Development] Pete02:
I don't think it's the rom. The tablet doesn't have enough space available on it to install V4A if I'm not mistaken. At least I remember that problem with older versions of V4A. Best to check with the Viper forum on it but I'm pretty sure there's a solution.

---------- Post added at 11:16 PM ---------- Previous post was at 11:10 PM ----------

When Pure Nexus releases an 8.0 rom it's possible that buffal0b1ll will port it for us but since it's frowned upon to ask for eta's it's probably best to just sit and keep our fingers crossed. :fingers-crossed:
[Nexus 7 (2013) Android Development] OSully:
Thanks. Wasn't asking when, was asking if.
[Nexus 7 (2013) Android Development] buffal0b1ll:
It's too early to say.
[Nexus 7 (2013) Android Development] 777.300:
Viper4Arise working fine here on my N7 and N9 using this great ROM.

I am using this version: ARISE+Magnum+Opus+20170506.

You have to place arise_customize.prop file, found within the downloded zip, in your main storage folder, configure it and than flash the ARISE+Magnum+Opus+20170506.zip via TWRP.

Working flawlessly, couldn't live without it.

https://xdaforums.com/showthread.php?t=3379709
[Nexus 7 (2013) Android Development] Spyros_V_S:
Thank you, already flashed and it works like a charm!!!
[Nexus 7 (2013) Android Development] buffal0b1ll:
[MENTION=7890918]boom1982[/MENTION] [MENTION=4160466]manfio[/MENTION]

New Build is up. The 03/22/2017 is identical to the 03/20/2017, except it doesn't include Chrome, Hangouts, or Photos in its included Gapps. This frees up about 100MB in the system partition.

ROM Downloads: https://www.androidfilehost.com/?w=files&flid=164137

-03/22/2017 build includes all the Pixel Gapps that the OFFICIAL Pure Nexus 3/17 builds include, EXCEPT Google Camera, Hangouts, Chrome, and Photos.

-03/20/2017 build includes all the Pixel Gapps that the OFFICIAL Pure Nexus 3/17 builds include, EXCEPT Google Camera.
[Nexus 7 (2013) Android Development] lollyjay:
I installed the Citi mobile app and get error message: Your Android System WebView is out of date....

WebView is installed and up to date. Any idea? I can supply log if necessary. Other banking apps are working
[Nexus 7 (2013) Android Development] buffal0b1ll:
ROM Uses Chrome Stable Webview.

Try this to see if Citi will work, and don't be surprised if there's side effects.

Install Android System Webview from PlayStore

Settings>Developer Options>Webview implementation>Google Webview

Settings>Apps>CitiMobile>Storage>Clear Data

Reboot
[Nexus 7 (2013) Android Development] lollyjay:
Well I had done that but I forgot to reboot (duh) :eek:
[Nexus 7 (2013) Android Development] manfio:
Thank you

Gone try when im back home
[Nexus 7 (2013) Android Development] buffal0b1ll:
I only advised a reboot because I did not know if it would matter or not and it was safer advice just to say to do it.

I am not trying to set a precedent here for trying to debug every user app that has nothing to do with whether or not the ROM is working, but since I am a CitiMobile user on my phone and I was curious, I installed it on my Flo and I had no problem at all logging in with the stock Google chrome webview and browsing around in the app.
[Nexus 7 (2013) Android Development] buffal0b1ll:
Warning: This is gonna be a TLDR if you're not following what has been going back and forth with [MENTION=4762414]lollyjay[/MENTION] and I with regards to CitiMobile not liking the ROM webview. The good news is that it works on the new 03/22/2017 slimmed down zip I built today.

So, [MENTION=4762414]lollyjay[/MENTION], it dawned on me after I posted that CitiMobile was working fine with Chrome Webview on my device that you and I were on different ROM versions (you 3/20 with Chrome as system app and me on 3/22 with Chrome as a user app). I flashed back to 3/20 and replicated your problem with CitiMobile complaining about webview version on first launch. This suggests to me that the Citi app needs an update to be compatible with a system based Chrome Stable Webview. It seems to me you have a few options to get CitiMobile working, as it works fine with either AOSP Android System Webview or the Chrome as-a-user-app's Chrome Stable Webview

1. On your current setup, Settings>Apps>Chrome uninstall updates and then Disable on your current ROM. Then open CitiMobile (you'll notice if you look around in Dev settings and Settings>Apps that AOSP Android System Webview will autoenable and auto disable itself when you disable and enable system app Chrome BTW)

2. On your current setup, uninstall updates to Chrome app and then with a root explorer delete the system/apps/Chrome directory. Reboot and install Chrome as a user app if you still want to have it.

3. On your current setup uninstall updates to Chrome, Hangouts, and Photos if they exist. Dirty flash 3/22 zip plus whatever else you usually flash. Installl Chrome, Hangouts, and Photos as user apps after system boots if you want them.

4. Clean flash 3/22 zip
[Nexus 7 (2013) Android Development] lollyjay:
Updated to the 22/03 build after making the changes. All's well with Citi Mobile app.
[Nexus 7 (2013) Android Development] Semtronix:
I'd love to give this ROM a go, but when I got to AFH, it says no mirrors found for either version you've posted :(

Annnnnd now they're there.
[Nexus 7 (2013) Android Development] buffal0b1ll:
Good. I was afraid you broke AFH:silly:
[Nexus 7 (2013) Android Development] lollyjay:
Working well for me. It seems to be very fast for such old (2013) technology
[Nexus 7 (2013) Android Development] DeeditTotoi:
Tq dev for bring this rom to flo.. Smooth and stable..tq so much
[Nexus 7 (2013) Android Development] hachiroku:
runs awesome without hickup so far. this ROM has given this old tablet a new breath of fresh air. thank you for bringing this to us.
[Nexus 7 (2013) Android Development] binuralka:
please upload a build without gapps ... so it is pure (as it was meant to be)
[Nexus 7 (2013) Android Development] buffal0b1ll:
Not going to fork the ROM from beans source. It is already as it is meant to be.
[Nexus 7 (2013) Android Development] hachiroku:
use titanium backup to remove the app
[Nexus 7 (2013) Android Development] kpeters59:
Thanks for this ROM!

It's the ONLY 7.x.x that I can text with Hangouts and my Google Voice number.

Plus, I'm a big fan of Pure Nexus!

-Kyle
[Nexus 7 (2013) Android Development] emiliobadillio:
This runs really well. I'm very happy with the speed, performance, and features. I had the official Pure Nexus Android 6.1 and it was good, but was really hoping to have the new Android 7 features. This makes me so happy. Thank you!
[Nexus 7 (2013) Android Development] buffal0b1ll:
I'm glad you like it. I must give credit where credit is due... the source and trees devs I thanked in the OP are truly the ones that deserve the most thanks.
[Nexus 7 (2013) Android Development] Pete02:
Sorry for my mis-wording there. I wasn't implying that you were asking for an eta. I was just trying to point out that since a PN 8.0 isn't out yet it would be hard to know so the most we can do at this point is hope for the best.
[Nexus 7 (2013) Android Development] bcote311:
The way I get Viper to work is:

1. Rename "audio_effects.conf" file under vendor/etc to "audio_effects.conf.bak"

2. Delete MusicFX file

3. Set kernel to permissive mode

Works every time
[Nexus 7 (2013) Android Development] tinyturtles:
Does this ridiculous awake time occur for anyone else? Anyone know how to fix it?
[Nexus 7 (2013) Android Development] L.F.B.:
I got it how to make viper4arise work!

Just used open gapps-config file to remove a lot of system apps and the system space jump to 240mb free space!

Also used titanium bk to remove another system bloats...

Thats gave me enough system space to flash viper4arise, and its working fine! ?
[Nexus 7 (2013) Android Development] oldman_58:
[MENTION=4831195]buffal0b1ll[/MENTION] Thank you very much for this build. I have missed Pure Nexus. Excellent work.
[Nexus 7 (2013) Android Development] shams6:
Any update.... Using purenexus last 6month.
[Nexus 7 (2013) Android Development] St0neC0ld:
Hey guys. Do you know any workaround for netflix?

Streams works fine. But when i play downloaded files, i got an error :(
[Nexus 7 (2013) Android Development] nigelhealy:
Ditto, it detects the custom ROM nature of Pure Nexus. I have a OnePlus 3T it works fine, a Pixel C works fine both them are stock ROMs with Magisk.

I have a Nexus 10 with Pure Nexus and Netflix says imcompatible and points me to an old version.
[Nexus 7 (2013) Android Development] Pete02:
I use the recommended Netflix version 4.8.5 from the OP and my Netflix works fine.

Edit, just reread your post. Sorry for the noise but I just stream not download.
[Nexus 7 (2013) Android Development] Ganesh A:
ROM download link? says backend error
[Nexus 7 (2013) Android Development] robthom:
I tried all the Nougat roms on the front page, and slim and CR and Commotio are all very good, but this one my fave.

Its small, its got BASE functions that I want, it doesn't have ones that I dont need, it seems stable as can be, it hits all the right notes.

Thank you.
[Nexus 7 (2013) Android Development] Pete02:
Maybe they had a glitch before cause it's working for me now.
[Nexus 7 (2013) Android Development] buffal0b1ll:
Blame AFH. Keep trying.
[Nexus 7 (2013) Android Development] jfive74:
Is your viper working with mixcloud, soundcloud or other? Only works for google music and Dolby doesn't work. Froze music fx and rename audio.conf
[Nexus 7 (2013) Android Development] cdnron:
[MENTION=4831195]buffal0b1ll[/MENTION] - I was going to install this ROM but I happened upon your GZOSP ROM on AFH which seems to be what you're focused on, as it's much more current than Pure Nexus. So far I am loving GZOSP. The only issue I've found so far is the camera app doesn't work (but I don't really use the camera on my tablet anyway so that's not a big deal). I didn't see an XDA listing for this ROM though. Is that coming? Thanks in advance!
[Nexus 7 (2013) Android Development] buffal0b1ll:
Yeah HAL1 is still broken on Oreo so camera not working on that test build you stalked of off AFH is expected.
[Nexus 7 (2013) Android Development] MikeTheTechSavvy:
Hey guys, here's a video review and a quick installation guide I've done on the latest Pure Nexus build for the N7 2013. I really think this is the best Nougat ROM for this tablet. You should watch it if you're thinking about pulling the trigger and you're not sure how it looks like or you'd like to find out more about it. Enjoy!

https://youtu.be/pxh5rjveLx0

Thanks, [MENTION=4831195]buffal0b1ll[/MENTION] , for developing and sharing it with all of us!
[Nexus 7 (2013) Android Development] kevk60:
Rom is great.

Went ahead and decided to flash this rom on my n7 2013. Everything went great. Actually got viper4android to work along with substratum. Tablet is awesome again. Thanks for your work.
[Nexus 7 (2013) Android Development] JT1510365:
how did you get viper to work
[Nexus 7 (2013) Android Development] skooter32:
Hi a flashed this rom and setup wizard fails a delete it and the screen goes blank any ideas
[Nexus 7 (2013) Android Development] kevk60:
I used this version of viper. I extracted then installed the "fix" version apk. I also froze Music fx with tb and removed the audio.effects.conf file from vendor/etc. It worked. https://drive.google.com/file/d/1WIKM9PL-gdLrWWxUjsuGJp_AN1T16CER/view?usp=drivesdk