1) To quote a Reddit meme, the icons are just... too damn big! Yes, the screen is lovely and the new icons are perfectly good looking, but they're huge! Even on a 5" 1080P screen, you are only allowed a 4x4 grid. I used a 6x6 grid on my Galaxy Nexus and think that size is far more appropriate, especially if you want to take advantage of multiple widgets on your homescreens, or a mix of widgets and shortcuts on the same homescreen.
2) Related to the first complaint, you can't create app folders in the app drawer. This makes it impossible to "hide" things like LightFlow, News & Weather, Keep Screen On, the default Email client, or other utilities and random apps you don't ever want to see. At least you get five rows of four, but still, the icons are infuriatingly large.
I haven't played with the camera enough to comment, and the battery is light years better than my Galaxy Nexus so I have no complaints there (yet). I do carry a Powerstick (http://www.powerstick.com) in my briefcase when traveling, though.
The fact that you can now do both video and voice, or just voice, Hangouts while on cellular networks is enough for me to overlook quite a few issues.
One last tidbit: the new dialer & phone app is much, much better than the old stock one (imho, this is something Samsung really did a good job of with Touchwiz), but it is not intuitive and there are some wonky things about it, like the fact that the standard dialing screen only shows 3 of your starred contacts and there is no apparent way to scroll/view the rest of your favorites.
I'm expecting a 4.4.1 sometime not too long from now because there are enough things lacking polish to warrant a few extra weeks in the oven.
As for the hardware, not a huge fan of the sharp edges, but it does feel good in the hand and the small side bezels make it feel smaller than a 5" phone should.
Then again, I wonder how much of the "your speakers suck" problem is really just "OMG netflix why the hell are your streams so quiet"?
Galaxy Nexus? Yes. Nexus 4? Closer, but still yes. Galaxy S3 and S4? Yes, because Samsung is really pissing me off with their lack of speedy updates. HTC One Play Edition? Undecided. Merging the two together would be the best phone (speakers on One, the proud buttons and texture on the N5) but I wouldn't trade one for the other at this point.
On the Nexus 4 and 5, the option is enabled regardless if you paid for tethering or not. This is because the phone comes directly from Google, so t-mobile did not get to install bloatware (custom OS) that disables the feature.
I call it "native" because it is built into the OS, versus installing third party apps that mimic the feature. Usually these apps require rooting your phone.
I have used nothing by samsung smart phones, the last phone I had that was a non-samsung was the Moto Razr Original Flip phone.
I currently run a Note II, will never buy another directly as a Result of their lack of updates for the device. Stilling have 4.1 as the official rom is ridiculous
The unremoveable bloatware and need-to-root for certain features is beyond frustrating. It's like that Dell laptop you got back in the early 2000's, except you need to reinstall the OS to run it normally.
Too bad I already ordered the 5, but if its as bad as you say, I may have to sell it and just give up on Nexus and get the HTC One.
I really wish they'd put some more effort into the speakers and camera on the Nexus phones, though the Verge review implies that the meh Nexus 5 camera is mostly software.
I'm extremely disappointed that Google launched such a tight integration with such key functionality missing.
I've also had to clean my phone off twice because Google's backup service continues to think the phone is new so it keeps sending me a bunch of crap I don't want on my phone.
I haven't seen a lot of lag issues yet, but I've only had it for 24 hours or so.
KitKat ship with an experimental version of ART, and it seems to perform better in synthetic benchmarks than Dalvkit. People online are also reporting a smoother experience with it (but it might be placebo, I don't think there's a scientific and unbiased comparative between the two yet).
The single and only lag complaint I've seen was an utterly ridiculous "scroll up and down quickly in Chrome" video preview on the Verge. Not only does it have zero association with actual use, iOS displays exactly the same so-called "lag" on premium devices with complex websites like the Verge.
The lag beast has been slayed. Perhaps mostly through just enormous computational horsepower, but it is a non-complaint.
http://bgr.com/2013/09/20/iphone-android-touch-screen-respon...
I'm a very happy owner of a 2013 Nexus 7, but I have to say I think this is perceptible. It's not showstopping or even disorienting, but it does translate in performance critical tasks like web browsing and gaming being slightly less satisfying. With an iPhone, scrolling feels like you're manipulating a piece of paper under your finger; Chrome on my Nexus 7 doesn't quite achieve that illusion.
Then again, the OS itself feels way more nimble than iOS: things like text-to-speech, app installs and multi-tasking are way more satisfying on Android.
However, I own a Samsung Galaxy S1 (that's 2010 era, people) running CyanogenMod 10.1.3 (that's 4.2.2) and my responsiveness is... just fine! Pulling down the slider I get the very slight initial lag (simply because my phone is crazy slow), and the slider itself does lag behind but that seems like it's by design.
Next I am on my homescreen; ADW Launcher, and I'm running running some taxing animations with 1x Animation Scale. There is no input lag. I can get the initial lag and again that is just my phone being a wreck by today's standards, but going back and forth the animation is as responsive as could be.
Based solely on my anecdotal evidence, I call BS.
Lag historically was a significant delay between interaction and response. It was also continual stutters and variances in interaction speeds.
But by Android 4.4 and the N5, that is generally annihilated. Paradoxically at the same time iOS 7 on my 3rd generation iPad has brought Android 2.x-style lag to that platform -- I now have an experience on it where keyboard presses respond 700ms later, and other activities have completely unpredictable delays.
On iOS, putting the finger on an icon and moving it feels more "real" because the icon stays under the finger. On Android, a quick motion of the finger lets the icon trail behind... Perfectly smoothly, but behind. I hope Google fixes this at some point but I suspect the low latency we see on iOS is possible thanks to a tight integration between hardware and software that would be difficult to achieve on Android.
Overall though, I feel like my HTC One with CM10.2 feels just as smooth as my previous iPhone 5 90% of the time. 10% of the time, it stutters a bit, but I'm going to chalk that up to CM10.2 being a community project.
Chrome has no access to the iOS Nitro JS engine so a difference would certainly be expected.
You just proved my point. They are not fixing anything, just adding work around after work around and one of them is throwing more horse power at it. The inherent problem is still there, they just keep covering it up.
The vibration motor is at the top of the phone. This is causing some people to complain on XDA that the haptic feedback is weak or non-existent. When you run a vibration test its easy to hone in on exactly where the motor is located which seems a bit off to me.
The speaker is absolutely anemic. I 'feel' the sound vibrating the back of my phone more than I can hear it through the single tiny speaker located at the bottom of the phone. Companies need to start emulating the HTC One and place the speakers on the front.
Otherwise the device feels elegant and the texture allows for a softer grip that allows longer use without getting crab hands.
Now KitKat (and specifically Hangouts) is a different story altogether...