search

swechha / android-notifier

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

not sending messages to computer #116

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
D/WifiService(   92): ACTION_BATTERY_CHANGED pluggedType: 1
D/WifiService(   92): acquireWifiLockLocked: WifiLock{NetworkLocationProvider 
type=2 binder=android.os.Binder@45f60d98}
D/WifiService(   92): enable and start wifi due to updateWifiState
D/WifiService(   92): releaseWifiLockLocked: WifiLock{NetworkLocationProvider 
type=2 binder=android.os.Binder@45f60d98}
D/WifiService(   92): enable and start wifi due to updateWifiState
D/WifiWatchdogService(   92): (android.server.ServerThread) Hopkins 
(00:24:36:9b:50:6b) does not require the watchdog
D/WifiService(   92): releaseWifiLockLocked: 
WifiLock{org.damazio.notifier.WifiEnable type=1 
binder=android.os.BinderProxy@462895c8}
D/WifiService(   92): enable and start wifi due to updateWifiState
D/WifiService(   92): acquireWifiLockLocked: 
WifiLock{org.damazio.notifier.WifiEnable type=1 
binder=android.os.BinderProxy@46339e30}
D/WifiService(   92): disable wifi due to updateWifiState
D/WifiService(   92): ACTION_BATTERY_CHANGED pluggedType: 1
D/WifiService(   92): acquireWifiLockLocked: WifiLock{NetworkLocationProvider 
type=2 binder=android.os.Binder@45f60d98}
D/WifiService(   92): enable and start wifi due to updateWifiState
D/WifiService(   92): ACTION_SCREEN_ON
D/WifiService(   92): enable and start wifi due to updateWifiState
D/WifiService(   92): releaseWifiLockLocked: WifiLock{NetworkLocationProvider 
type=2 binder=android.os.Binder@45f60d98}
D/WifiService(   92): enable and start wifi due to updateWifiState
D/WifiWatchdogService(   92): (android.server.ServerThread) Hopkins 
(00:24:36:9b:50:6b) does not require the watchdog
D/WifiService(   92): releaseWifiLockLocked: 
WifiLock{org.damazio.notifier.WifiEnable type=1 
binder=android.os.BinderProxy@46339e30}
D/WifiService(   92): enable and start wifi due to updateWifiState
D/WifiService(   92): acquireWifiLockLocked: 
WifiLock{org.damazio.notifier.WifiEnable type=1 
binder=android.os.BinderProxy@45f85c70}
D/WifiService(   92): disable wifi due to updateWifiState
D/WifiService(   92): ACTION_BATTERY_CHANGED pluggedType: 1
D/WifiService(   92): acquireWifiLockLocked: WifiLock{NetworkLocationProvider 
type=2 binder=android.os.Binder@45f60d98}
D/WifiService(   92): enable and start wifi due to updateWifiState
D/WifiWatchdogService(   92): (android.server.ServerThread) Hopkins 
(00:24:36:9b:50:6b) does not require the watchdog
D/WifiService(   92): releaseWifiLockLocked: 
WifiLock{org.damazio.notifier.WifiEnable type=1 
binder=android.os.BinderProxy@45f85c70}
D/WifiService(   92): enable and start wifi due to updateWifiState
D/WifiService(   92): releaseWifiLockLocked: WifiLock{NetworkLocationProvider 
type=2 binder=android.os.Binder@45f60d98}
D/WifiService(   92): disable wifi due to updateWifiState
D/WifiService(   92): ACTION_BATTERY_CHANGED pluggedType: 1
D/WifiService(   92): acquireWifiLockLocked: WifiLock{NetworkLocationProvider 
type=2 binder=android.os.Binder@45f60d98}
D/WifiService(   92): enable and start wifi due to updateWifiState
D/WifiWatchdogService(   92): (android.server.ServerThread) Hopkins 
(00:24:36:9b:50:6b) does not require the watchdog
D/WifiService(   92): releaseWifiLockLocked: WifiLock{NetworkLocationProvider 
type=2 binder=android.os.Binder@45f60d98}
D/WifiService(   92): enable and start wifi due to updateWifiState
D/WifiService(   92): ACTION_SCREEN_OFF
D/WifiService(   92): ACTION_BATTERY_CHANGED pluggedType: 1
D/WifiService(   92): ACTION_SCREEN_ON
D/WifiService(   92): enable and start wifi due to updateWifiState
D/WifiService(   92): ACTION_SCREEN_OFF
D/WifiService(   92): ACTION_SCREEN_ON
D/WifiService(   92): enable and start wifi due to updateWifiState
I/RemoteNotifier( 7785): Starting notification service
D/RemoteNotifier( 7785): Battery status: Charging
D/RemoteNotifier( 7785): Got battery level: 53
D/RemoteNotifier( 7785): Got battery update, but state change was not relevant
D/RemoteNotifier( 7785): Battery status: Charging
D/RemoteNotifier( 7785): Got battery level: 54
D/RemoteNotifier( 7785): Got battery update, but state change was not relevant
D/WifiService(   92): ACTION_BATTERY_CHANGED pluggedType: 1
D/WifiService(   92): ACTION_SCREEN_OFF
I/RemoteNotifier( 7785): Starting notification service
D/RemoteNotifier( 7785): Battery status: Charging
D/RemoteNotifier( 7785): Got battery level: 54
D/RemoteNotifier( 7785): Got battery update, but state change was not relevant
D/RemoteNotifier( 7785): Battery status: Charging
D/RemoteNotifier( 7785): Got battery level: 55
D/RemoteNotifier( 7785): Got battery update, but state change was not relevant
D/WifiService(   92): ACTION_BATTERY_CHANGED pluggedType: 1
D/WifiService(   92): ACTION_SCREEN_ON
D/WifiService(   92): enable and start wifi due to updateWifiState
I/RemoteNotifier( 7785): Starting notification service
D/RemoteNotifier( 7785): Battery status: Charging
D/RemoteNotifier( 7785): Got battery level: 55
D/RemoteNotifier( 7785): Got battery update, but state change was not relevant
I/RemoteNotifier( 7785): Starting notification service
D/RemoteNotifier( 7785): Battery status: Charging
D/RemoteNotifier( 7785): Got battery level: 55
D/RemoteNotifier( 7785): Got battery update, but state change was not relevant
D/RemoteNotifier( 7785): Sending notification: 
v2/22a100001372c07e/43481730933a4/PING//Test notification
D/RemoteNotifier( 7785): Sending wifi notification to IP 255.255.255.255
I/RemoteNotifier( 7785): Sent notification over WiFi.
D/RemoteNotifier( 7785): Sending notification: 
v2/22a100001372c07e/4348173c99323/PING//Test notification
D/RemoteNotifier( 7785): Sending wifi notification to IP 255.255.255.255
I/RemoteNotifier( 7785): Sent notification over WiFi.
D/RemoteNotifier( 7785): Sending notification: 
v2/22a100001372c07e/434817445dd3f/PING//Test notification
D/RemoteNotifier( 7785): Sending wifi notification to IP 255.255.255.255
I/RemoteNotifier( 7785): Sent notification over WiFi.
D/RemoteNotifier( 7785): Battery status: Charging
D/RemoteNotifier( 7785): Got battery level: 56
D/RemoteNotifier( 7785): Got battery update, but state change was not relevant
D/WifiService(   92): ACTION_BATTERY_CHANGED pluggedType: 1
D/WifiService(   92): acquireWifiLockLocked: WifiLock{NetworkLocationProvider 
type=2 binder=android.os.Binder@45f60d98}
D/WifiService(   92): enable and start wifi due to updateWifiState
D/WifiService(   92): releaseWifiLockLocked: WifiLock{NetworkLocationProvider 
type=2 binder=android.os.Binder@45f60d98}
D/WifiService(   92): enable and start wifi due to updateWifiState
I/RemoteNotifier( 7785): Starting notification service
D/RemoteNotifier( 7785): Battery status: Charging
D/RemoteNotifier( 7785): Got battery level: 56
D/RemoteNotifier( 7785): Got battery update, but state change was not relevant
D/RemoteNotifier( 7785): Using level 5 caller ID
I/RemoteNotifier( 7785): Starting notification service
D/RemoteNotifier( 7785): Battery status: Charging
D/RemoteNotifier( 7785): Got battery level: 56
D/RemoteNotifier( 7785): Notifying of battery state change
D/RemoteNotifier( 7785): Sending notification: 
v2/22a100001372c07e/43481762218dc/PING//Test notification
D/WifiService(   92): acquireWifiLockLocked: WifiLock{NetworkLocationProvider 
type=2 binder=android.os.Binder@45f60d98}
D/WifiService(   92): enable and start wifi due to updateWifiState
D/WifiService(   92): releaseWifiLockLocked: WifiLock{NetworkLocationProvider 
type=2 binder=android.os.Binder@45f60d98}
D/WifiService(   92): enable and start wifi due to updateWifiState
D/WifiService(   92): acquireWifiLockLocked: WifiLock{NetworkLocationProvider 
type=2 binder=android.os.Binder@45f60d98}
D/WifiService(   92): enable and start wifi due to updateWifiState
D/WifiService(   92): releaseWifiLockLocked: WifiLock{NetworkLocationProvider 
type=2 binder=android.os.Binder@45f60d98}
D/WifiService(   92): enable and start wifi due to updateWifiState
D/RemoteNotifier( 7785): Sending notification: 
v2/22a100001372c07e/434817b3d59d9/PING//Test notification
D/RemoteNotifier( 7785): Sending wifi notification to IP 10.0.1.255
I/RemoteNotifier( 7785): Sent notification over WiFi.
D/RemoteNotifier( 7785): Using donut SMS decoder
D/RemoteNotifier( 7785): Using level 5 caller ID
D/RemoteNotifier( 7785): Received Sms: SMS from Allie Cohn - Mobile 
(8019169702): Okay!
D/RemoteNotifier( 7785): Sending notification: 
v2/22a100001372c07e/825bb09a4a910c/SMS/8019169702/SMS from Allie Cohn - Mobile 
(8019169702): Okay!
D/RemoteNotifier( 7785): Sending wifi notification to IP 10.0.1.255
I/RemoteNotifier( 7785): Sent notification over WiFi.
D/NotificationFlashLightUtility getIncomingCall( 7073): load fail~~~~~~~~~~
D/RemoteNotifier( 7785): Sending notification: 
v2/22a100001372c07e/434817c301bc4/PING//Test notification
D/RemoteNotifier( 7785): Sending wifi notification to IP 10.0.1.255
I/RemoteNotifier( 7785): Sent notification over WiFi.

