Database Info

GPS is a quality control problem

Hey guys,
I got in my 3rd "refurbished" Captivate last Friday and I have been collecting some data. For the record, I am using Cognition BETA5.5 FROYO on it without any lagfixes or modified GPS settings.
My first two Captivates -- the GPS sucked. I tried every fix in the book: Jupiter.xml fixes, Epic 4G fixes, LbsTestMode settings, different firmwares etc... some things helped a bit, but the GPS was still unreliable.
My 3rd Captivate's GPS works great from day 1. I've been testing it daily since I got it. I had a long trip to the New York Comic Con, which I used my 3rd Captivate to navigate. In areas that I previously had problems with, my new Captivate handles them with ease. I attached a screen shot of "My Tracks" on a turn that the GPS always overshot previously (now which works fine).
Anyway, I believe JH7 was the software fix for the GPS. The software problem was keeping locks from satellites <20dbHz and using >8 satellites. The rest of the problem is hardware due to poor quality control. This would also explain why so many people have so many different experiences. I say, if you want a reliable GPS in a Captivate, keep warranty swapping it until you get one that works.
/this also explains why some Captivates shutdown randomly, while others don't: poor quality control.

I disagree with this. I bought mine a few days before the JH7 update and didn't have a ton of time to play with the GPS. Using GPS test I was finding 8 satellites and locking onto ~6 of them in a minute or so. With the JH7 update I was finding and locking onto 11 satellites in 15 seconds or less consistently. My accuracy would stand at 16.4 feet (I don't think anyone has achieved better than this with this device). Starting this past Friday (10/8) however my phone won't lock at all. I'm only seeing 4 satellites and no matter how long I leave it, or what settings I touch there is no lock. This is a problem many people have. The GPS works for a while then suddenly stops. This to me suggests a software issue.

I think it is partially hardware related as well. My GPS on stock didn't work so well with the factory settings but worked perfectly with the supl.google.com. Every update since then up to Cognition 2.1.6 has worked perfectly every time for me. If this was a software or firmware issue we would all be having similar problems.

If someone proposed the theory that maybe supple.google.com isn't the best source I must have missed it. So I propose it. Spirent obviously is not, that's a test site.
I wonder if there is supple1.google.com supple2.google.com tzpst.supple.google.com etc.

phr00t said:
/this also explains why some Captivates shutdown randomly, while others don't: poor quality control.
Click to expand...
Click to collapse
I agree that Samsung has poor quality control problem, or lack there of from my past experience with various Samsung products. However, I believe the GPS issue is a bad hardware design in Samsung's part. Based on my own observation, it is the poor GPS antenna design that causes poor GPS signal reception. In compensation for this poor design, Samsung tries to boost the GPS chip amplification power which in turn causes interference from all the difference radio sources and bad S/N ratio. Since this is purely an analog signaling issue, different phones show different results and even the same phone could show different results in different environment. I particularly noticed that whenever I pass by those noise isolating walls around the highways I travel daily, my GPS starts to jump all over the place. This indicates to me that the GPS receiver is very suspectible to signal reflections from those walls, may it be cell tower signals or else.
The problem with warranty replacement is that it is really a crap shot. You typically get a refurbished phones unless AT&T runs out of refurbs. Guess where those refurbished phones come from: (1) returns due to GPS issue. (2) returns due to shutdown issue. Since neither issue can be resolved or easily identified (the later is not even acknowleged as a problem AFAIK by AT&T), Samsuung/AT&T will simply refurbish those phones and send out as warranty replacements.

bwolmarans said:
If someone proposed the theory that maybe supple.google.com isn't the best source I must have missed it. So I propose it. Spirent obviously is not, that's a test site.
I wonder if there is supple1.google.com supple2.google.com tzpst.supple.google.com etc.
Click to expand...
Click to collapse
That's BS. spirent is not the problem. The original theory has been proved wrong long time ago. Change to supl.google.com does not solve the problem. Period. And getting a lock is only 1/3 of the GPS trouble you get into.

