FJ Software Foren-Übersicht  
 Homepage   •  Suchen   •  FAQ   •  Mitgliederliste   •  Registrieren   •  Login
 Samsung Galaxy S3 Phone book crash:Phone BUG Nächstes Thema anzeigen
Vorheriges Thema anzeigen
Neues Thema eröffnenNeue Antwort erstellen
Autor Nachricht
Unicornz0



Anmeldedatum: 10.02.2013
Beiträge: 12

BeitragVerfasst am: So Feb 10, 2013 21:51 Antworten mit ZitatNach oben

Hello,

Recently, (about 2 weeks ago when AT&T replaced my Samsung Galaxy S3 with a new Samsung Galaxy S3.
) MPE has started to crash on the PC side (host?).
Client v1.0.23
I've reinstalled client from Google Play.

I've updated to the newest version of MPE, 1.8.4, & installed on the PC.
After installation a prompt asks to run MPE. When I click finish, the installer populates again to the screen.
MPE crashed upon installation when it tried to sync phone book contacts from the Galaxy S3, via WIFI to the MPE Host
Restarted MPE, & it worked fine until I tried to download my contacts from phone to the MPE on the PC.
Now MPE crashes each time I launch it.
I once got a run time error 429, active x can't create object & an automation error.
I have a screen shot of the error message FYI, & will post or send it.

Now when I start MPE it immediately crashes & closes.

Windows XP SP3 is my OS.
Please provide a work around until this issue is resolved.
Thanks.

Edit 02.12.2013:
My Outlook Contacts have been corrupted, & all but 3 entries deleted.
This likely happened when MPE tried to sync contacts & crashed.

I also have Android 4.1.1 & MPE crashes when it tries to sync contacts from the phone, similar to another members (groncall) experience.

I too have uninstalled the antivirus & disabled the firewall & the MPE still crashes when syncing contacts with the phone. Samsung Galaxy S3.

It seems the MPE host on the PC crashes each time I restart MPE. when it loads the contacts it has downloaded from the phone.

This is a great program, & I have made a donation.
Please reply.

Edit 02.13.2013:
It appears MPE is not fully compatible with Android 4.1.1.
When I synced with my Samsung Galaxy Skyrocket Android 4.0.4.
MPE did not crash.

Please fix MyPhone Explorer so it will work with Android 4.1.1 .

Edit 02.13.2013:
Tried connecting by USB, & having the same crash issues as listed above.

Edit 02.13.2013:
When uninstalling MPE & I select the option to leave (MPE) personal information on the PC, MPE continues to crash when MPE is re-installed.
Please provide a fix.

Edit 02.13.2013:
I started having connectivity problems about 2 weeks ago when AT&T replaced my Samsung Galaxy S3 with a new Samsung Galaxy S3.
I've also tried MPE on another PC & this phone, & am having the same issues.

Edit 02.14.2013:
I tried syncing by Bluetooh, conecting once, contacts erased from phone, then when I tried to sync again got the following error message:
obex eror code: DO internal server error

Every time I try to sync now, WIFI or BT, get the
obex eror code: DO internal server error.

Edit 02.15.2013:
myDesktop Companion seems to be the only app that can access & sync the calendar. Even myDesktop Companion can only access & sync contact by USB. Even Samsung Kies can't access the calendar.

Edit 02.15.2013:
Cleared all calendar entries under Application Manager settings.
Now Contacts & Calendar sync with MPE works fine!!!
Outlook Notes will not sync.


Zuletzt bearbeitet von Unicornz0 am Fr Feb 22, 2013 17:10, insgesamt 12-mal bearbeitet
Benutzer-Profile anzeigenPrivate Nachricht senden
Unicornz0



Anmeldedatum: 10.02.2013
Beiträge: 12

BeitragVerfasst am: Do Feb 14, 2013 04:28 Antworten mit ZitatNach oben

