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
 

CM6 Nexus One touch screen issues??


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

#1 wilskywalker

wilskywalker
  • Members
  • 32 posts

Posted 12 July 2010 - 04:44 PM

I have just purchased a Nexus One, and flashed the latest cm6 froyo ROM. The ROM itself is fantastic as always!!

I have noticed a problem though, every so often the touch screen seems to register the touch much lower on the screen than where I press it. And then. Sometimes it just goes into meltdown where it doesn't register the touches correctly at all, and the phone vibrates wherever you touch the screen. This is only rectified by a reboot.

This does not seem to affect the touch buttons though strangley.

I wondered has anyone else experienced or heard of this problem? Is it due to the ROM or the froyo upgrade? Or do I have a broken phone?

Thanks :-)

#2 ushi

ushi
  • Members
  • 296 posts

Posted 12 July 2010 - 04:51 PM

Did you try a wipe/reflash?

Sometimes a flash just isn't as stable as others. I've had those kind of issues in the past, but dont after 5.0.8+

#3 wilskywalker

wilskywalker
  • Members
  • 32 posts

Posted 12 July 2010 - 05:30 PM

@ushi - Hi buddy, I did a full wipe when I first flashed CM6, I will try re-flashing the ROM, I'm not sure this will fix it from what I have read on the old t'internet since I posted.

I found this thread on the Google forum's, this seems to be a more wide spread problem than I thought to start with, and it doesn't seem to be restricted to the CM6 ROM...here

This has put my mind at rest a little as it is obviously a software issue as it is not constant, if it was hardware based the problem would surely be constant and in the same area of the screen?

Anyone else having these problems?

Any thoughts folks??  :rolleyes:

#4 bornio

bornio
  • Donators
  • 28 posts

Posted 12 July 2010 - 06:27 PM

I'm having a similar issue as well.
You can notice it quickly if you hold your finger on the keyboard and swipe around the keys quickly. It will quickly "lose signal".

However, if continue holding one finger, and touch with another finger for a moment, you will notice the sensing is restored perfectly, despite the "lost signal".

Weird.

#5 koreandutch

koreandutch
  • Members
  • 8 posts

Posted 12 July 2010 - 11:14 PM

yea, I experienced similar issue while I was using Market App.  My phone was installing a couple of apps, then all the sudden the phone vibrated every time I touched the screen.  It happened for a minute, then it went away. Scary.  :blink:

#6 VsIvAk

VsIvAk
  • Members
  • 1 posts

Posted 12 July 2010 - 11:25 PM

View Postkoreandutch, on 12 July 2010 - 11:14 PM, said:

yea, I experienced similar issue while I was using Market App.  My phone was installing a couple of apps, then all the sudden the phone vibrated every time I touched the screen.  It happened for a minute, then it went away. Scary.  :blink:

The simplest workaround is hitting the power button to turn the screen off, then hit the power button again and the screen calibration must reset itself. Atleast that is what I do when it happens to me. I know it is not a fix, but a solution rather than reboot.

#7 koreandutch

koreandutch
  • Members
  • 8 posts

Posted 13 July 2010 - 05:12 AM

View PostVsIvAk, on 12 July 2010 - 11:25 PM, said:

The simplest workaround is hitting the power button to turn the screen off, then hit the power button again and the screen calibration must reset itself. Atleast that is what I do when it happens to me. I know it is not a fix, but a solution rather than reboot.

I agree.  When that happened again, I turned off the screen by hitting the power button.  =|

#8 xcobrax

xcobrax
  • Members
  • 13 posts

Posted 13 July 2010 - 07:07 AM

View Postwilskywalker, on 12 July 2010 - 04:44 PM, said:

I have just purchased a Nexus One, and flashed the latest cm6 froyo ROM. The ROM itself is fantastic as always!!

I have noticed a problem though, every so often the touch screen seems to register the touch much lower on the screen than where I press it. And then. Sometimes it just goes into meltdown where it doesn't register the touches correctly at all, and the phone vibrates wherever you touch the screen. This is only rectified by a reboot.

This does not seem to affect the touch buttons though strangley.

I wondered has anyone else experienced or heard of this problem? Is it due to the ROM or the froyo upgrade? Or do I have a broken phone?

Thanks :-)

I have the same issue. It's the device. Some N 1s had this issue. Not too big of a deal but very annoying.  I noticed it gets like that if of is hot, or plugged in (heat given off by battery)...I also talked with our HTC Rep and he had the same issue.

#9 Rogobono

Rogobono
  • Members
  • 17 posts

Posted 13 July 2010 - 07:21 AM

I have gotten this as well, was pretty annoying. It doesn't happen often at all, but when it does, I just rub the screen on my pant leg for 2 seconds or so. Now I am not sure if it is me just rubbing off the YUCK that was on the screen that could have possibly been messing it up, OR, it could sense the heat from my leg on the screen and kind of confuse it into doing somewhat of a reset on the phones end. Either way, take your phone, and RUB it on your leg.... except while you're in Starbucks...

#10 jereeeemy

jereeeemy
  • Members
  • 3 posts

Posted 13 July 2010 - 07:44 AM

hmmm......frankly, my nexus one has this issue since the first day i got it....and my friends have this issue too, he doesn't flash CM at all.

#11 RightYouAreKen

RightYouAreKen
  • Members
  • 7 posts

Posted 13 July 2010 - 07:21 PM

Yep, I had this on stock and cm 5. I think the touchscreen controller just gets flaky sometimes. Turning off the screen then on again always fixes it. Happens to me maybe twice a week.

#12 wilskywalker

wilskywalker
  • Members
  • 32 posts

Posted 13 July 2010 - 08:54 PM

Thanks for all the replies folks, you have definitely put my mind to rest confirming I am not alone with this problem.

I have found it mostly happens when the battery is low, and also when the unit gets hot, be that external, or the surprisingly large amount of heat the phone itself generates internally when carrying out certain functions (is this also normal Nexus One behaviour??).

Originally I was rebooting to fix the problem as I assumed this would be required. But as most of you have noted, using the power button to merely turn the screen off and on again seems to immediately cure the problem. An annoyance certainly, but nothing I can't live with! :-)

#13 artcarney

artcarney
  • Members
  • 46 posts

Posted 15 July 2010 - 06:01 AM

View PostRightYouAreKen, on 13 July 2010 - 07:21 PM, said:

Yep, I had this on stock and cm 5. I think the touchscreen controller just gets flaky sometimes. Turning off the screen then on again always fixes it. Happens to me maybe twice a week.

This works. Seems to be the only fix that works for me.

#14 marzib

marzib
  • Members
  • 18 posts

Posted 29 October 2010 - 08:45 PM

I've had the same problem for a while now as well on my new Nexus One (bought in September). Has anyone found a hack/fix for it anywhere??

#15 snackbidi

snackbidi
  • Donators
  • 118 posts

Posted 30 October 2010 - 12:10 AM

Some people, after installing the new 5.12 radio, claim that the problem has vanished. I have yet to try this myself because I can't find a signed version of the radio zip file, but it's worth a try if you want to fix it.

If you search around for user reviews/feedback of the new radio, you will find that the issue has been fixed by updating that for many people.

#16 marzib

marzib
  • Members
  • 18 posts

Posted 30 October 2010 - 03:58 PM

View Postsnackbidi, on 30 October 2010 - 12:10 AM, said:

Some people, after installing the new 5.12 radio, claim that the problem has vanished. I have yet to try this myself because I can't find a signed version of the radio zip file, but it's worth a try if you want to fix it.

If you search around for user reviews/feedback of the new radio, you will find that the issue has been fixed by updating that for many people.

Thanks! You're right, people seem to say it fixed it. But yeah, only found non-signed versions (I don't mind and I'm about to try it), link is here

http://forum.xda-dev...ad.php?t=816917

#17 pconwell

pconwell

    It's okay, I'm from the Internet.

  • Donators
  • 345 posts

Posted 30 October 2010 - 05:15 PM

if that link doesn't work, here is a direct link: http://www.4shared.c...4/radioimg.html

Unzip it and check the MD5: 263fb298d747f9e5632b373c69ce7893

#18 snackbidi

snackbidi
  • Donators
  • 118 posts

Posted 30 October 2010 - 09:19 PM

I updated to the 5.12 radio through ADB and so far, everything looks good. No more screen issues as far as I can tell.
I'll do more extensive testing and report back. Also, wifi reception with the new radio seems to be a wee bit stronger.

If you can't flash the zip because it's unsigned and your particular recovery can't handle that, do it through ADB, its very simple and quick.

#19 Muzikant

Muzikant
  • Members
  • 1 posts

Posted 17 May 2011 - 07:26 AM

Hi, the installation guide of CyanogenMod says to use this radio only for korean users.

Anyone tried it (Who is not Korean)? Is everyone who commented on this post have radio version 5.08 ?

Why is this radio limited to Korean users only ?

#20 bassmadrigal

bassmadrigal
  • Moderators
  • 4,058 posts

Posted 17 May 2011 - 08:08 AM

From what I have noticed on this forum, the 5.08 radio seems to have the best performance and compatibility with Gingerbread. Google even released the 5.08 radio with the Gingerbread OTA update. Google had to of had a reason to not push that radio out to everyone, even if I don't know what it was.