> For the complete documentation index, see [llms.txt](https://docs.spectralink.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spectralink.net/amie-advanced/using-the-platform/device-details/device-session-activity.md). # Session Activity **Session Activity** is the first of the five sections beneath a device's details: a timeline of what the device, its battery and its network connection did over the seven days leading up to its last check-in. Every row is drawn against the same time axis, so events can be lined up against each other. To reach it, open a device from the Devices [Inventory](/amie-advanced/using-the-platform/devices-inventory.md) tab and scroll down. ## Why this screen matters When someone says "the phone was misbehaving at about ten o'clock", **Session Activity** shows what the charge, the network, the temperature and the apps were doing at ten o'clock. It puts a device's calls, charging, network reports and battery swaps on one clock. Use it to answer whether a dropped call coincided with a change of access point, whether a battery that went flat was ever charged, and whether the handset was hot or heavily loaded at the time. ## Before you start **Session Activity** covers the seven days ending at the device's last check-in, not the last seven days on the calendar. A device last seen a month ago shows the week before it went quiet. Read the **Last Seen** date at the top of the page before reading a time off the axis. It shows data for the device whose page you are on; the [group selector](/amie-advanced/using-the-platform/the-console.md#the-group-selector) in the header has no effect on it. ## Screen layout ![Session Activity for one handset: a week of calls, charge, temperature and network on one time axis.](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-a839f97c50c428906c2c50121d77d5a13ab91f83%2Fdevice-session-activity.png?alt=media) ### Heading **Session Activity** with a wave icon and a **?**. At the right of the heading, the hint **Ctrl/⌘+scroll to zoom, drag to pan** and, once you have zoomed or panned, a **Reset zoom** link. ### The rows Sixteen rows in three groups, each with a label on the left and a horizontal strip — the track — on the right where its marks are drawn. Faint vertical lines mark each midnight, in your browser's time zone, across every track. A row's marks are drawn in one of four ways: * Bars — a bar for each period during which the row's condition held (a call, a charge). * Ticks — a thin vertical line for each moment something happened (a button press). * A line — a value plotted over time (**Charge %** only). * Blocks — full-height shaded blocks labeled with a value, alternating shade at each change (**Serial** only). | Group | Row | Drawn as | What it shows | | ----------------- | --------------------- | ---------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **User Activity** | **Panic button** | Ticks, red | A tick at each report that the handset's emergency button had been pressed | | | **In call** | Bars | Each scored call, from its start to its end — the calls that carry a **Quality (MOS)** value under [Call History](/amie-advanced/using-the-platform/device-details/device-call-history.md) | | | **In use** | Bars | Each stretch during which the handset's reports flagged it as being handled and operated — from the first report so flagged to the first that was not | | | **Barcode scan** | Bars | Each stretch during which the barcode scanner was decoding a code — from the first report of decoding to the first report of the scanner idle | | | **Message received** | Ticks | A tick at each report carrying a message the handset had received | | | **Top app** | Ticks | Each report of which apps were consuming battery, including reports that listed none | | **Battery** | **Charge %** | Line | The battery's charge level, 0 to 100%, with **100**, **75**, **50** and **25** marked at the right edge. The first and last readings of the week are plotted, plus every reading where the level changed. With fewer than two readings the track is empty | | | **Temperature** | Bars | One bar for each change in temperature. Each bar ends at the reading that recorded a new value and carries that value; its length is the time since the previous different reading, not how long the new temperature then held. A temperature that never changed during the week draws no bar | | | **Hot swap** | Ticks, red | Each report that the main battery was absent — a battery being swapped | | | **Serial** | Blocks | Which battery was fitted, labeled with its serial number; a new block begins when a different battery is reported | | **System** | **Network Connected** | Bars | Each network report, running from the previous report to this one. A long bar can mean a long-lived connection or a long gap between reports; the same is true of **Temperature**, **CPU load** and **Memory usage** | | | **CPU load** | Bars | Processor load: one bar for each reading where either the CPU or the memory figure changed, running from the previous such reading to this one and carrying this reading's value | | | **Memory usage** | Bars | Memory in use, drawn the same way as **CPU load** | | | **Powered on** | — | Always empty. The device does not yet report whether it is powered on | | | **Charging** | Bars | Each charging period, from the first **Charging** or **Fully charged** report to the next **Discharging** report | | | **Docked** | Bars | Each period the device reported being in its dock | Bars and ticks are drawn in blue, except **Panic button** and **Hot swap**, which are red and whose labels are red. A row with nothing to show in the week is present with an empty track. {% hint style="info" %} Not yet available: the \*\*Powered on\*\* row. It is always empty. \[GAP-device-1] {% endhint %} When the device reported nothing in the seven days before its last check-in, or has never checked in, the whole section reads **No activity data for this device.** ### The time axis Beneath the rows, nine evenly spaced labels showing the date and time — for example **Sep 14, 9:00 AM** — across whatever span is currently in view. ## Controls | Control | What it does | | --------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Ctrl + scroll (Windows) or ⌘ + scroll (Mac) over the rows | Zooms in or out, centered on the pointer. You can zoom in to a span of one minute and out to the full span of the data — up to seven days. Scrolling without the key scrolls the page as usual | | Click and drag over the rows | Pans the view earlier or later, within the week | | **Reset zoom** | Returns to the full span of the data. Appears only while you are zoomed or panned | | Hover over a bar, tick or block | Shows a pop-up for that mark — see [What the pop-ups show](#what-the-pop-ups-show). Ticks that would draw on top of each other at the current zoom are merged into one mark. Whether or not marks are merged, the pop-up covers every mark under the pointer and says **N occurrences**; zoom in to separate them. A pop-up covering a single moment shows one time rather than a range | | Hover over the **Charge %** line | Shows a dashed crosshair at the nearest reading, with its date and time, the charge percentage, and an estimate of the same charge in milliamp hours (mAh) out of an estimated full-charge capacity | The view returns to the full span whenever the data reloads — when you open a different device, for example. ### What the pop-ups show Every pop-up in the table below begins with a heading — the row's name unless the table says otherwise — and the date and time, to the second, of the first and last mark it covers. | Row | Also shows | | ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Panic button**, **Message received**, **Hot swap** | **N occurrences** | | **In call**, **Barcode scan**, **Docked** | **active duration:** the total time covered by the bars, then **N occurrences** | | **In use** | **N occurrences** | | **Top app** | A table of **Package**, **Consumption** and **Time**: every app reported up to that point in the week, its most recent consumption figure (a share of a full charge, shown as a bare number without a percent sign), and when that figure was reported | | **Temperature** | **active duration:** and **N occurrences**, then a table with one row per distinct temperature — in °C and °F — with **Number of times** it was reported and **Total duration** it held | | **Network Connected** | **active duration:**, **N occurrences**, then a table of **BSSID**, **SSID**, **Band**, **Channel** and **Time** for each report — the access point's hardware address, the network name, the radio band and channel | | **CPU load**, **Memory usage** | **active duration:**, **N occurrences**, then a table of the reading (as a percentage) and its **Time** | | **Charging** | Headed **Charging state**: **active duration:**, **N occurrences**, then a table of **Charge Type**, **Start** and **End** for each charging period | | **Serial** | Headed **Serial:** and the battery serial, then **duration:** — how long that battery was fitted | {% hint style="warning" %} Review: the **Charge Type** column reads **is\_usb\_powered** or **is\_ac\_powered** — an internal value, not a label. The product specification is a readable label such as USB or AC. \[REVIEW-device-1] {% endhint %} ## Icons and indicators | Icon or indicator | Meaning | When it appears | | ------------------------------------------------------ | --------------------------------------------------------------------------- | ------------------------------------ | | Wave icon before the heading | Marks the section | Always | | **?** beside the heading | Hover over it for a short description of the section | Always | | Red row label and red marks | **Panic button** and **Hot swap**, the two rows that usually need attention | Always | | Faint vertical lines across the tracks | Midnight, in your browser's time zone | One per day in view | | **100 / 75 / 50 / 25** at the right of **Charge %** | The line's scale; 0 is the bottom edge | Whenever the line is drawn | | Alternating light and darker blue blocks on **Serial** | Successive batteries; the shade changes at each swap | Whenever a battery has been reported | | Grab-hand pointer over the rows | The view can be dragged | Always, once data is shown | | Dashed vertical line on **Charge %** | The reading nearest your pointer | While hovering the line | | Spinning icon in place of the rows | The data has not loaded yet | While loading | ## What to look for * A red tick on **Panic button**. Someone pressed the handset's emergency button at that moment. Hover to read the exact time, and line it up with **In call** and **Network Connected** to see what the phone was doing. * **Charge %** falling steeply while **In call** and **In use** are quiet. Something is draining the battery while the phone is idle. Hover over the **Top app** ticks in that stretch to see which apps were consuming, or open [Top App Consumption](/amie-advanced/using-the-platform/device-details/device-top-app-consumption.md). * **Charge %** never climbing back to 100 and no bars on **Charging**. The phone is not being charged between shifts. Check **Docked** for whether it is ever placed in its dock. * Frequent red ticks on **Hot swap**. The battery is being swapped often. **Serial** shows which batteries were fitted; open each on [Battery details](/amie-advanced/using-the-platform/battery-details.md) to compare their health. * A new bar beginning on **Network Connected** at the moment a call on **In call** ended. Hover over the bars either side to compare **BSSID** and **SSID**; if they differ, the handset moved between access points during the call. [Performance](/amie-advanced/using-the-platform/performance.md) shows whether that access point is a problem for other handsets too. * **Temperature** bars carrying higher values than the rest of the week while **Charging** is active. The phone is running hot on charge; check where it is charged. * A bar that reaches the right-hand edge. That condition — a charge, a docked period, a stretch in use — was still in progress at the device's last check-in. * **In call** and **In use** that do not line up. **In call** comes from the calls AMIE scored — the ones with a **Quality (MOS)** value under [Call History](/amie-advanced/using-the-platform/device-details/device-call-history.md) — and **In use** from the device's own reports; a device can be in a call without reporting itself in use. ## Metrics on this screen * [Time and time zones](/amie-advanced/metrics-reference/time-and-time-zones.md) — the seven days are a rolling window ending at the device's last check-in; the axis labels, midnight lines and pop-ups are in your browser's time zone, so a colleague elsewhere sees different clock times * [Battery Health Distribution](/amie-advanced/metrics-reference/battery-health-distribution.md) — charge versus health ## Related * [Device details](/amie-advanced/using-the-platform/device-details.md) — the details above this section * [Top App Consumption](/amie-advanced/using-the-platform/device-details/device-top-app-consumption.md) — the same app reports, grouped into stretches of activity * [Call History](/amie-advanced/using-the-platform/device-details/device-call-history.md) — the calls behind the **In call** row * [Battery details](/amie-advanced/using-the-platform/battery-details.md) — the battery behind the **Charge %** and **Serial** rows --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.spectralink.net/amie-advanced/using-the-platform/device-details/device-session-activity.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.