-6
Honestly, I've just about had enough
(lemmy.zip)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 03 Aug 2025
-6 points (42.1% liked)
Firefox
20561 readers
2 users here now
/c/firefox
A place to discuss the news and latest developments on the open-source browser Firefox.
Rules
1. Adhere to the instance rules
2. Be kind to one another
3. Communicate in a civil manner
Reporting
If you would like to bring an issue to the moderators attention, please use the "Create Report" feature on the offending comment or post and it will be reviewed as time allows.
founded 5 years ago
MODERATORS
Okay, that's the problem. 4GB of RAM isn't enough for modern Android. I know because it's what I have on my tablet and it's bullshit, if I use certain apps, others in the background are force closed, etc. All I can say is that with some of the changes taking place with the switch to Jetpack Compose, Firefox is getting better in terms of a smaller memory footprint, but that's little consolation for you now and your urgent/present needs.
BTW, well done for using a private DNS for stopping the problem at the root.
I'm running Lineage OS and everything else runs fine. My RAM usage doesn't seem to be the problem, or at least not that I can tell. I've looked under the system monitor and developer options and seen no problems.
As I said, I have a low memory device so I'm talking from experience.
In fact Google itself says that devices with less than 6GB of RAM should be running Android Go rather than Android 16.
Honestly, devices designed to be obsolete are a pain for everyone. We need devices that are designed to be usable in a few years, that means shipping them with decent processors, memory and storage. By Android 17, the minimum memory requirement is likely to be 8GB and there's going to be a bunch of people wondering why some apps, the more complex ones like browsers, don't run smoother.
Maybe a solution is that Firefox starts serving older devices an ESR.