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
Related
Disclaimer:
* You flash this ROM at your own risk and responsibility.
* This ROM is provided without ANY WARRANTY WHATSOEVER, not even the warranty that it works.
* None of the developers of this ROM will be held accountable for any damages, complaints or anything.
This rom is pre pre pre pre alpha, almost nothing is working! Just for everybody who want see Oreo look. I'm out of free time but I will update each time when I get some free time. Whats working, whats not working...etc? You tell me! You fix something, you tell me! You found something, you tell me! Adb somehow is not working, you need to change ro.build.type from userdebug to eng and adb will start working. If you have idea about whats going on with adb, you tell me! Somehow managed to boot this rom, a lot of work and time I spent to get Oreo boot, got also credentials working but somehow camera is fail to work, probably we must use Snap camera instead of the Camera2? You can try snap camera and tell me. You can try other cameras too and tell me!
Enjoy!
Source code && how to build:
https://forum.xda-developers.com/showpost.php?p=74724831&postcount=1008
Download:
https://mega.nz/#!ZB4ilbrL!nI_YV54IMBmKpA1BE4L9VYcwm3nsuLXAGKOu35NJdyQ
Can you post some screenshoots? Whats working? Whats not working? Etc? I'm so lazy
risk
while it is very risky to put this firmware.
munjeni said:
Can you post some screenshoots I'm so lazy Whats working? Whats not working? Etc?
Click to expand...
Click to collapse
Not a risky, just some more things is not working! Bugs need to be identified and fixed one by one.
Mobile data and camera are not working.
Viktor245 said:
Mobile data and camera are not working.
Click to expand...
Click to collapse
Wifi ok?
munjeni said:
Wifi ok?
Click to expand...
Click to collapse
Do not have the opportunity to check it out.
munjeni said:
Wifi ok?
Click to expand...
Click to collapse
Wifi can't be opened
Waoo, I changed my phone, now I can use my z1c to test all lol
In the afternoon I'm going to install it!
i will wait for working mobile data and wifi build
omkarmahananda said:
i will wait for working mobile data and wifi build
Click to expand...
Click to collapse
Me too I'm opened source code ppublic, everybody if free to use it and try fix something.
munjeni said:
Me too I'm opened source code ppublic, everybody if free to use it and try fix something.
Click to expand...
Click to collapse
actually i have no idea how this thing work.
but can you help learning ?!
any thread or any website or anything?
thank you
Did you have think include magisk for this version?
Sorry for being late:
Audio doesn't work
Wifi doesn't work
I'm not able to test cell data
Camera doesn't work, neither footej
ADB doesn't work, no usb at all, the device isn't listed neither with adb devices and devices control panel in windows
Bluetooth yes
Vibrating yes
@hackintosh5 here
Heyho. I just tested building from @munjeni 's sources. Unfortunately TWRP throwed an error 6. I checked the updater script and found some strange lines. With them removed I was able to install and boot
I'm really up for doing some fixes, but for me it's learning by doing which can be a time intensive process.
BTW: USB transfer works by disabling ADB in developer options... I just copied the screenshots off the device.
115ek said:
Heyho. I just tested building from @munjeni 's sources. Unfortunately TWRP throwed an error 6. I checked the updater script and found some strange lines. With them removed I was able to install and boot
I'm really up for doing some fixes, but for me it's learning by doing which can be a time intensive process.
BTW: USB transfer works by disabling ADB in developer options... I just copied the screenshots off the device.
Click to expand...
Click to collapse
But ADB works to you? Can you see the phone if you do adb devices?
@munjeni can I try to replace the libs just like as porting a custom rom from the N builds? Or it is wasted time?
-totonio- said:
But ADB works to you? Can you see the phone if you do adb devices?
Click to expand...
Click to collapse
Yes, adb works. But only if you revert this commit https://github.com/munjeni/android_device_sony_amami/commit/e0cde4386d51ad2b45d7700f495a85fdb75dc8d2.
Adb from the 8.0 tree seems to be broken, but maybe it's a problem with our devicetree.
Nevertheles, as Munjeni already did, replacing the adbd with a prebuilt one (I used one from an Android 7 tree i had lying around) works quite fine.
@munjeni : Is adb built from 8.0 source working for you? Or is it a permission problem?
Hey. I've got some news. Wifi was working for me. I just installed a new build and was able to connect
I can't test data connection - the sim reader is broken in my test device.
I think we should move ahead to lineage 15.1 (android 8.1) because support for lineage 15.0 was already dropped.
Unfortunately there are several build issues - let's see what the time brings.
*Edit: adb is fixed now
Booted 15.1 some minutes ago.
Working
adb
MTP
brightness slider
not working
wifi
automatic brightness
audio
camera
LEDs
everything else...
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
Was just wondering if anybody had tried this unofficial linage from erfanoabdi i found on android file host https://androidfilehost.com/?w=files&flid=248828, would like to know if its working or not before i unlock my bootloader.
Cheers Shane.
riskyfuture said:
Was just wondering if anybody had tried this unofficial linage from erfanoabdi i found on android file host https://androidfilehost.com/?w=files&flid=248828, would like to know if its working or not before i unlock my bootloader.
Cheers Shane.
Click to expand...
Click to collapse
download.invisiblek.org/roms/lineage-15.1/nash/lineage-15.1-20180411-UNOFFICIAL-nash.zip
More up to date. Follow same install instructions from AOSiP thread in ROM section.
Screenie. Works fine
Uzephi said:
download.invisiblek.org/roms/lineage-15.1/nash/lineage-15.1-20180411-UNOFFICIAL-nash.zip
More up to date. Follow same install instructions from AOSiP thread in ROM section.
Click to expand...
Click to collapse
Cheers will check I out
Any conflicts with pantheon kernel?
badhalf said:
Any conflicts with pantheon kernel?
Click to expand...
Click to collapse
Motomods currently don't work with pantheon kernel. Everything else is the sane, minus the upstream patches and the features in pantheon which work fine except 230 MHz UC of the CPU. Will work on it this weekend.
between Lineage or AOSiP, which would you recommend @Uzephi?
cervantesjc said:
between Lineage or AOSiP, which would you recommend @Uzephi?
Click to expand...
Click to collapse
That's on preference. I like the custom options of the owl's best in AOSiP personally
Uzephi said:
download.invisiblek.org/roms/lineage-15.1/nash/lineage-15.1-20180411-UNOFFICIAL-nash.zip
More up to date. Follow same install instructions from AOSiP thread in ROM section.
Click to expand...
Click to collapse
Ok so something curious happened to me, tried installing the invisiblek version of lineageOS on Twrp and now I hardbricked my cellphone. So now I just wasted $400 on a cellphone im not ever gonna use
Going to wait for a bit before I go ahead with rooting my phone as I have a Vodafone branded xt1789-06 international version. Don't want to risk bricking or loosing my IMEI as I made this mistake with my I9505. So I'm going to wait for some more development on my device.
PoisonDash2 said:
Ok so something curious happened to me, tried installing the invisiblek version of lineageOS on Twrp and now I hardbricked my cellphone. So now I just wasted $400 on a cellphone im not ever gonna use
Click to expand...
Click to collapse
Worked for me, so must have been how it was flashed. Did you flash the firmware files first for Nash? If not, you didn't flash right. A flash all fixed it for me when I forgot that.
I've been using linage for a few days now, I like how is a little more stable than AOSIP, and Moto mods work better on lineage, but I have a question, where can I see if the rom gets updated?
@Uzephi do you know if Lineage has been updated at all?
cervantesjc said:
I've been using linage for a few days now, I like how is a little more stable than AOSIP, and Moto mods work better on lineage, but I have a question, where can I see if the rom gets updated?
Click to expand...
Click to collapse
Audio work when recording video? That's really the only thing I'm waiting for on any of these ROMs before I flash. I have a motomod battery, so it's nice to know that'll work, but having audio while recording is way more important to me.
davehasninjas said:
Audio work when recording video? That's really the only thing I'm waiting for on any of these ROMs before I flash. I have a motomod battery, so it's nice to know that'll work, but having audio while recording is way more important to me.
Click to expand...
Click to collapse
That's still an issue, I really don't record that many videos, so really not an issue for me.
cervantesjc said:
@Uzephi do you know if Lineage has been updated at all?
Click to expand...
Click to collapse
Besides the normal LoS updates? None that I have seen on gerrit. You can always follow the development of LoS and our device by following their gerrit. I haven't checked it since two weeklies ago.
https://review.lineageos.org/#/q/nash
Link for our device specific additions, conflicts, abandons, etc.
Thanks for the reply, I found out that lineage takes advantage of Android seamless update, and I've been getting updates, just minor ones, but hopefully it'll be a fully working rom pretty soon.
I was using the build 20180515 from invisiblek and it was working very well. Today I installed the build 20180517 and the colours became funky and messy unfortunately, it cannot be used. I had to go back to the previous build.
Just sharing this here for you to know.
Scratch that, after a clean install it's all fine. No dirty flash from 0515 to 0517 then.
Does anyone know if lte is working on sprint?
always6s said:
Does anyone know if lte is working on sprint?
Click to expand...
Click to collapse
Yes, been working for the past couple of weeks
Hello to all,i have Redmi Note 5 Pro(whyred).I broke my screen and ordered new from Aliexpress.I arrived yesterday and i succesfully replaced it.Everything is working perfect except TWRP.I had installed RedWolf recovery and Masik 2.2 and i wanted to update it to 2.4.But when i restarted phone into recovery mode,screen was black(blank) and computer recognized it as mtp.My screen is huaxing nt36672 fhd video mode dsi panel.Is there any TWPR that supports this panel?
Me too!
Me too!
Me too!
---------- Post added at 04:53 AM ---------- Previous post was at 04:51 AM ----------
filipo96 said:
Hello to all,i have Redmi Note 5 Pro(whyred).I broke my screen and ordered new from Aliexpress.I arrived yesterday and i succesfully replaced it.Everything is working perfect except TWRP.I had installed RedWolf recovery and Masik 2.2 and i wanted to update it to 2.4.But when i restarted phone into recovery mode,screen was black(blank) and computer recognized it as mtp.My screen is huaxing nt36672 fhd video mode dsi panel.Is there any TWPR that supports this panel?
Click to expand...
Click to collapse
Me too
resolved
filipo96 said:
Hello to all,i have Redmi Note 5 Pro(whyred).I broke my screen and ordered new from Aliexpress.I arrived yesterday and i succesfully replaced it.Everything is working perfect except TWRP.I had installed RedWolf recovery and Masik 2.2 and i wanted to update it to 2.4.But when i restarted phone into recovery mode,screen was black(blank) and computer recognized it as mtp.My screen is huaxing nt36672 fhd video mode dsi panel.Is there any TWPR that supports this panel?
Click to expand...
Click to collapse
Twrp for multirom is good!
I have flashed it,but every custom non-Miui gives me black screen(Masik works fine).I can hear lock-unlock sounds,but everything else is black.Do you know any aosp-los based rom that works on this screen?
It is twrp multirom. You can flash any aosp/Los based in second partition
Yes,but it shows miui logo when booting starts and from there only black screen.I think that some drivers are missing in aosp/los based kernel from miui.And when developers port that drivers we will be able to use non-stock roms.
Did someone found solution for this problem??
same problem here
filipo96 said:
Did someone found solution for this problem??
Click to expand...
Click to collapse
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1314
They need to update vendor blobs in recovery, so they can recognise the new screens.
htchd2sucks said:
They need to update vendor blobs in recovery, so they can recognise the new screens.
Click to expand...
Click to collapse
Or they can try OrangeFox recovery for whyred.
DarthJabba9 said:
Or they can try OrangeFox recovery for whyred.
Click to expand...
Click to collapse
Which is based on...TWRP, so in theory it should get the same issue (unless they updated some components inside twrp).
Edit: @DarthJabba9 Oh I just notice you're the one doing the OrangeFOX recovery page on XDA.
It looks great!
Can you comment then on why they should use OrangeFox recovery instead of TWRP? Have you updated some "blobs" (im referring to the bug report on github saying that's why the users have black screen)? Just a quick explanation (unless it's a try-and-see).
htchd2sucks said:
Which is based on...TWRP, so in theory it should get the same issue (unless they updated some components inside twrp).
Edit: @DarthJabba9 Oh I just notice you're the one doing the OrangeFOX recovery page on XDA.
It looks great!
Can you comment then on why they should use OrangeFox recovery instead of TWRP? Have you updated some "blobs" (im referring to the bug report on github saying that's why the users have black screen)? Just a quick explanation (unless it's a try-and-see).
Click to expand...
Click to collapse
OrangeFox has no black screen issue, and has never had it, period. I cannot comment on why official TWRP has this problem (kernel? device tree? build system?).
As far as features are concerned, a list of extra features can be seen here: https://forum.xda-developers.com/re...ment/twrp-orangefox-recovery-project-t3837547
relax guys
official twrp maintainer is already working on issue and it will be ready soon in 2-3 days (probably)
and orangefox devs just started working on issue
DarthJabba9 said:
OrangeFox has no black screen issue, and has never had it, period. I cannot comment on why official TWRP has this problem (kernel? device tree? build system?).
As far as features are concerned, a list of extra features can be seen here: https://forum.xda-developers.com/re...ment/twrp-orangefox-recovery-project-t3837547
Click to expand...
Click to collapse
Yes, it's possible several things:
1) OrangeFOX did not had this issue because no one reported it yet
2) OrangeFox users did not have the new or different screen manufacturer
3) OrangeFox uses updated "Blobs" or whatever technical which would justify that the issue is not impacting (maybe root cause is unrelated).
That's the thing, it seems to be a few users who got a new HW, some it's because the screen had been broken and replaced. Others, maybe it's new versions of the device?
Yes, it's true, it's very simple, the user could simply flash OrangeFox and try. We read it was based on TWRP so I thought it was not going to change the missing "blobs" (unless twrp was modified in orangefox).
Anyway, we could also try for the TWRP person to comment on the bug and update, it's just everything long usually around here (I don't even have the black screen issue, I just want to know what was root cause).
htchd2sucks said:
Yes, it's possible several things:
1) OrangeFOX did not had this issue because no one reported it yet
2) OrangeFox users did not have the new or different screen manufacturer...
Click to expand...
Click to collapse
Both of these. It is a kernel driver issue. All that one needs is an updated kernel. I am sure that Ankit will release a fix soon. I will certainly be releasing one for OrangeFox.
DarthJabba9 said:
Both of these. It is a kernel driver issue. All that one needs is an updated kernel. I am sure that Ankit will release a fix soon. I will certainly be releasing one for OrangeFox.
Click to expand...
Click to collapse
Thanks for the information!
Just for my understanding, the kernel can come with the ROM, right? Because I have flashed the latest "PE" rom and it comes with some version of DERP kernerl 3.4 xyz.
So how come that would be impacting at recovery level?
I mean, if you flash the rom the first time, it should then update kernel... So how come that user got a black screen at that stage?
Unless there's something else at recovery level...I just don't see how come it can work and then not work with the same kernel (I assume his device worked in MIUI before custom rom)...
htchd2sucks said:
I mean, if you flash the rom the first time, it should then update kernel... So how come that user got a black screen at that stage?
Click to expand...
Click to collapse
Hey
Do you also have phone with huaxing screen panel ?
I've spoke to orange fox recovery dev and he said that there is barely any rom works with this screen, coz karnel sources isn't released by xiaomi yet. Pixel experience rom dev confirmed that.
Ankit said that any rom with GSI may probably work, but i doubt that
How can i test or prove it without actually getting "soft bricks" or without risk test roms with arb4 phone ?
htchd2sucks said:
Thanks for the information!
Just for my understanding, the kernel can come with the ROM, right? Because I have flashed the latest "PE" rom and it comes with some version of DERP kernerl 3.4 xyz.
So how come that would be impacting at recovery level?
I mean, if you flash the rom the first time, it should then update kernel... So how come that user got a black screen at that stage?
Unless there's something else at recovery level...I just don't see how come it can work and then not work with the same kernel (I assume his device worked in MIUI before custom rom)...
Click to expand...
Click to collapse
I think this is getting OT. LEt's just say that recoveries have their own kernel, and ROMs have their own kernel. Both do not mix. It can be easier to get a kernel working with a recovery than with a ROM, because a recovery is a self-contained OS in its own right.
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