<table><tr><td style="">nicolasfella added a comment.
</td><a style="text-decoration: none; padding: 4px 8px; margin: 0 8px 8px; float: right; color: #464C5C; font-weight: bold; border-radius: 3px; background-color: #F7F7F9; background-image: linear-gradient(to bottom,#fff,#f1f0f1); display: inline-block; border: 1px solid rgba(71,87,120,.2);" href="https://phabricator.kde.org/D9296" rel="noreferrer">View Revision</a></tr></table><br /><div><div><p>Disclaimer: Anything following might be wrong<br />
As far as I understand there is a difference between broadcast and multicast (see <a href="http://www.utilizewindows.com/the-difference-between-unicast-multicast-and-broadcast-messages/" class="remarkup-link" target="_blank" rel="noreferrer">http://www.utilizewindows.com/the-difference-between-unicast-multicast-and-broadcast-messages/</a>). We are BROADcasting to discover devices (to 255.255.255.255 to be specific), so this might not change anything at all.<br />
On the other hand, the second link indeed implies that this could solve some issues. It would be nice if we actually found somebody with a concrete issue.</p></div></div><br /><div><strong>REPOSITORY</strong><div><div>R225 KDE Connect - Android application</div></div></div><br /><div><strong>REVISION DETAIL</strong><div><a href="https://phabricator.kde.org/D9296" rel="noreferrer">https://phabricator.kde.org/D9296</a></div></div><br /><div><strong>To: </strong>mtijink, KDE Connect<br /><strong>Cc: </strong>nicolasfella<br /></div>