Related
I have unlocked and rooted with the latest 4.4 but have been facing lot of ghost touch, over heating and freeze. Is anyone else facing the same issues with their z1?
ravi_buz said:
I have unlocked and rooted with the latest 4.4 but have been facing lot of ghost touch, over heating and freeze. Is anyone else facing the same issues with their z1?
Click to expand...
Click to collapse
I haven't as yet but I did notice that the touch screen issue I had where my finger / thumb would lose contact briefly with the screen.
Hasn't happened a lot and holding the metal frame fixes it.
What youre describing could be a knock on effect of the new firmware having a higher sensitivity to the previous firmwares, I know Sony were aware of the touchscreen issue that people were facing and there was a fix where you could alter the sensitivity of the touch screen.
Could be that your touchscreen is set too high for your device in particular, either that or it's a problem with the touchscreen or even some dirt.
Give it a good old clean and a few reboots.
All the above is speculation of course, just having a stab at it for you m8.
Not sure where that thread is about the touchscreen but it's definitely in the Z1 forum.
dladz said:
I haven't as yet but I did notice that the touch screen issue I had where my finger / thumb would lose contact briefly with the screen.
Hasn't happened a lot and holding the metal frame fixes it.
What youre describing could be a knock on effect of the new firmware having a higher sensitivity to the previous firmwares, I know Sony were aware of the touchscreen issue that people were facing and there was a fix where you could alter the sensitivity of the touch screen.
Could be that your touchscreen is set too high for your device in particular, either that or it's a problem with the touchscreen or even some dirt.
Give it a good old clean and a few reboots.
All the above is speculation of course, just having a stab at it for you m8.
Not sure where that thread is about the touchscreen but it's definitely in the Z1 forum.
Click to expand...
Click to collapse
Cleaned it and rebooted. Din have this problem before rooting..but as soon as i rooted i started seeing these things happpen
ravi_buz said:
Cleaned it and rebooted. Din have this problem before rooting..but as soon as i rooted i started seeing these things happpen
Click to expand...
Click to collapse
So on the base that you were on you didn't have any issues, Rooting itself will not cause this issue.
What base were you on prior to rooting and what are you on now?
dladz said:
What youre describing could be a knock on effect of the new firmware having a higher sensitivity to the previous firmwares, I know Sony were aware of the touchscreen issue that people were facing and there was a fix where you could alter the sensitivity of the touch screen..
Click to expand...
Click to collapse
How can I alter the sensitivity of the Touch Screen?
EDIT: sorry, I forgot you don't know where it is..
---------- Post added at 02:32 PM ---------- Previous post was at 02:23 PM ----------
ravi_buz said:
Cleaned it and rebooted. Din have this problem before rooting..but as soon as i rooted i started seeing these things happpen
Click to expand...
Click to collapse
Same here, after rooting mine, it starts again the touch screen to respond strange, but not a big problem. Did not had this on .136.
dladz said:
So on the base that you were on you didn't have any issues, Rooting itself will not cause this issue.
What base were you on prior to rooting and what are you on now?
Click to expand...
Click to collapse
Actually Rooting can cause the issue because the Pre-Rooted version can be different from the original one installed on our phone.
After I received the phone from Repair they updated the Software and then I updated to .136 officially and the issue disappear, never had even a bit of it. Then I rooted, but to do so I used a different Base, NUT use the Frence region I think, and after that on mine .136 the problem with Touch Screen appear again, not badly, all is fine but sometime it skips something.
So I think it's really related to the Software and the all the phone have a specific Base.
eclyptos said:
Actually Rooting can cause the issue because the Pre-Rooted version can be different from the original one installed on our phone.
After I received the phone from Repair they updated the Software and then I updated to .136 officially and the issue disappear, never had even a bit of it. Then I rooted, but to do so I used a different Base, NUT use the Frence region I think, and after that on mine .136 the problem with Touch Screen appear again, not badly, all is fine but sometime it skips something.
So I think it's really related to the Software and the all the phone have a specific Base.
Click to expand...
Click to collapse
Then it would be down to the rom and not the rooting process, rooting alone won't affect the touchscreen m8.
The Rom could though.
dladz said:
Then it would be down to the rom and not the rooting process, rooting alone won't affect the touchscreen m8.
The Rom could though.
Click to expand...
Click to collapse
Of Course.
i have not experienced ghost touch but i did experience the screen failing to register two finger touch sometimes.
what i mean by that is when u quickly touch another part of the screen after its been touched it would register it as a swipe.
very annoying when typing keyboard or even pressing key pin on lockscreen.
i reproduced this in touch test and
once it registers as a faulty swipe while holding down the touch
it keeps registering swipe wherever the other finger presses untill i stop touching.
also when i installed a fresh rom it seems that the touch is very sensitive.
i tried this out http://forum.xda-developers.com/showthread.php?t=2691849
its not a fix but it helps out.
I think i have drilled down to the cause for this issue.
1. I started mounting my phone on my motorbike and ride. Due to excessive vibration the screen might have started acting out.
2. I also read that x alert causes this.
I have locked bootloder and installed stock ROM. Lets see whats happens
ravi_buz said:
I think i have drilled down to the cause for this issue.
1. I started mounting my phone on my motorbike and ride. Due to excessive vibration the screen might have started acting out.
Click to expand...
Click to collapse
I don't think this cause the issue.
ravi_buz said:
2. I also read that x alert causes this.
Click to expand...
Click to collapse
What is that or where it is?
Been trying to find that adjustment you can make for the touchscreen but can't find it. Its an adjustment of a file within android which deals with how sensitive the touch screen is. Buggered if I can find it though. I commented on it too. Eluded me.
Sent from my C6903 using XDA Premium 4 mobile app
dladz said:
Been trying to find that adjustment you can make for the touchscreen but can't find it. Its an adjustment of a file within android which deals with how sensitive the touch screen is. Buggered if I can find it though. I commented on it too. Eluded me.
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Maybe that Calibration.ini file magically can help?
BTW, if you find that thread let me know because I am interested too in changing the sensitivity, I will like to play with that.
eclyptos said:
Maybe that Calibration.ini file magically can help?
BTW, if you find that thread let me know because I am interested too in changing the sensitivity, I will like to play with that.
Click to expand...
Click to collapse
Will do m8.
dladz said:
Will do m8.
Click to expand...
Click to collapse
I would definitely be interested in this as well so could you please inform me as soon as you find something? Thanks
I am unable to pin point the problem.
1. Its not bcoz of root/boot loader
2. Not bcoz of mouting it on my bike. Infact when i mount it, it functions normally.
3. Ghost touch worsens when i play clash of clans but it is there other times too.
So its either bcoz of over heating (games make the phone heat a lot) or water entered it or i am not sure.
http://forum.xda-developers.com/showpost.php?p=51742613&postcount=8
He found my thread
I always surf the forums and check out what is happening, and this thread did catch my eye
I don't like to think that the touch screen issue is hardware related. I really hope it isn't.
Don't put your heart on this 'fix', as I have lost faith in it myself...
I'm going to post there now as well, to tell people what I have said here.
I've had my N6 since the 8th with no issues at all and suddenly it seems the OIS is acting up when I open the camera. Whatever mode I'm in it jumps all over the place and when in video mode this is then recorded in the same way. Its had no known drops and is in a rugged case anyway.
Has anyone else had this issue and is there a fix?
I have this issue while in landscape mode.. Seems like an RMA is the only solution.
I currently have this issue also. Jumps side to side in landscape mode then up and down in portrait mode. Your saying that it's hardware related? I really dont want to deal with the RMA process. I dont have the funds to do so either.
I've used the camera a lot, why has it suddenly started happening? Is there not a way to turn the OIS off? I've never had it before so I wouldn't miss it. I've looked in dev options and I've not rooted since JB so would rather avoid doing so.
Edit: Have any of you used Camera FV-5? I'm wondering if its since I used it as I didn't revert settings before uninstalling.
My camera is having the same issue. It jumps all over the place you can even hear it click. I decided to RMA. Should be getting another one soon.
Sent from my Nexus 6 using Tapatalk
jumpy camera? ive been seeing it all over the place.. get it exchanged, quick!
GMonkey said:
I've used the camera a lot, why has it suddenly started happening? Is there not a way to turn the OIS off? I've never had it before so I wouldn't miss it. I've looked in dev options and I've not rooted since JB so would rather avoid doing so.
Edit: Have any of you used Camera FV-5? I'm wondering if its since I used it as I didn't revert settings before uninstalling.
Click to expand...
Click to collapse
I use Camera FV-5 and all is fine with OIS on my side (at least for now) therefore I don't think it has anything to do with the issue you reported.
springer.music said:
I use Camera FV-5 and all is fine with OIS on my side (at least for now) therefore I don't think it has anything to do with the issue you reported.
Click to expand...
Click to collapse
Thanks, I'm happy its not the app as I liked some of the features. Guess its back to Tesco UK then. They should be ok for returns
Did you try with factory reset? I saw a case in which that solved it.
Hazzo31 said:
Did you try with factory reset? I saw a case in which that solved it.
Click to expand...
Click to collapse
Yeah, I tried it twice just to be sure. I was considering flashing a stock image at one point. I've taken it back for a replacement which should be ready to pick up on Monday. Just sat with my N5 for now and it feels tiny. How do my thumbs even fit on the screen? I was dreading going for such a big screen and now it's like I'm back on my old HTC Desire I had years ago. At least it's proved to me that when it comes to phones, bigger is better
GMonkey said:
I've used the camera a lot, why has it suddenly started happening? Is there not a way to turn the OIS off? I've never had it before so I wouldn't miss it. I've looked in dev options and I've not rooted since JB so would rather avoid doing so.
Edit: Have any of you used Camera FV-5? I'm wondering if its since I used it as I didn't revert settings before uninstalling.
Click to expand...
Click to collapse
I've never used Camera FV-5 and my phone has been in case (Spigen Neo Hybrid) since I took her out of the package.
Started out couldn't open the camera until after i rebooted consistently after taking pictures and stuffing it in my pocket; then focused like every 6 seconds this was annoying in video mode, then jumped side to side when in reg camera mode and video but not HDR+; but now its so bad that I can't even take pictures and forget zooming in looks like I'm in a fishbowl. Started RMA process today.
---------- Post added at 09:08 PM ---------- Previous post was at 09:02 PM ----------
Hazzo31 said:
Did you try with factory reset? I saw a case in which that solved it.
Click to expand...
Click to collapse
FDR (Factory Data Reset) did nothing for me. When I got home today I flashed stock 5.0.1 still have the same issue.
Here is a video I tried at the Texans game Sunday. https://www.youtube.com/watch?v=buzw9WZuHZ0
---------- Post added at 09:16 PM ---------- Previous post was at 09:08 PM ----------
Just looked directly at the camera and can see the lens moving around inside. Its definitely broken.
I have the same issue. Received on 12-14. Issue began and RMA created 12-22. Moto also has No stock to fulfill rma's with. Mine issue is in panorama mode only.
Video of camera jumping around. http://youtu.be/OkVoTMe1byo
Is there a way to try and FORCE this to happen? I get TINY a mounts of it but I'm not sure if its just the camera refocusing or if its actually an issue.
I have a similar problem that I believe is related to the OIS but instead of jumping it is almost vibrating. It focuses for a second then a blurry vibration look. I was gonna start the RMA process this afternoon.
Same problem didnt happen at first got worse over time, happens frequently now
I have the same problem. It did not happen for the first 5 or so days, then it started every once in a while, now it happens every time i record video.
Camera would refocus itself 2-3 times every few seconds -- seemed pretty rapidly but everyone seems to report this so I just assumed it was normal, but this constant refocusing during video could be an early warning sign that you will develope the OIS jumping problem.
Here is a video of the issue happening on my device:
http://youtu.be/H22vEKbujJk
Im on the phone right now with GPS store and this issue, my N6 camera has major shifting. The guy on the phone is checking if its a "known" problem, its sounds like he doesn't believe me, lol.
Having the same problem. If phone is in portrait, the image becomes incredibly fuzzy like an old television. In landscape, it's normal.
I have this weird brightness problem where I have it at 50% and it would randomly dim and brighten like crazy. I tested at 100% brightness and it also dims and brightens. Obviously, I don't have it on auto brightness but it sure acts like it.
Anyone with the same issue? Is it a defect? I just got the phone today and I'm afraid to exchange it to have the same problem again. I really like this phone. There's always a friggin issue on a new phone. It's ridiculous.
neotoky said:
I have this weird brightness problem where I have it at 50% and it would randomly dim and brighten like crazy. I tested at 100% brightness and it also dims and brightens. Obviously, I don't have it on auto brightness but it sure acts like it.
Anyone with the same issue? Is it a defect? I just got the phone today and I'm afraid to exchange it to have the same problem again. I really like this phone. There's always a friggin issue on a new phone. It's ridiculous.
Click to expand...
Click to collapse
I think is a software problem. Lollipop still have lot to fix. Mines look the same. Can be a display minor isue. Not sure, but for me this phone doesn't have the best brighness at all. But I love this phone better than others for now. If you came from samsung phone, there is a big diferent in brightness. Post some screen shoot. One in a white background, and the other in a grey one. I will post the same and you tell me if something is diferent. Sorry for my grammar. Is not the best !!!!?
---------- Post added at 09:22 AM ---------- Previous post was at 09:20 AM ----------
jfernandezv said:
I think is a software problem. Lollipop still have lot to fix. Mines look the same. Can be a display minor isue. Not sure, but for me this phone doesn't have the best brighness at all. But I love this phone better than others for now. If you came from samsung phone, there is a big diferent in brightness. Post some screen shoot. One in a white background, and the other in a grey one. I will post the same and you tell me if something is diferent. Sorry for my grammar. Is not the best !!!!?
Click to expand...
Click to collapse
Do it at 50%....
neotoky said:
I have this weird brightness problem where I have it at 50% and it would randomly dim and brighten like crazy. I tested at 100% brightness and it also dims and brightens. Obviously, I don't have it on auto brightness but it sure acts like it.
Anyone with the same issue? Is it a defect? I just got the phone today and I'm afraid to exchange it to have the same problem again. I really like this phone. There's always a friggin issue on a new phone. It's ridiculous.
Click to expand...
Click to collapse
My screen shoot!!!
neotoky said:
I have this weird brightness problem where I have it at 50% and it would randomly dim and brighten like crazy. I tested at 100% brightness and it also dims and brightens. Obviously, I don't have it on auto brightness but it sure acts like it.
Anyone with the same issue? Is it a defect? I just got the phone today and I'm afraid to exchange it to have the same problem again. I really like this phone. There's always a friggin issue on a new phone. It's ridiculous.
Click to expand...
Click to collapse
In Q&A is a thred call DPI Change. Try that, but reed carfully. you'll need root for that.
I appreciate your input but I don't know how the things you mentioned would help me in my case. I would need to do a video in order to see the problem instead of screen shots. Dpi change will do nothing in this case as well. You may be confused with the issue I have.
Well I try my best. As I sed could be a software problem. DPI is a resolution thing, can help a little. Also you can link a video to see exactly what you talking about. The reson I ask for the screen shoot is becaus I can probably see a differences between your brightness and mines. Hope somebody can help you on that.
I was wondering if anyone else had this issue with the front facing camera. There's a couple people that had this issue as well, check the
mentions for SamsungSupport on Twitter a couple days back(at the time of this post)
There's even a video of it in action: https://twitter.com/Hired_Assassin5/status/918633351510200320
As you can see at the top, there's some major discoloration going on. It's almost like a negative image.
https://i.imgur.com/2ipVzgS.jpg
I got the phone on Sep 15th, release day. The camera was working fine up until around Oct 5th that I know of. Taking selfies with the dog, etc.
Well, I opened it up on the 12th, haven't used it for a while, and I noticed that issue you see in the first image. I contacted Samsung and they had me
go through the whole troubleshooting process, all the way to me factory resetting my device. Factory Reset, then skipped all the setup wizards
and went straight to testing the camera. Issue is still present!
So the next day, I went to my carrier store, they said they never seen that before. So they're ordering me a shipment to replace it, possible defect.
Well, that night, I decided to try and look deeper into the issue. Flashlight on camera lenses, didn't see anything. Then I remembered from previous
android phones, there's hardware codes you can enter into the Dialer, so I input *#0*#, which is the hardware testing screen.
It looks like this:
https://i.imgur.com/RhJD4WJ.jpg
So obviously, one of the options is "FRONT CAM". I thought I would "test" it. I clicked on it, and it was working fine! I said oh sh!t, WTH.
This is the screenshot of it:
https://i.imgur.com/2BiaA7U.jpg
Then I took the picture as well, and it turned out just fine, like a normal camera. Well when you tap the screen again, it backs out, and switches
into a different mode, or something. And well sure enough, that issue I was having in my main camera app showed up!
This is a screenshot of it:
https://i.imgur.com/kGgJDD1.jpg
Now this is where I'm wondering if the Geniuses and good people here at XDA can figure out.
If you notice in the first screenshot of the "test" https://i.imgur.com/2BiaA7U.jpg
It says SUB AP at the top left....
Then in the next one, the defective one or whatever https://i.imgur.com/kGgJDD1.jpg
It says SUB CC.
Does anyone know what those are, or what they stand for? And if possible, how can I get my camera app to go back to using the correct mode or whatever that is.
This issue happens in all camera apps, the Samsung default camera app, play store camera apps, etc.
Thanks.
FunYunZ said:
I was wondering if anyone else had this issue with the front facing camera. There's a couple people that had this issue as well, check the
mentions for SamsungSupport on Twitter a couple days back(at the time of this post)
There's even a video of it in action: https://twitter.com/Hired_Assassin5/status/918633351510200320
As you can see at the top, there's some major discoloration going on. It's almost like a negative image.
https://i.imgur.com/2ipVzgS.jpg
I got the phone on Sep 15th, release day. The camera was working fine up until around Oct 5th that I know of. Taking selfies with the dog, etc.
Well, I opened it up on the 12th, haven't used it for a while, and I noticed that issue you see in the first image. I contacted Samsung and they had me
go through the whole troubleshooting process, all the way to me factory resetting my device. Factory Reset, then skipped all the setup wizards
and went straight to testing the camera. Issue is still present!
So the next day, I went to my carrier store, they said they never seen that before. So they're ordering me a shipment to replace it, possible defect.
Well, that night, I decided to try and look deeper into the issue. Flashlight on camera lenses, didn't see anything. Then I remembered from previous
android phones, there's hardware codes you can enter into the Dialer, so I input *#0*#, which is the hardware testing screen.
It looks like this:
https://i.imgur.com/RhJD4WJ.jpg
So obviously, one of the options is "FRONT CAM". I thought I would "test" it. I clicked on it, and it was working fine! I said oh sh!t, WTH.
This is the screenshot of it:
https://i.imgur.com/2BiaA7U.jpg
Then I took the picture as well, and it turned out just fine, like a normal camera. Well when you tap the screen again, it backs out, and switches
into a different mode, or something. And well sure enough, that issue I was having in my main camera app showed up!
This is a screenshot of it:
https://i.imgur.com/kGgJDD1.jpg
Now this is where I'm wondering if the Geniuses and good people here at XDA can figure out.
If you notice in the first screenshot of the "test" https://i.imgur.com/2BiaA7U.jpg
It says SUB AP at the top left....
Then in the next one, the defective one or whatever https://i.imgur.com/kGgJDD1.jpg
It says SUB CC.
Does anyone know what those are, or what they stand for? And if possible, how can I get my camera app to go back to using the correct mode or whatever that is.
This issue happens in all camera apps, the Samsung default camera app, play store camera apps, etc.
Thanks.
Click to expand...
Click to collapse
I'm not having that issue *knocks on wood*
But it doesn't sound like a hardware issue though.
Sub AP, Sub CC are probably different Samsung settings not available to end users. Any advice I'd give is to back up, hard reset, test if problem still present, if problem fixed restore data.
When does the problem usually happen, in bright or low light?
What if you use the front camera "flash" does it still happen?
lennie said:
I'm not having that issue *knocks on wood*
But it doesn't sound like a hardware issue though.
Sub AP, Sub CC are probably different Samsung settings not available to end users. Any advice I'd give is to back up, hard reset, test if problem still present, if problem fixed restore data.
When does the problem usually happen, in bright or low light?
What if you use the front camera "flash" does it still happen?
Click to expand...
Click to collapse
I originally thought it was a hardware issue, but seeing it function normally when I did the diagnostic testing, I knew it had to be
something that triggered the software to not work correctly.
the issue is still present no matter what settings I change. Changing resolution, flash on/off, picture size, HDR on/off/auto, all the settings
I can find, the issue is still exists.
EDIT: Is a hard rest the same as a Factory Reset?
FunYunZ said:
I originally thought it was a hardware issue, but seeing it function normally when I did the diagnostic testing, I knew it had to be
something that triggered the software to not work correctly.
the issue is still present no matter what settings I change. Changing resolution, flash on/off, picture size, HDR on/off/auto, all the settings
I can find, the issue is still exists.
EDIT: Is a hard rest the same as a Factory Reset?
Click to expand...
Click to collapse
hard reset = factory reset
have you tried using Odin and doing a fresh FW install?
htc-8925 said:
have you tried using Odin and doing a fresh FW install?
Click to expand...
Click to collapse
I have not. I did a factory reset.
My friend had the same issue.
whiteangelcl said:
My friend had the same issue.
Click to expand...
Click to collapse
Dam, that's unfortunate. That's 4 people now that have had this issue. I wonder how much worse it will get. Hopefully the new replacement doesn't have this issue.
It's weird because it was working fine for a few weeks, and then something happened. Not sure if it auto updated without me knowing and caused this issue.
FunYunZ said:
Dam, that's unfortunate. That's 4 people now that have had this issue. I wonder how much worse it will get. Hopefully the new replacement doesn't have this issue.
It's weird because it was working fine for a few weeks, and then something happened. Not sure if it auto updated without me knowing and caused this issue.
Click to expand...
Click to collapse
sounds like they're sending you a replacement. make sure you are satisfied with the replacement because they might send you a refurb.
i have the same issue as well ... so what happened at the end ? did they end up finding the issue ? how they fixed it ?
emazens said:
i have the same issue as well ... so what happened at the end ? did they end up finding the issue ? how they fixed it ?
Click to expand...
Click to collapse
Nope, Samsung never got back to me. I just went to the Tmobile store and they were like, yep, never seen that before. So they overnight me a new one.
I just begun to have the same issue on my phone and I'm not happy after spending 1k on it. I'm going to my career tomorrow but unfortunately don't know I this will be resolved. Please Let me know what Samsung did for you.
Same problem on my Note8. Following for solution.
solution anyone?
did anyone of u find a solution?
---------- Post added at 12:41 PM ---------- Previous post was at 12:38 PM ----------
i'm suffering with this problem presently and is trying to find a solve.
totaldepth said:
Same problem on my Note8. Following for solution.
Click to expand...
Click to collapse
i am seeing when i open camera ,camera failed
can anyone advise on how to fix?
If you did not mistreat the device, dropped it or fiddle with system settings or something of the sort, warranty is the all time solution for these problems
Hey my note 8 front camera just experienced the same issue. I've talked to Samsung support, and frankly it seems like it is a hardware issue. It is recommended that you use Samsung Support to make a service request. Free shipping both ways, so if you can live without your phone for a week or two (or have a backup phone to use), that's the route I recommend people going.
Original Problem:
MENU / COMMON APPLICATION ( NATIVE) - CAMERA / VIDEO - CAMERA EFFECTS NOT WORKING
Problem found:
FRONT CAMERA FAIL
Solution:
REPLACED COMPONENT
Click to expand...
Click to collapse
Did you manage to find the cause of the problem?
My front selfie camera has the same problem!
sorry to raise up this issue again.. my s8+ is from Indonesia region, and facing the same issue when try to use front camera is failed with notification Warning Unknown Error Occured.
already try Wipe cache partition and hard reset but still facing the same issue..
but if i use front camera for video call thru whatsapp it's working fine, but yet again if check thru *#0*# for Front Camera it's Camera Failed..
is it hardware issue or FW issue ?
Front Facing camera has double image
Has anyone found a fix for this issue yet? Mine started this issue last year and I haven't found a remedy for it yet. Ugh.
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?