Related
I've recently received my DHD and noticed that the internet browsing experience is slightly different than what I used to with Opera on Windows Mobile (HD2).
One of the specific annoyances I had was trying to force the full site to load rather than mobile versions of sites (eg. Engadget vs. Engadget Mobile).
Even choosing to view the "Full Version" of certain websites I am still redirected to view mobile versions - not presented with the versions that would appear on a Desktop browser.
I have done some searching in XDA (and the web) and the only thing I was able to find were references to WindowsMobile to change the Custom User-Agent under User Prefs (In Opera Browser type, "Opera:Config" -> User Prefs -> Custom User-Agent). I have changed this but it does not appear to work.
I came across http://www.zytrax.com/tech/web/browser_ids.htm but am not sure which Browser string I should try to use.
(Have tried IE settings as well as identifying my current desktop browser setting - Chrome - and inserting that) Additionally, I have also attempted to change the User Agent ("Opera:Config" -> User Agent) by incrementing the number and that does not appear to work either.
Attempting to connect to "About:debug" (in hopes of seeing some other settings somewhere) tells me that it failed to connect to the debugger at the default address/port.
I'm a little stuck as to where to go from here.
Has anyone else experienced this or managed to amend successfully?
Well, after further searching I still haven't been able to have the Opera Browser default to show me a Desktop view of web pages that seem to aggressively divert you to mobile versions of their sites.
However, I did download Dolphin Browser HD from the market and the settings page listed this as an option that works very well.
Based on my short experience with it, I actually think DolphinHD is actually a much better choice of browser for Android.
I got Swype to install but the rom wont let you select it
Right, you can't access the stock android settings page to enable it. Will likely need a custom rom before this can be done.
I dont have a fire yet so this is pure speculation....
Can you sideload a home screen replacement (like launcher pro) and have better access to the settings menus? Thus allowing ability to select swype?
I installed Go Launcher Ex, which worked for me, and I was unable to access any other settings other than the customized Kindle Settings.
sanewicked said:
I installed Go Launcher Ex, which worked for me, and I was unable to access any other settings other than the customized Kindle Settings.
Click to expand...
Click to collapse
Cool, well guess at least we know those work! Will have to wait for some devs to get other stuff working I guess (or learn ourselves).
Edit: And im guessing they disabled the function to where you can long press on a text entry field to change input methods?
big gulps huh? said:
Edit: And im guessing they disabled the function to where you can long press on a text entry field to change input methods?
Click to expand...
Click to collapse
That's what I was going to suggest trying.
Sent from my DROIDX using XDA App
big gulps huh? said:
Edit: And im guessing they disabled the function to where you can long press on a text entry field to change input methods?
Click to expand...
Click to collapse
There *is* a menu for input method that has only one entry, "Kindle Keyboard".
masayang
The kb has to be enabled in settings before it will show up in the input selection menu. Of course there is no way of doing that just yet
Sent from my ADR6400L
SikYou said:
The kb has to be enabled in settings before it will show up in the input selection menu. Of course there is no way of doing that just yet
Sent from my ADR6400L
Click to expand...
Click to collapse
Ok, I totally forgot about that. Oh well...
I am getting my kindle fire tomorrow and I've been looking at how to enable other keyboards. See if you can manually edit the file where settings are store: /data/data/com.android.providers/settings/databases/settings.db using an sql editor look for the field "enabled_input_methods". Type in the proper info for the keyboard you are adding and see what happens. Root is required obviously. With any luck this might work.
Swype working just fine.
Psxtreme said:
I am getting my kindle fire tomorrow and I've been looking at how to enable other keyboards. See if you can manually edit the file where settings are store: /data/data/com.android.providers/settings/databases/settings.db using an sql editor look for the field "enabled_input_methods". Type in the proper info for the keyboard you are adding and see what happens. Root is required obviously. With any luck this might work.
Click to expand...
Click to collapse
I got swype working last night after a few trials. Here's what I did (though I'm sure not all steps are necessary).
I of course first grabbed the swype APK from my ATTSGS2 and side loaded onto the fire (without root). I know you all said it wouldn't work, but this is just the way I troubleshoot issues.
Swype installed fine, but as you said I could not select it from the input options list (when you long click a text field it gives you the option to select input method).
Now, I haven't permanently rooted my fire. I quite like software updates, video, and security on my device. That said, I don't mind dabbling with the stock load a bit. I pushed zergRush out to /data/local and ran that to get a temporary root.
I then downloaded the settings.db as suggested above and used sqlite3 (included by default in Mac OS X) to edit the input methods list to add swype.
Here's a dump of the resulting field:
INSERT INTO "secure" VALUES(21,'enabled_input_methods','com.android.inputmethod.latin/.LatinIME:com.swype.android.inputmethod/.SwypeInputMethod');
If you aren't comfortable editing an sqlite database file I'm not going to walk you through it, a mistake with that file could brick your kindle.
You'll see I added Swype to the stock LatinIME.
That did the trick. After a reboot (which by the way removes my temporary root). I could select Swype. Of course upon launching the swype keyboard I discovered I was missing the swype core library. After another zergRush and an install of the library which I also found on my ATTSGS2 I got swype launched!
Great the keyboard came up .. and .. "license failure". Damn, that's the first piece of android I've seen with license enforcement.
That's okay though, I knew swype corp (now a division of Nuance) somehow gives away copies of the software. I left settings.db as is but removed the swype apk and corelibs.
Then I headed over to the swype website, signed up for the beta, downloaded the swype installer -- which by the way I had to do from my ATTSGS2 because the swype website insisted my kindle was not running android.
I side loaded the installer onto the kindle (without root), ran the installer, and everything went in smooth. I didn't even have to go back into settings.db to change the default input method -- the installer seemed to do that for me.
I'm not sure if the settings.db changes were necessary at all in fact, and if not this would be a completely safe procedure with no root required.
Some feedback would be good. I'm sure everyone would love to use this workaround to get swype running, though for most of you you'd better not touch sqlite databases directly. Its my opinion if editing that file IS necessary, then you're probably better off waiting for ROM support. Though it would of course be a violation of copyright law to distribute a ROM with swype preinstalled. Beware developers who ignore copyright law, their missing scruples may extend to other areas of software development.
I imagine at some point in the future someone will release a .apk that can modify those settings but it's good to know the settings are there and functional, just obfuscated by amazon. Also there is an android market app that lets you edit the sql database more easily but definitely not for the faint of heart.
Psxtreme said:
I imagine at some point in the future someone will release a .apk that can modify those settings but it's good to know the settings are there and functional, just obfuscated by amazon. Also there is an android market app that lets you edit the sql database more easily but definitely not for the faint of heart.
Click to expand...
Click to collapse
I looked quick in the market and couldn't find one. Do you know the name?
It would be much easier than adb shuffles back and forth.
It's not free but I think it's worth it, it's called "SQLite Editor"
[email protected] said:
I'm not sure if the settings.db changes were necessary at all in fact, and if not this would be a completely safe procedure with no root required.
Click to expand...
Click to collapse
They appear to be - just tried installing the swype beta without rooting yet and the new keyboard is not showing up.
I just used the same method to enable Swiftkey X (the non-tablet version). Works great!
My "enabled_input_methods" field is: "com.android.inputmethod.latin/.LatinIME:com.touchtype.swiftkey/.KeyboardService"
Don't forget after uploading the modified settings.db back to the device to reset the owner ("chown system.system settings.db") and permissions ("chmod 660 settings.db") on the file. And as always, back up everything you change before you do it.
I'll post a step-by-step later if I'm not too busy.
i'll make a script tomorrow to change the enabled keyboard from stock to swype for y'all
you'll have to be rooted
I got my fire now and edited the db on the device using SQLite Editor and it worked after a reboot. I tested using Simeji (Japanese IME).
Swyping this on my kindle fire ;-). Thanks for the post! I had already kindle rooted and I happened to have the beta swype account, so for me it was much easier. all I had to do was to install swype installer from their beta web site and then use SQLlite editor to modify enabled_input_methods
Off topic: looking for decent home launcher to replace kindle's. Any suggestions. Tried the Go launcher but it isn't optimized for tablet
Can't you just move Swype to system/app and then the lib to system/lib, and reboot? You don't have to enable system keyboards
Sent from my PG86100 using Tapatalk
As I am a newbie, I am not able to start a thread in "Nook Touch Android Development", so I post the thread here.
I am focusing about rooted 1.1 nook touch.
I just wonder if this is my own problem or it is a common problem,
that the webkit component seems to have problems.
The the problem is, any app using the webkit component, when the user scrolls the view, or even "touched" the webkit view, the app cannot update the view again. although in some apps, user can still scroll it, but the app cannot put in new information.
For example: the default build-in browser, it is normal if i just click the url and change it, it will jump to the required web page. but once i touch the main view, i cannot refresh / go to another web page.
not only for default browser, as it is useless for a rooted nook. but other apps may also use webkit component for formatted text. this problem will affect numbers of apps that we can use.
anybody here have the same problem with me?
i am using firmware 1.1 and rooted by SalsichaNooter 0.4
Thanks, and sorry for my bad english
no one have such a problem?
i even tried to write an app, having 2 buttons and a webkit view
before "scrolling" the webkit view, everything is fine
after i "scroll" the view, both buttons cannot work
but the program is not hang, just the webkit is not able to refresh again
i also uploaded the apk
could anybody have a try?
Is there a way to install keyboard for other languages on rooted NST so that books in other languages can be searched too?
I do not know for sure but if I were on your place maybe trying to use jokers for the missing characters is good place to start? For example you are searching for title named Rosé and you type in the search box Ros? or Ros* instead. That might work for Latin script.
Multiling keyboard 1.1.7 has the capability of using many languages other than English (you may need plugins...I did not investigate very deeply). Whether that would allow it to do what you want, I'm not sure.
Although it's not as clean looking as the stock keyboard (keys are more or less black...), I value this keyboard because it allows you to copy and paste from one place to another. To my knowledge there is no other way to access the paste buffer on the NST. Also a lot of fluff, but hey, it's free!
nmyshkin said:
Multiling keyboard 1.1.7 has the capability of using many languages other than English (you may need plugins...I did not investigate very deeply). Whether that would allow it to do what you want, I'm not sure.
Although it's not as clean looking as the stock keyboard (keys are more or less black...), I value this keyboard because it allows you to copy and paste from one place to another. To my knowledge there is no other way to access the paste buffer on the NST. Also a lot of fluff, but hey, it's free!
Click to expand...
Click to collapse
Thanks a lot. Any pointer to the Multiling keyboard, e.g., download, installation instruction etc?
SJT75 said:
I do not know for sure but if I were on your place maybe trying to use jokers for the missing characters is good place to start? For example you are searching for title named Rosé and you type in the search box Ros? or Ros* instead. That might work for Latin script.
Click to expand...
Click to collapse
Thx, oriental languages wouldn't work.
smjohn1 said:
Thanks a lot. Any pointer to the Multiling keyboard, e.g., download, installation instruction etc?
Click to expand...
Click to collapse
Here's a link to an earlier forum post of the app: https://forum.xda-developers.com/attachments/com-klye-ime-latin-1-apk.4613077/
Keyboard apps should be copied into /system/app, permissions: rw-r-r, with a reboot. That's the good news. The bad news is that B&N removed the "guts" needed to change keyboards without getting into a database.
I know of two other options: Nook Color Tools which, despite it's name, has a few options that are useful for the NST. BUT, you must resist the temptation to poke around in the app because some of the options will trigger a factory re-image without warning. Nook Color Tools should be copied into /system/app, permissions rw-r-r, with a reboot. The second option is my Nook Settings app which, among other things, has a call to the native Android keyboard selector. You don't have to keep the app if you don't want it, but it's an easy way to get access to keyboard changes--and other things not available from the stock Settings app.
The keyboard is a little confusing to set up so just keep at it. You can ask me if you get stuck, but I don't use much of the extra features. I've even disabled the word correction (always hate that on any device), etc.
nmyshkin said:
Here's a link to an earlier forum post of the app: https://forum.xda-developers.com/attachments/com-klye-ime-latin-1-apk.4613077/
Keyboard apps should be copied into /system/app, permissions: rw-r-r, with a reboot. That's the good news. The bad news is that B&N removed the "guts" needed to change keyboards without getting into a database.
I know of two other options: Nook Color Tools which, despite it's name, has a few options that are useful for the NST. BUT, you must resist the temptation to poke around in the app because some of the options will trigger a factory re-image without warning. Nook Color Tools should be copied into /system/app, permissions rw-r-r, with a reboot. The second option is my Nook Settings app which, among other things, has a call to the native Android keyboard selector. You don't have to keep the app if you don't want it, but it's an easy way to get access to keyboard changes--and other things not available from the stock Settings app.
The keyboard is a little confusing to set up so just keep at it. You can ask me if you get stuck, but I don't use much of the extra features. I've even disabled the word correction (always hate that on any device), etc.
Click to expand...
Click to collapse
Thanks a lot. Following your instructions, I installed the Multiling keyboard, and Nook Color Tools ( haven't tried your Nook Settings yet, but probably would be same ). Seems Multiling Keyboard takes over, but press the middle big "English" key, there appears no other options. Check the apk (com.klye.ime.latin-1.apk), there are many xml files there. So my question is: do I need to install other plugins for various languages, e.g., chinese?
smjohn1 said:
Thanks a lot. Following your instructions, I installed the Multiling keyboard, and Nook Color Tools ( haven't tried your Nook Settings yet, but probably would be same ). Seems Multiling Keyboard takes over, but press the middle big "English" key, there appears no other options. Check the apk (com.klye.ime.latin-1.apk), there are many xml files there. So my question is: do I need to install other plugins for various languages, e.g., chinese?
Click to expand...
Click to collapse
In the settings/setup for the keyboard (where you go when you tap on the app icon) option #4 is for enabling languages--I'm sure you've seen that already. It does state there something about plugins. Waaaay down the list there are various Chinese alternatives. I didn't get anywhere with this. Sliding over the spacebar did nothing.
Check out: https://play.google.com/store/apps/details?id=klye.hanwriting. I tried version 3.3 from another source but it would not install, so unless you can scare up an older version, you might be out of luck.
Whether MyAlpha is needed as well (https://play.google.com/store/apps/details?id=kl.myscript) I don't know. Again, you'd probably have to track down an older version that will run on Android 2.1.
Edit: You may be able to find out more and/or contact developer here: https://sites.google.com/site/hanwritingime/
nmyshkin said:
In the settings/setup for the keyboard (where you go when you tap on the app icon) option #4 is for enabling languages--I'm sure you've seen that already. It does state there something about plugins. Waaaay down the list there are various Chinese alternatives. I didn't get anywhere with this. Sliding over the spacebar did nothing.
Check out: https://play.google.com/store/apps/details?id=klye.hanwriting. I tried version 3.3 from another source but it would not install, so unless you can scare up an older version, you might be out of luck.
Whether MyAlpha is needed as well (https://play.google.com/store/apps/details?id=kl.myscript) I don't know. Again, you'd probably have to track down an older version that will run on Android 2.1.
Edit: You may be able to find out more and/or contact developer here: https://sites.google.com/site/hanwritingime/
Click to expand...
Click to collapse
You are right, I was able to switch to a Chinese input keyboard, but simply couldn't get the Chinese characters to appear. Doesn't seem to be font issue, as the space key does show Chinese characters correctly. Also tried French ( francais ), but no French accent either. I guess I need to learn more how to use this keyboard. Your instructions on installation totally work fine. Thanks again!
smjohn1 said:
You are right, I was able to switch to a Chinese input keyboard, but simply couldn't get the Chinese characters to appear. Doesn't seem to be font issue, as the space key does show Chinese characters correctly. Also tried French ( francais ), but no French accent either. I guess I need to learn more how to use this keyboard. Your instructions on installation totally work fine. Thanks again!
Click to expand...
Click to collapse
Well, not much success here either. First I had to enable swiping the spacebar to change languages. That took me awhile to figure out. I have most of the app functions deselected since I only need a regular keyboard and the cut/paste feature. I was able to get German and Greek to both work properly. I agree that French seems lacking in accent marks but I did note that the standard English QWERTY arrangement was not used in French, so whatever that may mean.
FWIW I managed to track down the Pinyin plugin (eventually replaced by the hanwriting plugin). The keyboard settings shows it as installed but it does not seem to do anything with it. Selecting just the plain "Chinese" option (no plugin) gives a memory error. There is probably enough stuff in the DroidSansFallback font to display some form of Chinese (the device Localization options include Chinese, after all) but that doesn't seem to make its way to the keyboard app.
I also located a copy of the MyAlpha app which is suggested as a "font problem" fixing thing. Doesn't seem to do anything.
So...I've attached both apps. Probably you should contact the developer. He/she might be able to give you the information we are apparently missing.
nmyshkin said:
Well, not much success here either. First I had to enable swiping the spacebar to change languages. That took me awhile to figure out. I have most of the app functions deselected since I only need a regular keyboard and the cut/paste feature. I was able to get German and Greek to both work properly. I agree that French seems lacking in accent marks but I did note that the standard English QWERTY arrangement was not used in French, so whatever that may mean.
FWIW I managed to track down the Pinyin plugin (eventually replaced by the hanwriting plugin). The keyboard settings shows it as installed but it does not seem to do anything with it. Selecting just the plain "Chinese" option (no plugin) gives a memory error. There is probably enough stuff in the DroidSansFallback font to display some form of Chinese (the device Localization options include Chinese, after all) but that doesn't seem to make its way to the keyboard app.
I also located a copy of the MyAlpha app which is suggested as a "font problem" fixing thing. Doesn't seem to do anything.
So...I've attached both apps. Probably you should contact the developer. He/she might be able to give you the information we are apparently missing.
Click to expand...
Click to collapse
Thanks. I tried these apks too, plus some others. None worked. MyAlpha is for some other "rare" languages, Chinese or Latin languages are not included, since I guess they are already installed in most Android systems.
I already sent an email to the developer. Not sure though if he/she is still active in this development. Will report here if getting response from him/her.
Thread reboot begins in post #14: AIType Keyboard!
It was user @ALinkToTao who first acquainted me with Multiling Keyboard. I don't care much about the potential for other languages (and I think maybe the Hacker's Keyboard does a better job), but I do really like the secondary keyboard which gives access to the system paste buffer or clipboard. It's nearly impossible to find an application which will allow a long press on an item to copy it to the clipboard (the URL line in Opera Mini is a notable exception). I've found this very useful in moving from a text editor to, say, Tasker, or even Opera Mini. Anyway, the keyboard is not without issues.
The principal issue I would like to solve is the invisibility of key options on a long-press. For example, a long press of the "u" key should bring up the number "7" along with a variety of diacritical variations of "u". I've installed the keyboard on a small KitKat device and it does display properly, with a highlight rectangle that can be moved around before releasing and accepting the character. In that particular installation, the potential characters are displayed in a line, just like they "might" be if they were only visible. The background is always dark (as on the stock NST) and the character font is always white, regardless of the font color on the keyboard.
I've taken the app apart and inspected every xml reference to font colors. Changing them all to "black" or "white" depending on the theme (and even adding some) has had no effect. I have been able to change the background color of the rectangle which should show the key options, but that's it. The selection process does work, but it's blind.
Just to see if this is an e-ink thing, I installed the keyboard on the NST-CM11 ROM. I've shown side-by-side screenshots of the board on the stock ROM and the CM11 ROM. Although the configuration of the rectangle has changed for some reason, the function remains the same and clearly works on the CM11 ROM.
This leads me to suspect that this could be a framework issue. I hope not.
So, if anyone is interested in working on this with me, I'd really like the extra input. I've attached a copy of the (unaltered) apk.
If I had the know-how, I would help you. But I'm ignorant in these matters. Glad to hear that you're still at it. I still freaking love my Nook Simple Touch that you've helped me with. I've gifted dozens of those to my friends customized specifically for them. I still use that DesktopVisualizer app on my Atrix 4g and all my Nooks. Thank you brother.
ALinkToTao said:
If I had the know-how, I would help you. But I'm ignorant in these matters. Glad to hear that you're still at it. I still freaking love my Nook Simple Touch that you've helped me with. I've gifted dozens of those to my friends customized specifically for them. I still use that DesktopVisualizer app on my Atrix 4g and all my Nooks. Thank you brother.
Click to expand...
Click to collapse
Well, thank you for this keyboard which is nearly perfect for my use. Just this one niggling thing.
BTW, I finally worked out a way to make the RNMenu app user-customizable (within limits). If you still use it, you might want to take a look here.
Thanks I'll check that out, and yes I do use it!
Code:
C:\>adb install com.klye.ime.latin-1.apk
Performing Push Install
com.klye.ime.latin-1.apk: 1 file pushed, 0 skipped. 3.4 MB/s (949941 bytes in 0.265s)
pkg: /data/local/tmp/com.klye.ime.latin-1.apk
Failure [INSTALL_FAILED_INVALID_APK]
W/PackageManager( 809): Native ABI mismatch from package file
You might need to rename lib/armeabi to lib/armeabi-v7a
Renate said:
Code:
C:\>adb install com.klye.ime.latin-1.apk
Performing Push Install
com.klye.ime.latin-1.apk: 1 file pushed, 0 skipped. 3.4 MB/s (949941 bytes in 0.265s)
pkg: /data/local/tmp/com.klye.ime.latin-1.apk
Failure [INSTALL_FAILED_INVALID_APK]
W/PackageManager( 809): Native ABI mismatch from package file
You might need to rename lib/armeabi to lib/armeabi-v7a
Click to expand...
Click to collapse
Huh. I'll try that tomorrow morning. Thanks!
Renate said:
Code:
C:\>adb install com.klye.ime.latin-1.apk
Performing Push Install
com.klye.ime.latin-1.apk: 1 file pushed, 0 skipped. 3.4 MB/s (949941 bytes in 0.265s)
pkg: /data/local/tmp/com.klye.ime.latin-1.apk
Failure [INSTALL_FAILED_INVALID_APK]
W/PackageManager( 809): Native ABI mismatch from package file
You might need to rename lib/armeabi to lib/armeabi-v7a
Click to expand...
Click to collapse
That was interesting. I've actually never tried installing this as a user app. I've always just copied the apk file into /system/app and rebooted. There, it behaves just as you would expect a keyboard app to except for this annoying display issue.
It won't install on the original NST as a user app. Via ADB it gives the error you show above, with or without lib/armbei renamed to lib/armbei-v7a.
If I try to install via file manager it warns that another version already exists on the device (it doesn't) and then the installation fails.
So that's not the way to address this problem--but it is interesting.
Edit: oh, and if I rename the lib sub-folder and then place the apk file in /system/app as I normally would, it is ignored.
nmyshkin said:
with or without lib/armbei renamed to lib/armbei-v7a.
Click to expand...
Click to collapse
Spelling counts: armeabi-v7a
Work-in-progress (named "ThemeSpy")
Code:
01010036 android:attr/textColorPrimary -> 01060001 android:color/primary_text_dark -> "res/color/primary_text_dark.xml"
01010037 android:attr/textColorPrimaryDisableOnly -> 01060040 android:color/primary_text_dark_disable_only -> "res/color/primary_text_dark_disable_only.xml"
01010038 android:attr/textColorSecondary -> 01060005 android:color/secondary_text_dark -> "res/color/secondary_text_dark.xml"
01010039 android:attr/textColorPrimaryInverse -> 01060003 android:color/primary_text_light -> "res/color/primary_text_light.xml"
0101003a android:attr/textColorSecondaryInverse -> 01060007 android:color/secondary_text_light -> "res/color/secondary_text_light.xml"
0101003b android:attr/textColorPrimaryNoDisable -> 01060002 android:color/primary_text_dark_nodisable -> "res/color/primary_text_dark_nodisable.xml"
0101003c android:attr/textColorSecondaryNoDisable -> 01060006 android:color/secondary_text_dark_nodisable -> "res/color/secondary_text_dark_nodisable.xml"
0101003d android:attr/textColorPrimaryInverseNoDisable -> 01060004 android:color/primary_text_light_nodisable -> "res/color/primary_text_light_nodisable.xml"
0101003e android:attr/textColorSecondaryInverseNoDisable -> 01060008 android:color/secondary_text_light_nodisable -> "res/color/secondary_text_light_nodisable.xml"
0101003f android:attr/textColorHintInverse -> 01060032 android:color/hint_foreground_light -> #ff555555
Renate said:
Spelling counts: armeabi-v7a
Click to expand...
Click to collapse
Oh my...I hope I didn't do something that stupid
I'll check tomorrow morning...
Renate said:
Spelling counts: armeabi-v7a
Click to expand...
Click to collapse
Yes, it does, but I'm apparently more careful when working with Apktool than when typing a post. I had the change right in the app, but it is not recognized by the NST as a system app and will not install as a user app.
I've searched for other potential mentions of "armeabi" elsewhere in the app just to be sure something didn't have to be changed to be consistent, but there were none.
Square one.
Edit: it just gets weirder. I located three previous versions of the app. None will install as user apps, always claiming they will replace an existing app (there is none) and then failing to install. Placed in /system/app instead, they are ignored. Only version 1.1.7 behaves as a system app on the NST (but will not install as a user app). So it's this version or none I guess.
I'm wondering if this version (1.1.7) has not already been modified by someone. @ALinkToTao, do you remember where you got this version?
Ah. Something, maybe a thread to tug on.
There are a couple of T9/compact keyboard modes. On the first of these, a long-press shows the sort of thing that ought to appear on the standard keyboard with a long-press. See screenshot below.
So the thing is doable on the device, but for some reason it's not working on the full-size keyboard.
Time to look at the xml again...
If it doesn't install normally you'll have to show the logcat why.
My NST has props:
Code:
[ro.product.cpu.abi]: [armeabi-v7a]
My contemporary (but cheap) cellphone has props:
Code:
[ro.product.cpu.abi]: [armeabi-v7a]
[ro.product.cpu.abi2]: [armeabi]
[ro.product.cpu.abilist]: [armeabi-v7a,armeabi]
[ro.product.cpu.abilist32]: [armeabi-v7a,armeabi]
My Onyx Poke3 has props:
Code:
[ro.product.cpu.abi]: [arm64-v8a]
[ro.product.cpu.abilist]: [arm64-v8a,armeabi-v7a,armeabi]
[ro.product.cpu.abilist32]: [armeabi-v7a,armeabi]
[ro.product.cpu.abilist64]: [arm64-v8a]
Renate said:
If it doesn't install normally you'll have to show the logcat why.
Click to expand...
Click to collapse
Yours has props, mine has peeps (but only me).
This is one for the Journal of Irreproducible Results. I think I see part of the crazy message source now. I deleted the apk file from /system/app, removed the folder for the app from /data/data and removed the dalvik-cache entry for the app. Then I tried to install the app again as a user app, following the logcat. I saw no errors but a lot of shuffling around of stuff. I forgot that the package manager and i guess packages.xml would retain information of previous installations, so it all became sort of a mush.
But I did see in logcat that it was sorting out the change from a system app to a user app. It did not complain about the armaebi business but did remark on it. And it installed.
Next I did what all the old threads about keyboards say to do. I moved the apk file from /data/app to /system/app, fixed the permissions and rebooted. The app showed up in the drawer and functioned as before--sadly.
But.
I believe I have something better. Time for a thread reboot when I have more time.
"My child, the Duke of Plaza-Toro does not follow fashions--he leads them. He always leads everybody. When he was in the army he led his regiment. He occasionally led them into action. He invariably led them out of it."
--The Gondoliers
Time for a thread reboot!
Since the Multiling keyboard would not play nice with me, no matter what I tried to fix the issue with the long-press options display in the normal keyboard mode, my attentions began to wander. Somewhere in the dark recesses of the forum I found a reference to the AIType Keyboard app. I searched for an old copy, found it and began to test it out.
It has a more limited language range then the Multiling keyboard, but those other languages on the Multiling required an addon and the last time I tried to help someone with it, we could not get it to work. Also, there is no finger-tracing recognition (I'll really miss that!). I tried to track down a few language plugins for the AIType Keyboard, but the ones I found refused to install (Arabic, for example). As it is, it works fine with languages using a Latin or modified Latin alphabet, Greek, Korean (surprise), and languages using Cyrillic. Much of that probably has to do with what the NST can support. "Download" invitations in the initial part of Settings do not work. The app contains a custom certificate which I'm sure has long-since expired. I also suspect the language addons are not actually free, so even if you track down an old one, it's not going to work.
I could not figure out the "prediction" stuff (possibly because I don't care about it), so I won't say it does not work. The app can even read your text in the edit mode using TTS.
And yes, the long-press options work on all the keys in all the modes!
Also there are many different keyboard styles to choose and you can change the colors of many things. Alas the color changing is done with the typical graphical picker. While a hex value for the selection is shown immediately after it is chosen, if you take a peek at the preferences.xml file, the colors have been obfuscated for some reason. They look like signed twos complement. Don't get me started.
Anyway....I played around trying to get something clean, resembling the stock keyboard. In the end when I had what I wanted I noticed that the navigation arrows in the edit keyboard were nearly invisible, being white on a white background with just a ghostly outline. I therefore altered those few images to make them gray. No other changes (except the signature, of course) have been made. See screenshots below for what I came up with.
If you like the looks of what I did or want to use it as a point of departure, see the spoiler that follows. If you would rather have the original, un-modded app and work with it yourself, you can download it from here.
To install and use, just treat this as a user app. It can figure out what to do. If you decide you don't like it, uninstalling will give you back the stock keyboard.
Spoiler: Reproducing my settings
In order to use the provided xml file that will make the keyboard look like it does in the screenshots, you need to be able to control which keyboard the NST is using. Nook Color Tools can access the Android Input chooser, but you should not fool around with other stuff in there. Some things can cause a spontaneous factory re-image from which there is no escape (I speak from experience). Safer would be my Nook Settings app (shameless plug) which has an Input option in the System section.
Here's the sequence:
1. Install the AIType Keyboard app.
2. Tap on the app icon and allow the app to access the Input chooser. You select the new keyboard and "Finish" at the bottom of the screen. This should be sufficient to generate the xml file in /data/data/com.aitype.android/shared_prefs.
If you want to be sure, access the keyboard with something just for a bit.
3. Now bring up the Input chooser using the Nook Settings app or Nook Color Tools (I guess there is an ADB option too...). Select the stock keyboard.
4. Download and upzip the file containing the preferences xml file.
5. Copy this file into /data/data/com.aitype.android/shared_prefs, overwriting what is there. Permissions on the file should be rw-rw-r.
6. With the Input chooser, select the AIType Keyboard and you're good to go!
Edit: 7-30-22--Ah, nagware. You gotta hate it.... How to stop the "limited time only" nuisance that comes up too often when the keyboard opens? I played around with this awhile and discovered that a likely setting in the xml preferences file I attached seemed to do the trick. I changed a date to some time in 2025 and no more nags. After that, well, I'll just change it again. I've updated the zip in the downloads, but if you have already made settings changes and don't want to start over, you can do this yourself. Look for this line in the xml file:
Code:
<long name="next_expiration_reminder" value="1657490536337" />
Your actual value (extended date time format) may be a little different, but what you want to do is change the second digit to a "7" so the line looks like this:
Code:
<long name="next_expiration_reminder" value="1757490536337" />
You should do this by copying out the file, making the change and then copying back over the original file.