Skip to content

fix: refresh Android VR client profile - #1482

Open
Serph91P wants to merge 1 commit into
anxdpanic:masterfrom
Serph91P:fix/android-vr-pico-profile
Open

fix: refresh Android VR client profile#1482
Serph91P wants to merge 1 commit into
anxdpanic:masterfrom
Serph91P:fix/android-vr-pico-profile

Conversation

@Serph91P

Copy link
Copy Markdown

Summary

  • refresh the ANDROID_VR client profile from Oculus Quest 3 1.65.10 to Pico 4 1.73.21
  • preserve the existing VR OAuth and stream processing behavior

Background

Issue #1481 reports adaptive stream requests failing with HTTP 403 when the add-on uses the existing ANDROID_VR profile. The current profile identifies as an older Oculus Quest client. Updating it to the current Pico 4 profile restores usable adaptive stream URLs in the reproduced case.

Scope

This is intentionally limited to client profile maintenance. It does not change client ordering, stream merging, authentication behavior, or implement a PO token provider.

Validation

  • python3 -m compileall -q resources/lib
  • targeted assertions for the generated Android VR identity, omitted Innertube platform field, and preserved VR auth type
  • kodi-addon-checker . --branch=nexus
  • live playback on LibreELEC x86_64 with the Pico 4 identity confirmed adaptive manifest parsing, 4K availability, and more than three minutes of playback without HTTP 403, inputstream.adaptive errors, or player restarts
  • the submitted diff additionally omits platform: MOBILE; this final adjustment passed compile and targeted profile checks but still awaits another live playback run

Acceptance criteria

  • adaptive playback no longer stops because ANDROID_VR URLs return HTTP 403 in the reproduced case
  • VR OAuth behavior and stream processing remain unchanged
  • the client context contains the Pico 4 identity without an unsupported platform override

Addresses #1481

Update the Android VR identity from the older Oculus Quest
profile to the current Pico 4 client while preserving VR OAuth
and stream processing behavior.
@popcornmix

Copy link
Copy Markdown

Tested this last night and it did fix my playback issues from #1481

@koentinius

Copy link
Copy Markdown

This fixed playback issues for me. Thanks for your effort!

@pepszzi

pepszzi commented Aug 18, 2026

Copy link
Copy Markdown

This works, thank you!

@ehoffman2

Copy link
Copy Markdown

Tested the patch, working fine so far...

Now... Here we go again... Cat and mouse. How long until Google block this new "device" (checking if it's actually a real Pico).

In the meantime, thank you for this patch. We can't control what G will do next and when, but a least we can try our best to find new ways around!

@KerballOne

Copy link
Copy Markdown

Is there a debug release with this patch? If not, how does one apply this on Kodi?

@celesteweforget

Copy link
Copy Markdown

Manually patched, seems to work well!

@BehnK

BehnK commented Aug 18, 2026

Copy link
Copy Markdown

Is there a debug release with this patch? If not, how does one apply this on Kodi?

Easiest way is download the Zip of 7.4.4, find the file and change the details then reinstall YouTube addon from that altered .zip

@yansunomo

Copy link
Copy Markdown

Thanks for this patch, working like a charm !

@Fabbzz

Fabbzz commented Aug 19, 2026

Copy link
Copy Markdown

Finally; thanks! I was stopping, pausing, etc. too much :)

/edit: something I noticed is that it repeats the video instead of stopping at the end.

@turbo-donkey

Copy link
Copy Markdown

Three days in this is working for me.

@Jalle19

Jalle19 commented Aug 19, 2026

Copy link
Copy Markdown

Fixed recent playback issues for me as well 👍

@TasPats

TasPats commented Aug 19, 2026

Copy link
Copy Markdown

this fixed my system

@christianhaitian

Copy link
Copy Markdown

Confirming that this resolves playback issues on my end as well on the latest version of osmc on a raspberry pi 4 with 2GBs of ram.

@Serph91P

Copy link
Copy Markdown
Author

@anxdpanic can you please take a look? Thank you!

@KerballOne

Copy link
Copy Markdown

How do these client profiles actually work?
Does it go in order and uses the first one that works? If so, then shouldn't it detect the error and Go on to the next client profile? Or would that not be possible because the error happens after?
Or does it pick a random profile each time?

@Tauli-gif

Tauli-gif commented Aug 20, 2026

Copy link
Copy Markdown

The stream kept freezing for me and Kodi crashed. Nothing worked anymore except for a manual restart. Now it's working again. Thank you very much.

@fix666

fix666 commented Aug 20, 2026

Copy link
Copy Markdown

Fixed the issues for me. Thank you!

@repitah

repitah commented Aug 21, 2026

Copy link
Copy Markdown

Confirmed working

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.