Slashdot Mirror
Google's Nexus 4, 7, 10 Strategy: Openness At All Costs
MrSeb writes "There have been plenty of rumors about how the Nexus program was going to grow and change with this year's announcement. Now that we have all the details, it looks like almost none of them were right. There is no Nexus certification program, and the dream of multiple Nexus phones seems well and truly dead. What we do have is a range of device sizes with the Nexus 4, Nexus 7, and Nexus 10. However, the Nexus program has been altered in one important way: we know what Nexus means now. There can no longer be any doubt: a Nexus device is about openness first and foremost. Last year the technology sphere was busily discussing whether or not the Verizon Galaxy Nexus was a 'true' Nexus device. This year we have an answer: a Nexus controlled by a carrier is no Nexus. Rather than get in bed with Verizon, Sprint, or AT&T to produce an LTE version of the Nexus 4, we have HSPA+ only. Even the new Nexus 7 with mobile data is limited to this enhanced 3G standard. And then there's the pricing: The super high-resolution (2560×1600) Nexus 10 tablet starts at just $399; The Nexus 7 is dropping in price to $199 for a 16GB tablet; The Nexus 4 with 16GB of storage is going to sell for $349, exactly the same as the old Galaxy Nexus was until yesterday. To put this into perspective, the LG Optimus G, which the Nexus 4 is based on, sells for $550 without subsidy. Google is pushing the idea of openness with the Nexus devices, but it's not an entirely altruistic endeavor. By giving us cheap and open devices, Google is making sure it's in control — not the carriers. That's better for the consumers, but it's also better for Google."
HSPA+ is just as 4G as LTE is, according to Wikipedia (which is to say, it was decided that while they weren't technically 4G they advanced 3G enough to be called 4G).
What advantages does LTE have over HSPA+ that would make the latter "lame" by comparison?
Several reasons:
1) It's supposed to guide carriers/mfgs away from partitioning the memory on their phones (apps/music/etc). The Nexus standard is for a single volume that the user can fill with whatever they like. Remember, the Nexus line is a "do as I do" standard.
2) Mixing EXT and FAT is silly, since the benefits of EXT are lost when users shift their stuff to the FAT SD card. Since most people think FAT is what you are when you're overweight, and EXT is a trim level on a Chevy truck, they don't realize what they're giving up (like filesystem security) by moving apps and data to their SD card.
3) Forcing MTP mode means the phone can keep it's entire filesystem mounted without having to hand it over to whatever computer it's plugged in to, as well as keeping control (permissions) over the actual data on/written to the disk. It also means that when you trip and yank the USB cable out in the middle of copying files over, you haven't corrupted your data.
4) It saves on hardware (cost, thickness, etc)
5) Fewer interoperability headaches. Not all SD cards are created equal, and someone trying to run a read/write intensive app off their slow-as-dirt cheap SD may blame poor performance on "my piece of shit phone"
When I first got my Galaxy Nexus, I too was concerned about the storage limitations. After all, I wanted to put my entire music library on my phone... never mind that my entire library is literally weeks of playtime, or that there are apps perfectly capable of streaming my own media off a home server for me on demand (with the caveat/concession that I am normally away from WiFi for no more than 30 minutes), or that if I *really* wanted to go gung-ho with music for some reason I had a perfectly capable MP3 player that was even better than my phone (battery life, etc) for that purpose. Nope, I wanted to put the whole thing on my phone because it would make me feel warm and fuzzy inside. The reality is that I don't need to do that, I just wanted to. Once I shifted my expectations to match my reality, it ceased to bother me.
I compare the lack of an SD card to the "range anxiety" you see in EV cars. It bothers us that it's not available even though the majority of trips are well within an EV's range. Once you prove to yourself that you don't really need it (and can work around it in case you do), it's not such a big deal.
> What has openness got to do with a micro sd slot!?
Internal SPI expansion bus that's trivially easy to program directly with minimal ceremony?
As an embedded hardware guy, I totally get warm fuzzies from SPI. It's just about the easiest low-ceremony bus on planet earth to use, and in a pinch you can even bitbang it with minimal effort. I know there's no room inside a microSD card for useful hardware thicker than a silicon wafer, but you could always use a fake microSD card connected to a ribbon cable to feed hardware built into a thicker replacement back.
I think the screen size is a reflection of the market. People are migrating towards phones with larger screens. For example, I'm guess that the Samsung S2 and S3 owe their success, at least in part to their large crisp screens. I'm not saying that 4.7" hasn't gone a little too far for the average user, but I bet that screen looks a lot prettier than the competition.
Personally, I have huge hands, so my next phone will be humongous. I avoid texting because I can't help but hit like 5 characters at once. I'm even considering the monstrously large Note 2.
Forcing MTP mode means the phone can keep it's entire filesystem mounted without having to hand it over to whatever computer it's plugged in to, as well as keeping control (permissions) over the actual data on/written to the disk. It also means that when you trip and yank the USB cable out in the middle of copying files over, you haven't corrupted your data.
Of course the big drawback is that MTP was originally a Windows-only protocol that was only later standardized by the USB group and support is very flaky on any Linux-based OS I've used. You're no longer guaranteed that you can plug the device in to any host and have it recognized.
You also can't edit files directly using MTP; you must edit it locally then re-upload in its entirety back to the device.