Forums | developer.brewmp.com Forums | developer.brewmp.com

Developer

Forums

This is a problem with BTIL not getting log messages from:

1.) Component Services
2.) Anything in a .mod1/.dll1
3.) AMSS

It is an inherent limitation in the way BTIL intercepts log messages. We advise users to use "COM/Diag" or Gateway for this very reason which should give them access to #1 and #2 (but by design *not* #3).

To clarify further, we have two means of connecting to a device:
1. Brew MP driver (Developer Mode), often referred to as Gateway, requires manual install of PC driver after menu item on phone entitled "Developer Mode" is enabled.  The driver install on Windows can be auto found by Windows Driver Wizard after installing Brew MP SDK.  Also, Developer Mode can be enabled via USB on Brew MP devices, after Brew MP driver is installed and OEM Mode COM/DIAG connection is made to the device.
2. OEM driver (OEM Mode), PC driver install is often auto detected and installed when hot plugged to PC.  Brew MP tools refer to such device connections as COM/DIAG or MODEM as this is how they register under r Windows Device Manager.
 
The COM/DIAG, MODEM and BTIL, are dialog options when establishing a session with the tools called Loader and Logger.  BTIL is an client / server method of communicating between PC and Brew MP Device.  The BTIL agent is good for some tool operations, but has proved ineffective when using Logger.   Logger is better serviced without intervening agent.  Also, use COM/DIAG as opposed to MODEM when using Logger.
 

To clarify further, we have two means of connecting to a device:
1. Brew MP driver (Developer Mode), often referred to as Gateway, requires manual install of PC driver after menu item on phone entitled "Developer Mode" is enabled.  The driver install on Windows can be auto found by Windows Driver Wizard after installing Brew MP SDK.  Also, Developer Mode can be enabled via USB on Brew MP devices, after Brew MP driver is installed and OEM Mode COM/DIAG connection is made to the device.
2. OEM driver (OEM Mode), PC driver install is often auto detected and installed when hot plugged to PC.  Brew MP tools refer to such device connections as COM/DIAG or MODEM as this is how they register under r Windows Device Manager.
 
The COM/DIAG, MODEM and BTIL, are dialog options when establishing a session with the tools called Loader and Logger.  BTIL is an client / server method of communicating between PC and Brew MP Device.  The BTIL agent is good for some tool operations, but has proved ineffective when using Logger.   Logger is better serviced without intervening agent.  Also, use COM/DIAG as opposed to MODEM when using Logger.