[Android Apps and Games] brandall:
V13 Up!

Overview

S'up folks, long time...

So, V13 has had a pretty major overhall and I really hope will be flawless on the logic side. Let me know!

There will be a V14 as I've discovered some hidden gems within Android regarding active wakelocks during sleep (whoop!), but extracting this data and presenting it correctly is beyond my shell capabilities at present.. I need to spend a few hours alone with Google to get my head around it.

Also, I've put in a request with the Tasker dev to convert com.blar.blar to the application name under the 'Test' action, so that I will indeed be able to honour my OP prediction of telling you the name of a specific troublesome application that has been holding wakelock.

Finally, in V14 the reports will be in HTML format so the wakelocks can be hyperlinked to a Google search for more information, or killed immediately by using the Task/Process Killer script I wrote for Tasker many moons ago. I need the html viewer .apk to be installed via shell during set-up and this involves a little more reading for me too..

Anyway, please read the set-up instructions below!

Let me know your feedback folks!

Change Log

[B][U]V13[/U][/B]

* Direct execute shell commands via Tasker (no longer use locale plugin)
* Changed logic for end call to prevent 'display off data stolen' errors
* Removed incorrect %DSCOFF variable clear in TIS tasks
* Corrected the DSDAdhocTIS upload
* Cleared errorlog.txt to avoid file failures
* Included toolbox generic tests in error log
* Populated XDA Username in error log and ReadMe
* Included busybox version in error log
* Let DisplayOff handle %NOCOUNT clearing
* Calculated time_in_state using shell (too many frequencies on recent devices)
* Included IF/ELSE logic in certain tasks
* Added failsafe for missing time_in_state files
* Set permissions using busybox to avoid permission to set permissions error!!
* Corrected binary PS request
* Increased data collected in error logging (nothing personal of course).
* Tried my best to make notification click work correctly...
* Collected DSP data when incoming call wakes from sleep and display goes off.
* Included Tasker version number in error log - credit [URL="http://xdaforums.com/member.php?u=2440628"]fubaya[/URL]
* Replaced all Test File actions
* Improved logic in almost every task
* Lots of other things I can't remember...

[B][U]To Do[/U][/B]

* Solve Tasker media 'bug'

Installation Instructions

* Delete all profiles and DSD* tasks from Tasker

* Delete all DSD* profiles and DSD* tasks from the folders Tasker/Profiles & Tasker/Tasks

* Unzip the latest version download

* Place the task files in /sdcard/Tasker/Tasks

* Place the profile files in /sdcard/Tasker/Profiles

* Place the folder DSD on the root of your storage card (after deleting/renaming any current folder from a previous version)

In Tasker, from the menu options/profile data 'Import One (15) Task':

DSDDON

DSDDONTIS

DSDDOFF

DSDDOFFTIS

DSDIntMaths

DSDNotify

DSDAdhoc

DSDAdhTIS

DSDAhMathsDST

DSDAhMathsUPS

DSDFileSetUp

DSDSUPOP

DSDSuperUser

DSDWakelock

DSDErrorLog

In menu options/profile data 'Import One (11) Profile':

DSD-DisplayOn

DSD-DisplayOff

DSD-Incall

DSD-EndCall

DSD-Power

DSD-Boot

DSD-ShutDSH

DSD-ShutDTIS

DSD-Notify

DSD-Reboot

DSD-Media

The above profiles also contain the following 13 tasks, which will be automatically imported:

DSDDispOn

DSDDispOff

DSDDeviceBoot

DSDDuringCall

DSDEndCall

DSDCharging

DSDChargeEnd

DSDMedia

DSDMediaEnd

DSDNClick

DSDShutDSH

DSDShutDTIS

DSDReboot

SuperUser

After plenty of headaches, my findings are that the settings used in the SuperUser application can slow down the execution of processes/commands requiring root. I strongly suggest that under the preferences, you set Access timeout to '0' and the Automatic response to 'prompt'.

First Run

* Ensure all of the task and profiles imported correctly

* Save out of Tasker to preserve the changes made

* Load Tasker and select the task DSDSuperUser

Thanks to nobnut and his testing, I've been able to establish that the SuperUser requests can take up to 30 seconds to appear (although mine appears in under a second!). There is only one command that needs permission. DSDSuperUser has a 30 second wait time to give the SuperUser application a chance to prompt. If it hasn't appeared by the end of the wait time, there is a pop up asking if you want to run the task again - I hope you'll only need to run it once though!

* Press 'test' in DSDSuperUser and follow the instructions from there! PLEASE do read the readme file as it contains other important instructions!

Let's get detecting... :eek: