Hi!
Lately, certain area of my screen weren't responsive while on a custom rom. Strangely after updating it to OOS5, the issue is gone. Now, whenever i try roms other than the OOS5, the issue persist again. Anyone who experience the same issue as me or have the explanations to this weird, unorthodox oneplus 3 behavior?
Thanks in advance
Which other ROMs did you try? Did they include the firmware? Did you flash the correct one if they did not?
Firmware for Nougat does not work on all Oreo ROMs, depends on which blobs developer is using.
Sent from my ONEPLUS A3003 using Tapatalk
morphvale said:
Which other ROMs did you try? Did they include the firmware? Did you flash the correct one if they did not?
Firmware for Nougat does not work on all Oreo ROMs, depends on which blobs developer is using.
Click to expand...
Click to collapse
The first rom that i noticed the issue was from the PA 7.3.1 which the firmware is included. Apart from that is the AICP 13 where the developer ask to flash firmware before the OO5 but i tried both firmwares from the OOS4.5.1 to 5. Still the problem persists. To clarify things, the issue was there when I was still in Nougat. I thought it was the hardware issue. But ,right after the OOS5 came out and I flashed it the issue's gone. Strange right?
Hi I am sorry that you are experiencing this issue.
OOS4.5.1 is basically the cause of your issue. If you opt to flash any other N-based ROM after flashing OOS4.5.1, you are bound to experience screen not responding.
The only way to resolve this issue is if you use any 8.x based OOS; be it stable or open beta.
Bobbi lim said:
Hi I am sorry that you are experiencing this issue.
OOS4.5.1 is basically the cause of your issue. If you opt to flash any other N-based ROM after flashing OOS4.5.1, you are bound to experience screen not responding.
The only way to resolve this issue is if you use any 8.x based OOS; be it stable or open beta.
Click to expand...
Click to collapse
Hey! thanks for the info m8. Really appreciate it. Am I safe to flash any other N ROMs after flashing the OOS Oreo without gettin the issue?
Hi,
My screen just stops working after MI logo on all AOSP based custom ROMs. It simply powers off completely. I have tried Lineage OS 15.1, Arrow OS pie, Bootleggers ROM pie, and its the same on all of them.
I know the custom ROMs boot because i can hear the screen lock/unlock sound when I press the power button.
Tried wiping cache/dalvik; installing only rom, without Magisk. Don't know what else to try, but I really don't want to use MIUI because the main reason I bought this phone is because it has a rich dev community.
Also, the latest version of TWRP works, but RedWolf recovery has the same problem as AOSP ROMs: Screen just shuts off and after MI logo, but I know the recovery has started because it shows my devices' files on my PC when plugged into USB.
Stock MIUI, and MIUI AM custom ROM I have tried work just fine: The screen works perfectly normal.
Does anybody know of a fix, or has a similar issue? I have bought this phone to install an Open Source system and not be dependent on Google anymore, but now I'm stuck on MIUI which has both Google and Xiaomi bloat
Any help would be highly appreciated. My phone is Redmi Note 5 - Global edition (Whyred). I got it a month ago, and tried flashing as soon as my 360h unlock period expired.
Thanks in advance!
EDIT: After digging, I have found out that other people have the same issue with Huaxing screens. Has anyone found a fix for this so far, or has info if someone is working on it?
Same Issue
I've same issue Please someone guide us who know about this issue please please
Flash NoName Kernel after your Rom and you're good to go. Can't explain why tho..
edit: or Derp (actually using this one with RR Rom / Oreo)
UPDATE:
temblor55 has made a Magisk patch for this problem, which he posted on 18 september::
https://drive.google.com/file/d/1-3y1CR6nfVhFYf9VpE11FXOmDEQl5VMt/view
Pat57 has confirmed that it works for him.
________________________________________________________________________________________________________
I have a RN8 from 11-2020 board ID 3.29
Instead of the usual Omnivision OV13855 frontcam, there is a new version OV13B10 inside.
This camera sensor is also installed in later Redmi phones
This new version works OK with Miui 11.0.11 -A9, and higher
Custom A11 rom's will problably work also all with this frontcam (I tried CrDroid 7.4 -A11 with succes)
But I can't find a custom A10 rom that can connect to this frontcam.
Always get the message "can not connect to camera"
Because of speed, stability and more development, I prefer a A10 custom rom (Resurrection Remix)
I think it isn't the Xiaomi FW, so maybe it could be the kernel.
I have tried the updated 2021 -A10 roms and A10 kernels without succes.
So problably it is about missing libs inside rom.
Is there a way to find these libs in a A11 custom rom or Miui rom and add them inside A10 rom?
I don't want to deep dig in it, because A11 will be the future solution.
But development on A11 rom's is fast ongoing, so there are bugs which some are irritating.
So if someone could give a direction, I will be thankfull
Elinx said:
I have a RN8 from 11-2020 board ID 3.29
Instead of the usual Omnivision OV13855 frontcam, there is a new version OV13B10 inside.
This camera sensor is also installed in later Redmi phones
This new version works OK with Miui 11.0.11 -A9, and higher
Custom A11 rom's will problably work also all with this frontcam (I tried CrDroid 7.4 -A11 with succes)
But I can't find a custom A10 rom that can connect to this frontcam.
Always get the message "can not connect to camera"
Because of speed, stability and more development, I prefer a A10 custom rom (Resurrection Remix)
I think it isn't the Xiaomi FW, so maybe it could be the kernel.
I have tried the updated 2021 -A10 roms and A10 kernels without succes.
So problably it is about missing libs inside rom.
Is there a way to find these libs in a A11 custom rom or Miui rom and add them inside A10 rom?
I don't want to deep dig in it, because A11 will be the future solution.
But development on A11 rom's is fast ongoing, so there are bugs which some are irritating.
So if someone could give a direction, I will be thankfull
Click to expand...
Click to collapse
I had similar problem, but i don't think it's not from the libs, it's a "persist" thing
restore "persistbak" and flash it (or if you already have a recovery backup of persist just restore it)
loopypalm said:
.... i don't think it's not from the libs, it's a "persist" thing
restore "persistbak" and flash it .....
Click to expand...
Click to collapse
No, I think it has nothing to do with the persist partition.
Because I have flashed several different rom's and kernels and found that only Miui and A11 custom does recognize the selfiecam
If the persist partition was corrupted, this wasn't possible.
Because FW is from Miui, it could be the kernel or rom.
A lot of A10 custom roms are EOL, they are build with the original early hardware drivers/libs
From 11-2020 PCB-ID 3.29 the camsensor is changed and the RN8 was also almost EOL.
In september 2020 the first A11 build came out and at the end of 2020 more and more builds.
So I assume most developers don't even think about updating the kernel or libs on their "old" A10 versions.
Inside the screenshots of the app "Device info HW" you see the 19 supported cams of CrDroid 7.4 and only 17 on RR 8.6.7
Elinx said:
No, I think it has nothing to do with the persist partition.
Because I have flashed several different rom's and kernels and found that only Miui and A11 custom does recognize the selfiecam
If the persist partition was corrupted, this wasn't possible.
Because FW is from Miui, it could be the kernel or rom.
A lot of A10 custom roms are EOL, they are build with the original early hardware drivers/libs
From 11-2020 PCB-ID 3.29 the camsensor is changed and the RN8 was also almost EOL.
In september 2020 the first A11 build came out and at the end of 2020 more and more builds.
So I assume most developers don't even think about updating the kernel or libs on their "old" A10 versions.
Inside the screenshots of the app "Device info HW" you see the 19 supported cams of CrDroid 7.4 and only 17 on RR 8.6.7
Click to expand...
Click to collapse
yes, on paper the problem sounds like it has nothing to do with persist
but as stupid as it sound ,it just worked ! (restoring persist) + latest stable A10 fw
devs didn't update the port because it just worked, and i heard it's a hard thing to mess with ...
loopypalm said:
...... as stupid as it sound ,it just worked ! (restoring persist) + latest stable A10 fw
devs didn't update the port because it just worked, and i heard it's a hard thing to mess with ...
Click to expand...
Click to collapse
For who has worked this? Have you one or more links to it?
I had read already the guides for restoring, but because all sensors does work I'm a bit holding back.
I like to read first some experiences with this, before I touch the persist partition.
Elinx said:
For who has worked this? Have you one or more links to it?
I had read already the guides for restoring, but because all sensors does work I'm a bit holding back.
I like to read first some experiences with this, before I touch the persist partition.
Click to expand...
Click to collapse
link to what ?
i had similar problem on my 128 variant and asked help in RR TG group (group is deleted by rodrigo) rr official dev is always offline, so rr users moved to milestone by zhan (which is miles better)
"all sensor work fine except camera"
nobody have idea and no dev support, so i try lot of things
and flashing latest A10 fw and restore persistbak + clean flash of RRos + 16 kernel are the last things i did and it worked
if you have orangfox do a backup of persist ,so if anything goes wrong you can just restore it
loopypalm said:
link to what ?
i had similar problem on my 128 variant and asked help in RR TG group (group is deleted by rodrigo) rr official dev is always offline, so rr users moved to milestone by zhan (which is miles better)
"all sensor work fine except camera"
nobody have idea and no dev support, so i try lot of things
and flashing latest A10 fw and restore persistbak + clean flash of RRos + 16 kernel are the last things i did and it worked
if you have orangfox do a backup of persist ,so if anything goes wrong you can just restore it
Click to expand...
Click to collapse
Ok I will try after backup
Which RN8 batch have you? Which camera didn't work?
Elinx said:
Which RN8 batch have you? Which camera didn't work?
Click to expand...
Click to collapse
what do you mean by batch ? i have ginkgo 6/128
the error was "can't connect to camera" (i guess,both front and back since i can't do anything while that error is apearing)
loopypalm said:
... batch ? i have ginkgo 6/128
the error was "can't connect to camera" (i guess,both front and back since i can't do anything while that error is apearing)
Click to expand...
Click to collapse
The batch date 11-2020 is the phone with problems.
First the problem with FW 12.01. This is the only phone that can't be flashed with that version. If you did with twrp, you had a brick.
Second the HW change of the selficam. I have seen I'm not the only one with Andoid Q "not connecting" to this specific cam.
On LOS 17 topic a saw there is a formel bug report published about this issue
I can use all other cams without problems. The error is only with selfiecam and A10. Not with Miui and not with A11.
That is why I think of a missing driver.
I read something about adding missing drivers, but think it isn't easy.
Also I understand that the vendor image contains the hardware drivers.
So trying kernels only hasn't influence on HW changes
I can imagine that A11 custom uses also later vendor images, that's why these roms work with selficam.
Next question would be.
Are vendor images for Ginkgo intechangable?
Elinx said:
That is why I think of a missing driver.
Click to expand...
Click to collapse
have you tried A10 latest stable FW ? (it has updated drivers in it)
Elinx said:
Are vendor images for Ginkgo intechangable?
Click to expand...
Click to collapse
as far as i tested(A10), they are all almost the same, except for some roms have some carrier overlays and BT in it and other have them in system
also audio mods and enhancement, some roms have it and other don't
loopypalm said:
have you tried A10 latest stable FW ?....
...
as far as i tested(A10), they are all almost the same, except for some roms ...
Click to expand...
Click to collapse
Yes I have the latest stable FW. First I thought that these contains the HW drivers.
But reading, I learned that with latest Android versions all drivers are inside vendor image.
That is why updating FW and kernel doesn't make any difference for RR.
Because of all brick/EDL troubles I'm being carefull what I flash.
I have made for now a twrp backup of vendor and efs partition.
The persist parttion must be backup with adb or terminal
My phone is still an empty phone so I can format data and so on.
I saw that Miui vendor files are downloadable.
The latest Global is 11.0.11
Elinx said:
The persist parttion must be backup with adb or terminal
Click to expand...
Click to collapse
use also recovery (you never know) ...
Elinx said:
I saw that Miui vendor files are downloadable.
Click to expand...
Click to collapse
before changing system try RR with A11 vendor just to make sure
(i did that between 2 A10 roms and it worked,but A11 = not tested)
you can wipe everything and flash rr since your data is not important
loopypalm said:
.....
before changing system try RR with A11 vendor just to make sure
(i did that between 2 A10 roms and it worked,but A11 = not tested)
...
Click to expand...
Click to collapse
Dit you flash the complete vendor.img from another A10 rom?
or replaced the 3 vendor files inside the rom's?
Elinx said:
Dit you flash the complete vendor.img from another A10 rom?
or replaced the 3 vendor files inside the rom's?
Click to expand...
Click to collapse
i flashed a rom (Don't remember the name) and i did a mess in vendor ,so instead of reflashing, i restored a recovery backup of vendor of an older rom (AEX) that was on my SD
of course error like app x stopped working popped off,so this is not a fix
this is just a crazy suggestion to test the compatibility of the drivers
also test this cam :
ɬɧɛ Ɩųŋąɬıƈ in Dtuxed Roms Public Group
t.me
it has updated libs
maybe it will work
loopypalm said:
...., i restored a recovery backup of vendor of an older rom (AEX) that was on my SD
.....
maybe it will work
Click to expand...
Click to collapse
Ok you flashed vendor.img with twrp
The download link is Miui camera.
There where no HW drivers inside
I already found also such a zip with libs, but without result
It is for improving camera results
Elinx said:
There where no HW drivers inside
Click to expand...
Click to collapse
i made a mistake in the zip
the cam that i wanted to give you is in the same group
i will see if i can find it
Try this bro
Thank you, I surely want to try this Magisk mod file, but the file isn't accessible without requist.
Maybe you have your reasons for that, but in that case it isn't possible to download.
I have tried to comment this with the video too, but you have disabled comments there.
temblor55 said:
Try this bro
Click to expand...
Click to collapse
temblor55 you forgot to make the file public
Sorry guy's made it public now
https://drive.google.com/file/d/1-3y1CR6nfVhFYf9VpE11FXOmDEQl5VMt/view
Hi guys.
I wanted to say something here. In this forum and elsewhere in the internet people are complaining about "Ok Google" being unavailable/greyed out.
People often recommend others to "flash NikGapps/MindTheGapps/FlameGapps" whatever else, which doesn't solve the issue and makes people waste their times.
I am not a dev, so I might be a bit mistaken, but I talked to some devs from StyxOS/LineageOS devs and they all told me it is because of something called "hotword blobs" that is needed by Android 11. Without those it doesn't work, regardless of which gapps you're using.
AFAIK, the it only works in LineageOS 18.1 for the Redmi 7 device. I tried it and it works with any Gapps (mindthegapps, NikGapps, FlameGapps and OpenGapps). Beware that the OpenGapps version is broken and a lot of stuff goes wrong with it, you shouldn't use it.
ROMs I tested where it doesn't work (only official ROMs)
- Nusantara 3.0 (Android 11)
- StyxOS
- PixysOS
- HavocOS 4.5/4.6
and a few other unnofficial ROMs
This doesn't mean there's a problem with the ROM. Except for HavocOS, which I just installed to check whether this was working, I used all the other ROM's for a few days or weeks and they're all stable.
ROM I tested where it works:
So far:
- LineageOS 18.1
- Any Android 10/MIUI ROM
If you choose LOS 18.1 be aware that SafetyNet is currently broken and MagiskHide Props won't fix it, and that flashing custom kernels will trigger all sorts of weird bugs (phone doesn't reboot/shutdown, simcard data switches itself, distorted audio, you name it).
Flashing Xiaomi.eu 12.5 causes bootloop, you need to flash disabled vbmeta for it to work. If I'm not mistaken OK Google is working in it too.
Thanks.
Thanks for your post, I have the same issue and didn't understand what was wrong.
At least now I know it isn't about Gapps.
It would be great if somebody knows how to add these blobs to ROMs not having them already.
Is there please someone who can help me?
I have an unlocked willow device.
But when I install any custom rom (AOSP like - Android 12 or 13) the display will not light on first power button press after going to deep sleep or display lock. It will take several button pressing, until the display will come alive/wake up.
Sometimes it seems, that the display is unlocked, but is at lowest brightness level. The hardware is okay. I changed the power button pcb already.
The latest MIUI firmware rom (from xiaomifirmwareupdater.com) runs without bug. Its a A11 image.
Is this a bug maybe in the vendor file? Is there any other solution than staying on stock rom MIUI A11?
Thx for your feedback in advance!
kerberos666 said:
Is there please someone who can help me?
I have an unlocked willow device.
But when I install any custom rom (AOSP like - Android 12 or 13) the display will not light on first power button press after going to deep sleep or display lock. It will take several button pressing, until the display will come alive/wake up.
Sometimes it seems, that the display is unlocked, but is at lowest brightness level. The hardware is okay. I changed the power button pcb already.
The latest MIUI firmware rom (from xiaomifirmwareupdater.com) runs without bug. Its a A11 image.
Is this a bug maybe in the vendor file? Is there any other solution than staying on stock rom MIUI A11?
Thx for your feedback in advance!
Click to expand...
Click to collapse
if it's not a hardware issue it's the firmware or you did a dirty flash ?
No dirty flash. Always clean install. I think that there could be a major bug in all custom images for Willow devices. I tested several custom rom. None worked correctly.
Is there noone else with a Willow and the same problem?
And is it the vendor Image part i should flash over custom rom's vendor part? Then the custom Image does not boot anymore...
Any help is appreciated. Thx!
This evening I mixed up dtbo, modem, efs partitions from MIUI official A11 rom with a current A13 custom rom. Now the display works as expected.
Maybe I messed something up myself some months ago. Now i have a backup of a working system. That is good!
Gonna try flashing some custom A13 rom(s) again and test If it will break the "display wake up" again.