yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] tkjeeper:
Since last night, when I switched back to 3.2, go sms is not even on the list in what's using my battery. So it's not go sms related.

Sent from the frozen tundra known as Canada.
[Captivate Android Development] pikachu01:
Download terminal emulator and use the command "top". You'll see it consuming 90% of CPU cycles.

My phone getting hot without doing anything was an indication. This only happens with Galaxy S (checking Gosms thread and Gosms blog).
[Captivate Android Development] bballer182:
Yeah i noticed that in the changelog but did not see the voltage differences in Control Freak?! i ended up decreasing UV by 25mV across the board that seemed to do the trick. This kernel is the Sh!t!!!
[Captivate Android Development] existz:
Yea, there was some voltages that were showing one thing but was actually something else, just fixed them so it showed correctly

Sent from my SGH-I897
[Captivate Android Development] smithisize:
Are there any plans on adding smartass to this kernel? Or are you leaving leaving that to your other kernel?

Great work, by the way! This is my favorite kernel! I use it with every ROM lol I was so stoked when you released your JVQ base ha :)

Regards

Smith
[Captivate Android Development] manny05:
Not sure if this has to do with the kernel or maybe spare parts app.

But when I get a text message (using handcent) the pop up window comes up but the notification sound comes up 6-7 second later...usually its suppose to all happen at the same time...

however when I go into my text msg app (handcent) and I stay in there and wait fire my next text everything works at the same time... Its the outside of the app that its causing me this problem...

Any fix to this???

EDIT: apparently freezing the messing app was the problem lol. Nvm guys. Great kernel btw.
[Captivate Android Development] harpo1:
I switched to a previous version of GOSMS Pro and the issue went away. Plus plenty of other people having the same issue if you read the reviews from the market.
[Captivate Android Development] simple man:
This kernel is amazing, it sure made a difference... so smooth... good colors. Good work Existz! :-)

Continuum 6.1. JVQ

TalonDev 0.4.1 no-overclock

JV6 modem
[Captivate Android Development] crazililazn:
Wait, so are these fixes in 0.4.1 or will they be in the next release?
[Captivate Android Development] existz:
Its already in 0.4.1. So with some steps you might not be able to UV as much, which technically it will still be the same.. for example, the 800 step showed the correct frequency, but was actually overvolted by like 25mV-50mV...you can check the git commits to see what all was actually changed
[Captivate Android Development] chappatti:
What is the status of autobrightness?

Thanks
[Captivate Android Development] existz:
Theres a DIY fix in i9000 forum.
[Captivate Android Development] geokilla:
Was there a problem? It'd be great if you can post a link as many don't go to other forums.
[Captivate Android Development] e36bmer:
I found that when using the Screen Filter app with this new kernel, the colors are adversely affected. Instead of the whole screen just getting darker, it seems to loose contrast, and not get as dark as the previous kernels. So, color quality is quite poor when using the screen filter app. I will try other apps to see if it has the same affect.
[Captivate Android Development] Spidious:
OK I am back. Installed latest version

But how the heck do I turn the stagefright on ?

I can't remember. That is the main reason I put on Talon...
[Captivate Android Development] LNJ:
Stagefright is activated by default I believe.

Samsung Galaxy S i896 on Cezar's Continuum v5 GingerBread
[Captivate Android Development] shane87:
I know you said you fixed the handcent popup coming before the notification by freezing the stock mms app, but I wanted to point out something else that could have been the culprit. If you look under menu > settings > popup settings, there is an option labeled "quick popup." Enabling this option causes the popup to pop as soon as the phone gets the sms/mms signal from the tower. Disabling this option causes the popup to wait for the message to be saved before popping the popup. The notification in the status bar does not activate until the message is fully retrieved and saved, so enabling quick popup will cause the popup to come up before the notification, especially if you are multi-tasking.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] crazililazn:
Ahhh ic, that would explain my severe instabilities with 0.4.1. I'm going to try it again and see if I can get it stable this time :D

