First of all, make a backup!! I am not responsible for the terrible things that can happen to an android device when things go awry lol....
Secondly, I have only tried this using Vegan rom (beta 4, and beta 5.1)... I am assuming it will work with any alternate rom but NO PROMISES!!
TO OBTAIN THE NEEDED FILES:
1) Do a google search for "swype on gtablet (kinda)"
2) Somewhere the search results (it was the very first one when I did the search), you should see a post on the tegratab.com forum entitled "swype on gtablet (kinda)" (posted by rothnic)
3) Download the package on that forum, and extract it. There should be three files located in this package: swype.apk, libswypecore.so, and build.prop.
**Keep the page open as we are also going to use the top of the build.prop file that rothnic posted there!! THANK YOU ROTHNIC!!!!!
INSTALL METHOD USING ROOT EXPLORER
I would complete these steps entirely from your gtab, as it does away with the need to transfer files from a pc, etc!
1) Using root explorer, copy first the swype.apk file, and paste it to \\system\app. Once it is copied, long press on it and click "permissions". The permissions should be set as follows:
Read: Check all three boxes down (for user, group, and others).
Write: Check the first box (for user)
Execute: Check the first box (for user)
2) Now again using root explorer, copy the libSwypeCore.so file, and paste it to \\system\lib. Make sure you mount the \\system\lib folder as "read/write" before copying. Once it is copied, set the permissions exactly as you did for the swype.apk file. Make sure you mount the \\system\lib folder as "read only" again before you exit.
3) Now its time to edit the build.prop file, only we are going to make it easy. Instead of going through and editing it, copy the top of the file that rothnic posted on the tegratab site, and replace the top of your build.prop file with what he has there. Don't edit it or anything, just copy it word for word. I did this in root explorer by doing the following:
Using Root Explorer, browse to \\system. Once in this folder, mark it as "read/write".
Locate the build.prop file, and long press on it.
Select "open in text editor".
Copy the text that rothnic had in the post on tegratab, and use it to replace the text that already exists there at the top of the file. It will fit exactly as the original one that you are replacing did. DO NOT CHANGE THE BOTTOM OF THE FILE AT ALL!!!
When you have copied the text, press the "settings" button, and press "save and exit".
(FYI, I am using Vegantab beta 5.1, and replacing the top of the build.prop file did not do any damage to the tablet at all)
Now restart the tablet.
When the tablet restarts, long press on any text entry field and press "input method".
Swype should be an option. Select it, and start swyping!!
If swype isn't listed, click settings, language and keyboard. Check the box next to swype.
(this will also be a good time to click on swype settings and DISABLE audio feedback, as it will drive you and everyone around you NUTS!!)
Now follow the steps above to set swype as your input method and enjoy!!
INSTALL METHOD USING TERMINAL (Courtesy of Terrypchan)
This can be done without root explorer, BUT you have to be willing to type commands in a terminal emulator. I did it without root explorer by using the terminal emulator app with the VEGAn b5 rom (which is already rooted). The only tricky command you need to do is:
1. su
2. cd /
3. mount -w -o remount /dev/block/mtdblock3 /system
Step 3 is how you mount /system as read-write. That allows you to copy the apk to /system/app and to copy the lib to /system/lib. You can also copy build.prop to /system here. I also did the chmod commands here as well, i.e.
chmod 644 /system/lib/libSwypeCore.so
chmod 644 /system/app/Swype.apk
I had already edited the build.prop on another machine where I could use a real text editor.
This is the command to remount /system as read-only:
mount -r -o remount /dev/block/blockmtd3 /system
reboot and I'm Swype-ing away.
any chance you could paste the build prop edit in here? For some reason my browser is cutting off part of it.
Thanx,
I bet the mod deletes this within the hour!
Hmm, wonder how long this post will last
Agreed... I respect the effort tho and his directions are perfect!
Thanks brotha...
Sent from my SGH-T959
Instructions worked perfectly for me with the small substitution of adb push/pull to edit the build.prop (root explorer force closed after I had edited the file and before saving so I said screw it ). Thanks!
Combine this with the rainex fix for screen smoothness and it makes for a pretty good time lol
Sent from my Droid using XDA App
You don't have to adb it, that's why he recommended root explorer. If you edit it there it automatically makes a backup for you. I've done this with three ROMs, vegan4, zpad3, and vegan5... Never had to use adb
Sent from my Zpad flavored Gtab...
Need help with editing build.prop....swype rar had build.prop in it. Do I copy that same file in full and paste it at the top of build.prop in /system/build.prop...I am confused as to hoe many lines of build.prop I need to edit or change?
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
worked for me just fine.
Followed instructions, and used a little common sence along the way. Now it's all up and running.
Thanks a lot for the write up..
Using swpe to type this...
Thanks so much man!
New2Android said:
Need help with editing build.prop....swype rar had build.prop in it. Do I copy that same file in full and paste it at the top of build.prop in /system/build.prop...I am confused as to hoe many lines of build.prop I need to edit or change?
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
Click to expand...
Click to collapse
No ignore the build file in the rar file....
You need to follow the directions exactly and copy the text from the forum post. Remember only the top portion
Swype Keyboard
Confirmed Working on the G tab following above steps. Stock TnT Firmware 3389. Working flawless. Sound and swype.
I am able to get the swype keyboard to come up and type on it but am not able to swype. Dont know what i am doing wrong.
Edited build.prop as shown in the forum still cant swype but just use swype keyboard as a regular keyboard.
Any help will be appreciated
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
Any downside to editing the build file in this manner?
Can you change it back after it is installed?
Do you have to redo this every time you go to update your rom?
TaterTot24 said:
Any downside to editing the build file in this manner?
Can you change it back after it is installed?
Do you have to redo this every time you go to update your rom?
Click to expand...
Click to collapse
Thats the nice thing about root explorer, it automatically makes a backup when you have modified it
Yes this would need to be redone for each rom.
Sent from my VegaN 'flavored' GTab...
New2Android said:
I am able to get the swype keyboard to come up and type on it but am not able to swype. Dont know what i am doing wrong.
Edited build.prop as shown in the forum still cant swype but just use swype keyboard as a regular keyboard.
Any help will be appreciated
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
Click to expand...
Click to collapse
I initially had the same issue, there's something incorrect in the build.prop. PM me and I'll get a copy of mine to you as i'm using VegaN5 as well.
Sent from my VegaN 'flavored' GTab...
Wow. I can't believe this is still here! Anyway, on to my question...
Is it possible/advised to edit the build.prop on a PC using a standard text editor like notepad? I ask because the browsers on my GTab don't show the whole of the text we're supposed to copy from tegratab.
Thanks in advance.
Editing on a pc is probably fine, however you have to make sure the formatting stays correct, otherwise it all goes south lol.
I printed out a copy of the top of the build.prop that rothnic posted on the tegratab site and used that for reference when editing on my tab....made it easier to see where I was in the text editor
Sent from my Droid using XDA App
TaterTot24 said:
Any downside to editing the build file in this manner?
Not that I have seen so far, and I've used this through two roms now
Can you change it back after it is installed?
as i2steve said, root explorer is awesome and makes a copy of the original file for you
Do you have to redo this every time you go to update your rom?
Click to expand...
Click to collapse
Unfortunatley, yes, so I would keep the files saved somewhere on your tab lol
Sent from my Droid using XDA App
alright... I rooted my nook color, and I was wanting to change the screen specs to match the galaxy tab, but when I open my system > build.prop file in the root explorer, I can't change anything... any suggestions??
this is because the NookColor's stock LCD density is 169.333, which is pretty low (Galaxy Tab is 240). Unlike resolution, which is hardware-based, density is software-based and can be changed. If you search the market for LCD density, there are a couple apps that will do this--a free one that won't survive a hard reboot, and a paid one that (supposedly) will.
If you want to make it permanent for free, you can edit your build.prop file. Again, use Root Explorer to open system/build.prop (BACKUP FIRST!), find the following two lines:
ro.sf.lcd_density.xdpi=169.33333
ro.sf.lcd_density.ydpi=169.33333
If you wanted your density to be 250, you'd replace them with the following single line:
ro.sf.lcd_density=250
Save the edited file, and reboot.
Click to expand...
Click to collapse
Mount the /system partition as r/w first, there is a button on the top.
Forgot to mention that I tried that.. I restarted root explorer... no change
Sent from my HTC Glacier using XDA App
I just did it with mine no problems.
Sent from my LogicPD Zoom2 using Tapatalk
long press "build.prop" and select "open in text editor" from the popup menu.
Also 240 will be way to big. The menus wont fit. Im on 200 right now and some screens are off but not to bad.
sent from my Rooted Nook Color using Tapatalk
arda99 said:
long press "build.prop" and select "open in text editor" from the popup menu.
Click to expand...
Click to collapse
thanks... only time I'd used it was on my HTC Glacier (mytouch 4g), and I didn't have to do that... works like a champ
Can't get /system into r/w
I'm trying to change my build.prop file to change the display density on my NC.
I have an edited file waiting to be used.
I want to rename the original build.prop to something like build.old and copy the new file in next to it.
But Root Explorer won't change /system to r/w.
I can't rename the original file or paste the new file.
I can flip root "/" back and forth from r/o to r/w without problem.
But nothing happens when I touch or hold the button when in /system.
?????????
Did you figure this out? I am having the same issue modifying files for the hulu fix.
I was confused...everytime i edited my build.prop with root explorer...i remounted R/W....i did every trick...and saved it...after a reboot..my build.prop returns back to the default things with no additional with my edited file.....whats happening here??...TT
i am using GDX v010
The same happen to me
Sent from my E15i using XDA Premium App
he he their are two bulidprop
so antother buildprop is in bin folder replace this also then it will permanently changed
Thanks
Sent from my X8 using XDA Premium App
u need to change the permissions to rw- r-- r-- before you reboot
Read - check all three
write - check the USER
execute - all are blank
save then reboot, then reboot (BE SURE TO MAKE A NANDROID BACKUP 1st!!!!)
Its not done that way.Even if the two build.props are edited and the permissions are set to rw-r-r sometimes you wont see a change.
This is because some custom roms now have a tweak to change the build.prop back to default on boot.So if you want to change the build.prop then you will have to change it in the computer and then reinstall the rom to your phone.
Sorry to ask this, but i was wondering why built.prop restored to it's original state when rebooting phone? i was going to edit built.prop to make some tweak...
But after reboot, built.prop look like untouched...
Using rootexplorer edit, Flash tool.
same result
ROM:Fd experience 2.0.0 rev3
Single built.prop in /system only
CKKnot said:
Sorry to ask this, but i was wondering why built.prop restored to it's original state when rebooting phone? i was going to edit built.prop to make some tweak...
But after reboot, built.prop look like untouched...
Using rootexplorer edit, Flash tool.
same result
ROM:Fd experience 2.0.0 rev3
Single built.prop in /system only
Click to expand...
Click to collapse
That problem I have but I searched theat build and find in system/bin/build and editet that and other in /system I don't know how is on Fd experience but on gingerxperia is
You have to edit both files in system/build.prop and system/bin/build.prop to make changes permanent.
And I think this applies on all ROMs.
Yes, must change /system/built.prop and /system/bin/built.prop to make a changes permanent for my rom it's /system/built.prop and /system/bin/built thanks
I need to follow these instructions -
Originally Posted by Robbie Hood
i will upload a revert back too mtp mod once the party is over.
If you really need it now then do this :
go to /system/build.prop and open it with a rooted text editor ( most file explorers have one) and remove this line:
Code:
persist.sys.usb.config=mass_storage,adb
then go to /system/etc/init.d and remove the S98MassStorage script.
Reboot and it should work fine.
If not , then you need to check rom customizer/. manage system apps / uninstalled tab and install anything kies, usb or mtp related
I have done the first part and removed - persist.sys.usb.config=mass_storage,adb but I can't change/delete/edit/move the S98MassStorage script, I have tried Root Browser Lite, ZArchiver and ES File Explorer.
Can somebody help me please, recommend a method/app?
Try "su -"
Then "rm whateverscript.sh"
To delete the file.
Assuming u got root perms.
Sent from my GT-N7000 using xda app-developers app
Make sure your /system is mounted read-write. It should be, since you edited build.prop, but you can double-check (there's an option in ES File Explorer to mount /system as read-write).