Hello Stackoverflow Community,
I am writing Phonegap application, and i need to support Android 2.3 - 4.1.
On earlier android there are some bugs with keyboard, so I've created custom one on html. Now, I need for all androids version API <= 10 turn of virtual keyboard. Any ideas how to completely programmatically disable it?
Thanks,
-Dima
put below code in your manifest file, inside actvity node
android:configChanges="orientation|keyboardHidden"
it may help you
On earlier android there are some bugs with keyboard
First, there are many implementations of "virtual keyboards" in use in Android.
Second, I am not aware that Web developers have generally had problems with Android's soft keyboards. You are welcome to provide links to evidence supporting your claim.
Now, I need for all androids version API <= 10 turn of virtual keyboard. Any ideas how to completely programmatically disable it?
That is not possible. However, if your Web page does not have anything that allows conventional text input (e.g., <textarea>), then the soft keyboard typically will not appear on its own.
Related
I'm having some trouble getting TalkBack to work with a web view (testing with a Nexus 9 on Android 5.1). I read that TalkBack support was added to web views around the release of Android JellyBean by checking a preference titled "Enhance Web Accessibility." I can't for the life of me find this preference in the system settings.
Focusing on the web view in our application simply reads "WebView" and provides no other options.
Was TalkBack support for web views removed in KitKat? If not, what am I missing here?
Am using Mobile accessibility Plugin to read my customized talkback
My app work fine with Android 4.4.4 . Am using aria-hidden=true to stop default talkback of Mobile accessibility. But with that attribute lollipop doesn't focus to the event and not all reading
Your question is a little unclear. But I can guarantee one thing, this has nothing to do with the "Enhanced Web Accessibility" option. This was an experimental accessibility setting in Android 4.1 - 4.2 and has since been deprecated. This is why you cannot find this setting. What "Enhanced Web Accessibility" did was add some visual elements to help users spot things like Links and such with nice outlines. It has nothing to do with basic TalkBack support for WebViews, which has been supported since TalkBack was released, though it has certainly improved since then, and is still improving.
Now, this doesn't really answer your question. Only removes one of the solutions you seem to have been concerned about investigating. As per your actual solution, your question is a little unclear what your actual problem is. It seems to me you have some sort of event firing in a custom WebView you have created, and this should cause TalkBack to read something out. I await further details to continue this answer, though I suspect that you have not set the WebView's accessibility delegate.
mWebView.setAccessibilityDelegate(new View.AccessibilityDelegate());
It must be set to setJavaScriptEnabled (false);
web components analysis appears to be view.view.
I would like to program an android app that replaces the standard keyboard by one with the one-hand optimized Coffee++ keyboard layout.
What special problems would I have to face in the progress? I guess that such a project would go deep into the android core, cause the keyboard is such an essential thing.
Is it wise to start with the Android Developer Tools (ADT)—Eclipse Plugin as described in this tutorial?
Or is there a better way to achieve this goal?
I am new to Android programming, but very firm in PHP, Mysql and javascript and I already use Eclipse for PHP
I guess that such a project would go deep into the android core, cause the keyboard is such an essential thing.
No. You can create an InputMethodService that is the implementation of your keyboard. There is a sample soft keyboard in your Android SDK installation (if you chose to download sample code from the SDK Manager), and there are open source input methods floating around as well, such as the Hacker's Keyboard. This InputMethodService is then distributed as part of an ordinary Android application, and the user can elect to activate your input method if the user chooses.
Is it wise to start with the Android Developer Tools (ADT)—Eclipse Plugin as described in this tutorial?
That is a fine starting point. I would also recommend that you spend some time learning Java, then developing ordinary Android apps, to get a feel for how Android works.
When you are ready to work on the InputMethodService itself, the documentation can help guide you, and you are welcome to return here for more specific questions. However, bear in mind that writing a soft keyboard is not all that common, and so support resources for it may be a bit lacking.
A soft keyboard in Android is called a InputMethod, and you don't have to go too deep to be able to create one. Creating a InputMethod is fairly straight forward especially if the keyboard is normal button kind.
You can check the following links to get a start :
Android's Official Tutorial or you can check out this tutorial too to get a head start.
I would also recommend downloading the source code for LatinIME keyboard available for the developers to tinker with.
I'm developing an application for Android (and iOS) using PhoneGap, and have come across a problem where as a result of some -webkit-transform: translate3d(x,y,z); calls, my text input boxes that are created by Android are no longer lined up with the element on the page.
The issue that I'm experiencing is the same as this one, however I wish to hide the boxes that Android creates and instead use the ones that are present within my application's DOM. Is this possible?
There is a specific article about Android form bugs in our documentation, check it out. Unfortunately there is no full solution for this problem, but at least the newer Kendo UI Mobile versions implement a partial workaround for this issue (which btw was finally fixed in Jelly Bean). Since the workaround has several negative effects, consider if you want to use it at all.
Im working in an app to modify the sounds when I key is press in the android soft-keyboard. I have download the sample soft-keyboard from Google. Now Im trying to figure out how to add sound to each or all the keys.
My question is: is it possible to assign a short customize sound to each key?
Can i change this in the already implemented keyboard?
You can't... it's already built and some manufactures provide their own keyboard implementations.
Or should i make my own keyboard?
Yes, you must.
If the latter is the case, how do i do that? Can i find the source code somewhere?
There are some open source projects of Keyboard implementations... for instance:
https://github.com/g1011999/Gingerbread-Keyboard/
http://code.google.com/p/softkeyboard/
There you can learn how to write your own keyboard, which is completely different from writing a conventional app.
My suggestion is to create a new fork of the Gingerbread-Keyboard (this supports Android 2.2 or higher only)... and then implement that specific change you want. For one of my apps I did so, and it's far easier than implementing the keyboard from scratch.
I want to add the functinality of Home,Back,Searcha and Menu Hard keys via some soft keys which can be accessed anytime the device is up.
I know their are few applications available which already do this, but i wanted to know the way this can be implemented.
Any help would be appreciated.
As stated elsewhere, the SDK is not enough to emulate hardware buttons: you need to be able to modify or at least call system sources, so you should be compiling Android from sources.
That said you can emulate the software button by calling "injectKeyEvent" in IWindowManager like done in these examples:
http://java-admin.iteye.com/blog/813208 (chinese)
http://tinyurl.com/5spjxja (android-x86 patch)