Tasnime / gtalksms

Automatically exported from code.google.com/p/gtalksms
0 stars 0 forks source link

No Notification of Phone Call Until After Answered or Muted #59

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Connect GTalkSMS
2. Call Phone
3. No Notification via IM until 
     a. Phone is answered
     b. phone is muted

What is the expected output? What do you see instead?
Once a phone call is being received, an IM via GTalkSMS should be notifying me 
of the phone call.

What version of the product are you using? On what operating system?
GTalkSMS v1.7.1 @ Yakoo
Droid X running Android 2.2.1

This was happening before the project owner switch as well.  Just FYI.

Original issue reported on code.google.com by nat...@mynarcik.com on 21 Jan 2011 at 7:06

GoogleCodeExporter commented 9 years ago
I am unable to reproduce this. Can you please generate a log 
http://code.google.com/p/gtalksms/wiki/GenerateAppLog

Original comment by fschm...@gmail.com on 29 Jan 2011 at 4:25

GoogleCodeExporter commented 9 years ago
Ok, just tried to reproduce it myself.  Had someone in my contacts try and call 
me.  Worked like a charm.  My assumption is that the issue only occurs when a 
number that is not in your contacts calls you.  I will try this method and then 
post the log.

Original comment by nat...@mynarcik.com on 29 Jan 2011 at 6:36

GoogleCodeExporter commented 9 years ago
Ok, just did it again.  It was from a number not in my contact list.  Phone is 
ringing. I waited for about 20-30 secs then ignored.  At that moment when I 
ignored the call, I was sent a message saying '########## is calling...'

Immediately created the log file below:

Version: 1.8
Kernel info: 2.6.32.9-g55626e1
w30471@il93lnxdroid08 )
#1 PREEMPT Sun Nov 7 23:24:32 CST 2010

--------- beginning of /dev/log/system
--------- beginning of /dev/log/main
01-31 17:22:19.577 D/gtalksms(13397): Xmpp packet received
01-31 17:22:30.468 D/gtalksms(13397): Xmpp packet received
01-31 17:23:44.320 D/gtalksms(13397): Xmpp packet received

Original comment by nat...@mynarcik.com on 31 Jan 2011 at 10:31

GoogleCodeExporter commented 9 years ago

Original comment by fschm...@gmail.com on 1 Feb 2011 at 6:35

GoogleCodeExporter commented 9 years ago
I suspect a boolean in the callListener of gtalksms to be the culprint.
Florent: Have you seen my message in the dev ml? 
https://groups.google.com/forum/#!msg/gtalksms-dev/23OeErUr9jA/a6KldjFxY8sJ
Do you know something about the purpose of the bool?

I just ran some tests without the bool and the callListener seems to be working 
fine. If its really not needed and just causing some trouble we should remove 
it (see attached bundle).

Original comment by fschm...@gmail.com on 4 Feb 2011 at 5:29

Attachments:

GoogleCodeExporter commented 9 years ago
Bug reporter, can you install the attached apk and get back if the problem 
still occurs?

Original comment by fschm...@gmail.com on 5 Feb 2011 at 8:16

Attachments:

GoogleCodeExporter commented 9 years ago
And could you also test if multiple succesive calls result in reduntant 
"calling" notifications?

Original comment by fschm...@gmail.com on 5 Feb 2011 at 8:37

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
For some reason, the apk will not install. I go to install and I chose which 
packager to use, it gives me the confirmation screen to overwrite. Then I hit 
ok when it shows what the app needs to access. After that it says installing, 
then returns "Application was not installed".

Any suggestions? 

Original comment by nat...@mynarcik.com on 5 Feb 2011 at 5:03

GoogleCodeExporter commented 9 years ago
It's not an official release, so you must uninstall the official one before 
install this one.
But you are going to loose your settings.

Original comment by Florent....@gmail.com on 5 Feb 2011 at 5:16

