yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] GGXtreme:
B6 gives me random reboots with a Live OC of 105%. B5 doesn't give me reboots at all. B6 also cut my wifi signal strength roughly in half for some reason. I'm wiping and reflashing just to be sure. Also, I'm not sure if this is a kernel issue, but I get a pretty annoying lockscreen/wake delay on all ICS ROM's and kernels I've tried. Gingerbread and Froyo ROM's and kernels wake instantly.

Edit: B6 is causing my phone to freeze, reboot and crash a lot with any sort of Live OC (no undervolting or anything else). This is a clean flash (full wipe, clean kernel files, etc.). Screenstate scaling and DIDLE are disabled, because they both give me almost instant sleep death. I'll flash back to B5 for now.
[Captivate Android Development] jcjcc:
On the latest beta, removal of Live OC on 100/200/400 steps is great! I'm able to get 130% live OC perfectly stable now, whereas before it was impossible to find stable voltages on the 200 step (at 260MHz).

Please keep this change!

edit: it has trouble jumping from a non-OC step to an OC step. With min freq & max freq set to 400, it's perfect. With min freq and max freq set to 800 (at 1040), it's perfect. With min freq set to 400 and max freq set to 800: instant death. Strange when both of the enabled frequencies are perfectly stable alone.

Well, bumping INT on 400 step to 1175 fixed it, so no worries. Now to flash i9000 GB bootloader and mess with DIDLE.
[Captivate Android Development] topiratiko:
+1 live oc is much improved

Sent from my Galaxy S Captivate on Slim ICS 2.9 w/latest IcyGlitch
[Captivate Android Development] scottcwhite:
My galaxy s settings doesn't have gamma hack I don't think. All I have is "color tuning" where everything is currently set at 1.000. Is this what your decreasing by 20/18/20 ?
[Captivate Android Development] mbc663:
Sounds like your on icssgs.
[Captivate Android Development] prbassplayer:
No. It's should be under those selectors.
[Captivate Android Development] capocaccia:
He is using team icssgs. I am too and gamma hacks doesn't show up in that app on my phone either.

Sent from my Samsung Captivate running Team ICSSGS 4.0.3
[Captivate Android Development] scottcwhite:
I'm on SLIM ROM. What ROM ate you running API I can pull the apk out of it and replace mine
[Captivate Android Development] prbassplayer:
Slim 2.9
[Captivate Android Development] Wakamatsu:
The gamma settings is accessed through Color Tuning.
[Captivate Android Development] scottcwhite:
same here.wonder why I don't have the second set of settings
[Captivate Android Development] disellusional:
try

.772

.772

.884

-12

-12

-15
[Captivate Android Development] cucumbersmell:
B6 issues when using the camera

I flashed v14b6 on 3 different Captivates all running Slim ICS 2.9 and then had issues with freezing or rebooting when using the camera. This was during my nephews birthday party while I tried to take a video and in less than a minute the phone froze and I had to pull the battery. So, dad grabbed my nieces Cappy to take pictures while mine was rebooting and then that phone rebooted itself. I flashed them all back to v14b5 and was able to take videos and pictures without any issues.
[Captivate Android Development] DJSave:
I tried your settings and I think its better

coz Super Amoled screen has on more green subpixel, everything gets more greeny I think. So what are the best settings to get natural color out of your Cappy screens?
[Captivate Android Development] b-eock:
more sub pixels of blue and green, not just green
[Captivate Android Development] shuyin1102:
That's too much yellow. My favourite setting :

0.6 0.8 1.0 -5 -5 -1
[Captivate Android Development] RootTheMachine:
I like your settings of -20 -18 -20, but sometimes at minimal brightness the screen becomes very greenish. I think there was a similar issue with voodoo color a long time ago

Sent from my Dark Knight ICS i897 Captivate
[Captivate Android Development] topiratiko:
Aaarrgg! I'm getting charge death EVERY night!!!! What can I do?

Sent from my Galaxy S Captivate on Slim ICS 2.9 w/latest IcyGlitch
[Captivate Android Development] Wakamatsu:
I have the same setup as you and had some problems with sleep deaths. Re-flashing everything did the trick for me.
[Captivate Android Development] cyberbandit1998:
I'm on b6 and when I restart my phone it keeps CPU at max after a while it will slow down. Is there anything that starts when phone does to cause this and anybody else notice this
[Captivate Android Development] sixstringsg:
Check the logcat and see. Maybe mediascanner.
[Captivate Android Development] scottcwhite:
Auto brightness

