Support and General Use > Hardware

Memory access noise on Clip+

<< < (2/6) > >>

Gunbuster:
Hi Saint,

Please consider that English is not my native language, and also the fact that it's hard to tell someone who have far more knowledge that I will ever have that I have strong convictions he may be wrong to assume things this way, without sounding like a total ass.

Again based on my experience, the records I provided, and more importantly my ears, I think you and saratoga are both wrong.

But I know you have reasons to assume things like this and it will be hard to convince you both.

I myself would be surprised if one could state the fact that my device is not affected by 3.7 and 3.8 but it is with all subsequent versions starting from 3.8.1 is a total accident and nothing can be learn from this.

I would be glad if I could help the community by lending my device to a developer.

[Saint]:
Gunbuster,

I am aware of the fact that many people that use these forums do not speak English natively, and although I do try to adjust my language to suit this, it may be the case that misunderstandings occur. I understand this.

I want to make totally clear to you that no one is denying that you are experiencing issues with audible memory access. This issue has been reported multiple times, across different devices, it is not uncommon. It is a known issue.

No one is saying you are not experiencing this.

What is being said, is that it is basically impossible for a developer to do anything about this unless they have a device that shows the issue. Presently, to my understanding, no one does.

Another thing that was said is that it would be surprising if this issue presented itself in one version of Rockbox, but not another. I agreed with this. It is important to understand that this is not saying that you are incorrect or mistaken, it is simply saying it is surprising.

No one is saying you are incorrect.

Your findings are helpful, and appreciated, and no one said that it wouldn't potentially lead to the cause of the issue. What is being said, however, is that it is not something that can be reproduced on demand (many devices do not show this problem at all), which makes the issue incredibly difficult to fix unless a developer has a device that shows this issue. Recordings of the issue happening are great, but not useful for the purpose of solving the issue. The only thing the recordings would solve is doubt the issue exists, but there is no doubt of this.

I understand this must be frustrating for you, but it seems you think that we are denying the issue exists. We are not.


[Saint]

Gunbuster:
I acknowledge my wording was unfortunate.

It was not my intention to make a fuss about this, and I apologize for all the misunderstandings.

Thank you for taking your time to explain me why it can't be solved that easily even though I'm pretty confident about my finding.

If a developer is somewhat interested about this issue, please let me know, I will send him my devices right away.

404_user_not_found:
I tried to test noise difference from 3.13 and 3.7 in my Clip+ 8 GB, but I can't downgrade to 3.7 due the error "No Partition Found. Insert USB Cable and fix".

Gunbuster:
That's weird, is everything ok when you revert back to 3.13 ? How is 3.8 then ?

Navigation

[0] Message Index

[#] Next page

[*] Previous page