OpenWiki

Palm Internals

Edit this page (last edited July 26, 2005)
Palm Notes | Recent Changes | Title Index | User Preferences | Random Page | Help
  • Introduction
  • Alarm list
  • Notification list
  • Introduction

    Palm Internals utility was written to discover Palm OS internal information like alarm list, notification list etc.

    Alarm list

    Alarm list is the first screen you see on Palm Internals start. You can refresh it with screen button "Alarm".

    Palm OS application can activate only one alarm. At alarm time Palm OS calls application. If application (like DateBook?) want to manage multiple alarms, it can do it with internal alarm queue and adding the earliest event to Palm OS alarm list. So there are no way to check internal queues, you can explore only one alarm per application. Alarm list cleared at each reset, so the applications add own alarm to list on reset. There are no reason to remove alarms manually: applications re-insert it at reset.

    There are three kinds of alarms: sublaunch alarm, arm procedure alarm and m68k procedure alarm. Sublaunch alarm is the most common kind of alarm. Palm OS launches application with special command code. Procedure alarm is a light kind of alarm. Procedure alarm activation doesn't wake up screen and executes 100 times faster than sublaunch one. Procedure alarms require more programmers efforts and used for fast system tricks. arm and m68k points to processor type: arm alarm executes by native arm app and m68k alarm executes in user app, written for motorla 68000 processor. 90% of applications for Palm OS are written as m68k apps, arm apps usually are system applications.

    How to read alarm list entries:

    Notification list

    Notification is a system mechanism to broadcast information. Each application (and Palm OS itself) can broadcast notifications and can be a notification subscriber. You can list notification subscribers with "Notif." button. Notifications are marked with four-letter code.

    This list can be useful in resolving system conflicts. Notifications are handled in background, independently to current application. So when your device crashes on power off or after hotsync, you can detect buggy app by checking notification subscribers for known code.

    Check the list of common notification codes:

    How to read notification entry
    ---hapl---
    * 45 'Uninstall Manager'
    * 46 'SdioSpiOmap' arm 402FFC37
    

    Palm Notes | Recent Changes | Title Index | User Preferences | Random Page | Help
    Edit this page
    Print this page | View XML
    Find page by browsing, searching or an index
    Edited July 26, 2005 (diff)
    Valid XHTML 1.0!Valid CSS!