yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] sixstringsg:
Stable settings mean nothing between kernel versions. Each kernel will OC different, especially with something as new and finicky as Live OC. You need to retest your settings, because clearly they are not stable anymore. The artifacting is typically too high of a Live OC, because you are pushing your bus too far, and getting memory or GPU corruption.
[Captivate Android Development] DJSave:
110 liveOC was stable back in B3, B4,B5, testbuild afterB5, and on B6 I got this reboots. okay maybe it lacks voltages, how much would be normal to increase voltages?
[Captivate Android Development] prbassplayer:
No one can answer this for you. Start playing with voltage by increasing or decreasing 25mV at a time. It can be a pain in the ars but the end result usually is worth it.
[Captivate Android Development] daskanda:
There's a live oc guide linked in op.... You should refer to it for info on live oc and limits of the cappy
[Captivate Android Development] scottcwhite:
Wouldn't you want to only decrease ARM to gain more battery not increase ?

That being said and I know every phone is different but I use the settings bass posted a while back and am loving life.

On a side note, I spent 20 bucks on Amazon.com and ordered 2 Anker 1800mAh batteries (came with a wall charger) and my first use with one ending this morning with 32 hours battery/ 6.5 hours screen time / 2% left.

So yes, I'm as happy as a hog in slop
[Captivate Android Development] sixstringsg:
Yeah, those are great. As far as under/overvolting goes, there is no real impact on battery. UV/OV should only be used to find a stable overclock, not to try and save batter. It's such small amounts of power, it's not really useful.
[Captivate Android Development] prbassplayer:
Lower voltage will offer better battery life but first you need to get it stable (usually requires to bump the voltage)
[Captivate Android Development] ThisWasATriumph:
Same exact thing happened to me. Opened the facebook app and the screen went all artifacty and rebooted. Was stable on 1344mhz and 112% overclock until b6...
[Captivate Android Development] Malorkus:
This is also what I reported last night-- screen artifacts and frozen, requiring a battery pull to reboot. My LiveOC settings (120%, and then I also tried 115%) never caused problems with any previous kernel versions. It even happened while using an extremely un-processor-intensive crossword puzzle app, although I suppose something running in the background could have been affecting it.

I went back to the unofficial B5/B6 update posted by sixstringsg right before the official B6. So far no problems, but it's still early.
[Captivate Android Development] DJSave:
I tried to dafault my OC settings and only used 1.2 max CPU, no liveOC and I got same artifacting-reboot thing :( I calibrated my screen on AOKP build 28 with Galaxy S Settings app, that comes with ROM. could this be a problem? Also installed Ram manager Pro and using Balance option. now I reset my screen color settings to default and trying to test 1.2 OC with NSTools , no liveOC. If problem persists, then it should be a B6 issue
[Captivate Android Development] mbc663:
Your screen color isn't going to affect performance. Do u have deep idle turned off? Not sure what u mean by the artifact term either.
[Captivate Android Development] drktigger:
I think he means the screen breaks up and freezes before the phone shuts off. It has happened to me once. Not sure what caused it though.
[Captivate Android Development] mbc663:
I know too low of a gamma setting can cause the green flicker issue. but if u returned to stock settings and still suffer the same problem, wipe and start over maybe. See if the problem still happens on the stock rom
[Captivate Android Development] pintek:
I'm abit hesitant to update to B6 from B5 atm cause i can stably run at 1.5ghz on performance for about 1day an a half with no issues an no over volting or undervolting an no lock ups while playing any 2d or 3d games phone does get rather warm though after a 5hour gaming session but not so hot to burn just like hmmm that back plate really wants to be a heatsink..
[Captivate Android Development] mbc663:
If you'd like bln, hop on to 6.
[Captivate Android Development] pintek:
updated an still able to get a stable 1.5ghz when needed
[Captivate Android Development] scottcwhite:
I'm stable at 1000 and OC'ed to 120
[Captivate Android Development] GGXtreme:
For those who are running stable LiveOC on B6, what bootloaders are you using? I'm using AT&T GB bootloaders (not even sure if it's current or from some old leak), and I can't OC or LiveOC at all on B6 with freezing, crashing and rebooting problems. I have no issues with OC and LiveOC on B5 or earlier. I've already tried clean-flashing and made sure to run clean kernel files. The vibrate mechanism in my phone stopped working, so now I've been relying on BLN.
[Captivate Android Development] scottcwhite:
Was successful with I9000 on B5 and now on I897 (AT&T) with B6
[Captivate Android Development] pintek:
Using the bootloader that came with CM7 an using 100% oc value an stable at 1.5ghz an no bad things happening just heat generation when i set it to performance an do some 3d gaming.
[Captivate Android Development] scottcwhite:
I too started experiencing the blurred screen lock ups that others have been mentioning since going to B6. Only 3 total and it happens sporadically. Latest was yesterday. Clicked menu and then settings and the screen basically went into this fuzzy lock up and my vibrate came on and stayed on until it eventually rebooted itself.

