Database Users

Anyone using CyanogenMod or Desire Rom encounter touch screen problem?

Anyone using CyanogenMod or Desire Rom encounter the random touch misalign problem that has flooded the google's forum http://www.google.com/support/forum/p/android/thread?tid=04134c63c784258e&hl=en

helloworld1 said:
Anyone using CyanogenMod or Desire Rom encounter the random touch misalign problem that has flooded the google's forum http://www.google.com/support/forum/p/android/thread?tid=04134c63c784258e&hl=en
Click to expand...
Click to collapse
happens occasionally, but now rarely (almost never) with the latest cyanogenMod (5.0.3.1) - turn off the screen and turn on fixes it.
i think it will be eradicated completely with the next offical (and cm update)

yes, it is better for me too with CyanogenMod 5.03.01, I feel it is more due to the new .32 kernel

Now that you mention it--yeah, the problem has all but disappeared ever since I flashed CM and now Modaco's Desire. I think I encountered it a grand total of once in two-three days, though admittedly I still haven't spent enough time with the Desire ROM.

I wonder whether the touch screen driver in CM is the same as the one in the official ROM>

No problems at all with Desire image and rarely using latest cyan. It was making my stock unusable.

Ha, id totally forgot about that issue, I havent experienced it at all since switching to Cyan, atleast not that I can remember

I noticed that the alignment/calibration problem has been improved. not perfect...but improved.

I've been actively trying to palm-wrap and tilt the screen at an angle that usually gave me calibration problems on stock. Nothing; touch alignment etc remains perfect. I guess it was a software and not hardware issue after all!

So the CM does not eliminate the problem. I hope google will fix the driver in the source code, or the problem will not be gone.

i have a question, does it fix the 3g dropping/switching to edge problem?

I still have it on cyanogen 5.0.3. Actually quite often and this really annoys me, I did a wipe install.

Anyone Else Tempted to Go Back to v3.01?

Is anyone else here tempted to go back to HC v3.01?
One of the main things I do on my A500 is watch downloaded videos, and I encounter quite a few problems with that on HC v3.1 that I never encountered on HC v3.01. MoboPlayer just flat out no longer works on my device -- I get nothing but unrecoverable lock-ups and force-closes. RockPlayer is still working (thankfully), but not in hardware mode. Even the stock video player can't play any of the files that I previously could.
Everything else that came with HC v3.1 is enough behind-the-scenes that I just don't notice it or it has no real world benefit for me. In other words, I definitely wasn't missing any of it back when I was running HC v3.01. I'm just not seeing any real world benefit to the v3.1 upgrade -- I'm only seeing negatives. I'm very tempted to go back.

internetpilot said:
Is anyone else here tempted to go back to HC v3.01?
One of the main things I do on my A500 is watch downloaded videos, and I encounter quite a few problems with that on HC v3.1 that I never encountered on HC v3.01. MoboPlayer just flat out no longer works on my device -- I get nothing but unrecoverable lock-ups and force-closes. RockPlayer is still working (thankfully), but not in hardware mode. Even the stock video player can't play any of the files that I previously could.
Everything else that came with HC v3.1 is enough behind-the-scenes that I just don't notice it or it has no real world benefit for me. In other words, I definitely wasn't missing any of it back when I was running HC v3.01. I'm just not seeing any real world benefit to the v3.1 upgrade -- I'm only seeing negatives. I'm very tempted to go back.
Click to expand...
Click to collapse
Had none of these issues. Maybe reinstall your player apps onto the new platform, especially since MOBO should prompt you to download a specific codec pack... other than that, maybe let us know what formats you're using so we can give more precise info.

simonsgray said:
Had none of these issues. Maybe reinstall your player apps onto the new platform, especially since MOBO should prompt you to download a specific codec pack... other than that, maybe let us know what formats you're using so we can give more precise info.
Click to expand...
Click to collapse
I deleted/reinstalled both RockPlayer and MoboPlayer, but no joy. I even factory reset my A500, and then after basic configuring only installed Mobo and the exact same issues occurred.
I'm attempting to play xvid files that worked just fine using MoboPlayer, RockPlayer, and the stock player on stock HC 3.01, but they just wont play on stock HC v3.1. For me, this is a HC v3.1 dealbreaker.
Edit: Just got notified of 4.010.10 gen2, downloaded it, updated, and things are now working a lot better. A little quirkiness was going on in both RockPlayer and Mobo, but it went away when I deleted both apps and reinstalled. Since that update, the stock player works fine on these same xvid files again.
Maybe I'll stick with HC v3.1 after all! (unless the next incremental breaks it again like the 4.010.8 gen1 did)

I had the opposite experience. Videos that would not play smoothly in 3.01, now play great in 3.1. The only issue I am having with 3.1 is the dropping WiFi, but hitting the reset button seems to be solving that for now.

nithos1 said:
I had the opposite experience. Videos that would not play smoothly in 3.01, now play great in 3.1. The only issue I am having with 3.1 is the dropping WiFi, but hitting the reset button seems to be solving that for now.
Click to expand...
Click to collapse
When you say "solving" does that mean you have to do the reset thing regularly?
(It may just be a syntactic difference, but if it was fixed, I'd have said "solved it for now". "Solving" implies an on-going condition of fix and re-fix)(Genuine question - I'm not commenting on your use of English)
To the OP:
I have no intention of letting my A500 update to 3.1. I've seen waay too many posts of bugs and faults in it.
OK, the rooters and rom flashers all say to root and delete this and do that.. I say you shouldn't HAVE to root and delete to fix the update's errors!.
Nope, me = 3.01 for now. I'll see what 3.2 might be like..

I will not never and ever go back to 3.0.1 for 1 pure main reason
USB support of my camera... I plug and the gallery popup and can transfert the files directly without thinking something else... (I hope we will have some kind of create folder by date or else...)

Fluffbutt said:
I have no intention of letting my A500 update to 3.1. I've seen waay too many posts of bugs and faults in it.
OK, the rooters and rom flashers all say to root and delete this and do that.. I say you shouldn't HAVE to root and delete to fix the update's errors!.
Nope, me = 3.01 for now. I'll see what 3.2 might be like..
Click to expand...
Click to collapse
I have to pretty much agree -- I have seen more problems than benefit. With the latest incremental update things seem to be working a lot better, but I am worried about what the next incremental update could break.
I didn't see much of a purpose in updating my HTC Evo 4G phone from Froyo to Gingerbread either. I immediately went back to a Froyo based ROM until the same ROM dev came out with a custom Gingerbread ROM. These OTA's from the manufacturer aren't always the gold and jewels everyone anticipates.
sanaell said:
I will not never and ever go back to 3.0.1 for 1 pure main reason
USB support of my camera... I plug and the gallery popup and can transfert the files directly without thinking something else... (I hope we will have some kind of create folder by date or else...)
Click to expand...
Click to collapse
I never had two much of a problem hosting my Pentax DSLR camera on HC v3.01. It was sometimes slow to discover it, but then I started using the USB Mount All app everything USB was discovered quickly.
I'm still not 100% happy with my video performance on v3.1. It's much better with 4.010.10 gen2, but it's still not as good as it originally was with v3.01.

I was experiencing major issues with the Wifi after the update as well. It was really annoying.
So last week I tried a bunch of things. What worked for me was to set the wifi to turn off when the screen was off. Now, if I am still downloading things it stays connected with the screen off. Also, I still hear the notification sound when an email comes in even if the tablet has the screen off and nothing running. Its been one week and I haven't noticed a difference between it being on or off with the screen. I haven't had to reset the tablet nor have I had to delete any files. It runs perfecto mundo and doesn't drain any extra battery. Last night I lost about 8% overnight. Just something to try out.

No way I would ever go back lol. Using full keyboard and mouse with RDP makes this tablet take advantage of the speed and power of powerful desktop at home. ANd using the HoneyVillain ROM everything runs so well and smooth including all my videos.

In a word, no. I'd never go back. 3.1 has been great all around.

