Related
I am using My Vodafone Magic (B) with Cyaonogen 3.9.7 and Palm Pre 1.9, and the CompCache Script. I got it all to work near perfect with the boot.img postet by xordis.
Now here is the (only) Problem:
Since I am german i am lacking some keys on the Touch Keyboard, so I tried to Install TouchPal w German Language Pack.
This returns: Installation Unsuccsessful and Package not signed or something like that.
So i looked: there already is some older version of TouchPal that had to come with the Rom, and I cannot uninstall it. The App hasnt even a real Icon in the package Browser.
Also i cannot remove the /system/app/TouchPalMain.apk with all the root i have, cause its on a "Read-only file system", though I dont know if that would solve my Problem.
I am absolutely out of Ideas and need help
I solved my Problem:
adb remount
adb shell find / >log.txt
search log.txt for all occurences auf "touchpal"
adb shell rm <file>
now i can install TouchPal from the Market succsessful, but:
TouchPal is showing up in the List of Input Methods after reboot
Hi guys,
I need some help. I'm on miui 1.7.22 N1.
The new market v. 3.0.27 is pretty laggy and takes time to load apps ecc
I prefer the old 2.3.6 (I think this is the last 2.x version) but everytime I install 2.3.6 the new version appears...with automatic update
So, is there a way to keep the 2.3.6 and stop vending.apk from being updated?
Thank you guys
Edit: what about changing some permission with rootexplore, could help?
Remove marketupdaelter.apk by any chance or maby use FOTAkill.apk
well this all depends on how android determines if you need an upgrade. if its based on version number then there is a 'permanent' fix. modify the AndroidManifest.xml and change the
Code:
android:versionCode="2.3.6"
android:versionName="2.3.6"
to
Code:
android:versionCode="999.0.0"
android:versionName="some crazy high version number"
maybe someone else will know the mechanism for knowing if an update is available but this should work... at least until your version number is actually in existance
@luke thank you but I tried this
a) Using Root Explorer, navigate to /data/data
b) Press and hold on the folder "com.android.vending.updater" and select "Move"*, then paste it in /sdcard.
c) Navigate to /system/app, press and hold on "Marketupdater.apk", select "Move"*, then paste it in /sdcard as well.
Then I tried a *#*#checkin#*#* reboot and the new market appears...
maybe there's the new apk cached somewhere...
@killer
Thank you Ill try the AndroidManifest.xml method
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!
Hi All,
I set out to flash my tablet back to stock with the goal of copying some of the awesome asus-specific widgets and applications and installing them back on my tablet after I re-rooted/modded it. I accomplished part of this goal by finding some of the .apk's I wanted, like the Asus weather & battery widgets, the Supernote.apk, anda few others (I still wasn't able to find the Swype Keyboard.apk file)
Anywho, I tried to install the .apk's on my tablet after re-installing cm9 and rooting it but it just says "Application not installed". Anyone have any ideas? And can anyone elaborate on how to copy that swype keyboard APK that I desperately want? I found the other .apk's in the /system/app folder but swype wasn't there.
My other questions relate to CM9:
1) is there any way to decrease the boot time for CM9, or at least customize the boot screen?
2) I'm currently running an older version of cm9 (rc0 unofficial) and I have the stable rc1 of cm9 but when i tried to flash it, it didn't work (i can get the exact error message if needed). Did I do something wrong in updating or is RC1 not compatible with the device? Should I just wait till CM10 comes out?
3) When I initially rooted/flashed cm9, I was able to connect my tablet to my computer and the root of the / directory, but after flashing stock and trying again, I don't have the same luck. Is there some step I missed?
I appreciate any responses, thanks.
- Opethfan89
3 days, 300 views, no responses. BUMP anyone?
opethfan89 said:
Hi All,
I set out to flash my tablet back to stock with the goal of copying some of the awesome asus-specific widgets and applications and installing them back on my tablet after I re-rooted/modded it. I accomplished part of this goal by finding some of the .apk's I wanted, like the Asus weather & battery widgets, the Supernote.apk, anda few others (I still wasn't able to find the Swype Keyboard.apk file)
Anywho, I tried to install the .apk's on my tablet after re-installing cm9 and rooting it but it just says "Application not installed". Anyone have any ideas? And can anyone elaborate on how to copy that swype keyboard APK that I desperately want? I found the other .apk's in the /system/app folder but swype wasn't there.
My other questions relate to CM9:
1) is there any way to decrease the boot time for CM9, or at least customize the boot screen?
2) I'm currently running an older version of cm9 (rc0 unofficial) and I have the stable rc1 of cm9 but when i tried to flash it, it didn't work (i can get the exact error message if needed). Did I do something wrong in updating or is RC1 not compatible with the device? Should I just wait till CM10 comes out?
3) When I initially rooted/flashed cm9, I was able to connect my tablet to my computer and the root of the / directory, but after flashing stock and trying again, I don't have the same luck. Is there some step I missed?
I appreciate any responses, thanks.
- Opethfan89
Click to expand...
Click to collapse
I haven't tried this, but it may work. If you have ADB on your computer, try doing an adb push [name of file].apk /system/app/
If you can't do that, try copy/pasting them there using a root explorer on your device itself. Make sure the permissions are set properly (I don't remember what they are off the top of my head).
After doing that, reboot. See if it works.
As for your CM Questions:
1) I'm not sure if you can reduce the time. For customizing the animation, look at something like Rom Toolbox Pro (which also includes a root explorer like I mentioned above).
2) All CM9 TF300T downloads are located here: http://get.cm/?device=tf300t RC1 is listed there so I'm assuming you did something wrong (what's the error you get?)
3) Did you re-root? I'm not sure I understand.
Link9228 said:
I haven't tried this, but it may work. If you have ADB on your computer, try doing an adb push [name of file].apk /system/app/
If you can't do that, try copy/pasting them there using a root explorer on your device itself. Make sure the permissions are set properly (I don't remember what they are off the top of my head).
After doing that, reboot. See if it works.
As for your CM Questions:
1) I'm not sure if you can reduce the time. For customizing the animation, look at something like Rom Toolbox Pro (which also includes a root explorer like I mentioned above).
2) All CM9 TF300T downloads are located here: http://get.cm/?device=tf300t RC1 is listed there so I'm assuming you did something wrong (what's the error you get?)
3) Did you re-root? I'm not sure I understand.
Click to expand...
Click to collapse
I apologize for the vagueness of my original post. I made this thread in anticipation of flashing everything back to stock, trying to copy over those Asus-specific .apk's (which I managed to do), and then re-rooting/re-flashing CM9.
I flashed the .30 firmware to get back to stock and found the Asus widgets & apk's I was looking for in the /system/app directory. After some bootloops and other fun, I was able to flash back to CM9 and when I tried to install the .apk's I immediately get the message "The Application was not installed"
Of the asus items I wanted, Supernote and Polaris Office were my top two picks, and I was able to acquire Supernote through 3-rd party means and install it. So I'm stoked to have Supernote on a CM9-flashed tablet. I wasn't able to find Polaris Office so I hope to at least be able to find a work-around to install that.
In response to #3 - yes I re-rooted my tablet (lost root with the .30 firmware) and previously I was able to browse the root directory of my tablet while it was connected to my computer. Now, I can only browse the SD card. I still haven't figured out a solution to this, but I just transfer files to my memory card and then to my tablet from there. I'm looking into how to do OTA file transfers via bluetooth or wi-fi, if at all possible.
opethfan89 said:
I apologize for the vagueness of my original post. I made this thread in anticipation of flashing everything back to stock, trying to copy over those Asus-specific .apk's (which I managed to do), and then re-rooting/re-flashing CM9.
I flashed the .30 firmware to get back to stock and found the Asus widgets & apk's I was looking for in the /system/app directory. After some bootloops and other fun, I was able to flash back to CM9 and when I tried to install the .apk's I immediately get the message "The Application was not installed"
Of the asus items I wanted, Supernote and Polaris Office were my top two picks, and I was able to acquire Supernote through 3-rd party means and install it. So I'm stoked to have Supernote on a CM9-flashed tablet. I wasn't able to find Polaris Office so I hope to at least be able to find a work-around to install that.
In response to #3 - yes I re-rooted my tablet (lost root with the .30 firmware) and previously I was able to browse the root directory of my tablet while it was connected to my computer. Now, I can only browse the SD card. I still haven't figured out a solution to this, but I just transfer files to my memory card and then to my tablet from there. I'm looking into how to do OTA file transfers via bluetooth or wi-fi, if at all possible.
Click to expand...
Click to collapse
So did you try what I suggested in my post (pushing the files to /system/app on your tablet, rather than trying to install them through File Browser or whatever)?
I'm not sure if they rely on any custom Asus framework stuffs, like with many other OEMs. I personally doubt it because Asus barely changes anything. I think it *should* work, but can't guarantee it.
The easiest way to get the files to /system/app (if you're not very ADB or tech. savvy) is to download a root explorer (like Rom Toolbox Pro has, for example) and copy all the .apks that you want from your sdcard to /system/app.
Link9228 said:
So did you try what I suggested in my post (pushing the files to /system/app on your tablet, rather than trying to install them through File Browser or whatever)?
I'm not sure if they rely on any custom Asus framework stuffs, like with many other OEMs. I personally doubt it because Asus barely changes anything. I think it *should* work, but can't guarantee it.
The easiest way to get the files to /system/app (if you're not very ADB or tech. savvy) is to download a root explorer (like Rom Toolbox Pro has, for example) and copy all the .apks that you want from your sdcard to /system/app.
Click to expand...
Click to collapse
I haven't tried pushing the files via ADB yet. I just wiped out my computer so I need to re-install the drivers to get the tablet recognized and/or the the Android SDK.
In the 3rd point of your point, do you mean my external SD card or the internal memory?
the Transformer Pad has a good portion of internal memory partitioned as an sdcard and mounts it at /sdcard/. I haven't used an external SD card with my tablet yet. Either one should work.
I also found out that Polaris Office has some library files that you probably should grab as well. You can find them at:
/system/lib/libpolarisoffice_tablet.so
/system/lib/libpolarisofficedump.so
/system/lib/libtfapps-polaris.so
/system/lib/libtflua-polaris.so
Click to expand...
Click to collapse
There might be some library files for the other apps. You might want to look around in the /system/lib folder for other libraries as well.
Link9228 said:
the Transformer Pad has a good portion of internal memory partitioned as an sdcard and mounts it at /sdcard/. I haven't used an external SD card with my tablet yet. Either one should work.
I also found out that Polaris Office has some library files that you probably should grab as well. You can find them at:
There might be some library files for the other apps. You might want to look around in the /system/lib folder for other libraries as well.
Click to expand...
Click to collapse
That's awesome, thanks. If I'm able to get this working I will post a guide for others to follow. I ended up just signing up for the swype beta (which I think is stupid since I paid for that app when I bought my tablet, shouldn't have to get a reduced version)
I was able to find a working supernote.apk app on a 3rd-party website and it installed and worked perfectly.
My other issue I'm having is I try to push the files with ADB and it tells me my tablet is read-only? it gives that same message no matter which directory I try to push to. I have the superuser app and have root, but superusers' log shows the 'adb shell' is consistently being denied root permission (if i try to do su or something similar). Any thoughts?
opethfan89 said:
That's awesome, thanks. If I'm able to get this working I will post a guide for others to follow. I ended up just signing up for the swype beta (which I think is stupid since I paid for that app when I bought my tablet, shouldn't have to get a reduced version)
I was able to find a working supernote.apk app on a 3rd-party website and it installed and worked perfectly.
My other issue I'm having is I try to push the files with ADB and it tells me my tablet is read-only? it gives that same message no matter which directory I try to push to. I have the superuser app and have root, but superusers' log shows the 'adb shell' is consistently being denied root permission (if i try to do su or something similar). Any thoughts?
Click to expand...
Click to collapse
You need to remount your system as read-write. Trying doing an adb remount. If that doesn't work, try typing the following into a terminal emulator:
su
busybox mount -o remount,rw /system
Click to expand...
Click to collapse
Try ADB pushing again after that.
if you are able to install the apps by adb push. then maybe a .zip file can be created and use CWM to install all the stock apps.
Link9228 said:
You need to remount your system as read-write. Trying doing an adb remount. If that doesn't work, try typing the following into a terminal emulator:
Try ADB pushing again after that.
Click to expand...
Click to collapse
Well part of the issue is that I can't "su" while in adb shell. It says permission denied. When I type ADB devices normally, it'll list my device. But when I'm in "adb shell" it doesn't show anything. "adb remount" gives me the message "error: device not found".
Any other suggestions?
opethfan89 said:
Well part of the issue is that I can't "su" while in adb shell. It says permission denied. When I type ADB devices normally, it'll list my device. But when I'm in "adb shell" it doesn't show anything. "adb remount" gives me the message "error: device not found".
Any other suggestions?
Click to expand...
Click to collapse
That's weird. I've never seen that before. Are you certain that your adb drivers are installed properly? You can always use a terminal emulator on your device itself to remount the system as read/write and then use adb afterwards.
Link9228 said:
That's weird. I've never seen that before. Are you certain that your adb drivers are installed properly? You can always use a terminal emulator on your device itself to remount the system as read/write and then use adb afterwards.
Click to expand...
Click to collapse
I'm pretty sure my drivers are installed correctly. Everything shows up in device manager, "adb devices" lists my device, fastboot flashes files just fine, so yea.
And yea I have the terminal emulator on my tablet and I've used it before for some stuff (installing Ubuntu) so I will try the steps you guys have mentioned. I'm in the process of trying out some other ROM's right now (Hydro atm, and then probably CleanROM) so once I go back to stock and have access to the appropriate files I'll try these steps.
Bought a new nexus 7 yesterday (after having my old one stolen...) and I decided to root and install AOKP JB MR1 Milestone 1. I'm really impressed with it but I was surprised to find the AOSP browser rather than Chrome and a lack of Performance Control.
I tried to install Chrome as a system app (download from Play, push from /data/app to /system/app and set permissions to rw-r--r--) and rebooted. I was again surprised when I found that "Chrome's installation was incomplete." It worked fine in /data/app but I am now curious as to why it won't work in /system/app. (Sorry if this sounds nooby, I haven't dealt with rooting Nexus devices before, I only rooted my crappy old GT-S5830)
Does anyone have a solution? Missing lib files or something else that I need to transfer over?
And as a sidenote, is Performance Control compatible with the N7 on this build? And does anyone have a working version of it?
Check the apk. I think it has a lib file that you need to put into /system/lib. I'm also trying this out as of the moment with a LatinIME.apk