Im currently running aokp build 5 and i did a lot of theming including .9.png files. i want to flash to the new milestone build. Can i simply pull the drawable folders out of my old one and drop em in the new one, or since there are .9.png files, would i have to decompile, put into the new apk, and recompile?
thanks
You may end up bootlooping if the new roms has more images or removed some. Your best bet would be to decompile both and then change out the images and then recompile the new apk.
Come to think about it there are lots of changes so follow the above.
Wayne Tech S-III
Related
Hello,
I always got Multiple lockscreen frameworks such as EDT and JKay's Lockscreens. I really want to know, actually where are these files located in framework-res..
I want to port EDT's JVR lockscreens to JVS framework.
Anybody willing to help me?
Regards,
Rahul
I'm quite interested in this too...and I guess that nobody will write us down a list with needed files .....I can tell you what I've found out so far and hope that it will be of any help to you.
The smali files for the lockscreen itself I think they should be in android.policy.jar
Then there also should be some changes in framework.jar which I do not know.
The ressource files like pictures etc are in the framework-res.apk
Then you also need the edt.apk in /system/app
Decompile the files with apkmanager/baksmali
Use a comparision tool like winmerge to see what files are added additionaly compared with the standard stock files. And also too see if there are smali changes in some files.
Good luck
Sent from my GT-I9000 using Tapatalk
why bother, they are not bug free anyways
$omator said:
why bother, they are not bug free anyways
Click to expand...
Click to collapse
You said that more than once now, but I sure as hell don't suffer any bugs while using them on JVQ or JVR.
While we're at it, I thought, hey, what the hell, I can learn and do it myself. Always good to learn this sort of thing. So I got smali/baksmali, winmerge, and Whitehawkx's source files, which I think will work.
But that's not the point.
The point is that baksmali is desassembling the .dex files just fine, but when I want to make a new file after merging the files from the sources with the originals of the .dex... It makes a .dex with the original files.
That is: disassemble -> merge the files -> I make sure the files are there. They are. -> I use smali, it creates the new .dex -> As everytime I do anything, I think, hey, lets disassemble the new file again to make sure the new files are there -> The files are not there.
It's driving me crazy... I mean, how the hell does it create a file from something that isn't there any more?
I can sort of get that the new files and folders don't make it to the new .dex (although, no, I don't get why would that be), but how can the overwritten files go back to be the original ones?
Seriously, driving me crazy.
Edit: Ok, nevermind what I said... The files change frigging places when smali assembles them...?
Edit2: Suprise, surprise, it didn't boot, but now I don't know if it's because I did something wrong or because the source files aren't good for JVS. I'm gonna try to do it on JVP, I'm curious now...
$omator said:
why bother, they are not bug free anyways
Click to expand...
Click to collapse
Well because some of them have features people want to have...and also because people can live with some of the bugs. I don't care if it writes me SIM-Card is locked even if it isn't. The functionality doesn't decrease because of that.
But well these lockscreens give us a music widget that works with other players then the crappy samsung stock one. And I can unlock directly to messages or phone. If it was for me I would only need something like the fourtab(which sadly has a memory leak)...but if the whole package could be ported or whatsoever and people would like to do it why not ?
Code is present in the android-policy.jar and framework.jar (for some lockscreens). You need to copy over the Smali Files fromt he MOD to the JVS framework and android policy. After that you need to copy over the drawables, layouts and other xml files to the framework apk of JVS and assign them each a unique resource ID. These resource IDs need to be substituted with the new values in the Smali files. Since the framework-res.apk changes with Firmwares, the Resource IDs are different for each framework.
It's very complicated stuff for rookies. You need to know which stuff to copy where and what modifications to make for specific lockscreens. And you need to use Logcat and do a lot of trial and error.
And $omator is right. Those lockscreens all together don't work perfectly due to conflicting code. For example, I made a SGS II Lockscreen Port http://forum.xda-developers.com/showthread.php?t=1070564 . The Same Lockscreen that is found along with 9 Lockscreen MOD is incomplete and doesn't work perfectly. I don't mean to say that the 9 lockscreen mod is useless, but It is very handly provided you compromise on what you get.
dhiru1602 said:
Code is present in the android-policy.jar and framework.jar (for some lockscreens). You need to copy over the Smali Files fromt he MOD to the JVS framework and android policy. After that you need to copy over the drawables, layouts and other xml files to the framework apk of JVS and assign them each a unique resource ID. These resource IDs need to be substituted with the new values in the Smali files. Since the framework-res.apk changes with Firmwares, the Resource IDs are different for each framework.
It's very complicated stuff for rookies. You need to know which stuff to copy where and what modifications to make for specific lockscreens. And you need to use Logcat and do a lot of trial and error.
And $omator is right. Those lockscreens all together don't work perfectly due to conflicting code. For example, I made a SGS II Lockscreen Port http://forum.xda-developers.com/showthread.php?t=1070564 . The Same Lockscreen that is found along with 9 Lockscreen MOD is incomplete and doesn't work perfectly. I don't mean to say that the 9 lockscreen mod is useless, but It is very handly provided you compromise on what you get.
Click to expand...
Click to collapse
Very complicated to do something like that from scratch, yes.
If at least one of the persons that have made a 9 lockscreen JVS rom posted the sources... From there I've learned by now that it's fairly easy to just include them into the files.
But no one have.
If you really want to learn how to do it i can only recommend read lots of info and do some investigations by yourself.
If some guy made the stuff for lets say XXJVQ then grab the files and compare them with the stock files. Decompile them with apkmanager. (jar files can also be modded this way, you only need to add .apk to the jar extention, and remove it later after compiling back)
This way you can see what files need to be added and what values need to be changed/added. First try to understand the process and after that make your own mods.
I used Winmerge for comparisation of the files.
Well... I modded the overscroll by myself. It's a start.
Thanks to Team Obssessed, we can already have multiple lockscreens on JVS.
I already made a theme as I like and added the lockscreens thanks to the files of this rom.
Now I can have a proper JVS .
Is just that I'm too used to puzzle and MIUI lockscreens to go back to stock or AOSP. And those two work without bugs, so... And don't know about the rest.
and btw. apkmanager got aapktool with outdated baksmali/smali ...
I have been reading a lot of posts about theming and people are talking about decompile apk's and where different images are located within the system and apps, however, I am somewhat confused as to where to start and what they mean. Could anyone shed some light and maybe get me started in the right spot. Trying to learn how to create my own themed phone.
I should mention I am currently running a custom rom, rooted, cwm, and have the basics down.
I think ICS still has issues with the apktool to decompile, need an older version to compile and newer to decompile. So its tricky. But you just pull your systemUI apk for example, make changes and flash it back. Or the real way is just mod the source code directly and compile. Search the apktool thread.
Does any one know how to theme the htc resources with out crashing? im theming MikG 3.11, but every time i theme the resources, it crashes on the weather widget. any help?
Hmmmm.
What are you using to theme it? Have you extracted the resources and right clicked an image and tried using a paint shop program then simply painting over the images? Thats what I am doing on CM7 and did some cool stuff with the widgets and MMS on the latest build (such as blach background and neon edges). What OS are you using? I'll try it since I wanna theme sense now. I'm too new to XDA to post my new roms. I'm focusing on stability and HD modifications but like your idea
alexthesniper21 said:
Does any one know how to theme the htc resources with out crashing? im theming MikG 3.11, but every time i theme the resources, it crashes on the weather widget. any help?
Click to expand...
Click to collapse
First thing you will need is an apktool then folow the directions to install the proper framework. Then use paint, photoshop, or gimp to make your changes. Be careful of anything that ends in .9 as these are special pngs and need to be handled differently. I used to theme Sense but stopped due to having to rewrite to many files for the changes I needed and have moved on the AOSP based roms which are much more straight forward.
Thank blaz1nr for this, all info he passed on to me, Hope it helps you,,,Later,,,
When you start working on transparency. The status bar/footer should be 20% less transparent than the background. Header starts at 10% less than background. Pop ups are where is gets a little harder. They must be opposite each other (ie) black/white text or white/black text. Black looks better but is more of pain. Make sure to keep pop ups slightly transparent, you should be able to see through them a little. Once you have the first one done then you be able to see what % to change and where,but these are good starting points. Status bar/header/footer should be the 3 darkest. It should look something like this. Status/[email protected] 60%, [email protected]%,[email protected]% pop [email protected] to 80%. So 100% is solid as you move down towards 10% it gets more see through.
PART 1:
Im going to to try to sqeeze this down as much as possible.Basically I'm gonna give you, the how to do stuff.Then I'm going to give the short cut's to figuring out what to do.First your gonna need some stuff.
1 Java EE jdk, jre
2 Apk tool
3 Android Sdk
4 Eclipse IDE
5 7 Zip
6 M10 editor
7 Cygwin
8 Android Kitchen
9 Notepad++
10 Alot of patience
Listed above is everything needed to build or theme a rom.
You wont need android kitchen or cygwin,if you just want to theme.You will need everything else.
This is a easy way to learn how to set up android kitchen so you can build your own roms from unrooted stock roms----> http://www.androidmerom.com/2012/01/11/4/
How to dev correctly----> http://forum.xda-developers.com/show....php?t=1273044
Porting things like clocks or widgets---> http://forum.xda-developers.com/show....php?t=1222746
Adding transparancies to status bar(its in the galaxY s forum but this is what you do) http://forum.xda-developers.com/show....php?t=1327565
Learn how to recompile and decompile apk's first,Since this is a sense rom, you need 3 things to do this,SystemUi.apk,its in system/apps,
framework-res.apk & com.htc.resources.apk, they are in system/frameworks
PART2
Ok so now I'm gonna give you a bunch of info that will speed up your learning of what to do.
Since this is a sense rom, When you decompile SystemUi.apk it needs dependencies.These are the two apk's you got from system/frameworks.Learn how to use apk tool there's guides everywhere when its time to add dependencies you need to use both of these commands in cmd. apktool if framework-res.apk,apktool if com.htc.resources.apk, i cant stress enough that you first learn building apk's and how to use apk tools. once you know how apk tools works the commands earlier will make sense.Learn how to push your new apk to your phone with sdk.
A system app cannot just be dropped in the system. Unless your rom zip is open and your building it. Here come's the good stuff, when your trying to do something like move you clock to the center of the status bar.What you can do is decompile the apk's from earlier out of a rom that has a feature you like.Open it and find what files you need, copy them to your desk top. Now find the same files you need to change in your rom and look through them to see whats different in yours that you need to change(Notepad ++ is used for this/also M10 editor). 7zip will be your best friend from here on out.In 7zip all you need to do is click open archive. now you can add or remove anything you want,when your done just close it.This works for every zip file.UOT kitchen can be used to do a small amount of theme work.
Build.prop work is done the same way using notepad++. Say you built your own rom,but your not sure how to get your rom name or add 3g/4g/wifi tweaks or hardware acceleration or what ever.There's a lot that can be done in a build.prop that will do some major magic.you could compare mine to yours and see whats different and make changes.Use common sense here.Don't just go changing things if you don't know what it is first. That's it all you need to know right there to get you started. Now all you have to do is search around for whatever it is you want to do. locate the things you need to change and your on your way.
Although basically I've given you everything you need to get you stared.Not everything can done by simply changing lines of code in one spot some things have files located in multiple location that will need to be edited so...RESEARCH RESEARCH RESEARCH.Remember don't be a **** and steal someone's thunder,just so you can say you built a rom. Give props and ask the other dev's if you want you use something they worked hard making.
I just recently switched my stock rom to be deodexed and I'm now looking at the possibility of theming and mods for my rom.
I already have a little experience modding the signal icons on a different Android device, and I've already downloaded a mod from this forum that turns part of the stock dialer to a holo dark/material theme, but I want to do more with it.
So far I can't seem to find a good tutorial on how to properly mod system files, especially knowing that the stock rom on the Moto G is a Motorola variant of Android KitKat, and not AOSP or similar, although it's close enough that I figure some mods might work since many Xposed modules for AOSP work fine on my stock rom.
Would it be safe to look for a tutorial based on AOSP 4.4.4, or does anyone know a good place to learn the proper way to modify and theme a Motorola stock rom?
chuman72486 said:
I just recently switched my stock rom to be deodexed and I'm now looking at the possibility of theming and mods for my rom.
I already have a little experience modding the signal icons on a different Android device, and I've already downloaded a mod from this forum that turns part of the stock dialer to a holo dark/material theme, but I want to do more with it.
So far I can't seem to find a good tutorial on how to properly mod system files, especially knowing that the stock rom on the Moto G is a Motorola variant of Android KitKat, and not AOSP or similar, although it's close enough that I figure some mods might work since many Xposed modules for AOSP work fine on my stock rom.
Would it be safe to look for a tutorial based on AOSP 4.4.4, or does anyone know a good place to learn the proper way to modify and theme a Motorola stock rom?
Click to expand...
Click to collapse
get apktool
with this decompile your apks you want to theme/mod
hapy theming! (there plenty of tutorials of how to edit images or the .9 patch files. with gimp etc.. just search )
after that recompile, if you just have edited some images (ressources) pull them afterwards from the new COMPILED apk out in a folder.
take the original apk & open with 7zip & pull the edited stuff into the right directions.
if you have done some advanced modification such as in values folder, you need after the new apk is compiled, open it with 7zip & pull from the original app the meta-inf folder into the new compiled one (singing) after tthat replace it on that phone
Hi everyone. I own the Samsung Galaxy J3 2016 carrier Virgin Mobile. I am attempting to decompile android.policy.jar to do some smali editing. And oddly enough a number of the general jars we all edit regularly to add mods such as reboot menu,etc. are pretty much empty files on my J3. The android.policy.jar file is only 309 bytes with nothing in it except a Meta INF folder with MANIFEST file in there but noting else at all. No classes.dex. Now I thought ok maybe its because I am not deodexed. So I looked in the arm folder in framework and there are indeed odex files in there but none for android.policy.jar nor other typical modded jars we tend to mod. Is this normal across the board for newer Samsung devices like the S6/7 models? Also when I decompile an apk like SystemUI.apk there are no smali files included with the decompiled apk. But the apk seems to decompile correctly and I can edit whats there just fine and recompile it and use it successfully. I just added a center clock mod to SystemUI in fact and it works fine. Just confused about what I am missing here. I seem to have all of my tools up to date for decompiling. Can anyone point me in the right direction? Or give me some insight on these new changes. Thanks