TouchFlo Exceptions list? - UPDATED 21/01/08

[Guest SMYKUL]

This is the one thing which I'm still not happy with. I love the ability to scroll but it messes with most of my games and any apps which involve drawing on the screen, including note-taking. I noticed that the xda-dev touchflo project has an exception list and was just wondering if there was one for the OEM version hidden somewhere?

Thanks.

I have since discovered that this is a fault on most touchscreen HTC devices which have hardware acceleration for graphics. The problem is only encountered on HTC devices and has been present for some time. In actual fact my old HP2210 Pocket pc can currently out-perform my touch dual. This is because HTC has failed to provide adequate drivers. Needless to say this is a HUGE oversight by HTC, and it affects anything which draws to the screen or gathers touchscreen input.

A website has been created to increase awareness and to hopefully force HTC to take action, it can be found at:

www.htcclassaction.org

Edited January 21, 2008 by SMYKUL

[Guest Paul (MVP)]

There's a registry entry for this somewhere, I believe under HKLM\Software\HTC\BioTouch but I don't have my dual to hand to check. Anyone?

P

[Guest SMYKUL]

You're right, I don't know how I missed it. It is located in: HKLM\Software\HTC\Biotouch\Disable4SpecificApp

The only problem I have now is that it works by ClassName and I can't for the life of me find a task manager which lists them on PPC. D'oh :(. Any ideas?

[Guest SMYKUL]

Figured out how to add to the exception list, only problem is that it doesn't disable scrolling, just the touch cube gesture! *smacks forehead". Anyways, I've added a guide below in case someone else needs this. Any more ideas anyone? :D

#1. Find the programs ClassName;

To do this you will need Fdc task manager, apparently the creators of this app know everything about PPCPE except how to make an icon that looks nice :(.

Anyways, put a link to the task manager in your start menu and start up the app you want to add to the exceptions list.

Now minimise it, this may be a bit tricky. I managed it by pressing an app button (Messaging, PIE, camera etc.) and then the start menu button.

Start Fdc Task Manager and go to the process list, then hold the stylus on the program you want to exclude and click details. Now click Windows and look for the one you want (In most cases the second entry) the text in parenthesis ("") is the window title and the text directly after that is the ClassName needed.

#2. Add to the exceptions list

Now create a new key in HKLM\Software\HTC\Biotouch\Disable4SpecificApp

Lets say you called it "AGame"

So you now have the path: HKLM\Software\HTC\Biotouch\Disable4SpecificApp\AGame

Add a string value in this key called "ClassName" with the value of the ClassName found using the method above.

The cube will now not be activated by the down->up gesture whilst the window with that ClassName is focused.

[Guest Paul (MVP)]

DOH!

:(

P

[Guest SMYKUL]

I'm afraid that I have come across something rather disturbing. After my exploits detailed above I continued to do some digging around and found some promising registry values under HKLM\Software\HTC\TouchScroll.

I copied the key called "HTCAlbumClass", renaming it to the class name of one of the programs I was looking to exclude. I then changed all of the values within to 0 (The most important being H_enable and V_enable, for horizontal and vertical scrolling). This did not fix the problem. Also please note that after all changes are made a soft-reset is required, I forgot to mention this in earlier posts.

Anyway, finding this quite strange I proceeded to change the values of "EnableCube" and "EnableScroll" in HKLM\Software\OEM\TFLOSettings to 0. This, in theory, should have disabled all the components of the touchflo system. Unfortunately it doesn't, full screen apps and programs/games which rely on touch screen input still slow to a crawl as soon as pressure is applied.

In short, it looks as though the problem is either somewhere else or TouchFlo continually catches all of the input from the touch screen, processes it, and then passes it on regardless of its settings. This is very bad news for touch-intensive applications.

[Guest SMYKUL]

*bump* - See first post