Your phone is trying to keep your battery alive. The lower the specs of the phone, then the more aggressive the OS is.
No, apps closing between switches is not a matter of battery, it’s a core feature of Android related to the management of RAM. Whenever the OS needs more available RAM, the OS will close a backgrounded app to make those resources available. This is why it happens more frequently on low-end devices - these generally ship with less RAM.
Some misguided vendors will limit background execution in incorrect ways in the name of saving battery, but the general thing with apps living in background is a story of RAM.
Interestingly enough, apps are supposed to be built to cope with being closed down due to lack of RAM and then be restored seamlessly, but this is an art that is uncommonly done correctly in the Android development space. The OS support is there, though.
I mean, putting in a bit of thinking before you actually hit the keyboard can be an incredibly effective form of optimization, if you can get for example an O(n^2) down to an O(log n). You’ll even save time on not having to rework the thing later, and if you build on poor foundations, chances are you’ll stumble upon fundamental architectural challenges down the road, which can be extremely costly in terms of development time.
I don’t really know what you think LLMs has to do with this case, but just for reference - Google have been notorious in automated moderation on the Play Store since long before LLMs were a thing in general use, and they are also really bad when it comes to managing these processes once an automated moderation action has been made. Lots of devs get screwed this way.
Doesn’t quite seem to be out on Android yet, at least not in my market. I could pre-register and have it download automatically when it’s out, though.
It didn’t list a price and said there was an in-app purchase, anyone know what that’s about? Will I be able to use the copy I bought for PC or what?
Anyway, this is great. Granted, I’ve been playing Balatro on mobile for many months already, but an officially supported version is even better.
Balatro University has some good guides if you’re looking to improve.
Consider the following:
One day we manage to reach the pinnacle of invention - we create the replicator from Star Trek. We can suddenly bring immense amounts of anything we want for everyone in the world, for very little energy (caveat: I don’t know enough about Star Trek lore to know this to be true).
Now, this machine would certainly make a whole lot of business models redundant - farming, factory work, you name it - they would all no longer be able to make a living doing what they did before this invention existed.
Now for the moral question - should the fact that this invention will harm certain groups’ way of life be considered enough of a motivation to prohibit the use of this invention? Despite the immense wealth we could bring upon the world?
Take a pause to form an opinion on the subject.
Now that you’ve formed an opinion on the replicator - consider that we already have replicators for all types of digital media. It can be infinitely replicated for trivial amounts of energy. Access to the library of all cataloged information in the world is merely a matter of bandwidth.
Now, should the fact that groups relying on copyright protection for their way of life be considered reason enough to prohibit the use of the information replicator?
To me, the answer is clear. The problem of artists, authors, actors, programmers and so on not being able to make money as easily without copyright protection does not warrant depriving the people of the world from access to the information replicator. What we should focus on is to find another model under which someone creating information can sustain themselves.
Google Tasks can also be good if you are willing to use a Google account. I’ve set up a bunch of recurring ones at regular intervals to stay on top of tasks that need to be completed throughout the day/week/month. I also like to be able to put a time on tasks, such that I get a notification at that time to be reminded of it.
That’s right. The art of correctly handling
savedInstanceState
is unfortunately not exactly well understood