Continued...:
In my experience, the issue exist regardless of the state of this option.
Note: I accidentally posted before I was done, I'm unable to edit the post due to the time limit.
GrapheneOS It has nothing to do with the exploit protections.
Thanks. I simply tried various things to see if it changed anything. Sometimes, issues spawns for weird reasons and sometimes it doesn't make sense why it causes issues. So I tried to not make any assumptions of where the source of the problem could or could not be. I was simply turning rocks one by one. :)
GrapheneOS You likely caused the issue with how you configured these devices. It's not up to us to fix it. Factory reset the device and use it with default settings without changing a bunch of things or using any developer options. Should work fine.
I'm of course open to the possibility that I caused the issue. The same reason would likely also have to be true for the other people in this thread and those outside this thread who also have the problem. There would have to be one or multiple common factors which all produce this issue on these multiple devices, whatever the reason is that's causing this to happen. I just want to actually figure out what it is. No matter what or who, knowing the actual reason will be insightful and useful.
It seems like you may be under the impression that I expect you to fix it. That was never the case. I just wanted to see if I could get in contact with others who may have experienced this or who could provide some input or help in any way. And I appreciate every reply here. :)
I appreciate the suggestion, but factory reset and not configuring the device to my use-case or liking isn't an option for me. I configure my devices the way I do for a reason and it has value to me personally. I hope you can respect that. It's not that I want to fix the problem. A factory reset could fix it, but it would erase any chance of figuring out what cause it in the process. And there would exist speculation about why, without there being actual knowledge of what caused this problem.
I'm not sure what you mean by "without changing a bunch of things". If there's anything I and others here have changed that caused this issue, then I'd just be happy to know the reason. I think everyone else feel the same. What caused it isn't important, it's the useful knowledge of what actually that is and why it causes such a problem to appear. Though, I'm not aware of any proof that demonstrate or explain that something related to my, or any others' configuration, is the cause of this. It doesn't add up considering that the issue can exist without the configuration details on my device, which you seem to be referring to.
That's not to say I don't think it's worth looking into or that I'm denying or confirming it. I'm just saying that it needs investigation and evidence before we can make any conclusions. In the same way that anyone who wanted to claim GrapheneOS had a bug (or a dev did something) which caused a problem, would require the appropriate investigation and evidence to reasonably and fairly make such a claim. In the same spririt, I kindly ask that you don't claim that I, or others, did something to cause this, if you don't know this for a fact. :) I have no problem with you believing so, but claiming it as a fact wouldn't be fair or polite.
Respectfully, I just want to troubleshoot this and find the actual root of it and I hope that someone can help in some way or another in the process. Speculation can be great for brainstorming and troubleshooting, but I don't want to factory reset on the basis of speculation and the lack of evidence supporting that hypothesis.
I understand that it can be frustrating when users change stuff they don't understand and it causes problems, especially if they expect you to fix it or put the blame on you. It's not fair, nor is it kind. I don't expect anything, every help I and others here get, is greatly appreciated. I also don't claim to be an expert or oracle. But I'm certainly not a complete novice either. :) Whenever a user is interested in learning and figuring things out, I'd say that's good for everyone. There must be a way for us users to track down the root of the problem and I think I'm alone in being motivated to figure this out.
I'd greatly appreciate if you, or anyone, could please point me in the direction of sourcing down the root of the problem. Be it with logging, debugging etc. Gathering some data that can tell us more about the issue. :)