Hi!

I installed mobilepcmonitor on my galaxy nexus and then on my pc. I set up the account on my pc and then used the same on my phone.

When I start the app on my phone it says "Socket is closed" almost immediately.

Do you know what the problem may be?

Hello,

Can you access https://wsn.pulseway.com/ from phone's browser ?

I have the same problem here. Using a HTC Sensation running Android 4.0.3. Through wifi everything works great, but on 3G I also get the message "Socket is closed". I have been using mobile pc monitor for a while and it always worked fine. Recently I updated my ROM from Android 3.xx? to 4. Is it possible that it has to do with this?

We managed to reproduce this error on some 4.0.X ROMs. (especially 4.0.4) - not quite sure what is causing this issue, it's only happening on some carriers. We'll keep you updated.

Hello,

Upon further investigations it seems to be a problem in Android 4. We've raised an issue for this at: http://code.google.com/p/android/issues/detail?id=29509&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars .

If you encounter this problem please star the android issue.

Hi,

I have the same problem with my Galaxy SII with 4.0.4. Only I have the problem by 3G with WiFi connection works fine.

We released a new update in Google Play store today that fixes this issue (version 3.1 build 120615)

We released a new update in Google Play store today that fixes this issue (version 3.1 build 120615)

Hi. I am having this exact issue.

Samsung Galaxy Tab2 10.1 with Android 4.0.4.

PC monitor 3.1.3 build 121001

Hi. I am having this exact issue.

Samsung Galaxy Tab2 10.1 with Android 4.0.4.

PC monitor 3.1.3 build 121001

What is the exact error message?

I can confirm the same issue for a Samsung S3 LTE (GT-I9305) running version 3.3 (build 121119) of PC Monitor. OS version is 4.1.1.

 

In my case I am getting the "Socket is closed" error message when I am on WiFi (same result on various WiFi networks). I do not see the issue when I am connecting via mobile network. Restarting the app or the phone does not help.

 

Regards

Michael

We have released an update (3.3.1) in Google Play that fixes this issue.

Yep, I can confirm that the new version fixed the problem on my S3. I'm highly impressed by that speed of support - Thanks!

 

Cheers

Michael