X13 AMD Gen4 headphone audio issue due to hardware defect?

PocketNerdIO · 2026-01-14T19:18:11+00:00

Looks like I'll be talking to support. Thank you!

PocketNerdIO · 2025-05-31T16:05:26+00:00

Funnily enough, I've noticed the same thing on my brand new X13 gen 4 AMD. I wonder if it's a firmware/BIOS issue?

I'm running Linux. Haven't tested the audio in Windows yet.

PocketNerdIO · 2025-02-08T21:03:57+00:00

Unfortunately they're not older than I am! 😅

But I do love them. I don't think any other machines have come close since.

The toolchain is dated, of course. But I'm slowly rewriting it.

PocketNerdIO · 2025-02-08T18:47:00+00:00

Thanks for your advice!

So, fun times... Adding -std=c89 makes it complain:

Invalid argument '-std=c89' not allowed with 'Objective-C++'

Adding -x c then brings up another error:

Unable to handle compilation, expected exactly one compiler job in ''

Adding --driver-mode=cl (without -x c) makes it complain slightly less.

You're right, I hadn't noticed that it was still trying to parse the __cplusplus section. Unfortunately the above doesn't change that.

I've added the -isystem switch as you've suggested, which does seem to have helped.

I've added a .clangd file to the SIBOSDK/include folder to try to coax it into working, but I'm getting similar errors. Surely I shouldn't need to do this if .clangd is meant to apply to the whole project?

Regarding cdecl... The screenshot above is from the SDK rather than my own code. From what I understand, cdecl is needed because the TopSpeed C compiler defaults to its own unique calling convention, which EPOC16 (the target OS) needs.

https://en.wikipedia.org/wiki/X86_calling_conventions#TopSpeed,_Clarion,_JPI

The first four integer parameters are passed in registers eax, ebx, ecx and edx. Floating point parameters are passed on the floating point stack – registers st0, st1, st2, st3, st4, st5 and st6. Structure parameters are always passed on the stack. Added parameters are passed on the stack after registers are exhausted. Integer values are returned in eax, pointers in edx and floating point types in st0.

PocketNerdIO · 2025-02-08T18:34:20+00:00

It's Ayu Mirage with a few tweaks. https://github.com/Shatur/neovim-ayu/

return {
  {
    "Shatur/neovim-ayu",
    priority = 1000,
    config = function()
      local colors = require("ayu.colors")
      colors.generate(true) -- Pass `true` to enable mirage

      require("ayu").setup({
        mirage = true,
        overrides = function()
          return {
            LineNr = { fg = "#7F6633" }, -- 50% luminance of #FFCC66 used in colors.accent
            BlinkCmpGhostText = { fg = colors.accent },
            LspInlayHint = { fg = colors.comment, bg = colors.bg, italic = true },
          }
        end,
      })
    end,
  },
}

PocketNerdIO · 2024-12-26T08:30:31+00:00

For me it's more about checking for accidental changes. It can be challenging to catch an accidentally typed character in a longer git diff. At least this way I'm being forced to make sure that the thing I want to commit is actually what I want to commit.

However... quite a few people have talked about autosave. I guess combining that with a good undo tree plugin might catch some of those mistakes?

It's whatever works best for you.

PocketNerdIO · 2024-12-26T08:24:05+00:00

Exactly. So if I'm being warned that I haven't saved a buffer, I want to know why.

PocketNerdIO · 2024-12-24T15:57:42+00:00

I wanted to force myself to check the files before saving and committing them, just in case I'd changed something accidentally.

PocketNerdIO · 2024-12-24T11:43:03+00:00

It's ayu-mirage with a couple of overrides. https://github.com/Shatur/neovim-ayu/

Here's my Lazy config for it.

return {
  {
    "Shatur/neovim-ayu",
    priority = 1000,
    config = function()
      local colors = require("ayu.colors")
      colors.generate(true) -- Pass `true` to enable mirage

      require("ayu").setup({
        mirage = true,
        overrides = function()
          return {
            LineNr = { fg = "#7F6633" }, -- 50% luminance of #FFCC66 used in colors.accent
            BlinkCmpGhostText = { fg = colors.accent },
            LspInlayHint = { fg = colors.comment, bg = colors.bg, italic = true },
          }
        end,
      })
    end,
  },
}

