Related
Has anyone had a problem with the the Evo 3D not responding on games with touch points?
Here is what I am experiencing.
All emulators I've tried, and nearly all touch-heavy games have had problems. During game-play, the touch points become unresponsive for a few moments and then start working again; or not at all. Multi-Touch points.. like when you are running on Meganoid and jump, instead of still running when he hits the ground like he is supposed to, he just stops. And I have to repress the directional points to get him going again. This is a very big problem with Emulators as well. Though I did not experience this when I was using the EVO 4G.
Has anyone had this happen? And if so, if there a solution?
I have a Video of the problem. (can't post the link, of course) But it's on my YouTube Channel MatlockEvo.
Sorry for the poor quality in advance. Can't find my Tripod for the camera. Had to work with my Laptop's Webcam.
Well, I play Tapsonic on E3D and it has to be the most "touch heavy" games ever, like 1000 taps on the screen in less then 3 mins. It responds very well, I never had any problem at all. Maybe your device is faulty.
Went to Sprint yesterday and sat.. literally, I had their Lead Tech sit besideme.Heacted likehedidn't know what to do lol Showed him what i was experienceing, and let him play with my phone. Showed him the multi touch apps and how they would jerk and eventually stop working. Told him how I tested the Digitizer with the #*#*3424*#*# code. He questioned how i knew about it. Duh.. LOL
Anyway, we tried problem solving, and eventually concluded it was more than likely a software issue.
Before i went to Sprint, i told myself if I could not get the problem solved, I would go ahead and Root for CyanogenMod. Maybe that would help the issue.
I did a Factory Reset and started over, again. The first thing I did was download Meganoid, to see if, just maybe, this time it would work right..
.. and wouldn't ya know it.. I am having no issues at all with my touch points.
Matlock.EVO said:
Went to Sprint yesterday and sat.. literally, I had their Lead Tech sit besideme.Heacted likehedidn't know what to do lol Showed him what i was experienceing, and let him play with my phone. Showed him the multi touch apps and how they would jerk and eventually stop working. Told him how I tested the Digitizer with the #*#*3424*#*# code. He questioned how i knew about it. Duh.. LOL
Anyway, we tried problem solving, and eventually concluded it was more than likely a software issue.
Before i went to Sprint, i told myself if I could not get the problem solved, I would go ahead and Root for CyanogenMod. Maybe that would help the issue.
I did a Factory Reset and started over, again. The first thing I did was download Meganoid, to see if, just maybe, this time it would work right..
.. and wouldn't ya know it.. I am having no issues at all with my touch points.
Click to expand...
Click to collapse
I had some touchscreen probs today. I had a dead zone over the e, s, x, buttons that went from top to bottom. I couldn't use the touchscreen in that section whatsoever. I went to sprint, showed them the line drawing test using HTCs testing app (v1.0) and an hour later I had a new touchscreen installed. I recommend getiing it looked at. More than likely it's hardware related, but comes and goes, but will eventually go. That's my two cents. Good luck to ya!
Sent from my HTC EVO 3D using Tapatalk... Get in the 3rd dimension!
Hey guys,
I ve recently started having trouble with the Touchscreen on my Evo 3D. The phone is fully rooted and S-Off, currenlty has Leedroid ROM 3.0.
Ive noticed that sometimes it will just stop responding. I press the power button to turn the screen off and back on again, then it works fine.
Other times it will be as if the screen has already been touched in 1 place (even though i havent touched the screen). If i touch the screen it detects a second finger and tries to pinch zoom.
Recently its gotten worse and now certain parts of the screen wont work at all, but other parts work perfect. For example, i can pull the notification bar down or even use the capacitive buttons at the bottom (Home, Menu, Back & Search).
The phone has never been dropped, I have removed screen protector and case, removed apps, defaulted phone, tested different ROMs, and removed the battery for a while. Nothing has helped and im only surviving right now by using Softkeys.
Has anyone seen this, or know what it could be?
Haven't had this problem myself but something to try would be to calibrate thr screen threw the phone options snd see if that helps at all.
Locked & Loaded
""shooter on Deck""
Long time lurker, first time poster, so pardon the n00b.
I am having the same issue. I was using Revolution HD (which is a phenomenal ROM if I say so myself), and a week or two ago my phone started having that issue. I thought possibly a ROM issue, but things had been running smooth for awhile, so it seems odd that it would just start happening out of the blue.
I uninstalled apps, and wiped my phone and reinstalled the ROM, and nothing seemed to fix the issue. I finally re-locked my phone yesterday, put stock ROM back on and still had the issues. I took it in to Sprint today and they said it was because the phone had outdated software and they updated it. The only thing I saw updated was the PRL, so I'm thinking they are full of it. I should have checked for updates before bringing it in, because then they wouldn't have been able to bring that up as an issue.
They also tried to blame some apps as potentially the issue, but I'm basically at stock with minimal added apps. The apps I'm using are ones that I've used since I first had the phone. Perhaps an update of one of those apps is causing the issue.
I'm gonna run it on stock for a day or two and see if the issue is resolved by whatever update they did. I will then put HD Revolution back on and see what happens.
If you figure something out, please post again. My issues sounds exactly like yours. Doesn't sound like a ROM issue, since you and I are using different ROMs. Maybe a manufacturer defect, but I wonder if we have a common app causing the issue.
Update: Have tried the HTC Touchscreen Calibrator here:
http://forum.xda-developers.com/showthread.php?t=1378142
No change at first. Then i re-calibrated the screen but this time touched below the designated targets (purposely putting the alignment slightly out). Now im able to pull the notification bar down! Meaning it thinks im touching part of the screen where the notification bar is when in fact im touching just below it. "Touch Test" from the Market is a great app for testing this.
Could this be a fault with certain parts of the digitizer?
I know digitizers can be found easily enough and theres videos on youtube, but has anyone actually replaced one or think it will help???
@gonzodog: How is yours looking? Do you think you can give this a try aswell?
I downloaded the calibration tool and will test over the next few hours. My screen issue doesn't seem quite as bad as yours. Turning on and off the screen usually resolves the issue ans it doesn't happen all the time.
I went back to Sprint to show the update he ran didn't work. He 'thinks' it is an HTC issue. I am am looking for a good AOSP Rom to try to see if it is a sense issue. The Sprint rep said he has the same issues on his phone.
I am new to Android (coming from webOS) so I am not used to having so many options for an OS, so I don't know which ROM I'm going to flash.
I saw another post in this forum by someone with similar sounding issues, starting to think it really may be a software issue and not a defect in the phone.
I'll let you know how it goes after the calibration.
I have this issue lately no matter what rom I run.. been running custom rom's now for Month's and this just started..can't seem to figure it out..it just gets stuck and the notification window will not pull down or it will think I want to copy and paste during a text, do goofy things while dialing etc....then I have to hit the power button to simply turn screen off and on..then all is good again...seems to be getting worse and I have used every wipe, rom etc..not sure what to do.
Someone else suggested it was a multi touch issue. Could an app cause that?
I have very few apps on my phone, since I reset to stock. Maybe I will remove the the ones I have downloaded and see what happens. I want to think the issue is caused by an app, maybe one that was recently updated.
My non stock apps are: tapatalk, barcode scanner, google authenticator, tasker, words free, godville, ringcentral, yahoo fantasy football, SwiftKey x, and Google+. Do you all use any common apps?
Sent from my PG86100 using Tapatalk
I'm having this issue as well. I'm loving the change in sprint policy making me go to a repair center just to get the run around. It's a bit silly that they can't hand me a new one. I'm well within my year manufacturer warranty and have insurance. I'm hoping that this issue can be tracked down. From my perspective as a former cell phone repair tech, I'm banking on defective digitizers that are wearing out or wearing in a strange manner to produce this effect. I've tried multiple roms, sense and aosp and still have the problem.
I have an unlocked evo (no carrier) full stock and it happens to me too.. Specially the "o" and "i" letters on keyboard.. It doesn't always happens but when it does is just a matter of seconds till it's ok again..
Sent from my HTC EVO 3D X515m using XDA App
@gonzodog: I dont actually use any of the apps. Even when i flashed a stock ROM, the fault occurred.
This seems more and more likely that its parts of the digitizer at fault....
This was the reason I went back to stock s on was having loads of problems
Sent from my HTC EVO 3D X515m using XDA Premium App
@ronin201085 If it is the digitizer, then the question is how to get Sprint to replace it. I may try a different Sprint store today and suggest a digitizer issue. I have insurance, so my preference would be fore Sprint to repair it. I did see that replacement digitizers are available via ebay for about $20, but I'd rather not pay to fix something when I have insurance.
honestly if you are covered under insurance then have they repair it for you... its too risky to replace the digitizer yourself, especially seeing as there are no good tear down videos available that show us how to separate the touchscreen and digitizer from the main body... suffering from the same problem
I have the same problem man.. sprints customers service blows, I have taken it down there twice and they still wont do anything because I can't "duplicate" the issue. And also, for me turning the screen off and on fixes the issue.
Sent from my PG86100 using XDA App
Same problem here. Took it to my local sprint store and they replaced the screen no questions asked, although I did have to unroot it before they would touch it. The way I showed them that the defective digitizer was the culprit was downloading the app touch test from the market. That got their attention. A whole section of my screen wasn't registering input.
@3vo kid: I really don't care to replace myself, but I have taken it to Sprint twice, and both times they said it was a software issue. I was able to replicate the issue in the store, still didn't help. I am going to try a different Sprint store, and if still a problem, maybe a call to customer service.
Sent from my PG86100 using Tapatalk
I work for an indirect dealer fixing Sprint phones and I can guarantee you that it is the digitizer. HTC really did disappoint with these crappy digitizers. Whats more sad is that sprint does not rule this as a common problem when it truely is.
Ok for starters im in Australia and this phone was an import, so sending it back under warranty is a loooooong process, so im open to ideas.
I know digitizers are easy to get, especially on ebay, there must be people that have already replaced them. Im engineer by trade so my technical skills arent bad. Im seriously considering just trying to replace it myself.
ronin201085 said:
Ok for starters im in Australia and this phone was an import, so sending it back under warranty is a loooooong process, so im open to ideas.
I know digitizers are easy to get, especially on ebay, there must be people that have already replaced them. Im engineer by trade so my technical skills arent bad. Im seriously considering just trying to replace it myself.
Click to expand...
Click to collapse
there are deff ppl that have replaced them... but no one has posted sufficient information, pics, or videos when replacing the screen. to my understanding the digitizers are attached to the lcds with an adhesive and there are ribbon wires that get in the way of removing them. in all seriousness it might be easier to order a replacement digitizer with an lcd already attached
Ur digitizers are dirty ... put you phones in boiling water .. should fix it
Sent from my PG86300 using XDA App
Hello,
I'm looking to figure out if anybody has found a software fix for the issue of screen backlight flickering on our phones. I've hunted down some threads through Google, but found nothing except 'go replace your phone and hope for the best.'
As a reminder, when grays are displayed onscreen (as in Play store loading screen), it seems as though the screen refresh rate can't 'keep up' with those colors. To me, the problem is even more noticeable when viewing pictures in the Gallery - seriously, I feel like I'm watching one of those 3D movies, and my eyes and head start to hurt! It's just enough that it drives me crazy, but other people do also seem to notice it, so I'm not just ACTUALLY going nuts. This problem showed up on stock before I rooted and went MeanROM, so I know it's not my fault. The problem is worse at higher brightness levels, and persists even with manual brightness settings on.
So yeah, anyone else have this problem? Any stories of successfully resolving it? I'm still within my Sprint 30-day replacement period, but already got 3rd-party insurance on my phone, so it'll be interesting to try to get a replacement phone insured under the same policy...
Yep have had this problem for a while now and actually got tired of it this morning and will take my phone back for a replacement whenever I have time! Gets so annoying especially noticing it in the littlest of places.
Sent from my EVO using xda premium
Hmm.. I never really noticed it until you pointed it out..
Sent from my EVO using xda app-developers app
drmclove69 said:
Yep have had this problem for a while now and actually got tired of it this morning and will take my phone back for a replacement whenever I have time! Gets so annoying especially noticing it in the littlest of places.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Whoa, please let me know if your replacement is any better after a day or two of playing with it. I will probably do the same if there's an improvement.
Was on meanROM 4.2 until today, when I relocked and unrooted in preparation for getting a replacement at Sprint (I'm still within my 30 days). I was going to replace the phone because of this exact problem - a weird, barely-perceptible strobe effect when viewing grays and looking at certain photos in the gallery. And now - after all the hard work of finding an RUU for 2.13, figuring out the android SDK, learning how to use ADB (not to mention the whole initial unlock/twrp bootloader shebang) - I find that the screen flicker has dropped off. OK, sometimes there's an extremely brief (~150ms) hint of it all on a gray screen, but absolutely nothing compared to the headache that it was before. I'd recommend completely unrooting/relocking your phone and pushing the correct RUU. QBking77's the best for it - look up his youtube vids on android sdk intstallation/usage, then relocking your bootloader, then unrooting/installing an RUU. Remember to clear your Google Wallet first, and set your fastboot to off (under power settings). After relocking your bootloader, you might notice that you cannot boot past it. That's fine; just push your RUU with fastboot USB. You'll know what I mean after watching the vids.
After all that, if your results were like mine, you'll know it actually had something to do with your custom ROM. I have no idea how that is possible, as I seem to recall a flickering in my stock ROM, too, but I guess I was wrong. Perhaps it has something to do with my charge status, and I'll see the issue come back... who knows?
For relocking/unrooting
Step 1: Android SDK setup
Step 2: Relock the bootloader
Step 3: Unroot/Push RUU (for some reason, I had to go straight to pushing RUU from step 2 without booting into any ROM).
From all my scouring online, though, I've noticed that the people most consistently hammered with this problem (especially on screens other than photos in the Gallery or gray colors in the battery histogram of power settings) have build issues with their screens. These include light leak seeming to emanate in bands fanning up out of the home 'button' or graphical issues. These people usually report a fix to the problem once they receive a replacement; the ones with my problems typically complained of having received up to 3 (!) phones in a row with the maddening flicker, suggesting a software issue. It seems that the HTC One X itself was plagued with these problems, with graphical glitches also entering the mix, but an OTA fix a month ago or so minimized issues.
Lemme know how things go... I still have 4 days or so to return my phone if the flicker comes back, haha.
I had to get my phone replaced. sadly for me it was a hardware failture. check google maps and see if it the graphics flicker there, of if the background on minecraft main screne flickers in and out
Spyderekz said:
I had to get my phone replaced. sadly for me it was a hardware failture. check google maps and see if it the graphics flicker there, of if the background on minecraft main screne flickers in and out
Click to expand...
Click to collapse
Yeah, woke up this morning and problem was back in full force. I think it might be charge-dependent or temperature dependent (which makes sense if its an analog hardware component like a voltage regulator that's being futzy). I ended up replacing it, too, but Sprint charged me a bull**** $35 because I bought the phone at third-party reseller instead of a corporate store (god... damn... it). Anyway, my new (and refurb, btw) unit has absolutely no problems. Zero. Rooting and reinstalling meanROM now, haha. At least the store people acknowledged that they could also see the problem. Software scans turned up absolutely nothing, although Sprint says HTC does not allow them to open things up because it's a unibody phone, so it's still possible that my regulator was faulty.
Anyway, seems to me that it's a hardware problem having to do with a particular batch of phones. Strange, since my new phone is a 0003 hardware revision, just like my last...
Went today for my 3rd time trying to get a replacement because of this issue and not to mention I got denied a replacement when I was in my 14 grace day period I went in 2 times after that today being the 2nd and I asked for a replacement, I then have to wait for the "tech" to look at it...waited 1 hour to get told it phone has no problems we ran all the tests and passed, me really confused asked her do you even know what the problem is? She replies no....I then am like WTF. I tell her about my issue and try shwowing her and somehow doesn't notice it. Then asks 5 other people and they notice it and then they replace my screen? After I wait another hour (caused me to be late to work) then once done it actually fixed the problem completely, go home to find out she broke my speaker and my sd card won't mount! Drop it off and picked it up and all is fixed. I know want to terminate my contract cuz sprint has been giving me Shi**y customer service since day one! Someone who works at sprint plz help me!
Sent from my EVO using xda premium
Hi everyone. Thank you for reading.
I am posting for help with a friend's phone. I, personally, have an S3 on Sprint and haven't had much experience with T-Mobile phones. He has rooted his S5 (T-Mobile, obviously) using galaxys5root.com (I'm now not fond of that site due to his bad experiences that consistently happen) and has not put a new ROM on yet. It has been successfully rooted for several weeks, but today he went to text someone a response and the screen went black, and the blue notification light breathes. It also does a light vibrate, like when you are turning it on. He's getting a replacement anyway, but we want to unroot it before sending in the defective device. I'm wondering (and to my knowledge it seems like) if it's a boot loop. Nothing shows up on the screen at all, not even the back light is coming on. I have yet to connect it to Odin to see if anything comes up. I'm just seeing if this has happened to anyone else and if they have figured out a way to resolve it. My suspicion is that there's a problem with either the boot sector or the recovery sector, as it does not go into recovery.
Any insight would be much appreciated. Thanks again!
caderyn19 said:
today he went to text someone a response and the screen went black, and the blue notification light breathes. It also does a light vibrate, like when you are turning it on.
Click to expand...
Click to collapse
It sounds like the LCD display has gone bad if the vibration and blue light function normally but you cannot see anything ever.
When they get the new device you might want to suggest that they follow the rooting instruction in this forum on XDA instead of going to a website to do it. Just my opinion.
We are thinking the LCD is bad as well, it just feels like a boot loop because the light vibration keeps happening (I forgot to mention that). Sometimes the blue light will go out and the phone will vibrate lightly and then the blue other starts breathing. It's just repeating that non-stop. I had to pull the battery.
As for him rooting through here, I told him to with his S4 and S5 but he didn't listen. The S4 took a crap, and now the S5 took a crap. I told him I think it's that site. The method is correct but who knows where those flash files come from... I've never had any issues rooting through here, just an occasional reset here and there, nothing as major as this.
caderyn19 said:
We are thinking the LCD is bad as well, it just feels like a boot loop because the light vibration keeps happening (I forgot to mention that). Sometimes the blue light will go out and the phone will vibrate lightly and then the blue other starts breathing. It's just repeating that non-stop. I had to pull the battery.
As for him rooting through here, I told him to with his S4 and S5 but he didn't listen. The S4 took a crap, and now the S5 took a crap. I told him I think it's that site. The method is correct but who knows where those flash files come from... I've never had any issues rooting through here, just an occasional reset here and there, nothing as major as this.
Click to expand...
Click to collapse
Normally, even in a boot loop you see the initial Galaxy splash screen when it first starts booting. Then you see it over and over again. If you see nothing, it normally means the LCD is bad and unfortunately it's the most expensive part of the phone.
Good Luck with it.
If I've been helpful, please hit the thanks button.
That's what I figured... Thanks for your help! (I hit the button )
caderyn19 said:
That's what I figured... Thanks for your help! (I hit the button )
Click to expand...
Click to collapse
Wouldn't surprise me if the device is rebooting itself trying to fix a hardware fault. Might be detecting the LCD has stopped forcing itself to reboot.
But yeah, stick to XDA from now on We are good people here Welcome to the family!
Lol I've been part of the family for years now... I've always come here first for any android help, and have always found just what I'm looking for!
caderyn19 said:
Lol I've been part of the family for years now... I've always come here first for any android help, and have always found just what I'm looking for!
Click to expand...
Click to collapse
Well get your friend over here too!
Sent from my SM-G900T using Tapatalk
Seems I posted this to the wrong area, hard to find this section from mobile..
I've gotten a couple of random reboots while playing games, not enough to be super concerning but enough to make me want to figure out what's going on.. Anyone else seen this issue? I think it has only happened during bomb squad but I'm not positive and its likely just coincidence..
It just happened to me during Netflix. Are you rooted?
noneabove said:
Seems I posted this to the wrong area, hard to find this section from mobile..
I've gotten a couple of random reboots while playing games, not enough to be super concerning but enough to make me want to figure out what's going on.. Anyone else seen this issue? I think it has only happened during bomb squad but I'm not positive and its likely just coincidence..
Click to expand...
Click to collapse
mine shutdown when I was trying to login to dead trigger 2 with an "unknown account" it didnt reboot I had to power it on its kinda concerning cause Ive heard of ppl's shield rebooting but not completely shutting off like mine did.
Hasnt happened yet so it could be a dead trigger 2 bug with the console.
crowruin said:
mine shutdown when I was trying to login to dead trigger 2 with an "unknown account" it didnt reboot I had to power it on its kinda concerning cause Ive heard of ppl's shield rebooting but not completely shutting off like mine did.
Hasnt happened yet so it could be a dead trigger 2 bug with the console.
Click to expand...
Click to collapse
Mine just keeps freezing while playing mupen64. then, it goes to this poltergiest screen. happens every hour if im playing a game continuously. Should I return it? I see a lot of people having reboots, but has anyone seen this before? I think I should probably return my shield pro.
postimg . org / image/tz7epmvml/115c7ef9/
I happened yesterday, I froze the image that way, I am root
HeroofTime92 said:
Mine just keeps freezing while playing mupen64. then, it goes to this poltergiest screen. happens every hour if im playing a game continuously. Should I return it? I see a lot of people having reboots, but has anyone seen this before? I think I should probably return my shield pro.
postimg . org / image/tz7epmvml/115c7ef9/
Click to expand...
Click to collapse
if your rooted i found going to bootloader menu and doing "fastboot -w" will stop random reboots.