Database Users

[Guide]Solving T-Mobile Engine/Cyanogenmod Theme "IMPROPERLY COMPILED" error

[Guide]Solving T-Mobile Engine/Cyanogenmod Theme "IMPROPERLY COMPILED" error
If u r using Cyanogenmod or Metamorph then u might see an error "THEME IMPROPERLY COMPILED" while applying some themes... Sometimes it might get fixed by just restarting the phone but many times it doesnt... There is a simple fix for this...
Requirements:-
1. Windows PC
2. Java Installed
Get one from here...
http://www.java.com/en/download/manual.jsp
3. apktool
Download here http://www.multiupload.com/OV96GE5JOL
4. Autosign Tool http://www.mediafire.com/?recnmyzergg
5. .apk file of the theme which you want to make work (there are many tools to create apk file of apps you downloaded like Astro file manager or Estrong file manager)
Huh.. That was quiet simple...
Procedure:-
1. Install the java you downloaded
2. Extract the apktool & autosign you downloaded (i assume you extracted it on desktop for convenience)
3. place .apk file of the theme in the same folder where you extracted apktool & rename it to something simple like theme.apk (in my case it is desktop/apktool)
4. open command prompt (type cmd in run)
5. Go to the location with command prompt where you extracted the apk tool
(in my case type cd desktop)
6. then type cd apktool ( I assume there is no sub folder inside apktool folder)
7. Now type apktool d theme.apk
It will process some files and in less then a minute it will be completed
8. Now type apktool b theme
9. Open the folder apktool on desktop (with windows explorer and not with cmd)
Go to folder "Theme", Open folder "dist"
10. Copy the file "theme.apk" inside dist folder and paste it in autosign folder on desktop (which you extracted earlier)
NOTE:- There shouldn't be any other .apk file except theme.apk in autosign folder)
11. Now open sign.bat and press any key to sign the app...
YOU ARE DONE
A file will be generated with name "your_app_signed.apk" copy this to your phone and install this (obviously after removing the theme which was giving error)
Now it should work without any problems..
NOTE:- In theme manager you wont get display image of the theme instead you will get a black coloured image with name @string/theme_name....
This is the theme you just installed (I dont know y no image is shown in display after recompiling)
IT MIGHT SEEM A DAUNTING TASK FOR THE BEGINNERS BUT IN SHORT WHAT I HAVE DONE IS EXPLAINED YOU THE WHOLE PROCESS IN DETAIL OF DECOMPILING & COMPILING THE APK FILE AND THEN SIGNING IT

Alternative
Thanks for solution friend, u can also add this aternative fix to ur post.
Download LCD densiy modder pro. change dpi to 140 reboot. install theme & apply. change dpi to default reboot. OK
Tested number of times on many roms, and works fine...
Found here: http://lavabite.blogspot.in/2012/10/cm-theme-chooser-fix-for-theme.html

AmAnzx said:
Thanks for solution friend, u can also add this aternative fix to ur post.
Download LCD densiy modder pro. change dpi to 140 reboot. install theme & apply. change dpi to default reboot. OK
Tested number of times on many roms, and works fine...
Found here: http://lavabite.blogspot.in/2012/10/cm-theme-chooser-fix-for-theme.html
Click to expand...
Click to collapse
Actually changing screen density changes the overall screen perspective, so its not good to recommend it, everything looks too small

fundoozzz said:
Actually changing screen density changes the overall screen perspective, so its not good to recommend it, everything looks too small
Click to expand...
Click to collapse
After applying theme returns to 160 dpi and everything looks normal.

Whenever I try to apply the 140 DPI setting, my boot screen screws up and I'm stuck in a boot loop. Running unofficial JB ROM on LG Phoenix. Any suggestions?

SiberianLeopard said:
Whenever I try to apply the 140 DPI setting, my boot screen screws up and I'm stuck in a boot loop. Running unofficial JB ROM on LG Phoenix. Any suggestions?
Click to expand...
Click to collapse
idk this error hapens on my thrive (same as phoenix) when im runing 4.2.1 cm10.1
why dont they work without the stupid fixes, the themes should work without them

