Database Info

Touch screen problems with the Fuze

As of late, my new Fuze (the 3rd one, I exchanged the other ones out because they got kinda scratched up) has been showing poor performance. And then today, the touch screen just stopped working. It still registers the touch, but it's like no matter where I touch it can only go to one of the two soft keys. Has anyone else been having this problem?
I'm going in to switch it out again, but I'm really not sure if I want to keep using the Fuze...overall, it's slow, buggy, and the GPS is trash. I love the phone, but it's just not working.

Are you using the stock ROM or did you use one of the cooked ROMs? I have a Fuze (upgraded from a Tilt) and everything works fine on mine. I read that a lot of people are having issues with the GPS. I did initially --- I could not get any GPS connectivity. I ran HTP GPS Tool and everything worked fine after that. Even after I flash another ROM it works fine. I use TomTom and GoogleMaps regularly and even GoogleMaps can get a GPS lock within 1 minute.
You may want to check the settings for the TouchFlo. Download DiamondTweak and Advanced Config 3.3. They have settings to improve the sensitivity of the touch screen... maybe you need this or at least give it a try.
As for slow, I think this has to do more with the ROM. Since I got my Fuze, the first thing I did was flash one of the cooked ROMs (of course, after HardSPL ).
Good luck.

I'm using the stock ROM, I'm kind of scared to flash a new one. I did all the performance tweaks and it made a pretty big difference, but it's still kind of slow. I can live with it though. The GPS works occasionally, but it isn't nearly as strong as other phones I've used/seen. And the touchscreen problem has nothing to do with the sensitivity, I'm fairly positive it's broken. Like, when I touch somewhere on the screen, it registers the touch as far to the left as possible (ie. I'm trying to close a program or open the task manager and it registers the touch as pressing the Start button). It may have something to do with the fact that I cleaned the screen with a monitor wipe, although I would assume that that shouldn't affect anything. It's just such a coincidence though; I literally used the monitor wipe like 2-3 minutes before it broke or screwed up or whatever. And it's not a software issue. I hard-reset it and it took a good 20 minutes to get past the screen alignment (I think it just gave up on me and went to the next screen). I'm just going to exchange it out for a new one I guess, although I'd really prefer an Xperia X1 at this point (or any point I guess...I just don't want to spend 700 dollars on it)

allhalf425 said:
As of late, my new Fuze (the 3rd one, I exchanged the other ones out because they got kinda scratched up) has been showing poor performance. And then today, the touch screen just stopped working. It still registers the touch, but it's like no matter where I touch it can only go to one of the two soft keys. Has anyone else been having this problem?
I'm going in to switch it out again, but I'm really not sure if I want to keep using the Fuze...overall, it's slow, buggy, and the GPS is trash. I love the phone, but it's just not working.
Click to expand...
Click to collapse
Dude, I hear ya..... I'm getting the same issue, it registers touch etc, you press your home key it vibrates you softrest with button on back and it starts up and I know its booted WM as I can hear the windows startup sound, It's not the first time this has happened to me, one other time after flashing a cooked rom, It did the same thing then I managed to blindly navigate the device into the bootloader then reflash the device, the screen suddenly decided to come back on at the "tap to setup device" stage, you know with the screen alignment...., then I did like 2 hard resets, cause at the time I thought that this was something to do with it, then everything has been working good as gold up untill last night when I flashed the cooks latest version, it worked for a lil bit but in my messing around with the device, the screen switched off then stayed off, I've been trying the same process that I tryed before, but it's not working, maybe I should of did the 2 hard resets straight away rather then fart arsing around loading cabs etc...?, not sure, as I'm at a loss with this one... maybe it was just on it's way out, upto HTC heaven and there's nothing I can do about it ?, God, I hope not !!, MY next thing I'm going to try is load a stock HTC ROM onto the storage card, and maybe that will work...hmmm??, anyway...do you know anymore or are you at a loss as well ?... Oh BTW, I'm using a Touch HD, with a manilla 2.5, 6.5 ROM, from one of the popular chefs, (I'm not gonna publish the chefs name) as I think it's not really his fault....everyone else seems to be OK, so must be something else, I've wondered sometimes about the amount of writes available on some types of memorys having something to do with it, but it can't be that..?, something with the screen, I've noticed it happens when the battery is running real hot as well !!, anyway if ya find out something, I'm keen to hear as well, as no one seems to be answering my post about it.....