Here is one of tbe error messages:
[/img]http://www.flickr.com/photos/27544233@N03/8472678448/in/photostream[img][/img]
Benutzer-Profile anzeigenPrivate Nachricht senden
Unicornz0



Anmeldedatum: 10.02.2013
Beiträge: 12

BeitragVerfasst am: Do Feb 14, 2013 04:58 Antworten mit ZitatNach oben

Here's links to screen shots of the error messages.
I hope they help provide a fix:

http://www.flickr.com/photos/27544233@N03/8472727106/in/photostream

http://www.flickr.com/photos/27544233@N03/8472678448/in/photostream
Benutzer-Profile anzeigenPrivate Nachricht senden
FJ
Site Admin


Anmeldedatum: 15.02.2006
Beiträge: 31906
Wohnort: Tirol

BeitragVerfasst am: Do Feb 21, 2013 23:43 Antworten mit ZitatNach oben

MyPhoneExplorer itself is very stable, its seldom that a user gets so many issues while installing. I assume the most issues were based on a failed installation - if you still get crashes then please post the logfile directly after crash: Start-Run-%appdata%\MyPhoneExplorer\Debug.txt

_________________
Ich bitte um Verständnis daß ich aufgrund des hohen Aufkommens im Forum und meines zeitlichen Rahmens nichtmehr jeden Thread im Forum persönlich lesen bzw. beantworten kann.

Bitte benutzt auch die Forum-Suche bzw. die FAQ
Benutzer-Profile anzeigenPrivate Nachricht sendenE-Mail sendenICQ-Nummer
Unicornz0



Anmeldedatum: 10.02.2013
Beiträge: 12

BeitragVerfasst am: Fr Feb 22, 2013 17:05 Antworten mit ZitatNach oben

Thanks FJ,

The problem turned out to be with The Samsung Galaxy S3.
Once all of the contacts were cleared (removed) using the Application Manager,
MPE, was able to run successfully.

Thanks Again for this great software!!!
Benutzer-Profile anzeigenPrivate Nachricht senden
Unicornz0



Anmeldedatum: 10.02.2013
Beiträge: 12

BeitragVerfasst am: Di Feb 26, 2013 07:30 Antworten mit ZitatNach oben

Now I have a new Galaxy S3 that was connecting to MPE & now can't be indentified by MPE when connected by wifi or USB.

Removing all downloaded apps, but that doesn't help at all.
Restored to factory settings, still MPE can't identify the phone.
Please help.
Thanks In Advance.

Below is the log:

Logdatei MyPhoneExplorer
************************
Programmversion: 1.8.2
Datum: 2/25/2013

