Problem with automatic connection on new computer

Anmeldedatum: 25.02.2010 Beiträge: 23

Hello,
I was using MPE on old laptop with Windows 7 where automatic connection worked more or less reliably trying all channels in particular order USB>WiFi>BT. Now on Windows 8.1 it seems to skip WiFi check completely (despite that MPE client is running in phone connected to same network via WiFi - I can connect MPE to phone if I force WiFi connection type). This says logfile:

Code:

21:24:25.88 RunADBCommand: start-server
21:24:26.22 ADB CommandResponse:
21:24:26.22 RunADBCommand: devices
21:24:26.39 ADB CommandResponse:
21:24:26.39 RunADBCommand: forward tcp:5210 tcp:5210
21:24:26.57 ADB CommandResponse:
21:24:26.57 Try connecting to 127.0.0.1...
21:24:27.08 RunADBCommand: shell am start -n com.fjsoft.myphoneexplorer.client/.MainActivity --ez adb true
21:24:27.33 ADB CommandResponse:
21:24:27.33 Try launch USB connection
21:24:27.94 Try launch USB connection
21:24:28.53 Try launch USB connection
21:24:29.14 Try launch USB connection
21:24:29.73 Try launch USB connection
21:24:30.33 Try launch USB connection
21:24:30.94 Try launch USB connection
21:24:31.54 Avaiable Ports: COM3=\Device\BthModem0; COM4=\Device\BthModem1;
21:24:31.54 Neue COM-Bibliothek wird verwendet
21:24:31.54 SPort Properties set, opening COM3
21:24:36.76 After OpenPort
21:24:36.76 Nelze otevřít COM3!
21:24:36.78 Connect to Android failed!
21:24:36.78 bOpened=False
21:24:36.78 Bluetooth: Nelze otevřít COM3!
21:24:36.78 Refresh ComDescriptions...
21:24:36.78 PORT: COM4 Enumerator=BTHENUM Displayed=Standardní sériová linka pomocí protokolu Bluetooth InstanceID=BTHENUM\{00001101-0000-1000-8000-00805F9B34FB}_LOCALMFG&0000\8&184B5469&0&000000000000_00000002
21:24:36.78 PORT: COM3 Enumerator=BTHENUM Displayed='Xperia P' Bluetooth-Port InstanceID=BTHENUM\{00001101-0000-1000-8000-00805F9B34FB}_VID&00020FCE_PID&0172\8&184B5469&0&D05162988472_C00000000
21:24:36.79 ErrMsg: Spojení s telefonem se nepodařilo navázat:
Bluetooth: Nelze otevřít COM3!
21:24:41.04 Refresh ComDescriptions...
21:24:41.04 PORT: COM4 Enumerator=BTHENUM Displayed=Standardní sériová linka pomocí protokolu Bluetooth InstanceID=BTHENUM\{00001101-0000-1000-8000-00805F9B34FB}_LOCALMFG&0000\8&184B5469&0&000000000000_00000002
21:24:41.04 PORT: COM3 Enumerator=BTHENUM Displayed='Xperia P' Bluetooth-Port InstanceID=BTHENUM\{00001101-0000-1000-8000-00805F9B34FB}_VID&00020FCE_PID&0172\8&184B5469&0&D05162988472_C00000000

From it is it clear that WiFi is not even tried, why?

Verfasst am: Do Jan 16, 2014 00:46

Please post the complete logfile (and restart your WiFi Router)

Anmeldedatum: 25.02.2010 Beiträge: 23

Restart hotspot doesnot help, this problem persists since I'm on new computer. Complete logfile contains alots personal data (SMS, phone numbers etc.). This not too wise post here. What part exactly U need?

This record for MPE connect in force WiFi mode:

Code:

