The Finnish phone maker reiterated that customers can either download and install the patch or exchange their phone at an AT&T store. Nokia had originally said to expect the software update to be ready by Monday.

“Consumers now have the opportunity to update their AT&T version Nokia Lumia 900 software through Zune and Windows Phone 7 Connector for Mac earlier than anticipated,” Nokia said in a statement.

All Lumia 900 customers, regardless of whether they have had problems, will get a $100 credit, Nokia U.S. head Chris Weber told AllThingsD earlier this week. Customers that buy or order a Lumia 900 before midnight PT on April 21 will also get the credit.

That effectively makes the device free, for now, since AT&T had been selling it for $99 with a new two-year contract.

Nokia has gotten plaudits for its prompt and generous dealing with the issues. However, the glitches still threaten to diminish the launch of a product seen as key to the ambitions of Nokia and Microsoft to take on the top smartphones and re-establish themselves as serious players in the U.S. market.

The issue was particularly unfortunate given the teaser campaign that Nokia had run, touting that the arrival of the Lumia 900 meant that “the Smartphone Beta Test was over.”

Nokia U.S. chief Chris Weber told AllThingsD that the problem is a memory-management issue with the phone’s software, and is not tied to any hardware issues or to a flaw with AT&T’s network. The connection problem affects only a limited number of customers, Weber said.

Nokia has created a software fix, and all customers can swap their device at an AT&T store for an updated one or download a software update starting around April 16.

“We’re already manufacturing devices with the new software,” Weber said. “Those are being shipped to AT&T stores.”

The company is offering a $100 credit to all customers, regardless of whether they are encountering the problem. The $100 credit is also being offered to any customer who purchases a Lumia 900 before midnight PT April 21, effectively making the device free.

“The customer always comes first, and I think we’re showing it here,” Weber said in an interview.

Weber said the cost of the program depends on how many people purchase Lumia devices through April 21, and said that the expense was not the issue.

Nokia, he said, was focused on “how do we do something unprecedented for any inconvenience, (and) pleasantly surprise the customers.”

Nonetheless, the issue is clearly not the way the company hoped to launch what is designed to be a flagship product aimed at reestablishing the company as a major smartphone presence in the U.S.

“Obviously you don’t want these things to happen,” Weber said.

AllThingsD’s Walt Mossberg noted in his review that he experienced some other issues with the 900, including problems loading Internet Explorer pages over Wi-Fi.

Weber hopes the company will be remembered more for how it handled the problem than for the issues themselves. And, he said, visits to six Chicago-area stores on Monday affirmed for him that enthusiasm for the Lumia 900 is strong.

“We’re seeing incredible customer excitement and buzz,” Weber said. “I think we have a very compelling device that customers are excited about.”

Nokia, Microsoft and AT&T are all counting on big sales for the device and have said they are putting unprecedented marketing behind its launch.

Oddly, though, the product went on sale on Easter Sunday, a day when most of the Microsoft and AT&T stores that carry the device were closed.

As for how such a significant issue could have made it through the company’s testing processes, Weber said, “That’s something we are doing a current investigation on.”

It’s particularly unfortunate given that one of Nokia’s marketing pitches for the Lumia 900 was an online and TV ad campaign saying that the Smartphone Beta Test was over, and encouraging existing smartphone owners to trade in their “beta” Androids and iPhones for a real smartphone.

In a blog post by one of its execs, titled “Flash to Focus on PC Browsing and Mobile Apps; Adobe to More Aggressively Contribute to HTML5,” Adobe said what had already been reported: That it would no longer be developing its well-known Flash for mobile devices.

Here’s the key graph:

“Our future work with Flash on mobile devices will be focused on enabling Flash developers to package native apps with Adobe AIR for all the major app stores. We will no longer continue to develop Flash Player in the browser to work with new mobile device configurations (chipset, browser, OS version, etc.) following the upcoming release of Flash Player 11.1 for Android and BlackBerry PlayBook. We will of course continue to provide critical bug fixes and security updates for existing device configurations. We will also allow our source code licensees to continue working on and release their own implementations.”

Last night, reports surfaced that the high-profile software company — whose Flash technology has been a flagship product — was halting development on the mobile version of its browser plug-in.

Now, Adobe will focus its PC Web browser business on tools that allow Flash developers to create mobile apps by packaging their code to run on Adobe’s AIR platform.

The move has big implications for Adobe going forward and also for mobile device makers, such as Google and Research In Motion. But not Apple.

As Ina Fried wrote:

“The move, if true, would be a major blow to Android device makers, who have long touted Flash compatibility as a key competitive advantage over Apple’s iPhone and iPad.

It would also mark a posthumous vindication for former Apple CEO Steve Jobs, who took a controversial stand by not supporting Flash on Apple’s mobile products.”

Turns out Jobs was prescient, as usual.

Here is the full version of the Adobe blog:

Flash to Focus on PC Browsing and Mobile Apps; Adobe to More Aggressively Contribute to HTML5

POSTED BY DANNY WINOKUR, VICE PRESIDENT & GENERAL MANAGER, INTERACTIVE DEVELOPMENT AT ADOBE ON NOVEMBER 9, 2011 5:59 AM IN BUSINESS PROFESSIONALS, CREATIVE PROFESSIONALS, DEVELOPERS, VIDEO

Adobe is all about enabling designers and developers to create the most expressive content possible, regardless of platform or technology. For more than a decade, Flash has enabled the richest content to be created and deployed on the web by reaching beyond what browsers could do. It has repeatedly served as a blueprint for standardizing new technologies in HTML. Over the past two years, we’ve delivered Flash Player for mobile browsers and brought the full expressiveness of the web to many mobile devices.

However, HTML5 is now universally supported on major mobile devices, in some cases exclusively. This makes HTML5 the best solution for creating and deploying content in the browser across mobile platforms. We are excited about this, and will continue our work with key players in the HTML community, including Google, Apple, Microsoft and RIM, to drive HTML5 innovation they can use to advance their mobile browsers.

Our future work with Flash on mobile devices will be focused on enabling Flash developers to package native apps with Adobe AIR for all the major app stores. We will no longer continue to develop Flash Player in the browser to work with new mobile device configurations (chipset, browser, OS version, etc.) following the upcoming release of Flash Player 11.1 for Android and BlackBerry PlayBook. We will of course continue to provide critical bug fixes and security updates for existing device configurations. We will also allow our source code licensees to continue working on and release their own implementations.

These changes will allow us to increase investment in HTML5 and innovate with Flash where it can have most impact for the industry, including advanced gaming and premium video. Flash Player 11 for PC browsers just introduced dozens of new features, including hardware accelerated 3D graphics for console-quality gaming and premium HD video with content protection. Flash developers can take advantage of these features, and all that our Flash tooling has to offer, to reach more than a billion PCs through their browsers and to package native apps with AIR that run on hundreds of millions of mobile devices through all the popular app stores, including the iTunes App Store, Android Market, Amazon Appstore for Android and BlackBerry App World.

We are already working on Flash Player 12 and a new round of exciting features which we expect to again advance what is possible for delivering high definition entertainment experiences. We will continue to leverage our experience with Flash to accelerate our work with the W3C and WebKit to bring similar capabilities to HTML5 as quickly as possible, just as we have done with CSS Shaders. And, we will design new features in Flash for a smooth transition to HTML5 as the standards evolve so developers can confidently invest knowing their skills will continue to be leveraged.

We are super excited about the next generations of HTML5 and Flash. Together they offer developers and content publishers great options for delivering compelling web and application experiences across PCs and devices. There is already amazing work being done that is pushing the newest boundaries, and we can’t wait to see what is still yet to come!

Memo to Flipboard, as well as Pulse, CNN’s Zite and AOL’s Editions: You might want to make some room in the already-crowded news and social reader space, because you’re about to get some bigfoot company.

Next Wednesday, according to sources close to the situation, Yahoo will finally officially unveil its offering, called Livestand.

And perhaps as early as next week or in the weeks soon after, Google will also weigh in with its version of the genre — code-named Propeller — which also might be the product’s name. Another moniker under strong consideration: Currents.

As I have previously reported, Google Propeller is an HTML5 reader for the Apple iPad and Android — essentially a souped-up version of similar apps such as Flipboard, AOL’s Editions, Zite (which was just bought by Time Warner’s CNN) and Pulse.

All these apps are part of the drastically changing habits of media consumers, helping users better navigate numerous social and media feeds — such as Facebook and Twitter, as well as news sites and more — using handsome interfaces and touch technologies on tablet devices.

Flipboard, the most prominent and elegant of these offerings, is now available only on the Apple iPad.

Flipboard’s traction among elite users, along with its high-level design ethos and strong reviews, is why Google tried to buy the well-funded company last year, sources said.

But Flipboard — which is backed by some of tech’s biggest venture players, who have invested more than $60 million at a $200 million valuation — declined the kind offer.

At the time, sources said, Google told Flipboard execs that if it did not buy the start-up, it planned to do a version of its own.

Hence, after I heard about the product earlier this year, I dubbed it the Flipinator.

According to sources, Propeller will launch with a plethora of media partners, as well as integration into the Google+ social network. The aim of the search giant is to offer media companies easy tools for publishing content on these devices, as well as a better path to monetization.

That is essentially the same plan at Yahoo, which has been working on Livestand with hopes of it being a product that will woo publishers into tight collaboration with the Silicon Valley Internet giant.

Livestand was announced by Yahoo’s now-fired CEO Carol Bartz in February, at a speech at the World Mobile Congress in Spain.

At the time, Bartz demoed a magazinelike platform that would allow publishers to put up content easily and give users the ability to personalize their selections based on search history and interests.

Bartz called it “content in context.” (You can see the demo video below.)

But while Bartz promised the product within three months, development has been slowed by its complex technologies, bugs and the need to sign on publishers.

Yahoo’s Chief Product Officer Blake Irving is pushing the product hard as a way for the company to reinvigorate its media products.

It’s not clear how many publishers Yahoo will have at launch, and neither are the distribution plans, beyond flacking it from the Web site and being present in app stores.

Google, on the other hand, has its Android platform to push out Propeller, although it all must work as well on Apple’s iPad, which is the dominant tablet on the market.

But just because both Yahoo and Google are big companies is by no means a guarantee of success — think Yahoo 360 or Google Wave or Buzz — and their lateness might be a hindrance.

And, in fact, other news reader apps are much further along. The leader, Flipboard, has already had four million downloads and 50 partnerships with leading publishers.

It also has started to introduce rich advertising products and, perhaps most importantly, has tight social integration with Twitter and Facebook.

There will be social elements on both Yahoo’s Livestand and Google’s Propeller. But news reading will be stressed more, making them more like Pulse, a tiny but highly innovative start-up.

Each of the existing apps will presumably compete by adding on more features. Pulse recently added cross-platform, cross-device syncing, while Flipboard is close to unveiling an iPhone version it has said it was working on.

Yahoo and Google PR declined comment.

Here is the Livestand demo video from February:

CIO Lars Rabbe says in a blog post that a set of support servers responsible for Skype instant messaging became overloaded, and as a result sent delayed responses. A bug in the latest Windows version of the Skype desktop software failed to process these delayed responses, causing them to crash. About half of the world’s Skype users who were signed on at the time the problem began were using that version of the software, and of those, about 40 percent crashed. Among them were users whose machines were serving as supernodes. Rabbe says as many as 30 percent of the Skype network’s supernodes were among the crashed machines.

Losing those supernodes increased the load on other still-functioning supernodes, which was compounded by all the crashed Windows users trying to restart their software and get back on the network. He says traffic to these supernodes surged to 100 times normal volume for that time of day.

What he doesn’t go into great detail about was why the instant messaging servers became overloaded in the first place. Was this another bug in the server software? It’s a little unclear from this explanation.

Rabbe says Skype is trying to learn from the incident and has instituted new procedures to try to prevent this sort of thing from happening again. But this can’t help but hurt its reputation as it looks for ways to diversify its base beyond the millions of free users it has and make some actual money.

The whole reason Skype is supposed to work as well as it usually does is the strength and resilience of the network, and the fact that the network gets stronger as more people are signed on to it. To say that two bugs in a strange confluence of events could bring that entire network down raises a lot of fundamental questions about Skype.

Rabbe says an investment program to increase capacity to support paid consumers and enterprise customers is underway and will continue into 2011. I’m betting Skype will speed it up.

Facebook said the issue only affected a “fraction of a percentage” of the social network’s users, and they fixed it within hours. The company also deleted all the ID information that some people sent in.

But the incident raised an interesting question: Why was Facebook asking for real-world IDs in the first place?

Unlike some other social networks, Facebook takes pride (and pitches advertisers) on the idea that its users present their real-world selves. But the ID request isn’t part of a broader effort to verify users’ identities–something that sites in countries such as China sometimes do.

Read the rest of this post on the original site

“I just noticed a flaw on my display,” one wrote in a message to Apple’s support forums. “It wasn’t very obvious, i was messing with the phone for a good 45 minutes till i even spotted it. On the bottom 10% of the screen there are 3 blotches about the size of shirt buttons that discolor the screen a brown/yellow color. Again hardly noticeable at first but now that i know it’s there my eyes get drawn too it. Shows up well when its a white background. I was hoping it was just some grime but wiping down the front didn’t help. Oh well, guess i’ll hang onto it until Apple gets a few more in stock and trade it in a few weeks from now.”

Similar reports are showing up on Gizmodo and MacRumors, where the blotch is described as more of a bar. “Just synced up my iPhone 4 and noticed that, on screens with a white background (i.e., Settings.), there is a decidedly yellow spot on the lower left corner of my screen,” another report reads. “It appears circular (about the size of a pencil eraser) but when you rotate the phone sideways, it’s more visible as running across the bottom edge of the screen a ways.”

It’s not yet clear how widespread the issue is, but there are enough complaints on Apple’s (AAPL) support forums to be concerning. I’ve asked the company for comment and will update here if offered one.

Meanwhile, reports of problems with the iPhone 4′s signal-strength bars are beginning to circulate as well. But as Walt Mossberg noted in his review, this is a known issue that Apple intends to fix:

In some places where the signal was relatively weak, the iPhone 4 showed no bars, or fewer bars than its predecessor. Apple says that this is a bug it plans to fix, and that it has to do with the way the bars are presented, not the actual ability to make a call. And, in fact, in nearly all of these cases, the iPhone 4 was able to place calls despite the lack of bars.

However, on at least six occasions during my tests, the new iPhone was either reporting “no service” or searching for a network while the old one, held in my other hand, was showing at least a couple of bars. Neither Apple nor AT&T could explain this. The iPhone 4 quickly recovered in these situations, showing service after a few seconds, but it was still troubling.

[Image credit: elitemrp, Apple Support Discussions]