Greetings,
I updated to OOS 5.0 when it was first released and since updating to the latest Oreo based firmware I am experiencing a strange issue. My phone randomly freezes at the OnePlus logo. Is anybody else experiencing this?
I am currently running with the official Oreo based Resurrection Remix build and yesterday it happened again. So I guess it must be related to the Oreo firmware and not the Rom.
I never experienced this issue on Nougat or Marshmallow and it only happens randomly. Difficult it is, to determine the cause.
Peace
Related
Everytime i try to connect it just says Connecting... ----> Disabled ----> Saved Repeat
I tried LineageOS and ressurection Remix. It worked on LineageOS when i first tried it but when i updated to a more recent build it juist stopped working.
So i reinstalled LineageOS but then the wifi didn't work so i flashed the stock 5.0 firmware and it worked and i rooted again, installed ressurection remix and the same thing is happening.
I have exactly the same problem. With the stock rom it is working.
With the latest build OS 14.1-20170131-NIGHTLY-jagnm not.
I can see all networks but if I connect it fails with authentication error an deactivates the network after some retries
I update today to latest version 20170207 still the same
Same issue
I´ve just to install the lastest version "lineage-14.1-20170517-nightly-jagnm-signed", even this from Resurrection Remix "RR-N-v5.8.3-20170428-jagnm-OFFICIAL" and both togheter has the same issue.
Did anybody find any solution?
Regards, David
Also my phone encounter.....it seems a kernel problem
same here, only on stock rom wifi works fine, resurrection and lineage have the same issue, today 30/6/17 on latest lineage os version
I have a very strange issue.i was running resurrection remix rom since I bought OnePlus 3t.A month ago touch was not working on a small row.i tried several roms including official oxygen os nougat,but the issue persist.but when I upgraded to Oreo it was fixed automatically.then I reverted to nougat again,and the issue is back again.since it's not a hardware problem,what could be the possible fix?
I got my Z2 Force in late January and instantly unlocked the BL, flashed TWRP and Magisk, updated to Oreo and rooted as well. I am also running the 8.0 Pantheon kernel which runs smoothly so far. I was just wondering if there has been any significant development in roms for our phone. I love the near stock android Lenovo has pushed with the device, but I am really hoping to be able to at least get Lineage OS on the device. What's the biggest hurdle so far? At what stage is the rom at? I'm not asking for an ETA just wanted to see where the development process is at. Thanks guys!
Lineage and AOSIP have unofficial builds. There are some lingering issues before it can be official and released, like needing to fastboot -w and swapping slots, Sprint doesn't have LTE, etc...
im having issues too in the roms i have tried to build it is the whole A/B partition issue and i and having issues with radios. once i have ironed out my bugs i will try to release a rom that is Resurrection remix built but i still will need to make it moto mod compatible and that is a whole different story as i haven't even gotten to that part yet. stay tuned we are working on it for your guys.
WE LOVE THOSE OF YOU DEVELOPING FOR THIS PHONE SO MUCH please don't stop your amazing efforts!
Android version 7.1.2
Rom lineageOS 14.1 0503
Modern MPSS.TR.2.0-397339f
Does anyone have a similar situation?
random reboot under any time any app.
of course
gxj8885718 said:
Android version 7.1.2
Rom lineageOS 14.1 0503
Modern MPSS.TR.2.0-397339f
Does anyone have a similar situation?
random reboot under any time any app.
Click to expand...
Click to collapse
I've also facing the same problem.. but i cant find a fix for it
Do Not Update to Stable Oxygen OS 12, it is a Havoc, after updating my phone has no signals and it's unstable AF. Even after a hard reset. If you don't want to RIP you phone, wait for Oxygen OS 12.1 Update.
There's already multiple threads about the issues. No need for another
Redundant thread closed