Database Users

[Q] Contact Synch using loads of data after PA install

I recently installing PA 4.6 Beta 6 on my Nexus 4 because Android 5 just wasn't working out for me. Unfortunately I've encountered a serious problem: my phone is now using about a gigabyte of data per day! I only noticed this when the default data warning limit kicked in, but initially dismissed it as a side-effect of downloading/synching everything after the install. I reset the data limit and thought nothing of it until 2 days later when the 2GB limit kicked in again.
I've installed Network Connections by Anti Spy Mobile which seems to indicate all the data usage is from Google Contact Synch. I can only imagine something is looping, but seriously how could it be using so much data!?
I've un-installed anything I don't use and turned off automatic backup, but the data flood continues. A search for similar problems hasn't revealed anyone else with this problem, so I thought I'd ask on here before removing PA and switching to Cyanogen Mod.
Cheers.

It's not the ROM causing this.
#stayparanoid

Yep - was never insinuating that it was PA; just that it occurred following the install.
Sadly I haven't been able to work out what was causing it and have had to flash a new ROM before heading back to work in the morning or my mobile provider is likely to have a fit. I've flashed CM and will see how it goes, but I may well come back to PA or go the PAC ROM route. I'm definitely a fan of the PA features and am grateful for the work done by the dev team.

Did you try to accept the 5.0 update while on the 4.6 beta? It would probably have come through a notification. If you told it to download, it will never stop trying until you clean flash
#stayparanoid

Pirateghost said:
Did you try to accept the 5.0 update while on the 4.6 beta? It would probably have come through a notification. If you told it to download, it will never stop trying until you clean flash
#stayparanoid
Click to expand...
Click to collapse
It was actually 4.45 I downloaded because I wanted a stable release. After install there were some OTA updates and I did download them assuming anything OTA would be fairly stable, but I didn't know/realise it would have tried to bring down a major new version (5.0). Looks like it could have been my mistake then for thinking it would just be updates to the version I'd installed.
I did take a backup before switching to CM so if I get some time I might flash the backup and check what version it is.

onyx26_uk said:
It was actually 4.45 I downloaded because I wanted a stable release. After install there were some OTA updates and I did download them assuming anything OTA would be fairly stable, but I didn't know/realise it would have tried to bring down a major new version (5.0). Looks like it could have been my mistake then for thinking it would just be updates to the version I'd installed.
I did take a backup before switching to CM so if I get some time I might flash the backup and check what version it is.
Click to expand...
Click to collapse
If it was the google ota, it wouldn't install anyway.
We have not provided an upgrade ota from 4.x to 5.x
Its likely you were still on whatever version you installed, but the ota was constantly trying to download
#stayparanoid

The strange encryption misfire between TWRP & LOS-based OS's (questions/thoughts?)

The strange encryption misfire between TWRP & LOS-based OS's (questions/thoughts?)
Things we know:
TWRP and LOS-based systems with encryption either don't install correctly or boot correctly afterward. (2 different things perhaps).
Installing Magisk on non-encrypted partition gives boot loop
All LOS-based OS's must be installed on non-encrypted partitions
There is no easily found issue in the Jira issue tracker or TWRP bug tracker about this problem for the OnePlus 5.
I earlier posted this reply in the RR LOS ROM thread in response to another question about LOS-based OS's and encryption. I thought that rather than take a thread off topic, this is a better place for it. (where it can be totally ignored ). I shouldn't have attached this issue to a single ROM's thread since it affects a lot of LOS-based ROMs. There are other little offshoot pieces to this and some may deserve their own threads or questions at least.
TWRP: A number of people using TWRP (official or non) have problems restoring nandroid backups, which pretty much defeats much of the utility of TWRP if you can't do this. Does it have anything to do with Encryption? IT appears to, at least on the encrypted version when using the non-official version. There is a warning about it right in the thread title for non-official TWRP. I've had no problems restoring while encrypted using the official 3.1.1-1 version, but I'm beginning to feel kind of lucky in that regard.
LOS-based systems: These devices that are going to use LOS based systems require decryption of the data partition before installing whichever LOS-based ROM you're interested in. For some people, it's fine. They don't care so I don't see them as having a problem. I actually like encryption and want it, so this problem will keep me from using LOS-based ROMs until it's fixed. I've got a lot of years with Linux and Android experience, have helped with coding and customizing kernels, OSs and recoveries (mostly Philz) in the past, and would be glad to dig into the problem, at least for awhile to see if anything new can come to light but I'm not kidding myself or anyone that I can figure any of this out myself and I'm way out of practice.
Magisk: and non-encrypted partitions are also not happy together, but since I'm not too sure about the nature of that problem, I'll just call it a one-off for the moment.
Things to do: It'd be nice to figure out which area this "blob" of a problem is most likely to be in, and it'd be even nicer if one of the devs that I'll list below already knows where it is and could tell us. I can see some reason for suspecting TWRP and some reason for suspecting a combination of the OP5 FS in combination with the LOS-based ROM (or it's installer). It's not clear yet. I made a quick dirty list of some of the devs either involved with OP5 TWRP or OP5 LOS-based systems and will "mention" them in this thread in case they already know and/or are working on these things.
Another bit of this is that I signed onto Jira bug tracker (Lineage OS) to see if I could find even one sample issue that resembled this on an OP5. I couldn't but I can find some similar ones on other devices with dates only a month old. Part of this would be to try to get this either/both onto the Jira bug tracker or the TWRP bug tracker or both. Another part before that is really deciding whether this issue belongs in those places.
My question:
It's even be helpful to know whether the suspicion of LOS-based ROM and TWRP devs @apascual89, @DarkExistence, @Dees_Troy, @koenkk, @chenxingyu and @xdvs23 is that it is a problem due to TWRP or LOS ROMS or is it the combination of the two? It's be more useful to know what is most suspected to be the actual problem.
Thinking it over: It seems possible that encryption as it exists on the OP5 (in it's native OSs) is not yet available either as a blob or in an API (or in code of course) to LOS. If that's a decent premise, then LOS is just awaiting some nebulous release of either code or prebuilts from OP (not that that's any small thing or can even be counted on).
Personally I'm just curious to know what is thought to be the biggest factor preventing using LOS with encrypted partitions.
Many thanks in advance to anyone that can supply an answer(s). I'm going to do a git on Resurrection Remix to start looking into it. I've got TWRP already and am looking at that. My odds of finding anything are slim alone. If anyone is interested in this, it'd be useful for you to note your interest. If I can think of a unique way (or if you can) to describe this as a LOS-based bug or a TWRP one, then please feel free to either tell me or just open a bug report on Jira or TWRP.
Addition: May as well ask if there's already a link to an issue in Jira. I've scanned it but not found one: https://jira.lineageos.org/browse/BUGBASH-612?filter=-5
Click to expand...
Click to collapse
Clarifications of what I/others would like for the OP5 (TWRP/LOS/MAGISK) spoken of above & below:
Thanks. I think my "needs" are not very many, but that like a lot of people my wants are more. In the era of very quick processors / TPUs (like the SD835/K960/Exynos/etc) AND dedicated H/W aboard for encryption/decryption, that encryption isn't a speed drain unless benchmarks are your main thing. (even then, I'm not sure it matters). Since encryption is a really important step in keeping at least some portion of our personal data personal, I like the idea of being able to use whichever OS/ROM I can get ahold of that I like with it enabled. It's not a do or die thing. I've used more phones without it than with, but I prefer it.
That's not really my main thrust with this thread, but it's one of them. The main thrust is just a hope that this will be one of those phones (like certain Nex(i) of the past and many phones of the far past including old droids) that allows you to configure them the way you want without too many impediments. I only mentioned about 3-4 items in the original post. If we could get a solid TWRP that reliably does what really defines TWRP (make & restore nandroid backups regardless of encryption) AND allows OTG, of course that's a great starting point. We've kind of got some of that spread across two different versions right now and I expect to see it pretty soon across both. Commits are out there that need applying and debugging so that is headed in the right direction.
The other big thing for me and I see others too is to be able to use the really innovative ROMs that are lately LOS-based without having to use non-encrypted phones, certain file systems, etc. I'd like to just have the phone setup however I want, and install the damned ROMs and have them work about the same regardless. I'm not going to gripe about the usual problem LOS-based ROMs have at first like non-working cameras and other things they need either code or blobs for because that's just normal. Eventually those things will work. I guess that as a long time developer I'd really like to know what developers think is the primary cause of the inability to install and get working LOS-based ROMs on the OP5s that are encrypted. Even if I don't think of it as some huge problem, I think it's really interesting and it's some sort of problem.
Magisk and SuperSU: I guess I just accept that these "SuperUser" utilities are always going to be problematic and part of the forever struggle between manufacturers and users that like to be in control of their phones. These two groups will be leap-frogging one another forever. Until the day when no one can any longer get a bootloader unlocked and root a phone, I'm interested and after that barrier is crossed, XDA will be a lot less interesting place and so will smartphones. Yeah, I realize most users don't even know what rooted means or bootloader. We can keep trying to meet these basic "standards/desires" until then.
So all I want is a good solid TWRP and the ability to install whatever ROM I want to without doing stuff to my phone I don't want to. I'll put this in some hidden section in the OP by the way. ----- Thanks.
Click to expand...
Click to collapse
Updates regarding latest encryption fixes in a couple of LOS-based ROMS:
I got multiple reports that CRDROID (Los-based) and Unofficial RR (LOS-based) are both now patched to work with Encryption.
SO: It looks good for LOS-based ROMs now. 2 out of ~9 or 10 of them are working so they'll all be working with encryption (and without) soon enough. I'll kill off that part of this thread and concentrate more on getting the full-featured TWRP we can all use:
TWRP should be able to:
1) Backup and restore nandroids whether in encrypted or decrypted mode.
2) Be able to access OTG devices
3) Be able to convert or at least create usable a) ext4, b) f2fs (is there more we care about?) filesystems for data and cache.
Click to expand...
Click to collapse
There's a few devs I'm aware of that work on it for OP5 but I'm not going to bug them just yet. I want to be more sure I know what each version of TWRP (off and non-off) can do and can't.
More updates about ROMs and TWRP's:
Here's some updates:
1) ROMs: It's looking like the custom LOS based ROM world is headed for encryption in some cases within a few versions. You can look at the last couple pages of official and unofficial RR to see what's been discussed, but it sounds like a trend is forming that pretty much matches the trend of smartphones in general.
2) TWRP: Even though this discussion (it's about the most recent dozen replies that include me, katinatez and xdvs23) is , I think, in the official twrp thread, it's about some combination of a) official b) unofficial and c) katinatez (Damn, I know I spelled his name wrong , sorry).
Official : Good points: Can do working restores encrypted /// Bad: Can't work with OTG
UnOfficial : Good points : Work's with OTG // Bad :: Can't do working restores usually.
katinatez TWRP: Good points: OTG OK, Restores OK, Encryption/Decrytion OK; But: It's not an official nor has a thread for it and you have to self-mount /system before doing these things.
The idea is to combine the best points of unofficial and katinatez and it sounds like development is back on, and maybe a commit of both katinatez and xdvs23's code can be performed pretty soon.
Some progress seems possible!
Click to expand...
Click to collapse
Looks possible that TWRP (Unofficial) just took a leap forward and is doing a bunch of things right:
Things it's doing well (well via the few reports starting here: https://forum.xda-developers.com/showpost.php?p=73220260&postcount=910)
1) Backup / Restore nandroids (I just asked for some details on encryption states in that thread but I think the restore was to encrypted partition.
2) OTG working
3) TWRP Themes working.
4) I'll try it and check adb access and sideload as well and report back.
Click to expand...
Click to collapse
Thanks for carrying on the battle. So far it seems good to me, so nice work! -- I just installed, plugged in and mounted OTG device and did a full (all partitions) encrypted backup to the usb-stick, then restored it. I saw no red characters, and I may have forgot to save the log (doH!) but will look in the backup folder in a bit.
Currently I'm running noLimits with Elemental 1.06. No problems. Oh yeah, themes working fine as well. Unless something odd crops up, this could be a real recovery.
Good work to you guys for persevering.
Other things tested: Sideload mode OK; Adb shell OK. Installed xXx ROM latest version with another kernel: OK.
-- Probably this will be the last entry since a fully functional TWRP was a big thing on the wish list and it appears to be here. The thread is the "Unofficial TWRP" thread currently, but maybe it'll be renamed.

This is the one thing killing me about this phone right now. I'm an avid ROM tester, and I jump from ROM to ROM especially in the early days of development trying to find the one that has the things that I need working.
At the moment, after trying a ROM, there is no way that I know of to get back to stock without flashing stock recovery and stock ROM and re-ecrypting with "fastboot oem lock" and thus wiping your SD card.
It's a crazy amount of work for something that has always been so easy.

ArkAngel06 said:
This is the one thing killing me about this phone right now. I'm an avid ROM tester, and I jump from ROM to ROM especially in the early days of development trying to find the one that has the things that I need working.
At the moment, after trying a ROM, there is no way that I know of to get back to stock without flashing stock recovery and stock ROM and re-ecrypting with "fastboot oem lock" and thus wiping your SD card.
It's a crazy amount of work for something that has always been so easy.
Click to expand...
Click to collapse
Same with me. I can a step back and sort of see the long view where this thing gets somehow solved in a day or a month or whatever, and the moment it's solved, no one recalls it was such a pain in the butt. IT does keep me from testing LOS-based OS's because encryption won't work with them. It does keep me on my toes whenever I have to restore my phone from a nandroid backup and that stuff seems like where we should focus some energy.
The thing that bugs me as much as anything is that there's no visibility into anyone "doing anything" about this. I keep hearing people saying (devs too) "I don't know" and "Someone will fix it" and that could certainly happen, (or not). I'd feel much better about it if I could at least search up a bug tracker issue in one of the fairly obvious places (Lineage (Jira) bug tracker) or (TWRP bug tracker).
You're right. It's an insane amount of time to waste for something that should be a 10 minute restore from nandroid backup, but the problem is clearly bigger than that even.
Forgot to add this::
Please try to add any ideas you've got no matter how stupid you might think they are. I'm going to start when I return home.

This would be a partial fix, if true....maybe not for you, because you seem to want/need encryption. But...
https://forum.xda-developers.com/showpost.php?p=73130727&postcount=9
I don't necessarily trust a random person with a sub 100 post count posting a supposed fix for something that seems like a more serious problem, but you asked for it. It's a little sketchy, like Magisk 13.2 passing safety net, when it shouldn't. Unless his Google frameworks hadn't been updated since last week. (week old video)
I'm not sure of your needs, but personally, I would be happy if you could use OOS and LOS both on unencrypted or encrypted. His post shows OOS running on unencrypted, so presumedly you could go back and forth from unencrypted OOS to unencrypted LOS.
I certainly haven't tested it, and I am not really willing to. I have already spent too much time reformatting my phone and starting over from scratch. I'm gonna stay on stock with Magisk till this all gets sorted out.

ArkAngel06 said:
This would be a partial fix, if true....maybe not for you, because you seem to want/need encryption. But...
https://forum.xda-developers.com/showpost.php?p=73130727&postcount=9
I don't necessarily trust a random person with a sub 100 post count posting a supposed fix for something that seems like a more serious problem, but you asked for it. It's a little sketchy, like Magisk 13.2 passing safety net, when it shouldn't. Unless his Google frameworks hadn't been updated since last week.
I'm not sure of your needs, but personally, I would be happy if you could use OOS and LOS both on unencrypted or encrypted. His post shows OOS running on unencrypted, so presumedly you could go back and forth from unencrypted OOS to unencrypted LOS.
@ArkAngel06
I certainly haven't tested it, and I am not really willing to. I have already spent too much time reformatting my phone and starting over from scratch. I'm gonna stay on stock with Magisk till this all gets sorted out.
Click to expand...
Click to collapse
Because I upload the video at 2017/07/16, Magisk 13.2 can passing safety net.
This method also works for LOS on decrypted OP5.
I am so sorry for having low post count, because English is not my native language. :angel:
@ArkAngel06
I also post this method in following posts, however nobody cares about it.
Ref:
https://forum.xda-developers.com/showpost.php?p=73046308&postcount=163
https://forum.xda-developers.com/showpost.php?p=73043647&postcount=585

snowwolf725 said:
Because I upload the video at 2017/07/16, Magisk 13.2 can passing safety net.
This method also works for LOS on decrypted OP5.
I am so sorry for having low post count, because English is not my native language. :angel:
Click to expand...
Click to collapse
It's no problem, I thought the video might be like a week old or something, but i figured you wouldn't just now be posting the fix if it was done a week ago.
I hope some people give it a try and it works for them. You'd be a hero. :highfive:

There are some manual scripts you can run to keep the phone decrypted if needs be, personally I wouldn't bother, the stock Roms are superb.
Run the remain decrypted script after each flash and you'll be fine
I have a thread for this in the htc 10 threads
Sent from my ONEPLUS A5000 using XDA-Developers Legacy app

ArkAngel06 said:
This would be a partial fix, if true....maybe not for you, because you seem to want/need encryption. But...
https://forum.xda-developers.com/showpost.php?p=73130727&postcount=9
I don't necessarily trust a random person with a sub 100 post count posting a supposed fix for something that seems like a more serious problem, but you asked for it. It's a little sketchy, like Magisk 13.2 passing safety net, when it shouldn't. Unless his Google frameworks hadn't been updated since last week. (week old video)
I'm not sure of your needs, but personally, I would be happy if you could use OOS and LOS both on unencrypted or encrypted. His post shows OOS running on unencrypted, so presumedly you could go back and forth from unencrypted OOS to unencrypted LOS.
I certainly haven't tested it, and I am not really willing to. I have already spent too much time reformatting my phone and starting over from scratch. I'm gonna stay on stock with Magisk till this all gets sorted out.
Click to expand...
Click to collapse
Thanks. I think my "needs" are not very many, but that like a lot of people my wants are more. In the era of very quick processors / TPUs (like the SD835/K960/Exynos/etc) AND dedicated H/W aboard for encryption/decryption, that encryption isn't a speed drain unless benchmarks are your main thing. (even then, I'm not sure it matters). Since encryption is a really important step in keeping at least some portion of our personal data personal, I like the idea of being able to use whichever OS/ROM I can get ahold of that I like with it enabled. It's not a do or die thing. I've used more phones without it than with, but I prefer it.
That's not really my main thrust with this thread, but it's one of them. The main thrust is just a hope that this will be one of those phones (like certain Nex(i) of the past and many phones of the far past including old droids) that allows you to configure them the way you want without too many impediments. I only mentioned about 3-4 items in the original post. If we could get a solid TWRP that reliably does what really defines TWRP (make & restore nandroid backups regardless of encryption) AND allows OTG, of course that's a great starting point. We've kind of got some of that spread across two different versions right now and I expect to see it pretty soon across both. Commits are out there that need applying and debugging so that is headed in the right direction.
The other big thing for me and I see others too is to be able to use the really innovative ROMs that are lately LOS-based without having to use non-encrypted phones, certain file systems, etc. I'd like to just have the phone setup however I want, and install the damned ROMs and have them work about the same regardless. I'm not going to gripe about the usual problem LOS-based ROMs have at first like non-working cameras and other things they need either code or blobs for because that's just normal. Eventually those things will work. I guess that as a long time developer I'd really like to know what developers think is the primary cause of the inability to install and get working LOS-based ROMs on the OP5s that are encrypted. Even if I don't think of it as some huge problem, I think it's really interesting and it's some sort of problem.
Magisk and SuperSU: I guess I just accept that these "SuperUser" utilities are always going to be problematic and part of the forever struggle between manufacturers and users that like to be in control of their phones. These two groups will be leap-frogging one another forever. Until the day when no one can any longer get a bootloader unlocked and root a phone, I'm interested and after that barrier is crossed, XDA will be a lot less interesting place and so will smartphones. Yeah, I realize most users don't even know what rooted means or bootloader. We can keep trying to meet these basic "standards/desires" until then.
So all I want is a good solid TWRP and the ability to install whatever ROM I want to without doing stuff to my phone I don't want to. I'll put this in some hidden section in the OP by the way. ----- Thanks.

snowwolf725 said:
Because I upload the video at 2017/07/16, Magisk 13.2 can passing safety net.
This method also works for LOS on decrypted OP5.
I am so sorry for having low post count, because English is not my native language. :angel:
@ArkAngel06
I also post this method in following posts, however nobody cares about it.
Ref:
https://forum.xda-developers.com/showpost.php?p=73046308&postcount=163
https://forum.xda-developers.com/showpost.php?p=73043647&postcount=585
Click to expand...
Click to collapse
Thanks snowwolf;
I think I replied to some of this in my reply to @ArkAngel06 already and I appreciate it. For Magisk, it seems like we're in a race between Google and the Magisk/SuperSU developers that'll never end. They have to keep leap-frogging each other which I suspect they'll do for a long time yet. It's great to have work-a-rounds and with SuperUser utilities, maybe that's about all we can ever hope for. The emphasis has been thrown on "high security" devices by too many companies and even governments so that the security world will never again look like the beginning of the smartphone era when nearly every phone had an unlocked/able bootloader. I appreciate the reply.

dladz said:
There are some manual scripts you can run to keep the phone decrypted if needs be, personally I wouldn't bother, the stock Roms are superb.
Run the remain decrypted script after each flash and you'll be fine
I have a thread for this in the htc 10 threads
Sent from my ONEPLUS A5000 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I might just be too tired to do this right now, but is there a link to those scripts as well? Thanks for the reply. I think a lot of stock ROMs are really good lately too and most of the time, until really solid TWRP implementations and ROM implementations, I just Root, make backups and fine tune stock ROMs, but I love the idea of having freedom to use LOS-based ROMs in any encryption configuration I want, and to make working restorable nandroid backups which we're still working towards. I appreciate it.

hachamacha said:
I might just be too tired to do this right now, but is there a link to those scripts as well? Thanks for the reply. I think a lot of stock ROMs are really good lately too and most of the time, until really solid TWRP implementations and ROM implementations, I just Root, make backups and fine tune stock ROMs, but I love the idea of having freedom to use LOS-based ROMs in any encryption configuration I want, and to make working restorable nandroid backups which we're still working towards. I appreciate it.
Click to expand...
Click to collapse
This is my thread, never got round to making a script but shouldn't be too hard.
Haven't tried this on the OnePlus but the principle should be the same.
https://forum.xda-developers.com/showthread.php?t=3604856
Sent from my ONEPLUS A5000 using XDA-Developers Legacy app

Another thing to take into account now that may be getting solved with some luck is that the RR official build has had this commit applied today to attempt to fix a LOS-based build to boot encrypted. No one has any idea (I think anyway) whether it works yet, but we should know pretty soon. RR is pretty popular.
Here is the commit(s) I found ::: https://github.com/apascual89/andro...mmit/a13eef258620e0726c6dcd9e83dacc1342080ed6
I'll update the OP if it worked.

Subscribed to this thread, this was a fantastic, cohesive way of trying to get these issues fixed! Hope to see it succeed!

MrWilsonxD said:
Subscribed to this thread, this was a fantastic, cohesive way of trying to get these issues fixed! Hope to see it succeed!
Click to expand...
Click to collapse
Thanks. That was my goal I thought maybe we're getting closer on some of these issues that all sort of whirl about one another in the encryption realm. The 'commit' in RR I noted above in some other reply was at least a brief ray of light but I've heard one report that it didn't work so far. I guess we'll see if anyone gets it to work. Cheers.
Quote of someone (and myself asking questions) from the RR Official thread where the commit to try to fix encryption+LOS happened earlier:
Hecke92 said:
Tried encrypted install, but cannot get past boot screen
Thanks anyway
Click to expand...
Click to collapse
Just curious if there's any details you could share about which version TWRP,
which version and type (SuperSU or Magisk) SU and what you had installed prior to this encrypted attempt.
Also which type of encrypted (ext4, f2fs, etc) would be the target?
many thanks for any information either way.
And the reply I got back::
I have the latest tarp by xdvd (as i saw it was newer than official twrp). I am always using magic, but that is of no relevance I think (because I clean flashed RR and no SU is integrated).
Partition is ext4 and before I had OOS (XXX)

so apparently over in the RR unofficial thread there are users reporting that they flashed and booted on an encrypted device.
success.

Solved https://forum.xda-developers.com/showpost.php?p=73143625&postcount=350

heisenberg33 said:
Solved https://forum.xda-developers.com/showpost.php?p=73143625&postcount=350
Click to expand...
Click to collapse
Hey cool! That's terrific. I don't have time to scan the source and see if it's any different than the changes I listed from official RR but really this at least halfway satisifies the premise of this thread. I guess I'll keep it going until we're sure that TWRP can backup/restore nandroids no sweat regardless of encryption state and also handle OTG devices. Then I think we're onto a more solid start.
I'll fix this thread up tomorrow in the OP and when it's served a purpose will stop updating it. Shouldn't be long
Thanks to you last two guys for shouting this out for people. I asked a question at the end of official about where their github is located. I don't see it in the OP where official RR lists theirs.

