[Q] How to test screen? - EVO 4G Q&A, Help & Troubleshooting

I've got some issues with my Evo 4G, I wanted to pool from the vast knowledge source here on XDA and see if I can get some help.
My touch screen is currently going crazy. When trying to slide to unlock or answer calls sometimes it takes 5-7 tries to unlock. Unfortunately an unsuccessful attempt to answer a call declines the call.
It also seems as if there is a dead spot on my screen which happens to be right where you would select "free" "update" or "install" in portrait mode in the market. Other times while texting my phone will repeatedly try to press "t", or hold down "t" and give me the number "5", other times it tries to select text to copy or cut.
Sometimes while on one of my home screens it will act as if it is trying to use pinch zoom when I try to slide my finger across to another home screen. Instead it will shrink or enlarge the screen.
I found this in the star code thread for the EVO - ##33284# - Debug - Debug Menu – (Debug Screen, Test Calls, RC Data, HDR/1X Selection, Voice Privacy, DTMF Set, Korea Mode Set)
I can't find any option to debug the screen while in this menu though, did the 2.3 update change the feature?
Are there any utilities I can use to attempt to try and find out what's happening with this screen?
I'm currently running stock 2.3.3 (OTA), so I can't try any method that requires root.
The phone has some damage caused by me, so I can't take it back for warranty.
I also just put this phone back on my account so I have to wait 30 days before I could use TEP, if I wanted to swap out the phone through insurance.

Related

Recalling active application when coming out of sleep mode

Yesterday I was doing some exploring, on foot, using Google Maps on my TP2. What I would do was check Google Maps, get a satellite lock, plan the next few minutes' walking, then press the power button to put it in "sleep" mode. A few minutes later I'd repeat the procedure - take the phone out, press the power button to wake it up, go back into Google Maps, etc.
The problem was that when I put the phone in sleep mode, Google Maps was the active application, in the foreground; but when waking up again, Google Maps had been pushed into the background, and the phone was displaying the TouchFlo home tab instead. That meant that every single time I did this I had to go into the task manager and bring Google Maps back to the foreground again.
Is there a way to get the phone to automatically bring up whichever application was running when it was switched into sleep mode and not default back to the home screen?
This is one of my biggest gripes about the Touch Flo.
It just get's in the way of so many things.
Does this happen only if you manually put it into sleep mode, or does it also happen if the screen goes dark on it's own?
This is my biggest gripe. I want to stay in the application I left when the phone went into sleep mode. The funny part is the application is running for a split second right before TF default back to the home screen. Massively irritating. I like TF and all but I want to start the app I was running right when I put the phone in sleep / suspend. It's BS.
So, this explains why the phone defaults back to the home screen when I am in the middle of a call. It is not just that the phone wants to always be on the homescreen, but that the Touch Flo specifically forces its way "in front" of anything else that is running.
That gives me even more of a reason to want to upgrade from the T-Mobile ROM that my phone came with. I like Touch Flo actually but this has become so irritating that I would happily give it up so I can call my voicemail and enter passwords/delete messages without having to open the phone five times per call...
pinhead said:
So, this explains why the phone defaults back to the home screen when I am in the middle of a call.
Click to expand...
Click to collapse
That's starting to annoy me as well.

disabling notes for phone calls?

I was trying to call an automated voice system up today and was asked to enter my phone number in. I hit the "keypad" button and instead of the keypad opening up the Note application opened up. I had to click on the "ok" button in the top right corner to close that and to get back to the regular keypad so that I might enter my number in.
Is there any way to change this? I had an HTC TyTN II for two years and I never utilized the phone call notes feature on that phone. Given that, I'm very confident I'm never going to be using it on this phone and yet that's what first pops up when I hit the "keypad" button.
Any ideas as to what I can do to fix this?
You can set the phone to open Notes when in a call simply by pulling out the stylus. It is in Phone Settings- Advanced tab.
i understand your concern, occasionally my cheek would open up notes while on a call and type random stuff. I don't find it annoying enough to disable it but at the same time i've never used the notes during a phone call feature.
Dont know if theres a way of disabling it but maybe if u dig around in the register and search for "notes.exe" or whatever the notes app is named u might find something relative.

How to prevent accidental dialing?

Dear all,
Is there any way to add a confirmation dialog for the number I am dialing from my Touch Pro2? I have accidentally dialed a few calls when I touch the contact quick links on my home page, and when I scroll through the call history or my contact list. I notice that this is a common problem for quite a few people but I have not been able to find a solution. Note that I am NOT asking for screening locking.
Thank you very much.
Welcome to forums
I have never made an accidental call...
You can always block your device
This is not about blocking. I have S2U2 installed and there is no pocket dialing or anything like that. What I am talking about is that when I look through my call history, scroll through my contact list or quick contact links, my finger action may not be a perfect scroll action to the phone so it start dialing right away.
I am new to the forum and can not post links here but if you google "touch pro2 dial confirmation", or "touch pro2 accidental dialing", this is a common problem, at least to new touchphone users.
I'm not a new touchphone user, and I completely know/agree with what you are talking about.
thank god. I thought it was me. For the first two weeks of owning this phone I actually would tell people who called me or that I called "I just bought a brand new phone so if you get a phone call from me and I do not leave a voice mail, it it because I dailed you by accident, sorry". Pretty embarressing especially for a business phone.
It is my first touch phone, but still .....
When you are on phone, do not try to scroll through recent call, especially with the keyboard up. And do not try to do it one handed, where you use your thumb to scroll. It doesn't work for me. My thumb is terrible at scrolling.
I then I don't realize that I am already on the phone screen and press the phone button.
Really cannot figure out all the ways I accidentally call someone. And it has mostly stopped. But still ....
I can usually press "End Call" before it starts ringing on the other end. But I agree that since the scroll gesture, and pressing to select/call are almost the same gesture, there should be a confirmation screen. Or they should make a scroll bar on the side (but that might clutter things up).
I have the same problem, and the end call button is to slow to stop the call. Calling happens so fast that even if I press the end call button immediately it rings at least once.
I've had touch phones for years.... This is just something you get used to. It will happen regardless of whether you are using an Iphone, Windows Phone etc etc.
You just have to be carefull I suppose, no other way around it. You would get very tired of having to confirm EVERY call you make I would think. I dont get any "accidental" calls any more. I havnt for years actually. It's just a matter of training your gestures I would think. When scrolling dont push your finger on a contact and hold it there but start at the bottom or top of the screen and start swiping your finger down (or up) before your finger touches the screen. The only time you get a "accidental" press would be if you start by pressing your finger down and leaving it there a second or ending with your finger on a contact for a second or so.
I'm somehow able to leave my finger on a contact and swipe up or down and it doesnt select the contact untill I actually hold my finger there so. It must just be a way you guys are doing whatever it is you are doing.
That's my two cents though!
I guess people get over this problem sooner or later so xda-developers, who are certainly experienced users of touch phones, do not feel a need to add such a confirmation box.
Anyway, confirmation box is not the only way to prevent accidental dialing. For example, if pressing end-call in 2 seconds actually stops dialing, I do not mind waiting 2 extra seconds for each call. Right now, even immediate end-call cannot stop a call.
XavierGr said:
I have the same problem, and the end call button is to slow to stop the call. Calling happens so fast that even if I press the end call button immediately it rings at least once.
Click to expand...
Click to collapse
I just noticed something, in Advanced Config, under "Phone", there is an item "End Call Delay". Its set to 3 seconds by default, which seems like a long time to delay ending the call. I've just changed it to 1 second, and going to see how that works out.
Advanced Config is here, if you don't already have it:
http://forum.xda-developers.com/showthread.php?t=418151
I must have had at least 50 accidental calls in the last month. Everytime I scroll through my recent history it somehow takes it like I clicked on a number to call...
can somebody please make a fix where I can click YES OR NO right before I make a call.. or maybe a 5 second timer with a cancel button before a call..
thanks a lot!!
btw.
i had an android and i used to use google voice so it would prevent accidently calling someone
google voice app for android has a message that pops up when you make a call that asks which number to use for the call (google voice, or phone)
something like that would work nice
Another thing that might be worth considering is tweaking the amount of pressure required with a touch to simulate a click. If you can find a sweet spot where you're able to select an item when you need to, and scrolling is still possible, could be worth a look. I think I've seen reg entries or tweaking programs that cover this, though it is possible they were for different HTC models, and perhaps ours doesn't register varying amounts of pressure? In which case, is it possible to alter how long you need to press on an item before a click is registered?
Not an answer re. wanting call confirmation, I realise, but something to consider, possibly.
I have the same issue with accidentally dialing numbers. Android has an app, think it's called "Confirm Call". A similar Windows Mobile app would be appreciated and used by many.
The trick is, to apply even pressure to the screen when scrolling up or down. Try not to let your finger press and release to quickly.

Since updating to 4.0.4 I cannot dial pass 10-digits

Sorry if this has already been posted, I did a search and couldn't find anything.
Anyway, this is a new issue for me as I didn't have this problem before getting my OTA of 4.0.4 last week. When I was on 4.0.2, I didn't have this issue - but I do now that I am on 4.0.4.
My phone will let me dial the area code + 7 digits, but if I am required to input numbers after the call is connected (like when calling your credit card company) the dial-pad screen and phone shuts off as soon as I click the 1st number.
I then have to turn on the phone, swipe to unlock, go back into the phone dialer and do this for each number input.
Anyone else having this issue? Any ideas/and or suggestions how to fix, or at least a workaround until Google gets it fixed?
Not sure if this matters, but I am stock GSM/T-Mobile.
Thank you.
Bmerz said:
Sorry if this has already been posted, I did a search and couldn't find anything.
Anyway, this is a new issue for me as I didn't have this problem before getting my OTA of 4.0.4 last week. When I was on 4.0.2, I didn't have this issue - but I do now that I am on 4.0.4.
My phone will let me dial the area code + 7 digits, but if I am required to input numbers after the call is connected (like when calling your credit card company) the dial-pad screen and phone shuts off as soon as I click the 1st number.
I then have to turn on the phone, swipe to unlock, go back into the phone dialer and do this for each number input.
Anyone else having this issue? Any ideas/and or suggestions how to fix, or at least a workaround until Google gets it fixed?
Not sure if this matters, but I am stock GSM/T-Mobile.
Thank you.
Click to expand...
Click to collapse
This happens to me, however I only have to pull my hand away from the phone to bring it back to the dial pad.
I am guessing you have your phone set to lock "immediately" when the screen goes black (I have mine set to five seconds, so this does not happen to me)
What is happening (in my case at least) is an overly sensitive proximity sensor. It catches your hand, thinking you're putting the phone to your face, and darkens the screen. I have to be careful where I place my hand when I use the dialer after I am on a call (say, checking voicemail and entering password)
If your phone is set to lock immediately, try setting it to five seconds, and see if that helps.
This also happened on my GS2..
ingenious247 said:
This happens to me, however I only have to pull my hand away from the phone to bring it back to the dial pad.
I am guessing you have your phone set to lock "immediately" when the screen goes black (I have mine set to five seconds, so this does not happen to me)
What is happening (in my case at least) is an overly sensitive proximity sensor. It catches your hand, thinking you're putting the phone to your face, and darkens the screen. I have to be careful where I place my hand when I use the dialer after I am on a call (say, checking voicemail and entering password)
If your phone is set to lock immediately, try setting it to five seconds, and see if that helps.
This also happened on my GS2..
Click to expand...
Click to collapse
Thank you, I will look into my settings and change it. But as for the other thing, one has to have their hand on/near the dialer in order to input more numbers. Perhaps I can angle the phone and my hand in a way that the sensor doesn't see my hand over the dial pad. (What a PITA! lol)
Nonetheless, thank you for chiming in!

[Q] Lockscreen shortcuts seem to be missing...

Alright, so I was setting up my ls990 and during the setup of everything (apps/widgets/screens/you know) I managed, or perhaps my phone managed, to simply stop displaying lock screen shortcuts. I know what you may be thinking, no, there are no passwords, knock codes, pins, locks, mods, extras, or anything that *could* cause this.
It's a simple swipe to unlock, that's it, there are shortcuts 'set' in the lock screen settings as you'd expect, but no matter what fiddling, swiping, or press-and-holding I try will bring them back. Every last combination of settings and lock screen fidgeting and 'oops I deleted the default circle lock screen widget thingy but found out how to bring it back and also learned how to set the default lock screen page that will show when I turn the screen on'-ing will make them show again... So after on and off and mostly on playing around with it over the last 10 hours or so, and seeing how it is now 5 am where I live, and certainly the tunnel vision has set in or I'm just plain ol' dumb and/or incapable of swiping my own buttons, I'd figure that somewhere in the population of LG g3 owning & xda browsing intelligental(wo)mens there could be somebody to set my plain ol' dumb button pushing straight.
Any ideas?
Posting on the chrome browser from my nifty ls990 via my Wi-Fi connection, tanks.
Well anything? Need smart people please, I'll consider this a bump.
Do you see the Emergency Call box at the bottom? I just had that same issue, and it appeared to be triggered by a lack of signal or going into roaming mode. Setting the device into Airplane Mode brought the shortcuts back for me. Here's exactly what I did:
1. Set the device into Airplane Mode (I used the shortcut from the notification shade).
2. Lock the device.
3. Hit the power button to bring up the lock screen. Verified shortcuts were there.
4. Shut off Airplane Mode (once again, used shortcut).
Let me know if that works...

Categories

Resources