Maemo Wiki Mirror - User contributions [en]

Ovi Store publishing

2010-02-20T18:12:33Z

88.113.140.230: /* QA issues with existing produkts */

http://store.ovi.com/ will support Maemo soon.

== Discussion ==
The official place to discuss Ovi publishing related topics is in the [http://discussion.forum.nokia.com/forum/forumdisplay.php?f=202 related Forum Nokia discussion board].

* Discuss and vote the Brainstorm proposal: [http://maemo.org/community/brainstorm/view/open_source_software_distributed_via_store-ovi-com/ Open source software distributed via store.ovi.com]
* Other Talk threads:
** [http://talk.maemo.org/showthread.php?t=34783 Confirmed/CAUTION: N900 Ovi Apps require Corporation + $1M USD Corporate General Liability Insurace]
** [http://talk.maemo.org/showthread.php?t=34661 Left high-and-dry by Nokia/Ovi store :(]

== Questions ==
Post here your questions/answers.
* The UK sign-up form Ovi requests a VAT number, but is the Tax ID number acceptable for a company that is not required to be VAT registered? Several posts in the Ovi Publisher forum suggest that the Tax ID number is OK, but it would be useful to have an authoritative answer from Nokia.

* Would it be possible to publish to Ovi directly from Extras, for example with a 'Promote to Ovi' mechanism (akin to 'Promote to Extras') ?

* Is Ovi going to have separate policies (liability, waivers, insurance, etc) for OSS projects compared to the current, commercial entity oriented policies ?

* What are the Ovi QA/testing requirements for Maemo devices ?

* Will publishing of Free (libre) applications to Ovi require a registration fee ?

== QA issues with existing produkts ==

If you find Ovi Store content which has serious bugs or is not compatible with the N900 please post details below...

Casper27
* WikiHow survival kit uses 5.4mb qt-webkit library dependency which is not optified.Also it cannot be installed when emelfm2 utility is installed.

--> Urho Konttori@ Nokia: PR1.2 will come with qt4.6 which will include qt-webkit. I would recomend developing your app on top of the extras-devel version of qt4.6 and releasing it after PR1.2 goes out.

*Happy Birthday Sis Pt 35 - MMS in N900 ovi store. In case Nokia dont realise the N900 does not support MMS out of the box.

* Publisher MojosMobile offers DRM protected audio books (file name ending in "dm") in a price range from €0,90 to €19,99. The Ovi Store team is aware that these files won't play on the N900 but they keep adding new ones. Why? [[User:ossi1967|ossi1967]]

Maemo 5/PR1.1.1

2010-02-16T19:30:58Z

88.113.140.230: /* locales */

Maemo 5 PR1.1.1 is being released on February 16, 2010.

This update can be installed over the air. Below you will find additional technical details.

The Maemo 5 SDK and tools were not updated as this is just a minor release.

There are reports that at least 42MB of free rootfs is needed for the update.

== Included packages ==
apt
apt-transport-https
cmt-firmware-rx51
connui-conndlgs
flasher
hildon-application-manager
icd2
libas-protocol-0
libconbtui0
libconnui
libgles2-sgx-img
libicd2
librtcom-call-ui0
locale-resolver-data
Maemo5
nolo
opengles-sgx-img-common
operator-wizard-settings
osso-accounts-plugin-skype
osso-applet-lanuageregional
osso-wlan
posix-locales
rtcom-call-ui
tablet-browser-controls
tablet-browser-daemon
tablet-browser-ui
tablet-browser-view
wl1251-firmware

=== Application manager ===
* Disables apt-get from installing ovi store content
* Enables .deb installation from file manager/browser/email/whatnot

=== locales ===
* Adds roughly 18 new regions

=== OpenGL 1.x ===
Passes conformity tests, so can be used for full blown game development.

== Community reports fixed ==

=== Browser ===
* [https://bugs.maemo.org/show_bug.cgi?id=5684 History images do not match actual URLs under them]
* [https://bugs.maemo.org/show_bug.cgi?id=8385 New browser windows contents are not updated when page loads in background]

=== Connectivity ===
* [https://bugs.maemo.org/show_bug.cgi?id=6416 Wifi won't connect until rebooted...]
* [https://bugs.maemo.org/show_bug.cgi?id=6699 Vodafone Italy: Wrong APN is autoconfigured]

=== Core ===
* [https://bugs.maemo.org/show_bug.cgi?id=6816 OpenGL ES 1.1 should be supported]

=== Settings and Maintenance ===
* [https://bugs.maemo.org/show_bug.cgi?id=6153 apt-get segfaults when system has ran out of ptys]

=== System software ===
* [https://bugs.maemo.org/show_bug.cgi?id=6615 Battery Dies Under 6 Hours with Very Moderate Use (Static IP?)]

=== Telephony ===
* [https://bugs.maemo.org/show_bug.cgi?id=7757 wrong cmt-firmware-rx51 (cell modem) version in published firmware?]

[[Category:fremantle]][[Category:N900]][[Category:Firmware_Upgrade]]

Maemo 5/PR1.1.1

2010-02-16T19:21:20Z

88.113.140.230: /* locales */

Maemo 5 PR1.1.1 is being released on February 16, 2010.

This update can be installed over the air. Below you will find additional technical details.

The Maemo 5 SDK and tools were not updated as this is just a minor release.

There are reports that at least 42MB of free rootfs is needed for the update.

== Included packages ==
apt
apt-transport-https
cmt-firmware-rx51
connui-conndlgs
flasher
hildon-application-manager
icd2
libas-protocol-0
libconbtui0
libconnui
libgles2-sgx-img
libicd2
librtcom-call-ui0
locale-resolver-data
Maemo5
nolo
opengles-sgx-img-common
operator-wizard-settings
osso-accounts-plugin-skype
osso-applet-lanuageregional
osso-wlan
posix-locales
rtcom-call-ui
tablet-browser-controls
tablet-browser-daemon
tablet-browser-ui
tablet-browser-view
wl1251-firmware

=== Application manager ===
* Disables apt-get from installing ovi store content
* Enables .deb installation from file manager/browser/email/whatnot

=== locales ===
* Adds roughly 18 new regions

== Community reports fixed ==

=== Browser ===
* [https://bugs.maemo.org/show_bug.cgi?id=5684 History images do not match actual URLs under them]
* [https://bugs.maemo.org/show_bug.cgi?id=8385 New browser windows contents are not updated when page loads in background]

=== Connectivity ===
* [https://bugs.maemo.org/show_bug.cgi?id=6416 Wifi won't connect until rebooted...]
* [https://bugs.maemo.org/show_bug.cgi?id=6699 Vodafone Italy: Wrong APN is autoconfigured]

=== Core ===
* [https://bugs.maemo.org/show_bug.cgi?id=6816 OpenGL ES 1.1 should be supported]

=== Settings and Maintenance ===
* [https://bugs.maemo.org/show_bug.cgi?id=6153 apt-get segfaults when system has ran out of ptys]

=== System software ===
* [https://bugs.maemo.org/show_bug.cgi?id=6615 Battery Dies Under 6 Hours with Very Moderate Use (Static IP?)]

=== Telephony ===
* [https://bugs.maemo.org/show_bug.cgi?id=7757 wrong cmt-firmware-rx51 (cell modem) version in published firmware?]

[[Category:fremantle]][[Category:N900]][[Category:Firmware_Upgrade]]

Maemo 5/PR1.1.1

2010-02-16T19:21:02Z

88.113.140.230: /* Community reports fixed */

Maemo 5 PR1.1.1 is being released on February 16, 2010.

This update can be installed over the air. Below you will find additional technical details.

The Maemo 5 SDK and tools were not updated as this is just a minor release.

There are reports that at least 42MB of free rootfs is needed for the update.

== Included packages ==
apt
apt-transport-https
cmt-firmware-rx51
connui-conndlgs
flasher
hildon-application-manager
icd2
libas-protocol-0
libconbtui0
libconnui
libgles2-sgx-img
libicd2
librtcom-call-ui0
locale-resolver-data
Maemo5
nolo
opengles-sgx-img-common
operator-wizard-settings
osso-accounts-plugin-skype
osso-applet-lanuageregional
osso-wlan
posix-locales
rtcom-call-ui
tablet-browser-controls
tablet-browser-daemon
tablet-browser-ui
tablet-browser-view
wl1251-firmware

=== Application manager ===
* Disables apt-get from installing ovi store content
* Enables .deb installation from file manager/browser/email/whatnot

=== locales ===
- Adds roughly 18 new regions

== Community reports fixed ==

=== Browser ===
* [https://bugs.maemo.org/show_bug.cgi?id=5684 History images do not match actual URLs under them]
* [https://bugs.maemo.org/show_bug.cgi?id=8385 New browser windows contents are not updated when page loads in background]

=== Connectivity ===
* [https://bugs.maemo.org/show_bug.cgi?id=6416 Wifi won't connect until rebooted...]
* [https://bugs.maemo.org/show_bug.cgi?id=6699 Vodafone Italy: Wrong APN is autoconfigured]

=== Core ===
* [https://bugs.maemo.org/show_bug.cgi?id=6816 OpenGL ES 1.1 should be supported]

=== Settings and Maintenance ===
* [https://bugs.maemo.org/show_bug.cgi?id=6153 apt-get segfaults when system has ran out of ptys]

=== System software ===
* [https://bugs.maemo.org/show_bug.cgi?id=6615 Battery Dies Under 6 Hours with Very Moderate Use (Static IP?)]

=== Telephony ===
* [https://bugs.maemo.org/show_bug.cgi?id=7757 wrong cmt-firmware-rx51 (cell modem) version in published firmware?]

[[Category:fremantle]][[Category:N900]][[Category:Firmware_Upgrade]]

QML

2009-12-14T19:24:52Z

88.113.140.230: /* Conclusion */

[[Category:Qt]]
[[Category:Development]]
== QML on N900 ==

=== Introduction ===
QML is the latest experimental feature based on Qt 4.6. If you don't know QML yet, probably you would like to look at demo [http://labs.trolltech.com/blogs/2009/11/04/qt-declarative-binaries/ here].

It's a Javascript like language and allow you to build your own application rapidly. And yes, you don't need to really care about your development platform too much. All you need to do is using QmlViewer to examine your code. That's pretty much the same when you run on the device (though might be slightly different because of resolution and performance. And note that currently it's still highly experimental!)

=== Building Qt 4.6 with QML ===
To build Qt with QML support on N900, you need a 32-bit Linux box (better choice is Ubuntu, I am using Karmic, but you can use other versions as well).

I assumed you already have Maemo SDK running (also Nokia closed binary with SGX). Now it's time to download [http://qt.gitorious.org/+qt-kinetic-developers/qt/kinetic/commits/kinetic-declarativeui Qt-declarative UI branch].

Once you unpack it within your scratchbox, say ''~/qt-kinetic'', create a build directory anywhere you like, e.g.: ''~/qt-build'', then do the following within scratchbox:

# Execute <code> export PKG_CONFIG_PATH=/usr/lib/pkgconfig; export PKG_CONFIG_SYSROOT=/ </code>
# Edit ''~/qt-kinetic/mkspecs/common/g++.conf'', and remove <code> -fvisibility=hidden -fvisibility-inlines-hidden</code>, otherwise qemu would crash during compiling.
# Configure Qt with <code>~/qt-kinetic/configure -platform linux-g++ -release -opengl es -webkit -force-pkg-config --prefix=/opt/qt</code>
# <code>make</code>
# <code>make install</code>

It will take a whole day to compile this sexy devil. Make sure you have brewed the coffee. In case of running into linking problem (or you have trouble to pass EGL test), please try <code>export SUBLIBS='-lX11 -lXau -lEGL -lGLESv2 ...'</code>, throwing whatever GCC complains what's missing (I left my laptop in the office, forgive me I am typing this in my plain memory).

Now, you should have the Qt 4.6 DUI binary sitting in your scratchbox. You can either copy those binaries under ''/opt/qt'' to your device or mount it as NFS.

=== Test Run on Device ===
On this stage, you should be able to write your first QML application.

<code><pre><nowiki>
#include <QtGui/QApplication>
#include <QmlView>
#include <QUrl>
#include <QGLWidget>

int main(int argc, char *argv[])
{
QApplication a(argc, argv);

QmlView *canvas = new QmlView;
QGLFormat format = QGLFormat::defaultFormat();
format.setSampleBuffers(false);
QGLWidget *glWidget = new QGLWidget(format); // make QmlView use OpenGL ES2 backend.
glWidget->setAutoFillBackground(false);
canvas->setViewport(glWidget);
canvas->setUrl(QUrl::fromLocalFile("/home/user/demos/declarative/flickr/flickr-desktop.qml")); // wherever your qml file is.
canvas->execute();
canvas->show();

return a.exec();
}</nowiki></pre></code>

Then you will see the program running as same as this [http://labs.trolltech.com/blogs/2009/05/13/qt-declarative-ui/ demo].

Some screenshots running on N900:

[[Image:Screenshot1.png|400px]]
[[Image:Screenshot2.png|400px]]
[[Image:Screenshot3.png|400px]]

=== Conclusion ===

Finally, here are some few notices / limitation of current Qt4.6-QML:
* Performance is not that great yet. You may suffer some tearing issues. Write your Qt app in full screen mode will give you some boost. Another alternative is turning off hildon-desktop (gives you 40-50 fps on the device):
$ dsmetool -k /usr/bin/hildon-desktop
To turn back on:
$ dsmetool -t /usr/bin/hildon-desktop
* On PR1.1 and onwards all fullscreen applications are automatically non-composited, so no trickery like the above is needed on N900 once that drops to end users devices.
* Document is bundle inside the source tree. Execute the following command will generate proper document for you:
$ make docs
* <code>-webkit</code> may crash your qmlviewer under N900 if you wish to try. That's why I wrote the code with QmlView binding. If you want to play with qmlviewer, please remove <code>-webkit</code> from your configuration.
* All credits go to Qt team. Thanks for their help on technical support. If you have any questions / comments, please don't hesitate to visit [http://labs.trolltech.com/page/Projects/Graphics/Kinetic QML Team] and give response.
* Happy hacking!

Installing applications

2009-11-11T21:03:11Z

88.113.140.230: /* .debs */

One of the major strengths of the tablets are their expandability. There are all sorts of 3rd party applications and packages available to users, and a variety of ways to get ahold of these packages and install them.

== Repositories ==

The preferred method for installing most packages is from repositories through the Application manager. The primary (and recommended) repository for most of these packages is [[Extras]]. Once a repository is added to your application catalog in Application manager, you will see the packages from that repository listed in Application manager's package list and can install them directly from there.

== .installs ==

.install files are provided in many places as a way to install applications directly from the browser using Application manager. [http://downloads.maemo.org/ Downloads] is a good example of this (the green arrows are .install files). Most of these .installs simply tell the Application manager to grab a package from a certain repository, and can automatically add repositories to your application catalog if required.

== .debs ==
[http://en.wikipedia.org/wiki/Deb_(file_format) .deb] (short for Debian) is the package format used by Maemo. .deb packages are roughly analogous to OS X's [http://en.wikipedia.org/wiki/.pkg .pkg] or Windows' [http://en.wikipedia.org/wiki/EXE .exe]/[http://en.wikipedia.org/wiki/Windows_Installer .msi] installers. .debs are how almost all packages are delivered, but you usually don't deal with them directly, except when installing locally. Some packages are simply not distributed through repositories, or offered separately as .debs (which you may prefer for whatever reason).

You can install .debs by opening them from the browser, or opening local copies with Application manager. The major disadvantage to installing .debs locally as opposed to installing from a repository is that you wont be automatically notified of updates to the package. Also dependency installation is not automatic.

Installing debs directly does not work anymore in fremantle.

== Console ==

<code>apt</code> and <code>dpkg</code> are the tools for managing packages from the console. These can be used locally through XTerm or remotely through [[SSH]].

=== apt ===

<code>apt</code> generally deals with installing packages from repositories. You can install packages from your repositories by running <code>apt-get install <package name></code>, and apt will attempt to fetch the .deb and all of its dependencies and install them. You can then remove packages by running <code>apt-get remove <package name></code>. To search the available packages from your repositories, simply run <code>apt-cache search <search string></code> and it will display a list of matching packages.

=== dpkg ===

<code>dpkg</code> is generally used for installing local .deb files directly, which can be done by running a <code>dpkg -i <local .deb></code> with a local .deb.

== Troubleshooting ==

There are a variety of ways the application installation process can fail, only the common ones are outlined here. Application manager keeps a log of recent activity that's available in the menu (Menu -> Tools -> Log...) which may help you in diagnosing problems.

; Unable to download : Typically, when the Application manager instantly complains about not being able to download when you attempt to install applications, this means that your internal flash card is corrupt and set to read-only. This can be fixed by fixing whatever is wrong with the internal card (likely a corrupt filesystem).

== Individual instructions ==

There is a wiki page for individual instructions. It is called [[Install instructions]]. There should be found instructions to every other piece of software that can't be installed by app manager or means above. If the article lacks instructions for some software, please contact the author and ask him to write instructions to wiki and link them to the [[Install instructions]] -page.

[[Category:Users]]
[[Category:HowTo]]
[[Category:Power users]]