Database Develop

creating personalized roms

my question is this, say for example I have my phone setup just as I like with the theme of my choosing, htc music app instead of the stock android app in the cyanogen mod. i would like to be able to create a rom from this setup that I could then just load on my phone as oppsed to loading a cm mod, then installing music player, then installing the theme. before the flaming begins, i tried the search to no avail. i am aware of how to sign the zip and all of that. just a point in the right direction would be MUCH appreciated.

Its something I would like to be able to do as well. According to Haykuros twitter hes going to be making a video about android rom cooking soon so that should help

jholt0130 said:
my question is this, say for example I have my phone setup just as I like with the theme of my choosing, htc music app instead of the stock android app in the cyanogen mod. i would like to be able to create a rom from this setup that I could then just load on my phone as oppsed to loading a cm mod, then installing music player, then installing the theme. before the flaming begins, i tried the search to no avail. i am aware of how to sign the zip and all of that. just a point in the right direction would be MUCH appreciated.
Click to expand...
Click to collapse
This should've gone in the Q&A section. Will probably get locked soon.
But in response to your question, I guess you could grab the CM rom, then grab the theme you use and overwrite the files in the rom, and then overwrite the music app with the HTC music. Resign and you got your update.zip customized how you want it.

xidominicanoix said:
This should've gone in the Q&A section. Will probably get locked soon.
But in response to your question, I guess you could grab the CM rom, then grab the theme you use and overwrite the files in the rom, and then overwrite the music app with the HTC music. Resign and you got your update.zip customized how you want it.
Click to expand...
Click to collapse
Thanks for the help and my apologies for the wrong section

how do you resign it?

joey3002 said:
how do you resign it?
Click to expand...
Click to collapse
by searching.
Stericson said:
Automatic version!
Do not use this to sign APK files in Vista or windows 7! It will cause your theme to loop phones when placed on a device. Only use this to sign update files if your using those O/S's
Note, this will not work if your SDK or the path that you place this in has any spaces in the dir name!
An Example of this is c:\users\Nikki and Stephen\sdk\tools
Try to put the SDK and the contents of the zip in a dir where the names are all together and not like the one above.
I have made a batch file that will automate the entire process of setting up to use the signing tool made by JF. This batch file will set the CLASSPATH, set the PATH, install the registries, and will even allow you to sign files manually if you wish. I plan on building onto this batch file to include other things. However, for the moment, it will only include what you see here.
In order to use this you should have downloaded the sdk already. Simply extract all of the files into the tools dir of your sdk, and run autosign.bat follow the instructions and go through the options one by one, starting with 1 working through 4. You can however, put the contents of this zip anywhere on your computer and it will work. It is just better to put them into the tools dir of your SDK. Especially for the consideration of future versions.
Autosign .zip: http://www.fightforthepits.com/Androidstuff/signing.zip
Want to set up the signing tool manually?
Here is the link for the signing tool: Http://www.FightForthePits.com/testsign(2).zip
Before using this you need to know how to set this up:
Now you will need to add the tools dir of your sdk to the environment variable CLASSPATH.
FOR XP:
Right click on My Computer click properties, then choose the tab that says advanced.
Click the button that says environmental variables.
Go to system variables find the one that says CLASSPATH
double click it
go to the end of variable value.
There should be a semicolon ; at the end, type in the path to the testsign.jar located in the tools directory of your SDK
for example the path to my testsign.jar was c:\sdk\android-sdk-windows-1.0_r1\tools\testsign.jar
If CLASSPATH is not in your system variables then create it.
Secondly, Find the system variable called PATH and add to the end of it, the full path to your sdk directory.
For example, mine was c:\sdk\android-sdk-windows-1.0_r2\tools
FOR VISTA:
Open a cmd prompt.
Replace THEEXACTPATHTO-TESTSIGN with the path to the dir that holds the file testsign.jar.
Type:
echo %CLASSPATH%
If it is returns %CLASSPATH%
Type the following:
set CLASSPATH=THEXACTPATHTO-TESTSIGN\testsign.jar
If it comes back with something else then
Type the following:
set CLASSPATH=%CLASSPATH%;.;THEXACTPATHTO-TESTSIGN\testsign.jar
For Example, when I type this it looks like:
set CLASSPATH=%CLASSPATH%;.;c:\Android\SDK\tools\tests ign.jar
To set the PATH
Replace THEEXACTPATHTO-SDK with the path to the tools dir of your SDK.
Now type:
set PATH=%PATH%;.;THEXACTPATHTO-SDK\tools
For example, when I type this out it looks like this:
path-%PATH%;.;c:\Android\SDK\tools
Now through doing this you have done two things, first off you have made the resigning process extremely easy, secondly you will not have to cd to the tools dir of the sdk to use adb or any other tool in the sdk.
Signing the Files:
Now right click the reg file that you extracted and choose to install it, or merge.
Now, right click an apk, do you see an option that says ResignApk? That's how you will resign your .apks and .zips.
When you choose it a cmd window should open for a few seconds and then close. the file you signed will be overwritten with the new resigned file.
If you find the right click menu not working for some reason you can type the following in cmd to sign your files: java testsign whateverfiletosign
Click to expand...
Click to collapse

.apk's not showing up after flash in resigned .zip
Ok, so I've created a ROM to my liking. All the .apk's I normally use and got rid of the ones I don't. My problem is after I customized the ROM and flashed it none of the .apk's I added showed up. The only ones that showed up were the paid apps. I never opened the .apk's and made changes. I assume I don't need to change them to .zip resign and back to apk. Do I? I am using Windows 7 though and am able to resign no problem. Thanks to anyone who replies.

[MOD] DIY Transparent Notification Drawer for Captivate FROYO

