Forums | developer.brewmp.com Forums | developer.brewmp.com

Developer

Forums

Forums:

Hi,

i have installed Brew 3.0.........i have problem in simulator.
i am able to view the image of my application on the simulator device but i am not able to run the application.
What may be the reason? please reply clearly

You are able to see the image because the simulator has found the mif file and is displaying the images from the mif.
As to why it will not run the application: you need to provide more information. What does the output window show?
Look at this thread:
http://brewforums.qualcomm.com/showthread.php?threadid=2696

You are able to see the image because the simulator has found the mif file and is displaying the images from the mif.
As to why it will not run the application: you need to provide more information. What does the output window show?
Look at this thread:
http://brewforums.qualcomm.com/showthread.php?threadid=2696

Welcome to the wonderful world of non-functional Brew 3.0 tools.

Welcome to the wonderful world of non-functional Brew 3.0 tools.

My advice: Give up on 3.0 and hope to God Qualcomm doesn't produce crap like this again. It has now screwed up my 2.1 settings and I have to re-install the SDK. Thanks Qualcomm!!

My advice: Give up on 3.0 and hope to God Qualcomm doesn't produce crap like this again. It has now screwed up my 2.1 settings and I have to re-install the SDK. Thanks Qualcomm!!

Earlier I installed beta version in a different system and it worked to certain extent with known issues.
Looks like the public release version has lots of issues. It is recommended that you don't install BREW 3.0 version in the same system where you have working SDK version.
ruben

Earlier I installed beta version in a different system and it worked to certain extent with known issues.
Looks like the public release version has lots of issues. It is recommended that you don't install BREW 3.0 version in the same system where you have working SDK version.
ruben

Quote:Originally posted by ruben
Earlier I installed beta version in a different system and it worked to certain extent with known issues.
Looks like the public release version has lots of issues. It is recommended that you don't install BREW 3.0 version in the same system where you have working SDK version.
ruben
Yeah don't install it with any working SDK for sure. This has officially cost me 2 days of downtime thanks to 3.0

Quote:Originally posted by ruben
Earlier I installed beta version in a different system and it worked to certain extent with known issues.
Looks like the public release version has lots of issues. It is recommended that you don't install BREW 3.0 version in the same system where you have working SDK version.
ruben
Yeah don't install it with any working SDK for sure. This has officially cost me 2 days of downtime thanks to 3.0

I have all existing versions of the SDK on my machine and have not encountered any issues. What issues are you encountering?
During SDK installation you will be prompted as to whether you want to change the environment variable BREWDIR to point to the new installation. BREWDIR controls BREW path information, and can be edited to match the SDK that you wish to develop your application with.
All SDK Known Issues are available on the BREW SDK download page. This Known Issues list is updated daily, so please check back often.
Devi Krishnan
BREW Support

I have all existing versions of the SDK on my machine and have not encountered any issues. What issues are you encountering?
During SDK installation you will be prompted as to whether you want to change the environment variable BREWDIR to point to the new installation. BREWDIR controls BREW path information, and can be edited to match the SDK that you wish to develop your application with.
All SDK Known Issues are available on the BREW SDK download page. This Known Issues list is updated daily, so please check back often.
Devi Krishnan
BREW Support

Could you guys please supply us with some sort of a contact point/email where we could submit bug reports for the tool sets, please? I don't really want to put up full bug reports for all kinds of tools on a public forum, as I feel it would be detrimental to Qualcomm's reputation. However, I would be more than happy to submit detailed bug reports whenever I encounter problems with the tools, as long as I know these reports go to the right people and don't disappear somewhere in the Nirvhana on Morehouse Drive. :)
Also, while a known-issues list is a nice thing to have, it's not really what is needed. What IS needed are updates, patches and fixes for those problems.

Could you guys please supply us with some sort of a contact point/email where we could submit bug reports for the tool sets, please? I don't really want to put up full bug reports for all kinds of tools on a public forum, as I feel it would be detrimental to Qualcomm's reputation. However, I would be more than happy to submit detailed bug reports whenever I encounter problems with the tools, as long as I know these reports go to the right people and don't disappear somewhere in the Nirvhana on Morehouse Drive. :)
Also, while a known-issues list is a nice thing to have, it's not really what is needed. What IS needed are updates, patches and fixes for those problems.

