Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Too "agressive" TracingService usage #112

Open
EnekoGomezTecnalia opened this issue May 19, 2020 · 0 comments
Open

Too "agressive" TracingService usage #112

EnekoGomezTecnalia opened this issue May 19, 2020 · 0 comments
Labels
prestandard This issue is referring to the "prestandard" solution and not the current GAEN implementation.

Comments

@EnekoGomezTecnalia
Copy link

Hi,

By calling ContextCompat.startForegroundService continuously to interact with TracingService and returning always START_REDELIVER_INTENT in its onStartCommand, if the OS (or you yourself) kills the service, when restarted it re-executes absolutely every intent that was executed in the past, all in a raw (the ACTION_START, all the numerous ACTION_RESTART_SERVER and all the even more numerous ACTION_RESTART_CLIENT). That is absolutely unnecessary and slows down the app and the system.

Not sure if the solution is to return START_REDELIVER_INTENT only on ACTION_START, return always START_NOT_STICKY or re-thinking the service...

@simonroesch simonroesch added the prestandard This issue is referring to the "prestandard" solution and not the current GAEN implementation. label May 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
prestandard This issue is referring to the "prestandard" solution and not the current GAEN implementation.
Projects
None yet
Development

No branches or pull requests

2 participants