Develop Bugs

[Q] Wake up problems during the call

I need an opinion on this one. I've looked for this problem but it seems not to be clear what is causing it. I have Wildfire S (EU) Marvel. The device is S-On but I unlocked the boot loader and installed CWM. I've already tried several ROMs but it doesn't help to solve the issue. The problem appears during making the call - the screen goes black when you put the phone next to head and after that doesn't want to wake up. The only thing that wakes it up is putting it next to strong light source so I think the light sensor is the one to blame. However automatic backlight seems to be working fine. I really hope that it is not hardware problem. Please give any suggestion to try solving this problem. I would even go for the option to shut down somehow the light sensor because restarting phone after each call is kind of annoying. Thank you in advance for any help you can provide. Sorry for such a long introduction.

anubius said:
I need an opinion on this one. I've looked for this problem but it seems not to be clear what is causing it. I have Wildfire S (EU) Marvel. The device is S-On but I unlocked the boot loader and installed CWM. I've already tried several ROMs but it doesn't help to solve the issue. The problem appears during making the call - the screen goes black when you put the phone next to head and after that doesn't want to wake up. The only thing that wakes it up is putting it next to strong light source so I think the light sensor is the one to blame. However automatic backlight seems to be working fine. I really hope that it is not hardware problem. Please give any suggestion to try solving this problem. I would even go for the option to shut down somehow the light sensor because restarting phone after each call is kind of annoying. Thank you in advance for any help you can provide. Sorry for such a long introduction.
Click to expand...
Click to collapse
long introduction is far better than a short one ...
did you install rom propperly (factory reset/cache clean/dalvik clean)?
did you try using any other dialer app just to check ?
Like this, or this
I think i have read about such problem somewhere, if i find it i will post you the link to it...
also here are some apps to check your proximity sensor :
ProxyLightTester i couldn't find it on market. (not tested)
Proximity Sensor Finder Market link. (tested) and it will report 'all or nothing'

b02 said:
long introduction is far better than a short one ...
did you install rom propperly (factory reset/cache clean/dalvik clean)?
did you try using any other dialer app just to check ?
Like this, or this
I think i have read about such problem somewhere, if i find it i will post you the link to it...
also here are some apps to check your proximity sensor :
ProxyLightTester i couldn't find it on market. (not tested)
Proximity Sensor Finder Market link. (tested) and it will report 'all or nothing'
Click to expand...
Click to collapse
Hi, Thanks a lot for suggestions. So it seems to me that proximity and light sensors work. I tried several software including the one you suggested and the proximity and light sensor respond ok. I also tried different dialer but it doesn't help. I have no idea what can it be. I am thinking to put the device back to the factory state and maybe install official ROM but I am not sure if this will solve the problem. Thank you again for helping. And your device never had this problem?

Never had that problem.. Try reflashing w/o any app2sd gapps and stuff, just clean new rom and try it..
Sent from my HTC Wildfire using xda premium

anubius said:
I am thinking to put the device back to the factory state and maybe install official ROM but I am not sure if this will solve the problem.
Click to expand...
Click to collapse
Before you do that try this build.prop file and see if it helps...Just remove the ".txt" and set your permissions same as the old build.prop file you renamed.

Tera Tike said:
Before you do that try this build.prop file and see if it helps...Just remove the ".txt" and set your permissions same as the old build.prop file you renamed.
Click to expand...
Click to collapse
Thank you guys for all the suggestions I followed your advices but the phone simply refuses to wake up after the call. I am trying to go back to factory default since this is my last hope. Really confused what is causing it.

[FIX]Proximity Sensor (In-call) issue

