Seite 10 von 13
Verfasst: Mo 17. Sep 2012, 14:11
von Pastim
An interesting result.
I fiddled and tinkered and tried everything I could think of. I started again several times. One of the better ideas was to isolate MPE under its own Wine prefix. That way I can set Wine up for this specific application, without affecting any other Wine installations.
My current set-up is Wine 1.5.9, MPE 1.8.4. I also have adb installed, and as you say I have to run that first.
MPE now works reasonably well (particularly after an MPE update which fixed an xml-related issue). I only have oleaut32 (native) and, as default, *msxml3 (native) set up in Wine. If I add riched20, MPE won't run - it complains that an SMS element is not installed or is out of date. I can run with or without gdiplus (native).
The only problem I have these days is that MPE crashes every single time on exit.
I should apologise for not updating my last post.
Verfasst: Mo 17. Sep 2012, 22:08
von mjacek
Well, I am running under same wineprefix as everything else (which is mainly MS Office 2007). gdi setting probably comes from MSOffice.
I recall having some complaint about SMS (but I am not sure...).
Never had an MPE crash at exit.
Just to make it clear: My Wine is emulating "Windows XP" and my library override full settings are:
Code: Alles auswählen
*gdiplus:(native)
*msvcr90:(native,builtin)
*msvcrt:(native,builtin)
*riched20:(native,builtin)
*riched32:(native,builtin)
riched20:(native)
I wonder what the double riched20 does, but I am not tinkering any more

