Tasker 4.8 Beta

[Pent]

http://tasker.dinglisch.net/beta.html

Pent

<P>Added</P>
<UL>
        <LI>manifest permission cyanogenmod.permission.PUBLISH_CUSTOM_TILE for action Quick Settings Add
        <LI>actions System / Quick Setting Add, System / Quick Setting Remove (recent Cyanogen ROMs only)
        <LI>event System / Quick Setting Clicked (recent Cyanogen ROMs only)
        <LI>scene element Number Picker: Format parameter
        <LI>support for Alarms Only Do Not Disturb mode (Android 6.0+)
        <LI>warning about disabled location services after editing Wifi Near state (Android 6.0+)
        <LI>manifest permission android.permission.REQUEST_IGNORE_BATTERY_OPTIMIZATIONS (for Android 6.0+)
        <LI>warning about enabled battery optimizations for Tasker (Android 6.0+)
</UL>

<P>Bugfixes</P>
<UL>
        <LI>support for new Android exact alarm API (Android 5.0+)
        <LI>tracking failure caused by Auto Brightness action pre-KitKat
        <LI>app creation: action Wifi Tether was failing in kid due to missing permission
        <LI>action Zip: was including ./ in front of entries
</UL>

<P>Changes</P>
<UL>
        <LI>run log: when condition for an action fails, run log shows IfFail instead of OK
        <LI>state Media Button, parameter Held: when checked, register a handler for Web Search intent in order to override Android's default behaviour for the media button (Android 5.0+)
        <LI>event Assistance Request: only enable Android event handler if needed by an enabled profile
        <LI>state Calendar Entry: / in calendar names in URL format are not treated as boolean or
</UL>

[David Wang]

I got an error when I update Tasker from 4.7u3m to 4.8b1m as usual. Logs captured and I find a line says "10-26 09:20:07.903 D/InstallAppProgress(16448): Installation error code: -103" in it. Then I get some information from github about the error code "-103":

public static final int INSTALL_PARSE_FAILED_NO_CERTIFICATES = -103;

Related logs(device info included) and screenshots attached.

P.S: I've send you email for reporting this issue a moment ago. Just forget the email, now I can login in GoogleGroups normally.

[Andrea Bruzzesi]

I face the same issue got by Dave Wang; I also notice that both of us have a device running Xiaomi MIUI interface, so it could be a ROM problem (not something hacked, I have a Xiaomi device indeed).

[Andrea Bruzzesi]

Sorry, fixed using the 'm' download. Now checking time trigger profile out.

[fiSh]

In Smart Manager (on S6 5.1.1) there is an app optimization list (battery section) disabling it for tasker and rebooting, does this help?

[John Doe]

Just a tip: this permission permission "android.permission.REQUEST_IGNORE_BATTERY_OPTIMIZATIONS" is only for instant messaging, voip or chat apps according to Google Play team. Your app will be removed from play store if you don't remove it. I know, the docs says that if doze/app standby break the core of your app you can use it, but it seems Google Play team is not agree with that statement.

[David Wang]

In Smart Manager (on S6 5.1.1) there is an app optimization list (battery section) disabling it for tasker and rebooting, does this help?

 No, that didn’t help. I use Android 4.1.2.

[David Wang]

Sorry, fixed using the 'm' download. 

 I always use the "m" download for updating. The issue still exists.

And I find some useful infomation about this issue in the log attached :

10-26 09:20:01.313 I/ActivityManager(490): START {act=android.intent.action.VIEW dat=file:///storage/sdcard0/Download/taskerm 4.8b1m.apk typ=application/vnd.android.package-archive cmp=com.android.packageinstaller/.PackageInstallerActivity u=0} from pid 16157

10-26 09:20:01.353 I/ActivityManager(490): Start proc com.android.packageinstaller for activity com.android.packageinstaller/.PackageInstallerActivity: pid=16448 uid=10031 gids={1028, 1015}

10-26 09:20:01.463 D/=== APP ENV ===(16448): com.android.packageinstaller.manufacturer=>null

10-26 09:20:01.463 D/=== APP ENV ===(16448): com.android.packageinstaller.model=>null

10-26 09:20:01.463 D/=== APP ENV ===(16448): com.android.packageinstaller.imei=>null

10-26 09:20:01.463 D/=== APP ENV ===(16448): com.android.packageinstaller.imsi=>null

10-26 09:20:01.463 D/=== APP ENV ===(16448): com.android.packageinstaller.mac=>null

10-26 09:20:01.463 D/=== APP ENV ===(16448): com.android.packageinstaller.android_id=>null

10-26 09:20:01.463 D/=== APP ENV ===(16448): com.android.packageinstaller.sim_type=>null

10-26 09:20:01.473 D/=== APP ENV ===(16448): com.android.packageinstaller.sim_number=>null

10-26 09:20:01.473 D/=== APP ENV ===(16448): com.android.packageinstaller.net_type=>null

10-26 09:20:01.683 W/PackageParser(16448): Unknown element under <application>: uses-feature at /storage/sdcard0/Download/taskerm 4.8b1m.apk Binary XML file line #188

10-26 09:20:01.693 I/PackageInstaller(16448): no recommeded for this package: net.dinglisch.android.taskerm(ver=5034)

10-26 09:20:01.883 W/PackageParser(16448): Unknown element under <application>: uses-feature at /storage/sdcard0/Download/taskerm 4.8b1m.apk Binary XML file line #188

10-26 09:20:02.403 W/PackageParser(16424): Unknown element under <application>: uses-feature at /storage/sdcard0/Download/taskerm 4.8b1m.apk Binary XML file line #188

10-26 09:20:02.443 W/PackageParser(16424): Unknown element under <application>: uses-feature at /storage/sdcard0/Download/taskerm 4.8b1m.apk Binary XML file line #188

10-26 09:20:03.003 I/ActivityManager(490): Displayed com.android.packageinstaller/.PackageInstallerActivity: +1s660ms

10-26 09:20:05.143 I/PackageInstaller.ParsePermissions(16448): Ignoring unknown permissin:cyanogenmod.permission.PUBLISH_CUSTOM_TILE

10-26 09:20:05.143 I/PackageInstaller.ParsePermissions(16448): Ignoring unknown permissin:android.permission.REQUEST_IGNORE_BATTERY_OPTIMIZATIONS

10-26 09:20:05.143 I/PackageInstaller.ParsePermissions(16448): Ignoring unknown permissin:android.permission.BODY_SENSORS

10-26 09:20:05.143 I/PackageInstaller.ParsePermissions(16448): Ignoring unknown permissin:com.latedroid.juicedefender.permission.CONTROL_JUICEDEFENDER

10-26 09:20:05.143 I/PackageInstaller.ParsePermissions(16448): Ignoring unknown permissin:com.latedroid.juicedefender.permission.TOGGLE_MOBILE_DATA

10-26 09:20:05.143 I/PackageInstaller.ParsePermissions(16448): Ignoring unknown permissin:com.android.phone.CHANGE_NETWORK_MODE

10-26 09:20:06.803 I/ActivityManager(490): START {dat=file:///storage/sdcard0/Download/taskerm 4.8b1m.apk cmp=com.android.packageinstaller/.InstallAppProgress (has extras) u=0} from pid 16448

10-26 09:20:06.903 W/InstallAppProgress(16448): Replacing package:net.dinglisch.android.taskerm

10-26 09:20:06.933 W/PackageParser(490): Unknown element under <application>: uses-feature at /storage/sdcard0/Download/taskerm 4.8b1m.apk Binary XML file line #188

10-26 09:20:07.003 I/ActivityManager(490): Displayed com.android.packageinstaller/.InstallAppProgress: +191ms

10-26 09:20:07.073 W/PackageParser(490): Unknown element under <application>: uses-feature at /data/app/vmdl-1562268372.tmp Binary XML file line #188

10-26 09:20:07.713 W/PackageParser(490): Exception reading AndroidManifest.xml in /data/app/vmdl-1562268372.tmp

10-26 09:20:07.713 W/PackageParser(490): java.lang.SecurityException: META-INF/RELEASE_.SF has invalid digest for res/layout/eventedit.xml in /data/app/vmdl-1562268372.tmp

10-26 09:20:07.713 W/PackageParser(490):  at java.util.jar.JarVerifier.invalidDigest(JarVerifier.java:131)

10-26 09:20:07.713 W/PackageParser(490):  at java.util.jar.JarVerifier.verifyCertificate(JarVerifier.java:350)

10-26 09:20:07.713 W/PackageParser(490):  at java.util.jar.JarVerifier.readCertificates(JarVerifier.java:258)

10-26 09:20:07.713 W/PackageParser(490):  at java.util.jar.JarFile.getInputStream(JarFile.java:378)

10-26 09:20:07.713 W/PackageParser(490):  at android.content.pm.PackageParser.loadCertificates(PackageParser.java:468)

10-26 09:20:07.713 W/PackageParser(490):  at android.content.pm.PackageParser.collectCertificates(PackageParser.java:656)

10-26 09:20:07.713 W/PackageParser(490):  at com.android.server.pm.PackageManagerService.installPackageLI(PackageManagerService.java:7597)

10-26 09:20:07.713 W/PackageParser(490):  at com.android.server.pm.PackageManagerService.access$1600(PackageManagerService.java:166)

10-26 09:20:07.713 W/PackageParser(490):  at com.android.server.pm.PackageManagerService$5.run(PackageManagerService.java:5885)

10-26 09:20:07.713 W/PackageParser(490):  at android.os.Handler.handleCallback(Handler.java:615)

10-26 09:20:07.713 W/PackageParser(490):  at android.os.Handler.dispatchMessage(Handler.java:92)

10-26 09:20:07.713 W/PackageParser(490):  at android.os.Looper.loop(Looper.java:137)

10-26 09:20:07.713 W/PackageParser(490):  at android.os.HandlerThread.run(HandlerThread.java:60)

10-26 09:20:07.713 E/PackageParser(490): Package net.dinglisch.android.taskerm has no certificates at entry AndroidManifest.xml; ignoring!

10-26 09:20:07.903 D/InstallAppProgress(16448): Installation error code: -103

10-26 09:20:07.913 I/XIAOMIANALYTICS(16448): start session(com.android.packageinstaller)

10-26 09:20:07.913 I/XIAOMIANALYTICS(16448): end session(com.android.packageinstaller)

10-26 09:20:24.403 W/dalvikvm(16521): VFY: unable to resolve virtual method 616: Landroid/content/pm/PackageManager;.getPackageInstaller ()Landroid/content/pm/PackageInstaller;

10-26 09:20:33.363 I/InstallAppProgress(16448): Finished installing net.dinglisch.android.taskerm

10-26 09:20:34.493 W/dalvikvm(16674): VFY: unable to resolve virtual method 616: Landroid/content/pm/PackageManager;.getPackageInstaller ()Landroid/content/pm/PackageInstaller;

10-26 09:20:34.863 I/ActivityManager(490): Process com.android.packageinstaller (pid 16448) has died.

10-26 09:20:47.093 W/dalvikvm(16769): VFY: unable to resolve virtual method 446: Landroid/content/pm/PackageManager;.getPackageInstaller ()Landroid/content/pm/PackageInstaller;

10-26 09:20:48.423 W/dalvikvm(16799): VFY: unable to resolve virtual method 446: Landroid/content/pm/PackageManager;.getPackageInstaller ()Landroid/content/pm/PackageInstaller;

Related links for "INSTALL_PARSE_FAILED_NO_CERTIFICATES" issue: http://stackoverflow.com/questions/2914105/android-what-is-install-parse-failed-no-certificates-error

[Scott Miller]

Interesting. I just tried to install it on my Galaxy Note 10.1 with Android 4.1.2 and it won't install for me, either. At first I thought it was because I downloaded the wrong version, which I did, but the correct version will not install, either. I am installing the market version.

I successfully installed the market version on two other devices, one running Android 5.0.1 and the other running Android 5.1.1.

Scott

On Oct 26, 2015 9:23 PM, "David Wang" <dance.of...@gmail.com> wrote:

In Smart Manager (on S6 5.1.1) there is an app optimization list (battery section) disabling it for tasker and rebooting, does this help?

 No, that didn’t help. I use Android 4.1.2.

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

[David Wang]

Interesting. I just tried to install it on my Galaxy Note 10.1 with Android 4.1.2 and it won't install for me, either. At first I thought it was because I downloaded the wrong version, which I did, but the correct version will not install, either.

I am installing the market version. I successfully installed the market version on two other devices, one running Android 5.0.1 and the other running Android 5.1.1.

So maybe the issue only affect specific Android version(e.g. 4.1.2). The issue never occured before for me(Android 4.1.2). 

 

[Pent]

Hey JD,

Just a tip: this permission permission "android.permission.REQUEST_IGNORE_BATTERY_OPTIMIZATIONS" is only for instant messaging, voip or chat apps according to Google Play team. Your app will be removed from play store if you don't remove it. I know, the docs says that if doze/app standby break the core of your app you can use it, but it seems Google Play team is not agree with that statement.

Do you have some reference discussion for that, or is it personal experience, or ?

I'm not enjoying this Android release :-)

Thanks,

Pent

[Pent]

Fortunately I have an old 4.1.2 Nexus S lying around and could
reproduce the install problem there, will fiddle around.

Pent

[John Doe]

Tested on field :( I quite agree with you about the release.

[Andrea Bruzzesi]

Hi Pent, I see the new beta leverages some CM specific features.

Would you consider including expanded desktop (or immersive mode) setting?

I'd love to automatically activate immersive in landscape mode and go back to normal when the phone orientation becomes portrait.

Long time ago Secure Settigs plugin was able to trigger that feature, but it stopped working.

Thanks in advance for your care.

[Pent]

    Fortunately I have an old 4.1.2 Nexus S lying around and could
    reproduce the install problem there, will fiddle around.

The problem is an updated part of my development environment
generating things that the older devices don't like related to the
APK signature.

I spent quite a while but have been unable to generate for the older
devices with the newer environment and will only be able to release
updates for newer devices (likely 4.3+) in the future.

My apologies :-(

Pent

[John Doe]

Just a tip: maybe you are using jarsigner from jdk 8, you need to use jdk7.

[PEN Chanter]

[ Pent ] "have been unable to generate for the older devices with the newer environment and will only be able to release updates for newer devices (likely 4.3+) in the future. My apologies :-( "

This is undesirable news indeed. I am stuck with 4.1.2 unless I root my Tab 3. So I will simply continue to have fun with the latest version I have already installed. THANK YOU, Pent, for all your time, energy, blood, sweat and tears that you have poured into this obvious labor of love. Tasker is one of the handful of softwares I have ever purchased using `real` monies... in fact, not just once, but twice (using my husband's and my separate Google accounts)!! I have always been keen in automation and utility. You are much appreciated!

[Dale Smith]

Just wanted to say that I'm pleased to see your feeling better enough to be back here and working on fixing all the things that Google broke. I know it must be frustrating to have your hard work constantly broken by new OS releases.

[Pent]

Just a tip: maybe you are using jarsigner from jdk 8, you need to use jdk7.

Good tip!

It didn't work with the JDK7 jarsigner either, but the JDK6 one was OK. Don't know
if there are any other implications but it seems to also install fine on a marshmallow
device with the JDK6 signer.

Pent

[John Doe]

I use openjdk 7 and it works. Starting from jdk7 jarsigner uses different algorithms as default. If it works with jdk6 it seems your environment is not taking into account this change. Are you using Eclipse? As I said I have no problem with the latest Android Studio version and jdk7.

[Pent]

Thanks again, I could get the JDK7 jarsigner working by specifying the default digest alg from JDK6 (am using command-line
ant for release builds).

Pent

[Pent]

I released 4.8b2, the main difference is a fix for the install problem on Android 4.1/4.2 devices.

Pent

[Thom Little]

I access the Tasker 4.8b2m link and stored it on my Windows 7 machine

I connect the LG Lucid by USB cable and copied the file to the SD card

I installer Tasker from the SD card

 

Tasker 4.8 loaded under Android 4.0.4

It created a Tasker folder on the SD card

I created a simple Task that displayed a Popup

I exited Tasker

I added a task widget and could invoke the Task I created

I could not reenter Tasker ... it simply does nothing when the icon is taped

I uninstalled Tasker and reinstalled it

I repeated the above

This is some progress ... under 4.7 it did not create the Tasker folder

 

... Thom

[Thom Little]

Tasker 4.8b2m on LG Lucid under Android 4.0.4

• If I transfer to a different app then tapping the Tasker icon will take me back to where I was inside Tasker.
• If I exit Tasker and select Save First tapping the Tasker icon does not open Tasker.

 

The problem I reported with an app created by Tasker 4.7u3 App Factory on an Android 5.1 system and run as a standalone app on the LG Lucid under Android 4.0.4 ...

Show Scene

Wait 4 sec

Destroy Scene

... would throw an error on the Destroy Scene that the task hat stopped.  (Yes continue on error was selected.)

 

If run under 4.8b2m it now works correctly and does not throw the error on the Destroy Scene.

 

... Thom

[Abdullah Alahdal]

Flashed Android 6 (Chroma) on my Nexus 4 and found Tasker unreliable in Time context profiles, usually 5+ late. I will keep testing before I flash Android 6 on Nexus 6.

[Walter Francis]

Sorry if this is spam; but great to see you back working on Tasker Pent :)

[Tony B.]

The proximity sensor doesn't seem to work on MM

[Pent]

The proximity sensor doesn't seem to work on MM

Couldn't reproduce that on N5 with 6.0 so it's unlikely to be a pure MM problem. Perhaps it's only with screen
off ? Try whitelisting Tasker in battery savings in Android settings.

Pent

[Pent]

Sorry if this is spam; but great to see you back working on Tasker Pent :)

Sorry to have to say it's a reluctant 'fix the worst MM bugs' effort.

Pent

[Tony B.]

I have an auto speakerphone task where it turns the speaker on if the device is taken away from my face, while in a call.

I just tried your suggestion and it did not work.

If you want, I can export the profile and you can try it yourself.

--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/MXEXhP4VzQM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.

[Pent]

I have an auto speakerphone task where it turns the speaker on if the device is taken away from my face, while in a call.

I just tried your suggestion and it did not work.

Try a simple proximity state -> flash message profile then.

Pent

[Tony B.]

If I do that, the proximity sensor is always green as if it is activated. I tried moving my hands around the proximity sensor to get it to go white, or to flash the message, neither happened.

--

[C S]

Issue using a reminder task in the latest beta.

Won't fire if I have more then one day set. Basically I want to be reminded to pay a bill on a certain day 10th of every month,then a reminder to pick up my pay cheque on the 7 and 21st, etc. Worked in last release. Not in latest beta.