yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] ThisWasATriumph:
If both the 100mhz and 200mhz steps are set to the same voltage, is there any reason to have the min freq at 100 vs 200?
[Captivate Android Development] mikel.canovas:
Another great update, thanks for the hard work six and tk!
[Captivate Android Development] scottcwhite:
Downloading now. Thanks
[Captivate Android Development] sixstringsg:
In my opinion, not really.
[Captivate Android Development] Tk-Glitch:
At same voltage, two times higher frequency will use more power. Add to that the GPU does run @ 200 MHz on 200MHz CPU step (versus 100MHz on the 100MHz CPU step), using more power as well, and reducing the lifespan of the chip when in sleep. Doesn't look like the best idea to me.
[Captivate Android Development] ThisWasATriumph:
Well I'm not sure if this is the cause, but after flashing beta 4 I noticed my wifi dropping connection and reconnecting in under a second about every 10 seconds... Anyone else have this issue?

Edit:Scratch that, AOKP issue not kernel.

Ah I see thanks.

The sleep-deaths are strong with this one. :(
[Captivate Android Development] herofmm:
I just flashed V14 beta 4 on ICSSGS. I experience death on sleep triple times. I set 1200 GHz for max frequency and nothing else. Tried both Glitchondemand and SmartassV2. Now I'm gonna go back to beta 3. Beta 3 was quite good.
[Captivate Android Development] Tk-Glitch:
@ everyone :

Wifi + DIDLE = SoD it seems.
[Captivate Android Development] ThisWasATriumph:
I didn't have didle enabled...
[Captivate Android Development] sixstringsg:
Did you intentionally disable it? Because it boots with it enabled.
[Captivate Android Development] ThisWasATriumph:
It wasn't checked in Nstools that I remember...huh well I'd check it again but I'm back on stock kernel now.
[Captivate Android Development] herofmm:
My first two SoD happened when not on Wifi. I don't remember about Didle. I put it default.
[Captivate Android Development] Tk-Glitch:
Other devices aren't suffering from this, so probably something to do with latest THS source update. If someone can provide me a logcat I'll be thankful.
[Captivate Android Development] ThisWasATriumph:
Just checked again. Default was off.
[Captivate Android Development] dohboy15:
I'm using nightshacks Miui V4 cappy port and Glitch 14 B4, and I haven't had a sleep of death yet
[Captivate Android Development] Tk-Glitch:
Yeah it is supposed to be off by default. Six was mistaken ^^
[Captivate Android Development] RootTheMachine:
I'm still getting occasional lockscreen lockups. I haven't experimented with deep idle yet, will do some tests.
[Captivate Android Development] ThisWasATriumph:
Logcatting now but it hasn't died while plugged in so that might make it hard to diagnose haha.
[Captivate Android Development] billyjed:
On b4 Didle off max 1320, min 220 liveoc 111% same settings as with b3. Sleep death every 10 minutes. Can't reboot, I have to pull the battery. Back on b3. Thanks.
[Captivate Android Development] herofmm:
I got the logcat, but it is too long and contains my personal info. Which part should I take? Can you give me some keyword or something like that? BTW, I'm back to beta3.
[Captivate Android Development] tkjeeper:
yep, two sod's for me on wifi both times, running beock's ics rom. back to b3, thanks. no didle, oc'd to 1400, no voltage changes
[Captivate Android Development] golfslicer:
After flashing b4, the phone shuts off, goes into such as sleep when it is not on the charger and I have to pull the battery to get it to power back on. Reflashed b3.
[Captivate Android Development] sicmadek:
the op hadnt changed when i posted that
[Captivate Android Development] sixstringsg:
In the OP, there is always a link to the changelog from the i9000 thread. That is what he was referring to. Tk always updates his thread first, then I update mine. Depending on how busy I am, it takes more time than others, but his thread is always up-to-date.
[Captivate Android Development] vcallas:
Same results here, am back to b3.
[Captivate Android Development] pickupman66:
Same here too. Flashed to b4 and restored settings from file in ns tools. Sleep death at first blank screen both with didle and without. No overclocking just lowered voltages. Back to b3 for me. Running the fusion ics from collective.
[Captivate Android Development] :
I've been getting consistent charge death on the latest kernel, never happened before on any kernel. Had SOD with didle on previously so stopped using it, anyway back to beta 3
[Captivate Android Development] sinichi21:
I have notice that I only get the lockscreen delay when i have my wifi on, when its off it works just fine so far no SOD or COD running on stock mode didnt touch any config on nstools
[Captivate Android Development] acras:
B4 with CM9 B16 (and KANG) - can't load OS, just stuck in kernel logo. Tried removing NSTools settings using kernel option - the same kernel logo. Back to B3.

Upd. It was screenstate scaling enabled in CWM causing the problem. I disable it and phone boots. DIDLE causes SoD for me even with default voltages.
[Captivate Android Development] sixstringsg:
A) glitch hasn't built a CM9

B) if he had, this wouldn't be the thread to report.
[Captivate Android Development] topiratiko:
Is anyone NOT getting sod?

Sent from my Galaxy S Captivate on ICSSGS 4.2 w/IcyGlitch v14b3
[Captivate Android Development] zuN!:
I'm not.

TeamHacksung's build 16, Glitch v14B4. LiveOC'ed to 120%.

No issues whatsoever.
[Captivate Android Development] pintek:
No SOD or "charge death" here though i don't use a dedicated charger for my phone i use a powered USB hub with factory cable
[Captivate Android Development] Tk-Glitch:
I'll revert latest THS changes. That should fix the SOD problems. I'll then upload B4.1.
[Captivate Android Development] TheSoaresan:
Hmm I didn't get any sod or cod but its extremely laggy after an hour of use...reverted to b3 till 4.1 comes out
[Captivate Android Development] Tk-Glitch:
Beta 4.1 pushed to supposedly fix SOD issue.

http://androtransfer.com/tk-glitch/CM9-kernels/Glitch/Captivate/CM9-captivatemtd-Glitch-V14-B4.1.zip
[Captivate Android Development] ptesmoke:
on ths build 16. no sod or cod runs smooth as butta. live oc at 110
[Captivate Android Development] Tk-Glitch:
@ ptesmoke

Not everyone will have this SOD issue. I don't ^^

No need to update if you don't have the issue btw.
[Captivate Android Development] antiochasylum:
Fixed SOD on my step child captivate with 14.1
[Captivate Android Development] ptesmoke:
sorry boss! seemed everyone was having sod and cod so i thought id let u know i wasnt! B-) cheers buddy and thnx for all your hard work!

if beta4 is working fine for me am i missing out on anything from the latest 14.1 or beta4.1 whichever you are calling it?
[Captivate Android Development] Tk-Glitch:
@ ptesmoke

No you don't :)
[Captivate Android Development] jecsah:
I'm on the latest CNA and I flashed Glitch 4 last night. I charged to 100% (with Lazy and didle on and no OC or voltage changes) unplugged and went to sleep.

Just woke up to a completely dead battery that will not take a charge at all, its dead. I had a spare battery that I put in and that one works fine, so it is a battery issue. Any ideas on what would have caused this? Kernel related or an extreme coincidence?
[Captivate Android Development] sinichi21:
Did 14.1 fix the lock screen delay?
[Captivate Android Development] antiochasylum:
It did on mine. Haven't had "unresponsive touchscreen" since flashed 14.1 this morning. Finally running awesome. Sad I have to sell it :(
[Captivate Android Development] Koizuma:
14.1 fixed the sleep issues for me thanks for the fast fix on the sleep death issue :)
[Captivate Android Development] brettchuck:
Same here. Back to B3.
[Captivate Android Development] mindphaser2k9:
I don't have any death issues with beta 4 (not 4.1): neither SOD nor COD. Works like a charm :) Do I need to flash 4.1?
[Captivate Android Development] Tk-Glitch:
No you don't :)
[Captivate Android Development] apg5031:
does this glitch have BLN control?
[Captivate Android Development] Tk-Glitch:
No it doesn't. It does have CyanogenMod LED notifications.
[Captivate Android Development] Keland44:
installing b4.1 good work glitch

updated*******

anybody using wifi tethering?

i'm on cm9 b16 running notice i'm getting sleep of death with sio/smartass v2/800 max/liveoc 100%
[Captivate Android Development] apg5031:
where do i go to turn that on?

i dont see any app or anything......any ideas?
[Captivate Android Development] daskanda:
Settings -> display -> pulse notification light
[Captivate Android Development] apg5031:
no doesnt seem to work...i tired that already.....

i have the Europhia rom on my captivate.
[Captivate Android Development] sinichi21:
That rom is base on aokp I believed aokp does not support it
[Captivate Android Development] prbassplayer:
AOKP doesn't support it. They use Semaphor that does support BLN.
[Captivate Android Development] tallsilver:
4.1

Running Vibranturk's AOKP with Glitch. B3 worked great. B4 had SOD. B4.1 seems to be working great at 1300Hz no undervolting.

Thanks Dev!!:D
[Captivate Android Development] drancid:
having COD on both B4 and B4.1. revert back to B3.
[Captivate Android Development] tkjeeper:
No sod here! Woohoo

Sent from the frozen tundra known as Canada.
[Captivate Android Development] Tk-Glitch:
The issue is known and supposed to happen even on stock CM9 kernel btw
[Captivate Android Development] :
COD is fixed on beta 4.1. Thank you very much Tk-Glitch. Mind if I ask what did you change to fix the issue?
[Captivate Android Development] drancid:
Hmmm.. let me try again w/o uv settings. thx ;) love glitch kernel!!
[Captivate Android Development] Tk-Glitch:
Reverted this commit : https://github.com/teamhacksung/samsung-kernel-aries/commit/b1ab6bb826b19755d9a1bc4906972a3ef70f7045

Now we know why the Nexus S kernel doesn't have this :p
[Captivate Android Development] ThisWasATriumph:
Figured this out as well. Wifi seems to be broken as it's connecting and disconnecting rapidly for me. Do you happen to be on AOKP? I think its a rom problem.
[Captivate Android Development] sinichi21:
Im on THS build 16 when I type that but before that i was on aokp didnt have that wifi problem but i have the lockscreen delay while i was aokp
[Captivate Android Development] nightshack0:
I found something strange

I've had SOD EVERY night with no exception with all the kernels, then beta 4 on first night didn't have a sod, seems like its the only one working,

I don't know if its a hardware issue on my captivate because I get SODs on stock captivate ROMs, but on CM7 I didn't get them, then with ICS they came back at like build 7 on THS

Haven't tested 4.1 but I don't know why when people report SODs I don't get them but when they don't, I get them

May be just my device ..hope not :(
[Captivate Android Development] ptesmoke:
ok so...on beta4 and 4.1 data stops on stock ics browser on ths build 16. works good for a few mins then wont load pages. other data apps work fine...back to beta3 and browser works perfect....wierd?

oh and this is on 3g not wifi...havent tested wifi.
[Captivate Android Development] sinichi21:
still have some lockscreen delay on b4.1 when wifi is on
[Captivate Android Development] shaker2k:
Yup same here. but no SOD's or COD'S
[Captivate Android Development] Tk-Glitch:
Beta 5 is up !

http://androtransfer.com/tk-glitch/CM9-kernels/Glitch/Captivate/CM9-captivatemtd-Glitch-V14-B5.zip
[Captivate Android Development] shadvich:
Renamed SmartassV2 governor to "GlitchassV2"

Haha, nice. Installing now. Will try wifi with DIDLE.

Edit: wifi with didle locks up my phone rather quickly when left idle, but my phone is rather sensitive to those sorts of things from what I've encountered
[Captivate Android Development] herofmm:
Are you kidding? kkk, thanks a lot~~~
[Captivate Android Development] ThisWasATriumph:
That's ok, its not like I literally just got 4.1 stable or anything. :rolleyes:
[Captivate Android Development] apg5031:
Tk glitch..... its working.... the notification lights seen to be working fine....

Thank u so much....
[Captivate Android Development] pickupman66:
So I tried 4.1 and still got sod when I enabled Didle. I am runningsome pretty low voltages and I'm sure that combo with the didle is the sod issue. What exactly does the didle do for me? I am on 4.1 now with the below volts. No overclock.

Arm-int

1000-1175-1025

800-1100-1000

400-950-975

200-800-950

100-800-950

I get plenty of performance for my needs with this setting. Is activating didle and bumping the volts going to do anything?
[Captivate Android Development] herofmm:
Unfortunately, I am still getting SoD on beta 5. I also had SoD on both B4 and B4.1. I am on ICSSGS RC4.2, and it worked fine with beta 3.

When I got SoD, I just changed Didle-on on NS tools and wifi was on ( However, I was away from my wifi router). I also set "wifi-off when screen off" on system setting.

Do you need more info? I like to provide my logcat, but I don't know how to make. I tried to enable logcat on recovery, but no idea how to see&save it.
[Captivate Android Development] sinichi21:
I have a question about the didle i remember i read somewhere that we need a framework mod for this to work do we still need that mod or it will now work without that mod? mine goes to sod when my screen turn off with diddle on whether my wifi is on or not so was thinking maybe i need that mod? sorry to ask since this didle were all new to me
[Captivate Android Development] sixstringsg:
Are you on GB bootloaders?
[Captivate Android Development] sinichi21:
yes I am on gb captivate bootloaders KK4 to be exact do i need i9000 gb bootloaders for the diddle to work?
[Captivate Android Development] nsyik:
I am on GB bootloader, aokp build 23. Whenever i set didle on, SOD will occur. No OC/UV. Im on Glitch B5. So now i can only set the didle off. :S
[Captivate Android Development] scottcwhite:
I just keep mine turned off. Does it really gain one that much by having it on ?
[Captivate Android Development] Wdustin1:
I don't really know I always have mine off and I get less than 2 percent an hour drain in standby I don't think It can get much better
[Captivate Android Development] pickupman66:
Tried 5. No oc/UV. Turned wifi on and got sod the very next screen lock with didle enabled. Grrr....
[Captivate Android Development] sixstringsg:
No, it doesn't. What people (not you specifically, just in general) need to remember, is Samsung disabled it for a reason. It is not stable on all phones, and even when it is stable, it doesn't help all that much. It doesn't even help everyone, because not everyone listens to music on their phone for extended periods or uses GPS a lot.
[Captivate Android Development] sinichi21:
Im just trying it since they included it. Just giving a feedback and trying things to make it work so far I have not found a way to make it work sod always as soon the screen turns off but yeah i guess samsung cant fix either thats why they left it disable. BLN works like charm though with the bln app thanks for the info six
[Captivate Android Development] demarton:
GB bootloader,

Still SoD when enabling DIDLE.

@sixstringsg: did Samsung official rom didn't have DIDLE enable?
[Captivate Android Development] sixstringsg:
It did not, no. It was included in the kernel source, that's how we have it, but it was not enabled to my knowledge.
[Captivate Android Development] pickupman66:
Thanks for teh info on it. I tried to do some more reading up on the feature and it looked like it could be really useful and could save battery. ill go back to my low voltages and hope that buys me some more time per charge.
[Captivate Android Development] sicmadek:
what is didle? is it enabled by default on this kernel? where do i enable/disable it?
[Captivate Android Development] sixstringsg:
http://xdaforums.com/showthread.php?t=1297535

Use NSTools to enable/disable it.
[Captivate Android Development] scottcwhite:
Didle is P Diddy's 2nd cousin

And also Deep Idle. Use NS
[Captivate Android Development] ptesmoke:
OK so this just started today....mobile data is stuck on H. Doesn't throttle back to 3g. I wiped and reflashed this build 16 and still only see H data constantly. This most likely carrier issue? Anyone on att in Florida relate?
[Captivate Android Development] Slayer_b:
"H" Mean that you are using 3,5G network. It is faster tan 3g but slower than 4G:D

H=HSDPA\HSUPA=High-Speed Downlink Packet Access\High-Speed Uplink Packet Access
[Captivate Android Development] prbassplayer:
Not necessary much faster. If you are on ATT the only difference is upload speed. Download doesn't change. ATT's 3g already runs on HSDPA but has HSUPA blocked for "4g" devices and Iphones.
[Captivate Android Development] ptesmoke:
Yes I know what H is. What I'm saying is it is always H. Before it used to be 3g when Inactive...hoping its att.
[Captivate Android Development] scottcwhite:
I don't have this problem but yesterday after getting home from my hour commute my wife asked if I got her voice mail or texts she sent 30 minutes prior. I checked and hadn't. Tried calling voice mail and nothing. Was just showing grey bars. No "H" or 3g. She dialed my phone again and just got a busy signal. Rebooted the phone and it started working fine again. So this and your problem may be kernel related. I'll see if it happens to me again and if so I'll revert back to b3 as I had no issues with that version.
[Captivate Android Development] techguy615:
Exact same issue here. I flashed it again to make sure and (even went back to stock Rom first) then reflashed Glitch. I am running CM9 alpha (v16). It seems like it just drops the data connection. I show 4 bars that are gray (no H or 3g). I go back in to make sure data is enabled and tell it search for the provider again and it finds the carrier. I am on AT&T as well.

Anyway, thought I was losing my mind and couldn't understand what I had done to cause it. Will watch it today and see if it still happens, but it happened this morning just a few minutes ago. Maybe a network issue for all I know.

Thanks for the hard work again.

Cheers
[Captivate Android Development] apg5031:
feedback

didle on - wifi off = works

didle on - wifi on = SOD
[Captivate Android Development] shuyin1102:
First thanks for this great kernel, working fine on CNA ROM.

Found a problem

: Enable Screenstate Scaling in CWM and the phone stuck in kernel logo.

Captivate Buid 1008

ROM: Codenameandroid 1.4

Kernel : Glitch 14 B4.1

Modem: UGKG3
[Captivate Android Development] krisvek:
You've still got two more states to test! (Diddle off: wifi on/off)
[Captivate Android Development] cheese74:
So I'm running 4.1 on CNA 1.3.3 ROM and hitting a rather strange issue. I can't seem to complete a CWM backup without it hanging while in the /data folder. I switched back to Beta 3 and the problem went away.

I'm running stock kernel settings. So in NSTools, I have fiops scheduler, glitchondemand governor, no OC, default voltages. Earlier I was having SOD issues when I turned on DIDLE, so I have already reverted it to 'off'.

Any ideas why this might be happening?
[Captivate Android Development] ptesmoke:
Still stuck on H. Fresh wipe and flash of the build 16. Tried stock kernel, glitch beta 3 and 4 and 5. Tried changing radios....I have no idea what's going on. It must be att.
[Captivate Android Development] apg5031:
didle off - wifi off = works

didle off - wifi on = works
[Captivate Android Development] krufttangoud:
Updater App Issue

I tried installing V4 and V5 yesterday both ending with a restore. It seems that when I click browse RC, click the version I would like to download then install, it asks would you like to wipe cache, dalvik, etc. As it is rebooting ROM manager asked for SU permission, then the CWM comes up with "preparing to install ROM" and basically does a factory reset.

Sixstringsg said, that the app cannot and does not have any functionality to do that. However, CWM formatted system, data, DataData, cache twice.

Could it be that its a bug with ROM manager? Has anyone had this happen?

I would like to use the app, but once you click install you can't stop the process.

Oh and I did tell it to do a Backup before the kernel installation, but it was corrupt when I went back to restore.
[Captivate Android Development] sixstringsg:
Deep Idle won't always work for everyone, we know that. There is a reason that Samsung disabled it before shipping out their ROM's. It doesn't help near as much as people think.
[Captivate Android Development] nuwan32:
yea im using gingerbread bootloaders.. is this bad? which ones should i use then?
[Captivate Android Development] sixstringsg:
No, GB bootloaders are correct. See my post above yours for more info.
[Captivate Android Development] Nick0703:
I got a random reboot with this kernel and my phone is not O.C, running stock frequency. But beside that everything is working perfectly.
[Captivate Android Development] Nick0703:
I'm confused??!? Isn't deep idle and deep sleep the same thing?
[Captivate Android Development] sixstringsg:
Absolutely not. Why would we have two different names if they were?
[Captivate Android Development] Koizuma:
Had a lunch break so redownloaded and reflashed. So far working smooth will report how it goes after.

Swyped from my SGH-I897 using XDA Premium App
[Captivate Android Development] theyurtingyeti:
No glitch splash?

Just upgraded to build 14 and Glitch v14 B1. I don't seem to have any glitch splash screen like I did last time I used a Glitch kernel. Is this a change or is something wrong?

I get two ATT screens followed by the ICS splash. In "about phone" it lists the glitch kernel so I know it flashed.
[Captivate Android Development] Nick0703:
What's the difference between them two?
[Captivate Android Development] balishared:
thank you!!

i flashed it yesterday on latest miui, no issues except i think my battery is lasting longer. i m using the default settings
[Captivate Android Development] airtower:
I know on the previews you needed GB bootloaders to see the splashscreen. You should get one though, saying ICY Glitch (no more trollface)
[Captivate Android Development] theyurtingyeti:
Thanks!

1) How do I know if I'm on GB boot loaders

2) If I'm not, how do I get on them :)
[Captivate Android Development] airtower:
There's no easy way to tell unless you know you've done it. Not seeing the glitch bootsplash is a good indicator, but that's only based on my own experience. When I was on froyo/eclair bootloaders the old ICS glitch bootsplash appeared severely distorted. Not sure what's changed and if it would cause it to not show at all now.

I only say all that to try and save you the time of one-clicking back to stock GB, because that's what you'll need to do to get the GB bootloaders if you don't have them. Find an odin one click with bootloaders and a CWM injected kernel. Flash it, boot back to recovery, reflash ICS, profit. Although I dont think you can restore a nandroid across bootloaders, but I could be wrong. A tibu restore works fine.
[Captivate Android Development] theyurtingyeti:
Ok, sounds like a potential plan. For the tibu backup, that's one where I backup all apps and system data? I'm only fairly familiar with backup stuff possible through tibu.

Thanks!
[Captivate Android Development] daskanda:
Yes tibu is used to backup apps and system data..... I don't suggest restoring any data after coming from a different rom (system or app).... Restoring just apps without data is okay....It seems to cause problems for me anyways
[Captivate Android Development] RootTheMachine:
I'm also getting reboot with didle. Is there any way to make it stable (like with bumping the min freq or UV)?

Also, can anybody explain the lagfree governor? Seems pretty snappy

Sent from my (CM9) ICS i897 Captivate
[Captivate Android Development] Gromlakh:
I've never had any problems restoring app data from Tibu. Never restore system data across different types of roms (eg gingerbread to ICS), but app data for individual apps is fine to restore.

Sent via Captivate (powered by CyanogenMOD)
[Captivate Android Development] erbsmokah:
So we are calling it CM9 now huh?

Hehe, well good work im going to try it out.