Test signature of 64-BREW application serialized in brew advanced and proficient-3G mobile value-added business operation, customization and development

Each application must have a valid digital signature (. Sig file) file to run on the target mobile phone. There are two types of digital signature files:

· Test signature: this is provided for registration developers' requests. A test Signature allows any application to run on a single device and only on this device. When applying for a test signature, you must provide the electronic serial code (ESN), IMEI, or meid of the target mobile phone.

· Commercial Signature: This type of signature is generated only when the application passes the true brew test. Unlike the test signature, the commercial signature enables a single application to run on any device. A commercial signature not only indicates that the application has passed the true brew test program, but also indicates that the application is intact, ensuring the integrity and consistency of the application.

Application. the Sig file must be the same as. the MOD file is stored in the same directory of the target mobile phone and must be the same. MOD files have the same file name. For example, if there is MyApp. moD, which must correspond to MyApp. SIG file. If the directory does not contain a valid. Sig file that belongs to one of the preceding two signatures, the aee layer will not start the application and will prompt an error message when running the application.

The test signature is generated by an Internet-based online tool named "testsig generator" on the developer's external network. The testsig generator creates a test signature file based on the mobile phone's ESN (or IMEI or meid. The signature file is valid for 90 days from the date of generation. After expiration, You need to generate a new signature file based on the information.