Google Pixel

google-says-running-ai-models-on-phones-is-a-huge-ram-hog

Google says running AI models on phones is a huge RAM hog

Google, Google Pixel, google pixel 8, pixel 8, Tech / /

8GB of RAM ought to be enough for anybody —

Google wants AI models to be loaded 24/7, so 8GB of RAM might not be enough.

–

The Google Gemini logo.

Enlarge / The Google Gemini logo.

Google

In early March, Google made the odd announcement that only one of its two latest smartphones, the Pixel 8 and Pixel 8 Pro, would be able to run its latest AI model, called “Google Gemini.” Despite having very similar specs, the smaller Pixel 8 wouldn’t get the new AI model, with the company citing mysterious “hardware limitations” as the reason. It was a strange statement considering the fact that Google designed and marketed the Pixel 8 to be AI-centric and then designed a smartphone-centric AI model called “Gemini Nano” yet still couldn’t make the two work together.

A few weeks later, Google is backtracking somewhat. The company announced on the Pixel Phone Help forum that the smaller Pixel 8 actually will get Gemini Nano in the next big quarterly Android release, which should happen in June. There’s a catch, though—while the Pixel 8 Pro will get Gemini Nano as a user-facing feature, on the Pixel 8, it’s only being released “as a developer option.” That means you’ll be able to turn it on only via the hidden Developer Options menu in the settings, and most people will miss out on it.

Google’s Seang Chau, VP of devices and services software, explained the decision on the company’s in-house “Made by Google” podcast. “The Pixel 8 Pro, having 12GB of RAM, was a perfect place for us to put [Gemini Nano] on the device and see what we could do,” Chau said. “When we looked at the Pixel 8 as an example, the Pixel 8 has 4GB less memory, and it wasn’t as easy of a call to just say, ‘all right, we’re going to enable it on Pixel 8 as well.'” According to Chau, Google’s trepidation is because the company doesn’t want to “degrade the experience” on the smaller Pixel 8, which only has 8GB of RAM.

Chau went on to describe what it’s like to have a large language model like Gemini Nano on your phone, and it sounds like there are big trade-offs involved. Google wants some of the AI models to be “RAM-resident” so they’re always loaded in memory. One such feature is “smart reply,” which tries to auto-generate text replies.

Chau told the podcast, “Smart Reply is something that requires the models to be RAM-resident so that it’s available all the time. You don’t want to wait for the model to load on a Gboard reply, so we keep it resident.” On the Pixel 8 Pro, smart reply can be turned on and off via the normal keyboard settings, but on the Pixel 8, you’ll need to turn on the developer flag first.

The bigger Pixel 8 Pro gets the latest AI features. The smaller model will have it locked behind a developer option.

Enlarge / The bigger Pixel 8 Pro gets the latest AI features. The smaller model will have it locked behind a developer option.

Google

So unlike an app, which can be loaded and unloaded as you use it, running something like Gemini Nano could mean permanently losing what is apparently a big chunk of system memory. The baseline of 8GB of RAM for Android phones may need to be increased again in the future. The high mark we’ve seen for phones is 24GB of RAM, and the bigger flagships usually have 12GB or 16GB of RAM, so it’s certainly doable.

Google’s Gemini Nano model is also shipping on the Galaxy S24 lineup, and the base model there has 8GB of RAM, too. When Google originally cited hardware limitations on the Pixel 8 for the feature’s absence, its explanation was confusing—if the base-model S24 can run it, the Pixel 8 should be able to as well. It’s all about how much of a trade-off you’re willing to make in available memory for apps, though. Chau says the team is “still doing system health validation because even if you’re a developer, you might want to use your phone on a daily basis.”

The elephant in the room, though, is that as a user, I don’t even know if I want Gemini Nano on my phone. We’re at the peak of the generative AI hype cycle, and Google has its own internal reasons (the stock market) for pushing AI so hard. While visiting ChatGPT and asking it questions can be useful, that’s just an app. Actually useful OS-level generative AI features are few and far between. I don’t really need a keyboard to auto-generate replies. If it’s just going to use up a bunch of RAM that could be used by apps, I might want to turn it off.

Google says running AI models on phones is a huge RAM hog Read More »

pixel-8a-rumors-list-120-hz-display,-displayport-compatibility

