skyhawk10x
Lurker
Hello,
I have a Samsung Galaxy S2 GT-i9100 phone. It's rooted with the stock Android 4.0.4 ROM installed. I'm facing the following issue:
My phone works perfectly but every one day and a half it loses its connection. The problem is only solved after a reboot. This is very annoying, so I started looking for a solution. I have tried this so far:
- Factory reset
- Trying to identify possible apps that might cause it by examining the log files
- Installing other modems
- Installing other RIL and modem combinations
Recently I narrowed the problem down a bit further:
The problem is solved when I use the NELP3 modem-RIL combination. But with that combination I never get on a H+ connection. When I install other combinations, my phone does connect on H+ but then the problem is there again: it works fine for about one day and then loses connection until reboot.
I examined the radio-log and noticed the following difference between NELP3 modem-RIL and other combinations:
NELP3 gives following "error" (log verbosity set to error level) very frequently, but nothing more than that:
E/RIL (1817)
+handle_modemctl_event
Other modem RIL combinations produce additional error:
(15588)ReaderLoop after select
(15588)ReaderLoop after FD_ISSET
I believe this eventually builds up until I eventually see the following:
02-25 09:59:45.850 D/RIL (5820)Send PSI Header indicate(30), length(f000), dummy(ff)
02-25 09:59:45.850 D/RIL (5820)4 bytes send done
02-25 09:59:45.850 D/RIL (5820)Send PSI data
02-25 09:59:45.890 E/RIL (5820)Write failed: -1, Out of memory
02-25 09:59:45.890 D/RIL (5820)boot: hsic_xmit_psi() failed
02-25 09:59:45.890 D/RIL (5820)xmm6260_boot_hsic start ..
02-25 09:59:45.890 E/RIL (5820)ehci sysfs open fail=-1(/sys/devices/platform/s5p-ohci/ohci_power)
02-25 09:59:46.665 D/RIL (5820)boot : check link connected
02-25 09:59:47.165 D/RIL (5820)boot : check link connected
02-25 09:59:47.215 D/RIL (5820)Send AT
02-25 09:59:47.215 D/RIL (5820)4 bytes send
02-25 09:59:47.215 D/RIL (5820)Read ack of AT
02-25 09:59:47.215 D/RIL (5820)ack read done: 0xf0
02-25 09:59:47.215 D/RIL (5820)
02-25 09:59:47.215 D/RIL (5820)Chip specific ID :0x16
02-25 09:59:47.220 D/RIL (5820)Prepare image from /dev/block/mmcblk0p8
02-25 09:59:47.225 D/RIL (5820)Loaded image Size: 0xf000
02-25 09:59:47.225 D/RIL (5820)Loaded image like below:
...
2-25 09:59:51.430 I/RILS (5189)Connected to '7777' socket
02-25 09:59:53.015 E/RIL (5820)open_new_interface: failed to open /dev/umts_ipc0. No such device.
02-25 09:59:53.015 E/RIL (5820)count : 2
02-25 09:59:55.020 E/RIL (5820)open_new_interface: failed to open /dev/umts_ipc0. No such device.
02-25 09:59:55.020 E/RIL (5820)count : 3
02-25 09:59:55.420 I/RILJ (29129)Couldn't find 'rild' socket; retrying after timeout
02-25 09:59:57.020 E/RIL (5820)open_new_interface: failed to open /dev/umts_ipc0. No such device.
At that point I see the "no signal" sign where normally my connection bar should be. The errors in the log keep repeating until I reboot. Then the "Readerloop" shows up again and after about one day I get the problem above again.
My questions:
- Does anyone know what could cause this issue?
- Does anyone know how to get the H+ connections without going into the ReaderLoop and eventually losing connection up until a reboot?
Thanks in advance!
I have a Samsung Galaxy S2 GT-i9100 phone. It's rooted with the stock Android 4.0.4 ROM installed. I'm facing the following issue:
My phone works perfectly but every one day and a half it loses its connection. The problem is only solved after a reboot. This is very annoying, so I started looking for a solution. I have tried this so far:
- Factory reset
- Trying to identify possible apps that might cause it by examining the log files
- Installing other modems
- Installing other RIL and modem combinations
Recently I narrowed the problem down a bit further:
The problem is solved when I use the NELP3 modem-RIL combination. But with that combination I never get on a H+ connection. When I install other combinations, my phone does connect on H+ but then the problem is there again: it works fine for about one day and then loses connection until reboot.
I examined the radio-log and noticed the following difference between NELP3 modem-RIL and other combinations:
NELP3 gives following "error" (log verbosity set to error level) very frequently, but nothing more than that:
E/RIL (1817)
+handle_modemctl_event
Other modem RIL combinations produce additional error:
(15588)ReaderLoop after select
(15588)ReaderLoop after FD_ISSET
I believe this eventually builds up until I eventually see the following:
02-25 09:59:45.850 D/RIL (5820)Send PSI Header indicate(30), length(f000), dummy(ff)
02-25 09:59:45.850 D/RIL (5820)4 bytes send done
02-25 09:59:45.850 D/RIL (5820)Send PSI data
02-25 09:59:45.890 E/RIL (5820)Write failed: -1, Out of memory
02-25 09:59:45.890 D/RIL (5820)boot: hsic_xmit_psi() failed
02-25 09:59:45.890 D/RIL (5820)xmm6260_boot_hsic start ..
02-25 09:59:45.890 E/RIL (5820)ehci sysfs open fail=-1(/sys/devices/platform/s5p-ohci/ohci_power)
02-25 09:59:46.665 D/RIL (5820)boot : check link connected
02-25 09:59:47.165 D/RIL (5820)boot : check link connected
02-25 09:59:47.215 D/RIL (5820)Send AT
02-25 09:59:47.215 D/RIL (5820)4 bytes send
02-25 09:59:47.215 D/RIL (5820)Read ack of AT
02-25 09:59:47.215 D/RIL (5820)ack read done: 0xf0
02-25 09:59:47.215 D/RIL (5820)
02-25 09:59:47.215 D/RIL (5820)Chip specific ID :0x16
02-25 09:59:47.220 D/RIL (5820)Prepare image from /dev/block/mmcblk0p8
02-25 09:59:47.225 D/RIL (5820)Loaded image Size: 0xf000
02-25 09:59:47.225 D/RIL (5820)Loaded image like below:
...
2-25 09:59:51.430 I/RILS (5189)Connected to '7777' socket
02-25 09:59:53.015 E/RIL (5820)open_new_interface: failed to open /dev/umts_ipc0. No such device.
02-25 09:59:53.015 E/RIL (5820)count : 2
02-25 09:59:55.020 E/RIL (5820)open_new_interface: failed to open /dev/umts_ipc0. No such device.
02-25 09:59:55.020 E/RIL (5820)count : 3
02-25 09:59:55.420 I/RILJ (29129)Couldn't find 'rild' socket; retrying after timeout
02-25 09:59:57.020 E/RIL (5820)open_new_interface: failed to open /dev/umts_ipc0. No such device.
At that point I see the "no signal" sign where normally my connection bar should be. The errors in the log keep repeating until I reboot. Then the "Readerloop" shows up again and after about one day I get the problem above again.
My questions:
- Does anyone know what could cause this issue?
- Does anyone know how to get the H+ connections without going into the ReaderLoop and eventually losing connection up until a reboot?
Thanks in advance!
