Usability and other Issues with BREW 2.1.2 | developer.brewmp.com Usability and other Issues with BREW 2.1.2 | developer.brewmp.com

Developer

Usability and other Issues with BREW 2.1.2

Forums:

I often find that the new BREW tool is inferior than the previous version in few aspects.

1. Open up the tool, you get the dialog box to select COM port etc. Don't select anything, just try to close the dialog box without selecting any COM port, you get an error message saying that "... device id". I didn't select any thing or hit OK button, so I don't expect any error dialog. Bad usability issue.

2. Using the new tool connect to your device and now reset the phone, without closing the BREW tool window. When the phone comes up, the new tool does not detect and connect automatically, whereas the previous version of the BREW tool used to do that. You need to close the BREW tool completely and then restart the tool to connect to the device.
When you need to reset the phone many times, it is reallt irritating to restart the BREW tool again and again.

ruben

Yup, I've had the same irritations with the App Loader as well.
Perhaps the most irritating is when the phone is disconnected from the computer. If this happens and the connection was USB, the App Loader will time out after a minute or two. If the phone is not reconnected before this happens, a computer restart is required.
And restarting my computer to get it working does not sound ideal. There has to be an easier solution than this. (And yes, I've killed damn near every process in the task manager and still a reboot is required. Killing OEMLayerServer only seems to work with Serial cables.)
Orion

Yup, I've had the same irritations with the App Loader as well.
Perhaps the most irritating is when the phone is disconnected from the computer. If this happens and the connection was USB, the App Loader will time out after a minute or two. If the phone is not reconnected before this happens, a computer restart is required.
And restarting my computer to get it working does not sound ideal. There has to be an easier solution than this. (And yes, I've killed damn near every process in the task manager and still a reboot is required. Killing OEMLayerServer only seems to work with Serial cables.)
Orion