1) I am using spirent (or whatever the stock SUPL server settings are) and my GPS is working great. The problem is not the SUPL server (although changing it might have helped some).
2) If it were purely a software / firmware issue, we would all be experiencing the same GPS problems, which we are not. In addition, I would see the same problems with my new Captivate (which is running the same software), which I am not.
3) I do not have poor S/N ratios on my phone. I get 25-40 (sometimes better) S/N ratios, which is a bit better than my wife's Aria. I did notice poor S/N ratios on my second phone (15-30), which had the worst GPS performance. If it was poor hardware design, we would all have the same poor S/N ratios (and performance), which we do not.
4) Yes, getting a warranty replacement is a crapshoot. But hey, your current phone sucks and your next refurbished phone might not. So, swap it out -- you might get lucky. Samsung owes you a good phone anyway.
The problem is really chaotic, and people cannot reproduce the same problems (and resolutions) across different devices. This can only explained by people not getting the same devices... some are just more broke than others. Poor quality control.
/personally, I'm sick of digging through the Captivate GPS problem.. now that I have one that works, I want to just enjoy my phone.

phr00t said:
3) I do not have poor S/N ratios on my phone. I get 25-40 (sometimes better) S/N ratios, which is a bit better than my wife's Aria. I did notice poor S/N ratios on my second phone (15-30), which had the worst GPS performance. If it was poor hardware design, we would all have the same poor S/N ratios (and performance), which we do not.
Click to expand...
Click to collapse
You are confusing digital circuitary with analog circuitary.
An analog hardware issue hardly will cause uniformly the same results. What you will see the S/N varies a lot between phones that's why some works, some doesn't. The antenna and satellite signal processing are still analog circuitary and prone to variations even with the same design. That's why SOME iPhone4s work just fine but others will drop calls when touched But no one is calling Apple lack of quality control.
Mine is 20 to 35 which is borderline.
The BroadCOM BCM 4751 is supposedly better at dealing with weak signals. I think Samsung is still experimenting different ways to get better locks in those marginal signal levels without causing the noise interference that in turn destroys the stable locks.

What is the general consensus of the % of owners actually having perceived GPS issues?

Someone please make a DIY on how to fix the damn thing myself... (hardware fix that is)

*Deep breath*
I know my 2cents really wont change this debate at all but ill go ahead and post my experiences with this issue K?
Cappy 1: Gps was just ok. it still worked but on navigation would try to "predict" where i was, jump off the roads and i would say on average i would be 20-50m off roof overhead and 10-20m if i put it directly on my dash where i couldnt see it.. This on average also took about 5 minutes to get a lock from standstill. Replaced for brick issue *incorrect flash being a newb*
cappy 2: Gps seemed to get worse everyday with this phone. mind you change the supl and jupiter tweaks seemed to help just a bit but honestly this one was just not usable. I could get a a lock in 5-10 seconds from a standstill and it would always be 10m accuracy.. so ok, it could help me know where i am immediatly but i cant see me standing in the woods going *deeerp where am i??* This was was replaced for random poweroff issue.
cappy 3: i literally just got this thing 2 hours ago picking up my mail so its fresh as can be guys.. jf6 stock right now. pulled my sim and battery into the phone at the mailbox and immediatly out of curiousity descided to test GPS. in no more than 20 seconds it got a lock of 50m..and then just a few seconds later im 5...5!!!!meters off. My eyes pop out of my head its in my hands at this time so i get ballsy and decide to put it in the lower tray in my car and take a drive. Wow...it just works now. It knew where i was and even told me and showed me a streetview of my destination before i got there...i should note this has NEVER happened i didnt even know it could/would do that :eek.
So my verdict is this. there are sofware tweaks to improve the quality and for some i dont doubt flashing firmware or applying changes has helped...BUT... overall this 3rd cappy is ...it just FEELS like the gps hardware is working right WITH the software. Things could always change with froyo and the the great devs here and if im proved wrong then wow count me impressed. Just dont hold your breath guys
EDIT: just to note exchanging your device is like playing the lottery. although these latest devices seem to have a higher success ratio im noticing. Ill also note i have NEVER exchanged instore but have always used mai to get my new cappy.

Based on the two comments here it sounds like I should try for a 3rd Captivate. Seems like 3rd times the charm. My 1st one GPS didn't work, I didn't run GPS Test or anything. Just know it never locked on me without the AGPS or whatever on. 2nd one same story. I have ran GPS Test on it and I'm lucky if I can get a view of 3 satellites outside in clear sky. It's usually 0 or 1. I've never had a satellite locked on.

all triumph problems are here... do you need to exchange?

GROUND RULES:
Who should keep reading:
Current owners of Triumph or perspective buys who are trying to cut through all the trolls, flame wars, useless and/or misleading information from the (many) other threads, to find out what or if anything was wrong with their phone, how to identify these problems and most importantly, how to make intelligent decisions on whether to return or exchange before the 30 days run out.
Who should stop now and go read a book instead:
People who have (or think they have) perfect phones and feels it’s necessary to defend the Triumph’s honor at any mentioning of a problem. People who believes everybody else is clueless therefore it’s necessary to advertise basic settings changes as cure-alls (i.e. enable “use wireless networks,” it will fix your GPS problems). please give others more credit than that. And last but not least, people who hate the T and thinks it’s just the worst phone ever made… you have no reason to stay here.
Still with me? Good…
I have personally owned two T’s. the first one had several problems that I ended up returning, the second one was much better but not problem free. I also have access to two other T’s owned by friends. Everything I post here are based on facts that I have personally observed, not second-hand info or hear-say.
** GPS problem:
First of all, Google Map does NOT depend on GPS. Being able to see your location on the map means NOTHING when it comes to GPS location. In order to test if you have a GPS problem you have to either use an app like GPS Test or start Google Navigation. All tests should be done outdoors under open sky and while you have a valid data connection (for A-GPS data download). The GPS should lock-in within 2 minutes or less (Google Navigation should start showing your real time location as a blue arrow and start giving you turn by turn instructions).
A few minutes after a gps lock, you should have a location accurate to within 15ft or less. If google nav consistently shows a visible blue circle (of any size) around your current location, then it is unable to give you an accurate location lock, it is a problem.
If you have any problem at all with GPS lock or location accuracy, your phone has a broken GPS. Take it back for an exchange! Do not listen to people saying that you could fix it by running some magical software or do a special gps dance. You are wasting your time. If it wasn’t broken in the first place then you would have no need for those “fixes.” My first phone had an almost unusable GPS, the replacement and both of my friend’s phones have no problem whatsoever. Using GPS Test app, I was able to clearly see how the satellite signal levels were 30-50% lower on the previous T when compared to my OV, while the replacement had levels that are comparable to the OV.
** Data disconnect and/or drop to 1x when GPS is turned on.
I did not notice this behavior on any of the 4 Triumph I tested on. GPS and wireless signal can not interfere with each other, so if this happens consistently and is making data connection unstable or GPS lock problematic then there’s most likely a hardware problem. the phone should be exchanged.
** Screen flicker, white out, color cast:
If your screen ever turns white completely, or has a VERY heavy color cast, the answer is obvious, get it exchanged. meanwhile, all Triumph’s screen have overall “cooler” color when compared to my V. there were slight variations between each phone but as long as it was not extreme (i.e. making white look blue and red look purple) it should not be considered a problem. Just make sure you have removed the top layer screen protector before making a judgement.
slight screen flicker while turning on/off the phone repeatedly might not be worth an exchange for that reason alone. My first phone and one of my friend’s phone had the flickers, while my replacement and the other friend’s phone did not. The slight flicker did not both me or my friends at all.
**screen protectors:
Yes, there are two screen protectors. No, there’s absolutely no reason to keep the top layer. The second layer is very well applied and I doubt it’s meant to be taken off. You will never be able to apply another protector as well as that. If you have screen sensitivity issues, I’d suggest exchanging the phone rather than taking off that second layer of protector. None of the 4 phones I tried had any sensitivity issue with the protector attached. If you had to take it off then your phone has a problem.
** visible touch screen sensor elements:
If you can see “dots” on the screen under normal use, you are seeing the sensor elements embedded in between glass players. You should NOT be able to see them in any way during normal use. Exchange the phone if you do. it was a known LCD panels manufacturing problem on some earlier phones (mostly HTC). None of the Triumph I have seen had that problem.
** Signal level:
All four of the Triumphs had lower signal dbm numbers when compared to my OV. However, with my borderline coverage (-105dbm at home and -110dbm in the office), I had not experienced any drop calls on the T. Data connections were marginal but no worse than the OV. Do not make any decision based on dBm numbers alone. dbm is a relative value and do not mean what a lot of people seemed to think it means. In any case, exchanging the phone is not going to help in any way.
** WIFI disconnect:
I have not run into this with Triumph however, I had similar issue running AOSP rom on my OV while having no problem with other roms. This is likely something caused by the combination of router and phone software. My suggestion would be to try as many different routers as you can also try router settings such as G vs N, WEP vs WPA, hidden vs broadcast… if you have same problem everywhere then by all means try an exchange, I doubt it would help however.
** Touch button in sensitivity:
This happens randomly on all the T I have tested. It is likely a software problem that will not be fixed by exchanging the phone.
** Camera clicking while focusing:
All 4 phones had slight clicking noise while focusing but none had trouble actually gaining a focus. Exchange if you can’t get it to focus at all. the clicking seems to be normal however.
** Camera color cast:
None of the phones I have tried had problem with “green/blue color cast in the middle of the screen” as some have reported. If you have already removed the green screen protector on the camera itself then you probably have a real problem and should exchange the phone. just check your expectations – cell phone cameras have cheap plastic little fish eye lenses. Don’t expect results like your Canon or Nikon.
** phone stops charging while on:
I noticed two things: 1. some micro-usb chargers such as the one that came with OV would at times refuse to charge while the phone was turned on. Unplugging a couple of times may fix it. I haven’t had problem with stock T charger or the charger that came with my BlackBerry. 2. The charger will shut off once the phone temperature reaches 42c. this is most noticeable while in a hot car with phone on the dashboard. This is normal and is the result of an (over)sensitive overcharge protection.
** light leakage around bottom edges:
All the phones I have tired had various degrees of light leakage. It is consistent with problems reported on other versions of the same phone released earlier. the leakage was only visible in relative darkness so personally I did not think it was worth worrying about.
** Mismatched MEID:
To check your phone’s MEID, go to settings-> about phone -> status. The MEID should be an 18 digit number matching the stickers on the box, outside of the battery door and behind the battery on the back of the phone. Both of my phones had mismatched MEID. The phone itself was showing a 17 digit number while the stickers all have 18 digit numbers. an 0 in the middle is missing on the phones. One person (VM rep?) in an earlier thread had said VM was aware that 3,000 phones had this MEID mismatch so it seemed to be a known problem.
Some people have reported trouble using Google Voice on phones with mis-matched MEID. I have not been able to verify that myself.
** software version 38 vs 39:
Both of my Triumphs had version 38 software. the previous one had horrible GPS and some screen flickering while the replacement did not. There were also some obvious software differences between the two phones, despite the same software version. The replacement phone camera default to 5mp, while the previous one default to VGA resolution. The previous phone gallery had four random pictures referencing some Chinese websites (seemed to be leftover web cache). These pictures were in the ROM and did not go away after hard reset. The replacement phone had an empty gallery. One of my friend’s Triumph came with v.39 software which also had some screen flickers.
By itself, the software version did not indicate a good or bad phone. test everything!
The main thing to keep in mind is that there are many reported problems, not all of them were all that crucial. Given the obvious inconsistencies in build quality, it is a real possibility that the exchange would turns out to be much worse than the original phone. you really have to look long and hard at each problem and make an educated decision for yourself. Meanwhile, there’s absolutely no reason to put up with major things like a broken LCD or gps or insensitive touch screen. Take it back to the store!
This list was put together over several days, mostly as notes to myself. So please excuse me if it rambles a bit. Let me know if there’s something else you would like me to check.
Thanks and good luck.

