App Loader 3.1 can't connect but app Loader 2.1 can connect | developer.brewmp.com App Loader 3.1 can't connect but app Loader 2.1 can connect | developer.brewmp.com

Developer

App Loader 3.1 can't connect but app Loader 2.1 can connect

We are having issues where we can't connect to a Samsung U340 and a Samsung U410 using App Loader 3.1. However, we are able to connect using App Loader 2.1. The U340 is BREW version 2.1.3 while the U410 is BREW version 3.1.4. Has anyone else seen this problem?

We were able to load the application on the U410 using App Loader 2.1. However, when we reboot the phone the application is not listed under Verizon's Get More Pictures (it is a wallpaper application). Therefore we can't run it on the phone.

Any suggestions?

Thanks!

If I remember correctly, I had issues connecting to the U340. Either I used EFS Explorer, or I explicitly set the EFS version to 1. I can't remember which at the moment.
If it was the EFS version, you have to set the following in your QCOMOEM.INI file:
[Detection Information]
ManualDetect=Yes

If I remember correctly, I had issues connecting to the U340. Either I used EFS Explorer, or I explicitly set the EFS version to 1. I can't remember which at the moment.
If it was the EFS version, you have to set the following in your QCOMOEM.INI file:
[Detection Information]
ManualDetect=Yes

hi
i actually req brew 2.1 Appliction loader,if you can tell me where to search n find
the above.
regards
ashu

hi
i actually req brew 2.1 Appliction loader,if you can tell me where to search n find
the above.
regards
ashu

I am able to load applications using Apploader version 3.1, but unable to find them after a power cycle.

I am able to load applications using Apploader version 3.1, but unable to find them after a power cycle.

Here are a few common reasons that I have found for an app to not show up after a power cycle that you might want to check out:

Phone not test enabled
Loading with incorrect BREW version (make sure you select "1.x/2.x" or "3.x and later" corresponding to the BREW version on the phone)
Invalid MIF file (wrong version, incorrect images, or just corrupt)
Invalid or missing test signature
File system full (many times the files will appear to have loaded correctly, but then will vanish after the phone is power cycled)
Looking in the wrong location (on some Verizon 3.x handsets, all apps will be put into "Get Going", no matter what the MIF file is set to, for example)

If it is not any one of these, is the application still on the phone and you just can't find it in the BREW app manager or is it being deleted after a power cycle? Also, what phone are you having a problem with and where are you looking for your application?
Also, it doesn't exactly seem like this is related to the original thread, so you might have wanted to create a new thread for your issue. Unless you are actually having a problem with the Samsung U340 or Samsung U410 and you tried the suggestion presented but it didn't work, in which case it might have been helpful to indicate that.

Here are a few common reasons that I have found for an app to not show up after a power cycle that you might want to check out:

Phone not test enabled
Loading with incorrect BREW version (make sure you select "1.x/2.x" or "3.x and later" corresponding to the BREW version on the phone)
Invalid MIF file (wrong version, incorrect images, or just corrupt)
Invalid or missing test signature
File system full (many times the files will appear to have loaded correctly, but then will vanish after the phone is power cycled)
Looking in the wrong location (on some Verizon 3.x handsets, all apps will be put into "Get Going", no matter what the MIF file is set to, for example)

If it is not any one of these, is the application still on the phone and you just can't find it in the BREW app manager or is it being deleted after a power cycle? Also, what phone are you having a problem with and where are you looking for your application?
Also, it doesn't exactly seem like this is related to the original thread, so you might have wanted to create a new thread for your issue. Unless you are actually having a problem with the Samsung U340 or Samsung U410 and you tried the suggestion presented but it didn't work, in which case it might have been helpful to indicate that.

You were right. I was loading with BREW 2 instead of BREW as I should have been. Thank you.

You were right. I was loading with BREW 2 instead of BREW as I should have been. Thank you.