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

Developer

Forums

Hello:

We've had an odd result during NSTL testing and I am someone can give us some insight into what may be going on.

As per the reports from NSTL, they download the application from the ADS to a Kyocera KX-13. They indicate yes to start the application. The application faisl to start, and when they then go to the BREW menu, it is there, but it shows as a name of "Application" not the actual name we specified in the MIF.

However, when they power cycle the phone, the application shows correctly in the BREW menu, and the application starts correctly.

Anyone got any insights into this area? It is hard to test directly as a developer, when loading the app from the Ap Loader, we power cycle or reset the devices as a matter of course durign our testing.

Thanks.

the only times i've seen this happen, is either memory fragmentation issues and the reboot clears it, or some problem in NSTL download, and redownloading it fixed it. .
check the known issues for the phone too

the only times i've seen this happen, is either memory fragmentation issues and the reboot clears it, or some problem in NSTL download, and redownloading it fixed it. .
check the known issues for the phone too

How about checking the BREW version that you used to compile? Some time that answers lot. If the application name itself is different, then chances are that app is not installed right. I have seen this happening in manual download itself. That one got resolved only be reloading the app after cleaning the old one.
Also check the s/w version that you and NSTL used.

How about checking the BREW version that you used to compile? Some time that answers lot. If the application name itself is different, then chances are that app is not installed right. I have seen this happening in manual download itself. That one got resolved only be reloading the app after cleaning the old one.
Also check the s/w version that you and NSTL used.

Charlie:
Sorry to be ignorant, where are known phone issues posted? I've been looking for them, can't find an entry point into that area.
Thanks for the help.

Charlie:
Sorry to be ignorant, where are known phone issues posted? I've been looking for them, can't find an entry point into that area.
Thanks for the help.

if you have access to extranet, this should show the list by carrier.
https://brewx.qualcomm.com/brew/sdk/authdownload.jsp?page=devices

if you have access to extranet, this should show the list by carrier.
https://brewx.qualcomm.com/brew/sdk/authdownload.jsp?page=devices

bru wrote:How about checking the BREW version that you used to compile? Some time that answers lot. If the application name itself is different, then chances are that app is not installed right. I have seen this happening in manual download itself. That one got resolved only be reloading the app after cleaning the old one.
Also check the s/w version that you and NSTL used.
I checked - the phones we tested on were RA1004, NSTL has RA1011. THere is a difference, but to the extent they have a higher release of the software, it seems less likely this is the root cause of our issues.

bru wrote:How about checking the BREW version that you used to compile? Some time that answers lot. If the application name itself is different, then chances are that app is not installed right. I have seen this happening in manual download itself. That one got resolved only be reloading the app after cleaning the old one.
Also check the s/w version that you and NSTL used.
I checked - the phones we tested on were RA1004, NSTL has RA1011. THere is a difference, but to the extent they have a higher release of the software, it seems less likely this is the root cause of our issues.

bru wrote:if you have access to extranet, this should show the list by carrier.
https://brewx.qualcomm.com/brew/sdk/authdownload.jsp?page=devices
I'm still feeling like there is something basic I am missing. I do have Extranet access, and I can get to the areas listing the specific BREW devices by carrier. I still can't find areas focusing on known phone issues. I can get the data sheet for the KX-13, stil am stumped on where to find issues.
Thanks for the patience and help.
- Sean

bru wrote:if you have access to extranet, this should show the list by carrier.
https://brewx.qualcomm.com/brew/sdk/authdownload.jsp?page=devices
I'm still feeling like there is something basic I am missing. I do have Extranet access, and I can get to the areas listing the specific BREW devices by carrier. I still can't find areas focusing on known phone issues. I can get the data sheet for the KX-13, stil am stumped on where to find issues.
Thanks for the patience and help.
- Sean

bru wrote:How about checking the BREW version that you used to compile? Some time that answers lot. If the application name itself is different, then chances are that app is not installed right. I have seen this happening in manual download itself. That one got resolved only be reloading the app after cleaning the old one.
Also check the s/w version that you and NSTL used.
I'll check the BREW version. We have tested the application on 4-5 different versions of this phone over many weeks, never seen anything like this, so woudl a BREW version problem only surface on ADS download?
Thanks again for all the help.

bru wrote:How about checking the BREW version that you used to compile? Some time that answers lot. If the application name itself is different, then chances are that app is not installed right. I have seen this happening in manual download itself. That one got resolved only be reloading the app after cleaning the old one.
Also check the s/w version that you and NSTL used.
I'll check the BREW version. We have tested the application on 4-5 different versions of this phone over many weeks, never seen anything like this, so woudl a BREW version problem only surface on ADS download?
Thanks again for all the help.

on the extranet use, list by manufacturer known issues are in there.

on the extranet use, list by manufacturer known issues are in there.

charliex wrote:on the extranet use, list by manufacturer known issues are in there.
Thanks - now I see them. :)

charliex wrote:on the extranet use, list by manufacturer known issues are in there.
Thanks - now I see them. :)

charliex wrote:the only times i've seen this happen, is either memory fragmentation issues and the reboot clears it, or some problem in NSTL download, and redownloading it fixed it. .
check the known issues for the phone too
The KX-13 shows as no reported errors - I guess the phone is perfect ;) .
I'll continue research - it still seems odd.

charliex wrote:the only times i've seen this happen, is either memory fragmentation issues and the reboot clears it, or some problem in NSTL download, and redownloading it fixed it. .
check the known issues for the phone too
The KX-13 shows as no reported errors - I guess the phone is perfect ;) .
I'll continue research - it still seems odd.

as i said, ask them to redownload it, i've had that report a few times over the years and i'm reasonably sure its always just gone away.

as i said, ask them to redownload it, i've had that report a few times over the years and i'm reasonably sure its always just gone away.

We resubmitted with a lower level of BREW compiled - gettign the same errors on 2 of the 3 phones we submited on. Anyone got additional ideas of where to look? I've heard soem discussios of needing to check the MIF version level, any ideas on that?

We resubmitted with a lower level of BREW compiled - gettign the same errors on 2 of the 3 phones we submited on. Anyone got additional ideas of where to look? I've heard soem discussios of needing to check the MIF version level, any ideas on that?

Hi
i got a simple workaround for u .. Post a message requiring the user to restart the handset after download.. let me know if this works with NSTL :D

Hi
i got a simple workaround for u .. Post a message requiring the user to restart the handset after download.. let me know if this works with NSTL :D

amarpreet99 wrote:Hi
i got a simple workaround for u .. Post a message requiring the user to restart the handset after download.. let me know if this works with NSTL :D
Uh...yeah, that would be a great way to throw away your testing fees.

amarpreet99 wrote:Hi
i got a simple workaround for u .. Post a message requiring the user to restart the handset after download.. let me know if this works with NSTL :D
Uh...yeah, that would be a great way to throw away your testing fees.