Screen not responding [answered]

asked 2014-09-11 15:39:00 +0200

Kayakist
861 ●16 ●18 ●23

updated 2014-10-21 15:39:55 +0200

This morning I was writing a message on the phone, when the screen started to respond erratically to my typing, and then stopped altogether. The phone was connected to the charger, so at first I thought it was overheating. So: unplugged the phone, took out the battery and left the phone alone for about 15 minutes. A restart after a thorough screen cleaning seemed to work, or at least got me past the PIN code entry and onto the lock screen, from where I was able to check my notifications once, before returning back to square one: a phone that responds to the power button and volume rocker, but not to screen commands.

The search came up with nothing similar, so I suspect I'm (among) the first to experience this?

Update: After a couple of hours of just lying around, the phone screen responded to a couple of commands, but then stopped working again...

Update 2: After being in touch with Jolla Care, and being asked some more details about the phone (disk usage etc.), they gave me three options to get a factory reset done: Send it to be flashed, bring it to their office in my home town for the same, or do it myself. So I reset the device at home, and after updating it back to U8 it has worked normally again.

So now we have a solution to the problem, but no apparent cause for it, so I'll close the question (but leave it to be re- opened if further information comes to light).

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by Kayakist
close date 2014-10-21 15:40:11.261645

Comments

I am experiencing this problem or something related at the moment. I had it in the past as well, but I am not sure how it was resolved. What is odd is that swipes from the edge of the screen work fine and I can start apps. But in the app itself there is no touch response. This is true for both Android as well as native apps.

Hhmm, after a reboot it works again.... but it might stop working as I had rebooted today once already and this is my second attempt to solve the issue. This is on update 11 btw, and I got plenty of space left, only 7.3GB used out of 14GB.

avdwoude ( 2015-03-06 12:50:29 +0200 )edit

Hello @Kayakist,

thanks for your input.

I have opened as well a thread about this with a workarround. Please have a look under the following link and if you do have more information on your topic would it be great if you could add it there.

https://together.jolla.com/question/132334/bug-sfos-2017-unlocking-the-phone-via-display-input-does-not-work-after-a-while-when-the-phone-was-locked/

Thank you.

Greetings, megalith

megalith ( 2016-04-24 13:54:31 +0200 )edit

0

answered 2014-09-11 17:32:11 +0200

till

1011 ●10 ●17 ●22

might be this problem: https://together.jolla.com/question/30822/root-and-home-disks-full-and-causing-various-problems/

edit flag offensive delete publish link

Comments

1

Possible, but I doubt it: after the last OS update I haven't had ANY of those 8 symptoms listed in the question you linked to, and I have more than ample space left on the internal storage (4,8 GB used, or at least that's what the phone tells me). I think the issue could maybe link to some type of overheating in the connections to/ from the display, as the phone went back to functioning normally after not being used for a couple of hours...?

Kayakist ( 2014-09-11 17:58:44 +0200 )edit

it may make sense to try the "How to evaluate the situation" section, because not the free space shown by the device info is important but the space used for metadata

till ( 2014-09-11 18:38:17 +0200 )edit

I had a similar issue. I thought it was the quickbar causing the problem. But I am.not sure. Did you run it?

TK ( 2014-09-11 19:24:39 +0200 )edit

@till I haven't tried to follow the evaluation steps in the instructions for two reasons: I had to go out for a while, and so wasn't able to, and I'm not that comfortable with activating developer mode and going through the steps, for I would be just following instructions without really understanding what I'm doing at every step. On the other hand, I doubt I could make the situation worse by following the instructions letter for letter :) @TK I haven't Quickbar at all...

Kayakist ( 2014-09-11 20:50:59 +0200 )edit

0

answered 2014-09-11 20:21:15 +0200

pycage
2325 ●27 ●36 ●49

This sounds exactly like what I had with my T-Mobile G1 a few years ago. I returned the device and got a replacement as it probably was a broken touch screen.

However, if this behavior is shown with the charger connected only, I wouldn't worry too much. Interferences with the touch screen are quite common (I haven't seen this on the Jolla, but on the N9 it was extreme). Maybe using another charger helps a bit.

edit flag offensive delete publish link

Comments

The problem started while the device was connected to a charger, but later the same thing happened while being used without charger connection. After about three hours of just sitting on my desk without a SIM card, but powered up, I got it to work for about 20 min first just connected to WiFi, and then after re- inserting the SIM it stopped working after another 15- 20 minutes of continuous use.

Kayakist ( 2014-09-11 20:34:30 +0200 )edit

Screen not responding [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by Kayakist
close date 2014-10-21 15:40:11.261645

Comments

2 Answers

Comments

Comments

Question tools

Stats

Related questions

Screen not responding [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by Kayakist close date 2014-10-21 15:40:11.261645

Comments

2 Answers

Comments

Comments

Question tools

Public thread

Stats

Related questions

The question has been closed for the following reason "the question is answered, an answer was accepted" by Kayakist
close date 2014-10-21 15:40:11.261645