Perfecting the One - progress of fixes - One (M7) General

Initial releases almost ALWAYS flesh out some build issues that quickly get fixed (even Apples, but not so often), so hopefully the title says it all. Since we already have seen a few issues with the initial builds, such as camera sensor quality, case gaps, dead pixels, etc., maybe this thread will be a good place to keep watch on the progress of the HTC One issues being remedied, as many of us wait for HTC to perfect the One before we make our order. We don't want to get stuck with hardware issues that may be quickly remedied after initial release.
So you early adopters can help the lurking masses who are anxiously waiting for the right time to buy. Once we have a lot of people reporting what is or isn't good, we can then get an idea of when issues are not really issues anymore.
Please list any hardware issues you have noticed (software too, but no so important since software can be fixed after purchase), and/or list any fixes to these issues or opinions on whether these have become non-issues, so that many of us who are waiting can check the problems off our lists. If there are ways of identifying which hardware versions have the problems vs. which ones do not, that would be great info for this thread as well so that we can check a device in the store or quickly return a device before committing to a purchase.
Hardware issues:
-- Camera sensor yielding image issues such as mis-focus and/or color banding in a small percentage of units, partly due to a HUGE number of image sensor being rejected and causing initial release delays.
-- Gaps is the seams of the case materials such that the unibody design doesn't seem so smooth and seamless.
-- Stuck display pixels or observable differences in displays on a small percentage of sold units, possibly due to HTC using more than a single screen manufacturer.
-- Is black anodize hard enough that resistance to scratching and chipping is on par with other brands out there?
-- Signal reception issues
Software/driver issues:
-- GPU tests not scoring as expected, in comparison to similar phones currently coming out.
-- Volume level adjustability more granular in the low volume end.
-- Capacitive buttons not responding when they should.
-- Battery Drain issues
-- Acceptable menu button solution / HTC logo touch digitizer mapped to become a button (not necessary, but would love to see developers make this happen!)

gruuvin said:
Initial releases almost ALWAYS flesh out some build issues that quickly get fixed (even Apples, but not so often), so hopefully the title says it all. Since we already have seen a few issues with the initial builds, such as camera sensor quality, case gaps, dead pixels, etc., maybe this thread will be a good place to keep watch on the progress of the HTC One issues being remedied, as many of us wait for HTC to perfect the One before we make our order. We don't want to get stuck with hardware issues that may be quickly remedied after initial release.
So you early adopters can help the lurking masses who are anxiously waiting for the right time to buy. Once we have a lot of people reporting what is or isn't good, we can then get an idea of when issues are not really issues anymore.
Please list any hardware issues you have noticed (software too, but no so important since software can be fixed after purchase), and/or list any fixes to these issues or opinions on whether these have become non-issues, so that many of us who are waiting can check the problems off our lists. If there are ways of identifying which hardware versions have the problems vs. which ones do not, that would be great info for this thread as well so that we can check a device in the store or quickly return a device before committing to a purchase.
I'll start it off. So far hardware issues to look out for:
- Camera sensor yielding image issues such as mis-focus and/or color banding in a small percentage of units, partly due to a HUGE number of image sensor being rejected and causing initial release delays.
- Gaps is the seams of the case materials such that the unibody design doesn't seem so smooth and seamless.
- Stuck display pixels or observable differences in displays on a small percentage of sold units, possibly due to HTC using more than a single screen manufacturer.
- Is black anodize hard enough that resistance to scratching and chipping is on par with other brands out there?
And possible software/driver issues with:
- GPU not testing where expected, in comparison to similar phones currently coming out.
- Volume level adjustability more granular in the low volume end.
- Acceptable menu button solution / HTC logo touch digitizer mapped to become a button (not necessary, but would love to see developers make this happen!)
Click to expand...
Click to collapse
The sometimes-not responding capacitive buttons which are most likely a software issue.

Also:
-Fix the color temperature of the screen, it's too much on the cooler side
-Fix the audio hissing in some 1080p videos made in a quiet environment
-Sense drains too much battery in stand-by
-Improve 4G/LTE signal reception
-'msm_hsic_host' wake lock keeps the phone awake on stand-by and drains battery

