Added better animations to the CM10 framework for Xperia Ion
Have used fxp 235 as base, but should work in other builds too.(NOT in miui and pa as they have a different framework)
Just copy and replace in /system/framework/ with correct permissions.
DO TAKE A BACKUP BEFORE.
framework-res.apk
have made a few more tweaks and modifications to the cm10 build, will be uploading a video shortly..if you guys like it i'll integrate it all as a rom
May i ask how you made your animations (sources tutorials blah blah)
Because im working on a stock jb framework
Another something i think does not get enough attention
Related
Hello all,
I have been searching for a while but couldn't find any specific info on this subject. I'm wondering if different lockscreens can be used on ROMs other than CyanogenMod. I use TheOfficial HTC ADP 1.6 DRC83 ROM, Can custom lockscreens like Stericson's be used? Thank you all Developers/ROM cookers for making all these awesome modifications to these phones possible. Please dont flame me, Im new to all this...
thanks all...
I am pretty sure the lockscreen has not been ported over to 1.6 yet. I know it is being worked on.
I know an unmodified services.jar from the 5a lockscreen will work with akirahs rom, but a modded services.jar will not go past the first splash screen.
Lockscreens can be added to any rom, provided you have the source for it's services.jar, however, as a simple "drop-in", no, it has to be designed for that rom because of specific dependencies between a rom's framework (though two roms based on the same framework should work as long as it's not been odexed). There's a way to do it, though, but it's a lot of work, you could have the services read off of an xml that you can store in your system folder (maybe etc) and toss your changes there. I'm working on..... .nevermind
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 ...
My phone (Galaxy S Plus) is running aosp ics built by broodplank and i want to theme it with touchwiz 5 cm9 theme. I used ninjamorph and copy and paste res file of the touchwiz 5 theme.apk (extracted) into both the systemui.apk and gramework-res.apk. I rebooted my phone and exactly no difference. Can someone tell me how to theme aosp? I hate cm9 cause aosp on my device runs smoother than vm9 and more slim
You probably didnt expect to see me here but i think you need to transfer those files with more care.
I mean the images in drawable-hdpi dont even match names probably so then its a waste of space only.
You need to check and study the contents of the aosp files good. And then based on what you know you start copying those files.
Im not a themer but i think its not just copying if you port them from a different framework (tw in this case)
broodplank1337 said:
You probably didnt expect to see me here but i think you need to transfer those files with more care.
I mean the images in drawable-hdpi dont even match names probably so then its a waste of space only.
You need to check and study the contents of the aosp files good. And then based on what you know you start copying those files.
Im not a themer but i think its not just copying if you port them from a different framework (tw in this case)
Click to expand...
Click to collapse
Thanks but are there any tw frameworks in your aosp?
Why you dont use the theme chooser from market and apply one touchwiz theme?
broodplank1337 said:
You probably didnt expect to see me here but i think you need to transfer those files with more care.
I mean the images in drawable-hdpi dont even match names probably so then its a waste of space only.
You need to check and study the contents of the aosp files good. And then based on what you know you start copying those files.
Im not a themer but i think its not just copying if you port them from a different framework (tw in this case)
Click to expand...
Click to collapse
he is completely right (it's broodplank, what you'd expect?)
I got a hint for you. these files which you extracted should have the same name as the same screen solution, if not, they are cannkt be displayed and you will get a fc.
How about making a team Juhan Jufri? you are a good modder! I'm building Project Stock at the moment (based on Broods AOSP (thank you again, really well done!)
It's a rom which should have all Samsung features we know well from our gb stock to make a stock like 4.0.4 rom (samsung said, they couldn't because of some hardware stuff, i will proof that).
It's not easy so I need help.
So? would you join my team and help me build Project Stock?
EDIT: forgot to answer your question. take the twframework.apk from a gb stock (based) rom. can be found (gess you already know) in system/framework
sent from my GameBoy Color
------------------------------
working on:
Project Stock (4.0.4)
Hi, I was just wondering if it would be possible to get the paranoid android colors feature where status and nav bar colors change based on the app you are in on AOKP rom. I know I could use a hybrid rom but that is the one feature that I want outside of AOKP. I did some searching but found nothing. Would I be able to install the paranoid preferences apk or does the feature depend on something in the rom?
i join your question
you cant do this , cause even with PAPref Apk , you need to change framework files which might take away AOKP stuff , your best bet is to use PAC , it uses ParanoidAndroid AOKP and CM , meaning all features of 3 roms is in .
-Jesco- said:
you cant do this , cause even with PAPref Apk , you need to change framework files which might take away AOKP stuff , your best bet is to use PAC , it uses ParanoidAndroid AOKP and CM , meaning all features of 3 roms is in .
Click to expand...
Click to collapse
Is there a way I can test what AOKP features would be compromised by editing framework files? Or would it just ruin the whole system framework?
This isn't exactly the same but may be a option to consider.
[MOD][XPOSED][4.0+] XThemeEngine beta5 - Theme engine for any rooted phone http://forum.xda-developers.com/showthread.php?t=2240180
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