Well it is difficult to reproduce without providing our full app.
Our architecture is a series of carousel pages that contain the circular gauge on them.
When the pages are added to the CarouselPage the circular gauge is created in the constructor of each page.
If the user taps on the gauge a new page is presented. When the user comes back to the page with the gauge on it from the child page, this is where the range is rendered incorrectly after some time. The rendering problem can also occur if the page with the gauge is displayed when the app resumes.
It seems like it has to do with the gauge being created in the constructor of the CarouselPage.