yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] drawde40599:
SoD

Had a few SoD I WAS overclocked to 110% 400/1100 no deep idle default gov led on 60sec no UV . Happened 3 times . Went back to 100% default settings and happened agn . Removed nstool app ( cause it didnt happen b4 i found out about that great app ) and hasn't happened since .?? To early to tell if/ Y it was the app itself but no issue since . Not complaining!! Just putting some info out there . AOKP build 27 - latest glitch version, latest nstools

Im running 400/1000, no nstools, glitch app is installed but not using it, I will see if happen agn ill drop to default min if dose see if ....
[Captivate Android Development] mindphaser2k9:
You need to play with voltages, try to increase first.
[Captivate Android Development] drawde40599:
Ya maybe?? I was reading that was fixing others issues but looks like stock voltage is Samsung stock no? And me having 400 for my min I don't see y that would fix? Didn't have any SoD till nstools was installed so from personal experience ( crack flashing addiction since 2009: )) always undo in order u did before problem ..... care to share your voltage with me? Cause this most likely my next step, and are we raising all freq voltage or just one? Wifi was off btw so not like other guys issue ^^ that link is just for OC? No? I'm stock atm
[Captivate Android Development] ThisWasATriumph:
Well I found a pretty simple fix for this... I just set it to turn wifi off with screen off. Working like a charm so far.
[Captivate Android Development] thangphysk48:
I have problem with backup/recovery. It seem tobe hang at backing up data.

With default recovery, everything work fine.
[Captivate Android Development] RootTheMachine:
This seems common lately. Try wiping cache

Sent from my CM9 ICS i897 Captivate
[Captivate Android Development] sixstringsg:
We're testing a version with this fixed.
[Captivate Android Development] tkjeeper:
I backed up using b5 while on aokp this am. Couldn't do it on fusion. Not sure if restoring would work, but the backup didn't hang and completed successfully.

Sent from the frozen tundra known as Canada.
[Captivate Android Development] sixstringsg:
It doesn't always work, and not for everyone. I haven't heard of issues restoring, just backing up.
[Captivate Android Development] RootTheMachine:
Sometimes there are just issues mounting /data in general

Sent from my CM9 ICS i897 Captivate
[Captivate Android Development] thangphysk48:
Wipe cache doesnt matter. I've try several time already.

Some time it stuck at backing up some txt file.
[Captivate Android Development] topiratiko:
I ONLY have issues restoring. Error can't mount data. Run again an its fine

Sent from my Galaxy S Captivate on ICSSGS 4.2 w/IcyGlitch v14b3
[Captivate Android Development] thangphysk48:
Easier if next time you try to wipe data before restore.
[Captivate Android Development] bondarun:
I went back to Stock THS build kernel and my sleep death is gone..
[Captivate Android Development] mikel.canovas:
Did you have DIDLE enabled? DIDLE + wifi = sleep death for many users. DIDLE in general can cause sleep death for some devices.
[Captivate Android Development] capocaccia:
I get sleep death and charge death with 0 modifications to icssgs rc 4.2 or settings besides the glitch kernel. Been using it since the day of release. I think it's just going to be a symptom of the beta were going to have to deal with for now.
[Captivate Android Development] kafepuya:
I looked at the Live OC/Custom Voltage Guide by Tk-Glitch as well as the FAQ in the OP, but I am not able to find a guide on choosing IO Scheduler or Governor. Back when I had GB roms, I would use Thunderbolt! scripts, and Pikachu01 had a guide on choosing both. I'm just wondering whether such a guide exist, and if it does, where can I find it.
[Captivate Android Development] scottcwhite:
Run FIOPS and GlitchassV2. You'll be happy
[Captivate Android Development] Keland44:
just in case you guys didn't see this http://rootzwiki.com/_/articles/kernels/kernel-devs-force-ac-charging-through-any-source-r500

i found it pretty interesting

sixstrings can you filter that up to glitch
[Captivate Android Development] sixstringsg:
The Galaxy S devices already charge at their fullest potential from what we can see.
[Captivate Android Development] Keland44:
oh okay good stuff
[Captivate Android Development] RDI:
If you charge Samsung Galaxy or Tab from any USB source it will read "Charging USB ", even if that source is 2100mA. It will not charge at its maximum. Samsung chargers "short" the data pins. This tells the Samsung device it is okay to draw its maximum. They will say "Charging AC". Some eBooks also use the Samsung "style" charger.

Sent from my SGH-I897 using ICSSGS RC4.2 with Icy Glitch v14b5. OverClocked with No-Frills CPU Control (1500MHz). Very easy, very stable.
[Captivate Android Development] mrsubway:
Where is B5?
[Captivate Android Development] elwilson4:
The link on the OP that says B4 is linked to B5 kernal. They just didn't update the text for the link.
[Captivate Android Development] Time_Zone:
FWIW. I was able to solve my charge death problems by increasing all my voltages by 25 points.
[Captivate Android Development] Gromlakh:
I believe it's located at the fifth Lagrangian point between Epsilon III and its primary moon, somewhere in the Epsilon Eridani star system.
[Captivate Android Development] grndnl:
Hello, I I have the sleep of death problem as well, after flashing V14b5 on RC4.2 and turning on DIDLE.an anyone explain a little more in detail how do I get out of this sticky situation? thanks in advance...
[Captivate Android Development] mbc663:
Yea, turn off didle
[Captivate Android Development] ChuckDaEngineer:
Disable Didle. I haven't been able to run it in any kernel, platypus or glitch.
[Captivate Android Development] grndnl:
Yeah, but how do I wake up my phone?
[Captivate Android Development] bimmernut318:
Pull the battery
[Captivate Android Development] grndnl:
I have taken the battery out, put it back in, tried to boot it with multiple button combinations because why not. but nothing. I have not tried plugging into a laptop yet, because I'm not near one, but if you think it will help I will wait for that. is it possible that the battery is completely dead?
[Captivate Android Development] bimmernut318:
There is that chance, does it even try to power?
[Captivate Android Development] prbassplayer:
Sounds like a hard brick or a very dead battery....
[Captivate Android Development] scottcwhite:
Have you tried putting a jig in and seeing if it will go into download mode ?
[Captivate Android Development] grndnl:
I don't have a jig, but basically the problem was that I was trying to charge it with the dock, and it wouldn't display anything. If I charged it with the cord it charged fine. the battery was completely dead, that's why it would not turn on when I pulled the battery.
[Captivate Android Development] grndnl:
Hey guys, so I flashed this kernel last night and had DIDLE on, and got a sleep of death. this is the battery stats. how is this even possible? It charged to 100% fine afterwords..
[Captivate Android Development] b-eock:
Turn off didle it causes sleep of deaths now
[Captivate Android Development] sixstringsg:
It doesn't always cause sleep of deaths. It has the potential to cause sleep of death.
[Captivate Android Development] thangphysk48:
I saw that more often happen when wifi is on. With wifi off, it less than.

But, anyway, better if we turn it off.
[Captivate Android Development] electech13:
Quick question about a Glitch advanced kernel option in cwm recovery. When to use the clear battery stats option? I assume this might be good when recalibrating a battery?

Thanks.

And amazingly enough this glitch is able to run on some 4.0.4 roms, much to my surprise. I know anything can happen and not supported but lovin' it so far!

Sent from my SGH-I897 running Glitch v14 b5 @1.785Ghz stable: ICS 4.0.4
[Captivate Android Development] RootTheMachine:
The phone automatically does that after being fully charged and unplugged

Sent from my CM9 ICS i897 Captivate
[Captivate Android Development] gabby131:
I can tell that when wifi sleep policy is set to "Never", sleep deaths occur. There is also a possibility of the Sync accounts, specially google calendar, that may result to SoDs. Proven by replicating the issue....my Cappy did not experience SoDs since I installed cm7 and custom kernel.
[Captivate Android Development] sinichi21:
Just want to say I think I fix my didle SOD by using a I9000 bootloader Im not having any sod at all even my wifi is on with didle on :) . I did a fresh flash stock jf6 and master reset flash I9000 bootloader and flash M4 then glitch so far no sod wifi and Bluetooth on with diddle on. I just can't get the Top=off to work it shows 0 on the idle stats but the top=on is working
[Captivate Android Development] Boomgawd:
top off will occurs if Bluetooth is off.

For those with sleep death, please try glitchassv2. I am on slim ics 2.8 and with glitchondemand scheduler I get sod with glitchassv2 I dont.

This was true when on teamhacksung build 16 as well.

For me this is repeatable every time. No matter if wifi or bt or diddle is on..

I get both top on (if bt enabled) and lots of top off when bt disabled.

That's my 2 cents..
[Captivate Android Development] apg5031:
doesn't work.....
[Captivate Android Development] grndnl:
hey so is there a fix for BLN not working on any ICS ROM out there with the latest build?
[Captivate Android Development] sixstringsg:
Yup, patience. It will be fixed soon.
[Captivate Android Development] electech13:
OK if so then what is the purpose of the clear battery stats option in the Glitch Cwm recovery kernel setting? I it must serve a purpose. Only good if battery level misreporting? No good for calibrating? Would love to know. Thanks

Sent from my SGH-I897 running Glitch v14 b5 @1.785Ghz stable: ICS 4.0.4
[Captivate Android Development] sixstringsg:
It is not specific to the Glitch CWM. It is in all versions of CWM, and it is absolutely useless.
[Captivate Android Development] ninjah:
Excellent, works for me
[Captivate Android Development] Javier.San1993:
+1
[Captivate Android Development] sinichi21:
Finally got my top=off to work it seems that I needed to modify my framework for the didle to work, I have tried to enable the screenscaling but it seems it does not make the didle to kill the bluetooth on sleep but after editing the framework everything start working as it should so happy with milestone 4 now :D. Thanks again six for the aokp milestone4 its really the best rom for me and tk-glitch for the kernel making all these smoothness possible.
[Captivate Android Development] Monfro:
Can you please post the link to the bootloader that is working for you?

So we can all test it and report if it is a solution for all
[Captivate Android Development] telefantastik:
I'm choosing "enable screen state scaling" in cwm and using "powersave" for sleep modes. Sometimes when turning on the screen/unlocking it gets stuck in powersave and is quite sluggish. The way to fix it for that wakeup is to manually switch governor in nstools to something correct.

Did anyone encounter this before? I'm on team hacksung's cm9.
[Captivate Android Development] bryman27:
Could you please tell us what you edited in the framework?
[Captivate Android Development] sixstringsg:
Powersave is a very bad idea for screen-off. It keeps your CPU at 100mhz, so everything takes forever. Also, we haven't quite worked out the bugs with NStools and screenstate scaling. NStools handles governors differently than Voltage Control did.
[Captivate Android Development] telefantastik:
Oh ok, so overall it sounds like it's best to keep screenstate scaling off in CWM for the time being?
[Captivate Android Development] Wakamatsu:
I had a problem with the Play Store that may be Glitch related. I'm running it with Slim ICS 2.8. I kept getting "Your device isn't compatible with this item" notices on certain apps (Superuser and Adobe Flash were two of them).

I cleared cache and data from recovery but the error kept occurring

I reflashed the ROM, then Glitch, then accessed the Play Store. Same thing.

I reflashed the ROM then accessed the Play Store. Problem is gone. I then flashed Glitch. This time, everything is okay.
[Captivate Android Development] sixstringsg:
There is no realistic way that a kernel can impact the market. Especially since your issue isn't reproducible.
[Captivate Android Development] Wakamatsu:
I wouldn't think so but it's the only thing I can think of. I tried playing around with screen resolution, etc. I actually reflashed Slim/Glitch twice and got the same problem. Then I flashed Slim by itself, accessed the market then flashed Glitch.

In any case, problem gone.
[Captivate Android Development] scottcwhite:
It is the ROM not the kernel. On ICSSGS with glitch it sees my phone. On slim with glitch even YouTube shows my device not compatible. I just put the old market back on and was done with it. Same damn thing anyway.
[Captivate Android Development] electech13:
I too have started getting your device is not compatible message in the newer play store market with certain apps and I know it's definitely the rom. I'm currently on. DARK KNIGHT 3 and I'm curious if there is a market fix instead of a reflash for a solution? Install old version? Or different market.apk file? Would love a work a round.

Sent from my SGH-I897 running Glitch v14 b5 @1.785Ghz stable: ICS 4.0.4
[Captivate Android Development] sixstringsg:
You'll have to ask your ROM dev what they broke, it could be any number of things that is making it not work right.
[Captivate Android Development] :
I've encountered this market problem (device is not compatible) several times and the fix I used was changing the dpi to 240 and clearing market data, sometimes doing it several times did the trick, then changing back to my desired dpi, the issue is definitely not kernel side, it would have happened before if it was
[Captivate Android Development] sinichi21:
Somewhere on bools the one on bluetooth adapter something cant recall the name lolz which is true make it false not on my computer so cant look at it now. But be aware when you do this sometimes it causes some phone wifi and bluetooth instability.
[Captivate Android Development] bryman27:
Found it. It's config_bluetooth_adapter_quick_switch for anyone else who's wondering. I'm gonna test it out.
[Captivate Android Development] anarche:
I've flashed this to my Captivate that is running the latest CM9 Build 17 and now I'm just getting constant reboots back into Glitch CWM. I've tried searching this thread as well as the rest of the forum but can't seem to find any explanation for it.

Sorry for such a lack of details, but if anyone has any suggestions it would be greatly appreciated. Before I flash back to a different kernel, I'd like to try to get this one functioning.

Thanks in advance.

-AnarchE
[Captivate Android Development] drawde40599:
Happened to me after undervolting put back to stock voltage it came with and hasn't happened since . ( is this your fix??? Dunno, but thought I'd share what happens to me
[Captivate Android Development] sinichi21:
Here is the I9000 jvt bootloader and Odin that I am using right now unzip it and flash the md5 file using odin on PDA slot. DO NOT FLASH THIS straight on ICS rom GO BACK to stock then flash it and after flashing it flash any ics rom you want.

NOTE: Flash this at your own risk I won't be responsible for any paper weight phone if it fails on your phone we know bootloaders looks harmless but when it fails your screwed especially if you can't go to download mode or recovery mode
[Captivate Android Development] apg5031:
but where do i go to edit this?
[Captivate Android Development] anishz:
I think flashing on ICS may cause problems as ICS roms use different partition format and not RFS used by Samsung. As these bootloaders are made for Samsung RFS partition i would suggest flashing to stock first.

Though i may be wrong, please correct me if so.
[Captivate Android Development] vibranturk:
ı know anish is right, ics uses mtd file system, gb samsung roms uses rfs(can convertable ext4)

Flashing over ics a bootloader may cause screewing and this maybe cause a not simple soft brick... I believe At least must go a stock rom for flashing bootloader reduces risks ...
[Captivate Android Development] akajunior:
I am running this kernel v 14 B4 with the hacksung CM9 ICS build 16....pure awesomeness.!! I have not a a single complaint. Of course I'm waiting for the rest of the ICS features to be added, but besides that, I'm psyched! great combo, would recommend to EVERYONE!! Everything works as it should. FAST, fast...fast! Battery last all day, in a building that B4 now has had crappy reception. I now get 3-4 blue bars and 3-4 blue WiFi bars as well. Even using this phone all day while working, Facebook, even! GReat, great..great! I cannot praise enough this setup! THANK YOU GUYS!! my captivate hasn's runthis well EVER! :cool:
[Captivate Android Development] apg5031:
Didle

Okay, so these are my steps so far.

downloaded apktools

uploaded the framekwork-res file on my computer

edited the bool bluetooth....to false

copied back to the phone

used root explorer to paste in into root folder

once i paste it...the phone restarts automatically and it freezes on boot animation...

any other way to get this framework-res.apk file pasted?
[Captivate Android Development] bryman27:
You could push it with adb while your phone is in recovery (and change its permissions). The commands would be:

adb push path/to/framework-res.apk/on/your/computer /system/framework/framework-res.apk
adb shell chmod 644 /system/framework/framework-res.apk
[Captivate Android Development] sinichi21:
Thanks for clearing that up edited the post flash to stock first :D
[Captivate Android Development] sinichi21:
BTW I have question about lazy governor im trying it right now since i heard that its a good combo on didle now if i set the screen off max frequency to on what does it benefit me? Does that mean my phone is always max frequency even on off?
[Captivate Android Development] Sword_of_a_1000_truths:
can i get a mirror to latest please, been trying to download from link in OP for a couple days and never connects to the site. this has always been a great ICS kernel for me and i want to use it again as i flash all the ICS roms
[Captivate Android Development] krufttangoud:
Back up issues

FYI, I have read in some threads about difficulty running nandroid backups. I tried a a bunch of different remedies that didn't work. No matter what it would hang on "Backing up Data." So in a desperate attempt I mounted Data before running backup. That seems to work. I don't know why. But if you want to get rid of the issue, there you go.

Edit: Looks this was a random one time fix. I have heard it helped some, I have tried it five times already and I am still locking up. Sorry guys.

Edit Edit: Try reboot to OS, reboot to recovery, wipe cache and Davlik, mount /data. Probably random, but it worked the first try.
[Captivate Android Development] sixstringsg:
Androtransfer is back up to the speeds you all know and love. If you want to know more about why, read on.

So, I've always been quite an open developer, so I'm going to explain what's been happening. Outside of Glitch, stevespear46 and I have been working on adding more open-source support (Such as Gummy, CNA, and AOKP) to the Galaxy S line. That, combined with already high downloads of this kernel (~18,000 per release last I measured) and other developers that I host for, creates quite a bit of traffic. Specifically, 5.25TB so far this month, and it's only the 12th. My hosting company (currently OVH) didn't inform me of this, but instead capped my bandwidth to 8mb/s, which was problematic considering the server runs at 125mb/s pretty much constantly. So, what's being done to fix it: recently I was donated a server by bytemark hosting for first of all a buildbot, but secondly for hosting (for more information see http://glitchteam.com) I do not have bandwidth caps with them. Therefore, every android file for anything I host will be automatically mirrored between two dedicated servers until at least when my OVH lease is up.

What this means for users: If you are a ROM dev that needs hosting, hit me up, I can help. For regular users, downloads will only be limited by your internet connection, never by the server. Which means, I can download a ROM on my connection in 32 seconds.
[Captivate Android Development] b-eock:
Just checked the beta testing section and it is still slow. It always loads in an instant IDK why it is being slow for awile...
[Captivate Android Development] juanzr1:
When playing a YouTube video from the app, you can only hear the sound and not the video, idk if its a problem with the milestone rom I'm using or if glitch kernel is causing this problem
[Captivate Android Development] tbrummell:
It's not Glitch, YouTube works fine for me. I'm on Gummy. :)
[Captivate Android Development] abenn26:
Hey, just flashed icyglitch v14 onto DK3 and its been fantastic but for some reason i can't boot into recovery. I am trying to recover from an unstable nstools OC setting that freezes then restarts my phone. For some reason i can voldown+power to go into recovery. Also I can't usb+vol up & down to recovery. Am I doin it wrong?

nevramind, fixed it. Not sure how I got to recovery but I did.
[Captivate Android Development] drakester09:
Bro, thanks! This allowed me to enable Deep Idle without Sleep Death.

+1 on this as a fix for DI+SOD.

This is VERY RISKY, you can HARD BRICK your phone! Do NOT attempt unless you know the risks and dangers and are willing to accept them.

Also it won't work if you flash on ICS, you MUST go back to stock. I used I897UCKI2 with no BL and Boogs Kernel (has CWM).

Otherwise you'll end up in recovery ALL the time.

Adding caps for emphasis, it's not something you should attempt if you don't know what you are doing.
[Captivate Android Development] Darth_Munkee:
I just wanted to piggyback on the bootloader topic. I decided to flash GB bootloaders the other day but I was in a hurry and didn't think it through. I flashed from Odin with it in the PDA slot like you're supposed to but I was still on CM9. I was only able to boot into recovery afterwards. I had to flash a stock GB ROM, then CM9, then do a nandroid restore. I got lucky that the fix was relatively easy. BE CAREFUL WITH BOOTLOADERS!

Sent from this fully armed and operational battle station running ICS.
[Captivate Android Development] sinichi21:
Good to hear that it works for you. If you guys are having trouble with the top=on you need to edit the framework for it to work wish we can hear more feedback on the bootloaders if it work or not so we can confirm if it really fix it but anyway glad to help :D
[Captivate Android Development] :
Thanks sinichi your fix with the jvt bootloader finally allowed deep idle to work on my phone. The top=on works without framework changes on my end (using tsunami ICS framework on official AOKP)
[Captivate Android Development] rjyanj:
Recovery = Vol up + Vol down + Power
[Captivate Android Development] apg5031:
can you provide more detailed instructions on how to do it.

I dont mind testing it on my captivate.

I am currently on ICS CM9 Build 17 with the stock kernel.

It would be great if you can give me step by step guide on how to go about making this work.

Starting from what Stock ROM to use....

;)
[Captivate Android Development] RDI:
Problem running Chase Bank app. All is okay until I try to use the "deposit a check" function, this takes pictures of front and back of check. (This is a function built-in the app) As soon as I snap the first picture, it throws me out of the app.

Sent from my SGH-I897 using ICSSGS RC4.2 with Icy Glitch v14b5
[Captivate Android Development] sixstringsg:
Have you checked stock kernel?
[Captivate Android Development] scottcwhite:
Why not long press power button to turn off, select reboot, then select recovery. Or had you tried that also ?
[Captivate Android Development] ninjah:
what about battery life with i9000 bootloader?
[Captivate Android Development] mbc663:
Bootloaders have zero effect on battery.