Need help with build.prop edit - G2 Q&A, Help & Troubleshooting

I have rooted my phone and installed cwm recovery with the loki images built in. I am trying to modify my build.prop file so I can hide my soft keys manually and use lmt pie, but when I'm using Root Explorer (after I've mounted it as r/w) and when I open it with a text editor from RE it says "This file is too I large..." and displays a truncate version. It also won't let me save any edits. What am I doing wrong?

in_dmand said:
I have rooted my phone and installed cwm recovery with the loki images built in. I am trying to modify my build.prop file so I can hide my soft keys manually and use lmt pie, but when I'm using Root Explorer (after I've mounted it as r/w) and when I open it with a text editor from RE it says "This file is too I large..." and displays a truncate version. It also won't let me save any edits. What am I doing wrong?
Click to expand...
Click to collapse
I can do that above with RE, very strange problem you have.
Try a build.prop editor, i used this in the link. It sets correct permissions after editing and so on. Use the pencil icon in the bottom right to edit.
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor

Hi,
Same thing for me with Root Explorer, instead I use build.prop Editor
EDIT: not fast enough :laugh:

qsec said:
I can do that above with RE, very strange problem you have.
Try a build.prop editor, i used this in the link. It sets correct permissions after editing and so on. Use the pencil icon in the bottom right to edit.
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Click to expand...
Click to collapse
I got it and tried exactly like you said, and while it does pull it up and my keyboard pulls up and I can feel the haptic feedback, no letters will be inserted in deleted...? Really weird.

Maybe it's related to my root access? TB is showing I'm rooted, but check out my superuser app when I try to update an install new binaries...

Get rid of Superuser and try SuperSu instead. Sometimes the old Superuser has issues on ROMs since ICS.

EniGmA1987 said:
Get rid of Superuser and try SuperSu instead. Sometimes the old Superuser has issues on ROMs since ICS.
Click to expand...
Click to collapse
Downloaded and installed... Removed the old one. Still not letting me edit... Looks an feels like it is but won't enter any characters. At least RE isn't giving me the "too large" error anymore

in_dmand said:
I got it and tried exactly like you said, and while it does pull it up and my keyboard pulls up and I can feel the haptic feedback, no letters will be inserted in deleted...? Really weird.
Click to expand...
Click to collapse
i had the same issue, couldn't figure out why. try replacing a commented line with the code to disable the nav bar

How do I know if it's just a commented line and not necessary to the program?

in_dmand said:
I have rooted my phone and installed cwm recovery with the loki images built in. I am trying to modify my build.prop file so I can hide my soft keys manually and use lmt pie, but when I'm using Root Explorer (after I've mounted it as r/w) and when I open it with a text editor from RE it says "This file is too I large..." and displays a truncate version. It also won't let me save any edits. What am I doing wrong?
Click to expand...
Click to collapse
i had the same issue any help?

If you are in stock android 4.4.2 dont do it
You will stuck on bootloop
If you still wand to do let copy your build.prop to pc and edit with notebat++ or some program and recopy overwrite to your phone
Sent from my LG-D802 using xda app-developers app

maxkanick said:
If you are in stock android 4.4.2 dont do it
You will stuck on bootloop
If you still wand to do let copy your build.prop to pc and edit with notebat++ or some program and recopy overwrite to your phone
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
You are right, I have tried to edit it on pc and stuck on a bootloop.

Use build.prop editor app from playstore
_____________________________________Read more write less and be smart

Related

Your Device is not compatible with this item?

Im dual booting winmo and just installed AmeriCanAndroid ( via SD) .So Since my HD2 is finally runnig android, I went to get words with friends to play with my wife.And it said " Your Device is not compatible with this item".I didnt see anywhere on forums that had to do with this error on HD2.Any help?
x_Jack_x said:
Im dual booting winmo and just installed AmeriCanAndroid ( via SD) .So Since my HD2 is finally runnig android, I went to get words with friends to play with my wife.And it said " Your Device is not compatible with this item".I didnt see anywhere on forums that had to do with this error on HD2.Any help?
Click to expand...
Click to collapse
Possibly that app doesn't support being installed to the sd card? Just a guess.. Maybe you could try app to sd?
kylew1212 said:
Possibly that app doesn't support being installed to the sd card? Just a guess.. Maybe you could try app to sd?
Click to expand...
Click to collapse
It doesnt give me that option.I click on the app ( and its several that are having this issue)It doesnt even give a dload option.As soon as i click the app, it gives that message.Ive already tried changing the lcd resolution.Still same issue.IDK if it the market, the build im using, or my phone is just mad I put android on it..lol.Like the facebook that on it.Facebook works, and said theres a newer version, I click to update to newer. and get that error aswell.Makes no sence to me.
x_Jack_x said:
It doesnt give me that option.I click on the app ( and its several that are having this issue)It doesnt even give a dload option.As soon as i click the app, it gives that message.Ive already tried changing the lcd resolution.Still same issue.IDK if it the market, the build im using, or my phone is just mad I put android on it..lol.Like the facebook that on it.Facebook works, and said theres a newer version, I click to update to newer. and get that error aswell.Makes no sence to me.
Click to expand...
Click to collapse
Something is wrong (obviously) is this the first SD build you've used? Check to see if theirs a newer version and try it because their could have been a bug.. Honestly I would recommend nand install but I understand not everyone wants that. I would have to at least try reinstalling it and possibly a different rom...
Hope that helped some!
Sent from my NexusHD2 using xda premium
Fix Market problem: AmeriCanAndroid HD2 GB2.3.7 CM7.1
x_Jack_x said:
Im dual booting winmo and just installed AmeriCanAndroid ( via SD) .So Since my HD2 is finally runnig android, I went to get words with friends to play with my wife.And it said " Your Device is not compatible with this item".I didnt see anywhere on forums that had to do with this error on HD2.Any help?
Click to expand...
Click to collapse
Install File Expert (file explorer).
Browse to /sdcard/Android/
Click to edit "startup.txt" & chose an editor (I use TED text editor)
Edit the lcd_density=167 to lcd_density=160
Exit editor saving the file
Browse to Internal storage /system/
Long click on "build.prop" and change permissions to get full access to the file.
Long click on "build.prop" and Open as.. text (Using TED text editor)
Scroll all the way down till you find & edit the ro.sf.lcd_density=167 to ro.sf.lcd_density=160
Exit editor saving the file.
Exit File Expert
Open Application Manager and go to Market
Select "Details/Clear cache/Force stop"
Click "Force stop" & "OK"
Click "Clear data" & "OK"
Exit App Manager
Open the Rom Manager app.
Touch "Fix Permissions"
Re-boot
Hopefully this works! If not, try changing density to 240 (instead of 160) as many advise this is better. However a 240 density, makes display larger, while 160 is very much similar to what you now have.
(based on this thread: http://forum.xda-developers.com/showthread.php?t=1344334)
I run NAND builds and this is something that I have noticed. For example an app would work just fine with typhoon CM7, but when running Hyperdroid CM7 it would give me the compatibility error like you're getting. My guess is it has something to with how the ROM is cooked, but I could be wrong; I'm still kinda NEWB
Sysifos said:
Install File Expert (file explorer).
Browse to /sdcard/Android/
Click to edit "startup.txt" & chose an editor (I use TED text editor)
Edit the lcd_density=167 to lcd_density=160
Exit editor saving the file
Browse to Internal storage /system/
Long click on "build.prop" and change permissions to get full access to the file.
Long click on "build.prop" and Open as.. text (Using TED text editor)
Scroll all the way down till you find & edit the ro.sf.lcd_density=167 to ro.sf.lcd_density=160
Exit editor saving the file.
Exit File Expert
Open Application Manager and go to Market
Select "Details/Clear cache/Force stop"
Click "Force stop" & "OK"
Click "Clear data" & "OK"
Exit App Manager
Open the Rom Manager app.
Touch "Fix Permissions"
Re-boot
Hopefully this works! If not, try changing density to 240 (instead of 160) as many advise this is better. However a 240 density, makes display larger, while 160 is very much similar to what you now have.
(based on this thread: http://forum.xda-developers.com/showthread.php?t=1344334)
Click to expand...
Click to collapse
I have tried this already.When I try to save the build.prop it has an error, and says unable to save.But when I reboot and go back to build.prop its changed to 240.. go figure.I also tried the market thing by clearing cache and force stop.Also tried ROM manager and fixing the permissions.Still nodda.I guess I can try a diff build.Any suggestions? Wanna do it the SD way.Im kinda new to the phone stuff.So easier is better for me atm.
First of all, the guideline works on SD ROM installation. I never tried NAND cause I need to have dual boot option
As for the "File not saved" warning, before editing the boot.prop remember to change permissions (you've missed a step)! After all changes are done, save and close. Then restore permissions...
Sent from my HTC HD2 using XDA App
Sysifos said:
First of all, the guideline works on SD ROM installation. I never tried NAND cause I need to have dual boot option
As for the "File not saved" warning, before editing the boot.prop remember to change permissions (you've missed a step)! After all changes are done, save and close. Then restore permissions...
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Thats probally my issue, the other tut like this i used didnt have the change permission thing.How do I change permission on such file?
After changing density to 160, you also have to change the phone model infos (search for adjusting build.prop to htc vision, but I'm not sure of this can be done in SD builds.
Also, you have to (after changing density) reboot and then force srop market and clear market data and cache.
Altogether, this should do it.
Edit: to be able to rewrite build.prop, get ES task explorer (it's free) and you have settings there, at their bottom is make system writable. Check that.
When I long click build.prop.. theres no option to change permissions.
x_Jack_x said:
When I long click build.prop.. theres no option to change permissions.
Click to expand...
Click to collapse
What file manager do u use?
I use 'File Expert' as file manager and by long press on the file, a pop-up menu appears. It has 'Permissions' at the mid-lower part of the menu. Open it and just enable all-you will fix permissioms at the end..
I don't know how other file managers handle this, but I'm sure they do it somehow!
Sent from my HTC HD2 using XDA App
matoflash said:
After changing density to 160, you also have to change the phone model infos (search for adjusting build.prop to htc vision, but I'm not sure of this can be done in SD builds.
Also, you have to (after changing density) reboot and then force srop market and clear market data and cache.
Altogether, this should do it.
Edit: to be able to rewrite build.prop, get ES task explorer (it's free) and you have settings there, at their bottom is make system writable. Check that.
Click to expand...
Click to collapse
I never changed model infos and works properly.. Can be done on SD builds though.
Sent from my HTC HD2 using XDA App
i use es file explorer.
x_Jack_x said:
i use es file explorer.
Click to expand...
Click to collapse
Go to settings, check root explorer and then check mount system as writable.
Save, reboot, and you should be there. It might ask for superuser permission, which you allow.
matoflash said:
Go to settings, check root explorer and then check mount system as writable.
Save, reboot, and you should be there. It might ask for superuser permission, which you allow.
Click to expand...
Click to collapse
On my es explorer, there is no setting that i can find.
x_Jack_x said:
On my es explorer, there is no setting that i can find.
Click to expand...
Click to collapse
When I click the middle, windows button on my HD2 when in ES explorer, it brings up menu and there is settings right there...
matoflash said:
When I click the middle, windows button on my HD2 when in ES explorer, it brings up menu and there is settings right there...
Click to expand...
Click to collapse
Well, it let me save the build.prop now.. did everything else. Still same error.
x_Jack_x said:
Well, it let me save the build.prop now.. did everything else. Still same error.
Click to expand...
Click to collapse
Here's how my part of my build.prop looks, maybe it will help, you should change it exactly to these:
ro.product.model=HTC Vision
ro.product.brand=tmobile
ro.product.name=vision
ro.product.device=vision
ro.product.board=vision
(then few lines lower)
ro.product.manufacturer=HTC
(Few more lines lower)
ro.build.product=vision
Plus of course the density to 160.
Save, reboot, clear market data and cache.
I have just checked my market and for me words with friends free is available for download.
So if THIS doesn't work, I give up.
matoflash said:
Here's how my part of my build.prop looks, maybe it will help, you should change it exactly to these:
ro.product.model=HTC Vision
ro.product.brand=tmobile
ro.product.name=vision
ro.product.device=vision
ro.product.board=vision
(then few lines lower)
ro.product.manufacturer=HTC
(Few more lines lower)
ro.build.product=vision
Plus of course the density to 160.
Save, reboot, clear market data and cache.
I have just checked my market and for me words with friends free is available for download.
So if THIS doesn't work, I give up.
Click to expand...
Click to collapse
That would be cool except I havd an HD2 not vision.And the board is leo not vision.Im not a phone DEV person, but somehow that doesnt look correct to me.If I changed my build.prop for htc hd leo to htc vision, it might corrupt my build.Maybe Im wrong, but I got this build out of the HTC HD2 leo android forums.

Gallery APK

hello forum
can any1 provide me with the official android gallery apk version 4.2.2 it suddenly stopped working and i deleted it by mistake now when i try to open it it says this application is not installed
my s4 GT-I9505 is rooted...
thanks
can some1 plz help?...its not hard u can use titanium backup.....i think
xweel said:
can some1 plz help?...its not hard u can use titanium backup.....i think
Click to expand...
Click to collapse
Hi,
Look HERE
malybru said:
Hi,
Look HERE
Click to expand...
Click to collapse
this doesnt work....it requires the app to be installed
first it asks me if i want to update the existing built in app, no other option but to choose install then i get the message " app not installed "
thanks
xweel said:
this doesnt work....it requires the app to be installed
first it asks me if i want to update the existing built in app, no other option but to choose install then i get the message " app not installed "
thanks
Click to expand...
Click to collapse
with root explorer move this app to system/app, then fix permission to 744, reboot
xweel said:
this doesnt work....it requires the app to be installed
first it asks me if i want to update the existing built in app, no other option but to choose install then i get the message " app not installed "
thanks
Click to expand...
Click to collapse
Hi,
Go to the market and get "FX File Explorer" + root
Navigate to system/app
Unlock the padlock at the top of the page.
Paste the Gallery app into the folder.
Save.
Reboot
malybru said:
Hi,
Go to the market and get "FX File Explorer" + root
Navigate to system/app
Unlock the padlock at the top of the page.
Paste the Gallery app into the folder.
Save.
Reboot
Click to expand...
Click to collapse
samersh72 said:
with root explorer move this app to system/app, then fix permission to 744, reboot
Click to expand...
Click to collapse
weird, the app was already in that folder.....i still moved the downloaded one though its the same, and i changed permission to 744, nothing changed....btw reboot as in restart?...
edit: now i cant see the gallery icon in the app drawer...
xweel said:
weird, the app was already in that folder.....i still moved the downloaded one though its the same, and i changed permission to 744, nothing changed....btw reboot as in restart?...
Click to expand...
Click to collapse
you ment that it is not deleted!
reboot=restart
samersh72 said:
you ment that it is not deleted!
reboot=restart
Click to expand...
Click to collapse
i thought it was deleted...the icon was in the app drawer...when i tried opening i get the message application is not installed, this happened after i cleared date from the application manager which i forgot to mention or thought it wasnt important..was it important ^^?
thanks
edit: maybe i should delete the .odex file? ..
i think a titanium back file will work...no1 can provide ??....or it wont work.....?
xweel said:
i thought it was deleted...the icon was in the app drawer...when i tried opening i get the message application is not installed, this happened after i cleared date from the application manager which i forgot to mention or thought it wasnt important..was it important ^^?
thanks
edit: maybe i should delete the .odex file? ..
i think a titanium back file will work...no1 can provide ??....or it wont work.....?
Click to expand...
Click to collapse
hey just root your phone with cf root download rootbrowser and replace the downloaded version with the one in system/app
then reboot
Hi guys!
I'm bumping an ancient thread here, hope that's okay with you.
I have this old S4+ lying around. I love it's Gallery app due to the built-in possibility to losslessly trim MPEG-4 AVC (H.264) videos by cutting to nearest keyframe, and also lossless rotation by changing the rotation metadata flag of the MP4 file in question. This simple feature is not implemented in "modern" Gallery apps, or well at least not in the OnePlus 5T I'm using today. So, I was thinking I could extract the .APK from my S4+ (running Android 5.x) and put it in my OP5T (running Android 8.x) without too much headache. Guess if I was wrong.
I get the error about that app was not installed. After browsing around on e.g. ApkMirror, I ultimately found a Samsung Galaxy derived Gallery .APK that I could install, it was a very early version (v1.x.something) which has the cutting feature, but not the rotation (flag changing) feature. So, this ancient Gallery3D .apk installed well, but not the one on my own Galaxy S4+.
So, what could be my issue? Is the .APK flagged to be installed as a system app, and due to my OP5T not being rooted I don't have access too /system/app/, therefor the error? Could it be that simple? If so, is it possible the modify the .APK to install as in /data/app/ instead? Of course I'd resign the APK with some dummy/androiddebug signature afterwards to make installation possible.
Could it be some silly (not really needed) demand listed in the AndroidManifest.xml of the APK in question? If so, is it possible to replace the AndroidManifest.xml with a very "basic" one listing more or less no demands, and re-wrap everything with new signature?
I'm really investigating all my options __except__ for having to root my OnePlus!
I figured that I could get a more specific error message from ADB than by just trying to install the .APK through the phone interface.
So, here goes..
Code:
C:\>adb.exe install F:\Galleri_com.sec.android.gallery3d.apk
adb: failed to install F:\Galleri_com.sec.android.gallery3d.apk: Failure [INSTALL_FAILED_INVALID_APK: Package couldn't be installed in /data/app/com.sec.android.gallery3d-RAEW5FZ4VBWqTWXx48LPmQ==: Package /data/app/com.sec.android.gallery3d-RAEW5FZ4VBWqTWXx48LPmQ==/base.apk code is missing]
What does this tell me?
gewone said:
What does this tell me?
Click to expand...
Click to collapse
The Galaxy S4 and most Samsung devices has a second framework app, twframework-res.apk, that only works with their apps. Here's the fun part: the existing Android framework-res.apk is modified by Samsung so both framework apps are required by a given Samsung app to function. Even better is that you cannot simply port the app and twframework-res.apk to a totally different device and expect it to function. You'd have to port the framework-res.apk as well, and with that apk being a system file, you'd soft brick your device after copying it and rebooting.
The tl;dr here? What you're attempting won't work due to Samsung modifications to Android.

[MOD] Add top number row to Swype

Hello guys,
Since I use a Samsung device, I'm used to the extra number row on top of the keyboard so I modded Swype to have that extra row. However since Swype is to be purchased and not distributed, I'll only tell here how to do it for your legally purchased copy. And this is a bit complicated and for advanced users and you need to be rooted. You also need Root Explorer. Here we go:
1- First buy/download Swype from Google Play.
2- Go to /mnt/asec/com.nuance.swype.dtc-1 folder, copy pkg.apk to your sdcard, rename it to com.nuance.swype.dtc-1.apk.(keep a backup of this file at all times)
3- Go to /mnt/asec/com.nuance.swype.dtc-1/lib folder copy the files (libnmsp_speex.so and libswypecore.so) to your sdcard.
4- Using apktool (I used version 1.52) decompile com.nuance.swype.dtc-1.apk.,
5- Go to decompiled folder\res\xml folder. kbd file pertaining to your language is to be edited, I edit kbd_qwerty.xml for English using Notepad++.
6- Check the attached kbd_qwerty.xml in portrait folder and notice the extra row section I added to the top. You can in fact add secondary characters to numbers or customize the keyboard completely, rearrange letters, add symbols etc.
7- Once done, save the file and go to decompiled folder\res\xml-land folder and edit the landscape for the layout, kbd_qwerty.xml file, notice the attached file in landscape folder.
8- Once done, save the file and go to decompiled folder\res\values folder and edit the dimens.xml file. Here I raise the height of the keyboard and height of the key to 270dip and 54dip respectively, check the top rows of the attached dimens.xml. Also increase the keyboard height for landscape (if you want) by changing the dimens.xml under res\values-land folder.
9- Once done, recompile the folder with apktool, go to decompiled folder\dist folder and copy the apk here to a different folder and rename it to temp.apk.zip
10- Open temp.apk.zip with 7z/winrar and copy the resources.arsc and kbd_qwerty.xml files from res\xml and res\xml-land folders to your PC(obviously keep the 2 files in seperate folders not to overwrite)
11- Then, rename the original apk from step 2 to com.nuance.swype.dtc-1.apk.zip , open with winrar and first delete resources.arsc file, then drag the resources.arsc file from step 10 to the archive, it will be added. Staying in winrar, go to res\xml folder and replace the file with kbd_qwerty.xml from step 10 (the portrait version). Do the same with res\xml-land folder and the landcape file.
12- Once finished rename the file back to com.nuance.swype.dtc-1.apk, don't sign it, don't delete META-INF folder, leave it as it is.
13- Now, on your phone, uninstall Swype. Reinstall it from the apk file on Step 2. Go to /data/app-lib/com.nuance.swype.dtc-1 folder and move the 2 files (libnmsp_speex.so and libswypecore.so) to system/lib folder. You have to mount the System R/W from Root Explorer on this step. Fix the permissions so these 2 files have the same permissions with other files there. If you can't find these files just use the ones from Step 3.
14- Once done, copy com.nuance.swype.dtc-1.apk from Step 12 to /system/app and fix the permissions so that it has the same permissions as other files there.
15- Then delete the com.nuance.swype.dtc-1.apk from /data/app/ folder. Restart your phone.
This should be it if you followed it exactly, tracing and Dragon voice dictation also works. While you're doing all this work (takes 10 minutes by the way), you might also consider changing how Swype looks (theming) and changing many other things like swype thickness, colors etc. Please note that this is for advanced and rooted users and please don't ask me to give you the modded apk, you have to do it on your legally bought version. You might consider doing backups just in case anything goes wrong. Have fun.
And a quick tip: if you swype from swype icon to symbol key(123), arrow keyboard opens up.
You can also add arrow keys by copying arrow keys from kbd_edit.xml, check the 2nd screenshot.
Please hit the thanks button if you think this is useful.
Nice how to. But may u should tell that the latest Android versions store purchased apps in data/app-asec as asec version, this need special procedure to get a apk from the asec format.
Can you please update this tutorial to 4.3 ? I couldn't find the files in the mentioned paths. . I'm on stock rooted 4.3 on gt9500
Sent from my GT-I9500 using XDA Premium 4 mobile app
lesalloum said:
Can you please update this tutorial to 4.3 ? I couldn't find the files in the mentioned paths. . I'm on stock rooted 4.3 on gt9500
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It works same for me on 4.3 stock rooted i9500, maybe you could do a file search to find the necessary folder. Here is another screenshot with the updated Swype(1.6.2.22328), where I made number buttons smaller like original Samsung Keyboard and hide the suggestions bar to save space.
ozkaya said:
Hello guys...
9- Once done, recompile the folder with apktool, go to decompiled folder\dist folder and copy the apk here to a different folder and rename it to temp.apk.zip
....
Click to expand...
Click to collapse
using the current play store version (1.6.3.22544), i decompiled com.nuance.swype.dtc-1.apk (/mnt/asec/com.nuance.swype.dtc-1/pkg.apk) using APKTool 1.52. i made no changes and attempted to recompile without success.
the first error displayed by apktool is:
"C:\Users\Phil\apktool\com.nuance.swype.dtc-1\res\values\arrays.xml:545: error: Found tag dimen-array where item is expected"
i do use APKTool successfully to mod other apps so i am familiar with the process.
QUESTION: what frameworks file are you using when making your mods? are you using a TW ROM frameworks? that's the only other variable i can think of...
EDIT: well, i just tried using TW framework too without success
PhilDX said:
using the current play store version (1.6.3.22544), i decompiled com.nuance.swype.dtc-1.apk (/mnt/asec/com.nuance.swype.dtc-1/pkg.apk) using APKTool 1.52. i made no changes and attempted to recompile without success.
the first error displayed by apktool is:
"C:\Users\Phil\apktool\com.nuance.swype.dtc-1\res\values\arrays.xml:545: error: Found tag dimen-array where item is expected"
i do use APKTool successfully to mod other apps so i am familiar with the process.
QUESTION: what frameworks file are you using when making your mods? are you using a TW ROM frameworks? that's the only other variable i can think of...
EXIT: well, i just tried using TW framework too without success
Click to expand...
Click to collapse
Latest version of Swype has incompatible tags with Apktool. What you do is go to all the lines that give error and change them to <string-array>. Then it compiles.
ozkaya said:
Latest version of Skype has incompatible tags with Apktool. What you do is go to all the lines that give error and change them to <string-array>. Then it compiles.
Click to expand...
Click to collapse
i'll give this a shot tomorrow, thanks a lot!
ozkaya said:
Latest version of Swype has incompatible tags with Apktool. What you do is go to all the lines that give error and change them to <string-array>. Then it compiles.
Click to expand...
Click to collapse
it works!!!
thanks man, appreciate the help and info!
I've been going nuts trying to edit swype for a week now and still can't seem to get it to work. All I want to do is change the suggested word color and maybe a few other minor color related things. I assumed just changing the color codes in /res/values/styles.xml that seemed to pertain to the holo theme would work but I can't ever get the app to install. Not even sure where to begin to ask for help on this one but if anyone has any advice I'd greatly appreciate it.
Ok I've tried this a hundred times following all the steps completely and it just wont work.
Once I go to install the final apk it always tries to install then sais App Not Installed.
TeknoGodz said:
Ok I've tried this a hundred times following all the steps completely and it just wont work.
Once I go to install the final apk it always tries to install then sais App Not Installed.
Click to expand...
Click to collapse
You don't install the final apk, in fact you can't since the certificate is no longer valid. You copy the final apk in place as in Step 14.
I would love this! I have used Swype for years but I would love a number row. To be honest I have no idea how to follow those instructions! I have a rooted phone - what can I do?
Am I right in concluding that you can't use TB to backup and restore the finished product and this will have to be done manually? I did this on my rooted Note 3 and I keep going back to my stock image because I don't want to have to keep doing the steps when I flash a new ROM or ROM update.
Would I maybe just have to do steps 12 onward every time?
mr.BeBoT said:
Am I right in concluding that you can't use TB to backup and restore the finished product and this will have to be done manually? I did this on my rooted Note 3 and I keep going back to my stock image because I don't want to have to keep doing the steps when I flash a new ROM or ROM update.
Would I maybe just have to do steps 12 onward every time?
Click to expand...
Click to collapse
When you install a new ROM, you install original Swype from apk file then you move the lib files to /system/lib, copy the modded apk to /system/app and delete original apk from /data/app folder. So it is 4 steps once you have the modded apk ready, should take no more than 5 minutes.
thumm138 said:
I've been going nuts trying to edit swype for a week now and still can't seem to get it to work. All I want to do is change the suggested word color and maybe a few other minor color related things. I assumed just changing the color codes in /res/values/styles.xml that seemed to pertain to the holo theme would work but I can't ever get the app to install. Not even sure where to begin to ask for help on this one but if anyone has any advice I'd greatly appreciate it.
Click to expand...
Click to collapse
This is similar. Please go through the steps, you don't (can't) install the modded apk, you move it in place.
ozkaya said:
This is similar. Please go through the steps, you don't (can't) install the modded apk, you move it in place.
Click to expand...
Click to collapse
Yeah I realized that after I posted and still nothing. I'm no programmer but I've never NOT been able to change a few things and recompile. Not sure how just changing a few color codes is causing such a problem. Shame such a nice keyboard has such little customization and few themes. Don't get me wrong I like orange but it really doesn't mesh at all with the rest of the UI. Thanks for the reply though.
ozkaya said:
This is similar. Please go through the steps, you don't (can't) install the modded apk, you move it in place.
Click to expand...
Click to collapse
I did all that and it changed the height of the keyboard, but didn't add any additional number row.
kdb_qwerty or whatever it's called is the default that comes up when you install it, right? Becuase I tried again and specifically made sure to use this one and it just wont give me the extra row, just the height.
TeknoGodz said:
I did all that and it changed the height of the keyboard, but didn't add any additional number row.
kdb_qwerty or whatever it's called is the default that comes up when you install it, right? Becuase I tried again and specifically made sure to use this one and it just wont give me the extra row, just the height.
Click to expand...
Click to collapse
It depends on your system language. Try kbd_qwerty_panlatin.xml.
ozkaya said:
Latest version of Swype has incompatible tags with Apktool. What you do is go to all the lines that give error and change them to <string-array>. Then it compiles.
Click to expand...
Click to collapse
Thank you for this change, this is exactly what I was looking for to compile.
Once again my Swype is blue!!! :victory:
here's my creation, what do you guys think?
the theme is "Lucid" from the pay store: https://play.google.com/store/apps/...lucid&pcampaignid=APPU_8szYUoedK9PNsAThnoDQDQ

[Q] Can't save build.prop edits - Rooted MF3

Hi, first time poster here. I can usually find what I need, but I'm stumped here.
I'm running a rooted Galaxy S4 on ATT with the i337ucuamf3 build.
I've successfully installed viper4android, but it only works on and off, with Google Music.
I'm pretty sure the fix for this is to change the build.prop lines: Ipa.decode, tunnel.decode and Ipa.use-stagefright.
I've tried everything that I can think of, but I no matter how I make the changes, they will not save. I've tried mounting System R/W in Rom Toolbox, and booting into System R/W. I've made the changes with Rom Toolbox Pro and ES File Manager. Nothing works.
Can anybody tell me if I just can't make these changes to build.prop because of the build I'm running?
Please, any help would be appreciated. When viper does work, it's incredible!
Thanks.
synesthesiac said:
Hi, first time poster here. I can usually find what I need, but I'm stumped here.
I'm running a rooted Galaxy S4 on ATT with the i337ucuamf3 build.
I've successfully installed viper4android, but it only works on and off, with Google Music.
I'm pretty sure the fix for this is to change the build.prop lines: Ipa.decode, tunnel.decode and Ipa.use-stagefright.
I've tried everything that I can think of, but I no matter how I make the changes, they will not save. I've tried mounting System R/W in Rom Toolbox, and booting into System R/W. I've made the changes with Rom Toolbox Pro and ES File Manager. Nothing works.
Can anybody tell me if I just can't make these changes to build.prop because of the build I'm running?
Please, any help would be appreciated. When viper does work, it's incredible!
Thanks.
Click to expand...
Click to collapse
Hello,
I was trying to edit the build prop file using the ES Explorer, but the same happened to me, I could edit the file by downloading the "build prop editor" from play store.
Edit the file by pressing the button in shape of a pencil and later press the save button. If you only search for the line you want to edit in the main screen of the app you will be able to modify the line but the changes are not saved.
Thanks/rate
synesthesiac said:
Hi, first time poster here. I can usually find what I need, but I'm stumped here.
I'm running a rooted Galaxy S4 on ATT with the i337ucuamf3 build.
I've successfully installed viper4android, but it only works on and off, with Google Music.
I'm pretty sure the fix for this is to change the build.prop lines: Ipa.decode, tunnel.decode and Ipa.use-stagefright.
I've tried everything that I can think of, but I no matter how I make the changes, they will not save. I've tried mounting System R/W in Rom Toolbox, and booting into System R/W. I've made the changes with Rom Toolbox Pro and ES File Manager. Nothing works.
Can anybody tell me if I just can't make these changes to build.prop because of the build I'm running?
Please, any help would be appreciated. When viper does work, it's incredible!
Thanks.
Click to expand...
Click to collapse
Never mind.
ES File doesn't always save, you'll just have to try a different app. Root explorer should work or fx file manager.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

[HOWTO] Enable Auto Rotation for Lock Screen & Launcher

This is a quick walk through for editing the build.prop to allow lock screen and launcher rotation.​
I got tired of looking at my phone sideways while it was propped up landscape wise, in my case.
1. Locate "build.prop" in /system using your favorite file explore
2. Open it up and at the bottom add the lines
Code:
log.tag.launcher_force_rotate=VERBOSE
lockscreen.rot_override=true
3. Save your edit and reboot.
Lockscreen rotation still not working for you???
A few users have reported that adding a blank line between the two, fixes this issue.
Once the phone reboots your lockscreen and Google Now launcher will rotate with the orientation of the device just like other apps do.
To undo this, simply remove the lines we added
:good:
Update: 11/10/2015
enigma9o7 Has figured out how to get this to stick even after an update! Head over to his post for the walkthrough and install guide!! Remember to give them a "thanks" for sharing the work!
Awesome I been wondering how to get this done.
Nice tip. I've always just used an app called Ultimate Rotation Control. Seems to work just fine on the Nexus 6. A quick build.prop tweak removes the need for a separate app for it, though. I might get around to trying this...eventually
can someone make a flash able zip for this please ?
thanks in advance
Anybody know how one would do this with adb?
N6
I used an app for quite some time but i disliked it running in the background.
Im not able to make a flashable zip. Maybe in time I will see if i can.
For adb, youd have to pull the build.prop, edit on computer then push it back. The instructions to do that are unclear to me
mrfuzzie23 said:
can someone make a flash able zip for this please ?
thanks in advance
Click to expand...
Click to collapse
You can install Nova Launcher and toggle the setting in there, or use the ultimate rotation app someone else mentioned.
Thx
If you set the DPI to 384 or less, this happens by default.
pavankp said:
If you set the DPI to 384 or less, this happens by default.
Click to expand...
Click to collapse
Thats good to know! Not surprising, the device is most likely changed to "tablet size" to the system. And they have full rotation.
Works great, thanks! (AT&T Nexus 6)
Would not work for me I get error saving
techrider6262 said:
Would not work for me I get error saving
Click to expand...
Click to collapse
Thats not good. What error are you getting?
eqbirvin said:
Thats not good. What error are you getting?
Click to expand...
Click to collapse
It just said error can't save and I tried a couple different time
techrider6262 said:
It just said error can't save and I tried a couple different time
Click to expand...
Click to collapse
gotcha. You are rooted, correct? and if so what file manager are you using to locate the build.prop?
es file explorer and i'm rooted.
in ES file explorer when you grant it root permissions, click on root, then mount R/W, make sure "/system" is RW instead of RO. (sorry if you already know this, im just trying to save time and figure your error out haha)
Thanks I got it working.:good:
Glad to hear it!
to each their own, I like being able to get OTAs so I'll stick with Ultimate Rotation Control

Categories

Resources