Develop Bugs

[APP] 100 Pushups - Beta - Stage1 - 0.1.9 [23/07/2010]

As requested I have begun development on a windows mobile version of a program on the iphone called "100 Pushups"
Web Link: http://www.hundredpushups.com/.
The idea of the application is to put you on a 6 week program which will lead you to being able to perform 100 push-ups. This is achieved by performing so many reps, for so many sets, 3 times a week. At the end of each week you will be tested on how many you can do and then a program is worked out for the following week. You can track your progress via bar charts and logs.
GUI PREVIEW VERSION ADDED. SEE POST #115 -(UPDATED 20-09-2010)
There will be 3 stages of the development of the program.
Stage 1 - Functionality.
At this point all I am concerned about is "does it work?". This means the GUI will probably look rubbish but the idea is to ensure the program is doing as it should.
Stage 2 - GUI
Once I'm happy with stage 1 I will begin developing a nice GUI to make a better user experience and to make the program look half decent
Stage 3 - Final
This is the point where I will start adding people's request/suggestions, fine tuning etc. Once done the version will then end Beta and become final build.
See Post 2 for changes log
Requirements:
.Net 3.5 for Windows Mobile
Developed for Windows Mobile 6.5.3. Not sure if it will work on anything less.
Example on how to use
Lets say you start this program on a Sunday
Sunday - Perform as many "good form" push-ups as you can and enter value.
Monday - Do first day Program.
Tuesday - Rest
Wednesday - Do second day program.
Thursday - Rest
Friday - Do third day program.
Saturday - Rest
Repeat.
Using the above example, every time you get to Sunday you will be required to enter a new value. This will set the program up for the next weeks training.
NOTE: First Release - Please take the following under consideration before testing.
# This is at Stage 1 so yes it will look rubbish! lol
# The "Good Form" button is disabled at the moment so pushing it will do nothing.
# If the program is in first run mode i.e no push-ups have been logged, pushing the graphs button will display random data. This is just for beta testing.
# This was developed and tested on the HTC HD2 only. I'm not sure what it will look like on other devices as I have none to test with.
# Upon first launch a log file will be created in \My Documents\PushupLog\. I suggest backing this up when trying new versions of this program as it contains all your progress!
# The Graph may not display correctly on other devices and I'm already working on fixing that.
# To clear all the data simply delete the log file located in "\My Documents\Pushuplog\log"
NOTES FOR STAGE 1 BETA TESTERS
If you press the menu button you will notice a sub menu called Debug. Here is an explanation on what the options are.
# Reset Timer - In the "Todays Program" screen, pushing this buttons will set the rest timer to 2 seconds. This is if you wish to quickly skip through the rest periods.
# Maximize - Basically just makes the program full screen (covers top task bar).
# No Limit - Check this if you want the program to ignore when you can perform the next program.
IF YOU ARE UPDATING FROM VERSION 0.1.7 OR BELOW PLEASE DO THE FOLLOWING
# Uninstall previous version.
# Go into "\Program Files" folder and delete folder "Pushups". There also maybe a file in the "\Program Files" folder called "100 push-ups - beta", delete this too.
# Go to "\My Documents" and delete the folder named "PushupLog"

Release Log
# 0.1.9 [23/07/2010]
- Added "No Limit" option to Debug menu. Pressing this will cause the application to ignore rest periods between programs. i.e You don't have to wait a day before continuing.
# 0.1.8 [22/07/2010]
- Fixed various issues with resetting log.
- Fixed Graph layout.
- Fixed issue where entering a test value and then resetting the log to a forward date would cause the wrong push-up program to be loaded.
- After performing a test and entering a value, the program will now not allow you to continue with "Todays Program" until 24 hours has passed.
- After completing push-up program for today, you must wait a day before continuing to the next program. This is so you get enough rest.
- After performing a test and entering a value, the new weeks program is added to the calender. Resetting the log will also update calender (not fully tested).
- Added basic Log View which can be accessed via "Logs and Graphs" button.
- Pushing "Rep Completed" button will cause "Perform X Pushups" text to change to "Rest Period".
# 0.1.7 [18/07/2010]
- Reset now only enabled in Main screen
- Fixed issue where entering Test value and then resetting log forward a day, causes you to enter test value again.
- Fixed issue where partially completing today's program and then returning back cause's the display of completed reps to be incorrect.
# 0.1.6 [17/07/2010]
- Complete re-write of log recording. (You old log file will be ignored if present)
- Added "Reset Log" to menu button.
- Added feature to reset log progress back and forward to any given week and week day. To reset log just select "Week 1 and Day 1".
- On first run, if you enter more than 20 on the test screen the program will move you to week 3
- Short cuts now in "Programs Folder" and "Start Menu"
- Program now remembers what set you was doing if you leave "Today's program" and then return back to it. NOTE: this only works while the program is running. You must restart sets again if you close the application.
# 0.1.5.40968 [13/07/2010]
- Removed top and bottom grey tabs to improve layout for low res screens.
- Added Menu button
- Moved Debug --> Rest Timer to Menu button
- Added Maximize to Debug in Menu button. Pressing this will maximize the application which hides the top bar in windows mobile. Press this button again to go back to normal view.
- Added Exit button to Menu button
- Added count down timer sound for stop watch/rest timer. Should kick in at about 6 seconds remaining
- Moved return button to bottom right
# 0.1.4.37187 [12/07/2010]
- Fixed various issues with logging.
- Fixed issue where entering test value and then exiting "Todays Program" will cause you to enter test value again.
- Fixed error occurring when repeatedly pressed "Reps Completed".
- Fixed error occurring when pressing "Return" button while rest timer is activated.
- Developed at 240 x 260 resolution so hopefully any display greater will work ok.
- Added debug Menu with item "Rest Timer". NOTE: Checking this item at the main screen will set the rest timer to always be 2 seconds. This is for people beta testing that want to speed up the rest periods.
# 0.1.3.11738 - [12/07/2010]
- Fixed error occurring when pressing return button on test screen.
# 0.1.2.41712 - [11/07/2010]
- Slight performance increase - switching screens is a little smoother
- A little GUI tweak to get a ruff idea of GUI layout
- After Completing a days program, if you try to do another a message is shown suggesting a days rest.
- Good Form button disabled - not implemented yet.
# 0.1.1.24890 - [10/07/2010]
- Fixed "ArgumentOutOfRangeException" which occurred after entering test result
# 0.1.0.23190 - [08/07/2010]
- First Release
Known Issues
Pressing the Return button on "Todays Program" will cause an error. Don't press it!
Pressing the completed button repeatedly on "Todays Program" may cause an error
This is being developed using a HTC HD2 so smaller screens may see error's with layout. Will try to fix this.

interested
Hi, is the source available for this? i'd be interested in contributing if it is.

thanks for the interest donbing
Sadly I would have to say the source is not available. It's a nice small project for myself and I would like to see it through like this. Once completed, I may think about releasing the source.
If you have any idea's you wish to cntribute then I'm all ears!
Also, if you fancy doing a similar project like this, there is also a similar app called "200 Situps". Basically works the same but you do situps and not push ups. I could easily modify my program to do this but if you fancy doing it then go for it. I would gladly use it

Ok, I installed the tool.
It starts, but thats about it. On my first run, i got an unexpected error.
ArgumentOutOfRangeException.
On the second run, i got ObjectDisposedException. This happened after pressing "completed" in the "todays program" page.
Hope this helps.

Excellant!!! bugs is what I'm after lol
Ok when you first run it you should get a screen with 3 buttons like so
Todays Program
Logs and Gaphs
Good Form
When you click Todays program it should come up with the test screen and asking you to perform some push ups and enter a value. Enter the value, press OK and it should take you to a screen for your first program.

