Different arrows on watch and phone

[MrField123]

Watch and phone showing different arrows but same numbers. The wear arrow is the same as the one at the original dexcom receiver.

Setup:
G6, Nativ Mode, Patched Huawei Watch, Galaxy S7 edge, latest xDrip+ build.

[parapenT1sta]

Can you try to change the Arrow trend to the new version? Some Android OS change the default arrow and it's not good...
Long press on xDrip+ (graph) upper left corner, and then activate the last option.

[jag111]

I see this too with G6, Nativ Mode, Sony SW 3, Moto E (2nd gen), Beta xDrip+ build. Don't understand "Long press on xDrip+ (graph) upper left corner, and then activate the last option" since long press does not bring up options. What is the name of the option that should be changed?

[MrField123]

The new arrow trend looks fine in the app thanks! But in notifications and on the watch the arrows are random.

Long press on the xDrip Logo (blood drop) will Open the settings

[jag111]

Long press on the xDrip Logo (blood drop) will Open the settings

Thanks, that worked. No effect on watch arrow though.

For me watch arrows are not random, but often less steep than phone arrows. Not a major issue for me, just something I noticed.

[teflonjoe]

I have this issue too. Using OnePlus 6T and Ticwatch C2. Arrow on watch face does not correspond to app.

[rca221]

Same issue here too with Xdrip and G5 on Android TicWatch E.

[hmbannister]

I have the same issue with xdrip/g6/fossil watch.

[wakefulpanda-web]

I have the same issue on xdrip+, G6 and Fossile G5. Watch arrow just remains straight while Xdrip app on phone will have the correct corresponding arrow for a rise/fall rate.

[Cagier]

I have this error too with my pebble but I think the problem is that although the xDrip is working out what the arrow should be, it is in fact sending the arrow that the G6 has derived instead. I've deduced this from the fact that we have a separate G6 receiver and the arrow direction on the watch (and NightScout site) always match the Dexcom receiver and these are often different to the xDrip app.

This seems to related to the G6 but may relate to G5 in Native Mode also?

I suggest that the xDrip app should transmit it's own arrow to remote systems rather than blindly sending on the arrow direction that Dexcom has worked out. It would be more consistent and less confusing (and more accurate!)

I think this may be related to #681

In Issue #414 jamorham mentions that the expected behaviour is for the trend arrow in xDrip to be the same one that is reported by the G5 (and presumably G6) in Native Mode. So the issue seems to be that this is not the case as the arrow in xDrip can be very different to what I see on my G6 receiver. However, what I see in my G6 receiver tends to match what I see on my watch.

The natural fix would seem to be to also "correctly" display the G5/G6 reported/Native arrow on xDrip as expected and then everything would be consistent. However, personally I find the one reported by the G5/G6 to be a lot less accurate than the one displayed in xDrip so I would strongly prefer to see that arrow direction derived by xDrip always sent to the watch (via NightScout) instead - even in Native Mode.

[sweetafro]

Same issue here. Watch trend arrow and phone trend arrow don't match.
Running latest nightly xdrip+, G6 8H series transmitter, Zenwatch2, Moto G7.

[Navid200]

There doesn't seem to be any active developer addressing WearOS concerns.
We can always reopen if such a developer joins.