Sometimes when writing a text message, my FN button doesn't work. I press the FN button and I get the FN icon in the status bar but when I go to press another key I don't get the FN version of that key.
To remedy the situation i have to flip close the phone, open the software keyboard and then flip open the phone again and then the FN function works properly.
Is there anyone else having this problem?
Do you have a Desire Z, or a G2? Are you running a different rom or keyboard? Has it always done this?
Sent from my SilverBullet "HTCDesireZ running CM7"
Desire Z - Stock ROM (in my sig ) Stock keyboard
vinokirk said:
Desire Z - Stock ROM (in my sig ) Stock keyboard
Click to expand...
Click to collapse
We using XDA on our phones can see sig's for some reason:O But as to your problem, I have never had it. Ever done a factory reset to it?
Sent from my SilverBullet "HTCDesireZ running CM7"
Nope never done a factory reset, its our lasses phone like, so she doesn't really want to do a reset....if possible
Yuh, FRing is a pain in the ass. But it can make the phone like new again. Sometimes it's all that's needed
Sent from my SilverBullet "HTCDesireZ running CM7"
i had that problem before
was it only with one messaging app? cause usually it works with every other app but that one
i was using handcent if its only that one app
but to fix it i flashed another rom and its been working great ever since~
hope you gets your fixed too
Let my try.... your'e using Handcent? I've the same problem and lot of people too. It started since the mid-march update. The only solution I foud is to hit the symbol button and then click back. If Handcent do not fix this soon, i'll surely change my messaging app...
Now that you mention it, it did start around that time for me. I have since switched to GoSMS and they have released their premium app for free and retired their previous free version. Check them out! Looks and feels exactly the same as Handcent but without the keyboard issues.
I have the same problem. I fixed it by installing another keyboard.
I think it has something to do with the HTC keyboard...
Related
hi
i have a problem with my nexus one cm6. let's say i'm enter to a game and pressing the back button so it goes to the main screen of the phone to the one with the clock. it was before that when i preesed the back button going to the an screen of the application's or let's say one screen before the game and these was the man screen of the application's so how get t back how it was before?
thenks!
What?
(10chars)
cymru said:
What?
(10chars)
Click to expand...
Click to collapse
I'm guessing he means that before he installed CM6, when he pressed the back button mid game it would take him to the homescreen, however it now takes him to the application he was using before starting up the game (Again this is a guess). Isn't this normal behaviour or have I become too accustomed to custom ROMs?
For example, you start the email app, download a document which then opens in whatever office suite. Once you press back enough times to exit the app you return to your emails. Doesn't stock froyo work like this
Hollow.Droid said:
I'm guessing he means that before he installed CM6, when he pressed the back button mid game it would take him to the homescreen, however it now takes him to the application he was using before starting up the game (Again this is a guess). Isn't this normal behaviour or have I become too accustomed to custom ROMs?
For example, you start the email app, download a document which then opens in whatever office suite. Once you press back enough times to exit the app you return to your emails. Doesn't stock froyo work like this
Click to expand...
Click to collapse
This is my understanding as well (of both the OP's verbal diarrhea and of how Android works).
I think its the other way around...
Since installing CM, his back button seems to be returning him to the home screen (the one with the clock, as he puts it), instead of just backing up a screen...
Sent from my Nexus One using XDA App
yes danger-rat explain me very good!
if i'm enter to astro from the main screen of application's and doing back it's brong me to the homescreen!not to the main screen of the application's
Yeah, I though that was the problem, but I'm not sure I can help. As far as I know, the back button cannot be configured.
Since the back button now acts like the home button, you could try configure the home button to act like the back button? Lol...
The best suggestion I have would be to wipe and reinstall CM6. This isn't normal behaviour, so you've possibly got something corrupt...
Sent from my Nexus One using XDA App
yeah...but these is after the new instalation of the new cm6...actually it's from the cm5.0.8
Still, it's not behaving like it should. A wipe and reinstall may help...
Sent from my Nexus One using XDA App
that's the only option?because every time that i changed my rom i did wipe already
What rom exactly are you running? CM 6 Stable or one of the nightly builds? I know that there is an option in the newer nightlies that a longpress on the back button with kill the app.
"Common: Kill foreground app by long-pressing back - Evan Charlton"
Link to changelog: http://github.com/CyanogenMod/android_vendor_cyanogen/blob/froyo/CHANGELOG.mkdn
i'r running CM 6 Stable the latest one
so my only option is just to install again the cm6(after wipe)?
Anyone else have issues with their Delete key? It seems I have to hit it twice to get it moving. I can type very fast and smooth with easy button presses, but the delete key seems to be a PITA.
dnalevelc said:
Anyone else have issues with their Delete key? It seems I have to hit it twice to get it moving. I can type very fast and smooth with easy button presses, but the delete key seems to be a PITA.
Click to expand...
Click to collapse
Don't have any problems here with any keys (that I've found so far). Is it a case of since its a little more difficult to get to (upper right) corner that you don't realize you are not pressing it the same way as the other keys?
Just a thought.
No problems here
Never had that problem.
Sent from my PG06100 using XDA App
Hard keyboard or virtual? I haven't had that issue with either. Off topic, but my spacebar on the landscape virtual is a pain, I always end up hitting the b or v.
Sent from my HTC EVO Shift 4G using XDA App.
wardfan220 said:
Hard keyboard or virtual? I haven't had that issue with either. Off topic, but my spacebar on the landscape virtual is a pain, I always end up hitting the b or v.
Sent from my HTC EVO Shift 4G using XDA App.
Click to expand...
Click to collapse
If you're not using a custom keyboard, have you tried calibrating your keyboard at:
Menu-->Settings-->Language&Keyboard-->Touch Input-->Text Input-->Calibration Tool
(Interestingly enough, Calibration tool is only available if you hold the phone in Portrait and not in Landscape)
Yeah, that was the first thing I tried. I'm going to try it again. Coming from the Hero and having the tight sliding due to my case, its going to be hard to get used a the hard keyboard again. It is weird that the calibration only works in portrait or w/e you call it, the Hero was the same way.
Sent from my HTC EVO Shift 4G using XDA App.
i think it might be that I'm just not hittin it right. I was typing last night and when I hit delete it worked right away. I just might be hittin it off center.
I'm on nightly 14 and sometimes when I'm typing on the keyboard, certain keys send me to certain shortcuts. Sometimes the keyboard will act normally, other times "s" sends me to calender "w" to my contacts which forces me to use the on-screen keyboard. Which I hate! Other keys open other apps.
How can I fix this? Thanks for any input!
Sent from my HTC Vision using XDA App
Have you ever installed any other keyboards onto your phone?
Not after rooting =/
Sent from my HTC Vision using XDA App
durps said:
I'm on nightly 14 and sometimes when I'm typing on the keyboard, certain keys send me to certain shortcuts. Sometimes the keyboard will act normally, other times "s" sends me to calender "w" to my contacts which forces me to use the on-screen keyboard. Which I hate! Other keys open other apps.
How can I fix this? Thanks for any input!
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Happened to me a while back really weirdly. Just do a reboot, fixed it for me.
Yeah a reboot fixes it, but rebooting 3-4 times a day because of a keyboard issue isn't cool lol.
Sent from my HTC Vision using XDA App
durps said:
Yeah a reboot fixes it, but rebooting 3-4 times a day because of a keyboard issue isn't cool lol.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Hmm happening that often? That's really weird. It has happened to me once in an entire month of using nightlies.
I tried a suggestion that I was told on another forum and it worked!
Just apply a shortcut to each of the quickkeys on the hardware keyboard and you're set! hasn't happened all day, stoked!
Hi all!
I'm starting a new thread about my problem because the two other ones i found did not give me any answer or clue. They are (at least) 2 months old and there's no news about that.
The old threads can be found here:
http://forum.xda-developers.com/showthread.php?t=885271
http://forum.xda-developers.com/showthread.php?p=12798131
I have this problem: When I try to write a text message with the physical keyboard, the screen start to "scroll up" in the conversation after a couple of seconds.
After some tests, here's what I can tell about the problem:
-I use HTC Sense messaging app
-Screens jumps a little bit IF i slide out the keyboard AFTER selecting the contact
-It can't be the trackball to me, (lot of people are saying that it is trackball related) because if you try to "scroll up" or down with the trackball while typing a message, it do not scroll the whole page, but only between your message's lines.
-Sometimes, it scrolls the page up AND unselect the message box, so pressing "delete" will offer you to delete messages (instead of deleting the last character you wrote), and some keys open a new message, etc.
-I tried with "Touch Input" and Swype as the software keyboard and it seems to be unrelated to the software keyboard (I get the problem with both of them)
-It seems to happen to me in EVERY conversation (even conversations with less than 50 messages, contrary to what some peoples says)
-It scroll up in two times, the first time I can see the "send" button a little bit and the second one I can't see the message box anymore. It always jump to the SAME point (with 10 messages or with 200..) the second "jump" occurs 1 second after the first one.
-It is REALLY annoying.
Here's infos on my cellphone:
Bell's HTC Desire Z (canada) with official ROM (not rooted) version 1.84.666.2 (On Android 2.2.1)
I'm using it in French with French Canadian Keyboard.
If someone find a solution (other than switch to another messaging app) i'll be really happy!!
UPDATE: I was having two more software keyboard, "Wifi Keyboard" (installed by Remote Web Desktop) and an unworking Gingerbread keyboard app. (The gingerbread keyboard whas installed a long time after the problem starts), I uninstalled both of them and seems to have no more problems. I'll test some applications and thing and will update this thread once I have a "final answer" on it!
I did a lot if test and it seems that with swype selected, it happens EVERYTIME I slide out the keyboard AFTER selecting a contact or a message.
If swype is not selected, it happens sometimes, but a lot less. Is there a solution to this? I'm not using swype so it do not matter to me, but i would like to fix this annoying bug
Sent from my HTC Vision using XDA App
joe540 said:
I did a lot if test and it seems that with swype selected, it happens EVERYTIME I slide out the keyboard AFTER selecting a contact or a message.
If swype is not selected, it happens sometimes, but a lot less. Is there a solution to this? I'm not using swype so it do not matter to me, but i would like to fix this annoying bug
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Yes I know how you feel.
Sadly, the only workaround I've found to minimise the jumps is by going to the list of messages first in landscape mode (keyboard out) before selecting the thread. It's not 100% foolproof but I found it cuts the phenomenon down significantly with my European Desire Z.
I'm hoping the promised upgrade to gingerbread may finally put this one to bed.
Just a quick update: I've uninstalled Swype Beta completely (rather then keeping it installed as an option) as I was hardly using it. Seems to have made a difference to how often the jumping occurs.
Sent using XDA Android Premium App
I get this in the messsaging app Only on Sense though....
Sent from my HTC Vision using XDA Premium App
i think its an android general issue i remember having the same problem with my xperia x10 and it happened also on an omnia ii i ported eclair to, so yeah...
This is a known issue. It has to do with ambient light hitting the black touchpad. It causes the screen to inadvertantly jump up. I had this problem before. When ever you see it happening just move the touchpad out of the light or cover it with your hand and it should be fine.
Sent from my T-Mobile G2 using XDA App
After my 4th g2 and a month with it, it starts happening to me here in the no airport =/
Sent from my T-Mobile G2 using XDA Premium App
So what's the REAL solution here? It happens every time for me and it has nothing to do with light...?
I had the desire for over a year now and it has gone back to get repaired twice. Hardware issues.
I use SwiftKey x and am happy with it. As last week, when I use the dedicated qwerty keyboard in a text message, and I hit the s button it saves the message and the g button it goes directly to gmail.
I think it is just a setting issue but can't seem to be able to turn it these short-cuts off.
Regards,
Tap
Had the same issue, its a Swiftkey issue, i switched to Better Keyboard and problems were gone, or restore with a rom =)
if i help'd hit that Thanks Button
Might wanna try Smartkeyboard pro...
Sent from my HTC Vision using Tapatalk
thats ur rom getting locked in hotkeys, try pressing search or menu
A reboot always seems to fix this issue for me