I've noticed that the Always On Display now lights up the entire screen, not just the pixels for the clock and date. As you can see in the pics, even the areas that are supposed to be black (i.e. unlit) are lit up in a dark black-ish kind of glow. This seems to be appearing after the most recent update. Is anyone else seeing this issue on their phones? Is this a software issue or a display problem? Would appreciate some insights on this. Thanks.
I dont have this problem
vrblr2405 said:
I've noticed that the Always On Display now lights up the entire screen, not just the pixels for the clock and date. As you can see in the pics, even the areas that are supposed to be black (i.e. unlit) are lit up in a dark black-ish kind of glow. This seems to be appearing after the most recent update. Is anyone else seeing this issue on their phones? Is this a software issue or a display problem? Would appreciate some insights on this. Thanks.
Click to expand...
Click to collapse
Technically speaking black color on AMOLED displays just turns off the pixels of the phone, it won't light up like what I saw from your picture.
If you are using a screen filter app such as twilight or night owl disable it and check, if not maybe try to reset your phone and I hope that is software related nothing more.
sa3d12 said:
Technically speaking black color on AMOLED displays just turns off the pixels of the phone, it won't light up like what I saw from your picture.
If you are using a screen filter app such as twilight or night owl disable it and check, if not maybe try to reset your phone and I hope that is software related nothing more.
Click to expand...
Click to collapse
Not using those apps. I did a phone reset, but the problem persists.
Did You purchase Your phone from an official Samsung seller? Only phones with non AMOLED panel would light up the whole screen.
Edit: just checked my AOD, Your AOD looks slightly different than mine. On my AOD I can see a date and two small icons.
Can you post similar pictures with the default AOD clock widget?
I'm also experiencing the same issue with my S7 Edge. Problem started out of the blue two days ago; there might have been Play Store updates but I dont reckon any system updates that day. I've been using the night clock for weeks and it was working fine before now.
The problem seems to affect only AOD and night clock, since the edge feed (rubbing the side) works completely fine - only lights the used pixels. AOD and night clock light up the whole screen (not much, but clearly visible in a dark room, grayish background)
Tried resetting and flashing older firmwares via Odin but nothing changed. Hope we find an answer to this, it's shame I cant use the night clock nor the AOD since its killing battery now. :/
I remember S6 edge having the same issue with night clock?
vrblr2405 said:
I've noticed that the Always On Display now lights up the entire screen, not just the pixels for the clock and date. As you can see in the pics, even the areas that are supposed to be black (i.e. unlit) are lit up in a dark black-ish kind of glow. This seems to be appearing after the most recent update. Is anyone else seeing this issue on their phones? Is this a software issue or a display problem? Would appreciate some insights on this. Thanks.
Click to expand...
Click to collapse
Mine is working fine. You must have received an update to something in the last few days if it worked before. Either that or it's a hardware issue.
This seems like a LCD and not AMOLED.. Did you get your display changed due to any reason?
OP stated that the problem occured after an update, so I think it was working fine before that? So I wouldnt say he has S7 edge with LCD display (for whatever reason that's even possible). I can say this for sure about my situation anyway. No display changes or any other repairs, it just started malfunction for no apparent reason.
I tried a third party app for AOD and it worked flawlessy... so the built-in AOD (& night clock) lights the whole screen, while edge feed and 3rd party AOD don't. Confusing.
@vrblr2405 : did you try night clock or 3rd part aod? Is the problem still there?
amritpal2489 said:
This seems like a LCD and not AMOLED.. Did you get your display changed due to any reason?
Click to expand...
Click to collapse
No. This is not an LCD, it's an AMOLED. This is an S7 Edge that I bought two weeks ago. Haven't changed the display or anything like that.
McKis said:
OP stated that the problem occured after an update, so I think it was working fine before that? So I wouldnt say he has S7 edge with LCD display (for whatever reason that's even possible). I can say this for sure about my situation anyway. No display changes or any other repairs, it just started malfunction for no apparent reason.
I tried a third party app for AOD and it worked flawlessy... so the built-in AOD (& night clock) lights the whole screen, while edge feed and 3rd party AOD don't. Confusing.
@vrblr2405 : did you try night clock or 3rd part aod? Is the problem still there?
Click to expand...
Click to collapse
This is the native AOD that comes preinstalled. Version 1.4.02. I've noticed that the edge clock also lights up the whole screen. Could you tell me which third party AOD app to use ? That way I can check and identify if it is a display problem or a software issue.
Try a fresh ODIN install of latest stock firmware
vrblr2405: I used (well, tried) Always on Screen by FayaX. Just make sure you disable the built-in AOD first and give the app the permissions it's asking for. Could you also check if the edge feed is working properly and doesn't lit up the screen? You know, the rubbin' thingy If those two work properly, I'm certain we are facing the same issue
@amritpal2489 : flashing stock didn't help on my situation, but of course it's always good to try.. I've been going through different (stock)firmwares now, just to see if something would change. No luck so far, downloading third one now.
Is there more to reset than the 4 files (AP, BL, CP, CSC)? How's the re-partition in Odin?
I'm unrooted, so I'll stick with stock fw's, but I'm wondering if there is something that's not "resetting" or if I can do something more to get to start every bit and piece from scratch.
Don't even think about re-partitioning in ODIN.. Its not required.
Moreover if you have already flashed stock firmware using ODIN then it is surely a hardware fault buddy. Get it checked at authorised service centre even if it is out of warranty. They will let you know the exact issue. Getting it repaired through them is your choice finally.
Yeah I guess that's what I need to do. Luckily there is a Samsung Service Center nearby.
I just can't understand why would the exactly same function work on a different app if it's hardware related. That's the reason I'm baffled with things to try to get it working.
@vrblr2405, let me know how it works out and share your thoughts, thanks!
McKis said:
vrblr2405: I used (well, tried) Always on Screen by FayaX. Just make sure you disable the built-in AOD first and give the app the permissions it's asking for. Could you also check if the edge feed is working properly and doesn't lit up the screen? You know, the rubbin' thingy If those two work properly, I'm certain we are facing the same issue
@amritpal2489 : flashing stock didn't help on my situation, but of course it's always good to try.. I've been going through different (stock)firmwares now, just to see if something would change. No luck so far, downloading third one now.
Is there more to reset than the 4 files (AP, BL, CP, CSC)? How's the re-partition in Odin?
I'm unrooted, so I'll stick with stock fw's, but I'm wondering if there is something that's not "resetting" or if I can do something more to get to start every bit and piece from scratch.
Click to expand...
Click to collapse
So I downloaded the app you said. The AOD works fine with that app. I tried a couple of other third party AOD apps. The AOD works fine - only the pixels for the clock light up. So it seems to be a software issue with the Samsung AOD.
I tried the edge feeds and it works fine. No lighting up the entire screen. The entire screen being lit up happens only with the preinstalled aod apparently.
I don't intend to root my phone at least till the warranty is valid, so sticking with the original Samsung software. Will go to a service center get this checked.
usmanyasin.bk201 said:
Can you post similar pictures with the default AOD clock widget?
Click to expand...
Click to collapse
Which is the default AOD clock?
Just a dumb thought. Wondering if the clock type might make difference. The default one is just a simple white one. Image attached.
usmanyasin.bk201 said:
Just a dumb thought. Wondering if the clock type might make difference. The default one is just a simple white one. Image attached.
Click to expand...
Click to collapse
I thought so too initially. Tried with all the different clock faces. Entire screen still lights up.
Weird. Have you ever rooted the device or is rooted right now?
Related
Hello
I have been having some problems with the main camera on the A500. It has different tints to it. Sometimes the picture seems to be divided in 4 and all 4 squares have a different hue to them. Restoring to factory settings seem to take care of it for a while. Initially I thought it was "skype" that messed it up, but it is not.
I just restarted the tablet and the camera is giving me a yellow tint, with a clear horizontal stripe about 3/4 inch wide through the middle.
The tab has stock 3.2 on it.
I was wondering if anyone has experienced similar problems and if there was a solution to the problem.
Thank you
Well, I would think the problem seems to be some app/apps you have installed. Based on when you do a factory reset, it goes away.
I would just do another factory reset. Then verify it went away. Run it for a couple of days WITHOUT installing any apps. This will probably rule out a hardware issue.
Then install apps, 1 at a time. Use the camera, and look for issues.
Thanx. I will give that a try.
I traced it back to Swift Key X keyboard for tablets. How is that even possible?
Also yahoo messenger is another one that ruins the camera. As soon as I install any of those apps and reboot, the camera is back to normal.
Does anyone out there use either of those apps?
mobilebone said:
I traced it back to Swift Key X keyboard for tablets. How is that even possible?
Also yahoo messenger is another one that ruins the camera. As soon as I install any of those apps and reboot, the camera is back to normal.
Does anyone out there use either of those apps?
Click to expand...
Click to collapse
So, everything is ok?
Rule #1,
Stay away from apps meant for phones.
Yes, they "may" have tested it it on "1" tablet, then gave it a clean bill of health. Maybe.
Moscow Desire said:
So, everything is ok?
Rule #1,
Stay away from apps meant for phones.
Yes, they "may" have tested it it on "1" tablet, then gave it a clean bill of health. Maybe.
Click to expand...
Click to collapse
I thought it would be ok. But after restarting a few times, the camera colors are off. I'm going to root and install a custom 3.2 to make sure it is not the hardware.
Spasiba for all your help )
any news about this problems.
it seems that my iconia has the same problem- i never noticed it because i dont use the rear camera.
i sold it it today and the guy who bought has described something like what you folks are talking about
the strange thing is that i had done a clean boot before i sold it, and the buyer hasnt installed anything on it yet.
im waiting to hear back from him after he tries another clean boot.
anyone else have any ideas ?
I'm having the same problem. I don't use it much, but the camera was ok before. When I tried using it this weekend, it showed colored translucent squares on the sides. It is not a config problem, as there are no effects turned on. The front camera works 100%. I will post a sample when I get home.
If I change the "whites" config to Incandescent, it kind of solves the problem. Sometimes, the squares appear, but not for most the time.
I believe this is not a harware issue, unless that whites configuration is made with hardware (highly doubt it). I don't have Swift key, or Yahoo messenger, or any other apps that use the camera (other than Skype, but it was already installed when the camera worked).
Did anybody find a fix to this? It seems it is only a problem on stock 3.2.
Edit: not an exclusive 3.2 stock issue, it appears that custom roms have this problem as well.
I have the same issue after ICS ota upgrade...
Any ideas?
I haven't had the issue since the ICS upgrade. Only tested once or twice, but it is working properly.
What I did to partially fix it was changing the White Balance to "Incandescent".
All of a sudden yesterday, my trusty old Nexus 10 stopped auto-rotating. Apps that have a fixed orientation will work and rotate the screen, but then the screen stays in that orientation until an app with a different fixed orientation is launched. I downloaded a couple sensor checking apps, and it seems the gyroscope/compass/acceleremeter are just dead. It doesn't register anything at all on the apps. I'm guessing it's just the result of age (no "trauma" to the device such as a drop or anything). Any similar experiences, or thoughts on repairing? I doubt I'll replace the tablet anytime soon, it's really just a media consumption device at this point, though a couple of the games I played used the gryo/accel. My initial thought is it's just time to let it go, use it for what I can, then provide a proper burial when it totally dies.
Hurricane Andrew said:
All of a sudden yesterday, my trusty old Nexus 10 stopped auto-rotating. Apps that have a fixed orientation will work and rotate the screen, but then the screen stays in that orientation until an app with a different fixed orientation is launched. I downloaded a couple sensor checking apps, and it seems the gyroscope/compass/acceleremeter are just dead. It doesn't register anything at all on the apps. I'm guessing it's just the result of age (no "trauma" to the device such as a drop or anything). Any similar experiences, or thoughts on repairing? I doubt I'll replace the tablet anytime soon, it's really just a media consumption device at this point, though a couple of the games I played used the gryo/accel. My initial thought is it's just time to let it go, use it for what I can, then provide a proper burial when it totally dies.
Click to expand...
Click to collapse
probably your sensor is dead(could you try to install some app that display all sensors informations? you should find that easily on the play store).
could you also tell us what is your ROM ?
I'm running the current official LMY49F, but rooted.
Hurricane Andrew said:
I'm running the current official LMY49F, but rooted.
Click to expand...
Click to collapse
Hm indeed your issue should not happen( I think) with lollipop.
MM had some issues with sensors but since you are on lollipop ...
Hehe, well then you should flash a rom with a QS tile to rotate hehe.
LOL, probably not going to mess with flashing a new ROM. Like I said, I only use it for media consumption and some light gaming...nothing that "needs" the gyro, so I'll just live with it until it totally dies
Huh, son a gun. Just flashed the Feb Nexus update via fastboot, and low and behold, it lives again! Looks like it was software related after all.
Hey all.
So I got my MXP about a month ago, as my faithful Nexus 6 has long been deteriorating (#RIPshamu), and I wanted to try something a little different. I love the device and have almost gotten it tweaked and set up just the way I like it. However, I'm currently facing an issue that I can't seem to fix.
When I have a dark gray image on screen, such as the dimming when you pull down the notification bar over a white screen, the left side of my screen flickers rapidly from dark to normal, as if changing brightness. It is most noticeable on higher brightness settings, but plenty present enough on lower ones anyhow. I have made sure that no odd display tweaks in GravityBox are interfering with system presets, and I can't figure out what might be causing this.
I'm hoping it is software-related; I bought the device off-contract and without warranty, as I do with all my handsets, but if the problem is with hardware I should be able to fix it on my own so long as I know what part is causing the issue.
I'm running TruPureXMM with FrankenClark kernel. (systemless SU, magisk/systemless-xposed if any of that matters to you). Can provide logs upon request, but things seem normal to me at first glance.
Anyone else experienced this or have a fix?
I too am running TruPure and Frankenclark. I've been having a similar issue with the display, except it's the bottom half of the screen that is dimmed. I've also noticed that the 'dimming' takes on vertical lines of color depending on what the screen is displaying. The 'dimming' has consistently been transparent for me.
I originally thought that it may have started because I changed some settings using kernel adiutor, however changing those settings back did not fix the issue. I've yet to try returning to stock. I've also noticed the same display issue on boot up and in TWRP, which suggests a hardware problem, not a software one.
Some research online suggests that there is a known display bug with the Moto pure, and that the temporary fix is to reboot, but that doesn't solve the problem for me.
I think I'll try reverting to stock first, and if that is unsuccessful, then I'll try to reseat the display connector.
My led light doesng work for my galaxy s8 plus i ha e tried checking the settings, it just doesnt work. The charging led light also doesnt work. It just doesnt work. Have tried to dial *#0*# to check the led setting even in that it doesn't work? Anyone else havjng the same issue?
Just checked mine for you and it works for me in the led tester. Cycles through the 3cilours. You might want to go into safe mode and try that tester again. If it still isn't working... You'll need to cheng your phone
How ti get into safe mode.
And i have been reading various threads that after the latest nougat update it stopped working for people, so im wonderkng if its a software issue or haddware issue
I am having the same problem, it worked when I first got it, then it updated and it stopped working, I have tried everything, even a factory reset, and nothing happens. Also tried the Samsung service menu and nothing.
It's really upsetting the phone is 3 days Old!
I had a note 7 and now This!
Hope the battery doesn't blow up!
Before returning the phone I would do factory reset, also sometimes cycling the setting could get it unstock. Mine worked fine before and after update.
All good and working for me.
There is a similar discussion in a German forum. Seems several people are affected. I cannot post links here, but you'll find it on a known online community site called "android-hilfe" in the Galaxy S8 section.
It happend to my S8+, too. After two days, the LED stopped working, and nothing helped (factory reset etc.). Had to return the phone.
Do you use an app like "Light Manager", "LED Blinker", "LightFlow" or similar?
Users in german forum report, that these apps might cause damage of LED of S8/S8+ :
http://www.android-hilfe.de/thema/benachrichtigungs-led-leuchtet-nicht-mehr.828003/ (german language)
I did not use such an App.
Tatsch said:
Do you use an app like "Light Manager", "LED Blinker", "LightFlow" or similar?
Users in german forum report, that these apps might cause damage of LED of S8/S8+ :
http://www.android-hilfe.de/thema/benachrichtigungs-led-leuchtet-nicht-mehr.828003/ (german language)
Click to expand...
Click to collapse
Forgot that Lightflow was one of the apps Google auto downloaded for me - this was causing my LED to not work right.
Thank you
Hello all.
I am on my second S8+ plus and the LED is now dead again. I use light manager pro and I have the led settings set to start at red when battery is low and then slowly ramp up to green via yellow for 50% to 75% until it hits 76% charge then goes green.
I suspected the app to kill the led in the phone, never happened on my S3, S4, S5 or S6 edge. No root on S8 so it has to use the kernels default brightness settings so it should not be able to kill the LED.....
I suspect that it is simply not built to do more than red, green and blue, when you mix in pinks, orange, purple and more, the thing just dies due to too much power to run all LEDs to create other colors. I think Samsung have gone cheep on us with the notification LED as they believe AOD is the way forward, which out be fine if they could implement a dot on the screen when the display is off, like the notification LED, only AMOLED.
Really upset as I love the rest of the phone but I really use the notification LED a lot and lean on it a great deal.
Same problem here. Stopped working last night after 12 days. I do have Lightflow but it's always worked fine on my S4 and S6.
Returning and replacing today, hopefully.
My S8+'s LED died without using such an app.
G-Tech said:
My S8+'s LED died without using such an app.
Click to expand...
Click to collapse
Are you using AQDG firmware? There is a user reported that AQDD firmware works fine so far, suspected AQDG firmware update could have spoilt it.
https://forums.overclockers.co.uk/threads/galaxy-s8-led-issue.18778041/page-2
I am still waiting for the replacement phone (don't know the sw version). Mine did not get an sw update though so I cannot blame it for the issue (referring to the thread you linked).
Kevin_R said:
Same problem here. Stopped working last night after 12 days. I do have Lightflow but it's always worked fine on my S4 and S6.
Returning and replacing today, hopefully.
Click to expand...
Click to collapse
What baseband firmware version are you using on your device with broken LED?
---------- Post added at 05:32 AM ---------- Previous post was at 05:30 AM ----------
SyLvEsTeR20007 said:
Hello all.
I am on my second S8+ plus and the LED is now dead again. I use light manager pro and I have the led settings set to start at red when battery is low and then slowly ramp up to green via yellow for 50% to 75% until it hits 76% charge then goes green.
I suspected the app to kill the led in the phone, never happened on my S3, S4, S5 or S6 edge. No root on S8 so it has to use the kernels default brightness settings so it should not be able to kill the LED.....
I suspect that it is simply not built to do more than red, green and blue, when you mix in pinks, orange, purple and more, the thing just dies due to too much power to run all LEDs to create other colors. I think Samsung have gone cheep on us with the notification LED as they believe AOD is the way forward, which out be fine if they could implement a dot on the screen when the display is off, like the notification LED, only AMOLED.
Really upset as I love the rest of the phone but I really use the notification LED a lot and lean on it a great deal.
Click to expand...
Click to collapse
What baseband firmware version are you using on your device with broken LED?
mckoo said:
What baseband firmware version are you using on your device with broken LED?
---------- Post added at 05:32 AM ---------- Previous post was at 05:30 AM ----------
What baseband firmware version are you using on your device with broken LED?
Click to expand...
Click to collapse
Hello Mckoo, Jevon Greatorex here. I have been emailing with you regarding this issue.
AQDG is current firmware and the first phone died before AQDG. I remember hoping that the update might fix it.
So you should be considering that the firmware before AQDG could be the cooperate if you think it's related at all.
Jevon
My Led works perfectly and I have all different colours set for my contacts.
I also have edge notifications working perfectly, no red tint, no home button issues, incredible battery life, gmail notifications, no scratches and no issues with bloat.
Did I miss anything? :laugh:
Light Emitting Diode Light?
Sent from my SM-G950F using Tapatalk
choccy31 said:
My Led works perfectly and I have all different colours set for my contacts.
I also have edge notifications working perfectly, no red tint, no home button issues, incredible battery life, gmail notifications, no scratches and no issues with bloat.
Did I miss anything? :laugh:
Click to expand...
Click to collapse
This thread is about a problem. Consider not filling it with bloat and instead give us your base-band number.
that static screen(snow) you get when your tv isnt on a channel, i get that flashed right before the ambient display shows. anyone one else have this issue ?
Probably have screen on/off setting on CRT in settings. Are you on a custom rom? I don't see the setting in OOS anywhere.
got same issue here
I've noticed the same thing randomly happening. Doesn't happen all the time so can't see what might be causing it. I'm using full stock and there is no setting I can see.
vuway said:
that static screen(snow) you get when your tv isnt on a channel, i get that flashed right before the ambient display shows. anyone one else have this issue ?
Click to expand...
Click to collapse
I get that since when I got the device last year but after update it show very less like maybe once a month. No way to fix it tho
Yup, Same here! Happens randomly on different custom kernels.
It's a feature, not a bug
I've noticed that it seems to happen when the screen lights up for a notification too.
I would only get this when on Smurf Kernel. When I switch to EX or RZ, the issue goes away.
thank you everyone for your input, its nice to know its a common issue. maybe ill try ex kernal. im currently on smurf. or i might just leave ambient turned off. doesn't seem to have much advantage over the regular lock screen anyway
I got this problem too a few weeks ago after trying out some kernels. I fixed it by dirty flashing OOS into both slots. It's a small but very annoying issue.
All kernels that use Dynamic FSync have this issue. You must turn OFF Dynamic FSYNC in EX Kernel Manager