Related
Hi there,
I'm trying the Lineage OS ROM on my Nexus 5. The rom working very well and I'm very satisfied of this, anyway I've noticed a little problem that comes when I update the nightly with the update tool available in Lineage OS rom.
The situation is this: I've installed the Pixel Launcher on the system partition, so I've organized all the folder in the home of the phone, when I flash a new nightly the Lineage OS will switch automatically to Trebuchet launcher (the default launcher) and I'll lost all the folder organization that I did.
I don't know if I'm doing something wrong in each rom update, but this situation is very annoying for me.
Anyone have experienced this issue? Some help for this?
Thanks.
askjafuji said:
Hi there,
I'm trying the Lineage OS ROM on my Nexus 5. The rom working very well and I'm very satisfied of this, anyway I've noticed a little problem that comes when I update the nightly with the update tool available in Lineage OS rom.
The situation is this: I've installed the Pixel Launcher on the system partition, so I've organized all the folder in the home of the phone, when I flash a new nightly the Lineage OS will switch automatically to Trebuchet launcher (the default launcher) and I'll lost all the folder organization that I did.
I don't know if I'm doing something wrong in each rom update, but this situation is very annoying for me.
Anyone have experienced this issue? Some help for this?
Thanks.
Click to expand...
Click to collapse
did you ever get this sorted ? Having same issue...
Tommmii said:
did you ever get this sorted ? Having same issue...
Click to expand...
Click to collapse
Sounds like a job for magisk or a different ROM with a launcher you like better.
Hi!
Lately, certain area of my screen weren't responsive while on a custom rom. Strangely after updating it to OOS5, the issue is gone. Now, whenever i try roms other than the OOS5, the issue persist again. Anyone who experience the same issue as me or have the explanations to this weird, unorthodox oneplus 3 behavior?
Thanks in advance
Which other ROMs did you try? Did they include the firmware? Did you flash the correct one if they did not?
Firmware for Nougat does not work on all Oreo ROMs, depends on which blobs developer is using.
Sent from my ONEPLUS A3003 using Tapatalk
morphvale said:
Which other ROMs did you try? Did they include the firmware? Did you flash the correct one if they did not?
Firmware for Nougat does not work on all Oreo ROMs, depends on which blobs developer is using.
Click to expand...
Click to collapse
The first rom that i noticed the issue was from the PA 7.3.1 which the firmware is included. Apart from that is the AICP 13 where the developer ask to flash firmware before the OO5 but i tried both firmwares from the OOS4.5.1 to 5. Still the problem persists. To clarify things, the issue was there when I was still in Nougat. I thought it was the hardware issue. But ,right after the OOS5 came out and I flashed it the issue's gone. Strange right?
Hi I am sorry that you are experiencing this issue.
OOS4.5.1 is basically the cause of your issue. If you opt to flash any other N-based ROM after flashing OOS4.5.1, you are bound to experience screen not responding.
The only way to resolve this issue is if you use any 8.x based OOS; be it stable or open beta.
Bobbi lim said:
Hi I am sorry that you are experiencing this issue.
OOS4.5.1 is basically the cause of your issue. If you opt to flash any other N-based ROM after flashing OOS4.5.1, you are bound to experience screen not responding.
The only way to resolve this issue is if you use any 8.x based OOS; be it stable or open beta.
Click to expand...
Click to collapse
Hey! thanks for the info m8. Really appreciate it. Am I safe to flash any other N ROMs after flashing the OOS Oreo without gettin the issue?
screen flickering or glitches on custom Roms like OMNI,PIXEL, Resurrection remix etc have same issue.... any solution?
A logcat sent to the ROM dev might be an idea.
Kaleem_qadir said:
screen flickering or glitches on custom Roms like OMNI,PIXEL, Resurrection remix etc have same issue.... any solution?
Click to expand...
Click to collapse
Wrong firmware
XDRdaniel said:
Wrong firmware
Click to expand...
Click to collapse
thanks for reply
i have oneplus 3 (A3003) .... which rom you suggest?
Kaleem_qadir said:
thanks for reply
i have oneplus 3 (A3003) .... which rom you suggest?
Click to expand...
Click to collapse
You can have any ROM so long as you have the matching firmware. Check in the ROM's thread.
tnsmani said:
You can have any ROM so long as you have the matching firmware. Check in the ROM's thread.
Click to expand...
Click to collapse
flashed 3/3T lineage and AOSP Roms. any difference between and 3T roms?
Kaleem_qadir said:
flashed 3/3T lineage and AOSP Roms. any difference between and 3T roms?
Click to expand...
Click to collapse
Unless it says Unified or 3/3T, they are different and flashing the wrong one can brick your phone.
Still not solving
I am still having issues. My nav bar gets a mirror effect on the uperside of the screen
I have a Oneplus A3000
Hello i have the same issue have you got any solution ?
I replaced my crack screen last month and last night I tried flashing AOSIP rom (From latest Open Beta) and got screen flickering and glitches to the point it was unusable. Wiped my phone clean again and tried RR rom and got the same flickering and glitches. Now I'm back to latest Open Beta. I wonder wether my new screen is the problem that caused me unbale to flash aosp roms? Because before my screen cracked I tried almost every rom and it's fine. Any idea guys?
I have the same problem, and I do too had my screen replaced, but some folks on OnePlus forum said that never replaced the screen
I tried many diferent versions of the firmware, and nice looking none fix for me
I have the same problem too, I've tried many kernels and many ROMs, it seems that only Sultanxda's ROM and Official ROM can be used. I've tried to compile MoKee with Sultanxda's Kernel source, it worked perfectly too. So I think that there maybe something kernel related is broken, and only Sultanxda fixed that. Maybe you could try it.
Thanks for reply . Los 14.1 and miui 9 are also ok
I've the same issue, and I think for the same cause because I replaced my cracked screen also, maybe OnePlus 3 have something like knox on samsgung where it'll be broken when rooted, Waiting to see if there's some kind of a solution because if the OOS (or OOS Beta) works fine it could be a kernel or firmware issue.
So it looks like the problem is with the replacement screen. Funny, because this is the 2nd time I replaced the screen (dont ask) but I didn't have flickering problem with the first one. Hopefully any talented devs can figure out the issue and resolves it, will gladly help however I can.
The change was merged:
h t t p s://review.lineageos.org/#/c/208861/
Maybe you could try the next build of LineageOS to see if the issue was fixed.
Lukedyue said:
The change was merged:
h t t p s://review.lineageos.org/#/c/208861/
Maybe you could try the next build of LineageOS to see if the issue was fixed.
Click to expand...
Click to collapse
thanks a lot .. i wil try this weekend for sure
Lukedyue said:
The change was merged:
h t t p s://review.lineageos.org/#/c/208861/
Maybe you could try the next build of LineageOS to see if the issue was fixed.
Click to expand...
Click to collapse
I've just installed it and still the same issue (The 2018-03-05 version)
N.B :
You can activate "Show surface updates" from the Developer Options Menu and the screen will not have those glitches anymore, because I realized that the glitches will go away whenever you update the screen.
rsm23 said:
I've just installed it and still the same issue (The 2018-03-05 version)
N.B :
You can activate "Show surface updates" from the Developer Options Menu and the screen will not have those glitches anymore, because I realized that the glitches will go away whenever you update the screen.
Click to expand...
Click to collapse
Well, by "next" I mean builds from 20180309 onwards.
Tried the 12-03 release, it does fix the screen errors, touch stop working if the screen is turned off, I need to reboot to it work again
Hi,
My screen just stops working after MI logo on all AOSP based custom ROMs. It simply powers off completely. I have tried Lineage OS 15.1, Arrow OS pie, Bootleggers ROM pie, and its the same on all of them.
I know the custom ROMs boot because i can hear the screen lock/unlock sound when I press the power button.
Tried wiping cache/dalvik; installing only rom, without Magisk. Don't know what else to try, but I really don't want to use MIUI because the main reason I bought this phone is because it has a rich dev community.
Also, the latest version of TWRP works, but RedWolf recovery has the same problem as AOSP ROMs: Screen just shuts off and after MI logo, but I know the recovery has started because it shows my devices' files on my PC when plugged into USB.
Stock MIUI, and MIUI AM custom ROM I have tried work just fine: The screen works perfectly normal.
Does anybody know of a fix, or has a similar issue? I have bought this phone to install an Open Source system and not be dependent on Google anymore, but now I'm stuck on MIUI which has both Google and Xiaomi bloat
Any help would be highly appreciated. My phone is Redmi Note 5 - Global edition (Whyred). I got it a month ago, and tried flashing as soon as my 360h unlock period expired.
Thanks in advance!
EDIT: After digging, I have found out that other people have the same issue with Huaxing screens. Has anyone found a fix for this so far, or has info if someone is working on it?
Same Issue
I've same issue Please someone guide us who know about this issue please please
Flash NoName Kernel after your Rom and you're good to go. Can't explain why tho..
edit: or Derp (actually using this one with RR Rom / Oreo)
Is there please someone who can help me?
I have an unlocked willow device.
But when I install any custom rom (AOSP like - Android 12 or 13) the display will not light on first power button press after going to deep sleep or display lock. It will take several button pressing, until the display will come alive/wake up.
Sometimes it seems, that the display is unlocked, but is at lowest brightness level. The hardware is okay. I changed the power button pcb already.
The latest MIUI firmware rom (from xiaomifirmwareupdater.com) runs without bug. Its a A11 image.
Is this a bug maybe in the vendor file? Is there any other solution than staying on stock rom MIUI A11?
Thx for your feedback in advance!
kerberos666 said:
Is there please someone who can help me?
I have an unlocked willow device.
But when I install any custom rom (AOSP like - Android 12 or 13) the display will not light on first power button press after going to deep sleep or display lock. It will take several button pressing, until the display will come alive/wake up.
Sometimes it seems, that the display is unlocked, but is at lowest brightness level. The hardware is okay. I changed the power button pcb already.
The latest MIUI firmware rom (from xiaomifirmwareupdater.com) runs without bug. Its a A11 image.
Is this a bug maybe in the vendor file? Is there any other solution than staying on stock rom MIUI A11?
Thx for your feedback in advance!
Click to expand...
Click to collapse
if it's not a hardware issue it's the firmware or you did a dirty flash ?
No dirty flash. Always clean install. I think that there could be a major bug in all custom images for Willow devices. I tested several custom rom. None worked correctly.
Is there noone else with a Willow and the same problem?
And is it the vendor Image part i should flash over custom rom's vendor part? Then the custom Image does not boot anymore...
Any help is appreciated. Thx!
This evening I mixed up dtbo, modem, efs partitions from MIUI official A11 rom with a current A13 custom rom. Now the display works as expected.
Maybe I messed something up myself some months ago. Now i have a backup of a working system. That is good!
Gonna try flashing some custom A13 rom(s) again and test If it will break the "display wake up" again.