yashsingh1/xdaforums huggingface dataset:
[Android Apps and Games] nobnut:
Sorry, all I picked up from that were the words Apple and prick.

Sent from my HTC Flyer using vodka
[Android Apps and Games] brandall:
Ha! I'd noticed you'd never mentioned an iPh*ne in your collection... :eek:
[Android Apps and Games] azj:
What's the proper way to update from V7 to V8? I can't import the V8 tasks since Tasker says they already exist. I can import the V8 profiles but that leaves me with two profiles with the same name. Should I disable Tasker, delete the task and profile files, restart Tasker and make sure it doesn't think any of those tasks and profiles exist, re-import all of them and then run the setup?
[Android Apps and Games] brandall:
I suppose that is the best way - a little tedious unfortunately... Within the Tasker app itself you can delete the profiles and then the tasks afterwards and you don't have to drag the V8 files into the profiles / tasks folders before you import them, they can be imported from any folder on the sdcard if that makes it any easier...?

Did you see my post regarding the file permissions? - For me, ticking 'other' on the file permissions in a root explorer meant Tasker could read them.
[Android Apps and Games] nobnut:
To be safe, you can also go into Superuser and 'forget' any previous SU permissions granted to Locale relating to DSD.

PS Where the heck was V7.0? I missed that one ;)

Sent from my Motorola StarTac using Voodoo
[Android Apps and Games] raylgo:
Is anyone kind enough to help a total newbie install and run this? :) Or is this for newbies at all?

I only got as far as "Importing the Tasks in DSD v8" from my memory card... And I got the Superuser Task to run but what else should I do? Make a profile?
[Android Apps and Games] nightranger73:
I think sgs2 have problems with the timings... have seen you set tasker to wait for 15 seconds on the setup task but it actually waits only 5 secs before executing next command... this is the reason for the missing superuser requests

Sent from my GT-I9100

If you find this post usefull please press the "Thanks" button
[Android Apps and Games] nobnut:
The instructions in the first few posts may appear a little confusing but if you go over them a couple of times, it will all make sense. You will also need to read this post relating to V8.0.

First you need to install the Tasker beta linked from the first page, then, as you have done, unzip and copy the task and profile files to the relevant task and profile folders (inside the Tasker folder) on your SD card. Then from within Tasker's menu, import all of the tasks and profiles.

Then refer to the instructions, open the DSDSetup task and click the test button. Wait for the two Superuser requests and accept them. Keep pressing the back button to exit from Tasker. Then reboot. Then you should be good to go.

We worked out yesterday that there is something strange about the SGSII and DSD relating to SU requests. But I don't believe that this process is happening in 5 seconds on the SGSII. It is hard to tell exactly when the process completes, but the popup notifications on my device are certainly being triggered at nearer the 15 second point rather than 5. Yesterday I edited the wait period but it didn't seem to help. I still have to run the test twice to get both SU requests. I guess I could test this theory by putting in a couple of vibrates, one at the start and one at the end of the wait period.

Just for the record, the SGSII is an amazing phone, catastrophically let down by a number of issues, both software and hardware related. In the space of a week I have gone from a love to a hate relationship with it. I do not rcommend this phone to anyone (I hope Samsung are reading this).
[Android Apps and Games] brandall:
Version 8b up shortly

Thanks for holding the fort nobnut - stupid real life things to do...

I've solved the detective report issue, so will be uploading a new version shortly. It appears that even with SuperUser requests granted for individual commands, the command that runs the script that contains the previously approved commands also needs root permissions... This fact was lost during my testing when everything happens in a 'piece it all together at the end' order...

Sorry for the inconvenience of a further version - V8b will be up shortly...

I'm going to include an ugly pop-up task that will loop the SU requests until the user confirms the correct amount have been approved - once the 'yes I did get that many' button is pressed, the remainder of the set-up will run.

Any better ideas?
[Android Apps and Games] nobnut:
Hey man! Don't apologise for the newer versions. If you finish this puppy, I will be out of a job! I love it.

Keep 'em coming I say.

Thank you by the way ;)
[Android Apps and Games] brandall:
V8a Up!

V8a

[!] Sorry to those that have already downloaded V8, but I needed to make changes for the reports to function correctly - Damn those SU requests!

* Changed set-up tasks to try and ensure SU requests are approved.

[!] Thanks to nobnut for his testing which discovered this.
[Android Apps and Games] brandall:
Can't have you out of work! V8a up, if you have the time, deleting the relevant SU permissions from the SU app log would be great as well as the entire DSD directory... Hope that's ok...?

Fingers crossed it works this time... :eek:

EDIT: brb in 30 mins!
[Android Apps and Games] nobnut:
So far, so good...

I got the three SU requests as intended. I didn't have to go for it again. I am now rebooting and will test for 20 minutes with screen off (no media playing) and report back.

Just two things to report so far. After the 3 SU permissions were granted, just before I exited Tasker (back arrow), I received a Tasker popup error stating 'Error: doesn't exist DSDSUPOP'. I ignored the hell clean out of it.

Following reboot, I received a popup stating 'Corrupt Shutdown Data'. EDIT: I attributed this to the fact that it hadn't had a full boot cycle since installing DSD.

I will leave it to run the test and come back in 20 minutes or so.

EDIT2: Oh balls. I just remembered that I didn't wipe the txt files from the SD. I will leave the test running and see what's what. If needs be, of course I will do the necessary and try again.

EDIT3: Damn and blast. Looks like I'll have to rerun the test. All of the files had yesterday's data. Will report back later.
[Android Apps and Games] azj:
No I can't seem to find that one. What files(s) do I need to change the permissions for?

I'm also confused about the instruction

Ensure Tasker has 'Accessibility' and 'Administrator' permission on your device. How do I do that?
[Android Apps and Games] nobnut:
I just reinstalled everything and the files weren't written to the SD card. I ran DSDSUPOP manually and the write files element appeared to work, so I then re-ran the Superuser task from within DSDSUPOP and no SU requests appeared which I guess is normal as they had already been granted.

Going for a reboot now to see what's what.

EDIT: Just before I rebooted, I checked for the txt files and they were there... sit down brandall before you read this next bit ;)

There wa a bunch of stuff under wakelock count!

Anyway I am rebooting now and will leave it to test for a short while, then report back, then go home.

Thanks!
[Android Apps and Games] nobnut:
For the Accessibility go to

Settings > Accessibility and make sure there is a tick next to Tasker. you will need to tick the top box probably to get it.

For the Administrator, it varies slightly from device to device

Settings > Security > scroll down to Device Administrators and put a tick next to Tasker
[Android Apps and Games] brandall:
I nearly fainted! WHOOP! Thanks again for all of this...

How was the initial set up task with the screen prompts and then the pop-up to run it again... then the bit where it opens the file...? Was it all fairly self-explanatory for new user do you think?
[Android Apps and Games] nobnut:
Yes, I think it was just fine. However... on one of my abortive attempts to install, I received a prompt to open a file. On the 'successful' attempts, I received no prompts :confused:

This could well be a 'user error'. Once I have reported back, I will have to scoot off.

Tomorrow morning I will uninstall everything and do it again... and again... and again, until I can definitively say what happens (for me at least). I will also (respectfully) suggest where I think that perhaps the new user might benefit from more prompting. Please feel free to ignore the cr@p out of me ;)
[Android Apps and Games] brandall:
It's much appreciated nobnut, and your feedback is most welcome, especially when it's good news!

As far as the abortive attempt goes, there is a variable set %SUCOUNT which runs the file set-up task when it is 2. Did this so only two attempts at SU task before the readme file offers further help regarding checking the SU app log to see if they are already there... Maybe I should up this to 3...

I'll let you let me know! Until tomorrow... :cool:
[Android Apps and Games] brandall:
I think you previously had a problem where Tasker couldn't read

/../../sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state

If you navigate to this file in a file/root explorer, you should have options to change the permissions. You need to make sure 'other' is ticked and then Tasker will be able to read it and return the data...

Tasker couldn't read

/../../sys/power/wake_lock
/../../sys/power/wake_unlock

for me, but could after I changed the permissions.
[Android Apps and Games] brandall:
LOL! Results are good news :) Until tomorrow... have a good one.
[Android Apps and Games] brandall:
Did you get it sorted raylgo? I'm going to update the set-up post to make it more clear.

Something's not right with the SU requests taking ages and differing from device to device and even from user to user - I have a 10 second delay for SU to confirm one of my commands has already been given permission... I'm going to take this up with the dev as is doesn't change on SuperUser Elite either - and as I'm a paying customer now, I can start making suggestions!
[Android Apps and Games] nobnut:
I always have issues with Elite. It always reverts back to standard after reboot for me.

Sent from my Motorola StarTac using Voodoo
[Android Apps and Games] brandall:
I had weird issues where it used the old icon, then the new one, then reverted to the old version... at which point I uninstalled!
[Android Apps and Games] azj:
Thanks. These weren't ticked but are now.
[Android Apps and Games] nobnut:
You are now an Android God!

Excellent. I won't be online much for about 12 hours but if you need help tomorrow, by all means send me a pm or post here if I can help you :)

Sent from my HTC Flyer using vodka
[Android Apps and Games] azj:
time_in_state already had the "other" read permission ticked. Just for kicks I un-ticked, saved and re-ticked the permission. I still get a file read error when running DSDAdhoc.

Neither wake_lock nor wake_unlock had the other permission ticked but they do now.
[Android Apps and Games] nightranger73:
I know it's different but can I point you out on that:

http://xdaforums.com/showpost.php?p=15619173&postcount=7058

Well... it works and helped me really a lot finding rogue apps on sleep.

The question is... how is it possible to read mW values from single process? And even distinguish between CPU/LCD/WiFi/data consumption for each process? That would be an useful addon to ds detective

Consumption report

XDA app alone

Sent from my GT-I9100

If you find this post usefull please press the "Thanks" button
[Android Apps and Games] brandall:
Thanks for sharing this nightranger73 - I'm making good headway on discovering where such details are hiding. As the versions go on, I intend to get up to this standard!

Damn it! Thought I'd solved this.... Can you work backwards from the file and check the permissions on each of the folders - make sure 'other' is ticked on each... It's only a 3 minute job...

Anyone have any suggestions of a chmod 777 command that could make sure all permissions are there?
[Android Apps and Games] azj:
I backed out from time_in_state and verified that all its parent folders have read ticked for other.

Nothing is being written to the Reports folder.

Also uptime is still not found:

REPORT START
-------------------------
Wed Jul 13 11:17:03 MST 2011
uptime: no such tool

"toolbox uptime" returns not found while busybox does work. Same results with and without running su first.
[Android Apps and Games] brandall:
Damn it! :mad:

Unfortunately, you seem to have all the problems I need to fix! I will be uploading standard binary soon so 'toolbox uptime' or 'DSD uptime' as it will be then will provide the desired output.

To resolve this in the short term, please navigate to /sdcard/DSD/wlapp.sh and edit the text from 'toolbox uptime >> $log' to 'busybox uptime >> $log'. That may not return useful information, but it won't kill the script.

I'm very puzzled - the main controlling task DSDDO also reads from

/../../sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state

Does this not error for you every time too???

Are the profiles performing normally for you apart from when you try to run DSDAdhoc??
[Android Apps and Games] nobnut:
Might including a 'common' Busybox be a solution? I know it was suggested previously. It might save you a whole tale of woe.

EDIT: Oops. I think that is what you just said...

I'll just get my coat.

Sent from my HTC Flyer using vodka
[Android Apps and Games] brandall:
Evening!

LOL! - It was sort of what I said... Busybox has gone down a different road to the binary present in most (it would appear) devices, therefore extracting the binary from my device and renaming it to DSD will enable the command line of 'DSD uptime' to return the desired output.

I think you knew this... but I don't understand how to get my 'uptime' to point to the renamed 'DSD' instead of 'toolbox' and I'm stuck until Pulser returns from his sandcastle adventure.....
[Android Apps and Games] azj:
I've changed the script to use busybox uptime. Manually executing it returns a useful line of info.

DSDDO and DSDAdhoc both return the file read error. DSDAdoc also then returns a second simple read error popup.

I'm not sure how to determine if the other tasks/profiles are operating normally. I could manually execute each task and report any errors. The profiles only kick in under specific conditions, right?
[Android Apps and Games] waydownsouth:
/sys is a virtual filesystem & gets recreated at each boot... so, setting perms via root explorer is only temporary until you reboot...

You'd need to put it into a script that runs at boot to correct the permissions.

something along the lines of:

chmod o+r /path/to/file

HTH :)
[Android Apps and Games] nobnut:
Evening ;)

