Showing posts with label smartphone. Show all posts
Showing posts with label smartphone. Show all posts

Sunday, May 6, 2012

Samsung Galaxy S III: disappointment, gimmicks, or good ideas?

We had planned to do this writeup yesterday, but everything felt too fresh. The Samsung Galaxy S III announcement created a tidal wave of news and we didn't want to just post a knee-jerk analysis of what had been announced, because there was quite a lot of information unpacked at Samsung's London event. The thing is that it didn't all hit solidly.


The disappointments

Of course, we have to keep in mind that the expectations were pretty high for the Galaxy S III announcement, and carriers had tried to mitigate those expectations to a certain extent, even saying that "It'll be like the iPhone 4S was to the 4," which turned out to be the most prophetic information we ever saw during the rumor rampage, even though it may have slipped through the cracks. As far as the hardware, this is definitely much more of an incremental update, which is a bit disappointing, but probably what we should have expected.

Sure, the international version will have a quad-core processor, but that really just sounds good on paper, because in the actual benchmarks that we saw, the dual-core Snapdragon that is expected to be in the US version (and currently in the HTC One X) posted pretty close numbers on Quadrant and actually beat out the quad-core Exynos on a few tests. The screen is essentially the same as that we've seen on the Galaxy Nexus, with the same PenTile matrix, just .2" larger (and without on-screen buttons, which will add even more usable space.) Aside from those two features, all of the other additions are software. And, in the software we get to the usual array of gimmicks and good ideas.

Before we get to the gimmicks though, we want to note one overall disappointment with the Galaxy S III announcement: Samsung almost completely avoided the fact that this is an Android device. Everything in the presentation was made out to be an amazing feature that is only available on this Samsung device. We understand that's how marketing works, but it's still annoying. S Voice leverages the power of the Android voice command service, but adds value in natural language recognition. The Galaxy S III camera has zero shutter lag, but that is a feature of Android 4.0, not that phone. S Beam is simply Android Beam with the addition of WiFi Direct for larger file transfer (admittedly Samsung did at least mention Android Beam on that one.) And, we're pretty sure that Smart Stay wouldn't have been as easy to implement without the built-in facial recognition of Android 4.0.

All we're saying is credit where it's due. Samsung has built quite an empire on Android, so it would be nice to see a bit more appreciation. We won't even get into how TouchWiz completely hides the UI improvements of Android 4.0, because that's a general disappointment with manufacturer UIs, and not one specific to Samsung. Anyway, on to the gimmicks!

The gimmicks

Let's not fool ourselves, every successful matured platform around has its share of gimmicks, which we define as features that make you say "wow", but don't really add a lot as far as function or usability. If you're showing off what your phone can do, you'll probably use these "features", and they will be the same things that will get you to drop down money in a store, but they don't really help your day to day life all that much.

Apple has FaceTime and Siri, both of which seem cool, but either aren't used all that much (FaceTime) or have limited benefits when the feature works (Siri). Google brought in Face Unlock to be its gimmick/cool feature of Ice Cream Sandwich. HTC has its blinged out Sense UI. And with the Galaxy S III, Samsung jumped on the gimmick train full force, and showed its own hypocrisy a bit.

The trouble is that Samsung uses every chance it gets to put down Apple, and even takes shots at Apple followers, but the truth is that Samsung would love nothing more than to be Apple and have that kind of devoted following. And, while Samsung did come up with some novel and innovative ideas with the Galaxy S III, the first feature talked about was S Voice, which is the worst kind of gimmick, because it's really just trying to be better than the Apple version, which doesn't work all that well in the first place.

Think about it, when S Voice was shown off in the announcement, as well as in our hands-on demo, there was a noticeable delay before it either launched the camera app or gave the weather. This is Android we're talking about, not iOS. You don't need to ask for the weather, you just need to look at your weather widget. And, what is the point of launching an app with your voice if it is faster to simply tap the app icon? The choice is either to start the voice recognition service, then say "I want to take a picture," at which point there will be a delay while the app figures out what you want and launches the camera, or just hit the home button and tap your camera icon.

This is the big issue with Samsung's presentation of S Voice. There is value in it, especially in initiating searches, dictating messages, or perhaps playing a specific song or video (none of which is special to S Voice, since Android has this functionality built-in,) but because Samsung wanted to highlight the natural language addition, the marketing took a hit. S Voice adds value to the stock Android voice command option by adding more natural language support, but in showing off the product, Samsung chose to perform two action that would have been faster without voice command. It would have been far better to say "Play Somebody That I Used to Know", and show how Android gives you the choice to play that through any of the apps available on your device like Spotify, Music, YouTube, etc. That is something that is faster to do via voice, and shows the power of this system over that of the competition, since Siri doesn't yet have those hooks (though Apple has said they will eventually exist).

The new Nature UX is also essentially a gimmick. It may very well make the phone more enjoyable to use, and it may make for an overall pleasant experience, but there is no real function behind it, which makes it a gimmick. Keep in mind here that not all gimmicks are bad things. Gimmicks can be delightful, but the problem is that gimmicks strive for delight rather than usability. However, not all the announcements were bad. Samsung also came out with some solid ideas that we'd love to see expanded through the mobile ecosystem.


The good ideas

The biggest difference between a great idea and a gimmick is that gimmicks are designed so you notice it, while truly great ideas may make your experience better without you ever realizing it. And, that is what Samsung hit with the introduction of Smart Stay. This is a feature that we've all wanted, but never even knew it until now. It is terribly annoying to be reading something or watching something and having to keep reminding the device that you're there by nudging the screen, so it won't go to sleep. So, to have your device be able to know when you're looking and when you aren't and control the screen accordingly is potentially an amazing feature. Obviously, we need to see Smart Stay in practice, but given the facial recognition already built-in to Android 4.0, it seems likely that this feature should work as promised. Additionally, auto-tagging friends in pictures with easy sharing from the gallery is another very good idea built on Android's facial recognition. That is another feature we expect to see more in other devices.

Direct Call is another idea that has a lot of potential, or at least the idea behind it has a lot of potential. Having devices anticipate what you want to do will be a big part of the evolution of smartphones from here on, and a lot of that will be tied to device gestures. We've gotten about as much as we can from touch gestures, now it's about context and how you move your device. Direct Call lets you call the person you're messaging simply by lifting the phone to your ear (and we're hoping this works in various apps like Google Voice, Gmail, Messaging, etc.) HTC added this into Sense a while back by making the ringer volume change whether the phone was placed screen up or down. So, what about the phone automatically launching the camera app if you lift the device into a picture taking position (landscape orientation at eye level, or portrait orientation pointed at the sky (for the ubiquitous "cleavage angle" the ladies love)). Or, your phone could automatically wake up and update various content or launch an app when you pick it up for the first time in the morning. The potential is very intriguing.

Of course wireless charging is also a great idea, but we've been waiting for that, and would have been somewhat disappointed had it not been part of the phone.

Conclusion

Overall, the Samsung Galaxy S III looks like a solid addition to the Android ecosystem. The disappointments were really nothing more than hoping for more than was reasonable, the gimmicks still have their uses or can be ignored fairly easily, and the additions are solid enough that the overall experience should be pretty positive. We like the evolution of TouchWiz, even if it buries the evolution of Android, because at least Samsung is aiming for adding moments of delight to what has been a fairly bland, if candy coated experience. S Voice will have its uses, and its drawbacks, just like every voice command system right now. And, the good ideas are good enough that they can subtly make the device much nicer than you'd expect on first glance.

Verizon shows off changelist for Motorola DROID 3 update

The Motorola DROID 3 was the last DROID in the series to not have LTE connectivity. The handset is underrated with a physical QWERTY that is among the best ever to find its way on a handset and the unit does have dual-core power under the hood. Still, that doesn't mean that the solidly built device couldn't use an update every now and then and Verizon has posted on its website the changelist for the Motorola DROID 3 update currently being soak tested.

The 5.7.905.XT862 update comes in at 230MB and unlike the update for the Motorola DROID X2, this one has a long changelist. Included in the list is a Google security patch for added level of protection. A bug is fixed that used to turn the device on without user interaction. You can now avoid interruption when trying to access an app before storage media is fully mounted on the phone and improvements in power cycles should prevent the phone from rebooting constantly. Additionally, the DROID 3 will no longer lock up and reboot when connected to Bluetooth and HDMI.

Those with the Motorola DROID 3 know how hard it is to use the camera on the phone. Improvements in AutoFocus will help cut the shutter's response time and enhance the quality of pictures taken. The Wireless Alerting System will be aboard the device after the update. The firmware update also lets you use a wired headset without hearing a high pitched noise. For those who travel often, Plus Code dialing has been improved making it easier to dial international calls. Using Bluetooth, playback media can be heard and using the contact widget a call can be made to the appropriate person. When moving apps to the microSD card, shortcuts to the apps will remain, and after updating the contact database from the Messaging App, the Messaging UI will display the latest contact information.



The update will allow you to post and play videos on Facebook and purchased ringtones can now be downloaded, saved and used where appropriate. Contact photos will display properly in Google Voice and VZ Navigator 3D City is now pre-loaded. Finally, the update will fix a problem that required excessive data usage and continuous downloading for VZ Navigator 3D City downloads.

No, the Motorola DROID 3 will most likely not get Android 4.0, but it remains a solid performer and users are just happy to see the manufacturer continue to support it.

source: Verizon

Motorola CLIQ 2 finally gets gingerbread

While everyone remembers the Motorola DROID as being the handset that kicked off Androidmania, it was not the manufacturer's first Android model. That honor belongs to the Motorola CLIQ which was released almost a full month before the game-changing DROID was. The handset was launched with Android 1.5 while the Motorola DROID was the first to have Android 2.0 installed.

About 15 and a half months after the CLIQ was released, Motorola came back with a sequel having the inspired name of the Motorola CLIQ 2. With a much larger screen size (3.7 inches vs. the original's 3.1 inch display) equipped with higher resolution, the sequel still featured a side sliding QWERTY keyboard. The camera remained at 5MP although the sequel had a dual LED flash. The OG CLIQ featured a Qualcomm MSM7201 A 528MHz processor vs. a single-core 1GHz Snapdragon under the hood of the sequel. But perhaps the biggest change was with the OS. The Motorola CLIQ 2 had Froyo, or Android 2.2 running the show which not only was miles and miles away from Android 1.5, but it also allowed CLIQ 2 users to run Adobe Flash and store apps on a microSD card.

Now, Motorola CLIQ 2 owners are moving up the ladder. Android 4.0? Uh, no. But Android 2.3 is finally coming to the Motorola CLIQ 2 and offers improved cursor controls, better battery performance, number and symbol shortcuts and updated calendar options. You can check out the entire (and rather lengthy) changelist by clicking on the sourcelink.

There is some bad news. This is not an OTA update which means you will need a Windows powered PC, a micro USB cable and the Motorola Software Application. Clicking on the sourcelink will bring you to the instructions for downloading the update. And while it doesn't take owners of the Motorola CLIQ 2 all the way to Android 4.0, it should make it feel like a brand new phone once you've completed the installation.

source: Mototola via Phandroid

Samsung punished by Judge for failing to turn over source code in Apple patent suit

Apple's request for sanctions against Samsung have been granted by United States District Court Magistrate Judge Paul S. Grewal. The Judge is presiding over an Apple-Samsung patent infringement battle and received a motion from Apple back in March requesting that the sanctions be placed on the Korean based firm for failing to produce source code and other documents that it had been ordered by the court to turn over. Apple's concern is that the delays caused by Samsung's failure to produce source code and documents make it too time consuming to conduct analysis of Samsung's ever changing Android source code. That, in turn, makes Apple's claim of patent infringement against Samsung a "moving target".

Just two weeks ago, Samsung was fined by the court after the same Judge found Samsung to be in violation of a court order. The company failed to turn over documents it had that mentioned Apple's products. The Cupertino based tech titan was planning on using these documents to show that Samsung had infringed on Apple's designs. Judge Grewal is a bit more upset now after the failure of Samsung to hand over the important source code. The code was supposed to show how Samsung had worked around Apple's patent in designing certain aspects of its products, including the "overscroll bounce" that is protected by U.S. Patent No. 7,469,381. Turning over the code might have helped Samsung with its defense.



Apple's attorneys have told the Judge that it is now too late for them to use the source code and asked the court to ban Samsung from using the source code for its defense. In his sanctions order, the Judge said, "Samsung shall be precluded from offering any evidence of its design-around efforts for the '381, '891 and '163 patents, and shall not argue that the design-arounds are in any way distinct from those versions of code produced in accordance with the court's order. Samsung must instead rely solely on the versions of code that were produced on or before December 31, 2011."

Samsung just might have shot itself in the foot as the older code that it has to rely on now with this case, is more likely to infringe on Apple's patents than the newer code that it failed to produce to the court in a timely fashion.

source: FossPatents via AppleInsider

Nokia 808 PureView meets FCC, still not coming to the States

Being a member of the FCC gives you many privileges that the average U.S. citizen doesn't have. For example, the other day the Nokia 808 PureView stopped in and the Feds got a chance to spend some time with the device and its 41MP camera. Remember, thanks to the allergy that Americans have to Symbian powered handsets, the Nokia 808 PureView will not be sold in the States, at least not for now. So when the FCC committee members came home and told their wives that they took apart the 808 PureView and its 41MP shooter, we're sure that there was pride on their faces. Even the kids were excited, pleading with their Dad to talk to the class on the next career day.

In addition to seeing the Nokia 808 PureView and its 41MP camera in perfect working condition, the FCC also got to rip the phone apart. We're not sure if they were looking for Waldo or Carmen Sandiego, but the pictures reveal a handset that is scheduled to launch some time this quarter globally, if by globally you mean just about everywhere but the States. Don't be surprised about Nokia's decision here. Didn't your Mama warn you what would happen if you stopped playing with Symbian powered phones?



source: FCC via Engadget