I like the predicitive text on the QWERTY keyboard, the eris feature where alternatives are shown for typed words, presenting an opportunity to choose the correct word. I enjoy using this when doing IMs in Google Talk, for example. This feature seems to be disabled in the default web browser on the eris, in 1.5 before, now in 2.1. The predictive text does not work in the search bar and it does not work in data entry fields in forms displayed by the browser, for example
Can anyone please tell me how one would enable this predictive text input in all apps on the phone? including the search bar for webkit and data entry on web forms?
<see last post for solution>
There is probably a good technical reason for this, like somehow the input method is not known to the web browser application. Perhaps the browser itself is not consulting a system table for availability of this input method at run time. Maybe it only happens at install time? Is there some manual change that could be made to enable this?
I think they disabled it in browser because a lot of websites have names that the predictive text obviously doesnt know and when you type fast and hit space quickly it auto selects words which Id imagine could be quite a pain in the ass online.
WalkingTaco said:
I think they disabled it in browser because a lot of websites have names that the predictive text obviously doesnt know and when you type fast and hit space quickly it auto selects words which Id imagine could be quite a pain in the ass online.
Click to expand...
Click to collapse
Thanks, You are right. I agree as to why they disabled it, but i think the way the feature works, it would really be more benefit to me than a hindrance.
1) Adding a mispelled word or one not in the dictionary is painless, editing this dictionary in the settings is easy too.
2) For activities like retyping stuff (like my email address) in data entry fields in the browser over & over; this would be much better with the ability to spell-check and remember words, especially when accuracy is critical.
I want predictive text in the browser. Why not a voice input option (like in the voice search applet) as well?
Can someone help at least give me the choice, I think these two input methods work very well.
Solved - 2.1 enhanced HTC keyboard, with voice too! - link
This pretty much gives you voice and predictive text wherever you want it without sacrificing anything:
nimbu.amorvi.com/2010/04/add-full-voice-to-text-to-htc-desire/
Followed the "HTC Sense Style Keyboard Instructions"
Instructions were for HTC desire but this worked fine on stock OTA 2.1 Eris, not rooted.
HTC_IME_lo_25.apk is the one that installed okay for me. I was half-asleep at the time and I think the other version did not install right, but you might want to try again.
Enjoy!
Related
I find it crazy that SMS-Chat seems to be the only program for Windows Mobile that combines touch-friendly scrolling with threaded messaging.
I have a Palm Treo Pro and in order to see the text I type, I have to hit enter, and then backspace, and then I can start typing.
My question: Is there an alternative to this? I would use the regular sms built into WM6 but in order to scroll up and down, I have to use the tiny scroll bar on the right instead of being able to scroll by touching and pulling the middle of the screen.
Yes, I've googled the crap out of this so I come to you guys seeing if anyone has a diamond in the dirt.
Slide2Send forum.xda-developers.com/showthread.php?t=602638
Thanks a lot for the link!
My only problem with this program is it doesn't show you the full content of each text from one person in a thread, and it doesn't default to the last text sent, it starts at the top which is a problem for a thread with many texts. I like it though, and hope to see improvements in the final versions.
MKH SMS (beta version and unstable)
Requirements: wm5+ compact framework 2+
it said "MKH software MKH SMS" cannot be installed. To try installing to a different location, chose a location" but it fails for SD card and phone memory. Weird.
Bump if anyone knows a good sms program. Like I said, it seems there is a problem on Palm Treo Pro's where the text won't show up when you type to a person unless you hit enter, then backspace. It's a hassle to do every time I send a text. Is there any program like this?
I hear certain ROMS will fix this issue but i'm not too savvy on roms..
Have you tried 'Pocket Contact Manager'
A bit old, but works ok on my 'old' device, displaying contacts but also SMS in a threaded way...
http://www.pocketcm.com/
And... ho... It's freeware !
I am looking for one myself for a long time and could found nothing.
1. SMS Chat - has lots of bugs, with an inbox with 50 or more messages, it freezes all the times. Contact with developer, no response
2. Slide2Send - slow as hell, missing lots of features
3. MKH SMS - very buggy, trying to scroll thru the messages is a pain
4. PocketCM - not really a replacement as you have to open a contact to see the list of SMS
5. Samsung SilverInBox - so buggy that even samsung have hidden it on the ROM
Can't find a good (or even resonable) message app that is finger friendly.
Tried another one, SMS at Hand, one of the ugliest interface (and confusing) I have ever seen.
If you wanna try MKH SMS, use this installer, it will work (removed Russian lang file, problem with cyrillic chars on the file name).
BTW, MKH SMS seem to be the only one still in development, you might try to contact the developer at http://www.mkh-soft.com/mkh-sms.aspx (it is in Russian).
Just a quick tip, if you tap on the top bar (middle), you will get some popups, like Settings (if you are at the folder list view), Delete SMS (if you are reading one), ...
I wish I knew coding. It's just kinda annoying I have to hit enter, then backspace just to see the text i'm typing in SMS-Chat. I love the program, but this is a pain. Even on their website help it suggests doing that...for a paid program.
no others?
I am using SMS at Hand. never can get it right. I do not want to be the default sms handler.
just like other sms program, no support for sending sms, u will only see the beautiful skin when scrolling the messages.
At the moment you click send new message it will go into the ugly ms default.
I am sticking with MKH SMS for now. Developer seen willing to move it forward, been talking with him about problems, suggestions and new translations. Version 1.2 seem very promissing.
Btw, it replaces the send sms with a graphical touch based one, you should try it.
there is 1.2?
Version 1.2 is still in development, but looks promising.
Hopefully easily skinnable as well!
Yes. The skin is a file with an extension of *.th, but that is only a zip file with some images a config (text) file. It comes with an iphone like skin. Would be nice to have at least two more, a manila and a diamond.
Translate is also easy, it is a text file (I have done one to Brazilian Portuguese).
bsinclair said:
Version 1.2 is still in development, but looks promising.
Click to expand...
Click to collapse
can we try it?
Just tried MKH on my HD Mini and it works just fine. also seems to take only half the memory of HTC Messages.
Hello,
I'm practicably legally blind and reading emails/SMSs and text in games is damn near impossible for me.
I've got the Samsung Ace and I've found an app to switch the answer slider with a big-ass button, I'm using WP_Clock (Which was mentioned here, thanks!) to see the time and date.
I've rooted and tried a few font resizers but none worked and the ones that did only worked on the English font (most of my phone is in Hebrew).
Does anyone have any idea how can I deal with this, other than getting Android eyes
Oh, one more thing:
I've used Total Recall and CallRecorder to record my calls, both record me fine but the other side through the mic, any idea if there are other apps that can record both sides at the same quality?
May all who read this post be touched by his noodly appendage,
Sam.
EDIT:
Oh yeah, My doctors told me it'll be easier to read white text on a black background, so I downloaded a few of those modified apps (Gmail and DropBox). If you know of any others, I'd appreciate a mention.
Noob to android!!
On my Samsung GT 5570, there is an accessibility option under "options", with text to speech features. But looks like the phone has to download several components. Have not tried them, will try them out if you are interested.
Running Gingerbread 2.3.3 (but it was there in froyo 2.2.1 Africa version too).
Saw that option on my run-through of the device (saw isn't exactly the word...)
Not that comfortable using an actual magnifying glass on your cellphone.
Can't stand that thing, that's why I'm posting, looking for something a bit more comfortable like resized fonts and such.
Thanks for trying though, appreciate your assistance!
Using accessibility features in Android
Ok. I have a Samsung GT S5570, "mini".
I have upgraded from 2.2.1 Froyo to 2.3.3 Gingerbread.
To enable accessibility features, more specifically, text to speech, you need to go into two options,
1, Settings > Voice input and output
2. settings > accessibility
I cannot remember which one I opened first, but the phone asked me to enable data downloads / background sync as I entered both menus. ("Always on GPRS" - if you are new to android - especially were using Nokia phones so far).
Once the data is downloaded, go to #1. First entry is "Listen to an example". You can change the language and speed of text to speech engine in other menu options below. At the bottom, I have and entry, which says "engine" and underneath, "PicoTTS". This means required data and text speech engine are installed on the phone.
I guess the available languages are dependent on the ROM you use - you probably need to have the African ROM. (Hope somebody will correct me here).
Here is how to actually enable the phone to read the screen,
Settings > Accessibility > Talkback.
Just enable Talkback. That is it.
Again, I appreciate your help but as I've said, I'm not too comfortable with the TTS and prefer, as long as I have other options, not to use it.
If anyone has any other apps in mind, I'd love to know.
Otherwise, The built in TTS has been checked and discarded, thank you.
I just updated to the new Firmware version.
I'm using the international GS3 and I'm running stock firmware and kernel and all the other mumbo jumbo.
Previously I was able to type things like "whateevr" and the phone would automatically correct it to "whatever" after I hit spacebar. I remember this setting being in the predictive texting option, however, after the update the phone does not do that anymore and the predictive texting option only offers me to "Learn from my Facebook etc." or turn personal texting on or off (This feature seems somewhat dubious to me but whatever).
So, how do I set it back the way it was so that I can mistype words and have them automatically corrected?
racinghammock said:
I just updated to the new Firmware version.
I'm using the international GS3 and I'm running stock firmware and kernel and all the other mumbo jumbo.
Previously I was able to type things like "whateevr" and the phone would automatically correct it to "whatever" after I hit spacebar. I remember this setting being in the predictive texting option, however, after the update the phone does not do that anymore and the predictive texting option only offers me to "Learn from my Facebook etc." or turn personal texting on or off (This feature seems somewhat dubious to me but whatever).
So, how do I set it back the way it was so that I can mistype words and have them automatically corrected?
Click to expand...
Click to collapse
I am also troubled with this. Browsing through the forums suggests that this is intentional and mimics the behaviour of the Note II keyboard, so cannot be readily changed.
I would suggest that this is a huge 'unimprovement' and would like to commend to our developer community the idea of integrating the previous keyboard auto-correct behaviour into custom ROMs.
has anyone had issues with swype not using it's custom dictionary but what appears to be the built OS custom dictionary (i'm assuming it's an android thing and not a LG thing)?
when i first setup swype it worked as expected. but it seems that the built in dictionary has taken over. here are two examples:
i prefer to see/use "LoL". don't care for "lol" and really dislike "Lol". the swype custom dictionary pays attention to the spelling and the capitalization of the words in its custom dictionary. the Android custom dictionary does not. hence most of my LoL's come out as Lol's.
the other is noticeable when sending email. when working properly, i can email to my work address by entering my first initial last name and it autocorrects properly and the email client presents the correct address. but when not, it autocorrects to an incorrect word and i thus have to type my name to the last letter. (the last letter is where where the autocorrect is wrong)
is there any way to disable the built in custom dictionary? I've tried unchecking 'spelling correction' from the Language and input menu. I've tried adding LoL and my firstinitallastname into the built in dictionary...but that doesn't work. i prefer to use the swype dictionary, mainly cause it works. it finds my name and pays attention to capitalization.
DraginMagik said:
has anyone had issues with swype not using it's custom dictionary but what appears to be the built OS custom dictionary (i'm assuming it's an android thing and not a LG thing)?
when i first setup swype it worked as expected. but it seems that the built in dictionary has taken over. here are two examples:
i prefer to see/use "LoL". don't care for "lol" and really dislike "Lol". the swype custom dictionary pays attention to the spelling and the capitalization of the words in its custom dictionary. the Android custom dictionary does not. hence most of my LoL's come out as Lol's.
the other is noticeable when sending email. when working properly, i can email to my work address by entering my first initial last name and it autocorrects properly and the email client presents the correct address. but when not, it autocorrects to an incorrect word and i thus have to type my name to the last letter. (the last letter is where where the autocorrect is wrong)
is there any way to disable the built in custom dictionary? I've tried unchecking 'spelling correction' from the Language and input menu. I've tried adding LoL and my firstinitallastname into the built in dictionary...but that doesn't work. i prefer to use the swype dictionary, mainly cause it works. it finds my name and pays attention to capitalization.
Click to expand...
Click to collapse
Try this, go to settings > general > language and input > uncheck spelling correction at the top. I think that's the default Android OS spell check or the one associated with the android keyboard. See if that helps.
if i go to apps and clear the Settings and Cache for Swype...then go to use it again (and go thru the setup) it works as it used to and as i expect. but once it try to add anything to the dictionary, it changes the behavior.
Hi there, first time poster. I was wondering if someone could answer a few questions for me as it pertains to HTML5 and bringing up a Keyboard on Android (any version). I am a website developer and I have recently gotten into making my web applications mobile friendly, but I'm running into some snags when trying to get a certain keyboard to show up on Android / iOS and I'm wondering why it's not a bigger issue than I've seen so far.
Right now, if I add an <input> onto my page and add type="number", Android will pull up a keyboard that has numbers, etc. My problem is, the field I'm using isn't a "real floating point number", which all major browsers (except IE11) disallow. If I have an input set up to take a credit card number, I cannot allow the user to add dashes to make it easier to read while using type="number". However, I'd rather have the number keypad pop up by default as it really is all numbers, just not a calculatable (is that a word?) number.
I was wondering how difficult it would be for Android to add in something so when a field is clicked into, it would look for a specific vendor prefix to load a soft keyboard of the web developer's choosing? For instance:
Code:
<input type="text" data-soft-keyboard="number">
or
Code:
<input type="text" data-soft-keyboard="email">
which will give the device very clear and explicit instructions on which type of keyboard to display.
Sorry if this seems way out in left field, but I haven't found a decent solution to this issue. I went to Chrome forums to discuss and people said Chrome is 100% working off of the HTML5 spec. My personal opinion is that the HTML5 spec is wrong and why the hell are browsers doing validation against data in textboxes when I didn't specifically ask for it. However, I'm not really sure which direction to go at this point.
Any suggestions or opinions on the matter would be very nice, thank you