yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] Coronado is dead:
Forgive me if this is answered elsewhere, I did search the thread :)

YouTube in the app is limited to 720p for me, no 1080p option shows up. Is there a specific version of the YouTube app i need to grab or a setting I missed?

On the latest version, WiFi model.

Thanks!
[Nexus 7 (2013) Android Development] buffal0b1ll:
Link me a video you think you should see a 1080p option in that you don't see it.

I just searched up 1080p in YouTube search, played a Transformers trailer and switched from 720 to 1080p no problems.

Having said all that, I'd never have noticed the difference between if the default was 360p TBH. Just be glad the Flo still works.
[Nexus 7 (2013) Android Development] Coronado is dead:
OMG, it was 3 separate videos listed as 1080p that were actually 720p. Tried a 4th and it works fine. Verified the 3 crap ones on my desktop now that I am home. Completely false alarm :/
[Nexus 7 (2013) Android Development] buffal0b1ll:
Start over. Don't use open Gapps. Use beans mini. Hundreds of others have flashed this without issue.
[Nexus 7 (2013) Android Development] pi0:
Thanks, [MENTION=4831195]buffal0b1ll[/MENTION] for the quick tip. Flashed again and things work just awesome :p Suggest stating that Gapps is REQUIRED for fresh installs to :) Keep working your awesome job :)
[Nexus 7 (2013) Android Development] buffal0b1ll:
Great. Glad you like.

OP clearly states to Use Beans Mini gapps and provides the link. If any users of this ROM are tin-foil-hat Google cord cutters, then they're crafty enough to know the right Gapps-less hack to workaround Setup Wizard FC on their own.
[Nexus 7 (2013) Android Development] iason747:
Hi there, so i flashed this Rom about a Week ago and really love it. The only problem is that GPS isnt working. It seems like it searches for satilites to connect to but isnt able to connect to them. Any ideas?
[Nexus 7 (2013) Android Development] Pete02:
Not really. With high accuracy on it took less than a minute and I locked into 6/20 satellites.
[Nexus 7 (2013) Android Development] JassyNL:
I just installed this ROM, coming from the original Marshmallow and I just like to say: WOW!! This is a very good one. No bugs, fast as Marshmallow but on the newest base so future proof. Excellent work!
[Nexus 7 (2013) Android Development] xaforib:
I'm having sound distortion while using nougat and USB DAC. It's not static, and it's not present on marshmallow roms.

And idea how to diagnose it? Is it possible to use marshmallow driver?

It happens on three nougat roms, with stock, Glitch, or ElementalX.
[Nexus 7 (2013) Android Development] buffal0b1ll:
No idea. I don't have that hardware so I can't even try to replicate it or debug. Sorry.
[Nexus 7 (2013) Android Development] arealcoolhand:
Using GPS Status shows I'm connecting to satellites okay (8 of 19) but was having trouble calibrating the compass. Had no trouble on my N6 or N4 so couldn't understand what was different about my N7. Then I remembered the case is magnetic. Doh! Popped it off and had no trouble calibrating it in either GPS Status or Google Maps.
[Nexus 7 (2013) Android Development] Djeypi:
Hello all!

I have a question:

Do I have to relock the bootloader?
[Nexus 7 (2013) Android Development] buffal0b1ll:
No
[Nexus 7 (2013) Android Development] daitalos:
google camera not working for me (from Link of OP) In each build (I have black screen) but working very well the DSLR app from playstore !!

It is not a serious problem for me,I do not use camera in Flo, I just mention it Because it seems strange :)

Generally, Rom working very correct & fast on my device