Like the title says, this is how to modify your Notification title drawer on the Captivate with Froyo like Tatuyama's theme's drawer(notification slide) for the i9000. This will tell you how to make it transparent and add a graphic or change the colors. This has been tested on Cog B7, dont think it works on i9000 roms like Shep's. I can help you though on this if you absolutely are dieing to do it. It will just take a little fandanglin and searching but can be done. I ripped apart Shep's rom and found all of Tat's mods, I jsut dont remember them off the top of my head..
I have also attached the drop bars from Tat's theme and another black AOSP bar should you want to use it. I have also included a PSD file to modify to your liking, my APK's for the frameworks I edited below (these include the tat icons already inside), a blank black background bar to use should you want, and other goodies for your modding needs. I have also slapped some screenies below to get an idea of wtf I am even talking about. Also if you use my Frameworks be aware that I am using the battery mod version "I" from that one thread, injected Tat's icons and goodies, and other MISC things.
I will try to do this as simple as possible. I dont linger in the themes area so you are pretty much on your own. I am going to write this tutorial based on Windows O/S and Adobe Photoshop. Attempt this at your own risk. If you biff it up its not my fault. I wrote the directions as I did it, and I am working great with awesome sauce dripping from my phone. I cannot be held responsible if you are below par of the preqs listed. I assume if you are going to attempt it you are competent and comfortable with all things required. However, should you somehow mess up, I do provide some SYA (save your ass) directions below. That being said, Good luck and Mod On!
Prerequisites:
1) ADB Dev Kit and experience using it (push, pull, shell)
2) Photoshop or other photo editing software & experience
3) Basic Windows experience: cut/copy/paste/rename/zipping/moving files. (if you use linux you shouldnt worry as you more than likely are a power user already and can cross apply).
Step 1: We need to download the APK's off the phone and get them ready for editing (or yank them out of the ROM package you download).
1) open a CMD (command prompt) window type:
adb pull /system/framework/twframework-res.apk C:\
adb pull /system/framework/framework-res.apk C:\​This will save the files to your root of C:. Should you want to do it elsewhere you can specify or else leave it blank and it will stick the files in your developer kit folder.
2) (OPTIONAL BUT RECOMMENDED! STEP) Navigate to where you saved the files, right click and copy/paste to make a set of backups of these files.
3) Rename the .apk to .zip files. You can also associate your .apk to a program like WinRAR or WinZIP instead. This will open APK Files by default or optional secondary(open with). This makes the whole thing a lot easier as you can open the file(APK) and leave it up, make the edits and drop them directly back into the APK. KEEP FILE STRUCTURE PROPER!
4) Extract the APK files to seperate folders or dig out the below files for editing.
Step 2: Editing the proper files.
1) Navigate to twframework.apk's extracted folder from above or these files you extracted.
2) Find and open sub folder /res/
3) Once in /res/ find and open /drawable-hdpi/
4) Once in /drawable-hdpi/ locate the following files:
- status_bar_background.9.png (actual background of the drawer)
- status_bar_header_background.png (this is the 5 icons across the top of drawer)
- status_bar_close_on.png (this is the dropdown bar at the bottom of drawer)
- quick_panel_list_bg_01.9 (seperator between carrier and application info)
5) Open these files in Photoshop(or another editor)
6) Verify these are set to RGB not Index color mode so you can edit them.
7) Edit the layers to make them transparent. If there are not layers, right click and "create layer from background". You can then edit your layer settings. I set mine to 75% transparency in Photoshop, the actual background to 85% to darken it up a little. This will take some tweaking to get it just perfect for you. Make sure you save them in .png format with the same name they started with and not the PSD or "copy". Also you want non interlaced if it prompts you.
8) Do the same steps for the framework-res.apk.
- status_bar_item_app_background_normal.9.png (not sure if this one is necessary)
- status_bar_item_background_normal.9.png (this is teh notifications)
Step 3: Put it together and upload.
After you update the files, you will need to inject them back ito the APK's where you got them (/res/drawable-hdpi/). You can do this by opening the APK with Winzip/WinRAR/7zip and put them in there or if you extracted the entire contents just zip it all back up. You will need to remove the .zip extension if you went that route. Also, make sure you open it after zipping and verify it maintains the correct structure or you will be doing the recovery shuffle after you reboot. If you see only 1 folder in your zip this is WRONG! You need to see assets, RES, META-INF, and 2 other files in there(manifests and resources). If you see all these then you are ready to rock and roll.
After you get them back together upload them to your device using:
adb push <location of apk you edited>\framework-res.apk /sdcard/
adb push <location of apk you edited>\twframework-res.apk /sdcard/​
then in teh same command prompt window (or another, whatever)
adb shell
su
cd sdcard
cp twframework-res.apk /system/framework/twframework-res.apk
cp framework-res.apk /system/framework/framework-res.apk
reboot​
It shouldnt take but a second to come back up. You are done.
It may take a little bit of editing of the files to get them to look OK. I spent most of my day today getting mine together. You can use them if you like the "hootie edition" or just edit your own.
SEE POST #6 IF SOMETHING GOES HORRIBLY WRONG!!!!!
Screenies:
http://www.wtfokc.com/sef****/snapshot-1.pnghttp://www.wtfokc.com/sef****/snapshot-2.pnghttp://www.wtfokc.com/sef****/snapshot-3.png

That looks fantastic. I want your notification drop down and all minus the owl of course and text, but can this be done by using metamorph instead of having to adb everything?

awsome write up. Looks pretty simple and I will attempt this when I get home today.

This is an absolutely EXCELLENT tutorial. Props to you. I will be doing this shortly to all my Captivates in the house, 3 in use, plus the 4th one I'm using as a Dev phone.

Hi,
I've followed your instructions. After the files have been pushed up, my phone goes through the usual errors due to the framework change. The problem I'm having is that after I restart my phone, the phone gets past the galaxy s screen, but then it goes black and does not respond. Any suggestions?

smeltn said:
That looks fantastic. I want your notification drop down and all minus the owl of course and text, but can this be done by using metamorph instead of having to adb everything?
Click to expand...
Click to collapse
To be honest I have never used metamorph on the Captivate. On my G1 yes you could acheive that. I googled the metamorph tutorial Junkdruggler did and it looks rather lengthy and involved editing XML files. You can find that info here. Also, the files you would need to do my way with just a blank one are above. Just download the closebars zip and the "blank" zip. Then mod/inject your APK - or hell mine from above- and push it to your device. This is a rather quick ordeal.
thehavock18 said:
awsome write up. Looks pretty simple and I will attempt this when I get home today.
Click to expand...
Click to collapse
miztaken1312 said:
This is an absolutely EXCELLENT tutorial. Props to you. I will be doing this shortly to all my Captivates in the house, 3 in use, plus the 4th one I'm using as a Dev phone.
Click to expand...
Click to collapse
Thanks guys, took me a little while to figure it all out and a lot of framework pushing to get it just right Let me know how it turns out for you! Hell post some screenshots when you are done. I want to see them
gangpe said:
Hi,
I've followed your instructions. After the files have been pushed up, my phone goes through the usual errors due to the framework change. The problem I'm having is that after I restart my phone, the phone gets past the galaxy s screen, but then it goes black and does not respond. Any suggestions?
Click to expand...
Click to collapse
THIS IS HOW TO SAVE YOURSELF
Well, not sure what you mean "usual errors" with framework change? I havent ever had any issues with the framework replacements. I occasionally have then crash if I replace them while phone is on and not in recovery. A reboot fixes this though. Are you using a Cap rom or an I9000? This doesnt work on I9000 roms as thier APK's are slightly different- teh HDPI folder has a v4 at the end (IIRC). I can help you through this though if that's the case..
If it truly is a cap rom, I did experience a similar problem on my phone one time when I pushed the framework.apk. What had happened is I right-clicked the ROOT directory I had placed all the files in and said to zip it. This caused the folder to be INSIDE the zip. So the file structure went like this:
>>ZIP FILE I CREATED>>
--------->>FOLDER ALL FILES WERE IN>>
------------------>>FILE STRUCTURE OF THE ORIGINAL APK>>
Which should have been
>>ZIP FILE I CREATED>>
--------->>FILE STRUCTURE OF ORIGINAL APK>>
To better explain it- If you open the zip you created, do you see the RES folder, META-INF folder, assets folder, and then there will be 2 other files? Or do you see 1 single folder? If you see 1 single folder you zipped it up incorrectly. You will need to go into the folder and select all-> right click-> zip (send to-> compressed folder). This should fix it. If this isnt the case something else went horribly wrong. To fix it we will need to restore the original files you hopefully backed up. If you didnt back up you still arent totally hosed- just redownload the ROM you are running, open it up and navigate to the /system/framework folder and pull out the original frameworks. Then follow these instructions to get them back on the device.
Step 1:
A quick way to get out of this situation is to take the copies rename them back to twframework-res.apk and framework-res.apk (or pull from the original rom package as mentioned above).
Hopefully you have the 2e recovery kernel, as you need it to get back to where you started. If you cant do clockwork, well you may as well odin cause you are a few flashes behind anyway.
K, so first you will need to download the update.zip I have included with this post. This is the clockwork recovery file. You will next need to put your phone in reocvery mode. to do this do:
adb reboot recovery
Step 2:
Next you will need push that file you downloaded to your SD. to do that you need to:
adb push <location of downloaded>\update.zip /sdcard/
Now, once in recovery- tell it to reinstall packages. This may reboot the phone. If it does, tell it to reinstall packages again. This should get you to clockwork recovery.
Step 3:
once you have a green clockwork recovery screen, you will get the chance to SU via ADB SHELL. You can then repeat the pushing of your ORIGINAL fles back to your phone and retry the process.
You could also pull the files you pushed to see what went wrong- but do that first as if you push before they will be overwritten with the original files.

Looking into doing a little custom work but before I do. Like Tat's theme do you need to edit XML files for specific things like the pop ups being black. Or do I just get the naming right and put the proper PNG in the apk.

thehavock18 said:
Looking into doing a little custom work but before I do. Like Tat's theme do you need to edit XML files for specific things like the pop ups being black. Or do I just get the naming right and put the proper PNG in the apk.
Click to expand...
Click to collapse
This is only for the notification drawer and not the actual pop ups. If you want to edit the popups you will need to edit the XML files.

Thanks for the quick response. I might have to dive into all the XML edits.

thehavock18 said:
Thanks for the quick response. I might have to dive into all the XML edits.
Click to expand...
Click to collapse
If you do post a how to thread cause I would like to know how myself

status_bar_background.9.png (actual background of the drawer)
If I ONLY wanted to make the pull-down menu background transparent the above file would be the only one that I need to mod... correct??

jslee1020 said:
status_bar_background.9.png (actual background of the drawer)
If I ONLY wanted to make the pull-down menu background transparent the above file would be the only one that I need to mod... correct??
Click to expand...
Click to collapse
That is correct.
The one problem though is the AT&T (carrier part) at the top is also transparent and you quickly notice it looks a little strange with your items not transparent. I tried to live with it for a little bit but ended up modding the rest too.

malfuncion said:
That is correct.
The one problem though is the AT&T (carrier part) at the top is also transparent and you quickly notice it looks a little strange with your items not transparent. I tried to live with it for a little bit but ended up modding the rest too.
Click to expand...
Click to collapse
quick_panel_list_bg_01.9 (seperator between carrier and application info)
is this the file for the AT&T carrier part??

The quick panel is actually the part that says "Notifications" or "On Going" below the AT&T part. THe AT&T and clear button is part of the actual background peice. So what happens is the AT&T part becomes transparent, while the notification peices are solid. It may not bother you but it bugged the crap out of me. It's personal preference really..

malfuncion said:
The quick panel is actually the part that says "Notifications" or "On Going" below the AT&T part. THe AT&T and clear button is part of the actual background peice. So what happens is the AT&T part becomes transparent, while the notification peices are solid. It may not bother you but it bugged the crap out of me. It's personal preference really..
Click to expand...
Click to collapse
I get it. Well I'll try it out and see... I guess no better way to learn then to experience it first hand Thanks!

I was able to take the Cog Beta 7 framwork and Tat's framwork. I pulled out all the changes from his theme and put them in cog beta 7. I actually did not have to edit any files and was able to apply it.
I had to change a few file names around so all the backgrounds / pop ups applied to the theme. I left DG's background.
I don't want to post it since it is not my own work but if you want to take a look at the framwork and twframwork I can send them PM.

notification bar??
What file is the actual notification bar with the battery/clock/etc... would it be inside twframework-res.apk or framework-res.apk?
EDIT: Just set background transparency to 80% in photoshop and changed the color to black. The transparency seems ok, but it resembles minimalistic theme too much... gonna fiddle with it some more today.

jslee1020 said:
What file is the actual notification bar with the battery/clock/etc... would it be inside twframework-res.apk or framework-res.apk?
Click to expand...
Click to collapse
it is in the framework.apk. The notification bar's file is:
statusbar_background.9.png
This is confirmed. I j ust set mine to a gradient and it actually looks kind of good.
screenie:
http://wtfokc.com/sef****/snapshot-4.png

Hey Malfunction,
Finally got it working past the galaxy S screen, thanks for the info. One last question, then I should be out of your hair. Where can I change the settings for the media scanning icons? Currently, the white default icons are showing, but I'm trying to change that to the black SD card. I'm going to look into it myself too; figured I'd ask though.
Thanks,

gangpe said:
Hey Malfunction,
Finally got it working past the galaxy S screen, thanks for the info. One last question, then I should be out of your hair. Where can I change the settings for the media scanning icons? Currently, the white default icons are showing, but I'm trying to change that to the black SD card. I'm going to look into it myself too; figured I'd ask though.
Thanks,
Click to expand...
Click to collapse
Good deal, glad you got it working. What was the problem?
As for the SDCard- depends which you need. In framework-res there are these 3:
stat_notify_sdcard.png
stat_notify_sdcard_prepare.png
stat_notify_sdcard_usb.png
I had to do some hunting to find out which program was the running process for the Media Scanner. It is "MediaProvider.apk" on your /system/app folder. I edited mine and it now works and has all the Tat icons loaded. Thanks for that heads up I hadnt noticed that little piece before you mentioned it.
I looked at Tat's ROM section and also saw that he has edited these, may consider if you are wanting to mimick his:
DownloadProvider (Market)
MediaProvider (Media Scanner)
Vending (Market)
PackageProvider.apk (Uninstallation Screen)
GoogleQuickSearchBox.apk (Google Search)

[MOD] Wake on Volume Keys via android.policy.jar

This has been bothering me for awhile now. I set the phone on the table and browse or read on it. The screen goes off and now I have to pick the phone up to wake it back up. Very irritating! I'd rather be able to press the volume keys and use the pattern lock than use the fingerprint reader, when I'm not holding the phone.
I decided I'd look into this tonight and actually it turns out it's very easy. The script took longer than figuring the mod itself. Surprise, surprise, the solution is in android.policy.jar again.
This mod will make pressing the volume keys wake the phone first, then subsequent presses will change volume as usual. I won't bother with a detailed how-to this time since I put some time into a fairly complete script, but for people who are curious, here are the details:
File: KeyguardViewMediator.smali
Method: private isWakeKeyWhenKeyguardShowing(I)Z
How: Delete cases 0x18 and 0x19 in the switch statement at the bottom of the method. These tell it to return true for volume up and down keys. Careful about changing the others. Some refer to non-existent buttons on the Atrix, but others (as I found out) affect your headset mic button and other events. For a detailed how-to on taking apart and putting together the android.policy.jar, please see this thread
The script is now universal, for all ROMs. OS X, Linux, Windows.
How does it do that? Like this:
1. It takes android.policy.jar directly from your phone.
2. Decompiles the jar.
3. Patches it.
4. Recompiles it.
5. Pushes the jar back onto your phone.
6. Cleans up and reboots the phone.
Some prerequisites before you run the script:
1. Obviously make sure you're backed up. You can't hard brick with this, but there is a possibility of soft brick if there's a bug. It should be safe because it checks for errors at nearly every command, but nevertheless have CWM ready. I have tested this on OS X and Windows. Linux users, you will need to test this yourself. It should be fine though, because you use the same script as OS X, but with a different adb. Just verify that the script and adb have the correct executable permissions, or chmod as necessary.
2. You must have java installed on your computer because it needs that to compile the android.policy.jar file. To check, you can type, "java" in a command line window. If you get a "no java command" type message, then java isn't installed correctly on your machine, or you need to add the path to java.exe to your path environment variable.
3. You must be deodexed.
4. Make sure to set your USB connection to "None" on your phone.
5. On your phone, go to Settings > Applications > Development and make sure USB debugging is turned on.
6. Plug your phone into your PC and let it install any necessary drivers. (OS X users ignore this, Linux users... You're on your own )
7. Then you can run wakeonvolume.sh for OS X/Linux and wakeonvolume.bat for windows.
* Thanks to natboy for solving the script issue for XP users!

I appreciate you and your work in the development of the atrix

xredjokerx said:
I appreciate you and your work in the development of the atrix
Click to expand...
Click to collapse
I'm happy to help out my fellow Atrix users

nice work, although you could have just installed nolock from the market and be done with it don't need root and a a risky mod for it
I hate the sliding finger lock screen.. it's worthless... Yet if you disable the screen lock it doesn't go away. i consider that a bug.

maledyris said:
2. You must have java installed on your computer because it needs that to compile the android.policy.jar file. To check, you can type, "java" in a command line window. If you get a "no java command" type message, then java isn't installed correctly on your machine, or you need to add the path to java.exe to your path environment variable.
Click to expand...
Click to collapse
You need a java compiler (javac) or just the java virtual machine (java) ?
If you need a compiler then you need the java sdk not just the j2se

No error msgs, phone rebooted but mod doesn't seem to work, phone doesn't wake up.

booting up my virtual machine as we speak
i'll report results soon.

-----------------------------------------
Pick your ROM:
1) Bell
2) Stock ATT 1.83
3) GingerBlur v4
4) Gladiatrix
-----------------------------------------
'choice' is not recognized as an internal or external command,
operable program or batch file.
Copying system files...
135 File(s) copied
-----------------------------------------
Do you want the "No Hardkey Vibrations" mod?
'choice' is not recognized as an internal or external command,
operable program or batch file.
-----------------------------------------
Do you want the "Volume Keys Wake" mod?
'choice' is not recognized as an internal or external command,
operable program or batch file.
-----------------------------------------
Compiling classes.dex...
-----------------------------------------
Packaging android.policy.jar...
7-Zip (A) 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Scanning
Updating archive .\android.policy.jar
Compressing classes.dex
Compressing META-INF\MANIFEST.MF
Everything is Ok
-----------------------------------------
Cleaning up work directory...
now i believe i have the standard services.jar, because hard key vibes are back.

n1ckr0th said:
-----------------------------------------
Pick your ROM:
1) Bell
2) Stock ATT 1.83
3) GingerBlur v4
4) Gladiatrix
-----------------------------------------
'choice' is not recognized as an internal or external command,
operable program or batch file.
Copying system files...
135 File(s) copied
-----------------------------------------
Do you want the "No Hardkey Vibrations" mod?
'choice' is not recognized as an internal or external command,
operable program or batch file.
-----------------------------------------
Do you want the "Volume Keys Wake" mod?
'choice' is not recognized as an internal or external command,
operable program or batch file.
-----------------------------------------
Compiling classes.dex...
-----------------------------------------
Packaging android.policy.jar...
7-Zip (A) 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Scanning
Updating archive .\android.policy.jar
Compressing classes.dex
Compressing META-INF\MANIFEST.MF
Everything is Ok
-----------------------------------------
Cleaning up work directory...
now i believe i have the standard services.jar, because hard key vibes are back.
Click to expand...
Click to collapse
same here, no errors, but no choices

stevendeb25 said:
same here, no errors, but no choices
Click to expand...
Click to collapse
Worked for me, just make sure you run batch as admin and put it on the root of the C drive.

Looks like for one thing the script is using CHOICE which isn't available in Windows XP/NT. It was in MS-DOS and in Vista/Win 7.
I'm supplying the CHOICE.COM that came with the MSDOS supplement disks. You can google it and download it straight from Microsoft, so there shouldn't be any problems here. Unzip it and put it in the same directory the batch file is in. Also modify the batch file on the 12th line instead of choice /c 1234 put:
choice /C:1234
Edit: I haven't actually tried this yet, but that should get it going. Will try in a few..
Edit 2: This should only be needed if you're running WinXP/NT. I'm assuming it works under Win7 already.
Edit 3: It works! Once I added the choice.com file and modified the script as stated above, it worked on my XP box. Thanks for the mods OP! FYI, I'm on Gladiatrix v3.
Edit 4: Sorry for keep editing this post I must be bored at work today. With this latest edit, I'm uploading a zip for XP that has the choice.com file in it and the script modified to work with it. I'd think it'd work in Win7 also, but someone should test it to try it out.

natboy said:
Looks like for one thing the script is using CHOICE which isn't available in Windows XP/NT. It was in MS-DOS and in Vista/Win 7.
I'm supplying the CHOICE.COM that came with the MSDOS supplement disks. You can google it and download it straight from Microsoft, so there shouldn't be any problems here. Unzip it and put it in the same directory the batch file is in. Also modify the batch file on the 12th line instead of choice /c 1234 put:
choice /C:1234
Edit: I haven't actually tried this yet, but that should get it going. Will try in a few..
Edit 2: This should only be needed if you're running WinXP/NT. I'm assuming it works under Win7 already.
Edit 3: It works! Once I added the choice.com file and modified the script as stated above, it worked on my XP box. Thanks for the mods OP! FYI, I'm on Gladiatrix v3.
Edit 4: Sorry for keep editing this post I must be bored at work today. With this latest edit, I'm uploading a zip for XP that has the choice.com file in it and the script modified to work with it. I'd think it'd work in Win7 also, but someone should test it to try it out.
Click to expand...
Click to collapse
thank you so much natboy!
worked for me!
maleydris i love your mods, if i had a way of donating i would.

natboy said:
Looks like for one thing the script is using CHOICE which isn't available in Windows XP/NT. It was in MS-DOS and in Vista/Win 7.
I'm supplying the CHOICE.COM that came with the MSDOS supplement disks. You can google it and download it straight from Microsoft, so there shouldn't be any problems here. Unzip it and put it in the same directory the batch file is in. Also modify the batch file on the 12th line instead of choice /c 1234 put:
choice /C:1234
Edit: I haven't actually tried this yet, but that should get it going. Will try in a few..
Edit 2: This should only be needed if you're running WinXP/NT. I'm assuming it works under Win7 already.
Edit 3: It works! Once I added the choice.com file and modified the script as stated above, it worked on my XP box. Thanks for the mods OP! FYI, I'm on Gladiatrix v3.
Edit 4: Sorry for keep editing this post I must be bored at work today. With this latest edit, I'm uploading a zip for XP that has the choice.com file in it and the script modified to work with it. I'd think it'd work in Win7 also, but someone should test it to try it out.
Click to expand...
Click to collapse
Ah, sorry guys! I didn't realize that wasn't part of XP!
And thank you natboy! I'll update the OP when i'm home from work
Sent from my MB860 using XDA Premium App

franciscojavierleon said:
You need a java compiler (javac) or just the java virtual machine (java) ?
If you need a compiler then you need the java sdk not just the j2se
Click to expand...
Click to collapse
No, you don't need the compiler, just the vm.
Sent from my MB860 using XDA Premium App

franciscojavierleon said:
nice work, although you could have just installed nolock from the market and be done with it don't need root and a a risky mod for it
I hate the sliding finger lock screen.. it's worthless... Yet if you disable the screen lock it doesn't go away. i consider that a bug.
Click to expand...
Click to collapse
Nah, why would I want to completely get rid of lock? It's useful to me. I also like the fingerprint reader. I just want to be able to wake the phone's screen without resorting to the recessed power button. I'm generally satisfied with the locking mechanism as it is.
Granted, the script is risky as we've found the mod itself though is very clean and it's very clear cut what the code is doing there.
Sent from my MB860 using XDA Premium App

The command to remount system should be
Code:
mount -o rw,remount /dev/block/mmcblk0p12 /system

maledyris said:
Ah, sorry guys! I didn't realize that wasn't part of XP!
And thank you natboy! I'll update the OP when i'm home from work
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Glad to help, thanks for the mod. I find it easier to unlock the phone now, by pushing the volume key with my thumb and swiping with my finger. Pushing the back button with the finger and sliding seemed to herky jerky to me.

thanks natboy modphone.zip working on xp
thanks maledyris for the original mod
great mod love it guys

You guys should try out no lock. It gets rid of the lock screen and allows you to wake up the phone with the volume keys.

rdubyah said:
You guys should try out no lock. It gets rid of the lock screen and allows you to wake up the phone with the volume keys.
Click to expand...
Click to collapse
yeah, but then it gets rid of the lock screen, which defeats the purpose of what the OP wanted.

★wildstang83's Guide For Basic Porting★

