Download presentation
1
Windows Mobile 6.5 Overview
Mobile Computing Division Windows Mobile 6.5 Overview
2
Naming Confusion Windows Mobile 6.x is based on CE 5.02 NOT CE 6.x
WM 5.0 and Prior WM 6.0 and Beyond Description Windows Mobile Smartphone Windows Mobile Standard Telephony with no touch screen (Moto Q, EWP 1000/2000) Windows Mobile for PocketPC Windows Mobile Classic Traditional PDA full feature set without Telephony Windows PocketPC Phone Edition Windows Mobile Professional Same as Classic with Telephony support ( Windows Mobile 6.x is based on CE 5.02 NOT CE 6.x “Windows Mobile 7” -> “Windows Phone 7” (“Consumer version” – Q4 2010)
3
Adaptation Kit Updates (AKU)
Method Microsoft uses to deliver WM updates to OEMs Similar to a Service Pack in Desktop Windows Generally bug fixes and minor feature enhancements Contains combination of Binary and source OEMs required to adapt AKU to their unique HW and needs HW initialization, Drivers, etc. Significant testing required by OEM Windows Mobile 6.x.x beyond original WM 6.0 are all AKUs (Adaption Kit Updates) Latest Version; “WM 6.5.3” = “Com3” = “Maldives” = “WM6 AKU 5.3” (originally called “WM 6.6”) This presentation will focus on WM as most products will use this MC75A is the exception and was initially released with WM 6.5.2
4
What’s New in Windows Mobile 6.5.3
A Windows Mobile AKU based on WM 6.1 Also referred to as Windows Mobile 6 AKU 5.3 No Microsoft license Upgrade fee from WM 6.1 Misc bug fixes More available Virtual Memory Refreshed UI, Designer Themes Gesture / Finger “friendly” Touch support Zip decompression included in File Explorer
5
What’s New in Windows Mobile 6.5.3
Optional Bundled Applications (games, facebook, etc.) Services (My Phone, Windows Marketplace) Improved Browser (IE 6 based) Same kernel (CE 5.2), driver model and APIs Same SDK for Application Development as WM 6.x Widget Application Development Framework Support for Capacitive Multi-Touch (not currently on any Motorola MCD products)
6
New Start Menu Designed to be “Finger” Friendly “Honeycomb” layout
Larger Application Icons Physics effects for scrolling Start Icon moved to bottom left of all screens Battery status and time now on all screens
7
MCD Value Add Feature for WM 6.5
Ability to change icon layout to columns Evaluating for initial releases
8
New WM6.5 Default Home Screen vs. WM 6.1
*** Note that WM6.5.3 can be reconfigured via Settings to use same home screen as WM6.1
9
Internet Explorer Mobile 6
Based on Desktop IE 6 Feature set (Ajax and DOM support) Adobe Flash Lite plug-in Zoom Feature Improved Finger Friendly UI Search in Address Bar Mobile / Desktop View
10
What’s new for Application Developers
Uses Same Windows Mobile 6 SDK APIs unchanged from WM 6.1 Only exception is GAPI (Game API) which was deprecated in WM 6.1 and no longer documented or required in WM 6.5 devices. Use DirectDraw instead of GAPI New Gesture API Provides Applications events for single finger gestures TAP, DOUBLE TAP, HOLD, PAN, FLICK New Physics Engine API for Animation
11
What’s new for Application Developers
Widget Framework New application development environment based on HTML/JavaScript JavaScript extensions for Menus, Soft Key, Querying System State (battery state, signal strength, etc.) IE 6 as container for applications Updated runtimes: .NET CF 3.5 and SQL CE 3.1 Gesture API installs on top of Windows Mobile 6 SDK Windows Mobile 6.5 Developers Tool Kit is downloadable from:
12
Application Compatibility
Expect Some Compatibility Issues with previous WM applications Potential GUI Issues Application Icons get scaled to for new Start menu Task Tray Icons do not work with New Home Screen Can change to Classic Mode of Home Screen Title bar is smaller to accommodate larger Menu Bar (10 pixels on VGA) While client area is the same, Applications that hardcoded the start position or hide menu bar without hiding Title bar could have a cosmetic issue Start Menu moved from Title Bar (top) to Menu Bar (bottom)
13
Application Compatibility
Soft Keys (Menu Items) replaced with bubbles Bubbles allow less characters in menu strings (approx 2 characters for VGA in portrait orientation) Tool Tips display complete string Selectable (ie: file explorer) lists have increased spacing to improve “Finger Friendliness” Number of items displayed in given area of list controls may not be consistent with previous versions Some browser differences due to IE 6 Since WM 6.1 already had an IE 6 browser this is more of an issue moving from WM 5 to WM 6.x
14
Application Compatibility Example
WM 6.5 WM 6.1
15
Application Compatibility Example (annotated)
1. Title bar was shrunk (approximately 10 pixels on VGA screen) 2. Menu bar increased (by amount title bar was shrunk) Provides same usable area to applications Should not affect most applications Applications which hard coded screen coordinates and/or offsets for title bar may require modification 3. OK and Close buttons moved from Title Bar to Menu bar 4. Size and look of Soft Keys changed to “Bubbles” Text may be clipped in some bubbles, tool tip on hover will display full string
16
Virtual Memory Improvements
WM 6.0, 6.1 improved available virtual memory for applications compared to WM 5 and prior WM 6.5 makes further improvements Most common symptom was DLLs unable to load due to lack of free virtual space in device.exe process, a.k.a. “DLL Crunch” Two Additional 32Mb Virtual memory slots added for DLLs (slots 60 and 61) Data for DLLs aligned on 4K vs. 64K boundaries reduces wasted space Device Driver stacks moved to separate 32Mb slot In stress testing we have loaded 50 large DLLs with space still available DLL Crunch DLL Crunch
17
MCD Product WM 6.5 Roadmap Product Architecture WM 6.1 WM 6.5.2
MC9500-K MPA 2 Q3 ‘09 Now MC75A WLAN tbd MC75A WWAN MC3100 MC75 MPA 1.5 MC55 VC6000 Q3 ‘10 ES400 MC65 Initial Release
18
Agenda Windows Mobile /CE Roadmap
19
Windows Mobile Roadmap
Microsoft committed to Windows Mobile for Enterprise customers We will see a fork in the roadmap between Enterprise Devices (Windows Embedded Handheld) Consumer Devices (Phone 7) Microsoft and Motorola Collaborating on future Windows Mobile 6.x versions WM 6.5 as the Baseline Targeted at large enterprise customers Extended lifecycle, and future feature enhancements for enterprise use
20
Windows Mobile Roadmap
21
Windows Embedded Handheld 7
updated kernel supports 32K of concurrent processes, 2GB of virtual address space ARM v7 and multi-core processing and additional BSP updated connectivity technologies: Ethernet, Wi-Fi, Cell Core, Bluetooth, Windows Device Stage and Exchange Airsync, Updated UI with multi-touch, Flash 10, gestures and browser updated enterprise support life cycle - 5 years of primary + 5 years of extended support. continued support for the .NET CF 3.5 framework
22
Windows Embedded Handheld 7
Native applications will not run because of the technology change between the CE5 and the CE7 kernel supports WinForm and SQL Compact database Use Expression Blend to write unmanaged Silverlight code no support for managed Silverlight applications created in Visual Studio 2010. The developer tool will continue to be Visual Studio 2008.
23
Windows Phone 7
24
Very limited focus on consumer media player space
Windows Phone 7 Very limited focus on consumer media player space “A Zune HD with phone capabilities” A new product not an extension of WM 6.x Focused on competing with the iPhone in the consumer market Initial HW “Chassis” specification is very restrictive Little room for differentiation Many enterprise features have been removed Believe this is a positive for us as it allows us to differentiate from consumer devices No support for Compact Framework or any applications which are not installed via the MarketPlace Currently no support for multi-tasking at release (this may change)
25
Windows Phone 7 Due to launch Q with a small number of selected manufacturers Future hardware specs discussed but not defined or committed yet Currently not appropriate for enterprise market WM 6.x to continue to be OS of choice for enterprise unless issues are addressed in WP7.
26
Mobile OS Feature Comparison (Engadget)
27
Mobile OS Feature Comparison (Engadget)
28
Windows Mobile 6.5 is the Right OS for the Enterprise
Windows Mobile is still the right operating systems for Enterprise customers Enterprise customers have unique needs that are currently best addressed by Windows Mobile. Enterprise customers must maintain and manage a “fleet” of devices as opposed to one or two for a typical consumer Devices are used for business critical applications and require different levels of reliability and security than consumer devices Windows Mobile Provides Commitment to Enterprise Customers From Microsoft Enhanced Lifecycle support Features Needed by the Enterprise Standardization allowing application compatibility across Manufactures and devices We of course continue to review all available OS and technology trends
29
Windows Mobile Commitment to the Enterprise
Microsoft is fully committed to the enterprise space To further this commitment Microsoft has recently announced that they will transition Windows Mobile 6.5 for Enterprise focused products to their Windows Embedded Business unit. This will allow Microsoft to provide additional focus to enterprise needs including enhanced lifecycle support Typically 10 years for products in this business unit Motorola working very closely with Microsoft to define future Windows Mobile versions tailored to Enterprise customers Consumer focused operating systems on the other hand have no commitments to the enterprise space and are clearly focused on consumer devices and target content and services to those devices. It is highly unlikely that support for these operating system will be available for the time frame needed for enterprise customers to maximize their device investments.
30
Application Portability
Windows Mobile has a well defined Standard Feature set Enforced under the Microsoft Logo Test Kit (LTK) program The LTK process validates both reliability and functional completeness Required by Licensee agreement of all Windows Mobile Devices Standard and validated configurations enables enterprise customers to more readily port applications from device-to-device Either within a single manufacturer portfolio or across multiple manufacturers Open Source Operating Systems actually encourage the opposite; “splintering” of the OS Each Device inevitability defines its own features and modifications For example often Desktop Linux Applications need to target individual distributions (i.e. Debian, Ubuntu, Fedora, openSUSE, etc. )
31
Windows Mobile Enterprise Features
Mass deployment and configuration capabilities Unattended OS and Firmware updates WLAN Advanced WLAN Supplicant Support (CCX, WPA2) WLAN operational features such as fast roaming FIPS 140 application level encryption support Onboard & Removable Media File Encryption Device Loss/Stolen – Remote Wipe FIPS Certified Cryptographic Security Mobile Device Management (from Multiple Vendors) Security Policies (Exchange , Application Execution, Device Password, etc.) Choice of Development Environments (C/C++, .NET, Java, WEB/HTML) Wide choice of available applications, utilities, databases, VPNs, etc. Eco system of partners and developers who are experts in Windows Mobile
32
Enterprise Extensions to OS (what we add)
Method to mass deploy configuration settings (i.e Regmerge and Copyfiles) Method to perform SW updates in an unattended manner Method to recover from failed SW update Ability to identify HW components at run-time Crucial to lifecycle management Keyboard wedge for transparent access to Scanning, Mag Stripe, RFID and other input data Ability to read Serial Numbers Requires process to program Serial Numbers at Manufacturing Persistent and Super persistent Storage Allows access to network and application re-deployment following clear of persistent storage Debug tools and developer support Ensure Data integrity following battery swaps, battery contact chatter, resets, etc. Removable media, SD card, can be accessed immediately following a suspend resume Enterprise level security (WLAN, FIPS encryption, etc.) Ability to “lock down” device to specific applications (AppCenter) Provisions for Keyboard remapping Deterministic method to launch applications on startup Independent Power Control for peripherals (backlight, keylight, touch, etc.) Icons to show state of keyboard (i.e Orange and blue alternate key states) Reset sequences that are common, can be called from applications and have failsafe to ensure they always work Preserving RTC across all resets / battery swap Improved audio quality and access to APIs to control Audio features Drivers/APIs for Scanning, imagers, mag stripe , RFID, etc. Robust, (i.e. survives suspend resume cycles etc.)
33
Agenda IE6 New Features
34
A New View of the Web New York Times eBay Yahoo
Sites will look very similar to experience on Internet Explorer 6 on PC running Windows®
35
What is new in Internet Explorer Mobile?
Same technologies as its PC counterpart (IE 6.x) Search integration Improved user experience Adobe FlashLite 3.1
36
Best of Both World Menu->View allows the user to choose between the mobile and PC web.
37
Detecting Internet Explorer Mobile 6
Mobile mode HTTP Headers Previous versions of IEMo GET ######### HTTP/1.1 Accept: */* Accept-Language: en-us Connection: Keep-Alive Host: ######### User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows CE; IEMobile 8.12; MSIEMobile 6.0) UA-pixels: 240x320 UA-color: color16 UA-OS: Windows CE (Pocket PC) - Version 5.2 UA-CPU: x86 Accept-Encoding: gzip, deflate UA-Voice: TRUE GET ######### HTTP/1.1 Accept: */* Accept-Language: en-us Connection: Keep-Alive Host: ######### User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows CE; IEMobile 7.11) UA-pixels: 240x320 UA-color: color16 UA-OS: Windows CE (Pocket PC) - Version 5.2 UA-CPU: x86 Accept-Encoding: gzip, deflate UA-Voice: TRUE
38
Detecting Internet Explorer Mobile 6
Desktop mode HTTP Headers Mobile mode HTTP Headers GET ######### HTTP/1.1 Accept: */* Accept-Language: en-us Connection: Keep-Alive Host: ######### User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows CE; IEMobile 8.12; MSIEMobile 6.0) UA-pixels: 240x320 UA-color: color16 UA-OS: Windows CE (Pocket PC) - Version 5.2 UA-CPU: x86 Accept-Encoding: gzip, deflate UA-Voice: TRUE GET /######## HTTP/1.1 Accept: */* Accept-Language: en-us Connection: Keep-Alive Host: ######### User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) UA-pixels: 240x320 UA-color: color16 UA-OS: Windows CE (Pocket PC) - Version 5.2 UA-CPU: x86 Accept-Encoding: gzip, deflate UA-Voice: TRUE Same as XP IE6!
39
Viewport size can be adjusted via registry keys
The Viewport is the dimensions of the screen the web page will be laid out on (i.e. virtual screen size) Viewport size can be adjusted via registry keys Parameter Default Minimum Maximum Width 1024 100 10000 Height 768
40
Mail and Phone integration
Send a Mail <a Feedback&body=I dig the commercials!%0A%0aKeep them coming.”>Feedback</a> Dial a number <a href=“tel: ”>Jenny</a>
41
FlashLite Youtube Adobe FlashLite 3.1
Delivering on PC experience for your mobile device Support most Flash 9 content No support for Action Script 3
42
FlashLite Full Screen Press and hold for context menu
Select “Full Screen” Works on most flash content Content may still have other mechanism for full screen Press and hold with cursor will also provide menu
43
Media Player OCX Windows Media Player
Embed on web page or launch to external player Supported in IEMo before as well
44
What is a widget? “A portable chunk of the web” Download as single package, runs locally Look and feel of traditional device applications
45
Widget Capabilities Full Browser-based support for AJAX and plug-ins like Flash/Silverlight Access to device data Installed as a shortcut in programs list Can be uninstalled via Remove Programs in Settings
46
Internet Explorer Mobile
Under the Hood Widget Package Widgets Runtime Powered by Internet Explorer Mobile Plug-ins Flash HTML Security Broker Silverlight Windows Media JavaScript CSS … Web Rendering Engine Script Engine Menu Images JavaScript Device Extensions Settings Location XML Manifest Camera …
47
3 Steps to Building a Widget
Develop Create User Interface using Expression Blend Develop Jscript Code Package Create XML Manifest Package as Zip, rename to .wgt Deploy Transfer to device as link on web page, attachment, sideload
48
Building a Widget: Creating UX
49
Building a Widget: Packaging
Easy method for packaging – zip all files together and rename .zip to .wgt Copy .wgt to device and exectute to install
50
Building a Widget: Installation screen
51
Special widget object hosts widget-specific APIs
Widget API Overview JavaScript Object Model extended to include widget-specific methods and events Menu/Softkey access Lightweight local persistence SystemState UI change events Manifest metadata Special widget object hosts widget-specific APIs
52
Widget APIs - Menu // Programmable softkeys
var leftSoftKeyMenu = widget.createMenuItem( 10 ); leftSoftKeyMenu.text = “Refresh”; leftSoftKeyMenu.onSelect = lskHandler; widget.menu.setSoftKey( leftSoftKeyMenu, widget.menu.leftSoftKeyIndex ); function lskHandler() { // left soft key // handler code here // to refresh }
53
Widget APIs – Persistent Storage
Persistent storage for strings Available across widget runs Preserved during upgrade process widget.setPreferenceForKey( “lastLocation”, “Istanbul ); // read previously stored setting var lastLocation = widget.preferenceForKey( “lastLocation” );
54
Widget APIs - SystemState
Access to key System State properties var systemState = widget.createObject("SystemState"); systemState.PowerBatteryStrength.addEventListener( ‘changed’, optimizeNetworkUsage );
55
Widgets can detect view state changes using onshow()/onhide() handlers
Widget APIs - UI Widgets can detect view state changes using onshow()/onhide() handlers widget.onshow = function() { // refresh UI }; widget.onhide = function() { // reduce network usage
56
Widget APIs – Manifest Metadata
Manifest metadata accessible via script locale Returns the current language-locale string, for example, "en-us”. identifier The App ID of the installed widget, as a string. currentIcon Pointer to a WidgetIcon object for the first icon in the manifest authorName The node text of the <author> element in the manifest. author The value of the attribute of the <author> element. authorURL The value of the href attribute of the <author> element. If not a valid URI, will return null. name The widget’s name description The node text of the <description> element, or null. version The widget version string. The value of the version attribute in the <widget> element, or null. width The width of the client area of the widget (not including any chrome.) height The height of the client area of the widget (not including any chrome.)
57
Questions
Similar presentations
© 2025 SlidePlayer.com Inc.
All rights reserved.