ITT people who don't understand that generative ML models for imagery take up TB of active memory and TFLOPs of compute to process.
Google Pixel
The World's Google Pixel community!
This community is for lemmings to gather and discuss all things related to the Google Pixel phone and other related hardware. Feel free to ask questions, seek advice, and engage in discussions around the Pixel and its ecosystem.
We ask you to be polite when addressing others and respect Lemmy.world's rules.
NSFW content is not allowed and will immediately get you banned.
It also goes without saying that self-promotion of any nature and referral links are not allowed. When in doubt, contact the mod team first.
Also, please, no politics.
For more general Android discussions, see [email protected].
This community is not in any way affiliated with Google. If you are looking for customer support regarding your Pixel phone, look here instead: https://support.google.com/pixelphone/
That's wrong. You can do it on your home PC with stable diffusion.
And a lot of those require models that are multiple Gigabytes in size that then need to be loaded into memory and are processed on a high end video card that would generate enough heat to ruin your phones battery if they could somehow shrink it to fit inside a phone. This just isn't feasible on phones yet. Is it technically possible today? Yes, absolutely. Are the tradeoffs worth it? Not for the average person.
You can for example run some upscaling models on your phone just fine (I mentioned the SuperImage app in the photography tips megathread). Yes the most powerful and memory-hungry models will need more RAM than what your phone can offer but it's a bit misleading if Google doesn't say that those are being run on the cloud.
So much for the brilliant AI-specialized Tensor processor
It's basically just a mediocre processor that offloads interesting things to the mothership.
Yep. What a joke. Goes to show you that google could Make these pixel features available to all android devices if they wanted to.
This really doesn't surprise me.
Yeah, obviously. The storage and compute required to actually run these AI generative models is absolutely massive, how would that fit in a phone?
They aught to just slap a phone in a 3090
Fuuuuck that.
Why ?
Because it's a privacy nightmare.
Using Google products has always been a "privacy nightmare" - it's not like this is some mega open source phone or anything it's literally Google's flagship. Is this really surprising? Playing with fire gets you burned.
Googles phones are the easiest to de-google surprisingly
And if you do, they won't upload your stuff to the cloud anymore.
But if you use Google's OS and services, you really shouldn't be surprised they upload your data to Google.
I’m not surprised at all, I’ve been trying to not use googles services for years
And if you do, they won't upload your stuff to the cloud anymore.
Wait - is that praise or criticism?
Even ignoring all the privacy issues with that, it's kinda shit to unnecessarily lose phone features when you've got no signal
Isn't that kinda the dream. We have devices that remote the os. So we get a super powerful device that keeps getting updated and upgraded. We just need a receiver ?
Isn't that what we want. Can reduce down the bulk on devices. Just a slab with battery, screen and modem and soc that can power the remote application ?
Sometimes that's what people dream about. On the other hand that hybrid cloud model is giving up the last remnants of computing autonomy and control over devices we own.
What I would like is something that gives me the framework to host my own server-side computations at home.
That would be, if Google wasn't constantly killing things that didn't do good enough. Especially given how expensive generative AI can be to run remotely. Just look at what happened with Stadia
Also, it just feels disappointing. Ever since chatGPT, they've been pouring near infinite budget into stuff like this by hiring the top talent, and working them to the latest hours of the night. And the best that they could come up with for the pixel 8 is feeding it data from the cloud.
And I can't even really believe the whole "consumer hardware isn't powerful enough" thing given that there's quite a few ARM processors, Apple especially, That's been able to build consumer hardware capable of performing generative AI (I've personally been able to run stable, diffusion and whisper on my M1 MacBook). Maybe not at the scale or quality of the cloud, but still capable of doing so regardless.
Google has a bad track record there, but they wouldn't kill things that were working on their end. What % of the population do you think even knew was Stadia ever was?
Especially given how expensive generative AI can be to run remotely.
Great point, except it proves the opposite of what you meant by it.
Aside from the fact the phones dont even remotely have the resources to do anything like that without sucking their batteries dry and over heating in record time, do you seriously think given the insane workload, hardware dedication, network bandwidth, and that many more people on the payroll, that Google is (choosing) to just do that to be nice? If they could offload all that to the users they would in a second! Even if the mindset is that its about the data mining, they could simply do that after the fact and send themselves the end result, and save themselves hundreds of millions in equipment, power needs, physical buildings, cooling costs and the never ending hardware costs. Ever work in a data center? Ever see how much shit breaks every single day even when everything's going as planned? Its insane.
I mean it sucks for offline situations or for actions that need very good latency.
But the phone's battery would be happier if the processing is not done locally.
For some things I prefer to do the stuff locally, for other things on the cloud.
Some cloud Vs local examples I'm thinking about:
-
For example (example not related to the Pixel) if I'm generating an image with stable diffusion at home I prefer to use my RX 6800 on my private local Linux rather than a cloud computer with a subscription. But if I had to do the same on a mobile phone with tiny processing power and battery capacity I'd prefer to do it on the cloud.
-
(Another non AI example): for gaming, I prefer to run things natively. At least until it is possible to stream a game without added latency. Obviously I don't play games on a phone.
-
Another example (Google photos): I would prefer to connect Google photos to a local NAS server at home, and "own the storage on premise" and then pay a lower fee to Google photos for the extra services it brings. Browsing, face and objects recognition, etc. But this is not an option. With this I would be able invest on my own storage, even if I had dozens of gigabytes in 4K60FPS videos.
This just strengthens the argument to install privacy/security first operating systems like CalyxOS and GrapheneOS. I don't was a phone that's more a service subscription than it is hardware. I have the pixel 8 and didn't get the pro due to the offloading to Google servers for some "features".
Just waiting for GrapheneOS to be released for the 8... Until then, I'm sitting uncomfortable knowing my phone is uploading telemetry to Google servers...
I've bitten the bullet, replaced my Redmi 13 to a Pixel 7 + GrapheneOS - because the MIUI spyware and google spyware are just too much... I still don't get why , as an owner of a phone , I'm not the owner of the phone.
You're very much the owner of the phone, which is why you were able to put Graphene on it.
I can't put grapheneOS on my p7 since at&t sells phones with locked bootloaders. I didn't know this when I bought it or I wouldn't have bought it.
Well, yes, however, installing GrapheneOS may mean not having access to "features" which were part of the marketing for the phone... Which begs the question around what are you paying for? To me, it's like you are paying for a product and also for services. Although the p8 and p8p both have 7 years of support, I wonder if that extends to features and services that are cloud based?
Fair enough when its out of context, but a privacy advocate doesnt but a Pixel for anything thats touted as a Google feature, what they're paying for, is the hardware that ironically allows them to most effectively cut ties with Google as a whole.
People who dont do that could care less how its happening, only that it is, and they their battery lasts.
Yea, Google features are very anti privacy, it's funny how it's still one of the most secure phones on the market. I got the pixel 8 for the fact its going to be supported with GrapheneOS, and get 7 years of security updates.
Currently using GrapheneOS on my 8 Pro, and the experience has been extremely smooth so far.
Yea I was tempted for a second to get it, but there was a comment that it "should" be possible to upgrade to the released version when available, I don't want to have to mess around in the event that it's not. So I'm just going to wait a week or so.
People didn't think this was the case already?
When some company praises the ground braking AI capability of a new SoC they have been built, you might get the idea that it's doing these tasks on said SoC.
Why would you think otherwise?
A list of what this phone does offline and what not would be great.
And?