The screen sometimes get missplaced

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Get an app running in horizontal mode then wait for the screen to turn off
2.Turn on the screen
3.The screen will be missplaced when viewing in vertical mode.

What is the expected output? What do you see instead?
I expect to see the app well placed in the screen and not missplaced, but it 
applies to all the screen in vertical mode not only the running app.

What version of MiniCM you are using? On what device (x10mini, x8 - x10mini

I'm on MiniCM 2.1.6 on X8
PRO is NOT supported)?

What app(s) are involved in the problem?
ADW Launcher
Android Market

Have you tried rebooting your device?
Yes, and it solved the problem, if didn't reboot it stays the same with the 
missplaced screen.

What is the adb logcat output when the problem accurs (see:
http://wiki.cyanogenmod.com/index.php?title=Logcat)

Please provide any additional information below.

Original issue reported on code.google.com by luis.cor...@gmail.com on 23 Dec 2011 at 3:10

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I'm using nAa-08 Kernel, I'm attaching a screencapture of the issue. And now it 
doesn't fix with restarting the phone once, i need to do it two or three times 
to solve it.

Original comment by luis.cor...@gmail.com on 28 Dec 2011 at 9:41

Attachments:

• screenshot-1325107587949.png

[GoogleCodeExporter]

Why the screenshot is normal if i did it when my device had the screen 
missplaced?

Original comment by luis.cor...@gmail.com on 28 Dec 2011 at 9:44

[GoogleCodeExporter]

I'm attaching a sample of what my screen looked like when the issue happens.

Original comment by luis.cor...@gmail.com on 28 Dec 2011 at 9:46

Attachments:

• screenshot-1325107587949-tweaked.png

[GoogleCodeExporter]

And if don't reboot my device it stays that way. Please help me. I have latest 
baseband and unlocked bootloader, I have followed all the steps in XDA. But 
with the new kernel the issue doesn't happens too often as before.

Original comment by luis.cor...@gmail.com on 28 Dec 2011 at 9:48

[GoogleCodeExporter]

I experience the same problem, see attached screenshots. SE Xperia X8 running 
MiniCM7-2.1.6, unlocked bootloader, nAa-08 kernel. If any additional platform 
info is required, please let me know.

Original comment by kriszti...@gmail.com on 2 Jan 2012 at 10:18

Attachments:

• droidbug2.jpg
• droidbug1.jpg

[GoogleCodeExporter]

Based in my experience, it's an Overclocking issue maybe, when I'm on stock 
speed I got the screen issue just 1 time with performance governor. Now i'm on 
nAa08b kernel with smartass v2 governor with stock speed and so far no screen 
issues. But when I enabled OC with smartass v2 governor I got the screen issue 
after turning off and on the screen 2 times.

Original comment by luis.cor...@gmail.com on 3 Jan 2012 at 10:51

[GoogleCodeExporter]

I also use Smartass v2 governor (kernel version 2.6.29.6-nAa-08). I read in 
some forums that increasing the minimum CPU frequency possibly solves the 
issue, so I set it to 245 MHz from the default 122 MHz to see if it helps (the 
maximum is currently set to 691 MHz).

The screen still gets misplaced sometimes, but it seems it is a bit more 
infrequent... but it's still happening randomly. Sometimes I do not experience 
the problem for a day, other times I have to reboot my device several times a 
day.

I feel I should add that I did NOT overclocked my phone when the issue started 
happening (in fact, I started poking the governor and frequency settings 
because of it), so I doubt turning OC off will solve this, but I will try your 
suggestion (i.e., setting default frequencies with Smartass v2 governor) and 
post my experiences.

Original comment by kriszti...@gmail.com on 5 Jan 2012 at 2:53

[GoogleCodeExporter]

I have tested with stock speed and smartass v2, for 2 days now and I have not 
had any screen cut. So I assume it's an OC issue.

Original comment by luis.cor...@gmail.com on 5 Jan 2012 at 10:33

[GoogleCodeExporter]

I also tested with default clock speed and smartass v2 governor, I've seen the 
issue only once (this morning) in two weeks. When I overclocked, it happened 
daily, so I as well suspect an OC-related cause.

Original comment by kriszti...@gmail.com on 21 Jan 2012 at 1:55

[GoogleCodeExporter]

The bug was in nobodyAtall's kernel v8: upgraded to nAa-11, no problems ever 
since. I think it was fixed in nAa-09, but I skipped that (upgraded to 11 from 
8). This thread can be closed I guess.

Original comment by kriszti...@gmail.com on 7 Mar 2012 at 2:41

[GoogleCodeExporter]

I'm experiencing that issue too on my phone. I'm on smartass V2 and OC to 690 
and before that the screen was normal. kernel nAa 11, mini 2.2.0, unlocked 
bootloader.

Original comment by Ira.BA...@gmail.com on 29 Apr 2012 at 9:27

[GoogleCodeExporter]

I have the same problem with the last version 2.2.1. 

Original comment by nuno.gom...@gmail.com on 13 Jun 2012 at 1:51

[GoogleCodeExporter]

Any news about this problem???

Original comment by nuno.gom...@gmail.com on 21 Jun 2012 at 10:15

[GoogleCodeExporter]

now with kernel 2.6.32.61-nAa-jb-06 and rom MiniCM10 4.1.0 still having the 
same situation.. No overclocked.. I hope someday idk if somebody can bring the 
solution to this really annoying issue.. this is how it looks... thank u

Original comment by carlosar...@gmail.com on 26 Oct 2013 at 11:14

Attachments:

• CameraZOOM-20131026160907030.jpg
• CameraZOOM-20131026160529077.jpg
• CameraZOOM-20131026161049155.jpg
• CameraZOOM-20131026161713528.jpg