Related
Just wondering if there is a registry hack that stops the screen from automatically rotating and displaying in portrait mode when you flip the screen round ?
i.e. it should stay in landscape mode no matter if the screen is facing in/out or otherwise.
You can do it manually by clicking on the screen rotate icon, or going into Settings > Screen > Orientation, so I figure there must be a reghack to put it permanently into Landscape ?
tia
Ok, i've found the key at least which shows what mode is currently in use:
This is Landscape (Right-handed) mode:
HKEY_LOCAL_MACHINE\System\GDI\Rotation
Angle 0x5A (90)
HideOrientationUI 0x0 (0)
LanscapeMode 0x1 (1)
The question is, how do I stop those being overwritten or change it so when it's in Portrait mode, it actually uses those settings ?
gaspx: I'm an odd fellow. I'd written you a long post about basically:
rotation is achieved at OS level, and driver level, so althought it's possible to be notified of the screen being rotated, intercepting it would require, AFAIK, some fairly substantial low level code or a reg key I'm not aware of.
But then I remembered my work on the Universal Voice Command/External Key issue in another thread. I've written a test program called VJElectrify, which contains a hack called ClamHack. And I just tried clamhack, and amongst its other side effects, yes, it does allow you to prevent the system forcing a rotation. So system stays in landscape if you open in laptop mode, or rotait into portrait mode. You then manually choose your rotations.
VJElectrify isn't finished yet, still a lot more research to do, but yes, it is possible to prevent it Keep an eye out for when VJElectrify is released.
Anyone else know another way to do this? I can't think of any relevant reg settings.
V
Heh heh, I knew it probably wouldn't be as simple as a reg hack.. cheers for the reply Vijay, i'll keep a watch on your website for the forthcoming VJElectrify..
gaspx said:
Ok, i've found the key at least which shows what mode is currently in use:
This is Landscape (Right-handed) mode:
HKEY_LOCAL_MACHINE\System\GDI\Rotation
Angle 0x5A (90)
HideOrientationUI 0x0 (0)
LanscapeMode 0x1 (1)
Click to expand...
Click to collapse
Thats just the keys where the current state is stored.
the key you need is HKLM\Services\ScreenRotate (you can change the ShowIcon value here to enable/disable the today icon)
Ive tried just renaming the ScreenRotate but that failed then i tried changing the dll name stored in the key, after all if it cant find the dll surlly it'll stop the rotations.
NOPE, i know the dll rename is working as the icon failed to appear, but the auto rotates continue to happen, it must be OS, it must be!!
.....the search continues
Ive tried just renaming the ScreenRotate but that failed then i tried changing the dll name stored in the key, after all if it cant find the dll surlly it'll stop the rotations.
Click to expand...
Click to collapse
I did that as well.. sorry, should've mentioned it in my original post, but I had the same idea as you! - the screenrotate.dll just seems to be tied to the icon in the systray. sigh.
Have to wait patiently for the VJClamhack to be released..
The clam hack has, by design, side effects - it disables part of the system OS, which conveniently disables screen rotation detection and some other stuff on the hinge. However, the bugger refuses to enable hardware keys with lid closed.
Because clamhack is quite a big sledgehammer for a nut, I'm a little worried about putting it out - however, I've never seen any negative sideeffects, only positive
V
Load DinarSoft MemMaid on your Universal.
Just as you can delete Startup Items, you can also delete Start Up Services. I believe I saw a service related to screen rotation in there.
I don't have my Universal for another week (getting replaced), but I do recall seeing that in there.
As always, perform a backup in case you can't "add" it back in.
I don't think that Rotation service helps, I tried it a bit earlier, since it seems to be an obvious target.
V
However, the bugger refuses to enable hardware keys with lid closed.
Click to expand...
Click to collapse
Thats OK, i don't need to use hardware keys when it's closed -- I figure this is part of a bigger problem you're looking at..
ust as you can delete Startup Items, you can also delete Start Up Services. I believe I saw a service related to screen rotation in there.
Click to expand...
Click to collapse
Yeah, I think that was the one Carnivor and myself had found.. we just prevented the service starting manually by bodging the registry key, but all it does is stop the little screen rotate icon from appearing.. thanks though
Has anyone figured this out yet?
Thanks
Hello!
I need to write software that disallows any screen rotation on my Wizard.
How can I do it? I didn’t found any registry settings for this. The best way
that I see is hooking ChangeDisplaySettingsEx. But unfortunately, SetWindowsHookEx
doesn’t works on WM 5.0, at least it said on some topics. Please, give me any solution for this problem or example code to hook some API function.
wm5: [HKLM\System\GDI\Rotation]
Angle=dword:0
00000000 portrait
0000005a righthanded landscape
0000010e lefthanded landscape
then RegistryNotifyCallback will do
tanks a lot
I will try this way.
But I afraid it will be notified after screen rotation starting.
Adjusting this registry value in regedit tool did't help.
So I suppose this value is changing after rotation is done.
You can delete the start up service of ScreanRotate.
Go to HKLM/Services/ScreanRotate and delete it.
I think before you doing this,you can export it to a reg file
It's not bad idea.
but delete this key leading to system restart for apply
I just try to stop this service.
Not luck : (
This key not present in the registry storage.
I am under WM 5.0
Maybe you talk about some early system.
Hi hoblano, I'm experiencing the same problem, did you find a solution ?
thanks,
Scalposcarno
use task manager 2.7 and stop service...if you know it is service...
same way to stop kbd lights...btw,
I tried, but the result is the same as the one obtained by manually deleting the Screen Rotate voice within the services voices in the registry: avoiding the load of the service providing the icon on the task bar enabling the user to rotate the sceen one or more times by tapping on it.
I still don't understand ... at this point the most probable thing is that the service that rotate the OS screen when rotating by hand the HW screen, is invisible with respect to registry voices and to applications like Task Manager 2.7 or MemMaid. Apart from criticizing the constructor choice (why didn't they thought that someone should have been more comfortable using only one view mode ? e.g. landscape one), is there a way to obtain a list of core services and to avoid one of those to be loaded ? or, otherway, is there a way to intercept the event thrown when manually rotating the screen of the terminal ?
By the way, I'll have to do it with Java ...
thanks all
BubbleLevel v1.02
My first attempt at utilizing the Touch Diamond's accelerometer. And it's free!
The sensor is a Kionix KXSD9.
Donate a cup of coffee!
Thanks for donating on my birthday: Damien (€2,00)
and another thank you for Nuno (€1,00)
Features:
- Measure the slope of a surface using the 'bubble level' concept
- Display the slope angle in degrees
- Real time display and calibration of sensor data
- Can be used upside down too (go measure yer ceiling matey!)
Changelog:
v1.02
- Added verbose calibration screen
- Real time sensor data monitoring
- Implemented two-direction calibration method (for absolute sensor bias compensation as suggested by Kionix)
- Calibration data is stored to memory (used for BubbleLevel only!)
v1.01
- Added icon and placed shortcut in Programs (instead of Start Menu)
- Fixed bug of bubble flying away >42 lightyears when device is tilted at 90 degrees, causing a warp core breach (thanks akito)
v1.00
- Initial release
You developers never cease to amaze me. Great work! XDA-Dev is wonderful!
Sounds nice ! So this software will let us be able to calibrate the Touch Diamonds Accelerometer?
I have downloaded the cab and installed it but how to use it?
I'm going to try this!! Thanks for posting it and letting us try :-D
Da9L said:
Sounds nice ! So this software will let us be able to calibrate the Touch Diamonds Accelerometer?
I have downloaded the cab and installed it but how to use it?
Click to expand...
Click to collapse
The shortcut's in your Start Menu. Click the Windows flag to get to it; I will find a nice icon and add a decent Programs shortcut later on
j0bro said:
The shortcut's in your Start Menu. Click the Windows flag to get to it; I will find a nice icon and add a decent Programs shortcut later on
Click to expand...
Click to collapse
Okay got it working now.. But when i calibrate and exit the program it resets the settings back to before it was calibrated.. So it doesnt save the calibration..
Brilliant!
Now if the Diamond had a flat back cover, I could actually use this for a bit of DIY
Bug found ;-)
Whether calibrated or not, when I hold my phone completely vertical making it show about 87 degrees of more the program crashes... actually my whole phone crashes cause I can't exit the program anymore and need to push the reset button
can anyone post some screens? my diamond is up and away for repair
edit: sorry my browser took some while to load the pic on the first post so I didn´t see it.
j0bro said:
BubbleLevel v1.0
My first attempt at utilizing the Touch Diamond's accelerometer. And it's free!
Click to expand...
Click to collapse
That is soo cool. Thanks Bro - great work.
.
akito said:
Bug found ;-)
Whether calibrated or not, when I hold my phone completely vertical making it show about 87 degrees of more the program crashes... actually my whole phone crashes cause I can't exit the program anymore and need to push the reset button
Click to expand...
Click to collapse
Thanks akito, I could indeed reproduce that behaviour quite easily... I guess I need some exception handling when doing vector dot product calculations
Will fix this asap.
Edit: Fixed in v1.01, check start post!
Version 1.01
Where can we download version 1.01 of Bubblelevel? Because the above problem still exists in the version which can be downloaded on the first page.
castor.troy said:
Where can we download version 1.01 of Bubblelevel? Because the above problem still exists in the version which can be downloaded on the first page.
Click to expand...
Click to collapse
Please check the About box in the program for the version number. The cause for the bug mentioned above is removed in v1.01, but you might have come across another situation. Please let me know if you find out when it happens exactly, thanks!
wasn't this program supposed to calibrate the accelerometer?
No. the calibration is only valid in the app.
chribruu said:
No. the calibration is only valid in the app.
Click to expand...
Click to collapse
Could it maybe be tweaked somehow so that it can calibrate globally, so that it will effect other software too ? Would be perfect.. !
Thanks for this software. Very Cool
Hi, could you please give me some advice how to programm with the g-sensor..
i have an idea for a small programm that uses the sensor...
i already found the "HTCSensorSDK" but when i want to load the project files within C# Express 2008 i became an error that the project files could not opend...
j0bro said:
BubbleLevel v1.01
My first attempt at utilizing the Touch Diamond's accelerometer. And it's free!
Features:
- Measure the slope of a surface using the 'bubble level' concept
- Display the slope angle in degrees
- Measure the relative angle between surfaces using the calibration function
- Can be used upside down too (go measure yer ceiling matey!)
Changelog:
v1.0.1
- Added icon and placed shortcut in Programs (instead of Start Menu)
- Fixed bug of bubble flying away >42 lightyears when device is tilted at 90 degrees, causing a warp core breach (thanks akito)
v1.0
- Initial release
Click to expand...
Click to collapse
Will this work with Omnia (i900) too?
it should also be possible to check if something is completely vertical.
when i hold my phone in the vertical position and tilt it a little bit the numbers change.
could you add indicators for vertical and horizontal bubblelevel?
could you also lower the refresh rate a little bit. the numers keep jumping making reading them almost impossible.
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.