Nexus 5 With Android 4.4 and Snapdragon 800 Challenges Apple A7 In Benchmarks 310
MojoKid writes "One of the hallmark features of Google's Nexus 5 flagship smartphone by LG isn't its bodaciously big 5-inch HD display, its 8MP camera, or its "OK Google" voice commands. That has all been done before. What does stand out about the Nexus 5 is Google's new Android 4.4 Kit Kat OS and LG's SoC (System on Chip) processor of choice, namely Qualcomm's Snapdragon 800 quad-core. Qualcomm is known for licensing ARM core technology and making it their own; and Qualcomm's latest Krait 400 quad-core along with the Adreno 330 GPU that comprise the Snapdragon 800, is a powerful beast. Google also has taken the scalpel to Kit Kat in all the right places, whittling down the overall footprint of the OS, so it's more efficient on lower-end devices and also offers faster multitasking. Specifically memory usage has been optimized in a number of areas. Couple these OS tweaks with Qualcomm's Snapdragon 800 and you end up with a smartphone that hugs the corners and lights 'em up on the straights. Putting the Nexus 5 through its paces, it turns out preliminary figures are promising. In fact, the Nexus 5 actually was able to surpass the iPhone 5s with Apple's 64-bit A7 processor in a few tests and goes toe to toe with it in gaming and graphics." Ars Technica has a similarly positive view of the hardware aspects of the phone, dinging it slightly for its camera but otherwise finding little to fault.
This is not a fair comparison (Score:5, Insightful)
Re: (Score:2)
Re: (Score:2)
Re:This is not a fair comparison (Score:4, Insightful)
Re: (Score:2)
Because we all know that the only people buying iPhones are original iPhone owners, right? Lame excuses are lame.
Breathtaking Ignorance (Score:3, Insightful)
The original iPhone caught on because it could play DRM iTunes.
You know, I don't think I've ever seen as horribly misguided a reason for the adoption of the iPhone as that one.
By your logic, the Motorola ROKR would have been a smash hit.
Re: (Score:3)
Re:This is not a fair comparison (Score:5)
Not trolling. Pointing out that vast numbers of people buy the iPhone despite it costing 2x as much. And this is despite the fact that most people are cheap - hence VHS winning against Betamax, Hyundai being way more popular than BMW, etc. It's also why most android handsets are not Nexus 5s or Galaxy 4s.
There are reasons for people buying iPhones despite all this. Chief amongst them is that the average Joe DOES NOT CARE about what the numbers are with synthetic benchmarks, number of pixels on screen, etc. They care about how well a device performance the functions they want it to do. Despite what many in the slashdot crowd may think, things like look and feel, UI consistency, battery life and integration with other devices and services is important.
The raw numbers are pretty irrelevant for everybody outside a very small subset of the population. For so many people to be buying iphones despite being "2x the price", there must be something they value in the device, otherwise they wouldn't be buying it.
Re:This is not a fair comparison (Score:5, Insightful)
Re:This is not a fair comparison (Score:5, Insightful)
The most common reason I usually get from non-technical people on why they want or why they purchased an iPhone (or iPad) was because they are 'cool' or 'trendy'. None of them has been able to tell me why or what features it has or does better than any of its competitors. Simply put, they didn't give a damn about how well their device functions when they use it, just the image they can reflect or inherit by owning one.
Re:This is not a fair comparison (Score:4, Interesting)
Re:This is not a fair comparison (Score:4, Informative)
I have lots of iPhone owning friends who switching to Android. Sometimes it was simply because they saw they could have the same functionality for half the price, or because they wanted a bigger screen, or just didn't like Apple's policies and software.
Anecdotes are worthless though, so let's look at the stats. Android is 80% of the market and on an upward trend. iOS is about 14% and falling. Source: https://en.wikipedia.org/wiki/File:World_Wide_Smartphone_Sales_Share.png [wikipedia.org]
Re: (Score:3)
It's a question of marketing. Samsung and Apple spend by far the most and have the most brand recognition, and unsurprisingly sell the best as well. Google doesn't do much mainstream advertising of its hardware, which is a shame because people would buy it in droves if they knew they could get something as good or better than a Galaxy S/iPhone for half the price.
It's only anecdotal evidence but I have seen people make this realization. The first time was when Apple sued Samsung over the infamous rounded cor
Re:This is not a fair comparison (Score:5, Interesting)
It kind of is. Of course, this excludes the fact that Android Apps are actually portable (unlike iPhone apps), and ultimately, when Google implements ART instead of Dalvik, Android will be significantly more competitive in performance (these benchmarks don't test the hardware exclusively, but the software environment also).
We can also install other Android builds easily on the Nexus phones, and so are able to do things, which are impossible on Apple (without risking completely messing up the phone on upgrades, such as screen recording).
Long term, Android is a better solution, and is is a more open environment, is less hostile to develop for, and I've found that my Nexus 5 is so snappy anyway, that the speed is irrelevent at this time. And yes, I have 3 other people in the office who are iPhone fans and my Nexus 5 has helped convert 2 of them, who are sick of all the small annoyances by Apple, such as getting cut by the broken glass backing of their iPhone (and the fact that on HSDPA/Wifi iPads for a very long time, we found they kept prioritising the HSDPA, making it painful for automation).
The Edge (Score:2, Offtopic)
Android Apps are actually portable (unlike iPhone apps)
Given the screen sizes of modern Android phones I'd say iPhone apps are actually quite a lot more portable. :-)
less hostile to develop for
Because good tooling is inherently bad for your health, just like using hammers is far inferior to the strength-building task of pounding in nails with railroad ties.
Re:This is not a fair comparison (Score:5, Interesting)
I think I'm qualified to comment on this. I've been an iOS developer since 2008. My company makes iOS and Android applications. I used flagship Android phones from 2008-2012 before switching to the iPhone. So I've had a lot of experience with both platforms from both the user and developer sides.
I think Android phones are terrible in comparison to iPhones. The reason why I started out with Android phones was for the reasons you outline - more open, and more flexible. I quickly discovered that wasn't all it was cracked up to be. The reason why I stayed with Android for so long was that a) I was holding out hope that it would be better in the long run and b) I wanted a hardware keyboard.
Open: Android is "open" in the "open cathedral" sense. It's very difficult to just jump in, make a few alterations, and see the changes running on your device. Practically speaking, it's not developed in an open sense in the same way most open source projects are. You could write a book about the implications this has and how it undermines the benefits open source normally provides.
Less hostile to develop for: not a chance. Yes, Apple have the ultimate say-so on what's allowed on the App Store. Yes, that's a big deal. But with Android, you have to contend with thousands of different models, each with their own shitty customisations that break things. We deployed an application last week for Android. It was finished weeks beforehand for iOS. Despite only having to target three recent Android tablets (it was an in-house project), each tablet was broken in different ways. iOS development is a breeze by comparison.
The problem with producing applications for the iPhone is Apple's policies. That's not a development obstacle, that's a policy issue. As we are a digital agency, all this really means for us is that we can say "Apple won't allow that" to clients when they ask for us to do something that Apple won't allow. And you know what? 99% of the time, it's when the client is asking for us to do something user-hostile.
The problem with producing applications for Android is development. The client asks for the feature, there's no intrinsic reason why it can't be done, but in practice you find that what should work and what does work on various devices differs radically.
Then there's the upgrade issue. I've done a lot of web development. Android is the Internet Explorer 6 of the mobile world. Masses of people don't upgrade, and more than a quarter of Android users are still on Gingerbread, released almost three years ago [android.com]. It takes less than a year for about 95% of iOS users to upgrade to the latest version.
This isn't just a developer problem, it's a user problem as well. When I bought my last Android phone, it was a flagship Sony phone shipped with 2.3 that they had committed to upgrading to 4.0. That's the only reason I gave in and stayed with Android. The promise that I might actually stay up to date for once. Sure enough, they broke that promise. But they dragged it out for a year saying that they would do it. Meanwhile, the version of Android I was stuck on had a bug that rendered my SIP phone line useless.
You lose features too. Remember when OTA upgrades were an advantage over iOS? The year before iOS added that feature, I got an Android upgrade that took that feature away. It was a shitty vendor customisation. I had to use a buggy desktop application that crashed my computer to upgrade Android. When I switched vendors? Same thing, but with a completely different buggy desktop application.
Android's a mess. It was a mess for the fours years I was using it, with every single handset I tried, as I was hoping in vain for it to get better. It never got better, in fact the problems with the platform became more numerous over time. It's "openness" is an illusion and is not going to fix the problems it faces.
I disli
Re:This is not a fair comparison (Score:4, Insightful)
Open: Android is "open" in the "open cathedral" sense. It's very difficult to just jump in, make a few alterations, and see the changes running on your device.
Wait, are you an app developer or an OS developer? Most app developers don't try to patch the OS. At least on Android you can submit patches, on iOS there is no way to do that. AOSP isn't hard to interact with, compared to say the Linux kernel or BSD.
Yes, Apple have the ultimate say-so on what's allowed on the App Store. Yes, that's a big deal.
Apple can make you waste vast amount of money developing something only for it to be blocked, and then copied by Apple themselves. That's more than a big deal. It's hard to get projects approved when managers see this happening.
But with Android, you have to contend with thousands of different models, each with their own shitty customisations that break things.
Only if you are a terrible programmer. Like most operating systems Android runs on multiple platforms and offers stable APIs to interact with that hardware. Just like you wouldn't design your Windows or Linux app to run at 800x600 and then get upset when people find it looks crap on their 1920x1200 monitor you should not be developing Android apps that are tailored to specific hardware.
Can you provide any concrete examples of standard Android API functions that are broken on popular Android devices? The worst I have seen is some flaky Bluetooth drivers, but those are down to the phone manufacturer in the same way you wouldn't call Windows broken because Dell ship broken drivers with some of their computers.
99% of the time, it's when the client is asking for us to do something user-hostile.
You mean like develop an alternative HTML rendering engine, or set up their own app/book/music/video store, or write a better SMS messaging system, or port their keyboard from Android, or some nefarious scheme like that?
Masses of people don't upgrade, and more than a quarter of Android users are still on Gingerbread, released almost three years ago.
31% of desktops are still running Windows XP, which was released in 2002. Of course that doesn't tell the whole story. .NET 4 is available for Windows XP, just like how many of the newer features in Android are available via non-OS updates that everyone gets via Play.
This really isn't the big issue crap programmers make it out to be. The API is stable, it's easy to deal with the differences and if a feature isn't available in Gingerbread there probably isn't any point trying to hack around it because devices of that age won't support it anyway. Can you point to any specific functions that have caused you problems, or is this just a general rant?
It takes less than a year for about 95% of iOS users to upgrade to the latest version.
Yes, and now you get complaints that your app is dog slow because the OS runs like a dog on older hardware, but users were not clever enough to block the update and can't downgrade.
It was a shitty vendor customisation.
Simple solution, don't buy from shitty vendors. Really, your argument is that once you bought a gas hob cooker and it was awful, leaked gas and eventually exploded burning your house down, therefore all gas hob cookers are shit and electric induction is the only way to go.
I dislike the controlling attitude of Apple and I dislike how much power they have in the mobile market.
No, you love it. You want your hand held. You want everyone to have a practically forced OS update with no downgrades, even if it makes their phone terribly slow. You want strictly controlled hardware and no choice about it so that you don't have to use your brain when writing apps.
Re:This is not a fair comparison (Score:5, Informative)
I'm not talking about the technical difficulty in writing a patch. I'm talking about the difficulty in applying a patch in practical terms. If I want to, say, modify my Xperia Pro so that a particular application that is useless to me isn't forcibly bundled, it's far more difficult than it should be.
I deal with people who commission apps on a regular basis. Unless the entire concept of an application is forbidden by Apple (e.g. porn), it's never been a deal breaker.
Which means nothing when vendors customise the implementations of those APIs and break them. It's all very well saying that, say, the API to draw a control on screen is the same across all devices, but if one device draws the control and another doesn't bother, that's kind of a problem.
I don't remember the full details, but the most egregious problem we had was that radio buttons simply weren't showing up on one device. At all. On another device, the rendering was completely fucked in some way, something like being a tenth of the size they should be or something. The code was right, and the application worked just fine on most of our test devices. But on some, they simply didn't work right due to vendor customisations.
Let's be straight here: I'm describing what Apple's policies mean for us in practice, and I'm reporting what clients actually ask us to do. You are scraping everything you can think of that Apple has ever rejected together. I'm sure there are lots of business plans that have fallen by the wayside in the five years Apple have been running the App Store. But that doesn't mean that they are a significant percentage of the apps people actually want to create.
No client has ever asked us to develop an alternative HTML rendering engine. Why would they? Besides, Apple don't have a problem with an alternative HTML rendering engine.
No client has ever asked us to set up their own app store. There are book stores on the App Store already, there's no rule against having a book/music/video store.
Alternative SMS messaging systems aren't against Apple's rules. I've got one on my phone right now.
No client has ever asked us to replace part of the system like a keyboard. If you have an application that needs a custom keyboard, you can implement one for your application, but you can't replace the keyboard in other people's applications.
When I say that the things clients ask us to do are things that are user-hostile, I'm talking about things like hookin
Re:This is not a fair comparison (Score:4, Insightful)
If I want to, say, modify my Xperia Pro so that a particular application that is useless to me isn't forcibly bundled, it's far more difficult than it should be.
That has nothing to do with Android and everything to do with Sony not wanting you to modify their proprietary ROM images. Also, how is it any worse than iOS which provides no mechanism at all?
Which means nothing when vendors customise the implementations of those APIs and break them.
Can you point to a specific example of a vendor doing this? I don't know of any. In fact one of the requirements of shipping a device with "Android" on it (as opposed to some custom OS that can't be called "Android", like the Kindle Fire OS) is that you don't break the standard APIs. There wouldn't really be any point doing that anyway as you would just get complains that apps don't work on your phone.
On another device, the rendering was completely fucked in some way, something like being a tenth of the size they should be or something.
Definitely sounds like a problem with your code, The Android Compatibility Test Suite checks for things like incorrect rendering settings when using the standard APIs, and vendors are required to use it if they want to use the Android trademark. Otherwise it's not Android, it's their own concoction.
No, not everyone gets via Play. You're confusing Play with Android. You don't have to license Play to deploy Android.
99% of Android devices have Play. Those that don't are almost all locked down by the manufacturer so you can't install any 3rd party apps other than the ones on their own market anyway, so are irrelevant to you.
You are repeatedly insinuating that we are crap developers simply because I am pointing out problems with Android.
No, I'm insinuating you are crap developers because you think there are problems with Android when in fact they are problems with your code or it wasn't even Android you were running on. You might want to think about that.
What are the non-shitty Android vendors? Because I was buying flagship phones with good reviews from mainstream vendors like Sony.
Sony are kinda shitty, especially with updates. They have tried to do better lately, but it remains to be seen if they have really made progress.
Obviously Google's devices are the best if you have a boner for running the latest version. Being a developer those would be the ones to go for. If you can stand to wait a few months for point releases Samsung are pretty good too.
Which Google phone did you have? What are you claiming was wrong with it?
Once you stop arguing against what I am saying, and put words in my mouth that are the opposite of what I believe, there really isn't much discussion to be had.
I was pointing out that you say you don't like Apple's policies, but prior to that complained about all the things you think are wrong with Android that stem from not having those policies. Devices don't always run the latest version of the OS because Google doesn't force vendors to release it for all current models and then ban downgrades. You complain about hardware variations because Google doesn't mandate one hardware platform with no variations. You seem to be saying that everything you "hate" about Apple's control over iOS is what makes it superior to Android, and that you think it is a good thing.
Re:This is not a fair comparison (Score:4, Informative)
Portable to what exactly?
Computers for starters.. Long term, we can run Android apps on Intel computers at full speed. On Apple, that won't be possible without an emulator, recompile, or switching the computer to ARM.
Ah yes, the classic Fandroid response of "Just around the corner it's gonna get better!!!"
Apple's program execution is nothing special. ART eliminates the disadvantages of using portable code, and allows the execution system to be far more flexible than Apple's. Android is using a slower system at the moment, but, better solutions do take more effort (one giant leap for mankind).
99% of Android users don't install other ROMs on their phone.
Where'd you get that figure? Anyone who purchased the humble bundles did. Part of the Apple Store's intention is to actively block competitors. That is even dodgier when you consider that Apple has stolen products in the past (which, after doing so, they will be competing against you). Also, if the hacker community wasn't there, we would have no good way to make videos of the product we developed for iPhone (we tried a video camera, it was terrible).
That to get any visibility you have to go through Google Play which has many the same terms as the Apple App Store.
Humble bundle gets plenty of visibility, and its a separate system. Also,if you spend 2 months developing software, you WILL be able to run it on the platform ultimately. On the Apple App store, you basically need to discard or Cydia the software if it isn't approved.
Finally, in 2009, it was estimated that Cydia was installed by 10% of the iPhone userbase (could be biased, from the Cydia website). And so, their app's obviously do have PLENTY of visibility on iPhone. The fact though that Cydia constantly breaks though is "hostile" towards unapproved apps. It shouldn't be necessary.
You can't afford $99? For any decent programmer that's not even 3 hours of pay.
That's $99 without any guarantee you will ever be able to sell the software you are developing on another iPhone (unless you go to Cydia). That sounds fantastic! There are so many developers on Cydia, who have developed great Apps, that Apple has screwed. I'm sure many Cydia developers LOVE Apple as much as you do.
Then maybe they should have gotten their phone replaced or put it in a case? How is it Apple's fault that someone drops their phone and is dumb enough to cut themselves on the glass?
Why is it an airplane's company fault if a pilot accidentally hits the wrong button causing the plane to crash? In the Airplane industry, they call this "Human Factors". The glass backing is an inexcusably poor design. The guy who I saw was cut, was just picking up his dropped phone . Basically, if you drop it on its back, it is designed to shatter, and if you are lucky, there are sharp glass fragments on the ground for other people to step on. Apple must have known that making the back out of glass (instead of Plastic or other materials), but instead, they decided to use an extremely fragile material (obviously weighing up whether the Apple Fanbase would care or not), and they ignored human factors in the process of designing the phone (all for the interest of making a good looking phone).
Re: (Score:2)
Well what are we comparing here price or performance?
Re: (Score:2, Funny)
Re: (Score:2)
Re:This is not a fair comparison (Score:5, Insightful)
No. you are stupid for basing your decisions on factors that don't affect your usage of the device. All that matters is how fast it brings up web pages, runs apps, etc., battery life, size and other factors such as features the OS and ecosystem provides. The clock rate of the processor is not relevant to the user.
Re: (Score:2)
Re:This is not a fair comparison (Score:5, Informative)
Re:This is not a fair comparison (Score:5, Insightful)
Now, if double cores and double the MHz give the Nexus 5 less battery life than the iPhone, then you have a leg to stand on.
Re: (Score:2)
And here I thought that the big thing about using 64-bit was to be able to access more RAM in the future. Since we are rapidly approaching the point where phones will have more than 4GB of RAM, I don't really see your point there. A quad-core does use more power than a dual-core, which is a good advantage in mobile. I think Apple has the right balance in the hardware (screen included) except the outrageous prices.
Me, I'm perfectly happy with a ZTE V965 and its very fast for what I need Mediatek 6589. I thin
Re:This is not a fair comparison (Score:5, Insightful)
You've got a Quad-Core ARM running at twice their Ghz and you barely post benchmarks ahead of a Dual-Core A7, you know you're stupid for buying one.
Stupid for buying a faster phone at half the price? You have a strange concept of stupid :-)
Re: (Score:2)
Re: (Score:3)
I don't agree with Google's octopus policies regarding privacy but you are very right about the Nexus 5. It has single-handedly managed to make any prospective iPhone buyer look like a complete fool.
Re:This is not a fair comparison (Score:5, Insightful)
Quad core doesn't help you on single-threaded, lightly-threaded, or GPU benchmarks, which is most of the benchmarks that I saw in the article. That means you can't say that Krait sucks because it has four cores and barely beats a dual core, since the four cores aren't being utilized. The conclusion you can draw is that a quad core CPU isn't necessary for a good user experience on a phone.
And needing a faster clock to reach the same performance levels isn't a meaningful metric either, at least not in a phone. In a phone that is power-constrained, the metric is performance per watt. If both CPUs burn the same power and give the same performance, they're basically equivalent. How each chooses to provide that performance is immaterial in a phone which is a power-constrained environment. Maybe the Apple CPU has some performance headroom at higher power budgets if it could run at a faster frequency (thus providing higher perf at the same freq as the Krait core), but that doesn't help you if it has to run throttled at all times so as to not blow through the phone's battery life and/or burn your pants.
Re: (Score:3)
This is not a fair comparison, the iPhone is twice the price.
You've got a Quad-Core ARM running at twice their Ghz and you barely post benchmarks ahead of a Dual-Core A7, you know you're stupid for buying one.
So, what you are saying is that the Nexus 5 is faster, but it needed twice as many higher clock speed processors, which is bad because it costs half as much or is it because it has a higher resolution display. And now that the iPhone doesn't have the highest resolution display, that's unimportant? Buying one of the fastest phones, that has a great display, has stock Android OS, and is cheap is stupid??? I do not think that word means what you think it means.
Re:This is not a fair comparison (Score:5, Informative)
Actually, if you look at the benchmarks it loses in everything but the GL benchmarks. Then go and look at the benchmarks at phonearena and the 5S hands the Nexus 5 it's ass on pretty much every test. Personally I'll reserve final judgement until I see an anadtech comparison but looking at everything out there right now, the Nexus 5 doesn't hold a candle to the iPhone 5s. That's not to say it's a bad phone, because it isn't. I'm just saying you're buying a fantasy if you think this thing is on par with the 5S.
Before I get called an Apple fanboy, you should know that I own two phones and they are both Samsung Android phones.
Re: (Score:2)
I hope you are talking about the Android phone?
http://blog.opower.com/2012/09/how-much-does-it-cost-to-charge-an-iphone-5-a-thought-provokingly-modest-0-41year/ [opower.com]
Re:This is not a fair comparison (Score:5, Informative)
And that fact is mostly irrelevant. Remember back when AMD started quoting their Athlon processors by speed rating rather than MHz because Intel went all out to get high clock speeds? I thought everyone knew that megahertz were not directly comparable between architectures these days.
In this case Apple has gone down the more complex route with a processor that can do more per clock cycle at the expense of added cost and power consumption. The Snapdragon CPU takes the opposite approach with simpler cores that run at higher clock rates. Such cores are cheaper to manufacture and have power consumption advantages when not running flat out at their maximum clock rate.
Also note that the benchmarks they ran don't saturate all four cores, and neither do most mobile games. The extra RAM helps the phone multitask, and no benchmarks or games use it all on either platform so it's meaningless.
It's pretty amusing that Apple spent so much time and money to develop their CPU and it ended up costing far more than the much simpler and equally fast competition. 64 bit turned out to be completely irrelevant at this stage.
Re: (Score:3, Insightful)
And the Nexus 5 has a SoC with 2 more cores, 80% higher max clock rate and double the RAM. That it can only keep up is pretty amusing.
What is amusing is that the Nexus 5 costs half what the iPhone does. Apple's target demographic has always been people with more money than brains. Thwok....ball's in your court.
Re:This is not a fair comparison (Score:5, Insightful)
And the Nexus 5 has a SoC with 2 more cores, 80% higher max clock rate and double the RAM. That it can only keep up is pretty amusing.
What is amusing is that the Nexus 5 costs half what the iPhone does. Apple's target demographic has always been people with more money than brains. Thwok....ball's in your court.
That's not really an argument.
Remove the word "Apple" from your argument and you're essentially saying that anyone who buys any product that costs more than the absolute cheapest product available in that class is an idiot.
This sort of bell curve of product purchasing is totally accepted in everyday life (cars, food, houses, sports equipment, televisions, jewellery, books, entertainment, holidays...) but somehow when the same metric is applied to computers, unless you buy from the bottom of the discount bargain bin, you're suddenly an idiot.
It's certainly a strange argument coming from the corner than claims to promote user choice. Or is it only the right choice if they make the same choice that you do? Anything else is the consumer clearly demonstrating they have "more money than brains"? Is it part of the Android experience to not just enjoy the phone and ecosystem you selected based on your own criteria, but also to insult anyone who had a different set of selection criteria to you? Put another way; I don't think all Android users are idiots for not choosing iOS, or OS X.
As is predictable in this thread, when Apple is on top on benchmarks, suddenly they don't matter. When Apple is behind on benchmarks they get bashed for having "expensive, old hardware that can't keep up". In other words, the argument positions between the extremes of the camps swaps over. Still, the underlying "if you didn't buy an Android you have more money than brains" always persists.
Thwok; ball is back in your court.
Re: (Score:3)
People like you badly need for there to be products other than Apple products. For some reason it matters that you have a company's product-line to champion.
It's really a strange phenomenon and Apple takes great advantage of it.
I do?
Or again are you just describing any company that makes a product that people like to buy.
Do you say the same thing about people who like Fords? Or Kellog's Cornflakes instead of the store brand?
What's wrong with having a positive opinion of a company? Other than the fact that you don;t like them of course.
This is going to seem out of place here (Score:5, Interesting)
Re: (Score:2)
They are very nice phones. One gives much better performance for the money, but both are nice. Of course, one runs an open OS and the other is controlled very tightly. Choose based on your needs.
Re: (Score:2)
Yes, wonderfully open. Open to Google who gets to peer into your shorts and your soul.
Unless you root the thing and put Cynogen on your device (if you can) you're merely switching gardens. The number of people interested and capable of doing so are well in the noise floor.
Re: (Score:2)
You need no contact with Google for _any_ version of Android that I know of.
Re: (Score:2)
I chose the N5 personally - I'm well invested in Android apps, and it automatically re-installs the apps I use with their data. But I do see why people like the iPhone. My daughters prefer it.
I wonder if the benchmarks enabled ART [androidpolice.com] though. I'm enabling the new ART runtime on mine and will report back if the numbers are significantly different from the article. It takes a while to enable ART if you have a lot of apps...
At this level though the benchmarks seem ridiculous. Both phones have the power and
Re: (Score:2)
Ice Storm Extreme benchmark on N5 with ART reports "Maxed Out! This test is too light for your device. Try running Ice Storm Unlimited instead." The only other device with this score is iPad Air. Ice Storm Unlimited reports Ice Storm score 16943. Details:
The other devices reported are Kindle Fire HDX 7, Acer Liquid S2, NVIDIA Shield and Pantech Vega LTE-A. The differences between these are not signif
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
They aren't really competing products with that kind of price difference.
Re: (Score:2)
Most people in the US buy an iPhone on contract at the $99 or $199 subsidized price.
I wonder how the carriers can sell the phone for $500 off list price, there must be some catch somewhere. I wonder what it could be.
Re: (Score:2)
Re: (Score:2)
They rape you on call costs for the duration of your contract.
Naaa, that can't be it. Anyone that can do simple arithmetic would quickly see through that scheme!
Re: (Score:2)
Re: (Score:2)
go get a fucking dictionary, my friend. then go get a woman so you can chill the fuck out.
You still don't get it! Specs do not matter... (Score:5, Insightful)
Qualcomm's latest Krait 400 quad-core along with the Adreno 330 GPU that comprise the Snapdragon 800, is a powerful beast.
If they had not focused much on the specs, but rather on battery life that can last a day of average use, I'd be happier. I ask my self: -
"Of what use is having the"latest and greatest if by mid-afternoon, I will be holding a brick in hand?
This is what I do to these good phones that are limited in the battery department. I underclock them with acceptable results.
By the way: Can one explain to me how Motorola was able to cram a 3000mAH into a phone smaller than this but Google and its LG partner cannot?
Re: (Score:3)
The LG G2 has a 3000mAH battery, so I am assuming it's an issue of keeping the cost down.
Re: (Score:3)
It would seem, the mAH doesn't seem to matter: KitKat (and presumably, with ART as well, as people have reported, but not the example I'm about to cite) have improved battery performance immensely. Here is one example of many [google.com].
Personally, I am getting 4 hours screen-on with 16 hours standby, and still have 15% battery left, using Dalvik, Google now (all options on), WiFi+LTE (but GPS and bluetooth off), which is more than acceptable IMO and great.
So maybe, much like the CPU MHz, we should stop concentrating
Re: (Score:2)
I have yet to see real battery benchmarks but Google is claiming 17 hours of talk time and 300 hours of standby. If the phone gets even half that it's going to have better battery life than any device released in the last 7 years.
Re: (Score:2)
Lol. The talk time metric is so outdated now. Hands up who uses their phone for voice more than anything else? Anyone? Bueller?
Thought not.
Re: (Score:2)
Qualcomm's latest Krait 400 quad-core along with the Adreno 330 GPU that comprise the Snapdragon 800, is a powerful beast.
If they had not focused much on the specs, but rather on battery life that can last a day of average use, I'd be happier. I ask my self: -
"Of what use is having the"latest and greatest if by mid-afternoon, I will be holding a brick in hand?
This is what I do to these good phones that are limited in the battery department. I underclock them with acceptable results.
By the way: Can one explain to me how Motorola was able to cram a 3000mAH into a phone smaller than this but Google and its LG partner cannot?
My N5 has been off the charger for 15 hours, I used it off and on today for Pandora streaming and web browsing, texting, and email, and the battery is down to 58%. What are you using the phone for that it won't last a day?
Can't I just have (cheap android phones) (Score:3)
Re: (Score:2)
... something better than my old HTC 3G EVO that runs latest android for a decent price? I'm switching to Ting and don't mind buying behind the curve, but it's not easy to get something at the same budget I'm used to when I get the phone(s) mostly subsidized from Sprint. Maybe I'm looking at the wrong review sites to find a peppy cheap android.
Last I heard, Ting was waiting to see if Sprint would let them activate the Google Play Nexus 5's, or if they could only activate ones bought from Sprint or from Ting.
I was testing my N5 against a 5S at lunch today (Score:5, Interesting)
We ran Sunspider (1.0.2).
The iPhone 5S (and a Nokia Lumia 920) pasted my Nexus 5 on Sunspider. Both were about twice as fast as the Nexus 5.
I like the Nexus 5, it's very snappy. But when using it, it doesn't feel faster than a 5S.
The N5 is a heck of a value.
Now, about the awful pictures it takes... Is there any chance a better camera app (which also sucks) can improve them some?
"Snapdragon" sounds like a pornstar's name (Score:2)
Really Awesome Phone (Score:2)
I have owned iPhones since the iPhone4. I currently own the iPhone 5. My wife owns the Nexus 5. I can tell you that there is *** NO LAG *** on either the Nexus 5 or the iPhone 5. They are equally fast, both very smooth and instantaneous response times. Both phones are very, very sweet.
The iPhone 5 presentation is slightly nicer, but for the price??? The Nexus 5 is king. There is NO comparison. When you consider the cost difference, Apple gets kicked to the curb.
My initial thoughts? I love the new I
Re:New phone almost as fast as month old phone (Score:5, Insightful)
Well it's actually worse than that. A phone that has a SoC with double the cores, cores that have a max clock rate 1 ghz higher and double the memory is only able to win in a couple of tests and just keep up with the A7 in every other test. Sounds like pretty fail.
Re: (Score:2, Interesting)
Now now that shit will get you down-modded here (as will this post, most likely). because here at slashdot we're all about software efficiency, not that bloated microsoft shit.
Owait..
Sooner or later, Google are going to have to admit that using a JVM was a bad idea. JVMs have been fail on the desktop since the mid 90s, and waiting for hardware to catch up has proven to be a mistake - especially in mobile. More cycles = more power = bigger battery required = more weight.
Re: (Score:2)
Re: (Score:3)
Re: (Score:3)
Re: (Score:3, Insightful)
whereas apple made the decision and bet on ARM.
Apple has experience and proven track record in quickly changing archs. If anything new cpu arch would mean more money for them - forced upgrade cycle in ecosystem where users currently upgrade almost only when old stuff breaks or new one looks nicer.
Re:New phone almost as fast as month old phone (Score:5, Informative)
the article doesn't touch on this, but I wonder how much untapped power is in that 64bit processor in iPhone. what's cool is, that's dormant in my phone right now, but will be unleashed next year so it will be like getting a new phone.
Please tell me you're being sarcastic... Even if all your apps get recompiled to 64-bit versions, you are not going to get a massive performance boost. Have you ever tried running a 32 vs. 64 bit install of Windows or Linux on the same hardware? Not too much difference for average use cases...
Re:New phone almost as fast as month old phone (Score:5, Funny)
yeah but if you use your iphone as a media transcoding server, the gains with be iMazing!
Re:New phone almost as fast as month old phone (Score:5, Informative)
The main advantage of 64 bitness is access to a far larger memory address space. Yes there can be a few minor performance improvements with proper use of larger registers, but it's really not that big an advantage. Until smartphones and tablets start exceeding 4 gigabytes of RAM there is really not much point other than marketing to use 64 bit code on such devices.
That has been debunked again and again and again.
There has been iOS code that was measured to be 45% faster just by being recompiled to 64 bit. There are plenty of tricks in the Objective-C runtime and the C++ libraries that make it _significantly_ more efficient when running on a 64 bit processor. For example, a std::string up to 22 chars doesn't allocate any memory on the heap in 64 bit code but just uses three 64 bit words.
Re:New phone almost as fast as month old phone (Score:4, Informative)
The main advantage of 64 bitness is access to a far larger memory address space. Yes there can be a few minor performance improvements with proper use of larger registers, but it's really not that big an advantage. Until smartphones and tablets start exceeding 4 gigabytes of RAM there is really not much point other than marketing to use 64 bit code on such devices.
Oh c'mon. Slashdot is supposed to be the smart nerds.
One advantage of a 64 bit architecture (such as x86_64 or the A7) is that in order to hold 64 bit data. But if you're still working with 32 bit data (and most of us are), you can simply load each register with two 32 bit chunks, basically doubling the amount of data you can hold on chip, and the processor has functions to support this.
And if you look at what Apple did with the A7, not only does their 64 bit chip do this, but the new ARM64 specifications double the number of registers in general:
"The ARMv8-A instruction set doubles the number of registers of the A7 compared to the ARMv7 used in A6.[13] It now has 31 general purpose registers that are each 64-bits wide and 32 floating-point/NEON registers that are each 128-bits wide."
http://en.wikipedia.org/wiki/Apple_A7 [wikipedia.org]
So basically you now have an crazy amount of registers, and an insane amount of registers if you are dealing with 32 bit data still. The NEON registers are 128-bits wide and there are 32 of them. If you have 32 bit data, you can process 128 chunks at a time! If you're working in float_16 with NEON, you can work through 256 chunks at a time. That's crazy good compared to ARM32. That would really speed up anything that works with media, images, video, animations, etc, most of which a modern window server does.
But that's not really the end of optimizations. If your registers are large enough, why bother using pointers? And that's what Apple did with the Objective-C runtime on ARM64.
http://www.mikeash.com/pyblog/friday-qa-2012-07-27-lets-build-tagged-pointers.html [mikeash.com]
Basically, if you've got a small enough object type, like an object that holds an 32 bit type, you can skip the allocation of extra memory to hold this data, and just store it in the pointer itself. A lot of the low level and frequently hit methods in Obj-C (like the entire memory allocation tracking system) have been optimized for this, so you should see a speedup in even basic applications.
Re: (Score:2)
Android already supports applications using native code. But a lot of apps just don't need it.
Re: (Score:2)
Re: (Score:3, Insightful)
It makes no difference to battery life; almost all the battery usage on Android phones goes to the display and the radio. And CPU-bound applications (e.g., PhotoSphere) are written using native code anyway.
Re: (Score:2)
Re: (Score:3)
I doesn't have "2x the CPU hardware"; the number of cores bears little relationship to the amount of "CPU hardware" a chip has. For mobile systems, people often use more cores but slower cores to save battery life, because for most tasks only one core needs to be activated. You'd use all cores only on compute-intensive tasks. And for benchmark comparisons, it gets even trickier because some benchmarks may be able to take advantage of lots of slow cores, while others prefer fewer faster cores. In the end, wh
Re:New phone almost as fast as month old phone (Score:5, Insightful)
Yeah but that phone is half the price of the iPhone.
Pretty impressive to me.
Re: (Score:3)
Where is the Nexus 5 half the price? Everyone is selling the Nexus 5 for $350 with contract while the iPhone 5s is $200 with contract.
Incorrect.
The Nexus 5 is $350 for the one with 16GB of space, $400 for the 32GB one, and that is with NO contract.
iPhone 5s is only $200 with a contact, if you want to buy it outright without a contract, it costs $650 for 16GB and $750 for 32 GB.
In other words, about 1/2 the price.
Re: (Score:3)
Nexus 5 $350 no contract, direct from google:
https://play.google.com/store/devices/details/Nexus_5_16GB_Black?id=nexus_5_black_16gb&hl=en
iphone5s is $650
http://store.apple.com/us/buy-iphone/iphone5s
The only real comparison is to compare phone prices without contract, because on contract the additional cost of the phone is included in your bill which you pay over the term of the contract.
The N5 is so close to half price of the iphone5s as to make no difference. I used to grudgingly admit iphones could be
Re:New phone almost as fast as month old phone (Score:5, Informative)
New phone almost as fast as month old phone.
Xperia Z1 was released same day as iPhone 5s. It is faster, waterproof, and has higher res 1080 screen. It also has a 20.7MP camera with a much larger 1/2.3" sensor.
Re:New phone almost as fast as month old phone (Score:4, Insightful)
Re: (Score:3)
Exactly. Until a mandatory firmware update some time after purchase.
Re: (Score:2)
The physics test is quite telling and shows just how limited the low speed, dual core
The physics test seems to have little relevance to actual gaming performance since even against the Note III in offscreen tests the iPhone 5S was pretty much neck and neck on rendering rate.
http://www.anandtech.com/show/7376/samsung-galaxy-note-3-review/4 [anandtech.com]
In that review the iPhone 5S won 4 of the 7 CPU tests that it was in. It won 3 of the 6 GPU tests measuring FPS rendering speed. In 2 of the tests that it lost it only lost by 1 fps, in the other offscreen test that it lost at it was 57 fps vs. 69 fps. Whi
Implementation is real weakling (Score:3, Informative)
iPhone 5 got its ass handed to it due to the weak CPU in it.
Weak CPU, or weak physics engine that didn't use OpenCL or the Accelerate framework...
In fact the benchmark technical guide [amazonaws.com] says explicitly:
The GPU load is kept as low as possible to ensure that only the CPUâ(TM)s capabilities are stressed.
Which is a really stupid way to compare things as anything that relied on advanced physics would be using some kind of accelerator for computation other than the CPU. It also means it's not using any of the
Re: (Score:2)
So the screen resolution is why it was faster in Sunspider and Browsermark? Also in the off-screen GPU test (of which screen resolution makes no difference) it was only 10% slower which makes sense since the GPU cores on the Snapdragon 800 are clocked faster.
Re: (Score:2)
Re: (Score:2)
Shame...
Re: (Score:2)
They talked about the fingerprint reader, the secure storage and how the new M7 processor will give you better battery life. These are real things that impact customers. Didn't they talk about faster LTE throughput too? Maybe I misremembered.
It wasn't just specs.
Re: (Score:2)
Actually, their last keynote did mention that sort of thing. 64 bit?
Re: (Score:2)
Re:Is it a phone ? (Score:5, Funny)
Re:Is it a phone ? (Score:5, Insightful)
I am curious...
Before the 20th Century did the average person drive an automobile?
Before the Industrial Revolution did the average person have access to cheap, mass produced good?
Before the Agricultural Revolution, did the average person have access to plentiful grain?
Before the Paleolithic, did the average person have access to crafted stone tools?
Don't get me wrong, I'm just curious...
Re: (Score:3)
Re: (Score:3)
Re: (Score:2)
So can get a supported version of Kit Kat on all past versions of my Nexus Phones?
Google said there's an 18 month update window, and anything Nexus than the Nexus 4 (like the Galaxy Nexus) won't get Kitkat:
https://support.google.com/nexus/answer/3468085 [google.com]
Is Google releasing Android 4.4 as a system update for Galaxy Nexus?
No, Galaxy Nexus phones won’t be receiving the update for Android 4.4 (KitKat).
Why isn’t Galaxy Nexus receiving the update to Android 4.4?
Galaxy Nexus, which first launched two years ago, falls outside of the 18-month update window when Google and others traditionally update devices.
Re: (Score:2)
The iPhone might not be any better (I don't know and don't care) but that's fucking pathetic.
As a Galaxy Nexus owner (who just bought a Nexus 5) I agree, an 18 month update window is pretty bad in an industry where 2 year contracts are common. There is a petition to get Google to release Kitkat for the Galaxy Nexus, but behind the scenes, Google is blaming it on TI:
http://news.cnet.com/8301-1035_3-57610844-94/galaxy-nexus-owners-petition-for-taste-of-kitkat/ [cnet.com]
Re: (Score:3, Interesting)
The iPhone might not be any better (I don't know and don't care) but that's fucking pathetic.
iPhone 3GS shipped with iOS 3.0 in June 17, 2009.
Final iOS update was 6.1.3 in March 19, 2013.
http://en.wikipedia.org/wiki/IOS_version_history [wikipedia.org]
That is 45 months. (Past performance does not guarantee future results.)