search

yucemahmut / android-on-freerunner

Automatically exported from code.google.com/p/android-on-freerunner
0 stars 0 forks source link

Screen output sporadically becomes garbled #148

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?

Sporadic issue, seems to occur mostly when there are heavy screen updates: In 
one case I started Clocksync 
(http://andappstore.com/AndroidApplications/apps/729006) and left it running 
overnight (phone plugged in and configured to stay awake). In the other I had 
automatic screen orientation activated, the phone was in a car cradle and I was 
driving down a bad road; jitter from the accelerometer caused the screen to 
rotate back and forth (see also issue 140). The issue occurred in both cases, 
plus in some more, of which I do not remember the exact details.

What is the expected output? What do you see instead?

Expected output is a normal Android screen. Instead I see garbled output, the 
ratio of pixel colors roughly matches (the blue background of Clocksync remains 
somewhat visible, when using OSMtracker I get a pattern of black and various 
shades of gray). The phone seems irresponsive (in fact I cannot tell if it 
still reacts to screen/button events as the screen is illegible); pressing and 
holding POWER will turn it off. After that it reboots normally.

What version of the product are you using? On what operating system?

Cupcake 0.2.0 RC1

Please provide any additional information below.

The issue may be related to frequent screen updates: in the Clocksync case, the 
screen was displaying two large clocks (hh:mm:ss) and updating them every 
second. In the other case, the application was OSMtracker (with a fairly static 
screen) but the jitter coming from the accelerometer caused permanent screen 
rotation in different directions.

For this reason my first suspicion would be a fault in the graphics driver.

Original issue reported on code.google.com by mich...@vonglasow.com on 27 Jul 2010 at 4:55

GoogleCodeExporter commented 9 years ago 
had similar behavior again the other day, still on Cupcake 0.2.0 RC1. This time 
the screen output was only slightly garbled but the picture was still mostly 
visible and fonts somewhat legible.

The screen saver read "No service" - apparently the GSM signal got lost.

The phone would still respond to key presses (holding Power would bring up the 
menu for sound, airplane mode or shutdown) but touchscreen input got difficult. 
If I remember correctly, it would still react but since the image was somewhat 
shifted input would get misinterpreted. I ended up shutting the phone down with 
a long press of the Power button.

This time I did not use any extensive graphics, the phone was plugged in and 
lying on my bedside locker - that after a 500 km drive over 3 country borders, 
(and thus at least 3 network switchovers, maybe more as I had crossed the Alps) 
starting in its home network.

Conclusion: Looks like the problem is somewhere in the kernel, maybe in more 
places, and apparently hampers with the functioning of more than one device 
driver. It looks a lot like some data structure gets corrupted.

Original comment by mich...@vonglasow.com on 23 Aug 2010 at 8:27