. I just don't want to lose my Office install which enables me to forget MS Windows7 partition. (OK, I am rebooting into Win when some document uses Microsft Equations....)
Bluetooth connection to Android (MPE+Wine) - need help/hint
Verfasst: Mo 17. Sep 2012, 22:55
von mjacek
Need help/hint with Bluetooth connection
I managed to connect via bluetooth, but failed to sync MPE.
The story is:
- I found out that a bluetooth script installed by myphoneinstaller3.2.sh script is not doing what is expected (probably some things have changed since 2008)
- so I did a binding manually:
- in a "sudo bash" session i did "sdptool browse xx:xx:...:xx" (xx...xx is my BT phone address)
- found that MyPhoneExplorer uses rfcomm channel 3 (this changes with any restart of MPE at the phone!)
- so I bound "rfcomm bind 0 xx:xx..:xx 3" (0=/dev/rfcomm0, 3=channel number)
- my useraccount is a member of dialout group, so he already has -rw- permissions to /dev/rfcomm0
- my .wine/dosdevices/com2 is a symlink to /dev/rfcomm0 (com1 is used for something else)
- so I tested the rfcomm link with "modem-cmd /dev/rfcomm0 ATI", reply was "OK" !!!! (modem-cmd is a tiny utility from modem-cmd ubuntu package)
- then I set "COM2" in MPE setiings, and MPE connected. However, when I tried to sync, I got OBEX timeout. Log contents below.
The question is - what I can do, what should I try? It seems that - maybe- the BT port does not like packet connections? Texts seem to get correct replies...
Logfile:
Code: Alles auswählen
22:56:48.66 Avaiable Ports: COM0=;
22:56:48.66 Neue COM-Bibliothek wird verwendet
22:56:48.66 SPort Properties set, opening COM2
22:56:48.82 After OpenPort
22:56:48.82 Settimeout: RT=5000 WT=500
22:56:49.32 Port 2 wurde geöffnet !
22:56:49.33 bOpened=True
22:56:49.33 [TX]: AT+CGSN
22:56:49.37 [RX]: AT+CGSN
22:56:49.37 [RX]: 3530(....edited to hide personal IMEI data)
22:56:49.37 [RX]: OK
22:56:49.38 Settimeout: RT=15000 WT=1000
22:56:49.40 [TX]: AT*PIN=a21c(......edited to hide.....)
22:56:49.41 [RX]: AT*PIN=a21c(...............)
22:56:49.41 [RX]: *PIN: ACCESS OK,10
22:56:49.41 [RX]: OK
22:56:49.45 [TX]: ATI
22:56:49.46 [RX]: ATI
22:56:49.46 [RX]: LGE LG-E610
22:56:49.46 [RX]: OK
22:56:49.47 [TX]: AT*APPVERSION=1.8.4
22:56:49.49 [RX]: AT*APPVERSION=1.8.4
22:56:49.49 [RX]: 15,1.0.21
22:56:49.49 [RX]: OK
22:56:49.50 [TX]: AT+CSCS="UTF-8"
22:56:49.51 [RX]: AT+CSCS="UTF-8"
22:56:49.51 [RX]: OK
22:56:49.52 [TX]: AT+CNMI=2,1,0,1
22:56:49.53 [RX]: AT+CNMI=2,1,0,1
22:56:49.53 [RX]: ERROR
22:56:49.55 [TX]: AT*ECAM=1
22:56:49.55 [RX]: AT*ECAM=1
22:56:49.55 [RX]: OK
22:56:49.56 Alle Verbindungsaktionen beendet
22:56:53.52 [TX]: AT+CBC
22:56:53.56 [RX]: AT+CBC
22:56:53.56 [RX]: +CBC: 0,47
22:56:53.56 [RX]: OK
22:56:53.74 Form_Activate fSync Operation=7
22:56:53.76 [TX]: AT+CPROT=0
22:56:53.82 [RX]: AT+CPROT=0
22:56:53.82 [RX]: CONNECT
22:56:53.83 OBEX Connect: 16384 Bytes Paketgröße, Target: IRMC-SYNC
22:56:53.83 [TX]: 80 00 13 10 00 40 00 46 00 0C 49 52 4D 43 2D 53 59 4E 43
22:57:08.83 [RX]: 00
22:57:08.83 Lesevorgang fehlerhaft! - Systemerror: 0 [Sukces.]
22:57:08.83 OBEX Disconnect
22:57:08.83 Settimeout: RT=10000 WT=10000
22:57:08.83 [TX]: 81 00 03
22:57:18.83 [RX]: 00
22:57:18.83 Lesevorgang fehlerhaft! - Systemerror: 0 [Sukces.]
22:57:18.83 Disconnect answered...
22:57:18.83 ErrMsg: Obex protocol could not be initialized!
OBEX Errorcode: 00 - Phone didn't answer, Timeout
22:57:42.30 Port 2 wird geschlossen
22:57:42.40 Port wurde geschlossen
"send SMS" editor problem
Verfasst: Mo 17. Sep 2012, 23:02
von mjacek
Problem with sending SMS
MPE 1.8.4, wine 1.4, setup as in my previous posts.
The problem is that I can write an SMS, but it is saved as empty (text length 0), and of course not sent.
It seems like a bug in the library widget - when I type, the text appears, but cursor does not move, and the SMS length counter does not advance (still 160 characters left) - in the result, the "send" button does not activate.
Any hint? Maybe the DLL for this widget should be overriden or substituted - so my question is which dll handles the widget?
Verfasst: Di 18. Sep 2012, 16:53
von Pastim
mjacek hat geschrieben:Well, I am running under same wineprefix as everything else (which is mainly MS Office 2007). gdi setting probably comes from MSOffice.
I recall having some complaint about SMS (but I am not sure...).
Never had an MPE crash at exit.
Thanks. I tried your settings - no change. Never mind - it synchronises - that's all that matters!
Verfasst: Di 18. Sep 2012, 17:02
von mjacek
Pastim hat geschrieben:
Thanks. I tried your settings - no change. Never mind - it synchronises - that's all that matters!
At pressing "x" button, with USB connection through ADB, I do get a squeezed info window saying something like "(unreadable text) OK?" - but I always say OK, then I recall that maybe I should disconnect phone connection, and after dicnonnecting MPE it allows me to close window. Maybe this info window is crashing you?
Verfasst: Di 18. Sep 2012, 17:44
von Pastim
mjacek hat geschrieben:At pressing "x" button, with USB connection through ADB, I do get a squeezed info window saying something like "(unreadable text) OK?" - but I always say OK, then I recall that maybe I should disconnect phone connection, and after dicnonnecting MPE it allows me to close window. Maybe this info window is crashing you?
I always disconnect first, so it isn't that. Never mind

