Is there an Android 6 rom still updated for security? - ONE General

Hi,
Was using cyanogenOS but after the termination, went to android 7.x.x roms for security reasons. Sadly, all 7.x.x roms (omni, aosp and lineage) have terrible issues with Apple AirPods.
TLDR: Wanting to go back to a 6.x.x rom, but is there one that is up to date security-wise?
Thanks!

I would recommend you getting CM13 unofficial by sultanxda. You'll not regret it.

Gawd said:
I would recommend you getting CM13 unofficial by sultanxda. You'll not regret it.
Click to expand...
Click to collapse
Thanks! Exactly what I was looking for, will flash!

Gawd said:
I would recommend you getting CM13 unofficial by sultanxda. You'll not regret it.
Click to expand...
Click to collapse
Thinking of installing this. Want to stay away from nougat until xposed comes. Can I dirty flash this over a cm13 build?

BoboBrazil said:
Thinking of installing this. Want to stay away from nougat until xposed comes. Can I dirty flash this over a cm13 build?
Click to expand...
Click to collapse
No, perform a clean flash otherwise you might experience weird behavior. Always perform a clean flash unless updating to a newer build of the same type/ just like for nightlies.

Would it be too hard to update jgcaap's cm13 ROM with color os blobs to the latest security patches? I've seen it done before... I can't go to another ROM after using the color os blobs, and unfortunately jgcaap isn't updating the ROM anymore. His android 7.1.1 ROM is still using cm blobs. I'm one of the few who need xposed because I use micro g instead of google apps.

Related

Downgrade to Marshmallow to avoid bootloop?

