PayPal > USD / EUR
All the details and downloads of TouchLockPro you can find here: http://touchlockpro.sourceforge.net
Youtube video
Changelog
Version 2.12.9 (15-7-2011) for all Windows Mobile touchscreen phones
- Added Czech translations, thanks to oldasuk
- Updated translations provided by BattClock users, including Greek, Hebrew and Polish
Version 2.12.8 (1-4-2010) for all Windows Mobile touchscreen phones, *NEW* Proximity sensor support for Samsung and HTC having proximity sensor
- Updated Russian translations, thanks to Vadim Bogaiskov
Version 2.12.7 (30-3-2010) for all Windows Mobile touchscreen phones, *NEW* Proximity sensor support for Samsung and HTC having proximity sensor
- Fixed problem that the Proximity Lock command was not always executed due to screen off
Version 2.12.6 (25-3-2010) Updated translations
- Translations updated with new Excel spreadsheet containing all translations Russian translations, thanks to Vadim Bogaiskov
- Chinese Simplified translations, thanks to zhongzw
- Chinese Traditional translations, thanks to victorchen101
- Spanish translation, thanks to animalote
- French translations, thanks to YoLoLo
- Italian translations, thanks to tigro11 and ephestione
- Norwegian translations, thanks to longice
- Dutch translation, thanks to myself ;-)
Version 2.12.5 (15-3-2010) for all Windows Mobile touchscreen phones, *NEW* Proximity sensor support for Samsung and HTC having proximity sensor
- Updated Chinese Traditional (thanks to victorchen101)
- Updated Chinese Simplified (thanks to zhongzw)
- Do not use HTCLockAPIWhenBluetoothActive when no call
- Added option to disable Zoombar
Version 2.12.4 (7-3-2010) for all Windows Mobile touchscreen phones, *NEW* Proximity sensor support for Samsung and HTC having proximity sensor
- Updated Russian (thanks to Vadim Bogaiskov) and Dutch translations (thanks to myself ;-) for BattConfig and TouchLockAction.
- Visual feedback if a button is pressed
- Do not do !SCREENON at end call when lock(suspend) command or bluetooth is active
- Some commands are now also executed when not power on/screen on (lockscreen, locksuspend, suspend) to achieve the previous point
- When multiple commands are specified, make sure to execute them via a request,so events related to a previous command are effected already (e.g. screen off).
- Fixed problem that multiple commands where only executed the first time (e.g. Proximity disable/ignore problems)
- Fixed possible problem that multiple commands could mean that an earlier one was not executed/overwritten
Version 2.12.3 (25-2-2010) for all Windows Mobile touchscreen phones, *NEW* Proximity sensor support for Samsung and HTC having proximity sensor
- Added command !PROXIMITYIGNORE, so the Proximity sensor keeps in the state it was, for other applications. TouchLockPro wil not react anymore, till !PROXIMITYACCEPT command is used.
- Added command !PROXIMITYACCEPT, so Proximity commands are accepted from then on.
Changed the defaults for better use of Proximity (note that those will only be overruled if not already set or by reset to defaults):
- Proximity Sensor Time (ProximitySensorTime = 700)
- Near (CmdProximityNear = "!SUSPEND")
- Not Near (CmdProximityNotNear = "!UNLOCK")
New settings:
- Lock (CmdLock = "!PROXIMITYACCEPT")
- Unlock Call (CmdUnlockCall = "!PROXIMITYIGNORE")
- Unlock No Call (CmdUnlockNoCall = "!PROXIMITYDISABLE")
Incorporated BattClock 1.9 improvements:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Show Battery percentage, temperature and Current above the top bar.
- Possibly to show the info in columns instead of rows (option Divide Horizontally)
- Added option to show Battery Temperature (updated once per minute)
- Added option to show Battery Current in mA (updated once per second), great to see power consumption
- Show CPU also if it getidletime is greater than 100
Version 2.12.2 (20-2-2010) for all Windows Mobile touchscreen phones, *NEW* Proximity sensor support for Samsung and HTC having proximity sensor
Do not do !SCREENON at end call, when (lock)suspend is configured as command at end call
InCallTweak: do also for landscape, for right handed people
Proximity changes:
CmdProximityNear, default !IDLE
CmdProximityNotNear, default !UNLOCK
CmdProximityOnBluetooth, default empty
Time proximity change configurable (ProximitySensorTime)
Added !PROXIMITYDISABLE command
Added !PROXIMITYENABLE command
Taken over BattClock 1.8.1 improvements:
Added option to show CPU usage percentage
Color of CPU info configurable
CPU indicator configurable (default %)
Thresholds for Battery and Free memory separate configurable
Extra commands:
Added !HOME command: add option to automatically go to the home screen when locked (Security)
Added !SOFTRESET command
Added !POWEROFF command
Added !UP command
Added !DOWN command
Added !LEFT command
Added !RIGHT command
Version 2.12.1 (14-2-2010) for all Windows Mobile touchscreen phones, *NEW* Proximity sensor support for Samsung and HTC having proximity sensor
Note that I could only test myself by simulating the Proximity Sensor via Stylus Sensor and Capacitive NavSensor. Please report if it is working!
Add support for proximity sensor
Proximity sensor Unlock when no object is nearby for approximate a second.
Proximity sensor option to do ScreenOff when detecting an object nearby for approximate one second
Proximity sensor option to disable proximity sensor when not locked
Proximity sensor option to disable proximity sensor when bluetooth is active
Version 2.11 (7-2-2010) for all Windows Mobile touchscreen phones
Fix: Do not do InCallTweak when not on battery or Bluetooth is active
Take over BattClock 1.6 and 1.7 standalone features in TouchLockPro
Added option to show info divided into 3 lines
Added option to see free memory
Date and Time color separate configurable
Option font color to be dependent on the battery/memory status
Add icon possibility as background and draw info on top of it, good for people having not a solid color or nicer looking icon alike
Added settings BattClockInfo1, BattClockInfo2, BattClockInfo3, BattClockVersion, MemoryIndicator, LowThreshold, MediumThreshold, LowColor, MediumColor, HighColor
Fontsize per info line configurable, text room is divided dependent on fontsize settings.
Option to show free memory in MB instead of %
Make BattConfig more finger friendly
Version 2.10.5 (2-2-2010) for all Windows Mobile touchscreen phones, *NEW* with Samsung SDK compatible Light Sensor and GSensor support
Added Chinese Simplified translations, thanks to zhongzw
Version 2.10.4 (29-1-2010) for all Windows Mobile touchscreen phones, *NEW* with Samsung SDK compatible Light Sensor and GSensor support
Removed automatic disabling of GSENSOR when no GSENSOR commands are configured, because InCallTweak also uses the GSENSOR
Do not do InCallTweak when not on battery or Bluetooth is active
Make sure the power state is reported as on, when a call is still connected or just ended, so the sensors keep working
Do no longer a !SCREENON part of power on or unlock to avoid side effects
Updated Russian translations, thanks to Vadim Bogaiskov
Added Norwegian translations, thanks to longice
Added Chinese Traditional translations, thanks to victorchen101
Version 2.10.3 (10-1-2010) for all Windows Mobile touchscreen phones, *NEW* with Samsung SDK compatible Light Sensor and GSensor support
Fixed problem that PhoneType could get the wrong value, locking up TouchLockAction
Delete debug log files if they exists when no debug logging is enabled. So make sure to copy the debug log files, before disabling debugging.
Merged BattClock 1.4 improvements into TouchLockPro
Version 2.10.2 (4-1-2010) for all Windows Mobile touchscreen phones, *NEW* with Samsung SDK compatible Light Sensor and GSensor support
Solved bug that FaceUp and FaceDown were reversed for Samsung SDK GSensor. Z-axis is positive going into the screen, while HTC has this negative
Change % into ~ when on (USB) power, to indicate in the BattClock when it is charging
Added Italian translations
Let the default minimum light be 9 lux for Samsung phones, otherwise it unlocks too easy
Version 2.10.1 (3-1-2010) for all Windows Mobile touchscreen phones, *NEW* with Samsung SDK compatible Light Sensor and GSensor support
Solved bug that light sensor was not working on Samsung SDK compatible phones
Version 2.10 (1-1-2010) for all Windows Mobile touchscreen phones, *NEW* with Samsung SDK compatible Light Sensor and GSensor support
Added support for Samsung SDK compatible phones, G-Sensor and Light Sensor. Samsung Windows Mobile SDK 1.2.1 or 2.1.0 are now supported! Just install also the appropriate Samsung SDK (see downloads)
Samsung SDK compatible (SGH-i900 Omnia, SCH-i910 Omnia, GT-I8000 Omnia 2, SCH-m490/m495 T*Omnia, Omnia Pro, GT-B7620 Armani, GT-I8000 Omnia II, SCH-i920 Omnia II), Sensors: Light Sensor, GSensor
TouchLockPro tries to identify your phone type now automatically and disables not available sensors
I discovered that the HTCSmartTouchDll window is also available on Diamond and Touch Pro, so now I only subclass for ZoomBar when PhoneType is Diamond2 or Touch Pro2
Added PhoneType configuration possibility in Index Settings screen, best is to first select your PhoneType before changing other settings and soft reset after changing your phone type and settings.
Added BootDelay registry key, if you want to change it, you need to do that via the registry, but be sure to know what you are doing. Default it is 60000 (60 seconds)
Version 2.9 (17-12-2009) for all Windows Mobile touchscreen phones, *NEW* ZoomBar unlock
Thanks to Cobaltikus for providing the solution!
Added ZoomBar unlock for Touch Diamond 2 and Touch Pro 2
Slide the Zoombar left or right to unlock
Triple touch the Zoombar to unlock, if you want different behaviour, change CapacitiveTouchesSequence (CapacitiveTouchesSequence = 222)
Version 2.8.2 (09-11-2009) for all Windows Mobile touchscreen phones
Solved InCallTweak related bug
Create new log file, when no debug logging, instead of appending
Solved problem of screen off after call ended (InCallTweak related)
Lock already at power off when AutoLockOnPowerOn = 1 and HTCLOCKAPI = 0 is used
Reintroduce and fixed Screen Off to Screen On, which was disabled in 2.8.1
Delayed Power On to Screen On when possible, so when the phone awakes without screen on (e.g. checking mail), no extra CPU is used by TouchLockPro which saves a bit power
Made it possible to use HTCLOCKAPI = 1 in general and only at incoming call lock keys only with the general keyboard hook
Improved HTCLockAPIWhenBluetoothActive
Made Bluetooth status detection event driven instead of polling on need and added debug logging for state changes
Version 2.8.1 (28-10-2009) now with improved GSENSOR and for all Windows Mobile touchscreen phones
Made HTCLockAPIWhenBluetoothActive = 0 the default, so only the people who want to answer with the bluetooth answer button can enable it.
Disabled feature, till further investigated: change from screen off to screen on as power on and lock appropriate
Version 2.8 (27-10-2009) now with improved GSENSOR and for all Windows Mobile touchscreen phones
Also see change from screen off to screen on as power on and lock appropriate, so when not going into a deep sleep and screen goes on, it will lock appropriate.
InCallTweak: also screenoff when reverselandscape is detected
Added setting HTCLockAPIWhenBluetoothActive to use HTCLockAPI when bluetooth is active, so you can use the general keyboard hook locking method when no bluetooth is active.
Improved GSENSOR
Compute orientation instead of using the HTC orientation field for better accuracy
Poll GSENSOR now once per 100 ms for greater sensitivity
At boot also open GSENSOR (only after first power off GSENSOR was activated)
Closing the GSENSOR when going to deep sleep (and setting the orientation to unknown)
Start/stop the GSENSOR service
added GSENSOR debug logging to GSENSOR Settings screen when debug is on
Version 2.7.6 (06-10-2009) now with InCallTweak and for all Windows Mobile touchscreen phones
Added !IDLE command
SUSPEND problem: request immediately deep sleep (POWER_STATE_SUSPEND) instead of screen off (POWER_STATE_IDLE)
Added InCallTweak option instead of ScreenOffWhenConnected: GSENSOR portrait: screen off, otherwise screen on
Redo screen off with above option, when backlight goes on again
!BACKLIGHTOFF and !SCREENOFF do no longer by default !KEEPALIVEON, to avoid unintended battery drainage
Changed NavSensor settings to execute !KEEPALIVEON with !BACKLIGHTOFF and !SCREENON (old behaviour, to correct above change)
More detailed info of the changes can be found here.
See here for QuickStart and Features
Number of AppToDate Users:
Many thanks to Dennis van de Sande, alias MR_Q, who has sponsored/donated for more than a year zuinigerijder.com website and domain. New location: touchlockpro.sourceforge.net
PayPal > USD / EUR
Screenshots
See my new website for the screenshots
Overrule Settings
See my new website for the settings
For future use
another one for future use.
Version History
See new website for the version history
Great job!
My only (stupid?) concern is that by using your (otherwise nice) "BattClock" we miss custom battery indicators.
You will say that, then we should disable this. But then (a) you still get it when device is locked (why we HAVE to see the valid taps after we get used to them?) and (b) you have one less method to lock the device from the very few: just two - i.e. one left.
This comes to the second thing. Why not also lock it with other method?
I can think of: (a) Touching the capacitive area one right, one middle (action button), one left.... in fact you could even UNLOCK by doing the opposite. (b) Using some program shortcut (for some of us is enough to lock the device by running a shortcut in TF3D or some today manager like SPB Pocket Plus or even changing a default action in TF3D via SSMaPa)...
The best way would be to still use the area of the battclock but WITHOUT changing whatever the user has there (is there such a thing like a transparent window?)...
Another way would be to auto-lock after some timeout (which in fact is also the most common method among smartphones too) or configurable if the power button is pressed.
For example in my case pressing the power button to sleep the device exactly means I don't want the screen functioning (so lock it if something else turns it on - like a call), while if I leave the device to sleep by timeout, I probably mean I have it on my desk and don't care or need to lock it.
Sorry for the brainstorm, I hope it gives you some ideas.
Seems to be working fine so far....but I have one problem;
I'm using wisbar so your battery indicator does not show on the screen when the phone is unlocked. This means I have to lock the phone by using the stylus. The indicator does however appear when the phone is locked.
Is there no way to correct this, or make a shortcut for locking instead?
can i set this app to only lock the screen on incomming phone call and unlock it by tapping 3 times on the capacitive area?
something like the answerkeys disabler did before uninstalling...
NLS said:
Great job!
My only (stupid?) concern is that by using your (otherwise nice) "BattClock" we miss custom battery indicators.
Click to expand...
Click to collapse
You can position the BattClock over the Windows Start logo, at the left side of the Start bar. You can still go to Programs, just by pressing the Start text then.
NLS said:
You will say that, then we should disable this. But then (a) you still get it when device is locked (why we HAVE to see the valid taps after we get used to them?) and (b) you have one less method to lock the device from the very few: just two - i.e. one left.
Click to expand...
Click to collapse
Yes, the BattClock must be visible AND have focus to get the capacitive touches. So moving to another position is the only option, if you want to use the triple touches approach to unlock.
NLS said:
This comes to the second thing. Why not also lock it with other method?
I can think of: (a) Touching the capacitive area one right, one middle (action button), one left.... in fact you could even UNLOCK by doing the opposite. (b) Using some program shortcut (for some of us is enough to lock the device by running a shortcut in TF3D or some today manager like SPB Pocket Plus or even changing a default action in TF3D via SSMaPa)...
Click to expand...
Click to collapse
I can only get keyboard/sensitive touches when my battClock has focus. And when there is another program in front, I cannot get them.
I am working on an Action screen addin for TouchLockPro. It will be activated by pressing the BattClock OR you can start the program by a shortcut, because it is a separate program. But be patient, working on that......I even want it possible by other programs to lock the device, just by writing some registry key.
NLS said:
The best way would be to still use the area of the battclock but WITHOUT changing whatever the user has there (is there such a thing like a transparent window?)...
Click to expand...
Click to collapse
To my knowledge, there is no real transparant window possible, you can just not draw the background. But the underlying windows will not update. Or does someone know this is possible?
NLS said:
Another way would be to auto-lock after some timeout (which in fact is also the most common method among smartphones too) or configurable if the power button is pressed.
For example in my case pressing the power button to sleep the device exactly means I don't want the screen functioning (so lock it if something else turns it on - like a call), while if I leave the device to sleep by timeout, I probably mean I have it on my desk and don't care or need to lock it.
Sorry for the brainstorm, I hope it gives you some ideas.
Click to expand...
Click to collapse
That would be something for my new Action screen program. I will think about your suggestions. Thansk for the ideas and comments.
flickering clock white/black
Hey ZuinigeRijder!!
thanxx again for your new app TouchLockPro 1.0!!
so far I have it on my diamond it's working ok, but I noticed one thing...when my screen is on standby f.e. see my clock etc...I saw that the clock/batt indicator is contantly flickering white/black....just like it's locked...unlocked....locked...unlocked...
Do you know what I mean or do I have to be more specific??
Maybe you did it on purpose....
Just wanted to report it to you...neways... thanxx man!!
You rule!
Greetzz Jeroen
fl4r3 said:
Seems to be working fine so far....but I have one problem;
I'm using wisbar so your battery indicator does not show on the screen when the phone is unlocked. This means I have to lock the phone by using the stylus. The indicator does however appear when the phone is locked.
Is there no way to correct this, or make a shortcut for locking instead?
Click to expand...
Click to collapse
I do not know wisbar, but apparently this is a FullScreen app, so the BattClock will not be visible.
As written as answer in my previous post:
I can only get keyboard/sensitive touches when my battClock has focus. And when there is another program in front, I cannot get them. This cause me also some serious thinking, how to solve this. I found a method, as described here:
http://forum.xda-developers.com/showthread.php?t=436671&page=5
I am working on an Action screen addin for TouchLockPro. It will be activated by pressing the BattClock OR you can start the program by a shortcut, because it is a separate program. But be patient, working on that......I even want it possible by other programs to lock the device, just by writing some registry key.
Pietje_1985 said:
Hey ZuinigeRijder!!
thanxx again for your new app TouchLockPro 1.0!!
so far I have it on my diamond it's working ok, but I noticed one thing...when my screen is on standby f.e. see my clock etc...I saw that the clock/batt indicator is contantly flickering white/black....just like it's locked...unlocked....locked...unlocked...
Do you know what I mean or do I have to be more specific??
Maybe you did it on purpose....
Just wanted to report it to you...neways... thanxx man!!
You rule!
Greetzz Jeroen
Click to expand...
Click to collapse
That is one of the magic tricks I needed to do, to get the focus to the BattClock, for getting the capacitive touches. I will only get those events, when a Form is in the foreground. And that is normally another application
When e.g. an incoming call is coming in, it will get the focus, because that is the foreground application. Or if you have a Full Screen application, the BattClock will even not be visible. But I discovered, when I make a Child Window at the start-bar as WS_POPUP, it will get focus, when created.
But damned, it will not keep focus, if another application regains focus
So how to solve this problem
The only solution, I could think of, was regularly recreate the WS_POPUP child window, and in between I switch back to another BattClock. At the same time, this 'flashing' indicates the system is accepting capacitive touches. So 4 seconds we have the WS_POPUP BattClock and 1 second the 'normal' BattClock. So actually I switch between 2 clocks.
More background info you can find here: http://forum.xda-developers.com/showthread.php?t=436671&page=5
at10ti0n said:
can i set this app to only lock the screen on incomming phone call and unlock it by tapping 3 times on the capacitive area?
something like the answerkeys disabler did before uninstalling...
Click to expand...
Click to collapse
Unfortunately not (yet).
I did not yet included specific code for detecting incoming calls, I just made a generic solution. But it might be something for the future.......
I think more people would like a general solution to distinguish when they press themselves the power button to awake the phone and when this is done by an application. For the latter, they would like it locked, on their initiative, they would like it automatically unlocked.
But still, in your pocket you can also accidently press the Power button, although less likely. But of sure you never want missed calls!
So I will think about it......
ZuinigeRijder said:
That is one of the magic tricks I needed to do, to get the focus to the BattClock, for getting the capacitive touches. I will only get those events, when a Form is in the foreground. And that is normally another application
When e.g. an incoming call is coming in, it will get the focus, because that is the foreground application. Or if you have a Full Screen application, the BattClock will even not be visible. But I discovered, when I make a Child Window at the start-bar as WS_POPUP, it will get focus, when created.
But damned, it will not keep focus, if another application regains focus
So how to solve this problem
The only solution, I could think of, was regularly recreate the WS_POPUP child window, and in between I switch back to another BattClock. At the same time, this 'flashing' indicates the system is accepting capacitive touches. So 4 seconds we have the WS_POPUP BattClock and 1 second the 'normal' BattClock. So actually I switch between 2 clocks.
More background info you can find here: http://forum.xda-developers.com/showthread.php?t=436671&page=5
Click to expand...
Click to collapse
Right! Well....I also see that actually the device itself stays locked, so I'm not so worried.....
on the other hand...I can imagine you would like to solve tis problem just like it was on StylusLock v1.6, because that one didn't had that issue...
To be honest...I really would like to help you, but I don't know how...I don't have any programming experience, so i'm sorry man
n e way...if I can help you with something else...please let me know!
Cheers
Jeroen
ok something else then
since this small window is the trick to make it work, I wonder (sorry I could probably find my self, but haven't installed yet) if we could just move the whole rectangle to... the BOTTOM bar (!), just left of the keyboard icon!
also change the battclock to a small lock (locked and unlocked) now THAT would make great sense AND not mess with our customisations
this looks nice, stylus lock 1.6 was impressive, i cant wait to try this!!
flashing a new rom tonight, ill be sure to install this first!!
thanks
Thanks for this great app!
One thing: When phone goes to suspend, approximately in the next 20 seconds i cant turn the screen on by pressing the power button. Only stylus-out turns the screen on. After 20 seconds everything runs fine.
Furthermore an option to also lock the phone when the screen switches off by pressing the power button would be very nice.
schluff1 said:
Furthermore an option to also lock the phone when the screen switches off by pressing the power button would be very nice.
Click to expand...
Click to collapse
I second That
seems like a good alternative to S2U2. although i dont know what this does that is better than S2U2.
Related
No install required - No Mobile Shell required - No third party programs required - this replacement for your Today screen is fully contained - and fully FREE!
FOR ANY INTERESTED PARTIES I HAVE UPLOADED THE SOURCE CODE NOW TO THIS PROJECT AS I HAVE NO MORE TIME FOR IT.
PLEASE FEEL FREE TO USE ANY OF IT AS YOU SEE FIT - HOWEVER IF YOU USE MY ALPHA TRANSPARENCY CODE PLEASE GIVE ME SOME CREDIT IN YOUR PROGRAM AND LET ME KNOW ABOUT IT!
Please note - this software is still under development and as such may contain bugs and empty pages until things are programmed - if this worries you or scares you please do not try my software!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
Skin packs:
http://forum.xda-developers.com/showthread.php?t=415563
http://forum.xda-developers.com/showthread.php?t=417423
http://forum.xda-developers.com/showthread.php?t=414699
Every resolution is supported. The two configuration files LANDSCAPE.XML and PORTRAIT.XML contain the screen size and button layout positions - if you have a differente size screen you can simply edit these two files to move the buttons around - full instructions are included in the XML file
So I have seen the great work that people have been doing here - and I absolutely love the themes from Greatbal - but the overhead from SPB (and having to have it installed) do not seem to justify the actual overhead.
I decided to start writing my own fully customizable fullscreen page - this will be updated as I add more features - and will post the executable for people to send and leave me feedback!
Transparencies are fully handled.
If you like the application and want to support me - you can do so with my Paypal link below - it is set to just $5 as I think this is plenty for anyone that so wishes to donate (all donations are going to be sent to Great Ormond Street Hospital here in the UK). THANKS!
https://www.paypal.com/cgi-bin/webs...y_code=USD&lc=GB&bn=PP-BuyNowBF&charset=UTF-8
DONATIONS from (first three letters of each name only for security) : Guv Ata , Joh Sha , Han Fuc , Tim Cro , Lou B , Chr Car , Man Oso , Ace Ace , Bob BBQ , Mic Kat , Ric Pla , Dea Dic , Ali Ama , Pet Hah , Vin Mac , Con Whe
THANKS!!!!!!
FAQ:
Q. It crashes because of xxxxx
A. First try copying and running the files from system memory as some devices (HTC Touch) have issues resuming from standby with program running from the storage card. If the program still fails - edit the config.XML and select YES for errorreporting - then run the program - when it crashes post the errorreport text file here and I can try and help you.
Q. Why is there nothing on the calendar or music or blah blah page?
A. Because the app isnt finished yet - as clearly stated above! - more is being added
Q. What version of WM do I need?
A. 6.x - it does not work on WM5 or below
Q. How do I install it?
A. You dont! - simply copy all files to a folder on the device and run the EXE - that's it - no install - no uninstall - nothing changed on the device - no registry entries required.
Q. What is the default unlock sequence
A. 1 single guesture - ^ (you can change this on config.xml)
Q. Can I change stuff?
A. Yes - everything! - the landscape.xml and portrait.xml contain all the positions for the icons and layouts for the skin, while config.xml contains details about non-skin related options
Q. What Compact Framework do I need?
A. You need either 2.0 or better still 3.5 - unfortunately some custom rom cookers have not fully incorporated CF into their build and this may cause you problems - not just with my app but anything that uses CF. My only suggestion here is to try an updated (or different) base rom! - it works perfect with all the WWE builds with CF installed - so I know it's the rom
Q. I get a white screen when starting the program
A. This can be caused by two things - either you did not UNZIP all the files into a directory (this will contain the program files and TWO sub directories :- PNG and WAV) or it can be caused by a problem with the custom ROM you are running and due to the cooker not implementing the compact framework correctly - and the only solution to this is to use a different rom (this will affect all programs that try to access these portions of the CF not just mine)
Code:
TO DO :
* move contact loading to calendar thread
* AlarmNotifications for sms/email/phone/voicemail - repeating alert sound
* screen off button for tab 6 (temp)
* soft reset button for tab 6 (temp)
* extend missed notifys to 9
* MMS Status icon
* Vibrate on volume control
* Voicemail icon dial voicemail
* MP3 player integration
* Weather
* Flo style favourites launcher
* Add optional notify icons for additional email accounts
* BUG : current days appointments displayed in reverse order
* BUG : lock keys unlocks after system notification
* BUG : Fix font sizes for VGA devices
* LOTS MORE!
Code:
Changes :
V.276 - International fixes!
V.275 - Clock 12/24 hour selectable in config.xml - also clicking clock takes you to clocks/alarms
V.274 - Missing draw bottom line fixed
V.273 - Finger Friendly launcher
V.272 - Launcher code tidied up
V.271 - Optimized launchers starting programs
V.270 - Font fix for launcher page
V.269 - Launcher skinned and options available
V.268 - Launcher Main code implemented
V.267 - More Apps added to test launcher
V.266 - Launcher fix
V.265 - Dim screen options
V.264 - App launching begins!
V.263 - Lock fixes
V.262 - More locking checking
V.261 - Lock error checks added
V.260 - Calendar updated edition
V.259 - All 3 lock levels now implemented
V.258 - More configurable email/SMS icons
V.257 - A2DP icon added + launcher icon added (skinners need to update XML)
V.256 - Bow down to pressure edition
V.255 - All errors logged now
V.254 - Screen redraw routine modified
V.253 - screen update and refresh after rotation handled faster now (less/no white block)
V.252 - Power/lock code re-written - calendar code re-written
V.251 - Even more error reporting - will now report Drawing:xxxx with the name of the icon its attempting to draw - useful for crash reporting
V.250 - Locking code updated
V.249 - Even more error reporting
V.248 - More error reporting
V.247 - Fixed glitch with notify icons not displaying properly
V.246 - FLO test screens removed - skinners can test all pages now - graphics fix in PNG alpha routines - GFX look much better now
V.245 - Appointments back - more error trapping - unlock changed to single UP guestuere - calendar centralised
V.244 - Erorr logging to file
V.243 - Calendar temporarily removed to test crash fix
V.242 - Manual Lock icon added to page 6 (can be moved via XML to any pages)
V.241 - LockTastic!
V.240 - The lock for all edition :D (hopefully)
V.239 - Still fixing the SX66 power on :(
V.238 - Smartphone power detect routines added
V.237 - new flo crashes stopped - also for skinners errors in PNG load now displays which PNG is wrong
V.236 - Lock on power sorted?
V.235 - Page four contains debugging infro for power states
V.234 - Lock really is locked - no get around with phone key now
V.233 - Voicemail notify added - shows 1 if you have 1+ voicemails waiting
V.232 - Lock code reworked
V.231 - Lock page centralised, made more responsive, bugs squished
V.230 - Swish To Unlock Edition
V.229 - Image loading classes rewritten - loading should be faster and mem usage reduced
V.228 - The volume Icon working edition!
V.227 - Contacts test!
V.226 - more FLO adjustments - page 4 fixed
V.225 - the finger friendly flo edition!
V.224 - Flo speed in config.xml
V.223 - Guestures improved further - test pages for contacts on pages 4 + 5 - calendar fixed for not display highlighted day on next month
good work thanks
I'm not one to stifle innovation, but i'm curious how this is/will be different from something like RLToday
(both are full screen, and use XML for configuration)
http://rotlaus-software.de/forum/viewtopic.php?id=1171
RLToday:
1. vjtoggletodayiialpha to remove topbar and bottom bar.
2. vjokbutt / mortscript to have X/OK icon we you lanuch application.
3. Mortscript to have Signal, battery, Wifi, Bluetooth, Volume on our new customized topbar.
The program I am using is pure .NET - no mortscript, no vjtoggle required to create full screen
I intend to replace all the original functionality of the device where possible.
The one thing I cant stand is a beautiful today screen and when you press the "messages" button you get the bloody horrible white page with the message display - I intend this to replace the messaging, calendar and contacts sub pages and make them feel a lot nicer to use.
I am using the full API and some imported DLL calls to reference the information on the device directly instead of using scripting programs - and as such as you can see - it's tiny in size and runs very quickly!
I have also already managed to code left and right guestures for page swapping although they are in the code provided - the guestures currently do nothing.
looks VERY promising, will keep an eye on this thread!
this is indeed very promising n will help to reduce the use of multiple programs and plugins
Nice! Sounds like alot alot of work...hope you find somebody to help you ! GL !
Nice work
It looks nice and promising, keep up the good work. I wish I am good at art work.
Hopefully somebody with good art sense will help you. Good luck friend.
Sounds like a cool idea.
1. How did you replace the home screen?
2. iContact has a fairly portable titlebar module you could use... it's in C++ win32 though.
The home screen isnt actually replaced - it's still running behind - the key is to use the API's to adjust the window up and over the title bar and make my app foremost so it takes over.....you can see the start menu still working by pushing your "windows" soft key - the menu will still pop up bottom left - although I need to make the title bar visible again when my application loses focus - something to do.
The main screen is actually just a custom built graphic which is updated periodically - but that has events behind it that detect "zones" on the page for clickable areas - the page is re-drawn in the back buffer and then flipped to the main screen to prevent any flicker - currently the display is set to update every 5 seconds - need to assess battery performance based on update speed.
The advantage is that because the page is built up from "element" small graphics pieces that can be interchanged or replaced totally and also resized to anywhere on screen - the layout is completely changeable!
dazzlingdaz said:
The home screen isnt actually replaced - it's still running behind - the key is to use the API's to adjust the window up and over the title bar and make my app foremost so it takes over.....you can see the start menu still working by pushing your "windows" soft key - the menu will still pop up bottom left - although I need to make the title bar visible again when my application loses focus - something to do.
The main screen is actually just a custom built graphic which is updated periodically - but that has events behind it that detect "zones" on the page for clickable areas - the page is re-drawn in the back buffer and then flipped to the main screen to prevent any flicker - currently the display is set to update every 5 seconds - need to assess battery performance based on update speed.
The advantage is that because the page is built up from "element" small graphics pieces that can be interchanged or replaced totally and also resized to anywhere on screen - the layout is completely changeable!
Click to expand...
Click to collapse
Oh, in that case, you could make the carrier, battery, signal strength, etc., configurable too!
They already are! - download the program and try - the icons at the top are all png/jpg/gif files in the PNG directory and the size and position of the icons at the top can be configured through the XML file in the application directory
<OperatorTextX>0</OperatorTextX> <X location of operator text
<OperatorTextY>0</OperatorTextY> <Y location of operator text
<OperatorTextSize>7</OperatorTextSize> <operator text size
<SignalX>155</SignalX> <signal strength x pos
<SignalY>0</SignalY> <signal strength y pos
<SignalW>25</SignalW> <signal strength width
<SignalH>10</SignalH> <signal strength height
But still everything that is included up to now - is all within 55K!
dazzlingdaz said:
They already are! - download the program and try - the icons at the top are all png/jpg/gif files in the PNG directory and the size and position of the icons at the top can be configured through the XML file in the application directory
<OperatorTextX>0</OperatorTextX> <X location of operator text
<OperatorTextY>0</OperatorTextY> <Y location of operator text
<OperatorTextSize>7</OperatorTextSize> <operator text size
<SignalX>155</SignalX> <signal strength x pos
<SignalY>0</SignalY> <signal strength y pos
<SignalW>25</SignalW> <signal strength width
<SignalH>10</SignalH> <signal strength height
But still everything that is included up to now - is all within 55K!
Click to expand...
Click to collapse
Hope you can keep working on this as it is quite promising.
sounds good, a new fullscreen skinnable gui that needs no other apps. i only know two really good ones: mobile shell and pointui. pointui has a batteryproblem and isnt skinnable and mobile shell isnt freeware hard to skin.
But you will have a lot of work man. thanks and good luck.
Ok - am going to leave the rest of status icons for the moment - I have all the API references for Bluetooth, GPRS, Edge HDSPA etc to see if they are active or not and will put them in in due course.
Next I am going to work on the new "send SMS" screen - this is going to be a total replacement for the horrible white screen sender - much more like the diamond SMS screen - but I found that to run really slowly on my Kaiser (under the mobile shell) - so will hopefully be making a much quicker version!
First thing to do is the screen layout - again the size and position of the entry box and the name box and the background will be customizable through the XML - yes - I am making everything move/sizeable lol.
Next will capturing the keyboard input to the boxes and finally using the SMS API to send the mesage and return to the main screen.
Looks promising, I'll be checkin this out the next days.
Keep up the good work!
wow this is amazing...one question will the sms program be a replacement threaded style ap or just to send? If this becomes something like point ui but with complete control that would be awesome. keep up the good work.
I intend a full SMS replacement UI - the SMS sender screen is already done and will be uplaoded shortly - the SMS history will also be completely re-written to be able to be viewed threaded or non threaded - however you want to see it! (hopefully)
thinkin of flash integration?
No plans for flash - but I can play flash moives through the .net framework - although - my aim to make a fast replacement.
Please see the latest version for bringing up the SMS screen - it is INSTANT - makes you wonder what MS is doing with their screen and why it's so slow at loading
==================================================================================================
More advanced *FREE* unlocking using all the HTC sensors can be found here: [APP]TouchLockPro
If you are fine with StylusLock 1.7, just keep using it. However, because StylusLock 1.7 is integrated in TouchLockPro, new developments within StylusLock 1.7 are not expected. So keep your eye on the new thread (you can even subscribe to it, via the "Thread tools" feature of XDA).
==================================================================================================
There are already a lot of applications to disable touchpanel and/or hardware keys for the Touch Diamond. I added another simple one:
StylusLock
Youtube video StylusLock in action on wmpoweruser.com. Note that this video is version 1.1. New version 1.2 onwards has a StylusLock indicator and vibration is different
Version 1.6 onwards has a BattClock, indicating the locked status
Unlocked:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Locked:
Features:
* Great to have *ANY* application locked, e.g. GPS navigation, Music player, Home screen, so you do not accidentally press touchpanel/hardware buttons.
* Works with Touch Diamond and Touch Pro.
* Be able to put the Touch Diamond in your pocket with touchpanel and all hardware buttons locked.
* Taking out the TD from your pocket: the touchpanel or a hardware button cannot be accidentally pressed when locked.
* Avoid missed calls, by accidentally pressing the TouchPanel and/or hardware buttons.
* With Bluethooth headset still incoming calls can be answered, although it is locked (confirmed by others)
* No effect on Battery life.
* Consumes no CPU cycles (only in case of an Stylus/Power event, no polling). Check it with a Task Manager!!
* Use Stylus for locking/unlocking
* Clock and battery percentage indicates Locked/Unlocked, pressing the indicator enables "Stylus lock mode" (version 1.6 onwards)
* Unlocked when on AC or USB power
* Vibration when changing lock state to locked
* Not having the Vibration bug of "SensorLock"
* Go to Suspend when locked and the backlight goes off (v1.3 onwards)
* Possibility to overrule default behaviour (v1.4 onwards)
What does it do:
* There are 2 modes, "stylus lock mode" enabled and disabled
- Mode 1 - enabled - stylus in = phone locked
- Mode 2 - disabled - stylus in = phone not locked
* You can enable "stylus lock mode" by pressing the BattClock (version 1.6 onwards)
* You can toggle the "stylus lock mode", by taking OUT the Stylus and putting it back IN within 1 second (3 seconds in versions before 1.4)
* In fact the second mode permits not to use the lock functionality, in order to use your fingers on the touchpanel and hardware buttons, rather than the stylus.
* On startup/boot/reset it will be always unlocked and "stylus lock mode" is disabled
* It will always be unlocked, when the Stylus is OUT
* It will always be unlocked, when on ACPower/USB power
* It will always be unlocked, when the program is exited
* In "stylus lock mode 1", putting the Stylus IN and on battery-power, the touchpanel and all hardware keys will be locked
* In "stylus lock mode 1", when switching to battery-power and the Stylus is IN, the touchpanel and all hardware keys will be locked
* Vibrate once when switching to unlocked state (till version 1.1, version 1.2 onwards does not vibrate anymore, because there is a StylusLock indicator when locked, saves battery)
* Vibrate when switching to locked state and/or "stylus lock mode" enabled
How to install:
* Deinstall the previous version of StylusLock and/or other locking programs
* Copy the StylusLock.x.x.CAB file from your computer to the Touch Diamond or Touch Pro Memory card
* Go via the explorer of the Touch Diamond or Touch Pro to the location where you copied the .CAB file and click on it to start installation
* Advice is to install it to the Phone memory and not to the Memory card, StylusLock is very small and so it also works in "DiskDrive" mode
How to use:
* Choose your "stylus lock mode", by using the method above (toggle the "stylus lock mode", by taking OUT the Stylus and putting it back IN within 1 second)
- e.g. if you want to put the TD in your pocket, enable "stylus lock mode"
- e.g. if you have your TD lying on the table, disable "stylus lock mode"
- e.g. you can also use always the "stylus lock mode" when your are fine to take out the stylus for unlocking (you do not need to operate the Power button anymore)
How to go to sleep mode immediately AND locking the phone when in "stylus lock mode"
Press the Power button and insert the Stylus. You will feel a vibration when the phone gets locked. In this way you do not rely in the Windows settings for going to sleep, it will go to sleep immediately.
Version 1.7
* Possibility to disable BattClock press via registry setting ClockClickable
Version 1.6
* Instead of the locked notification icon, now a Clock with Battery percentage is shown on the position of the battery icon
* When pressing the Clock, the "stylus lock mode" will be enabled
* When the phone is locked, the Clock will swap the background and foreground color, to indicate it is locked
* The default position of the BatteryClock can be overruled
* BattClock takes into account portrait and landscape mode (a negative value of ClockX position will count relative from the right, instead of from the left)
* The default foreground and background colors of the clock can be overruled
* StylusLock will become active after 30 seconds instead of 5 seconds, so the phone has time to start up
* Still Stylus(BattC)lock does consume no extra battery/CPU
Note that I hope that people having problems with the locked notification icon, do no longer suffer problems with this approach. Please let me know if this is solved now. Be sure not to run in 1.1 compatibility mode, though.
How to overrule default settings:
It is possible to overrule the default settings via registry HKCU\Software\ZuinigeRijder\LockSettings
Please use a registry editor to create the DWORD values, e.g. PHM RegEdit.
A value of 0 means No and a value of 1 means Yes. The default DWORD value is also mentioned. Please make sure to do a soft reset after adding the appropriate overrule settings.
* lockTouchPanelOnly = 0
* vibrate = 1
* beep = 0
* lockIndicator = 1
* clockClickable = 1
* suspendOnBacklightOff = 1
* unlockOnACPower = 1
* stylusAlwaysControl = 0
* stylusOutInToggleTime = 1000 decimal or 3E8 hexadecimal
* ClockX = -96 decimal, corresponds to unsigned 4294967200 decimal or FFFFFFA0 hexadecimal // minus means relative to the right
* ClockY = 0
* ClockWidth = 48 decimal or 30 hexadecimal
* ClockHeight = 48 decimal or 30 hexadecimal
* ClockBackground = 0 // Black, RGB(0,0,0)
* ClockForeground = 16777215 decimal or FFFFFF hexadecimal // White RGB(255,255,255)
You only need to define the values you want to overrule.
How to Use
Unlocking use case when "stylus lock mode" is enabled and e.g. a phone call is coming in.
* Option 1 (when you want to use the Stylus or have place to put it somewhere):
- Take the stylus OUT and keep it out
- Answer/Reject the call with the TouchPanel or Hardware keys
- When done with the call, put back the stylus IN
* Option 2 (if you do not want to use the Stylus and have no place to put it):
- Take the stylus OUT and put it back IN within 3 seconds ("stylus lock mode" disabled)
- Answer/Reject the call with the TouchPanel or Hardware keys
- When done with the call, Take the stylus OUT and put it back IN within 1 second ("stylus lock mode" enabled) (3 seconds for versions before 1.4).
Unlocking use case when "stylus lock mode" is disabled and e.g. a phone call is coming in.
- Answer/Reject the call with the TouchPanel or Hardware keys, because they are not disabled
I would like to thank surfsmurf for his SensorLock software which made it possible for me to have a quick start in programming Windows Mobile and the trick of locking the touchpanel and hardware keys.
Version 1.5.2
* Reverted back to version 1.5 (1.5.1 did not solve the crashes and gave other problems)
* Fixed bug with lockTouchPanelOnly = 1 (version 1.5 did not work with this setting)
* There can be occasional lockups, when using the lock indicator. You can disable the lock indicator with setting lockIndicator = 0 or use version 1.1.
Version 1.5.1
* Reverted lock code, because the 1.5 version did not work with lockTouchPanelOnly = 1
* lock indicator is now added/removed in Window callback
* Again an attempt to solve the reported crashes
Version 1.5
* Integrated latest lock code from SensorLock 0.3.4
* Maybe this solves the reported crashes
Version 1.4.1
* Fixed bug when lockTouchPanelOnly = 1 was set and a call comes in, the TouchPanel was unlocked. Now I reapply the lock on resume.
* Because of the complaints of crashes, I now do the Add/Remove of the lock icon in the background.
* Also there is a delay of 1 second before the icon gets added or removed and the lock status has not changed in that time.
* However, I do not know if this solves the crashes, but you can give it a try.
Version 1.4
* Solved the rarely occurring lockup bug
* Changed the Stylus Out/In time from 3 seconds to 1 seconds
* Made it possible to overrule the default settings via registry HKCU\Software\ZuinigeRijder\LockSettings
Version 1.3
* Go to Suspend when locked and the backlight goes off (v1.3) (saves again extra battery automatically)
* You can control this duration time via Windows Mobile power setting "backlight off time"
* This way someone can also quickly put on the phone with the Power button to check e.g. the time. It will now fall earlier to sleep
* So you do not need to wait too long for putting the Stylus back, if you do not want to toggle.
* Again did some measures for preventing rarely occurring lockups. I am convinced the problem is not fully solved though
Version 1.2.2
No longer vibrate when the backlight is on and it goes to locked, because the intention of StylusLock is to use no real extra battery:
* Added that StylusLock will no longer vibrate when the backlight is on and it goes to locked. The visual icon is good enough in that case.
* But if you put the TD to sleep first by using the power button or the backlight is off and thereafter locking the TD, then it will still vibrate for non-visual feedback.
* Also did some measures for preventing rarely occurring lockups.
Hope these improvement are liked, otherwise keep version 1.2.1.
Version 1.2.1
* Found the problem why the icon was disappearing. So now I do not need to redo the locked icon each 55 seconds. No CPU usage again.
* Apply the lock icon immediately AFTER it is really locked
* Remove the lock icon immediately AFTER it is really unlocked
* I had a lockup of the TD today (with version 1.2), so I do not hope this version is buggy
* Added the missing sources (forgot to put under source control)
Version 1.2
* Added StylusLock indicator when locked. Works for TouchFlo3D screen as well as other Today screens.
* Because the StylusLock indicator is now visible if locked, it no longer vibrates when unlocked (saves extra battery)
* Kept StylusLock as simple and small as possible (only 1Kb in memory) and does still consume no CPU (check with Task Manager!!).
* v1.2 is even a bit smaller then v1.1, although the StylusLock indicator has been added.
Version 1.1
When the stylus is put inside it will only vibrate if "stylus Lock mode" gets enabled and/or the phone is getting locked. If there is no vibration, you know the phone is not locked and "stylus Lock mode" is disabled. Added source code.
Version 1.0
First released version
FAQ
Q: Why do you not shutdown the power (go to sleep) when locking is enabled
A: Dependent of the usage, e.g. using GPS navigation or in a call, you do not want to go to sleep mode, because you still want to see the screen or operate. Now the sleep mode is just triggered by Windows Mobile settings, which should be convenient enough. But if you want to go to sleep mode immediately, press the Power Button and insert the Stylus IN. A double vibration will be felt, if the phone is locked.
In version 1.3 onwards it will go to sleep when in styluslockmode and the backlight goes off. Make sure that your GPS software does not trigger the backlight off. I use OziExplorer and IGO 8, and there this works. In TomTom, the backlight goes off, so I do not know if there is a setting to disable that. If you do not want the phone to go to sleep when the backlight goes off, you can overrule the setting suspendOnBacklightOff in version 1.4.
Q: Can you add a lock/unlock indication
A:Added in version 1.2.
Q: Can you add a method for locking by pressing a (TouchPanel) button
A: I am looking into the NavSensor to unlock or lock possibility in addition of Stylus control.
Q: Why do you not make it possible to disable only the TouchPanel
A: In my opinion, only locking the TouchPanel will not avoid e.g. missed calls, because also the hardware keys can be accidently pressed (although a little bit less likely). There are also problems reported that it unlocks, when you do not answer a call. This version (also locking hardware keys) does not have this problem. However, I added the possibility in version 1.4 to overrule this via setting lockTouchPanelOnly.
Q: Why do you not lock when going to/resuming from sleep mode
A: When you are in "stylus lock mode" it will be locked already if the stylus is IN. Otherwise you have decided not to use the "stylus lock" feature. You just can put the TD on a table and do as if StylusLock was not active when "stylus lock mode" is disabled.
Q: Why is this version better than SensorLock
A: The GSENSOR gestures in SensorLock uses CPU by polling (and takes also more battery). Also the way of turning is not so easy always (drop your TD). StylusLock does not have the vibrate bug. Accidently turning may lock/unlock the TD. Stylus control is the simplest way to operate your locking, why need an extra method for it?
Q: Is the Vibrate bug of SensorLock solved in StylusLock
A: Yes, the vibrate bug does not appear in StylusLock.
Q: Can you change the Vibrate into Beeps
A: In version 1.4 you can overrule the default setting. Even you can use both or none.
Q: Why is StylusLock better than other solutions?
A: It consumes no extra battery/CPU and is as simple as possible but still powerful. It can be used in conjunction with other software and does not interfere with e.g. GSENSOR applications.
Q: Can you please add this or that feature?
A: The intention is that the program must be lean and mean and still be easy to operate. So yes, you can ask for features and I will consider them, if it is easy to do (complexity) and does not influence battery usage. In version 1.4 default settings can be overruled. If you need more advanced features or more control, take a look at other applications.
Q: Which other solutions exist
A: This is a list of other solutions
* Get A Reward! Create A "answer Only With Hw Buttons" Option! http://forum.xda-developers.com/showthread.php?t=414731
* S2U2
* PDAVIET's dialer
* CSDEVCTRL http://forum.xda-developers.com/showthread.php?t=386451
* SensorLock http://forum.xda-developers.com/showthread.php?t=422871
* Answerkeys Disabler http://forum.xda-developers.com/showthread.php?t=425650
Very Nice >>
Nice one. The techniques for locking and polling are becoming pretty obvious now, and some great ideas are being implemented!
However, when on my bike (yeah we Dutchies ride them continuously ) and a call comes in, I'd have to let go of both hands... Hmmm..
Anyway, congratulations with an application that does NOT eat your battery! Job well done
drvdijk said:
Nice one. The techniques for locking and polling are becoming pretty obvious now, and some great ideas are being implemented!
However, when on my bike (yeah we Dutchies ride them continuously ) and a call comes in, I'd have to let go of both hands... Hmmm..
Anyway, congratulations with an application that does NOT eat your battery! Job well done
Click to expand...
Click to collapse
Ah, just a reason to stop when someone calls
Is also safer.
Man...you did a great job....another dimension of locking your device with the stylus has born.....thanxx for this great app
Thanks for your work.
Thanks for the work. Going to give this one a try.
ZuinigeRijder said:
There are already a lot of applications to disable touchpanel and/or hardware keys for the Touch Diamond. I added another simple one:
StylusLock
Click to expand...
Click to collapse
Sweet! I'm glad SensorLock got you started.
As for trying to fix the vibration bug, what have you done exactly? The vibration notifications look similar, is the vibration based on the SensorLock one?
any youtube about styluslock for me?
surfsmurf said:
Sweet! I'm glad SensorLock got you started.
As for trying to fix the vibration bug, what have you done exactly? The vibration notifications look similar, is the vibration based on the SensorLock one?
Click to expand...
Click to collapse
There are a couple of measures which can contribute to not having the vibration bug in StylusLock:
- I sleep 5 seconds, before doing some stuff, when started StylusLock first time
- I start always forced unlocked, when just started (so when it is vibrating, it maybe stops then)
- I do not use it in combination with the GSENSOR (maybe that can cause problems)
- Soft Resetting is normally done unlocked (because the Stylus is out ;-)
- I lock both the TouchPanel as the hardware keys (like in SensorLock 0.1)
- I vibrate only when not locked (so just before locking, and just after unlocking)
- I do not lock on PBT_RESUME
- I always unlock when I exit StylusLock
However, I am not sure it will be solved with the above things and which one is responsible for solving the vibrate bug.
Especially, because I did not having encountered this bug, also not with SensorLock.
Hope this gives you some clues/ideas.
But I am not sure my approach solves the vibration bug.
I think it is too early to conclude on that, let people try StylusLock.
Great job! Would you be kind enough to share the code?
ZuinigeRijder said:
There are a couple of measures which can contribute to not having the vibration bug in StylusLock:
Click to expand...
Click to collapse
Thanks for sharing, there's some interesting points in that list.
Personally I think the vibration bug in SensorLock is caused by bogus results from the G-Sensor, causing bogus gestures to be detected continually. The vibration code itself is SO simple I simply cannot see where a bug might be hiding in it.
I doubt very much that StylusLock would be suffering from the same problem, but as I said, it's an interesting list of points.
hi,
i am currently using answerkeys disabler, does this drain battery?
second question, am i correct in thinking, that with auto-lock enabled the only way to answer a call is to press the hardware answer key?
would this be a better app than answerkeys disabler to stop answering calls in my pocket?
Answerkeys Disabler does not drain power. StylusLock doesn't either. SensorLock a little more, but still nothing compared to S2U2.
I love it !
A few days ago i discoverd SensorLock.
I ran through the vibrating bug and others disadvantage (i lose the transcriber*).
With the version 0.3.0 of SensorLock, i was able to 'play' with it and i was kind of deceive :
The g-sensor-phone-360° thing was a good idea but finally it's not convenient as you said in the faq.
So i tried your application : great !
And it does not consume power at all, cool !
Like the 0.3.0 version of SensorLock, no vibrating bug anymore at start in your program.
Your tutorial is good but don't explain the auto lock mode stuff for beginners, i would have say something like :
There is 2 mode :
1 - stylus in = phone locked
2 - stylus in = phone not locked
In fact the second mode permit not to use the lock functionnality, in order to use your fingers on the touchpanel, rather than the sytlus.
Moreover : nothing happens 'automatically' after some time, so the words 'auto lock mode' is kinda wrong.
Last thing :
when switching to auto lock mode or not, there is no differences
maybe 3 short vibrations when switching to no auto lock mode ?
or just a different icon in the upcoming systray icon ?
Personnaly i don't need a systray icon but why not...
* For those concerned : I didn't reinstall my rom to get it back, i just desinstall SensorLock
Great app. Tkx
looking good, one add on suggestion, after watching the sprint diamond review, i saw that the sprint version turns on the the device when you pull the stylus out. maybe something you might be interested in looking at.
drvdijk said:
Answerkeys Disabler does not drain power. StylusLock doesn't either. SensorLock a little more, but still nothing compared to S2U2.
Click to expand...
Click to collapse
thanks for your help, i will probably stick to Answerkeys Disabler as it doesnot require intervention!
thanks for the app (Answerkeys Disabler) BTW
SensorScroll uses the HTC Touch Diamond/PRO Gesture Wheel to scroll up and down inside windows which allow scrolling (has a scroll bar). It can also emulate key pressing instead of scrolling.
It is in beta stage, please use carefully. All bug reports, fresh ideas and recommendations are welcome.
Instructions:
1. Install the application. It adds shortcut in Programs and in \Windows\Startup folders!
2. Right after installation you can run the application from Programs shortcut to start using it. There is no need for soft reset to have it running for the first time!
3. To use the application open a Window with a vertical scroll bar like Programs or File Explorer and try rotating the scroll sensor clockwise for scroll down and counter clockwise for scroll up. Don't forget to try the touch action too (double tap on the central button to switch on/off and touch the direction keys)
4. To fine tune the application behavior use the SensorScroll Settings application
5. Have fun!
6. To stop, run it again and you will have an option to stop it.
Notes:
Inside installation folder there is a file named no_process.txt. The file contains a list of process names which will not be affected by the application (or by SensorScroll Settings). It already has some entries like opera, teeter, etc.
The application is freeware (and will always stay free)
Known issues:
* Does not work with GScroll ! Both programs act like they have disabled each other.
Todo:
* Clear the source code and add some comments
* Open the source code if i consider it good enough to be open
Search for new ideas:
We can do something with the rest of the touch sensitive area. I'm collecting ideas. We can use single, double or triple click. Known limitation: you could track press and release coordinates, but cannot track finger movement (at least I don't know how). If you come with a good idea please share it and post a reply. Thanks in advance!
History:
* v0.7.1 (20.05.2009)
- Fixed a nasty bug resulting in SensorScroll working with all programs including those who needs to be ignored
- Temporary removed windows enumeration in SensorScroll Settings. I'll try to put some more complex code to handle poorly working API functions in the next version.
* v0.7 (17.05.2009)
- Fully changed working principles. Should be much more stable and compatible now.
- Added support for screen rotation. Read the manual about the 3 key screen rotation.
- Added support for process identify. Read the manual.
- Added handling of power notifications. Now it should consume almost no CPU when suspended.
- Added support for preventing the device to go to suspended state while using the d-pad
- Added support for vibrate feedback for "touch gestures switch", "screen rotation", "process identify"
- Fixed problem with saving/loading settings with non english versions of windows mobile
- Fixed problem with double tap working not only for the center button, but also in other areas (home, back, call, end call)
- Removed process enumeration in SensorScroll Settings. This caused more problems then it solved.
Full version history can he found here
Old version 0.6 can be found here
Thanks. Works well so far. One early issue I noticed upon installing your .cab is my device freezes for no apparent reason. I am also running GScroll, may have something to do with that. I'll try disabling it and report back.
Great app...props already http://www.fuzemobility.com/?p=1479
mr.jcarter said:
Thanks. Works well so far. One early issue I noticed upon installing your .cab is my device freezes for no apparent reason. I am also running GScroll, may have something to do with that. I'll try disabling it and report back.
Click to expand...
Click to collapse
Confirmed.... Does not play nice nice w/GScroll. After disabbling GScroll it works great unfortunately I need GScroll so I can have the double tap functionality to bring up SecondToday
Randomly the program will stop working (not sure if it completely shuts down or if its actually running, but not working). Instead of scrolling the page, it will start to scroll by each item. For example, in the Program menu it will go from app to app.
Works Perfectly for me.
Thanks!
The Mobile Spoon
Working perfect - thank you!
edit: after testing as already pointed out seems to turn off.
How does this compare with the cabs already out? I mean does it work in EVERY app? I mean I use RRE's Smart Touch Wheel Scroll.cab, but I'll try this one and see if there is any difference.
Kraize - this works in far more applications. It's really an expansion because you can set it to leave the defaults in place that Diamond Tweaks puts in. The only problem appears to be that it turns off at some points. Not sure what is causing the behavior.
Great App!!! is there any way you could make this scroll through touchflo? Like left 2 right? Always wanted this....lol sorry . Anyways thank you!
AT&T FUZE Touch Pro unstable
Awesome idea! Installed it on my 1 day old AT&T FUZE and crashed a few times and rebooted the phone once. Hopefully will be fixed soon. HAve the feeling AT&T touch flow 3D is causing the issue.
Nice app any way to get this to work with S2U2?
Thank you for sharing, I will give it a try
cheers
Works fine on my Touch Pro. Tnx mate for this!
the program chashes at my touch pro after a few minutes and doens´t scoll anymore so i have to exit and restart it again.
why runing additional app when this should be integrated just need to tell registry
check this - http://forum.xda-developers.com/showthread.php?t=406206
i don't have stability problems, but the app doesn't survive the first suspend
sheitan said:
why runing additional app when this should be integrated just need to tell registry
check this - http://forum.xda-developers.com/showthread.php?t=406206
Click to expand...
Click to collapse
it's still better to import dozens of reg files after each hard reset + it works with ALL toolbar-scroll windows ^^
hello, is it possible for you to make a version wich moves LEFT <> RIGHT instead of UP <> DOWN ?
I mean to scroll tabs on manilla, to change word when typing a sms cause may big fiingers are to dummy to easily use the left right keys
PS : excuse my english, i'm french
Perfect..
It works fine on my device
Thank a lot man
Thank you for your replies! I'll check the application with GScroll. I've never used it so far. I hope it will be possible to fix the problem.
Hi guys, this is my first time to post here
keyx has found a registry tweak that can fix the backlight off issue!
Click here to #94 for more details
This fix has been integrated to Backlight Controller since v0.9.5.3
[ Description rewrited on 11-Apr-2009 ]
The brightness settings in WM6 is so difficult to use with fingers. Also there is a known bug of 612c that the LCD backlight cannot be turned off by most of the software like WMP...
But Backlight Controller can solve all this problem
The interface is simple (Simple is beautiful), a very big slider that is so easy to use with your fingers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Backlight Controller will detect AC status automatically and modify the corresponding backlight settings, that's why there is only 1 slider for both AC and Battery mode, when the AC power plugged in / removed, the icon at the top left corner will change:
Landscape mode is supported too:
The most important feature - Toggle Screen
Since the LCD backlight of 612c cannot be turned off by standard API, the toggle screen feature of music players like WMP, Core Player has no use on 612c. Just run Backlight Controller and select Toggle Screen, 612c LCD backlight will be turned off completely and save your battery power!
Apart from selecting Toggle Screen from softkey menu, press "ENTER" on 612c keypad or use command line switch (/togglescreen) can also activate Toggle Screen.
***When Toggle Screen is activated, the screen and keypad will be Locked! you can only unlock 612c by pressing "ENTER". If you forgot how to unlock, just power Off and On (press power button 2 times), the backlight will on and screen will display "Press ENTER to unlock"
Command Line Switch Summary:
/setmax:
Set Max brightness /setmin:
Set Min brightness /setlevel x:
Set backlight level to x /togglemax:
Switch between Max brightness and original level /togglemin:
Switch between Min brightness and original level /togglescreen:
Turn off screen and backlight /lockandoff:
Lock the device using Standard WinMo lock and then turn off the device automatically. /increase:
Increase brightness /decrease:
Decrease brightess /?:
Display help
Command Line Switch Example:
WM6_612C_Backlight.exe /togglemax
- Set brightness to maximum, call this again will roll back to original brightness level
WM6_612C_Backlight.exe /setlevel 3
- Set brightness level to 3
WM6_612C_Backlight.exe /togglescreen
- Turn off LCD and backlight, and device will be locked. To exit, press "ENTER" on your keypad. (Also, turning your device off and on, you will see the unlock screen)
I hope you all will enjoy this.
If you have any suggestions / bugs encountered, please feel free to contact me. (Email is available in the software "About" screen)
======[ Release notes ]======
Version 0.9.5.3 (released 2009-10-28)
Changes:
- Install cab will now change Registry for the Backlight Fix (Thanks keyx for this great finding)
- Removed ToggleScreenMonitor (Because it's replaced by Registry fix)
- Added LockAndOff.lnk at installation folder, this will help you to lock and turn off device by just one click.
- Added more command line switch
/lockandoff:
Lock the device using Standard WinMo lock and then turn off the device automatically.
Remarks:
Although the newly added switch is not so much related to backlight, but I really want to add this feature. I found that Power button malfunction is very common on 61x series, I hope this lockandoff switch can reduce the use of Power button
===
Version 0.9.5.2 (released 2009-05-28)
Changes:
- Use PNG file instead of integrating BMP, support Skin Change
- Redraw the AC status icon and makes the drag button transparent
- Enhanced button drag algorithm
Remarks:
For Skin Change, just replace the corresponding PNG files under Graphics directory.
===
Version 0.9.5.1 (released 2009-04-22)
Fix:
- Error prompt of can't open the file 'WM6_612c_backlight.exe'
Remarks:
Please report if this release can fix the Can't open issue or not Thank you!
===
Version 0.9.5.0 (released 2009-04-20)
Changes:
- Cab file is now available for easy installation
- First release of ToggleScreenMonitor
- Backlight Controller can now intercept ScreenOff event, and start ToggleScreen mode automatically (Tested with WMP and CorePlayer only, please provide feedback)
- Added 2 more D-pad control: Right - Increase brightness / Left - Decrease brightness
===
Version 0.9.1.7 (released 2009-04-16)
Fixed
- Backlight Timeout value cannot restore if Device Power Off and On during ToggleScreen Mode.
===
Version 0.9.1.6 (released 2009-04-14)
Fixed
- D-pad Up/Down key turn on the backlight in ToggleScreen Mode (bug in v0.9.1.5)
===
Version 0.9.1.5 (released 2009-04-14)
Changes
- Automatically Exit after unlock from ToggleScreen Mode, making it more convenient to use.
- Flipped Landscape Mode UI, increase brightness from Left to Right
- Support D-pad control: Up - Increase brightness / Down - Decrease brightness
===
Version 0.9.1.4 (released 2009-04-11)
Fixed:
- Backlight timeout value will be restored when device unlock.
Changes
- When there is incoming call, automatically turn on LCD backlight
===
Version 0.9.1.3 (released 2009-04-02)
Changes:
- Toggle Screen (Beta) will lock screen and keyboard now, press "ENTER" key to unlock the device
- Added more command line switch
/togglescreen:
Turn off LCD screen and backlight, also lock the device, press "ENTER" to unlock
Known Issues:
- Backlight timeout will be disabled when Toggle Screen feature start, this will not restore automatically, user should enable this by themselves.
===
Version 0.9.1.2 (released 2009-02-06)
Changes:
- Added "Toggle Screen" Feature, completely turn off LCD backlight. (Beta)
(To turn on Backlight again, press "ENTER" button, above "POWER" button of your device)
Known Issues:
- The Backlight Timeout will be disabled after running Toggle Screen. There is a conflict between them, I'm solving this problem.
- After Toggle Screen, LCD is blank but still active! Don't touch it after Toggle Screen. I'm also solving this problem...
===
Version 0.9.1.1 (released 2009-02-03)
Changes:
- Added Landscape mode
===
Version 0.9.1.0 (released 2009-01-10)
Fixed:
- Spelling mistakes in help page
Changes:
- Redraw the EXE Icon (The circle blue bulb)
- Modify the About Dialog
- Added more command line switch
/increase:
Increase brightness
/decrease:
Decrease brightess
===
Version 0.9.0.7 (released 2009-01-09)
Changes:
- Added command line switch support
/setmax:
Set Max brightness
/setmin:
Set Min brightness
/setlevel x:
Set backlight level to x
/togglemax:
Switch between Max brightness and original level (suggested by hilline)
/togglemin:
Switch between Min brightness and original level
/?:
Display help
===
Version 0.9.0.6 (released 2009-01-08)
Fixed:
- Change back Dialog title to "Backlight"
===
Version 0.9.0.5 (released 2009-01-07)
Fixed:
- Can not drag the slider when it is at top or bottom of the slide area
Changes:
- Reduced EXE file size (397KB => 259KB) by reducing the BMP size
- Modified About box message
===
Version 0.9.0.4
Fixed:
- Disable "Press and Hold", avoiding that "Rotating circle"
- Appear of White screen when application start
Changes:
- Added About box at Right softkey
===
Version 0.9.0.3
Changes:
- Detect Power state change in run time.
===
Version 0.9.0.2
Fixed:
- AC Power detection failed in some cases
Changes:
- Directly push the scale bar to adjust the backlight, not only
dragging the button. (Suggested by biogerm)
===
Version 0.9.0.1 (released 2009-01-06)
Info:
- First release of WM6_612C_Backlight
======
i'll give this a go, but currently i use the D-Pad app that Zoltair posted here
http://forum.xda-developers.com/showthread.php?t=435026
This way i dont have to be able to seen the screen to increase its brightness ie im in full sunlight i dont need to find the icon to start the program to increase the brighness.
welcome to xda ke_steve_le
Your application is amazing, thanks. Very useful application. Can you make it skinnable, something like screen in attachment ?
thebranded said:
i'll give this a go, but currently i use the D-Pad app that Zoltair posted...
...
...d the icon to start the program to increase the brighness.
Click to expand...
Click to collapse
Yea I'm using cz app too~ I use that for gaming
But when it change backlight settings, it will alter my keyboard LED too, I don't like that anyway..
sergiorus said:
welcome to xda ke_steve_le
Your application is amazing, thanks. Very useful application. Can you make it skinnable, something like screen in attachment ?
Click to expand...
Click to collapse
Yes I'm making my app skinnable and support landscape~
However, the skin in your attached image may not be supported
Since I'm moving a static image up and down as a slider in my app, is not the same type as your attached image.
Any updates of this useful application?
sergiorus said:
Any updates of this useful application?
Click to expand...
Click to collapse
Hmm.. sorry about this late reply, I have made it works under Landscape mode ... I will update the thread in this few days
Thanks, i will wait for it
PS Can you make an application to toggle flash lamp, just turn it on-off? (not through camera menu)
sergiorus said:
Thanks, i will wait for it
PS Can you make an application to toggle flash lamp, just turn it on-off? (not through camera menu)
Click to expand...
Click to collapse
I want it too.. Since there is no standard API to control the camera flash light, it depends on differenent devices.. I dont know how to control 612's camera LED on/off..
v0.9.1.1 released.
It's now support Landscape May be it can work on 912c too? Any body can give it a try?
ke_steve_le said:
I want it too.. Since there is no standard API to control the camera flash light, it depends on differenent devices.. I dont know how to control 612's camera LED on/off..
Click to expand...
Click to collapse
i are interested too. but i don't find nothing about the camera led.
forum people stand-up and help us!!!
Wow! thanks for update
can you make this program with changing background?
I would like to use manila standart background (picture is photoshop)
And for slider skin maybe this files help you
sergiorus said:
can you make this program with changing background?
I would like to use manila standart background (picture is photoshop)
Click to expand...
Click to collapse
yes the background I can make it to use bmp file so that you can use any image for it.
But for that slider, I need to think about that, since your slider is not as easy as replacing the skin, it can't share the same logic with the original slider..
making it to support both or make a special version? hmm... anyway, I will do it when I have time~
Version 0.9.1.2 (released 2009-02-06)
Changes:
- Added "Toggle Screen" Feature, completely turn off LCD backlight. (Beta)
(To turn on Backlight again, press "ENTER" button, above "POWER" button of your device)
Known Issues:
- The Backlight Timeout will be disabled after running Toggle Screen. There is a conflict between them, I'm solving this problem.
- After Toggle Screen, LCD is blank but still active! Don't touch it after Toggle Screen. I'm also solving this problem...
Version 0.9.1.2 (released 2009-02-06)
Changes:
- Added "Toggle Screen" Feature, completely turn off LCD backlight. (Beta)
(To turn on Backlight again, press "ENTER" button, above "POWER" button of your device)
Click to expand...
Click to collapse
Em... the power button do the same. Or i dont understand something
sergiorus said:
Em... the power button do the same. Or i dont understand something
Click to expand...
Click to collapse
They are not the same
Have you ever used the Toggle Screen feature in Windows Media Player? Normally, it will turn off the LCD and backlight and continue to play the music, but it doesn't work on our iPAQ 612c. After toggle screen (Not my app, is WMP), the LCD becomes blank, but the backlight is still on! (You can try this in a dark place, look at the edge of the LCD screen and you will find that the backlight is on).
But yea, you may say that we can press Power button and the Music is still playing~ But this is not supposed to be a Power button feature of a Normal PPC... and also, this trick only works on WMP, but not others like CorePlayer.
Let me show you an example and you will see the difference:
Connect 612c with your PC thru ActiveSync, press Power button, the connection will lost.
But, if you use Toggle Screen of my app, the connection is still there, just the LCD and backlight turns off , device is still running.
Hope this information is useful for you~
hi all, I would like to ask
whether the time to connect your pc PDA problem with the backlight? my settings "backlight off" 30 seconds, and automatic "device off" 1 minute, but when connect via pc after 1 minute PDA screen blank (black screen) but the backlight stays on
anyone?
kancrutt said:
hi all, I would like to ask
whether the time to connect your pc PDA problem with the backlight? my settings "backlight off" 30 seconds, and automatic "device off" 1 minute, but when connect via pc after 1 minute PDA screen blank (black screen) but the backlight stays on
anyone?
Click to expand...
Click to collapse
No, I don't have this problem
I'm using ROM from yevg001 (WM6.1 20270 REV 1.2 Fix Manila 2D)
ke_steve_le said:
No, I don't have this problem
I'm using ROM from yevg001 (WM6.1 20270 REV 1.2 Fix Manila 2D)
Click to expand...
Click to collapse
hmm,,or maybe its hardware problem?
Hi All,
Updates for G-Trigger (v0.9.0+ beta):
First is, you can shake your device to change wallpaper of Today/Manila/S2U2, second is, save a screenshot and third to show/hide SIP (As suggested by tevike)
I have lowered the threshold value up to 5 for front-back action as some people find it very hard to shake. Although lower value less than 10 does not work on my device. If you find hard to shake try setting threshold value for front-back lesser than 10 and uncheck option "Discard accidental shakes".
I have added priorities to profiles in this version. It is useful in combination with Auto-Trigger profile option. If you have one or more profile which satisfies auto-trigger option for current device state, then higher priority profile will be selected to trigger an action.
This version 0.9.0 beta seems to be pretty stable. Hope it works fine for all.
For updated features from v0.8.0 onwards look here.
G-Trigger website: http://g-trigger.kneps.com
Thanks,
Krupal Desai
====||====||====||====||====||====||====||====||====||====
G-Trigger v0.9.2 beta [10-Jul-2009]
By Krupal Desai
Video: See it in action...
G-Trigger is a G-Sensor based ^shake^ detector application. It allows to trigger a predefined action on shaking your mobile phone (built-in with G-Sensor) in particular direction. Currently it is in development phase, so please bare the bugs.
Supported shaking directions:
Horizontally
Left to right
Right to left
Vertically
Top to bottom
Bottom to top
Front & Back
Front to back
Back to front
It will trigger the specified action when phone is forcibly moved from left to right or moved as above mentioned directions. Also you can assign different actions with keeping device face up and shaking device in any of the above action or keeping device face down and shaking device in any of the above action.
Currently supported actions:
Close/Minimize active window
Dial a number
Answer/Reject incoming call
Launch Program
Ringer Loud/Vibrate/Silent
Screen orientation
Send Keys*
Task Switch
Turn On/Off screen
WiFi/Bluetooth/Phone radio - On/Off/Toggle
Media Controls#
Volume Control
Simulate Power Button - Power Off/Power On/Long Press Power Button
Open control panel settings
Activate profile
Save Screenshot (BMP/JPG/PNG/GIF at predefined location) *new
Change Wallpaper (Today Screen, Manila Home & S2U2) *new
Show/Hide/Toggle On-Screen Keyboard (SIP) *new
*Please refer to readme.txt for sending special keys.
#Currently supported media players are: Windows Media Player, S2P, Microfi Nitrogen, Core Player, TCPMP, Pocket Player, Pocket Music and Manila (TF3D) Music Tab.
G-TriggerService will be suspended till the program specified in exceptions list is active.
Known Facts:
OSD is displayed with some delay after event is occurred
Sometimes shake actions are not triggered when device is busy processing
Action Media Control "Stop" does not work for all players
Media controls for "Pocket Player" works till it's window is active or minimized (not working when in notification mode)
Further development:
Display configured actions as OSD when device is lightly shaked
Add more actions like "Navigate Manila Page", "Open Quick Launch" etc on shaking
It is developed for HTC Touch Diamond. I have not tested it on any other device. Let me know if you try it on other device.
NOTE: Although running this application does not seem to make any damage, I take no responsibility for any kind of damage caused to the device or data due to this application.
PS: Credits to Koushik Dutta for sharing G-Sensor managed code for Diamond. Many thanks to Ageye for sharing updated G-Sensor code for Samsung Omnia (here).
Usage:
Transfer .cab file to any location in device.
Run the .cab file and install application to device storage.
Run the “G-Trigger” shortcut from programs.
Click “New” button on “Action” tab.
Enable the check boxes for the actions you want to activate.
Assign any action by clicking “…” button on the right side of action text box.
Click “Save” button on edit profile page, again click “Save” button on main page.
Click “Start” button to start the service.
Shake your phone and enjoy!
How to shake the phone?
Hold the mobile phone facing yourself and perform following:
Left to Right:
Quickly move the phone from current position towards right hand side for about 6 inches (Increase speed during motion from slow to fast and suddenly stop at the end to feel the shock)
Top to Bottom:
Quickly move the phone from current position to downwards for about 6 inches (Increase speed during motion from slow to fast and suddenly stop at the end to feel the shock)
Front to Back:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hold the phone facing yourself and near to you.
Quickly move the phone from current position to far away from you for about 6 inches (Increase speed during motion from slow to fast and suddenly stop at the end to feel the shock)
Back to Front:
Hold the phone facing yourself and little far from you.
Quickly move the phone from current position to nearer to you for about 6 inches from the last position (Increase speed during motion from slow to fast and suddenly stop at the end to feel the shock)
Click to expand...
Click to collapse
Quick guide to Auto Trigger:
If you want G-Trigger to behave differently for different active program, it's now possible. For example, you want left to right for playing next track, right to left for playing previous track, only if Windows Media Player is active then create a new profile, assign left to right for next track, right to left for previous track and check "Auto Trigger" with program name as wmplayer.exe. Bingo!!! Its done.
How G-Trigger works:
G-TriggerService.exe application runs all the time and polls the G-Sensor to get current position of the device. It polls G-Sensor for about 10 times a second and observes the positions of the device. It keeps track of last 5 positions and scans all the 5 positions and checks if any shake is detected. If shake is detected it looks for action and triggers an action.
FAQ:
1. Does polling of G-Sensor all the time damages it?
-It does not seems to damage sensor by polling but I don’t take any responsibility in a case. Use it at your own risk!
2. Does G-TriggerService impacts my device’s battery power?
-Yes! It runs all the time as soon as your device is awake and it keeps on polling the G-Sensor, so it will consume some battery power. Although, I am running it all the time since I developed, I don’t see any legible battery consumption. Though you need to benchmark if you want to see exact battery consumption.
3.How much memory does G-TriggerService eats?
-G-TriggerService takes around 500KB when OSD is off and takes around 1MB if OSD is on.
Screenshots:
Requirements:
HTC Touch Diamond (Not tested on any other device)
WM6.1/WM6.5/WM6.5.1
.Net Compact Framework v3.5
Supported devices as per user reviews:
HTC Touch Diamond
HTC Touch HD
HTC Touch Pro
Samsung Omnia (i900/i910)
Shake it at your own risk.
Bugs / Suggestions / Ideas are invited.
Email: [email protected]
Visit: http://g-trigger.kneps.com
I accept donation:
Click here to donate.
Donations Received:
2 USD chizzy58
10 USD 1800PocketPC.com
5 USD Jiri Kucera
3 USD Marek Pilarcik
5 USD 1800PocketPC.com
2 USD Daniel Pingen
10 USD mikeck (Mike Kanel)
3.33 USD rev0l
5 USD Jaz (Jasen Nannini)
10 USD Selby Stephen
Thanks a lot
AppToDate download count:
G-Trigger Change Log
G-Trigger v0.9.2 beta [10-Jul-2009]
Updated: Change Wallpaper Action with next/previous/random support
Fixed: Browsing for application files bug for "Launch Program" action
G-Trigger v0.9.1 beta [10-Jul-2009]
Fixed: Null reference bug on fresh installation
G-Trigger v0.9.0 beta [02-Jul-2009]
Added: Actions
Save Screenshot (BMP/JPG/PNG/GIF at predefined location)
Change Wallpaper (Today Screen, Manila Home & S2U2)
Show/Hide/Toggle On-Screen Keyboard (SIP)
Added: Added option to enable/disable debug logs
Added: Lower threshold value up to 5 for front-back actions
Added: Profile priority setting for auto-trigger profile option
Added: Included new samsung SDK for G-Sensor in setup
Fixed: Unable to detect screen is off on certain devices
Fixed: Auto Start Service on device boot up issue (introduced in 0.8.0)
Fixed: Few minor bugs
G-Trigger v0.8.1 beta [15-Jun-2009]
Fixed: Repeated debug logging like "There is something wrong with g-sensor! Lets refresh the sensor!"
G-Trigger v0.8.0 beta [14-Jun-2009]
Added: Different actions for shaking device when FaceDown and shaking device when FaceUp
Added: New user interface for organizing profiles with ease
Added: Auto-trigger profile option “Manila music is playing”
Added: Import/Export settings and/or profiles
Fixed: Samsung Omnia G-Sensor code to sort out issue of service crash after device is awake
Fixed: Auto-resize configuration utility dependent on resolution
Fixed: Faster editing of shake actions after opening edit profile once
Fixed: Modification to profile actions no more required to hit save button to make it active
Updated: Slight modification to shake algorithm to make front-back action more sensitive
Updated: new registry location ‘HKCU\Software\Kneps\G-Trigger’ (you will require to delete older location ‘HKCU\Software\G-Trigger’ manually, I apologize for this).
G-Trigger v0.7.1 beta [16-May-2009]
Added: Option to Discard Accidental Shakes (Uncheck this option if you feel very hard to shake)
G-Trigger v0.7.0 beta [10-May-2009]
Added: Actions
Open control panel settings
Activate profile
Added: Support for *.mscr file for 'Launch program' browsing
Added: Auto trigger profile when specified program is active
Added: Editing profile name
Fixed: Few minor bugs
G-Trigger v0.6.0 beta [26-Apr-2009]
Added: Actions
Bluetooth/Phone Radio - On/Off/Toggle
Simulate Power Button - Power On/Power Button Long Press
Updated: Optimized the shake detection algorithm
Added: Profiles - Quick change for the preset actions
Fixed: Error when comma entered in Program Launch arguments
Fixed: Few other minor bugs
G-Trigger v0.5.1 beta [13-Apr-2009]
Bug Fixed: Service start on device startup for all languages.
G-Trigger v0.5.0 beta [12-Apr-2009]
Added: Actions
Volume Control
Simulate Power Button
Added: Setting for vibrate LED number
Fixed: Delayed service start on device reboot
Fixed: Restart service when device is awake (for Samsung Omnia)
G-Trigger v0.4.0 beta [05-Apr-2009]
Added: Action for Media Control (Many more players)
Added: Conditional trigger action
Added: Disable Action Exceptions
Added: Option to disable actions when screen is off
Added: Option to suspend service during phone call
Added: AppToDate Support
Fixed few bugs
G-Trigger v0.3.2 beta [02-Apr-2009]
Bug fix: Omnia service crash on sleep
Added: Actions
Screen Off (With device lock)
Media Controls (Windows Media & Manila Music Tab)
Added: AppToDate Support
G-Trigger v0.3.1 beta [31-Mar-2009]
Service startup bug fixed
Added: Actions
WiFi On/Off/Toggle
Media Controls (Not yet implemented completely)
G-Trigger v0.3.0 beta [30-Mar-2009]
Added: Feedback settings (Vibrate, play sound & OSD)
Added: Actions
Task switch
Screen orientation
Ringer profile (Silent-Vibrate-Loud)
Fixed few bugs
G-Trigger v0.2.0 beta [23-Mar-2009]
Added: Exceptions list (Service will be suspended till application specified in exceptions list is active)
Added: Actions
Dial a number
Answer/Reject incoming call
Launch Program
Turn ON/OFF screen
Send Keys
Close/Minimize active window
Added: Errors will be logged to "G-Trigger\Log"
Updated: Shake algorithm optimization
G-Trigger v0.1.0 beta [18-Mar-2009]
First release
This will be a useful application in my daily life.
Thanks!
Holy ****! Sweet! Now I don't need programmable buttons like the tilt anymore
thx,preety usefull app, i will try it
?
Not got the time to test this right now, but can this app answer/end calls with a shake? or task switch? or end a running program? if not, then is it a possibility for future releases?
In pipeline
uniqueboy said:
Not got the time to test this right now, but can this app answer/end calls with a shake? or task switch? or end a running program? if not, then is it a possibility for future releases?
Click to expand...
Click to collapse
Currently not supported. But task switch & close foreground app are in pipeline.. though.. it will take some time . Thanks for idea about answer/end calls.
Working on HTC Touch HD!!
This will be such a great app. Does it auto start with windows??
wez89 said:
This will be such a great app. Does it auto start with windows??
Click to expand...
Click to collapse
Yes, there is option to auto start on "Advanced" tab. Let me know if you find any issue.
Takie said:
Working on HTC Touch HD!!
Click to expand...
Click to collapse
Great!! Update me for device dependent flaws..
krups said:
Yes, there is option to auto start on "Advanced" tab. Let me know if you find any issue.
Click to expand...
Click to collapse
Great !! i will test now and report any bugs
Ok just tested a few programs, found windows media player doesnt respond to any shakes, no message appears to come up so it registers the shake and program but fails to open winsows media player, anybody else have the same issue??
EDIT: got media player working! dont select the windows media player option from program files, instead goto the windows folder and select 'wmplayer.exe'
Sorry about triple posting lol
I have also found in order to register a 'left to right' shake you have to start by shaking your phone to the right. Start by shaking your phone to the left for a 'Right to left' shake. If i shake my phone 'right to left' once, it opens the 'left to right' application. Hope this is clear.
'My documents' doesnt work with 'left to right' shake from what i have tried
Great app any way im sure once bugs are fixed this will be great
Did anyone try this during car use? I mean, there is some g-force involved, in driving... steer, brake, accelerate, bumps...
teorouge said:
Did anyone try this during car use? I mean, there is some g-force involved, in driving... steer, brake, accelerate, bumps...
Click to expand...
Click to collapse
I havnt tried it during driving but im sure braking, steering and accelerating will have no effect although a big and i mean a big bump or bang may just shake the device abit
You need a quick, hard shake for it to register as a shake
wez89 said:
I havnt tried it during driving but im sure braking, steering and accelerating will have no effect although a big and i mean a big bump or bang may just shake the device abit
You need a quick, hard shake for it to register as a shake
Click to expand...
Click to collapse
G-forces aren't significant unless you're at Canada's Wonderland on the Bumper Cars ride.....
Nifty Program, Great Job! ...
Really a great program! Works like a charm.
One proposal: An exception list for some programs are running would be good (some needs the shake like Shake'n'save) - but especially S2U2 is a problem - because when device is locked with S2U2 - the shake still works - and opens the programs - with some indifferences with S2U2.
Keep up this real good work
Pierre
band27 said:
G-forces aren't significant unless you're at Canada's Wonderland on the Bumper Cars ride.....
Nifty Program, Great Job! ...
Click to expand...
Click to collapse
teorouge said:
Did anyone try this during car use? I mean, there is some g-force involved, in driving... steer, brake, accelerate, bumps...
Click to expand...
Click to collapse
wez89 said:
I havnt tried it during driving but im sure braking, steering and accelerating will have no effect although a big and i mean a big bump or bang may just shake the device abit
You need a quick, hard shake for it to register as a shake
Click to expand...
Click to collapse
It requires hard shake to detect an event so I don't think it gets an effect of bumps . Although you can increase threshold to make it even harder.
PierreDiamond said:
Really a great program! Works like a charm.
One proposal: An exception list for some programs are running would be good (some needs the shake like Shake'n'save) - but especially S2U2 is a problem - because when device is locked with S2U2 - the shake still works - and opens the programs - with some indifferences with S2U2.
Keep up this real good work
Pierre
Click to expand...
Click to collapse
Yes I have observed this issue. I am working on exceptions thing, so it could be overridden when S2U2 is in foreground. Will have to wait for some time..