yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Silencer96:
I'm getting charge death issues with this kernel, it wasn't happening before (but I heard it was a general problem with the ROM anyways).

Are there any precautions that you guys are taking in order to circumvent the issue? Because the charge death problem is kinda getting on my nerve.

Also, what are your guys' overclock and UV settings in nstools?

Thanks :D

Edit: After closing NSTools, I'm not getting any sleep deaths anymore... I wonder what went wrong?
[Captivate Android Development] Abaddon:
what's charge death? it's my second day on hacksung's rom + installed the kernel a while ago. the thing is. my phone suddenly died. 0% battery after baing at 70%. powered it on and died again. after charging for a while and clearing battery stats and clearing cache of nstools. now it's ok. I wonder what went wrong. :?
[Captivate Android Development] Koizuma:
Hate to say this kernel became unusable for me, every time i go to reboot the phone it would just boot loop so im back on 14p5 for the time being.

Edit: Even boot loops with the stock clock and no UV on beta 1
[Captivate Android Development] kevinnol:
Anyone got some experience with UV on the Kernel ?

On V13 i was able to UV 100mhz -200mv and now my phone cant handle -50mv ?

Kernel is awesome so far my cappy has never been snappier :D
[Captivate Android Development] zuN!:
These worked for me on pre5 but not on Beta 1 :(

Do you still need GB bootloaders for DIDLE to work or will DIDLE work no matter what now? I don't understand how it works or how to make sure that you enter that state.
[Captivate Android Development] kevinnol:
Download NSTools from market
[Captivate Android Development] :
It's probably your live OC that's causing it. What worked on v14 preview 5 might not be reproducible on beta 1. I can't OC past 108% (was possible 115%+ before) my UV for Arm are -50 like before for all steps and it's stable but if I even tweak a single setting other than Max Int Volt my camera doesn't work and the phone reboots. So I'm sticking with stock Int Voltages. Good news is it's faster visibly than v14p5
[Captivate Android Development] zuN!:
....if I tried the quoted settings then I would already have NSTools and yes I know you can press Deep Idle for it to be ON. However, in the old thread where this was discussed, you wouldn't be able to reach an actual DIDLE state unless you had GB bootloaders even with DIDLE turned ON in NSTools.

Unless I'm completely wrong about that.
[Captivate Android Development] acras:
As I noticed DIdle works only once when you firstly lock phone after reboot. If you unlock phone and lock again - it doesn't work.
[Captivate Android Development] Boomgawd:
problem

I installed this kernel after teamhacksung CM9 on a captivate with i9000 BL that was running APEX 12.2. Now I boot loop on the kernel and cannot flash teamhacksung again because I am told the zip isnt for this phone..

grrr.

EDIT: Basically I need a CWM zip that will install CM9 on my setup.. IDK why this version wont let me flash it.. plz help.

EDIT2: Lame DFU issue.... was trying galaxy S zip.. Frack.. sorry all, I'm good.
[Captivate Android Development] airtower:
Trying to set live OC values (to lower values than pre-5 by the way) has put me in a bootloop with no access to recovery. Download mode works, but I won't have access to a computer with odin until tonight. :D:D:D:D:D
[Captivate Android Development] Koizuma:
I didnt even touch live OC in this build, was happening on stock voltages with no OC period. I'll try giving it another go after work maybe i just had a bad download or something.
[Captivate Android Development] Geoff-dev:
Nice!

I tried pre-5 and had issues. Then this build came out and I did a full data wipe and installed THS Build 14, google apps, google apps fixer and rebooted.

Download Icy Glitch V14 and installed last night. I have not messed with voltages or OC and have been using it with no issues this morning.

One thing that strikes me is the UI is very responsive and the battery life is a lot better. Didn't charge the phone last night and check the phone this morning and the battery barely drained and the chart is almost flat.

May play with voltage and OC this weekend when I have time to test but at this point this combo of Glitch and THS is amazing!
[Captivate Android Development] JoshJ22:
This kernel is sweet! I've only slightly OC'ed and my phone is blazing fast. No problems here, just wanted to say thanks
[Captivate Android Development] jerkysh:
aaawww yeaaaa!!! finally!!!1 been on this for 5 hours, battery life is awesome, and everything is soooo smooth and snappy !! thanks a lot man!
[Captivate Android Development] nuwan32:
i dunno why but using deeep idle puts my phone in a sleep of death :s but everything else is great.. faster and snappier
[Captivate Android Development] sixstringsg:
Are you using GB bootloaders?
[Captivate Android Development] vcallas:
I encountered the same thing ICS 14 with Ginger Bread bootloaders.
[Captivate Android Development] jayRokk:
Will the gamma work with your CodenameAndroid port after flashing glitch??
[Captivate Android Development] b-eock:
Yes, it is the galaxy s app
[Captivate Android Development] jayRokk:
i shall get to the flashing!
[Captivate Android Development] zeropants:
That's the one I have wifi issues on so far.
[Captivate Android Development] sixstringsg:
We do not support it.
[Captivate Android Development] xxcaptcrunchxx:
I just installed the latest version, B3.. Is the call volume hack gone on this one? Everything else is working flawlessly!! Thanks for your hard work!!!
[Captivate Android Development] sixstringsg:
It didn't work on B2, now it works on B3.
[Captivate Android Development] xxcaptcrunchxx:
Is there a setting I'm missing? Mine is still low, like stock setting..

I also went to '/etc/init.d' and it showed '90call_vol'.. Is this correct, or does it even have anything to do with the hack?
[Captivate Android Development] sixstringsg:
You have to edit that file.
[Captivate Android Development] xxcaptcrunchxx:
Alright, thanks for the fast response!!

You guys rock!
[Captivate Android Development] voldomart13:
I just had some lock screen freezes and a 30+ second delay before the screen would kick on and a random reboot.
[Captivate Android Development] RootTheMachine:
Many people are getting the lockscreen delay, including me.

Beta 3 runs very smoothly, BUT has given me charge death every single night since I installed it. No ICS or glitch build has ever given me charge death until now.

Sent from my CM9 ICS i897 Captivate
[Captivate Android Development] sixstringsg:
Increase your low end voltages for sod.
[Captivate Android Development] RootTheMachine:
But I'm not getting sleep death, only charge death. Not sure if useful, but the phone was off within 100 minutes of being plugged in and screen off

Sent from my CM9 ICS i897 Captivate
[Captivate Android Development] voldomart13:
Not that i'm askin for an OTA but do you think the lock screen freeze or the 30+ wake lag will be fixed in the next build? If needed I can learn how to provide a log of when these events happen for the dev.
[Captivate Android Development] DudeWatsThat:
Mine's working fine,what kind of wifi issues?
[Captivate Android Development] tiuk:
I had wifi issues on b2, but b3 fixed it. Turning on wifi would make it toggle between on and off rapidly until reboot.
[Captivate Android Development] sixstringsg:
What ROM?
[Captivate Android Development] tiuk:
Build 15. Believe i flashed build 16 and glitch v14b3 at the same time so i don't know for sure which fixed it.
[Captivate Android Development] RootTheMachine:
Attached logcat of lockscreen freeze. It's somewhere within this 30 second window.
[Captivate Android Development] Keland44:
i had the lock screen freezes/sticking other then that pretty solid
[Captivate Android Development] theytalkalot:
I am getting sleep death...I thought I saw someone post what the arm and int volts could be set at to help

Avoid sleep death.....or am I just mistaken...I have read this thread a few times, but thought I.saw it here...argh!

Thank you!
[Captivate Android Development] sixstringsg:
Are you undervolting?
[Captivate Android Development] RootTheMachine:
Is the logcat of the lockscreen freeze of any use?

Sent from my CM9 ICS i897 Captivate
[Captivate Android Development] sixstringsg:
I am so busy this week, I haven't even looked at it yet. Sorry, I'll get to it when I can.
[Captivate Android Development] scottcwhite:
Chnging script affects all but internal speaker. Regardless of settings (1,2,3, etc)

the volume stays the same.

External speaker however blew my ears off.
[Captivate Android Development] theytalkalot:
no....should I be?
[Captivate Android Development] pickupman66:
Loving this kernel. so far I believe its been my favorite. I installed it with the team ICSSGS rom and it worked wonderfully. now running it with the NEW Fusion from The Collective (based off build 14 of the THS ICS) and it is rocking smooth. I am not running the overclock, but I am Undervolting it with the NS tools app to tweak the power usage.

so far, ZERO sleep or charger death issues in teh few days with the two roms.

thanks guys!!!
[Captivate Android Development] sixstringsg:
Hate to be that guy.... But did you turn down the volume within the OS?

You can try increasing your voltages a little bit on the lower steps to see if that helps.
[Captivate Android Development] scottcwhite:
All volumes within system settings are set to max. I was hoping to adjust the internal speaker louder with the script changes as I wear hearing aids and the louder the better. Nothing increased regardless of what I did.

The external speaker did change and I love it. I can actually watch youtube and movie trailers and actually hear them at the same time now. Now if I could just get that internal speaker to crank up I'd be happy.

I have to have phone on speaker whenever talking to someone because even with my hearing aid I still can't make out everything being said if I hold it up to my ear
[Captivate Android Development] Time_Zone:
Bluetooth volume seems to be stuck at 2 or 3 regardless of what call volume settings are set in 90_callvol. This leads to distorted conversations for me.

Thanks.
[Captivate Android Development] scottcwhite:
Concur on this also. Tested an hour ago in car. Called voice mail at each setting (0, 1, 2, 3) and all sounded identical. I can adjust volume up with stereo control so this isn't an issue for me but yes, it does exist
[Captivate Android Development] sixstringsg:
I assume that you reboot between each change? ALso, try manually echoing the values with terminal emulator or ADB and see if that works. If you do it manually, a reboot isn't required.
[Captivate Android Development] scottcwhite:
That I did not. Will retest and use TE to echo if that doesn't fix. I did reboot previously though after changing and reading internal speaker setting.

I did notice that after changing and upon first phone use a second script file is created named 90 call volume bak that has the original settings. I then have to manually delete this file so that only the original file with my adjustments exists.
[Captivate Android Development] sixstringsg:
The .bak one is created when you edit a text file with Root Explorer or something similar. It is a backup of the original file, and does need to be deleted in order for the changes to work.
[Captivate Android Development] wolfomega23:
Worked Great, until it Freaked Out

Was listening to music, then the screen froze, the picture shook, and the sound sounded like someone shot R2D2. Only happened when I flashed B3. Otherwise great work. You should contact Cyanogenmod and get into direct collaboration with them;)
[Captivate Android Development] sixstringsg:
How much OC are you doing? Also, elaborate on the collaboration with cyanogenmod. They do ROM, and we do kernel, what good would they do for us?
[Captivate Android Development] daskanda:
I'm getting the lockscreen freeze issue as well... Seems to be occurring more and more often the longer i keep the phone on without rebooting.... On build 16 and b3 kernel
[Captivate Android Development] :
This same thing was discussed a few pages back, its either DSP Manager or your OC/UV settings. I also use voodoo control (vc). I used both vc and dsp manager and my screen would get fuzzy and streaks would show up vertically after some hours of use and reboot. I used dsp manager alone and that R2D2 sound would show up after awhile then reboot. On vc no reboots and no sound.
[Captivate Android Development] thangphysk48:
Same problem like you.
[Captivate Android Development] sixstringsg:
The issue has been acknowledged, but a reason/fix has not been found as of yet.

