Compatibility Notes

Transcript

Compatibility Notes 7135 Software Release SZ1.0.29/MZ1.0.44 80-B9339-13_A Kyocera Wireless Corp. Proprietary Export of this technology or software is regulated by the U.S. Government. Diversion contrary to U.S. law prohibited. All data and information contained in or disclosed by this document are confidential and proprietary information of Kyocera Wireless Corp., and all rights therein are expressly reserved. By accepting this material, the recipient agrees that this material and the information contained therein are held in confidence and in trust and will not be used, copied, or reproduced in whole or in part, nor its contents revealed in any manner to others without the express written permission of Kyocera Wireless Corp. This software is controlled by the United States Government. Diversion contrary to U.S. law prohibited. Kyocera Wireless Corp. 10300 Campus Point Drive San Diego, California 92121 Copyright © 2003 Kyocera Wireless Corp. Printed in the United States of America. 80-B9339-13_A Kyocera Wireless Corp. Proprietary 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A Contents 1. Software Features ......................................................................................................2 1.1 Standard 7135 product features................................................................................2 1.1.1 Smartphone ......................................................................................................2 1.1.2 QUALCOMM MSM5100 mobile station modem...........................................2 1.1.3 Tri-mode support .............................................................................................2 1.1.4 Low and High Speed packet data, Async /G3 fax data services ......................2 1.1.5 Short Messaging System (SMS) ......................................................................2 1.1.6 FCC compliance Emergency 911.....................................................................2 1.1.7 Web browsers...................................................................................................3 1.1.8 IOTA ................................................................................................................3 1.1.9 IS-683-A standard over-the-air service provisioning.......................................3 1.1.10 IS-683-A format preferred roaming list ...........................................................3 1.1.11 TSB-50 A-key entry.........................................................................................3 1.1.12 Automatic volume control (Smart Sound).......................................................3 1.1.13 Downloadable roaming messages ....................................................................4 1.1.14 Resettable subsidy lock....................................................................................4 1.1.15 Speakerphone...................................................................................................4 1.1.16 VR 4.3 Support (Voice Services).....................................................................4 1.1.17 TTY Support ....................................................................................................4 1.1.18 GPS Support ....................................................................................................4 1.1.19 Mobile IP .........................................................................................................5 1.1.20 Enhanced Roaming Indicator...........................................................................5 1.1.21 Number Assignment Module (NAM) ..............................................................5 1.1.22 SDIO card support ...........................................................................................5 1.2 User Interface (UI) featuring bitmap display ...........................................................5 1.2.1 Up/down/OK keys............................................................................................6 1.2.2 End/Pwr key.....................................................................................................6 1.2.3 SMS memory ...................................................................................................6 1.2.4 Contacts and recent calls..................................................................................6 1.2.5 Vibrator support ...............................................................................................6 24 June 2003 Kyocera Wireless Corp. Proprietary i 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 2. 80-B9339-13_A 1.2.6 User interface languages ..................................................................................6 1.2.7 Customizable sounds .......................................................................................7 1.2.8 Text Entry ........................................................................................................7 1.2.9 Voicemail Access.............................................................................................7 Software Changes ......................................................................................................8 2.1 Changes Made in the SZ1010/MZ1020 Release......................................................8 2.1.1 SMS alerts not received while PDA sleeping ..................................................8 2.1.2 SMS stuck in pending ......................................................................................8 2.1.3 CDG3 failure CC34 in Sacramento .................................................................8 2.1.4 Openwave Browser: Exit during start screen fails..........................................8 2.1.5 Mobile display stuck in calling state................................................................8 2.1.6 Issues with MP3 playback interaction with other applications ........................8 2.1.7 Scrolling through SMS message list ................................................................9 2.1.8 Ringer volume from loudspeaker low with headset attached ..........................9 2.1.9 AMPS messaging failures at CTIA..................................................................9 2.1.10 PDA not locking with auto-lock ......................................................................9 2.1.11 Screen turned dark, but PDA was still responsive ...........................................9 2.1.12 AddressBook moved to next category when opened .......................................9 2.1.13 External signal strength indicator not updated when flip closed .....................9 2.1.14 Calls dropped sometimes when VMN received...............................................9 2.1.15 Stuck in resetting cycle after battery removed ...............................................10 2.1.16 Headset audio level increased ........................................................................10 2.1.17 Buttons would register with flip closed .........................................................10 2.1.18 Auto expand feature revealed passwords.......................................................10 2.1.19 MP3 ringers would sometimes end with a zap ..............................................10 2.1.20 PDA instability addressed..............................................................................10 2.1.21 External voice mail icon disappeared with open flip.....................................10 2.1.22 Erroneous E911 callback mode after call ended early ...................................11 2.1.23 Incorporated recent QCT Patch releases ........................................................11 2.1.24 CRC error on retune from GPS......................................................................11 2.2 Changes Made in the SZ1011/MZ1024 Release....................................................11 2.2.1 MT-SMS message may become segmented ..................................................11 24 June 2003 Kyocera Wireless Corp. Proprietary ii 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A 2.2.2 CRC error on retune from GPS – additional enhancement............................11 2.2.3 Phone powered down while sending MO-SMS message ..............................12 2.2.4 Unsuccessful Mobile IP call using AT commands ........................................12 2.2.5 Pending origination in page response state ....................................................12 2.2.6 Pending SMS client in LPM ..........................................................................12 2.2.7 Openwave WAP browser and dormancy .......................................................12 2.2.8 “Dial Before” number will default to nothing ...............................................12 2.2.9 Booting from a discharged battery.................................................................13 2.2.10 MP3 Player crash (Assertion Failed Error)....................................................13 2.2.11 External LCD backlight activated periodically..............................................13 2.2.12 MO-SMS character count incorrect after copying a message........................13 2.2.13 MO-SMS can exceed maximum if call back number included .....................13 2.2.14 Programming the voice mail callback number via PST.................................13 2.2.15 Memory leak with carrier logo.......................................................................14 2.3 Changes Made in the SZ1013/MZ1027 Release....................................................14 2.3.1 GPS dynamic range improvements................................................................14 2.3.2 OTASP completion status criteria relaxed.....................................................14 2.3.3 Voice mail list text in Inbox initialized .........................................................14 2.3.4 Fatal error with numbers ending in punctuation ............................................14 2.3.5 Key presses during call which Attention Manager active..............................14 2.3.6 CHAP selection from Phone Preferences ......................................................15 2.3.7 Crash when configuring or changing NAMs .................................................15 2.3.8 White screen when operating flip in a browser call.......................................15 2.3.9 Service programming of NAM 2 not available with OTKSL........................15 2.3.10 1X data icon not updated reliably ..................................................................15 2.3.11 ERI not shown every 5 minutes after PDA sleep...........................................15 2.3.12 VR stuck in calling.........................................................................................15 2.4 Changes Made in the SZ1013/MZ1030 Release....................................................16 2.4.1 Reset seen while switching clock rates in GPS sessions ...............................16 2.4.2 Increased microphone gain ............................................................................16 2.5 Changes Made in the SZ1017/MZ1030 Release....................................................16 2.5.1 1X data icon not activated when phone first powered on ..............................16 24 June 2003 Kyocera Wireless Corp. Proprietary iii 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A 2.5.2 Phone powered off when viewing SMS during tethered dormancy...............16 2.5.3 Phone remained in dormant mode after network release ...............................16 2.5.4 Shorten key tone length for phone keys .........................................................17 2.5.5 Keypad double entry ......................................................................................17 2.5.6 Do not play ringer volume when adjusting via side volume keys .................17 2.5.7 Digit collection is slow when DTMF length set to long ................................17 2.5.8 Slow keypad response for digit collection .....................................................17 2.5.9 MP3 app settings should only apply to MP3 mode........................................17 2.5.10 MP3 should not play during hotsync .............................................................17 2.5.11 Lockup after deleting MP3 ringer via File Manager......................................18 2.5.12 Crash when MMC card inserted/removed while Phone app running ............18 2.5.13 Unable to answer incoming call with large address book..............................18 2.5.14 Highlight voicemail, press SEND will originate a call to VMN ...................18 2.5.15 No alert from message received during voice call .........................................18 2.5.16 Phone app launched from SMS with invalid link ..........................................18 2.5.17 Openwave Browser playing double alert on incoming message....................18 2.5.18 Crash resulted from message signatures containing carriage returns ............19 2.5.19 Repeated Send from contact with no phone number caused crash ................19 2.5.20 E911 mode exited by power down, next E911 call not labeled.....................19 2.5.21 Insert MMC card and open flip resulted in white display.............................19 2.5.22 Alarm during hotsync caused crash ...............................................................19 2.5.23 Phone reported data service available in analog mode ..................................19 2.5.24 Duplicate address entries created without confirmation ................................20 2.6 Changes Made in the SZ1019/MZ1032 Release....................................................20 2.6.1 Phone will now re-register after over-the-air service provisioning................20 2.6.2 Enhancement to OTASP Protocol Capabilities Response Message ..............20 2.6.3 Carrier specific initial programming message ...............................................20 2.6.4 Caller ID not showing ....................................................................................20 2.6.5 Remove Workstyle application......................................................................20 2.6.6 Carrier specific control of editing network connection setting......................20 2.6.7 Back light incorrectly toggles when pressed to wake device.........................21 24 June 2003 Kyocera Wireless Corp. Proprietary iv 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A 2.7 Changes Made in the SZ1019/MZ1034 Release....................................................21 2.7.1 Phone crashed attempting tethered USB data with Mobile IP disabled.........21 2.8 Changes Made in the SZ1020/MZ1034 Release....................................................21 2.8.1 Outgoing SMS message can show scheduled status indefinitely...................21 2.8.2 Recent calls entry not updated immediately after call ended.........................21 2.8.3 Phone does not stop ringing immediately when call answered......................21 2.8.4 Latin-1 encoded SMS not processed correctly...............................................22 2.8.5 Carrier specific preference to overwrite call history with look up number ...22 2.8.6 Support for Phone Number Length, Area Code Length, International Access Code and Country Code .................................................................................22 2.8.7 IS-41 workaround failure ...............................................................................22 2.8.8 Time not correctly updated when switching time zone .................................22 2.8.9 Hide/Show Voice Privacy setting from phone preference .............................22 2.9 Changes Made in the SZ1023/MZ1036 Release....................................................22 2.9.1 Mobile sent unsolicited read ack messages....................................................22 2.9.2 Roaming indicator now consistent on internal and external displays ............23 2.9.3 Ringer not playing when in emergency callback mode .................................23 2.9.4 Web browser fatal exceptions ........................................................................23 2.9.5 Default multi-tap mode to digits when in numeric fields ..............................23 2.9.6 Speed address book name matches in phone UI ............................................23 2.9.7 Expanded SDIO support ................................................................................23 2.9.8 PDA crash while attempting to dial a number from the Address Book.........23 2.9.9 Hotsync freeze when using USB....................................................................24 2.9.10 Quick Access button triggered by loud noises on certain headsets................24 2.9.11 Pending SMS messages not erasable .............................................................24 2.9.12 Phone reset with bad Channel List Message..................................................24 2.10 Changes Made in the SZ1024/MZ1038 Release................................................24 2.10.1 Fatal crash using PDA auto-lock security feature..........................................24 2.10.2 ERI text overrides E911 text..........................................................................24 2.10.3 Fatal exception when using MMC/SD cards .................................................25 2.10.4 Fatal alert crash when optimizing address book ............................................25 2.10.5 Call not originated when hit SEND in address book .....................................25 24 June 2003 Kyocera Wireless Corp. Proprietary v 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A 2.10.6 Call not originated for numbers with illegal characters .................................25 2.10.7 Incoming data call after closing Openwave Browser.....................................25 2.10.8 Tethered data calls with &C1 not working with Win2000 ............................25 2.10.9 No Roaming option persisted in a particular customer configuration ...........26 2.11 Changes Made in the SZ1029/MZ1044 Release................................................26 2.11.1 Allow MO-SMS sending to two digit numbers .............................................26 2.11.2 Dormant mode indicator remains after disconnect in no signal state ............26 2.11.3 Graffiti2 support.............................................................................................26 2.11.4 Contrast adjustment .......................................................................................26 2.11.5 Freeze when low battery alert (and other sounds) occur................................26 2.11.6 OTKSL Menu update to include AMPS Home SID......................................27 2.11.7 Phone gets stuck in "Calling..." when placing an outgoing VR call ..............27 2.11.8 Phone doesn't respond to key presses or flip..................................................27 2.11.9 Menu for selecting Browser data settings on the Smartphone.......................27 3. 2.11.10 Improvements in EIS Browser ...................................................................27 2.11.11 Choosing an SMS read receipt notification on the Attention Manager shows the In box instead of Out box..........................................................27 2.11.12 Crash sending SMS message while putting phone into cradle ..................27 2.11.13 Calling #777 when in Dormant Mode .......................................................27 2.11.14 Multi-segmented msgs with Latin-1 encoding stuck in pending ...............28 2.11.15 Blank screen after tapping Attention Manager blinking indicator.............28 2.11.16 Fatal alerts from corrupted ROM...............................................................28 2.11.17 Updates from Qualcomm for DMSS 5100 2.1 Commercial Patch 6.........28 2.11.18 Generate three beeps at end of OTASP session.........................................29 2.11.19 UI battery gauging and AT+CBC response not close enough ...................29 2.11.20 AT+GMM displayed MOB_MODEL........................................................29 2.11.21 Missed calls due to phone reselecting for better service............................29 2.11.22 Added PRI control of IS-801 messaging in idle emergency mode ............29 2.11.23 Voice privacy icon not always displayed in MT calls................................29 Known Bugs..............................................................................................................30 3.1 Phone......................................................................................................................30 3.1.1 Unexpected power cycle events .....................................................................30 24 June 2003 Kyocera Wireless Corp. Proprietary vi 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 4. 80-B9339-13_A 3.1.2 Powerup and connecting external power .......................................................30 3.1.3 Behavior in poor RF conditions .....................................................................30 3.1.4 Incoming call during Hotsync may cause crash .............................................30 Cautions and Usage Notes .......................................................................................31 4.1 Phone......................................................................................................................31 4.1.1 Software version, ESN, PRL, service center items display ...........................31 4.1.2 Battery charging .............................................................................................31 4.1.3 Standby time testing.......................................................................................31 4.1.4 Battery removal..............................................................................................31 4.2 Accessories ............................................................................................................32 4.2.1 Travel charger ................................................................................................32 4.2.2 Desktop charger .............................................................................................32 4.2.3 Analog Portable Hands Free carKit (APHFK)...............................................32 4.2.4 Car power adapter (CPA)...............................................................................32 4.2.5 Headset...........................................................................................................32 4.2.6 Universal Data Interface Programmer (UDIP) cable .....................................32 4.3 Support tools ..........................................................................................................32 5. 4.3.1 Kyocera Product Support Tool (PST)............................................................32 4.3.2 Mobile diagnostic software: CMDA Air Interface Tool (CAIT)...................32 4.3.3 Roaming List Editor (RLE)............................................................................32 4.3.4 Palm Desktop .................................................................................................33 Software Upgrades...................................................................................................34 5.1 RF performance......................................................................................................34 5.2 Boot block and software upgrades .........................................................................34 5.3 Making use of new security features......................................................................34 24 June 2003 Kyocera Wireless Corp. Proprietary vii 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A Compatibility Notes 7135 Software Release SZ1.0.29/MZ1.0.44 Revised 24 June, 2003 Software versions SZ1.0.29/MZ1.0.44 are Kyocera software releases for the 7135 Trimode (1900 MHz CDMA / 800 MHz CDMA / 800 MHz AMPS) portable phone product, also known as the Kyocera Smartphone. Covered in this document are software features and changes of particular interest to carriers and manufacturers, emphasizing those that may raise compatibility issues. Also listed, are bugs and anomalies known or suspected to exist in the release that may impact compatibility. 24 June 2003 Kyocera Wireless Corp. Proprietary 1 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A 1. Software Features 1.1 Standard 7135 product features 1.1.1 Smartphone The 7135 is the successor of the 6035, or Kyocera Smartphone. It combines a CDMA Module, providing support for CDMA wireless communications, with the functionality of a Palm computing device. Thus, there are two releases of software that are loaded onto the phone. The software running under Palm OS is release SZ1.0.24. The code running on the CDMA Module is release MZ1.0.44. 1.1.2 QUALCOMM MSM5100 mobile station modem Release MZ1.0.00 and greater support QUALCOMM MSM5100 mobile station modem. 1.1.3 Tri-mode support Release SZ1.0.29/MZ1.0.44 supports 800 MHz CDMA, 1900 MHz CDMA and AMPS in accordance to Addendum 2 (to the IS2000 standard) TIA/EIA/IS2000 PN-4756 (Ballot Version). Supporting up to P_REV 6 CDMA2000 and IS-95A/B J-STD-008. 1.1.4 Low and High Speed packet data, Async /G3 fax data services The mobile supports low and high-speed packet data, asynchronous data, and G3 fax data services in full compliance with the IS-707, IS-707A, and IS-707A-1 standard. Quick Net Connect (QNC) is also supported. High Speed data capable, with advertised data rates up to 163Kbps on the Forward Link, and 86.4 Kbps on the Reverse. Our max F-SCH support is 153.6Kbps plus the F-FCH of 9.6Kbps == 163.2Kbps. Our max R-SCH support is 153.6Kbps plus the R-FCH of 9.6Kbps == 163.2Kbps. Fax and Async data is still supported at IS-95A data rates of 9.6 and 14.4 Kbps. 1.1.5 Short Messaging System (SMS) The mobile supports Mobile-Terminated SMS (MT-SMS) and Mobile-Originated SMS (MO-SMS) in compliance to the IS-637A standard. Internet Browser Alerts may be received over a non-standardized implementation of SMS. Decoding of the ‘Message Display Mode’ and ‘Multiple Encoding User Data’ subparameters is currently not supported. The 7135 currently does not support Data Network Number Type 010 (Internet Email Address), or addresses w/ Data Network Type of 001. 1.1.6 FCC compliance Emergency 911 When an emergency 911 call is originated by the user, the mobile will attempt to acquire any available system and originate the emergency call on that system, disregarding restrictions set by the roaming list. The FCC NPRM WT99-13, CC94-102 automatic analog A/B roaming option has been implemented for 911 emergency calls. Note that the 7135 contains Global Positioning System (GPS) support in accordance with IS-801.1 and meets the FCC’s E911 Phase I and Phase II requirements for emergency service. 24 June 2003 Kyocera Wireless Corp. Proprietary 2 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 1.1.7 80-B9339-13_A Web browsers The 7135 supports a number of HTML browsers running under Palm OS. The EIS Web Browser from Embedded Internet Solutions, Inc., and the EudoraWeb Browser from Qualcomm, Inc. are two HTML browsers which are provided as part of the 7135 software. The 7135 also provides the Openwave WAP Browser version 4.1.25i which uses Quick Net Connect (QNC) or asynchronous data service options. The WAP Client ID can be based on MIN or MDN as determined by PRI. The EudoraWeb and the Openwave browsers support 128-bit (strong) encryption. The 128-bit browser encryption technology is now exportable from the U.S. to most countries under the retail provision license exception, ENC. 1.1.8 IOTA The 7135 supports Openwave Phase I and the following Phase II IP-based Over the Air (IOTA) parameter update: · SPC/SPL · NAM block update · Authentication/A-key exchange 1.1.9 IS-683-A standard over-the-air service provisioning The mobile supports both over-the-air service provisioning (OTASP) and optional overthe-air parameter administration (OTAPA) as defined in the IS-683-A standard. 1.1.10 IS-683-A format preferred roaming list The mobile supports a preferred roaming list in the format defined in the IS-683-A standard. The Kyocera 7135 supports preferred roaming list sizes up to 4 Kbytes. The inclusion of Korean channels in the preferred roaming list is also supported. 1.1.11 TSB-50 A-key entry In accordance with the TSB-50 standard, pressing the keys that correspond to the letters AKEY (2539) will provide access to an A-key programming function. When this sequence is entered, an option is provided to allow the A-key programming function to be initiated. 1.1.12 Automatic volume control (Smart Sound) The automatic volume control feature combines a forward-link static gain audio boost and audio compressor to nominalize all forward-link audio levels to a consistent range. This range is then adjusted by the active speaker device (earpiece, headset or Analog Portable Hands Free carKit (APHFK)) volume control setting. The automatic volume control also monitors the user's background noise level, and automatically adjusts the user's volume based on that environmental noise. Automatic volume control can be enabled and disabled from the user menu. 24 June 2003 Kyocera Wireless Corp. Proprietary 3 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A 1.1.13 Downloadable roaming messages The roaming messages that are displayed on the top line of the idle display can be downloaded from the Kyocera Product Support Tool (PST) or the CDMA Air Interface Tool (CAIT) to allow these messages to be customized if desired. The messages can be up to 12 characters in length and the storage index of the messages and default values are listed in the following table. Roaming message Digital home Analoghome Digital solid roam Digital blink roam Analog solid roam Analog blink roam Index 1 2 3 4 5 6 Default string DIGITAL ANALOG DIGITAL ROAM DIGITAL ROAM ANALOG ROAM ANALOG ROAM 1.1.14 Resettable subsidy lock The subsidy lock can now be reset using the PST to allow the subsidy lock to be re-used, and the number of times that the subsidy lock code can be used also can be set using the PST. 1.1.15 Speakerphone The mobile features a speakerphone that is activated with a dedicated speakerphone key. 1.1.16 VR 4.3 Support (Voice Services) Voice services for the 7135 include Voice Tags, Voice Recognition Shortcuts, and the ability to record Voice Memos. These voice services are compliant with Qualcomm Voice Recognition Release 4.3. 1.1.17 TTY Support The TTY feature provides a method for reliably transporting the 45.45bps Baudot code in the audio path and is completely interoperable with the IS-733 and IS-127 standards. This feature makes digital wireless telephony accessible to TTY/TDD users. To support this feature on the 7135 requires a specialized cable to connect the phone to a TTY device. 1.1.18 GPS Support Global Positioning System (GPS) support is available in the Kyocera 7135. Using signals from the GPS satellite constellation and CDMA cell sites, the GPS functionality can enhance location services availability, accelerate the location determination process, and provide improved accuracy in accordance with TIA/EIA/IS-801-1. 24 June 2003 Kyocera Wireless Corp. Proprietary 4 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A 1.1.19 Mobile IP The Kyocera 7135 phone contains support for the Mobile Internet Protocol feature. This includes the mobile configuration, PPP, message formats, and procedures in accordance with TIA/EIA/IS-835. The ability to configure the Mobile IP Mode and associated parameters is available through the PST service programming application. It is also customer configurable, i.e. it can be pre-defined to be either ON/OFF by default through the customers’ individual PRI. 1.1.20 Enhanced Roaming Indicator Support for the Enhanced Roaming Indicator feature (ERI) is included in the Kyocera 7135 phone. An ERI file may be loaded onto the phone to configure the display for roaming indicators above 2 as specified in a Preferred Roaming List (PRL) also supporting ERI and loaded into the phone. Refer to TSB58B section 8.1 for detailed information on this feature. The 7135 does not support the additional functionality to allow bitmap images to be contained within the ERI file. 1.1.21 Number Assignment Module (NAM) The 7135 supports two NAMs. The ability for the user to select between a first and second NAM must be PRI enabled. If it is not, only a single NAM will be available to the user. The Auto-NAM feature is considered obsolete and is not provided. 1.1.22 SDIO card support The 7135 supports SDIO, enabling various third party card accessories to work with the device. 1.2 User Interface (UI) featuring bitmap display The large format LCD of the 7135 with bitmap UI provides an aesthetic and user friendly interface with the following basic features: · Variable sized fonts · Bold and regular fonts · Graphic icons · 16-bit color bitmap support · Bitmap and text animation support · Variable contrast · Variable brightness Additionally, there is a small external display viewable when the flip is closed. 24 June 2003 Kyocera Wireless Corp. Proprietary 5 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 1.2.1 80-B9339-13_A Up/down/OK keys Pressing the up and down page keys allows the user to navigate through the different menus and screens. Pressing in on the OK button allows the user to select menus, options, and advance through the UI. 1.2.2 End/Pwr key The End key and the Power key are combined into one (End/Pwr) key. Pressing and holding the End/Pwr key when the phone is off will turn on the phone. During normal operation, the function of the End/Pwr key is the same as the End key. Pressing and holding the End/Pwr key will power the phone off. 1.2.3 SMS memory This software release guarantees a minimum of 8 Kbytes of memory to store incoming messages. Under normal operating conditions there is ample memory available, depending on other applications/data stored in main memory of the device. If user memory is available, the phone can hold up to 200 messages. Maximum size per message is 544 Bytes. This software also includes support for mobile originated messaging, message concatenation, and user editable canned messages. 1.2.4 Contacts and recent calls Phone numbers in the Palm address book can be easily viewed and dialed with one hand. Adding voice recognition tags and speed dial entries is also easily done from the address book. The number of contacts that this device can store is limited only by available main memory. This amount will vary depending on what other applications/data are present. In normal use, this will allow several hundred address book entries. The recent calls list will hold up to 999 previous call numbers. The allowed number is settable by the user up to this maximum. The default is 99. 1.2.5 Vibrator support The vibrator can be enabled, disabled, or used in combination with the ringer according to the user’s preference. A special setting (silence all) will cause the phone to vibrate for all tones (alerts, ringer, SMS, etc.) This setting can be easily toggled by holding the side volume key up (normal sounds) or down (silence all). Note that when external power is applied from any accessory, the vibrator is disabled. The ringer will be used instead. 1.2.6 User interface languages The release SZ1.0.29/MZ1.0.44 supports only English at this time. French and Spanish may be supported in the future. 24 June 2003 Kyocera Wireless Corp. Proprietary 6 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 1.2.7 80-B9339-13_A Customizable sounds Ringers and flip sounds can be changed via the phone preferences application. MP3 and standard Palm sounds can be downloaded to the device for use as ringers and flip sounds. 1.2.8 Text Entry The mobile supports traditional alphanumeric text entry (multi-tap) as well as Palm pen based character recognition (graffiti). 1.2.9 Voicemail Access The voicemail number can be service programmed through the PST. This allows the user to press and hold the “1” key to access voice mail. This number can be changed by the user. 24 June 2003 Kyocera Wireless Corp. Proprietary 7 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A 2. Software Changes 2.1 Changes Made in the SZ1010/MZ1020 Release 2.1.1 SMS alerts not received while PDA sleeping With flip open and PDA sleeping (screen dark from inactivity), no alert was generated when an SMS was received. Not until the phone exited sleep, by pressing a button (e.g. OK button), did the phone alert the user. This issue has been resolved. 2.1.2 SMS stuck in pending Re-sending messages placed them back into the pending state (scheduled to be sent). However, messages that remained in pending were never sent out. After the user selected timer expired, only the most recent message was being sent. The remaining messages were not sent, thus they remained in the pending state. This issue has been resolved. 2.1.3 CDG3 failure CC34 in Sacramento While testing CDG3 section 8.1.1.9 (which sends a large number of MT SMS to the MS), a problem was seen where the T3 was not acking the BS quickly enough, causing a CC34 error. The occurrence of this problem was linked to times when the PDA was asleep and an incoming SMS arrived. This issue has been resolved. 2.1.4 Openwave Browser: Exit during start screen fails Exiting the Openwave WAP Browser (House button, END key, etc.) while the browser is still starting (splash screen or "starting browser please wait" still displayed), fails. The browser starts anyway, however the screen bitmaps will not update. While in this state, the softkeys are still functional and it is possible to navigate and exit the Browser. However, no other functionality is available until the browser is exited and launched again. This problem has been fixed. 2.1.5 Mobile display stuck in calling state Sometimes when a call has been initiated, the call never goes through and the mobile display indicates “Calling…”. The phone stays in this state until the end key is pressed. But the phone is in a state where it can’t place any calls. Any attempt to place a call will exhibit the same stuck in “Calling…” state. This state lasts indefinitely and requires battery removal and replacement to fix it. This problem is very rare and thus extremely difficult to reproduce. This was caused by tasks getting out of synchronization as to the calling state. The software has been changed to avoid such synchronization failures. 2.1.6 Issues with MP3 playback interaction with other applications There are interaction issues with other functions during MP3 playback. Using the phone app during MP3 playback could cause the “Phone Error” screen to display. To avoid these issues, the software has been changed so that it will pause the MP3 playback whenever the phone app is brought up. 24 June 2003 Kyocera Wireless Corp. Proprietary 8 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A Additionally, adjusting the ringer settings during MP3 playback exposed a race condition in the MP3 driver. The race condition has been eliminated. 2.1.7 Scrolling through SMS message list Tapping the page up or page down key while viewing the list of SMS messages would cause the list to page up or down. This has been corrected so that tapping the page up or page down key will move the selection one line up or down. In contrast, holding down the page up or down key will provide the page up or down functionality. 2.1.8 Ringer volume from loudspeaker low with headset attached The volume of the ringers as played from the loudspeaker was significantly lower when the headset was attached to the phone than without the headset. This problem has been significantly improved through both software and hardware changes. The volume of the ringers in these two scenarios is still not equivalent, but very close. 2.1.9 AMPS messaging failures at CTIA Some failures with AMPS messaging were discovered at the CTIA lab. This was traced to code which was mishandling IS-91 EP analog messages. This has been fixed. 2.1.10 PDA not locking with auto-lock It was discovered that there were some incompatibilities between the PDA auto-off feature and the auto-lock feature. These resulted in the PDA not locking after the autolock timeout. This has been fixed. 2.1.11 Screen turned dark, but PDA was still responsive Under certain circumstances involving a low battery and attaching external power, the PDA screen could turn dark. The PDA would still respond to key presses, originate a call, etc. However, the screen would remain dark. This has been fixed. 2.1.12 AddressBook moved to next category when opened Entering the AddressBook via the designated button would cycle the displayed category. This has been fixed. Now the AddressBook will open to the same category previously viewed by the user. 2.1.13 External signal strength indicator not updated when flip closed When the flip was closed, the signal strength indicator on the external LCD was not being updated. It would remain at whatever level it showed before the flip was closed. This has been fixed. 2.1.14 Calls dropped sometimes when VMN received When the phone was in a call while attached to the APHFK and voice answer had been enabled, the call would be dropped if a voice mail notification arrived. This has been fixed and calls will no longer be ended in this scenario. 24 June 2003 Kyocera Wireless Corp. Proprietary 9 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A 2.1.15 Stuck in resetting cycle after battery removed If the main battery is removed from the phone and the backup battery drains to a level where there is partial memory loss, then the phone can get into a cycle of repeated resets when the main battery is replaced. If the memory were completely lost, the phone would perform a hard reset and come up. This problem occurs when the loss has been insufficient to trigger a hard reset, but too much to allow a regular power up. A recovery mechanism has been introduced to trigger a hard reset if the phone gets into such a resetting cycle. 2.1.16 Headset audio level increased The gain settings for the headset volume have been increased to allow the headset to produce higher volume at the highest settings. 2.1.17 Buttons would register with flip closed With the flip closed, it was still possible for some of the buttons to be depressed; thus registering key presses on the phone’s display. The code now ignores key presses when the flip is closed. 2.1.18 Auto expand feature revealed passwords Passwords previously entered into secure text boxes could be revealed via the auto expand feature in unsecured text boxes. Now text entered as passwords will not be included in the list searched by the auto expand feature. 2.1.19 MP3 ringers would sometimes end with a zap When an MP3 ringer was playing and the user answered the call by pressing the Send key, the phone would often generate a zapping sound as the ringer stopped playing. Now MP3 ringers will end cleanly when calls are answered. 2.1.20 PDA instability addressed There have been dozens of individual problems fixed to address specific types of instability. In addition, certain externally developed software such as the HTML browser and the MP3 application have undergone extensive additional work to improve their stability. This Smartphone architecture remains vulnerable to issues of instability, because of the ability to load and run third party software. The Alpha and Beta testing which Kyocera Wireless Corp. has conducted shows that the stability of the device has improved greatly since the time of the initial SZ1000 software build. 2.1.21 External voice mail icon disappeared with open flip The icon on the external LCD to indicate the receipt of a voice mail notification would disappear whenever the flip was opened. This has been fixed so that the icon will remain on the external LCD until the message is acknowledged. 24 June 2003 Kyocera Wireless Corp. Proprietary 10 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A 2.1.22 Erroneous E911 callback mode after call ended early If an emergency call was originated and then ended before it was connected, the phone would erroneously indicate that it was in emergency callback mode. This has been fixed. 2.1.23 Incorporated recent QCT Patch releases This release incorporates changes provided by Qualcomm CDMA Technologies in their MSM5100 2.1C Patch 4 and Patch 5 releases. These changes include fixes in various areas of the code including Data Services, GPS, Call Processing, and Search. 2.1.24 CRC error on retune from GPS When the mobile retunes from GPS, several CRC errors occur. Qualcomm CDMA Technologies (QCT) is still working on resolving this problem. They refer to the issue as CR 22836, entitled “CRC failures on gpsOne test systems while sending SA request.“ They have provided at least four fixes to date. This build contains the so-called “delay flag fix” which was included in the MSM5100 2.1C Patch 4 code drop released by QCT. The description of the fix in the Application Note for this patch release reads: It was determined that the SRCH task requests SA from the PDSM task at the same time it instructs the MC task to turn on transmit. If MC "wins the race" and turns on Tx before PDSM sends the request, the message is sent out without issue. However, if the PDSM send "wins the race" and attempts to send the message before MC has completely turned on transmit, CRC errors occur. The fix involves waiting on a flag to make sure that transmit is on, then moving the SA data request in time from GPS post-visit processing to the point in time where SRCH received the MC_RESUMED_CDMA command. 2.2 Changes Made in the SZ1011/MZ1024 Release 2.2.1 MT-SMS message may become segmented During CDG-3 testing (tests 8.1.1.6 and 8.1.1.7) a problem was discovered in which one MT-SMS message was broken up into four separate messages. This problem occurred when external power was attached and the phone received several MT-SMS messages and a Voice Mail Notification in short succession (e.g. after power up). It was discovered that the mobile was not answering the call. Since the call never connected, the BS was sending the MS a Release Order after 10 seconds. The unsuccessful SMS call caused the network to determine that the phone had gone into analog mode. Thus, the base station was segmenting the message to fit the analog SMS delivery size. The mobile will now answer the call avoiding the segmentation issue. 2.2.2 CRC error on retune from GPS – additional enhancement When the mobile retunes from GPS, several CRC errors occur. A fix for this was included in the previously released software version that is described above in section 2.1.24. A change was added to the code in addition to the fix described there. This 24 June 2003 Kyocera Wireless Corp. Proprietary 11 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A change involves adding a delay equivalent to five PN rolls in the send/receive interaction between the mobile and the PDSM as added compensation for the timing differences. Testing has shown that the combination of these two fixes is most effective in addressing the CRC error problem. 2.2.3 Phone powered down while sending MO-SMS message The phone would sometimes power down when a MT-SMS message was received while the phone was in the process of sending a MO-SMS message. The code design was unable to handle a Mode Change request during an Origination attempt. The fix for this issue involves having the Call Manager code clean up the mobile-terminated "call” which, per design, does not force any mode change and avoids the conflict. 2.2.4 Unsuccessful Mobile IP call using AT commands If an IP address was entered using AT commands, the IP address would be stored in reverse order. The software was performing an invalid conversion on the AT command string. This has been resolved. 2.2.5 Pending origination in page response state A problem was caused by an origination attempt and a simultaneous incoming page to the mobile. This scenario would cause the software to get into a race condition where it would remain until the end key was pressed. The end key would clear the origination attempt. Then, the Layer 3 acknowledgement for the MT-SMS could finally be sent to the base station. This race condition has been addressed. 2.2.6 Pending SMS client in LPM This fix addresses another case of the problem described in section 2.2.5. It handles the case where the phone goes into Low Power Mode (LPM) before the race condition is cleared. 2.2.7 Openwave WAP browser and dormancy The implementation of the Openwave WAP browser on this phone assumed that the browser would be using a QNC call for a data connection. As a result, the PPP stack was torn down at the end of every call. In order to accommodate those customers who wish to run this browser with Service Option 33 calls, the browser implementation has been changed, so that it will not automatically tear down the PPP stack when a data call is ended. Thus, the Openwave WAP browser will leave the PPP stack open when the data session goes into dormant mode. 2.2.8 “Dial Before” number will default to nothing The “dial before” number setting which appears in the Phone Prefs app under the Dialing panel was defaulting to “1.” This is not correct. It now will default to nothing. 24 June 2003 Kyocera Wireless Corp. Proprietary 12 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 2.2.9 80-B9339-13_A Booting from a discharged battery Several problems were found and fixed which related to powering up a phone with a slightly charged battery and then removing it. The circumstances varied due to the exact voltage remaining in the battery, but all involved a slightly charged battery. These scenarios often led to the PDA going through a “hard reset” and, thus losing all the data stored thereon. These issues have all been addressed as much as possible. Data loss will still occur with a completely discharged main battery and backup battery (BUB). However, connecting and disconnecting a battery with a low charge will not cause data loss if the BUB still contains a charge. 2.2.10 MP3 Player crash (Assertion Failed Error) A conflict between the MP3 Player and incoming call functionality could cause the phone to crash. To duplicate the problem, the MP3 Player would have to be active when an incoming call was received. The user would then answer the call and switch back to the MP3 Player and start a track playing. This would result in an error message. At this point, if the user switched back to the Phone app instead of tapping “continue,” the phone UI would freeze. This problem has been fixed. 2.2.11 External LCD backlight activated periodically When the phone was in standby mode and the PDA is closed, the backlight for the external LCD would be activated briefly from time to time. This was in connection with RSSI updates being displayed on the external LCD. The backlight will no longer be activated in this scenario. 2.2.12 MO-SMS character count incorrect after copying a message When an MO-SMS message was created by copying an existing message, the character counter was not initialized properly. The counter would indicate that there were less character allowed in the message than there actually were. The counter is now initialized correctly. 2.2.13 MO-SMS can exceed maximum if call back number included When a user entered text for a MO-SMS message in the message screen, he was allowed to do so until he reached the maximum character count. This is to prevent the creation of a message that is too large to send as a single SMS message. However, if the user, after reaching this limit, went to the Options screen and included the call back number with the message, then the UI would insert the call back number into the message. This would cause the message to exceed the maximum size, resulting in some corrupted characters in the message text. 2.2.14 Programming the voice mail callback number via PST When the voice mail callback number was programmed via the Kyocera Product Support Tool (PST), the value did not appear in the UI. This has been fixed. The UI will now populate its voice mail callback number setting from the nv item written by the PST. 24 June 2003 Kyocera Wireless Corp. Proprietary 13 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A 2.2.15 Memory leak with carrier logo If the phone was powered on and off approximately 40 times or more without any resets (e.g. service programming, upgrades) being performed, the PDA would crash with a fatal error from memorymgr.c reporting an overlocked chunk. This was a result of the animation code copying bytes of the carrier logo bitmap from a database into heap memory but never clearing the heap memory. When heap space was exhausted, the fatal error would occur. This problem has been fixed. 2.3 Changes Made in the SZ1013/MZ1027 Release 2.3.1 GPS dynamic range improvements The 7135 GPS hardware implementation uses a SAW IF filter in the GPS signal path. This solution is different from that used by Qualcomm CDMA Technologies (QCT) on their development platform. The SAW IF filter provides much better performance in the presence of jamming signals. However, the channel response, in terms of phase and gain, for the 7135 is different from that of the hardware used by QCT. Thus the DSP baseband filter coefficients and thresholds recommended by QCT were not optimal for this implementation. QCT provided a new set of DSP baseband filter coefficients and thresholds to match the channel response of the 7135 hardware. In internal testing, these changes have shown a reduction in false alarms and an improvement in dynamic range without an impact to sensitivity. 2.3.2 OTASP completion status criteria relaxed Previously, the phone would show an OTASP session as having failed if any operation during the session failed. Thus, if an unlock attempt failed and then another succeeded, the overall status of the OTASP session would be reported as unsuccessful. This has been changed so that the success of the OTASP session is based on the success or failure of the last Commit request in the session. 2.3.3 Voice mail list text in Inbox initialized The voice mail list text in the Inbox contained garbage characters at the end. These were visible when the column was widened. The buffer used for this data was not being initialized properly. This has been corrected. 2.3.4 Fatal error with numbers ending in punctuation A fatal error would occur in the following scenario. Dial a number ending in nonalphanumeric characters (like punctuation). End the call. Select Find Number from the menu. This problem has been fixed. 2.3.5 Key presses during call which Attention Manager active During a call, the Attention Manager could replace the Phone App as the active application, for instance when an SMS message was received. In this state, the user could not press the keys to send DTMF signals to the other end of the call. Now, when the user 24 June 2003 Kyocera Wireless Corp. Proprietary 14 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A presses keys during a call and the Attention Manager is active, the Phone App will again be brought to the front of the display and it will process the key presses. 2.3.6 CHAP selection from Phone Preferences Previously, the user was unable to select CHAP authentication via the Phone Service menu in the Phone Preferences application. The setting would always revert to disabled. This has been fixed. 2.3.7 Crash when configuring or changing NAMs Sometimes a fatal error would occur after configuring a NAM or switching from one to the other. This has been fixed. 2.3.8 White screen when operating flip in a browser call During an Openwave WAP browser call, if the user closed and opened the flip, the screen would turn all white and the phone would freeze. This has been fixed. 2.3.9 Service programming of NAM 2 not available with OTKSL Previously, it was impossible to program NAM 2 via the Service Programming menu if the One Time Keypad Subsidy Lock (OTKSL) were used to access it. The Service Programming Code (SPC) had to be used. Now, the NAM 2 programming information is accessible using the OTKSL. 2.3.10 1X data icon not updated reliably The icon that indicates to the user that the phone has detected a 1X-capable network and, thus a 1X call is possible, was not working reliably. Changes were made in how the information is passed from the lower layers up to the UI and the icon is now changed whenever Call Processing updates the information. 2.3.11 ERI not shown every 5 minutes after PDA sleep The Enhanced Roaming Indicator should be shown on the UI every 5 minutes. This was being interrupted if the PDA slept. Now the ERI will be shown when the PDA comes out of sleep and every five minutes while the PDA does not sleep. 2.3.12 VR stuck in calling If the user attempted to place a call using voice recognition and the APHFK, the phone could get stuck in a calling state. This occurred infrequently, but was reproducible. The cause of the problem was found to be a race condition between the UI and the VR module. This has been addressed. 24 June 2003 Kyocera Wireless Corp. Proprietary 15 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A 2.4 Changes Made in the SZ1013/MZ1030 Release 2.4.1 Reset seen while switching clock rates in GPS sessions A reset condition was fixed that could occur during AGPS operations when the clock speed was switched from 4/3 TCXO (27MHz) to TCXO (20MHz). Thousands of calls under specific conditions were required to reproduce this reset. This reset could occur while in a normal call with network initiated AGPS operations. An E911 origination was not required to reproduce the problem. The problem occurred during AGPS call operations, when the vocoder interrupted the searcher task to access the QDSP while the searcher was switching the clock speed. The reset has been prevented by ensuring that these two operations do not occur simultaneously. 2.4.2 Increased microphone gain Based on feedback from users and from analysis in the lab, it was decided that the microphone gain should be increased slightly. This will compensate for low audio levels as heard at the other end of the call when the user holds the microphone farther from his/her mouth. 2.5 Changes Made in the SZ1017/MZ1030 Release 2.5.1 1X data icon not activated when phone first powered on A problem was found which caused the 1X data icon to not display correctly immediately after the phone was powered on. This icon indicates to the user that the phone has detected a 1X-capable network. The problem was caused by some variables in the UI layer responsible for passing system information to the Phone app. The variables were not being initialized properly. This has been fixed. 2.5.2 Phone powered off when viewing SMS during tethered dormancy Some incompatibilities were found in the interaction between the FaxModem app, the Alert Manager, the mechanism which switches from serial to USB mode and the data dormancy state. The phone would turn itself off if the user viewed an SMS message via the Alert Manager in a certain state. This would occur if the phone was attached to a computer via a USB connection and a data session was in dormant mode over that connection. The code which handles the state changes within the FaxModem app and within the phone were re-worked to handle this transition smoothly. 2.5.3 Phone remained in dormant mode after network release It was found that the phone would remain in dormant mode after the network had released the resources for the data session. This would occur when the data session was being run from a computer attached to the phone via the cradle or a data cable. This situation could be recreated by starting a data session and then not sending any data. Eventually, the network would time-out, releasing the data session. The phone would not inform the mobile pc that the data session had been released, but would remain in dormant mode. If 24 June 2003 Kyocera Wireless Corp. Proprietary 16 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A the pc attempted to send additional data, the transmission would fail. This has been fixed. The phone will now release the data session in response to the network’s release. 2.5.4 Shorten key tone length for phone keys The SEND, END, and CLR key tone length was longer than that used for the rest of the digit keys. This length has been shortened for consistency, and to improve responsiveness. 2.5.5 Keypad double entry While the phone was on, the phone keys occasionally registered twice when pressed. This was especially noticeable when in a call and accessing voice mail or entering a long credit card number. It was discovered that an extraneous key interrupt was generated when the phone was on. This interrupt has been masked off and ignored. 2.5.6 Do not play ringer volume when adjusting via side volume keys The up volume key will no longer play the ringer. This was changed for two reasons. First, when the volume side keys were used to adjust the ringer volume, it would often cause the PDA to slow down. Response to key presses would be delayed. Second, users have requested that the ringer not be played with the up volume key. They have noticed that adjusting volume with the down key does not cause a ringer sample to play and they prefer this behavior. The previous behavior caused inconveniences when they were trying to adjust ringers during meetings. 2.5.7 Digit collection is slow when DTMF length set to long The user preference (Phone prefs->Keypad->Key Beep->Length) is designed to enable users to navigate older automated phone systems with DTMFs. The older systems have trouble recognizing short DTMFs. However, when this preference is set, the key beep length for standby digit collection is also increased, slowing digit entry. The preference (and help screen) have been modified to only apply to the DTMF length while in a call. 2.5.8 Slow keypad response for digit collection To further improve digit collection responsiveness, the duration of key clicks has been shortened and the playing has been made asynchronous. Key tones have not been altered. 2.5.9 MP3 app settings should only apply to MP3 mode While the headset was installed, if any of the MP3 app settings (Volume, Balance, Bass, Treble) were adjusted, then this group of settings would become active for non-MP3 headset operation. This problem has been addressed. Changes to MP3 settings will only apply to MP3 mode. 2.5.10 MP3 should not play during hotsync If a hotsync was performed during MP3 playback, the playback audio would become very choppy and could not be halted until the hotsync was finished. MP3 playback will now 24 June 2003 Kyocera Wireless Corp. Proprietary 17 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A be paused when a hotsync begins. The user can resume the playback after the hotsync is complete. 2.5.11 Lockup after deleting MP3 ringer via File Manager Deleting an MP3 ringer via the File Manager and then going back to the Phone Prefs to change the ringer would result in a crash. This has been fixed. When the ringer was deleted, the UI was not notified and attempted to access memory (i.e. the ringer) that had been deleted. The UI now refreshes the ringer list before displaying it. 2.5.12 Crash when MMC card inserted/removed while Phone app running If the Phone app was present and the MMC card was inserted or removed, the event would go unrecognized. This could result in a crash, especially if the MP3 player was accessing the card when it was removed and then tried to access it again after removal. This has been fixed. 2.5.13 Unable to answer incoming call with large address book Under some conditions, the phone user would have difficulty answering a call while the phone worked on matching the incoming caller ID with entries in the AddressBook. This was seen when the AddressBook contained many entries (over 1000 entries) and when the incoming caller ID did not match an entry or matched an entry at the end of the list. This has been fixed by interrupting the look-up operation when input is detected from the user. 2.5.14 Highlight voicemail, press SEND will originate a call to VMN In the messages app, when the first item in the Inbox (i.e. the Voicemail entry) was highlighted, pressing the send key would not originate a call to the Voicemail Number (VMN). This issue has been addressed. If no VMN is specified, a dialog will come up to ask the user to provide a VMN. 2.5.15 No alert from message received during voice call If a message arrived at the phone while a voice call was in progress, no alert was given at the end of the call. The end of call notification was being missed and, as a result, the alert was not being played. This has been addressed. 2.5.16 Phone app launched from SMS with invalid link When viewing an SMS text message, pressing the SEND key should show the message links. If no valid links are found, the UI should display a warning indicating that no message links were found. However, the UI was launching the Phone app even when no valid links were found. This problem has been fixed. 2.5.17 Openwave Browser playing double alert on incoming message When an incoming SMS message was received during an Openwave Browser session, an alert was being played at the time the message was received and another was played after 24 June 2003 Kyocera Wireless Corp. Proprietary 18 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A the call was ended. Now, only the first alert will be played when a message is received during an Openwave Browser session. The same functionality applies to all data calls. 2.5.18 Crash resulted from message signatures containing carriage returns When populating the signature field in an SMS message, if the user entered carriage returns, the size of the signature would increase and would outrun the label size allocated for the display. Consequently the device would crash. The phone now truncates text to the size of the display field and puts an ellipsis at the end of it to indicate that the signature is longer than the displayed text. 2.5.19 Repeated Send from contact with no phone number caused crash By highlighting an AddressBook entry with no phone numbers and then pressing the Send key repeatedly, the user could cause the PDA to crash. The record was being locked each time the send key was pressed without being unlocked later. When the device exhausted the maximum number of locks, it crashed. This has been addressed by unlocking the contact at the appropriate time. 2.5.20 E911 mode exited by power down, next E911 call not labeled If the user entered emergency mode and then power cycled the phone, the UI would correctly indicate that the user was no longer in emergency mode. However, if the user then made another emergency call, the UI would still not indicate that the phone was in emergency mode. A flag indicating emergency mode was not being cleared at the appropriate time. This has been addressed. 2.5.21 Insert MMC card and open flip resulted in white display Inserting or removing an MMC card while the PDA was asleep would cause the device to wake up, but the LCD would remain off. In such a state, if the flip was opened, the backlight would turn on but the LCD would remain off. This would result in the display appearing blank and white. This issue has been fixed by waking up the device and the LCD on an MMC card insertion/removal. 2.5.22 Alarm during hotsync caused crash If an alarm went off while a hotsync was in progress, the PDA would crash. This was determined to be a debug crash used by Palm. The debugging feature was disabled and the issue was resolved. 2.5.23 Phone reported data service available in analog mode If the phone went into analog mode, the phone info application would continue to report that data service was available. This was rectified and the display now shows “No Data” when in analog mode. 24 June 2003 Kyocera Wireless Corp. Proprietary 19 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A 2.5.24 Duplicate address entries created without confirmation When the user saved an email address or a phone number from an SMS message, the phone was not performing duplicate detection. Thus, in this particular case, there was no warning if the address or phone number already existed in the database. A dialog is now shown to the user asking for confirmation before a duplicate entry is created from data contained in an SMS message. 2.6 Changes Made in the SZ1019/MZ1032 Release 2.6.1 Phone will now re-register after over-the-air service provisioning Previously the mobile would not register automatically following an OTASP, OTAPA or IOTA session. If NAM parameter blocks had been modified during the session, the mobile would need to re-register in order to receive pages from the network. Until some other action occurred to cause the mobile to register, mobile terminated calls would go to voice mail. The mobile will now force a registration when it enters the Call Processing state following an OTASP, OTAPA, or IOTA session in which the NAM parameters are updated. 2.6.2 Enhancement to OTASP Protocol Capabilities Response Message An enhancement was incorporated to the IS-683A OTASP Protocol Capabilities Response Message to implement carrier specific feature identifiers, in accordance with the latest ballot revision of TSB58. 2.6.3 Carrier specific initial programming message On power up when the phone determines that it has not been programmed (IMSI is set to default), a warning message will show in the phone UI. The user can dismiss it but it will show again on the next power on until the phone is programmed. 2.6.4 Caller ID not showing On incoming calls the caller ID briefly showed "Unavailable". However, if the call was missed, the phone would correctly show the caller ID. This happened with certain base stations like the Lucent 1900 that send two or more Alert with Info (AWI) messages during an incoming call. The phone UI was only handling the first AWI. It now updates the UI with the info from the last AWI. 2.6.5 Remove Workstyle application The Workstyle application was removed from the PDA and CD. Kyocera Wireless Corporation has decided not to promote this product. 2.6.6 Carrier specific control of editing network connection setting In previous builds, the Palm network settings for 1x and QNC could have been mistakenly changed by the user to render data connectivity inoperable. These special settings, which are defined by the carrier PRI file, are now uneditable except for the 24 June 2003 Kyocera Wireless Corp. Proprietary 20 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A network connection pull down menu. This pull down is typically set to wireless modem, but can be changed to another connection such as a third party VPN virtual interface. These VPN clients allow end users to access servers behind firewalls via IP tunneling. 2.6.7 Back light incorrectly toggles when pressed to wake device The LCD back light was mistakenly toggling whenever the PDA was manually put to sleep and awoken via the back light key. A special key event for updating the phone UI was being posted whenever the PDA was awoken. This unexpected key event was misinterpreted as another back light key. The code has been changed to correctly interpret this key. 2.7 Changes Made in the SZ1019/MZ1034 Release 2.7.1 Phone crashed attempting tethered USB data with Mobile IP disabled It was discovered that the phone would crash when a tethered data call was attempted in USB mode. Specifically, this problem occurred when a PPP call was attempted from a computer connected to the phone using USB, if the $QCMIP value was set to 0 (i.e. Mobile IP is disabled). This problem has been fixed. 2.8 Changes Made in the SZ1020/MZ1034 Release 2.8.1 Outgoing SMS message can show scheduled status indefinitely An outgoing message sent immediately could mistakenly show a clock icon (instead of a check mark) in the outgoing status. The algorithm for determining whether to show the clock icon compared the current time to the scheduled time of the message. When the message was created, the schedule time was incorrectly initialized. This has been addressed by correctly initializing the schedule time to the current time. 2.8.2 Recent calls entry not updated immediately after call ended For phones with large address books, it was possible that the recent calls database would not correctly update immediately after the call ended. The user would have to wait until the number was looked up in the address book before the entry would show. This has been corrected by creating the recent call entry immediately, and then updating the record when the address book match occurs. 2.8.3 Phone does not stop ringing immediately when call answered If a call was answered by opening the flip, the ringer did not stop immediately. The delay occurred due to processing of multiple tasks at the same time. It has been addressed by stopping the ringer audio at the interrupt level when the flip is opened instead of posting an event to stop the audio at a later time. 24 June 2003 Kyocera Wireless Corp. Proprietary 21 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 2.8.4 80-B9339-13_A Latin-1 encoded SMS not processed correctly For mobile originated and mobile terminated messages, Latin-1 encoding was not being handled. Code has been implemented to specifically accept and generate Latin-1 encoded messages. 2.8.5 Carrier specific preference to overwrite call history with look up number If a phone number matches an entry in the address book, it will be written to the call history instead of the original caller ID. This feature is specifically designed to handle networks where the caller ID received from an incoming call may differ from the number used to call the phone. It allows users to easily call back entries in the call history app and recent calls menu. 2.8.6 Support for Phone Number Length, Area Code Length, International Access Code and Country Code New NV items have been created to support the above listed features. These value are used to determine the correct number to dial if the number has a "+" in front of it. They are also used to format numbers that are being dialed. They can be edited by the user in the Phone Preferences->Dialing panel. 2.8.7 IS-41 workaround failure IS-41 workaround stopped working if 6245 was included as part of the user data. No email address was being presented to the user to save. This has been fixed by including the sender information in the list of email addresses and numbers that are extracted from the message. 2.8.8 Time not correctly updated when switching time zone The PDA time should not be offset when the preference for synchronizing PDA to CDMA time is set and the user changes the time zone. These preferences are found in Palm’s Date & Time panel. The PDA time should only be offset by the time zone setting when the “Manual Time Set” check box is checked since the CDMA time incorporates the time zone offset from the base station. 2.8.9 Hide/Show Voice Privacy setting from phone preference An NV item can be set by the carrier to hide or show the voice privacy setting located in the Phone Preferences->Phone Service panel. This setting allows the user to switch on or off enhanced voice privacy. Some carriers may want to provide this option to users. 2.9 Changes Made in the SZ1023/MZ1036 Release 2.9.1 Mobile sent unsolicited read ack messages Sometimes, the mobile was incorrectly generating Read Ack messages for MT SMS messages. If a message requested a Read Ack, the mobile would respond with Read Ack 24 June 2003 Kyocera Wireless Corp. Proprietary 22 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A messages for subsequent messages as well, even though no Read Ack had been requested for them. This was caused by a data structure not being initialized completely. The problem was fixed by initializing the structure correctly. 2.9.2 Roaming indicator now consistent on internal and external displays For carriers that use the universal roaming indicator (i.e. the delta symbol), modified the bitmap on the external display to be consistent with the one used in the internal phone display. It was showing an “R” on the external display. 2.9.3 Ringer not playing when in emergency callback mode Addressed missing alert issue during E911 privacy testing. If the mobile received a CALL FADE in E911 state, applications were not being informed about the call being lost. The ringer library would receive the incoming call signal, but would not play the ringer because it believed it was still in a call. The code has been fixed to correctly notify applications when the call is lost. 2.9.4 Web browser fatal exceptions The EIS Web browser has been updated to address two fatal errors. The first concerns a Javascript execution error which was reproducible by logging into AOL’s site. The second concerns a GIF library decoding issue discoverable by viewing GIF files with incorrect header files. The vendor has addressed these issues by more robustly handling error conditions found when parsing HTML. 2.9.5 Default multi-tap mode to digits when in numeric fields Certain numeric text fields (such as those editable phone numbers found in the address book or Calculator application) were incorrectly defaulting to alpha or symbol mode when using the phone digit keypad for multi-tap text entry. Numeric text fields now default to numeric mode. This bug also manifested itself as a crash when entering an AKEY value or when entering an alarm time for an event. 2.9.6 Speed address book name matches in phone UI For large address books there were problems matching a name at the end of the address book in time for the name to be displayed before the call was missed. A hashing mechanism has been put in place which greatly increases the speed with which a name is looked up in the address book. 2.9.7 Expanded SDIO support Additional SDIO driver support was added for the 3rd party accessory market. 2.9.8 PDA crash while attempting to dial a number from the Address Book If a phone number stored in the address book had two spaces before the number and an attempt was made from the address book to dial it, the PDA would crash. A problem with 24 June 2003 Kyocera Wireless Corp. Proprietary 23 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A a pointer was discovered where the code would advance the pointer past the leading spaces, and then free the pointer from the location where it had advanced to, causing the crash. This has been addressed by stripping the leading spaces without disturbing the value of the pointer itself. 2.9.9 Hotsync freeze when using USB If the Hotsync manager on the desktop machine did not have “Local USB” enabled and the user tried to perform a Hotsync, the PDA would freeze. An infinite loop was discovered where the USB driver was looking to connect to the PC. A timeout has been added to the driver to address this issue. 2.9.10 Quick Access button triggered by loud noises on certain headsets If certain third-party headsets were used with the phone, loud noises (like slamming car doors) could mistakenly cause the phone to detect the Quick Access button being pressed. This has been addressed by improving the detection and de-bounce logic for this key. 2.9.11 Pending SMS messages not erasable Users can now erase pending SMS messages. If an L3 ACK is not received (which could potentially happen if the PDA was manually reset while waiting for it), the message could potentially remain forever in the outbox. This is a rare occurrence, but the user can now manually remove those unwanted messages. 2.9.12 Phone reset with bad Channel List Message If the phone received a channel list message with an invalid channel, the phone could reset. This would occur when the phone tried to hash to the invalid channel. The phone will now validate any potential channel and stay on the current channel if a potential channel is invalid. 2.10 Changes Made in the SZ1024/MZ1038 Release 2.10.1 Fatal crash using PDA auto-lock security feature The PDA would crash as soon as the device was unlocked if the phone application was launched and the device had been locked using the auto-lock feature. The Palm OS Security application was not expecting the phone application to be running underneath it and was updating the wrong window. This has been fixed by hiding the phone application before presenting the security prompt. 2.10.2 ERI text overrides E911 text When the phone was in E911 callback mode, the enhanced roaming indicator text was being displayed on the first line of the standby screen. This was overwriting the “Emergency Calls Only” text that is necessary to display when in this mode. Now the E911 text has highest priority. 24 June 2003 Kyocera Wireless Corp. Proprietary 24 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A 2.10.3 Fatal exception when using MMC/SD cards MMC cards could get corrupted when being written to because a write buffer was not being initialized correctly. This could result in PDA crashes when accessing the memory card. Previously it was thought that pre-formatted cards caused this crash and the description “Using pre-formatted MMC cards may cause crash” was added to the known bugs section of this document. This known bug has been addressed and the item removed from the list. 2.10.4 Fatal alert crash when optimizing address book This fix addresses a crash introduced in SZ1023. Whenever the hash table (used for optimizing name lookups) was created, the PDA would crash if the address book entry contained a phone number field greater than 80 characters. This crash was fixed by increasing the buffer size used to process the phone numbers. 2.10.5 Call not originated when hit SEND in address book In the address book Address View of a record, the user can scroll up and down to select one of the five available numbers. Sometimes hitting SEND for an entry other than the first would result in the phone app showing, but not in a call origination. An error initializing a variable was discovered and fixed. 2.10.6 Call not originated for numbers with illegal characters Phone numbers in the address book can contain any text character. Some of the characters, like a semi-colon, are not dialable characters. When the user tried to dial a number that contained a non-dialable character, the phone app would show, but the call would not originate. The code has been changed to ignore anything after the non-dialable character instead of interpreting the entire number as non-dialable. 2.10.7 Incoming data call after closing Openwave Browser If the Openwave Browser was closed after the data session had gone into dormant mode, then the network would page the phone to close the session. Since this problem was dependent upon dormancy it would not occur in QNC data calls. The code has been changed so that in this scenario, the phone will automatically bring up a brief data call to notify the network of the end of the data session. 2.10.8 Tethered data calls with &C1 not working with Win2000 When the phone was configured to act as a wireless modem from a PC running Microsoft Windows 2000 and the &C1 setting was used, it would not support origination of data calls. The code has been changed to set the DCD line in &C1 mode as soon as the CONNECT indication is sent during the call origination state. Previously, it was waiting longer to set the line. The behavior of the DCD line at other times remains unchanged. Data call origination now works with &C1 and Windows 2000. 24 June 2003 Kyocera Wireless Corp. Proprietary 25 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A 2.10.9 No Roaming option persisted in a particular customer configuration In a particular customer configuration, the phone would remain in “No Roaming” mode if set there once by the user. If the user selected “No Roaming” for the Phone Prefs=>Phone Service=>Roam Option setting, the phone would go to a non-roaming mode. However, if the user selected “Automatic” after this, the setting would change in the UI, but the phone would remain in a non-roaming mode. This problem has been fixed for that particular customer configuration in which it occurred. 2.11 Changes Made in the SZ1029/MZ1044 Release 2.11.1 Allow MO-SMS sending to two digit numbers Some carriers require sending messages to two digit phone numbers. The code for prohibiting this has been removed. 2.11.2 Dormant mode indicator remains after disconnect in no signal state If the mobile lost service during a tethered packet data call, and the session was ended through dial up networking, the dormancy indicators would incorrectly show in the Phone App. The applications were not correctly being notified of transitions from dormancy to idle when in a PREV other than 6. 2.11.3 Graffiti2 support An updated version of Graffiti handwriting recognition has been included in this build. Character strokes are now more intuitive to learn since two strokes are now supported for certain characters. 2.11.4 Contrast adjustment The contrast of the device could inadvertently change whenever the screen was turned off and on via sleep or closing the flip. A timing issue was found in the LCD controller upon wakeup. Drivers have been modified to include sufficient delays before restoring the contrast setting. 2.11.5 Freeze when low battery alert (and other sounds) occur Under certain conditions the PDA would try to play two alert sounds at the same time. This could happen when the low battery alert occurred at the same time as the external power detection alert. It might also happen when keys are pressed at the same time as a phone alert occurs. Some of the sounds were being played in a background thread and were accessing non-reentrant code. The bug was fixed by moving the background sound playing to the foreground thread. 24 June 2003 Kyocera Wireless Corp. Proprietary 26 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A 2.11.6 OTKSL Menu update to include AMPS Home SID Added a new PRI item “OTKSL With AMPS SID” to include AMPS Home SID under OTKSL menu. When entered service programming using OTKSL, user can now program AMPS Home SID, if the PRI item was enabled. 2.11.7 Phone gets stuck in "Calling..." when placing an outgoing VR call If the user canceled a voice recognition initiated call, the phone UI could get stuck in the “Calling...” state. A small window was found in which the phone ignored the idle state notification. 2.11.8 Phone doesn't respond to key presses or flip In rare cases, the device could get into a state in which most key presses were ignored. These cases could have been caused by poor battery contacts falsely causing the PDA to go into emergency shut down mode. Code has been made more robust by unmasking the flip detection interrupt when external power is reapplied and rechecking flip state more often. False flip state detection could cause other keys to be ignored since they are masked when the flip is closed. 2.11.9 Menu for selecting Browser data settings on the Smartphone A separate (WAP) Browser setting is now available in the Palm Preferences application. The configurable settings are carrier specific, and operate independently of tethered and PDA network data settings. 2.11.10 Improvements in EIS Browser An updated Web browser has been included. The enhancements include numerous fixes of crashes, quicker page rendering, and backup of bookmarks. 2.11.11 Choosing an SMS read receipt notification on the Attention Manager shows the In box instead of Out box If there was a Read Receipt and a New Message alert on the Attention Manager, and the user chose the Read Receipt alert, the Messages application launched to the In box instead of the Out box. A record index, instead of a unique identifier, was being used to associate messages with notifications in the Attention Manager. 2.11.12 Crash sending SMS message while putting phone into cradle Sometimes inserting and removing phone from cradle immediately after sending an SMS message resulted in a crash. The form update code has been moved to an event handler rather than from a function callback to avoid potential stack overflows. 2.11.13 Calling #777 when in Dormant Mode During a non-tethered 1x data session, if the user interrupted transmission by launching the phone application, the phone would eventually enter dormant mode. However, it 24 June 2003 Kyocera Wireless Corp. Proprietary 27 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A could potentially connect and disconnect indefinitely if the data server was expecting an ACK. The phone application now times out to allow receipt of the data ACK. 2.11.14 Multi-segmented msgs with Latin-1 encoding stuck in pending Multi-segmented Latin-1 encoded messages sent to multiple recipients could get stuck in pending state. The phone would continue retrying and returning an error cause code of 34. The user data length was being set to one more than it should have been. 2.11.15 Blank screen after tapping Attention Manager blinking indicator If the user was viewing a message, received a text or voice mail notification, snoozed the Attention Manager, then deleted the messages, the Attention Manager would incorrectly show itself. The Attention Manager now correctly validates the message information before showing itself. 2.11.16 Fatal alerts from corrupted ROM A few phones have experienced fatal alerts even after a hard reset. The ROM image seems to have been corrupted. Additional precautions have been put in place to lock the ROM memory blocks and help prevent third party applications from writing to the ROM. 2.11.17 Updates from Qualcomm for DMSS 5100 2.1 Commercial Patch 6 The following items from Qualcomm DMSS 5100 2.1 Commercial Patch 6 (ND21756) were addressed: · 26444 - After emergency calls placed in AMPS systems SD 1.0, mobile may get stuck in AMPS A · 26639 - Retry of a failed emergency call in dynamic environment with multiple strong CDMA pilots may occur over AMPS · 26153,26251 - Abnormal data call termination may cause failure in handling subsequent MT voice calls · 26529 - High FER and CDMA call failure detected in factory with some MSM5100 ASICs · 21846 - Rx sensitivity failure after 1x HHO from PCS to cellular · 22463 - On rare occasions, mobile experiences an unexpected system loss when CCI is turned on · 26652 - On rare occasion, MSM demodulator is left with QPCH configuration after the mobile exits from the slotted sleep mode · 24456 - Occasional paging channel loss observed due to wrong mobile time setting after monitoring very early QPCH PI2 bits · 26172 - The mobile may reset during 1x-data call with at least one unassigned demodulating finger 24 June 2003 Kyocera Wireless Corp. Proprietary 28 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A 2.11.18 Generate three beeps at end of OTASP session The phone now generates 3 beeps at the end of an OTASP session, instead of 4 beeps. 2.11.19 UI battery gauging and AT+CBC response not close enough The battery gauging on the phone UI versus what was indicated in the +CBC response was not close enough. A change was made in the +CBC response to report the battery level (in percentage) based on the same data used for the UI display. If external power is connected, the phone will return 100% in response to AT+CBC. 2.11.20 AT+GMM displayed MOB_MODEL The software will now respond to the AT+GMM command with the mobile model number used as the marketing number of the phone, specifically 7135. The software was previously responding to this command with the MOB_MODEL as defined in the CDMA standard. 2.11.21 Missed calls due to phone reselecting for better service Incorporated Qualcomm ND21756 patch item 25265 - Delayed reselection causes mobile to use a less preferred system. This system determination change was incorporated to address an issue where the mobile was toggling between AMPS and CDMA upon reselection. In some cases, this toggling resulted in call-delivery problems in markets where AMPS and CDMA are present and the less preferred PRL entry used a generic cellular acquisition index. 2.11.22 Added PRI control of IS-801 messaging in idle emergency mode A PRI item has been added and associated with the “Enhancement to allow choice of supporting IS-801 messaging in idle emergency callback mode [26905]” change in the DMSS 5100 Release 2.1 Commercial ND21756 code drop. This new PRI item controls whether or not IS-801 messaging will be supported in idle emergency mode. This item is labeled “Pos Loc in E911 idle” in PST Service Programming. 2.11.23 Voice privacy icon not always displayed in MT calls Previously the phone was not always displaying the voice privacy icon during mobile terminated (MT) calls even though it had received and accurately processed the Long Code Transition Request Order. It was found that if the phone received this request order when the phone was still in Waiting For Answer state, then the notification that the phone had transitioned to voice privacy mode did not reach the UI. This has been fixed so that the UI will now be notified correctly and the voice privacy icon will be displayed. 24 June 2003 Kyocera Wireless Corp. Proprietary 29 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A 3. Known Bugs 3.1 Phone 3.1.1 Unexpected power cycle events Under certain rare conditions, the phone may experience a software failure leading to the phone power cycling or powering itself off. At the time of the release of version SZ1.0.29/MZ1.0.44, any known power cycle events are not critical to the normal usage of the phone. 3.1.2 Powerup and connecting external power If external power is quickly connected while the CDMA Module is powering up, the phone may go to charge mode instead of stand-by. 3.1.3 Behavior in poor RF conditions In certain poor RF conditions, the phone may stay searching for service for a long time and affect standby time. 3.1.4 Incoming call during Hotsync may cause crash The PDA can crash if an incoming call arrives while a Hotsync is in progress due to conflicts in accessing files. This is a Palm OS limitation and can be avoided by powering off the phone before performing a Hotsync. 24 June 2003 Kyocera Wireless Corp. Proprietary 30 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A 4. Cautions and Usage Notes 4.1 Phone 4.1.1 Software version, ESN, PRL, service center items display The two version displays are shown as a set of two letters and four digits (SZ1.0.29/MZ1.0.44) which together identify the software targets and releases. The two letters, SZ or MZ, specify that these releases are intended for the Kyocera 7135. The first digit identifies the major release level, the second digit identifies the minor release level, and the third and fourth digits identify the update revision of the software release. The phone software also contains information specific to a particular hardware/software combination. The phone model is identified by the Mobile Model Number and is equal to “75” decimal for the Kyocera 7135. The software is identified by the Mobile Firmware Revision and is equal to “1032” decimal for the software build MZ1.0.44. The ESN is displayed in decimal format. The PRL version is displayed. The ERI file version is displayed if the ERI feature is enabled. The phone stores the following information to aid service centers. · MCN · Service Center ID · Failure code · Automatically generated Warranty Date Code · Mobile Model Number equivalent to “75” decimal for Kyocera 7135 · Mobile Firmware Revision equivalent to “1032” decimal for software build MZ1.0.44 4.1.2 Battery charging Use only Kyocera chargers designed for this phone to recharge the battery. Applying incorrect voltages to the phone could cause damage to the phone and/or battery. 4.1.3 Standby time testing Standby time tests will be adversely affected by having the mobile connected to service programming cable. 4.1.4 Battery removal The phone should be turned off before removing the battery. The performance of the phone could be compromised by removing the battery while the phone is on. 24 June 2003 Kyocera Wireless Corp. Proprietary 31 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A 4.2 Accessories 4.2.1 Travel charger No special issues. 4.2.2 Desktop charger This charger has a slot for both a battery and a phone but charges them sequentially. Power is supplied to the slot which is filled first until that battery is charged. 4.2.3 Analog Portable Hands Free carKit (APHFK) The battery will only charge to approximately 85% of capacity using the Analog Portable Hands Free carKit (APHFK). This is by design to protect previous phone models which can be connected to the APHFK but cannot use the higher voltage. The APHFK does, however, provide sufficient current to support the phone in a phone call with a dead battery or no battery at all. 4.2.4 Car power adapter (CPA) No special issues. 4.2.5 Headset No special issues. 4.2.6 Universal Data Interface Programmer (UDIP) cable No special issues. 4.3 Support tools 4.3.1 Kyocera Product Support Tool (PST) Release 3.3.79 or higher of the PST application is required to successfully download software to and read/write all service programming items from/to the Kyocera Smartphone with software release SZ1.0.29/MZ1.0.44. 4.3.2 Mobile diagnostic software: CMDA Air Interface Tool (CAIT) Release 2.6.018.0 or higher of the CAIT application is required to provide total compatibility with software release SZ1.0.29/MZ1.0.44. 4.3.3 Roaming List Editor (RLE) Release 3.2.99 of the Roaming List Editor should be used with software release SZ1.0.29/MZ1.0.44. 24 June 2003 Kyocera Wireless Corp. Proprietary 32 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 4.3.4 80-B9339-13_A Palm Desktop The Connectivity Kit is not supported for the 7135. Use the Palm Desktop supplied with the phone to support the standard Palm hot sync functionality. The USB drivers for the PDA and the Phone are both contained within this installer. 24 June 2003 Kyocera Wireless Corp. Proprietary 33 7135 Release SZ1.0.29/MZ1.0.44 Compatibility Notes 80-B9339-13_A 5. Software Upgrades Software upgrades contain bug fixes and new features. Software upgrades are loaded into the phones using special hardware and software tools. If these tools are not used, the phone may operate poorly after the upgrade. Some of the possible symptoms are outlined below, as well as other considerations while upgrading to newer software. 5.1 RF performance If the proper version of the PST is not used, critical calibration data will be lost during the upgrade process. This will result in the phone operating with marginal to poor performance. 5.2 Boot block and software upgrades The software supports a “boot block” which is the last block to be erased and the first to be written during a software upgrade. In the event of an upgrade failure, due to loss of power or other problem, this special block allows the upgrade process to be repeated. If, however, the upgrade failure occurs during the write phase of the boot block, the phone will not be operable and can no longer be upgraded by the software tool. 5.3 Making use of new security features ESN/memory read/write prevention security measures are incorporated into the 7135 software. Currently, a limited set of security measures is being activated in the phones distributed from the manufacturer. 24 June 2003 Kyocera Wireless Corp. Proprietary 34