EAP version 1.33.0-dev

[Scotty]

Thanks Martin.

I didn't mention this in my original post, but I have three different Automagic flows that backup to Dropbox. All three were working in the EAP build that was going to expire a few days ago. After I installed the current build (which will expire at the end of February), only one of the three flows kept working. The second flow gave the "chunk" error that I reported, and the third flow gave a different error - something like "path_malformed". I didn't report that one to you in my original post because I played around with the flow, and fixed it (by removing, in the flow, a forward slash at the end of the target directory on Dropbox).

So given that 3/3 worked in the penultimate EAP build, and 2/3 failed in the current build -- maybe you tweaked something when preparing the current build?

Appreciate your response. Best wishes.

[Martin]

I can also reproduce the path/malformed issue. Should be fixed in the next build.
Thanks for reporting the issues!

[Martin]

A new EAP version is available.

Changes in this update:

• fixed reported Dropbox regressions
• minor changes & bug fixes

Download: Automagic.apk (2017-02-02)

Regards,
Martin

[Scotty]

Hi Martin

I installed & tested the new build. The flow that previously gave a "chunked" error now works - thanks. The first time I ran one of my other flows (one that hasn't previously given a problem), it ended with an error ("too_many_write_operations"). However, I have re-run it several times, and that error has not re-appeared, and the flow seems to terminate normally. If the error recurs, I'll post here. Thanks again.

[Martin]

Hi,

I've improved the handling of the too_many_write_operations error in the next build so it should not occur anymore.
Thanks for reporting and let me know if you find any other issues.

Regards,
Martin

[mbirth]

Did you change something with the Android Wear integration? My Sony SW3 only lasts short of a day since installing the latest EAP version. It lasted over 2 days before. The only other Wear-related app I updated recently was the watchface - but there were also only minor changes listed which shouldn't affect the runtime. (But I'll ask there, too.)

[Martin]

There were only minor changes to the wear app (feature to drag/drop overlays) which should not have any negative effect on the battery consumption.
Maybe Google Play services is causing troubles or tries to update. Try to restart the watch one or two times. On the watch also try to update Google Play services by going to Settings->About->Versions and click on Google Play services to start the update check.

Regards,
Martin

[mbirth]

There were only minor changes to the wear app (feature to drag/drop overlays) which should not have any negative effect on the battery consumption.
Maybe Google Play services is causing troubles or tries to update. Try to restart the watch one or two times.

I think you are spot on with your guess. Battery Historian showed 6-8% per hour consumption for the last few days. I rebooted it a few times without any result. However, yesterday, I switched it off completely and this morning it was down to <3%/hr. Battery Historian shows that it updated Google Maps on the watch (for which there wasn't an update on my phone) right after turning on. And even after that, the consumption didn't get higher than 4%/hr.

Thanks anyways!

[Martin]

A new EAP version is available.

Changes in this update:

• minor changes & bug fixes

Download: Automagic.apk (2017-02-19)

Regards,
Martin

[Martin]

A new EAP version is available.

Changes in this update:

• added new root method to activate WiFi tethering in action Set WiFi Tethering State for Android 7.1 **
• minor changes & bug fixes

Download: Automagic.apk (2017-03-05)

Regards,
Martin