I've never had this issue before so I just wanted to bring to the devs attention. I'll give it a few more times and then revert back to 5.1 until B7 mcomes out. And again, thank you for all the great work
[Captivate Android Development] airtower:
CM doesn't come with bootloaders. You're likely running whatever you flashed when you last one-clicked or flashed them with manually through odin or heimdall.
[Captivate Android Development] ctechbob:
I had the same thing just now as I was browsing this thread. Seems like I've had some apps crashing lately as well. Namely K9 Mail.
[Captivate Android Development] trinhdacquang:
anyone can tell me! how to use USBhost mode?

i was buy a OTG cable, but when connect to my phone, nothing happen :(

maybe hace to additional power?
[Captivate Android Development] brettchuck:
Smooth as silk on 1.4MHz with 100% OC. 1.5MHz with 100% caused FC when trying to play HD video. Will be inching up live OC on 1.4MHz.

I'm using K9 mail as well and it works great!

Awesome job again guys!!!
[Captivate Android Development] :
I got the blurry screen + reboot too cause I was using the same ARM values from previous kernel, had to bump up my values and it doesn't happen anymore, test for stability by playing HD videos on Mobo Player if it doesn't crash after about 5mins then its stable
[Captivate Android Development] jmtheiss:
This may have already been covered, but is encryption a function of the kernel in ICS?

If so, would it be possible (not asking for it to be done, just if the possibility exists) to compile a kernel with the encryption function disabled, so that Android never tries to check the internal SD for encryption status?
[Captivate Android Development] sixstringsg:
It's a ROM thing.
[Captivate Android Development] melvinaury:
Sixtring, I notice that you post AOKP 29 with 4.04 sorces.

Was Glitch are base on the same sorces and can we use it.

I remember that was mentioned that the Kernel and Rom should be base in the same sources for optimal performance.
[Captivate Android Development] prbassplayer:
Probably would (maybe some issues) but you should wait for Glitch kernel to catch up
[Captivate Android Development] melvinaury:
Then I just wait for Glitch 4.04 sorces before upgrade. ICS is not the same without Glitch.
[Captivate Android Development] sixstringsg:
4.0.4 has nothing to do with kernels. Just ROM side. The same kernels work.
[Captivate Android Development] prbassplayer:
I stand corrected.
[Captivate Android Development] shuyin1102:
After 3 days with glitch b6 on aokp b28, i feel that the battery was not as good as previous release of glitch. In display setting, the pulse notification option always turn on after a few minutes sleep. Maybe the BLN fix is the problem. Can you make a version w/out BLN modules for i897 only to prevent any unwanted issues?
[Captivate Android Development] mbc663:
For a second time in a couple days by six :)
[Captivate Android Development] imb951:
Is Beta 6 working on the latest official CM9 nightly? I'm on THS Build 17 right now and I'm hoping that when I flash the nigtly that I'll be able to use Glitch V14 Beta 6 again
[Captivate Android Development] RootTheMachine:
Yeah it works fine. I had an issue initially that I fixed by clearing NStools settings

Sent from my CM9 ICS i897 Captivate
[Captivate Android Development] melvinaury:
One way to solve you're problem it's to go back to beta 5.
[Captivate Android Development] DJSave:
reverted back to B5.1 (test build before B6) and 2 days stable 1.4 OC CPU w no LiveOC

not a single reboot.
[Captivate Android Development] iphone=closedsystem:
Is it just me, or since about V14.3 has anyone else been undervolting to get some crazy Days / use? I have noticed around total Life from %100 Charge +1.112 days with a -200Mhz underclock. (around 800Mhz Clock Speed.) (Where with the increased battery I have 19Hours was far beyond obtainable...at of course? 1.0Ghz Stock Kernel.)
[Captivate Android Development] TRusselo:
death to the sig above!

anyway glitch 14 b6 - i

was

having issues with sleep deaths while using LiveOC and Didle.

until i flashed i9000 GB booties - now no more sleep deaths.

and i still stand firm that any rom i use runs like crap if i dont install NStools. i have tested between my 2 captivates. if NStools is not installed, i can open an app after 8 hours and it will still be on the page/info i left it on, no matter how many other apps have been opened/used in the 8 hour span and the phone is LAGGGY as hell. however if NStools is installed, 8 hours later, the app opens as if it were the first time since turning on the phone, ie the app was killed as it should when the memory was needed.
[Captivate Android Development] topiratiko:
Imma have to leave glitch cause these charge deaths are killing me! Can't flash boot loaders because power buttons broke can't enter download.

Sent from my Galaxy S Captivate on Slim ICS 3.0 w/latest IcyGlitch
[Captivate Android Development] mbc663:
Adb download
[Captivate Android Development] topiratiko:
I tried terminal emulator reboot download and it just reboots. Do you for real think adb would work?

Sent from my Galaxy S Captivate on Slim ICS 3.0 w/latest IcyGlitch
[Captivate Android Development] sixstringsg:
Adb download doesn't work on MTD.
[Captivate Android Development] RootTheMachine:
You don't need power button for download... Only volume

Sent from my CM9 ICS i897 Captivate
[Captivate Android Development] mrsubway:
Any suggestions? I tried Semaphore and now cannot reflash Glitch. I get stuck on the splash screen and have to reflash Semaphore.
[Captivate Android Development] mindphaser2k9:
Clean init.d from Semaphore CWM then flash flash Glitch. If this doesn't help, clean init.d then flash z_UKCS_v4_by_lippol94.zip then flash Glitch.
[Captivate Android Development] mrsubway:
Cleaned init and did a fix permissions for the Hell of it. Worked! Icy B5 is the best I have found so far with glitchass as governor.
[Captivate Android Development] topiratiko:
Alright guys...been on slim 3.0 stock kernel for a half hour and already miss glitch. Mainly CALL VOLUME and live oc. Is there ANYTHING that can be done about the phone quitting while its on charge? Its done it with wall charger and USB...6 of past 7 nights AAAAARG! The only thing I could think of is maybe having it charge @ 100 MHz instead of entering deep sleep like gb used to do..but I'm no dev. Anyone have any insight?

To be fair, stock 3.0 kernels auto brightness seems to work better and kernel is very responsive for being capped @ 1ghz

Sent from my Galaxy S Captivate on Slim ICS 3.0 w/latest IcyGlitch
[Captivate Android Development] prbassplayer:
Ya I miss the OC as well but its very smooth for a "stock" clock and voltage. I would recommend bumping 100mhz voltage see if that would help on your charge death.
[Captivate Android Development] topiratiko:
Have a value in mind?

Sent from my Galaxy S Captivate on Slim ICS 3.0 w/latest IcyGlitch
[Captivate Android Development] Maroon Mushroom:
Icy Glitch seems to be more stable than Semaphore with the roms I have tried
[Captivate Android Development] prbassplayer:
I can't say but I would start bumping it by 25mV see if it works or not. I wouldn't bump it more than 75mV but that's just my 2 cents. I would also consider int voltage as well (maybe?). I don't suffer from that so I really can't help, just giving ideas on possible solutions.
[Captivate Android Development] topiratiko:
Also I beilive I read that were getting another glitch to support slim ics 3.0's ram boost 383 mb. HAWT

Sent from my Galaxy S Captivate on Slim ICS 3.0 w/latest IcyGlitch
[Captivate Android Development] b-eock:
It isn't just for SLIM it is for any ICS ROM that supports it, but Glitch only support TemaHackSung's work. I am one of their testers so you can trust my info on it :)
[Captivate Android Development] topiratiko:
As long as it works I'm good b-eock

Sent from my Galaxy S Captivate on Slim ICS 3.0 w/latest IcyGlitch
[Captivate Android Development] shaker2k:
Tk , six.. Glitch team.

I love you guys!!

:o:D
[Captivate Android Development] jcjcc:
I agree, and try bumping 200mhz ARM voltage as well.

Mem increase mod -- sweet! Can't wait for B7 lol
[Captivate Android Development] topiratiko:
F5. F5. F5. F5. F5. F5.

Sent from my Galaxy S Captivate on Slim ICS 3.0 w/latest IcyGlitch
[Captivate Android Development] shaolin95:
It is worth it...keeping pressing F5 cause you are going to love it :D
[Captivate Android Development] topiratiko:
:banghead: lol

Sent from my Galaxy S Captivate on Slim ICS 3.0 w/latest IcyGlitch
[Captivate Android Development] b-eock:
Why must you taunt them?!!?!?!? XD

It will come to ya'll when it is perfect:D
[Captivate Android Development] pizz0wn3d:
TK-Glitch you damn tease. Why must you taunt us so?

On the other hand, would the memory corruption on low freqs explain why my screen likes to turn black after playing Angry Birds space for a while? It reminds me of when video cards overheat and just shut off to prevent damage.

Herp derp Captivate XDA Premium
[Captivate Android Development] jcjcc:
I just noticed, smoothass governor never uses the 100-400 steps. Is this supposed to happen?
[Captivate Android Development] scottcwhite:
I'm on latest slim and glitch using what I like to call Bass settings and have had zero issues
[Captivate Android Development] topiratiko:
Bass?

Sent from my Galaxy S Captivate on Slim ICS 3.0 w/latest IcyGlitch
[Captivate Android Development] topiratiko:
f5................f5.......................f5...................................................f5.................................................................................f5

Sent from my Galaxy S Captivate on Slim ICS 3.0 w/latest IcyGlitch
[Captivate Android Development] sixstringsg:
It's not coming out tonight, TK is asleep :p
[Captivate Android Development] ptesmoke:
since this kernel is boss...im gonna go with boss lol
[Captivate Android Development] Wakamatsu:
ASS settings? He's on Slim also.
[Captivate Android Development] swimomatic:
sixstringsg, I cannot begin to thank you enough for how much better this has made my Cappy over the past <2 years. I just recently installed i9000 GB bootloaders along with the latest CM9 Nightly (3/30) with your B6 kernel release. I am amazed at this battery life! I am 8 hours in with little use (testing idling) with full HSDPA on and I have 85% battery left! This is unheard of any other time I have tried any combination of other roms. This is also with a 105% LiveOC with GlitchAssV2 as my governor and noop as my scheduler. I will be donating to you for all your hard work and again thank you!
[Captivate Android Development] Tk-Glitch:
I'll take your thanks for Efpophis and me ;)
[Captivate Android Development] topiratiko:
F5f5f5f5f5f5f5

Sent from my Galaxy S Captivate on Slim ICS 3.0 w/latest IcyGlitch
[Captivate Android Development] RootTheMachine:
Another didle success story with i9000 bootloaders! Still need to figure out top= off though

Sent from my CM9 ICS i897 Captivate
[Captivate Android Development] ptesmoke:
i must have missed it...whats the easiest way to get on i9000 bootloaders? and does tk and six recommend it?
[Captivate Android Development] anishz:
The only way to do is to flash to gb stock for i9000 with bootloaders., or you can go to gb stock i897 and flash boot loaders for i9000, but that's pointless. Don't try it on ICS.

I also got didle working with i9000 boot loaders.
[Captivate Android Development] scottcwhite:
Prbassplayer posted screen shots of his nstools a settings a while back in the icssgs thread. Ever since I started using them I've had nothing but great speed and stability
[Captivate Android Development] daskanda:
You mind sharing the settings? I'm trying to find the best settings for my phone right now
[Captivate Android Development] JoshJ22:
Yea, I've also been curious about this
[Captivate Android Development] tommyguns818:
deleted.....does this have CWM baked in this puppy?
[Captivate Android Development] b-eock:
-_- really all custom kernel have CWM in them...
[Captivate Android Development] tommyguns818:
^^^ Your the man. Im a noob tubber times 20. Thanks for quick response. Im from htc aria land and this is allot more steps to get rolling than my phone. Its my wife's cappy im trying to hook up. she already has glitch with latest cm7. I just have a slight SOD problem and have to revert to stock then flash i9000 bootloader.
[Captivate Android Development] b-eock:
I cam from the HTC Aria too. Just almost 2 years ago though. All Custom AOSP kernels have CWM built in. Yahh it is much different from how HTC ROLLS.
[Captivate Android Development] ninjah:
framework

framework-res.apk for AOKP build 29 with working top=offView attachment aokp_b29_framework_with_blutooth_false.zip
[Captivate Android Development] RootTheMachine:
What do I need to change in framework-res.apk to do this for CM9?
[Captivate Android Development] bryman27:
Here you go sir
[Captivate Android Development] jcjcc:
Here's a CWM flashable zip for the 03-30-2012 CM9 nightly. And ONLY the 03-30-2012 CM9 nightly. Don't flash this on a newer or older build.

Flashing this allows your phone to go into TOP=OFF when bluetooth is off (and use TOP=ON when bluetooth is on).

edit: My experience with this is that sometimes, wifi doesn't work after boot (the icon flashes on and off).

This post & others in the thread regarding this bug: http://xdaforums.com/showpost.php?p=21463880&postcount=164

