Can anyone make an ultimate fix for galaxy s4 smearing?
Are you talking about the graphical smearing/tearing that happens when you, for example, scroll?
This is caused by the pixels. In AMOLED devices, when a pixel shows black, it is actually turned off. However, there is a delay when turning that pixel back on. So if pixels have to change from black to colored and vice versa (for example, scrolling through your app drawer if it has a black background), this graphical glitch occurs because of the delay from turning the pixels off and on.
Samsung has rectified this issue on their stock ROMs by eliminating true black, making the pixels always on. This will also negate the battery saving effects of AMOLED displays when showing black. This is the only way I know to fix the problem.
If you were referring to another "smearing" please elaborate and we may be able to help better.
I'm talking about that one that you said.. but in 3rd part apps in 4.3 stock android roms there isn't any fix ,apart Screen adjuster setting contrast -10, i wanted to know if someone can change blacks in very dark grey keeping the other colors , not changing all the colors setting contrast -10 or SmearFix app
http://forum.xda-developers.com/showthread.php?t=2372357 Have a try!
Morning.
I noticed that even when I am in a somewhat dark room, the flash will not trigger when set to "Auto" unless the room is nearly pitch black dark. If I set to "On", the flash works fine. This happens with both the popular camera mods too.
Is this normal behavior by the phone or is my light sensor being strange?
Edit: Sorry, skipped past the question checkbox.
I've noticed with my G2 for quite a while that the screen brightness will dim by itself with auto brightness turned off. I have the brightness set at 70%. When I wake the screen and go to Gmail or any other light themed app where it's noticeable, the screen will dim approximately 5%. I did a little testing this morning and it only happens when the area is well lit. In the dark hallway, it wouldn't dim at all. I am running Cloudy G3 1.2 on my LS980. I've noticed the same thing on versions 1.3 and 2.0. I do think though, it's likely something to do with the proximity sensor rather than the ROM. I've tried different kernels and the same thing happens. I also have Xposed installed with the Tweaksbox module, but with Xposed disabled it doesn't change. I haven't had time to go back to stock and test but will try soon if nothing is resolved.
Anyone else experience this?
I'm having a couple issues with my nexus 4 after upgrading manually to Lollipop with the system image from Google Developers.
Sometimes, when the screen goes idle and turns off automatically or when it's turned off manually using the power button, the screen flashes on a higher brightness and shows the lockscreen before turning off. (I'm guessing the desired result is that the lockscreen should appear 'on screen' after the backlight is completely off).
What this causes is that when turning off the screen, the screen dims with the animation (fade to black and turn off), but before (and sometimes after) the animation is complete, it flashes for a few milliseconds displaying the lockscreen/background, even when locking the phone inside an app.
I could upload a video of the issue at a later time.
This bug didn't happen on any version/rom that went through my phone (many stock, many custom). Although I haven't tried installing another 5.0 ROM / AOSP.
The update also brought back a [hardware?] issue this Nexus 4 unit also has had since I got it. When dimming the screen using the brightness slider, sliding to the lowest setting turns off the backlight completely (effectively making the screen pitch black instead of dimming). This issue has been reported before and I was using Gravitybox to override the system lowest brightness level. Could these two issues be related? (Note that this issue didn't trigger this behavior before).
This issue has been reported by other users here:
http://forum.xda-developers.com/nexus-4/help/zero-brightness-t2168071
http://forum.xda-developers.com/nexus-4/help/problem-nexus-4-brightness-t2052857
https://www.youtube.com/watch?v=dvgt17sKQsU < this shows the screen going pitch black at lowest brightness, it happens either from the widget, the slider, and the option in settings.
Any ideas on why it happens or how can it be corrected?. Do you also have this issue?.
Many thanks in advance.
For some reason the notification LED doesn't function on my XL2. I installed LED Blinker Pro and it works like a charm. Just thought I would share incase anyone else is having this issue.
Settings, apps and notifications, notifications, blink light. It's off by default.
Now go get lightflow and go nuts.
Sent from my Pixel 2 XL using Tapatalk
I did that and it still didn't work. That app solved the problem though.
Have you used light manager? And if so which do you like better. Im using Light Manager but that app you showed looks more polished.
Also have you noticed this time around the phone has trouble making some colors. Like yellow looks kinda yellow/green and white is kinda blue/white
Light Flow works. But it seems that the built-in notification light triggers first overriding Light Flow. For example, if I get a text message (fast blue blinking light set in Light Flow), I get the slow, white stock notification. If I unlock and then immediately re-lock the phone Light Flow kicks in with the set blink/color settings. I've tried to disable the stock light notification, but if I do Light Flow won't work at all.
ckarrow2 said:
Light Flow works. But it seems that the built-in notification light triggers first overriding Light Flow. For example, if I get a text message (fast blue blinking light set in Light Flow), I get the slow, white stock notification. If I unlock and then immediately re-lock the phone Light Flow kicks in with the set blink/color settings. I've tried to disable the stock light notification, but if I do Light Flow won't work at all.
Click to expand...
Click to collapse
Light Flow didn't work well for me.
So is this just a software issue that could be addressed by Google in the future?
Sent from my Pixel 2 XL using Tapatalk
Andebad said:
So is this just a software issue that could be addressed by Google in the future?
Click to expand...
Click to collapse
My 6p was the same way when I first got it.... But once they built in led notification into the settings of the roms I then got more cookies and very crisp distinct colors too..... Im sure the custom roms and kernel will fix this and the OLED panel color issues
Light Flow works perfectly for me.
Enable the light in system settings.
Disable it when there is an option in specific apps.
Make sure it has the right permissions.
Sent from my Pixel 2 XL using Tapatalk
I installed the New Pixel 2 XL Launcher on my OG Pixel XL. My light stopped after installing, so I had to go to the launcher settings (long press blank area on home screen, Home settings, Notification Dots, Blink Light) and turn on the light in there to get it going again.
thacounty said:
I installed the New Pixel 2 XL Launcher on my OG Pixel XL. My light stopped after installing, so I had to go to the launcher settings (long press blank area on home screen, Home settings, Notification Dots, Blink Light) and turn on the light in there to get it going again.
Click to expand...
Click to collapse
Yep, that's how you get the LED to work. It's really wonky and idk why they buried the setting in that spot.
corywf said:
Yep, that's how you get the LED to work. It's really wonky and idk why they buried the setting in that spot.
Click to expand...
Click to collapse
Right? I found it by accident, and wondered how many people will never find this setting.
thacounty said:
I installed the New Pixel 2 XL Launcher on my OG Pixel XL. My light stopped after installing, so I had to go to the launcher settings (long press blank area on home screen, Home settings, Notification Dots, Blink Light) and turn on the light in there to get it going again.
Click to expand...
Click to collapse
If we ever meet in person, beer and a shot are on me!
I've been looking for that for about 2 days now....
--