HowTo: Use MyPhoneExplorer under GNU/Linux (English Version)
Thanks for guide.
I used USB. As suggested did wrote the rules, but got error while running next command chmod a+rx, error no such directory or files found.
After that I checked and found that I already had rule written with number 99 hope that is not the issue.
please suggest how to fix, as I was not allowed to delete old rule file from file manager directly. is there any command to remove it?
I used USB. As suggested did wrote the rules, but got error while running next command chmod a+rx, error no such directory or files found.
After that I checked and found that I already had rule written with number 99 hope that is not the issue.
please suggest how to fix, as I was not allowed to delete old rule file from file manager directly. is there any command to remove it?
Assuming you are using ubuntu or similar, and are using terminal commands, you need to use sudo commands to delete or move files (sudo rm ...., or sudo mv ... etc). This isn't the place for a linux lesson, so if you are unsure I suggest you do more reading about linux commands. I'm no expert either. I don't think the numbering matters a great deal, I believe it just determines the order the rules are processed in, but I'm not sure.mahp hat geschrieben:Thanks for guide.
I used USB. As suggested did wrote the rules, but got error while running next command chmod a+rx, error no such directory or files found.
After that I checked and found that I already had rule written with number 99 hope that is not the issue.
please suggest how to fix, as I was not allowed to delete old rule file from file manager directly. is there any command to remove it?
If you have just created a 99 rule then just move (ie rename) it using sudo mv.
Thanks for guidance.
Even after removing one rule and trying to search possible threads related to USB connecting to serial on web none is of help on solving the com permission error. other than udev rules also found some command for ttyusb0 or ttys0 under dev is it to do something with com connecting.
help me if you can as com1 error not allowing me to use MPE.
Even after removing one rule and trying to search possible threads related to USB connecting to serial on web none is of help on solving the com permission error. other than udev rules also found some command for ttyusb0 or ttys0 under dev is it to do something with com connecting.
help me if you can as com1 error not allowing me to use MPE.
I'm afraid I'm not sure what you are trying to do. com1 is a serial port, not USB. My comments were, as I said, for a USB connection. USB rules are probably, I believe, irrelevant to serial ports.mahp hat geschrieben:Thanks for guidance.
Even after removing one rule and trying to search possible threads related to USB connecting to serial on web none is of help on solving the com permission error. other than udev rules also found some command for ttyusb0 or ttys0 under dev is it to do something with com connecting.
help me if you can as com1 error not allowing me to use MPE.
So what is your connection. Proper USB, or a serial port?
Sorry to trouble you and confuse you.
I am using USB cable for connection and using Ubuntu.
I have refer the start of the same thread, which says that for using USB you need to write rules and also link it to com1 by following command
Code:
:~/$ cd ~/.wine/dosdevice/
:~/.wine/dosdevices$ ln -is /dev/
ttyACM0 com1
and to start MPE you need to input com1 in setting and then start.
but since that did not work I have to put in on forum.
I am using USB cable for connection and using Ubuntu.
I have refer the start of the same thread, which says that for using USB you need to write rules and also link it to com1 by following command
Code:
:~/$ cd ~/.wine/dosdevice/
:~/.wine/dosdevices$ ln -is /dev/
ttyACM0 com1
and to start MPE you need to input com1 in setting and then start.
but since that did not work I have to put in on forum.
Sorry, I don't know how that works. As I said in my first reply I use a program called adb to make the connection possible, rather than com1. I can't now find the instructions I used to do that, so you'll need help from someone else.mahp hat geschrieben:Sorry to trouble you and confuse you.
I am using USB cable for connection and using Ubuntu.
I have refer the start of the same thread, which says that for using USB you need to write rules and also link it to com1 by following command
Code:
:~/$ cd ~/.wine/dosdevice/
:~/.wine/dosdevices$ ln -is /dev/
ttyACM0 com1
and to start MPE you need to input com1 in setting and then start.
but since that did not work I have to put in on forum.
Bluetooth error
Hello,
I have a problem connecting the phone over bluetooth. I paired the phone successfully, I can talk to it with standard AT commands through serial monitor, but in MyPhoneExplorer I get "Phone not recognized". The debug log is:
My configuration:
* Ubuntu 14.04 LTS
* Wine 1.6.2
* MyPhoneExplorer 1.8.6
* Phone: Sony Ericsson K550i
I have a problem connecting the phone over bluetooth. I paired the phone successfully, I can talk to it with standard AT commands through serial monitor, but in MyPhoneExplorer I get "Phone not recognized". The debug log is:
I am interested, what is "error 31" and how to get rid of it. Is it Serial device not workig error? Any hints?Port 1 wurde geöffnet !
bOpened=True
[TX]: AT+CGSN
WritePort failed. TransferedBytes=31 Systemerror: 31 [General failure.]
Got no Model, close port
My configuration:
* Ubuntu 14.04 LTS
* Wine 1.6.2
* MyPhoneExplorer 1.8.6
* Phone: Sony Ericsson K550i
Re: HowTo: Use MyPhoneExplorer under GNU/Linux (English Vers
I understand that these UPDATES (copied from the very first post in this thread) are meant to take precedence over the original post, itself, which relates only to installing (much) older MPE versions, those below v1.7.0.
However, there are two updates above the 'body' of the original post, and both are undated, so I am at a loss as to which one came first, and which one came second, and therefore would take precedence over the other, for installing the current MPE download, which is v1.8.6.
The quoted updates are as follows:
"When using [installing] MyPhone Explorer 1.7.0 or higher, you can just use [run the] normal [Wine] setup [, or in other words, wine MyPhoneExplorer.exe].
But here, my understanding must be incorrect, because when the above is run in Terminal, you can see why the program fails to start: it is missing MSVBVM60.DLL. I have read (elsewhere) that this file might be needed, but since these directions seemed to say, 'run the executable as a normal setup', I thought perhaps the current version of Wine makes it unnecessary to do what was needed in the past -- but clearly this is not the case.
Moving along, to (what appears to be) the earlier UPDDATE located above the one I just followed, the one translated from Polish, there is mention of not only needing MSVBVM60.DLL, but also a great many other files.
However, these directions are dated 2010, obviously referring to both the Wine and MPE versions that were current five years ago. With both programs being updated so many times after these were written, I am of course wondering how much of this still applies?
So my questions:
Obviously, the 'update' that says to just run MPE directly with the Wine command is not working.
So, then should we disregard the 'lower UPDATE' and instead go directly to the upper one, as still being the proper procedure, even given the passage of time?
__________________
Linux Mint Quiana - Bodhi Linux 3.0
MPE v1.8.6
However, there are two updates above the 'body' of the original post, and both are undated, so I am at a loss as to which one came first, and which one came second, and therefore would take precedence over the other, for installing the current MPE download, which is v1.8.6.
The quoted updates are as follows:
weinbi_restored hat geschrieben:UPDATE:Please check this tutorial: http://translate.googleusercontent.com/ ... Rltax6RCRw
Assuming the updates are listed in order by date, I disregarded the first, assuming it was superseded by the second:UPDATE:When using MyPhoneExplorer 1.7.0 or higher, you can just use normal Setup!
"When using [installing] MyPhone Explorer 1.7.0 or higher, you can just use [run the] normal [Wine] setup [, or in other words, wine MyPhoneExplorer.exe].
But here, my understanding must be incorrect, because when the above is run in Terminal, you can see why the program fails to start: it is missing MSVBVM60.DLL. I have read (elsewhere) that this file might be needed, but since these directions seemed to say, 'run the executable as a normal setup', I thought perhaps the current version of Wine makes it unnecessary to do what was needed in the past -- but clearly this is not the case.
Moving along, to (what appears to be) the earlier UPDDATE located above the one I just followed, the one translated from Polish, there is mention of not only needing MSVBVM60.DLL, but also a great many other files.
However, these directions are dated 2010, obviously referring to both the Wine and MPE versions that were current five years ago. With both programs being updated so many times after these were written, I am of course wondering how much of this still applies?
So my questions:
__________________
Linux Mint Quiana - Bodhi Linux 3.0
MPE v1.8.6
Hardware/software/firmware specs:
M-Horse 9500mini, Model: SPHS on Hsdroid | Android version 4.1.2 (probably faked. I think real version is 2.3.5)
Kernel: 2.6.35.7 | Firmware: 6820_2.3.5_c913 ... | Android Calendar v4.1.2 | MPE v1.8.5 | MPE client v1.0.28 | USB connection | Windows7 SP1
M-Horse 9500mini, Model: SPHS on Hsdroid | Android version 4.1.2 (probably faked. I think real version is 2.3.5)
Kernel: 2.6.35.7 | Firmware: 6820_2.3.5_c913 ... | Android Calendar v4.1.2 | MPE v1.8.5 | MPE client v1.0.28 | USB connection | Windows7 SP1
How to install MPE 1.8.6 under Wine 1.6.2
Here is the most recent guide, how to install MyPhoneExplorer under Wine. Forget the process described on first page as well as the process on pages of our Polish friend and also everything using PlayOnLinux. The current process is much more simple. In fact it is described fully on MyPhoneExplorer page on WineHQ, it is only too brief - so here you are the HowTo with more explanation.
We will suppose, that you have already installed:
* Wine 1.6
* winetricks
* MyPhoneExplorer_Setup_1.8.6.exe downloaded to your home directory
Now the installation. It is strongly recommended to install the MPE into separate wineprefix, so that MPE does not interference with other programms installed with wine. Therefore all following commands have the wineprefix declaration at the beginning:
* initialize new wineprefix
* install msxml3 dll needed by MPE
* install vb6run dll needed by MPE (this is the thing RonCam is missing in previous post)
* install MPE
* click through the installer and here comes the main trick. When the advertisement window appears, you must kill it manually, else there is no chance to continue with installation - no buttons react.
You find the process number of this installer window by this command (The process name is "InstallMgr.exe")
And
(replace **** by number seen in previous command)
And that's all. Then you have to connect your phone - connecting Android phone over wifi should work out of the box, hints for connection by bluetooth or USB cable can be found on first page of this discussion thread.
We will suppose, that you have already installed:
* Wine 1.6
* winetricks
* MyPhoneExplorer_Setup_1.8.6.exe downloaded to your home directory
Now the installation. It is strongly recommended to install the MPE into separate wineprefix, so that MPE does not interference with other programms installed with wine. Therefore all following commands have the wineprefix declaration at the beginning:
* initialize new wineprefix
Code: Alles auswählen
WINEPREFIX=$HOME/.wine_myphoneexplorer wine 'wineboot'Code: Alles auswählen
WINEPREFIX=$HOME/.wine_myphoneexplorer winetricks msxml3Code: Alles auswählen
WINEPREFIX=$HOME/.wine_myphoneexplorer winetricks vb6runCode: Alles auswählen
WINEPREFIX=$HOME/.wine_myphoneexplorer wine ~/MyPhoneExplorer_Setup_1.8.6.exeYou find the process number of this installer window by this command (The process name is "InstallMgr.exe")
Code: Alles auswählen
ps -aux | grep InstallMgrCode: Alles auswählen
kill ****And that's all. Then you have to connect your phone - connecting Android phone over wifi should work out of the box, hints for connection by bluetooth or USB cable can be found on first page of this discussion thread.
Re: How to install MPE 1.8.6 under Wine 1.6.2
Thanks very much for posting this 'gem' of information. My only suggestion is that a moderator might make edits into the first post of this thread, removing the 'legacy' information and directing forum members to fugazza's post?fugazza hat geschrieben:Here is the most recent guide, how to install MyPhoneExplorer under Wine. Forget the process described on first page as well as the process on pages of our Polish friend and also everything using PlayOnLinux. The current process is much more simple.
...
Hardware/software/firmware specs:
M-Horse 9500mini, Model: SPHS on Hsdroid | Android version 4.1.2 (probably faked. I think real version is 2.3.5)
Kernel: 2.6.35.7 | Firmware: 6820_2.3.5_c913 ... | Android Calendar v4.1.2 | MPE v1.8.5 | MPE client v1.0.28 | USB connection | Windows7 SP1
M-Horse 9500mini, Model: SPHS on Hsdroid | Android version 4.1.2 (probably faked. I think real version is 2.3.5)
Kernel: 2.6.35.7 | Firmware: 6820_2.3.5_c913 ... | Android Calendar v4.1.2 | MPE v1.8.5 | MPE client v1.0.28 | USB connection | Windows7 SP1
-
user_deleted
Thanks to fugazza's very helpful posting on Jul 01, 2015 in this thread MPE in wine is working fine here. Connecting the Android phone over wifi worked out of the box.
A connection by USB cable as can be found on the first page of this thread (using /dev/ttyACM0) did not work here. But I have found an easy way to get the USB cable connection working. I installed 2 small packages into my Arch Linux:
android-tools (0,33 MByte)
android-udev (0,02 MByte)
This provides adb, fastboot and 51-android.rules . No need to install the android-sdk (340 MByte)!
I had to copy 51-android.rules to /etc/udev/rules.d/51-android.rules .
This file contains info for many android devices, including my Huawei. For other devices you may need to add info there.
Maybe other Linux distros have similar small packages for adb.
Next I did:
1.) Connect phone and Linux-PC by USB cable.
2.) In a terminal type "adb devices". The adb server starts and reports the connected device.
3.) Start MPE in wine.
4.) MPE-Client in the phone is starting automatically.
Also this sequence of commands worked:
1.) In a terminal type "adb devices" .
2.) Start MPE in wine.
3.) Connect phone and Linux-PC by USB cable.
4.) MPE-Client in the phone is starting automatically.
This method has the drawback that you can't check whether the device is connected.
My configuration:
Arch Linux 64 bit
Wine 1.7.47-1
MyPhoneExplorer 1.8.6
Phone: Huawei Ideos X3 (Android 2.3.3)
A connection by USB cable as can be found on the first page of this thread (using /dev/ttyACM0) did not work here. But I have found an easy way to get the USB cable connection working. I installed 2 small packages into my Arch Linux:
android-tools (0,33 MByte)
android-udev (0,02 MByte)
This provides adb, fastboot and 51-android.rules . No need to install the android-sdk (340 MByte)!
I had to copy 51-android.rules to /etc/udev/rules.d/51-android.rules .
This file contains info for many android devices, including my Huawei. For other devices you may need to add info there.
Maybe other Linux distros have similar small packages for adb.
Next I did:
1.) Connect phone and Linux-PC by USB cable.
2.) In a terminal type "adb devices". The adb server starts and reports the connected device.
3.) Start MPE in wine.
4.) MPE-Client in the phone is starting automatically.
Also this sequence of commands worked:
1.) In a terminal type "adb devices" .
2.) Start MPE in wine.
3.) Connect phone and Linux-PC by USB cable.
4.) MPE-Client in the phone is starting automatically.
This method has the drawback that you can't check whether the device is connected.
My configuration:
Arch Linux 64 bit
Wine 1.7.47-1
MyPhoneExplorer 1.8.6
Phone: Huawei Ideos X3 (Android 2.3.3)
Everything works fine, but..
Hi!
First of all thank you for the app, great!!
I've been with it for almost.. I donno.. 4-5 years..
Love it and this prg fills a huge gap in the sync line-up, I couldn't do without it basically I must say. Full credit to FJ.
Ok, that's about the intro, now some words about my difficulty please.
Everything works fine, but the Mpe is not able to see the com port please. Even in the Blueman there is a dedicated option to connect to Mpe and if clicked on a nice message comes up saying that "Serial port connected to /dev/rfcomm0" in the Mpe.
Also in the phone the client says "Connected via Bluetooth", but actually when I try to connect in the Mpe meanwhile having these promising signs Mpe says "Connection to phone could not be established: -2147418113 - Method '~' of object '~' failed".
I have tried many things and of course some parts of the method described at the beginning of this thread, but no use.
In my opinion everything is perfectly settled, cos there is a live serial port connection with the phone, but somehow Mpe does not recognise it please.
I am running v1.8.7 and the client is v1.0.38. I have been able to synchronize everything between a WinXp Sp3 laptop and the same cell for a long time please. The Wine version is 1.9.3, the PlayOnLinux is also the newest version. Otherwise no additional errors come up, just there is no connection.
I've been on it for some days now, you are my last resort please.
Thank you ever so much for your help.
First of all thank you for the app, great!!
I've been with it for almost.. I donno.. 4-5 years..
Love it and this prg fills a huge gap in the sync line-up, I couldn't do without it basically I must say. Full credit to FJ.
Ok, that's about the intro, now some words about my difficulty please.
Everything works fine, but the Mpe is not able to see the com port please. Even in the Blueman there is a dedicated option to connect to Mpe and if clicked on a nice message comes up saying that "Serial port connected to /dev/rfcomm0" in the Mpe.
Also in the phone the client says "Connected via Bluetooth", but actually when I try to connect in the Mpe meanwhile having these promising signs Mpe says "Connection to phone could not be established: -2147418113 - Method '~' of object '~' failed".
I have tried many things and of course some parts of the method described at the beginning of this thread, but no use.
In my opinion everything is perfectly settled, cos there is a live serial port connection with the phone, but somehow Mpe does not recognise it please.
I am running v1.8.7 and the client is v1.0.38. I have been able to synchronize everything between a WinXp Sp3 laptop and the same cell for a long time please. The Wine version is 1.9.3, the PlayOnLinux is also the newest version. Otherwise no additional errors come up, just there is no connection.
I've been on it for some days now, you are my last resort please.
Thank you ever so much for your help.
Connection to phone could not be established: -2147418113
Hi,
do you bind correct bluetooth channel to your /dev/rfcomm0? For eaxmple my SonyEricsson K550 has two channels: #3 is the correct one, which understands service command, while #2 serves as dial up modem for calling from computer.
How to debug, if you have right channel? After connecting the serial port, connect to /dev/rfcomm0 using some serial port monitor (I personally use minicom) and try to write some basic commands - like AT (phone should answer something like "OK") or AT+CGSN (phone should answer its IMEI number).
do you bind correct bluetooth channel to your /dev/rfcomm0? For eaxmple my SonyEricsson K550 has two channels: #3 is the correct one, which understands service command, while #2 serves as dial up modem for calling from computer.
How to debug, if you have right channel? After connecting the serial port, connect to /dev/rfcomm0 using some serial port monitor (I personally use minicom) and try to write some basic commands - like AT (phone should answer something like "OK") or AT+CGSN (phone should answer its IMEI number).
Minicom
Hi Fugazza,
Thanks for your kind reply and for your help.
I have installed Minicom and tried to change the Serial Device in the Serial Port Section to /dev/rfcomm0. Unfortunately when I tried to Save setup as dfl the message was Cannot write to /etc/minicom/minirc.dfl please.
I unplugged the BT stack and no Mpe was running, so I don't know what was the reason of it.
Any idea please?
Thank you!
Thanks for your kind reply and for your help.
I have installed Minicom and tried to change the Serial Device in the Serial Port Section to /dev/rfcomm0. Unfortunately when I tried to Save setup as dfl the message was Cannot write to /etc/minicom/minirc.dfl please.
I unplugged the BT stack and no Mpe was running, so I don't know what was the reason of it.
Any idea please?
Thank you!
Hi,
I guess, that you are not running minicom as sudo, therefore you do not have permissions to write into /etc. See also manual page, parameter configuration. Nevertheless even if you are not able to store your configuration, the minicom works with given port just after writing it in settings dialogue. ... Maybe if minicom is too difficult to use for you, you can use something different. For example arduino IDE has really usable serial port monitor (Yes, it is a little bit overhead to install arduino only because of its serial port monitor.)
I guess, that you are not running minicom as sudo, therefore you do not have permissions to write into /etc. See also manual page, parameter configuration. Nevertheless even if you are not able to store your configuration, the minicom works with given port just after writing it in settings dialogue. ... Maybe if minicom is too difficult to use for you, you can use something different. For example arduino IDE has really usable serial port monitor (Yes, it is a little bit overhead to install arduino only because of its serial port monitor.)
Still
Hi Fugazza,
Sorry for the late reply, but I had no time.
So, I managed to modify the port to /dev/rfcomm0 in Minicom and it stays as default after booting up the laptop.
So the port in Blueman and Minicom are identical, but Mpe still not able to connect.
Is there any other adjustable stuff in Minicom or somewhere else to fix the issue please?
Thank you ever so much!
Sorry for the late reply, but I had no time.
So, I managed to modify the port to /dev/rfcomm0 in Minicom and it stays as default after booting up the laptop.
So the port in Blueman and Minicom are identical, but Mpe still not able to connect.
Is there any other adjustable stuff in Minicom or somewhere else to fix the issue please?
Thank you ever so much!
Still
Is there any connection between the channel number and the port number pls?
And also this /dev/rfcomm0 is actually the port number, or let's say com1 would be a port number, because in Minicom in the menu of Serial port setup there is no other option which actually would say anything about ports just the serial device is mentioned which is /dev/rfcomm0. So actually I don't really see how to set up any port numbers in Minicom.
How many channels would be possible btw, cos in the Terminal the hcitool scan does not work for me. It starts scanning, and says nothing after a while just the prompt comes back, so my plan is to try to change the channel in the rfcomm.conf file from 1 to 30 and restart the laptop everytime trying to connect with Mpe as well to the phone..
Thanks if somebody is here.
And also this /dev/rfcomm0 is actually the port number, or let's say com1 would be a port number, because in Minicom in the menu of Serial port setup there is no other option which actually would say anything about ports just the serial device is mentioned which is /dev/rfcomm0. So actually I don't really see how to set up any port numbers in Minicom.
How many channels would be possible btw, cos in the Terminal the hcitool scan does not work for me. It starts scanning, and says nothing after a while just the prompt comes back, so my plan is to try to change the channel in the rfcomm.conf file from 1 to 30 and restart the laptop everytime trying to connect with Mpe as well to the phone..
Thanks if somebody is here.