What steps will reproduce the problem?
1. No idea I didn't change anything prelack of function
2.
3.

What is the expected output? What do you see instead?

Expect message to show up, don't see anything.

Please paste the application's log here (it should now be on your
clipboard):

See above, sorry!

What version of Android are you using?

2.2 HTC sense over

Original issue reported on code.google.com by ajh0...@gmail.com on 11 Sep 2010 at 8:24

GoogleCodeExporter commented 8 years ago 
Apparently the notification is being sent, but it could be the case that it's 
not being received.
Which client did you install on the desktop, the native mac client or the 
multiplatform client?
How's your network set up - are both the phone and the computer on the same 
network?
From the target address of 10.0.1.255 I'll assume you're using "DHCP broadcast" 
as the target. Does it work if you try with a custom IP target?

Original comment by rdamazio@gmail.com on 11 Sep 2010 at 4:26

GoogleCodeExporter commented 8 years ago

Original comment by rdamazio@gmail.com on 12 Sep 2010 at 6:38

GoogleCodeExporter commented 8 years ago 
I got the same problem on Fedora 13. It seems as the phone client will send it 
on port 10600 ("make sure your firewall allows connections on port 10600"), but 
the linux client listens on 10700 ("2010-09-28 14:50:55,865 DEBUG 
[ServiceServerImpl] - Starting service server on port [10700]")

This is stock setup.

Original comment by modinonl...@gmail.com on 15 Oct 2010 at 7:38

GoogleCodeExporter commented 8 years ago 
This ServiceServer is to stop the desktop app from the command-line when it's 
running without tray icon, the listener of notifications binds to port 10600. 
The multiplatform client does not support DHCP broadcast right now, if you're 
using it, please switch to custom IP or UDP broadcast.

Original comment by lehph...@gmail.com on 15 Oct 2010 at 1:12

GoogleCodeExporter commented 8 years ago 
Does the multiplatform client now properly support DHCP broadcast? It should.

Original comment by rdamazio@gmail.com on 31 Oct 2010 at 5:20

GoogleCodeExporter commented 8 years ago 
Taking over lehphyro's issues.

Original comment by rdamazio@gmail.com on 11 Jan 2011 at 4:31

GoogleCodeExporter commented 8 years ago 
Hi all,

Installed Multidroid notifier 0.5.1 (windows xp).  but is not showing pop-ups. 

Log show notification has been received :-
2011-02-16 21:10:38,632 INFO [NotificationManagerImpl] - Notification received: 
notificationId=38914667440929356, type=SMS
2011-02-16 21:11:19,791 INFO [NotificationManagerImpl] - Notification received: 
notificationId=1255313428778647, type=Ping

Original comment by markr...@gmail.com on 16 Feb 2011 at 9:27

GoogleCodeExporter commented 8 years ago 
Not receiving notifications on windows home laptop or ubuntu work desktop.  
uninstalled.

Original comment by ml...@nocturnal.org on 10 Mar 2011 at 1:50

GoogleCodeExporter commented 8 years ago 
I only receive SOME notifications on my PC, not all of them (e.g. text 
messages, battery state). Tried sending log from phone but crashes browser when 
I try to paste it in! :-(

Original comment by CiaraJan...@gmail.com on 30 May 2011 at 1:04

GoogleCodeExporter commented 8 years ago 
I'm having a similar issue where by when I open the app on my phone 
notifications are sent.  They continue to send for an hour or so, and then 
nothing else comes through until I open the app on the phone again.  On the 
phone I have it set to run at boot

Original comment by mattgpar...@gmail.com on 14 Jun 2011 at 5:03

GoogleCodeExporter commented 8 years ago 
@10 Is it likely that android is killing the application? Did you disable the 
icon from showing up in the notification area? I wonder if this is my problem..

Original comment by gordon.t...@gmail.com on 27 Jul 2011 at 8:34

GoogleCodeExporter commented 8 years ago 
No, the icon is still showing in the notification area and test pings work, yet 
the application still stops sending notifications of text messages to the 
computer after a while. Very annoying as this could be a great app if this 
problem was fixed! :-(

Original comment by CiaraJan...@gmail.com on 31 Jul 2011 at 8:58

GoogleCodeExporter commented 8 years ago 
Great great program but I'm experiencing the same i.e. Remote Notifier displays 
as running in the notification area but, after *guessing* 1 hour, it stops 
sending notifications until I open the app on the phone - at which point it 
starts sending them again.

FWIW, I'm running 0.2.8 it on a Samsung Galaxy S II (2.3.3). Notifications are 
set to go to custom IP address, wifi to never sleep, using tcp + udp and to 
send over cell network.

I've fiddled a bit in Tasker to create a task which disables and then enables 
the Remote Notifier service. This task then gets executed every hour. This 
appears to work in most cases but Remote Notifier does FC maybe 25% of the 
time. I've even tried adding in a pause between the disable and enable commands 
but that doesn't appear to make much difference.

It's a great program BTW. I use Growl a lot and this + Tasker lets me control a 
lot of home network duties with ease :)

Original comment by nel...@gmail.com on 5 Aug 2011 at 12:05

GoogleCodeExporter commented 8 years ago 
I got the same problem as the above.(stops working after an hour or so).
Running CM 7.1 on Desire HD.

Original comment by tomm...@gmail.com on 29 Aug 2011 at 2:36

GoogleCodeExporter commented 8 years ago 
Me too. I'm using Android 2.3.3 on a Nexus One, with version 0.2.8 on the phone 
and 0.5.1 on desktop (Windows 7).

Original comment by d...@natts.com on 18 Sep 2011 at 4:18

GoogleCodeExporter commented 8 years ago 
Same issue. It appears in the running programs list, but after a while it stops 
sending notifications. If I launch the application I instantly get a battery 
notification and it begins working again for a while.

Original comment by jedid...@gmail.com on 17 Dec 2011 at 6:55

GoogleCodeExporter commented 8 years ago 
Droid X2 and Windows 7 64 bit using bluetooth connection. The log shows that I 
am receiving the notifications, and in fact I notice that the android notifier 
icon becomes present in the status bar, as if there would be a pop up coming 
from it, but not message appears. I've replicated this for pings and text 
messages. It doesn't appear to be an issue closing of android notifier on the 
phone because the ping doesn't work either. 

I see it's been awhile for this thread, any new updates?

Original comment by ajcy...@gmail.com on 6 Dec 2012 at 7:07

GoogleCodeExporter commented 8 years ago 
Please do make this issue a priority as this app is a great concept but needs 
to be reliable.

Original comment by starman617@gmail.com on 26 May 2013 at 12:41