Develop Bugs

[UPDATED] Auto brightness flicker - Related to CPU load? Try different governer?

Hi all.
I'm reading a lot about 'screen flicker'. But it seems people are using this to describe a few different faults.
I've noticed that my one x backlight flickers when in auto brightness mode. But it only does it under artificial light. Under natural light it's totally fine.
If I turn off Auto brightness, it is completely fine also, regardless of what level I set the brightness to.
It's almost as if the software isn't filtering the auto brightness sensor output enough and trying to respond instantaneously to even the slightest light change, giving the impression of a flicker.
Who else has this issue specifically?
It looks to me like a software issue, but I only have 3 days left in my return for refund peiod and I'm not sure what the best option is.
Cheers.
EDIT: On to my 10th handset now with the same issue and just about ready to give up, but have noticed that the flicker seems to be worse when the CPU is coming on and off heavy load.
Can someone with Root and SETCPU installed please try different governers to see if they make any difference to this issue? I don't wan to root this phone to try it myself as I may end up returning it. Thanks!

Sentinel196 said:
Hi all.
I'm reading a lot about 'screen flicker'. But it seems people are using this to describe a few different faults.
I've noticed that my one x backlight flickers when in auto brightness mode. But it only does it under artificial light. Under natural light it's totally fine.
If I turn off Auto brightness, it is completely fine also, regardless of what level I set the brightness to.
It's almost as if the software isn't filtering the auto brightness sensor output enough and trying to respond instantaneously to even the slightest light change, giving the impression of a flicker.
Who else has this issue specifically?
It looks to me like a software issue, but I only have 3 days left in my return for refund peiod and I'm not sure what the best option is.
Cheers.
Click to expand...
Click to collapse
Oh well return it, and buy a new one thats probably the best option, i ordered mine yesterday, and ill do the same in 2 weeks if it have issues

Yeah I'm thinking that might be the best option. It's just that it seems to be a Software issue to me.
Anyone upgraded to 1.28 and seen this specific problem (not the screen jumping and flickering pixels) go away?

Sentinel196 said:
Yeah I'm thinking that might be the best option. It's just that it seems to be a Software issue to me.
Anyone upgraded to 1.28 and seen this specific problem (not the screen jumping and flickering pixels) go away?
Click to expand...
Click to collapse
I've upgraded to 1.28 and still have the flickering problem. I would love to be able to believe its software and its going to get fixed with an OTA, but at the moment everyone is simply uncertain as to what the future holds.

HTC advices anyone with a flickering screen to go to your carrier and ask for a replacement
Sent from my Desire HD using xda premium

On to my 10th handset with auto-brightness flicker now. At what point should i jsut give up? lol
It seems to be somehow related to CPU load also as I'm noticing the flicker is far worse when the cpu is changing power states.
Can someone with root try a different governer for the CPU and see if that changes the flicker at all?

BUMP. I'd be really great if someone rooted could test this theory!

..
I really cant help but ill tell my experience with my onex for the past two or three weeks.
I had the flickering screen twice,
1. random on the notification bar.
2. I was taking photos and got the CPU loaded because I was shooting too many pics. the bottom side of the screen was flickering.
anyway, I notice that the flickering only happend when the auto screen rotate is enabled.

Thanks for the reply, but I think you're talking about a different flicker. I'm talking about the back-light flicker when Auto Brightness is enabled. Not the LCD panel flicker.

Auto brightness issue? strange software glirch?

Does anyone else get this issue? I love having my brightness cranked to the fullest to see all the beautiful colors and sharpness of the screen. I noticed the other night while in my living room, the screen was dimmer than normal it made the whites have a yellow tint to it. Well case in point i checked my brightness settings and they were cranked up along with Auto Brightness turned off.
I did check in the display options that there is a color mode setup i always have mine on Cinema because it makes it the fullest of color and never changes.
I find this to be strange and im almost wondering that regardless of what i set my brightness too something in the software is manipulating the adaptive brightness. Hmm.. This is going to drive me bonkers. I wonder if its a Lollipop thing. Thanks!

I noticed when I was taking pictures on a sunny day and maybe a few times at the house. I have full brightness on until around dinner time. Hopefully fixed with a update.

I'm not sure where I read it, but this is a known occurrence on this phone, so there is nothing wrong with your phone..
I'll look for the story were I first saw this..

I have the same problem with the auto brigthness with my galaxy S6 edge . but when i uninstall the car app from samsung its gone
i hope it works for you too

jekuper said:
I have the same problem with the auto brigthness with my galaxy S6 edge . but when i uninstall the car app from samsung its gone
i hope it works for you too
Click to expand...
Click to collapse
has anyone tried this?

Trev420 said:
has anyone tried this?
Click to expand...
Click to collapse
yes doesn't work at all. I restored the phone and at that stage there is no car app installed yet, so it is not this causing the bug.
I suggest everyone that has the s6 edge to check it and eventually to return it back if you're still on time. Honestly I'm really disappointed, all this hype and then the flagship phone has this enormous bug! I chatted with my local assistance of Samsung and they were not aware of the issue. So I asked to the guy in chat if he could try to do the test that is on youtube (cover the light sensor and then use a flashlight comparing S6 and S6 edge) and he confirmed that even with brightness set to manual, the s6 edge is still reacting to the changes of light conditions. He didn't know if this is supposed to be a "feature" of the s6 edge but honestly I strongly doubt. It is a common bug of all the s6 edge, probably will be corrected, probably not, who knows. I returned mine in the meantime, if solved (confirmed by Samsung) I will consider to buy it again in the coming months.

Same problem
With auto brightness turned off it seems that the sensor still triggers the screen to dim or increase brightness.
I noticed it after i had the screen on and went from outdoor to indoor, it just automatically dimmed the screen. This is an issue with the software so hopefully with the new 5.1.1 update it will fix it.
heres a link to where i found out the issue but unfortunately since i am a new member i cannot post it yet.
but search THE DROID GUY SAMSUNG GALAXY S6 EDGE COMMON PROBLEMS
hope this helps

Problems with screen brightness, LED notifications, Xprivacy / slowness

So I seem to have a whole bunch of problems with my D851, and am curious if others have the same problems and know of fixes. Mine has 20g (stock Lollipop) installed, and is rooted.
Main problem: enabling Xprivacy makes this phone become significantly slower. The settings menu crawls with Xprivacy turned on. Anyone else experience this?
Auto brightness is *way* too dim to use. Surely, I must not be the only person experiencing this? I see a few people mention it in passing, but it doesn't seem to be an big deal. Are people not using auto brightness? Or do most folks not have this issue? All other devices I have with Lollipop allow a brightness range if set on auto. This one doesn't ? Can I get this feature somehow?
Even when I set the brightness manually, it keeps getting reset to 100% some half the times it wakes up from sleep. Anyone else experiencing this? Anyone know of a fix?
Also, the display off time never gets set. I set it to 30sec or 1min, and it always gets reset two 2 min.
The notification LED is virtually useless. It blinks once in like 20 seconds when I get an email (gmail app). I rely on this. Is there a fix to get it to blink every second or 2 seconds? Light manager didn't work.
What I don't understand is, since I experienced all these issue on pretty much a phone out of the box + rooted, I'm surprised they don't seem to be common problems.
Thanks in advance.

fivemill said:
So I seem to have a whole bunch of problems with my D851, and am curious if others have the same problems and know of fixes. Mine has 20g (stock Lollipop) installed, and is rooted.
Main problem: enabling Xprivacy makes this phone become significantly slower. The settings menu crawls with Xprivacy turned on. Anyone else experience this?
Auto brightness is *way* too dim to use. Surely, I must not be the only person experiencing this? I see a few people mention it in passing, but it doesn't seem to be an big deal. Are people not using auto brightness? Or do most folks not have this issue? All other devices I have with Lollipop allow a brightness range if set on auto. This one doesn't ? Can I get this feature somehow?
Even when I set the brightness manually, it keeps getting reset to 100% some half the times it wakes up from sleep. Anyone else experiencing this? Anyone know of a fix?
Also, the display off time never gets set. I set it to 30sec or 1min, and it always gets reset two 2 min.
The notification LED is virtually useless. It blinks once in like 20 seconds when I get an email (gmail app). I rely on this. Is there a fix to get it to blink every second or 2 seconds? Light manager didn't work.
What I don't understand is, since I experienced all these issue on pretty much a phone out of the box + rooted, I'm surprised they don't seem to be common problems.
Thanks in advance.
Click to expand...
Click to collapse
I think maybe you got a dud. Try flashing a rom and see if problems stop,if they don't then get another phone through warranty

Still_living714 said:
I think maybe you got a dud. Try flashing a rom and see if problems stop,if they don't then get another phone through warranty
Click to expand...
Click to collapse
Thanks, I think that was a part of it, but not all of it. I tried flashing stock on a different unit, and I found that the brightness issue was largely (but not fully) better, and the display settings not getting set issue went away. The Xprivacy and LED notification issues remain, and will occur on all units as far as I can tell. I haven't seen anything here that contradicts that info.

fivemill said:
Thanks, I think that was a part of it, but not all of it. I tried flashing stock on a different unit, and I found that the brightness issue was largely (but not fully) better, and the display settings not getting set issue went away. The Xprivacy and LED notification issues remain, and will occur on all units as far as I can tell. I haven't seen anything here that contradicts that info.
Click to expand...
Click to collapse
I have xprivacy and my phone is still very smooth plus my LED works just fine. I even changed the colors

Still_living714 said:
I have xprivacy and my phone is still very smooth plus my LED works just fine. I even changed the colors
Click to expand...
Click to collapse
Thanks a bunch for the info, this is good to know, and good to hear from another D851 user. The Xprivacy issue may be less easy to measure. The LED issue may be more objective. I have no trouble with changing LED colors. It's the blink rate that's at issue. Are you able to get it to blink say, twice per second, or even once per second when you get new email in your gmail app if you use that? Are you using any kind of an LED app?
Also, are you running Lollipop? Stock? Rooted? Thanks.

fivemill said:
Thanks a bunch for the info, this is good to know, and good to hear from another D851 user. The Xprivacy issue may be less easy to measure. The LED issue may be more objective. I have no trouble with changing LED colors. It's the blink rate that's at issue. Are you able to get it to blink say, twice per second, or even once per second when you get new email in your gmail app if you use that? Are you using any kind of an LED app?
Also, are you running Lollipop? Stock? Rooted? Thanks.
Click to expand...
Click to collapse
I'm always rooted lol I'm running fulmics 5.0 and in the settings it gives you the option of length and speed of the LED. I highly recommend that rom if you want to try out marshmallow.

Still_living714 said:
I'm always rooted lol I'm running fulmics 5.0 and in the settings it gives you the option of length and speed of the LED. I highly recommend that rom if you want to try out marshmallow.
Click to expand...
Click to collapse
Very good to know again, thanks for the recommendation! And the LED options are an additional reason. I'll try out fulmics soon.

Ambient Display Screen Flashes

Hi Guys!~
Hope all is well !!
... recently I came across my rooted android 11 Pixel 3XL got a screen flashes with bright home screen background during the screen turning off and entering ambient display mode.
I try my best to find a solution but haven't found one yet.
I have tried to reflash to stock, also doesn't fix the problems.
... the only solution I found at this moment is to get android 12 beta which the transition animation from turning off the screen to the wake up of ambient display is totally different and I still prefer to stay with rooted android 11.
Your browser is not able to display this video.

Sounds like a hardware failure, display or mobo.

blackhawk said:
Sounds like a hardware failure, display or mobo.
Click to expand...
Click to collapse
It only happens when the screen turning off from home screen or app.
Trying to shoot a vid to show the issue now.

haritvii said:
It only happens when the screen turning off from home screen or app.
Trying to shoot a vid to show the issue now.
Click to expand...
Click to collapse
If you tried multiple roms especially the stock* one unless it's something you loaded after the flash, it's got to be hardware related. It's possible the non stock rom blew out some hardware too.
Try setting brightness to manual.
A rework around may be the only viable solution.
You ever wonder what happens when one or two of the billions of semiconductor junctions/resistors/caps fails in the chipset or display? You might be looking at an example
It could be a loose connection, or a faulty ribbon cable/connector, a subassembly maybe even battery (if so there be more symptoms).
*unless a known issue in this device.

blackhawk said:
Sounds like a hardware failure, display or mobo.
Click to expand...
Click to collapse

