[Galaxy S II Original Android Development] HardCorePawn:
Heh... quite busy in here since the 3.1 release :good:

Apologies for being away... had a rather hectic weekend... :p

What exactly are you looking at in BBS?? You need to look at the "Other" screen in combination with the "Kernel Wakelock" and "Partial Wakelock" panels. The other screen will give a good overview on whether or not your phone is sleeping properly. You need to compare the Awake and Deep Sleep times with the "total" time shown at the top... and see if they make sense with what you've been doing with the phone...

If in your 6 hours, it was awake for 5 hours, asleep for 30 mins and screen on time of 30mins etc... then something is seriously wrong... then you can use the KWL and PWL panels to figure out what has been taking all the time!

Don't look at the %'s so much as the actual times... also, if you click on the graph, you'll get the breakdown of the various signals, like wifi, mobile network signal, gps, awake, screen on etc... this can be useful to determine if it is a crappy signal that might be causing issues... if the bar isn't mostly green then it might be reception related and the phone might be going silly trying to make connections (if I leave my phone connected in my locker at work it will drain the battery in about 2 hours trying and failing to get a phone signal!)

Sorry my friend... that camera is just broken... I and one of the other devs spent 2 days trying to figure it out... the error is being generated in camera binaries... so until Samsung release source codes for JB (fingers crossed for their 4.1.2 release, but don't hold your breath) there really isn't anything else we can do... :(

The issue stems from the CM camera attempting to have no shutter lag... it seems to be causing some sort of timing issue with various functions... The only workaround is to install a 3rd party camera to use for when you need FFC. Personally, II use Camera Zoom FX, but there are other free ones on the play store that work OK... just note that you'll probably end up with some shutter lag for the FFC. Sorry :(

TBH, I can't answer this... I haven't even got a 4.2 version built yet.

1. There was a reason for this, but I can't recall exactly what it was... I think it was due to other lockscreen changes that would push things off the bottom of the screen etc...

2. We can't put the weather/calendar stuff on the screen with the lockscreen pattern, there just isn't enough room... this is why they are not shown as options (only clock and battery) in the lockscreen menu when you have pattern set as the security setting.

3. That is strange... I just tested this and it seems to be fine?? An easy way to test your theory is to do a nandroid backup, then do a full wipe and install... if it works, then you know that this is probably the cause... ;) You can always restore the nandroid backup and all your data will be restored :)

Heh... real life getting in the way of my computer geekery! :p

Most probably... I assume you're talking about the inverted AIO package from this page: http://www.slimroms.net/index.php/downloads/all/viewcategory/106-inverted-addons-full-packages

I haven't had this issue myself, but I am only using the basic real dark slim gapps package (don't want all the extras! ;) )

You should be able to remove the inverted app (delete .apk from /system/app) and install the standard one... then it should let you update it.