I thought we tried that before... I haven't re-read Pulser's earlier post but I recall him saying something to the effect of as long as they're both in $Path and named uniquely that it should all be bada bing. Seems like that's not tickety-boo however.

*I really must stop using such arcane and silly language.

Pulser is around a lot in his thread, in fact he's been 'spamming' it today. You could chance your arm and drop the old bean a pm. I will if you want but he knows I'm retarded. Let me know if you want me to.

I'm really impressed with DSD. It's fantastic. I've found some really tiny issues but I'm going to hold off reporting them until I have wiped and reinstalled DSD and verified that it isn't me (or my phone) messing up the installation.

Tally Ho! Chin chin!

EDIT: ^^^ Hi waydownsouth. Mightily impressed with tweaKr also! I'll drop you a brief update when I wake up. Nothing else to report really. Excellent work.

Sent from my HTC Flyer using vodka
[Android Apps and Games] pulser_g2:
The command "uptime" is usually symlinked to busybox or toolbox.

Ie. I run "busybox uptime" to see uptime from busybox. If I renamed the busybox binary to bob, then command is "bob uptime"

If you can run "which bob", and it finds it, then it is in your path correctly.
[Android Apps and Games] nobnut:
Thank you Pulser and Waydownsouth. You guys are amazing.

Sent from my HTC Flyer using vodka
[Android Apps and Games] azj:
Executing the tasks manually:

DSDAdhoc: Read paragraph: file not found time_in_state folowed by a Data Read Error error.

DSDDeviceBoot:Missing Shutdown file error

DSDDO: Read paragraph: file not found time_in_state

DSDFileSetup: Unable to create Reports folder error if folder already exists. Runs successfully if I delete the Reports folder first allowing it to be created.

DSDShutdown: Read paragraph: file not found time_in_state. Task appears to then hang, possibly trying to write DSD-Shutdown.txt since that never gets created.

All other tasks run to completion with no error messages.
[Android Apps and Games] brandall:
DSDDO is the brains of the operation, so if that's not functioning for you then there's little going on behind the scenes. Can you try waydownsouth's command in the terminal and see if that makes a difference please - I can't think of another reason why Tasker can't read it... :confused:

I was hoping you might be around when I mentioned the need for a command! Thank you :) If the above doesn't work for azj, can you think of another reason how the output can be viewed in the terminal but not by Tasker...?

I can't....

I'm not sure I'd understand you if you didn't ;)

EDIT! Typing DSDBIN uptime gives no tool found.... Ignore my previous comments if you read them, they were nonsensical ..... [note, I renamed toolbox to DSDBIN. Typing 'which DSDBIN' returns /system/bin/DSDBIN]

Rather!

EDIT: I've run out of thanks meter thanks to use for everyone!!!
[Android Apps and Games] brandall:
Thanks for reporting back - as in the post above, can you try the permissions command in the terminal and see if that gets Tasker read access please
[Android Apps and Games] azj:
The chmod command returns Bad mode. Also tried chmod o +r time_in_state with same Bad mode result.

Interesting factoid: In Terminal I manually tried to work my way down to the time_in_state file first so I could have the output of PWD on the screen before I did the full chmod command. I could not change into the stats folder until I executed su.
[Android Apps and Games] brandall:
Hmmm... Did you get 'su' before running the chmod command?

I've messaged waydownsouth to shed some light...
[Android Apps and Games] nobnut:
Yes, the notification is triggered on reboot.

Done. Same deal without the lines taken out. The text file is written as before.

With the lines removed, same as before also ("DS Boot Report: 0%"). But it would be as we tried that one.
[Android Apps and Games] brandall:
Ok, this is making more sense to me now - DS Boot Report: 0% is expected with the lines removed - I thought you meant you were still getting the failure notification too.

When you get a chance, could you delete DS-BootReport.txt again, reboot and then post the file please. I'll be able to tell from the content how far along the task it's getting before the reboot is shutting it off.

