Touchscreen problems in RR at resume from Hibernate

**Bimmerstyle** · 12-22-2007, 11:59 PM

First of all, i've searched the forums about this but did'nt found an answer that matched my problem exactly.

When I resume from hibernation to RR everything works just fine. My touchscreen responds to all commands --until-- I leave the current screen that I'm in.

After I changed to another screen there is no responce anymore when I touch the screen. When I simply click with a mousebutton (anywhere) everything works fine again.

When I do a complete restart everything also works fine. It's only after hibernation.

Any Ideas? It's driving me up the wall by now!

**guino** · 12-24-2007, 10:55 AM

sounds like a driver or controller software issue -- I'd try to update it (or try a different version) and/or try different settings on it.. also, try clicking on different things within the same screen after resuming (without changing to different screens) to see if it also stops responding..

**Bimmerstyle** · 12-24-2007, 09:14 PM

Hi Guino, the problem is kinda solved.

First of all I have to say I had this problem also on my previous system. This was an Epia M10000 with 512Mb Ram 60Gb laptop drive and al lilliput 7" touchscreen with touchkit drivers and software. I never made a fuzz about it because when I pressed and holded the touchscreen for one second everything went back to normal and after a few times hibernating the problem was completely gone. But when I did a complete reboot and went in hibernation again after that it came back so I had to press and hold the touchscreen again to make it function again.

Now on my new system (see sig.) it didn't respond to the press and hold. I installed every different touchkit driver I could find but the problem remained. But when installing these drivers at some point I noticed that the "right click" function is disabled after installation and you have to enable it yourself. So I did enable this with little hope but hey...

And guess what, it works! So now the first time I came out of hibernation it didn't respond anymore after switching from the main menu screen to the music screen but when I pressed the touchscreen for about a second it came back alive. Now after a few times going in and out of hibernation the problem is gone just like it was with my Epia.

So now one question remaines: What's causing this? It doesn't bother me anymore since I have found a workaround but I still find it strange. Am I the only one having this problem? Is it Roadrunner? Is it my touchscreen? It can't be my system because I had the exact same problem on two different systems with a bunch of different touchkit drivers.

When I get a chance I'm going to try it on my friends system. He has a similar setup as my previous one (the epia) also with a lilliput and touchkit drivers and he is also using RR. He doesn't use hibernation so I'm curious what will happen if I make his PC go in hibernate. Will it have the problem or am I the only unlucky one that has it. Hmmm..?

**guino** · 12-25-2007, 08:41 AM

It's most likely the touchscreen software or the touchscreen itself.. perhaps during the hibernation your touchscreen is being signaled as "touched" and then it shuts off, so the software thinks it is still being pressed when resuming and then you need to signal it on/off again so it knows nothing is being pressed... even more likely to happen if you have some sort of motorized screen.. but all of this is speculation, there's no way to know without knowing a lot more details of your touchscreen/drivers.. chances are you MIGHT be able to fix it by disabling most of your advanced settings for the touchscreen for instance... if your touchscreen is plugged through a hub or something like that, it could also be part of the reason... honestly, when you deal with USB and Hibernation together, there's no telling what will happen...

**Bimmerstyle** · 12-25-2007, 12:11 PM

if your touchscreen is plugged through a hub or something like that, it could also be part of the reason...

Yeah, it's connected trough a hub. I was also thinking this could be a possible reason. Since I now have a few extra USB ports on my PC I'm gonna pull some extra USB wires to the front when I have some spare time. One to connect my touchscreen and I'm also planning to put in a SpaceNavigator so one wire will be for that.

honestly, when you deal with USB and Hibernation together, there's no telling what will happen...

I noticed that too in the past year or so I'm using hibernate on my car PC...

But for now it seems to work so I'm pretty happy. My previous system is sold to that same friend. He is gonna put it in his van but it will not have a lilliput screen on it. All settings remained the same on it so if it hasn't got the same problem after installing it, it will probably be the touchscreen of my lilliput that's causing it.

Anyway, thanks for your help. Alltough changing the drivers didn't help much it was while doing this I found a sollution that works, so thanks.

And also a big thank you for RR! It simply is the best frondend out here.

Merry christmas!

**jac1502** · 01-13-2009, 01:15 PM

Anymore news on this I am having the same issue on my second system? My touchscreen works in windows just not RR (I know this is an old thread)

**Ces///M3** · 06-12-2009, 05:10 PM

Im also having this issue w/ an atom 1.6 non dual core and a xenarc 701. I am using minlogon without ewf/horm and the touchscreen usb is plugged straight to the pc...

**Ces///M3** · 06-29-2009, 04:59 AM

nobody has come up with a fix for this yet? I recently updated my xenarc 701 to the latest driver as well as stopped hibernating, instead power off every time and still experience this problem from time to time

**guino** · 06-29-2009, 09:21 AM

Originally Posted by Ces///M3

nobody has come up with a fix for this yet? I recently updated my xenarc 701 to the latest driver as well as stopped hibernating, instead power off every time and still experience this problem from time to time

If you use a hub to connect the touchscreen to the computer, TRY (just to test) plugging your touchscreen's USB cable DIRECTLY to the computer and/or in a different USB port. Chances are that when resuming it takes some initializing of the controller and the hub or other usb devices may be interfering with it. I have a xenarc, plugged direct to the carpc -- never experienced anything like this.

**Ces///M3** · 06-29-2009, 10:13 AM

Hey Guino,
I do have the touchscreen connected directly to the usb port. I have since scrapped all resuming/hibernation as well, now it doesn't do it as often (with hibernate it happened every resume!) but it still does it none the less. It's the last glitch in my system before its 'perfect' and I was really trying to square it away. Any help is greatly appreciated.

P.S. - I am going to try and utilize a program called focus-genie as a workaround to this issue, hopefully that fixes it for me so I can scrap having the keyboard in the car