Threema: Jolla C (LED) notification
asked 2016-08-07 23:10:48 +0300
Hi,
I successfully moved my Threema account to the Jolla C and activated the notification as described here. I have polling and background services activated but I do not always get a notification. Sometimes I have to start Threema to get new messages. On my "old" Jolla this was only the case if I haven't had started the app after a reboot.
The second thing that is different now is the LED notification. It used to be a blue blinking, now I it is a steady white. Did something change here in the chat application list or is the white LED a new feature? Can anybody share their Threema experience on the Jolla C?
Thanks
afaik Jolla C has only single color white LED.
avhakola ( 2016-08-08 01:15:03 +0300 )editI can confirm the first and IMHO more important issue: threema messages are not that reliable on the Jolla C as they have been on my Jolla 1. This is really annoying. Does anyone have similar problems with other messaging apps (e.g. whatsapp)?
lenggi ( 2016-08-08 10:09:11 +0300 )editi also had this issue that sometimes threema don't connect to the mobile network. So i hat to restart the app.
monkeyisland ( 2016-08-08 11:50:54 +0300 )editso i have activate a logcat in threema...
here is some of the outputs....
Strange by changing wlan to mobile data...
I can say when i disconnect WLAN no messages arrive till i deactivate mobile Data and after activate mobile Data.
###################################
Sat Aug 13 15:08:24 MESZ 2016 NetworkInfo: type: mobile[UMTS], state: DISCONNECTED/DISCONNECTED, reason: apnChanged, extra: fake, roaming: false, failover: true, isAvailable: true, isConnectedToProvisioningNetwork: false Sat Aug 13 15:08:24 MESZ 2016 Connectivity change broadcast received: device is now OFFLINE Sat Aug 13 15:08:24 MESZ 2016 acquireConnection: source = connectivity_change, refCount = 1 Sat Aug 13 15:08:24 MESZ 2016 releaseConnectionLinger: source = connectivity_change, timeout = 30000 Sat Aug 13 15:08:24 MESZ 2016 releaseConnection: source = connectivity_change, refCount = 0 Sat Aug 13 15:08:24 MESZ 2016 ThreemaConnection state changed: CONNECTING Port: 5222 Sat Aug 13 15:08:24 MESZ 2016 ThreemaConnection state changed: DISCONNECTED Port: 443 Sat Aug 13 15:08:25 MESZ 2016 acquireConnection: source = activityResumed, refCount = 1 Sat Aug 13 15:08:28 MESZ 2016 ThreemaConnection state changed: CONNECTING Port: 443 Sat Aug 13 15:08:28 MESZ 2016 ThreemaConnection state changed: CONNECTED Port: 443 Sat Aug 13 15:08:28 MESZ 2016 ThreemaConnection state changed: LOGGEDIN Port: 443 Sat Aug 13 15:08:28 MESZ 2016 process ACK for message 12a4df8c5b8f083d Sat Aug 13 15:08:28 MESZ 2016 incoming message ID 617da7e010dbe0fe from ECHOECHO to D695T2FF Sat Aug 13 15:08:28 MESZ 2016 process delivery receipt for message ID 12a4df8c5b8f083d (state = READ) Sat Aug 13 15:08:28 MESZ 2016 incoming message ID ed5b2073a470f7c2 from ECHOECHO to D695T2FF Sat Aug 13 15:08:28 MESZ 2016 Nonce: 5891559c8e8cb7c156f772bca1da161217e8635c51a22181 Sat Aug 13 15:08:28 MESZ 2016 Data: 2577996fedab60c18973f7aa6fc9f5105acd187717a8372abf76b1ffc319 Sat Aug 13 15:08:28 MESZ 2016 Public key (ECHOECHO): 4a6a1b34dcef15d43cb74de2fd36091be99fbbaf126d099d47d83d919712c72b Sat Aug 13 15:08:28 MESZ 2016 processIncomingContactMessage: ed5b2073a470f7c2 Sat Aug 13 15:08:29 MESZ 2016 Showing notification d173e2e0-6f17-4b91-9efe-0d1d01c6b0a9 Sat Aug 13 15:08:29 MESZ 2016 Enqueue delivery receipt (delivered) message ID bec046ed00cbf179 for message ID ed5b2073a470f7c2 from ECHOECHO Sat Aug 13 15:08:29 MESZ 2016 process ACK for message bec046ed00cbf179 Sat Aug 13 15:08:30 MESZ 2016 NetworkInfo: type: mobile[UMTS], state: CONNECTED/CONNECTED, reason: connected, extra: fake, roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false
monkeyisland ( 2016-08-13 16:38:15 +0300 )edit