change background settins

would like to change the background of my roted Note 3 SM-9005 (settings, phone, sms, etc)
from
- Black Background with white fonts
to
- White or light Background with Black fonts
In doing so I have played with Xposed and Xbackground module, but I only was able to change background, NOT fonts.
Can somebody else share his experience?
Thank you
Saulo

I am willing to use a light themed ROM instead of my current one, but I found none
And yes, I do NOT care if the white background drains the battery: better short battery than unusable device (at least for my aging eyes...)
Thank you for any suggestions
SA

I found this:
http://galaxy-note2.wonderhowto.com...ckgrounds-your-samsung-galaxy-note-2-0147944/
But it works only partially: there are NO apps or mods available to exploit Xposed in order to achieve the revert of the colors.

I also found this:
http://forum.xda-developers.com/showthread.php?t=2281611
But I am not a techie...to complicated.
I would even pay someone to code those lines into an app:
...
from: http://forum.xda-developers.com/showthread.php?t=2281611
First download framework-res.apk from here: http://www.mediafire.com/?aaxgspj95aqj9nf
1. open the framework.apk with 7zip
2. Navigate to res/drawable-nodpi
3. Delete the file named background_holo_dark.png. it should be the very first one
4. Now choose any image and resize it to 512x512 using a photo editing software
5. Rename the chosen picture to background_holo_dark.png
6. Place it in res/drawable-nodpi
7. Now close 7zip and place the framework.apk onto your sd card
8. Now using root explorer copy the framework.apk into system/framework. ( remeber to delete the old framework.apk from the framework folder)
9. Change its permissions to rw--r--r
10. Reboot your phone
Thank you

no reply?

Tweak theme without computer

I don't spend lots of time at the computer, so I like to find ways to do as much as possible on the phone. One thing I've found is that every theme I try has at least one element I wish I could change, as much as I like it overall. I don't know enough to make my own theme, but I found a way to change elements of the theme without using a computer. I'm sure this is not news to many of you, but I figured there might be other non-experts like me out there who might appreciate it.
1. Download Apktool apk file below, install it, open it, {it will automatically update on the first use for some reason}, go to settings and check 'device has root', {leave other settings alone}, then close the app, reopen and grant su access.
2. Make a directory in storage somewhere called 'apktool', {or something}, and copy the following to it: /system/framework/framework-res.apk, /system/framework/SemcGenericUxpRes/SemcGenericUxpRes.apk, and whatever themes you want to mix and match.
3. Open apktool app, navigate to apktool directory, and import the framework files by tapping on each one and selecting 'import as framework'. When done, you can then tap on the theme apk files and select 'decompile all', and they will be decompiled into folders called {appname}-src. Go into the folders with a root explorer and change what you want, then go back to apktool, and tap on the folder you want and choose 'recompile'. When recompile is done you end up with an apk called '{appname}-src.apk'. Tap on that and choose 'sign'. When done you will get an apk called '{appname}-src-sign.apk, which you can install normally.
-Notes, questions-
- I'm currently using Z1c stock .236 deodexed rom. This app should work on other phones, roms, versions, etc, but I can't say for sure. What I know is that there are at least 5 versions of the app out there, {Google search for 'apktool 4.4' or '5.2', etc}, and it seems like each one works better on certain versions of Android. There are also configurable settings. If you have a different phone or rom, etc, you just have to mess around with it.
- This app should work as normal apktool for modding systemUI and framework, but I can't get it to recompile on LP, but only on Kk. Decompile works fine, but on recompile it complains about lacking resources. I don't know what file it wants. If someone can figure it out that would be great.
-If you don't know what files to change, all I can say is that I didn't either. Start with the obvious stuff, like navbar keys, and see how brave you get. Just make sure your file names are changed, since every app doesn't use the same names for the same files. As long as you work with copied files you have nothing to lose. If something is wrong with your modifications, then it won't recompile correctly, and you'll just get an error message, so you can't really install something that's going to mess up your phone.
- This also works for changing appearance of other apps, not just themes. See my recent posts in the Naked Browser thread for examples. However, sometimes it won't be able to decompile an app, and there's probably nothing you can do. I think the way apktool works is based on how the app was created. If something is not compatible, it just won't work.
- You don't have to decompile just to pull files out of an apk, but you do need an app that can do it. I use Rom Toolbox Pro. There may be free ones, {maybe Mixplorer}. I think you can just change the extension to zip and extract normally. However, some files and folders are not the same zipped in the apk as they are when decompiled.
File link - https://drive.google.com/file/d/0B5E7sFT1phjoS003R0tkM21qUlk/view?usp=docslist_api