My old Nexus 5X has already died with the bootloop issue, now I don't want to my Nexus 6P to die too..
Should I downgrade it to marshmallow?
I know that most people are claiming this as an hardware issue, but I actually don't believe on it, since both 5X and 6P with two completely different brands are getting the same problem, at the same time.
I'm also thinking of moving to CyanogenMod 14.1 (Not sure if anything changes..)
Curently I'm on Stock 7.1.1 NMF26F + FLASH-N6P Kernel
No! Suit yourself, but I would simply upgrade to N4F26I and enjoy your phone. There is nothing wrong with running stock and you have a good kernel. Viva! Saúde!
Until it boot loops like so many of us have had happen. If you are in warranty, the company is swapping them out with little aggravation. If you are not in warranty then maybe you have a good point. I for one will be running RR 6.0.1 until some real info comes out. Once was enough for me.
Sent from my Nexus 6 using XDA-Developers Legacy app
rcoliveirajr said:
My old Nexus 5X has already died with the bootloop issue, now I don't want to my Nexus 6P to die too..
Should I downgrade it to marshmallow?
I know that most people are claiming this as an hardware issue, but I actually don't believe on it, since both 5X and 6P with two completely different brands are getting the same problem, at the same time.
I'm also thinking of moving to CyanogenMod 14.1 (Not sure if anything changes..)
Curently I'm on Stock 7.1.1 NMF26F + FLASH-N6P Kernel
Click to expand...
Click to collapse
You realize that CyanogenMod is dead and that there will be no further development? People have been having the boot loop problems with custom ROMs as well as stock. Mine bootloops every time I flash updates, switch ROMs or try to restore a backup. So far I've always been able to get out of it. If your bootloader is unlocked every boot loop isn't necessarily the boot loop of death. But if your bootloader is locked you have pretty limited options to try and fix the phone. If you feel more comfortable on Marshmallow then just stay on your current ROM. But if you are going to flash a custom ROM I would stay away from CyanogenMod.
jhs39 said:
You realize that CyanogenMod is dead and that there will be no further development? People have been having the boot loop problems with custom ROMs as well as stock. Mine bootloops every time I flash updates, switch ROMs or try to restore a backup. So far I've always been able to get out of it. If your bootloader is unlocked every boot loop isn't necessarily the boot loop of death. But if your bootloader is locked you have pretty limited options to try and fix the phone. If you feel more comfortable on Marshmallow then just stay on your current ROM. But if you are going to flash a custom ROM I would stay away from CyanogenMod.
Click to expand...
Click to collapse
I know that CM is dead, but probably there will be unofficial development. I was thinking about it, because I would still have Nougat instead of Marshmallow..
My January OTA has just arrived, and I just blocked the notification, but I'm really thinking to flash the stock Marshmallow..
rcoliveirajr said:
I know that CM is dead, but probably there will be unofficial development. I was thinking about it, because I would still have Nougat instead of Marshmallow..
My January OTA has just arrived, and I just blocked the notification, but I'm really thinking to flash the stock Marshmallow..
Click to expand...
Click to collapse
CM will be replaced by Lineage OS.
Sent from my Nexus 6P using Tapatalk
Does anyone downgrade to Marshmallow?
Would you guys recommend me to do it?
jhs39 said:
You realize that CyanogenMod is dead and that there will be no further development? People have been having the boot loop problems with custom ROMs as well as stock. Mine bootloops every time I flash updates, switch ROMs or try to restore a backup. So far I've always been able to get out of it. If your bootloader is unlocked every boot loop isn't necessarily the boot loop of death. But if your bootloader is locked you have pretty limited options to try and fix the phone. If you feel more comfortable on Marshmallow then just stay on your current ROM. But if you are going to flash a custom ROM I would stay away from CyanogenMod.
Click to expand...
Click to collapse
Why do you say stay away from CM? It is actually very stable. I've had no issues with it besides the battery crap on N. The dedicated CM maintainers are working on Lineage OS still. They have released a few nightly builds, but not sure if they are going to try and get a automatic build server up and running again for the OTA nightly builds.
Jammol said:
Why do you say stay away from CM? It is actually very stable. I've had no issues with it besides the battery crap on N. The dedicated CM maintainers are working on Lineage OS still. They have released a few nightly builds, but not sure if they are going to try and get a automatic build server up and running again for the OTA nightly builds.
Click to expand...
Click to collapse
Lineage is starting from scratch. My understanding is that CM ceased to be open source after it was sold and Lineage can't simply update CM ROMs because that code is owned by the company that owns CM. There will be no more official development of current CM ROMs so I can't understand why anyone would want to use their ROMs. There are other ROMs that are in active development and are updated regularly so why not use them instead of CM?
I know this thread hour into the weeds regarding CM but in reference to downgrading, as I said before it's a judgement call. The boot loop of death does not appear to be happening on 6.0.1 so it's all about what you can deal with if it goes south on 7.x.x
Sent from my Nexus 6 using XDA-Developers Legacy app
CyberpodS2 said:
I know this thread hour into the weeds regarding CM but in reference to downgrading, as I said before it's a judgement call. The boot loop of death does not appear to be happening on 6.0.1 so it's all about what you can deal with if it goes south on 7.x.x
Click to expand...
Click to collapse
Some people have said it has happened to them on MM. Not sure how true it is but who knows.
---------- Post added at 03:13 PM ---------- Previous post was at 03:08 PM ----------
jhs39 said:
Lineage is starting from scratch. My understanding is that CM ceased to be open source after it was sold and Lineage can't simply update CM ROMs because that code is owned by the company that owns CM. There will be no more official development of current CM ROMs so I can't understand why anyone would want to use their ROMs. There are other ROMs that are in active development and are updated regularly so why not use them instead of CM?
Click to expand...
Click to collapse
Lineage IS CM. It literally is only a name change. If you go to the GIT you'll see, or even go to the CM thread. It's just the company and name is dead. All the source files were moved by maintainers and it was all rebranded to be called LineageOS. They just no longer have the pockets to run things the way it used to be.
And as far as custom Roms go, they are all the same. They are all either based on AOSP, or the Stock(Google) firmware of the device. They all carry the same features that they renamed to whatever the name of the ROM is. That has always been the problem with stock Android devices.
I have a 6p that does not know Nougat yet, I'll stick to MM until further clarification.
No issues - latest MM, SuperSU 2.79, Xposed v87 and Franco v28.
jhs39 said:
Lineage is starting from scratch. My understanding is that CM ceased to be open source after it was sold and Lineage can't simply update CM ROMs because that code is owned by the company that owns CM. There will be no more official development of current CM ROMs so I can't understand why anyone would want to use their ROMs. There are other ROMs that are in active development and are updated regularly so why not use them instead of CM?
Click to expand...
Click to collapse
Do some more research before releasing false information. Lineage OS isnt starting from scratch lol. Do you follow their threads or github? Cyanogen 7 was my first ROM on HTC Inspire...and it was BEASTMODE. They were pioneers on a digital frontier, and in my book OG. The name may be dead but Lineage is here to stay and they have all the OPENSOURCE code. Long live Cyanogen!!!!!
Well I downgraded as soon as the bootloop threads started to pop. Sorry to say it died in a week. Signs before the bootloop death, heat up, battery discharges rapidly, then whilst I was in a middle of a call, it rebooted to bootloop of death.
Uggg
Sent from my Nexus 6 using XDA-Developers Legacy app
Bad news, and there isnt official answer from Google
I was running MM and never once upgraded to N or used any beta previews always on MM. And mine started the bootloop of death 2 days ago. So I would say no don't downgrade it won't improve your chances of avoiding it
seand88 said:
I was running MM and never once upgraded to N or used any beta previews always on MM. And mine started the bootloop of death 2 days ago. So I would say no don't downgrade it won't improve your chances of avoiding it
Click to expand...
Click to collapse
That's actually good to know since the overwhelming majority of people on these threads seem certain that Nougat is to blame. Were you doing anything in particular when the boot loop hit?
---------- Post added at 11:50 PM ---------- Previous post was at 11:48 PM ----------
dogmatism said:
Well I downgraded as soon as the bootloop threads started to pop. Sorry to say it died in a week. Signs before the bootloop death, heat up, battery discharges rapidly, then whilst I was in a middle of a call, it rebooted to bootloop of death.
Click to expand...
Click to collapse
Hopefully your phone was still under warranty. Sounds like you got a lemon.
jhs39 said:
That's actually good to know since the overwhelming majority of people on these threads seem certain that Nougat is to blame. Were you doing anything in particular when the boot loop hit?
Sorry for the late reply. I was not doing anything at all. It was sitting in a cup holder as I was driving and thats when I noticed it looping.
Click to expand...
Click to collapse
CyberpodS2 said:
Until it boot loops like so many of us have had happen. If you are in warranty, the company is swapping them out with little aggravation. If you are not in warranty then maybe you have a good point. I for one will be running RR 6.0.1 until some real info comes out. Once was enough for me.
Sent from my Nexus 6 using XDA-Developers Legacy app
Click to expand...
Click to collapse
i do not understand what this thread is supposed to be about, are you people saying that a stock nexus 6p with no kernel mods or custom rom can just spontaneous go into a boot loop? and now people saying it can happen on MM and it is not just a N issue? or is this only for modded devices? or is it mainy something that ahppens on stock N?
my 6p has major battery issues and drains at about 1% per minute on stock MM, i need to RMA the phone now and it is on MM
i want to root it and install xposed so i do not want N , i found this thread looking to find out if a downgrade from N to MM is possible
so if my phone gets returned to me on N or if they send a new phone to me and it is on N, then am i stuck with N or can i downgrade in back to stock MM?
phone is not modded to root no TWRP no backup will i be able to get on MM if they return my phone on N or send a new one on N?

