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

Developer

Forums

Forums:

Anyone using it regulary, i just tried it for the first time, it crashed in different ways while using different features, wondering if i have something incompatible or its the norm

I used it couple of times. One of the known issue is, when you change device skin, for the first time it would crash but in the subsequent run it is okay.
ruben

I used it couple of times. One of the known issue is, when you change device skin, for the first time it would crash but in the subsequent run it is okay.
ruben

yeah thats one of the ones i saw, some were in running apps though

yeah thats one of the ones i saw, some were in running apps though

I can't get it to run properly either. It appears as if it doesn't find my applications' BAR files even though I have pointed the directories etc correctly.

I can't get it to run properly either. It appears as if it doesn't find my applications' BAR files even though I have pointed the directories etc correctly.

So, did anyone get it to run properly?

So, did anyone get it to run properly?

i'm presuming it sjust us, and everyone is off having agreat time with it.
i notice that the 3.0 brew_res tool isnt backwards compatible as well, theres no save to bri option i could see, though i did only load it once, just the once...
ps i had to lend my 310 to b.h. waiting for back ..... 690 do ?

i'm presuming it sjust us, and everyone is off having agreat time with it.
i notice that the 3.0 brew_res tool isnt backwards compatible as well, theres no save to bri option i could see, though i did only load it once, just the once...
ps i had to lend my 310 to b.h. waiting for back ..... 690 do ?

Never mind, I have already re-submitted. I'm sure it was a glitch.

Never mind, I have already re-submitted. I'm sure it was a glitch.

It seems to run further for you guys than for me.
I have my app directories set up so the 2.0/2.1 emulators work fine, but the 3.0 simulator does nothing when i select the app.
Well, this is what it prints in the output window:
#*p:ECode:101, Key:e035
#*p:ECode:100, Key:e035
#*gSU=16809984
#*gCL=16809984
#*g*C=101402c:3
#*g*C=101402d:3
#*g*C=101402e:3
#*gST=16866007
#*p:ECode:102, Key:e035and that's it. I tried remaking the mif so it was a v3.0 mif.
I suppose it's best just to stick to the 2.1 emulator?
--t

It seems to run further for you guys than for me.
I have my app directories set up so the 2.0/2.1 emulators work fine, but the 3.0 simulator does nothing when i select the app.
Well, this is what it prints in the output window:
#*p:ECode:101, Key:e035
#*p:ECode:100, Key:e035
#*gSU=16809984
#*gCL=16809984
#*g*C=101402c:3
#*g*C=101402d:3
#*g*C=101402e:3
#*gST=16866007
#*p:ECode:102, Key:e035and that's it. I tried remaking the mif so it was a v3.0 mif.
I suppose it's best just to stick to the 2.1 emulator?
--t

i gave up with it, i mentioned it to qualcomm this morning, if anyone else talks directly to them, it might be worth mentioning it as well.

i gave up with it, i mentioned it to qualcomm this morning, if anyone else talks directly to them, it might be worth mentioning it as well.

Yeah. I gave up too. I simply don't have the time to deal with tools that don't work or trying to get them to work. I expect them to do what they're supposed to do when I install them, which is clearly not the case here.

Yeah. I gave up too. I simply don't have the time to deal with tools that don't work or trying to get them to work. I expect them to do what they're supposed to do when I install them, which is clearly not the case here.

Have any of you tried setting breakpoints in your apps to see if any of your code gets executed? The log above seems to indicate that the the app manager successfully created an instance of the app, and if that is the case, it is very likely that the app's HandleEvent method is being called with EVT_APP_START.

Have any of you tried setting breakpoints in your apps to see if any of your code gets executed? The log above seems to indicate that the the app manager successfully created an instance of the app, and if that is the case, it is very likely that the app's HandleEvent method is being called with EVT_APP_START.

Whoa, this is interesting...
I blew away the Visual Studio v6.0 .ncb and .opt files, then re-setup my project settings, and the simulator actually works now. The app runs and everything works as usual.
I didn't rebuild. That doesn't make sense. I don't know why that would have fixed the problem. I must have had an incorrect setting in the simulator.
Anyway... thanks guys.
Now my question is: Is there anyway to make that properties sheet hidden upon startup? I have to close it every time I run the simulator. There don't seem to be any settings for it in the menus or in the Windows registry.
--t

Whoa, this is interesting...
I blew away the Visual Studio v6.0 .ncb and .opt files, then re-setup my project settings, and the simulator actually works now. The app runs and everything works as usual.
I didn't rebuild. That doesn't make sense. I don't know why that would have fixed the problem. I must have had an incorrect setting in the simulator.
Anyway... thanks guys.
Now my question is: Is there anyway to make that properties sheet hidden upon startup? I have to close it every time I run the simulator. There don't seem to be any settings for it in the menus or in the Windows registry.
--t

i think i ran it 3 times, it crashed 3 times, and i uninstalled it and went back to 2.1

i think i ran it 3 times, it crashed 3 times, and i uninstalled it and went back to 2.1

Quote:Originally posted by Dragon
Yeah. I gave up too. I simply don't have the time to deal with tools that don't work or trying to get them to work. I expect them to do what they're supposed to do when I install them, which is clearly not the case here.
Exactly. We shouldn't have to spend time tweaking after an install. It should just work. Going back to 2.1. :rolleyes:

Quote:Originally posted by Dragon
Yeah. I gave up too. I simply don't have the time to deal with tools that don't work or trying to get them to work. I expect them to do what they're supposed to do when I install them, which is clearly not the case here.
Exactly. We shouldn't have to spend time tweaking after an install. It should just work. Going back to 2.1. :rolleyes:

Quote:Originally posted by ruben
I used it couple of times. One of the known issue is, when you change device skin, for the first time it would crash but in the subsequent run it is okay.
ruben
Which skin did you try this with? Was it with one of the skins provided with the SDK?

Quote:Originally posted by ruben
I used it couple of times. One of the known issue is, when you change device skin, for the first time it would crash but in the subsequent run it is okay.
ruben
Which skin did you try this with? Was it with one of the skins provided with the SDK?

yep that happened to dragon and myself i believe, i can't remember which skin it was, but it crashed after trying to change it from the default one IIRC

yep that happened to dragon and myself i believe, i can't remember which skin it was, but it crashed after trying to change it from the default one IIRC

Yes I tried with one the skin supplied with SDK, however at this point I don't recall which one I used. I would let you know if I encounter it again.
ruben

Yes I tried with one the skin supplied with SDK, however at this point I don't recall which one I used. I would let you know if I encounter it again.
ruben

Yes it happened with one of the provided skins. Somehow I got that resolved - don't remember how - just to stumble into the next problem, whic hwas that I was unable to load data out of a BAR file because the emulator evidently never found my BAR file.

Yes it happened with one of the provided skins. Somehow I got that resolved - don't remember how - just to stumble into the next problem, whic hwas that I was unable to load data out of a BAR file because the emulator evidently never found my BAR file.

I've reverted to using the 2.1 emulator as well.
It's a pain to have that properties sheet taking up so much screen space. Even if you shrink it instead of closing it, then the next time the simulator comes up the properties sheet is full size again.
Even without crashing, the UI design, or lack of, basically makes it unusable as far as i'm concerned.

I've reverted to using the 2.1 emulator as well.
It's a pain to have that properties sheet taking up so much screen space. Even if you shrink it instead of closing it, then the next time the simulator comes up the properties sheet is full size again.
Even without crashing, the UI design, or lack of, basically makes it unusable as far as i'm concerned.

Quote:Originally posted by tom
It seems to run further for you guys than for me.
I have my app directories set up so the 2.0/2.1 emulators work fine, but the 3.0 simulator does nothing when i select the app.
Well, this is what it prints in the output window:
#*p:ECode:101, Key:e035
#*p:ECode:100, Key:e035
#*gSU=16809984
#*gCL=16809984
#*g*C=101402c:3
#*g*C=101402d:3
#*g*C=101402e:3
#*gST=16866007
#*p:ECode:102, Key:e035and that's it. I tried remaking the mif so it was a v3.0 mif.
I suppose it's best just to stick to the 2.1 emulator?
--t
It looks like the Applet directory that you selected is incorrect. Please make sure that the APplet directory points to one directory above the actual app directory. For e.g. BREW30/Examples and NOT BREW30/Examples/helloworld

Quote:Originally posted by tom
It seems to run further for you guys than for me.
I have my app directories set up so the 2.0/2.1 emulators work fine, but the 3.0 simulator does nothing when i select the app.
Well, this is what it prints in the output window:
#*p:ECode:101, Key:e035
#*p:ECode:100, Key:e035
#*gSU=16809984
#*gCL=16809984
#*g*C=101402c:3
#*g*C=101402d:3
#*g*C=101402e:3
#*gST=16866007
#*p:ECode:102, Key:e035and that's it. I tried remaking the mif so it was a v3.0 mif.
I suppose it's best just to stick to the 2.1 emulator?
--t
It looks like the Applet directory that you selected is incorrect. Please make sure that the APplet directory points to one directory above the actual app directory. For e.g. BREW30/Examples and NOT BREW30/Examples/helloworld

