• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Nexus 6P update to Android 8.0 OREO

Rob

Galaxy S20 Ultra
News Moderator
Administrator
Have you updated your Nexus 6P to Android OREO? How's it going for you so far?

I was already on the Android 8.0 Beta and after this official update, which I got as an OTA yesterday, everything seems to be working perfectly fine. I'm not overly impressed with anything, but definitely satisfied!
 
I'm still waiting for the release OTA to appear on my DP4-equipped 6P. I'll probably just flash the factory images once those get finalized; I understand that the images posted yesterday are actually several weeks out of date.
 
Has anyone been having trouble saving pics from camera apps? I'm on the Beta and any camera app says I have no free space.
 
I flashed the update last night, I liked it a lot, but one of the apps I use fairly regularly wasnt quite compatible yet, so I downgraded.
 
Make sure you've granted the Storage permission for that app.

I have. It's any camera app, including Google's own. On a lark I denied all permissions to the stock Camera just to see whether re-granting them would help. No joy; Camera still stays I don't have enough storage space.
 
Last edited:
Settings->Storage says 44.26G used of 128G, or 34% used. I have Smart Storage turned on, whatever that means. Photos & videos are 1.9G
 
Has anyone been having trouble saving pics from camera apps? I'm on the Beta and any camera app says I have no free space.
Saving pics, no. Taking pics, yes. Since 8.0 I have had blurry pictures and my camera won't focus. Not sure it if is related or not but it sucks. I guess I should do a clean flash and see if it helps. 🤔
 
^I'm thinking the same thing, but not looking forward to it. OTOH, I have a three-day weekend coming up...
 
I still didn't get the OTA. WTF?
What carrier are you on?

The OTA image for the 6P has a note that it's "Not for TMO/USCC/Fi," so it's possible that They are still waiting on the carriers to push it to those devices.

(I did get tired of waiting and flashed that factory image on my T-Mobile 6P; no issues to report.)
 
What carrier are you on?
<br>
<br> The
<a href='https://developers.google.com/android/ota#angler' target='_blank' class='externalLink'>OTA image</a> for the 6P has a note that it's 'Not for TMO/USCC/Fi,' so it's possible that They are still waiting on the carriers to push it to those devices.
<br>
<br>
<i>(I did get tired of waiting and flashed that factory image on my T-Mobile 6P; no issues to report.)</i>


Oh, I am on Fi. Blah. Thanks for reading for me... I lack that sometimes.
 
I had the OTA pushed to my Nexus 6P yesterday, but I prefer to flash the factory image myself. I did so, and also flashed TWRP 3.1.1 as well as rooted with SuperSU 2.82.

The "desktop" is slow to paint, Root Call Blocker Pro and Cerberus re-start once every minute, and this moring a popup message from SuperSU stated "zygote64 has silently been denied superuser status". An "adb shell" as root was unable to find anything named "zygote\*", so I chose to re-flash Android 7.1.2.

I'll never use a .0.0 release again.
 
I had the OTA pushed to my Nexus 6P yesterday, but I prefer to flash the factory image myself. I did so, and also flashed TWRP 3.1.1 as well as rooted with SuperSU 2.82.

The "desktop" is slow to paint, Root Call Blocker Pro and Cerberus re-start once every minute, and this moring a popup message from SuperSU stated "zygote64 has silently been denied superuser status". An "adb shell" as root was unable to find anything named "zygote\*", so I chose to re-flash Android 7.1.2.

I'll never use a .0.0 release again.

Did you include the data wipe when you flashed the factory image, or did you manually flash the file systems individually and skip userdata.img?
 
No joy on Safe Mode. I was considering doing an FDR, but if O is going non-beta next week anyhow, no point in doing it right now.
You might also try disabling the Camera app (Settings > Apps & notifications > App info > Camera > Disable), which will have the pleasant side-effect of removing any updates and restoring the version of the app that was included with the build you're on. You can then re-enable the app to see if that made any difference.
 
Back
Top Bottom