Frustrating Video Out/TV Out Behavior

Hi, everyone.
I searched for this and didn't find anything, but it's a little hard to know what to search for.
I use WunderRadio to listen to Internet radio. A few weeks ago, the Video Out (TV Out) screen started popping up at random times, usually when I was tapping something on the menu or on the screen. When it did, it was almost impossible to close and it really messed up my listening.
Some days it wasn't too bad. Sometimes, when it got really frustrating, a soft reset would stop it temporarily (or at least slow it down). When it was at its worst, though, nothing helped, and it was impossible to listen to WunderRadio.
It wasn't only in WunderRadio that this would happen--it would pop up occasionally in other applications, as well. But it was the most frustrating by far in WunderRadio.
I recently did a hard reset, so I only had a few applications installed. I first assumed that this was being caused by WunderRadio, so I uninstalled it. I still kept seeing that Video Out screen.
I selectively uninstalled applications and thought a couple of times that I had identified a program that was causing the problem. However, it kept coming back, seemingly regardless of what was installed or uninstalled.
A few days ago, this stopped happening. I haven't seen the Video Out screen a single time. I don't know if it has fixed itself (I doubt it) or whether it will suddenly reappear.
At this point, it seems like this could be due to faulty software, firmware, or hardware.
In July, I had a similar thing going on. I don't know if it was related to this or if this is just a coincidence. The phone all of sudden decided that it wanted to redial the last number called--over and over again! I would think I had it stopped, put the phone in my pocket, and get a call from a contact asking if I had called them. No, I hadn't, but my phone had!
As with the Video Out problem, sometimes a soft reset would help. Often, however, I ended up just having to turn the phone off for a few hours, then cross my fingers and try again.
With both of these problem, I was hesitant to send the phone in for warranty repair, because they were both so unpredictable that the repair shop would probably be unable to make either of these symptoms appear. My fears have since been borne out by the fact that both problems seem to have been solved--at least semi-permanently.
On the other hand, either or both of these problems could come back at any time!
Can anyone tell me what's going on here and what I can do about it?
Thanks in advance!

Are you using a wired headset? Maybe the pins are a little off and acting like the tvout cable USB pins and that's triggering it.
You should try to think if there is any correlation between a wire headset and this activity.
Also, do you actually use TV-out? You can just disable it entirely by a registry tweak so it won't be able to popup if that helps.
If you need anything further feel free to PM me since it's unlikely I'll find this post again

Good point! Yes, I am using a wired headset--most often when I'm listening to WunderRadio--which would explain why it happens most often when I'm listening.
I switched from headphones to earphones the other day, and that could very well be the reason it's no longer happening.

It's either the headphones or your USB port that's bad. But since you've said the problem has went away with new headphones, I'd say it's those. But it's a guaranteed hardware issue, although not necessarily the phone.

I had the same problem - TP would switch to TV Out mode randomly when mini usb was used (either charge or headphones). Mine needed a new usb socket, although I think theyyyyy jutssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssst swap the whole board. And I know it's off topic but can someone point me in the right direction to sort out my keyboard problem above?!

jjjacksonjjj said:
I had the same problem - TP would switch to TV Out mode randomly when mini usb was used (either charge or headphones). Mine needed a new usb socket, although I think theyyyyy jutssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssst swap the whole board. And I know it's off topic but can someone point me in the right direction to sort out my keyboard problem above?!
Click to expand...
Click to collapse
hehe does your keyboard repeat too quick? Settings - Personal - Buttons and reduce the repeat rates on 'up/down control'...on and stop eating so much candy while playing with your phone

Am I the only one having serious proximity sensor problems (hang ups)

this has gotten to be a real serious problem for me - hanging up with my face while on a call. i am surprised this isn't talked about more here. any help would be appreciated! is it possible for the dev's to not only remove the end call button but the mute as well?

so far you are the only one that has ever reported anything like that,ya know it could be a hardware defekt
sent via my bamfed out tbolt

Nope I'm in the same boat as im sure are many others. I have only ever had it actually impact me I think twice on phone calls out of almost a hundred or so that I have had since I purchased the phone. All the others times though it was extremely annoying to keep hearing the click sounds of the screen turning on and off on and off on and off etc.
I keep hoping for a software update that addresses the sensitivity of the sensor, but still no
I also wonder how much the battery is affected by the screen turning on and off repeatedly while in a phone conversation...

I get the same. More on my right ear than my left, but it will often take a digit that I just typed for an automated system and try to dial it, resulting in an alarm tone in my ear during the conversation.

sorry but i have 3 different bolts,the 1st one was rooted stock had that problem but it also went into the brick loop so it got replaced,rooted that one but never had the prob again,this one has the bamf 2 prev 3 on it and no probs that is why i suggested harware cause my first one had major hardware issues
sent via my bamfed out tbolt

i get it too. but i dont call so much. so i dont really care lol

I too had this problem, and did some quick searching on Google. Stumbled upon someone who said to spray it with canned air to clean it out. To my surprise, it worked. There is just enough room between the screen and the body of the phone for dust/crap to get in and it hinders both the light and proximity sensors.

You might be holding the phone in a weird position?
THUNDERBOLT

Damn, you lean something new every day, this thing makes phone calls too!

I've had the issue too recently. But it only started when I returned the last phone to stock. Before that, I had a small issue with it, but it didn't happen often.

pnd4pnd said:
this has gotten to be a real serious problem for me - hanging up with my face while on a call. i am surprised this isn't talked about more here. any help would be appreciated! is it possible for the dev's to not only remove the end call button but the mute as well?
Click to expand...
Click to collapse
I have the screen turn on during calls, but I've never had a face hang up. Honestly I think the screen turns on for me, but can't be interacted with.
Scratch that just did a test. I guess I'm lucky. Then again I don't hold the phone flat to my face. So I guess I would never hit it...

i have had hangups, the mute button pressed, and a 3 way call started. i just tried blowing the screen out with some compressed air as someone suggested. it seems better - will give an update after some testing.

No issues with hang ups for me. Had that problem all the time coming from the X.
Sent from B.A.M.F. 1.7 using Tapatalk

I have the same problem and have had it with every Rom I've run and stock. I'm surprised we don't have a way to adjust the proximity sensor yet, that's something I really miss about my Droid X.

After answering a call and putting the tb to my ear, my screen stays on.
Sometimes my ear dials numbers, sometimes the screen stays illuminated but doesn't respond to any touch! I have to toggle the screen on/off with the power button to get the touch response working again.

I have never had an issue. Been on mostly whatever the latest bamf release since rooting.

It happens to me whenever I forget the bluetooth especially after working out or anytime facial area is warmer then normal. I have a screen protector and clean the screen frequently.

I am having the same issue, so I called Verizon yesterday and they are sending me a new phone. I hope it works, because it makes talking on the bolt almost impossible.
Sent from my ADR6400L using XDA App

this is the first I am hearing of this. No problems for me.

Have the same problem...its really annoying man....will not get a refurbished unit until they fix the reboots

[Q] C/Would this cause my digitizer to stop responding?