For the first run problem, I just installed a new ROM on my phone and installed the program and now I am having the same problem. Will have a look tonight and hopefully post a fix, if not then tomorrow latest.
As for the problem when pushing the 'Completed' Button, does that occour when you first push the button or the last time you push it? Seem to work fine on my phone.

Gaz25 said:
For the first run problem, I just installed a new ROM on my phone and installed the program and now I am having the same problem. Will have a look tonight and hopefully post a fix, if not then tomorrow latest.
As for the problem when pushing the 'Completed' Button, does that occour when you first push the button or the last time you push it? Seem to work fine on my phone.
Click to expand...
Click to collapse
Got some bugs for you;
first thing is: The goodform button doesn't work, i don't know for what it is used but it doesn't do anything. second of all; the graphs tab just shows some random pushups third: It doesnt say how much push ups you need to do. it says week 1 - day 1 and a complete button + timer. Not how much pushups you need to do. And when i press the complete button a couple of times it crashes.

Got some bugs for you;
first thing is: The goodform button doesn't work, i don't know for what it is used but it doesn't do anything. second of all; the graphs tab just shows some random pushups third: It doesnt say how much push ups you need to do. it says week 1 - day 1 and a complete button + timer. Not how much pushups you need to do. And when i press the complete button a couple of times it crashes.
Click to expand...
Click to collapse
Right lets take this 1 by 1.
Yes the Good forms button doesn't do anything at the moment, Sorry I should have mentioned. Basically it will just show you how to perform a correct push-up
The Graphs screen will show random stuff if nothing is stored in log i.e first run of the program. This was for beta testing purposes.
When you push the "Todays Program" button, on the first run it should come up with a screen asking for you to do so many push ups and then enter the value. When you enter a value and press ok it should then take you to the "Todays Program" screen where you see the following.
Today (Week 1 - Day 1)
Rest Timer 00
1 - Pushups to perform #
2 - Pushups to perform #
3 - Pushups to perform #
..... etc etc
Press the 'Completed' button after
each rep to start timer
Completed
When you push the 'Todays Program', does it take you to a test screen or does it go straight to the screen I mention in blue above?

Gaz25 said:
Right lets take this 1 by 1.
Yes the Good forms button doesn't do anything at the moment, Sorry I should have mentioned. Basically it will just show you how to perform a correct push-up
The Graphs screen will show random stuff if nothing is stored in log i.e first run of the program. This was for beta testing purposes.
When you push the "Todays Program" button, on the first run it should come up with a screen asking for you to do so many push ups and then enter the value. When you enter a value and press ok it should then take you to the "Todays Program" screen where you see the following.
Today (Week 1 - Day 1)
Rest Timer 00
1 - Pushups to perform #
2 - Pushups to perform #
3 - Pushups to perform #
..... etc etc
Press the 'Completed' button after
each rep to start timer
Completed
When you push the 'Todays Program', does it take you to a test screen or does it go straight to the screen I mention in blue above?
Click to expand...
Click to collapse
Thanks for the info!
About the last thing: Yes, it asked me to push up as many times, so i did 5 as a test number. But i don't see pushups to perform. Just
Today (Week 1 - Day 1)
Rest Timer 00
Press the 'Completed' button after
each rep to start timer
Completed
EDIT:
When i press the "Return" button, the app crashes.
I also made a little video for you, to help you! http://www.youtube.com/watch?v=F4HgEX_Lu4Q

hhhmmm thats intersting, I can't seem to replicate it. I will have something posted later which should fix it

I don't know if you have seen my edit because i edited it @ 3.59 and you posted @ 3.54 but anyway: http://www.youtube.com/watch?v=F4HgEX_Lu4Q

igi0n
I can see the problem. It's because your screen size is much smaller than mine so what has happened is the list of push-ups you must perform has shrunk so much that it has become invisible. I'm just about to upload another version which I'm now thinking may not look right on your phone.
Could you try it out and post another video clip?

