Android apps background processes start unallowed

asked 2016-02-29 19:14:21 +0300

Toxip
3363 ●39 ●61 ●56

I noticed that in the latest update 2.0.1.7 Taalojärvi android apps start their background processes even when they're not allowed to in the settings. This happens very randomly and haven't been able to tell a specific pattern how and when they start. Sometimes after reboot they start and whenever I restart alien dalvik, they start again. This only started happening after the latest update and never happened in Saimaa update. This behavior is unwanted and should not happen since Android apps can quickly start consume system resources. Android apps should stay under control at all times.

edit retag flag offensive close delete

Comments

1

Yea I also experiencing this issue - often after restarting my Jolla I am directly receiving message notifications. But I also have Google Shit Services installed and thought that issue is caused by this - do you have Google Pla* services installed?

Alex ( 2016-02-29 19:39:51 +0300 )edit

2

I have the same experience. The Whatsapp has not allowed to run in the background, but will starts as soon as I start another Android application (for example, Waze).

cocovina ( 2016-02-29 20:27:24 +0300 )edit

1

I do not have Google services installed and can see this bug too.

Aslanex ( 2016-02-29 20:57:55 +0300 )edit

3

For me, google play store and google setting always running in background

TMavica ( 2016-03-01 03:57:06 +0300 )edit

4

answered 2016-03-01 12:29:24 +0300

coderus

22985 ●253 ●337 ●370

https://coderus.openrepos...

Most of android apps have abilities to start services on certain actions, not just booting system, and this behaviour cant be adjusted in jolla aliendalvik.

edit flag offensive delete publish link

Comments

1

Truely. I tried use a android tools to disable apps autostart, but it is still nil help (rooted need)

TMavica ( 2016-03-01 14:25:22 +0300 )edit

Not totally true: that behavior occurs ONLY once you start an app (that has that behavior).. If you start or restart Alien and DON'T start the app, that behavior doesn't occur.

palikao ( 2017-06-02 17:54:50 +0300 )edit

3

answered 2016-03-02 19:28:01 +0300

apivirot
91 ●2 ●3 ●7

updated 2016-03-02 19:28:40 +0300

I think this is a bug, since the option Settings->Applications->[Android App]->Allow background services to be performed at startup is not preventing that android application service to start at phone startup.

edit flag offensive delete publish link

Comments

1

There are a lot of events in android to make applications start, not just general startup. You just cant control it in sailfishos dalvik.

coderus ( 2016-03-02 19:45:57 +0300 )edit

3

answered 2017-06-01 14:44:47 +0300

articice
291 ●14 ●19 ●26

I have noticed a strange dependency on how the background processes are being started or not. First of all - my Android auto-start is disabled.

When I run my first Android app, it starts the Android layer and then the app's background process (for some apps like Skype or Hangouts I have to start them twice - first the background process is started, then - the front-end, if you may call it this way). Let's call this a cold-start.

Some apps, though, when cold-started, start not only their own background process, but ALL the background processes (or a subset of them?) for all installed apps (ignoring settings, of course). In my case there are many of them so it's noticeable.

If the emulation layer is already running, starting apps is easier although still slow (or has to be done twice) if their background process is disabled in settings. Let's call this a hot-start.

Scenarios/workarounds:

If I start Android support from settings -> Android support -> Start, it auto starts all allowed background processes (in most cases) and CPU/memory usage is adequate
If I cold-start Play Market, it seems to start only its own background process, but not other apps (probably the best)
If I cold-start, e.g. Amazon Kindle - all background processes are started (and phone starts lagging)
If I hot-start, e.g. Amazon Kindle - no such problem occurs
If I cold-start e.g. Skype - it starts only some things it needs from com.android namespace, like Gallery, but doesn't start other apps' background processes.

In conclusion - experiment with your own correct sequence of how to launch the Android apps. I also think it's a bug (or you may call it an Android processes control issue) and it has to be fixed.

edit flag offensive delete publish link

Comments

1

So it’s 2018 and I obeserved the behaviour as well. For me with Amazon App-Store. As the apps you get from there only operate, if your an are signed in with you Amazon username and password, it was likely that there has to be a background service running. Because I don’t like both of this, I don’t use apps from Amazon anymore. I first logged out and watched the behaviour with SailfishOS app Crest: com.amazon.venezia or something like this is always running, if you start the Android runtime. Same thing, after I disabled background service for the Amazon App-store. I had to make delete the Store from my Xperia X with SailfishX.

That’s bad behaviour, if you think you control the Android apps with your SailfishOS settings and it's nothappening!!!

What’s with the option to disable ability of Android apps to read your contacts? And f...ing lots of Android Apps want this and I want to prevent them doing this, by using these very important SailfishOS options!!!

zemideluxe ( 2018-01-12 18:49:10 +0300 )edit

Android apps background processes start unallowed

Comments

3 Answers

Comments

Comments

Comments

Question tools

Stats

Related questions

Android apps background processes start unallowed

Comments

3 Answers

Comments

Comments

Comments

Question tools

Public thread

Stats

Related questions