yeah, agree. Under GPL license, they should provide source to the user, i.e., us.
i dont believe so. but we can try it.
lets write a mail to motorola![]()
yeah, agree. Under GPL license, they should provide source to the user, i.e., us.
one question, does the code is really GPL? who's does it belong to? MVista or Motorola. anyone can shed some light on this?
i think we all should email to Moto/MVista for the code if it's GPL. even better if we could spread the news to other E680 users/forum ( hobo? ccweb? blah blah? ) something like recent Activism stuff being done @ OpenBSD effort for the Wifi thingy.
http://www.theage.com.au/articles/20...992287663.html
maybe we can even talk to the guys @ http://gpl-violations.org for some advice.
pls comment.
well, when it comes to the kernel we should be able refer to the GPL..
but qt-embedded, well depends if motorola created thier ezx for the GPL sources
or if they got it under other licensing (if that is possible)..
the gpl-violations guys are already on them tough, but more pressure is always good of course![]()
one small step for me but a huge step for all of us
1) i found out how to start opie apps while the ezx-windowsserver is running and it is possible to have input to the opie app. the disadvantage is that the buttons on top of the screen (home, contacts, message, phone) will resist and cover the titel and menu of the opie app. ;(
2) also i found out how to start ezx-apps when opie is running as qws server. (killing windowsserver before and starting a single opie app with -qws oder running qpe).
The app that acts as displaymanager will create a unix socket /tmp/qtembedded-??/Qt-Embedded-0 .
if ezxs windowsserver is running ?? is ezx (/tmp/qtembedded-ezx/Qt-Embedded-0)
if opie is running ?? is 0 (/tmp/qtembedded-0/Qt-Embedded-0)
in case 1) you need to symlink /tmp/qtembedded-ezx/Qt-Embedded-0 to /tmp/qtembedded-0/Qt-Embedded-0
in case 2) vis versa
for case 1) buttons does not realy work. only the navi button "up" and the real player button (upper left) does something.
for case 2) ezx apps need a proper set of env vars to work well.
wish you all a happy easter![]()
And here are two nice tools to explore the processes of the running system:
strace: a useful diagnostic, instructional, and debugging tool
lsof: list open files
That's great news!!
but I thought I'd tried that symlinking earlier and it didn't work then..
any special permissions or somehtin about that symlink?
do you run the apps as root or ezx?
ok, I got a few opie apps running, but some like tinykate and textedit
just quits right off.. the games seems to work better.. strange
both go and tetrix works fullscreen maybe they're pure qte apps
and not opie dependant..
at the moment for testing i run them as root.
and all apps started under qpe runs fine.
i did few changes for .config of opie. selected all apps and changed some other settings there.
nothing special about the symlinks. just "cd /tmp/qtembedded-0 && ln -s /tmp/qtembedded-ezx/Qt-Embedded-0"
how do you start the opie apps? and what about the covered titel and menu of opie apps by ezx buttons on top (home, contacts, message, phone)
I started them without qpe using my little script on my guide site..
Hmm but when I start qpe as root it seems to start an qws of its own
also the symlinks gone when I exit qpe (well, when I kill it since the native
qws runs on to of the whole qpe)
btw don't u create the /tmp/qtembedded-0 then?
I will investigate why some apps works for me with the ezx-qws and some
doesn't.. and we should check why we get different results