Allwinner A23 Tablet: Launching Camera App freezes Tablet. - Android Q&A, Help & Troubleshooting

Hello i changed the Rom on my Tablet to :
PH_A76h_android4.4_v2.0_800x480-auto-gc2035-gc0308-wifi5990p-20141211a.img
Everything works okay, but not the Camera.
The Tablet has 2 Cameras Front and Back with 0,3 Mpixels each.
The are on the same Cable going from the Mainboard to the FrontCam and then to the Back Camera.
When i launch the App the Tablet freezes.. Sometimes it resets itself after an Minute or so (not always)
BTW:
I have saved the Data of the Nand-Partitions with the old Firmware (if you need some infos/settings/config from them)
I also have changed the script0.bin from the old Firmware to fex and changed everything in DragonFaces SystemConfiguration like it was in the Script0.bin from the original Firmware.
Here is the Block i Changed in System-Editor:
Code:
;--------------------------------------------------------------------------------
;vip (video input port) configuration
;vip_used: 0:disable 1:enable
;vip_mode: 0:sample one interface to one buffer 1:sample two interface to one buffer
;vip_dev_qty: The quantity of devices linked to capture bus
;vip_dev(x)_isp_used 0: not use isp 1:use isp
;vip_dev(x)_fmt: 0:yuv 1:bayer raw rgb
;vip_dev(x)_stby_mode: 0:not shut down power at standby 1:shut down power at standby
;vip_dev(x)_vflip: flip in vertical direction 0:disable 1:enable
;vip_dev(x)_hflip: flip in horizontal direction 0:disable 1:enable
;vip_dev(x)_iovdd: camera module io power handle string, pmu power supply
;vip_dev(x)_iovdd_vol: camera module io power voltage, pmu power supply
;vip_dev(x)_avdd: camera module analog power handle string, pmu power supply
;vip_dev(x)_avdd_vol: camera module analog power voltage, pmu power supply
;vip_dev(x)_dvdd: camera module core power handle string, pmu power supply
;vip_dev(x)_dvdd_vol: camera module core power voltage, pmu power supply
;vip_dev(x)_afvdd: camera module vcm power handle string, pmu power supply
;vip_dev(x)_afvdd_vol: camera module vcm power voltage, pmu power supply
;x indicates the index of the devices which are linked to the same capture bus
;fill voltage in uV, e.g. iovdd = 2.8V, vip_devx_iovdd_vol = 2800000
;fill handle string as below:
;axp22_eldo3
;axp22_dldo4
;axp22_eldo2
;fill handle string "" when not using any pmu power supply
;--------------------------------------------------------------------------------
[csi0]
vip_used = 1
vip_mode = 0
vip_dev_qty = 2
vip_csi_pck = port:PE00<2><default><default><default>
vip_csi_mck = port:PE01<2><default><default><default>
vip_csi_hsync = port:PE02<2><default><default><default>
vip_csi_vsync = port:PE03<2><default><default><default>
vip_csi_d0 = port:PE04<2><default><default><default>
vip_csi_d1 = port:PE05<2><default><default><default>
vip_csi_d2 = port:PE06<2><default><default><default>
vip_csi_d3 = port:PE07<2><default><default><default>
vip_csi_d4 = port:PE08<2><default><default><default>
vip_csi_d5 = port:PE09<2><default><default><default>
vip_csi_d6 = port:PE10<2><default><default><default>
vip_csi_d7 = port:PE11<2><default><default><default>
vip_dev0_mname = "siv121d"
vip_dev0_lane = 1
vip_dev0_twi_id = 2
vip_dev0_twi_addr = 102
vip_dev0_isp_used = 0
vip_dev0_fmt = 0
vip_dev0_stby_mode = 0
vip_dev0_vflip = 0
vip_dev0_hflip = 0
vip_dev0_iovdd = "axp22_dldo3"
vip_dev0_iovdd_vol = 2800000
vip_dev0_avdd = "axp22_ldoio0" vip_dev0_avdd_vol = 2800000
vip_dev0_dvdd = "axp22_eldo2" vip_dev0_dvdd_vol = 1800000
vip_dev0_afvdd = ""
vip_dev0_afvdd_vol = 2800000
vip_dev0_power_en =
vip_dev0_reset = port:PE14<1><default><default><0>
vip_dev0_pwdn = port:PE15<1><default><default><1>
vip_dev0_flash_en = port:PB00<1><default><default><0>
vip_dev0_flash_mode =
vip_dev0_af_pwdn =
vip_dev1_mname = "siv121d"
vip_dev1_lane = 1
vip_dev1_twi_id = 2
vip_dev1_twi_addr = 102
vip_dev1_isp_used = 0
vip_dev1_fmt = 0
vip_dev1_stby_mode = 0
vip_dev1_vflip = 0
vip_dev1_hflip = 0
vip_dev1_iovdd = "axp22_dldo3"
vip_dev1_iovdd_vol = 2800000
vip_dev1_avdd = "axp22_ldoio0"
vip_dev1_avdd_vol = 2800000
vip_dev1_dvdd = "axp22_eldo2"
vip_dev1_dvdd_vol = 1800000
vip_dev1_afvdd = ""
vip_dev1_afvdd_vol = 2800000
vip_dev1_power_en =
vip_dev1_reset = port:PE16<1><default><default><0>
vip_dev1_pwdn = port:PE17<1><default><default><1>
vip_dev1_flash_en = port:PB00<1><default><default><0>
vip_dev1_flash_mode =
vip_dev1_af_pwdn =
[camera_list_para]
camera_list_para_used = 0
ov7670 = 0
gc0308 = 1
gt2005 = 0
hi704 = 0
sp0838 = 0
mt9m112 = 0
mt9m113 = 0
gc2035 = 1
ov2655 = 0
hi253 = 1
gc0307 = 0
mt9d112 = 0
ov5640 = 0
ov5647 = 0
gc2015 = 0
ov2643 = 0
gc0329 = 0
gc0309 = 0
s5k4ec = 0
siv121d = 0
siv120d = 0
I also copied camera.cfg from the old /system/etc to the new installation.
But still freezes don't know what to do now.
Please help.

Related

[Xperia U][JB] Camera error - cfg-file settings maybe wrong in ported jb?

I noticed differences between the cflashlib.cfg of ICS and the ported version of JB.
ICS:
# Configuration file for CFlashDriver.
#
# CFlashDriver is an interface towards ST-Ericssons
# camera implementation.
#
# This file contains settings the the STE camera is higly dependant
# upon.
#
# *** Available flashmodes: ***
# XENON Enables xenon drv.Strobe managed by lm3561 drv.
# XENON_EXTERNAL_STROBE Enables xenon drv.Strobe managed externally.
# VIDEO_LED Enables the video led driver. Strobing is managed by the driver
# VIDEO_LED_EXTERNAL_STROBE Enables video led driver. Strobing is managed externally to driver.
# FLASH_MODE_STILL_LED Enables the still LED driver. Strobing is managed by the driver.
# STILL_LED_EXTERNAL_STROBE Enables the still LED driver. Strobe is managed externally to driver.
# AF_ASSISTANT Enables the AF assistant driver. Strobe is managed by the driver.
# INDICATOR Enable the driver. Strobe is managed by the driver.
# STILL_HPLED Enables the still HP LED driver. Strobing is managed by the driver.
# HPLED_EXTERNAL_STROBE Enables the still HP LED driver. Strobe is managed externally to
# the driver.
#
# *** Available Cameramodes ***
# Primary, Secondary
#
# The parameters and in case of boolean values, everything is highly
# case sensitive. This means the True and true are two different value.
# For those who wonder, the accespted values are "true" and "false".
# The parser does handle duplicate entries in a way that only the first
# entry of the same type is used.
#
# *** Parameter setting begin here ***
#
FlashDriverType = VIDEO_LED
MinIntensity = 18
MaxIntensity = 149
MaxStrobeDuration = 1024000
IsIntensityProgrammable = true
IsDurationProgrammable = true
IsTimeoutProgrammable = true
SupportedCamera = Primary
Duration = 0
Intensity = 100
Timeout = 0
FlashDriverType = VIDEO_LED_EXTERNAL_STROBE
MinIntensity = 18
MaxIntensity = 149
MaxStrobeDuration = 1024000
IsIntensityProgrammable = true
IsDurationProgrammable = true
IsTimeoutProgrammable = true
SupportedCamera = Primary
Duration = 0
Intensity = 100
Timeout = 0
FlashDriverType = STILL_LED
MinIntensity = 36
MaxIntensity = 600
MaxStrobeDuration = 1024000
IsIntensityProgrammable = true
IsDurationProgrammable = true
IsTimeoutProgrammable = true
SupportedCamera = Primary
Duration = 1024000
Intensity = 100
Timeout = 1024000
FlashDriverType = STILL_LED_EXTERNAL_STROBE
MinIntensity = 36
MaxIntensity = 600
MaxStrobeDuration = 1024000
IsIntensityProgrammable = true
IsDurationProgrammable = true
IsTimeoutProgrammable = true
SupportedCamera = Primary
Duration = 1024000
Intensity = 100
Timeout = 1024000
FlashDriverType = AF_ASSISTANT
MinIntensity = 18
MaxIntensity = 149
MaxStrobeDuration = 1024000
IsIntensityProgrammable = true
IsDurationProgrammable = true
IsTimeoutProgrammable = true
SupportedCamera = Primary
Duration = 0
Intensity = 100
Timeout = 0
FlashDriverType = AF_ASSISTANT
MinIntensity = 18
MaxIntensity = 149
MaxStrobeDuration = 1024000
IsIntensityProgrammable = false
IsDurationProgrammable = false
IsTimeoutProgrammable = false
SupportedCamera = Secondary
Duration = 0
Intensity = 100
Timeout = 0
Click to expand...
Click to collapse
JB:
# Configuration file for CFlashDriver.
#
# CFlashDriver is an interface towards ST-Ericssons
# camera implementation.
#
# This file contains settings the the STE camera is higly dependant
# upon.
#
# *** Available flashmodes: ***
# XENON, XENON_EXTERNAL_STROBE, VIDEO_LED, VIDEO_LED_EXTERNAL_STROBE
# STILL_LED, STILL_LED_EXTERNAL_STROBE, AF_ASSISTANT, INDICATOR
# STILL_HPLED, STILL_HPLED_EXTERNAL_STROBE
#
# *** Available Cameramodes ***
# Primary, Secondary
#
# The parameters and in case of boolean values, everything is highly
# case sensitive. This means the True and true are two different value.
# For those who wonder, the accespted values are "true" and "false".
# The parser does handle duplicate entries in a way that only the first
# entry of the same type is used.
#
# *** Parameter setting begin here ***
#
FlashDriverType = VIDEO_LED
MinIntensity = 62
MaxIntensity = 500
MaxStrobeDuration = 1024000
IsIntensityProgrammable = true
IsDurationProgrammable = true
IsTimeoutProgrammable = true
SupportedCamera = Primary
Duration = 0
Intensity = 100
Timeout = 0
FlashDriverType = VIDEO_LED_EXTERNAL_STROBE
MinIntensity = 62
MaxIntensity = 500
MaxStrobeDuration = 1024000
IsIntensityProgrammable = true
IsDurationProgrammable = true
IsTimeoutProgrammable = true
SupportedCamera = Primary
Duration = 0
Intensity = 100
Timeout = 0
FlashDriverType = STILL_LED
MinIntensity = 125
MaxIntensity = 2000
MaxStrobeDuration = 1024000
IsIntensityProgrammable = true
IsDurationProgrammable = true
IsTimeoutProgrammable = true
SupportedCamera = Primary
Duration = 1024000
Intensity = 100
Timeout = 1024000
FlashDriverType = STILL_LED_EXTERNAL_STROBE
MinIntensity = 125
MaxIntensity = 2000
MaxStrobeDuration = 1024000
IsIntensityProgrammable = true
IsDurationProgrammable = true
IsTimeoutProgrammable = true
SupportedCamera = Primary
Duration = 1024000
Intensity = 100
Timeout = 1024000
FlashDriverType = AF_ASSISTANT
MinIntensity = 62
MaxIntensity = 500
MaxStrobeDuration = 1024000
IsIntensityProgrammable = true
IsDurationProgrammable = true
IsTimeoutProgrammable = true
SupportedCamera = Primary
Duration = 0
Intensity = 100
Timeout = 0
FlashDriverType = AF_ASSISTANT
MinIntensity = 62
MaxIntensity = 500
MaxStrobeDuration = 1024000
IsIntensityProgrammable = false
IsDurationProgrammable = false
IsTimeoutProgrammable = false
SupportedCamera = Secondary
Duration = 0
Intensity = 100
Timeout = 0
Click to expand...
Click to collapse
Has anybody tried to change it to ICS settings using JB drivers? the file is /system/etc/cflashlib.cfg
Tried already. Still not working.
Sent from my ST25i using xda app-developers app

