No compatible device detected | developer.brewmp.com No compatible device detected | developer.brewmp.com

Developer

No compatible device detected

From the Preferences dialog in Trigbuilder I'm trying to detect my device which is a Samsung A900.

For some reason the Trigbuilder cant detect it.

Using the BREW Apploader I can connect to the device and confirm that the necessary software modules are loaded. For example trigplayer, widgets, forms, extension3d and qc3dwidget. In addition all of the MIF files are on the handset.

I was able to install the BTIL client on the device and chose the ADS12arm9 I didn't get any signature errors during this process.

I'm using Trigbuilder version 5.2.0

Any ideas or thoughts appreciated.

Are you able to connect to the device through AppLoader using BTIL?
If not, then your device may not support BTIL (which means you're out of luck).
If you are, then you might be running into a problem with a COM port enumerated before your device port preventing the device from being detected. TrigBuilder enumerates through all available COM ports and attempts to detect devices. If a COM port misbehaves, it can prevent devices on later COM ports from being detected. You can try disabling COM ports to prevent the faulty port from interfering. Later versions of TrigBuilder allow you to manually specify a port and bypass the automatic detection.

Are you able to connect to the device through AppLoader using BTIL?
If not, then your device may not support BTIL (which means you're out of luck).
If you are, then you might be running into a problem with a COM port enumerated before your device port preventing the device from being detected. TrigBuilder enumerates through all available COM ports and attempts to detect devices. If a COM port misbehaves, it can prevent devices on later COM ports from being detected. You can try disabling COM ports to prevent the faulty port from interfering. Later versions of TrigBuilder allow you to manually specify a port and bypass the automatic detection.

I'm not able to connect AppLoader through the BTIL interface so I guess I am out of luck.
Thanks for the help :(

I'm not able to connect AppLoader through the BTIL interface so I guess I am out of luck.
Thanks for the help :(

mohlendo wrote:
If not, then your device may not support BTIL (which means you're out of luck).
If not able to connect my device though BTIL, what went wrong? any help?
thanks a lot

mohlendo wrote:
If not, then your device may not support BTIL (which means you're out of luck).
If not able to connect my device though BTIL, what went wrong? any help?
thanks a lot

Your device might just not support BTIL. If that's the case, you'll need to manually load your trigs using AppLoader.

Your device might just not support BTIL. If that's the case, you'll need to manually load your trigs using AppLoader.

Cool. Manual install. But how exactly does one do that? I'm exporting the parcel, unzipping the .zip file, then manually copying in the directory (containing mod, tmf), copying in the mif file, and finally putting the sig within the app dir. I still can't get the trig to show in the phone's app list however. I ensured that the BREW Launcher properties were set accordingly, but this still isn't working. Any ideas what's going wrong here?

Cool. Manual install. But how exactly does one do that? I'm exporting the parcel, unzipping the .zip file, then manually copying in the directory (containing mod, tmf), copying in the mif file, and finally putting the sig within the app dir. I still can't get the trig to show in the phone's app list however. I ensured that the BREW Launcher properties were set accordingly, but this still isn't working. Any ideas what's going wrong here?

Did you copy the MIF into the MIF directory? Are you using a unique class ID that's not being used by any other apps?

Did you copy the MIF into the MIF directory? Are you using a unique class ID that's not being used by any other apps?