[Samsung Galaxy SL i9003] loSconosciuto:
[MENTION=4463931]Gondya bhau[/MENTION]

It's happening to me also and as I said the same thing happened with this. I guess keeping awake the device using kernel wakelocks limits the activity of AlarmManager. I'm actually not sure that the device is really awake as much as shown in the history, I have to verify this yet, maybe it's some sort of bug in the stats. I'm thinking this because even if the device stays awake a lot of time, at least according to the history, there's no noticeable increase in the battery consumption when the device is considered awake.

I mentioned Android 4.2 because the changes to the battery history are maybe hiding the problem. Maybe I'm wrong and the problem was solved, I can't say for sure, but it's surely not a kernel problem.

[MENTION=265360]ricpersi[/MENTION]

I misunderstood your problem (I'm referring to the PM). It's just that untill now only completely lack of signal was reported to me as issue, you are having issues just with mobile data.

That's not happening to me. I will include Samsung's syng bug fix and see what happens. It was made for something else, but it could maybe help to solve this problem since it keeps the phone more active if I'm not wrong. It's been a long time since I used it.

I'm having a weird issue with mobile data though. Whenever I'm crossing a certain place, I lose the mobile data connectivity. It happens everytime and always in the same place. What I noticed is that the phone takes a while to realize that the connection is dead. Maybe what's happening to you is similar, but if the device is not awake, it doesn't reconnect.

Thanks again for the logs. I don't have so many reboots and I don't think it has to do with corrupted partitions.

[MENTION=4526632]nbrian2012[/MENTION]

I don't think it's a kernel issue. From Alpha8 to Alpha9 there were no changes that could have caused this problem (I'm not completely sure though) and if it happened with every CM build, including the ones running the old kernel, the problem is maybe somewhere else.

[MENTION=2606021]cukierkas[/MENTION]

Regarding the app, it's usually the opposite problem. If you are not allowed to use it, maxSdkVersion was probably defined. Read the red warning right below. As stated there, there should be no reasons for an app made for GB not to work on JB.

I don't know what else the problem could be, I don't even know of which app you are talking about nor if the problem is that you can't install it (so it's probably maxSdkVersion) or it just doesn't work (buggy).

EDIT: I kept reading what I linked. It seems that maxSdkVersion is now ignored, so that shouldn't be the problem.

On a different note, I found a way to disable SmartReflex only for the additional fifth OPP and so to make 1.2GHz stable. I'll decide whether to include it or not (it might bring some more instabilities) and whether to use 1.2GHz (which requires at least 1.4 V to work correctly on my device and no SmartReflex) or 1.1/1.15GHz (which works with SmartReflex enabled and 1.3875 V seems to be sufficient).

Also, I found that the L3 overclock is not actually working and I think that the recalibrations of the accelerometer (which you can perform from DeviceParts) are not working anymore, but who cares about this.