Arabic support for Android - Project - G1 Android Development

Good day all,
i'm just a simple guy tarting to learn development and trying to give back to the community through a project i need (arabic support for Android)
i started by tracing the [ROM] KB7SQI's Magic Mod w/ Flash & Arabic Support V2.7.2 to understand what gives it a difference
i found this file
Code:
libjni_parfieldime.so
it rang a bell as i have already seen the following
http://www.parfield.com/
which is a website that provides 3rd party arabic support for android
i opened the libjni_parfieldime.so with a text editor to find the following file names
Code:
libandroid_runtime.so
liblog.so
libcutils.so
libutils.so
libicuuc.so
libc.so
libstdc++.so
libm.so
so i extracted these files, opened them and was hoping to find something to call the libjni_parfieldime.so, but nothing, i pushed them into the /system/lib of the cyanogenmod 4.3.2.1 rom but it caused a halt at the G1 boot screen, hope Cyanogen could help on this
on the other hand when you push the libwebcore.so to that folder it gives you complete arabic browsing support
this is where am at,,, awaiting your support to reach the next step together

Arabic support for the browser on all ROOTED 1.6 donut edition roms only (tested on CyanogenMod 4.3.2.1)
its very simple
1- Download this file
http://www.mediafire.com/?mmmyzigmvem
2- Mount memory card on your computer (either by cable or by an SDcard reader)
3- Copy the libwebcore.so to your memory card root folder
4- open terminal emulator and type the following
Code:
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/libwebcore.so /system/lib/
reboot
5- Enjoy

I've already contacted Cyanogen about this. He said he will try to get it into the next release.

What this file does except Arabic fonts support? will it help me to align text to the right correctly etc.?
thanks

i'm trying to find what calls the libjni_parfieldime.so file in the ET rom
anyone know how to debug this ?

logically this would be done at boot to support the system to encode text in system wide applications
but what is the main player here is my question

Any new progress?

Hi all,
as far as I know, it is not that hard to make any build capable of reading and writing Arabic correctly. But, as the TIME is my main obstacle to test that and to try it on one of the builds, such as 1.6 or 2, I hope any one of you, fellows, will do it and try it.
What you need is a linux OS, Ubuntu is preferred. and also you need to download the android source project from 'http://source.android.com/download' also you need the latest webkit browser.
After that, replace all the files from the rendering folder from arabicandroid project from : "http://code.google.com/p/arabicandroid/downloads/list" ignore libwebcore.so (because it's already have been compiled)
After you replace all the files for the android core, you may now compile the android source. --> which will give an Arabic android > Hopefully
Hope this was clear enough, although I don't think so

do i need to install any font first http://forum.xda-developers.com/showthread.php?t=480964

thank you for the libwebcore.so it is a vital thing to have arabic support in the browser, it sometimes writes text backwards but something is better than nothing

yozpalang said:
do i need to install any font first http://forum.xda-developers.com/showthread.php?t=480964
Click to expand...
Click to collapse
sure thing

try it on cyanogen 4.2.6 and my device got stock on T-mobile screen ,but it works on 4.2.5, am I doing something wrong or it doesn't work with 4.2.6

any body else has this problem ?

this doesn't work on CM roms any more

.. delete plz

Related

Building and deploying from cupcake source code to my device - using Mac

Hi all,
I am trying to setup my Mac OSX (Mac Mini) to build and deploy the Cupcake source code and deploy the built images on my ADP1 device.
I must admit - I am no Linux guy, so a bit slow on understanding the various instructions.
My problem - I was somehow able to get the sources down to my Mac, and even run a successful MAKE.
But - got stuck there (could not figure out how to run the built images on the emulator).
So I decided to be brave and compile & install on my ADP1 device.
This is where I am stuck:
In the explanation at the Google site, they claim there should be a ".Repo" directory holding a file called "manifest.xml" in it, and that I should download and add to that directory a file called "local_manifest.xml".
I can not find such a ".Repo" directory, and hence - dont know where to put that file.
Any help would be highly appreciated !
Shimon Shnitzer
TAKEphONE said:
Hi all,
I am trying to setup my Mac OSX (Mac Mini) to build and deploy the Cupcake source code and deploy the built images on my ADP1 device.
I must admit - I am no Linux guy, so a bit slow on understanding the various instructions.
My problem - I was somehow able to get the sources down to my Mac, and even run a successful MAKE.
But - got stuck there (could not figure out how to run the built images on the emulator).
So I decided to be brave and compile & install on my ADP1 device.
This is where I am stuck:
In the explanation at the Google site, they claim there should be a ".Repo" directory holding a file called "manifest.xml" in it, and that I should download and add to that directory a file called "local_manifest.xml".
I can not find such a ".Repo" directory, and hence - dont know where to put that file.
Any help would be highly appreciated !
Shimon Shnitzer
Click to expand...
Click to collapse
".Repo" is a hidden folder any folder with a "." in front of it will be hidden, enable the viewing of hidden folders and you'll find it.
Thanks !
I knew I was probably missing something simple...

Any guides on how to create/compile custom roms?

I am a linux user...
Anyone can share the howto or if there are any guides?
+1 bumping this thread
Second that...
http://www.koushikdutta.com/2009/08/build-configuration-for-t-mobile.html#links
He seems to have a script to compile the Kernel...
I don't know to what extent this would help us but it is a start. I dont quite know how the apps are installed on a new ROM....
It would be nice if someone can explain what is needed and what is optional in the kernel and some of the mods that other people are doing and how they integrate in the OS.
I see a lot of improvements in the new ROM's but no how-to on doing it your self. I thought that was the point of having open source OS.
I would quite like this as well =o)
Have made a bit of a start by following this:
http://source.android.com/download
Shows you how to get all the code and do a build.
I believe the next thing would be to pick the required files from the output folder of the build, dump the boot.img and replace the kernel with 32B or 32A one, add the Magic model config file (to ramdisk) and recreate the boot.img
Replace/Add any modules required like maybe wifi or bluetooth, then need to change the build.prop file and put it all in to update.zip and sign the file.
Haven't had time to test this out but seems kind of logical...maybe?
Hello!
I'm following the android.com tutorial, but I want to ask: how can I download the donut branch? There's no mention in the entire site about it... Also, the cyanomod's multitouch and so on, where does it come from? Is it made by himself or it's somewhere in the net?
Thanks
Learn how to use GIT to get the donut branch from here: http://android.git.kernel.org/
Proble is that it doesn't specify the donut project path
Is there a command to list all project paths? I can't seem to find it
L10nH34Rt said:
Proble is that it doesn't specify the donut project path
Is there a command to list all project paths? I can't seem to find it
Click to expand...
Click to collapse
Code:
git branch -a
in any local git directory
Ok, then so far I've downloaded the donut branch, and compiled too. What now?
1. how to create a ROM from the made files?
2. how to compile the kernel / how to replace the one created with the make command with the one I'm running on?
3. is there any option I can configure to fit my phone? (HTC Magic 32A)
4. how can I root my ROM?
thanks
there is this guide that i have found:
http://www.koushikdutta.com/2009/08/build-configuration-for-t-mobile.html
'make' finished with success but i can't find how to transform it into 'update.zip' file...
anyone?
It says that in the link you have posted yourself.

[LNX]Rhobuntu on HTC ELF 09-11-2010

Rhobuntu -- Ubuntu like Linux
Download: http://technetic.net/rhobuntu/downloads/HTC ELF/
(right click --> save target as)
1. Download latest build
2. Unzip to sdcard (7zip)
3. run haret.exe
Changlog:
new init-script (thanks AmiPro)
new startup.txt
I'll have a play on lunch - but I don't know if I have enough time, but thank you very much for linking this in!
If I do't have time on my lunch - I'll give it a go on my lunch!
Hello, Walter, and thank you for sharing this.
I´m fighting with my Elfin but I think Rhobuntu needs at least 1,6 GB of free space in the SD card.
So, with my 1GB card, I think I´m sold .
Greetings.
I am using HTC TOUCH GSM.
I have installed the Rhobuntu.
It opens up till the main screen and hangs..
no pointer movement and the screen resolution is too small..
I am not even able to scroll and see the full screen.
It hangs ..
need help..
i tried it but its mere of a beta stage
Let´s try
Thanks!!!
Hi Walter, wheather it will work with HTC TOUCH GSM???
jonnigin said:
I am using HTC TOUCH GSM.
I have installed the Rhobuntu.
It opens up till the main screen and hangs..
no pointer movement and the screen resolution is too small..
I am not even able to scroll and see the full screen.
It hangs ..
need help..
Click to expand...
Click to collapse
I have the same problem after starting the desktop and the icons bar on the botton, the device show the keyboard but I'm not able to move the cursor with the stylus.
please note that the device shows me only part of the keyboard, seem like that the resolution is wrong.
During the startup the font changes size. can be related to the wrong resolution??
No actions can be done with the sistem.
thanks and let me know if more information is need
This thread made me come up with a new prefix for these threads.
[LNX]
So put [LNX] in threads for Non Android Linux builds. So users can easily identify or search for specific threads.
Spread the word mate
With /dev/input/event3 it works well.
AmiPro wrote a new detection script for touchscreen.
Now Rhobuntu works on HTC ELF.
yo.. you know what is Elfin device code? i got to edit the startup.txt to make this LXDE runs on it. thanks!
Could you post your startup.txt?
Download for new init-script: http://rhobuntu.googlecode.com/files/init
Hello excuse, you could tell me how to replace the init file? I tried to follow the explanation at the beginning of the post, but I could not mount the file ubuntu.img, in any way. I tried with a live ubuntu, but it did not work. I tried to mount the. IMG file with magic disc but can not mount it. I guess not enough to replace the init file in the destination folder? I tried but during boot change the resolution, and the screen remains fixed on a keyboard in the middle where you can not interact. As was the case before ... Could you explain in detail how to replace the init file, or at least to run on the touch rhobuntu elf?If you want to write me a pm. Thanks
P.s. sorry for my bad English
nightly_shadow said:
yo.. you know what is Elfin device code? i got to edit the startup.txt to make this LXDE runs on it. thanks!
Click to expand...
Click to collapse
MTYPE 2372
http://forum.xda-developers.com/showpost.php?p=4440575&postcount=7
ste81x said:
Hello excuse, you could tell me how to replace the init file? I tried to follow the explanation at the beginning of the post, but I could not mount the file ubuntu.img, in any way. I tried with a live ubuntu, but it did not work. I tried to mount the. IMG file with magic disc but can not mount it. I guess not enough to replace the init file in the destination folder? I tried but during boot change the resolution, and the screen remains fixed on a keyboard in the middle where you can not interact. As was the case before ... Could you explain in detail how to replace the init file, or at least to run on the touch rhobuntu elf?If you want to write me a pm. Thanks
P.s. sorry for my bad English
Click to expand...
Click to collapse
Download Ubuntu LiveCD
http://www.ubuntu.com/
Run liveCD
- copy Ubuntu.img to the root of your harddisk (c:\ for example)
- open terminal
- open folder of Ubuntu.img (cd /media )
- mount Ubuntu.img ( sudo mount -o loop Ubuntu.img /mnt )
- run: sudo nautilus (FileManager)
- select "show hidden files"
- copy new init to /mnt
- close nautilus
- maybe you have to end the nautilus task in terminal with CTRL+C
- umount Ubuntu.img ( sudo umount /mnt )
- copy new init to /mnt
Thank you soo much!!!! Now Rhobuntu run well on my elf!!!!
Failed to find Ubuntu.img on SD Card
Hi,
Thanks for a good initiative. I've HTC Touch GSM (HTC ELF) (P3450) in India. I always keep changing OS on my mobile. I was waiting for Linux on it. I downloaded Rhobuntu and replaced the init in img file also replaced STARTUP.TXT and zimage file with the given one. Now when I start herat I get
1osetup: /dev/block/loop2: No such file or directory
Failed
Failed to find Ubuntu.img on SD Card.
/bin/sh: can't access tty: job control turned off
/#_
After the hash (#) the cursor keeps blinking.
Can you please help me what I have done wrong.
Gourav
gouravjoshi said:
Hi,
Thanks for a good initiative. I've HTC Touch GSM (HTC ELF) (P3450) in India. I always keep changing OS on my mobile. I was waiting for Linux on it. I downloaded Rhobuntu and replaced the init in img file also replaced STARTUP.TXT and zimage file with the given one. Now when I start herat I get
1osetup: /dev/block/loop2: No such file or directory
Failed
Failed to find Ubuntu.img on SD Card.
/bin/sh: can't access tty: job control turned off
/#_
After the hash (#) the cursor keeps blinking.
Can you please help me what I have done wrong.
Gourav
Click to expand...
Click to collapse
http://forum.xda-developers.com/wiki/index.php?title=Ubuntu_on_the_Rhodium#Installation
did you replaced the init file?
Thanks buddy, I managed to get it installed. Mistake was mine, I copied Ubuntu.img file in ubuntu directory. as i moved it out on storage card root, it got installed.
But after installation there was a big key board on screen which i managed to drage down with stylus. but what I feel is the resolution need to be changes as it is showing everything so big.
Also, I tried to make a call to this device, we get ring at device from which I was calling, but there was nothing on the device on which I install rhobuntu. also I could not make a call from here. Can you help me in these cases.
Found something while starting rhobuntu, you may be interested to know.
While starting rhobuntu from haret.exe at one point it shows starting ophono daemon something, where it says can't create signal descriptor file. is it helpful to resolve this issue?
Gourav
Hi,
Got installed the Rhobuntu can access it. Facing two issues on it as follows;
1. Phone function not working as ofono daemon says - can not create signal filedescriptor: Function not implemented
2. Resolution are not as per device.
Please anybody help me to get all this working.
Gourav

Android NDK r5 - stdio.h : sys/cdefs.h not found !

Hello,
Sorry for my bad english...
I try to build a native application but i get a linkage problem.
Code:
...
/usr/src/android-ndk-r5/toolchains/arm-eabi-4.4.0/prebuilt/linux-x86/bin/arm-eabi-gcc -c -g -I/usr/src/android-ndk-r5/build/platforms/android-r5/arch-arm/usr/include test.c -o test.o
In file included from test.c:1:
/usr/src/android-ndk-r5/toolchains/arm-eabi-4.4.0/prebuilt/linux-x86/bin/../lib/gcc/arm-eabi/4.4.0/include-fixed/stdio.h:50:23: error: sys/cdefs.h: No such file or directory
/usr/src/android-ndk-r5/toolchains/arm-eabi-4.4.0/prebuilt/linux-x86/bin/../lib/gcc/arm-eabi/4.4.0/include-fixed/stdio.h:51:24: error: sys/_types.h: No such file or directory
...
I don't found sys/cdefs.h or sys/_types.h, there is juste sys/types.h exists, no other standard lib...
Can someone help me to clarify this situation ?
* Does Google forgot to put include on NDKr5 zip ?
* Or it's normal and so where can i found thems (cdefs.h & co) ?
Thanks a lot
Molux
Did you ever get an answer to this post. I have the same issue
A little late but these are outside of the actual toolchain, I found mine here...
-I/../AndroidNDK/android-ndk-r6/platforms/android-9/arch-arm/usr/include
why i no found folder 'arm-eabi-4.4.0' in ndk/toolchains ?
It's an old question, but it ranked high on Google searches, so the answer below may help a frustrated programmer or two:
Assume you just want to build a simple hello world application, and don't want to bother yourself with Makefiles.
Or maybe you do want to bother yourself with makefiles, but just want to build the same thing for Linux and Android, and just replace the toolchain. An easy going recipe is below. Versions numbers will change, principles will probably remain the same.
Assume you also got tired about figuring where the hell those crt* files are at, why the cross compiler insists on refusing to find your include files, and you are minutes away from doing the right thing and create a proper Android.mk file (or Gradle... see source link below for my personal thought about it [hint: they are not very positive]).
Then do the following, live long and prosper:
Host: linux-x86_64 . Target: ARM (thumb).
# Adding GCC wrapper for "stand alone" NDK:
$ export SYSROOT=$NDK/platforms/android-21/arch-arm
$ export CC_NDK="$NDK/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86_64/bin/arm-linux-androideabi-gcc-4.8 --sysroot=$SYSROOT"
Then you can build by invoking $CC_NDK ...
Use your own version of course. A similar method can be done with the AOSP/CM/whatever platform base you have itself, but that should get you going.
Source: http://ronubo.blogspot.co.il/2016/01/standalone-gcc-clang-cross-compiling.html
Thanks @ronubo. Helpful blog post on lkm debugging too.

[UTILITY][10-8-2012] APK Manager for Mac OS X, Intel only, v3.0

So almost everyone here should be pretty familiar with android, and that means you've probably heard of (and maybe even used yourself) the windows tool APK Manager by fellow XDA member Daneshm90.
Early last year I started to port the windows 4.9 version to mac using the outdated linux script for a base. And I had some early success at the time with simply using macports to install sox, optipng, etc. And then my computer crashed (double drive failure in July, 2011) and I gave up for the time being. Recently though I was excited to find that someone else tried to do the same thing, XDA member MAD Industries released a very basic port for mac.
Sadly though, a quick diff of his script and the outdated linux version shows that it was still woefully behind the windows version. And so I started working (once again) on my own port of APK Manager for Mac OS X, with my goal to not only bring this current to the windows feature set, but exceed it in many ways.
I've built in 32/64-bit architecture checking, and compiled and include the required missing binaries to re-enable optimizing png images and ogg files. I'm also including a .terminal file for easily configuring the default display, and a copy of my NEW favorite fixed-width font, Bitstream Vera Sans Mono.
And now some notes, and requests:
PLEASE note: this is currently INTEL only, but it supports both 32-bit and 64-bit all-in-one with architecture checking built-in to the script.
PLEASE note: if your computer is running OS X 10.7.X, "Lion" then it does not include a java runtime by default, please download it here first: http://support.apple.com/kb/DL1421
PLEASE note: due to the length of some of the strings used in the menus, etc., in order to not need to scroll your terminal window, you must adjust your default columns and rows settings. You can set this automatically by using the include "JocelynCustom.terminal" file, and you can also find simple instructions to set this yourself in the README.txt
PLEASE read the included readme for installation and very basic (for right now) usage instructions. I welcome any and all feedback on improvements for the readme file.
PLEASE report any and all bugs or generally wonky behavior, preferrably by posting here in this thread, or by posting a comment back on my blog.
LASTLY, please if you re-post this anywhere else, including blogs, other forums, etc. I would greatly appreciate if you would at least give me credit, and link back to my blog (http://girlintroverted.wordpress.com/) or at the very least, link back here to this post.
WHEN UPGRADING, DO NOT COPY OVER THE CONTENTS OF THE "other" directory or the root directory unless you absolutely know what you're doing.
IMPORTANT: Please see the second post in this thread for update notes, issues, concerns, etc. thanks
Download apk manager v2.2.5 here: http://www.mediafire.com/?o4idx4en9ldnwx4
Download migration tool v1.4 here: http://www.mediafire.com/?hbhftv9195tk86t
v3.0 BETA INFORMATION
May 11, 2012 - beta version of v3.0 is online now on github, if you want to help test it, I suggest backing up your old apk_manager directory entirely, and then going here, and reading the simple install instructions:
https://github.com/jocelynmallon/apkmanager
The basic install is pretty simple though: open terminal, cd into whatever directory you want the apkmanager folder to be created in, and run:
cd into whatever directory you want the apkmanager folder to be created in, and run:
Code:
git clone git://github.com/jocelynmallon/apkmanager.git
launch APKManager.app and follow all the instructions.
Also, git is utterly retarded when it comes to the OSX 'icon' resource files (for custom folder icons) so by default, the folder icon isn't included with 3.0+, but you can download it and apply it yourself still. Link is on the wiki here:
https://github.com/jocelynmallon/apkmanager/wiki/Basic-Information
and thank you very much to anyone that helps test this!
Cheers everyone
IMPORTANT!
5-11-2012 - v3.0 BETA notes
Some notes about the new v3.0 beta released today.
First, please backup your entire old apk_manager directory before you install/clone the 3.0 git repo. My OCD got the better of me when it came to releasing 3.0, and I ended up trashing my entire git repo/history (from v1.0-2.2.5) and starting a new history when I was ~90% through the 3.0 dev process. Because of that, your old directory will cause problems, DO NOT CLONE/INSTALL 3.0b into your old 1.X/2.X directory.
Second, for those comfortable with the command line that really want to help test APK Manager, there are four 'hidden' menu options in most menus (main menu, debug/settings menu, auto-updates menu, signing menu, clean menu) that turn on a variety of debugging options.
96) turns on 'trace mode' (set -x) for the entire script, once the main loop starts. This will make the script basically unusable for people, please only use this if you can reproduce a bug, and are saving the entire terminal output to submit an issue/error log.
97) turns on 'verbose mode' (set -v) for the entire script, once the main loop starts. This will cause some display issues, but the script will remain mostly usable.
98) turns on 'error mode' (set -e) for the entire script, once the main loop starts. This basically causes the script to exit if any condition/test/command fails. Not really useful on its own, but very useful in combination with option 96 or 97.
99) turns on a very (and I do mean VERY) simple debug information display between main apk manager header and most menus. This shows the current PID, the last exit/return code (Currently non-functional) and the last directory change.
So, if you can reproduce any bugs, please close apk manager, and delete your log.txt. Then open APK Manager again, and on the main menu, choose option 98, then next choose option 96. Then reproduce the bug, and copy/paste the entire terminal output into a log on pastebin.com, gist, etc., and send it to me. And of course, if you feel confident debugging and fixing it yourself, then fork the apkmanager repo, and send me a pull request with your changes.
4-14-2012 IMPORTANT!
An update to the issue below. This has been resolved in version 2.1 of APK Manager, and should not present any issues moving forward. However, because the old user settings and private keys were stored locally, inside the apk_manager directory, in order to save these before upgrading, I've created a migration utility/script, that needs to be run before you upgrade.
The link to this migration utility is in the original post in this thread, and the tool is also included in the APK Manager disk image starting with versions 2.1.1.
To run this tool:
mount the "Migration Utility.dmg"
Copy Migrate.app to your old root apk_manager directory.
Copy Migrate.sh to your old apk_manager/other directory.
From your old root apk_manager directory, run Migrate.app
Verify that the script completed without any errors
OPTIONAL - for those paranoid, you can double check that it worked manually. Execute the following commands in a terminal:
Code:
cd $HOME
ls -la | grep .apkmanager
cd .apkmanager
ls -la
4-13-2012 IMPORTANT!
AFFECTS all versions of apk manager prior to v2.1 (forthcoming release as of 4/13/2012.)
If you use any advanced signing functionality, you must backup your existing private key(s) and keystore(s) before upgrading to a new version of APK Manager.
Forthcoming version 2.1 will have a separate, automated, one-time backup & upgrade script to run, and all future versions will have automatic backup of key(s) and keystore(s) built in.
By default they get created and saved in the apk_manager/other/.keystores directory. This is a hidden directory by default. You can do one of several different things to unhide/view this directory, and backup your keystore(s).
I'm outlining one simple method here.
Enable 'show hidden files' in Finder. From a terminal copy and paste the following two lines:
Code:
defaults write com.apple.finder AppleShowAllFiles TRUE
killall Finder
Finder will restart after those two lines, browse to your apk_manager/other directory and make sure you see the .keystores folder (it should be dimmed compared to regular folders.)
Copy this folder and all contents somewhere safe (desktop, user home directory, user backup folder, dropbox, etc.)
Proceed with your upgrade (usually just delete the old apk_manager folder and copy over the new one, you might need to manually move project folders, etc. too)
Copy/Paste your saved .keystores directory into your new apk_manager/other folder
Test advanced signing functionality to ensure everything still works.
Once you've verified everything is working, run the following code to turn off viewing all files/folders in finder:
Code:
defaults write com.apple.finder AppleShowAllFiles FALSE
killall Finder
CHANGELOG
10-8-2012
fixed a couple bugs that were introduced with some changes to homebrew and pngcrush
updated smali.jar and baksmali.jar to version 1.4.0
fixed a few various typos
updated the built-in pngout downloader to download the newest version (May 30, 2012)
changed the "view changelog" option on the debug menu to use "git log" if you used homebrew & git to install
added the ability to forcibly reset the "home" directory by holding the command/apple key when launching APKManager.app
removed all the little "b/beta" tags I could find since this seems good enough for a "real" 3.0 release finally
4-28-2012
v2.2.5 uploaded! - Fixed "adb log" function. I have no idea how or when I broke this, but it was yet another boneheaded mistake.
4-28-2012
v2.2.4 uploaded! - Fixed a bug in the "batch sign with private key" option that would cause the signing process to fail if the key and keystore password weren't identical.
4-24-2012
v2.2.3 uploaded! - I'm retarded and somehow failed to include zipalign in every release. Fixed.
Added zipalign path information to debug/binary info screen.
Replaced all instances/uses of 'which' with 'command -v' instead.
Fixed an obscure bug that could cause infinite loop in the function to check and set png optimization tool.
4-20-2012
v2.2.2 uploaded! - Updated 32-bit optipng to v0.7.1 (Somehow I forgot to update the 32-bit binary when I last updated the 64-bit version)
Minor changes to the way debug/binary version info is scraped and displayed. I personally think this new method is cleaner, and more consistent.
Fixed bug in binary display screen (debug menu, option 2) whereby pressing "any key" did not actually close the screen and return to debug menu.
Updated other/Migrate.sh to dynamically pull the APKManager version banner from whichever other/Script.sh version is present, when its run. This should mean the end of unnecessary updates to Migration Utility.dmg, purely to bump the APK Manager version information.
4-17-2012
v2.2.1 uploaded! - Updated pngcrush to 1.7.27 (yep, that's it, lol)
4-16-2012
v2.2 uploaded! - Integrated color scheme selection into one single script, and removed the separate 'black text on light backgrounds' script file since its no longer needed.
Added new option to the "Clean" menu to reset/change color scheme.
Fixed a few obscure bugs with the apktool selection menu.
Added the actual apktool jar file in use to the debug menu information.
Changed the way the default apktool.jar symlink is created in order to prevent APK Manager from ever linking 'mod' versions by default.
Added a new custom icon for the apk_manager folder (CC by-nc-sa) Jocelyn Mallon, 2012
4-15-2012
v2.1.2 uploaded! - Fixed a bug causing decompile/compile errors due to old framework files not being deleted when changing apktool versions.
Added 2 new apktool versions, an upgraded 1.4.2 version, and 1.4.3 ICS Mod. For most instances, 1.4.3 is still the best option to use.
4-14-2012
v2.1.1 uploaded! - Fix brain-dead mistake regarding user settings & private key migration.
Packaged "Migration Utility.dmg" with APK Manager for easier upgrading from previous versions.
4-14-2012
v2.1 uploaded! - Migrated user settings and private keys to new location ($HOME/.apkmanager) to ensure preservation when upgrading.
Bumped copyright/CC info in various files to 2012
4-12-2012
v2.0.1 uploaded! - Quick hotfix for directory check/creation for advanced signing options.
4-12-2012
v2.0 uploaded! - Re-packaged into a DMG (mac disk image) file to alleviate potential unzip/setup errors.
Updated a lot of the various binaries to latest versions (adb, sox, optipng, pngcrush, etc.)
Added a new option to view java source, this has a lot of potential issues/caveats so please read the CHANGELOG.txt for more information.
Re-worked and (hopefully) simplified debug menu for the millionth time.
Added Chocolat.app to list of text editors/viewers http://chocolatapp.com/
Lots of stuff I probably missed, please read README.txt and CHANGELOG.txt for full details.
10-18-2011
v1.2.1 uploaded! - Mostly bugfixes for a few really stupid bugs I introduced in 1.2. If you had problems running APK Manager because of "missing programs" or "not in PATH" errors (from a clean install) it was my crappy coding skills, and it should be fixed now.
I honestly don't think I added any new features, just bug fixes and code cleanups.
10-10-2011
v1.2 uploaded! - Added another png tool option, pngout. Unfortunately, due to the licensing restrictions, it is illegal to redistribute the actual pngout binary, so instead, APK Manager will download and install the binary upon first attempted use of pngout. This means that if you never use pngout, it will never be downloaded.
Completely re-worked the adblog.txt function, now completely automated, and, with much clearer instructions.
Added two additional text editor/log viewer options: sublime text 2, and vico. Just like all the rest, they both require command line support to be installed in order to function.
Cleaned up adb shell, ddms, and draw9patch options so that they all now automatically close the new tabs that they open, and when necessary, will kill and re-start adb.
1.2 might be the last release. I had fun learning how to write shell script for this, but the overwhelming lack of interest in this project has already started to make it no fun for me. And well, its already basically good enough for everyday use, there's just not much else to keep adding.
10-8-2011
v1.1 uploaded! Please see Changelog.txt for full details.
switched some code back to a "portable" syntax and changed back to /bin/sh env in case users have a login shell other than bash set.
cleaned up and re-arranged debug menu again, it should be a lot less cluttered, and easier to use overall now.
fixed a few bugs in the startup check, hopefully nobody ever encountered them, they were pretty embarrassing, lol.
added option to choose between optipng and pngcrush for png optimization functions, and the setting is persistent between launches of APK Manager.
Good work man. Let me know if you'd like to collaborate or borrow ideas. I wrote Android-Utility and it is currently on v1.0.2 and development is active.
Tommy
Android-Utility Linky
tommytomatoe said:
Good work man. Let me know if you'd like to collaborate or borrow ideas. I wrote Android-Utility and it is currently on v1.0.2 and development is active.
Tommy
Android-Utility Linky
Click to expand...
Click to collapse
Hi Tommy,
Thanks for the compliment and the offer to work together. I'm not really sure how much else I'm going to add, but I did take a nod from your tool and add the option to choose between optipng and pngcrush. Mostly I added that just because optipng hasn't been updated in forever, and pngcrush just had an update last month.
So I compiled both 32-bit and 64-bit specific binaries of the newest pngcrush (v1.7.17) and included them with v1.1 of APK Manager.
Anyway, your tool is pretty amazing, I'm rather intimidated by how many features you have, lol.
Thanks again, cheers
s0niqu3 said:
Hi Tommy,
Thanks for the compliment and the offer to work together. I'm not really sure how much else I'm going to add, but I did take a nod from your tool and add the option to choose between optipng and pngcrush. Mostly I added that just because optipng hasn't been updated in forever, and pngcrush just had an update last month.
So I compiled both 32-bit and 64-bit specific binaries of the newest pngcrush (v1.7.17) and included them with v1.1 of APK Manager.
Anyway, your tool is pretty amazing, I'm rather intimidated by how many features you have, lol.
Thanks again, cheers
Click to expand...
Click to collapse
Back at you man. Yeah last week I went crazy. I went from version 1.0.2 to version 1.0.7 in three days. There's always something new that can be added.
Don't be intimidated! AU and apkmanager each have their places. I aimed to create a tool that encompasses everything to do with Android while apk manager focuses on modifying apks. Surprisingly however while I wrote the tool for mac users, I've had mote Linux users for au. But the mac community needed some love and attention, and now it has two tools to choose from
tapatalk signature here. lovely.
version 1.2 released, this might be the last release, I can't think of anything else to add really, and well, nobody really cares either, lol.
great work
1.2.1 uploaded with a few bugfixes, please re-download, and I'm really sorry I didn't catch them sooner until someone messaged me today.
Wow, this is amazing! So glad I don't need to boot into WinXP just to use apkmanager. I just downloaded the newest version, followed all instructions, and everything is working perfectly. Thanks for including all the extras such as terminal settings. Great for semi-noobs like myself.
Can't wait to try this tool out. Thanks for all the hard work in putting it together.
this not working anymore? Says applet version unsupported
Nhialor said:
this not working anymore? Says applet version unsupported
Click to expand...
Click to collapse
Yes same here
Hey,
Sorry, I'm pretty much stopped doing any work on android, but if you can describe the error in more detail, I'll look into it and try and fix the problem.
Sorry about that.
s0niqu3 said:
Hey,
Sorry, I'm pretty much stopped doing any work on android, but if you can describe the error in more detail, I'll look into it and try and fix the problem.
Sorry about that.
Click to expand...
Click to collapse
OK cool.
So it's not possible to start the setup file, because it's unsupported and starting the apk manager directly is also not possible because it has to be in the root directory
Gesendet von meinem Desire S mit Tapatalk
Kolo39 said:
OK cool.
So it's not possible to start the setup file, because it's unsupported and starting the apk manager directly is also not possible because it has to be in the root directory
Gesendet von meinem Desire S mit Tapatalk
Click to expand...
Click to collapse
Hi again,
Ok, so first, you can set the root directory manually if you open up the APKManager.command file with a text editor.
Look for the following:
Code:
# Set path to use this script in .command mode
# ENTER the POSIX path to your root APK Manager
# Directory between the quotation marks
MAINDIR=""
and inside the MAINDIR="" paste the full path to your apk_manager directory
for example, mine looks like:
Code:
MAINDIR="/Volumes/LappyHD/Android/apk_manager"
then you need to manually make the entire directory executable, so open a terminal window, and type:
Code:
chmod -R ug+x /Volumes/LappyHD/Android/apk_manager
But replace the path with the correct path for your setup (the same one you used in the .command file.)
Of course, that's not the solution for everyone, and I'd like to figure out why the setup script isn't working. I tried the setup script myself today on 10.7.3, x86_64 and it still works fine for me, so can you post some information about your mac, version information, java version installed, etc.?
sorry again about this, but hopefully I can get this fixed asap.
cheers,
s0niqu3 said:
Hi again,
Ok, so first, you can set the root directory manually if you open up the APKManager.command file with a text editor.
Look for the following:
Code:
# Set path to use this script in .command mode
# ENTER the POSIX path to your root APK Manager
# Directory between the quotation marks
MAINDIR=""
and inside the MAINDIR="" paste the full path to your apk_manager directory
for example, mine looks like:
Code:
MAINDIR="/Volumes/LappyHD/Android/apk_manager"
then you need to manually make the entire directory executable, so open a terminal window, and type:
Code:
chmod -R ug+x /Volumes/LappyHD/Android/apk_manager
But replace the path with the correct path for your setup (the same one you used in the .command file.)
Of course, that's not the solution for everyone, and I'd like to figure out why the setup script isn't working. I tried the setup script myself today on 10.7.3, x86_64 and it still works fine for me, so can you post some information about your mac, version information, java version installed, etc.?
sorry again about this, but hopefully I can get this fixed asap.
cheers,
Click to expand...
Click to collapse
I try this in the next days
My Mac Book Pro end 2011 has all updates installed (Lion 10.7.3)
---------- Post added at 05:17 PM ---------- Previous post was at 05:07 PM ----------
Ahh okay I fixed it!!!
The Unarchiver was not able to extract all files from the zip. So files doesn't work. But by using OSX Unarchiver everything works
Thanks a lot for this port!!
Kolo39 said:
I try this in the next days
My Mac Book Pro end 2011 has all updates installed (Lion 10.7.3)
---------- Post added at 05:17 PM ---------- Previous post was at 05:07 PM ----------
Ahh okay I fixed it!!!
The Unarchiver was not able to extract all files from the zip. So files doesn't work. But by using OSX Unarchiver everything works
Thanks a lot for this port!!
Click to expand...
Click to collapse
Hi again,
I'm glad you got it figured out. I think I'll start packaging it as a DMG file instead of a zip, and just made a custom background image to explain about copying the apk_manager folder somewhere.
I've also been working on updating it a little bit the past couple days, and will have a new version soon.
Cheers!
Uploaded version 2.0 update!
This adds a couple new features, some bug fixes, and re-packages the entire thing in a disk image, to hopefully alleviate those unzip/setup errors.
Please see OP for download link, and second post for changelog.
OP update with v2.0.1, hotfix for advanced signing options, please download the newest version.

Categories

Resources