Re: 'Fixed in Fremantle' and Diablo community SSU
 

I know this is a feature request, but is there hope of A2DP for Diablo or must I wait longer for my BT headphones to be useful again?
I installed the latest SSU, so far I notices modest has changed with display for rotation, which works... kind of. It rotates but hildon doesnt like the size and using it is difficult.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Any chance to add DSP speed tuning? This allows the DSP to be locked to a max frequency of 133 to allow the ARM to stay at 400 when audio is active. This is nice when listening to MP3s and browsing the web.

See here for details. The kernel is under the section PPTP client and kernel with MPPE support. Then look at N800/810 - IT2008 version 5.2008.43-7 (latest Diablo).

The changes define a tunable, /sys/power/op_dsp, 0 is 400/133, 1 is 330/220.

thanks,
Frank

Re: 'Fixed in Fremantle' and Diablo community SSU
 

I vote for including the dsp patch

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Thirding the DSP patch. Excellent find, Frank!

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Weird; I powered up my second N800, I installed the enabler and then tried to install the unlocked SSU via HAM. It said that all sorts of dependencies were missing. They looked like the contents of the SSU!

So I gained root, did apt-get update and apt-get install osso-software-version-rx34-unlocked so I could send the errors, but everything worked fine... :confused:

Re: 'Fixed in Fremantle' and Diablo community SSU
 

yeah i had to do the same thing to get the community SSU to install on my n810.

not sure whats up with that.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Oh I also had to manually run flash-and-reboot to get the SSU kernel...

Should "about product" report anything different?

Re: 'Fixed in Fremantle' and Diablo community SSU
 

No objections to making it tunable, as long as it defaults to the previous behaviour (ie, no surprises to users who don't know/care about it). Anyone feel like isolating that specific patch?

Re: 'Fixed in Fremantle' and Diablo community SSU
 

I don't suppose you saved the HAM log?

Yeah, that is handled by HAM and won't trigger via an apt-get upgrade.

Just the version number (should start with "5.2010"). /etc/osso_software_version and the output of /usr/bin/osso-product-info should be similarly updated.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

What's the current state of the art on this? I don't own such a headset so never paid much attention to the subject and obviously I can't test anything. The only relevant bug seems to be 667.

I'm not sure I understand what you mean, could you provide a screenshot with some explanation perhaps?

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Hey lma, sorry for not PM'ing you, but I just registered and can't PM yet. Can I help testing the SSU? I just yesterday did a clean flash of OS2008 on my n810, so I'm good to go :)

Great job btw!

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Just tested the latest SSU from a pretty fresh reflash (about a month ago) on a N810.

All seem to work fine, ls -Q works, PDF Viewers now zooms with 25% steps, screen rotation works.

I think I've seen the telepathy-gabble bug once using a friend's WiFi connection. I'll test it next time I'm there.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

The source patch is included in fanoush kernel package: http://fanoush.wz.cz/maemo/kernel-di...2maemo1.tar.gz
It is the diff against board-n800-dvfs.c

About the behaviour, it defaults to the 330/220 (in fact, I failed to change the setting at first because "echo 0>/sys..." it not the same as "echo 0 > /sys..." :P)
I've running it now for more than a day and have to say that I'm happy with it, it plays fine mp3/aac and doesn't skips under load.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Just tried this... and HomeTools is now reporting Internal storage twice...

Re: 'Fixed in Fremantle' and Diablo community SSU
 

That's probably due to the df fix (is "internal storage" / or /media/mmc2?) . Maybe we should get rid of the /dev/root check/mangling as well.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Anyway I can just turn that off or exclude that from the list? Otherwise, I'm pretty happy with all so far.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Ima,

I also just registered so not able to send PM:s yet :/ I could help with the testing with my N810!

I really appreciate your job guys!

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Not without breaking dependencies and missing the other busybox fixes :-(

I just pushed an updated version that makes the df fix conditional on having filesystem arguments on the command line (eg "df /"). This should make it bug-compatible with the official version in the general case, but let me know if it's still causing problems.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Where is that? Is it overwritten after each install?

Hmm, mine didn't update...

Re: 'Fixed in Fremantle' and Diablo community SSU
 

My hometools now not showing double root filesystem, thanks.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

AFAIK it's only a string in RAM unless you save it manually (Tools -> Log -> Save as).

Hm, the -unlocked variants didn't contain /etc/osso_software_version or the postinst script. Fixed, and thanks for spotting it.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

How much additional disk space is the community SSU taking up for you guys? I haven't cloned my OS yet (holding out for Mer), so I'm down to about 20 MB free.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

I'm not sure why, but there is some binary bloat simply by rebuilding the packages in the Diablo SDK :-(

For example, the default 5.2008.43-7 busybox (1.6.1.legal-1osso16) is:

-rwxr-xr-x 1 root root 228792 Sep 18 2008 /bin/busybox

while building the exact same version unmodified in scratchbox results in a file 314808 bytes long (the current community SSU one is 331264).

It's probably too late to complain to Nokia about this now, but if anyone has any ideas I'm all ears.

That should be more than enough though.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

The GPL version 2 states that the offer for sources, scripts to control compilation and the toolchain has to be available for 3 years and everything must match the binary provided with the device.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Prelink might have helped size in cases..

Re: 'Fixed in Fremantle' and Diablo community SSU
 

That was my first thought too but the busybox binary in the .deb is identical to the one in the jffs2 image. But since you're reading this, do you feel like poking the right people about it? It may be something as simple as different gcc defaults on the buildbot vs scratchbox. Somehow I doubt Nokia are maintaining two separate toolchains and keeping the good one secret :-)

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Prelink is done as a post-image-generation process - it goes in and runs it on the file system after putting in all the packages, effectively modifying the binaries.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Exactly, so if prelink was the cause the /bin/busybox binary in busybox_3%3a1.6.1.legal-1osso16_armel.deb would be larger than the one in the rootfs part of the FIASCO image.

I suppose there could also be something hinky in my Diablo SDK installation, it would be nice if someone else could verify the size discrepancy.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Strictly speaking, busybox in SDK doesn't have to be the same actual deb package as was used to build the image. It might be same source package but not same binary package.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

There's no SDK binary package, the deb I'm comparing against came from catalogue.tableteer.nokia.com (obtained with "apt-get --download-only --reinstall install busybox" on a freshly reflashed vanilla 5.2008.43-7 device) and the binary it contains is identical to the one on the image. It's only when rebuilding the same source package that I get a larger binary.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

I think of two possible reasons:
- Different compiling optimization (O1? O2?)
- Stripping

Re: 'Fixed in Fremantle' and Diablo community SSU
 

I can't follow your discussion but I thought I'd put in a cheer for the work you're doing.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

In the recently released update I beleive it has broken MSN (I have rtcomm). I use jabber, gtalk and aim. AIM never connects and msn doesnt even load if anything else is in use. The second you enable other accounts it breaks msn.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

My device has just notified me of an update for ...
OS2008 Community SSU, version 1:52010.14-2

Just finished installing ....

I can't seem to see what the difference is from the 14-1 version .

Will it be possible to put a small note in this thread (or highlight the changes from the previous version) so we know what to test for?


thanks ... :)

so far .... all seems to work ok.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Both binaries are stripped of course. It would be nice to know whether the official binaries are built with the same toolchain, but other than that the only way I can think of that compilation flags could differ between builds of the same source package is if the two build systems have different gcc.specs.

But, you know what's funny, I thought to check if this still applies to Fremantle and sure enough there's also a significant size discrepancy there, but in the opposite direction!

Original PR1.1.1 /bin/busybox from .deb (1.10.2.legal-1osso26+0m5): 355592 bytes.
Local rebuild of the same source package: 253196 bytes.

This is on a '5.0-final' SDK that has been apt-get upgraded to PR1.2, ie it's scratchbox 1.0.16 under the hood (the current SDK ships 1.0.14 for some reason). My Diablo SDK is a separate installation, using scratchbox 1.0.11.

This may be worthy of a bug report even, as it could suggest an easy way to shave a few MiBs off the Fremantle rootfs.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

The only difference is fixing the -unlocked meta-packages (mentioned in post #261).

Re: 'Fixed in Fremantle' and Diablo community SSU
 

I assume you mean rtcomm beta? Can anyone confirm that these protocols are still supposed to work on Diablo? ISTR some reports that they were broken in Fremantle, but I never had any interest in proprietory IM protocols personally so never paid much attention.

Do you know which package(s) on your system implement support for MSN/AIM? Could you also PM me the output of "dpkg -l"? Some syslog output (see here) might be helpful too, if you can.

The only change in the telepathy stack (a small workaround in loudmouth to stop telepathy-gabble spinning) shouldn't affect non-XMPP protocols in any way.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

I enabled the Red Pill mode on my tablet and found some updates available and was wondering if it would be safe or useful to update these packages?

The packages available for update are these:

gstreamer0.10-plugins-bad-ivorbis ver. 0.10.5-9
libmad0 ver. 0.15.1b-2.1maemo1
libpurple0 ver. 2.6.6-0nix1
libxcomposite1 ver. 0.4.0-3
libxml2 ver. 2.6.27.dfsg-1.maemo1
poppler-utils ver. 0.10.5-1maemo1
python-gdata ver. 1.2.3-0maemo2
telepathy-haze ver. 0.2.1-2
x11-common ver. 7.4-5maemo3

I can update this packages for testing with the SSU.

Thanks.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

None of these packages come from the SSU repository, and a few conflict with the versions depended on by osso-software-version and would cause it to be uninstalled thus breaking future updates. You might get better results with osso-software-version-rxXX-unlocked, but if it breaks you get to keep both pieces ;-)

Re: 'Fixed in Fremantle' and Diablo community SSU
 

rtcomm beta has worked perfectly fine with me in the past. Msn now no longer works... I'll post my dpkg... errr, pm it.
Edit: MSN only dies when aim tries to connect. Otherwise Msn works fine...