JungleLarry
Well-known member
HahahahaI've played with both the Moto X and the Iphone 5 at the ATT Store. I know.
HahahahaI've played with both the Moto X and the Iphone 5 at the ATT Store. I know.
The bad. The notification vibration sounds terrible. It sounds like the phone is coming apart every time I get an email or message. It males the phone sound/seem cheap. I have had some issues with battery life that I am trying to track down (may be app related) and my battery life has not been as good as the GS4 or Note II. As I mentioned in another thread, I have had very high "Time Without a Signal" percentages -- as high as 46%. Every other phone has shawn 1 to 2 percent at most. I think the X is just measuring LTE connection because it has a signal whenever I look at it or try to use it. The screen really shows fingerprints and looks bad most of the time. As mentioned, I would prefer the screen to be 5 inches. It is just easier to read, type on and use.
I'm awaiting this phone for T-Mobile, coming from a Nexus 4, mainly because of the small form factor, mostly stock android and battery life, so hearing about your issues with battery life gives me pause. I hope that isn't normal behavior for the phone.
I'm awaiting this phone for T-Mobile, coming from a Nexus 4, mainly because of the small form factor, mostly stock android and battery life, so hearing about your issues with battery life gives me pause. I hope that isn't normal behavior for the phone.
i was told that too by someone in a store when i asked him why the need for all this processing power when we were convesing about cpus,etc and also part of a conversation of why people always told me android was glitchy, and that's how he explained it to me, which made sense. he said it wasn't until generally this year and then end of last that the processing power and other hardware was able to run androids without glitches and other problems.
The main issue with Android's performance is honestly quite complex and is really a combination of things rather than any 1 thing. A lot of it has to deal with Google's original design on Android though they have been working hard with each new release to fix the issues.
Prior to ICS/Jelly Bean all animations were done via the cpus though now they use the GPU (think Win XP vs Win 7), being that the cpu had to both process all of the app data as well as the GUI there was a performance hit until ICS/JB. Jelly Bean took this to a whole new level with Project Butter and made the GUI even smoother.
Another issue is the GUI of Android is mostly Java based and while there is a JIT (added in 2.2), it still is never going to be quite as fast as native code and there is a performance hit (though it does allow many of the apps to run on both ARM and x86). With each release Google seems to work on improving the JIT's performance, optimizing the garbage collector, etc... but there still is work to be done.
Another issue that was only just resolved in 4.3 is the lack of TRIM support....this would cause devices to start to slow down over time simply from the internal memory blocks being written over but never "cleared" after the data was deleted which means the next write to that block has to both delete and then write the data. There were alternative fixes on the Android Market aka LagFix but they require root. There have been benchmarks showing a 10-25% performance increase depending on what is being done with File System performance after TRIM has been run.
Finally the last "big" issue is that Android offers true multitasking, not partial like iOS. This though also means that there is many background processes running and taking up ram. With the more modern devices coming with 2GB of ram, the multitasking issue is starting to go away. Even though many of the apps themselves aren't that big, Android runs many background processes for apps you've opened (and sometimes ones you haven't) so when you hit a low memory situation, it has to clear out some apps before it can load the new app....again slowing things down.
So to be fair its been both a combination of hardware and software improvements over the past 1-2 years that are helping Android become better and better.
X should theoretically be in immune to this problem, It has some interesting stuff going on with file system read/write, giving it great performance and it does have trim functionalty that 4.3 has, and it looks like moto implemented trim on delete too.one of the reasons why moto x is smooth and snappy in performance. Read anandtech review of moto x.
wow, that was some kind of review! i didn't see what you were referring to, but i got lazy and tried to find it instead of reading every page. do you remember what section it might have been in?
here is the link AnandTech | Moto X Review
Thank you for this link. This was and is very educating on motos choices for doing things.
AnandTech | Moto X Review
This Is awesome to see how the moto is in the running with all quad core performances. Interesting how the extra cores in s4 bring down cpu frequency in first 2 cores lowering the ceiling on achievable speeds while the moto maintains a 1.7 reading because it's only using 2 cores.
Posted via Android Central App
Totally agree.Looks like pretty advanced engineering to me. It looks like the only thing they have left to work out is how to incorporate a 1080p display without a battery hit. I think both this and the HTC One are on equal grounds here. This has more interesting features and a more advanced read/write to flash memory but the One has the better screen and indoor camera quality. For me it would boil down to whether I wanted the features built into the X or the camera and display of the One.
Sent from my Nexus 7 using Tapatalk 4
Looks like pretty advanced engineering to me. It looks like the only thing they have left to work out is how to incorporate a 1080p display without a battery hit. I think both this and the HTC One are on equal grounds here. This has more interesting features and a more advanced read/write to flash memory but the One has the better screen and indoor camera quality. For me it would boil down to whether I wanted the features built into the X or the camera and display of the One.
Sent from my Nexus 7 using Tapatalk 4
For me, what the One needs to improve on is the size. I'm sure you can blame boomsound speakers for some of the extra bezel, but the One is wayyyy taller than the X with the screen. That's pretty laughable. Even the 4.3" One Mini is taller than the X. I think all companies need to start worrying more about the footprint of the phone more than keeping it super thin. Moto did this one right on the ergonomic side.
IMHO, no Android phone up until now has matched the smoothness and fluidity of the iPhone 5, or even the 4S. All manufacturers have done is throw specs into their phones, and hope that they work. Finally, Motorola has taken a page from the Apple book, and tried to match hardware and software, which makes a snappier phone and a great user experience. That is why an iPhone runs smoother, and usually faster, than most Android phones, a does it with a dual-core and 1GB of RAM. And still does it even after a year of service, which is something that no Android can claim. Again, this is IMO, but I have had many, many Androids and none have matched the iPhone for smoothness and fluidity.
AND the notification bar...something that is common on all Android phones.But to be fair, the X only has 4.4" viewable when you account for the onscreen buttons.
But to be fair, the X only has 4.4" viewable when you account for the onscreen buttons.