When you install an APK on Android, the system will look for native libraries directories (armeabi, armeabi-v7a, arm64-v8a, x86, x86_64, mips64, mips) inside the `lib` folder of the APK, in the order determined by `Build.SUPPORTED_ABIS`.

If your app happen to have an `arm64-v8a` directory with missing libs, the missing libs will not be installed from another directory, the libs aren&#39;t mixed. That means you have to provide the full set of your libraries for each architecture.

So, to solve your issue, you can remove your 64-bit libs from your build, or set abiFilters to package only 32-bit architectures:

    android {
        ....
        defaultConfig {
            ....
            ndk {
                abiFilters &quot;armeabi&quot;, &quot;armeabi-v7a&quot;, &quot;x86&quot;, &quot;mips&quot;
            }
        }
    }

The above answer will help to generate a build with 32- bit only not a 64-bit. If you are using  [ abiFilters &quot;armeabi&quot;, &quot;armeabi-v7a&quot;, &quot;x86&quot;, &quot;mips&quot;  ]. generate signed apk means, that is not for 64 bit. It will raise an error when we upload into Google Play store. It is not an 64 bit build.

I&#39;m attempting to create a UIImage (like a thumbnail or something) from a PHAsset so that I can pass it into something that takes a UIImage. I&#39;ve tried adapting solutions I found on SO (since they all just directly pass it into say a tableview or something), but I have no success (likely because I&#39;m not doing it right).

    func getAssetThumbnail(asset: PHAsset) -&gt; UIImage {
        var retimage = UIImage()
        println(retimage)
        let manager = PHImageManager.defaultManager()
        manager.requestImageForAsset(asset, targetSize: CGSize(width: 100.0, height: 100.0), contentMode: .AspectFit, options: nil, resultHandler: {(result, info)-&gt;Void in
                retimage = result
        })
        println(retimage)
        return retimage
    }

The printlns are telling me that the manager.request line isn&#39;t doing anything right now. How do I get it to give me the asset as a UIImage.

Thanks.

PHAsset to UIImage

One of the dependencies declared in my project has a transitive dependency on `&#39;com.google.guava:guava:15.0&#39;`. But my application deployed on WAS/Weblogic doesn&#39;t work due to a CDI issue which has been fixed in `&#39;com.google.guava:guava:15.0:cdi1.0&#39;`. (same version, but with classifier) I need to tell gradle to use this jar during build and packaging. I am trying to figure on how we can ovrride this transitive dependency with a jar specific version classifier.

Tried the following approches:

 1. Added the dependency explicitly: `compile &#39;com.google.guava:guava:15.0:cdi1.0&#39;`. But both jars got included in the resultant WAR.
 2. Added the dependency explicitly and defined a resolution strategy:

        configurations.all {
            resolutionStrategy {
	            force &#39;com.google.guava:guava:15.0:cdi1.0&#39;
            }
        }
Even this didn&#39;t work.

 3. Defined a resolution strategy to check and change the version.

        configurations.all {
             resolutionStrategy.eachDependency { DependencyResolveDetails details -&gt;
    		     if (details.requested.group + &quot;:&quot; + details.requested.name == &#39;com.google.guava:guava&#39;) {
    	            details.useVersion &quot;15.0:cdi1.0&quot;
    	            //details.useTarget &quot;com.google.guava:guava:15.0:cdi1.0&quot;
    	        }
    	    }
        }
Even this didn&#39;t work.

Need your suggestions on how this issue can be tackled.

Gradle: Override transitive dependency by version classifier

I use a native library in my application that is only compiled for armeabi, armeabi-v7a and x86.

When this library is loaded on a 64-bit device like the Samsung S6, the application crashes with an UnsatisfiedLinkError

    java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file &quot;/data/app/com.myapp-2/base.apk&quot;],nativeLibraryDirectories=[/data/app/com.myapp-2/lib/arm64, /vendor/lib64, /system/lib64]]] couldn&#39;t find &quot;libfoo.so&quot;
	    at java.lang.Runtime.loadLibrary(Runtime.java:366)
	    at java.lang.System.loadLibrary(System.java:989)

The library is closed source unfortunately. Is there any way to fix this without recompiling the library with 64-bit targets?

How to use 32-bit native libraries on 64-bit Android device

I use a native library in my application that is only compiled for armeabi, armeabi-v7a and x86.
When this library is loaded on a 64-bit device like the Samsung S6, the application crashes with an UnsatisfiedLinkError
<pre><code class="hljs language-javascript">java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.myapp-2/base.apk"],nativeLibraryDirectories=[/data/app/com.myapp-2/lib/arm64, /vendor/lib64, /system/lib64]]] couldn't find "libfoo.so"
 at java.lang.Runtime.loadLibrary(Runtime.java:366)
 at java.lang.System.loadLibrary(System.java:989)
</code></pre>
The library is closed source unfortunately. Is there any way to fix this without recompiling the library with 64-bit targets?

My app generates a notification, but the icon I set for that notification is not being displayed. Instead, I get a white square.

I have tried resizing the png of the icon (dimensions 720x720, 66x66, 44x44, 22x22). Curiously, when using smaller dimensions the white square is smaller.

I have googled this problem, as well as the correct way of generating notifications, and from what I&#39;ve read my code should be correct. Sadly things are not as they should be.

My phone is a Nexus 5 with Android 5.1.1. The problem is also present on emulators, a Samsung Galaxy s4 with Android 5.0.1 and a Motorola Moto G with Android 5.0.1 (both of which I borrowed, and don&#39;t have right now)

The code for notifications follows, and two screenshots. If you require more information, please feel free to ask for it.

Thank you all.

    @SuppressLint(&quot;NewApi&quot;) private void sendNotification(String msg, String title, String link, Bundle bundle) {
		NotificationManager notificationManager = (NotificationManager) getSystemService(NOTIFICATION_SERVICE);
		Intent resultIntent = new Intent(getApplicationContext(), MainActivity.class);
		resultIntent.putExtras(bundle);
		PendingIntent contentIntent = PendingIntent.getActivity(this, 0,
				resultIntent, Intent.FLAG_ACTIVITY_NEW_TASK);
		Notification notification;
		Uri sound = Uri.parse(&quot;android.resource://&quot; + getPackageName() + &quot;/&quot; + R.raw.notificationsound);
        notification = new Notification.Builder(this)
					.setSmallIcon(R.drawable.lg_logo)
					.setContentTitle(title)
					.setStyle(new Notification.BigTextStyle().bigText(msg))
					.setAutoCancel(true)
					.setContentText(msg)
					.setContentIntent(contentIntent)
					.setSound(sound)
					.build();
		notificationManager.notify(0, notification);
	}

![without opening the notification][1]
![notifications opened][2]


  [1]: http://i.stack.imgur.com/MoPh0.png
  [2]: http://i.stack.imgur.com/3IVm3.png

Android Push Notifications: Icon not displaying in notification, white square shown instead

There are a **lot of system images** piling up on my disk in the android sdk folder. i hardly use the emulator. May be once in 6 months. Most of my development is directly on device. What i wanted to check was, **will removing the system images (at least for the old APIS i.e. &lt; 22) impact the development?**

**Also, the google apis folder seen below. Should i keep it for all versions or just the one in the latest suffice?**

![enter image description here][1]

Screenshot above is from WinDirStat tool. - 
https://windirstat.net

  [1]: http://i.stack.imgur.com/VyQK6.png

Android SDK folder taking a lot of disk space. Do we need to keep all of the System Images?

In my `Android Studio` project there are two `build configuration` with some `buildConfigField`:

        buildTypes {
        def SERVER_URL = &quot;SERVER_URL&quot;
        def APP_VERSION = &quot;APP_VERSION&quot;

        debug {
            buildConfigField &quot;String&quot;, SERVER_URL, &quot;http://dev.myserver.com&quot;
            buildConfigField &quot;String&quot;, APP_VERSION, &quot;0.0.1&quot;
        }

        release {
            buildConfigField &quot;String&quot;, SERVER_URL, &quot;https://myserver.com&quot;
            buildConfigField &quot;String&quot;, APP_VERSION, &quot;0.0.1&quot;

            minifyEnabled false
            proguardFiles getDefaultProguardFile(&#39;proguard-android.txt&#39;), &#39;proguard-rules.pro&#39;
        }
    }

I am getting and error as follows:

    /path/to/generated/BuildConfig.java
        Error:(14, 47) error: &#39;;&#39; expected
        Error:(15, 47) error: &#39;;&#39; expected

the generated `BuildConfig.java` is as follows:

    public final class BuildConfig {
        public static final boolean DEBUG = Boolean.parseBoolean(&quot;true&quot;);
        public static final String APPLICATION_ID = &quot;com.mycuteoffice.mcoapp&quot;;
        public static final String BUILD_TYPE = &quot;debug&quot;;
        public static final String FLAVOR = &quot;&quot;;
        public static final int VERSION_CODE = 1;
        public static final String VERSION_NAME = &quot;1.0&quot;;
        // Fields from build type: debug
        public static final String APP_VERSION = 0.0.1;
        public static final String SERVER_URL = http://dev.mycuteoffice.com;
    }

I think the `APP_VERSION` and `SERVER_URL` are not getting generated properly as being String type they do not have quotes. 

I am not sure why it is being generated in such a way. Please let me know how can I resolve this issues.  

How to generate buildConfigField with String type

How should I select a tab in TabLayout programmatically? 

     TabLayout tabLayout = (TabLayout) findViewById(R.id.tabs);
     tabLayout.setupWithViewPager(viewPager);

TabLayout tab selection

Background
--
According to the &quot;Resource Shrinking&quot; webpage of Andriod documentations ([here][1]), you can minimize the app&#39;s size via the build.gradle file, by using these lines:

    android {
        ...
    
        buildTypes {
            release {
                minifyEnabled true
                shrinkResources true
                proguardFiles getDefaultProguardFile(&#39;proguard-android.txt&#39;), &#39;proguard-rules.pro&#39;
            }
        }
    }

And, they say that when using it, it will also tell you how much is saved in the process:

&gt; When you enable shrinkResources, building your app should display
&gt; output like the following during the build:
&gt;
&gt; ...
&gt; Removed unused resources: Binary resource data reduced from 2570KB to
&gt; 1711KB: Removed 33%

The questions
--
I can&#39;t find out the answers to those questions:

1. When using Android-Studio itself to create the signed app, where can I find the information of how much was saved and which files were removed/modified?
2. What exactly does &quot;shrinkResources&quot; do that &quot;minifyEnabled&quot; don&#39;t? And why do &quot;shrinkResources&quot; depend on &quot;minifyEnabled&quot; ? 
3. Do any of those options affect the size and/or quality of image files?
4. Isn&#39;t Proguard responsible of shrinking source code? I ask this because it says &quot;you have to enable minifyEnabled in order to turn on code shrinking,&quot;


  [1]: http://tools.android.com/tech-docs/new-build-system/resource-shrinking

&quot;minifyEnabled&quot; vs &quot;shrinkResources&quot; - what&#39;s the difference? and how to get the saved space?

I have updated my Android Studio to version **1.3.0** before 3 days.

Before that I can use NDK and now I am getting error like ,

&gt;Error:(50, 0) Error: NDK integration is deprecated in the current plugin.  Consider trying the new experimental plugin.  For details, see http://tools.android.com/tech-docs/new-build-system/gradle-experimental.  Set &quot;android.useDeprecatedNdk=true&quot; in gradle.properties to continue using the current NDK integration.

I can not find file gradle.property at project level.

How can I solve this error?

After updating Android Studio to version 1.3.0 I am getting &quot;NDK integration is deprecated in the current plugin&quot; Error

How do I extract code from aar file.[Accidentally my main project is on another system can&#39;t access only have aar file on my mail]

I need to extract the JNI code from aar file. I tried to change the extension to .jar but its extract .class only, Do anybody know how to extract that aar thing.

Extract code from .aar file Android

I want to compile an open source android project (Netguard) using gradel (`gradlew clean build`) But I encountered this Error:

    A problem occurred configuring project &#39;:app&#39;.
    &gt; Exception thrown while executing model rule: NdkComponentModelPlugin.Rules#cre
    ateToolchains
       &gt; No toolchains found in the NDK toolchains folder for ABI with prefix: llvm
I serached but didn&#39;t find enything helping. Here is the main `build.gradle`:


    buildscript {
        repositories {
            jcenter()
        }
        dependencies {
    		classpath &#39;com.android.tools.build:gradle-experimental:0.6.0-alpha1&#39;
        }
    }
    allprojects {
        repositories {
            jcenter()
        }
    }
    task clean(type: Delete) {
        delete rootProject.buildDir
    }

And here is the `build.gradle` of the `app` project:

    apply plugin: &#39;com.android.model.application&#39;
    
    model {
        android {
            compileSdkVersion = 23
            buildToolsVersion = &quot;23.0.2&quot;
    
            defaultConfig.with {
                applicationId = &quot;eu.faircode.netguard&quot;
                minSdkVersion.apiLevel = 21
                targetSdkVersion.apiLevel = 23
                versionCode = 2016011801
                versionName = &quot;0.76&quot;
                archivesBaseName = &quot;NetGuard-v$versionName-$versionCode&quot;
            }
        }
        android.ndk {
            moduleName = &quot;netguard&quot;
            toolchain = &quot;clang&quot;
            ldLibs.add(&quot;log&quot;)
        }
        android.sources {
            main {
                jni {
                    source {
                        srcDir &quot;src/main/jni/netguard&quot;
                    }
                    exportedHeaders {
                    }
                }
            }
        }
        android.buildTypes {
            release {
                minifyEnabled = true
                proguardFiles.add(file(&#39;proguard-rules.pro&#39;))
                ndk.with {
                    debuggable = true
                }
            }
        }
        android.buildTypes {
            debug {
                ndk.with {
                    debuggable = true
                }
            }
        }
        android.productFlavors {
            create(&quot;all&quot;) {
            }
        }
    }
    
    dependencies {
        

    compile fileTree(dir: &#39;libs&#39;, include: [&#39;*.jar&#39;])
        compile &#39;com.android.support:appcompat-v7:23.1.+&#39;
        compile &#39;com.android.support:recyclerview-v7:23.1.+&#39;
        compile &#39;com.squareup.picasso:picasso:2.5.+&#39;
    }



And I&#39;m using `gradle-2.9-all` and `android-ndk-r10e`. I don&#39;t know if I should mention anything else, so comment if you need any information.

Error: No toolchains found in the NDK toolchains folder for ABI with prefix: llvm

I have an issue with third party libraries that are imported to my project.

I read quite a lot of articles about that but do not get any information how properly handle it.

I put my classes .so to the folder.

[![enter image description here][1]][1]

Problem is that the i try to run the app i receive 

    [INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113]


  [1]: http://i.stack.imgur.com/Bsfyx.png

[INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113]

So I know this has been questioned quite a lot. To be exact for example in these questions:  

1. https://stackoverflow.com/questions/31111377/run-nodejs-server-in-android  
2. https://stackoverflow.com/questions/11392590/how-to-run-my-node-js-project-on-android?lq=1  
and   
3. https://stackoverflow.com/questions/29145308/nodejs-on-ios-android?rq=1

Every option presented has a problem though:

 - I want to run it on my normal device so I would like to avoid installing another OS on my Device
 
 - Work on JXCore was stopped last month and (maybe as a result) I couldn&#39;t get it to compile (see https://stackoverflow.com/questions/36506305/cant-install-jxcore-cordova)
 - The Android Port of NodeJs [Anode](https://github.com/paddybyers/anode) has not been worked on since 2014 and wasn&#39;t really maintained back then anyways
 - The second answer in the second thread I linked to mentioned there is an official node distribution for Android now but apart from a link to the [Browse-Website of the latest dist](https://nodejs.org/dist/latest/) I couldn&#39;t find any info on how to actually use it
 - I also saw [this](http://www.goland.org/nodejsonandroid/) but it seems like the device has to be connected to a PC (or similar) to run the adb shell commands while I would like to make it as a separate App

With the time that past since these questions have been posted and as the &quot;best option&quot; JXCore seem to be now unusable:  
Is there a way to run a node.js application (a server in my case) on an Android device?

if you&#39;re wondering why I&#39;d want this: I made a WebApp with a Node.Js server and I now want a version you can launch locally from your phone without requiring an Internet connection. This means the server needs to run on an Android phone.


Running Node.Js on Android

What is the actual difference between `CMake` and `NDK` build in android studio project. I already went through google documentation but the concept is not clear yet. As per google documentation:

 **The Android Native Development Kit (NDK):** a toolset that allows you
  to use C and C++ code with Android, and provides platform libraries
  that allow you to manage native activities and access the physical device
  components, such as sensors and touch input.

 **CMake:** an external build tool that works alongside Gradle to build
  your native library. You do not need this component if you only plan
  to use ndk-build.

Can anyone has a better explanation with an example when we need to use what?

Content Type	Original Author	Original Content on Stackoverflow
Question	Philipp E.	View Question on Stackoverflow
Solution 1 - Android	ph0b	View Answer on Stackoverflow
Solution 2 - Android	Arun Kumar	View Answer on Stackoverflow

How to use 32-bit native libraries on 64-bit Android device

Android Problem Overview

Android Solutions

Solution 1 - Android

Solution 2 - Android

Gradle: Override transitive dependency by version classifier

PHAsset to UIImage

Attributions