Froyo lockscreen freeze

[Guest lixcab]

Froze again this morning, again just after getting off tube (so the phone was possibly reclaiming network.) I installed No Lock and activated pattern lock so I don't start making calls when phone is in my pocket. Fingers crossed.

Running Paul Alpha 4.

Edit: Uninstalled No Lock and just left pattern lock

Edited December 31, 2010 by lixcab

[Guest Storm3y]

I'm getting this also,

Any fix for it yet?

[Guest hicks]

Argos just swapped mine without argument. The cashier said they'd had a few back with similar problems, but then they tend to say that anyway :>

We'll see how this one goes.

[Guest Rab_UK]

My phone started doing this the other day.. definitely a hardware problem for me.. If I held the phone at the top and the bottom and

gave it a bit of "flex" the screen would work.

Took it back to Argos who exchanged with no fuss.. Hopefully this one will be ok.

[Guest mau34]

just wondering whr Argos at wiv their return policy coz Argos clearly stated that on mobile phones they do not hv their 30 days return policy so how did u guys manage to get an exchange??

[Guest Pully]

The 30day exchange policy is for returning unwanted items faulty goods can still be returned.

[Guest reallordx]

I was just reading through this thread an hour ago and NOW i got a screen freeze. (MCR 2.2 A3.)

Adb is stuck on "waiting for device". as i dont need the phone now, ill just leave it this way, till someone tells me what i need to do (or till i really need the phone).

Do I need something else for adb to work? Do i need the connect command? I usually use adb wireless, which i can't with a frozen screen.

Assuming i need to properly connect, how do i figure out my ip:port? I'm on 3G momentarily, to figure out wireless ip would have been easy...

EDIT:

Ignore above, logcat attached now.

had wrong (i.e. no) drivers, thanks to ACodwill on irc i got a logcat now. Maybe it'll be useful to someone.

btw:

Do we have some sort of irc chan? that would be really handy just now, assuming there's someone logged on who could help me.

Found the chan: #zteblade on freenode, but seems like there's no one just now. :/

log20110102.txt

Edited January 2, 2011 by reallordx

[Guest mau34]

so if I got a faulty phone how many days have I got to return the faulty phone BK to Argos?

[Guest fiendishlyclever]

just wondering whr Argos at wiv their return policy coz Argos clearly stated that on mobile phones they do not hv their 30 days return policy so how did u guys manage to get an exchange??

That doesn't apply when goods are faulty.

Speaking of faulty it would appear your keyboard is playing up - some of your vowels are missing! :unsure:

[Guest fiendishlyclever]

3 screen lockups today - two in my pocket and one at home (so can't be pressure from pocket etc).

I've admitted defeat - glad my HTC desire arrives next week, sold my SF on Ebay so won't be a problem much longer!

[Guest Simon O]

Reports of the screen freeze happening on Eclair too.

Sadly it's looking like a hardware issue. I wonder if the TFT phones get this?

[Guest fiendishlyclever]

Reports of the screen freeze happening on Eclair too.

Sadly it's looking like a hardware issue. I wonder if the TFT phones get this?

Mine is a TFT screen - it would appear they do!

[Guest lljkpugna]

My girlfriend's SF and mine both had the 'touch stops responding' problem the other day, running Paul's a4 Froyo. Hers is TFT, mine is OLED. Neither phones had done it before before, then they both did within minutes of each other. Peculiar. Hasn't happened since either.

[Guest lixcab]

3 screen lockups today - two in my pocket and one at home (so can't be pressure from pocket etc).

I've admitted defeat - glad my HTC desire arrives next week, sold my SF on Ebay so won't be a problem much longer!

^Envy.

Have fun with the Desire.

[Guest NightSt@lk3r]

I have only had 1 lockscreen freeze in the 3 weeks i have had this phone.

[Guest Maringer]

Had my OLED SF for a couple of months, only running Eclair ROMs and not a single freeze to report as yet. My sister has had a TFT SF for about a month with no freezes that I'm aware of. My girlfriend has had one a couple of weeks, no freezes yet.

It seems strange that reports of Eclair freezes are only just appearing whereas the Froyo problem has been around for some time.

[Guest bzzzzt]

had my first lockscreen freeze today. running jellyfish 3b without the overclock-patch. i really hope this doesnt turn out to be a hardware failure. i got mine from ebay and there are no OLED's left. (i hope the guy on ebay didnt sell it because of those issues)

Edited January 2, 2011 by bzzzzt

[Guest socialworker]

Reports of the screen freeze happening on Eclair too.

Sadly it's looking like a hardware issue. I wonder if the TFT phones get this?

Might be a hardware issue for the couple of guys experiencing it with 2.1.

Definitely ISN'T a hardware issue for the hundreds of ppl getting it STRICTLY with 2.2.

2.1 = working perfectly for weeks, NEVER EVER had a freeze

2.2 = freezing every now and then

[Guest mieleton]

I have a Blade with TFT screen and 5MP camera, and it seems that the current 2.2 roms are almost useless for me. If the phone is connected with USB to a computer, there's no problems. After disconnecting the USB cable and waiting for the screen to turn off, there's no way to get touch input back without taking the battery out or using adb reboot.

On the other hand, every 2.1 rom I've tried works perfectly, no "touch input freezes".

[Guest wbaw]

Reports of the screen freeze happening on Eclair too.

Sadly it's looking like a hardware issue. I wonder if the TFT phones get this?

Yes they do. The touch screen totally died on my first one in less than 10 days, that was tft. Flashing the stock orange 2.1 rom made no difference, the screen was still dead. I had to take it back & exchange it for a new phone. I've had my new one a week so far, it hasn't frozen at all yet & it's running the same rom (modaco froyo alpha 3). I think some phones are better than others, but it's just pot luck if you get a faulty one or not & how faulty it is.

It isn't unique to the blade either, I've seen reports of similar problems on different phones with capacitive touch screens, I saw a long thread on a google board about the same problem on the nexus one. Apparently the manufacturing tolerances have to be very tight, any slight manufacturing defects can cause problems with capacitive touch screens, they often don't cause problems until after a few days of use too, so they slip through quality control.

Edited January 3, 2011 by wbaw

[Guest gambieter]

Yes they do. The touch screen totally died on my first one in less than 10 days, that was tft. Flashing the stock orange 2.1 rom made no difference, the screen was still dead. I had to take it back & exchange it for a new phone. I've had my new one a week so far, it hasn't frozen at all yet & it's running the same rom (modaco froyo alpha 3). I think some phones are better than others, but it's just pot luck if you get a faulty one or not & how faulty it is.

Same here (white TFT, Froyo or different Eclair versions), but the Portugal trick in the Youtube video works. If I leave the right top corner loose (seen from screen side), no problem, click it in and bang, touchscreen freeze. The Z-device test is all fine, if I go into ClockWorkMod recovery, fine. I did fasten the screws inside earlier. So testing continues...

[Guest spirit222]

Same thing with my Blade with similar specs. Unless someone with Finnish Blade 512 ram 5mp camera proofs something else I would nearly suggest this as a "known issue". Same thing with all froyo roms. Instant freeze when first time entering Lock Screen. Widget Locker seemed to help, but only for a few times before the problem came back.

Edit: Checking now Japanese Jellyfish RLS1. See if it works.

I can confirm this. I have saunalahti blade with 5mpix camera. I haven't got a single freeze with 2.1 roms. But every 2.2 rom i tried freezes when lockscreen comes on. So it's not hardware problem with saunalahti blades. I have now finnish fillyjonk rls4 in my blade and no freezes.

[Guest Jet-Ace]

I have a Blade with TFT screen and 5MP camera, and it seems that the current 2.2 roms are almost useless for me. If the phone is connected with USB to a computer, there's no problems. After disconnecting the USB cable and waiting for the screen to turn off, there's no way to get touch input back without taking the battery out or using adb reboot.

On the other hand, every 2.1 rom I've tried works perfectly, no "touch input freezes".

Same here with the same phone. I would like to add that instead of computer connection charging serves the same thing. The key issue is that if the screen goes to sleep it freezes. By using a program that can set screen timeout to "never" there are no freezes but of course this is not an option for more than a brief testing. No matter which froyo you test the result is always the same. No lock-programs are totally useless.

There has been a couple of (1 or 2 persons with 512 MB / 5MP) saying that they have no problems, but I think they either have a 3.2MP or they have applications that won't let the screen go to sleep in reality. If there is someone with 512 MB / 5MP really would like to see list of installed programs.

I think all persons making these froyo roms have 256 MB / 3.2MP phones?

[Guest mieleton]

Same here with the same phone. I would like to add that instead of computer connection charging serves the same thing. The key issue is that if the screen goes to sleep it freezes. By using a program that can set screen timeout to "never" there are no freezes but of course this is not an option for more than a brief testing. No matter which froyo you test the result is always the same. No lock-programs are totally useless.

There has been a couple of (1 or 2 persons with 512 MB / 5MP) saying that they have no problems, but I think they either have a 3.2MP or they have applications that won't let the screen go to sleep in reality. If there is someone with 512 MB / 5MP really would like to see list of installed programs.

I think all persons making these froyo roms have 256 MB / 3.2MP phones?

Yup, I can confirm that just having the charger connected makes a difference - no freezes. Considering that the 5MP camera versus 3.2MP is a hardware difference, the logical conclusion would be that there's some other hardware differences as well. And those differences don't play well with the chinese beta kernel that all the 2.2 roms are using.

I may be wrong, but weren't the very first Blades sold by Saunalahti OLED models? It would be interesting to know whether the freezing problem occurs with them.

[Guest _mika]

Same here with the same phone. I would like to add that instead of computer connection charging serves the same thing. The key issue is that if the screen goes to sleep it freezes. By using a program that can set screen timeout to "never" there are no freezes but of course this is not an option for more than a brief testing. No matter which froyo you test the result is always the same. No lock-programs are totally useless.

There has been a couple of (1 or 2 persons with 512 MB / 5MP) saying that they have no problems, but I think they either have a 3.2MP or they have applications that won't let the screen go to sleep in reality. If there is someone with 512 MB / 5MP really would like to see list of installed programs.

I think all persons making these froyo roms have 256 MB / 3.2MP phones?

+1. The ones with 512MB/5MP w/o problems either have installed some software to prevent real sleep or this is just some weird Wi-Fi problem and their WiFi settings prevent the sleep.

If the phones really are the same inside this would only make sense if the error comes in the installation part.

People use different ways to root their phones, different clockwork versions and so on...

But the most probably this is caused by incompatible kernel we're using...

What I think is happening is that the freezes seem too random (the screen won't freeze EVERY time) so there must be something else that triggers it.

The kernel suspends resources during sleep and fails to bring them back on if some background process happened like sms/mail received, weather update, etc...