blackhawk said:
If you tried multiple roms especially the stock* one unless it's something you loaded after the flash, it's got to be hardware related. It's possible the non stock rom blew out some hardware too.
Try setting brightness to manual.
A rework around may be the only viable solution.
You ever wonder what happens when one or two of the billions of semiconductor junctions/resistors/caps fails in the chipset or display? You might be looking at an example
It could be a loose connection, or a faulty ribbon cable/connector, a subassembly maybe even battery (if so there be more symptoms).
*unless a known issue in this device.
Click to expand...
Click to collapse
Thank you so much, now I got a great reason to get a new Pixel 6 then

haritvii said:
Thank you so much, now I got a great reason to get a new Pixel 6 then
Click to expand...
Click to collapse
I could be wrong... and even if it is hardware that doesn't mean a work around doesn't exist to make it usable.
Play with it, Androids wuv attention

Screen unresponsive for a minute after unlocking

Any time the screen turns off and I turn it back on, I have to wait 30 seconds to a minute before the touch screen is responsive at all. I've tried using my fingerprint or removing all screen security and that doesn't seem to make a difference. Has anyone else run into a similar issue? Any idea on how to fix it?

zebinadams said:
Any time the screen turns off and I turn it back on, I have to wait 30 seconds to a minute before the touch screen is responsive at all. I've tried using my fingerprint or removing all screen security and that doesn't seem to make a difference. Has anyone else run into a similar issue? Any idea on how to fix it?
Click to expand...
Click to collapse
What android version are you running? Do you have many apps installed? Have you tried restoring back to factory defaults?

I believe it started after upgrading to 9 manually a few weeks ago. But I've tried a few different ROMs with the same situation. I have not rolled back to 8 to test that yet. It happens right out of the gate without installing any additional apps as well. I've done multiple full wipes, including unlocking the bootloader that for sure wiped everything with no change to the situation.

zebinadams said:
I believe it started after upgrading to 9 manually a few weeks ago. But I've tried a few different ROMs with the same situation. I have not rolled back to 8 to test that yet. It happens right out of the gate without installing any additional apps as well. I've done multiple full wipes, including unlocking the bootloader that for sure wiped everything with no change to the situation.
Click to expand...
Click to collapse
Fastboot upgrade? If not, i'd download 9 stock RETAIL and just flash it all with fastboot

Ok, I'll try that when I get a chance. we'll see if it works.

marcost22 said:
Fastboot upgrade? If not, i'd download 9 stock RETAIL and just flash it all with fastboot
Click to expand...
Click to collapse
I just re-flashed via fastboot 9 stock RETAIL found here. Looks like I'm still having the same issue as before with the touch screen not being responsive after turning the screen back on. Even if it's only been off for half a second, it will still not be responsive for a minute
Any further ideas? Or is there a better location to get the RETAIL image for XT1710-01?

zebinadams said:
I just re-flashed via fastboot 9 stock RETAIL found here. Looks like I'm still having the same issue as before with the touch screen not being responsive after turning the screen back on. Even if it's only been off for half a second, it will still not be responsive for a minute
Any further ideas? Or is there a better location to get the RETAIL image for XT1710-01?
Click to expand...
Click to collapse
This is gonna sound weird, but have you changed your screen at all?

marcost22 said:
This is gonna sound weird, but have you changed your screen at all?
Click to expand...
Click to collapse
Actually, yes. Just after getting the phone, it was dropped and the screen had to be replaced. The fingerprint sensor has been loose ever since then too. But this was never an issue until flashing a new ROM

zebinadams said:
Actually, yes. Just after getting the phone, it was dropped and the screen had to be replaced. The fingerprint sensor has been loose ever since then too. But this was never an issue until flashing a new ROM
Click to expand...
Click to collapse
did you have someone else replace your screen? If so, and it might sound weird, they might have installed an LCD screen instead of OLED; and then modified the stock rom for that. You might not know, but OLED and LCD have very different power profiles, so when turning LCD on you can just blast it, meanwhile oled you need to slowly bring the power up. This is what might be causing your issues

marcost22 said:
did you have someone else replace your screen? If so, and it might sound weird, they might have installed an LCD screen instead of OLED; and then modified the stock rom for that. You might not know, but OLED and LCD have very different power profiles, so when turning LCD on you can just blast it, meanwhile oled you need to slowly bring the power up. This is what might be causing your issues
Click to expand...
Click to collapse
Yeah, I had someone else install the screen for me. How would I go about checking if its LCD vs OLED? And do you know what would need to be modified in order to fix it if it is LCD?

zebinadams said:
Yeah, I had someone else install the screen for me. How would I go about checking if its LCD vs OLED? And do you know what would need to be modified in order to fix it if it is LCD?
Click to expand...
Click to collapse
You would need to remove the screen. Otherwise you can use something like AOD and check if the whole display lights up vs only the clock or whatever. On an LCD screen the whole display will light up a tiny bit vs complete black on OLED.
You would need to modifiy the dtb's and kernel, but it's something i would be able to do for you

marcost22 said:
You would need to remove the screen. Otherwise you can use something like AOD and check if the whole display lights up vs only the clock or whatever. On an LCD screen the whole display will light up a tiny bit vs complete black on OLED.
You would need to modifiy the dtb's and kernel, but it's something i would be able to do for you
Click to expand...
Click to collapse
It looks to me like OLED to me with only the clock lighting up. I could still take the screen off at some point to verify if needed.
Thanks for all of your help by the way

zebinadams said:
It looks to me like OLED to me with only the clock lighting up. I could still take the screen off at some point to verify if needed.
Thanks for all of your help by the way
Click to expand...
Click to collapse
I don't know if it's the reflection, but is there some bleed around the clock? Like is the dark areas lighter compared to the rest of the screen?

marcost22 said:
I don't know if it's the reflection, but is there some bleed around the clock? Like is the dark areas lighter compared to the rest of the screen?
Click to expand...
Click to collapse
I think it's just the reflection? Here's a shot of my Nexus 6p right beside it and I think they look basically the same.
The phone is used almost exclusively for kids videos so it's not the end of the world if I never get it fixed, but at the same time, it would alleviate some frustration when I'm helping my daughter turn a show on.

zebinadams said:
I think it's just the reflection? Here's a shot of my Nexus 6p right beside it and I think they look basically the same.
View attachment 5544389
The phone is used almost exclusively for kids videos so it's not the end of the world if I never get it fixed, but at the same time, it would alleviate some frustration when I'm helping my daughter turn a show on.
Click to expand...
Click to collapse
Yeah, to me it still looks significantly brighter around the clock

marcost22 said:
Yeah, to me it still looks significantly brighter around the clock
Click to expand...
Click to collapse
Ok, I'm willing to try modifying the ROM if that'll get rid of the stupid touch screen delay. How difficult is it? I know you said you would be willing to do it for me, but if it's not something that will persist through an update (I had been running AICP) and it's something that I could learn to do, all the better. If that's not realistic, that's fine as well.

zebinadams said:
Ok, I'm willing to try modifying the ROM if that'll get rid of the stupid touch screen delay. How difficult is it? I know you said you would be willing to do it for me, but if it's not something that will persist through an update (I had been running AICP) and it's something that I could learn to do, all the better. If that's not realistic, that's fine as well.
Click to expand...
Click to collapse
[REFERENCE] How to compile an Android kernel
Introduction Hello everyone, I will be going over how to compile a kernel from beginning to end! Prerequisites: A Linux environment (preferably 64-bit) Knowledge of how to navigate the command line Common sense A learning spirit, there will be...
forum.xda-developers.com
Is a great guide, you'd need to follow the clang guide tho, as our kernel IS clang-compiled, and i recommend repacking the boot.img
You'd need to change this line
kernel_motorola_msm8953/msm8953-albus.dtsi at 7befedacd91b84ed737b691671c088c89e394f66 · AICP/kernel_motorola_msm8953
Contribute to AICP/kernel_motorola_msm8953 development by creating an account on GitHub.
github.com
In your source to be
qpnp,qpnp-labibb-mode = "lcd";
If i'm right, after doing that and flashing it the issue will be fixed. Otherwise when you try to turn on the display it will cause a kernel panic
You would need to reflash this boot.img after every update, and redownload sources everytime i do something to kernel.