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
I have only had my tf701 a day but Ive noticed sometimes when docked to the keyboard if you dont touch the mouse for a few seconds sometimes when you move the mouse again it will make a flicker around where the mouse is located, it doesnt always do it, just wondering if anyone has noticed this or is it a fault with my tablet?
I can live with it, but if there is a known fix it would be nice to sort it.
Thank You
After a bit of messing about I think it only does it with live wallpapers? Which isnt a problem as I wont be setteling on a live wallpaper anyway found them far too distracting.
Would still be nice to know this is fixable though.
Thank You
I was wrong its not to do with live wallpapers, just seems to do it on some apps, for example if I go to apex launcher then settings, if I leave the mouse for 10 seconds or more than rouch to move it, it makes the strange flash across the screen.
Could anyone else please test if theirs does this?
Thanks
Asus considers it to be a feature - not a bug - and calls it "smart backlight adjuster".
For most people it goes away upgrading to 4.3 which I guess you haven't done?
berndblb said:
Asus considers it to be a feature - not a bug - and calls it "smart backlight adjuster".
For most people it goes away upgrading to 4.3 which I guess you haven't done?
Click to expand...
Click to collapse
Yeah I am running 4.3?
I have noticed it does it on the drawer too, only when using the dock and leaving the mouse dormant for 8 seconds or more than moving it again it sends horizontal lines across the screen for a split second, is this the bug *ahem* feature you speak of?
Thanks
berndblb said:
Asus considers it to be a feature - not a bug - and calls it "smart backlight adjuster".
For most people it goes away upgrading to 4.3 which I guess you haven't done?
Click to expand...
Click to collapse
Also when you say adjuster, that sounds like it would be something that requires adjusting but it still does this with screen set to full brightness, or least brightness, with auto off, also wit outdoor on or off, it still does the strange flicker.
I can happily live with it, doesnt bother me that much just dont want it to be something that is going to get worse as Im very close to unlocking the device and dont want to blow all warranty if I already have a fault.
Thanks
dougie175 said:
Also when you say adjuster, that sounds like it would be something that requires adjusting but it still does this with screen set to full brightness, or least brightness, with auto off, also wit outdoor on or off, it still does the strange flicker.
I can happily live with it, doesnt bother me that much just dont want it to be something that is going to get worse as Im very close to unlocking the device and dont want to blow all warranty if I already have a fault.
Thanks
Click to expand...
Click to collapse
No what I had in mind was the screen dimming and brightening. What you describe sounds more like the "flashing black lines" the TF700 has (which seems to be due to some nvidia driver issue). I have not noticed those on the TF701 but then, I am so used to them from the 700 I probably wouldn't even notice. Have not read anything about them in the forums though, so I suspect your situation is unique.
Are you in the US? Get a Squaretrade warranty. I find the peace of mind is worth the $75 since they don't care about locked/unlocked...
berndblb said:
No what I had in mind was the screen dimming and brightening. What you describe sounds more like the "flashing black lines" the TF700 has (which seems to be due to some nvidia driver issue). I have not noticed those on the TF701 but then, I am so used to them from the 700 I probably wouldn't even notice. Have not read anything about them in the forums though, so I suspect your situation is unique.
Are you in the US? Get a Squaretrade warranty. I find the peace of mind is worth the $75 since they don't care about locked/unlocked...
Click to expand...
Click to collapse
No I am in the UK Im afraid, hmmmmm its deffo a tf701 not a 700 hehe
Can you please test for me open your drawer, leave the mouse in the centre for 10 seconds then move it and see if it does the black lines?
Also did the issue ever get resolved or get any worse on the 700 or is it just something the user gets used to?
Thank You
dougie175 said:
No I am in the UK Im afraid, hmmmmm its deffo a tf701 not a 700 hehe
Can you please test for me open your drawer, leave the mouse in the centre for 10 seconds then move it and see if it does the black lines?
Also did the issue ever get resolved or get any worse on the 700 or is it just something the user gets used to?
Thank You
Click to expand...
Click to collapse
Don't have the keyboard for the TF701 - yet. So I can't help you with your test.
The black lines on the 700 are benign - I don't even notice them anymore. But I don't think my 701 has them, so there is a possibility that your tablet has a glitch...
berndblb said:
Don't have the keyboard for the TF701 - yet. So I can't help you with your test.
The black lines on the 700 are benign - I don't even notice them anymore. But I don't think my 701 has them, so there is a possibility that your tablet has a glitch...
Click to expand...
Click to collapse
Thanks, I have sent Asus an email to see if they will help me, I bought the tablet second hand though so they probably have no interest even though it is only 3 months old and hasnt been out long enough to be out of warranty.
If they will fix or replace it for me ill take that, if not i can happily live with it
dougie175 said:
No I am in the UK Im afraid, hmmmmm its deffo a tf701 not a 700 hehe
Can you please test for me open your drawer, leave the mouse in the centre for 10 seconds then move it and see if it does the black lines?
Also did the issue ever get resolved or get any worse on the 700 or is it just something the user gets used to?
Thank You
Click to expand...
Click to collapse
Just tried your test and I see no lines. Maybe because I'm not on the stock rom exactly?
dougie175 said:
Thanks, I have sent Asus an email to see if they will help me, I bought the tablet second hand though so they probably have no interest even though it is only 3 months old and hasnt been out long enough to be out of warranty.
If they will fix or replace it for me ill take that, if not i can happily live with it
Click to expand...
Click to collapse
I don't want to be negative here, but waiting for Asus' response is pretty useless. Their support staff has two answers for questions beyond: "Where do I find my pictures?" and they are:
a) Factory reset, and if that does not help:
b) Send it in for repair - which may or may not cost you a bundle...
If you do send it in get written confirmation that your tablet is still under warranty first and take pictures of your tablet documenting its condition, how you packed and shipped it etc.
Thanks for the replies
This is what I get
dougie175 said:
Thanks for the replies
This is what I get
Click to expand...
Click to collapse
That is entirely different from what I thought it was and I have no idea what could be causing it. Do you get that ever when the dock is not connected?
berndblb said:
That is entirely different from what I thought it was and I have no idea what could be causing it. Do you get that ever when the dock is not connected?
Click to expand...
Click to collapse
No it cannot be replicated when the dock is not connected or when just touching the screen with or without the dock connected, it only does it on some areas of the system such as drawer and some apps if the mouse if left dormant for 8 seconds or so then moved.
I have done a factory reset and cold boot as requested by Asus, but the problem still persists as shown here in the new video
http://s9.photobucket.com/user/dougie175/media/Mobile Uploads/MOV_0020.mp4.html
dougie175 said:
No it cannot be replicated when the dock is not connected or when just touching the screen with or without the dock connected, it only does it on some areas of the system such as drawer and some apps if the mouse if left dormant for 8 seconds or so then moved.
I have done a factory reset and cold boot as requested by Asus, but the problem still persists as shown here in the new video
http://s9.photobucket.com/user/dougie175/media/Mobile Uploads/MOV_0020.mp4.html
Click to expand...
Click to collapse
Mine definitely doesn't do that. Try switching the cursor mode to gesture mode for me and see if that makes a difference. (I doubt it will but you never know)
Then go to the system settings, about and click the build number 7 times to enable developer mode. Then go into developer settings and look for force GPU rendering and disable hardware overlays. Check both. Reboot - any difference?
Check the cables
When troubleshooting a screen flicker, I always check the cables first. Several TechRepublic members agree. Ian C B, Bruceb, Crjordan, and Aqmike all suggested checking the video and monitor power cables before doing anything else. Ian C B reminds us to confirm that the cables are screwed in tightly and to replace the cables with new ones to see if the problem persists.
"The color changes are almost always a faulty wire in the cable," Crjordan said. "Try working the cable back and forth near both connectors. If this causes the color change, you could have a broken wire in the cable, or a loose pin in one of the connectors. Make sure the cable is out of the way (from feet, hands, and other objects). You may also try zip-tying it to itself or another stable object until you can replace either the cable or the monitor."
Check the environment
If a cable isn't the culprit, then the user's workspace should be next on your hit list. Monitors are notoriously sensitive to magnetic fields. Speakers, florescent lights, fans, cell phones, radios, and any other electrical device can cause a wide range of monitor problems. (See Figure A.) "Check what's around the [monitors]," Vilefileman said. "Cell phones are known to cause screen flickers, among other things, and plugging a radio or fan into the same receptacle can also cause screen flickers."
Maybe its like some kind of electrostatic interefereence in your environment more to do with the power being supplied to the device. Check cables. Etc. I think its interference or something.
sbdags said:
Mine definitely doesn't do that. Try switching the cursor mode to gesture mode for me and see if that makes a difference. (I doubt it will but you never know)
Then go to the system settings, about and click the build number 7 times to enable developer mode. Then go into developer settings and look for force GPU rendering and disable hardware overlays. Check both. Reboot - any difference?
Click to expand...
Click to collapse
I have noticed one other thing, it will not do the fault on first reboot, until the screen is locked, once unlocked it starts doing this fault
Gesture mode made no difference
Also done the developer options and they made no difference :crying:
sbdags said:
Mine definitely doesn't do that. Try switching the cursor mode to gesture mode for me and see if that makes a difference. (I doubt it will but you never know)
Then go to the system settings, about and click the build number 7 times to enable developer mode. Then go into developer settings and look for force GPU rendering and disable hardware overlays. Check both. Reboot - any difference?
Click to expand...
Click to collapse
I was wrong disabling hardware overlays does seem to resolve the issue?
However each time I reboot the option is un ticked that's why I thought it didn't do it
YayYouFixedIt said:
Check the cables
When troubleshooting a screen flicker, I always check the cables first. Several TechRepublic members agree. Ian C B, Bruceb, Crjordan, and Aqmike all suggested checking the video and monitor power cables before doing anything else. Ian C B reminds us to confirm that the cables are screwed in tightly and to replace the cables with new ones to see if the problem persists.
"The color changes are almost always a faulty wire in the cable," Crjordan said. "Try working the cable back and forth near both connectors. If this causes the color change, you could have a broken wire in the cable, or a loose pin in one of the connectors. Make sure the cable is out of the way (from feet, hands, and other objects). You may also try zip-tying it to itself or another stable object until you can replace either the cable or the monitor."
Check the environment
If a cable isn't the culprit, then the user's workspace should be next on your hit list. Monitors are notoriously sensitive to magnetic fields. Speakers, florescent lights, fans, cell phones, radios, and any other electrical device can cause a wide range of monitor problems. (See Figure A.) "Check what's around the [monitors]," Vilefileman said. "Cell phones are known to cause screen flickers, among other things, and plugging a radio or fan into the same receptacle can also cause screen flickers."
Maybe its like some kind of electrostatic interefereence in your environment more to do with the power being supplied to the device. Check cables. Etc. I think its interference or something.
Click to expand...
Click to collapse
Theres not really any cables I can check, I have checked the connection is pushed in correctly which it is.
I have just tried to replicate the error outside with my phone turned off inside the house so no chance of interference and the error was still present.
Don't think this is quite the issue as it only does it when moving the mouse after leaving it on certain apps for 8 seconds.
Thank you for the help though
I have Moto360 and it's supposed to keep the phone unlocked. Well, once in a while (at least once per day) it doesn't work so I decided to add a Trusted Location (my house). This made it worse because there seems to be some sort of "race condition" and I get a lot more issues at work now. Basically it seems like it's seeing that I'm not home and skips the check of Moto360 presence all-together. I also added an NFC tag (for my car in case I forget Moto360 at home). So having these 3 settings enabled at once makes this a worse experience than just with Moto360 (which isn't reliable to begin with)
Anyway, this unlocking mechanism is one big mess and hasn't been reliable for me. I understand that it's better to be safe than sorry but these are clear bugs.
Anyone else experiencing this?
T-R said:
I have Moto360 and it's supposed to keep the phone unlocked. Well, once in a while (at least once per day) it doesn't work so I decided to add a Trusted Location (my house). This made it worse because there seems to be some sort of "race condition" and I get a lot more issues at work now. Basically it seems like it's seeing that I'm not home and skips the check of Moto360 presence all-together. I also added an NFC tag (for my car in case I forget Moto360 at home). So having these 3 settings enabled at once makes this a worse experience than just with Moto360 (which isn't reliable to begin with)
Anyway, this unlocking mechanism is one big mess and hasn't been reliable for me. I understand that it's better to be safe than sorry but these are clear bugs.
Anyone else experiencing this?
Click to expand...
Click to collapse
That's strange. I have the same setup except my car's BT is a trusted pair also.
No issues here.
Dusty Rhodes said:
That's strange. I have the same setup except my car's BT is a trusted pair also.
No issues here.
Click to expand...
Click to collapse
Is the BT in ur car capable to read your text msg? My note 4 use do it perfect but nexus is not option is grayed out on my car screen.
My home and work are "trusted places" and it works about 50% of the time. At work it barely works...My Nexus 5 was the same way. It is probably a thing on Google's end that they need to update.
T-R said:
I have Moto360 and it's supposed to keep the phone unlocked. Well, once in a while (at least once per day) it doesn't work so I decided to add a Trusted Location (my house). This made it worse because there seems to be some sort of "race condition" and I get a lot more issues at work now. Basically it seems like it's seeing that I'm not home and skips the check of Moto360 presence all-together. I also added an NFC tag (for my car in case I forget Moto360 at home). So having these 3 settings enabled at once makes this a worse experience than just with Moto360 (which isn't reliable to begin with)
Anyway, this unlocking mechanism is one big mess and hasn't been reliable for me. I understand that it's better to be safe than sorry but these are clear bugs.
Anyone else experiencing this?
Click to expand...
Click to collapse
i'm not experiencing this at all. i've had it working with my N5 flawlessly (before i got my N6) as well. if your phone isn't showing that you're at home, your location services might be turned off though.
worst case is that you back up your settings and try a clean wipe/reflash and see if it's working as expected.
*EDIT* are you sure that you're not accidentally hitting the little lock/unlock icon at the bottom of the screen? that will lock it regardless of the trusted devices/location settings.
NICEGYPT said:
Is the BT in ur car capable to read your text msg? My note 4 use do it perfect but nexus is not option is grayed out on my car screen.
Click to expand...
Click to collapse
Mine could work but I use hangouts as my messaging app and THAT doesn't work.
So that you know what I'm working with, I have a 2012 Mustang GT with MyFordTouch.
Dusty Rhodes said:
Mine could work but I use hangouts as my messaging app and THAT doesn't work.
So that you know what I'm working with, I have a 2012 Mustang GT with MyFordTouch.
Click to expand...
Click to collapse
I have a 2014 Charger with Uconnect
Lucke said:
*EDIT* are you sure that you're not accidentally hitting the little lock/unlock icon at the bottom of the screen? that will lock it regardless of the trusted devices/location settings.
Click to expand...
Click to collapse
Wow, that could be it! I didn't even realize this icon is there and I often unlock from the very bottom (old habits). I will pay attention from now on and hopefully this is exactly what it was.
Thank you!
T-R said:
Wow, that could be it! I didn't even realize this icon is there and I often unlock from the very bottom (old habits). I will pay attention from now on and hopefully this is exactly what it was.
Thank you!
Click to expand...
Click to collapse
Haha I had the same problem til I realized this
Seems I'm late to the party here as this forum may not have a lot of regular posters (save for the development thread that got an immediate answer this morning, which was awesome!)
Does anyone wear their Urbane (or any other smart watch) on the inside of their wrist? I've always worn my watches like this, to the point where it feels weird if I wear it on top.
Not as concerned with waking it up when I turn my wrist (though that would be awesome if I could figure that out), just wondering if I'm alone. Did a Google search and I found a couple of reddit posts on the Moto 360 being worn this way, but that's it.
Am I in danger of things like the step counter not functioning right? Has anyone figured out how to get the wake gestures working when it's worn this way? If not, that's fine. I can tap with no problems, just curious more than anything.
Really liking this watch so far. Next up will be a new band, I'm sure (after I get done messing with the faces, that is).
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.