Database Info

N8010: serious touchscreen / display bug, probably affecting whole batch / model

Hi,
I made this video to demonstrate a rather serious Galaxy Note 10.1 Bug
that i've encountered on two devices, bought from two separate stores.
The first device was a Note 10.1 N8010 with Jelly Bean, the second (the
one on the video) is a Note 10.1 N8010 with Ice Cream Sandwitch.
Transcript:
Hi.
I have in front of me a brand new Galaxy Note 10.1.. its a WIFI-model
N8010. With brand new i mean i bought it a couple of hours ago--here is
the recepit.
I already bought a Galaxy Note 10.1, same type and model.. about 6
Months ago, but its touchscreen suffered from a very weird
touchscreen-bug that was somewhat difficult to reproduce. When I tried
to return the first model, the device went away for almost 3 months and
when I got it back the bug was still there.
Since I was using the device mainly for writing assignments and taking
notes (thats why i bought it in the first place) i gave it back and went
to another store to buy a new one, hoping that the first place will give
me my money back. I needed the device urgently and it was, like i said,
3 months and I had to make a decision.
Well, as it turns out, though, the new device, the one you can see here,
has the same bug.. and I'm going to demonstrate it now.
Right now, as you can see, the device is not in a sane state.. and the
display hasn't turned off since I started speaking. The 2, well, the 4
dots, here, here, here and here.. this one is shaking.. the 4 dots are
supposed to indicate touch activity but are rather ghost-dots caused by
mentioned bug. Here for example is another dot.. I can make several of
them.. I can use a couple of fingers.. and.. this dot is caused by my
hand, the other ones by said bug. I can't do anything right now.. I
can't press on any of these buttons.. I can't call the menu, I can't
switch the homescreen left or right.. I can't drag the.. this thing
here, whatever its name is.. touch input is pretty much impossible.
How do you cause this bug? It's pretty simple.. you roll the palm of
your hand over the display. I can demonstrate this.. I can already
demonstrate this on the lockscreen, doesn't matter.. now, there are 3
dots.. and again.. well, lets try that one again.. now we see 4 dots..
and I can't unlock the lockscreen with my finger. I can though do it
with my pen. Alright.. like i said, you roll the palm of your hand over
the display.. angle and corner don't matter.. current application in
the foreground don't matter either. When this state is active.. it's
going to be almost impossible, I already mentioned that, to use
touch-input.. and with almost I mean there are certain situations where
touch-input will partially work.. but in most cases it won't. Like
you've seen the pen works in this state.. and sometimes, but just
sometimes, it will reset said state. I'm not sure.. I'm still not able
to use touch properly.. yeah, i'm still not able but the pen still
works. Let's reproduce it one more time.
If you want to reset this state your only option is to turn off the
display.. there you go. This bug occurs on ICS and JB.. this device here
has ICS, thats 4.0.4 and my last device, the one that i wanted to give
back.. is running JB 4.1.2, i think. (...) This bug is a show stopper
for everyone who'd like to use this device for lots of writing.. and
it's also a trouble maker since the repair-guys have a hard time
reproducing it, even if you provide them with a comprehensive video.
Now, I hope this video will reach someone who has the necessary access..
because, i don't know, either I'm very, very lucky and get my hands on
two exceptional devices with the exact same bug or this affects the
whole batch or every such model.
I can show perhaps a couple of other apps if the device will let me..
which it won't right now.. Its probably time to use the pen. For
example S-note.. pen works.. touch doesn't.. it's the same story, it
doesn't depend on the application or lockscreen or mainscreen, whatever.
Let me repeat: In this state, when you see these dots, the display will
never dim or go to sleep.. so if you write something and you don't
realize that the device is in such a state.. and you go somewhere for a
couple of hours.. you will come back and you will see that the display
never turned itself off and that you lost lots of battery.
If you want to contact me, i provided my address below (...) thanks for
watching."
Contact me at [ bergwitz at gmx.ch ]
Click to expand...
Click to collapse
Any help is appreciated.

bergwitza said:
Any help is appreciated.
Click to expand...
Click to collapse
I don't know what kind of help anyone's going to be able to provide. It's either a s/w problem which if you've hard reset the device and it's still there indicates a h/w problem. There's been some strangeness on particular regional versions of s/w. For example, different S Note versions have had various problems and different versions are shipped in different regional ROMs. You said two Note's you've had have the same problem though which doesn't make sense if one was ICS and one JB which means they were manufactured at different times so not from the same batch. Are you using a case with magnets in it? Some people have reported strange display issues when the Note's near magnets which causes electromagnetic interference.
The Note's been out since August and sold in the millions and this is the first this type of issue's been reported. So, to your point, maybe there was a batch of bad displays that got out and all ended up in whatever region you live in. Or all versions of your region's s/w has some type of display driver bug. Mine (from August) has no touch issues either via the pen or capacitive touches and I enabled "show touch" in the developer's settings to test it. It's also a pretty obvious issue so if it were common others would have commented or posted also.
The latest 4.1.2 s/w for the N8010 is for the Nordic Countries and was released in March. From your accent I'm guessing you're in the EU. The Nordic ROM is multi-CSC so can be used on any EU N8010. You might want to try installing it via Odin to see if it changes anything.
http://www.hotfile.com/dl/199761991/e927a4b/N8010XXUCMA8_N8010OXXCMB1_NEE.zip.html

BarryH_GEG said:
I don't know what kind of help anyone's going to be able to provide.
Click to expand...
Click to collapse
You provided help when you tried to reproduce the problem.
BarryH_GEG said:
It's either a s/w problem which if you've hard reset the device and it's still there indicates a h/w problem.
Click to expand...
Click to collapse
The first N8010 was reset a couple of times. The second wasn't but I guess that wouldn't make much of a difference.
BarryH_GEG said:
You said two Note's you've had have the same problem though which doesn't make sense if one was ICS and one JB which means they were manufactured at different times so not from the same batch.
Click to expand...
Click to collapse
Both had initially ICS. The first N8010 was upgraded to JB during the 3 month repair process.
BarryH_GEG said:
Are you using a case with magnets in it?
Click to expand...
Click to collapse
No, what you've seen in the video was just taken out of the box. There was nothing close or attached, just a tablet and two laptops on a table. The problem was initially reproducible in two different cities on several separate addresses.
BarryH_GEG said:
The Note's been out since August and sold in the millions and this is the first this type of issue's been reported.
Click to expand...
Click to collapse
Yes.. and that was pretty much the only reason why I was so convinced that my device was faulty and went out to get another one in order to get back to work as soon as possible. Now I have to deal with two retail stores.. trying to explain why I want a refund while looking like a shady guy who is trying to pull something.
BarryH_GEG said:
Mine (from August) has no touch issues either via the pen or capacitive touches and I enabled "show touch" in the developer's settings to test it.
Click to expand...
Click to collapse
Thanks for testing!
BarryH_GEG said:
It's also a pretty obvious issue
Click to expand...
Click to collapse
When touches are shown, yes. Otherwise, hell no.. it took me months to figure out what was wrong. I blamed all possible things for the various gitches that were a direct result of this bug.. mostly the apps I was using. When the touch-input freezes started to occur on a daily basis I started to debug.. which isn't that productive when you're not root. In the end I stumbled over the "show touches" option and was lucky that such an option even exists.
BarryH_GEG said:
From your accent I'm guessing you're in the EU.
Click to expand...
Click to collapse
Switzerland
BarryH_GEG said:
The Nordic ROM is multi-CSC so can be used on any EU N8010. You might want to try installing it via Odin to see if it changes anything.
Click to expand...
Click to collapse
Thanks for the link but right now I would just like to get my money back safely.. :|
Do you maybe know how to get in touch with samsung? Just in case the retail stores decide to give me a hard time..

I briefly experienced this issue while using my Note 10.1 in a place I don't usually use it (my brother's desk instead of my own). I was able to reproduce the issue many times by placing my palm on the screen just as in the video above.
Strangely enough, I haven't been able to reproduce the issue since that first time. I use my Note 10.1 in a number of different places (lecture halls, library, home desk, etc.), but can't seem to make it happen again.
I'm running a rooted, deodexed stock rom (4.1.2) on a NT-8013.

me too
Don't worry, you aren't crazy, I get this too.
I'm convinced its caused by pressure on the display components. My reasons are the following:
If i roll my palm across the screen relatively lightly (but still with enough pressure for the device to respond to normal touches) this never happens.
However as soon as i apply a littly more pressure I can replicate this problem every time. (To those reading thinking that I am putting an unreasonable amount of pressure on the device - I am not! I see people much more violent with their tablets day to day with no issue)
Furthermore, the more pressure I apply the longer the touches will stay after i remove my hand, suggesting that the device is kind of uncompressing.
Finally the area in which this is worst* there are some small LCD 'Mura' - that is light spots on the screen you can only see from some angles, these are normally the result of pressure.
I dont know about you guys but my note is pretty creaky, I would guess that there simply isnt enough rigidity to protect the screen components from stresses caused by pushing down on the device. (Note that i dont get this problem usually unless the device is sitting flat on its back.)
Dont get my wrong, I love my note and these issues are fortunately only an uncommon annoyance for me during typical use. But, this is kind of ****ty build quality and i will have reservations about buying another device from samsung.
*(e.g. if i roll my hand across the screen this is the most common area for a touch to 'stick')

drdoombot said:
Strangely enough, I haven't been able to reproduce the issue since that first time. I use my Note 10.1 in a number of different places (lecture halls, library, home desk, etc.), but can't seem to make it happen again.
Click to expand...
Click to collapse
In situations where I wasn't able to reproduce the bug (that happened every once in a while) I used a simple workaround: lock+unlock the screen and the bug was reproducible again.
6pool said:
you aren't crazy
Click to expand...
Click to collapse
You're right. After realizing that the second device has the same bug, I was close to declaring myself mental.
6pool said:
I dont know about you guys but my note is pretty creaky
Click to expand...
Click to collapse
Mine too. It feels cheap and the only reason I bought it is because of the pen.
6pool said:
these issues are fortunately only an uncommon annoyance for me during typical use.
Click to expand...
Click to collapse
What's your typical use? My typical use was writing and said bug made that very inconvenient. It basically prevented me from using touch-input after writing only a couple of lines..
Maybe a short update: I returned the second device, got my money back, and sent the first device once again to $REPAIR_GUYS, this time with a link to the video above.
I'm also thinking about buying a Note 8 if I get refund for the first device.
Bottom line: The tablet was supposed to replace all the cumbersome paper I have to deliver every week and I'm out of a working device since end of january. A huge waste of money, time, time and time.

bergwitza said:
Mine too. It feels cheap and the only reason I bought it is because of the pen.
Click to expand...
Click to collapse
Yeah if it wasn't for the pen I bet most people would have gone for something more sturdy/better screen/stock android.
It literally is the only device which can do annotation anywhere near properly though so Its a matter of priorities.
bergwitza said:
What's your typical use? My typical use was writing and said bug made that very inconvenient. It basically prevented me from using touch-input after writing only a couple of lines..
Click to expand...
Click to collapse
Typical use has been taking lecture notes for several hours a day, managed a years worth of university with it, and while its not perfect
it did save my back from having to lug around lots of books and notes.
I would guess that this issue is present on all devices, just at differing scales. Hopefully you can find one where it is at a level that doesn't
bother you, though I wouldn't blame you for giving up and avoiding Samsung from now on, must be a right pain.
bergwitza said:
I'm also thinking about buying a Note 8 if I get refund for the first device.
Click to expand...
Click to collapse
I would say that if you are planning on using the note 8 for lots of writing, maybe try it in store first, its probably way too small for any prolonged period, I find the 10.1 cramped and I have relatively small hands/writing. (Not helped by the fact the pen digitizer gets weird towards the edges of the screen)
Anyways, good luck!

6pool said:
I would say that if you are planning on using the note 8 for lots of writing, maybe try it in store first, its probably way too small for any prolonged period, I find the 10.1 cramped and I have relatively small hands/writing. (Not helped by the fact the pen digitizer gets weird towards the edges of the screen)
Click to expand...
Click to collapse
I never really used the whole screen for writing for various reasons:
1. the pen is not precise somewhere around the middle of the screen
2. the pen is not precise at the edges (as you mentioned)
Reason 2 is something all wacom digitizers seem to share (I remember watching a guy on youtube demonstrating the "edge-effect" on the note and two other, professional wacom devices), reason 1 I can't explain.
Anyway, I always ended up just using the upper half of the screen and that's basically the main reason why I think it wouldn't make much of a difference. But on the other hand my gut tells me that you could be right.
Right now I can't shake the feeling that the note is just some random entity in Samsung's massive brute-force output. Never mind the details or the quality, after 5 different pen-tablets the fifth iteration will be just fine. Sounds a lot like Agile SW development.. just with hardware.

Same problem, demonstrated by someone else:

Have two tablets stock and no root. I have none of the described bugs and these 2 tablets are solid and very well built. Solid as any tab that I have owned. That is a strange problem and probable a batch built on Friday about quiting time.

None of those issues could have been reproduced on my Note 10.1 (GT-N8000) from Germany. Mine was bought in October 2012.
Sorry to hear that you have gotten two faulty devices :-/
Grüße aus Deutschland
Sent from my GT-N8000 using XDA Premium HD app

