Talk:Razer - Revision history

140.228.204.156: Deleted as not substantial

2026-05-23T08:39:29Z

Deleted as not substantial

← Older revision		Revision as of 08:39, 23 May 2026
Line 10:		Line 10:

	Source: https://www.youtube.com/watch?v=fimfEhL-WRo timestamps of interest from the video: 1:33 and 22:18 [[User:SharpNikel\|SharpNikel]] ([[User talk:SharpNikel\|talk]]) 22:36, 3 January 2026 (UTC)		Source: https://www.youtube.com/watch?v=fimfEhL-WRo timestamps of interest from the video: 1:33 and 22:18 [[User:SharpNikel\|SharpNikel]] ([[User talk:SharpNikel\|talk]]) 22:36, 3 January 2026 (UTC)

	~~== Freyja haptics ==~~

	Haptics from this company have been a disaster with the majority of time under ownership the device has not responded correctly to inputs. Multiple tickets have been raised regarding this issue. As of recently this device has also been impacted by adjusting audio for individual apps from Windows volume mixer. It was I could adjust any app to desired listening levels and haptics would receive a pre-set level of audio from all apps and could be adjusted in the software. Instead of finding a solution to make this work as it once did I was told to have the apps as high as possible and only adjust the main volume. This would defeat the whole purpose of having a volume controller that allows my game to be at the desired listening level and adjust music/video volume as needed and keep haptics at a consistent level.


	This lack of attention to feedback/bug reports have lost me years of collecting devices from this company. I will now need to find other softwares to manage these devices. Freyja and gamer room devices do not have alternatives and will cause the loss of ability to use said products.


	~~[[Special:Contributions/140.228.204.156\|140.228.204.156]] 05:50, 14 May 2026 (UTC)~~

140.228.204.156: Deleted as not substantial enough

2026-05-23T08:38:46Z

Deleted as not substantial enough

← Older revision		Revision as of 08:38, 23 May 2026
Line 10:		Line 10:

	Source: https://www.youtube.com/watch?v=fimfEhL-WRo timestamps of interest from the video: 1:33 and 22:18 [[User:SharpNikel\|SharpNikel]] ([[User talk:SharpNikel\|talk]]) 22:36, 3 January 2026 (UTC)		Source: https://www.youtube.com/watch?v=fimfEhL-WRo timestamps of interest from the video: 1:33 and 22:18 [[User:SharpNikel\|SharpNikel]] ([[User talk:SharpNikel\|talk]]) 22:36, 3 January 2026 (UTC)

	~~== Update breaks ability to use Chroma light strip set aka Chroma wireless ARGB controller with Razer Aether strips or Razer Chroma Addressable RGB controller. ==~~

	Unable to switch lighting profiles within Razer's own software without devices moving from saved position. I have this set of RGB devices on the first Custom PC I built. It runs on Synapse 3 with minimal error. I participated in 2024 Synapse 4 beta with these devices. I also knew it was finally time to upgrade my 1080ti and a new build was in order so I started collecting the same devices mid 2024 to use on the new Synapse and whatever new PC tech came out after. Around CES 2025 I noticed I could no longer change lighting profiles without devices moving in Chroma studio. So I contacted support. I found their speakers Nommo v2 to not stay in saved position along with the issues described above. The speaker issue was resolved and I reported back that devices still move in their software. at this time I did not know the details on this error and reached out to support asking for help. I was asked if the issue could be resolved by using the refresh button. I responded back that refreshing the page would temporarily fix the issue however at the time of reporting that issue the software was very slow and could unresponsive and it could take up to two minutes for a process the old software could accomplish in twenty seconds. At this time I reported back this was not a proper solution please advise. No response. I then spent a lot of my free time trying diagnose this issue. I finally found that this only happens when Chroma light strip set is connected to either PCs I have and only happens when this device is connected with Razer Aether light strip or Chroma Addressable RGB controller and used with Synapse 4. I have since reported the exact issue several months ago. I have asked Razer for a working solution in their software or a refund. I have not got a solution for either. [[User:Dc1155\|Dc1155]] ([[User talk:Dc1155\|talk]]) 09:16, 12 February 2026 (UTC)

	== Freyja haptics ==		== Freyja haptics ==

140.228.204.156: /* Freyja haptics */Fixed grammer

2026-05-23T03:40:55Z

Freyja haptics: Fixed grammer

← Older revision		Revision as of 03:40, 23 May 2026
Line 20:		Line 20:


	This lack of attention to feedback/bug reports have lost me years of collecting devices from this company. I will now need to find other softwares to manage these devices ~~freyja~~ and gamer room devices do not have alternatives and will cause the loss of ability to use ~~other~~ products ~~within the Razer ecosystem~~.		This lack of attention to feedback/bug reports have lost me years of collecting devices from this company. I will now need to find other softwares to manage these devices. Freyja and gamer room devices do not have alternatives and will cause the loss of ability to use said products.


	[[Special:Contributions/140.228.204.156\|140.228.204.156]] 05:50, 14 May 2026 (UTC)		[[Special:Contributions/140.228.204.156\|140.228.204.156]] 05:50, 14 May 2026 (UTC)

140.228.204.156: /* Freyja haptics */Further explanation

2026-05-23T03:38:29Z

Freyja haptics: Further explanation

← Older revision		Revision as of 03:38, 23 May 2026
Line 20:		Line 20:


	This lack of attention to feedback/bug reports have lost me years of collecting devices from this company. I will now need to find other softwares to manage these devices ~~even though I was involved in every beta~~ to ~~further~~ the ~~experience~~.		This lack of attention to feedback/bug reports have lost me years of collecting devices from this company. I will now need to find other softwares to manage these devices freyja and gamer room devices do not have alternatives and will cause the loss of ability to use other products within the Razer ecosystem.


	[[Special:Contributions/140.228.204.156\|140.228.204.156]] 05:50, 14 May 2026 (UTC)		[[Special:Contributions/140.228.204.156\|140.228.204.156]] 05:50, 14 May 2026 (UTC)

140.228.204.156: /* Freyja haptics */Opinions removed

2026-05-23T03:31:00Z

Freyja haptics: Opinions removed

← Older revision		Revision as of 03:31, 23 May 2026
Line 17:		Line 17:
	== Freyja haptics ==		== Freyja haptics ==

	Haptics from this company have been a disaster with the majority of time under ownership the device has not responded correctly to inputs. Multiple tickets have been raised regarding this issue. ~~Currently does not work properly again. Will it enable haptics on boot? Will it continue to work while in use after turning off audio to haptics and turning back on?~~ As of recently this device has also been impacted by adjusting audio for individual apps from Windows volume mixer. It was I could adjust any app to desired listening levels and haptics would receive a ~~preset~~ level of audio from all apps and could be adjusted in the software. Instead of finding a solution to make this work as it once did I was told to have the apps as high as possible and only adjust the main volume. This would defeat the whole purpose of having a volume controller that allows my game to be at the desired listening level and adjust music/video volume as needed and keep haptics at a consistent level.		Haptics from this company have been a disaster with the majority of time under ownership the device has not responded correctly to inputs. Multiple tickets have been raised regarding this issue. As of recently this device has also been impacted by adjusting audio for individual apps from Windows volume mixer. It was I could adjust any app to desired listening levels and haptics would receive a pre-set level of audio from all apps and could be adjusted in the software. Instead of finding a solution to make this work as it once did I was told to have the apps as high as possible and only adjust the main volume. This would defeat the whole purpose of having a volume controller that allows my game to be at the desired listening level and adjust music/video volume as needed and keep haptics at a consistent level.

140.228.204.156: /* Freyja haptics */

2026-05-23T03:28:57Z

Freyja haptics

← Older revision		Revision as of 03:28, 23 May 2026
Line 20:		Line 20:


	This lack of attention to feedback/bug reports have lost me years of collecting devices from a company ~~I once thought had it all~~. I will now need to find other softwares to manage these devices even though I was involved in every beta to further the experience.		This lack of attention to feedback/bug reports have lost me years of collecting devices from this company. I will now need to find other softwares to manage these devices even though I was involved in every beta to further the experience.


	~~Anti consumer rights at it's finest.~~ [[Special:Contributions/140.228.204.156\|140.228.204.156]] 05:50, 14 May 2026 (UTC)		[[Special:Contributions/140.228.204.156\|140.228.204.156]] 05:50, 14 May 2026 (UTC)

140.228.204.156: /* Freyja haptics */ new section

2026-05-14T05:50:56Z

Freyja haptics: new section

← Older revision		Revision as of 05:50, 14 May 2026
Line 14:		Line 14:

	Unable to switch lighting profiles within Razer's own software without devices moving from saved position. I have this set of RGB devices on the first Custom PC I built. It runs on Synapse 3 with minimal error. I participated in 2024 Synapse 4 beta with these devices. I also knew it was finally time to upgrade my 1080ti and a new build was in order so I started collecting the same devices mid 2024 to use on the new Synapse and whatever new PC tech came out after. Around CES 2025 I noticed I could no longer change lighting profiles without devices moving in Chroma studio. So I contacted support. I found their speakers Nommo v2 to not stay in saved position along with the issues described above. The speaker issue was resolved and I reported back that devices still move in their software. at this time I did not know the details on this error and reached out to support asking for help. I was asked if the issue could be resolved by using the refresh button. I responded back that refreshing the page would temporarily fix the issue however at the time of reporting that issue the software was very slow and could unresponsive and it could take up to two minutes for a process the old software could accomplish in twenty seconds. At this time I reported back this was not a proper solution please advise. No response. I then spent a lot of my free time trying diagnose this issue. I finally found that this only happens when Chroma light strip set is connected to either PCs I have and only happens when this device is connected with Razer Aether light strip or Chroma Addressable RGB controller and used with Synapse 4. I have since reported the exact issue several months ago. I have asked Razer for a working solution in their software or a refund. I have not got a solution for either. [[User:Dc1155\|Dc1155]] ([[User talk:Dc1155\|talk]]) 09:16, 12 February 2026 (UTC)		Unable to switch lighting profiles within Razer's own software without devices moving from saved position. I have this set of RGB devices on the first Custom PC I built. It runs on Synapse 3 with minimal error. I participated in 2024 Synapse 4 beta with these devices. I also knew it was finally time to upgrade my 1080ti and a new build was in order so I started collecting the same devices mid 2024 to use on the new Synapse and whatever new PC tech came out after. Around CES 2025 I noticed I could no longer change lighting profiles without devices moving in Chroma studio. So I contacted support. I found their speakers Nommo v2 to not stay in saved position along with the issues described above. The speaker issue was resolved and I reported back that devices still move in their software. at this time I did not know the details on this error and reached out to support asking for help. I was asked if the issue could be resolved by using the refresh button. I responded back that refreshing the page would temporarily fix the issue however at the time of reporting that issue the software was very slow and could unresponsive and it could take up to two minutes for a process the old software could accomplish in twenty seconds. At this time I reported back this was not a proper solution please advise. No response. I then spent a lot of my free time trying diagnose this issue. I finally found that this only happens when Chroma light strip set is connected to either PCs I have and only happens when this device is connected with Razer Aether light strip or Chroma Addressable RGB controller and used with Synapse 4. I have since reported the exact issue several months ago. I have asked Razer for a working solution in their software or a refund. I have not got a solution for either. [[User:Dc1155\|Dc1155]] ([[User talk:Dc1155\|talk]]) 09:16, 12 February 2026 (UTC)

			== Freyja haptics ==

			Haptics from this company have been a disaster with the majority of time under ownership the device has not responded correctly to inputs. Multiple tickets have been raised regarding this issue. Currently does not work properly again. Will it enable haptics on boot? Will it continue to work while in use after turning off audio to haptics and turning back on? As of recently this device has also been impacted by adjusting audio for individual apps from Windows volume mixer. It was I could adjust any app to desired listening levels and haptics would receive a preset level of audio from all apps and could be adjusted in the software. Instead of finding a solution to make this work as it once did I was told to have the apps as high as possible and only adjust the main volume. This would defeat the whole purpose of having a volume controller that allows my game to be at the desired listening level and adjust music/video volume as needed and keep haptics at a consistent level.


			This lack of attention to feedback/bug reports have lost me years of collecting devices from a company I once thought had it all. I will now need to find other softwares to manage these devices even though I was involved in every beta to further the experience.


			Anti consumer rights at it's finest. [[Special:Contributions/140.228.204.156\|140.228.204.156]] 05:50, 14 May 2026 (UTC)

AnotherConsumerRightsPerson: reverting edits per mod noticeboard

2026-02-28T17:07:30Z

reverting edits per mod noticeboard

