Database Develop

[DISCUSSION] OTA Lollipop Update

I'm getting really mixed reviews for the lollipop update lately. Some love it, some hate it, some haven't even gotten it. I'm just curious towards the majority of opinions for the new update. So, should we or should we not update?

For me, it was great. Everything worked fine and you get the awesomeness of Android Lollipop. I've seem some people with problems with Xposed, but I don't use that.

zowpow said:
For me, it was great. Everything worked fine and you get the awesomeness of Android Lollipop. I've seem some people with problems with Xposed, but I don't use that.
Click to expand...
Click to collapse
Have you noticed any performance problems? Like slow menus or animations? I myself don't have the update, but that's a common problem I hear.

I tried it for short, but it was quite somewhat laggy and not as fast as I am now used to have on custom roms.
But I am interested what other users got to say

Lollipop and KitKat from LG both has terrible RAM management. I had to restart my phone every 48h to stop it from restarting my apps.
Besides that it's quite a good ROM. Very stable, bug free. Workes much faster than KitKat.

AlbinoCookie said:
Have you noticed any performance problems? Like slow menus or animations? I myself don't have the update, but that's a common problem I hear.
Click to expand...
Click to collapse
No, to me, it's faster than kitkat, but that might be because I flashed the kdz then reset the phone. I don't use CM because video recording doesn't work.

So after rooting my l90's I noticed my OTA updated one was at least 5 times slower than my offline updated ones. This is not an exaggeration, while installing an app, I was able to remove apps on my other phone, and install the same app, before the app finally installed on the OTA updated phone. That's just the start, menus are slower and there is tons of lag. I'm not sure exactly if it's the OTA that is the issue, but all of my l90s are at most a month old, and were purchased at the same time, so I doubt it's hardware. The firmware of the ota is identical to the offline updated, although I can't definitively determine if updating over the air is the issue because I only have one phone with the OTA. That being said I have also reflashed the same firmware with the offline method onto the ota, and it has made no changes.

[Q] Should I upgrade to 5.1 lollipop?

I just got my droid turbo about a week ago, and I've since Been hearing about all the battery drainage issues and charging issues, all of the apps I use are compatible with 4.4 KitKat, so I'm a little leery of upgrading because I use my phone a ton and the massive battery was the main reason I got it over an S6, and so if that is negated, is there any reason to upgrade?

Jordaneer said:
I just got my droid turbo about a week ago, and I've since Been hearing about all the battery drainage issues and charging issues, all of the apps I use are compatible with 4.4 KitKat, so I'm a little leery of upgrading because I use my phone a ton and the massive battery was the main reason I got it over an S6, and so if that is negated, is there any reason to upgrade?
Click to expand...
Click to collapse
My Turbo never had any of the issues others had. Easily get over a day with moderate to heavy use; 2 days with light usage. I'm still on 4.4.4. If you're worried about it, head over to the development section and follow the steps to flash 5.1 without eliminating your option to go back to KitKat.

As is all too common in these forums, those who experience problems go out of their way to publish them, giving the impression that everyone has issues when most, like I, experience none of them. If you are comfortable with the rather detailed (but manageable) process for getting rooted and reversible 5.1, then by all means go that route.
Otherwise, if you are happy with KitKat, don't feel pressured to go to Lollipop. On the other hand, most users (but by no means ever all users) that have taken the OTA upgrade are just fine with the results, with comparable battery life and improved performance in some functions.

Most users have reported that wiping cache solves their performance and battery issues. In your case, I would recommend a full wipe after the upgrade, ask around and you'll find that full wipe after update has almost 99.9% success rate.

So today was my first day being on rooted 5.1.
I unplugged at about 11am, and am now hitting 10% battery 9 hours later. That should suck right?
Well I also wanted to drain my battery today so I just let my phone stream video (plex library ftw) at max brightness.. 8 hours of straight screen on time...
I think in a normal usage day (where Im not trying to kill the battery) I clock 2-3 hours of on screen time...
So if we extrapolate that out, I'm just guessing... I would've made it 20-30 hours of battery at my normal usage.
Is that good? Dunno. No worse than when I was on rooted KK.. perhaps, I think, even better?
I also dirty flashed 5.1 over my 4.4.4.. never wiped cache or FDR.
Hearing that, its up to you to decide what to do, for me I'm sticking with rooted 5.1 and couldn't be happier.

I didn't know you could root 5.1 on droid turbo

Kiwironic said:
I didn't know you could root 5.1 on droid turbo
Click to expand...
Click to collapse
The breakthrough came from this thread yesterday: FrankenPop
Which then lead to this thread late last night: Instructions and first released image
Computerfreek released his image early this morning: Thread
Working from home has its benefits.
EDIT: I am surprised Droid-life or no other outlet has really picked up on this yet.

Well, if you can root 5.1, then there's are no cons to upgrading really. You can have customisation as well as the new user experience.

Kiwironic said:
Well, if you can root 5.1, then there's are no cons to upgrading really. You can have customisation as well as the new user experience.
Click to expand...
Click to collapse
You can't root from the ota so do not update that way!!!!

Kiwironic said:
Well, if you can root 5.1, then there's are no cons to upgrading really. You can have customisation as well as the new user experience.
Click to expand...
Click to collapse
Well if you go to the threads you'll see the root method requires 4..4.4 boatloader.. so taking the official update overwrites the bootloader to 5.1 and at that point there is no going back.
So for the average user, taking the upgrade is a major deal.. for those that don't mind some adb/fastboot work.. absolutely, go back and forth from KK to LP everyday! Just dont touch that 4.4.4 bootloader.

Thanks for the update. It makes sense now. We not talking upgrade vs staying on 4.4.4 we are talking upgrade path.
I see, I am still looking forward to finding a way to upgrade my xt1225 to 5.1 without data wipe, but so far there is nothing for us, no OTA or images yet. No upgrade path in sight

No. You would going from best to OK.

I upgraded to 5.1 and for me it was a mistake. My most valuable app (Record My Call) doesn't work with 5.1 and no other similar app will work either. I'm going to buy another another Droid Turbo on KitKat and sell my 5.1.
Ken

I updated both my and my wife's DT via the OTA. We didn't have root before and I simply haven't needed it, so I figured I'd just go ahead (if anything went wrong, I would have to harass Verizon, but so be it). In the end, both phones are working well (knock on wood)... and I didn't do the cache or factory reset either. Battery life is fine, even with some gaming... so it might be better than KK was, but it's certainly not worse for me.
emgo said:
I upgraded to 5.1 and for me it was a mistake. My most valuable app (Record My Call) doesn't work with 5.1 and no other similar app will work either. I'm going to buy another another Droid Turbo on KitKat and sell my 5.1.
Click to expand...
Click to collapse
Google Voice does this without needing an app.... that might get you a solution for free?
Seems like there are plenty of updated apps that can work in LP as well: https://www.androidpit.com/forum/632761/best-call-recorder-app-for-android-5-lollipop

schwinn8 said:
I updated both my and my wife's DT via the OTA. We didn't have root before and I simply haven't needed it, so I figured I'd just go ahead (if anything went wrong, I would have to harass Verizon, but so be it). In the end, both phones are working well (knock on wood)... and I didn't do the cache or factory reset either. Battery life is fine, even with some gaming... so it might be better than KK was, but it's certainly not worse for me.
Google Voice does this without needing an app.... that might get you a solution for free?
Seems like there are plenty of updated apps that can work in LP as well: https://www.androidpit.com/forum/632761/best-call-recorder-app-for-android-5-lollipop
Click to expand...
Click to collapse
This is from google Voice help.
"It's not currently possible to record outbound calls made through your Google number at this time."
Tried many recommend apps, none work. Found this information in a couple of places.
https://bitbucket.org/copluk/acr/issues/257/after-upgrading-to-android-5-cannot-record
"Motorola has stopped 2 way call recording support with Android 5. This is not our fault. Try any other call recording app you'll see that none works.
Your only option is to set audio source to MIC and set loudspeaker on.
I hope you understand and increase your star rating"
I'm currently looking for a used Turbo still on KitKat
Thanks,
Ken

emgo said:
This is from google Voice help.
"It's not currently possible to record outbound calls made through your Google number at this time."
Click to expand...
Click to collapse
Thanks for the info on Google voice not supporting outgoing calls. I didn't need it, so I never tested it.
emgo said:
Tried many recommend apps, none work.
Click to expand...
Click to collapse
I did a quick search and the recommended app was BoldBeast Recorder. I just tried it with a standard voice call (not GV) I had with my wife (outgoing if it matters) and it worked just fine in Mode 1. After the install, it defaulted to Mode 4 and didn't work, so i was going to start with Mode 1 and go from there... but it just worked there, so i didn't have to go further. To recap, I'm on the OTA updated Lollipop... no factory reset and no cache wipe.

