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

Developer

Forums

Hi

Has anyone tried to add a platform recently?

I'm trying to add a platform on the NSTL page, but there are no applications in drop down list "Current Production Applications". I'm trying to catch up with submission before Monday the 26th...

I've send them an email, but they usually don't reply during weekends...

I added a couple of platforms to an app just a couple of weeks ago. I had to wait until all the handsets in the original submission were completed, then the "Add Platform" link showed up in the app.'s line item on the NSTL site. If the "Add Platform" link doesn't show up, this means that the original submission has not passed on all targeted handsets. To me, it makes sense to make this link available as soon as the original submission has been accepted.

I added a couple of platforms to an app just a couple of weeks ago. I had to wait until all the handsets in the original submission were completed, then the "Add Platform" link showed up in the app.'s line item on the NSTL site. If the "Add Platform" link doesn't show up, this means that the original submission has not passed on all targeted handsets. To me, it makes sense to make this link available as soon as the original submission has been accepted.

Hi
Thanks for your reply. Actually I tried all three options there - "Upgarde", "Resubmit", "Add Platform". It has the same effect for all three.
To me it looks like something hasn't been updated in their DB. I might try with new, but then it may reject me because it's the same Class ID (BID).

Hi
Thanks for your reply. Actually I tried all three options there - "Upgarde", "Resubmit", "Add Platform". It has the same effect for all three.
To me it looks like something hasn't been updated in their DB. I might try with new, but then it may reject me because it's the same Class ID (BID).

What are you doing to access the 3 options you mention?
Are you logging into NSTL and selecting the "Add Platform" link for the app. in the "Action" column of the "Applications Submitted" page? This is the page that displays by default after you enter your password to log in to NSTL. There are no "Upgrade" or "Resubmit" options on this page. If the "Add Platform" link doesn't show up here, your app. likely isn't finished initial testing. Does your initial submittal show "Completed" in the "Current Status" column on the page accessed by clicking "Status of Existing Application"? If not, the "Add Platform" link will not show up until the app.'s current status is completed.
Murray

What are you doing to access the 3 options you mention?
Are you logging into NSTL and selecting the "Add Platform" link for the app. in the "Action" column of the "Applications Submitted" page? This is the page that displays by default after you enter your password to log in to NSTL. There are no "Upgrade" or "Resubmit" options on this page. If the "Add Platform" link doesn't show up here, your app. likely isn't finished initial testing. Does your initial submittal show "Completed" in the "Current Status" column on the page accessed by clicking "Status of Existing Application"? If not, the "Add Platform" link will not show up until the app.'s current status is completed.
Murray

It shows completed (all results were emailed earlier last week). I just wanted to add 2 more platforms to the submission.
Because by following the link from the "home" page, I couldnt do anything, I went directly to submittal page. Played with all three options, in case anyone of those would give me something in their drop down list, but drop down list was empty.

It shows completed (all results were emailed earlier last week). I just wanted to add 2 more platforms to the submission.
Because by following the link from the "home" page, I couldnt do anything, I went directly to submittal page. Played with all three options, in case anyone of those would give me something in their drop down list, but drop down list was empty.

Even though your application has been certified and passed it usually takes a few days until the resutls propagate through all the relevant databases at NSTL and Qualcomm.
I just checked, in my case, I can add new handsets without a problem, so there is no actual problem with NSTL's system at this time. It works fine and I'm submitting an app to beat the deadline, as I write this.

Even though your application has been certified and passed it usually takes a few days until the resutls propagate through all the relevant databases at NSTL and Qualcomm.
I just checked, in my case, I can add new handsets without a problem, so there is no actual problem with NSTL's system at this time. It works fine and I'm submitting an app to beat the deadline, as I write this.

I think u are right, Lucky Dragon :)
I guess their reference point is EST time zone so Im late anyway. Ill have to delay submission a few more days to finish the new docs... :(
tpw
PS this reply is written on a Symbian phone. :)

I think u are right, Lucky Dragon :)
I guess their reference point is EST time zone so Im late anyway. Ill have to delay submission a few more days to finish the new docs... :(
tpw
PS this reply is written on a Symbian phone. :)

Funny, when I want to submit an upgrade, it asks me to submit for BREW API 2.0.2, at least. Why would that be required?
Upgrade is an upgrade of an app, for whatever BREW platform it is (1.0.1, or 1.1. or so). What''s your experience with this?
Thank you for help!

Funny, when I want to submit an upgrade, it asks me to submit for BREW API 2.0.2, at least. Why would that be required?
Upgrade is an upgrade of an app, for whatever BREW platform it is (1.0.1, or 1.1. or so). What''s your experience with this?
Thank you for help!

I believe you are selecting the wrong checkbox. Upgrade is for an upgrade of your software, which you don't want to do, I believe. You want to submit additional handsets. In that case you will have to select
Submit new platform support for existing TBT application
After selecting it a drop-down menu will appear with the applications that have already been certified. Select the one you want to add your handsets to, and then simply continue filling out the rest of the form.

I believe you are selecting the wrong checkbox. Upgrade is for an upgrade of your software, which you don't want to do, I believe. You want to submit additional handsets. In that case you will have to select
Submit new platform support for existing TBT application
After selecting it a drop-down menu will appear with the applications that have already been certified. Select the one you want to add your handsets to, and then simply continue filling out the rest of the form.

But in this case I have $250 charge per platform, but I have new MOD and BAR file. Is that ok? I'm afraid that after filling in the CC information, I won't be able to upload new ZIP file (with new MOD and BAR).
Thanks...

But in this case I have $250 charge per platform, but I have new MOD and BAR file. Is that ok? I'm afraid that after filling in the CC information, I won't be able to upload new ZIP file (with new MOD and BAR).
Thanks...

If the .mod and .bar are new, you'll pay $1,000 for the first handset in the submission plus $250 for each additional handset in that submission.
Is it actually requiring you to submit for minimum api version 2.0? That's not what I'd have expected. Sorry, I've no experience with submitting an upgrade.

If the .mod and .bar are new, you'll pay $1,000 for the first handset in the submission plus $250 for each additional handset in that submission.
Is it actually requiring you to submit for minimum api version 2.0? That's not what I'd have expected. Sorry, I've no experience with submitting an upgrade.

No, you can. After you fill in the credit card info a separate page appears that allows you to upload your new files. I know the order is a bit concerning, and I was unsure about it a few times before myself, but after going through the routine quite a few times, I finally remember the steps. :))

No, you can. After you fill in the credit card info a separate page appears that allows you to upload your new files. I know the order is a bit concerning, and I was unsure about it a few times before myself, but after going through the routine quite a few times, I finally remember the steps. :))

Thank you guys!
Seems this worked this time, as "add new platform to an existing TBT app"
Eventually apge allowed me to upload new ZIP file as Dragon said it would (thanks!). Although, charges shown on the CC info page were $500, instead of expected $1250 (two new platforms).
That was kind of confusing, but, oh, well, hopefully it's going to be all ok :)

Thank you guys!
Seems this worked this time, as "add new platform to an existing TBT app"
Eventually apge allowed me to upload new ZIP file as Dragon said it would (thanks!). Although, charges shown on the CC info page were $500, instead of expected $1250 (two new platforms).
That was kind of confusing, but, oh, well, hopefully it's going to be all ok :)

It is $500 because you are adding to an existing platform. Only the VERY first submission costs you $1000. All commercial-handset additions to that are $250 each, hence your $500 bill.

It is $500 because you are adding to an existing platform. Only the VERY first submission costs you $1000. All commercial-handset additions to that are $250 each, hence your $500 bill.

I thought if you had to submit a new .zip file that differed from your original submission, that meant you had to incur the $1,000 hit again. Are you saying that you can change your .mod and .bar and still pay only $250 per handset?

I thought if you had to submit a new .zip file that differed from your original submission, that meant you had to incur the $1,000 hit again. Are you saying that you can change your .mod and .bar and still pay only $250 per handset?

Quote:Originally posted by Murray Bonner
I thought if you had to submit a new .zip file that differed from your original submission, that meant you had to incur the $1,000 hit again. Are you saying that you can change your .mod and .bar and still pay only $250 per handset?
Yeah, I'm a little confused now too if that is true. My understanding is the discount for adding platforms hinges upon the usage of the same mod and bar files. Perhaps the new zip file submission is there to allow you to change the documentation file(s)?

Quote:Originally posted by Murray Bonner
I thought if you had to submit a new .zip file that differed from your original submission, that meant you had to incur the $1,000 hit again. Are you saying that you can change your .mod and .bar and still pay only $250 per handset?
Yeah, I'm a little confused now too if that is true. My understanding is the discount for adding platforms hinges upon the usage of the same mod and bar files. Perhaps the new zip file submission is there to allow you to change the documentation file(s)?

No, but you will always have to upload a new ZIP file when you add additional handsets because you have to adjust the version number in your documentation, etc.
Once the zip file is uploaded it is checked for consistency, etc.

