Razer Synapse Not Showing Onboard Memory Option for DeathAdder V2 X Hyperspeed | Razer Insider
Skip to main content
Solved

Razer Synapse Not Showing Onboard Memory Option for DeathAdder V2 X Hyperspeed



I recently bought the Razer DeathAdder V2 X Hyperspeed, and according to the official product description, it supports onboard memory for saving custom profiles. However, in Razer Synapse, I’m not seeing any option related to onboard memory or profile storage.

Because of this, I’m unable to save custom profiles directly to the mouse for use on other systems, which is a key feature I was expecting. I haven’t updated the mouse firmware yet—could that be the reason? Or is there something else I need to do to access onboard memory for this specific model?

Any help or suggestions would be appreciated!

Best answer by FiszPL

sharpSteelTealsystem367 wrote:
FiszPL wrote:

It has only 1 onboard profile memory so it’ll be not directly visible in Synapse.

It’ll just always use your latest profile and save settings on the mouse like DPI / Hz and simple keybinds. Be aware, that macros for eg. will not be stored, and it’s still required to have Synapse running in background.

 

Okay, so as I understand it — the mouse has only one onboard profile, and it saves the latest settings like DPI, polling rate, and simple keybindings.

Now, here's my situation:
I have two systems — one running Windows and the other Linux.

On Windows, I set up my default profile in Synapse with custom button bindings and DPI settings. Since the mouse is supposed to save those settings onboard, I expected it to carry over when I switch to my Linux system.

But that's not happening — when I use the mouse on Linux, it behaves like a fresh device. The custom key bindings are lost, and it goes back to default behavior.

So my question is:
If there's truly one onboard memory profile, why aren’t the saved changes (like button remapping and DPI) being applied when I switch to another OS like Linux?

May be a bug in Synapse then. Which version you’re using? If 3 go with 4, if 4, try 3 again.

View original
Did this topic help you find an answer to your question?

6 Replies

FiszPL
Vanguard
Forum|alt.badge.img+1
  • VANGUARD
  • 7218 replies
  • April 11, 2025

It has only 1 onboard profile memory so it’ll be not directly visible in Synapse.

It’ll just always use your latest profile and save settings on the mouse like DPI / Hz and simple keybinds. Be aware, that macros for eg. will not be stored, and it’s still required to have Synapse running in background.


FiszPL wrote:

It has only 1 onboard profile memory so it’ll be not directly visible in Synapse.

It’ll just always use your latest profile and save settings on the mouse like DPI / Hz and simple keybinds. Be aware, that macros for eg. will not be stored, and it’s still required to have Synapse running in background.

 

Okay, so as I understand it — the mouse has only one onboard profile, and it saves the latest settings like DPI, polling rate, and simple keybindings.

Now, here's my situation:
I have two systems — one running Windows and the other Linux.

On Windows, I set up my default profile in Synapse with custom button bindings and DPI settings. Since the mouse is supposed to save those settings onboard, I expected it to carry over when I switch to my Linux system.

But that's not happening — when I use the mouse on Linux, it behaves like a fresh device. The custom key bindings are lost, and it goes back to default behavior.

So my question is:
If there's truly one onboard memory profile, why aren’t the saved changes (like button remapping and DPI) being applied when I switch to another OS like Linux?


FiszPL
Vanguard
Forum|alt.badge.img+1
  • VANGUARD
  • 7218 replies
  • Answer
  • April 11, 2025
sharpSteelTealsystem367 wrote:
FiszPL wrote:

It has only 1 onboard profile memory so it’ll be not directly visible in Synapse.

It’ll just always use your latest profile and save settings on the mouse like DPI / Hz and simple keybinds. Be aware, that macros for eg. will not be stored, and it’s still required to have Synapse running in background.

 

Okay, so as I understand it — the mouse has only one onboard profile, and it saves the latest settings like DPI, polling rate, and simple keybindings.

Now, here's my situation:
I have two systems — one running Windows and the other Linux.

On Windows, I set up my default profile in Synapse with custom button bindings and DPI settings. Since the mouse is supposed to save those settings onboard, I expected it to carry over when I switch to my Linux system.

But that's not happening — when I use the mouse on Linux, it behaves like a fresh device. The custom key bindings are lost, and it goes back to default behavior.

So my question is:
If there's truly one onboard memory profile, why aren’t the saved changes (like button remapping and DPI) being applied when I switch to another OS like Linux?

May be a bug in Synapse then. Which version you’re using? If 3 go with 4, if 4, try 3 again.


Yes, it worked! The issue was that I was using Razer Synapse 4. To save onboard memory, I needed to use Razer Synapse 3 instead. Thanks a lot for your help! FiszP

 


FiszPL
Vanguard
Forum|alt.badge.img+1
  • VANGUARD
  • 7218 replies
  • April 14, 2025

@Razer.Ten ​@Razer.Speedcr0ss ​@Razer.Aero - could you pass this issue to the software team Synapse 4 (beta aka. stable)?


Hi! I came across this post and felt I had to respond. I’m having the exact same issue with the same mouse model. The problem is that switching from Synapse 3 to 4 or from 4 back to 3 doesn’t change anything. I understand that this model only has one onboard memory profile, so in order to use things like macros (or anything that is stocked in on board memory), Synapse has to be running in the background.

The issue is, the software keeps telling me that Synapse is not running in the background… even though everything is properly installed and there’s no reason for Synapse not to be running. With Synapse 4, the problem is even worse: Razer Synapse doesn’t start under services.smc. The supposed path to the Synapse .exe leads nowhere.

On the other hand, with Synapse 3, there’s no issue in that regard: the path correctly leads to the Synapse .exe, and the service is clearly running : it can be stopped, suspended, and restarted without issue (which is not possible with Synapse 4 for the reason mentioned above).

So why am I still having the same issue with Synapse 3?

I made a long post on Reddit because I couldn’t find ANY solution (even with ChatGPT). Everything is described here: https://www.reddit.com/r/razer/comments/1jsgty9/problem_with_synapse_and_macros/

No one has replied to the post, however, I was contacted via PM (on Reddit) by Razer’s support team. That led to nearly two weeks of daily exchanges with different Razer professionals. Despite countless messages and troubleshooting steps, no solution was ever found, and Razer eventually stopped helping politely, but still.

What’s interesting is that I have two PCs, and I experience the same problem on both. I don’t understand what is going on, everything had been working fine for over a year, and then out of nowhere, my macros just stopped working


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings