yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] shaolin95:
My advice is....test the CPU using moboplayer in Software mode with a 720p video and then test the GPU with your favorite games. If it passes that, I consider it stable in my book.

If not, back down to 1.5Ghz and do the same test to make sure you are stable at that speed before moving on.

I am seriously considering removing stability test app from my mini OC guide right now. ;)
[Captivate Android Development] SirFunk:
Updater

First off. Gotta say, I love the kernel. It's fast and stable. However, I have a question about the updater I purchased from the market. Is there any way to tell what the latest available version is? will the updater let me know when a new version has been released or do i have to just blindly re-install and hope that it installs a new version?
[Captivate Android Development] sixstringsg:
http://xdaforums.com/search.php?searchid=97611865

Please search before posting. It was literally the second search result.
[Captivate Android Development] tiuk:
Quote from the Glitch thread in the I9000 forum:

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] RichMD:
Better battery life than the stock kernel

FYI on a quick test I did between stock and V13RC. Something had been draining battery fast so I reflashed CM7 158 and left the kernel stock. After running for a day I tried a test of standby. At 86% battery, I left the phone with WIFI on but the screen off for 3 hours. It dropped to 80% so roughly 2% per hour. I then flashed V13RC-HL via the app (after charging). When it dropped to 86% again (without changing any settings, apps, etc) I turned off the screen and left it for 3 hours. It dropped to 83% so roughly 1% per hour. I know this isn't a very scientific test and 3 hours is short enough to make it somewhat inaccurate but this kernel obviously is better on battery in standby with defaults - no OC/UV, etc than the stock kernel. Thanks again for your hard work. :)
[Captivate Android Development] Smasher816:
Market Version updated! (Incase you didn't notice).

And incase you didn't know It brings lots of new stuff.

GUI redo, and a whole lot of new stuff.
[Captivate Android Development] XsceneXhippieX:
Glitch v12b3 boot loops me on the latest nightly, 3 attempts, it probably works fine with r13 that I'm too broke to use yet lol
[Captivate Android Development] sixstringsg:
Checking...
[Captivate Android Development] Raul77:
those who got MiUi , does the latest RC 13 works with BLN (not blinky) ?
[Captivate Android Development] RichMD:
Thanks for the update. I installed it and have installed the latest RC. The only minor problem is that the market keeps showing that there is an update for the app. I click on update and it shows (open, uninstall) as if there is no update.
[Captivate Android Development] sixstringsg:
There is nothing I can do about any market issues youre having. That's all Google. Also, please post in the app thread, not here.
[Captivate Android Development] Gromlakh:
I've noticed the market does the same thing with the Adfree Android app.
[Captivate Android Development] RichMD:
Sorry, I didn't know there was a separate app thread for this kernel. However, I do think this isn't a general market issue - this is the only app I have seen it happen.
[Captivate Android Development] sixstringsg:
There is nothing I can do about the market. I upload the version and the description, set the price and the logos, then save. That is all I do market-wise, and all I can do. If you would like to E-mail the market support page and report the issue to them, you are welcome to. Their average response time is 3 days for the first email, then three days more for a real response.
[Captivate Android Development] tiuk:
Is it just me or does voltage backup not work? I create a backup, name it, then hit manage, and there are none listed.

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] sixstringsg:
Did you have any voltages set as boot?
[Captivate Android Development] tiuk:
I did. I did some more testing, if I don't put spaces in the name it works properly. "Max 1200mhz" doesn't work, but "Max1200mhz" does.

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] sixstringsg:
Makes sense, treats it as two separate entities in the script when there are spaces.
[Captivate Android Development] Doobysnacks:
Market app keeps force closing on me...right after I click yes for the latest rc. I'll keep trying to get it to work because I love your kernel.

I'm on cm7.1.0 and glitch v12.

Just seen the app thread;my bad...
[Captivate Android Development] WillyWonka23:
Is the new kernel layout in recovery changed yet? Or is that coming out in the final release?
[Captivate Android Development] Overgloc:
Dont know if its CM7 or Glicth related but my sound will go out on my Speakerphone or any game i play, the only way to get it back is to lower the volume all the way down and back up again. Reflash kernel and still no go.
[Captivate Android Development] sixstringsg:
We're looking into it.

Final release.

What kernel are you using, and are you using the volume script?
[Captivate Android Development] Overgloc:
v12H with volume script. Will try and take out volume script and see.
[Captivate Android Development] cumanzor:
So is V13 only available for the app owners?
[Captivate Android Development] Koizuma:
Just the RC version of 13 is, but once its fully finished then it will be out for public masses
[Captivate Android Development] sixstringsg:
Correct. It's almost done.
[Captivate Android Development] tkjeeper:
To quote Seinfeld, "it moved"

Sent from the frozen tundra known as Canada
[Captivate Android Development] Smasher816:
Yup. I fixed the error, waiting on sixstringsg to push it. Stupid ProGuard deleted the button functions after compiling. It worked fine on my phone because i used the dev version, when releasing and signing it proguard gets ran. No one noticed because I only used the dev version to test, and six didn't retry that part again on the release version before posting (didn't expect random stuff to break).

Hopefully we'll test it some more so stuff like this doesn't happen. This should be the last bug fix. However, it seems like I can't fix something without something else popping up.
[Captivate Android Development] Javs2010:
Do led notifications work using Captivate just bought it from the market and flashed the latest rc
[Captivate Android Development] sixstringsg:
BLN. and if you flashed the latest RC, can't you just check for yourself?
[Captivate Android Development] Javs2010:
Sry.. Didn't know but I'll deff check it out now
[Captivate Android Development] Raul77:
no one here with MiUi and this kernel ?

Thanks
[Captivate Android Development] sixstringsg:
It should work. Try BLN control first. If it works, then we're good. Blinky is a plus.
[Captivate Android Development] phlunkie:
try clearing cache and data for market in applications/all.
[Captivate Android Development] slayp00n:
BLN works with email but not with handcent sms or on missed calls?

Blinking won't work either.. Gets stuck 'on' when I have no notifications.
[Captivate Android Development] sixstringsg:
What kernel?
[Captivate Android Development] slayp00n:
Your latest RC.
[Captivate Android Development] sixstringsg:
On what ROM?
[Captivate Android Development] slayp00n:
CM 7.1 stable
[Captivate Android Development] sixstringsg:
I just flashed both of those, and blinking works for me. For handcent, you have to make sure that the settings inside of handcent are set to turn on an LED. I know GO SMS works, as well as stock SMS.
[Captivate Android Development] slayp00n:
I had the led light on, but because of earlier kernels I turned it off. Forgot I did. Now I turned it on and everything seems to be ship shape.

Thanks.

---------- Post added at 04:55 PM ---------- Previous post was at 04:53 PM ----------

Nope, same problem still exists... It worked fine for first text, but now I have no notifications at all and lights are still blinking?
[Captivate Android Development] mcala:
In the OP it is stated to try the HL version & if OC/UV works then stay there. What if my chip is a winner and LL works. Since it is posted to stay on HL I may never know my potential. Maybe it should be posted to start with LL then go up from there. Isn't LL chips better or do I have it backward.
[Captivate Android Development] Smasher816:
Repost. Hope it helps...
[Captivate Android Development] sixstringsg:
HL is Samsung default. I only know of one person that can 100% sure run LL entirely stable with a reasonable (above 1.4) overclock. It is possible that some phones won't even boot on LL. If HL gets what you want, but so does ML, then it doesn't matter which you pick.

No kernel is better than the other if you can overclock to a satisfactory level.

They don't save more battery or anything like that. Low Leakage chips are technically manufactured better, they have less acceptable error in them. This makes no difference to us really, because we made a kernel that can accommodate any variety. LL chips don't OC more, or save more battery, they just need less voltage going to the processor than HL chips, because they lose (or leak) less electricity while running.

P.S. Some chips are just bad at overclocking. Our goal is the 1.4-1.5 range on each phone, but that doesn't happen always.
[Captivate Android Development] mcala:
Ok now I get it. HL is like running Samsung stock CPU voltages. If I feel comfortable then I can work my way down from there. No guarantee I could run LL. Got it. Im gonna try playing with ML. I understand now.
[Captivate Android Development] sixstringsg:
Internal voltages, but yeah. None of the leakages are actually unsafe, some might be unstable for you though. But you've got it now.
[Captivate Android Development] Aus_Azn:
So if the leakage level alters the CPU's voltage, wouldn't using LL be more beneficial (despite the probable small voltage change) over H/ML for battery life?