schwinn8 said:
Thanks for the info on Google voice not supporting outgoing calls. I didn't need it, so I never tested it.
I did a quick search and the recommended app was BoldBeast Recorder. I just tried it with a standard voice call (not GV) I had with my wife (outgoing if it matters) and it worked just fine in Mode 1. After the install, it defaulted to Mode 4 and didn't work, so i was going to start with Mode 1 and go from there... but it just worked there, so i didn't have to go further. To recap, I'm on the OTA updated Lollipop... no factory reset and no cache wipe.
Click to expand...
Click to collapse
In mode 1 it records the call but like every app I've tried after the update to Lollipop it's using the microphone to record the call. My voice is loud and clear but the other person's voice is very faint or not heard at all. Did you get different results? Before the update "Record My Call" worked perfectly, it recorded the actually conversation somehow without using the mic.
Thanks,
Ken

emgo said:
In mode 1 it records the call but like every app I've tried after the update to Lollipop it's using the microphone to record the call. My voice is loud and clear but the other person's voice is very faint or not heard at all. Did you get different results? Before the update "Record My Call" worked perfectly, it recorded the actually conversation somehow without using the mic.
Thanks,
Ken
Click to expand...
Click to collapse
I did find my voice was a little louder, but my wife's was perfectly audible. Both required me to turn the volume up, but they worked fine and both were clear...
Maybe another mode would work better, but this was fine for my limited usage.

So I read these complaints and have decided to opt out of the upgrade to Lollipop on my Droid Turbo. When the upgrade notification screen came up, I just put no, and I haven't gotten a notification since. It's been a few weeks for me. A few other people in my family have the same phone. Unfortunately when they click "no" they seems to get the upgrade prompt again a few days later. I'm not sure why the prompt hasn't come up for me again.
Is there a way to stop the upgrade notification prompt for showing up repeatedly without root? I know that there are apps on a rooted system that can prevent the notification. I'm hoping there's a way to prevent it without root. Thanks for any info!

schwinn8 said:
I did find my voice was a little louder, but my wife's was perfectly audible. Both required me to turn the volume up, but they worked fine and both were clear...
Maybe another mode would work better, but this was fine for my limited usage.
Click to expand...
Click to collapse
I tried all modes and mode 1 seems best. I tried many apps that use the microphone and they are all about the same. They work OK if you are in a quite area but a noisy environment or step outside when the wind is blowing and the microphone recorders don't work well at all, not for me. I'm watching Ebay and Craigslist for one still on Lollipop. 64GB models are bringing around $400 no matter which OS they are on. Mine should bring about the same amount that I pay for one with KitKat so hopefully it won't cost much to correct my mistake of upgrading.
Ken

Help me get some more usage out of this phone :/ Asking basic questions!

Hi guys!
So I'm probably not as good with phones as you, but I learned to install a ROM, I've tried many of them but then returned to CyanogenMod ROM that was offered on their site. The performance is not that good, it lags often and battery life is too bad! The questions I want to ask you are:
1. Which ROM do you think is the most stable and would be a better alternative to Jelly Bean CyanogenMod?
2. What ROM are you using and why? Experiences etc.
Thank you!

Kind of in the same boat, just three meters further out. Have been putting off buying a new pho.... embiggened touch-pad device with phone capability and less battery life, that should in a reasonable world come with a carrying case with a shoulder-strap, and a stock portfolio for the handset maker... for a few years. But finally caved in, and bought something on sale with a really good screen, a replaceable battery, and a 3,5mm jack not made exclusively out of conductive rubber.
But. Now that I had a new phone pad, I wouldn't have to worry about bricking my old phone. All that much. So I went through a bunch of excruciating testing and failing yesterday to get something without ram-crippling bloatware and google applications that essentially force the 4x to run constantly at max speed.
What I seemed to be running into was two types of problems: a lot of the roms (custom firmware) were made by someone who was simply testing something new at the time, experimented a lot, and then left the project behind (or simply focused on other handsets). That's not necessarily a problem, but it can mean that you have stability issues you might not expect, and that has not been tested or reported while the project was active. And that might actually stop you from getting far enough to install some app that changes cpu-governor, ram-handling, and so on (even things like the standard keyboard/language variant.. kind of essential that that works). Install instructions also tend to link to outdated bootloaders, or have workaround suggestions that worked at the time, but now are obsoleted completely. The second problem was the OpenGapps - some of the core apps conflict with the builds' own apps.
And then there's the fact that the kernel in these roms tend to be from when the project was last maintained. I can't seem to decipher exactly what's going on, but I think a lot of the early roms were based on an old kernel with inserts (like the original one from LG). While the older builds on new kernel branches tend to have better support, but then have certain types of functionality simply gone completely. I don't know why that is, but the experience with this on linux laptops and android devices is what made me hold off until I had something that could replace the 4x before starting to try out some of the experiment builds people have.
So I went through getting the bootloader unlocked, trying a billion different methods before realizing they were all workarounds for the non-eu handsets - just use the oem-unlock method with fastboot. It's really as simple as it sounds. Use the "all in one" thing on the forum, set up the drivers, get root, and things like that - and then install a new, updated bootloader. I think after one of the official LG updates, everyone can actually use the oem-unlock.
Then I chose the wrong bootloader, apparently.. the cwm touch thing - superb bootloader. But apparently has some quirks that prevents it from installing certain firmware packages. I think it has something to do with consistency checking. I liked the idea of a multiboot, and didn't see why that wouldn't be extremely easy on android (with a storage size vs. cfw package being basically infinite to naught). But apparently what you want(need) is the twrp bootloader, and it has to be the last version. I don't know why that is, but you really don't want to be stuck - after basically wrecking your only boot - with an uninstallable image on your sdcard. So if you try something else than the "best one", just be prepared for an exit strategy with a backup and things like that before trying to install new images. There's also no way on these bootloaders to simply run a test first, nor is there a very easy way to partition the on-phone storage without having to start configuring install packages, so this is kind of awful if you're not actually deep into the development toolchains already.
I'd really love it if some of the tutorials said things like: our build really doesn't need a thorough wipe, and you can happily choose the file system you'd like, and the one that actually makes sense. For example. Or "for this cfw, you can just install gapps later on, that's going to work perfectly - don't force the install before you get through our own intro stage", etc. Alas.
Then I went through slimkat, an aosp lineage based rom, an old 4.1 rom, a new 5.1 rom, which all had different game-breaking problems. One refused to install gapps (note: you'll need the gapps that fit with the android version - but some packages simply won't install, period), another build had no sound other than on the speaker. One hanged randomly, another didn't scale the processor cores.
The good news is that this isn't really a problem - once you're set up you can just keep wiping and installing new ones. But it might be a really good idea to make a backup of your initial rom/custom firmware, just in case (i.e., you root, install the bootloader, and once you're in the bootloader, you make a backup of your current "rom" that is installed now. Then you can just revert to that without any problems later. I obviously didn't do that, because I was just fumbling around).
Some of the issues I ran into also might have workarounds, but I don't know - how would I, there's no way to actually tell what the problem is, or what it's related to. The most useful ones in the end seemed to be Vanir 6.0-based, and the one I ended up with, something called Euphoria on lollipop/5.1. That one seems to have all the hardware functions and benefitting a lot from a later kernel. I haven't done incredible amounts of testing on it yet, but it seems to work a lot better than the original firmware ever did.
And when you choose a gapps package, just go with the pico version. You can install everything you need after that from the store (and it takes less time than pre-installing the infinite amounts of crap in the stock package).
In sum - while you can get pretty far with the 4x on just rooting it and uninstalling some of the infinitely memory-hogging google crap, along with installing a new governor for the cpu and things like that. You can actually get something extremely neat by installing a new "rom"/cfw, that doesn't necessarily have the "oh, but you just have to forgo feature X, Y and Z because open source" problems.
I'm sure a cfw-developer is going to see this one day and roll their eyes back in their heads. And will have some very sharp words about the kind of effort that went into making a specific kernel, insert and build combination to even boot. But the later kernels seem to work really well.
And thanks to that Euphoria thing, I'm probably not going to use my new padphone-thing as much as I would. Because that one is over the "just testing stuff, getting it to work" stage. There's things with the home-button bar lighting up when there's notifications, things like that, that kind of show someone who used the handset was maintaining the build.
Anyway - I really recommend that you try out some different types to find these really good roms that works well. I'm sure there are lots of unknown cfw packages out there that work.. you know, for the 300 people who use it every day. That might be some of the early cfw variants with old kernels. And it might clearly also be some of the new ones, which I really didn't expect. Honestly, was kind of expecting stripes across the screen and hangs, but that didn't happen.
Optionally, a dev who actually knows what they're talking about could maybe suggest a list of cfw that have the later kernels that work, or the same kernels that Euphoria has Really, trying to search the net now, and find possible candidates was not easy.

RP2-specific fixes/updates with 9.0 update?

To those who have updated to Android 9.0, have you seen any improvements/fixes specific to the RP2? I know many of us have noted issues with the speakers (notably at lower volumes) and the camera software (mostly fixed by using Gcam), although there's been other more isolated/random issues for some too (Bluetooth, cellular signal, etc).

I haven't done extensive testing, but I do nelieve the small issues I've had with the speakers at low volumes are fixed. The only issue that I've seen in the last couple days I've had pie is that my wifi will randomly stop being able to access the internet, but turning wifi off and on fixes it and mostly a minor inconvienence. It's probably worth noting that I have Magisk with many modules installed.

Hangouts doesn't give a notification sound when the app isn't open. I've made another thread about that earlier
------------------------------------------------------------------------------
Never mind. Had to go deep into Hangouts settings to fix it. Still annoying

I would willingly trade fully functional wifi for speakers that don't crackle and cut out at lower volumes, since I have unlimited data and solid LTE signal everywhere I go. Though I've had that wifi issue on rare occasion on Oreo too.

They moved the clock :'(

Anyone notice potential decrease in touch sensitivity after the upgrade? I had a screen protector on and it seemed like I need to push down a little more to get the touches to register. Took off the protector to test and it was fine with just the screen. Put another one on and occasionally touches aren't registering or registering but releasing early on swipes.
Sent from my Phone 2 using Tapatalk

CalebQ42 said:
I haven't done extensive testing, but I do nelieve the small issues I've had with the speakers at low volumes are fixed. The only issue that I've seen in the last couple days I've had pie is that my wifi will randomly stop being able to access the internet, but turning wifi off and on fixes it and mostly a minor inconvienence. It's probably worth noting that I have Magisk with many modules installed.
Click to expand...
Click to collapse
How do you unlock your bootloader, bro? How did you root your phone?

acegrace said:
How do you unlock your bootloader, bro? How did you root your phone?
Click to expand...
Click to collapse
Follow the guide here, it's what I used to get everything under way. As long as you didn't install the latest OTA that dropped last week.
https://forum.xda-developers.com/razer-phone-2/how-to/root-pie-guide-t3910407

Gamesoul Master said:
Follow the guide here, it's what I used to get everything under way. As long as you didn't install the latest OTA that dropped last week.
https://forum.xda-developers.com/razer-phone-2/how-to/root-pie-guide-t3910407
Click to expand...
Click to collapse
crap, i just updated last night - can i factory reset and do the same thing?