I posted this almost verbatim to my G+ stream. It says it all, basically, and I don't have time (at work right now) to give a lot of detail but I wanted to get this out there...
----
I received three text messages this morning at 7:25 EDT.
They appeared to be random characters, like when an OS is trying to display characters from a language that requires a codepage it doesn't have installed. They are as follows:
<sisa:68571244:1:1:199:41970681>ezG7k3jzC7mFo6SSm7KUIg
<sisa:65471246:1:1:199:43800551>HE85MqRY33Xf0qmVbaCjyQ
<sisa:65471245:1:1:199:43799818>SpxSbHILo1mHG/EjkMAF2g
All three received at 7:25. I was able to use my phone up to this point because I was able to view the messages normally. Now, suddenly I have no digitizer response. None whatsoever. To use my phone, I have to pull the battery and boot to safe mode then use my trackpad and menu buttons to access certain features.
Now, it seems to me, the first part is like an address packet, maybe including a sequence number. The second part is like what I see when e.g. viewing the output of 'cat somefile.binary' in Linux. At first I thought it was spam from a foreign country, but now I'm wondering if this was some binary code received and interpreted by my phone. I wonder if this is possibly an android virus/remote hack? Is that possible?
I may wind up wiping the phone when I get home and have ability to back stuff up, but this is annoying, to say the very least.
-----------
Now, I did a little googling and it appears that it may just be that T-Mobile was trying to send an update to the phone (maybe the fact I'm on a custom ROM is why it borked). But has anyone had this or anything like it happen to them?
Thanks much in advance,
CJ

Update
It appears the digitizer fouling *may* have been a coincidence. Very odd how coincidences seem to keep happening to my electronics. Anyway, I'm about to wipe and reflash, see if it persists. If it was a software bork, it should be 100% resolved with a reflash. If hardware, it'll still be borky.
It is now intermittent, and I tapped the screen pretty firmly a bit ago and it started working almost reliably again. Sounds like a loose connection. Very odd coincidence.
Will update when decided for sure the cause.

cj chitwood said:
It appears the digitizer fouling *may* have been a coincidence. Very odd how coincidences seem to keep happening to my electronics. Anyway, I'm about to wipe and reflash, see if it persists. If it was a software bork, it should be 100% resolved with a reflash. If hardware, it'll still be borky.
It is now intermittent, and I tapped the screen pretty firmly a bit ago and it started working almost reliably again. Sounds like a loose connection. Very odd coincidence.
Will update when decided for sure the cause.
Click to expand...
Click to collapse
My evo **** needs a good smack every now and then when the kb gets opened because it has a bad flex cable. since I'm not with sprint and only test roms on that phone I don't need the kb anymore but sometimes the little one opens it
Sent from my myTouch_4G_Slide using Tapatalk 2

Yep, I'm not so lucky. I need the touchscreen more than the keyboard
Still, was on the phone for 45 minutes today talking with two different reps, and my replacement phone (another MT4GS in Khaki) is scheduled to arrive in three days.
Time to see if I can return it to stock. It's a hardware problem, so what ROM is on it shouldn't matter, but I don't want to give them any reason to balk.

[Q] Are these problems with cyanogen mod or the actual phone itself?

I'm pretty sure this is a hardware problem but I just want to make sure. I have an HTC Sensation 4G for T-Mobile (using Family Mobile) with Cyanogen Mod 10 installed. The problems I'm having are related to the touch screen. First of all, moving icons is really hard because it's like it doesn't detect that I'm still holding the icon. Thus, if I have an icon on the homescreen that I don't want, I usually have to first drag it up one row, then again and again until I get to the top to remove it. It also sometimes launches the app instead of moving it which is really annoying. The next problem is very similar to this one: whenever I'm scrolling through something (like contacts or a webpage, for example) the scrolling is kinda choppy and it sometimes takes a few swipes for it to actually scroll. It also sometimes opens links or the contact or whatever when I just want to scroll. Finally, long pressing is not reliable at all, it usually just considers it to be a tap. I literally spent like 1 minute yesterday just trying to open a link in a new tab before just giving up.
Oh yeah, I'm also experiencing trouble with the keyboard. Certain keys like "t" "c" and "f" are really hard to press. Whenever I try to type those keys in particular, it chooses the two keys on the sides instead (so if I type "f" it inserts "dg" or "gd" instead). I've installed a different keyboard which has kinda helped but it's still a problem because it slows down my typing to very slow speeds.
So basically, it looks like my screen is messed up, or I though maybe the processor is running too slowly to process the input or something like that. Looks like the screen though because I can sometimes identify "trouble spots" on the screen that cause the aforementioned behavior. Anyone else had problems like this before? I've heard that flashing the right radio can fix things like battery life and performance but I've never heard of something like this before. I bought the phone used on the internet so there's no way to get it repaired (besides paying for it of course, but that's not an option for me right now). The vibration also isn't working so I think it must have been dropped and that's why the vibration and screen are now messed up.

Ir0nMa1deN said:
I'm pretty sure this is a hardware problem but I just want to make sure. I have an HTC Sensation 4G for T-Mobile (using Family Mobile) with Cyanogen Mod 10 installed. The problems I'm having are related to the touch screen. First of all, moving icons is really hard because it's like it doesn't detect that I'm still holding the icon. Thus, if I have an icon on the homescreen that I don't want, I usually have to first drag it up one row, then again and again until I get to the top to remove it. It also sometimes launches the app instead of moving it which is really annoying. The next problem is very similar to this one: whenever I'm scrolling through something (like contacts or a webpage, for example) the scrolling is kinda choppy and it sometimes takes a few swipes for it to actually scroll. It also sometimes opens links or the contact or whatever when I just want to scroll. Finally, long pressing is not reliable at all, it usually just considers it to be a tap. I literally spent like 1 minute yesterday just trying to open a link in a new tab before just giving up.
Oh yeah, I'm also experiencing trouble with the keyboard. Certain keys like "t" "c" and "f" are really hard to press. Whenever I try to type those keys in particular, it chooses the two keys on the sides instead (so if I type "f" it inserts "dg" or "gd" instead). I've installed a different keyboard which has kinda helped but it's still a problem because it slows down my typing to very slow speeds.
So basically, it looks like my screen is messed up, or I though maybe the processor is running too slowly to process the input or something like that. Looks like the screen though because I can sometimes identify "trouble spots" on the screen that cause the aforementioned behavior. Anyone else had problems like this before? I've heard that flashing the right radio can fix things like battery life and performance but I've never heard of something like this before. I bought the phone used on the internet so there's no way to get it repaired (besides paying for it of course, but that's not an option for me right now). The vibration also isn't working so I think it must have been dropped and that's why the vibration and screen are now messed up.
Click to expand...
Click to collapse
Hi,
I found CM ROMS gave poor screen sensitivity .
Not as bad as you are describing,though.
Have you tried a Sense ROM?

I've never used this rom so I'm not sure weather or not this is a rom issue or not. You can find out by posting this question on their rom site. I have however had similar issues with other roms and the problem was solved once I flashed a different rom. What you can do for testing purposes is download another rom and see if there problem still persists. If it does than you know it's your device. If the issue is gone then the problem would be with the rom itself. Just because no one else is experiencing the issue it does not necessarily mean it's the device. I was using a rom once And had a lot of crazy issues going on. On the rom website they said it must be my device however after I installed a new rom all my issues we're gone never to appear again. So everyone's device is different. Do some testing and that will answer your question. Try out a couple of other roms, if the issue is gone than it was the rom. If it's still present with the other roms then it's your device. Good luck and I wish you the best. Hope this is helpful.
Sent from my HTC Sensation using xda premium

malybru said:
Hi,
I found CM ROMS gave poor screen sensitivity .
Not as bad as you are describing,though.
Have you tried a Sense ROM?
Click to expand...
Click to collapse
I'll try one today. I've held back from trying different ROMS because I don't want to screw everything up and be left without a phone for a few days. But now it's the weekend so I'll back everything up and try a sense rom.

malybru said:
Hi,
I found CM ROMS gave poor screen sensitivity .
Not as bad as you are describing,though.
Have you tried a Sense ROM?
Click to expand...
Click to collapse
I tried installing a sense rom but it didn't install correctly. I started the install and one second later it said it was done. When I rebooted it threw me back into Cyanogen Mod 10. Any ideas?

I have elegancia installed now, same problems. i'll be re-installing CM10 since it had some really nice features. I guess I'll just deal with it then.

The only possible solution i can think of is the ground pin.
Check this thread... and i hope it will help you..
http://forum.xda-developers.com/showthread.php?t=1239238
~HTC Sensation powered by Bricked AOKP milestone 6~