Beta Requests for MPA2.0 - OS Maint. Release (MC75A0 / MC31xx / MC91xx / MC55A0 / MC55N0 / MC9598/MC9590 / MC9596 / MC75A6 / ...

K Khazi-Syed Taheer Ahmed 3 years ago
0 0 0

The MPA2.0 OS Maintenance Release (MR) program is currently in T&V FC2 stage for our next release targeted for the January 2013 timeframe on the following products:

MC9590, MC9596, MC9598
MC75A0, MC75A6, MC75A8
MC3190 WM6.5, MC3190 CE6
 MC55A0, MC55N0 WM6.5
 MC9190 CE6.0

General highlights of this release:

WM 6.5:

WEHH AKU 6.5.3.12.24 Build 29193
MSP Components - v7.08.42
Stone Street Bluetooth Stack - v2.1.1.27990
Fusion 3.00.2.0.029R
Updated RIL (GSM/CDMA): HSDPA:            RIL 1.1.6.129               USB Client 01.01.01.99               MUX 01.03.02.299
CDMA:               RIL v3.28               swivsp.dll v1.29
DataWedge - v3.6. 8
Document Capture Feature v2.0
TEAM Express v1.1.62.0000
eMScript CAB Installer  is included in the OS Image

 CE6:

Built with Aug 2013 QFE (Cumulative up to Aug 2013)
Stone Street Bluetooth Stack - v2.1.1.27990
Fusion 3.00.2.0.029R
DataWedge - v3.6.8
Updated Team Express- 1.1.62
Added eMscript CAB Installer in the OS Image

I am taking requests for those that are interested in providing feedback on the BETA builds.

 

We will be conducting BETA on MC75A0, MC75A6, MC75A8, MC55A0, MC55N0, MC9190 CE6, MC9596, MC3190 and MC3190 CE6.  We expect the BETA software build to be available by the end of the week for WM6.5 and in two weeks for CE6.  At this time due to resource constraints, we are only planning to make available English builds; however requests for additional languages will be considered and prioritized.

If you are interested in testing the BETA and providing feedback, please send me an email (DO NOT REPLY TO THE FORUM) with the product to be tested, the country in which it will be tested, the customer (or indicate yourself as the tester, if it will not go to a customer), how many units of that type the customer currently has deployed, and the WAN carrier used if a phone model.

Customer participation in the BETA program:  Current customers must be under an active support contract in order to qualify for participation in the BETA.  Determination of this qualification is the responsibility of the TA/Account Team.  In addition, customer's wishing to participate in the BETA must complete a BETA agreement (attached) BEFORE they are given the software.  Note you are permitted to demonstrate the BETA software to a customer without the completion of the agreement, but you may not give them the software, load the software onto the customer's units, or leave your device with the BETA software with the customer without completion of the BETA agreement.  Changes to the BETA agreement will not be accepted.

Please note that if you provide the build to a customer for BETA, you will be responsible for providing first line support and feeding back issues to the development team.  Tier1/2 and ECRT does not provide support for BETA programs.

The software will be provided under conditions of BETA and must be removed from the devices once the production release is available.

CONTACT
Can’t find what you’re looking for?