Related
I saw that ADW 1,01 is out and i want it...
So how do i instal/update it to v1.01? [and will all my preferences and settings,apps,etc be usable once i put on the 1.01?]
and plz be datailed about it,since ima noob with the android.ty
aca85 said:
I saw that ADW 1,01 is out and i want it...
So how do i instal/update it to v1.01? [and will all my preferences and settings,apps,etc be usable once i put on the 1.01?]
and plz be datailed about it,since ima noob with the android.ty
Click to expand...
Click to collapse
What version do you currently have?
Did it come with your rom or did you download it?
You can backup your settings (export) to your sdcard and restore (import) with the new version if by chance your settings are not preserved.
Im using CM 5.0.8 ,and it came with 0.8.9.
And how do i go about doing that export/import?
Either download link from your phone and install or download on PC put on SD card open file manager and install are easiest. Put it on a friends phone. Looks good. Backup and restore are in settings adw.
Sent from my HTC Magic using XDA App
Do a search for ADW.Launcher in the Market, it's there. Just make sure you have a period in between "ADW" and "Launcher."
Hey,
I'm interested in updating the ADW.Launcher version that came with my CM5.0.8 rom, but I don't know if it's OK to update through market or get the apk file and use "adb install" or find a zip file to flash...
Could anyone make some light in here pls?
Thanks!
I have tried downloading the apk file for my CM5x and MDPI device from Anderweb's page but when I tried to "adb install" I get...
INSTALL_FAILED_ALREADY_EXISTS
Can someone shed some light? Is there a way to update the ADW.Launcher that comes with a specific ROM version?
Tried using android commander?
Sent from my Chromatic Magic using XDA App
Since I'm new to this scene, what is the difference between the "adb install" method and using the Android Commander (which I need install)?
Would Astro help in this case, because I remember reading that has support for installing apk files?
I'd like to do this update as clean as possible.
Thank you for the reply!
PS: I have actually installed Android Commander and installed the ADW.Launcher apk for CM5x MDPI as an Update (wasn't sure what to chose between Private, Application or Update) and the installer said it was successful but after reboot I still have the old version 0.8.6
Any ideas?
U can download it put it on your sdcard and install with a file manager. Doesn't matter which way u go. Should work. Done it both ways
Sent from my Chromatic Magic using XDA App
I did it somewhat the way you said and installed it with Android Explorer as an update because the regular installation would fail with the error that the application already exists.
The problem is that the new version gets copied into /data/apps/ and I can start using it but after the first reboot it's not there anymore and I get back to the one that came with my CM5.0.8 rom which is in /system/apps/
I would really like to get a solution that would update the one in /system/apps/ which might be harder because it's a memory mapped version of the ROM and changes get lost after reboot.
Please correct me where I am wrong...
Have u tried goin to the market and installing it from there? It's like version 1.4.1 or something now
Sent from my Chromatic Magic using XDA App
place the file on your /sd.
adb push /sdcard/filename.apk /system/app
restart home or reboot phone.
I ended up installing the one from Market and making that the default launcher, but I would really like to just replace the one in the system folder - no need to keep 2 versions of the same app
I'll try the method NetrixTardis was suggesting.
U can do it through the terminal as well. Maybe removing the old one will solve it. Use the rm command in the terminal and see if u can do it that way. Ex.
$su (enter after each line)
#rm /system/app/(name of app.apk)
Then u can use cp command to copy the one from your sdcard.
Cp /sdcard/(app.apk) /system/app/
Someone correct me if I'm wrong in the lines
Sent from my Chromatic Magic using XDA App
hey johnson8cyl
I'll try that and let you know if it worked, should I copy it to the same name?
like /system/app/adwlauncher.apk is the name for the system app, while the Market installed one is org.adwlauncher....apk
do you guys know a good keyboard replacement and a way to configure the vibration alarm on my CM5.0.8? these are mostly the things I miss from my stock ROM
oh...forgot to mention the CM5.0.8 default camera does not have all the setting (like I can't set the ISO), is there one that does that trick?
thanks!
I'll answer the keyboard part. I've got Smart Keyboard installed and its a lot better than the stock Android one.
Sent from my HTC Magic using XDA App
U have to use the names exactly the one your removing and one your copying. Names have to be what u want to remove or copy. That make sense?
Sent from my Chromatic Magic using XDA App
Makes total sense to keep the same names only that I have this problem...
any ideas? kinda makes sense because that comes from the ROM and is mounted as read-only
# su
su
# pwd
pwd
/system/app
# rm -f ADWLauncher.apk
rm -f ADWLauncher.apk
rm: can't remove 'ADWLauncher.apk': Read-only file system
ps: I actually managed to fix this what was missing is "adb remount" to mount system partition read-write
So you figured it out? Were you able to get it removed and replaced?
Sent from my Chromatic Magic using XDA App
Right, I applied this mod and didn't install another launcher as a backup before hand, now all I get is a black screen wit the top bar when I boot up the phone. (it boots fine, just there's no launcher)
Is there anyone out there that can provide me with an update.zip with the original touchwiz.apk for JM1? If there is anyone that can do this it would be greatly appreciated.
Thanks,
Luke.
EDIT: What I did was found a way of getting to the market (via a link in a text message that was sent to me and accessible via the notifications bar) and hence could access all my apps. I then downloaded another twlauncher.apk (it was jm8 but works fine on jm1, I'll post it here) and followed the instructions in the mod thread to put the modded launcher on the phone, but instead of pushing the modded one to the system/app folder it pushed the non-modded one, thus fixing the phone.
The link sent in the text was "http://cyrket.com/qr/15550" it searches for a tower defence game but you can then use the search to get to "Terminal Emulator" which is the app used to move the .apk in the first place.
Steps to fixing the launcher:
1)Get a TouchWiz30Launcher.apk (different firmware versions need different ones?),
2)Put the launcher.apk onto the internal SDcard (/sdcard/) I did this via USB mass storage, if you have Kies as default for USB or something other than mass storage then follow the next step but find "launcher pro" instead to get into the phone settings list to change USB settings.
3)Send a text to your phone with "http://cyrket.com/qr/15550" or another link to open the Android Market,
4)Search for "Terminal Emulator" to open the app,
5)Follow these steps (found in the mod thread):
chickie.tobias said:
3. type su then hit enter
4. type mount -o remount,rw / system then hit enter.
5. type cp -f sdcard/TouchWiz30Launcher.apk system/app then hit enter
6. type sync then hit enter
7. type reboot then hit enter
Click to expand...
Click to collapse
That's it, this is how I fixed my TouchWiz
Right I've managed to installed LauncherPro but I'd really like to be able to get TW back, can someone please help?
Also I keep getting force closes saying android.process.acore has stopped working... No idea what that is either...
Hi. I had the exact same problem. Only solution for me was a re-flash using Odin. But at least I now have Froyo.
Sent from my GT-I9000 using XDA App
One more thing. Don't try a system wipe, it will make things worse.
Sent from my GT-I9000 using XDA App
Hey there, I was thinking of doing that but I found a (crude) way of sorting it. It's now fixed with a new twlauncher I'll post a tutorial once I'm home on how I did it to see if it can help anyone. =)
Sent from my GT-I9000 using XDA App
How can I activate God Mode on a rooted XOOM? I want to nullify some stock apps, but Root Explorer is saying they are read only.
Thanks.
[edit] Changed the thread question.
LOL. I didn't know we were playing Quake.
What do you mean by god mode. You already have root. That's all you should need.
Sent from my Nexus One using XDA App
lol.
That might not be the correct term, and it may require a custom rom. Not sure, but on Project Elite for the OG Droid, there's an option under General>System called God Mode that gives you full access to files on the system. That may just be what Actngrezy calls it in PE.
I just want to rename some of the apps that were included on the XOOM. Specifically, I want to nullify the Quick Office apk so I can install the NI Adam version. When I navigate to the apk in Root Explorer, I get an error telling me it's a read only file. I never got that error with the Droid. I can change whatever I want to on that device.
Did you click on mount r/w in root explorer
arrtoodeetoo said:
How can I activate God Mode on a rooted XOOM? I want to nullify some stock apps, but Root Explorer is saying they are read only.
Thanks.
Click to expand...
Click to collapse
Did you install superuser? if so make sure you have allowed root explorer in it. Then on the top left hand side in root explorer hit mount r/w
arrtoodeetoo said:
lol.
That might not be the correct term, and it may require a custom rom. Not sure, but on Project Elite for the OG Droid, there's an option under General>System called God Mode that gives you full access to files on the system. That may just be what Actngrezy calls it in PE.
I just want to rename some of the apps that were included on the XOOM. Specifically, I want to nullify the Quick Office apk so I can install the NI Adam version. When I navigate to the apk in Root Explorer, I get an error telling me it's a read only file. I never got that error with the Droid. I can change whatever I want to on that device.
Click to expand...
Click to collapse
Im just visiting the forum to steal a few files to compare with atrix , how ever if i read your cleverly phrased question correctly and you are trying to remove/freeze some apps that came on the Xoom and you are getting read only error its because to modify anything in the /system dir you need to
1. back up anything you might remove via adb pull or via adb shell cp
2. adb shell
3.su
4. mount -o rw,remount (what ever the path to zoom block is i dont know cause i dont have one ) exp /dev/block/mmcblk0p12 /system
from there you can remove what ever you want out of system dir
5. exp. rm /system/app/quickoffice.apk
Thanks! I never noticed that button before. lol.
you can also get a system uninstaller in the market that will do it for you just the same, I usually use that in case there is more included than just the apk file
PaulG1488 said:
Did you click on mount r/w in root explorer
Click to expand...
Click to collapse
x 2
Sent from my Xoom using XDA Premium App
I thought about the uninstaller thing, but I'd rather not uninstall anything that came on the XOOM just in case. I just add an extra .null at the end of the apk (and associated files, which are easy to find) in case I need to restore them.
For instance, the NI Quick Office app force closes when you just breathe on the freaking tablet, so I had to restore the default one.
Using a soft keyboard different than the Asus one, when the dock is connected an annoying message pop up telling us that if we don't change the soft keyboard to the asus one, the dock keyboard could not function well.
This is mostly important for non US users, as when the soft keyboard isn't the Asus one, the layout used for the dock is the standard US one.
Root needed
Using Autostarts we can disable the popup when the dock is connected:
Download autostarts from the market, open the app, let it load all the the way, then click on Asus Keyboard under "Docking changed" and disable it
or in terminal
adb shell
su
pm disable com.nuance.xt9.input/.DockEventReceiver
For permanently change the standard layout of the dock keyboard:
Locate your national keychars in /system/usr/xt9/keychars
mine is qwerty-it_IT.kcm
The first 2 character after the - is the language of the keyboard, in my case Italian, the 2 characher after the _ is the country of the keyboard, Italy in my case.
copy this file in /system/usr/keychars
rename the standard one asusec.kcm in asusec.kcm.old for backup purpose.
then rename the one you copied in asusec.kcm
Locate your national layout in /system/usr/xt9/keylayout
mine is qwerty-it_IT.kl
copy this file in /system/usr/keylayout
rename the standard one asusec.kl in asusec.kl.old for backup purpose.
then rename the one you copied in asusec.kl
reboot and you are all done
P.S.
you can use root explorer to copy and rename those files, or you can do it with adb.
If you don't know how to use those, maybe is better to learn before messing around in the system files.
P.P.S.
If anyone know a free app that can replace autostarts, let me know so I can update the guide.
Great guide, thx a lot! If we mess with keychars and keylayout, we could also remap specific keys, right?
For example, I don't really need the three brightness buttons on the dock, i barely change brightness, and if i have to sometimes, i don't mind browsing to settings-->display.
Can we remap these to different keys OR specific apps, OR even better: to key combinations? Would be cool to have cut, copy and paste on the brightness buttons. What do you think?
Plus, one more off topic thing, I think you could know: Is there a file which could change mouse button mapping and perhaps enable additional mouse buttons (thumb mouse buttons for example)? I though of setting the "menu" key to the right mouse button instead of "back" for example.
Regards
qwer23
qwer23 said:
Great guide, thx a lot! If we mess with keychars and keylayout, we could also remap specific keys, right?
For example, I don't really need the three brightness buttons on the dock, i barely change brightness, and if i have to sometimes, i don't mind browsing to settings-->display.
Can we remap these to different keys OR specific apps, OR even better: to key combinations? Would be cool to have cut, copy and paste on the brightness buttons. What do you think?
Plus, one more off topic thing, I think you could know: Is there a file which could change mouse button mapping and perhaps enable additional mouse buttons (thumb mouse buttons for example)? I though of setting the "menu" key to the right mouse button instead of "back" for example.
Regards
qwer23
Click to expand...
Click to collapse
You can remap any key you want, I've seen a guide somewhere in the forums.
For the mouse I don't think you can do anything without some serious hacking, the dock trackpad follow the standard rules for mouses in android: left click = click, right click = back, whell button click = menu.
I also hate how they have implemented the 2 finger scrolling, when you scroll actually the trackpad long click where the cursor is, and invert the axis of the trackpad, so when you scroll down you are in fact long pressing and scrolling the cursor up, and so on.
It messes so many apps, as this simulated long click can be registered by the app
Updated on the first post how to disable permanently the asus keyboad popup when docking
qwer23 said:
Would be cool to have cut, copy and paste on the brightness buttons. What do you think?
Click to expand...
Click to collapse
You can do it with ctrl+x ctrl+c and ctrl+v
I can't see the Thank You button, but I thought I'd just say thanks!
This is an excellent guide and worked perfectly for my UK keyboard!
Much appreciated
I found an alternative to Autostarts, fire this commands in a terminal:
Code:
adb shell
su
pm disable com.nuance.xt9.input/.DockEventReceiver
These are the "cut&paste" commands for changing the layout:
Code:
adb remount
adb shell
mv /system/usr/keychars/asusec.kcm /system/usr/keychars/asusec.kcm.old
mv /system/usr/keylayout/asusec.kl /system/usr/keylayout/asusec.kl.old
cp /system/usr/xt9/keychars/qwerty-it_IT.kcm /system/usr/keychars/asusec.kcm
cp /system/usr/xt9/keylayout/qwerty-it_IT.kl /system/usr/keylayout/asusec.kl
I found my own solution for disabling the dock connected popup.
I modified the XT9IME.apk so that the popup is not displayed and posted it here before stumbling upon this thread.
Would it be possible to make a update zip, to do this in clockwork, ive just insalled a new rom, now i need to redo the fix.
jambo89liam said:
Would it be possible to make a update zip, to do this in clockwork, ive just insalled a new rom, now i need to redo the fix.
Click to expand...
Click to collapse
I could script this and have update.zips for it.
Perhaps someone else could create an app that does it via a menu system to select your country.
Fixed?
Over on http://forum.xda-developers.com/archive/index.php/t-1152317.html the last post says:
"The warning message has now been fixed, after the latest update 8.4.11. It now gives you the option of 'Do not show this again."
So maybe it's now fixed? (Don't have my Transformer at work to check for myself.)
You can use this as an executable (755) script file if you want to use another keyboard with another language
Code:
#!/system/bin/bash
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mv /system/usr/keychars/asusec.kcm /system/usr/keychars/asusec.kcm.orig
cp /system/usr/xt9/keychars/qwerty-de_DE.kcm /system/usr/keychars/asusec.kcm
mv /system/usr/keylayout/asusec.kl /system/usr/keylayout/asusec.kl.orig
cp /system/usr/xt9/keylayout/qwerty-de_DE.kl /system/usr/keylayout/asusec.kl
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
Just replace the "de_DE" parts with your language code.
Just wanted to bump this b/c of the ICS release.
While those ADB commands give me a "segmentation fault"...
Azhad said:
adb shell
su
pm disable com.nuance.xt9.input/.DockEventReceiver
Click to expand...
Click to collapse
the following procedure still works like a charm on ICS!
Azhad said:
Locate your national keychars in /system/usr/xt9/keychars
mine is qwerty-it_IT.kcm
The first 2 character after the - is the language of the keyboard, in my case Italian, the 2 characher after the _ is the country of the keyboard, Italy in my case.
copy this file in /system/usr/keychars
rename the standard one asusec.kcm in asusec.kcm.old for backup purpose.
then rename the one you copied in asusec.kcm
Locate your national layout in /system/usr/xt9/keylayout
mine is qwerty-it_IT.kl
copy this file in /system/usr/keylayout
rename the standard one asusec.kl in asusec.kl.old for backup purpose.
then rename the one you copied in asusec.kl
reboot and you are all done
Click to expand...
Click to collapse
Thanks again for working this out!
can anyone please make the dock keyboard work with latvian? i hate anysoftkeyboard, it stops working and its craching all the time.
i want to use dock like on a normal computer.
Does latvia have its own keyboard layout or do you use one that another country uses as well? Which county abbreviation would it be (like en for English and de for German)?
Doesn't work ?!
modmatt said:
the following procedure still works like a charm on ICS!
Click to expand...
Click to collapse
Doens' work for me, in fact, if I'm copying the de_DE files from Revolver 4 over to my EOS AOSP rom build and put the keychars (asusec.kcm) and the keylayout (asusec.kl) in their respective folders and reboot afterwards, nothing happens to the dock input. Still stays the same old QWERTY like before.
But I can see in file manager that the copying was successfull. New asusec.kl and asusec.kcm are there.
Someone help me ?
You already mentioned the reason yourself, I think. As you are using an AOSP ROM it means that you're using a plain vanilla android basis, which - correct me if I'm wrong - obviously doesn't know anything about asus*.* keyboard files. Just copying some files somewhere is not enough to let the system know what to do with it.
You probably have to deal with some scripts, that are run at every start up, that give proper instructions for the operating system. Unfortunately this is way beyond my knowledge.
modmatt said:
You already mentioned the reason yourself, I think. As you are using an AOSP ROM it means that you're using a plain vanilla android basis, which - correct me if I'm wrong - obviously doesn't know anything about asus*.* keyboard files. Just copying some files somewhere is not enough to let the system know what to do with it.
You probably have to deal with some scripts, that are run at every start up, that give proper instructions for the operating system. Unfortunately this is way beyond my knowledge.
Click to expand...
Click to collapse
What are you going on about? This works just fine on ICS with Revolver, just changed my dock back to azerty. rayman33 just did something wrong.
Please read that rayman33 uses an AOSP ROM that has nothin to do with Asus. You are using Revolver, which is bases on Asus' original ROM - that is why it works for you but not for him.
i just found this post as i'm having the very same issues using my transformer tf300 - currently running official stable CM10
the bad thing about it is only, in my CM10 i don't even have a /system/usr/xt9/ directory and when looking into the backup of my stock ASUS rom, I do have /system/usr/xt9/ and even subdirs keychars and keylayout, but without any content.
it would be lovely if someone would be so kind to suck out the de_CH files for me and could post them here!
UPDATE: updated instructions for Swiftkey X version 2.2.0.35 (released 11/18/2011) and later.
UPDATE 2: added known values for some other keyboard apps.
UPDATE 3: added warning, split the copying and chown/chmod step into two separate steps.
These instructions assume:
You've already rooted your KF and have ADB access.
You have the adb.exe debug shell installed. This is included with some rooting kits, or you can install the Android SDK (software development kit) from Google and get ADB straight from the source. The examples assume you have a directory called "C:\Android" where adb.exe is installed but yours may be installed elsewhere.
You've got some way of installing the Swiftkey X app, either by installing Android Market or by sideloading the apk.
You're using the purchased version of Swiftkey X (not the tablet version, not any beta or free version that might be out there).
You've got a SQLite editing software (or can use "sqlite3" itself); the instructions below use the free SQLite Database Browser 2.0 which can be downloaded from Sourceforge; just Google for "sqlite browser" (sorry as a n00b I can't post links).
WARNING: use these instructions at your own risk! Modifying, removing or incorrectly setting the permissions on the settings database can result in a non-booting device!
ALTERNATIVELY, you can use various Android apps to edit the database on the device without using ADB, and skip many of the steps below. Posts further down this thread has some recommendations for such apps. Two caveats if using such an app: make sure it doesn't alter the settings.db file ownership or permissions, and be very cateful when modifying the database entry, as there is a tendency for the keyboard or cut-and-paste to "helpfully" insert spaces or change capitalization.
If you try and install Swiftkey as you normally would, you'll get stuck at installation's step 2, which requires you to enable Swiftkey as an input method by redirecting you to the device's input method settings window; in the case of the KF, the option to enable alternate keyboard has been omitted, but as others (thanks PSXtreme and mfisch) have found it's possible to get around this problem and successfully install an alternate keyboard.
Connect the KF to your computer via USB.
When the Kindle tells you that USB storage is enabled, press the "Disconnect" button to disable it (having the USB storage mounted will prevent us from using ADB to copy to the sdcard directory).
Open an ADB shell and use it to make a backup copy of the settings database file (settings.db), and then to a directory where you can edit it (we'll use /mnt/sdcard/Download here) (stuff you need to enter below is in boldface):
C:\android>adb shell
$ su
# cd /data/data/com.android.providers.settings/databases
# cp settings.db settings.db.bak
# cp settings.db /mnt/sdcard/Download
Now enable USB storage by tapping on the KF's top notification bar and then on "USB is Connected / Select to copy files..."
Open the SQLite Browser, and then open the settings.db file you copied by navigating to the mounted USB drive (e.g. D:\Download\settings.db).
Click on SQLite Browser's "Browse Data" tab, and then "secure" from the droplist of tables. Find the row with the entry named "enabled_input_methods" (it's number 19, ID 21 in my file); you may need to widen the columns to see the full name.
Double-click on the entry's "value"; this will open an "Edit database cell" dialog.
The default value of the entry should be "com.android.inputmethod.latin/.LatinIME"; regardless, you want to add ":com.touchtype.swiftkey/.KeyboardService" to it (the ":" is a separator), e.g. changing the value to "com.android.inputmethod.latin/.LatinIME:com.touchtype.swiftkey/.KeyboardService". (Note: if you're installing a different keyboard program, you'll substitute a different value; I found the correct value for mine by downloading the settings.db file from another Android device with Swiftkey already installed.)
UPDATE: for Swiftkey X versions 2.2.0.35 (released 11/18/2011) and later, the value to be added is ":com.touchtype.swiftkey/com.touchtype.KeyboardService", so the resulting enabled_input_methods value is: "com.android.inputmethod.latin/.LatinIME:com.touchtype.swiftkey/com.touchtype.KeyboardService"
UPDATE 2: here's a list of known values for various keyboard apps:
Swiftkey (paid version): com.touchtype.swiftkey/com.touchtype.KeyboardService
Swiftkey Tablet (paid version): com.touchtype.swiftkey.tablet.full/com.touchtype.KeyboardService
Swype: com.swype.android.inputmethod/.SwypeInputMethod
SymbolsKeyboard & TextArt Pro: com.mobisters.textart.pro/.AsciiTextArtKeyboardPro
SlideIT: com.dasur.slideit/.SlideITIME
Graffiti Pro: com.access_company.graffiti_pro/.Graffiti
FlexT9: com.nuance.flext9.input/.IME
Beansoft Thumb Keyboard: com.beansoft.keyboardplus/.LatinIME
Hacker's Keyboard: org.pocketworkstation.pckeyboard/.LatinIME
Simeji: com.adamrocker.android.input.simeji/.OpenWnnSimeji
After you've changed the entry and double-checked you got it right, hit the "Apply Changes" button, close the dialog, and save your changes to the settings.db file. You can now close the SQLite Browser.
Disable USB storage again by hitting the "Disconnect" button on the KF.
Back in the ADB shell, copy the modified settings.db file back to its original location:
# cp /mnt/sdcard/Download/settings.db .
Still in the ADB shell, fix the file owner and permissions (IMPORTANT! skipping this step can prevent your KF from booting properly!):
# chown system.system settings.*
# chmod 660 settings.*
# ls -l
-rw-rw---- system system 22528 2011-11-17 21:04 settings.db
-rw-rw---- system system 22528 2011-11-17 17:30 settings.db.bak(The last command just confirms your handywork.)
Reboot the Android device using the ADB "reboot" command:
# reboot
Once rebooted, you can proceed with the Swiftkey installation. When you reach step 2 of the installation and it directs you to the KF input settings window, you can return from settings window and if you've correctly modified the settings it won't complain that you haven't enabled Swiftkey, and you can go on with the rest of the installation process.
After finishing the install, long-press on a text field to bring up the "Select input method" pop-up menu, which will allow you to switch between the Kindle keyboard and Swiftkey X.
Voila!
I love Swiftkey on my phone but damn this looks so complicated. Thanks though for getting it to work on our devices.
Sooner or later someone will write a script or an app to make it easy.
Interesting timing. A new version of Swiftkey X was released this morning that changed the input methods path; I've updated the instructions above.
If you updated Swiftkey and found it no longer working, as I did, all you need to do is edit the settings.db file using the procedures described above, and reboot the device, after which you can select Swiftkey X as an input method again.
Can you unroot after completing this guide and still keep Swiftkey? Or, in other words, can I temporarily root my KF just to install Swiftkey?
Thanks!
vtluu, why not the tablet version of Swiftkey?
scrotty, yes you can unroot your KF after--I've done that so I can play Amazon videos--and Swiftkey will keep working just fine.
Why not the tablet version? The mobile phone version just happens to be what I have purchased. I might eventually get the tablet version but I find the phone version works pretty well, and in landscape mode the keyboard isn't too wide for my thumbs and I don't find myself needing a split keyboard.
vtluu said:
scrotty, yes you can unroot your KF after--I've done that so I can play Amazon videos--and Swiftkey will keep working just fine.
Click to expand...
Click to collapse
Cool. I decided to use Voodoo OTA RootKeeper for now, but it's good to know a full unroot is viable.
vtluu said:
Why not the tablet version? The mobile phone version just happens to be what I have purchased. I might eventually get the tablet version but I find the phone version works pretty well, and in landscape mode the keyboard isn't too wide for my thumbs and I don't find myself needing a split keyboard.
Click to expand...
Click to collapse
That's exactly what I was hoping to hear!
Thanks!
This works great.
Maybe a list of what should be added for different keyboards in the first post?
Excellent! Waiting on my KF, was hoping someone would have SwiftKey working. Thank you!
//Tapatalk//
Anyone have the value for the Tablet version of swiftkey? It isn't the same as the phone version and I can't install the Tablet version on my phone to check it(it won't let me). Any help is appreciated.
Just figured out the value for Swiftkey X Tablet (v 2.1.0.223):
com.touchtype.swiftkey.tablet.full/.KeyboardService
Not sure (didn't test yet), but it's probably com.touchtype.swiftkey.tablet.full/com.touchtype.KeyboardService for the newer version [EDIT: confirmed by scrotty]
Nice work! Swiftkey is my favorite!!
brian112358 said:
Not sure (didn't test yet), but it's probably com.touchtype.swiftkey.tablet.full/com.touchtype.KeyboardService for the newer version
Click to expand...
Click to collapse
Confirmed. I just purchased Swiftkey Tablet X v2.2.0.38 through the Marketplace and used the value you hazarded above successfully. Yay!
By the way, with Swiftkey Tablet X, I did not get the number pad in the middle when in landscape mode.
On a hunch, I figured that this was due to the KF's resolution. So I installed the free LCD Resolution app from the Marketplace and set the pixel density from 160 (KF default) to 155. That was sufficient to get the number pad to appear.
WARNING: I tried to set the density to 159 at one point (just to set if I could get it as close to 160 as possible). That value seemed to prevent the KF from restarting (stuck forever at "Kindle Fire")! Thankfully, I had not selected the "apply setting on boot" option in the resolution app and so a simple reboot restored to the default 160 pixel density and the KF started properly. Whew!
I'm waiting for a easier way to do it with out risking so much cause knowing me I would mess up something. Keep of the good work
Sent from my Kindle Fire using Tapatalk
Updated: added values for various other keyboards, copied from Swype keyboard thread.
Any ideas if something similar would work on the Nook Tablet?
Very usefull, thank you bro!
downsay said:
Any ideas if something similar would work on the Nook Tablet?
Click to expand...
Click to collapse
If the NT has the same limitation (i.e. no UI to allow alternate keyboard) I would imagine the same procedure could work, yes. That assumes B&N hasn't screwed around with the text input field code to prevent you from selecting between enabled keyboards (via long-press on text intput field).
Only one way to find out... good luck!