RMMobile Last updated: 07/09/2021 ###### Version: 4.10.06 > Version value is set at [version.groovy](./versioning/version.groovy) > RMMobile version below 4.1.x is prone to failure on any Android OS above 7.x see [DRIV-1173]() ###### Requires RMGate v7.1.09 ###### Backward Compatible with: RM 6.2.19 | RMGate v6.17 RMGate v7.1.00 * (DRIV-842) Garage before run * (DRIV-979) Auto Run Stop RMGate v7.0.24 * (DRCORE-800) Put dispatcher name in Audit Log RMGate v7.0.23 * (DRIV-972) Put MBTA features in config bits in ONboardDeviceCharacteristics RMGate v7.0.22 * (DRIV-965) Improve wording for configuring VIMA pane for display of address * (DRIV-961) Automatic logout form RMMobile when driver presses Login button RMGate v7.0.21 release skipped RMGate v7.0.20 * (DRIV-953) Allow dispatch to complete breaks RMGate v7.0.19 does not enable any additional RMMobile features, it only adds extra logging for: * (DRIV-880) Force Stale Driver Session logout on requesting AutoRunSwap * (DRIV-660) Force Bulk Stale Driver Session logout on Timer RMGate v7.0.18 enables the following RMMobile features: * (DRIV-880) Force Stale Driver Session logout on requesting AutoRunSwap RMGate v7.0.17 enables the following RMMobile features: * (DRIV-877) Suppress prepopulation of run and vehicle fields with AutoRunSwap RMGate v7.0.16 enables the following RMMobile features: * (DRIV-666) Log out stale driver signins RMGate v7.0.15 enables the following RMMobile features: * (DRIV-790) Make Driver Login ID validity checks for Request Run Swap / Windowless Dispatch RMGate v7.0.14 enables the following RMMobile features: * (DRIV-740) Always send 24 hour clock times on Trips. Convert for display only RMGate v7.0.13 enables the following RMMobile features: * (DRIV-437) Run Swap feature * (DRIV-512) RMGate configures RMMobile before login w/ runswap RMGate v7.0.12 enables the following RMMobile features: * (DRIV-1616) Automatic Run Start configuration RMGate v7.0.11 enables the following RMMobile features: * (DRIV-1599) RMGate: Support half hour timezones in lisense check * (DRIV-1604, DRIV-1620, DRIV-1625) Readme and RMGate.properties documentation updatea * (DRIV-1558 and DRIV-1592) Sort order for Dropoff/Pickup at same location and update Sort Order Epoch RMGate v7.0.10 enables the following RMMobile features: * (DRIV-1622) RMGate: Support DB version of 4 parts: Major.Minor.Hotfix.Build RMGate v7.0.09 enables the following RMMobile features: * (DRIV-1610) Configuration control over which navigation buttons appear on MapPane * (DRIV-1611) Provide an Arrive Timer so that Arrive Button is not enabled prior to NoEarlier time RMGate v7.0.08 enables the following features: * (DRIV-1598) RMLog flushing parameters configurable from rmgate.properties file * (DRIV-1601) Corrects NoShow request AuditLog parameters * (DRIV-1603) Able to mark pickup depart in Dispatch in addition to Driver depart in RMMobile RMGate v7.0.07 enables the following features: * (DRIV-1567) Suppress Connectivity Beep on Logon Pane RMGate v7.0.06 enables the following features: * (DRIV-1516) No Show timer should only start if it is later than the Early window of the trip * (DRIV-1444) Provide the ability in RMMobile to display a set time window for manifest lines Other features (DRIV-1493) in v7.0.06 Do not affect RMMobile 4.6.15 directly RMGate v7.0.05 enables the following features: * (DRIV-1491) RmGate - Send manifest size to device before sending manifest Other features in v7.0.05 Do not affect RMMobile directly RMGate v7.0.04 enables the following features. * Version 7 of the core app * (DRIV-1458) VIMA template without the ETA label * (DRIV-1415) Restrict the number of visible manifest lines * (DRIV-1416) Restrict the driver from entering pay fields on the Departure Pane * (DRIV-1442) Allow reordering of tabs on RMMobile screen * (DRIV-1450) Force Driver to view details of next manifest stop (Note if these features are not needed, it is safe to use RMGate v6.17.00 ) Contents --- * [Installation](#installation) * [Installing RMMobile Android](#installing-rmmobile_android) * [Home Screen Setup](#home-screen-setup-android) * [Configuration](#configuration) * [Manifest Item Colors](#manifest-item-color-codes) * [Error Codes Description](#error-codes-description) * [PTT Activation/Usage Instructions](#ptt-activationusage-instructions) * [GPS Emulaion](gps-emulation) * [Version Overview](#version-overview). Installation ------------ **NOTE:** Please turn on the option of installing applications from "Unknown Source" by going to "Settings"-->"Applications" And check "Unknown Source". This will enable installation of non-Market applications is possible by checking on "Unknown sources" RMMobile_Android can be installed in multiple ways: 1. Installing RMMobile_Android OTA 2. Installing RMMobile_Android through computer 3. Installing RMMobile_Android through beta (Crashlytics) Installing RMMobile_Android --------------------------- #### i. Installing RMMobile_Android OTA ---------------------------------- * Browse to http://rmmobile.routematch.com/ * Choose `Android` * Choose the latest version of RMMobile Android release * Once the download starts, drag the status-notification bar of Android handset/tablet * Click on RMMobile_Android when the download is turned. * Click on `Install` #### ii. Installing RMMobile_Android through computer ----------------------------------------------- > _"Not sure if this still works"_ -Reggie * Navigate to Android 'market' on the handset * Search for `AppInstaller` * Install `AppInstaller` by Gregory House * Connect the handset to the PC with a mini-USB cable * Choose "Disk drive" as the 'connect to PC' type. * Browse to 'RMMobile_Android.apk' file on the hard disk and move it to the Removable Disk (handset). * After RMMobile_Android.apk is move to the handset, disconnect it from the PC. * Scroll to "appInstaller" and run the "applInstaller" * Choose `com.routematch.mdcclient` to be Installed. * RMMobile_Android will appear in the application menu list after the process is complete. #### iii. Installing RMMobile_Android through beta (Crashlytics) ----------------------------------------------- > Note: this is for RMMobile 4.1.x and up * Obtain access to beta by invitation from a developer with admin access to RouteMatch General group > Note: as of Android OS 4.2 you can no longer downgrade from a higher version to a low version. You will have to uninstall the higher version of RMMobile before installing the lower version. Home Screen Setup (Android) --------------------------- > NOTE: when installing RMMobile, it is important to set RMMobile as the default home screen. You can do this by performing the following actions on most Android devices: * Install this version of RMMobile (2.7.02_precut#2 or higher). * Open "Settings". * Choose "Home". * Select "RMMobile". after performing these actions, RMMobile becomes the home screen, which means that pressing the "home" button, exiting the app or restarting the device will bring RMMobile up by default rather than the normal launcher ("desktop") application. Configuration ------------- Each phone's IP address must be recorded in the rmgate.properties file if the phone has static IP, such as: device.gateway.config.rmp.ipaddr.for.device(1) = 72.7.30.103 In case the phone is assigned a dynamic IP from the carrier, please provision the phone as: device.gateway.config.rmp.ipaddr.for.device(1) = * The RMGate server's IP address must be entered in the phone's settings screen. The rmgate.properties file's listener-port and the phone's settings screen's port must match. Generally we have used `55926` for this, but any reasonable port number can be used. device.server.port.to.read = 55926 device.server.port.to.write = 55926 Please note that the above comment pertains to the port on which RMGate will listen for inbound messages from the phone; RMGate always sends outbound messages to the phone on port `1234`. This will likely be improved at some point such that `"device.server.port.to.write = <>"` will be honored as one might have expected, since RMGate knows by `"device.server.name = (gateway)"` that it is operating in this mode. However, for now, the use of port 1234 is hard-coded. Device Properties ----------------- Device properties can be set as of RMMobile version `4.1.00` from the "Configuration" screen: ``` 0x0000000000000100 //Encrypt all outbound messages and decrypt all inbound messages with RSA. 0x0000000000000400 //Use External NMEA as source for GPS 0x0000000000000800 //Use Internal NMEA as source for GPS 0x0000000000001000 //Units (speed, distance etc.) are in SI(metric) instead of Imperial (US). This results in msg //flag x40 to be "ON" when sending messages to RMGate to indicate that SI(metric) units are used. 0x0000000000010000 //Navigates straight to the login screne with the ID as 1111, PIN as 2222 and Odometer as 3333 //pre-populated. Also allows for the vehicle in motion screen blocker to be disabled for 60 seconds. 0x0000000000002000 // use manifest location for odometer estimates if GPS is intermittent 0x0000000000020000 //Emulate GPS so that 1 minute the speed is more than 5 mph and the next minute it is less than 5mph. 0x0000000000040000 //In case satellite GPS is not available, and neither is any previous GPS (stop arrival), turning this //this bit on will pass the City and Zip of the destination as the starting address to Google maps/nav. 0x0000000000080000 //Debug to file (local device property) if need to be written to file before login response. 0x0000000000100000 //This bit is used for the driver login option, leaving it as zero uses legacy assignment to the vehicle, //while setting it to one will assign it to driver 0x0000000000200000 //This bit is used for switching between standard and military time in the left panel and status bar clocks 0x0000000000400000 //This bit is used for displaying using the odometer as an integer or to include the tenths place 0x0000000000800000 //This bit is used for displaying the current odometer value in the status bar 0x0000000001000000 //Use Sygic as the default navigation tool; this will be part of the login response from the rmgate but //this can also be set as a local device property. 0x0000000002000000 //This bit is to disable the use of the "Map" tab in order to prevent excess data from being used. 0x0000000004000000 //This bit is to store the previous day's odometer to be displayed as a suggestion at the next login. //Note that this bit is tied to 0x0000000000100000 where if the device is assigned to driver then this bit will //function as though it were off. The device must be assigned to vehicle for this bit to make sense/have use. 0x0000000008000000 //Diplay MagtekBullet swipe card reader Demo. 0x0000000010000000 //Display the cubic mockup tab. 0x0000000020000000 //Allow automatic payment collection(AFC) demo, turns. 0x0000000040000000 //Hide the odometer field in login screen and departure screens. 0x0000000080000000 //External NFC reader ACSR1222L is connected to rmmobile device. 0x0000000004000000L //This bit is to store the previous day's odometer to be displayed as a suggestion at the next login. // //Note that this bit is tied to 0x0000000000100000 where if the device is assigned to driver then this bit will //function as though it were off. The device must be assigned to vehicle for this bit to make sense/have use. 0x0000000008000000L //Demo MagtekBullet swipe card reader. 0x0000000010000000L //Display the cubic tab. 0x0000000040000000L //Allow user to override odometer collected through GPS. 0x0000000020000000L //Allow automatic payment demo. 0x0000000080000000L //External NFC reader ACSR1222L is connected to rmmobile device. 0x0000000100000000L //Replace 'exit' options with 'logoff', which returns to login screen with fresh application state //rather than exiting app entirely. 0x0000000200000000L //Enables PTT button to request a session 0x0000000400000000L //Tells us whether RMwAgent is an expected part of the system or not. (ie, is paired with VLU?) 0x0000000800000000L //If enabled, record GPS hits to file. 0x0000002000000000L //If enabled, read GPS hits from file. 0x0000004000000000L //Used to only show next stop pane and remove all other tabs 0x0000008000000000L //Used to bring up VIMA screen/What's Next screen block if the speed if greater than 20 mph/km 0x0000010000000000L //Allows RMMobile to communicate with other apps using intents (RMPay for example) 0x0000040000000000L //Enables WVA API for use; this will allow the tablet to get values such as engine speed and odometer see IV-1074 0x0000080000000000L // enabled the user to edit the expected fare value on Multifare v3 0x0000110000000000L // enables hand held validator option in rmpay 0x0000020000000000L // allows RMMobile to communicate with RMDriverPay fixed flavor ``` Logging -------- As of `RMMobile_Android_V1-6_precut#4`, debug statements can be 'echoed' to RMGate and/or written to log based on the login response from RMGate. The kind of debug statements that are desired to be 'echoed' to RMGate or written to RMMobile's log can be set as device properties. Please note that `RMGate 5.3 precut#3+` is required to receive a proper login response to set the type of logging desired. RMMobile logs are located in "\rmlogs" in the SDCard and as of `v1-6_precut4`, all log files older than 3 days are purged. As of `RMMobile_Android_v1.7_precut#2` the SDCard is given a new file structure for storing RouteMatch related data. The folder located with reference to the device is `~\mnt\sdcard\RMMobile` which has two subdirectories: `\rmlogs` and `\rmconfig`, the logs are stored in the `\rmlogs` folder and follow the same rules as above. If `0x0000000000080000` local device property is set, following debug categories can be specified in the "Configuration" screen to log the desired statements to file, before a successful response from rmgate is received. 0x0000000000000002 // information about where the execution is within the code (now entering, now leaving, etc.) 0x0000000000000004 // general warning for possible and handled exceptions (usually in try/catch blocks) 0x0000000000000008 // blocking/halting errors that cause a crash/reboot 0x0000000000000100 // general flow in the code and dev output. 0x0000000000000200 // related to GPS gathering/sending/etc. 0x0000000000000400 // related to incoming(outbound from RMGate) messages to the phone 0x0000000000000800 // related to outgoing(inbound to RMGate) messages from the phone 0x0000000000001000 // user interface related interactions (button pressed, processing selection, etc.) 0x0000000000002000 // related to tree DS holding MUWs. 0x0000000000004000 // raw NMEA sentences as they are received from DEV receiver. 0x0000000000008000 // this is complete garbage statements, should never really need them in the field. 0x0000000000010000 // outbound message which is an Ack to an inbound msg. 0x0000000000020000 // All the gps etc. related stuff related to target analysis. 0x0000000000040000 // Flush the VIMA log file every time it is written to 0x0000000000080000 // automatic passenger counter related debug. 0x0000000000200000 // anything related to generic peripherals. 0x0000000000400000 // Location only, without the extra noise... 0x0000000000800000 // Location only, without the extra noise... 0x0000000001000000 // J17 only related debug. 0x0000000002000000 // all the J17 stuff that's going OUT on the wire 0x0000000004000000 // all the J17 stuff that's ON the wire. 0x0000000008000000 // thread timing and queue sizes. 0x0000000010000000 // Detailed target analysis; per target distance on every gps hit, etc. 0x0000000020000000 // Detailed J17 info, how every J17 msg is constructed, parsed. 0x0000000100000000 // capture adb log - BE VERY MINDFUL WHEN TURNING THIS ON AS IT RESULTS IN HUGE LOG FILE SIZE AND WILL INCUR SIGNIFICANT OVERHEAD // After the desired log has been captured, MAKE SURE to turn OFF this bit and reboot the device 0x0000000200000000 // dump to (system) console... make sure exclusive of DEBUG_CAT_ADB.. 0x0000000400000000 // Do NOT buffer log messages before notifying (writeToFile or 'print to console') // i.e. if this bit is on, the log message will be written to file and printed to console verbatim 0x0000000800000000 // current memory/heap usage vs total allocated. > NOTE: These debug bits can be set in the table t_OnboardDevices of the agency's db under the columns DeviceDebugToFile1 and DeviceDebugToFile2 For RMMobile_Android v2.1d and earlier, recommended DeviceDebugToFile bits are: `43D0E` For RMMobile_Android v2.2+, recommended DeviceDebugToFile bits are: `800003D0E` From RMGate's readme: >> RMGate 5.3... + precut#3 implements dm#82254 (debug echo/file fields in signon-response, debug-echo inbound at any time) as part of rmp protocol v0.4. requires db change (dm#82350 in 28.277 and dm#82354 in 29.002) adding new columns to table t_OnboardDevices: DeviceCharacteristics2, DeviceDebugToServer, DeviceDebugToServer2, DeviceDebugToFile, and DeviceDebugToFile2. the "2" columns are the "top" 32 bits and the corresponding "non numbered" columns are the "bottom" 32 bits of the 64 bit concept represented by each such related set of columns. set the "to server" and/or "to file" bits you want for any devices (and be sure to start rmgate after that, so as to pick up changes) and when the device subsequently signs on, they will be delivered in the signon accepted response message and the device will obey. note that the bits in question here are NOT the rmgate bits; they are defined by the device software. the currently defined values for rmmobile 1.6 android are listed here. note that they are listed in hexadecimal, but you have to enter them in the database by hand until the "gps options" GUI is updated as part of the rm#6.x product... and the database uses decimal; remember to convert. also note that the hexadeimal values are 64 bits (16 digits)... and you need to split them into the hi/lo 32 (8 digits each) bit columns as described above. currenty there are no hi bits defined, so this amounts to setting the "2" columns to 0; but please understand what you are doing. and if you want "all", then remember that decimal -1 equals 0xFFFFFFFF. 0x0000000000000002 info; someone may care to know this. 0x0000000000000004 warning; coping with some condition but not happy about it. 0x0000000000000008 error; could not do something. 0x0000000000000100 general flow in the code and dev output. 0x0000000000000200 related to GPS gathering/sending/etc. 0x0000000000000400 incoming (outbound from RMGate) messages to the phone. 0x0000000000000800 outgoing (inbound to RMGate) messages from the phone. 0x0000000000001000 user interface related interactions (button pressed, processing selection, etc.) new rmgate dbg logging (0x0000080000000000) for "RMP GATEWAY debug-echo received from device" needs to be ON in "rmgate dbg" (which is the good old debugging concept you have always used on rmgate's cmdline, NOT the new "device debug" just discussed) if you want to log the "to server" device debug messages that you request and rmgate subsequently receives. capische? << Targeting --------- Prior to `RMMobile_Android_v1.8_precut#1` the code targeted API Level 7/Android 2.0/Eclair. Starting with this precut the code now targets API Level 10/Android 2.3.3/Gingerbread in order to provide feature functionality to devices that can support it. Manifest Item Color Codes ------------------------------------------------------------------------------------ Light Blue [0xFF9BCDFE] - Normal manifest item Green [0xFF00FF00] - Addition Yellow [0xFFFFFF00] - Change Red [0xFFFF0000] - Removal Magenta [0xFFFF00FF] - "Day-of" work order Orange [0xFFFFA500] - Optional stop; has NOT been opted in Light Green [0xFF99FF99] - Optional stop; has been opted in Error Codes Description ------------------------------------------------------------------------------------ From RMMobile_Android_v2.7.00_precut#27+, the following enhanced error codes and corresponding messages are observed: #### Configuration Errors (01##) ---------------------- Error Code | Message to User -----|----- 0100|Unknown login error. 0101|Please complete configuration! 0102|Please complete RMMobile 'settings' to configure RMGate. 0103|configData has not been initialized. 0104|Error while processing Arrive, deviceId is null; configuration data has not been initialized. 0105|Error while processing Depart, logonResponseInfo is null; configuration data has not been initialized. 0106|Error while processing DriverMessage. CannedMsgList is null; configuration data has not been initialized. 0107|Error while processing NoShow, deviceId is null; configuration data has not been initialized. 0108|Error while processing NoShow, NoShowReasonItems is null; configuration data has not been initialized. 0109|Unable to execute %s, deviceId is null; configData has not been initialized. 0110|RMMobile is not configured properly, please complete configuration. 0111|Error while processing OutOfOrder, deviceId is null; configuration data has not been initialized. 0112|Error while processing OutOfOrder, OutOfOrderReasonItems is null; configuration data has not been initialized. #### Dispatch Errors (02##) ---------------------- Error Code | Message to User -----|----- 0201|Please contact dispatch as the address associated with the selected stop is invalid. 0202|Please contact dispatch to configure RMGate properly to send lat/lon coordinates with stops. #### Empty Errors (03##) ------------------- Error Code | Message to User -----|----- 0301|Server Port is undefined. 0302|TTL is undefined. 0303|Retry Limit is undefined. #### GPS Errors (04##) ----------------- Error Code | Message to User -----|----- 0401|GPS unavailable, are you sure you want to open navigation? 0402|GPS is not supported on this platform. #### Invalid Errors (05##) --------------------- Error Code | Message to User -----|----- 0501|Invalid answer for %s. 0502|The Attendants value is invalid. Please enter the appropriate value and retry operation. 0503|Invalid Debug Properties; please enter a value for Debug Properties or 0 if using the default properties. 0504|Device ID is undefined. 0505|Invalid Device Properties; please enter a value for Device Properties or 0 if using the default properties. 0506|The Fare entry amount is invalid. Please enter the appropriate value and retry operation. 0507|The Guests value is invalid. Please enter the appropriate value and retry operation. 0508|Invalid ID.\nPlease enter a valid ID and try again. 0509|IP is invalid. 0510|"The odometer value entered is less than the last odometer entry of %s. Please enter a larger value and retry operation." 0511|The odometer value entered appears to be invalid, please enter a valid odometer value and retry operation. 0512|Invalid Password! 0513|Invalid PIN; please enter a valid PIN. 0514|The values to Prompts associated with this stop are invalid. Please cancel the operation, re-enter the appropriate value and retry operation. 0515|Retry Limit is invalid. 0516|Server Port is invalid. 0517|The Service Animals value is invalid. Please enter the appropriate value and retry operation. 0518|TTL is invalid. 0519|Someone else is already logged in on this device. 0520|User is already logged into a different vehicle. 0521|You are already logged in on this device. 0522|You are already logged in on this device. 0523|Wrong driver type. 0523|Device not assigned to this vehicle. 0524|Wrong driver type. 0525|Vehicle not found. Please try again. 0526|Vehicle name is unsupported. 0527|That Driver ID is already logged in on this device. #### Manifest Errors (06##) ---------------------- Error Code | Message to User -----|----- 0601|Failed to update Manifest! 0602|Error finding selected manifest record, action invalid. 0603|Manifest can only be processed in order. 0604|No manifest loaded. #### Message Errors (07##) --------------------- Error Code | Message to User -----|----- 0701|Unable to receive messages for the past 10 minutes. Will retry automatically, but you can try to manually restart app. 0702|Please restart RMMobile - Unable to restart message listener internally. 0703|Thread was interrupted when trying to send message. 0704|Exception thrown while attempting to sync time with server. 0705|Unable to communicate with server. 0706|Unable to send login request. 0707|Did not receive login response. 0708|Could not prepare to send time sync request (message context was occupied). 0709|Could not prepare to send login request message (message context was occupied). 0710|Could not begin to send login message (queue was unavailable). 0711|Could not begin to send time sync message (queue was unavailable). 0712|Server returned an unknown error. 0713|Server could not interpret login request. 0714|VLU hasn't logged in. 0715|TimeSync was null. 0716|Could not prepare to send password request message. 0717|Could not begin to send password message. 0718|Did not receive password response. 0719|Run field must have a value entered. 0720|Both the Run and Vehicle fields must have a value entered. #### MUW Errors (08##) ----------------- Error Code | Message to User -----|----- 0801|Cannot determine if we should provide single button perform; missing MUW %s. 0802|Error while processing Arrive. Unable to find muwId %s in data-store. 0803|Error while processing Perform. Unable to find muwId %s in data-store. #### Pickup Errors (09##) -------------------- Error Code | Message to User -----|----- 0901|No action can be taken on this drop-off since the pickup has not yet been completed. #### SD Card Errors (10##) --------------------- Error Code | Message to User -----|----- 1001|SD Card not mounted or read/write access not allowed. 1002|Failed to write backup to SD Card. #### Selected Index Errors (11##) ---------------------------- Error Code | Message to User -----|----- 1101|Error while processing DriverMessage. SelectedIndex = %s, but list has %s elements. 1102|Error while processing NoShow. SelectedIndex = %s, but array has %s elements. 1103|Error while processing OutOfOrder. SelectedIndex = %s, but array has %s elements. #### Settings Errors (12##) ---------------------- Error Code | Message to User -----|----- 1201|Not all settings have a stored value. Using default values for unspecified settings. #### Vehicle Errors (13##) --------------------- Error Code | Message to User -----|----- 1301|The Vehicle was not set. #### Wifi Errors (14##) ------------------ Error Code | Message to User -----|----- 1401|Could not connect, check your connection. PTT Activation/Usage Instructions ------------------------------------------------------------------------------------ From `RMMobile_Android_v2.8.00_precut#4+`, the PTT (push to talk) service must be activated in order to use it. This feature also requires ESChat Dispatch (the desktop client for PTT), `RMGate 6.4.16+` and `RM 6.2.16precut#5+`. Instructions on how to activate and use the service are as follows: #### Activation 1. Go to `Config` 2. If required, enter the RMGate settings and/or the RMGate-defined password 3. Go to `Device Properties` 4. Scroll down to `PTT`, set it to `On`, and hit `Save` - This will enable the `PTT Activation Code` field on the Configuration screen 5. Enter the activation code for the device - In order to receive an activation code, you must request one from an admin of the PTT service - As of 12/30/15, Dale Kartushyn, Miles Foster and Tina Dennis can give you an activation code - Note: you will also need an activation code for ESChat Dispatch 6. Once an activation code is entered, hit either `Save` or the activation button, the `A` next to the field - You will be notified about whether or not the PTT service was successfully activated - The duration of the activation task is based on the TTL and Retry Limit - Once activated, there will be a green PTT icon in the status bar after you log in to RMMobile - Note: the activation code is only valid for a single instance of RMMobile, i.e., if RMMobile is uninstalled and reinstalled, you will need a new activation code #### Usage Instructions 1. Before logging in to RMMobile, there are a few prerequisites: - The PTT tab must be on by including `400` in the `PHONES.device.gateway.config.rmp.tabs.to.show` property in rmgate.properties - The RTT (request to talk) button and the PRTT (priority request to talk) button must be included in the logon response by turning the `0x00010000` and `0x00020000` bits on, respectively - Both RM and ESChat Dispatch must be up and running 2. Once logged in to RMMobile, go to the `PTT` tab 3. Press either the `RTT` or the `PRTT` button - Dispatch will receive a request to talk message in RM that you can either call or reject - If `Call` is pressed in RM, you will be asked if you want to call dispatch in RMMobile - If `Yes` is pressed, a call will be established and you will be able to talk to dispatch via ESChat Dispatch - **Note: if successful, a `Call Established` message will be sent to dispatch. Otherwise, a `Call Failed` message will be sent** - There are soft buttons in both RMMobile (bottom-right) and ESChat Dispatch (bottom-left) that must be held down in order to talk to one another - If dispatch is talking, there will be a `[Dispatch] is talking...` message displayed in the PTT pane in RMMobile - If `No` is pressed or you do not respond to the message within 30 seconds, it will be automatically dismissed and a `No Longer Available` message will be sent to dispatch - If `Reject` is pressed in RM, you won't be notified in RMMobile 4. If dispatch initiates the request to talk, the conditions are similar to those of the previous step except instead of dispatch receiving a `No Longer Available` message, they will receive a `Not Available` message 5. The call may be ended by using the buttons in either RMMobile (bottom-left) or ESChat Dispatch (bottom-left) or automatically after 30 seconds of inactivity - Dispatch will receive a "Call Terminated" message once the call has ended GPS Emulation ------------------------------------------------------------------------------------ From `RMMobile_Android_v2.8.00_precut#7+`, there is a device setting, "Read GPS hits from file" (`0x0000002000000000`L bit), that should be used in conjunction with the "Record GPS hits to file" setting (`0x0000000800000000`L bit). If the "Record GPS hits to file" setting is on, GPS hits (in one second intervals) are recorded to a .csv file and stored in the "`/rmlogs/rmgps/`" directory of the RMMobile folder. If the `Read GPS hits from file` setting is on, RMMobile will read a single GPS hit at a time (in one second intervals) upon successful login. In order for this emulation to work, there should be only one valid GPS .csv file in the "`/rmlogs/rmgps/`" directory. Note: if both settings are on, RMMobile will only try to read from the GPS file and will not record any GPS hits i.e. the `Read GPS hits from file` setting overrides the `Record GPS hits to file` setting. # Version Overview: ------------------------------- RMMobile_Android v4.10.06 --- * Req for Pay features: - Pay Driver App 5.4.2 - Pay Models 1.5.6 * [RMDR-1112](https://t3.uberinternal.com/browse/RMDR-1112) MA_MBTA Trips not moving to tablet (backs out RMDR-881) * [RMDR-989](https://t3.uberinternal.com/browse/RMDR-989) Moved trip remains on original tablet RMMobile_Android v4.10.05 DO NOT USE - RMDR-881 fix was defective --- * Req for Pay features: - Pay Driver App 5.4.2 - Pay Models 1.5.6 * [RMDR-848](https://t3.uberinternal.com/browse/RMDR-848) RMMobile - Produce Heartbeat for RMGate * [RMDR-881](https://t3.uberinternal.com/browse/RMDR-881) Moved trip remains on original tablet RMMobile_Android v4.10.02 --- * Req for Pay features: - Pay Driver App 5.4.2 - Pay Models 1.5.6 * [RMDR-710](https://t3.uberinternal.com/browse/RMDR-710) RMMobile - No Logon Info Received error message RMMobile_Android v4.10.01 (HOTFIX) --- * Req for Pay features: - Pay Driver App 5.4.2 - Pay Models 1.5.6 * [RMC-973](https://t3.uberinternal.com/browse/RMC-973) PAY: Driver Pay App crashing due to missing jwt (agency: MN_MRVT) RMMobile_Android v4.10.00 --- * Req for Pay features: - Pay Driver App 5.4.2 - Pay Models 1.5.6 * [DRIV-843](https://rmjira.atlassian.net/browse/DRIV-843) Run Start Time Before Garage Start Time * [DRIV-979](https://rmjira.atlassian.net/browse/DRIV-979) Auto Run Stop RMMobile_Android v4.09.11 --- * Req for Pay features: - Pay Driver App 5.4.2 - Pay Models 1.5.6 * [DRIV-978](https://rmjira.atlassian.net/browse/DRIV-978) GPS Freezes - use Google Play Services FusedLocationProvider --- RMMobile_Android v4.9.10 (versions 4.9.01 through 4.9.09 skipped) --- * Req for Pay features: - Pay Driver App 5.4.2 - Pay Models 1.5.6 * [DRIV-1051](https://rmjira.atlassian.net/browse/DRIV-1051) RMPsrv_SocketToDevices ReceiveMessages thread has received an ACK for tag 'xxx' but ACK for tag 'xxx+1' was expected error results in NAKs for all subsequent outbound trips messages RMMobile_Android v4.9.1 - v4.9.3 skipped in development. Never released. --- RMMobile_Android v4.9.0 --- * Req for Pay features: - Pay Driver App 5.4.2 - Pay Models 1.5.6 * [DRIV-837](https://rmjira.atlassian.net/browse/DRIV-837) Receive “Failed to retrieve rider data" error when clicking Fare button in RMMobile RMMobile_Android v4.8.22 --- * Req for Pay features: - Pay Driver App 5.4.2 - Pay Models 1.5.6 * [DRIV-958](https://rmjira.atlassian.net/browse/DRIV-958) Customer Internal ID disappears from Manifest when Arrive button is clicked. * [DRIV-1013](https://rmjira.atlassian.net/browse/DRIV-1013) Restart of InboundMessageSocket reworked. * [DRIV-1043](https://rmjira.atlassian.net/browse/DRIV-1043) RMMobile Clean install gives bogus Config / Encryption popup to driver * [DRIV-1044](https://rmjira.atlassian.net/browse/DRIV-1044) RMMobile Color dialog doesn't work properly when being configured from RMGate RMMobile_Android v4.8.21 --- * Req for Pay features: - Pay Driver App 5.4.2 - Pay Models 1.5.6 * [DRIV-972](https://rmjira.atlassian.net/browse/DRIV-972) RMMobile Add configuration settings for recent HotFix features * [DRIV-1000](https://rmjira.atlassian.net/browse/DRIV-1000) If Invalid DeviceID is entered into RMMobile (either already present or just added), you get stuck in a Contacting Server. Please Wait loop. RMMobile_Android v4.8.20 --- * Req for Pay features: - Pay Driver App 5.4.2 - Pay Models 1.5.6 * [DRIV-962](https://rmjira.atlassian.net/browse/DRIV-962) RMMobile will allow you bypass the no show timer if you view details of another trip RMMobile_Android v4.8.19 --- * Req for Pay features: - Pay Driver App 5.4.2 - Pay Models 1.5.6 * [DRIV-1633](https://jira.routematch.com/browse/DRIV-1633) Unable to scroll down in Details pane * [DRIV-845](https://rmjira.atlassian.net/browse/DRIV-845) RMMobile 4.6.20 - Fixed Route - Departures are not "Auto Completing" * [DRIV-906](https://rmjira.atlassian.net/browse/DRIV-906) RMMobile Add dialog to Auto Run Swap request * [DRIV-987](https://rmjira.atlassian.net/browse/DRIV-987) RMMobile Outbound Socket Sender not graceful when message not sent * [DRIV-989](https://rmjira.atlassian.net/browse/DRIV-989) Fresh install of RMMobile 4.8.18 or 4.8.15 does not show run name field RMMobile_Android v4.8.18 --- * Req for Pay features: - Pay Driver App 5.4.2 - Pay Models 1.5.6 * [DRIV-961](https://rmjira.atlassian.net/browse/DRIV-961) Possible instance where RMMobile was "not running" but was still receiving messages RMMobile_Android v4.8.17 --- * Req for Pay features: - Pay Driver App 5.4.2 - Pay Models 1.5.6 * [DRIV-975](https://rmjira.atlassian.net/browse/DRIV-975) RMMobile Put timeout in inbound socket listener RMMobile_Android v4.8.16 --- * Req for Pay features: - Pay Driver App 5.4.2 - Pay Models 1.5.6 * [DRIV-???](https://rmjira.atlassian.net/browse/DRIV-???) Refresh Manifest button on Info Pane RMMobile_Android v4.8.15 --- * Req for Pay features: - Pay Driver App 5.4.2 - Pay Models 1.5.6 * [DRIV-897](https://rmjira.atlassian.net/browse/DRIV-897) RMMobile Implement HeartBeat with RMGate, and add logging when OutboundQueue starts filling RMMobile_Android v4.8.14 --- * Req for Pay features: - Pay Driver App 5.4.2 - Pay Models 1.5.6 * [DRIV-949](https://rmjira.atlassian.net/browse/DRIV-949) RMMobile Implement HeartBeat with RMGate, and add logging when OutboundQueue starts filling * [DRIV-950](https://rmjira.atlassian.net/browse/DRIV-950) RMMobile Remove Driver dialog about MUW updates, and do NOT make Driver accept Manifest changes * [DRIV-951](https://rmjira.atlassian.net/browse/DRIV-951) RMMobile Only audible alert is 3 beeps for the first x number of items on the manifest list * [DRIV-944](https://rmjira.atlassian.net/browse/DRIV-944) RMMobile Put break time on Info Tab * [DRIV-952](https://rmjira.atlassian.net/browse/DRIV-952) RMMobile Remove Stale Driver "continue" popup from AutoRunSwapRequest workflow RMMobile_Android v4.8.07 --- * Req for Pay features: - Pay Driver App 5.4.2 - Pay Models 1.5.6 * [DRIV-596](https://rmjira.atlassian.net/browse/DRIV-596) MBTA-Using the T9 keyboard causes RMMobile to freeze if driver receives a message at the same time * [DRIV-726](https://rmjira.atlassian.net/browse/DRIV-726) DRIV-1589 - VIMA screen frozen when Map in foreground, VIMA up and sent pop up dispatch message * [DRIV-740](https://rmjira.atlassian.net/browse/DRIV-740) NC_CATS- manifest should be limited to 2hr horizon, but we are seeing past 2hrs * [DRIV-783](https://rmjira.atlassian.net/browse/DRIV-783) Auto Run Swap - If I type in an invalid PIN or ID, the run field disappears when returned to the logon screen * [DRIV-877](https://rmjira.atlassian.net/browse/DRIV-877) Auto Run Swap - suppress auto pre-population of run and vehcile fields on Login Pane * [DRIV-880](https://rmjira.atlassian.net/browse/DRIV-880) RMGate should log a driver off of any open login sessions when logging into a vehicle * [DRIV-918](https://rmjira.atlassian.net/browse/DRIV-918) RMMobile - Change wording on UI for Garage Stop * [DRIV-933](https://rmjira.atlassian.net/browse/DRIV-933) Show Rec or other dispatch action is causing moved trips to be left behind on tablets, causing excessive no shows. RMMobile_Android v4.8.03 --- * Req for Pay features: - Pay Driver App 5.4.2 - Pay Models 1.5.6 * [DRIV-596](https://rmjira.atlassian.net/browse/DRIV-596) MBTA-Using the T9 keyboard causes RMMobile to freeze if driver receives a message at the same time * [DRIV-726](https://rmjira.atlassian.net/browse/DRIV-726) DRIV-1589 - VIMA screen frozen when Map in foreground, VIMA up and sent pop up dispatch message * [DRIV-740](https://rmjira.atlassian.net/browse/DRIV-740) NC_CATS- manifest should be limited to 2hr horizon, but we are seeing past 2hrs RMMobile_Android v4.7.07 --- * Req for Pay features: - Pay Driver App 5.4.2 - Pay Models 1.5.6 * [DRIV-437](https://https://rmjira.atlassian.net/browse/DRIV-437) RMMobile: Driver should be able specify Vehicle and Run at time of login for auto run swap * [DRIV-512](https://https://rmjira.atlassian.net/browse/DRIV-512) Create a ConfigResponse and ConfigMessage between RMMobile and RMGate pre-login * [DRIV-463](https://rmjira.atlassian.net/browse/DRIV-463) Driver Pay App is randomly calling out to the auth service to find not-existant trips * [DRIV-653](https://rmjira.atlassian.net/browse/DRIV-653) Run Swap sends messages after successful swap occurs * [DRIV-658](https://rmjira.atlassian.net/browse/DRIV-658) Explicitly enable Auto Run Start * [DRIV-628](https://https://rmjira.atlassian.net/browse/DRIV-628) RMMobile save configuration on return * [DRIV-714](https://https://rmjira.atlassian.net/browse/DRIV-714) Windowless Dispatch :: RMMobile cannot login if Internal Vehicle ID has a capital letter * [DRIV-718](https://https://rmjira.atlassian.net/browse/DRIV-718) RMMobile is unable to send canned messages * [DRIV-719](https://https://rmjira.atlassian.net/browse/DRIV-719) RMMobile: Unable to press Perform on Stop Run RMMobile_Android v4.6.21 --- * Req for Pay features: - Pay Driver App 5.2.0 - Pay Models 1.5.6 * [DRIV-1584](https://jira.routematch.com/browse/DRIV-1584) Manifest Signatures not making it to Signature Capture Report * [DRIV-1586](https://jira.routematch.com/browse/DRIV-1586) Remove ManifestActionPane from WhatsNext workflow * [DRIV-1616](https://jira.routematch.com/browse/DRIV-1616) Automatic Run Start * [DRIV-493](https://https://rmjira.atlassian.net/browse/DRIV-493) Fix GPS reporting interval in Emergency Mode RMMobile_Android v4.6.20 --- * Compatibility: - RMGate 7.0.8 (see readme for list of features enabled) * Compatibility for Pay features: - Pay Driver App 5.4.0 - RMwAgent 4.1.02 (for RDPAY-7170) - Pay Models 1.5.6 * [DRIV-226](https://jira.routematch.com/browse/DRIV-226) Updated guest count doesn't reflect on hhv after * [DRIV-1538](https://jira.routematch.com/browse/DRIV-1538) Removing flavor restrictions between pay driver and rmmobile - [DRIV-122](https://rmjira.atlassian.net/browse/DRIV-122) Removing flavor restrictions RMMobile_Android v4.6.20 --- * Compatibility: - RMGate 7.0.8 (see readme for list of features enabled) * Compatibility for Pay features: - Pay Driver App 5.4.0 - RMwAgent 4.1.02 (for RDPAY-7170) - Pay Models 1.5.6 * [DRIV-226](https://jira.routematch.com/browse/DRIV-226) Updated guest count doesn't reflect on hhv after * [DRIV-1538](https://jira.routematch.com/browse/DRIV-1538) Removing flavor restrictions between pay driver and rmmobile - [DRIV-122](https://rmjira.atlassian.net/browse/DRIV-122) Removing flavor restrictions RMMobile_Android v4.6.19 --- * Req for Pay features: - Pay Driver App 5.2.0 - Pay Models 1.5.6 * [DRIV-1593](https://jira.routematch.com/browse/DRIV-1593) Add logging only. Check if setup info is corrupted * [DEX-72](https://rmjira.atlassian.net/browse/DEX-72) There should not be any local configuration for suppressing connectivity beep. It is overwritten by RMGate setting * [DRIV-1610](https://jira.routematch.com/browse/DRIV-1610) RMGate properties to govern navigation buttons on MapPane * [DRIV-1611](https://jira.routematch.com/browse/DRIV-1611) RMMobile - Provide a way to block the user pressing ARRIVE until the No Earlier Than time has passed * [DRIV-1612](https://jira.routematch.com/browse/DRIV-1612) Dispatching-CSR Comments in Dispatching trigger an update to tablet * [DRIV-1614](https://jira.routematch.com/browse/DRIV-1614) Legacy Dispatch - When a break is started by the driver Performing the break start, the start time AND end time get updated in the dispatch grid, but does NOT get updated in RMMobile, which creates a mismatch between RMMobile and dispatch * [DRIV-1620](https://jira.routematch.com/browse/DRIV-1620) Please provide a way in RMMobile to display the Customer INternalID field on the details screen. RMMobile_Android v4.6.18 --- * Req for Pay features: - Pay Driver App 5.3.3 - Pay Models 1.5.6 * [DRIV-1569](https://jira.routematch.com/browse/DRIV-1569) Editing expected fare should not change the fare type selected * [DRIV-1578](https://jira.routematch.com/browse/DRIV-1578) WiFi Direct should be disconnected when RMMobile is closed * [DRIV-1594](https://jira.routematch.com/browse/DRIV-1594) Send button unresponsive after payment (w/ 4 paytypes) is made from driver pay app RMMobile_Android v4.6.17 --- * Req for Pay features: - Pay Driver App 5.2.0 - Pay Models 1.5.6 * [DRIV-1596](https://jira.routematch.com/browse/DRIV-1596) Legacy Dispatch - If Driver requests a No Show, then Departs the pickup without pressing CANCEL on the tablet, the No Show Request message remains in limbo in RMLink * [DRIV-1600](https://jira.routematch.com/browse/DRIV-1600) RMMobile: In relation to Geofencing Arrive button becomes disabled when exiting Google Navigation. RMMobile_Android v4.6.16 --- * Req for Pay features: - Pay Driver App 5.2.0 - Pay Models 1.5.6 * [DRIV-1548](https://jira.routematch.com/browse/DRIV-1548) Please remove the Execute steps in RMMobile to reduce the number of button presses needed. * [DRIV-1559](https://jira.routematch.com/browse/DRIV-1559) Arrive Geofence does not automatically update the Arrive button state for the selected item when entering or exiting the geofence * [DRIV-1560](https://jira.routematch.com/browse/DRIV-1560) If GPS is not locked on and Disable MDC Pickup Arrive is enabled, the arrive button for the current stop should be active * [DRIV-1563](https://jira.routematch.com/browse/DRIV-1563) RMMobile - Drivers shouldn't be able to scroll infinitely on the manifest page. * [DRIV-1564](https://jira.routematch.com/browse/DRIV-1564) RMMobile - Drivers shouldn't be able to scroll infinitely on the Details page. * [DRIV-1566](https://jira.routematch.com/browse/DRIV-1566) Rmmobile - Remove manifest list item render warning and better log LWUIT issues * [DRIV-1567](https://jira.routematch.com/browse/DRIV-1567) RMMobile should not beep everytime the connection is made to RMGate * [DRIV-1572](https://jira.routematch.com/browse/DRIV-1572) RMMobile - NoShow from Dispatch does not inform Driver of change * [DRIV-1575](https://jira.routematch.com/browse/DRIV-1575) RMMobile - When a message tapped from Send MsG tab rmmobile intermittently selects the message below the one that was tapped. * [DRIV-1583](https://jira.routematch.com/browse/DRIV-1583) Remove Scheduled Time Window from RMMobile details screen * [DRIV-1585](https://jira.routematch.com/browse/DRIV-1585) RMMobile Details Pane not working properly * [DRIV-1587](https://jira.routematch.com/browse/DRIV-1587) RMMobile Needs to be a mechanism to programmatically determine current UI Pane RMMobile_Android v4.6.15 --- * Req for Pay features: - Pay Driver App 5.2.0 - Pay Models 1.5.6 * [DRIV-1444](https://jira.routematch.com/browse/DRIV-1444) Provide the ability in RMMobile to display a set time window for manifest lines * [DRIV-1510](https://jira.routematch.com/browse/DRIV-1510) Perform in order is not working correctly for Route Start and Run Start lines * [DRIV-1516](https://jira.routematch.com/browse/DRIV-1516) No Show timer should only start if it is later than the Early window of the trip * [DRIV-1517](https://jira.routematch.com/browse/DRIV-1517) RMMobile - History tab item layout breaks when trying to display pickup/dropoff time * [DRIV-1522](https://jira.routematch.com/browse/DRIV-1522) Please modify the Navigate button in RMMobile to send the ADDRESS rather than the GEOCODE to maps. * [DRIV-1532](https://jira.routematch.com/browse/DRIV-1532) RMMobile calculation of stop time in seconds is just wrong * [DRIV-1541](https://jira.routematch.com/browse/DRIV-1541) Please allow JUMP button to work even if dropoff is not in the viewable window * [DRIV-1544](https://jira.routematch.com/browse/DRIV-1544) RMMobile Need to fix extra beeps * [DRIV-1545](https://jira.routematch.com/browse/DRIV-1545) The dialog to accept changes when a stop is updated, added or removed has come back in 4.6.07+ * [DRIV-1546](https://jira.routematch.com/browse/DRIV-1546) When DEPARTing a GROUP trip (as identified by Group Arrive), and Perform In Order is enabled, Allow the driver to DEPART (or NOSHOW) the riders of the group in any order * [DRIV-1552](https://jira.routematch.com/browse/DRIV-1552) Arrive Button not activating when selecting current stop * [DRIV-1553](https://jira.routematch.com/browse/DRIV-1553) Selecting NOSHOW on an arrived trip then saving causes the trip to become unarrived and is rejected from the tablet to dispatch, but is saved as noshowed in dispatch * [DRIV-1554](https://jira.routematch.com/browse/DRIV-1554) Selecting NOSHOW and Synchronize in dispatch on an arrived trip removes trip from tablet without pop up message * [DRIV-1556](https://jira.routematch.com/browse/DRIV-1556) RMMobile does not check the Service Animal check box in the Fare collection screen when a service animal is selected * [DRIV-1577](https://jira.routematch.com/browse/DRIV-1577) Determine why RMMobile is controlling the microphone when in the foreground RMMobile_Android v4.6.14 --- * Req for Pay features: - Pay Driver App 5.2.0 - Pay Models 1.5.6 * [DRIV-1530](https://jira.routematch.com/browse/DRIV-1530) Passing Customer Internal id from rmmobile to driver pay app * [DRIV-1535](https://jira.routematch.com/browse/DRIV-1535) Send all trips to pay driver app when manifest is done loading * [DRIV-1542](https://jira.routematch.com/browse/DRIV-1542) Payments not coming into pay portal RMMobile_Android v4.6.13 --- * Req for Pay features: - Pay Driver App 5.1.1 - RMwAgent 4.1.02 (for RDPAY-7170) - Pay Models 1.5.2 * [DRIV-1529](https://jira.routematch.com/browse/DRIV-1529) timestamp saved on "execute pressed" * [DRIV-1534](https://jira.routematch.com/browse/DRIV-1534) no-show flow is broken RMMobile_Android v4.6.12 --- * Req for Pay features: - Pay Driver App 5.1.1 - Pay Models 1.5.2 * [DRIV-1505](https://jira.routematch.com/browse/DRIV-1505) AU_Kalianna - GPS is off once upgraded to RMMoblie 4.6.05 * [DRIV-1507](https://jira.routematch.com/browse/DRIV-1507) Trip Times And Odometers Jumping Forward After Executes Dropoff * [DRIV-1509](https://jira.routematch.com/browse/DRIV-1509) RMMobile - Do away with manifest location estimates for odometer (REDO) * DRIV-1509 required updates to correct QA failure * [DRIV-1514](https://jira.routematch.com/browse/DRIV-1509) Please add different beep sequences for trip changes vs messages RMMobile_Android v4.6.11 --- * Req for Pay features: - Pay Driver App 5.1.1 - Pay Models 1.5.2 * [DRIV-1521](https://jira.routematch.com/browse/DRIV-1521) Login Screen should not refresh during data entry * [DRIV-1523](https://jira.routematch.com/browse/DRIV-1523) Stop Arrive Time is no longer getting populated with RMMobile and HHV Implementtaion RMMobile_Android v4.6.08 (PAY) --- * Req for Pay features: - RMGate 7.0.x (for DRIV-1497) - Pay Driver App 5.1.0 - RMwAgent 4.1.02 (for RDPAY-7170) - Pay Models 1.4.1 * [DRIV-1497](https://jira.routematch.com/browse/DRIV-1497) receive manifest size from rmgate * [RDPAY-7170](https://jira.routematch.com/browse/RDPAY-7170) Create HoneyDoMessage flag for target updates from Rmwagent * [DRIV-1498](https://jira.routematch.com/browse/DRIV-1498) The highlighted stop on the manifest should always be the top one, should not jump when performing work * [DRIV-1503](https://jira.routematch.com/browse/DRIV-1503) Tech Debt - Device Testing config will now save your previously entered login and not just (1111,2222) RMMobile_Android v4.6.07-1bd3c2ed -- [download apk](http://ota.routematch.com/Android/v-4-6-07/RMMobile_v4.6.07.apk) --- * Req for Pay features: - Pay Driver App 5.0.6-31aff862 - Pay Models 1.3.1 RMMobile_Android v4.6.07 --- * [DRIV-1441](https://jira.routematch.com/browse/DRIV-1441) Please provide a URL integration to Waze similar to what we do for Google and Sygic * [DRIV-1455](https://jira.routematch.com/browse/DRIV-1455) RMMobile screen navigation inconsistencies for payment panes * [DRIV-1457](https://jira.routematch.com/browse/DRIV-1457) Perform in order can be circumvented by exiting warning message and then trying again * [DRIV-1458](https://jira.routematch.com/browse/DRIV-1458) Please provide a VIMA template that does not show the ETA field * [DRIV-1471](https://jira.routematch.com/browse/DRIV-1471) RMMobile Persistent Notification should do something when selected * [DRIV-1473](https://jira.routematch.com/browse/DRIV-1473) RMMobile should not show a blank screen for Details of non-address Manifest Items * [DRIV-1475](https://jira.routematch.com/browse/DRIV-1475) Fare Collection v3 is incorrectly computing expected fare as expected fare + value of each attendant/guest/animal * [DRIV-1468](https://jira.routematch.com/browse/DRIV-1468) (Tech Debt) apply default fare type logic for edit expected fare * [RDPAY-4559](https://jira.routematch.com/browse/RDPAY-4559) Noshow request not working with HHV flow -- fixing for single trips * [RDPAY-7170](https://jira.routematch.com/browse/RDPAY-7170) Create HoneyDoMessage flag for target updates from Rmwagent RMMobile_Android v4.6.06-3c2038f5 -- [download apk](http://ota.routematch.com/Android/v-4-6-06/RMMobile_v4.6.06.apk) --- * Req for Pay features: - Pay Driver App 5.0.6-eab194c - Pay Models 1.3.0 RMMobile_Android v4.6.06 --- * [DRIV-1330](https://jira.routematch.com/browse/DRIV-1330) Store and Forward data should be stored in non-volatile memory * [DRIV-1415](https://jira.routematch.com/browse/DRIV-1415) Provide the ability in RMMobile to display a set number of manifest lines * [DRIV-1416](https://jira.routematch.com/browse/DRIV-1416) Provide a way to restrict the ability to edit on the perform fare screens in RMMobile * [DRIV-1442](https://jira.routematch.com/browse/DRIV-1442) Please provide the ability to reorder RMMobile tabs. Alternatively change hard coded order * [DRIV-1443](https://jira.routematch.com/browse/DRIV-1443) When exiting Google navigation using the home or back buttons, RMMobile sometimes closes. * [DRIV-1447](https://jira.routematch.com/browse/DRIV-1447) RMMobile should maintain history across exit / re-launch * [DRIV-1448](https://jira.routematch.com/browse/DRIV-1448) Disclaimer screen in RMMobile is being dismissed by the logon readiness test and shout not be. * [DRIV-1449](https://jira.routematch.com/browse/DRIV-1449) Changes made to Dropoff leg of trip cause the pickup legs to uncomplete. * [DRIV-1450](https://jira.routematch.com/browse/DRIV-1450) Provide a way to force the driver to review trip details for the upcoming stop before leaving current stop. * [DRIV-1452](https://jira.routematch.com/browse/DRIV-1452) RMMobile should handle Dispatcher modifications to in progress trips properly. * [DRIV-105](https://jira.routematch.com/browse/DRIV-1405) Modifying the dropoff leg after the pickup has been processed brings the pickup leg back on the tablet. * [RDPAY-6411](https://jira.routematch.com/browse/RDPAY-6411) noshowed trips disappear from the manifest after group arrive (HHV) * [RDPAY-6418](https://jira.routematch.com/browse/RDPAY-6418) store and forward not storing ANY information * [RDPAY-5695](https://jira.routematch.com/browse/RDPAY-5695) trip updates not coming to HHV * [RDPAY-4559](https://jira.routematch.com/browse/RDPAY-4559) noshow request not working with HHV flow RMMobile_Android v4.6.05-563b046 -- [download apk](http://ota.routematch.com/Android/v-4-6-05/RMMobile_v4.6.05.apk) --- * Req for Pay features: - Pay Driver App 5.0.6-eab194c - Pay Models 1.1.34 RMMobile_Android v4.6.05 --- * [DRIV-1386](https://jira.routematch.com/browse/DRIV-1386) Request to add address comments to manifest of RMMobile. * [DRIV-1394](https://jira.routematch.com/browse/DRIV-1394) Tablet times and odometer values off on several tablets * [RDPAY-5322](https://jira.routematch.com/browse/RDPAY-3522) HHV Pay should allow driver to mark a rider as 'No Show' * [RDPAY-5835](https://jira.routematch.com/browse/RDPAY-5835) If Rmmobile receives no pay results from Driver Pay it should return to manifest screen * [RDPAY-6116](https://jira.routematch.com/browse/RDPAY-6116) Transactions don't get recorded bc there's no authentication * [RDPAY-6194](https://jira.routematch.com/browse/RDPAY-6194) HHV button missing * [RDPAY-6202](https://jira.routematch.com/browse/RDPAY-6202) Perform button not working * [RDPAY-6267](https://jira.routematch.com/browse/RDPAY-6267) trips don't autoarrive if all trips are noshowed on grouparrive * [RDPAY-6311](https://jira.routematch.com/browse/RDPAY-6311) gps lat/lon not being correctly sent to validator * various javadocs updates KNOWN ISSUE - While working on DRIV-1394, found that RMMobile does not work properly if both Home and Manifest Tabs are both enabled. Created DRIV-1439 to track the issue. RMMobile_Android v4.6.04-8146a0ec -- [download apk](http://ota.routematch.com/Android/v-4-6-04/RMMobile_v4.6.04.apk) --- * Req for Pay features: - Pay Driver App 5.0.6-9030850 - Pay Models 1.1.34 RMMobile_Android v4.6.04 --- * [RDPAY-2024](https://jira.routematch.com/browse/RDPAY-2024) Update Sequence and Payload in order to open RmPay * [RDPAY-2129](https://jira.routematch.com/browse/RDPAY-2129) Transfer information from RmMobile and the Pay App * [RDPAY-2057](https://jira.routematch.com/browse/RDPAY-2057) Wire up pay module * [RDPAY-2234](https://jira.routematch.com/browse/RDPAY-2234) Add paymodel version checking handshake * [RDPAY-2235](https://jira.routematch.com/browse/RDPAY-2235) Remove all csv content related to rmmobile/paydriver communication * [RDPAY-2059](https://jira.routematch.com/browse/RDPAY-2059) Send payment information to RMGate once pay driver returns * [RDPAY-2058](https://jira.routematch.com/browse/RDPAY-2058) Launch pay driver on arrive (or group arrive) * [RDPAY-2345](https://jira.routematch.com/browse/RDPAY-2345) Create configuration setting to enable HHV mode * [RDPAY-4668](https://jira.routematch.com/browse/RDPAY-4668) Bind RouteDTO * [RDPAY-4838](https://jira.routematch.com/browse/RDPAY-4838) Bind LocationDTO * [RDPAY-5093](https://jira.routematch.com/browse/RDPAY-5093) Send correct route pattern name * [RDPAY-5089](https://jira.routematch.com/browse/RDPAY-5089) Implement Done by broadcasting to pay fixed * [RDPAY-5541](https://jira.routematch.com/browse/RDPAY-5541) Return the correct count to core * [RDPAY-5604](https://jira.routematch.com/browse/RDPAY-5604) Accept odometer reading entered by driver rather than hardcoding it RMMobile_Android v4.6.03-4f7067f0 -- [download apk](http://ota.routematch.com/Android/v-4-6-03/RMMobile_v4.6.03.apk) --- * Req for Pay features: - Pay Driver App 5.0.6-c5e45df - Pay Models 1.1.26 RMMobile_Android v4.6.03 --- * [DRIV-1302](https://jira.routematch.com/browse/DRIV-1302) VIMA screen for demand use does not show trip following outbound message to device. * [DRIV-1315](https://jira.routematch.com/browse/DRIV-1315) VIMA Screen should not show Trip Details and Assistance Needs with new VIMA Screen bit enabled * [DRIV-1316](https://jira.routematch.com/browse/DRIV-1316) New VIMA screen stops displaying upcoming stop after a cancellation is sent to the tablet * [DRIV-1327](https://jira.routematch.com/browse/DRIV-1327) RMMobile should show the Common Name on the VIMA Screen, not just the street address * [DRIV-1336](https://jira.routematch.com/browse/DRIV-1336) New VIMA not configurable * [DRIV-1342](https://jira.routematch.com/browse/DRIV-1342) VIMA Configuration not correct * [DRIV-1351](https://jira.routematch.com/browse/DRIV-1351) Tablet - VIMA Screen showing Next Stop * [DRIV-1391](https://jira.routematch.com/browse/DRIV-1391) Version 4.2.08 - VIMA screen * [DRIV-1266](https://jira.routematch.com/browse/DRIV-1266) RMMobile > Create separate ID and Config files * [DRIV-1395](https://jira.routematch.com/browse/DRIV-1395) RMMobile > 4.6.03 Should not hang up on launch with fast tablet * [DRIV-79](https://jira.routematch.com/browse/DRIV-79) When Hide Odometer is on RMMobile will not allow login until odometer is input RMMobile_Android v4.6.02-ea8f58fb -- [download apk](http://ota.routematch.com/Android/v-4-6-02/RMMobile_v4.6.02.apk) --- * [Pay Driver App 4.2.05 Prod](http://rmmobile.routematch.com/RMDriver_Pay/v4-2-05%20production/rmdp-4.2.05-prod-debug.apk) RMMobile_Android v4.6.02 --- * [DRIV-1329](https://jira.routematch.com/browse/DRIV-1329) RMMobile > Create separate ID and Config files * [DRIV-57](https://jira.routematch.com/browse/DRIV-57) RMMobile > Add support for receiving NMEA data from an external source * [DRIV-1258](https://jira.routematch.com/browse/DRIV-1258) Update RMMobile splash screen to new logo * [DRIV-1372](https://jira.routematch.com/browse/DRIV-1372) RMMobile needs to be updated to have the new Routematch logo as the app icon. RMMobile_Android v4.6.01-eb0dc742 -- [download apk](http://ota.routematch.com/Android/v-4-6-01/RMMobile_v4.6.01.apk) --- * [Pay Driver App 4.2.05 Prod](http://rmmobile.routematch.com/RMDriver_Pay/v4-2-05%20production/rmdp-4.2.05-prod-debug.apk) RMMobile_Android v4.6.01 --- * [RDPAY1-2074](https://jira.routematch.com/browse/RDPAY1-2074) edit expected fare payment feature for multifarev3 * [DRIV-1345](https://jira.routematch.com/browse/DRIV-1345) allow driver to change default fare type when edit expected fare enabled * [DRIV-89](https://jira.routematch.com/browse/DRIV-89) RMMobile > Still can No-Show a client if NoShow timer is enabled * [DRIV-1376](https://jira.routematch.com/browse/DRIV-1376) No Show timer should only have one countdown, not two simultaneous ones * [DRIV-1338](https://jira.routematch.com/browse/DRIV-1338) RMMobile / RMGate should not pass through unspecified fare types * [DRIV-1325](https://jira.routematch.com/browse/DRIV-1325) Inaccurate GPS lat/long values being sent from RMMobile 4.3.04 RMMobile_Android v4.6.00-406ff33f -- [download apk](http://ota.routematch.com/Android/v-4-6-00/RMMobile_v4.6.00.apk) --- * [Pay Driver App 4.2.05 Prod](http://rmmobile.routematch.com/RMDriver_Pay/v4-2-05%20production/rmdp-4.2.05-prod-debug.apk) RMMobile_Android v4.6.00 --- * [RDPAY1-2074](https://jira.routematch.com/browse/RDPAY1-2074) edit expected fare feature (config req) RMMobile_Android v4.3.08-fb9f08d7 (detached branch) -- [download apk](http://ota.routematch.com/Android/v-4-3-07/RMMobile_v4.3.07.apk) --- * [Pay Driver 4.2.11-1f105c52 Prod](http://rmmobile.routematch.com/RMDriver_Pay/v4-2-11%20production/rmdp-4.2.11-prod-debug.apk) * [DRIV-1345]() edit expected fare fixing default faretype in MultiFarev3 * [DRIV-1348]() show default fare payment * [DRIV-1349]() changing fare field RMMobile_Android v4.3.07-26038ebc (detached branch) --- * [DRIV-1333]() manifest not downloading RMMobile_Android v4.3.04 --- * [DRIV-1229](https://jira.routematch.com/browse/DRIV-1229) RMMobile sending bad GPS date stamp * [DRIV-1250](https://jira.routematch.com/browse/DRIV-1250) Driver Swap not updating Info tab's driver ID * [DRIV-1252](https://jira.routematch.com/browse/DRIV-1252) ANR on Tab A tablets * [DRIV-1255](https://jira.routematch.com/browse/DRIV-1255) Internal application errors still happening * [DRIV-1259](https://jira.routematch.com/browse/DRIV-1259) RMMobile > VIMA screen interrupts login * Adding Crashlytics distribution code RMMobile_Android v4.2.01 --- * [DRIV-1181](https://jira.routematch.com/browse/DRIV-1181) VIMA screen error displaying on tablets * [DRIV-1226](https://jira.routematch.com/browse/DRIV-1226) Internal application error displaying on tablets * [DRIV-1251](https://jira.routematch.com/browse/DRIV-1251) Null pointer component issue RMMobile_Android v4.1.00 --- ``` IV-1074 Capture odometer from AVM and reflect in RMMobile IV-1091 Make AVM odometer capture configurable IV-1099 Add fallback logic in case wva fails IV-1103 For QA > Create a button on Info Pane that will interrupt AVM connection IV-1079 Driver Swap button is disappearing in RMMobile 3.7.00, rendering driver swap useless IV-1093 Fix bug where new VIMA shows run-end instead of next stop IV-1067 Allow configuration of VIMA screen for demand rather than forcing the details always IV-1064 (forward apply) Purge Non-Pertinent Messages setting does not appear to be working PAY-1255 CLONE - RMPay > Odometer, completed and MDC status do not get updated for zero dollar trips. DRIV-1173 RMMobile > Add read/write permissions check for Android OS 7.0+ Adding a prompt on clean install that requires the user to give the app permission to edit files in RMMobile folder. Once granted RMMobile will restart. DRIV-71 RMMobile > Send ACK to RMwAgent that logoff is complete IV-1100 Merging beacons with master DRIV-1172 RMMobile > Fix missing merged code from beacons ``` RMMobile_Android v4.0.00 (3.8.00) --- ``` IV-1010 RMMOBILE: The Plus and Minus buttons for the counters are tiny IV-1072 Add dummy date if date is missing from trips handled by RMPay IV-1064 Purge Non-Pertinent Messages setting does not appear to be working ``` RMMobile_Android v3.7.02 --- ``` IV-919 RMMobile > Samsung Tab 4 muted when RMMobile active (suppressed audio) IV-1055 RMMobile > Android freezing and RMMobile isn't responding error at log in screen IV-1009 RMMOBILE: Fares Entered On Second Fare Entry Screen Are Not Shown On Run Summary Screen IV-801 RMMobile > Show the Upcoming Demand Response Trip Details on the VIMA Screen IV-969 RMMobile > Driver Swap and Short Turn button do not show up under Info tab after starting route/run and performing stops. ``` RMMobile_Android v3.6.00 --- ``` IV-152 RMMobile > Paddle does not stay in correct scroll position after arriving IV-914 RMMobile > Internal application error in handlingEDTException IV-926 RMMobile > ManifestListItemRenderer error while loading manifest IV-960 RMMobile > Remove home launcher functionality IV-983 BDC > Covert Alarm should not end unless dispatch ends the communication IV-1016 RMMobile > Show the Upcoming Demand Response Trip Details on the HOME tab IV-1027 RMMobile freezes after a message is sent from Dispatching ``` RMMobile_Android v3.5.01 --- ``` Removing PTT feature ``` RMMobile_Android v3.5.00 --- ``` IV-947 IV-935 RMMobile > Driver Swap and Short Turn buttons do not appear when run start back-cleared IV-848 RMMobile intermittently freezes and stops responding IV-809 RMMobile BDC > Separate the RTT and PRTT buttons on PTT tab (removed) IV-703 RMMobile > Screen draw of buttons is not working correctly IV-660 RMMobile > When driver comes back from break or emergency, driver swap & short turn button disappears IV-495 RMMobile > Driver Swap does not update Driver ID on Info tab when performing driver swap from Home tab IVDP-43 Ability to pass fare type (& sub-type/sub-reason) from RMPay Driver App back to Demand Verification (App) ``` RMMobile_Android v3.4.01 --- ``` IV-932 RMMobile > Accept fare subtype passed from RMDriver Pay ``` RMMobile_Android v3.4.00 --- ``` IV-658 RMMobile > When clicking the Jump button the Manifest screen locks up and will not scroll IV-774 RMMobile > Properly handle covert alarm calls during PTT call IV-829 RMMobile > Accept fare type passed from RMPay IV-876 RMMobile > Remove hotspot and wifi functionality IV-878 RMMobile > Properly handle covert alarm calls during dispatch broadcast call IV-880 RMMobile > Send message to dispatch when covert alarm button is pressed while in a covert alarm call IV-882 RMMobile/RMGate > "Call failed" messages to dispatch should include reason why the call failed IV-894 RMMobile > "Task Error" generated when attempting to login ``` RMMobile_Android v3.3.00 --- ``` IV-182 RMMobile > Add functionality to enable drivers to cancel remaining uncompleted stops on a trip from the tablet IV-220 RMMobile > Have to login twice to see updated canned messages from RMGate IV-764 RMMobile > Customer Signature Prompt doesn't work when set as pickup depart prompt IV-769 RMMobile > ESchat features should only be active when logged in to rmmobile. IV-773 RMMobile > Hotspot SSID and password should not be hard coded IV-776 RMMobile > After covert alarm event is resolved driver cannot talk to Dispatching during PTT call IV-806 RMMobile > Depart Prompts Do Not Appear When Multi-fare is Enabled IV-811 RMMobile > New VIMA should be displayed regardless of whether or not Home tab is enabled IV-815 RMMobile > When Dispatch Broadcast call is made while VIMA is on messages appear over the VIMA screen IV-816 RMMobile > If PTT call rings and Dispatch Broadcast call comes in Broadcast call is established but PTT call still rings IV-832 PTT > RMMobile freezes up at the Request to talk pop up after a PTT call is missed IV-848 RMMobile intermittently freezes and stops responding IV-875 RMMobile > Canned messages disappears from Messages tab IV-891 RMMobile > CannedMessage "Compose" button doesn't flow properly IV-900 When opting in/out of a FR stop error appears IV-913 RMMobile > Home Tab turns into Manifest when a driver swap fails ``` RMMobile_Android v3.2.00 --- ``` IV-372 Covert alarm button should trigger silent alarm that sends request to dispatch IV-455 RMMobile > The audio for a Dispatch Broadcast Call should be properly routed to Audio Logic Controller Speaker IV-521 RMMobile > After tapping 'Defer' on pickup depart payment screen the fare collected screen still shows IV-568 PTT > Sometimes after driver acknowledges a group of missed call messages the RTT is not automatically sent IV-570 RMMobile > PTT is intermittently deactivated IV-579 Accept call from dispatch to initiate one-way covert alarm call IV-610 PTT > When VIMA ends established call message should appear on tablet "Call terminated by VIMA" IV-611 PTT > PTT ends call when completing a stop manually IV-620 PTT > Call missed because it was not answered within 30 seconds message is not seen in Dispatch IV-670 RMMobile > Terminate covert alarm state and close microphone IV-702 PTT > When SAVOX microphone is plugged in to tablet all ringing and tablet generated sounds come out of tablet speaker instead of SAVOX speaker IV-738 RMMobile should hide the cancel button once the payment is processed IV-740 RMMobile > Driver ID should be displayed on Home tab IV-744 PTT > Call Established before VIMA screen appears will establish more calls IV-753 PTT> When call is placed to tablet & VIMA comes on before answered tablet doesn't stop ringing IV-770 PTT > Remove Red call end button from rmmobile IV-772 PTT > Getting call missed because another call is in progress message when there is no call in progress ``` RMMobile_Android v3.1.00 --- ``` IV-445 RMMobile > Vehicle tracking prior to login does not report location until after login IV-487 RMMobile > No Show countdown behavior does not match set value and behaves erratically IV-492 RMMobile > Improve Driver Swap Button Enable/Disable Logic IV-500 RMMobile > Enable/Disable HotSpot when launching app (Forward Apply) IV-501 RMMobile > Enable/Disable WiFi when launching app (Forward Apply) IV-502 RMMobile will send driver credentials to RMPay Driver app upon login (Forward Apply) IV-613 Broadcast PTT > When the call is ended from ES Chat it takes over 20 seconds for the call terminated message to pop up on the tablet. IV-617 RMMobile > Cannot send canned messages when Home, Messages, and Mailbox tabs are enabled IV-642 RMMobile> Queued call pop up is not going away from the tablet IV-643 PTT > If there is an incoming call is in progress and another call is placed, the second call should be a missed call IV-681 Route & Run start/end do not appear on the manifest for DR IV-694 RMMobile > Emergency mode not working ``` RMMobile_Android v2.13.00 --- ``` IV-176 RMMobile > Illegal Argument Exception - Component is already contained in Container (MediumLabel) - This isn't a complete fix, it just lowers the possibility of it happening IV-238 Mixed trips between multiple driver ID's - Only filters for driver based work on login, filter turned off when swapping IV-365 Driver should be required to acknowledge missed call(s) IV-450 RMMobile > Generate audible indication that a PTT call is being received IV-453 RMMobile > Display popup message indicating that a Dispatch Broadcast Call is being received IV-454 RMMobile > Automatically accept Dispatch Broadcast Call IV-515 Driver Swap > Present number keypad to user instead of full keyboard. IV-516 RMMobile > Generate short audible tone to indicate that a Broadcast Call is being received IV-518 RMMobile > Display icon in status bar to indicate that PTT call is in-progress IV-519 RMMobile > Display icon in status bar to indicate that Dispatch Broadcast call is in-progress IV-522 RMMobile> PTT> RTT pop up dialog box will not go away from rmmobile IV-523 RMMobile > PTT When call is placed while VIMA screen is on, call should ring for 30 seconds before ending IV-566 RMMobile > FR Paddle does not load after login IV-571 RMMobile > PTT calls disconnected by the dispatcher or timeout should generate popup message IV-598 Turn off the trip filtering snippet when a driver swap happens IV-602 PTT scenario > If dispatcher calls tablet while another call is in progress, after the first call ends the 2nd call starts to be placed IV-603 PTT scenario > No acknowledgement message appears after unusual scenario happens IV-619 Icon request for current version of application for Push to Talk, Active Call ``` RMMobile_Android v2.12.00 --- ``` - Fixing GPS emulation so that lock screen doesn't interrupt login when testing IV-232 RMMobile > When Guests or Attendants are added in RMMobile a service animal is automatically added IV-230 Guest and attendant counts are not sent when using para-trip fare collection v2 & v3 IV-264 Added a fleet-wide stop size radius field to login response protocol to replace the local setting for "Auto Arrive/Depart (para)" flag and to set the value itself IV-309 RMMobile > Guest and attendant counts are not incremented properly after button press IV-238 Mixed trips between multiple driver ID's IV-299 RMMobile > Home (WhatsNext) tab generating NullPointExceptions IV-368 Users should receive indication that the RTT or PRTT was sent IV-452 RMMobile > Automatically send RMLink message to dispatch when call is terminated from the vehicle IV-364 RMMobile should maintain missed call log IV-451 RMMobile > Send RMLink message with reason code to dispatch when call is missed IV-366 Call terminated popup message should automatically close IV-367 Driver acknowledgment of missed call should trigger an RTT message to dispatch IV-490 RMMobile_2.11.01 - Tablet stopped reporting GPS / Completing work - IV-499 Forward apply to RMMobile 2.12.0 IV-282 RMMobile > Canned Messages are not being sent when 2 tabs are enabled (w/ Home Tab + Messages) - Canned messages will now return the user to the mailbox screen as intended IV-219 Ability to Display Address Phone and Address Comments On RMMobile Details Screen IV-362 Remove option to reject a call request IV-370 VIMA screen should immediately end an in progress call ``` RMMobile_Android_v2.11.00_precut#4 --- ``` IV-109 RMMobile > Provide Driver Swap functionality - Subtask: IV-318 Implement interface with RMGate ``` RMMobile_Android_v2.11.00_precut#3 --- ``` IV-379 Show the popup in the case where the logoff shows the Login screen. ``` RMMobile_Android_v2.11.00_precut#2 --- ``` IV-316 Add button for driver swap - Added button for driver swap to Info and WhatsNext panes IV-288 RMMobile > Making driver swap access configurable - Subtask: IV-322 Receive setting from RMGate - Subtask: IV-323 Apply setting from RMGate IV-261 Prevent pop-up for remote logoff if user is still logged in ``` RMMobile_Android_v2.11.00_precut#1 --- ``` Removed deprecated methods and variables from RMLogger Removed IV-273 IV-261 RMMobile 2.10.01 > Remote Logoff from Dispatching> "Attempt to get length of null array" error IV-254 RMMobile > Dynamically choosing to set app launcher to default based off Android OS - RMMobile icon no longer disappears - Home button is used to rotate between RMMobile and Home Kiosk IV-201 RMMobile > When PHONES.device.gateway.config.rmp.tabs.to.show = 0002 in RMGate cannot Login to RMMobile - If there are no tabs enabled OR there custom tabs are enabled but prompts are "none", an error will popup stating "no tabs configured to show" IV-287 RMMobile > Currently logged in Driver ID should be shown under Info tab IV-337 RMMobile > Illegal Argument Exception - Component is already contained in Container (Container) IV-338 Create stack trace for popup message ``` RMMobile_Android_v2.10.02S --- ``` Removed precut designation. - Debug bits hard coded to Reggie's recommendation in future cases IV-293 RMMobile > Auto-depart time for para stops should be sent even when stop manually departed beforehand - Auto-depart now works for multiple pane combinations. ``` RMMobile_Android_v2.10.02S_precut#2 --- ``` IV-293 RMMobile > Auto-depart time for para stops should be sent even when stop manually departed beforehand - Auto depart time will now send when the departure button "Send" is pressed. - If the driver decides not to press it, the time will send after they leave the threshold. ``` RMMobile_Android_v2.10.02S_precut#1 --- ``` IV-273 Provide one-off RMMobile release to set default settings for "Auto arrive/depart (para)" and "Stop radius" ``` RMMobile_Android_v2.10.02_precut#1 --- ``` IV-187 RMMobile Sending in Fare Collected Amount 1 Cent Less Without Driver Modification IV-254 RMMobile > Dynamically choosing to set app launcher to default based off Android OS - No more Honeycomb (H) versions will be needed in the future IV-238 RMMobile accepting and displaying stops received prior to driver logon - All trip messages prior to login are cleared to make room for new trips ``` RMMobile_Android_v2.10.01H --- ``` Releasing a version for Honeycomb version. ``` RMMobile_Android_v2.10.01 --- ``` Removed precut designation. ``` RMMobile_Android_v2.10.01_precut#1 --- ``` IV-176 RMMobile > Illegal Argument Exception - Component is already contained in Container - Sending this back into the field with better logging; unable to find source problem IV-215 RMMobile > Stops do not auto-clear off of tablet for 3.0.00 PC11 using tablet only solution IV-186 RMMobile > After tapping "Break" and then Pressing "Back" RMMobile take you to unusual screen - Break screen (within info tab) will no longer return you to WhatsNext screen when WhatsNext tab is enabled. ``` RMMobile_Android_v2.10.00 --- ``` Removed precut designation. ``` RMMobile_Android_v2.10.00H --- ``` Removed precut designation. ``` RMMobile_Android_v2.10.00H_precut#1 --- ``` IV-184 Kiosk mode should not be required in Android Honeycomb - (For Honeycomb Android OS Only) ``` RMMobile_Android_v2.10.00_precut#2 --- ``` IV-178 Schedule Adherence values appearing incorrect (flipped) in RMMobile - Flipped the SA logic around to work correctly IV-162 Changed flag to be fleet wide using bit 0x10000000 in setupFlags passed from RMGate ``` RMMobile_Android_v2.10.00_precut#1 --- ``` IV-166 RMMobile: Should be able to install and run RMMobile 2.7.x on Android OS 2.3.4 - Fixed issue where black/blue screen prevents access to RMMobile. ``` RMMobile_Android_v2.9.00_precut#2 --- ``` IV-150 Purge of Non Pertinent messages from the queue (IV-150) - Requires Local device property 'Purge Outbound Messages Before Login.', bit 0x0000010000000000L, to be turned on ``` RMMobile_Android_v2.9.00_precut#1 --- ``` IV-11 Added GPS delta time threshold when the device is not signed-on. ``` RMMobile_Android_v2.8.01_precut#1 --- ``` 96916 FORWARD APPLY: RMMobile Closes When Power Applied/Removed From Samsung Tab Active via Powered Cradle 96886 FORWARD APPLY: Local setting for specifying radius yards for all stops is not properly obeyed for auto arrive/depart analysis. ``` RMMobile_Android_v2.8.00 --- ``` - InboundMessageHandler checks for a null MUW object before updating the MUW object; it will now notify you if it's updating the MUW object or else it will tell you the object is null. - Updated ManifestPerformanceInfo log, before printing it checks if muwKindSF[i] is null or empty. - Fixed "**ERROR** Parsing ManifestPerformance section" log issue; muwKind and muwID values are verified (to be non-empty strings) before attempting to parse. - After a remote logout, another logoff message is no longer sent on application exit - Added local device configuration bit that enables Lock Screen to a default threshold of 20 mp/h or km/h 96137 File debug configuration properties did not match configuration properties seen on console (logcat) - RMMobile log files now match what is seen in console. 96138 FORWARD APPLY: Allowed to return from break regardless of error 95133 RMMobile should allow saving GPS data to CSV file - Made it so that you cannot save device settings if both "Record GPS hits to file" and "Read GPS hits from file" settings are on at the same time 96084 FORWARD APPLY: RMMobile > containers deadlock error - Same error where components were already contained in container but for the left side of the screen (where the buttons and small clock at the lower left reside); button components are now removed properly. - Removed the function that causes deadlock. There's no need to remove the buttons, we will just set them to invisible if they are not being used. 96041 FORWARD APPLY: [GA_GRTA] RMMobile Usability > Create new TAB screen for Fixed Route with improved layout, colors, and data presentation - Fixed a linking issue with the break button: break button would not return you to the HomeTab (WhatsNextScreen) upon canceling request. 96002 FORWARD APPLY: "Perform" button should not be present in "what's next" - Fixed NumberFormatException error that appears in the log when perform/action button is pressed. 95971 Unable to configure new device if encryption is enabled - Added an encryption field to the server settings dialog 96429 FORWARD APPLY: When a trip is completed on tablet, changes to trip in dispatch get sent to tablet. - Updated MUW_RecordManager so that it no longer notifies the user about rejected changes and instead sends a rejection message via the ManifestResponseMessage 96450 FORWARD APPLY: RMMobile > Perform Manifest in Order Not Preventing User From Performing in Order - Updated ManifestActionButton and ManifestPane so that it wouldn't proceed to the next pane if force in order is enabled 96449 FORWARD APPLY: Action button checks if current tab is Home tab (What's Next) when What's Next tab bit is off. - Fixed issue where Home tab (what's next) screen would display after action/perform when tab bit for Home tab (what's next) wasn't enabled. 96498 FORWARD APPLY: RMMobile "Vehicle In Motion" Screen Locks And Will Not Turn Off - Fixed issue with alert dialog showing a previously displayed message labeled with a queue index of -1 which displayed on screen as "?" - AlertController will now look for that outlier, remove it, and display the next alert in queue automatically. - Improved logging information for Alert messages. - VIMA lock screen will now disappear as intended after adding/deleting trips before manifest loads. - Resolves an issue where alert would display on top of lock screen (after adding/deleting a trip from manifest while trips are being updated in RMMobile); this causes the lock screen to stay visible until unlocked again by reaching the threshold and slowing down again. - Instead of waiting 100ms, we wait 500ms to display alerts. - Fixed issue where popup was not appearing from dispatch. - Improved logging and removed possible culprit code where alerts were getting displayed after lock screen is not visible. - Fixed issue where 2nd alert message would show before first alert message after VIMA went away. 96602 FORWARD APPLY: RMMobile > ETA table in legacy VIMA showing ellipses for "sched" time and "ETA" time (see 96560) - Ellipses is caused by the data being too long, in width, to display in the column; increased the width (spacing) of the first two columns in the ETA table to prevent ellipses from showing. 96759 FORWARD APPLY: RMMobile: Display of "Break" button should be optional via configuration (see 96190) 96797 FORWARD APPLY: RMMobile > Retrieving blank RMMobile logs 96802 FORWARD APPLY: RMMobile > SA Value wrong on RMMobile "Whats next?" Screen. (see 96716) ``` RMMobile_Android_v2.8.00_precut#8 --- ``` + For rmp 1.17, DM#92128, 94560, 94033, 95838 need RMGate 6.4.17_precut#6+ in order to use flagbits. - FORWARD APPLY: Changed password file from "password" in the RMMobile folder to "rmconfig.psw" in the rmconfig folder 96018 FORWARD APPLY: CUBIC - Recreate or correct dialog to guide the user into fallback mode - Changed reasonForFailure to be a memory variable - Corrected condition to enable fallback mode 96022 FORWARD APPLY: RMMobile work> invent functionality to allow dispatcher to remotely log a driver into RMMobile - Added PIN encryption type to LoginRequestInfo, LoginTask and the HoneyDOTask (remote login task) - Fixed the HoneyDOTask to parse the HoneyDO message properly - Added parameter to HoneyDOTask to determine if it is a sign in or sign off - Changed remote logout to return to the LoginPane 96024 FORWARD APPLY: RMFM - Add Stop Number/Count Info For Route Stops and Work Orders - Added RemainingFleetStopsLabel and RemainingWorkOrdersLabel to the status bar 96027 FORWARD APPLY: Display status bar labels received from RMGate - Introduced status bar bits to LogonResponseInfo - Updated status bar to be dependent on status bar bits - Changed LogonResponseInfo to handle the status bar labels bit (a hexadecimal value) 96030 FORWARD APPLY: RMMobile - Display time and stop points on driver manifest 96040 FORWARD APPLY: Exiting prompt from Fallback misspelled as "Failback" 96032 FORWARD APPLY: Odometer is validated upon login - Threshold value set from rmgate property "PHONES.device.gateway.config.rmp.odometer.validation.threshold" saves the odometer on logoff (threshold is used as a range the user's odometer can be when the odometer is validated). Example: If the threshold is 5 and the saved odometer is 20, entered odometer can be between 15 and 25. - If the odometer value is not within a 10 mile range OR an inavlid odometer is enetered, a popup will appear asking the user to re-enter the odometer value. - The odometer will automatically save upon force close, log off, or when the application is in the background. - per rmp 1.17, field 22 of login response (section) from rmgate identifies if odometer needs to be permanently stored on logoff and needs to be validated by the threshold defined in the field on the next login. 96033 FORWARD APPLY: VIMA Screen improved layout, colors, and data presentation - Refer to Document: RMMobile GRTA Driver Experience Proposal - VIMA(DM#94033) V1.1 - VIMA Lock Screen for Next Stop now updated to show the next stop on fixed route - NextStop bit (0X00000200) in LogonResponseInfo must be "on" in order for this LockScreen to be activated (configured from "PHONES.device.gateway.config.rmp.tabs.to.show" in rmgate properties). - Fixed bug where legacy VIMA screen was displayed even if the "What's Next" tab bit is on. 96041 FORWARD APPLY: [GA_GRTA] RMMobile Usability > Create new TAB screen for Fixed Route with improved layout, colors, and data presentation - Refer to Document: RMMobile GRTA Driver Experience Proposal - TABS(DM#94560) V1.1 - Refer to Document: RMMobile GRTA Driver Experience Proposal - TABS(DM#94560) V1.2 - When the "enabled tabs" in loginresponse from rmgate includes "NextStop" bit which is(0X00000200) + "Home" tab, which is the what's next screen is displayed. + When "NextStop" bit which is(0X00000200) is ON and "Mailbox" bit 0x020 is also ON then it will result in a tab which is a hybrid between (legacy) mailbox and sendmsg tabs, called "Message". User can switch to the "mailbox" screen by clicking the mailbox button in the message tab and back again by clicking the "canned" message button. - Added color to schedule adherence based off of SA status. Black background with white text if ahead of schedule, and White background with black text behind or on time. - Removed unnecessary rebuilding of left button pane and explicitly "removingall" in build of centralpane, which fixed issue of displaying nextstop-info stacked on top of previous. 96085 FORWARD APPLY: Display only time points in VIMA and "What'Next screen/tab". (rmgate:95243) - Properly updating data displayed. - Proper coloring of SA and ETA. - Schedule Adherence value as sent from rmgate was incorrectly handled in milliseconds instead of seconds. - Thresholds were introduced incorrectly indicating that vehicle is on time even if the SA value is 5 minutes behind or 1 minute ahead. Corrected the behavior by not introducing local thresholds. If it's negative the vehicle is behind, if it's positive the vehicle is ahead. - Schedule Adherence is now formatted per the doc "RMMobile GRTA Driver Experience Proposal - TABS(DM#94560) V1.2" - per rmp1.17, field 23 of login response (section) from rmgate identifies "whats next/vima control" bits. basically identifying the manifest items that need to be displayed on the What's Next and Home screens. 96002 FORWARD APPLY: "Perform" button should not be present in "what's next" - Introduced MUW flag MUWBHV_WHATSNEXT_ACTION_BUTTON_HIDDEN= 0x01000000 and MUWBHV_MANIFEST_ACTION_BUTTON_HIDDEN= 0x02000000 to hide action/perform buttons from What's Next and Manifest screens respectively; by default the perform/action button(s) is present. 96042 FORWARD APPLY: Legacy VIMA screen would not show next stop - Corrected the logic to display next stop address if it is configured to do so even if ETA is not present. - If ETA isn't available, only scheduled time and next stop will display. 95472 {RMMobile} Ability to send freehand text messages to Dispatching - Created TextMessageDialog in order to send text messages from the canned message pane - Changed sending canned message to switch to mailbox tab rather than manifest tab 96084 FORWARD APPLY: RMMobile > containers deadlock error - What's Next (Home Tab) and new VIMA Screen will no longer sends a popup stating that the component is already contained in another container; components are now removed properly from container and added to new screen. 96088 FORWARD APPLY: WhatsNext Home tab - Unable to read "button disable" flag because manifest is empty - Home tab will check if there is a manifest list before making a perform action button. 95765 Fatal exception occurs when the PTT service is called after the app closes - Fixed RMMobile so service connection doesn't leak on destroy ``` RMMobile_Android_v2.8.00_precut#7 --- ``` 95133 RMMobile should allow saving GPS data to CSV file - Added a device setting in order to read GPS data from a CSV file - see "GPS Emulation" section of readme for more details ``` RMMobile_Android_v2.8.00_precut#6 --- ``` 95750 [FORWARD APPLY] Vehicle field not showing up in LoginPane anymore 95765 Fatal exception occurs when the PTT service is called after the app closes 95784 [FORWARD APPLY] RMMobile no longer compatible with versions below Android 4.0 - Removed NFC stuff from the manifest - RMMobile can properly run on Android 2.3.3+ 95785 Disable RTT and PRTT buttons during PTT call 95133 RMMobile should allow saving GPS data to CSV file - Added directory for GPS logs - Updated formatting of CSV file by adding column headers and fixing format of the timestamp 95859 Need notification that PRTT and RTT messages were indeed sent - Added notification for when RTT and PRTT messages are sent - Changed RTT and PRTT messages to be "immediate send" canned messages - Created ToastDialog to act as our version of an Android Toast - Converted PTTTimeoutTask to be the more generic DialogTimeoutTask ``` RMMobile_Android_v2.8.00_precut#5 --- ``` - Added odometer to the status bar 95545 Integrate rmmobile with PTT service and implement rm PTT call management protocol. - Show PTT buttons only when call is established - Fixed the issue with the notification stopping older devices from activating - Fixed issue with RMMobile "activating" an already activated ESChat service - Fixed issue with two images showing in PTT buttons on bigger displays - Made the Talk/Hangup Buttons larger - Introduced PTTDialog (YesNoDialog with Answer/Reject buttons) - Stopped showing PTT messages in the mailbox - Changed wording for incoming PTT calls - Fixed the PTT button mechanics so it can't change when dispatch has the floor - PTTPane is brought to focus when call is initiated - Changed notification to show in status bar - Added PTT notification icons - Changed InboundMessageHandler to use "vid" for call and "user" for display 95604 RMMobile > "Password file too old" prompt preventing successful user login - Changed the "password too old" message to display only if the PasswordTask is not a background process - Fixed bug that stopped login error messages from displaying - Stopped using AlertController for password-related messages 94538 RMMobile work> invent functionality to allow dispatcher to remotely log a driver into RMMobile (related 94320, 94539) - Updated the InboundMessageHandler to handle HoneyDO Signin and Signoff requests - Introduced HoneyDOTask to allow remote logins and logouts ``` RMMobile_Android_v2.8.00_precut#4 --- ``` 95545 Integrate rmmobile with PTT service and implement rm PTT call management protocol. - Created an activation task that prompts the user upon failed or successful activation - Minor fixes to make the user more aware of when the PTT service is not activated - Updated readme to include detailed PTT Activation/Usage Instructions ``` RMMobile_Android_v2.8.00_precut#3 --- ``` 95545 Integrate rmmobile with PTT service and implement rm PTT call management protocol. - Introduced icons for different states of PTT button and hang up button. - Introduced PTT tab once the appropriate tab bit (0x400) is on in RMGate (requires at least 6.4.16) has RTT button to request to talk, PRTT button to priority request to talk, Hang Up button to end call, PTT button to talk to dispatch, and displays updates for contact name and floor occupant Note: the RTT button and PRTT buttons must be set using the logon responses (0x00010000 and 0x00020000 respectively) ``` RMMobile_Android_v2.8.00_precut#2 --- ``` 95545 Integrate rmmobile with PTT service and implement rm PTT call management protocol. - Bound the PTT service to the RMMobile activity per the documentation provided - PTT service needs to be activated; introduced local PTT device property (0x0000000200000000L); when on, PTT activation code needs to be entered in ConfigPane ``` RMMobile_Android_v2.7.04 --- ``` 95578 "coursemadegood" attribute is not by rmmobile GPS collector. - rmwagent does set "coursemadegood" attribute and TargetAnalyzer, which is in "shared" makes use of it when ever there are targets that have entry or exit angles associated with them. rmmobile never used to set the "coursemadegood" attribute, and only sets the "direction", so when targets are downloaded to rmmobile, the ones that have angle associated would never get fired properly. ``` RMMobile_Android_v2.7.03 --- ``` 95537 Incorporate fixes in "Target analyzing algo" covered under DM#95508 and DM#95509. - This DM is for rmmobile to include DMs (related to Targets analyzing algo) fixed in rmwagent v2.0.01, which are: DM#95508 Target isn't marked as "really entered", if there are no commands on entry and neither an entry angle is provided. + In such a case, if there were only commands on exit, they won't fire; the behavior is now fixed. DM#95509 Targets can fire multiple times. + If GPS hits are observed to be alternting "within" and "outside" of radius of target, then the target may fire multiple times. The behavior is fixed by marking the target as "fired" after it's fired once. And the status isn't cleared so target can't be fired again, unless device is atleast 3 times the radius of particular target. 95536 No Show RMMobile Flow Incorrectly takes you to Fare Collection Screen - When legacy fare collection mode is on, then there was no check in departure screen, if fare/attendants/service anumals should be displayed based on if it's a No Show or not. ``` RMMobile_Android_v2.7.02 --- ``` Removed precut designation. ``` RMMobile_Android_v2.7.02_precut#14 --- ``` 95423 Fallback mode should not be allowed in certain situations. - When login task fails due to reasons other than 'out of coverage' issues, like invalid username/password/device etc. then user shouldn't be prompted with the option of "fallback" mode. 95204 Implement improved auto-arrive and auto-depart algo in rmmobile. - Auto depart messages were sent with the incorrect (canned messages) messages code. - Improved logging. ``` RMMobile_Android_v2.7.02_precut#13 --- ``` 95204 Implement improved auto-arrive and auto-depart algo in rmmobile. - There was a bug in precut#12 where local radius of stop wasn't properly set when the local auto arrive/depart property is on. ``` RMMobile_Android_v2.7.02_precut#12 --- ``` 80853 RMMobile should have admin login feature added to Configuration settings (DM#94700 - RMGate) - Display errors properly on top of the server/admin dialog. 95323 RMMobile will not clear the stops - Manifest updates were from rmgate were not making to the local muw record manager, due to possible fix of 95191. The fix is still in place(i.e. not "adding" to record store, only insterting it from InboundMessageHandler) but the "insert" method is now improved to accept the muw change and update the manifest appropriately. 95204 Implement improved auto-arrive and auto-depart algo in rmmobile. - Local device property 0x0000001000000000 can now be turned on/off through radio button. In addition, if the property is ON, then "radius" of the stops for auto arrival/departure can also be specified be locally. As rmgate doesn't send radius if the "auto-arrive/depart" functionality is fleet-wide off. ``` RMMobile_Android_v2.7.02_precut#11 --- ``` - removed 'wasHomePressed' references from pause/start app behavior. there is no need for it and it never worked reliably anyhow. - removed some commented code in the 'anchor' package which is no longer relevant. - removed some Android specifics from 'LWUITActivity.java' and placed them in its subclass 'RMMobileActivity.java' since the purpose of that subclass is to act as an abstraction layer which should contain platform specifics. pieces moved to subclass: + uncaught exception handler class and instantiation in '#onCreate' + handling of NFC discovery/presence in onResume + setting Android screen orientation. - removed all references to android.graphics.Color - fixed an issue that would cause alerts to disappear when the screen changed. alerts now re-appear each time a new pane is shown so that they may be dismissed in the case that another modal dialog takes control of the screen. (this happens when the user is unable to connect, the password/admin dialog pops up, and upon successfully entering the config screen, the alerts disappear and reappear whenever another alert is shown (such as a manifest update)). 95293 Logoff Button does not send logoff message (when RMMobile is Home Screen) - logoff message is now sent whether or not RMMobile is the home screen - post inspection now displays on 'logoff' 95216 All dialogs should belong to a singular "alert queue" to be hidden/shown on VIMA enable/disable - fixed a bug where some alerts would be shown multiple times. 95074 RMMobile canned messages are offset by (1) when selecting - updated the Motion so when the screen is initialized the destination value is 0 (no offset) 95315 RMMobile does not generate popup message for day-of WO additions and requires user to 'Accept' twice - the problem was with the conditional in the 'addToTail' method in the alert controller. the logic has been fixed. 95074 RMMobile canned messages are offset by (1) when selecting - updated the Motion so when the screen is initialized the destination value is 0 (no offset) 95315 RMMobile does not generate popup message for day-of WO additions and requires user to 'Accept' twice - the problem was with the conditional in the 'addToTail' method in the alert controller. the logic has been fixed. - all alerts are now added to the tail of the alert queue. 95204 Implement improved auto-arrive and auto-depart algo in rmmobile. - Aside from the improvement of auto-arrive/depart mechanism, to indicate the vehicle/device is 'definitely in the circle, flag 0x02 is introduced in ManifestUnitOfWorkEvent section. To indicate the vehicle/device is 'definitely outside the circle' flag 0x04 is introduced. And if neither of the flags are ON, then it means we don't know the 'right now' GPS, even though gps info section may still be filled with the last known gps (within the confidence interval). - Introduced local bit 0x0000001000000000, to turn ON auto arrive/depart locally instead of fleet wide as login response from rmgate. 93853 RMwAgent (to fix its "wait before executing command" parm) in relation to new APC count method (rel. DM#93850, 93852) Notification to rmgate of entry/exit of the target however happens regardless of if the peripheral-command was completed successfully. ``` RMMobile_Android_v2.7.02_precut#10 --- ``` - removed ticker animation from color selection dialog - fixed a bug that would cause previously dismissed alert dialogs to popup again after VIMA is disabled. - removed some unused RMMobile references from LWUIT source. 92122 Provide ability to track vehicle location prior to RMMobile login - prelogin GPS reporting now depends on a bit sent from RMGate in the logon flags. RMMobile will only report GPS before logon if this bit is set, and a previous successful logon has occurred. - changed logon response info flag to 0x1000 per Dave. presence of this bit in the previous logon response enables sending GPS reports before user logs in. 94033 RMMobile Usability > Create new VIMA screen for Fixed Route with improved layout, colors and data presentation - changed the way that some font scaling is calculated. this will only affect the new clock in the locked screen (VIMA) with FR enhancements. see Font#createFontSize and Font#getFontScaleFactor(float). 95216 All dialogs should belong to a singular "alert queue" to be hidden/shown on VIMA enable/disable 95263 [FWD_APPLY] rmmobile becomes non-responsive when fallback mode is not an option ``` RMMobile_Android_v2.7.02_precut#9 --- ``` 95078 Stop type icons are missing from manifest - Added icons for break start and break end. - Generic icons for unknown muw kinds. And can handle no icon id. 95216 All dialogs should belong to a singular "alert queue" to be hidden/shown on VIMA enable/disable 95218 RMMobile needs human-readable text for MUW_kind_15 popup messages - Update of unknown muwkinds to rmmobile are presented with a popup that says "stop" instead of "muw_kind_x" - Introduced understanding of muwkind 15: fleet zone stop... 95191 RMMobile sometimes freezes when removing split run stops from manifest - After the manifest list is updated, setting the selected index to 0 seems to be the culprit. For the fix, for now we are keeping the same reference of manifestlist enclosing in try catch. ``` RMMobile_Android_v2.7.02_precut#8 --- ``` 95191 RMMobile sometimes freezes when removing split run stops from manifest - color actions (ie, accepting manifest changes) has changed from a platform specific interface to LWUIT interface, now avoiding race conditions between Android UI and LWUIT. ``` RMMobile_Android_v2.7.02_precut#7 --- ``` - made PasswordTask run in the background if configdata is present - fixed configdata so that it properly serialized ttl and retry limit 92858 ETA not displaying correctly in manifest.layout for FR - FR should now be able to take advantage of manifest layout in rmgate.properties. - ETA display should work as designed. note that ETA will not display until valid ETA data exists... 92122 Provide ability to track vehicle location prior to RMMobile login - device should now send in GPS reports before the device is logged on using the gps reporting interval set in a previous logon response. if there was no prior logon response, then the reporting thread is started at logon. 95078 Stop type icons are missing from manifest - some icons for fleet were missing in the latest precut. they have been re-added. 95081 RMMobile does not allow driver to accept multiple manifest additions/removals - "remove contiguous" and "remove all" colors should now work as designed. 95088 RMMobile does not send responses to messages from dispatching - popup messages should now send responses back as they did before. 95095 RMMoible 'Button' data type clears values before sending when using '80' modifier flag 95133 RMMobile should allow saving GPS data to CSV file 93451 Update 'force in order' to allow the ability to ask driver 'are you sure?' when out of order [stop]completion is generated - Consider Alternatively - Create an option for drivers to "undo" erroneous completions once recognized. (introduces some risk) - When a driver is completing stops on the tablet and selects a future stop to complete the RMMobile app should provide a prompt to ask the driver if they really want to complete a stop that is scheduled to occur in the future. 94684 Prompt driver for "reasons" why one want to do something out of order/ordinary - For example, if performing trips out of order, driver should be presented with prompts why he/she is doing so. - Also if the driver wants to un-arrive, or if he arrived outside the geo-circle of stop, he may be presented with a list of reasons. ``` RMMobile_Android_v2.7.02_precut#6 --- ``` - changed DeparturePane summary text display. there was an issue where prompts without choices were causing a null pointer exception when displaying summary text. 95050 RMMobile does not honor bit '80' modifier flag to clear all prompts after button press - there was a logic issue that made this modifier mutually exclusive to other actions. 95035 Logoff message is sent with the device time and not the "synched-time" - logoff message now uses synched time. ``` RMMobile_Android_v2.7.02_precut#5 --- ``` - turned off the showing of grid lines when prompts are built. - reduced code needed to find number of columns when laying out grid. 80853 RMMobile should have admin login feature added to Configuration settings (DM#94700 - RMGate) - There should be local cache file which holds an encrypted password - The creation of this file should be in response to RMGate handing RMMobile a password - The file should include a hashing-together-with operation which makes the saved value (only good on that particular phone) - If there is no cached password file stored yet, prompt the user for an RMGate IP/port to which you will connect and ask for current encrypted password - User must be in coverage for this to work and if not, should get appropriate error messages - After receiving an RMGate answer for password request, the password value is munged in code and the cache file is written - Once you have the cache file, prompt the user to enter password, then encrypt and munge so that you can direct-compare against the encrypted/munged password from the cache file (NEVER DECRYPT) - If passwords match, you let the user into the desired page, if not you tell him and allow retry - If he tries but fails 3 times in a row, you delete the cache file and he must connect back to RMGate ``` RMMobile_Android_v2.7.02_precut#4 --- ``` - fixed an issue which caused an error to be displayed when RMGate connectivity is detected in fallback mode. - inbound handler is now interrupted and stopped properly when logging out of fallback mode. - inbound listener no longer restarts itself if the thread is being killed. 94631 Fleet Manifest > Display hot accounts on the manifest - Reworked how the muwkind icons are displayed on the manifest. - each MUWKIND_??? value represents two default icons (but the two icon "pictures" may in fact be the same) for use by that MUW: + one with "its number" as iconId, desigating the "part 1" (pickup, start) half, and + another with "its number plus 1000" as iconId, desigating the "part 2" (dropoff, end) half. - if the MUW in question only has one half to it, then it still follows the "two default icondId values" rule, but only one gets used... for example, an FRSTOP (muwKind 4) has only the "second half" by its muwBehavior bits, so although it would have used iconId 4 as its "first half", since it doesn't have a "first half", that icon is simply not used... in this case, only iconId 1004 is used... as its "second half". - the two muwKind-based default iconId values of a MUW are only used if that MUW does not specify first-half and/or second-half icons by specifying MSGSECT_MUWDATA_FIELDNUM_STOP1_ICON_OVERRIDE and/or MSGSECT_MUWDATA_FIELDNUM_STOP2_ICON_OVERRIDE. - also avaialble for use as MSGSECT_MUWDATA_FIELDNUM_STOP1_ICON_OVERRIDE and/or MSGSECT_MUWDATA_FIELDNUM_STOP2_ICON_OVERRIDE are assorted well-defined MUWICON_??? iconId values in range 2000 to 2999. 94894 LogonResponseStoreHelper.setPreviousResponse stops InboundMessageHandler from running on login - added try catch for issue where inbound message handler dies if a previous logon response is not loaded. 94870 RMMobile pre-inspection screen disappears if VIM screen is enabled/disabled - pre-inspection screen comes back after VIMA disables if it was the previous screen being viewed ``` RMMobile_Android_v2.7.02_precut#3 --- ``` 93734 Targets > Port RMwAgent target functionality for Fixed Route into RMMobile (DM# 94761 - RMGate) - TargetAnalyzer now sends peristat messages with the proper Header section, i.e. if targets are being downloaded and analyzed either on rmmobile or rmwagent. ``` RMMobile_Android_v2.7.02_precut#2 --- ``` - added more info to beginning of log file regarding system configuration and software version - made some aesthetic changes to VIMA for certain options - added loads of comments to the process of prompts. some slight changes were made to the way that prompt tables are built. - Implements rmp v1.16 (DM#93734 and 92524) and require rmgate v6.4.09+. 93733 RMMobile Usability > Reduce keypresses needed for performing fixed route stop (Project 40) - removed "group arrive/sanity check" screen for fixed route stops 94870 RMMobile pre-inspection screen disappears if VIM screen is enabled/disabled - pre-inspection screen comes back after VIMA disables if it was the previous screen being viewed 94685 rmmobile should start when the device is turned on (related DM#92122). - RMMobile is now capable of becoming the default Android "home screen" - Please review the "Home Screen Setup (Android)" section in readme before installing this version for instructions on setting the home screen 93734 Targets > Port RMwAgent target functionality for Fixed Route into RMMobile (DM# 94761 - RMGate) - Arrive/Depart targets result in proper peristat messages. All peripheral command related targets result in rmmobiie logging errors that peripherals aren't supported by rmmobile yet. 92524 PTT > Provide Push-to-talk feature in rmmobile. (related 92820 - APP 92525 - RMGate) - Created PTTAudioThread and PTTMessage to handle push to talk audio - Updated MediaManager to work with the PTTAudioThread - Updated inbound and outbound message handlers to support PTT messages 94033 RMMobile Usability > Create new VIMA screen for Fixed Route with improved layout, colors and data presentation (Project 40) ``` RMMobile_Android_v2.7.02_precut#1 --- ``` 94685 rmmobile should start when the device is turned on 94686 User shouldn't be able to 'exit' rmmobile, can only 'log off' 94715 Remove ambiguous error messages. Add error code to messages (DM#93809) and provide link to explanation. - login request failure is now properly logged. - failure to receive login response now properly logged. - all failure codes are numbered and localized. ``` RMMobile_Android_v2.7.01_precut#13 --- ``` 95129 rmmobile becomes non-responsive when fallback mode is not an option - removed echoing fallback log lines in echo debug statements within the outbound sender. ``` RMMobile_Android_v2.7.01_precut#12 --- ``` - fixed an issue which caused an error to be displayed when RMGate connectivity is detected in fallback mode. - inbound handler is now interrupted and stopped properly when logging out of fallback mode. - inbound listener no longer restarts itself if the thread is being killed. 94894 LogonResponseStoreHelper.setPreviousResponse stops InboundMessageHandler from running on login - added try catch for issue where inbound message handler dies if a previous logon response is not loaded. 94870 RMMobile pre-inspection screen disappears if VIM screen is enabled/disabled - pre-inspection screen comes back after VIMA disables if it was the previous screen being viewed ``` RMMobile_Android_v2.7.01_precut#11 --- ``` - added more logging of basic information when the app is loaded - uncommented lines in InboundMessageListener which will allow the listener and/or handler to restart itself in the event of some mishap. 94314 RMMobile should not hide popup notifications after VIM screen is enabled/disabled - this was a problem with the current alert being invalid. for any situation where the current alert is incorrect, we instead display the first alert. 94485 RMMobile display of manifest is delayed if inspection is performed/skipped too quickly - this was an issue in the inbound message handler where an exception was not being caught. 94841 RMMobile VIM screen does not disappear after acknowledging popup message - this had to do with a weird race condition between displaying the dialogs and showing the root Form. - added a short sleep and synchronized display of dialogs on root Form object to avoid race condition with showing the root Form. ``` RMMobile_Android_v2.7.01_precut#10 --- ``` - login request failure is now properly logged. - failure to receive login response now properly logged. - all failure codes are numbered and localized. 94644 Cubic 2a > Improve prompt to enter fallback mode - fallback mode is automatically entered when the dialog is accepted asking if the user wants to enter fallback mode. - there should be no issues revolving around message context or other login issues. ``` RMMobile_Android_v2.7.01_precut#9 --- ``` - fixed an issue that caused fallback check thread to stop even if cancel is pressed from connectivity check dialog when coverage is detected again. - fixed an issue that caused fallback check thread to continue after next login. - fixed an issue that caused the manifest to disappear after the VIMA screen is disabled. 94536 [FWD_APPLY] QRScan mode check causes NullPointerException on Manifest loading, CannedMessages do not load - added a check both at startup and when config data is loaded from RMGate and check for null prompts list. 94360 [FWD_APPLY] Vehicle in Motion Screen Hides Done Button on Fare Screen - fixed an error that caused various exceptions when rebuilding root form after VIMA screen is disabled. 94513 Fare Clicker takes 5-7 seconds to display after button press to call it - initial lag is significantly reduced. - scroll lag issue has been solved. ``` RMMobile_Android_v2.7.01_precut#8 --- ``` 94347 [FWD_APPLY] RMFM - RMMobile does not properly hide VIM screen after period of time 94359 [FWD_APPLY] RMMobile should not hide popup notifications after VIM screen is enabled/disabled 94360 [FWD_APPLY] Vehicle in Motion Screen Hides Done Button on Fare Screen 94507 Should not be able to "perform" a stop that is not "opted-in" 94514 Fare Clicker Summary page no longer has "back" button 94513 Fare Clicker takes 5-7 seconds to display after button press to call it - this has NOT yet been fixed. still looking into this. ``` RMMobile_Android_v2.7.01_precut#7 --- ``` 94342 [FWD_APPLY] Odometer does not show for FR stops 92280 RMMobile - Support the ability to allow driver to select and 'add' a 'request only' stops re: DM 92001 - 'on demand' stops - fixed an issue that made the screen unusable after accepting a change. ``` RMMobile_Android_v2.7.01_precut#6 --- ``` 92280 RMMobile - Support the ability to allow driver to select and 'add' a 'request only' stops re: DM 92001 - 'on demand' stops - fixed an issue which caused changes to optional stops from dispatch to be rejected by tablet. 94309 [FWD_APPLY] RMMobile needs to send prompt data with NON_CHAR instead of choice-index "0" - there was an oversight wherein when the value is retrieved it would automatically replace whatever the prompt value was with the value of the field after it was set to NON_CHAR. this issue is specific to certain types of prompts: Money, PickList, PickButtons, Number, Alpha. ``` RMMobile_Android_v2.7.01_precut#5 --- ``` 94247 [FWD_APPLY] NoShow fails if debug category "flow" is disabled in debug settings 94248 [FWD_APPLY] "Defer" button on payment screen has no effect 94124 Add understanding of muw field #57, trip comment extract (TCX) - Fixed backward compatibility with rmgate versions that do no send muw with field 57. - Fixed manifest renderer error when rmgate sends with empty 'trip comment extract (TCX)' field. 92280 RMMobile - Support the ability to allow driver to select and 'add' a'request only' stops re: DM 92001 - 'on demand' stop - Fixed the bug introduced by v2.7.01 precut#4 which broke the No Show logic. 94271 Add understanding of muw field #58, customer internal ID part of rmp v1.15 ``` RMMobile_Android_v2.7.01_precut#4 --- ``` 92280 RMMobile - Support the ability to allow driver to select and 'add' a'request only' stops re: DM 92001 - 'on demand' stop rmmobile updates manifest and prompts properly when dispatch "opts-in" to a stop. All optional stops need to be opted-in either by driver or dispatch before they can be performed. ``` RMMobile_Android_v2.7.01_precut#3 --- ``` 94214 [FWD_APPLY] Pre / Post inspection items are getting sent to RMGate even when 'Skip' is pressed - made some changes after checking spec. NON-CHAR should be used as the answer if a prompt is skipped. 94215 [FWD_APPLY] "Hide Odometer Prompt" device property exhibits incorrect behavior - fixed a slight logic error. 94216 [FWD_APPLY] Demand Response Fare Summary screen shows up when completing G Stop for fixed route - if a single para stop is performed, it is displayed. otherwise it is not. 94217 [FWD_APPLY] NoShow causes RMGate SQL error - no show reason was only being saved to MUW store if there were no other prompts. it always saves now. 94218 [FWD_APPLY] RMFM - RMMobile does not allow 'Skip' of post-inspection - pre / post inspection are now handled properly and buttons should be in the right places. ``` RMMobile_Android_v2.7.01_precut#2 --- ``` Merged changes from v2.7.00 branch (precut#32 and DM#94010 in precut#33). DM# 92280 - RMMobile - Support the ability to allow driver to select and 'add' a'request only' stops re: DM 92001 - 'on demand' stop All the optional stops have background Orange so they can be distinquished from normal stops. Once opted in (either by driver or by dispatch), the color changes light green. Note that a stop opted-in by driver can only be opted out by driver and a stop opted in by dispatch can only be opted by dispatch. ``` RMMobile_Android_v2.7.01_precut#1 --- ``` NOTE: v2.7.01 branched out for OR_YORK(trip planner - zone) and WY_START(snow flake) projects. precut#1 doesn't include changes made in v2.7.00 precut#32. Fixed DM#94124 Add understanding of muw field #57, trip comment extract (TCX) Partially fixed 92280 - RMMobile - Support the ability to allow driver to select and 'add' a 'request only' stops re: DM 92001 - 'on demand' stops, Do not deploy 92280 in field, as some UI elements are not there but it is good enough to send opt-in/out messages from driver/dispatch. ``` RMMobile_Android_v2.7.00 FP --- ``` - removed precut designator ``` RMMobile_Android_v2.7.00_precut#38 --- ``` - fixed an issue that caused fallback check thread to stop if cancel is pressed from connectivity check dialog when coverage is detected again. - fixed an issue which caused normal login to fail after connectivity is detected in fallback mode. - fixed an issue that caused the manifest to disappear after the VIMA screen is enabled. 94528 QRScan mode check causes NullPointerException on Manifest loading, CannedMessages do not load - added a check both at startup and when config data is loaded from RMGate and check for null prompts list. 94082 Vehicle in Motion Screen Hides Done Button on Fare Screen - fixed an error that caused various exceptions when rebuilding root form after VIMA screen is disabled. ``` RMMobile_Android_v2.7.00_precut#37 --- ``` 94136 RMFM - RMMobile does not properly hide VIM screen after period of time 94314 RMMobile should not hide popup notifications after VIM screen is enabled/disabled 94082 Vehicle in Motion Screen Hides Done Button on Fare Screen 94304 RMMobile needs to send prompt data with NON_CHAR instead of choice-index "0" - fixing a ridiculous NullPointerException... 94340 Odometer does not show for FR stops ``` RMMobile_Android_v2.7.00_precut#36 --- ``` - fixed an issue that caused fallback check thread to stop even if cancel is pressed from connectivity 94304 RMMobile needs to send prompt data with NON_CHAR instead of choice-index "0" - there was an oversight wherein when the value is retrieved it would automatically replace whatever the prompt value was with the value of the field after it was set to NON_CHAR. this issue is specific to certain types of prompts: Money, PickList, PickButtons, Number, Alpha. ``` RMMobile_Android_v2.7.00_precut#35 --- ``` 94243 NoShow fails if debug category "flow" is disabled in debug settings 94230 "Defer" button on payment screen has no effect ``` RMMobile_Android_v2.7.00_precut#34 --- ``` precut 34 releasing due to incorrect versioning. ``` RMMobile_Android_v2.7.00_precut#33 --- ``` 94010 Pre / Post inspection items are getting sent to RMGate even when 'Skip' is pressed - made some changes after checking spec. NON-CHAR should be used as the answer if a prompt is skipped. 94193 "Hide Odometer Prompt" device property exhibits incorrect behavior - fixed a slight logic error. 94198 Demand Response Fare Summary screen shows up when completing G Stop for fixed route - if a single para stop is performed, it is displayed. otherwise it is not. 94213 NoShow causes RMGate SQL error - no show reason was only being saved to MUW store if there were no other prompts. it always saves now. 94202 RMFM - RMMobile does not allow 'Skip' of post-inspection - pre / post inspection are now handled properly and buttons should be in the right places. 94086 RMMobile - Run summary report should not be shown to fleet drivers ``` RMMobile_Android_v2.7.00_precut#32 --- ``` 94010 Pre / Post inspection items are getting sent to RMGate even when 'Skip' is pressed 94081 RMMobile - 'Back' button is missing from various screens 94149 RMFM - RMMobile freezes if popup notifications are cleared too quickly - reworked alerting so that only a single dialog is created. - Alerting is now slightly more abstract and there is only one type of AlertDialog. 93814 Enable system logging on app startup 00000 Cubic - problem with "import" statements Fixed DM#94124 Add understanding of muw field #57, trip comment extract (TCX) Partially fixed 92280 - RMMobile - Support the ability to allow driver to select and 'add' a 'request only' stops re: DM 92001 - 'on demand' stops, Do not deploy 92280 in field, as some UI elements are not there but it is good enough to send opt-in/out messages from driver/dispatch. ``` RMMobile_Android_v2.7.00_precut#31 --- ``` 94081 RMMobile - 'Back' button is missing from various screens 93030 DM#93030 CUBIC functionality in rmmobile should be available in offline mode. RMP1.14 implemented, which provides the ability to login to fallback mode when device is out of coverage and can not reach rmgate, iff there was a successful login prior to that and makes use of prompts(app state) that were downloaded in the last login. Once it is detected that device is back in coverage, open to exit fallback and login normally is provided. NOTE: RMwAgent v2.0 precut#15 and RMGate 6.4.04 are required for DM#93030. 94120 Invalid WO# displayed in new work popup window MUW ID makes sense only for MUWKIND_TRIP (para) but it was also being added to all other kinds of MUW. ``` RMMobile_Android_v2.7.00_precut#30 --- ``` abstracted file refresh for DM#94009 93980 RMMobile 2.7.00 pc#29 causing echo debug statements to be sent to RMGate - an excessively overzealous method was causing everything to be logged on all channels. 93975 RMMobile 2.7.00 pc#29 manifest Details button throws a Java error - string resources were improperly formed. 94009 Logs do not show up over MTP via USB until device is rebooted - refreshing the media store so that a device does not have to be rebooted to access logs via USB. ``` RMMobile_Android_v2.7.00_precut#29 --- ``` 92459 NullPointerException error after clicking Navigate on Map screen with no manifest loaded - checked if there was a selected point in the manifest table, if not display error message 93748 FORWARD APPLY: Diag Button from RMMobile 2.5 to 2.7 93471 All MUWKIND getKindString string notifications have been added to ManifestUnitofWorkDO 93133 Fixed NoShow timer to display correct minutes and seconds 93809 Add a publicly visible error code added to all prominent error messages 93888 RMMobile 2.7.00 pc#26 - application freezes when trying to complete stop arrival - DeparturePane was trying to parse an integer from a non-integer String. 91564 Prompting behavior bits for "looping", "keepval" and "optional" do not work - looping, keepval and optional flags should now work as designed. - fixed a bug that would cause looping PICKCHOICE answer types would result in an exception. - added LOOP counter on "Again" button for looping prompts. - fixed a bug wherein the wrong number of zubfields were passed as an answer. 93920 rmmobile 2.7.00 messages from dispatch pop up over VIMA, does not match prior version behavior - should be fixed. new incoming alerts weren't checking if the screen was locked or not. 93931 FORWARD APPLY: RouteMatch 'closing' after 9-11 minutes of no signal on Samsung Tab 4s 93833 RMMobile missing odometer at send screen, which results in blank screen on route start and departing pickup/dropoffs - there was a logic error in ManifestUnitOfWorkDO.promptForOdometer. 94680 Optionally hide the tabs you don't want - fixed a bug that caused the logon response parse to fail if tab field is not present ``` RMMobile_Android_v2.7.00_precut#28_NFC --- ``` - fixed an issue that would cause the entire account balance to be used for AFC para debit account types. - fixed 'IllegalStateException' in multi-fare. DM98382 RMMobile keypad is small and squished together ``` RMMobile_Android_v2.7.00_precut#27_NFC --- ``` this cut includes the NFC enhancements necessary to read cards using the ACS external NFC reader. ``` RMMobile_Android_v2.7.00_precut#26 --- ``` 93373 Fleet Dispatching > Communicate day-of changes for down routes to devices - alerts will now only sound when NOTIFY flag is on, and a dialog is displayed notifying the user of the change. 93471 All MUWKIND getKindString string notifications have been added to ManifestUnitofWorkDO 93133 Fixed NoShow timer to display correct minutes and seconds 93801 Synchronized way ManifestItemDetailsPane and ManifestHistoryItemDetailsPane created text box and details string 93815 Forward applied the activity elements to fix DM#93042 that was added to RMMobile v2.5.02precut#7 ``` RMMobile_Android_v2.7.00_precut#25 --- ``` 94680 Optionally hide the tabs you don't want 93373 Fleet Dispatching > Communicate day-of changes for down routes to devices - alerts will now only sound when NOTIFY flag is on, and a dialog is displayed notifying the user of the change. ``` RMMobile_Android_v2.7.00_precut#24 --- ``` 93582 FORWARD APPLY: RMMobile should provide at least same amount of info about connected Wifi SSID/ip address details... 93393 RMFM - RMMobile freezes when Next/Previous buttons are pressed in stop Detail 93596 RMMOBILE freezes when removing colors after an update. 93319 RMFM - Trim Account Name To Fit Serial Number on Manifest ``` RMMobile_Android_v2.7.00_precut#23 --- ``` 93536 Fleet items on manifest not considered "normal" render state NOTE: Please do note that this release is only to "demo" AFC (automatic fare collection otherwise called as EFP (Electronic Fare Payment)) capabilities for RMMobile. Here is a list of major shortcomings: - Fare-capsule as it gets to routeshout throw the fare-portal is parsed in routeshout and rmmobile only gets the account #. routeshout is to actually transfer the whole fare-capsule to rmmobile over nfc and rmmobile needs to parse the capsule out. - With external reader in place, the reader callback always returns account# "1" for ANY NFC card that is detected. ``` RMMobile_Android_v2.7.00_precut#22 (jumped precut numbers. other cuts were made from NFC demo branch) --- ``` - removed useless "Fire" command from all screens 93092 Manifest line icons should obey muwKind and muwdata fields. - new icons for para pickup and drop off. 93315 Forward Apply: Log indicates inability to procure message context for resend of messages after network inability. 93318 Forward Apply: Fare summary incorrectly displaying $0 93483 ManifestPerformance message causes exception 93482 Log device and debug bits in hex 93474 RMFM - RMMobile does not clear 'Accept' button after accepting day-of WO ``` RMMobile_Android_v2.7.00_precut#19 --- ``` 93821 RMFM - RMMobile does not change font color of 2nd line when manifest item selected 93284 RMFM - Improve RMMobile button layout for "Are you sure?" message prompts ``` RMMobile_Android_v2.7.00_precut#18 --- ``` 93214 Pre-Inspection/Post-Inspection Prompts Reverted to Label Prompts 93179 NoShow needs to be re-implemented (again) into 2.7 - NoShow timer should now be working properly. - NOTE: the timer still has problems with group arrive. if you arrive more than one stop at a time, the timers will "jumble" and all timers will update the same button text. this is mostly a visual issue and shouldn't affect the flow of operation. the timers still expire and you will be able to complete the action once they all finish counting down. this will be fixed in a later cut. - NOTE: NoShow text stays red, even after timers complete. this will be fixed in a later cut. 93103 pre and post inspection prompts show "prompts" in titlebar - pre- and post- inspection screens are now titled appropriately. 93119 Add "are you sure" option to tab# BUTTON prompts - buttons which have this bit enabled will now require confirmation before the action is completed. 93198 Default Fleet Manifest Layout - Current manifest layout should only be obeyed for MUWKIND_TRIP ?0?. - For all other muwkinds, layout should look as follows, i.e. manifest item should display following muw fields (depending on par1 or 2): o Line 1: Common Name o Line 2: City (left justified) Zip (Right justified) Note that this has nothing to do with address of the stop/endpoint; we are just abusing the protocol to display proper/desired stuff on manifest. rmgate never sent anything other than Common Name to rmmobile for muw kinds other than 0, so the above proposed fix although looks goofy but doesn?t break anything. Note that the addrCommonName rmgate sent for non-muwkind-0 was always a made up string based on the kind of muw in question. City and Zip will likelwise be "made up usage"; nothing to do with addresses? but the address fields are "separate per stop1 / stop2" so useful for abuse in this manner. For DMs 93198 and 93119 rmgate 6.4.00 precut#27 is required. ``` RMMobile_Android_v2.7.00_precut#17 --- ``` - fixed an issue that caused the left panel clock to not update. because there is only one left panel clock allowed, multiple left panels were registering with the clock manager. the tab switch listener on the tab screen now listens for which tab is being viewed currently, and registers that panel's clock with the clock manager. - Stop detail now obeys "no detail" flag and "Extra Title" and "Extra Detail" fields of MUW. i.e. everything besides para stop has the "no detail" flag and has "Extra detail" and "extra title" filled in by rmgate which would result in the detail screen appear different than it has before. [this was broken in precut#14 and is working again as of this cut]. 93209 Stops take increasingly long time to complete - selection listeners were triggering excessively. took care to allow them to trigger at more appropriate times in both the manifest and map tab. - there is now only a single instance of manifest pane in the application, which should reduce some slight performance issues. - references to other screens are removed more diligently. 93200 DEVCASE: Change one add one new RMMobile device config option (TAM) - odometer display changes. 93207 Forward Apply: ETA not displaying correctly in manifest.layout for FR (2.7.00) - NOTE: manifest item layouts are somewhat broken. it would appear that FR cannot display custom layouts, while para cannot properly display the default layout.... needs more digging and another case will be entered to cover this. for now, the ETA DOES appear on FR items with a custom layout, but nothing else does. ``` RMMobile_Android_v2.7.00_precut#16 --- ``` - previous cut did not have proper version code. 93144 screen creation causes excessive memory use ``` RMMobile_Android_v2.7.00_precut#15 --- ``` - Android version information for the device is now prepended to all log files. - Added some extra logging about GPS granularity. - manifest now honors "EXTRA_DATA" and "EXTRA_TITLE" if "NO_DETAILS" is enabled. - found exactly tab height, screens will no longer cut off at the bottom. 92912 Forward Apply: $0 payments on deferred payment of a $0 expected pay trip causes SQL error 92911 Forward Apply: driver is able to 'Done' through the fare screen on a $0 expected pay trip even without a $0 fare type 92910 Forward Apply: SQL error when trying to use $0 paytype on $0 expected stops 93142 RMMobile 2.7.00 pc#14 FleetRun start times are pulling end times in the manifest ``` RMMobile_Android_v2.7.00_precut#14 --- ``` 93092 Manifest line icons should obey muwKind and muwdata fields. - Added FR Stop icon and generic Route/(Garage) Pull In and Pull Out icons. ``` RMMobile_Android_v2.7.00_precut#13 --- ``` - Precut#12 deliverable identified itself as precut#11, so now releasing v2.7 precut#13 to indicate proper version. - System Info can now be viewed from Config Screen, so there is no need to Login to view what exact version of app it is. ``` RMMobile_Android_v2.7.00_precut#12 --- ``` - fixed an issue that would cause errors in the manifest item renderer if a single element in the list item was null. 92524 Provide Push-to-talk feature in rmmobile - added ability to record sound to file (dev only). 92761 RMMobile should cater to Fleet operations - RMP v1.12 implementation to cater to Fleet stop/MUW kinds - Straighten "stop type" designation, so now it is based off of MUW kind. - Stop detail now obeys "no detail" flag and "Extra Title" and "Extra Detail" fields of MUW. i.e. everything besides para stop has the "no detail" flag and has "Extra detail" and "extra title" filled in by rmgate which would result in the detail screen appear different than it has before. - ?draw attention to it" for stop/service that driver has never seen before, MUWFLAG_HAS_NEVER_BEEN_PERFORMED = 0x0040, implemented. Background is changed to magenta for a service stop that has never been seen before. - Manifest icons added, mostly for fleet related stops. ``` RMMobile_Android_v2.7.00_precut#11 --- ``` 92646 Change IP input field of configuration to allow IPv6 and port specifiers - fixed justification of config layout to look exactly as before. 89241 Add a "show/hide description" button to debug/device properties screens - fixed capitalization and grammar. 92722 RMMobile needs icons for "stop type" indication on manifest - added images to manifest in place of letters for stop type indicator. 92768 RMMobile 2.7.00 pc#10 rider incriments not honoring text input, only +/- button press - text input on counter type answers now honors both text input and +/- buttons. 92758 RMMobile 2.7.00 pc#10 multifare payment type delete doesn't update screen - delete button now updates screen as it should. ``` RMMobile_Android_v2.7.00_precut#10 --- ``` fixed some minor sizing issues with some text on the multifare screen. fixed an issue in multifare3 which caused wrong prompts to display for pickup depart if "defer" button is pressed. 91358 Forward Apply Electronic Signature Capture from RMMobile 2.5 to 2.7 - NullPointerException was caused by invalid reference in SplitUpMessage.java. this is resolved. 89241 Add a "show/hide description" button to debug/device properties screens - this feature has been added. - found an issue wherein the Font for the UnselectedStyle was being changed by the EDT somewhere. the Font manually assigned to a TextArea was not being used for sizing calculations. Since the UnselectedStyle is somewhat unreliable, I switched to the font of the DisabledStyle for calculating size constraints. it works. 92671 RMmobile 2.7.00 pc#9 multifare payment selection drop-down not displaying correctly - this combo box now appears normally. 92646 Change IP input field of configuration to allow IPv6 and port specifiers - ip entry is now a single entry field - added custom keyboard which accepts alpha-numeric text entry (for entering DNS names) for IP field. 92021 RMMobile 2.7.00 consistent creation of image artifacts in pc#3 - fixed! 92716 No Show request dialog text grammatically incorrect - fixed word replacement. 92479 Break times are that of the device and not the RMMMobile - added a reference to the AppClock and a check for timesync. 91489 Theme sometimes does not load - theme properties were being loaded after the splash screen was shown. this was causing the theme to "hiccup". 92570 Prompt questions are too large and cause issues with custom tab screen layout - disabled the TextArea and it now uses the correct font sizing so that elements line up on the screen as they should. ``` RMMobile_Android_v2.7.00_precut#9 --- ``` 89554 RMMobile should adapt to any DPI 87237 Prompting - fix SKIP function to work as intended (related - 87179) - fixed a bug in LWUIT (Button.java#getStyle()) which allowed disabled buttons to be "pressed". when pressed, the button style changed from 'disabled' to 'pressed'. 'pressed' style is now only used if the button is enabled. 92401 RMMobile - Audible Alerts do not occur when para updates are made - audible alerts were commented out for updates/additions/deletions. this is resolved. 90874 AutoArrive and AutoDepart should be "paratransit only" features - this is resolved. 92632 "use metric units" setting not being honored - the value wasn't properly being checked. this should be working now. ``` RMMobile_Android_v2.7.00_precut#8 --- ``` 92382 Redraw of prompts on prompt update causes artifacts and strange positioning of screen elements - fixed an issue that caused HTMLBOX to print in the top left corner sometimes. 92377 Driver Manifest displays 'expected customer payment ID' instead of 'expected customer payment' - expected payment type should appear when defined as part of the manifest layout rather than the payment type id. - (forward applied fix from 2.5.00) 92335 RMMobile - Audible Alerts doesn't work when messages are received. - audible alerts should now be working as designed. 92307 App freezes after selecting the Details button within the History tab - "details" and "status" are no longer shown unless a valid MUW is selected. 92378 PaymentType ListMessages always fail CRC check. - subfield values were not being sent properly in the login request message. 92020 RMMobile 2.7.00 unused checkbox on all manifest execute screens - checkbox only prints when group arrive selection is allowed. ``` RMMobile_Android_v2.7.00_precut#7 --- ``` 91974 Implement "html" prompt type - fixed an issue that caused prompt screens to only update from PRMANSD messages if they are the currently viewable screen. - fixed bug that caused custom tabs to show blank screen after receiving update ListMessage data post-login. - changed background color of box to a dark blue. 91410 ListMessages should use callbacks and have a proper centralized data model - prompts should appear correct, regardless of whether prompts have been changed recently in RMGate. 91555 Device and Debug properties screens need to draw without using prompts structure - this case was failed back due to the 'bit' values not being printed next to each item as in the previous version. this has been resolved. 91936 Implement "blank" prompt type - blank answers now send appropriate data back in prompt answer messages. 92205 pre-inspection prompts screen shows prompts from previous login - fixed an issue that caused the update to not work sometimes. 87237 Prompting - fix SKIP function to work as intended (related - 87179) - added 'skip' button to prompts that are optional iff all prompts on the same page are optional. ``` RMMobile_Android_v2.7.00_precut#6 --- ``` 86538 RMMobile manifest refresh prevents use of input prompts (i.e. fare clicker) (DM#86452 similar) - "Updating Manifest" spinner should now only appear if the manifest is in view. prompts should not be interrupted. 92205 pre-inspection prompts screen shows prompts from previous login - pre-inspection screen now displays the latest pre-inspection prompts - fixed an issue wherein changing prompt definitions was not recognized on the subsequent login 91974 Implement "html" prompt type - fixed an issue where content in the HTMLBOX did not properly wrap. - added scrolling capability to HTMLBOX within its defined boundaries. - fixed an issue that cause HTMLBOX to "truncate" to the right when it should not. - fixed more sizing issues with HTMLBOX type. - added border around html component. - fixed a spanning issue that caused any HTMLBOX elements to span too much. - added more logging. - reduced number of refreshes made to the screen when prompt items are updated. - changed color of background for HTMLBOX prompts. 92105 RMMobile 2.70.00 PC#3 VIMA screen inacurate - VIMA screen now has a somewhat new look. should be operating as designed now. ``` RMMobile_Android_v2.7.00_precut#5 --- ``` fixes: 91993 "GPS Enable" prompt dialog not working - the prompt dialog now operates the same as it did in 2.5.00. 92205 pre-inspection prompts screen shows prompts from previous login - pre-inspection screen now displays the latest pre-inspection prompts - fixed an issue wherein changing prompt definitions was not recognized on the subsequent login 91974 Implement "html" prompt type - fixed positioning of HTMLBOX. ``` RMMobile_Android_v2.7.00_precut#4 --- ``` fixes: 92103 Forward Apply Wifi Off Login Hangs (91502) Fix - Forward applied to cancel a login attempt after 2 * Retries * TTL seconds with a reminder to turn on connection 92018 having severe lag issues in application - 1 second sleep on VIMA screen causes the gps handling method to take more time than the time to the next GPS hit. Makes it feel unresponsive and eventually crash. - This has been removed, and VIMA screen re-enabled. 91408 Prompts need to have a more independent and solid structure - "across ok" feature (behavior bit 0x8) now works as it should. - fixed a bug in this implementation wherein non-"across ok" rows were placed horizontally when balancing the grid. - fixed a bug wherein prompt panes without a left container used the incorrect display width to calculate across ok grid - fixed a bug that caused failed logins when prompt data does not exist. 91490 Group arrive currently does not work - group arrive should now work the same as it did in previous versions of RMMobile. 91974 Implement "html" prompt type - implemented HTML prompt/answer type, which is merely a display of HTML data in a prompt format. - implemented SAPRES updates for altering prompt answers. - made changes for "PromptAnswerUpdateMessage" for RMP 1.11. - fixed an issue where html prompt list items were accessing the wrong indices for the data they contained. - fixed positioning of HTMLBOX. 91993 "GPS enable" prompt dialog not working - The "GPS enable" dialog has now been implemented as a LWUIT dialog - fixed an issue that made this prompt display constantly 91936 Implement "blank" prompt type - added a fixed height value to blank prompts equivalent to left panel button height 92024 Exceptions thrown on departure screen with fare collection v1 enabled. - payment type for collected data was blank after prompts were displayed. this has been fixed. 91473 Configuration sometimes does not save - this should be fixed once and for all. had to do with uninitialized prompt data. 92023 Break and NoShow request does not work - break requests now working. - fixed a bug that caused the "cancel" button to not refresh once a break response has been received. 91409 NoShow needs to be re-implemented (ported) into 2.7 - NoShow timer forward applied and adapted to the changes present in the 2.7 structure. 91892 Implement Configurable tabs based on LoginResponse - Processes field 15, 16, 17, 18, 19, and 20 of the logon response if available to add and configure additional tabs in the app. - Field 15 and 16 pertain to the first tab - Field 15 is what prompts should appear on the tab - The first zubfield of 16 is the name of the tab - 17 and 18 to the second - Field 17 is what prompts should appear on the tab - The first zubfield of 18 is the name of the tab - 19 and 20 to the third - Field 19 is what prompts should appear on the tab - The first zubfield of 20 is the name of the tab ``` RMMobile_Android_v2.7.00_precut#3 --- ``` fixes: 91936 Implement "blank" prompt type - blank prompt type has now been implemented. 91408 Prompts need to have a more independent and solid structure - prompt containers now have a hierarchy which makes the elements much more structured. - this prompt hierarchy has been implemented in both "left panel prompt" screens (ie pre/post-inspection, fare prompts) and "plain pane prompt" screens (ie cubic tabs). 81078 I introduce a prompt page without a left panel, and a vertically split prompt piece called a PromptParagraph - resolved an issue where the locked screen would cause the context menu to disappear after each GPS update. 91863 Implement "button" prompt type - this is now implemented - fixed an issue where "single answer" prompt buttons were returning the incorrect SAPRES flags. - fixed a null pointer exception caused by omission of code used to setup ButtonAnswer class's reference to the Pane it resides in. 90709 RMMobile - Provide Electronic Signature Capture for Medicaid trips - ROOT. (90710, 90711, 90712, 91119 related) Now actually sends the signature as a .png file to RMGate Responds to a subfield sent to determine the height of the resultant image, defaults to 50 if none is given, or maximum if * is given All messages are encoded using ISO-8859-1 explicitly Ok button only enabled when the canvas is dirtied. Display resolution is used to display signatures to customer. Editable while the canvas is dirty, regardless if it was from a previous signature, or not. Cleans up signature files when they are no longer needed A new signature has been supplied. The signature has been enqueued to be sent The previous signature has been cleared -> ok'd - ManifestUnitOfWorkDO updated with changes for parsing field 53 (Guests/Attendant/Animal associated dollar amounts in cents). - fixed a StackOverflow problem which caused AlertDialogs to exhibit funny behavior (like not drawing properly). Improved file deletion to account for crashes or shutting down, mid signature. 91857 AlertDialog does not draw properly - this was a stack overflow causing strange draw behavior. 91404 Locked screen logic needs revamping with more solidarity - locked screen now shows up at the proper speed thresholds, but with no data. 91823 new checkbox on manifest items, causing MUW error in RMGate - fixed a typo that caused dropoff depart to fail with event kind errors for fixed route. 91686 Manifest table should update properly - mail and alert items now have titles and show (X of Y) in the title bar as they used to. - deferral option shows up for pickup only with payment version 1. 93115 RMMobile 2.5.01 VIMA showing Schedule Adherence twice - with new VIMA implementation, this should no longer be an issue. 92827 ETA Showing on VIMA screen even though it is not configured to do so ``` RMMobile_Android_v2.7.00_precut#2 --- ``` 91686 Manifest table should update properly - Mail alerts and mail box items now popup and display and operate properly. ``` RMMobile_Android_v2.7.00_precut#1 --- ``` - removed "Route End Check" dialog when finishing a route or run. - fixed an issue wherein fare collection showed up on the departure screen every time, and odometer was never displayed. - fixed an issue wherein the manifest selection was not remembered when leaving and returning to the manifest screen. - fixed an issue wherein the manifest did not display on the manifest screen after leaving and returning to the screen. - fixed the "Back" button on the payment screen. it is now a cancel button which returns you to the manifest. - fixed an issue that caused departure prompts to be skipped from the payment screen. - fixed an issue with pre/post inspection where a NullPointerException would occur every time. - fixed an issue wherein RTT and PRTT buttons did nothing. - fixed an issue where the Route Status screen always read $0.00 for both actual and expected fares with multifare setups. 91358 Forward Apply Electronic Signature capture from RMMobile 2.5 to 2.7 Signature Capture applied up to the partial fix available in 2.5precut#17 91359 Improve rmlogger and it should be in the shared rmwagent,rmmobile project. Now uses the shared version of RMLogger 91339 "Jump" button should not be available on fixed route stops Updated so that jump no longer appears for fixed route MUWs in the details panels. Added clearer comments for the .isMUWNoPart2 and .isMUWNoPart1 91408 Prompts need to have a more independent and solid structure - prompts now have a structure with clearly distinct data and UI elements. - classes have been trimmed down to contain only what they need. - prompts now align properly and honor the "right justified" and "non-empty/non-zero bits" as in previous versions. 91338 History tab should not be shown if show history feature is disabled 91337 Map tab should not show if map feature is disabled 91403 Pre and Post inspection should be reworked into a more sensible structure - pre and post inspection now print to the screen using the new structure from DM#91408 above. - entry point for pre inspection is now in a more sensible place (post-login) - fixed a bug wherein if the RMGate pre-inspection prompts had changed, RMMobile would display the prompts from the previous login every time. - fixed an issue where the login screen would not progress to the pre-inspection screen on a new RMMobile install. 91492 Stops perform status changes even though action is cancelled - this was caused by an addMUW call in the wrong place within the PangalacticGargleblaster.doArrive() method. 91555 Device and Debug properties screens need to draw without using prompts structure 91686 Manifest table should update properly - odometer now updates properly - "Updating Manifest" now no longer occurs on pre-inspection screen, and doesn't proc unnecessarily. - Manifest now always displays on the manifest page/tab - departure pane now shows appropriate fields - prompt behavior bits are now being interpreted properly again. - ported the "multifare v1" screen to 2.7.00. ################################################################################### Note that v2.6 is shelved as that was branch of the code that included significant structural changes but it lost some functionality functionality that was provided by v2.5. 2.7 was created which included UI restructure from v2.6 but kept other structure same as of v2.5. ################################################################################### ``` RMMobile_Android_v2.5.02_precut#8 --- ``` 92979 RMMobile 2.5.01 on the inspection screens, when VIMA triggers, the app becomes unresponsive - VIMA now returns to parent screen rather than always returning to manifest screen. ``` RMMobile_Android_v2.5.02_precut#7 --- ``` 93042 RouteMatch 'closing' after 9-11 minutes of no signal on Samsung Tab 4s - Updated manifest file to inclide "mcc" and "mnc" in activity configuration changes. "mcc" The IMSI mobile country code (MCC) has changed ? a SIM has been detected and updated the MCC. "mnc" The IMSI mobile network code (MNC) has changed ? a SIM has been detected and updated the MNC. When the SIM card lost connection for an extended period it changed states to ?IMSI?. The android operating system by default closes all apps that attempt to use services that change states unless otherwise stated in the project properties file. The fix included in 2.5.02precut#7 to add the attributes ?mcc|mnc? to the application activity elements. Mcc and mnc are two codes used to identify mobile network operators, and when devices that rely on SIM cards lose signal for long periods they attempt to update their mcc and mnc codes, which was causing the application to crash in previous versions. ``` RMMobile_Android_v2.5.02_precut#6 --- ``` 93042 RouteMatch 'closing' after 9-11 minutes of no signal on Samsung Tab 4s - added WakeLock, pause in onCreate of Activity and enforced running separate processes in manifest. ``` RMMobile_Android_v2.5.02_precut#5 --- ``` 93547 Run End button not being honored for relief driver. - Added logging to assist in post-mortem what scenario played out. With the current logging, it appears that when route/run/end is pressed, instead of pressing "Perform", "Cancel" is pressed in the "Are you sure you want to end run/route?" dialog. Once cancel is pressed, screen navigates to manifest screen, which perhaps gives the notion that run/route end is actually performed. If "Cancel" is pressed now, Departure Screen will stay in view. ``` RMMobile_Android_v2.5.02_precut#4 --- ``` 93208 Log indicates inability to procure message context for resend of messages after network inability. ``` RMMobile_Android_v2.5.02_precut#3 --- ``` 92919 auto arrive/depart causes tablet to "un-arrive" a stop sometimes - depart status no longer being set on mobile device on auto depart procs. 92895 Fare summary incorrectly displaying $0 - this should now be resolved. only affected the display at the end of the route... - fixed issue where all transactions were being lumped under "CASH". all payment types now have correct values. ``` RMMobile_Android_v2.5.02_precut#2 --- ``` 92919 auto arrive/depart causes tablet to "un-arrive" a stop sometimes - this is now resolved. 92858 ETA not displaying correctly NOTE: this DM was added to the readme after the cut was made. the case was found to be FIXED in QA testing. adding fix to readme retroactively for this precut. ``` RMMobile_Android_v2.5.02_precut#1 --- ``` 92848 RMMobile 2.5.01 driver is able to 'Done' through the fare screen on a $0 expected pay trip even without a $0 fare type config 92845 RMMobile 2.5.01 $0 payments on defered payment of a $0 expected pay trip causing RMGate SQL error 92843 RMMobile 2.5.01 SQL error in RMGate when trying to use $0 paytype (or amount) on $0 expected pay stops - For all three of the above cases, there was an oversight in part of the conditional that allows the message processing to proceed. RMMobile now properly forms messages where $0 payments of any kind are made. 92858 ETA not displaying correctly in manifest.layout for FR - ETA now displays properly. ``` RMMobile_Android_v2.5.01 --- ``` - Removed precut designation. ``` RMMobile_Android_v2.5.01_precut#2 --- ``` 92603 FORWARD_APPLY: RMMobile sends two messages with same tag (DM#92556) Tag number acquisition is now synchronized. ``` RMMobile_Android_v2.5.01_precut#1 --- ``` 92452 RMMobile 2.5.00 FR manifest is not loading - this fix was causing index out of bounds exceptions as the address would attempt to parse the "performed time" data without checking for field validity or exceptions. (rel. 92238) ``` RMMobile_Android_v2.5.00 GA --- ``` - removed precut designator from .apk package. ``` RMMobile_Android_v2.5.00_precut#25 --- ``` 92379 Keyboard for entering vehicle number on login screen does not allow for numbers - changed from DEFAULT_QWERTY to CUSTOM_QWERTY keyboard (backward applied from 2.7.00). 92377 Driver Manifest displays 'expected customer payment ID' instead of 'expected customer payment' - expected payment type should appear when defined as part of the manifest layout rather than the payment type id. 92228 NoShow wait timer visible on history tab - Wasn't checking the current tab, now we do, so it only effects the manifest tab. 92238 RMMobile> Para> History Tab pickup/arrive updates all trips/stops with the same Dropoff time - Whenever the value of a field isn't set there are some graphical side effects. This in particular was being caused by the performed time not being set for pickups in the manifest. The perormed time is now set. ``` RMMobile_Android_v2.5.00_precut#24 --- ``` 91473 Configuration sometimes does not save - fixed a bug which caused the login to always fail on the first attempt after saving configuration data. 91502 - if WiFi is off, RMMobile hangs on log in forever RMMobile will not wait longer than twice the TTL*Retries. If RMMobile has no errors or responses in that time, RMMobile cancels the connection. This saves us from getting stuck during login. 92141 - RMMobile 2.5.00 stop arrives with prompt screens are not processing correctly when BACK is pressed Arriving to prompts, then backing out now leaves the manifest entries state unaltered. Accomplished by changing the MUW state after hitting send on the Departure Data Screen Summary ``` RMMobile_Android_v2.5.00_precut#23 --- ``` 92082 - Signature Prompts - RESET button generates a null pointer error when using 2 signature prompts Fixed null pointer exception, a required variable was nulled out before the last time it was used. This has been fixed and safeguards put in place so if the clean up methods are called while the intent is null it won't cause errors. ``` RMMobile_Android_v2.5.00_precut#22 --- ``` 92002 - Some devices do not save signatures Fixed issues with certain devices not displaying or saving signatures. Circumnavigated the need for getDrawingCache, which doesn't behave the same on different devices. Created our own canvas to hold the data to be saved instead of relying on the drawing cache Forgot to set the background white fixed. 92003 - Single Prompts are not appearing as the correct prompt Fixed issue with single prompts not being displayed correctly, the first digit was being used to create the prompt, not the whole number. Now the prompt string is properly split by the delimiter. ``` RMMobile_Android_v2.5.00_precut#21 --- ``` 91890 RMGate is dumping signitures when multiple signitures are coming in at the same time SplitUpMessages weren't being properly flagged as ack required. 90709 RMMobile - Provide Electronic Signature Capture for Medicaid trips - ROOT. (90710, 90711, 90712, 91119 related) Improved file deletion to account for crashes or shutting down, mid signature. ``` RMMobile_Android_v2.5.00_precut#20 --- ``` 90709 RMMobile - Provide Electronic Signature Capture for Medicaid trips - ROOT. (90710, 90711, 90712, 91119 related) Fixed a race condition between reading the saved image and deleting the image. 91871 RMMobile on 'back' on prompt screen, multifare is reverting to classic layout the back button on the prompts screen now returns to the manifest in multifare v3. ``` RMMobile_Android_v2.5.00_precut#19 --- ``` - fixed an issue where pickup arrive prompts are displayed for all arrivals, including dropoffs, which should display dropoff-arrive prompts. 90709 RMMobile - Provide Electronic Signature Capture for Medicaid trips - ROOT. (90710, 90711, 90712, 91119 related) Now actually sends the signature as a .png file to RMGate Responds to a subfield sent to determine the height of the resultant image, defaults to 50 if none is given, or maximum if * is given All messages are encoded using ISO-8859-1 explicitly Ok button only enabled when the canvas is dirtied. Display resolution is used to display signatures to customer. Editable while the canvas is dirty, regardless if it was from a previous signature, or not. Cleans up signature files when they are no longer needed A new signature has been supplied. The signature has been enqueued to be sent The previous signature has been cleared -> ok'd 89546 Extend rmp to support binary message transfer Related to DM#90709 RMMobile - Provide Electronic Signature Capture for Medicaid trips - ROOT. (90710, 90711, 90712 related) Outbound from rmmobile, inbound to rmgate messages, if greater than 2k, are now split up in chunks as defined in RMP v1.8. + Fixed bug where the splitup message was appended with RMP delimeters after it was properly formatted to be sent. 90659 Integrate more versatile and aesthetic multifare collection UI - added deeper "integrity checks" on RMGate data. G/A/A amounts are skipped in the following conditions: + field 53 is not present (no change from precut#18) + field 53 is empty + field 53 contains incorrect number of subfields. - fixed an issue where the "are you sure" prompt when cancelling payment occurred on screens other than the v3 multifare screen ``` RMMobile_Android_v2.5.00_precut#18 --- ``` 90659 Integrate more versatile and aesthetic multifare collection UI - moved input of Attendants,Guests and Animals to the fare screen. - added indication of G/A/A expected to fare screen. - added support for new subfields in MUW which contain ridership expected pay data (G/A/A). - added an indicator in the left hand panel that shows if there is scrollable content in the central container. - allow adding aggregate items after the maximum payment buckets are filled. - added "strikethrough" G/A/A text which indicates original value if changed by the driver. [removed] - total fare now changes with G/A/A changes according to amounts sent from RMGate. - "Cancel" warning dialog on multi-fare screen now also removes GAA count changes. - replaced "strikethrough" with emboldened green changes on the main fare screen for G/A/A. - added indication of "expected" G/A/A values to "Additional Riders" dialog. 91478 Multi-fare version 1 causes NullPointerException on Defer pressed - fixed an error where payment information was not sent on deferral. - fixed an error in "multi-fare v1" where NullPointerException occurred on deferral. - fixed an error in "multi-fare v1" where NumberFormatException (Invalid double: "") occurred when the payment screen was displayed. - fixed an error in "multi-fare v1" where the defer button does nothing. 91339 "Jump" button should not be available on fixed route stops - Jump button no longer displays on a MUW's detail panel if it doesn't have a second part. ``` RMMobile_Android_v2.5.00_precut#17 --- ``` 00000 - RMMobile_Androi-v2.5.00_precut#16 was signed with the incorrect keystore. 17 is the same code with the correct keystore ``` RMMobile_Android_v2.5.00_precut#16 --- ``` 86128 Configuration of a no-show timer for RMMobile (86244, 88315, 88723 and 89305 DUP) - Bug allowing a user to skip the NoShow wait if they pressed while the text "NoShow" was displayed has been fixed - Bug if two pickup-arrrives are performed the timer shows both countdowns has been fixed. 86129 Configuration of an out-of-order warning for RMMobile - Out of order warning disabled again, should not appear to a user. ``` RMMobile_Android_v2.5.00_precut#15 --- ``` - this cut addressed naming issues within the .apk. all references to versions have been updated. ``` RMMobile_Android_v2.5.00_precut#14 --- ``` 89546 Extend rmp to support binary message transfer Related to DM#90709 RMMobile - Provide Electronic Signature Capture for Medicaid trips - ROOT. (90710, 90711, 90712 related) Outbound from rmmobile, inbound to rmgate messages, if greater than 2k, are now split up in chunks as defined in RMP v1.8. 90659 Integrate more versatile and aesthetic multifare collection UI - expected fare amount must be satisfied before proceeding (MUW behavior bits) - default value cannot be "unselected" (MUW behavior bits) - Removed truncating of track/account # obtained onSwipe to 10 characters (rmgate should send proper regex to what account # is). Added support for "insufficient funds" paytype bit - only allowed to pick this type if balance is zero - payment amount is always whatever the remaining balance is - changes are not allowed to other payments after this type is used (until this payment type is deleted from the list). Added support for "zero fare" paytype bit - only one may be used. - injected automatically if only one is available, and it has not yet been entered manually, unless other payment entries are present. - other payments disallowed after this type is used (until this payment type is deleted from the list). Added account number validation 90709 Provide Electronic Signature Capture for Medicaid trips - Signatures now saving on all devices - Greatly increased performance on older devices. 89546 Extend rmp to support binary message transfer Related to DM#90709 RMMobile - Provide Electronic Signature Capture for Medicaid trips - ROOT. (90710, 90711, 90712 related) Outbound from rmmobile, inbound to rmgate messages, if greater than 2k, are now splitup in chunks as definied in RMP v1.8. ``` RMMobile_Android_v2.5.00_precut#13 --- ``` Fixed the following DM's: 90909 Comma to separate the next prompt key onto a new screen does not work with pre/post inspection ``` RMMobile_Android_v2.5.00_precut#12 --- ``` Fixed the following DM's: 90709 Provide Ability to capture signature - added support for SIGNATURE type prompts - sends string indicating whether or not it was signed to RMGate - Currently deletes signature files after 1 hour TODO : Add a deletion trigger, instead of time. 90659 Integrate more versatile and aesthetic multifare collection UI - added support for "acctNo must come from swipe" - added support for "must select some default payment type" - added support for "expected paytype selected until entry of that type exists" - all amount fields now default to the "remaining balance". adjustments default to their entered values. - adjustment dialog now uses the same program flow as payment entry. QA NOTE: please test additions AND adjustments for all possible payment types and note any discrepancies. - changed ordering of errors. "amount" related errors now popup before "account" related errors. 91041 Sygic URL Needs Updated in RMMobile - changed the call to Sygic to one that is more explicit so that the user option for "how to run this Intent" does not show as an option to the end user. 90820 RMMobile should display at least as much info as provided by IP Widget. More Robust error messages during login, it now should handle messages passed back from RMGate and give an appropriate error message. ``` RMMobile_Android_v2.5.00_precut#11 --- ``` Fixed the following DM's 90659 Integrate more versatile and aesthetic multifare collection UI - "Adjust" on swipe should definitely display acct number. - the "error" popup for "empty acct is invalid" (and possibly others) has OK then CANCEL, but other dialogs have CANCEL then OK. - Fixed token adjust you needed to hit back and the fwd to get it to display amt; displays amount either way now. 89546 Extend rmp to support binary message transfer (related: DM#90518 RMGate/RMMobile message length limits prevent delivery of all needed Per and Post Inspection prompt items )Only proper reception/handling of rmp messages that are greater than 2048 is implemented (outbound messages (inbound to rmgate) aren't implemented yet). RMP v1.8. Need rmgate 6.4.00 precut#15+ - Problem was when the message (that was sent in chunks from rmgate) was formed again after concatenating different chunks, the last char which indicates end of message delimeter wasn't taken off before it was sent to the handler (upper layer) to parse etc� so the last list item which in this case was prompt 51 didn't get parsed properly. ``` RMMobile_Android_v2.5.00_precut#10 --- ``` Fixed the following DM's 90659 Integrate more versatile and aesthetic multifare collection UI - Properly disconnect from bluetooth card reader on close of multifare dialog, so connection can be established again successfully if and when multifare dialog is launched again. ``` RMMobile_Android_v2.5.00_precut#9 --- ``` Fixed the following DM's 90659 Integrate more versatile and aesthetic multifare collection UI - Proper display of bluetooth card reader's connection status in the multifare dialog. - Account field sizing corrected. ``` RMMobile_Android_v2.5.00_precut#8 --- ``` Fixed the following DM's 86128 Configuration of a no-show timer for RMMobile (86244, 88315, 88723 and 89305 DUP) - Removed excess ResetLeftContainer Calls - Added support for RMMobile receiving a no show timer - Added support for locking the NoShow button and displaying a timer First appears in RMP1.5 - field#14 is number of seconds to wait after pickup-arrive before noshow button can be pressed. 0 for legacy/none. this field is for rmmobile dm#86128, which is not yet targetted. the rmgate.properties file now requires new key "device.gateway.config.rmp.pickup.noshow.timer" whenever the "device.gateway.class" key has specified RMP. First Used by RMGate 6.1.00 Precut#8 - Removed NoShow radio button from depart menu 89546 Extend rmp to support binary message transfer - rmmobile (which is already fixed) (related: DM#90518 RMGate/RMMobile message length limits prevent delivery of all needed Per and Post Inspection prompt items )Only proper reception/handling of rmp messages that are greater than 2048 is implemented (outbound messages (inbound to rmgate) aren't implemented yet). RMP v1.8. Need rmgate 6.4.00 precut#15+ 90709 RMMobile - Provide Electronic Signature Capture for Medicaid trips - ROOT. (90710, 90711, 90712 related, DUP 90981) Note that this is only the INITIAL PROOF OF CONCEPT IMPLEMENTATION... actual signatures are NOT sent into rmgate and/or stored in db. prompt-kinds "(dbg#01)" ... "(dbg#10)" can now specify "{SIGNATIRE}". rmmobile will place a button that brings up a drawing canvas so the user can sign their name. in this initial implementation, the only result sent into rgmate will be a "Signature captured" or "Not yet signed" string value, which will be visible in rmgate log messages, indicating what took place on the device. rmp protocol 1.8 implements new PRMTYPE_ANSWERFORMAT_SIGNATURE (0x07). Need rmgate 6.4.00 precut#15+ 90659 Integrate more versatile and aesthetic multifare collection UI - Error handling and UI improvements including correct display of amount collected while using tokens/passes and making adjustments etc. ``` RMMobile_Android_v2.5.00_precut#7 --- ``` Fixed/Implemented the following changes: 90659 Integrate more versatile and aesthetic multifare collection UI - have fun! Added support for deducting amounts from aggregate types on the MultiFarePaymentCentralContainer.java TODO:Add info about what was fixed and what's left for this DM ``` RMMobile_Android_v2.5.00_precut#6 --- ``` Fixed/Implemented the following changes: 90595 RMMobile > History data no longer displays. - applied the fix for the same issue present in 2.4.03. 90696 Add handling of failure code 12 : "VLU not yet initialized" - new failure code is handled appropriately and driver is prompted to try again. 90705 Signoff message needs to check and send time if it's synched with server/rmgate - fixed 90696 Add handling of failure code 12 : "VLU not yet initialized" - handled 89896 Display clock causes java.lang.OutOfMemory error if additional LeftContainers are used. - actually, this was fixed in 2.4.03. see DM#89848. ``` RMMobile_Android_v2.5.00_precut#5 --- ``` Fixed/Implemented the following changes: Forward applied all DMs from 2.4.03 "post-branch split". All DMs from 2.4.03 need to be tested against this release. ``` RMMobile_Android_v2.5.00_precut#4 --- ``` Fixed/Implemented the following changes: 80003 Need for a logoff button because new devices do not have the menu button - added 'Exit' button on Info tab left panel. 88646 Add RMMobile 'AUTO DEPART' functionality (DM# 88647 RMGate, 78066 related) - auto depart should now be fully functional, enabled by InternalID 218 bit 0x02 (auto arrive is 0x01, therefore 0x03 enables both). - check that auto depart works without auto arrive enabled. it's my suspicion that RMGate isn't sending the target radius values unless auto arrive is also enabled alongside auto depart. 78066 Geofencing should be implemented to support auto arrive. (DM#86416 related, 88429 DUP) - found and fixed a bug which caused the wrong time to return in the auto-arrive event. - when testing, please check the auto arrive times versus the actual arrive times and make sure they are correct. [BRANCH_SWITCH] /*************************************** * Due to time constraints, the 2.4.03_precut#9 code base was adapted to include required * DMs for delivery to client. The 2.5.00_UI code base will become 2.6.00. the 2.5.00 * version number will continue from 2.4.03_precut#9 ***************************************/ ``` RMMobile_Android_v2.5.00_precut#3 --- ``` Fixed/Implemented the following changes: 75893 NO SHOW as a "notification" or as a "request" based on the particular device char (similar-75892, RMGate-86617) 88646 Add RMMobile 'AUTO DEPART' functionality (DM# 88647 RMGate, 78066 related) 88197 Log In Button Disappears and Requires Refresh - this should still be happening very seldom. please dig into this and report any issues. TODO : What happened to precut 1 and 2 for 2.5? ``` RMMobile_Android_v2.4.03_precut#11 --- ``` + Fixed the following DM(s): 90569 Buttons not working after selecting "cancel" when performing Route/Run Stop; Dual Excute buttons are displayed - this was a problem with the left panel getting wonky when this dialog is displayed. - the "extra Execute" button still shows up, but goes away after the dialog is dismissed. - perform and cancel buttons should work properly. - for now, ending a route or run does NOT backclear the manifest. this is a known issue. do not fail the case back for this. - in the event that you DO try to execute one of the stops after you have completed the route/run, RMGate will reject it, so there is no danger. ``` RMMobile_Android_v2.4.03_precut#10 --- ``` + Fixed the following DM(s): 90268 Null Pointer Exception Error - added more logging and the problem should be alleviated now. 90513 Emergency Button screen redraw issues causes improper rendering of left panels buttons - when returning from the emergency screen, the current screen value was set incorrectly ``` RMMobile_Android_v2.4.03_precut#9 --- ``` + Fixed the following DM(s): 90139 Buttons intermittently disappear in app - finally found the root cause; when the manifest updates its central panel, it steals the left panel. - LeftContainer thievery is now outlawed in RMMobile. 90004 Vehicle in Motion Screen freezes and doesn't go away (Panasonic Toughpad) 90136 Internal Communication Failure (related DM#90004) 90012 RMMobile freezes when VIM uses device.gateway.config.rmp.options bit 0002 - added logging to further pinpoint the VIMA freeze issue. ``` RMMobile_Android_v2.4.03_precut#8 --- ``` + Fixed the following DM(s): 90012 RMMobile freezes when VIM uses device.gateway.config.rmp.options bit 0002 + In precut#7, instead of just updating the text of VIMA. When manifest is updated, screen would unblocked and then blocked. Now just updating the text. ``` RMMobile_Android_v2.4.03_precut#7 --- ``` + Fixed the following DM(s): 90012 RMMobile freezes when VIM uses device.gateway.config.rmp.options bit 0002 ``` RMMobile_Android_v2.4.03_precut#6 --- ``` + Fixed the following DM(s): 90028 Deselecting multiple customers with the same pickup and/or drop off results in error. - fixed concurrency issues with group arrive. ``` RMMobile_Android_v2.4.03_precut#5 --- ``` + Fixed the following DM(s): 89913 Properly handle manifest updates messages - back clear of stops. 89914 VIMA screen text should not be carried over to the next time it is displayed. ``` RMMobile_Android_v2.4.03_precut#4 --- ``` + Fixed the following DM(s): 89848 Tablets at UGA consistently getting "Out of Memory" Java errors in RMMobile. - fixed a memory leak with graphics components creating too many objects. ``` RMMobile_Android_v2.4.03_precut#3 --- ``` + Fixed the following DM(s): 89848 Tablets at UGA consistently getting "Out of Memory" Java errors in RMMobile. + Don't have a fix yet. HPROF dump couldn't be captured with the v2.4.03_precut#1precut#1or#2 as LWUIT library code actually catches OutOfMemoryError and the trigger for HPROF dump was OutOfMemoryError. Now explicitly calling HPROF dump capture where ever in LWUIT's Image.java OutOfMemoryError is explicitly caught. + In additon, same techniques that are used in LWUIT's Image.java to cope with OOM are applied when VIMA is to be displayed/removed so that image/references are cleared out before getting to the boil over limit. ``` RMMobile_Android_v2.4.03_precut#2 --- ``` + Fixed the following DM(s): 89789 Disclaimer message takes up whole screen and OK button not shown sometimes at launch. 89797 Dialogs shouldn't remove the interactive buttons regardless of the size of the screen. ``` RMMobile_Android_v2.4.03_precut#1 --- ``` Heap dump is captured in the rmmlogs directory whenever java.lang.OutOfMemoryError is observed. ``` RMMobile_Android_v2.4.02 --- ``` Removed "_precut#x" designator from version name. ``` RMMobile_Android_v2.4.02_precut#12 --- ``` + Fixed the following DM(s): 89685 End route sometimes does nothing when 'perform' button is pressed from manifest screen ``` RMMobile_Android_v2.4.02_precut#11 --- ``` + Fixed the following DM(s): 89762 beeps missing for "Acknowledgement" popups - beeps now occur for all popups as they should. - test with both RMGate 6.3 and RMGate 6.4 (latest cut). 89760 right justified fields on prompt screens are cut off on the right side - central panel sizing should now be correct for all screens. ``` RMMobile_Android_v2.4.02_precut#10 --- ``` + Fixed the following DM(s): 89760 right justified fields on prompt screens are cut off on the right side - central panel sizing should now be correct for all screens. ``` RMMobile_Android_v2.4.02_precut#9 --- ``` + Fixed the following DM(s): 89708 Route status screen may not populate with correct data. - route stats now populate as they should. ``` RMMobile_Android_v2.4.02_precut#8 --- ``` Solved a LWUIT bug when processing focus of newly created components. + Fixed the following DM(s): 89685 End route sometimes does nothing when 'perform' button is pressed from manifest screen - ending a run will no longer display the route stats screen. only route ends will. - performing a garage end should never fail. ``` RMMobile_Android_v2.4.02_precut#7 --- ``` + Fixed the following DM(s): 89675 When returning focus to app, dialogs cannot be interacted with and hangs RMMobile - BE SURE TO TEST WITH XPLORE 10" TABLET 89681 ManifestUpdateMessage with muw status updates don't result in refresh of manifest screen update. ``` RMMobile_Android_v2.4.02_precut#6 --- ``` Basically fixes the same DMs as precut#5, but the build is different as it now includes the most current files from repository. ``` RMMobile_Android_v2.4.02_precut#5 --- ``` + Fixed the following DM(s): 89661 If time sync request is successful, login request message should have the synched time in the EventTime section. 89539 Run End and Route End Lines Will Not Remove From RMMobile Until After Log Off/On ending a route/run early will never fail for FR or para. 89658 Manifest changes/updates should be allowed/viewable when blocker is displayed. ``` RMMobile_Android_v2.4.02_precut#4 --- ``` + Fixed the following DM(s): 89589 Cancels in dispatch are not received by RMMobile ``` RMMobile_Android_v2.4.02_precut#3 --- ``` Made an aesthetic change to the status bar that shifts the odometer, connection status and clock to the right. + Fixed the following DM(s): 89509 StatusUpdateMessage does not perform coloring (and possibly other stuff) on manifest changes. - updates now color properly. ``` RMMobile_Android_v2.4.02_precut#2 --- ``` + Fixed the following DM(s): 89584 Manifest list/table isn't updated after back-clear/status update messages are sent from rmgate. + MUW updates included in MUWStatus update messages are processed exactly the same way MUW updates were handled prior to rmp v1.6. ``` RMMobile_Android_v2.4.02_precut#1 --- ``` Added support for HoneyDo 'wait' command. + Fixed the following DM(s): 89509 StatusUpdateMessage does not perform coloring (and possibly other stuff) on manifest changes. - manifest popups now occur as normal. 89539 Run End and Route End Lines Will Not Remove From RMMobile Until After Log Off/On - ending a route/run early will never fail. 89584 Manifest list/table isn't updated after back-clear/status update messages are sent from rmgate. 87180 Prompts - comma in Inspection prompts list does not properly provide next page (related DM#74074) ``` RMMobile_Android_v2.4.01 --- ``` Removed "_precut#x" designator from version name. ``` RMMobile_Android_v2.4.01_precut#2 --- ``` + Fixed the following DM(s): 89508 Unable to remove trips from manifest that have been reassigned. - remove button now appears as it should. 89509 StatusUpdateMessage does not perform coloring (and possibly other stuff) on manifest changes. - deletions sent via StatusUpdateMessage MUWFlags now color as "removed" as they should. - fixed an issue with improper handling of empty performance sections in message. ``` RMMobile_Android_v2.4.00 --- ``` Removed "_precut#x" designator from version name. ``` RMMobile_Android_v2.4.00_precut#4 --- ``` + Fixed the following DM(s): 89435 Handling Route/Run Stops - RUN STOP line needs to pop up are you sure message. (follow up to DM#88159) - "end route" now actually works. ``` RMMobile_Android_v2.4.00_precut#3 --- ``` MERGED: 2.3.03 GA version has been merged into 2.4.00 as of this precut. + Fixed the following DM(s): 80067 Ability to show ETA on the Device (DM#82152 (RMGate Work), 88764 (DB Work) Dependent - Improved display of ScheduleAdherence in the status bar across various screen sizes. 89436 Handling Route/Run Stops - Pop up dialog is a little too small to show all the text - increase the box size - Dialog boxes now come with more width stretchiness. ``` RMMobile_Android_v2.4.00_precut#2 --- ``` + Forward applied fixes and code changes from v2.3.03_precut#3. + DM#80067 Ability to show ETA on the Device (DM#82152 (RMGate Work), 88764 (DB Work) Dependent "Vehicle in Motion" block screen is a full screen. Fixed dynamic ETA, SA and clock on VIM. ``` RMMobile_Android_v2.4.00_precut#1 --- ``` + Partial fix of DM#80067 Ability to show ETA on the Device (DM#82152 (RMGate Work), 88764 (DB Work) Dependent Implemented RMP v1.6 with the update MUWStatusUpdated message with ManifestPerformance section and ManifestPerformance Message. Schedule Adherence info is displayed in the status bar, red if behind schedule and green if ahead/on-time. ETA of a stop is only coded to be displayed either in the detail screen or if configured properly then in the "Vehicle In Motion (VIM)" block screen. VIM is currently NOT implemented as a full screen, however, clock update and SA/ETA information is dynamic. ``` RMMobile_Android_v2.3.03 --- ``` Removed "_precut#x" designator from version name. ``` RMMobile_Android_v2.3.03_precut#5 --- ``` + Fixed the following DM(s): 89420 RMMobile - Unable to exit emergency mode - breaks - better handling of the left panel. ``` RMMobile_Android_v2.3.03_precut#4 --- ``` + Fixed the following DM(s): 89420 RMMobile - Unable to exit emergency mode - breaks - added the "back" button back for emergency and break screens (returns to main info tab screen, as it did). 89106 occasionally RMMobile does not ACK the logon response from RMGate. - fixed and tested. 89367 "Dismiss" button need to be modify - buttons should no longer truncate button text. ``` RMMobile_Android_v2.3.03_precut#3 --- ``` + Fixed the following DM(s): 89062 Enabling Assistance Needs Removes Customer Name - "segments" which are larger than the screen will now ellipsize, taking only 1/nth of the screen where 'n' is the number of segments. 89238 Prevent Fare Report and Passenger Report displayed when garage stop completed - the fare and passenger report should only show if the device has processed para trips. 88159 Handling Route/Run Stops - you should now see a warning if you attempt to complete the end route stop before completing all other stops. ``` RMMobile_Android_v2.3.03_precut#2 --- ``` + Fixed the following DM(s): 89243 RMMobile Audible Alerts Do Not Sound - RMMobile should play an audible alert whenever the driver needs to be alerted of new messages. 89106 occasionally RMMobile does not ACK the logon response from RMGate. - added more config data persistence in the inbound listener. 78066 Geofencing should be implemented to support auto arrive. (DM#86416 related, 88429 DUP) - fixed some code displacement during the merging of the 2.4 branch which caused an improper key to be used when referencing manifest items against the auto-arrive list. 89386 "COPY-ADD" and "COPY-GPS" in map tab does not working in FR. - clipboard now works as it should. 89005 RMMobile generates "Invalid GPS" Warning every time it logs in. - fixed by sending empty GPS info in login request if no GPS info is available. 89233 Add enhancements to mailbox / dispatch message windows - adjusted button text size, as it might be too small for some drivers to see. - added (viewing X of Y messages) in title area of window. - adjusted message text size; needs to be slightly larger (10" screens make it look tiny). - mailbox needs to differentiate any messages in the mailbox that still require a driver response. ``` RMMobile_Android_v2.3.03_precut#1 --- ``` + Fixed the following DM(s): 89036 Improve look and feel of configuration screen - ensure that the 'clear' functionality works on the debug and device properties text entry fields. - allow full 64-bit entry into debug / device properties fields (this was actually a bug where the maximum value was tested against the field's original value and the new accepted value, which was just wrong. this was actually present in every field.) - allow saving invalid data. - disallow login if bad / incomplete data is present. - should not have to enter things in order and/or that are not needed by the subordinate popup forms (property and/or debug bitset) in order to get to those forms. 89243 RMMobile Audible Alerts Do Not Sound - RMMobile should play an audible alert whenever a dispatch message is received. 89233 (FIXED_PARTIAL) Add enhancements to mailbox / dispatch message windows - button text size adjusted. - "Viewing X of Y (Popups/Mails)" should appear in the upper left corner of all messages now, and display the appropriate value. - message text size is slightly larger. - messages which still require a driver response are now marked with an 'X' in the mailbox. - there are 2 more items in the DM which will be added in the next precut. 89106 occasionally RMMobile does not ACK the logon response from RMGate. - all login responses should ACK appropriately and config data is more persistent after config changes... 89250 Sometimes break updates are not sent when returning from break - all break updates should be sent as expected, even after visiting the configuration screen (or doing anything else the user can do). 88402 (FIXED_INDIRECTLY) RMMobile changes the Debug Properties value after going to break - this was fixed inadvertently when making improvements to the config screen (89036). test thoroughly. 89096 "Communication Failure" message needs to be re-worded. - changed wording of dialog to something more sensible and human-readable. 89156 Maps do not display if address info is not valid - maps would not display if only address info (no lat/lon) were available for the stop. now all stops should be mappable. - need to test for both Sygic and Google Maps. 89248 LOGGING: Log In Button Disappears and Requires Refresh - logging items to help with 88197. (Login button disappears). see DM Notes. ``` RMMobile_Android_v2.3.02 --- ``` Removed "_precut#x" from version ``` RMMobile_Android_v2.3.02_precut#5 --- ``` + Fixed the following DM(s): 89112 Add old features to new alert dialogs - fixed a minor issue with mail messages overlapping the screen blocker and not disappearing as they should. ``` RMMobile_Android_v2.3.02_precut#4 --- ``` *Added some extra logging for fare prompts for case 88154* + Fixed the following DM(s): 89112 Add old features to new alert dialogs - newest dispatch message popup now appears on top. - message queue does not 'loop' when using 'next' and 'prev' buttons - mailbox items can now be traversed using 'next' and 'prev' buttons from within the popup window ``` RMMobile_Android_v2.3.02_precut#3 --- ``` + Fixed the following DM(s): 89112 Add old features to new alert dialogs - Forgot to enclose the Android UI call .show inside the runOnUiThread Runnable. Herp Derp. ``` RMMobile_Android_v2.3.02_precut#2 --- ``` + Fixed the following DM(s): 89112 Add old features to new alert dialogs - "Previous" and "Next" buttons - Red text for dispatch messages ``` RMMobile_Android_v2.3.02_precut#1 --- ``` Accidentally included some excess changes in the 2.3.01 GA cut. Replacing 2.3.01 junk with pristine build of 2.3.01_precut#9 as 2.3.02_precut#1. ``` RMMobile_Android_v2.3.01 --- ``` Removed "_precut#x" from version + Fixed the following DM(s): 88132 RMMobile - Maintain versioning that is visible by AirWatch MDM solution - Changed a couple lines in the manifest so that (hopefully) the details of our app will appear in the Mobile Iron interface with the 'code version' and 'display name' fields populated properly. ``` RMMobile_Android_v2.3.01_precut#9 --- ``` + Fixed the following DM(s): 88773 Modify NOTIFY behavior to allow the ability to set MUW color without popping up (81739 related - RMGate) - fixed an issue where FR stop popups were not displaying properly. the dialogs make much more sense now. 89001 Reverse order of mailbox items so that newer items are at the top 84614 Provide a method in RMMobile to alert the driver that GPS is turned off and request it be turned on - provided an abstract GPS system setting interface/impl which detects GPS and prompts the user to enable it. - please see the DM, which contains Dave's input and my solution as well as test steps. ``` RMMobile_Android_v2.3.01_precut#8 --- ``` + Fixed the following DM(s): 88773 Modify NOTIFY behavior to allow the ability to set MUW color without popping up (81739 related - RMGate) - added proper handling of new color bit. 88742 Cannot Remove Update Alert Pop-up in RMMobile 2.3.00: - fixed a bug in CannedMessageTask which released the message context at inappropriate times, causing ACK messages to be ignored, and allowing messages to be sent when they should not be. ``` RMMobile_Android_v2.3.01_precut#7 --- ``` Removed FileNames.java, and instead marked logging, thread names and message context owner using 'class.getName()'. this ensures that, rather than relying on references to static strings (see FileNames.java in previous revision), we always get the actual name of the class doing the thing being logged/sent/whatever. + Fixed the following DM(s): 88742 Cannot Remove Update Alert Pop-up in RMMobile 2.3.00: 87433 freezes when attempting to send canned message: - fixed an error in the OutboundMessageSender / InboundMessageHandler which caused the next message sent after a "ACK only" message to fail and then requeue, (see 87433 comments in OutboundMessageSender.java and InboundMessageHandler.java). - changed canned message failure alert to something more understandable by the driver in the case where they attempt to send a canned message whilst another "immediate send" message is being sent. - went back to the old "display manifest screen after canned message send button pressed" behavior to indicate to the driver that their command is being processed. 88865 Communication Error on First Logon: - auto arrive analyzer thread was not instantiated before .start() was attempted. instantiation is now guaranteed. ``` RMMobile_Android_v2.3.01_precut#6 --- ``` + Fixed following DM(s): 88828 Initial login fails without error, stays on "Logging In" screen: - ensure socket creation success does not depend on config data being present. - ensured that socket creation is handled with appropriate errors on failure. - ensured that socket is only created once. ``` RMMobile_Android_v2.3.01_precut#5 --- ``` + Excluded work done for DM# 78066 Target checking and auto-arrive feature implemented, as it needs improved error handling. Instead of fixing the actual bug, excluding the code so FairBanks and other agencies can actually use rmmobile and other enhancements. ``` RMMobile_Android_v2.3.01_precut#4 --- ``` + Fixed following DM(s): 88829 RMMobile2.3.01 Precut#3: received error when trying perform a trip (related to DM#88798) 88742 Cannot Remove Update Alert Pop-up in RMMobile 2.3.00: 87433 freezes when attempting to send canned message: - applied dialog changes to mailbox items, so when they are viewed they use the new dialog style. - changed look of dialogs to correlate better with app theme. - added support for "standard"/"non-popup" messages to be answered from the mailbox. - added mailbox notification to notification bar indicating total mail messages as well as number unread. ``` RMMobile_Android_v2.3.01_precut#3 --- ``` 88193 Trips Rejected by Tablet - more logging added 88798 RMMobile doesn't discriminate the same ID across objects when receive muw work from RMGate - By RMP definition the unique key to identify a MUW is muwID/muwKind and muwKind exists specifically so two MUWs with same ID are properly considered distinct. ``` RMMobile_Android_v2.3.01_precut#2 --- ``` Precut#1 released with incorrect release key. re-releasing with proper .apk. Changes for DM#87433 and DM#88742 moved to UIController to ensure platform independence. + Fixed following DM(s): 88775 Improve behavior of color coding on RMMobile MUW changes in support of same dat FR manifest changes (RMGate DM#81739) - now properly checking for notify option when processing all MUWs (originally, only new MUWs were checking the bit). - added color bit handling for more control over MUW changes (new/change/remove) colors and notifications. ``` RMMobile_Android_v2.3.01_precut#1 --- ``` + Fixed following DM(s): 87433 freezes when attempting to send canned message: 88742 Cannot Remove Update Alert Pop-up in RMMobile 2.3.00: - added the ability to multitask while canned message is being sent. other messages which require "immediate send" while the canned message is processing will be rejected and a failure message will be displayed. - added subtle success message which doesn't interrupt user activity (using Toast). - ensured failure messages always get delivered to the screen. - fixed a bug that caused the task to be re-run in it's entirety (all retries and TTLs expired 3 times before the task failed). ``` RMMobile_Android_v2.3.00 --- ``` Removed "_precut#x" from version. ``` RMMobile_Android_v2.3.00_precut#10 --- ``` + Fixed following DM(s): 88692 RMMobile app display clock lags behind the system (server) clock. - Display clocks are refreshed every 1 second and got rid of java.util.TimerTask ``` RMMobile_Android_v2.3.00_precut#9 --- ``` + Fixed following DM(s): 88692 RMMobile app display clock lags behind the system (server) clock. ``` RMMobile_Android_v2.3.00_precut#8 --- ``` + Fixed following DM(s): 88684 departing break start causes break end to disappear from the manifest ``` RMMobile_Android_v2.3.00_precut#7 --- ``` N/A ``` RMMobile_Android_v2.3.00_precut#6 --- ``` NOTE: was released without synchronizing the code properly. Precut#7 includes the fixes in precut#6 essentially. 88065 Synchronize times across MDCs, VLUs, and servers (DM#85689/87780 related) Correctly update the display clock with the Server Time after synchronizing. 88455 Fix the "incomming" misspelling in debug properties ``` RMMobile_Android_v2.3.00_precut#6 --- ``` + Fixed following DM(s): 88065 Synchronize times across MDCs, VLUs, and servers (DM#85689/87780 related) Correctly update the display clock with the Server Time after synchronizing. 88455 Fix the "incomming" misspelling in debug properties ``` RMMobile_Android_v2.3.00_precut#5 --- ``` + Fixed following DM(s): 88065 Synchronize times across MDCs, VLUs, and servers (DM#85689/87780 related) ``` RMMobile_Android_v2.3.00_precut#4 --- ``` + Fixed following DM(s): 88574 StoreNforward messages permanently stored properly (related: 78070) 88575 Maintain proper order of messages outbound from rmmobile (inbound to rmgate). ``` RMMobile_Android_v2.3.00_precut#3 --- ``` + Fixed following DM(s): 78066 Target checking and auto-arrive feature implemented. 88153 RMMobile Configuration is Wiped Without User Edit 88020 RMMobile displays login screen after improper RMMobile exit even though device is still sending data to RMGate ``` RMMoobile_Android_v2.3.00_precut#2 --- ``` + Fixed following DM(s): 75893 "No Show" request implementation 88020 RMMobile displays login screen after improper RMMobile exit even though device is still sending data to RMGate 88380 RMMobile_2.3.00_precut#1 does not install on top of latest GAed 2.2.03 on Android 4.2.2 devices 88396 Msg received with a tag# that's receivd early should be checked if the contents is same, if not treat as new msg. ``` RMMoobile_Android_v2.3.00_precut#1 --- ``` + Fixed following DM(s): 87567 Merge Agent and Mobile code bases + Code version bumped to 0600 ``` RMMobile_Android_v2.2.03 --- ``` + Fixed the following 1 DM 00000 - Removed '_precut#' designation ``` RMMobile_Android_v2.2.03_precut#2 --- ``` + Fixed the following 1 DM 87764 - Sygic not available when GPS is unavailable + removed cancel button ``` RMMobile_Android_v2.2.03_precut#1 --- ``` + Fixed the following 1 DM 87764 - Sygic not available when GPS is unavailable ``` RMMobile_Android_v2.2.02 --- ``` + Fixed the following 1 DM 00000 - Removed '_precut#' designation ``` RMMobile_Android_v2.2.02_precut#7 --- ``` + Fixed the following 1 DM 87748 - Internal Error when attempting to send emergency message ``` RMMobile_Android_v2.2.02_precut#6 --- ``` + Fixed the following 1 DM 87628 - Initial Keyboard in RMMobile does not have number pad + Changed keyboard layout to follow Dave's design ``` RMMobile_Android_v2.2.02_precut#5 --- ``` + Fixed the following 1 DM 86719 - Dispatch Message Screen: Color/font of incoming text from Dispatching is difficult to read + reverted text color change, made the background lighter instead ``` RMMobile_Android_v2.2.02_precut#4 --- ``` + Added logging to GPS + Fixed the following 1 DM 86719 - Dispatch Message Screen: Color/font of incoming text from Dispatching is difficult to read ``` RMMobile_Android_v2.2.02_precut#3 --- ``` + Fixed the following 1 DM 87628 - Initial Keyboard in RMMobile does not have number pad + Fixed left/right navigation buttons + Changed CXL to CAN for three letter cancel + Fixed shift key not working ``` RMMobile_Android_v2.2.02_precut#2 --- ``` + Fixed the following 1 DM 87628 - Initial Keyboard in RMMobile does not have number pad ``` RMMobile_Android_v2.2.02_precut#1 --- ``` + Fixed the following 1 DM 87646 - Update RMMobile's code regarding GPSInfo ``` RMMobile_Android_v2.2.01 --- ``` + Fixed the following 1 DM 00000 - Removed '_precut#' designation ``` RMMobile_Android_v2.2.01_precut#18 --- ``` + Code clean-up + Fixed the following 2 DM 87304 - Failure to load correctly after a crash + Fixed MUWs m_behaviour and m_flags being saved as decimal but loaded as hex + Added a call to update the DriverManifestTabbed screen to fix the manifest screen sometimes loading empty + Moved call to load configuration to prevent it from not being loaded correctly 78071 - Screen lock when there is no GPS signal should be removed. + Added a GPSMonitor thread to determine if the last known GPS location was stored outside of the confidence interval ``` RMMobile_Android_v2.2.01_precut#17 --- ``` + Code clean-up + Disabled the language selector + Fixed the following 1 DM 87390 - TTL Exception popping immediately on Login + added the check to the debug/settings buttons ``` RMMobile_Android_v2.2.01_precut#16 --- ``` + Fixed the following 3 DM 87482 - Exit button should not be visible on post-inspection screen. 87443 - Vehicle in Motion window header is not visible on some devices. (RMMobile 2.2.01_precut#13) + Fixed the duplicate titles on devices on which this previously worked 87390 - TTL Exception popping immediately on Login ``` RMMobile_Android_v2.2.01_precut#15 --- ``` + Fixed the following 2 DM 87443 - Vehicle in Motion window header is not visible on some devices. (RMMobile 2.2.01_precut#13) 87304 - Failure to load correctly after a crash ``` RMMobile_Android_v2.2.01_precut#14 --- ``` +added null check to pre/post items + Fixed the following 5 DM 87445 - Hitting anywhwere under the OK button on the Disclaimer screen locks the button down. 87446 - Clicking 'Next' in trip details screen on final trip throws ArrayIndexOutOfBoundsException error message 87443 - Vehicle in Motion window header is not visible on some devices. (RMMobile 2.2.01_precut#13) 87442 - Font size is too big on the ET1's Vehicle in Motion screen (RMMobile 2.2.01_precut#13) 87435 - RMMobile sits at a blank blue screen after hitting Save or Cancel at the Config screen ``` RMMobile_Android_v2.2.01_precut#13 --- ``` + Fixed the following 2 DM 87339 - java.lang.Exception when attempting to log in to RMMobile. + added null check + changed foreach to for 87403 - RMMobile crashes if screen goes to sleep for more than 5 minutes. ``` RMMobile_Android_v2.2.01_precut#12 --- ``` + Fixed the following 3 DM 87392 - Set the Vehicle in Motion screen to be developer only option 87359 - OK button is half visible on GalaxyTab2 7' on the Login screen Invalid ID pop up window 85179 - Implement RTT and PRTT on the Manifest Screen + fixed inverted logic ``` RMMobile_Android_v2.2.01_precut#11 --- ``` + Fixed the following 2 DM 87339 - java.lang.Exception when attempting to log in to RMMobile. 87340 - Hitting the Help button at the login screen throws a java.lang.NullPointerException +also removed help button from pre/post inspection ``` RMMobile_Android_v2.2.01_precut#10 --- ``` + Code clean-up + Fixed the following 1 DM 87328 - Fix AM/PM spacing when in 12 hour mode ``` RMMobile_Android_v2.2.01_precut#9 --- ``` + Fixed the following 2 DM 87328 - Fix AM/PM spacing when in 12 hour mode 87307 - Upgrading from 2.1d to 2.2.0 and above brings up config screen with warning message + Fixed an issue with the device properties being populated with the x500000 bits on ``` RMMobile_Android_v2.2.01_precut#8 --- ``` + Fixed the following 1 DM 87307 - Upgrading from 2.1d to 2.2.0 and above brings up config screen with warning message ``` RMMobile_Android_v2.2.01_precut#7 --- ``` + Code cleanup - using constant values instead of magic numbers + Fixed the following 2 DM 87328 - Fix AM/PM spacing when in 12 hour mode 87304 - Failure to load correctly after a crash ``` RMMobile_Android_v2.2.01_precut#6 --- ``` + Fixed the radio buttons not working correctly on the device/debug properties screens + Fixed the following 2 DM 87328 - Fix AM/PM spacing when in 12 hour mode 87273 - Deleted trip from MUW should get back to the MUW if dispatching assigns it again to the vehicle ``` RMMobile_Android_v2.2.01_precut#5 --- ``` + Reverted to 2.2.01_precut#2 with the change to fix bit values on prompt items ``` RMMobile_Android_v2.2.01_precut#4 --- ``` + Fixed the following 1 DM 87179 - RMMobile prompts print giant SKIP button when using 0x20 modifier to put answers on next line (related DM#74074) + fixed issue with skip button usage ``` RMMobile_Android_v2.2.01_precut#3 --- ``` + Fixed null pointer on login + Fixed font scaling + Fixed the following 1 DM 87179 - RMMobile prompts print giant SKIP button when using 0x20 modifier to put answers on next line (related DM#74074) ``` RMMobile_Android_v2.2.01_precut#2 --- ``` + Fixed the following 2 DM 87131 - Rmmobile -RTT/PRTT generates erroneous/blank messages which generate NULLPointerException error 78070 - Store all undelivered 'store-forward' messages on the device permanently. + fixed the issues with sending to RMGate failing ``` RMMobile_Android_v2.2.01_precut#1 --- ``` + Fixed the following 2 DM 87134 - Settings reported as unsaved when saving config screen 87147 - Encryption does not work when other bits are used ``` RMMobile_Android_v2.2.00 --- ``` + Removed "_precut#x" from version. + Fixed 86004 RMMobile defaults to 1 minute GPS reporting when delta time set to 0 minutes by RMGate + In case there was no "previous" GPS message sent, rmmobile would send out at least one GPSInfo message; just added to the check to do so only if deltaTime set > 0. ``` RMMobile_Android_v2.2.00_precut#14 --- ``` +Fixed the redraw issues on History screen +Removed Back button functionality on Driver Login screen +Removed Config functionality on Driver Login screen when Driver is on break +Fixed the scroll issue on the Send MSG tab +Fixed crashing on exit +Fixed Canceling a Defer payment +Fixed the following 1 DMs 81453 - RM Mobile - Resize data on the tablet screen. (RMGate 85961. other:79995,79997,80476,79999,79605,76886,80475,80671) +Fixed ET1 sizing issue ``` RMMobile_Android_v2.2.0_precut#13 --- ``` +Fixed ManifestHistory Paid value showing cents instead of dollars & cents +Merged Fare file into Config file per Dave's instruction that there be only one file +Fixed issue where recovering from crash displayed History left panel on Driver Login screen +Fixed issue where recovering from crash displayed Manifest left panel on Driver Login screen +Fixed the following 6 DMs 87045 - Group Arrive screen should only scroll and not check/uncheck trips unless the trip's checkbox is selected. +Fixed selection/scrolling issue so now the checkbox is the only element that determines selection 87078 - When using ADB capture bit files do not stop being written to 85576 - Store ListItemMessages locally (chained 82802, 82803, 78070) +added synchronization to encryption/decryption 86889 - RM Mobile - Fare Clicker screen scrolls to end of pane on scroll event 81453 - RM Mobile - Resize data on the tablet screen. (RMGate 85961. other:79995,79997,80476,79999,79605,76886,80475,80671) 87031 - Fix UI Components on the Configuration Screen ``` RMMobile_Android_v2.2.0_precut#12 --- ``` +Fixed issue with RMMobileFontResource +Fixed LeftPanel disappearing issues +UI tweaks +Fixed the following 5 DMs 81453 - RM Mobile - Resize data on the tablet screen. (RMGate 85961. other:79995,79997,80476,79999,79605,76886,80475,80671) 85866 - Vehicle is not reporting GPS often enough (~1 minute instead of 15 seconds) . 85576 - Store ListItemMessages locally (chained 82802, 82803, 78070) 86795 - Customer Name and Phone Number Labels overlap in Execute screen. 87031 - Fix UI Components on the Configuration Screen ``` RMMobile_Android_v2.2.0_precut#11 --- ``` + Fixed null pointer issue on DriverLogin screen + Fixed Configuration screen per Dave White's instruction + Fixed the following 8 DMs 86202 - Screen Blocker - display info from SELECTED stop, unless perform in order on (related DM# 78076 is original implementation) + Fixed off-by-one error 81453 - RM Mobile - Resize data on the tablet screen. (RMGate 85961. other:79995,79997,80476,79999,79605,76886,80475,80671) + Fixed ET1 font sizing issue 86970 - Move the Properties button on the Configuration screen 86975 - Customer Name and Phone Number Labels overlap in Execute screen. 86988 - Multiple Fareclicker screens not working when using comma 86137 - Remove duplicate Left Panels + Remove left panel on button press 86067 - History screen MUW layout should follow the Manifest List layout similar to DM#82002 in RMMobile_Android_v2.2.0_precut#6 + Added 1002 value to display the odometer 81446 RM Mobile - Group Arrive for trips (time and location based) (related 81904, 82521 - duplicate) ``` RMMobile_Android_v2.2.0_precut#10 --- ``` + Fixed the following 8 DM 81446 - RM Mobile - Group Arrive for trips (time and location based) (related 81904, 82521 - duplicate) 86137 - Remove duplicate Left Panels + Fixed issues listed at the top of the DM 81897 - RM Mobile - Trip should maintain highlight after 'Arrive' action allowing 'Depart' action of trip without reselection 86717 - Pre inspection screen in not coming up for the driver 86932 - RMMobile throws an error when deffering a payment for a trip 86202 - Screen Blocker - display info from SELECTED stop, unless perform in order on (related DM# 78076 is original implementation) + Corrected the index to work with performInOrder + Fixed the font size on the blocker screen 86475 - move settings screen into configuration screen. + fixed settings screen not updating properly to show configuration 82803 - Save State onPause - phase 2 (chained 82802) + moved call to load so that it actually loads MUWs now + added storage check for maintain history ``` RMMobile_Android_v2.2.0_precut#9 --- ``` + Fixed the following 8 DM 81446 - RM Mobile - Group Arrive for trips (time and location based) (related 81904, 82521 - duplicate) 82803 - Save State onPause - phase 2 (chained 82802) 86870 - Counter on fareclicker is too large 86672 - RMMobile occasionally experiences ArrayIndexOutofBoundsExceptions while loading manifest. 86858 - RMMobile 2.2 precut 8 settings screen radio buttons should not scroll. 86471 - inconsistent left panel label sizes on history and info screens 86445 - centralcontainers scroll off screen 86427 - android "back" button not supported ``` RMMobile_Android_v2.2.0_precut#8 --- ``` + Updated log bits in Readme + Removed test code that was creating multiple files + Fixed post merge issues + Fixed the following 20 DMs 85487 - NullPointException when Progress Dialog is cancelled 86718 - When logging in without any ID or PIN, the app takes you to a blank manifest instead of prompting you for credentials. 85393 - Remove extra scroll pane from Send MSG, MailBox, and History tabs 86634 - Possible to have incorrect left panel buttons on manifest screen. 86672 - "RMMobile occasionally experiences ArrayIndexOutofBoundsExceptions while loading manifest." Fixed using selected synchronization statements on involved objects. Believe I can prove within reasonable doubt that there is no potential for deadlock using my method 86614 - combobox menus do not size correctly, do not use correct font 86427 - android "back" button not supported 86569 - Various screens in RMMobile do not put their button in the left pane. 86475 - move settings screen into configuration screen. 86471 - inconsistent left panel label sizes on history and info screens. 86445 - centralcontainers scroll of screen 81893 - Fare Total Report on tablet 86839 - RMMobile java.lang.NullPointerException errors after extended use. + Added better logging and some code clean up/formatting 86675 - RMMobile errors out on the fareclicker screen when i use 15 or more fareclicker types 86725 - RMMobile crashes the first time it is launched after an update 86720 - Disclaimer seem to disappear before pressing okay 81446 - RM Mobile - Group Arrive for trips (time and location based) (related 81904, 82521 - duplicate) + Implemented the proper checks to prevent start/stop/pullin/pullout/breaks from triggering group arrive 82002 - RM Mobile - Ability to change column order on tablet (DM#81971, 81890, 83255 - Duplicate, 82801 - rmgate) + Fixed not reading from RMGate properly + Added precomputed sizes to loop indexes for better performance 86452 - RMMobile manifest refresh interrupts use of input prompts (i.e. fare clicker) (DM#86538 similar) + Redesigned the fix to be more simple 86067 - History screen MUW layout should follow the Manifest List layout similar to DM#82002 in RMMobile_Android_v2.2.0_precut#6 + Fixed what is reported to RMGate + Fixed null pointer exception due to improper order of operations + Changed calls to create renderers ``` RMMobile_Android_v2.2.0_precut#7 --- ``` + Fixed an issue with the Settings screen not calling save properly + Fixed the odometer display showing ellipses + Fixed an issue with the fare prompts screen + Fixed the following 6 DMs 86137 - Remove duplicate Left Panels + Fixed issue with Inspection Screen Left Panel 86067 - History screen MUW layout should follow the Manifest List layout similar to DM#82002 in RMMobile_Android_v2.2.0_precut#6 86095 - cannot use count#off without count#on FR.prompt - NULL value fails 83253 - RMMobile: Suggest Odometer reading to Driver based on previous day's odometer vaule for vehicle 86406 - Text on login buttons changes size after unsuccessful logon 86202 - Screen Blocker - display info from SELECTED stop, unless perform in order on (related DM# 78076 is original implementation) ``` RMMobile_Android_v2.2.0_precut#6 --- ``` + Fixed the following 5 DMs 82002 - RM Mobile - Ability to change column order on tablet (DM#81971, 81890, 83255 - Duplicate, 82801 - rmgate) 81446 - RM Mobile - Group Arrive for trips (time and location based) (related 81904, 82521 - duplicate) 86395 - RMMobile 2.2.0 precut #6 crashes on startup with ArrayIndexOutofBoundsException 81453 - RM Mobile - Resize data on the tablet screen. (RMGate 85961. other:79995,79997,80476,79999,79605,76886,80475,80671) + fixed checkboxes in the group arrive section 86137 - Remove duplicate Left Panels + fixed screen navigation on the Manifest screen + fixed screen navigation on the History screen + fixed all reported/noticed stability issues ``` RMMobile_Android_v2.2_precut#5 --- ``` + Logging current memory usage/heap utilized. + Fixed decimal keyboard entry/deletion + Fixed null pointer on virtual keyboard + Added new splash screen + Fixed problem with screen freeze when recovering from crash + Fixed DriverLoginScreen losing commands after going to Settings/Config/Help screens + Fixed the following (3) DMs 81453 - RM Mobile - Resize data on the tablet screen. (RMGate 85961. other:79995,79997,80476,79999,79605,76886,80475,80671) + fixed font sizes on smaller devices + fixed font sizes for auto sized central panel objects and for the summary screen 86137 - Remove duplicate Left Panels + added font scaling + fixed several issues of the buttons not working as intended + fixed null pointer when recieving message from dispatch 86124 - Put all clocks on the same timing thread. ``` RMMobile_Android_v2.2_precut#4 --- ``` + Removed RTT/PRTT Hardcoding + Made logging threaded + Fixed outboundmessagesender so it does not poll + Added names to threads to make debugging easier + Updated threads and thread names + Added border around MUWs + Fixed Keyboard UI + Fixed the following (16) DMs 85881 - Forward port changes from 2.1b into 2.2 81453 - RM Mobile - Resize data on the tablet screen. (RMGate 85961. other:79995,79997,80476,79999,79605,76886,80475,80671) 85967 - Add the connected/disconnected icon 81402 - RM Mobile - show address "Common Name" by default if address has common name (dm#82812 related - RMGate) 85880 - Fix logging to move check for valid log bits are outside of the call to log. 81446 - RM Mobile - Group Arrive for trips (time and location based) (related 81904, 82521 - duplicate) 85541 - Array index out of bounds error when only one prompt is sent 78070 - Store all undelivered 'store-forward' messages on the device permanently. 85618 - Move all File IO process into a background thread 82803 - Save State onPause - phase 2 (chained 82802) + works in conjunction with the 5 min time limit from 82802 85577 - Load configuration during SplashScreen 85576 - Store ListItemMessages locally (chained 82802, 82803, 78070) + sends CRC checksum to determine if the lists need to be downloaded at login 85562 - Fix RSA Encryption/Decryption for arrays larger than 117 bytes 83365 - Identify new or changed manifest lines by a color change or other indication + fixed remove from Detail Screen not working properly 85487 - NullPointException when Progress Dialog is cancelled 86004 - RMMobile defaults to 1 minute GPS reporting when delta time set to 0 minutes by RMGate 84893 - When Sygic is launched from RMMobile, no route is shown ``` RMMobile_Android_v2.2_precut#3 --- ``` + Forward ported the changes from 2.1a + Restored RTT/PRTT which were overwritten by the 2.1a ported changes + Fixed the following (14) DMs 83365 - Identify new or changed manifest lines by a color change or other indication 85450 - All logs purged on the first day of the month 80195 - Driver is not required to log in after break if device sleeps/awakened while on break. 83570 - Vehicle in Motion screen disappears if home or sleep button are pressed and then the user goes back to RMMobile. + added awkward menu click to remove the screen per Dave White's instruction 78076 - RM Mobile - Next stop information visible while vehicle is in motion (dm#82811 related - RMGate) 78071 - Screen lock when there is no GPS signal should be removed. 85411 - Selection needs contrast in Send MSG, MailBox, and History tabs + Also fixed the Info tab 85408 - Local/config to specify debug-cats to be written to log which are superseded by login response from rmgate. + fixed save/loading issue + fixed duplicate text and no Spanish translation + fixed not checking for null/empty string when pressing 'Save' button + fixed need for static references 85393 - Remove extra scroll pane from Send MSG, MailBox, and History tabs 85384 - Jump button is visible for a Dropoff after the Pickup has been completed 83254 - RMMobile: Flag or alert to Driver that Trip or Address has special notes 85352 - Create a larger contrast for a selected MUW 83065 - Jump button doesn't scroll screen to selected item nor highlight it to demonstrate that it is selected 85463 - Force screen on. ``` RMMobile_Android_v2.2_precut#2 --- ``` + Fixed the following (5) DMs 85218 - Pressing Back from the Fare Prompts Screen after a payment has been deferred will not allow the payment to be changed 85204 - Cancel button at the Fare Collected screen does not go back to the Fare Type screen as it should. 85215 - Back button on Fare Prompts Screen does not display the previous screen. 85196 - Null pointer exception when prompts are left blank 85195 - Defer button reports IndexArrayOutOfBounds Error ``` RMMobile_Android_v2.2_precut#1 --- ``` + Fixed the following (1) DMs 85179 - Implement RTT and PRTT on the Manifest Screen ``` RMMobile_Android_v2.1d --- ``` Removed "_precut#x" version. ``` RMMobile_Android_v2.1d_precut#1 --- ``` + Fixed the following DM(s): 86222 Stop Route item disappears from Manifest after Stop Run is processed (related DM#86275). ``` RMMobile_Android_v2.1c --- ``` Removed "_precut#x" version. ``` RMMobile_Android_v2.1c_precut#1 --- ``` + Fixed the following DM(s): 86088 RMMobile out of memory errors after extended use - Introduced debug bit 0x0000000000040000 // current memory/heap usage vs total allocated. ``` RMMobile_Android_v2.1b --- ``` Removed "_precut#x" post fix from version. ``` RMMobile_Android_v2.1b_precut#1 --- ``` + Fixed the following DM(s): 80864 RMMobile Application frequently closes requiring the driver to log back in. (Related 81150, 82293 duplicate The problem with all versions of rmmobile (android 2.1a and prior across all platforms) was that all 'end points' of 'manifest of work', i.e. 'stops', are stored in a (vanilla) binary search tree. And as the manifests would grow larger, the depth of the tree gets larger and not so feasible for recursive search/insert with a (Android's) stack size of only 8k. The problem of (a very skewed (aka linked list)) tree is magnified when all the completed stops are added (from the active tree which are already sorted) to the "history" tree, which results in the history tree simply as a linked list because there was no self balancing feature. The self balancing feature, i.e. making these binary trees as AVL tree is the major undertaking under thid DM. Added debug category 0x0000000000002000 // related to tree DS holding MUWs. 85801 Add adb log (capture) bit, when turned on, should write all the adb log to rmmobile log file. 0x0000000000010000 // capture adb log - BE VERY MIDFUL WHEN TURNING THIS ON AS IT RESULTS IN HUGE LOG FILE SIZE AND WILL INCUR SIGNIFICANT OVERHEAD; when turned on the deviceDebugToFile will write the android adb log to file. ``` RMMobile_Android_v2.1a --- ``` + Fixed the following (1) DMs 00000 - Removed precutX designation ``` RMMobile_Android_v2.1a_precut#3 --- ``` + Fixed/Organized the code regarding the Back button from the Fare Prompts Screen + Fixed the following (3) DMs 85256 - Back button does not work on the Fare Prompts Screen when performing a fixed route stop 85218 - Pressing Back from the Fare Prompts Screen after a payment has been deferred will not allow the payment to be changed 85215 - Back button on Fare Prompts Screen does not display the previous screen. ``` RMMobile_Android_v2.1a_precut#2 --- ``` + Fixed the following (3) DMs 85256 - Back button does not work on the Fare Prompts Screen when performing a fixed route stop 85255 - The central panel of the Manifest Screen should not be scrollable 85253 - The Defer button is present during DropOffDeparts ``` RMMobile_Android_v2.1a_precut#1 --- ``` + Fixed the following (5) DMs 85218 - Pressing Back from the Fare Prompts Screen after a payment has been deferred will not allow the payment to be changed 85204 - Cancel button at the Fare Collected screen does not go back to the Fare Type screen as it should. 85215 - Back button on Fare Prompts Screen does not display the previous screen. 85196 - Null pointer exception when prompts are left blank 85195 - Defer button reports IndexArrayOutOfBounds Error ``` RMMobile_Android_v2.1 --- ``` + Fixed the following (1) DMs 00000 - Removed precutX designation ``` RMMobile_Android_v2.1_precut#9 --- ``` + Fixed the following (1) DMs 85169 - Counter Prompt Item can have the value be deleted 85160 - Settings not loading properly + Copy and paste error resulted in odometer display using the hide map's value, fixed it so that the correct values are being used ``` RMMobile_Android_v2.1_precut#8 --- ``` + Fixed the following (1) DMs 85160 - Settings not loading properly ``` RMMobile_Android_v2.1_precut#7 --- ``` 85157 Reset udp datagram packet buffer to default size before receiving each packet. ``` RMMobile_Android_v2.1_precut#6 --- ``` + Turned off space testing for fare clicker screens (was accidentally left on during a test for Dale) + Added check that allows for empty strings to be set in fare clicker 85135 - Pressing 'Back' from the NoShow summary screen goes to PickupDepart's Prompt screen 85125 - Implement 0x40 bit for Prompt Items 83044 - Implement ResourceBundle to replace String initialization + Some translations were not correct for the given context + Some translations were missed 85078 - Updated "wait-indication" to Android 'DialogFragment' Improved display and dismissal of FragmentDialog based on the manifest update/status. ``` RMMobile_Android_v2.1_precut#5 --- ``` + Fixed the following (2) DMs 85078 - Updated "wait-indication" to Android 'DialogFragment' +previous fix required touch to dismiss dialog by adding another call to cancel the dialog when the total trips get updated +fixed dialog displaying during pre-inspection 85080 - Check for improper "configuration" improved. +previous fix only checked for null, added check for empty ``` RMMobile_Android_v2.1_precut#4 --- ``` RMmobile keystore was re-generated to sign RMMobile_Android.apk and that's why if a device has an earlier version of rmmobile, it needs to be uninstalled before installing the new one. Going forward, the certificate with rmmobile will remain the same and there won't be any signature/certificate conflicts which will allow a newer version to install over the previous one (without the need of removing it). + Fixed the following DMs 85078 - Updated "wait-indication" to Android 'DialogFragment' 85079 - Check for previously stored "settings" improved. 85080 - Check for improper "configuration" improved. ``` RMMobile_Android_v2.1_precut#3 --- ``` RMmobile keystore was generated to sign RMMobile_Android.apk and that's why if a device has an earlier version of rmmobile, it needs to be uninstalled before installing the new one. + Fixed the following DMs 84964 - Refresh manifest screen only if there is no immediate update to manifest with 'wait' notification when multiple updates. 84965 - Default logging on, until login dbg categories with rmgate login response is received. 84966 - Correct log folder destination so they can be purged properly. ``` RMMobile_Android_v2.1_precut#2 --- ``` + Fixed the following (7) DMs 84882 - Unable to enter values for Boarding/Alighting when performing a stop. 80335 - FEATURE REQUEST: Ability to enable\disable the map functionality in RMMobile 82943 - Fare deferral button is displayed in RMMobile when it is not defined in device characteristics 83544 - Canned Message list is blank on device when more than 38 are listed in the properties file + Added check for message size greater than the receive size 74074 - Develop Electronic Vehicle Inspection Form for RMMobile App (dm#74075 related, 82693 ,83368 dup) 84575 - Add device properties for the settings screen so that their values can be entered + Added hexadecimal entry field for the config settings screen device properties + Made checkboxes larger/easier to use 83044 - Implement ResourceBundle to replace String initialization + Updated missing texts, added Spanish, added Device Setting to allow for language selection ``` RMMobile_Android_v2.1_precut#1 --- ``` + Fixed the following (3) DMs 83044 - Implement ResourceBundle to replace String initialization 74074 - Develop Electronic Vehicle Inspection Form for RMMobile App (dm#74075 related, 82693 ,83368 dup) 83544 - Canned Message list is blank on device when more than 38 are listed in the properties file ``` RMMobile_Android_v2.0 --- ``` + Fixed the following (1) DMs 00000 - Removed precutX designation ``` RMMobile_Android_v2.0_precut#8 --- ``` + Fixed the following (1) DMs 84489 - Prompts using 2 columns do not scroll or draw properly when they go past the end of the screen ``` RMMobile_Android_v2.0_precut#7 --- ``` + Fixed the following (4) DMs 82343 - Support user field prompts on all 5 para trip states - fixed the back buttons not working correctly for all prompt types 84487 - RMMobile prompt 'go to a new page' syntax is not being obeyed 84486 - RMMobile 2.0 is sending decoiaml rather than integer when using count#(on) and count#(off) prompt types - fixed number type and width 84485 - Remove gradient from manifest screen on RMMobile - made the background be a few shades lighter to promote contrast ``` RMMobile_Android_v2.0_precut#6 --- ``` + Fixed the following 84485 - Remove gradient from manifest screen on RMMobile 80520 - RMMobile > Implement 'Fare Clicker' on RMMobile for Idaho and other fixed route sites (related 77358, 78077) - fixed sending extra subfields and zubfields and incorrect prompts 84476 - RMMobile 'fare clicker' summary screen does not scroll ``` RMMobile_Android_v2.0_precut#5 --- ``` + Fixed the following 80520 - RMMobile > Implement 'Fare Clicker' on RMMobile for Idaho and other fixed route sites (related 77358, 78077) - fixed prompts not sending answers ``` RMMobile_Android_v2.0_precut#4 --- ``` + Fixed the following 80520 - RMMobile > Implement 'Fare Clicker' on RMMobile for Idaho and other fixed route sites (related 77358, 78077) - resolved conflict introduced into fixed route depart ``` RMMobile_Android_v2.0_precut#3 --- ``` + Fixed the following 82934 - Provide method in RMMobile to call an offline navigation tool, such as Sygic, as an alternative to Google Nav (dm#83045 dup) 82343 - Support user field prompts on all 5 para trip states 84189 - Unable to enter odometer reading lower than estimated odometer 80520 - RMMobile > Implement 'Fare Clicker' on RMMobile for Idaho and other fixed route sites (related 77358, 78077) - fixed scroll display ``` RMMobile_Android_v2.0_precut#2 --- ``` + Fixed the following 80520 - RMMobile > Implement 'Fare Clicker' on RMMobile for Idaho and other fixed route sites (related 77358, 78077) - fixed route displaying prompts ``` RMMobile_Android_v2.0_precut#1 --- ``` + Code clean up/refactoring and removed dead/inaccessible code + Added ATM style entry method for monetary values + Fixed the following (2) DMs 82343 - Support user field prompts on all 5 para trip states 80520 - RMMobile > Implement 'Fare Clicker' on RMMobile for Idaho and other fixed route sites (related 77358, 78077) ``` RMMobile_Android_v1.9 --- ``` +Fixed the following (1) DMs 00000 - Removed the _precut#X designation ``` RMMobile_Android_v1.9_precut#3 --- ``` + Fixed issues introduced by the precut#2 merge as it overwrote some changes from precut#1 that prevented logging and changing settings ``` RMMobile_Android_v1.9_precut#2 --- ``` + Merged the code up from 1.8e ``` RMMobile_Android_v1.9_precut#1 --- ``` + Code clean up and refactoring + Fixed the following (1) DMs 81108 - Allow Assigning Wireless Devices to Drivers vs. Vehicles (RMMobile Work) (rel. RMTS#5.5.00 DM#80161; RMGate DM#81107) ``` RMMobile_Android_v1.8e --- ``` + Fixed the following (1) DMs 00000 - Removed the _precut#X designation ``` RMMobile_Android_v1.8e_precut#4 --- ``` + Fixed the following (1) DMs 83626 - Notification for dispatch messages and manifest update - fixed timing issue with displaying dispatch messages received while screen was off ``` RMMobile_Android_v1.8e_precut#3 --- ``` + Fixed the following (1) DMs 83626 - Notification for dispatch messages and manifest update - fixed break not being reported (introduced by this change in precut#2) and messages not displaying when resuming from sleep. ``` RMMobile_Android_v1.8e_precut#2 --- ``` + Fixed the following (1) DMs 83626 - Notification for dispatch messages and manifest update - reverted back to forms and removed the break screen ``` RMMobile_Android_v1.8e_precut#1 --- ``` + Code cleanup - fixed the Settings Screen persisting components, + Fixed the following (2) DMs 83626 - Notification for dispatch messages and manifest update - reverted back to dialog style to fix issue on break screen 82802 - Save State onPause - phase 1 (related 82803) - device was not logging out properly ``` RMMobile_Android_v1.8d --- ``` + Fixed the following (1) DMs 00000 - Removed the _precut#X designation ``` RMMobile_Android_v1.8d_precut#7 --- ``` + Fixed the following (1) DMs 83801 - Receiving error in RMGate around fldLatitude and fldLongitude ``` RMMobile_Android_v1.8d_precut#6 --- ``` + Code cleanup + Memory management + Fixed the following (2) DMs 83591 - Tenth place of odometer readings should be optional. 83630 - RMMobile crashes when screen is asleep and a message from dispatching comes in. ``` RMMobile_Android_v1.8d_precut#5 --- ``` + Code cleanup + Fixed the following (2) DMs 83630 - RMMobile crashes when screen is asleep and a message from dispatching comes in. 83570 - Vehicle in Motion screen disappears if home or sleep button are pressed and then the user goes back to RMMobile. ``` RMMobile_Android_v1.8d_precut#4 --- ``` + Fixed the following (3) DMs 83781 - Null Pointer Exception when canceling a no show 83591 - Tenth place of odometer readings should be optional. 83714 - Sizing issue with Galaxy Tab 7in ``` RMMobile_Android_v1.8d_precut#3 --- ``` + Fixed the following (4) DMs 83716 - Update driver odometer when returning from break 83714 - Sizing issue with Galaxy Tab 7in 83626 - Notification for dispatch messages and manifest update - fixed vehicle in motion handling and dismissing notifications when acknowledging the prompts 83227 - Messages sent from Dispatching to RMMobile gets lost if driver does not hit Dismiss and another message arrives. - Fixed an issue with the mailbox's delete ``` RMMobile_Android_v1.8d_precut#2 --- ``` + Fixed the following (2) DMs 82802 - Save State onPause - phase 1 (related 82803) - Display the splash screen during recover login 83626 - Notification for dispatch messages and manifest updates - made a single notification ``` RMMobile_Android_v1.8d_precut#1 --- ``` + Fixed the following (2) DMs 83626 - Notification for dispatch messages and manifest updates 83630 - RMMobile crashes when screen is asleep and a message from dispatching comes in. ``` RMMobile_Android_v1.8c --- ``` + Fixed the following (1) DMs 00000 - Removed the _precut#X designation ``` RMMobile_Android_v1.8c_precut#4 --- ``` + Fixed the following (1) DMs 80941 - Trip count inputting value from previous trip count ``` RMMobile_Android_v1.8c_precut#3 --- ``` + Fixed the following (1) DMs 81949 - Out of Bounds Exception Error on Tablet ``` RMMobile_Android_v1.8c_precut#2 --- ``` + Fixed the following (1) DMs 83547 - Manifest Screen requires switching tabs to update fix UI broken by DM#83389 ``` RMMobile_Android_v1.8c_precut#1 --- ``` + Fixed the following (2) DMs 83547 - Manifest Screen requires switching tabs to update fix UI broken by DM#83389 83488 - Pressing dismiss fails when adding/deleting trips or receiving messages from dispatching, when there are 2 messages left. ``` RMMobile_Android_v1.8b --- ``` + Fixed the following DMs 83389 - Galaxy 10.1 tablets, after Ice Cream Sandwich upgrade, have issues with RMMobile closing down. 83227 - Messages sent from Dispatching to RMMobile gets lost if driver does not hit Dismiss and another message arrives. ``` RMMobile_Android_v1.8a --- ``` + Fixed the following DMs 83389 - Galaxy 10.1 tablets, after Ice Cream Sandwich upgrade, have issues with RMMobile closing down. ``` RMMobile_Android_v1.8 --- ``` + Fixed the following DMs 00000 - Removed the '_precut#X' from the version identification. ``` RMMobile_Android_v1.8_precut#8 --- ``` + Fixed the following (1) DMs 83331 - Prompts that appear when 'vehicle in motion', disappear when vehicle stops without acknowledging ``` RMMobile_Android_v1.8_precut#7 --- ``` + Reverted DM#81108 - Allow Assigning Wireless Devices to Drivers vs. Vehicles (RMMobile Work) (rel. RMTS#5.5.00 DM#80161; RMGate DM#81107) to be implemented in a later version of RMMobile. + Fixed the following (2) DMs 82410 - Requested Time Window Display on Tablet Devices (dm#82799 related - RMGate) 83227 - Messages sent from Dispatching to RMMobile gets lost if driver does not hit Dismiss and another message arrives. ``` RMMobile_Android_v1.8_precut#6 --- ``` + Fixed the following (2) DMs 82998 - GzOne: Last trip cannot be seen properly on the Manifest screen. 83227 - Messages sent from Dispatching to RMMobile gets lost if driver does not hit Dismiss and another message arrives. ``` RMMobile_Android_v1.8_precut#5 --- ``` + Fixed the following (5) DMs 82410 - Requested Time Window Display on Tablet Devices (dm#82799 related - RMGate) 81108 - Allow Assigning Wireless Devices to Drivers vs. Vehicles (RMMobile Work) (rel. RMTS#5.5.00 DM#80161; RMGate DM#81107) 83227 - Messages sent from Dispatching to RMMobile gets lost if driver does not hit Dismiss and another message arrives. 80167 - Trip stays on manifest in RMMobile after it is "Cancelled" or "Reassigned" in the dispatching module in RMTS (81892 similar) 81892 - 'Stop Route' line of manifest does not move off after completion (80167 similar) ``` RMMobile_Android_v1.8_precut#4 --- ``` + Fixed the following DMs 82044 - Implement correct delta gps send behavior and improve the way odometer value is determined. (dm#82774 duplicate) Fixed conversion from yards to miles (for Imperial US) and yard to kms (for SI) when determining distance for auto odometer. ``` RMMobile_Android_v1.8_precut#3 --- ``` + Fixed the following (3) DMs 83227 - Messages sent from Dispatching to RMMobile gets lost if driver does not hit Dismiss and another message arrives. 82331 - Request to remove the tenth place of the odometer reading 82044 - Implement correct delta gps send behavior and improve the way odometer value is determined. (dm#82774 duplicate) Reference location to calculate the distance travelled wasn't properly set in v1.8 precut#2 and it is fixed here. ``` RMMobile_Android_v1.8_precut#2 --- ``` + General code clean-up, warning removal + Fixed the following (5) DMs 82044 - Implement correct delta gps send behavior and improve the way odometer value is determined. (dm#82774 duplicate) 83035 - Option to display times in RMMobile as PM times instead of military time (dm#81788, 82063 duplicate) 82331 - Request to remove the tenth place of the odometer reading (Missed two displays) 80002 - Replace cancel button with go back button (Missed two buttons) 81281 - Android --> Messages in RMMobile "Mail Box" are limited to 19 characters ``` RMMobile_Android_v1.8_precut#1 --- ``` + Fixed the following (10) DMs 81705 - Direction Value Not Being Sent w/ibGPSPositionReports 83035 - Option to display times in RMMobile as PM times instead of military time (dm#81788, 82063 duplicate) 82331 - Request to remove the tenth place of the odometer reading 80002 - Replace cancel button with go back button 82410 - Requested Time Window Display on Tablet Devices (dm#82799 related - RMGate) 83003 - Client name repeated in MUW detail screen 80479 - when using 'Up' 'Down' buttons while navigating from Odometer to PIN to ID the curser stays on PIN twice 81894 - Messages from Dispatch should appear in a different color 82904 - Fare screen - update Service Animal field to be same font size as other lines, and fix font size changing when selected 80466 - AndroidManifest.xml should use 'sensorLandscape' as opposed to 'landscape" ``` RMMobile_Android_v1.7 --- ``` + Touched up comments + Fixed the following DMs 00000 - Removed the '_precut#X' from the version identification. 78907 - Adding/Modifying/Cancelling trip popup does not give any relevant information (Tablet) (related DM 82080 - duplicate) 80477 - On the opening disclaimer screen the font changes after you tap ok and before screen advance to login ``` RMMobile_Android_v1.7_precut#13 --- ``` + Fixed the following DMs 82802 - Save State onPause -phase 1 (related 82803) ``` RMMobile_Android_v1.7_precut#12 --- ``` + Fixed the following DMs 82802 - Save State onPause - phase 1 (related 82803) ``` RMMobile_Android_v1.7_precut#11 --- ``` + Reverted 82832 Removed the singular clock + Fixed the following DMs 82908 - Going on break never sends OnBreak message 82905 - Jump button is not working correct in RMMobile 1.7 precut 10 82912 - MUW Selected / Total MUWs displays ellipses ``` RMMobile_Android_v1.7_precut#10 --- ``` + Reverted 80261 changes from precut#9 + Reverted 82852 changes from precut#9 + Fixed the following DMs 82883 - Rmmobile not sending prompt choice code field#10 in to rmgate 82760 - Out Of Memory Error occurs when sending messages from RMMobile and Dispatching is not able to see the message. 82832 - Fixed clocks shifting position 82802 - Save State onPause - phase 1 (related 82803) ``` RMMobile_Android_v1.7_precut#9 --- ``` + Fixed the following DMs 82852 - Add a Cancel button to the Fixed Route prompts 82847 - RMMobile Passenger Counter should default to a numeric keyboard. 80477 - On the opening disclaimer screen the font changes after you tap ok and before screen advance to login 79605 - Font size decreases when selecting a "No Show" option in RMMobile. (dm#82519 duplicate) 80261 - Screen information is not clearing from top row when different tab is selected 82832 - Missed a clock in the previous precut 81890 - Added display of city to the address line of MUWs on the manifest screen ``` RMMobile_Android_v1.7_precut#8 --- ``` + Added logging support for onPause + Fixed the following DMs 82802 - Save State onPause - phase 1 (related 82803) 82832 - Coalesce all clocks into one timer ``` RMMobile_Android_v1.7_precut#7 --- ``` + Fixed the following DMs 82714 - Fixed the fonts being too large inside buttons ``` RMMobile_Android_v1.7_precut#6 --- ``` + Fixed the following DMs 82714 - Fixed the phones and small screen devices having fonts too large ``` RMMobile_Android_v1.7_precut#5 --- ``` + Fixed the following DMs 80475 - Fixed picket-fencing for buttons that are selected/focused 82714 - Larger font size inside buttons 82702 - Fix very small button sizes 78907/82080 - Fixed Update not displaying the full message as Add/Remove does ``` RMMobile_Android_v1-7_precut#4 --- ``` + Cleaned up calls to logging - Dev use only + Fixed the following DMs 80941 - Trip count inputting value from previous trip count 78907/82080 - Fixed issue with remove from manifest not actually removing 81778 - Fixed Out of Memory Error on return from break ``` RMMobile_Android_v1-7_precut#3 --- ``` + Fixed an issue with the keystore not using the correct key, requiring an uninstall to upgrade ``` RMMobile_Android_v1-7_precut#2 --- ``` + Updated versioning to the 400 series due to the code version being derived off of RMP which is currently (6/27/2012) RMPv0.4 compatible + Fixed the following DMs 81778 - Fixed Out of Memory Error on return from break 82271 - Preserve ID/PIN on return from break 82581 - Cleanup calls to Debug - Dev use only 78907/82080 - Full client info during add/remove 82043 - Preserve config settings across uninstall/reinstall ``` RMMobile_Android_v1-7_precut#1 --- ``` + Fixed following DMs 80486 Tabs on the manifest screen now have consistent capitalization 82514 Fonts now set to scale dependent on resolution, this is a precursor to further device size dependent formatting 82485 Fonts now have an option to be set to a standard point size, or scaled with respect to the screen resolution, currently this option is only available to developers 82512 The Manifest Screen now occupies all screen real estate, and the entire screen will not be scrolled, just the stops 81978 Faretype now defaults to the type set in TS, the default will be the first option if no faretype is set (in most cases this will be Cash) 79996 Faretype now creates multiple columns dependent on the number of rows reaching/exceeding the screen size ``` RMMobile_Android_v1-6 --- ``` + Fixes follwing DMs 00000 Remove 'precut#x' when identifying version of the app. ``` RMMobile_Android_v1-6_precut#6 --- ``` + Fixes follwing DMs 82441 RMMobile crashes when list message types included in login response are of unexpected structure. ``` RMMobile_Android_v1-6_precut#5 --- ``` Improved memory management through out the application and fixed possible deadlock in communication threads. + Fixes follwing DMs 82430 Clean up departure data (summary) screen after prompts entry. 82431 Logging bits shouldn't be on by default when running against pre rmgate v5.3 precut#3 ``` RMMobile_Android_v1-6_precut#4 --- ``` + Fixes follwing DMs 81668 RMMobile Logging > Create first revision of data logging of RMMobile app on device. 78911 Clicking in field to enter a number causes the cursor to go to the beginning of the number (82112, 79998, 82332 - duplicates) 81091 RMMobile Alerting > Audible alerts for all pop up messages (dm 82078 is duplicate) 82382 Change Alert Display for TTL NOTE: DM#81668 RMMobile Logging > Create first revision of data logging of RMMobile app on device, along with fix of DM# 78438 Implement support for prompts(regardless if MUW is fixed or para) to inquire rider demographic, make RMMobile_Android RMPv0.4 compatible. ``` RMMobile_Android_v1-6_precut#3 --- ``` + Fixes follwing DMs 78438 Implement support for prompts(regardless if MUW is fixed or para) to inquire rider demographic. Submit on departure detail screen includes the entered/selected value in the field 10 for the trip status change message, inbound to RMGate. ``` RMMobile_Android_v1-6_precut#2 --- ``` + Fixes follwing DMs 78438 Implement support for prompts(regardless if MUW is fixed or para) to inquire rider demographic. RMGate v5.3_precut#1 is required and RMMobile as of this release only caters to prompt.definition.4 and for pickup.depart.prompts. So properties are set so that the picklist is set by setting the following property in RMGate: xxxx.prompt.definition.4 = (trip#ufld01) {PICKLIST, red, blue, green} my field value 1 and pickup depart prompt is set to this prompt (i.e. 4) xxxx.pickup.depart.prompts = 4 ``` RMMobile_Android_v1-6_precut#1 --- ``` + Fixes follwing DMs 78438 Implement support for prompts(regardless if MUW is fixed or para) to inquire rider demographic. First shot at RMPv0.4 which introduces sub-subfieldd (zub fields). As of this release only PRMTYPE_ANSWERFORMAT_PICKLIST (i.e. combo box) is properly processed by RMMobile. And it is added to support feature requested by MN_AEOA to gather rider demographic information. ``` RMMobile_Android_v1-5 --- ``` + Fixes follwing DMs 00000 Remove precut from login message and system info screens. ``` RMMobile_Android_v1-5_precut#7 --- ``` + Fixes follwing DMs 00000 Add more debug statements and remove (debug) communication failure alerts. ``` RMMobile_Android_v1-5_precut#6 --- ``` + Fixes follwing DMs 81790 Screen lock is not required when speed threshold from RMGate is 999. ``` RMMobile_Android_v1-5_precut#5 --- ``` + Fixes follwing DMs 81780 RMMobile should exhibit legacy behavior (pre RMPv0.3) in locking screen if RMGate is pre RMPv0.3 81781 Speed and direction values shouldn't be sent (Instead of sending '0') when no GPS fix is obtained. ``` RMMobile_Android_v1-5_precut#4 --- ``` + Fixes follwing DMs 81770 Improve acquiring best GPS fix ``` RMMobile_Android_v1-5_precut#3 --- ``` Implemented RMPv0.3. Enhanced DM#81690: Setting device property to 1000 will set all outbound data from RMMobile to be in SI(metric) units and is sent out with the x40 bit on, in Header info. And in case any data is received from RMGate without x40 bit on (implying the data sent from RMGate is in Imperial(US)), it will be convereted to SI before processing. In addition, odometer fields has the unit (miles|km) appended to them for clarity and notification. + Fixes follwing DMs 80962 Customizable and configurable "Vehicle In Motion" settings for RMMobile devices Screen lock threshold speed is received by RMMobile as login response from RMGate. In case it's 999, screen shouldn't be locked. 81765 Confidence interval for GPS data. Confidence interval value is received as a login response, and it is discarded (i.e. GPS data will always be sent) if the value received is 0 ``` RMMobile_Android_v1-5_precut#2 --- ``` + Fixes follwing DMs 81690 [AU_TransitCare] Require GPS Odometer Calculation in Kilometers ``` RMMobile_Android_v1-4 --- ``` + Fixes follwing DMs 00000 Remove precut from System Info screen and login message. ``` RMMobile_Android_v1-4_precut#13 --- ``` + Fixes follwing DMs 80165 Prompts that appear when 'vehicle in motion', disappear when vehicle stops without acknowledging ``` RMMobile_Android_v1-4_precut#12 --- ``` + Fixes follwing DMs 80165 Prompts that appear when 'vehicle in motion', disappear when vehicle stops without acknowledging 80185 Remove java.lang error when choosing 'Detail' or 'Jump' on empty manifest 80370 Device property for emulated GPS ``` RMMobile_Android_v1-4_precut#11 --- ``` + Fixes follwing DMs 80371 Device property for developers to expedite debugging. ``` RMMobile_Android_v1-4_precut#10 --- ``` + Fixes follwing DMs 80183 Screen information is not clearing when different tab is selected 80245 Config setting to use either "current location"( thru cell tower/wifi) or stop's location, in case satellite GPS is unavailable ``` RMMobile_Android_v1-4_precut#9 --- ``` + Fixes follwing DMs 80185 Remove java.lang error when choosing 'Detail' or 'Jump' on empty manifest 80199 Buttons in MAP tab to place Copy-Addr and Copy-GPS to place the selected stop's address/gps on clipboard. 80200 Google maps/navigation should be invoked with correct address/gps format. 80201 In case gps can't be determined, coordinates of last completed or previous trip in the manifest should be used. ``` RMMobile_Android_v1-4_precut#8 --- ``` + Fixes follwing DMs 80166 Invoke Google maps->navigation from RMMobile when navigation is selected under MAP tab. 81063 Moving a trip to vehicle then removing it causes error ``` RMMobile_Android_v1-4_precut#7 --- ``` + Fixes follwing DMs 80156 All ACKs (even the ones for already received messages) should be encrypted. ``` RMMobile_Android_v1-4_precut#6 --- ``` + Fixes follwing DMs 80112 Synchronize manifest list/table so network update and view threads dont interfere when acessing/updating 79903 Drivers getting logged out of RMMobile when screen locks ``` RMMobile_Android_v1-4_precut#5 --- ``` + Fixes follwing DMs 80112 Error on device when removing a previously added trip from vehicle. 80117 Android App crashes after information is sent to device > device 'sleeps' and is 'awakened' ``` RMMobile_Android_v1-4_precut#4 --- ``` + Fixes follwing DMs 80108 RMMOBILE device properties defaults to value 100 after restarting application. ``` RMMobile_Android_v1-4_precut#3 --- ``` + Fixes follwing DMs 80059 RMMobile is not encrypting ACKs when the encryption bit is on. 80060 Configuration settings should be stored permanently. 80061 RMMobile device properties should be added to configuration settings. ``` RMMobile_Android_v1-4_precut#1 --- ``` + Fixes follwing DMs 77999 Update RMMoble to satisfy Federal FIPS 140-2 Encryption Requirements. ``` RMMobile_Android_v1-3c --- ``` + Fixes follwing DMs 79774 RMMobile should check for inaccurate GPS coordinates in addition to "Accuracy" provided by API. ``` RMMobile_Android_v1-3b --- ``` + Fixes follwing DMs 79280 Odometer value should be determined through GPS data. NOTE: DM#79280 was marked fixed in v1.3a, however, an issue was introduced in v1.3a which disabled the manual entry/update of odometer; this side effect is fixed in v1.3b. Please also note that no new DMs were created and history of DM79280 and RMMobile's readme are updated accordingly. ``` RMMobile_Android_v1-3a --- ``` + Fixes follwing DMs 79280 Odometer value should be determined through GPS data. ``` RMMobile_Android_v1-3 --- ``` + Fixes follwing DMs 79268 Alerts that result due to dispatch messages to driver which do not require a response, are not dismissed properly. 00000 Remove _precut#x from SystemInfo and login message to RMGate. ``` RMMobile_Android_v1-3_precut#6 --- ``` + Fixes follwing DMs 79268 Enlarge Numeric Keyboard Buttons 79551 Delete in mailbox screen should delete the selection 79552 Response to the dispatch message requesting a response "Yes/No" should correspond with the button selected. ``` RMMobile_Android_v1-3_precut#5 --- ``` + Fixes follwing DMs 79284 User shouldn't have to press "ok" on the virtual keyboard to make a change last in text field ``` RMMobile_Android_v1-3_precut#4 --- ``` + Fixes follwing DMs 78904 An error occurs when using "Jump" button on a "Dropoff" that the "Pickup" has already been completed ``` RMMobile_Android_v1-3_precut#3 --- ``` + Fixes follwing DMs 79277 All prompts, popups, alerts should have larger sized buttons 79278 RMMobile_Android should be RMPv0.2 compatible. 79280 Odometer value should be determined through GPS data. 79408 Add scroll buttons to assist in navigation between input fields of Login scren. ``` RMMobile_Android_v1-3_precut#2 --- ``` + Fixes follwing DMs 78902 All pop-up boxes should have a button(s) to react to that pop-up box, whether it be a close button, yes/no, 'OK', etc. 78896 Driver should be able to send "Break" message to dispatch. 78897 Driver should be able to get RMMobile in "Emergency" mode. ``` RMMobile_Android_v1-3_precut#1 --- ``` + Fixes follwing DMs 78915 RMMobile_Android on the tablets should only have landscape view. 78947 Stop detail screen should be able to span over multiple screens. 78903 Length of the manifest changes after a pickup or dropoff is executed NOTE: Although prompts and other Fixed Route related UI changes (prompts etc) are not ported to the "Ranger like touchscreen UI" of Android tablets; the RMMobile_Android_v1-3_precut#1 supports RMPv0.2 so this precut can be used to show case download offixed route manifest on Android tablets. ``` RMMobile_Android_v1-2 --- ``` Remove "precut_#" from System Info screen. ``` RMMobile_Android_v1-2_precut#4 --- ``` + Fixes follwing DMs 78852 Manifest history tab should be properly populated with the completed trips. ``` RMMobile_Android_v1-2_precut#3 --- ``` General UI improvement and designing the interface more like that of Ranger's. + Fixes follwing DMs 78851 Retain correct focus of the selected item when navigated to and from the main manifest screen. ``` RMMobile_Android_v1-2_precut#2 --- ``` + Fixes follwing DMs 78653 RMMobile_Android should support Ranger like touchscreen UI. ``` RMMobile_Android_v1-2_precut#1 --- ``` + Fixes follwing DMs 78548 Touch screen interface for select screens. ``` RMMobile_Android_v1-1a --- ``` + Fixes follwing DMs 78312 FRPrompts when set to "none" are not handled properly. 78313 Problem displaying stop detail screen. ``` RMMobile_Android_v1-1 --- ``` + Fixes follwing DMs 00000 Remove precut from App Version and increment code version. ``` RMMobile_Android_v1-1_precut#3 --- ``` + Fixes follwing DMs 78084 Increase size of the fonts in the message window ``` RMMobile_Android_v1-1_precut#2 --- ``` + Fixes follwing DMs 78065 Add support for 'Extra Title' and 'Extra Data' when the 'No Detail' bit is on. 78018 Manifest and other screens should have larger font. ``` RMMobile_Android_v1-1_precut#1 --- ``` + Fixes follwing DMs 77974 Support basic fixed route functionality and compatibility with v0.2 of RMP. ``` RMMobile_Android_v1-0 --- ``` + Fixes follwing DMs 00000 Application version 1.0; removed precut. ``` RMMobile_Android_v1-0_precut#3 --- ``` + Fixes follwing DMs 77343 Mail box should be properly populated with inbound/oubound messages. 77344 Default select command's text should be replaced by "fire"; J2ME terminology - 3rd softkey ``` RMMobile_Android_v1-0_precut#2 --- ``` + Fixes follwing DMs 76884 Permanent storage interface on Android platform (SQLite) so information can be store on the device. 77229 Exit from RMMobile should result in sending Signoff message to RMGate 77230 Sending out canned messages should be possible 77231 Textfields restricted with numeric input should only have numeric keyboard ``` RMMobile_Android_v1-0_precut#1 --- ``` + Fixes follwing DMs 76883 GPS receiver interface to determine GPS data on Android device. 76885 Device's motion (tilt, shaking etc) sensors should be properly handled and UI should respond accordingly 76888 Investigate inbound message listener thread hang-up. 76894 Touch screen input keyboard(s) should be appropriately sized and easy to use. ``` RMMobile_Android_V1-0_precut#0.1 --- ``` - It is precut#0.1 because it is just a prototype and it is not delivered to QA to test. precut#1 will be released once RMMobile's code is refactored to have multiple layers to accommodate different devices and platforms. RMMobile code will then essentially be a unified-base code which would allow mix-and-match to build for different devices and platforms. - precut#0.1 is able to successfully login to RMGate and download a manifest. Additionally, various manifest operations can also be performed. - It should be noted that neither GPS data is calculated on precut#0.1 nor any data is stored on the handset permanently. ```