Samsung galaxy S3 i9305 - reboots every 60s when screen is off

This a follow up of Reboot after installing on my SIII i9305 and as @bernar and @moosfisher described it in the the original post, I’m getting a reboot every 60 seconds when the screen of the phone goes dark. Rendering the install almost unusable (or you have to turn it off everytime you don’t use it).

I haven’t managed to understand if the reinstall Stock then reinstall /e/ had changed anything, but it seemed not so I haven’t gone down that path. On the gitlab I have found issues similar but which talk about different hardware. Is there anything specific to this device in the issue tracker ?

Thanks in advance for anyone’s advice on this. I can help out debugging this issue.

Hi @arthurlutz.

Based on another post of yours, it seemed you did flash the patch before the /e/ build. Is this correct?

I think so, but since I don’t have a SIM for it, I can’t check (or don’t know how to).

Doing a adb logcat shows a great deal of kickstart-qcks messages. Searching on the internet to find what this is, and if it’s “juste” related having adb running at that point…

10-12 10:05:08.443  2080  2080 E kickstart-qcks: Couldn't find "/dev/ttyUSB0", 8 of 10
10-12 10:05:08.943  2080  2080 E kickstart-qcks: Couldn't find "/dev/ttyUSB0", 9 of 10
10-12 10:05:09.444  2080  2080 E kickstart-qcks: Couldn't find "/dev/ttyUSB0", 10 of 10
10-12 10:05:09.944  2080  2080 E kickstart-qcks: '/dev/ttyUSB0' was not found
10-12 10:05:09.945  2080  2080 E kickstart-qcks: 1st enumeration failed
10-12 10:05:09.945  2080  2080 I kickstart-qcks: Trying to bring MDM9K out of reset
10-12 10:05:10.394  2080  2080 I kickstart-qcks: Testing if port "/dev/ttyUSB0" exists
10-12 10:05:10.395  2080  2080 E kickstart-qcks: Couldn't find "/dev/ttyUSB0", 1 of 10
10-12 10:05:10.895  2080  2080 E kickstart-qcks: Couldn't find "/dev/ttyUSB0", 2 of 10
10-12 10:05:11.396  2080  2080 E kickstart-qcks: Couldn't find "/dev/ttyUSB0", 3 of 10
10-12 10:05:11.896  2080  2080 E kickstart-qcks: Couldn't find "/dev/ttyUSB0", 4 of 10
10-12 10:05:12.397  2080  2080 E kickstart-qcks: Couldn't find "/dev/ttyUSB0", 5 of 10
10-12 10:05:12.897  2080  2080 E kickstart-qcks: Couldn't find "/dev/ttyUSB0", 6 of 10
10-12 10:05:13.398  2080  2080 E kickstart-qcks: Couldn't find "/dev/ttyUSB0", 7 of 10
10-12 10:05:13.898  2080  2080 E kickstart-qcks: Couldn't find "/dev/ttyUSB0", 8 of 10
10-12 10:05:14.399  2080  2080 E kickstart-qcks: Couldn't find "/dev/ttyUSB0", 9 of 10
10-12 10:05:14.900  2080  2080 E kickstart-qcks: Couldn't find "/dev/ttyUSB0", 10 of 10
10-12 10:05:15.400  2080  2080 E kickstart-qcks: '/dev/ttyUSB0' was not found
10-12 10:05:15.400  2080  2080 E kickstart-qcks: 1st enumeration failed
10-12 10:05:15.400  2080  2080 I kickstart-qcks: Trying to bring MDM9K out of reset
10-12 10:05:15.895  2080  2080 I kickstart-qcks: Testing if port "/dev/ttyUSB0" exists
10-12 10:05:15.895  2080  2080 E kickstart-qcks: Couldn't find "/dev/ttyUSB0", 1 of 10
10-12 10:05:16.395  2080  2080 E kickstart-qcks: Couldn't find "/dev/ttyUSB0", 2 of 10
10-12 10:05:16.896  2080  2080 E kickstart-qcks: Couldn't find "/dev/ttyUSB0", 3 of 10
10-12 10:05:17.396  2080  2080 E kickstart-qcks: Couldn't find "/dev/ttyUSB0", 4 of 10
10-12 10:05:17.897  2080  2080 E kickstart-qcks: Couldn't find "/dev/ttyUSB0", 5 of 10
10-12 10:05:18.397  2080  2080 E kickstart-qcks: Couldn't find "/dev/ttyUSB0", 6 of 10
10-12 10:05:18.898  2080  2080 E kickstart-qcks: Couldn't find "/dev/ttyUSB0", 7 of 10
10-12 10:05:19.399  2080  2080 E kickstart-qcks: Couldn't find "/dev/ttyUSB0", 8 of 10
10-12 10:05:19.899  2080  2080 E kickstart-qcks: Couldn't find "/dev/ttyUSB0", 9 of 10
10-12 10:05:20.400  2080  2080 E kickstart-qcks: Couldn't find "/dev/ttyUSB0", 10 of 10
10-12 10:05:20.900  2080  2080 E kickstart-qcks: '/dev/ttyUSB0' was not found
10-12 10:05:20.900  2080  2080 E kickstart-qcks: 1st enumeration failed
10-12 10:05:20.900  2080  2080 I kickstart-qcks: Trying to bring MDM9K out of reset
10-12 10:05:21.389  2080  2080 I kickstart-qcks: Testing if port "/dev/ttyUSB0" exists
10-12 10:05:21.389  2080  2080 E kickstart-qcks: Couldn't find "/dev/ttyUSB0", 1 of 10
10-12 10:05:21.890  2080  2080 E kickstart-qcks: Couldn't find "/dev/ttyUSB0", 2 of 10
10-12 10:05:22.390  2080  2080 E kickstart-qcks: Couldn't find "/dev/ttyUSB0", 3 of 10
10-12 10:05:22.891  2080  2080 E kickstart-qcks: Couldn't find "/dev/ttyUSB0", 4 of 10
10-12 10:05:23.392  2080  2080 E kickstart-qcks: Couldn't find "/dev/ttyUSB0", 5 of 10
10-12 10:05:23.892  2080  2080 E kickstart-qcks: Couldn't find "/dev/ttyUSB0", 6 of 10

Got a fix (or a workaround) for uses without a SIM.

adb root
adb shell
mount -o remount,rw /system
mv /system/bin/qcks /system/bin/qcks.disabled
reboot

For anyone curious about what is qcks, I found :

@Danno do you know what the system(sim_support).zip does and any reason why this can’t be patched after ? Or included in the /e/ image ? For now, it fits my use case, but if I want to give/lend this phone to someone with a SIM I might have to come back and fix this properly.

I claimed a fix a bit too quickly. The reboots still happen, but more spaced out, not sure if it’s regular or not, and having an adb logcat seems to put the phone in a situation where the bug doesn’t happen. Not sure how to proceed now… logcat over UDP ? looking into the old logs ? how do I debug from here ?

Honestly, you are quite a more advanced user than I. I had issues with the reboots as well until I flashed the patch and then immediately the /e/os zip. I did not reboot prior to flashing /e/. After this, I no longer had reboot or sim card recognition issues.

I do not know the exact workings of the patch. Another user on /e/'s gitlab described the patch as having fixed their reboot and sim card issues as well.

Dan.

Were you able to get it working?

Blockquote

@Danno yes it seems to be working. It get a some random reboots and from time to time it goes into that loop of rebooting until it drains the battery, not sure what are the conditions that lead it to that…

I’m going to open two other threads about A-GPS not working and battery statitics not being accessible by applications such as AccuBattery.

Mostly usable though.