Resources | developer.brewmp.com Resources | developer.brewmp.com

Developer

resources

Developer Mode enable

Developer Mode enable is the action of unlocking the phone to be able to use development tools and run code produced by the developer.

Brew MP Tools support the Developer Enablement Service (DES) or a Developer Enablement Signature. When using Brew MP Loader or Logger to connect to a device that does not have a valid signature file, a dialog will appear prompting you to use one of the following two methods to unlock the phone.

  • DES - Enable the device using a developer.brewmp.com username and password. Privileges for the devices are based off of username credentials. This is the preferred enablement method for Brew MP devices.

    Note: To use DES, you must be an authenticated developer. For more information, click Get Authenticated on the http://developer.brewmp.com.

    Enablement can be performed by using any Qualcomm tool that uses Connect. The Brew MP Connect Tool (CT) can be used to enable the device as well.

  • Developer Enablement Signature or signature file enable - Distributors, operators, and OEM manufactures often have the ability to generate signature files. These files provide privileges, according to the creator, to run code on the device. This is the common method to enable phones working off of a BREW distribution system. This is the only enablement path for BREW 3.x and 4.x devices. The Signature file needs to be installed on the device.

Development Enable Service (DES)

This Internet-based service is no longer available. To enable development mode on your device, use a Developer Enablement Signature. To use DES, you must be an authenticated developer. For more information, click Get Authenticated on the http://developer.brewmp.com.

The steps for using the DES are as follows:

  1. Obtain an account (a username and password) on the Brew MP website.
  2. Download the Brew MP SDK to your PC.
  3. Make sure the PC is connected to the Internet.
  4. Configure and connect the device to the PC as mentioned in the section on Device plugin and driver setup.
  5. Establish a device connection using Target Manager, as follows:
    1. In Target Manager, double-click on your device.

      A Properties window for the device will be displayed.

    2. Select the Developer Mode tab.
    3. Select Developer Mode Enablement Service.
    4. Enter your Brew MP Website username and password and click Enable.

      You should see a confirmation message indicating the device is enabled and the Lock icon will disappear from Target Manager.

    The device can be disconnected and it will remain enabled until the enablement expires.

Accounts

Brew MP Developer website accounts are limited in three ways:

  • Privilege -- The developer enablements granted for the username and password have limited privilege.
  • Expiration -- If the expiration for an account is 2 days, the enablements granted will have an expiration date two days after the grant was made.
  • Number of devices -- Each account may only have a limited number of devices enabled at a time.

An account is associated with one of two tiers:

  • Authenticated Developer (Tier 2)

    For more information, click Get Authenticated on the http://developer.brewmp.com. The Authenticated Developer tier privileges have limits. For more information, see the Device Code Security Technology Guide.

  • System Tier

    This tier is for OEMs and requires a Qualcomm AMSS Master Software Agreement. The System tier has all privileges.

When a developer has enabled the maximum number of devices that is allowed, no more devices can be enabled. Enablement on a device has to expire before another can be enabled.

Developer Enablement Signatures

A development enable signature is a digital signature designed to enable the application developer. It's a file with the .sig extension. Note that not all .sig files are development enable signatures. Each developer enablement signature has a set of privileges and an expiration date, like enablement via DES. Developer enablement signatures are tied to a specific device by the device ID (IMEI or ESN, for example). These signature files are installed on the device using Brew MP Target Manager, Loader, Logger, or the Connect Tool provided in the SDK. The tool prompts for the location of the signature file on your PC and copies it to the device. Once the sig file is copied to the device, the device is in development mode.

Developer Enablement Signatures are used internally by device manufacturers. Device manufacturers can issue their own Developer Enablement Signatures if they are a signing authority with access to a code authorization signing service. In addition, Developer Enablement Signatures can be requested from a Qualcomm Brew MP product representative. The exception is legacy BREW Test Enable Signatures. On many devices, test enable signatures can be used to put the device into developer mode by installing the test enable signature as a Developer Enablement Signature. Test enable signatures have very few privilege limitations and usually have an expiration period of several months. These signatures are available on the legacy BREW Developer Extranet, and require authentication and signing a legal agreement. These test enable signatures only work on devices on certain operators networks.

Device Support

Support for developer enabling devices varies by device manufacturer and by the device operator's network. Most Brew MP devices support the Developer Enablement Service. Legacy BREW devices do not.

Certain device manufacturers and certain operators may choose either to disable the Developer Enablement Service or limit the privilege they allow. For example an operator may choose to disallow access to the position location services and a device manufacturer may disallow access to copyrighted content. If there is a difference in the privileges, duration, or number of devices allowed for a Brew MP Developer website account and what is received on a specific device, it may be due to limits placed by the OEM and operator (there may be notifications and a display of this in some situations).

Test Enable Signatures

BREW supports test enable signatures. Test signatures have been the primary means of enabling code under development to on commercial devices live on operator networks. They are still supported, but Developer Mode Enable using the DES is now preferred.

The standard way of using test signatures is to copy the .sig file into the main application directory and install it with the application. There is a test signature for every application. This step is no longer required with Developer Enablement Signatures with Brew MP 1.0 and newer devices. This step is still required for Brew 3.x/4.x devices. The test signature can be installed on the device using the Brew MP SDK, and a device in Developer Mode does not require a test sig to be copied to the device with each application.

Some of the newer development tools in the SDK require the device to be in Developer Mode before the tools will run. Developer Mode enables some services on the USB port that are normally disabled. To use these tools with a test signature, the test signature has to be installed as a Developer Enablement Signature. Copying the test signature into an application's directory and installing the application will not enable Developer Mode.

Development Mode Signatures can be any .sig file from any version of BREW. All .sig file formats are supported. Some operators are using a different application download system, on which BREW Developer Extranet test signatures may not work.