Related
Maybe it is just me and my device, but since the MM update (the real one, not the beta) my notification LED doesn't work. I have tested it with text messages, emails, missed calls, charger plugged into my computer, charging plugged into a standard charger, and charging plugged into the fast charger... nada on any of them.
Anyone having this issue? If so how have you rectified it? It has been a minute since I first got this thing (got it at launch) and the MM update reset all my settings so maybe there is a setting to turn it back on I am missing?
Help out a brother if you can. Thanks.
OK, so does anyone have any suggestions for an app that might help by letting me manually setup the notification LED?
Is Do not disturb mode on?
Sent from my ASUS_Z00AD using XDA Premium HD app
madman604 said:
Is Do not disturb mode on?
Sent from my ASUS_Z00AD using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for the reply. It is not in DND as far as I can tell (not on).
If you haven't already, try a factory reset first
Trotter516 said:
Thanks for the reply. It is not in DND as far as I can tell (not on).
Click to expand...
Click to collapse
Have you found a fix for that? Facing the same issue and so far no luck.
godzin said:
Have you found a fix for that? Facing the same issue and so far no luck.
Click to expand...
Click to collapse
Actually yes. After I wiped my phone for my wife the notification now works.
Another issue that I recently found the solution to... if your ZF2's proximity sensor has gotten crazy sensitive since the update try cleaning it. Seriously. Especially if you have a tempered glass screen protector. I thought the piece of advice was bogus but I cracked out my lens cleaning spray and cloth and BOOM, the proximity sensor works correctly again.
Trotter516 said:
Actually yes. After I wiped my phone for my wife the notification now works.
Another issue that I recently found the solution to... if your ZF2's proximity sensor has gotten crazy sensitive since the update try cleaning it. Seriously. Especially if you have a tempered glass screen protector. I thought the piece of advice was bogus but I cracked out my lens cleaning spray and cloth and BOOM, the proximity sensor works correctly again.
Click to expand...
Click to collapse
Thanks! Got the led working again after a factory reset.
By the proximity sensor do you mean the little one next to the selfie camera or the GPS?
After a lot of fixed I've got the ZF2 working fine, except for the "smartlock - safe places" that thing can never work right.
godzin said:
Thanks! Got the led working again after a factory reset.
By the proximity sensor do you mean the little one next to the selfie camera or the GPS?
After a lot of fixed I've got the ZF2 working fine, except for the "smartlock - safe places" that thing can never work right.
Click to expand...
Click to collapse
Sorry, I just realized that you had replied.
Yes, the one beside the camera. Many have had an issue where the screen goes black after you start or answer a call, especially after the update. It seems the update made the proximity sensor much more sensitive. Since all decent screen protectors have a small cutout for the proximity sensor it will tend to accumulate dirt and oil from your skin. Wiping it down doesn't seem to get it clean enough for the sensor so you have to get a little more aggressive to clear the problem up. I went months enduring the problem and even set my phone so I could disconnect from calls using the power button and then ended up stumbling over the solution when setting up the phone for my wife when I upgraded to my Axon 7.
No led indicator
Hi i've been experiencing the same issue. After I update my zenfone 2 ZE551ML 4gb/64gb version, I have noticed that the led incator is not working and it is not found in the settings. Also, another issue I have encountered is that quick charging feature is not working sometimes but sometimes it works. I don't know how to fix. I'd be glad if someone could help with a step by step process. Thanks in advance!
I'm so fed up with these phones.
Is anyone else still having issues where when you go to make a call the screen goes black and you can't get out of it? No way to get into speakerphone mode, no way to hang up the call, no way to do a thing even after the call is finished.
This is with the June update which supposedly fix this issue.
If anyone has any insight I really appreciate it.
Never had the issue while on Oreo or while now on Android P DP3. Do you have a screen protector on it? Even pressing the power button doesn't wake the screen up while in call?
pilotgav said:
I'm so fed up with these phones.
Is anyone else still having issues where when you go to make a call the screen goes black and you can't get out of it? No way to get into speakerphone mode, no way to hang up the call, no way to do a thing even after the call is finished.
This is with the June update which supposedly fix this issue.
If anyone has any insight I really appreciate it.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
EeZeEpEe said:
Never had the issue while on Oreo or while now on Android P DP3. Do you have a screen protector on it? Even pressing the power button doesn't wake the screen up while in call?
Click to expand...
Click to collapse
No screen protector, and nope. Even power button won't get me back.
Very strange. It's replicable with every phone call? Any 3rd party dialer or display adjustment apps that you may be using that could affect it?
pilotgav said:
No screen protector, and nope. Even power button won't get me back.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
pilotgav said:
No screen protector, and nope. Even power button won't get me back.
Click to expand...
Click to collapse
I know you probably already did this but make sure your screen is clean around the sensor area, I've had a false reading before when the top of my screen was dirty.
Sent from my Pixel 2 XL using XDA Labs
I had the same issue a few months back. Did the online support and they RMA'd it.
It seems it was TrueCaller causing the issues. Thanks for all the advice guys!
pilotgav said:
I'm so fed up with these phones.
Is anyone else still having issues where when you go to make a call the screen goes black and you can't get out of it? No way to get into speakerphone mode, no way to hang up the call, no way to do a thing even after the call is finished.
This is with the June update which supposedly fix this issue.
If anyone has any insight I really appreciate it.
Click to expand...
Click to collapse
I had the problem with the proximity in dp3 it would not turn off while I was on the phone! After doing a FDR it worked great!
I had a feel you might've been using that or something similar. Glad you got it figured out.
pilotgav said:
It seems it was TrueCaller causing the issues. Thanks for all the advice guys!
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
I have gone the whole day testing this issue.
I hard reset my phone 3 times and tested this.
On every hard reset and fresh start the proximity sensor works perfectly well, as soon as I install true caller, the dead screen issue starts.
But I use truecaller without any problems on my other 3 non pixel phone without any issues. This problem is only with the pixel 2 and pixel 2 XL.
There is no resolution as of now. Does anyone know of anyways to get this resolved ?
hypermaster said:
I have gone the whole day testing this issue.
I hard reset my phone 3 times and tested this.
On every hard reset and fresh start the proximity sensor works perfectly well, as soon as I install true caller, the dead screen issue starts.
But I use truecaller without any problems on my other 3 non pixel phone without any issues. This problem is only with the pixel 2 and pixel 2 XL.
There is no resolution as of now. Does anyone know of anyways to get this resolved ?
Click to expand...
Click to collapse
I stopped using the pro version for issues I can't recall.
When I open the camera app, the screen is shaking hence can't take photos. Only happens on the rear camera photo and video. When taking selfies everything is ok. I already tried factory reset and it's still the same.
Can't attach the short video here, maybe someone can help me so I can show you guys.
Thanks for any info.
http://www.mediafire.com/file/cm8p5dp230ct5pj/video-16cabcf1288d8fd1d42fd4e79b122fc1-V.mp4/file
Sent from my Pixel 2 XL using Tapatalk
dennis_cu said:
When I open the camera app, the screen is shaking hence can't take photos. Only happens on the rear camera photo and video. When taking selfies everything is ok. I already tried factory reset and it's still the same.....
Click to expand...
Click to collapse
If this issue persists after FDR it is likely a hardware issue. Is your bootloader unlocked? As a last chance to rule out software you may want to try installing a full factory image from fastboot. Otherwise do you have any warranty options?
Maybe a video stabilization issue. Turn off the software option and see if it does anything. Either way, I would get a replacement.
Sent from my Pixel 2 XL using Tapatalk
Something weird, I tapped the camera lens at the back a bit hard multiple times and it fixed the issue. Problem is, after a few hours it shakes again and I have to tap the lens again for it to go away.
Sent from my Pixel 2 XL using Tapatalk
dennis_cu said:
Something weird, I tapped the camera lens at the back a bit hard multiple times and it fixed the issue. Problem is, after a few hours it shakes again and I have to tap the lens again for it to go away.
Click to expand...
Click to collapse
Sounds like a hardware issue to me. Time to explore any warranty options you may have.
I'm on my second Pixel 3 XL after an RMA for distorted bottom speaker.
I'm now noticing that the proximity sensor is stopping working when you bring the phone to your ear in a phone call and thus, leaving the screen visible and active.
A restart does fix this but only for about a day!
Has anyone else noticed this issue?
I didn't notice this on the unit that I sent back!
Thanks.
Do you have a screen protector covering the proximity sensor? It may not be working correctly if it's covered.
Is it only during calls or all the time? A few other people have posted about prox issues with the smaller Pixel 3, here's one thread:
https://forum.xda-developers.com/pixel-3/help/proximity-sensor-keeos-display-off-t3864055
Seems it can be fixed by cleaning the area around the sensor if you don't have a screen protector.
fury683 said:
Do you have a screen protector covering the proximity sensor? It may not be working correctly if it's covered.
Is it only during calls or all the time? A few other people have posted about prox issues with the smaller Pixel 3, here's one thread:
https://forum.xda-developers.com/pixel-3/help/proximity-sensor-keeos-display-off-t3864055
Seems it can be fixed by cleaning the area around the sensor if you don't have a screen protector.
Click to expand...
Click to collapse
Thanks for the suggestions.
No screen protector fitted or anything obscuring the sensor.
Next time it happens, I'll check to see if it might need cleaning.
One theory I have, is that this phone has been upgraded with the November patch and maybe there's something in there that has caused this issue.
Has anyone else noticed this after the Nov update?
Thanks.
jscsltd said:
I'm on my second Pixel 3 XL after an RMA for distorted bottom speaker.
I'm now noticing that the proximity sensor is stopping working when you bring the phone to your ear in a phone call and thus, leaving the screen visible and active.
A restart does fix this but only for about a day!
Has anyone else noticed this issue?
Click to expand...
Click to collapse
I just got the phone yesterday and am seeing the exact same behavior. It works and then it does not. Reboot temporarily fixes it.
I know there is a bug when using the pixel buds and unplugging them either before a call or during it would stop the proximity sensor from working.
a reboot was the only thing that would fix this issue for me
xweb10 said:
I just got the phone yesterday and am seeing the exact same behavior. It works and then it does not. Reboot temporarily fixes it.
Click to expand...
Click to collapse
I've RMA'd the phone that had this issue and still have the issue.
It does seem quite random. I'm hoping Dec Update will fix this along with the distorted bottom speaker.
I think that this issue is software related, as I tried using an App that shows when the proximity sensor is triggered and this seemed to work as expected.
How do I test my proximity sensor?
jscsltd said:
I've RMA'd the phone that had this issue and still have the issue.
It does seem quite random. I'm hoping Dec Update will fix this along with the distorted bottom speaker.
I think that this issue is software related, as I tried using an App that shows when the proximity sensor is triggered and this seemed to work as expected.
Click to expand...
Click to collapse
I am trying to get to the bottom of this. Do you happen to have a Samsung Gear watch? I have the S3 and removed the "phone calls" option from the Pixel Bluetooth menu and so far this issue has not occured, but I am still testing.
---------- Post added at 06:25 AM ---------- Previous post was at 06:24 AM ----------
swieder711 said:
How do I test my proximity sensor?
Click to expand...
Click to collapse
There are apps on the play store.
That's interesting regarding the Gear S3 watch.
Yes, I do have one of these watches.
I'll try what you've suggested and report back with the results.
What made you think it could be an interaction with the Gear S3?
Thanks.
jscsltd said:
That's interesting regarding the Gear S3 watch.
Yes, I do have one of these watches.
I'll try what you've suggested and report back with the results.
What made you think it could be an interaction with the Gear S3?
Thanks.
Click to expand...
Click to collapse
I have a pixel 2xl, as well. I looked at the Bluetooth setting on that phone when connected to my S3 and noticed the "phone calls" option was disabled.
I was looking at all apps that access the dialer or phone calls. Really just a guess.
xweb10 said:
I have a pixel 2xl, as well. I looked at the Bluetooth setting on that phone when connected to my S3 and noticed the "phone calls" option was disabled.
I was looking at all apps that access the dialer or phone calls. Really just a guess.
Click to expand...
Click to collapse
I see....good spot.
If I do disable this setting in Bluetooth though, will this just disable the ability to take voice calls on the watch using the internal microphone and speaker or will it as well, stop the watch from vibrating when a call comes in?
jscsltd said:
I see....good spot.
If I do disable this setting in Bluetooth though, will this just disable the ability to take voice calls on the watch using the internal microphone and speaker or will it as well, stop the watch from vibrating when a call comes in?
Click to expand...
Click to collapse
I believe it only disables the ability to take voice calls on the watch. It continues to vibrate when a call comes through.
I forgot: Also boot to Safe Mode first. I do not have a reason, but that is the path I took.
xweb10 said:
I believe it only disables the ability to take voice calls on the watch. It continues to vibrate when a call comes through.
I forgot: Also boot to Safe Mode first. I do not have a reason, but that is the path I took.
Click to expand...
Click to collapse
That's a shame that you can't take voice calls on the watch as that's a feature I do use at times.
Either, way I disabled it after more issues with the screen not blanking and will see how it goes.
I also had a new issue, where I'm in a call and could not switch to Speaker. I would choose the Speaker option but it just would not switch.
I'm wondering if you've had this same issue when you had your Gear S3 watch setup to take calls?
jscsltd said:
That's a shame that you can't take voice calls on the watch as that's a feature I do use at times.
Either, way I disabled it after more issues with the screen not blanking and will see how it goes.
I also had a new issue, where I'm in a call and could not switch to Speaker. I would choose the Speaker option but it just would not switch.
I'm wondering if you've had this same issue when you had your Gear S3 watch setup to take calls?
Click to expand...
Click to collapse
I am able to switch to speaker but I never have my S3 set to take calls. I have not gone full on Michael Knight yet.
BTW My proximity problems are gone. Must be the Bluetooth S3 issue.
I've had to RMA mine due to the bottom speaker crackling. I purchased from carphonewarehouse in the uk so have had to to a standard replacement. Does anyone know if they will send the replacement out before receiving the faulty one? They did this last year with the 2xl. It's not due to get back to them until next Thursday so hoping I won't have to wait too long.
baginz10 said:
I've had to RMA mine due to the bottom speaker crackling. I purchased from carphonewarehouse in the uk so have had to to a standard replacement. Does anyone know if they will send the replacement out before receiving the faulty one? They did this last year with the 2xl. It's not due to get back to them until next Thursday so hoping I won't have to wait too long.
Click to expand...
Click to collapse
I've had my pixel 3 XL replaced twice due to distorted bottom speaker by Carphone Warehouse Business.
They will deliver a replacement and then collect your faulty unit a few days later, in order to allow you to transfer your data to the new unit.
xweb10 said:
I am able to switch to speaker but I never have my S3 set to take calls. I have not gone full on Michael Knight yet.
BTW My proximity problems are gone. Must be the Bluetooth S3 issue.
Click to expand...
Click to collapse
I've switched off the ability to take calls on the S3 and can now switch to phone speaker with ease.
I'm hoping I can re-enable the S3 capability when an update by either Google or Samsung fixes the issue.
jscsltd said:
I've had my pixel 3 XL replaced twice due to distorted bottom speaker by Carphone Warehouse Business.
They will deliver a replacement and then collect your faulty unit a few days later, in order to allow you to transfer your data to the new unit.
Click to expand...
Click to collapse
Sorry I wasn't clear I've done an RMA with google so just wanted to see if anyone else had done the same even though they didn't purchase direct from them. Last year with the 2XL they would send the new one out once the faulty device was sent at the post office, they must have known from the tracking. This time it's via UPS and is going straight to Poland! Not due to arrive until the 4th. If a replacement doesn't get sent out tomorrow or Monday looks like I'll be waiting a while. I even noticed screen burn in when resetting it. Changed to Samsung displays and still burn in from the nav bar just like last year. I wish I'd gone back to carphonewarehouse now to get a replacement!
Wow, I never would have thought of the Samsung gear watch interfering. I have the newest one (the one after the s3) and had the same issue with the screen staying awake while on a call. It was the one thing I really didn't like about the phone. Seems like the symptoms are the same Pixel 3xl, verizon, Samsung Galaxy watch and a restart fixes the issue for a while. I just tried what you suggested. Thank you very much for posting your idea.
I've been dealing with a similar issue, but not exactly,
My screen turns off when I hold the phone against my ear, but the display still seems "active".
My cheek is still bringing the notification area down, toggling my quick settings or even going into the settings app (if my phone was unlocked while I answered a call).
It's been super constant and annoying because one time my flashlight was toggled in an elevator, which was a bit awkward.
Another time my clock app opened and changed my alarm time and then turned it off entirely.
Luckily I could feel the vibration so I knew something was going on but this is a really strange issue.
I have already setup a RMA since the phone has a speaker distortion problem as well, so we'll see what happens once the new device arrives.
The 3 XL has a really neat transition animation when you press the power button or double tap to wake, where your notifications kind of unfurl on your lockscreen.
Trouble is, I'm getting laggy animations 80% of the time. On occasion and for no apparent reason, it works and is fluid and smooth, but otherwise it's really choppy and stuttery. It's almost as if the phone is struggling to wake up properly.
Anyone else experiencing this? I noticed this pre-root, after root and on both stock & EX kernels. Rebooting the phone does not fix it, and it doesn't matter if the AOD option is on or off.
Yeps me to (
seeing some lag with the notifications on the lock screen, Don't know what could be triggering it
Same problem here on regular pixel 3, except it happens everywhere throughout the UI. I even got them to send a replacement device and it had the same issue. Really frustrating. Neither my pixel 1 or 2 had this issue.
RevoWution said:
The 3 XL has a really neat transition animation when you press the power button or double tap to wake, where your notifications kind of unfurl on your lockscreen.
Trouble is, I'm getting laggy animations 80% of the time. On occasion and for no apparent reason, it works and is fluid and smooth, but otherwise it's really choppy and stuttery. It's almost as if the phone is struggling to wake up properly.
Anyone else experiencing this? I noticed this pre-root, after root and on both stock & EX kernels. Rebooting the phone does not fix it, and it doesn't matter if the AOD option is on or off.
Click to expand...
Click to collapse
I'm facing the same issue. It's especially apparent when there are notifications on screen. Swiping a notification away looks incredibly laggy and painful. Really odd.
RevoWution said:
The 3 XL has a really neat transition animation when you press the power button or double tap to wake, where your notifications kind of unfurl on your lockscreen.
Trouble is, I'm getting laggy animations 80% of the time. On occasion and for no apparent reason, it works and is fluid and smooth, but otherwise it's really choppy and stuttery. It's almost as if the phone is struggling to wake up properly.
Anyone else experiencing this? I noticed this pre-root, after root and on both stock & EX kernels. Rebooting the phone does not fix it, and it doesn't matter if the AOD option is on or off.
Click to expand...
Click to collapse
Does that happen with the December patch ?
I had a similar problem on my Pixel 2 xl when I would pull down the notification shade. Turned out it was Pokemon go. Every time I had a notification from that app it would do it. The second I swiped it away it would go back to being fluid. I haven't installed it on my 3 xl.
Might want to swipe a notification away and see if that fixes it. Maybe something is weird with one app
malek777 said:
Does that happen with the December patch ?
Click to expand...
Click to collapse
Since the Dec patch, I haven't had it. All smooth for me. All stock.
malek777 said:
Does that happen with the December patch ?
Click to expand...
Click to collapse
Aaditya91 said:
Since the Dec patch, I haven't had it. All smooth for me. All stock.
Click to expand...
Click to collapse
I can confirm I'm still getting the issue with the December update...
I've noticed it's most evident/prominent when I'm on 4G/mobile network. When I'm connected to a WiFi network, it's almost always fluid. Weird...
I'm still getting the problem with the january update, I also present problems with the fingerprint reader when activating gestures, it doesn't always work
Anyone have further information on this. Really laggy compared to my 2xl. Same issue booting into safe mode as well
Sent from my Pixel 3 XL using Tapatalk
litrekid01 said:
Anyone have further information on this. Really laggy compared to my 2xl. Same issue booting into safe mode as well
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
I had 2 replacements because of this issue. I think it's a hardware issue.
malek777 said:
I had 2 replacements because of this issue. I think it's a hardware issue.
Click to expand...
Click to collapse
Wow, but you're good with the one u have now?
Sent from my Pixel 3 XL using Tapatalk
litrekid01 said:
Wow, but you're good with the one u have now?
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Yup this one so far has been good.
I also get this issue. Anytime I start seeing a bunch of lag, I always have a notification from Poke'mon GO. Once I clear it the lag goes away.
brand0nYates said:
I also get this issue. Anytime I start seeing a bunch of lag, I always have a notification from Poke'mon GO. Once I clear it the lag goes away.
Click to expand...
Click to collapse
I have exactly the same issue on my Pixel 2XL, manage to fix it by disabling Google Feed on the left of the main home screen. Try it let me know if it works