undefined | Better HN

0 pointskaba01y ago0 comments

How are intents not scriptable? I have an app that can literally call any other intent, but I can even write a bash/python script and run it from Termux to execute whatever I want. Look up the `am` executable.

Re the “killing stuff” paragraph sounds like a memory size issue - frankly, in that case killing something is a better option than desktop linux’s tendency to just freeze the hell up. Just for reference, on a modern low-end samsung I had no such experience.

After 15 years: android’s activity life cycle doesn’t make them constantly save stuff — there is a pause and stop lifecycle events that are appropriate places for saves to happen. Android will attempt to gracefully stop applications, unlike desktop linux’s oom killers. And this model works exceedingly well, you just don’t even notice it, only when it occasionally couldn’t clear enough memory and has to resort to killing.

I haven’t tried doing backups recently, I believe that it is not as streamlined as it should.

0 comments

g-b-r1y ago

That's ONE intent, and not even between two apps...

Have you ever had to pipe more than two applications to operate on something (image, video, whatever)? Or actually, more than one, since in your solution one app is am, or your intent-calling app?

> Re the “killing stuff” paragraph sounds like a memory size issue

Whatever it is, how about asking what to do, instead of assuming that users only care about the foreground app? (I risk smashing my monitor every time I read that in the documentation)

> And this model works exceedingly well, you just don’t even notice it

Nope, I notice it all the time, since apps are more likely to get killed than let to gracefully stop, in my experience.

I heard that the latest Samsung One UI versions behave better, though

j / k navigate · click thread line to collapse