Jump to content

Welcome to CyanogenMod

Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
  • Start new topics and reply to others
  • Subscribe to topics and forums to get automatic updates
  • Get your own profile and make new friends
  • Download files attached to the forum.
  • Customize your experience here
  • Share your CyanogenMod experience!
Guest Message by DevFuse
 

[Solved] 6.1RC2: Left quarter of screen scrolling slower


This topic has been archived. This means that you cannot reply to this topic.
37 replies to this topic

#1 H4wk_cz

H4wk_cz
  • Members
  • 7 posts

Posted 28 November 2010 - 12:57 AM

Hi, I upgraded to 6.1RC2 from 6.1RC1. I didn't wipe anything. I have a problem with screen animations. The left quarter of the screen seems to scroll slowly than the rest of the screen. For example in the User interface config menu in Cyanogenmod settings, when I am scrolling down, there is an invisible vertical delimiter before "ees" in "90 degrees", everything on the left side is scrolling slowly than the rest. When I am scrolling down, the right part of the screen is a few pixels under the left part. When I am scrolling up, it's few pixels above. I thought the problem could be with overscrolling, but it doesn't matter if it's on or off.
Does anyone else have the same problem? Do you have any idea what could be behind this weird behaviour?

EDIT: SOLVED in nightly build 201.

Edited by H4wk_cz, 02 December 2010 - 09:59 AM.


#2 kingryu1

kingryu1
  • Members
  • 2 posts

Posted 28 November 2010 - 01:07 AM

This is an issue I am also having if I understand what you are saying correctly.
On my Desire the left hand (when held portrait) seems to be out of sync with the rest of the display.
It is particularly evident when scrolling the notification bar or playing any kind of games (ruling out the fact that it is a launcher issue). I have wiped dalvik and cache and installed the latest GApps whilst upgrading.
Any ideas guys?

#3 last czarnian

last czarnian
  • Members
  • 202 posts

Posted 28 November 2010 - 01:22 AM

this is relevant to my interests - sounds like what Hippytyre and myself were talking about in the nightlies.

As to what's causing it, I haven't a scooby..

#4 yenemy

yenemy
  • Members
  • 30 posts

Posted 28 November 2010 - 02:20 AM

I was seeing this in RC1 as well, which is why I'm currently still on 6.0.2. I had assumed it was a problem in the kernel I had to flash to accommodate my more recent phone version.

#5 qoonik

qoonik
  • Members
  • 1 posts

Posted 28 November 2010 - 10:42 AM

I have the same problem.

Model number:     HTC desire
Android version:  2.2.1
Baseband version: 32.48.00.32U_5.11.05.14
Kernel version:   2.6.35.8-cyanogenmod
Mod version:      CyanogenMod-6.1.0-RC2-Desire
Build number:     FRG83


#6 Rosco

Rosco
  • Members
  • 4 posts

Posted 28 November 2010 - 11:49 AM

From what I can tell, seems like its affecting the SLCD screens. Nightly builds past 192 and the new RC2 all have this. Do you all have SLCD screens?

#7 last czarnian

last czarnian
  • Members
  • 202 posts

Posted 28 November 2010 - 11:53 AM

Hey Rosco, I can confirm I'm on an SLCD screen.

#8 H4wk_cz

H4wk_cz
  • Members
  • 7 posts

Posted 28 November 2010 - 12:14 PM

Me too.

Sent from my HTC Desire using Tapatalk

#9 ahunor

ahunor
  • Donators
  • 31 posts

Posted 28 November 2010 - 12:32 PM

Yep, same here.
EDIT: Amoled screen.

Edited by ahunor, 28 November 2010 - 12:46 PM.


#10 Glotzeulor

Glotzeulor
  • Donators
  • 185 posts

Posted 28 November 2010 - 12:36 PM

I have never experienced this issue. Amoled screen, if it does matter.

#11 grimezyd

grimezyd
  • Members
  • 16 posts

Posted 28 November 2010 - 01:02 PM

Is this issue being worked on, I have gsm s off slcd with same problem, also I see this problem is in the nightlies I have never been able to run a nightly on my three month old desire with s on or s off it just constantly reboots I'm not a total noob as I had a g1 since launch and had stock 1.1then jesusfreke 1.5 then cyanogen mod for about 18 months or more, I have missed using nightly builds and would like to know what would cause this behavior on my phone

#12 last czarnian

last czarnian
  • Members
  • 202 posts

Posted 28 November 2010 - 02:35 PM

View Postahunor, on 28 November 2010 - 12:32 PM, said:

Yep, same here.
EDIT: Amoled screen.
Bugger, there goes that idea then...

#13 kingryu1

kingryu1
  • Members
  • 2 posts

Posted 28 November 2010 - 04:20 PM

SLCD screen here. Rolled back to RC1 for the time being. Will keep an eye on this thread in the hopes it gets solved :-)
Let me know if you need any more info about my phone.

#14 Benlehot

Benlehot
  • Members
  • 1 posts

Posted 28 November 2010 - 04:38 PM

Same problem here!

#15 Msills

Msills
  • Members
  • 1 posts

Posted 28 November 2010 - 07:01 PM

Same problem here since RC2. (SLCD)

#16 blkqi

blkqi
  • Members
  • 26 posts

Posted 28 November 2010 - 07:12 PM

this bug affects the CDMA desire also. SLCD

#17 JokeyRhyme

JokeyRhyme
  • Members
  • 260 posts

Posted 28 November 2010 - 09:14 PM

I'm on A8183 (850MHz) with an AMOLED screen here and I've never experienced this issue. I've also never at any point changed any scheduler or clock-speed settings. I also have surface dithering disabled. I have no idea what may or may not effect this. /shrug

#18 last czarnian

last czarnian
  • Members
  • 202 posts

Posted 28 November 2010 - 10:17 PM

see post 122 in the nightly discussion...

#19 yenemy

yenemy
  • Members
  • 30 posts

Posted 29 November 2010 - 11:20 AM

For anyone lazy (like me), here is a link to the aforementioned post #122 from the nightlies.

Also, I guess it's a moot issue, but I'm using an SLCD version too.

#20 rapalax

rapalax
  • Donators
  • 40 posts

Posted 29 November 2010 - 11:11 PM

So we've determined that this is a common problem for slcd desire devices but does it affect ALL desire slcd devices? Could there be some sort of workaround out there until the kernel is fixed?

If anyone's slcd device is not doing this, please reply.

Edited by rapalax, 29 November 2010 - 11:12 PM.