Thus "waiting" lol. It's only a matter of time before the AT&T (which we MIGHT be able to use) or the international version comes out.

@clian: BSI = Back Side Illumination = better low light pictures.

This post has been edited by Eiraku: Oct 30 2011, 08:03 PM

True. I have enabled Dive PLUS Cerebrus, gila paranoid. Thus my crappy battery life lol.

After losing my iP4, it's expected I guess.

Try that lookout thing that engadget used a couple of weeks back? The one you can remote install.

This post has been edited by Eiraku: Oct 30 2011, 10:08 PM

To siyah kernel users, which governer are you using?

I tried lulzactive and found it laggy with xscope. SmartassV2 seems to be the best fer me right now. You guys?

Hmm, myself sticking with Smartassv2 for the smoothness.

Also RC3 is giving me reboots during calls that did not happen during RC2, so rolled back. I'm guessing enter sleep at 500mhz (which was changed in RC3) is still a tad wonky.

A shame, because we still have bluetooth streaming while screen off issues with RC2. Oh well, at least everything is a lot better now compared to the pre ver 2 days, when things used to simply die on me without any possible cause.

This post has been edited by Eiraku: Oct 30 2011, 10:26 PM

500 is still very much experimental it seems. IMHO, with bluetooth bug fixed RC2 is still the best RC to be pushed to stable, even with UV it's rock solid stable.

My UVs are VERY minimal anyhows, just to push heat down a notch.

And DarkAngel/Uncle Benny, thanks for the info.

I already know the general governers (Interactive, Powersave, Conservative, Ondemand) from my N900/810 days, but Brazilanwax, Smartassv2 I guess is a tad new for me.

That being said, my own proc ALREADY has issues at 500mhz, it never could be UVed much. All the other steps were fine (they could do -100mv no problem), but my 500mhz was (and still is) extra sensitive.

Maybe turning it into deep sleep freq just made things worse.

That's exceptional. I get 1/3 that normally.

@i9100g: take a pic of the batt and post here? Maybe new samsung strategy to make us buy the 2000mah batt? They can be sneaky bastards like that.

This post has been edited by Eiraku: Oct 30 2011, 11:47 PM

Dead EFS. Reflash efs backup OR send back to Sammy to change circuit board.

To confirm, type *#06# in dialer to check IMEI. If the output is "unknown" then confirm you lost your EFS.

Again backup EFS as soon as you root people.

This post has been edited by Eiraku: Oct 30 2011, 11:56 PM

Have you backed up your efs and using what method?

If not IDK how to save your phone short of sending it back to Sammy.

Some PCs are like that, registery's prolly all messed up. My PC also could never detect my BB. Solution, use another pc or reformat. You COULD try to Ccleaner your registry, but that's not guaranteed to work.

This post has been edited by Eiraku: Oct 31 2011, 12:32 AM

Even IF the battery fit, back cover how? The Note IS GINORMOUS compared to the SGS2, I doubt the back cover is interchangeable/our old back cover (the 1650 one) can fit the new batt.

The 2000mah one might be usable though. Or more realistically, the Spider-foot cover.

Is it just me or is logcat buggered up in Siyah 2.1rc2? Yes I've flashed the init.d script to enable it, but it's still somewhat weird. There's zero output in catlog too.

Applocker is functioning funny as a result.

Manual insmodding logger.ko results in system telling me it's already there. Hmmmmmmmm.

This post has been edited by Eiraku: Oct 31 2011, 08:43 AM

Edit: Reinstalled app locker. Working fine now. Funneh.

Catlog is still empty though. Prolly needs to reinstall as well (edit 2: yep that fixed it).

This post has been edited by Eiraku: Oct 31 2011, 09:17 AM