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

Developer

Forums

Hello Friends,

What is the average time does True BREW Testing (TBT) takes ?

When on should start contacting NSTL/Qualcomm for TBT ? I have heared that we get reply very late from Qualcomm. So, is it ok if we start contacting them before few days of completion of our application ?

Starting from contacting NSTL/Qualcomm for TBT to the end of TBT generally how many days does it take ?

How do they do the testing ? Are the very strict in testing and can reject the application having even a small difference from the Test Guide ? I mean do they want everything perfect ?

Regards,

Gaurang.

The NSTL website gives you an estimate of how long the test will take when you submit your application. I believe the estimate is currently 12 days.
This is pretty accurate, but don't be sad if your application takes as long as three or four weeks to get through testing. This is from the time that you submit it to NSTL, not when you first start talking to Qualcomm. The people at Qualcomm are nice, but it's not necessary to talk to them before you submit your application.
In my experience, the folks at NSTL are very conscientious and do notice small things in the test guide. However, not every difference will result in your application failing-- your application may just be "passed with notes".
I suggest that you get your application doing everything in the test guide before you submit. Bugs are easy to fix, so it's better to pass the first time than fail and have to fix them a month from now.

The NSTL website gives you an estimate of how long the test will take when you submit your application. I believe the estimate is currently 12 days.
This is pretty accurate, but don't be sad if your application takes as long as three or four weeks to get through testing. This is from the time that you submit it to NSTL, not when you first start talking to Qualcomm. The people at Qualcomm are nice, but it's not necessary to talk to them before you submit your application.
In my experience, the folks at NSTL are very conscientious and do notice small things in the test guide. However, not every difference will result in your application failing-- your application may just be "passed with notes".
I suggest that you get your application doing everything in the test guide before you submit. Bugs are easy to fix, so it's better to pass the first time than fail and have to fix them a month from now.

I have several sets of submissions that have been in the lab for 19 business days as of today.
---jeff

I have several sets of submissions that have been in the lab for 19 business days as of today.
---jeff

We have a couple at 31 :) Things were speedy until Qualcomm changed the pricing, everyone dumped a boatload of apps on NSTL before the price increase.
Also, I believe the phone you submitted for will affect things. As a rule - newer phones = faster service. Before the change we got things through in around 12 days, sometimes a week longer.
Curt

We have a couple at 31 :) Things were speedy until Qualcomm changed the pricing, everyone dumped a boatload of apps on NSTL before the price increase.
Also, I believe the phone you submitted for will affect things. As a rule - newer phones = faster service. Before the change we got things through in around 12 days, sometimes a week longer.
Curt

31 days and counting...

31 days and counting...

dang, this sounds horrible. I gotta make sure my apps don't fail then. I guess it takes about the same if you resubmit a previously tested one.

dang, this sounds horrible. I gotta make sure my apps don't fail then. I guess it takes about the same if you resubmit a previously tested one.

Hehe i've more than 45 days atm..
But yeah, should take the same time when you resubmit it, at least that what the brew support told me :(

Hehe i've more than 45 days atm..
But yeah, should take the same time when you resubmit it, at least that what the brew support told me :(

What phone you submit for makes a difference. We submitted for the VX10 and I fear it will be there forever, but our VX6000 app went through pretty quick.
Curt

What phone you submit for makes a difference. We submitted for the VX10 and I fear it will be there forever, but our VX6000 app went through pretty quick.
Curt

Hi Developers,
We at NSTL wish to apologize for the delays in application turn around time. Please be assured that we are doing our best to speed the process up as fast as we can.
With new handsets and new carriers added everyday, BREW is growing extermely quickly and it was difficult to staff for this. We are working tirelessly to improve the situation, and feel that developers will start noticing the difference soon.
Please contact eval(unescape('%64%6f%63%75%6d%65%6e%74%2e%77%72%69%74%65%28%27%3c%61%20%68%72%65%66%3d%22%6d%61%69%6c%74%6f%3a%62%72%65%77%2d%74%65%73%74%69%6e%67%40%6e%73%74%6c%2e%63%6f%6d%22%20%63%6c%61%73%73%3d%22%62%62%2d%65%6d%61%69%6c%22%3e%62%72%65%77%2d%74%65%73%74%69%6e%67%40%6e%73%74%6c%2e%63%6f%6d%3c%2f%61%3e%27%29%3b')) if your application has been in process for over 40 days. We'll do our best to give you an estimate on completion date.
Thanks,
Shital

Hi Developers,
We at NSTL wish to apologize for the delays in application turn around time. Please be assured that we are doing our best to speed the process up as fast as we can.
With new handsets and new carriers added everyday, BREW is growing extermely quickly and it was difficult to staff for this. We are working tirelessly to improve the situation, and feel that developers will start noticing the difference soon.
Please contact eval(unescape('%64%6f%63%75%6d%65%6e%74%2e%77%72%69%74%65%28%27%3c%61%20%68%72%65%66%3d%22%6d%61%69%6c%74%6f%3a%62%72%65%77%2d%74%65%73%74%69%6e%67%40%6e%73%74%6c%2e%63%6f%6d%22%20%63%6c%61%73%73%3d%22%62%62%2d%65%6d%61%69%6c%22%3e%62%72%65%77%2d%74%65%73%74%69%6e%67%40%6e%73%74%6c%2e%63%6f%6d%3c%2f%61%3e%27%29%3b')) if your application has been in process for over 40 days. We'll do our best to give you an estimate on completion date.
Thanks,
Shital

45 days or more and counting... on four of the six apps that I submitted.
Shital, no disrespect or anything, but these turn-around times are unacceptable for anyone who is taking this business serious. It was absolutely predictable to everyone in the industry that you guys would be flooded with submissions before the window closed and that NSTL was not prepared for the scenario only shows that maybe you guys should seriously reconsider your operations. Just apologizing won't do the trick, I'm afraid, though it is a nice move.

45 days or more and counting... on four of the six apps that I submitted.
Shital, no disrespect or anything, but these turn-around times are unacceptable for anyone who is taking this business serious. It was absolutely predictable to everyone in the industry that you guys would be flooded with submissions before the window closed and that NSTL was not prepared for the scenario only shows that maybe you guys should seriously reconsider your operations. Just apologizing won't do the trick, I'm afraid, though it is a nice move.

Sure, now Shital is here, I need to behave :) As I had stated, the phone you submit for makes a difference, and I guess the fact that they are swamped means it is probably worth it...
Curt

Sure, now Shital is here, I need to behave :) As I had stated, the phone you submit for makes a difference, and I guess the fact that they are swamped means it is probably worth it...
Curt

Does this mean we can expect something like 1 week turnarounds in the future?
Some of mine are almost at 2 months now...

Does this mean we can expect something like 1 week turnarounds in the future?
Some of mine are almost at 2 months now...

and how soon can we expect this new speed up? I'm going to have to submit some apps in the near future ( 1 - 2 weeks ) . Should i wait till you guys fix the slow downs?

and how soon can we expect this new speed up? I'm going to have to submit some apps in the near future ( 1 - 2 weeks ) . Should i wait till you guys fix the slow downs?

Hi All,
I hate to sound like the apologetic company guy, but I will :D
The price changed announced in July was unpredictable and the amount of submissions was definitely unpredictable. We have increased staff to help deal with the amount of applications. I think the turn around times should be dropped to 10 days probably in the next 2 or 3 weeks (but I won't stake my life on it).
No need to be nice though, I rejoined to get honest feelings from devleopers. I can't address problems that I don't know about. Although the turn-around problem I am all too aware of ;)

Hi All,
I hate to sound like the apologetic company guy, but I will :D
The price changed announced in July was unpredictable and the amount of submissions was definitely unpredictable. We have increased staff to help deal with the amount of applications. I think the turn around times should be dropped to 10 days probably in the next 2 or 3 weeks (but I won't stake my life on it).
No need to be nice though, I rejoined to get honest feelings from devleopers. I can't address problems that I don't know about. Although the turn-around problem I am all too aware of ;)

never submitting a brew application im not too sure how it would work. I suppose if my application works properly on the emulator won't garaunty that i pass TRUE BREW right?
Also i am making an application for various customers. The application though very simmilar isn't the same for each customer. All the changes from one app to the next can be done through a .res / .mif file. Will i have to resubmit EACH application again? Or can i some how keep changing the res/mif files with out a problem?
any explaination will help, thx.

never submitting a brew application im not too sure how it would work. I suppose if my application works properly on the emulator won't garaunty that i pass TRUE BREW right?
Also i am making an application for various customers. The application though very simmilar isn't the same for each customer. All the changes from one app to the next can be done through a .res / .mif file. Will i have to resubmit EACH application again? Or can i some how keep changing the res/mif files with out a problem?
any explaination will help, thx.

Wow, > 40 days for my app.. And the funny thing : mophun certification process: < 5 days. My app was certified in 1 day!! Btw mophun is really bad compared to brew..
/kUfa

Wow, > 40 days for my app.. And the funny thing : mophun certification process: < 5 days. My app was certified in 1 day!! Btw mophun is really bad compared to brew..
/kUfa

The testing document for BREW apps can be found on the development site, it is not a fun read but if you want to assure yourself of passing you should go through it.
I believe their are FAQs out there on common problems as well. Key things to remember is handling suspend/resume properly, file system full is another big one.
The 2.0 "emulator" is much better than the 1.1 one, but you will still want to see it running on a test enabled handset. We have submitted blindly in the past, but it is never the way you want to go.
Hope that helps,
Curt

The testing document for BREW apps can be found on the development site, it is not a fun read but if you want to assure yourself of passing you should go through it.
I believe their are FAQs out there on common problems as well. Key things to remember is handling suspend/resume properly, file system full is another big one.
The 2.0 "emulator" is much better than the 1.1 one, but you will still want to see it running on a test enabled handset. We have submitted blindly in the past, but it is never the way you want to go.
Hope that helps,
Curt

any ideas about my res/mif problem?

any ideas about my res/mif problem?

You will have to resubmit to make any changes to the application. It is tought to accept for awhile, but you will end up submitting for every phone seperately most of the time.
The only other option is if you have a text config file and just make small changes to that without changing the bar or mod files you can get a reduced testing fee.
Curt

You will have to resubmit to make any changes to the application. It is tought to accept for awhile, but you will end up submitting for every phone seperately most of the time.
The only other option is if you have a text config file and just make small changes to that without changing the bar or mod files you can get a reduced testing fee.
Curt

I have to submit my application for EACH phone? This seems kind of lame since i made my application to be used on ALL brew 1.1 and up phones. So if i submit for the lowest crappiest phone it won't allow me to pass for all the better phone as well?
How are developers supposed to get user's thier apps will with all these hastles?

I have to submit my application for EACH phone? This seems kind of lame since i made my application to be used on ALL brew 1.1 and up phones. So if i submit for the lowest crappiest phone it won't allow me to pass for all the better phone as well?
How are developers supposed to get user's thier apps will with all these hastles?

Quote: have to submit my application for EACH phone?
Well, at least you have to specify which phones you are targetting when you submit the application. If there is only 1 mod and 1 bar, then you will pay only for 1 certification. Btw the more phones, the longer it will take ;)
/kUfa

Quote: have to submit my application for EACH phone?
Well, at least you have to specify which phones you are targetting when you submit the application. If there is only 1 mod and 1 bar, then you will pay only for 1 certification. Btw the more phones, the longer it will take ;)
/kUfa

It isn't that you HAVE to, it is just the odds of writing an application that works on all phones is pretty slim. In the ringtone world we deal with things like some phones supporting setringer, some don't, different formats, screen sizes, etc...
For games you deal with processor speed, and whatever else you game people do :)
We have had single BREW apps work fine across four phones and pass NSTL, but we would rather tailor our app to each phone as much as possible (not to mention, every phone has its own "issues" to deal with).
I don't think anyone would argue that the testing is all that easy, but the rewards are access to pretty good carriers and a group of content that is all highly tested and good.
Curt

It isn't that you HAVE to, it is just the odds of writing an application that works on all phones is pretty slim. In the ringtone world we deal with things like some phones supporting setringer, some don't, different formats, screen sizes, etc...
For games you deal with processor speed, and whatever else you game people do :)
We have had single BREW apps work fine across four phones and pass NSTL, but we would rather tailor our app to each phone as much as possible (not to mention, every phone has its own "issues" to deal with).
I don't think anyone would argue that the testing is all that easy, but the rewards are access to pretty good carriers and a group of content that is all highly tested and good.
Curt

Btw all my games test at startup on which phone they are running, and change some internal settings... This way i save alot of money hehe :)
Btw if you have a kind of upper-layer API, it's very easy to do, you do not have to worry about those plateform specific bugs (except when you write this layer..)
/kUfa