Or is it the other way around/no change at all? Because I just want to aim for whatever's going to give me the best battery life... My phone overclocks fine to those levels on LL and gets very decent UV as well, but I could really care less if the battery life is better on a different one.
[Captivate Android Development] apparition:
Will there be a non-Voodoo colour variant of glitch?
[Captivate Android Development] tkjeeper:
Why bother?

Sent from the frozen tundra known as Canada
[Captivate Android Development] sixstringsg:
The voltage being changed isn't enough to matter battery life wise.

No there wont be.
[Captivate Android Development] CptTwinkie:
Remove please
[Captivate Android Development] spindizy:
Just wanted to let you know I installed this on my miuied captivate, runs at 1.5 fine, 1.7 reboots with HL kernel. And all I have to say is, HOLY CRUCKING FAP! My phone is now retarded fast.

Thank you.
[Captivate Android Development] zuN!:
Does anyone have issues using the volume script on MIUI?

When I was using CM7, I executed the volume script using Script Manager and it worked fine. In MIUI, it says the regular exec at the first two lines (if you try it out you will see), then it's followed by ": not found" 9 times.

Putting it into etc/init.d is screwy and doesn't seem to work for my old phone nor my new one.
[Captivate Android Development] sixstringsg:
I haven't really tested it using MIUI, nor Script Manager. Why doesn't it work in /etc/init.d?
[Captivate Android Development] Thunder22:
Is the volume script zip cwm flashable?
[Captivate Android Development] sixstringsg:
No. Follow the directions in the second post.
[Captivate Android Development] zuN!:
The settings don't stick despite a reboot. I remember posting about this issue before as well and you suggested to use Script manager which worked perfectly on CM7
[Captivate Android Development] Gromlakh:
If the settings aren't "sticking", check the script permissions. If it's not marked as executable, it's not launching on boot and not doing anything.
[Captivate Android Development] tiuk:
Are there any known issues/downsides with using v13rc1 on the latest nightly? Looks like there are kernel changes.

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] Javs2010:
I've been running it on the latest nightly without a problem
[Captivate Android Development] sixstringsg:
All of those changes were in Glitch before they were in the stock kernel, you're good. Except dock audio, that will be in V13 final.
[Captivate Android Development] zuN!:
It's marked as executable under the permissions. The values of the files to be affected (in sys/devices/misc/voodoo_sound) by the script remain the same default values of the script despite numerous reboots (incall boosts remain at 2)
[Captivate Android Development] takerfan:
Do I have to purchase the app to be able to get v13?

I don't see a link anywhere on the front page..
[Captivate Android Development] sixstringsg:
V13 official will be out soon. The RC has bugs in it that we've been working out, and are almost done. Until the official release though, you must buy the app.
[Captivate Android Development] Koizuma:
For the current RC version of 13 the only way to get it is by getting the app, when the final version of 13 is ready it will be available to the public

EDIT: lol beat me to it six
[Captivate Android Development] tiuk:
Thanks six and Javs. I always check the changelog before flashing because I can't stand the stock CM kernel. Never know when some other change might depend on one of the new kernel changes, so I appreciate the reassurance

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] sixstringsg:
No problem. Always happy to help.
[Captivate Android Development] shopealope:
Very nice kernel indeed. Using it on cm7 nightly and I've had no problems with it.

Sent from my Cappy
[Captivate Android Development] nuwan32:
hey guys, is it possible you can add a 600 mhz step for v13? because sometimes i play this mmo called order and chaos and its really battery intensive, so i underclock to 800 mhz when i dont have a charger around so that battery lasts. i know it would work fine with 600 mhz, but 400 is too low, so it this any possiblitiy?
[Captivate Android Development] Aus_Azn:
I'm beginning to get more adventurous with UV: 225 on 100-400 and 200 on 800-1000.

I hope this has a positive effect on battery life, which still leaves my 15-17 hour days with about 15-20% battery remaining at best.

What are the chances of a 600MHz clock being put in? While I don't know if this is a hardware limitation or a software tweak, I ask because it'd be perfect as a balance of battery life and performance... The 600MHz clock allows lower end Android phones (like the HTC Aria) to run decent software, while balancing battery life (for example, Angry Birds does not run with a 400MHz clock limitation, while it does under an 800MHz cap).

