Re: 'Fixed in Fremantle' and Diablo community SSU
 

No I don't. But I can tell you the rotate I had installed (sliderotate) had the option to set power and home as hardware rotate buttons. and of course the slide out keyboard made it rotate back to landscape. Maybe sliderotate was in addition to rotate?

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Right, so there's another package involved. As far as I can tell it's this, but I would advise against installing it as it forces installation of specific kernel & xserver packages and thus breaks SSU.

The package contains no licence information, but the garage page says GPL. Maybe someone could repackage it, or even better write a C version?

Re: 'Fixed in Fremantle' and Diablo community SSU
 

On Fremantle there is extra package which provides subtitle support to gstreamer. Can it be compiled/backported to Diablo ?

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Not as far as I can tell, since the gstreamer support is only part of it and the rest depends on mafw.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

The SSU installed smoothly without any problems.

There are two bugs I'd love to see fixed.

1. The crazy scrolling that happens occasionally where the D-Pad gets stuck in the down mode when you are browsing in either MicroB or Tear and so you scroll all the way down the page.
I don't know if this was "Fixed in Fremantle" but it's the most annoying bug on the n800 for me.

2. The repeated text entry when using the on-screen keyboard where letters randomly get repeated as you are entering them. I think this one was "Fixed in Fremantle"

Sorry I'm crap at searching bugzilla so I can't give bug numbers but I'm sure they are there (probably repeatedly).

Also many thanks to lma for taking this on and anyone else who helped. :)

Re: 'Fixed in Fremantle' and Diablo community SSU
 

one or both come from the interrupt system used, iirc.

basically, the release of the button gets lost in the system somehow and so it thinks the key is pressed until its pressed again so that a proper release signal gets registered. Heck, i have seen tear windows killed that way thanks to the long press feature on the back key (kills focused window) when the cpu is maxed out.

either that or its related to xomap somehow having a short keyboard signal queue or something so signals gets removed before they are acted on or whatever.

would not surprise me if the "fix" in fremantle involved the move to xorg...

Re: 'Fixed in Fremantle' and Diablo community SSU
 

I think it is a bug in hildon gtk or in the hildon keyboard itself, since I haven't seen any repeated keys when using the xterm's virtual keyboard hack. Also, notice that the stylus keyboard produces keyboard events only for the TAB, DEL, SHIFT and ENTER keys, normal keys do not generate events, so I doubt the bug is X related.
Anyway, it would be really interesting to get this bug fixed, so if anybody could shed any light about how this was fixed in fremantle...

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Sounds like bugs 1680, 2723 and/or 2751 (in fact they may all be the same underlying bug). No patches in any of those though :-(

Isn't that (bugs 2391 / 2394) supposed to be fixed? I'm not experiencing it on either of mine.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

ran into it today when entering a command in xterm, and seen it ever so often elsewhere, so no. That is, unless it actually was fixed in chinook, but then had a regression in diablo (imo, diablo was a messed up release).

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Would including Lock Code Dialog - Owner Tag appeal to you, lma? The only problem is that it hacks libhildon directly, due to the instance of the code lock dialog being used in a closed source program. That said, I don't think any other Diablo program uses that widget and I don't think new apps are a problem... strcmp on the title? :o