Anyone else's Auto Brightness not working on B6 ? I just tested on 3 different supported roms and it's not working. When you first select the box it dims, go out in sun and it get bright as normal but then go back into a dark room and it stays bright. Have to uncheck/check box to get it to dim again.

Flashed B5.1 (last version that fixed BLN that came after B5) on all three roms and it worked flawlessly on each. Reflashed B6 on all three , doesn't work.

Possibly for the dev to look into this ? Thanks
[Captivate Android Development] TRusselo:
not compaining as i love this kernel, but i have now after a year exeperienced my first few sleep deaths after for the first time overclocking by liveOC (bus) at a settings of 110% 105% and 102%.

perhaps bad bus is the cause of users sleep deaths, maybe allowing bus to be underclocked to 90% will fix sleep deaths for users that experience it at stock settings.
[Captivate Android Development] jerkysh:
never had SoD because of LiveOC, my stable is 800 mhz with 115%

my gaming option is 1200 + 120%

and hardcore 1000 + 150% ( or 1300 + 120%)
[Captivate Android Development] disellusional:
after reboot nstools shows min and max are the same (i set it at 200-1200 and it shows 1200 for both)

probably why cpu spy also says its on highest
[Captivate Android Development] scottcwhite:
At 1000 / 120 loc and never had sod either
[Captivate Android Development] tkjeeper:
no sleep death here, aokp build 28, live oc'd to 116%, 1392 Mhz, magic for me, saved in NS settings as the magic formula for my cappy
[Captivate Android Development] hyperpowerr:
For minimal brightness settings, I use -18, -16, -17. I get the best contrast with these settings and it seems to eliminate some of the blurriness.
[Captivate Android Development] daskanda:
Hey guys a weird issue..... I'm using this kennel with THS	ics..... Overclocked to1500....... When I have my phone on for a long period of time around 30 mins or so just browsing the market or playing a game i get this weird pixilated line about a quarter of the way down from the top of my screen.... It shows even on top of the lock screen and just keeps flickering the only way to get rid of it is to reboot...... Any ideas on what it could be?
[Captivate Android Development] Tk-Glitch:
GPU or RAM instability I think. Try to play with Int voltage further.
[Captivate Android Development] kevinnol:
Live OC/Custom Voltages is a awesome concept.. need some time for the user but its worth it :b

Got some problems with Didle everytime i turn it on i get sleep deaths
[Captivate Android Development] :
Yeah I got sleep death for the first time since I had my Cappy with Deep Idle, had to turn it off, wish there was a way to use it without SOD, reminds me of the good ol HD2 days when I got SOD daily
[Captivate Android Development] daskanda:
my Int voltages are as follows right now:

1304- 1250

1152- 1225

1000- 1200

800- 1175

400- 1150

200- 1150

100- 1075

my arm voltages are at:

1304- 1425

1152- 1400

1000- 1375

800- 1250

400- 1125

200- 950

100- 925

do you see anything wrong with these? should i try increasing the int voltages by 25 on each step or would that take it too high?

thanks.
[Captivate Android Development] Tk-Glitch:
Your Int voltages are looking unusually high to say the least. My phone don't like anything past 1.225 for example, and for the same OC as you, here are my Int settings :

1304- 1225

1152- 1200

1000- 1175

800- 1150

400- 1125

200- 1100

100- 1000

Also, for your ARM voltages, try to be more linear. Here are my settings :

my arm voltages are at:

1304- 1450

1152- 1375

1000- 1275

800- 1200

400- 1075

200- 950

100- 850

My settings may be unstable on your phone, but you get a starting point. Hope it helps :)
[Captivate Android Development] daskanda:
thank you.... im trying your settings now... will tweak them for my phone as i go :).... thank you for the great kernel
[Captivate Android Development] Monfro:
Old Clocks safer

My phone's bus/GPU can be overclocked safely only to 101 or 102%, at higher values applications or the phone itself crashes.

The processor on the other hand is quite good, and i can overcklock to 1400 without problems.

I want to ask: is it possible to go back to the clock scheme we had until v14preview5? So only the multiplier applied, and no bus speed added.

On v14b1 this is the scheme:

1440 MHz = 206 x 7

1304 MHz = 217 x 6

1152 MHz = 209 x 5.5

1000 MHz = 200 x 5

So the bus is overclocked in all the steps other than the stock 1000.

This makes my phone crashing at every speed other than stock 1000 (+102% liveOC).

It took me a while to understand why my phone was crashing, while on v14preview5 i could stay safely at 1400 (+102% liveOC).