Do you have problems with your Proximity sensor? Phone doesn't turn on while in call or randomly reboots within a call? Well, it's entirely a hardware issue found in most of the C8 (August 2012) production batch of Nexus. Not sure what your production year and month is? It's found on the sticker put on the phone (under the battery), the fourth and fifth numbers / letters are your phone's production date. A thread covering stuff about production date can be found here.
I tested this on two C8 Nexus(es). I don't guarantee if it will work for you or not but it looks like it fixed the issue for me. The only downside of this fix is that you have to use power button in order to lock your screen while in call and after the call you have to unlock it manually (This isn't a big issue in front of this issue, right?). Oh and by the way, it works on Android JellyBean version 4.2 and is untested on previous versions of Android.
So let's start:
1. So for the first step, you have to root your phone and flash Clockworkmod recovery into your Galaxy Nexus.
(WARNING: Flashing recovery and rooting leads to loss of all the data placed in your sdcard, so make sure your backup beforehand because it's better than crying later)
2. Download this zip and place it in your phone's sdcard: http://www.mediafire.com/?ir6z384vutepdmu
(To revert you can flash this (PLEASE NOTE THIS IS Version 2 and please use this version to revert successfully previous version had some flaws in it): http://www.mediafire.com/?d4n1fx3cj446k1l)
3. Power off the phone, after that press Volume up + Volume down + Power button to go into bootloader mode.
4. After entering into bootloader mode press Volume up two times and "Recovery Mode" should come up, press power button and the phone will restart into Recovery mode.
5. Select "install zip from sdcard" then press "choose zip from sdcard" then "0" then tap on the "ProximityFix.zip" (which you downloaded in step 2) and in last press "Yes".
6. After flashing of the zip is done tap on the "+++Go back+++" and then "reboot system now".
Voila you have a proximity sensor that no more interferes into calls or anything else!
What I did?
Basically I just Hexedit'ed "sensors.tuna.so" found inside "/system/lib/hw/" and changed "proximity" to "proximits".
What it does?
The stock "sensors.tuna.so" gets replaced by the modded "sensors.tuna.so" in order to completely disable the proximity.
CREDITS:
A very good friend of mine (zurchpet) from IRC for making edify script changes for the above supplied zip.
Alexander T. for figuring out production date.
Thank you

Nice idea, but your fix also removes other sensors as well, (all but sound) including screen rotation. Re-installed CM10, everything came back.
5pace said:
Do you have problems with your Proximity sensor? Phone doesn't turn on while in call or randomly reboots within a call? Well, it's entirely a hardware issue found in most of the C8 (August 2012) production batch of Nexus. Not sure what your production year and month is? It's found on the sticker put on the phone (under the battery), the fourth and fifth numbers / letters are your phone's production date. A thread covering stuff about production date can be found here.
I tested this on two C8 Nexus(es). I don't guarantee if it will work for you or not but it looks like it fixed the issue for me. The only downside of this fix is that you have to use power button in order to lock your screen while in call and after the call you have to unlock it manually (This isn't a big issue in front of this issue, right?). Oh and by the way, it works on Android JellyBean version 4.2 and is untested on previous versions of Android.
So let's start:
1. So for the first step, you have to root your phone and flash Clockworkmod recovery into your Galaxy Nexus.
(WARNING: Flashing recovery and rooting leads to loss of all the data placed in your sdcard, so make sure your backup beforehand because it's better than crying later)
2. Download this zip and place it in your phone's sdcard: http://www.mediafire.com/?ir6z384vutepdmu
(To revert you can flash this: http://www.mediafire.com/?muiza8fbwidq69d)
3. Power off the phone, after that press Volume up + Volume down + Power button to go into bootloader mode.
4. After entering into bootloader mode press Volume up two times and "Recovery Mode" should come up, press power button and the phone will restart into Recovery mode.
5. Select "install zip from sdcard" then press "choose zip from sdcard" then "0" then tap on the "ProximityFix.zip" (which you downloaded in step 2) and in last press "Yes".
6. After flashing of the zip is done tap on the "+++Go back+++" and then "reboot system now".
Voila you have a proximity sensor that no more interferes into calls or anything else!
What I did?
Basically I just Hexedit'ed "sensors.tuna.so" found inside "/system/lib/hw/" and changed "proximity" to "proximits".
What it does?
The stock "sensors.tuna.so" gets replaced by the modded "sensors.tuna.so" in order to completely disable the proximity.
CREDITS:
A very good friend of mine (zurchpet) from IRC for making edify script changes for the above supplied zip.
Alexander T. for figuring out production date.
Thank you
Click to expand...
Click to collapse

orph said:
Nice idea, but your fix also removes other sensors as well, (all but sound) including screen rotation. Re-installed CM10, everything came back.
Click to expand...
Click to collapse
I have a CA (Oct 2012) production batch of Nexus and have this issue too. It's just for statistics.
I also wish you would find some spare time to improve the realization of your idea by removing the proximity sensor only rather than other sensors as well.

yuryvrn said:
I have a CA (Oct 2012) production batch of Nexus and have this issue too. It's just for statistics.
I also wish you would find some spare time to improve the realization of your idea by removing the proximity sensor only rather than other sensors as well.
Click to expand...
Click to collapse
orph said:
Nice idea, but your fix also removes other sensors as well, (all but sound) including screen rotation. Re-installed CM10, everything came back.
Click to expand...
Click to collapse
It happens basically (to my knowledge) because of the custom ROMs you guys are on, sometimes contain files like "sensors.goldfish.so", which makes me wonder if it has any important role to play in disabling all of the sensors. You can tell me on which ROMs you are on and fetch "/system/lib/hw/sensors.tuna.so" and "/system/lib/hw/sensors.goldfish.so" and attach it here, I'll HexEdit those files and send it back over to you guys.

5pace said:
It happens basically (to my knowledge) because of the custom ROMs you guys are on, sometimes contain files like "sensors.goldfish.so", which makes me wonder if it has any important role to play in disabling all of the sensors. You both can tell me on which ROMs you are on and fetch "/system/lib/hw/sensors.tuna.so" and "/system/lib/hw/sensors.goldfish.so" and attach it here, I'll HexEdit those files and send it back over to you guys.
Click to expand...
Click to collapse
I have the stock JOP40D, yakju, the phone is rooted. My sensors.tuna.so is attached. I am new to android, did I understand you correctly all I have to do is to replace the original sensors.tuna.so by the modified file you will send back? Or I need to apply your patch as described in the 1st post (since my ROM is stock)?

THX 5pace,
i have the annoying bug of 8C :crying:
Paranoid Android 2.99 beta8
- sensors.tuna.so
- sensors.goldfish.so
The fix is ok, the proximity sensor is disabled.

I have this issue too. I am on CM 10.1 EuroSkank on stock kernel. Is there a zip file I can flash? Thanks for the fix!!!
Sent from my Galaxy Nexus using xda premium

PaXGeN said:
THX 5pace,
i have the annoying bug of 8C :crying:
Paranoid Android 2.99 beta8
- sensors.tuna.so
- sensors.goldfish.so
The fix is ok, the proximity sensor is disabled.
Click to expand...
Click to collapse
Is it compatible on other roms such as Xylon?
I got the same annoying problem
Sent from my Galaxy Nexus using xda premium

LKNim said:
Is it compatible on other roms such as Xylon?
I got the same annoying problem
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
You can try the Fix, if it doesn't work properly you can restore the backup with the Un-Fix :good:

Proximity Sensor Blues!
5pace said:
It happens basically (to my knowledge) because of the custom ROMs you guys are on, sometimes contain files like "sensors.goldfish.so", which makes me wonder if it has any important role to play in disabling all of the sensors. You both can tell me on which ROMs you are on and fetch "/system/lib/hw/sensors.tuna.so" and "/system/lib/hw/sensors.goldfish.so" and attach it here, I'll HexEdit those files and send it back over to you guys.
Click to expand...
Click to collapse
I'm new to this forum, so bear with me. I've been having the Proximity Sensor Blues lately and am in need of a cure. I've got a Verizon GNex (rooted and unlocked) running JB Sourcery 4.0 (soon to be 4.1 unless you tell me different) with their most recent "stock" kernel. I've attached the two files you requested, but have not tried the fix yet.
Considering the ROM I'm running and the attached files, is it OK for me to try the fix? Should I try a different kernel? Does it matter if I have TWRP instead of CWM? Please help!

Everything its ok
Sent from my Galaxy Nexus using xda premium

Sorry guys, I didn't have much time to reply this topic I had exams plus real life hassles to deal with, again I am sorry for the delay.
I've attached flashable zips files and appended your appropriate usernames with them, you can download and flash these files as per your usernames. If this still doesn't work (which means it still disables all the other sensors) you can try an app called Hardware Disabler, which you can get here: https://play.google.com/store/apps/d...dware_Disabler
After installing it and scrolling down, you will eventually find a tab called gp2a (gp2a is the name of the proximity sensor's manufacturer) and there would be a check mark under it, which would be followed by text; 4-0044 (model number of the sensor), when you press the check, it will disable proximity sensor irrespective of the ROM / Kernel you're on! The only downside is that when you reboot your phone the app would come up with a screen and you have to tap Yes for it to disable your proximity sensor.
On a side note I knew about the app (even before making this mod), but I wanted my proximity sensor to be disabled without depending upon an app so I eventually came up with disabling it through lib file which was far more efficient. And these files aren't supposed to disable all the other sensors, using other ROM libs on another ROM will stop the functioning of other sensors, it's just because every ROM is unique in it's own way so these files require to be modded according to their respective ROMs source files. And yeah, again I do not guarantee this mod would work because after applying it to my Nexus, it still rebooted but the reboots were less occurring as compared to when the proximity was enabled.
P.S. I re-purchased Galaxy Nexus, the old one was a C8 (White color), and luckily the new one was a C2 (Black color) and it can do wonders in overclocking and undervolting.

On my Nexus C8 not work this trick with disabling the proximity sensor
I use Xylon ROM, with his kernel...
What alse i can try to resolve the problem?

bacekoko said:
On my Nexus C8 not work this trick with disabling the proximity sensor
I use Xylon ROM, with his kernel...
What alse i can try to resolve the problem?
Click to expand...
Click to collapse
You may want to try this:
5pace said:
If this still doesn't work (which means it still disables all the other sensors) you can try an app called Hardware Disabler, which you can get here: https://play.google.com/store/apps/d...dware_Disabler
After installing it and scrolling down, you will eventually find a tab called gp2a (gp2a is the name of the proximity sensor's manufacturer) and there would be a check mark under it, which would be followed by text; 4-0044 (model number of the sensor), when you press the check, it will disable proximity sensor irrespective of the ROM / Kernel you're on! The only downside is that when you reboot your phone the app would come up with a screen and you have to tap Yes for it to disable your proximity sensor.
Click to expand...
Click to collapse
If it doesn't help in your case, then I am sorry as I am out of ideas.

So far, so good. Got fed up with the PS on my phone and tried this today. The sensor is disabled as far as I can tell. THANKS!

It worked for me, thanks.

All sensors are Off
Thakyou for this fix.
Not even a single call drop since i installed but none of the sensors are working.
I don't want any sensors but just the Camera so please if u can make it work I'll be very thankful.
Currently I'm on 4.1.1 JRO03C
I tried it on JDQ39 (4.2.2) it disabled only the proximity but calls were still dropping.
If possible then please make a fix to disable all sensors on 4.2.2 except camera and sound.
Thanx again.

I've a gnex with installed custom rom( minco v5 4.1.2 )
I've tried your mod for proximity sensor fix and it worked but it disabled light sensor too. I've tried app on playstore but it does the same.
I really need to disable proximity sensor to get my phone working good, but i won't to disable light sensor. Can you help me?
thank's,
Daniele.

My sensor PLS
Hi. I have the same screen problem as well. Would you prepare for me my sensor files for my device PLS.... I am on CM 10.1 M3 with leankernel 6.4

ryza666 said:
Hi. I have the same screen problem as well. Would you prepare for me my sensor files for my device PLS.... I am on CM 10.1 M3 with leankernel 6.4
Click to expand...
Click to collapse
I've use PaXGeN's sensors modified by you 5pace and there are working on my CM 10.1 M3 ( on every kernel ). I think PaXGeN pack sensors will work on every single custom rom based on jb 4.2.2. My proximity sensor is disabled but everything else is working smooth. I've checked efficiency by Android Sensor Box. Thanks for this thread.

[Q] Proximity sensors and black screen during calls

I'm experiencing black screen during calls issues, which is usually a sign telling the proximity sensor is gone bonkers.
I have that on EOS/CM11/D.U
I have not flashed COS 2.0, baseband/modem are still out-of-the-box ones (COS 1.20)
I kinda remember there were some package I could flash to try fixing this before sending it for RMA
Could some one please help me ?

theradec said:
I'm experiencing black screen during calls issues, which is usually a sign telling the proximity sensor is gone bonkers.
I have that on EOS/CM11/D.U
I have not flashed COS 2.0, baseband/modem are still out-of-the-box ones (COS 1.20)
I kinda remember there were some package I could flash to try fixing this before sending it for RMA
Could some one please help me ?
Click to expand...
Click to collapse
Use the search function:
Flash the Original Oppo recovery, then install COS 2.0, then go to COS 2.03 (beta), then back to one of the 1.2.* versions (I did it with 1.2.6). NOW install TWRP and use your favourite ROM. Your issues will then be fixed.
As I read it on the Oppo forums, something in the calibration of the sensors changed when 2.0 was introduced. I have no idea what, but the above steps fixed the problem for me.

Thank you very much
I understood those steps were for those who wanted to use custom rom from CoS 2.0
Not that it could fix other issue

theradec said:
Thank you very much
I understood those steps were for those who wanted to use custom rom from CoS 2.0
Not that it could fix other issue
Click to expand...
Click to collapse
Damn, I should have read more attentively. Maybe you could still just go to COS 2.0, then to 2.03 and back? Might be that on the way your problem might get fixed?

Bugs in 4.1.0 update

Hardware buttons not working after the 4.1.0 update .
Only Touch ID is working . Nothing else.

Taran3105 said:
Hardware buttons not working after the 4.1.0 update .
Only Touch ID is working . Nothing else.
Click to expand...
Click to collapse
Also the volume keys are not working.

no brothers both the capacitive buttons and volume rockers work flawlessly on 4.1.0

all is working for me :-/

Working fine for me.

Working fine for me. Seems like a temp issue or a wrong flash to me. You can try wiping system and flash full zip. If you are fully stock, i would advise to perform a factory reset.

Taran3105 said:
Hardware buttons not working after the 4.1.0 update .
Only Touch ID is working . Nothing else.
Click to expand...
Click to collapse
Sounds like a firmware issue. I suggest a full reflash.

I did a clean flash 4.0.3&4.1.0 OTA. Sometimes pulling down the notifications doesn't darken the background.

Clean flash ..stop making up bs posts

I cannot launch Google Assistant by voice with the screen off, whereas I could before the update

croques said:
I cannot launch Google Assistant by voice with the screen off, whereas I could before the update
Click to expand...
Click to collapse
As i have been saying repeatedly, the OTAs from OnePlus suck.
Clean flash the full ROM.

andrneumann said:
I did a clean flash 4.0.3&4.1.0 OTA. Sometimes pulling down the notifications doesn't darken the background.
Click to expand...
Click to collapse
Please PM me if you ever find a fix for this.. it forced me to use another ROM

Never call it Touch ID... This is not Apple.

works fine here clean flash

azaidi said:
Please PM me if you ever find a fix for this.. it forced me to use another ROM
Click to expand...
Click to collapse
Clean flashed again, now with OOS full zip 4.1.0, same thing. Pulling down notifications not always darken the rest of the screen. Still looking for a fix.

Factory reset solved the problem.

croques said:
I cannot launch Google Assistant by voice with the screen off, whereas I could before the update
Click to expand...
Click to collapse
I could never do that

andrneumann said:
Clean flashed again, now with OOS full zip 4.1.0, same thing. Pulling down notifications not always darken the rest of the screen. Still looking for a fix.
Click to expand...
Click to collapse
Did u find anything?
having the same issue
guess very few are having this issue (not many reported)

Anyone who's shortcut to for example a document on the home screen doesn't work anymore?
I already deleted the shortcut and made a new one, but still doesn't work

Ronak Chandak said:
Did u find anything?
having the same issue
guess very few are having this issue (not many reported)
Click to expand...
Click to collapse
I have the same issue...

Screen Bleeding issue

I am having a screen bleeding issue in my pixel experience rom 11/21
Magisk flashed
nothing else
the screen bleeding does exist in twrp as well
Can anyone tell me the solution ?
P.S.: I'm not allowed to send screenshots being a new member.

Hi,
It's hard to say what's a screen bleed according to your definition without visually see it. You could simply image upload and post the link, you'll get more results.
On the other hand, most standard screen bleeds are HW related so i'm not sure there's anything that can be done...
What FW do you have in your PE rom? (copy the baseband version from settings/ system/about phone/android version /baseband)

htchd2sucks said:
Hi,
It's hard to say what's a screen bleed according to your definition without visually see it. You could simply image upload and post the link, you'll get more results.
On the other hand, most standard screen bleeds are HW related so i'm not sure there's anything that can be done...
What FW do you have in your PE rom? (copy the baseband version from settings/ system/about phone/android version /baseband)
Click to expand...
Click to collapse
Okay ...
My problem on my device , left and right side of the screen is brighter than rest of the screen , it is SW related because it wasn't there on miui .... (I mean the area near the edges )
screenshot -> https://imgur.com/a/OcTYovC
Baseband version -> 660_GEN_PACK-1.164129.0.164270.1
I had miui 10.0.0.4 stable before this
do I need to flash firmware again? from here https://forum.xda-developers.com/redmi-note-5-pro/development/firmware-xiaomi-redmi-note-5-t3766138

DarkLegend_1943 said:
Okay ...
My problem on my device , left and right side of the screen is brighter than rest of the screen , it is SW related because it wasn't there on miui .... (I mean the area near the edges )
screenshot -> https://imgur.com/a/OcTYovC
Baseband version -> 660_GEN_PACK-1.164129.0.164270.1
I had miui 10.0.0.4 stable before this
do I need to flash firmware again? from here https://forum.xda-developers.com/redmi-note-5-pro/development/firmware-xiaomi-redmi-note-5-t3766138
Click to expand...
Click to collapse
Your baseband confirms you have firmware 10.0.0.4 stable, so you have the current latest stable.
I do have similar but I don't have any "screen bleed".
You should not need to flash anything again, it should be fine.
We don't see the screen bleed in the screen capture (which is probably normal), you could take a picture of the phone with another phone, or simply put a mirror a use the front camera.
To be fair, I doubt it's very visible, it might be "your perception", but do take a picture to show the extend.
(especially you have dark mode enabled, did you have that or similar in MIUI?)
In any case, I see your comment that it wasn't on MIUI, but it's rather strange and I never heard of that on PE. Maybe it's something like now your background is darker the the "screen bleed" is more visible or something.

htchd2sucks said:
Your baseband confirms you have firmware 10.0.0.4 stable, so you have the current latest stable.
I do have similar but I don't have any "screen bleed".
You should not need to flash anything again, it should be fine.
We don't see the screen bleed in the screen capture (which is probably normal), you could take a picture of the phone with another phone, or simply put a mirror a use the front camera.
To be fair, I doubt it's very visible, it might be "your perception", but do take a picture to show the extend.
(especially you have dark mode enabled, did you have that or similar in MIUI?)
In any case, I see your comment that it wasn't on MIUI, but it's rather strange and I never heard of that on PE. Maybe it's something like now your background is darker the the "screen bleed" is more visible or something.
Click to expand...
Click to collapse
Here is another picture https://imgur.com/a/Yhh5Kh3
observe closely ....

DarkLegend_1943 said:
Here is another picture https://imgur.com/a/Yhh5Kh3
observe closely ....
Click to expand...
Click to collapse
Hm, is that the "stain" on the bottom left?
Say starting 2cm from bottom left corner, up to 4cm higher?
Hm, you mention it's even in TWRP, which tends to indicate it's not even ROM related...At least not in system.
At this point I'm not sure what is the root cause and I'm not even sure if there's a problem...
You don' t have anything pressuring the screen like a bumper case or something?

htchd2sucks said:
Hm, is that the "stain" on the bottom left?
Say starting 2cm from bottom left corner, up to 4cm higher?
Hm, you mention it's even in TWRP, which tends to indicate it's not even ROM related...At least not in system.
At this point I'm not sure what is the root cause and I'm not even sure if there's a problem...
You don' t have anything pressuring the screen like a bumper case or something?
Click to expand...
Click to collapse
if it was because of the case I would have seen it way before , but will stop using it now !
the stain you see is the tempered glass having air bubble
I guess lcd density is messed up that's why I see something like this , because Ive watched a lot of videos regarding pixel experience , the icon size is comparitively small on my device.
I guess I'll have to go back to miui ...
Kindly tell me your
.TWRP version , Method of installation
(antirbpass dummy.img flash or fastboot boot recovery twrp.img and then flashing twrp )
.Rom that are using
.If I have to go back to miui
tell me the safest method so that I don't end up in bricking.

DarkLegend_1943 said:
if it was because of the case I would have seen it way before , but will stop using it now !
the stain you see is the tempered glass having air bubble
I guess lcd density is messed up that's why I see something like this , because Ive watched a lot of videos regarding pixel experience , the icon size is comparitively small on my device.
I guess I'll have to go back to miui ...
Kindly tell me your
.TWRP version , Method of installation
(antirbpass dummy.img flash or fastboot boot recovery twrp.img and then flashing twrp )
.Rom that are using
.If I have to go back to miui
tell me the safest method so that I don't end up in bricking.
Click to expand...
Click to collapse
https://in.c.mi.com/thread-714161-1-0.html
Seems easier than going through twrp. Although flashing latest miui rom should not trigger arbV4 protection so should not brick anything.

htchd2sucks said:
https://in.c.mi.com/thread-714161-1-0.html
Click to expand...
Click to collapse
I'm using anti 4 so I guess I'll have to flash latest miui 10.0.0.4 ... I'll update you if the problem persists maybe we could come up with the solution!
I had developed roms in gingerbread , I must say that was easiest Android version ??

DarkLegend_1943 said:
I'm using anti 4 so I guess I'll have to flash latest miui 10.0.0.4 ... I'll update you if the problem persists maybe we could come up with the solution!
I had developed roms in gingerbread , I must say that was easiest Android version
Click to expand...
Click to collapse
Yes, lot of things have changed...
By the way, there's a place where you can customize official miui rom, and for example, remove the ads and unwanted features.
The problem is someone posted that here on XDA but forgot the link.
If you want to look around...
I did flash back a MIUI rom from TWRP once, to have encryption again, I think if you want to come back "as MIUI was", the best is miui flash.

htchd2sucks said:
Yes, lot of things have changed...
By the way, there's a place where you can customize official miui rom, and for example, remove the ads and unwanted features.
The problem is someone posted that here on XDA but forgot the link.
If you want to look around...
I did flash back a MIUI rom from TWRP once, to have encryption again, I think if you want to come back "as MIUI was", the best is miui flash.
Click to expand...
Click to collapse
freezing msa will disable adds I guess!

DarkLegend_1943 said:
freezing msa will disable adds I guess!
Click to expand...
Click to collapse
https://mi-globe.com/rom-builder-features/?codename=whyred&img=redminote5pro.png&realname=RedMi+Note+5+Pro
I think that was the link, not entirely sure, I never found it again.
In that link it talks about installing ad blocker. I kind of remember that we could turn off some ads service in the MIUI rom custom thing...
Well that seems a good workaround anyway!
It even have clear instructions from TWRP:
https://mi-globe.com/globerom-rom-builder/

htchd2sucks said:
Yes, lot of things have changed...
By the way, there's a place where you can customize official miui rom, and for example, remove the ads and unwanted features.
The problem is someone posted that here on XDA but forgot the link.
If you want to look around...
I did flash back a MIUI rom from TWRP once, to have encryption again, I think if you want to come back "as MIUI was", the best is miui flash.
Click to expand...
Click to collapse
What's the step I need to flash lazy flasher ?
Don't need to format data ?
Mi flash doesn't read the updater script it does it on its own built in script I guess.....
I need to flash lazy flasher ?

DarkLegend_1943 said:
What's the step I need to flash lazy flasher ?
Don't need to format data ?
Mi flash doesn't read the updater script it does it on its own built in script I guess.....
I need to flash lazy flasher ?
Click to expand...
Click to collapse
No, lazy flasher is for example when you want to force disabling encryption checks.
Format data, I'm not sure, I think it's wiping it anyway during the flash. Nothing related to encryption (especially that MIUI rom will detect non encrypted /data fs and re.encrypt if needed).
Yes, maybe MIFlash only needs MI official roms (to be confirmed).
Maybe you need to wipe though, that i'm not entirely sure. I think a "clean flash" is expected (=wiping).

htchd2sucks said:
No, lazy flasher is for example when you want to force disabling encryption checks.
Format data, I'm not sure, I think it's wiping it anyway during the flash. Nothing related to encryption (especially that MIUI rom will detect non encrypted /data fs and re.encrypt if needed).
Yes, maybe MIFlash only needs MI official roms (to be confirmed).
Maybe you need to wipe though, that i'm not entirely sure. I think a "clean flash" is expected (=wiping).
Click to expand...
Click to collapse
confirmed
It's happening in pie only
I tried flashing linage os 15.1 (no success)
but the bleeding in twrp was gone.

DarkLegend_1943 said:
confirmed
It's happening in pie only
I tried flashing linage os 15.1 (no success)
but the bleeding in twrp was gone.
Click to expand...
Click to collapse
Then you might want to take proper screen illustration and describe your issue in a way that the dev can read it in the PE forum...
Maybe it's related to Derp Kernel, I don't know.
To be fair, others don't have the issue so maybe you have specific hw or pb?
There's an app called AIDA which can help to show you what's your screen manufacturer, it can be useful to post that too!

htchd2sucks said:
Then you might want to take proper screen illustration and describe your issue in a way that the dev can read it in the PE forum...
Maybe it's related to Derp Kernel, I don't know.
To be fair, others don't have the issue so maybe you have specific hw or pb?
There's an app called AIDA which can help to show you what's your screen manufacturer, it can be useful to post that too!
Click to expand...
Click to collapse
pannel is from official vendor

htchd2sucks said:
Then you might want to take proper screen illustration and describe your issue in a way that the dev can read it in the PE forum...
Maybe it's related to Derp Kernel, I don't know.
To be fair, others don't have the issue so maybe you have specific hw or pb?
There's an app called AIDA which can help to show you what's your screen manufacturer, it can be useful to post that too!
Click to expand...
Click to collapse
now facing screen burning ! I'm installing miui today I guess that's the most optimised rom.