Latest Contributions by ColinLawrence

Are you using an MDM to deploy Field Maps and have potential restrictions set on  your device Browser? The team was never able to reproduce this issue even while testing with Intune MDM deployment. Happy to investigate further if we can determine what is unique in these setups causing the app links to open in Edge.  ... View more

I believe the value is anything greater than 601dp for the width will support landscape view. This isnt always directly translatable from screen size and it is sometimes quite difficult to uncover this value from a manufacturer; that is one of the reasons we added the developer setting I mentioned above to verify the value. Again, we are re-evaluating this cutoff for a future release and hope to support some additional devices in landscape mode.  ... View more

Hi @Y_Chau , Generally speaking a 10" tablet should support rotation but ultimately the cutoff is not the screen size but pixel density. There is a developer setting in Field Maps Android that should give this info about your device. When signed in, tap the profile settings in the top right of your Maps list, then tap on your username 3 times rapidly. The first row in the developer settings window should give you the device form factor based on the predetermined Field Maps cutoffs, followed by the screen density values. The team is evaluating changes to the specific cutoffs in the future as we do frequently hear customers on smaller model tablets want to utilize landscape mode as well.  ... View more

It cannot be the active provider; you will need to select Integrated to be active first. I should have mentioned that before.  ... View more

Hi @Cepero_Eudel , you can remove this from the location provider screen but selecting the overflow menu (three dots on android or the "i" on iOS) and then selecting remove.  ... View more

Hi @CMJ , are you connecting to the R1 in TMM (via the `connect to position source` toggle)? I dont believe this should make a difference but try toggling this off as you will want it off anyway when connecting in Field Maps. You could also try forgetting the device in your bluetooth settings (again) and then performing a reset of the R1 by holding the power button for ~30 seconds; I believe the LED indicators should flash at this point. ... View more

Hi @JuanCervera , just to clarify, are you referring to Location Sharing (used to be called Tracking) or the streaming of line or polygon features? Both instances should work in the background but with a little different logic under the hood. With the way both of these functionalities are implemented on Android we do not need the "Always on" location permissions to get locations in the background, only the permission "when in use". Also, Android generally discourages and restricts when "Always" can be used. ... View more

Hi @LandConFellow , what model of Samsung tablet is it and what operating system is it running? Does at crash at a specific step in your workflow (ie taking a photo)?   ... View more

Can you please reach out to the email alias you posted? You will likely be interacting with me but this way I can also loop in others on the team. We can also chat more about the GPS receiver. Thanks! ... View more

Hi @travisajohnson_wsp , what Android devices and OS versions are you seeing this on? Would you be able to share your Web Map with us? You can add the Map and Feature Service(s) to a Group and invite the user "Arcgisfieldmaps". Thanks! ... View more

Updating this thread with a newer BUG number:  BUG-000159710 If you are encountering this issue please reach out to Tech Support to get attached to this bug and provide details about the device(s) you are using and your general workflow. ... View more

Hi @JoelCusick , thanks for the reply. The point I was trying to make is that taking a map "offline" in Field Maps does not mean that the data/wifi connection on your device stops or that we will not attempt to access it; it simply means the basemap is downloaded and edits made in this map will be stored on a local geodatabase and synced back to there server if/when a connection is available. You can use the "offline version" of a map with a data connection and with an RTK/correction service connection. I may be going off on a tangent a bit from the original question but I just wanted to try and clarify that. As RTK requires a data connection it might make sense to not have to bother preparing your maps for offline use. There are other services, as others have pointed out in this thread, that would allow high accuracy data collection in areas of no/low connectivity. I hope this helps clarify things! ... View more

Just cross posting my reply from the other thread here for visibility.  See more info below: Hi @WardMitchell2 , hopefully I can help clarify some things around this. The bug linked above BUG-000137313 is one that was logged some time back and was specific to Samsung Tab A (the first generation) devices as these devices had 2GB of memory. The Android system itself would consume about 1.4GB of memory alone with no other apps open, leaving about 500MB of memory to work with. When workflows with attachments are started the system can easily enter a low memory state and this would lead to crashes. This does not apply to your device.  More recently we have been hearing reports (BUG-000159710) on a wider range of Samsung devices (mostly Tab Actives, like you have) that are experiencing these "resets" of the app when taking photos; these devices do have higher memory capacity as you noted. Recently we did fix a low level memory related issue that alleviate some of these issues but that does not seem to have addressed all of the cases. We continue to investigate this. This issue has not been easy to reproduce on our end for some reason with Tab Active Pros so any additional information you can provide would be helpful, however trivial it may seem. If you reach out to the field maps email alias you posted above we can work with you more directly on this. I will work on getting a new BUG filed with Support so you and any others experiencing this can get attached to the correct and more relevant BUG. Thank you! ... View more

Hi @WardMitchell2 , hopefully I can help clarify some things around this. The bug linked above BUG-000137313 is one that was logged some time back and was specific to Samsung Tab A (the first generation) devices as these devices had 2GB of memory. The Android system itself would consume about 1.4GB of memory alone with no other apps open, leaving about 500MB of memory to work with. When workflows with attachments are started the system can easily enter a low memory state and this would lead to crashes. This does not apply to your device.  More recently we have been hearing reports (BUG-000159710) on a wider range of Samsung devices (mostly Tab Actives, like you have) that are experiencing these "resets" of the app when taking photos; these devices do have higher memory capacity as you noted. Recently we did fix a low level memory related issue that alleviate some of these issues but that does not seem to have addressed all of the cases. We continue to investigate this. This issue has not been easy to reproduce on our end for some reason with Tab Active Pros so any additional information you can provide would be helpful, however trivial it may seem. If you reach out to the field maps email alias you posted above we can work with you more directly on this. I will work on getting a new BUG filed with Support so you and any others experiencing this can get attached to the correct and more relevant BUG. Thank you! ... View more