I have an app that mutes the phone by using AudioManager and setting ringer mode to silent with this code:

    AudioManager audioManager = 
        (AudioManager) context.getSystemService(Context.AUDIO_SERVICE);
    try {
    	audioManager.setRingerMode(AudioManager.RINGER_MODE_SILENT)
    } catch (Exception e) {
     	e.printStackTrace();
    }

This works with Android 6, but now with Android 7, I get the following error:

    System.err: java.lang.SecurityException: Not allowed to change Do Not Disturb state
    System.err: at android.os.Parcel.readException(Parcel.java:1683)
    System.err: at android.os.Parcel.readException(Parcel.java:1636)
    System.err: at android.media.IAudioService$Stub$Proxy.setRingerModeExternal(IAudioService.java:962)
    System.err: at android.media.AudioManager.setRingerMode(AudioManager.java:1022)
    System.err: at controllers.SearchResultController.mutePhone(SearchResultController.java:185)

Are there any new permissions I need to ask for to make this work?

I looked through the Android permissions list, but couldn&#39;t find any that seemed relevant.

In Android 7 (API level 24) my app is not allowed to mute phone (set ringer mode to silent)

The app is crashing when I&#39;m trying to open a file. It works below Android Nougat, but on Android Nougat it crashes. It only crashes when I try to open a file from the SD card, not from the system partition. Some permission problem?

