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
Related
I flashed MIUI, then applied the theme I wanted, Elite Pro HD. I wanted the SCB battery mod as well, so booted into recovery and flashed the one I made of only the battery mod, however after uploading the framework-res.apk file in the kitchen it removed practically all themeing in MIUI after reboot. After I do that, it will not allow me apply any new themes. Some icons change but nothing else, the dock icons, fonts etc all stay stock MIUI and I can't figure out why so any help would be much appreciated. Would love to be able to somehow implement the SCB mod into the theme or just make them work together.
it sounds to me like you will have to learn how to make custom frameworks if you want it all working together.
my suggestions:-
choose whatever battery you want on UOT - make it for any rom, doesnt matter you only need the files.
decompile the UOT framework - take the .png's for the battery and .xmls that control them
decompile your already custom framework - copy .xml's and .png's from the UOT framework over to it.
compile framework, add it to an update.zip and sign that.
you might want to search xda if you dont know how to do any of the above, all the info is available here
EDIT: looking at that theme it already has a percentage battery, if the .xmls are the same as UOT you could just replace the .png's in the original update and re-sign
trialsrider1 said:
I flashed MIUI, then applied the theme I wanted, Elite Pro HD. I wanted the SCB battery mod as well, so booted into recovery and flashed the one I made of only the battery mod, however after uploading the framework-res.apk file in the kitchen it removed practically all themeing in MIUI after reboot. After I do that, it will not allow me apply any new themes. Some icons change but nothing else, the dock icons, fonts etc all stay stock MIUI and I can't figure out why so any help would be much appreciated. Would love to be able to somehow implement the SCB mod into the theme or just make them work together.
Click to expand...
Click to collapse
Kitchen removes nothing. if u cooked file from your rom, so u get everything stock.
U should cook framework-res.apk from the theme's zip.
I have trying to get themes to run in the Doc and Stefunel kitchen.
This is a pretty demanding task. Many (almost all) themes can not be used as is due to a non standard resources.arsc and 9.png errors.
There is some theme pro's here.
We like to find a some kind of way to enable any theme inserted in a rom.
Any ideas to make this in a easy way?
/Doc
No one here any ideas? I already proposed someone make a theme kitchen and integrate it with Doc's rom kitchen but apparently all the smart guys that got time and would know how to do that bought a Desire.
Which takes us back at doc's original question someone knows a fail-proof way to integrate themes into roms without having to flash a post-install zip?
Hi Doc,
i know this isnt way you want, but probably it can work:
What about make some script, witch will do:
1) after flashing ROM and start android - reboot android to recovery
2) (i dont know if it is possible) make script for CWM witch will automaticaly flash theme and reboot to system
If Im wrong .. ignore this
schiphol said:
Which takes us back at doc's original question someone knows a fail-proof way to integrate themes into roms without having to flash a post-install zip?
Click to expand...
Click to collapse
I've never need a post-install script to put a theme into a ROM.
Except for the JPY Gingerbread, but me and XGX got that hammered out in the thread in the Captivate forum and it works just fine without a second .zip.
MikeyMike01 said:
I've never need a post-install script to put a theme into a ROM.
Except for the JPY Gingerbread, but me and XGX got that hammered out in the thread in the Captivate forum and it works just fine without a second .zip.
Click to expand...
Click to collapse
Hi, any link to point in right direction is most welcome
I've merely dropped the framework-res.apk and twframework-res.apk into the /system/framework. And any other files like android.policy.jar that goes with it.
For JPY, I had to take a few extra steps:
http://forum.xda-developers.com/showpost.php?p=10258171&postcount=328
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 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