I have went through 3 of these tablets, ended returning each one to best buy. I absolutely love it for drawing and sketching....until the screens bugged up. All three of mine where the gray version, I'm tempted to pick up a white and give it a try.
Btw ...the second video posted in this thread is mine. :cyclops:

Interesting thread, after reading it I decided to test mine and it's not suffering with that bug, I'm in the UK and brought it 2 months ago, it's the grey variant
Sent from my GT-N8010 using Tapatalk 2

aaronbass said:
I have went through 3 of these tablets, ended returning each one to best buy. I absolutely love it for drawing and sketching....until the screens bugged up. All three of mine where the gray version, I'm tempted to pick up a white and give it a try.
Click to expand...
Click to collapse
Wait, are you saying that all 3 had the same bug?
ch0ka said:
None of those issues could have been reproduced on my Note 10.1 (GT-N8000) from Germany. Mine was bought in October 2012.
Sorry to hear that you have gotten two faulty devices :-/
Grüße aus Deutschland
Sent from my GT-N8000 using XDA Premium HD app
Click to expand...
Click to collapse
Smartie36 said:
Interesting thread, after reading it I decided to test mine and it's not suffering with that bug, I'm in the UK and brought it 2 months ago, it's the grey variant
Sent from my GT-N8010 using Tapatalk 2
Click to expand...
Click to collapse
Thanks to both of you for testing.

bergwitza said:
Wait, are you saying that all 3 had the same bug?
Thanks to both of you for testing.
Click to expand...
Click to collapse
Yep, all three had the same issue.
At first I thought the screen bug was from the tablet getting too hot while sketching (SketchBook). The tablet was pretty warm, not uncomfortable to touch or anything. Possibly overheating?
While streaming Netflix, the touch dots would randomly appear and not go away. The tablet wasn't warm like before when I was sketching and it wasn't even being touched.
Still tempted to try another one, i did love it when it was working and there aren't any other android devices sporting the wacom digitizer

Update:
After almost four months, some Samsung technician/representative reluctantly decided to issue a refund. Reluctantly because, and I quote, out of 100 times he tried to reproduce the bug demonstrated in not one but two videos.. he succeeded only once.
Not really satisfying but, oh well, if they dont give a f.., I won't either.

Any updates
Hi
I bought this Note for my girlfriend as a Christmas gift. She's loaded a few apps and mainly uses it to look up stuff on the web, FaceBook and things like that. The issue is the screen starts twitcihing and types random letters and will switch pges and change settings. I did a factory reset via the reset option in the settings tab. That did not help. I will post a video tonight showing the issue. Are there any other option out there??!!
Thanks
Dash

Touchscreen fixed with better USB cord on Note 10.1 2014
I have the same issue on Note 10.1 2014 SM-P605.
I've tried changing apps, dozens of keyboard settings, device covers, screen protectors, pen input, finger input, touching the corners to recalibrate, turning the divice upside down, locking, unlocking, running different tabs in chrome...way too much time on this issue.
Finally I found the cause.
A cheap monoprice USB cable attached will produce the problem 100% of the time.
Using a heafty stock USB cable works 100% of the time.
I spent three days setting up this new tablet. And it worked flawlessly, until the last day when I moved to a new room.
Now I'm loving it again.

i have problem in touch in several flashing my touch not working anymore anyone can spare me a helping hand to solve this issue sorry for my bad

Touch Screen Dead-Zone

Lately (since oreo i believe), a lot of phones affected by this weird bug. When you touch the screen, and move your finger really slowly, the OS ignores that slight accurate movement. After a couple of milimeters movement, it then recognize the movement, creating a sudden jump in detection .
It is not a sensitivity issue, because right after you touch the screen, it detects your finger. But the OS maybe choose to disregard that slight accurate movement as accidental.
In my experience, the same thing occurs in Sony XZ2, P20 Pro (now fixed since 120 firmware), in smaller extent in Mix 2s, and yes in OP6 as well (alo not as pronounced but definitely there).
Most users wont be aware of this issue, but avid fps gamers who needs accurate aiming might be troubled in getting their frags.
Check out these videos, one is of oneplus 6, and the other one as a comparison pixel 2 xl with almost zero deadzone.
Oneplus 6
Pixel 2 XL
Anyone else experiencing this "problem"? Still experiencing it on 5.1.6 ..
Huawei recognized this problem and fixed it. So this bug is definitely fixable.
Here is the thread from p20 pro forum
Here is the thread from XZ2 forum

Just test it with the multi-touch app and i can see it too.
But honestly, I was not aware of the issue. I didn't notice a thing in normal use.
Have you reported this to OP?

tWoBrO said:
Just test it with the multi-touch app and i can see it too.
But honestly, I was not aware of the issue. I didn't notice a thing in normal use.
Have you reported this to OP?
Click to expand...
Click to collapse
Yes under normal daily use it is definitely not noticeable..
Btw, how to report to OP? Oneplus forums?

I have it as well,
Mine is very annoying because every content that I wanna see is very frustrating because every tiny bit of a swipe makes the page go down or up a lot and fast
Is there any fix to that?

Allesa said:
Yes under normal daily use it is definitely not noticeable..
Btw, how to report to OP? Oneplus forums?
Click to expand...
Click to collapse
Here: https://forums.oneplus.com/feedback
They usually contact you in private for more info. Logs and stuff.

https://forums.oneplus.com/threads/touch-screen-latency-deadzone.851559/
Done.. Hopefully they recognize the problem and escalate this.. Loving the phone, but too bad it's unusable to play my kind of games

No one else have an issue with is? Or not a lot of pubg gamers around here?

no issues with pubg here, maybe the custom kernel fixes the issue? not sure but its really responsive with me on blu_spark

virtyx said:
no issues with pubg here, maybe the custom kernel fixes the issue? not sure but its really responsive with me on blu_spark
Click to expand...
Click to collapse
if you touch, hold, slowly slide your thumb to aim, will it follow instantly? Or does it have slight delay until it recognize your precise movement?

just a shot in the dark , But try disabling pocket mode under advance see if that makes a difference.

Feedback regarding touches on 8.12.13

Here's my observation so far after clean flashed 8.12.13 from 8.12.10
-Multi touches/Ghost touch and screen freezes is reduced on 8.12.13 compared to 8.12.10 BUT it's still there and most of the time it happens slightly below the notch and sometimes around the navbar. Playing games causes the notification bar to pop up out of nowhere :\
-Screen flicker is not yet fixed.
-Touch sensitivity isn't the same as 8.12.10 which has the best touch respond time and so smooth and the UI feels heckin smooth but at 8.12.10 there's A LOT
multi touch/ghost touches and screen freezes.
-Aiming in PUBG doesn't feel smooth and snappy as 8.12.10.
-The navbar isn't responsive like in 8.11.15
-Mistouches is still here
Overall touch issues is 'fixed' for me about 80% and this is coming from a user that has been *****ing about touch issues from day 1 so yeah.
Games are somehow more playable.
I know it's beta and I wrote this if anyone or the devs wants know some feedback on this beta
My Pocophone f1 is around September batch and made in China btw.
I wished the devs fixed the multi touch/screen freezes issue while keeping the touch senstivity from 8.12.10 on the next beta update and it'll be perfect (without breaking other parts ofcourse)
Also is there any links to submit a feedback regarding touches? If so please do put it here as I wanna give my feedback

What you mean about flicker not fixed? I have been like crazy trying to find a fix for getting Android Auto to work as it is meant to - currently the device flickers a lot and eventually screen goes blank when using Android Auto.
...haven't tried yet the latest 8.12.13 - just flashed it alone with latest LOS16 and now need to go to car and see if there is any improvements

Yep.
For me, .10 was better than .13

Jaco2k said:
What you mean about flicker not fixed? I have been like crazy trying to find a fix for getting Android Auto to work as it is meant to - currently the device flickers a lot and eventually screen goes blank when using Android Auto.
...haven't tried yet the latest 8.12.13 - just flashed it alone with latest LOS16 and now need to go to car and see if there is any improvements
Click to expand...
Click to collapse
Do give us a feedback after flashing latest LOS16.

I was on 100% stock rom 8.12.13, no problems at all and enjoying it.
Sent from my POCOPHONE F1 using Tapatalk

My girlfriend tried it on the car and the combination of LOS 16 with Firmware 8.12.13 also with Franco Kernel r7 and with HW overlays disabled in Developer settings seems to have done the trick.
Now I need to remove/disable a few of those things one by one to see what really solved it - my money is on the HW overlays disabled.

Jaco2k said:
My girlfriend tried it on the car and the combination of LOS 16 with Firmware 8.12.13 also with Franco Kernel r7 and with HW overlays disabled in Developer settings seems to have done the trick.
Now I need to remove/disable a few of those things one by one to see what really solved it - my money is on the HW overlays disabled.
Click to expand...
Click to collapse
Solved the screen flickers or android auto?

misleaded said:
Solved the screen flickers or android auto?
Click to expand...
Click to collapse
Yes. Working now as it should, but still not sure what exactly solved it.
---------- Post added at 10:51 AM ---------- Previous post was at 10:41 AM ----------
Jaco2k said:
Yes. Working now as it should, but still not sure what exactly solved it.
Click to expand...
Click to collapse
...and sooner I wrote it...
She just called saying that it is flickering again. The only thing that changed there was updating Magisk and rebooting the phone.
I am pretty sure that when you reboot the phone it resets the HW overlay setting in Developer options, so that seems to be the key to the flickering problem.
Would be good to see a more permanent fix than needing to resort to this hack.

Has anyone flashed 8.12.20? Is there any improvement

Xiaomi doesn't have a factory for making phones and their production is also the inventory model, no stocks or parts or phones. They just commission batches of phones at different times for the same models, according to large combined orders, probably in differing workshops if demand is high. So quality can vary.
Xiaomi also make little or as reported no real profit from phones, they use the phones as brand advertising and make money from their numerous branded trinkets. This is a well known fact in the Asian business world. They don't spend tens of millions or billions on advertising like other big names. Their phones' models at cheap prices is their advertising which costs them nothing. This is their strategic PR & primary business model. They also enjoy bothering giants like Apple Google Samsung Huawei ZTE by being market disrupters in this way, cutting their profits by competitive pricing, at cost.
So each batch of Pocophone could, and is probably, a different phone specially if fixing teething problems in the first few months of a new model.
So XDA users giving feedback on all these Pocophone threads about problems with screen, touch, delay, random reboot etc. should give their rough purchase date and seller's identity+location. Otherwise everyone is talking about different phones.
That could be why recent buyers are facing little to no problems. I suspect Xiaomi have been fixing problems by replacing the faulty parts (screens etc) or assembly processes as well as kernel/ROM/drivers with better hardware & software & assembly guidelines. Probably with feedback from here, MIUI forums, etc.
But Xiaomi seem to be doing this secretly, which happened to previous models too, in order not to damage their reputation. So they can claim to problematic users, it's just your problem, Look at others. Did you damage your phone? This adds to the confusion of people talking about (in effect) different Pocophone builds & hardware. This confusion also helps Xiaomi escape blame.
Lesson 1:
When Xiaomi brings out a new phone, wait at least 4 to 6 months, for them to fix teething issues in their haphazardly commissioned assembly batches.
+
It'll be also cheaper by then.
Lesson 2:
There is no standard Pocophone, after a few months the next wave of ordered batches could, and are probably, a different model, a slightly different Pocophone. With evolving parts & code & possibly even different hardware parts. Even if it's just a different assembly workshop or team or process with a different quality control.

wozhere said:
Xiaomi doesn't have a factory for making phones and their production is also the inventory model, no stocks or parts or phones. They just commission batches of phones at different times for the same models, according to large combined orders, probably in differing workshops if demand is high. So quality can vary.
Xiaomi also make little or as reported no real profit from phones, they use the phones as brand advertising and make money from their numerous branded trinkets. This is a well known fact in the Asian business world. They don't spend tens of millions or billions on advertising like other big names. Their phones' models at cheap prices is their advertising which costs them nothing. This is their strategic PR & primary business model. They also enjoy bothering giants like Apple Google Samsung Huawei ZTE by being market disrupters in this way, cutting their profits by competitive pricing, at cost.
So each batch of Pocophone could, and is probably, a different phone specially if fixing teething problems in the first few months of a new model.
So XDA users giving feedback on all these Pocophone threads about problems with screen, touch, delay, random reboot etc. should give their rough purchase date and seller's identity+location. Otherwise everyone is talking about different phones.
That could be why recent buyers are facing little to no problems. I suspect Xiaomi have been fixing problems by replacing the faulty parts (screens etc) or assembly processes as well as kernel/ROM/drivers with better hardware & software & assembly guidelines. Probably with feedback from here, MIUI forums, etc.
But Xiaomi seem to be doing this secretly, which happened to previous models too, in order not to damage their reputation. So they can claim to problematic users, it's just your problem, Look at others. Did you damage your phone? This adds to the confusion of people talking about (in effect) different Pocophone builds & hardware. This confusion also helps Xiaomi escape blame.
Lesson 1:
When Xiaomi brings out a new phone, wait at least 4 to 6 months, for them to fix teething issues in their haphazardly commissioned assembly batches.
+
It'll be also cheaper by then.
Lesson 2:
There is no standard Pocophone, after a few months the next wave of ordered batches could, and are probably, a different model, a slightly different Pocophone. With evolving parts & code & possibly even different hardware parts. Even if it's just a different assembly workshop or team or process with a different quality control.
Click to expand...
Click to collapse
Mahn i hear you loud and clear. But when life gives you lemons... you gotta learn to make lemonade rt? Thats why this thread was created. unless and until xiaomi acknowledges this issue its our own problem. What better can we do than to try out their so called 'fixes'. Replacement would be bigger blunder since we would prolly get more defective ones only. Thats simply the reason why i 've asked if there is any improvement with the latest build and i sincerely expect an answer from users like me who experience a genuine issue of ghost touches and freezes that render the phone rather difficult to use in the first place. Others tryn these builds would report them better than last ones as they do not have the issue in the first place.. i believe it is the initial batches of the phones that experience such issues.
Still waiting for a remark..

