Unable to run on device | developer.brewmp.com Unable to run on device | developer.brewmp.com

Developer

Unable to run on device

Forums:

Hello

We are having problems getting our application to run on LG 9800. When we install the game, the game does show up in the Get it Now folder. The problem occurs when we try to launch the application. When we select the icon to launch the application, nothing happens. The screen just stays at the get it now directory. The application is run fine on 3.1 simulator (using Brew 3.1.2) and was porting from the brew 2.0 version.

Regards,
Phichakhom

try putting some DBGprintfs after Appinit function. from there must the application crashing.

try putting some DBGprintfs after Appinit function. from there must the application crashing.

Thanks for your reply skumar_rao.
It seem like my application does not get any event at all. Is there any specific change in .mak file from version 2->3?
Regard,
Phichakhom

Thanks for your reply skumar_rao.
It seem like my application does not get any event at all. Is there any specific change in .mak file from version 2->3?
Regard,
Phichakhom

No there is no change in .mak file only think you can check is it picking the BREW3 header not BREW 2.X header if you have installed more then one SDKs. else it will work as it is..

No there is no change in .mak file only think you can check is it picking the BREW3 header not BREW 2.X header if you have installed more then one SDKs. else it will work as it is..

skumar_rao wrote:No there is no change in .mak file only think you can check is it picking the BREW3 header not BREW 2.X header if you have installed more then one SDKs. else it will work as it is..
I have the same problem. Anybody found the solution?
Thank you.

skumar_rao wrote:No there is no change in .mak file only think you can check is it picking the BREW3 header not BREW 2.X header if you have installed more then one SDKs. else it will work as it is..
I have the same problem. Anybody found the solution?
Thank you.

mzichao wrote:I have the same problem. Anybody found the solution?
Thank you.
All my 1.1 compiled apps run fine in the 9800.

mzichao wrote:I have the same problem. Anybody found the solution?
Thank you.
All my 1.1 compiled apps run fine in the 9800.

jmiller2 wrote:All my 1.1 compiled apps run fine in the 9800.
1.1 ???
I have the same problem, in the phone the first code executed in the entry point of my application is
while(1); //DEAD_LOCK
and it doesn't freeze but stay in the game menu. So I conclude that control is never given to my application.
Is it possible that my sig file is not correct ?
Which tests are done before control is given to the application's entry point ?

jmiller2 wrote:All my 1.1 compiled apps run fine in the 9800.
1.1 ???
I have the same problem, in the phone the first code executed in the entry point of my application is
while(1); //DEAD_LOCK
and it doesn't freeze but stay in the game menu. So I conclude that control is never given to my application.
Is it possible that my sig file is not correct ?
Which tests are done before control is given to the application's entry point ?

franckspike wrote:1.1 ???
I have the same problem, in the phone the first code executed in the entry point of my application is
while(1); //DEAD_LOCK
and it doesn't freeze but stay in the game menu. So I conclude that control is never given to my application.
Is it possible that my sig file is not correct ?
Which tests are done before control is given to the application's entry point ?
Does this exact same build work on other devices?

franckspike wrote:1.1 ???
I have the same problem, in the phone the first code executed in the entry point of my application is
while(1); //DEAD_LOCK
and it doesn't freeze but stay in the game menu. So I conclude that control is never given to my application.
Is it possible that my sig file is not correct ?
Which tests are done before control is given to the application's entry point ?
Does this exact same build work on other devices?

Yes this exact same build (.mod) with exact same .mif and the proper sig file for the other device (vx7000) and it locks.
Would the vx9800 alert me if the sig file wasn't correct ?

Yes this exact same build (.mod) with exact same .mif and the proper sig file for the other device (vx7000) and it locks.
Would the vx9800 alert me if the sig file wasn't correct ?

No...the VZW GIN UI is pretty bad about squelching error message display. Try looking at the logger output, chances are excellent that it's a sig error of some sort.

No...the VZW GIN UI is pretty bad about squelching error message display. Try looking at the logger output, chances are excellent that it's a sig error of some sort.

in the logger: brewappmgr is started twice then it seems to start my app
and I get those lines (which i think are the relevant lines)
------------------
[.......]
App_SendStart(0)...
App Started...
WakeResume (BREW App Activated)
WakeStart Done...
#*p:ECode:102, Key:e035 <----------- It seems to be an error code (102)
AEEKey_RemovePressed: 0xe035 <--- The very last log line
--------------------
0xe035 is the brew keycode for "fire" (or enter, or ok) (must be the same in the OS).
Then this key press raised an error which code is 102.
if error code is hexadecimal:
[INDENT]AEEError.h:[/INDENT]
//
// File Error Codes
//
#define FILE_ERROR (0x100)
#define EFILEEXISTS (FILE_ERROR) // File exists
#define EFILENOEXISTS (FILE_ERROR+1) // File does not exist
#define EDIRNOTEMPTY (FILE_ERROR+2) // Directory not empty <-- this one
then
[INDENT]the error code would be EDIRNOTEMPTY (0x102) Directory not empty[/INDENT]
else
[INDENT](the error code is decimal 102 = 0x66)
brew error 0x66 doesn't exist, so it must be the hexadecimal case.[/INDENT]
endif
Why do I get such an error ???
Does that make any sense ?
Is this error defined in AEEError.h or it is defined some where else ?
Is it a brew error code ?

in the logger: brewappmgr is started twice then it seems to start my app
and I get those lines (which i think are the relevant lines)
------------------
[.......]
App_SendStart(0)...
App Started...
WakeResume (BREW App Activated)
WakeStart Done...
#*p:ECode:102, Key:e035 <----------- It seems to be an error code (102)
AEEKey_RemovePressed: 0xe035 <--- The very last log line
--------------------
0xe035 is the brew keycode for "fire" (or enter, or ok) (must be the same in the OS).
Then this key press raised an error which code is 102.
if error code is hexadecimal:
[INDENT]AEEError.h:[/INDENT]
//
// File Error Codes
//
#define FILE_ERROR (0x100)
#define EFILEEXISTS (FILE_ERROR) // File exists
#define EFILENOEXISTS (FILE_ERROR+1) // File does not exist
#define EDIRNOTEMPTY (FILE_ERROR+2) // Directory not empty <-- this one
then
[INDENT]the error code would be EDIRNOTEMPTY (0x102) Directory not empty[/INDENT]
else
[INDENT](the error code is decimal 102 = 0x66)
brew error 0x66 doesn't exist, so it must be the hexadecimal case.[/INDENT]
endif
Why do I get such an error ???
Does that make any sense ?
Is this error defined in AEEError.h or it is defined some where else ?
Is it a brew error code ?

Problem Resolved!
The sig file I was provided wasn't working, the phone's serial number used to create the signature wasn't the correct one.
So it seems that the phone doesn't alert of a signature file created with a bad serial number.

Problem Resolved!
The sig file I was provided wasn't working, the phone's serial number used to create the signature wasn't the correct one.
So it seems that the phone doesn't alert of a signature file created with a bad serial number.

Glad to see you solved the problem...ecode is actually event code, and I believe that corresponded to the EVT_KEY_RELEASE event.

Glad to see you solved the problem...ecode is actually event code, and I believe that corresponded to the EVT_KEY_RELEASE event.