Are all 3.x phone test enableed by default? | developer.brewmp.com Are all 3.x phone test enableed by default? | developer.brewmp.com

Developer

Are all 3.x phone test enableed by default?

Forums:

Some one told me:
All 3.x phone are test enableed by default.
Who use these handset?
Would u confirm it?

thx.

There is no test enable bit in 3.x. If you have a test sig, you can run the application.

There is no test enable bit in 3.x. If you have a test sig, you can run the application.

I think mohlendo 's question is: if someone gets a new BREW SDK 3.x handset, can he load BREW application into the handset directly? Or he need enable the handset 's test mode?

I think mohlendo 's question is: if someone gets a new BREW SDK 3.x handset, can he load BREW application into the handset directly? Or he need enable the handset 's test mode?

You don't need to "test-enable" the device because there is no test enable bit. All you need is a test sig generated from the sig generator and you can cable-load it to any 3.x device right out of the box.

You don't need to "test-enable" the device because there is no test enable bit. All you need is a test sig generated from the sig generator and you can cable-load it to any 3.x device right out of the box.

Sounds good, this kind of handset are what I need.

Sounds good, this kind of handset are what I need.

I have got the VX9800 & Moto V3c.
I downloaded the app to vx9800 with cable, and the app can work well.
I can also download app to Moto V3c with cable, but I can NOT find the app logo in brew app manager screen. In fact the app and MIF save in the handset.
what's problem?

I have got the VX9800 & Moto V3c.
I downloaded the app to vx9800 with cable, and the app can work well.
I can also download app to Moto V3c with cable, but I can NOT find the app logo in brew app manager screen. In fact the app and MIF save in the handset.
what's problem?

Hi
I load Nokia 6315i (BREW 3.x) and I could not find apps on the handset but I can see all my app files from the BREW app loader. (Can someone help me with this?)
:confused:

Hi
I load Nokia 6315i (BREW 3.x) and I could not find apps on the handset but I can see all my app files from the BREW app loader. (Can someone help me with this?)
:confused:

i have the same problem with my 6315i.
Did anyone find out how to start the applications?

i have the same problem with my 6315i.
Did anyone find out how to start the applications?

I thought I was crazy, but good (unfortunately) to hear others have the same problem......Maybe Qualcomm will shed some light on this.
My Device is a Samsung SCH-U420 (Brew 3.1.4)
Very Frustrating!

I thought I was crazy, but good (unfortunately) to hear others have the same problem......Maybe Qualcomm will shed some light on this.
My Device is a Samsung SCH-U420 (Brew 3.1.4)
Very Frustrating!

I dont know about other devices.
But i was informed that the Nokia 6315i needs to be test enabled even if it's a 3.x handset. We have sent back ours to qualcomm and are waiting to get them back to see if it works.

I dont know about other devices.
But i was informed that the Nokia 6315i needs to be test enabled even if it's a 3.x handset. We have sent back ours to qualcomm and are waiting to get them back to see if it works.

Per Max:
You don't need to "test-enable" the device because there is no test enable bit. All you need is a test sig generated from the sig generator and you can cable-load it to any 3.x device right out of the box.
__________________
Max
BREW Support
Hmmmm - I'm really confused now.............But thanks for the heads up!

Per Max:
You don't need to "test-enable" the device because there is no test enable bit. All you need is a test sig generated from the sig generator and you can cable-load it to any 3.x device right out of the box.
__________________
Max
BREW Support
Hmmmm - I'm really confused now.............But thanks for the heads up!

Havn't used the 6315 yet, but on the V3C you can find your cable loaded apps in the "Get Going" option in the Verizon interface (assuming you have a verizon v3c that is).
It doesn't really suprise me that the 6315 is different than all the other BREW 3.x phones though. Nokia always manages to do it different somehow. One thing to double check is that the 6315 is really a BREW 3.x device. If not, it will still need to be test enabled for sure.

Havn't used the 6315 yet, but on the V3C you can find your cable loaded apps in the "Get Going" option in the Verizon interface (assuming you have a verizon v3c that is).
It doesn't really suprise me that the 6315 is different than all the other BREW 3.x phones though. Nokia always manages to do it different somehow. One thing to double check is that the 6315 is really a BREW 3.x device. If not, it will still need to be test enabled for sure.

I have the same problem with LG vx 8300. This phone has brew 3.1.4 so it mast be test enabled, but when I upload mod, mif file and test sig generated on https://brewx.qualcomm.com/testsig/testsig.jsp
my application doest appear in phone menu.
May be some one find the solution?
To: mohlendo – may be there are some special procedure?

I have the same problem with LG vx 8300. This phone has brew 3.1.4 so it mast be test enabled, but when I upload mod, mif file and test sig generated on https://brewx.qualcomm.com/testsig/testsig.jsp
my application doest appear in phone menu.
May be some one find the solution?
To: mohlendo – may be there are some special procedure?

For your VX8300 problem - you must be having a bad signature file. I worked with VX8300 pre-production handset and it had only IMEID on the back of the handset. It didn't have any HEX ESN. I generated signature file with the IMEID. Also suffix 0 (Zero) for the IMEID and make sure that the length of the IMEID is 15 digits.

For your VX8300 problem - you must be having a bad signature file. I worked with VX8300 pre-production handset and it had only IMEID on the back of the handset. It didn't have any HEX ESN. I generated signature file with the IMEID. Also suffix 0 (Zero) for the IMEID and make sure that the length of the IMEID is 15 digits.

The Nokia 6315i needed to have an internal setting changed to fully test enable it (ie, see the apps on the handset). I emailed QIS and received the proper keypresses to initiate the changes, but apparently it's only available to Authenticated Developers.

The Nokia 6315i needed to have an internal setting changed to fully test enable it (ie, see the apps on the handset). I emailed QIS and received the proper keypresses to initiate the changes, but apparently it's only available to Authenticated Developers.

xgogo wrote:For your VX8300 problem - you must be having a bad signature file. I worked with VX8300 pre-production handset and it had only IMEID on the back of the handset. It didn't have any HEX ESN. I generated signature file with the IMEID. Also suffix 0 (Zero) for the IMEID and make sure that the length of the IMEID is 15 digits.
Thanks for the answer.
But on my VX8300 under the battery only ESN HEX code, no MEID and no IMEI. May be there any possibility of obtaining phone MEID or IMEI from phone service menu?

xgogo wrote:For your VX8300 problem - you must be having a bad signature file. I worked with VX8300 pre-production handset and it had only IMEID on the back of the handset. It didn't have any HEX ESN. I generated signature file with the IMEID. Also suffix 0 (Zero) for the IMEID and make sure that the length of the IMEID is 15 digits.
Thanks for the answer.
But on my VX8300 under the battery only ESN HEX code, no MEID and no IMEI. May be there any possibility of obtaining phone MEID or IMEI from phone service menu?

rbenhardt wrote:Per Max:
You don't need to "test-enable" the device because there is no test enable bit. All you need is a test sig generated from the sig generator and you can cable-load it to any 3.x device right out of the box.
__________________
Max
BREW Support
Hmmmm - I'm really confused now.............But thanks for the heads up!
I have a sony ericsson w41s handset that is a 3.x device, but it cannot even connect to the file system with the apploader. I believed this is because the phone is not test-enabled, but if what you are saying is true then I should not need it test-enabled. Is that correct? If so, do you have any ideas why it cannot connect to the phone's file system?

rbenhardt wrote:Per Max:
You don't need to "test-enable" the device because there is no test enable bit. All you need is a test sig generated from the sig generator and you can cable-load it to any 3.x device right out of the box.
__________________
Max
BREW Support
Hmmmm - I'm really confused now.............But thanks for the heads up!
I have a sony ericsson w41s handset that is a 3.x device, but it cannot even connect to the file system with the apploader. I believed this is because the phone is not test-enabled, but if what you are saying is true then I should not need it test-enabled. Is that correct? If so, do you have any ideas why it cannot connect to the phone's file system?

Taras wrote:Thanks for the answer.
But on my VX8300 under the battery only ESN HEX code, no MEID and no IMEI. May be there any possibility of obtaining phone MEID or IMEI from phone service menu?
Hey I encountered the same problem, did u fix it?

Taras wrote:Thanks for the answer.
But on my VX8300 under the battery only ESN HEX code, no MEID and no IMEI. May be there any possibility of obtaining phone MEID or IMEI from phone service menu?
Hey I encountered the same problem, did u fix it?

Hi,
The BREW 3.x handsets are not test enabled by default, as we have the Motorola V3C in our network, which has a test bit option.
This can be accessed using the Motorola PST or the hidden configuration menu on the handset. But by default the handsets are not test bit enabled when they are launched in the market.
So assuming that all BREW 3.x handsets are test enabled by default would be erroneous.

Hi,
The BREW 3.x handsets are not test enabled by default, as we have the Motorola V3C in our network, which has a test bit option.
This can be accessed using the Motorola PST or the hidden configuration menu on the handset. But by default the handsets are not test bit enabled when they are launched in the market.
So assuming that all BREW 3.x handsets are test enabled by default would be erroneous.

