Thanks for the link... That's a shame that apps on the SD card have so many limitations. I'd rather not disable the ability to move to SD, as this app is much more than simply an input method, and I'd get far more complains about the inability to move to SD than I have about the input method being disabled. I'll add something to our Android Market listing about it, but it seems like Android should either add something to the input method enable screen about it, or the move to SD screen, or both.
Drew On May 23, 5:23 pm, Kostya Vasilyev <[email protected]> wrote: > Have you seen this? > > http://developer.android.com/guide/appendix/install-location.html#Sho... > > > Applications That Should NOT Install on External Storage > > Input Method Engines > > Your IME will be replaced by the default IME. When external > > storage is remounted, the user can open system settings to enable > > your IME again. > > Do you see this happen when the phone's memory card is mounted on a > computer? If so, this is expected, per the document above. > > -- Kostya > > 24.05.2011 1:17, Drew ?????: > > > > > > > > > > > After further debugging, it appears this problem is indeed an Android > > bug, and is only present if the app in question is moved to the SD > > card. I've reproduced with every app containing an input method that > > lets you move to SD so far. > > > I guess I'll report it through more conventional channels. > > > Drew > > > On May 17, 3:58 pm, Drew<[email protected]> wrote: > >> One of our Android applications contains an input method. A user > >> recently reported that the input method is randomly being disabled. > >> In other words, it's mysteriously no longer checked in Language& > >> keyboard settings. > > >> I can't reproduce, of course, and I wouldn't know where to begin > >> debugging such a problem, since the code that enables and disables > >> input methods is totally external to our application. > > >> The input method is originally based off the SoftKeyboard sample app > >> that comes with the Android SDK. I've had to fix several bugs that > >> were originally present in the SoftKeyboard sample app, so I wouldn't > >> doubt a similar bug could be causing this, but I can't for the life of > >> me think of a bug that would cause an input method to be disabled. > > >> He reports that other input methods, such as Swype and the default > >> Android keyboard, don't behave this way. > > >> He has a Samsung Epic 4G running Android 2.2, if that matters. > > >> Any debugging ideas would be greatly appreciated. Thanks. > > >> Drew > > -- > Kostya Vasilyev --http://kmansoft.wordpress.com -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