jomin_995 said:
Mahn i hear you loud and clear. But when life gives you lemons... you gotta learn to make lemonade rt? Thats why this thread was created. unless and until xiaomi acknowledges this issue its our own problem. What better can we do than to try out their so called 'fixes'. Replacement would be bigger blunder since we would prolly get more defective ones only. Thats simply the reason why i 've asked if there is any improvement with the latest build and i sincerely expect an answer from users like me who experience a genuine issue of ghost touches and freezes that render the phone rather difficult to use in the first place. Others tryn these builds would report them better than last ones as they do not have the issue in the first place.. i believe it is the initial batches of the phones that experience such issues.
Still waiting for a remark..
Click to expand...
Click to collapse
Yes that's why I really started that post and it got long: to ask people posting to say when they got the phone and preferably location and seller too. Not to mention ROM/drivers/fixes flashed. Then the faulty batch can be traced. But yeah, that is really sneaky of Xiaomi to pretend there was nothing wrong and it is all the users' fault. Then Xiaomi can be told look, the people who bought it at period X got screwed with this fault, by Xiaomi and:
1) What are they going to do about it
+
2) if there are fixes or tips or solutions by guys and girls here too
But a lot of fixes have been found thanks to threads like this or at least Xiaomi have been shown to be at fault, not the poor buyers. So well done Bro.

if you feel touch issue is still there with 8.12.20 confirm/report here
http://en.miui.com/forum.php?mod=viewthread&tid=5003318

jineshpatel30 said:
if you feel touch issue is still there with 8.12.20 confirm/report here
http://en.miui.com/forum.php?mod=viewthread&tid=5003318
Click to expand...
Click to collapse
Sure. I will

mine it's arriving the next the first week of january, this it's the version ive got, i'm not sure about the spanish text film, in all the reviews you'll see the text in english (the classic gearbest version) bought mine on amazon.com, my cousin says she dont feel any problem with the screen but i don't know, will be updating when i got it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

jineshpatel30 said:
if you feel touch issue is still there with 8.12.20 confirm/report here
http://en.miui.com/forum.php?mod=viewthread&tid=5003318
Click to expand...
Click to collapse
done, hope something can be done abt this

I think it is only the first few batches of phones that are affected right? Maybe creating a separate thread with this link to report will help to identify more people experiencing similar issues. lodging a mass complaint would make xiaomi to atleast acknowledge the hardware issue...

I just bought this phone for a week. Did not notice any touch issue yet appart from typing error ( might be because im not used to larger screen phone) . Tested official stable and latest open beta. Maybe the issue is there,but because im not into gaming i never noticed that. The only thing that i can confirm is,this phone scrolling is sluggish compared to last year pixel 2. But overal for the price im quite satisfied with this phone. If it could be better,then its wonderful.. cheap and fast phone for us all.

Touch lag issue is back on 8.12.27 firmware.
Why they introduced back it again ?
Anyone have any info ?
You can easily feel difference in keyboard and pubg, and also on edges of screen.

RohanAJoshi said:
Touch lag issue is back on 8.12.27 firmware.
Why they introduced back it again ?
Anyone have any info ?
You can easily feel difference in keyboard and pubg, and also on edges of screen.
Click to expand...
Click to collapse
I think below discussion will be helpful
Here is the whole story of tuch issues and screen bleeding issues :-
1) first batch - Xiaomi was using screen from some supplier and it had screen bleeding. (users facing screen bleeding but no touch issues)
2) Second Batch - Later xiaomi changed the whole panel and this time they fixed the screen bleeding but got the touch issues. (users facing touch issues but no screen bleeding like me)
3) Third and latest batch - Later again xiaomi changed the touch panel and this time they fixed all the above issues. (third batch users facing no issues, neither screen bleeding nor touch issues, mostly from outside of India pocophone f1 users and poco f1 users in India having October or later manufactured device)
4) Now xiaomi is trying to fix the touch issue for second batch user by changing kernel values because screen bleeding can't be fixed by software updates.
5) if xiaomi fixes the issues for second batch people by increasing the current supply for touch planel to reduce touch delays by tweaking kernel then first batch people starts having issues like ghost touches because of over sensitivity due to over current values.
6) if xiaomi tries to fix the issues for the first batch people by reducing the current for touch panel again by tweaking kernel values then second batch people starts having issues like touch delay and lake of touch sensitivity because of reduced current values.
7) Meanwhile the third batch people has average values so they don't get affected by any of the above kernel changes so they didn't had any kind of touch issues in any of the build.
8) Because there are three different touch panels being used for poco f1 and each one is using different current values its very difficult to control all of them from the same kernel value or by a universal Rom.
9) Xiaomi can provide the device specific build like different-different kernel values for different touch panel devices.
Disclaimer - Above are my personal observations, nothing is confirmed by xiaomi officials and i may be wrong so don't take it seriously
Click to expand...
Click to collapse
Oh they bring back feelings for touch on 8.12.27 the touch frimware on this version are perfect
Click to expand...
Click to collapse
Is that a joke or are you serious? Some reported the touch response is bad on 8.12.27
Click to expand...
Click to collapse
I update my phone and i confirm the touch lag is back.
Click to expand...
Click to collapse
My phone never had issue before when i was on miui 9 but when they start to play on touch firmware its become so sensitive and the touch not that good on home screen they shift to left when i press on icons but now i dont face any issue maybe my phone hardware not have issues u have guys
Click to expand...
Click to collapse
For me also touch responsiveness seem much better on 8.12.27 than 8.12.20/24.
There was visible lag for me in last builds but now it works much faster.
BTW I read somewhere that they changed the OTA file in morning with same No. 8.12.27 due to some bug. But i just downloaded and flashed the one that's currently available on xiaomi website. Give it a try once again and see it's still giving you touch issue or not, because for me it's working much better compared to previous builds. (though still not as responsive as 10.1.3 stable )
Yes they changed the OTA file. I recently updated and touch seems to be good so please redownload the whole update and update it. They suspended the morning build and know its live again with the new tweaked kernel with the same number 8.12.27 and it doesn't have touch issue and icon flickering is also gone
Click to expand...
Click to collapse

