Our group does not have access to the manufacturer's source code files, so we cannot offer any additional information. In most cases, this information is proprietary and of no real use to anyone else but the handset manufacturer's development teams.
To find the definitions of any particular debug message that is generated from a commercial phone that uses the QUALCOMM chips, we have to refer to the handset manufacturer who modifies the debug messages according to their development needs. They are used for development purposes only, and will never be documented beyond the source code. The list of potential debug messages is very extensive, and are constantly changing from build to build.
#Saving a logmask in qxdm software
The messages are used as a diagnostic aid to provide handset software developers with some insight into the behavior of the handset software program. Most of the debug messages are inherited from the ASIC code that QUALCOMM provides to the handset manufactuer, while others are introduced by the handset manufacturer as they develop their product. The debug messages consist of fixed text that is determined at compile time by the handset manufacturer. Event Reports are not ASCII text strings like Debug Messages. Event Reports need a database update, as the Event ID and payload needs to be parsed for the Event Report to have meaning. All such devices provide the debug text across the same transport described above, without the need to QXDM at all. QXDM does not need to be enhanced or changed to support debug messages for technologies in development. The software in the test handset provides debug messages to QXDM as part of the MESSAGE RESPONSE MESSAGE (A Diagnostic command response), CMD_CODE(31), and Event Reports as part of the EVENT REPORT MESSAGE (CMD_CODE 96). QXDM only logs or displays the messages as they are provided by the mobile.
QXDM does not generate the messages that are displayed on the Messages view, which is why they are not documented in the QXDM user guide. The events are not implementation-specific or internal strings like debug messages, but are typically indicators of common, industry standard terms that are easier to understand and follow when compared to debug messages. There are no QXDM user guides or addendums that define frequently used debug messages.Įvent Reports are a debugging mechanism that summarizes activity by the software. They are not documented beyond the source code itself. These messages are not specific to QXDM, are used primarily by QUALCOMM for developing ASIC software, change frequently, and are not documented.ĭebug Messages (labeled as Message Packets in QXDM) are software-specific printf strings created by the AMSS developer to help debug the AMSS itself. (it can also be configured to display log packets and strings). The Messages view displays debug and event messages received by the mobile. HOW DO I OBTAIN THE DEFINITIONS OF EACH DEBUG OR EVENT MESSAGE?