[Galaxy S II General] ph3n0mII:
Perhaps, but that that creates some interesting questions, some of them rhetorical and just 'food for thought' :).

Firstly, how new do you mean when you say 'new'? are we talking around november last year or more recent, or even since the move from cm10.0 to 10.1?

November last year is 'roughly' when i remember the problem starting on both my i9100's simultaneously, (1 with cpu type 2 and one with type 3 btw), and same also happens on my 3 month old p5100 since day 1 of installing cm10.1 on it.

There is also a high chance the problems could have been going on for some time before i first noticed too.

The problems 'appear to have been' fixed, then reintroduced several times since then, the longest time without them being about 2 weeks, and updating to almost every singly nightly since cm10.1.

It reminded me for a while, of the auto-brightness responsiveness problem that seemed to get alternatingly fixed then broken again every 3 or 4 nightlies for quite a while there.

Just trying to get a timeframe on things here.

Also if problem was merely from new/newer cm10.1 kernel code, wouldn't older versions of siyah or dorimanx that also didnt have this new code have 'not suffered from the problem? Dori 9.13 still had the problems, but something in more recent builds fixed it, intentionally or accidentally, i cant say.

But can you see what i'm trying to say here? Older cm10.0 (and maybe early cm10.1) kernel was fine in this regard, but 'new' one has the problem, where as (presumably all of) the older siyah based ones had the problem but very recent ones don't. Just seems an unlikely situation, thats all. If the new custom kernels (that ive tried) don't have the problem, and ALSO don't have the new code that supposedly causes the problem, why do the 'even older' custom ones which also lack the newer 'problem code' suffer from the problem also. :p

When was this new code added to the stock kernel, and which code is it exactly? :p.

Anyway I hope my ramblings help somehow.

Thanks for the advice. I tried that, and all other suggestions, plus many many other ones, all with no improvement.

The gsm signal usually drops out entirely when it happens, sometimes it recovers within 30 seconds on its own, sometimes needs a reboot (even wont auto-recover after 8 hours), sometimes just data drops out momentarily, but pretty much identical logs are produced for all 'versions' of this problem.

Doesn't seem to be caused by, affected by, or affecting calls at all, never once had a call drop out on me...

One interesting thing i've noticed it that the problem happens far more often after completion of data usage, as in, I can often download multi-gigabyte files uninterrupted, and it will drop out instantly as soon as the file is finished, rarely 'during usage' or when phone is idle, but still sometimes. Also, similarly, it rarely drops out if i'm playing a particular game that uses constant 8KB/s, but will very often drop out instantly when the stream is stopped (game is exited). I'm sure this info could help narrow it down, especially now that something in the new dorimanx kernel seems to not crash at all under any condition, so somethings obviously changed somewhere between v9.13 and 9.31 that seems to have fixed the problem, and i'm sure dorimanx now uses a kernel version far newer than cm10.1, which 'should therefore', surely have the same problem.

Please dont laugh at me anybody, i'm really trying to help narrow it down here. :angel: