RIL_HEX_TRACE log messges don't map directly to RIL messages
Bug #1331183 reported by
Tony Espy
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ofono (Ubuntu) |
Won't Fix
|
Medium
|
You-Sheng Yang | ||
Bug Description
If the environment variable OFONO_RIL_HEX_TRACE is set and exported before starting ofono on a supported Touch device, the low-level gril code will output log messages with the raw hex of the messages read and written to the rild socket.
Unlike OFONO_RIL_TRACE which causes higher-level tracing output, the hex trace facility doesn't map one to one to actual RIL messages. This is due to the way it hooks into the RIL socket IO. It's possible for RIL messages to be split across multiple log messages, or for a single log message to contain the hex for more than one RIL message.
| Changed in ofono (Ubuntu): | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| Changed in ofono (Ubuntu): | |
| assignee: | nobody → Vicamo Yang (vicamo) |
Revision history for this message
| You-Sheng Yang (vicamo) wrote | #1 |
| Changed in ofono (Ubuntu): | |
| status: | Confirmed → Won't Fix |
To post a comment you must log in.
Proposed pull request https:/