ArcGIS QuickCapture Blog - Page 2

Find version 1.5 of QuickCapture now in the Apple, Google Play and Windows app stores. This update makes QuickCapture a more powerful data collection tool, without compromising its simplicity. It adds support for multiple button user inputs, Juniper’s Geode GNS3 high accuracy receivers, and more!

Our next ArcGIS QuickCapture Holistic Testing session will be July 5th from 9:00AM - 12:00PM (US Pacific Time Zone).  We will give a few demos of the new features coming up and give you a chance to test the Beta software yourself. Our biggest aim with these sessions is to collect your feedback, so we are in the best shape possible for release. You can register for this virtual event through this form.

Read on to learn what's new in the June 2022 update of ArcGIS QuickCapture

The Field Notes podcast is focused on engaging with Esri customers and staff to understand mobile GIS, share stories from the field, and explore all things Field Operations

Collect field observations with a single tap on your mobile device. Read on to learn what's new in ArcGIS QuickCapture (March 2022)

ArcGIS QuickCapture Hands-On Session open to Early Adopters.

The dates are:

• Thursday, Feb 17, 2022 9:00AM - 12:00PM (Pacific Standard Time)
• Friday, Feb 18, 2022 1:00PM - 4:00PM (Australian Eastern Standard Time)

If you want to join, follow these steps:

1. First join our QuickCapture Early Adopter program. You will need an Esri account for that.
2. Complete this Registration form so we know you will be joining us for the event.

It is important to share your QuickCapture project properly so your mobile workers can access and use it successfully. Here are all of the ways to share that you need to know.

One more release to close 2021, and what a release! ArcGIS QuickCapture 1.12 now includes support for location tracking.  Read on to learn more...

We will host a couple of virtual sessions in November to share with you our progress with the upcoming release of ArcGIS QuickCapture.  During these sessions, we will grant you access to Beta builds of the software. Our focus will be location tracking within ArcGIS QuickCapture.

When using QuickCapture and the application crashes, the generated log files (logcat) can be retrieved to perform diagnostics and troubleshooting. However, as the app does not have Developer mode enabled by default, the log files can only be retrieved using the Android SDK developer toolset.

Procedure

The following workflow can be performed for non-rooted Android devices to extract the log files. However, prior to reproducing the error to generate and extract the log file, Developer mode must be activated on the Android device. A Windows computer is required to perform the extraction.

Warning:   
This workflow involves using Android SDK tools and is not supported by Esri.

1. On the Android device, navigate to Settings > About device, and tap the Build Number option seven times to enable developer mode.

   Note: On some Android devices, the Build Number option can be accessed via Settings > About phone > Software information.

2. Navigate back to the Settings menu, open Developer options > enable the USB debugging option.
3. For Android devices running on versions 5.0 or later, increase the Log buffer sizes to 4 MB per log buffer.

   Note: 4MB is sufficient for storing the logs. However, this can be increased as needed.

4. Open QuickCapture and reproduce the error. This generates the log file.
5. Connect the Android device to a computer with a USB cable.
6. Download Android SDK Platform Tools, and extract the contents to the computers c:\ drive.
7. Open the extracted c:\platform-tools folder and ensure adb.exe exists.
8. In Windows Search, type in cmd and then select Command Prompt and Run as administrator.
   

    

9. In the command prompt, perform the following:
   1. Change the directory by typing CD, followed by the extraction destination directory. For example:

      CD C:\platform-tools

   2. Enter the following command:

      adb logcat -v threadtime -d > C:\platform-tools\logcat.txt

10. The log file (logcat.txt) is now extracted to the destination folder using verbose logging.

    Note: For more information on understanding the log file, refer to Reading Bug Reports.