Hello.
I'm using my nexus for a couple of months now (device is assembled in november 2013), and there are two issues that really bother.
First of all, response of touchscreen is not always correct: it sometimes misses some touches (press the letter on a keyboard, for example - and nothing happens until 3-4-5th touch) or handles single touch like multitouch (scrolling through the page in browser with one finger suddenly acts like two-finger gesture). It usually happens on the top half of the display and while tablet lies on flat surface, but not always: I have noticed same behavior in hands. There are no exact circumstances that show that bug always and for sure, but it appears once a day or two. Today, though, it didn't respond to touches at top half at all, and when I ran a multitouch test, I saw this: http://youtu.be/XwEDCwUZ8h8
The other thing is upper loudspeaker. While it is on, a weird high-frequency sound is present. I can not describe it exactly, but I have recorded an example: https://dl.dropboxusercontent.com/u/71375852/%D0%B7%D0%B2%D1%83%D0%BA1.mov In fact, it is louder: I can hear it from a distance of 10-15 centimetre, and it is even louder if device is charging. But verdict of service-centre said, that this is a software issue, manufacturer is awared and will fix in oncoming ROMs.
So the questions are:
1) How common are these problems? Are there any fixes yet? Are the any people who had a replacement or moneyback because of the issues?
2) Are there any official feedback from Asus or services that recognise these issues as hardware fault which requires a repair or replacement?
As I said, my service-centre did not confirmed the sound issue as hardware issue and they also did not notice the touchscreen bug. But the device still had a 20 days repair: the battery was replaced because of unstable work. According to our laws, I need 10 more days of repairs to get a replacement of the device or have the money back. But there should be exactly a repair of a fault which is covered by warranty: it won't work if after 10 days service will just return the device, saying it had worked properly. So any information about these issues would be really appreciated.
Thanks for any responce.
Related
Hi
I upgraded to my new DHD less than 3 weeks ago. It is not rooted and I did the recent OTA update over Christmas.
Over the last couple of days I have started to experience difficulty unlocking the device on the slide-to-unlock screen. The problem seems intermittent - somethimes it will unlock fine, and other times the slider just seems to "get stuck" at the bottom of the screen.
At first I thought this a bug or something, but after some investigation I am concerned there is a problem with the digitiser. I opened a picture and zoomed in to fill the screen and tested the touchscreen in different places by sliding the picture around. What I found was that the bottom 1cm of the screen above the keys does not respond properly to Up and Down swipes. It is fine however with side-to-side and also individual taps. This is obviously a problem when trying to move the unlock slider!
I've had a screen protector on for about a week - I don't imagine this has caused the issue but haven't removed it to test as yet as I don't have a spare. Aside from this, the device has been very well looked after, definitely no bumps etc and kept in an HTC leather pouch.
Any ideas? Should I return it to CW?
Thanks
OK, I seem to have resolved this for the time being but expect the problem to return.
I downloaded a screen test app that allows you to draw on the screen and got some very strange results. A 1cm band of screen about 1cm up from the bottom was completely unresponsive. Trying to draw a horizontal line within this band would result in lines being drawn either above or below it, or strange vertical lines "jumping" around. The rest of the screen was fine. I realised this is why I have been struggling to close the keyboard - the button is placed within this band and trying to press it would result in on of the buttons above or below being pressed. Also have had problems with the sapce bar.
I did a restart (not fast) and this has resolved the issue, however I expect it may return as I did a restart only yesterday.
At least it is obviously software and not the digitiser....
Hi again. As expected, the issue returned after a couple of hours. This time however, restarting is not making a difference.
I resorted to a hard rest, which has not changed anything either.
Any help/ideas would really be appreciated...
Best to return it for repairs or exchange. Seems like the digitiser is faulty.
Sent from my Desire HD using XDA App
olivierlee said:
Best to return it for repairs or exchange. Seems like the digitiser is faulty.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
I agree, this definitely sounds like a hardware problem.
Does anyone else have weird touchscreen issues when charging their device? It only happens after you charge your device. You're gone for a few hours and when you come back to unlock the device, the screen is not responsive (the lockscreen for example rubber bands back). Sometimes, the capacitive buttons don't work. So far, locking and unlocking the device fixes the issue.
I'll just like to know if it's a general problem or a problem specific to my S II that may warrant an exchange.
Happy holidays all
-steven
edit: Doh, I should have used better search terms like separating touchscreen into 2 words. Found similar problems that way. It appears to be an issue with the included charger and not the device itself:
http://forum.xda-developers.com/showthread.php?t=1333258&highlight=charging+touch+screen
My Desire Z had a fall, and has developed two problems
1 - The hardware keypad has started to take hard-press and sometimes prints double characters on single press. I think the alignment is out or something... any other guess ?
2 - The touch screen sometimes stops working from an inch up from the bottom and continues to half an inch. Before and after that patch, the touch always works fine . Mostly, the whole touch screen works fine. But when the patch gets non-responsive, I have observed that by turning the screen off and on a couple of times makes it work again. I am not very sure what the problem is. Any clues ?
Thanks
I'm also experiencing a similar issue - for me it's usually an area that corresponds to the top row of the
on-screen keypad (for unlocking) or the top of the area for unlock patterns (portrait orientation).
Mine is a 2 year old DZ w. Cyanogenmod 7.1
No HW key problems & no droppage.
Liberal application of isopropyl alcohol and a microfiber cloth - especially around the edges of the screen
seem to help a little bit but not often enough to be better than random.
Switching the screen off and on occasionally helps but most often I get annoyed and use the HW keys to
unlock.
I have noticed that, after powering on the device, the SIM-lock keypad works just fine but the (different)
screen-unlock keypad fails. This leads me to believe it to be a software issue.
/b
I have had this experience on my G2
No fix for me but his my experience check out the url!
http://forum.xda-developers.com/showthread.php?p=31264095
Sent from my HTC Vision using xda premium
Thread moved to Q & A section.
So i am going for Digitizer replacement will post the result when the phone is back.
And what about the Keypad taking hardpresses ? what can be the issue there ?
so my desire z is in the shop for repairs. lets see what problem is diagnosed.
I have read in another thread in this forum that the hardware keyboard (need to press hard on some buttons) issue can happen when the phone falls.
Apparently, the flat cable that connects the keyboard to the rest of the phone gets loose and causes such trouble.
Since your phone is in for repair, I'm sure this will get sorted when U get it back.
ok so my phone got back from repairs, the guy couldnt fix the touch-screen rather made it worse. Now the touchscreen doesnt work at all. So i cant unlock the phone and cannot test the Keyboard problem. The guy said the touch problem is related to the ribbon cable and not the touchscreen itself.
Note 1: He says he tried replacing the touch panel altogether but it didnt work.
Note 2: I still think the ribbon is fine (call it intuition)
Note 3: I am giving my phone for repairs again, but this time to HTC service center which would probably cost me a lot more than third-party repairs but at least it will get fixed.
I will update when I my phone back from HTC service center.
Could you not unlock the phone by opening the keyboard ?
It does smell to be an issue with flat (ribbon) cable to me as well. As if there was some loose contact before (caused by you dropping it), and after the repair guy took the phone apart, he probably made even bigger mess by ruining the flat cable completely.
From my experience (and I've claimed warranty 3x for the broken digitizer (touch panel)), if it's broken, an area of the screen (or the whole screen) will be permanently dead. It would not come back to life every now and then.
btw, mine always started being unresponsive in the very middle of the screen, a bar of height around 1 cm (somewhat less than 1/2 inch). Each time they replaced the digitizer.
If it;s the flat cable, you shouldn't end up being charged too much - those thingies are very cheap (in China) and the labour will probably be the majority of the price. Fingers crossed.
So I got my phone back again... The HTC repair center was not located in my city so I went to another (better known) repair shop. The guy said, "your phone hasnt been opened at all from the touchscreen side, any *repair guy* who claims he has opened it and tried this and that but couldnt fix is simply lying. This said, he opened up my desire z replaced its Touch Panel and voilah! my desire z is sensing again in 15 mins
What's the status for the keypad and need to press it hard to work ?
nope... I had it cleaned using alcohol / thinner. now it works fine.
So, I updated to CM 7.2 last night but the touchscreen problems are still there.
Updated using CWM and deleted data & cache whilst doing so.
I really hate the prospect of getting a new phone as the current models available
in DK are all without physical keyboards
I got my G3 about a week ago and have been thoroughly enjoying it, however in the last couple of days I've been having a recurring intermittent issue with the touchscreen.
Essentially what's been happening is when the phone's gotten a bit warm the touchscreen stops registering long presses or swipes properly, and adds random break points in the swipe, this is especially annoying when trying to use the continuous input on the keyboard or add widgets.
Obviously the phone's still under warranty, so I'll return it if need be, but I was wondering if anyone else was having this issues or had any theories.
Thanks for your time.
the lg g3 is on top 3 list this fall and I did read about some of the heating problems
but based on your comments and the fact it is under warranty, I would replace it at your earliest convenience--:good:
I have to admit I have had nearly the same issue. My phone has been perfect everywhere except when it gets hot from a highly demanding game (demanding in the CPU Heat generation sense, games as simple as Angry Birds Epic cause it to get hot) and once it does, it gets to a point the touchscreen become much more erratic and less consistent on detecting taps, swipes, and holds. This digs badly into games since everything has onscreen controls and when the touchscreen looses its ability to detect touches, then all bets are off until the device cools down a bit.
It is not overly hot or uncomfortable to hold. The phone feels rather warm but otherwise everything looks and runs fine, just the touch input goes to crap for a few seconds then comes back. Has anyone else experienced this under a heavy load?
Have you resolved your issue?
ianpf said:
I got my G3 about a week ago and have been thoroughly enjoying it, however in the last couple of days I've been having a recurring intermittent issue with the touchscreen.
Essentially what's been happening is when the phone's gotten a bit warm the touchscreen stops registering long presses or swipes properly, and adds random break points in the swipe, this is especially annoying when trying to use the continuous input on the keyboard or add widgets.
Obviously the phone's still under warranty, so I'll return it if need be, but I was wondering if anyone else was having this issues or had any theories.
Thanks for your time.
Click to expand...
Click to collapse
I've been having a similar issue with my LG G3. I'm very pleased with the phone's overall performance but it has this touchscreen issue that's really affecting how I can use it. It has a great proc and gaming capabilities but I can't play some games because I can't rely upon the screen to register presses every time.
Have you been able to solve your issue? If so, what did you do?
Fellow Pixel-ers,
So, I broke my screen about 8 months ago. It had coverage and got it replaced by a Google authorized screen fixer place.
I noticed early on that things didn't seem quite right. If I pushed down too hard on the screen, my touch wouldn't register. But, it didn't happen too often and I didn't want to have to deal with arguing that they may have poorly installed the new screen/digitizer and that it wasn't 'my fault'.
As time went on I started noticing that the almost bottom of my screen would not register a touch but mostly only at night. Again, it didn't happen too often and it usually went away after a little poking/prodding/pushing/.
I also thought it might be an application that I gave 'screen Overlay' rights that I shouldn't have and it was causing issues.
I validated my issue by using a Touchscreen Test app.
When I use an app like Vysor I am able to 'access' that area of the screen even when my fingers cannot. Does that validate this is a hardware issue?
The area affected was definitely more than just a few pixels (see screenshots).
More recently it was happening more frequently (not just at night) and it almost never goes away.
I wanted to make sure it wasn't a software issue. So I planned on dirty flashing my OS (AquariOS), but actually ended up accidentally upgrading to a clean version of Android 10. Unfortunately, the issue was still there.
I then did a clean flash and downgraded back to Pie w/AquariOS.
Shortly after getting back up the issue showed up again.
At this point, I have virtually lost all touch response for the bottom 1/8 (not quite the very bottom) of my screen. I've had to use a floating keyboard because the space bar falls right in that area. Sometimes I can't click 'next' or 'continue' in apps or web sites.
Has anyone ever experienced this very odd digitizer issue like this? Any thoughts/suggestions/ideas.
I'm guessing the only solution is a new phone as it is not worth the money to fix it.
So now I'm just waiting for either the Pixel 4A or 5 to come out so I can get a new phone I guess.
I just find this very odd how specific this area of 'dead pixels' is. I always thought it was more random than a specific rectangle.
I look forward to hearing from anyone.
A (not working with a full screen) Bug
I've faced the same issue mate....
a_bug said:
Fellow Pixel-ers,
So, I broke my screen about 8 months ago. It had coverage and got it replaced by a Google authorized screen fixer place.
I noticed early on that things didn't seem quite right. If I pushed down too hard on the screen, my touch wouldn't register. But, it didn't happen too often and I didn't want to have to deal with arguing that they may have poorly installed the new screen/digitizer and that it wasn't 'my fault'.
As time went on I started noticing that the almost bottom of my screen would not register a touch but mostly only at night. Again, it didn't happen too often and it usually went away after a little poking/prodding/pushing/.
I also thought it might be an application that I gave 'screen Overlay' rights that I shouldn't have and it was causing issues.
I validated my issue by using a Touchscreen Test app.
When I use an app like Vysor I am able to 'access' that area of the screen even when my fingers cannot. Does that validate this is a hardware issue?
The area affected was definitely more than just a few pixels (see screenshots).
More recently it was happening more frequently (not just at night) and it almost never goes away.
I wanted to make sure it wasn't a software issue. So I planned on dirty flashing my OS (AquariOS), but actually ended up accidentally upgrading to a clean version of Android 10. Unfortunately, the issue was still there.
I then did a clean flash and downgraded back to Pie w/AquariOS.
Shortly after getting back up the issue showed up again.
At this point, I have virtually lost all touch response for the bottom 1/8 (not quite the very bottom) of my screen. I've had to use a floating keyboard because the space bar falls right in that area. Sometimes I can't click 'next' or 'continue' in apps or web sites.
Has anyone ever experienced this very odd digitizer issue like this? Any thoughts/suggestions/ideas.
I'm guessing the only solution is a new phone as it is not worth the money to fix it.
So now I'm just waiting for either the Pixel 4A or 5 to come out so I can get a new phone I guess.
I just find this very odd how specific this area of 'dead pixels' is. I always thought it was more random than a specific rectangle.
I look forward to hearing from anyone.
A (not working with a full screen) Bug
Click to expand...
Click to collapse
Hi bro, I've face the exact same issue, but for me it was at the center of the screen. Luckily my phone was under warranty, but getting them to replace my touch digitizer was a whole different thing. At first they just didn't acknowledge the issue, then I tried showing them proofs but they didn't believe as they were from some third party apps. Finally, I used markup to show them the issue and recorded it took some screenshots as well. So, they replaced my digitizer at last after constantly speaking them for 2-3 weeks. I can only suggest you that if your phone is still under warranty or you have accidental damage coverage, ask them to replace them. Otherwise, it'll be better to buy a new phone as replacing the screen from your pocket may be very costly.
For anyone who reads this thread,
I resigned myself to having a bad digitizer but was starting to look to replace the phone. Then about a week later I inadvertently dropped the phone in a pool. Unfortunately, as the screen had been replaced the waterproofing was no longer good and phone was a brick. So I never resolved the issue but will always assume that the company that replaced the screen did a less perfect job and that when a screen is replace the phone looses it's waterproofing ability
-A (new Pixel 3XL owning) Bug