3 issues I noticed with my e\/o

[lkillen]

Keep the wheel squeeking. That is where change comes from.

[jj14x]

Originally Posted by lkillen

One of the thing that the Swype and some other keyboards forgot was the collapse keyboard key. They assume you will be able to touch into a non-textual area. The keyboard goes down when you leave focus of a text receptive area.

Often you can find an area of the screen above the text window and touching it will throw the event to collapse. Lousey program design.

Pressing (and holding) the menu button will get rid of the keyboard too

[TREmp77]

Originally Posted by lkillen

One of the thing that the Swype and some other keyboards forgot was the collapse keyboard key. They assume you will be able to touch into a non-textual area. The keyboard goes down when you leave focus of a text receptive area.

Often you can find an area of the screen above the text window and touching it will throw the event to collapse. Lousey program design.

If you press the virtual back arrow button (next to the menu button) the keyboard goes away

[tx_dbs_tx]

Originally Posted by lkillen

One of the thing that the Swype and some other keyboards forgot was the collapse keyboard key. They assume you will be able to touch into a non-textual area. The keyboard goes down when you leave focus of a text receptive area.

Often you can find an area of the screen above the text window and touching it will throw the event to collapse. Lousey program design.

Originally Posted by gator352

I've run into a few situations where I couldn't tap in a neutral area without tapping something else. I agree the design is flawed and needs to be adressed.

Simply tap the "menu" key to minimize the on-screen keyboard. Press and hold the "menu" key when cursor is inside a text box to force open the on-screen keyboard.

[pinkbunniz]

A couple issues I've noticed and maybe someone can give me some hints as to how to fix them. I'm stock rom unrooted.

1. Sometimes when I set an alarm and it goes off when I'm on the phone it will keep beeping and I literally have to do a battery pull to get it to stop.
2. Also minor issue, how do I get voice dialing through my bluetooth? I can't seem to get it to work. I have a plantronics 240......do I need to have a bluetooth with A2DP technology?

Many Thanks!!

[lkillen]

Originally Posted by tx_dbs_tx

Simply tap the "menu" key to minimize the on-screen keyboard. Press and hold the "menu" key when cursor is inside a text box to force open the on-screen keyboard.

What is this crap with the over-sized front? How self-indulgent.

[TREmp77]

Originally Posted by lkillen

What is this crap with the over-sized front? How self-indulgent.

Plus swype doesnt work like that. Simply tapping the menu button just brings up the menu...its all about the back arrow next to menu if you want to force the keyboard down.

[jj14x]

Originally Posted by TREmp77

Plus swype doesnt work like that. Simply tapping the menu button just brings up the menu...its all about the back arrow next to menu if you want to force the keyboard down.

Pressing and holding the menu button minimizes the swype button for me (stock Sprint ROM)
http://forum.ppcgeeks.com/htc-evo-4g...ml#post2037304

Well on that not I've cam across an issue that drives me nuts. When I click on phone then touch some one i want to call the phone hesitates like 30-45 sec before calling. or when composing a text i start typing and nothing shows for like 30-35 secs. I'm running stock no root and I always hard reset after every update.

[lkillen]

Originally Posted by Raheinm

Well on that not I've cam across an issue that drives me nuts. When I click on phone then touch some one i want to call the phone hesitates like 30-45 sec before calling. or when composing a text i start typing and nothing shows for like 30-35 secs. I'm running stock no root and I always hard reset after every update.

pull out your SDCard and reboot the phone and see if it happens without the card