Please email your bug reports/suggestions for product improvement to eval(unescape('%64%6f%63%75%6d%65%6e%74%2e%77%72%69%74%65%28%27%3c%61%20%68%72%65%66%3d%22%6d%61%69%6c%74%6f%3a%62%72%65%77%2d%73%75%70%70%6f%72%74%40%71%75%61%6c%63%6f%6d%6d%2e%63%6f%6d%22%20%63%6c%61%73%73%3d%22%62%62%2d%65%6d%61%69%6c%22%3e%62%72%65%77%2d%73%75%70%70%6f%72%74%40%71%75%61%6c%63%6f%6d%6d%2e%63%6f%6d%3c%2f%61%3e%27%29%3b')). The BREW Support team will create Change Requests after validating the issue.
The BREW team values developer feedback on the BREW SDK, tools, and website and strives to incorporate feedback into future releases.
Devi Krishnan
BREW Support

Please email your bug reports/suggestions for product improvement to eval(unescape('%64%6f%63%75%6d%65%6e%74%2e%77%72%69%74%65%28%27%3c%61%20%68%72%65%66%3d%22%6d%61%69%6c%74%6f%3a%62%72%65%77%2d%73%75%70%70%6f%72%74%40%71%75%61%6c%63%6f%6d%6d%2e%63%6f%6d%22%20%63%6c%61%73%73%3d%22%62%62%2d%65%6d%61%69%6c%22%3e%62%72%65%77%2d%73%75%70%70%6f%72%74%40%71%75%61%6c%63%6f%6d%6d%2e%63%6f%6d%3c%2f%61%3e%27%29%3b')). The BREW Support team will create Change Requests after validating the issue.
The BREW team values developer feedback on the BREW SDK, tools, and website and strives to incorporate feedback into future releases.
Devi Krishnan
BREW Support

Concerning the initial question.
I have also experienced some problems of this type: the app's name and image apeared, but it did not execute. What was my problem: the dll file must be in a directory with the same name (ex: app.dll in .\app). The mif file must exist in the .\ directory, and you must point the Applet dir to that directory. For the examples app, point the Applet Dir to ....\examples.
I downloaded some BREW apps that had the mif file in the same dir with the dll. I guess that in earlier versions of BREW Simulator, this configuration worked (mif and dll in the same dir), but for sure that in 3.0 it does not work like this.
Maybe this was the cause of your trouble.
After I read this thread, I regret having downloaded the 3.0 suite before asking for advice.

Concerning the initial question.
I have also experienced some problems of this type: the app's name and image apeared, but it did not execute. What was my problem: the dll file must be in a directory with the same name (ex: app.dll in .\app). The mif file must exist in the .\ directory, and you must point the Applet dir to that directory. For the examples app, point the Applet Dir to ....\examples.
I downloaded some BREW apps that had the mif file in the same dir with the dll. I guess that in earlier versions of BREW Simulator, this configuration worked (mif and dll in the same dir), but for sure that in 3.0 it does not work like this.
Maybe this was the cause of your trouble.
After I read this thread, I regret having downloaded the 3.0 suite before asking for advice.

Interesting. I haven't put the mif in the same directory as the dll, so i never encountered that.
But you know what would solve a lot of confusion?
If the damn thing would just print an error message saying it can't find the dll!!!

Interesting. I haven't put the mif in the same directory as the dll, so i never encountered that.
But you know what would solve a lot of confusion?
If the damn thing would just print an error message saying it can't find the dll!!!

Quote:Originally posted by cristis1
I downloaded some BREW apps that had the mif file in the same dir with the dll. I guess that in earlier versions of BREW Simulator, this configuration worked (mif and dll in the same dir), but for sure that in 3.0 it does not work like this.
I had no problem running applications with the mif file in the same directory as the dll. Make sure that you have the "Mif directory different from applet directory" option set to 'Yes', and that you have specified the applet and mif directory correctly.

Quote:Originally posted by cristis1
I downloaded some BREW apps that had the mif file in the same dir with the dll. I guess that in earlier versions of BREW Simulator, this configuration worked (mif and dll in the same dir), but for sure that in 3.0 it does not work like this.
I had no problem running applications with the mif file in the same directory as the dll. Make sure that you have the "Mif directory different from applet directory" option set to 'Yes', and that you have specified the applet and mif directory correctly.

