[Q] Swype installs but you cant enable - Kindle Fire General

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

Related

[ROOT][HOWTO] Disable Lockscreen Ads

WARNING: I am not responsible for any bricked devices caused by attempting this howto. If you haven't read this how to twice, and fully understand the requirements, then please don't attempt it.
Introduction (not important):
First, this may not be the best way to do this, and if someone knows a better way, I'll be happy to listen.
I kinda stumbled across this solution after trying the many other ways to solve the problem, but all the other ways seemed to have something incomplete with them and ended with no ADS, but no something else, like rotating lock screens or something.
I started with the assumption that the ADS program (dtcp) can be disabled through a flag somewhere on the system, for if you pay the extra $20 you get a kindle with no ADS, but same Android build. After looking through lots of sqlite databases I found it in the com.android.providers.settings/settings.db file.
Prerequisites:
Basic knowledge of databases
SQLite Editor Pro (Free on 1Mobile Market)
DroidWall
Steps:
Open SQLite Editor
Open "Settings Storage" (com.android.providers.settings)
Open settings.db
open "global" table
Highlight entry "IS_DTCP_ENABLED"
Click the Edit Record button at the top
Change the value from a 1 to a 0
Click Save
Go back
Make same change on the "secure" table
Reboot kindle for new options to take effect.
Other Thoughts:
This just changes the value temporarily until the device checks back in with Amazon and then the value will get overridden again with the correct value. To prevent that install DroidWall and whitelist only the applications you need to access the internet. DroidWall requires root, which is why root is in the subject. But you should be doing this anyways to prevent OTA updates.
cool
Does this mean that you will now get the rotating native wallpapers that you would have if you paid for the dismissal of the ads? Currently I use adaway on my s4 hotspot and the only one I blacklist is (spectrum.s3.amazonaws.com) this has blocked updates because I am still on old software with no other blocking in place and I have noticed it also has blocked rotateing ads accept I have the same 1 at all times.
Edit: YAY !!!! and yes I now have rotating native wallpapers
Btw thank you for sharing and it is quite refreshing to see a new member join to share useful information in a well thought out and presented OP and not just join to start a thread with a question that is the heading of so many other threads that has been beat to death already..burying perfectly good information..thank you for joining us at XDA!
Awesome!!!! have been looking for a way to do this without factory reset for a while! You da man! Gonna spam that thanks button for a while lol
Thanks so much, that was easy!
Mind after a few days .2 went straight black lock screen
Anyone know what exactly I need to enable in droidwall to have internet but no ota updates or Amazon changing the lock screen back to ads?
Uhg
This mod works fine. No ads, rotating wallpapers appear every time. No reversion to black screen. No need for Droidwall. Use of Droidwall is impractical for this purpose. Who knows what not to include in some giant white list?
It appears that the wallpapers will continue to appear without reversion if you have blocked updates using the root kit.
earlgrey_44 said:
This mod works fine. No ads, rotating wallpapers appear every time. No reversion to black screen. No need for Droidwall. Use of Droidwall is impractical for this purpose. Who knows what not to include in some giant white list?
It appears that the wallpapers will continue to appear without reversion if you have blocked updates using the root kit.
Click to expand...
Click to collapse
Sorry, what's the root kit?
dras99 said:
Sorry, what's the root kit?
Click to expand...
Click to collapse
First link in this post:
http://forum.xda-developers.com/showpost.php?p=53451623&postcount=3
I assume the block update action from the rootkit is responsible for the lack of reversion to ads since I haven't done anything else except the steps I outlined in the post and the data base tweaks explained above. My kindle has been running for 5 days now without ads and with the startup wallpaper.
earlgrey_44 said:
First link in this post:
http://forum.xda-developers.com/showpost.php?p=53451623&postcount=3
I assume the block update action from the rootkit is responsible for the lack of reversion to ads since I haven't done anything else except the steps I outlined in the post and the data base tweaks explained above. My kindle has been running for 5 days now without ads and with the startup wallpaper.
Click to expand...
Click to collapse
I also blocked updates with the root kit. Then I followed this tutorial and it worked great however it did revert back to adds after a reboot or 2.
conan1600 said:
I also blocked updates with the root kit. Then I followed this tutorial and it worked great however it did revert back to adds after a reboot or 2.
Click to expand...
Click to collapse
Strange! What's different about my install I wonder?
earlgrey_44 said:
Strange! What's different about my install I wonder?
Click to expand...
Click to collapse
I'm left scratching my head over that as well. Tomorrow I will re run the ota block script as I'm now concerned that it perhaps did not do something correctly. I did check for updates and it says last update failed but better safe than sorry. I DO NOT want to end up getting updated again. I finally have this tablet running rather nicely and am quite satisfied with most aspects. Still need much more customization options but it's serviceable now. And this tablet has always had the best touch input response of any I've ever used. I'd hate to have to throw it back in the closet.
I am getting now BLACK SCREENS. Any way to change this?
Script
For anyone who wants to run this from command line (e.g. on reboot or network change event) you can create a script like below and use SManager to run it periodically. You will first need to install sqlite3 binary (google "SQLite Installer for Root").
Here is the script that needs to be executed as root:
Code:
#!/system/bin/sh
sqlite3 -batch /data/data/com.android.providers.settings/databases/settings.db "update global SET value='0' where name='IS_DTCP_ENABLED'";
sqlite3 -batch /data/data/com.android.providers.settings/databases/settings.db "update secure SET value='0' where name='IS_DTCP_ENABLED'";

[Q] How to set intent on the Nook Simple Touch to open "Reading Now"?

I am not at all a wizard in code, so if anyone could help me set an intent to open "reading now" on the Nook Simple Touch, that would be really helpful. I'm using it to have a "reading now" link on my desktop with an app. It lets me copy and paste any intent I want into it, and I thought this one would be handy. The app is Desktop VisualiseR.
ALinkToTao said:
I am not at all a wizard in code, so if anyone could help me set an intent to open "reading now" on the Nook Simple Touch, that would be really helpful. I'm using it to have a "reading now" link on my desktop with an app. It lets me copy and paste any intent I want into it, and I thought this one would be handy. The app is Desktop VisualiseR.
Click to expand...
Click to collapse
I have it, but not with me. Search the forum for Reading Now. It's there somewhere. Or when I return from vacation...
Edit: https://forum.xda-developers.com/showpost.php?p=20046625&postcount=5
nmyshkin said:
I have it, but not with me. Search the forum for Reading Now. It's there somewhere. Or when I return from vacation...
Edit: https://forum.xda-developers.com/showpost.php?p=20046625&postcount=5
Click to expand...
Click to collapse
Thanks brother. I appreciate it.
No hurry on a response, but I'm still trying to figure this out.
So what I'm trying to do is use Desktop VisualizeR to open the reader via the "Reading Now" Intent. I am making a very simple and intuitive browser like the one you have made, @nmyshkin for my friends and family who are not at all techie.
Here that post you referred me to below:
ros87 said:
No, not directly in Reader, but you can do it like this:
Code:
am broadcast -a com.bn.nook.launch.LAST_BOOK -n com.bn.nook.home/.HomeBroadcastReceiver
Click to expand...
Click to collapse
Here is a desktop I'm playing with. These images won't be the final product, but I would like to make an eye image that directly opens "Reading Now"
In the Desktop VisualizeR Widget, I go to "Select Action"-->"Clipboard" (with this exact text copied in the clipboard without quotes: "am broadcast -a com.bn.nook.launch.LAST_BOOK -n com.bn.nook.home/.HomeBroadcastReceiver" )
All I get are two options which pertain to "MX Player" which is merely a video player I have installed. Choosing either one of these and tapping to widget to run it yields no results. Is there a particular way to format the intent for Desktop VisualizeR to run it?
By the way, this homescreen thing is looking awesome! Here is what I've got now!
So I've been messing with using SMWidgets to create a shortcut with the "Eye" symbol on my desktop using this procedure here:
https://forum.xda-developers.com/showthread.php?t=1509030
Here were my results:
I was disappointed to find that the reader app did not launch, and the Script Manager app stayed with that message. I don't honestly know what it means. Anyone know what would be better to input?
ALinkToTao said:
In the Desktop VisualizeR Widget, I go to "Select Action"-->"Clipboard"/B]
Click to expand...
Click to collapse
Just got into Cairo. You've been busy. To my knowledge the clipboard does not work on the NST, at least not for me, so there's one thing.
I can easily create an app with Tasker that does the Reading Now thing. But not without my NST. Would that work?
nmyshkin said:
Just got into Cairo. You've been busy. To my knowledge the clipboard does not work on the NST, at least not for me, so there's one thing.
I can easily create an app with Tasker that does the Reading Now thing. But not without my NST. Would that work?
Click to expand...
Click to collapse
It would, for sure!
I have gotten the clipboard to work in the attempt to do this! It works with the attached keyboard app "Multiling Keyboard". There is an option to switch to a keyboard that has arrow keys, select all, copy, paste, cut, delete, etc.
nmyshkin said:
Just got into Cairo. You've been busy. To my knowledge the clipboard does not work on the NST, at least not for me, so there's one thing.
I can easily create an app with Tasker that does the Reading Now thing. But not without my NST. Would that work?
Click to expand...
Click to collapse
What might be better is if you're going to use tasker, to send me a backup of the macro that you create for the reading now action. That may suffice instead of writing a whole new app. I will probably install tasker since I already have so many tasker apps running it may save some RAM that way, not sure. I can also use tasker for other options on the desktop like toggling wifi etc. The attached version of tasker is the one I know is the latest and best for the NST.
Whichever is easier for you to do is whatever works for me. I really appreciate your help, and hope you have a wonderful and unforgettable trip in Cairo.
ALinkToTao said:
What might be better is if you're going to use tasker, to send me a backup of the macro that you create for the reading now action. That may suffice instead of writing a whole new app. I will probably install tasker since I already have so many tasker apps running it may save some RAM that way, not sure. I can also use tasker for other options on the desktop like toggling wifi etc. The attached version of tasker is the one I know is the latest and best for the NST.
Whichever is easier for you to do is whatever works for me. I really appreciate your help, and hope you have a wonderful and unforgettable trip in Cairo.
Click to expand...
Click to collapse
Yeah, when I get home. In the meantime you might try just
com.bn.nook.launch.LAST_BOOK
as the intent. Seems like that's what's in the RN Menu app, although that might be in a shell which I'm not seeing. Not sure of the intent format for DesktopVisualizer.
nmyshkin said:
Yeah, when I get home. In the meantime you might try just
com.bn.nook.launch.LAST_BOOK
as the intent. Seems like that's what's in the RN Menu app, although that might be in a shell which I'm not seeing. Not sure of the intent format for DesktopVisualizer.
Click to expand...
Click to collapse
Thank! I'll try that and let you know.
ALinkToTao said:
I was disappointed to find that the reader app did not launch, and the Script Manager app stayed with that message.
Click to expand...
Click to collapse
You don't have to put the component name in, that is no "-n com.bn....."
The broadcast receiver component might have changed in different versions.
The newer Nooks seem to use com.bn.nook.intent.action.OPEN_LAST_READ_BOOK
ALinkToTao said:
What might be better is if you're going to use tasker, to send me a backup of the macro that you create for the reading now action. That may suffice instead of writing a whole new app. I will probably install tasker since I already have so many tasker apps running it may save some RAM that way, not sure. I can also use tasker for other options on the desktop like toggling wifi etc. The attached version of tasker is the one I know is the latest and best for the NST.
Whichever is easier for you to do is whatever works for me. I really appreciate your help, and hope you have a wonderful and unforgettable trip in Cairo.
Click to expand...
Click to collapse
OK, so here is a simple little app and the xml task file that is used to create it. You can, of course, assign a different icon using DesktopVisualiser.
Awesome, man! I will try it!
ALinkToTao said:
I have gotten the clipboard to work in the attempt to do this! It works with the attached keyboard app "Multiling Keyboard". There is an option to switch to a keyboard that has arrow keys, select all, copy, paste, cut, delete, etc.
Click to expand...
Click to collapse
I've installed this but can't figure out what to do with it! The first "step" (1. Enable Multiling) says it cannot do an autosetup so see the FAQ. This I did, but nowhere can I find anything about how to proceed with the app
Any pointers on set-up or somewhere you can point me that actually tells you how to do it?
@nmyshkin Here's a way to easily access the copy paste function when typing: In the multiling app go to "keyboard settings" then go to "gestures" each section you see here refers to a different swipe on the keyboard ims over the keys when its active. I know the second one programs a swipe to the right and the fourth is a swipe left. Program one of these to "toggle mode". Swipe your gesture when ims is active.
You will see what you want here.
Swipe again to switch back to QWERTY keyboard.
Try that.
ALinkToTao said:
@nmyshkin Here's a way to easily access the copy paste function when typing: In the multiling app go to "keyboard settings" then go to "gestures" each section you see here refers to a different swipe on the keyboard ims over the keys when its active. I know the second one programs a swipe to the right and the fourth is a swipe left. Program one of these to "toggle mode". Swipe your gesture when ims is active.
You will see what you want here.
Swipe again to switch back to QWERTY keyboard.
Try that.
Click to expand...
Click to collapse
Yeah, I finally figured all that out. My big hurdle was how to get the NST to use the keyboard instead of stock. It can be done using sqlite but I ended up using Nook Color Tools for the first (and last) time and in the process initiating an erase/deregister which made me very unhappy
Having trouble with the dictionary plugin at the moment. I have the keyboard app in system/app but installed the dictionary plugin as normal. Maybe that was a mistake.
But...it's almost back to where it was before the event, then I'll make a more current backup.
Edit: I finally got the dictionary plugin so that it's not whining about memory issues, but it does not seem to do anything.
More importantly, I can only seem to select ALL when using copy/paste. Is there a way to select only part of something? Also the function does not work in all contexts, for example in Documents to Go.
Edit-Edit: Well, I figured out the selection process for copy/paste. Who knew the "shift" key was needed to bound the area to copy? I'm sure this keyboard can do lots of things but it's profoundly lacking in any material to explain how they can be done. Still can't get the word suggestions to work, which is probably just as well since I immediately turn that off on my other devices.
I tried to get word suggestions to work for that keyboard, as it's my go-to keyboard on my Atrix 4g, but it never worked for me on the NST. If it did, that would be my daily user. I use ICS keyboard which actually has autocorrect. It's the only one I know of that works for it. If multiling had autocorrect, I wouldn't switch between the two on the NST.
ALinkToTao said:
I tried to get word suggestions to work for that keyboard, as it's my go-to keyboard on my Atrix 4g, but it never worked for me on the NST. If it did, that would be my daily user. I use ICS keyboard which actually has autocorrect. It's the only one I know of that works for it. If multiling had autocorrect, I wouldn't switch between the two on the NST.
Click to expand...
Click to collapse
Mmm....OK. Whilst looking for an "ICS keyboard" in the YalpStore I was bemused to find that while I had typed "ics keyboard" what appeared in the search box was "Icarus keyboard". First time I noticed something like that and exactly why I always turn this "feature" off on all my devices. Perhaps removing the plugin will squelch that behavior.
Meanwhile, can you give me a link for the ICS keyboard you mention?
Edit: On further investigation, there is definitely auto"correction" going on as I type. What is missing is the typical display of potential substitutions and therefore any way to specify a choice. It just does what it wants by its own arcane rules.
In addition to having the English plugin installed, in the Settings for the Multiling keyboard under "Word suggestion settings" I originally had the first three selections checked as well as "Quick fixes" and "User dictionary". For me, this produced the behavior described.
I was able to stop auto"correct" by unchecking the first two options. This greyed-out everything else in the category.
nmyshkin said:
Mmm....OK. Whilst looking for an "ICS keyboard" in the YalpStore I was bemused to find that while I had typed "ics keyboard" what appeared in the search box was "Icarus keyboard". First time I noticed something like that and exactly why I always turn this "feature" off on all my devices. Perhaps removing the plugin will squelch that behavior.
Meanwhile, can you give me a link for the ICS keyboard you mention?
Edit: On further investigation, there is definitely auto"correction" going on as I type. What is missing is the typical display of potential substitutions and therefore any way to specify a choice. It just does what it wants by its own arcane rules.
In addition to having the English plugin installed, in the Settings for the Multiling keyboard under "Word suggestion settings" I originally had the first three selections checked as well as "Quick fixes" and "User dictionary". For me, this produced the behavior described.
I was able to stop auto"correct" by unchecking the first two options. This greyed-out everything else in the category.
Click to expand...
Click to collapse
I'm so sorry I haven't responded to your request for this. I've been busy building a house (a tiny house) to live in for my girlfriend and I. It's coming along very well, I have to say.
I've attached the apk file.
ALinkToTao said:
I'm so sorry I haven't responded to your request for this. I've been busy building a house (a tiny house) to live in for my girlfriend and I. It's coming along very well, I have to say.
I've attached the apk file.
Click to expand...
Click to collapse
Thanks. I'll take a look at it. I gave up on the other alternate keyboard. While it was able to copy and paste within an app, it didn't seem to have true clipboard capabilities to carry a line of text or a URL from one app to another. That's what I'd really like.

[Q] Fire HD8 (2018) w/ Play Store - app recognises it isn't Google, won't run.

The tablet is owned by someone else and they want to use one app called Landscape Magazine. On the Nexus 7 it runs fine but the battery just went on it and I'm having issues sourcing a replacement battery in the UK so that's where the HD8 comes in. I thought I could just put the Play Store on (plus framework etc) and it would be ok for them. It downloads the app fine, all others work fine but when I try to launch this one app it says it only works on Android tablets. I don't know why they'd code it that way but it is what it is.
Can anyone tell me if there's some way to get an app to run if it's throwing up an error like this?
Dyonas said:
The tablet is owned by someone else and they want to use one app called Landscape Magazine. On the Nexus 7 it runs fine but the battery just went on it and I'm having issues sourcing a replacement battery in the UK so that's where the HD8 comes in. I thought I could just put the Play Store on (plus framework etc) and it would be ok for them. It downloads the app fine, all others work fine but when I try to launch this one app it says it only works on Android tablets. I don't know why they'd code it that way but it is what it is.
Can anyone tell me if there's some way to get an app to run if it's throwing up an error like this?
Click to expand...
Click to collapse
Not easily. It would take experimentation to determine which device or rom characteristic(s) are trigging the behavior followed by additional fiddling to entice the app to run. Tethering that Nexus 7 to a slim power bank may be the best solution.
NEED ROOTED.
/system/build.prop
ro.product.brand = Amazon
ro.product.manufacturer = Amazon
Change to 'Google' or etc.
I think amazon is banned by the app.
The exact error message is "This app is only suitable for the Android platform."
Didn't see the pictures attached by @erono. If you root the tablet (or may be possible in temp root shell) and change the keys he mentioned, the app works after reboot.
Thanks all for replying, especially erono who seems to have found the solution. I'll see what I can do with it because my understanding is that there is still no major Android build for the 2018 HD8. I have a starting point if nothing else and that's more than I had before!
Dyonas said:
Thanks all for replying, especially erono who seems to have found the solution. I'll see what I can do with it because my understanding is that there is still no major Android build for the 2018 HD8. I have a starting point if nothing else and that's more than I had before!
Click to expand...
Click to collapse
You could always root it and just edit BuildProp (excellent guide by bibikalka) . As far as other ways, I'm not knowledgeable enough to know any alternatives. Maybe without root, you might be able to pull BuildProp from the elevated shell and push it back after changing the lines. I'm sure there would be some permissions changes required. Hopefully someone with a bit more experience pops in and can guide you if rooting isn't an option.
nujak said:
You could always root it and just edit BuildProp (excellent guide by bibikalka) . As far as other ways, I'm not knowledgeable enough to know any alternatives. Maybe without root, you might be able to pull BuildProp from the elevated shell and push it back after changing the lines. I'm sure there would be some permissions changes required. Hopefully someone with a bit more experience pops in and can guide you if rooting isn't an option.
Click to expand...
Click to collapse
No need to modify build.prop nor will any notable gains be realized by doing so. Simply follow the guides as written.
Davey126 said:
No need to modify build.prop nor will any notable gains be realized by doing so. Simply follow the guides as written.
Click to expand...
Click to collapse
Yeah, sorry I meant in specific context to having that particular app work on the HD 8 2018. Thanks to @erono (and testing it myself) Lanscape Magazine works with changing brand and manufacturer values in the BuildProp. I know it's possible and easy to do with root. I'm just not knowledgeable enough to know any other methods.
Method without root:
Use 'App Cloner (pro version)' create an cloned app.
You can modify MANUFACTURER and BRAND in 'Developer options -> Build props'.
App was modified, you can't update in Google Play Store or purchase any paid content.
This is not a good way.

NST keyboard for other languages

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.

Looking for help with modding Multiling keyboard

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.

Categories

Resources