Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

RWGPS IQ app not rendering properly.

spiderbundy
over 5 years ago

Just wondering if anyone else has noticed this when using the RWGPS iQ app to Download pinned rides to the 1030. Everything looks grand until you get to the Download screen and it doesn’t seem to render properly on the unit.  

  • 0 over 5 years ago

    I am currently running ver. 9.24 on the 1030 and rwgps app ver 1.2.2 and I am not experiencing the same issue. I would recommend syncing via express and see if that fixes it. if not you may also try our 9.25 beta sw version that is listed as a sticky at the top of the Edge 1030 forum page. Only once you have covered these trouble shooting steps would I recommend that you contact the developer through the apps page in the IQ store. 

  • 0 over 5 years ago in reply to Garmin-Duncan

    Hi Duncan and thanks for the reply. Running 1.2.2 myself but not on a beta version of 1030 firmware. 9.24 is still beta as far as I’m aware. (Running 9.10) 

    Syncing with GE doesn’t make any difference either. 

  • 0 over 5 years ago in reply to Garmin-Duncan

    Also tried deleting the app from the unit and reinstalling. Didn’t make any difference. Still not displaying properly. 

  • 0 over 5 years ago in reply to spiderbundy

    I'm running RwGPS app 1.2.2 on 9.25 beta with no problems on my 1030. I don't recall any issues on 9.24 either.

    There were some downloading issues on the Fenix 6 where the watch would hang when downloading & never complete but that seemed to get resolved with the beta 5.75 on that device. While I was having issues with the Fenix 6 though the Edge, which was on f/w 9.10 would download without issue.

    Are you downloading over GCM via BT or direct via WiFi? If you have WiFi on the edge enabled & connected the App will download via WiFi even if you have a BT connection to your Phone. If WiFi is/isn't enabled & connected you could try disabling or enabling it and see if that helps with your downloads  

  • 0 over 5 years ago in reply to hotdogpartysausage

    My rides download no problem. It’s just how that actual page renders. All other pages up to and after downloading display properly. 

  • 0 over 5 years ago in reply to spiderbundy

    Sorry I misunderstood your issue. No rendering issues here on any f/w. I'm sorry I can't help you more

  • 0 over 5 years ago in reply to hotdogpartysausage

    On the edge 1030 I have the same problem. Downloading with wifi is no problem, downloading with BT keeps it hanging. :( 

  • 0 over 5 years ago in reply to gABBY025

    I do not believe this is the same issue as the original poster has reported. You may want to contact us at support.garmin.com for further assistance with the issue you are experiencing. 

    Just to clarify the original poster is reporting an issue with the rendering of the home page of the RWGPS IQ app. Not a download issue.

  • 0 over 5 years ago in reply to Garmin-Duncan

    That’s correct Duncan.  It’s not the home page of the RWGPS IQ app but just that one page which allows me to Download or Download and ride. (Actual downloading works as expected)

  • 0 over 5 years ago in reply to gABBY025

    Is it hanging or just taking an age to download (but does eventually download the route)?

    For me downloading a route over WiFi takes seconds whereas if I do it over BT via GCM it will take several minutes. In fact it takes that long that when downloading using the GRouteLoader widget I have installed; if I don't keep tapping the screen every now & then the edge will go to sleep!!!!

    BT download used to be much quicker but I don't know if something changed within the Edge 1030 f/w or GCM but downloads via that method have been painfully slow for some time.

    Forgot to mention to the OP. I had a RwGPS issue a little while back following the f/w update on the 1030 & I had a good response from using the Contact Developer link for the app in the IQ Store where we were able to identify & fix the issue