... and for my first blog ever... SHR testing did not see activity for quite some time now. Mainly because there were lots of changes in and around SHR. The new kernel comes to mind... a constant flow of changes in OpenEmbedded which made building difficult from time to time... and inside SHR the restructured EFL frontend from quickdev. That all needed stabilizing.
Now we feel confident that SHR unstable is actually stable enough to be called
testing instead :-)
So, what will happen is that current SHR unstable appears as testing. We will set fixed revisions for the important components like frameworkd and only update those if really needed. Further we will try hard to not break it :-)
The other thing going to happen is unstable being rebased on to a newer EFL (enlightenment) revision. This is going to cause lots of things to break. Don't expect to be able to write SMS or edit contacts... expect it to segfault a lot instead - you have been warned ;)
In unstable we will then go wild to integrate lots of new stuff. Some things which we could put on the table are:
- rewrite of ophonekitd in vala
- switch to current enlightenment
- start integration of opimd
- replace udev with mdev
- base SHR on the new minimal distro config from mickeyl
This has consequences for current users of SHR. First... those of you still using the SHR testing images from last year will have to reflash to get the new testing.
Second, those of you using SHR unstable should change the repo config from unstable
to testing in /etc/opkg/*.conf. Otherwise your phone might brake with the next
opkg upgrade.
One big issue with current SHR is enlightenment still using lots of CPU. We still did not (yet) manage to solve that. One thing you can do to get the CPU usage down is:
a) wait until e started up
b) ssh into your phone
c) mv /usr/share/applications/openmoko-calendar.desktop /tmp
d) mv /tmp/openmoko-calendar.desktop /usr/share/applications
after that e should consume around 0.x% CPU - until next X restart.
Klaus 'mrmoku' Kurzmann
Now we feel confident that SHR unstable is actually stable enough to be called
testing instead :-)
So, what will happen is that current SHR unstable appears as testing. We will set fixed revisions for the important components like frameworkd and only update those if really needed. Further we will try hard to not break it :-)
The other thing going to happen is unstable being rebased on to a newer EFL (enlightenment) revision. This is going to cause lots of things to break. Don't expect to be able to write SMS or edit contacts... expect it to segfault a lot instead - you have been warned ;)
In unstable we will then go wild to integrate lots of new stuff. Some things which we could put on the table are:
- rewrite of ophonekitd in vala
- switch to current enlightenment
- start integration of opimd
- replace udev with mdev
- base SHR on the new minimal distro config from mickeyl
This has consequences for current users of SHR. First... those of you still using the SHR testing images from last year will have to reflash to get the new testing.
Second, those of you using SHR unstable should change the repo config from unstable
to testing in /etc/opkg/*.conf. Otherwise your phone might brake with the next
opkg upgrade.
One big issue with current SHR is enlightenment still using lots of CPU. We still did not (yet) manage to solve that. One thing you can do to get the CPU usage down is:
a) wait until e started up
b) ssh into your phone
c) mv /usr/share/applications/openmoko-calendar.desktop /tmp
d) mv /tmp/openmoko-calendar.desktop /usr/share/applications
after that e should consume around 0.x% CPU - until next X restart.
Klaus 'mrmoku' Kurzmann
c) mv /usr/share/applications/openmoko-calendar.desktop /tmp
d) mv /tmp/openmoko-calendar.desktop /usr/share/applications
What? Why does this help?
Reloading Home-Screen?
Is the new SHR testing based on MS4.1 or MS5?
The old testing works quite good for me, but in MS4.1 GPRS is too unstable (cellhunter crashes gsmd when uploading every 10 seconds). In MS5 it is should be stable.
Thanks for the nice distro,
Kelvan
ouch... it was meant to be calculator... not calendar :-)
mv /usr/share/applications/openmoko-calculator.deskop /tmp
mv /tmp/openmoko-calculator.desktop /usr/share/applications
why that does help? no idea.
Ahh, and SHR is MS5 based, yeah.
This is a great news!
Good job!
My unstable work well, if not considering details (GPS don't synchronize, sometimes GSM cant connect to dbus and I got "no service" ...)
Sure it will be fixed soon.
When do you plan to call it "stable" :)
Having a look at http://build.shr-project.org/shr-testing/ i get a bit confused by the directory structure: this directory still contains the december stuff whereas the ./glibc subdirectory within holds a bunch of new files. Is this intentional or a messup?
mv /usr/share/applications/openmoko-calculator.deskop /tmp
mv /tmp/openmoko-calculator.desktop /usr/share/applications
Is there a way to automate this so that it occurs every time X restarts? crontab perhaps?