GoogleCodeExporter commented 9 years ago
Installed.  Will report back early next week.  

Thanks guys!

Original comment by nat...@mynarcik.com on 6 Feb 2011 at 5:50

GoogleCodeExporter commented 9 years ago
Same issue as before.  GTalkSMS was one all day and now I just recieved a call 
from a number outside of my contacts and no notification from GTalkSMS until I 
mute or the call ends.

Version: 1.8
Kernel info: 2.6.32.9-g55626e1
w30471@il93lnxdroid08 )
#1 PREEMPT Sun Nov 7 23:24:32 CST 2010

--------- beginning of /dev/log/system
--------- beginning of /dev/log/main
02-07 17:24:21.059 D/gtalksms(29738): Xmpp packet received
02-07 17:24:50.333 D/gtalksms(29738): Xmpp packet received

Original comment by nat...@mynarcik.com on 7 Feb 2011 at 10:26

GoogleCodeExporter commented 9 years ago
We could add some debugging output to the listener. But it looks like a 
hardware/software specific issue, as we can't reproduce it and you said that 
this is since talkmyphone and only if someone not in your contact list calls.

Do you get with the apk reduntant "calling" notifications, if the same number 
calls multiple times?

We'll have to think about the next actions.

Original comment by fschm...@gmail.com on 8 Feb 2011 at 2:34

GoogleCodeExporter commented 9 years ago
Actually, it worked at the beginning of talkmyphone. I can't remember what
stage of it's development where it changed. What I don't get is, when a
contact calls it notifies me before the phone even rings. Why does a
non-contact matter?

I do not get redundant notifications though. Just late ones.
 On Feb 8, 2011 9:35 AM, <gtalksms@googlecode.com> wrote:

list

Original comment by nat...@mynarcik.com on 8 Feb 2011 at 3:28

GoogleCodeExporter commented 9 years ago
It shouldn't, the intent is broadcast-ed (normally) no matter if the contact is 
in your phone book or not. At the end you get a reply so there has to be an 
intent for it.

note to self: 
http://code.google.com/p/talkmyphone/source/browse/src/com/googlecode/talkmyphon
e/PhoneCallListener.java?r=8af11d80a4d73a4d8d1621e80a8dfcd5333a4d26 shows no 
significant changes over its lifetime.

Original comment by fschm...@gmail.com on 8 Feb 2011 at 6:36

GoogleCodeExporter commented 9 years ago
What if in your switch statement, you allowed a case for EXTRA_INCOMING_NUMBER?

http://developer.android.com/reference/android/telephony/TelephonyManager.html#A
CTION_PHONE_STATE_CHANGED

Not sure if that will deem the results you guys are after, but trying to spark 
something to get this issue resolved.  I do find it concerning that I am the 
only one experiencing this. 

Original comment by nat...@mynarcik.com on 8 Feb 2011 at 7:11

GoogleCodeExporter commented 9 years ago
Or even EXTRA_STATE_RINGING?

Original comment by nat...@mynarcik.com on 8 Feb 2011 at 7:14

GoogleCodeExporter commented 9 years ago
current phone callListener does not use the switch statement anymore.
BTW: did you loose your gtalksms configuration by installing the .apk?

Original comment by fschm...@gmail.com on 10 Feb 2011 at 9:44

GoogleCodeExporter commented 9 years ago
Yes, lost the config and noticed it doesn't set a reply contact on sms
messages now.

Original comment by nat...@mynarcik.com on 10 Feb 2011 at 12:53

GoogleCodeExporter commented 9 years ago
Rooted phone, fresh new ROM and still same results...

You guys still can't replicate eh?

Original comment by nat...@mynarcik.com on 10 Mar 2011 at 11:45

