Sorry wasn't dismissing what you had to say.emil10001 said:Na-Noo said:It's not always as simple as that. It could need a hardware fix. But fingers closed for software....
Right, but my question was hadn't they already tested the hardware to validate their design? I remember earlier iterations where nobody was really saying that wifi was a problem, aside from not having a decent front-end to manage it. I have followed the current situation, and I'm wondering:
a) if the dev team things that this is only a software issue, or if there might be hardware problems as well?
b ) if it is only a software issue, then why not just release it as-is and let us help fix the problem?
c) if it is possibly a hardware issue, where do you go from here? I am not really sure that I would feel comfortable accepting a device with a known hardware flaw that hampers core functionality of the device. I wouldn't have a problem with it being a software issue, but it's not exactly easy to roll-out a hardware patch a couple of months down the line.
d) if it is a hardware issue, why didn't we hear about this when the initial testing was done? IIRC, we were told that everything was good, and all that needed to be done was a front-end. (I realize that this was a few versions ago, but if the hardware works, then the hardware works, right?)
EDIT: @ED - that seems like a reasonable solution to me. I would be perfectly happy having the hardware in my hands plus the dongle and then getting it exchanged months or a year or so down the line when it gets worked out. I might even pay extra for it to be done sooner.
It's amazing just how these things can 'slip' through.
I'll not even go into all the different gpu's that's been broken on hardware level. <_<
Last edited by a moderator: