yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] cmfrtblynmb:
I also bought the app. I will try the v13 as well and will tell you the results

---------- Post added at 01:12 AM ---------- Previous post was at 01:11 AM ----------

Yes, exactly.

I am on CM7 and your kernel now. (I am installing RC 13, ML version)
[Captivate Android Development] sixstringsg:
Sounds good to me. You can hop in IRC if you would like, it's faster. Or we can continue here, whatever's convenient.
[Captivate Android Development] cmfrtblynmb:
Update: Nope, problem is bigger.

Oh, when I said stock I meant ODIN one click thing :) SOrry for the misunderstanding. I will do this now as a last resort.
[Captivate Android Development] 105437:
sixstringsg... I just bought your update app. Thanks for all your hard work, I love running the Glitch kernel!!

So my question is, how can I test which is best for my Cappy? Is there a way to test stability and performance to see if I should run ML or HL?

Thanks again.
[Captivate Android Development] sixstringsg:
https://gist.github.com/1280009 #4
[Captivate Android Development] Smasher816:
[APP RELATED STUFF]

Incase you didn't know sixstringsg came up with the idea,

and I made the current app, after improving/redoing d4rken's.

It is still a WIP so I am continuing to add features and fix problems.

If you have any suggestions then feel free to sugest them to me and ill run them by sixstringsg and Tk-Glitch, and then maybe get them in the app.

But im happy and suprised that this many people have bought it already and given it a good review. Thank you all.
[Captivate Android Development] pmgnet:
Wow, looking at setcpu for advanced, and I have no idea what numbers are good for what.

Can anyone share their table of moderate numbers (safe, and not extreme) to balance performance and battery life, for say 1400 OC, with stable UV numbers for all the frequencies?
[Captivate Android Development] pmgnet:
Ok, looked again at that first post and finally got my brain around the numbers. I'm using the recommended there for OC maxed at 1400. Will see how battery does now!
[Captivate Android Development] EnemyOfGlaDOS:
yeah dude :)

1400mhz should be attainable with this kernel i think for almost anyone. Try -100 across the board or -75. You may find that stable and then tweak it a little from there to get a little better battery life if you wanted. ...just a thought;)
[Captivate Android Development] sixstringsg:
Voltage control, right? Cause setCPU isn't what you want. And the big battery drain will go down once the kernel settles in. Start with -50, and go from there. Keep going down until it freezes.
[Captivate Android Development] SweetwaterBurns:
Anyone else try v10c2? I've been running it for the last few hours and have been stable at 1.5 where as with v10c I topped out at 1.3 and now I have a better undervolt to boot.
[Captivate Android Development] xAndrew225x:
Is smartass basically the same thing as interactive? I can't get the interactive governor to stick for some reason, it keeps switching back to smartass.
[Captivate Android Development] EnemyOfGlaDOS:
no, the smartass governor effectively gives the phone an automatic Screen Off profile, keeping speeds at a minimum when the phone is idle. The interactive governor is functionally similar to the ondemand governor with an even greater focus on responsiveness.

*have you tried going into CM Settings and performance> cpu> governor ... and tried changing it that way?
[Captivate Android Development] koflem:
You need to remove/edit the screenstate scaling script from the init.d folder if you want to choose your governor, else smartass is forced when the screen is on.
[Captivate Android Development] seriywolk1234:
The link in the header instead of the version of the theme "C-VC" swinging "B-VC", so if a topic keep it properly!
[Captivate Android Development] shaolin95:
WTF?! "If a sentence keep it understandable!" :rolleyes:

Gotta love a noob demanding things....on behalf of other , mature users, get lost!
[Captivate Android Development] EnemyOfGlaDOS:
Um... so if a properly keep, theme is C-VC swinging .. topic header link instead version.

There, my post is more confusing than yours :p
[Captivate Android Development] shaolin95:
JAR JAR Binks!
[Captivate Android Development] pmgnet:
Disable BLN?

How do I disable back light notification?

I'm pretty sure it's using up my battery and want to confirm. battery stats say display is 60% of battery usage, even though screen is off (like overnight).
[Captivate Android Development] EnemyOfGlaDOS:
I'm not positive.. but I don't think you can. Also the LED notifications I don't think use all that much battery.
[Captivate Android Development] sixstringsg:
If you get am old CMparts.apk you can. But you're right, it doesn't take much battery.
[Captivate Android Development] EnemyOfGlaDOS:
Nice.. I forgot about CMparts.apk and that little trick
[Captivate Android Development] apewall:
Soft buttons stop responding sometimes on c-vc2 and I have to lock/unlock for them to work again.
[Captivate Android Development] sixstringsg:
That's a bug in the BLN implementation that team hacksung decided to use. Its being worked on.
[Captivate Android Development] pmgnet:
Stuck soft keys?

Anyone getting the stuck soft keys where you have to hit power twice to get them to work?

This was an issue in the older CM7 builds that had BLN.
[Captivate Android Development] EnemyOfGlaDOS:
Hasn't happened in awhile.. but ... yeah. I forget which kernel version I was using.. I've since then upgraded :rolleyes:
[Captivate Android Development] airtower:
I would ask that the download path be user defined, or default to the sdcard. I know that may increase the likelihood the kernel is leaked, but for those on nightlies it's a bit of a pain to go dig it up every flash.
[Captivate Android Development] sixstringsg:
We're not putting it somewhere easy, for the reasons you stated. The app will flash nightlies later on. There also isn't much point flashing every night, just about once a week if that, so the app can be used that often, or you can find it that often.
[Captivate Android Development] airtower:
Well if the you all plan to have the app flash nightlies at some point then that's fine, but I doubt you're fooling anyone in here by putting it where it's going now. The full path is shown in recovery anyway.
[Captivate Android Development] RichMD:
Repeated Lockup when booting in airplane mode

I flashed CM7 #157 Sunday after a factory reset (so a clean install) and then installed the glitch app and V13RC. I then calibrated the battery - let it charge to 100% and then ran it until it died. For the last couple of hours I had it in airplane mode since I was at work. After it shut off, I let it charge until full overnight. This morning when I boot up (still in airplane mode) I can not unlock the phone. It boots up to the lock screen (no background which is odd) but everything else shows. I can't move any of the ringlock icons at all to unlock it though. I have rebooted several times and have the same result. I would just wipe everything and install clean but my last backup is before the 157 install...

Any ideas? Is there any reason that airplane mode would cause a problem if enabled at bootup when running V13RC or the new app?

Edit: I tried pulling the SIM card (to try something) and also I wiped dalvik, cache, and voltage settings by booting to recovery mode. No luck - the phone is locked solid every time it boots. I see an icon in the status bar like it is scanning the SD cards and it goes away but I get no response when trying to unlock the screen. After sitting at the lock screen for about a minute, it rebooted by itself... - still locked though.

Edit2: I booted to recovery, mounted USB storage and put V12B3 on my SD. I then used "clean kernel files" and then installed the V12B3 zip. After booting up - still locked. I was "guessing" this was kernel related but maybe not.
[Captivate Android Development] spawn4ever:
hi all...

i installed miui rom & glitch kernel v12 beta3 (medium).. (on samsung galaxy s)

my problem:

BLN not work!

i activate all LED notification @ miui rom...

and i also installed bln controll from market...

but it don't work...

can someone help me?

thx!
[Captivate Android Development] sixstringsg:
Please search the thread before posting. This question has been answered countless times. BLN doesn't work on V13B3 for everyone. I'm the FAQ it tells you things to try, you missed the third. V13 official will have working BLN.
[Captivate Android Development] sixstringsg:
Did you try reflashimg the nightly you had flashed? Also, does ADB recognize the phone in this state?

Edit: saw you got it working. Good.
[Captivate Android Development] Vaanhoot:
I know people are complaining about the touch keys staying lit but I like that. Is it possible to have that in v13 too?

Sent from my SGH-I896 running MIUI.
[Captivate Android Development] Holmes108:
Agreed... proper KTLO is my most missed feature since switching to MIUI. I love the ROM too though.
[Captivate Android Development] sixstringsg:
Well there isn't really a way to do both.

If the dev of KTLO wants to update his app, that's fine. I can't have it both ways, and I'm not making two versions. Popular vote was the lights timing out. I personally like them staying on, but oh well.
[Captivate Android Development] Gromlakh:
I don't suppose there's any way of coding it to work with a toggle switch, is there?
[Captivate Android Development] sixstringsg:
That would be a ROM change, not kernel.
[Captivate Android Development] Gromlakh:
Could this be done by a script? If so, I could write something and post it. I just don't know what setting is controlling whether the lights stay on.
[Captivate Android Development] sixstringsg:
I will look into it. Thank you for the offer, but if I figure out how to do it, I can just post the script for it.
[Captivate Android Development] Vaanhoot:
Yeah I don't expect you to make two versions. Just was wondering if there was a way the common user could do it himself. Thanks for your hard work on this great kernel.

Sent from my SGH-I896 running MIUI.
[Captivate Android Development] slayp00n:
Hi,

Not sure if it is this kernels fault but, I noticed that if I plug my USB cable into an iPad AC plug my phone charges in USB mode not AC mode.

I am pretty sure it didn't used to do this? Is there anything I can do to get it to charge in AC mode with a non samsung charger?
[Captivate Android Development] tiuk:
You can bridge the data pins in the USB connector (the middle two pins). You could either modify your cable, or make a USB make/female adapter to go between the cable and charger. If you look up the fun with resistors thread I've written a few posts about this.

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] slayp00n:
if you bridge the cable directly then plug it in a usb port, will you blow the usb port>
[Captivate Android Development] Koizuma:
Interesting, sounds like not alot of people can use the LL i'm guessing? I been using the LL since I came to MIUI.

Swyped from my SGH-I897 using XDA Premium App
[Captivate Android Development] sixstringsg:
LL is very rare. How much do you OC? Samsung default is HL, so LL is quite far away.
[Captivate Android Development] Koizuma:
Interesting. as far as OC and UV goes,

I've been able to push it to 1.5GHz at -125mV

normally i run 1.3Ghz - 400MHz @ -125mV, then 200MHz is -150mV and 100MHz is -200mV
[Captivate Android Development] techguy615:
I saw this subject earlier and it occurred to me that I had never tried LL before. So, I tried to see what I could do with it with just standard CM OC settings. LL worked fine up to about 1.2, ML is what I normally use and I get 1.5 with no stability problems.

LL must be a beast.
[Captivate Android Development] nuwan32:
if you CAN use LL is it better to use it than HL at same oc/uv settings?
[Captivate Android Development] sixstringsg:
No. If you can OC/UV the same, then it doesn't matter which you use. I highly doubt that you can use the same OC/UV settings on each, either that or you don't push your OC/UV very far.
[Captivate Android Development] Aus_Azn:
I'm on LL, and I can OC to 1.5GHz and UV to at least -150mV on all frequencies...
[Captivate Android Development] airtower:
wow, man with the golden phone!

But on another note, what exactly does one lose by going to a higher leakage? In other words, why doesn't everyone run HL? Do you lose stability if you have a LL CPU and HL kernel?
[Captivate Android Development] shaolin95:
Nothing is lost by using either one. It is just a matter of having 3 options to see which one your phone likes better in order to hit the max speed it can achieve. That is all there is to it.
[Captivate Android Development] Koizuma:
lol nice, thought i'd give -150 ago myself on the frequencies that I use so far so, the phone hasn't failed a stability test yet neither
[Captivate Android Development] shaolin95:
Are guys using Stability Test app or somethings stronger like mobo player running a 720p video in Software mode?
[Captivate Android Development] Koizuma:
Testing -175mV now on all frequencies and so far so good

for me I do 20 rounds of stability test, then some N64 Emulator, a little of angry birds, some texting and watch some videos that i got on my phone
[Captivate Android Development] slayp00n:
Hi,

bought the app to support the dev. Best kernel I have ever used...

1.5ghz stable all day everyday and sick bat life.

Just one suggestion, there is not 'check for newerversion of kernel' in the app..

Some of us OCD kernel junkies would love it :)
[Captivate Android Development] sixstringsg:
Thanks for your support! We're working on adding that in, there are just a few technical hurdles to overcome. It should be in the next update!
[Captivate Android Development] slayp00n:
One other thing: please ear mark my 5 dollars for beer consumption. :).
[Captivate Android Development] Smasher816:
Lets see if i can get this HL/ML/LL thing straightened out.

The three version control a special cpu voltage. You know how when you OC you have to find the right voltages for your phone, this is the same thing.

One is not 'better' than the other. The thing is that one will work 'better' on your phone.

HL is the most like stock samsung and cm7. and LL is few and far between. If you are happy with your OC stay at HL, if not try the other ones and see if your device works better with that one.

As they say there is no one size fits all. *Cough* koflem. (reason HL+LL exist). He could OC w/ special volts (LL) but no one else could. Everyone else could OC at normal (HL) except for him. So glitch made multiple versions to help everyone find their best.
[Captivate Android Development] slayp00n:
Not sure if this is the kernel or my phone... But out of the blue the power button seems to be stuck down? physically it still clicks and feels normal. I didn't drop the phone or anything it just started randomly... Could this be the kernel or is it hardware failure?
[Captivate Android Development] sixstringsg:
I don't know how it could be a kernel issue, but you could flash back to the stock CM7 kernel just to make sure.
[Captivate Android Development] SPE926:
My phone doesn't play nice with the new V13 kernel. First time after charging all night it erased all my music, tried to reboot bootlooped. V12 b3 was reinstalled problem went away. Tried V13 again thinking that previous problem was just a coincidence, after a day of use my home button started bringing me to the clock dock screen. Reflashed v12 problem went away again. Irk what's going on but I would think it has to be kernel related.
[Captivate Android Development] sixstringsg:
Where is your music stored? These kernels have been stress tested for two weeks, and nobody has had these issues. Your home button is ROM related, not kernel.
[Captivate Android Development] redsst:
Anybody else using the nice Voodoo Color settings (230,230,270 & -50,-53-44) and getting the old Green Tint Screen when the screen dims?
[Captivate Android Development] sixstringsg:
You're using the RC1 I'm guessing, correct? And are you using the "punchy" settings in Voodoo Color?
[Captivate Android Development] redsst:
Yes sir. RC1. I tried the punchy settings and the setting recommended here on xda (230,230,270 & -50,-53,-44). Both produced the same result.
[Captivate Android Development] Fate-Silver:
If you're using V13 RC1 and above(current DEV), you'll have this problem.

How to solve? Can't solve. Just set the Screen v1 Gamma Hack to adjust the setting yourself until you don't see any "GREEN TINT" thingy.
[Captivate Android Development] SPE926:
Music is on SD card, and if it was ROM related why would changing nothing but the kernel fix the issue? Just looking for clarification cause I figured since swapping nothing but the kernel fixes the issue that something with the kernel causes it......
[Captivate Android Development] sixstringsg:
The kernel is not capable of just deleting all of the music on your SD card. If anything were to happen SD card-wise, it would have been your entire SD card. The kernel is also not capable of changing it's mind and suddenly deciding to make your home key do different things. The button mapping is configured through the source, and isn't able to be changed after the kernel is built. Also, if there was an issue with the driver that controlled the home key, we would all have it. As far as bootloops go, it is a well-known fact that CM7 bootloops sometimes even on stock kernel for no reason at all. The reason that all of this could have been fixed by flashing a new kernel is because when you flash a kernel, it isn't just the kernel being installed that happens. Modules are copied over, caches are wiped, things are in general cleaned up. You could also have gotten a bad download. Kernels don't just behave differently for different people. If there is a kernel issue, it is almost always reproducable by others, and if it can't be then there is a good explanation as to why it can't. Does that answer your question?
[Captivate Android Development] SPE926:
I guess I'll give it another go and are what happens.
[Captivate Android Development] Snow.Goose:
Can't wait for v13! Great job on the kernel!

Sent from a Captivate running CM7
[Captivate Android Development] slayp00n:
The lock button magically fixed itself after about 5 hours... I was outside in very humid air for a few hours, I am thinking maybe some moisture got into the lock, then eventually dried out.
[Captivate Android Development] tiuk:
No, it makes no difference where the bridge is. Bridging the data pins is in the USB spec as triggering a "charging mode". It just lets the host know (host being the computer, in the case of your question) that it can supply up to 1A (instead of the usual 500ma for USB devices) to the port.

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] techguy615:
Phone went dead...

Ok, sorry if this has been addressed. I saw some comments on "deep sleep" and I am not sure if this is a sleep scenario or not. I woke up with my phone dead yesterday (had to pull the battery to reboot it). So, I rebooted it and though it was a fluke. It was left on the charger all night. Today I had the same thing happen at work. Had to pull the batter again to get the phone to come back on. This time I didn't have the phone on the charger. When I powered it back on my battery was at 57%.

