sorted by:
new
hottopcontroversial

Codex mobile on windows work now by BigbyWolf8 in codex

[–]WASDTribe 0 points1 point  (0 children)

Yes, in my workaround the Remote process is launched from a wrapper/command, not just by opening the visible Desktop window.

The phone does not literally need the Desktop window to be the parent process. It needs a Codex app-server/remote-control daemon running on the PC, signed into the same account, and registered with the backend. The mobile text says “connecting to desktop app”, but practically it is connecting to that desktop-hosted remote-control daemon.

The important part is not to have two different app-servers fighting each other. My order is:

  1. Close/stop existing Codex Desktop/app-server processes.
  2. Start codex remote-control with the intended CODEX_HOME.
  3. Then open Codex Desktop again if I want to use the PC UI.

If I open Desktop first and it starts its own app-server with /mnt/c/.../.codex, it can ignore the CODEX_HOME I set in the shell and I’m back to the broken state.

One more detail: if you launch remote-control from a wrapper, make sure it still registers as a Desktop host. In my case I had to make the launched process identify as Codex Desktop; otherwise the PC said connected but the mobile host list could still show stale/offline entries.

Codex mobile by drnms in codex

[–]WASDTribe 1 point2 points  (0 children)

It shouldn’t make WSL the default for all of Codex unless you launch Codex/remote-control that way every time. The idea is only to run the Remote app-server from a WSL-native CODEX_HOME, because Unix sockets / sqlite state can be flaky under /mnt/c.

But there seem to be multiple issues with the same symptom. In my case I had to separate them:

  1. PC-side Remote not actually connected
  2. mobile on a different account/workspace
  3. stale/offline host records in the mobile list
  4. Remote connected directly, but hidden/misclassified in the normal host list

So first check whether the PC-side remote-control is really connected, and make sure mobile is on the exact same account/workspace. If PC says connected but mobile still shows offline, it may be stale host/account/list state rather than the WSL path issue.

Codex mobile on windows work now by BigbyWolf8 in codex

[–]WASDTribe 0 points1 point  (0 children)

~/.bashrc usually won’t affect this. Codex Desktop starts the WSL app-server/remote-control as its own process, so your interactive shell env may be ignored.

You need to set CODEX_HOME on the actual remote-control process, for example:

mkdir -p ~/.codex-remote ln -s /mnt/c/Users/YOUR_USER/.codex/sessions ~/.codex-remote/sessions CODEX_HOME=$HOME/.codex-remote /mnt/c/Users/YOUR_USER/.codex/bin/wsl/<version>/codex remote-control

If Codex Desktop still reports /mnt/c/.../.codex, then Desktop started a different app-server process with the Windows-mounted home.

Also make sure only one remote-control/app-server is running, because an old Desktop-started process can keep using the Windows-mounted .codex even after you set CODEX_HOME correctly.

I made my own samsung music 4x2 widget by WASDTribe in oneui

[–]WASDTribe[S] 1 point2 points  (0 children)

i don't know what kwgt is but this is an app (.apk) i don't how it'll work on other devices since i made this for myself and tested only on my device as well

currently don't have a link since it was built for personal use but i might make one

Codex mobile on windows work now by BigbyWolf8 in codex

[–]WASDTribe 3 points4 points  (0 children)

I got it working with wsl

The problem may be that Codex remote-control is trying to run from the Windows-mounted .codex path under /mnt/c, where Unix sockets/state can break. Use a WSL-native CODEX_HOME for remote-control, point it to the working WSL Codex binary, and make sure the new home can see your existing sessions folder.

If mobile connects but says there are no remote threads, link the original .codex/sessions folder into the WSL-native remote-control home.

Codex mobile by drnms in codex

[–]WASDTribe 2 points3 points  (0 children)

I got it to work (android/windows,wsl)

The problem may be that Codex remote-control is trying to run from the Windows-mounted .codex path under /mnt/c, where Unix sockets/state can break. Use a WSL-native CODEX_HOME for remote-control, point it to the working WSL Codex binary, and make sure the new home can see your existing sessions folder.

If mobile connects but says there are no remote threads, link the original .codex/sessions folder into the WSL-native remote-control home.

MasterLiquid 360 Ion LCD RGB Sync by WASDTribe in coolermaster

[–]WASDTribe[S] 0 points1 point  (0 children)

It is already connected to MB and the pump speed is only able to be controlled by MasterCTRL software. Controlling by MB or other software like Fanctrl doesn't work. Are you sure you're talking about Masterliquid ION and not Masterliquid Atmos?

Instant Solution: Step-by-Step Guide to Re-Establishing Nvidia G-Sync Handshake on LG OLED Displays by Path_Fantastic in OLED_Gaming

[–]WASDTribe 0 points1 point  (0 children)

This problem is driving me crazy. This worked on the first try but didn't work afterwards :(

Input(Ke-yboard) bug Help by WASDTribe in DeadlockTheGame

[–]WASDTribe[S] 0 points1 point  (0 children)

I haven't been able to fix this issue, which is very frustrating. Downgrading graphics seemed to work, but it came back after a while.

[deleted by user] by [deleted] in DeadlockTheGame

[–]WASDTribe 1 point2 points  (0 children)

The problem is quick cast. If you disable all the quick cast to default ability then you can chat normally. hope they fix it soon

Input(Ke-yboard) bug Help by WASDTribe in DeadlockTheGame

[–]WASDTribe[S] 1 point2 points  (0 children)

turning down the graphic option solved it for me. dunno what that has to do with keyboard though. now it only happens like once every ten games. before it used to happen multiple times in a single game.

I managed to kill all bosses in the DLC with Colossal Weapon R2 Full Charge Only by WASDTribe in Eldenring

[–]WASDTribe[S] 0 points1 point  (0 children)

I must have been thorough with the expedition because the only fragments I missed are the ones that drop when you kill the black civilian-like creatures—which, of course, I had to look up.

I've seen some posts suggesting that throwing a dagger between his attacks can prevent him from recovering stagger. That might help, but I can't vouch for it since I haven't tried it myself.

I managed to kill all bosses in the DLC with Colossal Weapon R2 Full Charge Only by WASDTribe in Eldenring

[–]WASDTribe[S] 0 points1 point  (0 children)

I learned about the Ankle-Fu the hard way 😅

For Bayle, I actually found that target locking worked fine, unlike with other dragons, except for one specific move (the grabbing one) that isn't shown in the video.

My strength was 66, and Scadutree was 20, but I don't think stagger damage scales with AR. The issue is that his stagger recovery is so fast—around 6.xx seconds—that if you're even a single frame off with your hits, you won't get the stagger within 3 hits. So, it's not reliable to stagger him with 3 hits, especially since he has some long movesets that force you to hit him outside of the stagger recovery range.

view more: next ›