Is your device an SGS2? I wondered if a faster device (than my Desire) would shut down more quickly, or whether it would be comparable and perform the task more quickly... :(

Do you have any other Tasker profiles that run on shutdown? In the properties of DSD-Shutdown, did it keep the launch priority to 10 when it was imported?
[Android Apps and Games] nobnut:
Hi, I'm back at my desk now and will follow your instructions above.

Yes, I am using an SGSII and yes, it shuts down and boots extremely quickly. I have just timed it (if you want to know). Shutdown in about 5 seconds. Boot from cold in about 12 seconds.

Anyway... thanks for this, I will go and experiment.

EDIT: I have no other shutdown profiles running. Just some startup ones.
[Android Apps and Games] nobnut:
I've just tried, again using your DSDReport-V2. I can't post the .txt file as it hasn't written one. Upon reboot, I get a 'DS Data Failure' statusbar notification but then I get the option to clear or view the .txt file... if I select view, I get a toast notification telling me it doesn't exist.

There is no file written to the card now. I am guessing that the previous one must have been written when su was being granted.

I will keep trying.

Edit: No joy :(
[Android Apps and Games] brandall:
Damn your SGSII which is much better than my phone! :jealousface:

Below I've uploaded a new version of DSDReport and DSDDeviceBoot. I really don't think I can speed the DSDReport up any more than that now, so if it doesn't work, it's back to the drawing board for the daily report!

It's my error that the view file prompt is appearing when the file hasn't been written - the goto action should have jumped over that... I've changed it around.

Appreciate this - your thanks meter is increasing...
[Android Apps and Games] nobnut:
You my kind Sir, are a Gent!

I will set it up again, test and report back.

Thanks
[Android Apps and Games] nobnut:
Damn. No difference at all. No .txt file written and the same error on startup ('DS Data Failure').
[Android Apps and Games] brandall:
Damn it! :mad: I was really hoping that was going to be good news...

One last request for now please... Can you drag the variable set %DSBOOT to the first action in DSBootReport - That way the text file will be triggered regardless and at least we can see how far through the task it's getting....

Just paste the content if it's easier than posting the file...

Thanks
[Android Apps and Games] nobnut:
As requested:

---------------------
---------------------
Date | %DSDATE |
Time | %DSTIME |
DS against total uptime |% 0% |
DS against total DSP time | % 0 |
Total Display off time | %DISPOFFTD seconds |
---------------------
---------------------
---------------------
---------------------
Date | %DSDATE |
Time | %DSTIME |
DS against total uptime |% 0% |
DS against total DSP time | % 0 |
Total Display off time | %DISPOFFTD seconds |
---------------------
---------------------
[Android Apps and Games] brandall:
Thanks - that's pretty conclusively nothing!

I'm surviving on not much sleep at the moment and it's starting to show - Why am I try to squeeze all the maths in before shutdown :confused: Why aren't I just gathering the data I need and performing all the maths when the device next boots up... :o

Time for a coffee and full version 2! Thanks again for testing this and prompting common sense out of me!
[Android Apps and Games] nobnut:
Lol

Hey, if it was that easy, someone would have done it already. Looking forward to v2.0

Thanks again.

EDIT: I'm AFK 'til tomorrow.

Sent from my Motorola StarTac using Voodoo
[Android Apps and Games] brandall:
V2 Up!

True! V2 Up on your return...

[B][U]V2[/U][/B]
* Changed 'between boot report' maths to boot instead of trying to rush them in before shutdown
* Used locale/linux to perform some of the maths as I assume it's quicker?
* Cut down task sizes due to above
* Altered structure of output files for easy reading
* MASSIVE boot task that hurt my brain

Let me know your feedback folks!
[Android Apps and Games] nobnut:
Hi, thanks for v2.0. Here's my feedback.

I installed as per instrucions and selected each task, tested and granted SU where appropriate.

Three files have been written to the SD card: DeepSleepDetective.txt, DSD-Shutdown.txt and DSD-Uptime.txt.

I rebooted and cleared the contents of the files.

I rebooted a couple of times and then left the phone. I saw in battery usage that something was waking my phone for very short periods every 5 minutes or so (as normal). Nothing had been written to DeepSleepDetective.txt however :(

I then rebooted (in case the file wouldn't be written until after reboot) and the same thing happened.

At no point do I see any notifications.

Here are the contents of my files:

DSD-Shutdown.txt

07.38
791
%DISPOFFT
6-28-11
5148
07.53
838
%DISPOFFT
6-28-11
3672
07.53
878
%DISPOFFT
6-28-11
3816
08.20
1605
%DISPOFFT
6-28-11
14256

DSD-Uptime.txt (Just after a reboot)

1872

DSDSleepDetective.txt

[I](File empty)[/I]

I hope this helps.