yashsingh1/xdaforums huggingface dataset:
[Android Apps and Games] brandall:
Chuckle... I'll look forward to the puppy, thanks :)

For V14 I'll have to put something in to ensure a text editor is already installed... hmmm... How the hell am I going to do that....?

Anyway, please continue to refuse to Nandroid - these risks in life are the only way to make us feel truly alive... (and occasionally very frustrated).
[Android Apps and Games] strictlyrude27:
I haven't gotten to work on any Tasker projects and such on my own lately :( I do plan on rocking DSD again, but I kind of want to wait until Tasker 1.2 is in beta.. apparently there will be support for "projects"? hopefully?
[Android Apps and Games] nobnut:
Right, I installed it again and all went well... again.

Yes, the Readme addressed me as 'nobnut' (I would have preferred 'Sir Nobnut' ;)).

Just one thing I noticed, this also happened yesterday on v13 but I forgot to mention it. After set up, upon reboot, there is a statusbar notification showing a boot report is available. When I clicked the report 'link'... no report opens. This happens on subsequent reboots also. I hanve checked in the DSD folder and there is a DSD-BootLog.txt with a corresponding number of entries in it but the Reports folder is empty. I don't know if this is normal or not.

I will now leave the device/play some media etc to test and email you the report later.

EDIT: PM sent with a link to all the reports etc zipped up.
[Android Apps and Games] brandall:
Cheers Sir Nobnut (I'll correct that in V14), I'll check my pm shortly. The notification click only working when it wants to is annoying and I couldn't solve it... Perhaps adding a +1 here would help http://groups.google.com/group/task...8f0bf7886a538?lnk=gst&q=woes#5058f0bf7886a538 Making sure accessibility is ticked under Android settings or adding %NTITLE into a random notification text field can kick it into life...

The reports folder will populate with any errors or previous logs, so the fact that it is empty is good news!

Cheers for your testing. I may have an update to the dsd.sh file to post soon as the historic wakelocks aren't populating always.. :insertsuitableemoconhere:
[Android Apps and Games] brandall:
Excited to see what 1.2 will bring - anything to make structuring these mass profiles easier would make life easier!
[Android Apps and Games] brandall:
Cheers for the log Sir Nobnut.

In yours and others I've got, it's not picking up the ROM version correctly, resulting in the data being misaligned.

If you (and anyone else) has a mo, could you type getprop into a terminal and see what line your custom ROM description appears on please.

Mine is after ro.modversion, but it appears no one else's is!

Thank you thank you in advance...
[Android Apps and Games] bgx:
Found a problem brandall! I think this problem we had before?

When I import the task DHDAhTIS my tasker force close!
[Android Apps and Games] nobnut:
Mine is [ro.build.display.id]: [xxxxxx]

EDIT: This is obviously the same as the line in the build.prop
[Android Apps and Games] brandall:
Hmmm.... Are you definitely running the latest Tasker version??
[Android Apps and Games] brandall:
Thanks, but damn... mine doesn't show the ROM version next to that... Is it anywhere else in the output? I best check where devs are supposed to put it, as it maybe a chef error...
[Android Apps and Games] nobnut:
See my edit... that is the line from the build.prop. What does your build.prop say next to that line assuming you have one?

EDIT: Nowhere else in the getprop output.
[Android Apps and Games] brandall:
Saw the edit cheers - getprop is just the easiest way to view the file contents in the terminal.

I've Googled the 'correct' place to name the ROM in the build prop, but strangely no clues... I guess it'll come down to where it is 'usually'.

Mine says the device model on that line..

Can anyone else let me know their results please??
[Android Apps and Games] bgx:
Yes ver 1.1.1u2
[Android Apps and Games] brandall:
When you view your task list in Tasker, is it already there?
[Android Apps and Games] brandall:
It appears that ro.modversion that I'm using is a CM only thing to identify chefs that mod their source.

Quite why the ro.build.display.id then isn't populated with the same info is a little annoying...

Guess I need some sort of null check on the output...

If you get a mo Sir Nobnut, in the dsd.sh file in the DSD folder, can you edit the line that says ro.modversion to ro.build.display.id and then run the email log task pretty please......? Just want to make sure that aligns the output correctly...

Thank you thank you.

EDIT: Do you get any output from gretprop | grep ro.modversion ? I hope not...
[Android Apps and Games] bgx:
After import DHDAhTIS I can't view task list, because when I hit task list, tasker forced close!
[Android Apps and Games] brandall:
Ok... In a file explorer, can you navigate to sdcard/Tasker/ and long click on userbackup.xml and view the properties.

What is the size of the file?
[Android Apps and Games] bgx:
userbackup.xml is from the day before yesterday size is 158782 bytes

don't think that this is the reason, because when I reload my backup tasker work again!

Edit: Same problem when I try to import DSDSetup.tsk!
[Android Apps and Games] brandall:
Well I'm glad you took a recent backup! Can you reload the backup, then check your task list to ensure no DSD tasks remain. Can you also delete any DSD tasks/profiles from the Tasker folder on the sdcard.

Then can you first try and import one of the tasks that had previously crashed Tasker.

If the same result, can you open the backup file (on your pc maybe easier) and do a search for 'dsd'. I've had skeletons in my backup before...

Failing that. Ensure your backup is safe and wipe all data from Tasker (this shouldn't wipe the files on the sd).

Try importing the files from a fresh install as you may be hitting the data limit halfway through importing (this has also happened to me).

I hope one of these things resolves it! I'm particularly interested to known if you have any skeletons, as I reduced my backup by nearly half its size by clearing all data and re-importing all of my tasks/profiles and then taking a backup... I was going to report it to the dev.

Let me know!
[Android Apps and Games] bgx:
Huh thanks! Gonna try that and report back! ;-)
[Android Apps and Games] brandall:
You're a gent Sir Nobut

So, looking at the two outputs, it appears I'm best to check for the existence of ro.modversion, if it's not there, then instead go for ro.build.display.id

I need to segment the data differently too as there's no [ and instead an =

*sigh*

Time to pull out a little more hair working out how to do it... I really would have thought ROM version would be an easy thing to extract...

I'll be back!
[Android Apps and Games] nobnut:
Catch you later Arnie!
[Android Apps and Games] brandall:
Windows phone 7! You are a device addict....

One more favour on your return pretty please...

I need the ROM details starting after the '='

In the terminal can you type:

getprop | grep ro.build.display.id

To show the full output.

Then:

getprop | grep ro.build.display.id | awk '{ print $2 }'

To show the segmented output.

If the above displays only everything after the '=' then result! Otherwise, can you try:

getprop | grep ro.build.display.id | awk '{ print $2,$3 }'

Or maybe:

getprop | grep ro.build.display.id | awk '{ print $3,$4 }'

Or maybe just:

getprop | grep ro.build.display.id | awk '{ print $3 }'

Until you hit the output jackpot after the '=' !

Thank you thank you.

I shall be booking you an appointment to see my secretaries....
[Android Apps and Games] bgx:
Think you're right! After try a lot more to import getting the error on different tasks! Think I have to much tasks and when puffer is full tasker forces close!

Have try reinstall but the error is the same! :-(
[Android Apps and Games] nobnut:
Brandall, I'll give you the output in the morning. I'm Android free tonight. Can I see the Brunette first please?

BGX, I know what you mean. I'm always having trouble with my puffer. I'm going to see a doctor about it soon. I'm worried about a prolapse.
[Android Apps and Games] bgx:
Woooh :'( Don't become the last task imported! Yeah nobnut please take my tasker to the doctor too! :'(
[Android Apps and Games] brandall:
Chuckle.... I'll look forward to your return in the morning.

Ps. I hope you're not having a WP7 evening....
[Android Apps and Games] brandall:
Ok bgx, I need you to do some house-keeping when you have 20 mins spare....

Please restore your original back up file. Then on the sdcard using a file explorer, rename the current userbackup.xml to userbackupZ.xml.

Then rename the folders Tasker/profiles to Tasker/profilesZ and Tasker/tasks to Tasker/tasksZ - this will ensure that you can re-rename your backups and folders at any time and return to where you were.

The problem is that Tasker can only handle a certain amount of data in collective tasks and profiles. This is something I know the dev curses as it was an early development decision, but what I want to capture is that the userbackup.xml file is storing too much additional data which is compounding the problem.

Once you have renamed the above file and folders, from Tasker click on every profile you have and select export to sd. Then from each of your tasks, press the menu hardware button and export each of those.

Then, clear all the data from Tasker.

Then, individually import all of the profiles and tasks that have populated the new (automatically created) folders Tasker/tasks Tasker/profiles.

Then take another backup.

Then post the size of the original backup (Z) and new backup!

This should then create enough space to import all of the dsd profiles and tasks without errors....

In theory....

Have fun! ;)
[Android Apps and Games] nobnut:
That's some Dev love right there ^^

Many others couldn't give a monkey's bunghole about users. Credit to you Sir.

In answer to your earlier question. Yes. I am a WP7 user now. I still play around with Android and use a tablet fairly often, but my daily driver (as they say) is a Windows Phone.

I'm the only one in the village!
[Android Apps and Games] brandall:
I am passionate about monkeys bungholes....

You were the only one in the village prior to, well, technology in general... ;)