Wait, is the 800Mhz stepping the only one with the voltage change? Because I slightly raised voltage on that stepping and I still couldn't get it stable :X I think it would be a HUGE help if you can post all the stock voltages for each frequency in 0.4.1 because I couldn't understand the git commits X.X
[Captivate Android Development] upNsmokeAllDay:
WhY is my custom boot animation gone. It still shows up in system/media. All I have is the lame samsung boot now.
[Captivate Android Development] existz:
After first flash, or any dalvik cache wipe, it will show samsung bootanim, this is done so it does not show just a black screen...on second boot your custom bootanim will show
[Captivate Android Development] upNsmokeAllDay:
Nah I rebooted about 10 times so far. I knew about the first boot from your other releases.
[Captivate Android Development] crazililazn:
existz, would you mind posting all the voltages for the frequencies in 0.4.1. I'm still having trouble getting my phone stable.
[Captivate Android Development] upNsmokeAllDay:
Went back to the previous release and got it the custom boot screen back. Decided to use sgs kernel flasher instead of clockwork to flash the new release and I still get the samsung boot screen back. Clueless here and that doesn't normally happen to me :(

Other people in the thread are having the same issue with continuum.
[Captivate Android Development] mrhaley30705:
No problem here with Continuum boot animation after 0.4.1.
[Captivate Android Development] existz:
Try deleting the bootanim and re-add it, pull it from the rom zip.

Sent from my SGH-I897
[Captivate Android Development] existz:
You can see the voltages in VC. They are all still default for 100-1000, just in previous builds it was putting an extra 25-50mV on 800 step, then a couple higher frequencies were wrong. This was only in the last build or 2, they are set back to how they always been. Also some of the int_volt is higher on 1400/1440 builds, which will be fixed in 0.4.2 . But the lower frequency builds are still how they use to be (1000, 1200)

But also remember, you may have to tweak your UV settings from build to build, ..if there was any changes that might reduce cpu load, keeping it at lower frequencies, then it will spend more time at the lower steps and what might have been stable before might not be stable now...since its spending more time on that frequency...or vice versa if something changes to make it scale up quicker to help smoothness...then you might have to tweak them since its spending more time at different frequencies.

Sent from my SGH-I897
[Captivate Android Development] IDoMy0wnRacing:
I don't know if this is the DIY auto brightness fix eZistZ is refering to.

I haven't tried it yet. http://xdaforums.com/showthread.php?t=1130336
[Captivate Android Development] kodos96:
Question for you and anyone else who still isn't getting the custom boot animation (after the first boot).... are you on rfs or ext4? (i.e. do you have 'lagfix' enabled or disabled)?
[Captivate Android Development] upNsmokeAllDay:
Ext4 lagfix enabled
[Captivate Android Development] alexige:
That worked. I had the same issue.

I have EXT4 fs.
[Captivate Android Development] tkjeeper:
Two different roms now, the 1440 kernel, both big mem and normal, battery life is good, but when I charge it we heat up like a beatch and won't charge, have to flash back to 3.2 in order to stop the overheating. Any suggestions?

Sent from the frozen tundra known as Canada.
[Captivate Android Development] mrhaley30705:
Check cpuspy to see if its charging at 1400mhz. Should charge at 100mhz on wall charger, 200mhz on usb.
[Captivate Android Development] FredWorrell:
I have found that this kernel messes with Google maps and the internal compass. Anyone else notice this?
[Captivate Android Development] alexige:
Like it wont hold the gps location well or just compass? Hold is having issues for me, don't want to.put it on the kernel but I think it started when I installed the kernel.
[Captivate Android Development] FredWorrell:
What I'm noticing is that anything to do with the compass won't work, not the compass in google maps or any other for that matter. Google maps just hangs and won't show a pointer, just a dot. I'm currently running Apex 8.1, but I tried it on Mosaic V and the same things happened.
[Captivate Android Development] tkjeeper:
Well, back on 3.2 now and working fine, charging at 100, so what's the solution if it is charging at 1400?

Sent from the frozen tundra known as Canada.
[Captivate Android Development] alexige:
I don't have that my compass works fine on continuum 6.1.
[Captivate Android Development] mrhaley30705:
Don't use it. Try the 1300 or 1200 version. Also go to irc (#suckerpunch) and make sure existz knows.
[Captivate Android Development] manny05:
Ah I see. I'll deff keep an eye out for that if the problem comes up again. But so far everything is running smooth :D
[Captivate Android Development] topiratiko:
Any chance of a boot animation fix for 4.2 Existz?

Sent from my 2.3.4 Ext4 Fresh Ginger Blue equipped Samsung Captivate.
[Captivate Android Development] WickedNite:
What is the default value of the voodoo color in 0.3.1? I still want that value and I can't apply it now on 0.4.1, finding a hard time to make it look normal.

Sent from my Captivate
[Captivate Android Development] existz:
What bootanimation fix? bootanimation works fine for me...stock and custom... if its not working for you, just delete yours and re add it.. see if that works.
[Captivate Android Development] topiratiko:
tenfour

Sent from my 2.3.4 Ext4 Fresh Ginger Blue equipped Samsung Captivate.
[Captivate Android Development] chappatti:
THIS IS MY READING OF THE ISSUE. PL DON"T GO POSTAL ABOUT WHAT I SAY !!!!!!

The problem: In GB kernels, except some stock versions, the screen baclkight/brightness does not adjust properly to ambient room brightness. It will at the most do 2 steps of adjustment. For example, in Froyo using my GPS on car dash (good sunlight) I can see the map without problem. In GB though I cannot see the map.....only very faintly. I have to manually set the screen to MAX brightness or near so to get my map visible. The auto brightness setting does not proper to adjust to the total lux value it receives. This may just be a settings problem, where the MAX brightness value under auto brightness is set too low, or it may be a actual failure of the sensor "driver" that it does not measure the total incident light accurately. This seems to be the case if one reads the linked forum on the above post, and other arguments there.

In Talon 0.4.1 there is a really good improvement in the auto brightness responsiveness. I do not have to set the brightness MANUALLY when I am using it during the day (not just GPS), but the screen still just adjusts between "low", "medium" and "high". This is NOT how the phone is supposed to work compared to Froyo...where it has at least 5 step adjusment or so. This has remained a sticky issue, and for some reason keeps breaking with every custom rebuild of kernel..even in updating a kernel.

So it still needs a permanent fix. I have not tried a COMPLETE stock ROM of GB. I am doing that right now and will see if the auto brightness is a STOCK issue...I need to find whether this is so from first hand experience.

BTW, Talon kernel 0.4.1 is till very great because well it is great !!!!:D:D I love the screen color hacks since vodoo color is finally incorporated into GB. Great work !! Now if we could only get sharpness also a fix !!!!!;););););)
[Captivate Android Development] IDoMy0wnRacing:
Have you Tried calibrating the compass? Mine is working is why I ask.
[Captivate Android Development] crazililazn:
Sharpness is a hardware issue, specifically the pentile matrix instead of the usual RGB matrix.
[Captivate Android Development] harpo1:
What lockscreen are you using?
[Captivate Android Development] Reynaldinho111:
Has anyone seen an issue with the stock music player? Every now and then when the screen locks and im playing music my phone has a seizure and reboots. I cant reproduce it, seems to be random. Thought it was a rom issue so I posted in the mosaic thread but it just happened on apex 8.1. :confused: On mosaic I was running zachs modded snail kernel and right now im running 0.4.1 oc to 1400 no uv. Just wondering if anyone has experienced this too.
[Captivate Android Development] watsa:
Are u having AT&T bootloaders?
[Captivate Android Development] mrhaley30705:
Which lock screen are you using?
[Captivate Android Development] Reynaldinho111:
Yeha I am using the HTC bootloaders, didnt even consider that being the problem.

MIUI
[Captivate Android Development] watsa:
If you are using AT&T BL then try using music player from captivate GB rom, else switch over to I9000 BL. your problem will be solved.

Edit: If you see apex installation instructions, they suggest using I9000 BL, this is the reason.
[Captivate Android Development] Reynaldinho111:
Watsa you are a genius :P Thanks man.
[Captivate Android Development] mrhaley30705:
Try a different lockscreen, or a different player with miui.
[Captivate Android Development] tkjeeper:
Sorry exists, had to bail on the talon kernels. Just too many issues with heating up while charging, even the "safe" kernel, 3.2, started

Doing it as well. On apex 8.0. Between that and my kernel flasher getting broken while trying all the different talons to find one that wouldn't fry my battery, it's just too many negatives.

Back to dark core for me.

Sent from the frozen tundra known as Canada.
[Captivate Android Development] Sqb:
Lockscreen and music players see the culprit to most of the full speed cpu running during charging. Miui is bad news in my experience. Using puzzle lock now and the phone behaves beautifully during charging then comes out of the cage like a rabid dog when in use. Awesome work existz.

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] kodos96:
Is your phone running at a higher clock than it should be while charging?

The battery getting warm while charging is normal - it won't happen every single time, it depends on lots of factors, mostly physical factors unrelated to the kernel. So its not really something you need to worry about unless it's a symptom of the phone staying at too high a clock during charging.
[Captivate Android Development] pikachu01:
Did you install Go SMS by any chance?
[Captivate Android Development] bulawayo:
No bootani problems for me either
[Captivate Android Development] x3nhydr4lutr1sx:
The phone starts discharging once it reaches 100% on the AC. It wasn't doing that on 3.2. Although it says 100% while connected, disconnecting shows 70%.
[Captivate Android Development] kodos96:
That sounds like just the infamous "gingerbread charge bug", which affects all samsung gingerbread releases, and nobody's found a solution to yet.... so yeah, it probably was happening on 0.3.2, you just didn't notice it.

I've never heard of the "charge bug" getting all the way down to 70% though.... when it did that, did you check the charge a few minutes after taking it off the charger and see if it had adjusted upwards? It does that sometimes.
[Captivate Android Development] pikachu01:
Check the apps you've installed. Probably draining your battery while it's charging. Go sms recently had a 100% CPU leak bug on SGS. Go to terminal emulator and enter "top".
[Captivate Android Development] grkmaster:
existz, still getting the same thing. Happened when i first flashed RC3 with the new kernel, had flashed back to 1.2 and still same thing. In RC2 with 1.2 I had no issues. Anything else you think i can do?
[Captivate Android Development] jjtitus098:
Is no one else getting random reboots? Ill be doing something and ill lock the phone and it will go to bootanimation and reboot. Doesn't do it every lock. Don't know what is going on.
[Captivate Android Development] existz:
Check /etc/init.d/ and see if any scripts inside it are setting certain frequencies, if its happening on both kernels but started with RC3, but not RC2, then something in RC3 is setting it
[Captivate Android Development] harpo1:
What ROM and lock screen are you using?
[Captivate Android Development] F1reEng1neRed:
What happens if you wipe voltage in CWM and don't set any? Does it go to default?
[Captivate Android Development] Doug8796:
u guys should all work togethre with escapist and others to get some serious OC power.. this kernel has good promise.
[Captivate Android Development] F1reEng1neRed:
Something is absolutely killin' my battery. I'm down to 75 in less than 2 hrs unplugged. I checked what's using most battery and it looks like Google Maps is using alot more battery than any of the Froyo ROM's did unless GB is just reporting differently. Anyone else seen this?
[Captivate Android Development] existz:
UPDATE

TalonDEV-0.1.3

Revert back to old touchkey driver

Fixed Issue with KTLO

Compiled sound/soc/codecs as 02
[Captivate Android Development] jjtitus098:
I'm using Juwes 4.1 i9000 rom. I know its i9000 but seemed to be stable with xcal's kernel and others have been using it just fine. I'm using the android lockscreen. I'm probably going to go back to a Captivate rom after all this.
[Captivate Android Development] harpo1:
Try a different lock screen. I believe the android lockscreen was causing this on some ROMs.
[Captivate Android Development] harpo1:
So from here on out do we only install via odin? I notice you don't have the cwm3 links anymore. Plus cezar now requires the kernel be flashed via odin before installing his ROM.
[Captivate Android Development] existz:
Yea for now anyways...better chance of not having a bad flash
[Captivate Android Development] Dlev7:
Hey, if im on Darky 10.0 with Dark Core kernel 2.1 based off of Voodoo.

If I disable my lag fix can I flash this kernel on top via Odin. Just making sure I dont have to flash back to stock.

Also can I use SGS Kernel Flasher to flash this? I flash Dark Core kernel over X'Cals via. the kernel flasher app and it worked but does it work with this?

Thanks!
[Captivate Android Development] kodos96:
So I'm not sure if this is a problem with Talon, or with Perception, or with Galaxy Tuner, but since flashing perception II beta 1, Galaxy Tuner locks up when I try to go into its Sound screen. Logcat shows: "[ERROR] ssound: version magic '2.6.32.9 mod_unload ARMv7 ' should be '2.6.35.7-I9000XWJVB-CL118186 preempt mod_unload ARMv7 '"

Any ideas how to fix this? Or set my eq settings manually instead of with Galaxy Tuner? I can't live without my 5 band parametric EQ!
[Captivate Android Development] existz:
AFAIK galaxy tuner isnt updated for gingerbread yet...looks like its looking for 2.6.32.9 ...when its 2.6.35
[Captivate Android Development] harpo1:
Can you explain why this is? I intitially flashed the test kernel via recovery and now through odin and I don't see a difference. Everything seems the same. I'd just like to learn what the difference is. Plus it's nice to have the capability to change on the fly if need be.
[Captivate Android Development] MarlowXim:
Any reason why you decided to go o2 compile for soc sound. It compiles with o3 without any problems.
[Captivate Android Development] know8677:
This will probably just be another one of my dumb questions, but is there any chance of putting BLN in this?

I know it's likely not at the top of the priority list, but that is one of my favorite features in Android.

Since I'm on Continuum 5, I don't feel like I can try another kernel (at least for now) and I sure miss the lights when I get messages, emails, etc.
[Captivate Android Development] existz:
O2 seem to be more stable, we had this issue with froyo...also seems to have fixed the crackling/popping issue some were having playing music while using headphones/Bluetooth
[Captivate Android Development] existz:
Kinda waiting around to see if Neldar will port it for i9000 gingerbread, but Ive been messing with it some...everything that worked with 2.6.32 froyo wont work with 2.6.35, the code has changed alot, so alot of things will have to be rewrote or ported over...we have to basically start clean with everything and make it work with 2.6.35

Pretty much take everything you know/knew about froyo and forget about it...think of it as starting from nothing and working our way back up

On a side note, for those wanting to use custom bootanimation.zip, rename /system/media/bootanimation.zip to sanim.zip...i added it to the OP
[Captivate Android Development] Yuna:
never happened for me on 0.2 and jvb.
[Captivate Android Development] mrhaley30705:
Its very random
[Captivate Android Development] DON2003:
what is the best color setting?

also my notification tones seems low, any tips on adjustment?
[Captivate Android Development] tkjeeper:
not normal hot, brutal hot, and it doesn't charge when this happens.
[Captivate Android Development] tkjeeper:
yep, it's all I use, I know the issues with gosms, but this charge issue doesn't happen with darkcore, only talon. Is there a solution for it, because it was happening across the talon spectrum of kernels for me. Too risky.
[Captivate Android Development] FredWorrell:
Issues are gone now.

I flashed all the way back to stock and started fresh on Apex 8.1 and 4.1 Talon. All of my previous issues with the compass and apps hanging are gone. Runs greats now.
[Captivate Android Development] melvinaury:
Great Kernel
[Captivate Android Development] topiratiko:
Anyone have any info on vr sccheduler?

Sent from my 2.3.4 Ext4 Fresh Ginger Blue equipped Samsung Captivate.
[Captivate Android Development] krufttangoud:
it is very similar to SIO, I prefer VR, but you can test both and see what works best for you.
[Captivate Android Development] zacharias.maladroit:
The V(R) I/O Scheduler
[Captivate Android Development] Beny The Kid:
What did you use to go back to stock? I only ask because I used DGs JF6 one click and then I used the Apex installer package, which just basically installs new boot loaders and a kernel with CWM and then flashed 8.1....still had the lag with Talon, especially with Go SMS. However, when I flashed darkcore everything was wicked fast......I'm not very techie but if someone could explain why, I would appreciate it......I usually run Existz kernels on any custom ROM that I run......
[Captivate Android Development] Rhiannon224:
Use this method http://xdaforums.com/showthread.php?t=995143. It won't touch the bootloaders, I use it and have zero trouble. Follow the guide and you should be good to go. You should do a data and cache wipe from recovery before flashing stock for a clean install.
[Captivate Android Development] bballer182:
Interesting read. Curious, how does this apply to solid state media? I understand about the spinning disk, but we have SD flash storage.
[Captivate Android Development] crazililazn:
I'm not sure if this is a kernel issue or not, but lately I have had issues sending text after having my phone on for awhile. A reboot fixes it, but once my phone has been on for awhile, it happens again. I'm running TalonDev 0.4.1 on Serendipity VII Build 2.