internetpilot said:
Is anyone else here tempted to go back to HC v3.01?
One of the main things I do on my A500 is watch downloaded videos, and I encounter quite a few problems with that on HC v3.1 that I never encountered on HC v3.01. MoboPlayer just flat out no longer works on my device -- I get nothing but unrecoverable lock-ups and force-closes. RockPlayer is still working (thankfully), but not in hardware mode. Even the stock video player can't play any of the files that I previously could.
Everything else that came with HC v3.1 is enough behind-the-scenes that I just don't notice it or it has no real world benefit for me. In other words, I definitely wasn't missing any of it back when I was running HC v3.01. I'm just not seeing any real world benefit to the v3.1 upgrade -- I'm only seeing negatives. I'm very tempted to go back.
Click to expand...
Click to collapse
When making a post like this, it's a good idea to just throw the build you're on out there. I for one have no issues with 3.1. I never had issues with the first build that came and I am not having issues with the recent build seeded yesterday. I use Moboplayer as well.
Did you do any sort of modding? ie: Did you get 3.1 or 3.0.1 unofficially through XDA or are you/have you been running completely stock? There must be some reason user A. is getting one result and B. another - if it's not faulty hardware then it's faulty software. However, you said you factory reset. The last thing I can possibly think of is that you modded and it's messed with the system somehow or there really is some faulty hardware.
I'm running 4.010.10, I came from 4.010.08. I've been running stock from day 1. I've never rooted, nor installed any ROMs or mods (wifi supplicant, etc.) from XDA and as I mentioned, no trouble at all.

johnnyb82 said:
...What worked for me was to set the wifi to turn off when the screen was off. Now, if I am still downloading things it stays connected with the screen off. Also, I still hear the notification sound when an email comes in even if the tablet has the screen off and nothing running...
Click to expand...
Click to collapse
So what you're saying is you have wifi set to go OFF when the screen is off but it stays ON?
And that's not something anyone considers to be a bug (regardless of if it helped your wifi stay on or not)???

[Q] Hardware keyboard problems.

Hi, my DROID 2 has a keyboard issue, it seems that whenever I type, it'll randomly type the same letter multiple times. Thinking it was a Liberty GB issue, I used it as an excuse to jump ship to CM7. I'm running CM7, it's amazing. But, I still have the multiple entry problem. It's really bugging me, as my DROID 2 has never been better, and I don't think I can send it in for a warranty replacement due to it's cracked LCD, and I don't want to switch to my Xperia Play for messaging, because it doesn't have a hardware keyboard. I looked around, and it seems that it's a gingerbread problem, not specifically my phone, although I've not noticed the problem when using the soft keyboard, only the hard one, and only since I've started using Liberty and CM7. I was running an old version of Zombiestomped before, and I did not have that problem.

I'm running Miui and have never run into that problem. So it shouldn't be a GB problem. My guess is that it is either a CM/Liberty problem or a hardware problem (sticky keyboard).

I've been having the same problem. I used to use Fission, then I bumped up to CyanogenMod nightly #4, and last night I updated to #40. I THINKKKK I had the problem towards the end of using Fission, but I could be mistaken, that was a while ago and I can't really remember. It seems to have gotten progressively worse over the time that I've noticed it, which has led me to believe there might be something like dust in the keyboard which is causing it to fidget, or something along those lines.

phantom button press causing screenshot

