Google Unveils The New Nexus 7 Android Tablet
techcrunch.com
techcrunch.com
The Nexus 7 is a joy to use. It's light, the screen is great - it's quick (I got my daughter a Kindle Fire and sometimes you can see that device straining a bit: eg. load times on Despicable Me (I know! I know!) The Nexus 7 battery is great and I love getting the very latest Android s/w pushed to the device. It's a great device for consuming media: books, audio, video. Stock Android is a nice reference platform. Can't wait for Jelly Bean 4.3 real soon now. I would recommend a Nexus 7 to anyone considering a tablet on a budget. I just have to figure out how I can justify splashing out on the 2013 Nexus 7 :) I know I must sound like a total shill but I really was surprised at how far Android has come and how polished and optimized it is on the Nexus 7.
That is all :)
And yes, when I picked up and handled my Nex 7 for the first time I thought to myself "this is an iPad mini". I was absolutely flabbergasted that they could push a device of this quality out at the quasi-magical $250 price point.
Then Apple came out with a real iPad mini, and I'm still glad I got the Nex instead. Top-notch in terms of performance, ease of use, portability and clean design.
But the next tablet I get will have to be an iPad or Surface Pro, because I make music and all the tablet-based music software worth talking about is on iOS. Google largely ignored the creative market in developing Android and made no effort to address concerns about latency or similar issues. The only software of note to appear on Android in the last 2 years is Image Line's well-respected Fruity Loops audio/MIDI sequencer, but I'm so jaded that I can't be bothered to install it.
Result? A huge, thriving ecosystem of interoperable audio & MIDI apps on the iPad, with zero incentive to switch back to Android any time in the foreseeable future. Android becomes identified as a consumer-only platform, iOS as a producer platform. The number of musical artists that use an iPad is tiny compared to the overall consumer market, but artists tend to be vocal about the tools they use and are delighted to be seen using them, which I think has about 100x the PR value of any given commercial depicting actors having a good time with their consumer device.
For people who want to tinker with audio on Android, it's possible to swap AudioFlinger with PulseAudio[1] for lower latency (20ms vs 176ms)[2], but so far you have to build and flash your own AOSP image, so it's not exactly plug and play.
[1]: http://www.freedesktop.org/wiki/Software/PulseAudio/Ports/An...
[2]: http://arunraghavan.net/2012/01/pulseaudio-vs-audioflinger-f...
I think you're going to see more people doing this, with the Nexus devices and the Transformer tablet. Maybe I've overestimated the popularity of the ASUS-branded hardware, but I have always had the best of luck with my TF-101 getting current ROMs and updates from the third-party vendors like TeamEOS.
Now that TeamEOS is gone, there's a void, so more people are probably going to learn to build the ROMs. There are even people picking up the torch[1] with the TeamEOS source code, taking their branches and picking up where they left off.
I know as consumers, we all want vendors to support their products... but as members of Open Source community, I see it's irresponsible to depend on them exclusively for forward motion, progress, and updates, and for freedom's sake it shouldn't be an impossible proposition to compile and flash your own ROM. (Just think if you bought an x86 computer with Ubuntu or Fedora and you couldn't re-OS it.)
I hope in time that Android gets the same amount of attention because those apps will eventually bolster the Linux ecosystem in general. It's great to hear that Fruity Loops is available for Android, I remember a Mac-head showing me an early version of it like 15 years ago! Ouch, I feel old.
I have tried tons of different roms on the Galaxy Nexus and the factory roms on the One X, One, and S4, but they just don't have the iOS level of smooth.
Android is great, I wouldn't trade back to iOS for the world, but I've just learned to accept the hiccups, lag and odd behavior that hurts my "suspension of belief" (or whatever term describes the ability to believe that we're actually 'moving' things by touching a screen).
I should try it on my Nexus S that has become sluggish as hell (and I've tried different custom roms)
There are some optimizations that iOS can make that Android can't, but the gnex in particular I think is slightly crippled.
[1] https://android.googlesource.com/platform/dalvik/+/9907ca3cb...
If I didn't need an android tablet, I probably would not have one.
I can't speak to battery or speed as I haven't had a lot of hands-on time with the Mini, but I will note that the N7's slimmer aspect ratio means it fits nicely in a pocket, while the iPad Mini just plain doesn't.
I have both devices and I can comfortably say Nexus 7's display is much worse. Images appear washed out, it's not as bright as the iPad mini, it has worse viewing angles etc.
It could be contrast ratio, colour gamut, brightness, subpixel quality, viewing angles, reflectivity of coating, susceptibility to oils/fingerprints...
(I haven't used either, I'm just saying)
The iPad Mini Retina will likely be the perfect small tablet for most users.
I find that with the ipad mini viewing angles actually do seem kind of important, because—unlike a phone—I very often use the ipad mini without holding it, whether sitting on a table, on my lap, or propped up against something while I watch a video. The result is that one doesn't have nearly the same easy control over viewing angle one has when hand-holding a device...
Android indeed has a "bigger" learning curve which make people more efficient in a short time for doing things with their phone/tablet.
Easy example, Tasker, Gravity screen, NFC and Autovoice...
I can't stand seeing pixels, so the iPad Mini is not an option, but I'm also not willing to spend money on a tablet with lousy color. Hopefully Google gets it right this time.
[1] http://www.displaymate.com/news.html#8 [2] http://news.cnet.com/8301-1035_3-57479059-94/expert-claims-g...
You're also missing the fact that until this update, the Nexus 7 16GBs were only $199, which is a whopping 40% difference.
I have noticed it seems to be feeling slower over time, though not so much so that I've made an effort to look into it, particularly when starting larger apps or updating apps in the background while doing something else.
http://www.howtogeek.com/164106/why-is-my-nexus-7-so-slow-8-...
#1 was a step backwards, but so was horrible performance. Now things are running smoothly.
Mostly, I noticed jerkiness and lag scrolling web pages. I'm not sure what I'll do now. Between that and a huge stuck pixel that won't go away, I regret buying this Nexus 7, which was my second one after the screen broke on my first.
These things you really need to try before you buy.
There's another thread here about the potential slowdown issue. Same'll happen to a Mac or PC I reckon after a while. I've not noticed it. When you think about it Android tablets are pretty new so they haven't been used to their full extent, nor to the end of their lifespan.
Also really happy to see the LTE. I think having LTE on the go is crucial, and a 7-8" tablet is the right place to put it. Much of the time I use my iPad as an LTE hotspot (it get way better battery life in that use-case than any stand-alone LTE hotspot or tethered phone).
Question, however, about the need for LTE on a tablet. Assuming you have your phone with you normally, why not just use your phone's hotspot feature to get the tablet online? Or, turn on bluetooth tethering if you want to have your tablet online all the time, with minimal power drain.
Also, I'm not good at recharging my devices and I really like it that I can use tethering heavily on my Mini for several days to a week between recharges. I already kill my phone battery every day as it is--depending on it even more for tethering or surfing in line at the Starbucks would mean mid-day recharging.
I tether via WiFi rather than paying extra for a tablet with its own cell radio (and paying extra for a separate data account for it) - I carry an "emergency" battery that is enough to cover those occasions when I need to use it long enough for it to kill the phone's battery (though others may find that inconvenient).
I think one reason consumers prefer devices with their own modems is (intentional?) UI friction which makes "tethering" less convenient. In stock Android you cannot configure a device such that it will "use wireless if available, tether if not," which is what you really want to happen. It is possible to achieve something like this with third party apps, however.
* Force the phone to enable bluetooth tethering on every boot with Bluetooth Auto Tether: https://play.google.com/store/apps/details?id=de.refluxa.and...
* Install Bluetooth Auto Connect on the tablet, which allows for the tablet to connect to the phone automatically: https://play.google.com/store/apps/details?id=de.refluxa.and...
* Use an automation app (I prefer Llama https://play.google.com/store/apps/details?id=de.refluxa.and... ) to configure Bluetooth Auto Connect to happen when (e.g.) "screen on" and "wireless not connected", and configure it to disable Bluetooth Auto connect when "screen off" or "wireless connected." Add small delays here to avoid race conditions.
It all seems needlessly complicated, but the end result is that the device will tether if it is awake and cannot find wireless, and it will disconnect from the phone when it goes to sleep or when it does find wireless, which is exactly what I want.
Having both Nexus 7s and an iPad, I would say that I hugely favour the former for watching movies, and they are essentially equal when browsing the web (speaking purely of the aspect ratios. Safari on the iPad is a dramatically better web browser, so for that reason I usually favor the iPad). Personal opinion, of course.
The average use also favors using the web over watching movies and videos, which works better in the 4:3 format.
The entire computer and laptop market has overwhelmingly endorsed 16:10 and 16:9, and most content correspondingly adapted. This notion that the web was built for 4:3, or is somehow superior on it, seemed to rise out of nowhere the moment Apple happened to announce the iPad as 4:3.
Regarding the Pixel -- a device with shockingly little deployment (and whose form was driven by a lot more than the idea screen size) -- 3:2 is 1.5:1. The iPad is 1.33:1. 16:10 is 1.6:1. Meaning the Pixel is significantly closer to the ratio of the Nexus 7 than the iPad. So what now? What does that prove?
Now as to the web being "mainly vertical", the single and only place where that is true are a few spartan text blogs. Content sites are a rich cacaphony of horizontally distributed content -- Wikipedia is informational sidebars of all sorts, as an example. I find those experiences dramatically better on wider screens.
Anyway, how can you say websites are more horizontal than vertical? On any kind if site, you are much more likely to have to scroll vertically to get what you want. That means increasing visible vertical space improves your experience more than adding horizontal space will.
Edit: I run my web browser in the left half of my 1920x1200 screens because when I maximize them I feel like the window is much too empty. So there's room for preferences, of course. But I think most content on the web is taller than it is wide.
I agree with the point that content providers adapt but it's not a case of what's right for one type of content, it's what's good for one type of content on a specific device type, possibly in a specific situation.
(Worth noting that Apple certainly don't believe 4:3 is some universal "right" ratio - the iPhone 5 is 16:9 as are Macs, 4:3 is only the aspect ratio for the iPad)
It’s amazing – these two have been pending for more than 4 years. Google hasn’t cared to even comment on the former while thousands of users beg them to: https://code.google.com/p/android/issues/detail?id=82
Low latency audio is "fixed" on the Android side, it needs better device support though. Apps need to actually support the fast path as well, which I don't think many do.
http://www.youtube.com/watch?v=d3kfEeMZ65c
I don't know if the new Nexus 7 supports the low latency audio path, though. But Android itself does have low latency audio, it's a device-specific thing though.
(OK, most wireless chipsets can simulate Infrastructure-mode networks these days, so not supporting Ad-Hoc mode doesn't help much in that department.)
There are a number of use-cases reported on that bug: https://code.google.com/p/android/issues/detail?id=82
Less powerful than GPU in iPad 3 (or iPad 2 in some benchmarks); but of course, it's got a smaller display too.
Samsung will soon have a 3200x1800 display in their ATIV Book 9 Plus.
But it just boggles my mind that that's about it in terms of laptops with decent screens.
I use Linux, and don't want to pay the extra cash for the Apple logo, so that's not really a good option. The Google thing looks interesting, but the local disk is really limited.
Specifically, although I am not bothered by the exteriors of an early-2011 iPad and a mid-2011 Mac mini, I returned a mid-2013 Macbook Air because it made the hair on the back of my neck stand up to touch its aluminum-alloy exterior.
About when was the iPad that you hate made?
My email is in my profile. If you give me a way to contact you, I would update you on any new information I get about this issue.
Looks like I'll have to pick one of these up.
(And, I know what the comments are going to be but the Playbook is an underrated device IMO. For the price, it has some decent specs (for it's age) and as a browser/ereader it's great, but the fact that they dropped OS10 after promising it has me peeved.)
Asus is about to start shipping their new MeMo HD 7" for ~$150. On paper, it's somewhere between the 2012 and 2013 Nexus 7.
I'm on an unlimited plan with Verizon, if I could run multiple devices on the same plan without a premium I'd be highly inclined toward the LTE model.
Link: http://developer.android.com/guide/topics/data/install-locat...
Nexus 4 - 4.7" phone
Nexus 7 - 7" tablet
Nexus 10 - 10.1" tablet
"One year later, the Nexus 7 has gone from the best to worst tablet I’ve ever owned"
http://androidandme.com/2013/06/opinions/one-year-later-the-...
Otherwise back everything up (this is not that hard at all) and do a reset. If you navigate to Google Play on a PC you'll see a list of your devices and have a history of all the apps you ever installed and you can reinstall them remotely from the PC. It's cool to see them pushed from the PC through the cloud to your mobile device. Just make sure to back up your contacts (should be automatic by Google I've found, don't ask me how ... but anyway you can make a backup to be sure to be sure by going into contacts and playing around), your SMSes (I use SMS backup app for this to do this automatically), any pics (though you should be using dropbox to do this automatically) and so on.
I'm not saying that this should be happening. It's crap that it is. Maybe Android is the new Windows. Quick ... defrag!
Yeah... About that... Google removed that feature.
[1] - http://rootzwiki.com/topic/28677-rom-jdx-v143-formerly-jelly... [2] - http://rootzwiki.com/topic/36706-romaosp42271213-shiny-ota-l...
(both those links are specifically for the Verizon GN. If you have a different one, you'd have to look for different builds.)
I guess my point is that "the issue" might not be storage deterioration (for which you'd be inclined to blame Google, or Samsung). Perhaps the ROM you're using (sent to you by your carrier, right?) is the issue. If the custom ROM solves your problem, you'll both a) learn that the issue wasn't storage degradation, and b) make your phone usable. Again, if you're considering getting a new phone anyway (because it's slow), it's worth a shot. And it's kinda fun to hack into your phone, anyway, right?
I think it's because I freed lots of space, as I noticed this after I removed most of the apps (before a factory reset or anything else). It might work for you too.
This is a trimming issue of the internal memory.
- Root the tablet (if you haven't already).
- Install lagfix (free) from the market or crosscompile fstrim and run it on your sd card.
Your tablet / phone will be fast again.
There is no action that can be taken on an "sdcard" partition on a GNex. It has to be done on /data.
If you've rooted your device, you have several things to try to see what is going on exactly. One key thing to look at would be the 'dmesg' output. If there are a lot of read/write errors to the internal eMMC storage, then that probably indicates a hardware problem. If that isn't happening, and 'logcat' also doesn't show anything suspicious, then maybe do a full backup (like with Titanium Backup). After that, you can try to clear the caches and see if that helps. If you're still having problems, then maybe it is time to try a full factory wipe, which will erase all your data.
Wi-Fi should be included with every model IMHO.
They aren't even keeping pace with Samsung's IR camera gesture support or HTC's all metal body and TV remote capability we're seeing on phones.
Still, this is a better showing of "cheap but good" than the original N7...I'm rather disappointed in mine and it's been relegated to being the Jukebox in my house
As to the RAM being "paltry", compared to what? A desktop? There is no non-Intel tablet that I know of with more RAM. And of course it's shared memory, as it is on every comparable device -- again, are you comparing this with Haswell laptops or something?
The Nexus tablet is a very inexpensive device (as is the Nexus 4, for that matter). It is not intended to push any boundaries, but is to bring the advantages that other, much more expensive products brought to market to the low-end.
Apparently great screen, very decent SoC, dual cameras...$229. Yeah, it's a pretty good entrant.
I've been quite disappointed in my Nexus 7s as well, though half of that I attribute to nvidia -- they are the kings of overpromising and underdelivering. It also has suffered the well known flash degradation, and hopefully Asus/Google have learned something from that debacle.
Other than the storage capacity (and even then I want to know what's usable cough Surface cough not what's on the hardware) just tell me what I can do with it and make it work well, the rest is frankly marketing bullshit.