Thanks & sry for english
[Nexus 7 (2013) Android Development] buffal0b1ll:
That is very strange. That camera is the first thing I check after each new build boots. I'm glad I don't have your device:)
[Nexus 7 (2013) Android Development] JassyNL:
I downloaded the Google camera from the PlayStore and that one is working very well. You might give that a try.
[Nexus 7 (2013) Android Development] daitalos:
Not working for me..
[Nexus 7 (2013) Android Development] Nomad1600:
For what little camera use needed, Open Camera is free and works. Available in Play Store.
[Nexus 7 (2013) Android Development] buffal0b1ll:
Yes it does, but Open Camera wouldn't work on this build if the Google Camera suggested in the OP didn't work. The camera linked in the OP works.
[Nexus 7 (2013) Android Development] binuralka:
Hi, thank you for your work dev! My device however does not react to rotation with this ROM. On purenexus6.0.1 it works without a problem.

So I did one more clean install of 7.1.2 still no rotation reaction, then rooted it and installed parrotMod - did a reboot and still without a positive result :( I am hopeless...
[Nexus 7 (2013) Android Development] buffal0b1ll:
Clean the pipes with most recent Google factory image (confirm rotation working on stock) and then start over upgrading to 7.1.2. Hundreds of downloads and you're the only one who's reported a rotation issue.

Also, I'm wary of what other mods you may have added that could've broken rotation. You're clean with just ROM and beans mini gapps and clean wiped data partition without a bunch of restored apps, right?
[Nexus 7 (2013) Android Development] binuralka:
I am clean as much as its possible. I do not go for any mods, even any recovery tools, I do not install gapps at all. I just wipe everything apart from internal storage and then flash the ROM.

gonna try to clean the pipes!
[Nexus 7 (2013) Android Development] Woody:
Fwiw, I have 4 N7's running this and 3 of them have/had the rotation bug. Had to do the hardware fix on all 3, 2 of which have it reoccurring, 1 is still good. It's not ROM related, but the N7 has a wonky gyroscope due to its age.

HW fix is easy. Hardest part is finding the right sized paper/board/foam that's not too thick. I found that those 3M picture hangers strips work the best. Get the heavy duty ones, as they afford more girth and you won't have to double up on the standard ones (Yikes!! Thank goodness I'm talking about foam and not something else.:silly:)

Edit: But a good pipe cleaning would do it some justice too. Ahh! There I go again.
[Nexus 7 (2013) Android Development] buffal0b1ll:
This is the fix you're talking about, [MENTION=3200478]Woody[/MENTION] ?

[youtube]LLCAeBe2hVU[/youtube]
[Nexus 7 (2013) Android Development] Woody:
Yes, that's the one. There is also a Sensor apk in the Play Store that will tell you if your gyro is working properly, but it's pretty obvious when it is and isn't. I have it installed on my N7 at home, so not sure what it's name is right now.
[Nexus 7 (2013) Android Development] dt0807:
I had the same problem, when rotation would stop and require a reboot to work again. But as mentioned, it turned out to be a hardware issue (particularly with the cable). That fix is worth trying if you have the time

Honestly, I originally thought the guy in that video was selling snake oil until I tried it for myself a while ago, and I've haven't had any rotation issues since. Drove me crazy because my sensors worked perfectly fine, but I think the slightly movement in that ribbon cable seemed to disrupt the auto-rotation until reboot
[Nexus 7 (2013) Android Development] Sindee75:
Hi folks. My nexus 7 2013 is stuck at the boot animation on marshmallow stock, 6.0.1, build mob30x.

If I install this custom Rom will it boot normally? I tried lineage but it also booted stuck in boot animation. I'm hoping a custom Rom will get me out of this stuck at boot animation. Btw, ALL stock images from 5.0.1 and up get stuck in boot animation. Only 4.4.4 and below does NOT get stuck at boot animation. This problem has been driving me nuts for way too long ? please advice. Thank you, Cindy
[Nexus 7 (2013) Android Development] buffal0b1ll:
There's no magic pill to get out of your jam, which we really have no idea how you got to. I have no idea if this ROM will boot with a poke and hope attempt.

Recommend fastboot flashall official most recent Google Factory Image (Is this where you are right now?). Then you'll have a clean slate that we can use as a point of reference.

It's advised to boot once (don't really need to sign in) before continuing but if you can't then press on anyway.

Then fastboot flash most recent TWRP.

Then flash the ROM, Gapps, etc from the OP.
[Nexus 7 (2013) Android Development] Sindee75:
Thank you. I am on the latest stock rom 6.0.1 build mob30x from a recent flash-all from google factory images. What got me into this pickle was flashing down to 4.4.4 as a test for a touch screen issue. Then, all OTA after 4.4.4 or stock flash all after 4.4.4 gets me caught in the boot animation.

I am downloading purenexus now and bean gapps. Then will flash via twrp311.

Do you recommend full wipe except internal storage first? System, delvacke, cache, data? Or do you recommend factory reset or formatting every partition prior to Rom flashing? Thanks!
[Nexus 7 (2013) Android Development] buffal0b1ll:
Interesting pickle history. Perhaps your bootloader isn't updating? What bootloader version are you on now? Should be FLO-04.08

If it isn't you can extract the bootloader image from the factory image and fastboot flash it manually.

To answer your last questiuon, I always recommend advaced wiping all except internal storage (a true clean flash), but if you can't boot, you may not even have data/media (aka Internal Storage, aka sdcard) set up with it's specially formatted Download, Music, DCIM, etc folders anyway. Actually if you have an OTG I'd recommend flashing the zips from it. Otherwise, just move the rom and gapps zips to data/sdcard after wiping data and flash away.

Fingers crossed.
[Nexus 7 (2013) Android Development] Sindee75:
Thanks for quick reply. Was waiting to proceed. I do have bootloader .04.08 loaded. Will do recommend wipes. What I do is install twrp, then adb sideload the Rom and gapps to /sdcard/ then install the zips via twrp from sdcard folder. I even removed the bootanimation file under system/bin to see if that helps. It just hangs without an animation. Nice try though, lol! So yes, I do have data, media, etc.

Will proceed and keep you posted. Thank you!
[Nexus 7 (2013) Android Development] buffal0b1ll:
"adb sideload" ???? You mean adb push just moving files, right? adb push and pull are good skills to know, but MTP enabled in modern TWRP kinda makes them obsolete.
[Nexus 7 (2013) Android Development] Sindee75:
yes I meant adb push, lol... I have installed rom, now time for beangapps....
[Nexus 7 (2013) Android Development] buffal0b1ll:
Fingers still crossed...
[Nexus 7 (2013) Android Development] Sindee75:
both rom and beangapps installed with NO errors. restarted system, I am now at purenexus boot animation with 4 spinning dots. I have a feeling I will be stuck here too. How long shall I wait at this point?

Ill jump in the shower while waiting.....
[Nexus 7 (2013) Android Development] buffal0b1ll:
Shouldn't take more than 5min but I'd give it 10 before deciding it doesn't work.

If it doesn't I'd try going back down to 4.4.4 (that's the only one you can get to boot right?), then boot once without looging in.

Then fastboot flash bootloader <04.08 img> extracted from newest factory image

Then fastboot flash recovery <newest official TWRP img>

Then wipe system, data, cache, dalvik and flash ROM and Gapps
[Nexus 7 (2013) Android Development] Sindee75:
Anything 4.4.4 or below works. Kitkat or JB. I had even tried flashing 4.4.4 bootloader Flo 04.02 over 6.0.1 stock bootliader Flo 04.08 since we know 04.02 bootloader works. No success that way, just gives me a different problem, the dead android laying down.

I am going back to 4.4.4 now. Then you want me to flash 04.08 (the current non working one) over it? Then proceed with Rom and bean gapps? Just clarifying.

Need to run errands. Then will finish. I'll be back....
[Nexus 7 (2013) Android Development] buffal0b1ll:
Delete
[Nexus 7 (2013) Android Development] buffal0b1ll:
Yeah that's what I was suggesting.
[Nexus 7 (2013) Android Development] buffal0b1ll:
If you haven't already downgraded to 4.4.4 and run thru trying my last suggestion, you may wanna wait and try these other ideas that have come to mind.

The only time I've remotely seen anything that resembles what's happening to you kinda happened to me on a grouper once. I chalked it up to some hardware not being able to handle some software updates and never figured out why. For me whenever I tried to update this grouper to Lollipop, it'd boot but the screen would go black right after the boot animation finished (I could press hardware butttons and hear the screenshot sound, so I know it actually did boot). The only solution for me was to downgrade back to Jellybean;-(

Anyhow, here's some other ideas to try:

-Maybe flashing a custom kernel (I like EX) can get it over the "won't boot" hump.

-Maybe giving flashing just the ROM (no gapps) can get it over the "won't boot" hump.

-Maybe a non AOSP based ROM like LineageOS (CM base), Telsa (GZOSP - more CM CAF stuff), or Tipsy (Slim based) might get her to boot.
[Nexus 7 (2013) Android Development] Sindee75:
Ok. I have flashed flo-04-08 over kitkat 4.4.4s bootloader 04.02.

Did wipes. Flashed twrp and Rom, without gapps. I have booted and stuck at the 4 dots again. No sense in flashing beangapps not being able to get past animation? Right?

As original post said, I have tried lineage OS, Nougatella 14.1, and that also gets stuck at boot animation.

Looks like your last suggestion is install a custom kernel, but I've never done that. I'm not seeing where or how to flash it. Is it this one?

https://xdaforums.com/showthread.php?t=2389022

I have read some owners of nexus 7 2013 got soft bricked and stuck in boot loops or boot animations after the lollipop update.

My boot animation did get stuck when I downgraded to kitkat 4.4.4 and allowed the OTA updates. Once it went to lollipop 5.0.2 it went into boot animation. Hence, all of my troubles began. I have flashed nearly every Rom from Google's developers firmware images. All of them put me in a boot animation except for 4.4.4 and below.

The reported owners that had a boot issue after lollipop update ended up replacing their motherboards to fix flash memory to solve problem. Could this be my case? If so, why does it boot ok with kitkat and jellybean.?

I would even go back to kitkat but google play and google services constantly crash, even when I try different google play and services Apks.

So, I'm stuck. I just want to make it usable ? I could cry. This was the expensive 32gb model and just had a new digitizer installed.. ?
[Nexus 7 (2013) Android Development] buffal0b1ll:
Yes. That's the custom kernel I prefer. Just flash it's zip after the ROM and it'll replace the stock rom boot.img with the custom kernel boot.img. EX has an aroma installer so just tick next next next yes agree next to accept the default config and reboot to system.

Maybe your device has the same problem that those Lollipop OTA brick RMA people had. Seems like your experience is a positive correlation.
[Nexus 7 (2013) Android Development] juliatan:
Have been trying many most recent N roms lately on this device. I was about to give up concerning Nougat on my N7-13 Flo. LineageOS official especially but also unofficial such unstable bugfests. LineageOS based Resurrection Remix absurdly sssssllllloooooowwwww und very unstable too. CrDroid was least bad by far but only hardly sufficient for daily use. All at best mediocre idle battery life, but most terrible idle drain.

Was about to go back to stock 6.0.1 without compatible Substratum themes left. Then came along this Pure Nexus. Absolutely gold. Don't think Google could have done a better job. Performance is good, so far no bugs found after a week and hardly any idle battery drain. (I use Greenify with instant doze (+ on the go) and Leandroid for blocking mostly any non media streaming app from using internet with screen off).

Only issue I had was one to me important app (EDS with Veracrypt r/w mounting) refused to work with systemless root (both Magisk and SuperSu) on this rom. Other roms and devices that app no issue with systemless root. So using system based SuperSu now and missing the Magisk module goodies.

But most important is with this Pure Nexus finally a stable worthwhile custom N rom on my old Flo. Wauw are the other LineageOS (based) roms all bad. Very bad.

Thanks!!!
[Nexus 7 (2013) Android Development] ranaxda200:
Need to say this only this PN rom still survives our beloved Tablet since years and more. Keep on dev, beans and more users. We all love you guys :highfive:
[Nexus 7 (2013) Android Development] buffal0b1ll:
New 07/25/2017 build is up. Updates to OP copied below as usual.

READ EVERYTHING HERE BEFORE FLASHING:

-Updating to TWRP 3.1.1-0 is recommended

-Use BeansGapps Mini https://www.androidfilehost.com/?w=files&flid=171927

-Not prerooted. SuperSU stable or Magisk stable recommended

-No camera included. Google Camera 2.5.052 recommended http://www.apkmirror.com/apk/google-inc/camera/camera-2-5-052-release/

-As of the 4/23 release the ro.opa.eligible_device=true is no longer in the system/build.prop.

This will cause the Google App to use Google Now interface instead of Google Assistant. If you want to use Google Assistant use the Get Assistant - Root app on the PlayStore (choose NEW method when prompted) OR if you use Magisk theres a Google Assistant Enabler module for this.

-Want a Pixel Launcher that allows swipe up to App Drawer in landscape? Sideload the Android O Pixel Launcher from apkmirror.com http://www.apkmirror.com/apk/google...ixel-launcher-o-3952143-android-apk-download/

-Netflix casts fine but throws an Error on playback. Sideload Netflix 4.8.5 from apkmirror.com OR use the zipaligned Netflix4.8.5-signed.apk in the ROM Download folder https://www.androidfilehost.com/?fid=529152257862715472 . The zipaligned apk will never show up as needing an update on PlayStore.

-Features? Updates? Read the changelog below.

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

PureNexus Changelog: https://docs.google.com/document/d/1ROCTINpYR2M2QZ-uzErZSNK8gjIm_bXS6sXL83YePd0/pub

Source Code: https://github.com/PureNexusProject
[Nexus 7 (2013) Android Development] loadie:
Well that was quick. dirty and all is well. fantastic work, thanks
[Nexus 7 (2013) Android Development] daitalos:
you did excellent work bro! Rom works very stable & fast (I use elemental kernel)

no problems with new update & mini beans Jul 26 package

only somes substratum themes gives errors ( not all ) Thanks & sry for english !
[Nexus 7 (2013) Android Development] buffal0b1ll:
Thanks.

In regards to Substratum....

You clean flashed? You fresh installed substratum (not a TiBu restore)? You rebooted once after installing Substratum? You using themes updated to plugin 10.0.0?

You dirty flashed? You tried uninstalling and reinstalling Substratum? You rebooted once since installing Substratum? You using themes updated to plugin 10.0.0?
[Nexus 7 (2013) Android Development] manfio:
awesome

super fast update :D
[Nexus 7 (2013) Android Development] buffal0b1ll:
Substratum updated twice on PlayStore today. Make sure you install the newest version too.
[Nexus 7 (2013) Android Development] daitalos:
Yes I know & I tried everything... It's a matter of substratum ..Every day there is 1-2 updates ! Lol

Thanks..
[Nexus 7 (2013) Android Development] sami8519:
Thank you for this great work. Unfortunately I am not able to sign in to my google account. I get the message "unable to communicate with google servers. Try again later. Tried many times with different account but same result.
[Nexus 7 (2013) Android Development] buffal0b1ll:
Verify the WiFi you're using is good with another device?

Try a different WiFi?

Skip thru setup and add account manually thru settings? Start over from scratch?

Best I can do with the lack of detail (what did you wipe, what zips did you flash, what else can you tell me about the WiFi you're on) you've provided.
[Nexus 7 (2013) Android Development] sami8519:
Thanks for your reply. I started from scratch with the 07-26 update.zip. Installed it through TWRP after doing a full wipeout in TWRP. Wifi works just fine, even tried another internet connection same error message. I actually did not notice any setup after flashing the zip. I was taken right away to the home screen. I then installed Googleapps beans mini zip. I am noticing that message "google play service keeps stopping" keeps occuring every few minutes.

---------- Post added at 09:55 AM ---------- Previous post was at 09:40 AM ----------

I did factory reset from within the rom and now I am met by the setup, everything works as intended to be :) Thanks a lot.
[Nexus 7 (2013) Android Development] iason747:
Yeah, the problem was that you didn't flash the rom and gapps together the first time. I assume that you flashed the rom, rebooted and then flashed the gapps.
[Nexus 7 (2013) Android Development] sami8519:
Yeah I did exactly like you said.
[Nexus 7 (2013) Android Development] buffal0b1ll:
Start over. Advanced Wipe cache, dalvik, system, data. Flash ROM and beans mini gapps before first boot. Then you'll be in setup wizard and things should work
[Nexus 7 (2013) Android Development] NIK126:
AOSP keyboard

Post pls AOSP keyboard from previos build of ROM. Google keyboard is slow.
[Nexus 7 (2013) Android Development] iason747:
Gboard actually runs pretty fast for me, the only problem I have with it is, that I can't access the settings of Gboard. It will always crash.
[Nexus 7 (2013) Android Development] buffal0b1ll:
Can't replicate. Gboard Settings works fine here.

Lemme guess, you didn't wipe data and you flashed the new gapps after flashing ROM.
[Nexus 7 (2013) Android Development] buffal0b1ll:
It's not as simple as posting an apk here (it's a system app with associated libs and appropriately set permissions). Revert to previous build if you like AOSP keyboard better.
[Nexus 7 (2013) Android Development] L.F.B.:
Tanks buffal0b1ll just dirty flashed all smooth here!

It was nice...I think the last masgisk have survival mode... After flashing rom... then automatic magisk was flashed! ?
[Nexus 7 (2013) Android Development] sami8519:
Is there a minimal clean rom for Nexus 5 similar to this rom?
[Nexus 7 (2013) Android Development] ranaxda200:
Wrong thread bro. Hope you'll find one on N5 threads
[Nexus 7 (2013) Android Development] daitalos:
Yes I can confirm google keyboard (settings) are closing continuously (keyboard works ,settings is the problem & for me)..
[Nexus 7 (2013) Android Development] buffal0b1ll:
Can't replicate. Gboard Settings works fine here.

Lemme guess, you didn't wipe data and you flashed the new gapps after flashing ROM.

Or maybe theme related?
[Nexus 7 (2013) Android Development] iason747:
Seems to be an issue with Gboard reading old files from aosp keyboard. The only workaround would be a complete data wipe
[Nexus 7 (2013) Android Development] buffal0b1ll:
Where'd you come up with that?

Was I right about you not wiping data and flashing 7-25 gapps after the ROM or not?
[Nexus 7 (2013) Android Development] daitalos:
Thanks for reply...I did clean flash & flashing gapps immediately after Rom..

anyway Gboard works,(the problem for me is only the settings) & now I use & another Kboard..So,no problem
[Nexus 7 (2013) Android Development] iason747:
Yepp. https://github.com/opengapps/aosp_build/issues/116
[Nexus 7 (2013) Android Development] buffal0b1ll:
So you used Open Gapps or the recommenced PN Gapps? It'd be much easier to help you if you'd provide more details about what you wiped and what you flashed and what you had on there already if you'd dirty flashed.

Assuming you had June PN with June PN mini Gapps on the beforehand....

And if you don't want to wipe data to fix your gboard settings problem you could try this.

-Restore your June pn nandroid.

-Wipe cache and dalvik only.

-Flash July ROM with no Gapps (the backuptool addon script will backup and restore the Gapps that are on there when you flash the ROM, as long as you don't wipe system beforehand)