No, but you will always have to upload a new ZIP file when you add additional handsets because you have to adjust the version number in your documentation, etc.
Once the zip file is uploaded it is checked for consistency, etc.

> Once the zip file is uploaded it is checked for consistency, etc.
What would this exactly be?
I mean, if it ends up $250 per additional platform and with new ZIP file, that would mean that I can add different BAR files for each headset, and that would save significant amount of space on each headset (for example GIFs for those who support GIFs as well, and BMPs for those old ones that support only BMPs).

> Once the zip file is uploaded it is checked for consistency, etc.
What would this exactly be?
I mean, if it ends up $250 per additional platform and with new ZIP file, that would mean that I can add different BAR files for each headset, and that would save significant amount of space on each headset (for example GIFs for those who support GIFs as well, and BMPs for those old ones that support only BMPs).

Quote:Originally posted by ThePhoneWiz
But in this case I have $250 charge per platform, but I have new MOD and BAR file. Is that ok? I'm afraid that after filling in the CC information, I won't be able to upload new ZIP file (with new MOD and BAR).
Thanks...
TPW said here that his mod and bar have changed. To me, this means the "Add Platform" route is not for him. He has to submit a new version and this will cost him $1,250. Is my understanding correct?
Thanks.

Quote:Originally posted by ThePhoneWiz
But in this case I have $250 charge per platform, but I have new MOD and BAR file. Is that ok? I'm afraid that after filling in the CC information, I won't be able to upload new ZIP file (with new MOD and BAR).
Thanks...
TPW said here that his mod and bar have changed. To me, this means the "Add Platform" route is not for him. He has to submit a new version and this will cost him $1,250. Is my understanding correct?
Thanks.

Yes, as far as I know. Mind you, I'm not an NSTL expert, and I don't really know what the consistency check does. I just see it in the browser window that it unzips the package I submit and does various operations on it, most likely checking the validity of the files as well as doing a compare against the previous versions of the submission to validate the "Add platform" eligibility.

Yes, as far as I know. Mind you, I'm not an NSTL expert, and I don't really know what the consistency check does. I just see it in the browser window that it unzips the package I submit and does various operations on it, most likely checking the validity of the files as well as doing a compare against the previous versions of the submission to validate the "Add platform" eligibility.

Quote:Originally posted by jmiller2
... Perhaps the new zip file submission is there to allow you to change the documentation file(s)?
I never thought of that in my earlier post but it makes good sense.

Quote:Originally posted by jmiller2
... Perhaps the new zip file submission is there to allow you to change the documentation file(s)?
I never thought of that in my earlier post but it makes good sense.

I agree with you guys. I wouldn't submit an "add to an existing TBT app", but I would submit an "upgrade". However, "upgrade" didn't let me submit below BREW 2.0.2 (it required that BREW API field to be BREW 2.0.2). My upgrade is for BREW 1.1 phones...
So, I went and submitted an "add to an existing" - because only that allowed me to continue with BREW 1.1 and upload a ZIP.
Again, "upgrade" required BREW 2.0.2, and btw, BREW 2.0.2 was actually not in the list. Last item in that list was BREW 2.0.0 and selecting that didn't help as well - it still threw an alert on the page.
Yesterday and the day before, non of those was possible, since I wasn't able to pick an existing app from drop down menu. I tested all possible options ("add" "upgrade" "resubmit") for that, but nothing worked - there was no existing app in the list.
Anyway, I sent emails to NSTL about this. Hopefully they will be able to untie this knot...
Thanks again for hints.

I agree with you guys. I wouldn't submit an "add to an existing TBT app", but I would submit an "upgrade". However, "upgrade" didn't let me submit below BREW 2.0.2 (it required that BREW API field to be BREW 2.0.2). My upgrade is for BREW 1.1 phones...
So, I went and submitted an "add to an existing" - because only that allowed me to continue with BREW 1.1 and upload a ZIP.
Again, "upgrade" required BREW 2.0.2, and btw, BREW 2.0.2 was actually not in the list. Last item in that list was BREW 2.0.0 and selecting that didn't help as well - it still threw an alert on the page.
Yesterday and the day before, non of those was possible, since I wasn't able to pick an existing app from drop down menu. I tested all possible options ("add" "upgrade" "resubmit") for that, but nothing worked - there was no existing app in the list.
Anyway, I sent emails to NSTL about this. Hopefully they will be able to untie this knot...
Thanks again for hints.