Issue #1197


Cellular connection stops and wants PIN code again

Added by Flo Debian over 9 years ago. Updated almost 5 years ago.

Telephony and mobile data
Target version:
Start date:
Due date:
% Done:


Estimated time:
Galaxy S 2 (I9100)
Type of work:


Similar to issue 1173.

At some point the connection is lost and I am asked to enter the PIN Code. This happens once in something like three days.

Before entering the PIN I executed the following commands:

adb logcat -b main > crash-main_s2.txt
adb logcat -b radio > crash-radio_s2.txt

The device is running 4.2 0003


crash-radio_s2.txt (900 KB) crash-radio_s2.txt Flo Debian, 01/25/2015 06:13 PM
crash-main_s2.txt (402 KB) crash-main_s2.txt Flo Debian, 01/25/2015 06:13 PM
dmesg_s2.txt (1.01 MB) dmesg_s2.txt Flo Debian, 01/29/2015 03:28 PM
Actions #1

Updated by Paul Kocialkowski over 9 years ago

Remember that the symptoms are the same, but the issue is actually quite different. In that case, we can see:

E/RIL-IPC ( 1849): Polling IPC FMT client failed

Which indicates a modem-side problem. Running adb shell dmesg should provide kernel logs that reflect this situation. Feel free to grab some next time it happens and attach them here to confirm.
Ideally, Samsung-RIL should re-enter the PIN automatically so that this is transparent to the user, just like it is with the proprietary RIL (where those failures happen as well). In the meantime, you can simply disable the PIN code and it will get service back automatically.

In addition to that, Samsung-RIL does crash when flushing data, so this should be fixed. Perhaps a close/open cycle would have been enough to recovery from the issue. With the crash, a cold boot is triggered, leaving no chance of soft recovery.

Actions #2

Updated by Flo Debian over 9 years ago

Here is

adb shell dmesg > dmesg_s2.txt

from the last crash.

Thank you for your help.

Actions #3

Updated by Denis 'GNUtoo' Carikli over 8 years ago

  • Category changed from 81 to Telephony and mobile data
  • Device Galaxy S 2 (I9100) added
Actions #4

Updated by Kurtis Hanna almost 5 years ago

  • Resolution set to wontfix

This issue has been closed because Replicant 4.2 is no longer supported or maintained.

Actions #5

Updated by Kurtis Hanna almost 5 years ago

  • Status changed from New to Closed

Also available in: Atom PDF