- Jun 25, 2004
- 5,530
- 141
- 106
I have been using a Galaxy S2 for the past two and a half years and have been pretty happy with it overall. Last week my Republic Wireless Moto X came in, and I decided to share my experience.
It might be easier to compare the camera images in my XDA post because Anandtech reformats linked images.
(Physical Appearance)
Physically, the Galaxy S2 and Moto X are almost identical in vertical and horizontal size. The Galaxy S2 is a hair wider, and not quite as long. The Moto X packs a 4.7” screen into approximately the same sized package as the Galaxy S2 which has a 4.3” screen - though only around 4.45” of the X’s screen is usable most of the time due to onscreen buttons. The Moto X is considerably thicker (the S2 is an incredibly thin phone) though its shape is very pleasant to hold. Thinner is not always better. I was also surprised by how noticeable an increase from 122g to 130g is in my hand – the X feels surprisingly heavier and denser.
The screens on these two devices are both Samsung-manufactured OLED panels. The S2 uses the same RGB pixel layout as the Moto X, but runs at a lower resolution of 800x480 (16:10) as opposed to the X’s 1280x720 (16:9). The Moto X’s panel is basically the same panel as is used in the Note 2, though with smaller pixels, making it one generation behind the S4 and one generation ahead of the S2. Neither has the RGBG (pentile) layout of the Galaxy S, S3 and S4, which is arguably a plus.
Auto brightness:
Max brightness:
Although it’s difficult to capture with a camera (my second S2, in fact), the Moto X’s screen is a little brighter at any given level of auto-brightness, has a higher max brightness, and a slightly lower minimum brightness than the S2. The saturation is higher on the Moto X than on the S2 though its pixels have faded in the past two and a half years (a common problem with OLED panels). Interestingly, the S2’s blue pixels have faded more quickly than its red and green pixels, which has changed its originally overly-blue image to a slightly red-green tinted image. I have to wonder if Samsung did this intentionally with their tuning, and wonder if the Moto X will suffer the same pixel fading as it ages. Also worth noting is Samsung’s inclusion of “screen modes” which control the saturation, which is absent in the Moto X. I have been using the “natural” setting on my S2 for a while now and I wish the Moto X had the option to decrease it’s saturation a little too. (the images above are at the default setting, not "natural")
Subjectively, the Moto X’s screen is an incredible improvement. Text is easier to read due to the higher resolution, and it’s just generally a more pleasant screen to look at. Not to say that the S2’s screen wasn’t acceptable, but displays have come a long way in a short time.
One thing that surprised me was the feeling of the vibrations in the S2 vs the Moto X. The X’s vibrations remind me a lot of the OG Droid (I have not owned a Motorola phone since that one), and are a lot rougher or lower-frequency than those of the S2. I wouldn’t say one is better than the other, but they definitely feel different, each being very representative of their manufacturers.
(UI and subjective performance)
The UI on the Moto X (as you probably already know) is very near stock android. Aesthetically, I like it better than TouchWiz on the S2 though functionally they are not very different. Nearly everything is organized exactly the same in the S2’s version of TW, the major differences being in the font choices and colorfulness of icons and menus. One thing notably lacking on the Moto X (with the stock launcher) is the ability to resize widgets and add or remove homepages.
Some of the app skinning done in TouchWiz is arguably an improvement over stock android, and most of the places where things are better there, Motorola has done the same. The most notable example is the camera UI. To be frank, I don’t like the UI Google has chosen for its camera, and am glad Motorola made their own.
The S2 is one of the first phones that I felt was largely “fast enough”. It has a dual core Exynos 4 SOC clocked at 1.2GHz and 1GB of RAM (~830MB usable). The Moto X has a dual core Snapdragon S4 Pro clocked at 1.7GHz and 2GB of RAM. The Snapdragon is considerably faster per clock.
I have been running my S2 rooted since day 1 and with recent 3rd-party kernels, the UI is almost perfectly smooth if there isn’t anything running in the background. There are occasionally dropped frames, and animations can be choppy if things are running in the background. Scrolling up and down webpages as they are loading in Chrome can also show dropped frames. 1GB of RAM is sufficient right now, but only just, and with the increasing requirements of apps I expect the S2 will be limited by its RAM sooner than its SOC. I would like to note that TouchWiz actually runs better than more recent versions of Cyanogenmod, so I have gone back to a modified 4.1.2 TW. The Moto X by contrast has a perfectly fluid UI out of the box, and almost nothing I have done has produced any dropped frames. Subjectively, the Moto X is noticeably smoother than the S2, especially when multitasking.
Game-wise, there is no game on the Android Market that won’t run perfectly smoothly on the S2 (today). It even handles DS emulation smoothly – you can’t tell the difference between a DS game running on the S2 vs the Moto X. So, despite the Moto X being several times faster on paper, games and emulators show no improvement (yet).
Worth mentioning is how much more quickly the Moto X tends to connect to and authenticate over WiFi.
(Features)
The Moto X has several features which I appreciate, but they aren’t make-or-break for me. Sadly, it lacks a few features which almost are.
The twist-to-activate-camera feature is neat, but it takes very little more time to hit the power button and turn it on from the lockscreen. I was surprised to learn (and other reviews hadn’t mentioned) that the motion works regardless of what you’re doing. The camera can be activated via the motion from within a call, while watching a video, or from within a game (unless, I assume, the game takes control of the motion sensors). This is situationally pretty useful.
Active display is a wonderful feature which I find as useful because I can wake my phone without hitting the power button as seeing if I have notifications without fully waking the phone.
Moto Connect is a fantastic seamless integration of texting into your desktop browser, and I wonder why others haven’t done this before. It’s one of the main reasons I used primarily Google Voice for texting before.
Assist’s Sleeping and Meeting modes are useful, but I had to disable Driving as I suspect it was hitting my battery pretty hard (tons of GPS related wakelocks) for what I got out of it. I’ll admit, I sometimes check my texts while driving, but I always wait until I’m in a low-risk area (ie stopped at a traffic light, or when there are no cars for some distance on the highway) and it would probably save more than a few lives if this feature existed on all android phones. I thought the custom SOC was supposed to allow these features without a significant battery hit, but it seems that’s not entirely true. I may revisit this feature later.
Audio effects – I turned this off almost right away. It’s nice to have a system-wide equalizer included but it’s not a very robust implementation.
I haven’t yet felt the need to use Moto Care, but it seems a very thoughtful feature to include for non-tech savvy users.
What is the Moto X missing that the Galaxy S2 has?
1. uSD card slot. On my phone I keep ~16GB of music, ~2GB of audiobooks, ~3GB of game ROMs (PSX games are large), ~1.5GB of system ROMs and backups (or at least I did on my S2), and may use half a GB for photos / backgrounds / other images at any given time. Add in 4GB of system files/apps and keeping at least 20% spare area to keep performance up, and 32GB is just about right for me - assuming that my usage patterns don't change and I don't need any more space than I'm already using in the next 2 years. The Moto X has only around 10.5GB of usable space free unless you get the developer edition (not available through Republic Wireless and probably not through contract either) which a serious, serious problem for me.
I'm not happy with the idea of paying an extra $30+ per month for higher data limit when the amount of storage I need to decrease my data usage to near zero is less than $30 up front. If I don't need to stream anything, I can easily get by with a 300MB cap. Republic Wireless is uncapped when you have their basic data plan, but Sprint’s 3G is pretty much too slow to stream music, much less videos, and coverage is not great. As for the arguments about how it could negatively affect build quality – keep in mind, the phone already has a sim card slot, and uSD cards are not any larger.
2. Removable battery. This one is actually less of an issue for me now as I bought an external battery pack. I can live without it, but this can be a problem for some users. One thing to note is that generally, most of the replaceable batteries that will fit a phone will be manufactured for only as long as the phone is, so if you’re looking to replace an old battery with a new one, most that you buy will probably be equally old, just less used. Still, it is a point of failure that can easily be replaced, which brings me to the next point…
3. No user replaceable parts. Over the two and a half years I owned my S2, I needed to replace the camera module and the charge port. It’s arguable that build quality of the S2 is to blame here, but it isn’t an invalid criticism of the Moto X that parts are not user-replaceable as they are on Samsung phones. Twice I would have needed to replace my phone or send it to the manufacturer for repairs. The total cost of parts was $12 and about 10 minutes to pull the phone apart because of this “feature”. I’m actually waiting on rooting my Moto X until the one-month warranty/return period is over as I’m concerned about part failures.
Despite how much I like the Moto X, I might not have chosen it had it not been for the incredible pricing through Republic Wireless. A uSD card is practically a requirement for me.
(Subjective Sound Quality)
Using my Beyerdynamic DT 880’s, I feel that the Moto X has better quality output, though I know basically nothing about the hardware involved. I think I could most accurately describe it as sounding like the difference between using a pocket amplifier and not. It’s easier to distinguish individual instruments and sounds, and the noise floor is a bit lower.
It might be easier to compare the camera images in my XDA post because Anandtech reformats linked images.
(Physical Appearance)
Physically, the Galaxy S2 and Moto X are almost identical in vertical and horizontal size. The Galaxy S2 is a hair wider, and not quite as long. The Moto X packs a 4.7” screen into approximately the same sized package as the Galaxy S2 which has a 4.3” screen - though only around 4.45” of the X’s screen is usable most of the time due to onscreen buttons. The Moto X is considerably thicker (the S2 is an incredibly thin phone) though its shape is very pleasant to hold. Thinner is not always better. I was also surprised by how noticeable an increase from 122g to 130g is in my hand – the X feels surprisingly heavier and denser.
The screens on these two devices are both Samsung-manufactured OLED panels. The S2 uses the same RGB pixel layout as the Moto X, but runs at a lower resolution of 800x480 (16:10) as opposed to the X’s 1280x720 (16:9). The Moto X’s panel is basically the same panel as is used in the Note 2, though with smaller pixels, making it one generation behind the S4 and one generation ahead of the S2. Neither has the RGBG (pentile) layout of the Galaxy S, S3 and S4, which is arguably a plus.
Auto brightness:
Max brightness:
Although it’s difficult to capture with a camera (my second S2, in fact), the Moto X’s screen is a little brighter at any given level of auto-brightness, has a higher max brightness, and a slightly lower minimum brightness than the S2. The saturation is higher on the Moto X than on the S2 though its pixels have faded in the past two and a half years (a common problem with OLED panels). Interestingly, the S2’s blue pixels have faded more quickly than its red and green pixels, which has changed its originally overly-blue image to a slightly red-green tinted image. I have to wonder if Samsung did this intentionally with their tuning, and wonder if the Moto X will suffer the same pixel fading as it ages. Also worth noting is Samsung’s inclusion of “screen modes” which control the saturation, which is absent in the Moto X. I have been using the “natural” setting on my S2 for a while now and I wish the Moto X had the option to decrease it’s saturation a little too. (the images above are at the default setting, not "natural")
Subjectively, the Moto X’s screen is an incredible improvement. Text is easier to read due to the higher resolution, and it’s just generally a more pleasant screen to look at. Not to say that the S2’s screen wasn’t acceptable, but displays have come a long way in a short time.
One thing that surprised me was the feeling of the vibrations in the S2 vs the Moto X. The X’s vibrations remind me a lot of the OG Droid (I have not owned a Motorola phone since that one), and are a lot rougher or lower-frequency than those of the S2. I wouldn’t say one is better than the other, but they definitely feel different, each being very representative of their manufacturers.
(UI and subjective performance)
The UI on the Moto X (as you probably already know) is very near stock android. Aesthetically, I like it better than TouchWiz on the S2 though functionally they are not very different. Nearly everything is organized exactly the same in the S2’s version of TW, the major differences being in the font choices and colorfulness of icons and menus. One thing notably lacking on the Moto X (with the stock launcher) is the ability to resize widgets and add or remove homepages.
Some of the app skinning done in TouchWiz is arguably an improvement over stock android, and most of the places where things are better there, Motorola has done the same. The most notable example is the camera UI. To be frank, I don’t like the UI Google has chosen for its camera, and am glad Motorola made their own.
The S2 is one of the first phones that I felt was largely “fast enough”. It has a dual core Exynos 4 SOC clocked at 1.2GHz and 1GB of RAM (~830MB usable). The Moto X has a dual core Snapdragon S4 Pro clocked at 1.7GHz and 2GB of RAM. The Snapdragon is considerably faster per clock.
I have been running my S2 rooted since day 1 and with recent 3rd-party kernels, the UI is almost perfectly smooth if there isn’t anything running in the background. There are occasionally dropped frames, and animations can be choppy if things are running in the background. Scrolling up and down webpages as they are loading in Chrome can also show dropped frames. 1GB of RAM is sufficient right now, but only just, and with the increasing requirements of apps I expect the S2 will be limited by its RAM sooner than its SOC. I would like to note that TouchWiz actually runs better than more recent versions of Cyanogenmod, so I have gone back to a modified 4.1.2 TW. The Moto X by contrast has a perfectly fluid UI out of the box, and almost nothing I have done has produced any dropped frames. Subjectively, the Moto X is noticeably smoother than the S2, especially when multitasking.
Game-wise, there is no game on the Android Market that won’t run perfectly smoothly on the S2 (today). It even handles DS emulation smoothly – you can’t tell the difference between a DS game running on the S2 vs the Moto X. So, despite the Moto X being several times faster on paper, games and emulators show no improvement (yet).
Worth mentioning is how much more quickly the Moto X tends to connect to and authenticate over WiFi.
(Features)
The Moto X has several features which I appreciate, but they aren’t make-or-break for me. Sadly, it lacks a few features which almost are.
The twist-to-activate-camera feature is neat, but it takes very little more time to hit the power button and turn it on from the lockscreen. I was surprised to learn (and other reviews hadn’t mentioned) that the motion works regardless of what you’re doing. The camera can be activated via the motion from within a call, while watching a video, or from within a game (unless, I assume, the game takes control of the motion sensors). This is situationally pretty useful.
Active display is a wonderful feature which I find as useful because I can wake my phone without hitting the power button as seeing if I have notifications without fully waking the phone.
Moto Connect is a fantastic seamless integration of texting into your desktop browser, and I wonder why others haven’t done this before. It’s one of the main reasons I used primarily Google Voice for texting before.
Assist’s Sleeping and Meeting modes are useful, but I had to disable Driving as I suspect it was hitting my battery pretty hard (tons of GPS related wakelocks) for what I got out of it. I’ll admit, I sometimes check my texts while driving, but I always wait until I’m in a low-risk area (ie stopped at a traffic light, or when there are no cars for some distance on the highway) and it would probably save more than a few lives if this feature existed on all android phones. I thought the custom SOC was supposed to allow these features without a significant battery hit, but it seems that’s not entirely true. I may revisit this feature later.
Audio effects – I turned this off almost right away. It’s nice to have a system-wide equalizer included but it’s not a very robust implementation.
I haven’t yet felt the need to use Moto Care, but it seems a very thoughtful feature to include for non-tech savvy users.
What is the Moto X missing that the Galaxy S2 has?
1. uSD card slot. On my phone I keep ~16GB of music, ~2GB of audiobooks, ~3GB of game ROMs (PSX games are large), ~1.5GB of system ROMs and backups (or at least I did on my S2), and may use half a GB for photos / backgrounds / other images at any given time. Add in 4GB of system files/apps and keeping at least 20% spare area to keep performance up, and 32GB is just about right for me - assuming that my usage patterns don't change and I don't need any more space than I'm already using in the next 2 years. The Moto X has only around 10.5GB of usable space free unless you get the developer edition (not available through Republic Wireless and probably not through contract either) which a serious, serious problem for me.
I'm not happy with the idea of paying an extra $30+ per month for higher data limit when the amount of storage I need to decrease my data usage to near zero is less than $30 up front. If I don't need to stream anything, I can easily get by with a 300MB cap. Republic Wireless is uncapped when you have their basic data plan, but Sprint’s 3G is pretty much too slow to stream music, much less videos, and coverage is not great. As for the arguments about how it could negatively affect build quality – keep in mind, the phone already has a sim card slot, and uSD cards are not any larger.
2. Removable battery. This one is actually less of an issue for me now as I bought an external battery pack. I can live without it, but this can be a problem for some users. One thing to note is that generally, most of the replaceable batteries that will fit a phone will be manufactured for only as long as the phone is, so if you’re looking to replace an old battery with a new one, most that you buy will probably be equally old, just less used. Still, it is a point of failure that can easily be replaced, which brings me to the next point…
3. No user replaceable parts. Over the two and a half years I owned my S2, I needed to replace the camera module and the charge port. It’s arguable that build quality of the S2 is to blame here, but it isn’t an invalid criticism of the Moto X that parts are not user-replaceable as they are on Samsung phones. Twice I would have needed to replace my phone or send it to the manufacturer for repairs. The total cost of parts was $12 and about 10 minutes to pull the phone apart because of this “feature”. I’m actually waiting on rooting my Moto X until the one-month warranty/return period is over as I’m concerned about part failures.
Despite how much I like the Moto X, I might not have chosen it had it not been for the incredible pricing through Republic Wireless. A uSD card is practically a requirement for me.
(Subjective Sound Quality)
Using my Beyerdynamic DT 880’s, I feel that the Moto X has better quality output, though I know basically nothing about the hardware involved. I think I could most accurately describe it as sounding like the difference between using a pocket amplifier and not. It’s easier to distinguish individual instruments and sounds, and the noise floor is a bit lower.
Last edited:
Facebook
Twitter