I never even realized the 2 screen protectors but sure enough, they are there. As far as the light issues at the bottom of the screen, I definitely see it on mine as well.

microphone is awful.. sounds like there is tape on it. i checked, there isn't.
Heading to exchange it.

awesome write up. thank you sir

Another issue I just found out Im having is with my bluetooth. I have a Jawbone Icon and the sound seems overloaded. When I connect my older motorola BT headset to it, it works fine. Strange indeed!

My 30 day return period ends this weekend so I have to make a decision. GPS is really the only problem I have, and it is intermittent. I was hoping a software fix would come out so i wouldn't have to worry about exchanging.

As far as my bluetooth issues with the sound overpowering, I actually just bit the bullet and bought the a MOTO BT today to see how it would work. No issues. Fishy...

my biggest problem is that i cant seem to be able to stream music properly in google music. does everyone have this problem or should i exchange?
I even had full bars yesterday, and it was barely sputtering out any music.

crxmax said:
my biggest problem is that i cant seem to be able to stream music properly in google music. does everyone have this problem or should i exchange?
I even had full bars yesterday, and it was barely sputtering out any music.
Click to expand...
Click to collapse
I doubt that is a hardware issue. Probably a result of VM's network. Try running a speed test app and see what kind of speeds you are getting. I prefer "Open Signal."

the speeds i got on all the tests were all drastically different. I say an average of about 350kbs...is that normal?

Possible input lag/ Ghost Touches once again

A few people here and there have been starting to have this problem pop up- including me.
My phone was perfectly fine with absolutely no problems with the touch screen but about three days ago, my phone started acting weird.
At that time, I was running CM 5.1 nightly and then dirty flashed over to the latest. I thought that this was the problem and so I did a clean flash but still the problem was there.
Went back to the original CM nightly that I was previously on and problem is still there.
Tried many different ROMs but the problem is still there..
I can't type out a sentence without my phone failing to register a touch and sometimes registering rapid touches as one - the same problems before Synaptic released a 'fix' for this issue.
At this point, I don't really know what to do but it's aggravating that a phone can't do it's basic tasks such as type.
The phone seems really sluggish when I type - which I haven't encountered before this which slightly leads me to believe that input lag is the crux of the problem however, I can't say for certain.
Can anyone with more expertise help me with this?

Same issue
You_got_owned123 said:
A few people here and there have been starting to have this problem pop up- including me.
My phone was perfectly fine with absolutely no problems with the touch screen but about three days ago, my phone started acting weird.
At that time, I was running CM 5.1 nightly and then dirty flashed over to the latest. I thought that this was the problem and so I did a clean flash but still the problem was there.
Went back to the original CM nightly that I was previously on and problem is still there.
Tried many different ROMs but the problem is still there..
I can't type out a sentence without my phone failing to register a touch and sometimes registering rapid touches as one - the same problems before Synaptic released a 'fix' for this issue.
At this point, I don't really know what to do but it's aggravating that a phone can't do it's basic tasks such as type.
The phone seems really sluggish when I type - which I haven't encountered before this which slightly leads me to believe that input lag is the crux of the problem however, I can't say for certain.
Can anyone with more expertise help me with this?
Click to expand...
Click to collapse
Im having a similar problem. I cant type a single sentence without errors. It doesnt register the touch as well few times. Using a device is so sluggish.. hate it. Tried many roms with clean wipe but without any success. Would be nice if anyone could help with the above issues.

I have similar issues and I don't think it's a software issue - I have never flashed a ROM. I think it's hardware problem, probable the earthing suggested in this post:
http://forum.xda-developers.com/oneplus-one/general/fixing-ghost-touch-grounding-issue-hint-t2951000
There is an app that re-calibrates the touchscreen every time you turn it on, but it doesn't completely solve the problem for me and also prevents unlocking until it has completed, which is annoying. The fact that a re-calibration is needed to even achieve a little stability is consistent with an earthing problem.
If mine gets any worse, and I think it will, I'm going to investigate a warranty claim, but that sounds like a few weeks with no phone, which I can't tolerate.

hi, i'm experiencing the same problems. you can test this when registering 2 touches on the same Y axis (try with anyone of touch test apps).
I think that this is popping out to a lot of people in this moment because of the hot days kicking in. in fact, if your phone is cold (try to put in a fridge for 5 minutes) it will work perfectly, but when it will become hot again in your hands the touch will start to freak out again

What sucks is my phone was perfectly fine a few days ago and we've only had an increase of about 5 deg F over the week.
Occasionally the capacitive buttons don't register either.

Same thing here. Perfectly working screen, flashed 5.1 unofficial some weeks ago and no matter wich versión of cm or what kernel, randomly ghost touches happens.
Now with official 5.1 and ak 200 works better, but it's still there. There must be some kind of firmware/software problem, It's too curious that this issue begin to happend to many people at the same time.

