Skip to content
This repository has been archived by the owner on Feb 11, 2020. It is now read-only.

[BUG] 5.1.1 - Tasker Intent stop sending after 1-2 mins idle #149

Open
andy-harney opened this issue Jul 21, 2019 · 9 comments
Open

[BUG] 5.1.1 - Tasker Intent stop sending after 1-2 mins idle #149

andy-harney opened this issue Jul 21, 2019 · 9 comments
Labels
bug Something isn't working

Comments

@andy-harney
Copy link

Describe the bug
Tasker intents not working after device has been idle for 1-2 minutes.

To Reproduce
Steps to reproduce the behavior:

  1. send intent from tasker
Action: me.msfjarvis.viscerion.SET_TUNNEL_UP
Extra: tunnel_name:my_tunnel
Extra: integration_secret:_secret_
Package: me.msfjarvis.viscerion
Class: com.wireguard.android.services.TaskerIntegrationReceiver
  1. nothing.

Expected behavior
Tunnel up or down.

Screenshots
Viscerion - Cached Processes

Device information (please complete the following information):

  • Device: Pixel 3A XL
  • OS: Android 10 / Q Beta 5
  • Version 5.1.1

Additional context
The tasker intents haven't always worked on the Android 10 Betas if the Viscerion app wasn't used recently. I've been waiting for 8c57fed from #142 to appear in the play store, which happened quite recently. This didn't resolve the issue. I followed the steps in #148, and updated to 5.1.1, and noticed that the Viscerion processes don't appear to be running, rather appear as cached processes, see screenshot. I also rebooted the phone to see if that helped. No joy.

Thanks for a great app nonetheless.

@andy-harney andy-harney added the bug Something isn't working label Jul 21, 2019
@msfjarvis
Copy link
Owner

That's saddening :(

I'll ask around for a more resilient solution, please bear with me in the mean time.

@andy-harney
Copy link
Author

No rush from me, if you need any further details, just let me know.

Thanks.

@msfjarvis
Copy link
Owner

Thanks to Francisco Franco, I've found a viable solution for this problem that I truly believe will end this constant suffering of mine. I'll post an APK here in a couple hours, please let me know if it works out for you 🙏

@msfjarvis
Copy link
Owner

msfjarvis commented Jul 21, 2019

@andy-harney @cf00 Please try this APK and let me know if there's any regression/improvements. If this still fails I'll be moving to a foreground service.

Edit: Source is available at 9b3f8a1 in case you're someone who's interested by this particular problem :)

@andy-harney
Copy link
Author

andy-harney commented Jul 21, 2019

I've just given the linked apk a go. Enabled taskerIntegration, set Secret and the intents don't work at all.
I reinstalled the play store version, and they work again.

I'm under the assumption that the class, action & package remain the same with the tasker intent?

Edit. Francisco Franco? XDA... That takes me back, I used to moderate XDA... good times.

@cf00
Copy link

cf00 commented Jul 21, 2019

Sorry to report that this version doesn't work for me either.

As for the issue of the Tasker integration not working when the device has been idle for some time: I actually had the same problem initially with v5.1.1 (only noticed it after I had already confirmed that it worked). I tried disabling battery optimization for the Viscerion app and that seems to have done the trick - v5.1.1 now works for me also after longer idle periods (at least in the last few hours).

@msfjarvis
Copy link
Owner

Thanks for the quick testing, very appreciated. I'll give it another shove in the morning.

@msfjarvis msfjarvis changed the title [BUG] 5.1.1 - Tasker Intent stop sending after 1-2 mins idle. Android Q [BUG] 5.1.1 - Tasker Intent stop sending after 1-2 mins idle Oct 10, 2019
@RafhaanShah
Copy link
Contributor

A possible fix may be 'disabling battery optimization', seems very reliable on my Google Pixel 3a on Android 10.

App info for Viscerion -> Battery -> Battery optimisation.

Also have a look at https://dontkillmyapp.com

@github-actions
Copy link

This Issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale label Dec 20, 2019
@msfjarvis msfjarvis removed the stale label Dec 21, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants