导航:首页 > 版本升级 > abimaps安卓版本

abimaps安卓版本

发布时间:2023-01-17 21:30:19

⑴ abimaps签到偏差较大

莪可以解决任意位置签到及修改位置的问题,还有现场拍照都可以解决,联系莪用/户/名。

⑵ 怎么查看android abi架构

自动导入(推荐)在Mole的buid.gradle文件中添加依赖和属性配置:android{defaultConfig{ndk{//设置支持的SO库架构abiFilters'armeabi'//,'x86','armeabi-v7a','x86_64','arm64-v8a'}}}dependencies{compile'com.tencent.bugly:crashreport:latest.release'//其中latest.release指代最新版本号,也可以指定明确的版本号,例如1.2.8}

⑶ android gradle xml 配置文件的值吗

include ':app2'
project(':app2').projectDir = new File('path/to/app2')12

Mole中的build.gradle
//设置脚本的运行环境
buildscript {
//支持java 依赖库管理(maven/ivy),用于项目的依赖。
repositories {
mavenCentral()
}
//依赖包的定义。支持maven/ivy,远程,本地库,也支持单文件
dependencies {
classpath 'com.android.tools.build:gradle:0.4'
}
}
//声明构建的项目类型,这里当然是android了
apply plugin: 'android'
//设置编译android项目的参数
android {
compileSdkVersion 17
buildToolsVersion "17"

defaultConfig {
minSdkVersion 8
targetSdkVersion 17
}
//Android默认配置
sourceSets {
main {
manifest.srcFile 'AndroidManifest.xml'
java.srcDirs = ['src']
resources.srcDirs = ['src']
aidl.srcDirs = ['src']
renderscript.srcDirs = ['src']
res.srcDirs = ['res']
assets.srcDirs = ['assets']
}
//测试所在的路径,这里假设是tests文件夹,没有可以不写这一行
instrumentTest.setRoot('tests')
}

//这个是解决lint报错的代码
lintOptions {
abortOnError false
}
/**
* 签名设置
*/
signingConfigs {
myConfigs {
storeFile file("签名文件地址")
keyAlias "..."
keyPassword "..."
storePassword "..."
}
}
/**
* 混淆设置
*/
buildTypes {
release {
signingConfig signingConfigs.myConfigs
runProguard true
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
}
}
/**
* 渠道打包(不同包名)
*/
proctFlavors {
qqqq {
applicationId = '包名'
}
hhhhh {
applicationId='包名'
}
}
}
/**
* .so文件的导入
*/
task NativeLibs(type: Copy) {
from fileTree(dir: 'libs', include: 'armeabi/*.so') into 'build/lib'
}

tasks.withType(Compile) {
options.encoding = "UTF-8"
}

tasks.withType(Compile) {
compileTask -> compileTask.dependsOn NativeLibs
}
clean.dependsOn 'cleanCopyNativeLibs'
tasks.withType(com.android.build.gradle.tasks.PackageApplication) { pkgTask ->
pkgTask.jniFolders = [new File(buildDir, 'lib')]
}
//依赖库
dependencies {
compile fileTree(dir: 'libs', include: ['*.jar'])
}

一些关键词说明:
android用来指定Android打包插件的相关属性,其包含如下节点
compileSdkVersion(apiLevel):设置编译时用的Android版本
buildToolsVersion(buildToolsVersionName):设置编译时使用的构建工具的版本
defaultConfig:设置一些默认属性,其可用属性是buildTypes和ProctFlavors之和
sourceSets:配置相关源文件的位置,当你的项目的目录结构跟默认的有区别但又不想改的时候sourceSets就派上用场了
– aidl 设置aidi的目录
– assets 设置assets资源目录
– compileConfigurationName The name of the compile configuration for this source set.
– java Java源代码目录
– jni JNI代码目录
– jniLibs 已编译好的JNI库目录
– manifest 指定清单文件
– name The name of this source set.
– packageConfigurationName The name of the runtime configuration for this source set.
– providedConfigurationName The name of the compiled-only configuration for this source set.
– renderscript Renderscript源代码目录
– res 资源目录
– setRoot(path) 根目录
signingConfigs:配置签名信息
– keyAlias 签名的别名
– keyPassword 密码
– storeFile 签名文件的路径
– storePassword 签名密码
– storeType 类型
buildTypes:配置构建类型,可打出不同类型的包,默认有debug和release两种,你还可以在增加N种
– applicationIdSuffix 修改applicationId,在默认applicationId的基础上加后缀。在buildType中修改applicationId时只能加后缀,不能完全修改
– debuggable 设置是否生成debug版的APK
– jniDebuggable 设置生成的APK是否支持调试本地代码
– minifyEnabled 设置是否执行混淆
– multiDexEnabled Whether Multi-Dex is enabled for this variant.
– renderscriptDebuggable 设置生成的APK是否支持调试RenderScript代码
– renderscriptOptimLevel 设置RenderScript优化级别
– signingConfig 设置签名信息
– versionNameSuffix 修改版本名称,在默认版本名称的基础上加后缀。在buildType中修改版本名称时只能加后缀,不能完全修改
– zipAlignEnabled 设置是否对APK包执行ZIP对齐优化
– proguardFile(proguardFile) 添加一个混淆文件
– proguardFiles(proguardFileArray) 添加多个混淆文件
– setProguardFiles(proguardFileIterable) 设置多个混淆文件
proctFlavors:配置不同风格的APP,在buildTypes的基础上还可以让每一个类型的APP拥有不同的风格,所以最终打出的APK的数量就是buildTypes乘以proctFlavors
– applicationId 设置应用ID
– multiDexEnabled Whether Multi-Dex is enabled for this variant.signingConfig Signing config used by this proct flavor.
– testApplicationId 设置测试时的应用ID
– testFunctionalTest See instrumentation.
– testHandleProfiling See instrumentation.
– testInstrumentationRunner Test instrumentation runner class name.
– versionCode 设置版本号
– versionName 设置版本名称
– minSdkVersion(int minSdkVersion) 设置兼容的最小SDK版本
– minSdkVersion(String minSdkVersion) 设置兼容的最小版本
– proguardFile(proguardFile) 添加一个混淆文件
– proguardFiles(proguardFileArray) 添加多个混淆文件
– setProguardFiles(proguardFileIterable) 设置多个混淆文件
– targetSdkVersion(int targetSdkVersion) 设置目标SDK版本
– targetSdkVersion(String targetSdkVersion) 设置目标SDK版本
testOptions:设置测试相关属性
– reportDir 设置测试报告的目录
– resultsDir 设置测试结果的目录
– aaptOptions:设置AAPT的属性
– failOnMissingConfigEntry Forces aapt to return an error if it fails to find an entry for a configuration.
– ignoreAssets Pattern describing assets to be ignore.
– noCompress Extensions of files that will not be stored compressed in the APK.
– useNewCruncher Whether to use the new cruncher.
lintOptions:设置Lint的属性
– abortOnError 设置是否在lint发生错误时终止构建
– absolutePaths Whether lint should display full paths in the error output. By default the paths are relative to the path lint was invoked from.
– check The exact set of issues to check, or null to run the issues that are enabled by default plus any issues enabled via LintOptions.getEnable() and without issues disabled via LintOptions.getDisable(). If non-null, callers are allowed to modify this collection.
– checkAllWarnings Returns whether lint should check all warnings, including those off by default.
– checkReleaseBuilds Returns whether lint should check for fatal errors ring release builds. Default is true. If issues with severity “fatal” are found, the release build is aborted.
– disable The set of issue id’s to suppress. Callers are allowed to modify this collection.
– enable The set of issue id’s to enable. Callers are allowed to modify this collection. To enable a given issue, add the issue ID to the returned set.
– explainIssues Returns whether lint should include explanations for issue errors. (Note that HTML and XML reports intentionally do this – – – unconditionally, ignoring this setting.)
– htmlOutput The optional path to where an HTML report should be written.
– htmlReport Whether we should write an HTML report. Default true. The location can be controlled by LintOptions.getHtmlOutput().
– ignoreWarnings Returns whether lint will only check for errors (ignoring warnings).
– lintConfig The default configuration file to use as a fallback.
– noLines Whether lint should include the source lines in the output where errors occurred (true by default).
– quiet Returns whether lint should be quiet (for example, not write informational messages such as paths to report files written).
– severityOverrides An optional map of severity overrides. The map maps from issue id’s to the corresponding severity to use, which must be – “fatal”, “error”, “warning”, or “ignore”.
– showAll Returns whether lint should include all output (e.g. include all alternate locations, not truncating long messages, etc.)
– textOutput The optional path to where a text report should be written. The special value “stdout” can be used to point to standard output.
– textReport Whether we should write an text report. Default false. The location can be controlled by LintOptions.getTextOutput().
– warningsAsErrors Returns whether lint should treat all warnings as errors.
– xmlOutput The optional path to where an XML report should be written.
– xmlReport Whether we should write an XML report. Default true. The location can be controlled by LintOptions.getXmlOutput().
– check(id) Adds the id to the set of issues to check.
– check(ids) Adds the ids to the set of issues to check.
– disable(id) Adds the id to the set of issues to enable.
– disable(ids) Adds the ids to the set of issues to enable.
– enable(id) Adds the id to the set of issues to enable.
– enable(ids) Adds the ids to the set of issues to enable.
– error(id) Adds a severity override for the given issues.
– error(ids) Adds a severity override for the given issues.
– fatal(id) Adds a severity override for the given issues.
– fatal(ids) Adds a severity override for the given issues.
– ignore(id) Adds a severity override for the given issues.
– ignore(ids) Adds a severity override for the given issues.
– warning(id) Adds a severity override for the given issues.
– warning(ids) Adds a severity override for the given issues.
dexOptions
– incremental Whether to enable the incremental mode for dx. This has many limitations and may not work. Use carefully.
– javaMaxHeapSize Sets the -JXmx* value when calling dx. Format should follow the 1024M pattern.
– jumboMode Enable jumbo mode in dx (–force-jumbo).
– preDexLibraries Whether to pre-dex libraries. This can improve incremental builds, but clean builds may be slower.
compileOptions:设置编译的相关属性
– sourceCompatibility Language level of the source code.
– targetCompatibility Version of the generated Java bytecode.
packagingOptions:设置APK包的相关属性
– excludes The list of excluded paths.
– pickFirsts The list of paths where the first occurrence is packaged in the APK.
– exclude(path) Adds an excluded paths.
– pickFirst(path) Adds a firstPick path. First pick paths do get packaged in the APK, but only the first occurrence gets packaged.
– jacoco:设置JaCoCo的相关属性
– version 设置JaCoCo的版本
splits:设置如何拆分APK(比如你想拆分成arm版和x86版)
– abi ABI settings.
– abiFilters The list of ABI filters used for multi-apk.
– density Density settings.
– densityFilters The list of Density filters used for multi-apk.
dependencies:配置依赖

⑷ 我帮同事用abi maps签到可以吗

你可以试试看啊
如果同事确实没到
那么不能代签,那是违规

⑸ abi maps登陆不上去是怎么回事

网站封了,或者你的网络有问题

⑹ 腾讯X5内核集成-解决遇到的问题(ABI平台匹配加载理解)

上周项目有需要,集成了“腾讯X5浏览器内核”过程中,也遇到了一些问题。经过摸索,也顺带补充解决了之前ABI方面的理解。

APP,内容模块视频部分,使用时夏正流行H5技术。

Html5的Video控件播放视频,在Android平台的WebView中播放的效果,和IOS播放效果有差异。IOS点击视频部分,会用系统自带的浏览器全屏播放视频,体验效果佳;而Android的WebView无法全屏。至少体验效果比IOS上的差一些。

①Html5页面使用一些开源封装过的Video,带全屏等。

结果:产品部,认为体验不佳。提出疑问:“为什么在QQ上播放那么好呢?”,这,毕竟我们是技术方, 也不好直接说“别人技术牛”。

②重写WebChromeClient的onShowCustomView开启全屏;onHideCustomView退出全屏。

结果:相信有朋友也折腾过这玩意,在Android 4.4开始的手机,大部分不会进入该回调方法。

③技术体验上,不懂技术的同事等, 都是用QQ,微信举例。那就使用腾讯X5内核吧。

①成功调用x5内核条件是安装腾讯三个常见产品之一:1、手机QQ;2、微信;3、QQ浏览器。当然版本也有限制,到这里,我们至少知道,三者中一个,是很有可能成功的,只要版本不太低,至少身边朋友的版本,都不至于太低了。

②第一次安装集成该SDK的版本必须预热(从SDK接入文档中理解,理论上是, 大部分情况第一次是启动失败的,从试验中,是kill了进程,再开启才成功)。

③ABI只提供armeabi的.so

①导入相应的.jar,  .so 文件:

libs: tbs_sdk_v1.5.1.1057_25436_obfs_20160331_144900.jar

armeabi:liblbs.so

②预热X5内核:

/**

* 开启额外进程 服务 预加载X5内核, 此操作必须在主进程调起X5内核前进行,否则将不会实现预加载

*/

private voidpreinitX5WithService() {

Intent intent =newIntent(this,FirstLoadingX5Service.class);

startService(intent);

}

/**

* X5内核在使用preinit接口之后,对于首次安装首次加载没有效果

* 实际上,X5webview的preinit接口只是降低了webview的冷启动时间;

* 因此,现阶段要想做到首次安装首次加载X5内核,必须要让X5内核提前获取到内核的加载条件

*/

private voidpreinitX5WebCore() {

if(!QbSdk.isTbsCoreInited()) {

// preinit只需要调用一次,如果已经完成了初始化,那么就直接构造view

QbSdk.preInit(MainActivity.this, null);// 设置X5初始化完成的回调接口

}

}

③用多台手机测试:华为4A, 华为荣耀(忘记什么型号,是64位CPU),google nenux4, 小米4C, 华为mate 7, 红米Note2 等等。APP打包测试。

结果:只有我的华为4A能播放。 为什么别的,就不正常呢?

------------------------------以下-解决篇--------------------------------

①CPU方面,华为4A是比较老的CPU, 估计就是armeabi的了,由于别的机型,我都有对应的abi目录,都各自找到相应的平台目录, 所以无法加载“liblbs.so”。

②尝试将“liblbs.so”放在各个abi目录中, 结果还是没办法启动x5。

③通过网络,google等搜索,再次进行ABI方面的理解加深,获取解决方案:

项目的“build.gradle”文件defaultConfig,增加配置

ndk {

abiFilters"armeabi","armeabi-v7a","x86","mips"

}

结果:确实解决了问题。

①难道是别的平台都指向了最低兼容的armeabi目录? 噢,如果这样做的话,在APP中性能会有极大的损失。如arm-v7中的  浮点运算,这就损失极大。更何况64位的CPU。

②难道是机器是智能化了?先找相应平台的.so, 不行,再逐个查看向下的兼容平台?如果是这样,那就太好了。

③什么优先顺序呢?这个Android选取ABI的机制?我也想了解。 顺带这个问题一起学习。

①google一些资料,在overflow上,找到挺好的http://stackoverflow.com/questions/20674650/how-to-configure-ndk-with-android-gradle-plugin-0-7/21413011#21413011。

鬼老很务实, 他也有这种的疑问,从假象的提出,到论证,到结论。佩服。

文中的一些片段,我摘取一下:

To simply Link in Prebuilt Native Libraries, just add an ndk section to your task. For instance, I added it below in proctFlavors. The abiFilter is the folder name the libs are stored in. abiFilters means both libs from the comma separated list will be added to your final APK (so you could theoretically have "armeabi", "armeabi-v7a", "x86", and "mips" all in one APK, and the O/S would choose the supported architecture lib on install):

Very helpful. Thanks indeed. BTW, do you know the default search directory for user static libraries? I opt not to use the trick of "-I" in ldLibs, if possible. – weidongxu Apr 16 '14 at 20:10

how does one explore/download the files listed here?: docs.google.com/… – Cliff Apr 26 '14 at 17:47

Found the example download but now I'm facing another issue w/ Gradle 1.11. The generated Androud.mk file uses absolute paths: stackoverflow.com/questions/23344567/… – Cliff Apr 28 '14 at 16:09

Thanks for the ldlibs tricking - I just found out that ldlibs are not kept in the order you type them in, which makes using multiple static libraries just about completely unusable. Unless they're "one" argument, after which it works. Awesome! – dascandy Jan 1 '15 at 22:15

2

This is the most detailed step-by-step introction I've ever seen for ndk setup. Google should have hired you to rewrite all their documentations. – John Jul 15 '15 at 16:53

Thanks @John, nice of you to say. The closest interview to google I had was at Microsoft, but they told me I wasn't "the right fit for Microsoft" when I couldn't write a bubble sort algorithm on the board (who the frick would want to memorize that...). Actually, that was just 1 of 3 interviews, the other 2 offered me jobs, but I declined and started my own business. :) – reactive-core Oct 14 '15 at 18:49

@reactive-core, No wonder why Windows so fxxx up, they judge programmer by bubble sort algorithm! :) – John Oct 15 '15 at 7:17

add a comment

up vote

26

down vote

accepted

Found the answer. Including ndk.dir=path/to/ndk in the local.properties file did the trick.

Update: On the latest versions of Android Studio, you can set the value directly in the Project Structure > SDK location.

shareimprove this answer

edited Oct 8 '15 at 10:25

answered Dec 19 '13 at 7:13

user1906

1,1311920

Don't forget to accept your answer – orip Dec 23 '13 at 9:54

3

Is it a good idea to put something manually into the local.properties file, since it says "This file is automatically generated by Android Studio. Do not modify this file -- YOUR CHANGES WILL BE ERASED!" ?

从这对话中, 至少至少,都是能证明挺有料子的人。

OK,接下来,我也实验。

②项目中,有用到,信鸽,地图等一系列的.so文件。

我把armeabi的目录,只剩下腾讯x5内核的"liblbs.so"文件。用除了我手里的华为4A的,设备来安装apk, 非armeabi基础平台的设备,都能顺利加载x5内核。这是其次,最重要的是 armeabi目录删除的所有.so包的,功能存在。

结论:手机读取了对应手机平台的.so, 找不到"liblbs.so"的时候, 才去armeabi目录,找它。这样就很完美。符合提前提出的 疑问②。

①集成X5的APP, 第一次安装,多数手机是加载X5内核失败,取到sys core。

②back back 关闭应用,再打开仍然失败。要按 任务,“划掉“这个进程任务才成功。哎,这点,腾讯又不说,怎么做了。

① 启动 TBSDemo,等待几秒钟后看到提示框“x5内核安装成功,是否重启”,此时点击“重启” . 这句话是引用腾讯X5内核SDK接入文档(http://x5.tencent.com/doc?id=1003)

②重启体验不好吧,最后使用的方案是在 "关闭APP首页",时候彻底关闭这个进程。

@Override

public voidonBackPressed() {

//是否新装应用、或者刚更新到本次版本的应用

booleanisFist4Video = SharePreferenceUtil.getBooleanDataByKey(this,"isFist4Video", true);

if(isFist4Video){

SharePreferenceUtil.(this,"isFist4Video", false);

android.os.Process.killProcess(android.os.Process.myPid());

super.onBackPressed();

}

super.onBackPressed(); 

}

③上述虽然解决了,第一次安装,不用关闭进程,而让用户back首页关闭应用而杀进程。然而体验并不是非常好。 (这玩意测试过,对是否有问题,没有影响。只是第二次就好)

合作伙伴

微信,手机QQ,QQ空间,京东58,同城,搜狐视频,新浪新闻

这些”合作伙伴“,别人都是安装完,就正常使用的?如何做到呢?朋友们,一起讨论哦。

⑺ 越狱机不能安装abi maps吗

MAPS是一套促销员管理系统,简称MAPS。 SPR(促销员)通过手机进行签到和上报促销销量,对应主管PTL/PTA(促销主管/促销助理)可通过后台管理系统或手机查看促销员考勤和销量情况,监控并分配下属SPR的工作。

⑻ 如何创建Android库以及Android aar文件详解

创建 Android 库

Android 库在结构上与 Android 应用模块相同。它可以提供构建应用所需的一切内容,包括源代码、资源文件和 Android 清单。不过,Android 库将编译到您可以用作 Android 应用模块依赖项的 Android 归档 (AAR:Android Archive Resource) 文件,而不是在设备上运行的 APK。与 JAR 文件不同,AAR 文件可以包含 Android 资源和一个清单文件,这样,除了 Java 类与方法外,您还可以捆绑布局和可绘制对象等共享资源。

库模块在以下情况下非常有用:

阅读全文

与abimaps安卓版本相关的资料

热点内容
女汉子微信名霸气十足 浏览:65
win10手机蓝屏修复 浏览:419
windows2008激活工具 浏览:259
g71的编程应注意什么 浏览:572
文件路径不符合是什么意思 浏览:543
qq如何换绑微信绑定 浏览:67
文件包下载的安装包在哪里 浏览:811
90版本升级不送 浏览:186
工具箱英文 浏览:382
南翔嘉定编程课哪里好 浏览:853
win10改变文件格式 浏览:475
linux中的物理地址和虚拟地址 浏览:493
有哪些app可以接游戏订单 浏览:472
苹果硬盘数据恢复要多少钱 浏览:394
js绑定下拉框数据库数据 浏览:448
cad文件怎么复制到另一个文件里边 浏览:858
dxp钻孔文件 浏览:631
iphone大悦城换机 浏览:538
找结婚对象上什么网站 浏览:974
学生信息管理系统程序设计报告 浏览:640

友情链接