<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://consumerrights.wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Dc1155</id>
	<title>Consumer Rights Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://consumerrights.wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Dc1155"/>
	<link rel="alternate" type="text/html" href="https://consumerrights.wiki/w/Special:Contributions/Dc1155"/>
	<updated>2026-04-29T05:25:14Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.44.0</generator>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Talk:Google_Nest_Protect_forced_to_use_Google_app&amp;diff=36995</id>
		<title>Talk:Google Nest Protect forced to use Google app</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Talk:Google_Nest_Protect_forced_to_use_Google_app&amp;diff=36995"/>
		<updated>2026-02-14T10:36:07Z</updated>

		<summary type="html">&lt;p&gt;Dc1155: /* I got into the nest secure system to get local notifications to keep track of my children. */ new section&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== I got into the nest secure system to get local notifications to keep track of my children. ==&lt;br /&gt;
&lt;br /&gt;
I have the cameras, Nest x Yale lock, and nest secure. I lost the ability to get local phone notifications about events on the nest secure system. This was able to bring up a camera and show what the event was in my case the cameras were directed at the points of entry to my house. I was able to also have the door disarm the security system when entering the premises.  [[User:Dc1155|Dc1155]] ([[User talk:Dc1155|talk]]) 10:36, 14 February 2026 (UTC)&lt;/div&gt;</summary>
		<author><name>Dc1155</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Talk:Razer&amp;diff=36825</id>
		<title>Talk:Razer</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Talk:Razer&amp;diff=36825"/>
		<updated>2026-02-12T23:40:40Z</updated>

		<summary type="html">&lt;p&gt;Dc1155: /* Update breaks ability to use Chroma light strip set aka Chroma wireless ARGB controller with Razer Aether strips or Razer Chroma Addressable RGB controller. */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Large amounts of tracking in razer software ==&lt;br /&gt;
&lt;br /&gt;
I have come across this post: &amp;lt;nowiki&amp;gt;https://www.reddit.com/r/privacy/s/lc0V0dFeaT&amp;lt;/nowiki&amp;gt; recently and is probably good to mention in this article, I want to be able to verify the information is correct, but I don&#039;t own any razer or mac software: [[User:HeadedBranch|HeadedBranch]] ([[User talk:HeadedBranch|talk]]) 14:11, 9 December 2025 (UTC)&lt;br /&gt;
&lt;br /&gt;
== Update breaks support for touchpad LCD screen ==&lt;br /&gt;
&lt;br /&gt;
The Razer Blade Pro 17&amp;quot; (2015) had an LCD screen behind the touchpad and some of the keys that allowed them to be used as programmable keys in a manner similar to a Stream deck. This was (apparently) its main feature.&lt;br /&gt;
&lt;br /&gt;
However in 2019 an update to the software &amp;quot;Razer synapse&amp;quot; broke support for this LCD screen. Apparently this software came as subscription service. &lt;br /&gt;
&lt;br /&gt;
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)&lt;br /&gt;
&lt;br /&gt;
== Update breaks ability to use Chroma light strip set aka Chroma wireless ARGB controller with Razer Aether strips or Razer Chroma Addressable RGB controller. ==&lt;br /&gt;
&lt;br /&gt;
Unable to switch lighting profiles within Razer&#039;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)&lt;/div&gt;</summary>
		<author><name>Dc1155</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Talk:Razer&amp;diff=36824</id>
		<title>Talk:Razer</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Talk:Razer&amp;diff=36824"/>
		<updated>2026-02-12T23:27:06Z</updated>

		<summary type="html">&lt;p&gt;Dc1155: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Large amounts of tracking in razer software ==&lt;br /&gt;
&lt;br /&gt;
I have come across this post: &amp;lt;nowiki&amp;gt;https://www.reddit.com/r/privacy/s/lc0V0dFeaT&amp;lt;/nowiki&amp;gt; recently and is probably good to mention in this article, I want to be able to verify the information is correct, but I don&#039;t own any razer or mac software: [[User:HeadedBranch|HeadedBranch]] ([[User talk:HeadedBranch|talk]]) 14:11, 9 December 2025 (UTC)&lt;br /&gt;
&lt;br /&gt;
== Update breaks support for touchpad LCD screen ==&lt;br /&gt;
&lt;br /&gt;
The Razer Blade Pro 17&amp;quot; (2015) had an LCD screen behind the touchpad and some of the keys that allowed them to be used as programmable keys in a manner similar to a Stream deck. This was (apparently) its main feature.&lt;br /&gt;
&lt;br /&gt;
However in 2019 an update to the software &amp;quot;Razer synapse&amp;quot; broke support for this LCD screen. Apparently this software came as subscription service. &lt;br /&gt;
&lt;br /&gt;
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)&lt;br /&gt;
&lt;br /&gt;
== Update breaks ability to use Chroma light strip set aka Chroma wireless ARGB controller with Razer Aether strips or Razer Chroma Addressable RGB controller. ==&lt;br /&gt;
&lt;br /&gt;
Unable to switch lighting profiles within Razer&#039;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.  [[User:Dc1155|Dc1155]] ([[User talk:Dc1155|talk]]) 09:16, 12 February 2026 (UTC)&lt;/div&gt;</summary>
		<author><name>Dc1155</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Talk:Razer&amp;diff=36791</id>
		<title>Talk:Razer</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Talk:Razer&amp;diff=36791"/>
		<updated>2026-02-12T10:21:18Z</updated>

		<summary type="html">&lt;p&gt;Dc1155: /* Update breaks ability to use Chroma light strip set aka Chroma wireless ARGB controller with Razer Aether strips or Razer Chroma Addressable RGB controller. */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Large amounts of tracking in razer software ==&lt;br /&gt;
&lt;br /&gt;
I have come across this post: &amp;lt;nowiki&amp;gt;https://www.reddit.com/r/privacy/s/lc0V0dFeaT&amp;lt;/nowiki&amp;gt; recently and is probably good to mention in this article, I want to be able to verify the information is correct, but I don&#039;t own any razer or mac software: [[User:HeadedBranch|HeadedBranch]] ([[User talk:HeadedBranch|talk]]) 14:11, 9 December 2025 (UTC)&lt;br /&gt;
&lt;br /&gt;
== Update breaks support for touchpad LCD screen ==&lt;br /&gt;
&lt;br /&gt;
The Razer Blade Pro 17&amp;quot; (2015) had an LCD screen behind the touchpad and some of the keys that allowed them to be used as programmable keys in a manner similar to a Stream deck. This was (apparently) its main feature.&lt;br /&gt;
&lt;br /&gt;
However in 2019 an update to the software &amp;quot;Razer synapse&amp;quot; broke support for this LCD screen. Apparently this software came as subscription service. &lt;br /&gt;
&lt;br /&gt;
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)&lt;br /&gt;
&lt;br /&gt;
== Update breaks ability to use Chroma light strip set aka Chroma wireless ARGB controller with Razer Aether strips or Razer Chroma Addressable RGB controller. ==&lt;br /&gt;
&lt;br /&gt;
Unable to switch lighting profiles within Razer&#039;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. [[User:Dc1155|Dc1155]] ([[User talk:Dc1155|talk]]) 09:16, 12 February 2026 (UTC)&lt;/div&gt;</summary>
		<author><name>Dc1155</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Talk:Razer&amp;diff=36788</id>
		<title>Talk:Razer</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Talk:Razer&amp;diff=36788"/>
		<updated>2026-02-12T09:16:14Z</updated>

		<summary type="html">&lt;p&gt;Dc1155: /* Update breaks ability to use Chroma light strip set aka Chroma wireless ARGB controller with Razer Aether strips or Razer Chroma Addressable RGB controller. */ new section&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Large amounts of tracking in razer software ==&lt;br /&gt;
&lt;br /&gt;
I have come across this post: &amp;lt;nowiki&amp;gt;https://www.reddit.com/r/privacy/s/lc0V0dFeaT&amp;lt;/nowiki&amp;gt; recently and is probably good to mention in this article, I want to be able to verify the information is correct, but I don&#039;t own any razer or mac software: [[User:HeadedBranch|HeadedBranch]] ([[User talk:HeadedBranch|talk]]) 14:11, 9 December 2025 (UTC)&lt;br /&gt;
&lt;br /&gt;
== Update breaks support for touchpad LCD screen ==&lt;br /&gt;
&lt;br /&gt;
The Razer Blade Pro 17&amp;quot; (2015) had an LCD screen behind the touchpad and some of the keys that allowed them to be used as programmable keys in a manner similar to a Stream deck. This was (apparently) its main feature.&lt;br /&gt;
&lt;br /&gt;
However in 2019 an update to the software &amp;quot;Razer synapse&amp;quot; broke support for this LCD screen. Apparently this software came as subscription service. &lt;br /&gt;
&lt;br /&gt;
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)&lt;br /&gt;
&lt;br /&gt;
== Update breaks ability to use Chroma light strip set aka Chroma wireless ARGB controller with Razer Aether strips or Razer Chroma Addressable RGB controller. ==&lt;br /&gt;
&lt;br /&gt;
Unable to switch lighting profiles within Razer&#039;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 have a headache and will finish later. [[User:Dc1155|Dc1155]] ([[User talk:Dc1155|talk]]) 09:16, 12 February 2026 (UTC)&lt;/div&gt;</summary>
		<author><name>Dc1155</name></author>
	</entry>
</feed>