IssueTracker

This issue does not reproduce with dev preview 4.

Closing this issue as per comment #2 from reporter.

It seems that this backstage activity is totally obsolete. Sure enough, Google was left with more than one or two holes

Add up! Google is now allowing the front desk service to ignore all background restrictions

Please allow the application to stop all services (including the front service) and all broadcasts (including the bindservice) when the application is in the background.
Give us a real shutdown application background runtime implementation
That's not very high

@4 Capture a bugreport for them, otherwise they would probably ignore it, just like oasisfeng's report(the actual problem was already issued months before, and had been ignored)

Please do provide all the information requested in comment#3 to proceed further.
JFR, attaching the video of my observation.

@7

Actually, I don't quite know how to do issue
Can you help me?

@ 8
Your video. Look, taobao is fine

This is Android bug report.

Can you please check the issue on android Oreo release, OPR6.160623.013 and let us know the result?

If issue reproduces on latest build, please share  the bugreport for analysis. Also, please do attach the video demonstrating the issue.

Please address the comment#12 and share the details if the issue persists on Oreo release.

@13
I'm going to have a test for this, and will upload related information later

I tested it in OPP6.170623.013 can confim the background services in this specific case are killed, which should probably resmble the fix of the following issues:

https://issuetracker.google.com/issues/37126419
https://issuetracker.google.com/issues/62480012

However, please take a looke at this issue(Similar to route 4b, however with an app targeting API level 26)
https://issuetracker.google.com/issues/64535598
https://issuetracker.google.com/issues/65335068

Condition:

The app
https://play.google.com/store/apps/details?id=com.taobao.taobao
Version: 6.11.0
Published: Aug 31, 2017
(Besides I am wondering why you guys should even allow hot patch in Android platform )

Related action
1:Install the app
2:set AppOps RUN_IN_BACKGROUND to ignore since in this build user are still not always able to apply background limit(I think it is a bug) before the app has ever run
3:Start the app
4a:Leave the app by both back or home button
4b:Leave the app by both back or home button and swipe away the app's task from recent task list (within a minute)
5:Go to developer settings -> service, and watch apps' background service list.

Behavior:
4a route:  this app's service are killed after about 1 minute in step 5
4b route: this app's service are immediately killed after its task get swiped
After step 5, background service triggers are prevented

Related logcat output:

......(about one minute after step 4a)
W/ActivityManager(4634): Stopping service due to app idle: u0a83 -1m7s982ms com.taobao.taobao/com.taobao.tao.log.collect.AccsTlogService
W/ActivityManager(4634): Stopping service due to app idle: u0a83 -1m8s281ms com.taobao.taobao/com.taobao.accs.data.MsgDistributeService
......
......(several minutes later)
W/ActivityManager(4634): Background start not allowed: service Intent { act=org.agoo.android.intent.action.REPORT pkg=com.taobao.taobao cmp=com.taobao.taobao/.TaobaoIntentService } to com.taobao.taobao/.TaobaoIntentService from pid=25334 uid=10439 pkg=com.taobao.taobao
W/ActivityManager(4634): Background start not allowed: service Intent { act=org.agoo.android.intent.action.REPORT pkg=com.taobao.taobao cmp=com.taobao.taobao/.TaobaoIntentService } to com.taobao.taobao/.TaobaoIntentService from pid=25741 uid=10439 pkg=com.taobao.taobao
......(unlock the device)
W/BroadcastQueue(4634): Background execution not allowed: receiving Intent { act=android.intent.action.USER_PRESENT flg=0x24200010 } to com.taobao.taobao/com.taobao.accs.EventReceiver

Reproduces on OPR6.170623.013.
This app uses an Android Dynamic Component Framework called https://github.com/alibaba/atlas. It can dynamic load any components from server.

You may need to install and run the program for a longer period of time. This App will not immediately download some logic components.

@16
Did you observe the behavior described in 4a(of post  #15)?
4a:
Every background service of this app should be killed after a little more than 1 minute(In my case it is 67 or 68 seconds) after you leave the app.

Another reasonable doubt is that the app's background services were pulled up after procedure 4a.
In my case, I continued observing it for another tens of minutes, and all the logcat output I could find for this app are sorts of
"Background start not allowed: service Intent {****} to com.taobao.taobao/***** from pid=????? uid=????? pkg=com.taobao.taobao"

I tested it in the same device(Huawei Angler) as yours.

Can you please clarify the following questions, since it may be helpful for issue investigation?
1: So you must have opt-out the background activity(it is opt-in by default) for this app before your test, do you?
2: If 1 is yes, did you observe the services killed described in procedure 4a?
3a: If the answer of 2 is true, then did you observe the services of the app get pulled up later? When was it? How long did it take?
3b: If the answer of 2 is false, then that would be indicating some bugs still existing, since this issue seems to be irrelevant to 64535598 (https://issuetracker.google.com/issues/64535598  only apps targeting API 26 are affected)

I can confirm in this bugreport, the app did have background services for tens of hours:

Time spent running actively in the background   19h 46m 41s 616ms
Time spent cached       212ms

We've deferred this to a future release, but leaving this open for now.

I too have the same bug in nexus 6P after updating to 8.0. Most of the third party apps are still running in the background despite disabling background activity.

Anyways I think reporting and waiting for Google to fix is too lengthy and tedious. I have installed GREENIFY and now I am at peace again. It simply force stops all my selected apps as soon as screen is turned off.

Could you please check it on the latest release 8.1 and share the bugreport and necessary screenshots if the issue persists?

@#22
By saying this, do you mean this patch was landed in the public Developer Preview 1 of Android 8.1?

We have latest release available here : https://developers.google.com/android/images.
Please check it on the same and let us know by raising a new issue here : https://b.corp.google.com/issues/new?component=190923&template=841312 along with the necessary details.