Android pay lineage os?

Hi, I am currently running stock 7.1.1 on my Nexus 6P, I love Android pay. I use it nearly every day. With CM14 on my previous phone I could not use it. Do you know if there is a workaround for it? Or should I just stick with stock
Etheralrealm said:
Hi, I am currently running stock 7.1.1 on my Nexus 6P, I love Android pay. I use it nearly every day. With CM14 on my previous phone I could not use it. Do you know if there is a workaround for it? Or should I just stick with stock
Click to expand...
Click to collapse
The normal workaround people use involves using Magisk, Phil's SuperSU and a compatible kernel. If you do I search through the ROM threads you should find lots of posts regarding how people got Android Pay to work on their rooted phones.
jhs39 said:
The normal workaround people use involves using Magisk, Phil's SuperSU and a compatible kernel. If you do I search through the ROM threads you should find lots of posts regarding how people got Android Pay to work on their rooted phones.
Click to expand...
Click to collapse
I've seen those, haven't seen it with the new Lineage OS. With the rooted stock ROM on my m9 it worked but not with a custom ROM. So would it be the same with Lineage?
Etheralrealm said:
I've seen those, haven't seen it with the new Lineage OS. With the rooted stock ROM on my m9 it worked but not with a custom ROM. So would it be the same with Lineage?
Click to expand...
Click to collapse
I know people are using it successfully on Pure Nexus, Megapixel Rom and Cortex Rom. If Lineage has built in Super user like it's predecessor you would need to turn that off because you need to be rooted with Phil's.
jhs39 said:
I know people are using it successfully on Pure Nexus, Megapixel Rom and Cortex Rom. If Lineage has built in Super user like it's predecessor you would need to turn that off because you need to be rooted with Phil's.
Click to expand...
Click to collapse
Thanks, I'm gunna try installing it in the morning.
Etheralrealm said:
Thanks, I'm gunna try installing it in the morning.
Click to expand...
Click to collapse
Did you have any luck with this?
Yes I did, I'm running the latest Lineage OS 14.1 Rooted and use Android Pay with my BOA card.
Edit: I could not get stock kernel to work, had to use ElementalX Kernel.
Etheralrealm said:
Yes I did, I'm running the latest Lineage OS 14.1 Rooted and use Android Pay with my BOA card.
Edit: I could not get stock kernel to work, had to use ElementalX Kernel.
Click to expand...
Click to collapse
I am pretty sure nothing works anymore. As long as the bootloader is unlocked, then you are screwed. This is the exact reason we need a root option without unlocking bootloader..