darkgoon3r96 said:
The sometimes-not responding capacitive buttons which are most likely a software issue.
Click to expand...
Click to collapse
I get this aswell...
Also, whether its me or not but sometimes im on the phone and it randomly turns on speaker phone.... Going to wait n see how this one pans out tbh. It might be me touching it with my ear.

Xperia23 said:
I get this aswell...
Also, whether its me or not but sometimes im on the phone and it randomly turns on speaker phone.... Going to wait n see how this one pans out tbh. It might be me touching it with my ear.
Click to expand...
Click to collapse
If it is you touching it with your ear, then that is still a problem, as the proximity sensor should sense that the phone is close to your head and then shutdown the screen and touch sensor input so that touching the screen does nothing.

Maybe u could add links for each of the problems to related threads so users can get more info?
Sent from my Desire HD using xda premium

I just checked out the one at a nearby at&t store. I had such a hard time with the capacitve buttons that I am reconsidering the phone. Not once did I get them to work on my first touch. Extremely disappointed. Hoping it was that one model in that store. Will check out another store. Also looking at xperia zl as an alternative now. So disappointed though as it was pretty awesome looking and extremely light.
Sent from my SPH-L710 using xda app-developers app

gruuvin said:
- Acceptable menu button solution / HTC logo touch digitizer mapped to become a button (not necessary, but would love to see developers make this happen!)
Click to expand...
Click to collapse
My biggest issue with the lack of menu button is that I've always used it to quickly pull up the address bar on my browser. If you gently scroll up or down on the browser it will pull it up, but it doesn't always work very well. That is what I would like to see a solution to, first and foremost.

The home and back buttons are not very sensitive and don't always react on my first attempt. Also the battery is draining extremely quick. I'm losing 12% per hour.
Sent from my HTCONE using xda app-developers app

There's a fix for the capacitive buttons. Someone found a sensitivity setting.
Sent from my Nexus 7 using xda app-developers app

Element515 said:
There's a fix for the capacitive buttons. Someone found a sensitivity setting.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Care to share the light on this? A link or instructions?

I don't quite remember where I read it... I've been stalking these forums for a while because I really want the phone... If you play around in your settings, somewhere there's an option to adjust/calibrate the sensitivity. Then, if you just very lightly touch the buttons, it will calibrate to that sensitivity and then fixed!

gruuvin said:
-- Acceptable menu button solution / HTC logo touch digitizer mapped to become a button (not necessary, but would love to see developers make this happen!)
Click to expand...
Click to collapse

Does the hardware support this? As there might not be touch sensor on the logo... :/

Pr20 said:
I just checked out the one at a nearby at&t store. I had such a hard time with the capacitve buttons that I am reconsidering the phone. Not once did I get them to work on my first touch. Extremely disappointed. Hoping it was that one model in that store. Will check out another store. Also looking at xperia zl as an alternative now. So disappointed though as it was pretty awesome looking and extremely light.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
So I went and checked it out at another store and there was no problem with sensitivity. It had a weird problem where home would just bring up whatever screen you are on. Must be particular to that phone. Either way the sensitivity of the buttons was totally fine which was the main issue.
Also liked at xperia zl which is a fine phone in its own right but it just does not compare to the one. Although it does have one advantage which is that it is much easier to hack and get aosp and also get klp when it comes out.
Sent from my SPH-L710 using xda app-developers app

Element515 said:
I don't quite remember where I read it... I've been stalking these forums for a while because I really want the phone... If you play around in your settings, somewhere there's an option to adjust/calibrate the sensitivity. Then, if you just very lightly touch the buttons, it will calibrate to that sensitivity and then fixed!
Click to expand...
Click to collapse
I think this is the thread.
Solution to irresponsive back/home key

Case pitted
Got my 64bg on the 19th via mail direct order ATT. Top of aluminum case near power button front side chamfered edge had 2 pitted dents. Put back in box and immediately went to ATT store to return for new order replacement. I also noticed some rough finish in edges of aluminum casing where it meets plastic fill. Not at the level of my Iphone 5 fit and finish. Will see what replacement looks like in the next few days once received.

I'm glad I'm not the only one who feels the need to stab the hell out of the capacitive buttons when it comes time to go "home" or "back."
One of the few things that has agitated me about this phone is the effort required to press the back and home buttons. I actually began wondering if they were pressure-sensitive or something. After all, my Note 2 would often register inadvertent presses of the back and menu capacitive buttons because they were so sensitive. With the Nexus 4, the buttons are responsive, if not hypersensitive.

I have just set my calibration and the home /back buttons are immediately more sensitive.

omar302 said:
I think this is the thread.
Solution to irresponsive back/home key
Click to expand...
Click to collapse
Worked for me, thanks
Sent from my HTCONE using Tapatalk 2

g2525 said:

Does the hardware support this? As there might not be touch sensor on the logo... :/
Click to expand...
Click to collapse
Consensus is: yes, the hardware might support it, while software currently does not.
The sensor array likely completely covers a rectangular area but the coded area does not include the logo area. This might be hackable at the kernel layer.

Related

Touch screen w/o touching?

I've noticed that on my NS, I don't have to actually touch the screen to tap keys. I can keep my finger slightly hovering over the glass and it still recognizes my input. Sometimes it actually causes me to mistype at a higher rate than other phones.
Are you guys seeing this too?
Sent from my Nexus S using XDA App
Glad to see I'm not the only one who's experienced this....I thought I was going crazy. It's sporadic at best, but when it happens it is annoying. I can't say for sure what causes it, but I'd love to hear other people's opinions.
I've been getting this as well.
same here. Guess they have the capacitance set a bit too high.....
yup, me too. infact. my home button gets phatom long pressed and the light is off on it...have to power it off/ turn the screen off and on muliple times. that insanity has occured about 4 times thought.
Thanks for the replies. I went back into Best Buy and tried their demo phone. So either it's supposed to be this way or they messed up a whole batch of phones. I wish I could remember whether the vibrant did this or not, but it's not standing out.
Sometimes touchscreen nonresponsive too. This is not relating to partial outer border touching either.
Sent from my Nexus S using XDA App
kjy112 said:
Sometimes touchscreen nonresponsive too. This is not relating to partial outer border touching either.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I believe Engadget did mention did this during their review @ http://www.engadget.com/2010/12/10/nexus-s-review/.
Their exact quote: "One other thing of note -- we noticed a few missed or latent presses on the touchscreen which occasionally led to stuttery behavior or an opened item that we didn't mean to tap. It's hard to say if this was a software or hardware issue (and we know that sometimes Android devices can be particularly finicky when syncing). It wasn't a deal-breaker by any means, but we saw the issue rear its head a handful of times, and felt it was worth mentioning."
it's nothing ,, the Samsung galaxy S does that too D:
that happens due to the static on your finger.
Hi
I opened a thread (http://forum.xda-developers.com/showthread.php?t=879872) because I definitely have a problem on the back capacitive button, just wondering how many people are affected?
In fact I have seen this in four devices now, it looks that there is a batch of defective Nexus S phones out there affected by this problem?
It's normal. My Nexus One is like that too. It's magic.
So, it is normal to have un-responsive back button after some times?
Damn ... this is bad. I hope I can cope with it. I really hate hardware problem.
And still could not understand why Google cannot fix it.
Last time from HTC ...
And now from Samsung ...
*Still waiting Nexus S from UK*
nxt said:
It's normal. My Nexus One is like that too. It's magic.
Click to expand...
Click to collapse
gogol said:
So, it is normal to have un-responsive back button after some times?
Damn ... this is bad. I hope I can cope with it. I really hate hardware problem.
And still could not understand why Google cannot fix it.
Last time from HTC ...
And now from Samsung ...
*Still waiting Nexus S from UK*
Click to expand...
Click to collapse
There's a thread for the back button, that's a real issue. Some people have the Back button issue, some the Home button issue. Both of those buttons are on the outer edge of the phone, so something may be messed up when the phone was being assembled.

KF Touchscreen Sensitivity Issues

Hello everyone,
I have been playing with my Kindle Fire, since I got it, and I am about ready to chuck it out the window, or just call Amazon for a new one, but I first wanted to see if you guys had any suggestions. My touchscreen is oversensitive. WAY oversensitive. Oversensitive to the point that if I have to type anything into the keybaord, I will be three letters in, the keyboard will close, and I will have to start over. So sensitive/messed up that when scrolling an article in landscape mode, using only my left hand to scroll, random links will click on the right side of the page. The opposite happens if I do it with my right hand. I like the device, and look forward to rooting it, and ICS goodness eventually, but I wanted to know I have a dud and need to return it, or if there is some hidden setting somewhere or what. I am open to trying anything. Side note: I also own a thunderbolt, and find its touchscreen too sensitive, but nowhere NEAR the KF. I am making sure to make deliberate presses and swypes, and trying to make sure no extraneous part of my hand interferes at all. (sometimes even using one hand to poke at the keyboard with the device sitting on the table will still produce the problems.)
Thanks for the help!
Brock
Hey Brock!
I've noticed that my screen is a little more sensitive than my epic 4g but not to the extreme you are talking about.
Perhaps your screen is bugged or something try calling amazon and see what they say.
Also as a side note try rubbing your hands over the screen smudge it up pretty good. Does that make a difference? I know it will look ugly but maybe there was a film or something on the screen. Just to test
*forgive any grammar or spelling mistakes I injured my right hand and it is hard to type with bandages *
Hi
I have a bunch of problems too. Mine is sensitive, and its sometimes a problem not overscroll, but yours seem to be extreme.
As a way out, if you have time drop by a BestB** and try it there, if yours is the same, not to much left to do....
I've been using mine all day and I don't even need to touch the screen. If I get my finger really close to the screen it reads as a touch. I'd say that's a tad too sensitive.
Sent from my HTC Sensation Z710e using XDA App
johnsmith970 said:
I've been using mine all day and I don't even need to touch the screen. If I get my finger really close to the screen it reads as a touch. I'd say that's a tad too sensitive.
Sent from my HTC Sensation Z710e using XDA App
Click to expand...
Click to collapse
They are all like that. Its because the touch screen is capacitive. My Screen at work does that.
I'm having the opposite problem...I'm finding the touchscreen not sensitive enough....
The Dreamer
TheDreamer68 said:
I'm having the opposite problem...I'm finding the touchscreen not sensitive enough....
The Dreamer
Click to expand...
Click to collapse
Same here. I have to sometimes tap things a couple of times to register...
TheDreamer68 said:
I'm having the opposite problem...I'm finding the touchscreen not sensitive enough....
The Dreamer
Click to expand...
Click to collapse
Same here, I feel like I have to push the screen really hard to get it to register. I hit the screen lightly and it does not register my touch. I'm used to my EVO 4g, maybe it is just a lot more sensitive than the fire.
TheDreamer68 said:
I'm having the opposite problem...I'm finding the touchscreen not sensitive enough....
The Dreamer
Click to expand...
Click to collapse
Same problem here.
TheDreamer68 said:
I'm having the opposite problem...I'm finding the touchscreen not sensitive enough....
The Dreamer
Click to expand...
Click to collapse
Same here, but it's not as simple as it not registering the touch. Most times the button will animate to show I've touched it but nothing happens. It happens most often with the back button, but happens in the browser and some other apps occasionally. I've had some luck with slower more deliberate taps, but it seems like a software bug to me.
Sent from my Kindle Fire
I was using my mom's so I could teach her how to use it, and see if I wanted one. Her was also not sensitive enough many times. It wasn't just that I am used to my Droid 2 because my mom who never used a touch screen before had the same issues. Sometimes it would take 3 or 4 taps to make it work. I just thought it was a bug that would be fixed. It was minor. I ordered my one, so on Tuesday I will see how mine is.
OP I say contact tech support immediately.
My screen is fine, the only problem I'm having is the menu gets pressed, it shows that it was pressed but nothing happens
Sent from my Kindle Fire using Tapatalk
The two kindle fires I've used have the same touchscreen issue: there is a jerk (along the longest direction of the screen) on touch down. Once the finger is down the reported position is fairly stable, but the initial touch down needs to be smoothed out (or the first few samples from the touch screen should be thrown out).
This causes most of the issues I've seen on mine, where pressing buttons is either inaccurate or they go down and come up without activating (because the touchscreen reported a touch down inside the button and then jerked out of the button area and reported a touch up).
I've spent way too much time on touchscreen drivers (way too much!) and this is a fairly common electrical issue, and the software workaround is fairly straightforward to implement in the kernel. It's surprising that Amazon shipped the device like this (as well as various SGX drivers issues on some apps), especially as every review mentioned it as an issue!
Anyway, once we can build and flash kernels reliably I'm sure we can fix most of the touchscreen issues.
My kindle too !!!
Because of this, I'm getting very stressed ㅠㅠ
It's a matter of the touch panel... would be fixed by software?
If this is not possible... Then I'll be selling the Kindle
I downloaded an app called ILITEK Touch Utility which appears to have made my touchscreen work better. It is in the Google Market.
TheDreamer68 said:
I'm having the opposite problem...I'm finding the touchscreen not sensitive enough....
The Dreamer
Click to expand...
Click to collapse
Exactly x100
Sent from my Kindle Fire using xda premium
krelvinaz said:
I downloaded an app called ILITEK Touch Utility which appears to have made my touchscreen work better. It is in the Google Market.
Click to expand...
Click to collapse
I'll have to try that out, would be nice to tweak it some Thanks!
mine is not too sensitive, sometimes i have to press multiple times for it to register
Bumping this thread, because this issue is annoying the hell out of me. Those having the touchscreen not being sensitive enough, it's the same issue as those finding it too sensitive. The problem in reality is that it's ridiculously sensitive, and as your finger presses down on the screen, it's sometimes reading that as an attempt to swipe/scroll rather than a tap/press, which is why you see things light up still, but not launch.
This is frustrating me more and more as time goes on. I've tried this, which I can tell adjusts some of these settings but doesn't really make much difference for the problem. I've also tried this, which didn't help any after calibration.
Some people have speculated (or confirmed, for all I know) that this can be adjusted via the kernel. Does anybody know of anything that might help with this? It's so sensitive it's making me want to avoid the damned thing. I'm about ready to restore the stock ROM and give it to my sister as an early Christmas present.
The awesomeness that is Hashcode is working on 3.0 kernel over in the dev section. The kernel is still a work in progress and has come a long way. At the end he is apparantly going to update the touchscreen driver. I hope that will fix any said issues.
Sent from my Amazon Kindle Fire using XDA

What to check on a 2nd hand Nexus S

Hey guys, I'm about to buy a 2nd hand Nexus S from some guy on a local forum and we're going to do the exchange in person. What should I check on the phone before I give him the $$? Any common glitches common to this phone?
For example, I was using the Nexus One before this one, and I know the multitouch screen is wonky for some of the AMOLED models for that one, and the trackball gets dirt in it. Anything like that for the NS? Thanks guys!
rayrayw said:
Hey guys, I'm about to buy a 2nd hand Nexus S from some guy on a local forum and we're going to do the exchange in person. What should I check on the phone before I give him the $$? Any common glitches common to this phone?
For example, I was using the Nexus One before this one, and I know the multitouch screen is wonky for some of the AMOLED models for that one, and the trackball gets dirt in it. Anything like that for the NS? Thanks guys!
Click to expand...
Click to collapse
I would say one of the most important things would to make sure the volume rocker and the power button feel solid. This is the most heard of problem in the nexus s forums. We haven't really experienced problems like burn in but you can check for that by running a full screen app like a game at max brightness.
Good point, the volume rocker on my N1 was starting to act up with age too.
afzalarsalan said:
We haven't really experienced problems like burn in
Click to expand...
Click to collapse
Speak for yourself on that one. The buttons at the bottom got burned into mine from having the display stay on while charging.
burn on screen dont matter if u can see buttons at bottom for search back home ect as there used alot and are off the main screen and volume and power buttons even tho mine are still like new after 2 years if they have gone than there may be more problems elsewhere always play music and volume brightest to see if anything wrong with screen and sound i would play a game
Make sure the signal works. That would be a sign of a stolen phone. Apart from that its the usual of checking scratches, any big dents, making sure the buttons are working ok
My screen is still as nice as when I bought it, but the entire thing is covered in ghost armor. Hate the glossy fat bezel and though. Even cased it shows tiny less shiny scuffs on it though its never been dropped or in anything but silicone and tpu. 99% of people wouldn't even be able to see it, but I'm anal. I went through 8 phones to find a good screen and no glass crease. Foolish when I ended up getting a galaxy nexus just 13 months after paying full price for it from best buy. Buttons all work too after 4+ hours a day of use.
Sent from my Galaxy Nexus using xda premium
Make sure to check for touch sensitivity across the middle and bottom of the screen. I bought a second hand nexus s and didn't recognize the problem until it was too late.
The middle of the screen on my nexus s pretty much doesn't work sometime and starts working after I turn the screen off then on again.
Hope this helps.
Sent using xda app-developers app
1: buttons work
2: call *2 or whatever the cellular company's number is (Sprint will happily verify an ESN if you are buying used)
3: screen
4: is it rooted? (I would rather root myself, so I know it is done right, If I buy used, I buy stock)
5: GPS Signal
Verify SIM connector pins are important too.
Closed, thread here talking about the same issue.
In future search before posting.
Thank you.

[Q] Possible Touchscreen/Multi-Touch issue?

Multitouch Visible Test
With that app, 1-finger touch is alright, no issues.2 Fingers seems alright too. Adding up to 4 fingers seems to be alright and moving them around the screen.
Sometimes with 5 fingers though, they'll all show on the program, and then immediately vanish. If I keep moving my fingers across the screen, they'll pop in and out, but won't actually stay on screen and follow. But this only happens sometimes. Other times, 5-finger input works fine.
My other camera is dead at the moment and I have to run and get batteries for it tomorrow, so I can't actually upload video of what I mean. I was hoping to get some input from other people about how their multi-touch seems to be with that app. Not entirely sure if this is just a rare defect, widespread, or working as intended maybe (not entirely sure if there's anything saying how much multi-touch this screen is; figured it was 10 though)
Some things to try:
- Use 1 finger, drag it all over the screen
- Keep adding fingers 1 by one after dragging them across the screen (add finger, drag it around, add next finger, etc.)
- Don't touch the screen for about 3 seconds, then just have all 5 fingers come in-contact with the screen, and keep them in one spot (on mine most of the time, the points appear then immediately vanish)
Could it just be the app your using?
Try using this one...
Check out "MultiTouch Tester"
https://play.google.com/store/apps/details?id=com.the511plus.MultiTouchTester
See if it does the same thing.
Sent from my SPH-L710 using xda app-developers app
jjdevega said:
Could it just be the app your using?
Try using this one...
Check out "MultiTouch Tester"
https://play.google.com/store/apps/details?id=com.the511plus.MultiTouchTester
See if it does the same thing.
Click to expand...
Click to collapse
Yea it still does the same thing :/ Here's a video:
It could be as simple as compatibility issues with the app...
Sent from my SPH-L710 using xda app-developers app
Called up Google and it doesn't seem to be widespread (or at least the person didn't say it was), and I could get a replacement under warranty. I don't have the funds to put on hold currently so it'll have to wait if I do decide to do it.
Although I wonder if I really should, I mean I highly doubt I'm going to do anything requiring more then 2 fingers on the screen at any point (nor can I really think of anything), and aside from multitouch, everything else seems great. No dead pixels, back doesn't flex, screen is alright quality-wise.
Would be nice if some other people can try out multitouch though just to see if it really might be widespread or not though. The thing is though, it works fine sometimes, and other times it doesn't. Perhaps software might fix it in time, but I don't know. I thought I heard of the Nexus 7 having a similar issue, but I can't recall...
jjdevega said:
It could be as simple as compatibility issues with the app...
Click to expand...
Click to collapse
It seems to do the same even with the "Show touches" option enabled in Developer options (tried it on an empty homescreen).
Bump
Anyone? It only takes a minute or two at the most to test this... and the apps available to do so are free and light.
Doing the tests you described never caused anything on my tablet. But if I put my hand down on the tablet flat then put my five fingers on I get your issue. Then wait three seconds and try again and everything is fine till I put my palm back on.
Might be a badly configured palm detection algorithme? Op, do you have fat fingers? Sorry if that sounds rude
Chluz said:
Might be a badly configured palm detection algorithme? Op, do you have fat fingers? Sorry if that sounds rude
Click to expand...
Click to collapse
Lol, hmm, na I don't think I have fat fingers
How about fruit ninja, does that work properly? It's true that if show touches doesn't work, it's not a good sign. Unless it's a system firmware bug
1 and 2 fingers seems to work great in Fruit Ninja; 3+ randomly works or doesn't work, and when it does work it seems to cut-out at some point and then just show slashes delayed from where my finger is currently
Any idea if its hardware or software related? I have the same issue with my N10 and don't know if I should get a replacement or not.
Got mine today, same issue. Actually, that too bad since everything works fine, and i only got a minimal light bleed. I hope my replacement won't be worst regarding light bleed :/
Same issue on mine. Considering a replacement now with this and wakeup lag + battery issue (indicator not updating % at all!?)
Don't know if I wasn't lucky or just poor QA.
I'm pretty sure it is a software thing because when the problem occurs and I tab on the multitasking button twice (so it shows the multitasking menu and switches back to the app) the touchscreen acts normal again until I put more than three fingers on screen.
But if its a software problem, shouldn't it happen to on every N10 running the same Android version?
I have the same issue. If I slowly add one touch at a time, it usually works. But if I touch down 3+ fingers at once it gets very confused and bounces between zero and N touches. I have a Galaxy Tab 10.1 (first generation) and multitouch seems to work much better on it than the Nexus10. However, I did notice that the Nexus10 is better at distinguishing 2 very close touches than the GTab. On the Nexus10 I can have my fingers as close as 1/2 inch or so before the touches merge. On the GTab it is more like 3/4".
Hmm, kind of interesting to see that others are also having a similar issue.
I noticed that when I tried a custom ROM (latest Kernel sources + 4.2.1), the multitouch seemed to work, slightly better (the issue still occurs, just maybe not as much). Not too sure if it was placebo or what though.
I called the support and will replace mine with a new one. It might be just a software issue thats solved with an update but I don't want to risk it.
just got my replacement today, same issue (and also worst light bleed ). Third replacement on this way...

