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
Related
Hi all, I'm just wondering if there are others that have similar issue than mine?
The problem is that after updating my phone to CM13 20160922 version and any newer version, the touch screen would not work anymore on the ROM. Touch screen would still work in recovery.
I've tried to clean wipe before installation of ROM and the same problem persists.
If it helps, when I tried to install a new kernel (Xcelerate one) on the working ROM, the touch screen would also break.
Any help would be appreciated.
Do a clean install (by wiping cache, system, data) if you havent, and see if it helps. Can only suggest to take full logs (incl dmesg, and lastkmsg) and fetch it to fefifofum on the respective thread. Is the behaviour consistent or random? I face it randomly but I guess mine is a hardware fault.
The behavior is consistent. It always breaks the touch screen on the newer roms. I'll try to fetch the logs and maybe it would help. Thanks.
Anyone can help me with getting logs without a touch screen? ADB can't seem to connect and the device is unauthorized. Thanks for any help.
Well you are not the only one. Its all about drivers in kernel. I changed my digitizer and then with 6 or 7 touchscreen does not work although all fine in TWRP 3.0.2 Someone has to port those drivers to new kernel used in Android 6. i have little knowledge about it but i will try to fix it and if it works i will post it here-
mobaddict said:
updating my phone to CM13 20160922 version and any newer version,
Click to expand...
Click to collapse
wait do you mean it was working on cm13 before those versions ???
bauuuuu said:
wait do you mean it was working on cm13 before those versions ???
Click to expand...
Click to collapse
Yes, older CM13 version works. According to CM13 thread, it is the driver that doesn't work. I don't know how to fix the issue since this is a replacement screen and the driver works on older CM13.
... i will check
mobaddict said:
Yes, older CM13 version works. According to CM13 thread, it is the driver that doesn't work. I don't know how to fix the issue since this is a replacement screen and the driver works on older CM13.
Click to expand...
Click to collapse
OK.. I found the issue and fixed it. Atleast on my phone now the touch screen is working. I do not know the characteristics of you changed touchscreen but i can give you newly compiled version of cm13. You can confirm me if thats working for you !
bauuuuu said:
OK.. I found the issue and fixed it. Atleast on my phone now the touch screen is working. I do not know the characteristics of you changed touchscreen but i can give you newly compiled version of cm13. You can confirm me if thats working for you !
Click to expand...
Click to collapse
Okay. I can try. This is a replacement touch screen and is not an original one. I can try the compiled version that you made and see if that would fix the problem. Thanks
mobaddict said:
Okay. I can try. This is a replacement touch screen and is not an original one. I can try the compiled version that you made and see if that would fix the problem. Thanks
Click to expand...
Click to collapse
https://github.com/armani-dev/andro...mmit/7687212b3b2c083ac1929d3957239c76098bd886 its merged in the main device tree so i hope all the builds (and not only cm13) henceforth will be ok. i didnt get the time to compile everything yet.
bauuuuu said:
https://github.com/armani-dev/andro...mmit/7687212b3b2c083ac1929d3957239c76098bd886 its merged in the main device tree so i hope all the builds (and not only cm13) henceforth will be ok. i didnt get the time to compile everything yet.
Click to expand...
Click to collapse
Thank you. I'll try to check if this would work.
mobaddict said:
Thank you. I'll try to check if this would work.
Click to expand...
Click to collapse
I'll just wait for a kernel build since I don't know how to do this hehe
I am also facing the same problem after replacing my original broken touchscreen. I am not able to upgrade my rom to cm-14.1. Please suggest some help.
debasarkar said:
I am also facing the same problem after replacing my original broken touchscreen. I am not able to upgrade my rom to cm-14.1. Please suggest some help.
Click to expand...
Click to collapse
I think we just need to wait for a new build of the kernel and test if this solves our problem. I'm also waiting for a kernel build and will test it out if this would fix the issue. :good:
I don't know if the commit that was made by @bauuuuu was used in the new build of CM14.1 but the latest rom still has the touch screen issue. The new TWRP 3.0.2-1 is now also facing the same problem.
Looking at the source of CM14.1 kernel, the commit used was there so this means that this modification did not fix the touch screen issue for my device. Hoping to be able to find another solution
mobaddict said:
Looking at the source of CM14.1 kernel, the commit used was there so this means that this modification did not fix the touch screen issue for my device. Hoping to be able to find another solution
Click to expand...
Click to collapse
https://review.cyanogenmod.org/#/c/174024/
keep eye on new build there are more changes to match your touchscreen
bauuuuu said:
https://review.cyanogenmod.org/#/c/174024/
keep eye on new build there are more changes to match your touchscreen
Click to expand...
Click to collapse
Oh, wow! Hope that the 100Hz does the trick for my touchscreen and for others that are facing the same issue as me. Thank you for posting that. :good:
TWRP test build
Here is a test build for those with touchscreen issues. Please let me know if it works:
https://www.androidfilehost.com/?fid=313042859668276642
Seems that there are DU builds for the HTC 10 (pme). Here: https://download.dirtyunicorns.com/pme/
Has anyone tried them? If yes, what are your impressions? :laugh:
errikosd said:
Seems that there are DU builds for the HTC 10 (pme). Here: https://download.dirtyunicorns.com/pme/
Has anyone tried them? If yes, what are your impressions? :laugh:
Click to expand...
Click to collapse
It is AOSP based compared to LOS (CM) which the majority of the ROMs posted are.
DU is a great ROM. I found that it lacked some important features that I like, but a very solid ROM.
Yes i tried on Sprint but there was no data...even after entering the apn in
errikosd said:
Seems that there are DU builds for the HTC 10 (pme). Here: https://download.dirtyunicorns.com/pme/
Has anyone tried them? If yes, what are your impressions? :laugh:
Click to expand...
Click to collapse
Encryption was not working, even with a full data format prior to flashing.
Any other opinions?
I have been running the weekly and official builds with nebula eas kernel for about 5 weeks or so. I personally feel its the best non-sense based ROM for my usage. It does lack some customisations most others have but makes up for it by being super stable, fast, battery friendly and just works as its supposed to with bull. I use superSU, substratum and A.R.I.S.E audio mod with selinux permissive without dramas.
mrrflagg said:
I have been running the weekly and official builds with nebula eas kernel for about 5 weeks or so. I personally feel its the best non-sense based ROM for my usage. It does lack some customisations most others have but makes up for it by being super stable, fast, battery friendly and just works as its supposed to with bull. I use superSU, substratum and A.R.I.S.E audio mod with selinux permissive without dramas.
Click to expand...
Click to collapse
Does it come with root or Magisk out of the box?
To reverse the question, can I use it as clean Android without root, passing SafetyNet? Thanks!
errikosd said:
Does it come with root or Magisk out of the box?
To reverse the question, can I use it as clean Android without root, passing SafetyNet? Thanks!
Click to expand...
Click to collapse
It comes WITHOUT root. So you can choose your preffered method or no root at all.
I don't know about safetynet as I am not using android pay or anything that relies on it to pass.
Also I have not had any encryption issues as someone earlier replied
mrrflagg said:
I have been running the weekly and official builds with nebula eas kernel for about 5 weeks or so. I personally feel its the best non-sense based ROM for my usage. It does lack some customisations most others have but makes up for it by being super stable, fast, battery friendly and just works as its supposed to with bull. I use superSU, substratum and A.R.I.S.E audio mod with selinux permissive without dramas.
Click to expand...
Click to collapse
What firmware and TWRP Version are you using with it ? With the Nougat firmware and latest TWRP, I get the encryption issue..
Scutariu said:
What firmware and TWRP Version are you using with it ? With the Nougat firmware and latest TWRP, I get the encryption issue..
Click to expand...
Click to collapse
401.4 FW and 3.1.0 TWRP. What kind of encryption issue? I did have once only rebooted into recovery and it asked for the password but I just rebooted in recovery from TWRP and it never happened again.
mrrflagg said:
401.4 FW and 3.1.0 TWRP. What kind of encryption issue? I did have once only rebooted into recovery and it asked for the password but I just rebooted in recovery from TWRP and it never happened again.
Click to expand...
Click to collapse
I've tried several combinations, with older/latest firmware.
Every time, It would ask for the encryption password on bootup.
Even if I haven't set one up.. With data format prior to installing
Anyway, got sick of re-setting apps on my phone, just installed Maximus HD ROM, and that's that ?
Dirty Unicorns
errikosd said:
Seems that there are DU builds for the HTC 10 (pme). Here: https://download.dirtyunicorns.com/pme/
Has anyone tried them? If yes, what are your impressions? :laugh:
Click to expand...
Click to collapse
The 4-8-17 build is Android 7.1.2 and so far it is running really well. I am surprised that there is not a thread in the ROM section for DU.
morr22066 said:
The 4-8-17 build is Android 7.1.2 and so far it is running really well. I am surprised that there is not a thread in the ROM section for DU.
Click to expand...
Click to collapse
I think it was the DU team's decision to close all and not allow any XDA threads. Someone correct me if I am wrong.
No idea why though.
morr22066 said:
The 4-8-17 build is Android 7.1.2 and so far it is running really well. I am surprised that there is not a thread in the ROM section for DU.
Click to expand...
Click to collapse
A quick question.
What variant , firmware and TWRP are you using?
Everytime I try that rom..it encrypts itself with an unknown password, and upon restart I'm unable to access my phone
Encryption
Scutariu said:
A quick question.
What variant , firmware and TWRP are you using?
Everytime I try that rom..it encrypts itself with an unknown password, and upon restart I'm unable to access my phone
Click to expand...
Click to collapse
I have had that happen when switching from a sense based ROM to LOS or AOSP and it's a "pita"... Anything that I want to keep gets moved to my SD card before I reboot to recovery.
I read through several threads and tried several possible solutions so I can't remember exactly which one worked.
I am currently on Verizon, official Nougat with the flashed us unlocked "patch", TWRP 3.1.0-1. If you are on Verizon or Sprint you need to patch the image with a missing image that is found in the us unlocked model (there are threads discussing it where you can find the file).
LOS
Scutariu said:
A quick question.
What variant , firmware and TWRP are you using?
Everytime I try that rom..it encrypts itself with an unknown password, and upon restart I'm unable to access my phone
Click to expand...
Click to collapse
The Lineage is wiki spells things out pretty well.
https://wiki.lineageos.org/devices/pme/install
Here is another thread on twrp issues
https://forum.xda-developers.com/htc-10/how-to/guide-fix-pin-pattern-password-t3538438
morr22066 said:
The Lineage is wiki spells things out pretty well.
https://wiki.lineageos.org/devices/pme/install
Click to expand...
Click to collapse
It was not related to the data partition.
The format user data was done prior and after flashing it.
There is a DU Oreo-based build for the HTC 10: https://download.dirtyunicorns.com/?device=pme
For the time being it is under "RC". Downloading now, will report back!
Edit: ROM is very nice and is flying by. Only downside is that camera app is VERY slow... Also, woofer is not working (as expected).
What I like the most is that it is AOSP, i.e. no LineageOS stuff like AudioFX, etc. Customisation features are nice and the experience is close to Pixel with Stock OpenGapps. If the camera app is fixed, then this would be perfect (I believe it will, since this is the first RC release)!
Further notes: Capacitive buttons backlight is off by default (can't find any standard option to turn on, maybe with a kernel tool?) and notification LED does not work either. Don't mind for the capacitive buttons too much, but the LED is a real problem.
errikosd said:
There is a DU Oreo-based build for the HTC 10: https://download.dirtyunicorns.com/?device=pme
For the time being it is under "RC". Downloading now, will report back!
Edit: ROM is very nice and is flying by. Only downside is that camera app is VERY slow... Also, woofer is not working (as expected).
What I like the most is that it is AOSP, i.e. no LineageOS stuff like AudioFX, etc. Customisation features are nice and the experience is close to Pixel with Stock OpenGapps. If the camera app is fixed, then this would be perfect (I believe it will, since this is the first RC release)!
Further notes: Capacitive buttons backlight is off by default (can't find any standard option to turn on, maybe with a kernel tool?) and notification LED does not work either. Don't mind for the capacitive buttons too much, but the LED is a real problem.
Click to expand...
Click to collapse
Yea I'm having that sane problem with the touch key lights not working n it bothers me a bit. I didn't notice if the led was working or not. Keep me posted if u figure out the the key problem plz.
Hi,
I have search around but do not find what should be done with twrp in order to keep miui for ota with normal install.
I want to flash a kernel on miui.
Shall i keep read only ?
Shall i disable dm-verity ?
I already went once after flashing magisk to screen please enter Android password. Reboot solve the issue by the way.
Thanks
there is a kernel for miui roms? the only one I saw were for aosp / lineage
gohan456 said:
there is a kernel for miui roms? the only one I saw were for aosp / lineage
Click to expand...
Click to collapse
Blackbox kernel - currently brightness issue
rodolphe06 said:
Blackbox kernel - currently brightness issue
Click to expand...
Click to collapse
Blackbox is for AOSP, not MIUI...
Ok so i finally just flashed no name kernel without anything else and all ok.
Gonna try also bb
AnTuTu 95k...
On internet they spotted 112k
Edit:
It seems it broke something as i Can not anymore call.
I tried to restore boot but i Can only Receive call now.
Error sim is displayed.
What Can i do ?
Factory reset ?
rodolphe06 said:
AnTuTu 95k...
On internet they spotted 112k
Edit:
It seems it broke something as i Can not anymore call.
I tried to restore boot but i Can only Receive call now.
Error sim is displayed.
What Can i do ?
Factory reset ?
Click to expand...
Click to collapse
Dude, we are telling you 3rd time, its for AOSP roms. Of course it broke something, its for AOSP, not for MIUI.
rodolphe06 said:
AnTuTu 95k...
On internet they spotted 112k
Edit:
It seems it broke something as i Can not anymore call.
I tried to restore boot but i Can only Receive call now.
Error sim is displayed.
What Can i do ?
Factory reset ?
Click to expand...
Click to collapse
Reflash the stock rom.After that if you want to flash any custom kernels then try blackbox kernel(latest one).It supports MiUi roms
Incogn said:
Dude, we are telling you 3rd time, its for AOSP roms. Of course it broke something, its for AOSP, not for MIUI.
Click to expand...
Click to collapse
No offence but You are telling wrong:
Blackbox 1.3 support miui (see OP)
Noname has a miui version shared in telegram owner group
Hi, I'm facing this issue with my oneplus 3 on custom roms based on android pie..it still happens and has become very difficult for me to use. im very eager to use pie on my device :/ .I've tried Havoc 9.0, Nitrogen OS 9.0, Pixel Experience and even skydragon but it still happens. Whenever the phone goes to sleep or i lock it, and then when i try to wake it up from the lock using either fingerprint or power button, the screen lights up in black and the two capacitive buttons light up, i can hear a lock screen sound also, but the display stays black. but the rom works like it should until the display doesnt turn off.. i have to reboot the device completely to solve it.. currently im on oxygen os 5.05. someone please help
Is your display original or has it been replaced? I have same problem because i replaced broken original LCD with cheap one from eBay.
I agree too facing the same issue and it's seems to be because of the duplicate display panel. I too replaced my display panel with a duplicate one recently and facing this issue (pressing the power button, but screens turns to black but pressing the power button again and again turns it on) since then. Not only pie ROM but also on Oreo custom roms. Only pie ROM that seems to be working is Nitrogen OS. There may be some problem or mismatch with display drivers. Also the profiles like SRGB and others are not working.
No problem on OOS 5.0.6
yeah man.. its a duplicate display :/ is there any workaround for this?
I asked in a telegram group. A person said a commit is required for third-party display to work.
I am not too much in development thing. So if anyone from you can search for it. That could help.
---------- Post added at 06:04 AM ---------- Previous post was at 05:55 AM ----------
http://github.com/LineageOS/android...mmit/8e9f68f01764d96669f6040bf9ae0c8ea4ec55e1
A person on telegram gave me this link to the commit.
I forwarded the commit and the message to Dev of Havoc OS. He said he will ask the holy angel for what he can do.
Hope he looks after it.
@pantu99 @stepi1
The latest skydragon rom comes with the fix for the panic we are facing. You can test it. I can't test right now.
Let me know too, if it works or not.
Piyush lalwani said:
@pantu99 @stepi1
The latest skydragon rom comes with the fix for the panic we are facing. You can test it. I can't test right now.
Let me know too, if it works or not.
Click to expand...
Click to collapse
great ! i shall test it right away.. hope it works.
just installed the latest build of the rom.. nope still the same issue..
pantu99 said:
great ! i shall test it right away.. hope it works.
Click to expand...
Click to collapse
pantu99 said:
just installed the latest build of the rom.. nope still the same issue..
Click to expand...
Click to collapse
Seems some additional commits are required.
Can you ask developer of Franco kernel about the comitts maybe he can help.
Piyush lalwani said:
I agree too facing the same issue and it's seems to be because of the duplicate display panel. I too replaced my display panel with a duplicate one recently and facing this issue (pressing the power button, but screens turns to black but pressing the power button again and again turns it on) since then. Not only pie ROM but also on Oreo custom roms. Only pie ROM that seems to be working is Nitrogen OS. There may be some problem or mismatch with display drivers. Also the profiles like SRGB and others are not working.
No problem on OOS 5.0.6
Click to expand...
Click to collapse
So OOS 5.0.6. doesn't have any issues with cheap display replacements?
j03x2 said:
So OOS 5.0.6. doesn't have any issues with cheap display replacements?
Click to expand...
Click to collapse
Yes I am using it currently. And Franco kernel also doesn't has any problem.
Other kernel give problems.
NitrogenOS also works. Guys please find a workaround, very hard to find better displays in market
Installed NitrogenOS 8.1 with fk-r39-anykernel2.zip (Franco Kernel) and everything works just fine now.
Interestingly, the problem persists in TWRP (I cannot let the display sleep during backup or restore otherwise, I cannot switch the display back on).
j03x2 said:
Installed NitrogenOS 8.1 with fk-r39-anykernel2.zip (Franco Kernel) and everything works just fine now.
Interestingly, the problem persists in TWRP (I cannot let the display sleep during backup or restore otherwise, I cannot switch the display back on).
Click to expand...
Click to collapse
Nitrogen OS pie didnt had the problem with stock kernel too
Try it.
Fkr39 why not the latest?
Piyush lalwani said:
Nitrogen OS pie didnt had the problem with stock kernel too
Try it.
Fkr39 why not the latest?
Click to expand...
Click to collapse
There is no suitable version of Xposed framework for NOS 9 (pie).
Fkr44 (latest version of the kernel) showed more lag time before the screen turns on (like 2-3 sec).
Had the best experience with the older kernel.
Any fixes or working rom guys ? I really want pie in my OnePlus 3
Have you tried Resurrection Remix?
I had a similar issue with Havoc even with the original screen. So far, RR has been fine.
I have redmi note 5 pro indian version with huaxing display panel so if i flash any custom rom other than miui based rom it just shows a black screen ie no display so can anyone fix this?
I don't think Xiaomi will provide updated source codes
In recovery?
htchd2sucks said:
In recovery?
Click to expand...
Click to collapse
Recovery had the same issue earlier but latest builds fixed the issue
Now the issue is with roms
rahulrulz said:
Recovery had the same issue earlier but latest builds fixed the issue
Now the issue is with roms
Click to expand...
Click to collapse
Yes, I informed the various recovery devs about that, I know it was fixed on latest versions.
I'm surprised it's not working for ROMS, I though the problem was fixed...
Have you tried telling that to the roms dev? I doubt anyone will read that here in this questions section...
The latest PE rom (https://forum.xda-developers.com/redmi-note-5-pro/development/rom-pixel-experience-t3830197) is almost perfect. Maybe it can be updated to include the relevant drivers.
Maybe it's a kernel thing also, so maybe it's something you should discuss with Derp Kern devs, for example?
https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996
I don't really know who deals with "missing driver" in current context, try get more information in the threads?
htchd2sucks said:
Yes, I informed the various recovery devs about that, I know it was fixed on latest versions.
I'm surprised it's not working for ROMS, I though the problem was fixed...
Have you tried telling that to the roms dev? I doubt anyone will read that here in this questions section...
The latest PE rom (https://forum.xda-developers.com/redmi-note-5-pro/development/rom-pixel-experience-t3830197) is almost perfect. Maybe it can be updated to include the relevant drivers.
Maybe it's a kernel thing also, so maybe it's something you should discuss with Derp Kern devs, for example?
https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996
I don't really know who deals with "missing driver" in current context, try get more information in the threads?
Click to expand...
Click to collapse
I informed the kernel Dev he said xiaomi has to update the sources that I think is less likely to happen
Same issue here. There's a RR build working for me though but I don't see fingerprint settings in security menu. I have goodix though. I tried a few pie ROMs and all of them just have a black screen.
NitinRanganath said:
Same issue here. There's a RR build working for me though but I don't see fingerprint settings in security menu. I have goodix though. I tried a few pie ROMs and all of them just have a black screen.
Click to expand...
Click to collapse
Can you give the link to the working rom
Anyone has a working aosp rom for hauxing display
rahulrulz said:
I have redmi note 5 pro indian version with huaxing display panel so if i flash any custom rom other than miui based rom it just shows a black screen ie no display so can anyone fix this?
I don't think Xiaomi will provide updated source codes
Click to expand...
Click to collapse
NitinRanganath said:
Same issue here. There's a RR build working for me though but I don't see fingerprint settings in security menu. I have goodix though. I tried a few pie ROMs and all of them just have a black screen.
Click to expand...
Click to collapse
The calibration file for this panel is missing on custom ROMs, here's a flashable zip with this file from MIUI which should fix this, mount system and vendor on recovery before flashing (mandatory)
rocker00 said:
The calibration file for this panel is missing on custom ROMs, here's a flashable zip with this file from MIUI which should fix this, mount system and vendor on recovery before flashing (mandatory)
Click to expand...
Click to collapse
Wow, can you confirm if this works on all ROMs ? Also, I'm using a custom modified kernel currently in order to use custom ROMs but it breaks WiFi. Does this break WiFi too ?
EDIT: I dirty flashed Bootleggers ROM which I was using with the modified kernel and flashed only the ROM and the fix zip. The black screen issue still persists. I had mounted both system and vendor before flashing the ZIP. Maybe I'm doing something wrong. I request the OP to confirm if the ZIP fixed his issue.
NitinRanganath said:
Wow, can you confirm if this works on all ROMs ? Also, I'm using a custom modified kernel currently in order to use custom ROMs but it breaks WiFi. Does this break WiFi too ?
EDIT: I dirty flashed Bootleggers ROM which I was using with the modified kernel and flashed only the ROM and the fix zip. The black screen issue still persists. I had mounted both system and vendor before flashing the ZIP. Maybe I'm doing something wrong. I request the OP to confirm if the ZIP fixed his issue.
Click to expand...
Click to collapse
I don't have this panel and also using MIUI, i just found this file while i was looking for something else, i thought it might do the trick, maybe Xiaomi should update the source code to support this panel for custom ROMs, but clearly this file is the calibration for this panel!
rahulrulz said:
anyone has a working aosp rom for hauxing display
Click to expand...
Click to collapse
deleted reply
NitinRanganath said:
Wow, can you confirm if this works on all ROMs ? Also, I'm using a custom modified kernel currently in order to use custom ROMs but it breaks WiFi. Does this break WiFi too ?
EDIT: I dirty flashed Bootleggers ROM which I was using with the modified kernel and flashed only the ROM and the fix zip. The black screen issue still persists. I had mounted both system and vendor before flashing the ZIP. Maybe I'm doing something wrong. I request the OP to confirm if the ZIP fixed his issue.
Click to expand...
Click to collapse
Can u send me the kernel
NitinRanganath said:
Same issue here. There's a RR build working for me though but I don't see fingerprint settings in security menu. I have goodix though. I tried a few pie ROMs and all of them just have a black screen.
Click to expand...
Click to collapse
About the FP Sensor I'm have a goodix too, but the dev of Pixel Experience is working on fix for it, maybe if you contact him, you problem with the Display can be solved.
MarcoD14 said:
About the FP Sensor I'm have a goodix too, but the dev of Pixel Experience is working on fix for it, maybe if you contact him, you problem with the Display can be solved.
Click to expand...
Click to collapse
The fingerprint issue was only with the old RR May build. After flashing the latest ROMs, the fingerprint option is available and works fine. Thanks though. As far as the display is concerned, custom ROMs don't boot without a specific kernel and that kernel breaks WiFi. I appreciate the efforts though. Also, on some ROMs, the maximum is quite dim but its fine on NOS and McAOSP.
---------- Post added at 07:03 PM ---------- Previous post was at 07:03 PM ----------
rahulrulz said:
Can u send me the kernel
Click to expand...
Click to collapse
Check PM.
rocker00 said:
The calibration file for this panel is missing on custom ROMs, here's a flashable zip with this file from MIUI which should fix this, mount system and vendor on recovery before flashing (mandatory)
Click to expand...
Click to collapse
It doesn't work still black screen
has anyone actually found a fix for this, or a non MIUI rom that works? I also have the black screen problem...
Thanks
https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-huaxing-displays-t3873266
Here is the fix