If you enable bluetooth before rebooting, and disable bluetooth after boot, it works. Some people don't see this bug at all (ROM dependent?).
[Captivate Android Development] Austin Ag06:
Thanks for this. Can I ask what bootloaders you are on. Just curious if this is an effect of i9000 bootloaders and if it works on i897 bootloaders.
[Captivate Android Development] Gromlakh:
The bootloaders have absolutely no effect whatsoever on the phone once it's booted up.
[Captivate Android Development] b-eock:
But they do have to do with how the hardware is initialized, which is why I9000 BL's have sorta been proven to have better chance of no SOD than with I897 BL's
[Captivate Android Development] jcjcc:
I'm on i9000 GB bootloaders (JVT I believe). Can you report if you get the wifi bug or not?

You are right -- but the i897 bootloaders initialize the phone slightly differently. Deep idle is only working with i9000 bootloaders.

Here's a restore zip.
[Captivate Android Development] Austin Ag06:
Sorry, but I'm a bit new to some of this...if I'm running i897 bootloaders and I flash this I won't bootloop or brick or anything, right?
[Captivate Android Development] JoshJ22:
You shouldn't if u flash back to GB before you flash, like a kk4 rom
[Captivate Android Development] Koizuma:
So far running B6 on the cappy and its smooth as butter like always great job on the kernel!
[Captivate Android Development] jcjcc:
Get DIDLE TOP=ON working first -- if it doesn't work on your i897 bootloaders, take a nandroid backup, odin to stock, flash i9000 bootloaders, install ICS again, and restore your backup.

The zip I posted is for getting TOP=OFF to work (once you already have DIDLE working).
[Captivate Android Development] scottcwhite:
keep in my they may not work same for you as every phone is different

Gives me great results like below
[Captivate Android Development] scottcwhite:
Oh, and using fiops w/ glitchass v2
[Captivate Android Development] daskanda:
Thanks but what's your live OC setting?
[Captivate Android Development] TRusselo:
any overclocking setting is completely dependant on YOUR PHONE. no-ones settings will be the same as yours.
[Captivate Android Development] daskanda:
I understand but it helps to have a starting point that's stable and tested already
[Captivate Android Development] Wakamatsu:
That's what he's saying. What's stable and tested on someone else's phone could crash your phone all day long.
[Captivate Android Development] daskanda:
Yes, but it's a starting point.... It's just a matter of playing with the voltages..... And so far I have had good luck with all the settings posted by other members and some tested that I came up with..... Right now I'm running stable with a 252 bus speed...... I was just curious about his settings since he's mentioned them a couple of times
[Captivate Android Development] scottcwhite:
I run 1000 oc'ed to 120% but keep in mind Truss' warning because my exact settings send my wife's captivate into constant bootloops
[Captivate Android Development] :
I remember Tk-Glitch posted awhile back that your voltage settings should be linear and gave an example, helped me figure out the best settings and haven't gotten instability including sixstringsg's 720p Mobo Player stability test. Had to bump up my values 25mV on B6 though. My settings are:

1000 MHz Live OC 120%

1000 - 1275

800 - 1175

400 - 1075

200 - 975

100 - 875

Int Voltage is stock.
[Captivate Android Development] irishvandal:
USB Fast charge DEV kernal patch thread here. DEV TOPIC ONLY - NEEDS TO BE COMPILED

could this charge mod be enabled inside Glitch? I would love to locked down transfers when charging and gain fast usb charges. Would this become a pop-up(option) when hooking up to usb?

sidenote- what controls usb transfer speeds? the kernel or the rom? i am currently getting low usb speeds(.8-1.6 MB/s). is this normal with ics romz or glitch itself?

TIA
[Captivate Android Development] mindphaser2k9:
As you can see in the Changelog, this feature is already announced and currently is in development.
[Captivate Android Development] shuyin1102:
That is kernel issue, it seems like they didnt find out resolutions yet
[Captivate Android Development] jerkysh:
uuh, i'm sooo waiting for b7 :) !!!
[Captivate Android Development] topiratiko:
F5f5f5f5f5f5

Sent from my Galaxy S Captivate on Slim ICS 3.0 w/latest IcyGlitch
[Captivate Android Development] anishz:
Why hasn't your button broken yet? :p
[Captivate Android Development] topiratiko:
Its not as tight as it use to be that's fer sure

Sent from my Galaxy S Captivate on Slim ICS 3.0 w/latest IcyGlitch
[Captivate Android Development] mpencexda:
Thats what she said.. :)
[Captivate Android Development] scottcwhite:
LOL, he got you there Top
[Captivate Android Development] airtower:
So far so good with B6 on 4/02 nightly....

edit: having some issues with the phone losing connectivity. testing without glitch to see if it's kernel related or not.
[Captivate Android Development] TheSoaresan:
I broke my f5 key :(
[Captivate Android Development] Wdustin1:
Lol I saw in the facinate forums that the kernel is in testing and should be here soon! Be careful with your f5 keys