Updates from recent comments in RR ROM LOS-based Unofficial & Official versions::
Since I've not yet found the exact source used in the unofficial version which is now working encrypted on the OP5, I'll have to wait to put up a link to it. @Eliminater is the author so credits to him and whoever did the working commit. If @Eliminater can give us a link to the working github where the changes that made encryption work were committed, it'd be appreciated.
Comments from https://forum.xda-developers.com/oneplus-5/development/los-resurrection-remix-n-t3632856 (unofficial RR) seem to indicate that although they managed to get encryption working OK with RR unofficial that they "may" have lost the ability (at this point) to run non encrypted. I'm not certain of this but that's how the comments/replies look. I'm sure it'll settle out soon. I'm also pretty sure that every LOS-based developer for the OP5 knows where the source is where this change occurred and that's more important than me knowing where it is. (so good job!)
Comments from Official RR: https://forum.xda-developers.com/oneplus-5/development/rom-resurrection-remix-n-7-1-2-t3636578 where I found and posted the commit that was supposed to fix encryption, indicate that they're not yet quite there. Comments say that encrypted official RR is not yet working and still boot-loops. Shouldn't take long for them to get these two synced up, but that's just my take. On Official RR, decrypted works.

and now crdroid is also working on encrypted devices..
same Dev as unofficial rr.. (thanks eliminator!)
no word if it working on both encrypted and decrypted..
https://forum.xda-developers.com/oneplus-5/development/7-1-2-crdroidofficial-t3636441/post73146174

gershee said:
and now crdroid is also working on encrypted devices..
same Dev as unofficial rr.. (thanks eliminator!)
no word if it working on both encrypted and decrypted..
https://forum.xda-developers.com/oneplus-5/development/7-1-2-crdroidofficial-t3636441/post73146174
Click to expand...
Click to collapse
Thanks for the report. It looks good for LOS-based ROMs now. 2 out of ~9 or 10 of them are working so they'll all be working with encryption (and without) soon enough. I'll kill off that part of this thread and concentrate more on getting the full-featured TWRP we can all use:
TWRP should be able to:
1) Backup and restore nandroids whether in encrypted or decrypted mode.
2) Be able to access OTG devices
3) Be able to convert or at least create usable a) ext4, b) f2fs (is there more we care about?) filesystems for data and cache.
Click to expand...
Click to collapse
There's a few devs I'm aware of that work on it for OP5 but I'm not going to bug them just yet. I want to be more sure I know what each version of TWRP (off and non-off) can do and can't.

Has Oreo officially been released on the 1+5? or are there any fully functional ROMs?

Hi all,
seems that the installation methods are a little different compared to the normal run of the mill installations which is normally required.
As im on custom ROM and always have been I'm not aware of what is available on stock.
Slightly hesitant to commit to installing if there is an impending official version.
cheers.

Yes, Oreo OOS 5 is official. There are plenty of threads on this particular subject.

dladz said:
Hi all,
seems that the installation methods are a little different compared to the normal run of the mill installations which is normally required.
As im on custom ROM and always have been I'm not aware of what is available on stock.
Slightly hesitant to commit to installing if there is an impending official version.
cheers.
Click to expand...
Click to collapse
MadCow809 said:
Yes, Oreo OOS 5 is official. There are plenty of threads on this particular subject.
Click to expand...
Click to collapse
Oreo has been released officially but yesterday they cancelled the rollout due to some unspecified bugs.
Anyway, it seems fairly stable and the there are some download links for the full ROM here: https://forum.xda-developers.com/showpost.php?p=72799046&postcount=2

ulxerker said:
Oreo has been released officially but yesterday they cancelled the rollout due to some unspecified bugs.
Anyway, it seems fairly stable and the there are some download links for the full ROM here: https://forum.xda-developers.com/showpost.php?p=72799046&postcount=2
Click to expand...
Click to collapse
Wonderful and oops if they've pulled it, so it's not quite released then..
ok good to know..
I'll hold fire on stock, sorry should have made that clear, I only flash custom ROMs although stock OOS isn't too shabby, I'd miss the mods I use
thanks though mate, I'll keep an eye out for it, appreciate it :good:

I was really considering upgrading to OS 5.0 but I've seen mixed reviews about it. It seems like the installation is sort of hassle as well. I don't see anything wrong with nougat as of right now.

Dchoi229 said:
I was really considering upgrading to OS 5.0 but I've seen mixed reviews about it. It seems like the installation is sort of hassle as well. I don't see anything wrong with nougat as of right now.
Click to expand...
Click to collapse
precisely what I was thinking, my thinking is I can upgrade but I'd be leaving behind some serious stability, stamina and performance. Not to mention that I don't know what does or doesn't work on Oreo.
I think it would make perfect sense to hold fire until it's official.

dladz said:
precisely what I was thinking, my thinking is I can upgrade but I'd be leaving behind some serious stability, stamina and performance. Not to mention that I don't know what does or doesn't work on Oreo.
I think it would make perfect sense to hold fire until it's official.
Click to expand...
Click to collapse
yup.. pretty much what I'm thinking too.

dladz said:
precisely what I was thinking, my thinking is I can upgrade but I'd be leaving behind some serious stability, stamina and performance. Not to mention that I don't know what does or doesn't work on Oreo.
Click to expand...
Click to collapse
I could be wrong on this, but I think xposed won't work on Oreo. Most other apps shouldn't have any compatibility issues.
So far the overall experience of official Oreo OOS 5 seems to be a bit snappier and performs better than Nougat.

MadCow809 said:
Yes, Oreo OOS 5 is official. There are plenty of threads on this particular subject.
Click to expand...
Click to collapse
No it is not, it was pulled, no need to tell me about threads it's not helpful nor does it make you look clever.

MadCow809 said:
I could be wrong on this, but I think xposed won't work on Oreo. Most other apps shouldn't have any compatibility issues.
So far the overall experience of official Oreo OOS 5 seems to be a bit snappier and performs better than Nougat.
Click to expand...
Click to collapse
I don't care for xposed and until it's a final release I highly doubt it'll give the same stability I have right now.
Either way I won't be committing to Oreo until it's officially released and stably within custom ROMs.

I have installed OREO on my work phone, and for the moment I am not impressed by O. Nougat is so stable and refined after all, not very clear why to upgrade...?!?!?!?! I will maintaine N on the OP5 until FaceLock comes includede in O-

mlara.particular said:
I have installed OREO on my work phone, and for the moment I am not impressed by O. Nougat is so stable and refined after all, not very clear why to upgrade...?!?!?!?! I will maintaine N on the OP5 until FaceLock comes includede in O-
Click to expand...
Click to collapse
yep that's where my heads at, again I'll be holding fire for the time being.

Fair enough. It's hardly a secret that many users have experienced boot loop issues when upgrading to OOS 5.0, maybe that was the main reason why OnePlus decided to pull back the OTA. But loads of users have successfully flashed the rom and it stable as a daily driver, not to mention several users have already noticed a performance gain over the old Nougat rom.

MadCow809 said:
Fair enough. It's hardly a secret that many users have experienced boot loop issues when upgrading to OOS 5.0, maybe that was the main reason why OnePlus decided to pull back the OTA. But loads of users have successfully flashed the rom and it stable as a daily driver, not to mention several users have already noticed a performance gain over the old Nougat rom.
Click to expand...
Click to collapse
That's irrelevant, I'm not installing it, such is the thinking of many others.

dladz said:
That's irrelevant, I'm not installing it, such is the thinking of many others.
Click to expand...
Click to collapse
They've actually released another update over 5.0. I'm still not convinced either lol.

Dchoi229 said:
They've actually released another update over 5.0. I'm still not convinced either lol.
Click to expand...
Click to collapse
Suppose we'll know once a few custom rom's have been released.

What about an official H2os? the only downloads on the official h2os site are beta 1 and beta 2. Any expected dates for oreo h2os?

OcazPrime said:
What about an official H2os? the only downloads on the official h2os site are beta 1 and beta 2. Any expected dates for oreo h2os?
Click to expand...
Click to collapse
that's kind of what I'm getting at, we need an officially released base which can be used without any odd Flashing instructions and only with bugs which would affect the device as expected.
ie: stock OOS should work fine, LOS and AOSP will more then likely have some issues, which is to be expected.
From what I've read, there has been another base released.

dladz said:
that's kind of what I'm getting at, we need an officially released base which can be used without any odd Flashing instructions and only with bugs which would affect the device add expected.
I've: stock OOS should work fine, LOS and AOSP will more then likely have some issues, which is to be expected.
From what I've read, there has been another base released.
Click to expand...
Click to collapse
exactly.. what kind if update wipes your data and forces you to lock your bootloader.

dladz said:
that's kind of what I'm getting at, we need an officially released base which can be used without any odd Flashing instructions and only with bugs which would affect the device add expected.
I've: stock OOS should work fine, LOS and AOSP will more then likely have some issues, which is to be expected.
From what I've read, there has been another base released.
Click to expand...
Click to collapse
I agree completely. I refuse to use anything other than h2os now. I get such insane battery out of it but it seems to be on the back burner in terms of updates so i expect oreo to be a long ways out. Its cool there are open betas for it though but unfortunately the betas dont allow google apps. Side thought, it would be amazing to see some development for h2os.

May 2019 update is rolling out

Gang,
The May 2019 update is now rolling out.
You should get an OTA update any time soon.
Main update topics:
- Android Generic
https://source.android.com/security/bulletin/2019-05-01.html
- Pixel Specific
"There are no Pixel security patches in the May 2019 Pixel Update Bulletin. "
"All Pixel devices running Android 9 will receive an Android 9 update as part of the May OTA. This quarterly release contains many functional updates and improvements to various parts of the Android platform and supported Pixel devices."
https://source.android.com/security/bulletin/pixel/2019-05-01.html
Have fun

OTA Screenshot

What took you so long? I installed it more than two hours ago.

Seems nothing changed only security updates. However At-a-Glance widget now have only three options again.
No smart notifications and no Reminders notifications in the options.

