Best Buy has announced that customers pre-ordering the Samsung Galaxy Note for AT&T beginning February 5th will receive a little something extra for their interest. Pre-ordering the Note at a Best Buy/Best Buy Mobile store or online earns future owners a flip cover case to protect that sizable 5.3-inch display. The case normally retails for $29.99. The Galaxy Note will retails for $299.99 when it launches February 19th.

[via Best Buy]

http://phandroid.com/2012/02/03/best-buy-offering-flip-cover-case-with-galaxy-note-pre-orders/

Android Phone Fans

UPDATE: The Android Team’s Dan Morrill has posted an explanation for the removal of the Galaxy Nexus and other CDMA devices from the official developer support page. This has nothing to do with Google Wallet (we never thought it did) and everything to do with the way the Android code is compiled for CDMA devices. In short, if a dev were to simply compile the pure AOSP source code for the Verizon Galaxy Nexus the build would be lacking in full telephony functionality. Google still plans to support the devices directly via software updates.

A quick visit to the Android developer support page reveals some startling news. It appears as if Google is dropping the “developer device” tag of once-listed CDMA models. The Samsung Nexus S 4G, Verizon’s Motorola XOOM, and even the LTE Galaxy Nexus have disappeared from the site, leaving us with a note explaining exactly which versions of these devices will be supported moving forward. For the XOOM, only the “wingray” WiFi-only version of the slate gets developer designation. The GSM “crespo” version of the Nexus S also retains support. For the Galaxy Nexus, the GSM/HSPA+ “maguro” build is supported, but only if it originally shipped with the “yakju” build of Android 4.0.

We can speculate as to exactly why Google has decided against the inclusion of CDMA developer devices, but the fact that Sprint’s Nexus S 4G didn’t make the cut should silence those ready to blame Verizon and Google’s past disagreements about Google Wallet. In reality, Google is likely looking to simply streamline support and GSM tends to be the more global-ready network technology. CDMA devices function on a very limited portion of the globe’s cellular networks (despite Verizon and Sprint, two of the world’s largest carriers, both utilizing CDMA).

Does the removal of these devices from the developer support page mean they won’t be treated to the quick Android software version updates typically associated with the Nexus line? We get the feeling OS updates will still reach these devices just as quickly, if only due to their stock user interfaces. It’s hard to imagine Google neglecting any member of their Nexus family, lest they want to send mixed signals. And we’re not looking to have our hearts toyed with like that.

[via DroidLife]

http://phandroid.com/2012/02/03/verizon-galaxy-nexus-other-cdma-devices-no-longer-listed-with-google-developer-support/

Android Phone Fans

Because apps are the answer to any woe, Yahoo is trying to turn people’s obsession with smartphone software into page views with the introduction of Android Market (and iOS) search results. An apps tab can now be found when using Yahoo to search the web. Users can view Yahoo’s suggested apps or poke around for whatever suits their taste. Results can be filtered by operating system, price, and category. Application pages provide reviews from the Android Market as well as Yahoo users, but do little more than act as a forwarding page to the Android Market. Was this even necessary? Save a step and search directly through Google.

[AndroidCentral via Engadget]

http://phandroid.com/2012/02/03/yahoo-attempts-to-stay-relevant-now-searches-android-market-apps/

Android Phone Fans

USA TODAY

http://news.google.com/news/url?sa=t&fd=R&usg=AFQjCNE_mrSoLhNidnkopkC_yskmuDiMEg&url=http://www.usatoday.com/news/politics/story/2012-02-04/republican-nevada-caucus/52957864/1

nexus one – Google News

Globe and Mail

http://news.google.com/news/url?sa=t&fd=R&usg=AFQjCNEIWZz9Qcwr8dwZWp_6VNYxU1RcRQ&url=http://www.cnn.com/2012/02/04/world/meast/syria-unrest/?hpt%3Dhp_t2

nexus one – Google News

USA TODAY

http://news.google.com/news/url?sa=t&fd=R&usg=AFQjCNEU5zUWMJKwEMAEHfuFKwlAcZ0dFQ&url=http://www.reuters.com/article/2012/02/05/usa-protest-washington-idUSL2E8D413520120205

nexus one – Google News

Google has filed an application with the FCC for a 6-month permission to test a home entertainment system involving WiFi and Bluetooth enabled devices. While I don’t quite understand all the legal-speak, it seems quite clear that the system has to do with Android@Home, which was announced at Google I/O 2011. You can find the application here.

Please explain in the area below why an STA is necessary: 

Google is developing an entertainment device that requires testing outside the laboratory environment. The device is in the prototyping phase and will be modified prior to final compliance testing.

Please explain the purpose of operation: 

Testing throughput and stability of home WiFi networks using an entertainment device. Testing will include functional testing of all subsystems, including WiFi and Bluetooth radio. Users will connect their device to home WiFi networks and use Bluetooth to connect to other home electronics equipment. This line of testing will reveal real world engineering issues and reliability of networks.

What do you think said “entertainment device(s)” will include? With Android@Home, Android Open Accessory, and Google TV yet to make a huge splash, it could be Google I/O 2012 where physical products, accessories, and readily available apps and games make their first appearances. What do you think Google is dreaming up?

http://phandroid.com/2012/02/04/google-testing-mystery-entertainment-system/

Android Phone Fans

Many of you might have heard about PandoDaily, a new tech blog that was launched on the 16th of January by Sarah Lacy, a former TechCrunch writer. One particular article caught my attention, primarily because of it’s title: How Google can save Android: Close it. License it. Swim in the Profits.

The writer, Farhad Manjoo, isn’t the first person to make the suggestion, and he most certainly isn’t going to be the last. Many have used the example of Amazon’s Kindle Fire and other such Android forks to suggest that Google’s strategy is back-firing. To his credit, the article doesn’t come off as an Apple fanboy mocking Android as many such posts do, and has offered some decent ideas.

But I must admit, right from the beginning the article seemed to miss the bigger picture. And that seems to be the case with all journalists, especially since Apple’s outstanding quarterly results which have put Google’s "failures" in the spotlight.

Google’s main competition isn’t Apple. It’s Facebook.

Google’s business, at this point, is advertising. And the most important resource for it’s business is information. It’s the same thing with Facebook. Google and Facebook are, as such, competing for the same pie. Apple, on the other hand, is a hardware company. It’s profits come almost entirely from the huge margins it has on all of its devices.

For Google to take on Apple in terms of profits and revenues, it has to virtually pivot itself into a consumer electronics company. Admittedly, the purchase of Motorola speeds things up a bit, but with Moto struggling it would be a long, hard struggle to reach the required level.

"Closing" Android will only make a bigger mess

This is where Manjoo gets it wrong almost entirely. While in theory it would increase Google’s earnings from Android, it’s an extremely short-sighted option.

The move would hit the wrong note with the developer community who have flocked around Android because of its open nature. Additionally, it’s going to give all those who have already (unfairly) questioned Android’s open sourced nature a chance to say "I Told You So".

Also, the quoted amounts in Manjoo’s arguments are just plain wrong. The $25-30 amount for a Windows Phone license is what ZTE say they’re being charged. While there’s no confirmation about it, most believe the major manufacturers like Samsung and HTC pay about $15/device for a license. Considering they already pay about $5/device to Microsoft, a $10 charge from Google removes the current monetary benefit that comes with Android. And knowing MS, they’d probably reduce the amount they charge to push WP7 forward.

Who’s to say manufacturers won’t create their own forked versions of Android from the ICS code? They’ve already invested heavily in their own custom skins, they might just decide to use their current code as a base for their own operating systems, say Sense OS or TouchWiz OS.

Closing Android could actually cost Google

Manjoo quotes that Google makes $6-10 per user per year in mobile ad revenue based on a study. While I have my doubts about it, I’ll agree to it for the argument’s sake.

If closing Android results in more forks, it gives Microsoft a big opportunity to throw money at the manufacturers to put Bing as the default search engine on their devices. So not only does Android lose significant marketshare as a direct result, it ends up costing Google $6-10 per user, per year in revenue. They would need to sell as many licenses as the Bing-ed Android forks just to maintain status quo.

Additionally, we must keep in mind that mobile advertising is still in its infancy. It might not be as profitable as desktop ads right now, but more and more money is coming in as businesses shift their focus to mobile-users themselves.

The Kindle Fire has proved to be a boon for Android Tablets

As you might have read recently, Android tablets now enjoy a 39% marketshare. And a lot of the credit goes to the Kindle Fire. While it isn’t the "real" Android, it still puts a dent in the iPad’s success.

Manufacturers like Asus have also learnt their lessons, and as a price war starts, I expect to see a number of a good options in the $200-300 range this year. As a result, we could quite possibly see Android and iOS having an equal share in the tablet market by this time next year, which would be quite a feat considering where we were just a few months ago.

So what do you think: does Google really need to “save Android”? And either way, how do you feel about Manjoo’s suggestions to close off our beloved open OS?

http://phandroid.com/2012/02/04/android-does-not-need-saving/

Android Phone Fans

It had been quite a long wait for the official Wikipedia app to land on the Android Market. Barely two weeks after launch, it has racked up over 500,000 downloads with a 4.5 star average rating. And now, the team behind the app has posted a blog describing the development process.

The most interesting bit to note is the use of PhoneGap, the web-technologies based cross-platform development tool. Such tools have seen a rise in popularity because of the ability to target multiple platforms with the same code.

"Rather than diving into proprietary frameworks and SDKs, our application has been built on the same foundation as the open mobile web. And not only does this allow us to prepare for the future, it also accelerates our ability to develop across numerous platforms.

Within a short amount of time we’ve already developed a testing version of our iOS app with PhoneGap and we’ve established our first complete community port to the BlackBerry PlayBook. This demonstrates the power of using open tools and communities to improve the Internet as a whole and it is a critical component to our long term goals."

Many have argued that apps built using web technologies are no match for those built natively. Yet, despite having dabbled with PhoneGap quite a bit myself, I only learnt of its use by the Wiki team upon reading the blog post. Adobe bought PhoneGap’s parent company, Nitobi, last fall prior to announcing the end of mobile Flash.

Do you think Wikipedia’s use of PhoneGap foreshadows a shift towards open web-based technologies in favor of natively built apps?

http://phandroid.com/2012/02/04/wikipedia-discusses-the-development-of-its-app/

Android Phone Fans