T720 w/USB Cable

[starscream]

Hello all,

Has anyone had the following experience?

Boot into Win2K, use the AppLoader and everything is fine. Then, when you power-cycle the phone a New Hardware Detected box comes up in Win2K showing a USB Device and says the driver failed to install which then makes the USB connection worthless. The "COM4" entry disappears from the AppLoader pulldown and I'm unable to talk to the phone again until I reboot.

The power cycle seems to be the trigger here - before I do that I can launch/close AppLoader, plug/unplug the USB cable, etc. But after the powercycle it all goes to crap. Obviously, this is getting annoying. Thanks!

- Richard.

[tom]

When i power cycle the T720 while it's connected by USB to Win2k, it doesn't give me that "new hardware detected" popup. It only did that the first time i connected the T720 after installing the USB drivers. Sounds like your drivers aren't properly installed.

However there are many times AppLoader won't detect a handset until i reboot my computer. I haven't been able to isolate the cause of this problem, but for me it's not the power-cycle. And it's not just the T720 either -- that happens to the VX2200 and the CDM-9500 too.

BTW, I noticed that you don't always have to power-cycle the handset after using the AppLoader. You do power-cycle when you first install your app. But later, if you only replace the MOD and BAR files, then you can launch the app without power-cycling the handset.

I think you only need to power-cycle it when you replace the SIG and maybe the MIF file. I'm sure you do if you replace the SIG file, but not sure about the MIF.

[tyndal]

I am using WinXP and have similar problems with the AppLoader.

You dont really need to reset/power cycle the phone if you are only changing mod/bar/data files, but just if you modify the mif files (and someone mentioned .sig files in another posting) Just make sure you arent running brew on the phone when you are adding/deleting the files ;)

I have found it is best to close the apploader application before connecting/disconnecting and power-cycling a phone (just do it by hand). otherwise, Often a proccess called OEMLayerServer.exe seems to be left running and ends up taking 100% cpu, at least according to the task manager, though there is no noticable slowdown of the machine. If you kill that process (and maybe disconnect/reconnect the phone as well), you should be able to use the apploader application again without rebooting.

Maybe Win2k has the same problem.

Actually im pretty surprized with XP, the only times i have had to reboot is when Visual Studio occasionally hangs when i am debugging brew apps (i dont use VS for anything else currently)

-Tyndal

[tom]

Yeah, I've seen that "OEMLayerServer.exe." process running before, but usually it's left there because i was trying to use The Shaker and it locked up so i've killed The Grinder app.

Then, if i kill the OEMLayerServer on my Win2k machine, i can't use AppLoader or The Grinder -- at that point i have to reboot. Usually the reboot fixes it.

But sometimes, it's so hosed that i have to reinstall a USB driver. That doesn't take long to do, but it is a hassle.

[charliex]

i see this on most phones, usually i connect to one usb port, connect, do the upload, close the apploader, run my app etc, changes upload, if it doesnt want to reconnect (usually if something bad happens) i switch usb ports, then reconnect, or go into the system properties unplug and refresh the ports.

a lot of the phones and drivers will install a com port, but apploader cant see them,other software can, since apploader doesn't allow you to specify the com port its academic though


It also wont be listed under ports in the system hardware, but its there and its listed under the actual usb driver