App not showing on Hisense M2 Pro projector after install and unable to enable developer mode

[jpdom]

Describe the issue
Tested installation on my Hisense M2 Pro projector. The install reports success, but after restarting, the app does not appear. Tried the following steps:

• Attempted to enable developer mode, but the remote does not have number buttons. Tried inputting 1234 in the About screen via both the app and on-screen numbers, but developer mode could not be enabled.
• Device version: V0000.09.01X.P0609
• Extended version: X.P0609.X0003.W01.Y01.J01

Expected behavior:
App should show up after successful installation.

Actual behavior:
App does not appear after restart. Unable to proceed.

Device details:

• Model: Hisense M2 Pro projector
• Version: V0000.09.01X.P0609
• Extended version: X.P0609.X0003.W01.Y01.J01

Additional context:
If more logs or device info are needed, please let me know what to provide. Any workaround for enabling developer mode without number buttons would also be helpful.

[NoobyGains]

I pushed a fix set aimed at the false-success install path.

What changed:

• Method 1 no longer spoofs all DNS queries. It now only spoofs vidaahub.com and forwards everything else upstream.
• The installer now serves the UI and icon assets locally during install, instead of depending on remote GitHub Pages assets in the middle of the launcher install flow.
• The direct browser install prompt no longer writes a permanent localStorage installed flag after a status === 0 callback. If VIDAA reports success but no launcher entry is created, the prompt can appear again on a later visit instead of silently disappearing forever.
• Docs were updated to call out that some newer VIDAA firmwares/projectors appear to accept the install request but never create the launcher entry.

Commit now live on gh-pages:

• b9ccea8 Fix VIDAA installer DNS and launcher prompt flow

Verification:

• npm test
• Result: 67/67 Playwright tests passing

Please retest with the latest gh-pages build:

1. Run the updated installer/server.py
2. Point the TV/projector DNS at that machine
3. Open https://vidaahub.com
4. Install, then fully reboot the device

If the launcher entry still does not appear, that suggests the remaining issue is firmware-side blocking of Hisense_installApp() even when it returns success.

If you retest, please include:

• exact model
• VIDAA / firmware version
• whether the install page reported success
• whether the launcher entry appeared after a full reboot

[NoobyGains]

There is a second follow-up fix live on gh-pages now:

• ff086d7 Fix service worker rollout and DNS fallback behavior

What changed:

• bumped the service worker cache so older cached shells are replaced more reliably
• switched the app shell to network-first so deploys roll out instead of staying stale
• installer DNS forwarding now prefers the host machine's configured DNS servers, with public resolvers only as fallback
• launcher prompt now suppresses for 24h after an accepted install instead of either reappearing every session or disappearing forever

If you tested earlier, please retest again with the latest build and do one of these first:

• close and reopen the TV browser
• or clear the TV browser cache
• or add a cache-busting query like ?v=ff086d7

Then try Method 1 again and report:

• exact model
• VIDAA / firmware version
• whether the install page reported success
• whether the launcher entry appeared after a full reboot