Samsung Epic 4G Review: The Fastest Android Phone
by Anand Lal Shimpi on September 6, 2010 5:28 PM EST- Posted in
- Smartphones
- Samsung
- Epic 4G
- Gadgets
- Mobile
The Keyboards
“Wait, this is Swype?”
I read about Swype in Brian’s Droid X review, but Motorola shipped the keyboard disabled by default so I figured it’d be one of those things with a steep enough learning curve to dissuade the impatient. When I first started using the keyboard on the Epic 4G I fell in love. It was by far my favorite Android keyboard. It wasn’t until I finished typing a word and noticed a little info button blinking in the lower left corner of the keyboard that I realized I was using Swype.
Samsung ships the Epic 4G with Swype installed and enabled by default, and I totally get why. The keyboard layout is simply perfect for Android. You get a very simple keyboard with a layout that makes sense, I have absolutely no complaints about it. The keys are both big and well spaced enough on the 4” touchscreen to make typing quickly a non-issue. There’s no And if you want an alternate input form that requires fewer taps, there’s always Swype input.
The virtual keyboard rocks but what Swype lets you do is input characters an alternative way: by tracing a line over the letters of the word you’re trying to type. For example, if I wanted to Swype out the world “them” I’d place my finger over the letter ‘t’ on the keyboard, then draw a line down to h, diagonally up to e, and back down and to the right over to m. When I lift my finger there’d be a slight pause, and Swype would insert the word “them”. There are tricks to do more complicated things: make a little circle around a letter you need to enter twice, or extend a line up above the keyboard to create a capital letter. If Swype is unsure of what you’re typing it’ll give you a list of options to choose from, and manually typing in words adds them to the dictionary.
Swyping "hello"
I personally prefer the traditional typing method of text input but I can see how, with practice, you could be just as fast with Swype.
While Swyping you have to pay more attention to spelling. The iOS style of text input is pretty much tap and forget, if you misspell or mistype something the OS autocorrects. But with Swype, you actually need to know how to spell the words you’re trying to type and know where all of the keys are on the keyboard. I didn’t feel my mental CPU utilization hit 100% as Brian described in his first encounter, but I felt like I was in a constant spelling/key location bee. It just takes some getting used to but I actually liked Swyping when I didn’t feel like typing with two hands.
The downside to using Swype as a normal virtual keyboard is the optional autocorrection (you have to enable it under Swype settings). Instead of getting suggestions inline, you get a distracting popup. Thankfully you can easily switch back to the default Android keyboard just by holding down on any text input box and changing the input method.
The physical keyboard is a nice addition, I definitely appreciate it being there although most of the time I used the virtual keyboard. I’d probably prefer the other Galaxy S variants that lack the physical keyboard, but if you need tactile feedback the Epic 4G’s hybrid model works.
Facebook
Twitter
RSS
93 Comments
View All Comments
medi01 - Tuesday, September 7, 2010 - link
Java's JIT could create code that is faster than C/C++. Because unlike C++ compiler, it also has runtime info about executables, it could know for sure, which of the if branches is more likely to be true, for instance.The only part of Java that was much slower than C++ was (and I think still is) sin/cos related functions. Since Sun had to guarantee "runs anywhere" with the exactly the same results, instead of using CPU's features they "manually" calculate it.
Voo - Tuesday, September 7, 2010 - link
Well java WAS slow - around ten years ago, but people have already made up their mind, it's hard to get new ideas into some heads. Though the lack of a JIT in dalvik hampered performance, but that's hardly something where you can blame the language for..Ah, just like all those people who still believe that manual memory managment is inherently faster than GC..
medi01 - Tuesday, September 7, 2010 - link
Java is not inherently slower than C++, but it does need more memory.The problem with Androids up to 2.2 was Dalvik VM that had no JIT.
designerfx - Tuesday, September 7, 2010 - link
what a brilliant troll, or accidental. I'm not sure, but plenty of debunked this.What really brings down the entire samsung line of phones is that the GPS is horrible. I have one myself, and have the same issue on the vibrant as on the epic. Samsung really screwed the GPS up bigtime.
lwatcdr - Tuesday, September 7, 2010 - link
Well when faced with such a brilliant technical argument like "but Java sucks. Big time" what can one say.http://www.cnn.com/2004/TECH/space/01/16/space.mar...
Is an article from back in 2004 about how those idiots at NASA used Java to control the Spirit rover on Mars.
If only they had you available to show them how to do right.
Man I get sick of this crap. I heard the same thing way back when. People complaining when programmers used high level languages to write programs instead of assembly.
The thing is that it was all silliness just as it is now.
What really counts isn't the language but the programmer using it.
Android's speed issues tend to because by.
1. Not using the GPU for the UI
2. Using multitasking from the start.
IOS has only just now gotten official multitasking and even that is limited.
But really just drop the
Iksy - Tuesday, September 7, 2010 - link
Umm... to be clear, this is just the user interface used on Earth, which is something Java does well. The rovers themseves are controlled using VxWorks RTOS. VxWorks itself is written in C or C++ I believe.Ethaniel - Tuesday, September 7, 2010 - link
Well, it's not the kind of technical argument everyone would like, but it gets to the point. Anand reviewed like half a dozen of Android phones, all with the same problem. So, or the companies are making exactly the same mistake with each and every model they launch, or Java is to blame. And no, I'm not trolling because I do want to Android to succeed. A troll is based on hate, and it usually doesn't check back the thread he/she started. And you haven't seen a single insult in this thread, right? ;)ktwebb - Monday, September 6, 2010 - link
Sounds like an IPhone Fanboy that is trying his best to be subjective. Samsung actually did not get it right performance wise. They use an antiquated and slow file system. For a pleasurable UI experience on Android, the N1 is still king, especially on 2.2. The only way the samsung galaxy variants fly is with root access and ext2, 3 or 4 fixes. there are GPS fixes as well however where Samsung let down actually is in the UI with Touchwiz and their ridiculous homage to Apple. No wonder this twit liked it. Android people IMMEDIATELY change the launcher. Anyway, the Hardware on the Galaxy S is excellent. Samsung did their best to eff it up and only with tweaks and root level access is it a really strong phone. Google and Androids main problem is OS sprawl and fragmentation. They get that cleaned up and the IPhone 4 is a distant second mobile OS. Right now, with the clear advantages Android phones have, specifically customization and an open source community among others, it's essentially a wash. It's about what you prefer and are comfortable with. I'm an Android guy because I like to make my phone do what I want it to, not what Jobs wants my phone to be.StealthX32 - Monday, September 6, 2010 - link
ktwebb, I don't think Anand reviewed it w/ the ext2 FS hack/fix (whatever you want to call it). The UI speed is fine from the factory; it's much better than the EVO 4G (even with Froyo) and on par w/ the N1, just not as good as it *could* be once you root it and fix the filesystem.ktwebb - Tuesday, September 7, 2010 - link
N1 Froyo is faster than stock Galaxy S Variants. And yeah, he didn't review with hacks and I certainly understand why he wouldn't. Shouldn't need them. But that is a Samsung issue, not Android. Samsung has the potential for a very good handset with the Galaxy S. They are trying their best to eff it up though. I haven't played with the EVO but had android phones since the G1 inception. The N1 was the best UI experience after Froyo was pushed. And far better than any IPHone I've used, although my experience with 4 is limited.