[Galaxy S II General] ph3n0mII:
It's been discussed here a few times recently, and for me the problem predates the openRIL by several months and started occurring on some of the early CM10 builds (XXLQ6 was the newest modem out at the time, if my memory serves me correctly), but me and another victim of this problem have been using DorimanX kernel lately which seems to almost entirely fix this particular RIL crash + logs issue, and now we only get the signal drop + RIL crash logs about once per fortnight instead of multiple times daily, so theres definitely something there..

I've tried switching back to stock cm10.1 a few times in between by doing full wipe+reinstall just to test, and sure enough, within a few hours at most, I start getting entire network dropouts at least every 3 hours, no matter which combination of modem, sim card, telephone network, ROM, or APN settings I try, so keep in mind this is NOT just a cm10.1 specific issue and we should be careful not to pressure CM10.1 devs about it (well ok, maybe a little bit :p).

People have mentioned several things to try on here, with me and a few others with the same problem having collectively tried them all and several more, and every combination of each, and nothing makes it better OR worse mind you.

Once again, it even happens on stock Samsung Jellybean ROMs, but it seems any ROM + DorimanX 8.14/9.14 or higher seems to make it near-perfect.

So, based on all this information, with long and extensive experiments and observation, and because this particular problem survives multiple full wipes, reformatting/partitioning, and all possible ROM/sim/APN/network/relevant settings combinations, as I see it, there are only 3 possible conclusions to draw:

1). The problem is hardware related, but DorimanX kernel 8.14/9.14 or higher function in such a way that almost entirely masks the underlying hardware problem, perhaps in a similar way that some PC hardware is manufactured with a hardware malfunction and a firmware patch can 'workaround' it to avoid the need to replace/refund the hardware.

(Even if it turns out to be a hardware problem, Samsung will not deal with warranty claims in relation to it.

They have admitted that were fully aware of these RIl crashes and logs before the first jellybean leak and implemented logcat output in their stock ROM specifically for this issue, yet consider it as an acceptable problem, and 'theres nothing to worry about, it's normal', etc..

So I'm wondering why Samsung even bothered to have logcat output filling up a user's storage space without any advance warning or notification that this would happen, nor informing users that they are safe to delete, nor explaining how to do so.

There would undoubtedly and predictably be ALOT of 'noob iphone-like' users on stock Jellybean ROMs who would have no idea why they have no space left after a year, nor how to fix it.

I see no rational reason for the logs being intentionally designed to appear 'for official Samsung diagnostics reasons' to begin with anyway, if they are ALSO never going to be read by a technician to diagnose them anyway, and having already implied that they don't care, and stated they wont fix it.

It's one thing so do something nonsensical, but to spend a lot of money and pay people to make a whole string of crazy and 'even more nonsensical' decisions based upon that, which also have no bearing or relation to physical reality, is just mind-boggling.

I think some Samsung employees need serious and immediate emergency psychological intervention.)

2). There is some common code in stock Samsung Jellybean and stock cm10.1 kernels that causes the problem.

Having said that, there are others who have near-identical problems that have been fixed by one or another troubleshooting method mentioned on this forum, most of which were undoubtedly not on fresh installs and a lot of messing around had been done prior, so no surprise there.

3). The problem primarily lies in the modem firmware, but additionally, stock Samsung ROM or CM10.1 and other kernels make it worse somehow, or at least fail to minimise/workaround it, whereas DorimanX kernels 8.14/9.114 or higher coincidentally/unintentionally work almost flawlessly with the buggy modem firmware, perhaps just masking the problem, or interacting with it differently.

Personally, part of me hopes that it's an unfixable hardware fault, as mine still has over a year of warranty left, and I doubt they will replace the modem module in it, and we all know they won't fix the modem firmware if thats to blame, and will instead opt to give me a brand new boxed unit to replace it, which I will then put straight on ebay :)

Best of luck anyway :cowboy: