This widget could not be displayed.
This widget could not be displayed.
cancel
Showing results for 
Search instead for 
Did you mean: 

Bugs on RoG2 17.0240.2007.27

Please tell us some basic information before asking for help:
Model Name: ZS660KL WW
Firmware Version: 17.0240.2007.27
Rooted or not: yes
Frequency of Occurrence: continuous
APP Name & APP Version (If your issue relates to the app): com. 1.15.2.4
In addition to information above, please also provide as much details as you can, e.g., using scenario, what troubleshooting you've already done, screenshot, etc.
========================================
When trying to sign in to the My HEB app, the login fails (attestation error), with the following trace in logcat:
08-11 20:20:14.308  1243  1243 I keystore: del USRPKEY_unstable.c7202ece89390c490b1b94d5b71225e1.-1090556640775919093 10161
08-11 20:20:14.308  1243  1243 I keystore: del USRSKEY_unstable.c7202ece89390c490b1b94d5b71225e1.-1090556640775919093 10161
08-11 20:20:14.309  1243  1243 I keystore: del USRCERT_unstable.c7202ece89390c490b1b94d5b71225e1.-1090556640775919093 10161
08-11 20:20:14.309  1243  1243 I keystore: del CACERT_unstable.c7202ece89390c490b1b94d5b71225e1.-1090556640775919093 10161
08-11 20:20:14.311   614   621 D DrmLibTime: got the req here! ret=0
08-11 20:20:14.312   614   621 D DrmLibTime: command id, time_cmd_id = 770
08-11 20:20:14.312   614   621 D DrmLibTime: time_getutcsec starts!
08-11 20:20:14.312   614   621 D DrmLibTime: QSEE Time Listener: time_getutcsec
08-11 20:20:14.312   614   621 D DrmLibTime: QSEE Time Listener: get_utc_seconds
08-11 20:20:14.312   614   621 D DrmLibTime: QSEE Time Listener: time_get_modem_time
08-11 20:20:14.312   614   621 D DrmLibTime: QSEE Time Listener: Checking if ATS_MODEM is set or not.
08-11 20:20:14.312   614   621 D QC-time-services: Lib:time_genoff_operation: pargs->base = 13
08-11 20:20:14.312   614   621 D QC-time-services: Lib:time_genoff_operation: pargs->operation = 2
08-11 20:20:14.312   614   621 D QC-time-services: Lib:time_genoff_operation: pargs->ts_val = 0
08-11 20:20:14.315   811   954 D QC-time-services: Daemon: Connection accepted:time_genoff
08-11 20:20:14.316   614   621 D QC-time-services: Lib:time_genoff_operation: Send to server  passed!!
08-11 20:20:14.317   811 29561 D QC-time-services: Daemon:Received base = 13, unit = 1, operation = 2,value = 0
08-11 20:20:14.317   811 29561 D QC-time-services: Daemon:genoff_opr: Base = 13, val = 0, operation = 2
08-11 20:20:14.317   811 29561 D QC-time-services: offset is: 1 for base: 13
08-11 20:20:14.317   614   621 E QC-time-services: Receive Passed == base = 13, unit = 1, operation = 2, result = 0
08-11 20:20:14.317   614   621 D DrmLibTime: QSEE Time Listener: ATS_MODEM is set. Try to retrieve it.
08-11 20:20:14.317   811   954 E QC-time-services: Daemon: Time-services: Waiting to acceptconnection
08-11 20:20:14.317   811   954 D QC-time-services: Daemon: Connection accepted:time_genoff
08-11 20:20:14.318   811 29562 D QC-time-services: Daemon:Received base = 13, unit = 1, operation = 1,value = 0
08-11 20:20:14.318   811 29562 D QC-time-services: Daemon:genoff_opr: Base = 13, val = 0, operation = 1
08-11 20:20:14.318   811 29562 D QC-time-services: Daemon: genoff get for 13
08-11 20:20:14.318   811 29562 D QC-time-services: Daemon:Value read from QTimer mseconds = 54229727
08-11 20:20:14.318   811 29562 D QC-time-services: Daemon:Value read from RTC mseconds on boot = 322033000
08-11 20:20:14.318   811 29562 D QC-time-services: Daemon:Value read from QTimer mseconds = 54229727
08-11 20:20:14.318   811 29562 D QC-time-services: Daemon:Value read from generic offset = 1596818970385
08-11 20:20:14.318   811 29562 D QC-time-services: Daemon:Delta read on boot mseconds = 322014538
08-11 20:20:14.318   811 29562 D QC-time-services: Daemon:Final Time = 1597195214650
08-11 20:20:14.318   614   621 D DrmLibTime: QSEE Time Listener: Time GenOff - seconds: 1597195214
08-11 20:20:14.318   614   621 D DrmLibTime: time_getutcsec returns 0, sec = 1597195214; nsec = 0
08-11 20:20:14.318   614   621 D DrmLibTime: time_getutcsec finished!
08-11 20:20:14.319   614   621 D DrmLibTime: iotcl_continue_command finished! and return 0
08-11 20:20:14.319   614   621 D DrmLibTime: before calling ioctl to read the next time_cmd
08-11 20:20:14.319   811   954 E QC-time-services: Daemon: Time-services: Waiting to acceptconnection
08-11 20:20:14.338  1243 29560 D DropBoxManager: About to call service->add()
08-11 20:20:14.339  3304  5017 I DropBoxManagerService: add tag=keymaster isTagEnabled=true flags=0x0
08-11 20:20:14.347  1243 29560 D DropBoxManager: service->add returned No error
08-11 20:20:14.376   613   613 E KeyMasterHalDevice: Attest key send cmd failed
08-11 20:20:14.377   613   613 E KeyMasterHalDevice: ret: 0
08-11 20:20:14.377   613   613 E KeyMasterHalDevice: resp->status: -10003
08-11 20:20:14.377  1243 29565 E /system/bin/keystore: Keymaster reported error: -10003
08-11 20:20:14.377  1243 29565 E /system/bin/keystore: NOTE: This is an error in the vendor specific error range.
08-11 20:20:14.377  1243 29565 E /system/bin/keystore:       Refer to the vendor of the implementation for details.
08-11 20:20:14.377  1243 29565 E /system/bin/keystore:       Implementation name: Keymaster HAL: 4
08-11 20:20:14.377  1243 29565 E /system/bin/keystore:       Vendor name:         QTI
08-11 20:20:14.377  1243 29565 E /system/bin/keystore:       MajorVersion:        
08-11 20:20:14.379  1243  1243 I keystore: del USRPKEY_unstable.c7202ece89390c490b1b94d5b71225e1.-1090556640775919093 10161
08-11 20:20:14.380  1243  1243 I keystore: del USRCERT_unstable.c7202ece89390c490b1b94d5b71225e1.-1090556640775919093 10161
08-11 20:20:14.381  1243  1243 I keystore: del CACERT_unstable.c7202ece89390c490b1b94d5b71225e1.-1090556640775919093 10161
This doesn't seem like an app bug because of the Keymaster error (I can use the app fine on another phone), but I don't have access to the Qualcomm docs to see what -10003 means.
Another issue I've been having is a hard device reboot crash when using Discord (v34.6) to watch streams in a channel. Voice calls by themselves have no issues, and I haven't tried video calls. I'm not able to capture anything relevant in logcat at the time of the crash. Happens with or without Krisp noise suppression enabled, and with or without hardware scaling enabled.
Is anyone else able to reproduce either of these issues?
1 REPLY 1

I've found a workaround for the HEB app bug, but the crashes using Discord are still preventing me from watching streams. I can reproduce it reliably when streaming from an alt account in a channel with no other users, and even when the audio on both ends is muted. Changing the display settings on the phone (like the refresh rate) to conservative defaults doesn't seem to affect it. Attached is a logcat starting from just before joining a stream, and ending when the phone freezes and reboots. Please let me know what else I can supply to help track this issue down.