Note to everyone: we have a google code page, but haven't used it much. I'm seeing a lot of the same issues cropping up, so now seems like a good time to start using it. Here is the URL: http://code.google.com/p/glitch-kernel/issues/list

Rules of Google code: if your issue is the same as someone else's, do not make another one. Just star somebody else's, that way it's not hard for us to wade through them. Give very detailed information. IE:

What ROM were you on when it occured?

Were you OC/UV? If so, by how much?

What was happening when it occured?

Does it happen on stock kernel?

Does it happen often?

Etc

If your issue does not have enough information to move forward, I will not respond to it, I will just delete it. If you post in the thread about the same issue, that's fine, but please paste a link to your issue on google code. This is not a requirement, just a suggestion to make our lives easier, and to make us less frustrated. This way, we do not have to read the same issue over and over again. It gets tiring.

Thanks,

Six
[Captivate Android Development] thangphysk48:
How can I give you more informations to help you fix that problem? Now I've just back to v2 for daily use. Thanks for your kernel. Very awesome.
[Captivate Android Development] sixstringsg:
It'll just be some debug work. Another user has already posted a logcat of the event, so that might be useful. For all I know, Tk could already know what the issue is and I don't. I'll ask again if we need something else that we don't have.
[Captivate Android Development] mindphaser2k9:
There is a new feature in CM9 kernel:

But this doesn't seem to work with Glitch yet.

Are you planning to support this?
[Captivate Android Development] RootTheMachine:
Just use the voodoo control app

Sent from my CM9 ICS i897 Captivate
[Captivate Android Development] Tk-Glitch:
First, to everyone : I know about the lockscreen issue and I know how to fix it.

Now for the guys who are asking for dsp manager with voodoo sound options, there is still missing some voodoo sound settings in it, so it's probably better to wait before everything is added to support the feature, cause voodoo control doesn't recognize this implementarion.

Looks better to me not to loose features.

About the volume boost, I'll look into it but will also most likely need Efpo's help as he's the guy who made it, and since he's very busy it could take some time if I don't find exactly what to change.

Once again, I only have an i9000 to experiment with, so it's hard for me to fix other devices related issues.
[Captivate Android Development] metalfangs:
Great work as always glitch team! Thank you for your dedication.
[Captivate Android Development] airtower:
I'm having a problem with Chrome Beta. On otherwise perfectly stable OC/UV settings, I will get reboots in Chrome in almost every session. Light browsing, just a couple tabs, no flash sites etc. Had the same problem with Opera when I used it awhile back on GB glitch. I know the default response to this kind of thing is "OC/UV less" but I'd hate to sacrifice the rest of the performance of the phone just for the browser. Is there a more directed fix to address this?
[Captivate Android Development] Keland44:
Enjoying beta 3 right now using a 3500 mah china battery running a crap load of stuff 70% 4 hours 15 minutes 30 minutes of screentime 3 gmail accounts turning sync on and off maybe once or twice a hour
[Captivate Android Development] topiratiko:
Beta 4??? Where?!?

Sent from my Galaxy S Captivate on ICSSGS 4.2 w/IcyGlitch v14b3
[Captivate Android Development] Keland44:
correction beta 3
[Captivate Android Development] topiratiko:
Lol OK cool

Sent from my Galaxy S Captivate on ICSSGS 4.2 w/IcyGlitch v14b3
[Captivate Android Development] Time_Zone:
echoing values had no effect fwiw.
[Captivate Android Development] Tk-Glitch:
GPU or RAM may be a bit unstable. Opera was using GPU accel, and Chrome is memory heavy ^^ It could work okay in most cases then when pushed with such tasks show the unstability. You could try a bit more (or less) Int voltages.

Past some "low" OC frequencies, you'll need to find EXACT settings that will work on your phone. A bit too high or too low voltages will lead to unstability, more or less obviously depending on the OC level and your device. The "random user" (sorry, didn't find a more respectuous expression) will generally use a bit too high voltages when overclocking.
[Captivate Android Development] topiratiko:
This is proof of the quality of the Captivate. I remember this guy from the days of JI6 froyo and Paragon roms and even THEN he was running @ >1.5ghz! Been over a year severely overclocked and his device STILL works!!!
[Captivate Android Development] airtower:
Thanks for the follow up. I'm still trying to wrap my head around this whole live OC and arm/int voltages thing. FWIW here's what I have for INT volts (medium leakagesque settings)

1500 - 1200mv

1400 - 1175mv

1300 - 1150mv

1200 - 1125mv

1000 - 1100mv

800 - 1100mv

400 - 1100mv

200 - 1100mv

100 - 1000mv

Although I just cleared NStools settings and am going to start from scratch. I recently got a new captivate and it seems to OC better at times compared to my old one, just need to figure out how to keep it running well.

I'm trying to figure out a process to get the best performance at the lowest stable voltages. The liveoc guide does a good job explaining each part of the process, but I'm at a loss as to how to get values set up for my particular phone. "Messing" with the values doesnt seem to be getting me anywhere. Am i correct in assuming that I can not just dial in max stable clock and bus speeds then start bringing the voltages down?
[Captivate Android Development] sicmadek:
its been so long since ive played with the cappy. me and brother ryude left about the same time. i have no idea how to play with uv now. i dont evern know what leakage does. im like a fresh noob all over again.
[Captivate Android Development] sephoron:
hey, whats the reason the kernel dont have led or bln? greets

Gesendet von meinem GT-I9000 mit Tapatalk
[Captivate Android Development] sixstringsg:
Cause you either didn't install it or read the change log.
[Captivate Android Development] morrty:
I messed something up. I overclocked my phone and then set it on boot. Then my phone glitched out. I rebooted but it reapplies the overclock before I can get into the app to disable it and it glitches out. So effectively I can't boot my phone. How do I fix this?
[Captivate Android Development] Wdustin1:
You can go to recovery and go to glitch and disable the over clock stuff from there
[Captivate Android Development] jecsah:
dear god...step away from your phone.

after that. 3 button into recovery...glitch...clear nstools settings.
[Captivate Android Development] morrty:
How do I boot into recovery from the phone being off? Sorry, I always get into CWM by the power menu on the phone when it's boot up.
[Captivate Android Development] pickupman66:
Power plus volume down? Or plus volume up

sent from my hacked kyros tablet running honeycomb
[Captivate Android Development] Wdustin1:
3 button! vol up volume down power
[Captivate Android Development] morrty:
I fixed it, thanks.

---------- Post added at 08:25 PM ---------- Previous post was at 08:24 PM ----------

I tried this multiple times. Doesn't seem to work.
[Captivate Android Development] :
Boot to recovery and select Glitch. Then reset voltages...
[Captivate Android Development] daskanda:
You sir, need to do alotttt of reading
[Captivate Android Development] sixstringsg:
PM me if you want to test a ROM. A CM9 kang specifically.

Edit: no more, I had someone test it for me.
[Captivate Android Development] baghera1979:
Pm sent

when you tell someone something, it depends on what part of the united states you're standing in as to just how dumb you are--- Burt Reynolds
[Captivate Android Development] scottcwhite:
Practice this until you get it before doing anything else
[Captivate Android Development] rotman253:
I'm using SGS with the ICSSGS rom , do I need the Captivate version?

thank you
[Captivate Android Development] prbassplayer:
If you have a i9000 then you need i9000 kernel.
[Captivate Android Development] sixstringsg:
If you own a Captivate, you flash the Captivate kernel.
[Captivate Android Development] rotman253:
so... no icy glitch for me than?

I've tried it but home button is not functioning and the landscape/portrait is opposite to the phone status.

can you please recommend a good kernel to work with my ICSSGS rom?

Thank you...
[Captivate Android Development] shaker2k:
Are you sure you have the correct ROM for your phone. did you mistakenly flash a ROM for the i9000 and not the captivate?

It can be a bit confusing you can have i9000 bootloaders on a captivate. but you can't put an i9000 ROM on your captivate.

Please correct me if I'm wrong.
[Captivate Android Development] rotman253:
I'm sorry if I wasn't clear... I don't have captivate , I have the I9000
[Captivate Android Development] shaker2k:
Oh well your in the captivate forums. You might want to go to the i9000 forums,
[Captivate Android Development] sixstringsg:
You should probably check your own forum before asking these questions. There is a separate thread in the i9000 forum.
[Captivate Android Development] rotman253:
sorry , just saw it.

cheers.
[Captivate Android Development] b-eock:
We have had some real trolls on XDA today, I see them in a lot of threads!
[Captivate Android Development] leezrd:
+1
[Captivate Android Development] TheSoaresan:
Lol I think that guy was genuinely confused about what works and what doesn't between i9000 and captivate
[Captivate Android Development] scottcwhite:
Gotta admit that once upon a time I was ten times as confused about the exact same situation
[Captivate Android Development] leezrd:
I once got scared when voodoo partition sound came on and thought my phone was ruined ... Lol
[Captivate Android Development] Slayer_b:
Could someone post LiveOC settings you using on b3 kernel?

I'm interested in percentage of LiveOC, int and arm voltages, governor.

I'm stable on 1200 Mhz+110 % Live OC, int voltages are default, GlitchOnDemand.

ARM:

100 975

200 975

400 1050

800 1100

1000 1175

1200 1275

When I'm overclocking to 112% my buttons stops working :eek: touchscreen is working as it should.
[Captivate Android Development] sixstringsg:
There's an entire thread linked in the OP that can help you answer your question.
[Captivate Android Development] jayRokk:
Any support for Dark Knight Rom?
[Captivate Android Development] voldomart13:
Any chance that the next beta will have the touch cwm? ide like to be able to use the screen and save my buttons lol

Nevermind i thought it was available for i897 disregard this...
[Captivate Android Development] sixstringsg:
Touch CWM hasn't come to the SGS line last I checked.
[Captivate Android Development] JimmyD_92:
I have discovered the capacitive buttons will navigate in recovery. It's way easier than dealing with the side buttons.
[Captivate Android Development] ruagun:
i would love if the kernel could be ported to run on the dark knight rom it just makes it boot loop
[Captivate Android Development] TheSoaresan:
+1. .
[Captivate Android Development] Tk-Glitch:
Captivate beta 4 is up !

Go get yours from here :

http://androtransfer.com/tk-glitch/CM9-kernels/Glitch/Captivate/CM9-captivatemtd-Glitch-V14-B4.zip
[Captivate Android Development] sicmadek:
Changelog?
[Captivate Android Development] Tk-Glitch:
What about the changelogs button in the op ? ^^