37

Lets Confirm Who Has the Ghost Touch Issue

  1. saisaijo Froyo May 24, 2019

    saisaijo, May 24, 2019 :
    hi guys, i have no programming knowledge.. does this find point towards a software or a hardware issue?
    I'd rather not rma for something that could be fixed in an update...
     

  2. crazything Eclair May 24, 2019

    crazything, May 24, 2019 :
    Well it's hard to say. I would guess it's a driver issue (software) but mind you I might just be hoping here. Like I said before I can get proximity data without using the "faulty" sensor, so it feels s lot like some odd software glitch.
     

  3. jdpeters79 Gingerbread May 24, 2019

    jdpeters79, May 24, 2019 :
    This is all awesome info guys, thanks for sharing. I agree, it's in One Plus hands now. I took a chance on a replacement to see if that shows any differences, because I figured might as well use my 15 day window in case it turns out to be a somewhat random hardware issue. Or a combo of HW and SW. But only time will tell. The good thing is at least the OnePlus bug hunters are aware and going through this thread, and the logs.
     

  4. D1558344131743 Eclair May 24, 2019


  5. crazything Eclair May 24, 2019

    crazything, May 24, 2019 :
    If you only have a 15 days window rma might be worth it, I agree :) By law I have way longer so I'm going to sit still.
     

    RedWizard22 and jdpeters79 like this.
  6. jdpeters79 Gingerbread May 24, 2019

    jdpeters79, May 24, 2019 :
    I think they've asked a few of us on here for logs. They emailed me overnight and I sent them some. Seems like they're monitoring it
     

    D1558344131743 likes this.
  7. saisaijo Froyo May 24, 2019

    saisaijo, May 24, 2019 :
    where u from?
     

  8. Curtixman Froyo May 24, 2019

    Curtixman, May 24, 2019 :

    Well, ultimately it doesn't matter to me. Or shouldn't matter. I RMA returned it. OnePlus must have forwarded it to some repair shop because I received a follow-up from a authorized repair centre with a shipping label instructing me to send it to them.
    I called OnePlus to be sure and they said that once the authorized service centre checks it to make sure there is no physical damage (apx 14 days) they will process a refund.
    Truthfully I'll believe it when I see the money returned to my credit card because my overall experience with OnePlus this far has been embarrassingly sad.
    I wouldn't even know where to start to explain it but I did record all the calls and transcripts of my chat conversations.
    What a company.
    Anyway, I hope they get all the issues sorted out for the rest of you but I cannot wait to put OnePlus in my rearview mirror forever.
     

  9. crazything Eclair May 24, 2019

    crazything, May 24, 2019 :
    Sweden, got at least 2 months by law. Longer if it's deemed reasonable. It's up to 2 years in eu, up to 3 years in Sweden. But it depends a bit. It needs to be a fault from factory. If it's within 6 months it's up to the seller to prove I caused it, after that I have to prove I did not cause it.
     

    J1542606030006 and jdpeters79 like this.
  10. dcmcc24 KitKat May 24, 2019

    dcmcc24, May 24, 2019 :
    If it is software, how come it doesn't happen to everyone's phone?
     

  11. jdpeters79 Gingerbread May 24, 2019

    jdpeters79, May 24, 2019 :
    That's fantastic. Wish we had more time in the US.... Amazon at least gives 30 days, but not for all devices. everything else is 15.
     

  12. HomerSp Donut May 24, 2019

    HomerSp, May 24, 2019 :
    Interesting, another Swede eh? :)

    I will also wait with RMA until OnePlus responds - hopefully it can be fixed with a software update! If I were to guess it probably can be, in a worst case scenario the sensor can probably be disabled completely. For some reason there are actually multiple proximity sensors in the device, one is an infrared sensor that's far more precise embedded in the top-right part of the screen (you can test it using *#808#).
     

  13. HomerSp Donut May 24, 2019

    HomerSp, May 24, 2019 :
    That's a point, but I think it may be a hardware calibration issue or such that can be worked around in software.
     

  14. golgote25 Froyo May 24, 2019

  15. ursidae1 Donut May 24, 2019


  16. B1558429430009 Cupcake May 24, 2019

    B1558429430009, May 24, 2019 :
    I got my phone today. Activated showing the touch input, downladed CPU-Z, waited 3 minutes and no Ghost Touches. Hopefully it will be a software failure! So it can be fixed very fast for you guys
     

  17. C3C0 Froyo May 24, 2019

    C3C0, May 24, 2019 :
    Tried testing proximity sensor with DevCheck app by flar2 and no ghost touches. Didn't try cpu-z, though. My model is 6GB GM1913.
    1558736563883.jpg

    1558736563928.jpg
     

  18. parsa5 Jelly Bean May 24, 2019

    parsa5, May 24, 2019 :
    Someone from OnePlus called me 30 minutes ago(Hong Kong number) and told me that their management teams is looking at this issue.
     

  19. pgrey Honeycomb May 24, 2019

    pgrey, May 24, 2019 :
    "Relay for Reddit" has known overlay issues.
    Has ANYONE checked to make sure they have zero (0, none) overlay apps/services enabled?

    I have zero (with permissions), and I've tried about 20 times now, in various ways to repro this (I'm a s/w engineer, written hundreds of display tests over the years), to no avail.

    I can't even get touches to "register", in the video areas of CPU-Z, unless I turn on the dev-option to "show touches". Without this enabled, if I touch (with my finger) those areas that are in the videos, they don't even register.

    I still stand by my assertion that this is a s/w issue, nearly 100%. It could be a problem with the OS, the way overlay/touch is being managed, or similar, it's hard to say.
    I'm 100% confident that OP will get to the bottom of it, I've sent them several issues, with detailed traces and steps, over the past couple of years, and have gotten a 100% fix-rate, on them, most fixed relatively quickly.
     

  20. pgrey Honeycomb May 24, 2019

    pgrey, May 24, 2019 :
    Which apps? I use GBoard (pretty much exclusively on my Android devices), and cannot repro this, I've tried >20 times now, with CPU-Z, which seems to be a "sure thing", except it's not, for me.

    I'd love to get the bug-hunters team an "exact repro", along with the same slice of logs, but I can't get this to occur at all.
     

    Gaurav Rohilla and jdpeters79 like this.