Some very clever person who shall remain nameless (waydownsouth) has pointed out on email (to save my embarrassment) that simply entering getprop ro.build.display.id in the terminal will supply the required output without the need for any American currency tricks...

I really wondering if I should really publish the beginners guide to shell and Tasker that I'm half way through!
[Android Apps and Games] nobnut:
Shhhh! That was a secret.

I was wondering where you were going with the above. I blame the hallucinogenic substances you've been imbibing.
[Android Apps and Games] brandall:
If I don't have my daily imbib, I just don't feel right!
[Android Apps and Games] Blinkydamo:
Hi all,

Got the deep sleep installed and running but not sure what to make of the messages I get. Could someone tell me what they mean?

Getting 96% of dsp and ut @ 94% after 3 hours. Most of the messages are around the same values.

Cheers

Blinky
[Android Apps and Games] brandall:
Hi Blinky

DSP is Deep Sleep Potential, which is when your device could shut down the cpu and enter deep sleep. So, 96% of that is very good and your device is behaving as it should. However, if a rouge application leaves a process alive you will see this percentage drop or you'll get an alert if it's causing enough of a problem.

UT is the uptime of the device, which simply means how long since your last boot. A comparison of deep sleep to this is not really a true reflection of how your device is behaving, as if you've been using it, it will be very low! It's there for comparison purposes as some other apps only show that info, which can lead you to believe your device isn't sleeping when it should.