★wildstang83's Guide For Basic Porting★
You could always go to the TEAM REVERSE website and read the same guide, lol​
Disclaimer​It should be known that there is some risk involved when performing the porting method described below. If you still wish to continue on and follow this guide you are doing so at your own risk. Of course, I will not be held liable for what you do to your device on your own. I will say, use extreme caution and follow every step to its tiniest detail.​
Click to expand...
Click to collapse
Hey guys, I have had a few new users come to me wanting to learn how to port. So I have decided to take a little time and write up a guide for this subject. With this guide we will achieve at minimum a first time boot with Screen load and sound. This will not go into details of fixing G Sensor, MMS, eMMC, Cam or Netflix.​
NEEDED ITEMS:
Windows- Either 32 or 64 bit is fine. Ubuntu will work but is more complex.
7Zip
Notepad++
Android SDK
Android Kitchen
Our most recent Ginger Sense Leak ROM 4.01.605.0
Any Sense 1.0 or 2.1 ROM from the EVO Shift 4G, EVO 4G, HTC Desire. These 3 devices are the easiest to port from. Personally I find that the --EVO 4G is the easiest out of these three and is usually where I port from. Whatever ROM you choose must be deodexed for this guide.
A generic updater-script, update-binary and build.prop. I'll provide those in a link below.
From here on each rom will be refered to in this guide as such:
HTC Droid Incredible GingerSense Leak= Leak
Whatever ROM you choose to port= Port
Ok lets get it.
First things first. Take some measurements of file size.
Take the following size readings:
Ports zipped file size on disk:
Ports unzipped file size on disk:
Ports "system" folder size on disk after extraction: <---This is important!!!
Click to expand...
Click to collapse
We need to know the pre and post system folder size because the system has a max usage space of 250 MB. So in your final rom a system folder size that is below 250 is good. For example, in my latest build of my Pure Speed ROM I was able to achieve a system folder size of 163MB.
Phase One- Start with the Android Kitchen
Open the Android Kitchen and place your port into the original_update folder. Run the kitchen and go through the steps to make your working folder. Just hit enter whenever it asks any questions even when it asks about updater conversion. Once complete, choose the Option 2- Add root permissions. It may say 'su' already present just over ride it and choose option "f" ChainsDD's version. That will complete and go back to the main menu. Select option 3. Add Busy Box. Do the same thing. Now select option 0 for advanced options. In advanced options select option 17 to install busy box runparts. Once that finishes we can build the ROM. Select option 99, let it run then select option 1 for interactive mode, let it run, Then select "y" to zipalign the apks. it will run for awhile and then ask to convert back to updater-script. just hit enter for yes. hit enter to sign the rom. It will ask about renaming, just hit enter to by pass this. We will rename it later. It will say congratulations your rom is done or whatever. just hit enter and then close completely out of the kitchen. Go to where your kitchen is set-up and find a folder called OUTPUT_ZIP. Grab your rom out of there and place it on your desktop.
Phase Two- The actual porting operations
For good measure create two folders on your desktop. One called "Backup" and the other called "Dump". Both the leak and the port should now be on your desktop. Select them both and copy them to your backup folder you just created. Now open your port by right clicking it and navigating to 7Zip and clicking "open archive". Drag it to the edge of your screen. Open the dump folder so that it is side by side with the port. Now in the port navigate to the system folder. Select the "customize, lib and media" folders and drag them to your dump folder. Now delete them from your port along with the "usr" folder as well. You will see a folder in system named "etc". Open that folder and inside you will see a folder called "firmware". Delete the firmware folder. Also delete the "wimax" folder. We do not need it. Now open the Leak. navigate to system/etc and drag the firmware folder from leak to the port. Also drag AudioBTID.csv and vold.fstab from the leak to the port. Close the leak for now. In the port back up to the system folder. Open the bin folder and delete EVERYTHING with "a2sd, apps2sd or wimax" in its name. If there isn't any such things in there then don't worry about it. Now back up to system and go into "xbin". Do the same thing here. Once complete grab the "su" and "busybox" files and drag them to your dump folder on your desktop. Back up to system. Open bin. Drag those two files su and busybox from your dump folder to your ports bin folder. You should now have "su" and "busybox" in both of your ports bin and xbin folders. Now in the port back all the way to the root of the ports zip. You may see a folder called "data". Delete that folder and recreate it. just do it. Now open the data folder. In the dump folder on your desktop create a new folder called 'sysusr". Rename the "customize, lib and media" folders so they are "syscustomize, syslib and sysmedia" These folders are named so because they will be symlinked. Now drag these four folders to the data folder of the port. You can now delete the dump folder from your desktop. We don't need it anymore. Close everything thats open right now. Reopen both the leak and the port side by side. Of the leak navigate to system/usr. Of the port navigate to data/sysusr. Drag the contents only of the leaks usr folder to your ports sysusr folder. Navigate to system/lib of the leak. Navigate to data/syslib of the port. In the syslib folder of the port find the three folders called "egl, hw and modules" Delete them. Drag those same folders over from the leak to the port. Now in the leak system/lib folder find these files: libaudio.so, libaudioalsa.so, libaudioeffect_jni.so, libaudioflinger.so, libaudiopolicy.so, libAudioTrimmer.so, libEGL.so, libgsl.so, libhtc_ril.so and libhtc_ril_switch.so. Drag them to your ports data/syslib folder. Just drag and drop. Close everything on your screen. Reopen both the leak and the port side by side. In the port delete the boot.img and drag the boot.img from the leak over. Close the leak. navigate to "META-INF\com\google\android" of the port and drag and drop in the update-binary and updater-script that I have provided below. Navigate to system of the port and drag and drop the build.prop that I have provided below. one last thing. navigate to system/etc and drop in the apns-conf.xml that I have provided below. Close the port.
Porting is now complete​
We should now be ready to boot. Rename the ports zip if you like and drop it on your sd card, wipe and flash. If it boots, has sound and is somewhat usable pat your self on the back. You've just took the second step to becoming a great dev in the Android world. The first step was having the guts to even attempt this.
Here are those parts you need: wildstang83's Porting Parts​
Guide- How to customize your 2.1/3.0 Hybrid or 3.0 ROM lockring: http://forum.xda-developers.com/showthread.php?p=15681779#post15681779
Click to expand...
Click to collapse
If you run into any trouble while using my guide or notice anything that needs to be updated or added please feel free to PM me.
Credits:
PonsAsinorem- For giving me the idea to write this guide.
newtoroot- I'll never forget who took the time to teach me how to port.
joelZ9614- Allways being supportive especially when times were tuff and no one else was around.
wdfowty
NilsP
Conap
gnarlyc
Man the list goes on so really just a huge thank you to everybody!
Click to expand...
Click to collapse

Thanks! Been wanting to do this for a bit.

lol
10 characters

Guide made me 'lol'.

Alright guys, enough goofing around, lol
I added the whole guide for yall.

Sorry for those trying to read this in the xda app. It gets cut off around where it talks about the system size. You can just hit menu/browser and read it that way.

Porting a HTC Desire ROM tomorrow morning Thank you!

cbren said:
Porting a HTC Desire ROM tomorrow morning Thank you!
Click to expand...
Click to collapse
Good luck buddy. Let me know how it goes or if you need help.

Thanks stang
Sent from my ADR6300 using XDA Premium App

Thanks stang
Youre looking at a crackflashing troll with ORD

WoZZeR999 said:
Guide made me 'lol'.
Click to expand...
Click to collapse
The disclaimer made me lol

