Hi,
is anyone changed touch pressure via buildprop and system/usr/idc ?
I think we can improve the touch response.
I need to know is there any difference on idc file compared to Oreo.
Sometimes i feel like touchscreen doesnt work properly. Especially when i touch the screen standing on the table it doesnt respond.
Are you using tempered glass? I have absolutely no problems with the touch response of my device.
I was wondering the same thing, if there is any ways to tweak this using a custom rom / kernel, or even some hardware tips (adding tape on connectors ?).
I've been using my phone for almost a year, and changed my screen because I had ghost touches... Now it's fixed but sometimes it feels a bit off.
I'm used to touchscreen issues (since I've also a Nexus 7, which had ghost touches) but I don't find any solution regarding this phone.
They broke it a few updates ago. I have no idea what Xiaomi wants from their AndroidOne fanbase. I recently installed stock ROM and updated to latest, still had the same issue as you did. It doesn't register most of the taps and I think it does so I keep sending meaningless messages to my friends. I don't know about the solution on the current stock ROM, but I'd highly suggest switching to MIUI port because it's simply great and way more stable than stock. Cheers.
I am not so sure they broke it or not. I did some tests on my phone.
Test - 1
- Remove case (protective one u bought)
- Leave a phone on the table
- Touch only to the screen
Result:
Screen becomes unresponsive.
Test -2
- Remove case (protective one u bought)
- Leave phone on the table
- Lift the phone from behind with plastic sticks
- Touch only to the screen
Result:
Same results as Test -1 (Screen becomes unresponsive) so theyre not using accelerator sensor for whatever they did.
Test -3
- Remove case (protective one u bought)
- Hold the phone and touch the screen
Result:
Screen becomes responsive. Here is my theory; theyre using our hands static electric to prevent from ghost touch. Somehow Aluminium backcover collects all those static electric from our hand and phone thinks there is a human and it starts working as usual.
Stock Android 9 (Pie) - v10.0.16 (November 2019) Locked
OK I don't know how you came up with that result, but the thing is the phone doesn't have magical sensors on the aluminum parts on the back. It's a software issue that I also have on Stock Pie and I didn't have that issue on Oreo. Yes I use a screen protector, and it still happens when charging, only on stock ROMs though (both Oreo and Pie). When you flash a custom ROM those values change so the screen responsiveness change, that's why it affects the touch sensitivity. I don't know why I'm still trying to explain stuff to you, that result you came up with is just a really weird way of perceiving things.
marstonpear said:
OK I don't know how you came up with that result, but the thing is the phone doesn't have magical sensors on the aluminum parts on the back. It's a software issue that I also have on Stock Pie and I didn't have that issue on Oreo. Yes I use a screen protector, and it still happens when charging, only on stock ROMs though (both Oreo and Pie). When you flash a custom ROM those values change so the screen responsiveness change, that's why it affects the touch sensitivity. I don't know why I'm still trying to explain stuff to you, that result you came up with is just a really weird way of perceiving things.
Click to expand...
Click to collapse
I am using HybridOS Miui v11.0.3 right now and touch screen works fine. The result i came on top is not working on this rom. So i agree it has relation with software too. Probably this static electric thing is disabled on this rom.
My devices touch screen works fine while charging on Stock rom. This unresponsiveness happens when i leave my phone on the table. Thats the reason why i opened this thread.
Also theres is a hardware revisions. You can check ur phones hardware revision with this numbers *#*#0000#*#*
BRUH
Related
Good morning to all ..
I want to ask if anyone of you has the same problem: when I leave the galaxy nexus in charge in the night (all night) in the morning, when the alarm rings, I can not turn off the alarm because I can not use the phone, because I can not unlock the phone, if I touch the ring in the lock screen, nothing happens, as if the touch screen does not work but if i wait a while(15-30-60 seconds) it will wake up and i can re-use my phone.. and this problem has also occurred at other times... without the phone was in charge..in the afternoon, I could not answer a call arriving(not often).. let me say this thing that perhaps can be decisive, that my cell was 2 times under warranty, the first replacement for faulty screen (ehm...) and the second time because when they replaced the display does not have removed blue film that protects the far side of the screen next the front camera(i get i blue overlay effect on front camera images lol)..than i send it in warranty again.
it may be caused by the rom/kernel? if not, how you recommend to act?
ps: I was wondering also .. if when they replaced the display have replaced only the AMOLED part or also the glass and the multi-touch ... because the glass was intact and the multitouch worked.. is a single body or are separate pieces? Also remember that the phone stank of "liquid crystal" because they were leaked (this was the fault of the display, it was broken..) it might have caused the malfunction of the touch sporadically?
from what ive read sometimes rom's can screw up functions like camera etc, but if there tried and tested not sure why it would be a prob.
i would go down the warranty route personally.
big_mike_aka_mike said:
from what ive read sometimes rom's can screw up functions like camera etc, but if there tried and tested not sure why it would be a prob.
i would go down the warranty route personally.
Click to expand...
Click to collapse
mmmmmmmh...is the last resort .. I would avoid because they put us a month to fix it! this is the third time i would send it in the warranty .... almost makes me want to let them replace it with another device ... I fear them have ruined ...
what is your min mhz set to?
I had a similar problem with my old cappy running CM9. I had to restore it via Odin and start from scratch then it worked and didn't have that issue again. My suggestion would be to go back to 100% stock and then customize it again. It may or may not help but it is worth a shot.
sent from my GSM Galaxy Nexus
I just sent mine into Samsung for repair, due to the same thing happening. It started off that if I pulled the battery I could get it to work, but eventually it got to the point where that woudln't even work. Between this happening and the fact that I returned another one due to the out going audio dropping, I am starting to loose faith in the GNex.
Zepius said:
what is your min mhz set to?
Click to expand...
Click to collapse
i use 384Mhz (franco kernel first frequengy step) minimium frequency @ ondemand governover...isn't it the stock minimium frequency?
@thephoneguyusa i have tried... but i got the same thing with all stock, flashing factory images got from http://code.google.com/intl/it-IT/android/nexus/images.html ( i don't remember if i've rooted and changed the kernel, but i'm 99% sure that was all stock,maybe i'll give a try, again )
@HitchHiker my gnex crashed once (a good fall) and the display is ****ed .. but the glass and touch were intact ... is very sensitive .. but this is not good ... if I send, this will be the third time that I send it in for service since I bought it in December ... no good...
curiosity: attached the blue-film-front-camera-rendering-blue-effect-lol...
UPDATE:
I didn't use the charger last night and this morning I had the problem in question. But! I went to the bathroom to shower and the various routines gnex morning bringing with me, and I left the bathroom I wanted to use the phone, but! tataaaaan! the screen won't unlock...can humidity cause this problem?
my room is a bit wet because I live near the sea ...
perhaps too much humidity **** circuits of the touch .. or perhaps it is a contributing cause to a real defect of the display....
My Desire Z had a fall, and has developed two problems
1 - The hardware keypad has started to take hard-press and sometimes prints double characters on single press. I think the alignment is out or something... any other guess ?
2 - The touch screen sometimes stops working from an inch up from the bottom and continues to half an inch. Before and after that patch, the touch always works fine . Mostly, the whole touch screen works fine. But when the patch gets non-responsive, I have observed that by turning the screen off and on a couple of times makes it work again. I am not very sure what the problem is. Any clues ?
Thanks
I'm also experiencing a similar issue - for me it's usually an area that corresponds to the top row of the
on-screen keypad (for unlocking) or the top of the area for unlock patterns (portrait orientation).
Mine is a 2 year old DZ w. Cyanogenmod 7.1
No HW key problems & no droppage.
Liberal application of isopropyl alcohol and a microfiber cloth - especially around the edges of the screen
seem to help a little bit but not often enough to be better than random.
Switching the screen off and on occasionally helps but most often I get annoyed and use the HW keys to
unlock.
I have noticed that, after powering on the device, the SIM-lock keypad works just fine but the (different)
screen-unlock keypad fails. This leads me to believe it to be a software issue.
/b
I have had this experience on my G2
No fix for me but his my experience check out the url!
http://forum.xda-developers.com/showthread.php?p=31264095
Sent from my HTC Vision using xda premium
Thread moved to Q & A section.
So i am going for Digitizer replacement will post the result when the phone is back.
And what about the Keypad taking hardpresses ? what can be the issue there ?
so my desire z is in the shop for repairs. lets see what problem is diagnosed.
I have read in another thread in this forum that the hardware keyboard (need to press hard on some buttons) issue can happen when the phone falls.
Apparently, the flat cable that connects the keyboard to the rest of the phone gets loose and causes such trouble.
Since your phone is in for repair, I'm sure this will get sorted when U get it back.
ok so my phone got back from repairs, the guy couldnt fix the touch-screen rather made it worse. Now the touchscreen doesnt work at all. So i cant unlock the phone and cannot test the Keyboard problem. The guy said the touch problem is related to the ribbon cable and not the touchscreen itself.
Note 1: He says he tried replacing the touch panel altogether but it didnt work.
Note 2: I still think the ribbon is fine (call it intuition)
Note 3: I am giving my phone for repairs again, but this time to HTC service center which would probably cost me a lot more than third-party repairs but at least it will get fixed.
I will update when I my phone back from HTC service center.
Could you not unlock the phone by opening the keyboard ?
It does smell to be an issue with flat (ribbon) cable to me as well. As if there was some loose contact before (caused by you dropping it), and after the repair guy took the phone apart, he probably made even bigger mess by ruining the flat cable completely.
From my experience (and I've claimed warranty 3x for the broken digitizer (touch panel)), if it's broken, an area of the screen (or the whole screen) will be permanently dead. It would not come back to life every now and then.
btw, mine always started being unresponsive in the very middle of the screen, a bar of height around 1 cm (somewhat less than 1/2 inch). Each time they replaced the digitizer.
If it;s the flat cable, you shouldn't end up being charged too much - those thingies are very cheap (in China) and the labour will probably be the majority of the price. Fingers crossed.
So I got my phone back again... The HTC repair center was not located in my city so I went to another (better known) repair shop. The guy said, "your phone hasnt been opened at all from the touchscreen side, any *repair guy* who claims he has opened it and tried this and that but couldnt fix is simply lying. This said, he opened up my desire z replaced its Touch Panel and voilah! my desire z is sensing again in 15 mins
What's the status for the keypad and need to press it hard to work ?
nope... I had it cleaned using alcohol / thinner. now it works fine.
So, I updated to CM 7.2 last night but the touchscreen problems are still there.
Updated using CWM and deleted data & cache whilst doing so.
I really hate the prospect of getting a new phone as the current models available
in DK are all without physical keyboards
Hi everyone,
I've had my Desire Z for little over 2 years now and two months ago (was running CM7.2 at the time) I started getting a weird issue where my touchscreen would only be responsive when the keyboard was slid out (so the opposite problem of what quite a few other people have reported where the touchscreen becomes unresponsive when the keyboard is out). The status LED would also stay off whenever the keyboard was closed, and the keyboard backlight didn't come on anymore at all. Also, I had to make sure that the keyboard was slid out during boot, if the phone booted without the keyboard out the screen would not become responsive at all until after another reboot. My earpiece speaker stopped working around the same time so I was wondering whether it was just an issue with the flex cable becoming a bit loose, but the touchscreen would consistently start working again when I flipped the keyboard out, and also the physical scroll button on the top bit would always work, so I was still hoping it would be some weird software issue.
I then upgraded to Flinny's (amazing) Andromadus ROM (build 22, complete data+dalvik wipe) after which the keyboard backlight started working again, but the rest remained pretty much the same. Since then the touchscreen issues have been getting worse, so that I sometimes have to flip the keyboard in and out again a few times, or turn the screen on or off with the power button several times before it becomes responsive again, but then it tends to work fine until I lock the screen again, with no noticeable dead spots anywhere on the screen. I've had days where it worked all day without problems (except having to flip out the keyboard, that's been a constant for the past two months), and then today I haven't been able to get the screen to do anything at all even after dozens of reboots.
I've already bought a new digitizer and am all ready to put it in (I'll have to replace the broken earpiece anyway), but was wondering whether anyone has any thoughts on whether it could still be a software issue after all, or if anyone has experienced anything similar? The thing with having to flip the keyboard out to get not only the touchscreen but also the status LED to work is just so weird and makes me doubt that it's a pure broken digitizer or lose flex cable issue, so I'm wondering whether it would be better to first try reverting to a stock ROM before taking on the messy sticky glue stuff (I should be fine but still, never done it before)?
Many thanks!
From what you describe my best guess would be the main flex cable is what needs to be replaced. Flash a touch based recovery and see if you have the issue there as well, if so its very unlikely that its anything but a hardware fault
Sent from my Nexus 4 using Tapatalk 2
Thanks for the heads-up, I've been playing around a bit more with software and I do manage to get the screen working again occasionally, typically after the second boot into a newly flashed ROM or restoring a backup, and only until one or two reboots later when it becomes completely unresponsive again. I've tried CM 7.2.0 as well as Flinny's Andromadus 10, and it is only complete flashing that does the trick, cache wipe or factory reset alone does nothing. The two occasions where the touchscreen worked were still limited to when the keyboard was flipped out, and it also had to be flipped out during boot, otherwise nothing would work. I've learned to navigate my way around the phone by just using the hardware navigation button, but I'll have a close look at the flex cable when I take it apart to replace the earpiece speaker tonight...
Hello,
so I took my dear phone apart yesterday to replace the broken earpiece - everything went fine but after reassembly the replacement earpiece isn't working either, which leads me to think that all those little broken bits might actually be related to some contacts being a bit lose, all in the same region. Should've thought about that earlier really since the earpiece and the LED (only works when keyboard flipped out) are both in that top region that the digitiser data presumable also has to run through before passing through the flex cable.
In any case, I also took a picture of the flex cable which is slightly bent but doesn't seem straightforwardly damaged (see attachment, that thing on the right is *not* a rip). Think it's worth trying to replace it anyway?
What was truly bizarre is that after the first boot following reassembly the touchscreen worked quite consistently for the entire evening - I thought I might've fixed a lose contact by un- and replugging the digitiser cable, but then the screen went nonreactive again at some point. I wonder if the working screen was again actually related to some software reset caused by the battery being taken out for so long? In the meantime the actual screen and trackball are still working away perfectly. Bizarre.
Just to let people know the solution to the mystery: the increasingly odd behaviour was actually caused by an initially small rip in the flex ribbon cable that got bigger and bigger - it's actually half-visible in the picture I uploaded above, only that the rip is where the cable comes out from underneath the case, and not where it's wrinkled!
Just in case it could be useful for anyone, here's the (top half of phone) components in the order in which they failed on me, which I guess corresponds to the order of the respective data lines in the ribbon cable (from the top of the phone towards the center):
environment brightness sensor (I thought that the sensor had been broken for almost a year, but as soon as I rebooted with the new flex cable I noticed how my phone stopped shining into my face at full brightness - if your brightness sensor gets stuck reporting the same (low) value this means your flex cable is on its way out!)
earpiece speaker
status led
touchscreen
screen (non-alignment with edge of screen, visual artefacts)
screen (fade to black/power interrupt)
obstacle3 said:
Just to let people know the solution to the mystery: the increasingly odd behaviour was actually caused by an initially small rip in the flex ribbon cable that got bigger and bigger - it's actually half-visible in the picture I uploaded above, only that the rip is where the cable comes out from underneath the case, and not where it's wrinkled!
Just in case it could be useful for anyone, here's the (top half of phone) components in the order in which they failed on me, which I guess corresponds to the order of the respective data lines in the ribbon cable (from the top of the phone towards the center):
environment brightness sensor (I thought that the sensor had been broken for almost a year, but as soon as I rebooted with the new flex cable I noticed how my phone stopped shining into my face at full brightness - if your brightness sensor gets stuck reporting the same (low) value this means your flex cable is on its way out!)
earpiece speaker
status led
touchscreen
screen (non-alignment with edge of screen, visual artefacts)
screen (fade to black/power interrupt)
Click to expand...
Click to collapse
I'll for sure keep that in mind. Mine is still going strong for the time being, but it's good to know some warning signs if I need to replace parts or if it's time to get a new phone
fireball0093 said:
I'll for sure keep that in mind. Mine is still going strong for the time being, but it's good to know some warning signs if I need to replace parts or if it's time to get a new phone
Click to expand...
Click to collapse
Replacement parts all the way, the repair was 15$ and it feels as good as new! Well, it could do with a new battery but that's just another 5..
Just realised that the proximity sensor should actually be added to the very top of the list - just noticed that faint red light when taking a phone call, don't remember seeing that in almost a year :]
obstacle3 said:
Replacement parts all the way, the repair was 15$ and it feels as good as new! Well, it could do with a new battery but that's just another 5..
Just realised that the proximity sensor should actually be added to the very top of the list - just noticed that faint red light when taking a phone call, don't remember seeing that in almost a year :]
Click to expand...
Click to collapse
That's not a bad cost at all. I know I'm going to have to replace my keyboard in probably 2 months or so (maybe sooner) because some buttons are starting to not work. Other than that fact my phone is currently still going strong for being going on a 3 and a half year old phone
Its been some days, I'm experiencing this weird touch screen problem.
My DZ touch screen doesn't respond properly.
For example:
If i see an image and slide just one finger up and down then it would zoom in and out. And then the whole screen becomes unresponsive.
It seems as if, its touched by itself. Even the softkeys would go numb. Only the haptic feedback of my search button works at that moment.
But the trackpad works perfectly.
But, If i lock and unlock the screen using power buttons, it would work properly for some few moment and then again the problem repeats.
At present I'm repeating this process of locking and unlocking screen to use my phone.
One even worst weird thing is that, if the device is connected to a charger and kept on the table or floor. This problem doesn't occur.
I have done system format, restored my nandroids and even changed Roms. The problem still exists.
Please note, i don't use any Casing or covers that would press the device hard for malfunctioning of screen. I have even removed and replaced my screen guard.
I'm sure, its not a software issue.
And even i dont think its a strip issue, because i dont use my physical keyboard always.
Can anyone say what hardware issue it might be..?
Or what i need to do? I'm really out of options.
Do i have to replace my whole screen or the digitizer..?
Thanks...
Thats no fun,
As you stated it's more than likely a hardware fault, the two most likely culprits would be the digitizer or the main flex cable
Which would be this and this
both relatively easy to replace depending on your experience
in 4.x and up ROMs check the developers setting to show touch or use apps like
z device test
or
yet another multitouch test
these wont help you fix the issue but may show you where the bad points are on the screen
best of luck
I know the problematic spot. Its near Search softkey. Even Yet another multi-touch test would stuck at that spot....
As you can see in the image, that i'm not holding anywhere, still it shows that somewhere around Search softkey its touched by itself.
In second image, If i move my fingers around, it would show the other touch responds, but if i slide near search, it would go and stuck there itself.
So, i guess i would first go with the flex cable.
In actuality I'm leaning toward the digitizer in your case, but its possible to be either.
And if you have a spare phone it may be worth disassembling even without buying anything. On a G1 I once fixed a similar issue just taking out the digitizer and cleaning the contacts on the ribbon and the edges of it as well, when I put it back it worked like new. I think some dust may have gotten into the edges but it may be worth a shot before buying anything... But could make matters worse so if you don't have a spare, buy parts first
Best of luck
Sent from my Nexus 7 using XDA Premium 4 mobile app
I guess i should try disassembling and clean it first. If it still persists then i would go for digitizer.
And thanks for giving a hope.
Thanks...
I do not know whether this counts as ghost touch or not, but randomly there is a persistent touch on the bottom right corner of my Zenfone 2, ZE551ML. If i Lock the device and unlock it back again, (Through the power button), the issue goes away. It re appears after a while again.
I saw videos of people facing such issues on youtube, but in their cases, the entire touch automatically starts to act up. whereas in my case, this happens only if i start using the phone. And that too on the same area ( Bottom Right, Just over the Recents Button)
I wiped the screen / Scratch guard thoroughly. I even changed my scratch guard. but still the issue stays.
Im on Stock 183 (Not yet updated to 184).
Is this a hardware issue or a software one?
(My warranty just ended yesterday).
I feel this is software, because the touch works normally if i lock the device and then unlock it back.
Just for the record, my device passed the SMMI touch and multi touch test without issues.
Also i enabled the graph option under developer options. And i do not see any touch being registered under normal course.
But then when all the tools are off, randomly the issue just pops up again.
Does anyone have such issues?
Does CM or other Non-stock ROM solve this??
I actually a similar issue a month ago, which I thought was a software thing (completely wiped my phone, then installed latest XOSP) or me losing my mind, and it turns out it was neither.
It came back yesterday, and I learned that there's entirely a chance that the screen connectors are loose. Simply remove the back panel (the one with the screws, you'll need one of those eyeglass-repair screwdrivers) and press down on the connectors to make sure they're 100% snapped in and the issue should stop!
Also, see if Glove mode fixes it, since I know that works for a lot of people.
I had the problem. I just removed back cover and plugged a bit more the connectors that you can see when removing battery cover.
Its been 3 months without the problem.
gREENNNNN said:
I had the problem. I just removed back cover and plugged a bit more the connectors that you can see when removing battery cover.
Its been 3 months without the problem.
Click to expand...
Click to collapse
Kavka.V said:
I actually a similar issue a month ago, which I thought was a software thing (completely wiped my phone, then installed latest XOSP) or me losing my mind, and it turns out it was neither.
It came back yesterday, and I learned that there's entirely a chance that the screen connectors are loose. Simply remove the back panel (the one with the screws, you'll need one of those eyeglass-repair screwdrivers) and press down on the connectors to make sure they're 100% snapped in and the issue should stop!
Also, see if Glove mode fixes it, since I know that works for a lot of people.
Click to expand...
Click to collapse
Okay so
My issue is because of my flip cover.
I knew this wasn't hardware, coz the issue was only on one small area of the screen.
I did the following:
When there was ghost random touch.
I immediately removed my flip cover, and the issue went off
Did It twice, both times, it worked.
Thanks anyways.
Sent from my ASUS_Z00AD using XDA-Developers mobile app