Hello people, I've noticed a very annoying problem, that happens with every notable custom ROM based on Android 7. Tried LOS (CM based), Slim (AOSP based), and RR as well. Sometimes it takes a lot of time to unlock the screen when putting the finger on the home button on all of these roms, it usually should 1,5 secs but it can take up to 4. This never happens when the phone is locked from less than 5-6 seconds, or when it is charging. Does this happen to any of you? Please share your experience below.
Nope.
Fast as usual.
I'm on RR 5.8.1 btw.
Do any of you with this problem have a Sharp panel?
Bytecode said:
Hello people, I've noticed a very annoying problem, that happens with every notable custom ROM based on Android 7. Tried LOS (CM based), Slim (AOSP based), and RR as well. Sometimes it takes a lot of time to unlock the screen when putting the finger on the home button on all of these roms, it usually should 1,5 secs but it can take up to 4. This never happens when the phone is locked from less than 5-6 seconds, or when it is charging. Does this happen to any of you? Please share your experience below.
Click to expand...
Click to collapse
The same as you,l think it's a bug of lineage OS.
Xiaoyu Jiao said:
The same as you,l think it's a bug of lineage OS.
Click to expand...
Click to collapse
Ooooh nice to see I'm not alone on this. Can you put the phone in airplane mode, close all apps, let it sleep for ten seconds, and try to wake it up touching the fingerprint, and see how much it takes?
EDIT: also, when did you buy your phone? And when was it manufactured?
While rare, I have this same problem using CM. There is a small delay to wake up with the fingerprint, it takes 1 or 2 seconds.
It's a brand new device, received this month from Banggood.
Bytecode said:
Ooooh nice to see I'm not alone on this. Can you put the phone in airplane mode, close all apps, let it sleep for ten seconds, and try to wake it up touching the fingerprint, and see how much it takes?
EDIT: also, when did you buy your phone? And when was it manufactured?
Click to expand...
Click to collapse
I did as you said,and it took about 1-2seconds for my phone to wake up.I bought it in July last year,and it was manufactured in April last year.Excuse me for my bad English since I'm a Chinese.
---------- Post added at 03:59 PM ---------- Previous post was at 03:56 PM ----------
Bytecode said:
Ooooh nice to see I'm not alone on this. Can you put the phone in airplane mode, close all apps, let it sleep for ten seconds, and try to wake it up touching the fingerprint, and see how much it takes?
EDIT: also, when did you buy your phone? And when was it manufactured?
Click to expand...
Click to collapse
I'm using the latest official lineage OS.
Xiaoyu Jiao said:
I did as you said,and it took about 1-2seconds for my phone to wake up.I bought it in July last year,and it was manufactured in April last year.Excuse me for my bad English since I'm a Chinese.
---------- Post added at 03:59 PM ---------- Previous post was at 03:56 PM ----------
I'm using the latest official lineage OS.
Click to expand...
Click to collapse
All right. So 2016.04? And also, could you check if you have a Sharp display on your phone? (no worries about your english!)
BananaPrime said:
While rare, I have this same problem using CM. There is a small delay to wake up with the fingerprint, it takes 1 or 2 seconds.
It's a brand new device, received this month from Banggood.
Click to expand...
Click to collapse
I understand. Can you try to put it into airplane mode, close all apps, lock the screen and let it sleep for a while, and see how long does it take to unlock? Also, can you check manifacture data and panel manufacturer (Sharp, JDI, LGD)?
Bytecode said:
All right. So 2016.04? And also, could you check if you have a Sharp display on your phone? (no worries about your english!)
I understand. Can you try to put it into airplane mode, close all apps, lock the screen and let it sleep for a while, and see how long does it take to unlock? Also, can you check manifacture data and panel manufacturer (Sharp, JDI, LGD)?
Click to expand...
Click to collapse
The packing box has been thrown away by me,but I vaguely remember the number 201604 is written on the box.Display is jdi not sharp,In China, it's just as hard as hitting the jackpot to get a sharp display; almost all are jdi.What about your country.
Xiaoyu Jiao said:
The packing box has been thrown away by me,but I vaguely remember the number 201604 is written on the box.Display is jdi not sharp,In China, it's just as hard as hitting the jackpot to get a sharp display; almost all are jdi.What about your country.
Click to expand...
Click to collapse
Sharp :/ and I bought it from a Hong Kong Aliexpress store..
I will test in airplane later, but how do I check my screen manufacturer?
Here's the last line:
mdss_mdp.panel=1:dsi:0:qcom,mdss_dsi_lgd_fhd_td4322_cmd:1:none:cfg:single_dsi
In general I don't this delay is a big issue, at least for me it only happened a delay above 2 seconds once.
lte+
Hello . I have the mi5 32 GB version. Operators in my country in two band 1800, lte 2600 provides the lte Internet. But I do not have 4g+. Other phones have 4g+ .Carrier Aggregation not work. i am on miui global stable 8.1 . in cm14.1 Carrier Aggregation is work ?
Bytecode said:
Sharp :/ and I bought it from a Hong Kong Aliexpress store..
Click to expand...
Click to collapse
......
So, It seems my display is LGD (LG Displays).
I cleared all apps and put my phone in Airplane mode and somehow it got WORSE, I have to put my finger more than once and it takes 2-3 seconds until the screen turn on.
If I disable airplane mode it goes back to normal.
BananaPrime said:
So, It seems my display is LGD (LG Displays).
I cleared all apps and put my phone in Airplane mode and somehow it got WORSE, I have to put my finger more than once and it takes 2-3 seconds until the screen turn on.
If I disable airplane mode it goes back to normal.
Click to expand...
Click to collapse
Yep, have this problem too!
Same for me
I didn't get this with stock LOS, installing any sort of custom kernel has the issue.
Is there a way I can find out what display I have without the phone box?
No problem for me, on 32gb version with LOS, stock or custom kernel.
Happens on los based ROMs for me not on aosp.
Related
Please mention all the common issues found in this device (both Hardware and Software level)
So far I have gathered one issue mainly
- The USB/SD Card flap gets loosen or does not properly close.
Some units may have excessive gap between the glass and the frame, either top or bottom.
in_core said:
- The USB/SD Card flap gets loosen or does not properly close.
Click to expand...
Click to collapse
Because of this mine is on the way back to Vodafone [emoji22]
Mine has a dead pixel. But these arent common issues unless a lot of people complain about them tbh.
Servaas said:
Mine has a dead pixel. But these arent common issues unless a lot of people complain about them tbh.
Click to expand...
Click to collapse
Was the dead pixel noticeable from the very first day?
Ive got two things where im not sure if that are real Problems or just a question of settings.
First one is that voice from the other part is not really loud, even on the highest setting, during a phone call.
The other one is the battery time. I dont get such high results like 2 days from the tests on different websites. I only got one day with moderate usage.
in_core said:
Was the dead pixel noticeable from the very first day?
Click to expand...
Click to collapse
No second day, first day I probably didnt notice. Nor do I now to be honest... was hesitating about sending it back but ehh... its so much hassle and like I said I can hardly tell its dead.
I have returned mine to o2 within the initial cooling off period, there's too many problems to risk sorry. I loved the spec and design too
Did you experience any problems or did you just bottle it? I've had mine for a week or so with no problems at all.
qbert456 said:
I have returned mine to o2 within the initial cooling off period, there's too many problems to risk sorry. I loved the spec and design too
Click to expand...
Click to collapse
I'd assume that more than 90% of units have no major issues. The misleading thing is that, in communities like these, people with faulty units are far more represented than people who are satisfied.
Honestly, I didn't really use it,it kept all the plastic films on etc. It's not that I'm not going to get one if it proves reliable more that I'm quite unlucky with phones generally!
I will keep looking in here tho and will likely getting a red/orange one again in a few weeks....
qbert456 said:
Honestly, I didn't really use it,it kept all the plastic films on etc. It's not that I'm not going to get one if it proves reliable more that I'm quite unlucky with phones generally!
I will keep looking in here tho and will likely getting a red/orange one again in a few weeks....
Click to expand...
Click to collapse
I suggest you just get a silicone cover or something, to protect it. A wrist lanyard also helps a lot. And to increase your chance of getting a Z3C from a more recent production batch, you can keep an eye on a web shop and order a Z3C after the stock runs out and is restocked.
Camera Button
Is the Z3c hardware camera button designed to require a fairly lengthy press to activate? I'm guessing that maybe it's a design built in to perhaps avoid accidental pocket presses, but I'm not sure.
Just a quick tap does not activate it on mine, but it works fine with a slightly longer press.
Poojo said:
Is the Z3c hardware camera button designed to require a fairly lengthy press to activate? I'm guessing that maybe it's a design built in to perhaps avoid accidental pocket presses, but I'm not sure.
Just a quick tap does not activate it on mine, but it works fine with a slightly longer press.
Click to expand...
Click to collapse
Mine too, also there seems to be a 2-step press for it, as on a regular camera (half hold down to focus). Half pressing doesn't start it.
Have had to mess with settings to turn off the quick launch which was set to launch and capture as I have so many pics of either a finger or blackness!
---------- Post added at 05:17 PM ---------- Previous post was at 05:12 PM ----------
impact1991 said:
Ive got two things where im not sure if that are real Problems or just a question of settings.
First one is that voice from the other part is not really loud, even on the highest setting, during a phone call.
The other one is the battery time. I dont get such high results like 2 days from the tests on different websites. I only got one day with moderate usage.
Click to expand...
Click to collapse
On mine the sound is pretty loud through the mic, so much so that I thought the loudspeaker was on! Conversely though the actual loudspeaker doesn't seem that loud! Go figure!
For the battery I think you would only get 2 days with the Stamina settings active. I manage to get down to about 25% on a full day of regular usage (in office etc). The Stamina / Ultra stamina modes seem to just disable pretty much everything on the phone. OK if you need to keep it powered on but no good for regular usage. I've ended up turning stamina mode on and then re-enabling Wifi, seems to improve life quite a bit for the times I have been hammering it!
degraaff said:
I'd assume that more than 90% of units have no major issues. The misleading thing is that, in communities like these, people with faulty units are far more represented than people who are satisfied.
Click to expand...
Click to collapse
Always been the case since the Treo days, lol. People will look and see all these problems, but they are random people, that really only for the most part show up here to resolve "issues". While it is a great thing for folks looking for corrections, it does appear bad on the surface if you don't really understand the dynamic at play on boards like these.
---------- Post added at 12:38 PM ---------- Previous post was at 12:37 PM ----------
Poojo said:
Is the Z3c hardware camera button designed to require a fairly lengthy press to activate? I'm guessing that maybe it's a design built in to perhaps avoid accidental pocket presses, but I'm not sure.
Just a quick tap does not activate it on mine, but it works fine with a slightly longer press.
Click to expand...
Click to collapse
Yes. Your button is behaving normally.
I'm currently on my third unit within 7 days. My Internet connection seems to hang about 2 or 3 times a day, and until I try to use the Internet Is don't realise. After then restarting my phone, I get a flood of whatsapps, emails and fb alerts. It's getting really old really quickly,to the point where I just want rid of the phone.
jbhkhc said:
I'm currently on my third unit within 7 days. My Internet connection seems to hang about 2 or 3 times a day, and until I try to use the Internet Is don't realise. After then restarting my phone, I get a flood of whatsapps, emails and fb alerts. It's getting really old really quickly,to the point where I just want rid of the phone.
Click to expand...
Click to collapse
I've only had that once, last Fri however it is a bit weird, here's how mine manifested itself:
- Work most of the day in an office, good wifi connection. Don't use the phone much but see that it is working OK, getting emails, fb updates etc. Can browse the internet via Chrome
- Left the office and try to do a search. Using Google search from the home screen the results showed up very quickly but then when I tried to open any of those links in chrome it would just say no network or something similar. Tried shutting down chrome, clearing cache and data but made no difference.
The weird thing here is that the 4g / mobile data connection WAS working, but the issue was with Chrome.
I'm still stock, not likely to change that but since Chrome is now an intrinsic part of the Xperia build how do you uninstall / reinstall? Or do I end up installing another browser?
Chrome has done this to me on Z3 Compact and a few times on my previous Xperia ZR. Just close the browser from the multi-app right button by flicking it to the side, then try again. If it gets too tedious, install another browser.
Hi, any one have the same issue as me?
My Z3C black out after 2nd week of use then could not power on. Brought to service center and the person claim that it is software issue.. Took back the phone after they reformatted, then after 12hrs use, same problem again.. Then they change 1-1 for me.. but after another week of use, same issue on the 2nd phone!
who have the same issue as me? what should i do next? i cant be bringing the phone in to service center every week..
hello,
I think it's the same pb for me... "Z3 Compact" bought the 28.09.2014. The phone is turned off itself in the middle of the day in my pocket. The battery level was approx. 75% => Black screen, not even light on the charger...:S The Sony support told me to send them with charger and usb cable. I am waiting for news... approx. 10 days...
Installed Los 16 on the s5 last night. So far it works flawlessly. Looks like this little phone has another year of life left in it!!!!!!
mojorisin7178 said:
Installed Los 16 on the s5 last night. So far it works flawlessly. Looks like this little phone has another year of life left in it!!!!!!
Click to expand...
Click to collapse
Hi, can I ask what version of TWRP did you use? Thank you.
I'm just using the LOS 16 and works excellent.
mojorisin7178 said:
Installed Los 16 on the s5 last night.........
Click to expand...
Click to collapse
zrockcool said:
Hi, can I ask...........
Click to expand...
Click to collapse
twilightorange said:
I'm just using the LOS 16..........
Click to expand...
Click to collapse
Just an FYI...
The following thread has been used regarding support, guidance and feedback for the Official LineageOS 16.0 klte by Haggertk (the Official Lineage Team Maintainer).
https://forum.xda-developers.com/showthread.php?t=3850840
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.
zrockcool said:
Hi, can I ask what version of TWRP did you use? Thank you.
Click to expand...
Click to collapse
Hi,
It's all in the sgs5 klte subfourm. I am on the latest version.
twilightorange said:
I'm just using the LOS 16 and works excellent.
Click to expand...
Click to collapse
Excellent is about right. It's so much better than Oreo LOS for GS5, which had a lot of bluetooth issues. Performance is amazing for an old 32bit CPU.
edit: I also have LOS16 running on Nexus 7 2013 and it surprised how well it runs for such an old device.
What about the battery life compared to LOS 15.1?
Display "stays black" issue on SM-900F
Hi.
Upgraded my wife's S5 to LOS 16 (from LOS 15.1?) lately and she's still happily using it (thx to all supporters).
I recently got another used SM-900F and though it's battery is a bit drawn out it seemed to have working smoothly while still on Samsung stock ROM.
However since I flashed it to LOS 16 it has some strange behaviour with it's backlight / display.
After some time of inactivity the display goes off, but I can't the display lit again. When pressing the home or power button the LEDs of the "soft" buttons flash, but the display stays black.
But the device is working as I can press the power button and bring "up" the power menu, but as I can't see anything I have to press the "shutdown" option blindly, and yes, the device powers off then.
If I the take off the battery for a while everything seems to be ok again.
But if the device is in that "black" mode even powering it up in "download mode" the display stays dark. So I assume this can't be an issue of LOS!?
Re: Display "stays black" issue on SM-900F
odoll said:
So I assume this can't be an issue of LOS!?
Click to expand...
Click to collapse
It isn't. To be sure I reflashed the latest German Vodafone Samsung Stock 6.0.1 ROM back to the S5. Though everything worked smoothly in the beginning the display started *****ing after a while again. (it's sometimes lightly flashing green for a glimpse of a second)
As I got the impression it maybe related to a thermal problem I left it on a heating's radiator for a while, and yes, display got lit every time I tried. Let it get "cold" again and it starts *****ing ...
odoll said:
I can't the display lit again
Click to expand...
Click to collapse
this is a common failure of (this generation of) samsung's OLEDs
if you use low brightness or are in cold weather a lot, the display will start flickering until brightness is raised
the screen will also fail to turn on sometimes, just turn it off then on again, repeat as needed, sometimes you need to warm up the phone
(edit: i've seen the galaxy logo show up then fade to black on a fresh boot, i've also seen someone on stock have the problem, so it's definitely not software)
recently i read about mouse button failing to click or clicking multiple times, one remedy was cleaning off possible corrosion with isopropyl, so i wonder if this OLED issue is similar (it might be if cold temperature increases the problem, electricity doesnt flow as well, etc)
Hi,
excuse me
sometimes I play midi USB keyboards.
Anyone has tested USB OTG?
Does work well ?
Thks
Who else are facing the same problem ?
1)Initially, when I unlock phone by pressing power button the display was changed to dim colour(mostly yellowish) and with horizontal lines displayed when the brightness is below 50%. After tried with multiple times pressing on power button the display came back to normal.
2) Next stage, it's not solved with power button. I have to keep my phone aside for some time to get back to normal display. It's been 15 to 20 min then.
3) Now, I would get normal display only in morning. Else, I need to keep my phone idle without touching for at least 4 to 5 hours. I've also changed screen power off time from 30 Sec to 10 Minutes. So that my screen wont turn off and I can keep the normal display. If I forgot to use or kept aside more than 10 min then my screen would go off and display would gone again and irritation starts with that discoloration problem..
4) If display changes to yellowish to reduce the horizontal lines problem I need to increase the brightness to 80 or 85% but this causing my phone with another problem "heating issue"
Samsung haven't responded on this issue yet, how could we bring up the issue and get the proper resolution from Samsung.
This happened after last March update installation?
What note 9 do you have?
Probably not a hardware fault if it happened after recent software update.
A number of note9 affected although samsung seems to disagree at the moment.
Hello,
I also have a problem with the display after waking up with the POWER button. There are tinted colors distorted and some stripes like dim lines and slow refreshing. Everything started after updating to Android 10. In fact, when the display lights up incorrectly, it starts to heat up from the bottom. Putting the smartphone aside for a moment or cooling down causes the display to work correctly.
Workaround? I turned on Active Display and first knock to activate it, then the display lights up correctly and then I unlock the screen and use normally. It is known that battery consumption increases. Of course mine is Exynos.
hi guys,, i remember a similar experience sometime back.. try this. if u have turn on the proximity sensor i mean the advance feature where the phone screen doesn't turn on while in pocket , switch it off and restart the phone and see if the problem still exist.
i am having same issue
is anybody on xda come to rescue our issue?? friends need urgent help out ., if the solution is to reinstall the firmware kindly tell how to ?? while phone is just giving odd lines and not responding to touch even ??
ahmadtanveer7007 said:
is anybody on xda come to rescue our issue?? friends need urgent help out ., if the solution is to reinstall the firmware kindly tell how to ?? while phone is just giving odd lines and not responding to touch even ??
Click to expand...
Click to collapse
whats the firmware version u are having now and phone model?
Try wiping the cache partition in Recovery Mode. If that doesn't work then back up your device and manually reinstall the OS back onto your device.
Im having the exact problem. I flash LineageOS and it worked by max brightness then back to auto. I installed brightness widget to max brightness and back to auto everytime I turn on screen.
This issue is popular after March update. I tried everythings you mentioned above, reset, flash new firmware, even April update, wipe cached, flash cooked rom, heat screen, turn off features, disable gpu overlay, etc... Samsung Vietnam guaranteed can fix with new screen but I'm out of warranty.
I dont have any issues us unlocked snapdragon xaa model on latest android 10 version.
Can we confirmed that a screen replacement fixes the display problem or is it still a software issue
Signup said:
Who else are facing the same problem ?
1)Initially, when I unlock phone by pressing power button the display was changed to dim colour(mostly yellowish) and with horizontal lines displayed when the brightness is below 50%. After tried with multiple times pressing on power button the display came back to normal.
2) Next stage, it's not solved with power button. I have to keep my phone aside for some time to get back to normal display. It's been 15 to 20 min then.
3) Now, I would get normal display only in morning. Else, I need to keep my phone idle without touching for at least 4 to 5 hours. I've also changed screen power off time from 30 Sec to 10 Minutes. So that my screen wont turn off and I can keep the normal display. If I forgot to use or kept aside more than 10 min then my screen would go off and display would gone again and irritation starts with that discoloration problem..
4) If display changes to yellowish to reduce the horizontal lines problem I need to increase the brightness to 80 or 85% but this causing my phone with another problem "heating issue"
Samsung haven't responded on this issue yet, how could we bring up the issue and get the proper resolution from Samsung.
Click to expand...
Click to collapse
I have the same problem at the beginning it was when the phone was warm now the screen is yellow and when I lower the brightness I have lines coming out
jonaki said:
I have the same problem at the beginning it was when the phone was warm now the screen is yellow and when I lower the brightness I have lines coming out
Click to expand...
Click to collapse
Hi Bro, the same problem now facing by many users. We have created a Telegram group do discuss about the issue. Plz join there.
https://t.me/samsungDisplayProblem
luisfer21069 said:
Can we confirmed that a screen replacement fixes the display problem or is it still a software issue
Click to expand...
Click to collapse
No one knows what is the exact cause here, its noticed in many devices right after this March update but few are noticed months before. But, now the problem came to many users at same time. So its been brought up by many tech blogs, websites.
pheonixxdark said:
hi guys,, i remember a similar experience sometime back.. try this. if u have turn on the proximity sensor i mean the advance feature where the phone screen doesn't turn on while in pocket , switch it off and restart the phone and see if the problem still exist.
Click to expand...
Click to collapse
Thanks for tour suggestion, however I couldn't find the the exact option you mentioned in advanced features plz look into below once and help me to solve this.
joedellosso69 said:
This happened after last March update installation?
What note 9 do you have?
Click to expand...
Click to collapse
Hi, Yes like many other saying I too have this problem after March update only. I'm using Exynos one and also please have a look at below screenshot. Please let me know if you need anything further to know about the issue also attaching the links about the issue.
https://r2.community.samsung.com/t5...tion-amp-Overheating-Posting-4th/td-p/4049910
https://www.sammobile.com/news/galaxy-note-9-march-2020-security-update-broken-screen/
https://www.androidauthority.com/samsung-galaxy-note-9-march-update-broken-displays-1103766/
https://www.androidheadlines.com/20...in-of-broken-display-after-march-update.html/
pheonixxdark said:
whats the firmware version u are having now and phone model?
Click to expand...
Click to collapse
Please have a look into below screenshot. Plz let me know if you need any other info.
Rosli59564 said:
Probably not a hardware fault if it happened after recent software update.
A number of note9 affected although samsung seems to disagree at the moment.
Click to expand...
Click to collapse
Yes Bro but, We haven't found any fix for this till now.
Signup said:
Hi, Yes like many other saying I too have this problem after March update only. I'm using Exynos one and also please have a look at below screenshot. Please let me know if you need anything further to know about the issue also attaching the links about the issue.
https://r2.community.samsung.com/t5...tion-amp-Overheating-Posting-4th/td-p/4049910
https://www.sammobile.com/news/galaxy-note-9-march-2020-security-update-broken-screen/
https://www.androidauthority.com/samsung-galaxy-note-9-march-update-broken-displays-1103766/
https://www.androidheadlines.com/20...in-of-broken-display-after-march-update.html/
Click to expand...
Click to collapse
I'm having the exynos version too but with ITV (Italy) firmware ...never had this problem and now I'm on April's version after March's version.
This looks a little bit like what happened to the S5 years ago when after 1 and a half/ 2 and a half year's the screan began flickering, having green spots or lines, randomly didn't go on with low luminance settings since it completely died....a lot of people said on forum's that it was the screen and a replacement solves, but when it happened to me years ago the Samsung assistance center told me that it was another component (never told me what it was) causing the issue and once they changed it , they solved the problem.
So, after my experience with the S5, don't know what to think now for what is happening to some guys even if I think that this issue might depend with something happening after marchs update because for the too many people having it after the update, coincidences are not credible.
joedellosso69 said:
I'm having the exynos version too but with ITV (Italy) firmware ...never had this problem and now I'm on April's version after March's version.
This looks a little bit like what happened to the S5 years ago when after 1 and a half/ 2 and a half year's the screan began flickering, having green spots or lines, randomly didn't go on with low luminance settings since it completely died....a lot of people said on forum's that it was the screen and a replacement solves, but when it happened to me years ago the Samsung assistance center told me that it was another component (never told me what it was) causing the issue and once they changed it , they solved the problem.
So, after my experience with the S5, don't know what to think now for what is happening to some guys even if I think that this issue might depend with something happening after marchs update because for the too many people having it after the update, coincidences are not credible.
Click to expand...
Click to collapse
Yes, many people were facing this problem and how many times we have contacted the Samsung they are behaving like they just hearing the issue for the first time. Just created and posted the link in Members app and 67 members joined so far. Everyone having the display problem out of nowhere. All of them on out of warranty except one or two. Still members app floating with the display problem messages.
Display issue got noticed in S20 too but they immediately released the security patch and solved it. Don't know why they were silent on Note 9.
https://www.androidauthority.com/samsung-galaxy-s20-ultra-green-tint-1107738/
Is anyone else having an issue with the always on display? Not a big deal but occasionally the AOD goes off and the tap to wake function doesn't work. Unlocking/locking the phone fixes it but it reoccurs again randomly through the day.
andrewd71 said:
Is anyone else having an issue with the always on display? Not a big deal but occasionally the AOD goes off and the tap to wake function doesn't work. Unlocking/locking the phone fixes it but it reoccurs again randomly through the day.
Click to expand...
Click to collapse
I was having the same issue when I had the edge notification app installed that makes the screen light up around the camera when you get a notification.
Uninstalled and no issues since
Tap to wake not working for me
Not sure if this is connected but in addition to the always on display/tap to wake issue when I'm in a phone call the screen will stay off even when I move the phone from my ear to hang up, see the keypad etc. Again I have to use the power button to wake the screen. A problem with the proximity sensor perhaps?
andrewd71 said:
Not sure if this is connected but in addition to the always on display/tap to wake issue when I'm in a phone call the screen will stay off even when I move the phone from my ear to hang up, see the keypad etc. Again I have to use the power button to wake the screen. A problem with the proximity sensor perhaps?
Click to expand...
Click to collapse
Do you have any notification or edge lighting apps installed?
Mdizzle1 said:
Do you have any notification or edge lighting apps installed?
Click to expand...
Click to collapse
No, I've not installed any apps like that.
I am having both the issue with always on display and the screen staying off during a call even when it's not up to my face. I don't have any edge display app installed. They happened right out of the box. Glad it's not just me.
czm said:
I am having both the issue with always on display and the screen staying off during a call even when it's not up to my face. I don't have any edge display app installed. They happened right out of the box. Glad it's not just me.
Click to expand...
Click to collapse
This is an odd one - are you using a case? I just had a case through the post this morning and now using the phone with the case the issues have stopped! I'll keep checking through the day but as of now all is good.
andrewd71 said:
This is an odd one - are you using a case? I just had a case through the post this morning and now using the phone with the case the issues have stopped! I'll keep checking through the day but as of now all is good.
Click to expand...
Click to collapse
Not using a case. It's sporadic. Tap to wake works fine for a while and then stops. The issue during calls is constant. Not major issues just niggles.
Not noticed any bugs with ambient display, but it has used 20 percent battery in 21hrs.
Seems a bit high to me, have just turned it off, not worth a 5th of my battery.
czm said:
I am having both the issue with always on display and the screen staying off during a call even when it's not up to my face. I don't have any edge display app installed. They happened right out of the box. Glad it's not just me.
Click to expand...
Click to collapse
Yeah I'm having both issues happen RANDOMLY as well. I'm HOPING Google will put out a fix for these two issues very soon.
Tried working with Google's Tech Support Team via chat earlier on the AOD issue. Tried a few things like clearing the cache of the launcher & restarting in Safe Mode then back to Normal Mode, and it seems to be doing it less but then it just did it again for a short time like an hour ago.
Using a case, no edge stuff, and also using Nova Launcher (though it happened in Pixel Launcher as well).
If anyone finds a fix for this, I would appreciate it too!
RockStar2005 said:
Yeah I'm having both issues happen RANDOMLY as well. I'm HOPING Google will put out a fix for these two issues very soon.
Tried working with Google's Tech Support Team via chat earlier on the AOD issue. Tried a few things like clearing the cache of the launcher & restarting in Safe Mode then back to Normal Mode, and it seems to be doing it less but then it just did it again for a short time like an hour ago.
Using a case, no edge stuff, and also using Nova Launcher (though it happened in Pixel Launcher as well).
If anyone finds a fix for this, I would appreciate it too!
Click to expand...
Click to collapse
Mine is fine for a while them randomly the tap-to-wake won't respond. I had also hoped that the OTA would have addressed, but maybe it is affecting far fewer users than other bugs.
czm said:
Mine is fine for a while them randomly the tap-to-wake won't respond. I had also hoped that the OTA would have addressed, but maybe it is affecting far fewer users than other bugs.
Click to expand...
Click to collapse
Yeah. Seems like more and more people are noticing and like me reporting these various issues to Google. So hopefully the next batch will include fixes for all this stuff.
I have same two problem with AOD, touch to wake up and screen off/on when calling.
DOMIN_ said:
I have same two problem with AOD, touch to wake up and screen off/on when calling.
Click to expand...
Click to collapse
I recommend you guys report these issues to Google so to increase the odds of them coming up with an OTA sooner than later. You can call them or chat with them via this link (as I did). Just scroll down to the bottom and choose your contact preference.
RockStar2005 said:
I recommend you guys report these issues to Google so to increase the odds of them coming up with an OTA sooner than later. You can call them or chat with them via this link (as I did). Just scroll down to the bottom and choose your contact preference.
Click to expand...
Click to collapse
On the pixel support forum they also recommend you report it via settings>about phone>send feedback about device. I think this way it also easily picks up the log files.
I believe the answer to all of your questions lies in a faulty proximity sensor. I was driving myself nuts with all of these issues exactly, and no app was the culprit because I factory reset and still had the issue. I'm going to post a link to a Reddit thread that I found that confirmed my suspicions. on Wednesday of this week I went back to Verizon and traded the phone in and now I have received a phone that works 100% as expected.
Reddit thread.
Good luck all, hope this helps.
czm said:
On the pixel support forum they also recommend you report it via settings>about phone>send feedback about device. I think this way it also easily picks up the log files.
Click to expand...
Click to collapse
Yeah I got an e-mail from the support guy to do that as well after he'd ask that I send a bug report. Just did it regarding AOD not staying on all the time and also.............I noticed that Hold for Me doesn't ALWAYS come up when calling businesses. Two examples include T-Mobile Customer Service & a local major hospital in Chicago. In most cases though, it does. Just an FYI. Not sure if this is something that they will fix, but I think it should come up all the time, or AT LEAST when you're calling an established business of ANY kind.
---------- Post added at 05:30 PM ---------- Previous post was at 05:26 PM ----------
Morpherios said:
I believe the answer to all of your questions lies in a faulty proximity sensor. I was driving myself nuts with all of these issues exactly, and no app was the culprit because I factory reset and still had the issue. I'm going to post a link to a Reddit thread that I found that confirmed my suspicions. on Wednesday of this week I went back to Verizon and traded the phone in and now I have received a phone that works 100% as expected.
Reddit thread.
Good luck all, hope this helps.
Click to expand...
Click to collapse
Very interesting!
I REALLY don't want to send mine back because I've spent so much time setting it up already (and my sister's too lol). I did some changes in the settings so I'll just cross my fingers and hope it works right.
Is there a way to recalibrate the proximity sensor?
RockStar2005 said:
Yeah I got an e-mail from the support guy to do that as well after he'd ask that I send a bug report. Just did it regarding AOD not staying on all the time and also.............I noticed that Hold for Me doesn't ALWAYS come up when calling businesses. Two examples include T-Mobile Customer Service & a local major hospital in Chicago. In most cases though, it does. Just an FYI. Not sure if this is something that they will fix, but I think it should come up all the time, or AT LEAST when you're calling an established business of ANY kind.
---------- Post added at 05:30 PM ---------- Previous post was at 05:26 PM ----------
Very interesting!
I REALLY don't want to send mine back because I've spent so much time setting it up already (and my sister's too lol). I did some changes in the settings so I'll just cross my fingers and hope it works right.
Is there a way to recalibrate the proximity sensor?
Click to expand...
Click to collapse
I don't believe it's a calibration issue. The way mine worked (or didn't as the case may be) was sporadic and seemed to almost be as if the sensor or module was loose? Inside the housing. Quite literally, jostling it around would make it work sometimes. Furthermore, if you download the app in that reddit thread, the proximity sensor tester Link Here, you can sort of gauge yourself if it's actually occurring. With mine, sometimes it would work by swiping my hand over the sensor, the color would change. Other times, the color stayed the same, and as the video showed ,I could put pressure on where the sensor was and change the color. But if it wasn't working, jostling the phone around would sometimes make it work and the color would change.
Additionally in the advanced test in that app, it is supposed to tell you how far away from the sensor an object is. On my (nonworking) phone, that number for distance would be pegged at 0 regardless of how far away my hand was. However if I put pressure on the sensor, it would jump to like 5 cm.
See if your phone is doing these things. If so, I would recommend you get it replaced, as it likely will not work properly otherwise. Verizon deemed this a hardware issue when I swapped phones. Also note that I factory reset twice, and one of those times I imported literally nothing when setting it up. So it wasn't a settings or app issue. I do believe there's a rash of faulty proximity sensors going on here.
Morpherios said:
I don't believe it's a calibration issue. The way mine worked (or didn't as the case may be) was sporadic and seemed to almost be as if the sensor or module was loose? Inside the housing. Quite literally, jostling it around would make it work sometimes. Furthermore, if you download the app in that reddit thread, the proximity sensor tester Link Here, you can sort of gauge yourself if it's actually occurring. With mine, sometimes it would work by swiping my hand over the sensor, the color would change. Other times, the color stayed the same, and as the video showed ,I could put pressure on where the sensor was and change the color. But if it wasn't working, jostling the phone around would sometimes make it work and the color would change.
Additionally in the advanced test in that app, it is supposed to tell you how far away from the sensor an object is. On my (nonworking) phone, that number for distance would be pegged at 0 regardless of how far away my hand was. However if I put pressure on the sensor, it would jump to like 5 cm.
See if your phone is doing these things. If so, I would recommend you get it replaced, as it likely will not work properly otherwise. Verizon deemed this a hardware issue when I swapped phones. Also note that I factory reset twice, and one of those times I imported literally nothing when setting it up. So it wasn't a settings or app issue. I do believe there's a rash of faulty proximity sensors going on here.
Click to expand...
Click to collapse
Hey Morpherios,
Ok.............downloaded that app and tried it out several times. It passed some of the time, but then I'd try it again a few minutes later and it would fail on both tests. Ughh!!
You think even though it passed a few times I still need to replace it?
Hello guys
I come from a Pixel2XL where AOD stays always on the way it should be.
However, I don't know if it's a bug or the developers have forgot to keep 11Ultra AOD "always on" even when the option is selected in the settings for it to be, as it goes off just after few minutes!
Any idea what's the cause and is it happening for all devices (mine is GLOBAL variant)
So form of power management is active?
blackhawk said:
So form of power management is active?
Click to expand...
Click to collapse
No modification done...Vanilla 12.5.2 Global
Try to update to the latest 12.5.4.0 and see if the issue persists
amandeepparmar said:
No modification done...Vanilla 12.5.2 Global
Click to expand...
Click to collapse
I wouldn't sweat it as it sounds like a good feature. I use to always have AOD on but it got to be quit annoying for me after a year. It's set to tap on now.
100% availability means 100% no peace.
I got tired of playing the time game as well unless it's dinner
blackhawk said:
xNAPx said:
Try to update to the latest 12.5.4.0 and see if the issue persists
Click to expand...
Click to collapse
version not yet released
blackhawk said:
I wouldn't sweat it as it sounds like a good feature. I use to always have AOD on but it got to be quit annoying for me after a year. It's set to tap on now.
100% availability means 100% no peace.
I got tired of playing the time game as well unless it's dinner
Click to expand...
Click to collapse
the only thing that was lovable about always on display was to check if I had any notifications to respond to without tapping the device
Click to expand...
Click to collapse
Hope some developer gets an eye on this as it's a very useful feature where you don't even have an AlwaysON notification LED!
You can set the rear display to be on all the time if you want to
Change the 30 second timeout to 30 million seconds....
speedtripler said:
You can set the rear display to be on all the time if you want to
Change the 30 second timeout to 30 million seconds....
Click to expand...
Click to collapse
Yes... however, unlike the main screen the Xiaomi developers haven't set the pixels to move slightly for the rear screen and that might cause a screen burn!
amandeepparmar said:
Yes... however, unlike the main screen the Xiaomi developers haven't set the pixels to move slightly for the rear screen and that might cause a screen burn!
Click to expand...
Click to collapse
The time and date is always changing tho.... It should not be using the same pixels all the time
If I wanted to use the rear screen i wouldn't think twice but I don't like setting the phone face down anyway