What Roms is everyone running?

What ROM's are people running on their Verizon LG V20? Im getting ready to root mine and go through that process. Looking over the ROM's though and they seem to be lacking. Back in the day we had tons of options, now we have a handful on XDA. Are there ROM's people are running that arent listed?
Using the LineageOS weekly builds and they've been pretty good. Mostly just missing out on the second screen though.
Ashalinia said:
Using the LineageOS weekly builds and they've been pretty good. Mostly just missing out on the second screen though.
Click to expand...
Click to collapse
Ive been trying to find screenshots as Im pretty particular on my OS. I used to love MIUI when it was around.
Lineage for ls997 is horrible I'm using emotion build 4-16
pbedard said:
Lineage for ls997 is horrible I'm using emotion build 4-16
Click to expand...
Click to collapse
Why is it horrible? And why is Emotion better?
Depend on what device u using
pbedard said:
Depend on what device u using
Click to expand...
Click to collapse
That's true for anything. Just going out on a limb here, I'm guessing since we are in the LG V20 forum its safe to assume we are using that device.
Next time come prepared with proof of your claim. With no proof and bold claims you sound like a fool.
as Android goes further the ROM field is super small now KK had the biggest amount of ROMS not a lot of this model I have this version too we have RR DU is coming down the line Lineage WETA AOKP Here is a list of ROMS https://www.androidfilehost.com/?w=search&s=us996&type=files
I have a ls997 and im running Paranoid Android.
I have a vs995 and I'm running XOSP ?
Did i pick the wrong phone i cant seem to find a whole lot of roms for the verizon variant I want a debloated stock or a twrp stock flashable that i can use magisk on it is inexcuseable how much verizon pushed onto this phone is it such a tall task do i really have to choose between having no root with a carrier bloated rom and a working 2nd screen to use a asop type rom?
mirrin said:
Did i pick the wrong phone i cant seem to find a whole lot of roms for the verizon variant I want a debloated stock or a twrp stock flashable that i can use magisk on it is inexcuseable how much verizon pushed onto this phone is it such a tall task do i really have to choose between having no root with a carrier bloated rom and a working 2nd screen to use a asop type rom?
Click to expand...
Click to collapse
The Verizon build of not so stock is probably what you're looking for. Stock based so everything works minus all the bloat. Has static at boot, search some of the other kernels, there is a few that fix static at boot.
mkfryan said:
The Verizon build of not so stock is probably what you're looking for. Stock based so everything works minus all the bloat. Has static at boot, search some of the other kernels, there is a few that fix static at boot.
Click to expand...
Click to collapse
that is what i tried first but the rom was not rooted...
Gre thanks
mirrin said:
that is what i tried first but the rom was not rooted...
Click to expand...
Click to collapse
Did you flash supersu or magisk? Not all roms come rooted...
None I had issues getting it to work had issues booting found weta it worked it has a janky root but it worked and Pokemon go worked and I don't even get the static lines on the screen...
BroeknOs to be
Currently I'm running stock OS on LightningZap! kernel (still in beta, but looking like I'll have a release soon).
I have gotten BrokenOs running quite well and smoothly. But lacking the second screen is what's holding me back.
On LG V20 AT&T (H910), btw...

Moto X Style XT1572 infinite bootloop

Happy New Year everyone!
I am out of ideas, I hope you could help me. I tried to flash and install Lineage OS on my Moto X Style.
Unlocking bootloader went fine, I installed new TWRP 3.2.1.0 and so far it was OK. I flashed LineageOS nightly from 25 Dec with GApps but it won't boot. I have booting animation and from time to time there is very short vibration, just fraction of a second every 3-4 sec. I left the phone for an hour, still stuck on booting animation. I tried to wipe data/cache, tried several other builds from December- all have the same issue. I proceed to other ROMs, all behave in the same way, infinite bootloop. I went to find some solutions on XDA, but nothing seems to work.
I tried restore from backup: https://forum.xda-developers.com/moto-x-style/general/nougat-stock-rom-moto-x-style-xt1572-t3718460 Did not work, I still had booting animation form Lineage OS, even that it suppose to be stock rom.
I try below method to restore stock rom: https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110
With this firmware: https://firmware.center/firmware/Motorola/Moto X Style/Stock/XT1572/ and android 7.0 But I constantly have error msg: "(bootloader) Preflash validation failed FAILED (remote failure)"
I tried to look for solutions but at this point it starts to getting quite too difficult to grasp what should I try next, I do not want to brick the phone for good.
Could you please give me any advice and suggestions? I have Lineage OS on three other devices, never had this type of issues before.
which firmware you were on when you unlocked bootloader and flashed Lineage? Marshmallow or Nougat?
antariksh said:
which firmware you were on when you unlocked bootloader and flashed Lineage? Marshmallow or Nougat?
Click to expand...
Click to collapse
Nougat, 7.0 for sure, with October security patch I think.
zonewelld said:
Nougat, 7.0 for sure, with October security patch I think.
Click to expand...
Click to collapse
Flash this TWRP: https://forum.xda-developers.com/showpost.php?p=74235571&postcount=917
Flash this LineageOS: https://forum.xda-developers.com/showpost.php?p=74980159&postcount=1054
It's a pretty stable build, you might able to get it to boot up.
antariksh said:
Flash this TWRP: https://forum.xda-developers.com/showpost.php?p=74235571&postcount=917
Flash this LineageOS: https://forum.xda-developers.com/showpost.php?p=74980159&postcount=1054
It's a pretty stable build, you might able to get it to boot up.
Click to expand...
Click to collapse
Holly! It boots! Thanks a lot!
I tried a lot of ROMs, but all on 3.2.1 TWRP, maybe that was the problem. Anyway it seems to be fine now, I am very grateful for your help with it.
All the best!
zonewelld said:
Holly! It boots! Thanks a lot!
I tried a lot of ROMs, but all on 3.2.1 TWRP, maybe that was the problem. Anyway it seems to be fine now, I am very grateful for your help with it.
All the best!
Click to expand...
Click to collapse
It wasn't only the TWRP issue. From Marshmallow to Nougat was a major update for our device. Once upgraded to Nougat the data partition format is F2FS am not sure, but hope you get my point.
Developers had to compile ROMs based on this new updated Kernel, Modem and Vendor.
I have been using this unofficial builds for a week now and they are stable. No major bugs.
You can also flash the official Nougat firmware image over fastboot, in case you you wanna go back to Stock.
In case you want to try this old ROMs, you have to flash Marshmallow modem and then it will boot.
antariksh said:
From Marshmallow to Nougat was a major update for our device. Once upgraded to Nougat the data partition format is F2FS am not sure, but hope you get my point.
Developers had to compile ROMs based on this new updated Kernel, Modem and Vendor.
I have been using this unofficial builds for a week now and they are stable. No major bugs.
You can also flash the official Nougat firmware image over fastboot, in case you you wanna go back to Stock.
Click to expand...
Click to collapse
Thanks, I will keep that in mind, but I think I am good for now, had enough of messing with this phone for next couple of weeks
Cheers!
zonewelld said:
Thanks, I will keep that in mind, but I think I am good for now, had enough of messing with this phone for next couple of weeks
Cheers!
Click to expand...
Click to collapse
hahahahaha fair enough. I just compiled Nuclea ROM based on LineageOS for Nougat Kernel and Modem. Feel free to try it next week. Uploading....
antariksh said:
hahahahaha fair enough. I just compiled Nuclea ROM based on LineageOS for Nougat Kernel and Modem. Feel free to try it next week. Uploading....
Click to expand...
Click to collapse
You're evil! I... must... resist... temptation....
Thanks for all your hard work for the community!

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.

Categories

Resources