18:08:26.34 Broadcaster started
18:08:26.34 Sending broadcast
18:08:26.84 Sending broadcast
18:08:27.34 Sending broadcast
18:08:28.34 Try connecting to 192.168.137.99 (cached WifiIP)...
18:08:28.44 Connect to Android OK
18:08:28.44 Settimeout: RT=2000 WT=500
18:08:28.44 bOpened=True
18:08:28.45 [TX]: AT+CGSN
18:08:28.52 [RX]: AT+CGSN
18:08:28.52 [RX]: 3*************4
18:08:28.52 [RX]: OK
18:08:28.53 Settimeout: RT=15000 WT=1000
18:08:28.53 [TX]: AT*PIN=ec1deffb08dc36f93aa994c6041d10e1
18:08:28.54 [RX]: AT*PIN=ec1deffb08dc36f93aa994c6041d10e1
18:08:28.54 [RX]: *PIN: ACCESS OK,10
18:08:28.54 [RX]: OK
18:08:28.54 [TX]: ATI
18:08:28.55 [RX]: ATI
18:08:28.55 [RX]: Sony LT22i
18:08:28.55 [RX]: OK
18:08:28.55 [TX]: AT*APPVERSION=1.8.5
18:08:28.56 [RX]: AT*APPVERSION=1.8.5
18:08:28.56 [RX]: 15,1.0.28
18:08:28.56 [RX]: OK
18:08:28.56 [TX]: AT+CSCS="UTF-8"
18:08:28.56 [RX]: AT+CSCS="UTF-8"
18:08:28.56 [RX]: OK
18:08:28.57 [TX]: AT+CNMI=2,1,0,1
18:08:28.57 [RX]: AT+CNMI=2,1,0,1
18:08:28.57 [RX]: ERROR
18:08:28.58 [TX]: AT*ECAM=1
18:08:28.58 [RX]: AT*ECAM=1
18:08:28.58 [RX]: OK
18:08:28.58 [TX]: AT+CIND=?
18:08:28.59 [RX]: AT+CIND=?
18:08:28.59 [RX]: ERROR
18:08:28.59 [TX]: AT+CBC
18:08:28.59 [RX]: AT+CBC
18:08:28.59 [RX]: +CBC: 0,98
18:08:28.60 [RX]: OK
18:08:28.61 [TX]: AT+CSQ
18:08:28.61 [RX]: AT+CSQ
18:08:28.61 [RX]: +CSQ: 22,99
18:08:28.62 [RX]: OK
18:08:28.62 Alle Verbindungsaktionen beendet
18:08:34.54 Refresh ComDescriptions...
18:08:34.54 PORT: COM3 Enumerator=BTHENUM Displayed='Xperia P' Bluetooth-Port InstanceID=BTHENUM\{00001101-0000-1000-8000-00805F9B34FB}_VID&00020FCE_PID&0172\8&2A7BD2CF&0&D05162988472_C00000000
18:08:34.54 PORT: COM4 Enumerator=BTHENUM Displayed=Standardní sériová linka pomocí protokolu Bluetooth InstanceID=BTHENUM\{00001101-0000-1000-8000-00805F9B34FB}_LOCALMFG&0000\8&2A7BD2CF&0&000000000000_00000002
18:08:37.79 OK pressed in settingswindow
18:08:37.81 Set first swap of settings
18:08:37.81 Apply new holidays
18:08:37.81 DoItemUpdate
18:08:37.83 DoItemUpdate fertig
18:08:37.84 Holidays applied
18:08:37.84 Second swap of settings set
18:08:37.84 Everything is done
18:08:38.67 Settimeout: RT=3500 WT=800
18:08:38.67 [TX]: AT+CBC
18:08:38.69 [RX]: AT+CBC
18:08:38.69 [RX]: +CBC: 0,98
18:08:38.69 [RX]: OK
18:08:38.70 [TX]: AT+CSQ
18:08:38.70 [RX]: AT+CSQ
18:08:38.70 [RX]: +CSQ: 22,99
18:08:38.71 [RX]: OK
18:08:39.25 Androidsocket wird geschlossen 7
18:08:39.25 Port wurde geschlossen
18:08:39.25 Closing Broadcaster

This record for MPE connect in auto detect mode:

Code:

18:08:47.67 RunADBCommand: start-server
18:08:47.83 ADB CommandResponse:
18:08:47.83 RunADBCommand: devices
18:08:47.99 ADB CommandResponse:
18:08:47.99 RunADBCommand: forward tcp:5210 tcp:5210
18:08:48.16 ADB CommandResponse:
18:08:48.16 Try connecting to 127.0.0.1...
18:08:48.68 RunADBCommand: shell am start -n com.fjsoft.myphoneexplorer.client/.MainActivity --ez adb true
18:08:48.86 ADB CommandResponse:
18:08:48.86 Try launch USB connection
18:08:49.46 Try launch USB connection
18:08:50.05 Try launch USB connection
18:08:50.66 Try launch USB connection
18:08:51.26 Try launch USB connection
18:08:51.85 Try launch USB connection
18:08:52.46 Try launch USB connection
18:08:53.06 Avaiable Ports: COM3=\Device\BthModem0; COM4=\Device\BthModem1;
18:08:53.06 Neue COM-Bibliothek wird verwendet
18:08:53.06 SPort Properties set, opening COM3
18:08:58.29 After OpenPort
18:08:58.29 Nelze otevřít COM3!
18:08:58.29 Connect to Android failed!
18:08:58.29 bOpened=False
18:08:58.29 Bluetooth: Nelze otevřít COM3!
18:08:58.29 Refresh ComDescriptions...
18:08:58.29 PORT: COM3 Enumerator=BTHENUM Displayed='Xperia P' Bluetooth-Port InstanceID=BTHENUM\{00001101-0000-1000-8000-00805F9B34FB}_VID&00020FCE_PID&0172\8&2A7BD2CF&0&D05162988472_C00000000
18:08:58.29 PORT: COM4 Enumerator=BTHENUM Displayed=Standardní sériová linka pomocí protokolu Bluetooth InstanceID=BTHENUM\{00001101-0000-1000-8000-00805F9B34FB}_LOCALMFG&0000\8&2A7BD2CF&0&000000000000_00000002
18:08:58.29 ErrMsg: Spojení s telefonem se nepodařilo navázat:
Bluetooth: Nelze otevřít COM3!
18:09:02.34 Refresh ComDescriptions...
18:09:02.34 PORT: COM3 Enumerator=BTHENUM Displayed='Xperia P' Bluetooth-Port InstanceID=BTHENUM\{00001101-0000-1000-8000-00805F9B34FB}_VID&00020FCE_PID&0172\8&2A7BD2CF&0&D05162988472_C00000000
18:09:02.34 PORT: COM4 Enumerator=BTHENUM Displayed=Standardní sériová linka pomocí protokolu Bluetooth InstanceID=BTHENUM\{00001101-0000-1000-8000-00805F9B34FB}_LOCALMFG&0000\8&2A7BD2CF&0&000000000000_00000002

Verfasst am: So Jan 19, 2014 17:34

Zitat:

18:08:26.34 Broadcaster started
18:08:26.34 Sending broadcast
18:08:26.84 Sending broadcast
18:08:27.34 Sending broadcast

It seems the Broadcasts are not answered from the phone. Ensure that MyPhoneExplorer has all freedom in your firewall.

The second Log looks like you did not confirm the security prompt on your phone which is shown on the first try to connect, but i am not sure cause the logfile started too late.

If you are afraid of personal data (what i fully understand) then send the file to me via email with a link to this thread.

Anmeldedatum: 25.02.2010 Beiträge: 23

FJ hat Folgendes geschrieben:

Ensure that MyPhoneExplorer has all freedom in your firewall.

The second Log looks like you did not confirm the security prompt on your phone which is shown on the first try to connect, but i am not sure cause the logfile started too late.

Unfortunatelly it's not the firewall blocking WiFi discovery (remember that in forced WiFi mode MPE connects adequately). Disabling firewall doesnot change anything.

What do you mean by security prompt on my phone?
Neither in forced WiFi mode nor auto detect mode phone doesnot prompt for anything. WiFi PIN is set in MPE client but I can't find it in MPE server. Where's it set?

Anmeldedatum: 25.02.2010 Beiträge: 23

There must be some bug in your program. I have configured to auto-connect and automultiple synchro at startup.
On start in auto mode MPE tries USB then COM3 (BT), then shows bubble about failed connection and nothing happens. Then I open settings (F2) and click on Show Log button. After while phone connects and multisync starts, finishes successfully. But if I won't do this, phone won't connect. Something weird. I'm sending you the log from MPE start up to failed connection bubble (without opening settings)

Edit: actually the program connects even without opening settings but about one minute after it gives error message that no device is detected. If selected force WiFi mode it however connects instantly after start and autosync finishes successfully. On old machine (Win7), this worked flawlessly even in auto-detect mode, why? Anyway this is kinda inconvenient.

Anmeldedatum: 25.02.2010 Beiträge: 23

There's more nonfunctionality I see: When connected via USB in auto-detect mode, MPE now doesnot recognize incomming SMSs and calls (must manually download data from phone). I think this relates to my previously reported problem.

Verfasst am: So Feb 23, 2014 22:50

We should reduce the problem to USB or Bluetooth or WiFi - otherwise we will get confused. I got your logfile. The phone was not attached to the USB-Cable, did you want to connect via Bluetooth ? If yes then make a new Bluetooth-Pairing, this helps maybe.

Anmeldedatum: 25.02.2010 Beiträge: 23

The phone detection problem doesnot concern BT meda, phone receginzed perfectly using BT. There's only some weird problem using WiFi. Plus not detecting incoming SMS using any connection mode (including USB and BT). It behaves weird. I today added a new profile for old dumb SE phone using BT. And new profile inherited contact groups from my Android phone. Then Again when I switched to Android profile contact groups were noy changed from old phone. All this didnot happen on old computer. Switching to different phone profile updated the contacts and groups according new profile.

The profile for Android phone I transfered from old compute (ie. copied phone name folder from "C:\Users\Anakunda\AppData\Roaming\MyPhoneExplorer\"

Site Admin Anmeldedatum: 15.02.2006 Beiträge: 32092 Wohnort: Tirol

The missing incoming sms popup could be caused from SMS replacements like Handcent or GoSMS. The consume the System notification of incoming messages, you can control this behaviour f.e. in the settings of GoSMS

Profile switching: There is a known issue when you switch from non-Android to Android profile. It should be fixed in the current beta: http://www.fjsoft.at/files/MyPhoneExplorer_DebugUpdate.exe

Anmeldedatum: 25.02.2010 Beiträge: 23

Thanks for the beta but it probably doesn't address the WiFi autodetection problem. Do U need more logs?

Site Admin Anmeldedatum: 15.02.2006 Beiträge: 32092 Wohnort: Tirol

As i wrote already: The LAN broadcasts of MyPhoneExplorer are not answered from the phone, this is also the reason why MPE is not able to detect automatically if the phone is in range. Did you already restart your WiFi Router ? Try this

Informationen zum Datenschutz auf dieser Website