[Q] Locating task_struct::cred

Hi.
I develop an exploit for a public vulnerability. When executing in kernel mode I have to locate task_struct and cred struct and modify user ids. I take pointer to thread_info from stack, then extract pointer to task_struct, search task_struct for process name (comm field). There should be cred struct pointer before the field.
Code:
Code:
int f() //executed in kernel mode
{
unsigned int *p;
unsigned int *p3; //struct task_struct
unsigned int *cred; //struct cred
char *pc1, *pc2;
int i;
register unsigned long sp asm ("sp");
p = sp;
p = (int)p & ~(THREAD_SIZE - 1); //p points to thread_info
initial = p;
p3 = (int *)(p[3]);
task = p3; //p3 points to task_struct
state = task[0];
stack = task[1];
flags = task[3];
pc2 = (char *)p3 + 2056;
pc1 = (char *)p3 + 8;
//Now scan task_struct for comm field
for (; pc1 != pc2;)
{
if (pc1[0] == 'N' && pc1[1] == 'a' && pc1[2] == 'm' && pc1[3] == 'e')
{
pc2 = pc1;
break;
}
pc1++;
}
if (pc1 != pc2)
{
return -2;
}
cred = *(int **)(pc1 - 8); //cred points to struct cred now
...
}
The problem is that assumed cred pointer points to some strange structre. It contains uid but doesn't contain cred's magic and so on. Printing a few dword from cred pointer I see: 7, 7d0, 7d0, 7d0, 7d0, 0, 0. 0x7D0 is uid of the current process. I also dumped the task struct and it looks legit:
Code:
0 //runnable
da32a000 //stack
2 //usage
400000 //flags
0
0
1
1
78
78
78
0
c0808d2c
0
400
400000
1
d99cc3c0
0
d99cc3cc
c4123b84
1
3fb39b63
3f7
895ebf
0
c43e10f3
f2
895ebf
0
0
0
0
c4123708
0
0
d99ce710
d99ce710
0
a
4
0
0
c4123790
0
0
0
f
0
0
d99ce748
d99ce748
0
c0f41344
d99ce3d4
8c
d99ce760
d99ce760
d99ce768
d99ce768
dc585a40
dc585a40
1
3a
28
8
0
0
0
11
0
10000
800000
1
163a //pid
163a //tgid
b9dfb57
d99ce300
d99ce300
d99ce7bc
d99ce7bc
d99ce43c
d99ce43c
d99ce680
d99ce7d0
d99ce7d0
d99ce7d8
d99ce7d8
0
db51ad08
db51ad00
0
db51ad0c
db51ad00
d99ce478
db51af90
db51af80
d99ce804
d99ce804
0
0
0
0
1
0
1
0
0
0
3
11
1108
1a915a67
1108
1a915a67
ac
0
0
0
0
0
0
d99ce868
d99ce868
d99ce870
d99ce870
d99ce878
d99ce878
da456a00 //cred?
da456a00 //cred?
0 //??
65616d4e //'Name'
Any ideas what is this structure and where is cred?
Sorry for posting here, I can't post to development forum.
Thanks.
Ok, I didn't notice that magic is included only when CONFIG_DEBUG_CREDENTIALS is defined. So, there may be no magic.

Keycode_HOME don't work in custom ROM

I have a STB Android with a custom android ROM in which the virtual home key (keycode_HOME) don't work. These are the traces of logcat
03-30 23:37:28.872 D / WindowManager (3694): keycode = 3 interceptKeyTq screenIsOn keyguardActive = true = false = 2000000 policyFlags isWakeKey = false
03-30 23:37:28.872 I / WindowManager (3694): mapkey no map key list
03-30 23:37:28.872 D / WindowManager (3694): interceptKeyTi keyCode = 3 down = false repeatCount = 0 mHomePressed keyguardOn = true = true = false Canceled
03-30 23:37:28.872 W / ContextImpl (3694): Calling a method in the system without a qualified user process: android.app.ContextImpl.sendBroadcast: 1067 com.android.internal.policy.impl.PhoneWindowManager.interceptKeyBeforeDispatching: com.android.server.wm.InputMonitor.interceptKeyBeforeDispatching 1939 352 com.android.server.input.InputManagerService.interceptKeyBeforeDispatching: 1408 dalvik.system.NativeStart.run: -2
I do not have the source code of the kernel.
Any ideas?

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

@ 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!
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
Ricky D said:
FW 17.1.A.2.69
Click to expand...
Click to collapse
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
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.
hasenbein1966 said:
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.
Click to expand...
Click to collapse
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.
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.
These questions aren't really following the OP of this thread, but I'll answer anyway.
tumpin said:
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.
Click to expand...
Click to collapse
Vidd said:
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.
Click to expand...
Click to collapse
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.

Change screen sensitivity

Hi guys,
I really hate that my z2 screen is too sensitive and after searching online for ages I didn't find any solution to it, so I started experimenting myself.
Long story short I managed to find a file under /system/usr/idc/max1187x_touchscreen_0.idc
I opened it as text and it seems to have something to do with the touch screen, but I'm not sure what those things are exactly for. Could anyone please give me some advice on this? Thanks!
The content of the file:
# Device Type
touch.deviceType = touchScreen
# 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 = 580.0
touch.filter.tftype4.NoAccRate = 0.3
# Glove Mode
touch.gloveMode.deflatePressure = 1
pointercontroller.touch1.filename = /system/somc/touch/images/big_touch.png
pointercontroller.touch1.hotSpotX = 310
pointercontroller.touch1.hotSpotY = 310
pointercontroller.touchsplash1.filename = /system/somc/touch/images/splash.png
pointercontroller.touchsplash1.hotSpotX = 40
pointercontroller.touchsplash1.hotSpotY = 40
Sent from my D6503 using XDA Free mobile app

Categories

Resources