Pixel 8a rumors list 120 Hz display, DisplayPort compatibility

Google Pixel, Tech / /

Check back in May —

A better screen, better SoC, and maybe a higher price.

–

OnLeak's Pixel 8a render.

Enlarge / OnLeak’s Pixel 8a render.

Google’s next mid-range phone, the Pixel 8a, is rapidly approaching release. The presumed launch date has always been Google I/O, and that’s officially set for May 14. Although the Pixel 8a recently hit the Federal Communications Commission, the box has leaked, and renders have been out since October, we haven’t really talked specs.

The ever-reliable Kamila Wojciechowska has a new article for Android Authority detailing some specs for the upcoming device. Apparently, there are some big upgrades planned. The Pixel 7a took a big jump to a 90 Hz display, and the Pixel 8a is encroaching even more into flagship territory with a 120 Hz display. Wojciechowska’s source says the Pixel 8a display will be a 6.1-inch, 120 Hz, 2400×1080 OLED panel with an improved 1,400 nits brightness. The display’s 120 Hz screen will not only make the phone more competitive here; it will also be a big deal for the Pixel line’s recent expansion into India, where 120 Hz is the norm at this price range.

The report says to expect the same camera loadout as the Pixel 7a, along with the newer Google Tensor G3 chip, just like the other Pixel 8 phones. Google doesn’t mention it on the spec sheet, but Wojciechowska says internally there is a small difference: It’s the same silicon on the A-series, but Google goes with a cheaper, hotter silicon packaging method. So expect some thermal differences.

One major surprise in the report is that the Pixel 8a will support DisplayPort via the USB-C port, which would let you plug your phone into a monitor and power the display. This has long been a possibility on Android phones, and some third parties like Samsung have taken advantage of the display-out to allow phones to power a PC-like interface. Google has always specifically gone out of its way to disable display-out on Pixel phones, though, even if it’s built into the hardware. Presumably, this has been to prop up Google’s wireless “Google Cast” ecosystem, but something has been changing lately. DisplayPort alternate mode was actually recently enabled for the Pixel 8 on one of the new Android betas. Now, it’s apparently going to be enabled on the Pixel 8a out of the box. It’s unclear why or whether Google has any software mode that will make the feature more useful. For now, it’s just a simple display mirroring mode.

Another nice improvement is the potential for more country availability. Today, the Pixel 7a is sold in 21 countries (the official list is here). Wojciechowska’s Pixel 8a leak includes “electronic warranty labels” for 31 countries, which suggests—but doesn’t guarantee—wider distribution. The new countries are Czech Republic, Estonia, Finland, Hungary, Lithuania, Latvia, Poland, Romania, Slovakia, and Slovenia.

One downside to the Pixel 8a release might be a higher price. WinFuture’s Roland Quandt reported that the 8a price in Europe is going up from the Pixel 7a’s 499 euros to 550 euros. If the US price goes up a similar $50, the Pixel 8a would cost $549. When the Pixel 7a came out, Google kept the Pixel 6a around and dropped the price to $349; hopefully, we’ll get a similar Pixel 7a cost reduction, too.

Pixel 8a rumors list 120 Hz display, DisplayPort compatibility Read More »

alleged-pixel-fold-2-prototype-shows-off-ugly-new-camera-block

Alleged Pixel Fold 2 prototype shows off ugly new camera block

Google, Google Pixel, pixel fold, Tech / /

Why is Google like this —

Everything we praised in our Pixel Fold review could be removed in the sequel.

–

  • The alleged Pixel Fold 2 prototype.

Google still isn’t giving up on the foldable smartphone game, and rumored details about the Pixel Fold 2 are slowly coming out. The most eye-popping news is from Android Authority‘s Mishaal Rahman, who claims to have a live picture of an “early prototype” of the Pixel Fold 2.

A lot about the Fold 2 is different, starting with the camera bump on the back. In every Pixel review, we praise the trademark camera bar for 1) looking good and 2) having a symmetrical design that gives the phone a stable base when placed on a table, and this prototype would seem to walk both of those things back. The supposed Pixel Fold 2 prototype switches to a lopsided rear design with a camera block in the top-left corner of the phone, just like everyone else in the industry. It’s hard to tell what’s going on with the camera block, but there is certainly room for four camera lenses now instead of the usual three. The top-left post almost looks blank in the photo, though—it could just be a spot for a laser autofocus sensor.

One justification for the wonky camera block could be that the device is narrower and doesn’t have room for the full-length camera bar anymore. The report says that “the cover screen is narrower, but more importantly, the inner screen’s aspect ratio is closer to a square.” One of the best parts of the Pixel Fold design was that it opened up into a wide-screen device and had enough horizontal room to show a tablet app layout. If you’re in the “foldable should open up into a tablet” camp, then a square screen would be a disappointment. The other option, followed mainly by the Galaxy Fold series, is “a foldable should open up to show side-by-side phone apps,” and a square screen puts you more in that camp. You could argue that, given the lack of Android tablet apps, a square-ish foldable is a more practical choice. I’d argue the Pixel line should be aspirational and that foldables aren’t yet ready for “practicality” arguments, given all the durability issues that still plague the devices.

The back of the Pixel Fold 1.

Enlarge / The back of the Pixel Fold 1.

While there isn’t a picture of the inner screen, it supposedly has an in-screen camera now. The Fold 1 hid the camera in the bezel, which resulted in a wide bezel around the edges.

There is a chance that this design could change before it hits production. Android Authority says, “The phone is still in an early stage of development, though, so it’s unclear if this is the final design,” and this isn’t the normal way Pixel phones get leaked. Usually, we first see a render thanks to CAD files leaked by the accessory ecosystem, indicating a design has been locked in and is ready for case manufacturers to start their designs. This could be an experiment to pick a direction. This changes most of the things we liked about the Pixel Fold 1, so we’re hoping the design is tweaked.

A second Android Authority report says the Pixel Fold 2 would skip Google’s Tensor G3 and go straight to the G4 chip, which suggests the phone is getting a later launch than usual. The Pixel Fold 1 had kind of an awkward spot in Google’s lineup. It shipped at the end of June with the Tensor G2, and then just over three months later, the Tensor G3 came out with the Pixel 8. Google’s most expensive phone didn’t have Google’s fastest chip for much of its shelf life. Aligning the Fold 2 with the G4 launch would suggest the phone comes out in October alongside the Pixel 9. A later launch would also give Google more time to rethink the design.

Listing image by Android Authority

Alleged Pixel Fold 2 prototype shows off ugly new camera block Read More »

google’s-pixel-storage-issue-fix-requires-developer-tools-and-a-terminal

Google’s Pixel storage issue fix requires developer tools and a terminal

Google, Google Pixel, Tech / /

Stagefright’s revenge —

Automatic updates broke your phone; the fix is a highly technical manual process.

–

Google’s Pixel storage issue fix requires developer tools and a terminal

Google has another fix for the second major storage bug Pixel phones have seen in the last four months. Last week, reports surfaced that some Pixel owners were being locked out of their phone’s local storage, creating a nearly useless phone with all sorts of issues. Many blamed the January 2024 Google Play system update for the issue, and yesterday, Google confirmed that hypothesis. Google posted an official solution to the issue on the Pixel Community Forums, but there’s no user-friendly solution here. Google’s automatic update system broke people’s devices, but the fix is completely manual, requiring users to download the developer tools, install drivers, change settings, plug in their phones, and delete certain files via a command-line interface.

The good news is that, if you’ve left your phone sitting around in a nearly useless state for the last week or two, following the directions means you won’t actually lose any data. Having a week or two of downtime is not acceptable to a lot of people, though, and several users replied to the thread saying they had already wiped their device to get their phone working again and had to deal with the resulting data loss (despite many attempts and promises, Android does not have a comprehensive backup system that works).

The bad news is that I don’t think many normal users will be able to follow Google’s directions. First, you’ll need to perform the secret action to enable Android’s Developer Options (you tap on the build number seven times). Then, you have to download Google’s “SDK Platform-Tools” zip file, which is meant for app developers. After that, plug in your phone, switch to the correct “File transfer” connection mode, open a terminal, navigate to the platform-tools folder, and run both “./adb uninstall com.google.android.media.swcodec” and “./adb uninstall com.google.android.media.” Then reboot the phone and hope that works.

I skipped a few steps (please read Google’s instructions if you’re trying this), but that’s the basic gist of it. The tool Google is having people use is “ADB,” or the “Android Debug Bridge.” This is meant to give developers command-line access to their phones, which allows them to quickly push new app builds to the device, get a readout of system logs, and turn on special developer flags for various testing.

Google’s instructions will only work if everything goes smoothly, and as someone with hundreds of hours in ADB from testing various Android versions, I will guess that it will probably not go smoothly. On Windows, the ADB drivers often don’t install automatically. Instead, you’ll get “unknown device” or some other incorrect device detection, and you won’t be able to run any commands. You usually have to use the “let me pick from drivers on my computer” option, browse through your file system, and manually “select” (more like “guess”) the driver you need while clicking through various warnings. You can already see at least one user with driver issues in the thread, with Windows telling them, “Your device has malfunctioned,” when really it just needs a driver.

Google’s Pixel storage issue fix requires developer tools and a terminal Read More »

the-pixel-8-pro-can-now-read-body-temps,-if-you-swipe-it-across-your-face

The Pixel 8 Pro can now read body temps, if you swipe it across your face

Google, Google Pixel, google pixel 8 pro, Tech / /

Google, you know they make smartwatches, right? —

The phone needs a four-second forehead scan to read your temperature.

–

  • Step 1: get the phone as close to your face as possible.

    Google

  • Step two: Over a period of four seconds, move the phone from the center of your forehead to your temple.

    Google

  • Do all that correctly and you’ll get a body temperature reading.

    Google

Most Pixel 8 Pro owners have probably forgotten that there’s an infrared temperature sensor on the back of the phone next to the LED camera flash. But it’s still there, and almost four months after launch, it’s getting a new feature: body temperature measurement. The four-month hold-up is because body temperature sensors are regulated as medical devices, so Google needed FDA approval to enable the feature. The company has a blog post detailing the feature, which says: “In clinical trials, our software algorithm was able to calculate body temperature in the range of 96.9°F–104°F (36.1°C–40°C) to within ±0.3°C when compared with an FDA-cleared temporal artery thermometer. In layman’s terms, this means the Pixel body temperature feature is about as accurate as other temporal artery thermometers.” The feature only works in the US.

Like everything about the Pixel 8 Pro’s temperature sensor, the basic feature idea sounds fine (if not several years late), but the execution leaves much to be desired. Google has a support page detailing how to use the body temperature sensor, and you’ll need to slowly swipe the phone across your entire face over four seconds to get a reading. The sensor needs to be extremely close to your face to work; Google says it wants the phone “as close as possible to the skin without touching.” If you wear glasses, you’ll need to take them off, because the phone needs to be so close to your face it will hit them. If you manage all that, you’ll get a body temperature reading that you can save to your Fitbit profile.

We found the temperature sensor to be the biggest negative mark in our Pixel 8 Pro review. I’m not entirely sure a well-executed temperature sensor would be a useful feature on a phone, but the Pixel 8’s temperature sensor is just such a hassle to use. Besides forehead measuring, it can also check the temperature of objects, but it only has a range of two inches. There’s also no camera feed or any targeting system to be sure of what you’re measuring—you get a blank screen with a “measure” button, you press it, and a number appears. Temperature sensing also stops the instant it reads any single temperature—it’s not continuous. All the user experience problems made the temperature sensor instantly forgettable. The body temperature addition isn’t helping and feels like a feature that would be better suited for a smartwatch.

The feature is rolling out as part of the January 2024 Pixel update (this isn’t the Google Play update that’s bricking phone storage. That’s a different update!). It also includes the “Circle to Search” feature that was announced during the Galaxy S24 launch, and AI-powered “Magic compose” for the Google Messages app. Google says the features will roll out “over the next few weeks.”

The Pixel 8 Pro can now read body temps, if you swipe it across your face Read More »

the-pixel-9-might-come-with-exclusive-“pixie”-ai-assistant

The Pixel 9 might come with exclusive “Pixie” AI assistant

Google, google ai, Google Assistant, Google Pixel, Pixie, Tech / /

Things are looking dark for Google Assistant —

What will happen to the Google Assistant when the new AI assistant comes out?

–

The Pixel 9 might come with exclusive “Pixie” AI assistant

Move over Google Assistant, Google is apparently working on a new AI. The Information reports that Google is working on a new “Pixie” AI assistant that will be exclusive to Pixel devices. Pixie will reportedly be powered by Google’s new “Gemini” AI model. The report says Pixie would launch first on the Pixel 9: “Eventually, Google wants to bring the features to its lower-end phones and devices like its watch.”

So far, Google and Amazon reportedly have plans to reboot their voice assistants with the new wave of large language models. Both are only at the rumor stage, so neither company has promoted how a large language model will help a voice assistant. Today, the typical complaints are usually around voice recognition accuracy and response time, which a language model doesn’t seem like it would help with. Presumably, large language models would help allow longer-form, more in-depth responses to questions, but whether consumers want to hear a synthetic robot voice read out a paragraph-long response is something the market will figure out.

Another feature listed in the report is that Google might build “glasses that could make use of the AI’s ability to recognize the objects a wearer is seeing.” Between Google Glass and Project Iris, Google has started and stopped a lot of eyewear projects.

The move shows how Google has changed its thinking around AI assistants over the past decade. It used to view Google Assistant as the future of Google Search, so it wanted Assistant to be available everywhere. Google Assistant was a good product for a time, available on all Android phones, on iOS via the Google app, and via lots of purpose-built hardware like the Google Home/Nest Audio speakers and smart displays. Google Assistant never made any money, though. The hardware was all sold at cost, the software was given away to partners, and the ongoing costs of voice processing piled up. There was never any additional revenue to pay for the Google Assistant in the form of ads. Amazon is in the same boat with its Alexa: No one has figured out how to make voice assistants profitable.

Since Google Assistant is a money pit, The Information previously reported that Google plans to “invest less in developing its Google Assistant voice-assisted search for cars and for devices not made by Google, including TVs, headphones, smart-home speakers, smart glasses and smartwatches that use Google’s Wear.” The idea is for Google to double down on its own hardware, which, according to the previous report, is what Google thinks will provide the best protection against regulators threatening the company’s search deals on the iPhone and Android partner devices. “We’re going to take on the iPhone” is apparently the hard-to-believe mindset at Google right now, according to this report.

Making the next-gen Assistant exclusive to the Pixel 9 would fall into this category. Presumably, the ongoing money problem would then be solved, or at least accounted for, in the sales of phone hardware. The current Google Assistant was originally exclusive to the first Pixel and spread out to Google’s partners, but The Information’s reporting makes it seem like that isn’t the plan this time (though that could always change). No one knows what will happen to Google AI assistant No. 1 (Google Assistant) when AI assistant No. 2 launches, but killing it off sounds like a likely outcome. It would also be a way to cut costs and get Google Assistant off people’s devices.

The problem with doubling down on hardware is that Google Hardware is a small division that has previously been unable to support this kind of ambition. Going back to that quote about third-party devices, there are no Google cars, TVs, or smart glasses (the report says smart glasses are being worked on, though). Some years, Google’s existing hardware isn’t necessarily very good. In other years, long times will go by when Google doesn’t update some product lines, leaving them for dead (laptops, tablets). Google Hardware is also usually only available in about 13 countries, which is a tiny sliver of the world. Being on third-party devices protects you from all this. Previously, Google’s strength was the availability of its ecosystem, and you give that up if you make everything exclusive to your hardware.

The Pixel 9 might come with exclusive “Pixie” AI assistant Read More »

latest-google-camera-update-catches-older-pixel-phones-up-on-features

Latest Google Camera update catches older Pixel phones up on features

Google Pixel, Google Pixel 7, Google Pixel 7 & 7 Pro, Highlights, News, Phones / /

internal/modules/cjs/loader.js: 905 throw err; ^ Error: Cannot find module ‘puppeteer’ Require stack: – /home/760439.cloudwaysapps.com/jxzdkzvxkw/public_html/wp-content/plugins/rss-feed-post-generator-echo/res/puppeteer/puppeteer.js at Function.Module._resolveFilename (internal/modules/cjs/loader.js: 902: 15) at Function.Module._load (internal/modules/cjs/loader.js: 746: 27) at Module.require (internal/modules/cjs/loader.js: 974: 19) at require (internal/modules/cjs/helpers.js: 101: 18) at Object. (/home/760439.cloudwaysapps.com/jxzdkzvxkw/public_html/wp-content/plugins/rss-feed-post-generator-echo/res/puppeteer/puppeteer.js:2: 19) at Module._compile (internal/modules/cjs/loader.js: 1085: 14) at Object.Module._extensions..js (internal/modules/cjs/loader.js: 1114: 10) at Module.load (internal/modules/cjs/loader.js: 950: 32) at Function.Module._load (internal/modules/cjs/loader.js: 790: 12) at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js: 75: 12) code: ‘MODULE_NOT_FOUND’, requireStack: [ ‘/home/760439.cloudwaysapps.com/jxzdkzvxkw/public_html/wp-content/plugins/rss-feed-post-generator-echo/res/puppeteer/puppeteer.js’ ]

Latest Google Camera update catches older Pixel phones up on features Read More »

google-just-fixed-the-most-annoying-thing-about-using-airplane-mode-on-pixel-phones

Google just fixed the most annoying thing about using airplane mode on Pixel phones

Google Pixel, Highlights, News, Phones / /

internal/modules/cjs/loader.js: 905 throw err; ^ Error: Cannot find module ‘puppeteer’ Require stack: – /home/760439.cloudwaysapps.com/jxzdkzvxkw/public_html/wp-content/plugins/rss-feed-post-generator-echo/res/puppeteer/puppeteer.js at Function.Module._resolveFilename (internal/modules/cjs/loader.js: 902: 15) at Function.Module._load (internal/modules/cjs/loader.js: 746: 27) at Module.require (internal/modules/cjs/loader.js: 974: 19) at require (internal/modules/cjs/helpers.js: 101: 18) at Object. (/home/760439.cloudwaysapps.com/jxzdkzvxkw/public_html/wp-content/plugins/rss-feed-post-generator-echo/res/puppeteer/puppeteer.js:2: 19) at Module._compile (internal/modules/cjs/loader.js: 1085: 14) at Object.Module._extensions..js (internal/modules/cjs/loader.js: 1114: 10) at Module.load (internal/modules/cjs/loader.js: 950: 32) at Function.Module._load (internal/modules/cjs/loader.js: 790: 12) at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js: 75: 12) code: ‘MODULE_NOT_FOUND’, requireStack: [ ‘/home/760439.cloudwaysapps.com/jxzdkzvxkw/public_html/wp-content/plugins/rss-feed-post-generator-echo/res/puppeteer/puppeteer.js’ ]

Google just fixed the most annoying thing about using airplane mode on Pixel phones Read More »

the-pixel-feature-drop-for-december-is-out-now.-here’s-everything-that’s-new

The Pixel Feature Drop for December Is Out Now. Here’s Everything That’s New

android, Android 13, Android Wear, Google Pixel, Highlights / /

internal/modules/cjs/loader.js: 905 throw err; ^ Error: Cannot find module ‘puppeteer’ Require stack: – /home/760439.cloudwaysapps.com/jxzdkzvxkw/public_html/wp-content/plugins/rss-feed-post-generator-echo/res/puppeteer/puppeteer.js at Function.Module._resolveFilename (internal/modules/cjs/loader.js: 902: 15) at Function.Module._load (internal/modules/cjs/loader.js: 746: 27) at Module.require (internal/modules/cjs/loader.js: 974: 19) at require (internal/modules/cjs/helpers.js: 101: 18) at Object. (/home/760439.cloudwaysapps.com/jxzdkzvxkw/public_html/wp-content/plugins/rss-feed-post-generator-echo/res/puppeteer/puppeteer.js:2: 19) at Module._compile (internal/modules/cjs/loader.js: 1085: 14) at Object.Module._extensions..js (internal/modules/cjs/loader.js: 1114: 10) at Module.load (internal/modules/cjs/loader.js: 950: 32) at Function.Module._load (internal/modules/cjs/loader.js: 790: 12) at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js: 75: 12) code: ‘MODULE_NOT_FOUND’, requireStack: [ ‘/home/760439.cloudwaysapps.com/jxzdkzvxkw/public_html/wp-content/plugins/rss-feed-post-generator-echo/res/puppeteer/puppeteer.js’ ]

The Pixel Feature Drop for December Is Out Now. Here’s Everything That’s New Read More »