MeeGo wiki - User contributions [en]

ARM/N900/GettingStarted

2011-06-20T13:19:27Z

Hanshoi: /* Install Meego image */

= Getting Started =
== Introduction ==
This page helps you getting started with Meego 1.2 Community Edition for N900. Installing Community Edition (CE) on your N900 will nullify your warranty, and is meant for developer use only. Here we introduce the simplest and most recommended way of installing Community Edition on your phone, if you are looking for a different approach then look at the bottom of the page for [[#Alternative_Installations|alternative approaches.]] The recommended installation method will install Meego 1.2 Community Edition as a dual boot with your Maemo 5 fremantle operating system.

''' WARNING: Remember that installing Community Edition (CE) on your N900 will nullify your warranty, and is meant for developer use only. '''

== Install ==
Follow these steps to install Meego 1.2 Community Edition to your N900.
=== Prequisities ===
* N900 with Fremantle PR 1.3
* Linux (for windows & mac, look [[#Alternative_Installations|alternative approaches]])
* MicroSD (4Gb or bigger)
* [[N900#Download_image|Community Edition Image]]
* [[#Uboot_installation|U-Boot]] (on your phone)

'''WARNING: You have to use PR 1.3 version of Fremantle and nothing else '''

=== Uboot installation ===
Uboot is required for booting to Community Edition, or alternatively to your original operating system.

# Enable the maemo.org extras-devel repository, see http://wiki.maemo.org/Extras-devel in your N900.
# Install the 'uboot-pr13' package from 'System' section, of your N900 software center.
# Verify it's installed by restarting your N900. A penguin should show up at startup and U-boot will be mentioned, let it time out and boot into Maemo.

If this intallation didn't work for you, try the [http://wiki.meego.com/ARM/N900/Install/FlashUboot manual installation of U-Boot.]

=== Download image ===
* [http://repository.maemo.org/meego/n900-de/archive/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/mg-handset-armv7nhl-n900-de-sanity-1.1.99.7.20110516.2.DE.2011-05-23.1-mmcblk0p.raw.bz2 Download latest image] (recommended)
* [[N900#Image_releases|Release list.]]
* [http://repository.maemo.org/meego/n900-de/daily/ Latest daily] (unstable)
* [[ARM/Creating_ARM_image_using_MeeGo_Image_Creator|Build your own image.]]

=== Install MeeGo image ===

When inserting the microSD memory card in the card reader, you need to find out what the proper device for the card is. You can also plug the N900 into your computer's USB slot using the package provided cable. Make sure the external microSD card is unmounted, as with most modern linux distributions today it will get auto-mounted if the has a valid filesystem (FAT32 or ExtX). To unmount, you can try this example:
sudo umount /dev/sdX

And use the mount command to determine if/ where it is mounted:
sudo mount (for an example how the microSD would look go [[MountOutput here]].

Finding out the device node can also be done with for example fdisk:
sudo fdisk -l

An example output ('''NOTE: The /dev/sdX is used as an example on your PC this might be also called /dev/mmcblk0, /dev/sdd or something else''')
$ sudo fdisk -l
...
Disk /dev/sdX: 3965 MB, 3965714432 bytes
194 heads, 30 sectors/track, 1330 cylinders
Units = cylinders of 5820 * 512 = 2979840 bytes
Disk identifier: 0x0001ab40

Device Boot Start End Blocks Id System
/dev/sdX1 1 588 1708984 83 Linux

'''NOTE: The .raw image contains the partition table as well. So the image needs to be written to /dev/sdX not /dev/sdX1.'''

After you are 100% sure that the /dev/sdX is the microSD memory card you just inserted in the card reader, you can use for example dd to put the image to the card:
$ sudo dd bs=4096 if='''<raw_image>''' of=/dev/sdX

If you are low on disk space, you can use

$ bzcat <raw_image>.bz2 | sudo dd bs=4096 of=/dev/sdX

to decompress the compressed raw image on the fly without having to unpack it on you computer first. And if you have pv(1) installed, you can add it in between to display the progress (the image is ~ 2GB in size as of 2010-10-04):

$ bzcat <raw_image>.bz2 | pv | sudo dd bs=4096 of=/dev/sdX

The dd does not show any progress until the file is written to the device, so be patient.

dd will output:

328356+0 records in
328356+0 records out
1344946176 bytes (1.3 GB) copied, 105.625 s, 12.7 MB/s

After this, you can insert the card in the N900, and start using Meego Community Edition on your N900.

== Emulate image ==
You can use Meego Community Edition on your computer by emulating it with your chroot. However when using chroot no UI is available, only terminal. Good thing is that all changes you make there will be available for you on your phone.

Install chroot
apt-get install mic2

Insert your MicroSD card with Meego CE in it, and run chroot as a root, having the meego root folder as a parameter.
mic-chroot /media/XXXXXXXXXXXXXX

Now you should have a Meego CE running in one of your terminals. The Meego CE filesystem is also accessible from your linux filesystem, under /media/xxxxxxxxx .

== Alternative install ==
If the recommended way didn't help you, here is a list of alternative installation methods.

{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
|-
!style="border-style: solid; border-width: 0 1px 1px 0"| Topic
!style="border-style: solid; border-width: 0 0 1px 0"| Description
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/MMC|MMC Installation]]
|style="border-style: solid; border-width: 0 0 1px 0"| Installs MeeGo to a external SD card. Windows, Linux, and Mac OS X guides also.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/EMMC| eMMC Installation]]
|style="border-style: solid; border-width: 0 0 1px 0"| Install MeeGo on the internal memory. This will destroy the existing fremantle installation.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/chroot|Chroot install]]
|style="border-style: solid; border-width: 0 0 1px 0"| Chroot install is a way to try out MeeGo by running it on top of Maemo 5 on your N900 device.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/NFS|NFS-Root over usb networking]]
|style="border-style: solid; border-width: 0 0 1px 0"| With NFS-root install you can run MeeGo natively on your N900, without erasing Maemo 5, without flashing or using SD card. Rootfs speed over USB is the downside.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/U-Boot from scratch|Install U-boot from scratch]]
|style="border-style: solid; border-width: 0 0 1px 0"| If you cannot install uboot from Maemo repo, then use this one to get it installed.
|}

== Troubleshooting ==
If you encountered problems with your install, try one of the following.
* Try out one of the alternative and more comprehensive guides at list above.
* Create a question on the FAQ section below.
* [[ARM/N900#I_want_to_help!|Ask a question on our mailing list, or in irc channel.]]

=== FAQ ===

ARM/N900/GettingStarted

2011-06-20T13:00:22Z

Hanshoi: /* Download image */

= Getting Started =
== Introduction ==
This page helps you getting started with Meego 1.2 Community Edition for N900. Installing Community Edition (CE) on your N900 will nullify your warranty, and is meant for developer use only. Here we introduce the simplest and most recommended way of installing Community Edition on your phone, if you are looking for a different approach then look at the bottom of the page for [[#Alternative_Installations|alternative approaches.]] The recommended installation method will install Meego 1.2 Community Edition as a dual boot with your Maemo 5 fremantle operating system.

''' WARNING: Remember that installing Community Edition (CE) on your N900 will nullify your warranty, and is meant for developer use only. '''

== Install ==
Follow these steps to install Meego 1.2 Community Edition to your N900.
=== Prequisities ===
* N900 with Fremantle PR 1.3
* Linux (for windows & mac, look [[#Alternative_Installations|alternative approaches]])
* MicroSD (4Gb or bigger)
* [[N900#Download_image|Community Edition Image]]
* [[#Uboot_installation|U-Boot]] (on your phone)

'''WARNING: You have to use PR 1.3 version of Fremantle and nothing else '''

=== Uboot installation ===
Uboot is required for booting to Community Edition, or alternatively to your original operating system.

# Enable the maemo.org extras-devel repository, see http://wiki.maemo.org/Extras-devel in your N900.
# Install the 'uboot-pr13' package from 'System' section, of your N900 software center.
# Verify it's installed by restarting your N900. A penguin should show up at startup and U-boot will be mentioned, let it time out and boot into Maemo.

If this intallation didn't work for you, try the [http://wiki.meego.com/ARM/N900/Install/FlashUboot manual installation of U-Boot.]

=== Download image ===
* [http://repository.maemo.org/meego/n900-de/archive/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/mg-handset-armv7nhl-n900-de-sanity-1.1.99.7.20110516.2.DE.2011-05-23.1-mmcblk0p.raw.bz2 Download latest image] (recommended)
* [[N900#Image_releases|Release list.]]
* [http://repository.maemo.org/meego/n900-de/daily/ Latest daily] (unstable)
* [[ARM/Creating_ARM_image_using_MeeGo_Image_Creator|Build your own image.]]

=== Install Meego image ===

When inserting the microSD memory card in the card reader, you need to find out what the proper device for the card is. You can also plug the N900 into your computer's USB slot using the package provided cable. Make sure the external microSD card is unmounted, as with most modern linux distributions today it will get auto-mounted if the has a valid filesystem (FAT32 or ExtX). To unmount, you can try this example:
sudo umount /dev/sdX

And use the mount command to determine if/ where it is mounted:
sudo mount (for an example how the microSD would look go [[MountOutput here]].

Finding out the device node can also be done with for example fdisk:
sudo fdisk -l

An example output ('''NOTE: The /dev/sdX is used as an example on your PC this might be also called /dev/mmcblk0, /dev/sdd or something else''')
$ sudo fdisk -l
...
Disk /dev/sdX: 3965 MB, 3965714432 bytes
194 heads, 30 sectors/track, 1330 cylinders
Units = cylinders of 5820 * 512 = 2979840 bytes
Disk identifier: 0x0001ab40

Device Boot Start End Blocks Id System
/dev/sdX1 1 588 1708984 83 Linux

'''NOTE: The .raw image contains the partition table as well. So the image needs to be written to /dev/sdX not /dev/sdX1.'''

After you are 100% sure that the /dev/sdX is the microSD memory card you just inserted in the card reader, you can use for example dd to put the image to the card:
$ sudo dd bs=4096 if='''<raw_image>''' of=/dev/sdX

If you are low on disk space, you can use

$ bzcat <raw_image>.bz2 | sudo dd bs=4096 of=/dev/sdX

to decompress the compressed raw image on the fly without having to unpack it on you computer first. And if you have pv(1) installed, you can add it in between to display the progress (the image is ~ 2GB in size as of 2010-10-04):

$ bzcat <raw_image>.bz2 | pv | sudo dd bs=4096 of=/dev/sdX

The dd does not show any progress until the file is written to the device, so be patient.

dd will output:

328356+0 records in
328356+0 records out
1344946176 bytes (1.3 GB) copied, 105.625 s, 12.7 MB/s

After this, you can insert the card in the N900, and start using Meego Community Edition on your N900.

== Emulate image ==
You can use Meego Community Edition on your computer by emulating it with your chroot. However when using chroot no UI is available, only terminal. Good thing is that all changes you make there will be available for you on your phone.

Install chroot
apt-get install mic2

Insert your MicroSD card with Meego CE in it, and run chroot as a root, having the meego root folder as a parameter.
mic-chroot /media/XXXXXXXXXXXXXX

Now you should have a Meego CE running in one of your terminals. The Meego CE filesystem is also accessible from your linux filesystem, under /media/xxxxxxxxx .

== Alternative install ==
If the recommended way didn't help you, here is a list of alternative installation methods.

{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
|-
!style="border-style: solid; border-width: 0 1px 1px 0"| Topic
!style="border-style: solid; border-width: 0 0 1px 0"| Description
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/MMC|MMC Installation]]
|style="border-style: solid; border-width: 0 0 1px 0"| Installs MeeGo to a external SD card. Windows, Linux, and Mac OS X guides also.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/EMMC| eMMC Installation]]
|style="border-style: solid; border-width: 0 0 1px 0"| Install MeeGo on the internal memory. This will destroy the existing fremantle installation.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/chroot|Chroot install]]
|style="border-style: solid; border-width: 0 0 1px 0"| Chroot install is a way to try out MeeGo by running it on top of Maemo 5 on your N900 device.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/NFS|NFS-Root over usb networking]]
|style="border-style: solid; border-width: 0 0 1px 0"| With NFS-root install you can run MeeGo natively on your N900, without erasing Maemo 5, without flashing or using SD card. Rootfs speed over USB is the downside.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/U-Boot from scratch|Install U-boot from scratch]]
|style="border-style: solid; border-width: 0 0 1px 0"| If you cannot install uboot from Maemo repo, then use this one to get it installed.
|}

== Troubleshooting ==
If you encountered problems with your install, try one of the following.
* Try out one of the alternative and more comprehensive guides at list above.
* Create a question on the FAQ section below.
* [[ARM/N900#I_want_to_help!|Ask a question on our mailing list, or in irc channel.]]

=== FAQ ===

N900

2011-06-20T12:59:54Z

Hanshoi: /* Image releases */

N900

2011-06-20T12:59:17Z

Hanshoi:

ARM/N900

2011-06-20T12:54:43Z

Hanshoi: /* MeeGo 1.2 Community Edition for Nokia N900 */

= MeeGo 1.2 Community Edition for Nokia N900=

'''What's hot:'''
Test the '''MeeGoConf/SF release''' of the MeeGo 1.2 Developer Edition for N900: [http://repository.maemo.org/meego/n900-de/archive/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ download] - [[ARM/N900/GettingStarted|install]] - [[ARM/N900/CoolStuff|cool stuff]] - [http://forum.meego.com/forumdisplay.php?f=7 discuss]
Read the review by Nathan Willis ([http://lwn.net/SubscriberLink/445703/ec074038295f3d0f/ lwn.net])

== Introduction ==
The target of this activity is to make a Community Edition of MeeGo for the Nokia N900 device. '''Note: initiative was originally called Developer Edition, so you will see that mentioned in many places'''. Don't get confused, this is the same thing :)

The Community Edition is an 'overlay' constructed above the current core MeeGo 1.2. The Community Edition project is working as a draft of a MeeGo handset image, to make possible the MeeGo development on your N900 hardware. Being a draft it will not take into account all features commonly present in a handset OS. To see what features will be implemented look [[#Key_features]]. Flashed with this edition N900 will be usable as a primary phone device for a developer/hacker person. '''This is not meant for regular (Maemo 5) users. Using this release will probably void any warranty and there is no (other than community-based) support available.'''

=== Target ===
The focus is on meeting the non-functional targets (such as performance) rather than number of features. This will hopefully encourage more people to use MeeGo on N900, and continue enhancing the functionality or build new stuff. Community Edition is based on MeeGo 1.2 handset trunk content, and selected community contributions ([[ARM/N900/CoolStuff|see the candidates]]). Core MeeGo 1.2 Handset features can be found in [https://bugs.meego.com/report.cgi?x_axis_field=product&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=MeeGo+Features&product=MeeGo+Core+OS+Features&product=MeeGo+Handset+Features&version=1.0&version=1.1&version=1.2&version=1.0&version=1.1&version=1.2&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=ACCEPTED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bug_id_type=anyexact&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= featurezilla], and features of the Community Edition not yet implemented from [[ARM/N900/Configuration|Configuration list.]]

== Key features ==
These use cases shall be the prominent ones in the Community Edition. (If you want to promote a feature to this list, please add it to the feedback section first.)

'''Cellular voice calls''' (Dialer, People)

* Make voice calls (input number directly, initiate from Contacts, initiate from Call history)
* Receive calls
* Default ringtone plays
* Volume control works via System UI
* SIM PIN entry support

'''SMS''' (SMS, People)
* Send new SMS (input number, send from Contacts)
* Receive SMS, and reply to sender

'''Browser use over WLAN''' (Browser, Settings)
* Able to connect to WLAN AP (with security etc.)
* Open a complex modern website (eg. gmail.com)

'''Camera''' (meegocamera)
* Still image capture
* Support for N900 keys (zoom, capture)

'''Common SW''' (Settings, xterm, lock)

Common components such as System UI, Home screen etc. shall be made functional so that basic device usage is smooth and fast. N900 device specific features such as keys, display and battery will be optimized. [[SDK|MeeGo SDK]] fully supports this edition, as it is MeeGo 1.2 compliant.

== Status ==
The maturity of Community Edition image, can be seen from the [[ARM/N900/Status|Status page.]]

== Installing and running ==
Image download and installing instructions can be found from [[ARM/N900/GettingStarted|Getting Started page,]] please refer to them for more instructions.

* [[ARM/N900/GettingStarted|Download and install]] instructions page.
* [[ARM/N900/Status|Status and reports]] of the latest image.
* [[ARM/N900/CoolStuff|Applications and accessories]] for the Community Edition.

== Release schedule ==

This shows the '''release schedule''' and content. It should be understood that Community Edition is still based on "best-effort" model, so this might change any time. If you want to make sure targets are kept, please join the project and help us. For more detailed list of features that are implemented on the releases, look in the [[ARM/N900/Configuration|Configuration page.]]

{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
|-
!style="border-style: solid; border-width: 0 1px 1px 0"| Release
!style="border-style: solid; border-width: 0 1px 1px 0"| Date
!style="border-style: solid; border-width: 0 1px 1px 0"| Description
!style="border-style: solid; border-width: 0 0 1px 0"| Main Features
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| Summer Release
|style="border-style: solid; border-width: 0 1px 1px 0"| 22.6.2011
|style="border-style: solid; border-width: 0 1px 1px 0"| 1H/2011 achievement
|style="border-style: solid; border-width: 0 0 1px 0"| [[ARM/N900/Summer_Release|link]]
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ MeeGo Conference Release]
|style="border-style: solid; border-width: 0 1px 1px 0"| 23.5.2011
|style="border-style: solid; border-width: 0 1px 1px 0"| MeeGo Conference release
|style="border-style: solid; border-width: 0 0 1px 0"| [[ARM/N900/Configuration#Meego_Conference_Release|link]]
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.1.99.2.20110412.6.DE.2011-04-15.1/images/mg-handset-armv7nhl-n900-de-acceptance/ Alpha release]
|style="border-style: solid; border-width: 0 1px 1px 0"| 15.04.2011
|style="border-style: solid; border-width: 0 1px 1px 0"| Alpha release of the MeeGo Developer Edition image.
|style="border-style: solid; border-width: 0 0 1px 0"| [[ARM/N900/Configuration#Alpha_Release|Calls, SMS, Browser and Camera.]]
|-
|}

== I want to help! ==
Willing to contribute the code to MeeGo, but wondering where to start from? Learn the ropes from the MeeGo experts! This [[Media:Meegokickoff.pdf|material (meego developer's journey)]] gives the overview on the daily development workflow.

Some more concrete steps:

* To contribute fixes see [[ARM/N900/ReleaseProcess]].
* Follow Discussion
** Join [http://lists.meego.com/listinfo/meego-porting meego-porting@meego.com] and [http://lists.meego.com/listinfo/meego-handset meego-handset@meego.com] mailing lists
** Hang out in [http://webchat.freenode.net/?channels=#meego-arm #meego-arm IRC channel on irc.freenode.net]
** Join [[ARM/N900/Meetings|weekly team meetings]] are held in the public IRC. This meeting is registered on the [[MeeGo-Meeting_IRC_Schedule|MeeGo IRC Meeting Page]]. The agenda and the archives are also available.
* Learn
** Play a little with Tablet UX pre-alpha as it's possible the same applications will be replacing some of the Handset UX ones. Experiments are being tried with the Tablet UX on N900. Find more details on [[ARM/N900/TabletUX]].
** Look into learning QML if you haven't already.
*Contribute
** Would like to contribute the test cases? You will find the useful information [[Quality|here]].
** Would like to contribute artwork? See [[ARM/N900/Artwork]].
** To the [[ARM/N900/Performance|performance optimization]].
** Follow [http://qa-reports.meego.com/1.2/Handset/Acceptance/N900 acceptance testing reports] and see if there's anything of your interest you'd like to work on.
* Look through [[ARM/N900/Developers|Developers page,]] for tips and tricks.

== Organization ==
Core team, of Community Edition, is formed in and around Nokia. In addition to core team, we hope to see growing community working on this. There is something for everybody to contribute be it bugs, code, artwork or something else. Core team itself has been divided into following categories:

* Scrum master: [http://meego.com/users/msugano Makoto Sugano]
** [[ARM/N900/Performance|UX & Performance]] team lead: [http://meego.com/users/vesku Vesa-Matti Hartikainen]
** [[ARM/N900/Common|Adaptation]] team lead: [http://meego.com/users/harrihakulinen Harri Hakulinen]. **
** [[ARM/N900/CoolStuff|Applications]] facilitator: [http://meego.com/users/jukkaeklund Jukka Eklund]
** [[ARM/N900/ReleaseProcess|Release & integration]]: [http://meego.com/users/sage Marko Saukko].
* [[ARM/N900/QA|QA]]: [http://meego.com/users/jkunnari Jake Kunnari], [http://meego.com/users/jaritah Jari Tahvanainen], [http://meego.com/users/markraja Marko Rajala]
* Community manager: [http://meego.com/users/jukkaeklund Jukka Eklund]

<nowiki>*</nowiki>The Dialer project has been merged with the MeeGo mainstream [[Project/Dialer|Dialer project.]] 
<nowiki>**</nowiki>Includes the [[ARM/N900/HW_Adaptation_team|Hardware Adaptation]] (maintained by [http://meego.com/users/stskeeps Carsten Munk]).

== FAQ ==

Q. Let's assume my bug fix was accepted only in the Community Edition, but rejected in the official 1.2. What do we do with the bug? 
A. Submit the fix to 1.3. Change the status to "RESOLVED". Comment that the fix is available in Community Edition & 1.3.

Q. Which SD card should I be using? 
A. Class 6 and higher. The class has the impact on the performance.

Q. Where can I download the N900 Community Edition release? 
A. See [[ARM/N900/GettingStarted|installation instructions]]

Q. What is the UI of Community Edition going to be? 
A. Based on what's available on MeeGo trunk. At the moment we work with the MeeGo 1.1-originated Handset UX and apps. We are evaluating the new tablet-originated UX and apps (see [[ARM/N900/TabletUX]]). This is still to be decided, and there might be even multiple options for the user to select.

Q. If I get "The package integrity check failed." (NOKEY) when trying to zypper install MeeGo 1.2 packages, where can I find the missing keys?[1.6.2011] 
A. (no answer yet)

Q. I installed to eMMC and it's dog-slow? [1.6.2011] 
A. The eMMC currently has a severe performance problem, [https://bugs.meego.com/show_bug.cgi?id=18295 bug #18295]

Q. What is this Community Edition really about? 
A. [[ARM/N900/CE_Factsheet|Check out the reasoning of our Meego CE.]]

== Ideas, feedback etc. ==

Please add stuff to the [[ARM/N900/Ideas|Ideas]] page.

== Reporting bugs against N900 Community Edition ==

Currently there is no special Bugzilla product/component for the N900 Community Edition ([http://twitter.com/jukkaeklund/status/74396393195839488 it's "the same MeeGo"]). According to [http://twitter.com/jukkaeklund/status/74396845920632832 this post] by Jukka, you should:

* File a bug report on [http://bugs.meego.com/ bugs.meego.com]
* Use '''[DE]''' in the summary
* Add the '''N900''' keyword to the bug report

[[File:Splash-developers.png]]

[[Category:N900]]

ARM/N900

2011-06-20T12:52:54Z

Hanshoi: /* FAQ */

= MeeGo 1.2 Community Edition for Nokia N900=

'''What's hot:'''
Test the '''MeeGoConf/SF release''' of the MeeGo 1.2 Developer Edition for N900: [http://repository.maemo.org/meego/n900-de/archive/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ download] - [[#Installing_and_running|install]] - [[ARM/N900/CoolStuff|cool stuff]] - [http://forum.meego.com/forumdisplay.php?f=7 discuss]
Read the review by Nathan Willis ([http://lwn.net/SubscriberLink/445703/ec074038295f3d0f/ lwn.net])

== Introduction ==
The target of this activity is to make a Community Edition of MeeGo for the Nokia N900 device. '''Note: initiative was originally called Developer Edition, so you will see that mentioned in many places'''. Don't get confused, this is the same thing :)

The Community Edition is an 'overlay' constructed above the current core MeeGo 1.2. The Community Edition project is working as a draft of a MeeGo handset image, to make possible the MeeGo development on your N900 hardware. Being a draft it will not take into account all features commonly present in a handset OS. To see what features will be implemented look [[#Key_features]]. Flashed with this edition N900 will be usable as a primary phone device for a developer/hacker person. '''This is not meant for regular (Maemo 5) users. Using this release will probably void any warranty and there is no (other than community-based) support available.'''

=== Target ===
The focus is on meeting the non-functional targets (such as performance) rather than number of features. This will hopefully encourage more people to use MeeGo on N900, and continue enhancing the functionality or build new stuff. Community Edition is based on MeeGo 1.2 handset trunk content, and selected community contributions ([[ARM/N900/CoolStuff|see the candidates]]). Core MeeGo 1.2 Handset features can be found in [https://bugs.meego.com/report.cgi?x_axis_field=product&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=MeeGo+Features&product=MeeGo+Core+OS+Features&product=MeeGo+Handset+Features&version=1.0&version=1.1&version=1.2&version=1.0&version=1.1&version=1.2&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=ACCEPTED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bug_id_type=anyexact&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= featurezilla], and features of the Community Edition not yet implemented from [[ARM/N900/Configuration|Configuration list.]]

== Key features ==
These use cases shall be the prominent ones in the Community Edition. (If you want to promote a feature to this list, please add it to the feedback section first.)

'''Cellular voice calls''' (Dialer, People)

* Make voice calls (input number directly, initiate from Contacts, initiate from Call history)
* Receive calls
* Default ringtone plays
* Volume control works via System UI
* SIM PIN entry support

'''SMS''' (SMS, People)
* Send new SMS (input number, send from Contacts)
* Receive SMS, and reply to sender

'''Browser use over WLAN''' (Browser, Settings)
* Able to connect to WLAN AP (with security etc.)
* Open a complex modern website (eg. gmail.com)

'''Camera''' (meegocamera)
* Still image capture
* Support for N900 keys (zoom, capture)

'''Common SW''' (Settings, xterm, lock)

Common components such as System UI, Home screen etc. shall be made functional so that basic device usage is smooth and fast. N900 device specific features such as keys, display and battery will be optimized. [[SDK|MeeGo SDK]] fully supports this edition, as it is MeeGo 1.2 compliant.

== Status ==
The maturity of Community Edition image, can be seen from the [[ARM/N900/Status|Status page.]]

== Installing and running ==
Image download and installing instructions can be found from [[ARM/N900/GettingStarted|Getting Started page,]] please refer to them for more instructions.

* [[ARM/N900/GettingStarted|Download and install]] instructions page.
* [[ARM/N900/Status|Status and reports]] of the latest image.
* [[ARM/N900/CoolStuff|Applications and accessories]] for the Community Edition.

== Release schedule ==

This shows the '''release schedule''' and content. It should be understood that Community Edition is still based on "best-effort" model, so this might change any time. If you want to make sure targets are kept, please join the project and help us. For more detailed list of features that are implemented on the releases, look in the [[ARM/N900/Configuration|Configuration page.]]

{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
|-
!style="border-style: solid; border-width: 0 1px 1px 0"| Release
!style="border-style: solid; border-width: 0 1px 1px 0"| Date
!style="border-style: solid; border-width: 0 1px 1px 0"| Description
!style="border-style: solid; border-width: 0 0 1px 0"| Main Features
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| Summer Release
|style="border-style: solid; border-width: 0 1px 1px 0"| 22.6.2011
|style="border-style: solid; border-width: 0 1px 1px 0"| 1H/2011 achievement
|style="border-style: solid; border-width: 0 0 1px 0"| [[ARM/N900/Summer_Release|link]]
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ MeeGo Conference Release]
|style="border-style: solid; border-width: 0 1px 1px 0"| 23.5.2011
|style="border-style: solid; border-width: 0 1px 1px 0"| MeeGo Conference release
|style="border-style: solid; border-width: 0 0 1px 0"| [[ARM/N900/Configuration#Meego_Conference_Release|link]]
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.1.99.2.20110412.6.DE.2011-04-15.1/images/mg-handset-armv7nhl-n900-de-acceptance/ Alpha release]
|style="border-style: solid; border-width: 0 1px 1px 0"| 15.04.2011
|style="border-style: solid; border-width: 0 1px 1px 0"| Alpha release of the MeeGo Developer Edition image.
|style="border-style: solid; border-width: 0 0 1px 0"| [[ARM/N900/Configuration#Alpha_Release|Calls, SMS, Browser and Camera.]]
|-
|}

== I want to help! ==
Willing to contribute the code to MeeGo, but wondering where to start from? Learn the ropes from the MeeGo experts! This [[Media:Meegokickoff.pdf|material (meego developer's journey)]] gives the overview on the daily development workflow.

Some more concrete steps:

* To contribute fixes see [[ARM/N900/ReleaseProcess]].
* Follow Discussion
** Join [http://lists.meego.com/listinfo/meego-porting meego-porting@meego.com] and [http://lists.meego.com/listinfo/meego-handset meego-handset@meego.com] mailing lists
** Hang out in [http://webchat.freenode.net/?channels=#meego-arm #meego-arm IRC channel on irc.freenode.net]
** Join [[ARM/N900/Meetings|weekly team meetings]] are held in the public IRC. This meeting is registered on the [[MeeGo-Meeting_IRC_Schedule|MeeGo IRC Meeting Page]]. The agenda and the archives are also available.
* Learn
** Play a little with Tablet UX pre-alpha as it's possible the same applications will be replacing some of the Handset UX ones. Experiments are being tried with the Tablet UX on N900. Find more details on [[ARM/N900/TabletUX]].
** Look into learning QML if you haven't already.
*Contribute
** Would like to contribute the test cases? You will find the useful information [[Quality|here]].
** Would like to contribute artwork? See [[ARM/N900/Artwork]].
** To the [[ARM/N900/Performance|performance optimization]].
** Follow [http://qa-reports.meego.com/1.2/Handset/Acceptance/N900 acceptance testing reports] and see if there's anything of your interest you'd like to work on.
* Look through [[ARM/N900/Developers|Developers page,]] for tips and tricks.

== Organization ==
Core team, of Community Edition, is formed in and around Nokia. In addition to core team, we hope to see growing community working on this. There is something for everybody to contribute be it bugs, code, artwork or something else. Core team itself has been divided into following categories:

* Scrum master: [http://meego.com/users/msugano Makoto Sugano]
** [[ARM/N900/Performance|UX & Performance]] team lead: [http://meego.com/users/vesku Vesa-Matti Hartikainen]
** [[ARM/N900/Common|Adaptation]] team lead: [http://meego.com/users/harrihakulinen Harri Hakulinen]. **
** [[ARM/N900/CoolStuff|Applications]] facilitator: [http://meego.com/users/jukkaeklund Jukka Eklund]
** [[ARM/N900/ReleaseProcess|Release & integration]]: [http://meego.com/users/sage Marko Saukko].
* [[ARM/N900/QA|QA]]: [http://meego.com/users/jkunnari Jake Kunnari], [http://meego.com/users/jaritah Jari Tahvanainen], [http://meego.com/users/markraja Marko Rajala]
* Community manager: [http://meego.com/users/jukkaeklund Jukka Eklund]

<nowiki>*</nowiki>The Dialer project has been merged with the MeeGo mainstream [[Project/Dialer|Dialer project.]] 
<nowiki>**</nowiki>Includes the [[ARM/N900/HW_Adaptation_team|Hardware Adaptation]] (maintained by [http://meego.com/users/stskeeps Carsten Munk]).

== FAQ ==

Q. Let's assume my bug fix was accepted only in the Community Edition, but rejected in the official 1.2. What do we do with the bug? 
A. Submit the fix to 1.3. Change the status to "RESOLVED". Comment that the fix is available in Community Edition & 1.3.

Q. Which SD card should I be using? 
A. Class 6 and higher. The class has the impact on the performance.

Q. Where can I download the N900 Community Edition release? 
A. See [[ARM/N900/GettingStarted|installation instructions]]

Q. What is the UI of Community Edition going to be? 
A. Based on what's available on MeeGo trunk. At the moment we work with the MeeGo 1.1-originated Handset UX and apps. We are evaluating the new tablet-originated UX and apps (see [[ARM/N900/TabletUX]]). This is still to be decided, and there might be even multiple options for the user to select.

Q. If I get "The package integrity check failed." (NOKEY) when trying to zypper install MeeGo 1.2 packages, where can I find the missing keys?[1.6.2011] 
A. (no answer yet)

Q. I installed to eMMC and it's dog-slow? [1.6.2011] 
A. The eMMC currently has a severe performance problem, [https://bugs.meego.com/show_bug.cgi?id=18295 bug #18295]

Q. What is this Community Edition really about? 
A. [[ARM/N900/CE_Factsheet|Check out the reasoning of our Meego CE.]]

== Ideas, feedback etc. ==

Please add stuff to the [[ARM/N900/Ideas|Ideas]] page.

== Reporting bugs against N900 Community Edition ==

Currently there is no special Bugzilla product/component for the N900 Community Edition ([http://twitter.com/jukkaeklund/status/74396393195839488 it's "the same MeeGo"]). According to [http://twitter.com/jukkaeklund/status/74396845920632832 this post] by Jukka, you should:

* File a bug report on [http://bugs.meego.com/ bugs.meego.com]
* Use '''[DE]''' in the summary
* Add the '''N900''' keyword to the bug report

[[File:Splash-developers.png]]

[[Category:N900]]

ARM/N900

2011-06-20T12:52:25Z

Hanshoi: /* Installing and running */

= MeeGo 1.2 Community Edition for Nokia N900=

'''What's hot:'''
Test the '''MeeGoConf/SF release''' of the MeeGo 1.2 Developer Edition for N900: [http://repository.maemo.org/meego/n900-de/archive/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ download] - [[#Installing_and_running|install]] - [[ARM/N900/CoolStuff|cool stuff]] - [http://forum.meego.com/forumdisplay.php?f=7 discuss]
Read the review by Nathan Willis ([http://lwn.net/SubscriberLink/445703/ec074038295f3d0f/ lwn.net])

== Introduction ==
The target of this activity is to make a Community Edition of MeeGo for the Nokia N900 device. '''Note: initiative was originally called Developer Edition, so you will see that mentioned in many places'''. Don't get confused, this is the same thing :)

The Community Edition is an 'overlay' constructed above the current core MeeGo 1.2. The Community Edition project is working as a draft of a MeeGo handset image, to make possible the MeeGo development on your N900 hardware. Being a draft it will not take into account all features commonly present in a handset OS. To see what features will be implemented look [[#Key_features]]. Flashed with this edition N900 will be usable as a primary phone device for a developer/hacker person. '''This is not meant for regular (Maemo 5) users. Using this release will probably void any warranty and there is no (other than community-based) support available.'''

=== Target ===
The focus is on meeting the non-functional targets (such as performance) rather than number of features. This will hopefully encourage more people to use MeeGo on N900, and continue enhancing the functionality or build new stuff. Community Edition is based on MeeGo 1.2 handset trunk content, and selected community contributions ([[ARM/N900/CoolStuff|see the candidates]]). Core MeeGo 1.2 Handset features can be found in [https://bugs.meego.com/report.cgi?x_axis_field=product&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=MeeGo+Features&product=MeeGo+Core+OS+Features&product=MeeGo+Handset+Features&version=1.0&version=1.1&version=1.2&version=1.0&version=1.1&version=1.2&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=ACCEPTED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bug_id_type=anyexact&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= featurezilla], and features of the Community Edition not yet implemented from [[ARM/N900/Configuration|Configuration list.]]

== Key features ==
These use cases shall be the prominent ones in the Community Edition. (If you want to promote a feature to this list, please add it to the feedback section first.)

'''Cellular voice calls''' (Dialer, People)

* Make voice calls (input number directly, initiate from Contacts, initiate from Call history)
* Receive calls
* Default ringtone plays
* Volume control works via System UI
* SIM PIN entry support

'''SMS''' (SMS, People)
* Send new SMS (input number, send from Contacts)
* Receive SMS, and reply to sender

'''Browser use over WLAN''' (Browser, Settings)
* Able to connect to WLAN AP (with security etc.)
* Open a complex modern website (eg. gmail.com)

'''Camera''' (meegocamera)
* Still image capture
* Support for N900 keys (zoom, capture)

'''Common SW''' (Settings, xterm, lock)

Common components such as System UI, Home screen etc. shall be made functional so that basic device usage is smooth and fast. N900 device specific features such as keys, display and battery will be optimized. [[SDK|MeeGo SDK]] fully supports this edition, as it is MeeGo 1.2 compliant.

== Status ==
The maturity of Community Edition image, can be seen from the [[ARM/N900/Status|Status page.]]

== Installing and running ==
Image download and installing instructions can be found from [[ARM/N900/GettingStarted|Getting Started page,]] please refer to them for more instructions.

* [[ARM/N900/GettingStarted|Download and install]] instructions page.
* [[ARM/N900/Status|Status and reports]] of the latest image.
* [[ARM/N900/CoolStuff|Applications and accessories]] for the Community Edition.

== Release schedule ==

This shows the '''release schedule''' and content. It should be understood that Community Edition is still based on "best-effort" model, so this might change any time. If you want to make sure targets are kept, please join the project and help us. For more detailed list of features that are implemented on the releases, look in the [[ARM/N900/Configuration|Configuration page.]]

{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
|-
!style="border-style: solid; border-width: 0 1px 1px 0"| Release
!style="border-style: solid; border-width: 0 1px 1px 0"| Date
!style="border-style: solid; border-width: 0 1px 1px 0"| Description
!style="border-style: solid; border-width: 0 0 1px 0"| Main Features
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| Summer Release
|style="border-style: solid; border-width: 0 1px 1px 0"| 22.6.2011
|style="border-style: solid; border-width: 0 1px 1px 0"| 1H/2011 achievement
|style="border-style: solid; border-width: 0 0 1px 0"| [[ARM/N900/Summer_Release|link]]
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ MeeGo Conference Release]
|style="border-style: solid; border-width: 0 1px 1px 0"| 23.5.2011
|style="border-style: solid; border-width: 0 1px 1px 0"| MeeGo Conference release
|style="border-style: solid; border-width: 0 0 1px 0"| [[ARM/N900/Configuration#Meego_Conference_Release|link]]
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.1.99.2.20110412.6.DE.2011-04-15.1/images/mg-handset-armv7nhl-n900-de-acceptance/ Alpha release]
|style="border-style: solid; border-width: 0 1px 1px 0"| 15.04.2011
|style="border-style: solid; border-width: 0 1px 1px 0"| Alpha release of the MeeGo Developer Edition image.
|style="border-style: solid; border-width: 0 0 1px 0"| [[ARM/N900/Configuration#Alpha_Release|Calls, SMS, Browser and Camera.]]
|-
|}

== I want to help! ==
Willing to contribute the code to MeeGo, but wondering where to start from? Learn the ropes from the MeeGo experts! This [[Media:Meegokickoff.pdf|material (meego developer's journey)]] gives the overview on the daily development workflow.

Some more concrete steps:

* To contribute fixes see [[ARM/N900/ReleaseProcess]].
* Follow Discussion
** Join [http://lists.meego.com/listinfo/meego-porting meego-porting@meego.com] and [http://lists.meego.com/listinfo/meego-handset meego-handset@meego.com] mailing lists
** Hang out in [http://webchat.freenode.net/?channels=#meego-arm #meego-arm IRC channel on irc.freenode.net]
** Join [[ARM/N900/Meetings|weekly team meetings]] are held in the public IRC. This meeting is registered on the [[MeeGo-Meeting_IRC_Schedule|MeeGo IRC Meeting Page]]. The agenda and the archives are also available.
* Learn
** Play a little with Tablet UX pre-alpha as it's possible the same applications will be replacing some of the Handset UX ones. Experiments are being tried with the Tablet UX on N900. Find more details on [[ARM/N900/TabletUX]].
** Look into learning QML if you haven't already.
*Contribute
** Would like to contribute the test cases? You will find the useful information [[Quality|here]].
** Would like to contribute artwork? See [[ARM/N900/Artwork]].
** To the [[ARM/N900/Performance|performance optimization]].
** Follow [http://qa-reports.meego.com/1.2/Handset/Acceptance/N900 acceptance testing reports] and see if there's anything of your interest you'd like to work on.
* Look through [[ARM/N900/Developers|Developers page,]] for tips and tricks.

== Organization ==
Core team, of Community Edition, is formed in and around Nokia. In addition to core team, we hope to see growing community working on this. There is something for everybody to contribute be it bugs, code, artwork or something else. Core team itself has been divided into following categories:

* Scrum master: [http://meego.com/users/msugano Makoto Sugano]
** [[ARM/N900/Performance|UX & Performance]] team lead: [http://meego.com/users/vesku Vesa-Matti Hartikainen]
** [[ARM/N900/Common|Adaptation]] team lead: [http://meego.com/users/harrihakulinen Harri Hakulinen]. **
** [[ARM/N900/CoolStuff|Applications]] facilitator: [http://meego.com/users/jukkaeklund Jukka Eklund]
** [[ARM/N900/ReleaseProcess|Release & integration]]: [http://meego.com/users/sage Marko Saukko].
* [[ARM/N900/QA|QA]]: [http://meego.com/users/jkunnari Jake Kunnari], [http://meego.com/users/jaritah Jari Tahvanainen], [http://meego.com/users/markraja Marko Rajala]
* Community manager: [http://meego.com/users/jukkaeklund Jukka Eklund]

<nowiki>*</nowiki>The Dialer project has been merged with the MeeGo mainstream [[Project/Dialer|Dialer project.]] 
<nowiki>**</nowiki>Includes the [[ARM/N900/HW_Adaptation_team|Hardware Adaptation]] (maintained by [http://meego.com/users/stskeeps Carsten Munk]).

== FAQ ==

Q. Let's assume my bug fix was accepted only in the Community Edition, but rejected in the official 1.2. What do we do with the bug? 
A. Submit the fix to 1.3. Change the status to "RESOLVED". Comment that the fix is available in Community Edition & 1.3.

Q. Which SD card should I be using? 
A. Class 6 and higher. The class has the impact on the performance.

Q. Where can I download the N900 Community Edition release? 
A. See [[N900#Install|installation instructions]]

Q. What is the UI of Community Edition going to be? 
A. Based on what's available on MeeGo trunk. At the moment we work with the MeeGo 1.1-originated Handset UX and apps. We are evaluating the new tablet-originated UX and apps (see [[ARM/N900/TabletUX]]). This is still to be decided, and there might be even multiple options for the user to select.

Q. If I get "The package integrity check failed." (NOKEY) when trying to zypper install MeeGo 1.2 packages, where can I find the missing keys?[1.6.2011] 
A. (no answer yet)

Q. I installed to eMMC and it's dog-slow? [1.6.2011] 
A. The eMMC currently has a severe performance problem, [https://bugs.meego.com/show_bug.cgi?id=18295 bug #18295]

Q. What is this Community Edition really about? 
A. [[ARM/N900/CE_Factsheet|Check out the reasoning of our Meego CE.]]

== Ideas, feedback etc. ==

Please add stuff to the [[ARM/N900/Ideas|Ideas]] page.

== Reporting bugs against N900 Community Edition ==

Currently there is no special Bugzilla product/component for the N900 Community Edition ([http://twitter.com/jukkaeklund/status/74396393195839488 it's "the same MeeGo"]). According to [http://twitter.com/jukkaeklund/status/74396845920632832 this post] by Jukka, you should:

* File a bug report on [http://bugs.meego.com/ bugs.meego.com]
* Use '''[DE]''' in the summary
* Add the '''N900''' keyword to the bug report

[[File:Splash-developers.png]]

[[Category:N900]]

ARM/N900/GettingStarted

2011-06-20T12:50:25Z

Hanshoi: /* Prequisities */

= Getting Started =
== Introduction ==
This page helps you getting started with Meego 1.2 Community Edition for N900. Installing Community Edition (CE) on your N900 will nullify your warranty, and is meant for developer use only. Here we introduce the simplest and most recommended way of installing Community Edition on your phone, if you are looking for a different approach then look at the bottom of the page for [[#Alternative_Installations|alternative approaches.]] The recommended installation method will install Meego 1.2 Community Edition as a dual boot with your Maemo 5 fremantle operating system.

''' WARNING: Remember that installing Community Edition (CE) on your N900 will nullify your warranty, and is meant for developer use only. '''

== Install ==
Follow these steps to install Meego 1.2 Community Edition to your N900.
=== Prequisities ===
* N900 with Fremantle PR 1.3
* Linux (for windows & mac, look [[#Alternative_Installations|alternative approaches]])
* MicroSD (4Gb or bigger)
* [[N900#Download_image|Community Edition Image]]
* [[#Uboot_installation|U-Boot]] (on your phone)

'''WARNING: You have to use PR 1.3 version of Fremantle and nothing else '''

=== Uboot installation ===
Uboot is required for booting to Community Edition, or alternatively to your original operating system.

# Enable the maemo.org extras-devel repository, see http://wiki.maemo.org/Extras-devel in your N900.
# Install the 'uboot-pr13' package from 'System' section, of your N900 software center.
# Verify it's installed by restarting your N900. A penguin should show up at startup and U-boot will be mentioned, let it time out and boot into Maemo.

If this intallation didn't work for you, try the [http://wiki.meego.com/ARM/N900/Install/FlashUboot manual installation of U-Boot.]

=== Download image ===
* [http://repository.maemo.org/meego/n900-de/archive/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/mg-handset-armv7nhl-n900-de-sanity-1.1.99.7.20110516.2.DE.2011-05-23.1-mmcblk0p.raw.bz2 Download latest image] (recommended)
* [[N900#Download_image|Release list.]]
* [http://repository.maemo.org/meego/n900-de/daily/ Latest daily] (unstable)
* [[ARM/Creating_ARM_image_using_MeeGo_Image_Creator|Build your own image.]]

=== Install Meego image ===

When inserting the microSD memory card in the card reader, you need to find out what the proper device for the card is. You can also plug the N900 into your computer's USB slot using the package provided cable. Make sure the external microSD card is unmounted, as with most modern linux distributions today it will get auto-mounted if the has a valid filesystem (FAT32 or ExtX). To unmount, you can try this example:
sudo umount /dev/sdX

And use the mount command to determine if/ where it is mounted:
sudo mount (for an example how the microSD would look go [[MountOutput here]].

Finding out the device node can also be done with for example fdisk:
sudo fdisk -l

An example output ('''NOTE: The /dev/sdX is used as an example on your PC this might be also called /dev/mmcblk0, /dev/sdd or something else''')
$ sudo fdisk -l
...
Disk /dev/sdX: 3965 MB, 3965714432 bytes
194 heads, 30 sectors/track, 1330 cylinders
Units = cylinders of 5820 * 512 = 2979840 bytes
Disk identifier: 0x0001ab40

Device Boot Start End Blocks Id System
/dev/sdX1 1 588 1708984 83 Linux

'''NOTE: The .raw image contains the partition table as well. So the image needs to be written to /dev/sdX not /dev/sdX1.'''

After you are 100% sure that the /dev/sdX is the microSD memory card you just inserted in the card reader, you can use for example dd to put the image to the card:
$ sudo dd bs=4096 if='''<raw_image>''' of=/dev/sdX

If you are low on disk space, you can use

$ bzcat <raw_image>.bz2 | sudo dd bs=4096 of=/dev/sdX

to decompress the compressed raw image on the fly without having to unpack it on you computer first. And if you have pv(1) installed, you can add it in between to display the progress (the image is ~ 2GB in size as of 2010-10-04):

$ bzcat <raw_image>.bz2 | pv | sudo dd bs=4096 of=/dev/sdX

The dd does not show any progress until the file is written to the device, so be patient.

dd will output:

328356+0 records in
328356+0 records out
1344946176 bytes (1.3 GB) copied, 105.625 s, 12.7 MB/s

After this, you can insert the card in the N900, and start using Meego Community Edition on your N900.

== Emulate image ==
You can use Meego Community Edition on your computer by emulating it with your chroot. However when using chroot no UI is available, only terminal. Good thing is that all changes you make there will be available for you on your phone.

Install chroot
apt-get install mic2

Insert your MicroSD card with Meego CE in it, and run chroot as a root, having the meego root folder as a parameter.
mic-chroot /media/XXXXXXXXXXXXXX

Now you should have a Meego CE running in one of your terminals. The Meego CE filesystem is also accessible from your linux filesystem, under /media/xxxxxxxxx .

== Alternative install ==
If the recommended way didn't help you, here is a list of alternative installation methods.

{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
|-
!style="border-style: solid; border-width: 0 1px 1px 0"| Topic
!style="border-style: solid; border-width: 0 0 1px 0"| Description
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/MMC|MMC Installation]]
|style="border-style: solid; border-width: 0 0 1px 0"| Installs MeeGo to a external SD card. Windows, Linux, and Mac OS X guides also.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/EMMC| eMMC Installation]]
|style="border-style: solid; border-width: 0 0 1px 0"| Install MeeGo on the internal memory. This will destroy the existing fremantle installation.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/chroot|Chroot install]]
|style="border-style: solid; border-width: 0 0 1px 0"| Chroot install is a way to try out MeeGo by running it on top of Maemo 5 on your N900 device.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/NFS|NFS-Root over usb networking]]
|style="border-style: solid; border-width: 0 0 1px 0"| With NFS-root install you can run MeeGo natively on your N900, without erasing Maemo 5, without flashing or using SD card. Rootfs speed over USB is the downside.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/U-Boot from scratch|Install U-boot from scratch]]
|style="border-style: solid; border-width: 0 0 1px 0"| If you cannot install uboot from Maemo repo, then use this one to get it installed.
|}

== Troubleshooting ==
If you encountered problems with your install, try one of the following.
* Try out one of the alternative and more comprehensive guides at list above.
* Create a question on the FAQ section below.
* [[ARM/N900#I_want_to_help!|Ask a question on our mailing list, or in irc channel.]]

=== FAQ ===

ARM/N900

2011-06-20T12:49:03Z

Hanshoi: /* FAQ */

= MeeGo 1.2 Community Edition for Nokia N900=

'''What's hot:'''
Test the '''MeeGoConf/SF release''' of the MeeGo 1.2 Developer Edition for N900: [http://repository.maemo.org/meego/n900-de/archive/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ download] - [[#Installing_and_running|install]] - [[ARM/N900/CoolStuff|cool stuff]] - [http://forum.meego.com/forumdisplay.php?f=7 discuss]
Read the review by Nathan Willis ([http://lwn.net/SubscriberLink/445703/ec074038295f3d0f/ lwn.net])

== Introduction ==
The target of this activity is to make a Community Edition of MeeGo for the Nokia N900 device. '''Note: initiative was originally called Developer Edition, so you will see that mentioned in many places'''. Don't get confused, this is the same thing :)

The Community Edition is an 'overlay' constructed above the current core MeeGo 1.2. The Community Edition project is working as a draft of a MeeGo handset image, to make possible the MeeGo development on your N900 hardware. Being a draft it will not take into account all features commonly present in a handset OS. To see what features will be implemented look [[#Key_features]]. Flashed with this edition N900 will be usable as a primary phone device for a developer/hacker person. '''This is not meant for regular (Maemo 5) users. Using this release will probably void any warranty and there is no (other than community-based) support available.'''

=== Target ===
The focus is on meeting the non-functional targets (such as performance) rather than number of features. This will hopefully encourage more people to use MeeGo on N900, and continue enhancing the functionality or build new stuff. Community Edition is based on MeeGo 1.2 handset trunk content, and selected community contributions ([[ARM/N900/CoolStuff|see the candidates]]). Core MeeGo 1.2 Handset features can be found in [https://bugs.meego.com/report.cgi?x_axis_field=product&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=MeeGo+Features&product=MeeGo+Core+OS+Features&product=MeeGo+Handset+Features&version=1.0&version=1.1&version=1.2&version=1.0&version=1.1&version=1.2&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=ACCEPTED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bug_id_type=anyexact&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= featurezilla], and features of the Community Edition not yet implemented from [[ARM/N900/Configuration|Configuration list.]]

== Key features ==
These use cases shall be the prominent ones in the Community Edition. (If you want to promote a feature to this list, please add it to the feedback section first.)

'''Cellular voice calls''' (Dialer, People)

* Make voice calls (input number directly, initiate from Contacts, initiate from Call history)
* Receive calls
* Default ringtone plays
* Volume control works via System UI
* SIM PIN entry support

'''SMS''' (SMS, People)
* Send new SMS (input number, send from Contacts)
* Receive SMS, and reply to sender

'''Browser use over WLAN''' (Browser, Settings)
* Able to connect to WLAN AP (with security etc.)
* Open a complex modern website (eg. gmail.com)

'''Camera''' (meegocamera)
* Still image capture
* Support for N900 keys (zoom, capture)

'''Common SW''' (Settings, xterm, lock)

Common components such as System UI, Home screen etc. shall be made functional so that basic device usage is smooth and fast. N900 device specific features such as keys, display and battery will be optimized. [[SDK|MeeGo SDK]] fully supports this edition, as it is MeeGo 1.2 compliant.

== Status ==
The maturity of Community Edition image, can be seen from the [[ARM/N900/Status|Status page.]]

== Installing and running ==
Image download and installing instructions can be found from [[N900#Install|N900 page,]] please refer to them for more instructions.

* [[N900#Install|Download and install]] instructions page.
* [[ARM/N900/Status|Status and reports]] of the latest image.
* [[ARM/N900/CoolStuff|Applications and accessories]] for the Community Edition.

== Release schedule ==

This shows the '''release schedule''' and content. It should be understood that Community Edition is still based on "best-effort" model, so this might change any time. If you want to make sure targets are kept, please join the project and help us. For more detailed list of features that are implemented on the releases, look in the [[ARM/N900/Configuration|Configuration page.]]

{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
|-
!style="border-style: solid; border-width: 0 1px 1px 0"| Release
!style="border-style: solid; border-width: 0 1px 1px 0"| Date
!style="border-style: solid; border-width: 0 1px 1px 0"| Description
!style="border-style: solid; border-width: 0 0 1px 0"| Main Features
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| Summer Release
|style="border-style: solid; border-width: 0 1px 1px 0"| 22.6.2011
|style="border-style: solid; border-width: 0 1px 1px 0"| 1H/2011 achievement
|style="border-style: solid; border-width: 0 0 1px 0"| [[ARM/N900/Summer_Release|link]]
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ MeeGo Conference Release]
|style="border-style: solid; border-width: 0 1px 1px 0"| 23.5.2011
|style="border-style: solid; border-width: 0 1px 1px 0"| MeeGo Conference release
|style="border-style: solid; border-width: 0 0 1px 0"| [[ARM/N900/Configuration#Meego_Conference_Release|link]]
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.1.99.2.20110412.6.DE.2011-04-15.1/images/mg-handset-armv7nhl-n900-de-acceptance/ Alpha release]
|style="border-style: solid; border-width: 0 1px 1px 0"| 15.04.2011
|style="border-style: solid; border-width: 0 1px 1px 0"| Alpha release of the MeeGo Developer Edition image.
|style="border-style: solid; border-width: 0 0 1px 0"| [[ARM/N900/Configuration#Alpha_Release|Calls, SMS, Browser and Camera.]]
|-
|}

== I want to help! ==
Willing to contribute the code to MeeGo, but wondering where to start from? Learn the ropes from the MeeGo experts! This [[Media:Meegokickoff.pdf|material (meego developer's journey)]] gives the overview on the daily development workflow.

Some more concrete steps:

* To contribute fixes see [[ARM/N900/ReleaseProcess]].
* Follow Discussion
** Join [http://lists.meego.com/listinfo/meego-porting meego-porting@meego.com] and [http://lists.meego.com/listinfo/meego-handset meego-handset@meego.com] mailing lists
** Hang out in [http://webchat.freenode.net/?channels=#meego-arm #meego-arm IRC channel on irc.freenode.net]
** Join [[ARM/N900/Meetings|weekly team meetings]] are held in the public IRC. This meeting is registered on the [[MeeGo-Meeting_IRC_Schedule|MeeGo IRC Meeting Page]]. The agenda and the archives are also available.
* Learn
** Play a little with Tablet UX pre-alpha as it's possible the same applications will be replacing some of the Handset UX ones. Experiments are being tried with the Tablet UX on N900. Find more details on [[ARM/N900/TabletUX]].
** Look into learning QML if you haven't already.
*Contribute
** Would like to contribute the test cases? You will find the useful information [[Quality|here]].
** Would like to contribute artwork? See [[ARM/N900/Artwork]].
** To the [[ARM/N900/Performance|performance optimization]].
** Follow [http://qa-reports.meego.com/1.2/Handset/Acceptance/N900 acceptance testing reports] and see if there's anything of your interest you'd like to work on.
* Look through [[ARM/N900/Developers|Developers page,]] for tips and tricks.

== Organization ==
Core team, of Community Edition, is formed in and around Nokia. In addition to core team, we hope to see growing community working on this. There is something for everybody to contribute be it bugs, code, artwork or something else. Core team itself has been divided into following categories:

* Scrum master: [http://meego.com/users/msugano Makoto Sugano]
** [[ARM/N900/Performance|UX & Performance]] team lead: [http://meego.com/users/vesku Vesa-Matti Hartikainen]
** [[ARM/N900/Common|Adaptation]] team lead: [http://meego.com/users/harrihakulinen Harri Hakulinen]. **
** [[ARM/N900/CoolStuff|Applications]] facilitator: [http://meego.com/users/jukkaeklund Jukka Eklund]
** [[ARM/N900/ReleaseProcess|Release & integration]]: [http://meego.com/users/sage Marko Saukko].
* [[ARM/N900/QA|QA]]: [http://meego.com/users/jkunnari Jake Kunnari], [http://meego.com/users/jaritah Jari Tahvanainen], [http://meego.com/users/markraja Marko Rajala]
* Community manager: [http://meego.com/users/jukkaeklund Jukka Eklund]

<nowiki>*</nowiki>The Dialer project has been merged with the MeeGo mainstream [[Project/Dialer|Dialer project.]] 
<nowiki>**</nowiki>Includes the [[ARM/N900/HW_Adaptation_team|Hardware Adaptation]] (maintained by [http://meego.com/users/stskeeps Carsten Munk]).

== FAQ ==

Q. Let's assume my bug fix was accepted only in the Community Edition, but rejected in the official 1.2. What do we do with the bug? 
A. Submit the fix to 1.3. Change the status to "RESOLVED". Comment that the fix is available in Community Edition & 1.3.

Q. Which SD card should I be using? 
A. Class 6 and higher. The class has the impact on the performance.

Q. Where can I download the N900 Community Edition release? 
A. See [[N900#Install|installation instructions]]

Q. What is the UI of Community Edition going to be? 
A. Based on what's available on MeeGo trunk. At the moment we work with the MeeGo 1.1-originated Handset UX and apps. We are evaluating the new tablet-originated UX and apps (see [[ARM/N900/TabletUX]]). This is still to be decided, and there might be even multiple options for the user to select.

Q. If I get "The package integrity check failed." (NOKEY) when trying to zypper install MeeGo 1.2 packages, where can I find the missing keys?[1.6.2011] 
A. (no answer yet)

Q. I installed to eMMC and it's dog-slow? [1.6.2011] 
A. The eMMC currently has a severe performance problem, [https://bugs.meego.com/show_bug.cgi?id=18295 bug #18295]

Q. What is this Community Edition really about? 
A. [[ARM/N900/CE_Factsheet|Check out the reasoning of our Meego CE.]]

== Ideas, feedback etc. ==

Please add stuff to the [[ARM/N900/Ideas|Ideas]] page.

== Reporting bugs against N900 Community Edition ==

Currently there is no special Bugzilla product/component for the N900 Community Edition ([http://twitter.com/jukkaeklund/status/74396393195839488 it's "the same MeeGo"]). According to [http://twitter.com/jukkaeklund/status/74396845920632832 this post] by Jukka, you should:

* File a bug report on [http://bugs.meego.com/ bugs.meego.com]
* Use '''[DE]''' in the summary
* Add the '''N900''' keyword to the bug report

[[File:Splash-developers.png]]

[[Category:N900]]

ARM/N900

2011-06-20T12:48:45Z

Hanshoi: /* FAQ */

= MeeGo 1.2 Community Edition for Nokia N900=

'''What's hot:'''
Test the '''MeeGoConf/SF release''' of the MeeGo 1.2 Developer Edition for N900: [http://repository.maemo.org/meego/n900-de/archive/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ download] - [[#Installing_and_running|install]] - [[ARM/N900/CoolStuff|cool stuff]] - [http://forum.meego.com/forumdisplay.php?f=7 discuss]
Read the review by Nathan Willis ([http://lwn.net/SubscriberLink/445703/ec074038295f3d0f/ lwn.net])

== Introduction ==
The target of this activity is to make a Community Edition of MeeGo for the Nokia N900 device. '''Note: initiative was originally called Developer Edition, so you will see that mentioned in many places'''. Don't get confused, this is the same thing :)

The Community Edition is an 'overlay' constructed above the current core MeeGo 1.2. The Community Edition project is working as a draft of a MeeGo handset image, to make possible the MeeGo development on your N900 hardware. Being a draft it will not take into account all features commonly present in a handset OS. To see what features will be implemented look [[#Key_features]]. Flashed with this edition N900 will be usable as a primary phone device for a developer/hacker person. '''This is not meant for regular (Maemo 5) users. Using this release will probably void any warranty and there is no (other than community-based) support available.'''

=== Target ===
The focus is on meeting the non-functional targets (such as performance) rather than number of features. This will hopefully encourage more people to use MeeGo on N900, and continue enhancing the functionality or build new stuff. Community Edition is based on MeeGo 1.2 handset trunk content, and selected community contributions ([[ARM/N900/CoolStuff|see the candidates]]). Core MeeGo 1.2 Handset features can be found in [https://bugs.meego.com/report.cgi?x_axis_field=product&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=MeeGo+Features&product=MeeGo+Core+OS+Features&product=MeeGo+Handset+Features&version=1.0&version=1.1&version=1.2&version=1.0&version=1.1&version=1.2&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=ACCEPTED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bug_id_type=anyexact&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= featurezilla], and features of the Community Edition not yet implemented from [[ARM/N900/Configuration|Configuration list.]]

== Key features ==
These use cases shall be the prominent ones in the Community Edition. (If you want to promote a feature to this list, please add it to the feedback section first.)

'''Cellular voice calls''' (Dialer, People)

* Make voice calls (input number directly, initiate from Contacts, initiate from Call history)
* Receive calls
* Default ringtone plays
* Volume control works via System UI
* SIM PIN entry support

'''SMS''' (SMS, People)
* Send new SMS (input number, send from Contacts)
* Receive SMS, and reply to sender

'''Browser use over WLAN''' (Browser, Settings)
* Able to connect to WLAN AP (with security etc.)
* Open a complex modern website (eg. gmail.com)

'''Camera''' (meegocamera)
* Still image capture
* Support for N900 keys (zoom, capture)

'''Common SW''' (Settings, xterm, lock)

Common components such as System UI, Home screen etc. shall be made functional so that basic device usage is smooth and fast. N900 device specific features such as keys, display and battery will be optimized. [[SDK|MeeGo SDK]] fully supports this edition, as it is MeeGo 1.2 compliant.

== Status ==
The maturity of Community Edition image, can be seen from the [[ARM/N900/Status|Status page.]]

== Installing and running ==
Image download and installing instructions can be found from [[N900#Install|N900 page,]] please refer to them for more instructions.

* [[N900#Install|Download and install]] instructions page.
* [[ARM/N900/Status|Status and reports]] of the latest image.
* [[ARM/N900/CoolStuff|Applications and accessories]] for the Community Edition.

== Release schedule ==

This shows the '''release schedule''' and content. It should be understood that Community Edition is still based on "best-effort" model, so this might change any time. If you want to make sure targets are kept, please join the project and help us. For more detailed list of features that are implemented on the releases, look in the [[ARM/N900/Configuration|Configuration page.]]

{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
|-
!style="border-style: solid; border-width: 0 1px 1px 0"| Release
!style="border-style: solid; border-width: 0 1px 1px 0"| Date
!style="border-style: solid; border-width: 0 1px 1px 0"| Description
!style="border-style: solid; border-width: 0 0 1px 0"| Main Features
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| Summer Release
|style="border-style: solid; border-width: 0 1px 1px 0"| 22.6.2011
|style="border-style: solid; border-width: 0 1px 1px 0"| 1H/2011 achievement
|style="border-style: solid; border-width: 0 0 1px 0"| [[ARM/N900/Summer_Release|link]]
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ MeeGo Conference Release]
|style="border-style: solid; border-width: 0 1px 1px 0"| 23.5.2011
|style="border-style: solid; border-width: 0 1px 1px 0"| MeeGo Conference release
|style="border-style: solid; border-width: 0 0 1px 0"| [[ARM/N900/Configuration#Meego_Conference_Release|link]]
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.1.99.2.20110412.6.DE.2011-04-15.1/images/mg-handset-armv7nhl-n900-de-acceptance/ Alpha release]
|style="border-style: solid; border-width: 0 1px 1px 0"| 15.04.2011
|style="border-style: solid; border-width: 0 1px 1px 0"| Alpha release of the MeeGo Developer Edition image.
|style="border-style: solid; border-width: 0 0 1px 0"| [[ARM/N900/Configuration#Alpha_Release|Calls, SMS, Browser and Camera.]]
|-
|}

== I want to help! ==
Willing to contribute the code to MeeGo, but wondering where to start from? Learn the ropes from the MeeGo experts! This [[Media:Meegokickoff.pdf|material (meego developer's journey)]] gives the overview on the daily development workflow.

Some more concrete steps:

* To contribute fixes see [[ARM/N900/ReleaseProcess]].
* Follow Discussion
** Join [http://lists.meego.com/listinfo/meego-porting meego-porting@meego.com] and [http://lists.meego.com/listinfo/meego-handset meego-handset@meego.com] mailing lists
** Hang out in [http://webchat.freenode.net/?channels=#meego-arm #meego-arm IRC channel on irc.freenode.net]
** Join [[ARM/N900/Meetings|weekly team meetings]] are held in the public IRC. This meeting is registered on the [[MeeGo-Meeting_IRC_Schedule|MeeGo IRC Meeting Page]]. The agenda and the archives are also available.
* Learn
** Play a little with Tablet UX pre-alpha as it's possible the same applications will be replacing some of the Handset UX ones. Experiments are being tried with the Tablet UX on N900. Find more details on [[ARM/N900/TabletUX]].
** Look into learning QML if you haven't already.
*Contribute
** Would like to contribute the test cases? You will find the useful information [[Quality|here]].
** Would like to contribute artwork? See [[ARM/N900/Artwork]].
** To the [[ARM/N900/Performance|performance optimization]].
** Follow [http://qa-reports.meego.com/1.2/Handset/Acceptance/N900 acceptance testing reports] and see if there's anything of your interest you'd like to work on.
* Look through [[ARM/N900/Developers|Developers page,]] for tips and tricks.

== Organization ==
Core team, of Community Edition, is formed in and around Nokia. In addition to core team, we hope to see growing community working on this. There is something for everybody to contribute be it bugs, code, artwork or something else. Core team itself has been divided into following categories:

* Scrum master: [http://meego.com/users/msugano Makoto Sugano]
** [[ARM/N900/Performance|UX & Performance]] team lead: [http://meego.com/users/vesku Vesa-Matti Hartikainen]
** [[ARM/N900/Common|Adaptation]] team lead: [http://meego.com/users/harrihakulinen Harri Hakulinen]. **
** [[ARM/N900/CoolStuff|Applications]] facilitator: [http://meego.com/users/jukkaeklund Jukka Eklund]
** [[ARM/N900/ReleaseProcess|Release & integration]]: [http://meego.com/users/sage Marko Saukko].
* [[ARM/N900/QA|QA]]: [http://meego.com/users/jkunnari Jake Kunnari], [http://meego.com/users/jaritah Jari Tahvanainen], [http://meego.com/users/markraja Marko Rajala]
* Community manager: [http://meego.com/users/jukkaeklund Jukka Eklund]

<nowiki>*</nowiki>The Dialer project has been merged with the MeeGo mainstream [[Project/Dialer|Dialer project.]] 
<nowiki>**</nowiki>Includes the [[ARM/N900/HW_Adaptation_team|Hardware Adaptation]] (maintained by [http://meego.com/users/stskeeps Carsten Munk]).

== FAQ ==

Q. Let's assume my bug fix was accepted only in the Community Edition, but rejected in the official 1.2. What do we do with the bug? 
A. Submit the fix to 1.3. Change the status to "RESOLVED". Comment that the fix is available in Community Edition & 1.3.

Q. Which SD card should I be using? 
A. Class 6 and higher. The class has the impact on the performance.

Q. Where can I download the N900 Community Edition release? 
A. See [[N900#Install|installation instructions]]

Q. What is the UI of Community Edition going to be? 
A. Based on what's available on MeeGo trunk. At the moment we work with the MeeGo 1.1-originated Handset UX and apps. We are evaluating the new tablet-originated UX and apps (see [[ARM/N900/TabletUX]]). This is still to be decided, and there might be even multiple options for the user to select.

Q. If I get "The package integrity check failed." (NOKEY) when trying to zypper install MeeGo 1.2 packages, where can I find the missing keys?[1.6.2011] 
A. (no answer yet)

Q. I installed to eMMC and it's dog-slow? [1.6.2011] 
A. The eMMC currently has a severe performance problem, [https://bugs.meego.com/show_bug.cgi?id=18295 bug #18295]

Q. What is this Community Edition really about?
A. [[ARM/N900/CE_Factsheet|Check out the reasoning of our Meego CE.]]

== Ideas, feedback etc. ==

Please add stuff to the [[ARM/N900/Ideas|Ideas]] page.

== Reporting bugs against N900 Community Edition ==

Currently there is no special Bugzilla product/component for the N900 Community Edition ([http://twitter.com/jukkaeklund/status/74396393195839488 it's "the same MeeGo"]). According to [http://twitter.com/jukkaeklund/status/74396845920632832 this post] by Jukka, you should:

* File a bug report on [http://bugs.meego.com/ bugs.meego.com]
* Use '''[DE]''' in the summary
* Add the '''N900''' keyword to the bug report

[[File:Splash-developers.png]]

[[Category:N900]]

ARM/N900/GettingStarted

2011-06-20T12:44:00Z

Hanshoi:

= Getting Started =
== Introduction ==
This page helps you getting started with Meego 1.2 Community Edition for N900. Installing Community Edition (CE) on your N900 will nullify your warranty, and is meant for developer use only. Here we introduce the simplest and most recommended way of installing Community Edition on your phone, if you are looking for a different approach then look at the bottom of the page for [[#Alternative_Installations|alternative approaches.]] The recommended installation method will install Meego 1.2 Community Edition as a dual boot with your Maemo 5 fremantle operating system.

''' WARNING: Remember that installing Community Edition (CE) on your N900 will nullify your warranty, and is meant for developer use only. '''

== Install ==
Follow these steps to install Meego 1.2 Community Edition to your N900.
=== Prequisities ===
* N900 with Fremantle PR 1.3
* Linux (for windows & mac, look [[#Alternative_Installations|alternative approaches]])
* MicroSD (4Gb or bigger)
* [[N900#Download_image|Community Edition Image]]
* [[#Uboot_installation|U-Boot]] (on your phone)

''' You have to use PR 1.3 version of Fremantle and nothing else '''

=== Uboot installation ===
Uboot is required for booting to Community Edition, or alternatively to your original operating system.

# Enable the maemo.org extras-devel repository, see http://wiki.maemo.org/Extras-devel in your N900.
# Install the 'uboot-pr13' package from 'System' section, of your N900 software center.
# Verify it's installed by restarting your N900. A penguin should show up at startup and U-boot will be mentioned, let it time out and boot into Maemo.

If this intallation didn't work for you, try the [http://wiki.meego.com/ARM/N900/Install/FlashUboot manual installation of U-Boot.]

=== Download image ===
* [http://repository.maemo.org/meego/n900-de/archive/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/mg-handset-armv7nhl-n900-de-sanity-1.1.99.7.20110516.2.DE.2011-05-23.1-mmcblk0p.raw.bz2 Download latest image] (recommended)
* [[N900#Download_image|Release list.]]
* [http://repository.maemo.org/meego/n900-de/daily/ Latest daily] (unstable)
* [[ARM/Creating_ARM_image_using_MeeGo_Image_Creator|Build your own image.]]

=== Install Meego image ===

When inserting the microSD memory card in the card reader, you need to find out what the proper device for the card is. You can also plug the N900 into your computer's USB slot using the package provided cable. Make sure the external microSD card is unmounted, as with most modern linux distributions today it will get auto-mounted if the has a valid filesystem (FAT32 or ExtX). To unmount, you can try this example:
sudo umount /dev/sdX

And use the mount command to determine if/ where it is mounted:
sudo mount (for an example how the microSD would look go [[MountOutput here]].

Finding out the device node can also be done with for example fdisk:
sudo fdisk -l

An example output ('''NOTE: The /dev/sdX is used as an example on your PC this might be also called /dev/mmcblk0, /dev/sdd or something else''')
$ sudo fdisk -l
...
Disk /dev/sdX: 3965 MB, 3965714432 bytes
194 heads, 30 sectors/track, 1330 cylinders
Units = cylinders of 5820 * 512 = 2979840 bytes
Disk identifier: 0x0001ab40

Device Boot Start End Blocks Id System
/dev/sdX1 1 588 1708984 83 Linux

'''NOTE: The .raw image contains the partition table as well. So the image needs to be written to /dev/sdX not /dev/sdX1.'''

After you are 100% sure that the /dev/sdX is the microSD memory card you just inserted in the card reader, you can use for example dd to put the image to the card:
$ sudo dd bs=4096 if='''<raw_image>''' of=/dev/sdX

If you are low on disk space, you can use

$ bzcat <raw_image>.bz2 | sudo dd bs=4096 of=/dev/sdX

to decompress the compressed raw image on the fly without having to unpack it on you computer first. And if you have pv(1) installed, you can add it in between to display the progress (the image is ~ 2GB in size as of 2010-10-04):

$ bzcat <raw_image>.bz2 | pv | sudo dd bs=4096 of=/dev/sdX

The dd does not show any progress until the file is written to the device, so be patient.

dd will output:

328356+0 records in
328356+0 records out
1344946176 bytes (1.3 GB) copied, 105.625 s, 12.7 MB/s

After this, you can insert the card in the N900, and start using Meego Community Edition on your N900.

== Emulate image ==
You can use Meego Community Edition on your computer by emulating it with your chroot. However when using chroot no UI is available, only terminal. Good thing is that all changes you make there will be available for you on your phone.

Install chroot
apt-get install mic2

Insert your MicroSD card with Meego CE in it, and run chroot as a root, having the meego root folder as a parameter.
mic-chroot /media/XXXXXXXXXXXXXX

Now you should have a Meego CE running in one of your terminals. The Meego CE filesystem is also accessible from your linux filesystem, under /media/xxxxxxxxx .

== Alternative install ==
If the recommended way didn't help you, here is a list of alternative installation methods.

{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
|-
!style="border-style: solid; border-width: 0 1px 1px 0"| Topic
!style="border-style: solid; border-width: 0 0 1px 0"| Description
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/MMC|MMC Installation]]
|style="border-style: solid; border-width: 0 0 1px 0"| Installs MeeGo to a external SD card. Windows, Linux, and Mac OS X guides also.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/EMMC| eMMC Installation]]
|style="border-style: solid; border-width: 0 0 1px 0"| Install MeeGo on the internal memory. This will destroy the existing fremantle installation.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/chroot|Chroot install]]
|style="border-style: solid; border-width: 0 0 1px 0"| Chroot install is a way to try out MeeGo by running it on top of Maemo 5 on your N900 device.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/NFS|NFS-Root over usb networking]]
|style="border-style: solid; border-width: 0 0 1px 0"| With NFS-root install you can run MeeGo natively on your N900, without erasing Maemo 5, without flashing or using SD card. Rootfs speed over USB is the downside.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/U-Boot from scratch|Install U-boot from scratch]]
|style="border-style: solid; border-width: 0 0 1px 0"| If you cannot install uboot from Maemo repo, then use this one to get it installed.
|}

== Troubleshooting ==
If you encountered problems with your install, try one of the following.
* Try out one of the alternative and more comprehensive guides at list above.
* Create a question on the FAQ section below.
* [[ARM/N900#I_want_to_help!|Ask a question on our mailing list, or in irc channel.]]

=== FAQ ===

ARM/N900/GettingStarted

2011-06-20T12:06:57Z

Hanshoi:

= Getting Started =
== Introduction ==
This page helps you getting started with Meego 1.2 Community Edition for N900. Installing Community Edition (CE) on your N900 will nullify your warranty, and is meant for developer use only. Here we introduce the simplest and most recommended way of installing Community Edition on your phone, if you are looking for a different approach then look at the bottom of the page for [[#Alternative_Installations|alternative approaches.]] The recommended installation method will install Meego 1.2 Community Edition as a dual boot with your Maemo 5 fremantle operating system.

''' WARNING: Remember that installing Community Edition (CE) on your N900 will nullify your warranty, and is meant for developer use only. '''

== Install ==
Follow these steps to install Meego 1.2 Community Edition to your N900.
=== Prequisities ===
* N900 with Fremantle PR 1.3
* Linux (for windows & mac, look [[#Alternative_Installations|alternative approaches]])
* MicroSD (4Gb or bigger)
* [[N900#Download_image|Community Edition Image]]
* [[#Uboot_installation|U-Boot]] (on your phone)

''' You have to use PR 1.3 version of Fremantle and nothing else '''

=== Uboot installation ===
Uboot is required for booting to Community Edition, or alternatively to your original operating system.

# Enable the maemo.org extras-devel repository, see http://wiki.maemo.org/Extras-devel in your N900.
# Install the 'uboot-pr13' package from 'System' section, of your N900 software center.
# Verify it's installed by restarting your N900. A penguin should show up at startup and U-boot will be mentioned, let it time out and boot into Maemo.

If this intallation didn't work for you, try the [http://wiki.meego.com/ARM/N900/Install/FlashUboot manual installation of U-Boot.]

=== Download image ===
* [http://repository.maemo.org/meego/n900-de/archive/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/mg-handset-armv7nhl-n900-de-sanity-1.1.99.7.20110516.2.DE.2011-05-23.1-mmcblk0p.raw.bz2 Download latest image] (recommended)
* [[N900#Download_image|Release list.]]
* [http://repository.maemo.org/meego/n900-de/daily/ Latest daily] (unstable)
* [[ARM/Creating_ARM_image_using_MeeGo_Image_Creator|Build your own image.]]

=== Install Meego image ===

When inserting the microSD memory card in the card reader, you need to find out what the proper device for the card is. You can also plug the N900 into your computer's USB slot using the package provided cable. Make sure the external microSD card is unmounted, as with most modern linux distributions today it will get auto-mounted if the has a valid filesystem (FAT32 or ExtX). To unmount, you can try this example:
sudo umount /dev/sdX

And use the mount command to determine if/ where it is mounted:
sudo mount (for an example how the microSD would look go [[MountOutput here]].

Finding out the device node can also be done with for example fdisk:
sudo fdisk -l

An example output ('''NOTE: The /dev/sdX is used as an example on your PC this might be also called /dev/mmcblk0, /dev/sdd or something else''')
$ sudo fdisk -l
...
Disk /dev/sdX: 3965 MB, 3965714432 bytes
194 heads, 30 sectors/track, 1330 cylinders
Units = cylinders of 5820 * 512 = 2979840 bytes
Disk identifier: 0x0001ab40

Device Boot Start End Blocks Id System
/dev/sdX1 1 588 1708984 83 Linux

'''NOTE: The .raw image contains the partition table as well. So the image needs to be written to /dev/sdX not /dev/sdX1.'''

After you are 100% sure that the /dev/sdX is the microSD memory card you just inserted in the card reader, you can use for example dd to put the image to the card:
$ sudo dd bs=4096 if='''<raw_image>''' of=/dev/sdX

If you are low on disk space, you can use

$ bzcat <raw_image>.bz2 | sudo dd bs=4096 of=/dev/sdX

to decompress the compressed raw image on the fly without having to unpack it on you computer first. And if you have pv(1) installed, you can add it in between to display the progress (the image is ~ 2GB in size as of 2010-10-04):

$ bzcat <raw_image>.bz2 | pv | sudo dd bs=4096 of=/dev/sdX

The dd does not show any progress until the file is written to the device, so be patient.

Although sending a USR1 signal to a running dd process makes it print I/O statistics to standard error and then resume copying:
$ dd if=/dev/zero of=/dev/null& pid=$!
from another term:
$ kill -USR1 $pid

dd will output:

328356+0 records in
328356+0 records out
1344946176 bytes (1.3 GB) copied, 105.625 s, 12.7 MB/s

After this, you can insert the card in the N900, and start using Meego Community Edition on your N900.

== Emulate image ==
TODO: description of installing and using CE through chroot. (or qemu)

== Alternative install ==
If the recommended way didn't help you, here is a list of alternative installation methods.

{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
|-
!style="border-style: solid; border-width: 0 1px 1px 0"| Topic
!style="border-style: solid; border-width: 0 0 1px 0"| Description
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/MMC|MMC Installation]]
|style="border-style: solid; border-width: 0 0 1px 0"| Installs MeeGo to a external SD card. Windows, Linux, and Mac OS X guides also.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/EMMC| eMMC Installation]]
|style="border-style: solid; border-width: 0 0 1px 0"| Install MeeGo on the internal memory. This will destroy the existing fremantle installation.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/chroot|Chroot install]]
|style="border-style: solid; border-width: 0 0 1px 0"| Chroot install is a way to try out MeeGo by running it on top of Maemo 5 on your N900 device.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/NFS|NFS-Root over usb networking]]
|style="border-style: solid; border-width: 0 0 1px 0"| With NFS-root install you can run MeeGo natively on your N900, without erasing Maemo 5, without flashing or using SD card. Rootfs speed over USB is the downside.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/U-Boot from scratch|Install U-boot from scratch]]
|style="border-style: solid; border-width: 0 0 1px 0"| If you cannot install uboot from Maemo repo, then use this one to get it installed.
|}

== Troubleshooting ==
If you encountered problems with your install, try one of the following.
* Try out one of the alternative and more comprehensive guides at list above.
* Create a question on the FAQ section below.
* [[ARM/N900#I_want_to_help!|Ask a question on our mailing list, or in irc channel.]]

=== FAQ ===

ARM/N900/GettingStarted

2011-06-17T14:29:35Z

Hanshoi: Created page with "= Getting Started = == Introduction == This page helps you getting started with Meego 1.2 Community Edition for N900. Installing Community Edition (CE) on your N900 will nullify ..."

ARM/N900/Install/FlashUboot

2011-06-17T14:27:54Z

Hanshoi: Created page with "= Flash U-Boot = Instruction on you flash uboot straight into your device. This is the way how to install U-Boot if the recommended way fails. ([[ARM/N900/GettingStarted#Uboot_in..."

= Flash U-Boot =
Instruction on you flash uboot straight into your device. This is the way how to install U-Boot if the recommended way fails. ([[ARM/N900/GettingStarted#Uboot_installation|recommended way]]

You must be using the PR1.3 kernel and nothing else. You will likely end up in a reboot loop if you don't have this otherwise. You need dpkg tool to use this.

# Download 'uboot-pr13_*_armel.deb' from http://repository.maemo.org/extras-devel/pool/fremantle-1.3/free/u/uboot-pr13/
# unpack deb: "dpkg -X uboot-pr13_1.0.2_armel.deb uboot-pr13"
# flash to device: "sudo flasher-3.5 -f -F temp/boot/uboot-and-zImage-2.6.28-20103103+0m5.fiasco"

''' WARNING: You have to use PR 1.3 version of Fremantle and nothing else '''

N900

2011-06-17T13:44:14Z

Hanshoi: /* Download image */

[[File:20000101-034513.png|400px|thumb|right]]

= MeeGo 1.2 Community Edition for Nokia N900 =
'' "I have N900, and want to try MeeGo on it." '' 
'' "I want to develop MeeGo/Qt applications on my N900 device" '' 
'' "I want to develop MeeGo OS, on existing N900 or other ARM-based device" ''

== Introduction ==
When using MeeGo on the Nokia N900, or other ARM-based handset, it's recommended to use MeeGo [[ARM/N900|Community Edition]]. [[ARM/N900|Community Edition]] is an edition of the core MeeGo 1.2. The [[ARM/N900|Community Edition]] is developed with the ARM and handset compatibility in mind, this way developers already owning a N900 device may start developing with it immediately.

For more information about the Community Edition, please visit [[ARM/N900|page.]]

== Status ==
The working status of MeeGo for N900 implementation can be seen on [[ARM/N900/Status|Status page.]]

== Install ==
=== Download image ===
You can choose from several images from our repository, or even [[ARM/Creating ARM image using MeeGo Image Creator|build one yourself.]]

[[ARM/N900/GettingStarted]]

{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
|-
!style="border-style: solid; border-width: 0 1px 1px 0"| Image
!style="border-style: solid; border-width: 0 1px 1px 0"| Description
!style="border-style: solid; border-width: 0 0 1px 0"| Release date
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| Summer Release
|style="border-style: solid; border-width: 0 1px 1px 0"| Image for summer 2011.
|style="border-style: solid; border-width: 0 0 1px 0"| (coming soon)
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ SF/MeeGoConf Release]
|style="border-style: solid; border-width: 0 1px 1px 0"| San Francisco release, image released at MeeGo conference.(recommended)
|style="border-style: solid; border-width: 0 0 1px 0"| 23.5.2011
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.1.99.2.20110412.6.DE.2011-04-15.1/images/mg-handset-armv7nhl-n900-de-acceptance/ Alpha release]
|style="border-style: solid; border-width: 0 1px 1px 0"| Alpha release of the Meego Developer Edition image.
|style="border-style: solid; border-width: 0 0 1px 0"| 15.04.2011
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/ Weekly image]
|style="border-style: solid; border-width: 0 1px 1px 0"| From here you can find the weekly and daily builds.
|style="border-style: solid; border-width: 0 0 1px 0"|
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [https://meego.com/downloads/releases/1.1/meego-v1.1-handset MeeGo Core 1.1]
|style="border-style: solid; border-width: 0 1px 1px 0"| Original MeeGo core 1.1 release for N900.
|style="border-style: solid; border-width: 0 0 1px 0"| 28.10.2010
|}

=== Install image ===
Recommended way is to install MeeGo 1.2 Community Edition as dual boot to N900, with your Maemo 5 fremantle. However you can choose any one from the list with your own risk.

{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
|-
!style="border-style: solid; border-width: 0 1px 1px 0"| Topic
!style="border-style: solid; border-width: 0 0 1px 0"| Description
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/Dual_Boot|Dual-boot install]]
|style="border-style: solid; border-width: 0 0 1px 0"| Installs MeeGo as dual boot with your Maemo 5 fremantle. (Default)
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/MMC|MMC Installation]]
|style="border-style: solid; border-width: 0 0 1px 0"| Installs MeeGo to a external SD card. Does not destroy internal memory of your N900 device, and also a recommended way.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/EMMC| eMMC Installation]]
|style="border-style: solid; border-width: 0 0 1px 0"| Install MeeGo on the internal memory. This will destroy the existing fremantle installation.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/chroot|Chroot install]]
|style="border-style: solid; border-width: 0 0 1px 0"| Chroot install is a way to try out MeeGo by running it on top of Maemo 5 on your N900 device.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/NFS|NFS-Root over usb networking]]
|style="border-style: solid; border-width: 0 0 1px 0"| With NFS-root install you can run MeeGo natively on your N900, without erasing Maemo 5, without flashing or using SD card. Rootfs speed over USB is the downside.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/U-Boot from scratch|Install U-boot from scratch]]
|style="border-style: solid; border-width: 0 0 1px 0"| If you cannot install uboot from Maemo repo, then use this one to get it installed.
|}

=== Applications ===
If you want to try out some applications on Meego [[ARM/N900|Community Edition]] get them from [[ARM/N900/CoolStuff|here.]] Eventually applications will be in [[http://apps-beta.meego.com/applications/MeeGo Community apps site]].

== Participate ==
If you are interested to help developing MeeGo or applications for your favorite hardware. Please visit on MeeGo [[ARM/N900|Community Edition page.]]

== FAQ ==
Q. Where can I download the N900 Community Edition release? 
A. See [[#Download_image]]

Q. Where do I see the maturity of the current image? 
A. See the Community Edition [[ARM/N900/Status|Status page.]]

Q. My battery is drained, how shall I recharge it? 
A. Look from [[ARM/N900/Recover_From_Drained_Battery|battery recharge guide.]]

Q. I want to install back to Maemo5 as my only operating system, how will I do that? 
A. See the [http://wiki.maemo.org/Updating_the_firmware#N900_2 restore Maemo guide] from Maemo wiki.

Q. I want a usb connection to my N900, how will I do it? 
A. Use ssh. See [[ARM/N900/Tips_and_Tricks/N900_USB_Networking|guide.]]

N900

2011-06-17T13:14:10Z

Hanshoi: /* Download image */

[[File:20000101-034513.png|400px|thumb|right]]

= MeeGo 1.2 Community Edition for Nokia N900 =
'' "I have N900, and want to try MeeGo on it." '' 
'' "I want to develop MeeGo/Qt applications on my N900 device" '' 
'' "I want to develop MeeGo OS, on existing N900 or other ARM-based device" ''

== Introduction ==
When using MeeGo on the Nokia N900, or other ARM-based handset, it's recommended to use MeeGo [[ARM/N900|Community Edition]]. [[ARM/N900|Community Edition]] is an edition of the core MeeGo 1.2. The [[ARM/N900|Community Edition]] is developed with the ARM and handset compatibility in mind, this way developers already owning a N900 device may start developing with it immediately.

For more information about the Community Edition, please visit [[ARM/N900|page.]]

== Status ==
The working status of MeeGo for N900 implementation can be seen on [[ARM/N900/Status|Status page.]]

== Install ==
=== Download image ===
You can choose from several images from our repository, or even [[ARM/Creating ARM image using MeeGo Image Creator|build one yourself.]]

{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
|-
!style="border-style: solid; border-width: 0 1px 1px 0"| Image
!style="border-style: solid; border-width: 0 1px 1px 0"| Description
!style="border-style: solid; border-width: 0 0 1px 0"| Release date
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| Summer Release
|style="border-style: solid; border-width: 0 1px 1px 0"| Image for summer 2011.
|style="border-style: solid; border-width: 0 0 1px 0"| (coming soon)
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ SF/MeeGoConf Release]
|style="border-style: solid; border-width: 0 1px 1px 0"| San Francisco release, image released at MeeGo conference.(recommended)
|style="border-style: solid; border-width: 0 0 1px 0"| 23.5.2011
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.1.99.2.20110412.6.DE.2011-04-15.1/images/mg-handset-armv7nhl-n900-de-acceptance/ Alpha release]
|style="border-style: solid; border-width: 0 1px 1px 0"| Alpha release of the Meego Developer Edition image.
|style="border-style: solid; border-width: 0 0 1px 0"| 15.04.2011
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/ Weekly image]
|style="border-style: solid; border-width: 0 1px 1px 0"| From here you can find the weekly and daily builds.
|style="border-style: solid; border-width: 0 0 1px 0"|
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [https://meego.com/downloads/releases/1.1/meego-v1.1-handset MeeGo Core 1.1]
|style="border-style: solid; border-width: 0 1px 1px 0"| Original MeeGo core 1.1 release for N900.
|style="border-style: solid; border-width: 0 0 1px 0"| 28.10.2010
|}

=== Install image ===
Recommended way is to install MeeGo 1.2 Community Edition as dual boot to N900, with your Maemo 5 fremantle. However you can choose any one from the list with your own risk.

{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
|-
!style="border-style: solid; border-width: 0 1px 1px 0"| Topic
!style="border-style: solid; border-width: 0 0 1px 0"| Description
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/Dual_Boot|Dual-boot install]]
|style="border-style: solid; border-width: 0 0 1px 0"| Installs MeeGo as dual boot with your Maemo 5 fremantle. (Default)
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/MMC|MMC Installation]]
|style="border-style: solid; border-width: 0 0 1px 0"| Installs MeeGo to a external SD card. Does not destroy internal memory of your N900 device, and also a recommended way.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/EMMC| eMMC Installation]]
|style="border-style: solid; border-width: 0 0 1px 0"| Install MeeGo on the internal memory. This will destroy the existing fremantle installation.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/chroot|Chroot install]]
|style="border-style: solid; border-width: 0 0 1px 0"| Chroot install is a way to try out MeeGo by running it on top of Maemo 5 on your N900 device.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/NFS|NFS-Root over usb networking]]
|style="border-style: solid; border-width: 0 0 1px 0"| With NFS-root install you can run MeeGo natively on your N900, without erasing Maemo 5, without flashing or using SD card. Rootfs speed over USB is the downside.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/U-Boot from scratch|Install U-boot from scratch]]
|style="border-style: solid; border-width: 0 0 1px 0"| If you cannot install uboot from Maemo repo, then use this one to get it installed.
|}

=== Applications ===
If you want to try out some applications on Meego [[ARM/N900|Community Edition]] get them from [[ARM/N900/CoolStuff|here.]] Eventually applications will be in [[http://apps-beta.meego.com/applications/MeeGo Community apps site]].

== Participate ==
If you are interested to help developing MeeGo or applications for your favorite hardware. Please visit on MeeGo [[ARM/N900|Community Edition page.]]

== FAQ ==
Q. Where can I download the N900 Community Edition release? 
A. See [[#Download_image]]

Q. Where do I see the maturity of the current image? 
A. See the Community Edition [[ARM/N900/Status|Status page.]]

Q. My battery is drained, how shall I recharge it? 
A. Look from [[ARM/N900/Recover_From_Drained_Battery|battery recharge guide.]]

Q. I want to install back to Maemo5 as my only operating system, how will I do that? 
A. See the [http://wiki.maemo.org/Updating_the_firmware#N900_2 restore Maemo guide] from Maemo wiki.

Q. I want a usb connection to my N900, how will I do it? 
A. Use ssh. See [[ARM/N900/Tips_and_Tricks/N900_USB_Networking|guide.]]

ARM/N900/Status

2011-06-17T11:08:34Z

Hanshoi: /* N900 Community Edition current status */

== Status ==

Status page is meant to be, a frequently updated, status report of the progress of Meego Community Editions features. The status list itself is divided into two categories, Core and UX. Core level testing is all testing between UI and HW adaptation. UX (User Experience) is testing features from the UI level. The latest weekly image is marked in the list header (eg. wk17 against week 17 CE image).

=== Links ===
* '''Open [https://bugs.meego.com/buglist.cgi?priority=High&keywords=N900CE&query_format=advanced&keywords_type=allwords&field0-0-0=flagtypes.name&bug_severity=critical&bug_status=NEW&bug_status=NEEDINFO&bug_status=INDEFINITION&bug_status=ASSIGNED&bug_status=ACCEPTED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=WAITING&bug_status=REOPENED&type0-0-0=anyexact&value0-0-0=MeeGo_N900CE_Release_Blocker%2B&known_name=N900DE%20TOP%2010 TOP 10 Release Blocker Bugs]'''
* '''Open [https://bugs.meego.com/buglist.cgi?query_format=advanced&field0-0-0=flagtypes.name&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&type0-0-0=anyexact&value0-0-0=MeeGo_N900DE_Release_Blocker%2B DevEdition blocker bugs]''' ([https://bugs.meego.com/buglist.cgi?query_format=advanced&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=MeeGo_N900DE_Release_Blocker%3F proposed bugs])
* [http://qa-reports.meego.com/1.2/Handset/Key%20Feature/N900ce Use case reports], [http://qa-reports.meego.com/1.2/Handset/Dataflow/N900ce Data flow reports], [http://qa-reports.meego.com/1.2/Handset/Basic%20Feature/N900ce Basic feature reports]
* [http://wiki.meego.com/ARM/N900/QA/Performance Performance results]
* [https://bugs.meego.com/metrics/?stats=N900_DE_-_Release_Blocker Bug metrics]
* [https://bugs.meego.com/buglist.cgi?keywords=N900CE&query_format=advanced&keywords_type=allwords&resolution=--- All current open N900 specific bugs], based on 'N900' keyword.

=== N900 Community Edition current status ===
* Core = Core level testing. Testing from just under UI, down to hardware adaptation level. (eg. Qt-APIs, ofono)
* UX = User Experience level testing. Testing the product from users point of view. (eg. UI level features)

{| cellpadding="5" cellspacing="0" border="1"
! Feature !! Subfeature !! Core CE.2011-06-17.1 !! UX CE.2011-06-13.1
|-
| Cellular voice call
| Make a call directly
! style="background:green" | OK
! style="background:orange" | OK (1)*
|-
|
|Initiate call from contacts
! style="background:grey" | N/A
! style="background:red" | NOK (2)
|-
|
| Initiate call from history
! style="background:grey" | N/A
! style="background:green" | OK
|-
|
| Receive Voice call
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Default ringing tone plays
! style="background:orange" | OK (1)
! style="background:green" | OK
|-
|
| Volume control
! style="background:grey" | N/A
! style="background:green" | OK
|-
|
| SIM PIN code entry support
! style="background:green" | OK
! style="background:green" | OK
|-
| SMS
| Send SMS, Direct number input
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Send SMS, select contact
! style="background:grey" | N/A
! style="background:green" | OK
|-
|
| SMS, Reply to sender (Core: receive)
! style="background:green" | OK
! style="background:green" | OK
|-
| Multimedia
| Audio Playback
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Video Playback
! style="background:green" | OK
! style="background:orange" | OK (3)
|-
|
| Image Viewing
! style="background:green" | OK (2)
! style="background:green" | OK
|-
| Sensors
| Sensors return data
! style="background:red" | NOK (3)
! style="background:grey" | N/A
|-
| Browser over WLAN
| Able to connect to WLAN AP (with security etc.)
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Open a complex modern website (Core: Transfer data)
! style="background:green" | OK
! style="background:green" | OK
|-
| Camera (meegocamera)
| Still image capture
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Support for N900 keys (zoom, capture)
! style="background:green" | OK
! style="background:green" | OK
|-
| System UI
| Smooth and fast basic functionality
! style="background:grey" | N/A
! style="background:orange" | OK (4)
|-
| Homescreen
| Smooth and fast basic functionality
! style="background:grey" | N/A
! style="background:orange" | OK (5)
|-
| Performance
| Response times
! style="background:grey" | N/A
! style="background:yellow" | [http://wiki.meego.com/ARM/N900/QA/Performance MEASURED]
|-
|
| Power management
! style="background:yellow" | [http://wiki.meego.com/ARM/N900/QA/Performance MEASURED]
! style="background:gray" | N/A
|-
|}

* Note number referring to that issue.
==== Core Notes ====
# Rings (very softly, even at max volume) and *sometimes* dialer does open, but does not meet the requirements for a primary device, cannot be heard/felt, in pocket.
# Asset broken. bug #18810. RotationSensor fails to start.
# Not able to get good results. bug #14241

==== UX Notes ====
# HW keyboard cannot work in dialer's text entry field. With VKB ok (bug #8269)
# Unable to make an outgoing call by pressing the call icon in people application (bug #16055). Dialer's People page shows saved contacts only after reboot (bug #17857)
# Video files are not playing properly (bug #13856)
# Battery indicator doesn't reflect real battery status. No missed call notification in system UI (bug #18298)
# UI gets corrupted after changing themes (bug #17538)

[[Category:N900]]

ARM/N900/Status

2011-06-13T13:31:44Z

Hanshoi: /* N900 Community Edition current status */

== Status ==

Status page is meant to be, a frequently updated, status report of the progress of Meego Community Editions features. The status list itself is divided into two categories, Core and UX. Core level testing is all testing between UI and HW adaptation. UX (User Experience) is testing features from the UI level. The latest weekly image is marked in the list header (eg. wk17 against week 17 CE image).

=== Links ===
* '''Open [https://bugs.meego.com/buglist.cgi?priority=High&keywords=n900&query_format=advanced&keywords_type=allwords&field0-0-0=flagtypes.name&bug_severity=critical&bug_status=NEW&bug_status=NEEDINFO&bug_status=INDEFINITION&bug_status=ASSIGNED&bug_status=ACCEPTED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=WAITING&bug_status=REOPENED&type0-0-0=anyexact&value0-0-0=MeeGo_N900DE_Release_Blocker%2B&known_name=N900DE%20TOP%2010 TOP 10 Release Blocker Bugs]'''
* '''Open [https://bugs.meego.com/buglist.cgi?query_format=advanced&field0-0-0=flagtypes.name&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&type0-0-0=anyexact&value0-0-0=MeeGo_N900DE_Release_Blocker%2B DevEdition blocker bugs]''' ([https://bugs.meego.com/buglist.cgi?query_format=advanced&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=MeeGo_N900DE_Release_Blocker%3F proposed bugs])
* [http://qa-reports.meego.com/1.2/Handset/Use%20Case%20Testing%20For%20Developer%20Edition Use case reports], [http://qa-reports.meego.com/1.2/Handset/Data%20Flow%20For%20Developer%20Edition Data flow reports], [http://qa-reports.meego.com/1.2/Handset/Key%20Basic%20Feature%20For%20Developer%20Edition/N900 Key basic feature reports]
* [http://wiki.meego.com/ARM/N900/QA/Performance Performance results]
* [https://bugs.meego.com/metrics/?stats=N900_DE_-_Release_Blocker Bug metrics]
* [https://bugs.meego.com/buglist.cgi?keywords=N900&query_format=advanced&keywords_type=allwords&resolution=--- All current open N900 specific bugs], based on 'N900' keyword.

=== N900 Community Edition current status ===
* Core = Core level testing. Testing from just under UI, down to hardware adaptation level. (eg. Qt-APIs, ofono)
* UX = User Experience level testing. Testing the product from users point of view. (eg. UI level features)

{| cellpadding="5" cellspacing="0" border="1"
! Feature !! Subfeature !! Core CE.2011-06-13.1 !! UX CE.2011-06-08.1
|-
| Cellular voice call
| Make a call directly
! style="background:green" | OK
! style="background:orange" | OK (1)*
|-
|
|Initiate call from contacts
! style="background:grey" | N/A
! style="background:red" | NOK (2)
|-
|
| Initiate call from history
! style="background:grey" | N/A
! style="background:green" | OK
|-
|
| Receive Voice call
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Default ringing tone plays
! style="background:orange" | OK (1)
! style="background:green" | OK
|-
|
| Volume control
! style="background:green" | OK
! style="background:green" | OK
|-
|
| SIM PIN code entry support
! style="background:green" | OK
! style="background:green" | OK
|-
| SMS
| Send SMS, Direct number input
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Send SMS, select contact
! style="background:grey" | N/A
! style="background:red" | NOK (3)
|-
|
| SMS, Reply to sender (Core: receive)
! style="background:green" | OK
! style="background:green" | OK
|-
| Multimedia
| Audio Playback
! style="background:green" | OK
! style="background:grey" | N/A
|-
|
| Video Playback
! style="background:green" | OK
! style="background:grey" | N/A
|-
|
| Image Viewing
! style="background:green" | OK (2)
! style="background:grey" | N/A
|-
| Sensors
| Sensors return data
! style="background:red" | NOK (3)
! style="background:grey" | N/A
|-
| Browser over WLAN
| Able to connect to WLAN AP (with security etc.)
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Open a complex modern website (Core: Transfer data)
! style="background:green" | OK
! style="background:green" | OK
|-
| Camera (meegocamera)
| Still image capture
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Support for N900 keys (zoom, capture)
! style="background:green" | OK
! style="background:green" | OK
|-
| System UI
| Smooth and fast basic functionality
! style="background:grey" | N/A
! style="background:orange" | OK (4)
|-
| Homescreen
| Smooth and fast basic functionality
! style="background:grey" | N/A
! style="background:green" | OK
|-
| Performance
| Response times
! style="background:grey" | N/A
! style="background:yellow" | [http://wiki.meego.com/ARM/N900/QA/Performance MEASURED]
|-
|
| Power management
! style="background:yellow" | [http://wiki.meego.com/ARM/N900/QA/Performance MEASURED]
! style="background:gray" | N/A
|-
|}

* Note number referring to that issue.
==== Core Notes ====
# Rings (very softly, even at max volume) and *sometimes* dialer does open, but does not meet the requirements for a primary device, cannot be heard/felt, in pocket.
# Asset broken. bug #18810
# Not able to get good results. bug #14241

==== UX Notes ====
# HW keyboard cannot work in dialer's text entry field. With VKB ok
# Unable to make an outgoing call by pressing the call icon in people application
# Contact names aren't shown in SMS application. SMS text input field can't be seen when using VKB
# Battery indicator doesn't reflect real battery status. No missed call notification in system UI

[[Category:N900]]

ARM/N900/Status

2011-06-13T13:31:25Z

Hanshoi: /* N900 Community Edition current status */

== Status ==

Status page is meant to be, a frequently updated, status report of the progress of Meego Community Editions features. The status list itself is divided into two categories, Core and UX. Core level testing is all testing between UI and HW adaptation. UX (User Experience) is testing features from the UI level. The latest weekly image is marked in the list header (eg. wk17 against week 17 CE image).

=== Links ===
* '''Open [https://bugs.meego.com/buglist.cgi?priority=High&keywords=n900&query_format=advanced&keywords_type=allwords&field0-0-0=flagtypes.name&bug_severity=critical&bug_status=NEW&bug_status=NEEDINFO&bug_status=INDEFINITION&bug_status=ASSIGNED&bug_status=ACCEPTED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=WAITING&bug_status=REOPENED&type0-0-0=anyexact&value0-0-0=MeeGo_N900DE_Release_Blocker%2B&known_name=N900DE%20TOP%2010 TOP 10 Release Blocker Bugs]'''
* '''Open [https://bugs.meego.com/buglist.cgi?query_format=advanced&field0-0-0=flagtypes.name&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&type0-0-0=anyexact&value0-0-0=MeeGo_N900DE_Release_Blocker%2B DevEdition blocker bugs]''' ([https://bugs.meego.com/buglist.cgi?query_format=advanced&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=MeeGo_N900DE_Release_Blocker%3F proposed bugs])
* [http://qa-reports.meego.com/1.2/Handset/Use%20Case%20Testing%20For%20Developer%20Edition Use case reports], [http://qa-reports.meego.com/1.2/Handset/Data%20Flow%20For%20Developer%20Edition Data flow reports], [http://qa-reports.meego.com/1.2/Handset/Key%20Basic%20Feature%20For%20Developer%20Edition/N900 Key basic feature reports]
* [http://wiki.meego.com/ARM/N900/QA/Performance Performance results]
* [https://bugs.meego.com/metrics/?stats=N900_DE_-_Release_Blocker Bug metrics]
* [https://bugs.meego.com/buglist.cgi?keywords=N900&query_format=advanced&keywords_type=allwords&resolution=--- All current open N900 specific bugs], based on 'N900' keyword.

=== N900 Community Edition current status ===
* Core = Core level testing. Testing from just under UI, down to hardware adaptation level. (eg. Qt-APIs, ofono)
* UX = User Experience level testing. Testing the product from users point of view. (eg. UI level features)

{| cellpadding="5" cellspacing="0" border="1"
! Feature !! Subfeature !! Core DE.2011-06-13.1 !! UX DE.2011-06-08.1
|-
| Cellular voice call
| Make a call directly
! style="background:green" | OK
! style="background:orange" | OK (1)*
|-
|
|Initiate call from contacts
! style="background:grey" | N/A
! style="background:red" | NOK (2)
|-
|
| Initiate call from history
! style="background:grey" | N/A
! style="background:green" | OK
|-
|
| Receive Voice call
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Default ringing tone plays
! style="background:orange" | OK (1)
! style="background:green" | OK
|-
|
| Volume control
! style="background:green" | OK
! style="background:green" | OK
|-
|
| SIM PIN code entry support
! style="background:green" | OK
! style="background:green" | OK
|-
| SMS
| Send SMS, Direct number input
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Send SMS, select contact
! style="background:grey" | N/A
! style="background:red" | NOK (3)
|-
|
| SMS, Reply to sender (Core: receive)
! style="background:green" | OK
! style="background:green" | OK
|-
| Multimedia
| Audio Playback
! style="background:green" | OK
! style="background:grey" | N/A
|-
|
| Video Playback
! style="background:green" | OK
! style="background:grey" | N/A
|-
|
| Image Viewing
! style="background:green" | OK (2)
! style="background:grey" | N/A
|-
| Sensors
| Sensors return data
! style="background:red" | NOK (3)
! style="background:grey" | N/A
|-
| Browser over WLAN
| Able to connect to WLAN AP (with security etc.)
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Open a complex modern website (Core: Transfer data)
! style="background:green" | OK
! style="background:green" | OK
|-
| Camera (meegocamera)
| Still image capture
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Support for N900 keys (zoom, capture)
! style="background:green" | OK
! style="background:green" | OK
|-
| System UI
| Smooth and fast basic functionality
! style="background:grey" | N/A
! style="background:orange" | OK (4)
|-
| Homescreen
| Smooth and fast basic functionality
! style="background:grey" | N/A
! style="background:green" | OK
|-
| Performance
| Response times
! style="background:grey" | N/A
! style="background:yellow" | [http://wiki.meego.com/ARM/N900/QA/Performance MEASURED]
|-
|
| Power management
! style="background:yellow" | [http://wiki.meego.com/ARM/N900/QA/Performance MEASURED]
! style="background:gray" | N/A
|-
|}

* Note number referring to that issue.
==== Core Notes ====
# Rings (very softly, even at max volume) and *sometimes* dialer does open, but does not meet the requirements for a primary device, cannot be heard/felt, in pocket.
# Asset broken. bug #18810
# Not able to get good results. bug #14241

==== UX Notes ====
# HW keyboard cannot work in dialer's text entry field. With VKB ok
# Unable to make an outgoing call by pressing the call icon in people application
# Contact names aren't shown in SMS application. SMS text input field can't be seen when using VKB
# Battery indicator doesn't reflect real battery status. No missed call notification in system UI

[[Category:N900]]

ARM/N900/Status

2011-06-13T13:31:07Z

Hanshoi:

== Status ==

Status page is meant to be, a frequently updated, status report of the progress of Meego Community Editions features. The status list itself is divided into two categories, Core and UX. Core level testing is all testing between UI and HW adaptation. UX (User Experience) is testing features from the UI level. The latest weekly image is marked in the list header (eg. wk17 against week 17 CE image).

=== Links ===
* '''Open [https://bugs.meego.com/buglist.cgi?priority=High&keywords=n900&query_format=advanced&keywords_type=allwords&field0-0-0=flagtypes.name&bug_severity=critical&bug_status=NEW&bug_status=NEEDINFO&bug_status=INDEFINITION&bug_status=ASSIGNED&bug_status=ACCEPTED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=WAITING&bug_status=REOPENED&type0-0-0=anyexact&value0-0-0=MeeGo_N900DE_Release_Blocker%2B&known_name=N900DE%20TOP%2010 TOP 10 Release Blocker Bugs]'''
* '''Open [https://bugs.meego.com/buglist.cgi?query_format=advanced&field0-0-0=flagtypes.name&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&type0-0-0=anyexact&value0-0-0=MeeGo_N900DE_Release_Blocker%2B DevEdition blocker bugs]''' ([https://bugs.meego.com/buglist.cgi?query_format=advanced&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=MeeGo_N900DE_Release_Blocker%3F proposed bugs])
* [http://qa-reports.meego.com/1.2/Handset/Use%20Case%20Testing%20For%20Developer%20Edition Use case reports], [http://qa-reports.meego.com/1.2/Handset/Data%20Flow%20For%20Developer%20Edition Data flow reports], [http://qa-reports.meego.com/1.2/Handset/Key%20Basic%20Feature%20For%20Developer%20Edition/N900 Key basic feature reports]
* [http://wiki.meego.com/ARM/N900/QA/Performance Performance results]
* [https://bugs.meego.com/metrics/?stats=N900_DE_-_Release_Blocker Bug metrics]
* [https://bugs.meego.com/buglist.cgi?keywords=N900&query_format=advanced&keywords_type=allwords&resolution=--- All current open N900 specific bugs], based on 'N900' keyword.

=== N900 Community Edition current status ===
* Core = Core level testing. Testing from just under UI, down to hardware adaptation level. (eg. Qt-APIs, ofono)
* UX = User Experience level testing. Testing the product from users point of view. (eg. UI level features)

{| cellpadding="5" cellspacing="0" border="1"
! Feature !! Subfeature !! Core DE.2011-06-10.1 !! UX DE.2011-06-08.1
|-
| Cellular voice call
| Make a call directly
! style="background:green" | OK
! style="background:orange" | OK (1)*
|-
|
|Initiate call from contacts
! style="background:grey" | N/A
! style="background:red" | NOK (2)
|-
|
| Initiate call from history
! style="background:grey" | N/A
! style="background:green" | OK
|-
|
| Receive Voice call
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Default ringing tone plays
! style="background:orange" | OK (1)
! style="background:green" | OK
|-
|
| Volume control
! style="background:green" | OK
! style="background:green" | OK
|-
|
| SIM PIN code entry support
! style="background:green" | OK
! style="background:green" | OK
|-
| SMS
| Send SMS, Direct number input
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Send SMS, select contact
! style="background:grey" | N/A
! style="background:red" | NOK (3)
|-
|
| SMS, Reply to sender (Core: receive)
! style="background:green" | OK
! style="background:green" | OK
|-
| Multimedia
| Audio Playback
! style="background:green" | OK
! style="background:grey" | N/A
|-
|
| Video Playback
! style="background:green" | OK
! style="background:grey" | N/A
|-
|
| Image Viewing
! style="background:green" | OK (2)
! style="background:grey" | N/A
|-
| Sensors
| Sensors return data
! style="background:red" | NOK (3)
! style="background:grey" | N/A
|-
| Browser over WLAN
| Able to connect to WLAN AP (with security etc.)
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Open a complex modern website (Core: Transfer data)
! style="background:green" | OK
! style="background:green" | OK
|-
| Camera (meegocamera)
| Still image capture
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Support for N900 keys (zoom, capture)
! style="background:green" | OK
! style="background:green" | OK
|-
| System UI
| Smooth and fast basic functionality
! style="background:grey" | N/A
! style="background:orange" | OK (4)
|-
| Homescreen
| Smooth and fast basic functionality
! style="background:grey" | N/A
! style="background:green" | OK
|-
| Performance
| Response times
! style="background:grey" | N/A
! style="background:yellow" | [http://wiki.meego.com/ARM/N900/QA/Performance MEASURED]
|-
|
| Power management
! style="background:yellow" | [http://wiki.meego.com/ARM/N900/QA/Performance MEASURED]
! style="background:gray" | N/A
|-
|}

* Note number referring to that issue.
==== Core Notes ====
# Rings (very softly, even at max volume) and *sometimes* dialer does open, but does not meet the requirements for a primary device, cannot be heard/felt, in pocket.
# Asset broken. bug #18810
# Not able to get good results. bug #14241

==== UX Notes ====
# HW keyboard cannot work in dialer's text entry field. With VKB ok
# Unable to make an outgoing call by pressing the call icon in people application
# Contact names aren't shown in SMS application. SMS text input field can't be seen when using VKB
# Battery indicator doesn't reflect real battery status. No missed call notification in system UI

[[Category:N900]]

ARM/N900/Summer Release

2011-06-13T08:26:29Z

Hanshoi: /* Content in more detail */

= Summer release =

== Release themes ==

'''Faster and fancier'''. Focus on performance, eg. application start-up time and boot up. Dedicated team for this (lead by Vesa-Matti).

'''More applications, better settings'''. New contributions eg. new Terminal, Package manager, GPRS settings. More community applications (via Cool Stuff page), including Extras client. Fix critical bugs in existing use cases (phone calls, SMS, browser, camera). Dedicated team also for this. Jukka facilitating, but still looking for team lead if somebody wants to stand up.

== Schedule ==

Release image available in morning of '''22th June'''.

{| class="wikitable"
|-
! Date
! Note
|-
| Mon 20 Jun
| All changes in before '''UTC 14:00'''
|-
| Tue 21 Jun
| QA and Integration
|-
| Wed 22 Jun
| N900 Summer Release images available.
|}

== Content in more detail ==

* Bug fixes (re-evaluate and target TOP list, to be done)
** All green on: http://wiki.meego.com/ARM/N900/Status#N900_Community_Edition_current_status, for example:
** Voice calls: contact matching, contacts import from Maemo/Symbian?, profiles/silent
*** See Data Management pages for info on Maemo connectivity http://wiki.meego.com/ARM/N900/DataManagement
** SMS: contact matching, app start-up, message tone
** Camera: app start-up, stability, features?
** Browser: app start-up, GPRS connectivity, WLAN fixes/interoperability
* [[ARM/N900/Configuration|Configuration]] (not updated yet)
* For developers
** '''DONE''' PySide Qt bindings
** '''DONE''' meego-ux-components
** '''DONE''' new meego-terminal
* New apps
** New Qt Quick/WebKit browser
** '''DONE''' GPRS settings UI
** [http://wiki.meego.com/ARM/N900/CoolStuff#MeeGo_Community_Extras_Client MeeGo community extras client]
** TwimGo Twitter client (villev?)
** '''DONE''' [http://repo.pub.meego.com/home:/kyranto/DE/armv7hl/ Application manager]
** selected Tablet-based apps (email, calendar, music, video, ?)
** More, from [[ARM/N900/CoolStuff|Cool Stuff]]?
* New content
** Wallpaper
** Community images, videos, music

== Other ideas for summer time ==

* "Summer projects", list of ideas/apps to port over to MeeGo
* Can we do zypper update on top of Summer release?

ARM/N900/Status

2011-06-13T08:26:04Z

Hanshoi: /* Status */

== Status ==

Status page is meant to be, a frequently updated, status report of the progress of Meego Community Editions features. The status list itself is divided into two categories, Core and UX. Core level testing is all testing between UI and HW adaptation. UX (User Experience) is testing features from the UI level. The latest weekly image is marked in the list header (eg. wk17 against week 17 CE image).

=== Links ===
* '''Open [https://bugs.meego.com/buglist.cgi?priority=High&keywords=n900&query_format=advanced&keywords_type=allwords&field0-0-0=flagtypes.name&bug_severity=critical&bug_status=NEW&bug_status=NEEDINFO&bug_status=INDEFINITION&bug_status=ASSIGNED&bug_status=ACCEPTED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=WAITING&bug_status=REOPENED&type0-0-0=anyexact&value0-0-0=MeeGo_N900DE_Release_Blocker%2B&known_name=N900DE%20TOP%2010 TOP 10 Release Blocker Bugs]'''
* '''Open [https://bugs.meego.com/buglist.cgi?query_format=advanced&field0-0-0=flagtypes.name&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&type0-0-0=anyexact&value0-0-0=MeeGo_N900DE_Release_Blocker%2B DevEdition blocker bugs]''' ([https://bugs.meego.com/buglist.cgi?query_format=advanced&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=MeeGo_N900DE_Release_Blocker%3F proposed bugs])
* [http://qa-reports.meego.com/1.2/Handset/Use%20Case%20Testing%20For%20Developer%20Edition Use case reports], [http://qa-reports.meego.com/1.2/Handset/Data%20Flow%20For%20Developer%20Edition Data flow reports], [http://qa-reports.meego.com/1.2/Handset/Key%20Basic%20Feature%20For%20Developer%20Edition/N900 Key basic feature reports]
* [http://wiki.meego.com/ARM/N900/QA/Performance Performance results]
* [https://bugs.meego.com/metrics/?stats=N900_DE_-_Release_Blocker Bug metrics]
* [https://bugs.meego.com/buglist.cgi?keywords=N900&query_format=advanced&keywords_type=allwords&resolution=--- All current open N900 specific bugs], based on 'N900' keyword.

=== N900 Community Edition current status ===
* Core = Core level testing. Testing from just under UI, down to hardware adaptation level. (eg. Qt-APIs, ofono)
* UX = User Experience level testing. Testing the product from users point of view. (eg. UI level features)

{| cellpadding="5" cellspacing="0" border="1"
! Feature !! Subfeature !! Core DE.2011-06-10.1 !! UX DE.2011-06-08.1
|-
| Cellular voice call
| Make a call directly
! style="background:green" | OK
! style="background:orange" | OK (1)*
|-
|
|Initiate call from contacts
! style="background:red" | NOK (1)
! style="background:red" | NOK (2)
|-
|
| Initiate call from history
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Receive Voice call
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Default ringing tone plays
! style="background:orange" | NOK (2)
! style="background:green" | OK
|-
|
| Volume control
! style="background:green" | OK
! style="background:green" | OK
|-
|
| SIM PIN code entry support
! style="background:green" | OK
! style="background:green" | OK
|-
| SMS
| Send SMS, Direct number input
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Send SMS, select contact
! style="background:red" | NOK (3)
! style="background:red" | NOK (3)
|-
|
| SMS, Reply to sender
! style="background:green" | OK
! style="background:green" | OK
|-
| Browser over WLAN
| Able to connect to WLAN AP (with security etc.)
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Open a complex modern website (Core: Transfer data)
! style="background:green" | OK
! style="background:green" | OK
|-
| Camera (meegocamera)
| Still image capture
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Support for N900 keys (zoom, capture)
! style="background:green" | OK
! style="background:green" | OK
|-
| System UI
| Smooth and fast basic functionality
! style="background:grey" | N/A
! style="background:orange" | OK (4)
|-
| Homescreen
| Smooth and fast basic functionality
! style="background:grey" | N/A
! style="background:green" | OK
|-
| Performance
| Response times
! style="background:grey" | N/A
! style="background:yellow" | [http://wiki.meego.com/ARM/N900/QA/Performance MEASURED]
|-
|
| Power management
! style="background:yellow" | [http://wiki.meego.com/ARM/N900/QA/Performance MEASURED]
! style="background:gray" | N/A
|-
| Reliability
| Iterative
! style="background:grey" | N/A
! style="background:gray" | N/A
|-
|}

* Note number referring to that issue.
==== Core Notes ====
# From people application, clicking 'call' does seemingly nothing. In dialer I cannot see all the same contacts as in people application.
# Rings (very softly, even at max volume) and *sometimes* dialer does open, but does not meet the requirements for a primary device, cannot be heard/felt, in pocket.
# Contacts not available in the application

==== UX Notes ====
# HW keyboard cannot work in dialer's text entry field. With VKB ok
# Unable to make an outgoing call by pressing the call icon in people application
# Contact names aren't shown in SMS application. SMS text input field can't be seen when using VKB
# Battery indicator doesn't reflect real battery status. No missed call notification in system UI

[[Category:N900]]

ARM/N900/Status

2011-06-13T08:25:48Z

Hanshoi:

== Status ==

Status page is meant to be, a frequently updated, status report of the progress of Meego Community Editions features. The status list itself is divided into two categories, Core and UX. Core level testing is all testing between UI and HW adaptation. UX (User Experience) is testing features from the UI level. The latest weekly image is marked in the list header (eg. wk17 against week 17 DE image).

=== Links ===
* '''Open [https://bugs.meego.com/buglist.cgi?priority=High&keywords=n900&query_format=advanced&keywords_type=allwords&field0-0-0=flagtypes.name&bug_severity=critical&bug_status=NEW&bug_status=NEEDINFO&bug_status=INDEFINITION&bug_status=ASSIGNED&bug_status=ACCEPTED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=WAITING&bug_status=REOPENED&type0-0-0=anyexact&value0-0-0=MeeGo_N900DE_Release_Blocker%2B&known_name=N900DE%20TOP%2010 TOP 10 Release Blocker Bugs]'''
* '''Open [https://bugs.meego.com/buglist.cgi?query_format=advanced&field0-0-0=flagtypes.name&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&type0-0-0=anyexact&value0-0-0=MeeGo_N900DE_Release_Blocker%2B DevEdition blocker bugs]''' ([https://bugs.meego.com/buglist.cgi?query_format=advanced&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=MeeGo_N900DE_Release_Blocker%3F proposed bugs])
* [http://qa-reports.meego.com/1.2/Handset/Use%20Case%20Testing%20For%20Developer%20Edition Use case reports], [http://qa-reports.meego.com/1.2/Handset/Data%20Flow%20For%20Developer%20Edition Data flow reports], [http://qa-reports.meego.com/1.2/Handset/Key%20Basic%20Feature%20For%20Developer%20Edition/N900 Key basic feature reports]
* [http://wiki.meego.com/ARM/N900/QA/Performance Performance results]
* [https://bugs.meego.com/metrics/?stats=N900_DE_-_Release_Blocker Bug metrics]
* [https://bugs.meego.com/buglist.cgi?keywords=N900&query_format=advanced&keywords_type=allwords&resolution=--- All current open N900 specific bugs], based on 'N900' keyword.

=== N900 Community Edition current status ===
* Core = Core level testing. Testing from just under UI, down to hardware adaptation level. (eg. Qt-APIs, ofono)
* UX = User Experience level testing. Testing the product from users point of view. (eg. UI level features)

{| cellpadding="5" cellspacing="0" border="1"
! Feature !! Subfeature !! Core DE.2011-06-10.1 !! UX DE.2011-06-08.1
|-
| Cellular voice call
| Make a call directly
! style="background:green" | OK
! style="background:orange" | OK (1)*
|-
|
|Initiate call from contacts
! style="background:red" | NOK (1)
! style="background:red" | NOK (2)
|-
|
| Initiate call from history
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Receive Voice call
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Default ringing tone plays
! style="background:orange" | NOK (2)
! style="background:green" | OK
|-
|
| Volume control
! style="background:green" | OK
! style="background:green" | OK
|-
|
| SIM PIN code entry support
! style="background:green" | OK
! style="background:green" | OK
|-
| SMS
| Send SMS, Direct number input
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Send SMS, select contact
! style="background:red" | NOK (3)
! style="background:red" | NOK (3)
|-
|
| SMS, Reply to sender
! style="background:green" | OK
! style="background:green" | OK
|-
| Browser over WLAN
| Able to connect to WLAN AP (with security etc.)
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Open a complex modern website (Core: Transfer data)
! style="background:green" | OK
! style="background:green" | OK
|-
| Camera (meegocamera)
| Still image capture
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Support for N900 keys (zoom, capture)
! style="background:green" | OK
! style="background:green" | OK
|-
| System UI
| Smooth and fast basic functionality
! style="background:grey" | N/A
! style="background:orange" | OK (4)
|-
| Homescreen
| Smooth and fast basic functionality
! style="background:grey" | N/A
! style="background:green" | OK
|-
| Performance
| Response times
! style="background:grey" | N/A
! style="background:yellow" | [http://wiki.meego.com/ARM/N900/QA/Performance MEASURED]
|-
|
| Power management
! style="background:yellow" | [http://wiki.meego.com/ARM/N900/QA/Performance MEASURED]
! style="background:gray" | N/A
|-
| Reliability
| Iterative
! style="background:grey" | N/A
! style="background:gray" | N/A
|-
|}

* Note number referring to that issue.
==== Core Notes ====
# From people application, clicking 'call' does seemingly nothing. In dialer I cannot see all the same contacts as in people application.
# Rings (very softly, even at max volume) and *sometimes* dialer does open, but does not meet the requirements for a primary device, cannot be heard/felt, in pocket.
# Contacts not available in the application

==== UX Notes ====
# HW keyboard cannot work in dialer's text entry field. With VKB ok
# Unable to make an outgoing call by pressing the call icon in people application
# Contact names aren't shown in SMS application. SMS text input field can't be seen when using VKB
# Battery indicator doesn't reflect real battery status. No missed call notification in system UI

[[Category:N900]]

ARM/N900/Status

2011-06-10T12:56:39Z

Hanshoi: /* N900 Developer Edition current status */

== Status ==

Status page is meant to be, a frequently updated, status report of the progress of Meego Developers Editions features. The status list itself is divided into two categories, Core and UX. Core level testing is all testing between UI and HW adaptation. UX (User Experience) is testing features from the UI level. The latest weekly image is marked in the list header (eg. wk17 against week 17 DE image).

=== Links ===
* '''Open [https://bugs.meego.com/buglist.cgi?priority=High&keywords=n900&query_format=advanced&keywords_type=allwords&field0-0-0=flagtypes.name&bug_severity=critical&bug_status=NEW&bug_status=NEEDINFO&bug_status=INDEFINITION&bug_status=ASSIGNED&bug_status=ACCEPTED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=WAITING&bug_status=REOPENED&type0-0-0=anyexact&value0-0-0=MeeGo_N900DE_Release_Blocker%2B&known_name=N900DE%20TOP%2010 TOP 10 Release Blocker Bugs]'''
* '''Open [https://bugs.meego.com/buglist.cgi?query_format=advanced&field0-0-0=flagtypes.name&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&type0-0-0=anyexact&value0-0-0=MeeGo_N900DE_Release_Blocker%2B DevEdition blocker bugs]''' ([https://bugs.meego.com/buglist.cgi?query_format=advanced&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=MeeGo_N900DE_Release_Blocker%3F proposed bugs])
* [http://qa-reports.meego.com/1.2/Handset/Use%20Case%20Testing%20For%20Developer%20Edition Use case reports], [http://qa-reports.meego.com/1.2/Handset/Data%20Flow%20For%20Developer%20Edition Data flow reports], [http://qa-reports.meego.com/1.2/Handset/Key%20Basic%20Feature%20For%20Developer%20Edition/N900 Key basic feature reports]
* [http://wiki.meego.com/ARM/N900/QA/Performance Performance results]
* [https://bugs.meego.com/metrics/?stats=N900_DE_-_Release_Blocker Bug metrics]
* [https://bugs.meego.com/buglist.cgi?keywords=N900&query_format=advanced&keywords_type=allwords&resolution=--- All current open N900 specific bugs], based on 'N900' keyword.

=== N900 Developer Edition current status ===
* Core = Core level testing. Testing from just under UI, down to hardware adaptation level. (eg. Qt-APIs, ofono)
* UX = User Experience level testing. Testing the product from users point of view. (eg. UI level features)

{| cellpadding="5" cellspacing="0" border="1"
! Feature !! Subfeature !! Core DE.2011-06-10.1 !! UX DE.2011-06-08.1
|-
| Cellular voice call
| Make a call directly
! style="background:green" | OK
! style="background:orange" | OK (1)*
|-
|
|Initiate call from contacts
! style="background:red" | NOK (1)
! style="background:red" | NOK (2)
|-
|
| Initiate call from history
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Receive Voice call
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Default ringing tone plays
! style="background:orange" | NOK (2)
! style="background:green" | OK
|-
|
| Volume control
! style="background:green" | OK
! style="background:green" | OK
|-
|
| SIM PIN code entry support
! style="background:green" | OK
! style="background:green" | OK
|-
| SMS
| Send SMS, Direct number input
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Send SMS, select contact
! style="background:red" | NOK (3)
! style="background:red" | NOK (3)
|-
|
| SMS, Reply to sender
! style="background:green" | OK
! style="background:green" | OK
|-
| Browser over WLAN
| Able to connect to WLAN AP (with security etc.)
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Open a complex modern website (Core: Transfer data)
! style="background:green" | OK
! style="background:green" | OK
|-
| Camera (meegocamera)
| Still image capture
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Support for N900 keys (zoom, capture)
! style="background:green" | OK
! style="background:green" | OK
|-
| System UI
| Smooth and fast basic functionality
! style="background:grey" | N/A
! style="background:orange" | OK (4)
|-
| Homescreen
| Smooth and fast basic functionality
! style="background:grey" | N/A
! style="background:green" | OK
|-
| Performance
| Response times
! style="background:grey" | N/A
! style="background:yellow" | [http://wiki.meego.com/ARM/N900/QA/Performance MEASURED]
|-
|
| Power management
! style="background:yellow" | [http://wiki.meego.com/ARM/N900/QA/Performance MEASURED]
! style="background:gray" | N/A
|-
| Reliability
| Iterative
! style="background:grey" | N/A
! style="background:gray" | N/A
|-
|}

* Note number referring to that issue.
==== Core Notes ====
# From people application, clicking 'call' does seemingly nothing. In dialer I cannot see all the same contacts as in people application.
# Rings (very softly, even at max volume) and *sometimes* dialer does open, but does not meet the requirements for a primary device, cannot be heard/felt, in pocket.
# Contacts not available in the application

==== UX Notes ====
# HW keyboard cannot work in dialer's text entry field. With VKB ok
# Unable to make an outgoing call by pressing the call icon in people application
# Contact names aren't shown in SMS application. SMS text input field can't be seen when using VKB
# Battery indicator doesn't reflect real battery status. No missed call notification in system UI

[[Category:N900]]

ARM/N900/Status

2011-06-09T06:20:51Z

Hanshoi: /* N900 Developer Edition current status */

== Status ==

Status page is meant to be, a frequently updated, status report of the progress of Meego Developers Editions features. The status list itself is divided into two categories, Core and UX. Core level testing is all testing between UI and HW adaptation. UX (User Experience) is testing features from the UI level. The latest weekly image is marked in the list header (eg. wk17 against week 17 DE image).

=== Links ===
* '''Open [https://bugs.meego.com/buglist.cgi?priority=High&keywords=n900&query_format=advanced&keywords_type=allwords&field0-0-0=flagtypes.name&bug_severity=critical&bug_status=NEW&bug_status=NEEDINFO&bug_status=INDEFINITION&bug_status=ASSIGNED&bug_status=ACCEPTED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=WAITING&bug_status=REOPENED&type0-0-0=anyexact&value0-0-0=MeeGo_N900DE_Release_Blocker%2B&known_name=N900DE%20TOP%2010 TOP 10 Release Blocker Bugs]'''
* '''Open [https://bugs.meego.com/buglist.cgi?query_format=advanced&field0-0-0=flagtypes.name&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&type0-0-0=anyexact&value0-0-0=MeeGo_N900DE_Release_Blocker%2B DevEdition blocker bugs]''' ([https://bugs.meego.com/buglist.cgi?query_format=advanced&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=MeeGo_N900DE_Release_Blocker%3F proposed bugs])
* [http://qa-reports.meego.com/1.2/Handset/Use%20Case%20Testing%20For%20Developer%20Edition Use case reports], [http://qa-reports.meego.com/1.2/Handset/Data%20Flow%20For%20Developer%20Edition Data flow reports], [http://qa-reports.meego.com/1.2/Handset/Key%20Basic%20Feature%20For%20Developer%20Edition/N900 Key basic feature reports]
* [http://wiki.meego.com/ARM/N900/QA/Performance Performance results]
* [https://bugs.meego.com/metrics/?stats=N900_DE_-_Release_Blocker Bug metrics]
* [https://bugs.meego.com/buglist.cgi?keywords=N900&query_format=advanced&keywords_type=allwords&resolution=--- All current open N900 specific bugs], based on 'N900' keyword.

=== N900 Developer Edition current status ===
* Core = Core level testing. Testing from just under UI, down to hardware adaptation level. (eg. Qt-APIs, ofono)
* UX = User Experience level testing. Testing the product from users point of view. (eg. UI level features)

{| cellpadding="5" cellspacing="0" border="1"
! Feature !! Subfeature !! Core DE.2011-06-08.1 !! UX DE.2011-05-23.1
|-
| Cellular voice call
| Make a call directly
! style="background:green" | OK
! style="background:orange" | OK (1)*
|-
|
|Initiate call from contacts
! style="background:red" | NOK (1)
! style="background:red" | NOK (2)
|-
|
| Initiate call from history
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Receive Voice call
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Default ringing tone plays
! style="background:orange" | NOK (2)
! style="background:green" | OK
|-
|
| Volume control
! style="background:green" | OK
! style="background:green" | OK
|-
|
| SIM PIN code entry support
! style="background:green" | OK
! style="background:green" | OK
|-
| SMS
| Send SMS, Direct number input
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Send SMS, select contact
! style="background:red" | NOK (3)
! style="background:red" | NOK (3)
|-
|
| SMS, Reply to sender
! style="background:green" | OK
! style="background:green" | OK
|-
| Browser over WLAN
| Able to connect to WLAN AP (with security etc.)
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Open a complex modern website (Core: Transfer data)
! style="background:green" | OK
! style="background:green" | OK
|-
| Camera (meegocamera)
| Still image capture
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Support for N900 keys (zoom, capture)
! style="background:green" | OK
! style="background:green" | OK
|-
| System UI
| Smooth and fast basic functionality
! style="background:grey" | N/A
! style="background:orange" | OK (4)
|-
| Homescreen
| Smooth and fast basic functionality
! style="background:grey" | N/A
! style="background:green" | OK
|-
| Performance
| Response times
! style="background:grey" | N/A
! style="background:yellow" | [http://wiki.meego.com/ARM/N900/QA/Performance MEASURED]
|-
|
| Power management
! style="background:yellow" | [http://wiki.meego.com/ARM/N900/QA/Performance MEASURED]
! style="background:gray" | N/A
|-
| Reliability
| Iterative
! style="background:grey" | N/A
! style="background:gray" | N/A
|-
|}

* Note number referring to that issue.
==== Core Notes ====
# From people application, clicking 'call' does seemingly nothing. In dialer I cannot see all the same contacts as in people application.
# Rings (very softly, even at max volume) and *sometimes* dialer does open, but does not meet the requirements for a primary device, cannot be heard/felt, in pocket.
# Contacts not available in the application

==== UX Notes ====
# HW keyboard cannot work in dialer's text entry field. With VKB ok
# Unable to make an outgoing call by pressing the call icon in people application
# Contact names aren't shown in SMS application
# Bluetooth icon remains in system UI eventhough BT is disabled from Settings. Battery indicator doesn't reflect real battery status. Settings crashes when adding wallpaper first time.

[[Category:N900]]

ARM/N900/Status

2011-06-09T05:07:04Z

Hanshoi: /* N900 Developer Edition current status */

== Status ==

Status page is meant to be, a frequently updated, status report of the progress of Meego Developers Editions features. The status list itself is divided into two categories, Core and UX. Core level testing is all testing between UI and HW adaptation. UX (User Experience) is testing features from the UI level. The latest weekly image is marked in the list header (eg. wk17 against week 17 DE image).

=== Links ===
* '''Open [https://bugs.meego.com/buglist.cgi?priority=High&keywords=n900&query_format=advanced&keywords_type=allwords&field0-0-0=flagtypes.name&bug_severity=critical&bug_status=NEW&bug_status=NEEDINFO&bug_status=INDEFINITION&bug_status=ASSIGNED&bug_status=ACCEPTED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=WAITING&bug_status=REOPENED&type0-0-0=anyexact&value0-0-0=MeeGo_N900DE_Release_Blocker%2B&known_name=N900DE%20TOP%2010 TOP 10 Release Blocker Bugs]'''
* '''Open [https://bugs.meego.com/buglist.cgi?query_format=advanced&field0-0-0=flagtypes.name&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&type0-0-0=anyexact&value0-0-0=MeeGo_N900DE_Release_Blocker%2B DevEdition blocker bugs]''' ([https://bugs.meego.com/buglist.cgi?query_format=advanced&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=MeeGo_N900DE_Release_Blocker%3F proposed bugs])
* [http://qa-reports.meego.com/1.2/Handset/Use%20Case%20Testing%20For%20Developer%20Edition Use case reports], [http://qa-reports.meego.com/1.2/Handset/Data%20Flow%20For%20Developer%20Edition Data flow reports], [http://qa-reports.meego.com/1.2/Handset/Key%20Basic%20Feature%20For%20Developer%20Edition/N900 Key basic feature reports]
* [http://wiki.meego.com/ARM/N900/QA/Performance Performance results]
* [https://bugs.meego.com/metrics/?stats=N900_DE_-_Release_Blocker Bug metrics]
* [https://bugs.meego.com/buglist.cgi?keywords=N900&query_format=advanced&keywords_type=allwords&resolution=--- All current open N900 specific bugs], based on 'N900' keyword.

=== N900 Developer Edition current status ===
* Core = Core level testing. Testing from just under UI, down to hardware adaptation level. (eg. Qt-APIs, ofono)
* UX = User Experience level testing. Testing the product from users point of view. (eg. UI level features)

{| cellpadding="5" cellspacing="0" border="1"
! Feature !! Subfeature !! Core DE.2011-06-08.1 !! UX DE.2011-05-23.1
|-
| Cellular voice call
| Make a call directly
! style="background:green" | OK
! style="background:orange" | OK (1)*
|-
|
|Initiate call from contacts
! style="background:red" | NOK (1)
! style="background:red" | NOK (2)
|-
|
| Initiate call from history
! style="background:red" | NOK (2)
! style="background:green" | OK
|-
|
| Receive Voice call
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Default ringing tone plays
! style="background:orange" | NOK (3)
! style="background:green" | OK
|-
|
| Volume control
! style="background:green" | OK
! style="background:green" | OK
|-
|
| SIM PIN code entry support
! style="background:green" | OK
! style="background:green" | OK
|-
| SMS
| Send SMS, Direct number input
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Send SMS, select contact
! style="background:red" | NOK (4)
! style="background:red" | NOK (3)
|-
|
| SMS, Reply to sender
! style="background:green" | OK
! style="background:green" | OK
|-
| Browser over WLAN
| Able to connect to WLAN AP (with security etc.)
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Open a complex modern website (Core: Transfer data)
! style="background:green" | OK
! style="background:green" | OK
|-
| Camera (meegocamera)
| Still image capture
! style="background:green" | OK
! style="background:green" | OK
|-
|
| Support for N900 keys (zoom, capture)
! style="background:green" | OK
! style="background:green" | OK
|-
| System UI
| Smooth and fast basic functionality
! style="background:grey" | N/A
! style="background:orange" | OK (4)
|-
| Homescreen
| Smooth and fast basic functionality
! style="background:grey" | N/A
! style="background:green" | OK
|-
| Performance
| Response times
! style="background:grey" | N/A
! style="background:yellow" | [http://wiki.meego.com/ARM/N900/QA/Performance MEASURED]
|-
|
| Power management
! style="background:yellow" | [http://wiki.meego.com/ARM/N900/QA/Performance MEASURED]
! style="background:gray" | N/A
|-
| Reliability
| Iterative
! style="background:grey" | N/A
! style="background:gray" | N/A
|-
|}

* Note number referring to that issue.
==== Core Notes ====
# From people application, clicking 'call' does seemingly nothing. In dialer I cannot see all the same contacts as in people application.
# From application stucks on Dialing window, though call is made.
# Rings (very softly, even at max volume) and *sometimes* dialer does open, but does not meet the requirements for a primary device, cannot be heard/felt, in pocket.
# Contacts not available in the application

==== UX Notes ====
# HW keyboard cannot work in dialer's text entry field. With VKB ok
# Unable to make an outgoing call by pressing the call icon in people application
# Contact names aren't shown in SMS application
# Bluetooth icon remains in system UI eventhough BT is disabled from Settings. Battery indicator doesn't reflect real battery status. Settings crashes when adding wallpaper first time.

[[Category:N900]]

ARM/N900/QA

2011-05-30T09:46:51Z

Hanshoi: /* Contact */

= Meego Developer Edition Quality Assurance =
Quality Assurance for Meego [[ARM/N900|Developers Edition.]] [[ARM/N900|Developer Edition]] QA uses many same components as in core Meego, therefore remember to look [[Quality|Meego core quality page.]] Monitoring the [[ARM/N900|Developer Edition]] maturity is one of the main tasks of [[ARM/N900|Developer Edition]] QA. The current maturity status can be found from the [[ARM/N900/Status|Status page.]]

== Organization ==
* Error Management
** Error Manager: Iekku Huttunen
* QA Tools
* Core Testing
* User Experience Testing (UX)

== Reports ==
* [http://wiki.meego.com/ARM/N900/Status General DE N900 Feature status]
* [http://wiki.meego.com/ARM/N900/QA/Performance Performance results]
* [http://qa-reports.meego.com/1.2/Handset/Data%20Flow%20For%20Developer%20Edition Dataflow reports]
* [http://qa-reports.meego.com/1.2/Handset/Use%20Case%20Testing%20For%20Developer%20Edition Use case reports]

== Meetings ==
QA IRC meeting every Tuesday:
* [http://wiki.meego.com/MeeGo-Meeting_IRC_Schedule MeeGo-Meeting IRC Schedule]

N900 DE Blocker Bug Triage meeting minutes:
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-19-06.59.html Meeting minutes 19-05-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-12-06.59.html Meeting minutes 12-05-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-05-07.00.html Meeting minutes 05-05-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-21-07.01.html Meeting minutes 21-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-14-07.00.html Meeting minutes 14-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-07-07.02.html Meeting minutes 07-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-31-07.00.html Meeting minutes 31-03-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-24-06.59.html Meeting minutes 24-03-2011]

== Contact ==
* [http://lists.meego.com/listinfo/meego-qa QA-mailing list]
* join #meego-qa at freenode

= QA Tools =
Developers Edition uses same QA Tools as in core Meego. For more information please refer to the [[Quality/QA-tools|Quality/QA-tools]].

== QA-Tools Task List ==
List of tasks the QA-Tools are doing for Meego Developer Edition.
If you need something from QA please tell it to us :)
=== OTS setup ===
(Open Testing System)
* [http://194.136.64.78/logger/view/ OTS server] DONE
* [http://194.136.64.78/logger/view/workers/ OTS worker(s) for core tests]- DONE
* [http://qa-reports.meego.com/1.2/Core/Hourly%20-%20Automated Reporting of hourly tests to QA-reports] - DONE
* Minimize automatic installation time to 10mins - DONE
* OTS worker for UX tests - NOTSTARTED
* OTS Worker(s) for DE tests - ONGOING (timakima)
* Power consumption measurements - NOTSTARTED

=== Test automation images ===
* Setup hourly image building for autotest image on own setup - Riku Halonen/Timo Harkonen/Ville Ilvonen - DONE (in OTS subnet, see above)
* We need to be able to control included test packages - ONGOING (http://meego.gitorious.org/meego-quality-assurance/handset-hourly-automated-tests)
* Move to use images from release engineering (1. download image, 2. install automation enablers, core dumping enablers etc. using mic-chroot, 3. install image to device 4. test) - NOT STARTED

== Applications for testing ==
* qt-demos already available from the repos
* Small applications that use Qt mobility APIs to access things like sensors to help manual testing

== Test asset ==
We are using mainly MCTS test assets, so please refer to the [[Quality/TestSuite/MCTS|MCTS page.]] You can find list of open bugs also from there.
* [https://bugs.meego.com/buglist.cgi?quicksearch=mcts List of open bugs for MCTS]
** see priorities below - discuss with Iekku about priorities of open bugs for MCTS tests
# WLAN cases
# Call/SMS cases
# Audio policy framework cases (lower priority)
# Camera cases (lower priority)
# Sensor data cases (Qt Mobility, lower priority)

== Crash analysis support for ARM core dumps ==

[[File:Text9867-0-4-8.png|350px|thumb|right|Automated testing and crash reporting]]

Core dump processing and backtraces from crashing ARM processes (click the image on right).

* Rich Core dumping
** Make rich-core dumping to work in MeeGo N900 DE (basic functionality) - DONE (sampos, rikhalon)
*** Changes in MeeGo Gitorious ([https://meego.gitorious.org/meego-quality-assurance/rich-core/commits/meego-n900de meego-n900de] branch).
*** Dumps are generated in /home/meego/core-dumps
*** In file name, string "xxxx" is used instead of IMEI digits (privacy issue)
*** Get latest packages [http://repo.pub.meego.com/home:/rha/Project_DE_Trunk_Testing_standard/armv7l/ here]
*** Add "-corewatcher" and "-corewatcher-applet" to .ks file to remove overlapping corewatcher.
** Fix core-reducer (https://bugs.meego.com/show_bug.cgi?id=17134) - DONE (alkuznet)
** Oopslog (and lifelog) functionality - NOT STARTED

* Set up back-end server for core processing - ONGOING (rikhalon, sampos, timakima)

* Image building and test run triggered from cron - trigger-testrun.sh -u <URL> - DONE (timakima)

* Implement OTS Conductor plugin to fetch debug package list (before test run) and upload rich-core dumps to post-processing (after testrun )- DONE (rikhalon)

* testrunner-lite sets a UID for each test case on DUT kernel core pattern. So that a coredump can be matched with a test case - DONE (rikhalon)

* Debug image is built (simultaneuosly) on the core proscessing backend server - build-autotest-image.sh -f fs -d -p debug-packet-list -s 8000 -u <URL>, and saved as target for core prosessing - DONE (sampos)

* After each test case, cores matched against the UID are fetched from the DUT by testrunner-lite. - DONE (sampos)
** testrunner-lite needs to write unique identifier to results.xml e.g. md5 hash from rich-core.
[[File:backend.png|350px|thumb|right|Core Processing Backend]]
<crashes>
<crash-id>1234567890ABCDEF</crash-id>
<crash-id>1234567890ABCDEF</crash-id>
<crash-id>1234567890ABCDEF</crash-id>
</crashes>

* The core processing backend extracts the rich core and looks for proper target (if not available waits...) - PofC DONE (sampos)

* The core processing backend chroots to the target with debug symbols and executes statically linked cross gdb for backtrace - DONE (sampos)

* Upload processed crash data using [[Quality/QA-tools/CrashReports/API|Crash Reports API]] - DONE (rikhalon)

== Boot time measurement ==
* Measure and optimize N900 boot time (timakima, ONGOING)

== CPU load measurement during audio/video playback ==

== Application Manager ==
* Implement an application manager (similar to one in N900/Fremantle) to control install/uninstall/update applications and other packages. (kyranto, ONGOING).

= UX testing =
== Test execution schedule ==
* UX testing schedule: DE / Meego.com testing
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release !! Priority
|-
| Monday
| Dataflow
| DE Weekly
| P1
|-
| Monday
| Use cases
| DE Weekly
| P2
|-
|Monday
| Key feature
| DE Weekly
| P3
|-
| Monday
| Performance
| DE Weekly
| P5
|-
| Monday
| Reliability / Iterative
| DE Weekly
| P6
|-
| Monday
| Dataflow
| DE Trunk testing
| P4
|-
| Tuesday
| Dataflow
| DE Trunk testing
| P1
|-
| Tuesday
| Dataflow
| DE Trunk
| P2
|-
| Tuesday
| Acceptance
| Meego Trunk testing
| P3
|-
| Tuesday
| Key feature
| DE Tablet (N900)
| P4
|-
| Wednesday
| Dataflow
| DE Trunk testing
| P1
|-
| Wednesday
| Dataflow
| DE Trunk
| P2
|-
| Wednesday
| Key feature
| Meego.com weekly
| P3
|-
| Wednesday
| Sanity
| Meego.com weekly
| P4
|-
| Thursday
| Dataflow
| DE Trunk testing
| P1
|-
| Thursday
| Dataflow
| DE Trunk
| P2
|-
| Thursday
| Acceptance
| Meego.com Trunk testing
| P3
|-
| Friday
| Dataflow
| DE Trunk Testing
| P1
|-
| Friday
| Dataflow
| DE Trunk
| P2
|-
| Friday
| Acceptance
| Meego.com Trunk testing
| P3
|}

== Performance Testing ==
Performance testing results done from UI can be found [[ARM/N900/QA/Performance|here]]

= Core Testing =
== QA Tasks For Developer Edition ==
QA tasks for the [[ARM/N900|Developer Edition]] differ from the usual N900 approach in that there are less features to be tested. This is described in more detail in [[ARM/N900#Target|Developer Edition Targets.]] There are currently 2 test sets for the [[ARM/N900|Developer Edition]], these are the Sanity Test Set and the Feature Test Set. They are described below.

=== Test Sets ===
==== Sanity Test Set ====
The sanity set should be run automatically on every image. As such it must meet the following requirements:
* 100% automated
* Testing only basic features
==== Feature Test Set ====
The feature set will be run periodically and will test the basic features as well as enablers for those features (e.g. PIM for phoning contacts). Performance will also be analysed, at the moment, this will include browser startup time, a CPU/Memory benchmark, files system, and power measurement, but this will be explained later.

Suggestions are welcome.

=== Testing schedule ===
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release
|-
| Monday
| Feature
| DE Weekly
|-
| Tuesday
| Sanity
| DE Trunk testing
|-
| Wednesday
| Sanity
| DE Trunk testing
|-
| Thursday
| Sanity
| DE Trunk testing
|-
| Friday
| Sanity
| DE Trunk Testing
|-
|}

=== Core QA Team Backlog ===
The Core QA team intends to keep its backlog as public as possible. The limitation on this is the amount of work generated by doing this. We will attempt to keep an up-to-date lists of tasks and progress on these tasks. At the moment, the task list looks like this:

==== Continuous tasks ====
* Bug verification

==== Backlog ====
* Testcase automation list

==== In progress ====
* DE Hourly Automation improvement
* Wiki clean/update (waiting for comments)

==== Done ====
* * Plan Feature testset (.xml updated)
* Create weekly schedule for MRT (currently in draft form)
* Week 15 DE Sanity Testing
* Maturity statement of Alpha RELEASE (result in QA-report)
* Alpha RELEASE testing

== QA Tasks for MeeGo.com N900 ==

=== Test execution schedule ===
* MeeGo.com N900 Core weekly test schedule for MeeGo1.3
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release !! Priority
|-
| Monday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Monday
| Basic feature test (OK)
| MeeGo.com pre-weekly
| P2
|-
| Tuesday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Tuesday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|-
| Wednesday
| Dataflow (OK)
| MeeGo.com weekly
| P1
|-
| Wednesday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P2
|-
| Thursday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Thursday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|-
| Friday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Friday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|}

=== META team backlog for MeeGo1.2 N900 ===

==== Continuous tasks ====
* Bug verification
* MeeGo1.3 N900 daily validation

==== Backlog ====
* Optimize acceptance automation script
* Testability for MeeGo1.3 features.

==== In progress ====
* Automation testing for trunk:test and trunk image

==== Done ====
* Publish automation test result
* MeeGo1.2 feature verification

= Usefull links =

* [[ARM/N900/Install/MMC|Flashing instructions]]
Flashing tested with http://download.meego.com/testing-daily/builds/trunk/1.1.90.8.20110318.89/

[[Category:N900]]

ARM/N900/QA

2011-05-30T09:46:27Z

Hanshoi: /* Contact */

= Meego Developer Edition Quality Assurance =
Quality Assurance for Meego [[ARM/N900|Developers Edition.]] [[ARM/N900|Developer Edition]] QA uses many same components as in core Meego, therefore remember to look [[Quality|Meego core quality page.]] Monitoring the [[ARM/N900|Developer Edition]] maturity is one of the main tasks of [[ARM/N900|Developer Edition]] QA. The current maturity status can be found from the [[ARM/N900/Status|Status page.]]

== Organization ==
* Error Management
** Error Manager: Iekku Huttunen
* QA Tools
* Core Testing
* User Experience Testing (UX)

== Reports ==
* [http://wiki.meego.com/ARM/N900/Status General DE N900 Feature status]
* [http://wiki.meego.com/ARM/N900/QA/Performance Performance results]
* [http://qa-reports.meego.com/1.2/Handset/Data%20Flow%20For%20Developer%20Edition Dataflow reports]
* [http://qa-reports.meego.com/1.2/Handset/Use%20Case%20Testing%20For%20Developer%20Edition Use case reports]

== Meetings ==
QA IRC meeting every Tuesday:
* [http://wiki.meego.com/MeeGo-Meeting_IRC_Schedule MeeGo-Meeting IRC Schedule]

N900 DE Blocker Bug Triage meeting minutes:
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-19-06.59.html Meeting minutes 19-05-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-12-06.59.html Meeting minutes 12-05-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-05-07.00.html Meeting minutes 05-05-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-21-07.01.html Meeting minutes 21-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-14-07.00.html Meeting minutes 14-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-07-07.02.html Meeting minutes 07-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-31-07.00.html Meeting minutes 31-03-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-24-06.59.html Meeting minutes 24-03-2011]

== Contact ==
* [[http://lists.meego.com/listinfo/meego-qa| QA-mailing list]]
* join #meego-qa at freenode

= QA Tools =
Developers Edition uses same QA Tools as in core Meego. For more information please refer to the [[Quality/QA-tools|Quality/QA-tools]].

== QA-Tools Task List ==
List of tasks the QA-Tools are doing for Meego Developer Edition.
If you need something from QA please tell it to us :)
=== OTS setup ===
(Open Testing System)
* [http://194.136.64.78/logger/view/ OTS server] DONE
* [http://194.136.64.78/logger/view/workers/ OTS worker(s) for core tests]- DONE
* [http://qa-reports.meego.com/1.2/Core/Hourly%20-%20Automated Reporting of hourly tests to QA-reports] - DONE
* Minimize automatic installation time to 10mins - DONE
* OTS worker for UX tests - NOTSTARTED
* OTS Worker(s) for DE tests - ONGOING (timakima)
* Power consumption measurements - NOTSTARTED

=== Test automation images ===
* Setup hourly image building for autotest image on own setup - Riku Halonen/Timo Harkonen/Ville Ilvonen - DONE (in OTS subnet, see above)
* We need to be able to control included test packages - ONGOING (http://meego.gitorious.org/meego-quality-assurance/handset-hourly-automated-tests)
* Move to use images from release engineering (1. download image, 2. install automation enablers, core dumping enablers etc. using mic-chroot, 3. install image to device 4. test) - NOT STARTED

== Applications for testing ==
* qt-demos already available from the repos
* Small applications that use Qt mobility APIs to access things like sensors to help manual testing

== Test asset ==
We are using mainly MCTS test assets, so please refer to the [[Quality/TestSuite/MCTS|MCTS page.]] You can find list of open bugs also from there.
* [https://bugs.meego.com/buglist.cgi?quicksearch=mcts List of open bugs for MCTS]
** see priorities below - discuss with Iekku about priorities of open bugs for MCTS tests
# WLAN cases
# Call/SMS cases
# Audio policy framework cases (lower priority)
# Camera cases (lower priority)
# Sensor data cases (Qt Mobility, lower priority)

== Crash analysis support for ARM core dumps ==

[[File:Text9867-0-4-8.png|350px|thumb|right|Automated testing and crash reporting]]

Core dump processing and backtraces from crashing ARM processes (click the image on right).

* Rich Core dumping
** Make rich-core dumping to work in MeeGo N900 DE (basic functionality) - DONE (sampos, rikhalon)
*** Changes in MeeGo Gitorious ([https://meego.gitorious.org/meego-quality-assurance/rich-core/commits/meego-n900de meego-n900de] branch).
*** Dumps are generated in /home/meego/core-dumps
*** In file name, string "xxxx" is used instead of IMEI digits (privacy issue)
*** Get latest packages [http://repo.pub.meego.com/home:/rha/Project_DE_Trunk_Testing_standard/armv7l/ here]
*** Add "-corewatcher" and "-corewatcher-applet" to .ks file to remove overlapping corewatcher.
** Fix core-reducer (https://bugs.meego.com/show_bug.cgi?id=17134) - DONE (alkuznet)
** Oopslog (and lifelog) functionality - NOT STARTED

* Set up back-end server for core processing - ONGOING (rikhalon, sampos, timakima)

* Image building and test run triggered from cron - trigger-testrun.sh -u <URL> - DONE (timakima)

* Implement OTS Conductor plugin to fetch debug package list (before test run) and upload rich-core dumps to post-processing (after testrun )- DONE (rikhalon)

* testrunner-lite sets a UID for each test case on DUT kernel core pattern. So that a coredump can be matched with a test case - DONE (rikhalon)

* Debug image is built (simultaneuosly) on the core proscessing backend server - build-autotest-image.sh -f fs -d -p debug-packet-list -s 8000 -u <URL>, and saved as target for core prosessing - DONE (sampos)

* After each test case, cores matched against the UID are fetched from the DUT by testrunner-lite. - DONE (sampos)
** testrunner-lite needs to write unique identifier to results.xml e.g. md5 hash from rich-core.
[[File:backend.png|350px|thumb|right|Core Processing Backend]]
<crashes>
<crash-id>1234567890ABCDEF</crash-id>
<crash-id>1234567890ABCDEF</crash-id>
<crash-id>1234567890ABCDEF</crash-id>
</crashes>

* The core processing backend extracts the rich core and looks for proper target (if not available waits...) - PofC DONE (sampos)

* The core processing backend chroots to the target with debug symbols and executes statically linked cross gdb for backtrace - DONE (sampos)

* Upload processed crash data using [[Quality/QA-tools/CrashReports/API|Crash Reports API]] - DONE (rikhalon)

== Boot time measurement ==
* Measure and optimize N900 boot time (timakima, ONGOING)

== CPU load measurement during audio/video playback ==

== Application Manager ==
* Implement an application manager (similar to one in N900/Fremantle) to control install/uninstall/update applications and other packages. (kyranto, ONGOING).

= UX testing =
== Test execution schedule ==
* UX testing schedule: DE / Meego.com testing
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release !! Priority
|-
| Monday
| Dataflow
| DE Weekly
| P1
|-
| Monday
| Use cases
| DE Weekly
| P2
|-
|Monday
| Key feature
| DE Weekly
| P3
|-
| Monday
| Performance
| DE Weekly
| P5
|-
| Monday
| Reliability / Iterative
| DE Weekly
| P6
|-
| Monday
| Dataflow
| DE Trunk testing
| P4
|-
| Tuesday
| Dataflow
| DE Trunk testing
| P1
|-
| Tuesday
| Dataflow
| DE Trunk
| P2
|-
| Tuesday
| Acceptance
| Meego Trunk testing
| P3
|-
| Tuesday
| Key feature
| DE Tablet (N900)
| P4
|-
| Wednesday
| Dataflow
| DE Trunk testing
| P1
|-
| Wednesday
| Dataflow
| DE Trunk
| P2
|-
| Wednesday
| Key feature
| Meego.com weekly
| P3
|-
| Wednesday
| Sanity
| Meego.com weekly
| P4
|-
| Thursday
| Dataflow
| DE Trunk testing
| P1
|-
| Thursday
| Dataflow
| DE Trunk
| P2
|-
| Thursday
| Acceptance
| Meego.com Trunk testing
| P3
|-
| Friday
| Dataflow
| DE Trunk Testing
| P1
|-
| Friday
| Dataflow
| DE Trunk
| P2
|-
| Friday
| Acceptance
| Meego.com Trunk testing
| P3
|}

== Performance Testing ==
Performance testing results done from UI can be found [[ARM/N900/QA/Performance|here]]

= Core Testing =
== QA Tasks For Developer Edition ==
QA tasks for the [[ARM/N900|Developer Edition]] differ from the usual N900 approach in that there are less features to be tested. This is described in more detail in [[ARM/N900#Target|Developer Edition Targets.]] There are currently 2 test sets for the [[ARM/N900|Developer Edition]], these are the Sanity Test Set and the Feature Test Set. They are described below.

=== Test Sets ===
==== Sanity Test Set ====
The sanity set should be run automatically on every image. As such it must meet the following requirements:
* 100% automated
* Testing only basic features
==== Feature Test Set ====
The feature set will be run periodically and will test the basic features as well as enablers for those features (e.g. PIM for phoning contacts). Performance will also be analysed, at the moment, this will include browser startup time, a CPU/Memory benchmark, files system, and power measurement, but this will be explained later.

Suggestions are welcome.

=== Testing schedule ===
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release
|-
| Monday
| Feature
| DE Weekly
|-
| Tuesday
| Sanity
| DE Trunk testing
|-
| Wednesday
| Sanity
| DE Trunk testing
|-
| Thursday
| Sanity
| DE Trunk testing
|-
| Friday
| Sanity
| DE Trunk Testing
|-
|}

=== Core QA Team Backlog ===
The Core QA team intends to keep its backlog as public as possible. The limitation on this is the amount of work generated by doing this. We will attempt to keep an up-to-date lists of tasks and progress on these tasks. At the moment, the task list looks like this:

==== Continuous tasks ====
* Bug verification

==== Backlog ====
* Testcase automation list

==== In progress ====
* DE Hourly Automation improvement
* Wiki clean/update (waiting for comments)

==== Done ====
* * Plan Feature testset (.xml updated)
* Create weekly schedule for MRT (currently in draft form)
* Week 15 DE Sanity Testing
* Maturity statement of Alpha RELEASE (result in QA-report)
* Alpha RELEASE testing

== QA Tasks for MeeGo.com N900 ==

=== Test execution schedule ===
* MeeGo.com N900 Core weekly test schedule for MeeGo1.3
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release !! Priority
|-
| Monday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Monday
| Basic feature test (OK)
| MeeGo.com pre-weekly
| P2
|-
| Tuesday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Tuesday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|-
| Wednesday
| Dataflow (OK)
| MeeGo.com weekly
| P1
|-
| Wednesday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P2
|-
| Thursday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Thursday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|-
| Friday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Friday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|}

=== META team backlog for MeeGo1.2 N900 ===

==== Continuous tasks ====
* Bug verification
* MeeGo1.3 N900 daily validation

==== Backlog ====
* Optimize acceptance automation script
* Testability for MeeGo1.3 features.

==== In progress ====
* Automation testing for trunk:test and trunk image

==== Done ====
* Publish automation test result
* MeeGo1.2 feature verification

= Usefull links =

* [[ARM/N900/Install/MMC|Flashing instructions]]
Flashing tested with http://download.meego.com/testing-daily/builds/trunk/1.1.90.8.20110318.89/

[[Category:N900]]

ARM/N900/QA

2011-05-30T09:46:13Z

Hanshoi: /* Meego Developer Edition Quality Assurance */

= Meego Developer Edition Quality Assurance =
Quality Assurance for Meego [[ARM/N900|Developers Edition.]] [[ARM/N900|Developer Edition]] QA uses many same components as in core Meego, therefore remember to look [[Quality|Meego core quality page.]] Monitoring the [[ARM/N900|Developer Edition]] maturity is one of the main tasks of [[ARM/N900|Developer Edition]] QA. The current maturity status can be found from the [[ARM/N900/Status|Status page.]]

== Organization ==
* Error Management
** Error Manager: Iekku Huttunen
* QA Tools
* Core Testing
* User Experience Testing (UX)

== Reports ==
* [http://wiki.meego.com/ARM/N900/Status General DE N900 Feature status]
* [http://wiki.meego.com/ARM/N900/QA/Performance Performance results]
* [http://qa-reports.meego.com/1.2/Handset/Data%20Flow%20For%20Developer%20Edition Dataflow reports]
* [http://qa-reports.meego.com/1.2/Handset/Use%20Case%20Testing%20For%20Developer%20Edition Use case reports]

== Meetings ==
QA IRC meeting every Tuesday:
* [http://wiki.meego.com/MeeGo-Meeting_IRC_Schedule MeeGo-Meeting IRC Schedule]

N900 DE Blocker Bug Triage meeting minutes:
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-19-06.59.html Meeting minutes 19-05-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-12-06.59.html Meeting minutes 12-05-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-05-07.00.html Meeting minutes 05-05-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-21-07.01.html Meeting minutes 21-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-14-07.00.html Meeting minutes 14-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-07-07.02.html Meeting minutes 07-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-31-07.00.html Meeting minutes 31-03-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-24-06.59.html Meeting minutes 24-03-2011]

== Contact ==
* [[http://lists.meego.com/listinfo/meego-qa|QA-mailing list]]
* join #meego-qa at freenode

= QA Tools =
Developers Edition uses same QA Tools as in core Meego. For more information please refer to the [[Quality/QA-tools|Quality/QA-tools]].

== QA-Tools Task List ==
List of tasks the QA-Tools are doing for Meego Developer Edition.
If you need something from QA please tell it to us :)
=== OTS setup ===
(Open Testing System)
* [http://194.136.64.78/logger/view/ OTS server] DONE
* [http://194.136.64.78/logger/view/workers/ OTS worker(s) for core tests]- DONE
* [http://qa-reports.meego.com/1.2/Core/Hourly%20-%20Automated Reporting of hourly tests to QA-reports] - DONE
* Minimize automatic installation time to 10mins - DONE
* OTS worker for UX tests - NOTSTARTED
* OTS Worker(s) for DE tests - ONGOING (timakima)
* Power consumption measurements - NOTSTARTED

=== Test automation images ===
* Setup hourly image building for autotest image on own setup - Riku Halonen/Timo Harkonen/Ville Ilvonen - DONE (in OTS subnet, see above)
* We need to be able to control included test packages - ONGOING (http://meego.gitorious.org/meego-quality-assurance/handset-hourly-automated-tests)
* Move to use images from release engineering (1. download image, 2. install automation enablers, core dumping enablers etc. using mic-chroot, 3. install image to device 4. test) - NOT STARTED

== Applications for testing ==
* qt-demos already available from the repos
* Small applications that use Qt mobility APIs to access things like sensors to help manual testing

== Test asset ==
We are using mainly MCTS test assets, so please refer to the [[Quality/TestSuite/MCTS|MCTS page.]] You can find list of open bugs also from there.
* [https://bugs.meego.com/buglist.cgi?quicksearch=mcts List of open bugs for MCTS]
** see priorities below - discuss with Iekku about priorities of open bugs for MCTS tests
# WLAN cases
# Call/SMS cases
# Audio policy framework cases (lower priority)
# Camera cases (lower priority)
# Sensor data cases (Qt Mobility, lower priority)

== Crash analysis support for ARM core dumps ==

[[File:Text9867-0-4-8.png|350px|thumb|right|Automated testing and crash reporting]]

Core dump processing and backtraces from crashing ARM processes (click the image on right).

* Rich Core dumping
** Make rich-core dumping to work in MeeGo N900 DE (basic functionality) - DONE (sampos, rikhalon)
*** Changes in MeeGo Gitorious ([https://meego.gitorious.org/meego-quality-assurance/rich-core/commits/meego-n900de meego-n900de] branch).
*** Dumps are generated in /home/meego/core-dumps
*** In file name, string "xxxx" is used instead of IMEI digits (privacy issue)
*** Get latest packages [http://repo.pub.meego.com/home:/rha/Project_DE_Trunk_Testing_standard/armv7l/ here]
*** Add "-corewatcher" and "-corewatcher-applet" to .ks file to remove overlapping corewatcher.
** Fix core-reducer (https://bugs.meego.com/show_bug.cgi?id=17134) - DONE (alkuznet)
** Oopslog (and lifelog) functionality - NOT STARTED

* Set up back-end server for core processing - ONGOING (rikhalon, sampos, timakima)

* Image building and test run triggered from cron - trigger-testrun.sh -u <URL> - DONE (timakima)

* Implement OTS Conductor plugin to fetch debug package list (before test run) and upload rich-core dumps to post-processing (after testrun )- DONE (rikhalon)

* testrunner-lite sets a UID for each test case on DUT kernel core pattern. So that a coredump can be matched with a test case - DONE (rikhalon)

* Debug image is built (simultaneuosly) on the core proscessing backend server - build-autotest-image.sh -f fs -d -p debug-packet-list -s 8000 -u <URL>, and saved as target for core prosessing - DONE (sampos)

* After each test case, cores matched against the UID are fetched from the DUT by testrunner-lite. - DONE (sampos)
** testrunner-lite needs to write unique identifier to results.xml e.g. md5 hash from rich-core.
[[File:backend.png|350px|thumb|right|Core Processing Backend]]
<crashes>
<crash-id>1234567890ABCDEF</crash-id>
<crash-id>1234567890ABCDEF</crash-id>
<crash-id>1234567890ABCDEF</crash-id>
</crashes>

* The core processing backend extracts the rich core and looks for proper target (if not available waits...) - PofC DONE (sampos)

* The core processing backend chroots to the target with debug symbols and executes statically linked cross gdb for backtrace - DONE (sampos)

* Upload processed crash data using [[Quality/QA-tools/CrashReports/API|Crash Reports API]] - DONE (rikhalon)

== Boot time measurement ==
* Measure and optimize N900 boot time (timakima, ONGOING)

== CPU load measurement during audio/video playback ==

== Application Manager ==
* Implement an application manager (similar to one in N900/Fremantle) to control install/uninstall/update applications and other packages. (kyranto, ONGOING).

= UX testing =
== Test execution schedule ==
* UX testing schedule: DE / Meego.com testing
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release !! Priority
|-
| Monday
| Dataflow
| DE Weekly
| P1
|-
| Monday
| Use cases
| DE Weekly
| P2
|-
|Monday
| Key feature
| DE Weekly
| P3
|-
| Monday
| Performance
| DE Weekly
| P5
|-
| Monday
| Reliability / Iterative
| DE Weekly
| P6
|-
| Monday
| Dataflow
| DE Trunk testing
| P4
|-
| Tuesday
| Dataflow
| DE Trunk testing
| P1
|-
| Tuesday
| Dataflow
| DE Trunk
| P2
|-
| Tuesday
| Acceptance
| Meego Trunk testing
| P3
|-
| Tuesday
| Key feature
| DE Tablet (N900)
| P4
|-
| Wednesday
| Dataflow
| DE Trunk testing
| P1
|-
| Wednesday
| Dataflow
| DE Trunk
| P2
|-
| Wednesday
| Key feature
| Meego.com weekly
| P3
|-
| Wednesday
| Sanity
| Meego.com weekly
| P4
|-
| Thursday
| Dataflow
| DE Trunk testing
| P1
|-
| Thursday
| Dataflow
| DE Trunk
| P2
|-
| Thursday
| Acceptance
| Meego.com Trunk testing
| P3
|-
| Friday
| Dataflow
| DE Trunk Testing
| P1
|-
| Friday
| Dataflow
| DE Trunk
| P2
|-
| Friday
| Acceptance
| Meego.com Trunk testing
| P3
|}

== Performance Testing ==
Performance testing results done from UI can be found [[ARM/N900/QA/Performance|here]]

= Core Testing =
== QA Tasks For Developer Edition ==
QA tasks for the [[ARM/N900|Developer Edition]] differ from the usual N900 approach in that there are less features to be tested. This is described in more detail in [[ARM/N900#Target|Developer Edition Targets.]] There are currently 2 test sets for the [[ARM/N900|Developer Edition]], these are the Sanity Test Set and the Feature Test Set. They are described below.

=== Test Sets ===
==== Sanity Test Set ====
The sanity set should be run automatically on every image. As such it must meet the following requirements:
* 100% automated
* Testing only basic features
==== Feature Test Set ====
The feature set will be run periodically and will test the basic features as well as enablers for those features (e.g. PIM for phoning contacts). Performance will also be analysed, at the moment, this will include browser startup time, a CPU/Memory benchmark, files system, and power measurement, but this will be explained later.

Suggestions are welcome.

=== Testing schedule ===
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release
|-
| Monday
| Feature
| DE Weekly
|-
| Tuesday
| Sanity
| DE Trunk testing
|-
| Wednesday
| Sanity
| DE Trunk testing
|-
| Thursday
| Sanity
| DE Trunk testing
|-
| Friday
| Sanity
| DE Trunk Testing
|-
|}

=== Core QA Team Backlog ===
The Core QA team intends to keep its backlog as public as possible. The limitation on this is the amount of work generated by doing this. We will attempt to keep an up-to-date lists of tasks and progress on these tasks. At the moment, the task list looks like this:

==== Continuous tasks ====
* Bug verification

==== Backlog ====
* Testcase automation list

==== In progress ====
* DE Hourly Automation improvement
* Wiki clean/update (waiting for comments)

==== Done ====
* * Plan Feature testset (.xml updated)
* Create weekly schedule for MRT (currently in draft form)
* Week 15 DE Sanity Testing
* Maturity statement of Alpha RELEASE (result in QA-report)
* Alpha RELEASE testing

== QA Tasks for MeeGo.com N900 ==

=== Test execution schedule ===
* MeeGo.com N900 Core weekly test schedule for MeeGo1.3
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release !! Priority
|-
| Monday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Monday
| Basic feature test (OK)
| MeeGo.com pre-weekly
| P2
|-
| Tuesday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Tuesday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|-
| Wednesday
| Dataflow (OK)
| MeeGo.com weekly
| P1
|-
| Wednesday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P2
|-
| Thursday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Thursday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|-
| Friday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Friday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|}

=== META team backlog for MeeGo1.2 N900 ===

==== Continuous tasks ====
* Bug verification
* MeeGo1.3 N900 daily validation

==== Backlog ====
* Optimize acceptance automation script
* Testability for MeeGo1.3 features.

==== In progress ====
* Automation testing for trunk:test and trunk image

==== Done ====
* Publish automation test result
* MeeGo1.2 feature verification

= Usefull links =

* [[ARM/N900/Install/MMC|Flashing instructions]]
Flashing tested with http://download.meego.com/testing-daily/builds/trunk/1.1.90.8.20110318.89/

[[Category:N900]]

ARM/N900

2011-05-27T13:48:41Z

Hanshoi: /* I want to help! */

= MeeGo 1.2 Developer Edition for Nokia N900=

'''What's hot:'''
Test the '''MeeGoConf/SF release''' of the MeeGo 1.2 Developer Edition for N900: [http://repository.maemo.org/meego/n900-de/daily/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ download] - [[#Installing_and_running|install]] - [[ARM/N900/CoolStuff|cool stuff]]

== Introduction ==
The target of this activity is to make a Developer Edition of MeeGo for the Nokia N900 device. This Developer Edition is an 'overlay' constructed above the current core MeeGo 1.2. The DE project is working as a draft of a MeeGo handset image, to make possible the MeeGo development on your N900 hardware. Being a draft it will not take into account all features commonly present in a handset OS. To see what features will be implemented look [[#Key_features]]. Flashed with this edition N900 will be usable as a primary phone device for a developer/hacker person. '''This is not meant for regular (Maemo 5) users. Using this release will probably void any warranty and there is no (other than community-based) support available.'''

=== Target ===
The focus is on meeting the non-functional targets (such as performance) rather than number of features. This will hopefully encourage more people to use MeeGo on N900, and continue enhancing the functionality or build new stuff. Developer Edition is based on MeeGo 1.2 handset trunk content, and selected community contributions ([[ARM/N900/CoolStuff|see the candidates]]). Core MeeGo 1.2 Handset features can be found in [https://bugs.meego.com/report.cgi?x_axis_field=product&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=MeeGo+Features&product=MeeGo+Core+OS+Features&product=MeeGo+Handset+Features&version=1.0&version=1.1&version=1.2&version=1.0&version=1.1&version=1.2&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=ACCEPTED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bug_id_type=anyexact&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= featurezilla], and features of DE not yet implemented from [[ARM/N900/Configuration|Configuration list.]]

== Key features ==
These use cases shall be the prominent ones in the Developer Edition. (If you want to promote a feature to this list, please add it to the feedback section first.)

'''Cellular voice calls''' (Dialer, People)

* Make voice calls (input number directly, initiate from Contacts, initiate from Call history)
* Receive calls
* Default ringtone plays
* Volume control works via System UI
* SIM PIN entry support

'''SMS''' (SMS, People)
* Send new SMS (input number, send from Contacts)
* Receive SMS, and reply to sender

'''Browser use over WLAN''' (Browser, Settings)
* Able to connect to WLAN AP (with security etc.)
* Open a complex modern website (eg. gmail.com)

'''Camera''' (meegocamera)
* Still image capture
* Support for N900 keys (zoom, capture)

'''Common SW''' (Settings, xterm, lock)

Common components such as System UI, Home screen etc. shall be made functional so that basic device usage is smooth and fast. N900 device specific features such as keys, display and battery will be optimized. [[SDK|MeeGo SDK]] fully supports this edition, as it is MeeGo 1.2 compliant.

== Status ==
The maturity of Developer Edition image, can be seen from the [[ARM/N900/Status|Status page.]]

== Installing and running ==
Image download and installing instructions can be found from [[N900#Install|N900 page,]] please refer to them for more instructions.

* [[N900#Install|Download and install]] instructions page.
* [[ARM/N900/Status|Status and reports]] of the latest image.
* [[ARM/N900/CoolStuff|Applications and accessories]] for the Developer Edition.

== Release schedule ==

This shows the '''release schedule''' and content. It should be understood that Developer Edition is still based on "best-effort" model, so this might change any time. If you want to make sure targets are kept, please join the project and help us. For more detailed list of features that are implemented on the releases, look in the [[ARM/N900/Configuration|Configuration page.]]

{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
|-
!style="border-style: solid; border-width: 0 1px 1px 0"| Release
!style="border-style: solid; border-width: 0 1px 1px 0"| Date
!style="border-style: solid; border-width: 0 1px 1px 0"| Description
!style="border-style: solid; border-width: 0 0 1px 0"| Main Features
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| "Summer release"
|style="border-style: solid; border-width: 0 1px 1px 0"| end of June
|style="border-style: solid; border-width: 0 1px 1px 0"| Summer release of Meego DE
|style="border-style: solid; border-width: 0 0 1px 0"| (coming soon)
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/daily/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ MeeGo Conference Release]
|style="border-style: solid; border-width: 0 1px 1px 0"| 23.5.2011
|style="border-style: solid; border-width: 0 1px 1px 0"| Meego conference release
|style="border-style: solid; border-width: 0 0 1px 0"| [[ARM/N900/Configuration#Meego_Conference_Release|link]]
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.1.99.2.20110412.6.DE.2011-04-15.1/images/mg-handset-armv7nhl-n900-de-acceptance/ Alpha release]
|style="border-style: solid; border-width: 0 1px 1px 0"| 15.04.2011
|style="border-style: solid; border-width: 0 1px 1px 0"| Alpha release of the Meego DE image.
|style="border-style: solid; border-width: 0 0 1px 0"| [[ARM/N900/Configuration#Alpha_Release|Calls, SMS, Browser and Camera.]]
|-
|}

== I want to help! ==
Willing to contribute the code to DE/MeeGo, but wondering where to start from? Learn the ropes from the MeeGo experts! This [[Media:Meegokickoff.pdf|material (meego developer's journey)]] gives the overview on the daily development workflow.

Some more concrete steps:

* To contribute fixes see [[ARM/N900/ReleaseProcess]].
* Follow Discussion
** Join [http://lists.meego.com/listinfo/meego-porting meego-porting@meego.com] and [http://lists.meego.com/listinfo/meego-handset meego-handset@meego.com] mailing lists
** Hang out in [http://webchat.freenode.net/?channels=#meego-arm #meego-arm IRC channel on irc.freenode.net]
** Join [[ARM/N900/DeveloperEdition/Meetings|weekly team meetings]] are held in the public IRC. This meeting is registered on the [[MeeGo-Meeting_IRC_Schedule|MeeGo IRC Meeting Page]]. The agenda and the archives are also available.
* Learn
** Play a little with Tablet UX pre-alpha as it's possible the same applications will be replacing some of the Handset UX ones. Experiments are being tried with the Tablet UX on N900. Find more details on [[ARM/N900/TabletUX]].
** Look into learning QML if you haven't already.
*Contribute
** Would like to contribute the test cases? You will find the useful information [[Quality|here]].
** Would like to contribute artwork? See [[ARM/N900/Artwork]].
** Follow [http://qa-reports.meego.com/1.2/Handset/Acceptance/N900 acceptance testing reports] and see if there's anything of your interest you'd like to work on.
* Look through [[ARM/N900/Developers|Developers page,]] for tips and tricks.

== Organization ==
Core team, of Developer Edition, is formed in and around Nokia. In addition to core team, we hope to see growing community working on this. There is something for everybody to contribute be it bugs, code, artwork or something else. Core team itself has been divided into following categories:

* Program lead: [http://meego.com/users/bittinen Mika Leppinen]
** R&D lead: [http://meego.com/users/msugano Makoto Sugano]
*** [[ARM/N900/VoiceSMS|Voice/SMS]] team lead: [http://meego.com/users/sabotage Shane Bryan]. *
*** [[ARM/N900/Browser|Browser/WLAN]] team lead: [http://meego.com/users/vesku Vesa-Matti Hartikainen]
*** [[ARM/N900/Common|Common SW]] team lead: [http://meego.com/users/harrihakulinen Harri Hakulinen]. **
*** [[ARM/N900/ReleaseProcess|Release & integration]]: [http://meego.com/users/ericlr Eric Le Roux], [http://meego.com/users/stskeeps Carsten Munk], [http://meego.com/users/sage Marko Saukko].
** [[ARM/N900/QA|QA]]: [http://meego.com/users/jaritah Jari Tahvanainen], [http://meego.com/users/markraja Marko Rajala]
** [[ARM/N900/PM|Product management]]: [http://meego.com/users/jukkaeklund Jukka Eklund], [http://meego.com/users/samipienimaki Sami Pienimäki]

<nowiki>*</nowiki>This project is merged with the MeeGo mainstream [[Project/Dialer|Dialer project.]] 
<nowiki>**</nowiki>Includes the [[ARM/N900/HW_Adaptation_team|Hardware Adaptation]] (maintained by [http://meego.com/users/stskeeps Carsten Munk]).

== FAQ ==

Q. Let's assume my bug fix was accepted only in the DE, but rejected in the official 1.2. What do we do with the bug? 
A. Submit the fix to 1.3. Change the status to "RESOLVED". Comment that the fix is available in DE & 1.3.

Q. Which SD card should I be using? 
A. Class 6 and higher. The class has the impact on the performance.

Q. Where can I download the N900 DE release? 
A. See [[N900#Install|installation instructions]]

Q. What is the UI of DE going to be? 
A. Based on what's available on MeeGo trunk. At the moment we work with the MeeGo 1.1-originated Handset UX and apps. We are evaluating the new tablet-originated UX and apps (see [[ARM/N900/TabletUX]]). This is still to be decided, and there might be even multiple options for the user to select.

== Ideas, feedback etc. ==

Please add stuff to the [[ARM/N900/Ideas|Ideas]] page.

[[File:Splash-developers.png]]

[[Category:N900]]

ARM/N900

2011-05-27T13:24:48Z

Hanshoi: /* Release schedule */

= MeeGo 1.2 Developer Edition for Nokia N900=

'''What's hot:'''
Test the '''MeeGoConf/SF release''' of the MeeGo 1.2 Developer Edition for N900: [http://repository.maemo.org/meego/n900-de/daily/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ download] - [[#Installing_and_running|install]] - [[ARM/N900/CoolStuff|cool stuff]]

== Introduction ==
The target of this activity is to make a Developer Edition of MeeGo for the Nokia N900 device. This Developer Edition is an 'overlay' constructed above the current core MeeGo 1.2. The DE project is working as a draft of a MeeGo handset image, to make possible the MeeGo development on your N900 hardware. Being a draft it will not take into account all features commonly present in a handset OS. To see what features will be implemented look [[#Key_features]]. Flashed with this edition N900 will be usable as a primary phone device for a developer/hacker person. '''This is not meant for regular (Maemo 5) users. Using this release will probably void any warranty and there is no (other than community-based) support available.'''

=== Target ===
The focus is on meeting the non-functional targets (such as performance) rather than number of features. This will hopefully encourage more people to use MeeGo on N900, and continue enhancing the functionality or build new stuff. Developer Edition is based on MeeGo 1.2 handset trunk content, and selected community contributions ([[ARM/N900/CoolStuff|see the candidates]]). Core MeeGo 1.2 Handset features can be found in [https://bugs.meego.com/report.cgi?x_axis_field=product&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=MeeGo+Features&product=MeeGo+Core+OS+Features&product=MeeGo+Handset+Features&version=1.0&version=1.1&version=1.2&version=1.0&version=1.1&version=1.2&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=ACCEPTED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bug_id_type=anyexact&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= featurezilla], and features of DE not yet implemented from [[ARM/N900/Configuration|Configuration list.]]

== Key features ==
These use cases shall be the prominent ones in the Developer Edition. (If you want to promote a feature to this list, please add it to the feedback section first.)

'''Cellular voice calls''' (Dialer, People)

* Make voice calls (input number directly, initiate from Contacts, initiate from Call history)
* Receive calls
* Default ringtone plays
* Volume control works via System UI
* SIM PIN entry support

'''SMS''' (SMS, People)
* Send new SMS (input number, send from Contacts)
* Receive SMS, and reply to sender

'''Browser use over WLAN''' (Browser, Settings)
* Able to connect to WLAN AP (with security etc.)
* Open a complex modern website (eg. gmail.com)

'''Camera''' (meegocamera)
* Still image capture
* Support for N900 keys (zoom, capture)

'''Common SW''' (Settings, xterm, lock)

Common components such as System UI, Home screen etc. shall be made functional so that basic device usage is smooth and fast. N900 device specific features such as keys, display and battery will be optimized. [[SDK|MeeGo SDK]] fully supports this edition, as it is MeeGo 1.2 compliant.

== Status ==
The maturity of Developer Edition image, can be seen from the [[ARM/N900/Status|Status page.]]

== Installing and running ==
Image download and installing instructions can be found from [[N900#Install|N900 page,]] please refer to them for more instructions.

* [[N900#Install|Download and install]] instructions page.
* [[ARM/N900/Status|Status and reports]] of the latest image.
* [[ARM/N900/CoolStuff|Applications and accessories]] for the Developer Edition.

== Release schedule ==

This shows the '''release schedule''' and content. It should be understood that Developer Edition is still based on "best-effort" model, so this might change any time. If you want to make sure targets are kept, please join the project and help us. For more detailed list of features that are implemented on the releases, look in the [[ARM/N900/Configuration|Configuration page.]]

{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
|-
!style="border-style: solid; border-width: 0 1px 1px 0"| Release
!style="border-style: solid; border-width: 0 1px 1px 0"| Date
!style="border-style: solid; border-width: 0 1px 1px 0"| Description
!style="border-style: solid; border-width: 0 0 1px 0"| Main Features
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| "Summer release"
|style="border-style: solid; border-width: 0 1px 1px 0"| end of June
|style="border-style: solid; border-width: 0 1px 1px 0"| Summer release of Meego DE
|style="border-style: solid; border-width: 0 0 1px 0"| (coming soon)
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/daily/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ MeeGo Conference Release]
|style="border-style: solid; border-width: 0 1px 1px 0"| 23.5.2011
|style="border-style: solid; border-width: 0 1px 1px 0"| Meego conference release
|style="border-style: solid; border-width: 0 0 1px 0"| [[ARM/N900/Configuration#Meego_Conference_Release|link]]
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.1.99.2.20110412.6.DE.2011-04-15.1/images/mg-handset-armv7nhl-n900-de-acceptance/ Alpha release]
|style="border-style: solid; border-width: 0 1px 1px 0"| 15.04.2011
|style="border-style: solid; border-width: 0 1px 1px 0"| Alpha release of the Meego DE image.
|style="border-style: solid; border-width: 0 0 1px 0"| [[ARM/N900/Configuration#Alpha_Release|Calls, SMS, Browser and Camera.]]
|-
|}

== I want to help! ==
Willing to contribute the code to DE/MeeGo, but wondering where to start from? Learn the ropes from the MeeGo experts! This [[Media:Meegokickoff.pdf|material (meego developer's journey)]] gives the overview on the daily development workflow.

Some more concrete steps:

* Join [http://lists.meego.com/listinfo/meego-porting meego-porting@meego.com] and [http://lists.meego.com/listinfo/meego-handset meego-handset@meego.com] mailing lists
* Hang out in [http://webchat.freenode.net/?channels=#meego-arm #meego-arm IRC channel on irc.freenode.net]
* Join [[ARM/N900/DeveloperEdition/Meetings|weekly team meetings]] are held in the public IRC. This meeting is registered on the [[MeeGo-Meeting_IRC_Schedule|MeeGo IRC Meeting Page]]. The agenda and the archives are also available.
* Follow [http://qa-reports.meego.com/1.2/Handset/Acceptance/N900 acceptance testing reports] and see if there's anything of your interest you'd like to work on.
* Play a little with Tablet UX pre-alpha as it's possible the same applications will be replacing some of the Handset UX ones. Experiments are being tried with the Tablet UX on N900. Find more details on [[ARM/N900/TabletUX]].
* Look into learning QML if you haven't already.
* To contribute fixes see [[ARM/N900/ReleaseProcess]].
* Would like to contribute the test cases? You will find the useful information [[Quality|here]].
* Would like to contribute artwork? See [[ARM/N900/Artwork]].
* Look through [[ARM/N900/Developers|Developers page,]] for tips and tricks.

== Organization ==
Core team, of Developer Edition, is formed in and around Nokia. In addition to core team, we hope to see growing community working on this. There is something for everybody to contribute be it bugs, code, artwork or something else. Core team itself has been divided into following categories:

* Program lead: [http://meego.com/users/bittinen Mika Leppinen]
** R&D lead: [http://meego.com/users/msugano Makoto Sugano]
*** [[ARM/N900/VoiceSMS|Voice/SMS]] team lead: [http://meego.com/users/sabotage Shane Bryan]. *
*** [[ARM/N900/Browser|Browser/WLAN]] team lead: [http://meego.com/users/vesku Vesa-Matti Hartikainen]
*** [[ARM/N900/Common|Common SW]] team lead: [http://meego.com/users/harrihakulinen Harri Hakulinen]. **
*** [[ARM/N900/ReleaseProcess|Release & integration]]: [http://meego.com/users/ericlr Eric Le Roux], [http://meego.com/users/stskeeps Carsten Munk], [http://meego.com/users/sage Marko Saukko].
** [[ARM/N900/QA|QA]]: [http://meego.com/users/jaritah Jari Tahvanainen], [http://meego.com/users/markraja Marko Rajala]
** [[ARM/N900/PM|Product management]]: [http://meego.com/users/jukkaeklund Jukka Eklund], [http://meego.com/users/samipienimaki Sami Pienimäki]

<nowiki>*</nowiki>This project is merged with the MeeGo mainstream [[Project/Dialer|Dialer project.]] 
<nowiki>**</nowiki>Includes the [[ARM/N900/HW_Adaptation_team|Hardware Adaptation]] (maintained by [http://meego.com/users/stskeeps Carsten Munk]).

== FAQ ==

Q. Let's assume my bug fix was accepted only in the DE, but rejected in the official 1.2. What do we do with the bug? 
A. Submit the fix to 1.3. Change the status to "RESOLVED". Comment that the fix is available in DE & 1.3.

Q. Which SD card should I be using? 
A. Class 6 and higher. The class has the impact on the performance.

Q. Where can I download the N900 DE release? 
A. See [[N900#Install|installation instructions]]

Q. What is the UI of DE going to be? 
A. Based on what's available on MeeGo trunk. At the moment we work with the MeeGo 1.1-originated Handset UX and apps. We are evaluating the new tablet-originated UX and apps (see [[ARM/N900/TabletUX]]). This is still to be decided, and there might be even multiple options for the user to select.

== Ideas, feedback etc. ==

Please add stuff to the [[ARM/N900/Ideas|Ideas]] page.

[[File:Splash-developers.png]]

[[Category:N900]]

ARM/N900

2011-05-27T13:23:23Z

Hanshoi: /* Release schedule */

= MeeGo 1.2 Developer Edition for Nokia N900=

'''What's hot:'''
Test the '''MeeGoConf/SF release''' of the MeeGo 1.2 Developer Edition for N900: [http://repository.maemo.org/meego/n900-de/daily/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ download] - [[#Installing_and_running|install]] - [[ARM/N900/CoolStuff|cool stuff]]

== Introduction ==
The target of this activity is to make a Developer Edition of MeeGo for the Nokia N900 device. This Developer Edition is an 'overlay' constructed above the current core MeeGo 1.2. The DE project is working as a draft of a MeeGo handset image, to make possible the MeeGo development on your N900 hardware. Being a draft it will not take into account all features commonly present in a handset OS. To see what features will be implemented look [[#Key_features]]. Flashed with this edition N900 will be usable as a primary phone device for a developer/hacker person. '''This is not meant for regular (Maemo 5) users. Using this release will probably void any warranty and there is no (other than community-based) support available.'''

=== Target ===
The focus is on meeting the non-functional targets (such as performance) rather than number of features. This will hopefully encourage more people to use MeeGo on N900, and continue enhancing the functionality or build new stuff. Developer Edition is based on MeeGo 1.2 handset trunk content, and selected community contributions ([[ARM/N900/CoolStuff|see the candidates]]). Core MeeGo 1.2 Handset features can be found in [https://bugs.meego.com/report.cgi?x_axis_field=product&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=MeeGo+Features&product=MeeGo+Core+OS+Features&product=MeeGo+Handset+Features&version=1.0&version=1.1&version=1.2&version=1.0&version=1.1&version=1.2&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=ACCEPTED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bug_id_type=anyexact&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= featurezilla], and features of DE not yet implemented from [[ARM/N900/Configuration|Configuration list.]]

== Key features ==
These use cases shall be the prominent ones in the Developer Edition. (If you want to promote a feature to this list, please add it to the feedback section first.)

'''Cellular voice calls''' (Dialer, People)

* Make voice calls (input number directly, initiate from Contacts, initiate from Call history)
* Receive calls
* Default ringtone plays
* Volume control works via System UI
* SIM PIN entry support

'''SMS''' (SMS, People)
* Send new SMS (input number, send from Contacts)
* Receive SMS, and reply to sender

'''Browser use over WLAN''' (Browser, Settings)
* Able to connect to WLAN AP (with security etc.)
* Open a complex modern website (eg. gmail.com)

'''Camera''' (meegocamera)
* Still image capture
* Support for N900 keys (zoom, capture)

'''Common SW''' (Settings, xterm, lock)

Common components such as System UI, Home screen etc. shall be made functional so that basic device usage is smooth and fast. N900 device specific features such as keys, display and battery will be optimized. [[SDK|MeeGo SDK]] fully supports this edition, as it is MeeGo 1.2 compliant.

== Status ==
The maturity of Developer Edition image, can be seen from the [[ARM/N900/Status|Status page.]]

== Installing and running ==
Image download and installing instructions can be found from [[N900#Install|N900 page,]] please refer to them for more instructions.

* [[N900#Install|Download and install]] instructions page.
* [[ARM/N900/Status|Status and reports]] of the latest image.
* [[ARM/N900/CoolStuff|Applications and accessories]] for the Developer Edition.

== Release schedule ==

This shows the '''release schedule''' and content. It should be understood that Developer Edition is still based on "best-effort" model, so this might change any time. If you want to make sure targets are kept, please join the project and help us. For more detailed list of features that are implemented on the releases, look in the [[ARM/N900/Configuration|Configuration page.]]

* '''"Summer release"''' by end of June, targets are to be refined based on beta achievement and community activity.
* '''[[ARM/N900/SF2011|MeeGo Conference release]]''': on week 20, see the [[ARM/N900/ReleaseProcess/Plan]].
** [http://repository.maemo.org/meego/n900-de/daily/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ Download here].
** Known issues: Coming soon.
* '''Alpha release''': on week 15
** Official DE image available with key overlays on top of MeeGo 1.2 trunk (see [[ARM/N900/Configuration]]).
** Calls, SMS, Browser and Camera should be in a demo-able state (MeeGo Summit FI).
** Key performance and usability items fixed (PM kernel, backlight control)
** [http://repository.maemo.org/meego/n900-de/archive/1.1.99.2.20110412.6.DE.2011-04-15.1/images/mg-handset-armv7nhl-n900-de-acceptance/ Download here].

{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
|-
!style="border-style: solid; border-width: 0 1px 1px 0"| Release
!style="border-style: solid; border-width: 0 1px 1px 0"| Date
!style="border-style: solid; border-width: 0 1px 1px 0"| Description
!style="border-style: solid; border-width: 0 0 1px 0"| Main Features
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| "Summer release"
|style="border-style: solid; border-width: 0 1px 1px 0"| end of June
|style="border-style: solid; border-width: 0 1px 1px 0"| Summer release of Meego DE
|style="border-style: solid; border-width: 0 0 1px 0"| (coming soon)
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/daily/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ MeeGo Conference Release]
|style="border-style: solid; border-width: 0 1px 1px 0"| 23.5.2011
|style="border-style: solid; border-width: 0 1px 1px 0"| Meego conference release
|style="border-style: solid; border-width: 0 0 1px 0"| [[ARM/N900/Configuration#Meego_Conference_Release|]]
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.1.99.2.20110412.6.DE.2011-04-15.1/images/mg-handset-armv7nhl-n900-de-acceptance/ Alpha release]
|style="border-style: solid; border-width: 0 1px 1px 0"| 15.04.2011
|style="border-style: solid; border-width: 0 1px 1px 0"| Alpha release of the Meego DE image.
|style="border-style: solid; border-width: 0 0 1px 0"| [[ARM/N900/Configuration#Alpha_Release|Calls, SMS, Browser and Camera.]]
|-
|}

== I want to help! ==
Willing to contribute the code to DE/MeeGo, but wondering where to start from? Learn the ropes from the MeeGo experts! This [[Media:Meegokickoff.pdf|material (meego developer's journey)]] gives the overview on the daily development workflow.

Some more concrete steps:

* Join [http://lists.meego.com/listinfo/meego-porting meego-porting@meego.com] and [http://lists.meego.com/listinfo/meego-handset meego-handset@meego.com] mailing lists
* Hang out in [http://webchat.freenode.net/?channels=#meego-arm #meego-arm IRC channel on irc.freenode.net]
* Join [[ARM/N900/DeveloperEdition/Meetings|weekly team meetings]] are held in the public IRC. This meeting is registered on the [[MeeGo-Meeting_IRC_Schedule|MeeGo IRC Meeting Page]]. The agenda and the archives are also available.
* Follow [http://qa-reports.meego.com/1.2/Handset/Acceptance/N900 acceptance testing reports] and see if there's anything of your interest you'd like to work on.
* Play a little with Tablet UX pre-alpha as it's possible the same applications will be replacing some of the Handset UX ones. Experiments are being tried with the Tablet UX on N900. Find more details on [[ARM/N900/TabletUX]].
* Look into learning QML if you haven't already.
* To contribute fixes see [[ARM/N900/ReleaseProcess]].
* Would like to contribute the test cases? You will find the useful information [[Quality|here]].
* Would like to contribute artwork? See [[ARM/N900/Artwork]].
* Look through [[ARM/N900/Developers|Developers page,]] for tips and tricks.

== Organization ==
Core team, of Developer Edition, is formed in and around Nokia. In addition to core team, we hope to see growing community working on this. There is something for everybody to contribute be it bugs, code, artwork or something else. Core team itself has been divided into following categories:

* Program lead: [http://meego.com/users/bittinen Mika Leppinen]
** R&D lead: [http://meego.com/users/msugano Makoto Sugano]
*** [[ARM/N900/VoiceSMS|Voice/SMS]] team lead: [http://meego.com/users/sabotage Shane Bryan]. *
*** [[ARM/N900/Browser|Browser/WLAN]] team lead: [http://meego.com/users/vesku Vesa-Matti Hartikainen]
*** [[ARM/N900/Common|Common SW]] team lead: [http://meego.com/users/harrihakulinen Harri Hakulinen]. **
*** [[ARM/N900/ReleaseProcess|Release & integration]]: [http://meego.com/users/ericlr Eric Le Roux], [http://meego.com/users/stskeeps Carsten Munk], [http://meego.com/users/sage Marko Saukko].
** [[ARM/N900/QA|QA]]: [http://meego.com/users/jaritah Jari Tahvanainen], [http://meego.com/users/markraja Marko Rajala]
** [[ARM/N900/PM|Product management]]: [http://meego.com/users/jukkaeklund Jukka Eklund], [http://meego.com/users/samipienimaki Sami Pienimäki]

<nowiki>*</nowiki>This project is merged with the MeeGo mainstream [[Project/Dialer|Dialer project.]] 
<nowiki>**</nowiki>Includes the [[ARM/N900/HW_Adaptation_team|Hardware Adaptation]] (maintained by [http://meego.com/users/stskeeps Carsten Munk]).

== FAQ ==

Q. Let's assume my bug fix was accepted only in the DE, but rejected in the official 1.2. What do we do with the bug? 
A. Submit the fix to 1.3. Change the status to "RESOLVED". Comment that the fix is available in DE & 1.3.

Q. Which SD card should I be using? 
A. Class 6 and higher. The class has the impact on the performance.

Q. Where can I download the N900 DE release? 
A. See [[N900#Install|installation instructions]]

Q. What is the UI of DE going to be? 
A. Based on what's available on MeeGo trunk. At the moment we work with the MeeGo 1.1-originated Handset UX and apps. We are evaluating the new tablet-originated UX and apps (see [[ARM/N900/TabletUX]]). This is still to be decided, and there might be even multiple options for the user to select.

== Ideas, feedback etc. ==

Please add stuff to the [[ARM/N900/Ideas|Ideas]] page.

[[File:Splash-developers.png]]

[[Category:N900]]

ARM/N900

2011-05-27T12:54:11Z

Hanshoi: /* Release schedules */

= MeeGo 1.2 Developer Edition for Nokia N900=

'''What's hot:'''
Test the '''MeeGoConf/SF release''' of the MeeGo 1.2 Developer Edition for N900: [http://repository.maemo.org/meego/n900-de/daily/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ download] - [[#Installing_and_running|install]] - [[ARM/N900/CoolStuff|cool stuff]]

== Introduction ==
The target of this activity is to make a Developer Edition of MeeGo for the Nokia N900 device. This Developer Edition is an 'overlay' constructed above the current core MeeGo 1.2. The DE project is working as a draft of a MeeGo handset image, to make possible the MeeGo development on your N900 hardware. Being a draft it will not take into account all features commonly present in a handset OS. To see what features will be implemented look [[#Key_features]]. Flashed with this edition N900 will be usable as a primary phone device for a developer/hacker person. '''This is not meant for regular (Maemo 5) users. Using this release will probably void any warranty and there is no (other than community-based) support available.'''

=== Target ===
The focus is on meeting the non-functional targets (such as performance) rather than number of features. This will hopefully encourage more people to use MeeGo on N900, and continue enhancing the functionality or build new stuff. Developer Edition is based on MeeGo 1.2 handset trunk content, and selected community contributions ([[ARM/N900/CoolStuff|see the candidates]]). Core MeeGo 1.2 Handset features can be found in [https://bugs.meego.com/report.cgi?x_axis_field=product&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=MeeGo+Features&product=MeeGo+Core+OS+Features&product=MeeGo+Handset+Features&version=1.0&version=1.1&version=1.2&version=1.0&version=1.1&version=1.2&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=ACCEPTED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bug_id_type=anyexact&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= featurezilla], and features of DE not yet implemented from [[ARM/N900/Configuration|Configuration list.]]

== Key features ==
These use cases shall be the prominent ones in the Developer Edition. (If you want to promote a feature to this list, please add it to the feedback section first.)

'''Cellular voice calls''' (Dialer, People)

* Make voice calls (input number directly, initiate from Contacts, initiate from Call history)
* Receive calls
* Default ringtone plays
* Volume control works via System UI
* SIM PIN entry support

'''SMS''' (SMS, People)
* Send new SMS (input number, send from Contacts)
* Receive SMS, and reply to sender

'''Browser use over WLAN''' (Browser, Settings)
* Able to connect to WLAN AP (with security etc.)
* Open a complex modern website (eg. gmail.com)

'''Camera''' (meegocamera)
* Still image capture
* Support for N900 keys (zoom, capture)

'''Common SW''' (Settings, xterm, lock)

Common components such as System UI, Home screen etc. shall be made functional so that basic device usage is smooth and fast. N900 device specific features such as keys, display and battery will be optimized. [[SDK|MeeGo SDK]] fully supports this edition, as it is MeeGo 1.2 compliant.

== Status ==
The maturity of Developer Edition image, can be seen from the [[ARM/N900/Status|Status page.]]

== Installing and running ==
Image download and installing instructions can be found from [[N900#Install|N900 page,]] please refer to them for more instructions.

* [[N900#Install|Download and install]] instructions page.
* [[ARM/N900/Status|Status and reports]] of the latest image.
* [[ARM/N900/CoolStuff|Applications and accessories]] for the Developer Edition.

== Release schedule ==

This shows the '''release schedule''' and content. It should be understood that Developer Edition is still based on "best-effort" model, so this might change any time. If you want to make sure targets are kept, please join the project and help us. For more detailed list of features that are implemented on the releases, look in the [[ARM/N900/Configuration|Configuration page.]]

* '''"Summer release"''' by end of June, targets are to be refined based on beta achievement and community activity.
* '''[[ARM/N900/SF2011|MeeGo Conference release]]''': on week 20, see the [[ARM/N900/ReleaseProcess/Plan]].
** [http://repository.maemo.org/meego/n900-de/daily/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ Download here].
** Known issues: Coming soon.
* '''Alpha release''': on week 15
** Official DE image available with key overlays on top of MeeGo 1.2 trunk (see [[ARM/N900/Configuration]]).
** Calls, SMS, Browser and Camera should be in a demo-able state (MeeGo Summit FI).
** Key performance and usability items fixed (PM kernel, backlight control)
** [http://repository.maemo.org/meego/n900-de/archive/1.1.99.2.20110412.6.DE.2011-04-15.1/images/mg-handset-armv7nhl-n900-de-acceptance/ Download here].

== I want to help! ==
Willing to contribute the code to DE/MeeGo, but wondering where to start from? Learn the ropes from the MeeGo experts! This [[Media:Meegokickoff.pdf|material (meego developer's journey)]] gives the overview on the daily development workflow.

Some more concrete steps:

* Join [http://lists.meego.com/listinfo/meego-porting meego-porting@meego.com] and [http://lists.meego.com/listinfo/meego-handset meego-handset@meego.com] mailing lists
* Hang out in [http://webchat.freenode.net/?channels=#meego-arm #meego-arm IRC channel on irc.freenode.net]
* Join [[ARM/N900/DeveloperEdition/Meetings|weekly team meetings]] are held in the public IRC. This meeting is registered on the [[MeeGo-Meeting_IRC_Schedule|MeeGo IRC Meeting Page]]. The agenda and the archives are also available.
* Follow [http://qa-reports.meego.com/1.2/Handset/Acceptance/N900 acceptance testing reports] and see if there's anything of your interest you'd like to work on.
* Play a little with Tablet UX pre-alpha as it's possible the same applications will be replacing some of the Handset UX ones. Experiments are being tried with the Tablet UX on N900. Find more details on [[ARM/N900/TabletUX]].
* Look into learning QML if you haven't already.
* To contribute fixes see [[ARM/N900/ReleaseProcess]].
* Would like to contribute the test cases? You will find the useful information [[Quality|here]].
* Would like to contribute artwork? See [[ARM/N900/Artwork]].
* Look through [[ARM/N900/Developers|Developers page,]] for tips and tricks.

== Organization ==
Core team, of Developer Edition, is formed in and around Nokia. In addition to core team, we hope to see growing community working on this. There is something for everybody to contribute be it bugs, code, artwork or something else. Core team itself has been divided into following categories:

* Program lead: [http://meego.com/users/bittinen Mika Leppinen]
** R&D lead: [http://meego.com/users/msugano Makoto Sugano]
*** [[ARM/N900/VoiceSMS|Voice/SMS]] team lead: [http://meego.com/users/sabotage Shane Bryan]. *
*** [[ARM/N900/Browser|Browser/WLAN]] team lead: [http://meego.com/users/vesku Vesa-Matti Hartikainen]
*** [[ARM/N900/Common|Common SW]] team lead: [http://meego.com/users/harrihakulinen Harri Hakulinen]. **
*** [[ARM/N900/ReleaseProcess|Release & integration]]: [http://meego.com/users/ericlr Eric Le Roux], [http://meego.com/users/stskeeps Carsten Munk], [http://meego.com/users/sage Marko Saukko].
** [[ARM/N900/QA|QA]]: [http://meego.com/users/jaritah Jari Tahvanainen], [http://meego.com/users/markraja Marko Rajala]
** [[ARM/N900/PM|Product management]]: [http://meego.com/users/jukkaeklund Jukka Eklund], [http://meego.com/users/samipienimaki Sami Pienimäki]

<nowiki>*</nowiki>This project is merged with the MeeGo mainstream [[Project/Dialer|Dialer project.]] 
<nowiki>**</nowiki>Includes the [[ARM/N900/HW_Adaptation_team|Hardware Adaptation]] (maintained by [http://meego.com/users/stskeeps Carsten Munk]).

== FAQ ==

Q. Let's assume my bug fix was accepted only in the DE, but rejected in the official 1.2. What do we do with the bug? 
A. Submit the fix to 1.3. Change the status to "RESOLVED". Comment that the fix is available in DE & 1.3.

Q. Which SD card should I be using? 
A. Class 6 and higher. The class has the impact on the performance.

Q. Where can I download the N900 DE release? 
A. See [[N900#Install|installation instructions]]

Q. What is the UI of DE going to be? 
A. Based on what's available on MeeGo trunk. At the moment we work with the MeeGo 1.1-originated Handset UX and apps. We are evaluating the new tablet-originated UX and apps (see [[ARM/N900/TabletUX]]). This is still to be decided, and there might be even multiple options for the user to select.

== Ideas, feedback etc. ==

Please add stuff to the [[ARM/N900/Ideas|Ideas]] page.

[[File:Splash-developers.png]]

[[Category:N900]]

ARM/N900

2011-05-27T12:53:45Z

Hanshoi: /* Release schedules */

= MeeGo 1.2 Developer Edition for Nokia N900=

'''What's hot:'''
Test the '''MeeGoConf/SF release''' of the MeeGo 1.2 Developer Edition for N900: [http://repository.maemo.org/meego/n900-de/daily/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ download] - [[#Installing_and_running|install]] - [[ARM/N900/CoolStuff|cool stuff]]

== Introduction ==
The target of this activity is to make a Developer Edition of MeeGo for the Nokia N900 device. This Developer Edition is an 'overlay' constructed above the current core MeeGo 1.2. The DE project is working as a draft of a MeeGo handset image, to make possible the MeeGo development on your N900 hardware. Being a draft it will not take into account all features commonly present in a handset OS. To see what features will be implemented look [[#Key_features]]. Flashed with this edition N900 will be usable as a primary phone device for a developer/hacker person. '''This is not meant for regular (Maemo 5) users. Using this release will probably void any warranty and there is no (other than community-based) support available.'''

=== Target ===
The focus is on meeting the non-functional targets (such as performance) rather than number of features. This will hopefully encourage more people to use MeeGo on N900, and continue enhancing the functionality or build new stuff. Developer Edition is based on MeeGo 1.2 handset trunk content, and selected community contributions ([[ARM/N900/CoolStuff|see the candidates]]). Core MeeGo 1.2 Handset features can be found in [https://bugs.meego.com/report.cgi?x_axis_field=product&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=MeeGo+Features&product=MeeGo+Core+OS+Features&product=MeeGo+Handset+Features&version=1.0&version=1.1&version=1.2&version=1.0&version=1.1&version=1.2&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=ACCEPTED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bug_id_type=anyexact&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= featurezilla], and features of DE not yet implemented from [[ARM/N900/Configuration|Configuration list.]]

== Key features ==
These use cases shall be the prominent ones in the Developer Edition. (If you want to promote a feature to this list, please add it to the feedback section first.)

'''Cellular voice calls''' (Dialer, People)

* Make voice calls (input number directly, initiate from Contacts, initiate from Call history)
* Receive calls
* Default ringtone plays
* Volume control works via System UI
* SIM PIN entry support

'''SMS''' (SMS, People)
* Send new SMS (input number, send from Contacts)
* Receive SMS, and reply to sender

'''Browser use over WLAN''' (Browser, Settings)
* Able to connect to WLAN AP (with security etc.)
* Open a complex modern website (eg. gmail.com)

'''Camera''' (meegocamera)
* Still image capture
* Support for N900 keys (zoom, capture)

'''Common SW''' (Settings, xterm, lock)

Common components such as System UI, Home screen etc. shall be made functional so that basic device usage is smooth and fast. N900 device specific features such as keys, display and battery will be optimized. [[SDK|MeeGo SDK]] fully supports this edition, as it is MeeGo 1.2 compliant.

== Status ==
The maturity of Developer Edition image, can be seen from the [[ARM/N900/Status|Status page.]]

== Installing and running ==
Image download and installing instructions can be found from [[N900#Install|N900 page,]] please refer to them for more instructions.

* [[N900#Install|Download and install]] instructions page.
* [[ARM/N900/Status|Status and reports]] of the latest image.
* [[ARM/N900/CoolStuff|Applications and accessories]] for the Developer Edition.

== Release schedules ==

This shows the '''release schedule''' and content. It should be understood that Developer Edition is still based on "best-effort" model, so this might change any time. If you want to make sure targets are kept, please join the project and help us. For more detailed list of features that are implemented on the releases, look in the [[ARM/N900/Configuration|Configuration page.]]

* '''"Summer release"''' by end of June, targets are to be refined based on beta achievement and community activity.
* '''[[ARM/N900/SF2011|MeeGo Conference release]]''': on week 20, see the [[ARM/N900/ReleaseProcess/Plan]].
** [http://repository.maemo.org/meego/n900-de/daily/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ Download here].
** Known issues: Coming soon.
* '''Alpha release''': on week 15
** Official DE image available with key overlays on top of MeeGo 1.2 trunk (see [[ARM/N900/Configuration]]).
** Calls, SMS, Browser and Camera should be in a demo-able state (MeeGo Summit FI).
** Key performance and usability items fixed (PM kernel, backlight control)
** [http://repository.maemo.org/meego/n900-de/archive/1.1.99.2.20110412.6.DE.2011-04-15.1/images/mg-handset-armv7nhl-n900-de-acceptance/ Download here].

== I want to help! ==
Willing to contribute the code to DE/MeeGo, but wondering where to start from? Learn the ropes from the MeeGo experts! This [[Media:Meegokickoff.pdf|material (meego developer's journey)]] gives the overview on the daily development workflow.

Some more concrete steps:

* Join [http://lists.meego.com/listinfo/meego-porting meego-porting@meego.com] and [http://lists.meego.com/listinfo/meego-handset meego-handset@meego.com] mailing lists
* Hang out in [http://webchat.freenode.net/?channels=#meego-arm #meego-arm IRC channel on irc.freenode.net]
* Join [[ARM/N900/DeveloperEdition/Meetings|weekly team meetings]] are held in the public IRC. This meeting is registered on the [[MeeGo-Meeting_IRC_Schedule|MeeGo IRC Meeting Page]]. The agenda and the archives are also available.
* Follow [http://qa-reports.meego.com/1.2/Handset/Acceptance/N900 acceptance testing reports] and see if there's anything of your interest you'd like to work on.
* Play a little with Tablet UX pre-alpha as it's possible the same applications will be replacing some of the Handset UX ones. Experiments are being tried with the Tablet UX on N900. Find more details on [[ARM/N900/TabletUX]].
* Look into learning QML if you haven't already.
* To contribute fixes see [[ARM/N900/ReleaseProcess]].
* Would like to contribute the test cases? You will find the useful information [[Quality|here]].
* Would like to contribute artwork? See [[ARM/N900/Artwork]].
* Look through [[ARM/N900/Developers|Developers page,]] for tips and tricks.

== Organization ==
Core team, of Developer Edition, is formed in and around Nokia. In addition to core team, we hope to see growing community working on this. There is something for everybody to contribute be it bugs, code, artwork or something else. Core team itself has been divided into following categories:

* Program lead: [http://meego.com/users/bittinen Mika Leppinen]
** R&D lead: [http://meego.com/users/msugano Makoto Sugano]
*** [[ARM/N900/VoiceSMS|Voice/SMS]] team lead: [http://meego.com/users/sabotage Shane Bryan]. *
*** [[ARM/N900/Browser|Browser/WLAN]] team lead: [http://meego.com/users/vesku Vesa-Matti Hartikainen]
*** [[ARM/N900/Common|Common SW]] team lead: [http://meego.com/users/harrihakulinen Harri Hakulinen]. **
*** [[ARM/N900/ReleaseProcess|Release & integration]]: [http://meego.com/users/ericlr Eric Le Roux], [http://meego.com/users/stskeeps Carsten Munk], [http://meego.com/users/sage Marko Saukko].
** [[ARM/N900/QA|QA]]: [http://meego.com/users/jaritah Jari Tahvanainen], [http://meego.com/users/markraja Marko Rajala]
** [[ARM/N900/PM|Product management]]: [http://meego.com/users/jukkaeklund Jukka Eklund], [http://meego.com/users/samipienimaki Sami Pienimäki]

<nowiki>*</nowiki>This project is merged with the MeeGo mainstream [[Project/Dialer|Dialer project.]] 
<nowiki>**</nowiki>Includes the [[ARM/N900/HW_Adaptation_team|Hardware Adaptation]] (maintained by [http://meego.com/users/stskeeps Carsten Munk]).

== FAQ ==

Q. Let's assume my bug fix was accepted only in the DE, but rejected in the official 1.2. What do we do with the bug? 
A. Submit the fix to 1.3. Change the status to "RESOLVED". Comment that the fix is available in DE & 1.3.

Q. Which SD card should I be using? 
A. Class 6 and higher. The class has the impact on the performance.

Q. Where can I download the N900 DE release? 
A. See [[N900#Install|installation instructions]]

Q. What is the UI of DE going to be? 
A. Based on what's available on MeeGo trunk. At the moment we work with the MeeGo 1.1-originated Handset UX and apps. We are evaluating the new tablet-originated UX and apps (see [[ARM/N900/TabletUX]]). This is still to be decided, and there might be even multiple options for the user to select.

== Ideas, feedback etc. ==

Please add stuff to the [[ARM/N900/Ideas|Ideas]] page.

[[File:Splash-developers.png]]

[[Category:N900]]

ARM/N900

2011-05-27T12:49:18Z

Hanshoi: /* MeeGo 1.2 Developer Edition for Nokia N900 */

= MeeGo 1.2 Developer Edition for Nokia N900=

'''What's hot:'''
Test the '''MeeGoConf/SF release''' of the MeeGo 1.2 Developer Edition for N900: [http://repository.maemo.org/meego/n900-de/daily/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ download] - [[#Installing_and_running|install]] - [[ARM/N900/CoolStuff|cool stuff]]

== Introduction ==
The target of this activity is to make a Developer Edition of MeeGo for the Nokia N900 device. This Developer Edition is an 'overlay' constructed above the current core MeeGo 1.2. The DE project is working as a draft of a MeeGo handset image, to make possible the MeeGo development on your N900 hardware. Being a draft it will not take into account all features commonly present in a handset OS. To see what features will be implemented look [[#Key_features]]. Flashed with this edition N900 will be usable as a primary phone device for a developer/hacker person. '''This is not meant for regular (Maemo 5) users. Using this release will probably void any warranty and there is no (other than community-based) support available.'''

=== Target ===
The focus is on meeting the non-functional targets (such as performance) rather than number of features. This will hopefully encourage more people to use MeeGo on N900, and continue enhancing the functionality or build new stuff. Developer Edition is based on MeeGo 1.2 handset trunk content, and selected community contributions ([[ARM/N900/CoolStuff|see the candidates]]). Core MeeGo 1.2 Handset features can be found in [https://bugs.meego.com/report.cgi?x_axis_field=product&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=MeeGo+Features&product=MeeGo+Core+OS+Features&product=MeeGo+Handset+Features&version=1.0&version=1.1&version=1.2&version=1.0&version=1.1&version=1.2&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=ACCEPTED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bug_id_type=anyexact&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= featurezilla], and features of DE not yet implemented from [[ARM/N900/Configuration|Configuration list.]]

== Key features ==
These use cases shall be the prominent ones in the Developer Edition. (If you want to promote a feature to this list, please add it to the feedback section first.)

'''Cellular voice calls''' (Dialer, People)

* Make voice calls (input number directly, initiate from Contacts, initiate from Call history)
* Receive calls
* Default ringtone plays
* Volume control works via System UI
* SIM PIN entry support

'''SMS''' (SMS, People)
* Send new SMS (input number, send from Contacts)
* Receive SMS, and reply to sender

'''Browser use over WLAN''' (Browser, Settings)
* Able to connect to WLAN AP (with security etc.)
* Open a complex modern website (eg. gmail.com)

'''Camera''' (meegocamera)
* Still image capture
* Support for N900 keys (zoom, capture)

'''Common SW''' (Settings, xterm, lock)

Common components such as System UI, Home screen etc. shall be made functional so that basic device usage is smooth and fast. N900 device specific features such as keys, display and battery will be optimized. [[SDK|MeeGo SDK]] fully supports this edition, as it is MeeGo 1.2 compliant.

== Status ==
The maturity of Developer Edition image, can be seen from the [[ARM/N900/Status|Status page.]]

== Installing and running ==
Image download and installing instructions can be found from [[N900#Install|N900 page,]] please refer to them for more instructions.

* [[N900#Install|Download and install]] instructions page.
* [[ARM/N900/Status|Status and reports]] of the latest image.
* [[ARM/N900/CoolStuff|Applications and accessories]] for the Developer Edition.

== Release schedules ==

This shows the '''release schedule''' and content. It should be understood that Developer Edition is still based on "best-effort" model, so this might change any time. If you want to make sure targets are kept, please join the project and help us.

* '''"Summer release"''' by end of June, targets are to be refined based on beta achievement and community activity.
* '''[[ARM/N900/SF2011|MeeGo Conference release]]''': on week 20, see the [[ARM/N900/ReleaseProcess/Plan]].
** [http://repository.maemo.org/meego/n900-de/daily/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ Download here].
** Known issues: Coming soon.
* '''Alpha release''': on week 15
** Official DE image available with key overlays on top of MeeGo 1.2 trunk (see [[ARM/N900/Configuration]]).
** Calls, SMS, Browser and Camera should be in a demo-able state (MeeGo Summit FI).
** Key performance and usability items fixed (PM kernel, backlight control)
** [http://repository.maemo.org/meego/n900-de/archive/1.1.99.2.20110412.6.DE.2011-04-15.1/images/mg-handset-armv7nhl-n900-de-acceptance/ Download here].

== I want to help! ==
Willing to contribute the code to DE/MeeGo, but wondering where to start from? Learn the ropes from the MeeGo experts! This [[Media:Meegokickoff.pdf|material (meego developer's journey)]] gives the overview on the daily development workflow.

Some more concrete steps:

* Join [http://lists.meego.com/listinfo/meego-porting meego-porting@meego.com] and [http://lists.meego.com/listinfo/meego-handset meego-handset@meego.com] mailing lists
* Hang out in [http://webchat.freenode.net/?channels=#meego-arm #meego-arm IRC channel on irc.freenode.net]
* Join [[ARM/N900/DeveloperEdition/Meetings|weekly team meetings]] are held in the public IRC. This meeting is registered on the [[MeeGo-Meeting_IRC_Schedule|MeeGo IRC Meeting Page]]. The agenda and the archives are also available.
* Follow [http://qa-reports.meego.com/1.2/Handset/Acceptance/N900 acceptance testing reports] and see if there's anything of your interest you'd like to work on.
* Play a little with Tablet UX pre-alpha as it's possible the same applications will be replacing some of the Handset UX ones. Experiments are being tried with the Tablet UX on N900. Find more details on [[ARM/N900/TabletUX]].
* Look into learning QML if you haven't already.
* To contribute fixes see [[ARM/N900/ReleaseProcess]].
* Would like to contribute the test cases? You will find the useful information [[Quality|here]].
* Would like to contribute artwork? See [[ARM/N900/Artwork]].
* Look through [[ARM/N900/Developers|Developers page,]] for tips and tricks.

== Organization ==
Core team, of Developer Edition, is formed in and around Nokia. In addition to core team, we hope to see growing community working on this. There is something for everybody to contribute be it bugs, code, artwork or something else. Core team itself has been divided into following categories:

* Program lead: [http://meego.com/users/bittinen Mika Leppinen]
** R&D lead: [http://meego.com/users/msugano Makoto Sugano]
*** [[ARM/N900/VoiceSMS|Voice/SMS]] team lead: [http://meego.com/users/sabotage Shane Bryan]. *
*** [[ARM/N900/Browser|Browser/WLAN]] team lead: [http://meego.com/users/vesku Vesa-Matti Hartikainen]
*** [[ARM/N900/Common|Common SW]] team lead: [http://meego.com/users/harrihakulinen Harri Hakulinen]. **
*** [[ARM/N900/ReleaseProcess|Release & integration]]: [http://meego.com/users/ericlr Eric Le Roux], [http://meego.com/users/stskeeps Carsten Munk], [http://meego.com/users/sage Marko Saukko].
** [[ARM/N900/QA|QA]]: [http://meego.com/users/jaritah Jari Tahvanainen], [http://meego.com/users/markraja Marko Rajala]
** [[ARM/N900/PM|Product management]]: [http://meego.com/users/jukkaeklund Jukka Eklund], [http://meego.com/users/samipienimaki Sami Pienimäki]

<nowiki>*</nowiki>This project is merged with the MeeGo mainstream [[Project/Dialer|Dialer project.]] 
<nowiki>**</nowiki>Includes the [[ARM/N900/HW_Adaptation_team|Hardware Adaptation]] (maintained by [http://meego.com/users/stskeeps Carsten Munk]).

== FAQ ==

Q. Let's assume my bug fix was accepted only in the DE, but rejected in the official 1.2. What do we do with the bug? 
A. Submit the fix to 1.3. Change the status to "RESOLVED". Comment that the fix is available in DE & 1.3.

Q. Which SD card should I be using? 
A. Class 6 and higher. The class has the impact on the performance.

Q. Where can I download the N900 DE release? 
A. See [[N900#Install|installation instructions]]

Q. What is the UI of DE going to be? 
A. Based on what's available on MeeGo trunk. At the moment we work with the MeeGo 1.1-originated Handset UX and apps. We are evaluating the new tablet-originated UX and apps (see [[ARM/N900/TabletUX]]). This is still to be decided, and there might be even multiple options for the user to select.

== Ideas, feedback etc. ==

Please add stuff to the [[ARM/N900/Ideas|Ideas]] page.

[[File:Splash-developers.png]]

[[Category:N900]]

ARM/N900

2011-05-27T12:48:20Z

Hanshoi: /* MeeGo 1.2 Developer Edition for Nokia N900 */

= MeeGo 1.2 Developer Edition for Nokia N900=

'''What's hot:'''
Test the '''MeeGoConf/SF release''' of the MeeGo 1.2 Developer Edition for N900: [http://repository.maemo.org/meego/n900-de/daily/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ download] - [[#Installing_and_running|install]] - [[ARM/N900/CoolStuff|cool stuff]]

== Introduction ==
The target of this activity is to make a Developer Edition of MeeGo for the Nokia N900 device. This Developer Edition is an 'overlay' constructed above the current core MeeGo 1.2. The DE project is working as a draft of a MeeGo handset image, to make possible the MeeGo development on your N900 hardware. Being a draft it will not take into account all features commonly present in a handset OS. To see what features will be implemented look [[#Key_features]]. Flashed with this edition N900 will be usable as a primary phone device for a developer/hacker person. '''This is not meant for regular (Maemo 5) users. Using this release will probably void any warranty and there is no (other than community-based) support available.'''

=== Target ===
The focus is on meeting the non-functional targets (such as performance) rather than number of features. This will hopefully encourage more people to use MeeGo on N900, and continue enhancing the functionality or build new stuff. Developer Edition is based on MeeGo 1.2 handset trunk content, and selected community contributions ([[ARM/N900/CoolStuff|see the candidates]]). Core MeeGo 1.2 Handset features can be found in [https://bugs.meego.com/report.cgi?x_axis_field=product&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=MeeGo+Features&product=MeeGo+Core+OS+Features&product=MeeGo+Handset+Features&version=1.0&version=1.1&version=1.2&version=1.0&version=1.1&version=1.2&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=ACCEPTED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bug_id_type=anyexact&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= featurezilla], and features of DE not yet implemented from [[ARM/N900/Configuration|Configuration list.]]

== Key features ==
These use cases shall be the prominent ones in the Developer Edition. (If you want to promote a feature to this list, please add it to the feedback section first.)

'''Cellular voice calls''' (Dialer, People)

* Make voice calls (input number directly, initiate from Contacts, initiate from Call history)
* Receive calls
* Default ringtone plays
* Volume control works via System UI
* SIM PIN entry support

'''SMS''' (SMS, People)
* Send new SMS (input number, send from Contacts)
* Receive SMS, and reply to sender

'''Browser use over WLAN''' (Browser, Settings)
* Able to connect to WLAN AP (with security etc.)
* Open a complex modern website (eg. gmail.com)

'''Camera''' (meegocamera)
* Still image capture
* Support for N900 keys (zoom, capture)

'''Common SW''' (Settings, xterm, lock)

Common components such as System UI, Home screen etc. shall be made functional so that basic device usage is smooth and fast. N900 device specific features such as keys, display and battery will be optimized. [[SDK|MeeGo SDK]] fully supports this edition, as it is MeeGo 1.2 compliant.

== Status ==
The maturity of Developer Edition image, can be seen from the [[ARM/N900/Status|Status page.]]

== Installing and running ==
Image download and installing instructions can be found from [[N900#Install|N900 page,]] please refer to them for more instructions.

* [[N900#Install|Download and install]] instructions page.
* [[ARM/N900/Status|Status and reports]] of the latest image.
* [[ARM/N900/CoolStuff|Applications and accessories]] for the Developer Edition.

== I want to help! ==
Willing to contribute the code to DE/MeeGo, but wondering where to start from? Learn the ropes from the MeeGo experts! This [[Media:Meegokickoff.pdf|material (meego developer's journey)]] gives the overview on the daily development workflow.

Some more concrete steps:

* Join [http://lists.meego.com/listinfo/meego-porting meego-porting@meego.com] and [http://lists.meego.com/listinfo/meego-handset meego-handset@meego.com] mailing lists
* Hang out in [http://webchat.freenode.net/?channels=#meego-arm #meego-arm IRC channel on irc.freenode.net]
* Join [[ARM/N900/DeveloperEdition/Meetings|weekly team meetings]] are held in the public IRC. This meeting is registered on the [[MeeGo-Meeting_IRC_Schedule|MeeGo IRC Meeting Page]]. The agenda and the archives are also available.
* Follow [http://qa-reports.meego.com/1.2/Handset/Acceptance/N900 acceptance testing reports] and see if there's anything of your interest you'd like to work on.
* Play a little with Tablet UX pre-alpha as it's possible the same applications will be replacing some of the Handset UX ones. Experiments are being tried with the Tablet UX on N900. Find more details on [[ARM/N900/TabletUX]].
* Look into learning QML if you haven't already.
* To contribute fixes see [[ARM/N900/ReleaseProcess]].
* Would like to contribute the test cases? You will find the useful information [[Quality|here]].
* Would like to contribute artwork? See [[ARM/N900/Artwork]].
* Look through [[ARM/N900/Developers|Developers page,]] for tips and tricks.

== Release schedules ==

This shows the '''release schedule''' and content. It should be understood that Developer Edition is still based on "best-effort" model, so this might change any time. If you want to make sure targets are kept, please join the project and help us.

* '''"Summer release"''' by end of June, targets are to be refined based on beta achievement and community activity.
* '''[[ARM/N900/SF2011|MeeGo Conference release]]''': on week 20, see the [[ARM/N900/ReleaseProcess/Plan]].
** [http://repository.maemo.org/meego/n900-de/daily/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ Download here].
** Known issues: Coming soon.
* '''Alpha release''': on week 15
** Official DE image available with key overlays on top of MeeGo 1.2 trunk (see [[ARM/N900/Configuration]]).
** Calls, SMS, Browser and Camera should be in a demo-able state (MeeGo Summit FI).
** Key performance and usability items fixed (PM kernel, backlight control)
** [http://repository.maemo.org/meego/n900-de/archive/1.1.99.2.20110412.6.DE.2011-04-15.1/images/mg-handset-armv7nhl-n900-de-acceptance/ Download here].

== Organization ==
Core team, of Developer Edition, is formed in and around Nokia. In addition to core team, we hope to see growing community working on this. There is something for everybody to contribute be it bugs, code, artwork or something else. Core team itself has been divided into following categories:

* Program lead: [http://meego.com/users/bittinen Mika Leppinen]
** R&D lead: [http://meego.com/users/msugano Makoto Sugano]
*** [[ARM/N900/VoiceSMS|Voice/SMS]] team lead: [http://meego.com/users/sabotage Shane Bryan]. *
*** [[ARM/N900/Browser|Browser/WLAN]] team lead: [http://meego.com/users/vesku Vesa-Matti Hartikainen]
*** [[ARM/N900/Common|Common SW]] team lead: [http://meego.com/users/harrihakulinen Harri Hakulinen]. **
*** [[ARM/N900/ReleaseProcess|Release & integration]]: [http://meego.com/users/ericlr Eric Le Roux], [http://meego.com/users/stskeeps Carsten Munk], [http://meego.com/users/sage Marko Saukko].
** [[ARM/N900/QA|QA]]: [http://meego.com/users/jaritah Jari Tahvanainen], [http://meego.com/users/markraja Marko Rajala]
** [[ARM/N900/PM|Product management]]: [http://meego.com/users/jukkaeklund Jukka Eklund], [http://meego.com/users/samipienimaki Sami Pienimäki]

<nowiki>*</nowiki>This project is merged with the MeeGo mainstream [[Project/Dialer|Dialer project.]] 
<nowiki>**</nowiki>Includes the [[ARM/N900/HW_Adaptation_team|Hardware Adaptation]] (maintained by [http://meego.com/users/stskeeps Carsten Munk]).

== FAQ ==

Q. Let's assume my bug fix was accepted only in the DE, but rejected in the official 1.2. What do we do with the bug? 
A. Submit the fix to 1.3. Change the status to "RESOLVED". Comment that the fix is available in DE & 1.3.

Q. Which SD card should I be using? 
A. Class 6 and higher. The class has the impact on the performance.

Q. Where can I download the N900 DE release? 
A. See [[N900#Install|installation instructions]]

Q. What is the UI of DE going to be? 
A. Based on what's available on MeeGo trunk. At the moment we work with the MeeGo 1.1-originated Handset UX and apps. We are evaluating the new tablet-originated UX and apps (see [[ARM/N900/TabletUX]]). This is still to be decided, and there might be even multiple options for the user to select.

== Ideas, feedback etc. ==

Please add stuff to the [[ARM/N900/Ideas|Ideas]] page.

[[File:Splash-developers.png]]

[[Category:N900]]

ARM/N900

2011-05-27T12:47:54Z

Hanshoi: /* Target schedules */

= MeeGo 1.2 Developer Edition for Nokia N900=

'''What's hot:'''
Test the '''MeeGoConf/SF release''' of the MeeGo 1.2 Developer Edition for N900: [http://repository.maemo.org/meego/n900-de/daily/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ download] - [[#Installing_and_running|install]] - [[ARM/N900/CoolStuff|cool stuff]]

== Introduction ==
The target of this activity is to make a Developer Edition of MeeGo for the Nokia N900 device. This Developer Edition is an 'overlay' constructed above the current core MeeGo 1.2. The DE project is working as a draft of a MeeGo handset image, to make possible the MeeGo development on your N900 hardware. Being a draft it will not take into account all features commonly present in a handset OS. To see what features will be implemented look [[#Key_features]]. Flashed with this edition N900 will be usable as a primary phone device for a developer/hacker person. '''This is not meant for regular (Maemo 5) users. Using this release will probably void any warranty and there is no (other than community-based) support available.'''

=== Target ===
The focus is on meeting the non-functional targets (such as performance) rather than number of features. This will hopefully encourage more people to use MeeGo on N900, and continue enhancing the functionality or build new stuff. Developer Edition is based on MeeGo 1.2 handset trunk content, and selected community contributions ([[ARM/N900/CoolStuff|see the candidates]]). Core MeeGo 1.2 Handset features can be found in [https://bugs.meego.com/report.cgi?x_axis_field=product&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=MeeGo+Features&product=MeeGo+Core+OS+Features&product=MeeGo+Handset+Features&version=1.0&version=1.1&version=1.2&version=1.0&version=1.1&version=1.2&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=ACCEPTED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bug_id_type=anyexact&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= featurezilla], and features of DE not yet implemented from [[ARM/N900/Configuration|Configuration list.]]

== Key features ==
These use cases shall be the prominent ones in the Developer Edition. (If you want to promote a feature to this list, please add it to the feedback section first.)

'''Cellular voice calls''' (Dialer, People)

* Make voice calls (input number directly, initiate from Contacts, initiate from Call history)
* Receive calls
* Default ringtone plays
* Volume control works via System UI
* SIM PIN entry support

'''SMS''' (SMS, People)
* Send new SMS (input number, send from Contacts)
* Receive SMS, and reply to sender

'''Browser use over WLAN''' (Browser, Settings)
* Able to connect to WLAN AP (with security etc.)
* Open a complex modern website (eg. gmail.com)

'''Camera''' (meegocamera)
* Still image capture
* Support for N900 keys (zoom, capture)

'''Common SW''' (Settings, xterm, lock)

Common components such as System UI, Home screen etc. shall be made functional so that basic device usage is smooth and fast. N900 device specific features such as keys, display and battery will be optimized. [[SDK|MeeGo SDK]] fully supports this edition, as it is MeeGo 1.2 compliant.

== Release schedules ==

This shows the '''release schedule''' and content. It should be understood that Developer Edition is still based on "best-effort" model, so this might change any time. If you want to make sure targets are kept, please join the project and help us.

* '''"Summer release"''' by end of June, targets are to be refined based on beta achievement and community activity.
* '''[[ARM/N900/SF2011|MeeGo Conference release]]''': on week 20, see the [[ARM/N900/ReleaseProcess/Plan]].
** [http://repository.maemo.org/meego/n900-de/daily/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ Download here].
** Known issues: Coming soon.
* '''Alpha release''': on week 15
** Official DE image available with key overlays on top of MeeGo 1.2 trunk (see [[ARM/N900/Configuration]]).
** Calls, SMS, Browser and Camera should be in a demo-able state (MeeGo Summit FI).
** Key performance and usability items fixed (PM kernel, backlight control)
** [http://repository.maemo.org/meego/n900-de/archive/1.1.99.2.20110412.6.DE.2011-04-15.1/images/mg-handset-armv7nhl-n900-de-acceptance/ Download here].

== Status ==
The maturity of Developer Edition image, can be seen from the [[ARM/N900/Status|Status page.]]

== Installing and running ==
Image download and installing instructions can be found from [[N900#Install|N900 page,]] please refer to them for more instructions.

* [[N900#Install|Download and install]] instructions page.
* [[ARM/N900/Status|Status and reports]] of the latest image.
* [[ARM/N900/CoolStuff|Applications and accessories]] for the Developer Edition.

== I want to help! ==
Willing to contribute the code to DE/MeeGo, but wondering where to start from? Learn the ropes from the MeeGo experts! This [[Media:Meegokickoff.pdf|material (meego developer's journey)]] gives the overview on the daily development workflow.

Some more concrete steps:

* Join [http://lists.meego.com/listinfo/meego-porting meego-porting@meego.com] and [http://lists.meego.com/listinfo/meego-handset meego-handset@meego.com] mailing lists
* Hang out in [http://webchat.freenode.net/?channels=#meego-arm #meego-arm IRC channel on irc.freenode.net]
* Join [[ARM/N900/DeveloperEdition/Meetings|weekly team meetings]] are held in the public IRC. This meeting is registered on the [[MeeGo-Meeting_IRC_Schedule|MeeGo IRC Meeting Page]]. The agenda and the archives are also available.
* Follow [http://qa-reports.meego.com/1.2/Handset/Acceptance/N900 acceptance testing reports] and see if there's anything of your interest you'd like to work on.
* Play a little with Tablet UX pre-alpha as it's possible the same applications will be replacing some of the Handset UX ones. Experiments are being tried with the Tablet UX on N900. Find more details on [[ARM/N900/TabletUX]].
* Look into learning QML if you haven't already.
* To contribute fixes see [[ARM/N900/ReleaseProcess]].
* Would like to contribute the test cases? You will find the useful information [[Quality|here]].
* Would like to contribute artwork? See [[ARM/N900/Artwork]].
* Look through [[ARM/N900/Developers|Developers page,]] for tips and tricks.

== Organization ==
Core team, of Developer Edition, is formed in and around Nokia. In addition to core team, we hope to see growing community working on this. There is something for everybody to contribute be it bugs, code, artwork or something else. Core team itself has been divided into following categories:

* Program lead: [http://meego.com/users/bittinen Mika Leppinen]
** R&D lead: [http://meego.com/users/msugano Makoto Sugano]
*** [[ARM/N900/VoiceSMS|Voice/SMS]] team lead: [http://meego.com/users/sabotage Shane Bryan]. *
*** [[ARM/N900/Browser|Browser/WLAN]] team lead: [http://meego.com/users/vesku Vesa-Matti Hartikainen]
*** [[ARM/N900/Common|Common SW]] team lead: [http://meego.com/users/harrihakulinen Harri Hakulinen]. **
*** [[ARM/N900/ReleaseProcess|Release & integration]]: [http://meego.com/users/ericlr Eric Le Roux], [http://meego.com/users/stskeeps Carsten Munk], [http://meego.com/users/sage Marko Saukko].
** [[ARM/N900/QA|QA]]: [http://meego.com/users/jaritah Jari Tahvanainen], [http://meego.com/users/markraja Marko Rajala]
** [[ARM/N900/PM|Product management]]: [http://meego.com/users/jukkaeklund Jukka Eklund], [http://meego.com/users/samipienimaki Sami Pienimäki]

<nowiki>*</nowiki>This project is merged with the MeeGo mainstream [[Project/Dialer|Dialer project.]] 
<nowiki>**</nowiki>Includes the [[ARM/N900/HW_Adaptation_team|Hardware Adaptation]] (maintained by [http://meego.com/users/stskeeps Carsten Munk]).

== FAQ ==

Q. Let's assume my bug fix was accepted only in the DE, but rejected in the official 1.2. What do we do with the bug? 
A. Submit the fix to 1.3. Change the status to "RESOLVED". Comment that the fix is available in DE & 1.3.

Q. Which SD card should I be using? 
A. Class 6 and higher. The class has the impact on the performance.

Q. Where can I download the N900 DE release? 
A. See [[N900#Install|installation instructions]]

Q. What is the UI of DE going to be? 
A. Based on what's available on MeeGo trunk. At the moment we work with the MeeGo 1.1-originated Handset UX and apps. We are evaluating the new tablet-originated UX and apps (see [[ARM/N900/TabletUX]]). This is still to be decided, and there might be even multiple options for the user to select.

== Ideas, feedback etc. ==

Please add stuff to the [[ARM/N900/Ideas|Ideas]] page.

[[File:Splash-developers.png]]

[[Category:N900]]

ARM/N900

2011-05-27T12:45:53Z

Hanshoi: /* Target schedules */

= MeeGo 1.2 Developer Edition for Nokia N900=

'''What's hot:'''
Test the '''MeeGoConf/SF release''' of the MeeGo 1.2 Developer Edition for N900: [http://repository.maemo.org/meego/n900-de/daily/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ download] - [[#Installing_and_running|install]] - [[ARM/N900/CoolStuff|cool stuff]]

== Introduction ==
The target of this activity is to make a Developer Edition of MeeGo for the Nokia N900 device. This Developer Edition is an 'overlay' constructed above the current core MeeGo 1.2. The DE project is working as a draft of a MeeGo handset image, to make possible the MeeGo development on your N900 hardware. Being a draft it will not take into account all features commonly present in a handset OS. To see what features will be implemented look [[#Key_features]]. Flashed with this edition N900 will be usable as a primary phone device for a developer/hacker person. '''This is not meant for regular (Maemo 5) users. Using this release will probably void any warranty and there is no (other than community-based) support available.'''

=== Target ===
The focus is on meeting the non-functional targets (such as performance) rather than number of features. This will hopefully encourage more people to use MeeGo on N900, and continue enhancing the functionality or build new stuff. Developer Edition is based on MeeGo 1.2 handset trunk content, and selected community contributions ([[ARM/N900/CoolStuff|see the candidates]]). Core MeeGo 1.2 Handset features can be found in [https://bugs.meego.com/report.cgi?x_axis_field=product&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=MeeGo+Features&product=MeeGo+Core+OS+Features&product=MeeGo+Handset+Features&version=1.0&version=1.1&version=1.2&version=1.0&version=1.1&version=1.2&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=ACCEPTED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bug_id_type=anyexact&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= featurezilla], and features of DE not yet implemented from [[ARM/N900/Configuration|Configuration list.]]

== Key features ==
These use cases shall be the prominent ones in the Developer Edition. (If you want to promote a feature to this list, please add it to the feedback section first.)

'''Cellular voice calls''' (Dialer, People)

* Make voice calls (input number directly, initiate from Contacts, initiate from Call history)
* Receive calls
* Default ringtone plays
* Volume control works via System UI
* SIM PIN entry support

'''SMS''' (SMS, People)
* Send new SMS (input number, send from Contacts)
* Receive SMS, and reply to sender

'''Browser use over WLAN''' (Browser, Settings)
* Able to connect to WLAN AP (with security etc.)
* Open a complex modern website (eg. gmail.com)

'''Camera''' (meegocamera)
* Still image capture
* Support for N900 keys (zoom, capture)

'''Common SW''' (Settings, xterm, lock)

Common components such as System UI, Home screen etc. shall be made functional so that basic device usage is smooth and fast. N900 device specific features such as keys, display and battery will be optimized. [[SDK|MeeGo SDK]] fully supports this edition, as it is MeeGo 1.2 compliant.

== Target schedules ==

This shows the '''target schedule''' and content. It should be understood that Developer Edition is still based on "best-effort" model, so this might change any time. If you want to make sure targets are kept, please join the project and help us.

* '''"Summer release"''' by end of June, targets are to be refined based on beta achievement and community activity.
* '''[[ARM/N900/SF2011|MeeGo Conference release]]''': on week 20, see the [[ARM/N900/ReleaseProcess/Plan]].
** [http://repository.maemo.org/meego/n900-de/daily/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ Download here].
** Known issues: Coming soon.
* '''Alpha release''': on week 15
** Official DE image available with key overlays on top of MeeGo 1.2 trunk (see [[ARM/N900/Configuration]]).
** Calls, SMS, Browser and Camera should be in a demo-able state (MeeGo Summit FI).
** Key performance and usability items fixed (PM kernel, backlight control)
** [http://repository.maemo.org/meego/n900-de/archive/1.1.99.2.20110412.6.DE.2011-04-15.1/images/mg-handset-armv7nhl-n900-de-acceptance/ Download here].

== Status ==
The maturity of Developer Edition image, can be seen from the [[ARM/N900/Status|Status page.]]

== Installing and running ==
Image download and installing instructions can be found from [[N900#Install|N900 page,]] please refer to them for more instructions.

* [[N900#Install|Download and install]] instructions page.
* [[ARM/N900/Status|Status and reports]] of the latest image.
* [[ARM/N900/CoolStuff|Applications and accessories]] for the Developer Edition.

== I want to help! ==
Willing to contribute the code to DE/MeeGo, but wondering where to start from? Learn the ropes from the MeeGo experts! This [[Media:Meegokickoff.pdf|material (meego developer's journey)]] gives the overview on the daily development workflow.

Some more concrete steps:

* Join [http://lists.meego.com/listinfo/meego-porting meego-porting@meego.com] and [http://lists.meego.com/listinfo/meego-handset meego-handset@meego.com] mailing lists
* Hang out in [http://webchat.freenode.net/?channels=#meego-arm #meego-arm IRC channel on irc.freenode.net]
* Join [[ARM/N900/DeveloperEdition/Meetings|weekly team meetings]] are held in the public IRC. This meeting is registered on the [[MeeGo-Meeting_IRC_Schedule|MeeGo IRC Meeting Page]]. The agenda and the archives are also available.
* Follow [http://qa-reports.meego.com/1.2/Handset/Acceptance/N900 acceptance testing reports] and see if there's anything of your interest you'd like to work on.
* Play a little with Tablet UX pre-alpha as it's possible the same applications will be replacing some of the Handset UX ones. Experiments are being tried with the Tablet UX on N900. Find more details on [[ARM/N900/TabletUX]].
* Look into learning QML if you haven't already.
* To contribute fixes see [[ARM/N900/ReleaseProcess]].
* Would like to contribute the test cases? You will find the useful information [[Quality|here]].
* Would like to contribute artwork? See [[ARM/N900/Artwork]].
* Look through [[ARM/N900/Developers|Developers page,]] for tips and tricks.

== Organization ==
Core team, of Developer Edition, is formed in and around Nokia. In addition to core team, we hope to see growing community working on this. There is something for everybody to contribute be it bugs, code, artwork or something else. Core team itself has been divided into following categories:

* Program lead: [http://meego.com/users/bittinen Mika Leppinen]
** R&D lead: [http://meego.com/users/msugano Makoto Sugano]
*** [[ARM/N900/VoiceSMS|Voice/SMS]] team lead: [http://meego.com/users/sabotage Shane Bryan]. *
*** [[ARM/N900/Browser|Browser/WLAN]] team lead: [http://meego.com/users/vesku Vesa-Matti Hartikainen]
*** [[ARM/N900/Common|Common SW]] team lead: [http://meego.com/users/harrihakulinen Harri Hakulinen]. **
*** [[ARM/N900/ReleaseProcess|Release & integration]]: [http://meego.com/users/ericlr Eric Le Roux], [http://meego.com/users/stskeeps Carsten Munk], [http://meego.com/users/sage Marko Saukko].
** [[ARM/N900/QA|QA]]: [http://meego.com/users/jaritah Jari Tahvanainen], [http://meego.com/users/markraja Marko Rajala]
** [[ARM/N900/PM|Product management]]: [http://meego.com/users/jukkaeklund Jukka Eklund], [http://meego.com/users/samipienimaki Sami Pienimäki]

<nowiki>*</nowiki>This project is merged with the MeeGo mainstream [[Project/Dialer|Dialer project.]] 
<nowiki>**</nowiki>Includes the [[ARM/N900/HW_Adaptation_team|Hardware Adaptation]] (maintained by [http://meego.com/users/stskeeps Carsten Munk]).

== FAQ ==

Q. Let's assume my bug fix was accepted only in the DE, but rejected in the official 1.2. What do we do with the bug? 
A. Submit the fix to 1.3. Change the status to "RESOLVED". Comment that the fix is available in DE & 1.3.

Q. Which SD card should I be using? 
A. Class 6 and higher. The class has the impact on the performance.

Q. Where can I download the N900 DE release? 
A. See [[N900#Install|installation instructions]]

Q. What is the UI of DE going to be? 
A. Based on what's available on MeeGo trunk. At the moment we work with the MeeGo 1.1-originated Handset UX and apps. We are evaluating the new tablet-originated UX and apps (see [[ARM/N900/TabletUX]]). This is still to be decided, and there might be even multiple options for the user to select.

== Ideas, feedback etc. ==

Please add stuff to the [[ARM/N900/Ideas|Ideas]] page.

[[File:Splash-developers.png]]

[[Category:N900]]

N900

2011-05-27T12:32:08Z

Hanshoi: /* Download image */

[[File:20000101-034513.png|400px|thumb|right]]

= MeeGo for Nokia N900 =
'' "I have N900, and want to try MeeGo on it." '' 
'' "I want to develop MeeGo/Qt applications on my N900 device" '' 
'' "I want to develop MeeGo OS, on existing N900 or other ARM-based device" ''

== Introduction ==
When using MeeGo on the Nokia N900, or other ARM-based handset, it's recommended to use MeeGo [[ARM/N900|Developer Edition]]. [[ARM/N900|Developer Edition]] (DE) is an edition of the core MeeGo 1.2. The [[ARM/N900|DE]] is developed with the ARM and handset compatibility in mind, this way developers already owning a N900 device may start developing with it immediately.

For more information about [[ARM/N900|Developer Edition]], please visit [[ARM/N900|Developer Edition page.]]

== Status ==
The working status of Meego for N900 implementation can be seen on [[ARM/N900/Status|Status page.]]

== Install ==
=== Download image ===
You can choose from several images from our repository, or even [[ARM/Creating ARM image using MeeGo Image Creator|build one yourself.]]

{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
|-
!style="border-style: solid; border-width: 0 1px 1px 0"| Image
!style="border-style: solid; border-width: 0 1px 1px 0"| Description
!style="border-style: solid; border-width: 0 0 1px 0"| Release date
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/daily/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ SF/MeeGoConf Release]
|style="border-style: solid; border-width: 0 1px 1px 0"| San Francisco release, image released at MeeGo conference.(recommended)
|style="border-style: solid; border-width: 0 0 1px 0"| 23.5.2011
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.1.99.2.20110412.6.DE.2011-04-15.1/images/mg-handset-armv7nhl-n900-de-acceptance/ Alpha release]
|style="border-style: solid; border-width: 0 1px 1px 0"| Alpha release of the Meego DE image.
|style="border-style: solid; border-width: 0 0 1px 0"| 15.04.2011
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/ Weekly image]
|style="border-style: solid; border-width: 0 1px 1px 0"| From here you can find the weekly and daily builds of DE image.
|style="border-style: solid; border-width: 0 0 1px 0"|
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [https://meego.com/downloads/releases/1.1/meego-v1.1-handset Meego Core 1.1]
|style="border-style: solid; border-width: 0 1px 1px 0"| Original Meego core 1.1 release for N900.
|style="border-style: solid; border-width: 0 0 1px 0"| 28.10.2010
|}

=== Install image ===
Recommended way is to install MeeGo DE as dual boot to N900, with your Maemo 5 fremantle. However you can choose any one from the list with your own risk.

{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
|-
!style="border-style: solid; border-width: 0 1px 1px 0"| Topic
!style="border-style: solid; border-width: 0 0 1px 0"| Description
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/Dual_Boot|Dual-boot install]]
|style="border-style: solid; border-width: 0 0 1px 0"| Installs Meego as dual boot with your Maemo 5 fremantle. (Default)
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/MMC|MMC Installation]]
|style="border-style: solid; border-width: 0 0 1px 0"| Installs Meego to a external SD card. Does not destroy internal memory of your N900 device, and also a recommended way.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/EMMC| eMMC Installation]]
|style="border-style: solid; border-width: 0 0 1px 0"| Install Meego on the internal memory. This will destroy the existing fremantle installation.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/chroot|Chroot install]]
|style="border-style: solid; border-width: 0 0 1px 0"| Chroot install is a way to try out MeeGo by running it on top of Maemo 5 on your N900 device.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/NFS|NFS-Root over usb networking]]
|style="border-style: solid; border-width: 0 0 1px 0"| With NFS-root install you can run MeeGo natively on your N900, without erasing Maemo 5, without flashing or using SD card. Rootfs speed over USB is the downside.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/U-Boot from scratch|Install U-boot from scratch]]
|style="border-style: solid; border-width: 0 0 1px 0"| If you cannot install uboot from Maemo repo, then use this one to get it installed.
|}

=== Applications ===
If you want to try out some applications on Meego [[ARM/N900|Developer Edition]] get them from [[ARM/N900/CoolStuff|here.]] Eventually applications will be in [[http://apps-beta.meego.com/applications/MeeGo Community apps site]].

== Participate ==
If you are interested to help developing MeeGo or applications for your favorite hardware. Please visit on MeeGo [[ARM/N900|Developer Edition page.]]

== FAQ ==
Q. Where can I download the N900 DE release? 
A. See [[#Download_image]]

Q. Where do I see the maturity of the current image? 
A. See the Developer Edition [[ARM/N900/Status|Status page.]]

Q. My battery is drained, how shall I recharge it? 
A. Look from [[ARM/N900/Recover_From_Drained_Battery|battery recharge guide.]]

Q. I want to install back to Maemo5 as my only operating system, how will I do that? 
A. See the [http://wiki.maemo.org/Updating_the_firmware#N900_2 restore Maemo guide] from Maemo wiki.

Q. I want a usb connection to my N900, how will I do it? 
A. Use ssh. See [[ARM/N900/Tips_and_Tricks/N900_USB_Networking|guide.]]

ARM/N900

2011-05-27T12:31:36Z

Hanshoi: /* Target schedules */

= MeeGo 1.2 Developer Edition for Nokia N900=

'''What's hot:'''
Test the '''MeeGoConf/SF release''' of the MeeGo 1.2 Developer Edition for N900: [http://repository.maemo.org/meego/n900-de/daily/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ download] - [[#Installing_and_running|install]] - [[ARM/N900/CoolStuff|cool stuff]]

== Introduction ==
The target of this activity is to make a Developer Edition of MeeGo for the Nokia N900 device. This Developer Edition is an 'overlay' constructed above the current core MeeGo 1.2. The DE project is working as a draft of a MeeGo handset image, to make possible the MeeGo development on your N900 hardware. Being a draft it will not take into account all features commonly present in a handset OS. To see what features will be implemented look [[#Key_features]]. Flashed with this edition N900 will be usable as a primary phone device for a developer/hacker person. '''This is not meant for regular (Maemo 5) users. Using this release will probably void any warranty and there is no (other than community-based) support available.'''

=== Target ===
The focus is on meeting the non-functional targets (such as performance) rather than number of features. This will hopefully encourage more people to use MeeGo on N900, and continue enhancing the functionality or build new stuff. Developer Edition is based on MeeGo 1.2 handset trunk content, and selected community contributions ([[ARM/N900/CoolStuff|see the candidates]]). Core MeeGo 1.2 Handset features can be found in [https://bugs.meego.com/report.cgi?x_axis_field=product&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=MeeGo+Features&product=MeeGo+Core+OS+Features&product=MeeGo+Handset+Features&version=1.0&version=1.1&version=1.2&version=1.0&version=1.1&version=1.2&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=ACCEPTED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bug_id_type=anyexact&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= featurezilla], and features of DE not yet implemented from [[ARM/N900/Configuration|Configuration list.]]

== Key features ==
These use cases shall be the prominent ones in the Developer Edition. (If you want to promote a feature to this list, please add it to the feedback section first.)

'''Cellular voice calls''' (Dialer, People)

* Make voice calls (input number directly, initiate from Contacts, initiate from Call history)
* Receive calls
* Default ringtone plays
* Volume control works via System UI
* SIM PIN entry support

'''SMS''' (SMS, People)
* Send new SMS (input number, send from Contacts)
* Receive SMS, and reply to sender

'''Browser use over WLAN''' (Browser, Settings)
* Able to connect to WLAN AP (with security etc.)
* Open a complex modern website (eg. gmail.com)

'''Camera''' (meegocamera)
* Still image capture
* Support for N900 keys (zoom, capture)

'''Common SW''' (Settings, xterm, lock)

Common components such as System UI, Home screen etc. shall be made functional so that basic device usage is smooth and fast. N900 device specific features such as keys, display and battery will be optimized. [[SDK|MeeGo SDK]] fully supports this edition, as it is MeeGo 1.2 compliant.

== Target schedules ==

This shows the '''target schedule''' and content. It should be understood that Developer Edition is still based on "best-effort" model, so this might change any time. If you want to make sure targets are kept, please join the project and help us.

* '''Alpha release''': on week 15
** Official DE image available with key overlays on top of MeeGo 1.2 trunk (see [[ARM/N900/Configuration]]).
** Calls, SMS, Browser and Camera should be in a demo-able state (MeeGo Summit FI).
** Key performance and usability items fixed (PM kernel, backlight control)
** [http://repository.maemo.org/meego/n900-de/archive/1.1.99.2.20110412.6.DE.2011-04-15.1/images/mg-handset-armv7nhl-n900-de-acceptance/ Download here].

* '''[[ARM/N900/SF2011|MeeGo Conference release]]''': on week 20, see the [[ARM/N900/ReleaseProcess/Plan]].
** [http://repository.maemo.org/meego/n900-de/daily/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ Download here].
** Known issues: Coming soon.
* '''"Summer release"''' by end of June, targets are to be refined based on beta achievement and community activity.

== Status ==
The maturity of Developer Edition image, can be seen from the [[ARM/N900/Status|Status page.]]

== Installing and running ==
Image download and installing instructions can be found from [[N900#Install|N900 page,]] please refer to them for more instructions.

* [[N900#Install|Download and install]] instructions page.
* [[ARM/N900/Status|Status and reports]] of the latest image.
* [[ARM/N900/CoolStuff|Applications and accessories]] for the Developer Edition.

== I want to help! ==
Willing to contribute the code to DE/MeeGo, but wondering where to start from? Learn the ropes from the MeeGo experts! This [[Media:Meegokickoff.pdf|material (meego developer's journey)]] gives the overview on the daily development workflow.

Some more concrete steps:

* Join [http://lists.meego.com/listinfo/meego-porting meego-porting@meego.com] and [http://lists.meego.com/listinfo/meego-handset meego-handset@meego.com] mailing lists
* Hang out in [http://webchat.freenode.net/?channels=#meego-arm #meego-arm IRC channel on irc.freenode.net]
* Join [[ARM/N900/DeveloperEdition/Meetings|weekly team meetings]] are held in the public IRC. This meeting is registered on the [[MeeGo-Meeting_IRC_Schedule|MeeGo IRC Meeting Page]]. The agenda and the archives are also available.
* Follow [http://qa-reports.meego.com/1.2/Handset/Acceptance/N900 acceptance testing reports] and see if there's anything of your interest you'd like to work on.
* Play a little with Tablet UX pre-alpha as it's possible the same applications will be replacing some of the Handset UX ones. Experiments are being tried with the Tablet UX on N900. Find more details on [[ARM/N900/TabletUX]].
* Look into learning QML if you haven't already.
* To contribute fixes see [[ARM/N900/ReleaseProcess]].
* Would like to contribute the test cases? You will find the useful information [[Quality|here]].
* Would like to contribute artwork? See [[ARM/N900/Artwork]].
* Look through [[ARM/N900/Developers|Developers page,]] for tips and tricks.

== Organization ==
Core team, of Developer Edition, is formed in and around Nokia. In addition to core team, we hope to see growing community working on this. There is something for everybody to contribute be it bugs, code, artwork or something else. Core team itself has been divided into following categories:

* Program lead: [http://meego.com/users/bittinen Mika Leppinen]
** R&D lead: [http://meego.com/users/msugano Makoto Sugano]
*** [[ARM/N900/VoiceSMS|Voice/SMS]] team lead: [http://meego.com/users/sabotage Shane Bryan]. *
*** [[ARM/N900/Browser|Browser/WLAN]] team lead: [http://meego.com/users/vesku Vesa-Matti Hartikainen]
*** [[ARM/N900/Common|Common SW]] team lead: [http://meego.com/users/harrihakulinen Harri Hakulinen]. **
*** [[ARM/N900/ReleaseProcess|Release & integration]]: [http://meego.com/users/ericlr Eric Le Roux], [http://meego.com/users/stskeeps Carsten Munk], [http://meego.com/users/sage Marko Saukko].
** [[ARM/N900/QA|QA]]: [http://meego.com/users/jaritah Jari Tahvanainen], [http://meego.com/users/markraja Marko Rajala]
** [[ARM/N900/PM|Product management]]: [http://meego.com/users/jukkaeklund Jukka Eklund], [http://meego.com/users/samipienimaki Sami Pienimäki]

<nowiki>*</nowiki>This project is merged with the MeeGo mainstream [[Project/Dialer|Dialer project.]] 
<nowiki>**</nowiki>Includes the [[ARM/N900/HW_Adaptation_team|Hardware Adaptation]] (maintained by [http://meego.com/users/stskeeps Carsten Munk]).

== FAQ ==

Q. Let's assume my bug fix was accepted only in the DE, but rejected in the official 1.2. What do we do with the bug? 
A. Submit the fix to 1.3. Change the status to "RESOLVED". Comment that the fix is available in DE & 1.3.

Q. Which SD card should I be using? 
A. Class 6 and higher. The class has the impact on the performance.

Q. Where can I download the N900 DE release? 
A. See [[N900#Install|installation instructions]]

Q. What is the UI of DE going to be? 
A. Based on what's available on MeeGo trunk. At the moment we work with the MeeGo 1.1-originated Handset UX and apps. We are evaluating the new tablet-originated UX and apps (see [[ARM/N900/TabletUX]]). This is still to be decided, and there might be even multiple options for the user to select.

== Ideas, feedback etc. ==

Please add stuff to the [[ARM/N900/Ideas|Ideas]] page.

[[File:Splash-developers.png]]

[[Category:N900]]

ARM/N900/Configuration

2011-05-27T12:28:51Z

Hanshoi: /* N900 Developer Edition configuration */

== N900 Developer Edition configuration ==
List of features implemented ( or to be implemented) in different Meego Developer Edition releases.

=== Default settings for the Handset UX===

==== Meego Conference Release ====

* '''Bluetooth''': off by default (kallam), '''not done yet'''
* Pre-started applications
** Dialer (done) and SMS (arun), should be running in background to have quick access. DONE
** Lock app (Ronksu), not done yet. (no need?)
** Camera? (theodor), not done yet?
* Application content and home screen configuration
** '''Quick bar''': Dialer, SMS, People, Camera (OK)
** '''Home screen 1st row''': fennec, Terminal, Peregrine, Settings, Mad developer
** Home screen 2nd row & other screens: Kasvopus, TwimGo, QmlReddit, Qatbowling, widgets gallery, Music, Video
** Icons for Email, Calendar should be removed (and Lock, Meego-PIN etc.). Show only one Widgets gallery icon.
** Investigating possibility to include new MeeGo UX applications (Sage), not feasible now (tested by Jukka).
* Application grid improvements
** Structure home screen icons to correct order, see above (Sage, mirek), NOT DONE YET
** Finalize correct icons for applications (from base theme)(mirek), DONE
* Theme improvements
** Work on DE theme, and fix UI glitches and bad usability (see [https://bugs.meego.com/show_bug.cgi?id=17039 META bug], mirek), mostly done.
** New wallpaper for SF2011? (wazd?), DONE
* Splash screens (msugano)
** kernel message appears on the boot splash (msugano: this was solved in the smia driver, error level reduced for certain messages, KERN_ALERT to KERN_INFO).
** Boot splash screen should stay on screen until device booted (msugano: the bootsplash is wiped away once X windows starts. what about X->xsetroot->mcompositor?)
** Looks OK for now (Jukka)
** Shutdown splash should stay on screen until device is powered off
** Weird behaviour while shutdown, not done.
* Backlight behaviour (lamikr/done)
** Increase the timeout to 1min (done)
** Backlight should turn off only when power button is released. When powering the device off (keeping power button pressed), backlight shouldn't turn off (done)
** Backlight should not dim while booting, before the device is fully booted so that user sees when that happens (done)
* Automatic lock (lamikr/done)
** Screen and keys should be locked automatically after a time-out (done)
* Hardware key features
** Power button is used to toggle backlight, and for powering on and off (lamikr/done)
** Lock key works (lamikr/done)
** Camera key starts the Camera application (joonasta)
** Volume can be controlled with volume keys during call (jpeltonen)
* Media content
** Based on community contribution, can we have open source videos, ringtones, audio and images? (ask from karoliina salminen)

==== Alpha Release ====

* Theme: Development (ie. base theme), should show the new colourful new icons instead of default MeeGo ones. OK, there is a new DE theme based on base theme.
* Wallpaper: all black (need to make a 800x480 image for that?)
** Changing wallpaper from Settings should work
* Quick bar: Dialer, SMS, Browser, Camera
* Application grid: Dialer, SMS, Browser, Camera, Settings first and then the rest.
** remove current duplicate browser icons
** should include mad-developer
* Backlight turn off delay: 30s
* Boot splash screen
* Shutdown splash screen

=== Settings for experimental MeeGo UX (Tablet) ===
* Menu key mapped to N900 camera key (or proximity sensor?)
* Use Dialer, SMS and Browser from Handset UX.

=== Ideas, feedback ===
* When we get new artwork, we can use that [[ARM/N900/Artwork]]

[[Category:N900]]

ARM/N900/Configuration

2011-05-27T12:27:49Z

Hanshoi:

== N900 Developer Edition configuration ==
List of features implemented ( or to be implemented) in different Meego Developer Edition releases.

=== Default settings for the Handset UX===

'''To be implemented for MeeGo conference beta release''' (responsible action owner in ()'s)

* '''Bluetooth''': off by default (kallam), '''not done yet'''
* Pre-started applications
** Dialer (done) and SMS (arun), should be running in background to have quick access. DONE
** Lock app (Ronksu), not done yet. (no need?)
** Camera? (theodor), not done yet?
* Application content and home screen configuration
** '''Quick bar''': Dialer, SMS, People, Camera (OK)
** '''Home screen 1st row''': fennec, Terminal, Peregrine, Settings, Mad developer
** Home screen 2nd row & other screens: Kasvopus, TwimGo, QmlReddit, Qatbowling, widgets gallery, Music, Video
** Icons for Email, Calendar should be removed (and Lock, Meego-PIN etc.). Show only one Widgets gallery icon.
** Investigating possibility to include new MeeGo UX applications (Sage), not feasible now (tested by Jukka).
* Application grid improvements
** Structure home screen icons to correct order, see above (Sage, mirek), NOT DONE YET
** Finalize correct icons for applications (from base theme)(mirek), DONE
* Theme improvements
** Work on DE theme, and fix UI glitches and bad usability (see [https://bugs.meego.com/show_bug.cgi?id=17039 META bug], mirek), mostly done.
** New wallpaper for SF2011? (wazd?), DONE
* Splash screens (msugano)
** kernel message appears on the boot splash (msugano: this was solved in the smia driver, error level reduced for certain messages, KERN_ALERT to KERN_INFO).
** Boot splash screen should stay on screen until device booted (msugano: the bootsplash is wiped away once X windows starts. what about X->xsetroot->mcompositor?)
** Looks OK for now (Jukka)
** Shutdown splash should stay on screen until device is powered off
** Weird behaviour while shutdown, not done.
* Backlight behaviour (lamikr/done)
** Increase the timeout to 1min (done)
** Backlight should turn off only when power button is released. When powering the device off (keeping power button pressed), backlight shouldn't turn off (done)
** Backlight should not dim while booting, before the device is fully booted so that user sees when that happens (done)
* Automatic lock (lamikr/done)
** Screen and keys should be locked automatically after a time-out (done)
* Hardware key features
** Power button is used to toggle backlight, and for powering on and off (lamikr/done)
** Lock key works (lamikr/done)
** Camera key starts the Camera application (joonasta)
** Volume can be controlled with volume keys during call (jpeltonen)
* Media content
** Based on community contribution, can we have open source videos, ringtones, audio and images? (ask from karoliina salminen)

'''Implemented for the alpha release'''

* Theme: Development (ie. base theme), should show the new colourful new icons instead of default MeeGo ones. OK, there is a new DE theme based on base theme.
* Wallpaper: all black (need to make a 800x480 image for that?)
** Changing wallpaper from Settings should work
* Quick bar: Dialer, SMS, Browser, Camera
* Application grid: Dialer, SMS, Browser, Camera, Settings first and then the rest.
** remove current duplicate browser icons
** should include mad-developer
* Backlight turn off delay: 30s
* Boot splash screen
* Shutdown splash screen

=== Settings for experimental MeeGo UX (Tablet) ===
* Menu key mapped to N900 camera key (or proximity sensor?)
* Use Dialer, SMS and Browser from Handset UX.

=== Ideas, feedback ===
* When we get new artwork, we can use that [[ARM/N900/Artwork]]

[[Category:N900]]

ARM/N900

2011-05-27T12:22:33Z

Hanshoi: /* MeeGo 1.2 Developer Edition for Nokia N900 */

= MeeGo 1.2 Developer Edition for Nokia N900=

'''What's hot:'''
Test the '''MeeGoConf/SF release''' of the MeeGo 1.2 Developer Edition for N900: [http://repository.maemo.org/meego/n900-de/daily/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ download] - [[#Installing_and_running|install]] - [[ARM/N900/CoolStuff|cool stuff]]

== Introduction ==
The target of this activity is to make a Developer Edition of MeeGo for the Nokia N900 device. This Developer Edition is an 'overlay' constructed above the current core MeeGo 1.2. The DE project is working as a draft of a MeeGo handset image, to make possible the MeeGo development on your N900 hardware. Being a draft it will not take into account all features commonly present in a handset OS. To see what features will be implemented look [[#Key_features]]. Flashed with this edition N900 will be usable as a primary phone device for a developer/hacker person. '''This is not meant for regular (Maemo 5) users. Using this release will probably void any warranty and there is no (other than community-based) support available.'''

=== Target ===
The focus is on meeting the non-functional targets (such as performance) rather than number of features. This will hopefully encourage more people to use MeeGo on N900, and continue enhancing the functionality or build new stuff. Developer Edition is based on MeeGo 1.2 handset trunk content, and selected community contributions ([[ARM/N900/CoolStuff|see the candidates]]). Core MeeGo 1.2 Handset features can be found in [https://bugs.meego.com/report.cgi?x_axis_field=product&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=MeeGo+Features&product=MeeGo+Core+OS+Features&product=MeeGo+Handset+Features&version=1.0&version=1.1&version=1.2&version=1.0&version=1.1&version=1.2&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=ACCEPTED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bug_id_type=anyexact&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= featurezilla], and features of DE not yet implemented from [[ARM/N900/Configuration|Configuration list.]]

== Key features ==
These use cases shall be the prominent ones in the Developer Edition. (If you want to promote a feature to this list, please add it to the feedback section first.)

'''Cellular voice calls''' (Dialer, People)

* Make voice calls (input number directly, initiate from Contacts, initiate from Call history)
* Receive calls
* Default ringtone plays
* Volume control works via System UI
* SIM PIN entry support

'''SMS''' (SMS, People)
* Send new SMS (input number, send from Contacts)
* Receive SMS, and reply to sender

'''Browser use over WLAN''' (Browser, Settings)
* Able to connect to WLAN AP (with security etc.)
* Open a complex modern website (eg. gmail.com)

'''Camera''' (meegocamera)
* Still image capture
* Support for N900 keys (zoom, capture)

'''Common SW''' (Settings, xterm, lock)

Common components such as System UI, Home screen etc. shall be made functional so that basic device usage is smooth and fast. N900 device specific features such as keys, display and battery will be optimized. [[SDK|MeeGo SDK]] fully supports this edition, as it is MeeGo 1.2 compliant.

== Target schedules ==

This shows the '''target schedule''' and content. It should be understood that Developer Edition is still based on "best-effort" model, so this might change any time. If you want to make sure targets are kept, please join the project and help us.

* '''Alpha release''': on week 15
** Official DE image available with key overlays on top of MeeGo 1.2 trunk (see [[ARM/N900/Configuration]]).
** Calls, SMS, Browser and Camera should be in a demo-able state (MeeGo Summit FI). For top issues see [[http://wiki.meego.com/User:Jukkaeklund]].
** Key performance and usability items fixed (PM kernel, backlight control)
** [http://repository.maemo.org/meego/n900-de/archive/1.1.99.2.20110412.6.DE.2011-04-15.1/images/mg-handset-armv7nhl-n900-de-acceptance/ Download here].

* '''[[ARM/N900/SF2011|MeeGo Conference release]]''': on week 20, see the [[ARM/N900/ReleaseProcess/Plan]].
** [http://repository.maemo.org/meego/n900-de/daily/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ Download here].
** Known issues: Coming soon.
* '''"Summer release"''' by end of June, targets are to be refined based on beta achievement and community activity.

== Status ==
The maturity of Developer Edition image, can be seen from the [[ARM/N900/Status|Status page.]]

== Installing and running ==
Image download and installing instructions can be found from [[N900#Install|N900 page,]] please refer to them for more instructions.

* [[N900#Install|Download and install]] instructions page.
* [[ARM/N900/Status|Status and reports]] of the latest image.
* [[ARM/N900/CoolStuff|Applications and accessories]] for the Developer Edition.

== I want to help! ==
Willing to contribute the code to DE/MeeGo, but wondering where to start from? Learn the ropes from the MeeGo experts! This [[Media:Meegokickoff.pdf|material (meego developer's journey)]] gives the overview on the daily development workflow.

Some more concrete steps:

* Join [http://lists.meego.com/listinfo/meego-porting meego-porting@meego.com] and [http://lists.meego.com/listinfo/meego-handset meego-handset@meego.com] mailing lists
* Hang out in [http://webchat.freenode.net/?channels=#meego-arm #meego-arm IRC channel on irc.freenode.net]
* Join [[ARM/N900/DeveloperEdition/Meetings|weekly team meetings]] are held in the public IRC. This meeting is registered on the [[MeeGo-Meeting_IRC_Schedule|MeeGo IRC Meeting Page]]. The agenda and the archives are also available.
* Follow [http://qa-reports.meego.com/1.2/Handset/Acceptance/N900 acceptance testing reports] and see if there's anything of your interest you'd like to work on.
* Play a little with Tablet UX pre-alpha as it's possible the same applications will be replacing some of the Handset UX ones. Experiments are being tried with the Tablet UX on N900. Find more details on [[ARM/N900/TabletUX]].
* Look into learning QML if you haven't already.
* To contribute fixes see [[ARM/N900/ReleaseProcess]].
* Would like to contribute the test cases? You will find the useful information [[Quality|here]].
* Would like to contribute artwork? See [[ARM/N900/Artwork]].
* Look through [[ARM/N900/Developers|Developers page,]] for tips and tricks.

== Organization ==
Core team, of Developer Edition, is formed in and around Nokia. In addition to core team, we hope to see growing community working on this. There is something for everybody to contribute be it bugs, code, artwork or something else. Core team itself has been divided into following categories:

* Program lead: [http://meego.com/users/bittinen Mika Leppinen]
** R&D lead: [http://meego.com/users/msugano Makoto Sugano]
*** [[ARM/N900/VoiceSMS|Voice/SMS]] team lead: [http://meego.com/users/sabotage Shane Bryan]. *
*** [[ARM/N900/Browser|Browser/WLAN]] team lead: [http://meego.com/users/vesku Vesa-Matti Hartikainen]
*** [[ARM/N900/Common|Common SW]] team lead: [http://meego.com/users/harrihakulinen Harri Hakulinen]. **
*** [[ARM/N900/ReleaseProcess|Release & integration]]: [http://meego.com/users/ericlr Eric Le Roux], [http://meego.com/users/stskeeps Carsten Munk], [http://meego.com/users/sage Marko Saukko].
** [[ARM/N900/QA|QA]]: [http://meego.com/users/jaritah Jari Tahvanainen], [http://meego.com/users/markraja Marko Rajala]
** [[ARM/N900/PM|Product management]]: [http://meego.com/users/jukkaeklund Jukka Eklund], [http://meego.com/users/samipienimaki Sami Pienimäki]

<nowiki>*</nowiki>This project is merged with the MeeGo mainstream [[Project/Dialer|Dialer project.]] 
<nowiki>**</nowiki>Includes the [[ARM/N900/HW_Adaptation_team|Hardware Adaptation]] (maintained by [http://meego.com/users/stskeeps Carsten Munk]).

== FAQ ==

Q. Let's assume my bug fix was accepted only in the DE, but rejected in the official 1.2. What do we do with the bug? 
A. Submit the fix to 1.3. Change the status to "RESOLVED". Comment that the fix is available in DE & 1.3.

Q. Which SD card should I be using? 
A. Class 6 and higher. The class has the impact on the performance.

Q. Where can I download the N900 DE release? 
A. See [[N900#Install|installation instructions]]

Q. What is the UI of DE going to be? 
A. Based on what's available on MeeGo trunk. At the moment we work with the MeeGo 1.1-originated Handset UX and apps. We are evaluating the new tablet-originated UX and apps (see [[ARM/N900/TabletUX]]). This is still to be decided, and there might be even multiple options for the user to select.

== Ideas, feedback etc. ==

Please add stuff to the [[ARM/N900/Ideas|Ideas]] page.

[[File:Splash-developers.png]]

[[Category:N900]]

N900

2011-05-27T12:22:05Z

Hanshoi: /* MeeGo for Nokia N900 */

[[File:20000101-034513.png|400px|thumb|right]]

= MeeGo for Nokia N900 =
'' "I have N900, and want to try MeeGo on it." '' 
'' "I want to develop MeeGo/Qt applications on my N900 device" '' 
'' "I want to develop MeeGo OS, on existing N900 or other ARM-based device" ''

== Introduction ==
When using MeeGo on the Nokia N900, or other ARM-based handset, it's recommended to use MeeGo [[ARM/N900|Developer Edition]]. [[ARM/N900|Developer Edition]] (DE) is an edition of the core MeeGo 1.2. The [[ARM/N900|DE]] is developed with the ARM and handset compatibility in mind, this way developers already owning a N900 device may start developing with it immediately.

For more information about [[ARM/N900|Developer Edition]], please visit [[ARM/N900|Developer Edition page.]]

== Status ==
The working status of Meego for N900 implementation can be seen on [[ARM/N900/Status|Status page.]]

== Install ==
=== Download image ===
You can choose from several images from our repository, or even [[ARM/Creating ARM image using MeeGo Image Creator|build one yourself.]]

{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
|-
!style="border-style: solid; border-width: 0 1px 1px 0"| Image
!style="border-style: solid; border-width: 0 1px 1px 0"| Description
!style="border-style: solid; border-width: 0 0 1px 0"| Release date
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/daily/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ SF/MeeGoConf Release]
|style="border-style: solid; border-width: 0 1px 1px 0"| San Francisco release, image released at MeeGo conference.
|style="border-style: solid; border-width: 0 0 1px 0"| 23.5.2011
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.1.99.2.20110412.6.DE.2011-04-15.1/images/mg-handset-armv7nhl-n900-de-acceptance/ Alpha release]
|style="border-style: solid; border-width: 0 1px 1px 0"| Alpha release of the Meego DE image. (recommended)
|style="border-style: solid; border-width: 0 0 1px 0"| 15.04.2011
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/ Weekly image]
|style="border-style: solid; border-width: 0 1px 1px 0"| From here you can find the weekly and daily builds of DE image.
|style="border-style: solid; border-width: 0 0 1px 0"|
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [https://meego.com/downloads/releases/1.1/meego-v1.1-handset Meego Core 1.1]
|style="border-style: solid; border-width: 0 1px 1px 0"| Original Meego core 1.1 release for N900.
|style="border-style: solid; border-width: 0 0 1px 0"| 28.10.2010
|}

=== Install image ===
Recommended way is to install MeeGo DE as dual boot to N900, with your Maemo 5 fremantle. However you can choose any one from the list with your own risk.

{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
|-
!style="border-style: solid; border-width: 0 1px 1px 0"| Topic
!style="border-style: solid; border-width: 0 0 1px 0"| Description
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/Dual_Boot|Dual-boot install]]
|style="border-style: solid; border-width: 0 0 1px 0"| Installs Meego as dual boot with your Maemo 5 fremantle. (Default)
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/MMC|MMC Installation]]
|style="border-style: solid; border-width: 0 0 1px 0"| Installs Meego to a external SD card. Does not destroy internal memory of your N900 device, and also a recommended way.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/EMMC| eMMC Installation]]
|style="border-style: solid; border-width: 0 0 1px 0"| Install Meego on the internal memory. This will destroy the existing fremantle installation.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/chroot|Chroot install]]
|style="border-style: solid; border-width: 0 0 1px 0"| Chroot install is a way to try out MeeGo by running it on top of Maemo 5 on your N900 device.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/NFS|NFS-Root over usb networking]]
|style="border-style: solid; border-width: 0 0 1px 0"| With NFS-root install you can run MeeGo natively on your N900, without erasing Maemo 5, without flashing or using SD card. Rootfs speed over USB is the downside.
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/Install/U-Boot from scratch|Install U-boot from scratch]]
|style="border-style: solid; border-width: 0 0 1px 0"| If you cannot install uboot from Maemo repo, then use this one to get it installed.
|}

=== Applications ===
If you want to try out some applications on Meego [[ARM/N900|Developer Edition]] get them from [[ARM/N900/CoolStuff|here.]] Eventually applications will be in [[http://apps-beta.meego.com/applications/MeeGo Community apps site]].

== Participate ==
If you are interested to help developing MeeGo or applications for your favorite hardware. Please visit on MeeGo [[ARM/N900|Developer Edition page.]]

== FAQ ==
Q. Where can I download the N900 DE release? 
A. See [[#Download_image]]

Q. Where do I see the maturity of the current image? 
A. See the Developer Edition [[ARM/N900/Status|Status page.]]

Q. My battery is drained, how shall I recharge it? 
A. Look from [[ARM/N900/Recover_From_Drained_Battery|battery recharge guide.]]

Q. I want to install back to Maemo5 as my only operating system, how will I do that? 
A. See the [http://wiki.maemo.org/Updating_the_firmware#N900_2 restore Maemo guide] from Maemo wiki.

Q. I want a usb connection to my N900, how will I do it? 
A. Use ssh. See [[ARM/N900/Tips_and_Tricks/N900_USB_Networking|guide.]]

ARM/N900/QA

2011-05-18T14:51:17Z

Hanshoi: /* QA Tasks For Developer Edition */

= Meego Developer Edition Quality Assurance =
Quality Assurance for Meego [[ARM/N900|Developers Edition.]] [[ARM/N900|Developer Edition]] QA uses many same components as in core Meego, therefore remember to look [[Quality|Meego core quality page.]] Monitoring the [[ARM/N900|Developer Edition]] maturity is one of the main tasks of [[ARM/N900|Developer Edition]] QA. The current maturity status can be found from the [[ARM/N900/Status|Status page.]]

== Organization ==
* Error Management
** Error Manager: Iekku Huttunen
* QA Tools
* Core Testing
* User Experience Testing (UX)

== Reports ==
* [http://wiki.meego.com/ARM/N900/Status General DE N900 Feature status]
* [http://wiki.meego.com/ARM/N900/QA/Performance Performance results]
* [http://qa-reports.meego.com/1.2/Handset/Data%20Flow%20For%20Developer%20Edition Dataflow reports]
* [http://qa-reports.meego.com/1.2/Handset/Use%20Case%20Testing%20For%20Developer%20Edition Use case reports]

== Meetings ==
QA IRC meeting every Tuesday:
* [http://wiki.meego.com/MeeGo-Meeting_IRC_Schedule MeeGo-Meeting IRC Schedule]

N900 DE Blocker Bug Triage meeting minutes:
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-12-06.59.html Meeting minutes 12-05-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-05-07.00.html Meeting minutes 05-05-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-21-07.01.html Meeting minutes 21-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-14-07.00.html Meeting minutes 14-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-07-07.02.html Meeting minutes 07-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-31-07.00.html Meeting minutes 31-03-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-24-06.59.html Meeting minutes 24-03-2011]

= QA Tools =
Developers Edition uses same QA Tools as in core Meego. For more information please refer to the [[Quality/QA-tools|Quality/QA-tools]].

== QA-Tools Task List ==
List of tasks the QA-Tools are doing for Meego Developer Edition.
If you need something from QA please tell it to us :)
=== OTS setup ===
(Open Testing System)
* [http://194.136.64.78/logger/view/ OTS server] DONE
* [http://194.136.64.78/logger/view/workers/ OTS worker(s) for core tests]- DONE
* [http://qa-reports.meego.com/1.2/Core/Hourly%20-%20Automated Reporting of hourly tests to QA-reports] - DONE
* Minimize automatic installation time to 10mins - DONE
* OTS worker for UX tests - NOTSTARTED
* OTS Worker(s) for DE tests - ONGOING (timakima)
* Power consumption measurements - NOTSTARTED

=== Test automation images ===
* Setup hourly image building for autotest image on own setup - Riku Halonen/Timo Harkonen/Ville Ilvonen - DONE (in OTS subnet, see above)
* We need to be able to control included test packages - ONGOING (http://meego.gitorious.org/meego-quality-assurance/handset-hourly-automated-tests)
* Move to use images from release engineering (1. download image, 2. install automation enablers, core dumping enablers etc. using mic-chroot, 3. install image to device 4. test) - NOT STARTED

== Applications for testing ==
* qt-demos already available from the repos
* Small applications that use Qt mobility APIs to access things like sensors to help manual testing

== Test asset ==
We are using mainly MCTS test assets, so please refer to the [[Quality/TestSuite/MCTS|MCTS page.]] You can find list of open bugs also from there.
* [https://bugs.meego.com/buglist.cgi?quicksearch=mcts List of open bugs for MCTS]
** see priorities below - discuss with Iekku about priorities of open bugs for MCTS tests
# WLAN cases
# Call/SMS cases
# Audio policy framework cases (lower priority)
# Camera cases (lower priority)
# Sensor data cases (Qt Mobility, lower priority)

== Crash analysis support for ARM core dumps ==

[[File:Text9867-0-4-8.png|350px|thumb|right|Automated testing and crash reporting]]

Core dump processing and backtraces from crashing ARM processes (click the image on right).

* Rich Core dumping
** Make rich-core dumping to work in MeeGo N900 DE (basic functionality) - DONE (sampos, rikhalon)
*** Changes in MeeGo Gitorious ([https://meego.gitorious.org/meego-quality-assurance/rich-core/commits/meego-n900de meego-n900de] branch).
*** Dumps are generated in /home/meego/core-dumps
*** In file name, string "xxxx" is used instead of IMEI digits (privacy issue)
*** Get latest packages [http://repo.pub.meego.com/home:/rha/Project_DE_Trunk_Testing_standard/armv7l/ here]
*** Add "-corewatcher" and "-corewatcher-applet" to .ks file to remove overlapping corewatcher.
** Fix core-reducer (https://bugs.meego.com/show_bug.cgi?id=17134) - ONGOING (alkuznet)
** Oopslog (and lifelog) functionality - NOT STARTED

* Set up back-end server for core processing - ONGOING (rikhalon, sampos, timakima)

* Image building and test run triggered from cron - trigger-testrun.sh -u <URL> - DONE (timakima)

* Implement OTS Conductor plugin to fetch debug package list (before test run) and upload rich-core dumps to post-processing (after testrun )- DONE (rikhalon)

* testrunner-lite sets a UID for each test case on DUT kernel core pattern. So that a coredump can be matched with a test case - DONE (rikhalon)

* Debug image is built (simultaneuosly) on the core proscessing backend server - build-autotest-image.sh -f fs -d -p debug-packet-list -s 8000 -u <URL>, and saved as target for core prosessing - DONE (sampos)

* After each test case, cores matched against the UID are fetched from the DUT by testrunner-lite. - NOT STARTED
** testrunner-lite needs to write unique identifier to results.xml e.g. md5 hash from rich-core.
[[File:backend.png|350px|thumb|right|Core Processing Backend]]
<crashes>
<crash-id>1234567890ABCDEF</crash-id>
<crash-id>1234567890ABCDEF</crash-id>
<crash-id>1234567890ABCDEF</crash-id>
</crashes>

* The core processing backend extracts the rich core and looks for proper target (if not available waits...) - PofC DONE (sampos)

* The core processing backend chroots to the target with debug symbols and executes statically linked cross gdb for backtrace - DONE (sampos)

* Upload processed crash data using [[Quality/QA-tools/CrashReports/API|Crash Reports API]] - ONGOING (rikhalon)

== Boot time measurement ==
* Measure and optimize N900 boot time (timakima, ONGOING)

== CPU load measurement during audio/video playback ==

== Application Manager ==
* Implement an application manager (similar to one in N900/Fremantle) to control install/uninstall/update applications and other packages. (kyranto, ONGOING).

= UX testing =
== Test execution schedule ==
* UX testing schedule: DE / Meego.com testing
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release !! Priority
|-
| Monday
| Dataflow
| DE Weekly
| P1
|-
| Monday
| Use cases
| DE Weekly
| P2
|-
|Monday
| Key feature
| DE Weekly
| P3
|-
| Monday
| Performance
| DE Weekly
| P5
|-
| Monday
| Reliability / Iterative
| DE Weekly
| P6
|-
| Monday
| Dataflow
| DE Trunk testing
| P4
|-
| Tuesday
| Dataflow
| DE Trunk testing
| P1
|-
| Tuesday
| Dataflow
| DE Trunk
| P2
|-
| Tuesday
| Acceptance
| Meego Trunk testing
| P3
|-
| Tuesday
| Key feature
| DE Tablet (N900)
| P4
|-
| Wednesday
| Dataflow
| DE Trunk testing
| P1
|-
| Wednesday
| Dataflow
| DE Trunk
| P2
|-
| Wednesday
| Key feature
| Meego.com weekly
| P3
|-
| Wednesday
| Sanity
| Meego.com weekly
| P4
|-
| Thursday
| Dataflow
| DE Trunk testing
| P1
|-
| Thursday
| Dataflow
| DE Trunk
| P2
|-
| Thursday
| Acceptance
| Meego.com Trunk testing
| P3
|-
| Friday
| Dataflow
| DE Trunk Testing
| P1
|-
| Friday
| Dataflow
| DE Trunk
| P2
|-
| Friday
| Acceptance
| Meego.com Trunk testing
| P3
|}

== Performance Testing ==
Performance testing results done from UI can be found [[ARM/N900/QA/Performance|here]]

= Core Testing =
== QA Tasks For Developer Edition ==
QA tasks for the [[ARM/N900|Developer Edition]] differ from the usual N900 approach in that there are less features to be tested. This is described in more detail in [[ARM/N900#Target|Developer Edition Targets.]] There are currently 2 test sets for the [[ARM/N900|Developer Edition]], these are the Sanity Test Set and the Feature Test Set. They are described below.

=== Test Sets ===
==== Sanity Test Set ====
The sanity set should be run automatically on every image. As such it must meet the following requirements:
* 100% automated
* Testing only basic features
==== Feature Test Set ====
The feature set will be run periodically and will test the basic features as well as enablers for those features (e.g. PIM for phoning contacts). Performance will also be analysed, at the moment, this will include browser startup time, a CPU/Memory benchmark, files system, and power measurement, but this will be explained later.

Suggestions are welcome.

=== Testing schedule ===
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release
|-
| Monday
| Feature
| DE Weekly
|-
| Tuesday
| Sanity
| DE Trunk testing
|-
| Wednesday
| Sanity
| DE Trunk testing
|-
| Thursday
| Sanity
| DE Trunk testing
|-
| Friday
| Sanity
| DE Trunk Testing
|-
|}

=== Core QA Team Backlog ===
The Core QA team intends to keep its backlog as public as possible. The limitation on this is the amount of work generated by doing this. We will attempt to keep an up-to-date lists of tasks and progress on these tasks. At the moment, the task list looks like this:

==== Continuous tasks ====
* Bug verification

==== Backlog ====
* Testcase automation list

==== In progress ====
* DE Hourly Automation improvement
* Wiki clean/update (waiting for comments)

==== Done ====
* * Plan Feature testset (.xml updated)
* Create weekly schedule for MRT (currently in draft form)
* Week 15 DE Sanity Testing
* Maturity statement of Alpha RELEASE (result in QA-report)
* Alpha RELEASE testing

== QA Tasks for MeeGo.com N900 ==

=== Test execution schedule ===
* MeeGo.com N900 Core weekly test schedule for MeeGo1.2(Tu Qingqing)
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release !! Priority
|-
| Monday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
|Monday
| Sanity test (OK)
| MeeGo.com trunk
| P3
|-
| Monday, Tuesday
| Basic feature test (OK)
| MeeGo.com pre-weekly
| P2
|-
| Tuesday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Tuesday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|-
| Wednesday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P2
|-
| Wednesday
| Sanity test (OK)
| MeeGo.com trunk
| P3
|-
| Wednesday, Thursday
| Dataflow (OK)
| MeeGo.com weekly
| P1
|-
| Thursday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Thursday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|-
| Friday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Friday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|}

=== META team backlog for MeeGo1.2 N900 ===

==== Continuous tasks ====
* Bug verification
* MeeGo1.2 N900 daily validation

==== Backlog ====
* Optimize acceptance automation script

==== In progress ====
* MeeGo1.2 feature verification
* Automation testing for trunk:test and trunk image

==== Done ====
* Publish automation test result

= Usefull links =

* [[ARM/N900/Install/MMC|Flashing instructions]]
Flashing tested with http://download.meego.com/testing-daily/builds/trunk/1.1.90.8.20110318.89/

[[Category:N900]]

ARM/N900/QA

2011-05-18T14:44:15Z

Hanshoi: /* Meego Developer Edition Quality Assurance */

= Meego Developer Edition Quality Assurance =
Quality Assurance for Meego [[ARM/N900|Developers Edition.]] [[ARM/N900|Developer Edition]] QA uses many same components as in core Meego, therefore remember to look [[Quality|Meego core quality page.]] Monitoring the [[ARM/N900|Developer Edition]] maturity is one of the main tasks of [[ARM/N900|Developer Edition]] QA. The current maturity status can be found from the [[ARM/N900/Status|Status page.]]

== Organization ==
* Error Management
** Error Manager: Iekku Huttunen
* QA Tools
* Core Testing
* User Experience Testing (UX)

== Reports ==
* [http://wiki.meego.com/ARM/N900/Status General DE N900 Feature status]
* [http://wiki.meego.com/ARM/N900/QA/Performance Performance results]
* [http://qa-reports.meego.com/1.2/Handset/Data%20Flow%20For%20Developer%20Edition Dataflow reports]
* [http://qa-reports.meego.com/1.2/Handset/Use%20Case%20Testing%20For%20Developer%20Edition Use case reports]

== Meetings ==
QA IRC meeting every Tuesday:
* [http://wiki.meego.com/MeeGo-Meeting_IRC_Schedule MeeGo-Meeting IRC Schedule]

N900 DE Blocker Bug Triage meeting minutes:
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-12-06.59.html Meeting minutes 12-05-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-05-07.00.html Meeting minutes 05-05-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-21-07.01.html Meeting minutes 21-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-14-07.00.html Meeting minutes 14-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-07-07.02.html Meeting minutes 07-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-31-07.00.html Meeting minutes 31-03-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-24-06.59.html Meeting minutes 24-03-2011]

= QA Tools =
Developers Edition uses same QA Tools as in core Meego. For more information please refer to the [[Quality/QA-tools|Quality/QA-tools]].

== QA-Tools Task List ==
List of tasks the QA-Tools are doing for Meego Developer Edition.
If you need something from QA please tell it to us :)
=== OTS setup ===
(Open Testing System)
* [http://194.136.64.78/logger/view/ OTS server] DONE
* [http://194.136.64.78/logger/view/workers/ OTS worker(s) for core tests]- DONE
* [http://qa-reports.meego.com/1.2/Core/Hourly%20-%20Automated Reporting of hourly tests to QA-reports] - DONE
* Minimize automatic installation time to 10mins - DONE
* OTS worker for UX tests - NOTSTARTED
* OTS Worker(s) for DE tests - ONGOING (timakima)
* Power consumption measurements - NOTSTARTED

=== Test automation images ===
* Setup hourly image building for autotest image on own setup - Riku Halonen/Timo Harkonen/Ville Ilvonen - DONE (in OTS subnet, see above)
* We need to be able to control included test packages - ONGOING (http://meego.gitorious.org/meego-quality-assurance/handset-hourly-automated-tests)
* Move to use images from release engineering (1. download image, 2. install automation enablers, core dumping enablers etc. using mic-chroot, 3. install image to device 4. test) - NOT STARTED

== Applications for testing ==
* qt-demos already available from the repos
* Small applications that use Qt mobility APIs to access things like sensors to help manual testing

== Test asset ==
We are using mainly MCTS test assets, so please refer to the [[Quality/TestSuite/MCTS|MCTS page.]] You can find list of open bugs also from there.
* [https://bugs.meego.com/buglist.cgi?quicksearch=mcts List of open bugs for MCTS]
** see priorities below - discuss with Iekku about priorities of open bugs for MCTS tests
# WLAN cases
# Call/SMS cases
# Audio policy framework cases (lower priority)
# Camera cases (lower priority)
# Sensor data cases (Qt Mobility, lower priority)

== Crash analysis support for ARM core dumps ==

[[File:Text9867-0-4-8.png|350px|thumb|right|Automated testing and crash reporting]]

Core dump processing and backtraces from crashing ARM processes (click the image on right).

* Rich Core dumping
** Make rich-core dumping to work in MeeGo N900 DE (basic functionality) - DONE (sampos, rikhalon)
*** Changes in MeeGo Gitorious ([https://meego.gitorious.org/meego-quality-assurance/rich-core/commits/meego-n900de meego-n900de] branch).
*** Dumps are generated in /home/meego/core-dumps
*** In file name, string "xxxx" is used instead of IMEI digits (privacy issue)
*** Get latest packages [http://repo.pub.meego.com/home:/rha/Project_DE_Trunk_Testing_standard/armv7l/ here]
*** Add "-corewatcher" and "-corewatcher-applet" to .ks file to remove overlapping corewatcher.
** Fix core-reducer (https://bugs.meego.com/show_bug.cgi?id=17134) - ONGOING (alkuznet)
** Oopslog (and lifelog) functionality - NOT STARTED

* Set up back-end server for core processing - ONGOING (rikhalon, sampos, timakima)

* Image building and test run triggered from cron - trigger-testrun.sh -u <URL> - DONE (timakima)

* Implement OTS Conductor plugin to fetch debug package list (before test run) and upload rich-core dumps to post-processing (after testrun )- DONE (rikhalon)

* testrunner-lite sets a UID for each test case on DUT kernel core pattern. So that a coredump can be matched with a test case - DONE (rikhalon)

* Debug image is built (simultaneuosly) on the core proscessing backend server - build-autotest-image.sh -f fs -d -p debug-packet-list -s 8000 -u <URL>, and saved as target for core prosessing - DONE (sampos)

* After each test case, cores matched against the UID are fetched from the DUT by testrunner-lite. - NOT STARTED
** testrunner-lite needs to write unique identifier to results.xml e.g. md5 hash from rich-core.
[[File:backend.png|350px|thumb|right|Core Processing Backend]]
<crashes>
<crash-id>1234567890ABCDEF</crash-id>
<crash-id>1234567890ABCDEF</crash-id>
<crash-id>1234567890ABCDEF</crash-id>
</crashes>

* The core processing backend extracts the rich core and looks for proper target (if not available waits...) - PofC DONE (sampos)

* The core processing backend chroots to the target with debug symbols and executes statically linked cross gdb for backtrace - DONE (sampos)

* Upload processed crash data using [[Quality/QA-tools/CrashReports/API|Crash Reports API]] - ONGOING (rikhalon)

== Boot time measurement ==
* Measure and optimize N900 boot time (timakima, ONGOING)

== CPU load measurement during audio/video playback ==

== Application Manager ==
* Implement an application manager (similar to one in N900/Fremantle) to control install/uninstall/update applications and other packages. (kyranto, ONGOING).

= UX testing =
== Test execution schedule ==
* UX testing schedule: DE / Meego.com testing
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release !! Priority
|-
| Monday
| Dataflow
| DE Weekly
| P1
|-
| Monday
| Use cases
| DE Weekly
| P2
|-
|Monday
| Key feature
| DE Weekly
| P3
|-
| Monday
| Performance
| DE Weekly
| P5
|-
| Monday
| Reliability / Iterative
| DE Weekly
| P6
|-
| Monday
| Dataflow
| DE Trunk testing
| P4
|-
| Tuesday
| Dataflow
| DE Trunk testing
| P1
|-
| Tuesday
| Dataflow
| DE Trunk
| P2
|-
| Tuesday
| Acceptance
| Meego Trunk testing
| P3
|-
| Tuesday
| Key feature
| DE Tablet (N900)
| P4
|-
| Wednesday
| Dataflow
| DE Trunk testing
| P1
|-
| Wednesday
| Dataflow
| DE Trunk
| P2
|-
| Wednesday
| Key feature
| Meego.com weekly
| P3
|-
| Wednesday
| Sanity
| Meego.com weekly
| P4
|-
| Thursday
| Dataflow
| DE Trunk testing
| P1
|-
| Thursday
| Dataflow
| DE Trunk
| P2
|-
| Thursday
| Acceptance
| Meego.com Trunk testing
| P3
|-
| Friday
| Dataflow
| DE Trunk Testing
| P1
|-
| Friday
| Dataflow
| DE Trunk
| P2
|-
| Friday
| Acceptance
| Meego.com Trunk testing
| P3
|}

== Performance Testing ==
Performance testing results done from UI can be found [[ARM/N900/QA/Performance|here]]

= Core Testing =
== QA Tasks For Developer Edition ==
There is a wiki article about the [[ARM/N900/DeveloperEdition|Developer Edition]].

QA tasks for the Developer Edition differ from the usual N900 approach in that there are less features to be tested. There are currently 2 test sets for the Developer Edition, these are the Sanity Test Set and the Feature Test Set. They are described below.

=== Test Sets ===
==== Sanity Test Set ====
The sanity set should be run automatically on every image. As such it must meet the following requirements:
* 100% automated
* Testing only basic features
==== Feature Test Set ====
The feature set will be run periodically and will test the basic features as well as enablers for those features (e.g. PIM for phoning contacts). Performance will also be analysed, at the moment, this will include browser startup time and a CPU benchmark but this will be expanded later.

Suggestions are welcome.

=== Testing schedule ===
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release
|-
| Monday
| Feature
| DE Weekly
|-
| Tuesday
| Sanity
| DE Trunk testing
|-
| Wednesday
| Sanity
| DE Trunk testing
|-
| Thursday
| Sanity
| DE Trunk testing
|-
| Friday
| Sanity
| DE Trunk Testing
|-
|}

=== Core QA Team Backlog ===
The Core QA team intends to keep its backlog as public as possible. The limitation on this is the amount of work generated by doing this. We will attempt to keep an up-to-date lists of tasks and progress on these tasks. At the moment, the task list looks like this:

==== Continuous tasks ====
* Bug verification

==== Backlog ====
* Testcase automation list

==== In progress ====
* DE Hourly Automation improvement
* Wiki clean/update (waiting for comments)

==== Done ====
* * Plan Feature testset (.xml updated)
* Create weekly schedule for MRT (currently in draft form)
* Week 15 DE Sanity Testing
* Maturity statement of Alpha RELEASE (result in QA-report)
* Alpha RELEASE testing

== QA Tasks for MeeGo.com N900 ==

=== Test execution schedule ===
* MeeGo.com N900 Core weekly test schedule for MeeGo1.2(Tu Qingqing)
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release !! Priority
|-
| Monday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
|Monday
| Sanity test (OK)
| MeeGo.com trunk
| P3
|-
| Monday, Tuesday
| Basic feature test (OK)
| MeeGo.com pre-weekly
| P2
|-
| Tuesday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Tuesday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|-
| Wednesday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P2
|-
| Wednesday
| Sanity test (OK)
| MeeGo.com trunk
| P3
|-
| Wednesday, Thursday
| Dataflow (OK)
| MeeGo.com weekly
| P1
|-
| Thursday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Thursday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|-
| Friday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Friday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|}

=== META team backlog for MeeGo1.2 N900 ===

==== Continuous tasks ====
* Bug verification
* MeeGo1.2 N900 daily validation

==== Backlog ====
* Optimize acceptance automation script

==== In progress ====
* MeeGo1.2 feature verification
* Automation testing for trunk:test and trunk image

==== Done ====
* Publish automation test result

= Usefull links =

* [[ARM/N900/Install/MMC|Flashing instructions]]
Flashing tested with http://download.meego.com/testing-daily/builds/trunk/1.1.90.8.20110318.89/

[[Category:N900]]

ARM/N900/QA

2011-05-18T14:38:50Z

Hanshoi: /* Test asset */

= Meego Developer Edition Quality Assurance =
Quality Assurance for Meego Developers Edition. Developer Edition QA uses many same components as in core Meego, therefore remember to look [[Quality|Meego core quality page.]]

== Organization ==
* Error Management
** Error Manager: Iekku Huttunen
* QA Tools
* Core Testing
* User Experience Testing (UX)

== Reports ==
* [http://wiki.meego.com/ARM/N900/Status General DE N900 Feature status]
* [http://wiki.meego.com/ARM/N900/QA/Performance Performance results]
* [http://qa-reports.meego.com/1.2/Handset/Data%20Flow%20For%20Developer%20Edition Dataflow reports]
* [http://qa-reports.meego.com/1.2/Handset/Use%20Case%20Testing%20For%20Developer%20Edition Use case reports]

== Meetings ==
QA IRC meeting every Tuesday:
* [http://wiki.meego.com/MeeGo-Meeting_IRC_Schedule MeeGo-Meeting IRC Schedule]

N900 DE Blocker Bug Triage meeting minutes:
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-12-06.59.html Meeting minutes 12-05-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-05-07.00.html Meeting minutes 05-05-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-21-07.01.html Meeting minutes 21-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-14-07.00.html Meeting minutes 14-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-07-07.02.html Meeting minutes 07-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-31-07.00.html Meeting minutes 31-03-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-24-06.59.html Meeting minutes 24-03-2011]

= QA Tools =
Developers Edition uses same QA Tools as in core Meego. For more information please refer to the [[Quality/QA-tools|Quality/QA-tools]].

== QA-Tools Task List ==
List of tasks the QA-Tools are doing for Meego Developer Edition.
If you need something from QA please tell it to us :)
=== OTS setup ===
(Open Testing System)
* [http://194.136.64.78/logger/view/ OTS server] DONE
* [http://194.136.64.78/logger/view/workers/ OTS worker(s) for core tests]- DONE
* [http://qa-reports.meego.com/1.2/Core/Hourly%20-%20Automated Reporting of hourly tests to QA-reports] - DONE
* Minimize automatic installation time to 10mins - DONE
* OTS worker for UX tests - NOTSTARTED
* OTS Worker(s) for DE tests - ONGOING (timakima)
* Power consumption measurements - NOTSTARTED

=== Test automation images ===
* Setup hourly image building for autotest image on own setup - Riku Halonen/Timo Harkonen/Ville Ilvonen - DONE (in OTS subnet, see above)
* We need to be able to control included test packages - ONGOING (http://meego.gitorious.org/meego-quality-assurance/handset-hourly-automated-tests)
* Move to use images from release engineering (1. download image, 2. install automation enablers, core dumping enablers etc. using mic-chroot, 3. install image to device 4. test) - NOT STARTED

== Applications for testing ==
* qt-demos already available from the repos
* Small applications that use Qt mobility APIs to access things like sensors to help manual testing

== Test asset ==
We are using mainly MCTS test assets, so please refer to the [[Quality/TestSuite/MCTS|MCTS page.]] You can find list of open bugs also from there.
* [https://bugs.meego.com/buglist.cgi?quicksearch=mcts List of open bugs for MCTS]
** see priorities below - discuss with Iekku about priorities of open bugs for MCTS tests
# WLAN cases
# Call/SMS cases
# Audio policy framework cases (lower priority)
# Camera cases (lower priority)
# Sensor data cases (Qt Mobility, lower priority)

== Crash analysis support for ARM core dumps ==

[[File:Text9867-0-4-8.png|350px|thumb|right|Automated testing and crash reporting]]

Core dump processing and backtraces from crashing ARM processes (click the image on right).

* Rich Core dumping
** Make rich-core dumping to work in MeeGo N900 DE (basic functionality) - DONE (sampos, rikhalon)
*** Changes in MeeGo Gitorious ([https://meego.gitorious.org/meego-quality-assurance/rich-core/commits/meego-n900de meego-n900de] branch).
*** Dumps are generated in /home/meego/core-dumps
*** In file name, string "xxxx" is used instead of IMEI digits (privacy issue)
*** Get latest packages [http://repo.pub.meego.com/home:/rha/Project_DE_Trunk_Testing_standard/armv7l/ here]
*** Add "-corewatcher" and "-corewatcher-applet" to .ks file to remove overlapping corewatcher.
** Fix core-reducer (https://bugs.meego.com/show_bug.cgi?id=17134) - ONGOING (alkuznet)
** Oopslog (and lifelog) functionality - NOT STARTED

* Set up back-end server for core processing - ONGOING (rikhalon, sampos, timakima)

* Image building and test run triggered from cron - trigger-testrun.sh -u <URL> - DONE (timakima)

* Implement OTS Conductor plugin to fetch debug package list (before test run) and upload rich-core dumps to post-processing (after testrun )- DONE (rikhalon)

* testrunner-lite sets a UID for each test case on DUT kernel core pattern. So that a coredump can be matched with a test case - DONE (rikhalon)

* Debug image is built (simultaneuosly) on the core proscessing backend server - build-autotest-image.sh -f fs -d -p debug-packet-list -s 8000 -u <URL>, and saved as target for core prosessing - DONE (sampos)

* After each test case, cores matched against the UID are fetched from the DUT by testrunner-lite. - NOT STARTED
** testrunner-lite needs to write unique identifier to results.xml e.g. md5 hash from rich-core.
[[File:backend.png|350px|thumb|right|Core Processing Backend]]
<crashes>
<crash-id>1234567890ABCDEF</crash-id>
<crash-id>1234567890ABCDEF</crash-id>
<crash-id>1234567890ABCDEF</crash-id>
</crashes>

* The core processing backend extracts the rich core and looks for proper target (if not available waits...) - PofC DONE (sampos)

* The core processing backend chroots to the target with debug symbols and executes statically linked cross gdb for backtrace - DONE (sampos)

* Upload processed crash data using [[Quality/QA-tools/CrashReports/API|Crash Reports API]] - ONGOING (rikhalon)

== Boot time measurement ==
* Measure and optimize N900 boot time (timakima, ONGOING)

== CPU load measurement during audio/video playback ==

== Application Manager ==
* Implement an application manager (similar to one in N900/Fremantle) to control install/uninstall/update applications and other packages. (kyranto, ONGOING).

= UX testing =
== Test execution schedule ==
* UX testing schedule: DE / Meego.com testing
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release !! Priority
|-
| Monday
| Dataflow
| DE Weekly
| P1
|-
| Monday
| Use cases
| DE Weekly
| P2
|-
|Monday
| Key feature
| DE Weekly
| P3
|-
| Monday
| Performance
| DE Weekly
| P5
|-
| Monday
| Reliability / Iterative
| DE Weekly
| P6
|-
| Monday
| Dataflow
| DE Trunk testing
| P4
|-
| Tuesday
| Dataflow
| DE Trunk testing
| P1
|-
| Tuesday
| Dataflow
| DE Trunk
| P2
|-
| Tuesday
| Acceptance
| Meego Trunk testing
| P3
|-
| Tuesday
| Key feature
| DE Tablet (N900)
| P4
|-
| Wednesday
| Dataflow
| DE Trunk testing
| P1
|-
| Wednesday
| Dataflow
| DE Trunk
| P2
|-
| Wednesday
| Key feature
| Meego.com weekly
| P3
|-
| Wednesday
| Sanity
| Meego.com weekly
| P4
|-
| Thursday
| Dataflow
| DE Trunk testing
| P1
|-
| Thursday
| Dataflow
| DE Trunk
| P2
|-
| Thursday
| Acceptance
| Meego.com Trunk testing
| P3
|-
| Friday
| Dataflow
| DE Trunk Testing
| P1
|-
| Friday
| Dataflow
| DE Trunk
| P2
|-
| Friday
| Acceptance
| Meego.com Trunk testing
| P3
|}

== Performance Testing ==
Performance testing results done from UI can be found [[ARM/N900/QA/Performance|here]]

= Core Testing =
== QA Tasks For Developer Edition ==
There is a wiki article about the [[ARM/N900/DeveloperEdition|Developer Edition]].

QA tasks for the Developer Edition differ from the usual N900 approach in that there are less features to be tested. There are currently 2 test sets for the Developer Edition, these are the Sanity Test Set and the Feature Test Set. They are described below.

=== Test Sets ===
==== Sanity Test Set ====
The sanity set should be run automatically on every image. As such it must meet the following requirements:
* 100% automated
* Testing only basic features
==== Feature Test Set ====
The feature set will be run periodically and will test the basic features as well as enablers for those features (e.g. PIM for phoning contacts). Performance will also be analysed, at the moment, this will include browser startup time and a CPU benchmark but this will be expanded later.

Suggestions are welcome.

=== Testing schedule ===
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release
|-
| Monday
| Feature
| DE Weekly
|-
| Tuesday
| Sanity
| DE Trunk testing
|-
| Wednesday
| Sanity
| DE Trunk testing
|-
| Thursday
| Sanity
| DE Trunk testing
|-
| Friday
| Sanity
| DE Trunk Testing
|-
|}

=== Core QA Team Backlog ===
The Core QA team intends to keep its backlog as public as possible. The limitation on this is the amount of work generated by doing this. We will attempt to keep an up-to-date lists of tasks and progress on these tasks. At the moment, the task list looks like this:

==== Continuous tasks ====
* Bug verification

==== Backlog ====
* Testcase automation list

==== In progress ====
* DE Hourly Automation improvement
* Wiki clean/update (waiting for comments)

==== Done ====
* * Plan Feature testset (.xml updated)
* Create weekly schedule for MRT (currently in draft form)
* Week 15 DE Sanity Testing
* Maturity statement of Alpha RELEASE (result in QA-report)
* Alpha RELEASE testing

== QA Tasks for MeeGo.com N900 ==

=== Test execution schedule ===
* MeeGo.com N900 Core weekly test schedule for MeeGo1.2(Tu Qingqing)
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release !! Priority
|-
| Monday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
|Monday
| Sanity test (OK)
| MeeGo.com trunk
| P3
|-
| Monday, Tuesday
| Basic feature test (OK)
| MeeGo.com pre-weekly
| P2
|-
| Tuesday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Tuesday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|-
| Wednesday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P2
|-
| Wednesday
| Sanity test (OK)
| MeeGo.com trunk
| P3
|-
| Wednesday, Thursday
| Dataflow (OK)
| MeeGo.com weekly
| P1
|-
| Thursday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Thursday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|-
| Friday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Friday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|}

=== META team backlog for MeeGo1.2 N900 ===

==== Continuous tasks ====
* Bug verification
* MeeGo1.2 N900 daily validation

==== Backlog ====
* Optimize acceptance automation script

==== In progress ====
* MeeGo1.2 feature verification
* Automation testing for trunk:test and trunk image

==== Done ====
* Publish automation test result

= Usefull links =

* [[ARM/N900/Install/MMC|Flashing instructions]]
Flashing tested with http://download.meego.com/testing-daily/builds/trunk/1.1.90.8.20110318.89/

[[Category:N900]]

ARM/N900/QA

2011-05-18T14:34:34Z

Hanshoi: /* OTS setup and automated hourly testing */

= Meego Developer Edition Quality Assurance =
Quality Assurance for Meego Developers Edition. Developer Edition QA uses many same components as in core Meego, therefore remember to look [[Quality|Meego core quality page.]]

== Organization ==
* Error Management
** Error Manager: Iekku Huttunen
* QA Tools
* Core Testing
* User Experience Testing (UX)

== Reports ==
* [http://wiki.meego.com/ARM/N900/Status General DE N900 Feature status]
* [http://wiki.meego.com/ARM/N900/QA/Performance Performance results]
* [http://qa-reports.meego.com/1.2/Handset/Data%20Flow%20For%20Developer%20Edition Dataflow reports]
* [http://qa-reports.meego.com/1.2/Handset/Use%20Case%20Testing%20For%20Developer%20Edition Use case reports]

== Meetings ==
QA IRC meeting every Tuesday:
* [http://wiki.meego.com/MeeGo-Meeting_IRC_Schedule MeeGo-Meeting IRC Schedule]

N900 DE Blocker Bug Triage meeting minutes:
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-12-06.59.html Meeting minutes 12-05-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-05-07.00.html Meeting minutes 05-05-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-21-07.01.html Meeting minutes 21-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-14-07.00.html Meeting minutes 14-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-07-07.02.html Meeting minutes 07-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-31-07.00.html Meeting minutes 31-03-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-24-06.59.html Meeting minutes 24-03-2011]

= QA Tools =
Developers Edition uses same QA Tools as in core Meego. For more information please refer to the [[Quality/QA-tools|Quality/QA-tools]].

== QA-Tools Task List ==
List of tasks the QA-Tools are doing for Meego Developer Edition.
If you need something from QA please tell it to us :)
=== OTS setup ===
(Open Testing System)
* [http://194.136.64.78/logger/view/ OTS server] DONE
* [http://194.136.64.78/logger/view/workers/ OTS worker(s) for core tests]- DONE
* [http://qa-reports.meego.com/1.2/Core/Hourly%20-%20Automated Reporting of hourly tests to QA-reports] - DONE
* Minimize automatic installation time to 10mins - DONE
* OTS worker for UX tests - NOTSTARTED
* OTS Worker(s) for DE tests - ONGOING (timakima)
* Power consumption measurements - NOTSTARTED

=== Test automation images ===
* Setup hourly image building for autotest image on own setup - Riku Halonen/Timo Harkonen/Ville Ilvonen - DONE (in OTS subnet, see above)
* We need to be able to control included test packages - ONGOING (http://meego.gitorious.org/meego-quality-assurance/handset-hourly-automated-tests)
* Move to use images from release engineering (1. download image, 2. install automation enablers, core dumping enablers etc. using mic-chroot, 3. install image to device 4. test) - NOT STARTED

== Applications for testing ==
* qt-demos already available from the repos
* Small applications that use Qt mobility APIs to access things like sensors to help manual testing

== Test asset ==
* [https://bugs.meego.com/buglist.cgi?quicksearch=mcts List of open bugs for MCTS]
** see priorities below - discuss with Iekku about priorities of open bugs for MCTS tests
# WLAN cases
# Call/SMS cases
# Audio policy framework cases (lower priority)
# Camera cases (lower priority)
# Sensor data cases (Qt Mobility, lower priority)

== Crash analysis support for ARM core dumps ==

[[File:Text9867-0-4-8.png|350px|thumb|right|Automated testing and crash reporting]]

Core dump processing and backtraces from crashing ARM processes (click the image on right).

* Rich Core dumping
** Make rich-core dumping to work in MeeGo N900 DE (basic functionality) - DONE (sampos, rikhalon)
*** Changes in MeeGo Gitorious ([https://meego.gitorious.org/meego-quality-assurance/rich-core/commits/meego-n900de meego-n900de] branch).
*** Dumps are generated in /home/meego/core-dumps
*** In file name, string "xxxx" is used instead of IMEI digits (privacy issue)
*** Get latest packages [http://repo.pub.meego.com/home:/rha/Project_DE_Trunk_Testing_standard/armv7l/ here]
*** Add "-corewatcher" and "-corewatcher-applet" to .ks file to remove overlapping corewatcher.
** Fix core-reducer (https://bugs.meego.com/show_bug.cgi?id=17134) - ONGOING (alkuznet)
** Oopslog (and lifelog) functionality - NOT STARTED

* Set up back-end server for core processing - ONGOING (rikhalon, sampos, timakima)

* Image building and test run triggered from cron - trigger-testrun.sh -u <URL> - DONE (timakima)

* Implement OTS Conductor plugin to fetch debug package list (before test run) and upload rich-core dumps to post-processing (after testrun )- DONE (rikhalon)

* testrunner-lite sets a UID for each test case on DUT kernel core pattern. So that a coredump can be matched with a test case - DONE (rikhalon)

* Debug image is built (simultaneuosly) on the core proscessing backend server - build-autotest-image.sh -f fs -d -p debug-packet-list -s 8000 -u <URL>, and saved as target for core prosessing - DONE (sampos)

* After each test case, cores matched against the UID are fetched from the DUT by testrunner-lite. - NOT STARTED
** testrunner-lite needs to write unique identifier to results.xml e.g. md5 hash from rich-core.
[[File:backend.png|350px|thumb|right|Core Processing Backend]]
<crashes>
<crash-id>1234567890ABCDEF</crash-id>
<crash-id>1234567890ABCDEF</crash-id>
<crash-id>1234567890ABCDEF</crash-id>
</crashes>

* The core processing backend extracts the rich core and looks for proper target (if not available waits...) - PofC DONE (sampos)

* The core processing backend chroots to the target with debug symbols and executes statically linked cross gdb for backtrace - DONE (sampos)

* Upload processed crash data using [[Quality/QA-tools/CrashReports/API|Crash Reports API]] - ONGOING (rikhalon)

== Boot time measurement ==
* Measure and optimize N900 boot time (timakima, ONGOING)

== CPU load measurement during audio/video playback ==

== Application Manager ==
* Implement an application manager (similar to one in N900/Fremantle) to control install/uninstall/update applications and other packages. (kyranto, ONGOING).

= UX testing =
== Test execution schedule ==
* UX testing schedule: DE / Meego.com testing
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release !! Priority
|-
| Monday
| Dataflow
| DE Weekly
| P1
|-
| Monday
| Use cases
| DE Weekly
| P2
|-
|Monday
| Key feature
| DE Weekly
| P3
|-
| Monday
| Performance
| DE Weekly
| P5
|-
| Monday
| Reliability / Iterative
| DE Weekly
| P6
|-
| Monday
| Dataflow
| DE Trunk testing
| P4
|-
| Tuesday
| Dataflow
| DE Trunk testing
| P1
|-
| Tuesday
| Dataflow
| DE Trunk
| P2
|-
| Tuesday
| Acceptance
| Meego Trunk testing
| P3
|-
| Tuesday
| Key feature
| DE Tablet (N900)
| P4
|-
| Wednesday
| Dataflow
| DE Trunk testing
| P1
|-
| Wednesday
| Dataflow
| DE Trunk
| P2
|-
| Wednesday
| Key feature
| Meego.com weekly
| P3
|-
| Wednesday
| Sanity
| Meego.com weekly
| P4
|-
| Thursday
| Dataflow
| DE Trunk testing
| P1
|-
| Thursday
| Dataflow
| DE Trunk
| P2
|-
| Thursday
| Acceptance
| Meego.com Trunk testing
| P3
|-
| Friday
| Dataflow
| DE Trunk Testing
| P1
|-
| Friday
| Dataflow
| DE Trunk
| P2
|-
| Friday
| Acceptance
| Meego.com Trunk testing
| P3
|}

== Performance Testing ==
Performance testing results done from UI can be found [[ARM/N900/QA/Performance|here]]

= Core Testing =
== QA Tasks For Developer Edition ==
There is a wiki article about the [[ARM/N900/DeveloperEdition|Developer Edition]].

QA tasks for the Developer Edition differ from the usual N900 approach in that there are less features to be tested. There are currently 2 test sets for the Developer Edition, these are the Sanity Test Set and the Feature Test Set. They are described below.

=== Test Sets ===
==== Sanity Test Set ====
The sanity set should be run automatically on every image. As such it must meet the following requirements:
* 100% automated
* Testing only basic features
==== Feature Test Set ====
The feature set will be run periodically and will test the basic features as well as enablers for those features (e.g. PIM for phoning contacts). Performance will also be analysed, at the moment, this will include browser startup time and a CPU benchmark but this will be expanded later.

Suggestions are welcome.

=== Testing schedule ===
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release
|-
| Monday
| Feature
| DE Weekly
|-
| Tuesday
| Sanity
| DE Trunk testing
|-
| Wednesday
| Sanity
| DE Trunk testing
|-
| Thursday
| Sanity
| DE Trunk testing
|-
| Friday
| Sanity
| DE Trunk Testing
|-
|}

=== Core QA Team Backlog ===
The Core QA team intends to keep its backlog as public as possible. The limitation on this is the amount of work generated by doing this. We will attempt to keep an up-to-date lists of tasks and progress on these tasks. At the moment, the task list looks like this:

==== Continuous tasks ====
* Bug verification

==== Backlog ====
* Testcase automation list

==== In progress ====
* DE Hourly Automation improvement
* Wiki clean/update (waiting for comments)

==== Done ====
* * Plan Feature testset (.xml updated)
* Create weekly schedule for MRT (currently in draft form)
* Week 15 DE Sanity Testing
* Maturity statement of Alpha RELEASE (result in QA-report)
* Alpha RELEASE testing

== QA Tasks for MeeGo.com N900 ==

=== Test execution schedule ===
* MeeGo.com N900 Core weekly test schedule for MeeGo1.2(Tu Qingqing)
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release !! Priority
|-
| Monday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
|Monday
| Sanity test (OK)
| MeeGo.com trunk
| P3
|-
| Monday, Tuesday
| Basic feature test (OK)
| MeeGo.com pre-weekly
| P2
|-
| Tuesday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Tuesday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|-
| Wednesday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P2
|-
| Wednesday
| Sanity test (OK)
| MeeGo.com trunk
| P3
|-
| Wednesday, Thursday
| Dataflow (OK)
| MeeGo.com weekly
| P1
|-
| Thursday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Thursday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|-
| Friday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Friday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|}

=== META team backlog for MeeGo1.2 N900 ===

==== Continuous tasks ====
* Bug verification
* MeeGo1.2 N900 daily validation

==== Backlog ====
* Optimize acceptance automation script

==== In progress ====
* MeeGo1.2 feature verification
* Automation testing for trunk:test and trunk image

==== Done ====
* Publish automation test result

= Usefull links =

* [[ARM/N900/Install/MMC|Flashing instructions]]
Flashing tested with http://download.meego.com/testing-daily/builds/trunk/1.1.90.8.20110318.89/

[[Category:N900]]

ARM/N900/QA

2011-05-18T14:28:43Z

Hanshoi: /* General info */

= Meego Developer Edition Quality Assurance =
Quality Assurance for Meego Developers Edition. Developer Edition QA uses many same components as in core Meego, therefore remember to look [[Quality|Meego core quality page.]]

== Organization ==
* Error Management
** Error Manager: Iekku Huttunen
* QA Tools
* Core Testing
* User Experience Testing (UX)

== Reports ==
* [http://wiki.meego.com/ARM/N900/Status General DE N900 Feature status]
* [http://wiki.meego.com/ARM/N900/QA/Performance Performance results]
* [http://qa-reports.meego.com/1.2/Handset/Data%20Flow%20For%20Developer%20Edition Dataflow reports]
* [http://qa-reports.meego.com/1.2/Handset/Use%20Case%20Testing%20For%20Developer%20Edition Use case reports]

== Meetings ==
QA IRC meeting every Tuesday:
* [http://wiki.meego.com/MeeGo-Meeting_IRC_Schedule MeeGo-Meeting IRC Schedule]

N900 DE Blocker Bug Triage meeting minutes:
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-12-06.59.html Meeting minutes 12-05-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-05-07.00.html Meeting minutes 05-05-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-21-07.01.html Meeting minutes 21-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-14-07.00.html Meeting minutes 14-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-07-07.02.html Meeting minutes 07-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-31-07.00.html Meeting minutes 31-03-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-24-06.59.html Meeting minutes 24-03-2011]

= QA Tools =
Developers Edition uses same QA Tools as in core Meego. For more information please refer to the [[Quality/QA-tools|Quality/QA-tools]].

== OTS setup and automated hourly testing ==

=== OTS setup ===
* [http://194.136.64.78/logger/view/ OTS server] DONE
* [http://194.136.64.78/logger/view/workers/ OTS worker(s) for core tests]- DONE
* [http://qa-reports.meego.com/1.2/Core/Hourly%20-%20Automated Reporting of hourly tests to QA-reports] - DONE
* Minimize automatic installation time to 10mins - DONE
* OTS worker for UX tests - NOTSTARTED
* OTS Worker(s) for DE tests - ONGOING (timakima)
* Power consumption measurements - NOTSTARTED

=== Test automation images ===
* Setup hourly image building for autotest image on own setup - Riku Halonen/Timo Harkonen/Ville Ilvonen - DONE (in OTS subnet, see above)

* We need to be able to control included test packages - ONGOING (http://meego.gitorious.org/meego-quality-assurance/handset-hourly-automated-tests)

* Move to use images from release engineering (1. download image, 2. install automation enablers, core dumping enablers etc. using mic-chroot, 3. install image to device 4. test) - NOT STARTED

If you need something else from QA please tell it to us :)

== Applications for testing ==
* qt-demos already available from the repos
* Small applications that use Qt mobility APIs to access things like sensors to help manual testing

== Test asset ==
* [https://bugs.meego.com/buglist.cgi?quicksearch=mcts List of open bugs for MCTS]
** see priorities below - discuss with Iekku about priorities of open bugs for MCTS tests
# WLAN cases
# Call/SMS cases
# Audio policy framework cases (lower priority)
# Camera cases (lower priority)
# Sensor data cases (Qt Mobility, lower priority)

== Crash analysis support for ARM core dumps ==

[[File:Text9867-0-4-8.png|350px|thumb|right|Automated testing and crash reporting]]

Core dump processing and backtraces from crashing ARM processes (click the image on right).

* Rich Core dumping
** Make rich-core dumping to work in MeeGo N900 DE (basic functionality) - DONE (sampos, rikhalon)
*** Changes in MeeGo Gitorious ([https://meego.gitorious.org/meego-quality-assurance/rich-core/commits/meego-n900de meego-n900de] branch).
*** Dumps are generated in /home/meego/core-dumps
*** In file name, string "xxxx" is used instead of IMEI digits (privacy issue)
*** Get latest packages [http://repo.pub.meego.com/home:/rha/Project_DE_Trunk_Testing_standard/armv7l/ here]
*** Add "-corewatcher" and "-corewatcher-applet" to .ks file to remove overlapping corewatcher.
** Fix core-reducer (https://bugs.meego.com/show_bug.cgi?id=17134) - ONGOING (alkuznet)
** Oopslog (and lifelog) functionality - NOT STARTED

* Set up back-end server for core processing - ONGOING (rikhalon, sampos, timakima)

* Image building and test run triggered from cron - trigger-testrun.sh -u <URL> - DONE (timakima)

* Implement OTS Conductor plugin to fetch debug package list (before test run) and upload rich-core dumps to post-processing (after testrun )- DONE (rikhalon)

* testrunner-lite sets a UID for each test case on DUT kernel core pattern. So that a coredump can be matched with a test case - DONE (rikhalon)

* Debug image is built (simultaneuosly) on the core proscessing backend server - build-autotest-image.sh -f fs -d -p debug-packet-list -s 8000 -u <URL>, and saved as target for core prosessing - DONE (sampos)

* After each test case, cores matched against the UID are fetched from the DUT by testrunner-lite. - NOT STARTED
** testrunner-lite needs to write unique identifier to results.xml e.g. md5 hash from rich-core.
[[File:backend.png|350px|thumb|right|Core Processing Backend]]
<crashes>
<crash-id>1234567890ABCDEF</crash-id>
<crash-id>1234567890ABCDEF</crash-id>
<crash-id>1234567890ABCDEF</crash-id>
</crashes>

* The core processing backend extracts the rich core and looks for proper target (if not available waits...) - PofC DONE (sampos)

* The core processing backend chroots to the target with debug symbols and executes statically linked cross gdb for backtrace - DONE (sampos)

* Upload processed crash data using [[Quality/QA-tools/CrashReports/API|Crash Reports API]] - ONGOING (rikhalon)

== Boot time measurement ==
* Measure and optimize N900 boot time (timakima, ONGOING)

== CPU load measurement during audio/video playback ==

== Application Manager ==
* Implement an application manager (similar to one in N900/Fremantle) to control install/uninstall/update applications and other packages. (kyranto, ONGOING).

= UX testing =
== Test execution schedule ==
* UX testing schedule: DE / Meego.com testing
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release !! Priority
|-
| Monday
| Dataflow
| DE Weekly
| P1
|-
| Monday
| Use cases
| DE Weekly
| P2
|-
|Monday
| Key feature
| DE Weekly
| P3
|-
| Monday
| Performance
| DE Weekly
| P5
|-
| Monday
| Reliability / Iterative
| DE Weekly
| P6
|-
| Monday
| Dataflow
| DE Trunk testing
| P4
|-
| Tuesday
| Dataflow
| DE Trunk testing
| P1
|-
| Tuesday
| Dataflow
| DE Trunk
| P2
|-
| Tuesday
| Acceptance
| Meego Trunk testing
| P3
|-
| Tuesday
| Key feature
| DE Tablet (N900)
| P4
|-
| Wednesday
| Dataflow
| DE Trunk testing
| P1
|-
| Wednesday
| Dataflow
| DE Trunk
| P2
|-
| Wednesday
| Key feature
| Meego.com weekly
| P3
|-
| Wednesday
| Sanity
| Meego.com weekly
| P4
|-
| Thursday
| Dataflow
| DE Trunk testing
| P1
|-
| Thursday
| Dataflow
| DE Trunk
| P2
|-
| Thursday
| Acceptance
| Meego.com Trunk testing
| P3
|-
| Friday
| Dataflow
| DE Trunk Testing
| P1
|-
| Friday
| Dataflow
| DE Trunk
| P2
|-
| Friday
| Acceptance
| Meego.com Trunk testing
| P3
|}

== Performance Testing ==
Performance testing results done from UI can be found [[ARM/N900/QA/Performance|here]]

= Core Testing =
== QA Tasks For Developer Edition ==
There is a wiki article about the [[ARM/N900/DeveloperEdition|Developer Edition]].

QA tasks for the Developer Edition differ from the usual N900 approach in that there are less features to be tested. There are currently 2 test sets for the Developer Edition, these are the Sanity Test Set and the Feature Test Set. They are described below.

=== Test Sets ===
==== Sanity Test Set ====
The sanity set should be run automatically on every image. As such it must meet the following requirements:
* 100% automated
* Testing only basic features
==== Feature Test Set ====
The feature set will be run periodically and will test the basic features as well as enablers for those features (e.g. PIM for phoning contacts). Performance will also be analysed, at the moment, this will include browser startup time and a CPU benchmark but this will be expanded later.

Suggestions are welcome.

=== Testing schedule ===
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release
|-
| Monday
| Feature
| DE Weekly
|-
| Tuesday
| Sanity
| DE Trunk testing
|-
| Wednesday
| Sanity
| DE Trunk testing
|-
| Thursday
| Sanity
| DE Trunk testing
|-
| Friday
| Sanity
| DE Trunk Testing
|-
|}

=== Core QA Team Backlog ===
The Core QA team intends to keep its backlog as public as possible. The limitation on this is the amount of work generated by doing this. We will attempt to keep an up-to-date lists of tasks and progress on these tasks. At the moment, the task list looks like this:

==== Continuous tasks ====
* Bug verification

==== Backlog ====
* Testcase automation list

==== In progress ====
* DE Hourly Automation improvement
* Wiki clean/update (waiting for comments)

==== Done ====
* * Plan Feature testset (.xml updated)
* Create weekly schedule for MRT (currently in draft form)
* Week 15 DE Sanity Testing
* Maturity statement of Alpha RELEASE (result in QA-report)
* Alpha RELEASE testing

== QA Tasks for MeeGo.com N900 ==

=== Test execution schedule ===
* MeeGo.com N900 Core weekly test schedule for MeeGo1.2(Tu Qingqing)
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release !! Priority
|-
| Monday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
|Monday
| Sanity test (OK)
| MeeGo.com trunk
| P3
|-
| Monday, Tuesday
| Basic feature test (OK)
| MeeGo.com pre-weekly
| P2
|-
| Tuesday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Tuesday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|-
| Wednesday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P2
|-
| Wednesday
| Sanity test (OK)
| MeeGo.com trunk
| P3
|-
| Wednesday, Thursday
| Dataflow (OK)
| MeeGo.com weekly
| P1
|-
| Thursday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Thursday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|-
| Friday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Friday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|}

=== META team backlog for MeeGo1.2 N900 ===

==== Continuous tasks ====
* Bug verification
* MeeGo1.2 N900 daily validation

==== Backlog ====
* Optimize acceptance automation script

==== In progress ====
* MeeGo1.2 feature verification
* Automation testing for trunk:test and trunk image

==== Done ====
* Publish automation test result

= Usefull links =

* [[ARM/N900/Install/MMC|Flashing instructions]]
Flashing tested with http://download.meego.com/testing-daily/builds/trunk/1.1.90.8.20110318.89/

[[Category:N900]]

ARM/N900/QA

2011-05-18T14:20:29Z

Hanshoi: /* OTS setup */

= General info =
Quality Assurance for Meego Developers Edition.

== Organization ==
* Error Management
** Error Manager: Iekku Huttunen
* QA Tools
* Core Testing
* User Experience Testing (UX)

== Reports ==
* [http://wiki.meego.com/ARM/N900/Status General DE N900 Feature status]
* [http://wiki.meego.com/ARM/N900/QA/Performance Performance results]
* [http://qa-reports.meego.com/1.2/Handset/Data%20Flow%20For%20Developer%20Edition Dataflow reports]
* [http://qa-reports.meego.com/1.2/Handset/Use%20Case%20Testing%20For%20Developer%20Edition Use case reports]

== Meetings ==
QA IRC meeting every Tuesday:
* [http://wiki.meego.com/MeeGo-Meeting_IRC_Schedule MeeGo-Meeting IRC Schedule]

N900 DE Blocker Bug Triage meeting minutes:
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-12-06.59.html Meeting minutes 12-05-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-05-07.00.html Meeting minutes 05-05-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-21-07.01.html Meeting minutes 21-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-14-07.00.html Meeting minutes 14-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-07-07.02.html Meeting minutes 07-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-31-07.00.html Meeting minutes 31-03-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-24-06.59.html Meeting minutes 24-03-2011]

= QA Tools =
Developers Edition uses same QA Tools as in core Meego. For more information please refer to the [[Quality/QA-tools|Quality/QA-tools]].

== OTS setup and automated hourly testing ==

=== OTS setup ===
* [http://194.136.64.78/logger/view/ OTS server] DONE
* [http://194.136.64.78/logger/view/workers/ OTS worker(s) for core tests]- DONE
* [http://qa-reports.meego.com/1.2/Core/Hourly%20-%20Automated Reporting of hourly tests to QA-reports] - DONE
* Minimize automatic installation time to 10mins - DONE
* OTS worker for UX tests - NOTSTARTED
* OTS Worker(s) for DE tests - ONGOING (timakima)
* Power consumption measurements - NOTSTARTED

=== Test automation images ===
* Setup hourly image building for autotest image on own setup - Riku Halonen/Timo Harkonen/Ville Ilvonen - DONE (in OTS subnet, see above)

* We need to be able to control included test packages - ONGOING (http://meego.gitorious.org/meego-quality-assurance/handset-hourly-automated-tests)

* Move to use images from release engineering (1. download image, 2. install automation enablers, core dumping enablers etc. using mic-chroot, 3. install image to device 4. test) - NOT STARTED

If you need something else from QA please tell it to us :)

== Applications for testing ==
* qt-demos already available from the repos
* Small applications that use Qt mobility APIs to access things like sensors to help manual testing

== Test asset ==
* [https://bugs.meego.com/buglist.cgi?quicksearch=mcts List of open bugs for MCTS]
** see priorities below - discuss with Iekku about priorities of open bugs for MCTS tests
# WLAN cases
# Call/SMS cases
# Audio policy framework cases (lower priority)
# Camera cases (lower priority)
# Sensor data cases (Qt Mobility, lower priority)

== Crash analysis support for ARM core dumps ==

[[File:Text9867-0-4-8.png|350px|thumb|right|Automated testing and crash reporting]]

Core dump processing and backtraces from crashing ARM processes (click the image on right).

* Rich Core dumping
** Make rich-core dumping to work in MeeGo N900 DE (basic functionality) - DONE (sampos, rikhalon)
*** Changes in MeeGo Gitorious ([https://meego.gitorious.org/meego-quality-assurance/rich-core/commits/meego-n900de meego-n900de] branch).
*** Dumps are generated in /home/meego/core-dumps
*** In file name, string "xxxx" is used instead of IMEI digits (privacy issue)
*** Get latest packages [http://repo.pub.meego.com/home:/rha/Project_DE_Trunk_Testing_standard/armv7l/ here]
*** Add "-corewatcher" and "-corewatcher-applet" to .ks file to remove overlapping corewatcher.
** Fix core-reducer (https://bugs.meego.com/show_bug.cgi?id=17134) - ONGOING (alkuznet)
** Oopslog (and lifelog) functionality - NOT STARTED

* Set up back-end server for core processing - ONGOING (rikhalon, sampos, timakima)

* Image building and test run triggered from cron - trigger-testrun.sh -u <URL> - DONE (timakima)

* Implement OTS Conductor plugin to fetch debug package list (before test run) and upload rich-core dumps to post-processing (after testrun )- DONE (rikhalon)

* testrunner-lite sets a UID for each test case on DUT kernel core pattern. So that a coredump can be matched with a test case - DONE (rikhalon)

* Debug image is built (simultaneuosly) on the core proscessing backend server - build-autotest-image.sh -f fs -d -p debug-packet-list -s 8000 -u <URL>, and saved as target for core prosessing - DONE (sampos)

* After each test case, cores matched against the UID are fetched from the DUT by testrunner-lite. - NOT STARTED
** testrunner-lite needs to write unique identifier to results.xml e.g. md5 hash from rich-core.
[[File:backend.png|350px|thumb|right|Core Processing Backend]]
<crashes>
<crash-id>1234567890ABCDEF</crash-id>
<crash-id>1234567890ABCDEF</crash-id>
<crash-id>1234567890ABCDEF</crash-id>
</crashes>

* The core processing backend extracts the rich core and looks for proper target (if not available waits...) - PofC DONE (sampos)

* The core processing backend chroots to the target with debug symbols and executes statically linked cross gdb for backtrace - DONE (sampos)

* Upload processed crash data using [[Quality/QA-tools/CrashReports/API|Crash Reports API]] - ONGOING (rikhalon)

== Boot time measurement ==
* Measure and optimize N900 boot time (timakima, ONGOING)

== CPU load measurement during audio/video playback ==

== Application Manager ==
* Implement an application manager (similar to one in N900/Fremantle) to control install/uninstall/update applications and other packages. (kyranto, ONGOING).

= UX testing =
== Test execution schedule ==
* UX testing schedule: DE / Meego.com testing
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release !! Priority
|-
| Monday
| Dataflow
| DE Weekly
| P1
|-
| Monday
| Use cases
| DE Weekly
| P2
|-
|Monday
| Key feature
| DE Weekly
| P3
|-
| Monday
| Performance
| DE Weekly
| P5
|-
| Monday
| Reliability / Iterative
| DE Weekly
| P6
|-
| Monday
| Dataflow
| DE Trunk testing
| P4
|-
| Tuesday
| Dataflow
| DE Trunk testing
| P1
|-
| Tuesday
| Dataflow
| DE Trunk
| P2
|-
| Tuesday
| Acceptance
| Meego Trunk testing
| P3
|-
| Tuesday
| Key feature
| DE Tablet (N900)
| P4
|-
| Wednesday
| Dataflow
| DE Trunk testing
| P1
|-
| Wednesday
| Dataflow
| DE Trunk
| P2
|-
| Wednesday
| Key feature
| Meego.com weekly
| P3
|-
| Wednesday
| Sanity
| Meego.com weekly
| P4
|-
| Thursday
| Dataflow
| DE Trunk testing
| P1
|-
| Thursday
| Dataflow
| DE Trunk
| P2
|-
| Thursday
| Acceptance
| Meego.com Trunk testing
| P3
|-
| Friday
| Dataflow
| DE Trunk Testing
| P1
|-
| Friday
| Dataflow
| DE Trunk
| P2
|-
| Friday
| Acceptance
| Meego.com Trunk testing
| P3
|}

== Performance Testing ==
Performance testing results done from UI can be found [[ARM/N900/QA/Performance|here]]

= Core Testing =
== QA Tasks For Developer Edition ==
There is a wiki article about the [[ARM/N900/DeveloperEdition|Developer Edition]].

QA tasks for the Developer Edition differ from the usual N900 approach in that there are less features to be tested. There are currently 2 test sets for the Developer Edition, these are the Sanity Test Set and the Feature Test Set. They are described below.

=== Test Sets ===
==== Sanity Test Set ====
The sanity set should be run automatically on every image. As such it must meet the following requirements:
* 100% automated
* Testing only basic features
==== Feature Test Set ====
The feature set will be run periodically and will test the basic features as well as enablers for those features (e.g. PIM for phoning contacts). Performance will also be analysed, at the moment, this will include browser startup time and a CPU benchmark but this will be expanded later.

Suggestions are welcome.

=== Testing schedule ===
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release
|-
| Monday
| Feature
| DE Weekly
|-
| Tuesday
| Sanity
| DE Trunk testing
|-
| Wednesday
| Sanity
| DE Trunk testing
|-
| Thursday
| Sanity
| DE Trunk testing
|-
| Friday
| Sanity
| DE Trunk Testing
|-
|}

=== Core QA Team Backlog ===
The Core QA team intends to keep its backlog as public as possible. The limitation on this is the amount of work generated by doing this. We will attempt to keep an up-to-date lists of tasks and progress on these tasks. At the moment, the task list looks like this:

==== Continuous tasks ====
* Bug verification

==== Backlog ====
* Testcase automation list

==== In progress ====
* DE Hourly Automation improvement
* Wiki clean/update (waiting for comments)

==== Done ====
* * Plan Feature testset (.xml updated)
* Create weekly schedule for MRT (currently in draft form)
* Week 15 DE Sanity Testing
* Maturity statement of Alpha RELEASE (result in QA-report)
* Alpha RELEASE testing

== QA Tasks for MeeGo.com N900 ==

=== Test execution schedule ===
* MeeGo.com N900 Core weekly test schedule for MeeGo1.2(Tu Qingqing)
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release !! Priority
|-
| Monday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
|Monday
| Sanity test (OK)
| MeeGo.com trunk
| P3
|-
| Monday, Tuesday
| Basic feature test (OK)
| MeeGo.com pre-weekly
| P2
|-
| Tuesday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Tuesday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|-
| Wednesday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P2
|-
| Wednesday
| Sanity test (OK)
| MeeGo.com trunk
| P3
|-
| Wednesday, Thursday
| Dataflow (OK)
| MeeGo.com weekly
| P1
|-
| Thursday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Thursday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|-
| Friday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Friday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|}

=== META team backlog for MeeGo1.2 N900 ===

==== Continuous tasks ====
* Bug verification
* MeeGo1.2 N900 daily validation

==== Backlog ====
* Optimize acceptance automation script

==== In progress ====
* MeeGo1.2 feature verification
* Automation testing for trunk:test and trunk image

==== Done ====
* Publish automation test result

= Usefull links =

* [[ARM/N900/Install/MMC|Flashing instructions]]
Flashing tested with http://download.meego.com/testing-daily/builds/trunk/1.1.90.8.20110318.89/

[[Category:N900]]

ARM/N900/Artwork

2011-05-18T12:50:17Z

Hanshoi: /* Involved people */

This is a page to help organise those interested in doing artwork/themes/images/sounds/etc for [[ARM/N900/DeveloperEdition|MeeGo N900 Developer Edition]].

== Involved people ==
{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
|-
!style="border-style: solid; border-width: 0 1px 1px 0"| Name
!style="border-style: solid; border-width: 0 1px 1px 0"| Irc-Nick
!style="border-style: solid; border-width: 0 0 1px 0"| Comment
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| Jukka Eklund
|style="border-style: solid; border-width: 0 1px 1px 0"| jukkaeklund
|style="border-style: solid; border-width: 0 0 1px 0"| can't produce anything but will give feedback and get the stuff in DE
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| Andrew Zhilin
|style="border-style: solid; border-width: 0 1px 1px 0"| wazd
|style="border-style: solid; border-width: 0 0 1px 0"| can produce everything and lead the way
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| Derek McTavish Mounce
|style="border-style: solid; border-width: 0 1px 1px 0"| hyphyphyph
|style="border-style: solid; border-width: 0 0 1px 0"| can easily conquer the world. :)
|}

== Needed artwork ==

* List what is currently missing
** Splash screens for boot and shutdown
** Wallpapers
** Sample-media: video, audio (something else than 'Big Bang Bunny' would be nice!)
*** Anssi Takku (zotte): FYI...We have a bunch of testing media files here http://testdata.meego.com/. Most of videos are about big bunny in different formats but if needed we have one resource who can generate needed video/audio/image files
** Themes (replacing or building on top of MeeGo Handset base theme or Tablet UX)
** Ring tones (phone call and SMS don't have any audios atm)
** Fonts (Nokia Pure?)

== Existing artwork ==

* List what we currently have (URL's to images, repositories, etc)
* http://meego.gitorious.org/meegotouch/meegotouch-theme
* https://picasaweb.google.com/115954093358648404696/MDEArtwork# by wazd

== Licensing ==

We should be careful with licensing such that component offerings are usable now and in the future around the entire MeeGo project.

The Creative Commons license group are seen as applicable for this, however the specific licenses usable should be identified here.

== Resources ==

* Useful resources for artwork/themes/etc within MeeGo
** [[Theming in MeeGo Touch]]
** [http://apidocs.meego.com/git-tip/mtf/styling.html Meego Touch: Styling documentation]

[[Category:N900]]