Related
Does anyone have a solution for phantom taps on your NC?
I'm on my 3rd Nook Color when I pick up the replacement unit this afternoon.
My general issues are phantom taps - or the NC doing things I don't want it to. So far a very poor experience when typing, turning a page in a book, or even just navigating the ui. The whole issue may be me, it happens regardless if I am plugged in or not. I keep a very clean screen so there is very to little gunk.
I do have sweaty palms on occasion but not out of the ordinary. I have other touch devices that have never given me this issue. If anything I think the screen is overly sensitive - hardware or software issue?
Nope it's not just you. Mine has a multitude of issues with the touchscreen...
Essentially I cannot use the touchscreen when the device is plugged into stock charger/cable as wherever I put my finger, a random touch appears somewhere on the x-axis near my finger.
It seems that the device does not like changes in temperature or humidity either when it is unplugged. Using my tablet while cold was impossible, and likewise while it had been warm.
I'm on my second tablet from Best Buy-- the first one had dead pixels galore (enough to make the best buy rep say "dang!"), and now this one has a bad touchscreen and hard to press power button.
However: I purchased one of these for my mother a few days before mine at Barnes and Noble, and it has no issues whatsoever... at least not yet.
I've come to the conclusion that this hardware is quite beta, but I'm willing to give them a chance since it is the best bang for the buck, even if I have to go through a couple of returns... it's honestly almost worth the time for me since a tablet is so valuable for schoolwork.
Fortunately mine does not do this. I think maybe for those that are having this issue it may be able to be fixed in a firmware update.
My EVO had extremely similar problems when it first came out with the touchscreen and not being able to use the dropdown menu while the device wasn't grounded. After a firmware update the phone was great with touch sensitivity.
my first one did this also. so far the second is doing fine, but the first didn't have any problems till the 13th day of owning it.
i'm hoping it's just an issue that can be fixed via software - maybe someone put an incorrect voltage input somewhere.
I was having the same issues. I bought a screen protector and that seemed to solve it. So far, it's been working fine.
I noticed the screen protector stabilized the touchscreen a lot. Before I seem to have a problem finding the sweet spot for a touch. Now it seems better.
However, my phantom pinky is always touching something while I am trying to navigate. As long I only get one finger near the screen, it's fine.
Mine came from B&N.
The only other issue I have is the magnetic clasp in the cover seems to throw the internal compass/magnetometer off a lot.
Awats said:
The only other issue I have is the magnetic clasp in the cover seems to throw the internal compass/magnetometer off a lot.
Click to expand...
Click to collapse
Considering the Nook has neither I think you are okay.
khaytsus said:
Considering the Nook has neither I think you are okay.
Click to expand...
Click to collapse
Then how is it managing to correctly position the screen with Google Sky? Is it just spooky smart?
Mine only has problem when screen gets dirty. Try a screen protector or use gloves.
is there really a compass in this thing? I just assumed there wasn't. if there is I'm buying another tomorrow!
Screen protector helps to solve my problem.
Are you seeing more issues right after cleaning the screen? I see issues then and I think it is because I an using some moisture on the cloth. If I just dust it lightly with a dry cloth and live with a few finger prints there seem to be less of an issue.
Awats said:
Then how is it managing to correctly position the screen with Google Sky? Is it just spooky smart?
Click to expand...
Click to collapse
Wifi location services provided by Google from data collection by Street Cars or by Location Services on Android phones.
iolinux333 said:
is there really a compass in this thing? I just assumed there wasn't. if there is I'm buying another tomorrow!
Click to expand...
Click to collapse
....no
khaytsus said:
Wifi location services provided by Google from data collection by Street Cars or by Location Services on Android phones.
....no
Click to expand...
Click to collapse
Oh well, it could be worse although I don't see how Google data can tell which direction I am facing.
Thanks dad!
Awats said:
Oh well, it could be worse although I don't see how Google data can tell which direction I am facing.
Thanks dad!
Click to expand...
Click to collapse
Nor can your Nook Colour.. Using something like TetherGPS would have some heading information, but the NC itself without help would not.
It might show 0, dunno there. Maps for me just shows a dot, if yours is showing different, that'd be... interesting.
For S&G I tried "Compass", it of course FC's immediately like almost all apps that try to use the GPS. Enabled TetherGPS (with no server, just the client) and it ran, but of course no data, no heading, etc.
Is this occuring when the nook is plugged in? sometimes the charger can cause phatom touches with the touchscreen. Cleaning the screen and being on a stable ROM usually gets rid of that problem.
If only I weren't so stupid ...
khaytsus said:
Nor can your Nook Colour.. Using something like TetherGPS would have some heading information, but the NC itself without help would not.
It might show 0, dunno there. Maps for me just shows a dot, if yours is showing different, that'd be... interesting.
For S&G I tried "Compass", it of course FC's immediately like almost all apps that try to use the GPS. Enabled TetherGPS (with no server, just the client) and it ran, but of course no data, no heading, etc.
Click to expand...
Click to collapse
LOL! Ok, I sat down with it and played for a bit. It appears some tilt sensor is handling the up and down tilt. If you raise the screen over your head, it shows those stars and if you tilt it down, I see what is below the horizon. That is pretty consistent. But it's also "simulating" a compass inadvertently.
By that I mean that if I happen to turn it on facing north, it appears to track as you turn in a circle but it's really just me tilting it and it's rotating he view. If you do it enough it has no clue the direction it's facing.
I'm just glad I figured this out before I got lost in the Amazon.
Just got mine plugged it in and unplugged and within stew minutes phantom touches couldn't even reboot it im on cyanogen mod 7
Sent from my SCH-I500 using XDA Premium App
Nook Screen Recalibrate
You guys can try my app from the market
assid2 said:
You guys can try my app from the market
Click to expand...
Click to collapse
Wow, it seems to have improved the accuracy! I need to play with it more to be sure.
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
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...
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?