Reset phone: Can't get past "Loading"

(Lance Haverkamp) #1

Been using Syncthing for several months. My Android MotoG4+ crashed, so I had to do a factory reset on the phone. Now Syncthing won’t completely load, It said generating keys, the circle goes around, it said “loading…”, eventually I get a “taking too long” error from syncthing. Wiped & restarted a few times, it’s repeatable 100% of the time. Nothing else is installed on the phone other than what’s factory from Motorola & Google, Syncthing it the only other app on the phone.

Here’s the Syncthing log:

--------- beginning of main 02-28 17:02:56.779 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:56 http: TLS handshake error from 127.0.0.1:48392: remote error: tls: illegal parameter 02-28 17:02:56.787 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:56 http: TLS handshake error from 127.0.0.1:48394: tls: client offered an unsupported, maximum protocol version of 302 02-28 17:02:56.800 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:56 http: TLS handshake error from 127.0.0.1:48395: tls: client offered an unsupported, maximum protocol version of 301 02-28 17:02:57.030 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:57 http: TLS handshake error from 127.0.0.1:48398: remote error: tls: illegal parameter 02-28 17:02:57.037 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:57 http: TLS handshake error from 127.0.0.1:48399: tls: client offered an unsupported, maximum protocol version of 302 02-28 17:02:57.043 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:57 http: TLS handshake error from 127.0.0.1:48400: tls: client offered an unsupported, maximum protocol version of 301 02-28 17:02:57.313 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:57 http: TLS handshake error from 127.0.0.1:48402: remote error: tls: illegal parameter 02-28 17:02:57.319 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:57 http: TLS handshake error from 127.0.0.1:48404: tls: client offered an unsupported, maximum protocol version of 302 02-28 17:02:57.330 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:57 http: TLS handshake error from 127.0.0.1:48405: tls: client offered an unsupported, maximum protocol version of 301 02-28 17:02:57.562 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:57 http: TLS handshake error from 127.0.0.1:48407: remote error: tls: illegal parameter 02-28 17:02:57.568 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:57 http: TLS handshake error from 127.0.0.1:48408: tls: client offered an unsupported, maximum protocol version of 302 02-28 17:02:57.576 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:57 http: TLS handshake error from 127.0.0.1:48409: tls: client offered an unsupported, maximum protocol version of 301 02-28 17:02:57.814 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:57 http: TLS handshake error from 127.0.0.1:48411: remote error: tls: illegal parameter 02-28 17:02:57.821 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:57 http: TLS handshake error from 127.0.0.1:48412: tls: client offered an unsupported, maximum protocol version of 302 02-28 17:02:57.833 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:57 http: TLS handshake error from 127.0.0.1:48413: tls: client offered an unsupported, maximum protocol version of 301 02-28 17:02:58.087 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:58 http: TLS handshake error from 127.0.0.1:48415: remote error: tls: illegal parameter 02-28 17:02:58.099 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:58 http: TLS handshake error from 127.0.0.1:48416: tls: client offered an unsupported, maximum protocol version of 302 02-28 17:02:58.107 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:58 http: TLS handshake error from 127.0.0.1:48417: tls: client offered an unsupported, maximum protocol version of 301 02-28 17:02:58.333 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:58 http: TLS handshake error from 127.0.0.1:48418: remote error: tls: illegal parameter 02-28 17:02:58.340 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:58 http: TLS handshake error from 127.0.0.1:48419: tls: client offered an unsupported, maximum protocol version of 302 02-28 17:02:58.347 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:58 http: TLS handshake error from 127.0.0.1:48420: tls: client offered an unsupported, maximum protocol version of 301 02-28 17:02:58.579 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:58 http: TLS handshake error from 127.0.0.1:48422: remote error: tls: illegal parameter 02-28 17:02:58.592 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:58 http: TLS handshake error from 127.0.0.1:48423: tls: client offered an unsupported, maximum protocol version of 302 02-28 17:02:58.603 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:58 http: TLS handshake error from 127.0.0.1:48424: tls: client offered an unsupported, maximum protocol version of 301 02-28 17:02:58.849 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:58 http: TLS handshake error from 127.0.0.1:48426: remote error: tls: illegal parameter 02-28 17:02:58.853 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:58 http: TLS handshake error from 127.0.0.1:48427: tls: client offered an unsupported, maximum protocol version of 302 02-28 17:02:58.862 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:58 http: TLS handshake error from 127.0.0.1:48428: tls: client offered an unsupported, maximum protocol version of 301 02-28 17:02:59.116 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:59 http: TLS handshake error from 127.0.0.1:48452: remote error: tls: illegal parameter 02-28 17:02:59.122 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:59 http: TLS handshake error from 127.0.0.1:48454: tls: client offered an unsupported, maximum protocol version of 302 02-28 17:02:59.129 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:59 http: TLS handshake error from 127.0.0.1:48455: tls: client offered an unsupported, maximum protocol version of 301 02-28 17:02:59.375 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:59 http: TLS handshake error from 127.0.0.1:48456: remote error: tls: illegal parameter 02-28 17:02:59.384 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:59 http: TLS handshake error from 127.0.0.1:48459: tls: client offered an unsupported, maximum protocol version of 302 02-28 17:02:59.390 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:59 http: TLS handshake error from 127.0.0.1:48460: tls: client offered an unsupported, maximum protocol version of 301 02-28 17:02:59.612 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:59 http: TLS handshake error from 127.0.0.1:48461: remote error: tls: illegal parameter 02-28 17:02:59.619 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:59 http: TLS handshake error from 127.0.0.1:48463: tls: client offered an unsupported, maximum protocol version of 302 02-28 17:02:59.626 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:59 http: TLS handshake error from 127.0.0.1:48464: tls: client offered an unsupported, maximum protocol version of 301 02-28 17:02:59.877 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:59 http: TLS handshake error from 127.0.0.1:48465: remote error: tls: illegal parameter 02-28 17:02:59.885 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:59 http: TLS handshake error from 127.0.0.1:48466: tls: client offered an unsupported, maximum protocol version of 302 02-28 17:02:59.895 W/SyncthingNativeCode( 6787): 2019/03/01 00:02:59 http: TLS handshake error from 127.0.0.1:48467: tls: client offered an unsupported, maximum protocol version of 301 02-28 17:03:00.149 W/SyncthingNativeCode( 6787): 2019/03/01 00:03:00 http: TLS handshake error from 127.0.0.1:48468: remote error: tls: illegal parameter 02-28 17:03:00.155 W/SyncthingNativeCode( 6787): 2019/03/01 00:03:00 http: TLS handshake error from 127.0.0.1:48470: tls: client offered an unsupported, maximum protocol version of 302 02-28 17:03:00.165 W/SyncthingNativeCode( 6787): 2019/03/01 00:03:00 http: TLS handshake error from 127.0.0.1:48471: tls: client offered an unsupported, maximum protocol version of 301 02-28 17:03:00.416 W/SyncthingNativeCode( 6787): 2019/03/01 00:03:00 http: TLS handshake error from 127.0.0.1:48473: remote error: tls: illegal parameter 02-28 17:03:00.423 W/SyncthingNativeCode( 6787): 2019/03/01 00:03:00 http: TLS handshake error from 127.0.0.1:48474: tls: client offered an unsupported, maximum protocol version of 302 02-28 17:03:00.429 W/SyncthingNativeCode( 6787): 2019/03/01 00:03:00 http: TLS handshake error from 127.0.0.1:48475: tls: client offered an unsupported, maximum protocol version of 301

