You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to use QCSuper on a non-rooted Samsung Galaxy A36 (SM-A366E/DS) which features a Qualcomm Snapdragon 6 Gen 3 chipset.
While I can successfully enable Diag Mode and bind the device to the option driver in Linux (detected as 04e8:XXXX), QCSuper is unable to correctly decode LTE RRC and NAS signaling.
Environment:
OS: Linux (Debian/Ubuntu based)
QCSuper Version: Latest from master.
Phone Model: Samsung SM-A366E/DS (Global).
Chipset: Qualcomm Snapdragon 6 Gen 3.
Connection Method: USB Diag Mode (/dev/ttyUSBX forced via new_id).
Symptoms:
Initial attempts with --info often result in DIAG_LOG_CONFIG_F timeouts.
In Wireshark, the captured traffic only shows "Paging" messages on the PCCH channel, but the fields are empty or contain zeros.
GSMTAP headers appear to have incorrect metadata (e.g., Signal Level 0 dB, ARFCN 0, and mapping to SDCCH instead of LTE channels).
Standard LTE RRC/NAS signaling (Attach Request, RRC Connection Setup) is not appearing even after toggling Airplane Mode.
Request:
It seems that the log packet format for this newer chipset (Snapdragon 6 Gen 3) or the Samsung-specific encapsulation for this model is not yet supported or correctly dissected by QCSuper. Is there a specific log mask or a manual update needed to support this newer hardware?
I am trying to use QCSuper on a non-rooted Samsung Galaxy A36 (SM-A366E/DS) which features a Qualcomm Snapdragon 6 Gen 3 chipset.
While I can successfully enable Diag Mode and bind the device to the option driver in Linux (detected as 04e8:XXXX), QCSuper is unable to correctly decode LTE RRC and NAS signaling.
Environment:
OS: Linux (Debian/Ubuntu based)
QCSuper Version: Latest from master.
Phone Model: Samsung SM-A366E/DS (Global).
Chipset: Qualcomm Snapdragon 6 Gen 3.
Connection Method: USB Diag Mode (/dev/ttyUSBX forced via new_id).
Symptoms:
Initial attempts with --info often result in DIAG_LOG_CONFIG_F timeouts.
In Wireshark, the captured traffic only shows "Paging" messages on the PCCH channel, but the fields are empty or contain zeros.
GSMTAP headers appear to have incorrect metadata (e.g., Signal Level 0 dB, ARFCN 0, and mapping to SDCCH instead of LTE channels).
Standard LTE RRC/NAS signaling (Attach Request, RRC Connection Setup) is not appearing even after toggling Airplane Mode.
Request:
It seems that the log packet format for this newer chipset (Snapdragon 6 Gen 3) or the Samsung-specific encapsulation for this model is not yet supported or correctly dissected by QCSuper. Is there a specific log mask or a manual update needed to support this newer hardware?