I’ve been using this tablet – model # SM-T500 – for my Zwift display for the past 4 years. Recently, it’s started being flaky: sometimes, I can get a ride in, sometimes it just crashes to the Android desktop on or near the start of a route. And during rides, I occasionally see the graphics start getting all choppy, which is a prelude to a crash.
Software, including Zwift and OS, is up to date.
This device appears to be within the specified device limits for Zwift (as documented here in the " Supported Devices to Run Zwift" page). Available storage: 16.8 GB, Memory 806 MB.
Any clues or suggestions?
I wonder if it’s related to the recent change to Android graphics quality as speculated over here…
Also I think @Run.10K.Every.Day has one of those tablets
I do and having the exact same issue.
Only way i can prevent it is to ensure absolutely nothing else is running at the same time.
Even then performance is juddery.
Luckily my tablet is only used for fan viewing and is not my main zwift device.
Definitely linked to the recent graphic improvements which has tipped this tablets ability to run Zwift over the edge.
Thanks, Paul. Don’t think that my tablet would be affected by that change, as the change is for Android devices with 4GB or RAM; mine only has 3GB (with about 750 GB available). Maybe I’ll try to free up some RAM, anyways.
That being said, the behavior of the graphics before it fails is suspiciously chunky/blocky looking (when I see it, that is; sometimes it just crashes right away). Maybe their available RAM for textures detection is wonky.
Thanks, Stuart. That’s interesting, and at least somewhat confirmatory. The timing of my crash experience vs. the latest update that can use larger textures is indeed suspicious.
I am using this tablet for the main Zwift display, with an old Android phone for the Companion.
My wife also has an issue but with her Samsung Galaxy S6 lite, but its with bluetooth dropouts during her rides, and there is no definite time. It can happen .5km into a ride, or it can happen 500m before her ride ends.
It seems to be from the Zwift updates because it usually gets fixed on one update, then it will fail on the next update. This past update it fails, so she has to use my Galaxy Tab S5E which is an older tablet.
I believe the 4gb was a guide and that devices with less RAM would also see some improvements.
It seems to me that it’s the changes related to the new textures – when things start going badly, the display gets really laggy and jaggy and jittery for a bit before Zwift just dies. There’s no setting to use the old, coarser textures on Zwift on my tablet, at least that I’ve been able to find.
No updates available today, so I’ll just have to try it again.
It’s tricky to ride with ones’ fingers crossed… 
Yesterday my event was in Makuri. It loaded but within a few seconds crashed and terminated.
Reloaded and all good. It’s certainly unstable.
Glad to hear it.
I reported my symptoms to a separate discussion on “Poor graphical quality on Android”
I did figure out how to clear the cache, as recommended there, and that seemed to work, once. Will try again tomorrow to see if that was the answer, or just a lucky break, in which case, something else it awry.
Here again to report the the cache clearing step doesn’t always work. Today I shut down my tablet, started it up again, cleared the cache, loaded Zwift and started a pacer ride. About 10 minutes in, the graphics went jittery, and the app crashed to the home screen. I then repeated the whole sequence, and was able to get a ride in.
Hoping that this fixed in the next update, whenever that is…