The apploader needs major improvements

[flarb]

Ok, can Qualcomm finally fix the apploader so that when a device crashes, it doesn't require a reboot to get the apploader to recognize the device again? This happens with both USB and serial devices. It's highly annoying. I've had to reboot like 8 times today trying to debug on one handset.

This has been a problem with apploader since day 1, and I think it really needs to be addressed.

[tyndal]

Yes, we definately need more stable software for development..

Can you just kill the OEMServerLayer.exe program from the task manager? it takes 100% cpu for me when something goes wrong, but if i kill that then restart the apploader (after disconnecting / reconnecting the phone), it usually works ok. Im using XP though... In another forum someone said this didnt help but it is worth a try.

[flarb]

Nice trick! I'll try this next time. (I'm using Win2k)

[msponer]

Exiting the apploader when you run code that may crash also works.

[flarb]

That never works for me, but killing that DLL process works perfectly! Woo hoo!

[Kevin]

Which version of Apploader are you guys using? I haven't seen this issue in a long time.

[flarb]

2.1.1 or whatever the latest one is. This problem is in every version of the apploader I've ever used.

[Kevin]

I will file a CR. Thanks for reporting it. Do you have specific steps that could help me reproduce it?

[flarb]

It seems to happen any time a device that is connected with the PC crashes. I've had the T606 come back from the dead on the serial connection before, but that's a rarity. Usually USB or Serial, if it crashes while connected to the PC (whether Apploader is open or not), that COM port the phone was attached to is no longer available when you bring up the Apploader again.

I'm using Win2k.

[Kevin]

The AppLoader doc has documented how to work around this issue (as you have found) by killing the OEMLayerServer. A CR is already on file for this, and I have made the developer aware that it is a larger issue for BREW developers that originally perceived. We are targeting the 3.0 release as the OEMLayerServer works with many QC Applications which will also undergo many changes at that time.

[Dragon]

While we're on the subject, Kevin, there's another thing that would be nice to change in regards to the AppLoader. Because of the issues Flarb and the others described, it is essentially necessary to exit AppLoader every time before launching an application on the phone because the risk of crashing the application and hence having to reboot the entire dev machine is just too high. I'll have to try killing the process ,though. that's sounds like a neat fix...

However, while going through this routine numerous times now, I noticed that AppLoader always defaults to its own directory when you select "New" to upload files to the device. It would be so great if the application could actually remember where I last uploaded files from, to speed up this step.

[polygonsheep]

Regarding adding files, I always use drag and drop from windows explorer.