[Xperia Play Android Development] Spizzy01:
To get the dmesg the manual way I had to boot into recovery and do

adb shell
dmesg > /sdcard/dmesg.txt
exit
adb pull /sdcard/dmesg.txt

Just in case anyone else needs it in the future.

Edit: Hmm.. We don't by any chance have an issue with the voltages do we? I've checked the driver and it doesn't look like it just 'kills' itself once it finds out that the firmware is wrong..

I have however checked dmesg to see the following lines:

<3>[ 3.316101] ldo10: requested voltage range [2600000, 2600000] does not fit within previously voted range: [2850000, 2850000]
<3>[ 3.327484] Failed to set voltage for gp4: -22
<3>[ 3.331909] snddev_hsed_voltage_init: could not set regulator voltages: -22

At the end of the day though, something doesn't have the right voltage set... Whether it's the touchscreen or something else. +1 for something else to look into. ><

As for the touch...

<7>[ 4.777404] CY8CTMA300_TOUCH: V0.9b-mt built Mar 4 2014 16:59:28
<7>[ 4.777832] CY8CTMA300_TOUCH: SPI setup (requesting 1000000Hz) OK
<6>[ 4.835418] Charging with 0mA current
<6>[ 4.835601] entering into lpm
<6>[ 4.835815] msm_otg_suspend: Turn on phy comparators
<6>[ 4.836029] msm_otg_suspend: usb in low power mode
<6>[ 4.945831] CY8CTMA300_TOUCH: TP_REG_FW 0x00
<6>[ 5.105834] CY8CTMA300_TOUCH: Bootloader FW Ver 0.0
<6>[ 5.125823] CY8CTMA300_TOUCH: Application FW Ver 0.0
<6>[ 5.145874] CY8CTMA300_TOUCH: Silicon Revision E
<6>[ 5.165863] CY8CTMA300_TOUCH: Customer ID 0
<6>[ 5.185882] CY8CTMA300_TOUCH: old FW version, reset workarounds DISABLED.
<6>[ 7.486297] CY8CTMA300_TOUCH: TP_REG_FW 0x00
<6>[ 7.646301] CY8CTMA300_TOUCH: Bootloader FW Ver 0.0
<6>[ 7.665954] CY8CTMA300_TOUCH: Application FW Ver 0.0
<6>[ 7.685943] CY8CTMA300_TOUCH: Silicon Revision E
<6>[ 7.705932] CY8CTMA300_TOUCH: Customer ID 0
<6>[ 7.725952] CY8CTMA300_TOUCH: old FW version, reset workarounds DISABLED.
<6>[ 7.866546] input: cy8ctma300_touch as /devices/platform/spi_qsd.0/spi_master/spi0/spi0.0/input/input5
<6>[ 7.885559] CY8CTMA300_TOUCH: Device registered OK

Apparently instead of 'disabling' it.. I made it simply reset? ...:confused:

Although... It's not straight away now that we get the 'Invalid data' errors... Which is perhaps why I could get the touchscreen to last a bit longer than normal...

<6>[ 9.467926] CY8CTMA300_TOUCH: invalid data?
<6>[ 9.910156] CY8CTMA300_TOUCH: invalid data?
<6>[ 10.352508] CY8CTMA300_TOUCH: invalid data?
<6>[ 10.794921] CY8CTMA300_TOUCH: invalid data?

Right... I've completely stopped the driver from even thinking the firmware could be bad. Or 's**t_firmware' as the driver calls it...

<6>[ 4.702270] input: synaptics_touchpad as /devices/virtual/input/input4
<6>[ 4.702606] synaptics_touchpad 4-0020: synaptics_touchpad_set_power: powered 1, activated 0, users 0, standby 0
<7>[ 4.703155] CY8CTMA300_TOUCH: V0.9b-mt built Mar 4 2014 20:44:56
<7>[ 4.703552] CY8CTMA300_TOUCH: SPI setup (requesting 1000000Hz) OK
<6>[ 4.761444] Charging with 0mA current
<6>[ 4.761627] entering into lpm
<6>[ 4.761840] msm_otg_suspend: Turn on phy comparators
<6>[ 4.762054] msm_otg_suspend: usb in low power mode
<6>[ 4.871856] CY8CTMA300_TOUCH: TP_REG_FW 0x00
<6>[ 5.031890] CY8CTMA300_TOUCH: Bootloader FW Ver 0.0
<6>[ 5.051879] CY8CTMA300_TOUCH: Application FW Ver 0.0
<6>[ 5.071868] CY8CTMA300_TOUCH: Silicon Revision E
<6>[ 5.091857] CY8CTMA300_TOUCH: Customer ID 0
<6>[ 5.252136] input: cy8ctma300_touch as /devices/platform/spi_qsd.0/spi_master/spi0/spi0.0/input/input5
<6>[ 5.254211] CY8CTMA300_TOUCH: invalid data?
<6>[ 5.271514] CY8CTMA300_TOUCH: Device registered OK
<6>[ 5.272399] input: gp2ap002a00f as /devices/virtual/input/input6
<6>[ 5.273284] GPIO Input Driver: Start gpio inputs for gpio-slider in interrupt mode
<6>[ 5.273773] input: gpio-slider as /devices/virtual/input/input7
<6>[ 5.274932] GPIO Input Driver: Start gpio inputs for gpio-keypad in interrupt mode
<6>[ 5.275482] input: gpio-keypad as /devices/virtual/input/input8

However, we still get the 'invalid data' error...

I think we may be looking in the wrong direction. What about the possibility that the device thinks the screen is off or in standby? Due to the failure of another device? Or perhaps the proximity sensor is partly working and is disabling the touchscreen but not the display itself?

I just don't understand how it can work for a split second and not work after... Unless we need to be checking the logcat as well... - I'll give it a try!

Edit: So far cant get a logcat - since Android doesn't work properly it cant connect via ADB/cant activate USB Debugging...