Help - Search - Members - Calendar
Full Version: Unit Stops Responding (input)
OESF Forums > Distros, Development, and Model Specific Forums > Model Specific Forums > 6000 - Tosa
daeos
After adding some packages and updating a lib or two , it would seem that one of these updates/packages for pdaXrom has created a new issue for me to tackle. My SL-6000L will boot fine, load X fine but after a few uses of some tools or even if i stop touching it... The unit refuses to respond to touch screen/keypad input. I have tried to test if its an issue with the hardware... and it works fine after a reboot by removing the battery and external power plug. Even if i run a program like top and leave it on the desktop, it will continue to run and the clock will still keep track of time, but touchscreen response works ONLY to move the mouse, will not click on anything and buttons do not do anything on the unit... what might have caused this?


I hope this is the right location for this question
the_oak
I don't run pdaXrom (yet), so I don't have any idea on how to fix your problem, but maybe posting in the pdaXrom area of Distro Support would turn up some suggestions.

I'm waiting for version 2 of pdaXrom for my 6000, as I've read that the current version is a little buggy on the 6000.
daeos
QUOTE(the_oak @ Jul 15 2008, 07:31 PM) *
I don't run pdaXrom (yet), so I don't have any idea on how to fix your problem, but maybe posting in the pdaXrom area of Distro Support would turn up some suggestions.

I'm waiting for version 2 of pdaXrom for my 6000, as I've read that the current version is a little buggy on the 6000.



I believe I had solved my issue... I was able to replicate the issue when pango wasn't properly working and I would try to change the time on my tosa. It would lock up after the time tried to change.
pelrun
I had that problem with pdaXrom - if I changed the time significantly, keyboard and tap detection would stop working until I either reset the Z or sshed in and restarted X.

I seem to recall pdaxrom having a kludge in the restore script because if too much time passed between suspend and resume you'd hit this. Something to do with a buggy timeout in the select() call?
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2014 Invision Power Services, Inc.