First try autodetection. If it doesn't find your phone, and you are sure you have it connected via USB cable and all drivers installed, you have to set it manually. In Windows Device Manager there should be "(BenQ-)Siemens Mobile Phone" under "Modems" for OBEX port, and "(BenQ-)Siemens Diagnostic Interface" under "COM and LTP ports" for BREW. For further instructions, see Help file (F1)
Make sure you have selected correct COM ports for both Brew and Obex, as it is described in previous topic, and that you have your phone connected to a USB cable (DCA 540 or DCA 140).
If you still cannot connect, see if your phone isn't behaving very slowly. This is because it is reindexing MMC card, and it doesn't have time to comunicate with BMC. Wait till the phone has reindexed the MMC card (up to 30 minutes) and try to connect again.
If you still cannost connect, it is possible your phone is not among supported. For BREW should all Qualcomm based phones work, but OBEX is only available for some of them (SXG75, EF81, SL91 and possibly some others). If you have troubles with these phones or with Brew mode, contact me
You have to select a JAD/JAR/SDT file in the left window and press CTRL+I. For Java installation, you need a Jad file. If you don't have one, you may generate it thru the installation window. Then you just select wheter it is a game or app, click on Install and you are done. After copying finishes, you have to restart your phone for the installation to finish, but you don't have to, if you would like to install more themes/java.
There are a few possible explainations. Either the original JAD file is corrupted - in that case, make a new one in BMC and reinstall the Java. Or There is a bug in creating new JAD in BMC - in that case, try to use JadGen for creation new JAD and reinstall in BMC. Or the game simply is not suitable for your phone. Some games have some special requirements and the phone will not even let them install. In this case, you have no choice. But you may try to upload it to some site, and install it directly from phone's internet browser. That's the last option.
In main menu choose Phone > JAVA permitions > Games/Apps. There you choose the JAVA.ids file (the names are not the same, but similar as in phone) and press CTRL + J. There you may choose the permition or completely sign the JAVA to behave as trusted. Then you click on Write to phone.
The main difference is that in Brew you can see the entire File System of your phone, while in OBEX you only see what you can see in phone. Brew is a natural protocol for Qualcomm based phones, that is why it is much faster then Obex (you may see in on loading the directory contain). On the contrary, in OBEX you can send bigger packets of data - that is why it seems copying files in Obex is faster.
If you are deleting a file visible in phone - you HAVE TO delete it thru OBEX! The same goes for copying file to phone - you want it visible in phone? U HAVE TO use OBEX. Explaination is in the next topic.
Why is phone so slow? Why is copying files so slow? Why don't I sometimes see files on MMC, but I am sure they are here? Let me tell you why.
In the phone, there is a certain file under brew/shared/content called sql_content_db.sql. You will notice this file cannot be deleted. It is the most important file in the whole phone. Why? Well, simply because when you are browsing thru the phone's file system, in Obex or Phone, you are in fact just browsing thru this very file. This DB file contains names and addresses of all indexed file on both MMC and in Phone. So when you navigate your phone to File Explorer to MMC, you in fact aren't looking at your MMC, but into this file. Here is an example: you get a new MMC, copy some files to it thru card reader, because it is faster. Then you put it to the phone and.... nothing. Phone will be like jammed. Very slow, almost not responding. Then you notice a blinking icon of a memory card next to battery status. This means that the phone is going thru the MMC and creating the SQL file - names, locations, attributies etc. Sometimes some files are skipped and you don't see them cause they are not in the SQL file.
Now if you want to delete a file in phone, the phone will not just delete the file - it also updates the SQL file - and that takes a lot of time.
Another problem is with Brew protocol - in Brew you don't give a shit about some SQL file - you access directly the files in memory - that is why it is so fast. The problem is when you copy or delete files in phone's accessable memory (memory you can see in the phone) - because you access the memory directly, the phone will not update the SQL file - so if you delete a file in Brew, you will still be able to see it in Obex/Phone.
What to say about it? I wish there was a common FS as in EL71/S75...
Please note: This is just my expirience based on using and working with my SXG75. It may be different in your phone, especially in EF81v58, it has many changes so I cannot say
First take a look on a topic above, about the sql_content_db.sql. This file also contains attributies of all indexed files. It also stores whether the file is a part of M3U playlist. This means, when you open a playlist in internal player, the phone searches the mentioned DB file for files that are in this playlist. Phone doesn't read these files from a separated M3U file, even though there are such - they have no purpose. So adding M3U support to BMC would need to edit this DB file. You see, it is impossible to edit so big and elaborate file - only trying to understand the structe would take a long time. We were 2 on cracking the addressbook file, and there still were unknown anomalies we were unable to explain. Plus, cracking such important file would be dangerous - any mistake would result in possible loss of the files in phone - because there is no way how to make the phone reindex files in its memory, this is only possible for file on MMC. That's why BMC will never support creating/editing M3U playlists.