Resultados 1 a 4 de 4
  1. #1
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010

    [EN] Google Leak Reveals Massive Pixel 2 Cancellation

    Gordon Kelly
    Jun 13, 2017

    Goodbye ‘Muskie’ we hardly knew you. Yes, there is major news out of Google land today as multiple sources are claiming Google has cancelled plans for its much anticipated Google Pixel XL sequel…

    The ever reliable Android Police delivers the news explaining:

    “Based on information from three separate sources, we are now confident that Google has shelved plans to release one of its upcoming Pixel phones. The device, codenamed 'muskie’, was intended to succeed the Pixel XL.”

    So sure is Android Police that it said “We rate this information 9 out of 10 on our rumor confidence scale” and confirmed “We have corroborated this story with several sources we deem reliable”. Historically the site’s track record is excellent.

    Given the Pixel XL was the best of the two Pixel handsets Google debuted last year, this development should be terrible news, but there could be an upside.


  2. #2
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010

    Play Store downloads show Google Pixel sales limited to 1 million units

    The Pixel is seen as Google's answer to the iPhone, but considering Apple sells 40 to 50 million iPhones in a quarter, Google has some catching up to do.

    Ron Amadeo

    The Google Pixel, Google's first totally self-branded phone, launched about eight months ago. Google declared itself a smartphone OEM and jumped into the world of manufacturing, but while the company's software and optimizations have made the phone a critical success, how have the sales numbers been?

    Unlike just about every hardware manufacturer on Earth, Google doesn't share official sales numbers for the Pixel phones, choosing to bundle the income under Alphabet's "Other Revenues" during earnings reports. We do have one very solid signal for Pixel sales, though: the Play Store, which shows install numbers for apps. If there was an app that was exclusive and install-by-default on the Pixel phones, like say, the Pixel Launcher, the install number would basically be the number of sold activated phones.

    This calculation is complicated by the fact that Google Play doesn't show exact install numbers; it shows installs in "tiers" like "100,000-500,000." So most of the time, we won't have an exact Pixel sales number—except when the Pixel Launcher crosses from one download tier to another. So guess what just happened? The Pixel Launcher just crossed into the "1,000,000-5,000,000" install tier (you can see some third-party tracking sites, like AppBrain, still have it listed at 500,000). So for this one moment in history, eight months after launch, we can say Google finally sold a million Pixel phones.

    The Play Store device targeting ensures no one other than Pixel owners can download the Pixel Launcher, and the install count doesn't include sideloading. The most popular sideloading site, APKMirror, has more than 1.3 million downloads on just a single version of the Pixel Launcher, so we know that sideloaders actually outnumber legitimate Pixel Launcher users. There are some statistically insignificant root shenanigans you could pull to download the Pixel Launcher from the Play Store on a non-Pixel device, but there is no way the number of sold Pixels is higher than 1 million units at this point in time.

    The Pixel is seen as Google's answer to the iPhone, but considering Apple sells 40 to 50 million iPhones in a quarter, Google has some catching up to do.

    We've reached out to Google for a comment and will update this piece if we get a response.

    Update: Here's a few more tidbits on how this correlates to actual users. Pre-installed apps do count in Google Play's install numbers, otherwise you'd never get apps like Google Talkback, a niche accessibility service, over the billion install mark. They only count once per account, regardless of how many times you update or wipe the phone. The Play Store version of the Pixel launcher also doesn't work with the Pixel C.

  3. #3
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010

    Google's getting serious about building its own iPhone

    The Android maker has decided that building its own version of the iPhone is the best way to compete with the iPhone.

    Vlad Savov
    Jun 14, 2017

    To compete with Apple, Google has to become Apple.

    When Google curtailed its Nexus program last year in favor of the Pixel, many commentators dismissed that as merely a rebranding exercise to make the latest thing feel fresh. I was in the minority that bought into Google's promise of a fundamentally different approach that would signal a direct challenge to Apple's iPhone, but the Pixel was still just the beginning. What we're seeing in recent times, in the ever-swirling rumor mill and through Google's hiring of new engineers, indicates the depth of Google's commitment to taking on Apple at its own game.

    I wrote about this at length back in October: the big difference for Apple isn't just software, hardware, or customer service, it's all of those combined. Apple's unmatched strength is in the integration of all the important aspects that go toward building up a satisfying user experience, and it's long been true that the only company that could hope to match Apple was Google, owing to its dominance on the software front with the Android OS. The Pixel showed that Google was willing and able to produce a premium, uniquely differentiated phone (the Pixel camera remains unmatched, many months later), but it obviously wasn't the finished product of Google's grander project.

    Apple's hardware lead is built atop a tight control, often monopolization, of its component supply chain. That's exactly where Google looks to be headed, with recent rumors and leaks indicating that the Mountain View company is working hard to secure a reliable source of OLED displays for a presumed Pixel successor with minimal screen bezels in the same vein as the Samsung Galaxy S8 and LG G6. That's why indications of an LG-produced Google phone for later this year make so much sense: it's not impossible for Google to still use HTC as its manufacturing partner and source panels from LG Display (which is nominally independent from LG Electronics), but it's more complicated than just going all-in with the Korean supplier.

    Just like Apple, Google commands vast reserves of cash that it can deploy to help smooth out its supply deals, and that's exactly what its reported investment in LG Display is building toward. If the original Pixel was a trial run to test out what it's like to source and assemble all your own components, Google's big lesson from it was that demand for its phones will be high — and disappointment in the event of shortages would be even higher. Unlike Apple, Google doesn't yet have the promise of enormous unit sales to dangle as a carrot in front of potential suppliers, but that is liable to change dramatically with this year's Pixel, which would presumably enjoy much wider distribution and marketing than the original.

    Google is literally hiring Apple engineers to build its mobile processors

    Two things were revealed yesterday: one is that Google is designing its own system on a chip (SoC) for future mobile devices, and the other is that the lead architect for that project is a man named Manu Gulati, who, until very recently, had been a senior engineer at Apple. Both of these are massive developments, showing that Google won't be content until it has maximum control over every aspect of its smartphone — exactly the same goal that Apple pursues with every new generation of iPhone — and furthermore underlining the level of ambition by poaching away someone who would surely have needed a lot of incentive to leave a job at Apple.

    The SoC is the processing heart that powers the vast majority of functions of any modern smartphone, tablet, or smart speaker. Qualcomm's Snapdragon is the most famous and widely used example, Samsung's Exynos is a comparable competitor, and Apple's A series of SoCs are the current gold standard, delivering unmatched performance and efficiency. If Google is determined to not be dependent on another company's whims or fortunes, having its own SoC is an essential part of its future business as a mobile hardware vendor.

    The current Pixel is built around the Snapdragon 821 chip — its speed and feature-rich architecture contribute to the excellent Pixel camera — but the instructive example for Google to beware is the Snapdragon 810. Qualcomm had a ton of overheating issues with that piece of silicon, sufficient for Samsung to skip using that chip at all in its Galaxy S6, and Google can't afford to find itself in a similar situation with the Snapdragon 845 or whatever there is down the line. So Google is now building its own SoC, as fully evidenced by its litany of job listings attesting to that ambition.

    Integration always wins

    Beside freeing itself of the unpredictability of relying on other companies for critical components, Google's effort to control all the hardware inside its future devices will help it create more tailored, custom solutions. For instance, look at the way that notifications on the Samsung Galaxy S8 are signaled with a pulse of blue light tracing its way around the edges of its almost bezel-less display — that's nowhere near as impressive on a phone without the S8's sleek design. The coherence and synergy that can be drawn from hardware and software designers working in concert is best demonstrated by Apple, naturally, but I can envision future Google devices that have custom processing modules specifically to power Google's magical camera algorithms. How much better and faster would the Pixel be if its internal components were each designed for specific tasks instead of built to fulfill a generic set of requirements?

    We don't know what difference a Google SoC would make to future Pixel phones, but it's obvious that Google is determined to find out. It's probably safe to presume Google is doing similar work to lock down its supply chain for less glamorous parts, like batteries and vibration engines and so on, and not all of it will be ready to debut by this year's end when the Pixel successor comes out. In fact, it's a practical certainty that Google's mobile processor is years away from making its debut in a consumer product, but that just goes to underline that Google is in this for the long haul. The Android maker has decided that building its own version of the iPhone is the best way to compete with the iPhone.

  4. #4
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010

    Google poaches Apple employee in move to build its own processors

    Todd Haselton
    13 Jun 2017

    It looks like Google is getting awful serious about designing its own smartphone processors.

    The company recently hired an engineer named Manu Gulati from Apple, according to Variety. Gulati has at least 15 Apple patents related to chip design under his belt and will be key in Google's plan to build its own processors, Variety said.

    Apple currently builds its own smartphone processors but Google does not.

    Apple's newest A10X chips, for example, are built-in house instead of by companies like Intel or Qualcomm. Qualcomm currently supplies its Snapdragon processor for Google's Pixel and Pixel XL smartphones.

    Gulati's LinkedIn profile says he's now Google's "lead SOC architect." SoC stands for "system on a chip." Gulati worked at Apple for almost 8 years as a micro-architect and has also been employed by Broadcom and AMD.

    If Google begins building processors in house, like Apple, it would potentially cut down on Google's reliance on Qualcomm. That may not be a big hit for Qualcomm, at least not yet, since the company still provides millions of its Snapdragon processors to smartphone makers such as Samsung, LG, HTC and others.

    Still, this is a significant trend in the smartphone market. Other firms, such as Huawei and Samsung, have also started to build chips in-house, allowing them to rely less on potential supply restraints from outside parties.

    A spokesperson for Apple was not immediately available for comment. Google confirmed Manu is now working for Google but declined to provide additional details.

Permissões de Postagem

  • Você não pode iniciar novos tópicos
  • Você não pode enviar respostas
  • Você não pode enviar anexos
  • Você não pode editar suas mensagens