Thanks for all your messages, they've been of great help, although you only give hints of solutions, not the real solution itself.
I'm afraid that's all we can do. There's simply no one-stop-fixes-all answer.
If by "system" you mean Android, then it's not that it doesn't like mode-N, it simply doesn't support it. There's actually quite a good reason for that.... I don't think there's an N-mode chipset available for mobile devices yet.This version of the system really doesn't like N networks. But seems to go ok on B and G. The older the better - it's a collectionist hehehehe...

Erm, iPhone doesn't support N-mode either for starters. Plus it's still not certain that the 'flaw' IS with the Hero; it could just as easily be with the routers. To use a more familiar example, a web page written strictly to comply with W3C standards will still not display correctly in IE. This doesn't mean that the HTML code is broken..... similarly rewriting that page to display correctly in all browsers doesn't mean that the code is good. Right now there's not enough data to say for sure what the cause is, so all we can do is look for cures.But it's really a huge flaw from HTC, former Q-Tek, former Qualcomm... iPhone has it's flaws and had much more, but how come the HTC guys didn't test this before selling?
One other thing: I'm another one-in-a-million whose Hero connects to my router without problems. I sure don't know why that's the case but if/when I do we might be nearer finding a workable solution for everyone.
/Al


So it's still a little useless.