Closed GoogleCodeExporter closed 8 years ago
What steps will reproduce the problem? Don't really know. It seems to be more frequent with one of my devices that has roaming disabled and is only connected when in Wifi range. What is the expected output? Connection should happen (or abandon and retry later). What do you see instead? GtalkSms is stuck in "Connecting" state. No way to restart connection by hand (must force-quit). Additional informations: Log (of my Galaxy S2) doesn't show anything: GTalkSMS Preferences notifiedAddress: florian@loitsch.com notifySmsInChatRooms: false useGoogleMapUrl: true XMPPSecurityOptional: 3 connectionSettingsObsolete: false manuallySpecifyServerSettings: false notifySmsSentDelivered: true batteryNotificationInterval: 10 startAtBoot: true forceMucServer: false showStatusIcon: true XMPPSecurityDisabled: 1 notificationIncomingSmsType: same notifyBatteryInStatus: true notifyInMuc: false login: XXX@gmail.com stopOnPowerDisconnected: false dontDisplayRecipient: false notifySmsDelivered: false batteryNotificationIntervalInt: 10 notifySmsSent: true callLogsNumber: 10 roomPassword: gtalksms serverHost: talk.google.com notifySmsInSameConversation: true showSentSms: false mucServer: conference.jwchat.org notifyApplicationConnection: false notifyBattery: false locale: default smsMagicWord: GTalkSMS formatResponses: false publicIntentsEnabled: false XMPPSecurityRequired: 2 useOpenStreetMapUrl: false serviceName: gmail.com xmppSecurityModeInt: 3 markSmsReadOnReply: false useCompression: false startOnBoot: false smsReplySeparate: false startOnPowerConnected: true startOnWifiConnected: true debugLog: true stopOnWifiDisconnected: false smsNumber: 5 connectOnMainscreenShow: true publicIntentTokenRequired: false serverPort: 0 notifyIncomingCalls: true stopOnPowerDelay: 1 publicIntentToken: secret GTalkSMS Version: 4.3 Android API: 17 Kernel info: 3.0.64-CM-g855d6a6 build02@cyanogenmod) ) #1 SMP PREEMPT Fri Jun 21 00:21:44 PDT 2013 Phone model: Galaxy S2 (cyanogenmod) and Nexus 4 (stock).
Original issue reported on code.google.com by florian@loitsch.com on 18 Jul 2013 at 3:04
florian@loitsch.com
Seems to be duplicate of issue 290.
Original comment by florian@loitsch.com on 18 Jul 2013 at 3:07
Original comment by Florent....@gmail.com on 1 Oct 2013 at 9:18
Florent....@gmail.com
Original issue reported on code.google.com by
florian@loitsch.com
on 18 Jul 2013 at 3:04