Touch latency

I was having a tough time typing fast on the phone and made a post about it earlier. Trying to look for the issue, I came across these
https://www.reddit.com/r/Xiaomi/comments/9ntl73/is_your_device_affected_by_touch_latency_issues/
https://www.reddit.com/r/Xiaomi/comments/a1m7ao/xiaomi_mi_a2_touch_latency/
Surprisingly, the behaviour is quite similar to these threads here. I request xda users with a redmi note 7/ 7 pro to carry out this small test of trying to type the words 'qu' and 'scope' fast (if possible, try to run this test a few times with space after each qu and scope, say 10 times, so that we can be sure that the results are consistent and do remember to type the same word 10 times consecutively and then move on to the other word and type it ten times consecutively) and report how many times it turns out as uq and scoep on doing so.
Please mention if you tried this test with:
a screen protector installed (also mention the type of screen protector, i.e. tempered glass or plastic) or without one
your device variant (indian or chinese) and
if possible your display manufacturer which should appear after typing *#*#6484#*#* in dialer and going to software information> lcm information
If you have any other devices, try this on them as well and report how it goes, so that we can have some reference points.
For reference my device is redmi note 7 pro indian variant with edge to edge tempered glass protector installed, lcm information: nt36672a shenchao panel.

Hello sir/ma'am, i just tried this "test" and i found no such issues on my device. If it is of any importance, my device is a chinese one.

1375965485501144093271341 said:
Hello sir/ma'am, i just tried this "test" and i found no such issues on my device. If it is of any importance, my device is a chinese one.
Click to expand...
Click to collapse
Thanks for reporting sir/ma'am. Do you have any screen protectors installed? (If yes, tempered glass or plastic)
Your device variant description was indeed important, I'll update the original post requesting to include device variant as well.
Could you also provide the display manufacturer details? It should be appear after typing *#*#6484#*#* in dialer and going to software information> lcm information.

Deleted

I am not using any screen protectors on my device (PRO), sir/ma'am. The info you requested: nt3672a video mode dsi schenchao panel

1375965485501144093271341 said:
I am not using any screen protectors on my device (PRO), sir/ma'am. The info you requested: nt3672a video mode dsi schenchao panel
Click to expand...
Click to collapse
Thanks kind sir/ma'am. Could you also try typing scope fast for a few times and report what you observe?
Both of our devices have panels from the same manufacturer but mine has nt36672a instead.

I am sorry sir/ma'am, i made a typo in my last sentence. The display in my device also has a nt36672a designation. As far as typing scope, no mater how fast i try to type it, it always gets registered without any problems. I can not produce the issue you and some other users are facing.

I an facing a similar issue my is the global varient of note 7 pro and its lags during typing and i am using full screen tempered glass

kingd0097 said:
I an facing a similar issue my is the global varient of note 7 pro and its lags during typing and i am using full screen tempered glass
Click to expand...
Click to collapse
So far, atleast 3 confirmed cases including mine.

Display: nt26672a video mode dsi shenchao panel.
Screen protector: none.
Device and rom: Chinese
I used Poco F1 which does not have any sort of touch problems. Always wondered that the fuss was about then this N7P.
There is certainly a touch delay which is worse if you use a keyboard with vibration: the mismatch between actual touch and vibration makes it feel like you are using a juice-spilled keyboard. I overcame this issue by greatly reducing strength of vibration and typing a bit slowly.
What still get me is its touch scroll behavior. Short fling, especially bottom to up, does not move screen in a smooth way. Rather, it scrolls a bit then abrupt break. Worse is when you are using Instagram. When you swipe left or right to see the next picture, it will show about 1/4 of it then jump back to previous one. Very annoying. Overall, it feels like I am using a phone with outdated CPU.
With Poco F1, this sort of touch problems were addressed heavily which lead Xiaomi to come up with fixes. I do not expect that will be the case with N7P. I am hoping that changing touch friction and scroll fling values in buildprop would at least make it less annoying. I may try that once I get unlocked.

I do not have the same issue, I use SwiftKey as my keyboard though if that makes any difference.
Have the RN7 Pro Chinese version with no screen protector.
I can't get the screen info, when I copy / paste the code and dial it does not complete?
That being said I have felt as if SwiftKey is a little laggy on my previous phone and it's better on the RN7 Pro - although not as smooth as on my Mi 5 I use to have.
Sent from my Redmi Note 7 Pro using Tapatalk

4K2K said:
Display: nt26672a video mode dsi shenchao panel.
Screen protector: none.
Device and rom: Chinese
I used Poco F1 which does not have any sort of touch problems. Always wondered that the fuss was about then this N7P.
There is certainly a touch delay which is worse if you use a keyboard with vibration: the mismatch between actual touch and vibration makes it feel like you are using a juice-spilled keyboard. I overcame this issue by greatly reducing strength of vibration and typing a bit slowly.
What still get me is its touch scroll behavior. Short fling, especially bottom to up, does not move screen in a smooth way. Rather, it scrolls a bit then abrupt break. Worse is when you are using Instagram. When you swipe left or right to see the next picture, it will show about 1/4 of it then jump back to previous one. Very annoying. Overall, it feels like I am using a phone with outdated CPU.
With Poco F1, this sort of touch problems were addressed heavily which lead Xiaomi to come up with fixes. I do not expect that will be the case with N7P. I am hoping that changing touch friction and scroll fling values in buildprop would at least make it less annoying. I may try that once I get unlocked.
Click to expand...
Click to collapse
I don't use vibrate on keypress but I still face the issue.
For Instagram, I just downloaded it to check that out and I too experience that sometimes it does not move to the next image and even moves backwards/to the previous image instead. One more thing I noticed was, on Instagram, when you go to explore and are checking posts which have 'more' (large amount of text and hence the option to read 'more') in their descriptions, it often jumps to the next post instead of allowing you to read more of what is written in the description, almost feels like the touch accuracy is off or might be just an Instagram thing.
Scrolling is also a bit inconsistent, on short flings, it sometimes moves downwards and then upwards a bit and at times it scrolls in the opposite direction (but that is rare).