Another thing to verify is that you have actually clicked the Apply button at the bottom of the properties tab. If you just changed one of the directories you'll need to click it twice, since the first click will just make the button active.

Another thing to verify is that you have actually clicked the Apply button at the bottom of the properties tab. If you just changed one of the directories you'll need to click it twice, since the first click will just make the button active.

Quote:Originally posted by mohlendo
I had no problem running applications with the mif file in the same directory as the dll. Make sure that you have the "Mif directory different from applet directory" option set to 'Yes' [...]You're right, and no offense, but when you think about that, it's really funny! :p
The mif and the dll are in the same directory, but you have to say "Yes" -- the "Mif directory different from applet directory".
Doesn't that strike anyone as ironic?
Okay... I'll shut up now.
--t

Quote:Originally posted by mohlendo
I had no problem running applications with the mif file in the same directory as the dll. Make sure that you have the "Mif directory different from applet directory" option set to 'Yes' [...]You're right, and no offense, but when you think about that, it's really funny! :p
The mif and the dll are in the same directory, but you have to say "Yes" -- the "Mif directory different from applet directory".
Doesn't that strike anyone as ironic?
Okay... I'll shut up now.
--t

Quote:Originally posted by tom
Interesting. I haven't put the mif in the same directory as the dll, so i never encountered that.
But you know what would [B]solve a lot of confusion?
If the damn thing would just print an error message saying it can't find the dll!!! [/B]
We are planning a new release and plan to include some of the suggestions from developers from the forum.
This release will be fixing the issue where it does not display a message when it can't see the DLL.

Quote:Originally posted by tom
Interesting. I haven't put the mif in the same directory as the dll, so i never encountered that.
But you know what would [B]solve a lot of confusion?
If the damn thing would just print an error message saying it can't find the dll!!! [/B]
We are planning a new release and plan to include some of the suggestions from developers from the forum.
This release will be fixing the issue where it does not display a message when it can't see the DLL.

Thanks Abhi, you rock!

Thanks Abhi, you rock!

I have tried it, and it still doesn't work. I have set the mif directory and the applet directory identically, I clicked apply after changing each field, and I can see the data in the mif, but no app is loaded when clicking.
The 2.1 Simulator had this kind of problems too? I'm planing to moving to the 2.1 SDK, and I wonder if it is a wise decission.

I have tried it, and it still doesn't work. I have set the mif directory and the applet directory identically, I clicked apply after changing each field, and I can see the data in the mif, but no app is loaded when clicking.
The 2.1 Simulator had this kind of problems too? I'm planing to moving to the 2.1 SDK, and I wonder if it is a wise decission.

Quote:Originally posted by cristis1
I have tried it, and it still doesn't work. I have set the mif directory and the applet directory identicallyFor files in a directory structure like this:
C:\some_path\app_name\app_name.mif
C:\some_path\app_name\app_name.dllYou need this:
Applet Directory | C:\some_path
MIF directory different from App | yes
MIF Directory | C:\some_path\app_name

Quote:Originally posted by cristis1
I have tried it, and it still doesn't work. I have set the mif directory and the applet directory identicallyFor files in a directory structure like this:
C:\some_path\app_name\app_name.mif
C:\some_path\app_name\app_name.dllYou need this:
Applet Directory | C:\some_path
MIF directory different from App | yes
MIF Directory | C:\some_path\app_name

Now I get the trick; Maybe in the next releases they will be more explicit in this field.
Thanks.

Now I get the trick; Maybe in the next releases they will be more explicit in this field.
Thanks.

Quote:Originally posted by mohlendo
Another thing to verify is that you have actually clicked the Apply button at the bottom of the properties tab. If you just changed one of the directories you'll need to click it twice, since the first click will just make the button active. I wonder if this is why I was having problems with it earlier... I don't remember pressing the apply button at all. However, I would close and reopen the simulator and it would keep the settings that I used, so I don't think that was it.

Quote:Originally posted by mohlendo
Another thing to verify is that you have actually clicked the Apply button at the bottom of the properties tab. If you just changed one of the directories you'll need to click it twice, since the first click will just make the button active. I wonder if this is why I was having problems with it earlier... I don't remember pressing the apply button at all. However, I would close and reopen the simulator and it would keep the settings that I used, so I don't think that was it.