No OC settings used since I don't have CM7 set to apply the settings on reboot for now. Running CM7 signed and not the nightly. I saw where someone else had the same issue a while back. I am on the v13 RC Medium Leakage.

Just reporting it for the sake of it. :)
[Captivate Android Development] sixstringsg:
That has nothing to so with deep sleep. What are your UV settings?
[Captivate Android Development] techguy615:
I am honestly not sure.100MHZ min, 1000MHZ Max, Governor is ONDEMAND. This is just standard CM7. Never had the need to tweak anything else really.

Sorry, if this too generic of a reply.
[Captivate Android Development] Smasher816:
Here is a little teaser of the next app version.

http://xdaforums.com/showpost.php?p=18833152&postcount=84
[Captivate Android Development] simple man:
Nice app, and RC kernel is sweet too. Good work all involved! :-)
[Captivate Android Development] Grandelama:
Fantastic job guys, I'm liking v13RC1 very much. I was only hoping on a "on all the time" victory in the poll but sadly the defeat is clear :p

I know that this has already been discussed, but I still have a problem with the incall volume (toooo loud).

I already applied the call volume script on the OP and set every "In call boost" value to zero. I tested it and I have to say it is working correctly both through init.d on boot and when loaded with script manager.

With the script and system volume on lower level the situation improved and some of the calls are now bearable, but in most of them the volume is still too loud (still painful) and I just cannot keep the phone on my ear.

Is there anything else I can do to improve the situation?
[Captivate Android Development] Fate-Silver:
After using these kernels for quite a while, I can say the only bug I encounter is:

BLN works flawless on V13RC1 and above in CM 7.1 ROM.

But, BLN doesn't work correctly on MIUI ROM...
[Captivate Android Development] slayp00n:
I know, but I mean if I used a bridge cable and plug it into a USB computer port, will it not overload that port and burn it out?

Like I will need to make sure not to mix up my cables
[Captivate Android Development] tiuk:
What I was saying is, the computer's USB controller is designed to act accordingly when the data pins are bridged. The first cable like this that I made was to use with my laptop. Windows XP used to charge a device at full current if pins 2 and 3 were open (not bridged). When I formatted it with Windows 7 I discovered it was taking a lot longer to charge. I made the cable, plugged it in, and it worked as expected.

So, don't worry.

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] cumanzor:
Hi guys. Not sure if this is related to the kernel or to CM7, but I have enabled to logcat but I'm not getting any output from my apps. In fact, it looks like I'm only getting hardware related information.

Any ideas? Everything is normal on the simulator.
[Captivate Android Development] Smasher816:
MORE TEASERS :P

http://xdaforums.com/showpost.php?p=18852353&postcount=91
[Captivate Android Development] sixstringsg:
Not a lot of logging is enabled right now. We're working on it.
[Captivate Android Development] Tk-Glitch:
I did change that already in V13 source. V13 final will give you normal logging again :)

Sent from my glitched GT-I9000
[Captivate Android Development] cumanzor:
Alright then. Any word on when V13 will be out? I'll move to the stock kernel in the meantime.
[Captivate Android Development] Tk-Glitch:
I did have to fix some major bugs after RC1 so we can consider it's in final testing phase ATM. Hopefully all will be fine and we'll be able to release it quickly now ;)
[Captivate Android Development] Koizuma:
thats good to hear i need some new sexy glitch love on my phone :P
[Captivate Android Development] omnikai:
Which fixes might those be? Or is it customary to wait for the git changelog?
[Captivate Android Development] sixstringsg:
You can see the git changelog whenever you want. github.com/Glitchkernel. There were some big issues in the source, a lot relating to a bad hotspot that Glitch was at when he pushed we believe. If you would like more, wait for the official release, which will be not long.
[Captivate Android Development] cumanzor:
That's good to hear. Thanks!
[Captivate Android Development] CptTwinkie:
Anyone having problems with video stability on captivate?

cm nightly 158

Glitch v13rc1 ml

I'm at 1600mhz and passing all stability tests (and getting a great benchmark in antutu). The only problem I'm having is running the gpu test in stability test. It locks or reboots every time.

I've tried some less aggressive clock speeds with the same results. Any advice?

Sent from my Captivate w/ CyanogenMOD and Glitch