yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Koizuma:
Love the sig pics, very nice work on them
[Captivate Android Development] Fate-Silver:
LOL. Thanks for using it. :p

I am glad. But, why is it so small? The details seem to be torned apart when scaled down that much.

Where's sixstringsg? He's sleeping?
[Captivate Android Development] sixstringsg:
I just got up :p they look great. Thank you!
[Captivate Android Development] airtower:
All I could think when I saw this:

"If you can't be an athlete, be an athletic supporter!"
[Captivate Android Development] Fate-Silver:
Now, I wish to do a CWM screen for the next coming Glitch Kernel and maybe the booting screen. :o

Can I do it?

Anyway, please included these banners in the 1st Page for other fans/supporters to see and have them put into their signature too. :)

Thanks.
[Captivate Android Development] sixstringsg:
You are welcome to do the CWM. I'll have to talk to Glitch about boot screen, that one he did.
[Captivate Android Development] Koizuma:
I like How they look at normal size but for me its like oversized to what the rest of my looks like, yeah i'm weird LOL

Swyped from my SGH-I897 using XDA Premium App
[Captivate Android Development] Fate-Silver:
Sure, you can discuss about it with TkGlitch 1st.

Why OP doesn't have my lovely banners? I am sad.

The new happy task I wish: :o

a.) Bootscreen for Glitch.

b.) CWM screen.

---------- Post added at 03:33 AM ---------- Previous post was at 03:33 AM ----------

LOL. Weirdo. :p

---------- Post added at 03:43 AM ---------- Previous post was at 03:33 AM ----------

This is something Coreym suggested and wanted, 2 is better than 1. LOL.

Not sure if I got this correctly...
[Captivate Android Development] EnemyOfGlaDOS:
So close fate! Was looking to get both tester and supporter .. only one glitch logo though :p

Awesome job though dude. I likey :D
[Captivate Android Development] Fate-Silver:
Will do.

But, I hope you'll use it. Thanks.
[Captivate Android Development] EnemyOfGlaDOS:
..well yeah :p
[Captivate Android Development] Fate-Silver:
Done.

It's here. I think it's much better now.

Supporter and Tester are meant to be together. You won't test it at all if you don't support it.

Here you go...
[Captivate Android Development] EnemyOfGlaDOS:
i was thinking of supporter as "donator" Not everyone is a tester. Not everyone is a donator either :P

..anyway.. THANK YOU!:)
[Captivate Android Development] airtower:
To that point, what exactly qualifies one as a tester? I've tested a couple kernels for SG but I don't hang out in the IRC channel 24/7 or anything
[Captivate Android Development] sixstringsg:
If you have to ask, you're not a tester :p
[Captivate Android Development] sixstringsg:
I'm doing it soon, I promise.
[Captivate Android Development] askpcguy:
If I understand the OP, the latest Glitch kernel is the 12B3 which will work with the current Miui release 1.9.23? How come the date still says July?

14/07/2011 - V12B3 (High leakage)
[Captivate Android Development] timn2bama:
testing

testing glitch v12 beta out from stock 1.9.23 How do I backup kernels using MIUI rom? I used SGS kernel flasher but it doesnt seem to work on these kernels.
[Captivate Android Development] sixstringsg:
Do a nandroid backup. the /boot portion is the kernel.

Edit: The banner is now attached to the OP. If you are a tester or a supporter, PM me and I'll get you the appropriate banner. If you're not and you use one that is posted, well that's just rude and I will come find you.
[Captivate Android Development] JigsterNL:
Thank you!!!
[Captivate Android Development] vvaffles:
I'm not sure undervolting works in the v12 beta 3 LL. I have -200 on everything till 1.3ghz and its still running fine. Not to mention the battery drain is crazy on cm7 nightly 130 (though ppl report the battery drain on the rom thread too) is there anyway to test the voltage?
[Captivate Android Development] sixstringsg:
We've tested to make sure it works. We have absolutely no idea why it goes that low, but we have successfully frozen phones with the UV, therefore it works.
[Captivate Android Development] Fate-Silver:
The date said it's 22th of September but, that's for HL and ML. Not sure for LL because my Captivate is not happy enough to run LL.

Maybe you'll need to reflash it? Or maybe you need to flash back to STOCK Gingerbread(with GB Bootloaders) and flash MIUI all over again.

---------- Post added at 06:05 AM ---------- Previous post was at 06:01 AM ----------

I am thinking to do a 3D Version of Glitch Kernel for OP Title too. :o
[Captivate Android Development] sixstringsg:
Oops, missed the date. Fixing now.

Edit: fixed. Kudos to you for reading!
[Captivate Android Development] Akitohk:
same here but i'm using v12b3 ML;)

i think undervoltage is works since i got few reboot when i have every frequency -200mv to 1.3Ghz

after i changed uv to -175 on 1000Mhz, 800mhz, 400mhz, reboot gone:p
[Captivate Android Development] vvaffles:
I'm at 1.4 ghz now with -200 across the board, this has to be too good to be true
[Captivate Android Development] sixstringsg:
I've been looking and looking. I am 99% sure we didn't break anything with voltages.
[Captivate Android Development] EnemyOfGlaDOS:
wow:eek:.. my phone would NEVER be able to use that much UV. Shows how different 2 cpu's can be :p
[Captivate Android Development] timn2bama:
inching my way there now! hope my phone doesnt melt! lol
[Captivate Android Development] EnemyOfGlaDOS:
phone should stay cool as long as your not stressing on end for hours :p
[Captivate Android Development] vvaffles:
Gonna give 1.5ghz a try when I get home can't have the phone rebooting on me with 14% batt left
[Captivate Android Development] tkjeeper:
I'm topped out at 1440, and 100 uv across the board. Still experimenting.

Edit:Soft reboot, 75 across now.

Sent from the frozen tundra known as Canada.
[Captivate Android Development] Chahk:
Captivate running CM7 nightly #130, and Glitch v12 b3 (medium leakage.) On 3 out of 5 incoming calls I can't hear the caller, while they can hear me just fine. That's like the reverse "wonk" that used to plague my Nexus One (people couldn't hear me, but I could hear them.) Anyone else experience this?
[Captivate Android Development] sixstringsg:
This has happened to me once. I'll look into it.
[Captivate Android Development] vvaffles:
phone dies on me on 1.44ghz with -200, but its fine as long as it stay 1.4ghz and lower. so werid
[Captivate Android Development] askpcguy:
Running v12b3 hl and things seem great. At 1.2ghz and slight undervolt.
[Captivate Android Development] sixstringsg:
Try different leakages. And that's a 40% OC as it is. That's a lot.
[Captivate Android Development] razielvn:
Anyone help ,

I'm using Captivate with MIUI 1.9.23 and Glitch V12 beta low leakage. Everything is ok but I can't answer incoming call by press button on my headset (original).

If headset is still plugged in and I slide down lock screen to answer, my call will drop automatically.
[Captivate Android Development] sixstringsg:
Which beta? To find out, go into a terminal emulated, type in su, press enter, then Uname -a and press enter. And are you sure it's not a MIUI issue?
[Captivate Android Development] razielvn:
I'm sure that MIUI work well because when I combine it with Platypus kernel, everything is ok except for not able to use 90call_vol script.

PS : I'm using V12B3 (Low leakage) (CM7Captivate-Glitch-DEV-LL-20110922_2027.zip) and when type Uname -a, terminal show "Uname: not found"

Thanks
[Captivate Android Development] nuwan32:
if you uv more than 100 on the lower voltages like 100 or 200, does that cause rebooting than if you keep everything 100?
[Captivate Android Development] SweetwaterBurns:
Should have been uname (not capitalized) but doesn't really matter since you knew the kernel...
[Captivate Android Development] razielvn:
Yes, it's uname. :) But anyone know how to fix this error ?
[Captivate Android Development] SweetwaterBurns:
I remember atinm fixed an issue with 3-pole headsets sometime before teamhacksung was incorporated into CM7 officially. In May or April? I don't have a headset with a button to test or I would get some logs for you.

You might see if theescapist, yetter or atinm can point you in the right direction. Maybe supercurio, he's generally pretty helpful with audio stuff.
[Captivate Android Development] pizz0wn3d:
How do you guys figure out which leakage version is best for your phone? I'm running the ML atm, but I'm wondering if I should try out the LL to see if it'll be better for me. The thing is, I don't really know what to look for after the flash. Just overall stability?

Herp derp Captivate XDA Premium.
[Captivate Android Development] sixstringsg:
I don't have this error on mine. I am running CM7.

What can you overclock to?
[Captivate Android Development] melbourne408:
Hmmm, defiantly something I have to check out. Haven't updated my nightly since 127.

(edit-going to make some calls in a quick sec, see if anything happens out of the ordinary.)
[Captivate Android Development] bigbadwolf311:
What is the best way to flash this kernel. I tryed sgs kernel flasher but it is not compatiable. Should i odin flash or is there another way. I extracted the zip file and made it a .tar. Would that work for odin flash
[Captivate Android Development] melbourne408:
Your making it too complicated, it's a lot simpler, just flash the kernel through recovery :)
[Captivate Android Development] bigbadwolf311:
That sounds easier. Lol.
[Captivate Android Development] melbourne408:
hahaha yeee!
[Captivate Android Development] nuwan32:
keep oc/uving and see which version lets you push your phone the most. best way to test is what i usually do after each oc/uv play a 720p video for about 5 minutes. if your phone doesnt crash. your good.
[Captivate Android Development] pizz0wn3d:
Thanks ill give that a shot :)

Edit: actually, should I run a CPU stress test?

Herp derp Captivate XDA Premium.
[Captivate Android Development] Smasher816:
720/480p mkv with software decoding in mobo player.

If you can hit 5-10minutes then you should be good.

Best way to test your cm7 overclock (don't know why).
[Captivate Android Development] XsceneXhippieX:
does anybody have a good experienced comparison of thestock cm7 kernel (nightly 132 if that matters) vs the v12 beta?

glitch used to run amazingly on my phone, but started acting up back in the #70 something nightlys so i switched to NEO for stock kernel performance with voodoo color (i feel the stock cm7 kernel runs EXTREMELY well) but im iffy going back to glitch for some reason, is it even working with the newest nightly? there are mixed reports >.<
[Captivate Android Development] pizz0wn3d:
Hmm, i think ill put anchorman on my phone and try that out haha. I'm on miui though.

Tried pimp my cpu stress test out and it ran for about 6min perfectly fine at 1440 before I bumped it up to 1500MHz. Then my phone locked up and I had to battery pull. Rebooted and tried again with -50mv on 1500 and it locked up again. Looks like 1440 is my limit, at this leakage at least.

Herp derp Captivate XDA Premium.
[Captivate Android Development] airtower:
Not to bash glitch in any way, but voodoo-like color adjustments are coming soon to the stock kernel.

The latest v12 beta works perfect with the newer nightlies
[Captivate Android Development] sixstringsg:
Yes, it works on the latest nightly. There aren't mixed reports, just old ones and new ones. The newest beta zip int the OP works. If all you want is voodoo color, then use stock. If you want a smoother, faster, more battery efficient kernel, run Glitch.

This is correct.
[Captivate Android Development] sixstringsg:
Actually, it doesn't have full voodoo color support. Just basic.
[Captivate Android Development] airtower:
Yeah, I believe RGB adjustments only. No gamma corrections.
[Captivate Android Development] EnemyOfGlaDOS:
yup... exactly.
[Captivate Android Development] Fate-Silver:
A lot of people is complaining Glitch Kernels are having darker screen.

In fact, this is actually better. The Black-to-White Gradient is much stabler than Platypus Kernels.
[Captivate Android Development] airtower:
It bewilders me that people just slap the "recommended" voodoo settings in and then wonder why their screen is dark. It's customizable[/] so if it's too dark then crank the brightness and gamma up!

I prefer it darker if only for better battery life.
[Captivate Android Development] zuN!:
There's one issue I encountered with the volume script. When I flashed a new nightly version from the previous one where I had the volume script installed, the script no longer exists in the etc/init.d folder, yet the volume is still loud. I then place the script in etc/init.d again with settings set to a lower volume, but it seems as if it only adds dB onto the already pre-existing settings. I tried putting the values of audio output to 0 (no gain) and yet it's still really loud. Any fix for this issue without having to wipe data/have a fresh install of CM7 (wiping cache/dalvik wouldn't make any sense in fixing this nor did it do anything when i did)?
[Captivate Android Development] sixstringsg:
Remember to reboot after putting the script there. Scripts in /etc/init.d get executed on boot.
[Captivate Android Development] zuN!:
I did reboot and nothing changed. I checked out the files located in "/sys/devices/virtual/misc/voodoo_sound/" which would be affected by the script and the old values are still there, meaning that changing the 90_vol script and rebooting didn't seem to affect it.

edit: going to that folder and manually changing the values worked.
[Captivate Android Development] sixstringsg:
I have to ask, you did remember to reflash the kernel after the nightly?
[Captivate Android Development] zuN!:
Yes, I did. That's why I don't understand why after flashing the new nightly --> latest Glitch --> eventually placing the 90_call script in etc/init.d again didn't seem to change the values set from the first time I ever did the whole 90_call script process.
[Captivate Android Development] sixstringsg:
Try running the script through script manager. Ssewk2x actually did that part, so I would have to do some more research to help you further.
[Captivate Android Development] nuwan32:
if you want my imo, here are my oc/uv settings using v12b3 HL. i can do anything perfectly without crashing, playing games or watching 720p movies.

1500 -25

1440 -25

1400 -50

1300 -50

1200 -75

1000 -75

800 -100

400 -100

200 -125

100 -150
[Captivate Android Development] psycho2097:
Can someone recommend the best governor settings, for v12b3 ll, on miui... I tried to read up a lot on it, but no specific thread with concrete info exists afaik. I m kinda muddled on smartass, interactive, interactive x, etc... Can't figure out which one to use...

Anyways, I use pimp my cpu, n my requirements are purely battery based, because I don't play many games or stuff, just basic browsing, news, mail, calls, etc. Used the experimental ondemand governor in the screen state scaling script, worked pretty good, but I was wondering if there was any governor that gives as decent a battery life, but with slightly increased performance.

Sent from my cell phone. DUH
[Captivate Android Development] sixstringsg:
The defaults is the default for a reason. We've found ondemand to be a very good governor for a mix of battery and performance. People tend to like smartass a lot. Most have a favorite without any good reason why it's their favorite.
[Captivate Android Development] pizz0wn3d:
Hmm. I should probably try to uv more on 100-200mhz. I'm at -100 all the way up to 1000mhz and -75 for 1200MHz, which is currently my max clock. The battery drainage above 1200MHz doesn't seem to be worth the slight performance boost to me imo. =/

Yeah I usually just stick with the dev's default haha. I figure they know a lot more about the governors and how well they work with their kernel.

Herp derp Captivate XDA Premium.
[Captivate Android Development] nnexuss:
Hi,

I´m with CM7i9k-Glitch-DEV-HL-20110922_2259 (Galaxy I9000) and my BLN doesn ´t work! Any ideas?

Thanks.
[Captivate Android Development] zerkai:
Try Blinky from market and make sure you match that kernel with an i9000 and not a captivate I guess.
[Captivate Android Development] psycho2097:
K, I trust you... :P but seriously, if someone could point me to some resource on this, It would be greatly appreciated.

Plus, what scheduler should I use? currently using sio because it had always given me great results on i9000 Roms.

Sent from my cell phone. DUH
[Captivate Android Development] XsceneXhippieX:
Google is your friend in the world of Google phones lol, look up sio vs deadline or cfq do some info scouring, all of them are intelligently designed, its a matter of your current app setup and what you use your tablet for most that will change how each performs event really comes down to it, I mean some are better for benchmarking but make real world use ****ty, and vice versa
[Captivate Android Development] askpcguy:
While on Glitch v12B3 HL, I went to sleep with 60% battery and woke up to a powered off phone. Pressing power did nothing. Plugged into the wall and the battery icon showed no charge. Samsung Captivate, Miui 1.9.23
[Captivate Android Development] sixstringsg:
I'm guessing something kept a wakelock overnight. were your battery stats intact when you turned it on?
[Captivate Android Development] XsceneXhippieX:
v12b3 runs awesome, no lagginess, battery is great but worse than NEO by a bit, performance is awesome though, tethering is flawless and fast, no complaints whatzoever
[Captivate Android Development] nuwan32:
yea why does this happen? sometimes when phone is off, instead of putting it to deep sleep, it uses max clock...
[Captivate Android Development] sixstringsg:
It's an app taking up resources. Use some kind of system monitor to check what's going on.
[Captivate Android Development] nuwan32:
i use the miui sidekick to kill apps before locking phone. is this not enough?
[Captivate Android Development] pizz0wn3d:
Doubt it. It's probably a background process that just relaunches right after you close it.

Herp derp Captivate XDA Premium.
[Captivate Android Development] sixstringsg:
That's correct. That's actually why we recommend not to use a task killer. If you'll notice, most of apps that are "killed" relaunch immediately. Therefore require the cpu and memory to work to kill it, then again work to relaunch it. Android has a very good application manager, so long as the Apps are written well. When apps aren't written well or they go haywire, then they can keep wakelock, or actually be doing a lot. You don't notice it because the screen is off, but then it kills your battery.
[Captivate Android Development] nuwan32:
yea but some apps that still eat cpu/ram when you close them can be stopped by the app killer. only required system apps like keyboard and framework are unkillable, because theyre needed. i actually like app killers because they free up ram. but anyway no other way to fix that problem huh?
[Captivate Android Development] sixstringsg:
Well it's not a problem with the kernel. It was an app that ran away on you. Also I disagree with you on the point that only required system apps are unkillable. For example: slacker radio. If you have it installed and don't limit it through autostarts, it will open and take RAM every time a ringtone/notification happens, because it triggers at a media event. Most widgets you have stay in RAM, (I know for a fact Beautiful Widgets does) so when you kill those, they automatically pop back up. If you have facebook or twitter or e-mail coming to your phone by either push or sync, they will live in RAM and will restart when killed. The Amazon Appstore also has a nasty habit of opening up in your RAM whenever you use an app you download from it, as does Getjar. Both Mighty Text and DeskSMS hang out in RAM, as does Blinky. Skype does sometimes too. All the apps specifically mentioned will reappear after being killed unless you limit them by either uninstalling them, or limiting them via autostarts. I'm not trying to be rude or prove you wrong, I'm just trying to help you understand how the android application manager works, and how some apps don't work as they should with it.
[Captivate Android Development] Fate-Silver:
I heard this from a lot of experienced users as well.

Last time, I was using something like Advance Task Killer, etc. Some people said it saves battery life. But, then, I don't notice it. And, it kills my battery life.

---------- Post added at 01:45 PM ---------- Previous post was at 01:40 PM ----------

More to mention:

Google Maps

WhatsApp Messenger

Google +

Tango

Keyboard(the specific one you're using currently, included Swype, Smart Keyboard Pro, etc)
[Captivate Android Development] sixstringsg:
Yeah, I use SwiftKey and it alone uses 20mb of memory. And gets relaunched when killed.
[Captivate Android Development] WillyWonka23:
If I just have the ATK widget on my screen to free up ram when needed will that drain battery in the background? I don't have the application running just the widget.

How do you check if the phone is on wakelock when screen is off and not being used? Is it the "Keep awake" under i.e. Android System in the Battery Use?
[Captivate Android Development] pizz0wn3d:
It shouldn't, but if you're running MIUI, the task manager (hold down the home button) has a button that kills background apps when pressed. I personally just stay away from task killers in general. They're unnecessary and, more often than not, do more harm than good.

Herp derp Captivate XDA Premium.
[Captivate Android Development] Doug8796:
how is B3?
[Captivate Android Development] askpcguy:
I believe my 100 mhz was -100 and I didnt check anything, out of frustration I re-flashed miui 1.9.23 to get things working. I did notice today I got terrible battery performance.

I'll give power tutor a run to see if anything looks odd.
[Captivate Android Development] Burstaholic:
Graphical glitches

I just started using CM7 w/ Glitch and my phone runs great, but I'm having a strange graphical issue - strange gray splotches appear on any dark wallpaper I use for the home screen.

It's especially noticeable in the Galaxy live wallpaper and the first 'planet view' CyanogenMod wallpaper.

This doesn't show up in screenshots, so I'm assuming it appears somewhere down the pipeline, like in my GPU or screen.

This does not occur with the stock CM7 kernel - has anyone else seen this issue?
[Captivate Android Development] EnemyOfGlaDOS:
I have not sorry. Occasionally I'll see a wacky color from a failed OC messing around but not normally. My dark wallpapers look fine :(
[Captivate Android Development] Burstaholic:
My best guess is my GPU doesn't like being overclocked, but I don't know how I could test that currently.

It's not a deal-breaker, but those do happen to be my two favorite wallpapers :\
[Captivate Android Development] :
Try using the voodoo color settings in post #962, and adjust to your liking.
[Captivate Android Development] Burstaholic:
I should have mentioned I tried that. Changing Voodoo Color settings does affect the splotches, but can't eliminate them.

Basically, doing that I can make them be any of a hundred different shades of gray, but not make them go away, except by using an unaffected wallpaper.
[Captivate Android Development] Fate-Silver:
This affect all kernels, except the current newest Stock Kernel comes with MIUI 1.9.30. Platypus Kernel is the worst. Super broken.

Glitch and Talon are still acceptable.

The Black-to-White Gradient is broken. No matter how you adjust the VC, it's still broken... Except, you forcefully make it(using the 2nd VC solution setup I posted previously). It fixes the broken gradient. But, it'll cause the screen dark colors to become really dark(like full black).

I'll give some examples here later.

I think all MIUI/CM7 Kernel makers should look into this.

---------- Post added at 02:06 AM ---------- Previous post was at 01:31 AM ----------

See here,
[Captivate Android Development] sixstringsg:
I'm pretty sure the reason that happens is because of our "fix" of the green flash at too low of a brightness. I'll look into it.