Related
GgI am currently working on a major update to the apk manager application as well and changing the name to APK Multi-Tool with some new added features and also to fix some issues with some code errors.
I am also changing a lot of the features as well since a lot of the code has been outdated for a while.
I have updated all the files and modified Apk manager's Scripts to fix many user reported bugs from Daneshm90 apk manager which he had written a simple script to ease the process of editing apks. Got a lot of downloads so thought its in demand
Whether you're doing basic image editing or editing the smali or xml files, on average u have to use (Brut.all or JF's smali/baksmali) awesome tool to extract the apk, edit it, then sign the apk and then adb push/install it. This process is quite tiresome if you are testing a method that needs fine tweaking.
This script should make the process a LOT smoother.
Theres an option of compiling/signing/installing all in one step
Thanks:
Goes to Daneshm90 the Original Writer of APK Manager
Goes to Brut.all for his awesome tool.
Goes to JF for ofcourse, smali/baksmali
Features:
- Added framework dependent decompiling (For non propietary rom apks). (Option 10). Checks whether the dependee apk u selected is correct.
- Allows multiple projects to be modified, switch to and from.
- Allows to modify system apk's using apktool but ensures maximum compatibility in terms of signature / manifest.xml
- Batch optimize apk (Zipalign,optipng,or both)
- Batch Ogg optimization
- Batch install apk from script (option 19)
- Batch Theme Image Transfer TOOL
- Batch Theme optipng TOOL
- Batch Theme Zipalign APK TOOL
- Compression level selector (monitor status above menu)
- Error detection. Checks if error occurred anytime u perform a task, and reports it
- Extract, Zip apk's.
- Incorporates brut.all's apktool
- Improved syntax of questions/answers
- Logging on/off has been removed. Instead a log.txt is created which logs the activities of the script organized using time/date headers
- Optimize pngs (ignores .9.pngs)
- Pull apk from phone into modding environment.
- Push to specific location on phone
- Quick sign an apk (Batch mode supported)
- Read log (Option 24)
- Sign apks
- Supports batch installation, so if u drag multiple apks into the script (not while its running) it will install them all for u. U can ofcourse drag a single apk as well
- User can change the max java heap size (only use if certain large apks get stuck when decompiling/compiling apks) (Option 19)
- U can now set this script as ur default application for apks. When u do, if u double click any apk it will install it for u.
- Zipalign apks
- Much Much More
Instructions:
- Place apk in appropriate folder (Any filename will work, if running for first time folders will not be there, you must run and then the folders will be created)
- Run script
- Minimize the script
- Edit files inside the project folder
- Maximize the script
Requirements:
Java 1.7
Android SDK
FAQ
Resulting apk file is much smaller than original! Is there something missing?
First: compression of resources.arsc file. Sometimes this file is compressed in original apk, sometimes not and apktool always compress it. Second: lack of META-INF dir. Apktool builds unsigned apks, so they lack signatures stored in this dir. Third: apktool uses newest Android SDK, so it could optimize files better, especially if original app is old. So: unpack both original and resulting apk, remove META-INF from original and then compare sizes. If they're still much different, then you could report on XDA or somewhere.
There is no META-INF dir in resulting apk. Is this ok?
Yes. META-INF contains apk signatures mostly and after modifying apk in no longer signed, so there are no signatures in it. You have to sign resulting apk and then META-INF dir will be created.
What do you call "magic apks"?
Sometimes there are some apks which (for my current knowledge) are invalid, broken, theoretically they shouldn't exist. There may be many reasons of their existence: my lack of understanding of Android resources; some non-public, maybe future SDK tools or custom modifications of these; manual hacking of binaries, etc. Usually I can't do anything about it, but you could at least try to replace broken parts by something valid. Actually it's quite likely that they aren't even used, because if they would, then application would crash.
Got problems ?
1. Make sure your path has no spaces
2. Your filename has no wierd characters
3. Java/adb are in your path
4. It's not a proprietary rom's apk (aka Sense,Motorola,Samsung) (If u are, then use option 11 and drag the required framework, eg com.htc.resources, twframework-res...etc)
5. It's not a themed apk (if it is, expect .9 png errors, use as close to stock as possible)
6. Look at the log to know whats happening
7. If all else fails, post as much info as possible and we will try to assist you.
TO DO LIST
Add new feature to Randomly Generate a new Key File for signing the apk files after modifying and recompiling of the apk files this will also allow of uploading to the android market as this added feature will allow you to sign apk files that you may of compiled without signing beforehand.
Modify the Signapk script to be compatible with the Randomly Generation feature in the works
and a few other added features are in the works as I am redesigning the application and rewriting a lot of the code to fix issues as well as some of the new features have broken parts as some features have been moved and broken some command line prompts.
Installing APK Multi-Tool Itself
Instructions (Linux):
1-Download, create a folder in your sdk called "APK-Multi-Tool" and extract into it.
2-Goto the the "sdk/APK-Multi-Tool" folder and rename "Script.sh" to "script.sh".
3-Go into the "other" folder, right click on one file at a time, goto "permissions" in the new window and check the execute box.(do this with all the files)
4-To add the path to your folder open up a terminal and type in -
sudo su
PATH=$PATH:/THE PATH TO YOUR "SCRIPT.SH"
(for me this looks like the following)
PATH=$PATH:/sdk/APK-Multi-Tool/other/
5-export PATH
6-install "sox"
7-Type into the terminal "cd PATH TO YOUR SCRIPT.SH"
7.5 export PATH={PATH}:/PATH TO Your SDK/sdk/platform-tools/adb
8-Type "./script.sh"
9-You should have a running APK-Multi-Tool.
how to install sox:
Open the software center of the linux service and searched for sox. Installed it and it there you will have SOX working.
- Place apk in appropriate folder (Any filename will work, if running for first time folders will not be there, you must run and then the folders will be created)
- Open terminal and change-directory to APK-Multi-Tool(Easiest way is to type "cd ")
- Chmod 755 Script.sh
- Chmod 755 all files apps inside other folder
- Run script by typing ./Script.sh
- Minimize the script
- Edit files inside the out folder
- Maximize the script
Downloads:
https://github.com/APK-Multi-Tool/APK-Multi-Tool-Linux/archive/master.zip
Please check back daily or weekly as this project is under active Development and I am releasing Alpha releases on the website for Testing and bug reports.
Lol, why has nobody commented on this?
You're a savior. This is awesome. Can't wait for the rewrite.
AW: [Linux][UTILITY][TOOL] APK Multi-Tool
+1
Haven't seen this also available for Linux, so this is great.
Sent from my Galaxy Nexus using xda premium
Binary updates
UPDATED to apktool-cli-1.5.3-SNAPSHOT
-Updated to smali/baksmali to v1.4.2
-Fixed (issue #396) - Correctly handle android:debuggable while in debug
mode.
-Fixed (issue #340) - Fixed superclass errors on debug mode.
-Updated to Gradle 1.4
-Updated known bytes for configurations to 38 (from addition of layout
direction)
-Fixed NPE when handling odex apks even with --no-src specified. (Thanks
Rodrigo Chiossi)
-Fixed (issue #427) - Correctly handles `--frame-path` on uild
Error 404 on GitHub download page
xcly said:
Error 404 on GitHub download page
Click to expand...
Click to collapse
Fixed
Sent from my DROID RAZR CDMA XT912 using Tapatalk 2
I merged a few projects together instead of having multiple Android developer projects. I did some spring cleaning and deleted a few projects that was not useful and served no purposes. Also renamed the project organization which broke the link forgot to update lol.
Sent from my DROID RAZR CDMA XT912 using Tapatalk 2
I ran the script but I can't see any folders being created.. Trying to sign an apk. Looked up on google and all I can find is your instructions to put apk in appropriate folder (which I can't see..)
Thanks in advance
I will look into this ABCs see what's up
Sent from my DROID RAZR CDMA XT912 using Tapatalk 2
I ran the apksign tool separately using terminal for now
I got
The program sox is missing or is not in your PATH,
please install it or fix your PATH variable
If I go to the other folder there is no sox like in the windows version.
I will look into this asap once I get some free time
Sent from my DROID RAZR CDMA XT912 using Tapatalk 2
civato said:
I got
The program sox is missing or is not in your PATH,
please install it or fix your PATH variable
If I go to the other folder there is no sox like in the windows version.
Click to expand...
Click to collapse
I had the same problem but it was fixed once I installed sox. There was a tutorial on google search for setting up apk manager you might wanna have a look at.
Sent from my GT-I9300 using xda premium
raziel23x said:
I will look into this asap once I get some free time
Sent from my DROID RAZR CDMA XT912 using Tapatalk 2
Click to expand...
Click to collapse
xcly said:
I had the same problem but it was fixed once I installed sox. There was a tutorial on google search for setting up apk manager you might wanna have a look at.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I got it solved , I just entered the Ubuntu software center and searched for sox. Installed it and it works.
Maybe good to add this in OP when using linux. It is stupid of me thinking it was something harder so thank you for your help and fast response.
A other methode I found here
PS:
You don't need to type in ./Script.sh in teminal in linux , just clicking on it (Script.sh) and select "run in terminal" does the trick without typing anything.
updated the original post with detailed instructions
raziel23x said:
updated the original post with detailed instructions
Click to expand...
Click to collapse
Put updated info into the README file. Made a few corrections (hope you like).
AndyOpie150 said:
Put updated info into the README file. Made a few corrections (hope you like).
Click to expand...
Click to collapse
pushed your changed to github all code changes are welcome even forking the repo on github and making changes and doing pull request are welcome
raziel23x said:
pushed your changed to github all code changes are welcome even forking the repo on github and making changes and doing pull request are welcome
Click to expand...
Click to collapse
Just uploaded changed attachment. Fixed minor typos in Installation Instructions. Sorry I didn't get it straight before you pushed to github.
I deleted the info for Windows in previous attachments as well due to this being for the Linux version. Didn't know if you caught that.
PS: Thought I would let you decide if you liked my hair brained ideas first.
Is there any way to have a .jar file work without having to rename to .apk, or is that a mind bogling code rewrite. I'm all for learning.
Hey, I made some changes to the script to act more like the windows version of this tool. I added a setup.sh which will create all the folders and set permissions to everything. i also the ability to have multiple projects going at the same time, and also added a separate jar/dex folder so there is no need to rename the jar files to .apk to edit it. and other updates as well. its not 100% up to par with the windows one, but these few changes make a huge difference. Would you be interested in this?
---------- Post added at 11:38 AM ---------- Previous post was at 11:36 AM ----------
AndyOpie150 said:
Just uploaded changed attachment. Fixed minor typos in Installation Instructions. Sorry I didn't get it straight before you pushed to github.
I deleted the info for Windows in previous attachments as well due to this being for the Linux version. Didn't know if you caught that.
PS: Thought I would let you decide if you liked my hair brained ideas first.
Is there any way to have a .jar file work without having to rename to .apk, or is that a mind bogling code rewrite. I'm all for learning.
Click to expand...
Click to collapse
actually yes there is..i made an updated version of the script which has those features
clmowers said:
Hey, I made some changes to the script to act more like the windows version of this tool. I added a setup.sh which will create all the folders and set permissions to everything. i also the ability to have multiple projects going at the same time, and also added a separate jar/dex folder so there is no need to rename the jar files to .apk to edit it. and other updates as well. its not 100% up to par with the windows one, but these few changes make a huge difference. Would you be interested in this?
---------- Post added at 11:38 AM ---------- Previous post was at 11:36 AM ----------
actually yes there is..i made an updated version of the script which has those features
Click to expand...
Click to collapse
Make a pull request on github and in will merge it
Sent from my Xoom using Tapatalk HD
Whenever I create a new Android application project, my gen folder is missing thus giving me the error of R cannot be resolved to a variable.
I've searched around and tried cleaning and building but that did not fix the issue.
Has anyone dealt with this issue before? If so, how did you fix it?
Thanks
I had this issue when there was an error in one of my xml files. Have a close look at every layout again.
nikwen said:
I had this issue when there was an error in one of my xml files. Have a close look at every layout again.
Click to expand...
Click to collapse
I've also read somewhere that it was the xml files causing this issue.
Could you clarify if I should only be looking at the xml files in my layout folder?
Thanks
InfiniteStratas said:
I've also read somewhere that it was the xml files causing this issue.
Could you clarify if I should only be looking at the xml files in my layout folder?
Thanks
Click to expand...
Click to collapse
There should be a red X in Eclipse if there is an error. Sometimes it just appears in the file but not in the project tree.
Since the new sdk update (22) I need to check all boxes under project properties - java build path - import / export.
Taptalked u see .. əəs n pəʞlɐʇdɐʇ
I've had a similar issue some days ago. My R.java was not regenerated after I cleaned my project.
Here is what fixed it for me: It seems like as of SDK version 22, which I had recently downloaded, there is an additional package you have to download from the SDK manager called "Android SDK build-tools". I installed it, restarted Eclipse and everything was working again.:good:
I had found the solution on StackOverflow: http://stackoverflow.com/a/16643060/1691231
Check for any XML Errors Drawables/Layout/Menu/XML (Major issue in Eclipse)
As mentioned above, Update to latest SDK and Add-ons from the SDK Manager and Eclipse Updater
Remove any R.Android Imports in your Java Classes
And make sure your using a capadible fit version of Eclipse for android Development. Easiest Setup is to use the ADT Combo Package (Altho consumes more Ram)
I've spent about 3 days now trying to figure out a way to put a SwipeListView onto an Activity. Here's everything I've tried.
First, I downloaded SwipeListView from Github here: github.com/47deg/android-swipelistview
then I went straight to the tutorial in the Issues section here: github.com/47deg/android-swipelistview/issues/17
Unfortunately, There were still errors after I had followed the directions.
"R cannot be resolved to a variable" was in my SwipeListView.java file, as well as my PackageAdapter.java file. I don't know how to clear those up. These errors are associated with layout/ files, however after putting the layout files in both the SwipeListView project and my project, neither seemed to resolve the error.
Next I tried installing it as a Maven Dependency, by following the directions here: rgladwell.github.io/m2e-android/
However, after doing so, I did not see as the screenshot suggested a 'MAVEN DEPENDENCIES' folder in my project hierarchy. I am even more confused with Maven than I was trying to install the library on my own.
I really don't know what else to do at this point. Any help is appreciated!!
Copy the sources of the library to your src folder
Resources of the library to your res folder
Create a file named R.java in the library package and extend the R.java of your project
Done
Sent from my GT-S5302 using Tapatalk 2
Hi,
today Samsung published the Beta Browser and the Edge panel for opening web pages does not work anymore as the package name of the browser changed.
I decompiled the sbrowseredge app, changed the app name as well as the hardcoded part (in cocktail_widget.xml) to the beta, compiled it again with apktool 2.2.2 and signed without problems. However, I'm not getting it installed.
Failed to install Internet panel_2.0.14\dist\Internet panel_2.0.14.apk: Failure [INSTALL_FAILED_INVALID_APK: Package couldn't be installed in /data/app/myapp.sbrowseredge-1: Package /data/app/myapp.sbrowseredge-1/base.apk code is missing]
Click to expand...
Click to collapse
I installed the Nougat framework-res.apk for apktool. What else do I miss?
I still use jarsigner and thus v1 signing, however, my own apps (not Samsung related) do install without any problems.
(I tried as well just to decompile, change name only and compile/sign again with the same result.)
Thank you!
Andreas
andiling said:
Hi,
today Samsung published the Beta Browser and the Edge panel for opening web pages does not work anymore as the package name of the browser changed.
I decompiled the sbrowseredge app, changed the app name as well as the hardcoded part (in cocktail_widget.xml) to the beta, compiled it again with apktool 2.2.2 and signed without problems. However, I'm not getting it installed.
I installed the Nougat framework-res.apk for apktool. What else do I miss?
I still use jarsigner and thus v1 signing, however, my own apps (not Samsung related) do install without any problems.
(I tried as well just to decompile, change name only and compile/sign again with the same result.)
Thank you!
Andreas
Click to expand...
Click to collapse
I just tried and it works... here... https://www.sammobile.com/apk/samsung-internet-beta/samsung-internet-beta-5-4-00-3/
S7 Edge Powered By Echoe
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