![]() |
2011-08-04
, 07:35
|
Banned |
Posts: 32 |
Thanked: 11 times |
Joined on Aug 2011
|
#2
|
![]() |
2011-08-04
, 07:53
|
Posts: 147 |
Thanked: 228 times |
Joined on Feb 2010
@ Toronto, Canada
|
#3
|
I conclude that its because of undervolting the CPU.
In my experience and experimentation, Running multiple apps at the same time causes more CPU load.
Well an idiot knows that too, but, if undervolted, CPU is starved, so working on full load reducees the performance of the frequency causing, in your case, a non responsive touchscreen.
Try cranking up the voltage, see if it works.
![]() |
2011-08-04
, 11:52
|
Posts: 291 |
Thanked: 435 times |
Joined on Apr 2011
@ RO
|
#4
|
The Following User Says Thank You to SHARP66 For This Useful Post: | ||
![]() |
2011-08-05
, 07:01
|
Posts: 842 |
Thanked: 1,197 times |
Joined on May 2010
|
#5
|
![]() |
2011-08-07
, 02:18
|
Posts: 147 |
Thanked: 228 times |
Joined on Feb 2010
@ Toronto, Canada
|
#6
|
I'd chalk it up to a FBReader glitch. I don't have that problem, but in the same mode, I'll have it scroll *up* if I'm about 1 finger's width above the bottom of the screen, in both portrait and landscape modes. Hitting the bottom edge of the screen works, but that spot just does the wrong thing.
Who knows why.
Here's where it gets interesting. First, finger tapping anywhere else on the screen works on the first try. Second, once the problem occurs, repeated finger taps in that spot do not register. However tapping anywhere else on the screen works, and tapping again in the problem area also registers. Third, stylus tapping the problem area works every time.
So I tested the screen with the sketch app. I could draw continuous lines, interrupted lines, dots, circles both with my finger and the stylus anywhere on the screen, and every single input registered including the problem area.
Now if other apps had a problem, or the stylus did not register, I may think the resistive layer is developing a problem. But it's limited to fbreader, and only developed fairly recently.
Any ideas? My N900 is running kernel-power47 overclocked to 750Mhz, the latest CSSU, and many apps from extras-devel. Under these circumstances, I would understand some crashes, but the N900 is rock solid with great performance and battery life, except for the wonky finger tap input in fbreader...