Active Topics
-
Maemo repository (8)
to Community by Maemish - 1 day ago -
Porting apps to Leste (44)
to Maemo 7 / Leste by norayr - 1 day, 4 hrs ago -
List of well performing apps on Leste (35)
to Maemo 7 / Leste by smatkovi - 4 days, 2 hrs ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (13)
to SailfishOS by edp17 - 5 days ago -
Sailfish OS for the Samsung Galaxy Note 4 (SM-N910C) - (treltexx) (79)
to SailfishOS by edp17 - 5 days ago -
U-Boot for Nokia RX-51 with BootMenu (updated version 2012.10-rc3-1) (843)
to Alternatives by Arno_11 - 5 days, 5 hrs ago - more...
 |
|
2012-01-11
, 22:49
|
|
Posts: 1,986 |
Thanked: 7,698 times |
Joined on Dec 2010
@ Dayton, Ohio
|
#32
|
Originally Posted by woody14619
Not a problem on my machine. I have seen problems after 60 or more days of uptime, though, so there must be some parts of PR1.X that could use fixing. (That is, assuming it wasn't something I did to the machine myself.)
I'd be willing to bet that most people runing PR1.X without CSSU have problems achieving more than 7 days of uptime without needing to reboot.
I can tell you the GUI improvements in CSSU are really nice. ... It also no longer grows in memory size every day, like the old one did.
 |
|
2012-01-11
, 23:18
|
|
Posts: 1,455 |
Thanked: 3,309 times |
Joined on Dec 2009
@ Rochester, NY
|
#33
|
Originally Posted by Copernicus
I can tell you that's probably a very very rare experience. Either you're not using it at all, or you've tweaked the crap out if it. Most stock PR1.3 users don't see uptimes beyond a week. The forum is chock-full of people siting just that.
Not a problem on my machine. I have seen problems after 60 or more days of uptime,
Originally Posted by Copernicus
No, I can't. I can tell you that on my PR1.3 system, hildon-desktop and/or hildon-home would increase in size over time. Short of killing them, and re-starting, they would not get smaller. I no longer have that issue with CSSU, and have changed nothing desktop wise in that time frame.
Now, this is something interesting! Can you provide any documentation about this fix? Where was the memory leak? What was done to fix it? Can we put this somewhere in the CSSU wiki?
If I could have provided a line/diff/offset to show where it was leaking, it wouldn't have been, because I would have fixed it. Though I'm sure if you look at the CSSU source garage and searched for "leak" you'd find plenty of check-ins matching.
I'm not here to help you justify loading CSSU on your device. That's your decision. I'm just here to tell you, it's not all about portrait mode and flashy transitions. Want to see what was changed? Read the change log that's been linked to by at least 3 posts now (including edits to the top post). I'm off to enjoy my N900, with CSSU installed.
| The Following 3 Users Say Thank You to woody14619 For This Useful Post: | ||
|
|
2012-01-11
, 23:29
|
|
Posts: 2,076 |
Thanked: 3,268 times |
Joined on Feb 2011
|
#34
|
Originally Posted by woody14619
It is also full of people who install speed patches, battery patches and other improvements, so it is not a good measure. Pretty sure long-uptime stability is introduced by KP as I am another very rare example of uptimes of around a month with no issues.
I can tell you that's probably a very very rare experience. Either you're not using it at all, or you've tweaked the crap out if it. Most stock PR1.3 users don't see uptimes beyond a week. The forum is chock-full of people siting just that.
| The Following 2 Users Say Thank You to szopin For This Useful Post: | ||
|
|
2012-01-11
, 23:48
|
|
Posts: 2,076 |
Thanked: 3,268 times |
Joined on Feb 2011
|
#35
|
Btw, the cause of backward incompatibility was introduced in the first leet version of CSSU:
http://wiki.maemo.org/Community_SSU/...g#PR_1.3.3.7-1
The whole patch for bug 6009 is one line change:
- {GDK_KP_Enter, _vte_keymap_GDK_KP_Enter},
+ {GDK_KP_Enter, _vte_keymap_GDK_Return},
In keymap.c file of vte, not a new upstream version, just remapping that causes, very rarely, issues. Not sure if there isn't another workaround, but remapping and pushing it to a release (of a non-removable os update) after 20 days of testing definitely wouldn't catch all possible problems with repos full of programs (Jan 2011).
Bugfixes like this should cause now every maintainer to push two versions (or three with stable version out now) of their progs? All the hundreds of maintainers should now come back and recompile? If this would update libvte I would probably consider it an option (4 vs 9, sure why not), but as a quick fix that introduces incompatibility, sorry but no
http://wiki.maemo.org/Community_SSU/...g#PR_1.3.3.7-1
The whole patch for bug 6009 is one line change:
- {GDK_KP_Enter, _vte_keymap_GDK_KP_Enter},
+ {GDK_KP_Enter, _vte_keymap_GDK_Return},
In keymap.c file of vte, not a new upstream version, just remapping that causes, very rarely, issues. Not sure if there isn't another workaround, but remapping and pushing it to a release (of a non-removable os update) after 20 days of testing definitely wouldn't catch all possible problems with repos full of programs (Jan 2011).
Bugfixes like this should cause now every maintainer to push two versions (or three with stable version out now) of their progs? All the hundreds of maintainers should now come back and recompile? If this would update libvte I would probably consider it an option (4 vs 9, sure why not), but as a quick fix that introduces incompatibility, sorry but no
| The Following User Says Thank You to szopin For This Useful Post: | ||
|
|
2012-01-12
, 00:02
|
|
Posts: 291 |
Thanked: 398 times |
Joined on Jan 2011
@ USA
|
#36
|
I did tried the stable cssu and didn't see anything different and then I tried the testing cssu i noticed the portrait mode and camera ui changes, portrait mode was a nice but most app was just opened in landscape mode, which made the portrait mode kinda silly and the cssu did break the sketch app on my device. In the end I decided to reflash the device and just installed kernel power and few other necessary apps, and unstalled most of the pre-installed games and widgets that i don't need. I've using n900 for 2yrs and my device have never shutdown on its own. The longest uptime i remember that I had was about six months and all others was just me rebooting the phone after messing with the system.
| The Following User Says Thank You to khuong For This Useful Post: | ||
|
|
2012-01-12
, 00:47
|
|
Posts: 1,986 |
Thanked: 7,698 times |
Joined on Dec 2010
@ Dayton, Ohio
|
#37
|
Originally Posted by woody14619
Ok, then, I guess I'm a rarity. As you might guess, I don't really tweak much; never felt the need. Perhaps I do use my phone more "gently" than others here, but I do use it every single day, browsing the web, listening to podcasts, editing files in Vim. But yeah, I don't see a lot of problems with stock PR1.3.
I can tell you that's probably a very very rare experience. Either you're not using it at all, or you've tweaked the crap out if it. Most stock PR1.3 users don't see uptimes beyond a week. The forum is chock-full of people siting just that.
| The Following User Says Thank You to Copernicus For This Useful Post: | ||
 |
|
2012-01-12
, 00:50
|
|
Posts: 5,028 |
Thanked: 8,613 times |
Joined on Mar 2011
|
#38
|
Originally Posted by Copernicus
Here I agree 100% - I'm not sure if current description brings always "desired" audience to the project... Yet, it's really a *minor* (minorish minor) issue, and if CSSU would have only such problems, I would be happy penguin.
Beyond the bare assertion that the CSSU is the "continuation of Nokia's SSU", all that the wiki talks about (beyond how to install it) is the new pretty transitions, rotations, and portrait mode.
Honestly, we could do with a bit of instruction here, if the CSSU is actually not what it is being advertised to be...
Also, woody14619 provided some nice links with detailed changelogs. + I totally agree with his rationale about compatibility - sorry szopin, but I remember crawling through pages and pages of discussions, about how PR1.3 resulted in some package being incompatible.
You ask, if maintainers should fork their applications? IMO no, they should write it to work well on latest upstream version (being CSSU Stable now), which 99% of the times meant working well on experimental (CSSU-testing). If it also works nice on PR1.31, PR1.3, PR1.2, PR1.1 and so goes on, it's great. If not, it's generally problem of user refusing to upgrade - after all, it's FOSS, and you don't need to pay for new version...
Of course, if maintainer want to fork program for different (C)SSU's - that's great. As it was stated, it happened many times, when PR1.3 was young. If not maintainer, but someone else want to backport things to older (C)SSU's, that's also great. But, it isn't required.
/Estel
__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
| The Following User Says Thank You to Estel For This Useful Post: | ||
|
|
2012-01-12
, 00:58
|
|
Posts: 131 |
Thanked: 62 times |
Joined on Feb 2010
|
#39
|
Havnt updated simply cause my phone works.
If I could be sure that the various fiunctions I use work in CSSU then I would update.
rather than mess aorund making them work, easier to stick with a functioning system.
Since I can easily program any function I need that does not exist, I am happy to work with what I have.
Hats off to the community and I fully support the efforts to update CSSU.
rgds
If I could be sure that the various fiunctions I use work in CSSU then I would update.
rather than mess aorund making them work, easier to stick with a functioning system.
Since I can easily program any function I need that does not exist, I am happy to work with what I have.
Hats off to the community and I fully support the efforts to update CSSU.
rgds
|
|
2012-01-12
, 01:14
|
|
Posts: 2,076 |
Thanked: 3,268 times |
Joined on Feb 2011
|
#40
|
Originally Posted by Estel
That is also the problem. Main focus on portrait mode is visible through whole this thread. Biggest feature advertised it would seem. Patches introduced incompatiblity in a _must have_ app - xterm a year ago, yet everyone was testing how the screen rotates. I would be a happy penguin if CSSU was just bringing latest upstream versions and properly tested fixes.
Here I agree 100% - I'm not sure if current description brings always "desired" audience to the project... Yet, it's really a *minor* (minorish minor) issue, and if CSSU would have only such problems, I would be happy penguin.
Originally Posted by Estel
That's not great at all. Latest 'supported' (for whatever it's worth) upstream version of maemo OS is 1.3.1, not leet version. Decisions about keymapping was made probably too long ago to make everyone happy (N810 had similar issues and the patch didn't make it upstream at that time, which would have probably prevented problems currently), but xterm incompatibility 'fix' that claims to:
Also, woody14619 provided some nice links with detailed changelogs. + I totally agree with his rationale about compatibility - sorry szopin, but I remember crawling through pages and pages of discussions, about how PR1.3 resulted in some package being incompatible.
You ask, if maintainers should fork their applications? IMO no, they should write it to work well on latest upstream version (being CSSU Stable now), which 99% of the times meant working well on experimental (CSSU-testing). If it also works nice on PR1.31, PR1.3, PR1.2, PR1.1 and so goes on, it's great. If not, it's generally problem of user refusing to upgrade - after all, it's FOSS, and you don't need to pay for new version...
Of course, if maintainer want to fork program for different (C)SSU's - that's great. As it was stated, it happened many times, when PR1.3 was young. If not maintainer, but someone else want to backport things to older (C)SSU's, that's also great. But, it isn't required.
/Estel
The fix makes sure the key works as expected under any X Terminal application.
clearly does not do so.
End users refusing to update? You have been on this forum enough to know how easy it is to contact maintainers of apps from a year ago to rebuild/update. Sad, but every backwards incompatible 'fix' is a mess
| The Following User Says Thank You to szopin For This Useful Post: | ||
I've been playing around with Qt on Maemo for a few months now, works pretty well for me so far. The bug fixes mentioned on the 4.7.4 changes page would be nice to have, but they don't look earth-shattering. I don't see why I can't live without them...