this post was submitted on 20 Nov 2023
89 points (86.8% liked)

Android

27947 readers
247 users here now

DROID DOES

Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.

The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:

Rules


1. All posts must be relevant to Android devices/operating system.


2. Posts cannot be illegal or NSFW material.


3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.


4. Non-whitelisted bots will be banned.


5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.


6. Memes are not allowed to be posts, but are allowed in the comments.


7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.


8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.


Community Resources:


We are Android girls*,

In our Lemmy.world.

The back is plastic,

It's fantastic.

*Well, not just girls: people of all gender identities are welcomed here.


Our Partner Communities:

!android@lemmy.ml


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] AlmightySnoo@lemmy.world 22 points 1 year ago* (last edited 1 year ago) (2 children)

I think the problem is the conflicting goals that Google has with that chip. They want the chip to be able to run AI stuff locally with the Edge TPU ASIC that it includes, but at the same time Google also wants to make money by having Pixel devices offload AI tasks to the cloud. Google can't reconcile these two goals.

[–] Kushan@lemmy.world 9 points 1 year ago (2 children)

I don't think they're opposing goals. Google does not make more money from a task running in its cloud than on its devices, if anything that costs them more money.

[–] AlmightySnoo@lemmy.world 1 points 1 year ago* (last edited 1 year ago)

I think it's realistic to assume that Google is going to impose quotas on those "free" AI features that are running on the cloud right now and have people pay for more quota. It makes no economic sense for Google to keep offering those compute services for free. Remember Google Colab? Started completely free with V100 and A100 GPUs, now you have to pay to just keep using a simple T4 GPU without interruption.

[–] nottheengineer@feddit.de 5 points 1 year ago (1 children)

There's a solution: Charge the customer once for the hardware and then add a monthly fee to be able to use all of it. Sony and Microsoft have great success with that.

[–] 520@kbin.social 8 points 1 year ago (1 children)

Do that and an unlock hack will swiftly follow.

[–] crystal@feddit.de 5 points 1 year ago (1 children)
[–] 520@kbin.social 3 points 1 year ago* (last edited 1 year ago)

Lol you wut?

Do you know how expensive conventional AI setups are? An unlocked AI chip on a phone would fast replace nVidia cards in the AI scene for low level researchers, especially those dealing with sensitive data for whom cloud access is not viable.

My laptop is $1500, and is just about viable for this kind of stuff. It took it three days non-stop to create a trading model for ~22 stocks, processing 10 years worth of data for each.

Now maybe it doesn't mean much for the consumer, that's true. It means a hell of a lot for small time developers though, including those developing the apps consumers use.