[Sony Xperia S, Acro S, Ion] cronot:
As far as features, it's final. Read the OP. With that said, I do plan to release at least a couple more builds, but nothing really big, mainly just maintenance and scracthing an itch I still have (Camera). Remember that CM 10.1 itself has been frozen upstream, so there's nothing really new to expect about it - even CM 10.2 should very soon die out too, as KitKat is making the rounds. The only thing that should be expected of CM 10.1 / OpenSEMC-U at this point is bugfixes or workarounds for bugs, whenever and whichever is possible. What's currently on my task list:

Try to port the CM 10 / JB 4.1 Camera into CM 10.1 / 4.2, to minimize issues with flickering preview on Camera. That's the first thing I wanna tackle when I've got the time to do it

Get the blobs on CameraMixedBlobs.zip integrated on build, and eliminate the need for the Camera*.zip files at all

Minor tweaks on build.prop

On Feature request: Try to find where is the fix for Bluetooth AVRCP on the CM 10.2 tree, and try to cherry-pick it into my tree

On Feature request: Enable SCSI multi-lun on kernel

On Feature request: Try to merge EAP-SIM support (letama's instructions seem to stop short on the UI implementation though, so it'll probably be rough around the edges)

Keep in mind that's a tentative list, however: I'm still not sure I'll be able to accomplish all this, all I can say is that I'll try, and I'm confident I'll accomplish at least some of these tasks.

But that's about it, I think - there's nothing else screaming for improvement on this ROM, besides the display drivers that still has minor problems with 0.1% of apps, but I don't have the skills to work at that low level, and frankly, I think the benefits (getting less than a handful apps working and fixing minor glitches that don't really affect normal usage) aren't worth the time I'd have to spend to fix the issue(s).

As for a timeline - I'm swamped with (real) work until the end of this month, so don't expect anything before the end of the first week of December.

First of all, I believe your problem is much likely to be something specific in your setup. Something in either your router or SIM chip is hosed - you're that guy that tried swapping the SIM card before, and it solved the problem for awhile right? I suppose you've already tried the "full wipe" routine also. I wouldn't rule out that either your telco operator got you another hosed SIM card, or at worst case, you really have a hardware problem, because you're the only one so far that reported this problem, and by that statistic I'd say it's very unlikely that the problem is on the source code. So I can't really do much to help you.

With that said, it's a bit hard trying to parse in that humongous logcat where exactly the problem could be kicking in. It would be more helpful if you've recorded, along with the logcat, the exact time (of day) that you noticed the problem kicking in. There are some weird occurances like "wlan0: Failed to initiate AP scan", and you seem to have an unsually large number of fast-dormancy errors too (you may want to try [MENTION=4900593]mirhl[/MENTION] 's tweak, look a few pages back for the link), but there aren't any more details on these messages besides that "something went wrong", and I can't be sure if these occurances are actually related to your problem, so I don't even know where to start looking at this point. Maybe a dmesg log would help too. Maybe reflashing back to stock, or at least reflashing the modem/radio partition could help.

But again, being honest, don't expect me to spend much time with this unless I eventually spot something really obvious on your logs that help out - but I find that very unlikely, so, other than that, I still think the problem is specific to your device / setup. Any effort on my side then would be wasted time, because I (and most other users) don't have that problem.