Diablo performance nightmare
 

I've been sitting on my hands waiting for quite a while but now I'm starting to reach the end of my tether.

My N800 running Diablo is plagued by the infamous button-press-gets-stuck-repeating problem. It's so bad that I get hit by it at least a dozen times a day.

When I applied the latest Diablo patch the problem went away completely for two or three days. Now matter how hard I tried I couldn't get it to happen. But then the problem suddenly came back with a vengeance. I can't say for certain that it's worse than it was before, but it sometimes seems that way. It certainly seems worse now when using the built-in pdf reader and mplayer.

I'm just wondering how many people have this problem. I'm booting off the internal SD slot, but I can't think of any other modifications to the basic system.

I'm wondering if I should bother starting fresh with a new install or even go back to OS2007.

Re: Diablo performance nightmare
 

Are these hardware buttons or software ones?

Re: Diablo performance nightmare
 

These are the hardware buttons and the problem is in all versions of Diablo. You can use xset770 command to make it happen less, but still a nuisance.

This bug will probably never been solved, I believe. It wasn't there in 2007 OS, and is probably a tiny hack to get rid of the key bounce, but I may have live with it.

If anybody has a clue how to solve it, every hint is welcome. Here we have genius hackers who provide the webkit engine, but I just need a proper avoidance of keybounce .... :eek:

Re: Diablo performance nightmare
 

Strange, I've never seen this problem.

Re: Diablo performance nightmare
 

I think that this is https://bugs.maemo.org/show_bug.cgi?id=2723

For me it happens very rarely, but if I give my tablet to someone else it happens almost instantly. So there something about how you use the d-pad.

Re: Diablo performance nightmare
 

Maybe it is something you learn to evade subconsciously?

Its ironic, my Nokia phone running S60 has this too. When using too fast the keys, then the sound is produced throughout the previous sound. Result is a crackled sound is heard, or the sound is hard --at least much harder than normal. Ie. tick tick TI-TICK tick tick.

In the case of the tablet it also hangs the keypad/machine, or produces multiple times the same key.

Re: Diablo performance nightmare
 

Thanks for the xset770 suggestion. I'll give it a try.

It seems for me that the bug really only affects a handful of applications and unfortunately, those few are the ones I seem to use the most. I can't really say what behavior seems to trigger it, as there doesn't seem to be much of a pattern. Pushing a button repeatedly doesn't seem to be required. Before fbreader was altered to avoid this bug, one isolated page-down tap was enough to set it off.

It's a shame really, that despite my enthusiasm for the tablet overall, this bug is enough to turn me off considering another maemo product. Sure the next OS probably won't have this particular problem, but is it going to have some other equivalent problem that just gets swept under the rug?

SIGH

Re: Diablo performance nightmare
 

I understand your concern, but please, at least vote for this bug then :)

Re: Diablo performance nightmare
 

I never have this problem with diablo, but when I was using Penguinbait's KDE, it was a real nuisance :eek:

I thought it was a software problem w/KDE, but I guess it's more widespread.

I'll vote for the bug, then :)

Re: Diablo performance nightmare
 

I run the following code for some slight improvement:

for i in 111 116 ;
do
xset770 -r $i 0
done

~ $

Re: Diablo performance nightmare
 

I was going to say I've never seen this, which is technically true, but then I thought about it and realized I never use the d-pad. I've used it sparingly when reading an e-book, but even then I never saw this problem.