yep i agree with tom, even if it did work the UI isn't very useful, its rare i ever have to change most of that stuff, those college interns have to have something to do though, right ;) ?
It'd be nice to be able to specify skin, heap size/type and mod to load and execute on the command line, i don't know if thats been added to 3, or possibly even 2.

yep i agree with tom, even if it did work the UI isn't very useful, its rare i ever have to change most of that stuff, those college interns have to have something to do though, right ;) ?
It'd be nice to be able to specify skin, heap size/type and mod to load and execute on the command line, i don't know if thats been added to 3, or possibly even 2.

Quote:Originally posted by Abhi
It looks like the Applet directory that you selected is incorrect. Please make sure that the APplet directory points to one directory above the actual app directory. For e.g. BREW30/Examples and NOT BREW30/Examples/helloworld Sorry, but that's not quite possible. I could see the applet in the brewappmgr, and hit the OK button. How else would the applet show up if i hadn't selected the proper directory, i.e. the mif is one directory above the actual app directory. The app directory does not have a mif in it.
The fact that it happens to so many other people should tell you one of two things:
(1) the design is so bad that all of us experienced brew developers made the same mistake, or
(2) it is a bug in the 3.0 simulator.

Quote:Originally posted by Abhi
It looks like the Applet directory that you selected is incorrect. Please make sure that the APplet directory points to one directory above the actual app directory. For e.g. BREW30/Examples and NOT BREW30/Examples/helloworld Sorry, but that's not quite possible. I could see the applet in the brewappmgr, and hit the OK button. How else would the applet show up if i hadn't selected the proper directory, i.e. the mif is one directory above the actual app directory. The app directory does not have a mif in it.
The fact that it happens to so many other people should tell you one of two things:
(1) the design is so bad that all of us experienced brew developers made the same mistake, or
(2) it is a bug in the 3.0 simulator.

Maybe I wasn't clear in the earlier post.
The Simulator has 2 settings: App directory and MIF directory.
The Field for App directory conatains the path to a directory one level above the App directory.
The field for the MIF directory should contain the path to the directory where the MIF resides.
Could you please confirm that you have set the app directory as expected? I have not been able to reproduce the problem that you are facing.

Maybe I wasn't clear in the earlier post.
The Simulator has 2 settings: App directory and MIF directory.
The Field for App directory conatains the path to a directory one level above the App directory.
The field for the MIF directory should contain the path to the directory where the MIF resides.
Could you please confirm that you have set the app directory as expected? I have not been able to reproduce the problem that you are facing.

Thank you Abhi, but I think you missed my posting that says I don't have a problem running the simulator anymore, but instead I don't like the user interface.
However, if you want to know about the initial problem I had:
The first several times I tried running the simulator (during a few different sessions over the past couple months), it kept happening, and I tried several settings on different apps.
You must understand that the directory structure worked with the 2.0 emulator:
D:\BREWdev\Client1\game1.mif
D:\BREWdev\Client1\game1\game1.dll
At first, the settings were:
Applet Directory: D:\BREWdev\Client1
MIF directory: No
Mif Directory: D:\BREWdev\Client1
But I didn't like using that properties sheet. I did try it, but when it didn't work, I closed the properties sheet and used the method that worked on the 2.0 emulator.
That is, under Tools | Settings, the Specify MIF Directory was unchecked, and I selected the directory which contained the mif from the File menu using Change Applet Dir... I did this several times. I could see the applet in the brewappmgr, so I knew I had the right directory.
But it doesn't really matter now, because it has started working for whatever reason, and now I can't reproduce the problem either.
Thanks anyway...
--t

Thank you Abhi, but I think you missed my posting that says I don't have a problem running the simulator anymore, but instead I don't like the user interface.
However, if you want to know about the initial problem I had:
The first several times I tried running the simulator (during a few different sessions over the past couple months), it kept happening, and I tried several settings on different apps.
You must understand that the directory structure worked with the 2.0 emulator:
D:\BREWdev\Client1\game1.mif
D:\BREWdev\Client1\game1\game1.dll
At first, the settings were:
Applet Directory: D:\BREWdev\Client1
MIF directory: No
Mif Directory: D:\BREWdev\Client1
But I didn't like using that properties sheet. I did try it, but when it didn't work, I closed the properties sheet and used the method that worked on the 2.0 emulator.
That is, under Tools | Settings, the Specify MIF Directory was unchecked, and I selected the directory which contained the mif from the File menu using Change Applet Dir... I did this several times. I could see the applet in the brewappmgr, so I knew I had the right directory.
But it doesn't really matter now, because it has started working for whatever reason, and now I can't reproduce the problem either.
Thanks anyway...
--t

