Shattered Screen? Turn Your Broken Device into a Complete Media Center!

A cracked screen usually means you’ll have to spend a hefty … more

Gmail 5.0: Material Design and Multiple Account Support

Google started to materialize many of its applications right after announcing the … more

Some of Our Favorite Features in Android 5.0 Lollipop

Android 5.0 Lollipop is the latest major revision to Google’s mobile operating … more

Sony SmartEyeglass SDK Developer Preview Released

A little over a month ago in Tokyo, Japan, Sony unveiled its new SmartEyeglasstechnology. … more
Thread Deleted

touch.dll development/hacking ( cab file of the rebuild touch driver added )

OP rogro82

16th November 2008, 06:20 PM   |  #21  
rogro82's Avatar
OP Senior Recognized Developer
Thanks Meter: 440
 
862 posts
Join Date:Joined: May 2008
Donate to Me
More
Did any of you tried to set the values to 109 and see how it reacted? Setting it to 109 will give it a higher priority..

As stated before this is not a fix... for me its just a solution for the slow rendering when touching the screen at the moment. The real fix will consist of a lot of cleaning up of the garbage code in touch.dll like removing debug, cube code etc.

I am working on it but dont expect a quick fix on that, because basically the complete dll needs to be rebuild from asm and then the stripping can begin. So for people that dont have any issues the reg hack is great, but any problems that arise from it all comes down to the fact that the touch.dll is one big pile of $#%.
Last edited by rogro82; 16th November 2008 at 06:23 PM.
16th November 2008, 06:27 PM   |  #22  
Senior Member
Flag London
Thanks Meter: 2
 
117 posts
Join Date:Joined: Feb 2008
More
Quote:
Originally Posted by rogro82

Did any of you tried to set the values to 109 and see how it reacted? Setting it to 109 will give it a higher priority..

Also noticed that scrolling is much better when Priority is set to 255, but the screen becomes unresponsive to touch for a few seconds in iGO8.3 when I browse the map or when the map is shown. Setting the priority to 109 or even 200 fixes the iGO problem, but I found that scrolling in All Programs becomes as slow as it was before.

As the screen only becomes unresponsive when it starts to build up the map, I will leave my settings at 255 as i am not touching the screen while driving anyway.
16th November 2008, 06:41 PM   |  #23  
m.schmidler's Avatar
Senior Member
Thanks Meter: 1
 
302 posts
Join Date:Joined: Apr 2008
More
Just tested, seems to work better than before. Also tested with value=200, a bit worse than with 255.

I underlined "seems" because I think udK cooked some improvements into scrolling. At least in programs-folder when you scroll slowly it is soft as hell. If you scroll a bit and put off your finger it gradually gets slower, really nice done.

Don´t know if this is also an improvement in the touch.dll ?

to rogro82: big thanks for starting the thread, just another "how-can-we-improve-our-polaris-so-it-becomes-an-awesome-device"-thread, like the P3D-thread.

regards,
Martin
16th November 2008, 07:51 PM   |  #24  
Junior Member
Thanks Meter: 0
 
17 posts
Join Date:Joined: May 2008
I don't have any problems with tomtom7.

I'm not using udk rom...
16th November 2008, 08:24 PM   |  #25  
Junior Member
Thanks Meter: 0
 
16 posts
Join Date:Joined: Feb 2008
Smile
230 and 230 works very well!
Scrolling is very fast and
TomTom works also good.
I use the M-Amine 2.0 german
final Rom.
16th November 2008, 08:40 PM   |  #26  
rogro82's Avatar
OP Senior Recognized Developer
Thanks Meter: 440
 
862 posts
Join Date:Joined: May 2008
Donate to Me
More
Some information about priority levels:

0 through 96
Reserved for real-time above drivers.

97 through 152
Used by the default Windows Embedded CE–based device drivers.

153 through 247
Reserved for real-time below drivers.

248 through 255
Mapped to non-real-time priorities.
16th November 2008, 08:59 PM   |  #27  
m.schmidler's Avatar
Senior Member
Thanks Meter: 1
 
302 posts
Join Date:Joined: Apr 2008
More
Quote:
Originally Posted by rogro82

Some information about priority levels:

0 through 96
Reserved for real-time above drivers.

97 through 152
Used by the default Windows Embedded CE–based device drivers.

153 through 247
Reserved for real-time below drivers.

248 through 255
Mapped to non-real-time priorities.

thx for the info, but its rather expert info, since you don´t advice us which ones best for which scenario
16th November 2008, 10:54 PM   |  #28  
Senior Member
Flag Munich
Thanks Meter: 2
 
377 posts
Join Date:Joined: Oct 2006
More
Hey guys great find! It really works a lot faster in scrolling. But i also can confirm the bug in igo!!
If this development goes on we don't need any 2d drivers!!
17th November 2008, 06:31 AM   |  #29  
c_shekhar's Avatar
Recognized Developer
Thanks Meter: 34
 
1,941 posts
Join Date:Joined: Jun 2005
@rogro82
The tip is overwhelmingly superb. I have tested with values 256 and no issues at all. It makes the scrolling a real pleasure. Thanks a lot bro! keep up the good share...
17th November 2008, 08:16 AM   |  #30  
NeoS's Avatar
Senior Moderator / Recognized Developer - There is no N00b...
Flag Somewhere in NL
Thanks Meter: 843
 
3,326 posts
Join Date:Joined: Jan 2008
Donate to Me
Rog, why is it that this only works on Polaris? Because the HD doesn't seem to have that issue when touching the screen. I imagine the Polaris is a hastily created device by HTC. The HD seems much more finetuned.

Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes