Related
Recently, I've been considering getting a Nexus One, however, most of the reviews I read say that the N1's capacitive buttons are a little unresponsive. You must tap the upper half of the button as opposed to the bottom half of the button.
I've also read that some of the cyanogen roms have fixed this problem. Can anyone give me more insight on this issue?
I've never had a problem with mine.
I saw a review saying that they got in the way when typing w/ the onscreen keyboard, but I haven't even had that, and I'd like to think that I have pretty normal-sized fingers.
Some people have problems, others don't i personally haven't. I wouldn't consider it to be something important enough to sway me from a sale though.
Stock Rom had this issue. If you unlock your bootloader, all the kernels (and mods) available now have a fix for this, as well as a few other things.
Im sure when 2.2 update comes out this fix will be passed on to the stock version too (at least as far as im aware it hasnt already!?). So tbh this isnt an issue for you not to get a nexus one...also, there's no point getting a nexus one if ur too scared to unlock the bootloader!!
adam18488 said:
Stock Rom had this issue. If you unlock your bootloader, all the kernels (and mods) available now have a fix for this, as well as a few other things.
Im sure when 2.2 update comes out this fix will be passed on to the stock version too (at least as far as im aware it hasnt already!?). So tbh this isnt an issue for you not to get a nexus one...also, there's no point getting a nexus one if ur too scared to unlock the bootloader!!
Click to expand...
Click to collapse
Definitely! That's one of the biggest reasons why I want an N1. It has a good root and dev community and gets android updates first.
I just thought it'd be annoying to have to use a phone with crappy capacitive buttons, but I'm glad to hear that the problem has been fixed.
The only other thing I'm worried about is the dualtouch but it's most definitely going to get fixed in the next update.
Thanks to everyone for their input. I'll definitely be picking up an N1 soon
I have rooted and custom roms etc and I still hate the capacitive buttons with a passion. They are not nearly enough to topple the overall awesome that is the N1 but man I hate those things.
I only hate those buttons, when Nex is in my car mount!
adam18488 said:
Stock Rom had this issue. If you unlock your bootloader, all the kernels (and mods) available now have a fix for this, as well as a few other things.
Click to expand...
Click to collapse
Is this true? I've tried plenty of ROMs and kernels and I don't remember any of them changing the button sensitivity.
The best way to show off how frustrating the buttons can be is to give the phone to someone that's never played with it before and watch as they struggle to register touches on the buttons. The people that use the phone daily have recognized that the touchpad is above the button and never think about it any more.
It's very apparent as soon as you rotate the phone into a different position though.
PrawnPoBoy said:
Is this true? I've tried plenty of ROMs and kernels and I don't remember any of them changing the button sensitivity.
The best way to show off how frustrating the buttons can be is to give the phone to someone that's never played with it before and watch as they struggle to register touches on the buttons. The people that use the phone daily have recognized that the touchpad is above the button and never think about it any more.
It's very apparent as soon as you rotate the phone into a different position though.
Click to expand...
Click to collapse
I also haven't noticed any change in the sensitivity with different ROMs or kernels. For me though, sometimes if I hit right on top of the button it won't register. I am used to just tapping it a little above and it works everytime.
As others have said, this is definitely not a deal breaker for me or shouldn't be for any person IMO. This phone's pros far outweigh the cons.
The best way to show off how frustrating the buttons can be is to give the phone to someone that's never played with it before and watch as they struggle to register touches on the buttons. The people that use the phone daily have recognized that the touchpad is above the button and never think about it any more.
Click to expand...
Click to collapse
When someone is doing that you should just say that it has Finger print authentication technology
absolutely true and this was my discovery today (day 4 with n1). the buttons work fine if you cheat towards the top of the button area and overlap into the screen area.
that solved it for me.
resolved for me for now...
xboomer55 said:
absolutely true and this was my discovery today (day 4 with n1). the buttons work fine if you cheat towards the top of the button area and overlap into the screen area.
that solved it for me.
resolved for me for now...
Click to expand...
Click to collapse
Did you just buy your N1 from Google brand new?
Those buttons are a pain in the bum, but you get used to them, the bigger problem is if the phone gets too cold it starts mis-registering the touchscreen necessitating a reboot or a bunch of mucking around to fix it. This is the biggest annoyance with the phone for me, hopefully they fix the screen calibration in 2.2!
Almost swapped mine for a Desire, thinking less of doing so now, unless anyone can offer a good reason
I got my N1 straight from Google on day one, and I'm currently running CM 5.06
I find the capacitive buttons to be _awful_ if I tap directly on them it takes 2-5 attempts to get it to register.
However, I have found that if I swipe from the button down off the bottom of the button it registers ever single time.
I'm pretty convinced that the problem isn't the digitiser itself but in the driver that splits that section of the digitiser off. I believe it checks to see if there is upward movement before registering a button tap and if it does detect upward motion it cancels the tap event and forwards the event as a touch screen event. I also thing that because I have pretty big fingers any time I press the flattening of my finger registers as a slight upward motion.
If I could find the button "sub"-driver I'd be hacking at it right now.
Still, I wouldn't give up my N1.
SilentMobius said:
I got my N1 straight from Google on day one, and I'm currently running CM 5.06
I find the capacitive buttons to be _awful_ if I tap directly on them it takes 2-5 attempts to get it to register.
However, I have found that if I swipe from the button down off the bottom of the button it registers ever single time.
I'm pretty convinced that the problem isn't the digitiser itself but in the driver that splits that section of the digitiser off. I believe it checks to see if there is upward movement before registering a button tap and if it does detect upward motion it cancels the tap event and forwards the event as a touch screen event. I also thing that because I have pretty big fingers any time I press the flattening of my finger registers as a slight upward motion.
If I could find the button "sub"-driver I'd be hacking at it right now.
Still, I wouldn't give up my N1.
Click to expand...
Click to collapse
Just realized that!!
It does not get the upward movement
It gets: right, left & down
So this means, one could set different options for different directions...
hacker01 said:
Recently, I've been considering getting a Nexus One, however, most of the reviews I read say that the N1's capacitive buttons are a little unresponsive. You must tap the upper half of the button as opposed to the bottom half of the button.
I've also read that some of the cyanogen roms have fixed this problem. Can anyone give me more insight on this issue?
Click to expand...
Click to collapse
I have noticed no issues when holding the phone in my hands but the responsiveness is not that great if the phone is flat on a desk or a similar surface. I wonder what if anything the accelerometer may play a factor.
PrawnPoBoy said:
Is this true? I've tried plenty of ROMs and kernels and I don't remember any of them changing the button sensitivity.
The best way to show off how frustrating the buttons can be is to give the phone to someone that's never played with it before and watch as they struggle to register touches on the buttons. The people that use the phone daily have recognized that the touchpad is above the button and never think about it any more.
It's very apparent as soon as you rotate the phone into a different position though.
Click to expand...
Click to collapse
I dunna man, my 3-year-old daughter figured it out within a minute of getting my phone. I set her up in a game and she decided she wanted something else, so she messed with the capacitive buttons until she got out of the game. Once she had it once or twice (~5-10 seconds for her to figure out each time) it was pretty much instant after that. If a 3-yo can figure it out, I'm pretty sure it's not THAT difficult. Annoying, sure....but not difficult.
hacker01 said:
Did you just buy your N1 from Google brand new?
Click to expand...
Click to collapse
Yes. Direct from Google.
Wow there's definitely a good mix of answers. I thought that the newer batches of N1's fixed the capacitive button problem, but apparently not.
I guess there's not a definite answer. It seems the only conclusion you can make is that some N1's may still have the problem, some may not. Some can be fixed with custom roms and unlocking the bootloader and some cannot. Your results may very.
EDIT: After rereading some of the previous posts (more carefully. excuse my sleep deprived state lol), the capacitive button issue might actually be more of a feature than an issue. I've read similar posts about the capacitive buttons having that sort of "motion detection" thing to prevent accident presses. Hopefully for anyone still having the problem, you can reread some of the posts on this page and give their methods a try
I haven't had a problem with mine but I haven't had the problems most people say they have with the phone so I would recommend this phone to anyone that wants an android phone
-------------------------------------
Sent from my Nexus One
I've scoured the internet in attempt to resolve this issue, and I know it's been talked about many a time before, but this just doesn't have an answer yet afaik.
Does anybody have any experience with fixing the inaccuracy of the touch screen after prolonged use? I love the nexus one, it's by far the best phone I've owned; but this little bug makes the phone completely unrealistic in real-world use.
If this isn't a software issue, it has to be something with the digitizer being powered off and back on to remove the accuracy bug. In that case, is there any low-level way to turn the digitizer off and back on as fast as possible every X seconds? That would mean losing touch capability for a few milliseconds, but is much better than locking and unlocking the phone each time it "goes wild."
I had given up all hope that this issue could be resolved in any fashion as dodgy hardware is, well...dodgy. Nothing can be done about it right?
I haven't had a screen wonk since starting in on the CM7 nightlies many moons ago!
IN YOUR FACE WONK!
Is there an FAQ about this digitizer issue?
JoeSchmoe007 said:
Is there an FAQ about this digitizer issue?
Click to expand...
Click to collapse
No, but it's been covered so extensively that nobody really mentions it any more. Either that or others have found what i have, that somehow the CM7 ROM mitigates the problem. Seriously, i haven't had an issue with it for months!
My particular N1 was never good with stock ROMs. Hated them and gave me endless trouble with one thing or another. It's the polar opposite for me with CM ROMs. Never any issues at all. No call or screen wonk, none of the bugs that others often complain about. It's like the phone has an attitude!
After flashing something ridiculous like 40+ CM7 Nightlies and stable releases, i've not had to wipe data once
DirkGently1 said:
No, but it's been covered so extensively that nobody really mentions it any more. Either that or others have found what i have, that somehow the CM7 ROM mitigates the problem. Seriously, i haven't had an issue with it for months!
My particular N1 was never good with stock ROMs. Hated them and gave me endless trouble with one thing or another. It's the polar opposite for me with CM ROMs. Never any issues at all. No call or screen wonk, none of the bugs that others often complain about. It's like the phone has an attitude!
After flashing something ridiculous like 40+ CM7 Nightlies and stable releases, i've not had to wipe data once
Click to expand...
Click to collapse
Can you please describe what the digitizer issue was/is? I just ordered N1 and haven't received it yet. And what about call wonk? I haven't seen anything about this one.
JoeSchmoe007 said:
Can you please describe what the digitizer issue was/is? I just ordered N1 and haven't received it yet. And what about call wonk? I haven't seen anything about this one.
Click to expand...
Click to collapse
Basically the digitizer has a couple of quirks. One is that after prolonged use (I found it to be completely random) the accuracy goes berserk, registering touches nowhere near they actually are. Secondly there is a switching of the axis when you cross two points: video. They are hardware related so there is no fix. The wonk is a problem with CyanogenMod7 specifically, causing black screens when receiving calls.
Personally I rarely if ever come across the digitizer problem and have never came across the wonk. They aren't deal breakers but can cause a few problems if you play a lot of multi-touch games.
Hollow.Droid said:
Basically the digitizer has a couple of quirks. One is that after prolonged use (I found it to be completely random) the accuracy goes berserk, registering touches nowhere near they actually are. Secondly there is a switching of the axis when you cross two points: video. They are hardware related so there is no fix. The wonk is a problem with CyanogenMod7 specifically, causing black screens when receiving calls.
Personally I rarely if ever come across the digitizer problem and have never came across the wonk. They aren't deal breakers but can cause a few problems if you play a lot of multi-touch games.
Click to expand...
Click to collapse
When accuracy goes berserk - does powering phone off/on help?
JoeSchmoe007 said:
Can you please describe what the digitizer issue was/is? I just ordered N1 and haven't received it yet. And what about call wonk? I haven't seen anything about this one.
Click to expand...
Click to collapse
Well, the touchscreen issue is nothing more than a bad digitizer that was released with the phone and never improved during manufacture of the device. All Nexii have the same one, although people suffered the problem in varying degrees. What would happen is every so often your touch on the screen would register in the wrong place so you may be selecting a shortcut on your homescreen to launch an app, but it might register the touch as being an inch higher/lower/somewhere random. the solution has always been to simply press the power button to turn the screen off/on again. This would fix the issue... until it occurred again.
The call wonk is really in two parts. Stock GB ROMs had a habit of introducing a slight delay in one party being able to hear the other during the start of a call. On CM7 ROMs it was a more significant issue of black screens and freezes during the start of a call. These didn't affect affect everyone though, and even Cyanogen himself didn't have it on on his own device.
EDIT: The other issue affecting the N1 was a weak, and often failing, power button. With the need to keep using it to fix the screen wonk the problem was made worse. That's why you might often see mentions of Trackball wake as it reduced the need to use the power button, therefore extending it's life. Trackball wake is only available on custom ROMs so bear that in mind too!
The phone isn't perfect but with the custom ROM devs doing there thing it's pretty decent for me
Hollow.Droid and DirkGently1 - I appreciate your responses.
Can I bring your attention to my other question to which nobody responded yet?
http://forum.xda-developers.com/showthread.php?t=1077733
JoeSchmoe007 said:
When accuracy goes berserk - does powering phone off/on help?
Click to expand...
Click to collapse
When the issue happens you just lock and unlock the screen to fix it. No need for a reboot.
This issue isn't really such a big deal. It happens once a week or so, and it takes a few seconds to black out the screen then unlock, problem gone.
Please mention all the common issues found in this device (both Hardware and Software level)
So far I have gathered one issue mainly
- The USB/SD Card flap gets loosen or does not properly close.
Some units may have excessive gap between the glass and the frame, either top or bottom.
in_core said:
- The USB/SD Card flap gets loosen or does not properly close.
Click to expand...
Click to collapse
Because of this mine is on the way back to Vodafone [emoji22]
Mine has a dead pixel. But these arent common issues unless a lot of people complain about them tbh.
Servaas said:
Mine has a dead pixel. But these arent common issues unless a lot of people complain about them tbh.
Click to expand...
Click to collapse
Was the dead pixel noticeable from the very first day?
Ive got two things where im not sure if that are real Problems or just a question of settings.
First one is that voice from the other part is not really loud, even on the highest setting, during a phone call.
The other one is the battery time. I dont get such high results like 2 days from the tests on different websites. I only got one day with moderate usage.
in_core said:
Was the dead pixel noticeable from the very first day?
Click to expand...
Click to collapse
No second day, first day I probably didnt notice. Nor do I now to be honest... was hesitating about sending it back but ehh... its so much hassle and like I said I can hardly tell its dead.
I have returned mine to o2 within the initial cooling off period, there's too many problems to risk sorry. I loved the spec and design too
Did you experience any problems or did you just bottle it? I've had mine for a week or so with no problems at all.
qbert456 said:
I have returned mine to o2 within the initial cooling off period, there's too many problems to risk sorry. I loved the spec and design too
Click to expand...
Click to collapse
I'd assume that more than 90% of units have no major issues. The misleading thing is that, in communities like these, people with faulty units are far more represented than people who are satisfied.
Honestly, I didn't really use it,it kept all the plastic films on etc. It's not that I'm not going to get one if it proves reliable more that I'm quite unlucky with phones generally!
I will keep looking in here tho and will likely getting a red/orange one again in a few weeks....
qbert456 said:
Honestly, I didn't really use it,it kept all the plastic films on etc. It's not that I'm not going to get one if it proves reliable more that I'm quite unlucky with phones generally!
I will keep looking in here tho and will likely getting a red/orange one again in a few weeks....
Click to expand...
Click to collapse
I suggest you just get a silicone cover or something, to protect it. A wrist lanyard also helps a lot. And to increase your chance of getting a Z3C from a more recent production batch, you can keep an eye on a web shop and order a Z3C after the stock runs out and is restocked.
Camera Button
Is the Z3c hardware camera button designed to require a fairly lengthy press to activate? I'm guessing that maybe it's a design built in to perhaps avoid accidental pocket presses, but I'm not sure.
Just a quick tap does not activate it on mine, but it works fine with a slightly longer press.
Poojo said:
Is the Z3c hardware camera button designed to require a fairly lengthy press to activate? I'm guessing that maybe it's a design built in to perhaps avoid accidental pocket presses, but I'm not sure.
Just a quick tap does not activate it on mine, but it works fine with a slightly longer press.
Click to expand...
Click to collapse
Mine too, also there seems to be a 2-step press for it, as on a regular camera (half hold down to focus). Half pressing doesn't start it.
Have had to mess with settings to turn off the quick launch which was set to launch and capture as I have so many pics of either a finger or blackness!
---------- Post added at 05:17 PM ---------- Previous post was at 05:12 PM ----------
impact1991 said:
Ive got two things where im not sure if that are real Problems or just a question of settings.
First one is that voice from the other part is not really loud, even on the highest setting, during a phone call.
The other one is the battery time. I dont get such high results like 2 days from the tests on different websites. I only got one day with moderate usage.
Click to expand...
Click to collapse
On mine the sound is pretty loud through the mic, so much so that I thought the loudspeaker was on! Conversely though the actual loudspeaker doesn't seem that loud! Go figure!
For the battery I think you would only get 2 days with the Stamina settings active. I manage to get down to about 25% on a full day of regular usage (in office etc). The Stamina / Ultra stamina modes seem to just disable pretty much everything on the phone. OK if you need to keep it powered on but no good for regular usage. I've ended up turning stamina mode on and then re-enabling Wifi, seems to improve life quite a bit for the times I have been hammering it!
degraaff said:
I'd assume that more than 90% of units have no major issues. The misleading thing is that, in communities like these, people with faulty units are far more represented than people who are satisfied.
Click to expand...
Click to collapse
Always been the case since the Treo days, lol. People will look and see all these problems, but they are random people, that really only for the most part show up here to resolve "issues". While it is a great thing for folks looking for corrections, it does appear bad on the surface if you don't really understand the dynamic at play on boards like these.
---------- Post added at 12:38 PM ---------- Previous post was at 12:37 PM ----------
Poojo said:
Is the Z3c hardware camera button designed to require a fairly lengthy press to activate? I'm guessing that maybe it's a design built in to perhaps avoid accidental pocket presses, but I'm not sure.
Just a quick tap does not activate it on mine, but it works fine with a slightly longer press.
Click to expand...
Click to collapse
Yes. Your button is behaving normally.
I'm currently on my third unit within 7 days. My Internet connection seems to hang about 2 or 3 times a day, and until I try to use the Internet Is don't realise. After then restarting my phone, I get a flood of whatsapps, emails and fb alerts. It's getting really old really quickly,to the point where I just want rid of the phone.
jbhkhc said:
I'm currently on my third unit within 7 days. My Internet connection seems to hang about 2 or 3 times a day, and until I try to use the Internet Is don't realise. After then restarting my phone, I get a flood of whatsapps, emails and fb alerts. It's getting really old really quickly,to the point where I just want rid of the phone.
Click to expand...
Click to collapse
I've only had that once, last Fri however it is a bit weird, here's how mine manifested itself:
- Work most of the day in an office, good wifi connection. Don't use the phone much but see that it is working OK, getting emails, fb updates etc. Can browse the internet via Chrome
- Left the office and try to do a search. Using Google search from the home screen the results showed up very quickly but then when I tried to open any of those links in chrome it would just say no network or something similar. Tried shutting down chrome, clearing cache and data but made no difference.
The weird thing here is that the 4g / mobile data connection WAS working, but the issue was with Chrome.
I'm still stock, not likely to change that but since Chrome is now an intrinsic part of the Xperia build how do you uninstall / reinstall? Or do I end up installing another browser?
Chrome has done this to me on Z3 Compact and a few times on my previous Xperia ZR. Just close the browser from the multi-app right button by flicking it to the side, then try again. If it gets too tedious, install another browser.
Hi, any one have the same issue as me?
My Z3C black out after 2nd week of use then could not power on. Brought to service center and the person claim that it is software issue.. Took back the phone after they reformatted, then after 12hrs use, same problem again.. Then they change 1-1 for me.. but after another week of use, same issue on the 2nd phone!
who have the same issue as me? what should i do next? i cant be bringing the phone in to service center every week..
hello,
I think it's the same pb for me... "Z3 Compact" bought the 28.09.2014. The phone is turned off itself in the middle of the day in my pocket. The battery level was approx. 75% => Black screen, not even light on the charger...:S The Sony support told me to send them with charger and usb cable. I am waiting for news... approx. 10 days...
I've experienced some serious touch issues in the past two days. It's happened very randomly and I can't replicate the issues. The screen losses touch sensitivity and I can't do anything, then it randomly comes back after 10 seconds only to animate every touch I made during the 10 second lull.
Has anyone had any touch issues like me?
Edit: disregard this post. got the forums mixed up with another device.
bryancotton84 said:
I've experienced some serious touch issues in the past two days. It's happened very randomly and I can't replicate the issues. The screen losses touch sensitivity and I can't do anything, then it randomly comes back after 10 seconds only to animate every touch I made during the 10 second lull.
Has anyone had any touch issues like me?
Click to expand...
Click to collapse
sounds like a software glitch, is anything eating up the processor?
I'm on LRX210 out of the box. I haven't had any battery stat app running but nothing unusual is going on in the regular battery app
I have this issue as well. Drives me nuts when I'm playing clash of clans. Found a sprint forum post that says it could relate to screen protectors? I have an invisible shield on right now.
Mauk80 said:
I have this issue as well. Drives me nuts when I'm playing clash of clans. Found a sprint forum post that says it could relate to screen protectors? I have an invisible shield on right now.
Click to expand...
Click to collapse
I have a screen protector but I've never had issues with it before. The touchscreen is COMPLETELY unresponsive 100% of the time
cowkong said:
I have a screen protector but I've never had issues with it before. The touchscreen is COMPLETELY unresponsive 100% of the time
Click to expand...
Click to collapse
Have you updated to 5.1? Since 5.1, there were significant changes that appear to have been made to proximity sensor that seem to be affected by any sort of screen protector that may cover it. If your protector covers the sensor, then I suggest removing it.
I haven't. I currently have the notification on my lockscreen (since I can still use the power button and view that basic info). It simply just stopped working while I was using it. Going into the Sprint store early this afternoon
My N6 arrived yesterday and was immediately unusable. The keyboard filled in a ton of garbage when I was asked to first enter my name ... Power cycled to try again and have had nothing but reliability issues with typing at times the screen will lock while trying to type (no response) or assume I've clicked when I haven't which makes accurate data entry impossible.
wiped, reset and upgraded software from 5.0 to 5.01 to 5.1 - had to remove my ATT sim which initially blocked this process and reset. Issues are still present seems like the screen is defective.
Support has issued an RMA to return the device after suggesting they would replace. Not a great start.
im having the same issue with my nexus, i went back to stock, not even rooted anymore, still doing it, its driving me nuts..
RMA. It's quite obvious you have a hardware problem.
graydiggy said:
RMA. It's quite obvious you have a hardware problem.
Click to expand...
Click to collapse
I'm actually not so sure that it is. I've seen this issue intermittently across 3 different devices, but only on 5.1.1 firmwares.
semperfi123 said:
I'm actually not so sure that it is. I've seen this issue intermittently across 3 different devices, but only on 5.1.1 firmwares.
Click to expand...
Click to collapse
Although we're in an pls thread, I tend to agree. If it was a hardware issue, I don't think we'd see the OS acting out the touches later.. It means the hardware actually accepted the input but the OS didn't do any thing., Likely an OS hang or something.
bryancotton84 said:
I've experienced some serious touch issues in the past two days. It's happened very randomly and I can't replicate the issues. The screen losses touch sensitivity and I can't do anything, then it randomly comes back after 10 seconds only to animate every touch I made during the 10 second lull.
Has anyone had any touch issues like me?
Click to expand...
Click to collapse
I have a Samsung Tab 3 and recently the touch screen has gone haywire. I drop a troop at 12oc and heal spell drops randomly at 6oc or wherever. I click on the screen and the screen zooms in and out irradictly . Trying to do a raid must less a war attack is impossible. Anyone have the same issues?
[email protected] said:
I have a Samsung Tab 3 and recently the touch screen has gone haywire. I drop a troop at 12oc and heal spell drops randomly at 6oc or wherever. I click on the screen and the screen zooms in and out irradictly . Trying to do a raid must less a war attack is impossible. Anyone have the same issues?
Click to expand...
Click to collapse
This is a N6 thread [emoji4]
All of a sudden the lower part of display (about 7 mm) has become unresponsive to touch which means no more gestures (swipe up to get to home screen is not working) e struggle to use the classic navigation buttons.
Sadly I had the same issue in my mi5 but in that case phone had the issue since the unboxing.
I'm starting thinking the xiaomi touchscreen tend to be more fragile than others.
Now I'm waiting for gearbest support.
Anyone has any advice or similar experience?
I made a screen recording
https://youtu.be/bIOUK1V56Ao
No one? Any advice?
jendrassik said:
No one? Any advice?
Click to expand...
Click to collapse
Regarding Xiaomi Quality
While climbing into my truck, I dropped my Mi8 from a height of about 4 ft on accident and it landed flat on its face , on the concrete. Freaked out, I left it laying their for about a minute fearing that the screen had been smashed into a million pieces. However, I picked it up to see that it was fine, and not a single scratch. So I immediately went out and bought the Love Mei 360 case.
Anyway, regarding your touch issue, you should really provide more some information about how this issue came about, what rom were you using, did the phone get wet, etc.
Also, I had an issue with my Mi8 soon after unlocking the bootloader where the top part of the screen would not register my touches, I first tried recalibrating the screen using Miui hidden settings app, the test is called QMMI ( I think) and if I remember correctly there are several menus of testing that also calibrate the screen for me this worked and for good measure I reinstalled a Miui rom and havent had the issue since.
Try it, hopefully that is the only issue. If you are using a AOSP. It's possible that you have a driver issue. So before sending the phone off for service its worth testing.. If you are on stock and still have a locked bootloader, I would try resetting the phone before trying anything else.
Good Luck.
Some gravedigging, but the question is still on the table - have you managed to fix it?