- Created by Michelle Cabaya on Aug 23, 2018
You are viewing an old version of this page. View the current version.
Compare with Current View Version History
Version 1 Next »
Three tips to help choose mobile devices that are right for you.
- When considering hardware devices for X Mobile, be sure to obtain a test/demo unit from your provider. Only after testing specific units and observing firsthand how X Mobile performs on the devices should customers consider purchasing those units. Be sure to complete your device testing within your provider's return/cancellation policy period.
- All devices, especially Android devices, vary in form, weight, connectivity, resolution, performance, and reliability. Keep in mind that open-source operating systems such as Android can be modified by device manufacturers, therefore customers should not assume consistency between devices running the same Android version.
- CXT Software tests and confirms compatibility levels on each device at the time we receive them. Since we can only test the current system software when the device is received, we're not able to guarantee compatibility of updated operating systems. Firmware and/or operating system changes can alter operating behavior over the life of a hardware device.
(Please make sure to read the "Compatibility Testing Results" and note the OS version and any Comments applicable to the devices you're considering.)
*** IMPORTANT NOTE REGARDING BLUETOOTH SCANNERS ***
CXT Software strongly recommends that customers select devices indicated as having "Excellent Compatibility" 
with X Mobile for dock or mission-critical barcode scanning. For light-duty scanning, the Bluetooth scanners listed below may provide good results with specific Android devices. Due to the large number of available Android devices as well as the variability in Bluetooth support on those devices, customers MUST test Bluetooth scanner and Android device combinations before deploying them to drivers. Customers cannot assume that any Bluetooth scanner will pair reliably with any Android device. CXT Software does not test Bluetooth scanners with all Android devices compatible with X Mobile.
| Scanner | Compatibility | Interface | Ruggedized | |
|---|---|---|---|---|
| Cipher Labs 1660 | | Bluetooth |  | References Comments
Test Results When I initially started testing the unit I first had to pair the unit. This requires that both your Android device and the scanner are in pairing mode. Once they were both in pairing mode the scanner came with these barcode sheets which I scanned that set the passcode to "0000". I was then prompted on the Android device to enter the pairing code "0000". Once I entered the code the device was successfully paired. After pairing was completed I then launched GetBlue and changed my Datasource to BlueTooth which then triggered GetBlue to try and connect to the scanner. Once GetBlue was connected I was able to scan a barcode and see the input being passed into X Mobile. The scanner has dozens of settings that customers will have to navigate on their own as we won't be able to provide support for the devices multiple configuration options. If customers have issues with the device they should start over, this requires the device be reset to defaults, re-paired, and then tested to confirm functionality. The device puts it'self to sleep after approximately 20 minutes of inactivity. Once this happens the user will have to press the power button and wait for the scanner to re-establish communication with the Android device. This process takes about 10 - 30 seconds and seemed to work 5 out of the 5 times I tested resuming from sleep. The scanning quality of this device seemed significantly lower than a dedicated all in one scanner such as the Intermec CN50 or Motorola MC65. The scanners recognition at times took multiple attempts to read barcodes. I would consider this a low-end economy scanner since its recognition was substantially slower and less accurate at times than higher end all in one devices. The device has a single light which from what I saw can change to Blue, Red, and Green. When the device recognizes a barcode the status light appears to flash green momentarily and the unit makes a single beep. The beeping of the unit will most likely cause confusion for drivers since they might be inclined to believe that because the barcode scanner beeped, that they scanned the correct barcode. I couldn't determine if there was a way to disable the acquisition beep on the scanner, but customers should definitely train drivers to ignore the scanner beep and only listen to the X Mobile beeps. The devices manufacturer page indicates the unit should last all day however this might be inconvenient since the batteries would have to be charged daily. My test unit has "NO USB" (1660) connection so charging is only possible by removing the two triple A batteries that power the unit. According to the manufacturer's site it appears there might be two versions of this unit for sale the 1660 and 1661. The one I tested has the two blue buttons on the top (1660). http://www.cipherlab.com/catalog.asp?CatID=8&SubcatID=11&ProdID=469 The last thing to note is that since both the power and scan button are on the same surface it's going to be very common for customers to press the power button instead of the scan button possibly shutting the device off when they're intending to scan a barcode. I don't like this design aspect and I would have put the power button somewhere besides right next to the scan button. Overall the device seems like it will do fine for light duty scanning and will require that customers familiarize themselves in depth with maintaining a Bluetooth connection between their devices. The unit will also require that drivers have some spare batteries since the 1660 unit has no way to charge the batteries. One caveat is that the batteries are triple A and they could be purchased at almost any gas station. Est. Mfg. Date: 2011 |
| Motorola CS3070 | | Bluetooth |  | References Comments
Test Results Steps taken to test:
Est. Mfg. Date: 2011 |
| Serial IO KDC200 |  | Bluetooth | | References Comments
Test Results When I initially started testing the unit I first had to pair the unit. This requires that both your Android device and the scanner are in pairing mode. Once the device had been paired, the GetBlue application needs to be configured to use this device to capture barcode scan data. GetBlue is able to be configured to use this device, however, since the device has issues staying paired, GetBlue was not able to stay connected to the device in order to be able to capture barcode scan data. Est. Mfg. Date: Unknown |
| Serial IO Scanfob® 2002 | | Bluetooth | | References Comments
Test Results When I initially started testing the unit I first had to pair the unit. This requires that both your Android device and the scanner are in pairing mode. The device can be set to Pairing Mode by either scanning the Start Pairing barcode or by pressing and holding a small button on the unit. This unit was never recognized by the Android device and could not be paired. If the device cannot be paired with a device, you will not be able to use it to scan. Tried to pair this device with different Android devices, however, I encountered the same pairing issue. Est. Mfg. Date: 2002 |
| Socket Mobile CHS 7P (CX2862-1298) | | Bluetooth | | References Comments
Test Results Steps taken to test:
Est. Mfg. Date: 2011 |
| Socket Mobile CHS 7Xi (CX2864-1336) | | Bluetooth | | References Comments
Test Results Steps taken to test:
Est. Mfg. Date: 2011 |
| Unitech MS910 | | Bluetooth | | References Comments
Test Results
Est. Mfg. Date: 2012 |
Compatibility:
| OS:
| Ruggedized:
| Cell Carriers:
| X Mobile Features:
|
|---|
|
|
|
|
|
| |
|---|---|---|---|---|---|---|
| Alcatel OneTouch Evolve 5020T |
|
|
|
|
| Comments
Compatibility Testing Results
References Est. Mfg. Date 10/01/2013-Current as of 7/1/2014 |
| Alcatel Verizon Ellipsis |  |
| |
|       | Comments
Compatibility Testing Results
References |
| Apple iPhone |
|
| |
|
| Comments All Apple products are unsupported.. "they don't work" with X Mobile References Est. Mfg. Date 2007 - Current |
| Asus Nexus 7 (Tablet) | |  | |
| | Comments
Compatibility Testing Results
Tested with 2000 X Dispatch parcels, no problems at all, took less than ten seconds to process. Tested with 2000 X Route parcels, no problems at all, but took a little longer to process about 30 seconds. References Est. Mfg. Date 2012 |
| Casio Commando | |
| |  | | Comments
Compatibility Testing Results This device is very rugged and would be a good device for delivery use since it's water, dust, and shock resistant.
References Est. Mfg. Date 2011 |
| Cipher Labs CP45 | |
| |
|
| Comments
Compatibility Testing Results
References Est. Mfg. Date 2012 |
| Cipher Labs RS30 | | | |  | References | |
| Honeywell CT 50 | | | | | Comments Required build number * or higher to use the scanner. The device must have the "Scan to Intent" option under scanner settings, and be enabled, to scan parcels. Compatibility Testing Results
References | |
| Honeywell Dolphin 6000 | |  | |
| | Comments Honeywell Dolphin 6000 URL: http://www.honeywellaidc.com/en-US/Pages/Product.aspx?category=Scanphone&cat=HSM&pid=Dolphin6000 Recommended Vendor Compatibility Testing Results ** This device has low volume in X Mobile which can't be adjusted. Est. Mfg. Date 2011 |
| Honeywell Dolphin 70e Black | | | |
| | Comments
Compatibility Testing Results
References Est. Mfg. Date 10/23/12 |
| Honeywell Dolphin 7600 II | | | |   | | Comments
Compatibility Testing Results
References Est. Mfg. Date 2009 |
| HTC Droid Incredible 2 | | | | | | Comments
Compatibility Testing Results ** The virtual keyboard doesn't work in Landscape mode at the time of this writing. The keyboard also randomly stops accepting input and requires a quick hop from X Mobile to the home screen and back to enable the keyboard again.
References Est. Mfg. Date 2011 |
| HTC EVO 3D (X515a) | | | |  |       | Comments
Compatibility Testing Results
Build 168 REV 20547 "HIGH" Resolution JVM was used for testing. The device was running Android 2.3.4 References Est. Mfg. Date 2011 |
| HTC EVO Shift 4G | | | |  | | Comments
Compatibility Testing Results
References Est. Mfg. Date 2010 |
| HTC Evo View 4G Tablet | | | | | | Comments
Compatibility Testing Results
References Est. Mfg. Date 2011 |
| HTC Fuze | | | | |
| References |
| HTC G2 | | | | | | Comments
References Est. Mfg. Date 2010 |
| HTC Inspire 4G | | | | | | Comments
Compatibility Testing Results ** The virtual keyboard doesn't work in Landscape mode at the time of this writing. The keyboard also randomly stops accepting input and requires a quick hop from X Mobile to the home screen and back to enable the keyboard again.
References Est. Mfg. Date 2011 |
| HTC My Touch 4G | | | | | | Comments
References Est. Mfg. Date 2010 |
| HTC One V | | | |
| | Comments
Compatibility Testing Results
References Est. Mfg. Date 2012 |
| HTC PPC 6700 | | | |
| | References |
| HTC Raider (X710a) | | | |
| | Comments Because of all the issues listed in the "Compatibility Testing Results", this device is listed as "Not Compatible". Compatibility Testing Results
Build 168 REV 20547 "HIGH" Resolution JVM was used for testing. The device was running Android 2.3.4 References Est. Mfg. Date 2011 |
| HTC Tilt | | | | | | References |
| HTC Tilt2 | | | | | | Comments ** This device is not a rugged device and anyone purchasing this device needs to make sure they fully understand that this device will be less forgiving to abuse. References |
| HTC Touch Pro | | | | | | References |
| HTC Touch Pro2 | | | | | | Comments ** This device is not a rugged device and anyone purchasing this device needs to make sure they fully understand that this device will be less forgiving to abuse. References Est. Mfg. Date Discontinued. |
| HTC Trinity | | | | | | References |
| HTC Wing | | | | | | Comments |
| HTC Wizard | | | | | | References |
| HTC XV6700 | | | | | | References |
| HTC XV6800 | | | | | | References |
| HTC XV6900 | | | |
| | References |
| Intermec CN3 | | | | | | References Recommended Vendor Est. Mfg. Date 2006 |
| Intermec CN50 | | | | | | Comments
Compatibility Testing Results
** The speaker is a little weak on the CN50. Sound volume should be maximized to hear all audio alerts. References Recommended Vendor Est. Mfg. Date 2009 |
| Intermec CN51 (Android) | | | | | | References Est. Mfg. Date 2014 |
| Intermec CN70 | | | | | | Comments
Compatibility Testing Results The device was remarkably accurate with hard to read bar codes and time to scan acquisition was almost instantaneous. GPS settings on the Intermec CN70 are as follows:
Test using X Mobile 12.1.2 and Option 1 JVM References Recommended Vendor Est. Mfg. Date 2011 |
| Intermec CS40 | | | |
| | References Recommended Vendor Est. Mfg. Date 2010 |
| Kyocera Brigadier | | | | | | Comments Phone tested on X Mobile 14.3 with Hi Res JVM. Compatibility Testing Results
References Est. Mfg. Date 2014 |
| Kyocera DuraCore | | | | | | Comments ** This device is not compatible with X Mobile because it doesn't run either Android or Windows Mobile as it's operating system. ** Compatibility Testing Results ** This device is not compatible with X Mobile because it doesn't run either Android or Windows Mobile as it's operating system. ** References |
| Kyocera Duraforce | | | | | | Comments Tested on X Mobile 14.2.2 with JVM - High Resolution (Build: 8/15/2013) Compatibility Testing Results ***The device performed all major function of the compatibility test. ***
References |
| Kyocera DuraMax | | | | | | Comments ** This device is not compatible with X Mobile because it doesn't run either Android or Windows Mobile as it's operating system. ** Compatibility Testing Results ** This device is not compatible with X Mobile because it doesn't run either Android or Windows Mobile as it's operating system. ** References Est. Mfg. Date 2011 |
| Kyocera Duralus | | | | | | Comments This device is very rugged and meets the military specification 810G, which makes it resistant to dust, extreme temperatures, low pressure, rain, salt fog, shock, and vibration. It can also be submerged in up to 3 feet of water for 30 minutes. Compatibility Testing Results
X Mobile 12.0.0 Rev A References Est. Mfg. Date 2011 |
| Kyocera Echo (SCP9300KIT) | | | | | | Comments **As with all Android apps, X Mobile must be running in the foreground to prevent Android from closing it to free memory. **
Compatibility Testing Results
Overall the device has a quick processor and seems responsive to physical and touchscreen input. The device runs a highly customized version of Android 2.2, and the dual screens cannot be used for X Mobile. There are a limited number of applications that can support the dual screens as it's not a standard Android code base. This could prove to be a significant drawback if a future build of Android renders X Mobile unstable on this device. References Est. Mfg. Date 2011 |
| Kyocera Hydro Xtrm/ (C6522) | | | | | | Comments
Compatibility Testing Results ***X Mobile would crash frequently during heavy use throughout different areas of X Mobile.
References |
| Kyocera Rise (C5155) | | | | | | Comments ** As with all Android apps, X Mobile must be running in the foreground to prevent Android from closing it to free memory. **
Compatibility Testing Results
Device Info
X Mobile Info
On Demand Orders
Routed Work
BOL
Device
References Est. Mfg. Date 2012 |
| Kyocera Torque | | | | | | Comments ** As with all Android apps, X Mobile must be running in the foreground to prevent Android from closing it to free memory. **
Compatibility Testing Results
References Recommended Vendor Est. Mfg. Date 2013 |
| LG Enlighten (VS700) | | | | | | Comments ** X Mobile must be running in the foreground, otherwise, it may be closed unexpectedly **
Compatibility Testing Results ** This device was 4 times slower creating 2000 parcels than the Samsung Stratosphere **
Build 168 REV 20547 "LOW" Resolution JVM was used for testing. The device was running Android 2.3.4 References Est. Mfg. Date 2011 |
| LG Fathom (VS750) | | | | | | Comments In our testing of the LG Fathom (VS750) on the Verizon network, we found the GPS reception to be poor, but it does work. We are happy to say this is the first Windows Mobile smartphone from Verizon that we have seen where the GPS was accessible by X Mobile without needing to apply aftermarket hacks to unlock it. It is worth noting, however, the GPS on this device did not work out of the box with X Mobile. We'll be writing a knowledge base article soon on how to enable GPS to work on this device. References Est. Mfg. Date Discontinued. |
| LG G Pad 7 | | | | | | Comments "Capture Image" function does not work on this device, X Mobile will crash if the feature is used. Compatibility Testing Results
References |
| LG G Vista LG-VS880 | | | | | | References |
| LG G2X | | | | | | Comments ** As with all Android apps, X Mobile must be running in the foreground to prevent Android from closing it to free memory. **
Compatibility Testing Results
References Est. Mfg. Date 2011 |
| LG Optimus S | | | | | | Comments ** As with all Android apps, X Mobile must be running in the foreground to prevent Android from closing it to free memory. **
Compatibility Testing Results
References Est. Mfg. Date 2011 |
| LG Vortex (VS660) | | | | | | Comments ** As with all Android apps, X Mobile must be running in the foreground to prevent Android from closing it to free memory. **
Compatibility Testing Results
References Est. Mfg. Date Discontinued. |
| Motorola Admiral (XT603) | | | | | | Comments ** As with all Android apps, X Mobile must be running in the foreground to prevent Android from closing it to free memory. **
Compatibility Testing Results
Build 168 REV 20547 "HIGH" Resolution JVM was used for testing. Device was running Android 2.3.5.3 References Recommended Vendor Est. Mfg. Date 2011 |
| Motorola Atrix 2 (MB865) | | | | | | Comments ** As with all Android apps, X Mobile must be running in the foreground to prevent Android from closing it to free memory. **
Compatibility Testing Results
Build 168 REV 20547 "HIGH" Resolution JVM was used for testing. References Est. Mfg. Date 2011 |
| Motorola Droid | | | | | | Comments ** As with all Android apps, X Mobile must be running in the foreground to prevent Android from closing it to free memory. **
** This device is discontinued and it's recommended that customers purchase newer devices. This device, however, was tested to run X Mobile and works. Compatibility Testing Results
References Est. Mfg. Date 2009 |
| Motorola Droid 3 | | | | | | Comments ** As with all Android apps, X Mobile must be running in the foreground to prevent Android from closing it to free memory. **
*** Physical keyboard support only. Onscreen keyboard doesn't function and crashes on prior Android OS Builds *** Compatibility Testing Results ** Initially the device had Android 2.3.1 when received. The unit's "on-screen keyboard" would not provide input to X Mobile and crashed. We upgraded the Android OS by using the built-in check for update feature and the device successfully upgraded to 2.3.4. Once the device was on 2.3.4 the keyboard input would not work but the crashing stopped. ** ONLY THE PHYSICAL KEYBOARD WORKS ON THIS DEVICE **
References es 2011 |
| Motorola Droid 4 | | | | | | Comments
Compatibility Testing Results
References Est. Mfg. Date 2013 |
| Motorola Droid Pro | | | | | | Comments ** As with all Android apps, X Mobile must be running in the foreground to prevent Android from closing it to free memory. **
Compatibility Testing Results ** The test unit didn't include an SD card which seems to be required in order to install applications such as X Mobile.
References Est. Mfg. Date 2011 |
| Motorola Droid Razr HD | | | | | | Comments
Compatibility Testing Results Tested with:
References Est. Mfg. Date 2012 |
| Motorola DROID RAZR M | | | | | | Comments ** We have had a couple complaints that X Mobile is not stable and the alert tones are very quiet after upgrading to Android 4.4.2, if you experience this issue please open a Support Ticket **
Compatibility Testing Results Tested on:
References Est. Mfg. Date 09/13/2012 |
| Motorola Droid Razr Maxx HD | | | | | | Comments
Compatibility Testing Results Tested with:
References Est. Mfg. Date 2012 |
| Motorola Droid X | | | | | | Comments ** As with all Android apps, X Mobile must be running in the foreground to prevent Android from closing it to free memory. **
** This device has no "sound". We're working to try and correct this, no ETA. If you need sound please consider a different device. This device has a large touchscreen and allows for ample room to gather signatures. Compatibility Testing Results
References Est. Mfg. Date 2010 |
| Motorola Droid X2 | | | | | | Comments ** As with all Android apps, X Mobile must be running in the foreground to prevent Android from closing it to free memory. **
** Device initially had keyboard input problems... Please see test results for full details. ** Compatibility Testing Results ** Initially the device had Android 2.3.2 when received. The unit's on-screen keyboard would not provide input to X Mobile. We upgraded the Android OS by using the built-in check for update feature and the device successfully upgraded to 2.3.4. Once the device was on 2.3.4 the keyboard input started to function correctly and all features worked.
References Est. Mfg. Date 2011 |
| Motorola ES400 | | | | | | Comments The ES400 looks like a great new device. It combines a lot of high-end features for a low-end price. Motorola has done a good job at packing in all the needed features for couriers to do light duty scanning, sig capture, and GPS tracking for much less than comparable high end rugged devices. *** If you experience issues with the DataWedge, you need to install version 3.3.19 or higher, available from Motorola. *** *** Might have trouble scanning through transparent materials. Check with your vendor for details regarding scanning limitations etc. References Recommended Vendor Est. Mfg. Date 2010 |
| Motorola ES400S | | | | | | Comments **** This device is locked to the Sprint Network.**** Sprint doesn't provide any staging or lock down services. If you choose to purchase this device through Sprint rather than one of our recommended vendors, you're responsible for your own lock-down/staging services. The recommended vendor for this device is listed in the details. *** If you experience problems with the DataWedge, please make sure you have version 3.3.19 or higher installed, available from Motorola. *** *** Might have trouble scanning through transparent materials. Check with your vendor for details regarding scanning limitations etc References Recommended Vendor Est. Mfg. Date 2010 |
| Motorola ET1 Enterprise Tablet | | | | | Comments ** As with all Android apps, X Mobile must be running in the foreground to prevent Android from closing it to free memory. **
Compatibility Testing Results
Build 168 REV 20547 "HIGH" Resolution JVM was used for testing. Device was running Android 2.3.4 Est. Mfg. Date 2011 | |
| Motorola i1 | | | | | | Comments This device doesn't run the minimum version of Android (2.1). Compatibility Testing Results Unable to install X Mobile.... minimum OS level not met. References Est. Mfg. Date 2010 |
| Motorola i886 | | | | | | Comments This device runs a modified operating system that is "not" compatible with X Mobile. Compatibility Testing Results When we tested this device we quickly found out it's not a typical iDen device running the typical i series Motorola handset software. After reading online and searching through the device it does appear to be running Android, however, it's heavily crippled. Regular Android applications are not allowed, the J2ME emulation doesn't work correctly with the iDen version of X Mobile either. Customers considering this device should look for an actual Android device or an i series device already listed as "Excellent" or "Partial" compatibility. References Est. Mfg. Date 2010 |
| Motorola MC35 | | | | | | References Est. Mfg. Date 2005 |
| Motorola MC45 | | | | | | Comments
Compatibility Testing Results
Recommended Vendor Est. Mfg. Date 2013 |
| Motorola MC55 | | | | | | Comments Some cellular carriers may be reducing the coverage of their 2.5G networks. Customers looking for maximum coverage should consult with their vendor before considering these devices for purchase. *** The MC55 has been successful for many CXT Software customers. The MC55 has a great price point and should provide years of service. *** Motorola has recently revamped their rugged device lineup and the MC55 is now a 4 walls device. The MC65 is the "Motorola" suggested device for outside the four walls. AKA... The new MC55 is WIFI only. Please speak with the recommended vendor for details. MC5574 (Cellular Capable) MC5590 (WIFI Only) Compatibility Testing Results
References Recommended Vendor Est. Mfg. Date 2009 |
| Motorola MC65 | | | | | | Comments The MC65 is like the big brother to the MC55. It includes a much more powerful and accurate scanner, bright and crisp screen, faster processor, more memory, and it looks identical to the MC55. Because of the cross compatibility, all of your existing accessories for the MC55 should work with the MC65. See the recommended vendor for specifics on this device. Compatibility Testing Results
References Recommended Vendor |
| Motorola MC70 | | | |
| | Comments WIFI only device. Some models may not have WIFI check with your vendor for details. References Est. Mfg. Date 2007 - 2010 |
| Motorola MC75 | | | | | | Comments The MC75 has a new model called the MC75a which has the ability to switch cellular providers in the field. See the recommended vendor for more details.
Compatibility Testing Results
** Brief device specs
References Recommended Vendor Est. Mfg. Date 2008 |
| Motorola MC9097 | | | | | | References |
| Motorola Moto Q 9c | | | | | | References Est. Mfg. Date Discontinued. |
| Motorola Razr (XT910) | | | | | | Comments ** As with all Android apps, X Mobile must be running in the foreground to prevent Android from closing it to free memory. **
Compatibility Testing Results
***On occasion when switching from landscape to portrait the bottom half of the screen will remain black. This does not affect X Mobiles functions, and the application still works. Flip the phone into landscape and back will correct.***
***The signature capture is a little boxy, and not as smooth as other devices.***
Build 168 REV 20547 "HIGH" Resolution JVM was used for testing. Device was running Android 2.3.5 References Est. Mfg. Date 2011 |
| Motorola TC55 | | | |  | | Comments
Compatibility Testing Results *** The device performed all major function of the compatibility. ***
References Est. Mfg. Date 2013 |
| Opticon H16A | | | |  | | Comments This device has a slide-out keyboard and is very similar to the HTC Tilt device released a few years ago. Although the device is "lightly" ruggedized, it does have a great scanner and is capable of running the latest Windows Mobile OS. Compatibility Testing Results The Preamble / Postamble for the Opticon Windows Mobile Smartphone devices (H16, H19, and H21) are configured in a little bit of a different manner than regular barcode scanners. To configure the Opticon with the options you will find in the universal menu book please follow the instructions below.
References Est. Mfg. Date 2008 |
| Opticon H19A | | | | | | Compatibility Testing Results The Preamble / Postamble for the Opticon Windows Mobile Smartphone devices (H16, H19, and H21) are configured in a little bit of a different manner than regular barcode scanners. To configure the Opticon with the options you will find in the universal menu book please follow the instructions below.
References Est. Mfg. Date 2008 |
| Palm Treo Pro | | | | | | References |
| Pantech Breakout (ADR8995VW) | |
| | | | Comments ** As with all Android apps, X Mobile must be running in the foreground to prevent Android from closing it to free memory. **
Compatibility Testing Results
Device is Android 2.3.3 References Est. Mfg. Date 2011 |
| Pantech Element (P4100) | | | |
| | Comments *** Because X Mobile does not launch, this device is listed as "Not Compatible". *** Compatibility Testing Results *** X Mobile does not startup/load completely ***
Build 168 REV 20547 "HIGH" Resolution JVM was tested. References Est. Mfg. Date 2012 |
| Psion Teklogix Ikon | | | | | | Comments The Ikon device has a nice small form factor and is very ruggedized. Compatibility Testing Results Tested with Windows Mobile 6.0 Professional. References Est. Mfg. Date 2007 |
| Psion Teklogix WorkAbout Pro G1 | | | | | | Comments This device is no longer manufactured and should not be used if possible. References Est. Mfg. Date 2004 - 2008 |
| Psion Teklogix WorkAbout Pro G2 | | | | | | |
| RIM BlackBerry (All Devices) | |  | |
| | Comments All BlackBerry devices are unsupported... "they don't work" with X Mobile. References Est. Mfg. Date N/A |
| Samsung Epic 4G | | | |  | | Comments ** As with all Android apps, X Mobile must be running in the foreground to prevent Android from closing it to free memory. **
** "Low-resolution JVM required". Small font size may not be desirable by some customers. X Mobile download page may automatically recommend high-resolution JVM. Compatibility Testing Results ** Customers have indicated that when used with the lower resolution JVM, GPS works, but the font sizes are less than desirable. One customer indicated they had difficulty reading the text. Please test this device before making a purchase decision to determine if the text size is smaller than what you would consider acceptable. ** ** Prior build of X Mobile had the following issues.
References Est. Mfg. Date 2010 |
| Samsung Exhibit II 4G (SGH-T679) | | | | | | Comments ** As with all Android apps, X Mobile must be running in the foreground to prevent Android from closing it to free memory. **
Compatibility Testing Results ** X Mobile must be running in the foreground, otherwise, it may be closed unexpectedly **
References Est. Mfg. Date 2011 |
| Samsung Galaxey S7 | | | | | | Compatibility Testing Results Although it works the size of the Fonts and inability to access the command buttons makes the device unusable. Had to use a stylus to open the keyboard and select buttons and even then was very hit or miss. The Full HD JVM was the only one that was even readable The HiRes JVM was too small The LowRes JVM was even smaller than the HiRes JVM References |
| Samsung Galaxy A5 SM-A500W | | | | | Comments X Mobile will load and initially run with Hi-Res JVM but the operation is very problematic - because of the issues listed below, this device is not compatible. com Android Version 5.0.2 tested with X Mobile version 15.1.0, High-Resolution JVM The font size is very small with the High-Resolution JVM, not stable at all on either the Full HD or Low-Resolution JVM. References | |
| Samsung Galaxy Grand Prime SM-G530W | | | | | Compatibility Testing Results Android version 5.1.1 (Lollipop) and X Mobile 15.1.0 with High-Resolution JVM
References | |
| Samsung GALAXY NEXUS (GT-19250) | | | |  | | Comments ** As with all Android apps, X Mobile must be running in the foreground to prevent Android from closing it to free memory. **
Compatibility Testing Results
***Sometimes when in portrait mode, the bottom half of the screen will turn black. You will still see the keyboard control, and the two X Mobile buttons will work. Rotating to landscape, back to portrait, or moving to another screen in X Mobile fixes the issue. You do not lose any functionality.***
***Let the device sit for 2 days, and X Mobile was non-responsive. Had to close X Mobile and relaunch to get it working again.***
Build 168 REV 20547 "HIGH" Resolution JVM was used for testing. References Est. Mfg. Date 2011 |
| Samsung Galaxy Note II (SPH-L900) | | | | | | Comments ** As with all Android apps, X Mobile must be running in the foreground to prevent Android from closing it to free memory. **
Compatibility Testing Results
Device is Android 4.1.1 References Est. Mfg. Date 2012 |
| Samsung Galaxy S 4G | | | | | | Comments ** X Mobile must be running in the foreground, otherwise, it may be closed unexpectedly ** Compatibility Testing Results GPS doesn't work I get a message saying GPS error null. No sound on this device. Made sure volume was all the way up and no sound. References Est. Mfg. Date 2010 |
| Samsung Galaxy S Blaze 4G (SGH-T769) | | | | | | Comments
Compatibility Testing Results
References Est. Mfg. Date 2012 |
| Samsung Galaxy S II Epic Touch 4G (SPH-D710) | | | | | | Comments ** As with all Android apps, X Mobile must be running in the foreground to prevent Android from closing it to free memory. **
Compatibility Testing Results
Device is Android 2.3.6 References Est. Mfg. Date 2011 |
| Samsung Galaxy S II LTE (SGH-I727R) | | | | | | Comments After testing the device, we have found the Samsung Galaxy S II LTE to be incompatible with X Mobile. Please see the compatibility results for further details. Compatibility Testing Results *** X Mobile intermittently starts.
Build 168 REV 20547 "HIGH" Resolution JVM was used for testing. References Est. Mfg. Date 2011 |
| Samsung Galaxy S4 - See | | | | | | Comments The notification tones on this device do not function correctly, instead, the device makes a quiet clicking noise. Compatibility Testing Results
References Est. Mfg. Date Mid-2013 - Current |
| Samsung Galaxy S5 | | | | | | Comments Keyboard requires a very specific touch to open takes some getting used to. About halfway down on the icon Compatibility Testing Results
References Est. Mfg. Date 2016 |
| Samsung Galaxy S5 neo SM-G903W | | | | | Comments This device is not compatible with X Mobile for the reasons outlined below. Compatibility Testing Results Android version 5.1.1, tested with X Mobile version 15.1.0, tested with all 3 available JVMs Font size too small to be functional on either High Resolution or Low-Resolution JVMs. References | |
| Samsung Galaxy S5 Sport | | | | | | Comments Tested on X Mobile 14.2.2 with JVM - High Resolution (Build: 8/15/2013) Compatibility Testing Results *** The device performed all major function of the compatibility test. ***
References Est. Mfg. Date Jun-23-2014 |
| Samsung Galaxy SIII | | | |
| | Comments When you open the virtual keyboard you have to click the back button to get it to go away so you can see other buttons. Compatibility Testing Results
References Est. Mfg. Date 05/2012 - current |
| Samsung Galaxy Tab (SCH-I800) | | | | | | Comments ** As with all Android apps, X Mobile must be running in the foreground to prevent Android from closing it to free memory. **
Compatibility Testing Results
Build 168 REV 20547 "HIGH" Resolution JVM was used for testing. Compatibility Testing Results Est. Mfg. Date 2011 |
| Samsung Galaxy Tab 2 | | | | | | Comments *** Device must use the latest version of JVM 08/15/2013 or greater and X Mobile version 14.0.1 or greater" **** Compatibility Testing Results *** The device performed all major function of the compatibility. ***
References Est. Mfg. Date 2012 |
| Samsung Galaxy Tab 3 | | | | | | Comments JVM version 03/23/2013 and below had an issue with sound not functioning correctly. The device must use JVM 08/15/2013 or higher and X Mobile version 14.0.1 or higher. Compatibility Testing Results *** The device performed all major function of the compatibility test. ***
References Est. Mfg. Date 10/01/2013 |
| Samsung Galaxy Tab 4 | | | | | | Comments While the camera will capture an image (not a barcode scan) there is no preview of the image prior to tapping capture. The image captured is displayed after the fact. In Landscape mode for capture, there were numerous screen artifacts but tapping capture does still work. Tested with JVM High Resolution (build 8/15/2013) Compatibility Testing Results *** The device performed all major function of the compatibility test. ***
References Est. Mfg. Date 04/01/2014 |
| Samsung Replenish (SPH-M580) | | | | | | Comments ** As with all Android apps, X Mobile must be running in the foreground to prevent Android from closing it to free memory. **
######## See Compatibility Results for more details! ####### Compatibility Testing Results
References Est. Mfg. Date 2011 |
| Samsung Rugby Pro (i547) | | | | | | Comments ** As with all Android apps, X Mobile must be running in the foreground to prevent Android from closing it to free memory. **
Compatibility Testing Results
Device is Android v4.0.4 (Ice Cream Sandwich) and Android 4.1.1 (Jelly Bean) References Recommended Vendor Est. Mfg. Date 2012 |
| Samsung Rugby Smart (SGH-I837) | | | | | | Comments ** As with all Android apps, X Mobile must be running in the foreground to prevent Android from closing it to free memory. **
Compatibility Testing Results
Device Info
X Mobile Info
Routed Work
BOL
Device
GPS
Garbage Collection - Does it stay open - Leave on overnight
Remarks
References Est. Mfg. Date 2012 |
| Samsung SCH-i760 | | | | | | References Est. Mfg. Date 2007 |
| Samsung SGH-i907 Epix | | | | | | Comments NO GPS It's suggested that customers look at newer devices but this device was tested to work with X Mobile despite limited compatibility and NO GPS. References Est. Mfg. Date Discontinued. |
| Samsung Stratospher (SCH-I405) | | | | | Comments ** As with all Android apps, X Mobile must be running in the foreground to prevent Android from closing it to free memory. **
Compatibility Testing Results
Build 168 REV 20547 "HIGH" Resolution JVM was used for testing. References Est. Mfg. Date 2011 | |
| Samsung Stratosphere 2 | | | | | | Comments
Compatibility Testing Results
References Est. Mfg. Date 2013 |
| Samsung Transform (SPH-M920) | | | | | | Comments ** As with all Android apps, X Mobile must be running in the foreground to prevent Android from closing it to free memory. **
######## See Compatibility Results for more details! ####### Compatibility Testing Results
This device needs the smaller resolution JVM to get the sound and GPS working. References Est. Mfg. Date 2010 |
| Sony Xperia M4 Aqua E2306 | | | | | Comments Font size is small but functional on High-Resolution JVM. X Mobile crashed on the Low Resolution and Full HD JVMs though so High Resolution is the only compatible JVM. Compatibility Testing Results Tested on Android 5.0 (Lollipop) and X Mobile 15.1.0 on High-Resolution JVM
References | |
| Viewsonic G Tablet | | | |
| | Comments ** As with all Android apps, X Mobile must be running in the foreground to prevent Android from closing it to free memory. **
Although X Mobile works on this tablet customers should consider all the limitations before purchasing this device. This device is not a phone, it's an "Android Tablet" and ideally could be used in any scenario where a computer-sized screen is needed for visibility. Screen scaling looks good and the app scales to fit the screen. Device has a dual-core processor and is very quick. Low-cost device. References Est. Mfg. Date 2010 |
| Windows Phone 7 (All Devices) | | | |  | | Comments Windows Phone 7 devices are not compatible with X Mobile. References Est. Mfg. Date N/A |
| ZTE Optik (SV55TAB) | | | | | | Comments *** This device is listed as "Not Compatible" due to instability issues running X Mobile. Please refer to the "Compatibility Testing Results" for more details. Requires a separately purchased capacitive stylus for capturing signatures. Compatibility Testing Results *** The stability of X Mobile installed on this device was very poor. ♦♦♦ Often times the application would freeze and become totally unresponsive. When the application did run it fit the screen nicely, however, the navigation bar on the bottom might be distracting to end users since that's exactly where X Mobile's navigation bar is located. Every time testing the device X Mobile froze up.
Build 168 REV 20547 "HIGH" Resolution JVM was used for testing. References Est. Mfg. Date 2011 |
- No labels