Hosting MkEzx binary images

[fubar]

1- Is "Calendar" stable?

2- Never tried mkexz apps before. Is "Contacts" application supposed to import the original "contacts"? Because it initialized empty.

3- why "to-do" and "contacts" are in the "office" folder and "calendar" is in the "others"? ....sorry...I am just playing with a new toy inside my new toy (my ming).

Most of the applications (other than MkPhone) are from the GPE project, so for these applications I suggest you look at notes provided by the original authors of these applications.

The GPE contacts application has absolutely no knowledge of the EZX contacts, so there is no import function provided. However, writing an import utility should be quite straightforward. GPE contacts are stored in ~/.gpe/contacts, in the form of an SQLite database, if you want you can transfer this to your PC and manipulate it with the "sqlite" utility, or code that uses the sqlite library.

[fubar]

Overall the GUI is slow and laggy, it takes several minutes to start.

What handset are you using? I too experienced problems on A780, but it works fine on A1200, not sure what's causing this. Maybe something to do with power management?

* Telephony aplication refuses to start, both from launcher and from folder.
* Both terminal, File manager and rest of applications refused to start, but show at least a error window with message "Cannot create ~/.gpe: Operation not permited"

The MkPhone application won't run unless ~/.gpe exists, and I know that error is currently silent, will fix in a later version. It's strange you can't create ~/.gpe, normally /ezxlocal/home/ezx gets mounted onto /home/native to allow you to write to your home directory if you use the .mpkg I provided. Could you possibly check:

a/ what directory is listed as the "ezx" user's home directory in /etc/passwd?
b/ what is the list of mounts ("mount")?

[fubar]

Can this GUI support Chinese?

I am afraid you will run into a lot of problems, because basically the version of glibc on EZX handsets is f*cked up and all multibyte character conversions fail. This is also why currently SMS with non-ascii characters look have problems when MkPhone is running on EZX.

I am currently working on a variant of MkEzx which would run in a chroot. This would enable us to use a proper version of glibc, and from then on Chinese display should not be a problem.

[GreenHorn]

ok i will continue with trying

[CLOVIS KKK]

I made the same changes fubar suggested to intoxicated (adapted to A1200i L4). NOW IT IS WORKING . But, I did not have time to use it.

Could you please give the exact change you made so I can integrate it into MkEzx?

Sure. But I don't have diff/patch here at work, so I will post the entire "\mkezx\mkezx.boot\sbinmkezx-modtool" file for MING R532L4_G_11.40.0FR.

killall: Could not kill pid '97': No such process
killall: Could not kill pid '99': No such process
killall: Could not kill pid '100': No such process
hostname: Host name lookup failure
xauth:  creating new authority file /home/native/.serverauth.392
xauth:  creating new authority file /home/native/.Xauthority
xauth:  creating new authority file /home/native/.Xauthority

_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/(none):0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
Extended Input Devices not yet supported. Impelement it at line 625 in kinput.c

Not sure why killall is giving errors, but I shouldn't worry about it.

The hostname error is to be expected, EZX handsets don't have a valid /etc/hostname, but that's not a problem.

As for the X server warnings, don't worry either, nothing bad there.

I was more worried about the xserver errors. For the "No such process" error, it usually occurs when a script grabs all pid at once and then start to kill then. If it kill a parent/master process before a child/dependant process then when it tries execute the second kill there is no process to kill.
well I think you already know this .

[swifty]

@GreenHorn
>Do I have to flash a new kernel to run mkezx?
you don't need a new kernel it runs on the original phone.
have you followed the steps given by fubar correctly?

@fubar
on A780.

>a/ what directory is listed as the "ezx" user's home directory in /etc/passwd?
EZX:/home/native

>b/ what is the list of mounts ("mount")?
rootfs on / type rootfs (rw)
/dev/root on / type cramfs (rw)
none on /ram type ramfs (rw)
proc on /ram/proc type proc (rw)
/dev/tffsa on /usr/language type cramfs (rw)
/dev/roflash2 on /usr/setup type cramfs (rw)
none on /dev/pts type devpts (rw)
/dev/mtdblock2 on /ezxlocal type vfm (rw,noatime)
/dev/tffsb1 on /diska type vfat (rw)
/dev/mmca1 on /mmc/mmca1 type vfat (rw)
/dev/root on /ram/tmp/realjava type cramfs (rw)
/dev/mtdblock2 on /usr/SYSjava type vfm (rw,noatime)

[GreenHorn]

@swifty

Yes I did what he said. TWO PARTITIONS ON ONE SD-CARD!?
FAT16=100MB , ext2 =394MB! (with Gparted)

tar -xf mkezx-0.9.17pre1-image.tar.bz2 - on the ext2 parttion!

So the root-fs are shown..

Now click on mkezx.desktop and nothing happens..

Telnet into it and run mkezx-boot.sh
And after this it shows me the errors. Kernel not support ext3.

[swifty]

you have missed point 2.

mkfs.ext3 -j /dev/sda2

and the next part is also not correct from you:
tar -C /media/handset -xf mkezx-0.9.17pre1-image.tar.bz2

it takes a long time for the first start.
i hope this helps!

[GreenHorn]

I hope..

I thought that the command will format the partition to ext2?
So I format the card with gparted and thought it´s enough..

Thanks for your time

[CLOVIS KKK]

I hope..

I thought that the command will format the partition to ext2?
So I format the card with gparted and thought it´s enough..

Thanks for your time

mmmm....how did you untared over a unformatted partition? have you mounted that partition?

if not, you have untared over a rootfs's directory.