I think it is better to give OC steps determined only by the multiplier, leaving to users to set liveOC.

Probably i am unlucky with a bus/gpu that can be only light overclocked, but i think i am not the only one.

For this reason i am asking if it is possible to have OC steps determined only by the multiplier, as in thev14preview series.

Big thanks to all the people involved in this wonderful project!!
[Captivate Android Development] Silencer96:
Update:

I've logged 8 hours of light usage on my phone with 82% left.

I'm using Glitch onDemand with the stock Samsung battery.

I'm definitely impressed, thanks for your hard work guys!
[Captivate Android Development] sinichi21:
Im having a momentary lag when from time to time like when i go to xda app browse threads then press back repeatedly until it reach the homescreen launcher i get a lag when doing that but it happen only a sec then jsut let sit and lag will go away is this normal? using ondemand stock arm and int voltage
[Captivate Android Development] pboy:
OC/UV stability

Just wanted to thank the incredible work you guys are doing here. The beta version is even easier to OC/UV than pre5 for me. Running at 1512 with decent UV. I've been testing stability with my usual usage and some games, so far it's fast & smooth. Any suggestions to really test/stress the phone for stability? Thanks!!
[Captivate Android Development] sixstringsg:
Run a 720p mkv on software decode in mobo player. It stresses everything.
[Captivate Android Development] pboy:
Cool, will give that a run a bit later. Btw, correct me if I'm wrong here, OC doesn't shorten the lifespan of the phone but a HIGH voltage settings would right? I'm all for UVing to save battery but I don't need to OCing if it might kill my phone in a few months.
[Captivate Android Development] shaolin95:
The kernel is not using more voltage than what is the max set by default so you are not really running dangerous voltages but then again..heat is always a factor so if you live in a ultra hot climate you want to make sure your phone is nor burning your hand. :-) Also INT voltages over 1250 really does not help as far as I know so try to not go over that.

As for lifespan...as always there should be some effect when you run something faster compared to someone running stock but really, just like PC CPUs, the phone will be outdated way before you can killed it by running overclock IMHO. I overclock pretty much anything that gets on my hands (not that your pervs!) :D
[Captivate Android Development] jayRokk:
Tried out the latest Kernel.....

WOW!!!!!!!!!!!

Thnx a bunch guys!!!!!!!
[Captivate Android Development] acras:
LiveOC values under 100% aren't applied. Trying to get 1200 from 1304 by using low LiveOC value.
[Captivate Android Development] daskanda:
Just wondering..... Why exactly would you want to do that? When you can just use the lower frequency step as max?

Sent from sweet sweet sgh-i897 running ice cream sandwich
[Captivate Android Development] Monfro:
Because his bus/gpu can not be overclocked too much, like mine.

On B1 OC steps include all bus overlooking and we need a lower liveOC than the one set in those frequencies, otherwise our phone crashes.

I forget to write this in my previous post: liveOC settings under 100% are not selectable.

Sent from my Captivate
[Captivate Android Development] acras:
You're wright. Just wanted 1200=200x6 with lower bus speed instead of 1304=217x6.
[Captivate Android Development] stewi21:
In call volume script

Hi all i have skimmed past a few posts about a script that can change my in-call volume, i recall it being glitch related, where can i find it? I searched but with no avail. Thanks in advance :)

On another note the kernel is running great :D
[Captivate Android Development] ThisWasATriumph:
So whats the consensus on i9000 bootloaders? Do they seem generally beneficial? (I've read they fix Didle sods but is that all they affect?)
[Captivate Android Development] unknownyello:
i am on the gb bootloaders and i get sod with didle enable whatever governor i choose. i'm thinking about testing it with the i9000 bootloader.

o btw, i'm on DK rom.
[Captivate Android Development] shuyin1102:
Im on i9000 bootloader for 2 days, no SoD/CoD with DIDLE :) REMEMBER back to stock GB ROM before flashing, heartache... :o
[Captivate Android Development] Monfro:
Yes, before go stock and then flash i9000 bootloader.

And after flashing you will have i9000 button combos to enter recovery and download mode
[Captivate Android Development] swimomatic:
Have you tried using DIDLE yet? What governor and scheduler are you using as well?
[Captivate Android Development] drawde40599:
color settings

Any1 tell me what ALL color ( gamma / multipliers ) values of this kernel are ? Or where r the files located?
[Captivate Android Development] topiratiko:
As far as charge deaths go....can someone plug they're phone into charge and let it sit for a minute then fire up CPU spy and see if phone enters deep sleep? I remember that it does (I think?) If that's the case, then its essentially a sleep death, not a charge death and maybe implementing a 100mhz charge frequency like in gb would help

Sent from my Galaxy S Captivate on Slim ICS 2.9 w/latest IcyGlitch
[Captivate Android Development] mbc663:
i remember from before, mine wouldnt enter deep sleep while plugged in
[Captivate Android Development] topiratiko:
K just got home n plugged in n reset stats in CPU spy...phone DOES enter deep sleep...100 mhz probably would take care of charge death...but the problem of sleep death remains...damn cappys

Sent from my Galaxy S Captivate on Slim ICS 2.9 w/latest IcyGlitch
[Captivate Android Development] NightHawk877:
Had a sleep death three times since installing beta 6 today. went back to beta 5.
[Captivate Android Development] darvo:
Call record

Dear sixstringsg. I know call record isn't supported in CM because it is illegal in some countries, but I'm wondering if it is illegal to distribute a kernel with such capabilities. After all, you are not responsible for anything that may happen using your kernel. I did a research about it and only found an answer from b-eock and I was just curious to hear about it from you. Thank you for your contribution and sorry if this is considered as spam.
[Captivate Android Development] space_eyes:
I would suggest that you should look into your research again from a reliable legal source.
[Captivate Android Development] sixstringsg:
Before I say anything, I am going to preface it with none of this is fact. It is what I remember, mixed with a little assumption. I am almost sure that call recording is entirely ROM side. That being said, I am not sure about the legality of releasing a ROM with call recording enabled. I don't know if it's illegal because it's aiding, or it's legal because the developer is not doing the recording.
[Captivate Android Development] darvo:
The reason I'm asking is because some custom kernels on xda have the required patch and many call record apps are available on Google Play. Also, I know it is totally legal in Canada. It might also be only because of the lack of proper kernel drivers for our device. Just wanted to have a final answer from sixstringsg.
[Captivate Android Development] mindphaser2k9:
AFAIK, there are 2 options for implementing a call recording:

- In the kernel side, then using a specially written software, like this which uses kernel with patches. But currently nobody made kernel patches for Galaxy S

- In the ROM side, using libs with the call recording ability, then software which records calls using Android API. This is how the recording works on SGS with Android 2.2 and how it works on SGS2 with Android 2.3. There are no solutions for SGS with Android 2.3+ for now.

And it looks like there are no any legal issues at all to support recording ability on kernel side or with audio libs until there is no recording software in the ROM.
[Captivate Android Development] aalh:
I have had no SoD/CoD with B6

I have a warranty replacement cappy because of the SoD issue

as a bonus the GPS works great

I would recommend making the call if you have warranty left
[Captivate Android Development] b-eock:
It was in MIUI GB for some time. It has the be both ROM and Kernel for it to support it.
[Captivate Android Development] shaolin95:
Sup guys....I making a come back! So should be posting more again! :D
[Captivate Android Development] b-eock:
Whats up man, haven't see you forever :P
[Captivate Android Development] TRusselo:
Re: Call Recording

it is illegal to record a conversation without consent (or notification) in most states, and countries, and in India you need WRITTEN consent. As when you call your carrier to ***** at them you get a message " This call may be monitored for quality assurance and training purposes"... or some crap. Thats them telling you... "this is being recorded, hang up if you do not agree".

There are apps out there that record calls but reviews are not promising and seem hit and miss. Give those a shot. one may work.
[Captivate Android Development] Malorkus:
Anyone else been getting a lot of hard crashes (requiring battery pull) since updating to B6? I'm downgrading now to see if it goes away..
[Captivate Android Development] raz123:
Citation needed.

According to Wikipedia, quite a few countries allow recording without mutual consent.

Moreover, it shouldn't be developers' job to police who uses what.

This was the rationale when the camera shutter sound was made optional.

PS: Korean Samsung ROMs have access to recording option by default.
[Captivate Android Development] disellusional:
i'm not sure what i'm doing wrong..

i finally thought i had a stable live oc and voltages

i tested with stability test and also with a video on mx player sw on

then all of a sudden im scrolling through a database and the phone freezes/locks up and i have to reboot

what am i suppose to do now?
[Captivate Android Development] visionlogic:
+1

