search

kailIII / android-notifier

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

Can not load UI - Wrong version of Java? #297

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I am trying to load the software and I'm getting a message that the UI can not 
be loaded. It says if I want to run 64x that the OS and Java must be both 64x. 
My OS is 64x and I downloaded and ran the recommended Java version and 
validated it. 

Currently running 1.6.0_16. 

Can you please assist?

Original issue reported on code.google.com by rugger...@gmail.com on 25 Nov 2010 at 12:01

GoogleCodeExporter commented 9 years ago 
Related to issue 212.

Original comment by rugger...@gmail.com on 25 Nov 2010 at 12:06

GoogleCodeExporter commented 9 years ago 
I am getting this issue too. I opened a new defect (297) but then I located 
this one in a search. Currently running Windows 7 64x and Java 1.6.0_16. I am 
pretty sure I'm using 32x Java however which shouldn't matter (only if I was on 
a 32x machine trying to use 64x Java... correct?).

What I've done so far...

1. Removed all version of Java
2. Downloaded and reinstalled latest Java VM from Sun.
3. Removed Notifier software using Revo, cleaned registry and removed directory 
left-overs.
4. Installed MultiDroidNotifier-0.5.1-x86 into a fresh directory.

Still received error message.

Original comment by rugger...@gmail.com on 25 Nov 2010 at 12:11

GoogleCodeExporter commented 9 years ago 
Java 32-bit can run on both 32 and 64-bit operating systems but Java 64-bit can 
only run on 64-bit OSes. The desktop app architecture must match Java 
architecture.

You probably installed Java 64-bit, try MultiDroidNotifier-0.5.1-x86_64.exe.

Original comment by lehph...@gmail.com on 25 Nov 2010 at 2:30

GoogleCodeExporter commented 9 years ago 
Ok, I have both 32 and 64 bit Java running on the machine but it seems the file 
you mentioned works (although I don't see an icon in the tray or anything). 
However I am not getting notified even after I opened up port 10600 through my 
firewall.

Thoughts?

Original comment by rugger...@gmail.com on 27 Nov 2010 at 1:12

GoogleCodeExporter commented 9 years ago 
D/RemoteNotifier(13860): Battery status: Charging
D/RemoteNotifier(13860): Got battery level: 63
D/RemoteNotifier(13860): Battery level change: 1
D/RemoteNotifier(13860): Got battery update, but state change was not relevant
D/RemoteNotifier(13860): Battery status: Charging
D/RemoteNotifier(13860): Got battery level: 64
D/RemoteNotifier(13860): Battery level change: 2
D/RemoteNotifier(13860): Got battery update, but state change was not relevant
D/RemoteNotifier(13860): Battery status: Charging
D/RemoteNotifier(13860): Got battery level: 65
D/RemoteNotifier(13860): Battery level change: 3
D/RemoteNotifier(13860): Got battery update, but state change was not relevant
D/RemoteNotifier(13860): Battery status: Charging
D/RemoteNotifier(13860): Got battery level: 66
D/RemoteNotifier(13860): Battery level change: 4
D/RemoteNotifier(13860): Got battery update, but state change was not relevant
D/RemoteNotifier(13860): Battery status: Discharging
D/RemoteNotifier(13860): Got battery level: 66
D/RemoteNotifier(13860): Battery level change: 4
D/RemoteNotifier(13860): Notifying of battery state change
D/RemoteNotifier(13860): Sending notification: 
v2/6523a32f360df3fc/8de94d07d62f09/BATTERY/66/Discharging, remaining charge: 66%
D/InCallScreen(  200): onStop()...
D/InCallScreen(  200): onStop: state = IDLE
D/RemoteNotifier(13860): Not notifying over IP/wifi - not connected.
I/AndroidRuntime(14577): AndroidRuntime onExit calling exit(0)
E/BluetoothService.cpp(  120): stopDiscoveryNative: D-Bus error in 
StopDiscovery: org.bluez.Error.Failed (Invalid discovery session)
D/RemoteNotifier(13860): Not starting service again
D/WifiService(  120): ACTION_BATTERY_CHANGED pluggedType: 0
D/WifiService(  120): acquireWifiLockLocked: WifiLock{NetworkLocationProvider 
type=2 binder=android.os.Binder@44126680}
V/WifiStateTracker(  120): Connection to supplicant established, 
state=DISCONNECTED
V/WifiMonitor(  120): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2 
BSSID=00:00:00:00:00:00]
V/WifiStateTracker(  120): Changing supplicant state: DISCONNECTED ==> SCANNING
V/WifiMonitor(  120): Event [WPS-AP-AVAILABLE ]
V/WifiMonitor(  120): Event [Trying to associate with 00:1b:5b:df:0b:39 
(SSID='HG Squared' freq=2442 MHz)]
V/WifiMonitor(  120): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=3 
BSSID=00:1b:5b:df:0b:39]
V/WifiStateTracker(  120): Changing supplicant state: SCANNING ==> ASSOCIATING
V/WifiMonitor(  120): Event [CTRL-EVENT-STATE-CHANGE id=0 state=4 
BSSID=00:1b:5b:df:0b:39]
V/WifiStateTracker(  120): Changing supplicant state: ASSOCIATING ==> ASSOCIATED
V/WifiMonitor(  120): Event [Associated with 00:1b:5b:df:0b:39]
V/WifiMonitor(  120): Event [CTRL-EVENT-STATE-CHANGE id=0 state=5 
BSSID=00:00:00:00:00:00]
V/WifiStateTracker(  120): Changing supplicant state: ASSOCIATED ==> 
FOUR_WAY_HANDSHAKE
V/WifiMonitor(  120): Event [CTRL-EVENT-STATE-CHANGE id=0 state=5 
BSSID=00:00:00:00:00:00]
V/WifiStateTracker(  120): Changing supplicant state: FOUR_WAY_HANDSHAKE ==> 
FOUR_WAY_HANDSHAKE
V/WifiMonitor(  120): Event [CTRL-EVENT-STATE-CHANGE id=0 state=6 
BSSID=00:00:00:00:00:00]
V/WifiStateTracker(  120): Changing supplicant state: FOUR_WAY_HANDSHAKE ==> 
GROUP_HANDSHAKE
V/WifiMonitor(  120): Event [CTRL-EVENT-STATE-CHANGE id=0 state=6 
BSSID=00:00:00:00:00:00]
V/WifiStateTracker(  120): Changing supplicant state: GROUP_HANDSHAKE ==> 
GROUP_HANDSHAKE
V/WifiMonitor(  120): Event [WPA: Key negotiation completed with 
00:1b:5b:df:0b:39 [PTK=TKIP GTK=TKIP]]
V/WifiMonitor(  120): Event [CTRL-EVENT-STATE-CHANGE id=0 state=7 
BSSID=00:00:00:00:00:00]
V/WifiStateTracker(  120): Changing supplicant state: GROUP_HANDSHAKE ==> 
COMPLETED
V/WifiMonitor(  120): Event [CTRL-EVENT-CONNECTED - Connection to 
00:1b:5b:df:0b:39 completed (auth) [id=0 id_str=]]
V/WifiStateTracker(  120): New network state is CONNECTED
D/WifiStateTracker(  120): DhcpHandler: DHCP request started
V/WifiStateTracker(  120): DhcpHandler: DHCP request succeeded
V/WifiStateTracker(  120): IP configuration: ipaddr 192.168.1.74 gateway 
192.168.1.254 netmask 255.255.255.0 dns1 192.168.1.254 dns2 0.0.0.0 DHCP server 
192.168.1.254 lease 86400 seconds
D/WifiWatchdogService(  120): (android.server.ServerThread) HG Squared 
(00:1b:5b:df:0b:39) does not require the watchdog
D/WifiService(  120): releaseWifiLockLocked: WifiLock{NetworkLocationProvider 
type=2 binder=android.os.Binder@44126680}
E/BluetoothService.cpp(  120): stopDiscoveryNative: D-Bus error in 
StopDiscovery: org.bluez.Error.Failed (Invalid discovery session)
D/RemoteNotifier(13860): Not starting service again
D/RemoteNotifier(13860): Sending notification: 
v2/6523a32f360df3fc/493e714a1fa7a/PING//Test notification
D/RemoteNotifier(13860): Sending wifi notification to IP 255.255.255.255
D/RemoteNotifier(13860): Sending over UDP
D/RemoteNotifier(13860): Sent over UDP
I/RemoteNotifier(13860): Sent notification over WiFi.
D/RemoteNotifier(13860): Battery status: Discharging
D/RemoteNotifier(13860): Got battery level: 65
D/RemoteNotifier(13860): Battery level change: 1
D/RemoteNotifier(13860): Got battery update, but state change was not relevant
D/WifiService(  120): ACTION_BATTERY_CHANGED pluggedType: 0
D/RemoteNotifier(13860): Sending notification: 
v2/6523a32f360df3fc/493e718e1b3bc/PING//Test notification
D/RemoteNotifier(13860): Sending wifi notification to IP 255.255.255.255
D/RemoteNotifier(13860): Sending over UDP
D/RemoteNotifier(13860): Sent over UDP
I/RemoteNotifier(13860): Sent notification over WiFi.
D/RemoteNotifier(13860): Sending notification: 
v2/6523a32f360df3fc/493e71a292bf8/PING//Test notification
D/RemoteNotifier(13860): Sending wifi notification to IP 255.255.255.255
D/RemoteNotifier(13860): Sending over UDP
D/RemoteNotifier(13860): Sent over UDP
I/RemoteNotifier(13860): Sent notification over WiFi.

Original comment by rugger...@gmail.com on 27 Nov 2010 at 1:23

GoogleCodeExporter commented 9 years ago 
OK to close.

Original comment by rugger...@gmail.com on 27 Nov 2010 at 1:41

GoogleCodeExporter commented 9 years ago

Original comment by lehph...@gmail.com on 27 Nov 2010 at 12:51

GoogleCodeExporter commented 9 years ago 
Installed on 01/04/2012 with current Java being 6.30   Program is asking for 
Java 1.6.  What is the fix for this?

Original comment by cac380...@gmail.com on 4 Jan 2012 at 6:45

GoogleCodeExporter commented 9 years ago 
Hi I had similar issue.

The log file (C:\Users\%USER_NAME%\.android\android-notifier-desktop)

2013-10-24 16:44:28,699 ERROR [ApplicationImpl] - Error starting SWT
java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons: 
    no swt-win32-3703 in java.library.path
    no swt-win32 in java.library.path
    D:\Temp\swtlib-32\swt-win32-3703.dll: Access is denied
    Can't load library: D:\Temp\swtlib-32\swt-win32.dll

The solution:

1. Find swtlib-32 folder with swt-gdip-win32-3703.dll & swt-win32-3703.dll 
files (it should be stored in you temp folder)
2. Change permissions for these files or file or remove the folder 

Now it's runs OK.

Original comment by l...@kitsis.ca on 24 Oct 2013 at 8:52

Attachments: