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.
Related
Hi!
So, I decided to have a look inside AuraxTSenses framwork-res.apk ( applied SmoothSense to it ), and found .pngs and thought that I'm gonna try editing these. And so I did, and changed my lockscreen.
Then I did some more, and then I tried to change battery icons to Super Circle Battery just by replacing the .pngs and couple of xml files, but I ended up having no battery icon at all. Then I found UltraLinx's Minimal Matte Grey, and thought man I'd like to combine this and some of SmoothSense's icons + grey Super Circle.
Now, I know what I'm doing ( and did ) is NOT the right way, I basically just extracted the files I wanted to change, and then I threw the modified files back in to the framework-res.apk , and then I threw the modified framework to SmoothSense's installing zip and flashed the zip at recovery. And I did have the nice new lock screen look, but Theme Kitchen said that the framework is basically all the way corrupted.
So now I'd like to know what I need to do in order to do this thing correctly? The Theme Kitchen said that Minimal Matte Grey's framework is corrupted too, so I guess it's no good using it as the base-framework, and add the things I'd like to it? I know I'm supposed to sign something and compile and decompile and something?
If someone can give me any advice I would be more than grateful.
I've searched but can't find specific instructions on the exact files needed to pull, edit and push back to the framework to make the status bar semi-transparent or clear. This is something that always bothers me. I'm running CM7 n29 but if I had the general instructions it would be great so I could apply it to future updates as well without having to flash a whole theme. Thanks in advance...
Well, a quick fix would to be to use a theme; The honeybread theme give you a transparent notification bar; I use it and runs great.
http://forum.xda-developers.com/showthread.php?t=943423
I don't know which file it is in CM7, but in a sense rom the specific file I believe is common_app_list_null.png
And it is located inside com.htc.resources.apk > res > drawable-hdpi
You can rename any .apk into a .zip to open it and extract it for editing. Once you edit it, you may need to sign the file. I just use metamorph for my theming stuff, which makes things a lot faster.
As far as editing, you'd just need to select the area you want to be transparent or translucent, and edit its opacity accordingly with a decent image editing app. If you are looking for one, paint.net is a surprisingly good free one.
Thanks for the quick replies. I forgot about Metamorph. I've not messed with it but maybe I'll see what I can find out going that route. I don't want to change the whole theme because theres always something I don't like (icons, etc). I have Photoshop so its no problem editing it when I find it, just making sure I edit the correct .png! Thanks again!
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 ...
So, I forgot to backup my system & framework apk's before I uploaded them into the kitchen and made a new theme. *I know, shame on me*.
Is there a default/stock for those or are they created based of individual phone information?
What i'm asking is, do I need to re-install the rom to get those back or can I just pull them from above said stock apk's?
Android: 2.3.5
Rom:Cm7(08012011)
Any help would be greatly apprecaited!!!
Thanks-
Jodsfk421
Jodsfk421 said:
So, I forgot to backup my system & framework apk's before I uploaded them into the kitchen and made a new theme. *I know, shame on me*.
Is there a default/stock for those or are they created based of individual phone information?
What i'm asking is, do I need to re-install the rom to get those back or can I just pull them from above said stock apk's?
Android: 2.3.5
Rom:Cm7(08012011)
Any help would be greatly apprecaited!!!
Thanks-
Jodsfk421
Click to expand...
Click to collapse
i'm confused. are you saying you dont like your theme and want to go back to stock or you want you want to update to the next nightly but dont want to do the kitchen every time?
I'm not reaaal familiar with the kitchen stuff, I know more than enough to get myself in trouble (changing radio's, roms, etc) but haven't completely grasped the themes yet.
It SEEMS like a couple of things are not changing even if I create a completely new theme (The battery icon, the lockscreen buttons and something else I forget)
My thinking is, there's a generic theme(s) for the rom and when you create a get a new one, it updates certain aspects of it.
If I create a new theme in kitchen and only change the battery, wouldn't all of the other settings revert to the "default" theme?
On a completely different note-
What's the difference between ADW themes and Themechoose themes?
Jodsfk421 said:
I'm not reaaal familiar with the kitchen stuff, I know more than enough to get myself in trouble (changing radio's, roms, etc) but haven't completely grasped the themes yet.
It SEEMS like a couple of things are not changing even if I create a completely new theme (The battery icon, the lockscreen buttons and something else I forget)
My thinking is, there's a generic theme(s) for the rom and when you create a get a new one, it updates certain aspects of it.
If I create a new theme in kitchen and only change the battery, wouldn't all of the other settings revert to the "default" theme?
On a completely different note-
What's the difference between ADW themes and Themechoose themes?
Click to expand...
Click to collapse
Ah. ok. so what ever you change in the kitchen it will change in the apk. it wont touch the rest of the apk. its kinda like an online apktool. it unpackages it changes the png's you want and then packages it up again using the resources from the apk you submitted. ADW themes are for the ADW launcher so it only themes the home screens. but Themechooser themes the whole phone, or as much as the developer of themechooser allowed it to do.
Great! Thanks
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.