Related
Hi guys, i really like the phone but I have one major problem with it. Sometimes the screen randomly thinks my finger is tapping instead of swiping.. So when scrolling through a list, it doesn't scroll through the list, but rather taps the links. I compared it with my M8 and its definitely a huge difference
Sent from my One using XDA Premium 4 mobile app
Seems we are paying the price of being seduced by this sh****ty phone:
https://forums.oneplus.net/threads/issues-with-my-and-many-others-opo.54770/
https://forums.oneplus.net/threads/serious-touch-problem.59264/
https://forums.oneplus.net/threads/opo-touch-screen-issues-works-only-sometimes.62253/
Some of this links are more related to your specific issue, the other less; but in general you got the idea that the touch screen is ....(put your own words after the beeeep)
Everything works fine for me on my device. Maybe you should try to get the device exchanged or only contact the support for more information.
area. said:
Everything works fine for me on my device. Maybe you should try to get the device exchanged or only contact the support for more information.
Click to expand...
Click to collapse
sweet advice from you.
I would really recommend to look at oneplus forum.....very interesting reading
Just to sum up, the customer support in OnePlus is nearly non-existend.
I have seen the reports that someone with RMA ticket number 98 (can you imagine, just in first hundred) does not have any reply from them already 3 weeks.
God im seriously thinking about keeping my M8...
I am also experiencing the tap instead of swipe bug. Its a bit annoying. I love the potential of this phone and hope that Cyanogen will get all the kinks fixed. Maybe that's one of the real reasons for the official release not taking place.
Sent from my One using XDA Premium 4 mobile app
OuncE718 said:
I am also experiencing the tap instead of swipe bug. Its a bit annoying. I love the potential of this phone and hope that Cyanogen will get all the kinks fixed. Maybe that's one of the real reasons for the official release not taking place.
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thats the only reason I'm gonna sell my M8 and keep the OPo, because im confident that CM can really sort out those bugs, or the community can fix them themselves
Radixtrator said:
Hi guys, i really like the phone but I have one major problem with it. Sometimes the screen randomly thinks my finger is tapping instead of swiping.. So when scrolling through a list, it doesn't scroll through the list, but rather taps the links. I compared it with my M8 and its definitely a huge difference
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Are you by any chance having the issue when not holding the phone in your hand? There seems to be some sort of grounding problem(?) when the phone is on e.g. a pillow which did not exist before the update pushed in the beginning of july. Apparantely CM is working on fixing it again.
d4fseeker said:
Are you by any chance having the issue when not holding the phone in your hand? There seems to be some sort of grounding problem(?) when the phone is on e.g. a pillow which did not exist before the update pushed in the beginning of july. Apparantely CM is working on fixing it again.
Click to expand...
Click to collapse
Yup its especially bad when not holding the phone. And its gone when connected to a charging cable.. Still sometimes its buggy even when holding the phone.. I do use a case though..
Radixtrator said:
Yup its especially bad when not holding the phone. And its gone when connected to a charging cable.. Still sometimes its buggy even when holding the phone.. I do use a case though..
Click to expand...
Click to collapse
There is no fix yet, but for your reference I am linking to the corresponding CM bug reports.
https://jira.cyanogenmod.org/browse/BACON-169 (resolved as duplicata)
https://jira.cyanogenmod.org/browse/BACON-55 (pending fix)
Radixtrator said:
Thats the only reason I'm gonna sell my M8 and keep the OPo, because im confident that CM can really sort out those bugs, or the community can fix them themselves
Click to expand...
Click to collapse
I really hope they do rectify these issues. Cause I'm kind of regretting selling my Nexus 5. I mean this hardware is superb and I love the feel of the sandstone back. The software is just not ready for the masses.
I can't wait till the software is bug free. This phone will be a beast!
Sent from my One using XDA Premium 4 mobile app
RalphLauren said:
sweet advice from you.
I would really recommend to look at oneplus forum.....very interesting reading
Just to sum up, the customer support in OnePlus is nearly non-existend.
I have seen the reports that someone with RMA ticket number 98 (can you imagine, just in first hundred) does not have any reply from them already 3 weeks.
Click to expand...
Click to collapse
I am looking at the forums. And: for me, the support responded to my questions within 24h in 3 of 4 cases. That's my personal experience.
I think you should try it. If this does not work: give your request an update. Or two. Or three. And then, if all that doesn't work, either: make pressure on the public forums. THEN you can/should be upset.
area. said:
I am looking at the forums. And: for me, the support responded to my questions within 24h in 3 of 4 cases. That's my personal experience.
I think you should try it. If this does not work: give your request an update. Or two. Or three. And then, if all that doesn't work, either: make pressure on the public forums. THEN you can/should be upset.
Click to expand...
Click to collapse
I'm very happy for you and wish that the support was satisfactory in the cases of my interaction with OPO.
here are 2 videos:
1 - about grounding problem:
first part of video i have OPO in my hand (6 touch) second part on the bed (difficult to reach 2 touch).
https://drive.google.com/file/d/0B7BSKYMyAho3YVVTbzhtbEtmeTg/edit?usp=sharing
2 - fast typing issue:
here you can see how fast touch are recognized by OPO as swype:
http://youtu.be/CkHYdvwf_xM (please see it fullscreen with hd quality)
Ciao
Hello, anyone knows if in the end a solution was found? I have this problem even with the latest update of cyanogenOS.
Someone could tell me if this problem is common? Because I'm considering opening a one RMA support, as in different upgrades they have not solved ...
Enviado desde mi 1+1 con tapatalk
abelbus said:
Someone could tell me if this problem is common? Because I'm considering opening a one RMA support, as in different upgrades they have not solved ...
Enviado desde mi 1+1 con tapatalk
Click to expand...
Click to collapse
Yes it's common, i have this issue as well. I think it happens when the phone stutters/lag, the swipe turns to a tap. My solution is to flash fast, lag-free ROMs, reducing the incidents. You should try jgcaap Lag-free CM13 ROM and see if it gets better, it worked for me.
Thank you very much for your advice, I'm testing this rom, and doing very well not have lag or loses touch for now.
Enviado desde mi 1+1 con tapatalk
The display stopped working 2-3 days ago. On booting i can see the google logo for 2-3 seconds before the screen goes dark. The phone works and i can hear dings of messages, but i cant access any of it. Once i kept shut it for a day i was able to see the screen for 10-15 seconds( i used this window to remove the screen lock so that i can use the usb transfer ). Now keeping the phone shut for long duration has no effect.
I can see the fastboot screen but not the recovery screen throught it.
I also bought a slimport so that i could see the screen on my pc. It works (not for the fastboot or recovery), however the touch doesn't work and the volume and power buttons response is too sluggish. I can connect the mouse but it is of no use as i can't see the screen on PC and use the mouse at the same time. I tried adb ( i have no experience of it ) but i cant touch the allow pernmissions key on the screen for the above reasons. Also what advantage would adb be in this case?.
Any advice ?
PS: i have cyanogenmod
I think ram is your only option. It definitely sounds like it's hardware and not software related.
Sent from my Nexus 5 using XDA Free mobile app
Sorry, i don't follow. U mean a ram replacement is needed ?
jd1639 said:
I think ram is your only option. It definitely sounds like it's hardware and not software related.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
nexmus said:
Sorry, i don't follow. U mean a ram replacement is needed ?
Click to expand...
Click to collapse
It was a typo.. He meant RMA
- Sent from an IceCold Hammerhead!
Oh, you mean sending it to LG for servicing? I am a bit hesitant since i have cyanogenmod and also am in india and i doubt they will give a replacement. I think going back to stock rom and then sending it for repairs might help but i have no idea how to go about doing that in this situation.
vin4yak said:
It was a typo.. He meant RMA
Click to expand...
Click to collapse
nexmus said:
Oh, you mean sending it to LG for servicing? I am a bit hesitant since i have cyanogenmod and also am in india and i doubt they will give a replacement. I think going back to stock rom and then sending it for repairs might help but i have no idea how to go about doing that in this situation.
Click to expand...
Click to collapse
Its all done via fastboot or lg flash tool. Probably the latter is best for you. Have a read of the guides in my signature
How can i do it using fastboot ?
rootSU said:
Its all done via fastboot or lg flash tool. Probably the latter is best for you. Have a read of the guides in my signature
Click to expand...
Click to collapse
nexmus said:
How can i do it using fastboot ?
Click to expand...
Click to collapse
I do t understand the question. Is this question one you're asking having already read the fastboot return to stock guide?
Same issue I had pretty much, it died about 2 months ago. I was still able to copy all of my files, phone worked perfectly but the screen was black. Had it replaced it no time. Is that by any mean a 311k? I've seen another thread like that pop up lately.
vnvman said:
Same issue I had pretty much, it died about 2 months ago. I was still able to copy all of my files, phone worked perfectly but the screen was black. Had it replaced it no time. Is that by any mean a 311k? I've seen another thread like that pop up lately.
Click to expand...
Click to collapse
What does the month it was made have to do with anything?
rootSU said:
What does the month it was made have to do with anything?
Click to expand...
Click to collapse
I don't know yet, I'm just trying to figure out whether it's a particular batch that started failing or it's completely random, just curious. The two replacements I was sent were 403K. Build is perfect, but they both had some light bleed issues. Looks like every batch comes with some good and some bad, QC definitely hasn't been too great on this phone.
vnvman said:
I don't know yet, I'm just trying to figure out whether it's a particular batch that started failing or it's completely random, just curious. The two replacements I was sent were 403K. Build is perfect, but they both had some light bleed issues. Looks like every batch comes with some good and some bad, QC definitely hasn't been too great on this phone.
Click to expand...
Click to collapse
They're not really built in batches. Manufacturing was continuous. They just changed the serial number every time the month changes so I dont think this would actually mean anything
I know but I'd still use it as a milestone more than anything, I mean there have been some differences in the units (eg bigger speaker holes), this way it's easier to track them along the timeline, because they definitely do change something in the manufacturing process from time to time if they have to make up for issues or something. They also did it with the N4 if I remember well.
vnvman said:
I know but I'd still use it as a milestone more than anything, I mean there have been some differences in the units (eg bigger speaker holes), this way it's easier to track them along the timeline, because they definitely do change something in the manufacturing process from time to time if they have to make up for issues or something. They also did it with the N4 if I remember well.
Click to expand...
Click to collapse
Speaker holes is a bad example because even the latest built devices it was still a lottery whether you got bigger or smaller holes. That's down to what you mentioned earlier, QC
rootSU said:
Its all done via fastboot or lg flash tool. Probably the latter is best for you. Have a read of the guides in my signature
Click to expand...
Click to collapse
I was able to unroot and flash the stock image. The problem still exists though, so it has to be a hardware issue. Fortunately the phone is still in warranty.
Thanks for all the support.
Recent commit in the touchpanel kernel drivers area:
http://review.cyanogenmod.org/#/c/75571/
Looks like getting the touchscreen controller's firmware ready for a WINTEK touchscreen (versus TPK, which is the current one).
Any info anyone?
javideslomao said:
Recent commit in the touchpanel kernel drivers area:
http://review.cyanogenmod.org/#/c/75571/
Looks like getting the touchscreen controller's firmware ready for a WINTEK touchscreen (versus TPK, which is the current one).
Any info anyone?
Click to expand...
Click to collapse
I'm curious about it :|
javideslomao said:
Recent commit in the touchpanel kernel drivers area:
http://review.cyanogenmod.org/#/c/75571/
Looks like getting the touchscreen controller's firmware ready for a WINTEK touchscreen (versus TPK, which is the current one).
Any info anyone?
Click to expand...
Click to collapse
Maybe they found TPK to be too unreliable in terms of quality control and decided to try Wintek out?
Wintek are known to make touchscreen for iPhones and other phones.
Sent from my SM-G900F using Tapatalk
I wonder if you can RMA based on crappy touch screen and get a wintek screen panel?
How do you check what panel you have now, is there a way?
Sent from my A0001 using XDA Free mobile app
If this is the case, and it would fix all the existing touch problems, that would be so unfair towards customers who purchased phones with this issue...
Mine is 26/08 and I have no quality problems at all, no yellow band, no ghost touches, but still!
Verstuurd vanaf mijn One A0001 met Tapatalk
TiVON said:
If this is the case, and it would fix all the existing touch problems, that would be so unfair towards customers who purchased phones with this issue...
Mine is 26/08 and I have no quality problems at all, no yellow band, no ghost touches, but still!
Verstuurd vanaf mijn One A0001 met Tapatalk
Click to expand...
Click to collapse
Golden rule of technology: Never buy the first generation of anything.
It's not unfair, it's just a nice perk to those who came after us. OnePlus had no way of knowing the touch panel would be as big of a problem as it has been. We'll still be getting driver updates and the like to make our panels more usable.
Wtf i want a new device. I hate yellow banding.
Sent from my A0001 using XDA Free mobile app
DerRomtester said:
Wtf i want a new device. I hate yellow banding.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
This doesn't resolve yellow banding. That's an issue in manufacturing that was fixed long ago.
In your case, find a UV light somewhere. Hair salon has them. Just leave your phone under it for a bit and the yellow will be gone. It's because they didn't leave them under UV long enough in the factory to dry the glue holding the panel to the LCD.
TiVON said:
If this is the case, and it would fix all the existing touch problems, that would be so unfair towards customers who purchased phones with this issue...
Mine is 26/08 and I have no quality problems at all, no yellow band, no ghost touches, but still!
Verstuurd vanaf mijn One A0001 met Tapatalk
Click to expand...
Click to collapse
Where do you check that yours is 26/08?
ek69 said:
Where do you check that yours is 26/08?
Click to expand...
Click to collapse
Should be on the back of the box
mobbarley said:
Should be on the back of the box
Click to expand...
Click to collapse
Yupp, got it from there. I always keep the boxes of expensive stuff I bought . Makes me feel proud of myself...
Verstuurd vanaf mijn One A0001 met Tapatalk
1/4 Life said:
This doesn't resolve yellow banding. That's an issue in manufacturing that was fixed long ago.
In your case, find a UV light somewhere. Hair salon has them. Just leave your phone under it for a bit and the yellow will be gone. It's because they didn't leave them under UV long enough in the factory to dry the glue holding the panel to the LCD.
Click to expand...
Click to collapse
Oh sry did not read carefully. But nothing solved my yellow banding yet. I were in nail saloon but it is still there.
Sent from my A0001 using XDA Free mobile app
DerRomtester said:
Oh sry did not read carefully. But nothing solved my yellow banding yet. I were in nail saloon but it is still there.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
it is a backlight issue. cannot be fixed.
TiVON said:
If this is the case, and it would fix all the existing touch problems, that would be so unfair towards customers who purchased phones with this issue...
Mine is 26/08 and I have no quality problems at all, no yellow band, no ghost touches, but still!
Verstuurd vanaf mijn One A0001 met Tapatalk
Click to expand...
Click to collapse
My first phone had touchscreen and yellow tint problems it was made 15/06 now I have one made 22/09 and it works perfectly
Sent from my Oneplus (Bacon)
1/4 Life said:
This doesn't resolve yellow banding. That's an issue in manufacturing that was fixed long ago.
In your case, find a UV light somewhere. Hair salon has them. Just leave your phone under it for a bit and the yellow will be gone. It's because they didn't leave them under UV long enough in the factory to dry the glue holding the panel to the LCD.
Click to expand...
Click to collapse
The yellow banding was not in any way caused by the adhesive/glue. That was an excuse offered by OnePlus as damage limitation. It is one of their many many many poorly thought out excuses for all the early hardware problems.
Oh and the problem does still exist in the current batches.
I had hoped we'd left the yellow band / yellow tint stuff behind us. Can't we just leave it now? It's not productive. It's not the point of the thread.
istrikerx said:
The yellow banding was not in any way caused by the adhesive/glue. That was an excuse offered by OnePlus as damage limitation. It is one of their many many many poorly thought out excuses for all the early hardware problems.
Oh and the problem does still exist in the current batches.
Click to expand...
Click to collapse
^ This. My phone has a build date of 10/10 and I still have yellow banding...
beany> said:
I had hoped we'd left the yellow band / yellow tint stuff behind us. Can't we just leave it now? It's not productive. It's not the point of the thread.
Click to expand...
Click to collapse
While I do see your point, you have to realize that any thread regarding display discussion is going to result in talking about the yellow banding. Unfortunately, the number of people who have it is VERY large and many people who spent their hard earned cash on the phone feel let down by it. So naturally, if a topic comes up about a new display, the conversation is going to turn to discussing if this new display solves this widespread problem.
Is it annoying to read about it every day? Yes. But is it an issue that OnePlus refuses to admit to as being a defect and something that bothers A LOT of OnePlus One users? You bet. It will not be left behind until OnePlus truly acknowledges the issue and solves it. Until then they will continue to distribute the phone and buyers will keep noticing it and rehashing the topic in this forum.
just got mine today 10/10/2014 on the box.
How can i tell if it has the new touch panel ?
vadergr said:
just got mine today 10/10/2014 on the box.
How can i tell if it has the new touch panel ?
Click to expand...
Click to collapse
On a terminal app or an adb shell, do:
Code:
cat /sys/class/input/input0/vendor_id
TP vendor codes being:
Code:
#define TP_VENDOR_WINTEK 1 //ʤ»ª
#define TP_VENDOR_TPK 2 //TPK
#define TP_VENDOR_TRULY 3 //ÐÅÀû
#define TP_VENDOR_YOUNGFAST 4 //Ñó»ª
Most likely you'll get "2"... I think we would have known via an official channel if there is an important change like this. Also the driver would probably undergo some changes to adopt a new TP and we would know via gerrit / github. Still, Steve Kondik's comment "Needed for the next batch." puzzles me.
Received my oneplus today, built Nov 3
the above procedure shows vendor_id 1 so WINTEK
Galaxy S7 screen not responding to touch sometimes. The bottom portion of the display is affected. I tried 6 different S7 and all of them have the same problem, test yours like this and tap gently not hard, when you press hard you press 3mm on the screen and that is a lot ! The problem is worse when the phone is cold (20C) This is annoying because the place where its not working is the same place where the space bar is and the "." Does anyone else have that exact problem? Here is a video of the problem : https://youtu.be/OW_FQBMcuOE
IMPORTANT !
Install Phone INFO app (green adroid logo) see when the phone is manufactured, mine is 2016.02.18 ! maybe the first batch of the production have that problem! We might be on something here!!!
There are two threads already open with this situation.
I have this problem at the same location you demonstrate. The right side has this problem too. From bottom right to the top 1 cm and 2 or 3 cm up you are going to reproduce the same thing.
I get used to it but it is very annoying. Never liked Samsung because of this things. They use low quality material all around. I will never trust them.
Sent from my SM-G930F using XDA-Developers mobile app
goTouch said:
There are two threads already open with this situation.
I have this problem at the same location you demonstrate. The right side has this problem too. From bottom right to the top 1 cm and 2 or 3 cm up you are going to reproduce the same thing.
I get used to it but it is very annoying. Never liked Samsung because of this things. They use low quality material all around. I will never trust them.
Sent from my SM-G930F using XDA-Developers mobile app
Click to expand...
Click to collapse
I cant seem to find the other threads will you be nice enough to paste a link. btw should i ask for a replacement ? or all of them are like this because ive tested 10 phones by now but all 930X showroom phones and all are the same...i dont have much days left for my replacement deal so i dont know what to do, everything else is perfect only the front camera i feel like its not focusing good enough compared to the s6..
brane871 said:
I cant seem to find the other threads will you be nice enough to paste a link. btw should i ask for a replacement ? or all of them are like this because ive tested 10 phones by now but all 930X showroom phones and all are the same...i dont have much days left for my replacement deal so i dont know what to do, everything else is perfect only the front camera i feel like its not focusing good enough compared to the s6..
Click to expand...
Click to collapse
Found one, some post an answer recently:
http://forum.xda-developers.com/showthread.php?t=3343175
Sent from my SM-G930F using XDA-Developers mobile app
IMPORTANT !
Install Phone INFO app (green adroid logo) see when the phone is manufactured, mine is 2016.02.18 ! maybe the first batch of the production have that problem! We might be on something here!!!
brane871 said:
IMPORTANT !
Install Phone INFO app (green adroid logo) see when the phone is manufactured, mine is 2016.02.18 ! maybe the first batch of the production have that problem! We might be on something here!!!
Click to expand...
Click to collapse
Mine was manufactured 2016.03.04 (yyyy.mm.dd)
Sent from my SM-G930F using XDA-Developers mobile app
Mine was 2016/04/08
Sent from my SM-G930W8 using XDA-Developers mobile app
go to samsung store
Just received H9 update and the release notes did not mention anything about LCD, touch screen or anything related to it.
But since the update, I've been trying to reproduce the problem trying to find the blind spots and for my surprise I did not find anything. The touchscreen is perfect and I can feel it is more sensitive.
Before the update I could reproduce the problem very easy! Now it is perfect.
The update here in my region (Brazil - ZTO) was about 170MB. Samsung Cloud was introduced.
Wow, mine was manufactured 2 weeks ago (2016.08.16) and I've owned it since about the 24th too, so it was 8 days old when I received it
Hi,
got 1 more issue and 1 more question.
1. I love tap to wake function. Had it on all my Lumias and it was awesome.
Now in Z5 with tap to wake on I got phone constantly ON in my pocket!!! WRRRRR!!!!
What is going on and how can I prevent it?
What is the point of this feature if phone turns on by itself every minute?
2. Just got new SD card - how do I move more than 1 app at the time from internal storage to sd card?
In W10m I could select few aps and simply move them - here I do not see such option
No one has such issue with phone getting unlocked in a pocket?
galtom said:
No one has such issue with phone getting unlocked in a pocket?
Click to expand...
Click to collapse
There're loads of people reporting this problem - just take a look around this forum. You'll just have to turn it off like the rest of us do. Total garbage feature as currently implemented.
Ok, thanks. I cant believe old and cheap Lumias do it perfectly and Z5 cant
Since Z5 in on a market long time and problem has not been solved I guess Sony does not care?
galtom said:
Ok, thanks. I cant believe old and cheap Lumias do it perfectly and Z5 cant
Since Z5 in on a market long time and problem has not been solved I guess Sony does not care?
Click to expand...
Click to collapse
You're right, this issue has been ongoing since the very release of this device. I don't think this will ever get solved as there are maybe more pressing issues with the z5.
I would try a third-party pocket detection implementation.
I have used with good results: gravity screen, glimpse notifications. Not sure of HiLocker..
millicent said:
You're right, this issue has been ongoing since the very release of this device. I don't think this will ever get solved as there are maybe more pressing issues with the z5.
I would try a third-party pocket detection implementation.
I have used with good results: gravity screen, glimpse notifications. Not sure of HiLocker..
Click to expand...
Click to collapse
Thanks, I will try those!
galtom said:
Thanks, I will try those!
Click to expand...
Click to collapse
Also consider Smart Pocket Guard. I've been using it for three weeks and it seems to work fine. Only problem is it doesn't auto-start on boot.
I'm plagued by this bug too. Any idea if it is related to the screen touch hardware?