(Max) #2

It’s a known issue and was discussed here: Android and TLS1.2

As for what to do, there’s a beta version floating around which fixes this issue, but I think it’s not available in playstore yet.

#3

Do you have any link for “floating around”? I’m facing the same blocking on startup issue on a Kitkat phone. Yeah, I know, the phone is bloody old and it runs an outdated Android. That’s what happens to everyone who tries to use a hardware as long as reasonable and who did not buy a mainstream phone sold in large amounts.

(Max) #4

The official version which fixes these issue has been released as v0.10.19 just 9 hours ago, and it’s already available in the playstore. On F-Droid it seems to be still pending, their website still lists 0.10.17 as the most recent.

The apk I was talking about can be found on syncthing’s build server, but as far as I’m aware it’s only available as a non-signed debug apk and those don’t play well with official-codesigned builds so I can’t recommend using this in production, as it will likely mess things up.

Edit: Apparently I was totally wrong, the build server does have signed release builds; The most recent (0.10.19) is this one: https://build.syncthing.net/repository/download/Syncthing_Release_ReleaseSyncthingAndroid/35304:id/release/app-release.apk

(Login as guest to download)

(Bt90) #5

I think it’s already fixed in the syncthing-fork app: https://play.google.com/store/apps/details?id=com.github.catfriend1.syncthingandroid

(Catfriend1) #6

@Bt90 no need to advertise the fork as we already released the same fix with official 0.10.19 :wink:

(system) closed #7

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