search

baljeetverma / android-notifier

Automatically exported from code.google.com/p/android-notifier
0 stars 0 forks source link

Notifications will only be recieved if the phone send a ping #326

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Notifications are not recieved till I send a ping from the phone. 

What steps will reproduce the problem?
1. Connect Laptop and Phone to WLAN
2. Recieve SMS 
3. See if there is a notification

What is the expected output? What do you see instead?
I expect to see a notification. But there is no, if I didn't ping the PC first. 

What version of the product are you using? On what operating system?
0.5.1 on Ubuntu 10.10 amd64 

I recieved SMS before 22:22, too. 

2010-12-27 20:30:40,065 INFO [ApplicationImpl] - Starting SWT
2010-12-27 20:30:41,470 INFO [ApplicationImpl] - Showing tray icon
2010-12-27 20:30:41,709 DEBUG [ServiceServerImpl] - Starting service server on 
port [10700]
2010-12-27 20:30:41,938 DEBUG [InetAddresses] - Looking for local address
2010-12-27 20:30:42,052 INFO [ApplicationImpl] - Starting [System default] 
broadcaster
2010-12-27 20:30:42,054 INFO [ApplicationImpl] - Starting [Libnotify] 
broadcaster
2010-12-27 20:30:42,231 INFO [ApplicationImpl] - Starting [TCP] receiver
2010-12-27 20:30:42,235 DEBUG [InetAddresses] - Local address found
2010-12-27 20:30:44,124 INFO [ApplicationImpl] - Starting [UDP] receiver
2010-12-27 20:30:44,416 INFO [ApplicationImpl] - Adding to startup
2010-12-27 22:20:40,431 INFO [NotificationManagerImpl] - Notification received: 
notificationId=1236260300993231, type=Ping
2010-12-27 22:46:00,303 INFO [NotificationManagerImpl] - Notification received: 
notificationId=38324055630300676, type=SMS
2010-12-27 22:55:51,010 INFO [NotificationManagerImpl] - Notification received: 
notificationId=38324073235399645, type=SMS
2010-12-27 23:00:21,307 INFO [NotificationManagerImpl] - Notification received: 
notificationId=38324084219466239, type=SMS

Original issue reported on code.google.com by mrstraus...@googlemail.com on 27 Dec 2010 at 10:02

GoogleCodeExporter commented 9 years ago 
I think this happened after the update to Android 2.2 on my Wildfire.

Original comment by mrstraus...@googlemail.com on 28 Dec 2010 at 10:40

GoogleCodeExporter commented 9 years ago 
I'm seeing a similar issue, I think with Gentoo and a Samsung Captivate.

Original comment by guardian...@gmail.com on 30 Dec 2010 at 5:18

GoogleCodeExporter commented 9 years ago 
Did a little digging with wireshark, it appears the broadcast isn't being sent, 
at least for UDP.  Trying a custom ip to see if that has the same behavior.

Original comment by guardian...@gmail.com on 31 Dec 2010 at 12:03

GoogleCodeExporter commented 9 years ago 
Custom IP using TCP doesn't work.

Easy to test, reboot your phone and then call it.  You should see a 
notification, but you don't.

Original comment by guardian...@gmail.com on 31 Dec 2010 at 6:02

GoogleCodeExporter commented 9 years ago 
I am having this issue. Running Ubuntu 10.10 netbook edition. Log shows that 
message received, but no notification shown. Works fine on my Win 7 Pro 32 and 
64 as well as Win 7 Starter.

Original comment by thomas.f...@gmail.com on 5 Jan 2011 at 2:58

Attachments:

GoogleCodeExporter commented 9 years ago 
I got the same issue, but im on Android 2.3.1!

Original comment by siriu...@gmail.com on 19 Jan 2011 at 11:28

GoogleCodeExporter commented 9 years ago 
samilar issue. replicated on both 2.2.1 and 2.2.2 on Nexus One (t-mobile 
varient)

"ping" from isnide notifier not required...
If phone has been to sleep and is turned on and used no notifications are sent. 
Opening remote notify and going back to home screen then notifications start 
working again.

On wifi - using both broadcast AND custom IP on local LAN to 3 differnte win 7 
32/64bit PC's.

Tried ringing the phone and thrid part test message through "tasker".

Original comment by pcreeves...@gmail.com on 26 Jan 2011 at 12:43

GoogleCodeExporter commented 9 years ago 
Yep same thing happens to me, Android 2.3.2.

It will only work if the service is restarted by going to the application 
itself. The service doesn't get KILLED, since if you check android services it 
has been running for some time (like 14hrs for me!)... but somehow message 
doesn't get to me!

Original comment by mohammed...@gmail.com on 24 Feb 2011 at 12:59

GoogleCodeExporter commented 9 years ago 
I have this problem too.  It appears that this is problem with the service on 
the phone going to sleep and only opening the application window (which seems 
to reset the service) fixes the problem:

2011-07-19 12:55:10,381 INFO [NotificationManagerImpl] - Notification received: 
notificationId=1286443935136705, type=Ping
2011-07-19 12:55:20,444 INFO [NotificationManagerImpl] - Notification received: 
notificationId=39880114747337306, type=Battery
2011-07-19 12:55:23,834 INFO [NotificationManagerImpl] - Notification received: 
notificationId=39880116379873972, type=Battery
2011-07-19 13:15:06,998 INFO [NotificationManagerImpl] - Notification received: 
notificationId=39880151592687327, type=Battery
2011-07-19 13:45:04,947 INFO [NotificationManagerImpl] - Notification received: 
notificationId=39880205099499744, type=Battery
2011-07-19 13:54:35,326 INFO [NotificationManagerImpl] - Notification received: 
notificationId=39879878918585714, type=Third-party
2011-07-19 13:55:03,967 INFO [NotificationManagerImpl] - Notification received: 
notificationId=39880223478355746, type=Battery
2011-07-19 13:55:54,623 INFO [NotificationManagerImpl] - Notification received: 
notificationId=39880224429002935, type=Battery
2011-07-19 14:29:44,527 INFO [NotificationManagerImpl] - Notification received: 
notificationId=39880285119422912, type=Battery
2011-07-19 14:29:48,871 INFO [NotificationManagerImpl] - Notification received: 
notificationId=39879941821239529, type=Third-party

Between 13:15:06,998 and 13:45:04,947 there were no notifications and all 
attempts to send notifications in this time were useless until I opened the 
application and a battery notification was sent immediately.

I have checked the packets being sent with Wireshark and no packets are 
recieved at the PC for any notifications once the service goes into this sleep 
state until you open the application on the phone again.  UDP and TCP packets 
appear as expected when the notifications are working properly.  "Third Party" 
notifications in my logs are from Tasker.

Original comment by rosswill...@gmail.com on 19 Jul 2011 at 4:45

GoogleCodeExporter commented 9 years ago 
I'm getting this too and going crazy!
I've tried every imaginable thing.
Yesterday I receive a ring notification somehow, but today - nothing!
Only ping notifications are displayed.
I've tried with and without encryption, custom IP address, opened ports, 
forwarded ports, you name it.

Please fix this!

Original comment by itieko...@gmail.com on 11 Aug 2011 at 5:53

GoogleCodeExporter commented 9 years ago 
I am also having the same problem - Mint Linux Debian Edition & MIUI Android 
2.3.7

Original comment by chrsp...@gmail.com on 15 May 2012 at 9:06

GoogleCodeExporter commented 9 years ago 
same problem here. it only works with the program window open. samsung galaxy 5 
with cyanogen mod 9.

Original comment by chris.n...@gmail.com on 27 Jul 2013 at 4:48