Also, what governor do you blokes use? I've been experimenting to see if my usage of the conservative governor has been creating drain that doesn't need to occur.
[Captivate Android Development] nuwan32:
lol wtf did u read my post above or did u randomly ask that because i asked the exact same thing... lol. and theres no hardware limitation or anything its totally possible. infact neo 17 r18 has a 600mhz step, i just dont like it because it doesnt let me uv as far and eats battery like crazy.

as for governor, i use conservative as well, its best combination for power and battery. use it with the v51 script, customize it for your phone depending on ur likes, and itll be perfect.
[Captivate Android Development] Aus_Azn:
I actually typed the post before yours appeared, got distracted, went to do work without refreshing the page, returned, finished it, posted, then saw that you posted the exact same thing. I was thinking "oops".

I use AdrenalineShotVXIX.
[Captivate Android Development] XsceneXhippieX:
How's testing coming along for official (and free) v13 release?

Sent from cyanogen mod 7
[Captivate Android Development] sixstringsg:
Tk has been gone for a few days, and he was mid-change in code. We just implemented a feature that allows you to change the leakages on your own though. It will be another feature in the Glitch menu. I know I've said soon a million times, but right now it's out of my hands.
[Captivate Android Development] XsceneXhippieX:
Thank you for the update! I really do appreciate it, if I had any spare cash I would just buy the market app :)

Sent from cyanogen mod 7
[Captivate Android Development] toy028:
Loving V12 so far! Rock stable on miui running at 1400mhz.
[Captivate Android Development] Fate-Silver:
I tested the Glitch latest DEV kernel on Android 4.0.1 MIUI ROM.

It's still rocking! No problem! :)
[Captivate Android Development] tkjeeper:
Yep, me too! Well, the v12b anyways!

Sent from the frozen tundra known as Canada
[Captivate Android Development] Tk-Glitch:
Someone did steal my luggage, papers and credit card, and since I'm away from home these last days were quite a bit annoying.. I'll be back home in ~10 hours, and I'll then finish the small changes I've planned.

Sent from my glitched GT-I9000
[Captivate Android Development] tkjeeper:
Nice, Bastards!

Sent from the frozen tundra known as Canada
[Captivate Android Development] shaolin95:
Wow mate that is horrible. :mad:

My first suspect is CoreyM....we need to investigate him now! :D

Hope you get everything sorted amigo. ;)
[Captivate Android Development] EnemyOfGlaDOS:
Lol :D your on to me! Currently sippen margaritas poolside wearing an ugly shirt and pants that don't fit! :p

Nah but for real, sorry TK. Hope you get it all sorted out :)
[Captivate Android Development] EnemyOfGlaDOS:
Oops double post
[Captivate Android Development] cmfrtblynmb:
ioexception?

Hello

I have the app and tried to check glitch app for updates.

Firs thing I noticed was that there was an update file. Is this sth we should install?

Also, I can not download and install update file, or any other kernel file for that matter. I get the error about "can't connect to ftp server" and also it says something about ioexception

Would be glad if someone could help. Phone went bad now, it is not working properly, I want to re-install kernel but I can not (at least via the app)
[Captivate Android Development] sixstringsg:
http://xdaforums.com/showthread.php?t=1315255

By XDA rules I cannot provide support to to a paid app outside the paid software forum.
[Captivate Android Development] cmfrtblynmb:
Oh, sorry!

Thanks for the reply. I did not know that page existed. I will look for my answer there
[Captivate Android Development] bentonhall:
When I get a text or email, BLN lights up my LED's but they only stay lit for like 5 seconds or so. I have tried using BLN Control and Blinky and get the same result. Anyone have any ideas? I would like for it to stay lit like it does on the stock CM7 kernel if possible. Thanks!
[Captivate Android Development] Aus_Azn:
Wait for V13, where it is fixed.
[Captivate Android Development] Fate-Silver:
Known issues for MIUI ROM. Claimed to be fixed during the next release(V13).

