search

Raconeisteron / omnia2droid

Automatically exported from code.google.com/p/omnia2droid
0 stars 0 forks source link

sleep: Lines onscreen when lock/unlock screen #4

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. do something on the phone after that press the lock button
2. wait a sec, unlock the phone -> Lines across screen / No lines
3. do it again, if no lines

What is the expected output? What do you see instead?
well unlock the screen and use normal touch input, but it does not respond at 
all when the lines are in screen

What version of the product are you using? On what operating system?
Latest beta 1024ROM

Please provide any additional information below.

Original issue reported on code.google.com by jjrt1...@gmail.com on 19 Jan 2011 at 12:26

GoogleCodeExporter commented 8 years ago 
Confirmed. The bug is caused by the lack of working 2D/3D drivers. Check 
http://www.modaco.com/content/i8000-omnia-ii-gsm-rom-discussion/322429/android-o
n-omnia-ii-i8000/ for more info and a fix.
Make sure you have installed the latest version of the beta from 
http://o2droid.phj.hu/index_en.php or you won't be able to apply the fix.

Original comment by nathrin...@gmail.com on 19 Jan 2011 at 5:34

GoogleCodeExporter commented 8 years ago 
After fix is applied, seems to be a lot better. However, still got it once. 
Doesn't seem to prevent any input though. Reopening.

Original comment by nathrin...@gmail.com on 19 Jan 2011 at 5:50

GoogleCodeExporter commented 8 years ago 
yes it seems a bit better with the patch, ( i used the patch before i created 
this ticket )  but still got some freezes / lines across te screen ( also using 
the new zImage )

Original comment by jjrt1...@gmail.com on 19 Jan 2011 at 6:15

GoogleCodeExporter commented 8 years ago 
why is priority low ? this bug prevents android from running more stable on 
omnia II more like major ?

Original comment by jjrt1...@gmail.com on 19 Jan 2011 at 6:18

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Reverting it back.
We'll see how the devs wan't to handle it.

Original comment by nathrin...@gmail.com on 19 Jan 2011 at 6:27

GoogleCodeExporter commented 8 years ago 
Using latest zImage and without 2d/3d drivers an oops systematically came when 
the interface freeze (didn't happened anymore since installed the 2d/3d 
drivers).
ADB stays up since I disabled the panic on oops.
Log attached.

Original comment by BeamRi...@gmail.com on 19 Jan 2011 at 11:06

Attachments:

GoogleCodeExporter commented 8 years ago

Original comment by elbee1...@gmail.com on 20 Jan 2011 at 8:12

GoogleCodeExporter commented 8 years ago 
I'm aware of this bug. We have to change some timings in the display drivers. I 
have already done this partially but not moved to the main kernel.

Original comment by Marcvanh...@gmail.com on 20 Jan 2011 at 1:25