Related
So, I'm very eager to upgrade to a 7.1.1 custom ROM from 6.0.1 (currently using Dirty Unicorns 6.0.1), but I seem to have an issue with any android 7.1.1 version of a custom ROM I install where the sensors for auto rotate and auto brightness stop working. I've tried complete wipes and resets and installed crDroid, resurrection remix dirty unicorns and lineage OS. All of them have the same result. When downloading any apps that can be used to test and calibrate sensors, they all will read for that the sensor is unavailable for all hardware in the phone except for Wifi and GPS. Is this a general issue with android 7.0.1 on nexus 5x or is this just me? I've yet to find any other forums or pages with anyone experiencing this.
Any suggestions at all on this? I don't want to be stuck using Android 6 forever.
Any advice that can be offered would be greatly appreciated!
Ryan
kvothe26 said:
So, I'm very eager to upgrade to a 7.1.1 custom ROM from 6.0.1 (currently using Dirty Unicorns 6.0.1), but I seem to have an issue with any android 7.1.1 version of a custom ROM I install where the sensors for auto rotate and auto brightness stop working. I've tried complete wipes and resets and installed crDroid, resurrection remix dirty unicorns and lineage OS. All of them have the same result. When downloading any apps that can be used to test and calibrate sensors, they all will read for that the sensor is unavailable for all hardware in the phone except for Wifi and GPS. Is this a general issue with android 7.0.1 on nexus 5x or is this just me? I've yet to find any other forums or pages with anyone experiencing this.
Any suggestions at all on this? I don't want to be stuck using Android 6 forever.
Any advice that can be offered would be greatly appreciated!
Ryan
Click to expand...
Click to collapse
Make sure you read the OP of the ROM you are installing.
Clean flash everything with correct vendor image.
kvothe26 said:
So, I'm very eager to upgrade to a 7.1.1 custom ROM from 6.0.1 (currently using Dirty Unicorns 6.0.1), but I seem to have an issue with any android 7.1.1 version of a custom ROM I install where the sensors for auto rotate and auto brightness stop working. I've tried complete wipes and resets and installed crDroid, resurrection remix dirty unicorns and lineage OS. All of them have the same result. When downloading any apps that can be used to test and calibrate sensors, they all will read for that the sensor is unavailable for all hardware in the phone except for Wifi and GPS. Is this a general issue with android 7.0.1 on nexus 5x or is this just me? I've yet to find any other forums or pages with anyone experiencing this.
Any suggestions at all on this? I don't want to be stuck using Android 6 forever.
Any advice that can be offered would be greatly appreciated!
Ryan
Click to expand...
Click to collapse
I have a similar problem with every 7.1.1 custom ROM. Lift to check phone is not working (and yes, ambient display is enabled, vendor is correct). Every stock-based 7.1.2 ROM does work. Try flashing Stock+ 7.1.2 and see if your sensors work.
indian84 said:
Make sure you read the OP of the ROM you are installing.
Clean flash everything with correct vendor image.
Click to expand...
Click to collapse
I am always clean flashing. What do you mean by correct vendor image? It's always a bullhead version of the ROM. Maybe I misunderstand what you mean.
kvothe26 said:
I am always clean flashing. What do you mean by correct vendor image? It's always a bullhead version of the ROM. Maybe I misunderstand what you mean.
Click to expand...
Click to collapse
There is something called vendor image that you have to flash along with the ROM. It's generally linked to the build number.
Read the OP of the ROM you are using, it should have the correct vendor image you should use. If THE OP does not mention anything about the Vendor image, just search the thread or politely ask what vendor image to use.
Hopefully someone should link the download link for you. If not, you can easily Google it.
indian84 said:
There is something called vendor image that you have to flash along with the ROM. It's generally linked to the build number.
Read the OP of the ROM you are using, it should have the correct vendor image you should use. If THE OP does not mention anything about the Vendor image, just search the thread or politely ask what vendor image to use.
Hopefully someone should link the download link for you. If not, you can easily Google it.
Click to expand...
Click to collapse
Ohh. I was never aware of having to do something like this. I've always just downloaded the ROM and flashed it. Really appreciate this! Thanks! I'll have to give this a try.
kvothe26 said:
Ohh. I was never aware of having to do something like this. I've always just downloaded the ROM and flashed it. Really appreciate this! Thanks! I'll have to give this a try.
Click to expand...
Click to collapse
I have a strong feeling flashing correct vendor image will solve your problems.
indian84 said:
I have a strong feeling flashing correct vendor image will solve your problems.
Click to expand...
Click to collapse
You were right!
I downloaded the latest image from google and used the flash-all.bat script through fastboot, reflashed twrp, flashed crDroid 7.1.1, got a vendor image mismatch error on boot, then flashed the recommended vendor image version and now I'm booting without error and all sensors are working! I noticed Wifi detection and connection were working a but slow before, now everything is working perfectly. I was completely unaware that this needed to be done. It never came up as an issue for me when I was on Nexus 5.
I love the XDA community! Thanks a million for your help!
kvothe26 said:
You were right!
I downloaded the latest image from google and used the flash-all.bat script through fastboot, reflashed twrp, flashed crDroid 7.1.1, got a vendor image mismatch error on boot, then flashed the recommended vendor image version and now I'm booting without error and all sensors are working! I noticed Wifi detection and connection were working a but slow before, now everything is working perfectly. I was completely unaware that this needed to be done. It never came up as an issue for me when I was on Nexus 5.
I love the XDA community! Thanks a million for your help!
Click to expand...
Click to collapse
Separate Vendor partition was introduced with 5X and 6P. It was not needed on earlier devices.
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.
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
Hello everyone,
It has been a while since I toyed with my Zuk Z2 and I totally missed the Oreo train.
I would like to update my custom ROM with the newest Resurrection Remix OS but some things are still quite unclear.
I saw a lot of talk around updating the baseband version to enable offline charging. And some users also recommend to flash a stock ZUI Oreo ROM before flashing any custom Oreo.
My question is : can I update only my baseband using (fastboot or TWRP) and then directly flash RR 6.0 using the standard full wipe ?
Does that make sense or do I have to take the extra step with the stock ROM ? If so : which version should I install ? 1.9 and then let the OTA do their job ? Will it lock my bootloader again ?
Finally, what step should I take to make this upgrade as easy as possible ?
I am sorry if those questions have been asked lots of time before but I can't figure a clear answer about all of this,
Cheers,
Sinero said:
Hello everyone,
It has been a while since I toyed with my Zuk Z2 and I totally missed the Oreo train.
I would like to update my custom ROM with the newest Resurrection Remix OS but some things are still quite unclear.
I saw a lot of talk around updating the baseband version to enable offline charging. And some users also recommend to flash a stock ZUI Oreo ROM before flashing any custom Oreo.
My question is : can I update only my baseband using (fastboot or TWRP) and then directly flash RR 6.0 using the standard full wipe ?
Does that make sense or do I have to take the extra step with the stock ROM ? If so : which version should I install ? 1.9 and then let the OTA do their job ? Will it lock my bootloader again ?
Finally, what step should I take to make this upgrade as easy as possible ?
I am sorry if those questions have been asked lots of time before but I can't figure a clear answer about all of this,
Cheers,
Click to expand...
Click to collapse
Since you are currently on AEX 4.6, I believe that the offline charging is not working. Even I am on 4.6 and I have tried few Oreo ROMs. I think if you are on 1.76 or 1.70 baseband, you are good to go, flash RR.
Question is do you really want offline charging to work? Personally I'm not going to go through all this hassle for just making the offline charging work. I have been using AEX 4.6 without offline charging for a long time and I don't care if my future ROM has it or not.
Yeah, you can flash baseband using fastboot or TWRP
sixth.pr1m3 said:
Since you are currently on AEX 4.6, I believe that the offline charging is not working. Even I am on 4.6 and I have tried few Oreo ROMs. I think if you are on 1.76 or 1.70 baseband, you are good to go, flash RR.
Question is do you really want offline charging to work? Personally I'm not going to go through all this hassle for just making the offline charging work. I have been using AEX 4.6 without offline charging for a long time and I don't care if my future ROM has it or not.
Yeah, you can flash baseband using fastboot or TWRP
Click to expand...
Click to collapse
Thank you for clearing my doubts.
I flashed RR, went smoothly, everything seems to work as planned except for the camera : I do not have the HDR option, and I think a lot of options are missing. Do you have any ideas about that?
As you said offline charging is still not working, and I do not really care neither.
EDIT: Alright, I installed "Arnova's Pixel2Mod v6" and I now have a working camera. Do not mind my question. I also noticed that you posted the link (on another thread) where I found the Camera mod, so thanks again for your help!
Sinero said:
Thank you for clearing my doubts.
I flashed RR, went smoothly, everything seems to work as planned except for the camera : I do not have the HDR option, and I think a lot of options are missing. Do you have any ideas about that?
As you said offline charging is still not working, and I do not really care neither.
Click to expand...
Click to collapse
Using GCam? HDR option should be working, try the recommended one's from here: https://www.celsoazevedo.com/files/android/google-camera/
Slow motion is not working. If you have dark video issue, use OnePlus 5T Cam.
Thanks again for that link, seems like I edited my last post while you answered !
Here is a little feedback after ten days of usage :
My camera started acting up : usually when going through the camera's gallery the application will crash. I will try another Gcam.
I also noticed that my calls are not working. I can dial someone but when they pick up the call we cannot hear each-other. Does anyone have experienced this kind of situation ?
Everything else is working smoothly, better than under AEX 4.6, sadly with those two main problems I may have to try something else.
Sinero said:
Hello everyone,
It has been a while since I toyed with my Zuk Z2 and I totally missed the Oreo train.
I would like to update my custom ROM with the newest Resurrection Remix OS but some things are still quite unclear.
I saw a lot of talk around updating the baseband version to enable offline charging. And some users also recommend to flash a stock ZUI Oreo ROM before flashing any custom Oreo.
My question is : can I update only my baseband using (fastboot or TWRP) and then directly flash RR 6.0 using the standard full wipe ?
Does that make sense or do I have to take the extra step with the stock ROM ? If so : which version should I install ? 1.9 and then let the OTA do their job ? Will it lock my bootloader again ?
Finally, what step should I take to make this upgrade as easy as possible ?
I am sorry if those questions have been asked lots of time before but I can't figure a clear answer about all of this,
Cheers,
Click to expand...
Click to collapse
For offline charging flash at beast kernal
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