backtop


Print 16 comment(s) - last by omnicronx.. on Jul 27 at 11:34 AM


The Galaxy S lineup will be upgraded to Android 2.2 with Flash 10.1 support.  (Source: Samsung)
All major U.S. carriers will get Galaxy S variant, Froyo

After bungling the Behold II's Android update with a will-they-won't-they approach, Samsung is attempting to cast aside any doubts that its upcoming line of Galaxy S phones will suffer the same fate.

Samsung announced the welcoming news last night via a Twitter post:

Galaxy S phones will come with Android 2.1 and be upgradeable to Android 2.2 which will support Adobe Flash 10.1

The announcement comes fresh off the heels of another Galaxy S development. Though we've recently covered T-Mobile's Galaxy S variant, the Vibrant, as well as AT&T's Captivate, according to CNET, the super AMOLED smartphone will be available in some form or another on all the major U.S. carriers.

While we've also covered Sprint's Galaxy S Pro, the only full QWERTY device in the initial Galaxy lineup has been dubbed "Epic". In addition to its spec sheet, the device will come with a video store to download movies and TV shows, though it is unclear at this time who will provide the content.

Verizon -- not to be left in the other carriers' warp trail -- will entice consumers with the Fascinate, which sounds to be almost identical to the Vibrant and Captivate. Two things stand out about the Fascinate that have not been revealed on the other variants, though: support for numerous video codecs, including DivX, and DLNA support, which allows wireless sharing between other DLNA-supported devices like HDTVs and gaming consoles.

The fifth-largest mobile provider (and most often-overlooked), U.S. Cellular will be receiving a version of the Galaxy S as well.

Availability and pricing of Verizon, Sprint, and U.S. Cellular's handsets has not been announced.

And while Froyo will be coming to the Galaxy S handsets at one point or another, MyDroidWorldhas leaked an official test build for Motorola DROID users that includes root access and a customized kernel.



Comments     Threshold


This article is over a month old, voting and posting comments is disabled

RE: Useful cheat sheet
By Mitch101 on 6/30/2010 10:17:53 AM , Rating: 4
Definitely looks like a sweet device but I think droid is creating a problem with such fragmented hardware screen sizes and hardware specs through the droid line. As a developer its a headache taking into consideration how many possible hardware/screen resolutions droid devices have.

But if I had to pick a droid phone device I would go that route being the top end of the spectrum it should run every available app and then some for a while.

The nice part about Microsoft Mobile 7 is they drew a line in the sand and said can only have two screen resolutions and must be multi touch, much have this minimum CPU and this graphics power, must have 7 megapixel camera or better, options like GPS and accelerometer must be in every device. Much easier to develop for the device when every version of the device has a minimum spec. In droid world it might be more flexible but your apps may not work across every device. Google should draw the line in the sand and say version 2.2 must have this hardware spec minimum and nothing less.


RE: Useful cheat sheet
By adiposity on 6/30/2010 12:41:24 PM , Rating: 3
Droid and Droid X (and probably Droid 2) have same screen res (848x480). But I would design for 800x480. Then the droid/droid x/droid2 has a few extra pixels...at worst you can leave 48 pixels empty or put some useless ad there. And Nexus1/Samsung phones/Evo/Incredible will work.

I don't agree with Win7 and the mandated resolution. It has good intentions, but the result is, I can't buy a higher res phone if I want one. Personally I like my extra 48 pixels when reading web pages.

And all the apps I use work fine on my Droid and my buddy's incredible. So I'm not sure the screen res difference is that big of a problem.


RE: Useful cheat sheet
By Mitch101 on 6/30/2010 12:59:09 PM , Rating: 2
Not slamming just pointing out droid screen/resolution go beyond the two devices you mention.

http://developer.android.com/guide/practices/scree...

Although the platform currently supports the nine possible size-density configurations listed in the table, you do not necessarily need to create custom resources for each one of them. The platform provides robust compatibility features, described in the sections below, that can handle most of the work of rendering your application on the current device screen, provided that the UI is properly implemented.

Droid Resolutions
240x320
240x400
240x432
320x480
480x800 (160 and 240 hdpi)
480x854 (160 and 240 hdpi)

As a developer I have to agree with Microsoft's Mobile 7 support of two screen sizes it allows for much easier development of the UI also Microsoft provides templates for easy user interface view. Personal preference maybe but I like developing knowing I can program for one common hardware set.


"Can anyone tell me what MobileMe is supposed to do?... So why the f*** doesn't it do that?" -- Steve Jobs














botimage
Copyright 2014 DailyTech LLC. - RSS Feed | Advertise | About Us | Ethics | FAQ | Terms, Conditions & Privacy Information | Kristopher Kubicki