1. Scroll using touchflo to Messaging
2. select a message and choose MENU > REPLY from touch 3d screen.
3. Slide out keyboard and start typing
4. PROBLEM: it kicks me out of the text message and opens up into 'telus quick find' and continues typing what I started to type. (It boots me out of the text messaging application).
Anyone know why this is?
It shows my blinking cursor in the text messaging field.... just before it boots me out of the texting application.
Mine does this sometimes too, haven't found a cause and/or solution.
Another problem is that if I close the keyboard as soon as I press the send button, sometimes TF3D crashes.
I don't worry too much though, they only happen occasionally.
jusetan said:
1. Scroll using touchflo to Messaging
2. select a message and choose MENU > REPLY from touch 3d screen.
3. Slide out keyboard and start typing
4. PROBLEM: it kicks me out of the text message and opens up into 'telus quick find' and continues typing what I started to type. (It boots me out of the text messaging application).
Anyone know why this is?
It shows my blinking cursor in the text messaging field.... just before it boots me out of the texting application.
Click to expand...
Click to collapse
I have a similiar problem and I need to click the blinking cursor in the text field to "lock" it there. It went away after a hard-reset. Still do not understand why...
i think i can help
i had a similar problem today, my problem was it switched to landscape, in 1 second opens my dialpad then i have to close that and continue typing.
what solved my problem was installing a file called "RemoveSkcerts.cab" or something similar, sorry but i dont have it with me on my touch pro, hope this helps u out
When you hit reply, do you wait fully until the whole messaging screen pops up or do you do press reply, and immediately open up keyboard?
I used to have this problem until I realized that you should let the whole messaging screen come up.
keyboard closes
when I reply to e-mail or even SMS, when I hit the space bar (both in physical keyboard & SIP), the application CLOSES ! ! this just started happening.
CarlCastro said:
When you hit reply, do you wait fully until the whole messaging screen pops up or do you do press reply, and immediately open up keyboard?
I used to have this problem until I realized that you should let the whole messaging screen come up.
Click to expand...
Click to collapse
Exact issue i have
Yep, mine's been doing the same for a couple of days now... Stock T-Mobile ROM UK... Only had it a month, so haven't researched enough to change anything much.
I hit reply for the text, slide out the keyboard. I start typing and about 3 words into the reply it closes the SMS window and goes back to the main screen. It's fairly annoying as bugs go.
I hope this helps you work it out.
ciscossj2 said:
i had a similar problem today, my problem was it switched to landscape, in 1 second opens my dialpad then i have to close that and continue typing.
what solved my problem was installing a file called "RemoveSkcerts.cab" or something similar, sorry but i dont have it with me on my touch pro, hope this helps u out
Click to expand...
Click to collapse
probably removesdkcerts.cab
http://forum.xda-developers.com/showthread.php?t=362659
but this will change ur icons
so has anyone found an answer to this issue?????.......
remove sdkcerts file did'nt really help.......i'd really appreciate if someone can debug this....extremely irritating.........
tnks
Read post number 5
vvivek said:
so has anyone found an answer to this issue?????.......
remove sdkcerts file did'nt really help.......i'd really appreciate if someone can debug this....extremely irritating.........
tnks
Click to expand...
Click to collapse
Hi!
Post number 5 is correct.
When you hit reply, do you wait fully until the whole messaging screen pops up or do you do press reply, and immediately open up keyboard and start typing? This the cause.
I used to have this problem until I realized that you should let the whole messaging screen come up.
So let the messaging screen come up completely.
Hope this help.
udgn said:
Hi!
Post number 5 is correct.
When you hit reply, do you wait fully until the whole messaging screen pops up or do you do press reply, and immediately open up keyboard and start typing? This the cause.
I used to have this problem until I realized that you should let the whole messaging screen come up.
So let the messaging screen come up completely.
Hope this help.
Click to expand...
Click to collapse
tried this....i still have the same issue......tp inadvertently kicks out to either home screen, or in most cases the phone dialpad screen !!!!
i tried soft reset and then reply, then things are fine......mebbe this happns because the dialpad application does not really close properly???? although i don't really see it running in the background or anythin......the dialpad cannot run in the background......but this dos'nt explain why occasionally it kicks out to the home screen???
When ever I am starting to text my Fuze will go to the same screen as if you slid open the keyboard(email,message,favorites,web search,appointment,tasks,note,and contact) description of the screen. And sometimes it will also got to contacts or it will go to my keypad to my phone.....I am getting a little frustrated does anyone have any answers????? Help me!!!
You're in the wrong forum here guy; the Fuze is the Touch Pro, not the Touch Diamond.
thread moved
hope this helps
I have the same issue.. It seems like when ever I get a txt and push reply and the slide the keyboard out once I start typing it goes to the phone dial pad menu
This has happened to me a few times. It only happens when I slide the keyboard open before the text message reply screen is fully loaded. If I let the screen completely load and then slide the keyboard and start typing I have no problems. So just give it a couple of seconds before sliding the phone open. Hope this helps!
I'm pretty sure I GOT IT!!!!!
hondaguyjoe said:
I have the same issue.. It seems like when ever I get a txt and push reply and the slide the keyboard out once I start typing it goes to the phone dial pad menu
Click to expand...
Click to collapse
Honda I have a question for ya??? Do you have any form of voice command on your phone?????
I've got voice command disabled and I have this issue all the time. I basically have to start any text in portrait mode, wait a few seconds... and then slide open the keyboard and proceed as normal.
It sucks because if I'm looking at a text in TF3D and hit 'menu' and 'reply' then flip the keyboard open, I'll even have time to type a few letters before I'm looking at the stupid a$$ landscape TF3D screen. Then I have to hit 'Messages' and tap on the message to type my reply in the threaded view.
Would love to use a major function of my phone without having to hesitate!
tman1425 said:
This has happened to me a few times. It only happens when I slide the keyboard open before the text message reply screen is fully loaded. If I let the screen completely load and then slide the keyboard and start typing I have no problems. So just give it a couple of seconds before sliding the phone open. Hope this helps!
Click to expand...
Click to collapse
That's the way I've been doing it on my Sprint TPro. It's become second nature now so I don't even have to think about it any more.
Yep.
KCMatt said:
I've got voice command disabled and I have this issue all the time. I basically have to start any text in portrait mode, wait a few seconds... and then slide open the keyboard and proceed as normal.
It sucks because if I'm looking at a text in TF3D and hit 'menu' and 'reply' then flip the keyboard open, I'll even have time to type a few letters before I'm looking at the stupid a$$ landscape TF3D screen. Then I have to hit 'Messages' and tap on the message to type my reply in the threaded view.
Would love to use a major function of my phone without having to hesitate!
Click to expand...
Click to collapse
FWIW, I have this exact same issue and find it pretty annoying. Guess ya just gotta wait a few seconds before sliding open the keyboard...
I keep having this issue even on stock rom before root. everytime my txt hits either split message over 160, or i try tap the screen to change a word, it scrolls to the top of conversation and gets kind of annoying.
anyway to fix
No but using the hardware "B" key can get you back to the bottom really fast
Sent from a MikSupremed Shift
I'm not sure why this happens this way but just about every time I go to compose a new SMS, as soon as I start to type in the main text field, it puts up the 'select' cursor which is the little blue box that hangs over the 'W' key on the keyboard.
If I need to start typing and the first word starts with a W, I have to wait about 5 seconds for this cursor to disappear so I can then hit the letter. How the hell do I remove this and stop it from happening? I'm not sure what to look for in the settings but as of yet haven't seen anything. I'm on the latest version and it's been happening for the past few revisions.
Oh and I'm using Smart Keyboard Pro if it's possibly a keyboard issue and not the fault of Go SMS Pro itself.
[EDIT] I think the problem is that when I go to compose a new message, the cursor is blinking in the field to type but my keyboard isn't on the screen. When I click the field to get the keyboard to pop up, then it brings up the cursor which you'd normally see if you want to select text and/or past something from the clipboard. I just tested in Dolphin HD and this doesn't happen this way as the keyboard presents itself as soon as I click in the url field.
Hitting the phone icon on my home screen gets me only to a boring screen from which I have to hit the dialpad icon. Thus, two clicks to get to dial a call. Any way to get a shortcut or whatever so the standard Google phone handset gets to the dialpad with one click, as it does in my AOKP 4.1.1 ROM on my One S?
I have found a very nice widget, Simple Dialer Widget, which puts a mini-keypad on a home screen as a widget. Although smaller than the regular keypad it's plenty big enough to dial on, on the N5's big screen. But I'd still like to know if I can use the plain ol' Google handset. . . .
ecdy