Crash in Android 8.1
Andy Holmes
andrew.g.r.holmes at gmail.com
Fri Jan 19 21:10:03 UTC 2018
It was my bad. After the update the app was letting me send SMS, but I
hadn't enabled the new permission so it was having issues. Thanks for
checking.
On Tue, Jan 16, 2018 at 4:11 PM, Andy Holmes
<andrew.g.r.holmes at gmail.com> wrote:
> Hmm, it seems to refresh after a force stop or reboot, but it comes
> back after a few messages. I can tell they're different packets
> because the time stamp is about 40 milliseconds later. I'll try
> clearing the app cache and repairing to see if it helps.
>
> On Tue, Jan 16, 2018 at 2:16 PM, Albert Vaca <albertvaka at gmail.com> wrote:
>> I can't reproduce it :/
>>
>> On Tue, Jan 16, 2018 at 11:03 PM, Andy Holmes <andrew.g.r.holmes at gmail.com>
>> wrote:
>>>
>>> Albert,
>>>
>>> I've just installed 1.7.1 from the play store. SMS events
>>> (kdeconnect.telephony/event: sms) seem to be duplicated, sometimes 4x
>>> by the telephony plugin. I fixed it temporarily with a force stop, but
>>> it has returned. Can you confirm?
>>>
>>> On Tue, Jan 16, 2018 at 12:40 PM, Albert Vaca <albertvaka at gmail.com>
>>> wrote:
>>> > Thanks Philip for the patch! I've just released version 1.7.1 with this
>>> > fix
>>> > for Android 8.1 (and the rest of changes recently merged to master).
>>> >
>>> > On Sat, Jan 6, 2018 at 2:48 PM, Albert Vaca <albertvaka at gmail.com>
>>> > wrote:
>>> >>
>>> >> Hi guys,
>>> >>
>>> >> Thanks for noticing this.
>>> >>
>>> >> Philip, can you send a patch adding 'synchronized', so we can at least
>>> >> mitigate the issue for now?
>>> >>
>>> >> There are reports of this crash on the Play Store console every few
>>> >> minutes... so I think it's crashing for every Android 8.1 user :/
>>> >>
>>> >> Unfortunately the stack trace is very unspecific on when/where/why this
>>> >> happens...
>>> >>
>>> >> Albert
>>> >>
>>> >> On Thu, Jan 4, 2018 at 12:35 AM, Philip Cohn-Cort <cliabhach at gmail.com>
>>> >> wrote:
>>> >>>
>>> >>> Hiya,
>>> >>>
>>> >>> I dunno if this helps, but I have a Nexus 6P with what I believe is
>>> >>> the
>>> >>> same build of 8.1.0, but a slightly different fatal backtrace. I've
>>> >>> added
>>> >>> that at https://paste.kde.org/ptolqcpya .
>>> >>>
>>> >>> I think it's possible that the platform's RSA key logic is not
>>> >>> threadsafe,
>>> >>> and so the root cause of that crash is some sort of race condition. I
>>> >>> could not get the app to crash at all when I added the 'synchronized'
>>> >>> keyword to LanLinkProvider's addLink function. Not sure that that's
>>> >>> the best place to synchronize, though...
>>> >>>
>>> >>> ~Philip Cohn-Cort
>>> >>>
>>> >>> On Wed, Jan 3, 2018 at 3:14 PM, Matthijs Tijink
>>> >>> <matthijstijink at gmail.com> wrote:
>>> >>> > Hi,
>>> >>> >
>>> >>> > I'm not sure what happens, but the dump seems to indicate the
>>> >>> > problem
>>> >>> > is in "/system/lib64/libssl.so". Some quick googling didn't reveal
>>> >>> > similar issues :-(
>>> >>> > Do you have Android Studio installed? If so, maybe you can run KDE
>>> >>> > Connect in the debugger and see where exactly it crashes.
>>> >>> >
>>> >>> > Kind regards,
>>> >>> >
>>> >>> > Matthijs Tijink
>>> >>> >
>>> >>> > 2018-01-03 17:55 GMT+01:00 Aleix Pol <aleixpol at kde.org>:
>>> >>> >> Hey,
>>> >>> >> Since my phone updated to 8.1 I've been having some crashes. KDE
>>> >>> >> Connect actually works quite well, but I have repeatedly dialogs
>>> >>> >> about
>>> >>> >> sending feedback when it happens to crash.
>>> >>> >>
>>> >>> >> I did an "adb logcat" to see if we can figure out what's going
>>> >>> >> wrong
>>> >>> >> (I don't really see much though). Here's what looks relevant to me.
>>> >>> >>
>>> >>> >> https://paste.kde.org/ptxzfshv2
>>> >>> >>
>>> >>> >> Any ideas? :/
>>> >>> >> Aleix
>>> >>
>>> >>
>>> >
>>
>>
More information about the KDEConnect
mailing list