I would like to research which parameters could be altered in which way by the user to correct the touchscreen problem.
There are some SGP521 users who already got the new .55 firmware and report that the touch problem is gone on their device.
Could please one of you post the content of the file
Code:
/system/usr/idc/clearpad.idc
? This would be very nice, because we then could see whether it's just altered values in that file which can perhaps be adopted by other users.
(Altered the values already myself, but improvement is only partial.)
Thanks in advance!
Here you go:
# Device Type
touch.deviceType = touchScreen
# Pressure
touch.pressure.scale = 0.01
# Size
touch.size.scale = 16.63
# Touch Filter
touch.filter.level = 2
touch.filter.path = /system/lib/touchfilter/tftype4.so
touch.filter.tftype4.Enabled = 1
touch.filter.tftype4.AssumedDelayFactorA = -11.71
touch.filter.tftype4.AssumedDelayFactorB = 12.53
touch.filter.tftype4.AssumedDelayFactorC = -0.81
touch.filter.tftype4.MaxSpeed = 0.036
touch.filter.tftype4.PositionFactorA = 0.2
touch.filter.tftype4.PStablePositionFactor = 0
touch.filter.tftype4.DirectivePriorityFactor = 0.95
touch.filter.tftype4.LatestSpeedWeight = 0.9
touch.filter.tftype4.GapResolver = 0.8
touch.filter.tftype4.OrgSize = 8
touch.filter.tftype4.AccSize = 8
touch.filter.tftype4.AddInitialAcc = 1
touch.filter.tftype4.DefaultInitialAcc = 0
touch.filter.tftype4.DragRangeSize = 3
touch.filter.tftype4.NoAccDistanceMin = 15.0
touch.filter.tftype4.NoAccDistanceMax = 500.0
touch.filter.tftype4.NoAccRate = 0.3
Gesendet von meinem SGP521 mit Tapatalk
Does your device have any touchscreen problems, or is reaction always perfect?
I had followed all the complaints about the touch input and was concerned about that when I finally got my tab a few days ago. When I turned on the tablet for the first time I immediately got an update notification and updated to the. 55 fw, so I cannot compare to how it was with the previous firmware version. This one is just fine and I have not been experiencing any problems so far!
I am so glad because that was the only thing speaking against this great tablet and would really have been a dealbraker...
Gesendet von meinem SGP521 mit Tapatalk
Here's the next one, taken from a "German" device, bought via Sony.
BUT: LTE version suffers of the same touchscreen issue.
Right at the first start, the Z2 rebooted itself without any user intervention, showing that famous green Android with the rotating polyhedron - so system files got changed. After the second boot, the system updated to V2.55.
NO touchscreen issues for about two days, no "loose feel at the right bezel", no creaking sounds if pushing down on the right bezel. See the thread here at XDA. Reason might be a deformation of the tablet's body, device is slightly curved. You can see that by peeking along the long side.
Then creaking started, at the same time the touchscreen began behaving erratic. I don't know if there's any connection, just to mention it.
Here's the file's contents...
# Device Type
touch.deviceType = touchScreen
# Pressure
touch.pressure.scale = 0.01
# Size
touch.size.scale = 16.63
# Touch Filter
touch.filter.level = 2
touch.filter.path = /system/lib/touchfilter/tftype4.so
touch.filter.tftype4.Enabled = 1
touch.filter.tftype4.AssumedDelayFactorA = -11.71
touch.filter.tftype4.AssumedDelayFactorB = 12.53
touch.filter.tftype4.AssumedDelayFactorC = -0.81
touch.filter.tftype4.MaxSpeed = 0.036
touch.filter.tftype4.PositionFactorA = 0.2
touch.filter.tftype4.PStablePositionFactor = 0
touch.filter.tftype4.DirectivePriorityFactor = 0.95
touch.filter.tftype4.LatestSpeedWeight = 0.9
touch.filter.tftype4.GapResolver = 0.8
touch.filter.tftype4.OrgSize = 8
touch.filter.tftype4.AccSize = 8
touch.filter.tftype4.AddInitialAcc = 1
touch.filter.tftype4.DefaultInitialAcc = 0
touch.filter.tftype4.DragRangeSize = 3
touch.filter.tftype4.NoAccDistanceMin = 15.0
touch.filter.tftype4.NoAccDistanceMax = 500.0
touch.filter.tftype4.NoAccRate = 0.3
I have the lte version with the latest update but still have touchscreen issues.. its mostly an issue when its laying flat on its back.
Hi all, are we all sure that this is only a software issue? If so,i will wait for the Software update. If not, i will change into the lte Version. Many thanks
Gesendet von meinem SGP512 mit Tapatalk
silver2k1 said:
Hi all, are we all sure that this is only a software issue? If so,i will wait for the Software update. If not, i will change into the lte Version.
Click to expand...
Click to collapse
Not logical!
Tumpin and Chefproll both have the LTE model with .55 firmware and report that the touchscreen has issues under certain circumstances.
So nothing is won with changing to the LTE version!
With my "own" fix, my Wifi tablet is on the same "almost ok" level (when in hands, all is 100% ok; when lying around or in a stand, dependent on the material, there are missed touches). Interestingly, when I lay the tablet on the blanket in bed, I can type and touch without problems; when I lay it on the bedcover, touchscreen becomes less responsive...
Sounds like the same then. So I doubt a change to the lte Version would help then. Your own fix requires a root? I just remember when i had the most issues tablet was on the table in a stand and i used a physical keyboard. It made me mad, do you think this will improve when rooting and patching?
Gesendet von meinem SGP512 mit Tapatalk
clearpad.idc
I'm testing few minutes, sgp521 lte europe edition, sw version 2.36. Tablet's offering OTA update to 2.55 (5MB) to download. Here is v2.36 clearpad.idc content:
Code:
# Device Type
touch.deviceType = touchScreen
# Pressure
touch.pressure.scale = 0.01
# Size
touch.size.scale = 16.63
# Touch Filter
touch.filter.level = 2
touch.filter.path = /system/lib/touchfilter/tftype4.so
touch.filter.tftype4.Enabled = 1
touch.filter.tftype4.AssumedDelayFactorA = -11.71
touch.filter.tftype4.AssumedDelayFactorB = 12.53
touch.filter.tftype4.AssumedDelayFactorC = -0.81
touch.filter.tftype4.MaxSpeed = 0.036
touch.filter.tftype4.PositionFactorA = 0.2
touch.filter.tftype4.PStablePositionFactor = 0
touch.filter.tftype4.DirectivePriorityFactor = 0.95
touch.filter.tftype4.LatestSpeedWeight = 0.9
touch.filter.tftype4.GapResolver = 0.8
touch.filter.tftype4.OrgSize = 8
touch.filter.tftype4.AccSize = 8
touch.filter.tftype4.AddInitialAcc = 1
touch.filter.tftype4.DefaultInitialAcc = 0
touch.filter.tftype4.DragRangeSize = 3
touch.filter.tftype4.NoAccDistanceMin = 15.0
touch.filter.tftype4.NoAccDistanceMax = 500.0
touch.filter.tftype4.NoAccRate = 0.3
I guess same as 2.55 posted before. I'll update system and compare file later. My first feeling with v2.36: touch issue, when it lay on table.
My experience with the touch issues
Just to add my input on the touch issues.
I've tried the original fw (don't remember the number) and the .55 fw.
The first fw was pretty bad with touch sensitivity (I'd rate it 2-3 out of 10) requiring a full pad of finger tip touch to register, sometimes (about 60% of the time) having to touch several times to get a response.
The second fw requires a much lighter touch and registers about 95% of the time but there seems to be another issue with it in that if the device is in deep sleep for a while the screen takes about 15-20 seconds to wake up and start registering touches.
I don't remember if the first fw had the deep sleep issue because I updated pretty quickly after discovering the first fw's major flaw.
Ideally there would be no lag for the touch sensors to wake up and the responsiveness would be improved even further, the responsiveness is still not as good as other recent Sony devices (I have used Z, Z1 and Tablet Z).
Just my two cents to anyone baking a fix.
Ricky D said:
Just to add my input on the touch issues.
I've tried the original fw (don't remember the number) and the .55 fw.
The first fw was pretty bad with touch sensitivity (I'd rate it 2-3 out of 10) requiring a full pad of finger tip touch to register, sometimes (about 60% of the time) having to touch several times to get a response.
The second fw requires a much lighter touch and registers about 95% of the time but there seems to be another issue with it in that if the device is in deep sleep for a while the screen takes about 15-20 seconds to wake up and start registering touches.
I don't remember if the first fw had the deep sleep issue because I updated pretty quickly after discovering the first fw's major flaw.
Ideally there would be no lag for the touch sensors to wake up and the responsiveness would be improved even further, the responsiveness is still not as good as other recent Sony devices (I have used Z, Z1 and Tablet Z).
Just my two cents to anyone baking a fix.
Click to expand...
Click to collapse
I have the problem with the tocuh freezing from time to time, mostly occurs while charging tho. Have to unplug the charger the touch comes back, BUT it has happened without charging aswell. I have the older version. I wonder when they will update the none-lte versions to .55?
Skogstoken said:
I have the problem with the tocuh freezing from time to time, mostly occurs while charging tho. Have to unplug the charger the touch comes back, BUT it has happened without charging aswell. I have the older version. I wonder when they will update the none-lte versions to .55?
Click to expand...
Click to collapse
Even with. 55 the touch isn't great especially down the sides...
tumpin said:
Even with. 55 the touch isn't great especially down the sides...
Click to expand...
Click to collapse
The most annoying problems with the touch not responding is when I am trying to close tabs in Chrome. Thats near impossible at sometimes and you are telling me that still occurs in .55? ;<
Skogstoken said:
The most annoying problems with the touch not responding is when I am trying to close tabs in Chrome. Thats near impossible at sometimes and you are telling me that still occurs in .55? ;<
Click to expand...
Click to collapse
It does on mine.. It doesn't always register touches. I only just got mine and it updated to .55 straight away so I dont know how it compares to before .55.
I find its worse when the device is lying on its back, do you get that? If I hold it up its not as bad. I really would like to know if this is a hardware or a software problem.
tumpin said:
It does on mine.. It doesn't always register touches. I only just got mine and it updated to .55 straight away so I dont know how it compares to before .55.
I find its worse when the device is lying on its back, do you get that? If I hold it up its not as bad. I really would like to know if this is a hardware or a software problem.
Click to expand...
Click to collapse
Ah ok, well thats my biggest problem.
Yeah I have alot of problems to when the tablet is lying flat, especially on a softer surface, like a bed or something. If you combine that with the task of closing a Chrome tab you could almost make a comic show out of it...
Skogstoken said:
Ah ok, well thats my biggest problem.
Yeah I have alot of problems to when the tablet is lying flat, especially on a softer surface, like a bed or something. If you combine that with the task of closing a Chrome tab you could almost make a comic show out of it...
Click to expand...
Click to collapse
Yes on the bed its very noticeably worse which is strange! So I guess we know .55 doesnt fix that. Could this be hardware and does it affect everyone or just some of us? Oh man I really dont wanna have to send this thing back, its perfect for my needs.
---------- Post added at 12:08 PM ---------- Previous post was at 11:34 AM ----------
tumpin said:
Yes on the bed its very noticeably worse which is strange! So I guess we know .55 doesnt fix that. Could this be hardware and does it affect everyone or just some of us? Oh man I really dont wanna have to send this thing back, its perfect for my needs.
Click to expand...
Click to collapse
I have just received the official dock. When its in the dock the touch screen plays up, especially the home and back button.. I have to tap theback button about 5 times to get it to register..
tumpin said:
Yes on the bed its very noticeably worse which is strange! So I guess we know .55 doesnt fix that. Could this be hardware and does it affect everyone or just some of us? Oh man I really dont wanna have to send this thing back, its perfect for my needs.
---------- Post added at 12:08 PM ---------- Previous post was at 11:34 AM ----------
I have just received the official dock. When its in the dock the touch screen plays up, especially the home and back button.. I have to tap theback button about 5 times to get it to register..
Click to expand...
Click to collapse
Hmm I like the tablet aswell but one of the most important things about a tablet is touch response, the whole decive depends on it and if its not working like it should I am afraid I will have to return it ;(. I hoped that the .55 version solved the problem but when you say that you still have I am not to confident anymore.
Do you mean the official case or the charging dock?
Skogstoken said:
Hmm I like the tablet aswell but one of the most important things about a tablet is touch response, the whole decive depends on it and if its not working like it should I am afraid I will have to return it ;(. I hoped that the .55 version solved the problem but when you say that you still have I am not to confident anymore.
Do you mean the official case or the charging dock?
Click to expand...
Click to collapse
I mean the official charging dock. When in the dock it barely registers the home and back buttons. Can anyone else confirm this with .55? Maybe mine is just dodgy..
Skogstoken said:
The most annoying problems with the touch not responding is when I am trying to close tabs in Chrome. Thats near impossible at sometimes and you are telling me that still occurs in .55? ;<
Click to expand...
Click to collapse
It still occurs in .55 but is 90% fixed. For me the older FW is unbearable and completely unusable (like using a resistive touch screen with a 10 pence piece glued to your fingertip).
The newer FW is just about usable daily, it drops touches occasionally (it's still annoying) and the screen appears dead around 5 times a day (by my usage).
Related
Are there other ways to increase the touchscreen sensitivity? or Increase the X10 multi-touch Accuracy?
I want to ask this question too, but just specific on accuracy.
When I use apps to test the muiltitouch function, it will show a completely wrong result when I using two fingers.
It just show the result just like a "X"
(Assume that the end points of \ are my fingers and the end points of another / are the result)
eh_hk said:
I want to ask this question too, but just specific on accuracy.
When I use apps to test the muiltitouch function, it will show a completely wrong result when I using two fingers.
It just show the result just like a "X"
(Assume that the end points of \ are my fingers and the end points of another / are the result)
Click to expand...
Click to collapse
jrchan01 said:
Are there other ways to increase the touchscreen sensitivity? or Increase the X10 multi-touch Accuracy?
Click to expand...
Click to collapse
Short answer = (almost) "Impossible"
Almost cuz - you can maybe get the Multi-touch if you write the drivers from scratch (I guess you aren't good to driver coding )
Guys, accuracy and sensitivity are the opposite of capacitive touchscreens...
Its the bad on their technology and it is currently impossible to adjust their performance.Hw doesnt support it.
All is caused by massive "cool" fingerfriendy display hungry population.
Btw I am still crying for good phone with stylus performace screen capable for drawing...
So...
maybe I just pretend I am using a phone without muiltitouch
Is anyone able to play with the Archos 80 9g?
I got the Turbo 1,5ghz version but im not able to play frontline commando or shadowgun because the touchscreen is.. how should i say.. maybe unresponsive?
it feels like the touchscreens resolutions itself is very low and you cant aim precisely. Using latest Archos ICS (4.06 atm)
cheers
*snip*
I have the same issue..maybe a anti reflex display protection might work? I know that they make a smooth and "soft" feeling!
Ncyde47 said:
Is anyone able to play with the Archos 80 9g?
I got the Turbo 1,5ghz version but im not able to play frontline commando or shadowgun because the touchscreen is.. how should i say.. maybe unresponsive?
it feels like the touchscreens resolutions itself is very low and you cant aim precisely. Using latest Archos ICS (4.06 atm)
cheers
Click to expand...
Click to collapse
I noticed the exact same thing.
I installed the following app from the Play store:
Input Benchmark (not allowed to post external links yet)
It's really simple and it has only three tests: Touch, Accelerometer, Multitouch.
Touch test shows the frequency of the touch events. My G9 shows only 50 to 52 touch events per second if you move your finger really fast. My phone (Samsung Galaxy Spica) shows 60 events per second.
Accelerometer shows around 130 events per second, and my phone shows around 100 events per second.
The multi-touch test shows the pixel positions of all touch points. My phone can detect sub-pixel changes. After you calculate the touch resolution it recognizes around 1024*1024 touch points on a 3.2 inch screen (480x320).
My Archos G9 80 Turbo shows only around 227*227 touch points. Usually the touch quantization works out to 3.37335 pixels vertical and 4.4978 pixels horizontal. This means that the touchscreen cannot resolve finer movements, and this is the reason why homescreen scrolling from left to right looks very choppy if you keep your finger on the screen, and much smoother if you fling (start the transition with rapid finger movement and take the finger off of the screen). Sometimes I got other pixel values that were about in between other the values I usually got. I think that this means that the touchscreen is at least capable of double the current precision (probably around 512*512 touch points), but it still lags behind my phone from 2009/2010.
In the teardown tread the touchscreen controller is identified as Cypress TMA 340. I found some Cypress presentations that classify this as a 3rd Generation touchscreen controller that is intended for screens with less than 5.1" diagonal, with a notice that 4 point multi-touch should be used on screens smaller than 4.6 inches.
I found that HTC Sensation (that had a lot of touchscreen issues) also uses a Cypress TMA 340 series 4-point multi-touch digitizer as a replacement digitizer (there are at least 4 different digitizers used on the Sensation production). On a international HTC Sensation I get around 1024*1024 touch points resolution @ 60 touch events per second, so the controller should be capable of at least that. It isn't ideal for our screen size but it would be a significant improvement over the current situation.
This means the issue could be either hardware (the capacitive matrix is low-res), or software (the driver is broken or poorly written). If the issue is hardware, we can't do anything about it (except to perhaps replace the digitizer with a better one, and add support for it in the kernel). If the issue is software, we maybe get some improvement later via improved or tweaked drivers (Cypress has released their drivers as open source)
Perhaps there is a trade off between 4-point multi-touch and 2-point multi-touch, and we could get better touch resolution if we allow only 2-point multi-touch.
neur0mans3r said:
...
My Archos G9 80 Turbo shows only around 227*227 touch points. Usually the touch quantization works out to 3.37335 pixels vertical and 4.4978 pixels horizontal. This means that the touchscreen cannot resolve finer movements...
Click to expand...
Click to collapse
This explains why when using a stylus and drawing a diagonal line I see an image that looks like a fine staircase rather than a smooth line.
So what can we do?
Does any1 know if Archos is aware of this fact?
Anyone willing to downgrade to honeycomb and test? Then we can know if its a kernel problem or a hardware problem
I made a basic test that displays the touch data provided by Android. For my G9 80 it shows a touchscreen resolution of 2048x2048, but in most cases the actual resolution is much lower.
When you move your finger horizontally or vertically, the difference between touch points on the main axis (the direction your finger is moving) is around 9 points (around 4.5 pixels horizontally and 3.37 pixels vertically). However, on the other axis you get much better results (all the way down to 1 touch point). The apparent touchscreen resolution depends on the angle between the motion of the finger and the horizontal and vertical axises of the digitizer.
To recap, in the most basic use case when moving your finger horizontally to navigate homescreen and app drawer, you get stuttering because the touch events are reported like that, not because the hardware is slow to render.
Since in games you usually move your fingers in the direction you need them to go this does not work as expected because the aiming jumps around too much.
I really hope this is a driver issue (some sort of poorly written averaging filter).
Shano56 said:
Anyone willing to downgrade to honeycomb and test? Then we can know if its a kernel problem or a hardware problem
Click to expand...
Click to collapse
I am on Honeycomb most of the time (my Gen9 doesn't like ICS)
Gen9 101 1GHz 512MB, using Input Benchmark:
Touch- 62-75 Hz
Accelerometer- 125-130 Hz
Multitouch- max x-y is correct (1280x800) but touch point move is registered
a)for "normal" speed- every 4-5 pixels for X and every 3-4 pixels for Y
b)for slow speed (press a finger to the touchscreen and tilt it slowly left/right)- readings are inaccurate- it registers 1 pix for X and 1 pix for Y but there is plenty of places where registered point "goes back" (eg- 630->tilt right->blinks between 627 and 631) and/or touch is not detected (this also flickers)
neur0mans3r said:
My phone (Samsung Galaxy Spica) shows 60 events per second.
Click to expand...
Click to collapse
I guess you use tom3q's CM7?
Were you by any chance using FrankenKenrel or FrozenLake previosuly?
gen_scheisskopf said:
I guess you use tom3q's CM7?
Were you by any chance using FrankenKenrel or FrozenLake previosuly?
Click to expand...
Click to collapse
Yes, tom3q's CM7 with the underclocked-overclocked-synced kernel (sound silly but is an accurate description) . I was mainly using Yonip kernels with FroYo.
I made a simple test app (attached in the above post) that shows the difference in the coordinates of touch events in pixels and touch points themselves. I tried it on a HTC Sensation and it's working OK with sub-pixel precision.
It looks like this behavior is not ICS specific, but Archos specific (maybe even G9 80 specific).
neur0mans3r said:
Yes, tom3q's CM7 with the underclocked-overclocked-synced kernel (sound silly but is an accurate description) .
Click to expand...
Click to collapse
I know what you mean, I did some pre-alpha tests for tom3q
neur0mans3r said:
I was mainly using Yonip kernels with FroYo.
Click to expand...
Click to collapse
Competition.....
FrankenKernel was for Ecalir btw
neur0mans3r said:
I made a simple test app (attached in the above post) that shows the difference in the coordinates of touch events in pixels and touch points themselves. I tried it on a HTC Sensation and it's working OK with sub-pixel precision.
It looks like this behavior is not ICS specific, but Archos specific (maybe even G9 80 specific).
Click to expand...
Click to collapse
Tested and
-"normal" speed 4-5 pixel precision for both X and Y
-slow speed- 4-5 pixel precision for the main movement axis and at the same time 1 pixel precision for the second axis
gen_scheisskopf said:
Tested and
-"normal" speed 4-5 pixel precision for both X and Y
-slow speed- 4-5 pixel precision for the main movement axis and at the same time 1 pixel precision for the second axis
Click to expand...
Click to collapse
I think the difference in touch points is more representative because we get an integer (4-5 pixels is 9-10 touch points).
Main question is can this be fixed (or atleast improved somewhat) with a driver update/fix, or is this a limitiation of the digitizer.
P.S. I skipped Eclair and went straight to criminal's CM 6.1.
neur0mans3r said:
I think the difference in touch points is more representative because we get an integer (4-5 pixels is 9-10 touch points).
Main question is can this be fixed (or atleast improved somewhat) with a driver update/fix, or is this a limitiation of the digitizer.
Click to expand...
Click to collapse
Main question- how outdated are drivers and touchscreen firmware (if present), and who wrote them (read: can we source newer/not broken/just better ones?)
neur0mans3r said:
P.S. I skipped Eclair and went straight to criminal's CM 6.1.
Click to expand...
Click to collapse
SM-Froyo by any chance?
gen_scheisskopf said:
Main question- how outdated are drivers and touchscreen firmware (if present), and who wrote them (read: can we source newer/not broken/just better ones?)
Click to expand...
Click to collapse
Look in the hardware hacking thread, it looks like we only need to set a smaller active distance value in the controller configuration. I think the default value (8) is used (maybe the active distance value is not even configured explicitly so it defaults to 8).
gen_scheisskopf said:
SM-Froyo by any chance?
Click to expand...
Click to collapse
I used Voku's CM Mod+X for quite some time also, but then the phone would freeze and/or crash when using 3G to surf while commuting. After I lost data due to a damaged /data ext2 partition, I switched to CM7.4. It's really stable for me (over 400h uptime today, battery lasts 3 days since I don't use the phone much).
neur0mans3r said:
Look in the hardware hacking thread, it looks like we only need to set a smaller active distance value in the controller configuration. I think the default value (8) is used (maybe the active distance value is not even configured explicitly so it defaults to 8).
Click to expand...
Click to collapse
I've seen your post. Unfortunately I don't have enough time to dig in sources now
neur0mans3r said:
I used Voku's CM Mod+X for quite some time also
Click to expand...
Click to collapse
...which is based on SpicagenMod
gen_scheisskopf, by any chance, have you tried new 4.0.7? What problems did your G9 have on ICS? I suggest you RMA that s***
Shano56 said:
gen_scheisskopf, by any chance, have you tried new 4.0.7?
Click to expand...
Click to collapse
Nope, last ICS I used was 4.0.6-test4
Shano56 said:
What problems did your G9 have on ICS?
Click to expand...
Click to collapse
-device gets hot quite fast and it's quite hot even when I use not very demanding apps (pdf readers mostly)
-connected with above- shorter battery life
-there are system freezes (reset required) even when using not very demanding apps
-there seems to be a problem with memory management- sometimes using "ram heavy" app (like Firefox or Aurora) shell restarts
Shano56 said:
I suggest you RMA that s***
Click to expand...
Click to collapse
I have to contact service anyway- charger died
Anyway before that I have to return to stock partition layout (and I need tablet right now, still 5 test to pass, all materials are in pdf and reading them on a PC is killing me)
Tell them your GPS doesn't work or something, they'll say its a hardware error and replace it
Shano56 said:
Tell them your GPS doesn't work or something, they'll say its a hardware error and replace it
Click to expand...
Click to collapse
I don't know what is required to replace the device (maybe I'll run an infinite benchamark loop on ICS with tablet wrapped in a blanket or something? )
gen_scheisskopf said:
I don't know what is required to replace the device (maybe I'll run an infinite benchamark loop on ICS with tablet wrapped in a blanket or something? )
Click to expand...
Click to collapse
my otg usb port/charger port stopped working like many others, i simply said the device no longer received a charge (wasn't sure if it was the chargers fault or the tablets fault) and they said to ship the tablet and shipped a replacement to me after they received.
Hello all and please forgive my poor english
I really love this tablet (thickness, battery, weight, screen) BUT i have a major problem with it : i often need to tap 2 or 3 times on something in order to launch/select it and it ruins my global experience with the tablet :crying:
Do you guys have this problem and is there a way to alter the sensivity of the screen ?
Thanks
yanouch said:
Hello all and please forgive my poor english
I really love this tablet (thickness, battery, weight, screen) BUT i have a major problem with it : i often need to tap 2 or 3 times on something in order to launch/select it and it ruins my global experience with the tablet :crying:
Do you guys have this problem and is there a way to alter the sensivity of the screen ?
Thanks
Click to expand...
Click to collapse
Yes, I have the same problem. Some say, it's software issue, and suggest to wait until tab gets updated.
xbad1 said:
Yes, I have the same problem. Some say, it's software issue, and suggest to wait until tab gets updated.
Click to expand...
Click to collapse
Yeah that's what i expected but wanted just to know if others had the same problem and if there was already a workaround for this
Many people have this problem, including a number of reviewers.
Nevertheless Sony refuses to acknowledge the existence of the issue. When I called them, the guy said "You are the first to report such a problem". (Probably he lied and was advised "from above" to say so...)
The customer is left in the cold!
Some people have a return policy - what if one waits for a software update, the return period expires, the update comes, but it doesn't fix the problem and it turns out to be a hardware problem??
The information politics of Sony and other companies (yes, Google, you too!) is an absolute PILE OF S**T!!
Yup, me too. The annoying thing it is difficult to document. Yesterday my tablet was charging and I turned the screen on using power button - lock screen didn't react at all to my inputs. Tried switching screen on/off a few times but it didn't help. Also tried double-tap to wake with no success. Went to get my camera to document, then of course it started working...
I've written this elsewhere, but this is how I notice the touch screen problems:
For me the tablet randomly doesn't recognize touches during the below instances. In all cases either going to the home screen and relaunching the app or turning the screen off/on will solve the problem. The problems occur several times per day but not constantly.
Sometimes opening apps will cause everything but the bottom android-buttons to be non-responsive. This can happen in any app it seems, including native ones such as Google Play.
Sometimes the lockscreen doesn't recognize touches at all.
While charging I've had issues getting the touchscreen to recognize touches, disconnecting the charger has helped.
Double-tap to wake seems to be very moody, sometimes working sometimes not. Sometimes it turns the screen on even by me just holding the tablet with my palm resting against the screen.
While not a bug per se, also the android-buttons seem very picky that you have to hit them right on the spot to work.
Other threads on same topic:
http://talk.sonymobile.com/t5/Xperia-Z2-Tablet/Touch-screen-problem/m-p/620325
http://community.sony.fi/t5/Tablets/Xperia-Z2-tablet-touch-screen-issue/td-p/1582051
http://www.android-hilfe.de/sony-xp...screen-reagiert-nicht-immer-zuverlaessig.html
Damn ! i'm not alone....
One forumer said he thinks that switching OFF Stamina mode helped a little bit...
I don't have my tablet with me, can someone test this ?
"A little bit" help is NOT enough.
The touchscreen MUST work perfectly, whether with Stamina Mode on or off or whether with Mode XY on or off. No discussion.
Sony HAS to fix this.
Already solved in .55 firmware
hasenbein1966 said:
Nevertheless Sony refuses to acknowledge the existence of the issue. When I called them, the guy said "You are the first to report such a problem". (Probably he lied and was advised "from above" to say so...)
Click to expand...
Click to collapse
The same experience with Z1 compact and support. Told them the camera is really broken - they told me there is absolutely nothing wrong with the camera and I'm the first one who got this problem. That was some weeks before, now they officialy added that maybe some devices are defect.
But that´s Sony, they give a **** about u, don't even try to contact the support.
I'm also having this issue, if I'm using the Sony sleve it's impossible to use the touchscreen as it will tip over when I press hard enoug for the screen to actually register it.
No problem here.
Only early days yet. The only prob I've got atm is Dropbox isn't showing up in the Album.
Edit: Fixed the Dropbox problem by using the Dropsync app.
I also seem to get this. The tablet works fine when tilted at an angle but for some reason can be completely unresponsive when it's laid flat. Would this suggest a hardware issue or a software bug?
I also get this, sometimes it's like I just need to press harder (so hard the tablet falls over when using the cover as a stand), but other times it seems that no matter how hard I press or how many fingers I apply it doesn't register a thing for periods at a time.
I'm lead to believe that this is either software or firmware considering the intermittent nature. Are there any custom ROMs out yet that we could flash to eliminate the software aspect?
I have same problem, most noticeable in Chrome, switching tabs fails to register 10% of time. I can only think Sony have a hardware quality control issue with the digitizer as if it was firmware related, surely everyone would be suffering. Strange none of the reviews have picked this up, but I'm going to have to return mine.
No, no, no.
It's most surely a firmware problem!
The electric current threshold for registering a touch is set too high. So if the tablet lies on a non-conducting surface, and especially if it was not touched for a longer time, there will be touch problems. Also touching the tablet with a fingernail will not suffice because nails conduct current worse than skin. Other tablets which have a lower current threshold also accept fingernail touches.
I'm very sure: If you hold the tablet with one hand and touch with the other (and don't accidentally use fingernails), touch will be OK! Right? This is because more current will flow.
The .55 firmware which is out for LTE devices already and will follow for WiFi devices lowers the threshold and thus fixes the problem.
Up to then always take the tablet in your hands when operating it.
Interesting theory, just gave it a go, inclusive, but does seem worse in case. However if Sony aware, why have they not rushed out firmware as otherwise initial user experience is ruined.
QUOTE=hasenbein1966;52005720]No, no, no.
It's most surely a firmware problem!
The electric current threshold for registering a touch is set too high. So if the tablet lies on a non-conducting surface, and especially if it was not touched for a longer time, there will be touch problems. Also touching the tablet with a fingernail will not suffice because nails conduct current worse than skin. Other tablets which have a lower current threshold also accept fingernail touches.
I'm very sure: If you hold the tablet with one hand and touch with the other (and don't accidentally use fingernails), touch will be OK! Right? This is because more current will flow.
The .55 firmware which is out for LTE devices already and will follow for WiFi devices lowers the threshold and thus fixes the problem.
Up to then always take the tablet in your hands when operating it.[/QUOTE]
POTENTIAL FIX FOUND (ROOTED ONLY)!
Rooted users can try this fix, works for me! Touch seems to work perfectly now, also when tablet not in hands and lying on non-conducting surface!
Edit the file
/system/usr/idc/clearpad.idc
and alter these two lines:
Code:
touch.pressure.scale = 0.0001
(original value: 0.1)
and
Code:
touch.filter.level = 1
(original value: 2)
Don't forget a nandroid before
Please report whether it helped! :good:
P.S.: just for the curious - on the first Tablet Z, the two values are also lower: touch.pressure.scale is 0.0074, and touch.filter.level is also only 1.
Thanks for suggestion but dont wish to root (I use it to watch Sky which wont work if rooted) - seems there is more assistance on this forum to the issue than from Sony. I'll give it another week for a firmware fix before returning it.
elaborate...
nos1609 said:
Already solved in .55 firmware
Click to expand...
Click to collapse
If this is fixed in the 55 firmware then how do you get it?
I haven't had a firmware update?
I'm using 16GB Wi-Fi only in the UK
---------- Post added at 09:17 PM ---------- Previous post was at 09:11 PM ----------
homme_fromage said:
If this is fixed in the 55 firmware then how do you get it?
I haven't had a firmware update?
I'm using 16GB Wi-Fi only in the UK
Click to expand...
Click to collapse
My bad, didn't read all the way through, ignore me.
Now after a few days I can say:
With the root fix described above, my tablet works like butter. Simply perfect. :good:
Only instance where I have still problems is when the tablet was lying around for a while and I try to operate the touchscreen without taking it in my hands. Then sometimes (not always) the screen doesn't react, but only for a short time.
The problem seems to be related to static electricity.
Hello there,
My Pocophone died yesterday. I've send it to the retailler. Dunno if there are going to fix or replace me by a new one ?
I bought it in september (first batch) and i've got touchscreen issue with the latest stable miui 10 (10.0.60)
Some have issue, other don't have the issue.
So it's LCD or Motherboard or software (which doesn't fix everything) ?
If they'll fix my phone by changing the motherboard (can't start the phone, it staying black and i can't charge it, no led blinking)
Can i hope better touchscreen ?
Thx
Install latest Pie stable or beta 8.12.10, your problem will be fixed.
hero355 said:
Install latest Pie stable or beta 8.12.10, your problem will be fixed.
Click to expand...
Click to collapse
Not really
Pie stable = touch delay around edges,try type 'q' then 'i' it outputs 'iq' pubg aimiing can't detect small swipes,
8.12.10=touch dela around edges is fixed pubg aiming fixed BUT lots of touches sometimes not registering around the nav area and if your apply so much pressure on the screen lots of ghost touch will happen
I can't install anything, i have no more phone for the moment...
I was on 10.0.60 and i have swap letter when i'm trying iq qi...
And touchdelay when scrooling down and up
Also high sensitivity on touchscreen
I've disabled multitouch screenshot
My phone has been fix by the retailler. I didn't receive it yet but the motherboard has been changed..
I'll see if i'll still have touchscreen issue when i'll get it back
TL;DR: I have a hunch that the SAR sensor is related to touch issues, which I observed by experimentation. Is there a way to tell the system I am holding my phone regardless of SAR sensor readings? (always set SAR value above threshold)
SAR - Specific Absorption Rate
Hello everyone, I posted this since i can't seem to find solutions or maybe I have just overlooked it.
As we know, Pocophone is well known to have touch screen issues, in which I have observed in my unit that it shows the issues whenever I am not holding my phone. Later I have discovered that this phone has a SAR sensor, which I think might be the cause for this touch problem since I tried holding the phone while not triggering the SAR sensor and my touches where not registered most of the time, and only registering if I press it hard. When I held my phone while triggering the SAR sensor, the touches worked properly again.
Is there a way to always send data that I am holding my phone? (i.e.: always send a "held state" regardless of SAR reading?)
SAR readings are accessible on : Settings > About Phone > Kernel Version tap 3× to enter CIT > scroll to the bottom #35
aztigin009 said:
SAR readings are accessible on : Settings > About Phone > Kernel Version tap 3× to enter CIT > scroll to the bottom #35
Click to expand...
Click to collapse
I did the SAR test. CS0 ranges between 2900 to 3400 when holding with one hand on the top. When I approached the other hand to the bottom of the phone CS0 ranges from 12000 to 14000.
CS2 is always at 22000.
I never had any touch screen issues on my Poco. Not with Android 8.1 nor Android 9 none of the miui 10 updates had touch issues, I am currently on 10.3.6
Most of the time I am wearing rather thick rubber gloves and I'm not holding the phone, it's just laying over a metal or plastic surface.
I hope it helps shedding some light into your suspicions
Cheers
Thank you so much for yur response!
Maybe this is not a more general issue as I had initially thought, since I considered this when I read about other people having touch issues when they don't touch their units.
TheBlackening said:
I did the SAR test. CS0 ranges between 2900 to 3400 when holding with one hand on the top. When I approached the other hand to the bottom of the phone CS0 ranges from 12000 to 14000.
CS2 is always at 22000.
I never had any touch screen issues on my Poco. Not with Android 8.1 nor Android 9 none of the miui 10 updates had touch issues, I am currently on 10.3.6
Most of the time I am wearing rather thick rubber gloves and I'm not holding the phone, it's just laying over a metal or plastic surface.
I hope it helps shedding some light into your suspicions
Cheers
Click to expand...
Click to collapse
RESOLVED
The root cause has not been found but the latest update (MIUI Global 11.0.5. 0) fixed this touch issue.
My SAR reading are a bit different from before, which maintains a higher value than before even without physical contact(high value means there is a presence of tissue nearby) , but I am not entirely sure if it is related.
Thank you for your kind responses!
Whenever my hands are little wet with water or sweat My touch doesn't respond and Ghost touches appears. Then i just wipe up my hands and everything works well . Hope that helps.