So I'm currently using a MMS app that is modded with emojis + other useful settings . But I was wondering if anyone could help me add the emojis from ios6 into that application. I took the emojis out of the Handcent Emoji Plugin application and I'll attach it with this post along with the MMS.apk that has the "regular" emojis that I'm using at the moment.
If not, could someone help me with editing/modding the MMS.apk so I can add them myself? I played around with APKtool and also APK manager but I'm unable to "decompile" the application
Edit: Some possibly useful or useless information-Galaxy Nexus running on a rom that is on 4.2.1 (aosp)
:fingers-crossed:
Update!
So i was able to change the public.xml file to add the ios6 emojis. But now, when I recompile the apk, theres an error. Where else should I change the code?
I would also like this
Sent from my Nexus 4 using xda premium
areole said:
Update!
So i was able to change the public.xml file to add the ios6 emojis. But now, when I recompile the apk, theres an error. Where else should I change the code?
Click to expand...
Click to collapse
What error are you getting? Are you defining images in the public XML and not adding the actual image? Anyway a log would help also it's easier to just add the images try to recompile and let the public XML build new resource ids for the new images. I have never looked into this but i would imagine you would need to add something else in styles or strings can't remember which one. Also I'm not sure how well those new icons will play with other phones it might work i just don't know.
Sent from my Galaxy Nexus using xda premium
Beamer9408 said:
What error are you getting? Are you defining images in the public XML and not adding the actual image? Anyway a log would help also it's easier to just add the images try to recompile and let the public XML build new resource ids for the new images. I have never looked into this but i would imagine you would need to add something else in styles or strings can't remember which one. Also I'm not sure how well those new icons will play with other phones it might work i just don't know.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
The error I'm getting is "public drawable symbol is not defined"
I added the actual image (.png) files to the folder where all the other drawable images were located. I believe the folder was called drawable-xhdpi (I don't have access the the computer I used to mod the mms.apk at the moment). This was the only folder were the older emojis were in. Could you explain to me the recompiling? Do I not physically edit the public.xml file, and let it update itself?
This is what I did:
1. Extracted new emoji's from handcent
2. Decompiled the mms.apk + added new emojis to drawable-xhdpi folder (I tried recompiling here but when I used the app, there were no new emojis)
3. I clicked around and opened the public.xml file and saw that there were emojis names and id codes so I manually added more coding so that the new emojis would have codes.
4. When I added id codes to all the new emojis, I noticed that the id codes doubled in some misc. picture files so I manually changed those as well so the id codes wouldn't double
5. Save and recompiled it but it wouldn't work.
The .png icons that I extracted from handcent (I believe) are the same ones in the mms.apk currently since they have the same names. So I assumed that it was okay to do, but I might be wrong.
Thank you, sorry for the trouble
Related
I am trying to use percentage icons with CM nightly build. I tried to unzip it and replace icons and xml battery files but I don't get any battery icons to show up on my status bar. I was able to make my own theme by replacing icons and image files but I wan percentage battery icons. I tryied to change xml files in CM source code and recompiled it and then I gor random icons instead of my battery icons. I also tried to replace all images but then would tell me that images are missing something and will stop compile. Could somone point me the right direction on how to mod framework-res to include percentage icons
http://forum.xda-developers.com/showthread.php?t=724778
I tried it and does not work. The kitchen does wird stuff to my framework and makes the phone reboot
tritron777 said:
I am trying to use percentage icons with CM nightly build. I tried to unzip it and replace icons and xml battery files but I don't get any battery icons to show up on my status bar. I was able to make my own theme by replacing icons and image files but I wan percentage battery icons. I tryied to change xml files in CM source code and recompiled it and then I gor random icons instead of my battery icons. I also tried to replace all images but then would tell me that images are missing something and will stop compile. Could somone point me the right direction on how to mod framework-res to include percentage icons
Click to expand...
Click to collapse
In addition to changing the XML files in the /res/drawable folder, specifically:
stat_sys_battery_charge.xml
zzz_stat_sys_battery_1.xml
stat_sys_battery.xml
And adding the new png file to /res/drawable-hdpi
You MUST make sure you add resource IDs for each of your newly added png files to the /res/values/public.xml file. Otherwise, the XML has no way of referencing the new images by ID, and the likely reason why you were getting random imagines, rather than the new ones specified.
If you are manually editing and recompiling, you can then just grab the above referenced XML files and the 'resources.arsc' file from the newly built apk file and drop them in your original.
JsChiSurf said:
In addition to changing the XML files in the /res/drawable folder, specifically:
stat_sys_battery_charge.xml
zzz_stat_sys_battery_1.xml
stat_sys_battery.xml
And adding the new png file to /res/drawable-hdpi
You MUST make sure you add resource IDs for each of your newly added png files to the /res/values/public.xml file. Otherwise, the XML has no way of referencing the new images by ID, and the likely reason why you were getting random imagines, rather than the new ones specified.
If you are manually editing and recompiling, you can then just grab the above referenced XML files and the 'resources.arsc' file from the newly built apk file and drop them in your original.
Click to expand...
Click to collapse
What's the easiest way to get the resource ID's for the new images?
HeyItsLou said:
What's the easiest way to get the resource ID's for the new images?
Click to expand...
Click to collapse
Decompile an existing super battery framwork-res and pull the IDs from it's public.xml file.
You do not need to put in the ID's. You can just edit the xml files add the pics to your hdpi folder and recompile, apkmanager will make the ID's by itself.
rujelus22 said:
You do not need to put in the ID's. You can just edit the xml files add the pics to your hdpi folder and recompile, apkmanager will make the ID's by itself.
Click to expand...
Click to collapse
I don't use apk manager but I do use apktool which apk manager uses and I can verify this to work 100%
If you open say com.htc.resources.apk with an archive manager like 7zip for windows or archive manager if you're using linux and drop in your edited png's then use apktool to decompile the framework it should create all of the resource ID's in the public.xml file for you. At this point if you have any xml edits or smali edits to do complete those then recompile. Now just extract the "res" folder and the "resources" files from the compiled apk and using the same archive manager from above to open the original com.htc.resources.apk and replace the files you should be good to go.
IS there a way to autogenerate image ids?
tritron777 said:
IS there a way to autogenerate image ids?
Click to expand...
Click to collapse
Not that I'm aware of however I'm no pro themer. As far as I know you have to manually edit the xml's in the drawable directory by creating the strings that point to the drawable hdpi images you created or it won't work.
if you use http://circle.glx.nl/ you won't need to do the manual xml updating. i use this kitchen for my cm6 nightly ROM.
extract the framework.apk file from the cm6nightly that you are using (current nightly builds have had changes to the framework...thus if you flash tonight you may need to redo the process..perhaps you can just dump the updated framework and resign the zip..i just go back to the kitchen and recook) anyway..
after extract
go to kitchen
set ur desired options
upload the framework file
wait
download the UOTxxx.zip file
put on root of evo sdcard
reboot into recovery
flash the UOT zip file
enjoy
but then, that's the automated cheater way.
I suppose if you don't know what you're doing, kitchens are great. For non noobs who don't want / need to use (the whole point of the thread as the op had problems), doing it manually makes sure it is done right without making your framework all screwy.
Sent from my HTC Evo
JsChiSurf said:
I suppose if you don't know what you're doing, kitchens are great. For non noobs who don't want / need to use (the whole point of the thread as the op had problems), doing it manually makes sure it is done right without making your framework all screwy.
Sent from my HTC Evo
Click to expand...
Click to collapse
I completely agree. I rather learn how to do something the manual way it just empowers you for any future mods you may want to do. Not to mention if you rely on one resource and all of a sudden that resource such as a kitchen goes away you're out of luck.
HeyItsLou said:
I completely agree. I rather learn how to do something the manual way it just empowers you for any future mods you may want to do. Not to mention if you rely on one resource and all of a sudden that resource such as a kitchen goes away you're out of luck.
Click to expand...
Click to collapse
Completely agree, Learning how to do something is always better.
I've just tried some of the themes available here against the apkmanager tool - decompiling and then compiling the framework-res.apk and twframework-res.apk and all of the custom themes give tons of errors (sometimes won;t even compile back) .. the only one that goes without troubles is the stock framework-res.apk and twframework-res.apk
I'm just wondering whether this is correct or not and where is the issue - is it apkmanager or the themes that are wrong ?
w83 said:
I've just tried some of the themes available here against the apkmanager tool - decompiling and then compiling the framework-res.apk and twframework-res.apk and all of the custom themes give tons of errors (sometimes won;t even compile back) .. the only one that goes without troubles is the stock framework-res.apk and twframework-res.apk
I'm just wondering whether this is correct or not and where is the issue - is it apkmanager or the themes that are wrong ?
Click to expand...
Click to collapse
I never had much luck with APKManager, that's why I use APKTool.
Try v1.3.1 if you can find it, 1.3.2 has problems.
Apk Manager uses apktool too.
@w83
Take a look at log.txt.
I guess it's due to corrupted .9.png.
Solution:
Replace all modded .9.png with original files, decompile, make your changes, compile.
Then you can put in your modded .9.pngs again...
scheichuwe said:
Apk Manager uses apktool too.
@w83
Take a look at log.txt.
I guess it's due to corrupted .9.png.
Solution:
Replace all modded .9.png with original files, decompile, make your changes, compile.
Then you can put in your modded .9.pngs again...
Click to expand...
Click to collapse
Is it really a solution ? .. cause it seems like all of the modded .9.pngs are basically broken
You're right, let's say workaround
For fixing your modded .9.png search for xUltimate draw 9 patcher. I don't know what it's called exactly.
But for editing framework-res.apk the workaround should be acceptable.
I can manage to decompile the theme (usually with some patched pngs messed up) but when I try to compile it (even without any changes) I end up with tons of errors in the form:
apktools/vagreen_frame/res/values/public.xml:3760: error: Public symbol drawable/zzzzz_tw_quickcontact_top_frame declared here is not defined.
(lots of these ones)
any idea what's wrong ?
w83 said:
I can manage to decompile the theme (usually with some patched pngs messed up) but when I try to compile it (even without any changes) I end up with tons of errors in the form:
apktools/vagreen_frame/res/values/public.xml:3760: error: Public symbol drawable/zzzzz_tw_quickcontact_top_frame declared here is not defined.
(lots of these ones)
any idea what's wrong ?
Click to expand...
Click to collapse
Once your 9.pngs are poorly done, errors such as the above would appear. There were only 6 9.png errors and the log generated a loh file size of 130+kb. But once solved, all errors were eliminated.
Sent from my GT-I9000 using XDA App
scheichuwe said:
You're right, let's say workaround
For fixing your modded .9.png search for xUltimate draw 9 patcher. I don't know what it's called exactly.
But for editing framework-res.apk the workaround should be acceptable.
Click to expand...
Click to collapse
I'm either using the android sdk draw9patch to generate the pngs or even GIMP to do it. Just make sure the first and last row/column must be either alpha or black. No other colours are allowed there.
Sent from my GT-I9000 using XDA App
g00ndu said:
I'm either using the android sdk draw9patch to generate the pngs or even GIMP to do it. Just make sure the first and last row/column must be either alpha or black. No other colours are allowed there.
Click to expand...
Click to collapse
Ok so ur saying that after I should correct the patch 9 pngs in the framework and it should compile correctly ? .. so two options: [1] decompile, replace the pngs with correct ones, compile ? .. or .. [2] correct pngs, compile in eclipse, replace in framework, decompile, compile ?
I am pretty sure that I've already tried correcting them using [1] and it didn't help at all .. I was still flooded with errors ..
I guess I'll try to modify things from the bottom up .. take the stock theme with extended menu and play around with it .. are there any significant changes in the .jars inside the /system/framework in most of current themes ?
but still it would be way nicer if I could decompile and compile one of current themes without errors .. I'm so curious how the theme gurus are doing it .. I envy their knowledge
w83 said:
...
but still it would be way nicer if I could decompile and compile one of current themes without errors .. I'm so curious how the theme gurus are doing it .. I envy their knowledge
Click to expand...
Click to collapse
Replace all modded .9.png with original files, decompile, make your changes, compile.
The person who made the theme did it lazily and incorrectly. The first couple versions of my ROM had this problem. Did some research into how .9 PNGs work.
If you want to fix them, I can tell you how. It's a bit tedious.
scheichuwe said:
Replace all modded .9.png with original files, decompile, make your changes, compile.
Click to expand...
Click to collapse
Yep that worked perfectly !! Thx mate for that
I'll try to mod something and see how it works
MikeyMike01 said:
The person who made the theme did it lazily and incorrectly. The first couple versions of my ROM had this problem. Did some research into how .9 PNGs work.
Click to expand...
Click to collapse
Most of the available themes can't be compiled and decompiled without errors
w83 said:
Most of the available themes can't be compiled and decompiled without errors
Click to expand...
Click to collapse
But mine can.
Spent a couple days fixing every .9 PNG one at a time. All you have to do is:
Decompile the unthemed .apk
Copy the broken PNG equivalents from the unthemed .apk
Decompile the themed .apk
Delete the broken .9 PNGs
APK Manager will rename the broken xxxxx.9.png to xxxxx.png
Open the non-broken PNGs in your favorite image editor
Delete everything but the 1 pixel border
Paste the edited PNG over it, without touching the 1 pixel border
Save
Recompile the themed.apk
MikeyMike01 said:
But mine can.
Spent a couple days fixing every .9 PNG one at a time. All you have to do is:
Decompile the unthemed .apk
Copy the broken PNG equivalents from the unthemed .apk
Decompile the themed .apk
Delete the broken .9 PNGs
APK Manager will rename the broken xxxxx.9.png to xxxxx.png
Open the non-broken PNGs in your favorite image editor
Delete everything but the 1 pixel border
Paste the edited PNG over it, without touching the 1 pixel border
Save
Recompile the themed.apk
Click to expand...
Click to collapse
Thank you so very much for sharing this info!!!
MikeyMike01 said:
But mine can.
Click to expand...
Click to collapse
Perfect
MikeyMike01 said:
Delete everything but the 1 pixel border
Paste the edited PNG over it, without touching the 1 pixel border
Click to expand...
Click to collapse
You can just edit the broken png in draw9patch (or gimp or whatever) but sticking to the patch 9 png rules
Thanks for sharing !
Could you briefly explain how the editing in draw9patch is done, please.
MikeyMike01 said:
But mine can.
Spent a couple days fixing every .9 PNG one at a time. All you have to do is:
Decompile the unthemed .apk
Copy the broken PNG equivalents from the unthemed .apk
Decompile the themed .apk
Delete the broken .9 PNGs
APK Manager will rename the broken xxxxx.9.png to xxxxx.png
Open the non-broken PNGs in your favorite image editor
Delete everything but the 1 pixel border
Paste the edited PNG over it, without touching the 1 pixel border
Save
Recompile the themed.apk
Click to expand...
Click to collapse
But lets say I want to change the default blue of 'statusbar_background.9.png' to full plain black. If I leave the 1 pixel border and fill the rest to black, wouldn't I have a blue border in the status bar?
brittosa said:
But lets say I want to change the default blue of 'statusbar_background.9.png' to full plain black. If I leave the 1 pixel border and fill the rest to black, wouldn't I have a blue border in the status bar?
Click to expand...
Click to collapse
No, there's a special one pixel border that has black and transparent pixels that tell the system how to stretch the image without making it look stretched.
That's why you'll note that .9 PNG files are buttons and other things that are used to make different sized objects.
Sent from my Captivate.
I would like to add some emoticons into whatsapp
Sent from my GT-I9100 Westcrips ICS using xda premium
RodneyNL said:
I would like to add some emoticons into whatsapp
Sent from my GT-I9100 Westcrips ICS using xda premium
Click to expand...
Click to collapse
You probably wont be able to add any, you can change the current ones by editing the apk, signing it then installing it. Once you open up the apk (with 7zip, winrar etc.) look inside the drawable-hdpi folder. Thats probably where the emoticons are kept.
I can help if you need.
You might want to check out these custom whatsapp's by yorzua :
http://forum.xda-developers.com/showthread.php?t=1543631
Thanks for your reply om gonna try it out i'll let you know of i need your help (probably i will need it xD)
Sent from my GT-I9100 using xda premium
Adding icons to whatsapp
Hey Guys has anyone tried adding new icons into the default whatsapp?
Or do the modded versions allow adding additional GIF'S to be added to the instant messenger?
Thanks
yes i have tried it, but it's useless since the recipient of the emoticon should have the "moded" version too, so that he could see the emoticon
Just wanted to add that Ive noticed the Iphone has new icons and I can view them on my phone which dont have those icons :/
esk02k said:
You probably wont be able to add any, you can change the current ones by editing the apk, signing it then installing it. Once you open up the apk (with 7zip, winrar etc.) look inside the drawable-hdpi folder. Thats probably where the emoticons are kept.
I can help if you need.
You might want to check out these custom whatsapp's by yorzua :
http://forum.xda-developers.com/showthread.php?t=1543631
Click to expand...
Click to collapse
I used 'Formatter' to rename (whatsapp) .apk file into .zip did required changes (replaced one .png smiley file) & again renamed it into .apk
But then, I'm not able to install it (even after uninstalling previous version). An error saying 'Application not installed' shows.
How can I modify .apk files (in terms of replacing only the smiley image files) & repack it into proper .apk file so that I'll be able to install it without any error?
Please help me..
thanks
yogz214 said:
I used 'Formatter' to rename (whatsapp) .apk file into .zip did required changes (replaced one .png smiley file) & again renamed it into .apk
But then, I'm not able to install it (even after uninstalling previous version). An error saying 'Application not installed' shows.
How can I modify .apk files (in terms of replacing only the smiley image files) & repack it into proper .apk file so that I'll be able to install it without any error?
Please help me..
thanks
Click to expand...
Click to collapse
i also want a new smiley, for example a puking smiley
After modifying the apk i think you should resign it to be able to install it
Check zipsigner from the play store
Sent from my GT-I9100G using XDA Premium 4 mobile app
fmardini said:
After modifying the apk i think you should resign it to be able to install it
Check zipsigner from the play store
Sent from my GT-I9100G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
so i have to download the whatsapp.apk, unrar it, change the icons in it, and resign it?
Were are the folder?
I am getting a "parsing" error by installing whatsapp
jonny.pl said:
i also want a new smiley, for example a puking smiley
Click to expand...
Click to collapse
That is exactly what I am trying to do here.
I was looking for the same & found these.
http://www.techgyd.com/whatsapp-stickers-free-android-iphone/12739/
Good idea, but not practical
In order to install an apk, it must be properly signed and with a password that only the developers know. If you own the app though, you will still need to to decompile and recreate the apk structure by turning the directories of the zip into an android structure, since the compiling will change pretty much everything.
Worst part of it all, if you somehow manage to change and install the app, only you will be able to see it since only the apk installed on your phone has those custom emoticons.
Cheers :good:
how do I put emoticons on viber /whatsapp for sell
Just get your friends to use wechat, has all the emos in the world. Whatsapp is crap
Recently SwiftKey released a beta version of their keyboard that backs up data to the cloud and installs separately from the market version. In order to have all my previous use data uploaded, I should be able to install this beta as an update to the market version of SwiftKey and the data will be backed up. The market version has package name com.touchtype.swiftkey and the beta is package name com.touchtype.swiftkey.phone.obeta . I tried changing the package name in AndroidManifest.xml and styles.xml , along with replacing every instance of com.touchtype.swiftkey.phone.obeta with com.touchtype.swiftkey within the decompiled apk. Using both APK-Multi-Tool and Virtuous Ten Studio it will not recompile, and I cannot figure out how to fix the issues to build. Attached to this post is a log from Virtuous Ten Studio when trying to recompile, any help is appreciated. Or if there is another easier way to change the internal package name, please let me know. Thank you in advance!
LOG FILE HERE--> https://copy.com/byWYTLWSt8Idf6OI
Also if someone could enlighten me on how to use the aapt command "--rename-manifest-package" it would be very much appreciated, as I think that would be the easiest solution if I just knew what to type!
imaconeheadXD said:
Recently SwiftKey released a beta version of their keyboard that backs up data to the cloud and installs separately from the market version. In order to have all my previous use data uploaded, I should be able to install this beta as an update to the market version of SwiftKey and the data will be backed up. The market version has package name com.touchtype.swiftkey and the beta is package name com.touchtype.swiftkey.phone.obeta . I tried changing the package name in AndroidManifest.xml and styles.xml , along with replacing every instance of com.touchtype.swiftkey.phone.obeta with com.touchtype.swiftkey within the decompiled apk. Using both APK-Multi-Tool and Virtuous Ten Studio it will not recompile, and I cannot figure out how to fix the issues to build. Attached to this post is a log from Virtuous Ten Studio when trying to recompile, any help is appreciated. Or if there is another easier way to change the internal package name, please let me know. Thank you in advance!
LOG FILE HERE--> https://copy.com/byWYTLWSt8Idf6OI
Also if someone could enlighten me on how to use the aapt command "--rename-manifest-package" it would be very much appreciated, as I think that would be the easiest solution if I just knew what to type!
Click to expand...
Click to collapse
Zarboz is beast.
Sent from my HTC6435LVW using xda premium
Bump, anyone?
You need to rename each subdirectory to match the new package name as well
Did you replace all references inside the smali too? As in, a reference to com/touchstone/swiftkey/phone/0beta/Class.smali is now com/touchtype/swiftkey/Class.smali
Sent from my buttered S3
CNexus said:
You need to rename each subdirectory to match the new package name as well
Did you replace all references inside the smali too? As in, a reference to com/touchstone/swiftkey/phone/0beta/Class.smali is now com/touchtype/swiftkey/Class.smali
Sent from my buttered S3
Click to expand...
Click to collapse
From what I could tell I replaced everything, the log is showing errors with aapt so it's not building for me still. Would you happen to know how to use the aapt command "--rename-manifest-package"? I saw this post here but I'm not sure where I type what he mentioned or how it works, if you could enlighten me that would be great (since I know you use Linux, maybe it relates?)
http://forum.xda-developers.com/showpost.php?p=37885462&postcount=14
Okay, so I am trying to get the navbar working on the Samsung Galaxy Note 3. Pretty much, I have a feeling that SystemUI is missing the icons for the navbar, which causes it to crash when the build.prop has the line "qemu.hw.mainkeys=0". The SystemUI has all the other files that were required for the S4 sysui mod, except for the icons. Being a noob at this, I went ahead and tried to add the icons, but my apk resulted in "System UI has stopped.".
So I decided maybe I am doing something wrong. So with Android Multitool for windows, I installed framework-res.apk, SystemUI.apk, and twframework-res.apk. Next I select the SystemUI.apk for decompiling, and decompile it. Then I simply select the decompiled directory (didn't modify anything!), and recompile it. I then open the new SystemUI.apk in 7z and add the META-INF and AndroidManifest.xml from the old SystemUI.apk. I then select the newly compiled SystemUI.apk for signing, then I sign it.
This is just decompiling, then building the same thing without modifications. SystemUI.apk before decompiling is 2.7 MB, the newly compiled one is only 2 MB! Something is missing out of the new one, but when I compare them in 7z, the only thing I can see that is different is the packed size; whereas the old one has files and folders that take up more space packed than the new one.
When I try doing this with just apktool and cmd, I get java errors like crazy, and the whole SystemUI.apk ends up only half decompiling.
Any idea what I am doing wrong?
Your best bet would be to copy the log to pastebin, and post it in the apktool support thread. Get more views there for sure. Which version of apktool are you using? Can you decompile and recompile anything? Also, if you want post your systemui up and i could see if I can get it to work, narrow it down to a problem on your end that way.
Sent from my SM-N900T using Xparent Skyblue Tapatalk 2
This is my first time doing this, so of course I make a noob mistake! I thought I had to sign ALL apks, but this is a SYSTEM app, and I don't sign it. All is well! Thanks for the reply. I also updated my apktool to 1.5.2, so that may have helped too.
all you have to do is add a + before the @ sign in the line that is giving you errors....umm depending if it is xml errors....
post the errors.....
gakio12 said:
This is my first time doing this, so of course I make a noob mistake! I thought I had to sign ALL apks, but this is a SYSTEM app, and I don't sign it. All is well! Thanks for the reply. I also updated my apktool to 1.5.2, so that may have helped too.
Click to expand...
Click to collapse
You don't need to sign it? I have also this problem. It gives me error that SystemUI has stopped.