Another update and no changes.. Well disappointing

100rabh7791 said:
Another update and no changes.. Well disappointing
Click to expand...
Click to collapse
Oh, there are changes, Google is just getting lazy documenting them. How often to you see app updates that only state "bug fixes and performance improvements". I think they just cut & paste that into everything these days...

Pkt_Lnt said:
Oh, there are changes, Google is just getting lazy documenting them. How often to you see app updates that only state "bug fixes and performance improvements". I think they just cut & paste that into everything these days...
Click to expand...
Click to collapse
Haha lets find them out then
1) battery % on the bottom of always on displays looks a bit bigger

The android security patch now says May! :silly::laugh:

I think Google focusing on Android Q and at this point make no sense to add improvements for Android P.
Android Q Beta 3 will be released after/during Google IO event. There will be a lot of announcement and new features for Android Q. Maybe a good time to upgrade.

Any of you guys rooted with magisk? It seems the may updates killed magisk and bootloops, at least for me.

Here's one change i noticed. Charging my device doesn't slow down until 95% full. ampere app shows 1020ma using a QC 3.0 enabled charger, not like before once the device hits 80% it slows down the charging from 1020ma to 600 to 700ma.

agplugged said:
Any of you guys rooted with magisk? It seems the may updates killed magisk and bootloops, at least for me.
Click to expand...
Click to collapse
Same here. I'm running unrooted because of bootloops

Can someone tell me exactly how to update, im on april update stock magisk rooted with twrp recovery and custom kernel, cuz last time i updated from march to april update i messed up my phone and ended up wiping everything from it

agplugged said:
Any of you guys rooted with magisk? It seems the may updates killed magisk and bootloops, at least for me.
Click to expand...
Click to collapse
I checked and made sure everything is in the latest version, and failed like you. John Wu is going to Apple to get a internship, maybe the update for the new version of magisk would not came out that fast as before. And now I choose to stay in the April update.

zenjedi said:
Same here. I'm running unrooted because of bootloops
Click to expand...
Click to collapse
naive_tode said:
I checked and made sure everything is in the latest version, and failed like you. John Wu is going to Apple to get a internship, maybe the update for the new version of magisk would not came out that fast as before. And now I choose to stay in the April update.
Click to expand...
Click to collapse
The easiest fix to regain root is....go to twrp, flash the magisk uninstaller.zip, then immediately flash the magisk 18.1 zip. You'll have to install your modules again, but that's not too big a deal :good::good:
---------- Post added at 07:27 PM ---------- Previous post was at 07:22 PM ----------
Nightf0x_007 said:
Can someone tell me exactly how to update, im on april update stock magisk rooted with twrp recovery and custom kernel, cuz last time i updated from march to april update i messed up my phone and ended up wiping everything from it
Click to expand...
Click to collapse
Fastboot the May factory image with the -w removed from the flash-all.bat file, and let it boot up. Go back to fastboot mode, and fastboot twrp, I use the 323-1 version since I didn't have any luck with the 330-0 version. Once in twrp, flash the twrp installer zip, then flash the magisk uninstaller zip, then flash magisk 18.1 zip, boot up, install your magisk modules again, and done :good:

If I am going to do a clean install (with wipe) do I still need to uninstall magisk in order to prevent bootoops w current version?

Cowbell_Guy said:
If I am going to do a clean install (with wipe) do I still need to uninstall magisk in order to prevent bootoops w current version?
Click to expand...
Click to collapse
Not really since your phone will be completely wiped anyways. You may need to use magisk 18.1 though. The May update and magisk 19+ versions did not work for me :good:

agplugged said:
Any of you guys rooted with magisk? It seems the may updates killed magisk and bootloops, at least for me.
Click to expand...
Click to collapse
Works fine for me . I had to change to partition a this time to though

There is a UI change which I don't really like, though i will get used to it - probably for the best.
There's a new loading arrow symbol on all apps and pages that are loading. It uses the colour theme of the app.
See attached .
Everyone else notice this?

I want to update but dont want bootloops

Android 11 Beta 1 Available Now

https://www.xda-developers.com/oneplus-8-oneplus-8-pro-android-11-beta-download/
Is anyone eager to flash this or has flashed yet? What are your thoughts/opinions?

TheKnux said:
https://www.xda-developers.com/oneplus-8-oneplus-8-pro-android-11-beta-download/
Is anyone eager to flash this or has flashed yet? What are your thoughts/opinions?
Click to expand...
Click to collapse
I'd hold off a bit. From previous experience the first release or two are unstable (crashes, excessive battery drain, etc) and functionality is poor. Unless you got some free time on your hands and just want to quick check it out, but I'd def anticipate downgrading back to 10. Once the initially one is out they churn out more stable releases fairly quickly.

TheKnux said:
https://www.xda-developers.com/oneplus-8-oneplus-8-pro-android-11-beta-download/
Is anyone eager to flash this or has flashed yet? What are your thoughts/opinions?
Click to expand...
Click to collapse
this is not a beta this is developer preview 1, these are basically alpha builds beta will be next. I installed it yesterday and it is unusable for the most part