Database Develop

[INFO] List of Files NOT to Optimize

Hi all, I started this thread hoping that we can consolidate a list of files not to zipalign or optimize the PNGs within it. Personally, I use http://forum.xda-developers.com/showthread.php?t=560271 on my themes to optimize the apks within it.
So far:
VoiceSearch.apk - Do not optimize it using http://forum.xda-developers.com/showthread.php?t=560271, it will result in FCs. However, optimizing the PNGs, putting them back into the apk, and zipaligning it works fine (thanks to djengizz for testing). Probably due to the script repacking stuff wrongly?
HTC_IME.apk - Do not optimize it.
HTC_CIME.apk - Do not optimize it.
framework-res.apk - *May* cause problems. Did it myself with no issues but others are reporting it.
Other issues:
Settings.apk - Do not compress with highest compression using apkopt. Causes a problem with MetaMorph if you use it. Reported by djengizz. More info here: http://forum.xda-developers.com/showpost.php?p=5007059&postcount=17

Did you try to extracting the images, optimize them and put them back in the apk without repacking? I think repacking might be the problem here.
From my experience none of the Google apps like resigning so i only zipalign them. I haven't ran into any problems changing (or optimizing) the images in them as long as you don't repack.

djengizz: Have yet to try that, will do so when I'm taking a break from studying, exams soon . Thank you! I've optimized the rest of the Google Apps using the above script with no issues so far (except VoiceSearch).

I've just set the script to use the maximum compression (-mx9 instead of -mx5) and i get the same results. Everything is working fine except for VoiceSearch (FC's).
Transferring the optimized png's back to the original apk and zipaligning it (not signing) works and VoiceSearch doesn't FC anymore. You might want to try it using even less compression than -mx5 and maybe than it'll also work for VoiceSearch.

do not optimize framework and HTC_CIME. They can semi-brick your phone.

djengizz: Thanks for testing out and updating this thread! Does mx9 work much better than mx5?
JokerAce: Care to elaborate more? I've optimized framework with no issues so far...

Wysie said:
djengizz: Thanks for testing out and updating this thread! Does mx9 work much better than mx5?
Click to expand...
Click to collapse
Well, not much, a little bit.
The apk i used for testing went from 2.18 MB to 1.37 MB using -mx5 and to
1.34 MB using -mx9.

yeah- HTC_IME.apk didnt work for me either..

MontAlbert: Didn't work using the batch? How about optimizing the PNGs separately, putting them back into the zip, and then zip aligning them?

tried that and zipaligned it myself... but then somehow not all pngs went across so it isnt themed properly anymore..... it worked at least though.

Oh, when I optimized them, the phone was unable to load the system, and was stucked at the splash screen. When I installed by the previous file (before optimization) the phone was working again.

JokerAce: What did you optimize by "them"? Thanks !
MontAlbert: So does it work or not? Haha ^^.

"Them" refers to the framework_res.apk and HTC_CIME.apk

JokerAce: Ok, thank you. I honestly had no issues with framework_res.apk, and I've been doing some reading in the Dream themes forum. Most of them have optimized their framework_res.apk as well (although the method used isn't stated) with no issues. I'll still add it to the list, thank you!

Aww, I tried for the second time, to optimize the framework_res.apk, and it made my phone stuck at the splash screen. Guess, some phones can (like yours) and some phones can't (like mine).
I am recently changing loads of stuff in the apks and optimizing them. If I found anymore problems, I will contribute them over here.
Cheers

framework-res works perfectly for me every time.

I found another problem with apkopt.
I compress every apk in my theme using the highest compression except for VoiceSearch.apk and if i flash this everything works fine.
After applying a morph with MetaMorph on Settings.apk it got corrupted. I replaced the optmized Settings.apk with one that only contains optimized images and MetaMorph was working fine again.
For some reason something got corrupted when MetaMorph re-zipped the optizmized apk which doesn't happen when i don't use the high compression from the apkopt script.
BTW, this is not only related to MetaMorph: when pushing the apk manually it will also corrupt and Settings will give FC's whenever it's used. For some reason when you flash it, it does work...

djengizz: Interesting problem there! Thanks! Will update the first post. is there any chance it's related to MetaMorph and not apkopt?

Wysie said:
djengizz: Interesting problem there! Thanks! Will update the first post. is there any chance it's related to MetaMorph and not apkopt?
Click to expand...
Click to collapse
Nah, i don't think so cause manually pushing the optimized apk (without running MetaMorph) also gives FC's and the Settings item disappears from the launcher.
When i push the not optimized version it works fine.

Some new info:
Brut.all said:
BTW for all who are repackaging apks: don't use zip or jar commands for app packaging. Android is compatible with them only on a first sight, but in some cases, as above, it isn't. Use aapt instead.
And I haven't see such warning in Android docs :-/
Click to expand...
Click to collapse
Hope it helps . Taken from the Maps thread.

[GUIDE] Dummies guide to port MIUI rom for ideos X6 variant!

Lets discuss about ROM port guidance for dummies like me. Hope it will help others also who want to port it.
Here is my experience for porting several MIUI in my phone, shall other to make it perfect.
First we must have a source rom to port. Desire HD is my chosen since it has some similar hardware.
I replace the source rom using several files from the previous working MIUI rom.
I never mix framework with any other files from previous miui version, I just patch framework.jar and services.jar (decompile and recompile). And for system app files I let them as is, except for torch.apk taken from 1.11.11 and systemUI.apk with manual patch (decompile and recompile).
I use the same driver modules files in every my port (wifi, sensor, light, gps), the rest drivers are compiled in the kernel so we can't touch them except if we can build from source. I use almost the same library in every port. ( You can see the same files from my 2.2.3 and my 2.3.9)
The other files are came from the source dhd rom and additional apps taken from other rom or any mod as long as they're not accessing the hardware directly.
And for the kernel, lately I use SDKernel and mOCK kernel. I've modified both boot image of them. At 2.3.9 as you knew, I use modded SDKernel, I've change default cpu clock and also bringing up the fm radio service in it. And for my current miui (2.3.16) I'm using mOCK kernel, I've change the default cpu clock also, but not bringing up fm service (since I've not succeded yet using FM radio).
Here are some files I don't use from source rom (replace by following files):
- Torch.apk
- hciattach
- netd
- wpa_supplicant
- liba2dp
- libc****
- libcamera
- libcamera_service
- libffmpeg
- libgemini
- libhardware_legacy
- libmmipl
- libmmjpeg
- liboemcamera
- libril
- librpc
- libskia
- libwebcore
- vold
- vold.stab
- btwlancoex
- compassd
- geomagneticd
hci_qcomm_init
hostapd
hostapd_cli
lightd
load_wifi
modempre
netmgrd
nt_password_hash
oem_rpc_svc
orientationd
port-bridge
proximityd
pwgen
qmuxd
rmt_oeminfo
zipalign
all files from system/etc/firmware/wlan
some files in init.d script, I use just hostapd, tweak sdcard read and zipalign. The rest setting I let the default config.
init.qcom.xxx
loca_parameter.ini
wpa_supplicant.conf
all files from /system/lib/hw and /system/lib/modules from previous port ( taken from 1.11.11 and triumph if I'm not wrong... not exactly remembered)
libaudio***
libauth
libcm
libcommondefs
libdiag
libdll
libdsi_netctrl
libdsm
libdsmutils
libgsd**
libidl
libloc***
libmmgsdilib
libnetmgr
libnv
liboem_rapi
liboncrpc
libOpenVG
libpbmlib
libposteffect
libqdp
libqmi
libqueue
libreference-ril
libril***
libwms**
and also all file in /system/usr/keychars and /system/usr/keylayout
If I'll change kernel, then I'll change wifi lib also which work with it.
And add some addons... not related to the core.
wpa_supplicant.conf, gps.conf, build.prop are changed as needed
I think those files are sufficient to make a new port...
Tools to decompile and recompile apk and jar files is apktool, you can use apkmultitool from apkmultitool.com.
How to fix headset:
Decompile services.jar, use this command line;
apktool d services.jar
You'll find services.jar.out folder as output. Find HeadsetObserver.smali file and replace any "h2w" word with "headset_sensor". Use notepad++ to do it. And recompile using this command line:
apktool b services.jar.out
Find the new compiled file at services.jar.out/dist folder.
How to fix native wifi tether and haptic feedback:
The file need to modify is framework-res.apk. You can do the same to decompile and recompile just like fixing headset. Decompile the file and find array.xml in framework-res.out/res/values. Find "wl.0" replace with "softap.*". You'll easily find the level values pattern for haptic feedback in the same file. The pattern values is "off,on,off,on" format to turn off and turn on vibrate in milisecond. Recompile again.
The new compiled file can not be used yet, you should restore the META-INF folder and AndroidManifest file from the original framework-res.apk file. Use 7zip application to open both old and new framework-res.apk and drag META-INF folder and AndroidManifest file to the new compiled framework-res.apk then it ready to use.
Happy porting......!!!
I'll update this post if there are some more useful...
Any suggestion are welcome...

Thank you very much for this. Will surely help newbies like me

FR... I got an idea... if there is an app which will do just like your future release miui kitchen BUT it run in device, so it will have an OTA update, how cool....! I want to help to port it to an android app (apk file), but I just only have several hours in a week for this fun.

I have already scripted what you have written in the first post.
What needs to be done with the framework files?

Free Radical said:
I have already scripted what you have written in the first post.
What needs to be done with the framework files?
Click to expand...
Click to collapse
I think we have to let the original theme and standard apps, the customization is optional due to different need of users. (For example you and me could be like beat audio or maybe not).
For the headset, you have to decompile service.jar, open headsetobserver.smali (i forgot for the exactly name) and change every "h2w" word to "headset_sensor" then recompile, then headset will work.
Sent from my CSL-MI410 with my MIUI 2.3.16 using tapatalk

The kitchen app shall be ready in a day or two.
Shall experiment later when I return home.
Btw, what to change in the framework folder?
Also, you need to mention in your guide that the proprietary hw, keylayout,keychar, module files need to be preserved.
I have pmed zuk regarding his set of proprietary fih/fb0 files so that we can make a skeleton framework to be used for cooking every Rom.
Sent from my Spice MI-410 on my rom!

Free Radical said:
The kitchen app shall be ready in a day or two.
Shall experiment later when I return home.
Btw, what to change in the framework folder?
Also, you need to mention in your guide that the proprietary hw, keylayout,keychar, module files need to be preserved.
I have pmed zuk regarding his set of proprietary fih/fb0 files so that we can make a skeleton framework to be used for cooking every Rom.
Sent from my Spice MI-410 on my rom!
Click to expand...
Click to collapse
Service.jar is in framework folder FR. My prev post mention the change of this file.
Yes, any files in hw,modules,keychar and keylayout folder at the source rom should be deleted and replaced by files from the working rom.
The skeleton for other rom willbe different. You have to make different folder for skeleton files for different rom. Several are the same files, but separating them will make you easier to manage. So the list file names is not too important, just put them in the folder will be enough. Sorry .... Just my though...
Sent from my CSL-MI410 with my MIUI 2.3.16 using tapatalk

AND LADIES & GENTLEMEN... WE HAVE LIFT OFF!!!!!!!!!!!
REJOICE.
I have made an automatic miui rom porter.
I am calling the app F-CuK-R
Thank you CK, edowar, zuk and elol.
Just booted up 2.3.16 successfully. Ported using my app (Testing the rom it churned out. I am hoping native wifi tethering is fixed)
Shall upload after midnight.
Now we can have MIUI GB release the same day after every official release
Although I must confess a lot of the files I am using are missing in this post.
but fear not, I shall make them public as soon as the app is ready for prime time with a nice gui.
Made the list after several failed experiments over the last week. Finally a simple file comparison (using a script I made) between the official MIUI release and the original 1.11.11 release helped.

Free Radical said:
AND LADIES & GENTLEMEN... WE HAVE LIFT OFF!!!!!!!!!!!
REJOICE.
I have made an automatic miui rom porter.
I am calling the app F-CuK-R
Thank you CK, edowar and zuk.
Just booted up 2.3.16 successfully. Ported using my app (Testing the rom it churned out.)
Shall upload after midnight.
Now we can have MIUI GB release the same day after every official release
Although I must confess a lot of the files I am using are missing in this post.
but fear not, I shall make them public as soon as the app is ready for prime time with a nice gui.
Made the list after several failed experiments over the last week. Finally a simple file comparison (using a script I made) between the official MIUI release and the original 1.11.11 release helped.
Click to expand...
Click to collapse
Greaattt FR... Can't wait to taste it....!!!!
Sent from my CSL-MI410 with my MIUI 2.3.16 using tapatalk

I guess I spoke too soon.
My port again has an issue with the headset. :sigh: back to the drawing board

sorry FR, for not replying for your PM. I was away for internet for some time...!!
You have already done a really Good job. I should say, really quick...!!
This will real Good deal for MIUI lover's.
Good Luck...!!

Can someone enumerate changes to be done to systemUI, android.policy, framework.jar and framework-res in different mods so that I can script them for my cooker?
Sent from my Spice MI-410 on my MIUI 2.3.16 port

CacingKalung said:
Lets discuss about ROM port guidance for dummies like me. Hope it will help others also who want to port it.
Here is my experience for porting several MIUI in my phone, shall other to make it perfect.
First we must have a source rom to port. Desire HD is my chosen since it has some similar hardware.
I replace the source rom using several files from the previous working MIUI rom.
I never mix framework with any other files from previous miui version, I just patch framework.jar and services.jar (decompile and recompile). And for system app files I let them as is, except for torch.apk taken from 1.11.11 and systemUI.apk with manual patch (decompile and recompile).
I use the same driver modules files in every my port (wifi, sensor, light, gps), the rest drivers are compiled in the kernel so we can't touch them except if we can build from source. I use almost the same library in every port. ( You can see the same files from my 2.2.3 and my 2.3.9)
The other files are came from the source dhd rom and additional apps taken from other rom or any mod as long as they're not accessing the hardware directly.
And for the kernel, lately I use SDKernel and mOCK kernel. I've modified both boot image of them. At 2.3.9 as you knew, I use modded SDKernel, I've change default cpu clock and also bringing up the fm radio service in it. And for my current miui (2.3.16) I'm using mOCK kernel, I've change the default cpu clock also, but not bringing up fm service (since I've not succeded yet using FM radio).
Here are some files I don't use from source rom (replace by following files):
- Torch.apk
- hciattach
- netd
- wpa_supplicant
- liba2dp
- libc****
- libcamera
- libcamera_service
- libffmpeg
- libgemini
- libhardware_legacy
- libmmipl
- libmmjpeg
- liboemcamera
- libril
- librpc
- libskia
- libwebcore
- vold
- vold.stab
- btwlancoex
- compassd
- geomagneticd
hci_qcomm_init
hostapd
hostapd_cli
lightd
load_wifi
modempre
netmgrd
nt_password_hash
oem_rpc_svc
orientationd
port-bridge
proximityd
pwgen
qmuxd
rmt_oeminfo
zipalign
all files from system/etc/firmware/wlan
some files in init.d script, I use just hostapd, tweak sdcard read and zipalign. The rest setting I let the default config.
init.qcom.xxx
loca_parameter.ini
wpa_supplicant.conf
all files from /system/lib/hw and /system/lib/modules from previous port ( taken from 1.11.11 and triumph if I'm not wrong... not exactly remembered)
libaudio***
libauth
libcm
libcommondefs
libdiag
libdll
libdsi_netctrl
libdsm
libdsmutils
libgsd**
libidl
libloc***
libmmgsdilib
libnetmgr
libnv
liboem_rapi
liboncrpc
libOpenVG
libpbmlib
libposteffect
libqdp
libqmi
libqueue
libreference-ril
libril***
libwms**
and also all file in /system/usr/keychars and /system/usr/keylayout
If I'll change kernel, then I'll change wifi lib also which work with it.
And add some addons... not related to the core.
wpa_supplicant.conf, gps.conf, build.prop are changed as needed
I think those files are sufficient to make a new port...
I'll update this post if there are some more useful...
Any suggestion are welcome...
Click to expand...
Click to collapse
How do you decompile and recompile service.jar n framwork.jar???

nitin1978 said:
How do you decompile and recompile service.jar n framwork.jar???
Click to expand...
Click to collapse
I have added how to fix the headset, haptic feedback and native wifi tether at the first post including how to decompile and recompile files.
Happy porting....!!!
Sent from my CSL-MI410 using Tapatalk

thanks bro...

[Q] Does those network build.prop tweaks really work?

Hi Ladies & Gents
Just wondering, does the these build.prop tweaks work for the Note?
http://forum.xda-developers.com/showthread.php?t=1588439
- In particular the network related ones?
- If they do is there a reason why are they not included in the stock build.prop?
Thanks for helping me answer these questions

Bump any one?

altrstar said:
Hi Ladies & Gents
Just wondering, does the these build.prop tweaks work for the Note?
http://forum.xda-developers.com/showthread.php?t=1588439
- In particular the network related ones?
- If they do is there a reason why are they not included in the stock build.prop?
Thanks for helping me answer these questions
Click to expand...
Click to collapse
1.yeah build.prop tweaks does work.There are mant tweaks like making H/W UI rendering,making jpg quality 100%,increase the sppet of browsing by increasing the buffer rate etc...Yeah the network one works.And I have implemented some tweaks to my rom too...
2.Stock roms doesnt contain most of the tweaks/mods seen in custom roms...Thats what differentialtes stock and custom roms....

Thanks for the response! I'll give it a shot and see
BTW: just a note guys if you edit the build.prop in es explorer make double sure you change the settings of the file back to rw-r--r-- or your going to get a nice black screen on boot!

altrstar said:
Thanks for the response! I'll give it a shot and see
BTW: just a note guys if you edit the build.prop in es explorer make double sure you change the settings of the file back to rw-r--r-- or your going to get a nice black screen on boot!
Click to expand...
Click to collapse
You may use this way:
1.pull your build.prop from /system to your pc
2.open it in notepad++
3.Edit the file.you may copy paste from the thread in op
4.make a cwm zip
5.flash in recovery
No need to worry about perms...

Editing build.prop via recovery flashable zip

I an looking to edit the build.prop file and I have no idea on how to edit existing lines as well as add new lines. I've tried searching and I can't seem to find a decent answer.

No offence, but if you have no idea on how to edit the build prop, then you shouldn't edit it at all
That said you should install Build prop editor from play store. It's a free app from JRUMMY.
Sent from my HTC One using XDA Premium HD app

Editing build.prop is very easy. But to understand it better you should google around for a guide that shows what each line means and what lines can be modified for your device. I also suggest that you don't delete any lines depending on your rom and instead add any tweaks you may want.

[3.0.0 beta] EVilTheme: VRTheme Reborn

About
Eviltheme (Enhanced VillainROM Theme Engine) is an Android system modification platform meant for use with custom Android recoveries.
It allows modification of application resources without the need to replace the whole app or install a new operating system.
Eviltheme is based on the VRTheme Engine from 2011, though versions 3.x.x and up heavily differ from the original VillainROM code.
Disclaimer
Eviltheme is provided to you without warranty. You are free to try it on your device, but you are doing so at your own risk. I will not be responsible for bricked devices, wiped devices, etc.
Features
Automatic systemless mode with version 3.x.x+ (Magisk required, version 13.1+ recommended)
System mode fallback in case Magisk is not present
Supports both Dalvik and ART platforms
Smart bytecode refresh (delete classes.dex/classes.art only if it is replaced by the theme)
Easy uninstallation via automatically generated flashable ZIP or through Magisk Manager (if installed systemlessly)
Delete files (even inside APKs)
Support for pre/post-(un)installation scripts
Support for dual /system partitions
Downloads
Latest beta: 3.0.0-beta4
Last 2.x release (no systemless support): 2.0.6
Changelogs
GitHub
Documentation
Second post
Help
Third post
Credits
The VillainROM team
@djb77
@Spannaa
@topjohnwu
Source code (GPLv3)
Eviltheme main repo
Eviltheme restore ZIP repo

Documentation
Things to remember​
Compile your res/smali/etc files first before you put them in your theme! You can use APKtool for that, then just extract the files from the resulting APK.
Theming user apps is not supported, because modifying the contents breaks the signature.
Remember to properly edit .9.png files, or else you might get a bootloop!
You do not need to put theme files in a subfolder inside the main APK folder, e.g. /system/priv-app/SystemUI/SystemUI.apk. EVilTheme automatically does that for you.
Do I need to download the official Magisk module template?​Nope! EVilTheme includes post-fs-data.sh, service.sh, and system.prop. Look for them in META-INF/tk/aureljared/magisk-common and edit them to your liking. The module.prop is automatically generated from information you put in eviltheme.prop.
In the event that the official module template is updated, I will update EVilTheme to ensure compatibility as soon as I can.
How do I theme an app (or apps) using EVilTheme?​Inside the ZIP, there are three folders that you can modify as needed; namely, data, system, and vrtheme.
Your patches/theme files go in vrtheme, while APK files that you want to install onto the device go in data and system.
For example, you want to theme Settings.apk, which is located in /system/priv-app.
Let's say your theme replaces res/drawable-hdpi/battery_icon_50.png in the APK, and also replaces classes.dex because you changed some smali files.
These are the steps you need to follow to make a flashable theme ZIP:
Ensure you've downloaded the appropriate template ZIP. Make a folder somewhere you can remember and extract the ZIP there.
The folder should now contain the folders META-INF, data, system, vrtheme, and a file called eviltheme.prop.
Open eviltheme.prop in a text editor (please use Notepad++ if you are on Windows!) and add your theme information there.
In the vrtheme folder, go to system and make a new folder called priv-app. Inside it, make another folder called Settings.apk. Make sure you capitalized correctly!
Now make folders as necessary, according to the location of the files you want to theme. For example, battery_icon_50.png is located in res/drawable-hdpi, so make a folder named res inside Settings.apk. Inside it, create a folder named drawable-hdpi, then paste your new battery_icon_50.png inside.
Repeat step 5 until you've placed your theme files in their appropriate locations.
When you're done, go back to the root folder of the theme (the one that contains new, vrtheme, etc.) and put all 5 objects in a ZIP file. You should use Deflate compression method only. Any compression level will work.[/u]
If the recovery that the theme is intended to be used with requires signing, sign the ZIP now.
Test your theme! :victory:
How do I uninstall a theme?​If the theme was installed systemlessly, remove it in Magisk Manager.
Otherwise, flash the relevant zip in /data/eviltheme-backup.
How do I delete files inside APKs to be themed?​To delete files, add the filenames to a text file named "delete.list" inside the APK theme folder.
This is an example of a delete.list:
Code:
res/drawable-hdpi/ic-launcher.png
res/drawable-xxhdpi/battery_full.9.png
How do I delete files that aren't inside APKs?​You will also need a "delete.list". Remember to use full paths:
Code:
/system/app/Bloatware/Bloatware.apk
/system/etc/hosts
Put that in the "vrtheme" folder.
How can I exclude deleted files from being backed up?​Eviltheme versions 3 and up will automatically back up files that your theme deletes (in non-systemless mode).
To exclude a file, add "no-backup" to the end of the corresponding line in vrtheme/delete.list.
Code:
/system/app/Bloatware/Bloatware.apk [B]no-backup[/B]
How do I force installation on /system?​Eviltheme versions 3 and up will automatically install in systemless mode with Magisk 13.1+, but if you want to force your theme to install to /system, create a file named .eviltheme-force-system (notice the preceding dot) in /sdcard before installing.
I need to execute some commands during the theme (un)installation.​Inside META-INF/tk/aureljared/eviltheme, there are files named "pre-install.sh-example", "post-install.sh-example", "pre-uninstall.sh-example", and "post-uninstall.sh-example". Remove the "-example" part from the file name of your desired script, and edit that file in the text editor (please please please use Notepad++ if you're on Windows).
Use the comments in that file as a guide.

Help section
The theme wasn't successful, and I believe that the problem lies in the engine itself.​Post here describing the problem. Be as descriptive as possible. I will ignore all bug reports without an attached logcat dump and/or recovery.log. I'll try to look into the problem when time permits.
I am just a student, not a full-time developer. I may not be able to provide a fix for some bugs, so feel free to help me and everyone else out. If you know how to work with Git, an upstream patch to the project would be highly appreciated :good:
The theme was / wasn't successful, but I am stuck in a bootloop.​Try wiping your Dalvik cache. If the problem is still there, uninstall the theme and post a bug report in this thread. Include the relevant /cache/recovery.log and the theme you installed.
The theme was successful, but the app I was theming does not reflect my changes.​This is a tough one to solve. Try recompiling the APK itself with your theme files. If it works, it's either the problem lies in how you put the theme files in the ZIP, or maybe it's the script that's buggy. Try to make a ZIP again, following the instructions to the letter. If it still doesn't work, you can file a bug report here and attach your logcat dump, recovery.log, and (if you want) the themed APK.
The theme was successful, and now I'm ready to release my theme to the public.​All I ask for is some credit and a link back to this thread. :fingers-crossed:
The theme wasn't successful, and I found a problem in your engine script(s).​If you're familiar with Git, you can make a pull request to the EVilTheme repository.
If you don't know how to use Git, you can just edit the script(s) you need and send me a PM containing the fixed script(s). I'll add you to the credits list in the first post if your bugfix is effective!

Great work :good:
I particularly like the smart selective dalvik-cache wiping
Maybe it could be even smarter if the script only wipes an apk's dalvik-cache if the apk has had it's classes.dex replaced by the theme...
I'm working on something like this myself but mine is based on the unreleased GS2XFormROM by @hawkerpaul
I'll throw you a link when it's ready

Spannaa said:
Great work :good:
I particularly like the smart selective dalvik-cache wiping
Maybe it could be even smarter if the script only wipes an apk's dalvik-cache if the apk has had it's classes.dex replaced by the theme...
I'm working on something like this myself but mine is based on the unreleased GS2XFormROM by @hawkerpaul
I'll throw you a link when it's ready
Click to expand...
Click to collapse
Let me know if you need any help on the scripting side of things butty.
Sent from my GT-I9505G using XDA Free mobile app

hawkerpaul said:
Let me know if you need any help on the scripting side of things butty.
Click to expand...
Click to collapse
I will - cheers mate
Got it working but I'm sure you'd do a better job - .sh scripting isn't my thing at all.
Apologies to the OP for the OT...
Sent from my GT-I9300...

Spannaa said:
Great work :good:
I particularly like the smart selective dalvik-cache wiping
Maybe it could be even smarter if the script only wipes an apk's dalvik-cache if the apk has had it's classes.dex replaced by the theme...
I'm working on something like this myself but mine is based on the unreleased GS2XFormROM by @hawkerpaul
I'll throw you a link when it's ready
Click to expand...
Click to collapse
Hmm, yes I think I'll implement this in v1.1. Thanks for the suggestion!
Sent from my GT-I8730 using Tapatalk

Version 1.1 released!
v1.1: Link
What's new?
- Even smarter Dalvik wiping: delete dex files only for those apps whose classes.dex were changed (thanks @Spannaa)
- Corrected a typo in the restore script (please delete 'restore-vr' inside your /system/xbin, if any!)
- Removed unused methods in installtheme.sh
Click to expand...
Click to collapse

aureljared said:
Version 1.1 released!
v1.1: Link
Click to expand...
Click to collapse
How about making this TWRP compatible too - then it'd be even more useful
Reference 1
Reference 2

Spannaa said:
How about making this TWRP compatible too - then it'd be even more useful
Reference 1
Reference 2
Click to expand...
Click to collapse
Version 1.2 released!
v1.2: Link
What's new?
- Refinements to Smart Dalvik Wipe
- Switch to Linus Yang's BusyBox 1.21.1, which will hopefully make theming TouchWiz < 4.2 possible
- TWRP compatibility: switch to a static zipalign binary, grep method for OUTFD to look for updater binary
- Cleaner zip hierarchy: new apps to be installed to /system and /data are now in their respective folders in a folder named 'new'
Click to expand...
Click to collapse
Sent from my GT-I8730 using Tapatalk

aureljared said:
Version 1.2 released!
v1.2: Link
Sent from my GT-I8730 using Tapatalk
Click to expand...
Click to collapse
Very good job on this...one thing, in kitkat 4.4.2 touchwiz roms half of the apps that need to be themed are in /system/priv-app. This folder location does not seem to be in your installtheme.sh script. I can manually change everything myself but if you would like other users to take advantage of your work, you may want to consider updating for these users.

deuce_biggins said:
Very good job on this...one thing, in kitkat 4.4.2 touchwiz roms half of the apps that need to be themed are in /system/priv-app. This folder location does not seem to be in your installtheme.sh script. I can manually change everything myself but if you would like other users to take advantage of your work, you may want to consider updating for these users.
Click to expand...
Click to collapse
Oh right... How could I forget Am working on this now.
Thanks for the heads-up!

Version 1.3 released!
v1.3: Link
What's new?
- Support for KitKat's system apps in priv-app
Click to expand...
Click to collapse
Silly me, forgetting this while using a KitKat ROM

aureljared said:
Version 1.3 released!
v1.3: Link
Silly me, forgetting this while using a KitKat ROM
Click to expand...
Click to collapse
Nice work aureljared, the quick response and update is much appreciated :good:

Thank you @aureljared, deuce_biggins pointed me here, and I must say nice work to you.. Thank you

I tried to vrt a data/app, and it may have broke the signature.. It did theme the app, but it was no longer visible/available in my app drawer.. I could see the themed icon in data/app tho.. I don't think the original VRT could theme in data/app either... I did use your new version 1.3 with twrp on my Galaxy Tab 3, so that is good news.. It also made two folders on my internal sd, one was for data/app and one for system/app.. It did make a copy of the apk it themed in data/app, and placed it in the folder on my internal sd . I will test this on my Note 3 with twrp later..Thank you

aureljared said:
Version 1.3 released!
v1.3: Link
Silly me, forgetting this while using a KitKat ROM
Click to expand...
Click to collapse
cerj said:
I tried to vrt a data/app, and it may have broke the signature.. It did theme the app, but it was no longer visible/available in my app drawer.. I could see the themed icon in data/app tho.. I don't think the original VRT could theme in data/app either... I did use your new version 1.3 with twrp on my Galaxy Tab 3, so that is good news.. It also made two folders on my internal sd, one was for data/app and one for system/app.. It did make a copy of the apk it themed in data/app, and placed it in the folder on my internal sd . I will test this on my Note 3 with twrp later..Thank you
Click to expand...
Click to collapse
@aureljared, just curous...to follow up on with what cerj said, have you ever successfully themed an app inside of /data/app with your VRT? Seems to kill the app every time, your thoughts?

deuce_biggins said:
@aureljared, just curous...to follow up on with what cerj said, have you ever successfully themed an app inside of /data/app with your VRT? Seems to kill the app every time, your thoughts?
Click to expand...
Click to collapse
No, I only tried it with the old VRTheme, and it didn't work either (no icon in drawer). I don't think it'll work on EVilTheme either as I haven't changed the process of /data/app.

aureljared said:
No, I only tried it with the old VRTheme, and it didn't work either (no icon in drawer). I don't think it'll work on EVilTheme either as I haven't changed the process of /data/app.
Click to expand...
Click to collapse
Do you even think it's possible?

deuce_biggins said:
Do you even think it's possible?
Click to expand...
Click to collapse
It could be possible, if we can find a way to go around the sig verification. Or perhaps it just needs a Dalvik wipe, I don't really know [emoji26]