Motorola DROID MAXX, Black 32GB (Verizon Wireless)..
Special Price Motorola DROID MAXX, Black 32GB (Verizon Wireless) By Motorola
Most helpful customer reviews
312 of 322 people found the following review helpful.
By Nathaniel Allen
[updated Jan 27th 2014; OS update 19.5.3 applied -- see paragraphs marked with +++ for my edits]
[updated Nov 11th 2013; OS update 12.15.15 applied -- increased my rating to 5 stars (from 4) -- see paragraphs marked with >> for my edits]
I didn't intend to buy a Droid Maxx on launch day; at least, not until a few minutes before 10am, when I read on Droid Life it would *really* be in stores that morning. I would only stop in to check it out in person. Then... it just happened. If you're like me and coming from a Samsung Galaxy Nexus, I'm betting this latest batch from Motorola caught your eye, too. I fully intended to wait for the first reviews, maybe check out the oversized Note III and HTC One Max, and see what LG was bringing to the table, but...
The Maxx's oversized battery is only part of the attraction. My Nexus had become fickle -- I weeded out a few apps that were absolute battery hogs on that device. While I didn't expect the full two day battery life promised by Verizon, the Maxx had to be at least 2x better than the Gnex, based alone on double battery capacity. But better! After my first 100% charge, I ended my day at 7% after 16 hours off the charger, heavy "first day with a new phone" usage, 1.5 hours video, 1+ hours audio streaming, 45 minutes unplugged Nav, forum browsing & posting, futzing with apps, editing this review, Bluetooth headset use, switching between wifi and 4G about 50/50, lots of screen on time, etc. I've since repeated this with up to 23 hour days, 5-8 hours screen time, video & nav, completely off the charger. I've bumped my screen timeout to 5 minutes, and don't bother switching off WiFi or GPS. And if that's not epic enough (for me, it is), there's a "Battery Saver" slider on the settings menu -- I haven't bothered to flick that On to see what it affects.
Amazingly, the extra battery doesn't come at the expense of size. Held back to back, side to side, end to end, these two phones are close to identical in size. You can get the numbers from the spec sheet, but the Maxx is about 3-4 millimeters taller and wider than the Gnex, and more or less identical in thickness. According to my straight edge, the Maxx's screen even has a slight curve to it, ala the overly-hyped curved glass of the Galaxy Nexus.
But it's definitely shaped differently. I ran my Gnex without a case for the past year, and I'm starting out caseless with the Maxx. I don't see it visually, but the Maxx has a "wedge" feel to it, where the top end of the phone is thicker, and it slims down towards the bottom. The top end is also heavier. What this means is that, when I'm holding it in one hand, most of that weight is concentrated on my index finger. I'd prefer it the other way around -- with that weight and thickness at the bottom -- where it's resting more on two fingers. I know, I know... we're only talking about 164g according to my scale, but the phone feels more comfortable and balanced when I hold it flipped around like that. Despite the very similar size to my old phone, the Maxx has a definite chunky feel to it, not UNcomfortable, but -less- comfortable than my previous phone.
+++ My wife slipped a Diztronic TPU case onto her Maxx, and despite its slim dimensions, the phone feels bulky and unpocketable. My recommendation is to skip the case if you can.
+++ If you need a quality holster for this phone and want to run caseless, and don't mind an easy do-it-yourself mod, check my review for this Sedio spring clip unit: Seidio HLSSG4AASA
The phone's back is interesting. It's not the shiny, hard plasticky finish of the Droid Ultra. Instead, it's a very lightly textured ("rubberized") but smooth finish, with the appearance of a fiber weave. This finish wraps around the bottom edges of the phone and even around the chin to the face, down by the mic. The bottom corners are all rounded, so they're somewhat comfortable -- not squared off, though not as rounded as the Galaxy Nexus. The back is smooth enough that it -does- gets smudged with fingerprints, but matte enough that they're not easily noticeable. The Verizon and Droid labels are modestly sized, and rather than bright white, are of a dark gray hue that is easy to ignore.
All together it creates a package with a hefty, high-quality feel. I never minded the durable all-plastic construction of my Nexus and Samsung's Galaxy lineup -- something many reviewers and forum posters dismiss as "cheap." But the Maxx feels anything but, possibly belied by its flat slab appearance.
Interrupting the smooth Kevlar wrap are the power and volume buttons -- all stacked on the right side -- that project from the device perhaps a little more than necessary, and with very square edges and textured surfaces. The buttons don't really jive with the carefully crafted, smooth-to-the-touch backside finish, but then again, there's no mistaking when my fingers are resting on them -- even lightly -- so hopefully no accidental presses.
+++ Boot is about 55 seconds to home screen and signal lock [post KitKat 4.4 update; original boot time was 30 seconds, which increased to 45 seconds with 12.15.15]. That's still pretty quick to phones I've owned previously, but nearly double the stock, Day 1 boot time. The busy (and noisy) Droid boot animation, followed by the default red home screen, put me off at first -- it all just feels very "angry" -- but as I'm sure you're aware, that's all easily changeable with a good selection of included live and static wallpapers (a soothing blue relaxed the feel of the phone for me; I wonder if the default aggressive red tone -- VZW's Droid branding -- turns off would be buyers at the in-store display).
While looking for my next phone, I've been really intrigued by the front-firing speaker on the HTC One. My previous phone (like practically every other phone) was rear-firing, but with speaker placement at the bottom of the phone, where my hand tended to cup it and muffle the volume. Not to mention it was a pretty weak speaker. The Maxx? Surprisingly good, by comparison. The speaker is at the top of the phone, co-located with the camera. It's loud. Even when facing into my passenger seat, the Google Nav directions come through crisply. I've tried to muffle the sound with my hand, like for instance when holding the phone in landscape mode to watch a video, and it comes through loud and clear. The sound is still projecting to the rear, which means the phone is projecting away from me and toward the rest of the room that I'm facing, but it's so much improved over the Gnex that I'm now only partially envious of the HTC speaker.
I recall quite a bit of forum debate over the 3.5mm audio jack placement on the Nexus -- some folks absolutely HATE the bottom placement (I, for one, was a fan). The Maxx puts that jack up on the top of the phone, where many users think is its rightful place. I suppose I'm indifferent since I tend to use bluetooth headphones when I'm out. But at home, laying in bed and catching up on some YouTube while plugged in to my charger, I've now got to contend with cords coming out of both sides of my phone.
One other design niggle -- wnen using the phone on a flat surface, screen presses anywhere within a half inch of the edges causes the phone to rock. The back runs flat for a few inches from top to bottom (down the spine), but is curved side to side all the way across.
Let's talk about the Super AMOLED (RGB) screen. The quality is great. Really, I'm don't feel deprived without 1080p. But, don't hate me for this, I preferred some aspects of the Galaxy Nexus Pentile (non-RGB) AMOLED better. Here's what I'm noticing with the Maxx:
- whites look slightly gray, particularly in a dark room
- blacks have sort of a reddish tinge to them, particularly in dark
- in general, pictures look underexposed (for instance when browsing a news website)
- in video playback, the black and darker areas of the screen have better overall consistency than on my Gnex (less noise)
- in bright sunlight, the screen brightness can't meet the challenge (so what's new?)
- but in dark rooms, it's almost as though the screen can't dim enough (but just slightly so)
- the active notifications appearing on the screen aren't ever-present -- the phone needs to be jostled / disturbed for the blank screen to briefly light up and display the current notifications, BUT the phone does not need to be flipped over to activate this (a light tapping of the face-up phone causes the Active Display to light up)
- >> the capacitive buttons now dim during most video playback [as up 12.15.15 update] -- nice; they were originally full bright, which was distracting in a dark setting.
- there's just the slightest amount of light leak from between the screen and capacitive buttons, over the Back button -- but only noticeable in a dark room
- the Maxx pixels per inch (PPI) display density works out to 296 PPI across the 5" screen. The Gnex screen was slightly smaller (4.7" -- less if you consider on-screen buttons took up some of that space), so despite it being the same resolution, would have been 316 PPI -- except for its shared-pixel Pentile display. I've seen the case made that the Pentile display dropped the effective PPI down to the 200 range. I can't say I ever took issue with that screen by Samsung, but I could see jaggies on certain websites, and those just aren't present on the Maxx -- this display, overall, appears sharper.
There's going to be an adjustment period for me, no doubt, but despite some of the negatives I've listed, I don't consider any of these to be deal breakers.
I mentioned the capacitive buttons. Versus the on-screen buttons found on the Moto X and Gnex, these ones are ever-present. Accessing Google Now takes a slightly paused press of the home button before swiping up, vs. the simple swipe motion (no hold) of an on-screen home button. And some older apps still call up the 3-dot menu button which takes up a whole 'nother row (a black "menu bar" across the entire bottom of the display). On phones with the virtual buttons on-screen, the main three (Back, Home, and Task) would simply make room for the skinny 3-dot -- making it all the more obscene that when it appears on the Maxx, it takes up its own row. To get around that, I can go into Settings and enable a "long press of task switcher" option. That gets rid of the wasted screen, but now I have to remember which apps use this long press to access the menu (and some apps only do this on certain screens). This should be less and less of a problem as developers update their apps, as I believe the standard for the OS v4.0 and higher is to display the menu ellipses at the top right corner of the application.
+++ Speaking of OS, my phone came with Jelly Bean 4.2.2, but units shipping now ought to have KitKat 4.4 installed (or otherwise readily downloadable via an easily access "Check For Updates" selection in the Settings > About Phone > System Updates menu). If you're coming from a Gnex, KitKat is basically the same, only snappier. If you're coming from Ice Cream Sandwich or Gingerbread, I guarantee you'll be impressed with the smoothness and overall look/feel of this operating system.
I'm still setting up my various apps and checking them for compatibility. I'm not going to attempt to generate a comprehensive list of what does / doesn't work, but here are some quick notes:
- +++ As of the KitKat update, FoxFi is no longer compatible for WiFi tethering. You'll have to resort to USB tethering instead.
- >>> As of 11/12/13, FoxFi is compatible for tethering. It *requires* a PIN-enabled lock screen (not pattern) due to some VPN nonsense that I admittedly don't completely understand (FoxFi was great on the Galaxy Nexus, and didn't require this)
- +++ Google Wallet tap-to-pay IS FINALLY supported with as of the KitKat OS -- an app I've been running on the Gnex since about week one. Cruel irony, my purchase of the Maxx was my last Google Wallet NFC transaction before the KitKat update (Verizon clerk: "Oh, I've never seen THAT before!" as I swiped my Nexus across her payment terminal)
- YouTube updated me to version 5.0, which I was not yet able to access on the Play Store from my Gnex or my TF700T tablet
- Swype keyboard is working A-Ok, and pops up nearly instantly when called
- +++ Nova Launcher is working A-Ok; mic icon in "persistent search bar" (shortcut to Google Now) calls up the voice recognition screen nearly instantly; [new KitKat option for transparent notification bar works as demonstrated on Nexus KitKat devices]
- Sound Profile app by Corcanoe is A-Ok without any of the problems / workarounds experienced by Galaxy S4 users
- The stock Android dialer app has been enhanced to allow dialing by first or last name, or partial phone number -- nothing new for users of skinned versions of Android (Touchwiz, Sense, Motoblur) or other OSs, but a feature requiring an aftermarket app for stock Nexus users
- +++ "OK Google Now" is quick, responsive, and so far pretty awesome... but less so with a lock screen [New with KitKat: with user permission, the phone allows certain voice commands to process even if the phone is locked; actions requiring an unlock allow the user to speak the PIN code]
- "Set alarm for ten a.m." used to take me directly to the stock clock app, even though I had alternate alarm applications installed. No longer; I'm now given the option to default to whichever one I choose (tested with Timely and Alarm Clock Xtreme); no such luck with "set timer for three minutes", which still just sets an alarm for whatever time is closest to 3 minutes from now
- As expected, logging in with my Google credentials automatically downloaded all my apps and contacts, with the exception, oddly enough, of Facebook
- Not exactly an app, but the brightness slider from the main pull-down menu is very picky, doesn't like switching back to "Auto," and times out quickly -- but works fine from Power Control widget
- +++ There's a bug in the task switcher where not all open apps appear -- including the app I'm currently using (this originally was the same with the Gnex, but was changed in a recent OS update). [This seems to have been partially resolved with KitKat -- it still happens, but less frequently.]
- +++ [Settings > Apps now has a dedicated "Disabled Apps" view to allow me to see all the unwanted Verizon pre-installed goodies I've exiled from my app drawer. They used to appear at the bottom of the lists.]
+++ The Camera [post 12.15.15 update & post KitKat observations]: I'm now super happy with the camera. Images were always as sharp as can be expected from a cell phone, with good, natural colors. There's no longer a problem with highly contrasted scenes (original firmware couldn't handle bright backlighting, such as under a canopy of trees with a bright sky in the background). I'll continue to rely on my compact camera outfitted with an Eye-Fi Mobi when I'm looking for best clarity and dynamic range, but the Maxx's results are definitely suitable for everyday, in-the-moment type shots. Under KitKat, Tap-To-Focus has been replaced with "Drag-To-Focus:" drag the focal bracket anywhere on the screen to set the focal point and exposure; tapping anywhere on the screen releases the shutter. Holding my finger press captures a multiple exposures at a rate of one frame per second (and displays a convenient counter), great for automatic GIF animation by the magic behind Google Plus (which I have set up to auto-upload my pics). The updated camera UI moves the mode dial to a large arc along the left edge, and utilizes that nifty "twist yer wrist" technique to pop directly into camera mode from sleep, like the Moto X (and no unlock PIN required). There's also a half-decent slo-mo video mode, which is fun for well-lit scenes of fast moving objects, or just a honey bee landing on a flower. The HDR mode is incrementally improved with OS 4.4 -- still not on par with true 3-frame HDR post-processing, but an acceptable substitute for scenes where compromised lighting would otherwise challenge these rinky-dink sensors. As of the 12.15.15 update, the camera software now appears to be updated as an app in Google Play, which ought to mean no more delays waiting for Verizon to vet the software via their "slowest in the biz" OS update process.
The flash is dimmer and yellower than what I've become accustom to on my Nexus, but this is only evident when I'm using it as a flashlight. In flash-filled photos, the camera's white balance is adjusted appropriately for the non-exactly-white LED, and as long as my expectations aren't too high (i.e. subjects are within 6-10 feet of the camera and I'm not trying to light a whole room), the photos seem to be adequately focused, and in a matter of only a second or two. But don't expect you're going to freeze any poorly-lighted motion with this shooter, and expect to see a good amount of noise at full rez. This isn't a Nokia, after all!
The operating system is pretty dang close to stock Jelly Bean. Motorola threw some extras in there for the camera and photo sharing, plus a widget or two, and of course there's a whole bevy of Verizon bloat including NFL, MyVZW, visual voicemail, VZW nav, etc... even a caller ID service that sneakily activates, then tries to enroll the user for monthly billing. But with 32 gigs of memory on board, a little attention paid, and the ability to quarantine these apps, they're hardly a bother. The phone's interface is pure Google.
In that list of apps up above, I pointedly mention the delay-free call-ups of the Swype keyboard and the Google Now microphone icon. Launching these actions had been increasingly bogged down on my Nexus, I believe due to memory management issues. Androids TRIM memory management in Android 4.4 should prevent that on this phone.
+++ The "OK Google Now" voice wake (well, really, it works when the phone is already awake, too) is shaping up to be more than a gimmick. After an initial "voice training" session in a quiet place, I OK Google Now'd my phone where it sat on the passenger seat cushion. "Navigate to work" (work already being defined in my Google Now account) and, bingo, I'm hearing Google's familiar, clear directions. Same with text messages to my wife, and setting an alarm. One step closer to hands free. With KitKat, many actions such as Navigation or alarm settings can be voice-initiated without entering a PIN or Pattern unlock. If I dictate a text to my wife, after voice-composing the message and verifying the recipient, the Maxx will prompt "Say or type PIN code" before sending, for a true hands free interaction!
+++ Although regarding pin/pattern unlock, the Maxx offers up a cool option (excuse me if this is old news -- new to me) to recognize trusted Bluetooth devices, and gives the option to leave the phone unlocked as long as it remains in range. Think car, smartwatch, a generic USB dongle in a home or office PC, etc. -- the phone will only lock down when it "walks away" out of signal range of one of these trusted Bluetooth devices. [However, I've deactivated this built-in feature for a paid app called SkipLock, which does the same, but with WiFi, too, and it works extremely well.]
Oh... face unlock makes a reappearance, too. I actually used that a bit on the Gnex.
I can't post this review without mentioning the all-important connectivity. The radios are great -- both 4G & wifi.
- In my basement, where I've struggled to pull a 3G signal on the Gnex, I maintained a 4G connection on the Maxx, which allowed me to download apps (initial phone setup) while watching an HD video on YouTube
- On the main floor of the house, where my signal would flip between 3G and 4G on the Gnex, the Maxx operates decidedly in 4G territory
- At work, one room in the office far removed from the wifi antenna would consistently go to zero bars (yet, frustratingly, not lose it completely and therefore would not switch over to the strong 4G signal), I now have at least one wifi bar accompanied by a usable flow of data
- Overall, switching between wifi and 4G on the margins seems improved vs. what I had before, though even with "ignore weak wifi connections" checked, the Maxx at times seems indecisive about switching from one to the other. If I have one wifi bar that's trickling data, and a 3-bar 4G signal available, the choice should be obvious
- No problem with Bluetooth connections; I'm stoked that I now have full integration with my Ford's Sync system, with artist/track tagging from Pandora, and read-out-loud messaging with canned replies
- Voice call quality overall is excellent. This is one of Motorola's strong suits, I hear. I'm impressed.
Do you remember the iPhone 4's "death grip" problem? It seems that in marginal 4G areas (like that signal-quashing basement I mentioned), turning the Droid Maxx to landscape mode and holding it with both hands causes it to show a drop of 5 to 10 dBm off the signal strength meter (Settings > More > Mobile Networks > Network Type and Strength). If I'm already in the (low strength) -115 to -120 range, this results in me completely losing 3G and 4G connectivity. Releasing one hand brings the signal back to life. Where my 4G signal is strong, the signal drop is there, but my connection remains intact.
I've taken GPS accuracy for granted for a few years, so I was surprised to notice the Maxx's sense of direction may be slightly off. I use Google Nav frequently, and on a couple of occasions, the Maxx seemed to think I strayed off course onto the streets vs. getting on the freeway on-ramp, or exited when I really stayed on the highway, and as such gives me a fast re-route and impossible directions. It (well, Google Nav) then quickly corrects itself. I'd chock this up to accepted errors in compacted urban driving environments, except that the Gnex, previous Garmin devices, and Ford GPS simply don't exhibit this behavior. It would only be a problem if I already screwed up and missed a turn, but this nevertheless results in confusing instructions. Though other than those relatively minor blips, location setting is fast and mostly accurate, even in many indoor settings.
Another point to mention: Heat. My Galaxy Nexus often ran hot. When it did, I knew it was busy with something that was burning through the battery. This phone has run even hotter, both times in the car plugged in. The first was just downloading apps, the second was also running Nav with the screen on the whole time. But I've yet to see it run this hot outside of the car, and in fact, in the car running Nav but not plugged in, and not downloading apps, is was perfectly cool (and only lost 4% of the charge over about 20 minutes of Nav + screen-on time). So I'm guessing the heat comes from the 4G radio and processor working overtime switching cell sites, transferring data, and unpacking / installing applications, though again, this isn't the case when it's doing those same tasks sitting still in the house (and on 4G).
Check back. I'm sure I'll have some more detail to add to this already too-long review as I get to know this phone, particularly with respect to battery life, application compatibility problems & successes, and more observations on the radio switching & possible "death grip" issue.
But in summary, I'm sticking with my title -- this phone may have some issues here and there, and it may not be the fastest/biggest/most beautiful/polished specimen out there this late summer and fall, but in my opinion it's the first suitable contender to supersede the Samsung Galaxy Nexus, and betters that phone in a number of key areas. I have a great deal of confidence in Motorola at this time -- both in their tie to Google, and their strong affiliation with VZW. Thankfully, if you're tied to Verizon, you've suddenly got a few good choices after a long drought.
93 of 96 people found the following review helpful.
By Brian M.
Like the first reviewer here on Amazon, I was moving from the Samsung Galaxy Nexus to...something with a battery that lasted more than 8 hours. Overall, I liked the GNex, but I had gotten to the point where I had to charge the phone mid-day even if I hadn't taken the "darn" thing out of my pocket. And sometimes it got HOT in my pocket, again even though I hadn't pushed a single button. I had a total of four batteries for the phone because if I was traveling, I could easily go through three in a day.
I had not intended to pick up Droid Maxx on release day. I figured I would wait and see what the reviews were like, but I stopped by the store anyway to check it out. And I was hooked. BTW, Motorola Migrate is awesome. It would be even better if it also put on the same apps you had on the old phone, but moving my pictures and music with my contacts was a big bonus.
Battery was issue #1 and I knew that it couldn't get much better. My wife has the iPhone 4S and both my boys have Droid Razr Maxx phones. All those phones are pretty good when it comes to battery life. I hate the iPhone because I don't find it easy to use and Siri is an idiot compared to Google.
Anyway, I immediately went on a trip to Washington DC with the new phone and despite HEAVY usage pretty much all day long, I still had 32% battery at the end of that first long day (it is my work station on the road). The next two days were even better since I wasn't downloading so many apps. BTW, the Moto rep was in the store when I got the phone and talking to both the rep and the technical specialist, they twisted my arm to get the wireless charger. I don't think I will ever go back. It is supposed to be the best charging method and you don't have wear and tear on the charging port. It is really sweet!
I love the screen. Despite the fact that phone is nearly the same size as my GNex, the screen is larger. It is clear and I don't have any issue with the colors. I let the phone auto-adjust the screen brightness to save battery and it works well. I am not a screen purist, so others may disagree.
We routinely spend weekends in a area that ranges between one bar of 3G down to no reception. My GNex would be dead in about three hours while it struggled to get a signal. The Maxx had 62% battery at the end of the long day.
Signal reception is excellent. Like I said in our trip to the sticks, the other phones in our party had little or no signal. The Maxx had better reception than all other phones. The GNex always had a very weak signal (often zero G) in my office, while the Maxx has three bars of 4G.
Call quality has been excellent. There is a tiny bit of hiss when the other party is talking, but otherwise there is no background noise at all. I've not got the best hearing in the world, but I can hear the other party quite well.
The final battery test was at work. If I had minimal phone use during the day, my GNex would be at 10% battery by 7pm, sometimes less (even with a higher capacity battery I purchased at Amazon). After a full day at work, the Maxx was at 82% battery. That sealed the deal for me!
114 of 121 people found the following review helpful.
By G. Frank
This phone integrates elements designed by Google/Motorola and Verizon. I can definitely see which company has its act together and which does not. (hint: VZW should stick to building networks)
+ Battery life is truly amazing, and is actually as advertised. 2 days without recharging. Moto has done really well. This is by FAR the biggest selling point of the phone - and it's a very important one. It's as transformative to the phone's usefulness as broadband was to computers.
+ The wifi and LTE radios are much better than my wife's iPhone 5. Cleaner switching between multiple 2.4G and 5G access points throughout the house, and better rural LTE reception. Also amazingly, the LTE radio doesn't drain the battery at the pace other phones seem to experience.
+ The 720p AMOLED screen is great, contrary to what others say. I can't see pixels on even the smallest text. It's bright enough in daylight, and can go to a blacker black than others I've owned.
+ The ROM is pretty close to stock, with the exception of Verizon stuff (see below).
+ The voice control is wonderful. I can say "OK google now, play a song by Adele", even in the presence of background car noise while driving, and without touching a thing it'll start Spotify and play Adele. (I don't like the Google Play Music stock app but it lets you select which app is used for auto audio play).
+ The UI is buttery smooth irrespective of apparent CPU load. Finally, an Android phone as responsive as an iPhone.
+ The case and screen feel good to touch and hold. I won't be (voluntarily) testing how strong the Kevlar is, but it looks solid. The phone overall is bit too wide to hold comfortably, particularly with the nav button on the lower left which causes one's thumb to have to really reach for any backup action on a web page, for example.
+ Motorola has free live human tech support for this phone for any questions. People on web chat, backed up with good searchable documentation. Very responsive, minimal waiting.
- It's full of Verizon crapware. NFL football, VZW Navigator, VZW Backup Assistant Plus, VZW Tones, etc. These can be disabled in most cases (except Backup Assistant Plus), but cannot be uninstalled, at least with the stock ROM. Backup Assistant Plus crashed the phone repeatedly to the degree that I had to do a complete factory reset - 3 hours after having got the phone. Seriously, when will VZW learn that their apps suck and if people want them they can install them themselves. This is by far the most negative aspect of the phone and I nearly returned it because of this. There are Amazon apps also installed into the ROM by default but I don't mind these - I'm an enthusiastic Amazon customer so I'd have installed them anyway, and their apps actually function, in contrast to Verizon's.
- Even though it has NFC, Verizon has again blocked Google Wallet. They haven't provided an alternative because their Isis service hasn't been launched yet. So they are shutting off the market till THEY are ready. Shouldn't there be an antitrust case about this? I find it preposterous. I should be the one deciding what service I use to pay with my money, not Verizon. If their Isis service is compelling when it's launched, I'll use it. But don't block me from using a service that is running now, that I like, and that is supported by a device that I paid for in full. All this does is to make me distrust Verizon.
- The Miracast screen sharing and "Droid Zap" file sharing apps that are hyped in the ads are gimmicks. Miracast sucks anyway, Google Chromeplay is better and I can't see why they didn't opt for that. Droid Zap (a simple file sharing technology) requires a receiving phone also of the Motorola persuasion, so that's unlikely to be useful to most people.
- The back is not removable (probably to accommodate the battery shape required for its amazing capacity). So you can't keep spare batteries for long business trips, but you won't have to. There is no SDcard slot. But it's got 32GB built in so that's OK for most uses. Frankly I'd rather have the battery capacity.
- Brightness for the navigation buttons cannot be changed. They're permanently bright, even if the screen is dimmed, so these act as an involuntary flashlight shining in your eyes when you watch a movie, for example. Brightness control apps like Lux cannot control them either. You have to root, which I don't want to do with a new phone (and there aren't ROMs out yet that can use the voice control anyway).
- The presence of special features such as always-awake voice control via that custom low-power chip means that this phone will probably not have that many custom ROMs written for it in the future. At least not ones that include all of the phone's nice features. Which means that one would rely on Verizon for ROM updates - and they have a terrible track record for updates. The Verizon Galaxy Nexus "toro" phone for example lagged 4 releases behind Google, despite their promises that it would stay up to date with Android releases as a Nexus phone. I don't trust them to update this phone competently so I have to be happy with the ROM being static the way it is on release day, even though Google will continue to release improvements to Android.
Tidak ada komentar:
Posting Komentar