The following links are to WiKi's maintained and hosted by maemo.org The Home of the Maemo Community, where you will find more information on what Maemo software is, how to develop with Maemo, and how to make your development work available to users.
Beginner
Power user
Developer
On maemo.nokia.com you fill find more general information about the N900 mobile computer powered by Maemo.
***
(This a draft message for a locked sticky thread that we may all use for reference. Some text will be replaced with links to additional information as it becomes available.)
The Maemo 5 operation system comes preloaded with a variety of core applications. Beginning with Diablo and continuing with Fremantle (Maemo5) a user can receive "over-the-air" updates to the live system. This over the air "Seamless Software Update" or SSU method also decouples bundled software updates from the major system updates as was required with the previous flash-based software update method. This now allows Nokia the ability to release more frequent updates to individual packages than it had before.
Nokia expects that the open source community will play a large part in the development of applications for Maemo 5.
Maemo uses an on device “Application Manager” that will notify you of updates to installed software and allow you to browse and install new software from pre-loaded and user loaded software catalogues. These catalogues or “repositories” will provide any needed dependant files required by new software or updates.
Now here is the rub…
Only official Nokia or stable repositories from maemo.org should be installed by the average end user. 3rd party repositories and repositories and catalogues with “eval”, “evaluation”, “devel”, or “developer” in their name should be avoided by the average end user as the software they contain may:
- Fill memory because they ignore recommendations for installing big files in the internal memory. (read more)
- Significantly shorten use times because the widgets or apps do not take advantage of proper power management techniques.
These examples are not because of developer malice or ineptitude but may simply be because that is why some of these repositories are made available in the first place… for development. They are not for use by the average end user.
It is easy to get caught up in new user enthusiasm and although the “Application Manager” usually warns the user when new catalogues are being installed, it is easy to click through these warnings or overlook them as yet another long licensing agreement or credits page.
A method to restore to all factory defaults will also be provided in this thread as the information becomes available.
Errors and Omissions: This thread will remain closed so that it can provide this relevant information quickly. I can always be reached by Private Message if corrections or additions are required.![]()





Bookmarks