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

Developer

Forums

I have a doubt. Kindly consider the following situation :-
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I have a BREW app, for which I want to get the TBT done, for the first time. The client expects the app to run on 20 devices.

But currently I have only 2 devices, on which I have personally tested, and found it to be able to clear the TBT. And the rest of the 18 devices fulfill the criteria required to run my app, based on the info from the DDS. Now as I have tested it only on 2 devices, I get the TBT done only on those 2 devices, for a given operator, and pass the TBT.

But as my client expects it for 20 devices, can I claim to my client that it will run on other 18 devices as well. Or will I have to get the TBT done for the rest of all 18 devices ?

And will the operator become ready to include the application on a commercial catalog, for all the 20 devices, given that TBT has been done for only 2 devices for that app??
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Please clarify

No you can't, its certainly possible to say they'll run and you might get away with it, but often there are firmware problems that will cause issues with your app.
stuff like menus not working, font size differences, sound not working as expected, clamshell issues, suspend/resume problems, different speeds, heap issues, etc etc etc
if you've got a working library and skeleton you've already TBT'd on all the devices it helps, but if its a first time or one off, then chances aren't as good..
typically its best to submit one for TBT see if it passes, then submit the others, but if you do it blindly, you may get failures for dumb things.
youll have to TBT all devices to get them on deck, at least as far as i know, there may be some operators that aren't as strict but it seems unlikely.

No you can't, its certainly possible to say they'll run and you might get away with it, but often there are firmware problems that will cause issues with your app.
stuff like menus not working, font size differences, sound not working as expected, clamshell issues, suspend/resume problems, different speeds, heap issues, etc etc etc
if you've got a working library and skeleton you've already TBT'd on all the devices it helps, but if its a first time or one off, then chances aren't as good..
typically its best to submit one for TBT see if it passes, then submit the others, but if you do it blindly, you may get failures for dumb things.
youll have to TBT all devices to get them on deck, at least as far as i know, there may be some operators that aren't as strict but it seems unlikely.

Thanks charliex for you input. That clears a part of my doubt.
What still remains is, if I say now, I got the TBT done once, and passed for those 2 devices. will the operator become ready to include the application on catalog, for all the 20 devices, given the fact, that those 18 devices clears the criteria to run the app, decided based on the DDS, like heap, screen, audio ?
Or rather, on what basis does an operator decide, for which devices a given app should be placed under the catalog ? Is it just based on which devices the app has cleared the TBT, or other reasons(if any, which?) ?

Thanks charliex for you input. That clears a part of my doubt.
What still remains is, if I say now, I got the TBT done once, and passed for those 2 devices. will the operator become ready to include the application on catalog, for all the 20 devices, given the fact, that those 18 devices clears the criteria to run the app, decided based on the DDS, like heap, screen, audio ?
Or rather, on what basis does an operator decide, for which devices a given app should be placed under the catalog ? Is it just based on which devices the app has cleared the TBT, or other reasons(if any, which?) ?

no, because there is no way for you to know if they match the spec, the DDS are not accurate on everything, see the known issues for instance.
even with the DDS, known issues, etc there may be differences that will cause it to fail,, they aren't all documented.
for instance say on the LGVX 6000 something as simple as the horizontal menu control doesn't work, on the Motorola V710, sound doesn't work properly.
the only way is to get them all TBT'd, you can submit the same app on multiple phones if it runs on all of them to cut costs, but an initial submit of one or two is a good idea.
as i said you might get lucky and pass TBT blind, but you'll still have to submit them for TBT if you want them on deck ( unless as i said the operator allows a bypass, something i've never heard of )

no, because there is no way for you to know if they match the spec, the DDS are not accurate on everything, see the known issues for instance.
even with the DDS, known issues, etc there may be differences that will cause it to fail,, they aren't all documented.
for instance say on the LGVX 6000 something as simple as the horizontal menu control doesn't work, on the Motorola V710, sound doesn't work properly.
the only way is to get them all TBT'd, you can submit the same app on multiple phones if it runs on all of them to cut costs, but an initial submit of one or two is a good idea.
as i said you might get lucky and pass TBT blind, but you'll still have to submit them for TBT if you want them on deck ( unless as i said the operator allows a bypass, something i've never heard of )

Alright. I got your point Charliex.
Could you help me with the left-out question i.e. on what basis does an operator decide, for which devices a given app should be placed under the catalog ? Is it just based on which devices the app has cleared the TBT, or other reasons(if any, which?) ?

Alright. I got your point Charliex.
Could you help me with the left-out question i.e. on what basis does an operator decide, for which devices a given app should be placed under the catalog ? Is it just based on which devices the app has cleared the TBT, or other reasons(if any, which?) ?

sorry i misunderstood your question
operator acceptance is based on a number of things, passing TBT, branding of the app, bribery, who you know ,etc.
if you pass TBT and the operator wants your app you should be good to go, normally this is predetermined, but never in stone.

sorry i misunderstood your question
operator acceptance is based on a number of things, passing TBT, branding of the app, bribery, who you know ,etc.
if you pass TBT and the operator wants your app you should be good to go, normally this is predetermined, but never in stone.

Ok. So out of what I understood is that :-
1. One should get the TBT done for all those devices, for which we are expecting operator acceptance. :eek:
2. The operator would include the TBT-passed app, ONLY for those devices (officially) on which it was tested for TBT. For e.g., if an app clears TBT for 2 devices, the operator would include the app for download only for these 2 devices, and no other :rolleyes: .
Please correct me, if im wrong. :p

Ok. So out of what I understood is that :-
1. One should get the TBT done for all those devices, for which we are expecting operator acceptance. :eek:
2. The operator would include the TBT-passed app, ONLY for those devices (officially) on which it was tested for TBT. For e.g., if an app clears TBT for 2 devices, the operator would include the app for download only for these 2 devices, and no other :rolleyes: .
Please correct me, if im wrong. :p

AS to the best of my understanding, yes.
basically if you want on the deck for a device, the app must have passed TBT on that device, either individualy or as a grouped TBT (an app that runs on multiple devices without any changes whatsoever can be grouped for lower cost)

AS to the best of my understanding, yes.
basically if you want on the deck for a device, the app must have passed TBT on that device, either individualy or as a grouped TBT (an app that runs on multiple devices without any changes whatsoever can be grouped for lower cost)

Could anyone help me, from where to find the document called "TRUE BREW Test Guide". I have been searching all the way, but couldn't find it.
Please help.

Could anyone help me, from where to find the document called "TRUE BREW Test Guide". I have been searching all the way, but couldn't find it.
Please help.

brew page, developer/developer extranet/ documents for the submission guide
http://brew.qualcomm.com/brew/en/
for the procedures
https://brewx.qualcomm.com/brew/sdk/download.jsp?page=devrelations/brewd...

brew page, developer/developer extranet/ documents for the submission guide
http://brew.qualcomm.com/brew/en/
for the procedures
https://brewx.qualcomm.com/brew/sdk/download.jsp?page=devrelations/brewd...

I have been through these documents.
What I am looking for is a file which calls itself "TRUE BREW Test Guide", whose reference can be found both in the forums and the brew site. Unfortunately, i have been unable to spot its download path.
PS:- The above two links refer to the "AppSubmit" and Test related docs.

I have been through these documents.
What I am looking for is a file which calls itself "TRUE BREW Test Guide", whose reference can be found both in the forums and the brew site. Unfortunately, i have been unable to spot its download path.
PS:- The above two links refer to the "AppSubmit" and Test related docs.

http://www.redbusdev.com/brew_bnry/pdf/documentation/80-D4187-1_E.pdf
ps. the previously linked docs also contain the test procedures

http://www.redbusdev.com/brew_bnry/pdf/documentation/80-D4187-1_E.pdf
ps. the previously linked docs also contain the test procedures