on tonights version, I get error after return from Todays program on HD2.
pushups.exe
ArgumentException
Column 'PROG0' does not belong to table PUSHUPS.
at
System.Data.DataRow.GetDataColumn(StringcolumnName)
at System.Data.DataRow.get_Item(StringcolumnName)
at pushups.Core.GetTodaysProgram()
at pushups.UserControls.ucToday..ctor()
at
Pushups.frmMainNew.TestTime_Disposed(Object sender, EventArgs e)
at
System.ComponentModel.Component.Dispose(Boolean disposing)
at
etc. tired of typing..lol...sorry and hope this helps
Thanks for your great app & idea....

Thanks noellenchris for the post
ok let me just understand a bit more on how this error happened.
You clicked "Todays Program" and test screen came up?
You then entered a value and was brought to "Todays Program" screen?
You then completed the days program which was indicated by a message?
Pressing ok on this message brought you back to the main menu?
Did the error occur when you was brought back to the main menu?
Edit
Never mind I think I see what your saying. The error comes when you press return on the "test screen". uploading fix now :-D

Im going to try the new version now! Btw, if you press the return button but the timer is still @ 0 its not crashing, only when the timers counts down
EDIT:
Hmm the GUI is better but the layout on the screen is pretty messed up @ 320x320.
Im uploading a new video now
EDIT: http://www.youtube.com/watch?v=VvtB1ZASWAs

you videos are helping alot
ok the next course of action, which I hope I will get finished for tonight, will be this.
# Fix the crash when pressing the return button while the timer is running.
# Fix crash when hitting the completed button multiple times while timer is running.
# Fix the GUI layout for smaller screens :-D
Edit
Try newest version I just uploaded. I developed at a lower res so hopefully it will display better.
Please uninstall the old version first and delete \My Documents\PushupLog\log before installing new one.

Gonna install it now, and make a little video!
EDIT:
The text doesn't fit the screen, the size is ok but you cannot scroll down. Also, the timer uses 2 seconds each rep, it needs to be 60?
And when you are done for today, it tell you. Have a days rest before attempting the next program
It needs to be without the S
Video: http://www.youtube.com/watch?v=1l2amIRGf0U
EDIT2:
After completion of the exercise it says: "You have compeleted" The E needs to be deleted

Excellent, no crashes!!!! lol
The count down timer will only do 2 seconds if you pushed and checked Debug -> Rest Timer.
Try running the program again and don't push the debug button.
Other than that it seems there is still an issue with layout and an Issue with I can't spell haha.
Strange because the window size is set to 240 x 260 so I'm not sure why its not displaying correctly.

Oh yeah, i see it . Btw, is there a way to add a feature so that you can begin at a certain week/day and maybe can you add a reset button? Thanks already!

[Q] MortScript Backlight Status

How to use the mortscript to get the backlight status or sleep mode?
I had wrote a alarm script to announce the time with file.wav
I used the ToggleDisplay(ON) to wake up the phone to Start the program and ToggleDisplay(OFF) to end the program.
If the phone is at sleep mode, it work fine. but if the user is using the phone, my script also turn off the screen after alarm announce.. i wanna... to keep the original staus of phone while my alarm is running,, any idea to catch the status of backlight or sleep mode?

Here is some hint...courtesy xda_uc
Code:
# ReadBacklight TimeOut values and Disable Backlight TimeOut
############################################################
BattSuspendTimeout = RegRead ("HKLM", "System\CurrentControlSet\Control\Power\Timeouts","BattSuspendTimeout")
ACSuspendTimeout = RegRead ("HKLM", "System\CurrentControlSet\Control\Power\Timeouts","ACSuspendTimeout")
BatteryTimeout = RegRead ("HKCU", "ControlPanel\Backlight", "BatteryTimeout")
ACTimeout = RegRead ("HKCU", "ControlPanel\Backlight", "ACTimeout")
Brightness = RegRead ("HKCU", "ControlPanel\Backlight", "Brightness")
ACBrightness = RegRead ("HKCU", "ControlPanel\Backlight", "ACBrightness")
RegWriteDword ("HKLM", "System\CurrentControlSet\Control\Power\Timeouts","BattSuspendTimeout",0)
RegWriteDword ("HKLM", "System\CurrentControlSet\Control\Power\Timeouts","ACSuspendTimeout",0)
RegWriteDword ("HKCU", "ControlPanel\Backlight", "BatteryTimeout", 0)
RegWriteDword ("HKCU", "ControlPanel\Backlight", "ACTimeout", 0)
RegWriteDword ("HKCU", "ControlPanel\Backlight", "Brightness", 10)
RegWriteDword ("HKCU", "ControlPanel\Backlight", "ACBrightness", 10)

I don't want to Disable Backlight TimeOut , ijust want to get the status of screen on or off.
Thank Your Reply , I still have no idea about the registry which you point out.... Is it the value will be change at screen on or off status...

edwinho said:
I don't want to Disable Backlight TimeOut , ijust want to get the status of screen on or off.
Thank Your Reply , I still have no idea about the registry which you point out.... Is it the value will be change at screen on or off status...
Click to expand...
Click to collapse
Do you want to keep the script running all the time?
did you consider to use notifications?
it was long time I touched mort but you might get some ideas about reading backlight status and do notifications from "paplight" there is kaiser and rhodium versions.
as I remember it they didnt even turn light on, but not always get triggered too.
well thats all the trouble about different standby modes in winmo.
try it and come back with results.

Thank your suggestion!!!
Yes I want to keep the voice announcer at every 15 or 30 or 60 min something like that "Now is 11:30. AM" , My porgram is work through all the status of Phone, Sleeping or Using Status ... ..But have some bugs on phone screen on...I found no way or command can detect the screen on status with mortscript. I don't want to install another program to act as part of my script..... so i will try your suggestion... and find the way through notifications..
Thank!!

You first need to understand what registry does to your backlight...the answer you are looking for is in the code that i gave you. Good luck.

edwinho said:
How to use the mortscript to get the backlight status or sleep mode?
Click to expand...
Click to collapse
Simply impossible!
But you always can ask the MortScript professionals:
http://forum.xda-developers.com/showthread.php?t=289197

ok, with another thought I may have a solution. read below.
in an answer to:
ai6908 said:
You first need to understand what registry does to your backlight...the answer you are looking for is in the code that i gave you. Good luck.
Click to expand...
Click to collapse
i see you want to be helpfull, but actually those reg values you posted will not help him at all with what he need.
they read timeout values, not status. there might, and probably is a value in registry which can be used to detect standby thought.
I guess you can't avoid using notifications as you can't have the code running all the time. I would freeze uppon standby, or keep pda awake. but winmo standby is behaving strengly, it depends if you have flight mode, wifi, gprs on in standby...
safe way is to use notifications. even they sometimes didn't trigger on one of my winmo in flight mode.
first try if the light goes ON when running your script with notif. it might be that light would stay off.
if not... this is the trick..
make another script, which run nonstop and get started on system startup. just simple few lines:
while 1=1 {
- check the entry - "yourapp/lasttick" If lasttick older then one minute (60 sec) then write reg. "yourapp/standby=1" else "yourapp/standby=0"
- write reg. entry "yourapp/tick= actual time in unix format"
- sleep 60 ( or whatever, but this is needed otherwise you freeze your phone)
}
we assume this script will freeze on standby and will not "tick"
your main announce script then will check on your reg value you using in the first script.
you cant read standby value of it of course as it always would be 0 on start of main script until another tick of secondary script. you need to do both:
if time minus 60 > "yourapp/tick" OR "yourapp/standby = 0"
the second part would cover us in case tick would come right after start of notification and main script.
remember this would not cover all situations.. its just to show you what I meant to do.
runaway situation: user will press power to use the phone and notification will come during first 60 secs following it.

