Re: [Announce] CSSU stable release
 

Full full like this Community SSU/ChangelogStable

Greetings.

Re: [Announce] CSSU stable release
 

who can take a picture to see difference CSSU?

Re: [Announce] CSSU stable release
 

how to install cssu stable.i hav the latest cssu. but dint get the stable in the app manager

Re: [Announce] CSSU stable release
 

Where have you been?
reflash the phone and install the stable from the beginning
or stay with the testing

Re: [Announce] CSSU stable release
 

If you mean the latest cssu-testing by "latest" then you can only install stable by reflashing and following the instructions on the wiki.

But keep in mind that stable is only a subset of testing, if you want to stay bleeding edge I advise against switching to stable.

Re: [Announce] CSSU stable release
 

I see a lot here about reflashing, or reflashing if something goes wrong.

Does that mean it's not safe to install CSSU with a broken USB port?

(Regrettably I don't know how to get the port fixed, except purchase another N900.)

Thanks,

Re: [Announce] CSSU stable release
 

Definitely not the Stable one!

Re: [Announce] CSSU stable release
 

im currently running on http://i41.tinypic.com/11sku15.png

do i need a reflash? please confirm.

Re: [Announce] CSSU stable release
 

Just did a clean install on my friends N900. First updated to PR 1.3.1 and then to CSSU stable. Had some problems with Advanced power monitor but reinstall helped. Did the whole proces as in the wiki but one thing came out during this proces. Faster Aplicaiton Manager isn't that good. While I wanted to uninstall Advanced power monitor it wanted to uninstall severall other apps as oppposite to HAM which did it properly. HAM is slow bud does things as it should.

Re: [Announce] CSSU stable release
 

It should be possible to "drift" from testing to stable just like one would do in Debian. To do that one would have to change the repository from testing to stable which should be done as soon as possible (given that the current testing works fine for you right now).

The effect would be that at the moment nothing will happen because the testing packages are newer than the stable packages. But as time goes by new packages will enter stable and eventually they'll have higher version numbers than the current testing and replace the testing packages bit by bit until nothing of the current testing is left.
Until the transition is complete (which will only happen if eventually all testing packages will make it to stable) the system will be in a state which is similar to one that is based on stable but has some (at the moment - all) packages pinned from testing.
If you chose that way you should know exactly what you're doing. As a rule of thumb: If you don't know what I'm talking about in ths post, don't do it!