6 points

Damn. I wonder if a custom OS remove this “feature”…

permalink
report
reply
11 points
*

If apps and the OS weren’t such ram/storage hogs, this would be plenty. Like does the Home Depot app really need half a gig or more? 🙄

permalink
report
reply
8 points

id imagine some apps are just running on electron or some microbrowser, so theyre fuctionally browsers and come with some of the memory penalties from running with said sdks. not many conpanies want to design something from the bottom up.

permalink
report
parent
reply
5 points

It’s shitty coding and the app stores should reject this garbage and tell the dev to ship it as a web app. If you’re going to ship an entire web browser with every app, then what’s the point of it being an app?

See also apps that bundle twenty different frameworks and then use maybe one or two percent of what’s bundled. 🙄

permalink
report
parent
reply
5 points

You most likely wouldn’t be shipping an entire web browser with the app. You would use the Webview component (or similar) which just uses the Android System WebView system app that should already be on the phone.

permalink
report
parent
reply
10 points

I presume if you run a custom ROM it would not reserve the RAM in this way

permalink
report
reply
3 points

Not sure, it could be allocated in the firmware, kind of like integrated GPUs on desktop/laptop processors. For example my Amd 6800HS laptop with 16GB RAM has only 14 available because the GPU takes up 2GB (but I can change it in BIOS)

permalink
report
parent
reply
6 points

I was going to say NBD, 3GB is a decent bit for the OS, but 13 should be fine for anything you want on your phone.

But most of it is for shitty LLM nonsense? Fuck that.

permalink
report
reply
14 points
*
Deleted by creator
permalink
report
reply
4 points

The huge amount of RAM on Android in general is less about supporting a single hungry app and more about keeping as many apps as possible in memory so that you can multitask between them without any of them losing their state. If one app manages to eat most of the memory, then it’s already too little for the intended experience.

Also the memory is supposed to be enough for at least the 7 years this phone will be supported for - that’s plenty of time for apps memory footprint to grow.

Maybe I’m biased by always having used devices with RAM size in the lower end (which is always also coupled by a not-so-great CPU so when you do run out of memory and the system starts killing apps you want to multitask between, you’re going to notice it that much more), but I’ll always take more RAM in a device that might survive a decade with a couple of battery swaps.

permalink
report
parent
reply
1 point
*
Deleted by creator
permalink
report
parent
reply
2 points

apps that are programmed by a 13 year old that wants to scam people.

That’s a weird way to spell “project manager who doesn’t let developers waste time making efficient apps when they could just add more marketable features”. The competition won’t hesitate, and users will always flock to apps with more features and nicer UI over optimizations.

People need to learn how to close apps.

If you have enough RAM, there’s no reason to - it’s not like they are actually running and consuming CPU cycles. If you don’t have enough RAM, you also don’t need to - Android will do it for you. My phone with 3 GB of RAM could barely handle maps and a browser at once, so there were plenty of times when the map app restarted and recentered on my current position when I came back from checking the website of whatever company I looked at.

The recent apps screen is really just a history of open apps, with some of them maybe still in memory, and with some opaque mechanism for automatically removing old entries. You can reboot your phone and the apps will still be there with a screenshot of their last state. Doesn’t mean they will get back to that state when you switch to them.

permalink
report
parent
reply

Google Pixel

!googlepixel@lemdro.id

Create post

The home of /r/GooglePixel on Lemmy and the Fediverse!

The place for everything related to Google Pixel devices, including news, reviews, tips, tutorials, rooting, and app discussions.

!googlepixel@lemdro.id

Rules

  1. Stay on topic: all posts should be related to Google Pixel devices.
  2. No offensive/low-effort content: avoid posting offensive or low-effort content that does not contribute positively to the community.
  3. No self-promotional spam: active community members are welcome to post their apps but should also participate in comments and discussions. Please do not post links to your own website, YouTube channel, or blog.
  4. No reposts/rehosted content: whenever possible, submit original sources. If the original source is not available in English, you may provide a translation. Reposts of the same content are not allowed.
  5. No editorializing titles: when submitting articles, do not change the titles. You may add the author’s name if it is relevant.
  6. No piracy: sharing or discussing pirated content is strictly prohibited.
  7. No unauthorized polls/bots/giveaways: please do not create unauthorized polls, use bots, or organize giveaways without proper authorization.
  8. No affiliate links: posting affiliate links is not allowed.

Community stats

  • 85

    Monthly active users

  • 252

    Posts

  • 515

    Comments

Community moderators