Kyocera KX 414 | developer.brewmp.com Kyocera KX 414 | developer.brewmp.com

Developer

Kyocera KX 414

Forums:

after downloading my app into Kyocera KX 414, I cannot see my app in Get It Now!
and even worse, the app I downloaded would be deleted after I power cycle the phone...
Does any have similar problem? Please help...

Thanks in advance,
Jean

Did you have the test flag enabled on the phone (did you send it in to qualcomm?)
check out Step 5 here:
http://www.qualcomm.com/brew/developer/resources/ds/kb/49.html
-Tyndal

Did you have the test flag enabled on the phone (did you send it in to qualcomm?)
check out Step 5 here:
http://www.qualcomm.com/brew/developer/resources/ds/kb/49.html
-Tyndal

We haven't had any trouble with the KX414 so far.

We haven't had any trouble with the KX414 so far.

We had an issue like that once when we didn't upload the sig file right away, we rebooted, uploaded everything with the sig and it stuck fine.
Curt

We had an issue like that once when we didn't upload the sig file right away, we rebooted, uploaded everything with the sig and it stuck fine.
Curt

We're having this problem also.
I've tried pulling two SIGs from the BREW SIG Generator (in case I had a typo in the ESN; its happened before), and all three MIF versions v1.00, v2.00, and v2.0b. I also tried a smaller image in the MIF, making it a copy of the icon like I do for the A530, just in case.
In every case the app is deleted on power cycle. I *think* that the phone is test-enabled, but this behavior is consistent with a phone which is not test-enabled (as per tyndal's link above). Does anybody know how to confirm that the phone is test-enabled before I ship it back to San Diego?
midringtones: did you just use the per-file load in the AppLoader, or did you use per-module load? Typically I load via the Perl interface to the AppLoader, using per-file copies, but I've never had this problem before and after all, it's a new, quirky, BREW device. I'm wondering if that makes a difference.
Thanks,
-Jesse

We're having this problem also.
I've tried pulling two SIGs from the BREW SIG Generator (in case I had a typo in the ESN; its happened before), and all three MIF versions v1.00, v2.00, and v2.0b. I also tried a smaller image in the MIF, making it a copy of the icon like I do for the A530, just in case.
In every case the app is deleted on power cycle. I *think* that the phone is test-enabled, but this behavior is consistent with a phone which is not test-enabled (as per tyndal's link above). Does anybody know how to confirm that the phone is test-enabled before I ship it back to San Diego?
midringtones: did you just use the per-file load in the AppLoader, or did you use per-module load? Typically I load via the Perl interface to the AppLoader, using per-file copies, but I've never had this problem before and after all, it's a new, quirky, BREW device. I'm wondering if that makes a difference.
Thanks,
-Jesse

I have confirmed the above problem and fix: we sent the KX414 down to QUALCOMM for test enabling and when it came back the problem was gone: it turns out somebody *told* us that the phone was test enabeld, but it wasn't.

I have confirmed the above problem and fix: we sent the KX414 down to QUALCOMM for test enabling and when it came back the problem was gone: it turns out somebody *told* us that the phone was test enabeld, but it wasn't.

I'm having exactly the same problems with my Kyocera KX414c as described above. Is there any way to determine if it is test-enabled before I send it back to Qualcomm? I am able to enter debug mode on it though.
I did that with my Audiovox 8400 and it still hasn't returned... it is close to 2 months already...

I'm having exactly the same problems with my Kyocera KX414c as described above. Is there any way to determine if it is test-enabled before I send it back to Qualcomm? I am able to enter debug mode on it though.
I did that with my Audiovox 8400 and it still hasn't returned... it is close to 2 months already...

My 414 acted as if it the test bit wasn't enabled also.
However, I suspect it might be like the A530 and require that the clock be set beyond the date that the .sig was generated. (most phones don't seem to care?)
But unlike the A530, I cannot find a way to set the clock manually and I'm not in an area with CDMA. Out of 9 phones it's the only one I couldn't get going.
I wish there was a way to check the test-bit easily on this phone to be able to rule that out!

My 414 acted as if it the test bit wasn't enabled also.
However, I suspect it might be like the A530 and require that the clock be set beyond the date that the .sig was generated. (most phones don't seem to care?)
But unlike the A530, I cannot find a way to set the clock manually and I'm not in an area with CDMA. Out of 9 phones it's the only one I couldn't get going.
I wish there was a way to check the test-bit easily on this phone to be able to rule that out!

Does the ###[dbgmode] feature work on all phones, even those that are not test enabled?

Does the ###[dbgmode] feature work on all phones, even those that are not test enabled?

I just grabbed hold of an LG VX6000 Verizon phone bought off the shelf, which was not sent to Qualcomm yet. Apparently
###[Debug Mode] seems to work on such non-test enabled phones.
Has anyone tried this with any other phone? So it appears that debug mode is not a good indicator of whether it is test-enabled or not.

I just grabbed hold of an LG VX6000 Verizon phone bought off the shelf, which was not sent to Qualcomm yet. Apparently
###[Debug Mode] seems to work on such non-test enabled phones.
Has anyone tried this with any other phone? So it appears that debug mode is not a good indicator of whether it is test-enabled or not.

Well, if that's the case (that you can enter debug modes without the phone being test enabled) then maybe I'm not going crazy either. I've been trying to get my app to stick on a kyocera slider and I was under the assuption that it was test enabled because I could put it in the debug modes with ###. Unfortunately, the rest of my phones are test enabled, so I don't have any off-the-shelf phones around here to compare against right now.

Well, if that's the case (that you can enter debug modes without the phone being test enabled) then maybe I'm not going crazy either. I've been trying to get my app to stick on a kyocera slider and I was under the assuption that it was test enabled because I could put it in the debug modes with ###. Unfortunately, the rest of my phones are test enabled, so I don't have any off-the-shelf phones around here to compare against right now.

Ok, I've received confirmation from BREW support that the debug modes will work on a non-test enabled phone as well. We conclude that entering debug mode is not indicative of whether a phone is test enabled or not. So what is? *scratches head*

Ok, I've received confirmation from BREW support that the debug modes will work on a non-test enabled phone as well. We conclude that entering debug mode is not indicative of whether a phone is test enabled or not. So what is? *scratches head*

If an app with a valid sig file sticks or not :) Seriously though, we have received phones from carriers that are supposed to be test bit enabled that aren't, I am sure that is the case. It is tough since it can take awhile to get things back from Qualcomm, but I believe sending it in is the only method.
Curt

If an app with a valid sig file sticks or not :) Seriously though, we have received phones from carriers that are supposed to be test bit enabled that aren't, I am sure that is the case. It is tough since it can take awhile to get things back from Qualcomm, but I believe sending it in is the only method.
Curt

I had the same problem, and the solution seems to be to use the 2.1 MIF editor to create a version 1.0 MIF. If you use a lower mif editor, the kyocera doesn't seem to like it

I had the same problem, and the solution seems to be to use the 2.1 MIF editor to create a version 1.0 MIF. If you use a lower mif editor, the kyocera doesn't seem to like it