YouTube shorts play at double speed after initial playing

urban_crawler​ Ak70​ NMGeekmom​ 

While this particular ongoing YT "shorts skipping" issue is frustrating (there are many others, both currently and historically, for different models/model types - more on this later) and you might not like atc98092​'s response, it is in fact accurate - this is entirely of Google's creation/responsibility to fix .

FYI a few points of fact about the RokuOS YouTube/YouTube TV apps: 

1. Google entirely codes the YT/YTTV apps, including the common library (cobaltlib - hidden middleware code library) they both rely on.
2. YT/YTTV apps consist of a platform layer/version downloaded/updated from the platform's app store (e.g Roku Channel Store), and a UI layer/version downloaded/updated from Google's servers @ app runtime (yes - each YT/YTTV app has two different versions  (platform+UI) that work in combination to support specific features/functionality).
3. YT/YTTV app platform updates are almost always released in coupled version+build pairs (YT+YTTV) for specific models/model types (e.g. Legacy, HD, MStar C2 Soc, RTD 131x SoC, RTD 161x SoC, 4K/HDR, Ultra, Roku TV,  "Newest released model", etc) - this means there are significantly/slightly different YT/YTTV app platform versions/builds for different models/model types.
4. Google often links YT/YTTV app platform updates to specific RokuOS firmware versions/builds (e.g. 14.1.4 & 14.5.4 and 14.6.4 may each have different YT/YTTV platform versions/builds for a given model/model type)
5. YT/YTTV platform app versions/builds updates are released in certain "tracks" or "paths" - meaning certain major versions (e.g. 2.22/2.23/2.24/2.25) only apply to certain models/model types, and they will only get builds within that version.
6. because of the above situation @ any given point in time, there can be up to 10 different YT/YTTV app platform version pairs for different models/model types using the same RokuOS version/build.
7.  If different "current" major RokuOS versions/builds are included in this, there can be 20-30 different YT/YTTV app platform version/build pairs.
8. (and this doesnt include UI layer updates, which are downloaded @ app run time, and may be different depending on when the app was loaded - which can get us to 40-60 different YT/YTTV platform+UI layer version/build pairs).
9. Google controls which specific YT/YTTV app platform version/build pairs (e.g. 2.24.245/2.24.102) apply to which specific Roku models (e.g. 4800/4801/4802) with which specific RokuOS versions/builds via their developer control panel @ The Roku Channel Store
10. Considering all of the above information, it becomes pretty clear that Google having to track and support so many different RokuOS YT/YTTV app platform version/build pairs for different models/model types AND RokuOS versions/builds results in Google eventually/sometimes losing track of which RokuOS YT/YTTV app platform versions/builds apply to which models, and the WRONG RokuOS YT/YTTV platform app version/build is sent to a model/model type.
11. In addition to the above, due to Google having to track so many different RokuOS YT/YTTV app platform versions/builds inevitably leads to a lowering of code quality/app behavior because they cannot possibly keep up with all of the resultant behavioral differences.
12. Just like with all modern software (especially as a "service"), including Windows OS, RokuOS, Android TV OS, networked apps, etc etc, we (users) are the QA/QC and (involuntary) beta testers of their software/services updates - many/most issues are only known/solved/resolved due to external specific user usage feedback, and not via internal testing.
13. Google chose to use different YT/YTTV platform app versions/builds for different Roku models/model types and/or RokuOS versions/builds, and created their own ongoing support nightmare.

Examples of 7 different current YT versions/builds w/OS 14.5.4 build 59xx:

AML S905Yx (3830): 2.25.160

RTD 131x (394x/382x): 2.25.159

RTD 161x (4850):  2.25.158

RTD 131x (3840):  2.25.157

RTD 131x (480x/396x):  2.24.245

MStar C2 (4670/3810): 2.22.130000106

MStar C2 (3910/3800):  2.20.110005163

** Notice that there is a single build difference for 4 different models/model types **

As for this specific YT "shorts speedup" issue: its only noticed on certain models (e.g. 48xx Ultra) with certain firmware versions because the YT app platform version/build updated relative to the firmware version, and is a model/model type specific YT version/build - this is entirely within Google's control (of both the app's code, and the app version/build applicability via their Roku Channel Store update manager developer control panel)

As for Roku's CS agents/product managers interfacing with Google YT/YTTV RokuOS app developers/engineers/platform provisioning: This is relatively limited, and would/does consist entirely of Roku passing along their ticket/case/issue information, waiting for Google's YT/YTTV RokuOS app developers/engineers/platform provisioning to do whatever it is they are going to do (platform app update, server-side provisioning change) and communicating that result back to them if/when it occurs, and if done in a timely manner (before fix release/change) communicating that to the CS agents/managers here in the community forum who then may provided an updated "Solved" post - its merely communications window dressing and has absolutely nothing to do with enhancing or improving the timeliness of a given third-party app's/service's issue being fixed.  It may make you/us "feel better" regarding Roku's support, but has zero actual impact on if/when/how a third-party app/service issue is fixed.

(FTR in case it matters: I may be considered an "expert" on Google's RokuOS (and other platform) YT/YTTV apps/service/development/deployment: both Roku community users/staff and Google's engineers/CS have in the past used content from my previous posts on this topic (YT/YTTV versions/builds) to address/fix specific problems related to incorrect RokuOS YT/YTTV platform app versions/builds being applied to specific Roku models thinking that the content was provided by Google and/or Roku engineers when in fact it was provided by me - ergo if Google CS/engineers, Roku CS/engineers, and Roku users are all referencing/using my content/knowledge to address/fix problems with the YT/YTTV apps on Roku devices, then that probably makes me some kind of "expert", if thats a concern for the validity of post content)