vikrambk wrote:Hi,
The BREW 3.x handsets are not test enabled by default, as we have the Motorola V3C in our network, which has a test bit option.
This can be accessed using the Motorola PST or the hidden configuration menu on the handset. But by default the handsets are not test bit enabled when they are launched in the market.
So assuming that all BREW 3.x handsets are test enabled by default would be erroneous.
Incorrect. While there is a test bit in the PST, it does nothing. Please don't spread misinformation when this topic has already been answered by QUALCOMM.

vikrambk wrote:Hi,
The BREW 3.x handsets are not test enabled by default, as we have the Motorola V3C in our network, which has a test bit option.
This can be accessed using the Motorola PST or the hidden configuration menu on the handset. But by default the handsets are not test bit enabled when they are launched in the market.
So assuming that all BREW 3.x handsets are test enabled by default would be erroneous.
Incorrect. While there is a test bit in the PST, it does nothing. Please don't spread misinformation when this topic has already been answered by QUALCOMM.

I'm having a similar problem. I run AppLoader in v3 mode. It communicates with the RAZR Moto V3c phone and brings up the phone's file structure. When I try to copy a file or files to the phone, I get a write error. Any ideas?

I'm having a similar problem. I run AppLoader in v3 mode. It communicates with the RAZR Moto V3c phone and brings up the phone's file structure. When I try to copy a file or files to the phone, I get a write error. Any ideas?

1. Are you using a recent version of Apploader? If so, did you apply the BTIL patch to address issues with the QCOMOEM.dll? http://brewforums.qualcomm.com/showthread.php?t=12555
2. Some Moto devices require flashing with a flex file to unlock the EFS for writing. Did you have your device flashed by our phone center?

1. Are you using a recent version of Apploader? If so, did you apply the BTIL patch to address issues with the QCOMOEM.dll? http://brewforums.qualcomm.com/showthread.php?t=12555
2. Some Moto devices require flashing with a flex file to unlock the EFS for writing. Did you have your device flashed by our phone center?

I'd just like to clarify something.
BREW US support says:
Max> "You don't need to "test-enable" the device because there is no test enable bit. All you need is a test sig generated from the sig generator and you can cable-load it to any 3.x device right out of the box."
Mohlendo> "While there is a test bit in the PST, it does nothing"
Japanese BREW support says: (paraphrased) "all KDDI phones (including 3.X) need to be sent to the US BREW HQ to get test-enabled before you can even connect in Apploader" (message here )
Can someone verify this is correct, ie, that this non-US phones (or at least, Japanese KDDI 3.X phones) really do need to be sent to the US to get test-enabled, and the stuff about "all 3.x phones don't need to be test enabled" don't apply?
Our publisher sent us a (I assume test-enabled) KDDI 3.X phone after the one I bought didn't work. But I still want to double check this for the future, also I see bestey17 had the same issue in this thread.

I'd just like to clarify something.
BREW US support says:
Max> "You don't need to "test-enable" the device because there is no test enable bit. All you need is a test sig generated from the sig generator and you can cable-load it to any 3.x device right out of the box."
Mohlendo> "While there is a test bit in the PST, it does nothing"
Japanese BREW support says: (paraphrased) "all KDDI phones (including 3.X) need to be sent to the US BREW HQ to get test-enabled before you can even connect in Apploader" (message here )
Can someone verify this is correct, ie, that this non-US phones (or at least, Japanese KDDI 3.X phones) really do need to be sent to the US to get test-enabled, and the stuff about "all 3.x phones don't need to be test enabled" don't apply?
Our publisher sent us a (I assume test-enabled) KDDI 3.X phone after the one I bought didn't work. But I still want to double check this for the future, also I see bestey17 had the same issue in this thread.

KDDI plays by their own rules, and I don't know all the details of their developer programs. All support for KDDI devices is handled by QUALCOMM Japan.

KDDI plays by their own rules, and I don't know all the details of their developer programs. All support for KDDI devices is handled by QUALCOMM Japan.

This is very confusing. I have the Nokia 6315i and the LG Chocolate. I can't see my app on either of them (while on the V3C for example everything is fine), so I assumed I could get a keypress combination like the user above reported and emailed Qualcomm support.
The response:
You will need to send them into our phone center to have them test enabled.
But... they are BREW 3.x devices, they are not supposed to have a "test enable" bit as even admins here insist on.
Anybody care to explain?

This is very confusing. I have the Nokia 6315i and the LG Chocolate. I can't see my app on either of them (while on the V3C for example everything is fine), so I assumed I could get a keypress combination like the user above reported and emailed Qualcomm support.
The response:
You will need to send them into our phone center to have them test enabled.
But... they are BREW 3.x devices, they are not supposed to have a "test enable" bit as even admins here insist on.
Anybody care to explain?

