I want to make Swype my default keyboard. I have have CyanogenMod's flasable zip and Swype's working apk. I want to replace default keyboard in the zip with Swype. is it possible to do it?
please help
Long pressing on any text field will open a menu..click input method, select keyboard of your choice
gaurav.mishra280295 said:
I want to make Swype my default keyboard. I have have CyanogenMod's flasable zip and Swype's working apk. I want to replace default keyboard in the zip with Swype. is it possible to do it?
please help
Click to expand...
Click to collapse
Ur question isn't clear dude.. if u just want 2 use it as ur default keyboard,do as my friend said.but if u want to delete default keyboard, delete d keyboard apk from system/app using root explorer
Press thnx button if it was helpful(plz)
Sent from my GT-S5670 using XDA
"if u just want 2 use it as ur default keyboard,do as my friend said"
Long pressing to change the keyboard does not make the keyboard the default. Upon reboot, your stock keyboard is used or none if you have removed it. I have to change to Swype upon every boot. Very annoying. There must be a way around this. Does anyone know?
thejayjetson said:
"if u just want 2 use it as ur default keyboard,do as my friend said"
Long pressing to change the keyboard does not make the keyboard the default. Upon reboot, your stock keyboard is used or none if you have removed it. I have to change to Swype upon every boot. Very annoying. There must be a way around this. Does anyone know?
Click to expand...
Click to collapse
I'd love to hear the answer to this as well. Prior to last release of Android, Swype said that it was an Android problem and the next release would fix it. They stated on the user comments section that "we can't help sloppy Android code and it's not our fault". The problem was neither - it still comes up with the standard keyboard as default upon reboot every time
gaurav.mishra280295 said:
I want to make Swype my default keyboard. I have have CyanogenMod's flasable zip and Swype's working apk. I want to replace default keyboard in the zip with Swype. is it possible to do it?
please help
Click to expand...
Click to collapse
Try SwiftKey.
The issue happens with all paid keyboard.
Someone says it's an os fault..someone a Play store fault..someone a bad app coding fault.
The fact is that no one had made a fix.
It's there a way to fix this without touching the alt keyboard (I mean without moving it or installing it manually so to avoid any strange future updates failure) that can prevent the default stock keyboard to stick back as default at each reboot??
I mean..if I back up the stock android keyboard and then uninstall it with Titanium Backup..could it fix?
Sent from my Samsung Galaxy S3 GT-i9300 using TapaTalk2
PIRATA! said:
The issue happens with all paid keyboard.
Someone says it's an os fault..someone a Play store fault..someone a bad app coding fault.
The fact is that no one had made a fix.
It's there a way to fix this without touching the alt keyboard (I mean without moving it or installing it manually so to avoid any strange future updates failure) that can prevent the default stock keyboard to stick back as default at each reboot??
I mean..if I back up the stock android keyboard and then uninstall it with Titanium Backup..could it fix?
Sent from my Samsung Galaxy S3 GT-i9300 using TapaTalk2
Click to expand...
Click to collapse
This issue happens with (almost) all paid keyboards, as the only available keyboards at boot are the stock and free ones, given paid apps are stored in a protected storage area that is unavailable at boot time, at least until the Google Play service is actually started.
That's why (for instance) SwiftKey Free or Smart Keyboard Free are indeed kept as default keyboards after a reboot, but their corresponding paid apps will not and hence the 1st available free/stock keyboard will be selected.
The solution (developers?) could be the paid keyboard being the same free app, working with a "license" paid app. This way, the keyboard would be available at boot time and could be enabled as default, while keeping paid/premium features.
I'm afraid this is an OS restriction (bug maybe?) not yet addressed but with a helper app. The best ones so far imho (just workarounds anyway, as they still require user intervention):
Keyboard Picker
Keyboard Swap
I managed to get it working on 2.3.7 & 2.3.8 successfully but the gesture feature doesn't work(coz it asks for license):sly:. Does anyone know where the Swype licence gets stored(somewhere in /system partition)??
swype somehow checks your build.prop file and based on that check, Swype will work or not.
steps you have to do first:
http://forum.xda-developers.com/showthread.php?t=959192
First you will need to extract the needed files from a stock ROM. If you are still running the stock software, you can use a file explorer app to make a copy onto your SD card. Just copy and paste. You can also pull the files from the stock image or from the Iced glacier ROM. Pulling from Iced Glacier is the easiest method. Just unzip the ROM file and find the needed files.
There are two files, both in the system partition. The first is "Swype.apk" and is in /system/app folder. The second is "libSwypeCore.so" and is in /system/lib/ folder.
Edit: 7/25/11
It seems you must also conciser the source ROM and destination ROM when obtaining the files. Swype does a device/licence check when running, and if it fails the check then Swype will not work. The build.prop lists "t-mobile/htc/ect" as product.brand and Swype seems to check this before running. So use a version of Swype from a ROM with the same build.prop or edit the build.prop manually.
Now to install Swype:
There are two ways to do this, ADB or root explorer. (or other file manager with RW)
Any extra info to help explain what is going on for any new guys will be in green text.
For ADB:
First put the files you extracted into the tools folder of the android SDK, then open an ADB shell to your phone. When that is done, use the following commands. (each line is a separate command)
Remember Linux commands are case sensitive.
First is to mount /system as RW. (this allows you to save files to /system)
Code:
mount -o remount,rw /dev/block/mtdblock4 /system
Then you need to push (save a copy) the files to the correct locations.
Code:
adb push Swype.apk /system/app/Swype.apk
adb push libSwypeCore.so /system/lib/libSwypeCore.so
It may give the files the wrong permissions. (how much access to the system they have) Just to be safe we need to give the files the right permissions.
Code:
chmod 644 /system/app/Swype.apk
chmod 644 /system/lib/libSwypeCore.so
sync
reboot
Your phone will reboot and then you are done.
For Root Explorer:
Extract a copy of the needed files and put them on the SD card.
Then open root explorer and open the "sdcard" folder.
Next find "Swype.apk" and long press it and select "copy" (or if you have already completed this step once, copy "libSwypeCore.so")
Use the back button to go back to the root of the folder tree (up top where it shows your current location, it will show "/" this is where you started from when opening the app)
Locate and open the "system" folder.
You then need to tap the button up top marked "Mount R/W" (this will allow you to make changes and copy the files to the right locations) (this step should not be needed if you have already done so before)
Next open the "app" folder. (or if you are moving "libSwypeCore.so" open the "lib" folder)
Hit the "paste" button to copy the file.
Next long press the file you just copied "Swype.apk" and select "permissions" (or "libSwypeCore.so" as appropriate)
You will see a bunch of check boxes. The will be labeled "read" "write" "execute" across the top and "user" "group" "others" down the left side.
For "user" select the "read" and "write" boxes
For "group" and "others" select the "read" box only. Then select "OK"
When done with the first file, repeat the above steps again with the second file. Observe any changes to the steps that are in orange text.
Next open up a "terminal emulator" app and then run the following commands.
Code:
su
sync
reboot
Your phone will reboot and then you are done.
Hope this helps someone.
Click to expand...
Click to collapse
however, this has not helped my with my Galaxy Ace with custom rom. I guess the build.prop files do not match.
You can try with your Fit however. You need to have the swype.apk and the libswypecore.so files from your Original rom.
Related
Download v0.2 here http://www.megaupload.com/?d=AE4KBC1W
By downloading this you take full responsibility for your actions
original swype.apk if needed http://www.megaupload.com/?d=1S7SILS4
*optional (using astro or root explorer) Navigate to your system/app folder, find the existing swype.apk, make a copy to a back up location.
Rename the download to Swype. Place this on your sd card, navigate to it with astro or your fav file browser, open the apk and choose uninstall to uninstall other version. Then choose install.
if it doesnt uninstall....
Open terminal emulator on your X
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
rm /system/app/Swype.apk
reboot
After reboot verify its gone.
Reopen Terminal Emulator
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/Swype.apk /system/app
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
exit
Open a text box and verify.
This cannot be done by copy and paste in root explorer.
Credit goes to ME
About to try this, I'll let you know if it works.
Worked great thanks bad4u6669!
Worked great, although I had to use the terminal commands. Out of curiosity, is there any reason why I had to resort to using the terminal commands? The installer just failed to install.
Mikerrrrrrrr said:
Worked great, although I had to use the terminal commands. Out of curiosity, is there any reason why I had to resort to using the terminal commands? The installer just failed to install.
Click to expand...
Click to collapse
You don't have to install. Just set permissions and reboot once you drop it in the system apps folder. That assumes you have deleted or renamed the original file.
Straight install typically wont work because the file is edited and it knows it. So you have to force it in there, dont take no for an answer!!!
Worked like a charm =). Best part is the caps lock button has a green indicator to differentiate between it and the shift. Thanks again!
This is a nice upgrade from the homely blue and grey. Thanks.
Nice, looks MUCH better than the blue "Swype -X-"
Works well too
I noticed the Swype icon is just a bit too low in the button
And in the edit panel (Swype from the Swype icon button to the "abc" button) the text is white and hard to read
So the swype icon you hit to bring up the options sits too low in its little box? Possible screen shot.
In the edit box that pops up, what color should it be changed to? One that still goes with the theme but at the same time makes the text readable.
Let me know, get me some screen shots, I'll work on it later.
Okay, the install failed and the terminal commands didn't work. It moved the modified Swype.apk to system/app but it still fails the install.
Any ideas what I'm doing wrong?
EDIT: I didn't uninstall the first Swype. There was no uninstall option in the App Manager. Both the one that Root Explorer pulls up and the one in Settings/Applications.
EDIT 2: Okay, I reinstalled stock Swype and uninstalled it. Now I'm going to try the terminal.
cypherx82 said:
Okay, the install failed and the terminal commands didn't work. It moved the modified Swype.apk to system/app but it still fails the install.
Any ideas what I'm doing wrong?
EDIT: I didn't uninstall the first Swype. There was no uninstall option in the App Manager. Both the one that Root Explorer pulls up and the one in Settings/Applications.
EDIT 2: Okay, I reinstalled stock Swype and uninstalled it. Now I'm going to try the terminal.
Click to expand...
Click to collapse
Your not trying this with root explorer are you?
bad4u6669 said:
Your not trying this with root explorer are you?
Click to expand...
Click to collapse
It's okay, I just got it to work.
Also, I can send you screenshots of what the other guy was talking about if you like.
How did you get it to finally work, posting this will help people wo might run into the same problem.
Screenshots would be nice.
bad4u6669 said:
How did you get it to finally work, posting this will help people wo might run into the same problem.
Screenshots would be nice.
Click to expand...
Click to collapse
I'll do a writeup in a second.
What I did:
1. Email MegaUpload link to my phone because USB wasn't playing nice.
2. Save as Swype.apk
3. Move it to /sdcard (was in /sdcard/downlaods)
Here's where I go wrong.
4. Delete Swype.apk in /system/app
5. Move modified Swype.apk to /system/app
6. Try install and terminal.
Here's where I fix it.
7. Delete modified Swype.apk in /system/app
8. Download original Swype.apk (I somehow lost the backup I saved >.<)
9. Place in /system/app.
10. Install
11. Go to Settings/Applications
12. Uninstall Swype
13. Use terminal
14. ??????
15. Profit!
I edited the screenies into the last post but here they are again.
You can see the Swype icon is a little too low in the first pic.
the second image with the text wont show, can you re upload?
bad4u6669 said:
the second image with the text wont show, can you re upload?
Click to expand...
Click to collapse
I quick pulled it down when I realized there was a phone number in it. I re-uploaded with it edited.
Here it is again.
You get to this menu when you Swype from OPT to ABC.
You should note the Swype logo is misaligned in portrait mode as well as landscape.
Yes, the last few screenshots explain exactly what I was trying to say
Swype icon sits too low, edit panel text is hard to read
AHHHH i see now, ok 2 options, leave that one keyboard as stock XSwype, so it will be gray and blue, or shade those keys gray(or some other color). Swype itself puts the images there when the keyboard is loaded. Its not like all the other keyboards where the letters are part of the image. Changing just one part of the code is beyond my capabilities...
I've read about this here a bit but it's not really well documented or tutorialized.
So, how can someone change stock launcher to whatever launcher he/she wants ?
I know this is done via adb console, this is not the issue. But dunno what needs to be taken out and replaced; if something needs to be renamed or not. Where can the apk files be found for newly installed software ? and also what needs to be removed from the stock launcher ? odex & apk ? I know where to find the apk, but not the odex. and are any more files "bound" to the stock launcher except the apk and the odex file ? If say i use a filemanager to locate my desired launcher (having said launcher installed), will pushing it into the /system/app folder do the trick or do I have to rename it ? That means that basically the system/app folder is like a folder for apps that are launched automatically when phone starts.
Can someone help me & shed some light on this ? Thanks !
as few ways to do this. isntall launcherpro (or what launcher you want).
use root explorer to move com.fede.launcher.apk from /data/app to /system/app
change the name to launcherpro.apk
change the permissions to read for user, group and others. write for user only.
reboot
once you select launcherpro, use root explorer, go to /system/app, and delete launcher.apk or home.apk or whatever your rom uses as stock home/launcher.
or, use adb
Code:
abd push launcherpro.apk /system/app
Thanks man, though I have some questions:
Q1: how do I do
change the permissions to read for user, group and others. write for user only.
Click to expand...
Click to collapse
Q2:
once you select launcherpro, use root explorer, go to /system/app, and delete launcher.apk or home.apk or whatever your rom uses as stock home/launcher.
Click to expand...
Click to collapse
Don't I have to rename launcherpro.apk to home.apk in order for it to work @ startup time ?
Instead of deleting home.apk, perhaps moving them to the sdcard might be better (just in case).
ldq said:
Thanks man, though I have some questions:
Q1: how do I do
Q2: Don't I have to rename launcherpro.apk to home.apk in order for it to work @ startup time ?
Instead of deleting home.apk, perhaps moving them to the sdcard might be better (just in case).
Click to expand...
Click to collapse
you can use root explorer to change permissions. just long press the apk and a submenu will pop up with permissions being an option.
whether or not you need to change the name of launcherpro will depend on your rom/device. you can leave launcherpro as is and leave home.apk in there, reboot. when it boots, it should have a popup asking which you'd like to use as the launcher.
or, install launcherpro like normal, select it to be the default launcher and it should always launch at boot.
thanks a lot ! will try this out !
How to change stock launcher with any launcher
Victory !
Step by step:
1. Backup original launcher
Code:
adb pull /system/app/Launcher.apk Launcher.apk.bak
2. Backup installed launcherpro/adw/golauncher apk's to either HDD or SDcard
2a. Use root explorer mount r/w to copy corresponding file to SDcard & after that
rename the file to Launcher.apk or whatever your stock launcher is. ( user installed apps can be found in /data/app)
2b. Pull file to HDD
Code:
adb pull /data/app/Launcher.apk Launcher.apk
3. Push file to /system/app
Code:
adb push Launcher.apk /data/app/Launcher.apk
4. Reboot & Enjoy
so it seems its a system limitation when using dialer apps where the missed call notification doesn't get cleared when opening the dialer app.. the stock phone app needs to be opened in order to clear it...
i'm running cm7.1 on nexus s 4g.. just installed touchpal dialer.. i read on this site
http://stackoverflow.com/questions/2007024/push-my-apk-to-system-app
that you could push the app into the system folder and that would address the problem.. i downloaded the app from the market so no idea how to get the apk..
i assume if i could get a hold of the apk.. i could use root explorer to change the persmissions, then move the file into system/app and then install the app??
any help would be appreciated.
p.s. all i really want is the search feature of these apps which stock dialer doesn't have.. which is a big oversight by google not to have this.. so if any other solutions are available.. great.. love to hear them
The apk should be somewhere in /data/app, there are also apps that let you backup apk files to sdcard.
Afterwards remount /system to read+write and push the apk file to /system/app.
do i need to uninstall the app from /data/app after? or should i leave that file in there
Using Root Explorer, find the apk in /data/app, long-press and select move. Navigate to /system/app, mount r/w (by pressing the button at the top), and paste. Long-press the apk again, select permissions and set to rw-r--r--, then mount r/o and reboot.
Voila! Your user app is now a system app. You can also use Titanium Backup to convert a user app to system app and vice versa. As I have the paid version I'm not sure if this feature is available in the free version.
Sent from my Evo + MIUI using Tapatalk!
thanks.. seems to work now.. i'm surprised apps can't automatically install in that way to notifications can be dealt with.. guess they don't have permissions to install into system?..appreciate the help.. all works now!!
so seems doesn't like to work like that.. every time i reboot i get a force close popup... then i have to delete the app and restart.. had permissions set correctly and everything
Hey guys,
I still rename my bloat, I know, you probably see this as lame, but maybe someone has the answer anyway.
In system/app, the Motorola Migrate apk (fswriter.apk) can be renamed using root and Root Explorer, but after a minute or so, or a reboot, the apk returns to the original name (I usually add .old to the end). Just about all of the other apks I rename in that folder retain .old in the name even after a reboot. The entire contents of system/vendor/app does this. I can rename the apks, refresh and see they are still renamed, and then a minute later, or a reboot later, they drop the .old or .delete extension.
For now, I disabled the ones that appear in the app drawer, but maybe someone who is curious enough knows the answer.
Thanks,
Jason
JaBr1884 said:
Hey guys,
I still rename my bloat, I know, you probably see this as lame, but maybe someone has the answer anyway.
In system/app, the Motorola Migrate apk (fswriter.apk) can be renamed using root and Root Explorer, but after a minute or so, or a reboot, the apk returns to the original name (I usually add .old to the end). Just about all of the other apks I rename in that folder retain .old in the name even after a reboot. The entire contents of system/vendor/app does this. I can rename the apks, refresh and see they are still renamed, and then a minute later, or a reboot later, they drop the .old or .delete extension.
For now, I disabled the ones that appear in the app drawer, but maybe someone who is curious enough knows the answer.
Thanks,
Jason
Click to expand...
Click to collapse
are you rebooting into R/W mode aka recovery mode? For this line of Droids, after rooting, in order for you remove or change anything within the system you need to reboot into "recovery" and i use the quotations is because in all androids in the past (at least the ones i have had) recovery is TWRP or CWM but with our phones recovery is the OS but the OS is R/W...so make sure you are rooted and then you can either use an app like Rom Toolbox for example, use the rebooter option within and in that menu select Reboot Recovery, it'll reboot into the OS but rewritable once you are booted that way you can add and remove system apps as well as make any name changes to the system files and whatnot...hope this helps
Holo reboot in play store works great for rebooting into recovery or just a normal reboot!
Sent from my XT1080 using xda app-developers app
Hi everyone,
There is a way to find the .apk of apps downloaded from playstore. ull need root and root browser, we will use here esfile explorer. open esfile explorer and press top left-->tools enable root explorer and show hidden files, then go to local-->device now go to file data-->app and thats it, to find system apps u can go to device-->system-->app.
Wiked dudes production
Pull Apk in Non-Rooted Device.
There is no need of a rooted device,
you can pull the apk by using following techniques.
//_______________________________________________________
A) Using ADB
1) Determine the package name of the app, e.g. "com.whatsapp" (WhatsApp).
if you don't know the package name, you have 2 options to get the package name
i) Visit play store and search for the desired application, The link of the app contains the package name. "https://play.google.com/store/apps/details?id=com.whatsapp" (WhatsApp) where com.whatsapp is the package name
ii) use command "adb shell pm list packages" , this will list the package name of all application installed.
2) Once you know the package name, get the apk installed path by using command "adb shell pm path com.whatsapp"
it will return the apk path of the application, like this
package:/data/app/com.whatsapp-2/base.apk
3) Now to pull apk, by using command "adb pull /data/app/com.whatsapp-2/base.apk"
Apk will be extracted to the same folder where adb is present
//_______________________________________________________
B) Using ESFileExplorer
1) Open ESFileExplorer and navigate to User Apps either by (swiping left to right twice) or (goto APP under Library in Navigation Drawer)
2) Select App you want to pull, and click on Share.
3) Share the Apk to another device via Bluetooth or to desktop via AirDroid,
shanrais said:
There is no need of a rooted device,
you can pull the apk by using following techniques.
//_______________________________________________________
A) Using ADB
1) Determine the package name of the app, e.g. "com.whatsapp" (WhatsApp).
if you don't know the package name, you have 2 options to get the package name
i) Visit play store and search for the desired application, The link of the app contains the package name. "https://play.google.com/store/apps/details?id=com.whatsapp" (WhatsApp) where com.whatsapp is the package name
ii) use command "adb shell pm list packages" , this will list the package name of all application installed.
2) Once you know the package name, get the apk installed path by using command "adb shell pm path com.whatsapp"
it will return the apk path of the application, like this
package:/data/app/com.whatsapp-2/base.apk
3) Now to pull apk, by using command "adb pull /data/app/com.whatsapp-2/base.apk"
Apk will be extracted to the same folder where adb is present
//_______________________________________________________
B) Using ESFileExplorer
1) Open ESFileExplorer and navigate to User Apps either by (swiping left to right twice) or (goto APP under Library in Navigation Drawer)
2) Select App you want to pull, and click on Share.
3) Share the Apk to another device via Bluetooth or to desktop via AirDroid,
Click to expand...
Click to collapse
ur right however, not all system apps are present using the second way, and first way is complicated for some people and might confuse them. if someone would want to change something he saw on google, that is connected to system apps or other stuff"like systemui" i think rooting and copying the apk from its directory is best. btw thanks for ur concern about this, believe it or not for the first 7 month i posted this it posted in android wear, and no one was commenting, i made it with the xda app, i think it has alot of bugs.
Lord_of_Death said:
ur right however, not all system apps are present using the second way, and first way is complicated for some people and might confuse them. if someone would want to change something he saw on google, that is connected to system apps or other stuff"like systemui" i think rooting and copying the apk from its directory is best. btw thanks for ur concern about this, believe it or not for the first 7 month i posted this it posted in android wear, and no one was commenting, i made it with the xda app, i think it has alot of bugs.
Click to expand...
Click to collapse
IMO, if one is able to root the phone, then he will certainly not find any complication in pulling apk using first way.
shanrais said:
IMO, if one is able to root the phone, then he will certainly not find any complication in pulling apk using first way.
Click to expand...
Click to collapse
u might be right bro but rooting is only downloading a file and flashing it through odin.