Sample code:

    File file = new File(&quot;/storage/emulated/0/test.txt&quot;);
    Intent intent = new Intent(Intent.ACTION_VIEW);
    intent.setDataAndType(Uri.fromFile(file), &quot;text/*&quot;);
    intent.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
    startActivity(intent); // Crashes on this line

Log: 

&gt; android.os.FileUriExposedException:
&gt; file:///storage/emulated/0/test.txt exposed beyond app through
&gt; Intent.getData()

**Edit:**

When targeting Android Nougat, `file://` URIs are not allowed anymore. We should use `content://` URIs instead. However, my app needs to open files in root directories. Any ideas?

android.os.FileUriExposedException: file:///storage/emulated/0/test.txt exposed beyond app through Intent.getData()

My `XML` layout is not rendering with this error message. I am already using Java 8.

[![enter image description here][1]][1]


Also using latest build tools in Gradle.

    android {
        compileSdkVersion &#39;android-N&#39;
        buildToolsVersion 24.0.0 rc1
        ...
    }

XML Error - 

[![enter image description here][2]][2]


  [1]: http://i.stack.imgur.com/qNGLL.png
  [2]: http://i.stack.imgur.com/bj7SN.png

Android N requires the IDE to be running with Java 1.8 or later?

Android 7 introduced some changes to the way certificates are handled (http://android-developers.blogspot.com/2016/07/changes-to-trusted-certificate.html) and somehow I cannot make my Charles proxy work any more.

My network_security_config.xml:

    &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?&gt;
    &lt;network-security-config&gt;
        &lt;base-config&gt;
            &lt;trust-anchors&gt;
                &lt;certificates src=&quot;system&quot; /&gt;
            &lt;/trust-anchors&gt;
        &lt;/base-config&gt;
        &lt;debug-overrides&gt;
            &lt;trust-anchors&gt;
                &lt;certificates src=&quot;user&quot; /&gt;
            &lt;/trust-anchors&gt;
        &lt;/debug-overrides&gt;
    &lt;/network-security-config&gt;

I&#39;m running in debug mode. But no matter what, I get `javax.net.ssl.SSLHandshakeException: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found.`.

Needless to say, I did install a `pfx` certificate from `Settings -&gt; Security -&gt; Install from storage`. The certificate shows in `User Credentials` but not in `Trusted credentials -&gt; User`. On my lollipop device, the certificates are listed there. 

I&#39;m using okhttp3 as HTTP library.


Any idea what I am doing wrong ?


How to get charles proxy work with Android 7 nougat?

I&#39;m seeing this native crash with the following stack trace.

This happens in Android 7.0 &amp; 7.1 only. Nothing new has been added to the app, which has been in production for a few years, but with more devices being updated to Nougat this crash happens frequently now and is becoming a nuisance. 

Any advice would be appreciated.

    native: pc 000000000007a6c4  /system/lib64/libc.so (tgkill+8)
      native: pc 0000000000077920  /system/lib64/libc.so (pthread_kill+64)
      native: pc 000000000002538c  /system/lib64/libc.so (raise+24)
      native: pc 000000000001d24c  /system/lib64/libc.so (abort+52)
      native: pc 000000000001225c  /system/lib64/libcutils.so (__android_log_assert+224)
      native: pc 00000000000610e0  /system/lib64/libhwui.so
      native: pc 000000000003908c  /system/lib64/libhwui.so
      native: pc 000000000003609c  /system/lib64/libhwui.so
      native: pc 000000000003b4fc  /system/lib64/libhwui.so
      native: pc 000000000003c520  /system/lib64/libhwui.so
      native: pc 000000000003e694  /system/lib64/libhwui.so (_ZN7android10uirenderer12renderthread12RenderThread10threadLoopEv+152)
      native: pc 00000000000127f0  /system/lib64/libutils.so (_ZN7android6Thread11_threadLoopEPv+336)
      native: pc 00000000000a50b0  /system/lib64/libandroid_runtime.so (_ZN7android14AndroidRuntime15javaThreadShellEPv+116)
      native: pc 00000000000770f4  /system/lib64/libc.so (_ZL15__pthread_startPv+204)
      native: pc 000000000001e7d0  /system/lib64/libc.so (__start_thread+16)

Here&#39;s a list of devices that are affected: 
[![enter image description here][1]][1]


  [1]: https://i.stack.imgur.com/vLqjH.png



**UPDATE 7/18:**

Still unable to get to the root of this, so I decided to purchase a device which had most occurrences and was reasonably priced, which turned out to be Samsung Galaxy J3 2017 version with Android 7.0. Unfortunately I am still unable to reproduce the crash.

I&#39;ve also made some memory usage improvements to the app in production, but the crash is still happening.

From all the comments and my own research it seems to be related to dynamically linked NDKs, but I&#39;m not using any and its hard to find out if any of the dependencies do.

I would like to share my dependencies, it would be great if other folks facing the same issue could call out if they are using one of the same dependencies - perhaps we can spot the culprit this way.

    // App Compat
        compile &#39;com.android.support:support-v4:23.0.1&#39;
        compile &#39;com.android.support:appcompat-v7:23.0.1&#39;
        compile &#39;com.android.support:cardview-v7:23.0.1&#39;
        compile &#39;com.android.support:recyclerview-v7:23.0.1&#39;
    
        // Play Services
        compile &#39;com.google.android.gms:play-services-location:8.3.0&#39;
        compile &#39;com.google.android.gms:play-services-maps:8.3.0&#39;
        compile &#39;com.google.android.gms:play-services-analytics:8.3.0&#39;
        compile &#39;com.google.android.gms:play-services-appindexing:8.3.0&#39;
        compile &#39;com.google.android.gms:play-services-ads:8.3.0&#39;
    
        // Misc Libraries
        compile &#39;fr.avianey.com.viewpagerindicator:library:2.4.1@aar&#39;
        compile files(&#39;app/libs/htmlcleaner-2.7.jar&#39;)
        compile files(&#39;app/libs/protobuf-java-2.6.0.jar&#39;)
        compile files(&#39;app/libs/nineoldandroids-2.4.0.jar&#39;)
    
        // Fabric
        compile(&#39;com.twitter.sdk.android:twitter:1.13.0@aar&#39;) { transitive = true; }
        compile(&#39;com.crashlytics.sdk.android:crashlytics:2.5.5@aar&#39;) { transitive = true; }

For folks facing the same crash, please respond in comments if you are using any of these dependencies / versions. Maybe we can single out the problem dependency. 

Android 7 Native Crash: libc.so tgkill

I have a published app that is crashing at startup on Android N when the newly introduced `Display size` OS setting is set to too large a value.

When I look in logcat, I see the following message:

    java.lang.RuntimeException: Canvas: trying to draw too large(106,975,232 bytes) bitmap.

I&#39;ve traced the issue to an ImageView in my first Activity that shows a nice big background image. The image in question is 2048x1066 and is in my generic `drawables` directory, so no matter the density, this image will be used.

Everything works okay when the `Display size` setting is `Small`. But when I go up to `Default`, it stops working. If I then swap the image out with a smaller one, it works at `Default`, but if I go up to `Large`, it stops working again.

My guess is that adjusting `Display size` up causes your device to behave like a physically smaller device with a higher pixel density. But I don&#39;t understand what I&#39;m supposed to do here. If I put in progressively smaller images for progressively higher resolutions, it won&#39;t look good on actually large displays. Or am I not understanding something?

Any pointers would be greatly appreciated.

&quot;Canvas: trying to draw too large bitmap&quot; when Android N Display Size set larger than Small

I have an android.app.RemoteServiceException (RSE) but without any message.
I get the following crash report on Google Play Console. When I get a RSE due to a bad Notification or Broadcast I get the related message but in this case it is a black crash.

```none
android.app.RemoteServiceException: 
  at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1813)
  at android.os.Handler.dispatchMessage (Handler.java:102)
  at android.os.Looper.loop (Looper.java:154)
  at android.app.ActivityThread.main (ActivityThread.java:6781)
  at java.lang.reflect.Method.invoke (Method.java)
  at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:1520)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1410)
```

I started getting these crashes primarily on Android 7 and Samsung devices (in large).

[![Android versions and devices][1]][1]

We are following standard guidelines for Notifications and Broadcasts.
 

    targetSdkVersion 25
    compileSdkVersion 26

I have gone through many StackOverflow questions related to RemoteServiceException but not been able to find RCA hence posting the new question.   
Listed below are the questions I have checked and not been able to find a resolution for RSE:

 - https://stackoverflow.com/questions/25317659/how-to-fix-android-app-remoteserviceexception-bad-notification-posted-from-pac
 - https://stackoverflow.com/questions/10607097/how-to-add-vertical-line-to-remoteview-for-custom-android-notifications
 - https://stackoverflow.com/questions/24968556/how-to-fix-this-bug-android-app-remoteserviceexception-bad-notification-post
 - https://stackoverflow.com/questions/48124458/fcm-how-to-fix-android-app-remoteserviceexception-bad-notification-posted-fro
 - https://stackoverflow.com/questions/40175713/android-getting-cant-deliver-broadcast-error-on-dynamically-registered-broa
 - https://stackoverflow.com/questions/46971153/fatal-exception-android-app-remoteserviceexception-cant-deliver-broadcast-at


  [1]: https://i.stack.imgur.com/Zjzva.png

How to fix: android.app.RemoteServiceException without any message (not related to Bad Notification or Broadcast)

My app has an auto-update feature that download an APK and when the download is finished that a Intent.VIEW_ACTION to open the app and let the user install the downloaded apk

         

    Uri uri = Uri.parse(&quot;file://&quot; + destination);
    Intent install = new Intent(Intent.ACTION_VIEW);
    install.setFlags(Intent.FLAG_ACTIVITY_CLEAR_TOP);
    install.setDataAndType(uri,
        manager.getMimeTypeForDownloadedFile(downloadId));
    activity.startActivity(install);

This works great for all the device &lt; 24

Now with Android 24 apparently we are not allowed any more to start intents with file:/// and after some googling it was advised to use A File Provider

new code:
   

 

    Intent install = new Intent(Intent.ACTION_VIEW);
    install.setFlags(Intent.FLAG_ACTIVITY_CLEAR_TOP);
    install.setFlags(Intent.FLAG_GRANT_READ_URI_PERMISSION);
    Uri apkUri = FileProvider.getUriForFile(AutoUpdate.this,
        BuildConfig.APPLICATION_ID + &quot;.provider&quot;, file);
    install.setDataAndType(apkUri,
        manager.getMimeTypeForDownloadedFile(downloadId));
    activity.startActivity(install);

Now activity.startActivity(install); throws an error

&gt; No Activity found to handle Intent { act=android.intent.action.VIEW
&gt; dat=content://com.xxxx.xx.provider/MyFolder/Download/MyApkFile.apk
&gt; typ=application/vnd.android.package-archive flg=0x4000000 }

Is there any way I can open the APK viewer in Android 7 (24) ?




Android install apk with Intent.VIEW_ACTION not working with File provider

I updated Nexus 5X to Android N, and now when I install the app (debug or release) on it I am getting TransactionTooLargeException on every screen transition that has Bundle in extras. The app is working on all other devices. The old app that is on PlayStore and has mostly same code is working on Nexus 5X.
Is anyone having the same issue?

    java.lang.RuntimeException: android.os.TransactionTooLargeException: data parcel size 592196 bytes
       at android.app.ActivityThread$StopInfo.run(ActivityThread.java:3752)
       at android.os.Handler.handleCallback(Handler.java:751)
       at android.os.Handler.dispatchMessage(Handler.java:95)
       at android.os.Looper.loop(Looper.java:154)
       at android.app.ActivityThread.main(ActivityThread.java:6077)
       at java.lang.reflect.Method.invoke(Native Method)
       at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:865)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:755)
    Caused by: android.os.TransactionTooLargeException: data parcel size 592196 bytes
       at android.os.BinderProxy.transactNative(Native Method)
       at android.os.BinderProxy.transact(Binder.java:615)
       at android.app.ActivityManagerProxy.activityStopped(ActivityManagerNative.java:3606)
       at android.app.ActivityThread$StopInfo.run(ActivityThread.java:3744)
       at android.os.Handler.handleCallback(Handler.java:751)&#160;
       at android.os.Handler.dispatchMessage(Handler.java:95)&#160;
       at android.os.Looper.loop(Looper.java:154)&#160;
       at android.app.ActivityThread.main(ActivityThread.java:6077)&#160;
       at java.lang.reflect.Method.invoke(Native Method)&#160;
       at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:865)&#160;
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:755)&#160;

android.os.TransactionTooLargeException on Nougat

I have a multilingual app with primary language English and secondary language Arabic.

As described in the [documentation](https://developer.android.com/about/versions/android-4.2.html#RTL),

 - I have added `android:supportsRtl=&quot;true&quot;` in the manifest.
 - I have changed all xml properties with `left` and `right` attributes to `start` and `end` respectively.
 - I have added Arabic language strings in `strings-ar` (and similarly for other resources).

The above setup works properly. After changing the `Locale` to `ar-AE`, Arabic text &amp; resources are correctly displayed in my Activities.

&gt; However, every time I navigate to an `Activity` with a `WebView`
&gt; and/or a `WebViewClient`, the locale, text and layout direction
&gt; abruptly revert to the device default.

**Further hints:**

 - This is occurring ***only*** on a Nexus 6P with **Android 7.0**. Everything works properly on Android 6.0.1 and below.
 - The abrupt shift in locale happens ***only*** when I navigate to an `Activity` that has a `WebView` and/or a `WebViewClient` (and I have several). It does not occur on any of the other Activities.

Android 7.0 has multi-locale support, allowing the user to set more than one default locale. So if I set the primary locale to `Locale.UK`:

[![enter image description here][1]][1]

&gt; Then on navigating to the `WebView`, the locale changes from `ar-AE`
&gt; to `en-GB`.

**Android 7.0 API changes:**

As indicated in the [list of API changes](https://developer.android.com/sdk/api_diff/24/changes.html), new methods pertaining to locale have been added to the following classes in API 24:

[**`Locale`:**]()

 - [`Locale.getDefault(...)`](https://developer.android.com/reference/java/util/Locale.html#getDefault%28java.util.Locale.Category%29)
 - [`Locale.setDefault(...)`](https://developer.android.com/reference/java/util/Locale.html#setDefault%28java.util.Locale.Category,%20java.util.Locale%29)

[**`Configuration`:**]()

 - [`getLocales()`](https://developer.android.com/reference/android/content/res/Configuration.html#getLocales%28%29)
 - [`setLocales(...)`](https://developer.android.com/reference/android/content/res/Configuration.html#setLocales%28android.os.LocaleList%29)

&gt; However, I am building my app with API 23, and am not using any of
&gt; these new methods.

**Furthermore ...**

 - The problem occurs on the Nexus 6P emulator as well.

 - To get the default locale, I am using [`Locale.getDefault()`](https://developer.android.com/reference/java/util/Locale.html#getDefault%28%29).

 - To set the default locale, I am using the following code:

        public static void setLocale(Locale locale){
            Locale.setDefault(locale);
            Configuration config = new Configuration();
            config.setLocale(locale);
            Context context = MyApplication.getInstance();
            context.getResources().updateConfiguration(config,
                    context.getResources().getDisplayMetrics());
        }


Has anyone encountered this problem before? What is the reason for it, and how do I resolve this?

**References:**

**1.** [**Native RTL support in Android 4.2**](http://android-developers.blogspot.in/2013/03/native-rtl-support-in-android-42.html).

**2.** [**Multilingual Support - Language and Locale**](https://developer.android.com/guide/topics/resources/multilingual-support.html).

**3.** [**Be wary of the default locale**](https://developer.android.com/reference/java/util/Locale.html).

  [1]: https://i.stack.imgur.com/gPxVk.png

Android - WebView language changes abruptly on Android 7.0 and above

There is a crash in my app on devices running version `7.0`, `7.1.1` and `8.0.0` with the following stacktrace:

    Fatal Exception: java.lang.RuntimeException: Unable to resume activity {xxx/xxx.views.activities.HomeActivity}: java.lang.IllegalArgumentException
       at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3788)
       at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3828)
       at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2991)
       at android.app.ActivityThread.-wrap14(ActivityThread.java)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1635)
       at android.os.Handler.dispatchMessage(Handler.java:102)
       at android.os.Looper.loop(Looper.java:154)
       at android.app.ActivityThread.main(ActivityThread.java:6692)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1468)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1358)
    Caused by java.lang.IllegalArgumentException
       at android.os.Parcel.readException(Parcel.java:1697)
       at android.os.Parcel.readException(Parcel.java:1646)
       at android.app.ActivityManagerProxy.isTopOfTask(ActivityManagerNative.java:6600)
       at android.app.Activity.isTopOfTask(Activity.java:6142)
       at android.app.Activity.onResume(Activity.java:1331)
       at android.support.v4.app.FragmentActivity.onResume(FragmentActivity.java:485)
       at xxx.views.activities.BaseActivity.onResume(BaseActivity.java:50)
       at xxx.views.activities.HomeActivity.onResume(HomeActivity.java:364)
       at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1277)
       at android.app.Activity.performResume(Activity.java:7058)
       at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3765)
       at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3828)
       at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2991)
       at android.app.ActivityThread.-wrap14(ActivityThread.java)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1635)
       at android.os.Handler.dispatchMessage(Handler.java:102)
       at android.os.Looper.loop(Looper.java:154)
       at android.app.ActivityThread.main(ActivityThread.java:6692)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1468)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1358)

My code on the reported lines is simply:

    // HomeActivity class
    @Override
    public void onResume() {
        mPresenter.onResume();
        super.onResume();

        renderView();
    }

    // BaseActivity class
    @Override
    protected void onResume() {
        super.onResume();
        // some other code
    }


I did some digging about this and found this similar [question][1].

Since the `IllegalArgumentException` thrown contains no detail message, I am going to try putting in extra logs as suggested [here][2]. 

Meanwhile please appreciate any help!


  [1]: https://stackoverflow.com/questions/42758643/java-lang-runtimeexception-unable-to-resume-activity-with-java-lang-illegalargu
  [2]: https://stackoverflow.com/a/47765497/3579786

Unable to resume activity with java.lang.IllegalArgumentException on Android api &gt;=24

I&#39;m trying to figure out how the expand/collapse animation of the toolbar is done. If you have a look at the Telegram app settings, you will see that there is a listview and the toolbar. When you scroll down, the toolbar collapse, and when you scroll up it expands. There is also the animation of the profile pic and the FAB. Does anyone have any clue on that? Do you think they built all the animations on top of it? Maybe I&#39;m missing something from the new APIs or the support library.

I noticed the same behaviour on the Google calendar app, when you open the Spinner (I don&#39;t think it&#39;s a spinner, but it looks like): The toolbar expands and when you scroll up, it collapse. 

Just to clearify: I don&#39;t need the QuickReturn method. I know that probably Telegram app is using something similar. The exact method that I need is the Google Calendar app effect. I&#39;ve tried with 

    android:animateLayoutChanges=&quot;true&quot;

and the expand method works pretty well. But obviously, If I scroll up the ListView, the toolbar doesn&#39;t collapse.

I&#39;ve also thought about adding a `GestureListener` but I want to know if there are any APIs or simpler methods of achieving this. 

If there are none, I think I will go with the `GestureListener`. Hopefully to have a smooth effect of the Animation. 

Thanks!

Expand/Collapse Lollipop toolbar animation (Telegram app)

I am using `Html.fromHtml` to view html in a `TextView`.

    Spanned result = Html.fromHtml(mNews.getTitle());
    ...
    ...
    mNewsTitle.setText(result);


But `Html.fromHtml` is now deprecated in Android N+

What/How do I find the new way of doing this?

Html.fromHtml deprecated in Android N

I&#39;m working on an app for which the (power)users have to set up their own server (i.e. nginx) to run the backend application. The corresponding domain needs to be configured in the app so it can connect. I&#39;ve been testing primarily on my own phone (sony z3c) and started developing for 5.1. Later I received an update for 6.0 but still maintained a working 5.1 inside the emulator. Not too long ago, I started to work on an AVD with an image for 7.0 and to my suprise it won&#39;t connect to my server, telling me the ssl handshake failed. My nginx configuration is pretty strict, but it works for both 5.1 and 6.0, so .... ?!

Here is what I know:

- I use v24 for support libs, i.e. my compileSdkVersion is 24.
- I use Volley [v1.0.0](https://bintray.com/android/android-utils/com.android.volley.volley).
- I&#39;ve tried the [TLSSocketFactory](https://stackoverflow.com/a/33874126), but it doesn&#39;t change anything. This seems to be used most of the times to prevent SSL3 use for older SDK versions anyway.
- I&#39;ve tried increasing the [timeout](https://stackoverflow.com/questions/32184787/com-android-volley-noconnectionerror-javax-net-ssl-sslhandshakeexception-javax), but it doesn&#39;t change anything.
- I&#39;ve tried using HttpURLConnection directly, but it doesn&#39;t change anything apart from the stack trace (it&#39;s without the volley references, but identical otherwise).

Without the TLSSocketFactory the request are made through a bare request queue, instantiated with ```Volley.newRequestQueue(context)```.

This is what I see in android studio:

    W/System.err: com.android.volley.NoConnectionError: javax.net.ssl.SSLHandshakeException: Connection closed by peer
    W/System.err:     at com.android.volley.toolbox.BasicNetwork.performRequest(BasicNetwork.java:151)
    W/System.err:     at com.android.volley.NetworkDispatcher.run(NetworkDispatcher.java:112)
    W/System.err: Caused by: javax.net.ssl.SSLHandshakeException: Connection closed by peer
    W/System.err:     at com.android.org.conscrypt.NativeCrypto.SSL_do_handshake(Native Method)
    W/System.err:     at com.android.org.conscrypt.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:357)
    W/System.err:     at com.android.okhttp.Connection.connectTls(Connection.java:235)
    W/System.err:     at com.android.okhttp.Connection.connectSocket(Connection.java:199)
    W/System.err:     at com.android.okhttp.Connection.connect(Connection.java:172)
    W/System.err:     at com.android.okhttp.Connection.connectAndSetOwner(Connection.java:367)
    W/System.err:     at com.android.okhttp.OkHttpClient$1.connectAndSetOwner(OkHttpClient.java:130)
    W/System.err:     at com.android.okhttp.internal.http.HttpEngine.connect(HttpEngine.java:329)
    W/System.err:     at com.android.okhttp.internal.http.HttpEngine.sendRequest(HttpEngine.java:246)
    W/System.err:     at com.android.okhttp.internal.huc.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:457)
    W/System.err:     at com.android.okhttp.internal.huc.HttpURLConnectionImpl.connect(HttpURLConnectionImpl.java:126)
    W/System.err:     at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getOutputStream(HttpURLConnectionImpl.java:257)
    W/System.err:     at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.getOutputStream(DelegatingHttpsURLConnection.java:218)
    W/System.err:     at com.android.okhttp.internal.huc.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java)
    W/System.err:     at com.android.volley.toolbox.HurlStack.addBodyIfExists(HurlStack.java:264)
    W/System.err:     at com.android.volley.toolbox.HurlStack.setConnectionParametersForRequest(HurlStack.java:234)
    W/System.err:     at com.android.volley.toolbox.HurlStack.performRequest(HurlStack.java:107)
    W/System.err:     at com.android.volley.toolbox.BasicNetwork.performRequest(BasicNetwork.java:96)
    W/System.err:   ... 1 more
    W/System.err:   Suppressed: javax.net.ssl.SSLHandshakeException: Handshake failed
    W/System.err:     at com.android.org.conscrypt.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:429)
    W/System.err:       ... 17 more
    W/System.err:   Caused by: javax.net.ssl.SSLProtocolException: SSL handshake terminated: ssl=0x7ffef3748040: Failure in SSL library, usually a protocol error
    W/System.err: error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE (external/boringssl/src/ssl/s3_pkt.c:610 0x7ffeda1d2240:0x00000001)
    W/System.err: error:1000009a:SSL routines:OPENSSL_internal:HANDSHAKE_FAILURE_ON_CLIENT_HELLO (external/boringssl/src/ssl/s3_clnt.c:764 0x7ffee9d2b70a:0x00000000)
    W/System.err:     at com.android.org.conscrypt.NativeCrypto.SSL_do_handshake(Native Method)
    W/System.err:     at com.android.org.conscrypt.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:357)
    W/System.err:       ... 17 more

Since it says ```SSLV3_ALERT_HANDSHAKE_FAILURE``` I can only assume it for some reason tries to connect using SSLv3 and fails, but this doesn&#39;t make any sense to me whatsoever. It might be a cipher-issue, but how can I tell what it is trying to use ? I would rather not enable a ciphers on the server, make a connection attempt and repeat.

My nginx site uses a let&#39;s encrypt certificate and has the following configuration:

    ssl_stapling on;
    ssl_stapling_verify on;
    ssl_trusted_certificate /etc/ssl/certs/lets-encrypt-x1-cross-signed.pem;
    ssl_ciphers ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:!aNULL;
    ssl_dhparam /etc/ssl/certs/dhparam.pem;
    ssl_ecdh_curve secp384r1;
    ssl_prefer_server_ciphers on;
    ssl_protocols TLSv1.2;

To test these ciphers I&#39;ve a [script](https://superuser.com/a/224263) and it confirms these ciphers (run on a wheezy vps outside the server&#39;s network):

&lt;pre&gt;
Testing ECDHE-RSA-AES256-GCM-SHA384...YES
Testing ECDHE-ECDSA-AES256-GCM-SHA384...NO (sslv3 alert handshake failure)
Testing ECDHE-RSA-AES256-SHA384...NO (sslv3 alert handshake failure)
Testing ECDHE-ECDSA-AES256-SHA384...NO (sslv3 alert handshake failure)
Testing ECDHE-RSA-AES256-SHA...NO (sslv3 alert handshake failure)
Testing ECDHE-ECDSA-AES256-SHA...NO (sslv3 alert handshake failure)
Testing SRP-DSS-AES-256-CBC-SHA...NO (sslv3 alert handshake failure)
Testing SRP-RSA-AES-256-CBC-SHA...NO (sslv3 alert handshake failure)
Testing DHE-DSS-AES256-GCM-SHA384...NO (sslv3 alert handshake failure)
Testing DHE-RSA-AES256-GCM-SHA384...NO (sslv3 alert handshake failure)
Testing DHE-RSA-AES256-SHA256...NO (sslv3 alert handshake failure)
Testing DHE-DSS-AES256-SHA256...NO (sslv3 alert handshake failure)
Testing DHE-RSA-AES256-SHA...NO (sslv3 alert handshake failure)
Testing DHE-DSS-AES256-SHA...NO (sslv3 alert handshake failure)
Testing DHE-RSA-CAMELLIA256-SHA...NO (sslv3 alert handshake failure)
Testing DHE-DSS-CAMELLIA256-SHA...NO (sslv3 alert handshake failure)
Testing AECDH-AES256-SHA...NO (sslv3 alert handshake failure)
Testing SRP-AES-256-CBC-SHA...NO (sslv3 alert handshake failure)
Testing ADH-AES256-GCM-SHA384...NO (sslv3 alert handshake failure)
Testing ADH-AES256-SHA256...NO (sslv3 alert handshake failure)
Testing ADH-AES256-SHA...NO (sslv3 alert handshake failure)
Testing ADH-CAMELLIA256-SHA...NO (sslv3 alert handshake failure)
Testing ECDH-RSA-AES256-GCM-SHA384...NO (sslv3 alert handshake failure)
Testing ECDH-ECDSA-AES256-GCM-SHA384...NO (sslv3 alert handshake failure)
Testing ECDH-RSA-AES256-SHA384...NO (sslv3 alert handshake failure)
Testing ECDH-ECDSA-AES256-SHA384...NO (sslv3 alert handshake failure)
Testing ECDH-RSA-AES256-SHA...NO (sslv3 alert handshake failure)
Testing ECDH-ECDSA-AES256-SHA...NO (sslv3 alert handshake failure)
Testing AES256-GCM-SHA384...NO (sslv3 alert handshake failure)
Testing AES256-SHA256...NO (sslv3 alert handshake failure)
Testing AES256-SHA...NO (sslv3 alert handshake failure)
Testing CAMELLIA256-SHA...NO (sslv3 alert handshake failure)
Testing PSK-AES256-CBC-SHA...NO (no ciphers available)
Testing ECDHE-RSA-DES-CBC3-SHA...NO (sslv3 alert handshake failure)
Testing ECDHE-ECDSA-DES-CBC3-SHA...NO (sslv3 alert handshake failure)
Testing SRP-DSS-3DES-EDE-CBC-SHA...NO (sslv3 alert handshake failure)
Testing SRP-RSA-3DES-EDE-CBC-SHA...NO (sslv3 alert handshake failure)
Testing EDH-RSA-DES-CBC3-SHA...NO (sslv3 alert handshake failure)
Testing EDH-DSS-DES-CBC3-SHA...NO (sslv3 alert handshake failure)
Testing AECDH-DES-CBC3-SHA...NO (sslv3 alert handshake failure)
Testing SRP-3DES-EDE-CBC-SHA...NO (sslv3 alert handshake failure)
Testing ADH-DES-CBC3-SHA...NO (sslv3 alert handshake failure)
Testing ECDH-RSA-DES-CBC3-SHA...NO (sslv3 alert handshake failure)
Testing ECDH-ECDSA-DES-CBC3-SHA...NO (sslv3 alert handshake failure)
Testing DES-CBC3-SHA...NO (sslv3 alert handshake failure)
Testing PSK-3DES-EDE-CBC-SHA...NO (no ciphers available)
Testing ECDHE-RSA-AES128-GCM-SHA256...YES
Testing ECDHE-ECDSA-AES128-GCM-SHA256...NO (sslv3 alert handshake failure)
Testing ECDHE-RSA-AES128-SHA256...NO (sslv3 alert handshake failure)
Testing ECDHE-ECDSA-AES128-SHA256...NO (sslv3 alert handshake failure)
Testing ECDHE-RSA-AES128-SHA...NO (sslv3 alert handshake failure)
Testing ECDHE-ECDSA-AES128-SHA...NO (sslv3 alert handshake failure)
Testing SRP-DSS-AES-128-CBC-SHA...NO (sslv3 alert handshake failure)
Testing SRP-RSA-AES-128-CBC-SHA...NO (sslv3 alert handshake failure)
Testing DHE-DSS-AES128-GCM-SHA256...NO (sslv3 alert handshake failure)
Testing DHE-RSA-AES128-GCM-SHA256...NO (sslv3 alert handshake failure)
Testing DHE-RSA-AES128-SHA256...NO (sslv3 alert handshake failure)
Testing DHE-DSS-AES128-SHA256...NO (sslv3 alert handshake failure)
Testing DHE-RSA-AES128-SHA...NO (sslv3 alert handshake failure)
Testing DHE-DSS-AES128-SHA...NO (sslv3 alert handshake failure)
Testing DHE-RSA-SEED-SHA...NO (sslv3 alert handshake failure)
Testing DHE-DSS-SEED-SHA...NO (sslv3 alert handshake failure)
Testing DHE-RSA-CAMELLIA128-SHA...NO (sslv3 alert handshake failure)
Testing DHE-DSS-CAMELLIA128-SHA...NO (sslv3 alert handshake failure)
Testing AECDH-AES128-SHA...NO (sslv3 alert handshake failure)
Testing SRP-AES-128-CBC-SHA...NO (sslv3 alert handshake failure)
Testing ADH-AES128-GCM-SHA256...NO (sslv3 alert handshake failure)
Testing ADH-AES128-SHA256...NO (sslv3 alert handshake failure)
Testing ADH-AES128-SHA...NO (sslv3 alert handshake failure)
Testing ADH-SEED-SHA...NO (sslv3 alert handshake failure)
Testing ADH-CAMELLIA128-SHA...NO (sslv3 alert handshake failure)
Testing ECDH-RSA-AES128-GCM-SHA256...NO (sslv3 alert handshake failure)
Testing ECDH-ECDSA-AES128-GCM-SHA256...NO (sslv3 alert handshake failure)
Testing ECDH-RSA-AES128-SHA256...NO (sslv3 alert handshake failure)
Testing ECDH-ECDSA-AES128-SHA256...NO (sslv3 alert handshake failure)
Testing ECDH-RSA-AES128-SHA...NO (sslv3 alert handshake failure)
Testing ECDH-ECDSA-AES128-SHA...NO (sslv3 alert handshake failure)
Testing AES128-GCM-SHA256...NO (sslv3 alert handshake failure)
Testing AES128-SHA256...NO (sslv3 alert handshake failure)
Testing AES128-SHA...NO (sslv3 alert handshake failure)
Testing SEED-SHA...NO (sslv3 alert handshake failure)
Testing CAMELLIA128-SHA...NO (sslv3 alert handshake failure)
Testing PSK-AES128-CBC-SHA...NO (no ciphers available)
Testing ECDHE-RSA-RC4-SHA...NO (sslv3 alert handshake failure)
Testing ECDHE-ECDSA-RC4-SHA...NO (sslv3 alert handshake failure)
Testing AECDH-RC4-SHA...NO (sslv3 alert handshake failure)
Testing ADH-RC4-MD5...NO (sslv3 alert handshake failure)
Testing ECDH-RSA-RC4-SHA...NO (sslv3 alert handshake failure)
Testing ECDH-ECDSA-RC4-SHA...NO (sslv3 alert handshake failure)
Testing RC4-SHA...NO (sslv3 alert handshake failure)
Testing RC4-MD5...NO (sslv3 alert handshake failure)
Testing PSK-RC4-SHA...NO (no ciphers available)
Testing EDH-RSA-DES-CBC-SHA...NO (sslv3 alert handshake failure)
Testing EDH-DSS-DES-CBC-SHA...NO (sslv3 alert handshake failure)
Testing ADH-DES-CBC-SHA...NO (sslv3 alert handshake failure)
Testing DES-CBC-SHA...NO (sslv3 alert handshake failure)
Testing EXP-EDH-RSA-DES-CBC-SHA...NO (sslv3 alert handshake failure)
Testing EXP-EDH-DSS-DES-CBC-SHA...NO (sslv3 alert handshake failure)
Testing EXP-ADH-DES-CBC-SHA...NO (sslv3 alert handshake failure)
Testing EXP-DES-CBC-SHA...NO (sslv3 alert handshake failure)
Testing EXP-RC2-CBC-MD5...NO (sslv3 alert handshake failure)
Testing EXP-ADH-RC4-MD5...NO (sslv3 alert handshake failure)
Testing EXP-RC4-MD5...NO (sslv3 alert handshake failure)
Testing ECDHE-RSA-NULL-SHA...NO (sslv3 alert handshake failure)
Testing ECDHE-ECDSA-NULL-SHA...NO (sslv3 alert handshake failure)
Testing AECDH-NULL-SHA...NO (sslv3 alert handshake failure)
Testing ECDH-RSA-NULL-SHA...NO (sslv3 alert handshake failure)
Testing ECDH-ECDSA-NULL-SHA...NO (sslv3 alert handshake failure)
Testing NULL-SHA256...NO (sslv3 alert handshake failure)
Testing NULL-SHA...NO (sslv3 alert handshake failure)
Testing NULL-MD5...NO (sslv3 alert handshake failure
&lt;/pre&gt;

I *can* open the server-url in the emulator&#39;s browser and get a perfect json response so I know the system itself is capable.

So the question is, why can&#39;t I connect on Android 7 ?

**Update**:

I&#39;ve looked at a captured packet using tcpdump and wireshark and the enabled ciphers are in the ClientHello, so that should not be a problem.

&lt;pre&gt;
Cipher Suites (18 suites)

Cipher Suite: Unknown (0xcca9)
Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02b)
Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02c)
Cipher Suite: Unknown (0xcca8)
Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f)
Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030)
Cipher Suite: TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x009e)
Cipher Suite: TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x009f)
Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (0xc009)
Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (0xc00a)
Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013)
Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014)
Cipher Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x0033)
Cipher Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039)
Cipher Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 (0x009c)
Cipher Suite: TLS_RSA_WITH_AES_256_GCM_SHA384 (0x009d)
Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA (0x002f)
Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA (0x0035)
&lt;/pre&gt;

As you can see ```0xc02f``` and ```0xc030``` match, but the next TLSv1.2 packet says: ```Alert (21), Handshake Failure (40)```.

**Update 2**:

These are the curves from Android 5.1 in the ClientHello:

&lt;pre&gt;
Elliptic curves (25 curves)

Elliptic curve: sect571r1 (0x000e)
Elliptic curve: sect571k1 (0x000d)
Elliptic curve: secp521r1 (0x0019)
Elliptic curve: sect409k1 (0x000b)
Elliptic curve: sect409r1 (0x000c)
Elliptic curve: secp384r1 (0x0018)
Elliptic curve: sect283k1 (0x0009)
Elliptic curve: sect283r1 (0x000a)
Elliptic curve: secp256k1 (0x0016)
Elliptic curve: secp256r1 (0x0017)
Elliptic curve: sect239k1 (0x0008)
Elliptic curve: sect233k1 (0x0006)
Elliptic curve: sect233r1 (0x0007)
Elliptic curve: secp224k1 (0x0014)
Elliptic curve: secp224r1 (0x0015)
Elliptic curve: sect193r1 (0x0004)
Elliptic curve: sect193r2 (0x0005)
Elliptic curve: secp192k1 (0x0012)
Elliptic curve: secp192r1 (0x0013)
Elliptic curve: sect163k1 (0x0001)
Elliptic curve: sect163r1 (0x0002)
Elliptic curve: sect163r2 (0x0003)
Elliptic curve: secp160k1 (0x000f)
Elliptic curve: secp160r1 (0x0010)
Elliptic curve: secp160r2 (0x0011)
&lt;/pre&gt;

In the ServerHello ```secp384r1 (0x0018)``` is returned.

And this is from Android 7:

&lt;pre&gt;
Elliptic curves (1 curve)

Elliptic curve: secp256r1 (0x0017)
&lt;/pre&gt;

Resulting in the Handshake Failure.

Changing the nginx configuration by removing secp384r1 or replacing it with the default (prime256v1) does get it to work. So I guess the question remains: am I able to add elliptic curves ?

The captured data is the same when using the emulator as when using an Android 7.0 device (General Mobile 4G).

**Update 3**:

Small update, but worth mentioning: I got it to work in the emulator using Android 7.1.1 (!). It shows the following data (again, grabbed using tcpdump and viewed using wireshark):

&lt;pre&gt;
Elliptic curves (3 curves)

Elliptic curve: secp256r1 (0x0017)
Elliptic curve: secp384r1 (0x0018)
Elliptic curve: secp512r1 (0x0019)
&lt;/pre&gt;

It shows the same 18 Cipher Suites.


SSLHandshakeException: Handshake failed on Android N/7.0

I found really weird bug that is reproduced only on Android N devices.

In tour of my app there is a possibility to change language. Here is the code that changes it. 

     public void update(Locale locale) {

        Locale.setDefault(locale);

        Configuration configuration = res.getConfiguration();

        if (BuildUtils.isAtLeast24Api()) {
            LocaleList localeList = new LocaleList(locale);

            LocaleList.setDefault(localeList);
            configuration.setLocales(localeList);
            configuration.setLocale(locale);

        } else if (BuildUtils.isAtLeast17Api()){
            configuration.setLocale(locale);

        } else {
            configuration.locale = locale;
        }

        res.updateConfiguration(configuration, res.getDisplayMetrics());
    }


This code works great in activity of my tour ( with `recreate()` call) but in all next activities all String resources are wrong. Screen rotation fixes it. What can i do with this problem? Should i change locale for Android N differently or it&#39;s just system bug?

P.S. Here&#39;s what i found. At first start of MainActivity (which is after my tour) `Locale.getDefault()` is correct but resources are wrong. But in other activities it gives me wrong Locale and wrong resources from this locale. After rotation screen (or perhaps some other configuration change) `Locale.getDefault()` is correct.

All Android 7.0-Nougat Solutions on Gang of Coders

Total of 15 Android 7.0-Nougat Solutions