Database Users

REQUESTING HELP Editing and creating NEW flipfont APKs

I have been working on this issue for most of the day over in the Vibrant forums.
I am posting here in hopes of getting someone who knows more about apk editing and fonts then I do to help out.
Link to the post on the XDA Vibrant forum here
Please post your response there. Once the issue is solved I will repost a walk-through on all Galaxy S forums.
Here is the start of my thread, please read the link to see the progress.
I am aware that there are other ways to edit the fonts on our phone, by replacing renaming the default font. This is NOT what I would like to accomplish.
Since the Galaxy S is the first android phone to use Flipfont, I think we should take advantage of it. It gives us a nice preview of the font in the built in menu option and is thus superior to the other methods.
I originally purchased the Bauhaus font from the market and made a backup of it through ASTRO. After pulling the file from my phone and putting it on the computer I started editing the file with Apk Manager 4.8 found here
Steps preformed
Copied original apk into place-apk-here-for-modding folder
Run script.bat and choose option 9 ***this maybe where the issue is as I may need to choose option 10 and include the dependancy if there is one for the flipfont apk.
replace bauhaus.ttf with a .ttf font of my choosing
edit all XML, yml and smali files to include the font name or font.ttf depending on the entry in the original file *** I did not change any of the other coding so again this maybe where the problem is, as I may need to change something else to have the font act properly.
Edit the last folder name in the smali folder tree from bauhaus to the name of my font
Replace font with custom font and replace the preview image with my own
Compile apk
Sign apk
Rename apk
install apk on my phone
After putting the apk on my phone and installing the file, it shows up as expected in settings>Sound and Display>Font style. The font thumbnail shows up properly as does the font preview. The preview does show up a little larger then the other fonts and may be a sign that the font is not optimized properly or that I missed something in the XML.
After applying the font and restarting, the phone is extremely slow, freezing quite often and the font does not show up, it shows the default font instead.
If anyone that knows more about XML or apk editing/creation can help it would be great.
I have included the edited font apk if you would like to download it and run it through Apk Manager 4.8. If you want to try it with the bauhaus or one of the other fonts you will need to buy it from the market and back it up. (trying not to break any rules here.)
[EDIT][More info] Ok I took a closer look at the font that came with the Bauhaus akp
In the discription of the font it list:
OpenType Layout, Digitally Signed, TrueType Outlines
I know that opentype is a new format and that alot of the fonts for OpenType that I find are made by Monotype, the same people that make the fonts available for download. I think this may have something to do with it or maybe Im just grasping. :ºp
Any font guys out there have any info on this?
CAUTION THE FOLLOWING FILE IS NOT MEANT FOR USE AND WILL CAUSE YOUR PHONE TO RUN SLOW!!!
Download Font APK

You only can use .ttf (true type font) any other type will not work,if you have a font u want to use but is not in .ttf then you need to convert it to .ttf, btw i prefer the Type Fresh app to manage and change my fonts is easier than the method you described.

Also, make sure the font has a full latin library. I learned the hard way from the TypeFresh app (which is a way better solution IMO). In its instructions which I only read the second time, one font (i believe its called DroidSansFallback.ttf) needs to have a COMPLETE set, including latin, I believe for certain coding going on somewhere. I bricked my phone within two hours of rooting it. Took three to get it back. (Backup people!)
Anyways, now I use TypeFresh, it gives you options on which system font to replace, and I never replace that one.
Hope this helps.

[Q] getting Application Name from APK file

Hi
I have a folder with +2000 apk files and they named like 'app.apk' , 'app1.apk' , and many more like this. so I want to make a software that rename these files like this
app.apk ---> <ApplicationName> <version> .apk
so I need a way to get the application name from the package
I already tried decompiling xml file but there is only package name
I searched xda and google for this matter and no luck....
can you help me to get the application name?

Run "aapt d badging some.apk" and search for "application: label=". aapt is a part of SDK.

Brut.all said:
Run "aapt d badging some.apk"
Click to expand...
Click to collapse
Thanx for this very useful.

There is a script by phsorx that automates this

If you're really in a pickle you can put the apk on your device's sd card and run it. It will show you the app name and permissions before actually installing.
This method would be tedious and painful, but effective.
Comin' at you from Dead Space. 2, that is.

apkspy
or run this:
http://forum.xda-developers.com/showthread.php?p=14523375
it does exactly what you want.
I'm the author btw.

I use aapt.exe from latest SDK. Some apk doesn't show a label or a valid english label.
(Android Asset Packaging Tool, v0.2-3303571)
Your have to use the old version of aapt.exe that work great!
(Android Asset Packaging Tool, v0.2)

[Q] Hero Stock Rom .. Any possibility to run newer apps

I just installed my Hero's stock rom.. Android 1.5 with the first version of sense..
I did this with the sole purpose of seeing how it actually ran back then, compared to all the custom roms thats out there.. And i actually think it runs damn well! Its very snappy and it does have the functionality i need.. But most of the apps i use does not support Android 1.5 anymore which is a problem for me..
Is there any way you can "fake" that the android version you are running is maybe 2.1 ? So that i can download the apps i need, or would that not work? I remember that when i had a Tattoo i could fake the resolution of the display, so that more apps would show, and it worked fine actually.

You can try Change model!
If i remember correctly I've a solution:
You need root privileges (and I think you've =)) and a file manager as ES File Explorer.
In ES go to Setting -> Root Option -> Explore as Root and Mount File Sistem
In system folder find and open file build.prop, make a backup and edit the original
Setting, for example:
ro.product model=Nexus S
ro.product manufacturer= Samsung
Save and now you can install all apps...

I don't think it's that simple. Try this:
Reference: http://developer.android.com/guide/appendix/api-levels.html
Tool: http://code.google.com/p/android-apktool/
1 - Put the apk you want to change in the apktool folder and open cmdline.
2 - Run: apktool decode name.apk
3 - Use notepad to edit the AndroidManifest.xml and change the value for 'minSdkVersion':
<uses-sdk android:minSdkVersion="3" /> (3 or whatever version of Android you want your app to be compatible with.)
4 - Build a new apk. eg. apktool b C:\apktool\name name2.apk
Even if the apk installs; some or all features of the app may not work. Also, you will probably need to change the 'AndroidManifest' of any new version or update.
The other option is to find older versions of the app.

Smart Manager with Application Permission from Note 5

This is for those who wanted to have this function in their beast and yet no Note 5 rom is availble for their device , well smile..here you go
:good:Try at your own risk. I wont go in detail like step by step or what root explorer to use. You will have to figure it out. Im not trying to be mean but you will have to learn it =P
Your device must be rooted.
Download any rom that is made for Note 5 , custom or stock (make sure you ask for permission from the creator) , extract the folder "system/app/applicationspermissions"
and copy the folder (doesnt matter if is odex or deodexed) then paste it to your system/app/ and set the permission to the copied folder and the apk itself.
Then add the code below into your others.xml in you csc folder.
Code:
<!-- Smart Manager -->
<CscFeature_SmartManager_ConfigDashboard>dual_dashboard</CscFeature_SmartManager_ConfigDashboard>
<CscFeature_SmartManager_DisableAntiMalware>true </CscFeature_SmartManager_DisableAntiMalware>
<CscFeature_SmartManager_ConfigSubFeatures>roguepopup|autoclean|autorestart</CscFeature_SmartManager_ConfigSubFeatures>
Save , reboot and voila.
Bug
Nofitications - Block app notifications will FC.
Application Permissions - Sort by permission , will take some times to load the apps.
And it works , it does block what it offered.
Feel free to use

Thank you but nowhere i could got this foleder
system/app/applicationspermissions
can you please upload it.
Thanks in advance

SmartManager Dual dashboard
http://forum.xda-developers.com/note5/themes-apps/smartmanager-dual-dashboard-t3273609

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