Related
Finally ! Straight from Google DEVS
"nakasi" for Nexus 7 (Wi-Fi) 5.1.1 (LMY47V)
I found 5.1 official stock quite laggy on mine, coming from 4.4.4 official stock. So I wonder if there is a silver lining on this 5.1.1 or not. I won't hold my breath, but surprised that Google is willing to upgrade it despite it doesn't perform very well (similar to my iPad 1st gen taking 5.1.1, ironically, now same version number).
fortissimo said:
I found 5.1 official stock quite laggy on mine, coming from 4.4.4 official stock. So I wonder if there is a silver lining on this 5.1.1 or not. I won't hold my breath, but surprised that Google is willing to upgrade it despite it doesn't perform very well (similar to my iPad 1st gen taking 5.1.1, ironically, now same version number).
Click to expand...
Click to collapse
I believe this was to fix the memory leak that was still present.
Installed via fastboot and rebooting now. Will update when I know more.
I do know that removing Facebook appears to help with performance, but there was still a performance issue on 5.1 that required a reboot at times.
I just think that this Nexus 7 (2012) is too old for LP.
iBolski said:
I believe this was to fix the memory leak that was still present.
Installed via fastboot and rebooting now. Will update when I know more.
I do know that removing Facebook appears to help with performance, but there was still a performance issue on 5.1 that required a reboot at times.
I just think that this Nexus 7 (2012) is too old for LP.
Click to expand...
Click to collapse
I think the memory leak still hasn't been fixed yet, or it seems Google have found a fix but it STILL hasn't been released so it won't be in the 5.1.1 update.
https://code.google.com/p/android/issues/detail?id=170151&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars
gsmyth said:
I think the memory leak still hasn't been fixed yet, or it seems Google have found a fix but it STILL hasn't been released so it won't be in the 5.1.1 update.
https://code.google.com/p/android/issues/detail?id=170151&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars
Click to expand...
Click to collapse
thats for the Nexus 5 though, I havent seen anything for the N7 yet.
2 of mine are bricked (one APX mode, the other corrupted emmc but seems to "work" - sort of - with all F2FS rom), I bought a board for $40 to replace one of them but the digitizer clamp and pins flaked off on contact when trying to reassemble it so Im reluctant to do anything with it without touch capability. its just going to sit there with my blutooth mouse for kitchen-netflix for now. Im thinking of selling them all "as is" but Im curious if this update pans out, I might keep the touchless one.
There's a lollipop rom for F2FS??
Varnak said:
There's a lollipop rom for F2FS??
Click to expand...
Click to collapse
Every lollipop rom can be run with f2fs on data and cache with an appropriate kernel. I use rastapop and franco kernel r82 in with f2fs and its golden
JerryPi said:
Every lollipop rom can be run with f2fs on data and cache with an appropriate kernel. I use rastapop and franco kernel r82 in with f2fs and its golden
Click to expand...
Click to collapse
ok thanks. But i need to format system with normal partition?
Varnak said:
ok thanks. But i need to format system with normal partition?
Click to expand...
Click to collapse
You leave system partition on default ext4.
JerryPi said:
You leave system partition on default ext4.
Click to expand...
Click to collapse
How can i check wich partition are f2fs? i used a zip from this thread to convert http://forum.xda-developers.com/showthread.php?t=2678140
Varnak said:
How can i check wich partition are f2fs? i used a zip from this thread to convert http://forum.xda-developers.com/showthread.php?t=2678140
Click to expand...
Click to collapse
With the newer versions of twrp that zip is really not necessary to convert your partitions to a different file system.
To check and change format of your partitions go in your twrp recovery under wipe -advanced wipe - choose your partition - then repair or change your file system - there it says wich file system you are using and you can change it accordingly.
in twrp when you are changing the filesystem, it tells you which is the current.
Edit: just saw JerryPi's post
Two days in, 5.1.1 clearly better than 5.1 on my 32gb n7 2012 wifi.
Stock load/kernel/ext4 filesystems maintained, factory reset, full device restore/reinstall from cloud backup, rooted via TWRP, updated with SuperSU.
Nova Launcher, I just prefer it, no functional reason over stock Launcher.
Kindle app runs noticeably better, heck the Zinio reader app seems to work well too.
Google sheets/docs/presentation seems good.
TapaTalk Pro works well, as does Feedly. Notably less latency on network i/o and page transitions.
Facebook app doesn't seem to bring it down, even without any services disabled.
Haven't tried Chrome yet, and need to reload my music/video content to see how Rocket Player does.
disclaimer: I've taken to running "Trimmer (fstrim)" on an automatic schedule, daily, to keep nand free block lists healthy. That probably helps. I was doing that on 5.1 though.
If this keeps up I'd consider it a completely reasonable upgrade from KK.
Hi, what to do with the tgz file ? No zip to flash in custom recovery ?
Regards.
Marcovanbasten said:
Hi, what to do with the tgz file ? No zip to flash in custom recovery ?
Regards.
Click to expand...
Click to collapse
You need to flash via fastboot.
The Nexus 6 was my first Nexus. Since I am unlocked, rooted, stock I have been using the factory images to update throughout the life cycle of lollipop. Flashing all but User Data. I have never updated through a major OS revision before.
With 6.0 possibly being released today, would it be ok to dirty flash from the latest 5.1.1 to 6.0?
Probably, though a rooted user should take a nandroid backup and titanium app / data backup too in case a wipe is needed. A Wipe is always best when upgrading a major OS version
Thanks, I do have a nandroid backup and Titanium app/data just in case a full wipe was needed. Just was curious if I should even attempt a dirty flash.
So I am guessing there is different code in an OTA as opposed to the Factory Images to safely migrate settings?
An OTA doesn't do anything special to "migrate data" at all, if you look at the scripts.... and it's for this reason that if I received an OTA ever, I would wipe (Though I've never taken an OTA in 5+ years)...
You can attempt it, yes. I Believe you can flash the preview 3 without wipe
Hi, dirty flash (manually fastboot flash.... everything except user data) worked fine for me, from LMY48M to MRA58K.
Alright, so I just flashed MRA58N yesterday, and today there is a new MRA58R image added? What's the difference here? The first build was a security update, but what's this new one? And why only a day difference? Thanks!
Sent from my Nexus 6
Changelogs aren't made readily available.
Perhaps this script will help people who update their local AOSP repo's will help.
https://groups.google.com/forum/#!msg/android-building/0DtsHawjs4k/And8o3Dni_UJ
Obviously some modification will be required
I'm in the same position. Yesterday I flashed the MRA58N build and today I saw they already uploaded the MRA58R build, LOL, so annoying.
http://www.androidpolice.com/androi....0_r2-to-android-6.0.0_r4-AOSP-changelog.html
Quetzalcoalt_Lp said:
I'm in the same position. Yesterday I flashed the MRA58N build and today I saw they already uploaded the MRA58R build, LOL, so annoying.
http://www.androidpolice.com/androi....0_r2-to-android-6.0.0_r4-AOSP-changelog.html
Click to expand...
Click to collapse
Damn, I wonder if it's even worth flashing! I installed MRA58N and then re rooted my phone, reinstalled all my apps, reinstalled multirom, etc. Took a while, wonder if it's worth flashing!
Sent from my Nexus 6
I am currently running 6.0 MRA58R / Rooted / No Encryption. I notice no difference at all between N and R. Not that I would anyways. I'm wondering what the difference is myself.
Rektifying said:
I am currently running 6.0 MRA58R / Rooted / No Encryption. I notice no difference at all between N and R. Not that I would anyways. I'm wondering what the difference is myself.
Click to expand...
Click to collapse
What kernel are you using?
H4X0R46 said:
Damn, I wonder if it's even worth flashing! I installed MRA58N and then re rooted my phone, reinstalled all my apps, reinstalled multirom, etc. Took a while, wonder if it's worth flashing!
Sent from my Nexus 6
Click to expand...
Click to collapse
Did you do a full wipe/flash? You only really need to flash system... You'll need to reroot after, but don't need to mess with your apps and what not...
If you want to be a little more complete, flash boot, bootloader and radio too, none of which will mess with hour apps...
But if you flash boot, you will need to reflash your kernel and if your unencrypted you have to make sure you boot straight to recovery and flash kernel WITHOUT booting android.
scryan said:
Did you do a full wipe/flash? You only really need to flash system... You'll need to reroot after, but don't need to mess with your apps and what not...
If you want to be a little more complete, flash boot, bootloader and radio too, none of which will mess with hour apps...
But if you flash boot, you will need to reflash your kernel and if your unencrypted you have to make sure you boot straight to recovery and flash kernel WITHOUT booting android.
Click to expand...
Click to collapse
I never do a dirty flash just to avoid conflict, but I guess it couldn't hurt to try right? So not wiping userdata should work?
Sent from my Nexus 6
If its just the monthly updates, I wouldn't touch userdata.
If your on completely stock kernel, and encrypt do bootloader, boot, radio and system
If your unencrypted, flashing boot occasionally may help update ramdisk, but you run the risk that someday your tired or otherwise not paying attention and you boot android and it re-encrypts/wipes your device. Never done this so I am not sure if you would have the chance to stop it, or if it would just start formatting userdata out of nowhere...
Always best to take a backup right before. Then if there are issues you can restore backup things individually and install clean.
If I were on stock, most the time I would likely just backup, fastboot flash system.IMG and call it good unless issues popped up. Occasionally I would update bootloader/radios/boot... Maybe every other/every three... When people were talking about benefits of doing so here...
I have always had zero issues applying newer stock images over older stock images on a Nexus device. I do this all the time when the OTA is not available and only the main updated Google Factory image is available.
I think the trick is to always wipe dalvik and cache after a flash of system and use TWRP that supports encryption. When you wipe the dalvik and cache the system acts like an OTA and performs an upgrade on all your apps. I *think* it effectively rebuilds the cache for all apps, but it never touches the app data or user data (sdcard/pictures/etc).
I also always flash the radios and bootloader *IF* they are updated from the last image. I used to flash the stock boot images too, but now that looks like from a going forward point we won't be able to do this and have root. I do look forward to system-less root
scryan said:
If its just the monthly updates, I wouldn't touch userdata.
If your on completely stock kernel, and encrypt do bootloader, boot, radio and system
If your unencrypted, flashing boot occasionally may help update ramdisk, but you run the risk that someday your tired or otherwise not paying attention and you boot android and it re-encrypts/wipes your device. Never done this so I am not sure if you would have the chance to stop it, or if it would just start formatting userdata out of nowhere...
Always best to take a backup right before. Then if there are issues you can restore backup things individually and install clean.
If I were on stock, most the time I would likely just backup, fastboot flash system.IMG and call it good unless issues popped up. Occasionally I would update bootloader/radios/boot... Maybe every other/every three... When people were talking about benefits of doing so here...
Click to expand...
Click to collapse
Cool dude! Thanks for the advice! Yea, I use ElementalX kernel on my device, unencrypted device makes no noticeable difference for performance to me, but the battery life is another story! ElementalX has superb battery life!
Sent from my Nexus 6
Any word on the changes between this and previous build yet?
Surely we expect the security updates to show no visible differences? When my antivirus updates itself I don't ask to see the changelog, since it has no effect whatsoever on the machine's performance or user experience, no...?
If the security update is doing what it's supposed to, the only difference is that one day you won't see your device pwned.
dahawthorne said:
Surely we expect the security updates to show no visible differences? When my antivirus updates itself I don't ask to see the changelog, since it has no effect whatsoever on the machine's performance or user experience, no...?
If the security update is doing what it's supposed to, the only difference is that one day you won't see your device pwned.
Click to expand...
Click to collapse
The security updates were also in the previous build, MRA58N.
All we really know for sure is that the OTA for MRA58R is being pushed out by Verizon. The OTA path skips MRA58N.
Pushed out by big red.... I think that's something I'll definitely wait on.
jbeezley said:
Pushed out by big red.... I think that's something I'll definitely wait on.
Click to expand...
Click to collapse
I've never had a problem with their updates and, realistically, this is actually a Google update. I'm just impressed that they're leading the charge.
I'm on MRA58K after sideloading the first Marshmallow OTA. I just noticed there's an OTA from K to N but there's nothing from any Marshmallow build to R.
I'm on N and haven't seen anything detailing what's different in R. I'm just a bit suspicious of anything pushed by Verizon, although you are correct @GilmourD3. It's Google's update, but why would Verizon spearhead the rollout? I would rather just stay on N awhile until we have someone in the know look over the details of the update to R.
I flashed it and I see no difference, I'm running it rooted with that custom kernel I mentioned earlier, it runs exactly the same as N so my guess is just very small bug fixes that don't change anything on the user end.
H4X0R46 said:
I flashed it and I see no difference, I'm running it rooted with that custom kernel I mentioned earlier, it runs exactly the same as N so my guess is just very small bug fixes that don't change anything on the user end.
Click to expand...
Click to collapse
Anything change from K to N? I might just sideload the N OTA since I'm currently on K and I'm not finding an OTA path from K to R.
R is apparently the OTA update to 6.0 and the November security update for Verizon Nexus 6. My wife got it Thursday and her build and security date both changed.
OOS 5.0 (Oreo) seems to have a few hiccups, most notably lower battery life, and many are reverting back to OOS 4.5.1.
For those who've tried to downgrade to 4.5.1, can it be done without wiping internal storage? I'm trying to avoid this because I don't want to copy close to 100GB of files back to my phone as it's very time-consuming.
I use Titanium Backup so I'm not worried about app data too much. I'm currently rooted with Magisk and would like to go back to the same rooted setup on 4.5.1. I'm also on blu_spark/eng.stk's oreo-compatible TWRP right now.
rebelpixel said:
OOS 5.0 (Oreo) seems to have a few hiccups, most notably lower battery life, and many are reverting back to OOS 4.5.1.
For those who've tried to downgrade to 4.5.1, can it be done without wiping internal storage? I'm trying to avoid this because I don't want to copy close to 100GB of files back to my phone as it's very time-consuming.
I use Titanium Backup so I'm not worried about app data too much. I'm currently rooted with Magisk and would like to go back to the same rooted setup on 4.5.1. I'm also on blu_spark/eng.stk's oreo-compatible TWRP right now.
Click to expand...
Click to collapse
Unless you backup your 4.5.1 with the same twrp you are using right now, there might be a risk.
but you already have backup, right ? the worst thing is having to wait for those 100GB data to be copied back to your phone, rather than loosing everything.
I actually didn't bother doing a nandroid backup of my 4.5.1 partitions, all I did before upgrading to oreo was:
- titanium backup of all apps
- copy all of /sdcard to an external disk
I'm just considering what would be the shortest path to going back to 4.5.1.
What would be great though is if Oneplus releases the next version of stable Oreo that fixes the battery drain and the other issues that people have encountered.
I don't know why the peoples are complaining high battery drain in oxygen os 5.0. Peoples also complaint about VOLTE issues but I am using it without any issue. Perhaps they don't perform clean flash before ROM installation.
ersandeepkr said:
I don't know why the peoples are complaining high battery drain in oxygen os 5.0. Peoples also complaint about VOLTE issues but I am using it without any issue. Perhaps they don't perform clean flash before ROM installation.
Click to expand...
Click to collapse
Clean flashing would be a good option for tbose who have time. But the Oreo update was designed to be a seamless upgrade from OOS 4.x, especially for normal users who haven't even heard of the xda forums.
I don't think the same issues manifested for everyone, but considering the general response in Oneplus's forum, I think the OOS 5.0 problem has some issues.
Just to add, I can confirm better performance and battery life when I downgraded to 4.5.1.
rebelpixel said:
Clean flashing would be a good option for tbose who have time. But the Oreo update was designed to be a seamless upgrade from OOS 4.x, especially for normal users who haven't even heard of the xda forums.
I don't think the same issues manifested for everyone, but considering the general response in Oneplus's forum, I think the OOS 5.0 problem has some issues.
Just to add, I can confirm better performance and battery life when I downgraded to 4.5.1.
Click to expand...
Click to collapse
XDA forum is mainly for rooter.......
rebelpixel said:
Clean flashing would be a good option for tbose who have time. But the Oreo update was designed to be a seamless upgrade from OOS 4.x, especially for normal users who haven't even heard of the xda forums.
I don't think the same issues manifested for everyone, but considering the general response in Oneplus's forum, I think the OOS 5.0 problem has some issues.
Just to add, I can confirm better performance and battery life when I downgraded to 4.5.1.
Click to expand...
Click to collapse
Where exactly is it stated that Oreo is designed like this?
Sent from my ONEPLUS A3003 using Tapatalk
RASTAVIPER said:
Where exactly is it stated that Oreo is designed like this?
Click to expand...
Click to collapse
Hey, the thread has been cleaned because of your trolling. Just stop it if you can't contribute anything useful to this topic.
So recently I've been thinking of upgrading my phone from Oreo to Pie now that it is available and has had a few updates.
Now I haven't updated my phone in a while. The last time was around the summer of 2018. The OxygenOS version my 3T currently is running is 5.0.4 and my TWRP is on version 3.2.3-0.
A while back I was using the custom ROM 'FreedomOS' (for anyone that still remembers) but that ROM hit it's EOL point last year.
After FreedomOS went EOL I switched to stock ROM following this guide to stay decrypted: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Since I switched back to stock I haven't touched the system or recovery at all besides updating Magisk now and then.
Now the question I'm having is how do I update my phone to the latest Pie version of OxygenOS? Which is version 9.0.5 as of writing this post.
Preferably I would like to upgrade with a dirty flash to keep my data (if I run into issues after I'll clean flash) and I also want to stay dencrypted and have Magisk as root.
For your own sakes don't do that. You probably won't be happy unless you want to update to have bigger numer in info screen. (Well if you would like to update to have bigger number in info screen I would suggest editing some conf file to achieve that.)
it's here all the the time, just follow the guide
https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
First of all, both of you thanks for the replies.
wojtek007pl said:
For your own sakes don't do that. You probably won't be happy unless you want to update to have bigger numer in info screen. (Well if you would like to update to have bigger number in info screen I would suggest editing some conf file to achieve that.)
Click to expand...
Click to collapse
Is the update that bad? If so, what makes Pie so much worse when comparing it to Oreo?
BrahmaGandhi said:
it's here all the the time, just follow the guide
https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Click to expand...
Click to collapse
I've read through the thread a bit and notices this: "Important Note: If your device’s Bootloader is Unlocked, then installing this firmware will factory reset your phone as this is a firmware upgrade. All your personal data and app data will be wiped clean! So backup before flashing!"
Does this mean it will actually reset the entire phone and will wipe all of my apps and files? Is there not a way to dirty flash this new version without losing my apps and such?
Now also in the "Custom ROM" part it says the following: "3. Format Data partition - system will be encrypted (this is a must else system will not boot the new Android version)"
As my device is unencrypted at the moment do I need to let it encrypt for OOS 9 to actually boot up? Or can I just follow the steps in this guide and follow procedure 1 to stay unencrypted? https://forum.xda-developers.com/oneplus-3t/how-to/dm-verity-disable-oxygen-os-t3922324
allard1997 said:
First of all, both of you thanks for the replies.
Is the update that bad? If so, what makes Pie so much worse when comparing it to Oreo?
Click to expand...
Click to collapse
In simple words phone is slower and hotter. Battery isn't better too (battery life for me was decreased from 5 to 3, 3.5 hours screen on time). You can find more on Oneplus forums.
allard1997 said:
First of all, both of you thanks for the replies.
Is the update that bad? If so, what makes Pie so much worse when comparing it to Oreo?
I've read through the thread a bit and notices this: "Important Note: If your device’s Bootloader is Unlocked, then installing this firmware will factory reset your phone as this is a firmware upgrade. All your personal data and app data will be wiped clean! So backup before flashing!"
Does this mean it will actually reset the entire phone and will wipe all of my apps and files? Is there not a way to dirty flash this new version without losing my apps and such?
Now also in the "Custom ROM" part it says the following: "3. Format Data partition - system will be encrypted (this is a must else system will not boot the new Android version)"
As my device is unencrypted at the moment do I need to let it encrypt for OOS 9 to actually boot up? Or can I just follow the steps in this guide and follow procedure 1 to stay unencrypted? https://forum.xda-developers.com/oneplus-3t/how-to/dm-verity-disable-oxygen-os-t3922324
Click to expand...
Click to collapse
i personally would suggest you to stay on oreo or jump to pie custom roms, just skip the oos 9.0.5..
the only thing that really fast and smooth just the face unlock feature :laugh:
as far as i know when you flashed stock oos your data will always be (re)encrypted, unless you do the firmware's patch things like you did before.
jumping (upgrade) from diff. android version it's better to do a clean flash (4 wipes, exclude int. storage will be saved)...and it's mandatory required (from stock to any custom roms). except when you forced to format data you'll lost all data in your phone, for sure.
and if you want to stay unencrypted and disable dm verity for good, it's better to do all that stuffs while on stock oos before you jump onto custom roms.
for more details and assistance i suggest you post on the main thread.