Recording capability does not equate to recording under US federal or any state laws. A plethora of analog and digital devices for recording various communications are manufactured and sold legally. Only when recording takes place is the recording party subject to the legal strictures of their particular jurisdiction, if any.
[Captivate Android Development] sixstringsg:
Ok guys, it's been talked about enough. If there is a specific patch that someone would like me to include to enable it, I am happy to do so. I am not going to personally put effort into it, as it is not a feature I plan on using at all.
[Captivate Android Development] shuyin1102:
I think Icy Glitch is very close to final release, just fix the usb transfer speed and it's not BETA anymore, the best kernel for ICS, cant wait for that... :p
[Captivate Android Development] raz123:
For those who have installed the i9000 BL, any special instructions? :confused:

I went back to stock GB and used Odin to flash, but I keep getting failures.

See pic:
[Captivate Android Development] b-eock:
Are you on an AOSP ROM or STOCK?
[Captivate Android Development] raz123:
Stock KH3 w/CWM. One-click Heimdall.
[Captivate Android Development] shuyin1102:
My exp in flashing : install samsung drivers, connect your phone to pc, open Device Manager in Windows, if you see a modem icon (not a usb icon, try different usb port) then you open Odin and start to flash, i always flash with the pit file

Why was you flash in pda slot? What we need is update bootloader, so check the Phone Bootloader update and flash in bootloader slot
[Captivate Android Development] raz123:
Just following the intructions:

EDIT: Tried Odin with the file (bootjvt.tar.md5) in the Bootloader slot. Failure as well. Going back to 1-click Odin (I897UCKK4).
[Captivate Android Development] topiratiko:
hey guys is 1300mv too high of an arm voltage @1332mhz?

Sent from my Galaxy S Captivate on Slim ICS 2.9 w/latest IcyGlitch
[Captivate Android Development] jcjcc:
Strange, I did it from 1-click KH3 too and it was fine (deep idle working perfectly btw!).

I think mine was at ARM 1400 and INT 1175 for 1300MHz (1000 at 130% live OC).
[Captivate Android Development] topiratiko:
Cool thx man

Sent from my Galaxy S Captivate on Slim ICS 2.9 w/latest IcyGlitch
[Captivate Android Development] jcjcc:
Can someone else try this: on the latest beta, set max and min frequency to 200MHz, all stock voltages, no Live OC, no Deep Idle, unplug the phone, and see if it sleep deaths?

For me, with frequency locked to 200MHz it sleep deaths almost instantly (with all settings at stock!), and it's totally fine at 100MHz and all other frequencies.

Maybe this is related to why so many people are reporting sleep deaths. Or maybe it's just my phone being weird.
[Captivate Android Development] sixstringsg:
Bump the arm voltages 25 on 200, and test.
[Captivate Android Development] jcjcc:
Nope, still get a sleep death.

ARM 975mV, INT 1100mV
[Captivate Android Development] sixstringsg:
Play with raising them each a little, then testing. Something wonky might be happening with the new live OC thing, I'm not sure.
[Captivate Android Development] sinichi21:
did you unzip the file? you need to be on stock rom first before you can flash this
[Captivate Android Development] jcjcc:
So far so good at +75 (ARM 1025, INT 1100).

Stock

1000	/ ARM 1275, INT 1100

800	/ ARM 1200, INT 1100

400	/ ARM 1050, INT 1100

200	/ ARM 950, INT 1100 <- ARM 1025, INT 1100 eliminates sleep death

100	/ ARM 950, INT 1000
[Captivate Android Development] tkjeeper:
Hey six thought I'd run this by you. Tried another rom, then tried my build 28, glitch build 6 nandroid, I flashed the rom, then the kernel, then tried the nandroid, failed to mount data. Had to go back to my nandroid from same rom but with b5. Probably something I did wrong but wanted to run it by you. Thanks for all you do

Sent from the frozen tundra known as Canada.
[Captivate Android Development] RootTheMachine:
Usually, just wipe data or toggle mounting it manually

Sent from my CM9 ICS i897 Captivate
[Captivate Android Development] Blackcrx:
out of curiosity, can someone please post their voltage settings while using slim 2.9 rom?

just want to make some comparisons

i currently dropped 50mv off all the arm voltages. tried enabling DIdle and it died within a few minutes
[Captivate Android Development] DJSave:
I'm getting ramdom Freezes and reboots, with B6 and my stable tested settings:

110% LiveOC 1325 max core, min 200 and unchecked use default voltages thing. my Cappy freezes and shows some artifacts on screen on some pixels and then reboots. I even went back to test build after B5 and I got 2 reboots on new settings LiveOC 117 and 1.4 max core. now I'm on B6 , 1.2 CPU and no Live OC

what can I do with that? I want to have stable 1.4 CPU with 110-115 live OC