iPhone SE and Dual XGPS150A - no sensor data

[adam12345]

Thank you for any help. I am unable to get external GPS sensor data in LapTimer Grand Prix.

Here is what I am using:
* iPhone SE iOS 9.3.1 (13E238)
* Dual XGPS150A firmware 1.3.2
* Harry's LapTimer Grand Prix 20.0.3

What works
* Successfully connect iPhone to Dual XGPS via bluetooth
* Can see Dual XGPS GNSS as Available - Yellow in LapTimer sensor list
* GPS light on Dual XGPS is on/solid, meaning it has satellite to fix position

What doesn't work/errors
* Dual XGPS GNSS is always "Available", not "Connected"
* No data available in Real-Time GPS screen (Signal, speed, heading, long/lat)
* LapTimer status Red items are:
* - Location Services ?
* - Dual XGPS GNSS ?
* - GPS Position ?
* - Accuracy ?
* Steps that crash LapTimer every time
* - On the RealTime menu screen, clicking Satellites
* - After clicking GPS in the Realtime menu screen, clicking the signal strength bar (red/yellow/green)

Confirmed iPhone settings
* Privacy -> Location Services -> ON
* Privacy -> Location Services -> LapTimer -> While Using

Other testing
* Successfully used same Dual XGPS150A device on a friend's iPhone 6s v9.3.1 running LapTimer v19.0.30 - saw multiple satellites and successful long/lat.
* Attempted to use friend's Dual XGPS160 with my iPhone SE, same problem --> Bluetooth Connection but no GPS data
* Factory reset iPhone SE and deleted all data, loaded LapTimer and connected to XGPS150A via bluetooth. Same result, no sat data in LapTimer

Screenshots attached

Screen shots

all_images.png (194.82 KiB) Viewed 3499 times

Thank you for any help/suggestions!

[Harry]

Please check LapTimer ‣ Administration ‣ Settings ‣ Expert Settings ‣ Accessory Tweaks / Use Accessories ‣ ON.
Make sure you have the XGPS150 micro switch in Apple position.
Unpair and pair the XGPS150 with your phone again.
Make sure you do not have any app using the Dual directly active (e.g. Dual's app).

As a special test you may turn off Accessories in LapTimer. This means LapTimer does not access accessories directly. Instead, it will use iOS's location service. For a well working XGPS, iOS will replace the internal GPS by the XGPS and pass XGPS data through Location Service to app. This means LapTimer will report the GPS as iPhone GNSS but will actually get data from the XGPS. You can recognize this situation looking into the update rate - it will be 4 or 5, not 1.

- Harry

[adam12345]

Harry,
Thank you for the quick reply. Use Accessories = ON. XGPS150A switch in Apple position (farthest away from USB jack). Closed all apps on iPhone, unpaired and paired Dual XGPS, then launched LapTimer, same result.

When turning off Accessories, I do get a GPS fix, but it does not go over 1 Hz (see screenshot attached).

I have downloaded the GPS Buddy. Are there any specific steps that I could capture that would be helpful?

Thank you!

[Harry]

Yes, please check the instructions to create a trace log in the FAQ section first. The trace classes you need to tick are Sensor Connection and GPS/GNSS Sensors.

The log sequence is:

Turn the XGPS off.
Start LapTimer, start logging.
Switch to Sensor List.
Turn the XGPS on.
You should see the BT icon blink and LapTimer should show the XGPS now.
Wait some seconds.
Stop the log and send it.

- Harry

[Harry]

The snapshots look strange, test should be black on light background. Is this how you see it?

[Harry]

Hi Adam,

Thanks for the log files, but I have no good news...

This is probably an issue with the phone or the phone’s accessory connection state in general.

Here is a section from the log:

Code: Select all

EASENSORS      0001025923@main  00 --> call to AccessorySensor::executeAccessoryChangeQueue ()
EASENSORS      0001025923@main  01   --> Accessory will be connected
EASENSORS      0001025923@main  02     --> call to AccessorySensor::reconnectAccessory ()
EASENSORS      0001025923@main  04         --> call to AccessorySensor::tryConnectingToAccessory:withProtocol:toMode: (., com.dualav.xgps150, .)
EASENSORS      0001025923@main  05           --> call to AccessorySensor::connectAccessorySessionWithAccessory:forProtocol: (., com.dualav.xgps150)
EASENSORS      0001025923@main  06             --> trying to connect to protocol com.dualav.xgps150 for accessory XGPS150-41DA8C
EASENSORS      0001025924@main  06             --> failed to get session for protocol com.dualav.xgps150...
EASENSORS      0001025924@main  05           --> AccessorySensor::connectAccessorySessionWithAccessory:forProtocol: () returns false
EASENSORS      0001025924@main  04         --> AccessorySensor::tryConnectingToAccessory:withProtocol:toMode: () returns
EASENSORS      0001025924@main  04         --> call to AccessorySensor::tryConnectingToAccessory:withProtocol:toMode: (., com.emprum.ultimategps, .)
EASENSORS      0001025924@main  05           --> call to AccessorySensor::connectAccessorySessionWithAccessory:forProtocol: (., com.emprum.ultimategps)
EASENSORS      0001025924@main  06             --> accessory XGPS150-41DA8C does not publish protocol com.emprum.ultimategps...
EASENSORS      0001025924@main  05           --> AccessorySensor::connectAccessorySessionWithAccessory:forProtocol: () returns false
EASENSORS      0001025924@main  04         --> AccessorySensor::tryConnectingToAccessory:withProtocol:toMode: () returns
EASENSORS      0001025924@main  04         --> call to AccessorySensor::tryConnectingToAccessory:withProtocol:toMode: (., com.tomtom.gps, .)
EASENSORS      0001025924@main  05           --> call to AccessorySensor::connectAccessorySessionWithAccessory:forProtocol: (., com.tomtom.gps)
EASENSORS      0001025924@main  06             --> accessory XGPS150-41DA8C does not publish protocol com.tomtom.gps...
EASENSORS      0001025924@main  05           --> AccessorySensor::connectAccessorySessionWithAccessory:forProtocol: () returns false
EASENSORS      0001025924@main  04         --> AccessorySensor::tryConnectingToAccessory:withProtocol:toMode: () returns
EASENSORS      0001025924@main  02     --> AccessorySensor::reconnectAccessory () returns false
EASENSORS      0001025924@main  00 --> AccessorySensor::executeAccessoryChangeQueue () returns

The item “failed to get session for protocol com.dualav.xgps150” means LapTimer has recognized the accessory, but iOS does not allow the app to connect to it. I know this phenomena because it happens in case a protocol used (com.dualav.xgps150) is not declared as a valid protocol too. This declaration is part of Apple’s white listing process. However, both LapTimer and Buddy are white listed and have the valid declaration included. To make sure, I loaded a fresh Buddy from the store and connected a XGPS150 to my iPhone 6S. It worked without an issue and reported 5 Hz and green.

I have checked Apple’s forums on known issues with iPhone SEs and accessories but have not found anything. So it does not seem to be general issue with the device type but some configuration issue. I'm not aware of a specific privacy or configuration setting influencing accessory access, but you may go through the phone settings and check for any special setting you have. In particular, using airplane mode has an impact on many device components, so please turn if off.

- Harry

[adam12345]

Harry,
I worked with Apple Support and was able to resolve the issue.

I performed a full restore to wipe the phone and apply the latest iOS release. Steps taken:

1. Back up iPhone with iTunes
2. Disconnect iPhone from USB cable
3. Shut down iPhone
4. Hold down iPhone "Home" button
5. While holding button, plug back into USB/iTunes
6. Hold button until you see following message in iTunes:
"iTunes has detected a device in recovery mode. You will need to restore the device before it can be used."
7. Select the "Restore" Option in iTunes
8. iTunes will wipe the phone, download and apply the latest iOS release
9. When you see this message in iTunes: "congratulations, your iphone has been unlocked", disconnect iPhone from USB
10.Follow prompts to setup as a new phone
11.Download LapTime and connect to XGPS150A --> Success! 5hz rate and "Connected" Dual XGPS GNSS accessory with multiple satellites.
12.Restore iPhone backup taken in step 1
13.Re-Confirm LapTime and XGPS150A continues to work

All set for this weekend at Mid-Ohio!

[Harry]

I'm happy to hear, so it was indeed the iPhone configuration that has been screwed up. Despite the reset operations - have they given any background on this issue? Were they aware of it as a recurring issue?

Harry

[adam12345]

They did not discuss if they had seen it before, but immediately went to applying the newest OS release. It seemed like a standard procedure to wipe/apply latest release for something beyond normal "How To" fixes.