Join now - be part of our community!

Unable to swipe down after update

Sixstrings
Visitor

Unable to swipe down after update

Hi,

Last saturday had an update (23.4.A.1.232 I believe) and after that the top 3 to 4 milimeters do not respond to touch, so I'm unable to swipe down quick settings and all other options.

Not being able to swipe down is very limiting and frustating!

21 REPLIES 21
bhunachicken
Visitor

I'm expereiencing something weird lately: the bottom portion of my Z3C's screen responds oddly to touches.

If I tap the bottom 1/8th or so of the screen, two touches are registered. However, these two touches will appear a short way above and below the area. These two touches will always appear EXACTLY in the same places, as if they are being redirected to a rectangle.

Sliding your finger across the affected area will produce two perfectly horizontal lines. I can reproduce this 100% every time. Oddly, this doesn't affect the very left of the screen - it's like a rectangular area that is shunted to the right.

The over all problem this causes is that if I try and do something like press the space key on a keyboard, both the space bar AND a letter on the lower part of the keyboard is pressed. Also, when gliding over Google keyboard, I notice that the trail vanishes when I move over the rectangular area.

Anyone else expereinced this? Running a D5833, with buid 23.4.A.200 (most recent release). I'm thinking that this might be due to the recent firmware release, since I only just noticed it after updating.

xavinux
Enthusiast

Hi @bhunachicken

Please, try from your Home screen:

1. Tap the Application screen icon.
2. Find and tap Settings -> Apps.
3. Swipe to the All tab.
4. Find and tap on Xperia Home.
5. Tap Force stop -> Clear data.
6. Restart the phone.

This will reset home screen to default settings (widgets, shortcuts). Check if this issue persists.

bhunachicken
Visitor

Thanks for the suggestion, but after doing so the problem persists.

xavinux
Enthusiast

Hi @bhunachicken

Well, I suggest you in this case, to first run a backup of the device information like this:

http://talk.sonymobile.com/t5/FAQ/Backup-amp-Transfer/m-p/407253#U407253

Try performing a system repair using PC Companion or Bridge for MAC.

The process will erase all internal memory.You might need to charge your device for about 1-2 hours before so the device has at least 80% battery. Switch off your phone and unplug from Pc (Hold volume up and power for around 10 seconds). Start PC Companion and select Support zone then Update my phone/tablet then in Blue Repair my phone/tablet and follow the on screen instructions - When prompted connect your phone still switched off holding volume down or back button - This should start the repair or reformat process If you are using Windows 8/8.1 or a 64bit operating system then adjust the settings for PC Companion and run in compatibility mode and chose Windows 7 or XP.

Umutq
Visitor

Yes I have this problem after the update.
bhunachicken
Visitor

Using the PC companion update did not fix this issue for me.

I'm still not sure if this is hardware or software related.

If hardware, this is disappointing, as first ever Xperia and it's only 3 months old. If software, I'm wondering how I can downgrade to before 23.4.A.1.200 to test.

bhunachicken
Visitor

Umutq - are the symptons you're suffer similar to mine (i.e. - the bottom of the touch screen is detecting two horizontal touches, instead of the usual one)?

What model are you using? I'm on the D5833 here.

xavinux
Enthusiast

Hi @bhunachicken

Please, try to boot your device into safe mode as explained here and check if the problem also persists. f this issue is not present in this mode, that indicates a third party app is causing the problem. In this case exit Safe Mode and then un-install any third party apps you don't need and clear the cache/data for the apps you want to keep.I´m at disposal for any question.

bhunachicken
Visitor

Clearing Dalvik Cache: didn't fix.

Safe Mode: didn't fix.

PC Companion repair: didn't fix.

Hardware problem? I swear this happened after the update to 23.4.A.1.200, though.