Related
So, I was watching an unboxing video of the D2 R2-D2 & noticed that an app "The Best of R2D2" was listed. I found it odd because, the MyDroidWorld ROM dump did not have this app. I did some more research and found that it's also missing 2 live wallpapers. So, to recap:
Missing Applications
http://www.youtube.com/watch?v=oSubLQgsj_M
The Best of R2D2
A launcher for the exclusive video
Missing Live Wallpapers
http://www.youtube.com/watch?v=YFpeMVSN9qQ
3D Millennium Falcon
"Touch the screen and watch the
Millennium Falcon fly thru the
asteroid field"
The Empire Strikes Back
"Tap your screen to view the
greatest moments from Star Wars:
Episode V"
I don't mean for this to sound like I'm not grateful for the rom dump (I now get to have some of the exclusive stuff on my regular Droid 2), I just wanted to point out that some things were missing.
The original MDW/TBH R2D2 Rom release has the live wallpapers and the cheesy binocular app, as well as the standard wallpapers... I don't recall really looking for (or caring about) the "Best of" video or the lightsaber app before deleting all of it with the rest of the bloat anyway. And thankfully Motoboy removed the annoying C3PO on all of my contacts that do not have a pre-existing photo!
Sorry to necro an old thread but this one comes up in search results and it seems like it hasn't been answered yet. I figured I should answer it in case anyone comes along from a search engine.
In addition to the missing apps listed by the OP, there's also a 15th wallpaper, Han Solo in Carbonite, that seems to be missing from the leaks.
The leaked wallpapers all have the same naming scheme:
StarWarsESB_asteroids.apk
StarWarsESB_Binoculars.apk (this is the AT-AT Binoculars app)
StarWarsESB_lightspeed.apk
StarWarsESB_R2D2.apk
StarwarsESB_spaceslug.apk
And are present in /system/app. You can copy them out of there once you're rooted.
However, the two missing wallpapers are named differently, but still in /system/app:
Asteroids.apk (this is the 3D Millennium Falcon wallpaper)
swipe.apk (this is the The Empire Strikes Back live wallpaper, not Swype)
However, when I copy them out, I get a "App not installed" message. If I ever figure this out, I'll update my guide with instructions on fixing it (see link below).
The missing static wallpaper is with all the others in:
/system/app/BlurHome.apk/res/drawable-hdpi/
(APK's are just zip files, so you can open them up and see inside)
The Best of R2D2 App is just a video player which automatically loads the video located at:
/system/media/video/startupvideo_en.3gp
But the app is a normal user app, not a system app, so it's apk isn't located in /system/app like the rest. You can back it up using Titanium Backup or Astro File Manager or whatever.
I figured this stuff out while writing a guide about ripping all the R2-D2 theme elements from the stock R2-Droid 2 and getting them working again in a ROM on the R2-D2. Here's a link if you want to know more:
http://www.droidforums.net/forum/dr...-r2-d2-droid-2-keep-all-r2-d2-theme-bits.html
Hello, I'm creating a Conversion Calculator App for a school project and I have gotten along pretty nicely. I started off using Radio buttons because my original intentions were to only do temperature (Celsius, Fahrenheit, Kelvin) but then I changed my mind and decided why not impress my professor and do all the English and metric conversions I can think of. Well, obviously that would be one HELL of a lot of radio buttons. I remember seeing, in an app, a popup window with a list view inside of it. I searched google but came up empty. Anyone have any idea how to do this?
Thanks guys!
*bump*
Anyone?
Has anyone tried both of these apps on your Iconia? Impressions, pros-cons of each one?
Which would you recommend?
Thanks,
docs to go here
I use docs to go.have had it a very long time.not tried the others in a very long time or on this tab.a full office suit.and other full featured also will come Indo think
You will find what you need here
http://forum.xda-developers.com/showthread.php?t=1085173&highlight=comparison
docs 2 go is on sale until 6/17 for $15, 50% off
The comparison link takes you to a great comparison review...a lot work done here! What I
I saw here was a reference to Polaris Office which seems to be only available on the Transformer. It sure looks like it would be nice to have on my Acer. Google search will take to the company's web site, but there is no download/purchase link. There are some YouTube videos showing in action.
I have found a version of Polaris that works (I have tested it). Some guy took it from the rom and posted it on the internet and I'm not sure if I'm allowed to post the link since it's not for our devices. I'll post the link if a mod gives us a green light.
I can just say that it works nicely and that it performs and looks way better than my paid version of Quickoffice. I'm actually sorry that I've bought it now.
Edit: Mod Edit: XDA rules prevent to use OEM apps outside any custom/stock Rom so link removed.If you want any OEM app just download any custom Rom that does include it.Here is the file[/URL] (instructions as to where to copy the libs are included). App works fine on my tablet but you do need root to copy the needed libs.
I thought Polaris was crap and avoided it for a while - now it's my go-to Office suite on Iconia.
I got it from another link, but just in case users come across this thread in search, if Polaris Office force-closes for you whenever you actually try and open something, it's usually because the permissions of the lib files you copied into /system/lib need to be updated.
You can do this using a free root browser like File expert (if I recall). Enable root exploring in its options, then pop into /system/lib and confirm the polaris office libs match the permissions of the surrounding files.
quickoffice HDpro for me and I like it....
Here's my take on QuickOffice HD
http://forum.xda-developers.com/showpost.php?p=15847398&postcount=5
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.