Database Users

[Q] Swype installs but you cant enable

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

In search of minimal system .apk

Hello,
I have decided to try and find exactly what .apk I can remove from a freshly rooted system using NookManager. At this time;
Disabled:
Accessories.apk
AccountAndSyncSettings.apk
AFfileDownloadService.apk
AirRuntime.apk
BnAuthenticationService.apk
BnCloudRequestSvc.apk
CloudService.apk
ContactsProvider.apk
DemoMode.apk
DeviceManager.apk
DeviceRegistrator.apk
DownloadAdmin.apk
Gallery.apk
GoogleSearch.apk
Home.apk
Launcher.apk
Library.apk
Music.apk
NookCommunity.apk
NookHWTest.apk
Oobe.apk
Phone.apk
PicoTts.apk
QuickStartActivity.apk
ReaderRMSDK.apk
ServiceOne.apk
Shop.apk
Social.apk
SysChecksum.apk
TelephonyProvider.apk
ThumbnailService.apk
TtsService.apk
WaveformDownloader.apk
Enabled:
ApplicationsProvider.apk
Browser.apk
CertInstaller.apk
CryptoServer.apk
DownloadProvider.apk
DrmProvider.apk
GlobalSearch.apk
HTMLViewer.apk
LatinIME.apk
MediaProvider.apk
PackageInstaller.apk
Settings.apk
SettingsProvider.apk
UserDictionaryProvider.apk
-Problems so far:
1) Under Settings->Device Info->About Your Nook field 'Software version' is listed as 'Unavailable'
2) The quick launch is still displayed - What .apk disables this?
3) Graphical layout of No-frills CPU Control slightly impaired - Usable but something has broken it.
Can you help with any of the above?
I have tried disabling other .apk files however I was a little too ambitious and ended up with many more problems and a boot loop so I intend to be a little more systematic. I would like to find the bare minimum that is required. I will keep this thread updated but appreciate any help that can be given.
Thank you.

LavaChild0809 said:
1) Under Settings->Device Info->About Your Nook field 'Software version' is listed as 'Unavailable'
Click to expand...
Click to collapse
Maybe DeviceManager.apk, maybe AccountandSyncSettings.apk - I think you'll just need to try renabling things until it works.
LavaChild0809 said:
2) The quick launch is still displayed - What .apk disables this?
Click to expand...
Click to collapse
Its not in an .apk. B&N buried it in the system framework. Unless your quest for minimalism takes you to baksmali system jars, rip out code and smali then you can just use Nook Touch Mod Manager (installed with NookManager) to remap your n key to whatever you want it to do.

straygecko said:
Maybe DeviceManager.apk, maybe AccountandSyncSettings.apk - I think you'll just need to try renabling things until it works.
Its not in an .apk. B&N buried it in the system framework. Unless your quest for minimalism takes you to baksmali system jars, rip out code and smali then you can just use Nook Touch Mod Manager (installed with NookManager) to remap your n key to whatever you want it to do.
Click to expand...
Click to collapse
Thanks for the tips, I'll give it a shot. My only reason for messing with the .apk is that I'd like to maximise battery life. I've read about Phone and TelephonyProvider and so I gathered while there I may as well remove other stuff. My intention is definitely not to remove anything that other applications may have dependancies on - It's real tough knowing so I might just end up leave them all there. Do you know of any application (or perhaps a different systematic way) that will (somehow - not sure if possible) work out the dependancy of installed apps and list those that can be removed?
Additionally, on my first attempt at removing .apk I was a little too over ambitious and in addition to the list of 'Disabled' apps I also disabled:
ApplicationsProvider.apk
Browser.apk
CryptoServer.apk
DownloadProvider.apk
DrmProvider.apk
GlobalSearch.apk
HTMLViewer.apk
MediaProvider.apk
SettingsProvider.apk
UserDictionaryProvider.apk
One of these caused the quick launch to disappear - Whether that is because one of those .apk actually contains the quick launch or because quick launch is dependant on one of these to function I do not know... I suppose I could go remove one of these at a time and see which is responsible.
The only reason I'm against trying each one at a time is it very time consuming to remove and reboot between each (let alone then testing everything I can think of to check for any misbehaviour!).
Thanks

When I got my NST I spent a bit of time doing exactly the same thing you are doing.
In my System/app folder I have the following:
ApplicationsProvider.apk
BnCloudRequestSvc.apk <------ I did this a while ago, so I can't remember why I left this one in....
DeviceManager.apk <------ again, I can't remember why I left this in...
LatinIME.apk
PackageInstaller.apk
ReaderRMSDK.apk <---- built in reader app. I don't like the look of any other epub reader. I use Renate's amazing library app with this.
Settings.apk
SettingsProvider.apk
UserDictionaryProvider.apk
Note: I don't use ANY of B&N's services.
I don't have Browser.apk as I use Opera instead xD
I have had no problems with this setup: I've been using this for the last ~3 months with no crashes/reboots etc.
HOWEVER there is an apk missing: In this state my NST refuses to go to deep sleep when I let it go to sleep.
As for the QuickNav, while I dont use it (and is disabled by Nook Touch Mod Manager on my NST) I can confirm that these apk have QuickNav.
I would continue to experiment, but I no longer have the time. If someone could work out of the remaining apks which would allow deep sleep, and whether BnCloudRequestSvc and DeviceManager are necessary, I would be eternally grateful :good:

chowy993 said:
When I got my NST I spent a bit of time doing exactly the same thing you are doing.
In my System/app folder I have the following:
ApplicationsProvider.apk
BnCloudRequestSvc.apk <------ I did this a while ago, so I can't remember why I left this one in....
DeviceManager.apk <------ again, I can't remember why I left this in...
LatinIME.apk
PackageInstaller.apk
ReaderRMSDK.apk <---- built in reader app. I don't like the look of any other epub reader. I use Renate's amazing library app with this.
Settings.apk
SettingsProvider.apk
UserDictionaryProvider.apk
Note: I don't use ANY of B&N's services.
I don't have Browser.apk as I use Opera instead xD
I have had no problems with this setup: I've been using this for the last ~3 months with no crashes/reboots etc.
HOWEVER there is an apk missing: In this state my NST refuses to go to deep sleep when I let it go to sleep.
As for the QuickNav, while I dont use it (and is disabled by Nook Touch Mod Manager on my NST) I can confirm that these apk have QuickNav.
I would continue to experiment, but I no longer have the time. If someone could work out of the remaining apks which would allow deep sleep, and whether BnCloudRequestSvc and DeviceManager are necessary, I would be eternally grateful :good:
Click to expand...
Click to collapse
Hello! Could you please tell me how you know it does not go to 'deep sleep'? I'd like to know how to check this to keep an eye out and ensure I also do not break this behaviour. Thank you!

I don't have either of my Nooks with me at work today so I can't check which .apks I still have on them. However, I can suggest the method I used to get to where I am....
I installed "Go TaskManager EX", this app allows you to see what is running and kill processes you don't want. With this app, I was able to find some .apks that start automatically that perform services that I don't use. (Example: Social.apk) So I have moved all .apks for services that start automatically to a directory I created called /system/archive. (This way I still have a copy on the device, making restoration easier just in case.) I have left .apks in /system/apps that I don't use as long as I don't find them starting up automatically. My rational is that if it does not start automatically, then it is not using battery. I will try to remember to check my Nooks and post what .apks I have left tomorrow.

David0226 said:
I don't have either of my Nooks with me at work today so I can't check which .apks I still have on them. However, I can suggest the method I used to get to where I am....
I installed "Go TaskManager EX", this app allows you to see what is running and kill processes you don't want. With this app, I was able to find some .apks that start automatically that perform services that I don't use. (Example: Social.apk) So I have moved all .apks for services that start automatically to a directory I created called /system/archive. (This way I still have a copy on the device, making restoration easier just in case.) I have left .apks in /system/apps that I don't use as long as I don't find them starting up automatically. My rational is that if it does not start automatically, then it is not using battery. I will try to remember to check my Nooks and post what .apks I have left tomorrow.
Click to expand...
Click to collapse
That would be great - Thank you!