alawiggle said:
crap, i just updated last night - can i factory reset and do the same thing?
Click to expand...
Click to collapse
Nah, you're good now. Warrior's thread (which the post I gave you directly references) has the updated boot image for MR1 (which is what you're on now), so just use that and you should be fine.
Oh! And turn off any unlock security (PIN, fingerprint, etc) you may have on before doing it. Just to be safe. You can turn it all back on when you're done rooting.

Gamesoul Master said:
Nah, you're good now. Warrior's thread (which the post I gave you directly references) has the updated boot image for MR1 (which is what you're on now), so just use that and you should be fine.
Oh! And turn off any unlock security (PIN, fingerprint, etc) you may have on before doing it. Just to be safe. You can turn it all back on when you're done rooting.
Click to expand...
Click to collapse
nice, thanks!

Stuck on rooted OOS 5.0.8 - Now what? OOS 9.x.x with(out) full wipe? Custom ROM?

Hi guys,
my OP3T is increasingly getting on my nerves and I'd love some input on what I should do next. I've been running rooted OxygenOS with TWRP and SuperSU - as far as I can tell, this is old technology. Every time Oneplus released an update, I'd download the full zip file, flash it in TWRP and flash SuperSU over it. Reboot and I'm up and running again right away.
Now with the OOS 9.x.x release issues, things are getting a bit more complicated - I think this might be the right point in time to do a full wipe, back up everything via Titanium Backup and start fresh with a new custom ROM that will (maybe) provide updates for the next year or two.
In general the OP3T is starting to get a little slow. Google Assistant is flakey (Sometimes doesn't activate properly on "OK Google", sometimes plays the beep and then doesn't record any commands, sometimes pops up behind the home screen icons so you can't read any of the text, sometimes just ignores the "OK Google") and the battery life is going downhill a little bit. I'm hoping a fresh wipe and maybe a new ROM will help here. I also need to take care of the earpiece issues - mine is clogged with dust, as are many Oneplus phones if Google results are anything to go by...
So I have a few options:
1. Sell the OP3T cheap (can't give it to my girlfriend because of the earpiece), buy a Pixel or some other phone
2. Upgrade the OP3T to OxygenOS 9.x.x and keep my data with this method (https://forum.xda-developers.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164)
3. Upgrade the OP3T to OOS 9.x.x, wipe everything and move to Magisk or something like that - what are my options here? Is Magisk the go-to method to get root these days?
4. Pick a custom ROM, wipe everything and just move to that. Anyone have a recommendation that's pretty much stock Android, stable and will likely receive regular security updates for the next one or two years? Easy updates with root would be a definite plus!
Any suggestions? Half of me is about ready to trash the OP3T and just get a Pixel now that I can't hear callers when I answer the phone

bemymonkey said:
...
Any suggestions? Half of me is about ready to trash the OP3T and just get a Pixel now that I can't hear callers when I answer the phone
Click to expand...
Click to collapse
You could get the ear piece and microphone ports cleaned.
You could do a clean install.
You could install custom ROMs
You could upgrade.
These are all choice you make.
My personal choice: I'm keeping my phone for at least 4 years. I'd be happy very with just OOS (I think it's the best rom I've ever used), but I want security updates. And for that reason I use LineageOS (I've been using it and CM since 2012).
You make your choice based on what matters too you.
Sent from my OnePlus 3T using XDA Labs

Hi Bill,
thanks for your answer.
Of course it's a personal choice that I'll have to make - I'm just looking to get some more info and pros/cons for each choice before wasting my time. Cleaning my earpiece is something that'll take an hour or so of careful fiddling (Is there a permanent fix to get it dustproof? Maybe an aftermarket dust gasket of some kind?), and backup/wipe/flash/restore is something that'll certainly take a chunk out of one of my weekends. All in all that's probably 12 hours of my life I'm not getting back.
Mainly what I want to know is: Is wiping the phone flashing a custom ROM like LineageOS viable for reliable day to day use on the OP3T? How has your experience been compared to OxygenOS in regards to:
-Updates (both security and Android version) - Is the update process seamless now or is it still done purely by a flash from recovery?
-Stability (I'm seeing only nightly builds on the LineageOS page [https://download.lineageos.org/oneplus3] - are there stable or even milestone builds?)
-Feature completeness compared to OxygenOS... do things like double-tap-to-wake work?
-Root... as I asked in my OP, what method is standard these days? Lineage suggests its "AddonSU" package but everyone else seems to say Magisk ist the way to go...?
-Is anything broken?
?
Does anyone else have alternative suggestions in regards to ROMs that may be exactly what I'm looking for? Something that looks and feels exactly like OxygenOS?

bemymonkey said:
...
Mainly what I want to know is: Is wiping the phone flashing a custom ROM like LineageOS viable for reliable day to day use on the OP3T? How has your experience been compared to OxygenOS in regards to:
-Updates (both security and Android version) - Is the update process seamless now or is it still done purely by a flash from recovery?
-Stability (I'm seeing only nightly builds on the LineageOS page [https://download.lineageos.org/oneplus3] - are there stable or even milestone builds?)
-Feature completeness compared to OxygenOS... do things like double-tap-to-wake work?
-Root... as I asked in my OP, what method is standard these days? Lineage suggests its "AddonSU" package but everyone else seems to say Magisk ist the way to go...?
-Is anything broken?
...
Click to expand...
Click to collapse
Updates: I dirty flash them in recovery once a month.
Security updates: Los gets them every month. OOS may get one more update, but that will be the last.
Completeness: I find Los as good as OOS. And Nlos (https://forum.xda-developers.com/on...elopment/rom-nlos-16-0-t3879405/post78433980) even has scrolling screenshots. Note: I don't care much about the camera as I rarely use it.
Root: I've been using Magisk since SuperSU became unsupported. I like it better than SuperSU. I have absolutely to problems with it.
Broken: nothing's broken for me.
But you would have known all of this if you read through the various threads. And there's no "best" rom as it's a subjective decision.
So jump in and try things for yourself.
Sent from my OnePlus 3T using XDA Labs