Kyo
Well-Known Member
Your solution to just not discuss something that obviously needs to be discussed will not solve anything, and provoking the thread to be closed is just stupid
Q: Warranty At 800Mhz?
- Thread starter PhonicUK
- Start date
- Status
WizardStan
Mega GP Mania
- Joined
- May 24, 2008
- Messages
- 16,731
You don't understand warranty. If the warranty says you can't overclock, and you overclock, the warranty is void. If something totally unrelated to the CPU that was not affected in any way by the overclocking occurs, even if it was previously covered by warranty, it will no longer be fixed for you since you did something that voids the warranty. That is what the original poster wanted to know: will they still fix other things if we overclock the CPU? This is not a fuss over nothing; even if overclocking does not cause any damage, even if CPU runs perfectly fine forever and ever and ever, if you overclock and something else breaks, you are boned.GPJosh said:Since many droid users have been doing this already for a while, this might be all be a fuss over nothing.
Last edited by a moderator:
mali
-
@dispute
Craig simply didn't know, that an ARM chip could be damaged by overclocking. The logical consequence would have been to say: "wait a moment, I have to contact the OP Team members to discuss this, and will come back to you". In that light, my introduction of that Asus example was way off the line, but how should I know? I was expecting that Craig just didn't want to talk about it. So I was very wrong. I apologize. It wouldn't have happened if you, Craig, would just have said something instead of trying to cancel my non-existent order.
I really, really hope we can take this embarrassing thread as a chance to improve communication on the boards. Craig, just be honest and I'll gladly help to bias the discussion positively. If we want to be a real community, we should act like one. Im willing to do so.
Craig simply didn't know, that an ARM chip could be damaged by overclocking. The logical consequence would have been to say: "wait a moment, I have to contact the OP Team members to discuss this, and will come back to you". In that light, my introduction of that Asus example was way off the line, but how should I know? I was expecting that Craig just didn't want to talk about it. So I was very wrong. I apologize. It wouldn't have happened if you, Craig, would just have said something instead of trying to cancel my non-existent order.
I really, really hope we can take this embarrassing thread as a chance to improve communication on the boards. Craig, just be honest and I'll gladly help to bias the discussion positively. If we want to be a real community, we should act like one. Im willing to do so.
PhonicUK
Member
WizardStan said:
+1
Last edited by a moderator:
borgqueenx
Well-Known Member
offtopic, but why didnt you pre-order for this great device?mali said:
Last edited by a moderator:
TaG
Fau-fau-faulty software.
I would rescind my post and apoogise for the language I used, but it's now in these damn pyramids.
Actually, I will apologise for my language, Craig.
Actually, I will apologise for my language, Craig.
Kyo
Well-Known Member
He did, but he canceled.
WizardStan said:
The following question is purely hypothetical. I'm an honest guy okay. And yes, sadly I do know my order number...
How willl OpenPandora know that you've been indulging in overclocking if some other non-cpu-component fails?
Last edited by a moderator:
Kyo
Well-Known Member
They could save it somewhere, but you can reflash the internal memory. So yeah, you could totally get away with it, hypothetically.
VRAndy
Well-Known Member
- Joined
- Sep 23, 2008
- Messages
- 1,127
Absolutely. He was doing work for free for a for-profit company. He had every right to stop at any moment. (Though, probably not the right to change the license to code he'd already handed over.)Poem58 said:
I was just saying that you can't say it wasn't a threat. Because it clearly was.
Last edited by a moderator:
renegadechic
Active Member
- Joined
- Sep 10, 2008
- Messages
- 787
this thread makes me sad. theres obvious a lot of stresses and frustrations going on with the various problems and its a shame things have gotten so passionate and volatile.
in many ways it makes me wish we were having a very basic (possibly even as basic as the ubuntu for netbooks GUI) as the only provided OS so that work like the PND format and other things could have been more distinctly separated from the project. as work is being doing to provide software and programs for release it is attaching the efforts more to the success of the project. if it was just clean cut an open device provided and then a community allowed free reigns then we would have fewer sad situations like this.
i hope that some time in the future when the dust has settled and we have a few batches out that these kinds of problems go away
in many ways it makes me wish we were having a very basic (possibly even as basic as the ubuntu for netbooks GUI) as the only provided OS so that work like the PND format and other things could have been more distinctly separated from the project. as work is being doing to provide software and programs for release it is attaching the efforts more to the success of the project. if it was just clean cut an open device provided and then a community allowed free reigns then we would have fewer sad situations like this.
i hope that some time in the future when the dust has settled and we have a few batches out that these kinds of problems go away
PhonicUK
Member
ashdjones said:
IIRC most CPUs 'blow' a fuse the first time they are overclocked beyond spec by more than about 5% (Error margin) I'm not sure how you check for this afterwards, but I've know a few people who overclocked some old AMD Durons, fried them, tried to send them back as faulty, got told no because they've been OC'd.
This is x86 though, I'm not sure if the same applies to the particular chips that the Panda use (Esp since they are binned, and the previous story is prior to AMD binning in major amounts if at all)
Last edited by a moderator:
Poem58
Active Member
Kyosys said:
So in other words, there is nothing anyone can do anyway to prove it so it really is up to your honesty? Then the debate is truly over. Just be honest people. It really is the best policy.
Last edited by a moderator:
This is a problem, as many of us are highly technical. We're the kind of nerds who know that data isn't really gone when you delete it.
What if the technical users don't even believe that overclocking causes damage? You think they'll be honest?
What if someone posts how to modify this hypothetical log file and posts it here? If this forum is independant then knowledge like that cannot be suppresed.
SNESFAN
Retro game fanatic
this brings up a conversation I had a while back on my theory why major manufacturers put limitations on their software to prevent tampering ..and detour piracy. Piracy taken out of the equation here. Companies try their hardest (within reason) to stop you from damaging your device via alternate firmwares etc because of the $$ it costs to repair the brick'd device because some dumbass user was monkeying around with their stuff. OP could just as easily say "you askew from the bundled software... warranty voided" I agree with craigix in that you dick with your gear they shouldn't be responceable for it... period.WizardStan said:
Don't be dicking around where your dick shouldn't be and you won't run the risk of catching a VD... i made a rhyme
Last edited by a moderator:
GPJosh
Addicted to Chrono Trigger
WizardStan said:You don't understand warranty. If the warranty says you can't overclock, and you overclock, the warranty is void. If something totally unrelated to the CPU that was not affected in any way by the overclocking occurs, even if it was previously covered by warranty, it will no longer be fixed for you since you did something that voids the warranty. That is what the original poster wanted to know: will they still fix other things if we overclock the CPU? This is not a fuss over nothing; even if overclocking does not cause any damage, even if CPU runs perfectly fine forever and ever and ever, if you overclock and something else breaks, you are boned.GPJosh said:Since many droid users have been doing this already for a while, this might be all be a fuss over nothing.
Very true, I was thinking about the end user who decides to overclock anyway (knowing full well that this violates the warranty, if that's what the case is). Myself, I'm probably going to keep it at 720 max and buy + replace the board if this does, in fact, fry something. It seems there's really no way to know until some real world testing is done either by OP or us first batchers try for an extended period of time.
Granted there are way bigger issues going on in this thread, mainly the situation and reactions getting way out of control.
It seems now that things have come down a bit and everyone is talking rationally again, so I'm happy - that's all I was trying to say.
Last edited by a moderator:
SNESFAN
Retro game fanatic
that's probally why no companies share OP's policy... it gets expensive to be at the will of tinkerers.ashdjones said:
Last edited by a moderator:
mali
-
I think the most reasonable solution lies somewhere in between. Allow overclocking till a certain value without voiding warranty. Above that value further overclocking voids the warranty. OP won't have a chance to prove if someone went beyond that limit, so it depends on the users honesty to find out. Maybe no Pandora will ever fail because of overclocking and all of this is a non-issue. To block overclocking or to put nifty tricks that save that info to flash is no satisfying solution, because Pandora has been advertised as being overclockable till yesterday. I'm sure the OP team will find a solution we all can live with.
- Status
