Black screen bug again in a few hours on cwb-test-4 :/.
You shouldn't need to do anything more than flash them to the active partition your on. And one fails . It's ok your still getting patch.Black screen bug again in a few hours on cwb-test-4 :/.
Does it matter which boot slot and vendor_boot they are installed in?
With cwb-test-4 by default it is installed in slot b, but I think other times it has been installed in slot a.
I just force install in both slots (boot and vendor_boot), but vendor_dlkm won't let me force it (Writing 'vendor_dlkm_a' FAILED (remote: 'No such file or directory')), by default it installs in slot b too.
thanks, I just documented about the 2 slots. I already understand how it works. Come from an op5 with a single slot.
hypothetical - if i have already flashed the 3 files but i did not use thefastbootD mode, is it okey to just flash the 3 files again but this time nin the fastbootD mode? no need to reinstall the rom?
v3 was better than v4. Issue seen on both, about once every 24-48h, but v4 seems to do it at random. With v3 I pinpointed it to a specific scenario (see my last post).
I confirm this. With v4 yesterday he was bug again, once every 24h. With v3 I only have a black screen once in just over 48 hours.
Don't use any of them, they were just for testing resolutions to the issue. None of them work. Waiting for OnePlus to release newer kernel sources since they haven't since .C44.
I think that in spite of everything, your patches work better than the stock, especially v3.
Yes, at least with movistar (spain). But the icon is not shown, even if the calls are really HD (volte or vowifi).
That would also interest me very much. I did it according to the wiki instructions. And there is no fastbootD.hypothetical - if i have already flashed the 3 files but i did not use thefastbootD mode, is it okey to just flash the 3 files again but this time nin the fastbootD mode? no need to reinstall the rom?
woud if be a better install if i flash first the 3 files before flashing the rom?
At least I know I'm not the only person with this problem anymore.
Ignore super_empty and vbmeta completely. Moving to LineageOS from C.63 should be fine.Nameless is dead, crDroid is not stable, so this is my last hope.
I am on c63 in both slots. i know the whole vendor_boot / btfo / boot replacement thing, my concern is the extra image files in the OP9 lineage directory and no mention anywhere in instructions or here in the comments.
and the 2 new image files im concerned about is...
I've pulled enough hair out of my head between nameless' maintainers rudeness and CrDroid's bugs, can anyone just tell me if I need to do anything with these files dated from a few days ago in the OP9 lineage directory?
also, c63(current latest) should be fine, right? i can MSM back to c62.
Also, if anyone wants to buy a OP9 phone in great condition, let me know. Seems this scene is on life support and it may already be time to change devices
I tried so much to make crDroid work, but it kept killing itself. I am on PixelExperience now and, so far, its perfect.
What is your-- LineageOS version: LineageOS Download url: Gapps version: Did you-- wipe: restore with titanium backup: reboot after having the issue: Are you using-- a task killer: a non-stock kernel: other modifications: Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed: