Database Info

customize Biotouch sensitivity, scroll duration?

say i go to Start > Programs and then i finger-flick to scroll down... the scrolling speed and scrolling duration are just out of whack. i flick and then wait like 5 seconds till it stops and even one normal flick is enough to go from first to the last icon on the page. if i want to scroll smaller distance, i intuitively do a slower flick but then biotouch ignores that gesture and next thing i know is i'm randomly opening programs.
i used to have htc-titan/ppc6800 with installed version of biotouch, and finger-flicking scrolled at the same speed but for much shorter time, like 1 to 2 seconds, which was much more desireable. the sensitivity also was more fine-tuned that even slower flicks were interpreted as scrolling gestures... the whole biotouch experience was much more snapper and was actually usable. now with touch pro i find myself preferring to use scrollbars to even scroll small distances...
i've tried quite a few customization tools including Advanced Config and none of them allowed me to fine-tune the scrolling duration and finger-flick speed sensitivity. does anybody know where these settings, and hopefully other settings, are located for biotouch? i just want to fine-tune them to be more "usable"...
Thanks!

half a day passed and the thread is already on the 5th page... dang things here evolve quickly!
so, anybody knows how to or where to tweak biotouch config?

Is there an application that can easily change volume and screen backlight by a tap?

I am wondering if there exists an application which can easily change volume and screen backlight by a simple tap?
Well this is what im after: at night I always set my backlight to 10% and the volume very low. During daytime i set the volume at 80% and the backlight to 40%. My wish is to be able to switch between these setups fast, instead of having to access the settings etc. I guess it is some sort of profiling application, but the backlight option is a must.
Would also be nice if it had an automatic time setting.
Please share your knowledge if you know the answer to this.
Thank you.
MOD EDIT: tnyynt: Thread renamed! Please use relevant information in thread title!

very easy. the magic word is: profile
have a look here: http://www.pocketmax.net/phoneAlarm.html normaly the fr of v2.31 should coming out this weekend ...

THX bro!
I'll definately give it a go!

Quick Set Backlight & sound for HTC HD2
I built one myself for my HD2. Its called Quick Set.
No guarantee it works on other HTC's.
On the HD2, pressing the leftmost button for 4 secs brings up a screen where you can select 0-25-50-75-100% sound levels and 10%-automatic-100% backlight levels.
If you want to keep a possible Long-Send.lnk already present in \Windows, please save it before and restore it after executing Quick_Set.CAB
In that case Quick Set must be launched via the start menu.
See attachments.
Have fun
Bert

Quick Set Backlight and Volume for HTC HD2 Version 1.1
Quick Set for HTC HD2 Version 1.1
Copy Quick_Set.CAB on the storage card and execute it.
It needs Microsoft .NET Compact Framework 3.5 Redistributable, possibly you must download an install it before.
After installation, pressing the leftmost button for 4 secs brings up a screen where you can select between 2 sound- and 3 backlight levels by touching c.q. the appropriate speaker and hd2 pictures.
This can be done easily, e.g. while driving and using the HD2 as navigator.
After selection, the application closes and the original screen is restored.
The first sound level is 0 (muted) and selected by touching the muted speaker picture left.
The second is determined by the setting of the top slider and selected by touching the right speaker picture
The first backlight level is dim and determined by the setting of the dark bottom slider.
It is selected by touching the dark HD2 picture left.
The second level is auto and determined by HD2's light sensor; selected by the middle HD2 picture.
The third level is bright and determined by the setting of the white middle slider;
selected by the white HD2 picture right.
While driving it is not recommended to operate the sliders.
If you want to keep a possible Long-Send.lnk already present in \Windows, please save it before and restore it after installation.
In that case Quick Set must be launched via the start menu.
Have fun
OpaPiloot