I've had this issue since the update to ED01 (or maybe before, I can't remember). Anyway it's darn annoying. I froze the screenshot apk to keep the screenshots from happening but there is still the issue with random back/return button presses. Sometimes it's the home key. Sometimes the search key will long-press and cause voice search to come up. It's mostly the return/back key.
I've had this problem on two Fascinates (the modem died on my first one and was replaced about a month ago). It happened with ED05 and it is now happening (although less frequently) with PWGB EH09 ROM v2.0b3 running ED05 modem. My daughters fascinate was having the same problem on stock ED05.
I've searched through several forums and it seems that lots of people have the same or similar symptoms with the fascinate/captivate as well as with the Nexus S.
I see that google tracked it as a problem earlier in the year and claimed to be working the issue and had a fix that was supposed to be rolled out. Never happened.
I think I've narrowed it down to only happening when the phone is using 3G data.
I'd like to locate and fix the problem but I could use some help getting started. For starters, I'd like to get a development environment set up and running so that I can build and test kernels. I can do this on my own but if someone could guide me so that I don't have to go through that learning curve, it would be appreciated.
My first thought is that it's a driver issue. In the source code there's a folder under src/kernel/drivers named "input" that has a bunch of drivers. Does anyone know which driver is used for this phone?
Thanks,
Dale
UPDATE: 15 Mar 2012:
I added a 100pf capacitor to the interrupt line on the cypress touchkey chip today. Everything works fine now. dmesg shows that I'm no longer getting any false interrupts. I downloaded a 6meg file over 3G and had zero false interrupts. Without the cap there would have been at least a couple of hundred (I use dmesg to check for false interrupts since I have printk statements in my code). I'll keep testing but I think this is it. I'll try to get some pics of the tack on showing where I added the cap. It's some tiny sh-t to work on. I had to do the soldering under a microscope. It was not easy. The cap I put on is a 100pf 50v X7R I bought from Digikey. Digikey part number 445-6856-1-ND. I got a 100 of them for <$6 with shipping.
I'll go back to the driver and remove the software fixes to see if the hardware fix takes care of the problem completely.
The parts are $0.028 each if you buy a hundred. They're less than a penny if you buy thousands. Seems a shame that Samsung couldn't pony up an extra penny to keep this problem from happening in the first place.
For those of you who don't want to crack your phone open, there's still the software (read: duct tape) fix.
Here's a link to the thread showing the hardware mod http://forum.xda-developers.com/showthread.php?p=23725671#post23725671

Yeah a lot of people have tried to fix this but nothing has ever worked. It's a well-known issue.

sageDieu said:
Yeah a lot of people have tried to fix this but nothing has ever worked. It's a well-known issue.
Click to expand...
Click to collapse
Yeah, that's why I'd like to try to fix the problem. Not to dismiss the skills of the other people who have tried, but I'm pretty good at finding bugs in hardware.

Well more power to ya, if you fix it then you will make a LOT of people very happy. You should absolutely get in contact with some developers of kernels (jt1134, sixstringsg, Tk-Glitch, sswek2, etc) if you have any ideas or get anything fixed. I'm sure they will be glad to help you out with the issue and use any of your changes in their kernels.

i have a SGS I9000. my problem is phantom presses of menu and back button. tried flashing to stock firmware etr (original was xeu). installed ics. all with no result. FINALLY found that it occurs only when using packet data (edge) we dont have 3g yet. i ve tried disabling packet data and using wi-fi and there is no preblem.
the diagnosis finally comes to this - problem related with packet data and may be (most probably be) related to software bug in the touch button firmware.

It only seems to happen to me at my house, which is in a low signal area. I'm betting it is buried somewhere in the tower switching code, as my phone switches towers constantly at home.
Sent from my SCH-I500

Yes the problem only seems to occur for me when on 3g and not wifi. I've verified this with the three other fascinates in my house. I'm digging through the interrupt routines now using the kgb kernel source.
Does anyone know which interrupt line on the processor the cypress touchkey device is connected to?
I'm almost ready to break open the phone and start probing with an o'scope.

electric bill said:
Yes the problem only seems to occur for me when on 3g and not wifi. I've verified this with the three other fascinates in my house. I'm digging through the interrupt routines now using the kgb kernel source.
Does anyone know which interrupt line on the processor the cypress touchkey device is connected to?
I'm almost ready to break open the phone and start probing with an o'scope.
Click to expand...
Click to collapse
Hey Bill (I'm also a Bill, heh) :
You'll probably want to check out the changes I did for the V13.1 Glitch kernel. They seem to have at least severely limited the phantom keypresses. I did find some GPIO pins that were configured differently by the dpram driver and the mach-aries.c gpio (and gpio while sleeping) settings, and making those match up seemed to help a lot.
I'm an embedded guy, but more on the software side. I don't particularly want to tear my phone apart and hit it with a scope, but hey .. if you do that and find anything, go for it!
FYI, I was able to determine that the IRQ number used for the cypress-touchkey driver, and the one that's firing during the phantom key events, is IRQ 334 (0x14E). Without having a schematic to look at, though, I wasn't able to figure out what might be causing it to fire, nor even begin to guess why it has something to do with poor signal strength.
Anyway .. I've been beating my head against this problem for a long time .. so if there's anything else you'd like to pick my brain about, let me know.

Downgrade
I have found that the only thing that works is to downgrade. I am however through uscellular so my phone is the mesmerize. I tried talking to a representative about my problem but all they would say is to upgrade. After multiple tries and different methods I downgraded to DI14 from EH09 and I have not had one problem since. Besides one with random menu flashes but it turned out to be the application Zedge. Hope this helps. If not at least I can say I tried.

ssewk2x said:
Hey Bill (I'm also a Bill, heh) :
You'll probably want to check out the changes I did for the V13.1 Glitch kernel. They seem to have at least severely limited the phantom keypresses. I did find some GPIO pins that were configured differently by the dpram driver and the mach-aries.c gpio (and gpio while sleeping) settings, and making those match up seemed to help a lot.
I'm an embedded guy, but more on the software side. I don't particularly want to tear my phone apart and hit it with a scope, but hey .. if you do that and find anything, go for it!
FYI, I was able to determine that the IRQ number used for the cypress-touchkey driver, and the one that's firing during the phantom key events, is IRQ 334 (0x14E). Without having a schematic to look at, though, I wasn't able to figure out what might be causing it to fire, nor even begin to guess why it has something to do with poor signal strength.
Anyway .. I've been beating my head against this problem for a long time .. so if there's anything else you'd like to pick my brain about, let me know.
Click to expand...
Click to collapse
What? _I_ found out that it is interrupt 334! )
Sent from my SCH-I500 using Tapatalk

electric bill said:
What? _I_ found out that it is interrupt 334! )
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Yes, yes you did, lol. And you're probably going to end up fixing the whole thing before i get a chance to look at it again, lol.

ssewk2x said:
Yes, yes you did, lol. And you're probably going to end up fixing the whole thing before i get a chance to look at it again, lol.
Click to expand...
Click to collapse
I've been testing the code for about a day. I added the int test to the interrupt handler just now and I'll test for awhile. I'll prob also put it on my daughters phone since she uses hers about 10x what I do.

Excellent. You're welcome to drop by the glitch kernel thread, btw. I've got some folks testing there with good results so far.

Superclean Rom has screenshot removed. Also Geewiz 2.4.2 has a mod to remove the screenshot, just flash this in recovery:
http://db.tt/xERensX3
It happens when you have a low signal. It's was so annoying but no longer have that issue.
Keep me Fascinated.

It's not just the screenshot that's annoying. When using navigation, the phone will keep saying "this will end the navigation" as if the back button keeps getting pressed. Sometimes the menu comes up as well. Really annoying and kind of dangerous to have to keep hitting cancel while driving. Removing the screenshot app will not fix this. I'm really hoping someone finds a true fix for this. Otherwise I'm getting a new phone soon.
Sent from my SCH-I500 using XDA App

SnrSuave said:
It's not just the screenshot that's annoying. When using navigation, the phone will keep saying "this will end the navigation" as if the back button keeps getting pressed. Sometimes the menu comes up as well. Really annoying and kind of dangerous to have to keep hitting cancel while driving. Removing the screenshot app will not fix this. I'm really hoping someone finds a true fix for this. Otherwise I'm getting a new phone soon.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I actually just re-enabled screenshot on my phone. The glitch kernel ( http://forum.xda-developers.com/showthread.php?t=1252871 ) has a fix that they're testing that seems to work pretty good. I'm not sure if it's in their release or just in testing. I think comradesven is putting the code into the kgb kernel too http://forum.xda-developers.com/showthread.php?t=1364912
I've been running my own butchered up kgb kernel for a few days with the fix and it seems to help quite a bit.

electric bill said:
I've had this issue since the update to ED01 (or maybe before, I can't remember). Anyway it's darn annoying. I froze the screenshot apk to keep the screenshots from happening but there is still the issue with random back/return button presses. Sometimes it's the home key. Sometimes the search key will long-press and cause voice search to come up. It's mostly the return/back key.
I've had this problem on two Fascinates (the modem died on my first one and was replaced about a month ago). It happened with ED05 and it is now happening (although less frequently) with PWGB EH09 ROM v2.0b3 running ED05 modem. My daughters fascinate was having the same problem on stock ED05.
I've searched through several forums and it seems that lots of people have the same or similar symptoms with the fascinate/captivate as well as with the Nexus S.
I see that google tracked it as a problem earlier in the year and claimed to be working the issue and had a fix that was supposed to be rolled out. Never happened.
I think I've narrowed it down to only happening when the phone is using 3G data.
I'd like to locate and fix the problem but I could use some help getting started. For starters, I'd like to get a development environment set up and running so that I can build and test kernels. I can do this on my own but if someone could guide me so that I don't have to go through that learning curve, it would be appreciated.
My first thought is that it's a driver issue. In the source code there's a folder under src/kernel/drivers named "input" that has a bunch of drivers. Does anyone know which driver is used for this phone?
Thanks,
Dale
Click to expand...
Click to collapse
Sent from my SCH-I500 using XDA App
I had the same problem...I went to big red and exchanged my phone...well they actually sent me a refurb... this was last week

electric bill said:
I actually just re-enabled screenshot on my phone. The glitch kernel ( http://forum.xda-developers.com/showthread.php?t=1252871 ) has a fix that they're testing that seems to work pretty good. I'm not sure if it's in their release or just in testing. I think comradesven is putting the code into the kgb kernel too http://forum.xda-developers.com/showthread.php?t=1364912
I've been running my own butchered up kgb kernel for a few days with the fix and it seems to help quite a bit.
Click to expand...
Click to collapse
Thanks all u guys. I 'd really appreciate if u could find a standalone fix for this issue i.e. no modded kernel only the touchkey fix. Thanks again.

th3b3 said:
Sent from my SCH-I500 using XDA App
I had the same problem...I went to big red and exchanged my phone...well they actually sent me a refurb... this was last week
Click to expand...
Click to collapse
yeah, I'm on my third phone. there's been some speculation that phones built early (ie when they just started making them) don't have the problem. the data code on mine is 08/05/2011.

dff_jx said:
Thanks all u guys. I 'd really appreciate if u could find a standalone fix for this issue i.e. no modded kernel only the touchkey fix. Thanks again.
Click to expand...
Click to collapse
technically if we change the driver code, which is in the kernel then it's been modded...
If you want to run fully stock ROM and see this problem go away then I think you can add a 120pf cap from the interrupt pin on the cypress chip to ground. I haven't tried it yet but I'm going to as soon as I get done testing the s/w fixes.

Portion of my screen does not work on Gingerbread Roms

I have been hoping that this would be corrected once the OTA dropped, but that is not the case. Also, I have come across people having this issue with the Asus Transformer, however, it seems that they had a bad piece of hardware. I doubt that is the case with my Epic, as the error only occurs on Gingerbread roms (including CM7).
On the left side of my screen, in either portrait or landscape orientation, that will be unresponsive for what seems to be a random period of time, or until I turn the screen off and on again. It is in the left-center of the screen, all the way to the S key on a soft keyboard, down to Z, and up past the text entry field.
Has anyone else experienced this, or have any recommendations on correcting this?

I have experience that exact same issue on both ACS ICS Rom and ERA RC1 rom. I'm currently on ERA rom and switch backed to the Android keyboard because it seems like the Swype keyboard was giving me more issues. Hopefully someone looks into this because I really like the swype keyboard better.

I have experienced this on Froyo roms as well. Mine has always been down the center of my screen. That really sucks since most notifications are in the center. When I upgraded to Gingerbread this got much worse! I filed an insurance claim with best buy yesterday for some physical damage on the phone, so i am hoping my new epic doesn't have this issue.
oh and on GB, my phone does this on stock without root. it is maddening i tell ya lol.

So was it deemed a hardware problem?

I haven't had this problem and i've been running Cyanogen on it for a while, my girlfriend is running stock and hasn't mentioned anything like that to me.Revert to stock and do an OTA to the stock gingerbread build and see if it still happens.