Closed GoogleCodeExporter closed 8 years ago
Hmm, so you basically saying that you can't get GTalkSMS to login (!=
registration) with your google credentials?
This should work. Hence the name GTalk..sms. Please generate an app log.
Original comment by fschm...@gmail.com
on 15 Jun 2011 at 6:08
So, my google apps domain is 'varovalka.com' and I'm trying to login to email
account 'android'.
In pidgin there is entry 'domain', which I set to 'varovalka.com' and under
advanced tab there is 'connect server' which I set to 'talk.google.com'.
There is no domain and connect server separation in GTalkSms, but just 'Server
host' which I set to 'talk.google.com' and I tried to add domain information by
adding domain name to the login name under 'Login' entry, which I set to
'android@varovalka.com'.
GTalkSMS Preferences
notifiedAddress: kukovec@gmail.com
useDifferentAccount: true
useGoogleMapUrl: true
locale: default
manuallySpecifyServerSettings: true
batteryNotificationInterval: 10
startAtBoot: false
serviceName: talk.google.com
showStatusIcon: true
notifyBatteryInStatus: false
notificationIncomingSmsType: same
useCompression: false
ringtone: content://media/internal/audio/media/13
login: android@varovalka.com
displayIconIndex: 0
startOnWifiConnected: false
debugLog: true
stopOnWifiDisconnected: true
smsNumber: 5
notifySmsSent: true
callLogsNumber: 10
roomPassword: gtalksms
serverHost: talk.google.com
serverPort: 5222
mucServer: conference.jwchat.org
notifyApplicationConnection: false
notifyBattery: false
notifyIncomingCalls: false
GTalkSMS Version: 2.2.4
Android API: 8
Kernel info: 2.6.32.15-gf5a401c
htc-kernel@and18-2 )
#1 PREEMPT Thu Sep 16 21:44:24 CST 2010
--------- beginning of /dev/log/system
--------- beginning of /dev/log/main
06-16 14:45:39.634 I/gtalksms( 1320): service destroyed
06-16 14:46:12.974 I/gtalksms( 1320): service destroyed
06-16 14:47:40.044 E/gtalksms( 1320): xmpp login failed: SASL authentication
failed using mechanism DIGEST-MD5
06-16 14:47:43.814 I/gtalksms( 1320): service destroyed
Original comment by marko.ku...@gmail.com
on 16 Jun 2011 at 12:58
GTalkSMS has the same setting: connection settings -> enable "manual server
settings" -> got to "server settings" -> here you can set the (xmpp) domain and
the server's host.
Can you try that?
Original comment by fschm...@gmail.com
on 16 Jun 2011 at 4:51
Under 'server settings' I have 3 fields:
- Server host which I set to 'talk.google.com'
- Server port which I left by default '5222'
- Service name; is this meant as 'domain' setting? I set it to 'varovalka.com'
Login name is now just 'android'. Registration is still unsuccessful.
GTalkSMS Preferences
notifiedAddress: kukovec@gmail.com
useDifferentAccount: true
useGoogleMapUrl: true
locale: default
manuallySpecifyServerSettings: true
batteryNotificationInterval: 10
startAtBoot: false
serviceName: varovalka.com
showStatusIcon: true
notifyBatteryInStatus: false
notificationIncomingSmsType: same
useCompression: false
ringtone: content://media/internal/audio/media/13
login: android
displayIconIndex: 0
startOnWifiConnected: false
debugLog: true
stopOnWifiDisconnected: true
smsNumber: 5
notifySmsSent: true
callLogsNumber: 10
roomPassword: gtalksms
serverHost: talk.google.com
serverPort: 5222
mucServer: conference.jwchat.org
notifyApplicationConnection: false
notifyBattery: false
notifyIncomingCalls: false
GTalkSMS Version: 2.2.4
Android API: 8
Kernel info: 2.6.32.15-gf5a401c
htc-kernel@and18-2 )
#1 PREEMPT Thu Sep 16 21:44:24 CST 2010
--------- beginning of /dev/log/system
--------- beginning of /dev/log/main
06-16 22:31:39.100 I/gtalksms( 1320): service destroyed
06-16 22:32:27.331 E/gtalksms( 1320): xmpp login failed: SASL authentication
failed using mechanism DIGEST-MD5
06-16 22:32:32.040 I/gtalksms( 1320): service destroyed
06-16 22:33:18.170 E/gtalksms( 1320): xmpp login failed: SASL authentication
failed using mechanism DIGEST-MD5
06-16 22:33:23.480 I/gtalksms( 1320): service destroyed
Original comment by kuko...@gmail.com
on 16 Jun 2011 at 8:38
Looks like there is a newline at the serviceName. Please try to remove that.
Original comment by fschm...@gmail.com
on 21 Jun 2011 at 10:42
I tried it multiple times with no success. There is no new line in serviceName.
I do all the entering with touch screen keyboard. When I configure for
jabber.org account, login is successful.
Original comment by marko.ku...@gmail.com
on 22 Jun 2011 at 11:13
Currently I have GTalkSMS v3.0 installed and it looks like this 'Issue 186' is
no longer a problem. It works as expected.
Under 'server settings':
- Login '<phone_account>@varovalka.com'
- Server host which I set to 'talk.google.com'
- Server port which I left by default '5222'
- Service name; is meant as 'domain' and is set to 'google.com'
GTalkSMS Preferences
notifiedAddress: <notify_account>@gmail.com
useDifferentAccount: true
useGoogleMapUrl: true
locale: default
manuallySpecifyServerSettings: true
batteryNotificationInterval: 10
serviceName: google.com
showStatusIcon: false
notificationIncomingSmsType: same
notifyBatteryInStatus: true
login: <phone_account>@varovalka.com
smsReplySeparate: false
startOnWifiConnected: true
stopOnWifiDisconnected: true
debugLog: true
smsNumber: 5
notifySmsSent: true
callLogsNumber: 10
roomPassword: gtalksms
serverHost: talk.google.com
serverPort: 5222
mucServer: conference.jwchat.org
notifyApplicationConnection: false
notifyBattery: false
notifyIncomingCalls: false
GTalkSMS Version: 3.0
Android API: 8
Kernel info: 2.6.32.15-gf5a401c
htc-kernel@and18-2 )
#1 PREEMPT Thu Sep 16 21:44:24 CST 2010
Original comment by marko.ku...@gmail.com
on 2 Aug 2011 at 11:50
Great so I'll close this issue as invalid.
Original comment by Florent....@gmail.com
on 2 Aug 2011 at 12:07
Original issue reported on code.google.com by
marko.ku...@gmail.com
on 15 Jun 2011 at 12:40