GoogleCodeExporter commented 9 years ago
Nope sorry, but there is now a log message (with time stamp), called 
"PhoneCallListener Call State Ringing with incomingNumber:" for every phone 
call we notice. Generate a log or install the Alogcat App ( 
https://market.android.com/details?id=org.jtb.alogcat ) and check if you see 
this log message and look for the time stamp.
But as it works for most of the people, I am stuck here on how to fix this...
(could be some hardware specific behavior)

Original comment by fschm...@gmail.com on 11 Mar 2011 at 12:19

GoogleCodeExporter commented 9 years ago
Latest Log...

Version: 2.0
Kernel info: 2.6.32.9-g55626e1
w30471@il93lnxdroid08 )
#1 PREEMPT Sun Nov 7 23:24:32 CST 2010

--------- beginning of /dev/log/system
--------- beginning of /dev/log/main
03-11 16:35:47.350 I/gtalksms( 3348): PhoneCallListener Call State Ringing with 
incomingNumber:7326671641
03-11 16:35:51.670 D/gtalksms( 3348): Xmpp packet received
03-11 16:37:37.905 E/AndroidRuntime( 3664): FATAL EXCEPTION: main
03-11 16:37:37.905 E/AndroidRuntime( 3664): java.lang.RuntimeException: Unable 
to instantiate application android.app.Application: 
java.lang.NullPointerException
03-11 16:37:37.905 E/AndroidRuntime( 3664): at 
android.app.ActivityThread$PackageInfo.makeApplication(ActivityThread.java:661)
03-11 16:37:37.905 E/AndroidRuntime( 3664): at 
android.app.ActivityThread.handleBindApplication(ActivityThread.java:4306)
03-11 16:37:37.905 E/AndroidRuntime( 3664): at 
android.app.ActivityThread.access$3200(ActivityThread.java:129)
03-11 16:37:37.905 E/AndroidRuntime( 3664): at 
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2145)
03-11 16:37:37.905 E/AndroidRuntime( 3664): at 
android.os.Handler.dispatchMessage(Handler.java:99)
03-11 16:37:37.905 E/AndroidRuntime( 3664): at 
android.os.Looper.loop(Looper.java:143)
03-11 16:37:37.905 E/AndroidRuntime( 3664): at 
android.app.ActivityThread.main(ActivityThread.java:4701)
03-11 16:37:37.905 E/AndroidRuntime( 3664): at 
java.lang.reflect.Method.invokeNative(Native Method)
03-11 16:37:37.905 E/AndroidRuntime( 3664): at 
java.lang.reflect.Method.invoke(Method.java:521)
03-11 16:37:37.905 E/AndroidRuntime( 3664): at 
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
03-11 16:37:37.905 E/AndroidRuntime( 3664): at 
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
03-11 16:37:37.905 E/AndroidRuntime( 3664): at 
dalvik.system.NativeStart.main(Native Method)
03-11 16:37:37.905 E/AndroidRuntime( 3664): Caused by: 
java.lang.NullPointerException
03-11 16:37:37.905 E/AndroidRuntime( 3664): at 
android.app.ActivityThread$PackageInfo.initializeJavaContextClassLoader(Activity
Thread.java:541)
03-11 16:37:37.905 E/AndroidRuntime( 3664): at 
android.app.ActivityThread$PackageInfo.getClassLoader(ActivityThread.java:486)
03-11 16:37:37.905 E/AndroidRuntime( 3664): at 
android.app.ActivityThread$PackageInfo.makeApplication(ActivityThread.java:653)
03-11 16:37:37.905 E/AndroidRuntime( 3664): ... 11 more
03-11 16:37:37.936 E/AndroidRuntime( 3664): Error reporting crash
03-11 16:37:37.936 E/AndroidRuntime( 3664): java.lang.IllegalArgumentException: 
Unknown package: org.damazio.notifier
03-11 16:37:37.936 E/AndroidRuntime( 3664): at 
android.os.Parcel.readException(Parcel.java:1251)
03-11 16:37:37.936 E/AndroidRuntime( 3664): at 
android.os.Parcel.readException(Parcel.java:1235)
03-11 16:37:37.936 E/AndroidRuntime( 3664): at 
android.app.ActivityManagerProxy.handleApplicationCrash(ActivityManagerNative.ja
va:2515)
03-11 16:37:37.936 E/AndroidRuntime( 3664): at 
com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeIni
t.java:76)
03-11 16:37:37.936 E/AndroidRuntime( 3664): at 
java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:887)
03-11 16:37:37.936 E/AndroidRuntime( 3664): at 
java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:884)
03-11 16:37:37.936 E/AndroidRuntime( 3664): at 
dalvik.system.NativeStart.main(Native Method)
03-11 16:44:32.834 D/gtalksms( 3348): onFailedToReceiveInterstitial
03-11 16:44:33.155 D/gtalksms( 3348): Update presence: ********@gmail.com - Away
03-11 16:44:33.162 D/gtalksms( 3348): Update presence: ********@gmail.com - 
Offline
03-11 16:44:33.162 D/gtalksms( 3348): Update presence: ********@gmail.com - 
Online
03-11 16:44:33.178 D/gtalksms( 3348): Update presence: ********@gmail.com - 
Online
03-11 16:44:33.178 D/gtalksms( 3348): Update presence: ********@gmail.com - 
Offline
03-11 16:44:33.186 D/gtalksms( 3348): Update presence: ********@gmail.com - 
Online
03-11 16:44:33.186 D/gtalksms( 3348): Update presence: ********@gmail.com - Away
03-11 16:44:33.186 D/gtalksms( 3348): Update presence: ********@gmail.com - 
Online
03-11 16:44:33.194 D/gtalksms( 3348): Update presence: ********@gmail.com - 
Offline
03-11 16:44:33.209 D/gtalksms( 3348): Update presence: ********@gmail.com - 
Offline
03-11 16:44:33.209 D/gtalksms( 3348): Update presence: ********@gmal.com - 
Offline
03-11 16:44:33.217 D/gtalksms( 3348): Update presence: ********@gmail.com - 
Offline
03-11 16:44:33.225 D/gtalksms( 3348): Update presence: ********@gmail.com - 
Online
03-11 16:44:33.233 D/gtalksms( 3348): Update presence: ********@gmail.com - 
Offline
03-11 16:44:33.233 D/gtalksms( 3348): Update presence: ********@gmail.com - 
Offline
03-11 16:44:33.233 D/gtalksms( 3348): Update presence: ********@gmail.com - 
Offline
03-11 16:44:33.436 D/gtalksms( 3348): onFailedToReceiveInterstitial

Original comment by nat...@mynarcik.com on 11 Mar 2011 at 9:46

GoogleCodeExporter commented 9 years ago
03-11 16:35:47.350 I/gtalksms( 3348): PhoneCallListener Call State Ringing with 
incomingNumber:7326671641
At least this shows that the PhoneCallListener is reporting properly.
The next GTalkSMS release will have improved log message, which could help to 
find the error in your case. I have attached new debug version.

Original comment by fschm...@gmail.com on 12 Mar 2011 at 12:37

Attachments:

GoogleCodeExporter commented 9 years ago
No reports since 6 month. Please report back if the issue still exists or if we 
can close this.

Original comment by fschm...@gmail.com on 30 Nov 2011 at 10:13

GoogleCodeExporter commented 9 years ago
This issue still exists for me.  I haven't tried it with the latest update that 
was downloaded yesterday.  Will post back with results.

Original comment by nat...@mynarcik.com on 30 Nov 2011 at 10:16

GoogleCodeExporter commented 9 years ago
Any results?

Original comment by fschm...@gmail.com on 27 Dec 2011 at 11:06

GoogleCodeExporter commented 9 years ago
I just installed gtalksms for the first time on my Samsung Galaxy S2. 
Everything seems to be working as expected, but I don't get any IM's at all 
when someone calls me (not while ringing or if I press engaged). The setting is 
ticked. When I receive an SMS, I am notified immediately. Is there something I 
can do to help you find the bug or is the problem on my side?