The 6315 has a configuration change that needs to be made to allow the phone to display cable-loaded devices. It's not actually the test-enable bit, but in essence it's the same thing. For the VX8500, see this thread to see if it covers your issue: http://brewforums.qualcomm.com/showthread.php?t=14091&highlight=%2A8500%2A

The 6315 has a configuration change that needs to be made to allow the phone to display cable-loaded devices. It's not actually the test-enable bit, but in essence it's the same thing. For the VX8500, see this thread to see if it covers your issue: http://brewforums.qualcomm.com/showthread.php?t=14091&highlight=%2A8500%2A

This is ridiculous, I chose the Nokia 3615i because from the info on this forum seemed it would be ready for developing with some keypresses, without having to wait the 10 bussiness days + shipping + fees of test enabling. Now, support wrote me that while this was true until a while ago, they stopped giving the code to developers for "security reasons".
I would believe it is for "security reasons" if they told me they just hold them for a day for this procedure and won't charge me, but since their answer indicated neither I will assume the reason is probably the extra profit.

This is ridiculous, I chose the Nokia 3615i because from the info on this forum seemed it would be ready for developing with some keypresses, without having to wait the 10 bussiness days + shipping + fees of test enabling. Now, support wrote me that while this was true until a while ago, they stopped giving the code to developers for "security reasons".
I would believe it is for "security reasons" if they told me they just hold them for a day for this procedure and won't charge me, but since their answer indicated neither I will assume the reason is probably the extra profit.

What profit?
We aren't allowed to give out the key sequences for legal concerns. They allow access to configuration menus that display information potentially sensitive to OEMs and carriers.

What profit?
We aren't allowed to give out the key sequences for legal concerns. They allow access to configuration menus that display information potentially sensitive to OEMs and carriers.

This LG VX8300 is very interesting. I am using a live (prod) handset and it does have hex ESN. I used this sig file to load a sample Brew app (mif, mod, bar, sig and config) and it loaded fine (it just that the program did not work yet :). However, when I used the same sig and load my own app, after I power re-cycled, the app dissapeared completely. My app works perfectly fine in the simulator. No idea why and I am still debugging this problem. (I built the mod file using gnude). If you have any lights on this problem, please share.
Regards,

This LG VX8300 is very interesting. I am using a live (prod) handset and it does have hex ESN. I used this sig file to load a sample Brew app (mif, mod, bar, sig and config) and it loaded fine (it just that the program did not work yet :). However, when I used the same sig and load my own app, after I power re-cycled, the app dissapeared completely. My app works perfectly fine in the simulator. No idea why and I am still debugging this problem. (I built the mod file using gnude). If you have any lights on this problem, please share.
Regards,

Problem solved. I followed a hint from another post. My fault. I did not specifiy the app type in MIF Editor. Wtih type set to Tool, I see it now under Get It Now - Get Tunes & Tones.

Problem solved. I followed a hint from another post. My fault. I did not specifiy the app type in MIF Editor. Wtih type set to Tool, I see it now under Get It Now - Get Tunes & Tones.

I am having a problem locating the games on my NOKIA 6315i, i was able to load them through brew apploader using the Qualcomm DLL, Brew 3x and EFS1
but after power cycle i am unable to locate the games.
I read on another post that this phone needs to be sent to Qualcom to enable it
http://brewforums.qualcomm.com/showthread.php?t=14442&highlight=6315
but I thought that all 3x phones did not need to be sent in.
Can some one help me out?

I am having a problem locating the games on my NOKIA 6315i, i was able to load them through brew apploader using the Qualcomm DLL, Brew 3x and EFS1
but after power cycle i am unable to locate the games.
I read on another post that this phone needs to be sent to Qualcom to enable it
http://brewforums.qualcomm.com/showthread.php?t=14442&highlight=6315
but I thought that all 3x phones did not need to be sent in.
Can some one help me out?

Hey all
After reading all the replies in the various threads, I still haven't got the exact response whether Test Bit Enabling is required in the handsets supporting Brew 3.x version n above or not?
I am sorry to ask this question but after every 2-3 replies some one says that it is required.Now we need to port the application on a device available in India working on 3.1.5, but which one to buy is a major question.Time is very less to send the device to Qualcomm for enabling it.
Please Help
Regards
Akshay

Hey all
After reading all the replies in the various threads, I still haven't got the exact response whether Test Bit Enabling is required in the handsets supporting Brew 3.x version n above or not?
I am sorry to ask this question but after every 2-3 replies some one says that it is required.Now we need to port the application on a device available in India working on 3.1.5, but which one to buy is a major question.Time is very less to send the device to Qualcomm for enabling it.
Please Help
Regards
Akshay