Device ID formatting

Hello,

I would expect that the purpose of “DeviceID” is to identify a Syncthing instance on another device. Why isn’t this field automatically filled in during installation, in order to allow the user to give the device a more easily recognizable name or description?

.

I am wondering why I do get the folowing error-message after typeing an qunique description to the Device ID field:

“the device ID is not formatted correctly”

Thank’s in advance!

You are not meant to edit the device id. It is meant to be globally unique and it is tied to the device keys.

You say it is not filled in during installation. It should be. How did you install and run Syncthing?

There is no description available, but you can set your own device name if you go to Actions → Settings in the Web GUI.

2 Likes

Yes the same with v1.30.0.1 and v2.0.3.0.

With Obtainium from Github resource URL (Releases · Catfriend1/syncthing-android · GitHub)

Just tapped the blue Syncthing icon on the Android (16) startup screen.

Can you show some screenshots?

1 Like

What a shame… but in the other profile there was no typing error :slight_smile:

Sorry! I(or rather Obtainium) downloaded it from:

1 Like

This version is installed:

What is the actual issue? As stated before, device IDs are automatically generated and you cannot modify them. What you can edit to your liking are device names :slight_smile:.

No, they are not automatically generated..

.

Am I seeing this correctly? In the other profile of GOS, there should be a different device name under AZ?

Thank you!

Do you mean that you’re trying to run Syncthing in different profiles on GrapheneOS? If yes, then this information should have definitely been included in the original post, as we have likely just been wasting time here… :downcast_face_with_sweat:

Running Syncthing in different profiles on Android is similar to running multiple Syncthing instances on the same device, and it requires some tweaks (e.g. using different ports for the GUI, listeners, etc.) to actually make it work.

I don’t think there exist any official documentation on this, but if you search the forum for “multiple instances” or “android profiles”, you should be able to find more detailed information on which exact settings need to be modified.

1 Like

I didn’t expect that the fact I’m trying to sync between different GrapheneOS profiles was so important that it needed to be mentioned. Sorry about that!

Also, I thought this should be clear, since I enabled (x) Local Discovery and defined a port number in the WebUI TCP port option.

Up to now, I haven’t found the crucial information. Of course, I would be very grateful for any additional hints.

First of all, is Syncthing working in your main profile, or are you experiencing the same issue in all profiles? Basically, what should happen is when you install the app and launch it for the first time, a new device ID is generated, and you cannot change it unless you clear the app data and start from scratch (or you’ve got root access and delete the key files, but that’s yet another story :wink:).

In other words, I would make sure that Syncthing is up and running in the main profile first, and only then try to install and run it in other profiles as well. Also, I think there are some restrictions in the OS about what can run in other profiles at the same time, so I’m not sure if running Syncthing simultaneously like that is actually possible.

Thank you for your continuous help and patience! I am trying to put your recommendations into practice. At the moment, the following is still unclear to me:

Under “Add Device,” there is a field called A’Z.

Is my assumption correct that in every different instance of Syncthing a different name has to be defined/entered?

That is the device name field. You can put anything you want there, it doesn’t need to match. Each side can just assign a name that makes sense to call the other instance.

1 Like

Is it even necessary to enter a description into the device name field?

No, if you are fine with memorizing partial device IDs (mostly random characters).

1 Like

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