That's a good thought, however that file is only read AFTER a Trimble receiver has been selected in Field Maps. The config file is read to obtain correction and coordinate system info.
Mark.
Original Message:
Sent: 12-11-2023 08:23
From: Eric Eric
Subject: Catalyst DA1 and Android 10 issues with Field Maps
Hi Micah,
The Trimble folks ought to chime in here, but as I understand it, TMM writes a config file that Field Maps ought to pick up for seeing the DA2 and its parameters. That config file may be corrupted or have issues?
------------------------------
Eric Collins, P.L.(Eng.), P.Tech.(Eng.)
Operations Technology, Chief Operations Engineering
Calgary, AB, Canada
Original Message:
Sent: 12-08-2023 10:24
From: Micah Holzbauer
Subject: Catalyst DA1 and Android 10 issues with Field Maps
Hi Mark,
I uninstalled and re-installed Field Maps. I also unpaired the DA2 from my bluetooth, reset the DA2 bluetooth connections (held down power button for ~5 seconds). The DA2 is still not listed as an available provider in Field Maps.
------------------------------
Micah Holzbauer
Original Message:
Sent: 12-04-2023 14:23
From: Mark Kellaway
Subject: Catalyst DA1 and Android 10 issues with Field Maps
Thanks Micah.
That's one theory out of the window! :-). We've just tried it here on the same device and it's working fine. Just confirming again, if you add a location provider (as opposed to the list of known providers) in Field Maps you can't see the paired DA2? I know it's a pain, but it might be worth removing Field Maps completely and reinstalling it on that device if you haven't tried that already.
Regards,
Mark.
------------------------------
Mark Kellaway
Original Message:
Sent: 12-04-2023 06:00
From: Micah Holzbauer
Subject: Catalyst DA1 and Android 10 issues with Field Maps
Thanks for the quick response, Mark. I agree that it seems quite strange that the DA2 doesn't appear as an available position source.
My DA2 firmware version is 1.58. FYI, I found the firmware version listed under the "Position Source" window instead of "Status" in TMM.
------------------------------
Micah Holzbauer
Original Message:
Sent: 12-03-2023 15:58
From: Mark Kellaway
Subject: Catalyst DA1 and Android 10 issues with Field Maps
Hi Micah,
It's strange that Field Maps doesn't see the DA2, and this feels like the issue we need to focus on. Can you confirm which Firmware version your DA2 has installed? You can see this by looking at the Status view in TMM while connected to the receiver.
Thanks,
Mark.
------------------------------
Mark Kellaway
Original Message:
Sent: 12-01-2023 16:40
From: Micah Holzbauer
Subject: Catalyst DA1 and Android 10 issues with Field Maps
Using a DA2, I'm running into what sounds like a similar issue on a Samsung Note 9 (Android 10) . TMM is able to connect to and utilize my DA2 receiver just fine. It is able to achieve the Catalyst subscription level of accuracy (1-cm). When I try to use the DA2 in Field Maps, things go bad.
When I jump over to Field Maps (after toggling OFF the TMM's "Connect to position source"), I am unable to add the DA2 receiver as a location provider because the DA2 is not listed as an available location provider. All of my other bluetooth devices are listed as available location providers, but not the DA2. I've unpaired and paired the DA2 numerous times, but that doesn't seem to help. Meanwhile, when I look at my genaral bluetooth device list, the DA2 is listed.
As an attempted workaround, I tried the mock location route.
- I closed Field Maps
- I closed TMM
- Opened Developer Settings for mock location and set it to TMM
- Opened TMM and connected to the DA2 as the position source
- Enabled TMM's Location Sharing under Application Settings
- Opened Field Maps and confirmed the location provieder is "Integrated"
- Open a map in Field Maps
At this point, my map loads, but the map glitches while flashing "GPS location not available" repeatedly. If I disconnect the DA2 in TMM, the Field Maps map will load and show my location with the integrated GPS accuracy around 2.8 meters (native cell phone GPS).
Both TMM and Field Maps are fresh installs as of today.
I have performed the same steps on a Galaxy Tab S7 FE 5G (Android 13) using the same DA2 and both of my scenarios described above work fine. Field Maps is able to accept the DA2 as a location provider with good accuracy, and I am able to perform the mock location approach with good results. ESRI claims Field Maps supports Androids with Android 8.0 (Oreo) or later (https://doc.arcgis.com/en/field-maps/get-started/requirements.htm)
Any recommendations would be apprecatiated.
------------------------------
Micah Holzbauer
Original Message:
Sent: 10-27-2023 15:26
From: Zach Edwards
Subject: Catalyst DA1 and Android 10 issues with Field Maps
Matthew, field Maps is actually supported on android 8 and above. I'm wondering what was causing the issue though.I am guessing the android device that you were using is just not quite enough horsepower to run the Catalyst Service for the DA1.
https://play.google.com/store/apps/details?id=com.esri.fieldmaps&hl=en&gl=US
------------------------------
Zach Edwards
Original Message:
Sent: 10-27-2023 07:30
From: Matthew Hobson
Subject: Catalyst DA1 and Android 10 issues with Field Maps
We had this same issue with a DA1. It was caused by Fieldmaps only supporting Android 10.6.1 and later. We swapped in a newer handset running Android 13 and this fixed the issue.
------------------------------
Matthew Hobson
Original Message:
Sent: 06-22-2022 08:46
From: Andrew Guardi
Subject: Catalyst DA1 and Android 10 issues with Field Maps
I'm using a Catalyst DA1 with a Samsung Galaxy S4 tablet that is running Android 10. I have no problem when connecting with TMM and finding satellites. When I go to Field Maps it says that it can't locate a GPS signal. I used a Catalyst DA2 with the tablet and there were no issues. Then I used the DA1 with an Android phone running Android 12 and there were no issues. Is there an issue with the DA1 and Android 10?
------------------------------
Andrew Guardi
------------------------------