edwinho said:
ijust want to get the status of screen on or off.
Click to expand...
Click to collapse
This is an excerpt of a script I am using to turn off the screen, might help you to get an idea how to determine whether screen is off and/or on.
Code:
#
# adjust to your needs
Set STEP_WIDTH, "20"
Set SCREEN_OFF_EXE, "ScreenOff.exe"
Set FULLFILEPATHNAME_SCREEN_OFF_EXE, "\My Flash Disk\SystemProgs\" & SCREEN_OFF_EXE
Sleep 300
#
# initially set to false
turnOff = 0
#
black = RGB ( 0, 0, 0 )
# get screen dimensions
wdth = ScreenWidth()
hght = ScreenHeight()
#
# test each xth pixel per row and column
For w = 1 To (wdth - %STEP_WIDTH%) Step %STEP_WIDTH%
For h = 1 To (hght - %STEP_WIDTH%) Step %STEP_WIDTH%
#
# get pixel's color
clr = ColorAt( w, h )
#
# if pixel's color isn't black,
# set to true
If (clr <> black)
turnOff = 1
EndIf
Sleep 50
#
Next
Sleep 50
Next
#
#

check screen on/off status
Hi all,
i'm also interested in checking whether the screen is on or off and I had the same idea to check the color of pixels and "deduce" the screen status that way.
What I'm experiencing that ColorAt() function always returns the wallpaper color even if the phone is in stand by... and therefore that method seems not to work.
Don't know whether I do something wrong or if someone has experienced the same.
Waiting for news.
Thanks in advance

Disable soft key back light fix

I recently flashed Axium and man is this thing nice. Def a must have. Anyways I noticed that like many roms the back light of the soft keys stay on. I ended up downloading an app called
Adjbrightness
It works perfectly. Make sure to go to the menu settings and lock it on disable soft key back light.
Enjoy!!!

on Arc S
while button-backlights are off value of
/sys/class/leds/button-backlight/brightness is 0
while its 0 change permissions to read only
they are disabled
I can also limit current to 150 in max_current which limits current and lights are dimmed if you want it running but not at max brightness...
added
echo 0 > /sys/devices/i2c-0/0-0040/leds/button-backlight/brightness
chmod 444 /sys/devices/i2c-0/0-0040/leds/button-backlight/brightness
Click to expand...
Click to collapse
to /system/etc/hw_config.sh
now they are set off on boot

Bada Hacking Codes .....Must Read Bada User...

How To Increase Volume Of Music And Call??
Please see the instruction below
Eg, "dial type in the box and enter * # 197328640 # 4, type 8, type 1" as the old layout
This summary is also * # 197328640 # 481 Have you noticed the 481 abbreviated slightly.
Now, let's go * # 197328640 #
This code is easy to remember because it has symmetry if you type the number 28,640 is the figure as a "+" sign by the arrangement of keys, while the 1973 head is simple then, just noticed that when you press the view!
Activate mDNie
* # 197328640 # 652
then press the lock and hit back lock
Check the cpu and mem factor
* # 197328640 #, 481 to 482 for cpu and mem, 483 for mem
Music and call volumes
* With audio (speaker)
* # 197328640 #
press 5231 then saw a 6 line 0. 1. 2. 3. 4. 5. 6. is the level of speaker volume = music
Maintained at level 1 and level 6 is 70dB 30db
should increase in the threshold of 10dB in steps small and large power increase in 5bd
In for example the threshold 6 (After entering 5231) Enter 6, then (see text WRITEo top line) touch cursor is blinking and the claws on its key panel, switch to 70 number keys and then press enter OK 3 times then we see value in the last line 70dB
* With the call
* # 197328640 #
press 5237
Sound Boost adjust any parameters.
* # 197328640 # 554
[1] SB mode. Corby is to have the choice 0 = bypass (ignore) 1 = mono 2 = 3 = non-interlace interlace stereo stereo
but our wave only 0 = off, 2 = on
[2] SB low ***: feature not cut out the low frequency loudspeaker
corby is the cutoff frequency = 400 ~ 700 to manually enter your Wave
Normal cutoff frequency should be 80 ~ 150Hz in audio equipment
Wave it also effectively opens only how individual pieces
maybe 100 ~ 250Hz
[[3] SB gain. This reference corby children, a few dozen units.
[4] SB clarity: this is open, temporary 100
Please if u visit themobiforest.com than click on google advertise which in site.
Thank You.

[MOD] Using Tasker to gain full control over the LEDs

Way back in my EVO OG days, someone had discovered how to directly access the LEDs, and I had put together some Tasker scripts to put them to good use. I know that there are apps like LightFlow that allow you to do a bunch of stuff to the LEDs, but I found them very cumbersome to use, and there were all kinds of settings that don't work on the Note 2. There was no easy way to know what settings to choose and what were appropriate for the Note 2. Also, Light Flow only works when the display is off, and interferes with the Phones own notification system. This mod works whether the display is on or off (if you want) and is independent of the built in charging notifications.
Also, it's way more awesome to learn to do stuff yourself!
I've used Tasker for years, and although it takes some getting used to, it does a great job at executing tasks based on events.
--------------------------------------------------------------------------------------
Anyway, here's what you can do using Terminal Emulator (which can then be scripted in Tasker). YOU WILL NEED ROOT ACCESS.
Background
1. There are 3 LEDs used for notifications, leg_r (red), led_g (green) led_b (blue).
2. Each LED can be set to a specific brightness from 0 to 255 (where 0 is off and 255 is full brightness), by writing to the "brightness" file.
3. Each LED can be set to blink by writing a value of 0 (off) or 1 (on) to the "blink" file.
4. You can set the time the LED illuminates and the time it is dark when blinking by writing to the "delay_on" and "delay_off" files (values are in milliseconds).
5. These files are located in /sys/class/leds
It appears that "blink" must be executed again after changing the delay for it to have an effect, and turning the LED off requires you to revert the last change - if you set brightness and then blink, you must set blink to 0 to turn it off. If you turned it on with brightness last, then you must set brightness to 0 to turn off. (still investigating this part).​
All you need to do is enter the following commands:
echo 500 > /sys/ckass/leds/led_b/delay_on <- sets the ON time to 1/2 second
echo 500 > /sys/ckass/leds/led_b/delay_off <- sets the OFF time to 1/2 second
echo 128 > /sys/ckass/leds/led_b/brightness <- sets LED brightness (blue) to about 1/2 of max (note that this turns on the steady LED)
echo 1 > /sys/ckass/leds/led_b/blink <- Blinks the Blue LED at the above intervals​
Now in Tasker you can:
a. Create a profile for the "Missed Call" State (or event).
b. Add a Task and in that task add 4 "Scripts" of type "Shell" for each of the above.
c. Make sure you check "Use Root" for each script
I've done this to have my phone flash red for missed calls, blue for missed texts and green for missed calendar events (each as its own Tasker profile)
You need to create one (or two) additional profiles to disable the flashing. All it needs is the following 3 commands to turn all the LEDs off.
echo 0 > /sys/ckass/leds/led_b/blink
echo 0 > /sys/ckass/leds/led_r/blink
echo 0 > /sys/ckass/leds/led_g/blink​
I set one for the "Screen Unlock" event and one for the "Notification Bar". This way, the flashing stops in intuitive ways.
There's way more stuff you can do and trigger alerts on using Tasker.
You can also access the 2 Flashes and 2 Task Lights on the back of the phone (although I suspect it is really just two LEDs that run in 2 different modes). They are located at:
/sys/class/leds/leds-sec1
/sys/class/leds/leds-sec2
/sys/class/leds/torch-sec1
/sys/class/leds/torch-sec2
These only have a brightness setting to turn them on, and are limited to what ever value is stored in max_brightness.
I've attached a couple of Tasker pictures, but feel free to post any questions.