Survey123 location not working on my android phone. Even we have 4g and location service turned on, after that also its not working. Please tell us solution ASAP
Hi Shoumen,
I need some more information in order to properly diagnose what the issue might be:
1) Can you confirm that your location appears in Collector or another mapping application?
2) What model of phone are you using?
3) Are you using the internal GPS or an external receiver?
Hi,
One of our field workers has also problem with the location in survey123 .
All her submited surveys located in 0,0 (Near Gabon).
She has Xiaomi Redmi Note 4 with Android 6.0.
The location works perfect in Collector.
Is there a way to fix it?
Thanks
Guy
Hi Guy.
What version of the Survey123 app are you using?
Are you indoors or outdoors at the time of trying to get a location fix?
Regards,
Phil.
Hi Phil
The version of the survey123 app is 2.2.15.
We use the same version of the app in another android device with no problems.
Thanks Guy,
Does the device have GPS signal when Survey123 is opened and the location question selected? Or are you opening the app and trying to get the location when indoors.
There is currently a known issue with Survey123 with some Android devices where if the GPS signal is not available for the current location, it will not fall back to the network/wifi location information. This causes no location to be returned from the device. A fix for this issue is currently being developed and hopefully will be available in a future release.
In the meantime, can you ensure that the GPS is working and has a valid signal when opening and using Survey123 and let me know if the device still does not report the location.
Hi Guy, I will need to investigate this further and get back to you. Thanks for all the additional information. Phil.
Hi Phil,
I was wondering if there had been any reports of a similar error "Position Source Access Error" occurring with iPad Mini's? It's an intermittent problem, where sometimes the location can be accessed in Survey123, and sometimes that error appears. When positioning was tested in Collector (outside), the location is being picked up and reported correctly - this issue only appear sporadically in Survey123. We've made sure the app is up-to-date, but still can't figure out what is causing this to happen. We are using a Bad Elf GPS Pro receiver with an iPad that is NOT cellular-enable (it always runs offline).
Any help with this would be greatly appreciated, even if you think it might be worth going directly to Bad Elf to determine if it's a firmware issue. We have other iPad/GPS pairs using the same products and no others are having this issue...
Thank you!
Erica
We have numerous users getting the "Position Source Access Error" since the update to 3.0.132.
Yes, works in Collector, Google Maps, and GNSS Status when offline
2) What model of Tablet are you using?
Samsung Galaxy Tab A (2016) SM-T280 Android version 5.1.1
Just the device GPS
We can't manually enter location either.
No issues with location on all of the other devices we use with this version of the app.
Hi Damien,
Do you have any calculations or defaults on your geopoint questions? Does it happen or all devices with all surveys, or just some devices and some surveys? If so which ones?
Are you able to share a copy of your xlsx file if you think it is specific to one of your surveys only?
Hey Philp,
The survey in question works great on a variety of devices but has issues on the Tab A model mentioned previously as well as on a iPad mini 4 64 gig (Model: MK822LL/A) iOS 11.4. The survey has calculations/geofence on geopoint fields so 0,0 isn't accepted. I tested the Tab A on another survey with no calculations on the geopoint and while I was able to manually add location, it never got a location fix. This was in open canopy on flat terrain. Collector, GNSS status, and Google Maps were able to provide location from the same spot. I'll send you what we have on our geopoints.
Thank you,
D
Attached is the geopoint info for the survey that can’t get location input (or manually enter location) on a couple of device models.
Thanks,
Sorry for the delay in getting back to you, I was at the UC and now back in office catching up on outstanding tasks, plus I wanted to test your survey on some of our devices here in the office. So, I am unable to replicate the issues you are having with certain devices not getting a valid position source. I tested your survey on a similar spec Tab A and iPad, as well as a range of other iOS, Android and Windows devices. All of them worked as expected, with the location being set from the GPS either automatically, or using the cross hair to update, or I could manually set location by the geoseach entry method or typing in the coordinates. In all cases the calculations you have set work to display the note when I am outside of the US.
For the devices getting a "Position Source Access Error" this usually means the device is offline, location services is disabled or there is an error on the device with location information. It could be that another app is trying to access location information and causing Survey123 not to get access to location services.
You mention that you could not manually enter coordinates either, with the 3.0 release we have changed the way manual entry of coordinates worked as well as implemented geosearch and geocoding features. Regardless of whether the device has a position source or valid location, you should still be able to manually move the map or enter the coordinates via the "Map coordinate input only" option. You can find out more here: Quick reference—Survey123 for ArcGIS | ArcGIS and in more details regarding coordinate formats here: https://community.esri.com/groups/survey123/blog/2018/07/08/working-with-usng-and-mgrs-in-survey123-for-arcgis
Hope this helps.
Hi all,
I have been having a similar problem with a setup using iPad Mini 2s without cell service and even with Ipad Mini 4s with cell service that are paired with an EOS Arrow 100. Our crews collect a point in collector and I use the URL_Schema to send attribute info along with the ESRIGNSS_LAT and ESRIGNSS_LONG as the center point to Survey123, But what seems to happen is that the current location of the device is where the Survey123 point is located in its feature service even though the ESRIGNSS LAT and LONG fields in the collector feature service have the correct locations. This also happens when the crews use collector on the way back from fieldwork or back at the hotel to update 123 forms. This has become a big issue with our implementation of Survey123 and we may have to go back to just using collector if we are unable to figure this issue out. Is there a way to force 123 to use the stored ESRI GNSS values from the collector point?
LTK
Hi LTK,
Are you still having this issue? Have you tested the latest 3.5 release of Survey123 which now includes support for external GNSS receivers?
Hi Phil.
I've been experiencing this problem with my users for quite some time (over a year). This usually happens on Android devices where Survey123 has been running normally for more than 6 months, and Survey123 unexpectedly stops collecting the coordinates, but other applications collect normally. Well, after a lot of testing, apps installations to fix AGPS, etc., the solution I found unfortunately was to prompt the user for a "factory reset" on the device. It seems that after some time of use and after many software/apps updates the Survey123 kind of "loses" the preference for GPS, even if reinstalled. However, after the Factory Reset, the device always returns the GPS signal on Survey123. One way I did to "work around" this problem in devices that could not reset was to change my search to accept a photo (collected by an external app - OpenCamera - in my case) and then transfer the coordinates of this photo to the geopoint by a calculate.
Anyway, I hope this my experience help you to find a definitive solution for this issue in Survey123 field app code.
Good luck.
PS: I also realized that this problem occurs more often on devices with little internal memory. When I say "little memory", I mean 16GB or less.
Hi Adilson,
You should not need to do a factory reset. It sounds as if the location permissions settings are getting "out of whack" on the device, and with Android, when you do an uninstall the app settings to not get deleted, they remain in the settings folder. As we have done a lot of changes to support external GNSS receivers and other improvements to location services, it could be the app settings that have conflicting settings, provided that location services is enabled for the app in the device system systems.
You can delete the app settings by navigating to ~\ArcGIS\AppStudio\Settings\ on the device (on Android it will be in the Internal Storage folder) and delete the *.json files in this folder. This will delete all the settings saved by the app, and when you open the app again it will re-create this file.
On iOS, when you uninstall the app, this folder is deleted, so a new files is always created. But for Windows, MacOS and Android, the settings are kept even though app is uninstalled.
Hi Team,
One of our client is having issue regarding the GPS issue in Survey123 for ArcGIS.
The GPS is working perfectly fine in the device as they use Google Maps and other mapping apps and is able to locate the correct location.
However, while getting into Survey123 for arcgis the GPS is not working and the location automatically picked is 0,0.
The device was taken outdoor and checked. But the issue still persists.
I would request team to please help us out with this is hampering the production work of the client.
Newer versions of Android block the location from apps until turned on - app by app. Have to tried this?
iPads actually will turn location off again every time a new version is installed.
Thanks Doug for your response.
I will have user test this and update you.
Also make sure they are not in airplane mode or have battery saver on. We had a number of people doing that and it shuts the GPS off. (You can use these, and it helps with battery, but you must remember to manually turn location back on).
Dear All.
I had this problem some time ago. After to try a lot of methods to solve this problem (including factory reset, which turns GPS back on in Survey123) I received a perfect solution from ESRI (I don’t remember who provided this solution for me, sorry).
This solution is:
On your phone, open the File Manager and go to this folder:
Internal Storage/ArcGIS/AppStudio/Settings
Remove (or rename the extension of) all JSON files.
Open Survey123 and try again.
The explanation:
These JSON files are generated at first time when the Survey123 is opened after of first installation. In some cases, this configuration file may be old for the new version of Survey123, Removing this file forces the new Survey123 to create this configuration file again.
An advice: If you use the DEVICE ID in your projects, take in mind that removing this file the DEVICE ID of your device will change.
Well, I hope this can help you and others with the same problem.
Best regards.
Adilson Furlani
Research
Phone: +55 11 3039-6894 | Email: adilson.furlani@ldcom.com<mailto:adilson.furlani@ldcom.com>
Louis Dreyfus Company Brasil S. A.
São Paulo / Brazil
http://www.ldc.com/br<https://emea01.safelinks.protection.outlook.com/?url=http://www.ldc.com/br&data=02|01|ADILSON.FURLANI@LDCOM.COM|8a0b7c1cb890493859f908d654e62366|40a64d0bf2f94a34b1b30992ac0e5e4e|1|0|636789744746079120&sdata=W+r8nPVG6OYo3IYTmJn8AXkaAgp7HMsT+roK+IpG+os=&reserved=0>
Hello all,
I noticed this issue related to another thread that has a solution, so I will add the link:
Solved: Location data not recorded - Esri Community
Here is the instruction to be executed in Survey123 on the problematic Android devices:
Hope it helps.
Kind Regards,
George
Thanks @GeorgeJoubert for linking the issue. As per my comment in that issue, this issue has been resolved in the upcoming 3.16 October Release of Survey123 with some Android devices not getting a valid location causing the geopoint to not be updated correctly. You can test out the latest 3.16 beta builds via the Early Adopter Community to get early access to these builds.
The workaround you provided above does work (for testing and debug purposes) however be aware that using the "Google Play Location API" may provide less accurate GPS locations and certain Android Extras location metadata will not be available. If high accuracy (horizontal and vertical accuracy) are needed, or you are using pulldata(@geopoint) to extract additional information, you may notice a difference when you switch to that provider.
The 3.16 release will be public next week in the Google Play store. Remember to check the setting is reverting back to "Android Location API" provider as default.
Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