[BLUETOOTH] i've tried million ways..
Verfasst: Di 4. Dez 2012, 02:43
von chika.tambun
Anonymous hat geschrieben:K got it working from usb cable
Millions thanks for this tutorial
but still not working.. i've followed every step on first thread.. even i've tried the 1.7.6 to 1.8.4 version but still no luck
is the previous version on this link
www.fjsoft.at/files/MyPhoneExplorer_wine.zip mandatory to be downloaded?
[because it is a dead link now]
the bluetooth have already connected but.. this image error i've got
*i want to this ubu-box connect to MPE through BlueTooth connection desperately
best regards,
chika.tambun@gmail.com
PS: this is my log file
http://paste.ubuntu.com/1409358/
Re: [BLUETOOTH] i've tried million ways..
Verfasst: Di 4. Dez 2012, 18:29
von Pastim
chika.tambun hat geschrieben:
but still not working.. i've followed every step on first thread.. even i've tried the 1.7.6 to 1.8.4 version but still no luck
What type of phone is it?
What version of Ubuntu?
Do you have wine installed properly. Which version?
1.8.4 of MPE works fine for me with an Android phone, USB and ADB installed. However I have not used bluetooth recently.
The instructions I followed were those at
http://translate.google.com/translate?h ... u-a271.htm
I'm not sure if the bluetooth instructions are 100% accurate.
Re: [BLUETOOTH] i've tried million ways..
Verfasst: Fr 7. Dez 2012, 11:24
von chika.tambun
Pastim hat geschrieben:
What type of phone is it?
What version of Ubuntu?
Do you have wine installed properly. Which version?
1.8.4 of MPE works fine for me with an Android phone, USB and ADB installed. However I have not used bluetooth recently.
I'm not sure if the bluetooth instructions are 100% accurate.
w610i it works well on windows*
lucid lynx
timkubus@kubuslab:~$ wine --version
wine-1.2.3
i want BT connection with this box
btw thanks for your quick reply
Re: [BLUETOOTH] i've tried million ways..
Verfasst: Fr 7. Dez 2012, 12:18
von Pastim
chika.tambun hat geschrieben:i want BT connection with this box
Since you say the phone is properly connected/paired then all I can suggest is that MPE is not using the right device.
If you have multiple bluetooth devices connected that might cause a problem. Other than this I'm out of my depth I'm afraid.
Re: [BLUETOOTH] i've tried million ways..
Verfasst: Do 13. Dez 2012, 15:01
von chika.tambun
Pastim hat geschrieben:chika.tambun hat geschrieben:i want BT connection with this box
Since you say the phone is properly connected/paired then all I can suggest is that MPE is not using the right device.
If you have multiple bluetooth devices connected that might cause a problem. Other than this I'm out of my depth I'm afraid.
finally work
ubuntu 12.04
wine 1.4
mpe 1.8.4
with BT connection
with stable connection ENABLED

(refer to first post ever)D
thankyou for your response

Verfasst: Do 21. Feb 2013, 08:48
von beelze
Upgrading wine from 1.5.22 to 1.5.23 broked MPE (1.8.4) — after showing main windows raised «Unhandled exception: page fault on read access to 0x00000101 in 32-bit code (0x7e8461f1).»
Does anyone has the same issue? How it can be fixed?
Verfasst: Mo 1. Jul 2013, 10:40
von Nickel21
my problem have solve..Thanks alot..
Verfasst: Mo 16. Sep 2013, 14:21
von Pastim
I just installed version 1.8.5 on my ubuntu 12.04 64 bit system under Wine 1.5.29, with adb drivers installed.
The usb cable connection no longer works, giving the error 'Connection to phone could not be established'.
This has previously been running very reliably with 1.8.4, so I can only assume something has changed in this area.
I understand linux isn't supported, but any clues as to changes would be helpful. For instance, are newer adb drivers needed? My phone's android version is 2.3.
In the mean time I have successfully reverted to 1.8.4, so it is definitely something in 1.8.5 that is new and incompatible.
Verfasst: Fr 20. Sep 2013, 23:21
von FJ
Copy the file C:\Programs\MyPhoneExplorer\DLL\adb.exe, install MyPhoneExplorer 1.8.5 and then overwrite the new version of adb.exe with the old one.
Don't forget to tell me if this fixed your problem
Verfasst: Sa 21. Sep 2013, 10:36
von Pastim
Great! Worked first time. Thank you very much.
I will get round to Donating!
Verfasst: Di 1. Okt 2013, 10:27
von jawedmaha
i'll put the link when i find it back
Verfasst: So 16. Feb 2014, 05:58
von mahp
I managed to install MPE 1.8.4 in wine. Getting error while connecting USB through com1 giving error permission denied.
suggest how to fix it. or how to find free com port and use it. as I am new to Linux.
Verfasst: So 16. Feb 2014, 10:35
von Pastim
mahp hat geschrieben:I managed to install MPE 1.8.4 in wine. Getting error while connecting USB through com1 giving error permission denied.
suggest how to fix it. or how to find free com port and use it. as I am new to Linux.
Are you using a serial link through com1, or a USB port on the PC?
Do you have adb installed?
If using a USB port and adb, then you need to do several things. I am on ubuntu, and use the following commands.
Once the gedit (or leafpad or whatever editor you use) window pops-up, type the following line:
Code: Alles auswählen
SUBSYSTEM=="usb", ATTRS{idVendor}=="nnnn", SYMLINK+="android_adb", MODE="0666" GROUP="plugdev"
when nnnn is the USB vendor code for your phone. You should be able to find this using the lsusb command when your phone is connected, from the ID string nnnn:xxxx
Then:
Code: Alles auswählen
sudo chmod a+rx /etc/udev/rules.d/51-android.rules
sudo restart udev
Find the adb program and run it as follows:
the command:
should show your phone.
If you still have problems you may have to change the security of the adb command. A not very secure way is to find where your adb program is and change directory to it. Then: