Building E680i's native applications is simple, however

[chiennk]

As you know, Motorola did not use Trolltech's Qtopia to build applications for E680i. They use EZX Application on top of Trolltech's embedded Qt. Here is the sofware structure:

EZX Aplication
|
Qt embedded
|
Linux


So building E680i's native applications is simple, things you need:

qt-embedded-2.3.6
E680i's EZX header files
E680i's libezx* libraries
linux-arm-gcc binaries
qvfb (Qt virtual frame buffer)
tmake 1.8

Then you just use qt designer and qvfb (phone's screen simulator)
to develop your qt applications for E680i. Sound is very simple.

Unfortunately, Motorola did not public E680i's EZX header files. Without E680i's EZX header files, we can not use qt designer to build E680i native applications. We will not know how to handle E680i touch screen or sound...
because we dont know ZApplication objects and its function declaration in the header files.


EZX OPIE project team has worked around to build applications for E680i, building E680i applications base on EZX's QtPalmtop without E680i header files.

I believe they are facing the same problem right now. Without knowing E680i's EZX header files, they can not active Opie to support E680i touch screen, sound in their applications!

Why Motorola did not public E680i's EZX header files? If I have E680i header files, my first qt application will be a scientific calculator application support touch screen on E680i. I also believe others will build thousand native applications for E680i.

Why Microsoft and Symbian users can easily build their own native applications for their smartphone? Why Motorola did not want us to build native applications for Linux phone? Why Motorola makes such a lovely open-source Linux phone become closed-source?

I hope one day, Motorola will pay attention to this www.motorolafans.com and read this article. I hope Motorola knows that their fans, their supporters around the world are suffering and facing the problem on building native applications for their linux phones. I hope Motorola will public E680i's header files and release documents on how to use E680i's ZApplication objects and its functionaries.

In conclusion, smartphone on Linux platform can not compare to Symbian's, Palms' or Windows Mobile's, each with thousands of native applications.

I give up my attempt to build E680i native application without Motorola's support. E680i is just a smart phone without support. It is just a phone, no need to spend so much time for it.

We have to sit and wait Motorola China releases new firmwares, new native applications by themself.






This world has six billion people
Suppose, each person eat one animal being per day
Can be more than one per person
Six billion animal being have been killed per day
Just to feed human being day by day

Today, did you eat any animal being?
Before you eat, think about my calculation
Six billion animal being have been suffered today!

[eakrin]

Does EZX library is GPL. i think it's not. EZX library is belong to Sunraisesoft.

[samr7]

Qt Designer? Why would not having headers for libezxappbase or such impede the use of that? There are certain things that the libezxappbase and ZApplication/ZMainWidget classes are very useful for, but it is possible to write straight-up Qt/E applications that are mostly functional and do not link against libezxappbase.

There are a few problems with not using classes from libezxappbase. Sometimes it will fail to load the system font. Your app won't show up in the task manager. Your app won't yield or accept focus like others. Your app's widgets will behave strangely with regard to having the system wallpaper image painted behind them. The system's single-instancing mechanism won't work. The virtual keyboard won't show up when a text input field is highlighted. ZApplication seems to do some secret handshaking in its constructor, and merely replacing the app's QApplication instance with ZApplication seems to fix most of these problems. I believe that a reasonable GUI could be constructed using only ZApplication with the well-documented Qt/E classes.

On top of ZApplication, there are a few other classes that support the EZX look and feel. For example, ZMainWidget is a container widget that provides a main content area with a lower toolbar area, and ZMessageBox supports standard dialog boxes. They're just variations on existing Qt/E ideas, nothing new or complicated.

This all comes from some reverse-engineering work that I did on the A780 libqte among others. Results are posted here:

http://lsb.blogdns.net/ezx-devkit/

This package comes with header files that should provide very good coverage of changes to the Qt library, but not so great coverage of the libezx*.so libraries, at least right now. In particular, this has headers, but scant documentation for:

• Some GUI related components of libezxappbase
• libezxnotification (Notification area / exclamation point menu API)
• libezxqtnapi (Connection manager API)

But none yet for:

• Audio
• Camera
• Bluetooth
• Everything else not mentioned

The fact that Motorola refuses to release some sort of native SDK does not make it impossible to write native apps, it just makes it more difficult. I am a bit curious what you would consider acceptably simple and well-documented. Some sort of manual? Lots of example code? What would it take?

[chiennk]

@eakrin,

Yes, EZX library is not GPL. I am not sure whether it belongs to Sunraisesoft or Motorola.

@samr7,
Before I post this topic, I already exam your unoffical ezx sdk kit. I even leave a comment in your website before I post this topic.

I give up my attempt to develop E680i's native application after I realize that Motorola did not want to support their Linux phone. It is unfair for Linux phone's developers compare to Microsoft and Symbian phone's developers.

Did you know how good Microsoft and Symbian phone's developers can get support from Microsoft and Nokia? They can get SDK and all the documents officially.

Compare to that, what Linux phone's developers get from Motorola? Closed-source, debug and reverse the libraries by ourself without any hope?

Why we need to spend so much time for debug and reverse the libraries without any hope instead of thinking of new ideas and focusing on develop new applications?





These two types of people
are difficult to find in the world.
What two?
One who will do a favour fast
and one who is grateful for a favour done.

[MAPGPS]

Look at this article:
Build native application on E680
It uses the leaked EZX SDK of Motorola A760/A768.

[MAPGPS]

The saw the "reason" why Motorola not public the EZX SDK:
Welte's GnuMonks Blog

[chiennk]

@MAPGPS

Thank for your information. I already know the article "Build native application on E680" before I post this topic.



I have read the article "why Motorola not public the EZX SDK"

<<<
Also, I have received reports that Motorola actually distributes a Linux SDK to selected third party vendors. Parts of those SDK's (the hedaer files for the EZX libraries) have actually leaked, which support the position that there is a SDK.

In many ways, the EZX phones are a combination of a traditional Neptune-based Motorola GSM phone, plus a Linux-based PDA. Therefore, if any native linux apps on the PDA half could influence the 'network health' in a negative way, then any other Neptune based phone could, too.
>>>

Now we can confirm EZX is combination of Neptune-based + Linux-based PDA, no wonder why Motorola is afraid of E680i' EZX header files leak will afftect their Neptune phone, too.

Why did Motorola use their own EZX Application (not free, not GPL) to develop native applications for Linux phones? If they use Qtopia for their linux phones then we can develop plenty of native applications for our phones because Qtopia is free and GPL (if we not use Qtopia for commercial purpose).

I just did an exam on qonsole native application run on my E680i. Surprisingly, this qconsole native appication can support E680i's touch screen, can handle E680i volume up/down buttons. It is likely qonsole used ezx libraries instead of qt embedded libraries.

Do you know who is the author of qonsole native application, which can run properly on E680i? How can I contact him? It seems that he know how to use ezx header files and how to link ezx libraries to write a proper native application for E680i.




Let one control speech and mind
And do no wrong deed with the body.
If the home is well stocked with goods,
Let one have faith, be gentle,
Share his goods with others and speak kindly.

[rpconnect]

@chiennk
with regards to qconsole using ezx-libs vs qt-embedded (standard) libs, you will notice that the keyboard is always there, and is different from the standard ezx keyboard that pops up for native ezx apps.

Also you seem supprised that the touchscreen stuff works, and previously you mentioned:

I believe they are facing the same problem right now. Without knowing E680i's EZX header files, they can not active Opie to support E680i touch screen, sound in their applications!

Have you tried one cyph's opie packages? touchscreen works fine and sound can be made to work, we just need to massage the native soundmanager a bit more. And with cyph's opieproxy there is no problem developing against open-source qt libs (e.g. standard qt-2.3.10), the proxy handles swapping the framebuffer between the native ezx sutff and opie so both can coexist even though they are built against different qt libs.

Attached is an audio analyzer applet that works under Opie. In its beta state it basically just plays a special noise sequence out and then measures the impulse response from the speaker to the mic. (warning, its really beta....)

I had tried to to this same thing with both J2ME and the "native" ezx (using the leaked and reverse engineered native ezx headers) and the Opie option was by far the easiest; the qt-classes/functions are well documented and, unlike the paritally compatable leaked and/or reverse-engineered headers, you know function calls exist and work. For the cleanest possible deployment i'd still prefer to develop apps that work with the native ezx-qt libs, but until I get more experience with both C++ and the changes between standard qte and the ezx stuff, the Opie option is the most well supported, and quick-to-develop option for me.

[MAPGPS]

Do you know who is the author of qonsole native application, which can run properly on E680i? How can I contact him? It seems that he know how to use ezx header files and how to link ezx libraries to write a proper native application for E680i.

The author of qonsole is mcbee from CCMOVE, and the original thread can be found from: (in Chinese)
qonsole - a Console for E680i/A780

[ndpndnt16]

your wish is actually granted
hongkong is giving some free upgrade firmware in motorola service centers....
here is the post by@R1967 in www.whensite.com

#1 E680i HK service center upgrade firmware

To HK E680i user :
之前系其他site, 各大大話自己upgrade firmware; 好似ccmove d 改版 C5ABP 中國移動蕊機版; 會冇左保用..

我之前都自己upgrade左, 但唔鍾意ccmove 中移d開機, icon... 好驚冇左保用...立刻找來C5A4P保鑊..好彩好似系臺版8成同香港firmware一樣, 只有字典吾系金山而系x-live...

2日前有大大話自己去左moto service upgrade (HK) 系C5ABP, 諗住膽粗粗上去試下...冇保用咪走...

一早上去..話等一句鐘..

到機時...話我知已經upgrade左...立刻開機 ...WWW008W ...

得左 C5ABP ...再加個MSN添..

如果有HK E680i user 想要C5ABP HK firmware(之前upgrade左中移版+唔仲意, 可以自己上moto service center試下, 如果怕一開機人地見中移版唔保, 可以up左C5A4P先再上去service center upgrade...

再者, 想問其實有冇辦法clone左個firmware或好系Ghost咁backup成個system...請幫忙...因又想裝software試下E680i威力, 又怕死...嘻嘻

另外..成功轉MP4 25-30fps movie 想分享但唔識響呢度加插圖..可否告之..謝謝

一定要backup d 野..up完冇曬phone book 同message

[ Last edited by R1967 on 2006-1-4 at 02:49 ]

its chinese but kinda useful for hk users
i wish they will still continue the seminar about moto e680i applications
next time i will go