Replicant

Sadly, it looks like the modem crashing, which happens, even with the proprietary RIL. The way they work around it is by storing the PIN somewhat encrypted and unlocking the SIM after it reboots, so that it's almost transparent to the user.

That's really a problem from the modem side, nothing we can do about it except handle the crash better. If it comes back to the PIN dialog, it already means that recovery from the crash worked, which is already something!

I will look into storing the PIN in a similar fashion so that it becomes more transparent and doesn't make you miss calls or messages.

Please tell me which log and at which time I should provide.

The best thing to do is to not enter your PIN, connect the device to a computer and grab logs. This way you can make sure that the crash is there. Please include both the radio and main buffers.

That was I can confirm this is what I'm talking about, but there is no real fix for that behaviour.

Thank you for looking into it.

It happenend that I got an S2 as a friend changed to an S5.
The S2 seems to be more stable (it only happened two times the last 5 days). So for me it's not that urgent anymore. I steped back to 4.2 0002 which doesn't have that issue and is good enough as backup device.

Nevertheless I will provide the log files. Since I am out of town for a couple of days more I can't do that before end of next week.

Regards.

The Galaxy S 2 (I9100) should indeed be more stable on this regard.

I steped back to 4.2 0002 which doesn't have that issue and is good enough as backup device.

That's very odd, there should be no regression between 4.2 0002 and 4.2 0003 (well, as you know, I still can make mistakes). If it worked better with 0002, then it may not be modem-related, in which case the logs will be even more important.

Right now my S2 showed the same problem as well, for the third time. This happens much less frequent than with the S. Unfortunately the permissions were not set correctly for debugging and I couldn't read the logs. I will do this next time (if a computer is available).

This looks like an actual issue on our software implementation side, I will have to take a deeper look into it.

This is probably not the same problem on the other device, feel free to open a new ticket with logs from the S2!