Re: 'Fixed in Fremantle' and Diablo community SSU
 

Update: after a lot of experimentation with various more exotic flags (that was a waste of a perfectly good Sunday afternoon!) it seems the only difference in the case of busybox is -mthumb. I'll treat this as a packaging bug in and set it explicitly in this case.

However it's becoming apparent that the Nokia build machine applies different compiler flags on different packages (outside of what is defined in the packages themselves).

For example, xorg-server needs DEB_BUILD_OPTIONS=vfp to even compile, and an SDK osso-pdf-viewer build of the original unmodified package (without -mthumb) produces a binary that is significantly smaller than the Nokia package: 938972 vs 1162620 bytes. I suspect this case may be some vfp optimisation, but really don't feel like spending any more time tracking down this sort of thing - these discrepancies have come to light after touching just 8 source packages, and there's a lot more to go. Also, size differences in executables are relatively harmless, but there may be more tricky issues with libraries and such.

Stskeeps: any chance you can "liberate" the internal per-package build flags so we can apply them properly to the packaging metadata?

Re: 'Fixed in Fremantle' and Diablo community SSU
 

I also want to try the Diablo community SSU. What should I do?

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Change your forum profile settings so that people can send you PMs and/or emails.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

That's not an option for hamunguia yet. He/she needs to make one more post before his/her private messaging automatically activates.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Ah, I thought that was related to account age and it certainly looked old enough. You learn something new every day :-)

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Hey Lma, I figure the problems I've been having are my own since noone else is reporting desktop reseting to defaults. So I am considering doing a reinstall on my external. If I re-add the community SSU repository after the reinstall will I be able to get caught up again?
Sorry I haven't sent any reports yet, everytime I try I just keep running into problems, or having to do something else with my time. But I am ready for a fresh install anyway.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Sure, that's the point :-)

Re: 'Fixed in Fremantle' and Diablo community SSU
 

This fixed things for me. Thanks. Still plugging away.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Reflashed latest Diablo, added community SSU. Manually refreshed and installed. All fine so far.

Frank

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Ima,

Do you have everything you need for the DSP underclock patch? It doesn't appear to be in the current version. I understand you may just need time but if there's anything that you need help with, please let me know and I'll try.

thanks,
Frank

Re: 'Fixed in Fremantle' and Diablo community SSU
 

I think so, but I haven't even tried to apply it yet.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

ok i did a complete reinstall, got updated and got up. So far everything is well, no desktop crashes, and my batery life is even better. Camera wasn't working in my old install but it now works too. The only thing is I don't have a hardware key for rotate anymore. Is there a way I can set that? Also is there anything else I can help with?

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Is there any estimated date for a public release?

Re: 'Fixed in Fremantle' and Diablo community SSU
 

I too installed SSU successfully. Application manager first gave installation error with some missing packets, but after manual install with apt-get I could finish the SSU installation.

Nice work!

Re: 'Fixed in Fremantle' and Diablo community SSU
 

not sure if this is the right place to ask, but i was wondering if someone involved in this was capable of creating a patch for the existing modest code for os2008 that would add a menu entry that would allow the user to initiate a image download if a mail was html based.

modest have the capability, thanks to a option hiding inside gconf, but its not accessible from the gui, and one may not always want to have it enabled.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Hi!

I have also experienced desktop resetting to default. Is there any logs in N8x0 for debugging?

This occasionally happens after heavy browsing with microb...

Re: 'Fixed in Fremantle' and Diablo community SSU
 

I'm glad I'm not the only one. It crashed again, but I think it's only when I am using a lot of resources.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

I've gotten desktop crashes with stock Maemo, only clock and OMWeather active on the desktop.

So far I haven't had any desktop crashes with the community SSU but the frequency of crashes I had before the update lead me to believe that this is inconclusive evidence one way or another.

Frank

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Good question. I'd rather sooner than later, but the reports of hildon-desktop crashes worry me a bit. On the other hand we haven't bricked any devices yet, so it probably isn't too unsafe to unleash. What do people think?

What desktop/statusbar/navigation applets were running at the time?

Even with syslog running I don't think you would see anything in the logs. The best way to debug this would be to produce a core dump and stack trace. If anyone's up for it, see http://maemo.org/development/tools/diablo/ for the relevant tools and docs.

Failing that, has anyone experienced a hildon-desktop crash with no third-party applets enabled? FWIW both of mine are stable with load applet, advanced backlight and statusbarclock (only the statusbar applet, the desktop applet that comes with it crashes reliably).

Re: 'Fixed in Fremantle' and Diablo community SSU
 

I don't know :-/ Do you have a pointer at relevant docs/patches?

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

Re: 'Fixed in Fremantle' and Diablo community SSU
 

I get it all the time when entering text using the on-screen keyboard and stylus (I don't use the thumb board).
Thankfully I don't normally enter a lot of text - just urls and CLI commands but if was normally typing in a lot I think I'd have flung the n800 out the window long ago :D.

I could have sworn that D-Pad scrolling problem was Fixed-in-Fremantle. Oh well :(.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

I vote for including this :)

Re: 'Fixed in Fremantle' and Diablo community SSU
 

I get it all the time too

Re: 'Fixed in Fremantle' and Diablo community SSU
 

I used to get it too, but since I changed the screen I didn't see it anymore, so I'm not sure it's software only.
Now, I'm not using my n800 very much since I changed the screen, so that's may be another reason I don't see the issue.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Bug 2394 is about the stylus keyboard (see the description - the summary was incorrectly changed at some point by a triager but there's little point reopening now).

According to that bug report the issue was fixed in chinook, but if some people are still having it there could be a hardware bug specific to some N800s. Maybe the reason I'm not experiencing it is that mine had the touchscreen replaced (due to bug 1069). In any case, without a patch or even reproducibility there's not much I can do about it, sorry :-(

Re: 'Fixed in Fremantle' and Diablo community SSU
 

That's actually a good reason for it to be included (since it obviously can't go to extras).

However I'm not crazy about configuring via a fragile text file (especially in /etc, thus requiring root permissions). Does anyone feel like updating the patch to use something like a GConf string? Then someone could even write a control panel applet for configuring it.

Also, is there anything that can be done to make text changes apply without requiring a reboot? Killing systemui sounds like one way to do it, but does it break anything else?

Re: 'Fixed in Fremantle' and Diablo community SSU
 

I've always thought of GConf as the place to store one-liner strings...
A control panel applet that has a "helper" program whitelisted in sudoers would probably work.

Well, it appears that the file is read each time HildonCodeDialog is instantiated by a program. I wouldn't think systemui would keep a static instance of the HildonCodeDialog that it instantiates. That said, a watch could be kept.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Nah, too many unnecessary moving parts :-) If it's got to be in the filesystem let's stick it somewhere under /home/user (or even better /home/user/.osso so it gets backed up/restored automatically without additional configuration).

Hm, is there a GIOCondition that would notify for file creation? Maybe inotify could work instead, but either way adding an application-specific main loop callback inside a widget library seems dirty to me.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

*nod*

Good point. Truth be told, I don't think there really needs to be a watch. I haven't checked it, but I think systemui keeps instantiating a new instance of HildonCodeDialog each time. And who's gonna modify the text file while the tablet is locked?

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Wow. First time I've ever quoted myself. This feels weird. :p

Anyway, I was at least hoping to get a response on this.

Thanks.