Database Info

[Possible DEFECT] UPDATE! (Sep. 16, 2011) Touchscreen Responsiveness Issues

Ok I've been meaning to make this thread for a while now but held off on it assuming it was just my phone, or maybe even just a small batch of phones. But now that I have noticed a lot of people having the same problem as mine the I feel that it should definitely be addressed and hopefully more people will be more aware of it.
Basically the problem is with the touchscreen while I am typing. Certain keys will just "lock" up and become unresponsive. The most noticeable key would be the "Delete" key. It won't work and would be completely unresponsive, only way it will come back in working form is if I just simply wait, or close/re-open the keyboard. Other keys get affected as well, such as other vowels and the letter "O" is prominent as well. But pretty much almost every key gets affected here and there, the "delete" key is just the most prominent and happens more than the others.
Now the obvious first act would be to pin-point the problem. Various possibilities would be:
- Keyboards fault
- Kernel/ROM's fault
- Or if it's just a manufacture defect
First I thought it was just the stock Android KB's problem, so I'e literally tried almost every mainstream KB out there in the market such as:
- SmartKeyboard Pro
- SwiftKey X
- Flex T9
- Swype
- HTC's Touch Input
- Go Keyboard
And with all of those I still experience the problem. So I counted out the possibility of the KB being the cause of the problem. So then i figured it was the ROM itself, but I've tried numerous ROM's such as Virtual Fusion, Virtual Unity, speedDEMON MIUI, CM7 and it's numerous RC's/Nightly's. And the problem still persisted with all of those ROM's.
The only ROM's I know it doesn't happen on is Royal Ginger 2.1 and the stock T-Mobile mySense build. Also I've had other MT4G's in the past that did not have this problem on any ROM.
That confused me as now I can't tell if the problem is software or hardware related.
Thus, I called TMO for a warranty exchange. The phone I had where the problem happened was good screen with BAD eMMC chip. The new one I just received is good screen with GOOD eMMC. With my new phone the problem still persists.
So basically I would just like to get to the bottom of this problem and see if anyone else is having this problem, and if so please post your issue here as well. I would really like to know if this is just maybe a kernel issue with the latest MT4G kernels that are out, or if it's just another one of the plethora of hardware problems that haunts the MT4G.
====UPDATE====
Okay, so there seems so have been a fix floating around for this and it was DEFINITELY not what I had expected. Credit goes to the dude that found it and for jberg22 for bringing it to the attention in this thread. Here is the thread that you can read up on. I'm not sure if it's a 100% fix but it has been a fix for some. Try it and let us know what your results are! It would be nice to know if this has worked for people with this problem. Here's a picture of what it looks like on our MT4G thanks to Mathato!

Glad you decided to post about this. Since more and more people are having touchscreen issues, it's definitely becoming a problem. The mystery is why the problem occurs on all ROMs except for RG. Hopefully more people will post here with their issues and we can get this thing nailed down!

TeeJay3800 said:
Glad you decided to post about this. Since more and more people are having touchscreen issues, it's definitely becoming a problem. The mystery is why the problem occurs on all ROMs except for RG. Hopefully more people will post here with their issues and we can get this thing nailed down!
Click to expand...
Click to collapse
I had that problem with my first mytouch 4g and then ended up bricking it trying to unroot it...but i've never had a problem with this one.

never had any problems like this before... did it happen over time? or immediately after you flashed the ROM?

saranhai said:
never had any problems like this before... did it happen over time? or immediately after you flashed the ROM?
Click to expand...
Click to collapse
Pretty much after a day I started to notice it with VU. But it's usually instant.

I've been complaining about this for a while. Since it doesn't happen on stock rom I don't know wtf to think.
Sent from my HTC Glacier using XDA Premium App

I've definitely seen this,
Some keys lock,
The answer button when receiving a call,
The pull down bar not sticking, for example able to grab it but once sliding it down an inch it goes right back up.
All this on ONLY VU.
No other ROM does this to me, but I stick with it because I love unity!
Sent from my HTC Glacier using XDA App

I wonder if this is happening on 2.3.4 builds only?

my2sense said:
I wonder if this is happening on 2.3.4 builds only?
Click to expand...
Click to collapse
I'm assuming the ota 2.3.4 doesn't have this issue?
Sent from my HTC Glacier using XDA Premium App

Phateless said:
I'm assuming the ota 2.3.4 doesn't have this issue?
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Good question. I have yet to try the official TMO OTA ROM. But I would assume the problem would disappear in that build. I'll probably flash it to check one day.
Sent from my HTC Glacier using XDA Premium App

If there's at least one build that doesn't have this bug (and which happens to be the original build) - it means that it's SW issue.

Jack_R1 said:
If there's at least one build that doesn't have this bug (and which happens to be the original build) - it means that it's SW issue.
Click to expand...
Click to collapse
I agree. I went back to stock, almost hoping to see the issue appear again, but it didn't.

Jack_R1 said:
If there's at least one build that doesn't have this bug (and which happens to be the original build) - it means that it's SW issue.
Click to expand...
Click to collapse
I would tend to think so too, but I've run VU since the day it was released with no issues, yet Mackster can't run that ROM because he's unable to type. I think it's possible that within the MT4G production run, there are slight H/W differences somewhere within the phone's internals. I mean, the problem occurs on almost every ROM for him (everything except RG). The problem seems a little more complex than a simple ROM bug.

This happens on my phone as well. Thought it was just me... it didn't happen on stock mySense, or RoyalGinger 2.1. I'm currently running RoyalGinger 3.0 & it hasn't happened yet. It DOES/DID occur on CM7 (nightly & stables), MIUI, Virtuous unity & virtuous fusion ...
I currently have a mt4g with the good screen & bad eMMC chip...
Sent from my HTC Glacier using XDA App

cbutt said:
This happens on my phone as well. Thought it was just me... it didn't happen on stock mySense, or RoyalGinger 2.1. I'm currently running RoyalGinger 3.0 & it hasn't happened yet. It DOES/DID occur on CM7 (nightly & stables), MIUI, Virtuous unity & virtuous fusion ...
I currently have a mt4g with the good screen & bad eMMC chip...
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
God damn dude, same exact situation as me. What are the odds?? Lol. Weird ain't it?
I have a new phone now with good eMMC and it doesn't happen nearly as much, but still happens a little.

mackster248 said:
God damn dude, same exact situation as me. What are the odds?? Lol. Weird ain't it?
Click to expand...
Click to collapse
I don't think it's chance. I think we're onto something here. On phones that have the touchscreen typing problem, it occurs on every ROM except for stock and RoyalGinger. So the question is, what's different about RG? What does it have in common with the stock OTA ROM?

I believe RoyalGinger should be considered stock for this discussion - because it's based on stock.
The pattern you're pointing to might mean that there are indeed some HW differences within MT4G production run, that are accounted for by the stock drivers, but aren't accounted for by other drivers.

Jack_R1 said:
I believe RoyalGinger should be considered stock for this discussion - because it's based on stock.
The pattern you're pointing to might mean that there are indeed some HW differences within MT4G production run, that are accounted for by the stock drivers, but aren't accounted for by other drivers.
Click to expand...
Click to collapse
How is it based on stock btw? Because isn't RG pretty much like 99% CM7? And I think he said his kernel is based off of Zinx's?

Jack_R1 said:
I believe RoyalGinger should be considered stock for this discussion - because it's based on stock.
The pattern you're pointing to might mean that there are indeed some HW differences within MT4G production run, that are accounted for by the stock drivers, but aren't accounted for by other drivers.
Click to expand...
Click to collapse
I think you're thinking of RoyalGlacier, which is based on mySense. RoyalGinger is an AOSP-type CM7-based ROM. I think you're right that this issue may be driver related. It'd be nice to figure out what's different about the stock and RG drivers, compared to all other ROM's hardware drivers.

TeeJay3800 said:
I think you're thinking of RoyalGlacier, which is based on mySense. RoyalGinger is an AOSP-type CM7-based ROM. I think you're right that this issue may be driver related. It'd be nice to figure out what's different about the stock and RG drivers, compared to all other ROM's hardware drivers.
Click to expand...
Click to collapse
I think for the purpose of testing we should roll back to a 2.3.3 build of cm7, because I never noticed this until a couple months ago.
Sent from my HTC Glacier using XDA Premium App

[Q] GPS always drops signal after ~5 mins of navigation

A while ago I rooted my AT&T HTC Inspire and put on Cyanogenmod 7.2.0, and things are all working quite well except the GPS. However, extensive googling and I've not been able to find something that exactly matches my symptoms. It always camps quickly, that's no problem. When it is connected, things seem fine and fast. However, each time I start driving navigation, after about 5 mins it loses the GPS signal and won't recover on its own. It will recover if I turn off the GPS and turn it back on. At that point we're back to normal but eventually it will happen again and it's quite annoying and unsafe to have to toggle the radio to keep navigation going.
I have tried several combinations of the RILs/Radio software found here: http://forum.xda-developers.com/showthread.php?t=1106324
However, there is never a behavior change. It is beginning to make me think maybe the problem is not with my radio software. Is there any kind of middleware as part of the ROM which may be causing this? Can anyone think of a way to troubleshoot bad hardware? I wonder if it is possible my baseband hardware was damaged through the modding process?
Thanks!

rpod83 said:
A while ago I rooted my AT&T HTC Inspire and put on Cyanogenmod 7.2.0, and things are all working quite well except the GPS. However, extensive googling and I've not been able to find something that exactly matches my symptoms. It always camps quickly, that's no problem. When it is connected, things seem fine and fast. However, each time I start driving navigation, after about 5 mins it loses the GPS signal and won't recover on its own. It will recover if I turn off the GPS and turn it back on. At that point we're back to normal but eventually it will happen again and it's quite annoying and unsafe to have to toggle the radio to keep navigation going.
I have tried several combinations of the RILs/Radio software found here: http://forum.xda-developers.com/showthread.php?t=1106324
However, there is never a behavior change. It is beginning to make me think maybe the problem is not with my radio software. Is there any kind of middleware as part of the ROM which may be causing this? Can anyone think of a way to troubleshoot bad hardware? I wonder if it is possible my baseband hardware was damaged through the modding process?
Thanks!
Click to expand...
Click to collapse
I believe that this is just a bug with the Navigation app on Cyanogenmod 7.x ROMs. It happened to me on every CM7 ROM I ran and I remember reading that it was the Navigation app's fault. But it's a normal bug, nothing should be damaged hardware-wise unless this happens on Sense or ICS ROMs that don't have documented cases of this issue.

MagicalHobo said:
I believe that this is just a bug with the Navigation app on Cyanogenmod 7.x ROMs. It happened to me on every CM7 ROM I ran and I remember reading that it was the Navigation app's fault. But it's a normal bug, nothing should be damaged hardware-wise unless this happens on Sense or ICS ROMs that don't have documented cases of this issue.
Click to expand...
Click to collapse
Thanks, MagicalHobo. Did you ever try a different ROM with success?

rpod83 said:
Thanks, MagicalHobo. Did you ever try a different ROM with success?
Click to expand...
Click to collapse
This is a common problem on AOSP ICS roms as well. I have read it is fixed on aospx, but the rom was too vanilla for me to keep it long enough to test.
As for Gingerbread, I can tell you that Navigation works perfectly on all ClearDroid roms as well as Virtuous Unity through 2.35, I can't remember using Nav on Gingerbeast.
Sent using the power of the dark side.

Please post all questions in the Q & A section. Thanks! Thread moved.
Sent from my Galaxy Nexus using Tapatalk 2

biglittlegato said:
This is a common problem on AOSP ICS roms as well. I have read it is fixed on aospx, but the rom was too vanilla for me to keep it long enough to test.
As for Gingerbread, I can tell you that Navigation works perfectly on all ClearDroid roms as well as Virtuous Unity through 2.35, I can't remember using Nav on Gingerbeast.
Sent using the power of the dark side.
Click to expand...
Click to collapse
From my experience, GPS works perfectly on aospx.

Flickering screen

Hey guys so I've got a huge issue. I'm on now my 3rd SGSIII and I'm getting very annoyed. My screen goes nuts randomly. I think I've found a fix, but I'm not sure what's causing it, as most people don't show the symptoms. My screen starts flashing and flickering, whether it's the lockscreen, the homescreens, within an app or in the app menu it does the same thing. I haven't taken a video of it yet, but will if someone wants to see what's happening. I've had it happen only on JB, both roms and stock doesn't seem to matter. The 'fix' is the same one as AOSP rom users use, which is to disable hardware overlay, however I don't know why a non-AOSP rom would need to deal with this. The roms I've used are: Vengeance, CleanRom, Synergy and The Executioner. I've gotten so annoyed that I've gotten Verizon to allow me to switch to the DNA if I want. I've taken a few Logcat's, if someone who can decipher them more than I can to figure out what's actually wrong would be great! I've taken a bunch of logcats, but only have one posted to pastebin. It was taken whilst I was having the issues. Thanks for the help guys!
http://pastebin.com/2SZkQGZJ

LlirasChosen said:
Hey guys so I've got a huge issue. I'm on now my 3rd SGSIII and I'm getting very annoyed. My screen goes nuts randomly. I think I've found a fix, but I'm not sure what's causing it, as most people don't show the symptoms. My screen starts flashing and flickering, whether it's the lockscreen, the homescreens, within an app or in the app menu it does the same thing. I haven't taken a video of it yet, but will if someone wants to see what's happening. I've had it happen only on JB, both roms and stock doesn't seem to matter. The 'fix' is the same one as AOSP rom users use, which is to disable hardware overlay, however I don't know why a non-AOSP rom would need to deal with this. The roms I've used are: Vengeance, CleanRom, Synergy and The Executioner. I've gotten so annoyed that I've gotten Verizon to allow me to switch to the DNA if I want. I've taken a few Logcat's, if someone who can decipher them more than I can to figure out what's actually wrong would be great! I've taken a bunch of logcats, but only have one posted to pastebin. It was taken whilst I was having the issues. Thanks for the help guys!
http://pastebin.com/2SZkQGZJ
Click to expand...
Click to collapse
is the show screen updates or something similar on in developer settings?

dragon1357 said:
is the show screen updates or something similar on in developer settings?
Click to expand...
Click to collapse
Nope, I don't run that stuff because all of the rendering updates and stuff can get annoying to look at while working. I'm able to get the same issues on a fully stock rom, and a pure flashed rom, with a few programs installed. But the fact that the hardware render seems to be the issue to me is just very odd on a non-AOSP rom.

I have been having screen flickering issues ever since I flashed the latest AOKP build (AOSP) I originally thought that it was because of the kernal and the under voting that I applied but even with a different governor and normal volt settings the screen still flickeres. After some poking around I figured you that it is only happening while I am trying to type and by uninstalling the Swype beta keyboard the screen flicker had been reduced to almost nothing. I do not know why the keyboard would amplify the effect but if I use the system keyboard the flickering becomes almost non existent.
Also, the screen flickers anytime a pop up menu is on screen, such as in the tapatalk app, the menu that pops up to allow you to quote someone..
Sent from my SCH-I535 using Tapatalk 2

Had been having the same issue on Baked Bean 6, flashed BB7 last night and it seems the problem is gone. BB7 being 4.2.1 I'm guessing whether intentional or not somewhere along the process of updating the "bug" if it indeed was as it appeared was squashed.
I'd be curious to know what was causing this, if by chance you find a definitive answer please post it.
Thanks

Lk
I had a very similar issue for a while, i flashed LEAN KERNEL
Rebooted twice, and problem went away.

For an update, I flashed kt's latest kernal and the flashing has ceased.
Sent from my SCH-I535 using Tapatalk 2

1.8 jellykang camera issues

hey everyone, first off thanks for all the awesome support documentation on how to get this phone running a new rom without having to post for help!
i tryed a few roms out there and really like the cm 10.1 based roms and the one i have had the least amount of issues with has been jellykang1.8 im open to trying again with other but the camera issues seemed to be worse at least to what i remember lol.
anyhow its been working pretty well with the exception of a couple things 1 is the camera. at first the camera button the the phone would only focus but not take a pic. after another wipe and reload it seemed to be working. now its doing the same thing again. another thing is the flash. when i use the flash it reboots the phone. i charge it all the way up and it seemed to work.. so i think its something with the charge level but im not sure
only other thing i have seen an issue with is the new google maps. seems to have rendering issue, like tilting back and forth the screen looks all crazy like the image is just way distorted and flickers alot and sometimes causes a reboot of the phone.
***UNLOCKED***
Doubleshot PVT SHIP S-ON RL
HBOOT-1.45.0013
MICROP-0353
eMMC-boot
Nov 21 2011,20:20:47
i am willing to head to a differnet rom i just have finally got settled into this one just wish it was a bit more stable, but rom alternatives are welcome as long as im not going to just run into the same thing lol
thanks
Tampoon.

Tampoon said:
hey everyone, first off thanks for all the awesome support documentation on how to get this phone running a new rom without having to post for help!
i tryed a few roms out there and really like the cm 10.1 based roms and the one i have had the least amount of issues with has been jellykang1.8 im open to trying again with other but the camera issues seemed to be worse at least to what i remember lol.
anyhow its been working pretty well with the exception of a couple things 1 is the camera. at first the camera button the the phone would only focus but not take a pic. after another wipe and reload it seemed to be working. now its doing the same thing again. another thing is the flash. when i use the flash it reboots the phone. i charge it all the way up and it seemed to work.. so i think its something with the charge level but im not sure
only other thing i have seen an issue with is the new google maps. seems to have rendering issue, like tilting back and forth the screen looks all crazy like the image is just way distorted and flickers alot and sometimes causes a reboot of the phone.
***UNLOCKED***
Doubleshot PVT SHIP S-ON RL
HBOOT-1.45.0013
MICROP-0353
eMMC-boot
Nov 21 2011,20:20:47
i am willing to head to a differnet rom i just have finally got settled into this one just wish it was a bit more stable, but rom alternatives are welcome as long as im not going to just run into the same thing lol
thanks
Tampoon.
Click to expand...
Click to collapse
Not the first mention of camera issues. Can't speak for anything else as it's the first and only ROM I've flashed and I've been quite happy with it, but I'm using SilverL's unofficial CM10.1 and haven't had any camera issues like mentioned. I've successfully used the flash well below 50% battery, at levels the stock phone wouldn't even let me use it. My camera button will still focus on half press, and take a photo on full press. The only thing I couldn't get to work was the new JB gallery/camera. It worked, but was much buggier between transitions (portrait/landscape and FFC vs main) and also my reason for trying to load it up, photosphere, didn't work.
Anyway, I feel like I got sidetracked. Not sure if I'm lucky or what, but yeah the Unofficial CM10.1 been using as a DD for a while now doesn't seem to have any camera issues I've found!

PsychoPhreak said:
Not the first mention of camera issues. Can't speak for anything else as it's the first and only ROM I've flashed and I've been quite happy with it, but I'm using SilverL's unofficial CM10.1 and haven't had any camera issues like mentioned. I've successfully used the flash well below 50% battery, at levels the stock phone wouldn't even let me use it. My camera button will still focus on half press, and take a photo on full press. The only thing I couldn't get to work was the new JB gallery/camera. It worked, but was much buggier between transitions (portrait/landscape and FFC vs main) and also my reason for trying to load it up, photosphere, didn't work.
Anyway, I feel like I got sidetracked. Not sure if I'm lucky or what, but yeah the Unofficial CM10.1 been using as a DD for a while now doesn't seem to have any camera issues I've found!
Click to expand...
Click to collapse
thanks for the reply.
i decided to take your advise and try out silverL's and it is working better the shutter button works as expected, and the new maps app is working correctly so far as i can tell. the flash issue causeing reboots is still happening but im thinking it definatly has something to do with the battery level. the first thing i did after loading the rom was to use the flash and it crashed only had like 25-35% battery level. ill keeo playing with it just wish there was a automatic block of that almost like the stock app but ill just have to keep an eye on it
i do really like the rom the only thing that im not liking as much as what the jellykang rom had was the messaging app, the look of the other one was i think dark theme and the dark theme toggle is broken on this app, i would love to just import the one from jellykang but i am not sure how to do that.
anyhow so far so good. thanks!

Tampoon said:
thanks for the reply.
i decided to take your advise and try out silverL's and it is working better the shutter button works as expected, and the new maps app is working correctly so far as i can tell. the flash issue causeing reboots is still happening but im thinking it definatly has something to do with the battery level. the first thing i did after loading the rom was to use the flash and it crashed only had like 25-35% battery level. ill keeo playing with it just wish there was a automatic block of that almost like the stock app but ill just have to keep an eye on it
i do really like the rom the only thing that im not liking as much as what the jellykang rom had was the messaging app, the look of the other one was i think dark theme and the dark theme toggle is broken on this app, i would love to just import the one from jellykang but i am not sure how to do that.
anyhow so far so good. thanks!
Click to expand...
Click to collapse
Glad to help, but I do find your flash issue weird. I tested this again last night multiple times, I think the lowest level I got to was 18% battery, and flash worked, pic took, and phone didn't reboot. Wish I had more to offer!

PsychoPhreak said:
Glad to help, but I do find your flash issue weird. I tested this again last night multiple times, I think the lowest level I got to was 18% battery, and flash worked, pic took, and phone didn't reboot. Wish I had more to offer!
Click to expand...
Click to collapse
well if thats the case then i really have no idea what it could be. i jumped in and did this test right after the rom past the setup and before it started loading all other 3rd party apps. im totally clueless honestly. maybe i should try a alt camera app see if that still crashes it. could it otherwise be the gapps im installing, looking at the rom thread it had a listing for the 2013 apps and 2012, i installed the 2013.. and when i installed the rom i reset everything. only thing i didint wipe was the sd card. so i dont know.

had this same issue..when i flashed jellykang...then i set d flash to auto...no more reboots...u can try this if u want...and if u still prefer an external camera...go for ucam from the play store

Carbon Rom Slow/Freeze

It freezes (seems like a freeze, is actually a slow crawl). It seems to happen if/when scrolling with the keyboard open (such as scrolling down during a google search/most common for me/). Close the keyboard and wait a minute and everything returns to normal. Not sure if this is related to 7/19 nightly and earlier, as i have adjusted my habits accordingly to compensate for the bug.

ws46290 said:
It freezes (seems like a freeze, is actually a slow crawl). It seems to happen if/when scrolling with the keyboard open (such as scrolling down during a google search/most common for me/). Close the keyboard and wait a minute and everything returns to normal. Not sure if this is related to 7/19 nightly and earlier, as i have adjusted my habits accordingly to compensate for the bug.
Click to expand...
Click to collapse
Why aren't you on a newer nightly? 1.8 release actually just dropped.
Does it happen on any other ROM?

arrrghhh said:
Why aren't you on a newer nightly? 1.8 release actually just dropped.
Does it happen on any other ROM?
Click to expand...
Click to collapse
I am on a newer build. This was happening to other people and since I couldnt answer on that thread do to lack of posts, just figured Id shed a little light on it. It did not happen to me on CM or Slim bean. Also not 100% certain it doesnt happen now, but as I said, Ive adjusted my habits to avoid the issue, since I like this rom. Maybe its been fixed already, but the guys in the thread were saying it was a freeze, but it was actually a near freeze type of slow crawl. And it would correct itself when keyboard closed.
Also, havent had the chance to thank you for your work. Very sad to see your no longer have a working Q.. Although the Epic is just as epic . Anyway, Thanks very much for your work.