Help debugging KDE Connect issue

[Aleix Pol]

On Mon, Mar 30, 2015 at 1:55 AM, Aleix Pol <aleixpol at kde.org> wrote:
> On Sun, Mar 29, 2015 at 8:37 AM, Albert Vaca <albertvaka at gmail.com> wrote:
>> I reviewed the LanLinkProvider code and fixed some minor things, including a
>> potential "Too Many Open Files" crash because  we were holding a reference
>> to a socket and thus preventing the garbage collector to do its job
>> releasing it. I don't think this is your problem, though, so we need to keep
>> investigating. I built a version with more debug messages for you to try so
>> we have more information:
>>
>> https://dl.dropboxusercontent.com/u/8820360/apks/kdeconnect-android-debug.apk
>>
>> Also the logs are prefixed by "KDE/" so it's easier for you to filter them.
>>
>>
>> On Wed, Mar 25, 2015 at 10:35 AM, Aleix Pol <aleixpol at kde.org> wrote:
>>>
>>> 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
>>> >
>>> >
>>
>>
>
> I haven't been able to reproduce the problem now, but I have a
> different set up today. I'll keep on trying... :/
>
> Aleix

I managed to reproduce the error again, that's the adb logcat output I
get on refresh:
I/KDE/BackgroundService(29555): OnNetworkChange
E/KDE/LanLinkProvider(29555): onNetworkChange
E/KDE/FileCount(29555): 58
E/KDE/FileCount(29555): 56
I/KDE/LanLinkProvider(29555): Using tcpPort 1714
E/KDE/FileCount(29555): 58
E/KDE/LanLinkProvider(29555): Sending packet to 1 ips
I/KDE/LanLinkProvider(29555): Udp identity package sent to address
/255.255.255.255

Does that tell you anything?

Aleix