Help debugging KDE Connect issue

[Aleix Pol]

I forgot to mention, even though I get those messages, no devices
appear in the connected/available fields.

Aleix

On Wed, Mar 25, 2015 at 6:32 PM, Albert Vaca <albertvaka at gmail.com> wrote:
> I would say this is normal: every time a new identity packet is received the
> phone opens a connection with the desktop client. There is some logic
> afterwards that will check if we already had a link to the same device, and
> will transparently switch to the most recent one.
>
> Recently I've sometimes seen that the link count increase above 3 links at
> the same time, which makes me think that maybe we are not deleting the old
> ones properly though :/
>
> Albert
>
> On Wed, Mar 25, 2015 at 10:23 AM, Aleix Pol <aleixpol at kde.org> wrote:
>>
>> Hi,
>> As you will know, I'm no Android guru, so I need your help.
>>
>> I've been having issues with KDE Connect pairing and just decided to
>> go into adb and see if there was a crash going on or something.
>> Everything I see when I refresh both from the android app and the KCM
>> is these messages [1].
>>
>> Do you have any idea of what could be going on?
>>
>> Cheers!
>> Aleix
>>
>> [1]
>> I/LanLinkProvider( 6202): Identity package received, creating link
>> I/LanLinkProvider( 6202): Identity package received, creating link
>> I/LanLinkProvider( 6202): Identity package received, creating link
>> I/LanLinkProvider( 6202): Identity package received, creating link
>> I/LanLinkProvider( 6202): Identity package received, creating link
>> _______________________________________________
>> KDEConnect mailing list
>> KDEConnect at kde.org
>> https://mail.kde.org/mailman/listinfo/kdeconnect
>
>