Related
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 ...
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)
What you will need:
Basic tools
- Notepad++
- ZIP manager tool like 7zip
Advanced tools
- Cygwin
- smali (assembler/disassembler)
- APKTool/APK Multi-tool
Lets Begin:
Download a ROM (we use CM in this guide) of your choice (don’t forget to get the permissions for it modding from the developer) and extract it. When you extract it, you will see at least two folders and one file
Folders
- system
- META-INF
Files
- boot.img [this is not present in defy/defy+ ROMs so don't worry about it ]
NOTE THAT I AM ONLY GIVING DETAILS ABOUT THOSE FOLDER WHICH YOU CAN REMOVE/EDIT
THE \system\bootmenu\2nd-boot\ FOLDER
In this folder you'll find the kernel [zImage] file of the ROM here you can change it with the one you compiled or by others.
The Tts folder
The ‘TTS folder’ is all about Text-To-Speech. It contains all the files needed by the Android system to get Text-To-Speech working. If you are removing the TTS feature from your ROM, make sure you remove this entire folder and the TTS related apps from the ‘system folder’, as this will save a lot of space.
The WiFi and Usr folders
The WiFi folder contains the drivers required by the WiFi module to function. So i strongly recommend NOT to touch this folder. If you delete any file from this folder, you will mess up the WiFi functionality.
The usr folder contains some miscellaneous but very important stuff. It may contain anything and everything needed by the Android operating system. For instance, this folder contains all the key-mapping. If such files are messed with, your device will be non-functional although it will boot.
The Build.prop
The build.prop file is pretty self-explanatory. Here, you can change the most basic things, like the android version that setting shows. Wondered how people are making 2.3.4 look like 4.0.3 in settings? Its build.prop. Also,you can change what ‘About phone’ shows here.
Other things,you can change things like,how long your wifi scans,how much battery your phone saves while in sleep, Dalvik VM heapsize and default ringtones. If you are wondering what # stands for, it signifies that, the particular line is commented out, and the system does not read it. You can use it add comments to the build.prop. This helps others understand, what is the function of a particular tweak.
A guide for some basic build.prop tweaks can be found here.
Please be aware that, these build.prop modifications are not universal. So, you will have to experiment with the tweaks and their values.
The META-INF folder
This folder contains instructions for the Android Recovery about how to work with the files present in the zip. This folder contains many folders, but the only one we need to edit is the update-script file.
Making Flashable ZIP
In order to create a flashable zip, first zip the ‘system, META-INF’ folder and the ‘boot.img’. Let’s name this zip as ‘update.zip’. Next we need to sign the zip. Get a signer here. Put your update zip in the same folder as the signer. Then run the ‘signer.bat’ file. This will sign your zip file. After the signing process is complete, you can change the name of the zip to your liking.
confused
hi,,,i'm new here,,,,
after reading ur post, actually i can't do this,,,
and i installed miui v5 rom and always find crashing about "android process stopped."
and i can't edit the rom or make update of it because of no jnderstanding it, but i like miui so far.
so, can u give me the link of miui v5 rom that not crash, in order to me just to instal it without editting.
thx so much.
gwesal said:
hi,,,i'm new here,,,,
after reading ur post, actually i can't do this,,,
and i installed miui v5 rom and always find crashing about "android process stopped."
and i can't edit the rom or make update of it because of no jnderstanding it, but i like miui so far.
so, can u give me the link of miui v5 rom that not crash, in order to me just to instal it without editting.
thx so much.
Click to expand...
Click to collapse
Checkout my miui thread I have already posted the original link there
D5+/cm11/1.2GHz.
Sent from Tapatalk app
coolshahabaz said:
Checkout my miui thread I have already posted the original link there
D5+/cm11/1.2GHz.
Sent from Tapatalk app
Click to expand...
Click to collapse
which one???
is it the official rom from miui site or edited rom you created??
actually its take too long doenloading from official site. but rom i doawnloaded is always crashing android.process.stopped.
gwesal said:
which one???
is it the official rom from miui site or edited rom you created??
actually its take too long doenloading from official site. but rom i doawnloaded is always crashing android.process.stopped.
Click to expand...
Click to collapse
The one I edited had that prob of crashing, n the one on official site is about 240mb ty its taking time
D5+/cm11/1.2GHz.
Sent from Tapatalk app
DISCLAIMER
Flash at your own risk.
INTRODUCTION
Hello everyone, This is my first time posting my own thread, I've been lurking around these forums since the release of Galaxy Note 1 (N7000) ,my first android phone. I've learnt to flash custom roms, root devices, etcetera. This is my first time I've extracted and repacked an apk file.
Anyways, I've learnt how to change the background wallpaper of the Smart Cover app whilst the cover is on the phone. I've used this site as my source; http://www.oppoforums.com/threads/m...-sfondo-per-le-custodie-easy-cover-etc.17149/
Credits goes to the author for the original apk and zip files. I am no app developer neither am I proficient in creating custom scripts or apk files. I just repacked the apk and zip files and replaced the jpg files located here:
\system\app\OppoLeather\res\drawable-hdpi\window_bg.jpg
\system\app\OppoLeather\res\drawable-xxhdpi\window_bg.jpg
The first 3 flashable files were created by the aforementioned author from the linked forum.
INSTRUCTIONS
I flashed this using the custom ROM, Kulay OS v1.1 on my Find 7a X9006, on CWM Philz Touch Recovery 6.42.2.
I believe you will not face any problem using the stock ROM on any Custom Recovery.
First download the attached 7zip file, then extract
Choose your preferred flashable zip based on the attached screenshots in this thread
Copy it in the internal/External SD card of your phone
Reboot into recovery
Perform a wipe cache and Dalvik-cache (you will not lose your settings and apps installed)
Select the zip file you downloaded earlier and flash
Reboot the phone
SCREENSHOTS/ DOWNLOADS
You may also click the pic for their individual download links
BG 01:
BG 02:
BG 03:
BG 04:
BG 05:
BG 06:
BG 07:
BG 08:
BG 09:
BG 10:
BG 11:
BG 12:
PS
I am using NILLKIN Thin PU Leather Smart Flip Pounch Cover Case for Oppo Find 7 X9007 if anyone asks.
Hi @leihuwan,
Can I include this work as an option during installation in Kulay ROM in my next release?
tantrums said:
Hi @leihuwan,
Can I include this work as an option during installation in Kulay ROM in my next release?
Click to expand...
Click to collapse
Of course!
PS
Give me a few minutes, I will update OP for more stuff
update
Updated OP for more backgrounds (07 to 12), included individual download links per pic via mediafire
Support 7s or not ?
Yes, it works wird 7s... I tested it in my x9076
Gesendet von meinem Oppo Find 7
Hi leihuwan,
Thanks for the fine work. Working fine on my 9076, but it doesn't wake the screen when i open the smart cover. I have to double tap to wake it. Although not a big problem, would be nice to see a fix for it.
Once again thank you.
P.S tried four of your mods and the problem persists on all of them.
Hey,
I love this, thanks a lot! I always use BG 01, it's perfect.
However, it does not wake the device anymore if you use the new ColorOS 2.0.0i
Will you fix this? I'd love to continue using it, but if it prevents the device from waking up I can't
Thanks for this !
Each one of them, so much nicer than the stock one...
Great job.
DonVito2020 said:
Hi leihuwan,
Thanks for the fine work. Working fine on my 9076, but it doesn't wake the screen when i open the smart cover. I have to double tap to wake it. Although not a big problem, would be nice to see a fix for it.
Once again thank you.
P.S tried four of your mods and the problem persists on all of them.
Click to expand...
Click to collapse
What version of ColorOS are you using? Have you tried setting screen lock to None at Settings > Safety & Privacy > Screen Lock?
MB48 said:
Hey,
I love this, thanks a lot! I always use BG 01, it's perfect.
However, it does not wake the device anymore if you use the new ColorOS 2.0.0i
Will you fix this? I'd love to continue using it, but if it prevents the device from waking up I can't
Click to expand...
Click to collapse
I am terribly sorry. Truthfully I am not a programmer and my knowledge in coding and packaging APK files is very limited. I only translated the instructions I've discovered at oppoforums seen at the link at OP. Maybe they changed something in the apk of the official ColorOS 2.0 release. If someone more knowledgeable than me is present, feel free to chime in.
leihuwan said:
I am terribly sorry. Truthfully I am not a programmer and my knowledge in coding and packaging APK files is very limited. I only translated the instructions I've discovered at oppoforums seen at the link at OP. Maybe they changed something in the apk of the official ColorOS 2.0 release. If someone more knowledgeable than me is present, feel free to chime in.
Click to expand...
Click to collapse
Alright, thanks.
I read what you did and fixed the problem myself since it's pretty easy.
I took the original OppoLeather.apk of ColorOS 2.0.0i and modified the background of it and put it in your .zip
This works without problems for me and the device now wakes up properly. Yes, they did some changes to it in 2.0.0i.
If anyone else wants it, in the attachment is a working flashable .zip for ColorOS 2.0.0i with Background picture 1 of the original post.
please help...
MB48 said:
Alright, thanks.
I read what you did and fixed the problem myself since it's pretty easy.
I took the original OppoLeather.apk of ColorOS 2.0.0i and modified the background of it and put it in your .zip
This works without problems for me and the device now wakes up properly. Yes, they did some changes to it in 2.0.0i.
If anyone else wants it, in the attachment is a working flashable .zip for ColorOS 2.0.0i with Background picture 1 of the original post.
Click to expand...
Click to collapse
I suggest you to make a tutorial review....please,I have no idea on how to do it.....appreciate your kindness.....
For me it's perfect like this...
Before that ,the screen went on even with a little opening of the cover .
Now,I decide when the screen goes on...
huffaz841 said:
I suggest you to make a tutorial review....please,I have no idea on how to do it.....appreciate your kindness.....
Click to expand...
Click to collapse
Find the oppoleather.apk (it's somewhere in the /root partition of the phone)
copy it to your computer
rename it from .apk to .zip
you can now open it with any zip browser.
Replace the window_bg.jpg in /res/drawable-hdpi and /res/xxhdpi with a picture of your choice.
Make sure your picture is also a .jpg, has the exactly same name and resolution.
After you replaced the pictures in the .zip you can close your file browser and rename the file into .apk
Your apk is now modified.
To flash it:
Download any of the flashable .zip's the creator of this thread put up.
when you have a flashable .zip open it.
In there will be the OppoLeather.apk and some other files. Replace the OppoLeather.apk with your modified .apk.
Make sure your apk has the exact same name as the one you're replacing it with.
After replacing you can close your file browser and copy the modified flashable .zip on your phone.
Now you only have to flash it (see instructions in first post).
Hi! I know this is an old thread, but I have a question concerning this little mod. I recently got the N3 and since the cover had a square window, the default easy cover window of the OPPO N3 is a circle.
So, I decided to flash one of the modified packages provided by the op and they work great. However, there is a slight misalignment - unsurprisingly - due to the resolution and size differences between the 7/7a and the N3. What I would like to know, is whether it is possible to to decompile and modify the apk, in order to place the small window screen a bit higher. I have decompiled the apk myself, but I haven't yet figured which string to modify.
A small help would be greatly appreciated!!!
Feregorn said:
Hi! I know this is an old thread, but I have a question concerning this little mod. I recently got the N3 and since the cover had a square window, the default easy cover window of the OPPO N3 is a circle.
So, I decided to flash one of the modified packages provided by the op and they work great. However, there is a slight misalignment - unsurprisingly - due to the resolution and size differences between the 7/7a and the N3. What I would like to know, is whether it is possible to to decompile and modify the apk, in order to place the small window screen a bit higher. I have decompiled the apk myself, but I haven't yet figured which string to modify.
A small help would be greatly appreciated!!!
Click to expand...
Click to collapse
You can do it manually with a root enable file browser.
Find the OppoLeather.apk in /system/app/Oppoleather, copy it into your phone storage then transfer it to your computer, open the apk with 7-Zip, navigate to find window_bg_circle (.png or jpg), extract it, modify the picture while keeping its dimensions, put it back into the apk, transfer the apk in your phone storage. With the file browser, change the suffix of the original OppoLeather.apk into .bak, copy the modified apk into the /system/app/Oppoleather folder, modify its permissions according to the old file (i.e. rw-r--r--). That's it.
Thanks on behalf of many owners here. It's rare to see someone reply to something in such a helpful manner and in plain english instead of abbreviated jargon