PsyCLown89 said:
I do not have the same issue, I use SwiftKey as my keyboard though if that makes any difference.
Have the RN7 Pro Chinese version with no screen protector.
I can't get the screen info, when I copy / paste the code and dial it does not complete?
That being said I have felt as if SwiftKey is a little laggy on my previous phone and it's better on the RN7 Pro - although not as smooth as on my Mi 5 I use to have.
Click to expand...
Click to collapse
You can access this through settings> about phone> kernel version (tap a few times)> software version> lcm information. Thanks for the feedback.

kakatorres1999 said:
You can access this through settings> about phone> kernel version (tap a few times)> software version> lcm information. Thanks for the feedback.
Click to expand...
Click to collapse
Nt36672a
Sent from my Redmi Note 7 Pro using Tapatalk

kakatorres1999 said:
I don't use vibrate on keypress but I still face the issue.
For Instagram, I just downloaded it to check that out and I too experience that sometimes it does not move to the next image and even moves backwards/to the previous image instead. One more thing I noticed was, on Instagram, when you go to explore and are checking posts which have 'more' (large amount of text and hence the option to read 'more') in their descriptions, it often jumps to the next post instead of allowing you to read more of what is written in the description, almost feels like the touch accuracy is off or might be just an Instagram thing.
Scrolling is also a bit inconsistent, on short flings, it sometimes moves downwards and then upwards a bit and at times it scrolls in the opposite direction (but that is rare).
Click to expand...
Click to collapse
Yes, that is the issue. It is too bad that the phone failed QC this bad; otherwise, it would have been a great phone.
BTW, is your phone unlocked? Are you using a Chinese version of the phone. I am wondering if changing to Indian rom or different roms would fix this issue.

4K2K said:
Yes, that is the issue. It is too bad that the phone failed QC this bad; otherwise, it would have been a great phone.
BTW, is your phone unlocked? Are you using a Chinese version of the phone. I am wondering if changing to Indian rom or different roms would fix this issue.
Click to expand...
Click to collapse
No, my phone isn't unlocked and I mentioned in the OP that I have an Indian variant.

I am also facing the same issue my varient is Redmi note 7 pro india 4/64gb

kakatorres1999 said:
I was having a tough time typing fast on the phone and made a post about it earlier. Trying to look for the issue, I came across these
https://www.reddit.com/r/Xiaomi/comments/9ntl73/is_your_device_affected_by_touch_latency_issues/
https://www.reddit.com/r/Xiaomi/comments/a1m7ao/xiaomi_mi_a2_touch_latency/
Surprisingly, the behaviour is quite similar to these threads here. I request xda users with a redmi note 7/ 7 pro to carry out this small test of trying to type the words 'qu' and 'scope' fast (if possible, try to run this test a few times with space after each qu and scope, say 10 times, so that we can be sure that the results are consistent) and report how many times it turns out as uq and scoep on doing so.
Please mention if you tried this test with:
a screen protector installed (also mention the type of screen protector, i.e. tempered glass or plastic) or without one
your device variant (indian or chinese) and
if possible your display manufacturer
If you have any other devices, try this on them as well and report how it goes, so that we can have some reference points.
For reference my device is redmi note 7 pro indian variant with edge to edge tempered glass protector installed.
Click to expand...
Click to collapse
Indian variant 4/64
NT36672a
Edge to edge tempered glass applied
4/10 times I was failed to type scope... Sometimes it registered scoep and sometimes e was never registered.

AbhiAbhiBisht said:
Indian variant 4/64
NT36672a
Edge to edge tempered glass applied
4/10 times I was failed to type scope... Sometimes it registered scoep and sometimes e was never registered.
Click to expand...
Click to collapse
Quite similar experience to mine except mine has a tendency to miss a's instead of e's.

Indian variant here, with shenchao panel, touch latency issues are there typing scope faster makes it scoep and also 4-5 times out of 10 times typing qt makes it tq
I have installed screen protector though
Issues are similar to my friends pocofone

Any known issues?

Hey guys. Have currently ordered my new 12 gb one plus 7 pro nebula blue and I can't wait till it arrives but had a quick question for everyone......
Has anyone noticed any major or minor bugs or glitches on the phone?
I'm coming from a huawei p20 pro and I know the os and everything is going to feel fluid and google like but it's a major step for one plus to go to a curved display and 2k display and 90 hertz display so it could be little experimental but I was just wondering if anyone was having any issues with the phone if they don't mind sharing. I would love to know.
I'm sorry if I put a duplicate thread but didn't notice a thread with bugs and issues.
And I did see online that people were experiencing "phantom" touches issues and was wondering if anyone else was having that issue and what I need to do to avoid it from happening to my phone.
Thanks in advance

zizzyboi said:
Hey guys. Have currently ordered my new 12 gb one plus 7 pro nebula blue and I can't wait till it arrives but had a quick question for everyone......
Has anyone noticed any major or minor bugs or glitches on the phone?
I'm coming from a huawei p20 pro and I know the os and everything is going to feel fluid and google like but it's a major step for one plus to go to a curved display and 2k display and 90 hertz display so it could be little experimental but I was just wondering if anyone was having any issues with the phone if they don't mind sharing. I would love to know.
I'm sorry if I put a duplicate thread but didn't notice a thread with bugs and issues.
And I did see online that people were experiencing "phantom" touches issues and was wondering if anyone else was having that issue and what I need to do to avoid it from happening to my phone.
Thanks in advance
Click to expand...
Click to collapse
Hi,
I actually have ghost touch issues, and it seems a lot of people also got it, if not everyone. But due to the fact it happens under some condition, not everybody seems to be aware of it. You have to run your screen at 90Hz, with NFC enable, and launch some specific apps like CPU-Z or reddit for it to happens, because it seems the issue come from the NFC. I heard it was a software issue and Oneplus is working on it, and I hope it is, because if it's an hardware issue, I will sell my phone.
Well, if you can deal with this ATM, this is a very nice phone, I sold my S10 to get this one and I'm absolutely not disappointed!

Dat.Silhouette said:
Hi,
I actually have ghost touch issues, and it seems a lot of people also got it, if not everyone. But due to the fact it happens under some condition, not everybody seems to be aware of it. You have to run your screen at 90Hz, with NFC enable, and launch some specific apps like CPU-Z or reddit for it to happens, because it seems the issue come from the NFC. I heard it was a software issue and Oneplus is working on it, and I hope it is, because if it's an hardware issue, I will sell my phone.
Well, if you can deal with this ATM, this is a very nice phone, I sold my S10 to get this one and I'm absolutely not disappointed!
Click to expand...
Click to collapse
So if I understood correctly. You're saying it is possible because of nfc connection being on?
It disappears if nfc is off? I barely use nfc anyways so hopefully my phone will be fine.
And hopefully it is software and not hardware issue. That would suck as I can't return it where I am atm and will have to wait a month or so before I can if it's hardware issue.
And to my understanding.... Oneplus had a software update that improved camera and performance etc... Did you install it and have you noticed the ghost issue gone or still present in the new update?
Thanks for the update

zizzyboi said:
Hey guys. Have currently ordered my new 12 gb one plus 7 pro nebula blue and I can't wait till it arrives but had a quick question for everyone......
Has anyone noticed any major or minor bugs or glitches on the phone?
I'm coming from a huawei p20 pro and I know the os and everything is going to feel fluid and google like but it's a major step for one plus to go to a curved display and 2k display and 90 hertz display so it could be little experimental but I was just wondering if anyone was having any issues with the phone if they don't mind sharing. I would love to know.
I'm sorry if I put a duplicate thread but didn't notice a thread with bugs and issues.
And I did see online that people were experiencing "phantom" touches issues and was wondering if anyone else was having that issue and what I need to do to avoid it from happening to my phone.
Thanks in advance
Click to expand...
Click to collapse
From my understanding the phantom touches issue is very rare. I havent havent had the issue. The only bug I have noticed is when a phone call ends, youre always taken back to the homescreen. So if youre on twitter or playing a game, once the call ends any app will auto close. Its annoying but nothing crazy and will most likely be fixed soon.

whatthekj said:
From my understanding the phantom touches issue is very rare. I havent havent had the issue. The only bug I have noticed is when a phone call ends, youre always taken back to the homescreen. So if youre on twitter or playing a game, once the call ends any app will auto close. Its annoying but nothing crazy and will most likely be fixed soon.
Click to expand...
Click to collapse
First time hearing about that one. But thanks for you input.
Not a deal breaker for me but I can see how that can get annoying.
Have you or anyone noticed the earpiece random noises when on the call like other people have?
Or it's just device specific?
I bought the phone Friday when it came out. So I'm scared I bought the phone too soon and I might get more bugs on my phone that anyone else's but only time will tell when I get the device in hand.
(I ordered it early but since I'm in Africa right now, I had to ship it to USA international then ship from there to me using a third party delivery shipping service. That's why I haven't received the phone yet and have been waiting for a while)

whatthekj said:
From my understanding the phantom touches issue is very rare. I havent havent had the issue. The only bug I have noticed is when a phone call ends, youre always taken back to the homescreen. So if youre on twitter or playing a game, once the call ends any app will auto close. Its annoying but nothing crazy and will most likely be fixed soon.
Click to expand...
Click to collapse
Yep, no issues for me at all.
Sent from my GM1915 using Tapatalk

zizzyboi said:
First time hearing about that one. But thanks for you input.
Not a deal breaker for me but I can see how that can get annoying.
Have you or anyone noticed the earpiece random noises when on the call like other people have?
Or it's just device specific?
I bought the phone Friday when it came out. So I'm scared I bought the phone too soon and I might get more bugs on my phone that anyone else's but only time will tell when I get the device in hand.
(I ordered it early but since I'm in Africa right now, I had to ship it to USA international then ship from there to me using a third party delivery shipping service. That's why I haven't received the phone yet and have been waiting for a while)
Click to expand...
Click to collapse
No I haven't had the earpiece bug either. Just the call ending issue.

whatthekj said:
No I haven't had the earpiece bug either. Just the call ending issue.
Click to expand...
Click to collapse
That's good. Fingers crossed mine doesn't have any issues. My first oneplus device.
I've always wanted oneplus for their speed and oxygen os.
And the 7 pro really sold me with the 90hertz and that amazing speed and display.
I can't wait for the device to come in.
When did you buy and get the device? Ddi you guys order on Friday when it got out on the store like me or were you guys at the pop up event in New York or other places?

zizzyboi said:
That's good. Fingers crossed mine doesn't have any issues. My first oneplus device.
I've always wanted oneplus for their speed and oxygen os.
And the 7 pro really sold me with the 90hertz and that amazing speed and display.
I can't wait for the device to come in.
When did you buy and get the device? Ddi you guys order on Friday when it got out on the store like me or were you guys at the pop up event in New York or other places?
Click to expand...
Click to collapse
Yeah this is my first OnePlus device as well. I just switched from a Note 8 so I was already used to the edge display and I can say the edge display on this device is much better. The speed with 90hertz is also amazing and you can really tell the difference from 60hertz. The display is also great. With the front camera hidden inside the phone, the phone really feels like it is all display. Also the phone gets really bright making it easier to see in direct light and the night mode to tone down the blue light.... The greatest. I have sensitive eyes so looking at bright things at light was a rarity for me but this device can get really dark compared to phones Ive used in the past.
Anyways, I bought the phone the Friday when it went on sale. I had a lot of faith in OnePlus after hearing it do so well the past few years so I took the chance and got it.

whatthekj said:
Yeah this is my first OnePlus device as well. I just switched from a Note 8 so I was already used to the edge display and I can say the edge display on this device is much better. The speed with 90hertz is also amazing and you can really tell the difference from 60hertz. The display is also great. With the front camera hidden inside the phone, the phone really feels like it is all display. Also the phone gets really bright making it easier to see in direct light and the night mode to tone down the blue light.... The greatest. I have sensitive eyes so looking at bright things at light was a rarity for me but this device can get really dark compared to phones Ive used in the past.
Anyways, I bought the phone the Friday when it went on sale. I had a lot of faith in OnePlus after hearing it do so well the past few years so I took the chance and got it.
Click to expand...
Click to collapse
Yea those are some of the reasons I got the phone as well. I'm coming from a used huawei p20 pro, a phone my brother passed on to me when he got the new mate 20 pro.
I've never bought a new phone. My first phone I ever bought was on contract which was the LG g4. Loved the curved back but screen didn't last for me (only one year in a 3 year contract at the time) then was using my back up phones until my brother gave me his p20 pro.
I've always wanted to try a curved screen display rather than curved back.
And I've been following one plus for a while, (I even got a referral for the oneplus one when they had a refferal service) but ended up selling it to someone else because I didn't trust oneplus back then but then after the other devices from one plus came out then I slowly gained interest.
And this oneplus 7 pro really caught my attention but these issues and bugs everyone is experiencing is really scaring me. If it's a hardware issue then I would have to take a long process to return the phone and I really don't want to do that.
Really hope it's a software issue and can get fixed in a future software update.
Or if I don't get the issues at all then that would be even better. Fingers crossed and will update the forum when my phone comes in.
I don't use the cpu app nor do I use nfc. So hopefully I don't encounter the issues but let's see. You never know

And how is the new update? Worth updating or made it worse?
Usually it's better but some people have been experiencing issues idk
Would love your input whether to skip that update when my phone comes or to download it right away