Repair Autoremote URL

[baudi]

I'm having to do the "Repair Autoremote URL" action every day or two. I can't really rely on it working. Is there any way to determine inside Tasker whether it's registered or not, and then, if it's not, have Tasker repair it automatically?

[João Dias]

You shouldn't need to repair your URL ever, unless you're installing a new ROM or something. I suspect you have another app that's messing with AutoRemote and make it not work...

On Wed, Oct 22, 2014 at 8:22 PM, baudi <dch...@gmail.com> wrote:

I'm having to do the "Repair Autoremote URL" action every day or two. I can't really rely on it working. Is there any way to determine inside Tasker whether it's registered or not, and then, if it's not, have Tasker repair it automatically?

--
You received this message because you are subscribed to the Google Groups "joaomgcd" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joaomgcd+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[baudi]

Another app "messing with Autoremote"? How is that possible? What app could be doing that? How could it do it, given android's protections? 

Can you please be more specific? 

Could you explain what happens when I click "Repair Autoremote URL"?

[João Dias]

I mean that there are "battery saving" apps or similar that freeze other apps for example. These require rooted devices usually. Do you have a rooted device?

When you click the "Repair AutoRemote URL" AutoRemote gets a new GCM registration from google and starts using that after discarding the old one.

[baudi]

I do have a rooted device, and I do use Greenify as a battery saving app. I do not have greenify set to hibernate any of your Auto-apps, but I have now disabled it. I'll see if that makes a difference.

Thanks.

[João Dias]

With a rooted device "How could it do it, given android's protections?" doesn't apply :) A rooted app can do anything it wants to your system.

Thanks for your feedback

[baudi]

OK, I have set up a process on my Windows machine to send an autoremote message to Tasker every 10 minutes. If Tasker sees that it has not received a message for 10 minutes, it will post a notification. I have also enabled "Full Content" logging for SuperSU, so that I can see any superuser activity around the time of any notification. Maybe that will help identify the culprit if it's the fault or a rooted app.

[baudi]

Well, this is kind of interesting. I've been using the Watchdog process described above for the past 3 days, and there's only one instance of the message not being received. Subsequent messages were received without having to repair autoremote's URL. In the past, without the watchdog, I would have had to repair the URL at least once during that time. 

I wonder if the very act of sending/receiving a message every 10 minutes keeps the URL working.

I'll let the Watchdog keep running and see what happens.

[bdanders]

I've recently been having to repair my AutoRemote url about once a day. It seems to have coincided with activating some advanced features in Greenify. I do not use Greenify to hibernate the AutoRemote app, but when I activated the "GCM push for greenified apps" option I started having trouble with AutoRemote.

Any insight as to why this could be affecting my AutoRemote messages even though it isn't a greenified app?

[João Dias]

Sorry, I don't actually know how greenify works, so I can't help you there...

--