Google Delays The Nexus Q To Make It “Better,” But Pre-Order Customers Get A Free Dev Unit

Chris Velazco is a mobile enthusiast and writer who studied English and Marketing at Rutgers University. Once upon a time, he was the news intern for MobileCrunch, and in between posts, he worked in wireless sales at Best Buy. After graduating, he returned to the new TechCrunch to as a full-time mobile writer. He counts advertising, running, musical theater,... ? Learn More

google-nexus-q,W-A-343306-13

Here’s hoping you weren’t planning on using one of Google’s Nexus Qs any time soon — the company has just revealed to pre-order customers that it has postponed the device’s consumer launch because users wanted more out of the curious little orb.

That said, Google’s tiny media streamer has been unceremoniously yanked from the Google Play store. All interested consumers can do now is give the company their email address for future updates on the situation, as there’s no word yet on when Google expects that full-blown launch to take place.

Thankfully, there’s a silver lining to be found here: anyone who already pre-ordered the Nexus Q will receive a developer unit (a.k.a. the existing device that Google gave out in droves at I/O) for free. Seeing how the developer device is exactly what those customers pre-ordered in the first place, I’d say they’re making out pretty nicely. Still, there are some intriguing new questions at play now — what exactly does Google plan to add to the little guy to make it more of a competitor in a space already crowded with arguably superior hardware?

An actual user interface would be a nice place to start; while the dev model connects to a television just fine, users have to select content for the Nexus Q to play from a wirelessly-connected Android device. Being able to call up YouTube videos and movies from the Google Play Store directly on the television screen (perhaps using those additional Android devices as remotes) could help the Nexus better hold its own against the Apple TV and the Boxee Box. It wouldn’t be a shock to see Google cram support for more media sources into the thing too — Netflix, Hulu, and the like would be great additions to a device that otherwise lives solely within Google’s content ecosystem.

Google is playing its cards close to its metaphorical vest, but for now here’s the email notice in full courtesy of Droid-Life:

We have an important update about your Nexus Q pre-order.

When we announced Nexus Q at Google I/O, we gave away devices to attendees for an early preview. The industrial design and hardware were met with great enthusiasm. We also heard initial feedback from users that they want Nexus Q to do even more than it does today. In response, we have decided to postpone the consumer launch of Nexus Q while we work on making it even better.

To thank you for your early interest, we’d like to extend the Nexus Q preview to our pre-order customers and send you a free device. If you had other items in your order, your credit card will be charged for those items only.

Your Nexus Q will be on its way soon and you will receive a notification and tracking number from Google Play when it ships.


View the original article here


This post was made using the Auto Blogging Software from WebMagnates.org This line will not appear when posts are made after activating the software to full version.
-

Comments

Post a Comment

Popular posts from this blog

scala - 'wrong top statement declaration' when using slick in IntelliJ -

Image
i'm porting project scala 2.9 2.10, therefore have use slick instead of scalaquery. i'm using slick 2.1.0 since supports ms access. according this tutorial , upgrade guide changed robs object class , added val robs : why error message wrong top statement declaration , how rid of it? edit: i'm new scala... according this question seems can't put val outside of methods or classes, right? code above directly in packge. right approach slick then? should move code in class or trait? according this changed val robs = tablequery[robs] to object robs extends tablequery(new robs(_)) {} . no warnings or errors anymore. :)
Read more

c# - DevExpress.Wpf.Grid.InfiniteGridSizeException was unhandled -

Image
when using devexpress, see error: devexpress.wpf.grid.infinitegridsizeexception unhandled message="by default, infinite grid height not allowed since grid rows rendered , hence grid work slowly. fix issue, should place grid container give finite height grid, or should manually specify grid's height or maxheight. note can avoid exception setting gridcontrol.allowinfinitegridsize static property true, in case grid run slowly." the problem dxgrid has infinite height. to fix, set height non-infinite. snoop absolutely invaluable this: if "height" xaml element infinite (i.e. 0 or nan ), can set using one of following: option 1: height="{binding path=actualheight, relativesource={relativesource mode=findancestor, ancestortype=uielement}}" option 2: verticalalignment="stretch" option 3: height="auto" hint: use verticalalignment="stretch" if child of grid <rowdefinition height=
Read more

PySide and Qt Properties: Connecting signals from Python to QML -

i trying run simple pyside appliccation design made in qml. call function in qml python in separated thread. i have following qml view: import qt 4.7 rectangle { visible: true width: 100; height: 100 color: "lightgrey" text { id: datestr objectname: "datestr" x: 10 y: 10 text: "init text" font.pixelsize: 12 function updatedata(text) { datestr.text = qstr(text) console.log("you said: " + text) } } } here application: some imports.... #!/usr/bin/python import sys import time pyside import qtdeclarative, qtcore pyside.qtgui import qapplication pyside.qtdeclarative import qdeclarativeview the qthread worker.... #worker thread class worker(qtcore.qthread): updateprogress = qtcore.signal(int) def __init__(self, child): qtcore.qthread.__init__(self) self.child = child def run(self):
Read more