Wolvic for Pico G2
Historical Wolvic home page running inside the Pico G2 virtual environment
Pico G2 / G2 4K · Community port

Wolvic for Pico G2

A newer web and VR video entry point for Pico G2. Built on Wolvic 1.6.2, GeckoView 128 and native PicoVR.

Historical Pico G2 capture · single-eye crop · not the current release UI

GeckoView 128Browser engine
Native PicoVRLegacy runtime
3DoFHead tracking and controller
arm64-v8aTested on Android 8.1
01 / The port

A browser port for this headset

Native display, video handoff and player controls adapted around real Pico G2 workflows. An independent community project, unaffiliated with Wolvic or PICO.

01

Native PicoVR and WebXR

Restores the G2 legacy PicoVR backend on Wolvic 1.6.2 with GeckoView 128. Preserves 3DoF tracking and controller input, with historical device records for browsing, video textures and immersive WebXR.

02

Video crop and projection fixes

Corrects video Surface sizing and wait order to address persistent fullscreen cropping and projection-switch white screens. Native 2D, 180°, 360° and stereo modes are available; special projection models have separate limits.

03

Hamezo native video handoff

General video tools hand off the media and its renderer instead of enlarging the entire page. The Hamezo Video.js VR path has historical device acceptance. After native takeover, a reload may be needed to restore the site VR button.

04

Per-page Quest UA fallback

If a non-desktop site does not offer a usable immersive entry, apply Quest/Oculus UA to the current page and reload. The previous UA returns after leaving. Historical checks cover Pornhub / YouPorn, not every website.

05

Immersive controls and hover

A shared MGP SVG / CanvasTexture layer addresses black icons and adds the YouPorn VR activation condition. The shared native choice widget also fixes single-row hover flicker. User acceptance records cover these fixes.

06

Real same-video codec choices

Player and protocol discovery shows the menu only for at least two confirmed playable, switchable codec families. Natural Eporner H.264 / AV1 switching passed in both directions. Resolution is not a codec; recovery and other adapter limits remain documented.

02 / Download

Download and versions

New release · tested baseline / static APK audit

Wolvic 1.6.2 / 2026-11-13

The 2026-11-13 build adds general video tools, native handoff, codec selection, per-page UA and player fixes. Functional assets match the final tested baseline; the relabelled APK has not had a separate headset installation.

About 110 MiB · arm64-v8a · unofficial prerelease

Still available · older fallback

Wolvic 1.6.2 / 0052

0052 has historical device acceptance for the native backend and early projection fixes, without the later complete codec tools.

The new build retains the test package ID and coexists with 0052, without sharing or automatically migrating browser data.

Download the 0052 fallback
03 / Evidence

What has been verified

The current release retains historical device work. Codec evidence distinguishes the final functional baseline, historical natural pages and controlled tests. Functional assets match, but the relabelled APK has not had separate headset installation acceptance. An adapter is not proof of support on every website.

PathEvidenceBoundary
PicoVR / WebXR0052 device acceptance for playback, tracking, controls and textures.Pico G2 family scope; not a current OpenXR build.
Handoff / projectionHistorical native handoff on paths such as Hamezo, plus user regression checks.Page fullscreen, native projection and site VR stay distinct; special projection models are not universally supported.
Video.js / VHSNatural Eporner H.264 / AV1 switching in both directions.A manifest timeout is recorded; no universal success or performance claim.
xPlayerHistorical natural xHamster dual-codec and quality-mode checks.Not fully rerun in the final APK; the video must actually offer two codecs.
HTML / hls.js / dash.jsControlled device player, state and recovery tests.Not proof of natural dual-codec support on arbitrary websites.
Shaka / MGP / DelightControlled switching and varying natural binding or discovery evidence.Natural dual codecs, audio, quality mapping and VR combinations still have specific gaps.
Bilibili / ordinary pagesSite controls retained; historical ordinary-use regression feedback.The last round did not verify every quality and VR combination.

Full evidence matrix and known limits

04 / Installation

Install on Pico G2

Use the headset package installer or ADB from your computer. Verify the downloaded APK with SHA256 first.

  1. Download and verify

    Download on the headset, or transfer the APK from your computer into its Download folder.

  2. Open the Android installer

    Allow the installation source when prompted. ADB users can use the commands alongside.

  3. Launch and browse

    Open Wolvic Pico G2. Check ordinary browsing and playback before a site immersive entry.

adb devices
adb install -r .\Wolvic-1.6.2-picog2-20261113-arm64-signed.apk

These commands install the new build over the same test package. 0052 has a different package ID and can coexist. Uninstalling either app deletes its own data.

New-build installation and rollback

New APK · SHA256AFA8E6451E1E5F5871497729A161F7834606E6FE2612281A59B1F55C42A8B950

Before you download

Is this a Firefox Reality alternative for Pico G2?

It is a community alternative based on Wolvic 1.6.2 and GeckoView 128. It brings a newer web engine to Pico G2, without promising compatibility with every modern website or streaming service.

Can I use it on Pico 4, Neo, G3 or Quest?

This port targets the Pico G2 / G2 4K family. The tested device is a G2 running Android 8.1; builds are arm64 only. Other headsets are unverified and should use their officially supported browser.

How do site VR and native projection differ?

Start playback on the ordinary page first. The site VR entry uses its own immersive player; the browser extension named “VR 视频工具” provides native projection and per-page UA. Page fullscreen, site VR and native projection are distinct paths. Operate the extension from the ordinary page. Native takeover of some renderers may require a reload before site VR works again.

Why might the media-source menu be absent?

Codec selection requires at least two verified playable codecs for the same content. Single codecs, resolution-only choices, unknown identity or unsupported playback stay hidden. The older 0052 build does not include the complete codec tools.

Will H.264 or AV1 necessarily play more smoothly?

No. Network, bitrate, resolution, player and device decoding support all affect playback. The recorded tests demonstrate switching on specific paths, not a controlled same-spec performance comparison.

What if video stops or the display goes black?

Separate network failures from decoding problems and test ordinary video first. A full headset reboot recovered a historical codec/Surface resource failure; that is a recovery method, not a proven permanent fix.

Is this an official Wolvic or PICO product?

No. This is a community legacy-device port using native PicoVR rather than the current picoxr OpenXR backend. Derived source is MPL-2.0; third-party components retain their own licenses.