[8525, TyTN, MDA Vario II, JasJam General] sergiopi:
Nothing OFFICIAL :lol: published on line, on HTC website no FAQ on screen alignment problem: SA doesn't exist.

If you CALL (voice) or e-mail (nothing you can use in a court action against...) they know very well the problem

The UNOFFICIAL but REAL position is on HTCwiki site and is clearly explained:

http://www.htcwiki.com/page/TyTN quoted below

"TyTN

TyTN Release Date: July 2006

(a.k.a. Hermes, Vodafone 1605, Orange SPV M3100)

IMPORTANT: 70% of HTC TyTN devices have screen alignment problem!!!

HTC WILL NOT REPLACE IT AFTER TWO WEEKS, YOU CAN ONLY GET IT REPAIRED. So push it hard and make it hot on your first week after buying it to see if the screen alginment problem appears on your device, otherwise the screen alignment problem will appear later and your device will not be replaced, only repaired as per HTC DOA.

If you are thinking of buying an HTC TyTN, make sure you get an HTC636 or higher serrial number. Avoid S/N HTC62XXX and HTC63[1-5]XXX

Why is UNOFFICIAL and not only rumors from internet?

Beause the owner of the domain is the HTC communication agency

Because the commagency is the same for Microsoft and HTC

Because it has the HTC OFFICIAL Logo on it

Because it use the HTC official trademark (and HTC is stock quoted)

Because those info's are on line since many days and HTC and media agency leave it on line

From Waggener Edstrom website about their on-line strategies:

http://www.waggeneredstrom.com/what_we_do/expertise/online_communications.asp

Wikis. Wikis (pronounced wick-ees) are community Web sites with controlled access. They allow for real-time collaboration and communication, increasing both the flow of information and the ability to track that flow and dialogue. Waggener Edstrom Worldwide creates event wikis to help clients manage announcements, activities and communications efforts during product launches, conferences and events. The agency also develops wikis to manage issues and crises, helping companies quickly respond to issues and perceptions that arise during an event. We can provide pre-event wiki training as well as site monitoring, counsel and ongoing support. See also Virtual Pressrooms.

TO DO WITH BLOGGER, from Waggener Edstrom

DO’S

	Identify the top 10-20 bloggers your audiences should care about, based on:

	Topics they blog about

	Number of unique visitors

	Inbound/outbound links

	Audiences they reach

	Pick-up by mainstream media

	Google Page Rank

	Know what type of blogger they are (i.e. journalist, political pundit, corporate, gossip columnist, technology expert, etc.)

	Read them. Daily! Subscribe!

	Understand slant, tone, etiquette, and the writer’s bias.

	Be aware of how they have reacted to previous interactions with PR professionals.

	Look for rules of engagement. Many bloggers state these rules/guidelines up front.

	Identify frequent/influential links.

	Know your bloggers’ blogroll:

	Who’s on their radar screen?

	What do they watch, read, listen to?

	Use an RSS aggregator to track postings and links on relevant topics (i.e. Technorati, DayPop, Feedster, News Gator).

	Establish your own relationship with the blogger: Post a response, offer helpful resources and credible sources.

	Ensure your comments add value (key expertise, thoughtful analysis, new perspective, issue-oriented, etc.).

	Offer visuals, video clips and podcast interviews.

	Plan ahead: Establish relationships with bloggers by commenting on their sites, and linking to them for your own blog/client blog (if applicable).

	Understand the emerging role of blog networks. Where else is this blogger’s content posted?

HEY MEN TAKE A LOOK ON THEIR SITE: THEY SAID ARE LOOKING AT US, COMMENTING. DO YOU BELIEVE? HEY W.E. CRISIS UNIT, HAVE YOU UNDERSTOOD WHAT AND WHO YOU ARE FACING? IS A BIG GAME, AND WE KNOW HOW TO PLAY, MAY BE BETTER THAN YOU. WE ARE DIGITAL NATIVES, YOU'RE JUST DIGITAL IMMIGRANTS! :)

Sorry for the long post, I promise: it will be the only one, but we live in a complex world... an SA isn't only a TECHNICAL problem!