The MPA1.5 OS Maintenance Release (MR) program is currently in T&V RC1 stage for our next release targeted for the June 2011 timeframe on the following product:

MC17 Product Family

General highlights of this release:

MC17 Maintenance Release OS Features

 

QFE

 

The latest CE version of MS Quality Fix Engineering (QFE) covers up to Jan 2011. 

 

QFE updates that are made available by Microsoft contain information in the Release Notes about the files and registry settings that are updated. Typically, the Additional Information section of the Release Notes is sufficient to author a Device Update Agent script.  The Additional Information section of the Release Notes includes a list of the updated files, destination directories, and registry updates that are contained in the QFE. MS will require an up-to-date QFE on the device for troubleshooting related issues should the need arise.

 

Fusion version 3.00.2.0.014R

 

The Power Save mode can be enabled, and MC17 Battery Life has been improved.

 

WLAN Radio reset observed on device when pinging with packet size of above 8KB from a host PC. - SELECT_AND_CONNECT API blocks and hence block the RD Client from continuing its processing. SELECT_AND_CONNECT is executed in a separate process called FPPluginProfile.exe.- 

 

RD/Airbeam Client version v07.03.46

 

“Max Jobs” feature in MSP is available for MC17.

 

Pocket Browser version 3.0.7

 

Pocket Browser v3.0.7 is an enhanced version of SPB2.2 including the following key enhancements: Plug-in architecture, XML configuration/plug-in, Selectable browser engine, and Updated scripting language EMML1.1.

 

 

SPR Listings

 

SPR 18813 - MC17T - file corruption on SD Card when under stress. Benefit: If heavy I/O operations are carried on SD card with customer applications, file corruption would not happen

 

SPR 17401 - Date setting can turn to 1.1.1980 after re flashing the OS and cold boot. Benefit: Customer applications will work fine since date would not reset to 1980

 

SPR 18269 - EPIC 34884 - In Fusion 3.00.0.0.042R, Wlan Radio reset observed on device when pinging with packet size of above 8KB from a host PC. Benefit: User can download 100MB or more using Fusion without any issues

 

SPR 18445 - MC17T-00 touch panel intermittently does not respond to touch. Benefit: Upon suspend/resume if the user try to access the touch panel immediately, device would not have any issues with touch panel

 

SPR 18895 - USI is not able to program Flash on production line. Benefit: User can use IPL method to download images. This fix is applicable only to MC17 new

 

SPR 19157 - MC17-T cold boot (3 finger clod boot)   hang up issue. – Benefit: user can use 3 finger cold boot

 

SPR 19967 - USB OTG over current pin causes excess current draw in suspend state. Benefit: Customer will get more battery life.

 

Also included are the following enhancements:

 

Video Codec - Support for Video codes V8 and V9

 

Support for video playback including .mpe, .mpg, .mpeg and .avi files playback have been added. 

 

-Noe: Some .Avi files will not get played or only the audio comes if it requires different codecs other than Microsoft provided one.-

 

.NET CF3.5 OS dependencies

 

Customers can run their .NET application now on MC17 terminals.

 

-Prerequisite: User needs to download the .NET CF 3.5.cab from the web and install it on the terminal. After the installation of .NET CF3.5,  .NET CF v1.0, v2.0, v3.5 applications can be run on MC17.-

 

I am taking requests for those that are interested in providing feedback on the BETA builds. We will be conducting BETA on MC17.  We expect the BETA software build to be available by March 25.  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.