Hope that explains it for you. Any further questions, please do ask.
[Android Apps and Games] Blinkydamo:
Cheers for the info on that, makes sense now. How do I know what applications are keeping the CPU awake the rest of the time?
[Android Apps and Games] brandall:
The 4% of DSP you are losing is negligible and may well be down to the wakelock Tasker is holding (as part of the profile) for 10 seconds after the display is turned off to check what others remain at that point.

You'll get a notification and directed to a text file detailing the process/app if something is detected.

If you want to test it's working, go to your music app and start playing an album. Press home (which will prevent Tasker from logging the foreground activity) and then turn your display off for 7 minutes.

Turn it back on and you'll see what the app/profile has detected!
[Android Apps and Games] nobnut:
... like magic.
[Android Apps and Games] Blinkydamo:
Hiya, run the music app in the background with the screen off, when I turned the screen back on it stated something wad wrong and said gathering evidence. Once this finished it told me the click the notification to see the report. Upon doing this nothing was displayed, am I doing something wrong?

Cheers for all your help.
[Android Apps and Games] nobnut:
I have a similar issue which I reported to Brandall. I believe he's working on a fix :)
[Android Apps and Games] brandall:
It's an issue with %NTITLE that is out of my control... I've posted the problem to the dev, but it persists to only work sometimes... Can you make sure Tasker is ticked under the Android accessibility options - it definitely won't work if not. That option randomly becomes unticked which I've also reported...

Clicking the notification should open the file /sdcard/DSD/deepsleepdetective.txt. You can manually open it in a file explorer.
[Android Apps and Games] nobnut:
Absolutely. I can attest to the unticking issue. It is strange. It has only happened once to me though.

Thanks Brandall.
[Android Apps and Games] fsmith3x:
A little help please...

Good evening gang!

I've got a real mystery here. DSD on my Photon is telling me the phone never sleeps.

DSD always reports |No DSP|Charging|. Even though the phone hasn't been on a charger in hours.

The DSP.txt file shows:

UPT || 02:11:00 || 0%

DSP || 03:25:00 || 0%

With only one wakelock holder is net.dinglisch.android.taserm.

Any thoughts?
[Android Apps and Games] nobnut:
Weird. It sounds like DSD isn't working correctly on your device, rather than your phone never sleeping. Possibly uninstall DSD fully and reinstall it from scratch and see if the problem persists. Maybe a task or profile was missed upon install.

If that fails, post your log and we'll see what else we can try.
[Android Apps and Games] brandall:
It's not a glitch I've come across before, but somehow Tasker hasn't recognised your charger being removed.

If you go into the variable editor in Tasker and clear the variable %CHRG, that should do the trick.

If it occurs again, can you unplug and replug your charger and confirm if there's a glitch with your device and Tasker not being able to detect it.

Let me know!
[Android Apps and Games] fsmith3x:
That's better

Thanks guys! It just needed be put on the charger again.

I'm still getting "Deep Sleep Prevented | 0" whenever there is a report.

Here's what the beginning of the report says:

-------------DSD-------------

UPT || 10:35:00 || 0%

DSP || 01:10:00 || 0%

-------------DSD-------------

REPORT START

-------------------------

Fri Dec 2 06:56:30 EST 2011

up time: 10:35:44, idle time: 15:01:05, sleep time: 00:00:-2

Wakelock Holders

-------------------------

net.dinglisch.android.taskerm
[Android Apps and Games] brandall:
Something doesn't look right with your binary output there... Can you go into the task DSDErrorLog and press the play/test button and then email me the output please.

I'll take a look...
[Android Apps and Games] nobnut:
Oooh! Look at you and your Beats Audio paraphernalia! Whatever next.

lol
[Android Apps and Games] brandall:
Sorry, you'll have to type in capitals from now on, I can't hear very well... The bass line in thebestofdubstep8 has burst all three of my ear drums...

BooyakashA!

Eye.
[Android Apps and Games] brandall:
The log you emailed over shows your output from 'toolbox uptime' is ending with ':-number'. That's not something I've seen before... Strange.

Can you go into the task dsdahoctis and press play in that and let me know if you get an error or a toast of your stats.

Cheers
[Android Apps and Games] fsmith3x:
That ':-number' is up to '-14' now (or down to, since it's negative) ;)

I see a DSDAhTIS task here. Running it gives me no errors and displays:

UPT || 41.33.00 || 554%

DSP || 109.41.00 || 20%
[Android Apps and Games] brandall:
Hmmm... I'm puzzled as to why the binary doesn't work on just your device...!? Plenty of other downloads throughout the 13 versions and you're the first!

Anyway, for now, can you reboot and wait 15 mins plus and run the adhoctis task again for me please - let me know what it reports.

All tasks that end in 'tis' run if the binary fails. Unfortunately, I didn't add in any safety-nets for the binary working, but reporting rubbish! Damn...

Should've include a manual 'switch to tis only' button...
[Android Apps and Games] fsmith3x:
How's this?

UPT || 00:21:00 || 83%

DSP || 154:00:00 || 0%

I'm beginning to think the phone has 'issues'. This is a freshly flashed stock rom with very little tweaked and added to it. I've been trying to track down this wakelock issue for a few weeks now and thought I'd try your scripts.

Nice work btw.
[Android Apps and Games] brandall:
Not great! But lucky for you I like a mystery....

Ok, I'm falling asleep, so will post some further instructions tomorrow - in the mean time, if you want to flash a different ROM to rule that out, that'd help - no worries if not, we'll solve anyway.
[Android Apps and Games] brandall:
Firstly, can you enter this in terminal:

cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state | awk '{sum +=$2/100} END {printf "%.0f\n", sum}'

and let me know the output please
[Android Apps and Games] fsmith3x:
Well that was disappointing. After ALL of that typing I got...

718

I expected so much more! ;)
[Android Apps and Games] brandall:
:) Well you'll be pleased to know that it was what I was after!

To make it easier for you, I've attached a text file, so you can copy directly into the terminal/adb.

Now these please:

cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state > /mnt/sdcard/dsdtest.txt

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies >> /mnt/sdcard/dsdtest.txt

cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state | awk '{sum +=$2/100} END {printf "%.0f\n", sum}' >> /mnt/sdcard/dsdtest.txt

The ouput will be stored in the file sdcard/dsdtest.txt - can you copy and paste the output please or attach the file if it's easier for you. Cheers
[Android Apps and Games] brandall:
Sir Nobnut

If you're around Sir Nobnut, can you test this for me if you have a moment please.

This command will run at screen off and capture wakelock count in a text file:

awk '{ if ( $2 > 1 && $9 > 1 && $3 > 1 ) print $1,$2}' /proc/wakelocks > /mnt/sdcard/wakelocktest.txt

awk '{ if ( $2 > 1 && $9 > 1 && $3 > 1 ) print $1,$2}' /proc/wakelocks > /mnt/sdcard/wakelocktest.txt

Then this command will run at screen on to see which ones have been active during the screen off time:

awk 'BEGIN {while (getline < "/proc/wakelocks"){arr[$1] = $2}} {if (arr[$1] > $2 ) printf "%-20s %5d %.0f\n",$1,$2,arr[$1]-$2 }' /mnt/sdcard/wakelocktest.txt

awk 'BEGIN {while (getline < "/proc/wakelocks"){arr[$1] = $2}} {if (arr[$1] > $2 ) printf "%-20s %5d %.0f\n",$1,$2,arr[$1]-$2 }' /mnt/sdcard/wakelocktest.txt

Can you bung the first one into the terminal/adb to populate the text file and then keep executing the second one to see if the values are increasing for you please? - You don't need any screen off time, as the device being awake whilst you do this should hopefully provide sufficient active wakelocks...

Let me know captain!
[Android Apps and Games] fsmith3x:
Ok brandall, here's what I got (fyi, I did flash a new rom and haven't installed many apps.)

216000 1940347

456000 1802253

750000 195846

1000000 100018

1200000 61122

1300000 278418

216000 456000 750000 1000000 1200000 1300000

43819
[Android Apps and Games] brandall:
Great thank you - That's confirmed your device can use all of the 'tis' tasks and DSD will function correctly.

I'll have a ponder about how I can redirect all of your tasks to do this without you having to adjust them manually. I'll definitely add this into V14 in case other users suffer the same issue.

In your new ROM, is toolbox uptime (in the terminal) still providing strange output? If you go to your device settings/about phone/Battery is the Up time reporting correctly in there?
[Android Apps and Games] fsmith3x:
Uptime in the battery stats is reporting correctly, unfortunately I'm still getting the strange output from toolbox. A bad battery wouldn't be the source of this would it?
[Android Apps and Games] brandall:
No, it'll just be some incompatibility with your device and the binary - no idea what though.

I'll be back with a solution soon - In the mean time if you change the perform task action near the end of DSDDispOn to perform DSDONTIS and the same in DSDDispOff to DSDOFFTIS, that should give you some more working functionality for now.
[Android Apps and Games] fsmith3x:
Bingo! That fixed the reporting. Now back to figuring out these wake locks! (ugh)

Kudos Sir! Thanks for your help.
[Android Apps and Games] nobnut:
Blimey Governor, I've just seen this and will have a bash tomorrow if I can. I've been waylaid (not laid) in hospital. With a damned lurgy.

Yours as
[Android Apps and Games] nobnut:
Sorry for typos ^^. I can't edit it for some reason :(
[Android Apps and Games] nobnut:
Sorry for the delay Chief.

I ran these several times over as I didn't get the outcome I was expecting. Following he first command, the content of the wakelocktest.txt file was:

name count
"mmc_delayed_work" 5
"prx_wake_lock" 4
"svnet" 32

And executing the second command, time after timer after time, yielded no further information being written to wakelocktest.txt, but I received the following in terminal each time I ran it (yes, the values were identical):

'mmc_delayed_work' 51
'sunet' 32 2

So what I saw after a few times executing it was:

'mmc_delayed_work' 51
'sunet' 32 2
'mmc_delayed_work' 51
'sunet' 32 2
'mmc_delayed_work' 51
'sunet' 32 2
'mmc_delayed_work' 51
'sunet' 32 2
'mmc_delayed_work' 51
'sunet' 32 2
[Android Apps and Games] brandall:
Sh*T are you ok??? You back on your feet now?
[Android Apps and Games] nobnut:
I'm dandy now thanks. I had a nasty bug of some kind whereby I couldn't keep my balance and it also caused stomach problems. Lots better now thanks.
[Android Apps and Games] brandall:
Sounds nasty... I can empathise as I once got so drunk I **** myself... Glad you're on the mend!

Thanks for posting the results above... Odd that the count didn't increase... Damn it! The first command should have captured data and executing the second should have picked up the wakelocks that increased from the count in the file... Hmmm... Perhaps your device simply wasn't doing anything in the background...? I'll ponder... Thanks again.
[Android Apps and Games] nobnut:
'Pappering' your tweeds is a nice touch, but the pros go for the 'Grand Slam'... pee, puke and crap, all in one go. That's classy!

I will try the command on another device in a while. Just to emphasise, the second command didn't populate the file. The results were given in terminal.
[Android Apps and Games] brandall:
I do try to achieve that every New Year's Eve, but I always seem to get arrested before I manage it... Perhaps 2011/12 will finally be my year...

Thank you thank you - You are correct about the file not being updated, that will be the screen off data capture only - the second command will run on screen on and populate the log file only if the count has increased... That's the plan anyway... :eek: