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?
Related
Hey guys,
Thought I'd post this here and keep you guys updated on further developments.
I live in the Netherlands and bought a 32GB version at Dixons at the 13th of November 2012
I had found the touchscreen a bit unresponsive sometimes in the past.
But couldn't really find out why it was acting up. I finally isolated the issue.
It is exactly the same as this guys vid:
(Thanks for the vid injahnet)
Together with a little backlight bleeding, I decided to send for repair.
(The problem persisted after a factory reset, no other apps were open when testing.)
I went back to Dixons and showed the problem to the Dixons dude.
He acknowledged there was an issue and sent it for repairs or replacement.
Due to the holidays this can take some time. Maybe even next year
I was about to open my tablet for a look inside one of these days, boy am I glad I didn't do that yet
Anyway to get a good view on this issue globally, are there more people that have the same issue?
You could go to: Settings > Developer options > and then under "Input" you can enable Show touches. and try to to the same procedure as in the vid. (Thanks Peterk-1)
Or you could test with MultiTouchTester like Injahnet.
The weird thing is, my dad's N7 16GB does the same.
Update 17-12-2012: Please do not test while plugged in as the device will be grounded and the issue will not occur. (Thanks dad)
Feedback is really appreciated!
Please vote in the poll above!
Cheers,
Daan
I have zero problems with multitouch while using my Nexus 7. Working just fine, but you must disable any apps which interfere with gestures or it'll steal events.
Can't say I've ever used multitouch with the N7 laying on a random object however.
But sure, send it in for repair......... I'll keep using mine.
If anyone thinks they have multi touch problems then loading an app isn't required. Just go into Developer Options and under Input you have two options to display touch and track detail.
peterk-1 said:
If anyone thinks they have multi touch problems then loading an app isn't required. Just go into Developer Options and under Input you have two options to display touch and track detail.
Click to expand...
Click to collapse
Nice one. I'll add that.
khaytsus said:
I have zero problems with multitouch while using my Nexus 7. Working just fine, but you must disable any apps which interfere with gestures or it'll steal events.
Can't say I've ever used multitouch with the N7 laying on a random object however.
But sure, send it in for repair......... I'll keep using mine.
Click to expand...
Click to collapse
I've done a factory reset before I tested No apps are open except MultiTouchTester
It's in for repairs
Well... Over 200 views. And only 4 votes, which includes mine
Community feedback is failing hard.
Anyway, I'll keep you guys posted on the repaired Nexus.
At the moment of writing we know that three people are having this issue.
I know someone else with a nexus I'll check if he has the issue too.
Cheers,
Daan
Yes, i have this problem. And only while device is laying on the table.
Wow, this is bizarre, thanks for pointing it out. I can confirm it happens when it's laying on my pillow, and doesn't when I'm holding it.
Thanks for the vote guys.
By the way, it seems obvious that the Nexus should not be plugged in while testing.
However I cannot test this 'cause mine is at the shop
Would anyone be willing to test?
I'll add that in the original post (+ a mention of your name and a thank you of course))
Cheers,
Daan
Mine was unplugged while testing.
Sent from my Nexus 7 using Tapatalk 2
if the two touch-points got the same X or Y coordinate my nex7 does only detect one of them. i don't think this is an issue.
herrrevo said:
if the two touch-points got the same X or Y coordinate my nex7 does only detect one of them. i don't think this is an issue.
Click to expand...
Click to collapse
However, zooming in Google maps for example will become quite difficult
Anyone try and see if taping the ground pin on the wifi antenna fixes the issue? This seams like a grounding problem.
ionstorm66 said:
Anyone try and see if taping the ground pin on the wifi antenna fixes the issue? This seams like a grounding problem.
Click to expand...
Click to collapse
Exactly! I was also thinking of this.
Do people who have this issue also have the flickering issue!?
ecoviws buttress
Just an FYI, I installed CM 10.1 with Trinty Seven. Now I get 10 touches on pretty much any surface.
I don't have a multitouch issue, but I do have an entire band on my screen which has stopped responding to touch at times. It all started when I let my tab shut down due to low battery. Initially, the Nexus 7 neither charged (when put on charging, obviously), nor did it boot up. After trying for several hours, somehow it started charging. And since then, sometimes certain areas of my touchscreen become unresponsive to touch. Since the band which is unresponsive is towards the upper part of the screen, using notifications becomes completely impossible. It keeps 'snapping back up' when I try to pull it down, cos while I am pulling it down, the notification tray encounters an unresponsive area, so it just goes back up. Called up Google and they will be sending a replacement device. All I am afraid about is that I have an 8gb version, and they would be sending an 8gb as well, so I hope it isn't refurbished or something, as Asus has stopped making the 8gig model.
I'm having an issue where the screen, ( mostly in a webpage or document,) starts moving up and down and zooming in and out without my input.
Sent from my Nexus 7 using xda app-developers app
Just tested this out and yes, my device is doing it too. Interesting. No other issues like screen flicker (except the auto brightness bug in 4.2). My n7 is c9O
DaanJordaan said:
Well... Over 200 views. And only 4 votes, which includes mine
Community feedback is failing hard.
Anyway, I'll keep you guys posted on the repaired Nexus.
At the moment of writing we know that three people are having this issue.
I know someone else with a nexus I'll check if he has the issue too.
Cheers,
Daan
Click to expand...
Click to collapse
community feedback is not failing hard, more like you're just starting a new thread without bothering to search if issue/topic already exist.
this isn't new and there is no fix, that is just how the touchscreen function. the N7 isn't the only device to have this.
dilldoe said:
community feedback is not failing hard, more like you're just starting a new thread without bothering to search if issue/topic already exist.
this isn't new and there is no fix, that is just how the touchscreen function. the N7 isn't the only device to have this.
Click to expand...
Click to collapse
Don't feed the trolls!
Must... not... feed... aaargh....
You are kinda missing the point of this thread.
It is to see how many people have this issue.
There is no thread capturing that in an easy way unless you want to count every post.
Now please tell your brain to start functioning again and leave this thread alone if you have nothing to add.
Asus Google Nexus 7 32GB touch death zone
Hi DaanJordaan,
Found out that my brand new N7 seems to have a similar "no touch zone" issue; an area the size of my little finger on the left lower part of my screen does not seem to react to touch! It interferes with typing the keyboard in portrait mode (no keyboard problems in up-side-down portrait mode).
When I use the Easylabs Multi Touch test I can see the dot changing color when I move over this area, doesn't happen anywhere else on the screen..
Using the developer tools (turning on the two options that allows to show touch/leave a trail of touch) it becomes even more clear that this area does not react to touch! I can "paint" lines around the "no touch zone" (it actually splits into 2 touch areas using one finger around the "death spot"), and the "no touch zone" reveals itself by not showing any trail/history line of touch..
Oh yes, and it does not matter if I lay the N7 on the table, or hold it in my hand, the issue is always there.
Therefore I returned the N7 back to the MediaMarkt, and they will send it in for repairs...
I've got a bad feeling about this | - )
I am curious to hear about experiences with your N7, once you have it back!
I'll report mine here, in three weeks or so (that's the outlook...).
Cheers!
NeverMind
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...
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.
This is a pretty big issue that blue up on the OnePlus forum and Reddit. People are experiencing ghost touches in apps. It's very easy to also experience this by opening cpu-z and letting it sit there for a minute or two not doing anything. It seems not everyone is experiencing this though. I have tested and do experience it. Do you?
Yup. Mine does with cpu-z open. what do we do?
BossJ said:
Yup. Mine does with cpu-z open. what do we do?
Click to expand...
Click to collapse
Depends if it's a hardware or software issue. Personally I already submitted a return request with OnePlus.
I just cancelled my order.. hopefully there is a software fix for you guys
This only happens to me on cpu-z and not in any other app. So I guess a future software update is gonna fix it.
Left it for a minute and didn't notice anything. On 9.5.3, bootloader unlocked and patched boot image with root.
I haven't experienced in a few days, it was happening a lot until I disabled pretty much all gestures.
I installed CPU-Z just to check on my International 8GB/256 model and I've got no issue with ghost touches. Not sure what is causing this for you all, but I do hope it is sorted out for you all.
When I turned off NFC the issue went away for me glad I don't use it whatsoever haha
Purest said:
I haven't experienced in a few days, it was happening a lot until I disabled pretty much all gestures.
Click to expand...
Click to collapse
Well that's not a solution disabling a useful feature to not have ghost touch issue.
On screen/off screen gesture are one of my favorite using it, so not a solution to me.
Simple will return the device.
I haven't order yet but i will next couple of days.
There's many reports across oneplus forum.
https://www.androidpolice.com/2019/...ros-are-suffering-phantom-touch-input-issues/
I left CPU-Z running for at least 10 mins.
And all is OK. Maybe it's a rouge program or something to do with the unlock\twrp?
The only way to be sure is to reset to stock and only install CPU-Z
Seems OnePlus using Novatek panels https://github.com/OnePlusOSS/andro...input/touchscreen/oneplus_touchscreen/Novatek
Poco F1 had same problems with Novatec and only way fix it was replacing whole panels, they tried to fix over updates but witout luck
romanB_SK said:
Seems OnePlus using Novatek panels https://github.com/OnePlusOSS/andro...input/touchscreen/oneplus_touchscreen/Novatek
Poco F1 had same problems with Novatec and only way fix it was replacing whole panels, they tried to fix over updates but witout luck
Click to expand...
Click to collapse
Wow that's seems real bummer.
Why would OP use Novatek display controller since had bad reputation and bad track record.
So the question is how do we know if all that units effected having all of the them Novatek display controller?
Or if there's another supplier for those units that don't have that issue.
Man things are getting much worse if it's hardware related and not software that I thought.
Sent from my V1821A using Tapatalk
It's extremely annoying it has happened to me a few times even when I was boasting about the new device to some colleagues at work. I thought it was me at first until then I read IRS an actual thing. I won't return it yet but I might if it's not sorted soon. It's extremely irritating.
Sent from my [device_name] using XDA-Developers Legacy app
Looks like ghost touches are related to NFC. Try with NFC turned off.
C3C076 said:
Looks like ghost touches are related to NFC. Try with NFC turned off.
Click to expand...
Click to collapse
Can confirm. My Ghost touches seize when NFC is disabled.
Sent from my GM1913 using Tapatalk
I've started yesterday experiencing that ghost touchs and also screen not responsive to touch in some panel sections (mostly the upper right zone). The phone didn't gave me that problem since I bought. I noticed when this happening, pulling the notification bar down to the tile settings makes that zone work again. Same thing happened when that random ghost touchs happens.
Didn't had any problems, don't use NFC, tried turning it on, ghost touches started appearing on cpuz, but not on other apps. As i don't use NFC i probably won't return the phone.
I just tried with CPU-Z and a few seconds after starting the app, the screen turns crazy tapping here and there. Can confirm also disabling NFC solves it.
Turning off nfc or not using gestures or not using cpuz app is just temporary solution.
And there's multiple reports that ghost issues happening other app too.
And we never know if thing get worse over time.
I'm afraid it's a more common issue than we thought but many users simple didn't notice it until now.
Oneplus should clearly take attention on that issue seriously and fix it ASAP.
Shouldn't be happening at all with any kind app or scenario of usage.
Sent from my V1821A using Tapatalk
Hi all,
Been quite a few years since I posted anything here!
I have just received my pixel 5 and have noticed that dead center of the notification tray when in portrait, there is a flickering dot, especially in low light it flickers white or if not flickering leaves a faint grey dot over whatever is on the screen (stays in the same place even if I rotate the phone or watch a video)
If I reboot I can't see it for a minute or so until it then appears.
Factory reset doesn't solve it.
Has anyone else noticed this? I'm thinking it might be the ambient light sensor under the display but it is really irritating, possibly mine is faulty?
Cheers!
It's the underscreen proximity sensor.
I get that it is the proximity sensor but, It is flashing constantly - I spoke to google and they said that it should only show when in a call - it is flashing even while watching YouTube - does anyone else get this same behaviour?
Not showing on mine
I have it constantly when KinScreen is running, I saw someone having it with cpuz
I hadn't noticed until I saw this thread. I did wonder where the proximity sensor was. It's only visible when on a phone call for me.
Is the light sensor under the screen also? You can usually see that on a lot of devices when you tilt the screen slightly.
Joshhudsy said:
I get that it is the proximity sensor but, It is flashing constantly - I spoke to google and they said that it should only show when in a call - it is flashing even while watching YouTube - does anyone else get this same behaviour?
Click to expand...
Click to collapse
Mine only shows when on a call
You probably have some apps using it. Possibly something like Tasker that happened to have proximity sensor based profiles configured, etc.
Mine went mental during Google Play downloading all my apps on initial phone setup. Then it went out and I've not seen it since.
Joshhudsy said:
I get that it is the proximity sensor but, It is flashing constantly - I spoke to google and they said that it should only show when in a call - it is flashing even while watching YouTube - does anyone else get this same behaviour?
Click to expand...
Click to collapse
It's a software bug. I read about it on reddit and twitter yesterday. Did you move your data from your old phone using the cable?
To fix it you should factory reset, then migrate your old data using WiFi, not cable, don't restore or restore your apps manually (at least until you make sure it's fixed).
If that still doesn't work, check if you have an app called HomeAssistant (HASSIO) installed. There's one report of that causing it. To fix that you need to disable the proximity sensor on the assistant app itself.
Sources: here, here, and here.
I got the same Problem after installing notifybuddy. There must be some Bug where the sensor gets started the moment an overlay is shown. I can reproduce the Bug over and over again. Install notifybuddy and Start the App give all permissions and than Pull down notificationscenter (its an overlay). To solve the Problem, uninstall notification Apps That are using overlays.
Mine is working fine. Only during a call or listening to voice messages.
akpe said:
It's a software bug. I read about it on reddit and twitter yesterday. Did you move your data from your old phone using the cable?
To fix it you should factory reset, then migrate your old data using WiFi, not cable, don't restore or restore your apps manually (at least until you make sure it's fixed).
If that still doesn't work, check if you have an app called HomeAssistant (HASSIO) installed. There's one report of that causing it. To fix that you need to disable the proximity sensor on the assistant app itself.
Sources: here, here, and here.
Click to expand...
Click to collapse
Hit the nail on the head there!
It was the Home assistant app causing it (even though it had installed after restoring from my backup, I had never opened it yet since having this phone). Uninstalled home assistant and it has stopped flashing!
Thanks so much for the replies all!
Have this issue on my one too...which is the home assistant app? Deleted the "Home" but that doesn't seem to have solved the problem.
Anwar902 said:
Have this issue on my one too...which is the home assistant app? Deleted the "Home" but that doesn't seem to have solved the problem.
Click to expand...
Click to collapse
Go to the gestures options (don't know exactly where the specific one is located, it could also be at the Digital Wellbeing settings) and disable the Flip to Shh one. See if that helps.
Στάλθηκε από το Mi A2 μου χρησιμοποιώντας Tapatalk
Anwar902 said:
Have this issue on my one too...which is the home assistant app? Deleted the "Home" but that doesn't seem to have solved the problem.
Click to expand...
Click to collapse
The Home assistant is a 3rd party home automation app that I had previously installed - if you don't use it, I'd check for any other apps you have installed for something that might be using the proximity sensor.
Couldn't find that was causing the issue. After a restart it would be fine but once unlocked and apps started loading it would go crazy. Went through all my apps but couldn't find the cause so just reset my phone. Hopefully it doesn't show up again.
Seems to.be software issue so hopefully google will do something about it
Joshhudsy said:
The Home assistant is a 3rd party home automation app that I had previously installed - if you don't use it, I'd check for any other apps you have installed for something that might be using the proximity sensor.
Click to expand...
Click to collapse
It really shouldn't matter if something is using the proximity sensor. It shouldn't ever be visible.
jimv1983 said:
It really shouldn't matter if something is using the proximity sensor. It shouldn't ever be visible.
Click to expand...
Click to collapse
That's incorrect. A quick Google search for "S20 proximity sensor blinking" will yield results that show otherwise. Maybe go to YouTube instead as there's quite a few videos there on it. The Samsung subreddit has an influx of posts, it seems, for almost every device they've released over the past couple of years because folks aren't used to seeing it. It's visible under the display on my S20 Ultra and I had it on my S10 plus also.
Now of course there's bugs where it's blinking on the Pixel 5 when it shouldn't, but is it supposed to be visible when an app is using it legitimately? Yes.
Edit: It just dawned on me that YouTube vids wouldn't be the best example of this because they use cameras to video the proximity detector. Everything else stands though. Google searches and Samsung subreddits are ripe with examples though.
MasterBelch said:
That's incorrect. A quick Google search for "S20 proximity sensor blinking" will yield results that show otherwise. Maybe go to YouTube instead as there's quite a few videos there on it. The Samsung subreddit has an influx of posts, it seems, for almost every device they've released over the past couple of years because folks aren't used to seeing it. It's visible under the display on my S20 Ultra and I had it on my S10 plus also.
Now of course there's bugs where it's blinking on the Pixel 5 when it shouldn't, but is it supposed to be visible when an app is using it legitimately? Yes.
Edit: It just dawned on me that YouTube vids wouldn't be the best example of this because they use cameras to video the proximity detector. Everything else stands though. Google searches and Samsung subreddits are ripe with examples though.
Click to expand...
Click to collapse
If what you are saying is true then why can't you see the sensor flashing on any phone when in a phone call or when the "Flip To Shhh" feature is enabled with just your eyes?
And if that is true about the Pixel 5 then there will be no way to use the "Flip To Shhh" feature without always seeing the sensor flashing which I can do with my Pixel 2 XL.
Here is a video of my Pixel 2 XL taken with the camera on my tablet. You can see that the tablet picks up the flickering sensor when "Flip To Shhh" but the sensor goes off when I turn the feature off. That's because the feature uses the proximity sensor to work. However, the flickering is ONLY picked up by the camera on my other device. I can't see it with just my eyes looking at the phone even though the sensor is active.
https://streamable.com/z30mgx