Hosting MkEzx binary images

[TheSin]

any plans to Xsdl on mkezx ?
why not put mkezx inside a ext2 or ext3 image instead a partition ?

I'm testing mkezx inside a 180mb ext3 image with Xsdl.
I can receive a call when using mkezx. I can shutdown mkezx and return to standard phone environment without loose anything and without restart the phone.

During my tests, swap memory usage reaches 20mb.

Really nice idea though, I really like that method at least for now till the phone app becomes more usable anyhow.

[hata_ph]

wow.....this is great....I would really like to try it.....
but I will wait until the final version is release then will try it out....

is there a official website regarding this?
I try www.mkexz.org but it only show the code.........
I want to keep track of it progress so that when the final release is out I can be the first to know it....

[swifty]

the correct and official website is:
http://www.mkezx.org/

[fubar]

wow.....this is great....I would really like to try it.....
but I will wait until the final version is release then will try it out....

As for any piece of open source software, the only reason for a release to be "final" is the death of the project, so I sincerely hope this will not be the case in the near future! If you want MkEzx to live on, it's time to subscribe to the development mailing list and start submitting patches:

http://lists.jerryweb.org/mailman/listinfo/mkezx

[fubar]

Also is there a way to shutdown the X11 part without needed to turn off the entire phone to return to the motoDesktop?

Killing X11 is straightforward, you kill the "Xfbdev" process and all X11 applications should die.

Restarting Motorola's native UI if it has been killed is quite another story, I have not found any way to do it and sincerely doubt it can be done. The root cause for this is that the framebuffer (display) driver is buggy as hell, and the initialisation code that gets run by Motorola's windowing server crashes the second time it is run!

[ghostwheel]

I once managed to restart the motorola interface by playing around with telinit. Not everything was perfect, though - for example, the battery showed 0%, so eventually I had to shut down and restart the phone. I haven't played around with it much more.

[TheSin]

Also is there a way to shutdown the X11 part without needed to turn off the entire phone to return to the motoDesktop?

Killing X11 is straightforward, you kill the "Xfbdev" process and all X11 applications should die.

Restarting Motorola's native UI if it has been killed is quite another story, I have not found any way to do it and sincerely doubt it can be done. The root cause for this is that the framebuffer (display) driver is buggy as hell, and the initialisation code that gets run by Motorola's windowing server crashes the second time it is run!

right but have you looked at the boot script, it mounts dirs and does a killall on something. So just killing X11 won't put it 100% back. need to umount and restart what ever pid it killed, and start it properly, doesn't sound easy unless you know your way around the phone quiet well, but I'm working on it :P

[epinter]

I made a .mpkg that run the mkezx environment using Xsdl. The EZX environment remains completely untouched, no need to create partitions or kill any programs. The only problem it's memory, swap is required...
The .mpkg is big, but I will try to upload tonight.

Also is there a way to shutdown the X11 part without needed to turn off the entire phone to return to the motoDesktop?

Killing X11 is straightforward, you kill the "Xfbdev" process and all X11 applications should die.

Restarting Motorola's native UI if it has been killed is quite another story, I have not found any way to do it and sincerely doubt it can be done. The root cause for this is that the framebuffer (display) driver is buggy as hell, and the initialisation code that gets run by Motorola's windowing server crashes the second time it is run!

right but have you looked at the boot script, it mounts dirs and does a killall on something. So just killing X11 won't put it 100% back. need to umount and restart what ever pid it killed, and start it properly, doesn't sound easy unless you know your way around the phone quiet well, but I'm working on it :P

[fubar]

@epinter : the whole point of getting X11 to run was to free up memory and provide a clean (EZX-free) environment in which to run X11 apps, so running X on top of EZX doesn't really make sense to me. Also, how is partitioning related to Xsdl versus Kdrive?

[epinter]

the "whole point" don't include testing ?

I will use Xsdl to test funcionality of the environment. I agree that performance can't be compared. Xsdl will be slower than Xfbdev.

Xsdl it's kdrive ... check the xorg source ...
partitioning is not related to X ... I'm trying to simplify the test making a ext3 or ext2 image, so we don't need to partition the sd card to test mkezx.

I will be the first to install mkezx on my phone when it's ready, but, for now, the only thing we can do it's test and contribute.

I believe if we simplify the process, many users will test, not only experienced ones.

@epinter : the whole point of getting X11 to run was to free up memory and provide a clean (EZX-free) environment in which to run X11 apps, so running X on top of EZX doesn't really make sense to me. Also, how is partitioning related to Xsdl versus Kdrive?