Wow this is great bro. I have to try this out!

When I try and flash my port, I get
Finding update package...
Opening update package...
Installing update...
Installation aborted.
It's an evo port and Android 2.3.3 Htc sense 2.1 I think.
http://forum.xda-developers.com/showthread.php?t=1046622

Same one I used and it worked perfectly just try again... follow stangs directions exactly as they're written..
Sent from my ADR6300 using XDA Premium App

Guys, if you are gonna report errors here please provide the error status as well.
It will make it easier for me and everyone else to see what you did wrong(not saying anything bad here) and to know what to look for next time.
A lot of problems can be solved by mounting usb through recovery and then transfering your ports over.

What do we use the OUTPUT_ZIP ROM for? Is that the "port" that we should be messing with?

cbren said:
What do we use the OUTPUT_ZIP ROM for? Is that the "port" that we should be messing with?
Click to expand...
Click to collapse
Yes thats the final rom that you zipaligned and rooted in the kitchen. Now take that and put it on your desktop and build it exactly as my instructions say and you should be good.

Will there be an " Advanced Porting " Thread? If so can you shed some light on github?

hightech316 said:
Will there be an " Advanced Porting " Thread? If so can you shed some light on github?
Click to expand...
Click to collapse
Im not a compiler. Im a porter. I'm sure we could get some info in here though.

hightech316 said:
Will there be an " Advanced Porting " Thread? If so can you shed some light on github?
Click to expand...
Click to collapse
What kind of github info do you need? I'm no where near an expert, but I know how to sync a repo from github to my computer. That's all I've ever needed to do, at least so far.

[MOD] Lower Auto-Brightness levels to save battery

This is best done after you flash a ROM as you might lose some settings.
(I noticed my wall paper changed and i had to sign back into Google account)
---This framework-res.apk file is different for every ROM---
Hi,
I wanted to share a little mod that could help in extending battery life - lowering default auto-brightness levels. As all of You know our big, bright SuperLCD is an excelent display but for that it uses most of our battery:/
I like the idea of auto-brightness but I find it too bright for most of the time. Setting brightness manualy to one level makes it either too dim or it uses too much battery and switching it all the time that You go outside or turn on the light is a little bit inconvenient.
In order to lower auto-brightness levels You have to change values in framework-res.apk/res/values/arrays.xml and here is how (read whole post first )
These are stock HTC Raider values:
Click to expand...
Click to collapse
Code:
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>75</item>
<item>75</item>
<item>75</item>
<item>97</item>
<item>120</item>
<item>142</item>
<item>170</item>
<item>198</item>
<item>227</item>
<item>255</item>
</integer-array>
These are values that I use and found best for me:
Code:
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>20</item>
<item>40</item>
<item>50</item>
<item>70</item>
<item>90</item>
<item>100</item>
<item>130</item>
<item>155</item>
<item>180</item>
<item>225</item>
</integer-array>
These brightness levels are corresponding to the amount of light that light sensor is getting - the lowest value is while in the low light the highest when for example your phone is in direct sunlight. Brightness values are defined by numbers 1 is the lowest possible setting and 255 is the maximum brightness that can be set.
As You can see I was pretty aggressive with lowering these values and yet the screen is still bright in every situation. You can set them a little bit higher or lower in order to suit your preferences.
Here is a guide on how to perform this mod on any framework-res.apk using apk manager (thanks for the guide goes to desean):
1. Download APK manager and unpack somewhere
2. Grab framework-res.apk from your phone under \system\framework\ (e.g. adb pull) and place it in the "place-apk-here-for-modding" folder
3. Run Script.bat and select option 9
4. Once done, go to projects\framework-res.apk\res\values\arrays.xml and edit your values as per first post.
5. Once edited, compile the apk using option 11
6. Qn: Is this a system apk. Ans: y
7. Qn: Aside from the signatures, would .... least. Ans: y
8. Prompt: In the apk manager folder u'll find a keep folder..... done then press enter on this script. Press any key to continue . . . You have to go to "keep" folder and delete resources.arsc because arrays.xml have been changed. After this You can press any key in apk manager window.
9. Once done, input 25 in apk manager and select "unsignedframework-res.apk" by entering the number that stands for it. After selecting it You should see in apk main window in the top right corner "Current-App: unsignedframework-res.apk".
10. Now press 5 to zipalign apk. You will find your completed, zipaligned apk under place-apk-here-for-modding\unsignedframework-res.apk.
11.Rename it back to framework-res.apk and adb push the file back to your phone
Click to expand...
Click to collapse
To send it back to your phone
Prerequisites have...
The file you are pushing must be placed in the platform-tools folder of adb so if you are pushing file "framework-res.apk" this needs to be downloaded/copy and pasted in C:\android-sdk-windows\platform-tools
1: go to run and type cmd (or just open your command prompt)
2: cd C:\android-sdk-windows\platform-tools
3: adb remount
4: adb devices *if everything is set up right this should output a serial number*
5: adb push FFFFFFF.FFF /#####/###### *i hope my notes help here you need to put the file name in for the F(s) and in the pound signs you put the destination on the devices:
Code:
adb push framework-res.apk /system/framework
7. adb reboot this is how you finish
Click to expand...
Click to collapse
You have to copy the file to your phone with ADB or you will get a boot loop and have to re install your ROM.
Link for APK Manager HERE
If you have problems with apk manager showing java error (like it did) this post helped me fix that
Sources:
http://forum.xda-developers.com/showthread.php?t=1235212
http://forum.xda-developers.com/showthread.php?t=695701
http://forum.xda-developers.com/showthread.php?t=642437
APK Manager 4.9 download link (currently original thread link down)
http://www.zshare.net/download/99034654c32618ba/

WOW! I was just about to ask if anyone knew how to accomplish this! Thanks dude!
Edit: Er..phone just went into a bootloop. Lemme try again..
Edit2: I first replaced the framework-res.apk using root explorer...big mistake, phone went into a bootloop and I couldnt adb to it to push the apk correctly, whoops. Just reinstalled the ROM I was using and pushed the apk using adb and all is well.
I noticed two other very similar looking values: config_autoBrightnessLcdBacklightValuesUp and config_autoBrightnessLcdBacklightValuesDown. Is it necessary to change these as well?

m0biusace said:
WOW! I was just about to ask if anyone knew how to accomplish this! Thanks dude!
Edit: Er..phone just went into a bootloop. Lemme try again..
Edit2: I first replaced the framework-res.apk using root explorer...big mistake, phone went into a bootloop and I couldnt adb to it to push the apk correctly, whoops. Just reinstalled the ROM I was using and pushed the apk using adb and all is well.
I noticed two other very similar looking values: config_autoBrightnessLcdBacklightValuesUp and config_autoBrightnessLcdBacklightValuesDown. Is it necessary to change these as well?
Click to expand...
Click to collapse
Yes you have to use adb ill put that in the first post,
to be honest i am not entirely sure what that is for i assume, that it is when you move the slider what values it displays when you slide it, i noticed a change without changing those values.
also i changed the button back lights to 200, i find it more than enough for me.

Is there a working mirror to APK manager? The link in the thread is down.

uploaded
sbddude said:
Is there a working mirror to APK manager? The link in the thread is down.
Click to expand...
Click to collapse
uploaded here
http://www.zshare.net/download/99034654c32618ba/

Serious props to you jul644 for detailing this process! I've always hated how the Hero, Evo, & now Vivid I've had never got dark enough in pitch black rooms, and now I'm excited to fix that problem. I was curious though since I just modded my battery meter using UOT Kitchen, if I could drop in the backlight-modded framework-res.apk via 7-zip replacing the UOT framework-res.apk file then flash it via recovery. I wonder if that would make me sign into Google and mess with settings like you mentioned. Thanks.

How-To with UOT
jul644 said:
You have to copy the file to your phone with ADB or you will get a boot loop and have to re install your ROM.
Click to expand...
Click to collapse
How, if it's possible, do we integrate this modded framework-res.apk into a UOT Kitchen zip flash file? I want to mod my battery icons and would like to install at the same time so one doesn't interfere with the other. Should I upload the framework-res.apk from this to UOT Kitchen (with my original SystemUI.apk) and then change the battery icons, then download and flash?
Thanks for your help!
*****EDIT - 2/15/2011*****
Ok so I did the framework-res.apk edits by decompiling/recompiling per jul644, uploaded that into UOT Kitchen along with original SystemUI.apk and com.htc.resources.apk. I chose my battery icon mod, downloaded, cleared all the caches and flashed in recovery with no problems ) Just wanted to let you guys know how to make it a recovery flashable zip instead of pushing via ADB.

ICS?
So can anyone confirm or deny if this still works wit ICS will be trying it myself, when I get a chance, but would rather not waste time if it wont work!

It does work, I have done it. ICS it's just more difficult to decompile & recompile. I added it & 1% stock-style battery icons into Pirateghost's CWM .56 flashable ROM.

Keep getting errors when recompiling using stock telstra ICS+ root
error on 1st line after selecting option 11 ie. step 5 above
could not find sources????
Any suggestions what I am doing wrong????
---------- Post added at 09:37 PM ---------- Previous post was at 09:24 PM ----------
okay also getting this error twice before it de-compiles
the system cannot find the path specified
then seems to decompile happily???????????
Any suggestions?

I'm getting an 'Operation not permitted' when I try to remount before pushing the file back. Anyone else having this problem? I'm running a WCX GB ROM (no ICS, I'm on Rogers).

formicae said:
I'm getting an 'Operation not permitted' when I try to remount before pushing the file back. Anyone else having this problem? I'm running a WCX GB ROM (no ICS, I'm on Rogers).
Click to expand...
Click to collapse
are you trying to remount your sd card? if so do not, just select charge only

No, just trying to remount as per the instructions in the first post, so /system is R/W. Setting it to charge only. No dice.
I tried doing it in recovery (by mounting /system, then going through the ADB commands, all of which are successful), but the result is a bootloop once I'm done.
Edit: It's also worth noting that newer versions of APK Manager/Multi-tool seem to have different numbering for the operations. In step 9, number 22 sets the compression level, whereas I think it used to set the active APK (which I think is 25 now).

I ended up taking the stock framework-res from the ROM, modifying the arrays.xml values as per the OP instructions, then going through the UOT Kitchen (I had a battery mod anyway). Worked perfectly.
Thanks to pauley for reporting success earlier, which provided me with the workaround.

Has anyone done this that could possibly create a flashable zipped version of it? I tried to do it myself but with the new APK Multi Tool things were different to the instructions of OP and I couldn't get it to work
Edit: Nvm managed to fix it and make my own flashable zip. Thanks for the effort OP

I have tried to do this... And I keep getting an error on the recompile side...
Just wondering... Does apkmanager require windows 7 or something... Or is there some reason it wouldn't work on windows xp?
Sent from my HTC PH39100 using Tapatalk 2

rignfool said:
I have tried to do this... And I keep getting an error on the recompile side...
Just wondering... Does apkmanager require windows 7 or something... Or is there some reason it wouldn't work on windows xp?
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
The errors I encountered when compiling were solved by:
1) Putting Java in the windows path
2) Putting ADB in the windows path
3) Not having any spaces in the APK Manager file path
There are no OS dependencies that I'm aware of. Just open the log from within the APK manager and you should be able to identify the error.

The problem is I don't really speak java all that well...
Could I just move the java executable to the working directory?
Sent from my HTC PH39100 using Tapatalk 2

rignfool said:
The problem is I don't really speak java all that well...
Could I just move the java executable to the working directory?
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
For java, all you have to do is download the JDK (i got the 32 bit version), and then add 'C:\Program Files (x86)\Java\jdk1.7.0_03\bin' to the windows path so it becomes something like:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\MATLAB\R2011a\runtime\win64;C:\Program Files\MATLAB\R2011a\bin;C:\Program Files (x86)\MKVToolNix;C:\Program Files (x86)\Java\jdk1.7.0_03\bin;C:\Android\android-sdk\platform-tools\;C:\Android\APKMultiTools\
For Windows XP, you'd probably be running 32 bit and so it would be installed in the regular program files.

pod0087 said:
For java, all you have to do is download the JDK (i got the 32 bit version), and then add 'C:\Program Files (x86)\Java\jdk1.7.0_03\bin' to the windows path so it becomes something like:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\MATLAB\R2011a\runtime\win64;C:\Program Files\MATLAB\R2011a\bin;C:\Program Files (x86)\MKVToolNix;C:\Program Files (x86)\Java\jdk1.7.0_03\bin;C:\Android\android-sdk\platform-tools\;C:\Android\APKMultiTools\
For Windows XP, you'd probably be running 32 bit and so it would be installed in the regular program files.
Click to expand...
Click to collapse
thanks for the help! can you tell me the new number system with apk manager?