← Older revision		Revision as of 17:07, 28 February 2026
Line 11:		Line 11:
	Source: https://www.youtube.com/watch?v=fimfEhL-WRo timestamps of interest from the video: 1:33 and 22:18 [[User:SharpNikel\|SharpNikel]] ([[User talk:SharpNikel\|talk]]) 22:36, 3 January 2026 (UTC)		Source: https://www.youtube.com/watch?v=fimfEhL-WRo timestamps of interest from the video: 1:33 and 22:18 [[User:SharpNikel\|SharpNikel]] ([[User talk:SharpNikel\|talk]]) 22:36, 3 January 2026 (UTC)

	Razer ~~supprt leaves consumer~~ without the ~~abilty~~ to use Razer ~~products~~ in ~~new Razer~~ software for ~~over a year~~.		== Update breaks ability to use Chroma light strip set aka Chroma wireless ARGB controller with Razer Aether strips or Razer Chroma Addressable RGB controller. ==

			Unable to switch lighting profiles within Razer's own software without devices moving from saved position. I have this set of RGB devices on the first Custom PC I built. It runs on Synapse 3 with minimal error. I participated in 2024 Synapse 4 beta with these devices. I also knew it was finally time to upgrade my 1080ti and a new build was in order so I started collecting the same devices mid 2024 to use on the new Synapse and whatever new PC tech came out after. Around CES 2025 I noticed I could no longer change lighting profiles without devices moving in Chroma studio. So I contacted support. I found their speakers Nommo v2 to not stay in saved position along with the issues described above. The speaker issue was resolved and I reported back that devices still move in their software. at this time I did not know the details on this error and reached out to support asking for help. I was asked if the issue could be resolved by using the refresh button. I responded back that refreshing the page would temporarily fix the issue however at the time of reporting that issue the software was very slow and could unresponsive and it could take up to two minutes for a process the old software could accomplish in twenty seconds. At this time I reported back this was not a proper solution please advise. No response. I then spent a lot of my free time trying diagnose this issue. I finally found that this only happens when Chroma light strip set is connected to either PCs I have and only happens when this device is connected with Razer Aether light strip or Chroma Addressable RGB controller and used with Synapse 4. I have since reported the exact issue several months ago. I have asked Razer for a working solution in their software or a refund. I have not got a solution for either. [[User:Dc1155\|Dc1155]] ([[User talk:Dc1155\|talk]]) 09:16, 12 February 2026 (UTC)

140.228.204.156: /* Update breaks ability to use Chroma light strip set aka Chroma wireless ARGB controller with Razer Aether strips or Razer Chroma Addressable RGB controller. */

2026-02-28T04:45:06Z

Update breaks ability to use Chroma light strip set aka Chroma wireless ARGB controller with Razer Aether strips or Razer Chroma Addressable RGB controller.

← Older revision		Revision as of 04:45, 28 February 2026
Line 11:		Line 11:
	Source: https://www.youtube.com/watch?v=fimfEhL-WRo timestamps of interest from the video: 1:33 and 22:18 [[User:SharpNikel\|SharpNikel]] ([[User talk:SharpNikel\|talk]]) 22:36, 3 January 2026 (UTC)		Source: https://www.youtube.com/watch?v=fimfEhL-WRo timestamps of interest from the video: 1:33 and 22:18 [[User:SharpNikel\|SharpNikel]] ([[User talk:SharpNikel\|talk]]) 22:36, 3 January 2026 (UTC)

	~~== Update breaks ability~~ to use ~~Chroma light strip set aka Chroma wireless ARGB controller with~~ Razer ~~Aether strips or~~ Razer ~~Chroma Addressable RGB controller~~. ==		Razer supprt leaves consumer without the abilty to use Razer products in new Razer software for over a year.

140.228.204.156 at 04:43, 28 February 2026

2026-02-28T04:43:42Z

← Older revision		Revision as of 04:43, 28 February 2026
Line 12:		Line 12:

	== Update breaks ability to use Chroma light strip set aka Chroma wireless ARGB controller with Razer Aether strips or Razer Chroma Addressable RGB controller. ==		== Update breaks ability to use Chroma light strip set aka Chroma wireless ARGB controller with Razer Aether strips or Razer Chroma Addressable RGB controller. ==

	Unable to switch lighting profiles within Razer's own software without devices moving from saved position. I have this set of RGB devices on the first Custom PC I built. It runs on Synapse 3 with minimal error. I participated in 2024 Synapse 4 beta with these devices. I also knew it was finally time to upgrade my 1080ti and a new build was in order so I started collecting the same devices mid 2024 to use on the new Synapse and whatever new PC tech came out after. Around CES 2025 I noticed I could no longer change lighting profiles without devices moving in Chroma studio. So I contacted support. I found their speakers Nommo v2 to not stay in saved position along with the issues described above. The speaker issue was resolved and I reported back that devices still move in their software. at this time I did not know the details on this error and reached out to support asking for help. I was asked if the issue could be resolved by using the refresh button. I responded back that refreshing the page would temporarily fix the issue however at the time of reporting that issue the software was very slow and could unresponsive and it could take up to two minutes for a process the old software could accomplish in twenty seconds. At this time I reported back this was not a proper solution please advise. No response. I then spent a lot of my free time trying diagnose this issue. I finally found that this only happens when Chroma light strip set is connected to either PCs I have and only happens when this device is connected with Razer Aether light strip or Chroma Addressable RGB controller and used with Synapse 4. I have since reported the exact issue several months ago. I have asked Razer for a working solution in their software or a refund. I have not got a solution for either. [[User:Dc1155\|Dc1155]] ([[User talk:Dc1155\|talk]]) 09:16, 12 February 2026 (UTC)