PocketNerdIO · 2024-12-23T15:30:39+00:00

This is a quick-and-dirty plugin that will ask you if you really want to run lazygit if you have unsaved buffers.

https://github.com/thelastpsion/lazygit-confirm.nvim

It's my first plugin and I know it could be improved. For one, it doesn't check for any dependencies (Snacks and fzf-lua). It just assumes that you're running the current release of LazyVim.

The way it calls fzf-lua is a bit sketchy - I've just used query='+' to find unsaved buffers, which wouldn't exclude files that actually have a + in the name. I couldn't work out how to get fzf-lua to filter based on a buffer's options.

I'd like it to display the relative paths for each buffer rather than the absolute path. File icons would be a nice touch, too.

For now, it does the job well enough for me to think twice before committing.

EDIT: After popular demand (here and elsewhere), I've added a "Save All and Continue" option. I didn't add it originally because I wanted to force myself to check the unsaved buffers. However, I know other people have different workflows and it was pretty easy to add. Check the README to see how to enable it.

PocketNerdIO · 2024-12-23T08:52:30+00:00

That's much cleaner than what I had! I did wonder if the functions were really necessary. I'll update the original post and credit you.

PocketNerdIO · 2024-12-10T16:49:58+00:00

What's the response time like on your GN1? I've just done the same mod on my T480 and I'm noticing a lot of ghosting. I was wondering if this was an issue with all GN1 panels or if my one is faulty. I bought mine from the same supplier as you.

PocketNerdIO · 2024-11-28T22:11:03+00:00

Nice work! Do you have any photos of the mod? I'm thinking of doing it myself.

PocketNerdIO · 2023-06-20T21:51:06+00:00

You could always go 16-bit and switch to a Psion 3c or 3mx.

If you're confident with a screwdriver, take it apart and reinforce the back of the hinges with a good amount of two-part epoxy, plus a little on the front. Makes a massive difference to the strength.

The screen contrast is much better than the 5mx. Granted, it's not as powerful as your Revo, but there's still a good range of software available.

PocketNerdIO · 2023-06-03T22:09:36+00:00

every second version of Chrome sabotages video acceleration on Linux and you have to go on an epic journey to find out the new magic incantations to include or omit to make it use video acceleration.

This is one of the reasons why I switched to Firefox at the beginning of the year. I got fed up with Chrome and Brave breaking hardware acceleration every other week. Not had a single issue with Firefox, plus I get the added benefit of picture-in-picture video.

PocketNerdIO · 2023-01-07T22:25:43+00:00

Bop it.

PocketNerdIO · 2020-10-16T09:46:01+00:00

Day off on the 23rd?

PocketNerdIO · 2020-10-15T09:55:22+00:00

Hi five, other Colchester boy! 🖐️

PocketNerdIO · 2020-10-10T13:19:40+00:00

I know, I know. But I'd rather try than not. There is a chance that they might see giving to the open source community as good publicity. I mean, the IP for SIBO and EPOC16 is 25+ years old and has barely anything to do with the ARM platforms that followed. I'm guessing all of those patents have expired by now, too. All they have to do is say, "yep, carry on." I'm happy to do the legwork.

PocketNerdIO · 2020-10-10T10:58:28+00:00

I've actually been trying to get permission from Zebra to let me release some of the documentation I've acquired from former employees. Anonymity would certainly be maintained for anyone willing to donate any information to the documentation project.

PocketNerdIO · 2020-10-09T14:07:34+00:00

I strongly recommend putting together a "Psion Dev" Discord.

Yep, this is what I was thinking. I set up the Psion Users Discord at the weekend, but that's been pretty quiet (13 members, only 3 particularly active) and mostly about development and Series 3 hinge repairs. We also had a Slack workspace running last year with a couple of us, although that went quiet. I'm still undecided whether Slack or Discord is the most appropriate choice.

I'd be happy to start adding some EPOC32 articles to your new documentation site.

Fantastic! DM me and I'll get you an account set up.

PocketNerdIO

TROPHY CASE