The gingerbread keyboard was stripped from Vegan and TNT lite for stability issues ( i think ) - but I never ran into a problem with it... I've been missing it so I decided to pop the lib and apk into my system and, so far, it has worked without a hitch.
So for those of you who prefer to have the gingerbread keyboard (sound on key press actually works), here is how:
1) use root explorer (or the equivalent) to mount certain folders as R/W
2) backup libjni_latinime.so in the system/lib/ folder (just in case) and copy the new libjni_latinime.so file from the zip attached.
3) backup LatinIME.apk found in system/app/ folder and copy the new LatinIME.apk from the zip.
4) change the permissions on LatinIME.apk as rwxrwxr-- (not sure if this is needed, but was needed when using other IME input methods, like wiimote) and reboot the tablet.
The gingerbread keyboard should be fully functional now! Don't get nervous if it takes a little to open the keyboard settings for the first time (or switch input from TNT stock to android keyboard) as it took 15 seconds for me the first time but pops up right away after that.
Enjoy!
Check to see if you have a problem while having voice search installed. I think I had FC only with the GB keyboard and voice search both being installed.
Moved to applications
theimpaler747 said:
Moved to applications
Click to expand...
Click to collapse
Oops! And voice search works without a hitch
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
TheTruth said:
The gingerbread keyboard was stripped from Vegan and TNT lite for stability issues ( i think ) - but I never ran into a problem with it... I've been missing it so I decided to pop the lib and apk into my system and, so far, it has worked without a hitch.
So for those of you who prefer to have the gingerbread keyboard (sound on key press actually works), here is how:
1) use root explorer (or the equivalent) to mount certain folders as R/W
2) backup libjni_latinime.so in the system/lib/ folder (just in case) and copy the new libjni_latinime.so file from the zip attached.
3) backup LatinIME.apk found in system/app/ folder and copy the new LatinIME.apk from the zip.
4) change the permissions on LatinIME.apk as rwxrwxr-- (not sure if this is needed, but was needed when using other IME input methods, like wiimote) and reboot the tablet.
The gingerbread keyboard should be fully functional now! Don't get nervous if it takes a little to open the keyboard settings for the first time (or switch input from TNT stock to android keyboard) as it took 15 seconds for me the first time but pops up right away after that.
Enjoy!
Click to expand...
Click to collapse
No joy yet running the GB keyboard on TnT Lite 3.1.4.
I noticed that I didn't have a LatinIME.apk file in the /system/apps directory. Also, I noticed the timestamp of the libjni_latinime.so file is back from 2008. Are you sure you included the correct version of the shared library file?
I also tried changing the permissions of the libjni_latinime.so file to match the other shared library files in the directory. and I tried it using the original libjni_latinime.so file.
Was anyone else successful installing the GB keyboard on TnT Lite 3.1.4?
Just tried it but no luck
Edit: Went back and changed the permissions and it works perfectly now
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
I like the larger buttons on the keyboard thwt comrs with vegan so is there any way to use this library with that keyboard? Just tried to replace the existing library and got force closes
Edit: or if someone can make this keyboard larger then I would love it
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
Butch1326 said:
No joy yet running the GB keyboard on TnT Lite 3.1.4.
I noticed that I didn't have a LatinIME.apk file in the /system/apps directory. Also, I noticed the timestamp of the libjni_latinime.so file is back from 2008. Are you sure you included the correct version of the shared library file?
I also tried changing the permissions of the libjni_latinime.so file to match the other shared library files in the directory. and I tried it using the original libjni_latinime.so file.
Was anyone else successful installing the GB keyboard on TnT Lite 3.1.4?
Click to expand...
Click to collapse
I zipped this up using 7zip and pulled the apk and lib files straight from a system running the gb keyboard... I've used it in latest tnt and vegan roms without a hitch... are you getting FCs nonstop? Did you change the input method to android keyboard?
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
Tried this method with no luck, and now trying to restore the original APK and Lib fail. Any suggestions?
i can't get it to work
any tweak?
blakestimac said:
Tried this method with no luck, and now trying to restore the original APK and Lib fail. Any suggestions?
Click to expand...
Click to collapse
Simply removing the supplied apk and .so then replacing the original apk and lib files will do the trick, with a reboot after the changes to the system have been made.
I have tried this with both roms and also two "generations" gtabs (initial 1000 production run and post mass production run) with success. I am unsure as to why this is hit or miss with some folks. Of course a logcat of your system while trying to use this would help...
I think I will just make a flashable zip file to be used in CWM.
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
Related
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
OK.. so I want to change the keyboard colors on my phone and I've been reading for a while on apk files and just want to make sure I have it right
I took the original swype apk (after backing up a copy) and changed it to a zip file and unzipped. Went into where the keyboard png files live and changed the color of the text to my liking.
I took the original backed up swype.apk and used the apk package manager to decompress it (files were in projects folder). I copied over my keyboard pngs over the originals and then use apk manager to package it back up I'm pretty sure but
1. Is swype a system app?? Apk manager warns about keeping the signature or not
2. Does my new swype apk have to have the same name?? I now have a unsignedswype.apk file in my "place-apk-here-for modding" folder probably because I chose that
Was planning on using sideload wonder machine to put it on the phone, just wanted to make sure I had everything correct before screwing something up royally
I've played around a bit with Swype themes. MetaMorph is an easy way to apply your theme. I've also had no problems with copying my Swype.apk from /system/App, opening it with Astro, deleting the files I changed, and pasting in the replacements. Then I just overwrite the original apk with mine using Root Explorer.
Let me know if you need any more help, can also show you how to hex edit the lib to change the trail color (mine is green).
Sent from my SGH-I897 using XDA App
Hi there, I would have posted in the captivate android dev darky's thread but apparently I need 10 posts for that or something stupid.
I was on Darky's 9.2 and was all working well and then swype told me the license had expired so I thought I may as well update to 9.3 because I thought that might fix my swype. Updated to that and selected the swype option in the darky app etc and that didn't seem to work, swype still says I need a new license. I signed up for the swype beta and downloaded that but in order to install the new swype I have to uninstall my current version. How do I go about doing this? If I go settings/manage apps/all/swype the uninstall option is greyed out. How do I uninstall it?
Thanks
Use titanium backup
CM7
mcord11758 said:
Use titanium backup
CM7
Click to expand...
Click to collapse
?
I backed up my old swype from when I was using cognition and just tried to restore that but it said swype crashed.
I meant delete current version then sign up for beta and dl
CM7
Oh I see, didn't see the uninstall but. Cool thanks will try that now.
I now go through all the steps in the swype installer and at the end it says application not installed.
Did you try both dl versions?
CM7
You mean full and english/spanish? Yup.
I found this:
http://samsunggalaxysforums.com/showthread.php/3922-Application-Not-Installed-Have-lost-Swype
Ok first things first;
1: Your Rooted and have a Root file explorer
2: You have 2 files that you downloaded, Swype.apk and libSwypeCore.so
Remove original swype.apk from /system/app then remove the libSwypeCore.so from /system/lib.
Restart phone
Now add your new swype.apk to /system/app and the libSwypeCore.so to /system/lib
and restart just to make sure
Click to expand...
Click to collapse
I tried deleting libSwypeCore.so through root explorer but it said read only, how do I delete this?
Top there I'd a button in root explorer r/o or r/w. Click it, try again
CM7
Okay, I deleted that file and it still didn't work so I restarted my phone and it installed and now works perfectly. Thanks
Glad it worked
CM7
They need to put their app in the market like everyone else. It's rather ridiculous.
MikeyMike01 said:
They need to put their app in the market like everyone else. It's rather ridiculous.
Click to expand...
Click to collapse
+1 enough already
CM7
Arabic Swype on Captivate!
I've actually encountered several woes when it comes to Swype on my Captivate but using Darky's ROM is still worth it in my opinion!
What adds to my troubles is the fact that I use Arabic on my Swype keyboard so the BETA by itself is no good.
However for those in my situation the solution goes something along the lines of:
1- Remove anything Swype related on your phone (Swype.apk/Swype Installer/LibSwypeCore.So) so you can have a fresh start with this.
LibSwypeCore.so is found in /system/lib/
2- Sign up and install the Swype BETA
3- After installing the BETA go to : /data/data/com.swype.android.inputmethod/swypedata/
4- Make a copy of "license.dat" file.
This is essential as without it you will most likely receive "This package of Swype is configured for another device" error.
5- Place the copy somewhere convenient like /mnt/sdcard for example.
6- Uninstall the Swype BETA,Swype Installer and delete the LibSwypeCore.So
7- Get the Swype.apk & LibSwypeCore.So that comes with Darky 9.3
8- Place the Darky LibSwypeCore.so in /system/lib
The rest of the guide is dedicated to adding arabic to the Swype package
9- First get a hold of a swype package that already has Arabic on it (Dr.Akrim Gingerblue ROM for example)
10- Rename the Darky Swype.apk to SwypeD.zip
11- Rename the Arabic Swype.apk to SwypeA.zip and extract its contents
12- Go to the extracted folder then navigate to \assets\files
13- Search for and select all files containing Arabic
14- Copy the selected files and paste them into SwypeD.zip\assets\files
Note: Do NOT extract the SwypeD.zip as repacking it would require signing which is a hassle I like to avoid.
15- Now go to \assets\keyboards in the SwypeA extracted folder
16- Search for and select all files containing Arabic
17- Copy the selected files and paste them into SwypeD.zip\assets\keyboards
18- Lastly, go to SwypeD.zip\assets\files\languages.lst and open the file in notepad.
19- add Arabic to the language list so it should look something like:
"Arabic,EnglishUS,Russian,Hebrew,EnglishUK"
20- Repeat the above process to helplanguages.lst
21- Rename SwypeD.zip back to SwypeD.apk or whatever you like (Swype.apk)
22- Place this newly modified apk in /system/app
23- Enjoy
EDIT: IF The method above does not work there is an alternative method of simply changing your Model Number (via editting the build.prop file found in /system/ and replace any mentions of "SGH-i897" with "GT-I9000"
This will allow you to use any Swype package that provides arabic with no problems.
MikeyMike01 said:
They need to put their app in the market like everyone else. It's rather ridiculous.
Click to expand...
Click to collapse
u get this working on ur rom? Every theme I try wrecks my swype
Hi all,
I recently installed AOKP ICS Milestone 5 onto my Samsung Galaxy S I9000, but one of the things i hate is the stock keyboard, the keys are too small and i end up hitting the wrong letters.
So i decided to try and install HTC_IME keyboard with Clicker_hi, the problem with this is that it forced closed everytime i selected a word.
I downloaded a compatible version but when i unzipped HTC_IME_hi22 there were 7 files in the folder i.e assets, lib, META-INF, res, AndroidManifest, classes,dex and resources.arsc. but what do i do with them.
I'm can't code for the life of me, can someone help me with this?
The thing you unzipped is the apk. Try if it works with putting it into /system/apps. Then give it right permissions(rw-r-r) and reboot.
dark_knight35 said:
The thing you unzipped is the apk. Try if it works with putting it into /system/apps. Then give it right permissions(rw-r-r) and reboot.
Click to expand...
Click to collapse
The 2 files i downloaded vere .Zip files and not .akps should they be installed via recovery?
any help would be great
robbiejuk08 said:
The 2 files i downloaded vere .Zip files and not .akps should they be installed via recovery?
Click to expand...
Click to collapse
But classes.dex are only in apks, not in zips. The keyboards are always apks.
--------------------------------
dark_knight35 said:
But classes.dex are only in apks, not in zips. The keyboards are always apks.
--------------------------------
Click to expand...
Click to collapse
I just discovered from another forum that renaming the files from ZIP to APK does the trick.
Decided to start a new thread as this one was getting a bit messy (and I couldn't change the title anymore)
http://forum.xda-developers.com/galaxy-s6/themes-apps/mod-multi-dpi-samsung-apps-camera-t3141148
----------------------------------------------------------
Hi all, after changing the dpi to 480 the camera was the main thing bugging me. Looking for a solution I found this thread:
http://forum.xda-developers.com/galaxy-s6/themes-apps/mod-fix-samsung-camera-app-device-dpi-t3131995
But that did not work for me, so I decided to try it myself and I finally managed to create multi-dpi versions of the Camera and Samsung Keyboard apps. They are based on the apks from the XtreStoLite Universal Deo-Mod Edition 1.5 as I'm currently running that. So just give it a try (backup the original apks first! I usually just rename them to "filename.org") and let me know if it works for you. I tested on 480 and 520 dpi and that works here...
Installation:
1. Backup original apk (in system\app\SamsungCamera4 and/or systemm\app\SamsungIMEv2 )
2. Extract modded apk to the corresponding folder
3. Wipe data for the app
4. Reboot
I basically modified the dimens.xml file to hardcoded pixel sizes instead of dip value, modifying dip value caused other issues for me (camcorder not working, pro mode messing up). Hopefully it's of use to some.
I have not been able to fix the Contacts/Dialer (SecContacts_L.apk in the priv-app folder)! I either get a corrupt apk (parsing error) or it just won't show up in my apps. Corrupted apk gives a parsing error when trying to install manually, otherwise it just says 'install failed'.
I am guessing this is somethiong with the priv-app folder and other restrictions there. I also tried copying the apk to the system\app folder instead but that didn't work either...
If anyone has ANY idea how to fix this? (I tried with both apktool as apk multitool).
*SCRIPTS ADDED*
Added the scripts and all I've written for this to this post for those wanting to try themselves (dpi_mod.zip). They are not completely polished so need some manual editing every now and then...
Basically, doubleclicking apk_process.bat in the root will go through the apk's in the apk subfolder and
1. Decompile them to the decompiled subfolder
2. Edit the dimens.xml file in the res\values subfolder of the decompiled folder replacing all the <n>dip values with <4*n>px (So 640 dip becomes 2560px for example...)
3. Rebuild the apk to the dpimod_apk subfolder (using the -c option to keep original manifest and signature files)
The files folder contains the files used (apktool, the subscripts for each step, signature files, (g)awk and an awk script to process the xml file replacing the values, etc)
There is also a script for signing the apk manually, but somehow the apk then also doesn;t work in my case it seems...
ALl scripts are windows batch files (and an awk file) as I mainly use windows at home. Shouldn't be too hard for the linux users to convert them to bash files if desired...
*EDIT2*
Added patched services.jar (and original services.jar for restoration in case of issues). Flash through twrp recovery... This allows you to use the modded SecContacts_L.apk supplied, the services.jar needs to be patched to disable the signature verification for the (system) apk files. Note that this might cause issues (an invalid services.jar caused my phone to get stuck in boot... had to restore the original to be able to continue) so use at your own risk!
Great job !
I have not been able to decompile the contacts.apk either.. I am a bit rusty tho.. will have to look into that a little more.
fOmey said:
Great job !
I have not been able to decompile the contacts.apk either.. I am a bit rusty tho.. will have to look into that a little more.
Click to expand...
Click to collapse
Thanks! And yeah, weird stuff.
I actually was only really bothered by the camera, not using the samsung keyboard at all myself and don't mind the contacts as much (perfectly usable for me) but it's now a matter of principle If you find anything out, I would love to hear.
dagrim1 said:
Thanks! And yeah, weird stuff.
I actually was only really bothered by the camera, not using the samsung keyboard at all myself and don't mind the contacts as much (perfectly usable for me) but it's now a matter of principle If you find anything out, I would love to hear.
Click to expand...
Click to collapse
But In Call screen looks weird with 480 DPI right? Would you know any fix for that? Thanks.
Sent from my SM-G925F using XDA Free mobile app
ksekhar said:
But In Call screen looks weird with 480 DPI right? Would you know any fix for that? Thanks.
Sent from my SM-G925F using XDA Free mobile app
Click to expand...
Click to collapse
Yup, it does. (But again, doesn't bother me as much as I don't look at it long because I usually hold my phone to my ear anyway ).
But yeah, I think I know where to fix it... It's the Contacts apk I mentioned above but there is an issue with decompiling/rebuilding it so can't fix it yet. Looking into it.
Did notice when decompiling and recompiling including resources it fails, when keeping resources intact it does work.
To successfully mod seccontacts you have to do these steps :
- Decompile apk
- Edit xml files in res folder
- Recompile apk
- Extract xml edited files in res folder from recompiled apk
- Paste these xml files in the original apk in the res folder with compression tool like Winrar
It works I made this with my S5.
Meh, been looking into it some more and also found this:
http://forum.xda-developers.com/android/software-hacking/how-to-recompile-tw-contacts-phone-t3066350
and
http://www.ez-pg.com/guide-how-to-decompilerecompile-lollipop-seccontacts.html
I tried modifying the manifest as instructed, but the apk still didn't work. Perhaps because signature verfication is not properly disabled on my rom. BUt if it isn't it is also not for the majority of the users in which case siumply supplying the apk wouldn't work anyway.
I also tried resigning the apk, no luck. Copying the original manifast is also not going to work afaik with a changed manifest file...
More info about signature verficiation:
http://forum.xda-developers.com/showthread.php?t=2725233
http://forum.xda-developers.com/showthread.php?t=2342262
Perhaps I will try this soon as well, but for now I think I'll leave it be...
sebdigital said:
To successfully mod seccontacts you have to do these steps :
- Decompile apk
- Edit xml files in res folder
- Recompile apk
- Extract xml edited files in res folder from recompiled apk
- Paste these xml files in the original apk in the res folder with compression tool like Winrar
It works I made this with my S5.
Click to expand...
Click to collapse
Thanks for the tip, had looked into that as well but this xml file is in the values folder which is not simply found in the res folder of the apk but compiled into the resources.arsc file in the apk so this is not working unfortunately.
dagrim1 said:
Thanks for the tip, had looked into that as well but this xml file is in the values folder which is not simply found in the res folder of the apk but compiled into the resources.arsc file in the apk so this is not working unfortunately.
Click to expand...
Click to collapse
I'm on 5.1.1 today and noticed that contacts/dialer is (almost) multi DPI already without having to do anything. And your camera mod works on 5.1.1 too!
Sent from my SM-G920F using XDA Free mobile app
can u change this Camera 480 dpi camera s6 to 420 dpi?
https://mega.nz/#!M4Ui0KoR!TKsPKkMl-XQHyiJ_DNf53eQCGZTrYWhuHaAnhAYXeSM
thanks you very much
can be used for other than s6 for SamsungCamera4. ??
my android device A8 6
dagrim1 said:
Decided to start a new thread as this one was getting a bit messy (and I couldn't change the title anymore)
http://forum.xda-developers.com/galaxy-s6/themes-apps/mod-multi-dpi-samsung-apps-camera-t3141148
----------------------------------------------------------
Hi all, after changing the dpi to 480 the camera was the main thing bugging me. Looking for a solution I found this thread:
http://forum.xda-developers.com/galaxy-s6/themes-apps/mod-fix-samsung-camera-app-device-dpi-t3131995
But that did not work for me, so I decided to try it myself and I finally managed to create multi-dpi versions of the Camera and Samsung Keyboard apps. They are based on the apks from the XtreStoLite Universal Deo-Mod Edition 1.5 as I'm currently running that. So just give it a try (backup the original apks first! I usually just rename them to "filename.org") and let me know if it works for you. I tested on 480 and 520 dpi and that works here...
Installation:
1. Backup original apk (in system\app\SamsungCamera4 and/or systemm\app\SamsungIMEv2 )
2. Extract modded apk to the corresponding folder
3. Wipe data for the app
4. Reboot
I basically modified the dimens.xml file to hardcoded pixel sizes instead of dip value, modifying dip value caused other issues for me (camcorder not working, pro mode messing up). Hopefully it's of use to some.
I have not been able to fix the Contacts/Dialer (SecContacts_L.apk in the priv-app folder)! I either get a corrupt apk (parsing error) or it just won't show up in my apps. Corrupted apk gives a parsing error when trying to install manually, otherwise it just says 'install failed'.
I am guessing this is somethiong with the priv-app folder and other restrictions there. I also tried copying the apk to the system\app folder instead but that didn't work either...
If anyone has ANY idea how to fix this? (I tried with both apktool as apk multitool).
*SCRIPTS ADDED*
Added the scripts and all I've written for this to this post for those wanting to try themselves (dpi_mod.zip). They are not completely polished so need some manual editing every now and then...
Basically, doubleclicking apk_process.bat in the root will go through the apk's in the apk subfolder and
1. Decompile them to the decompiled subfolder
2. Edit the dimens.xml file in the res\values subfolder of the decompiled folder replacing all the <n>dip values with <4*n>px (So 640 dip becomes 2560px for example...)
3. Rebuild the apk to the dpimod_apk subfolder (using the -c option to keep original manifest and signature files)
The files folder contains the files used (apktool, the subscripts for each step, signature files, (g)awk and an awk script to process the xml file replacing the values, etc)
There is also a script for signing the apk manually, but somehow the apk then also doesn;t work in my case it seems...
ALl scripts are windows batch files (and an awk file) as I mainly use windows at home. Shouldn't be too hard for the linux users to convert them to bash files if desired...
*EDIT2*
Added patched services.jar (and original services.jar for restoration in case of issues). Flash through twrp recovery... This allows you to use the modded SecContacts_L.apk supplied, the services.jar needs to be patched to disable the signature verification for the (system) apk files. Note that this might cause issues (an invalid services.jar caused my phone to get stuck in boot... had to restore the original to be able to continue) so use at your own risk!
Click to expand...
Click to collapse
how to fix on parse error, after recompile SamsungCamera4.apk with apktool
with or without edit error on parse...
My device Galaxy-A8