Ok so I downloaded a screen filter to make the screen darker at night and now I noticed when I'm in the YouTube app and I go to full screen the screen gets yellowish and I can see a few faint lines in the display. I tried to disable it and that didn't work so then I deleted the app and uninstalled all updates and it still does the same thing. Anybody else had this problem and how do I fix it? Really don't want to restore the whole phone. Just checked and its not just in the app but its on the website version too. Real bummer probly gonna have to ****ing reset me phone cause the app messed up the brightness.
This is ****ing bull**** I just reset my phone and the problems still here.
Related
Hello,
the following problem appears when i try to unlock the phone after some hours: i can see my home screen, but the screen stays extremely dim. When i try to start an app (e.g. browser) the screen turns black. I can unlock it again, but the screen stays dim. after some unlocking the screen becomes normal (normal brightness) and also the apps are startable.
i am using autobrightness, the stock firmware, 4.1.1 (i9300xxdlih) power saver is not turned on.
thx, i hope you can help me solving this problem
fanbayer
Fanbayer said:
Hello,
the following problem appears when i try to unlock the phone after some hours: i can see my home screen, but the screen stays extremely dim. When i try to start an app (e.g. browser) the screen turns black. I can unlock it again, but the screen stays dim. after some unlocking the screen becomes normal (normal brightness) and also the apps are startable.
i am using autobrightness, the stock firmware, 4.1.1 (i9300xxdlih) power saver is not turned on.
thx, i hope you can help me solving this problem
fanbayer
Click to expand...
Click to collapse
i updated mobile phone to android versiopn 4.1.2. this morning. Unfortunately the problem still appears.
Maybe its a hardware defect?
Try to disable somehow light sensor and change settings to non auto brightness.
Sent from my GT-I9300 using xda app-developers app
d0hn said:
Try to disable somehow light sensor and change settings to non auto brightness.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
i disabled auto brightness and set the brightness to the highest level. But its still same: very dim and after a while a black screen; after a few times of unlocking, the display works normally
I have just seen the same issue on a friend's S3.
Anyone else? I feel like this is a very big issue that is still lurking in a lot of devices.
I tried it myself and I toggled the power button to turn the screen on and off.
It doesn't take long but sometimes when the screen turns back on, it's super dim and you can faintly see the lockscreen image.
You have to cycle the screen several more times to get it to the 'correct' brightness, and no it is NOT a brightness setting.
It's some hardware issue in the phone.
Sorry for the necrobump, but I only found this thread. I have this problem too since about a week back. It makes my phone useless at times. I first thought it was a software issue. I have an app (called Twilight) for dimming the screen more than normal settings and also toning it, for nightime use, and I thought that was the culprit first, but nope. I have flashed rom, recovery, wiped all caches I can think of. Still happens, just now I was in the middle of installing android revolution hd, and the screen ultradimmed on me so I can't finish the process
Thing is, a few months ago I managed to crack my screen by way of gravity and concrete. I let the samsung brand service centre in Stockholm repair it for me (it is out of warranty) and this issue with the dimming never happened before that. Then again, it didn't happen directly afterwards either... but still. So, I am thinking: either me dropping it caused more damages and this is because of that. Or the service center did a bad install of the new screen. Or, the replacement screen that was installed has a defect in itself. I am leaning a bit towards the third explanation... maybe different batches of screens?
Does anyone have any ideas? If I am to contact the service center and complain about their work I would like to be able to point towards a "known problem"...
8Fishes said:
I have just seen the same issue on a friend's S3.
Anyone else? I feel like this is a very big issue that is still lurking in a lot of devices.
I tried it myself and I toggled the power button to turn the screen on and off.
It doesn't take long but sometimes when the screen turns back on, it's super dim and you can faintly see the lockscreen image.
You have to cycle the screen several more times to get it to the 'correct' brightness, and no it is NOT a brightness setting.
It's some hardware issue in the phone.
Click to expand...
Click to collapse
Take it back, if it didn't happen before then the new screen is most likely.
It isn't a common problem
I don't know if this is the right area but here it goes.
The area where the software buttons are located are not being affected by Twilight anymore. I don't know if the problem is with Twilight per se or something else, but I do know the problem appeared right after I tried using Muzei, I was messing around with it, seemed like a good app but I was enjoying the wallpaper I was previously using, but when I went back to it this glitch appeared, I'll link a screenshot of the phone that better illustrates it.
http://imgur.com/chnlK2K
On the lock screen it seems to work without problems:
http://imgur.com/CBWPBHI,uuy5ao4#1
I know it's a minor bug but it's one of those little things that can be very annoying.
I've already tried clearing the data both from Twilight and Muzei, and removing and re-installing them, did not work.
I don't know if it matters but I messed around with the blur and dim settings on Muzei that first time I used it, although since clearing the data and re-installing it they are back to default. Also, the problem persists with other wallpapers, even with the Muzei ones.
Also, using a Motorola Moto G with KitKat, not rooted and stock rom and launcher.
Anyone ?
I really wish I wouldn't have to make a factory reset just because of this but it's really annoying.
Twilight has never covered the software buttons for me on my Moto G. I switched to EasyEyes and it seems to work fine, the brightness of the buttons doesn't seem to change but at least it doesn't look nearly as wrong anymore.
I've had the same thing appear today. Bar at bottom of screen with software buttons undimmed by twilight. No new apps installed & not using Muzei. Phone is Oneplus 2.
Is anyone else having issues with AOD turning off even with slight darkness. For some reason my AOD keeps turning off even though there still some light in the room. It used to stay on when I wake up at 6am when there some sunlight but now it just turns off. I have to point the phone directly to the light sometimes to get it to turn on. Don't have any screen protector that is blocking the light sensor and seems to function correctly checking the debug mode (*#0*#). I have to reboot the phone to fix the issue but after a few days it goes back to being wonky.
yeah, i updated it via Samsung Galaxy App store, then did a data clear in the setting menu and now it works. But mine did the exact same thing.
clearing the data still causes me the problem.. Only fix for me is to reboot the phone =/
Do you have a screen protector?
Tidbits said:
Do you have a screen protector?
Click to expand...
Click to collapse
I have a screen protector but have all the cutouts that isn't blocking the proximity sensor. I've tested the sensor in debug mode and no issues at all.
what was updated or installed recently that had this started happening with. It may be an app that introduced a bug. Did you try and see if there is a AOD update?
Tidbits said:
what was updated or installed recently that had this started happening with. It may be an app that introduced a bug. Did you try and see if there is a AOD update?
Click to expand...
Click to collapse
what screwed it up was the AOD update (go figures ).. I reverted back to the original before the update but somehow it's broken now. As mention it works like it should after a reboot but after a few days it becomes all wonky.
Hey everyone,
I'm hoping someone can help me figure this out.
I just bought this phone used and I'm noticing a weird issue in Android
There are 3 dots near the top of the display that I can see flashing.
I've tried doing a reset to see if this works, but it doesn't.
These dots ONLY show up after Android is initialized. On the same screen during the reset process, you can't see them. I've included a couple of videos showing what I'm talking about
First video shows the phone after a factory reset
Second video shows the boot screen after a restart from Android
Third video shows it during normal app usage in Android
Fourth video shows the recovery menu to ensure Android hasn't loaded
https://www.youtube.com/watch?v=YfAFf2UOwq4
viper98 said:
Hey everyone,
I'm hoping someone can help me figure this out.
I just bought this phone used and I'm noticing a weird issue in Android
There are 3 dots near the top of the display that I can see flashing.
I've tried doing a reset to see if this works, but it doesn't.
These dots ONLY show up after Android is initialized. On the same screen during the reset process, you can't see them. I've included a couple of videos showing what I'm talking about
First video shows the phone after a factory reset
Second video shows the boot screen after a restart from Android
Third video shows it during normal app usage in Android
Fourth video shows the recovery menu to ensure Android hasn't loaded
https://www.youtube.com/watch?v=YfAFf2UOwq4
Click to expand...
Click to collapse
Those are the proximity sensors.
The bad news is that you need to tell Motorola to replace your phone.
I'm not sure what the good news is here.
I have the three dots too, just purchased 5 days ago. It's just the proximity sensors. I know it's kinda annoying, but they only flash occasionally and it's not easy to see unless you're in darkness or doing something to trigger them. I'm choosing to ignore them -- seems all of the moto edge phones do this, really doesn't bother me and I can't be bothered returning the phone when the screen seems to be working OK.
viper98 said:
Hey everyone,
I'm hoping someone can help me figure this out.
I just bought this phone used and I'm noticing a weird issue in Android
There are 3 dots near the top of the display that I can see flashing.
I've tried doing a reset to see if this works, but it doesn't.
These dots ONLY show up after Android is initialized. On the same screen during the reset process, you can't see them. I've included a couple of videos showing what I'm talking about
First video shows the phone after a factory reset
Second video shows the boot screen after a restart from Android
Third video shows it during normal app usage in Android
Fourth video shows the recovery menu to ensure Android hasn't loaded
https://www.youtube.com/watch?v=YfAFf2UOwq4
Click to expand...
Click to collapse
3 dots
I have had a lot of issues with my phone screen but I've never seen the 3 dots
hello
The device I just received has the same problem as you. The three dots flashing on the screen should be sensors
tveith said:
I have the three dots too, just purchased 5 days ago. It's just the proximity sensors. I know it's kinda annoying, but they only flash occasionally and it's not easy to see unless you're in darkness or doing something to trigger them. I'm choosing to ignore them -- seems all of the moto edge phones do this, really doesn't bother me and I can't be bothered returning the phone when the screen seems to be working OK.
Click to expand...
Click to collapse
Yes we have a common problem, but the three dots flashing on the screen are supposed to be sensors, and I wonder what kind of sensor it is
Yes those 3 dots worried me te first day I noticed them but I just tested the proximity sensor and they are under the screen so is not a issue.. but I have a question.. did you guys experienced a battery drain in stand by?
I purchased my S21 about 5 weeks ago and I am not sure if I have been experiencing this issue since I bought it but in the last week, I have noticed this issue. When my phone is locked, the AOD will either show for a few seconds to a minute or just won't show. I've ensured it is set to always show, power-saving not set to turn it off, no Bixby routines and any updates are installed for phone/AOD. I've even factory reset my phone and removed the case and screen protector and the issues are still persisting. Does anyone else experience this issue?
Disable all power management... it screws up all kinds of things.
Does AOD show if you tap the screen?
I have disabled all power management that I am aware of and still experiencing issues. I've set it to show on tap and while it worked the first time, subsequent taps do not show the AOD
Video demonstrating AOD tap to show issue
Sounds like a firmware glitch or the flash was corrupted.
Double check all AOD and screen lock settings.
Try turning AOD always on.
Try disabling screen lock... a lock out is the last thing you want anyway.
Play with it... Android's wuv attention.
The case or screen protector won't do this more than likely.
blackhawk said:
Sounds like a firmware glitch or the flash was corrupted.
Double check all AOD and screen lock settings.
Try turning AOD always on.
Try disabling screen lock... a lock out is the last thing you want anyway.
Play with it... Android's wuv attention.
The case or screen protector won't do this more than likely.
Click to expand...
Click to collapse
I normally use AOD always on, I'd tried the tap on the option to test. Going to try flashing it today to see if that helps despite the factory reset not helping.
So I've flashed the stock firmware back onto my device and the issues are still persisting. I've contacted support through the Samsung Members app and it's been escalated to the Research and Development team and am just waiting to hear back.
Did you update any Samsung apps after the reload before testing it? Go with the factory app loads.
Try disabling the lock screen... they tend to end up locking out the intended user anyway, sooner or latter.
If no one else is having this issue it very well maybe a hardware issue.
Did you ever wonder what happens when one or two micro transistor junctions out of the millions in a phone fail? Yes, well...
Unfortunately I can't recall if Samsung apps updated before I tested. I've already factory reset a few times so I'd rather avoid that for now. I've noticed the issues occur when using auto-brightness on AOD in lower light settings. When I say lower light, I mean in my study during the day which I never experienced issues with on my S20 FE. I've sent a report to Samsung Members and am waiting on them to come back to me.
The you
brodieb321 said:
Unfortunately I can't recall if Samsung apps updated before I tested. I've already factory reset a few times so I'd rather avoid that for now. I've noticed the issues occur when using auto-brightness on AOD in lower light settings. When I say lower light, I mean in my study during the day which I never experienced issues with on my S20 FE. I've sent a report to Samsung Members and am waiting on them to come back to me.
Click to expand...
Click to collapse
Did you ever get this fixed. I have the exact same issue on my s20 ultra
Edit: Nevermind just fixed it after 3 days troubleshooting. Oddly it was the the disable AOD while in power saving mode that needed to be disabled even though I don't use power saving mode. Samsung never seem to amaze me with these dumb persistent bugs.
Glad to see you solved the issue. I'd already confirmed this setting was off for me. It's still happening. Looks like it's something to do with the level of light detection as the issue only happens when I have auto brightness set for the AOD. The problem is it's not even that dark when it's happening and never occurred with my S20 FE.