Btw all my games test at startup on which phone they are running, and change some internal settings... This way i save alot of money hehe :)
Btw if you have a kind of upper-layer API, it's very easy to do, you do not have to worry about those plateform specific bugs (except when you write this layer..)
/kUfa

thanks for all the help.

thanks for all the help.

No, having an app running in the emulastor will not guarantee TRUE BREW testing. Not even having it runningon a handset does. There is an 80-page checklist on the Extranet that outlines the steps required to pass the test, and believe you me, that is not a trivial thing. It takes alot of discipline and a lot of coding along certain guidelines. If you haven't checked out the document I would recommend you do so soon, only to get a feel for what you're up against.
As for your different versions, I'm afraid that will be an expensine undertaking because yes, you will have to have EVERY one of your version certified, and you have to have it certified for EVERY handset it will run on. Costs per certification are currently at $1000 if the application passes and a multiple of that if it fails, depdning on how many times you have to resubmit it.

No, having an app running in the emulastor will not guarantee TRUE BREW testing. Not even having it runningon a handset does. There is an 80-page checklist on the Extranet that outlines the steps required to pass the test, and believe you me, that is not a trivial thing. It takes alot of discipline and a lot of coding along certain guidelines. If you haven't checked out the document I would recommend you do so soon, only to get a feel for what you're up against.
As for your different versions, I'm afraid that will be an expensine undertaking because yes, you will have to have EVERY one of your version certified, and you have to have it certified for EVERY handset it will run on. Costs per certification are currently at $1000 if the application passes and a multiple of that if it fails, depdning on how many times you have to resubmit it.

ya, i'm just getting into the heavy docs now. 1000$ per submition seems unreasonable cost for the simple application that i'm making. $250 to change the URL/Splash screen, but i can't change mod/bar files that will cost another 1000$
Once we use up our first 3 free Submitions i don't think we will be developing on this platform anymore (unless the clients are willing to put up the testing money)
This whole process is far too complicated and expensive. And i love how i can't look at any of the documents envolving testing until i've forked over the 400$ to Verisign.

ya, i'm just getting into the heavy docs now. 1000$ per submition seems unreasonable cost for the simple application that i'm making. $250 to change the URL/Splash screen, but i can't change mod/bar files that will cost another 1000$
Once we use up our first 3 free Submitions i don't think we will be developing on this platform anymore (unless the clients are willing to put up the testing money)
This whole process is far too complicated and expensive. And i love how i can't look at any of the documents envolving testing until i've forked over the 400$ to Verisign.

Well, the whole concept behind this is, of course, security, and while it may seems a bit complicated, it does have a purpose and it serves that purpose extremely well. I have to admit that the process could be streamlined, that the costs should be reduced at least somewhat and that the timeline should be optimized to get applications through the process altogether, but at the same time, this rigorous procedure and entry barrier keeps all the junk away from the Brew platform, which most of us are very thankful for. Anyone who's looked at the offerings in the J2ME or Microsoft Smartphone market, knows that allowing the market to be flooded with third-rate product is not a good idea.
The $1000 price tag per handset submission is unreasonable for ANY application, though, that I agree with. And that is only the cheapest version for the most simple Brew applications. Costs go up gradually as you add functionality.

Well, the whole concept behind this is, of course, security, and while it may seems a bit complicated, it does have a purpose and it serves that purpose extremely well. I have to admit that the process could be streamlined, that the costs should be reduced at least somewhat and that the timeline should be optimized to get applications through the process altogether, but at the same time, this rigorous procedure and entry barrier keeps all the junk away from the Brew platform, which most of us are very thankful for. Anyone who's looked at the offerings in the J2ME or Microsoft Smartphone market, knows that allowing the market to be flooded with third-rate product is not a good idea.
The $1000 price tag per handset submission is unreasonable for ANY application, though, that I agree with. And that is only the cheapest version for the most simple Brew applications. Costs go up gradually as you add functionality.

Just one quick correction, $1000 covers any app now, including Tier3... Good news for those of us who need TAPI to get a unique ID on the phone.
Only other thing I would add, just in the US, getting on BREW gives you access to over forty (closer to fifty) million customers. If you can create a great app, $1000 is nothing compared to the return. Just ask the folks at JamDat :)
Curt

Just one quick correction, $1000 covers any app now, including Tier3... Good news for those of us who need TAPI to get a unique ID on the phone.
Only other thing I would add, just in the US, getting on BREW gives you access to over forty (closer to fifty) million customers. If you can create a great app, $1000 is nothing compared to the return. Just ask the folks at JamDat :)
Curt

1000$ per application is a lot...since i tailor each app for each client. I'm going to have to figure a way that i can manage to resubmit via the $250 thinger...that is the only ways it's some what cost effective. I can't pass the $1000 fee to the client, since most won't want to pay that much for the product in the first place.

1000$ per application is a lot...since i tailor each app for each client. I'm going to have to figure a way that i can manage to resubmit via the $250 thinger...that is the only ways it's some what cost effective. I can't pass the $1000 fee to the client, since most won't want to pay that much for the product in the first place.

Quote:Anyone who's looked at the offerings in the J2ME or Microsoft Smartphone market, knows that allowing the market to be flooded with third-rate product is not a good idea. Quote:If you can create a great app, $1000 is nothing compared to the return. Just ask the folks at JamDat
Well, i know this is not the subject, but there are much more better games for J2ME.. Why? Because you can get much more skilled people (ppl can train, make samples etc).. And if you game/app is good, even if they are lame games on the market, you will still earn alot of money..
Havent seen any good brew game so far..
/kUfa

Quote:Anyone who's looked at the offerings in the J2ME or Microsoft Smartphone market, knows that allowing the market to be flooded with third-rate product is not a good idea. Quote:If you can create a great app, $1000 is nothing compared to the return. Just ask the folks at JamDat
Well, i know this is not the subject, but there are much more better games for J2ME.. Why? Because you can get much more skilled people (ppl can train, make samples etc).. And if you game/app is good, even if they are lame games on the market, you will still earn alot of money..
Havent seen any good brew game so far..
/kUfa

What the Hell are you doing here then?

What the Hell are you doing here then?

Making better games ;)

Making better games ;)

I knew you'd say that. :D

I knew you'd say that. :D

hehe ;)
Btw do not get me wrong, i mostly complaining about the TBT which is expensive and takes loooong time.. We would have such a great community is anyone would be able to show his talent.. For example, Worms. It's probably not the best game ever, but was done by an english student. Team17 found it, hired the guy, and yop, made alot of money with a good game. Would it be possible with Brew? Even mophun (baah crap) is faster and cost nothing.. Ok you need to become a "premium" developer to get your game certifcated, the only thing you need is to send a sample of your app/game. I have the opportunity to work in a company that has money, but what about the others?
But this is not the topic of this thread, and if we want to talk more about it we should create a new one!
/kUfa

hehe ;)
Btw do not get me wrong, i mostly complaining about the TBT which is expensive and takes loooong time.. We would have such a great community is anyone would be able to show his talent.. For example, Worms. It's probably not the best game ever, but was done by an english student. Team17 found it, hired the guy, and yop, made alot of money with a good game. Would it be possible with Brew? Even mophun (baah crap) is faster and cost nothing.. Ok you need to become a "premium" developer to get your game certifcated, the only thing you need is to send a sample of your app/game. I have the opportunity to work in a company that has money, but what about the others?
But this is not the topic of this thread, and if we want to talk more about it we should create a new one!
/kUfa

...60 days and still counting! This is beyond ridiculous now and is turning into pathetic!
Is here anyone who submitted his applications after July 18 and has had them coming out of certification by this time? I am under the impression here that something fishy is going on...

...60 days and still counting! This is beyond ridiculous now and is turning into pathetic!
Is here anyone who submitted his applications after July 18 and has had them coming out of certification by this time? I am under the impression here that something fishy is going on...

yeah, unfortunately you are right, it s really pathetic.. (also submitted my app along time ago..)
I thought about spamming nstl and qualcomm with hourly where-are-my-results?-mails but heh i already know the results if i do that :rolleyes: :D

yeah, unfortunately you are right, it s really pathetic.. (also submitted my app along time ago..)
I thought about spamming nstl and qualcomm with hourly where-are-my-results?-mails but heh i already know the results if i do that :rolleyes: :D

Okay, it has now come to my attention that certain titles that were submitted well after the June 21 deadline - up to 2 weeks after the deadline, actually - have already passed NSTL certification, while at the same time apps like mine - which have been submitted a number of days BEFORE the deadline are still nowhere to be seen.
I am speechless, to be honest, as there is evidently some sort of preferential treatment going on. It is bad enough that NSTL don't have their act together but this is an outrage! No matter how nicely Shital apologizes herein the forum for the delays, but despite his claims it DOES NOT AFFECT EVERYONE!
Shame on you!

Okay, it has now come to my attention that certain titles that were submitted well after the June 21 deadline - up to 2 weeks after the deadline, actually - have already passed NSTL certification, while at the same time apps like mine - which have been submitted a number of days BEFORE the deadline are still nowhere to be seen.
I am speechless, to be honest, as there is evidently some sort of preferential treatment going on. It is bad enough that NSTL don't have their act together but this is an outrage! No matter how nicely Shital apologizes herein the forum for the delays, but despite his claims it DOES NOT AFFECT EVERYONE!
Shame on you!

Quote:Originally posted by Dragon
Okay, it has now come to my attention that certain titles that were submitted well after the June 21 deadline - up to 2 weeks after the deadline, actually - have already passed NSTL certification, while at the same time apps like mine - which have been submitted a number of days BEFORE the deadline are still nowhere to be seen.
I am speechless, to be honest, as there is evidently some sort of preferential treatment going on. It is bad enough that NSTL don't have their act together but this is an outrage! No matter how nicely Shital apologizes herein the forum for the delays, but despite his claims it [B]DOES NOT AFFECT EVERYONE!
Shame on you! [/B]
that's not the kind of i like to hear just becomming a registered developer. I think some kind of compensation should be given to Dragon to show some good faith from the NSTL. Good luck Dragon...i hope your app's get certified as quickly as possible.

Quote:Originally posted by Dragon
Okay, it has now come to my attention that certain titles that were submitted well after the June 21 deadline - up to 2 weeks after the deadline, actually - have already passed NSTL certification, while at the same time apps like mine - which have been submitted a number of days BEFORE the deadline are still nowhere to be seen.
I am speechless, to be honest, as there is evidently some sort of preferential treatment going on. It is bad enough that NSTL don't have their act together but this is an outrage! No matter how nicely Shital apologizes herein the forum for the delays, but despite his claims it [B]DOES NOT AFFECT EVERYONE!
Shame on you! [/B]
that's not the kind of i like to hear just becomming a registered developer. I think some kind of compensation should be given to Dragon to show some good faith from the NSTL. Good luck Dragon...i hope your app's get certified as quickly as possible.

I know that there is one submission that I completed in late August that has already passed NSTL. It was submitted by somebody with substantial clout (not me).
It was a single-handset submission.
I agree, this is really lame.

I know that there is one submission that I completed in late August that has already passed NSTL. It was submitted by somebody with substantial clout (not me).
It was a single-handset submission.
I agree, this is really lame.

Check it out:
Quote:
Subject: Message from NSTL
Dear BREW developers,
As you know, we have been experiencing a surge in the number of submissions to TRUE BREW testing over the last 8 weeks. As a standard practice, QUALCOMM and NSTL regularly work together to estimate the volume of future submissions and to plan accordingly. However, due to the overwhelming acceptance and success of BREW, recent submission volume has been unusually high.
While this is extremely encouraging as it relates to the new business opportunities with both new and existing BREW carriers, we fully understand that delays in the testing process have a significant impact on your business. We would like to assure you that this issue is very serious to NSTL and we are committed to reducing turnaround times. Based on the rate of submission we have experienced over the last few weeks, we estimate that the average turnaround time will be reduced to 10 days by October 24, 2003.
Thank you for your understanding and support
Will see how it s gonna be now..
/kUfa

Check it out:
Quote:
Subject: Message from NSTL
Dear BREW developers,
As you know, we have been experiencing a surge in the number of submissions to TRUE BREW testing over the last 8 weeks. As a standard practice, QUALCOMM and NSTL regularly work together to estimate the volume of future submissions and to plan accordingly. However, due to the overwhelming acceptance and success of BREW, recent submission volume has been unusually high.
While this is extremely encouraging as it relates to the new business opportunities with both new and existing BREW carriers, we fully understand that delays in the testing process have a significant impact on your business. We would like to assure you that this issue is very serious to NSTL and we are committed to reducing turnaround times. Based on the rate of submission we have experienced over the last few weeks, we estimate that the average turnaround time will be reduced to 10 days by October 24, 2003.
Thank you for your understanding and support
Will see how it s gonna be now..
/kUfa