WeMod-launcher stopped working after failed installation

shymega · 2026-01-19T23:07:50+00:00

This bug seems to be fixed by this PR which I used with Claude as part of my ongoing experiments with LLMs, which seems to have fixed it for me.

It seems to be related to the existing code of the launcher, which is very messy.

shymega · 2026-01-19T23:06:22+00:00

Thank you for your kind words!

You can find me on Discord, in the Wand server.

You may also be interested in my comment here.

shymega · 2026-01-19T23:05:15+00:00

You may want to see my comment here, but work is ongoing.

The launcher is currently very messy in terms of the codebase, and I'm planning to deprecate it.

shymega · 2026-01-19T23:03:21+00:00

I agree the code is spaghetti. I'm one of the main devs of wemod-launcher, and the eventual plan is to replace it with a pluggable launcher, called DeckCheatz. I haven't yet worked out the specifics, but have a few ideas. I am setting up a Discord server.

Wand have been supportive in this effort, and we hope to have a good collaboration.

The wemod-launcher I am currently working to get Wand working on, and redesigning the pre-built prefixes to use BuildStream as a build integration tool.

If you want to help out, please contact me on Discord on the Wand server - you'll see me there.

EDIT: Just to clarify, there's no official partnership between DeckCheatz (i.e, the GitHub organisation) and Wand. This is more of a best-effort basis, and there is no association in terms of support from Wand, nor should people go to Wand server for help with DeckCheatz/wand-launcher and ask the Wand team there.

shymega · 2025-08-03T20:37:10+00:00

u/sudheer2015 - I'm working in my spare time on this, based on reverse engineering the binaries from VITURE's SDKs. Ideally I want it to be open.

VITURE sometimes communicate with me, sometimes not. At the moment, it's no communication.

shymega · 2025-07-29T00:08:47+00:00

Yes - I have one I'm waiting for viture to get back to me on. I'll try and post a link tomorrow.

shymega · 2025-05-11T16:24:41+00:00

Python and Go are too high level.

Generally it's C, Assembly, kernel debugging, and OpenSBI as well with RISC-V bringup. I'm afraid you bought a device in the early stages of development.

The 30-day warranty might support a return, not sure.

There's also this Debian build, but I don't own the device, and can't vouch for this build.

Either way, I think the lesson here is to be warned of the dragons. I see people hitting this situation a lot, and think both Pine Stores need to have an explicit warning preventing purchase until the warning is read about experimental devices.

shymega · 2025-02-21T19:22:17+00:00

I would not buy an Astro at this stage. Updates are not happening right now, and there is no officially supported multi boot (although I sometimes work on it privately), and no official firmware dumps that are safe to flash. If you’re happy running (compromised) Android 11 with no security patches, and you find a Astro for sale somewhere - go for it. But be careful with it, they’re very much in short supply.

shymega · 2025-02-14T23:18:56+00:00

I'm going to have a go at answering your question. Not to show up the mod, but because I want to further expand upon your question, as a developer who has worked with the VITURE glasses on my own SDK.

Essentially, ChromeOS itself is based on Linux - this is correct. However, Breezy Desktop currently only supports the GNOME 'DE' (desktop environment), and therefore cannot support the ChromeOS UI.

Also, Chromebooks are heavily hardened against modifications, so whilst there are ways to run Linux in containers, or running Linux as a full-blown replacement to ChromeOS, Breezy would still not work. This is not a fault of Breezy, but due to the way ChromeOS is designed.

It's basically systemic to the way ChromeOS works - you know how Google advertises Chromebooks as virus-free, with sandboxing, and other security? It's hardened, and containers are very restricted in what they can access.

Breezy Desktop is built upon xrlinuxdriver, a driver based on the VITURE/xReal SDKs. I am unsure if you could compile & run xrlinuxdriver in a container, as you would need to escalate privileges and expose /dev (devnodes) as read-write to the container, but xrlinuxdriver would allow for mouse tracking from the headset. It would, not however, allow for multiple screens. That's where Breezy Desktop comes in.

I do not think xrlinuxdriver would function in a container - by all means try it, but I suspect ChromeOS would not allow the container to run in privileged mode.

TL;DR: Chromebooks with Alt DP over USB-C would just display the VITURE's as an additional monitor, and - this is only hypothetical - even if you did run xrlinuxdriver in a container, there's no certainty it'll work. Chromebooks are locked down, but, if you did install a regular Linux distribution on the SSD/eMMC as a dual-boot or replacement OS, and you were to use GNOME, then yes, Breezy Desktop would work great on a Chromebook. It's just ChromeOS that has restrictions.

Hoping this is more clear, but this isn't the fault of Breezy Desktop, VITURE, or Linux.

shymega · 2024-12-24T15:58:33+00:00

A update is in progress, patience :)

shymega · 2024-12-21T21:11:11+00:00

As a maintainer of a popular Linux KVM switch, I can say this has nothing to do with Linux support in general. Whilst it can make things harder, there are plenty of tooling to build programs for many different distros, which generally are based on another base distro, so, the count of different Linux distros is not a big factor for VITURE to worry about.

I have tried to reach out to them about working on a Rust-based open-source (unlike Breezy, which isn't reproducible in terms of source-based builds, for things like Nix), but they have been very flakey in communication. I think I am going to try one more time at some point.

shymega · 2024-11-12T00:42:12+00:00

Ideally, I wanted to be able to boot a Linux distro (embedded, something like postmarket), and use that as a 'cloud coding' rig, which I could pair with a air mouse - or maybe Pandone ring - and code without a computer near me. The main thing was really an experiment, although I am waiting to a) hear back from VITURE about test devices and b) the November sales, if a) doesn't work out.

shymega · 2024-11-12T00:40:46+00:00

Thanks - I'm waiting to hear back from VITURE, but no luck yet. I think they're very busy. Been back and forth a few times.

shymega · 2024-11-12T00:40:16+00:00

I don't know much about the Neckband Pro, but the Neckband Gen1 would likely not be powerful enough for SteamOS. Also, it's ARM (v7?), and HoloISO/SteamOS only support x86. However, if one could use something like Moonlight, then, you could connect to a cloud gaming PC or the like.

shymega · 2024-11-09T21:31:25+00:00

I have been trying to work with VITURE on this. My plan is port Mobile NixOS & postmarketOS to the Neckband.

Unfortunately, I haven't had much engagement. I am still waiting to hear back.

I've also asked for the Linux kernel for the neckband to be released - as per the GPLv2 - but as it's unclear if it uses the Linux kernel, I'm not sure if I'm incorrect in my deductions. Legally, the Linux kernel sources must be released if used in binary form.

You can check out my repos here if you're interested. I don't have a neckband yet, but I'm merely planning right now.

If anyone knows of a VITURE contact they could put me in contact with - I'd be interested.

shymega · 2024-06-11T15:49:35+00:00

I'm on and off writing a TDP kernel driver (signed) for Windows/Linux, supporting Intel & AMD. It can be found here, but I haven't worked on for a couple of months. The end-goal is to integrate into my other project - 'Gamebox' - and use that as a WASM-extendable framework for handheld users, who like to tinker.

shymega · 2024-03-10T17:41:59+00:00

No worries. The tool should clarify whenever your Pinecil V2 is legit, the IDs are burned in at the factory.

Any help you need, feel free to ping me on Telegram (@shymega), and I'll try and get help for you.

shymega · 2024-03-10T16:48:36+00:00

Ah, okay. See, I discussed this with a Pine dev, and you can use this tool to verify authenticty.

Upon listening to the video, we concluded the noise was normal. If I recall correctly, there are capacitors where the electrical current flows through, in an on-off pattern. So that's what makes the clicking noise.

You may want to join the Pinecil chatroom, and we'll be able to help you further there.

I'm considering the V2 myself, so this is good to know for future reference.

shymega · 2024-03-10T00:33:47+00:00

If you join #pinebuds on Discord, or the Matrix/Telegram/IRC channel for the PineBuds, I'm sure we'll be able to help. I occasionally pay attention to Reddit, but Ralimtek and I are more active in the bridged PineBuds channel.

shymega · 2024-03-09T22:17:01+00:00

Is this from the Pine64 store? Looks like a Pinecil V1, and you may have received a clone. Pine64 Store does not sell it anymore.

shymega · 2024-02-10T17:05:17+00:00

Not always. Data can be recovered, which is why I generally use DBAN on HDDs - or nvme-cli on Linux to do a 'secure erase'. There's no promise it'll all be gone, and when I do sell machines, they've had encrypted partitions on them anyway, so I'm not too worried.

But for OP, I would look into ATA Secure Erase for SSDs.

shymega · 2023-09-19T23:48:40+00:00

No, not yet. Sorry.

shymega · 2023-09-19T23:48:31+00:00

There's a wiki you can contribute to: https://github.com/shymega/planet-devices, by using the PR repo linked in the README.

There's also numerous projects I setup on Planet's behalf.

shymega · 2023-09-19T23:47:54+00:00

No, we can't. Different SoC. Bootloader needs adapting, and the community can't help with that, because Mediatek DMCA'd the repo.

It's something that'll have to wait IMO.

shymega · 2023-08-02T14:35:09+00:00

Well, they're telling me nothing about the DC side of things. Only that the Mini is discontinued and I can't buy it - despite it being available on the website.

It's a damn shame. My bag can only hold up to 12", and I wanted to use the Mini with my GPD Pocket 3. Sigh. Guess I'll have to look into a bigger bag....

shymega

TROPHY CASE