Quote:
I could see the applet in the brewappmgr, so I knew I had the right directory.Now that I think about it, I did notice something odd about that. When the applet was in the brewappmgr, it did not have the proper icon. It had a different image there, but it did have the app name. It was as if it found the mif file but could not get the icon image out of the mif.
Later, when it started working, it was showing the icon image properly.
--t

Quote:
I could see the applet in the brewappmgr, so I knew I had the right directory.Now that I think about it, I did notice something odd about that. When the applet was in the brewappmgr, it did not have the proper icon. It had a different image there, but it did have the app name. It was as if it found the mif file but could not get the icon image out of the mif.
Later, when it started working, it was showing the icon image properly.
--t

As I stated earlier, the log posted by Tom indicates that the app with class ID 16866007 was constructed successfully. (CreateInstance on that class ID succeeded, which means the app's DLL must have been found.) There are three CreateInstance failures indicated in the log, but these class IDs correspond to some fonts that IDisplay tries to instantiate that are not present on the simulator. These errors are normal and are not harmful.
It would be very helpful if those of you who are experiencing problems with the 3.0 Simulator would step through your code in the debugger and determine what code in your application is being executed, and whether any calls into BREW are failing.
If the problem is file access, like what Dragon reports, I would guess it is because the file being accessed is not named with all lowercase letters on the file system. This is the way it has always worked on devices, but not on the simulator until now.

As I stated earlier, the log posted by Tom indicates that the app with class ID 16866007 was constructed successfully. (CreateInstance on that class ID succeeded, which means the app's DLL must have been found.) There are three CreateInstance failures indicated in the log, but these class IDs correspond to some fonts that IDisplay tries to instantiate that are not present on the simulator. These errors are normal and are not harmful.
It would be very helpful if those of you who are experiencing problems with the 3.0 Simulator would step through your code in the debugger and determine what code in your application is being executed, and whether any calls into BREW are failing.
If the problem is file access, like what Dragon reports, I would guess it is because the file being accessed is not named with all lowercase letters on the file system. This is the way it has always worked on devices, but not on the simulator until now.

Thanks Mark. Next time I have a problem I'll put a breakpoint at the beginning of the app.
I always lowercase any file that goes onto the handset. I know Apploader automatically lowercases them, but I lowercase the file on Windows anyway because if you submit them with uppercase letters then the test submission process fails.
BTW, the app worked fine on the 2.0 emulator. I wouldn't touch anything about the app, but when i launched the 3.0 simulator it wouldn't work. Usually I get a whole bunch of DBGPRINTF logging in the output window. I have a lot of logging that starts up just at the beginning of the app, so something in the simulator was failing before any file operations were attempted.
--t

Thanks Mark. Next time I have a problem I'll put a breakpoint at the beginning of the app.
I always lowercase any file that goes onto the handset. I know Apploader automatically lowercases them, but I lowercase the file on Windows anyway because if you submit them with uppercase letters then the test submission process fails.
BTW, the app worked fine on the 2.0 emulator. I wouldn't touch anything about the app, but when i launched the 3.0 simulator it wouldn't work. Usually I get a whole bunch of DBGPRINTF logging in the output window. I have a lot of logging that starts up just at the beginning of the app, so something in the simulator was failing before any file operations were attempted.
--t

Just a quick note that my 3.0 simulator is miraculously working all of a sudden! I did nothing. Just ran a test-program that Abhi sent me and all of a sudden all my apps were working on it.
No, the testapp he sent me did not do anything, it was a simple bitmap display. :)
Very strange, but at least it's working now. Let's see if I will get used to the interface and see any real noticeable benefits over the 2.0 emu, especially since so far I have not seen an device-specific emulator image updates that would accommodate the new features.

Just a quick note that my 3.0 simulator is miraculously working all of a sudden! I did nothing. Just ran a test-program that Abhi sent me and all of a sudden all my apps were working on it.
No, the testapp he sent me did not do anything, it was a simple bitmap display. :)
Very strange, but at least it's working now. Let's see if I will get used to the interface and see any real noticeable benefits over the 2.0 emu, especially since so far I have not seen an device-specific emulator image updates that would accommodate the new features.

if you can specify the skin or mod to load and execute, i'd update ,otherwise i'll wait for you to beta test it :)

if you can specify the skin or mod to load and execute, i'd update ,otherwise i'll wait for you to beta test it :)

I had some problems as well when I made the switch from 2.0 to 3.0. I fixed it by reinstalling the SDK 3.0 WITHOUT core files..... just the device files, simulator, and documentation.
Hope that helps,
Jin

I had some problems as well when I made the switch from 2.0 to 3.0. I fixed it by reinstalling the SDK 3.0 WITHOUT core files..... just the device files, simulator, and documentation.
Hope that helps,
Jin