Related
Hi,
I upgraded my Samsung Galaxy R today to the official ICS version. The phone was on the stock ROM (Gingerbread) earlier.
I did the update using KIES and the update went without any errors. Post upgrade, my Samsung Galaxy R's screen isn't working normally when viewing things involving pure black background. For example, when I open the "Settings" and try scrolling through the list that is shown in the black background, the text leaves streaking effect (leading to multi color dots in the black areas). As a result, the text in the black background becomes scrambled. This problem also happens when the phone is powered on and the start up splash screen (samsung logo in pure black background) appears. The weird fact is that the screen looks absolutely normal when there is no "pure black" element involved in the display and all other colors looks okay.
Just to confirm, I installed the Gingerbread version again (using custom ROM) and the screen works perfectly okay even when scrolling through the various settings with pure black background. Splash screen at the start up doesn't leave any streaks/dots either.
Finally, I tried to install ICS once again in OTA mode and the display issue started happening again. Please find attached the image that shows the problem.
Could you please let me know if I am missing something.
P.S: One more interesting point to note is that the problem happens only when the screen is kept in the portrait mode. The moment I turn the phone to the landscape mode, the screen becomes perfectly clean.
Thanks,
KB.
Hi,
I have attached a couple more screenshots that illustrates the problem.
The issue gets fixed once I put the phone in landscape mode and the issue doesn't happen when displaying colors other than black.
Thanks!
ece2k2 said:
Hi,
I have attached a couple more screenshots that illustrates the problem.
The issue gets fixed once I put the phone in landscape mode and the issue doesn't happen when displaying colors other than black.
Thanks!
Click to expand...
Click to collapse
Hmmm..Its may be lag of ICS. can you give me details like, is it was happening to you in GB as well..??
Or have you flashed any other ROM for the fix..??
kataria.vikesh said:
Hmmm..Its may be lag of ICS. can you give me details like, is it was happening to you in GB as well..??
Or have you flashed any other ROM for the fix..??
Click to expand...
Click to collapse
Hi Vikesh,
I am not facing any issues with GB. The display is absolutely perfect when I tried out GB. I tried the following sequence:
1. The phone was working perfectly in GB and I decided to upgrade to the official ICS
2. Upgraded my phone to ICS using Samsung Kies. Found the display issue the minute ICS started
3. Worried about the problem, I tried flashing the stock GB ROM. This fixed the display issue
4. Tried upgrading to ICS once again - without KIES this time (using Wifi - OTA). Upgrade went without any error, but the display problem started once again after the upgrade
Currently I am using the ICS and it works fine except for the aforementioned display problem. Even the display is pretty responsive and I don't feel any lag while using the phone. Display issue gets sorted the moment I turn the phone to the landscape mode and the problem happens only with black backgrounds in the display.
I am not sure what I am supposed to do and I am thinking of moving back to GB.
Please let me know if you need any other information.
Thanks,
KB.
ece2k2 said:
Hi Vikesh,
I am not facing any issues with GB. The display is absolutely perfect when I tried out GB. I tried the following sequence:
1. The phone was working perfectly in GB and I decided to upgrade to the official ICS
2. Upgraded my phone to ICS using Samsung Kies. Found the display issue the minute ICS started
3. Worried about the problem, I tried flashing the stock GB ROM. This fixed the display issue
4. Tried upgrading to ICS once again - without KIES this time (using Wifi - OTA). Upgrade went without any error, but the display problem started once again after the upgrade
Currently I am using the ICS and it works fine except for the aforementioned display problem. Even the display is pretty responsive and I don't feel any lag while using the phone. Display issue gets sorted the moment I turn the phone to the landscape mode and the problem happens only with black backgrounds in the display.
I am not sure what I am supposed to do and I am thinking of moving back to GB.
Please let me know if you need any other information.
Thanks,
KB.
Click to expand...
Click to collapse
buddy, This kinda problem I never faced. Might b few problem while updating your device, is occurring (which is not reporting as error). So, My suggestion is can you please use ODIN V3.07 & flash it using Offiline mode. i.e. Flashing ICS using ODIN.
Procedure is here -> Click here
First 3 question & answer will let you know everything.
If still problem persist, then do visit SSC or flash latest cm10.1 & based ROM over it.
The point of the topic:
Post your issues found in STOCK / CM11 or post a solution.Simple as that,very productive.
I'll start with a list of bugs:
CM11 ISSUES:
-Video recording lags in reduced luminosity.
-The phone heats too much when playing/watch videos for long time and so on.
-Volume during call is too low.
-Ocasionally freezes & crashes.
-Some graphical issues when the phone freezes.
-Wifi MAC Address is always 00:0a:f5:89:89:ff.
If there are 2 Xperia L using CM11 / Custom Kernel connected to the same wifi, both connections will be dropped.
STOCK ISSUES:
-Video blinks in low light(from what I've read it focuses wrong on the light source and starts blinking).
-The proximity sensor remains on after a missed call.
-Multi touch doesn't work as well as on CM11.
-Some weird freezes during call ( the screen remains off / freezes and you can't end the call / sometimes even answer )
-Camera doesn't have as much detail as in CM11 ( if you zoom in,the image doesn't clarify).
-Wifi MAC Address is always 00:0a:f5:89:89:ff.
If there are 2 Xperia L using CM11 / Custom Kernel connected to the same wifi, both connections will be dropped.
CM11 FIXES:
-Lag in video recording can be reduced by lowering the exposure.In medium to low light " - 1 " works pretty good and in very low to low light " - 2 " .However,when you use " - 2 " ,the recorded video will be very dark.Still haven't found a solution for this.
-About heating problem,you might want to try @Shivam Kuchhal 's kernel.He reported that his phone doesn't get heat up more than normal.
-About volume during call,it's been solved partially in newer releases by editing snd_soc_msm file.However,if the value is too high,the phne volume will also be too high and the speaker will produce distorsioned sound.However,I see they found a resonable value and both,the volume during call & speaker is about fine.
-For headset buttons not working,you must edit Generic.kl file.Here's a short tutorial to help you:
Go to: system/usr/keylayout/Generic.kl and change as below
key 226 HEADSETHOOK
key 256 BUTTON_1
change to
key 226 BUTTON_1
key 256 HEADSETHOOK
STOCK FIXES:
-For proximity sensor and weird freezes during a call use this tutorial .Haven't tested it personally,but people reported it works even on latest .17 fw.
-For Mac issue [ works for cm11 as well ]
1)Restore original MAC Address
Open /data/etc/wlan_macaddr0
Copy it's content. Ex: 01:12:13:14:15:16
Open /etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini
Find this line
Code:
Intf0MacAddress=000AF58989FF
Replace 000AF58989FF with the content of wlan_macaddr0, but write back to front. Ex: from 01:12:13:14:15:16, write to 161514131201. So it will look like this
Code:
Intf0MacAddress=161514131201
Save & Exit, Reboot the phone
That's all for now,continue to post bugs&fixes and most important:
HELP EACHOTHER
Marius Cristian said:
The point of the topic:
Post your issues found in STOCK / CM11 or post a solution.Simple as that,very productive.
I'll start with a list of bugs:
Click to expand...
Click to collapse
Proximity fix not working!!!
More Kitkat Bugs List:-
1. Headset buttons
2. Camera experiencing crashes randomly, sometimes cause overexposure and being unstable at flash mode
3. Black graphical glitch/scanning effect first time after you turn your screen off then on again after first restart/turning on phone.
4. Call bugs(e.g. distortion etc.)
5. Lag when using the video camera
6. battery draining faster then on stock rom. (was improved on early nightly releases....now its back again)
7. GPS not working again (for some it does...others it doesnt....again...wasnt there on first nightlies)(Mostly Happens In CM11)
8. Camera quality is much,much worse then on stock rom
9 . Phone may left hanging and screen wont turn on for several seconds...
10. Some apps are unsupported on playstore...
CM11 bugs
CM11:
1. Switch to HDR mode and within 3 snaps camera app will FC.
2. Headset buttons.. I have to manually edit that Generic.kl after every nightly update.
3. As mentioned above, graphical glitch after updates.
Some of bugs that u mentioned @David pro has been fixed by users, but device maintainer didn't merged it for some reason in official builds. So, get started:
1. These buttons can be fixed, someone(I don't remember who, Sorry) has created a modified Generic.kl. You can find that file somewhere on this forum.
2. Camera quality is medium, but videos are very poor..
3. Still exist
4. @up
5. As I said, videos are bad
6. Caused by Google Play Services, 1st method is use xposed Framework and one of its add-ons, 2nd is just disable Services from Settings>Apps(i'm using second one, because I just don't like Xposed)
7.GPS is working fine, at least for me. No fix needed
8.Yep, on stock it is better.
9.It's caused by "Black graphical glitch/scanning effect first time after you turn your screen off then on again after first restart/turning on phone."
10.Well, some of them are only for one platform or type of devices,eg. Tegra 4 games.
No heating issues noticed so far(I use my kernel obviously) and yeah the camera and video quality isn't anything worth praising. Also the hwcomposer issue happens only one time after every boot, after that its all fine.
I normally use AOSPA.
Actually,I think the cm11 camera takes better photos than stock,but it can be buggy sometimes :silly:
About GPS,it's working fine for me too.
About video camera being laggy...I think it's because our phone lacks drivers update.It's hard to believe the video camera will ever be 100% fixed.
I'm sorry I'm kinda busy those days and I don't have time to administrate this thread.I'll edit the main post as soon as I can with solution you guys posted.But it's true,there are things which can't be fixed.Until I come back, HELP EACHOTHER
an another bug with stock rom is that "camera not available "or the camera takes a long time to recover after taking a shot
chrome browser restarts the phone or makes the phone to hang
vishalaestro said:
an another bug with stock rom is that "camera not available "or the camera takes a long time to recover after taking a shot
chrome browser restarts the phone or makes the phone to hang
Click to expand...
Click to collapse
Haven't experienced those kind of issues when I used stock.Try to do a factory reset or flash the ftf again.Maybe you added some mods or apps which affected the system.
Overall,we have to admit that CM11 is blazing fast and that's why I'm still using it.I'll update the OP now with your solutions.Thanks guys and keep helping eachother.
Marius Cristian said:
Haven't experienced those kind of issues when I used stock.Try to do a factory reset or flash the ftf again.Maybe you added some mods or apps which affected the system.
Overall,we have to admit that CM11 is blazing fast and that's why I'm still using it.I'll update the OP now with your solutions.Thanks guys and keep helping eachother.
Click to expand...
Click to collapse
another BUG with the stock ROM
1)walkman app flickers in the widget lockscreen
2)poor memory management need to restart the phone daily else the phone lags like a hell
3)camera app didn't respond ,it doesn't even the focus sometimes ,clearing the app data solves this problem temporarily and i think it was not present with the .12 update ,so if anybody could extract the camera app from the .12 update similar to the phone app freeze issue the problem might be solved.
3)walkman app or any other music player makes music to stutter when the same song is played more than one time provided if the songs are stored in memory card also i know that my sdcard doesn't have any problem because it worked fine with galaxy s3.my sd card is sandisk ultra class 10 32 gb
4)battery drain heavy when wifi is switched on compared to previous android 4.1.2
note:i have not rooted my phone or modded my firmware .all i run is the apps taken from the playstore.i have done a factory reset for more than 4 times.
CM11 / Stock (using custom kernel) bug:
Wifi MAC Address is always 00:0a:f5:89:89:ff.
If there are 2 Xperia L using CM11 / Custom Kernel connected to the same wifi, both connections will be dropped.
Solution:
Restore original MAC Address
Open /data/etc/wlan_macaddr0
Copy it's content. Ex: 01:12:13:14:15:16
Open /etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini
Find this line
Code:
Intf0MacAddress=000AF58989FF
Replace 000AF58989FF with the content of wlan_macaddr0, but write back to front. Ex: from 01:12:13:14:15:16, write to 161514131201. So it will look like this
Code:
Intf0MacAddress=161514131201
Save & Exit, Reboot the phone
solution for Play Services battery drain in CM11
CM11 issues
1. GPS Not Working
2. NFC not Working.
3. NFC icon not provided in Status bar when NFC is ON.
4. Frequent Crashes : Blue Screen on latest Nightlies 20140827.
5. Camera quality getting worse.
chinmay1234 said:
1. GPS Not Working
2. NFC not Working.
3. NFC icon not provided in Status bar when NFC is ON.
4. Frequent Crashes : Blue Screen on latest Nightlies 20140827.
5. Camera quality getting worse.
Click to expand...
Click to collapse
Nfc icon not in statusbar is on all cyanogenmod/aosp based rom
chinmay1234 said:
1. GPS Not Working
2. NFC not Working.
3. NFC icon not provided in Status bar when NFC is ON.
4. Frequent Crashes : Blue Screen on latest Nightlies 20140827.
5. Camera quality getting worse.
Click to expand...
Click to collapse
1. For many people works,for some don't.I don't understand how's possible...
2.Haven't tested it...for me it's a useless feature.
4.Well,crashes happens.However,they're not too frequent.
5.I really like the photos cm11 takes.About video...another story.Try to notice the details in the photos in comparison with stock.
I am going back to stock in order to see if I can obtain(with all the bug fixes from here) a more stable software than cm11.I'll report to you soon guys.Until then, help eachother
@underd0g
Nice fix for WiFi-Mac interference problem. :good:
Marius Cristian said:
1. For many people works,for some don't.I don't understand how's possible...
2.Haven't tested it...for me it's a useless feature.
4.Well,crashes happens.However,they're not too frequent.
5.I really like the photos cm11 takes.About video...another story.Try to notice the details in the photos in comparison with stock.
I am going back to stock in order to see if I can obtain(with all the bug fixes from here) a more stable software than cm11.I'll report to you soon guys.Until then, help eachother
Click to expand...
Click to collapse
guys please try to solve the issues with stock ROM because they are the stable ones and the bugs are easily repairable if the bugs are reached to right hands.so pls first concentrate on stock ROM
I've been playing around with 4.4 video recording..what i think is the lags occurs when we record in low lights related with the kernel..i'm testing with snapcam as its has auto flash when recording in low lights..First result is same as stock..but in snapcam it has touch to focus when recording..after touch,the recording will get a bit darker when it refocus and walla..no lags..
What i found is, the camera will automatically reduced the exposure to -1 for avoiding the lags even it is on default setting..
When moving the camera in low lights,the recording will lags again after few second..that is with continuous focus..set to normal or auto..no lags..so our stock cam using continuous focus for recording..
Back to the kernel thing..from what i see from the recording is same like this when i'm playing with cnt rom to to get wifi and overclock working.
Ok,so I went back to stock.I'm amazed by the battery life,it lasted 2 days and I used the phone a lot ( especially for calls ).
However,after using the fix for freezes during call and so on,I still have experienced this morning an issue.While I was talking to someone,someone else called and the phone was beeping but the screen was frozen.I had to press the power button to lock the device then unlock it to get the screen to show who's calling and to give me the possibility to answer the call.What do you think I should do?For now I'll wipe phone app data,but I'm also waiting if someone knows a good,another solution to post.
Anyone know a way to remove the automatic shutdown?
My phone shuts down if it reaches 25%
Hi,
Just installed latest ROM - cm-12.1-20150518-NIGHTLY-bacon.zip .
Everything works well, I was hopping to fix the touchscreen issues (the phone is less sensitive than CM11), but feels the same as CM12S.
Anyway, if I am adding a new profile, and set it up based on my needs (for example to disable the look screen when I am home), after rebooting the screen is black, notification bar is running, I can expand it, but that's all I can do.
I cannot start any app, desktop is black.
Anybody having the same issue?
Thanks
paulserban said:
Hi,
Everything works well, I was hopping to fix the touchscreen issues (the phone is less sensitive than CM11), but feels the same as CM12S.
Thanks
Click to expand...
Click to collapse
CM reverted the change due to high battery drain, use an earlier nightly such as 20150515 (or a custom kernel like Boeffla beta15, ak246). Once it is fixed, it'll be re-added to the CM Repo.
As for the profiles part, I have not encountered that issue, however I am not on the CM's nightlies, but on temasek's custom forged.
Hi guys,
I'm running OOS Stable Pie on my OnePlus 6. I know I'm also running Magisk and a custom kernel (blu spark) but I don't know why it would have to do with my issue. It also happenned to me with Radioactive kernel.
So basically, randomly, when I wake up the screen, I can tell the screen tones have changed and when I go to settings, I can see that "srgb" is selected, however, if I select "default", then the colors don't change, and then if I select "srgb" again, then the colors go back to what I picked earlier, before turning on the screen.
It happenned to me a few times now, and I think it always happens after waking up the screen. I don't think it happens while the screen is on.
I didn't change any display settings in kernel apps such as Kernel Adiutor.
Am i the only one affected by this bug? Is this known? Is there a fix that should come?
Thanks for your help.
Up
same here
both OOS and HOS 9.0
xxal said:
same here
both OOS and HOS 9.0
Click to expand...
Click to collapse
Thanks for reporting the same bug. it's kind of reassuring that I'm not the only one affected. So we can hope for a fix for next update! It really makes my eyes bleeding back to default settings
Issue:
1.Some users (like me) must have faced issue of screen ghosting or retention in which if the device is used at max brightness, they see a ghosted image on sides of their phone. (Especially visible when switching from a light theme to dark, for eg, going in chrome incognito mode you will see it)
2.Usually it happens after flashing a custom ROM or kernel.
Fix:
Method 1:
1. In case if its a custom ROM, go to Settings > Display > LiveDisplay
2. Set the Color Profile to ‘Standard'.
3. Go to color calibration setting and set the following values:
Red at 90%
Green at 90%
Blue at 90%.
4. Keep the display screen of for some time (15 min) and boom! Issue solved.
[Note: Max brightness may feel a little less than before but its still better, you will get used to it]
Method 2:
1.In case you have a custom kernel, you can refer to other threads or manually set the values of Red, Green and Blue by yourself by using a ‘Kernel Manager App'.
Just keep it at minimum than its original values.
Conclusion:
This issue is NOT a hardware issue, its a software issue that can be fixed by implementation of any following methods.
Source:
I got through some other threads of Redmi having same issue. Just the difference is in the settings I used, you can customize it as per your own will BUT make sure that the ghosting does not appear by use of that setting. If successful, you may replay
What are you talking about??
This issue is not available in Pixel exp plus pie, is this a Stock rom issue??
but i didn't experience it for whatever hours i was on stock Miui.
It is not software issue, but the low hardware quality I presume
Ravindrasan said:
What are you talking about??
This issue is not available in Pixel exp plus pie, is this a Stock rom issue??
but i didn't experience it for whatever hours i was on stock Miui.
Click to expand...
Click to collapse
It is not the case that every user will face it. In case if it occurs, you may make use of these procedures.
Mostly, if you use max brightness and switch suddenly to dark grey, you can notice it (in custom ROMs / custom kernel ).
Sent from my POCO F1 using XDA Labs
OdinDxD said:
It is not software issue, but the low hardware quality I presume
Click to expand...
Click to collapse
No it is a software issue. I am not talking about the yellow spot issue (that is hardware issue)
This one is ghosting or temporary burn in caused due to change in the default color calibration.
I faced it before but after trying the above settings, even at max brightness, the ghosting did not appear again. So it actually works.
Ghosting does not remain forever in LCD. So its not harmful to hardware in any way. (Just buggy)
Sent from my POCO F1 using XDA Labs
Devlik said:
It is not the case that every user will face it. In case if it occurs, you use make use of these procedures.
Mostly, if you use max brightness and switch suddenly to dark grey, you can notice it (in custom ROMs / custom kernel )
Sent from my POCO F1 using XDA Labs
Click to expand...
Click to collapse
What exactly will i notice, i want to know what happens??
I agree. Screen Retention or Ghosting is mostly present on other devices (I'm not talking about the Pocophone alone but on every other devices) and can be fixed via software implementations or updates. Changing color profile and/or color settings can be a solution too.
Ravindrasan said:
What exactly will i notice, i want to know what happens??
Click to expand...
Click to collapse
Umm. You can google it. For example, look at this picture: (From search result, it just occurred in dark backgrounds in my case)
Sent from my POCO F1 using XDA Labs
Devlik said:
Umm. You can google it. For example, look at this picture: (From search result, it just occurred in dark backgrounds in my case)
Sent from my POCO F1 using XDA Labs
Click to expand...
Click to collapse
Can't it be issue related to bottom bar of chrome (u said when switching to incognito mode)?
Ravindrasan said:
Can't it be issue related to bottom bar of chrome (u said when switching to incognito mode)?
Click to expand...
Click to collapse
Well it appears on every side of the screen and not just bottom. Even when I boot to twrp after being on a bright screen for long time, the status bar, some text and navigation bar appears. ... It fades away tho, not permanent as in amoled. LoL
Sent from my POCO F1 using XDA Labs
Devlik said:
Issue:
1.Some users (like me) must have faced issue of screen ghosting or retention in which if the device is used at max brightness, they see a ghosted image on sides of their phone. (Especially visible when switching from a light theme to dark, for eg, going in chrome incognito mode you will see it)
2.Usually it happens after flashing a custom ROM or kernel.
Fix:
Method 1:
1. In case if its a custom ROM, go to Settings > Display > LiveDisplay
2. Set the Color Profile to ‘Standard'.
3. Go to color calibration setting and set the following values:
Red at 90%
Green at 90%
Blue at 90%.
4. Keep the display screen of for some time (15 min) and boom! Issue solved.
[Note: Max brightness may feel a little less than before but its still better, you will get used to it]
Method 2:
1.In case you have a custom kernel, you can refer to other threads or manually set the values of Red, Green and Blue by yourself by using a ‘Kernel Manager App'.
Just keep it at minimum than its original values.
Conclusion:
This issue is NOT a hardware issue, its a software issue that can be fixed by implementation of any following methods.
Source:
I got through some other threads of Redmi having same issue. Just the difference is in the settings I used, you can customize it as per your own will BUT make sure that the ghosting does not appear by use of that setting. If successful, you may replay
Click to expand...
Click to collapse
I am neither using a custom ROM nor have done anything to change device performance.
---------- Post added at 10:04 AM ---------- Previous post was at 09:54 AM ----------
Devlik said:
Issue:
1.Some users (like me) must have faced issue of screen ghosting or retention in which if the device is used at max brightness, they see a ghosted image on sides of their phone. (Especially visible when switching from a light theme to dark, for eg, going in chrome incognito mode you will see it)
2.Usually it happens after flashing a custom ROM or kernel.
Fix:
Method 1:
1. In case if its a custom ROM, go to Settings > Display > LiveDisplay
2. Set the Color Profile to ‘Standard'.
3. Go to color calibration setting and set the following values:
Red at 90%
Green at 90%
Blue at 90%.
4. Keep the display screen of for some time (15 min) and boom! Issue solved.
[Note: Max brightness may feel a little less than before but its still better, you will get used to it]
Method 2:
1.In case you have a custom kernel, you can refer to other threads or manually set the values of Red, Green and Blue by yourself by using a ‘Kernel Manager App'.
Just keep it at minimum than its original values.
Conclusion:
This issue is NOT a hardware issue, its a software issue that can be fixed by implementation of any following methods.
Source:
I got through some other threads of Redmi having same issue. Just the difference is in the settings I used, you can customize it as per your own will BUT make sure that the ghosting does not appear by use of that setting. If successful, you may replay
Click to expand...
Click to collapse
I am neither using a custom ROM nor have done anything in past which can have these after effects. I am facing these issue or may be noticeable after the rollout of the MIUI11 ROM. So i contacted other who owns pocof1 , but their device don't have these issues. Then i contacted the service center and they reinstalled the MIUI11 but the problem persists.
So then i thinking of a screen replacement since i m on a warranty period so should i do that to solve this issue?.
Also u gave the settings to resolve the issue for a stock/CustomUI but wht for the MIUI , pls give the setting for them too.
pls answer all my queries!
Kakipa said:
I am neither using a custom ROM nor have done anything to change device performance.
---------- Post added at 10:04 AM ---------- Previous post was at 09:54 AM ----------
I am neither using a custom ROM nor have done anything in past which can have these after effects. I am facing these issue or may be noticeable after the rollout of the MIUI11 ROM. So i contacted other who owns pocof1 , but their device don't have these issues. Then i contacted the service center and they reinstalled the MIUI11 but the problem persists.
So then i thinking of a screen replacement since i m on a warranty period so should i do that to solve this issue?.
Also u gave the settings to resolve the issue for a stock/CustomUI but wht for the MIUI , pls give the setting for them too.
pls answer all my queries!
Click to expand...
Click to collapse
This reply is pretty late, sorry for that.
1.You need to be rooted.
2.Download ColorChanger app from PlayStore.
3.Give root privileges.
4.Decrease the color in Custom1/Custom2/Custom3 by long tapping to these values:
R:240
G:240
B:240
S:1.00.
5.Save it (top left corner)
Con: You need to apply this every time you boot into your device.
You can upgrade to pro and enable “Activate on boot" from app setting to make this happen automatically.
I did it but it doesn't work, I'll consider change the hole panel
Can you take a look at the attached screenshot and confirm if these values are okay. Apart from RGB values, do I need to tweak anything else? Thanks in advance.
Oh I see, I got this problem, and realize I set livedisplay profile to dynamic. I thought my screen was wore out
Devlik said:
This reply is pretty late, sorry for that.
1.You need to be rooted.
2.Download ColorChanger app from PlayStore.
3.Give root privileges.
4.Decrease the color in Custom1/Custom2/Custom3 by long tapping to these values:
R:240
G:240
B:240
S:1.00.
5.Save it (top left corner)
Con: You need to apply this every time you boot into your device.
You can upgrade to pro and enable “Activate on boot" from app setting to make this happen automatically.
Click to expand...
Click to collapse
Is it a s/w or h/w issue and if i install custom ROM(pixel experience) will that help
Kakipa said:
Is it a s/w or h/w issue and if i install custom ROM(pixel experience) will that help
Click to expand...
Click to collapse
This is a hardware problem, i tried everything and failed so i got original lcd folder replaced from the service center and now no screen retention.
I am from India itself, do you know which service center to go to? Since poco split from mi, am i in trouble or i should head to the mi service center. And my is under a warranty of 6 months and i'm in the 3rd month now....is it free or you got to pay money for the service?
Thanks in Advance.
Deleted
I solve this problem on miui oficial without root, Just applying standard contrast on screen settings.