# This file is used to override default values used by the Ant build system.## This file must be checked in Version Control Systems, as it is# integral to the build system of your project.# This file is only used by the Ant script.# You can use this to override default values such as#  ‘source.dir‘ for the location of your java source folder and#  ‘out.dir‘ for the location of your output folder.# You can also use it define how the release builds are signed by declaring# the following properties:#  ‘key.store‘ for the location of your keystore and#  ‘key.alias‘ for the name of the key to use.# The password will be asked during the build when you use the ‘release‘ target.key.store=【签名文件绝对路径】 key.store.password=【签名密码】key.alias=【别名】key.alias.password=【签名密码】

# This file is automatically generated by Android Tools.# Do not modify this file -- YOUR CHANGES WILL BE ERASED!## This file must *NOT* be checked into Version Control Systems,# as it contains information specific to your local configuration.# location of the SDK. This is only used by Ant# For customization when using a Version Control System, please read the# header note.sdk.dir=【sdk绝对路径】

<?xml version="1.0" encoding="UTF-8"?><project name="【项目名称】" default="help">    <!-- The local.properties file is created and updated by the ‘android‘ tool.         It contains the path to the SDK. It should *NOT* be checked into         Version Control Systems. -->    <property file="local.properties" />    <!-- The ant.properties file can be created by you. It is only edited by the         ‘android‘ tool to add properties to it.         This is the place to change some Ant specific build properties.         Here are some properties you may want to change/update:         source.dir             The name of the source directory. Default is ‘src‘.         out.dir             The name of the output directory. Default is ‘bin‘.         For other overridable properties, look at the beginning of the rules         files in the SDK, at tools/ant/build.xml         Properties related to the SDK location or the project target should         be updated using the ‘android‘ tool with the ‘update‘ action.         This file is an integral part of the build system for your         application and should be checked into Version Control Systems.         -->    <property file="ant.properties" />    <!-- if sdk.dir was not set from one of the property file, then         get it from the ANDROID_HOME env var.         This must be done before we load project.properties since         the proguard config can use sdk.dir -->    <property environment="env" />    <condition property="sdk.dir" value="http://www.mamicode.com/${env.ANDROID_HOME}">        <isset property="env.ANDROID_HOME" />    </condition>    <!-- The project.properties file is created and updated by the ‘android‘         tool, as well as ADT.         This contains project specific properties such as project target, and library         dependencies. Lower level build properties are stored in ant.properties         (or in .classpath for Eclipse projects).         This file is an integral part of the build system for your         application and should be checked into Version Control Systems. -->    <loadproperties srcFile="project.properties" />    <!-- quick check on sdk.dir -->    <fail            message="sdk.dir is missing. Make sure to generate local.properties using ‘android update project‘ or to inject it through the ANDROID_HOME environment variable."            unless="sdk.dir"    />    <!--        Import per project custom build rules if present at the root of the project.        This is the place to put custom intermediary targets such as:            -pre-build            -pre-compile            -post-compile (This is typically used for code obfuscation.                           Compiled code location: ${out.classes.absolute.dir}                           If this is not done in place, override ${out.dex.input.absolute.dir})            -post-package            -post-build            -pre-clean    -->    <import file="custom_rules.xml" optional="true" />    <!-- Import the actual build file.         To customize existing targets, there are two options:         - Customize only one target:             - copy/paste the target into this file, *before* the               <import> task.             - customize it to your needs.         - Customize the whole content of build.xml             - copy/paste the content of the rules files (minus the top node)               into this file, replacing the <import> task.             - customize to your needs.         ***********************         ****** IMPORTANT ******         ***********************         In all cases you must update the value of version-tag below to read ‘custom‘ instead of an integer,         in order to avoid having your file be overridden by tools such as "android update project"    -->    <!-- version-tag: 1 -->    <import file="${sdk.dir}/tools/ant/build.xml" /></project>

1    #!/bin/bash2    apktool="/Users/shunpingliu/GreenSoftware/apktool/apktool.jar"3    #channellist="channel.data"4    channellist="channel.data"5    ijiamifile="/Volumes/MacintoshHD/Users/liushunping/station/apk/com.hiwifi.hiwifi_20140801181424_yingyongbao.apk"    【爱加密之后的apk文件】6    java -jar $apktool d -f $ijiamifile tobuild7    for channel in $(cat $channellist)8    do9        sed -i .bak ‘145s/.*/<meta-data android:name="UMENG_CHANNEL" android:value="http://www.mamicode.com/‘${channel}‘" \/>/‘  tobuild/AndroidManifest.xml10        java -jar $apktool b tobuild com.hiwifi.hiwifi_$channel.apk11    done