Mart5.1 | # 691 | 2011-02-17, 07:47 | Report

Thanks for your help, Sorry for the delay.
here is the command output you asked for.

BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso30+0m5) built-in shell (ash)
Enter 'help' for a list of built-in commands.

~ $ gconftoo -R /system/osso/dsm
-sh: gconftoo: not found
~ $ gconftool -R /system/osso/dsm
/system/osso/dsm/vibra:
touchscreen_vibra_enabled = false
/system/osso/dsm/locks:
devicelock_password_changed = false
devicelock_failed = 0
devicelock_total_failed = 0
devicelock_autolock_timeout = 1000
devicelock_autolock_enabled = false
touchscreen_keypad_autolock_enabled = true
/system/osso/dsm/leds:
PatternCommonNotification = true
PatternBatteryCharging = true
PatternCommunicationSMS = true
PatternCommunicationEmail = false
PatternDeviceOn = false
PatternCommunicationCall = true
PatternCommunicationIM = true
/system/osso/dsm/display:
display_brightness = 2
display_dim_timeout = 30
inhibit_blank_mode = 0
enable_power_saving = true
~ $ gconftool -R /system/osso/dsm
/system/osso/dsm/vibra:
touchscreen_vibra_enabled = false
/system/osso/dsm/locks:
devicelock_password_changed = false
devicelock_failed = 0
devicelock_total_failed = 0
devicelock_autolock_timeout = 1000
devicelock_autolock_enabled = false
touchscreen_keypad_autolock_enabled = true
/system/osso/dsm/leds:
PatternCommonNotification = true
PatternBatteryCharging = true
PatternCommunicationSMS = true
PatternCommunicationEmail = false
PatternDeviceOn = false
PatternCommunicationCall = true
PatternCommunicationIM = true
/system/osso/dsm/display:
display_brightness = 2
display_dim_timeout = 30
inhibit_blank_mode = 0
enable_power_saving = true

---

Last edited by Mart5.1; 2011-02-17 at 07:49.

slender | # 692 | 2011-02-17, 07:55 | Report

Reading this thread just shows us that how frustrating it is to give users updates to their core system. No wonder why there is so much noise in bugzilla Nokia dudes test probably _only_ with freshly flashed devices where there is no 3rd party apps. Additionally I have to say that during n900+maemo I have realized that why other mobile systems are so freakishly locked down. Looks like that It makes sense :|

If you update your device then everything comes basically to this: Have you installed _any_ applications that alter system settings. Of course most of users can´t give answers to this question easily because well, they just install what they install by clicking stuff from HAM or FAP and in worst case do not even know if it´s from extras, testing or devel repositories.

I think devels of Community SSU should more clearly point out and that if you cannot debug stuff by yourself then maybe this thing is not for you.

Put big BOX on top of this page:
http://wiki.maemo.org/Community_SSU

I have not YET tried to test this update but I would like to ask that is it possible to give user popup warning before installation with SINGLE SENTENCE where he/she is warned about using this update.

btw. There is no link to community-SSU from main page of repositories:
http://repository.maemo.org/

wumpwoast | # 693 | 2011-02-17, 08:00 | Report

Problem disappeared -- my MyDocs partition was full at the time so this may have been the cause. May be cause to improve error handling for certain events in modest, but inevitably a ebcak-style issue.

slender | # 694 | 2011-02-17, 08:15 | Report

Okeyyyy...

Is there garage page for this project?
Is there maemo.org/packages page for this project?
There is GIT page for all these packages?
There is bugzilla pages for these packages?
Should there be twitter page that is automatically updated when repository is updated...to boost stuff up and market this wonderful project.
There is wiki page for this project. There is TMO entry for this project.
Could we use brainstrom? How it could be integrated closely to this so that it isn't just one extra "module" of pages around this?

Currently I see spaghetti of stuff from point of tester/user Devels probably swim there like sharks but to me all this looks like big blob of strings flowing around.

How we can combine all of these in efficient way? Of course putting links to wiki page is first thing to do but what then? How we could categorize conversations so that people talking about hildon-desktop do not come same conversation where people have talk about modest? Maemo.org/packages kind of resolution. Or what else?

I´m not giving any resolution here just thinking aloud stuff that comes to my head

First and foremost I think it should be really important to point out users WHAT packages there is currently inside of this update. "Go look from git", or "use dpkg -zxczxczxcxzcz" tadaa is not what I´m lookg for. List of applications and not only package names because to most of users modest doesn't mean anything. IMO this should be stated on Wiki page before anything else.

And reason why I do not do any wiki editing is that I´m 85% sure that it would go wrong :| Not that I do not know how to edit but information I would put there would probably be not exact!

wimmme | # 695 | 2011-02-17, 09:28 | Report

works for me too !

nicolai | # 696 | 2011-02-17, 09:33 | Report

Hi Mart5.1,

there are some gconfsettings missing. Have changed your
gconf manually. Or did you use any other application which
changed the display brightness configuration.

Nicolai

Mart5.1 | # 697 | 2011-02-17, 09:56 | Report

Hi Nicolai,
I do not think i have any apps that change the brightness, I did have to change gconf once but cannot remember for which app or widget sorry.But after installing the ssu package it reboots and says installing do not interrupt, then reaches 7% and shuts off, in app man its says the package is broken but installable, the ssu pack is always in the update list but seems to only partially install.

AlMehdi | # 698 | 2011-02-17, 10:04 | Report

My guess is that one of the packages are missing an dependency and thus fails to install all the packages. Could you try installing using apt-get instead?

1. sudo gainroot
2. apt-get update
3. apt-get upgrade

droitwichgas | # 699 | 2011-02-17, 10:31 | Report

In my view there are sufficent warnings and the Developers are doing a fantastic job. It seems we have two choices here either we accept the CSSU may not be perfect all users or we accept there will never be anymore upgrades for the N900 as it is clear Nokia will not be issuing PR1.4 etc.

I no which option I will take and I assume that will go for 99% of the forum users.

Any users who have run into problems do seem to have received fantastic assistance from the Developers and all seem to have had any issues resolved.

I do agree the first page could be altered and have rasied this prevously as the original page on this thread did list the download instructions/warnigs. Perhaps there is an arguement for closing this thread and starting a new one with the CSSU instuctions as the first post but perhaps that will happen when the CSSU moves to stable in due course?

Jaffa | # 700 | 2011-02-17, 10:38 | Report

Apparently the first page can't be altered, except by the original author. Anyway, maintaining the information in two places is a recipe for disaster. The definitive instructions are, and always will, be at:

http://wiki.maemo.org/Community_SSU

The mini-site is evolving really well, and we now have a page (which needs fleshing out, contributions welcome!) on how to use the new features in transitions.ini

---

Last edited by Jaffa; 2011-02-17 at 10:43. Reason: BBCode