Nice tutorial bro :good:

Thank you very much!
Sent from my D5503 using XDA Free mobile app

Since sharing themes with others' work is not kosher, (http://forum.xda-developers.com/crossdevice-dev/sony/share-frankentheme-t3282360), I figured I'd add a little more here for anyone's personal use. In general, here's what I've found with these themes:
- Within each apk there is an 'assets' folder, which contains zip files. Each zip file mods a certain aspect of the ui. For example, there will be one for settings, which contains the little pictures next to each settings option, (personalization, with the little rainbow, etc). You can experiment with simply swapping these around with different themes. However, if you want to add a settings zip, for example, to a theme base that does not already have a settings zip in it, you have to mod the main android manifest file in the top level of the apk. If you want to see how it needs to be modded, look at one that has it already. It's pretty obvious, since it's the same entry for each zip, but with the corresponding zip name. You can also extract these zips and replace files in them and rezip. Keep in mind, though, that there are some things that aren't that simple and just won't work.
- There are some things that are coded in, and can't be changed, (as far as I can figure out), like accent color. It seems like accent color just comes with the 'android' zip, and there's nothing you can do about it. As a workaround, you can find an 'android' zip with a color you like, and change out the other files from the zip you wish you could change the accent on. Again, sometimes it just won't work and you won't know why.
- Some themes don't follow this pattern at all. I haven't learned much about them yet.
Screenshots show examples I've used...

[stock] Cm launcher with auto-rotation - no computer needed

Need root. Tested on Z1c with stock deodexed rom.
1) Flash this port, (not my work) - http://forum.xda-developers.com/moto-e/themes-apps/app-cm12-1-trebuchet-rom-t3145576 Now you can use Trebuchet on stock rom.
2) Install apktool for Android here - http://onhax.net/tag/apktool-for-android-5-2-0-apk Choose the right version for your phone. I'm using Z1c, so I installed 'arm7'. After installed, go to settings and check 'device has root', then close the app, and reopen to grant root access.
3) Using a root browser, make a directory in storage somewhere called 'apktool', {or something}, and copy the following to it: /system/framework/framework-res.apk, /system/framework/SemcGenericUxpRes/SemcGenericUxpRes.apk, and Trebuchet.apk, (from the zip you flashed).
4) Open apktool, go to apktool directory, and import all 3 files as framework, by tapping them and choosing the option. Now you can decompile Trebuchet, and you should get a folder called Trebuchet-src.
For auto-rotation - go to /res/values/bools.xml and change 'false' to 'true' in the 'allow rotation' line.
For other tweaks - poke around and figure some stuff out. I was trying to change the background in the app drawer, since I don't like the white, and you can see in screenshots that I changed the background behind the background, but the white is still there around the apps. I did it by changing a color value in 'colors', then adding a line in 'apps_customize_pane', but I haven't figured out the other layer. I think it might be in smali somewhere. I also changed the background in Trebuchet settings.
After saving changes, open apktool app and tap on the Trebuchet-src folder and choose 'recompile'. You should get a new apk called 'Trebuchet-src.apk'. Then tap on that, and choose 'sign', which will create a new apk called 'Trebuchet-src-sign.apk', which you can install normally. Note that you might get an error message on recompile about default translation. Don't worry about it; as long as there is a new apk created, it should be fine.
{Mods: I know I'm not a dev, and I was going to just post in Z1c general, but it seems like it may apply to 'cross-device', so I figured I'd give it a shot. Please judge as you will}

Found a couple more layers...

Got it, (kind of - it's a hack)...

This was an old post so not sure it still applies..found it while searching.
Might be a stupid question..but
Does CM Launcher not work in landscape mode? It's not rotating and no setting for it. Can't imagine it doesn't in 2018..
What am I missing here?

Modifying the layout of the Joying Radio app

Modifying the layout of the Joying Radio app.
version 0.2 See changelog at the bottom of this post.
This works in essence for most apks. There are some differences where the layout is defined in xml files or in json files.
Requirements:
java runtime version 7 or better.
apktool: (https://ibotpeaches.github.io/Apktool/)
Editor that handles unix LF correct. Any linux or Mac OS/X editor will do. Notepad on Windows does NOT. On Windows use Notepad++: (https://notepad-plus-plus.org/download/) for example.
Optional: ApkPack: (http://mirrors.gtxlabs.com/joying/3_Misc_Tools/ApkPack/)
Read(!!) the basic apktool Basic, Decoding, Building: (https://ibotpeaches.github.io/Apktool/documentation/) documentation to get a general understanding for the apk structure. It's about 1½ page and prevents a lot of questions.
Knowledge of working in a terminal / command box (some people still call this a DOS-box). These actions are not done using a nice graphical interface/program.
Installation of requirements:
Java: Either use Sun java: (https://www.java.com) for all platforms, Openjdk: (http://openjdk.java.net) for linux, or Mac OS/X's own java version (make sure it is version 7 or better)
apktool: See here: (https://ibotpeaches.github.io/Apktool/install/)
ApkPack.exe: This one can be used to pack/unpack the Allapp.pkg. This allows you to get the apks. Another option is to "adb pull" the original from your unit to work on.
apkPack is a windows binary but runs fine under wine.
General note
An apk file is actually nothing more than a zip file. This means that you can also unzip/rezip an apk. For only modifying buttons and other graphical elements, this is sufficient. When you also want to modify the layout of the main screen or sub-screens, you really need apktool to decompile/compile. If you want to do minor code changes, you also need apktool. (Also a java jar file is also nothing more than a zip file).
Note for Windows users
Text files contain lines (obvious). These lines end with CRLF ("\r\n") line endings on Windows (and MAC versions before OS/X). On linuxes/unixes they end with "\n".
For some files inside an apk this really matters! That's why you need an editor that can handle that correctly, like for example Notepad++.
Android is Case sensitive! Uppercase and lowercase characters do matter and are different (unless when used in strings)
Getting the radio apk
Copy one of my radio mods.
Use ApkPack.exe to get the apk out of the Allapp.pkg.
Use adb to copy the apk from the unit like "adb pull /system/app/JY-1-C9-Radio-V1.0/JY-1-C9-Radio-V1.0.apk ." (the last "." is not a typo). This assumes you already made a connection via USB or tcpip
Download the apk from "http://mirrors.gtxlabs.com/joying/1_Firmware/".
Install framework-res for use in apktool
This step might not be necessary for the radio apk, but is necessary if you modify apks that use system functions. It's anyway better to do this step.
Every Apktool release contains internally the most up to date AOSP framework at the time of the release. This allows you to decode and build most apks without a problem. However, manufacturers add their own framework files in addition to the regular AOSP ones. To use apktool against these manufacturer apks you must first install the manufacturer framework files.
Inside the 5009_60.zip (or previously the 5009_20.zip), you will find inside "/system/framework" the "framework-res.apk". Extract that one from the zip.
In a terminal window, you do on the command line:
Code:
<path_to>/apktool if <path_to>/framework-res.apk
You need to do this step for every new ROM upgrade from Joying.
Decompile the apk
Create some folder where you want to work on the apk.
Inside that folder do inside a terminal:
Code:
<path_to>/apktool d <path_to>/JY-JY-1-C9-Radio-V1.0.apk
(Change forward slash "/" to backward slash "" on windows.).
This will create a folder "JY-JY-1-C9-Radio-V1.0" containing the decompiled apk including the from-binary-to-UTF-8 text converted AndroidManifest.xml.
Code:
AndroidManifest.xml (file)
apktool.yml (file)
assets (folder containing "all kind of things" needed by the apk, but not belonging to the standard res structure. This can be images, files, scripts or even other apks)
original (folder containing original AndroidManifest.xml)
res (folder containing layout, graphics, translations, etc.)
smali (folder containing the decompiled code in "smali" format)
The "res" folder contains a large amount of sub folders.
The three most important folders are:
Code:
drawable-land-nodpi-v4 (contains resolution unspecific graphic elements for landscape mode)
drawable-nodpi-v4 (portrait version of above. Only needed because the original apk contains a corrupt png and can't be recompiled)
raw (contains screen config/layout in json formatted files. Most apks have the config/layout in straight xml)
Initial steps when using the original apk
When using the original apk (instead of one of my mods), you need two extra steps:
- Copy the "ic_point.png" from the folder "drawable-land-nodpi-v4" to the folder "drawable-nodpi-v4". As mentioned: that png is corrupt in the original "drawable-nodpi-v4" which makes that you can't recompile the apk.
- You need to make a small code change in smali to get rid of the "PS:" prefix in front of the PS-text containing the station name.
Edit the "smali/com/syu/radio/RadioController.smali" in a good editor! (NOT Notepad).
Search for the string "PS:" which is in line 1557.
Change:
Code:
const-string v3, "PS:"
into
Code:
const-string v3, ""
Relation between the graphical elements and the layout definition
All the graphical elements like buttons, the frequency ruler and numbers for the (big) frequency are in "res/drawable-land-nodpi-v4".
The layout definition is in "raw/radio_ui.json". The "radio_ui.json" determines which graphical elements are used, and how and where they are positioned. The "radio_ui.json" also determines which texts in which font and font size are used and where they are positioned.
Examples:
The big frequency ruler is named "type":"HorizontalRuler" in the radio_ui.json and defined by the graphical element "drawables":["bk_ruler"], where "bk_ruler.png" is the image. Note that in the json file no extensions (.png) are used.
The "type":"StationView" determines the 6 buttons with inactive (unselected: *_n), active (current selected: *_p) and "on_click/on_tap" (*_p) state. Note also that you will find a ' "extras":[30,0,0,0],' in these sections. This will offset the x-postion 30 pixels to the right. If you want to center the text, change it to: "extras":[0,0,0,0],
The Frequency numbers and the buttons left/right around it. The frequency numbers are the images "num_0.png" to "num_9.png", plus the "num_point.png". The buttons left/right are the "drawables":["ic_freqm_n", "ic_freqm_p"] (down) and "drawables":["ic_freqp_n", "ic_freqp_p"] (up).
The PS, TA, AF, PTY etcetera can easily be found. These do not contain "drawables" (images), but are defined by textsize and text color.
All elements are positioned in a "X0,Y0,X1,Y1" or "top_left_X, top_left_Y,bottom_right_X, bottom_right_Y] rectangle.
Actually this is all.
You can play with it to change the layout.
If you want to change color or form of buttons, ruler or other elements, you have to modify exiting elements or create new elements in either Gimp or Photoshop or another package you are familiar with.
Note1: most PNGs are stored in "optimized" color mode (only store used colors) instead of "RGB" color mode (use full color palette). On small PNGs this can reduce the files by a factor 2, thereby reducing your apk size from ~2 MB to ~1.5 MB. This also means that in Gimp or Photoshop (or whatever), you first need to set the color mode to "RGB" before altering the elements, and before saving them back to "optimized".
Note2: Remember that Android is case-sensitive. When working with the layout or the graphics, keep this in mind!
Recompile the apk
When you are done "playing" and you want to experience the great and glorious app you created, you need to recompile it.
In your folder where you have the unpacked folder "JY-JY-1-C9-Radio-V1.0", you do a:
Code:
<path_to>/apktool -c b JY-JY-1-C9-Radio-V1.0
- Note that you specify the folder name, not some apk name
- the "b" is for build.
- The "-c" is to use the original AndroidManifest.xml
If you see errors, please first google for it before asking questions. There is so much to find on this stuff on the web.
If your apk compiled successfully (don't mind the warnings), you will find it inside "JY-JY-1-C9-Radio-V1.0/disẗ" as a new "JY-JY-1-C9-Radio-V1.0.apk".
Push the apk to your unit.
Simply use one of the scripts from my repository. Make sure to have adb in the right place (windows) or change the script accordingly. Read the Readme: (https://github.com/hvdwolf/Joying-RootAssistant/blob/master/Radio-Mod/Readme.md) on my github repository inside the "Radio-Mod" section for info on how to use the scripts to install it on your unit.
Troubleshooting
Q1. adb or adb.exe can't be found.
A1. Make sure you have adb installed. Use the proper path to adb.
Q2. I can't get a connection to the unit.
A2. Search the web and find out how adb should work, see also the readme in my Radio mods. On 6.0.1 first activate adb over tcpip, or conect via USB.
Q3. You get an android icon instead of the Radio icon and when you tap it, your unit says "application not installed".
A3. Reboot, check again and try another time to copy it to your unit. If nothing works (after a couple of attempts), reboot and copy the original radio apk back in place, reboot again.
Q4. You rebooted the unit and you hear music, but you don't see a Radio icon.
A4. Same as Q3/A3: so do the same. This is due to the fact that the Radio function is a 2-step approach on the Intel joying units. The CarRadio.apk (hidden) does the real work. The Radio.apk is just the visible "tweak and go" app.
Changelog:
Version 0.2, 06 June 2017; few typos and rephrasing; Add reference to working in terminal / cmd box; Add paragraph on installing framework-res.apk as dependency for apktool.
Version 0.1, 05 June 2017; first version

Do you need to pull the framework file from the unit and load into apk tool first?
https://ibotpeaches.github.io/Apktool/documentation/#framework-files
I ran into issues on 6 with apktool until I loaded the framework.

gustden said:
Do you need to pull the framework file from the unit and load into apk tool first?
https://ibotpeaches.github.io/Apktool/documentation/#framework-files
I ran into issues on 6 with apktool until I loaded the framework.
Click to expand...
Click to collapse
Did you have issues with the Radio app or with the SofiaServer apk?
I tried with the framework that came with apktool (inside the jar) and with the framework-res.apk from the joying unit.
Apart from the issues you can encounter on this 6.0.1 version, I didn't notice differences for the Radio app.
I can imagine that with SofiaServer being a real system app, that it also might need the framework-res.apk.
However, normally when decompiling you get an error if you miss a "framework" type apk. It will even mention which apk you need. (Had that on my previous Samsung phone which uses a lot of Samsung only resource and framework like apks.
I will at least add a 5th Q/A section describing how to do that.

surfer63 said:
Did you have issues with the Radio app or with the SofiaServer apk?
I tried with the framework that came with apktool (inside the jar) and with the framework-res.apk from the joying unit.
Apart from the issues you can encounter on this 6.0.1 version, I didn't notice differences for the Radio app.
I can imagine that with SofiaServer being a real system app, that it also might need the framework-res.apk.
However, normally when decompiling you get an error if you miss a "framework" type apk. It will even mention which apk you need. (Had that on my previous Samsung phone which uses a lot of Samsung only resource and framework like apks.
I will at least add a 5th Q/A section describing how to do that.
Click to expand...
Click to collapse
I had issues when I made changes to the SofiaServer apk. I initially built against the 6.0.1 ROM using the 5.1.1 framework. I didn't see any errors, the apk just would not work when loaded on the unit. Now, I pull it from the ROM and load on every ROM update ( just to be safe).

gustden said:
I had issues when I made changes to the SofiaServer apk. I initially built against the 6.0.1 ROM using the 5.1.1 framework. I didn't see any errors, the apk just would not work when loaded on the unit. Now, I pull it from the ROM and load on every ROM update ( just to be safe).
Click to expand...
Click to collapse
I added a section and not as a new Q/A