Magic 8 Ball on the VivoCube + a few bugs and requests

UltraBARX
1

I built a Magic 8 Ball for the VivoCube. Tap the ball and it shows an answer for 8 seconds, then goes back to the ball.

magic8ball

magic8ball-ball
magic8ball-ball540×960 43.3 KB

How it works

  • The cube shows the ball alone on layer 1 and three answers on layer 2, all custom images.
  • The ball’s Click action is Open App, which opens a small Android app on the CoreBar. The app picks a random answer and switches the cube to it with the same layer-switch message the launcher uses.

Bugs (CoreBar LineOS 1.0.3. These are on the CoreBar/VivoCube side, so they should affect Windows users too; I tested with the macOS UltraWorkSpace 1.0.0.14)

  1. Only the first VivoCube button runs its actions. Every later button gets a doubled scene id, and the bar logs “场景不存在” (scene doesn’t exist) when it’s pressed. The LineOS 1.0.8 code on GitHub fixes this, but my bar is still on 1.0.3. How do existing bars get 1.0.8? Installing LineOS_v1.0.8.apk from GitHub on its own doesn’t work: the modules stop responding.
  2. The “App opened” automation trigger never fires. No matcher is registered for APP_STATE, and 1.0.8 is the same.
  3. Only 2 VivoCube layers can be switched to. Layers 3–6 are refused even when deployed. Does the VivoCube_V2_20260728 firmware change this?

Requests
4. An official way to switch the cube’s layer, and to run an automation, through the 7431 API. Act 1204 (SCENE_TRIGGER) is defined but has no handler.
5. A random action (pick one of several actions). That alone would let anyone build this without writing an app.
6. An option to hide the page dots when a layer has more than one widget.
7. Document the cube’s limits: about 1 MB of images per deploy (more shows a red X), and the visible area (images at 100% get clipped; about 88% fits).
8. Let Choose Icon accept a local PNG, if newer builds don’t already. I only see the online library in the macOS app.

2

Hi Xacto,

Thank you so much for testing our beta version and sharing your feedback with us. We’re delighted to hear from you. Here are our responses to your suggestions:

  1. The VivoCube can switch between only the first two pages and won’t access the following pages

    We’ve confirmed that this is a bug. We’re planning a major VivoCube update soon to address the issue.

  2. Uploading custom icons from a local device

    This feature has already been added to our development roadmap.

  3. Automation features

    We’ve made some recent changes in this area. Automation requires an upgrade on the CoreBar, and the feature is still being tested. You’re welcome to try the beta version early. To upgrade, go to Settings → About, long-press the LineOS module, and then enter the passcodes 3344 and 3355 in sequence.

  4. Hiding the page indicator dots on the VivoCube

    We originally added the page indicator dots to help users see which page they’re on when they have configured multiple pages, so we believe they serve a useful purpose. However, we’ll pass your suggestion to the relevant team for review.

We look forward to hearing more of your feedback!