23:55:23.68 Setting Port: 999
23:55:23.68 Setting Baud: 115200
23:55:23.68 Avaiable Ports: COM1=\Device\Serial0; COM3=\Device\PTSerial0;
23:55:23.68 Main Load frmSplash
23:55:23.68 Load frmSplash...
23:55:23.70 Show splash...
23:55:23.71 frmSplash geladen
23:55:24.21 Hauptfenster wird geladen
23:55:24.35 Sidebar fertig geladen
23:55:24.38 UC SMS wird geladen
23:55:24.48 UC Phonebook wird geladen
23:55:24.53 UC Phonebook fertig geladen
23:55:24.53 UC Calls wird geladen
23:55:24.57 UC Organizer wird geladen
23:55:24.68 Organizer initiated
23:55:24.73 Startpage=1
23:55:24.73 UC Filebrowser wird geladen
23:55:24.82 UC Filebrowser fertig geladen
23:55:24.82 UC AppBrowser wird geladen
23:55:24.84 UC Notes wird geladen
23:55:24.85 UC Calls wird geladen
23:55:24.92 Setting Lastuser:
23:55:24.93 Lade Userdatenbank:
23:55:24.96 Kontakte geladen
23:55:24.98 Anrufe geladen
23:55:24.98 Organizer geladen
23:55:25.00 Notizen geladen
23:55:25.00 SMS geladen
23:55:25.37 Hauptfenster fertig geladen
23:55:25.81 Downloader: RC=6 BytesMax=5 URL=http://www.fjsoft.at/myphoneexplorer/version.txt
23:55:32.92 Broadcaster started
23:55:32.92 Sending broadcast
23:55:33.42 Sending broadcast
23:55:33.92 Sending broadcast
23:55:34.92 bOpened=False
23:55:34.92 Failed to obtain the IP-address of the phone
23:55:34.92 Refresh ComDescriptions...
23:55:35.04 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
23:55:35.18 MODEM: COM3 Enumerator=PCI Displayed=56HP-PCT FriendlyName=56HP-PCT InstanceID=PCI\VEN_134D&DEV_7891&SUBSYS_0001134D&REV_02\4&BB29FA6&0&08F0
23:55:35.18 ErrMsg: Connection to phone could not be established:
Failed to obtain the IP-address of the phone
23:58:35.32 DBT_DEVICEARRIVAL: COM22
23:58:37.56 DBT_DEVICEREMOVECOMPLETE: COM22
23:58:41.85 DBT_DEVICEARRIVAL: COM22
23:58:45.85 Refresh ComDescriptions...
23:58:45.96 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
23:58:46.09 MODEM: COM3 Enumerator=PCI Displayed=56HP-PCT FriendlyName=56HP-PCT InstanceID=PCI\VEN_134D&DEV_7891&SUBSYS_0001134D&REV_02\4&BB29FA6&0&08F0
23:58:46.09 MODEM: COM22 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem #3 FriendlyName=SAMSUNG Mobile USB Modem #3 InstanceID=USB\VID_04E8&PID_6860&MODEM\6&2E02BE2&0&0001
00:18:40.07 Got new Broadcast: 002915373C17162E1D095E5F42533F0F06333A1C1D1F3A3B405F51522E31362B2F484A594B4804081E046364396C66484B5C56490700070F7C6170692F0A1206160C5C5710650C1D160A1D3E5E3822311F7907027A
00:18:45.56 Refresh ComDescriptions...
00:18:45.68 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
00:18:45.79 MODEM: COM3 Enumerator=PCI Displayed=56HP-PCT FriendlyName=56HP-PCT InstanceID=PCI\VEN_134D&DEV_7891&SUBSYS_0001134D&REV_02\4&BB29FA6&0&08F0
00:18:45.79 MODEM: COM22 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem #3 FriendlyName=SAMSUNG Mobile USB Modem #3 InstanceID=USB\VID_04E8&PID_6860&MODEM\6&2E02BE2&0&0001
00:18:46.71 StickyNotesPath=H:\WINDOWS\Sysnative\StikyNot.exe FileExists=False
00:18:47.85 OK pressed in settingswindow
00:18:47.87 Set first swap of settings
00:18:47.87 Apply new holidays
00:18:47.87 Holidays applied
00:18:47.89 Second swap of settings set
00:18:47.89 Everything is done
00:18:53.51 Sending broadcast
00:18:53.57 Got new Broadcast: 002915373C17162E1D095E5F42533F0F06333A1C1D1F19480B021E077B686B6D7D4D0F5850480A070306786072666248465D190A535D43432337650C1234203E2B3E1F63777E6019726B64
00:18:54.01 Sending broadcast
00:18:54.07 Got Broadcast
00:18:54.51 Sending broadcast
00:18:54.57 Got Broadcast
00:18:55.51 Try connecting to 192.168.2.4...
00:18:55.60 Connect to Android OK
00:18:55.60 Settimeout: RT=2000 WT=500
00:18:55.60 bOpened=True
00:18:55.60 [TX]: AT+CGSN
00:18:57.60 Got no Model, close port
00:18:57.60 Androidsocket wird geschlossen 7
00:18:57.60 Port wurde geschlossen
00:18:57.60 Phone could not be identified
00:18:57.60 Refresh ComDescriptions...
00:18:57.73 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
00:18:57.84 MODEM: COM3 Enumerator=PCI Displayed=56HP-PCT FriendlyName=56HP-PCT InstanceID=PCI\VEN_134D&DEV_7891&SUBSYS_0001134D&REV_02\4&BB29FA6&0&08F0
00:18:57.84 MODEM: COM22 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem #3 FriendlyName=SAMSUNG Mobile USB Modem #3 InstanceID=USB\VID_04E8&PID_6860&MODEM\6&2E02BE2&0&0001
00:18:57.84 ErrMsg: Connection to phone could not be established:
Phone could not be identified
00:20:07.26 Sending broadcast
00:20:07.39 Got Broadcast
00:20:07.76 Sending broadcast
00:20:07.90 Got Broadcast
00:20:08.26 Sending broadcast
00:20:08.31 Got Broadcast
00:20:09.26 Try connecting to 192.168.2.4...
00:20:09.35 Connect to Android OK
00:20:09.35 Settimeout: RT=2000 WT=500
00:20:09.35 bOpened=True
00:20:09.35 [TX]: AT+CGSN
00:20:12.00 Got no Model, close port
00:20:12.00 Androidsocket wird geschlossen 7
00:20:12.00 Port wurde geschlossen
00:20:12.01 Phone could not be identified
00:20:12.01 Refresh ComDescriptions...
00:20:12.12 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
00:20:12.25 MODEM: COM3 Enumerator=PCI Displayed=56HP-PCT FriendlyName=56HP-PCT InstanceID=PCI\VEN_134D&DEV_7891&SUBSYS_0001134D&REV_02\4&BB29FA6&0&08F0
00:20:12.25 MODEM: COM22 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem #3 FriendlyName=SAMSUNG Mobile USB Modem #3 InstanceID=USB\VID_04E8&PID_6860&MODEM\6&2E02BE2&0&0001
00:20:12.25 ErrMsg: Connection to phone could not be established:
Phone could not be identified
00:22:14.57 DBT_DEVICEREMOVECOMPLETE: COM22
00:23:02.28 DBT_DEVICEARRIVAL: COM22
00:23:04.10 DBT_DEVICEREMOVECOMPLETE: COM22
00:23:08.25 DBT_DEVICEARRIVAL: COM22
00:23:12.25 Refresh ComDescriptions...
00:23:12.35 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
00:23:12.48 MODEM: COM3 Enumerator=PCI Displayed=56HP-PCT FriendlyName=56HP-PCT InstanceID=PCI\VEN_134D&DEV_7891&SUBSYS_0001134D&REV_02\4&BB29FA6&0&08F0
00:23:12.50 MODEM: COM22 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem #3 FriendlyName=SAMSUNG Mobile USB Modem #3 InstanceID=USB\VID_04E8&PID_6860&MODEM\6&2E02BE2&0&0001
00:23:35.32 Sending broadcast
00:23:35.46 Got Broadcast
00:23:35.64 Got new Broadcast: 002915373C17162E1D095E5F42533F0F06333A1C1D1F3A3B405F51522E31362B2F484A594B4804081E046364396C66484B5C56490700070F7C6170692F0A1206160C5C5710650C1D160A1D3E5E3822311F7907027A
00:23:35.82 Sending broadcast
00:23:35.84 Got new Broadcast: 002915373C17162E1D095E5F42533F0F06333A1C1D1F19480B021E077B686B6D7D4D0F5850480A070306786072666248465D190A535D43432337650C1234203E2B3E1F63777E6019726B64
00:23:36.32 Sending broadcast
00:23:36.37 Got Broadcast
00:23:37.32 Try connecting to 192.168.2.4...
00:23:37.40 Connect to Android OK
00:23:37.40 Settimeout: RT=2000 WT=500
00:23:37.40 bOpened=True
00:23:37.42 [TX]: AT+CGSN
00:23:39.42 Got no Model, close port
00:23:39.42 Androidsocket wird geschlossen 7
00:23:39.42 Port wurde geschlossen
00:23:39.42 Phone could not be identified
00:23:39.42 Refresh ComDescriptions...
00:23:39.54 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
00:23:39.65 MODEM: COM3 Enumerator=PCI Displayed=56HP-PCT FriendlyName=56HP-PCT InstanceID=PCI\VEN_134D&DEV_7891&SUBSYS_0001134D&REV_02\4&BB29FA6&0&08F0
00:23:39.65 MODEM: COM22 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem #3 FriendlyName=SAMSUNG Mobile USB Modem #3 InstanceID=USB\VID_04E8&PID_6860&MODEM\6&2E02BE2&0&0001
00:23:39.65 ErrMsg: Connection to phone could not be established:
Phone could not be identified
00:23:44.95 Refresh ComDescriptions...
00:23:45.06 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
00:23:45.18 MODEM: COM3 Enumerator=PCI Displayed=56HP-PCT FriendlyName=56HP-PCT InstanceID=PCI\VEN_134D&DEV_7891&SUBSYS_0001134D&REV_02\4&BB29FA6&0&08F0
00:23:45.18 MODEM: COM22 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem #3 FriendlyName=SAMSUNG Mobile USB Modem #3 InstanceID=USB\VID_04E8&PID_6860&MODEM\6&2E02BE2&0&0001
00:23:46.17 StickyNotesPath=H:\WINDOWS\Sysnative\StikyNot.exe FileExists=False
Benutzer-Profile anzeigenPrivate Nachricht senden
TheLandYacht



Anmeldedatum: 09.06.2011
Beiträge: 143

BeitragVerfasst am: Di Feb 26, 2013 09:33 Antworten mit ZitatNach oben

I assume you're upgrading from an older phone?

Did you update your version of Android SDK (and the ADB that comes with it)? That ended up being my problem when I recently upgraded from an older phone.

Run SDK Manager, allow it to do its updates & restart SDK Manager...then run it again...and again...until it comes back with no more updates...and you should be in business.

It took (I think) 4 repetitions of update & restart (the program) before it worked.
Benutzer-Profile anzeigenPrivate Nachricht senden
Unicornz0



Anmeldedatum: 10.02.2013
Beiträge: 12

BeitragVerfasst am: Di Feb 26, 2013 15:43 Antworten mit ZitatNach oben

Thanks,
I'm trying to connect to another new Galaxy S3.
My other two Galaxy S3's are able to connect with MPE

How do I update Android SDK?
Benutzer-Profile anzeigenPrivate Nachricht senden
FJ
Site Admin


Anmeldedatum: 15.02.2006
Beiträge: 31906
Wohnort: Tirol

BeitragVerfasst am: So März 24, 2013 01:41 Antworten mit ZitatNach oben

Which Android version does your phone have ?
Check if you have installed security apps on the phone, f.e. "AppGuard" is able to block the internet connections of other apps

_________________
Ich bitte um Verständnis daß ich aufgrund des hohen Aufkommens im Forum und meines zeitlichen Rahmens nichtmehr jeden Thread im Forum persönlich lesen bzw. beantworten kann.

Bitte benutzt auch die Forum-Suche bzw. die FAQ
Benutzer-Profile anzeigenPrivate Nachricht sendenE-Mail sendenICQ-Nummer
Beiträge der letzten Zeit anzeigen:      
Neues Thema eröffnenNeue Antwort erstellen


 Gehe zu:   



Nächstes Thema anzeigen
Vorheriges Thema anzeigen
Du kannst keine Beiträge in dieses Forum schreiben.
Du kannst auf Beiträge in diesem Forum nicht antworten.
Du kannst deine Beiträge in diesem Forum nicht bearbeiten.
Du kannst deine Beiträge in diesem Forum nicht löschen.
Du kannst an Umfragen in diesem Forum nicht mitmachen.

Powered by phpBB © 2001, 2002 phpBB Group :: FI Theme :: Alle Zeiten sind GMT + 1 Stunde
Deutsche Übersetzung von phpBB.de