Closed awlx closed 10 years ago
Until Jolla delivers SDK for the new release, there is not much I can do.
New SDK is now available. https://together.jolla.com/question/60940/sailfish-os-sdk-update-1410-released/
Another bug is, that the call notification does not work.
Yep, looks like something has changed:
Oct 28 19:38:19 Jolla pebbled[13475]: 28.10.2014 19:38[0x01d19278] WARN Qt - QObject::connect: No such signal org::nemomobile::voicecall::VoiceCall::statusChanged()
Oct 28 19:38:20 Jolla pebbled[13475]: 28.10.2014 19:38[0x01d19278] WARN Qt - QObject::connect: No such signal org::nemomobile::voicecall::VoiceCall::lineIdChanged()
Oct 28 19:38:20 Jolla pebbled[13475]: 28.10.2014 19:38[0x01d19278] WARN Qt - QObject::connect: No such signal org::nemomobile::voicecall::VoiceCall::durationChanged()
Oct 28 19:38:20 Jolla pebbled[13475]: 28.10.2014 19:38[0x01d19278] WARN Qt - QObject::connect: No such signal org::nemomobile::voicecall::VoiceCall::startedAtChanged()
Oct 28 19:38:20 Jolla pebbled[13475]: 28.10.2014 19:38[0x01d19278] WARN Qt - QObject::connect: No such signal org::nemomobile::voicecall::VoiceCall::emergencyChanged()
Oct 28 19:38:20 Jolla pebbled[13475]: 28.10.2014 19:38[0x01d19278] WARN Qt - QObject::connect: No such signal org::nemomobile::voicecall::VoiceCall::multipartyChanged()
Oct 28 19:38:20 Jolla pebbled[13475]: 28.10.2014 19:38[0x01d19278] WARN Qt - QObject::connect: No such signal org::nemomobile::voicecall::VoiceCall::forwardedChanged()
Oct 28 19:38:30 Jolla pebbled[13475]: 28.10.2014 19:38[0x01d19278] ERROR Manager - Error: "Telepathy Handler Invalidated: org.freedesktop.Telepathy.Error.Terminated - Release By User
doing some tests with the 1410 sdk
Maybe you can fix the crash bug :x. https://github.com/smokku/pebble/pull/24
yea i noticed a segfault :) do you mean this?
Yep, I think this is because of the QtByteArray error mentioned in the other thread.
Ok, found the problem for call notification, fixing right now.
Working Call notification version: http://smurfy.de/files/jolla/pebble-0.12-1-update9_1.armv7hl.rpm Source: https://github.com/smurfy/pebble/commits/fix_update9
I try some things to reproduce the crash.
I cannot reproduce the test on command. It happens from time to time when something gets read from socket. But like every 5 - 15mins for me. Pebble version is 2.7.
ok, lol i'm still at 2.5 :) but i'm in luck, i have a S5 laying around at the moment to update ^^
my build has debug logging enabled so hopefully i will notice what message causes the segfault.
Ok, hopefully it will be easy to fix :). I did not see any message because it crashed right after receiving :-/. The only thing I saw is posted in the mentioned thread.
I am running your build, too. Hopefully the crash won't occur ;).
Ok, this was fast ;).
28.10.2014 21:48[0x00f6f278] DEBUG watch::WatchConnector - read
28.10.2014 21:48[0x00f6f278] FATAL Qt - ASSERT: "uint(i) < uint(size())" in file /usr/include/qt5/QtCore/qbytearray.h, line 414
28.10.2014 21:48[0x00f6f278] DEBUG ::LoggerRepository - Shutting down Hierarchy
Do you have many notifications or is it mostily silence? :)
Mostly silent.
Ok, after enabling logging via the android app i'm able to get it crash more often. I think i found the code where it crashes. Using some debug output to narrow it down.
Found the problem, working on a fix
Nice one!
Updated Version: http://smurfy.de/files/jolla/pebble-0.12-1-update9_2.armv7hl.rpm
Hi,
I just installed the new Jolla update with plenty of features. But now pebbled is unable to start because of the following error: writev(2, [{"pebbled", 7}, {": ", 2}, {"symbol lookup error", 19}, {": ", 2}, {"pebbled", 7}, {": ", 2}, {"undefined symbol: _ZN11QtBluetoo"..., 71}, {"", 0}, {"", 0}, {"\n", 1}], 10pebbled: symbol lookup error: pebbled: undefined symbol: _ZN11QtBluetooth16QBluetoothSocket16staticMetaObjectE ) = 111
Cheers