[Q] Nexus 4 all known hardware issue?

What are all known hardware issue to the nexus 4? Like the rattling sound , some little creaking sound and such.. and does it exist only on very few units? and does anyone here experience screen flickering?
Well I'm on my 4th one now....
1. Screen issues
2. USB connector faulty , and overall construction didn't seam to be sturdy ..
3. Volume and power buttons squeaky
My 4th nexus is fine but not perfect
Sent from my Nexus 4 using xda premium
MattSkeet said:
Well I'm on my 4th one now....
1. Screen issues
2. USB connector faulty , and overall construction didn't seam to be sturdy ..
3. Volume and power buttons squeaky
My 4th nexus is fine but not perfect
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
You have such a special talent that attract broken devices.
Maybe those QA depts can offer you a job.
Proximity sensor and ear piece buzzing while screen off
Sent from my Nexus 4 using xda premium
When I went to Carphone Warehouse to see a Nexus in person I WISH I listened to the guy.
He said LG are know for poor build quality - they get a lot of complaints and returns. He liked the Nexus but didn't think it will be smooth going being a LG phone and said I should wait....
He was right...
My nexus has loose buttons (power button has become loose with use), The side creaks/snaps as if something wasn't put together correctly.
The Sound quality from the mics on videos IS APPALLING !
Rear speaker is tinny, wosre than any phone I have heard TBH.
The camera could be better
The Battery is crap (if you use the features you are supposed to use like Google Now, Location etc)
The WiFi reception pickup is worse than any device I have owned.
The ear-peace has processor noise on it- especially bad when you take a call.
I really don't know what to make of the phone. It has its advantages too but in fairness its just not the golden ticket it was made out to be.
My FFC has dust in it....so many hardware issues.
What are the screen issues? I'm planning on buying this since I don't live in US i would ship it in my country but it looks like I need a warranty for this device maybe a used galaxy s3 better to buy then?
What are the screen issues? I'm planning on buying this since I don't live in US i would ship it in my country but it looks like I need a warranty for this device maybe a used galaxy s3 better to buy then?
Click to expand...
Click to collapse
yellow blobs when you play a game for few minutes (after phone heats up)
screen is generally yellow, this (4th) device is nearly white, previous ones I had to calibrate screen like 225/230/255, my latest is about 255/238/255
You have such a special talent that attract broken devices.
Maybe those QA depts can offer you a job.
Click to expand...
Click to collapse
Trust me I didnt ask for faulty devices, and yes if they would offer me a job none of them would pass if it wasnt perfect.
My 4th device is nearly OK, but there is some creaking and that rubbery frame in some places hase a little "give",
Any device that has any creaking, screen problems, loose parts etc shouldnt go throu QC
MattSkeet said:
Well I'm on my 4th one now....
1. Screen issues
2. USB connector faulty , and overall construction didn't seam to be sturdy ..
3. Volume and power buttons squeaky
My 4th nexus is fine but not perfect
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
You returned it due to squeaky buttons? Really?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Eric-1987 said:
You returned it due to squeaky buttons? Really?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
My £30 2 year old Xbox 360 controller doesnt squeak. Its a brand new £400 device, not used or refurb, there should be no build quality issues. And try using most used buttons on the device when wvery single time you can hear and feel it being not right. Previous device didnt have it so why should I accept that one?
Look at iPhone or Lumia, from build quality view these are perfect devices, and fault ratio is a lot lower than e.g Nexus4.
I had GNexus (3 of them) one had screen issues, second was clicking like this http://www.youtube.com/watch?v=QxGhlnRCneY
after couple of days.... is this acceptable in your opinion?
ichilouch said:
What are all known hardware issue to the nexus 4? Like the rattling sound , some little creaking sound and such.. and does it exist only on very few units? and does anyone here experience screen flickering?
Click to expand...
Click to collapse
Screen freeze when trying to unlock.
For example: Screen is off, wants to unlock phone, turn screen on with power button, screen is on, but doesnt respond to any touch (cant swipe to unlock).
Turn screen off, then turn it back on, now touch is not frozen and unlock is possible.
What batch is it from?
What batch does your current nexus 4 is from? I heard there is some kind of batch the first released ones and the second one is after the sold out?
unfaix said:
Screen freeze when trying to unlock.
For example: Screen is off, wants to unlock phone, turn screen on with power button, screen is on, but doesnt respond to any touch (cant swipe to unlock).
Turn screen off, then turn it back on, now touch is not frozen and unlock is possible.
Click to expand...
Click to collapse
It is not hardware issue...
unfaix said:
Screen freeze when trying to unlock.
For example: Screen is off, wants to unlock phone, turn screen on with power button, screen is on, but doesnt respond to any touch (cant swipe to unlock).
Turn screen off, then turn it back on, now touch is not frozen and unlock is possible.
Click to expand...
Click to collapse
This will propably software issue. ashirviskas overtook me.
I have an issue with a rattling sound coming from the top of the device, it sounds like something is loose or disconnected on the inside. Maybe the headphone jack? Or the earpiece speaker? I wasn't looking for anything wrong with the device, its just that I noticed it when I put my phone down on the table. It sounded broke in some way. I kinda looked at it funny and said to myself, "That isn't right?". So I picked it up and tapped on the phone (lightly) and definatly noticed there is something loose on the inside. Is this a reason for a return. I have had phone for 10 days and this my first time noticing this. I have not dropped, put down hard or, anything of that manner to the phone.
For those that came in here that haven't purchased a N4 yet, let me tell you there are many people, like myself and my wife, who received phones without any of the issues listed above.
People with issues are louder than those of us without, so while it may look like the N4 is riddled with issues...it is not as bad as it sounds in this thread.
We both have 16Gb versions, one ordered in the first batch, and one in the 2nd.
- Neither screen has yellowing of any sorts, even after playing games or watching movies for a period of time.
- Neither has creaks, squeaks, or rattles
- Neither has soft or loose buttons
- Neither has poor speakers (back or ear)
- Neither has had freezing issues on the OS or apps
- Neither has had the screen flicker
- Neither gets abnormally hot during use
- USB and 3.5mm headphone connectors are solid
- Battery lasts all day with typical use (for instance, yesterday while waiting for the Hobbit to start, I was streaming music and browsing the web for just over an hour. During that time the battery dropped 8%. To me, that's pretty damn good) (and yes, I have Google Now turned on, with the unwanted services turned off)
all that said...I'd expect my experience is pretty normal, where as those posing issues were the unlucky ones. Don't let these reviews scare you out of buying a really great device.
So does the 16 gb is enought to you? Do you think it is enough if I plan on installing like only 3 Graphic intense games then 2 to 3 HD movie length videos, productivity apps like a reader for ms word,powerpoint, camera apps, video player and such (but i think those apps does not consume much space?) then a lot of picture but would occasionally (like every 3 months) store them on PC?
my back speaker pops something serious at random times when all the way up but dear god this screen is beautiful
Rattling sound + i dont believe volume buttons will live long .....but haters gonna hate... Still best phone ever had
Sent from my Nexus 7 using xda app-developers app

Categories

Resources