I have setup an Android API 30 emulator (from Android Studio), where I have installed two physical keyboard layouts. According to the system, I should be able to switch languages via Control+space. But that does not work.
I've tried:
Changing the "send keyboard shortcuts" to "virtual device" - effectively disables multi-touch but that's it.
Installed tons of different apps (including Hackers Keyboard) but saw no difference at all - seems they only work for the soft keyboard
I tried changing the kcm keyboard file from open source projects (and it worked well for changing e.g. "a" to "9") but I could not make for instance Shift+space to execute a language switch fallback
I even tried to write apps but I am not sure where to start (and from my experience with the other apps I tried, I am not sure if this will work at all)
Any ideas what else I can do?
I ended up using Android x86. The control+space works there just fine.
Related
I have an android app that disables the use of soft keyboard, as it has it's own soft keyboard for use. However, it is still downloadable by android devices with physical keyboards and they can input into the apps editTexts.
Is there any manifest code I can use to prevent the app being downloaded by such devices with physical keyboards?
Also, I'm going to make a version of the app that will only be used by such devices. Is there any manifest code to make sure it is only downloaded by such devices?
You can try uses-configuration manifest tag. For physical keyboard :
<uses-configuration android:reqHardKeyboard="true"/>
You can see more examples here
I am trying to write an application with Mono for Android. In an attempt to do this, I'm using the default template in monodevelop. I can successfully compile and run the application. When I run the application, it looks similar to the one shown here: http://docs.xamarin.com/android/getting_started/hello_world
There are two oddities in my version though:
The button is red
I can't seem to actually click the button. When I use my computers mouse, it acts like it won't click the button. This is not limited to the application either. If I try to click the home or search button in the emulator itself, I noticed that nothing happens either. Its like the emulator is not responding to my mouse.
As someone new to working with Android, can someone please tell me what I'm doing wrong? I'm using MAC OS X with Lion installed. I'm assuming that I have the SDK and Java SDK installed properly considering the app compiles and when I press "play" I can load the app in the emulator. I just can't figure out why I can't actually click the button. So bizarre.
Any ideas?
The title of this question is pretty misleading, since you're saying that the emulator is not very responsive even outside the Mono for Android application. The problem here is with the emulator itself. The one thing I would recommend trying with respect to Mono for Android is to try starting the application without debugging, as debugging will add extra overhead to running the app.
The Android emulator is notoriously slow, since it is fully emulating the ARM instruction set in software. That said, there are certain things you can do in order to squeeze some more speed out of it. One thing that I've seen make a big difference is to decrease the screen size of the emulator image. Setting this to a small screen size (such as QVGA) can make a big difference. You can manage these settings through Android's AVD Manager.
I'm very new to Java and the Android SDK but I'm almost done with porting one of my iOS apps over to Android. I'm targeting Android 2.2 (minSdkVersion=8) and higher and recently bought a cheapo LG Optimus S with 2.2.1 for $75 to test with. On the AVDs I've set up (2.2 & 2.3.3) and my test device (2.2.1), everything is working as expected: user data input, graphing user results, sharing on facebook and twitter, and uploading data to a mysql database via php. My problem arises when I test my app on AVDs 3.1, 3.2, and 4.0. Simply put, the Soft Keyboard does not pop up at all when I select an EditText box with any of these versions through the AVD. This behavior didn't occur in 2.2, 2.2.1, or 2.3.3.
I've created and deleted at least a dozen AVDs and have set Keyboard support = no, Keyboard lid support = no, and any other related input type to no and the Soft Keyboard still doesn't pop up when I click on an EditText box. After tinkering with 3.2 through the AVD, I was able to set up the Soft Keyboard and use it with my app, so that's no longer a concern. However, I still can't get it to pop up with 4.0. Should I even worry about this? After all, it's just an AVD and not the real thing. Will an actual Android 4.0 device without any type of physical keyboard know when to pop up a Soft Keyboard or do I need to add some keyboard show/hide methods for it (and maybe 3.1/3.2)? I can't buy a cheapo Android 4.0 device yet..
Thanks,
j
As long as you aren't doing anything weird, tapping on an EditView should pop up a keyboard on any device that doesn't have a hardware keyboard so it should work fine on a 4.0 device.
I'd still try to get the AVD working correctly. Pop-up keyboards work fine on my 4.0 AVDs.
I just took a look on different devices and their soft keyboards. They are all looking a bit different. I attach two screenshots. One is from my HTC Desire (Android 2.2), another one from Emulator (Android 2.3).
As you can see on the device the enter key is on device just a symbol, on emulator it is "send".
Can I change it somehow?
I had this problem a year ago, my problem was that the numeric keypad is very different from each provider (not only on style but on the buttons that are shown)
In my personal experience is a pain to try to change that, you would need to create your own SoftKeyboard class with your own images.
If it's not an important issue I recommend to just pass over it, or find a keyboard type that satisfies your needs.
However, I don't know if in the newest versions of Android you get an easier way to customize keyboards.
Good luck on there :)
I have an enterprise Flex web application, served up over https, that runs fine on Flash player 10.0 and beyond on a desktop computer/browser.
However, when I run it from my HTC Incredible with Android 2.2 the app loads fine, but there is no on-screen keyboard and so I cannot log in. I can see the blinking cursor inside the username and password text fields. I can switch between them. I can even hit the login button and see an authentication error!
According to Adobe this should Just Work. Any ideas? I wanna show off our spanking new app to strangers at the bus stop!
Seems the problem is different implementations of the keyboard in the browser. See the comment from Adobe here as they shut the bug as unfixable: https://bugs.adobe.com/jira/browse/FP-5704
I have the same problems on a Galaxy S2 - though manually forcing the keyboard up here isn't an option as the address bar automatically gains focus.
Mobile Text Input
Flash Player 10.1 provides support for use of native device virtual keyboards with TextField support if no physical keyboard is detected. A virtual keyboard is automatically raised and lowered in response to focus changes on text fields when editing text on mobile devices supporting a virtual keyboard to enable unobstructed and intuitive text editing. The focused text field is centered in the visible region of the page and appropriately zoomed/scrolled to ensure it is not obscured by the virtual keyboard. Upon screen rotation, incoming calls, or other system events, any already existing text input is retained. The virtual keyboard works with TextField but does not currently work with the Text Layout Framework or other Flash Text Engine text.
The spark components in Flex 4 are not currently optimized for mobile. The next release of Flex codenamed "Hero" will provide mobile optimized skins for the spark TextInput/TextArea components. These skins are based on TextField and they are also optimized for performance with ActionScript skins and a more appropriate default size. Text support in the current Hero preview release is minimal, but the final release will be more robust, for example supporting scrolling in a TextArea. Check out the spec for more information: http://opensource.adobe.com/wiki/display/flexsdk/Mobile+Text+Components
It's probably worthwhile to note that the mobile features in Hero are designed with standalone mobile applications in mind, not browser-based applications. That said you might be able to grab those mobile skins and try using them in a browser-based Flex application compiled with Hero.
have you tried republishing your work strictly for 10.1? i believe that any applications which support versions of Flash prior to 10.1 are seen as Flash Lite on mobile devices, which may (or may not) be the problem.
it's worth a try.
Not a programming solution, but long press on the menu button brings up the keyboard if it doesn't pop up by itself (at least on my HTC Desire, 2.2 android).
Device: Kindle Fire
I had the same problem. My mathlab uses flash for homework assignments, and I could not access my keyboard for input. Until I found this.
Download and Install "Keyboardflash_1.0.0.apk" on your Android device.
go to the flash program in your browser
run the "Game Keyboard" app and click "Tap here to call out keyboard after exit"
return to your browser
You will notice I did not perform the direction the app gives you because the kindle fire is not compatible with those steps. Maybe it is with your device.
You may have trouble getting this to work with a browser app like "Dolphin"
Your Welcome :)
and respect the developer
Gamepad is also on the android market.