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 ...
Was wondering if there is a themeing form for dummies on how to theme galaxy s3, or a list of themes for blazer rom. I want to change colors of mms, icons in pull down, change carrier label, basically change the color theme of touch wiz to match the new sype beta red theme(white, black, and red), just need pointed in the right direction not asking for someone to do it for me. All the post i could find were for themeing samsung epic touch and so on. Thanks in advance and i will hit the button if helped.
First you need to set up apktool on your computer/laptop. Google "How to Set Up Apktool". I don't know what OS your home computer/laptop so you'll have to tailor your set up.
I use Windows, here is a decent guide for Windows 7 x64
After you install the prerequisites (java, sdk etc) go here and grab the modified apktool.jar AND aapt.exe and place them in your apktool directory (it will replace the older ones you used in the guide, the one I linked to is a new, updated version that works with TW and AOSP very well)
After you have everything installed and apktool is ready to go, pull these files from your ROM and place them into your apktool folder (you can use adb pull or simple copy/paste the apk's from your system onto your SD then transfer them to your computer). You will need:
Code:
-/system/framework/framework-res.apk
-/system/framework/twframework-res.apk
-/system/app/SecMms.apk
-/system/app/SystemUI.apk
Place all of these apk's into your apktool directory. Now open a new command prompt window and "cd" your apktool folder. For instance, mine is C:\apktool\ so I type
Code:
cd apktool
Next, type
Code:
apktool if framework-res.apk
apktool if twframework-res.apk
This will install resources so you can now decompile apk's that use framework-res.apk and twframework-res.apk resources
Next you can decompile all of those apk's. SecMms.apk is the messaging app, SystemUI.apk is the statusbar and the two framework files are the system framework
To decompile:
Code:
apktool d framework-res.apk
After you make changes you recompile (your new apk will be in the framework-res/dist folder):
Code:
apktool b framework-res
You can alter the folder names of each of these. For example if you want the decompiled framework-res folder labeled per ROM you could do
Code:
apktool d framework-res.apk framework-res-blazer
So, to make everything red and black your going to have to manipulate both xml's and png's. For png's I suggest Paint.NET or GIMP, both are free. I honestly prefer Photoshop and have been using it for quite some time, however it is expensive (I think they do a free trial and have discounts for students). Pay special attention on ".9.png's", these are stretchable images and need to be treated differently (Google some guides on that)
For XML's. in framework-res/res/values/ you will find plenty of colors to change, especially for TW. I would go to colors.xml and change the holo_blue_light and holo_blue_dark to a red color (I use this tool to find appropriate hex colors that android uses). If you see an "ff" in front of the color it just means that the color will be shown 100% (no transparency).
So I would dig through those apk's, the easiest parts will be modifying the images as sometimes colors can be tricky to mod in xml's, but like I said, those two holo colors do control a lot. Same in the SecMms.apk and twframework-res
After you recompiled you apk's you need to copy over the META-INF folder AND the AndroidManifest.xml from the original apk to your new one ( I use WinRar, however 7-Zip is free)
Here is a guide I made on how to make a flashable zip after you made your apk's, just follow that and make a backup before flashing
Good Luck!
So I typically like to tinker when I get new phones/tablets. One of the first mods I always attempt is an extended power menu. That means android.policy.jar and framework-res.apk need to be pulled to my computer for decompiling. Not to mention, deodexing the jar file. But for the life of me, I cannot find the odex component for android.policy.jar. Has anyone else found it? In past OS versions they were there beside their jar/apk mates. And in lollipop, looks like in /system/framework there is an /art folder which has SOME of the odex files but not all.
There are no odex files because they are deodexed by default.
There is no android.policy.jar for Android 6.0 both GPE and Sense.
If you want to add in Advance Power Menu, you need to see services.jar & framework-res.apk
Hint : \services.jar\smali\com\android\server\policy
If you manage to make one, let me know (by PM also ok) because I don't have the time to look further into it.
All it takes is for you to take a backup and run the deodex wrapper on your device creating classes.dex's files in all you'r apks allowing to edit the smali. I would do it myself but I currently dont own the device.
Pneuma1985 said:
All it takes is for you to take a backup and run the deodex wrapper on your device creating classes.dex's files in all you'r apks allowing to edit the smali. I would do it myself but I currently dont own the device.
Click to expand...
Click to collapse
Here you go i included the app, dex, framework, odex, priv-app you will need 7-zip because i compressed it from 850mb's to 350mb's.
https://www.androidfilehost.com/?fid=24549084345925845
That does not have all the .dex files in the dex folder. Thus I can not access the smali... Which is what I was after a certrain method within the netxbit systemUI smali. Though it did give me the .dex files of several apks just not the exact one I was after. How do I access the systemUI .dex. It's been a long time since I've made roms and deodexed apks especially now with art. I'm really after the UI .dex file so I can gain access to a specific method within in it. If you could post that I'd be ecstatic Something I decompile to track down smali methods I want to recreate in my own custom 6.0 SystemUI.
Nvm Ticklefish's tool did the job http://www.mediafire.com/download/czod7v081w0ravt/TickleMyAndroid+-+v13.3.0.exe
The only tool out of all the deodexing tools that worked!!!!! The only one! Aside from the linux kitchen but I wasnt setting that up... Mess up my linux install no thanks!
FM radio
Is this FM radio apps
Hello,
I need your help!!
I have been customizing my Galaxy Tab S, which I recently updated to Lollipop, and I have successfully customized SystemUI.apk, SecSettings.apk, etc. However, when I wanted just change a value in framework-res, I got many FC's. I cannot even open Settings.
So, I decompiled framework-res and recompiled it without changing anything. The result is the same. I got many FC's and not even the power button is working. And, I need to reflash original framework-res.
As I normally use Apk Multi-tool (with Apktool 2.2.2.), I tested Advanced Apktool (4.1.0). The result is the same and the recompiled framework-res is not usable.
What am I doing wrong? Maybe there is something special about this framework-res?
Maybe it is the version of Apktool? What is the version which works for framework-res?
Which tool do you use to work with framework-res from Galaxy Tab S (Lollipop)?
By the way, I did not have any problem with Kitkat framework-res from Galaxy Tab S. Neither did I with Lollipop framework-res for Galaxy Note 3.
Can someone help?