Thedawn
02-01-2005, 04:28 AM
Whenever I try to connect to my Samsung SCH-N362 (either with AppLoader or with Logger version 3.0.0.12) it freezes for a minute or two, and then tells me that the connection failed. (Logger says "could not initialize device (error code 64)").
After that, when I try accessing the device as a modem, it fails as well (i.e. Query Modem in the device manager), which works perfectly fine if it don't try to use the Brew tools.
For it to work again, i need to restart the device.
For what it worth, the device is suppose to be test enabled.
Scenario:
1. Connect to USB
2. Restart device
3. Do Query Modem - returns a lot of bullshit, or use HyperTerminal
4. Try connecting with AppLoader or Logger - fails after a minute or so as if there isn't any device connected on that COM port
5. Do Query Modem again - fails
:(
It appears to be as if the device drivers I've downloaded from Samsung are incompatible with the Brew utils, while other modem utils work fine.
My other CDMA devices work fine with Brew tools.
WHY ME????
After that, when I try accessing the device as a modem, it fails as well (i.e. Query Modem in the device manager), which works perfectly fine if it don't try to use the Brew tools.
For it to work again, i need to restart the device.
For what it worth, the device is suppose to be test enabled.
Scenario:
1. Connect to USB
2. Restart device
3. Do Query Modem - returns a lot of bullshit, or use HyperTerminal
4. Try connecting with AppLoader or Logger - fails after a minute or so as if there isn't any device connected on that COM port
5. Do Query Modem again - fails
:(
It appears to be as if the device drivers I've downloaded from Samsung are incompatible with the Brew utils, while other modem utils work fine.
My other CDMA devices work fine with Brew tools.
WHY ME????