Related
Hi all! I have a brand new LG Optimus One, but I think it has a problem. When I tap on the screen or write a message and tap on one letter, sometimes the screen respond 2-3 or more taps (want to write "word", but when i pres the "D" it goes "wordddd". Does anyone have the same problem or? Thanks a lot!
P.s. Sorry for my poor english
Same here..
I have the same problem too but i think it happens more often with gingerbread keyboard. The lg keyboard lags little more than default android keyboard. I think I'll stick with swype for now
Sent from my LG-P500 using XDA App
No problems here. Works fine, am using swype tho.
Sent from my LG-P500 using XDA App
JulyDerek said:
No problems here. Works fine, am using swype tho.
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
same here , didnt have any problems everything works quick and fast
Can it be something with the stock protection foil?
Or may be i must go to the shop and return it
I removed the foil and still has the issue. I haven't tried other keyboards. Using the default LG Keyboard.
vladsk8 said:
I removed the foil and still has the issue. I haven't tried other keyboards. Using the default LG Keyboard.
Click to expand...
Click to collapse
I am with the default keyboard too. Its very annoying, when the vibration is ON and when i just touch a letter...it's vibrating for 2-3 seconds.. Today i will try to go to the mobile shop and i will write after my visiting there.
Same here, I believe this is normal behavior, you have to remember that this phone has an entry level touch screen, so you can't except much from it. There are other problems with the keyboards as well related to touch. For example, in the Gingerbread keyboard you can do proper multi-chorded inputs (aka pressing shift + a character to capitalize the character) because of the touch screen quality. Same for pinch to zoom problems.
Download a touch screen test app to see what's really going on and why some things just don't work the way you expect. If you want better touch screen response you should've bought a more expensive phone. I'm happy with my Optimus One since I knew that this is a budget phone and that you can't have high expectations. That said, and knowing how much I paid for it new and unlocked (180€) I'm quite impressed with it's quality.
Timerever said:
Same here, I believe this is normal behavior, you have to remember that this phone has an entry level touch screen, so you can't except much from it. There are other problems with the keyboards as well related to touch. For example, in the Gingerbread keyboard you can do proper multi-chorded inputs (aka pressing shift + a character to capitalize the character) because of the touch screen quality. Same for pinch to zoom problems.
Download a touch screen test app to see what's really going on and why some things just don't work the way you expect. If you want better touch screen response you should've bought a more expensive phone. I'm happy with my Optimus One since I knew that this is a budget phone and that you can't have high expectations. That said, and knowing how much I paid for it new and unlocked (180€) I'm quite impressed with it's quality.
Click to expand...
Click to collapse
I am happy with my phone too! But when other people say, that they have no problems, what must i think about? I am from Bulgaria and here 180$ are not little money
So i went to the market and i played with the sample... It has the same "problem" )) So now I think, that all of this is because of my big fingers and "don't know how to touch" This is my first touchscreen phone and may be this is why i woried about. So thanks all for the answers, now i am a bit more calm! Great wishes for the NEW YEAR to all! Bye!
No problems with original android keyboard same as with SmartKeyboard Pro
Try to change to a different type of keyboard first and change back maybe after about 2-3 mins.
same problem
Hello folks!!
I have the same ptoblem with my touchscreen but only when i plug the usb cable to charge ...any solution?
it happens because of the touch screen lag bug. there is too much cpu usage when the touch screen is tapped.
that is why when you try to type fast using lg or android keyboard you will experience such problems.
this problem is not there with swype since you don't have to tap on the keys to type.
there is a touch screen bug fix and that will solve the problem.
I wish optimus one didn't have so many problems.
A day or so after upgrading to Jokersax's 0.5.0 build for the Atrix with the Aroma installer, I've discovered that some of the letters on on the keyboard stopped working. Using Touch Test, I've confirmed that there is a roughly 1 inch vertical stripe of my touch pad that just does not register inputs.
Downgrading to previous builds or restoring previous backups of the ROM do not fix the issue.
Is there a chance that the touchpad calibration utility for Aroma caused a miscalibration of the touchpad? Or is this likely physical damage of some sort? I've already tried rerunning through the Aroma installer and recalibrating the touchpad to no good effect.
Any other suggestions from folks?
-----
Update: Solved by replacing the screen/digitizer
mines is doing the same exact thing. from what i have read on there your digitizer is going out. I ordered another one and it should be here today, once I install it, I will let you know if it continues to do this or not.
The digitizer is a common issue with the Atrix. Motorola went cheap on the Atrix.
Funny. I also started experiencing this last week.
How much did your digitizer cost? ( @ Quinto)
Sent from my MB860 using XDA
I just installed JokerSax 0.5.0 2 days ago as well, and today I have noticed a strip up the entire touch screen that is not responding to input. I too used Touch Test to confirm that there is a strip from the back key, all the way up to between 'OROL' in the word Motorola at the top of the phone.
This affects keys B H and Y when in portrait, and the entire qwerty row when in landscape with the usb port to the top.
I dont recall this happening before running Jokersax CM9 but it very well could have been..
shirzadians said:
Funny. I also started experiencing this last week.
How much did your digitizer cost? ( @ Quinto)
Sent from my MB860 using XDA
Click to expand...
Click to collapse
got for $33 off of eBay. Here is the link:
http://www.ebay.com/itm/OEM-Motoroloa-Atrix-4G-MB860-digitzer-frame-/251030640695?pt=LH_DefaultDomain_0&hash=item3a72979837#ht_5015wt_754
It came yesterday and I am going to attempt to put it on tonight.
Thanks, and good luck. Keep us posted.
Sent from my MB860 using XDA
Somebody gave me a stock atrix with a similar condition, it was about 1/2 inch at the top and another 1/2 inch near the bottom (in portrait) mode.....so it's not the rom that you installed.
I too ordered a new digitizer off ebay....except mine cost $43 :-( i should have looked for a little longer...ohh well
I don't think it's necessarily a hardware issue :
The fact that it happened just after installing a new ROM is very disturbing
I have the same problem, and sometimes, with a new ROM, the problem disappears for a couple of hours, then my screen goes totally crazy, then the unresponsive strip reappears
Some people have this problem and a new digitizer didn't solve it
Is there any way that CM9-based ROMs overwrites some touchpad driver ? Does someone else could testify that it could be something else that the digitizer ?
Interesting idea. For the record though, I'm running pure CM7 RC 2. I have heard that the reason one might lose and then regain touch response is due to a hardwear connection/reconnection issue.
When this problem first began to occur, I would briefly retain touch response in the dead strip after rebooting. To test if this was a software or hardwear issue, I physically twisted my phone a few times and regained touch response temporarily, suggesting a hardwear response.
Just my two cents.
Sent from my MB860 using XDA
Anyone have luck with the replaced digitizer yet? I'm hoping to avoid ordering if that doesn't resolve the issue.
Ok, I broke down and bought the digitizer from ebay via the link that quinto0827 provided. I just installed it, and things are working great.
shirzadians said:
Interesting idea. For the record though, I'm running pure CM7 RC 2.
Click to expand...
Click to collapse
Off topic, where did you find cm7 rc2? All I'm finding is rc1 which is what I'm running.
David Guillot said:
I don't think it's necessarily a hardware issue :
The fact that it happened just after installing a new ROM is very disturbing
I have the same problem, and sometimes, with a new ROM, the problem disappears for a couple of hours, then my screen goes totally crazy, then the unresponsive strip reappears
Some people have this problem and a new digitizer didn't solve it
Is there any way that CM9-based ROMs overwrites some touchpad driver ? Does someone else could testify that it could be something else that the digitizer ?
Click to expand...
Click to collapse
I think the same thing.
I had the same problem with my Huawei Ideos U8150 after flashing Dronix 0.5 Rom.
In CWM I can see that the digitizer every 2 seconds it loose my fingers.
same has happened to me on my atrix. one perfectly straight line down the screen which doesnt react to touch. This line is moveable within the aroma installer calibration tool, which btw is what created the problem for me in the first place, after i decided to try the alternate touch option.. So yup, i agree too. I KNOW it was aroma installer that messed my atrix up.. SIGH...And i had just gotten it running top notch too..grrr .. btw that new touch file manager installed through cwm will also move this ghost line around, which could perhaps help some users navigate a little better on their touchscreen.. This is another point that suggests its not a hardware issue. Only other, worse thing i can think of is that the aroma touch installer played with the voltages feeding the screen, and did maybe blow something physically.....
Hey look at this... Just happened today and im so sad... Sometimes this solution in the link seems to work so it should be a hardware issue... http://forum.xda-developers.com/showpost.php?p=27595402&postcount=1
Hello,
I have Acer A100 tablet for about 2 years now and it was working fine until this new update came and the problem started. After the update the tablet just do random stuff as someone is operating it, screen changes, keyboard appearing and typing itself and other randon app selection. This condition will not resolve unless I heat the tab by placing it front of an heater for a few seconds.
I thinks it's the update that cause it but I don't know how to go back to the old state?
Anyone with solution(s)?
Thanks,
DKMej
Some people have had that issue before, but seems weird that it it gets better with heat as that would typically indicate a hardware issue vs software. Did this happen as SOON as the update was done? Which update was it? Stock or custom?
es0tericcha0s said:
Some people have had that issue before, but seems weird that it it gets better with heat as that would typically indicate a hardware issue vs software. Did this happen as SOON as the update was done? Which update was it? Stock or custom?
Click to expand...
Click to collapse
Thanks for the reply to my question. The issue started the next day after I updated the tablet. The tablet was cold and it acted out. Don't know how to fix it?
Like many other ZU owners i'm experiencing phantom touches now and then. My culprit is for example some dirt, like a fingerprint, on the screen. If I clean it the issue is gone for a while.
I'm convinced this is a software issue, and I've read at several places about other users with the same idea.
I've found some tips, like tweaking the touch pressure scale in clearpad idc and the touch filter level in max1187x_pen_0.idc but nothing seems to completely fix the problem.
So, I would like to know if someone made some more digging?
There is one file which loads the touchscreen firmware at boot called pre_hw_config.sh
It loads the touchscreen drivers in /sys/devices/virtual/input
Can we find something here?
The firmware version of the touchscreen drivers can be found at:
/sys/devices/virtual/input/max1187x/few_ver
I'm on:
fw_ver (1.4.13) chip_id (0x75)
config_id (0x0010) customer_info[1:0] (0xFFFF, 0xFFFF)
Are you on a more recent firmware without issues?
If you feel for joining me in the search for a fix please do so,
Thanks
Per
Sent from my C6833 using Tapatalk
I had those problems too, but since i removed (it takes a lot of time because it is glued :X) the screenprotector, the problems are gone.
When i used another screenprotector, the isues returned. So now I work on the glass, and have no isues at all.
I don't want to remove this as I think it's glued for a reason.
But if there's no other way to solve the touchscreen issue I might consider it
Sent from my C6833 using Tapatalk
fw_ver (1.4.13) chip_id (0x75)
config_id (0x0012) customer_info[1:0] (0xFFFF, 0xFFFF)
Your config_id is 10 while mine's 12.
Can't say I have any serious cases of phantom touching.
Sent from my C6833
LordManhattan said:
fw_ver (1.4.13) chip_id (0x75)
config_id (0x0012) customer_info[1:0] (0xFFFF, 0xFFFF)
Your config_id is 10 while mine's 12.
Can't say I have any serious cases of phantom touching.
Sent from my C6833
Click to expand...
Click to collapse
This is interesting. I suppose we're on the exact same hardware but with different config. If there is any way to upgrade this config I want to know. Will do some searching.
Sent from my C6833 using Tapatalk
I get this too. I have to keep my screen really really clean. The false touches tend to be nearer the home button. When it starts to happen I quickly press power/sleep and clean the screen, because it can cause chaos!
I too think it can be tuned in software, because I rarely experienced phantom touches when I first got my XZU on Jellybean 4.2; it started becoming a lot worse and the only reason I can ascribe is the upgrade to Jellybean 4.3.
I only just took the plunge and upgraded to KK/4.4.2, so it will be interesting to see whether it solves the problem.
Edit: these modifications below sometimes help a little bit but DOES NOT FIX ANYTHING
@devs please close this thread.
Hi,
just found a thread at sony about the touchscreen issues. Since that post also references some XDA-Threads I guess it has been published before in some other Xperia threads, but I did not searched for it.
I tested this running stock Xperia ROM (.402) and also CM11 and these issues are gone for me. The touchscreen is much more responsive now and I never noticed that complete touch freeze again.
What's about your device? Does this fix help?
Note: You need root to apply this fix!
Change these two lines in /system/usr/idc/clearpad.idc
R/W-Mount /system (mount -o remount,rw /system)
In /system/usr/idc/clearpad.idc change the values of
touch.pressure.scale to 0.001 (original value: 0.1)
Code:
touch.pressure.scale = 0.0001
touch.filter.level (original value: 2)
Code:
touch.filter.level = 1
reboot
Is this for fixing my z2t screen sometimes just not respond to my fingers pressing keys or stuff?
Sent from my SGP511 using XDA Premium HD app
Just try and report. You can revert if you dont like
Sent from my D6502 using XDA Premium 4 mobile app
markusmuster said:
...The touchscreen is much more responsive now and I never noticed that complete touch freeze again.
What's about your device? Does this fix help?
Click to expand...
Click to collapse
schurgatzi said:
Is this for fixing my z2t screen sometimes just not respond to my fingers pressing keys or stuff?
Click to expand...
Click to collapse
As said above: I never noticed that complete touch freeze again
This is hasenbein1966's suggested fix, unfortunately didn't seem to make a difference to me. But then again, I don't have the issue where the screen completely freezes, only occasional unregistered touches and some glitchy two-finger gestures, when the tablet is resting on a stand or some other surfaces.
degraaff said:
This is hasenbein1966's suggested fix, unfortunately didn't seem to make a difference to me. But then again, I don't have the issue where the screen completely freezes, only occasional unregistered touches and some glitchy two-finger gestures, when the tablet is resting on a stand or some other surfaces.
Click to expand...
Click to collapse
Thanks for the hint!
According to this I searched a little bit and found another thread from hasenbein1966 on the german Android-Forum
There he reports that this TS issue is gone when he replaced the library in /system/lib/touchfilter/tftype.so with one from the Z1.
The complete thread is in german but google translate can do the (or tell me the #msg and I'll translate it for you if it's not too much
I didn't tried it since my Z2 is currently @home, but I think it's worth a try if the issue ever comes back to me.
markusmuster said:
Thanks for the hint!
According to this I searched a little bit and found another thread from hasenbein1966 on the german Android-Forum
There he reports that this TS issue is gone when he replaced the library in /system/lib/touchfilter/tftype.so with one from the Z1.
The complete thread is in german but google translate can do the (or tell me the #msg and I'll translate it for you if it's not too much
I didn't tried it since my Z2 is currently @home, but I think it's worth a try if the issue ever comes back to me.
Click to expand...
Click to collapse
Just tried the tftype4.so fix and while it doesn't fix the touch issue 100%, I definitely do see a noticeable improvement.
Update: never mind, the touch screen just went back to its usual behavior. The improvement was probably purely due to rebooting.
Update 2: yup, just got the same temporary post-reboot improvement after restoring the backup of the original touch filter file.
I suppose I will just wait until they finally start to roll-out that latest certified firmware, and see if that brings any improvement. But I don't have my hopes high since it's obviously a grounding issue, which of course is hardware-based.
I tried the "fix" involving the clearpad.idc changes, too.
It did not fix anything, I regret.
Touchscreen response is still a pain in the you-know-where.
Haha, this whole touchscreen thing is bordering on hocus-pocus...
Yes, I suggested this "fix" here weeks ago because it seemed to improve the issue back in the days when I still had the .36 firmware.
It wast just a suggestion for people to try it, I didn't claim it to be a definitive "fix" or so.
Meanwhile I had to reset the clearpad.idc values to 0.1 and 2, because annoyingly the tablet often recognized double taps when I only tapped once which made, for instance, inputting passwords nearly impossible. Now I haven't this problem anymore, so obviously clearpad.idc DOES make a difference - it's only mysterious what clearpad.idc values really do, there is no documentation available anywhere.
The touch screen is also rather dependent on weather - here in Germany it's now hot and humid, and touchscreen operation, especially with greasy hands, is less reliable than in cooler, drier weather.
hasenbein1966 said:
Haha, this whole touchscreen thing is bordering on hocus-pocus...
Yes, I suggested this "fix" here weeks ago because it seemed to improve the issue back in the days when I still had the .36 firmware.
It wast just a suggestion for people to try it, I didn't claim it to be a definitive "fix" or so.
Meanwhile I had to reset the clearpad.idc values to 0.1 and 2, because annoyingly the tablet often recognized double taps when I only tapped once which made, for instance, inputting passwords nearly impossible. Now I haven't this problem anymore, so obviously clearpad.idc DOES make a difference - it's only mysterious what clearpad.idc values really do, there is no documentation available anywhere.
The touch screen is also rather dependent on weather - here in Germany it's now hot and humid, and touchscreen operation, especially with greasy hands, is less reliable than in cooler, drier weather.
Click to expand...
Click to collapse
Double taps are painful experiences! I can hardly stand it.. So you completely fixed double taps problem? May I have your clearpad.idc code? And one more question is what's your rom region and version? I want to flash my tablet if your rom and method can solve this problem
Thanks a lot!!
xjoewoo said:
Double taps are painful experiences! I can hardly stand it.. So you completely fixed double taps problem? May I have your clearpad.idc code? And one more question is what's your rom region and version? I want to flash my tablet if your rom and method can solve this problem
Thanks a lot!!
Click to expand...
Click to collapse
He only restored his clearpad to factory default, so your clearpad is most likely the same as his.