maemo.org - Talk - 'Fixed in Fremantle' and Diablo community SSU

maemo.org - Talk (https://talk.maemo.org/index.php)

- OS2008 / Maemo 4 / Chinook - Diablo (https://talk.maemo.org/forumdisplay.php?f=29)

- - 'Fixed in Fremantle' and Diablo community SSU (https://talk.maemo.org/showthread.php?t=30648)

Re: 'Fixed in Fremantle' and Diablo community SSU

Installed easily and successully. Looking forward for new patches to be included into this upgrade!

Re: 'Fixed in Fremantle' and Diablo community SSU

Maybe I'm missing it but where is the change log for what is included in this first round? I thought it would be on the wiki page but can not seem to find it (a change log that calls out the individual changes with bug report #'s).

Edit: I think you see it when you are about to install in the App Manager but I was looking for a list online.

Re: 'Fixed in Fremantle' and Diablo community SSU

Upgraded with apt-get upgrade ('cause Application manager doesn't show any updates). Thanks for your work, well done!

Re: 'Fixed in Fremantle' and Diablo community SSU

Does the Community SSU restart metalayer-crawler? Battery life has gotten poor all of a sudden again, almost the same as when I let metalayer-crawler run.

Re: 'Fixed in Fremantle' and Diablo community SSU

Quote:

Originally Posted by gerbick (Post 647372)

Does the Community SSU restart metalayer-crawler?

Well, it restarts the whole device :-) I guess what you mean is that you had disabled it somehow and after updating it starts again?

If so, how did you disable it? If by any chance you had simply removed the package then reinstalling the osso-software-version metapackage would have that effect. Do you have the symlink to its init script in /etc/rc2.d?

Re: 'Fixed in Fremantle' and Diablo community SSU

Quote:

Originally Posted by gerbick (Post 647372)

Does the Community SSU restart metalayer-crawler? Battery life has gotten poor all of a sudden again, almost the same as when I let metalayer-crawler run.

I too noticed a hit in battery life, but metalayer crawler is still disabled for me.

Re: 'Fixed in Fremantle' and Diablo community SSU

Quote:

Originally Posted by lma (Post 647589)

Code:

update-rc.d metalayer-crawler remove

I'm noticing a slight battery drain, faster than before but same level as when metalayer was running rampant. I've only charged up and ran that above code earlier this morning, so I can't give any metrics compared to yesterday.

But I'll update you in a bit.

Re: 'Fixed in Fremantle' and Diablo community SSU

I haven't noticed unusual battery drain on either of mine, but these reports worry me. Does top show anything out of the ordinary?

Re: 'Fixed in Fremantle' and Diablo community SSU

Top doesn't show anything alarming or odd. Only thing that's new is Advanced Power, but even that was before the recent update, but after your first (unsigned) update last week or so.

I'll test through the day.

Re: 'Fixed in Fremantle' and Diablo community SSU

This is really unscientific... but let the battery drop below 93% via Advanced Power. Then reboot via the terminal. Your new level will be under 60%. This is after like 18 minutes of use from a fresh battery.

I've duplicated this twice since this morning. But the normal battery icon reports nearly full still. Seems like something broke in the battery sampling routine. But power seems to be about the same...

I'll still keep testing today though.

Re: 'Fixed in Fremantle' and Diablo community SSU

I wasn't able to get consistent readings of the battery charge level even before the community SSU update. I bought a brand new original Nokia battery and after every reboot the battery-meter shows something different than before the reboot. Sometimes the charge level is higher, sometimes lower than before. As a side note, I use Advanced Power all the time, cause I like to run the device at 400MHz.

Re: 'Fixed in Fremantle' and Diablo community SSU

Quote:

Originally Posted by derhorst (Post 647999)

Ah, I never knew that. Thanks!

Re: 'Fixed in Fremantle' and Diablo community SSU

I've been using the community update for more than a week and I haven't noticed any battery related differences.

Frank

Re: 'Fixed in Fremantle' and Diablo community SSU

Quote:

Originally Posted by lma (Post 646000)

Copying from http://wiki.maemo.org/Seamless_Softw...tware-version:

You'll need to run apt-get with root privileges btw.

Since you no longer have osso-software-version installed it is quite likely that something else you have installed conflicted with it and the above may fail. In that case you may have better luck with apt-get install osso-software-version-rxXX-unlocked, but pay extra attention to what apt proposes to do before accepting it.

I ran this and it asked me to install few packages. I went through without any problems. Then I ran opened the repository URL again with MicroB and after that opened Application manager. It asked me if I want to install Comminity SSU enabler (don't remember exact message..) and I answered yes. Still, I don't see any new updates. I even disabled all my other repos except Nokia System Software Updates which I cannot disable.
I have Mer installed. Does it affect the process somehow? What I should do next?

Re: 'Fixed in Fremantle' and Diablo community SSU

a thought popped to mind, can a microb versioon with better javascript performance be provided?

Re: 'Fixed in Fremantle' and Diablo community SSU

Quote:

Originally Posted by Mixu (Post 648112)

Still, I don't see any new updates.

Even after refreshing? If so could you save the application manager log (Tools -> Log -> Save as) and post it here?

Re: 'Fixed in Fremantle' and Diablo community SSU

Ima, don't worry about the battery. Went the entire day, some asleep, some not... and it was fine all day. It's the battery reading that's off.

Re: 'Fixed in Fremantle' and Diablo community SSU

Quote:

Originally Posted by lma (Post 649045)

Even after refreshing? If so could you save the application manager log (Tools -> Log -> Save as) and post it here?

This is what I get after I re-enabled few repos back. Community SSU (testing) is of course also enabled.

Code:

hildon-application-manager 2.1.19.1

apt-worker:Ignoring version from wrong domain: libdb4.2 4.2.52+dfsg-2

apt-get worker: /var/lib/apt/lists/repository.maemo.org_extras_dists_diablo_free_binary-armel_Packages

apt-worker:Ignoring version from wrong domain: libdb4.2 4.2.52+dfsg-2

apt-get worker: /var/lib/apt/lists/repository.maemo.org_extras_dists_diablo_free_binary-armel_Packages

Edit:
Kroll wrote that he didn't see any updates so he ran apt-get upgrade. I ran it also and it suggested following things:

Code:

The following packages have been kept back:

  libdb4.2  libxml2

The following packages will be upgraded:

  libgdbm3  libpurple0  pidgin-sounds  pre-installed-documentation-rx44

I didn't install those yet. Should I do it?

Re: 'Fixed in Fremantle' and Diablo community SSU

Another n800 with a successful upgrade.
I have to investigate why keychain stopped working (Error: Unable to use "ps" to scan for ssh-agent processes)

Edit: found it, ps doesn't support anymore the "ps x" syntax.

Re: 'Fixed in Fremantle' and Diablo community SSU

Quote:

Originally Posted by Mixu (Post 649087)

This is what I get after I re-enabled few repos back.

Nothing out of the ordinary there :-(

Could you also run "apt-key list" and "hildon-application-manager-config dump" in a terminal and check that their output contains

Code:

pub   1024D/3F027BB1 2010-05-04

uid                  maemo.org community repositories (diablo) <repositories@maemo.org>

sub   2048g/05F64387 2010-05-04

and

Code:

 <domain>

  <name>community-updates</name>

  <trust-level>650</trust-level>

  <key>11AA89A58197BDEFE5D7B0C96713C33F3F027BB1</key>

 </domain>

respectively?

Quote:

I ran it also and it suggested following things:

(no community updates) What does "dpkg -l osso-software-version-*" report?

Quote:

Code:

The following packages have been kept back:

  libdb4.2  libxml2

The following packages will be upgraded:

  libgdbm3  libpurple0  pidgin-sounds  pre-installed-documentation-rx44

I didn't install those yet. Should I do it?

Up to you, these packages are not relevant for the SSU. Do not install the libdb4.2 & libxml2 packages from extras though.

Re: 'Fixed in Fremantle' and Diablo community SSU

Quote:

Originally Posted by luca (Post 649393)

I have to investigate why keychain stopped working

Hm, what/where is that? Sounds interesting :-)

Quote:

found it, ps doesn't support anymore the "ps x" syntax.

Strictly speaking it never did. It claims to support POSIX-style arguments (rather than BSD, "ps -e" would be the closest equivalent) but silently ignores most of them :-/

But yeah, for some reason it now complains about x whereas it didn't before, thanks for spotting it. The change in behaviour is caused by CONFIG_FEATURE_PS_WIDE. With this enabled it compiles in call to getopt32 with the only option it does support, causing it to fail with anything else. I'll get rid of it.

Re: 'Fixed in Fremantle' and Diablo community SSU

Well, it's not a problem, after all keychain is a shell script so I edited it.

Edit: duh, I didn't see your question, this is keychain you have to be careful to only launch it from .profile when a terminal is actually available, otherwise the tablet will hang on boot.

Re: 'Fixed in Fremantle' and Diablo community SSU

Quote:

Originally Posted by lma (Post 649471)

Nothing out of the ordinary there :-(

Could you also run "apt-key list" and "hildon-application-manager-config dump" in a terminal and check that their output contains

Code:

pub   1024D/3F027BB1 2010-05-04

uid                  maemo.org community repositories (diablo) <repositories@maemo.org>

sub   2048g/05F64387 2010-05-04

and

Code:

 <domain>

  <name>community-updates</name>

  <trust-level>650</trust-level>

  <key>11AA89A58197BDEFE5D7B0C96713C33F3F027BB1</key>

 </domain>

respectively?

(no community updates) What does "dpkg -l osso-software-version-*" report?

I don't have a good place to host files at the moment so I will just dump these here :(

Code:

/etc/apt/trusted.gpg

--------------------

pub   1024D/13FA4ED6 2007-10-05 [expires: 2012-10-03]

uid                  Nokia repository signing key 4v1

sub   2048g/8B1115B2 2007-10-05 [expires: 2012-10-03]



pub   1024D/4C36F0B6 2007-10-05 [expires: 2012-10-03]

uid                  Nokia repository signing key 4v2

sub   2048g/3CF7720A 2007-10-05 [expires: 2012-10-03]



pub   1024D/32009917 2007-10-05 [expires: 2012-10-03]

uid                  Nokia repository signing key 2v1

sub   2048g/1F2E958F 2007-10-05 [expires: 2012-10-03]



pub   1024D/E1448911 2007-10-05 [expires: 2012-10-03]

uid                  Nokia repository signing key 2v2

sub   2048g/EE0B0D1A 2007-10-05 [expires: 2012-10-03]



pub   1024D/C8009E74 2007-10-05 [expires: 2012-10-03]

uid                  Nokia repository signing key 1v1

sub   2048g/C1B723AA 2007-10-05 [expires: 2012-10-03]



pub   1024D/7C4B240D 2007-10-05 [expires: 2012-10-03]

uid                  Nokia repository signing key 1v2

sub   2048g/0580E9EB 2007-10-05 [expires: 2012-10-03]



pub   1024D/413DA5CA 2007-10-05 [expires: 2012-10-03]

uid                  Nokia repository signing key 3v1

sub   2048g/4D5BEEF4 2007-10-05 [expires: 2012-10-03]



pub   1024D/EC9627ED 2007-10-05 [expires: 2012-10-03]

uid                  Nokia repository signing key 3v2

sub   2048g/0E39BF83 2007-10-05 [expires: 2012-10-03]



pub   1024D/3F027BB1 2010-05-04

uid                  maemo.org community repositories (diablo) <repositories@maemo.org>

sub   2048g/05F64387 2010-05-04

Code:

<config>

 <catalogue>

  <uri>http://catalogue.tableteer.nokia.com/certified/</uri>

  <components>user</components>

  <name>

   <en_GB>Nokia catalogue</en_GB>

   <default>Nokia Catalogue</default>

   <ru_RU>ÐšÐ°Ñ‚Ð°Ð»Ð¾Ð³ Nokia</ru_RU>

   <pt_BR>CatÃ¡logo Nokia</pt_BR>

   <fr_FR>Catalogue Nokia</fr_FR>

   <fr_CA>Catalogue Nokia</fr_CA>

   <da_DK>Nokia-katalog</da_DK>

   <it_IT>Catalogo Nokia</it_IT>

   <sv_SE>Nokia-katalog</sv_SE>

   <fi_FI>Nokia-tuotevalikoima</fi_FI>

   <nl_NL>Nokia-catalogus</nl_NL>

   <en_US>Nokia catalog</en_US>

   <de_DE>Nokia Katalog</de_DE>

   <es_MX>CatÃ¡logo de Nokia</es_MX>

   <es_ES>CatÃ¡logo de Nokia</es_ES>

   <pt_PT>CatÃ¡logo Nokia</pt_PT>

  </name>

  <sort-weight>100</sort-weight>

 </catalogue>

 <catalogue>

  <uri>http://catalogue.tableteer.nokia.com/non-certified/</uri>

  <components>user</components>

  <name>

   <en_GB>Nokia catalogue (3rd party software)</en_GB>

   <default>Nokia Catalogue (3rd party applications)</default>

   <ru_RU>ÐšÐ°Ñ‚Ð°Ð»Ð¾Ð³ Nokia (ÐŸÑ€Ð¾Ð³Ñ€Ð°Ð¼Ð¼Ð½Ð¾Ðµ Ð¾Ð±ÐµÑ�Ð¿ÐµÑ‡ÐµÐ½Ð¸Ðµ Ñ�Ñ‚Ð¾Ñ€Ð¾Ð½Ð½Ð¸Ñ… Ð¿Ñ€Ð¾Ð¸Ð·Ð²Ð¾Ð´Ð¸Ñ‚ÐµÐ»ÐµÐ¹)</ru_RU>

   <pt_BR>CatÃ¡logo Nokia (softwares de terceiros)</pt_BR>

   <fr_FR>Catalogue Nokia (logiciels de tiers)</fr_FR>

   <fr_CA>Catalogue Nokia des logiciels d&apos;autres fournisseurs</fr_CA>

   <da_DK>Nokia-katalog (tredjepartssoftware)</da_DK>

   <it_IT>Catalogo Nokia (software di terzi)</it_IT>

   <sv_SE>Nokia-katalog (tredjepartsprogramvara)</sv_SE>

   <fi_FI>Nokia-tuotevalikoima (kolmannen osapuolen ohjelmistot)</fi_FI>

   <nl_NL>Nokia-catalogus (software van derden)</nl_NL>

   <en_US>Nokia catalog (3rd party software)</en_US>

   <de_DE>Nokia Katalog (Software eines Fremdherstellers)</de_DE>

   <es_MX>CatÃ¡logo de Nokia (software de otros fabricantes)</es_MX>

   <es_ES>CatÃ¡logo de Nokia (software de terceras partes)</es_ES>

   <pt_PT>CatÃ¡logo Nokia (software de terceiros)</pt_PT>

  </name>

  <sort-weight>99</sort-weight>

 </catalogue>

 <catalogue>

  <name>

   <default>Nokia System Software Updates</default>

   <ru_RU>ÐžÐ±Ð½Ð¾Ð²Ð»ÐµÐ½Ð¸Ñ� Ñ�Ð¸Ñ�Ñ‚ÐµÐ¼Ð½Ð¾Ð³Ð¾ ÐŸÐž Nokia</ru_RU>

   <pt_BR>AtualizaÃ§Ãµes do Software de Sistema Nokia </pt_BR>

   <fr_FR>Mises Ã* jour systÃ¨me Nokia</fr_FR>

   <fr_CA>Mise Ã* jour du logiciel systÃ¨me Nokia.</fr_CA>

   <da_DK>Nokia system-softwareopdateringer</da_DK>

   <it_IT>Aggiornamenti software di sistema Nokia</it_IT>

   <sv_SE>Uppdateringar av Nokia-systemprogramvara</sv_SE>

   <fi_FI>Nokia-jÃ¤rjestelmÃ¤ohjelmiston pÃ¤ivitykset</fi_FI>

   <nl_NL>Updates voor Nokia-systeemsoftware</nl_NL>

   <en_US>Nokia System Software Updates</en_US>

   <de_DE>Nokia Systemaktualisierung</de_DE>

   <es_MX>Actualizaciones de Software del Nokia System</es_MX>

   <es_ES>Actualizaciones del software del sistema Nokia</es_ES>

   <pt_PT>ActualizaÃ§Ãµes de Software Nokia System</pt_PT>

   <en_GB>Nokia System Software Updates</en_GB>

  </name>

  <uri>http://catalogue.tableteer.nokia.com/updates/diablo-2/</uri>

  <dist>./</dist>

  <essential/>

  <nobackup/>

  <sort-weight>98</sort-weight>

 </catalogue>

 <catalogue>

  <uri>http://repository.maemo.org/extras/</uri>

  <dist>diablo</dist>

  <components>free non-free</components>

  <name>Maemo Extras</name>

  <sort-weight>50</sort-weight>

 </catalogue>

 <catalogue>

  <uri>http://browser-extras.garage.maemo.org/browser-extras/</uri>

  <dist>chinook</dist>

  <components>browser-extras</components>

  <disabled/>

  <name>Browser Extras</name>

 </catalogue>

 <catalogue>

  <uri>http://repository.maemo.org/extras/</uri>

  <dist>chinook</dist>

  <components>free non-free</components>

  <disabled/>

  <name>Chinook Extras</name>

 </catalogue>

 <catalogue>

  <uri>http://repository.maemo.org/community-testing/</uri>

  <components>free non-free</components>

  <name>Community SSU (testing)</name>

 </catalogue>

 <catalogue>

  <uri>http://repository.maemo.org/extras-devel</uri>

  <dist>diablo</dist>

  <components>free non-free</components>

  <disabled/>

  <name>Maemo Extras-Devel</name>

 </catalogue>

 <catalogue>

  <uri>http://maemo-hackers.org/apt</uri>

  <dist>chinook</dist>

  <components>main</components>

  <disabled/>

  <name>Maemo Hackers</name>

 </catalogue>

 <catalogue>

  <uri>http://ftp.mozilla.org//pub/mozilla.org/mobile/repos/1.9.2_multi</uri>

  <dist>chinook</dist>

  <components>extras</components>

  <disabled/>

  <name>Mozilla 1.9.2 multi Catalog</name>

 </catalogue>

 <catalogue>

  <uri>ftp://ftp.mozilla.org/pub/mozilla.org/mobile</uri>

  <dist>chinook</dist>

  <components>release</components>

  <disabled/>

  <name>Mozilla Catalog </name>

 </catalogue>

 <catalogue>

  <uri>http://moff.mozilla.com/</uri>

  <dist>chinook</dist>

  <components>release</components>

  <disabled/>

  <name>Mozilla Catalog </name>

 </catalogue>

 <catalogue>

  <uri>http://qole.maemobox.org/repository</uri>

  <components>user</components>

  <disabled/>

  <name>Qole&apos;s repo</name>

 </catalogue>

 <catalogue>

  <uri>http://trac.tspre.org/</uri>

  <dist>installer</dist>

  <components>main user</components>

  <disabled/>

  <name>TSpre.org installer repository</name>

 </catalogue>

 <catalogue>

  <uri>http://repository.maemo.org/extras</uri>

  <dist>chinook</dist>

  <components>free non-free</components>

  <disabled/>

  <name>maemo Extras (chinook)</name>

 </catalogue>

 <catalogue>

  <uri>http://repository.maemo.org/extras-devel/</uri>

  <components>free non-free</components>

  <disabled/>

  <name>maemo Extras-Devel</name>

 </catalogue>

 <domain>

  <name>maemo-extras</name>

  <trust-level>200</trust-level>

  <key>1CC1A2A2B8CE8F258F896B4207C0DFF713FA4ED6</key>

  <key>CC3E6BA3EE288AECEE24FD8EB6ECBFF74C36F0B6</key>

 </domain>

 <domain>

  <name>nokia-certified</name>

  <trust-level>400</trust-level>

  <key>690BD534D587789DA1A52A2934BAC20232009917</key>

  <key>E864E565F170B70682C58C56CA597434E1448911</key>

  <certified/>

 </domain>

 <domain>

  <name>nokia-system</name>

  <trust-level>500</trust-level>

  <key>24A87CA5126ECA0768C98704F5925991C8009E74</key>

  <key>1EBB13C52EE93405F7945357C25C6C897C4B240D</key>

  <default/>

  <certified/>

 </domain>

 <domain>

  <name>nokia-selected</name>

  <trust-level>300</trust-level>

  <key>A3AD7F8641DBAFE6B73FB11B711EA8AC413DA5CA</key>

  <key>3E8E0B3B55ECA44D2B06D6637DB1CFFAEC9627ED</key>

 </domain>

 <domain>

  <name>community-updates</name>

  <trust-level>650</trust-level>

  <key>11AA89A58197BDEFE5D7B0C96713C33F3F027BB1</key>

 </domain>

 <notifier>

  <uri>http://tableteer.nokia.com/application-notices/notice-${HARDWARE}-diablo</uri>

 </notifier>

</config>

Code:

Desired=Unknown/Install/Remove/Purge/Hold

| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed

|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)

||/ Name                                             Version                                    Description

+++-================================================-==========================================-======================================================================================================

ii  osso-software-version-rx44                       1:5.2010.16-1                              Bug fixes and enhancements to kernel, X server, modest, busybox, DNS resolution, PDF viewer and Jabber

un  osso-software-version-variant                    <none>                                     (no description available)

Re: 'Fixed in Fremantle' and Diablo community SSU

Quote:

Originally Posted by Mixu (Post 649617)

Code:

ii osso-software-version-rx44 1:5.2010.16-1

According to this your device is already up-to-date, or am I missing something?

Re: 'Fixed in Fremantle' and Diablo community SSU

Quote:

Originally Posted by lma (Post 649659)

According to this your device is already up-to-date, or am I missing something?

Then it must be. I thought that I need to install something after the enabler. I'm bit confused.. :confused:

Thanks for the help!

Re: 'Fixed in Fremantle' and Diablo community SSU

only if one had not tested the community update before, iirc.

heck, even now the community update is not official, but with the repos in place, its closer then ever.

Re: 'Fixed in Fremantle' and Diablo community SSU

I haven't tested the previous update. But most likely my device is just fine and I just don't know what I'm doing as usual ;)

Re: 'Fixed in Fremantle' and Diablo community SSU

Quote:

Originally Posted by lma (Post 642634)

Thanks to X-Fade who spent this afternoon working on this, we now have maemo.org signed repositories! Without further ado, they are:

Code:

deb http://repository.maemo.org/community/ diablo free non-free

deb http://repository.maemo.org/community-testing/ diablo free non-free

The community/ one is supposed to be the "stable" one and is currently empty, while community-testing now holds the contents of my private testing repository.

To current testers: all further development will happen there, so feel free to remove the private repo from your application manager config (I'll be closing it down anyway, but disabling it will save you unnecessary HTTP requests).

To everyone else who is interested in testing:

Make sure you have not (perhaps unintentionally) removed the appropriate osso-software-version-rxXX package for your device, of if you have re-install it as SSU simply won't work without it.
Visit http://repository.maemo.org/communit...esting.install with the built-in browser (microb) and open it with the application manager when prompted. This will install the community-testing repository and an enabler package that loads its public key and sets up the package domain with a higher priority than the nokia-system one so that nokia-system packages can be updated.
Refresh the application manager (bottom right button) so it will see the packages in the community-updates domain and offer the update.
Install the update.
Report any issues here (for now, I'll be bugging Andre for a bugs.maemo.org product soon).

To anyone interested in contributing: look at http://wiki.maemo.org/Talk:Diablo_Community_Project for the backlog and see if anything grabs your interest :-)

If possible can this info put on the first post for other users ?

Re: 'Fixed in Fremantle' and Diablo community SSU

IS there a list somewhere online that shows WHAT is in this SSU?

It is my understanding that the list in http://wiki.maemo.org/Talk:Diablo_Community_Project is not the list of changes in this SSU.

Re: 'Fixed in Fremantle' and Diablo community SSU

Quote:

Originally Posted by silvermountain (Post 652748)

IS there a list somewhere online that shows WHAT is in this SSU?

I posted a list here.

Quote:

It is my understanding that the list in http://wiki.maemo.org/Talk:Diablo_Community_Project is not the list of changes in this SSU.

Correct, that's more of a TODO list.

Re: 'Fixed in Fremantle' and Diablo community SSU

Quote:

Originally Posted by lma (Post 653007)

I posted a list here.

Thanks!!!
Either you just posted it - or I am more blind than I thought :)
Now I got a check-list to use when trying out the SSU update.

Thanks again.

Re: 'Fixed in Fremantle' and Diablo community SSU

So, I decided to test my updated N810 and installed Advanced Backlight. If I try to rotate the screen, it doesn't really rotate. Screen stays the same (or sometime there are some artifacts) BUT the actual controls are changed. For example if I rotate the screen upside down, the image that I see is the same but I have to click top right corner to access the home menu instead of bottom left.
So do I need to do some additional steps to get the Advanced Backlight to work or is my N810 still not upgraded?

Re: 'Fixed in Fremantle' and Diablo community SSU

Quote:

Originally Posted by Mixu (Post 653604)

If I try to rotate the screen, it doesn't really rotate. Screen stays the same (or sometime there are some artifacts) BUT the actual controls are changed.

Sounds like you have rotation support in the X server but not in the kernel. This could happen if you updated with apt, which doesn't actually write the new kernel in the appropriate flash partition. If that's the case, close all apps and run /usr/bin/flash-and-reboot as root.

Re: 'Fixed in Fremantle' and Diablo community SSU

Ah, now it works! Thanks!

Re: 'Fixed in Fremantle' and Diablo community SSU

Installed SSU and it works really well - no issues detected so far.
The Advanced Power screen rotation options are nice.

Re: 'Fixed in Fremantle' and Diablo community SSU

Anyone tried installing sliderotate after updating? It worked fine for me when I updated and had it already installed, but in this thread, Silvermountain claims that the automatic install script for sliderotate isn't working for him, which strikes me as odd seeing as very few (if any) people reported issues after the automatic script was released, and my natural instinct (as with any other problem these days) is to blame the SSU

Re: 'Fixed in Fremantle' and Diablo community SSU

Quote:

Originally Posted by notnarb (Post 654844)

If the binary package (I can't browse the repository as it redirects to the blog) is the same as the one found in the garage page, it depends on a specific xserver-xomap version:

Code:

Depends: python2.5-runtime, xrandr (>= 1:1.2.2-0), xserver-xomap (= 1:1.3.99.0~git20070321-0osso20074202), libxrandr2 (>=2:1.2.1-1), xmodmap, flash-and-reboot

that is different to the one in the community SSU. Making it work should be a simple matter of repackaging, however there are no source packages that I can find and the garage SCM is empty.

Re: 'Fixed in Fremantle' and Diablo community SSU

been observing a slight distortion of the theme when i use screen rotation.

Re: 'Fixed in Fremantle' and Diablo community SSU

Quote:

Originally Posted by notnarb (Post 654844)

True.
My install steps were as follows;

1) Installed SSU update
[Advanced Light rotation options works well]

2) Installed Slideroate
[First got a message in App Manager it had failed, tried update it, failed, uninstalled it and re-installed which made it install ok]

3) Used the Sliderotate settings option and the one thing that doesn't happen is a self-reboot after instaling xrandr support.
Manually rebooted. None of the features from sliderotate are active.

(I repeated steps 2-3 maybe three times and sometimes there was a flicker of functionality (like the power button rotating the screen) but it only lasted for so long then nothing).

I will be reflashing my N810 this weekend and this time I can try to install slide-rotate first and then the SSU - but am taking 'suggestions' on what to try/do if anything could benefit the SSU project.

Re: 'Fixed in Fremantle' and Diablo community SSU

Quote:

Originally Posted by lma (Post 654931)

that is different to the one in the community SSU. Making it work should be a simple matter of repackaging, however there are no source packages that I can find and the garage SCM is empty.

It is python, so the package itself can be the sources (I haven't looked at it)