Related
hi,
the new version is out, look here.
Original PoinUI files attached on this post.
Code:
New Features
* Smartphone support
* PDA's (without phone) support
* Voice mail count is now displayed under the missed call count for those with phone networks supporting this feature.
* Lock screen will fade back to Home screen to allow you to see all of the status information even when device is locked.
* Translation support - see the forums for more information.
* New customise option: can choose digital or analog clock.
* New customise option: Lock Device, Show Home, or Show Home Screen when device is switched on.
* New customise option: automatically switch bluetooth on only during phone calls and switch off at the end of the call (not supported on all devices). The idea behind this is that if you only use bluetooth during phonecalls for headset etc and don't need it on all the time, then this option could be useful to you. It will turn bluetooth on as soon as an incoming/outgoing call is detected, and turn it off when you hang up.
* New customise option: can choose to use Home's comm manager or system default if supported.
* New customise option: can choose to not show screenshots in Currently Running screen (if your device has issues showing the screenshots).
* New customise option: can choose to Show Home, Show Call Summary Screen, or Do Nothing when call is finished.
* New customise option: can choose to use Home's task bar or standard system task bar.
* The list of applications now merges the list of favorites so you can view the entire list together
* Call summary screen added to display who was called and how long call lasted for at end of call.
* Lock screen can now be used on smartphones - you press up then down on dpad.
* You now have an additional option to "Lock Device" on power on.
* Battery saving - now only uses marginally more battery power than normal - smartphone users should notice a big difference (of course this is dependent on how excessive you are with using it).
Changes
* Taskbar in all other standard apps is no longer changed except for the Start button area which still takes you to Home's Task Menu.
* Windows Media icon has been replaced with Favorites.
* Appointments summary shows only the next 7 days of appointments.
* Tasks summary no longer shows completed tasks.
* Force close now returns focus back to Home.
* Ringer volume and profile button on sound screen for non-phone devices are no longer displayed.
* Appointments now display all day events in bold and should not display events that have been completed for the day.
* "Today" and "Tomorrow" in appointments also now show the date after them
* Smartphones no longer have a Windows Mobile section as it's not relevant.
* Shortcut no longer includes "." at start which was causing issues for button mapping.
* Soft key on Today screen no longer overridden. (NOTE: you will need to reset it back to what it was manually if you have a previous version installed).
Bug Fixes
* Many bugs fixed!
* Memory leak issues fixed.
* Lock screen locks keys as well, and when orientation changed while locked the keys remain locked.
* Recurring appointments now displayed.
* Hardware buttons now working.
* Volume controls now working.
* Volume controls support stereo.
* Control panel applets have had a number of bug fixes. They still are only categorised correctly for English ROMS unless you use a translated terms file as described in the forums.
* Battery shouldn't show 255% any more but some devices for some reason do not report the correct % when asked and can take a while before they report it successfully.
* The speed that tasks load has been improved and should no longer cause freezes.
* Currently Running screen causing device to freeze has been fixed on most devices, but still is problematic with some devices in which case you need to switch off the screenshots option.
* Closing home sometimes caused it to freeze needing soft reset issue has been fixed.
Known Issues
* See the forums for more details.
wfg
Starbase64
And here both the cdl files, blue and black
http://rapidshare.com/files/89917296/home_1_02b_cdl.rar
Still not working with the LG ks20.
I guess it 'll never work,not untill it has some decent direct3d drivers.I assume kaiser users have the same issue with pointui?
nstamoul said:
Still not working with the LG ks20.
I guess it 'll never work,not untill it has some decent direct3d drivers.I assume kaiser users have the same issue with pointui?
Click to expand...
Click to collapse
Works absolutely flawlessly on my Tilt/Kaiser...
no way to change SMS application?
works perfectly on my Artemis
How can I customize the Favorites???
dacib said:
How can I customize the Favorites???
Click to expand...
Click to collapse
Add links to the \Windows\Start folder.
Ok am I missing something or is there still no way to reverse the slide up and down and side to side? Its backwards from every other finger sliding program I have used and it just makes it feel wrong.
Man I can't believe they still haven't made this an option.
Can I use this one for VGA? because I ever tried using the previous version but can not display well
just edit your Menu under Settings
i have folders in the \windows\start menu folders such as '\Office 2007' and '\Accessories'
how can i access them?? i hope favorites can also support folders in the future version.. i kind of like the way PoinUI is right now (optional top bar, optional homescreen).. because i only want PointUI to be an Application Launcher of some sort and not a complete overall UI..
also, can the scroll function be reversed? i mean an option to do so? because i use FtouchFLO and TouchFLO for general OS and application navigation and it's scroll/finger swipe function is when you swipe up, list scrolls down.. and a swipe down does the opposite direction (list goes up)
it is a bit disorienting to have a different/reversed swipe/finger scroll direction in PointUI other that what the whole OS has..
besides those requests.. i'm enjoying the launcher 100%
dont know what happened....phone froze during a phone call...uninstalling
screnshoot please
This is pretty good. Have decided to give it a go now that you aren't stuck with that hideous blue!
Just one question - how do you go straight into Contacts to make a phone call. I have been using pocketcm which is great, but now have to go looking for it as an application, instead of just hitting the soft button.
Or am I missing something?
still no way of changing which email account to use from the main page i see (defaults to outlook/exchange) even though i've not got that set up at the moment and have done with the windows live mail
that and the backward touch scrolling is making it hard to use this program which does look really good.
it just needs its own email/sms reader and contacts just like its got with the recent calls list.
Merciless said:
dont know what happened....phone froze during a phone call...uninstalling
Click to expand...
Click to collapse
Same here... I have a Cingular 8125. Other then that I like it, its fast and it does not use as much memory as the previous version.
dacib said:
Same here... I have a Cingular 8125. Other then that I like it, its fast and it does not use as much memory as the previous version.
Click to expand...
Click to collapse
also, the phone hung up the call and froze...not sure if i dont know what to do or what, but the call detail is hard to get to(want to end call or something)
A few bugs
Still have problems with CZ diacritics ěščřžýáíéúů
nstamoul said:
Still not working with the LG ks20.
I guess it 'll never work,not untill it has some decent direct3d drivers.I assume kaiser users have the same issue with pointui?
Click to expand...
Click to collapse
It is the KS20 directdraw drivers who are corrupt... not direct3d drivers !!
==================================================================================================
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
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.
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.
Credits:
Foremost, let us all acknowledge Koushik for his brilliant "Sensors" library upon which most if not all non-HTC apps that use the G-Sensor, Light-Sensor, and Navi-Sensor are built, simply ingenious. Moreover, I would like to recognize No2chem for the NeuLed2 library which is an equally exquisite peace of code that allows access to the Diamond/Pro Leds. Without those two guys, accessing these advance interfaces on the diamond/pro would be inapproachable at best.
Reason: HTC gave these phones lots of sensors, lets give them.."Sense".
......... EXTRA-Sense ...........
* Hopefully an innovaton, though mostly an integration of RANDOM but needful features...
Features:
1. Courtesy Profiles:
- Set Volume Profiles to activate on Face-Down & Face-UP events. Choose from: None, Silent, Normal, and Vibrate. You can also choose to suspend the Phone when its facing down.
2. Notifications-Sense:
- IF there is/are any outstanding notification(s), the device will vibrate whenever you move it - at customizable intervals: Missed Call(s), Voice Mail, and SMS.
3. Stylus-Sense:- When the Stylus is in/out: Will play sound + Blink the Back button's light.
- When the Stylus is out and the device is moved: Device will vibrate faintly + blink the Back button's light to REMIND you that the Stylus has not been placed back in. This goes on UNTIL the Stylus is placed where it should be.
* Uses "in.wav" & "out.wav" files in the \XSense\ Dir; you can use whatever wave files for this. OR, use the UI to select whichever wave files you want!
4. General Settings:
- Polling Interval: From 200 to 3000 Miliseconds. This determines the rate at which the G-Sensor is polled. Lower values give higher response times and fluid operation at the cost of battery life & CPU utilization.
- Flash Navi Lights: Will blink button lights to notify you of Profile changes and Stylus In/Out.
- Vibrate on Events: Will induce very subtle vibrations to notify you of Notifications and Profile changes.
- Suspend when UP-Side-Down: ???
- Light Navi Button When Suspended: Will do just that when the Light Sensor senses Dim or Dark conditions. This is an independent setting that turns ON the Navi button's light at suspend time, and OFF at Resume time (this is Event Driven, so no polling is involved). This feature really helps if, like me, you want to see where the damn thing is in the dark - before you launch it against the floor.
5. Installs to "\Program Files\XSense", and Creates 2 shortcuts:
"Start Menu\Programs\XSense" and "Startup\XSenseSvc".
Program Settings are saved to the Registry at "HKCU\Software\XSense\".
Use of System Resources:
1. Diskspace: 162 KB RAM footprint: 374-535 KB Battery: NOT observed.
2. CPU Usage: %0.29 Average. Spikes for 2 seconds to %2.7 - %8.5.
3. Battery Impact: Neligeable if at all!
* Indicated CPU usage occurs ONLY when there is an EVENT (posture changed, stylus in/out Sounds playing,
etc)
- Vibration: The way I like it is in waves of 200 miliseconds length! I generally hate vibrations, so if you want it at 201 ms. you're welcome to make your own program and exercise your personal taste.
- This prgram Registers Event Handlers for: "G-Sensor", "Incoming Call", "Phone Call in Progress", "Stylus in/out", and Power Manager events. DO NOT move it to Internal Storage, you have been warned.
Requirements:
.NET 3.5 + HTC device with GSensor & Light Sensor.
Compatibility:
Specifically designed for Diamond & Raphael, but will work fine on HD/Rhodium/Topaz/HD2 etc...
Bugs/Limitations:
Knock yourself out...
Release Notes:
- This is the LAST revision/release/app I make; programming too much work
- Download & Install the CAB
- Run the XSense from your Start Menu\Programs, customize to taste, and enjoy!
Change Log:
- Brand New UI: VERY "finger friendly" this should be especially useful if you have a WVGA Device
i.e. HD/Rhodium/Topaz/HD2 etc...
- Revised entire code for existing & potential bugs, and Performance
tweaked to death.
- Removed various functions (auto speakerphone, car-kit options, etc...). Use "Touch InCall Screen Tweak" for these,
its handles Phone/Speaker brilliantly!
- Shortcut added to Startup for automatic launch after reboot.
- Shortcut with a nice icon added to Start Menu (Credit to VetVito).
- General Tab:
- Navi Button will only light up if the device is in a dark place, i.e. You will
always see where your phone is (before you trash it against the wall).
- Stylus Tab:
- UI elements to select & set sounds for Stylus-in/out events.
Disclaimer:
This program is provided strictly on "as is" basis. It is intended only as a proof-of-concept. Although fully functional, it must NOT be considered for daily use. This software is very likely to compromise the integrity of your data as well as invariabley cause your device to malfunction in any way, shape, or form. Therefore, the developer shall be absolved of all responsibility towards testers and/or their computers & devices. While using this software you agree to be solely liable for all and any damages you do to yourself, your device, or any damn thing you possess and care for!
Download XSense v1.2 - Final
http://forum.xda-developers.com/attachment.php?attachmentid=265847&d=1263112521
This app sounds very interesting. Im installing it now & will report back with results. Thanks for the app.
thebigrhinoone said:
This app sounds very interesting. Im installing it now & will report back with results. Thanks for the app.
Click to expand...
Click to collapse
I appreciate that, Big Rhino... enjoy
shirreer,
Very Nice!
May I suggest if we could use a "Shake" motion to change the gesture profile?
What I want to do is...Slient mode when face down and shake for wake up.
Thanks!
Let´s give it a try.
And guys please don´t forget to vote for Rhodium!
mobilio said:
shirreer,
Very Nice!
May I suggest if we could use a "Shake" motion to change the gesture profile?
What I want to do is...Slient mode when face down and shake for wake up.
Click to expand...
Click to collapse
Interesting suggestion, mate; however, the battery won't take it :s I thought of it several times over and eventually settled for the overall performance. Cheer up tho, 2 newsworthy items: WM7 will have the functionality natively + there is an app that does exactly this - its in the HD2 section if you're game enough to try it
Cheers & Enjoy
orb3000 said:
Thanks!
Let´s give it a try.
And guys please don´t forget to vote for Rhodium!
Click to expand...
Click to collapse
A pleasure, do tell if you like or hate it
Every time I soft reset (backup app does this every night) it "loads" (top bar) even when I'd unloaded it. Would be nice if it remembered the setting I've selected
dik23 said:
Every time I soft reset (backup app does this every night) it "loads" (top bar) even when I'd unloaded it. Would be nice if it remembered the setting I've selected
Click to expand...
Click to collapse
Oh boy, you are lazier than even me, ain't that something?! Dude, delete the shortcut: \Windows\Startup\XSenseSvc
Cool little app - trying it out...
shirreer said:
Oh boy, you are lazier than even me, ain't that something?! Dude, delete the shortcut: \Windows\Startup\XSenseSvc
Click to expand...
Click to collapse
Thanks, had no idea that was there.
Seems a bit odd that I can start it manually and it doesn't say loaded in the top bar.
this app could be very useful to me...installing now, will report back soon
Nice little app..thx..
akademik_acheeba said:
this app could be very useful to me...installing now, will report back soon
Click to expand...
Click to collapse
Lot of meetings, eh? perhaps I know how you feel... enjoy
Cheerios
- This prgram Registers Event Handlers for: "G-Sensor", "Incoming Call", "Phone Call in Progress", "Stylus in/out", and Power Manager events. DO NOT move it to Internal Storage, you have been warned.
Click to expand...
Click to collapse
so we install this on our storage card??
Great work.
One thing I would like to remark:
The phone goes to vibration as I've set it when I turn it upside down.
However, when I turn it up again, it doesn't go back to normal unless I press one of the hard key buttons and "wake" it up.
Is this to save the battery life? If so I fully understand. I don't know if there is a solution where battery life is not affected and this can be solved.