Some CM7 ROM users also have this problem previously, but, RARE.
[Captivate Android Development] bentonhall:
Thanks for the info. Ill wait and see how it goes in the next update. I'm currently running CM7 10312011 Nightly with Glitch V13RC1. BLN works but only for a few seconds.
[Captivate Android Development] mcala:
OK, what is this "V6 supercharger" script I see in alot of sigs? I did a search in this thread but it just shows me all the post with the sigs. Please explain what it does & where it can be found.
[Captivate Android Development] Gromlakh:
Lots and lots of info here, from Pikachu01.
[Captivate Android Development] \/icious:
Is that the same as this? I have not read your link but the one I provided is the v6 supercharger for anyone looking for it specifically
[Captivate Android Development] imb951:
Sigh. Patiently waiting on v13.

v12 is extremely buggy on all the latest nightlies. FC's everywhere.
[Captivate Android Development] Gromlakh:
No, it's for Pikachu's ridiculously in-depth analysis of various ways of optimizing your Galaxy S for performance, including a breakdown of the various init.d scripts (including Supercharger) and how they may/may not benefit people. It's a great read.
[Captivate Android Development] sixstringsg:
Well I'm sorry you're getting FC's, but it is highly unlikely that is due to the kernel. FC's usually occur when the system can't find a file or an attribute inside of an .apk that it expects to find, so it crashes, causing the Force Close dialog to appear. Except in very very rare circumstances, a kernel can not cause this. Also, I am on the latest nightly, just flashed V12, and am not experiencing any FC's.
[Captivate Android Development] cfili:
Check your /datadata partition. If it's full or near full you'll get FC's
[Captivate Android Development] Vaanhoot:
I am also getting some fc on the recent miui releases. When i try to download something or post pics using the xda app and I get a system fc once in a while. Never happens on stock kernel. I get a lot better battery life using glitch kernel so I stick with it cause battery life is important to me and I can life with the fc's.
[Captivate Android Development] imb951:
Thanks for the clarification. Sorry I was quick to blame the kernel. I am doing a nandroid now and I will test v12 again with the latest nightly.

---------- Post added at 07:14 PM ---------- Previous post was at 07:10 PM ----------

Will do. Thanks!
[Captivate Android Development] Gromlakh:
I'm skeptical about this whole "/datadata being nearly full causes FCs" business. Every time I've checked /datadata w/the "df" command, it's been over 90% full which is supposedly the magic cutoff point where it's supposed to start causing FCs. The highest I've seen it on my phone or my wife's (running the same setup as me) is 99%. I've never experienced any kind of widespread FCs.
[Captivate Android Development] sixstringsg:
It has been proven over and over again that that is the cause. It doesn't happen all of the time, nor does it happen to everyone, but anytime someone has widespread FC's, if they get /datadata down, it fixes it.
[Captivate Android Development] imb951:
Is the best way to do this to simply uninstall unneeded apps or is there a better way via ADB?

Also how does one check the status of /datadata? I navigated to it in File Manager and its showing empty. Surely this is not the case...
[Captivate Android Development] sixstringsg:
In the market there is an app called diskusage. Give it root privelages, and it will tell you what's taking up all the space. Then either uninstall those, or move them to the SDcard.
[Captivate Android Development] imb951:
Thanks again sir! Happy to report that v12 is working well with latest nightly. Though the stock kernel included with the latest nightlies has recently improved, I did miss the 1.5ghz step and the rock solid UV performance with Glitch, not to mention all the other goodies.

Looking forward to the v13 release while keeping an eye on my /datadata!!!
[Captivate Android Development] Holmes108:
Happens to me all the time when I'm in the 90's... moving apps to SD or uninstalling instantly fixes the problem.
[Captivate Android Development] bentonhall:
Same here!
[Captivate Android Development] pizz0wn3d:
You can use cachemate or something similar to keep datadata under control as well.

Herp derp Captivate XDA Premium.
[Captivate Android Development] jwood55812:
The only time I've gotten widespread FC's I checked my datadata and sure enough, 98% full. I've looked around for info on this, but couldn't ever seem to find any, but is there a good reason why datadata can't be increased in size? Seems like it would be an easy fix, to allocate even 100MB more and I think hardly anyone would hit the cap then.
[Captivate Android Development] sixstringsg:
Because we don't have the flash storage space to increase it.
[Captivate Android Development] RichMD:
Hi SixStringsG,

As you are working out the bugs, why not release another RC to get broader testing before releasing the final? I'd be happy to test V13RC2 if I knew what bugs it is supposed to fix and could watch for them, etc.