LavaChild0809 said:
Hello! Could you please tell me how you know it does not go to 'deep sleep'? I'd like to know how to check this to keep an eye out and ensure I also do not break this behaviour. Thank you!
Click to expand...
Click to collapse
I use a free app called CPU Spy. It shows you what states the CPU has been in over time. If you can't access the play store on your NST, I've put it in the attachments.
I first got suspicious when I noticed at some point that my NST drained battery really fast compared to pre-root status. So I installed CPU spy, and that told me that the device wouldn't go into deep sleep.
I look forward to seeing your results in what APKs are the minimal requirements.

David0226 said:
I don't have either of my Nooks with me at work today so I can't check which .apks I still have on them. However, I can suggest the method I used to get to where I am....
I installed "Go TaskManager EX", this app allows you to see what is running and kill processes you don't want. With this app, I was able to find some .apks that start automatically that perform services that I don't use. (Example: Social.apk) So I have moved all .apks for services that start automatically to a directory I created called /system/archive. (This way I still have a copy on the device, making restoration easier just in case.) I have left .apks in /system/apps that I don't use as long as I don't find them starting up automatically. My rational is that if it does not start automatically, then it is not using battery. I will try to remember to check my Nooks and post what .apks I have left tomorrow.
Click to expand...
Click to collapse
Would it be possible to post what .apk you have left please? Thanks!
chowy993 said:
I use a free app called CPU Spy. It shows you what states the CPU has been in over time. If you can't access the play store on your NST, I've put it in the attachments.
I first got suspicious when I noticed at some point that my NST drained battery really fast compared to pre-root status. So I installed CPU spy, and that told me that the device wouldn't go into deep sleep.
I look forward to seeing your results in what APKs are the minimal requirements.
Click to expand...
Click to collapse
I'll be sure to give this a try - Thank you.

LavaChild0809 said:
Would it be possible to post what .apk you have left please? Thanks!
Click to expand...
Click to collapse
I am not sure you want me to at this point. Before posting earlier in the week I tried to remove a few others and got my Nook so messed up that I had to do a "factory reset" about six times. So I obviously removed too much.
I also believe that how much you can remove depends upon whether you want to be able to read books with B&N DRM. I "think" my Nook got messed up when I remove AirRuntime.apk and then tried to use the stock library. The library never loaded and the screen just kept flashing black/white, black/white. I had to power off by pushing the power button for 20 seconds and even restoring AirRuntime did not work. So I had to restore from the factory zip image.
That was a long explanation to say that at this point I don't trust what I have done and to reiterate the making a backup before trying any thing like this is critical.

Just a note regarding your experimentation:
All the .apks are part of the Android system, not the underlying Linux.
You should always be able to get through to a shell on ADB.
The screen might be showing wackiness but ADB should still be working.
When playing around, "start" and "stop" in ADB should be your friends.
Code:
# stop [color=red]// stop the Android subsystem[/color]
# mv whatever.apk whatever.bak [color=red]// modify something[/color]
# start [color=red]// start the Android subsystem[/color]

David0226 said:
I am not sure you want me to at this point. Before posting earlier in the week I tried to remove a few others and got my Nook so messed up that I had to do a "factory reset" about six times. So I obviously removed too much.
I also believe that how much you can remove depends upon whether you want to be able to read books with B&N DRM. I "think" my Nook got messed up when I remove AirRuntime.apk and then tried to use the stock library. The library never loaded and the screen just kept flashing black/white, black/white. I had to power off by pushing the power button for 20 seconds and even restoring AirRuntime did not work. So I had to restore from the factory zip image.
That was a long explanation to say that at this point I don't trust what I have done and to reiterate the making a backup before trying any thing like this is critical.
Click to expand...
Click to collapse
That's some useful feedback all the same - It really is making me consider whether it's worth all of the fuss. I do have a backup, thankfully, and I've used it numerous times but none the less I can imagine I case where the vast majority of .apk will need to be kept in any case. If nothing else, I think the list of what can/cannot be removed will vary widely between users depending on their needs. Personally I have no use for *anything* B&N apart from the Reader. Even then, it's hard to know what minor breakages might be related to removing a particular .apk which you may not notice until a later date (by which time you'll perhaps have removed (or added) more). Definitely needs a more systematic approach than trial and error, I fear.
Renate NST said:
Just a note regarding your experimentation:
All the .apks are part of the Android system, not the underlying Linux.
You should always be able to get through to a shell on ADB.
The screen might be showing wackiness but ADB should still be working.
When playing around, "start" and "stop" in ADB should be your friends.
Code:
# stop [color=red]// stop the Android subsystem[/color]
# mv whatever.apk whatever.bak [color=red]// modify something[/color]
# start [color=red]// start the Android subsystem[/color]
Click to expand...
Click to collapse
Now that's some useful information - Thank you.

DeviceManager.apk does not work without BnCloudRequestSvc.apk and CloudService.apk. Without DeviceManager.apk no information device info.
Without CloudService.apk appear error in log...

khseal said:
DeviceManager.apk does not work without BnCloudRequestSvc.apk and CloudService.apk. Without DeviceManager.apk no information device info.
Without CloudService.apk appear error in log...
Click to expand...
Click to collapse
So have you worked out exactly what can be removed and what cannot? Can you give a full list? Thanks for the help so far!

LavaChild0809 said:
So have you worked out exactly what can be removed and what cannot? Can you give a full list? Thanks for the help so far!
Click to expand...
Click to collapse
I recently purchased Nook. I test and see the relationship. I will write what services should be left when I've finished experimenting.

Sounds great - I'm sure lots of people would be very very interested!

Sounds great - I'm sure lots of people would be very very interested!
Click to expand...
Click to collapse
I think the systems applications are not heavily loaded device.
So in these operations delete system applications, do not big sense. A little more memory and little more bugs.

khseal said:
I think the systems applications are not heavily loaded device.
So in these operations delete system applications, do not big sense. A little more memory and little more bugs.
Click to expand...
Click to collapse
So are there any you would recommend removing or none at all? Thanks!

There are some I know can be deleted. The telephone related ones obviously and DemoMode.apk. I am not sure removing these will do anything but speed up the boot time from complete power off. As the Nook has no native sound capability, I believe you can also delete PicoTts.apk, Music.apk and TtsService.apk, but again I am not sure that will help improve battery life.

Does anybody know which .apk is responsible for the 'recommend to a friend' (or similar) notifications? And are there are side-effects/implications to removing this apk? It's definitely the most annoying!

Secret apps list found in Home menus!

After I used terminal emulator with the pm disable function to disable both Gamecircle apps,Amazon Video,Photos (screensaver usage),and the Amazon AppStore,and resetting with ctrl+alt+del,I found a nice little surprise in the apps tab on the Home screen.
When I went to the Apps section,the list of all my installed apps appeared on the right!
When selecting them,they open immediately,but I can't long press to view the details of an app.
However,since they are still in the settings menu as well,I can still view the details from there.
The only issue with it is that it is a little buggy with scrolling through apps.
You can figure out the com-names using 7zipper 2.0 to view the advanced "details" of your apps.
To get the names to disable the same apps I did, change 7zipper's app list to system mode.
Info for people who really hate resource hogs:KFTV Launcher is currently using 80.59MB according to memory booster!
It probably has something to do with each menu selection loading dozens of images and information and sub-apps that seem to have no individual apps for selecting to disable.
So rbox,when you feel the Home Menu MOD is stable enough,please let me know when you release it for xposed.

retroben said:
After I used terminal emulator with the pm disable function to disable both Gamecircle apps,Amazon Video,Photos (screensaver usage),and the Amazon AppStore,and resetting with ctrl+alt+del,I found a nice little surprise in the apps tab on the Home screen.
When I went to the Apps section,the list of all my installed apps appeared on the right!
When selecting them,they open immediately,but I can't long press to view the details of an app.
However,since they are still in the settings menu as well,I can still view the details from there.
The only issue with it is that it is a little buggy with scrolling through apps.
You can figure out the com-names using 7zipper 2.0 to view the advanced "details" of your apps.
To get the names to disable the same apps I did, change 7zipper's app list to system mode.
Info for people who really hate resource hogs:KFTV Launcher is currently using 80.59MB according to memory booster!
It probably has something to do with each menu selection loading dozens of images and information and sub-apps that seem to have no individual apps for selecting to disable.
So rbox,when you feel the Home Menu MOD is stable enough,please let me know when you release it for xposed.
Click to expand...
Click to collapse
This has been known for some time. I think you found the secret that I hadn't been able to figure out; I bet it was disabling the Amazon Appstore. From what I remember, the initial reports were that sideloading the Appstore from Android caused this to happen. The code I haven't been able to find yet, must check for the Appstore and it's not there or the wrong one, it falls back to this grid view. At one point I was working on a mod that exposed (get it... cuz I use Xposed... haha) a similar, but less buggy grid. I may go back to working on that.
As for the menu mod, I just got the UI done for selecting which items should be visible, and I'm just working on the saving/loading of the preferences and getting the menu to reload after it's been changed.

What all did you disable and do you have the disable code you ran?

cybertlc said:
What all did you disable and do you have the disable code you ran?
Click to expand...
Click to collapse
pm disable "com.amazon.venezia"
Note this breaks Netflix completely.

Does disabling Photos and Gamecircle break Netflix as well? What are the package names for those 2?

Download and install "Package Name Viewer" : https://play.google.com/store/apps/details?id=com.gijoon.pkgnameviewer&hl=en

Or if you already have 7Zipper 2.0,you can view the names in the applications section in the details option via longpressing an app.
7Zipper 2.0 is the only well-known app that can extract 7z files on Android.

That's time consuming to do it for every app...Package Viewer does only what it says, shows you the com.xxxx.xxx name for installed packages.

I get a "Failed to connect to dumb state service killed" error when using the pm disable command
Any ideas

Stevie G said:
I get a "Failed to connect to dumb state service killed" error when using the pm disable command
Any ideas
Click to expand...
Click to collapse
How did you get to that point? The easiest is to run 'adb shell', then 'su' and verify you have the # prompt and it should work.

rbox said:
How did you get to that point? The easiest is to run 'adb shell', then 'su' and verify you have the # prompt and it should work.
Click to expand...
Click to collapse
We'll I did not type that.what is the correct way of typing it out adb shell su com.amazon.avod

Stevie G said:
We'll I did not type that.what is the correct way of typing it out adb shell su com.amazon.avod
Click to expand...
Click to collapse
1. adb shell
2. su
3. pm disable com.amazon.avod

lightning413 said:
1. adb shell
2. su
3. pm disable com.amazon.avod
Click to expand...
Click to collapse
Thanks bud

Press enter after every part.
1a. adb shell
1b. Press Enter
2a. su
2b. Press Enter
3a. pm disable name.of.app (some begin with org instead of com)
3b. Obviously press Enter,unless you changed your mind.

Does anyone have a list of what can safely be disabled without interfering with other features/apps/functions? I want to keep my Netflix/Pandora fully functional (but could care less about games).

cybertlc said:
Does anyone have a list of what can safely be disabled without interfering with other features/apps/functions? I want to keep my Netflix/Pandora fully functional (but could care less about games).
Click to expand...
Click to collapse
Why do you feel like you have to disable anything?

rbox said:
Why do you feel like you have to disable anything?
Click to expand...
Click to collapse
I'm assuming there are things that can be disabled to use less resources.

cybertlc said:
I'm assuming there are things that can be disabled to use less resources.
Click to expand...
Click to collapse
Not really. If you run ps from adb shell, there really isn't that much running that you'd be able to disable without completely break everything.

I find that Fire TV is actually not that bad about bloating apps when compared to the GS7 that got replaced by it.
The Sony NSZ-GS7 has some bloat apps like the TTS and most of the other ones I can't remember because none of them are on Fire TV.
Kernel Tuner:
I found out that the best performance governor for CPU is the Interactive governor.
And for I/O Schedular,the deadline mode is the fastest one.

This failed the wife acceptance test as it also causes issues with (but does not totally break) Pandora.

NO ROOT REQUIRED: Completely disable and enable your lock screen

Many of us don't have root and many of us also uninstalled may system apps, including Fire Launcher. That left us with some annoyances. One major annoyance was being kicked to the lock screen whenever we swiped away apps from the recent apps menu. Some people saw annoying flashes. Well this isn't quite a fix, but it pretty much takes care of the problem. You can now remove your lock screen completely and replace it at will and you do NOT need root access.
***WARNING: Touching any other settings on your tablet during this guide can cause a brick!!!***
1. Download and install Settings Database Editor.
2. Plug your tablet into your PC and open an ADB window. Enter the following:
Code:
adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
Step number 2 MUST be done in order for this to work.
3. Open Settings Database Editor and tap on the 'secure' tab at the top.
4. These settings are in alphabetical order. Scroll until you see:
Code:
"lockscreen_disabled" "0"
5. Change the 0 to a 1. DO NOT CHANGE ANYTHING ELSE
6. Close Settings Database Editor
Now turn off your screen. Now turn it back on. You are welcome! I have a few more tricks coming. Watch for some later!
IF THE ABOVE DOESN'T WORK, TO DISABLE LOCK SCREEN:
Code:
adb shell settings put secure lockscreen_disabled 1
ENABLE LOCK SCREEN:
Code:
adb shell settings put secure lockscreen_disabled 0

Both methods don´t work on my Fire HD10 2017.

tommes-d said:
Both methods don´t work on my Fire HD10 2017.
Click to expand...
Click to collapse
It worked almost instantly for me. Maybe wait a bit? Did you reboot? It won't work on every device. Doesn't work on my Galaxy S7.

Not working for me too (Fire HD 8 2016). Also, you've made a mistake: original setting name is "lockscreen.disabled" (dot, not an underscore).

sensboston said:
Not working for me too (Fire HD 8 2016). Also, you've made a mistake: original setting name is "lockscreen.disabled" (dot, not an underscore).
Click to expand...
Click to collapse
Disappointing. Today I got a good one though. I can't wait to get home and post a thread.

I know this isn't the correct forum for this but I tried this on a Fire 7 (2017) and it also does not seem to work.

is there an updated way to do this?
is there an updated way to do this?
edit: kindle fire 8 7th gen, confirmed not working.

Doesn't work on my Fire HD8. But while browsing through Settings Database Editor I have found something useful.
In the "Global Table" tab there's a setting called LOCKSCREEN_AD_ENABLED. Change the value from 1 to 0, save. Turn off screen, turn it on again --> ads are gone!
At least for a while...

Seems to be working on KFAUWI (Fire 7 7th Gen) on 5.4.0.0.
EDIT: Maybe it doesn't work with 5.4.0.1 and later?
It would be useful for those reporting success/failure to include not just device model, but fw version as well.
EDIT1: After some time playing around the system I have found out that by default it actually does not work, but if Global Table->"device_provisioned" = 0 then lock screen gets disabled, but serial number gets greyed out and developer options get disabled, while adb remains functional.
On 5.6.0.0 even change to "device_provisioned" did not disable the lock screen.

gabosius said:
Seems to be working on KFAUWI (Fire 7 7th Gen) on 5.4.0.0.
EDIT: Maybe it doesn't work with 5.4.0.1 and later?
It would be useful for those reporting success/failure to include not just device model, but fw version as well.
Click to expand...
Click to collapse
There are settings in the "private" class that override some of these lower ones, usually in favor their using their own software. I think most device stock settings are hidden for the purpose of favoring their own software. Though with Amazon, I scratch my head. Why spend the large amount of money, to install a high tech, customizable GPS system on devices, only to spend more money carelessly blocking your Access?
Sent from my Samsung Galaxy S4 using XDA Labs

DragonFire1024 said:
There are settings in the "private" class that override some of these lower ones, usually in favor their using their own software. I think most device stock settings are hidden for the purpose of favoring their own software. Though with Amazon, I scratch my head. Why spend the large amount of money, to install a high tech, customizable GPS system on devices, only to spend more money carelessly blocking your Access?
Sent from my Samsung Galaxy S4 using XDA Labs
Click to expand...
Click to collapse
That's fairly simple, the same goes for one of the iPhones (don't recall which gen exactly) which had two different models of radio chips, one of which did support LTE, but Apple decided to disable LTE support for that gen of the phone altogether.
Now more on the topic, checked the specs of all 7th gen tablets, indeed none of them seem to support GPS officially (for some reason I thought that HD8/HD10 might have it), but if they have the hw, it could be for testing purposes to test proprietary GPS related sw on development devices before introducing it in the next gen? Or simply they decided to drop it somewhere along the way but left the hardware (as we still have Serial/UART on some production devices nowadays, which are used only for debugging in the development stage).
On the other hand, where did you get the info that it actually has GPS related hardware? Because while exploring my device settings I only found a hint on A-GPS support (which is not proven).

gabosius said:
That's fairly simple, the same goes for one of the iPhones (don't recall which gen exactly) which had two different models of radio chips, one of which did support LTE, but Apple decided to disable LTE support for that gen of the phone altogether.
Now more on the topic, checked the specs of all 7th gen tablets, indeed none of them seem to support GPS officially (for some reason I thought that HD8/HD10 might have it), but if they have the hw, it could be for testing purposes to test proprietary GPS related sw on development devices before introducing it in the next gen? Or simply they decided to drop it somewhere along the way but left the hardware (as we still have Serial/UART on some production devices nowadays, which are used only for debugging in the development stage).
On the other hand, where did you get the info that it actually has GPS related hardware? Because while exploring my device settings I only found a hint on A-GPS support (which is not proven).
Click to expand...
Click to collapse
Add a few .xml configuration files to start and there is configuration settings in the framework. Look for an app on the tablet with HERE in all caps in the title. That's the APK module making it possible. And yes I figured out a way to modify framework settings

DragonFire1024 said:
Add a few .xml configuration files to start and there is configuration settings in the framework. Look for an app on the tablet with HERE in all caps in the title. That's the APK module making it possible. And yes I figured out a way to modify framework settings
Click to expand...
Click to collapse
I see, just checked MT8127 specs, and indeed there seems to be integrated support for GPS with GLONASS, that may be something interesting to play with.
EDIT: HD8/HD10 even have broader support of GPS related technologies according to their SoC specs.
Yeah, I was following root progress thread, even tried Blueborne exploit (the one published by Armis labs on github) on KFAUWI without much success as there is no access to /proc/<pid>/maps. And framework-res.apk mod looks promising only for devices having root, as getting required permissions outside /system is rather problematic.
Yet I was surprised that WRITE_SECURE_SETTINGS can be assigned outside /system. As I was poking around com.amazon.dcp.permission.DISPLAY_DEBUG_UI for quite some time.

gabosius said:
Yet I was surprised that WRITE_SECURE_SETTINGS can be assigned outside /system. As I was poking around com.amazon.dcp.permission.DISPLAY_DEBUG_UI for quite some time.
Click to expand...
Click to collapse
Do you have any idea if you can grant something like Activity Launcher the DISPLAY_DEBUG_UI permission? Some of the activities gave me errors when I tried to open them, saying they require com.amazon.dcp.permission.DISPLAY_DEBUG_UI.
The thing is, this appears to be a custom permission added by Amazon, not available in the official Android documentation.
Would Activity Launcher even be capable of launching certain "hidden" activities with this permission granted? Presumably you would grant permission over ADB the same way as WRITE_SECURE_SETTINGS?
Any ideas would be great.

lakitu47 said:
Do you have any idea if you can grant something like Activity Launcher the DISPLAY_DEBUG_UI permission? Some of the activities gave me errors when I tried to open them, saying they require com.amazon.dcp.permission.DISPLAY_DEBUG_UI.
The thing is, this appears to be a custom permission added by Amazon, not available in the official Android documentation.
Would Activity Launcher even be capable of launching certain "hidden" activities with this permission granted? Presumably you would grant permission over ADB the same way as WRITE_SECURE_SETTINGS?
Any ideas would be great.
Click to expand...
Click to collapse
Tried granting it to other apps and it resulted in "com.amazon.dcp.permission.DISPLAY_DEBUG_UI is not a changeable type" the command I used was pm grant com.amazon.dcp com.amazon.dcp.permission.DISPLAY_DEBUG_UI so yes, the syntax is the same with custom amazon permissions. Also execution of dumpsys package com.amazon.dcp shows that app already has DISPLAY_DEBUG_UI permission.
My guess is that it requires root, as even when I am launching activity from adb shell (not in context of activity manager) I get the same error that it requires the permission, and the same goes for some other hidden amazon applications.
EDIT: you can get list of device permissions by executing "pm list permissions" without quotes from adb shell, there are at least a few interesting ones.

lakitu47 said:
Do you have any idea if you can grant something like Activity Launcher the DISPLAY_DEBUG_UI permission? Some of the activities gave me errors when I tried to open them, saying they require com.amazon.dcp.permission.DISPLAY_DEBUG_UI.
The thing is, this appears to be a custom permission added by Amazon, not available in the official Android documentation.
Would Activity Launcher even be capable of launching certain "hidden" activities with this permission granted? Presumably you would grant permission over ADB the same way as WRITE_SECURE_SETTINGS?
Any ideas would be great.
Click to expand...
Click to collapse
That's a great question and one that hasn't been asked before. I can tell you I've been able to, in some apps, modify the manifest permissions. For example, I can use an app to edit the manifest of Jack Pals terminal emulator to add the secure settings permission and have it successfully install etc. I never thought of doing the same with activity launcher and if successful, seeing what happens. This could be very interesting. If you give me a few copies of some of the manifests permissions, I can see if a recompile and install will hold.

DragonFire1024 said:
That's a great question and one that hasn't been asked before. I can tell you I've been able to, in some apps, modify the manifest permissions. For example, I can use an app to edit the manifest of Jack Pals terminal emulator to add the secure settings permission and have it successfully install etc. I never thought of doing the same with activity launcher and if successful, seeing what happens. This could be very interesting. If you give me a few copies of some of the manifests permissions, I can see if a recompile and install will hold.
Click to expand...
Click to collapse
I attached a text document with ALL of the permissions listed by "pm list permissions" since it was too long to put here.

lakitu47 said:
I attached a text document with ALL of the permissions listed by "pm list permissions" since it was too long to put here.
Click to expand...
Click to collapse
Give me a few hours to see if I can modify the app. If I can, I'll upload a. APK
Sent from my Samsung Galaxy S4 using XDA Labs

DragonFire1024 said:
Give me a few hours to see if I can modify the app. If I can, I'll upload a. APK
Sent from my Samsung Galaxy S4 using XDA Labs
Click to expand...
Click to collapse
Questionable whether anything would change, as I don't see where activity launcher would need write secure settings permission.
On the other hand I did some digging on the "not a changeable permission type" message, and this provides some answer on what it might be expecting in order to activate?/assign the permission.

gabosius said:
Questionable whether anything would change, as I don't see where activity launcher would need write secure settings permission.
On the other hand I did some digging on the "not a changeable permission type" message, and this provides some answer on what it might be expecting in order to activate?/assign the permission.
Click to expand...
Click to collapse
Interesting. So each permission has a certain "protection" level?

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.