My bro has the same problem, some days after flasing CM12S the screen doesn't feel as responsive anymore.
The screen isn't able to handle multiple touches anymore what makes typing really annoying, scrolling through settings also goes really slow.
Tried flashing latest 12.1 nightly but I don't think any ROM will be able to fix it.
No idea what caused it and if there is a way to fix it.

ZuLa said:
Same thing here. Perfectly working screen, flashed 5.1 unofficial some weeks ago and no matter wich versión of cm or what kernel, randomly ghost touches happens.
Now with official 5.1 and ak 200 works better, but it's still there. There must be some kind of firmware/software problem, It's too curious that this issue begin to happend to many people at the same time.
Click to expand...
Click to collapse
This is exactly what happened to me and it seems like it happened to a good number of people around the same time. Either 1)It's a huge coincidence 2)OnePlus rigged our phones to go haywire around this time or 3)Something in one of the nightlys got messed up for a few people however like you said, flashing new roms for kernels doesn't help anymore which makes me want to do a complete wipe - Internal data included.

Same issue
I was sure it's the heat some time back but then this touchscreen fixer app in the Themes and Apps section is actually helping. That makes me wonder if its the firmware, coz the problem only kicked off after the CM12.1 update. A few of my classmates purchased the OPO at the same time as I did and they dont have this issue (they didnt go to CM12.1).
Any tips on what firmware/ROM to revert to?
Edit: I also flashed the Oxygen OS firmware.

It's not a change in the firmware, mine did it spontaneously. It's hardware. OnePlus will do everything they can to spin a software story and indeed it will often be possible to partially mitigate in software, but ultimately everyone with this problem should be getting a replacement. That could be a lot of people.

patp said:
It's not a change in the firmware, mine did it spontaneously. It's hardware. OnePlus will do everything they can to spin a software story and indeed it will often be possible to partially mitigate in software, but ultimately everyone with this problem should be getting a replacement. That could be a lot of people.
Click to expand...
Click to collapse
I'd love to see how you jumped to such a definite conclusion. I live in a warm climate to begin with, temperatures are actually lower now than they were a month and a half ago, and the CPU of my OPO has definitely risen above the 41-45 Celcius range that people seem to quote for this current wave of issues (and I have corroborated with my own testing). However, if I go to the recovery, the touchscreen seems to have normal responsiveness, regardless of the CPU temperature. Unless it was a built in hardware malfunction set for a specific moment, the probability of a sample, even of this size, where a series of individuals can all see the exact same lineup of hardware-based issues occurring at the same time, is too ugly for me to try and imagine calculating. But I would fare to bet it isn't high.
However, if a set of users are all changing their software as new versions and builds come out, just as the release occurs... At least then you have a series of events occurring all at the same time. Not causation, but at least there's a stronger correlation than "it's warming up so now we see the hardware defects".
The temperature range this "defect" is being attributed to can be reached quite easily in normal use in temperate areas, but even in colder climates, it should be simple to reach such temperatures if the phone isn't underclocked, as the phone is set to charge, or even if the phone is running a software update of some kind, and countless other things.
TL;DR - Don't jump to conclusions that fast, weather changes aren't a strong correlation.

hyshion said:
I'd love to see how you jumped to such a definite conclusion. I live in a warm climate to begin with, temperatures are actually lower now than they were a month and a half ago, and the CPU of my OPO has definitely risen above the 41-45 Celcius range that people seem to quote for this current wave of issues (and I have corroborated with my own testing). However, if I go to the recovery, the touchscreen seems to have normal responsiveness, regardless of the CPU temperature. Unless it was a built in hardware malfunction set for a specific moment, the probability of a sample, even of this size, where a series of individuals can all see the exact same lineup of hardware-based issues occurring at the same time, is too ugly for me to try and imagine calculating. But I would fare to bet it isn't high.
However, if a set of users are all changing their software as new versions and builds come out, just as the release occurs... At least then you have a series of events occurring all at the same time. Not causation, but at least there's a stronger correlation than "it's warming up so now we see the hardware defects".
The temperature range this "defect" is being attributed to can be reached quite easily in normal use in temperate areas, but even in colder climates, it should be simple to reach such temperatures if the phone isn't underclocked, as the phone is set to charge, or even if the phone is running a software update of some kind, and countless other things.
Click to expand...
Click to collapse
The outside temperature being warm would keep the screen hot for a prolonged period of time as compared to the phone heating while charging or intense usage. However, your recovery argument is spot on! The touch works flawlessly in recovery!

goldengargoyle said:
The outside temperature being warm would keep the screen hot for a prolonged period of time as compared to the phone heating while charging or intense usage. However, your recovery argument is spot on! The touch works flawlessly in recovery!
Click to expand...
Click to collapse
Well I guess it's good that it's not hardware damage.
Has anyone tried going back to android 4.x to see if it helps- if it really is software?
Surprised there hasn't been more people experiencing this issue given the number of people going to android 5.x

I have the same frustrating issue

Same here, works fine in recovery. Also had this issue arise after the first bout of touch issues: https://www.youtube.com/watch?v=yoFYcFawTI4&feature=youtu.be
(clearing cache seems to alleviate that particular problem)

I think it's a software issue. I mean possibly there is hardware problems too but mine started appearing only after I installed the 5.1 update... also some things for me feel like a software issue for example when scrolling instagram back up to the top. as soon as it gets to the top it bounces back down again.. seems like software problem to me.

This is definitely a hardware issue. My phone was working perfectly. Until I went on a 5 days trip and used it for navigation, and went very hot. Up until then I was on the same CM12 rom for weeks without a problem. Since then, I've flashed many roms and the problem persists. It's definitely a hardware problem. For me it occurs whenever the phone runs a little bit hot. Practically all the time when I'm on 3G. When the phone has been in my pocket with 3G on, it's almost impossible to unlock it when I try to use it.
I contacted Oneplus a week ago and I still try to get them to RMA the phone. They've sent me all sorts of crap emails, I wiped the phone and now they ask me to shoot a video to showcase the problem. This company has the worst customer service you can find. As much as I like the pricing, I won't be bothered again with their devices. I only hope they'll RMA it otherwise I'll open it myself and try to fix the grounding issue. There is a detailed how to which also explains what's the problem.

I always had it but it was so minim that maybe couple of times a day weren't that big problem!
Just yesterday and today the issue is now intolerable! I removed the screen protector and used the stock lollipop keyboard (bcz swiftkey is kinda slower the issue was there more).
It's still very annoying and I can't type easily! I had to remove flow/swype feature to minimize it further!
Seriously considering buying another phone although I wanted to keep it for a year at least! But the hate is growing on me...

HAha exact same problem here happening since 3days.
I was on Euphoria 29/3 build. I flashed ak kernel, after reboot i couldn't type properly anymore. I was like damn, maybe its bad kernel setting or so. Didn't help.
Cleanflashed 3 roms since then, didn't solve anything. All tho touch works fine in twrp for me. So im really clueless. Swiping does seem to work better for some unknown reason to me!

The ghost swipes while typing is driving me crazy. Thinking of going back to 5.0.2 to see if that helps. Do I need to flash an old firmware to go back to a previous Android version

Issue list after about one year of use !

Well, I've been using my Oneplus since a pretty long time, and I decided to list all the issues I have since I got it. It's pretty long so stay sitted.
- Ghost touches on touchscreen.
- Touch screen becoming suddently unresponsive.
- Never could manually select my carrier.
- Never could connect to carrier network.
- Never could download MMS.
- Never could connect to LTE/4G, even though the APN was correctly set up.
- Camera freezes randomly.
- Phone keeps waking up for no reason (the touch to wake keeps getting triggered, certainly a ghost touch issue).
- Photos are pretty bad, stabilisation sucks.
- Call app keeps randomly crashing, only solution to use it again is to reboot the phone.
- Messages app keeps randomly crashing, only solution to use it again is to reboot the phone.
- Random system crashes (something similar to a segfault somewhere in the UI management code).
- High battery drain (I mean, REALLY high, like, "a full battery in half a day" high !).
- SMS sending/receiving fails very often.
- GPS fixe is unreliable, it keeps draging my position over the whole town and never settles.
- Compass is unreliable, according to it, I keep spinning around, even after a recalibration.
I guess that's about it, I am missing some, but that's already pretty long.
I tried everything and made a clean install after each update to be sure, and the problems kept on adding onto each others.
The only thing that could explain that could be very poor build quality and Cyanogen mod's team incompetence (yeah, these guys really can't code properly, putting their ROM on the phone was a big mistake from OnePlus).
I would like to precise that I treated the phone very well, it never fell down, it doesn't even have a little scratch. It really feels like using one of those counterfeit phones, even though I got it from the official online store.
How many of these issues did you have ? And if you did, how did you fixe it (if you could ever fixe them) ?

There's something pretty wrong with your phone, it shouldn't act like that. You need to provide some more information.
What build are you on?
Is your bootloader unlocked?
Do you have a custom recovery?
Have you modified it in any way?
What was the last update you took and how did you apply it?

I have similar things happening to mine.
I've treated it well with no major damage to the phone.
After having it from a year and a month I've noticed that it's started. I've updated normally through OTA to CM12.1-YOG4PAS1N0.
Never rooted ( really considering it now, was very lazy haha ), never customised just kept all stock.
The problems I am having that really are concerning me :
- Very high battery drain (doesn't last 4-5 hours at most).
- Very high CPU usage (and hence the phone getting quite hot) thought it was the google play services bug, didn't change when I applied the changes.
- SMS taking a while to send (between 1.5~2 minutes for a message to send).
I'm thinking of factory restoring my phone, just want to find something decent to back my important data up (e.g. sms, some app data) [anyone welcome to suggest anything, I'm still looking].
If I factory reset I will post any results of what happens.

As I've stated in another forum thread started by the above user, I have had a lot of the aformentioned problems and worse.
We've both described our issues in that thread and as I've stated I'm growing so weary. I had my PC fail on me last year and spent all year chasing warranties and RMA's and having to coax companies, who are legally bound to do what I am having to beg and threaten before they do it. Then this year I get a defective OnePlus One and One Plus themselves ignore, deflect, delay and misdirect me. I've had the phone 10 months now and I've been complaining and fighting for 6 months with the above problems and I was only just offered an RMA (or RRR as they call it) this month. That's 6 months of begging, pleading and then demanding. Safe to say I have sought third party legal advice and will be taking this as far as it can go.
I would make contact with them as soon as you can regarding these issues or they will only use that against you.

Intermittent Lag makes phone impossible to use

Description of the problem:
This happens several times in a day, but I have had a few days when this did not happen. When waking the phone it becomes super slow, like 1-2 frames per second slow. After rebooting- the recovery is just as slow. Sometimes the view is moved vertically up, the top part that is moved outside of screen and is drawn ant the bottom. Sometimes the image flickers. I have not noticed any pattern what stops this behaviour, it is just over after some time (5s to 2 hours).
What I have tred with no success:
Rebooting, clearing cache, factory reset, bringing the phone to full stock (http://forum.xda-developers.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390), updating to latest version, several ROMs and different kernels with each of them. After flashing any new rom the phone used to work fine for a day or two, then the stutter reapeared. Tried it without installing any apps- same problems.
I had to replace the cracked screen and the camera that didn't focus to far objects. The touchscreen ribbon is now insulated from the metal LCD back since some people suggested this might be the reason for touchscreen responsiveness issues.
It seems that the processes work normally, but the view on the screen is updated slowly.
What made the problem less bad:
I had applied a glass screen protector. Removing it increased the time between slowdowns.
Since I bought the phone secondhand and had tinkered with it I cannot get it replaced.
I have tried everything I could, now I need your help
Any suggestions?
A video to visualize the issue: https://www.youtube.com/watch?v=h8z06xnlqk8

Noone? No ideas?

Hi,
Sounds like a Hardware issue to me.The board ist mostly bad soldered. It can happen sometimes in the factory(not only at OnePlus, Samsung, HTC too), even if they test the devices before shipping.
Background: We had some germans around here had the same issue, they got a new replacment by OnePlus, OPO support told the customers that the hardware was faulty.
Can u afford another Mainboard for the OPO ? That will fix that issues for sure.

Well that makes sense I'll poke around to see if I can get one for as little as possible. So far I'd expect to spend ~250$ and that is just bad business

no worrys, u dont need to spent that much.check aliexpress or if your lucky buy a dropped OnePlus One on eBay. One with working mainboard. It will cost around 30-50% less than a single Mainboard would Sounds ridiculous but its true.