-
@mmain
It depends of course whether you're presently running the latest version or not. If it's the latest then a downgrade might fix it, if it's an older version then an upgrade is appropriate, far less risky and much easier. Please supply answers to all 3 questions below as fw manipulations can be a little dicey and certainly more so without knowing some history of the device.
- Did you do a fw upgrade just before these RTL errors started?
- Has the DA50 ever been cross-flashed? e.g. APEC device had US/EU fw loaded or vice versa?
- What device do you have, US/EU (HWID 2270) or APEC (HWID 2596)? Look here to check: [Only registered and activated users can see links. Click Here To Register...].
I have only one old version of US/EU (V5.40) as well as current US V5.90 & APEC V2.70. it's more difficult to find older versions since [Only registered and activated users can see links. Click Here To Register...] went offline.
-
@Butters, please find below responses
Did you do a fw upgrade just before these RTL errors started? It started with the upgrade to 5.70, however, 5.70 resolved a problem I was having with Garmin SmartLink on iOS at the time
Has the DA50 ever been cross-flashed? e.g. APEC device had US/EU fw loaded or vice versa? No
What device do you have, US/EU (HWID 2270) or APEC (HWID 2596)? Look here to check: How to find your Garmin Device's HWID. It'2 2270
-
Have you tried using the device at the problem locations without your iPhone linked?
-
Yes, have run with bluetooth disabled, just the same
-
So much for that thought then.
The chance of this glitch being fw related now seems likely being as you've indicated it started when v5.70 was loaded. Did you have any problem with SmartLink using earlier fw (before v5.70)?
-
Yes I had a problem when the app was upgraded to 2.9.0 revision with the earlier 50 LM firmware, which 5.70 and 2.9.2 resolved, not sure which of these actually resolved the problem of no communication from Smart Link for traffic / waypoints etc; smart notifications were unaffected and I never used bluetooth phone capability. Also, this was iOS 11.4 at the time.
-
To sum up:
- V5.40 fw or 2.9.0 Smartphone Link (or combination thereof) broke the app's connectivity
- V5.70 fw or 2.9.2 SmartphoneLink (or combination thereof) restored it but then the shutdowns started
Questions:
- Is above summation correct?
- What version of fw is on the DA50 now, 5.70 or 5.90?
- What version of the app is now on your iPhone?
I note that there were SIX separate updates for various fixes issued for the app over 15 months, from 2.9.2 on June 7 2018 to the latest being 2.9.8 on Sept 9 2019. Nothing since so the app's likely stable with 2.9.8 and it's minimum system requirement is iOS 11.4.
-
@Butters your summation is correct, currently running 5.90 and 2.9.8 respectively, now on iPhone 11 pro on iOS 14.7.1, was previously iPhone 6S
-
Therefore the only remaining potential software solution is to downgrade the device firmware to below V5.70. If that doesn't work then there's possibility of a hardware fault of some kind (unlikely imo, due to the specific nature of the errors and the fact they are RTL Traps).
If you want the V5.40 fw and/or assistance to downgrade just ask and i'll make you a flash kit. No responsibility however, the risk although slight is all yours if you downgrade. The other alternative is do nothing and see if a future fw version or map update fixes it for you.
-
@Butters, I would like to take up your offer of firmware and downgrade assistance. Many thanks for your support and perseverance with my problem
