Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Serval Mesh is overwriting device's bluetooth name #115

Open
rodneyrod opened this issue Feb 17, 2016 · 4 comments
Open

Serval Mesh is overwriting device's bluetooth name #115

rodneyrod opened this issue Feb 17, 2016 · 4 comments

Comments

@rodneyrod
Copy link

Installed the latest test build from Google Play on two phones and both have had their device name changed to something like:

Serval:Ѐ -,Ԁ

I'm not sure if this is supposed to happen or if it's a bug.

@lakeman
Copy link
Member

lakeman commented Apr 18, 2016

This is by design. It may not be an ideal design, and we may in future need a separate configuration option to control this behaviour.
We use the device name as the first step in identifying peers that are also running our software. When our software is disabled, the original name should be restored.
We can also use device names as a low bandwidth communication channel, if we can't establish any other link between devices.

@skylarmt
Copy link

the original name should be restored

I can confirm that doesn't happen.

@ShadwMan
Copy link

I can confirm that this keeps hijacking the bluetooth name. I had to uninstall to stop it from happening. Happens even when Serval is not run.

@axelsimon
Copy link

Adding confirmation to this.
Even though I have no one to test Serval with and therefore hardly ever run Serval, the sofware makes its presence known and continuously and aggressively overwrites my device's bluetooth name.

Only way to be able to set the name to something "normal" again is to uninstall.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants