this post was submitted on 05 Apr 2025

61 points (94.2% liked)

Android

18793 readers

97 users here now

The new home of /r/Android on Lemmy and the Fediverse!

Android news, reviews, tips, and discussions about rooting, tutorials, and apps.

💡Content Philosophy:

Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.

Support, technical, or app related questions belong in: !askandroid@lemdro.id

For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id

💬Matrix Chat

💬Telegram channels / chats

📰Our communities below

Rules

Stay on topic: All posts should be related to the Android OS or ecosystem.
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.
No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.
No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities

Lemmy App List

See thread

Chat and More

founded 2 years ago

MODERATORS

ijeff@lemdro.id

ladfrombrad@lemdro.id

Paradox@lemdro.id

multimoon@lemdro.id

mikestevens@lemdro.id

Devgard@lemmy.world

limerod@reddthat.com

Netrunner@lemdro.id

Android 16 has a new trick to speed up app installation (www.androidauthority.com)

submitted 1 day ago* (last edited 1 day ago) by henfredemars@infosec.pub to c/android@lemdro.id

17 comments fedilink hide all child comments

Android 16 now supports cloud compilation, a new feature that could speed up new app installs.
The goal of cloud compilation is to avoid running the dex2oat tool during app installations by offloading compilation to the cloud.
Dex2oat takes an APK file and generates app artifact files that the Android Runtime loads. Depending on the device and the amount of code to compile, this could take some time.

It looks like the ART (Android Runtime) JIT is playing an increasingly less important role with time.

Friendly reminder that the cloud is just someone else's computer.

top 17 comments

sorted by: hot top controversial new old

[–] space_iio@sopuli.xyz 4 points 21 hours ago

It's an interesting trick because it makes me ponder: why would google do this?

Pre-compiling on the server means spending compute resources that are not free on something that was free before. In other words: cost. Why would google incur a cost on something that is non-user marketable or even perceptible? Were there really that many users complaining about how long it took to install x random app? Would google do this out of the kindness of their hearts?

So here's my best theory of why they're doing this: **Automatic installing of apps / ads on the background. **

here's why I think that:

Google has a history of trying this in-between state of app/website with "instant apps". Instant apps were never really "instant" though and they never really took off.
There are already several full screen ads for dopaming-hacking games that are partially interactive. It wouldn't take much to jump into a "pass the first level to skip the ad" kind of mechanic instead of "watch 20 seconds of this video to skip the ad" The limiting factor is how quickly does the ad install on your device.
Xiaomi and other Chinese companies have demonstrated how lucrative auto-installed crapware is. If one assumes that the concept generates revenue, imagine the following pitch:
For $20 we'll highlight your app on the play store
For $200 we'll show 20 full screen ads on 1000 users
For $2000 we'll pre-install the app on 1000 users from May 1st to June 1st

[–] MaXimus421@lemmy.world 22 points 1 day ago (2 children)

Without actually reading anything other than the title of the article, which I should prolly do, I'm gonna make this comment anyway.

What apps are you installing that take more than 30 secs?

[–] skullgiver@popplesburger.hilciferous.nl 3 points 23 hours ago (1 children)

I quite regularly see installation stall on older and cheaper phones. One single app install is fine, but when five or ten apps update all at once the phone becomes sluggish for minutes.

With Android consisting mostly of what, four instruction sets, this problem should've been prevented years ago in my opinion. Precompile for the most common platforms, leave the current slow processes for instruction sets nobody uses in practice, like MIPS and RISC-V.

[–] MaXimus421@lemmy.world 1 points 22 hours ago (1 children)

Well that's a issue, for sure.

I absolutely NEVER allow Google Play to just update my apps when it wants to. That's insane. That would be constantly updating all day everyday. There is no need for daily software updates. There is no need for weekly updates. It's borderline ridiculous.

One can argue "but muh security" all they like and go right ahead and do it if you need that validation in your life but when 10 apps are in que for an update 24/7 around the clock it's almost suspicious.

[–] skullgiver@popplesburger.hilciferous.nl 1 points 22 hours ago (1 children)

I have a lot of apps on my phone. Several government and banking apps require to be updated at least weekly or they're locked out for security reasons. Sure I could interrupt my 2FA login flow to update the app (assuming I have fast Internet available) but why bother? Google Play should be updating those things in the background while the phone charges. Same with F-Droid, though that's buggy and gets stuck all the time.

My Android devices are nothing compared to my Linux installs, anyway.

[–] MaXimus421@lemmy.world 1 points 22 hours ago

Sure, banking and work related apps. Set those for auto-update.

The rest, I'd manually do it monthly.

[–] limerod@reddthat.com 7 points 1 day ago (1 children)

You should've read the article. In an ideal world every device phone gets this process done in seconds. But, we don't and not everyone can afford to buy a decently powerful enough phone.

For those people, downloading the optimized odex files could be faster than creating them on device. Thanks to availability of super fast internet.

[–] MaXimus421@lemmy.world 4 points 1 day ago

Underpowered device or not, one thing that remains a constant is they will download a simple app very quickly, as long as the internet is there for it to do so.

So it really has nothing to do with the device but rather the internet speed.

[–] termaxima@jlai.lu 13 points 1 day ago (2 children)

Next time they’ll “invent” using a compiled language in the first place

[–] henfredemars@infosec.pub 14 points 1 day ago

Compiled isn't a property of a language but it describes the implementation. You can compile Python for example to native code using Cython, but it will need a Python runtime that is not much less work than running the code through the interpreter. There are C interpreters. Further, Java is compiled to native code and is being used in this fashion right now. You can also ship native C, C++, or Go binaries by using the Android Native Development Kit and that's exactly what most Android games do for performance.

Should Android not have started with Java? Even looking back, it's hard to say. Java helped Android get started quickly using a language many developers already knew how to use. We might have been discussing something other than Android if that wasn't the case. I cannot know.

[–] tyler@programming.dev 8 points 1 day ago

You can compile Java and Kotlin to native if you want. That’s not the issue here. Like OP responded to you, it’s not a property of the language but the implementation.

[–] Die4Ever@retrolemmy.com 6 points 1 day ago (1 children)

I can't believe it took them this long lol. There's like millions of whatever latest Samsung Galaxy phone, running that compilation locally millions of times is just a waste of global compute power and everyone's time, run it once in the cloud and cache it.

[–] henfredemars@infosec.pub 9 points 1 day ago* (last edited 1 day ago)

There are CPU and Android version differences, but it's not that hard a problem to solve. On-device bytecode->native compilation long struck me as a bit of a silly hack. Surely Google can cache build products.

[–] ilinamorato@lemmy.world -3 points 1 day ago (1 children)

Or we could give up on native apps and just use a browser for everything. In a lot of ways I wish we would.

[–] catloaf@lemm.ee 0 points 1 day ago (1 children)

That's not going to work too well when you're offline

[–] ilinamorato@lemmy.world 1 points 34 minutes ago* (last edited 33 minutes ago) (1 children)

Oh no? We've had browser storage and cached web apps for twenty years now. The technology exists and could be improved, if we stopped forcing everything to be a native app.

I mean, honestly, most "native" apps are webviews displaying cached content. Clearly we can make it happen, it just needs to be more discoverable and have smoother integration.

[–] catloaf@lemm.ee 1 points 22 minutes ago

So you're just reimplemenying the current model but with the extra layer of a browser in between. Installing a PWA is the same as installing a native app, except instead of running it directly you also have to have a browser installed to run it. It's adding a significant amount of complexity for no good reason. Browsers are huge attack targets.