hSoftware Garmin Connect IQ Apps - Case [00541] Data-field Crash after Smartphone update by Bluetooth

Case - [00541] Data-field Crash after Smartphone update by Bluetooth

Details

Reference:	00541
Type:	Issue
Product:	hHRZone 5.2 (18 July 2017)
Title:	Data-field Crash after Smartphone update by Bluetooth
Device:	Fenix 5X
Priority:	Major
Raised On:	04 September 2017 15:51
Raised By:	author
Status:	Open-Development-Ready-Closed
Description:
I've Changed refresh interval from 5 sec to 2 sec by my phone (Fenix 5X was connected by Bluetooth). After that when HR face was changed - Data-field was crashed - screenshot - https://www.dropbox.com/s/cchhjr1swxgtez1/HR-error-2sec-update-by-sdmartphone.jpg?dl=0 I've tried to change intervasl back - it doesn't work for me :-( I've installed last value 10 sec back by USB cable via Garmin Express and sync Fenix 5X - it's working now.
Closed:	05 November 2018 15:32 (Cannot Reproduce)

Related Cases

00536	Introduction	hHRZone		Closed
00537	High HR custom level for graph	hHRZone		Closed
00538	Min - Max HR values on the graph	hHRZone		Closed
00540	Wrong directions for HR and Elevation data-field	hHRZone		Closed
00542	HR graph was cleared when activity paused and started again	hHRZone		Closed
00543	Current HR value doesn't change on graph	hHRZone		Closed

Subscribers

There are 2 Subscribers watching this Case.

Comments

5 older comments (click to show)
04 September 2017 17:31 Aauthor	P.S. Could you check my registration credentials? I've got 2-3 duplicates of each messages login - author@prostabzor.ru
04 September 2017 18:17 AAdmin	Thanks you for the log. Are you using an Android phone? PS I've check the multiple messages, and can't see a problem. Let me know if it continues.
04 September 2017 18:29 Aauthor	yes, here it is info: -------------------- Phone - Samsung Galaxy S7 Edge OS - Android 7.0
10 October 2017 08:23 AAdmin	Hi, Can you try the latest update for me, as I've made some major changes behind the scenes?
05 November 2018 15:32 AAdmin	Case closed, as unable to repeat.

This case is now closed

CommentLinkSubscribeReturn