wow. thanx mate.
Will try & review it!
edit:
Just tried it and the brightness setting works flawlesly. The sound works too, but it doesnt update the sound icon in the taskbar tho :-(
If you are still developing on this, you could add 2 more buttons to it. Night & Day mode. These2 modes could be configurable...
Example: Night mode, brightness level 0 sound level 0.
Day mode, brightness level 100 sound level 100.
Cheers. Great application mate! Keep up the good work!

Thanks for the compliment.
Quick Set was developed for a number of reasons.
I was dissatisfied with the implementation of some HD2 settings.
In particular, backlight and volume; the latter also because I used VolDpad to remap the volume buttons to Up/Down so that I had less trouble using MS Reader.
Setting backlight and volume when using Tomtom navigator while driving
compromises safety.
As a hobby, I wanted to gain experience with Smart Device program development tools.
I never thougt about the speaker icon.
It only shows "muted" if both the ringer- and system volume settings are set to zero via the regular controls.
Hence, if it shows "not muted", you are not sure what this exactly means.
If you want to be sure, you have to access the controls.
My conclusion is, that quick access to the controls is preferred, and that is what Quick Set is about.
Night & Day mode does not seem practical, because in general the actual requirements for sound and brightness depend on the environment and these are often not correlating with the time of day.
E.g. in my case the ringer volume is never muted, while the system volume is mostly muted if I don't use Tomtom Navigator; brightness is set to minimum if I'm in bed, otherwise it's set to Auto or maximum if I am outdors or showing pictures.
Also then quick access to the controls is preferred.
Adding more controls is not consistent with my design goals.
I omitted the sliders in my first design.
I only added them because a friend of mine with somewhat detoriated eyesight had trouble with the minimum brightness while Auto was too bright for him; moreover it enabled me to gain more experience.
For the latter reason I may do something about the speaker icon.
Have fun,
Bert

just tried it. the screen settings work but not the sound. using tmob hd2. it would be great if it works though.

Updated [Jan-10]: [App] [G-Sensor] [Brand New] The XSense v1.2 Final

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 "as is". 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 1.2 - Final:
http://forum.xda-developers.com/attachment.php?attachmentid=265847&d=1263112521

This initiative sounds great But I would love one more feature. The ability to lock and unlock the device by using G-sensor. In particular, a gesture consisting of tilting the device donwards (with the screen facing the ground) and then upwards again (the screen facing the sky)

Look promising, but ... Leo dont have a stylus

Caramel said:
Look promising, but ... Leo dont have a stylus
Click to expand...
Click to collapse
I'm glad you noticed!!!
I'm just too lazy to make this LEO-specific, and this way I don't have to make 2 programs (one for LEO and one for everything else)....
Cheers

jgal said:
This initiative sounds great But I would love one more feature. The ability to lock and unlock the device by using G-sensor. In particular, a gesture consisting of tilting the device donwards (with the screen facing the ground) and then upwards again (the screen facing the sky)
Click to expand...
Click to collapse
Max Manila does this. Well, it locks when you aim the top of the phone at the floor.

Doesn't seem to work well with S2U2. For example, if your HD2 is set to lock with S2U2, then u put if face down, phone is not put in silent mode until u press a button to light up the screen when the screen is face down. So the first call to come in will still ring. But subsequent calls won't because when the first call comes in, the screen lights up and phone is set to silent.
The reverse is also true. If I revert to face up from a silent-ed face down position, and I do not press any button to light up the screen, it remains in silent mode until an action that lights up the screen.
Anyway to work around this? Or is it sorely the problem of S2U2?

kenkiller said:
Doesn't seem to work well with S2U2. For example, if your HD2 is set to lock with S2U2, then u put if face down, phone is not put in silent mode until u press a button to light up the screen when the screen is face down. So the first call to come in will still ring. But subsequent calls won't because when the first call comes in, the screen lights up and phone is set to silent.
The reverse is also true. If I revert to face up from a silent-ed face down position, and I do not press any button to light up the screen, it remains in silent mode until an action that lights up the screen.
Anyway to work around this? Or is it sorely the problem of S2U2?
Click to expand...
Click to collapse
This is not due to interference wth S2U2, it is in fact a programmed behaviour - I made it this way. The reason for this was conserving power; the device wakes up to incomming calls on a priority basis -think bus mastering- and the only way around it is to give the G-Sensor polling a higher priority, which means continuous polling + disallow the device to suspend power (the same effect as Shake2Wake). This costs you lots of battery juice, and according to Microsoft, a non-snapdragon device won't last the day in this operation mode!
Nonetheless, suggestions are welcomed...
Cheers

shirreer said:
This is not due to interference wth S2U2, it is in fact a programmed behaviour - I made it this way. The reason for this was conserving power; the device wakes up to incomming calls on a priority basis -think bus mastering- and the only way around it is to give the G-Sensor polling a higher priority, which means continuous polling + disallow the device to suspend power (the same effect as Shake2Wake). This costs you lots of battery juice, and according to Microsoft, a non-snapdragon device won't last the day in this operation mode!
Nonetheless, suggestions are welcomed...
Cheers
Click to expand...
Click to collapse
Hmmm...so the first call that comes in when phone is face down will not be silenced, and the first call that comes in when phone is face up after being moved from a face down orientation will always be silent?
The first scenario is still ok, can still silence it with a key press. But the 2nd scenario makes it possible to miss a call even when phone is face up. That does sound like it defeats the purpose of the app.
I'm not sure of the technical side of solving this, but missing every first call after flipping face up just sounds strange.

Finally, the closest thing to what i've been looking for. I have a HTC Fuze. With this app, I can only get the center LED (around the D-pad) to be on solid only in the dark, which is a nice feature, but i'd like to have all the LEDs at the bottom of the device (Home, Back, Send and End) to be on in dim or dark conditions, WHILE the phone is in use or suspended.
Can it be added, or how would I go about setting it up myself?
Thanks
~Des

(MOD) make touch more responsive

Dear guys and gals,
Found a key for touch prediction that when edited showed a marked improvement in keyboard responsiveness and small item manipulation ie classic desktop, file explorer, etc.
The key is: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\TouchPrediction
Edit key for latency from 8 to 2.
Edit sample time from 8 to 2
Restart
See attached for a edited registry key to inject. Tested on two surfaces with no ill effects.
edit: to answer a few questions: this increases performance on all touch aspects of the device

The most likely ill effect would be a decrease in battery life as the system must poll the touchscreen more often... just be aware. Otherwise, cool find.

Keyboard does seem faster... Does this also affect swiping? it seems like I can swipe in any way and get the full length of the page / app in one swipe?

Haven't noted in marked increase in battery consumption but I will monitor.

Could this improve the home key button, when my surface is on standby it takes about 6 taps to get the surface to wake up.

possibly, I have not tested the mod for that per say,
Dane Reynolds said:
Could this improve the home key button, when my surface is on standby it takes about 6 taps to get the surface to wake up.
Click to expand...
Click to collapse

I also have not noticed an increase in battery usage on my asus vivo tab. Not a surface, but rt.

What would decreasing the values to 1 due? I am assuming the lower the value, the better. Or did it not test well on Surface?

Originally I choose 2 to test the battery draw. However, now that I haven't seen any significant increase in battery usage the drop to 1 can be done.
Dadstar said:
What would decreasing the values to 1 due? I am assuming the lower the value, the better. Or did it not test well on Surface?
Click to expand...
Click to collapse

Is it that easy for all the values? In other words, can all of the registry values be set to 1 to improve performance? Or are all the values a certain number for a reason? Cuz if latency of 1 works better than the original 8, idk why Microsoft would put it at 8 in the first place. Sorry for all the questions. This stuff is interesting to me!

First off all any values are "safe values". Some screens might be of worse quality then others (different manufacturers of parts). Having that value setup to happy medium means all screens act the same. You lower the value you demand that screen reads the inputs faster and more often. Might not be a good idea on some devices.
Not only talking about surface. Remember win8 (especially pro) will go on many different devices.
Also if you set sampling and refresh to low it might start having ghost touches from minimum input that would normally not be visible (oversensitive).
Best to practice and find perfect for you and your device.

ruscik said:
First off all any values are "safe values". Some screens might be of worse quality then others (different manufacturers of parts). Having that value setup to happy medium means all screens act the same. You lower the value you demand that screen reads the inputs faster and more often. Might not be a good idea on some devices.
Not only talking about surface. Remember win8 (especially pro) will go on many different devices.
Also if you set sampling and refresh to low it might start having ghost touches from minimum input that would normally not be visible (oversensitive).
Best to practice and find perfect for you and your device.
Click to expand...
Click to collapse
How about the other regs that don't really have a highest/lowest rate? For example, Disable Hotmail is defaulted at 2. What would changing that to 1 do?

Dadstar said:
How about the other regs that don't really have a highest/lowest rate? For example, Disable Hotmail is defaulted at 2. What would changing that to 1 do?
Click to expand...
Click to collapse
No there is no general rule where lower value is better. Some of the values displayed are "face values" where 2 is 2 like refresh 2 times a second. Some times 2 and 1 have a meaning off or on (like your hotmail). Remember PC reads numbers. Even more sometimes numbers, text or mix you see like 8 or 4 are actually representations of some kind of code for example hex or binary.
If you do not know what the number represents then changing it is a guess and nothing more. Just have a backup copy as fiddling in registry with drivers can have funny side effects. I did make my hd7 think i am touching it everywhere all the time so it hang seconds after boot

Are we sure this does anything at all? In order to test if the differences were psychological, I set the number to a ridiculously high value and it didn't seem to behave any differently.

Yup I found noticeable differences in fine touch control including in the registry,window control, etc.
Wupideedoo said:
Are we sure this does anything at all? In order to test if the differences were psychological, I set the number to a ridiculously high value and it didn't seem to behave any differently.
Click to expand...
Click to collapse

Thanks a lot!

Is 2 a good value in the case of the surface PRO 1 ?

"touch prediction" did prediction, not pooling!
"Latency" = how much milisecond to look ahead
"SampleTime" = the period in milisecond to average your finger's motion
The effect is thus:
Larger "latency" make the pointer overshoot, smaller "latency" make the pointer lag behind (1 - 100 milisecond depending on your system performance).
There's no penalty on your tablet's battery or digitizer's life for turning TouchPrediction off, and you don't need to restart to see the effect. (try finger drawing in MS Paint to see effect)
If your Surface missed touch, then try to cool the back of your tablet. It might be thermal throttling.

[Q] Is the threshold for registering a touch event adjustable?

I'm using an Adonit Jot style stylus on a Android phone (ZTE V5 Max on Android 4.4.4, but I experience similar problems with other devices), which generates less signal on the capacitive touch screen than a finger. The phone's software appears to be configured with only hand touch in mind, and drawing with the stylus results in broken lines a lot.
On the pointer location debug display the minimum pressure I can get for a touch point to register is 0.09, and with this stylus I get 0.10~0.11 most of the time, so the head room is really low. With a finger the pressure level is usually above 0.15. This makes me wonder if I can tweak the threshold for a signal to be registered as touch to make inking with the stylus more stable.
I'm aware of some Build.prop configs suggested here and there. However after playing with several versions and reading some of the documentation I believe those values only change the touch behavior after a touch point has been registered. The actual threshold for a signal to be recognized as touch is not changed, and my problem remains.
I've also came across this thread which appears to be very relevant, unfortunately the mentioned file system paths are not found on my 4.4 ROM.
Is there anything I can play with to change such a threshold? (I have root access.) Or is it hard-coded in device-specific drivers?