[Android] After 0.10.16-beta1 update this happens.

Support
1

Okay, so I was happy about to use the app and this showed up on the 1st run:

  1. After the 1st run, and the setup wizard, it goes to this:

image
image720×1280 47.5 KB

  1. I switch tasks and after opening the app again it keeps on that screen forever, won’t let me open the material menu or the plus sign.

image
image720×1280 79.3 KB

  1. On WiFi tethering it shows me this message:

image
image720×1280 71.4 KB

Within the settings…

image
image720×1280 140 KB

Then, after opening the settings, even I toggled everything on/off, it keeps showing the message and hangs on the main screen forever.

  1. After a while, I decided to connect to my router again and it showed me this option:

image
image720×1280 61.9 KB

Here’s a fragment of the activity log. I pasted only the lines that repeats a lot on it. The rest is all redundant.

Activity log (fragment, click to view)

--------- beginning of main

01-16 17:29:21.332 W/SyncthingNativeCode(24196): 2019/01/16 19:29:21 http: TLS handshake error from 127.0.0.1:42793: remote error: tls: illegal parameter

01-16 17:29:21.337 W/SyncthingNativeCode(24196): 2019/01/16 19:29:21 http: TLS handshake error from 127.0.0.1:42794: tls: client offered an unsupported, maximum protocol version of 302

01-16 17:29:21.341 W/SyncthingNativeCode(24196): 2019/01/16 19:29:21 http: TLS handshake error from 127.0.0.1:42795: tls: client offered an unsupported, maximum protocol version of 301

01-16 17:29:21.554 W/SyncthingNativeCode(24196): 2019/01/16 19:29:21 http: TLS handshake error from 127.0.0.1:42796: remote error: tls: illegal parameter

I didn’t try on other devices yet. I just need to transfer some important data from the PC to the phone. If it helps, I’m on a Xiaomi Redmi Note 4X running MIUI 10. Here are further details:

image
image720×1280 110 KB

Just tell me if I need to roll back to the stable release, post it on GitHub or somewhere else.

Oh, not to forget that this discussion is also on Telegram. (Link)

PS: Don’t mind the Portuguese UI. I just wanted to make this quick. But the visuals must be enough to recognize the error. :grin:

Thanks for the help.

2

It seems the version of android you are using does not support TLS 3, which seems to be required for the new version of syncthing. I guess the only way forward is to downgrade.

3

That’s what I thought. Thanks for the reply. I’ll leave the Google Play beta program then.

However, why such no support on a beta version? Just fmi.

4

It’s dependant on Android version rather than the app version.

5

So, are you telling that it’s a fault on my Android version that doesn’t support TLS 3? If yes, what am I supposed to do? Won’t newer versions of Syncthing include such built-in support? Or I just need to wait until Xiaomi devs do something about it? :thinking:

Sorry for so many dumb questions.

6

That’s a reasonably modern Android which should support TLS 1.2 (the actual relevant version number). I’m not sure why it claims not to.

1 Like
7

On my android 9, the beta works fine, so either android 7 is too old, or Xaomi has some magic hacks in their android version.

One thing I noticed in this case is the fact that go conplains about tls in this case, not android, which is strange.

8

Alright, if you guys want some further details on this, I guess I can help. I’m not a programmer, just an enthusiast. But tell me if there’s anything I can do for you to solve this riddle. :wink:

9

@calmh ideas why go would be complaining?

10

Not really, but are you sure that’s the real issue? The great variety of different errors in a short timespan feels to me like the client is capability probing. If it finally tries with TLS 1.2, we’d get no visible indication of it.

(Also, I guess the app could use HTTP locally, no?)

11

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.