AppCenter 1.1 (Build 2068) Release Notes
AppCenter CE 1.10
AppCenter is an end-user application access control engine that restricts activity to a set of authorized applications on mobile devices
• Active and passive approach to restricting application activity
• Locks the user out of executing “unauthorized” applications
Presents a launch platform of authorized applications in icon form
• Unauthorized applications terminated
• Typical scenario - kiosk application
• End-user runs ONLY specified application
A valid Symbol security key must exist in the device registry before AppCenter will operate on the device. Refer to the RegFile-Readme.txt file located in the PlatformReg folder contained in the ZIP file.
Installation and Cold Boot Recovery for Symbol platform instructions are included in the AppCenter CE Admin Guide (AppCenterCE.NET Admin GuideV110.pdf).
AppCenter CE 1.10 compatible with the following Symbol devices:
Windows CE 4.x
Windows CE 5.x
Windows CE 6.x
Windows CE 7.x
Version v1.10 Build 2068
1. Added support for MK3100.
2. There is a new setting named UseWinsockForIpAddress that is used in conjunction with the DisplayIpAddress setting. The new setting defaults to true and should provide more reliable display of the IP address with no need to ever manually enter an adapter name. If the older behavior is preferred, set UseWinsockForIpAddress to false. The new setting has no effect unless DisplayIpAddress is true.
3. The logic for automatically identifying the best adapter for use with ShowSignalStrength, DisplayIpAddress and DisplayMacAddress has been brought in line with AppCenter for Windows Mobile. The need to specify an AdapterName in the admin settings should be largely eliminated.
4. The MSP AppCenter Plugin has been brought up to date. The DefDoc is now version 1.23 and supports the UseWinsockForIpAddress setting. In order to access the new setting, "CE Build 2056 Support" must be set true. The new setting is under "Configure Options->CE Specific Settings".
Version v1.10 Build 2032
1. Added support for MC9200, VC7000 and WT4100.
Version v1.10 Build 2030b
1. Added support for MC2100.
Version v1.10 Build 2030
1. The ShowKeyStates setting now supports two states for the Alpha, Function and Shift keys. For example, on the MC3190, the Shift key is single use if pressed once and locked if pressed twice.
2. On some devices the ShowKeyStates Alpha key icon was displaying the opposite of what was expected. This problem has been fixed.
Version v1.10 Build 2022
1. The AlternateTitle setting now supports special tokens. Tokens are designated by surrounding keywords with square brackets. If a token is invalid, [Invalid Token] will display as the title. If a token is not supported on a device, [Not Supported] will display as the title.
Specifying an AlternateTitle of [ESN] (Electronic Serial Number) will display the results of the GetESN function as the title. Not all devices support this function. Some devices will return 0000000000000000 as the serial number. The System Info applet under Settings can be used to check the value of ESN.
Specifying an AlternateTitle of [UUID] will display the results of the GetUniqueUnitIdEx function as the title. Most devices support this function. The System Info applet under Settings can be used to check the value of UUID.
Specifying an AlternateTitle of [DeviceID] will display the results of IOCTL_HAL_GET_DEVICEID as the title. This is a generic call that can be used on all Windows Mobile devices. Often the results of UUID and DeviceID are identical.
Specifying a registry key and value inside square brackets will display the registry value as the title. Only string values are supported. A full registry key should be specified followed by a colon and the value name (no spaces). If the default value for the registry key is desired, leave off the colon and value name.
Examples: [HKEY_LOCAL_MACHINE\SOFTWARE\Symbol\AppCenter] "AlternateTitle"="[ESN]"
"AlternateTitle"="[DeviceID]" "AlternateTitle"="[HKEY_LOCAL_MACHINE\SOFTWARE\XYZ Incorporated]" (Default value)
Version v1.10 Build 2018
1. AppCenter Case sensitive passwords are now allowed. Passwords created in previous versions are lowercase and will need to be created again to support uppercase letters.
Version v1.10 Build 2000
1. AppCenter CE now uses the same program approval algorithm as AppCenter WM. This means the approved windows are no longer global in scope. Each approved program has an ExeNames setting that can be set to one or more EXE names. The approved windows apply only to those EXEs. For most approved programs, this means the approved windows can be set to *|* as AppCenter will match first based on the EXE name. If multiple approved programs use the same EXE name, as in the case of control panel applets, then each approved program should supply approved windows to uniquely identify itself. The new ExeNames setting is stored in the registry in a manner similar to the Windows setting. The 1st EXE name is stored as ExeName1, the 2nd as ExeName2 and so forth. The numbering must start at 1 and have no gaps.
2. AppCenter CE will automatically attempt to convert existing settings to use the new ExeNames setting. The EXE name specified in the Execute setting will be used as the default for the ExeNames setting. If the Execute setting is blank, the ExeName will need to be manually added.
AppCenter CE will not change the existing approved windows. It is suggested, but not required, that you change the approved windows to *|*, unless the EXE names specified are used in other approved programs. In general it is good practice to not specify a window title unless necessary. AppCenter CE will work more efficiently when you specify *|* or *|ClassName as approved windows.
Since the conversion process may not be perfect, it is suggested that users let AppCenter CE convert the existing settings on one device and then test.
3. AppCenter CE now provides a user interface for all settings except AdminLoginDisabled.
4. The AdminDebugMode setting is no longer supported. As in AppCenter WM, AppCenter CE now logs all unapproved windows.
5. The UnresponsiveAppTimeout setting is no longer supported. If an app is unresponsive for one second, AppCenter CE now assigns a blank title to the foreground window. This is the same as AppCenter WM. For unresponsive apps the best strategy is to set approved windows to *|* in which case AppCenter never needs to retrieve the window title and the unresponsiveness is no longer an issue.
6. In addition to ExeNames, each approved program now supports the AppCenter WM AlwaysLaunch and AddToToolsMenu settings.
7. AppCenter CE now supports the following AppCenter WM settings: AirBeamLock
IconsDisabledCount BrowseControlPanel RegionalTimeFormat RegionalTimeOptions
8. AppCenter CE now stores the current build number in the registry at the following location:
[HKEY_LOCAL_MACHINE\SOFTWARE\Odyssey Software\AppCenter] "Build"=dword:000007D0
9. The Tools menu in user mode, now has an "Exit..." item. The admin password is required to exit AppCenter.
Version v1.10 Build 1516
1. Enhanced detection of Fusion radio and usage of Fusion API is used for signal strength when appropriate.
Version v1.10 Build 1510
1. HideAllTaskBars now supports 3 settings.
0 = Don't hide all taskbars (previously supported)
1 = Hide all taskbars and set work area to full screen (previously supported) 2 = Hide all taskbars but don't set work area (new)
Version v1.10 Build 1508b
5. Added support for MC3100.
Version v1.10 Build 1508
1. The alpha key state now works correctly on the MT2000.
2. The taskbar time is now shown in the same font as the title.
Version v1.10 Build 1502
1. The MSP Plugin for AppCenter has been updated to skip new WM-only features.
2. AppCenter is unchanged in this release.
Version v1.10 Build 1500
1. Two command line options have been added. -restart will stop the current AppCenter process and then launch a new AppCenter process. This allows configuration changes to be reloaded. -terminate stops the current AppCenter process.
2. The MSP Plugin for AppCenter has been added to this release.
Version v1.10 Build 1490
1. An issue was encountered with applications, such as IE, that require the work areas (screen size) to be set before they can be viewed in full screen mode, not being presented in full screen mode correctly through AppCenter. To address this, improvements have been made to the HideAllTaskBars feature.
Version v1.10 Build 1478
1. To address an issue where, after repeated cold resets, AppCenter was starting before the registry key had been created and would present a “not approved platform” error message on CE5.0 devices, AppCenter now waits up to 10 seconds for a valid platform registry key before failing.
Version v1.10 Build 1472
1. The AppCenter taskbar was being covered by full screen windows after a MB_TOPMOST message box displayed. This issue has been fixed.
Version v1.10 Build 1466
1. A bug was introduced in build 1450. Tapping on white space in the AppCenter window was launching the last selected program. This issue has been fixed.
Version v1.10 Build 1458
1. Added support for the WT4000 NG Wearable.
2. A new registry setting allows you to return to the AppCenter screen using a keystroke rather than tapping the Home icon.
HomeHotKey defaults to Ctrl+F10 (2121). Set to zero to disable this feature. The setting can be changed to any valid virtual key code. For example the F1-F10 keys have virtual key codes of 112-121. All virtual key codes are documented in MSDN (http://msdn.microsoft.com). Search on "virtual key codes". The documented values are in hexadecimal and should be converted to decimal.
To combine a key with the Alt, Control or Shift keys, add 1000 for Alt, add 2000 for Control and add 4000 for Shift.
The setting is located at HKEY_LOCAL_MACHINE\Software\Symbol\AppCenter. There is no user interface for this setting. When AppCenter is run this registry setting is created with the default value if it doesn't already exist.
3. The AdminLoginHotKey setting can now be defined to use the Alt, Control or Shift keys. Add 1000 for Alt, add 2000 for Control and add 4000 for Shift.
4. A HideSip checkbox has been added to the Options dialog. This setting defaults to false and controls whether the SIP icon is displayed on AppCenter's taskbar when AppCenter is in the foreground.
Version v1.10 Build 1360
1. A new registry setting allows you to bring up the admin login dialog with one key press.
Version v1.10 Build 1332
1. There is a new program option named HideAllTaskBars. When this option is set true and a program is run from within AppCenter, both the Windows and AppCenter task bars are hidden. This option can be used with programs that want to use the whole screen. The program is responsible for setting its window size to the full screen size.
Version v1.10 Build 1286
1. The signal strength icon can now be configured to run the new Symbol Fusion radio utilities. The new FusionMode registry setting is located at HKEY_LOCAL_MACHINE\SOFTWARE\Symbol\AppCenter.
There is no user interface for this setting. The first time AppCenter is run this registry setting is created with the default value of 0. If this setting is greater than zero, it will override the MobileCompanionMode setting. The following values are supported:
0 - No action is taken.
1 - Run the Fusion status program.
2 - Run the Fusion diagnostics program.
3 - Show a menu for status or diagnostics. 4 - Show the full Fusion menu.
2. A new ShowKeyStates registry setting can be used to display taskbar icons showing the current state of the Alpha, Func, Shift and Ctrl keys. The setting is located at HKEY_LOCAL_MACHINE\SOFTWARE\Symbol\AppCenter.
There is no user interface for this setting. The first time AppCenter is run this registry setting is created with the default value of false (0) which is consistent with previous versions. Set true (1) to enable the display of key state icons on the taskbar.
Components of .zip file
Define the files in the .zip file
AppCenter Admin Guide
WCE 410/420/500/600/700 Folder
Main AppCenter executable
Readme file for security registry key information
Symbol security registry files for devices
Document Number / Revision / Release Date
AppCenter CE 1.10 Release Notes (Build 2068).doc / October 11, 2013