Hi guys,
First sorry for my english, im french..xD
I have some "backlight flickering" problem on my MI4C.
There is quick varitions of backlight intensity at random times.
I had this problem with MIUI so i flashed cm-12.1-20151016, and more problems.
But i updated to CM12.1 cm-12.1-20151112-UNOFFICIAL-libra and the problem is back.
Do you have a solution ??
Thanks.
I noticed that suddenly the screen will get very bright, quite annoying.
ermacwins said:
I noticed that suddenly the screen will get very bright, quite annoying.
Click to expand...
Click to collapse
Ty for you answer, but it's not just the brightness who change but more the backlight doing like flashes.
I found a youtube video with similar problem.
But i cant post link.
You can find it on youtube typing :Sony Xperia Z1 backlight flickering.
semtex37 said:
Ty for you answer, but it's not just the brightness who change but more the backlight doing like flashes.
I found a youtube video with similar problem.
But i cant post link.
You can find it on youtube typing :Sony Xperia Z1 backlight flickering.
Click to expand...
Click to collapse
I watched the Video, but i have never seen this in my Mi4c.
https://youtu.be/uaGPgP_mmcQ
In miui the problem should be already fixed in 5.11.5, at least this is in the changelog.
Wow it is weird. I don't have that either (nor miui nor cm)
Yes i saw this for miui but i didnt tried, i changed for CM12.1 just before.
But i didn't saw the problem on the first CM build.
It's strange.
It happened to me twice. 5.11.5 the problem still continues. Now I use 5.11.12 not yet any flickering:fingers-crossed:
What if you change the level of adaptive display ? It is like you are on the edge between two different states and the phone doesn't know which one to choose.
bibihub said:
What if you change the level of adaptive display ? It is like you are on the edge between two different states and the phone doesn't know which one to choose.
Click to expand...
Click to collapse
I tried with low or high level of brightness and with adaptativ display on and off.
Same.
Hi everybody,
It happened again today so i tried differents things:
-Disabled Double Tap 2 Wake (1 of the new feature of the cm update): useless
-Turn ON the option to Disable HW Overlays (I saw on internet that can solve some screen flickering problems): wait and see
there is a risk ??
-I enabled performance mod on battery settings:
Is it good or not ?
Is it useless if im already using kernel adiutor set in on demand ??
Thanks.
I had a similiar problem with my Mi4 and managed to solve the problem by flashing this kernel after flashing CM: https://www.androidfilehost.com/?fid=24686681827314188
Little downside is; the kernel has a double-tap-to-wake-feature, which gives me some random unlocks in my pocket.
Related
Dear all,
I am suffering from the following bug.
bit.ly/1vF0MDS
Have tried both CM 11 and CM 11S. I think if I can change the sensor settings, may be situation would improve. Any ideas how to do the same ?
sahilkhurana said:
Dear all,
I am suffering from the following bug.
bit.ly/1vF0MDS
Have tried both CM 11 and CM 11S. I think if I can change the sensor settings, may be situation would improve. Any ideas how to do the same ?
Click to expand...
Click to collapse
I have face the same scenario almost every time. I have tried different things but no luck. Although, I have noticed that after finishing a call, if I pull the phone away from my ear vertically then the notification shade won't come down (success rate is about 60-70%). I added my vote for the bug resolution on jira.
Its kind of irritating and I guess playing with proximity sensor will help things. Have been searching on how to do the same without luck.
Sent from my iPad using Tapatalk
Hey Everyone.
I have had this issue for about 5 days now, I started out on CM 12.1 when I started to notice random black screens which required a reboot. Prior to this it has been fine for a few months.
Since then, I have tried a new ROM each day, CM 13, SLIM, RR and Mokee.
All seem to start out fine, restore apps from playstore / settings, phone performance is good.
The next day however is when the issues seem to arise, Sluggish behavior and random black screens which require reboot.
Has anyone else seen such behavior? Im a bit stuck, starting to think there is an issue with the phone.
Thoughts? Suggestions?
Thanks.
did u use ambient display?
try to disable it
faizauthar12 said:
did u use ambient display?
try to disable it
Click to expand...
Click to collapse
Everything under display is disabled except "Adaptive Brightness"
Fastboot flash and then try your desired rom
Over the couple of months, many Moto G4 Plus owners have been complaining about the screen burn issue.
Well there wasn't a fix for this through software except Blue Light Filter (which didn't work for me), and while trying for the fix, I feel I have found one.
Prerequisites:
1. Android Nougat (7.0) (I am running on the stock NPJ25.93-14 i.e the 1st December 2016 Security Patch)
2. System UI Tuner enabled.
No Root Needed.
My device is the Indian variant XT1643 i.e 2GB RAM variant.
For those who are on Android Marshmallow CM based Custom ROM, you can try using the live display and setting the value nearby 3000~3500K (Although I am not sure if this would work since I haven't tried it yet).
Its the Night Mode!
1. Go download the "Night Mode Enabler" app from the Play Store --> https://play.google.com/store/apps/details?id=org.michaelevans.nightmodeenabler&hl=en
2. Open it and click on "Enable Night Mode".
3. It will take you to System UI Tuner where you can toggle night mode on/off.
4. Go to the quick settings edit option, and you will see a new tile - "Night Mode".
Toggle on the night mode and see the effect after some time (it started to show effect as soon as I enabled it and fixed the issue within 20 minutes for me).
[Q]. What will happen if I toggle off night mode?
[A]. The Screen burn will occur once again.
You need to have the Night Mode to be always on in order to get rid of that Screen Burn issue.
I know that many might not like the color temperature of Night Mode, so if you have a CM based ROM, you can edit the temperature with "Live Display" option.
Well, try it out and lets see if it works or not!
Credits : Mike Evans for making this app.
First of all, thank you for sharing this.
But your "fix" is just a workaround and not a proper fix for our broken displays.
The only real fix is to replace the display.
Thadeus Griff said:
First of all, thank you for sharing this.
But your "fix" is just a workaround and not a proper fix for our broken displays.
The only real fix is to replace the display.
Click to expand...
Click to collapse
Umm, I guess you are right. I have changed the title now.
Even screen replacement is not a permanent solution. I have replaced display and within 3 weeks issue reoccurred
It fixed the issue
The night mode enabler has fixed the issue for now. But the screen is of some weird color(especially white background).
Anyways, Its good to see my phone screen without the screen burn issue after such a long time.
Thanks
RGB calibration is the best fix for screen burn in !
unfortunately if u r on stock rom ,Then you have to root ur device .
Malware injector said:
RGB calibration is the best fix for screen burn in !
unfortunately if u r on stock rom ,Then you have to root ur device .
Click to expand...
Click to collapse
Where i can download?
nikkali25 said:
Where i can download?
Click to expand...
Click to collapse
Kernel Adiutor can modify rgb values for example.
Hello everybody,
I've got a problem with a Oneplus One.
First a brief history of the device. I got it on ebay with a shattered display about 1 1/2 years ago and replaced the display. Since then my girlfriend managed to shatter the display 3 times more. So I'm quite used to replace the display on this device.
Since the last display replacement (the 4th) the device developed a partial Screen-of-Death problematic.
Sometimes the display just stays blank, while the backlight is clearly working (you can see the blueish light in dark environments). Also the device reacts to touch and button inputs, like e.g. double-tap-power to start camera. Or double-tap-screen to wake up (you can feel the vibration or display input sounds).
I "just" have to wait about 10-20 seconds, try again and the display turns on without any problems. In other cases I have to try this a couple of times to wake the screen.
A hard reset is not necessary, the device will wake up sooner or later. In this aspect it differs from all SoD descriptions I found online!
An other strange thing is, after the screen replacement the device forgot all wifi networks. The wpa_supplicant.conf was empty. Strangely enough all other apps were OK, I didn't noticed any irregular acting applications.
As the device was sill running on CM13 I decided to give it a fresh nougat installation and assumed the SoD symptomatic would vanish.
Now after flashing back and forth different factory images and custom-rom's the SoD is still there and renders the device almost unusable.
I tried the latest CM13 snapshot and sultans CM13, which I have been using on another OPO without problems for a long time.
I also tried to install different original factory images.
cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot_64GB.zip
and also another one I got long time ago from Oneplus to fix an annoying Wifi-Reboot-Problem. It contained additional image files like persist.img and reserve4.img.
I tried to turn on and off the setting for the proximity sensor that could interfere with the activation of the screen.
I tried different radio firmware's, as I could remember that there had been some problems in the past with incompatible firmwares, android versions and the proximity sensor.
I enabled and disabled all off-screen-gestures, although they are always working regardless if the display stays blank or not.
Unfortunately I've got no luck.
Literally every single android version I tried suffered from SoD. The only problem free thing is TWRP. Running the latest 3.1.1-0 I never got a blank/black screen on powering up the display.
So now I'm out of ideas and would be happy to hear any additional guesses to fix this problem.
I was also wondering if anybody knows more about the SoD. I couldn't find any information's regarding the causes of this problem. Is it hardware related or software?
thanks!
p.s. another strange thing I noticed now on the latest Slim7 rom (20170526). If I try to take a screenshot with power+vol-down, the screenshot animation happens. But a status bar notification from Android-System tells me, there is not enough free space to save the screenshot. But there is at least 40GB of free space.
I'm not sure if this is related to my problem or just to Slim7. And I'm also a little tired to reflash the device just to test this issue...
Maybe there is a problem with permissions or the flash memory?
p.p.s here a logcat. I couldn't find anything helpful.. https://pastebin.com/UWfwc1VX
Hello,
can anybody recommend an alternative kernel (for SLIM 7 rom), that allows me to increase the minimum CPU frequency.
I remember by doing that on a HP touchpad, I could avoid SoD.
Thanks!
pesche80 said:
Hello,
can anybody recommend an alternative kernel (for SLIM 7 rom), that allows me to increase the minimum CPU frequency.
I remember by doing that on a HP touchpad, I could avoid SoD.
Thanks!
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/orig-development/cm-lightning-kernel-v1-t3273308
Only this kernel is fully compatible with AOSP-based roms like Slim7.
---------- Post added at 08:37 AM ---------- Previous post was at 08:34 AM ----------
pesche80 said:
Hello everybody,
I've got a problem with a Oneplus One.
First a brief history of the device. I got it on ebay with a shattered display about 1 1/2 years ago and replaced the display. Since then my girlfriend managed to shatter the display 3 times more. So I'm quite used to replace the display on this device.
Since the last display replacement (the 4th) the device developed a partial Screen-of-Death problematic.
Sometimes the display just stays blank, while the backlight is clearly working (you can see the blueish light in dark environments). Also the device reacts to touch and button inputs, like e.g. double-tap-power to start camera. Or double-tap-screen to wake up (you can feel the vibration or display input sounds).
I "just" have to wait about 10-20 seconds, try again and the display turns on without any problems. In other cases I have to try this a couple of times to wake the screen.
A hard reset is not necessary, the device will wake up sooner or later. In this aspect it differs from all SoD descriptions I found online!
An other strange thing is, after the screen replacement the device forgot all wifi networks. The wpa_supplicant.conf was empty. Strangely enough all other apps were OK, I didn't noticed any irregular acting applications.
As the device was sill running on CM13 I decided to give it a fresh nougat installation and assumed the SoD symptomatic would vanish.
Now after flashing back and forth different factory images and custom-rom's the SoD is still there and renders the device almost unusable.
I tried the latest CM13 snapshot and sultans CM13, which I have been using on another OPO without problems for a long time.
I also tried to install different original factory images.
cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot_64GB.zip
and also another one I got long time ago from Oneplus to fix an annoying Wifi-Reboot-Problem. It contained additional image files like persist.img and reserve4.img.
I tried to turn on and off the setting for the proximity sensor that could interfere with the activation of the screen.
I tried different radio firmware's, as I could remember that there had been some problems in the past with incompatible firmwares, android versions and the proximity sensor.
I enabled and disabled all off-screen-gestures, although they are always working regardless if the display stays blank or not.
Unfortunately I've got no luck.
Literally every single android version I tried suffered from SoD. The only problem free thing is TWRP. Running the latest 3.1.1-0 I never got a blank/black screen on powering up the display.
So now I'm out of ideas and would be happy to hear any additional guesses to fix this problem.
I was also wondering if anybody knows more about the SoD. I couldn't find any information's regarding the causes of this problem. Is it hardware related or software?
thanks!
p.s. another strange thing I noticed now on the latest Slim7 rom (20170526). If I try to take a screenshot with power+vol-down, the screenshot animation happens. But a status bar notification from Android-System tells me, there is not enough free space to save the screenshot. But there is at least 40GB of free space.
I'm not sure if this is related to my problem or just to Slim7. And I'm also a little tired to reflash the device just to test this issue...
Maybe there is a problem with permissions or the flash memory?
p.p.s here a logcat. I couldn't find anything helpful.. https://pastebin.com/UWfwc1VX
Click to expand...
Click to collapse
I've had this issue before,it is due to faulty display only.I changed the display and it started working normal.
Ps-Better change your gf.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/orig-development/cm-lightning-kernel-v1-t3273308
Only this kernel is fully compatible with AOSP-based roms like Slim7.
---------- Post added at 08:37 AM ---------- Previous post was at 08:34 AM ----------
I've had this issue before,it is due to faulty display only.I changed the display and it started working normal.
Ps-Better change your gf.
Click to expand...
Click to collapse
Thanks!
I'm going to consider a new display... but not a new gf
pesche80 said:
Thanks!
I'm going to consider a new display... but not a new gf
Click to expand...
Click to collapse
Don't forget to invite me to your wedding.
Hello everyone,
anyone experienced the main screen dimming to a very low brightness level " in the sun " and no difference happens if i switched off adaptive brightness and got it to the max. I am not sure if that is related to the phone heating, but in general sometimes it dims very quick without even having the phone that heated.
OR maybe the phone gets heated very fast with simple use in the sun light.. any experiences related to that issue ??
Thank you great people.
Can't confirm your observation ... . But there is an option to dimm the screen in the settings of the energy or battery saving mode.
m.
It's a false positive from the light sensor. Some phones add a special setting to increase the brightness when it's overly bright to offset it, but I haven't come across one for this phone. It's a little impressive that so few phones actually address it after it's been a known issue so long.
I thought this issue was fixed already... what sw version are you on? share the device' model number as well please.
Additionally, submit error report to Samsung Members after reproducing the issue, you should be able to get guidance on how to get the fix...
meduza said:
Can't confirm your observation ... . But there is an option to dimm the screen in the settings of the energy or battery saving mode.
m.
Click to expand...
Click to collapse
no that is not the case, it happens even when not enabling the power saving mode.
twistedumbrella said:
It's a false positive from the light sensor. Some phones add a special setting to increase the brightness when it's overly bright to offset it, but I haven't come across one for this phone. It's a little impressive that so few phones actually address it after it's been a known issue so long.
Click to expand...
Click to collapse
so do you mean there is a solution or it is just a bug with the sensor ?
TheNewGuy92 said:
I thought this issue was fixed already... what sw version are you on? share the device' model number as well please.
Additionally, submit error report to Samsung Members after reproducing the issue, you should be able to get guidance on how to get the fix...
Click to expand...
Click to collapse
can you tell me how to submit this error report ? is it through the samsung members application ??
also the model number is SM-F711B
software version is android 11.. one ui 3.1.1 ..
k.a.h said:
so do you mean there is a solution or it is just a bug with the sensor ?
Click to expand...
Click to collapse
It's a bug that should have been fixed already.
twistedumbrella said:
It's a bug that should have been fixed already.
Click to expand...
Click to collapse
Sadly its not fixed at my side !
k.a.h said:
can you tell me how to submit this error report ? is it through the samsung members application ??
also the model number is SM-F711B
software version is android 11.. one ui 3.1.1 ..
Click to expand...
Click to collapse
If you don't have Samsung Members app installed then go to Galaxy or Play store and download it. In the app, click the Blue circle with+ icon. Then select Error Report.
Provide as much detail about the issue as you can and if possible include any screenshots or screen recording (make sure it's 1 issue per ticket).
Sorry for the late Reply... hope this helps and any future issues, submit a ticket as your first step so Samsung can start working on the issue while you look for work arounds or fixes
It might be a bug related to overheating. Had that happen to mine. The phone becomes too hot and dims the screen, turns off multi-window.