Original comment by tomas.s....@gmail.com on 29 Dec 2011 at 2:34

GoogleCodeExporter commented 9 years ago
@thomas: An App Log is always the first step when it comes to tracing down 
problems. Please generate and send us one: 
http://code.google.com/p/gtalksms/wiki/GenerateAppLog

Original comment by fschm...@gmail.com on 29 Dec 2011 at 2:45

GoogleCodeExporter commented 9 years ago
I followed the instructions in the link you attached, and called myself and 
hung up without doing anything on the phone. No IM. Here's the log:

GTalkSMS Preferences
notifiedAddress: XXXXXXX
useDifferentAccount: true
useGoogleMapUrl: true
locale: default
smsMagicWord: GTalkSMS
manuallySpecifyServerSettings: false
batteryNotificationInterval: 10
serviceName: gmail.com
startAtBoot: true
showStatusIcon: true
useCompression: false
notificationIncomingSmsType: same
notifyBatteryInStatus: true
login: XXXXXXX
ringtone: content://media/internal/audio/media/34
displayIconIndex: 0
xmppSecurityMode: opt
debugLog: true
smsNumber: 5
notifySmsSent: true
callLogsNumber: 10
roomPassword: XXXXXXX
serverHost: talk.google.com
serverPort: 5222
mucServer: conference.jwchat.org
notifyBattery: false
notifyIncomingCalls: true

GTalkSMS Version: 3.3
Android API: 10
Kernel info: 2.6.35.7-I9100XWKI4-CL575468
root@DELL143 )
#2 SMP PREEMPT Wed Sep 14 20:49:18 KST 2011

--------- beginning of /dev/log/system
--------- beginning of /dev/log/main

Original comment by tomas.s....@gmail.com on 29 Dec 2011 at 3:02

GoogleCodeExporter commented 9 years ago
The log is empty :( Make sure that GTalkSMS is running and connected. It's also 
a good idea to kill GTalkSMS with an task killer and restart the GTalkSMS 
service before taking the log.

Original comment by fschm...@gmail.com on 29 Dec 2011 at 4:12

GoogleCodeExporter commented 9 years ago
Yeah, I thought it looked a little bit minimal...  By killing it with task 
killer and then restarting the program, IMs now work for phone calls!! Thanks 
for your prompt replies!

Original comment by tomas.s....@gmail.com on 29 Dec 2011 at 5:15

GoogleCodeExporter commented 9 years ago
Hi,
I have the same issue with notification of incomming calls - I receive 
notification after end of ringing (when I reply to call or calling abonent drop 
the call).
BUT this problem arrive only when my phone is connected to Internet over GPRS, 
with WiFi connection I immediatelly receive notification about incoming call.

Hardware/software:
GTalkSMS 4.2
Sony Ericsson Xpreia Mini Pro running Android 2.3.4

I attached two log files:
1) gtalksms_latenotifincall.txt - connection over GPRS (problem exists)
2) gtalksms_latenotif_wifi.txt - connection over WiFi (no problem)

Original comment by oleg.tsi...@gmail.com on 7 Sep 2012 at 2:47

Attachments:

GoogleCodeExporter commented 9 years ago
@oleg that is not surprisingly: If you phone is connected via 2G then a call 
will disrupt data connectivity, which will be restored if you call is ended. 
Therefore GTalkSMS has to chance to send the notification before or while the 
call is ongoing.

Original comment by fschm...@gmail.com on 7 Sep 2012 at 3:01

GoogleCodeExporter commented 9 years ago
Closing. It's normal if the phone is no more connected.

Original comment by Florent....@gmail.com on 8 Mar 2015 at 5:12

GoogleCodeExporter commented 9 years ago

Original comment by Florent....@gmail.com on 8 Mar 2015 at 5:12