== Preface ==

In this meeting, we share the status, agree on the actions around the targets explained [[ARM/N900/DeveloperEdition | here]] (MeeGo Community Edition for N900). Naturally our priority goes to the aforementioned targets.

In short, ''The focus is on meeting the non-functional targets (such as performance) rather than number of features.''

== Agenda ==

* General information sharing (Makoto)
* Product impression (Jukka)
* Quality status (Jake)
* Progress & Bug Status (Vesku, Essi & Harri)
* AOB

== Time & Place==

* Every Tuesday at 11:00 UTC, 14:00 EEST
* 1 Hour
* @freenode, #meego-meeting

== Archive ==

* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-06-28-10.56.html 20110628]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-06-21-10.59.html 20110621]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-06-14-10.57.html 20110614]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-06-07-10.57.html 20110607]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-31-10.57.html 20110531]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-17-10.58.html 20110517]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-10-10.59.html 20110510]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-03-10.59.html 20110503]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-04-26-10.59.html 20110426]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-19-11.00.html 20110419]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-12-11.01.html 20110412]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-05-11.03.html 20110405]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-29-10.59.html 20110329]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-15-10.58.html 20110315]

[[Category:N900]]

ARM/N900/DeveloperEdition/Meetings

2011-06-21T12:09:57Z

Msugano: /* Archive */

ARM/N900/DeveloperEdition/Meetings

2011-06-14T12:00:48Z

Msugano:

ARM/N900/Performance

2011-06-14T08:51:20Z

Msugano: /* UX & Performance team */

= CE Performance page =
== UX & Performance team ==
* Communications
** IRC-channel #meego-arm at freenode
** CE daily meetings (time tbd)
** meego-handset mailing list
* Contributors
** Vesa-Matti Hartikainen IRC-nick: veskuh
** Vijay Nayani IRC-nick: vnayani
** Timo Rongas IRC-nick: ronksu
** Miroslav Safr IRC-nick: mirek or mirek2

== Problems ==

* Startup time of applications
* Startup time of the device
* Right after the homescreen has loaded, after the first boot, device is unusable for a while
* Memory use
* Slow I/O performance 2-20x slower than Maemo5 on N900
* UI scrolling freezes for 1-2s from time to time

== Task list ==
=== UX fixes ===
'''Tasks'''
* Theming bugs
* Localization issues (Apps team)
* SMS does not not notify user (mkainu)
* Orientation issue with meego-ux-apps (Ronksu)
* Close button for meego-ux based apps (selesnie)
** This should be done on generic component itself, not to individual apps
* Remove systemui looking bar from meego-ux apps (it's confusing since it is not fully functional)

'''Tasks Done'''
* Meta bug for UX and usability issues for Summer Release created:
[http://bugs.meego.com/show_bug.cgi?id=18862 Bug 18862] - [META] [DE] UX glitches and bad usability in N900 DE Summer Release

=== Reducing App Startup time ===
'''Tasks'''
* Investigate if booster really helps (veskuh)
* eMMC performance investigation, maemo is 2-20x faster? see [https://bugs.meego.com/show_bug.cgi?id=18295 bug #18295] (Q/A team to rerun the tests)
* last resort type of thing: taking NAND to use as swap (and destroying maemo installation)

'''Tasks Done'''
* eMMC vs. MMC, according to Sage, no major difference in old experiments

=== Reducing memory use ===
'''Tasks'''
* Remove unused applifed processes. (Ronksu)
* lower GLES ParamBuffer size (veskuh)
* Merge meego-volume-control to systemui (jpeltonen)
* adjust stack sizes
* zram (formerly known as ramzswap and compcache) trial (tazpa)

'''Tasks Done'''
* meego-ux to drop GL-context: https://bugs.meego.com/show_bug.cgi?id=18268

=== Improving first boot ===
'''Tasks'''
* tracker to preindex filesystem to improve first boot. see [https://bugs.meego.com/show_bug.cgi?id=18759 bug #18759] (maitrey)
* Reduce the number of .desktop files and icons meegohome scans at first boot (vnayani)
* Reduce I/O priority of tracker-miner and tracker-store (use ionice to to launch)
* delay start of tracker indexing
'''Tasks Done'''

=== Improving system startup ===
'''Tasks'''
* Reduce the list of [[ARM/N900/Performance/autostart|autostarted apps.]]
* Delay the startup of dialer trackers to happen once destop is ready (lamikr)
* tracker configuration (maitrey)

'''Tasks Done'''
* autostarted backlight setup.desktop file removed from the nokia-n900-configs (mce handles backlight) (lamikr)
* bootchart generated svg from the N900 processes starting up attached to bug https://bugs.meego.com/show_bug.cgi?id=9527 (lamikr)

=== Improving UI Performance ===
'''Tasks'''
* Check if newer MTF improves performance (mirek)
* Check if newer Qt improves performance
'''Tasks Done'''

=== Misc ===
'''Tasks'''
* optimizing MTF packages, there might be some configuration options, etc.?
* CGROUPS optimization, most likely still not done
* cache some often used data in NAND and symlink there
* test overclock with known testing (from qa-tools guys perhaps)
** kjokinie: Tested on my set up boot-times with some [[ARM/N900/Performance/OverclockBootTimeTest | overclock configurations]] already
*** practically it does not help at least boot time
*** however, at least audio player seemed much more responsive, so application performances should still be tested by QA.
* real microsdhc tests based on class speed rating
** actually answer specific questions about how write/read speed effect perf
*** app startup times
*** general usage
*** media write times
*** cataloguing media
* Swap on memory card (probably will not help if the os is on the card also, otherwise might)
* Taking fennec more frequently from upstream beta repository http://lists.meego.com/pipermail/meego-handset/2011-June/000467.html
* Profile startup of simple MTF, QML, and Qt apps
* Profile memory use of simple MTF, QML, and Qt apps
* Investigate configuration options for MTF
* Investigate configuration options for Qt
* Investigate configuration options for QML
* Update MTF (libmeegotouch, mcompositor, home, system ui, etc. ) to get latest optimizations from upstream
* Update Qt
'''Tasks Done'''
* Carsten tweaked kernel virtual memory settings (increased swappiness), Fennec bootup improved a lot and also system responsivness
* thumbnails images for pre-installed images should be done during the build time. (Now thumbnails are generated only when user wants to get the image list and that takes times)

== Benchmark results ==
* Results from Q/A http://wiki.meego.com/ARM/N900/QA/Performance
* Different class SD card benchmarking
** [[File:SDcard_benchmarking_060611.jpg]]
** Used image 05-30.1 acceptance image
** With class 10 card image worked really unstable. Measurements were got after several tries.
** Current class10 measurements are not comparable but give somekind of direction
* SunSpider (JavaScript performance
** 6.1s with GPE MiniBrowser (image DE.2011-05-30 acceptance)
** 6.8s with Fennec (image DE.2011-05-30 acceptance)
** These are actually pretty good results. Indicates that raw CPU perfomance is ok.
* widgetsgallery -timedemo -log-fps
Page name StaticPageBenchmark (0) PanningBenchmark (0) RotationBenchmark (90) StaticPageBenchmark (90) PanningBenchmark (90) RotationBenchmark (0)
ApplicationMenu 48fps | 2988ms n/a | n/a 25fps | 557ms 53fps | 2984ms n/a | n/a 29fps | 578ms
DisplayModes 55fps | 2989ms 54fps | 421ms 40fps | 574ms 53fps | 2983ms n/a | n/a 47fps | 546ms
ToolBar 51fps | 2972ms 41fps | 503ms 34fps | 602ms 55fps | 2998ms 46fps | 298ms 20fps | 250ms
CustomNavigationBar 53fps | 2989ms n/a | n/a 46fps | 579ms 54fps | 2980ms n/a | n/a 52fps | 572ms
Label 50fps | 3157ms 45fps | 87ms n/a | n/a 54fps | 2989ms n/a | n/a 40fps | 573ms
Image 55fps | 2996ms 55fps | 379ms n/a | n/a 52fps | 2989ms 54fps | 129ms 7fps | 139ms
ProgressBar 49fps | 2981ms n/a | n/a 34fps | 644ms 54fps | 2973ms n/a | n/a 36fps | 627ms
Spinner 52fps | 2989ms n/a | n/a n/a | n/a 53fps | 2989ms n/a | n/a 27fps | 436ms
PushButton 48fps | 2982ms 45fps | 3427ms 28fps | 671ms 47fps | 2985ms 44fps | 4521ms n/a | n/a
IconButton 52fps | 2991ms n/a | n/a 35fps | 674ms 54fps | 2989ms n/a | n/a 38fps | 621ms
Switch 54fps | 2989ms n/a | n/a 31fps | 694ms 54fps | 2991ms n/a | n/a 28fps | 657ms
Checkbox 52fps | 2989ms n/a | n/a 30fps | 780ms 54fps | 2997ms n/a | n/a 38fps | 649ms
ButtonGroup 53fps | 3005ms 27fps | 323ms n/a | n/a 50fps | 2988ms 52fps | 491ms n/a | n/a
SingleSelectionDialogsPage 56fps | 2998ms 46fps | 345ms n/a | n/a 53fps | 3004ms n/a | n/a 42fps | 654ms
QueryDialogsPage 50fps | 2997ms n/a | n/a 35fps | 696ms 53fps | 2987ms n/a | n/a 36fps | 655ms
SheetsPage 54fps | 2988ms 59fps | 151ms n/a | n/a 55fps | 2982ms n/a | n/a 40fps | 666ms
BannersPage 51fps | 2996ms n/a | n/a 37fps | 740ms 54fps | 3000ms n/a | n/a 38fps | 671ms
NotificationsPage 54fps | 2994ms n/a | n/a 35fps | 733ms 55fps | 3000ms n/a | n/a 39fps | 678ms
List 54fps | 2989ms 53fps |20539ms 2fps | 485ms 56fps | 2973ms 51fps |19630ms n/a | n/a
Grid 16fps | 2961ms 48fps | 2777ms 16fps | 1016ms 42fps | 3147ms 48fps | 3252ms n/a | n/a
ObjectMenu 44fps | 2988ms 52fps | 248ms n/a | n/a 54fps | 2991ms 55fps | 181ms n/a | n/a
ComboBox 52fps | 2946ms n/a | n/a 25fps | 856ms 53fps | 2984ms n/a | n/a 30fps | 784ms
ContentItems 55fps | 2987ms 39fps | 4197ms n/a | n/a 54fps | 2988ms 29fps | 3483ms 7fps | 407ms
SpeechBubble 52fps | 2986ms 47fps | 3842ms n/a | n/a 51fps | 2989ms 29fps | 3906ms n/a | n/a
TextEntry 54fps | 2988ms 43fps | 3209ms n/a | n/a 52fps | 2988ms 35fps | 2541ms n/a | n/a
TextEntryNavigation 53fps | 2989ms n/a | n/a 18fps | 912ms 50fps | 2982ms n/a | n/a 22fps | 794ms
TextEntryAttributeExtension 54fps | 2988ms 41fps | 192ms n/a | n/a 53fps | 2988ms n/a | n/a 19fps | 860ms
Slider 54fps | 2997ms 37fps | 404ms n/a | n/a 53fps | 2989ms n/a | n/a 18fps | 865ms
InputFeedback 52fps | 2988ms 55fps | 90ms 19fps | 902ms 40fps | 2988ms 43fps | 69ms n/a | n/a
Information Display 53fps | 3001ms 26fps | 188ms 24fps | 930ms 54fps | 2999ms n/a | n/a 28fps | 857ms
Take a screenshot 49fps | 3217ms n/a | n/a 23fps | 1028ms 55fps | 2978ms n/a | n/a 26fps | 893ms
** Conclusion: Graphis performance seems to be ok

* processes eating more than 2000kb of memory (2010-06-08)
** (ps -e -orss=,args= | sort -b -k1,1n | pr -TW100)
<nowiki>
2016 /usr/sbin/ofonod
2228 /usr/sbin/connmand -W nl80211,wext
2400 uxlaunch
2616 /sbin/mce -d
2624 /usr/libexec/upowerd
2952 /usr/sbin/dsme -p /usr/lib/dsme/libstartup.so
3084 /usr/libexec/mission-control-5
3440 /usr/bin/meego-volume-control
3616 /usr/sbin/sensord -c=/etc/sensorfw/sensord-rx_51.conf -d --log-target=4 --log-file-path=/var/l
3900 /usr/bin/timed
3984 /usr/lib/tumbler-1/tumblerd
4084 /usr/bin/pulseaudio --start -n --file=/etc/pulse/arm_nokia_rx_51_board.pa
4564 /usr/sbin/ohmd
7172 /usr/libexec/tracker-miner-fs
7460 /usr/bin/applifed
12384 /usr/bin/applauncherd.bin
14160 /usr/libexec/tracker-store
14524 /usr/bin/messageserver
16568 /usr/bin/Xorg :0 -dpi 120 -nolisten tcp -noreset -auth /home/meego/.Xauthority -nocursor vt2
20108 /usr/bin/mthemedaemon
21676 /usr/bin/mcompositor
26820 /usr/bin/meego-im-uiserver -remote-theme
27344 booster-m
27852 /usr/bin/mdecorator -software -remote-theme
32620 /usr/bin/sysuid -remote-theme
33172 /usr/bin/meegotouchhome -remote-theme
38544 /usr/bin/dialer -prestart
</nowiki>

* Conclusion: meego-volume-control went down from 26000 kb to 3440 thanks for the qml ripout
* Can we reduce the mem usage of processes like sysuid, mdecorator, mthemedaemon
* Is booster-m really improving our performance as it takes itself a lot of from our memory that we do not have any extra without swapping?
** by removing the applauncherd (process starting booster-m) and tracker-store and delaying the dialer ui (40000 kb) launch by 30 second, bootup time will improved from 72 second to 59.

== Tools & Links ==
* Smaps (Memory use) http://wiki.meego.com/ARM/N900/Developers/Sp_smaps_snapshot
* [[ARM/N900/Performance/bootup_memory_usage_script|Bootup script for collecting ]] data from smaps and other memory usage tools
* Bonnie (I/O performance) http://wiki.meego.com/Bonnie
* [[ARM/N900/Performance/bootchart|Bootchart for measuring bootup details ]]
* Gprof
* Perf http://omappedia.org/wiki/Using_perf
* IOtop http://guichaz.free.fr/iotop/
* vmstat
* iostat
* Oprofile (obsolete, use perf instead)
* More: http://wiki.meego.com/SDK/Developer_tools
* QML Performance Monitor: http://labs.qt.nokia.com/2011/04/07/qml-perfomance-monitor/
* libmeegotouch benchmarks: http://meego.gitorious.net/meegotouch/libmeegotouch/trees/master/benchmarks

== Ideas ==

Use settings from M5 rc scripts, such as reducing ptys, etc to save memory

== Team meeting minutes ==
http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-06-10-06.58.html

ARM/N900/Performance

2011-06-14T08:50:53Z

Msugano: /* CE Performance page */

= CE Performance page =
== UX & Performance team ==
* Communications
** IRC-channel #meego-arm at freenode
** DE daily meetings (time tbd)
** meego-handset mailing list
* Contributors
** Vesa-Matti Hartikainen IRC-nick: veskuh
** Vijay Nayani IRC-nick: vnayani
** Timo Rongas IRC-nick: ronksu
** Miroslav Safr IRC-nick: mirek or mirek2

== Problems ==

* Startup time of applications
* Startup time of the device
* Right after the homescreen has loaded, after the first boot, device is unusable for a while
* Memory use
* Slow I/O performance 2-20x slower than Maemo5 on N900
* UI scrolling freezes for 1-2s from time to time

== Task list ==
=== UX fixes ===
'''Tasks'''
* Theming bugs
* Localization issues (Apps team)
* SMS does not not notify user (mkainu)
* Orientation issue with meego-ux-apps (Ronksu)
* Close button for meego-ux based apps (selesnie)
** This should be done on generic component itself, not to individual apps
* Remove systemui looking bar from meego-ux apps (it's confusing since it is not fully functional)

'''Tasks Done'''
* Meta bug for UX and usability issues for Summer Release created:
[http://bugs.meego.com/show_bug.cgi?id=18862 Bug 18862] - [META] [DE] UX glitches and bad usability in N900 DE Summer Release

=== Reducing App Startup time ===
'''Tasks'''
* Investigate if booster really helps (veskuh)
* eMMC performance investigation, maemo is 2-20x faster? see [https://bugs.meego.com/show_bug.cgi?id=18295 bug #18295] (Q/A team to rerun the tests)
* last resort type of thing: taking NAND to use as swap (and destroying maemo installation)

'''Tasks Done'''
* eMMC vs. MMC, according to Sage, no major difference in old experiments

=== Reducing memory use ===
'''Tasks'''
* Remove unused applifed processes. (Ronksu)
* lower GLES ParamBuffer size (veskuh)
* Merge meego-volume-control to systemui (jpeltonen)
* adjust stack sizes
* zram (formerly known as ramzswap and compcache) trial (tazpa)

'''Tasks Done'''
* meego-ux to drop GL-context: https://bugs.meego.com/show_bug.cgi?id=18268

=== Improving first boot ===
'''Tasks'''
* tracker to preindex filesystem to improve first boot. see [https://bugs.meego.com/show_bug.cgi?id=18759 bug #18759] (maitrey)
* Reduce the number of .desktop files and icons meegohome scans at first boot (vnayani)
* Reduce I/O priority of tracker-miner and tracker-store (use ionice to to launch)
* delay start of tracker indexing
'''Tasks Done'''

=== Improving system startup ===
'''Tasks'''
* Reduce the list of [[ARM/N900/Performance/autostart|autostarted apps.]]
* Delay the startup of dialer trackers to happen once destop is ready (lamikr)
* tracker configuration (maitrey)

'''Tasks Done'''
* autostarted backlight setup.desktop file removed from the nokia-n900-configs (mce handles backlight) (lamikr)
* bootchart generated svg from the N900 processes starting up attached to bug https://bugs.meego.com/show_bug.cgi?id=9527 (lamikr)

=== Improving UI Performance ===
'''Tasks'''
* Check if newer MTF improves performance (mirek)
* Check if newer Qt improves performance
'''Tasks Done'''

=== Misc ===
'''Tasks'''
* optimizing MTF packages, there might be some configuration options, etc.?
* CGROUPS optimization, most likely still not done
* cache some often used data in NAND and symlink there
* test overclock with known testing (from qa-tools guys perhaps)
** kjokinie: Tested on my set up boot-times with some [[ARM/N900/Performance/OverclockBootTimeTest | overclock configurations]] already
*** practically it does not help at least boot time
*** however, at least audio player seemed much more responsive, so application performances should still be tested by QA.
* real microsdhc tests based on class speed rating
** actually answer specific questions about how write/read speed effect perf
*** app startup times
*** general usage
*** media write times
*** cataloguing media
* Swap on memory card (probably will not help if the os is on the card also, otherwise might)
* Taking fennec more frequently from upstream beta repository http://lists.meego.com/pipermail/meego-handset/2011-June/000467.html
* Profile startup of simple MTF, QML, and Qt apps
* Profile memory use of simple MTF, QML, and Qt apps
* Investigate configuration options for MTF
* Investigate configuration options for Qt
* Investigate configuration options for QML
* Update MTF (libmeegotouch, mcompositor, home, system ui, etc. ) to get latest optimizations from upstream
* Update Qt
'''Tasks Done'''
* Carsten tweaked kernel virtual memory settings (increased swappiness), Fennec bootup improved a lot and also system responsivness
* thumbnails images for pre-installed images should be done during the build time. (Now thumbnails are generated only when user wants to get the image list and that takes times)

== Benchmark results ==
* Results from Q/A http://wiki.meego.com/ARM/N900/QA/Performance
* Different class SD card benchmarking
** [[File:SDcard_benchmarking_060611.jpg]]
** Used image 05-30.1 acceptance image
** With class 10 card image worked really unstable. Measurements were got after several tries.
** Current class10 measurements are not comparable but give somekind of direction
* SunSpider (JavaScript performance
** 6.1s with GPE MiniBrowser (image DE.2011-05-30 acceptance)
** 6.8s with Fennec (image DE.2011-05-30 acceptance)
** These are actually pretty good results. Indicates that raw CPU perfomance is ok.
* widgetsgallery -timedemo -log-fps
Page name StaticPageBenchmark (0) PanningBenchmark (0) RotationBenchmark (90) StaticPageBenchmark (90) PanningBenchmark (90) RotationBenchmark (0)
ApplicationMenu 48fps | 2988ms n/a | n/a 25fps | 557ms 53fps | 2984ms n/a | n/a 29fps | 578ms
DisplayModes 55fps | 2989ms 54fps | 421ms 40fps | 574ms 53fps | 2983ms n/a | n/a 47fps | 546ms
ToolBar 51fps | 2972ms 41fps | 503ms 34fps | 602ms 55fps | 2998ms 46fps | 298ms 20fps | 250ms
CustomNavigationBar 53fps | 2989ms n/a | n/a 46fps | 579ms 54fps | 2980ms n/a | n/a 52fps | 572ms
Label 50fps | 3157ms 45fps | 87ms n/a | n/a 54fps | 2989ms n/a | n/a 40fps | 573ms
Image 55fps | 2996ms 55fps | 379ms n/a | n/a 52fps | 2989ms 54fps | 129ms 7fps | 139ms
ProgressBar 49fps | 2981ms n/a | n/a 34fps | 644ms 54fps | 2973ms n/a | n/a 36fps | 627ms
Spinner 52fps | 2989ms n/a | n/a n/a | n/a 53fps | 2989ms n/a | n/a 27fps | 436ms
PushButton 48fps | 2982ms 45fps | 3427ms 28fps | 671ms 47fps | 2985ms 44fps | 4521ms n/a | n/a
IconButton 52fps | 2991ms n/a | n/a 35fps | 674ms 54fps | 2989ms n/a | n/a 38fps | 621ms
Switch 54fps | 2989ms n/a | n/a 31fps | 694ms 54fps | 2991ms n/a | n/a 28fps | 657ms
Checkbox 52fps | 2989ms n/a | n/a 30fps | 780ms 54fps | 2997ms n/a | n/a 38fps | 649ms
ButtonGroup 53fps | 3005ms 27fps | 323ms n/a | n/a 50fps | 2988ms 52fps | 491ms n/a | n/a
SingleSelectionDialogsPage 56fps | 2998ms 46fps | 345ms n/a | n/a 53fps | 3004ms n/a | n/a 42fps | 654ms
QueryDialogsPage 50fps | 2997ms n/a | n/a 35fps | 696ms 53fps | 2987ms n/a | n/a 36fps | 655ms
SheetsPage 54fps | 2988ms 59fps | 151ms n/a | n/a 55fps | 2982ms n/a | n/a 40fps | 666ms
BannersPage 51fps | 2996ms n/a | n/a 37fps | 740ms 54fps | 3000ms n/a | n/a 38fps | 671ms
NotificationsPage 54fps | 2994ms n/a | n/a 35fps | 733ms 55fps | 3000ms n/a | n/a 39fps | 678ms
List 54fps | 2989ms 53fps |20539ms 2fps | 485ms 56fps | 2973ms 51fps |19630ms n/a | n/a
Grid 16fps | 2961ms 48fps | 2777ms 16fps | 1016ms 42fps | 3147ms 48fps | 3252ms n/a | n/a
ObjectMenu 44fps | 2988ms 52fps | 248ms n/a | n/a 54fps | 2991ms 55fps | 181ms n/a | n/a
ComboBox 52fps | 2946ms n/a | n/a 25fps | 856ms 53fps | 2984ms n/a | n/a 30fps | 784ms
ContentItems 55fps | 2987ms 39fps | 4197ms n/a | n/a 54fps | 2988ms 29fps | 3483ms 7fps | 407ms
SpeechBubble 52fps | 2986ms 47fps | 3842ms n/a | n/a 51fps | 2989ms 29fps | 3906ms n/a | n/a
TextEntry 54fps | 2988ms 43fps | 3209ms n/a | n/a 52fps | 2988ms 35fps | 2541ms n/a | n/a
TextEntryNavigation 53fps | 2989ms n/a | n/a 18fps | 912ms 50fps | 2982ms n/a | n/a 22fps | 794ms
TextEntryAttributeExtension 54fps | 2988ms 41fps | 192ms n/a | n/a 53fps | 2988ms n/a | n/a 19fps | 860ms
Slider 54fps | 2997ms 37fps | 404ms n/a | n/a 53fps | 2989ms n/a | n/a 18fps | 865ms
InputFeedback 52fps | 2988ms 55fps | 90ms 19fps | 902ms 40fps | 2988ms 43fps | 69ms n/a | n/a
Information Display 53fps | 3001ms 26fps | 188ms 24fps | 930ms 54fps | 2999ms n/a | n/a 28fps | 857ms
Take a screenshot 49fps | 3217ms n/a | n/a 23fps | 1028ms 55fps | 2978ms n/a | n/a 26fps | 893ms
** Conclusion: Graphis performance seems to be ok

* processes eating more than 2000kb of memory (2010-06-08)
** (ps -e -orss=,args= | sort -b -k1,1n | pr -TW100)
<nowiki>
2016 /usr/sbin/ofonod
2228 /usr/sbin/connmand -W nl80211,wext
2400 uxlaunch
2616 /sbin/mce -d
2624 /usr/libexec/upowerd
2952 /usr/sbin/dsme -p /usr/lib/dsme/libstartup.so
3084 /usr/libexec/mission-control-5
3440 /usr/bin/meego-volume-control
3616 /usr/sbin/sensord -c=/etc/sensorfw/sensord-rx_51.conf -d --log-target=4 --log-file-path=/var/l
3900 /usr/bin/timed
3984 /usr/lib/tumbler-1/tumblerd
4084 /usr/bin/pulseaudio --start -n --file=/etc/pulse/arm_nokia_rx_51_board.pa
4564 /usr/sbin/ohmd
7172 /usr/libexec/tracker-miner-fs
7460 /usr/bin/applifed
12384 /usr/bin/applauncherd.bin
14160 /usr/libexec/tracker-store
14524 /usr/bin/messageserver
16568 /usr/bin/Xorg :0 -dpi 120 -nolisten tcp -noreset -auth /home/meego/.Xauthority -nocursor vt2
20108 /usr/bin/mthemedaemon
21676 /usr/bin/mcompositor
26820 /usr/bin/meego-im-uiserver -remote-theme
27344 booster-m
27852 /usr/bin/mdecorator -software -remote-theme
32620 /usr/bin/sysuid -remote-theme
33172 /usr/bin/meegotouchhome -remote-theme
38544 /usr/bin/dialer -prestart
</nowiki>

* Conclusion: meego-volume-control went down from 26000 kb to 3440 thanks for the qml ripout
* Can we reduce the mem usage of processes like sysuid, mdecorator, mthemedaemon
* Is booster-m really improving our performance as it takes itself a lot of from our memory that we do not have any extra without swapping?
** by removing the applauncherd (process starting booster-m) and tracker-store and delaying the dialer ui (40000 kb) launch by 30 second, bootup time will improved from 72 second to 59.

== Tools & Links ==
* Smaps (Memory use) http://wiki.meego.com/ARM/N900/Developers/Sp_smaps_snapshot
* [[ARM/N900/Performance/bootup_memory_usage_script|Bootup script for collecting ]] data from smaps and other memory usage tools
* Bonnie (I/O performance) http://wiki.meego.com/Bonnie
* [[ARM/N900/Performance/bootchart|Bootchart for measuring bootup details ]]
* Gprof
* Perf http://omappedia.org/wiki/Using_perf
* IOtop http://guichaz.free.fr/iotop/
* vmstat
* iostat
* Oprofile (obsolete, use perf instead)
* More: http://wiki.meego.com/SDK/Developer_tools
* QML Performance Monitor: http://labs.qt.nokia.com/2011/04/07/qml-perfomance-monitor/
* libmeegotouch benchmarks: http://meego.gitorious.net/meegotouch/libmeegotouch/trees/master/benchmarks

== Ideas ==

Use settings from M5 rc scripts, such as reducing ptys, etc to save memory

== Team meeting minutes ==
http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-06-10-06.58.html

2011-05-11T12:30:26Z

Msugano: /* Tips and Tricks */

= Developer's corner =

== Useful tools / scripts / etc ==

* [[bonnie | Bonnie++ disk IO benchmark utility]]

== Tips and Tricks ==

* msugano wanted to branch uxlanuch from the public OBS to his home in the community OBS.

On his local laptop:

$ osc -A https://api.pub.meego.com branch -cm "would like to experiment e.g. xsetroot right after the start_X_server() to enhance the UX." MeeGo.com:MeeGo:1.2:oss uxlaunch

* The new project was downloaded to his local environment. Now, it's possible to edit the source.
* The new project was created in the community OBS under msugano's home (Build Service > Projects > home:msugano:branches:MeeGo.com:MeeGo:1.2:oss > uxlaunch).
* However, the above project page says ''The project this package belongs to currently has no build targets defined.''
* Hence, msugano clicked the linked to "build targets" to specify, but could not find any target build that looked relevant for the DE.
* Then msugano received the advice to use the command line instead.
* osc meta prj Project:DE:Trunk:Testing

== Links ==

Placeholder, let's start linking relevant information on this page.

ARM/N900/Developers

2011-05-11T12:29:12Z

Msugano: /* Tips and Tricks */

ARM/N900/Developers

2011-05-11T12:29:01Z

Msugano: /* Tips and Tricks */

2011-04-19T13:27:59Z

Msugano: /* Organization */

= MeeGo 1.2 Developer Edition for N900 =

== Target ==

Target is to make a Developer Edition of MeeGo for the Nokia N900 device. Flashed with this edition N900 will be usable as a primary phone device for a developer/hacker person. '''This is not for regular Maemo 5 end users'''.

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 trunk content. MeeGo features are found in [https://bugs.meego.com/ bugzilla].

You can join the development and discussion at the [http://lists.meego.com/listinfo/meego-handset meego-handset mailing list] and in IRC (#meego-arm @freenode).

== Key features ==

'''Do not edit these directly, instead add feedback to the bottom of page'''. These use cases shall be the prominent ones in the device Home screen. In addition there will be separate folder containing other available Handset apps from repositories, and there is a possibility to promote any app to the main view if the non-functional targets are met.

'''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's MeeGo 1.2 compliant.

== Organization ==

* Core team is formed in and around Nokia.
* 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: This project is merged with the MeeGo mainstream [http://wiki.meego.com/Project/Dialer Dialer project], lead by sabotage. Makoto acts as the bridge in between.
*** [[ARM/N900/Browser|Browser and 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], including current [[ARM/N900|N900 HW adaptation team]].
*** Architect: [http://meego.com/users/mythi Mikko Ylinen]
*** Release & integration: [http://meego.com/users/kad Alexander Kanevskiy], [http://meego.com/users/ericlr Eric Le Roux]
** [[ARM/N900/QA|QA]] lead: [http://meego.com/users/jaritah Jari Tahvanainen]
** [[ARM/N900/PM|Product management]]: [http://meego.com/users/jukkaeklund Jukka Eklund], [http://meego.com/users/samipienimaki Sami Pienimäki]

* 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!

== Schedule ==

* '''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].

* '''MeeGo Conference release''': on week 20
* "Summer release" by end of June

The criteria and content for the milestones will be defined further, but this is just to show our '''target schedule'''.

== Status ==

See the [[ARM/N900/Status|Status]] page for reports.

== Meetings ==

* Work space in IRC (@freenode, #meego-arm) and regular MeeGo mail lists (primarily we will be using [http://lists.meego.com/listinfo/meego-handset meego-handset@meego.com].
* [[ARM/N900/DeveloperEdition/Meetings|Weekly team meetings]] are held in the public IRC. The agenda and the archives are also available. This meeting is registered on the [[MeeGo-Meeting_IRC_Schedule|MeeGo IRC Meeting Page]].

== Installing and running ==

* Developer Edition images: [http://repository.maemo.org/meego/n900-de/ download here], see also [[ARM/N900/ReleaseProcess]]. Check the [http://qa-reports.meego.com/1.2/Handset/Data%20Flow%20For%20Developer%20Edition/N900 Data flow] and [http://qa-reports.meego.com/1.2/Handset/Use%20Case%20Testing%20For%20Developer%20Edition/N900 Use case] test results before downloading.
** '''Before installing please read about the recommended method: [[ARM/N900/Install/Dual_Boot|dual boot installation]]'''. That way you can keep Maemo on the device at same time.
* [[ARM/N900/Install/MMC#Installing_Rootfs_on_external_MMC_card|Flashing instructions]] (when using dual boot method, no need to flash/load the kernel separately).
* There is also some more [[ARM/N900/CoolStuff|Cool stuff]] to try on top of the MeeGo image.

== 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]] gives the overview on the daily development workflow. Thanks Fathi Boudra & Markus Lehtonen for the contribution. Also any suggestion where to locate the links to this material is appreciated.

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]
* 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 with the Tablet UX on N900. Find more details on [[ARM/N900/TabletUX]].
* Look into learning QML if you haven't already.
* Would like to contribute the test cases? You will find the useful information [[Quality|here]].
* Would like to contribute artwork? See [[ARM/N900/Artwork]].

== 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. This is work in progress. See the [[ARM/N900/ReleaseProcess|release process]] explained by Carsten.

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/DeveloperEdition/Meetings

2011-04-19T12:03:11Z

Msugano: /* Archive */

ARM/N900/DeveloperEdition/Meetings

2011-04-12T12:08:39Z

Msugano: /* Archive */

ARM/N900/DeveloperEdition

2011-04-08T09:20:00Z

Msugano: /* FAQ */

= MeeGo 1.2 Developer Edition for N900 =

== Target ==

Target is to make a Developer Edition of MeeGo for the Nokia N900 device. Flashed with this edition N900 will be usable as a primary phone device for a developer/hacker person. '''This will not be something for regular end users'''.

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 trunk content. MeeGo features are found in [https://bugs.meego.com/ bugzilla].

You can join the development and discussion at the [http://lists.meego.com/listinfo/meego-handset meego-handset mailing list] and in IRC (#meego-arm @freenode).

== Use cases (do not edit these directly, instead add feedback to the bottom of page) ==

These use cases shall be the prominent ones in the device Home screen. In addition there will be separate folder containing other available Handset apps from repositories, and there is a possibility to promote any app to the main view if the non-functional targets are met.

'''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)

'''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's MeeGo 1.2 compliant.

== Organization ==

* Core team is being formed in and around Nokia.
* 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/essi Essi Vehmersalo]
*** [[ARM/N900/Browser|Browser and 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], including current [[ARM/N900|N900 HW adaptation team]].
*** Architect: [http://meego.com/users/mythi Mikko Ylinen]
*** Release & integration: [http://meego.com/users/kad Alexander Kanevskiy], [http://meego.com/users/ericlr Eric Le Roux]
** [[ARM/N900/QA|QA]] lead: [http://meego.com/users/jkunnari Jake Kunnari]
** [[ARM/N900/PM|Product management]]: [http://meego.com/users/jukkaeklund Jukka Eklund], [http://meego.com/users/samipienimaki Sami Pienimäki]

* Community involvement is very desirable, and there will lots of areas to contribute (see below).

== Schedule ==

* Alpha release: on week 15
** Official DE image available with some overlays on top of MeeGo 1.2 trunk (see [[ARM/N900/Configuration]]).
** Calls, SMS and Browser should be in a demoable state (MeeGo Summit FI). Camera as a bonus.
** Some key performance and usability items fixed (PM kernel, backlight control)

* Beta release: on week 20 (MeeGo Conference)
** TBD

* Final release candidate: on week 25

The criteria and content for the milestones will be defined further, but this is just to show our '''target schedule'''.

== Status ==

See the [[ARM/N900/Status|Status]] page for reports.

== Meetings ==

* Work space in IRC (@freenode, #meego-arm) and regular MeeGo mail lists (primarily we will be using [http://lists.meego.com/listinfo/meego-handset meego-handset@meego.com].
* [[ARM/N900/DeveloperEdition/Meetings|Weekly team meetings]] are held in the public IRC. The agenda and the archives are also available. This meeting is registered on the [[MeeGo-Meeting_IRC_Schedule|MeeGo IRC Meeting Page]].

== Installing and running ==

* N900 Handset images: [http://repo.meego.com/MeeGo/builds/trunk/latest/ weekly build], [http://download.meego.com/trunk-daily/builds/trunk/latest/ Trunk-daily], [http://download.meego.com/testing-daily/builds/trunk/latest/ Trunk-Testing]
** See the [[Release Engineering/Repo List|release engineering repository list]] for explanation of different images.
** '''Before installing please read about the recommended method: [[ARM/N900/Install/Dual_Boot|dual boot installation]]'''. That way you can keep Maemo on the device at same time.
* Developer Edition images: Coming soon, see [[ARM/N900/ReleaseProcess]]. PM recommends to try with current [http://qa-reports.meego.com/1.2/Handset/Acceptance/N900 Acceptance images]. Check the test results, and if they look good you can find the image name in the report.
* [[ARM/N900/Install/MMC#Installing_Rootfs_on_external_MMC_card|Flashing instructions]] (when using dual boot method, no need to flash/load the kernel separately).
* Tips and tricks (please add yours here!)
** Connect to WLAN: Settings->Applications->WiFiApplet
* There is also some more [[ARM/N900/CoolStuff|Cool stuff]] to try on top of the MeeGo image.

== 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]] gives the overview on the daily development workflow. Thanks Fathi Boudra & Markus Lehtonen for the contribution. Also any suggestion where to locate the links to this material is appreciated.

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]
* 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 with the Tablet UX on N900. Find more details on [[ARM/N900/TabletUX]].
* Look into learning QML if you haven't already.
* Would like to contribute the test cases? You will find the useful information [[Quality|here]].
* Would like to contribute artwork? See [[ARM/N900/Artwork]].

== 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. This is work in progress. See the [[ARM/N900/ReleaseProcess|release process]] explained by Carsten.

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/DeveloperEdition/Meetings

2011-04-05T13:01:57Z

Msugano: /* Agenda */

ARM/N900/DeveloperEdition/Meetings

2011-04-05T12:03:15Z

Msugano: /* Archive */

ARM/N900/DeveloperEdition

2011-03-30T08:04:41Z

Msugano:

= MeeGo 1.2 Developer Edition for N900 =

== Target ==

Target is to make a Developer Edition of MeeGo for the Nokia N900 device. Flashed with this edition N900 will be usable as a primary phone device for a developer/hacker person. '''This will not be something for regular end users'''.

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 trunk content. MeeGo features are found in [https://bugs.meego.com/ bugzilla].

You can join the development and discussion at the [http://lists.meego.com/listinfo/meego-handset meego-handset mailing list] and in IRC (#meego-arm @freenode).

== Use cases (do not edit these directly, instead add feedback to the bottom of page) ==

These use cases shall be the prominent ones in the device Home screen. In addition there will be separate folder containing other available Handset apps from repositories, and there is a possibility to promote any app to the main view if the non-functional targets are met.

'''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)

'''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. N900 DE also supports the [[SDK|MeeGo SDK]] for easy development.

== Organization ==

* Core team is being formed in and around Nokia.
* 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/essi Essi Vehmersalo]
*** [[ARM/N900/Browser|Browser and 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], including current [[ARM/N900|N900 HW adaptation team]].
*** Architect: [http://meego.com/users/mythi Mikko Ylinen]
*** Release & integration: [http://meego.com/users/kad Alexander Kanevskiy], [http://meego.com/users/ericlr Eric Le Roux]
** [[ARM/N900/QA|QA]] lead: [http://meego.com/users/jkunnari Jake Kunnari]
** [[ARM/N900/PM|Product management]]: [http://meego.com/users/jukkaeklund Jukka Eklund], [http://meego.com/users/samipienimaki Sami Pienimäki]

* Community involvement is very desirable, and there will lots of areas to contribute.

== Status ==

See the [[ARM/N900/Status|Status]] page for reports.

== Meetings ==

* Work space in IRC (@freenode, #meego-arm) and regular MeeGo mail lists (primarily we will be using [http://lists.meego.com/listinfo/meego-handset meego-handset@meego.com].
* [[ARM/N900/DeveloperEdition/Meetings|Weekly team meetings]] are held in the public IRC. The agenda and the archives are also available. This meeting is registered on the [[MeeGo-Meeting_IRC_Schedule|MeeGo IRC Meeting Page]].

== Installing and running ==

* N900 Handset images: [http://repo.meego.com/MeeGo/builds/trunk/latest/ weekly build], [http://download.meego.com/trunk-daily/builds/trunk/latest/ Trunk-daily], [http://download.meego.com/testing-daily/builds/trunk/latest/ Trunk-Testing]
** See the [[Release Engineering/Repo List|release engineering repository list]] for explanation of different images.
** '''Before installing please read about the recommended method: [[ARM/N900/Install/Dual_Boot|dual boot installation]]'''. That way you can keep Maemo on the device at same time.
* Developer Edition images: Coming soon, see [[ARM/N900/ReleaseProcess]]. PM recommends to try with current [http://qa-reports.meego.com/1.2/Handset/Acceptance/N900 Acceptance images]. Check the test results, and if they look good you can find the image name in the report.
* [[ARM/N900/Install/MMC#Installing_Rootfs_on_external_MMC_card|Flashing instructions]] (when using dual boot method, no need to flash/load the kernel separately).
* Tips and tricks (please add yours here!)
** Connect to WLAN: Settings->Applications->WiFiApplet
* There is also some more [[ARM/N900/CoolStuff|Cool stuff]] to try on top of the MeeGo image.

== 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]] gives the overview on the daily development workflow. Thanks Fathi Boudra & Markus Lehtonen for the contribution. Also any suggestion where to locate the links to this material is appreciated.

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]
* 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 with the Tablet UX on N900. Find more details on [[ARM/N900/TabletUX]].
* Look into learning QML if you haven't already.
* Would like to contribute the test cases? You will find the useful information [[Quality|here]].

== FAQ ==

Q. Let's assume my bug fix was accepted only in the DE, but not in the official 1.2. What do we do with the bug? 
A. Remove the DE_Blocker flag from the official bug. Comment that the fix is available in DE. Try to contribute the fix to 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. This is work in progress. See the [http://wiki.meego.com/ARM/N900/ReleaseProcess release process] explained by Carsten.

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]]