Logo of Binary Runtime Environment for Wireless
Logo of Binary Runtime Environment for Wireless

Binary Runtime Environment for Wireless (Brew MP, Brew, Qualcomm BREW, or BREW) is an application development platform created by Qualcomm, originally for code division multiple access (CDMA) mobile phones, featuring third-party applications such as mobile games. It is offered in some feature phones (mostly with specifications similar to those of mid to high-end mobile phones) but not in smartphones. First developed in 1999, as a platform for wireless applications on CDMA-based mobile phones, it debuted in September 2001. As a software platform that can download and run small programs for playing games, sending messages, and sharing photos, the main advantage of Brew MP is that the application developers can easily port their applications among all Brew MP devices by providing a standardized set of application programming interfaces. Software for Brew MP enabled handsets can be developed in C or C++ using the freely downloadable Brew MP software development kit (SDK).[1] The BREW runtime library is part of the wireless device on-chip firmware or operating system to allow programmers to develop applications without needing to code for system interface or understand wireless applications. BREW is described as a pseudo operating system, but not a true mobile operating system. BREW is not a virtual machine such as Java ME, but it runs a native code.

Software

For software developers, Brew MP is a full set of application programming interfaces (API) that enables making software and applications in C, C++, Java, and is supported (platform) by an application-specific integrated circuit (ASIC). It has a memory footprint of about 15,900 K (15.9 MB), From 1.x until 2.x (before 2004), it has less memory footprint (around 60kb). BREW also features direct hardware access. Versions before Brew MP ran/relied on REX OS (Qualcomm's own RTOS), while Brew MP uses Brew RTOS (another RTOS for advanced feature phones). Rather than using an interpreter-based code, BREW also relied on its own mobile hardware.

Version history

BREW 1.0 / 1.1 (2001–2003)

Debuted in 2001, it was the first actual version of BREW. Originally made for the Kyocera QCP-3035 (which was the earliest BREW-enabled phone commercially available) and Sharp Z-800. It made use of personal digital assistant-level features (usually for some applications and the ability to run BREW applications). However, it lacks advanced multimedia features and support for Java ME that were available in subsequent versions. It was the only version of BREW to support monochrome screens as support for monochrome screens were removed in BREW 2.0. BREW 1.1 was the first version of Brew to run Java ME applications. It was available in some BREW-enabled phones in 2002 and early 2003.

BREW 2.0 / 2.1 (2002–2009)

Released in the mid-2002, it was installed for most of the BREW-enabled phones in late-2002 until late-2009. It includes support for advanced multimedia playbacks (the ability to play video and audio files, as well as support for 3GPP multimedia formats), connectivity for EV-DO and Bluetooth support, as well as screen savers and other improvements. It also supports MIDP 2.0 on BREW 2.1 and it is backwards compatible with BREW 1.x applications.

It was installed on most feature phones in the Indonesia, China, and in other countries since 2004 and it is still supported by a few carriers until 2017.

BREW 3.0 / 3.1 (2004–2012)

Released in the mid-2002, it was installed for most of the BREW-enabled phones in late-2004 until early-2012. It was the first version of BREW to have major changes and it has a vast majority of features for mobile phones, such as WiFi connectivity, OpenGL ES 1.0, support for 3G, GPS, QWERTY-based keypads, and support for mobile screens that are higher than 176x220. It is backwards compatible with BREW 2.x applications, but not with BREW 1.x applications.

It is also the first version of BREW to support 3D graphics rendering, althrough it only uses software rendering (which also supports JSR 184 for Java ME games). Hardware acceleration is also natively supported via OpenGL ES 1.0 (if a 3D acceleration chip is available).

It was installed on most feature phones in the United States and in other countries since 2005 and it is still supported by a few carriers.

BREW 4.0.1 - 4.0.2 (2007–2011)

Released in 2007 until 2011, it was only integrated on very few mobile phones (such as LG enV Touch and the LG Versa). It has only a few improvements and it was later succeeded by Brew MP. It has additional features that are also available in Brew MP, such as accelerometer support and other changes.

It is also used for the Zeebo console in Mexico and Brazil.

Brew MP 1.0.1 - 1.0.4 (2009–2021)

Released in 2009, internally known as BREW 5.0, it has new various features (including SVG images support) and certain improvements and it is backwards compatible with BREW 3.x and 4.x applications. It is also the first version of BREW to make certain APIs and legacy files deprecated. It is also the first version of BREW to rely on its own RTOS rather than Qualcomm's own REX OS.

The Brew MP developer page was shut down in 23 July 2021 due to inactivity for 8 years ago.

BREW application development

For testing applications during the development process, the SDK includes a BREW emulator, or starting with BREW version 1.1 and above, the BREW Simulator. The BREW environment provides for multiple levels of application signatures. One signature authenticates the developer. Another signature verifies that an application has passed True BREW testing and is bestowed through Intertek. The individual telecommunications operators configure the handsets to either enforce or ignore the presence and verification of this second signature. BREW-enabled handsets have a test mode that allows applications to bypass verification of the signature. Qualcomm makes applications that have passed testing available to BREW-enabled wireless network operators. The operators are then able to choose which of these applications to make available to end-users on their catalog.

BREW's own signatures is protected by an Electronic Serial Number (ESN) and a Mobile Equipment Identifier (MEID), this means it prevents the unauthorized distribution/sideloading of BREW applications to 3rd-parties rather than carriers. Once the application is downloaded OTA via a BREW-based carrier, the .sig file will automatically generate an electronic serial number to its installed handset.

The BREW emulator, named BREW Simulator, does not emulate handset hardware. Instead, the BREW application is compiled to native code and linked with a compatible BREW runtime library. Because of this, applications cannot be tested for platform bugs related to memory alignment and various firmware related glitches without a BREW handset operating in test mode.

For testing purposes, BREW applications can be transferred using a Universal Serial Bus (USB) or serial cable to any BREW-compatible handset using BREW App Loader from Qualcomm. A BREW application contains several components which, if not present and valid, cause the application to be automatically deleted on reboot. This includes the compiled binary file, a file which describes the application, the features it uses and permissions requested, a file that contains string and image resources if required, and a file containing the application's digital signature.

BREW applications may be unloaded from a consumer handset to save handset memory space. This is referred to as "Disable/Restore", and is a requirement of the True BREW Test Process. Saved files are kept intact using Disable/Restore, and it is possible to re-load the application without paying for it again. In a "Disable" situation, all .bar, .mod, and .sig files are deleted from the handset, while any other files remain in their original place. During the "Restore" operation, the .bar, .mod, and.sig files are downloaded from the carrier's mobile store, and the previously disabled application will have full functionality remaining. The Disable/Restore process is only available to consumer users once the handset's memory is full.

On May 28, 2008, Qualcomm and Adobe announced a partnership to integrate Adobe Flash Lite as a supported user interface on BREW.

Since March 2006, the least expensive digital signature package for developers costs US$400 for 100 application submissions.[2]

Business model implications/availability

Strictly speaking, time to market can take longer with BREW than with Java ME because of Qualcomm BREW's rigorous certification requirements. This certification process may be perceived as an advantage by established software developers because the difficulties associated with testing and development costs create a high cost of entry to developers with low budgets and little time, resulting in less market dilution. Specifically, developers of casual games run less risk of having to compete with freeware workalikes developed and self-published by hobbyists. However this comes as a cost to the end-user as there is less competition to develop the best solution at the lowest price to the end user.

Differences between Java ME and BREW

Currently, most developers choose to support both Java ME and BREW, or only Java ME.[citation needed] Java ME may offer a lower cost to market because most carriers allow non-certified Java ME applications to run on their phones. Java ME phones have a larger market share than BREW enabled handsets. Java ME is widely used in Europe, while BREW is primarily used in the U.S. and Japan. Even in the U.S.[citation needed] One of the initial advantages of BREW was that Verizon made it easy to purchase applications from the phone, while most Java ME carriers did not. However, most carriers of Java ME phones now offer easy-to-access purchasing portals.

Owing to its different APIs, Java ME relies on Java's virtual machine (interpreter-based code), which is technically slower than BREW, which uses native C/C++ plus and direct hardware access (especially for games).[3] Java ME has limited subset of APIs (both for applications and games). However, 3rd-party APIs and implementations (such as MascotCapsule by HI CORPORATION. (3D rendering API) and DoJa/Star by NTT Docomo) are available, but not popular and successful outside Japan (particularly device adoption). BREW (on the other hand), relies on its own APIs and direct hardware access.

Performance for Java ME applications and games are slow than BREW. For 3D games, Java ME uses JSR 184 (M3G), which 3D games that are developed on Java ME are slower (which results in 10 frames per second on some/most handsets) and have limited graphics, while BREW uses either software rendering (if the BREW handset does not have a 3D acceleration chip) or OpenGL ES (which it can take advantage of its performance).[4]

Unlike the Java ME, when the BREW application crashes, the phone will cause reboot due to BREW can't handle and recover while the application crashes, it creates "$SYS.EXCEPT_(4-Digit Number)" into the "except" folder on the root of directory, then the phone will automatically reboot by itself, when the Java ME application crashes under BREW, Java ME will handle correctly and recover them from phone rebooting by itself.

Some/few handset manufacturers do not allow to integrate Java ME's virtual machine on a few of their phones.

There are now commercial technologies to fully automate porting from Java ME to BREW. This reduces the entry barrier to produce BREW applications by eliminating the need to develop two versions of the same application in both Java and C/C++.

System Failure

System Failure in BREW is caused by the components are stopped working properly, a file required for an BREW application is missing, application crash, or some other errors. It creates the "$SYS.EXCEPT_XXXX" file inside the "except" folder on the root of directory. BREW's System Failure has 2 variants, the "Component Error" and the "Reboot of Death (RoD)".

Component Error (example.c XXXXX)

BREW 2.0.2 Component Error on the Samsung SCH-S399.
BREW 2.0.2 Component Error on the Samsung SCH-S399.
$SYS.EXCEPT_0002 affected by the Component Error in Notepad.
$SYS.EXCEPT_0002 affected by the Component Error in Notepad.

Component Error is an error that will display an black, white, or blue screen with an error text for about 5 seconds if the components are stopped working properly, then the phone will reboot by itself. this error may vary depending on your activity, for example:

• fs_dir.c (File System Error)

• mdsptask.c (Task Error)

• oemheap3x.c (Heap Violation)

• memory.c (Memory Corruption)

• nvm.c (NVM Check Violation)

• srch_mdsp.c (Index Error)

• callheap.c (Call Error)

Rarity of this variant to occur are very rare, generally, crashing BREW can lead to system reboot without black, white, or blue screen with text, it's known as the "Reboot of Death (RoD)". Here's the example of this activities to trigger this variant:

• Undervolting the phone while it's running, it will cause memory corruption ( Usually if the battery is near flat, on modern devices, undervoltage protection was added) (e.g. LG VX10, LG VX4400, LG PM225)

• The phone is at defective condition, usually, the phone will trigger the "Reboot of Death (RoD)" variant, which it will restart itself without black/white/blue screen with text. (e.g. Nokia 1325)

• "brew", "nvm", or ".efs_private" folder is removed. (fs_dir.c or nvm.c)

Reboot of Death (RoD)

$SYS.EXCEPT_0003 affected by the Reboot of Death (RoD) in Notepad, has some random characters.
$SYS.EXCEPT_0003 affected by the Reboot of Death (RoD) in Notepad, has some random characters.

Reboot of Death (RoD) is an error that will reboot the phone by itself instead of displaying an black, white, or blue screen with text known as "Component Error", rarity of this variant to occur are common, Here's the example of this activities to trigger this variant:

• Crashing an application.

• Removing the R-UIM card.

• The phone is at defective condition.

• Incorrectly entering an SP code.

• Application that requires files are missing.

• Running the exception test on engineering mode.


For Example:

Device usage and carrier availability

BREW 1.0 - 1.1 App Manager (2001-2003) (e.g. LG VX4400) (Screenshot 1)
BREW 1.0 - 1.1 App Manager (2001-2003) (e.g. LG VX4400) (Screenshot 1)
BREW 1.0 - 1.1 App Manager (2001-2003) (Screenshot 2)
BREW 1.0 - 1.1 App Manager (2001-2003) (Screenshot 2)
BREW 1.0 - 1.1 App Manager (2001-2003) (Screenshot 3)
BREW 1.0 - 1.1 App Manager (2001-2003) (Screenshot 3)
BREW 2.0.1 - 2.1.2 App Manager (2002-2009) (e.g. LG VI5225, ZTE S100, Ubiquam U-105, and most CDMA feature phones running BREW 2.0.2 or 2.1.2)
BREW 2.0.1 - 2.1.2 App Manager (2002-2009) (e.g. LG VI5225, ZTE S100, Ubiquam U-105, and most CDMA feature phones running BREW 2.0.2 or 2.1.2)
BREW 3.0.1 - 3.1.2 App Manager (2004-2009) (e.g. LG VX3400, Samsung SCH-A630, LG VX8600 Chocolate Flip, and some CDMA feature phones. Including most BREW SDKs
BREW 3.0.1 - 3.1.2 App Manager (2004-2009) (e.g. LG VX3400, Samsung SCH-A630, LG VX8600 Chocolate Flip, and some CDMA feature phones. Including most BREW SDKs
BREW 3.1.4 - 4.0.2 App Manager (2005-2012) (e.g. Zeebo, Samsung SCH-R351 Freeform, LG Voyager VX10000, and some CDMA feature phones. Including BREW SDKs)
BREW 3.1.4 - 4.0.2 App Manager (2005-2012) (e.g. Zeebo, Samsung SCH-R351 Freeform, LG Voyager VX10000, and some CDMA feature phones. Including BREW SDKs)
BREW MP 1.0.1 - 1.0.4 App Manager (2009-2015) (e.g. Pantech Verse, Samsung SCH-R270 Chrono 2, and few CDMA feature phones)
BREW MP 1.0.1 - 1.0.4 App Manager (2009-2015) (e.g. Pantech Verse, Samsung SCH-R270 Chrono 2, and few CDMA feature phones)
Partially Branded BREW App Manager
Partially Branded BREW App Manager
Heavily Branded BREW App Manager
Heavily Branded BREW App Manager

Qualcomm BREW is used by some mobile phone manufacturers and mobile networks, however most often the end-user does not know this since mobile phones running BREW most often lack any Qualcomm BREW branding and BREW runs in the background with the custom "skins" of the mobile phone manufacturer or operator on-top. Qualcomm BREW is used by Sprint Nextel, metroPCS, U.S. Cellular, Verizon, Syringa Wireless, Cricket Wireless, and AT&T (in the HTC Freestyle) in the US, KDDI in Japan, KT and SK Telecom in South Korea, China Telecom in China, MOVILNET in Latin America, Sistema Shyam (now MTS) in India, and by the 3 network in much of Europe, the UK and Australia on many mobile phones produced especially for their network.

Because BREW is only offered to mobile networks that operates in CDMA, other countries (with the exception of parts of Europe, the UK and Australia via the 3 network, India, Japan and China) do not have BREW, because they do not have CDMA networks.

Manufacturers such as Huawei, INQ Mobile, Amoi, LG, Samsung Mobile, ZTE, and HTC amongst others use Qualcomm BREW in some of their mobile phones and it is featured in 3 UK phones such as the 3 Skypephone, INQ1, ZTE Z431, LG T385 and Huawei u7510 (3 Touch). Tectoy's Zeebo is the only game console to use BREW. Motorola's own T720 as well as the RAZR V3m also use Qualcomm BREW.

See also

References

  1. ^ SDK & Tools | Brew MP Developer Archived 2012-12-17 at archive.today. Developer.brewmp.com. Retrieved on 2013-07-21.
  2. ^ Code Signing Certificates for Authentic Document IDs for BREW - Digital Signatures | Symantec Archived February 5, 2009, at the Wayback Machine. Verisign.com. Retrieved on 2013-07-21.
  3. ^ "Choosing between J2ME and BREW for wireless development - TechRepublic". TechRepublic. Retrieved 2017-06-21.
  4. ^ "See the graphical difference between Java and BREW games". Pocket Gamer. Retrieved 2017-06-21.