File Name Recognition Problem On Android

[lisp]

First, I am a Korean.

I have been using the v1.3 version to the current v1.4.83 btsync. (Android platform)

Well, I had no problem using 1.3. But the file name is not a recognized problem in v1.4.

Often the problem is not recognized properly, like the Korean file name.

For example, a non-recognized btsync such as "1234-산" file name.

So, the file is not synced.

The problem is only in the Android version.

 

[RomanZ]

@lisp

 

Just to make sure I understand you correctly:

 

1) When you were using Sync 1.3, files with Korean symbols in filename were syncing to PC with no issues.

2) After you upgraded your PC and Android device to 1.4, files with Korean symbols no longer sync.

 

Is this correct?

If yes - I'll need your debug logs. 

[lisp]

You said it exactly right.

The problem appears only in v1.4 of the Android platform.

I will attach the log file of the Windows platform.

But there is nothing about the file name inside the log files.

File name is '1234-산'

This file has a clear inside the folder of the internal memory.

However, this name does not appear in the Android app.

 

 

IP 10.1.1.21  is my android phone.

 

 

version: 1.4.83

platform: Windows workstation 6.1.7601 x86

[2014-09-24 00:03:46] total physical memory 4294967295 max disk cache 33554432

[2014-09-24 00:03:46] Using IP address 10.1.1.50

[2014-09-24 00:03:46] Aes BCrypt algorithm provider has been loaded and initialized

[2014-09-24 00:03:46] Loading config file version 1.4.83

[2014-09-24 00:03:46] SF[79BC]: Loaded folder \\?\C:\Down\btsync\image

[2014-09-24 00:03:46] failed to set IP_ADD_MEMBERSHIP for 169.254.122.75:0: -1

[2014-09-24 00:03:46] failed to set IP_ADD_MEMBERSHIP for 169.254.52.243:0: -1

[2014-09-24 00:03:49] Incoming connection from 10.1.1.21:30822

[2014-09-24 00:03:49] Incoming connection from 10.1.1.21:53041

[2014-09-24 00:03:56] NAT-PMP: Unable to map port with NAT-PMP.

[2014-09-24 00:03:56] Incoming connection from 10.1.1.1:38152

[2014-09-24 00:04:17] Incoming connection from 10.1.1.21:53041

[2014-09-24 00:07:18] Incoming connection from 10.1.1.21:53044

[2014-09-24 00:07:18] Incoming connection from 10.1.1.1:38155

[2014-09-24 00:07:18] Incoming connection from 10.1.1.21:53044

[2014-09-24 00:07:20] Incoming connection from 10.1.1.21:30822

[2014-09-24 00:07:31] Incoming connection from 10.1.1.21:53044

[2014-09-24 00:08:02] Incoming connection from 10.1.1.21:53046

[2014-09-24 00:08:02] Incoming connection from 10.1.1.1:38157

[2014-09-24 00:08:02] Incoming connection from 10.1.1.21:53046

[2014-09-24 00:08:02] Incoming connection from 10.1.1.21:30822

[2014-09-24 00:08:16] Incoming connection from 10.1.1.21:53046

[2014-09-24 00:08:47] Incoming connection from 10.1.1.21:53048

[2014-09-24 00:08:47] Incoming connection from 10.1.1.1:38159

[2014-09-24 00:08:48] Incoming connection from 10.1.1.21:53048

[2014-09-24 00:09:01] Incoming connection from 10.1.1.21:30822

[2014-09-24 00:09:01] Incoming connection from 10.1.1.21:53048

[2014-09-24 00:10:00] Incoming connection from 10.1.1.21:53048

[2014-09-24 00:10:32] Incoming connection from 10.1.1.21:53050

[2014-09-24 00:10:32] Incoming connection from 10.1.1.1:38161

[2014-09-24 00:10:33] Incoming connection from 10.1.1.21:53050

[2014-09-24 00:10:33] Incoming connection from 10.1.1.21:30822

[2014-09-24 00:10:50] Incoming connection from 10.1.1.21:53050

[2014-09-24 00:11:21] Incoming connection from 10.1.1.21:53052

[2014-09-24 00:11:21] Incoming connection from 10.1.1.1:38163

[2014-09-24 00:11:21] Incoming connection from 10.1.1.21:53052

[2014-09-24 00:11:23] Incoming connection from 10.1.1.21:30822

[2014-09-24 00:11:37] Incoming connection from 10.1.1.21:53052

[2014-09-24 00:12:07] Incoming connection from 10.1.1.21:53055

[2014-09-24 00:12:07] Incoming connection from 10.1.1.1:38166

[2014-09-24 00:12:08] Incoming connection from 10.1.1.21:53055

[2014-09-24 00:12:37] Incoming connection from 10.1.1.21:30822

[2014-09-24 00:12:37] Incoming connection from 10.1.1.21:53055

[2014-09-24 00:13:08] Incoming connection from 10.1.1.21:53057

[2014-09-24 00:13:08] Incoming connection from 10.1.1.1:38168

[2014-09-24 00:13:08] Incoming connection from 10.1.1.21:53057

[2014-09-24 00:13:09] Incoming connection from 10.1.1.21:30822

[2014-09-24 00:13:32] Incoming connection from 10.1.1.21:53057

[2014-09-24 00:13:42] Incoming connection from 10.1.1.21:53059

[2014-09-24 00:13:42] Incoming connection from 10.1.1.1:38170

[2014-09-24 00:13:42] SyncEncryptHandler: bad shareID (STATE_BEGIN)

[2014-09-24 00:13:42] SyncEncryptHandler: bad shareID (STATE_BEGIN)

[2014-09-24 00:13:42] Shutdown. Saving config sync.dat

 

[RomanZ]

@lisp

The log you show belongs to your desktop - and it is not debug log. Could you please tap "Send feedback" on your Android phone and agree to send debugging information? If you already did that - could you please let me know the number of ticket you get assigned?

[lisp]

@RomanZ

Thank you for your kindly response.

I just now sent the debug log. 

Ticket number is #13936

[RomanZ]

@lisp

 

Thanks! We are aware of this isssue. It is fixed already and will be included in next Android update.