Users who already have .69 update - help with info from you needed!

Search This thread

hasenbein1966

Senior Member
Aug 9, 2011
1,129
337
@ all who already have the .69 update:

Would be really great if you could post here the content of the file

Code:
/system/usr/idc/clearpad.idc
(use, for instance, ES file explorer to access it, no root needed for that).

So we can find out whether the improved touchscreen response in the update has anything to do with altered parameters in that file.

Thanks in advance!
 

Ricky D

Senior Member
Apr 7, 2010
177
53
Doncaster + Beijing
FW 17.1.A.2.69

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
 

xsacha

Senior Member
Sep 18, 2008
327
230

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

Original firmware

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


Sent from my SGP521 using XDA Premium 4 mobile app
 
Last edited:

hasenbein1966

Senior Member
Aug 9, 2011
1,129
337
OK, so if there really is a fix in .69, it has absolutely nothing to do with clearpad.idc, since the values are always exactly the same in every firmware iteration.:cool:
 

Ricky D

Senior Member
Apr 7, 2010
177
53
Doncaster + Beijing
OK, so if there really is a fix in .69, it has absolutely nothing to do with clearpad.idc, since the values are always exactly the same in every firmware iteration.:cool:

always may not be exactly correct, all is maybe what you meant, in this FW update the values in this file haven't changed.

Code:
touch.filter.path = /system/lib/touchfilter/tftype4.so

This file is referenced and may have changed.

Also, there may be other factors e.g. a break in the commands that wake up the touch-screen from deep sleep or just better overall CPU responsiveness resulting in a clearing of a bottleneck of processes elsewhere.
 
  • Like
Reactions: hasenbein1966

tumpin

Senior Member
Mar 10, 2009
121
12
Is .69 being pushed out over the air? Im still on .55 but no option to update. Support site says .55 is latest version also.
 

Vidd

Member
Sep 1, 2007
19
0
Hey, in the same vein, does this fix any issue with audio lag or video playback in the likes of Netflix?

Sitting on .36 here with no update available.
 

Ricky D

Senior Member
Apr 7, 2010
177
53
Doncaster + Beijing
These questions aren't really following the OP of this thread, but I'll answer anyway.

Is .69 being pushed out over the air? Im still on .55 but no option to update. Support site says .55 is latest version also.
Hey, in the same vein, does this fix any issue with audio lag or video playback in the likes of Netflix?

Sitting on .36 here with no update available.

PCC or SUS is where I found this update for my device, I didn't get an OTA update message. Your customisation or model number may not have the FW released yet. but keep checking SUS is what I suggest.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    OK, so if there really is a fix in .69, it has absolutely nothing to do with clearpad.idc, since the values are always exactly the same in every firmware iteration.:cool:

    always may not be exactly correct, all is maybe what you meant, in this FW update the values in this file haven't changed.

    Code:
    touch.filter.path = /system/lib/touchfilter/tftype4.so

    This file is referenced and may have changed.

    Also, there may be other factors e.g. a break in the commands that wake up the touch-screen from deep sleep or just better overall CPU responsiveness resulting in a clearing of a bottleneck of processes elsewhere.