yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] backdownup:
Sorry man. Basic install of your kernel drained to 15% in 12 hours with about an hour throughout the day of checking text messages (approx 20 text messages checked and 12 sent).

Reflashing to stock kernel(With no other changes at 100% battery), with Dolphin HD browser usage, and Poweramp music player used for 13 minutes, plus 34 text message checks/22 sent. After 12 hours I'm at 65% battery.

Explain.

It's not battery behaviour. When I got home with 15% left, I watched an episode of futurama, got half way through and powered off. I powered on the phone, opened the episode and it immediately powered off. The power button did not work after that.

I did the same thing with my stock kernel (Except this was a day and a few hours after my 12 hour test) by turning on futurama (Same episode, same player) and waiting for it to die... I waited, watched the same episode 4 times. It finally died at 11am the next day. I turned it back on, watched the same episode another 1.5 times. It died again. This time it would not turn back on.

It's not some power saving feature for the battery. It's broken. I'm not trying to be a ****, just telling you my experience.

EDIT: If it makes a difference. And I am thinking it may, I'm with Rogers in Canada with a brand new Captivate.

EDIT 2: I realize this is my first time complaining... so I'll satisfy all of the people I read in here.

I disabled wifi from the second I unplugged my phone both times. I switched to GSM only (No HSPA, we have that luxury in Canada Captivate). I have juice defender installed (I didn't use it for the stock kernel test). I have Droid Wall installed and active and blocking EVERYTHING except my mms and dolphin and a few other key apps. I ensured I had nothing running during these tests). My AB is off and my brightness is set at the lowest setting. I've bump charged and drained and bump charged several times.

The battery log showed 96% screen usage.

So, no. I'm not a noob.
[Captivate Android Development] backdownup:
You don't have to. But you could respect other people... that would be a start.

EDIT: Oh wait. You are the gentlemen that did the serendipity rom. I expected more. Way to contribute to the community.
[Captivate Android Development] ease_the_pain:
Friends ,there is no need to be aggressive; we are using this kernel with many other roms, mine is serendipity 5.0 .

I never experienced the battery drain problem so there must be another issue except kernel and battery.
[Captivate Android Development] tietherope:
I would suggest downloading the app "spare parts" from the market. Open it up, pick battery history > partial wake usage. Here you will be able to tell if there is a program or process not letting your phone go into sleep mode. It happens to me from time to time and a simple reboot fixes it.

Also open your phone settings and go to about phone > battery use > cell standby. If there is a time without signal percentage displayed that is an issue too. It will most likely be 50%. I have this every morning and switching to airplane mode for 30 seconds and then back will resolve it. After that you will see the time without signal percentage dropping quick.

Those are a couple things you could look into regarding battery life that are outside of the kernel and make a big difference for some people.
[Captivate Android Development] skoNuff:
I just have a quick question... I'm already using Speedmod in my Serendipity rom. Can I just simply flash the updated version of this kernel via CWM and be good to go? It's that simple correct?
[Captivate Android Development] hardcore:
Yes u can.
[Captivate Android Development] hardcore:
Also download an app like Android Status and check cpu usage on idle and also any process that may be stuck running and using cpu continuously.
[Captivate Android Development] grkmaster:
I went into recovery and enabled the lagfix to ext4 from rfs and now after it backed up and restored everything, im getting all my programs to FC ... other than redoing my whole rom, what can i do?
[Captivate Android Development] bpodz34:
Recalibrateing your battery may help your issues. Just search xda for a guide.

Hope this helps :)
[Captivate Android Development] JGGW:
From what I understand, Hardcore's speedmod kernel is not an OC/UV kernel. check out glitterballs' kernel if you want to play with that stuff.

I am running cog 3.04 with speedmod k13A and ZNKP1 modem and as you can see on the left side of this post, I am canadian. Moderate usage I can get 36 hours out of this setup. Hardcore, my hat is off to you as always for a great Kernel.

when you say you restored everyting did you restore system data with TiBu? Also, ext4 should be enabled by default if I am not mistaken. It was for me when I installed the kernel.
[Captivate Android Development] grkmaster:
Well i already had everything restored and was working fine before the lagfix but I had forgotten that lagfix was not enabled by default so in recovery I clicked on Enable lagfix. It restarted and I clicked Yes on the conversion and it backed everything up and restored afterwards.

Everything started FC when it first booted, THen after wards when i started opening individual apps.... I know uninstalling the apps and reinstalling them the FC dissapeared, but i dont wanna do this for 100 apps. That would be a pain

.. Im just going to end up doing the lafgix with factory reset and no backup and then just go back into titanium and do my restore that way since all my stuff was backed up last night anyway before I did a new rom.. But for future purposes what can be done to avoid this? Pretty much what im doing now?
[Captivate Android Development] doreyu:
Try deleting the dalvik cache via CWM
[Captivate Android Development] skoNuff:
Thank you hardcore.. Last question, which version should I flash, K13A or K12U? Serendipity currently uses K12S-T3 so I'm assuming I stick with K12U right?
[Captivate Android Development] slifer315:
serendipity uses that because that was the current kernel when Mikey released that rom version. k13a is the most recent version of this kernel and is therefore the recommended version to use.

Sent from a phone, playing a phone, disguised as another phone.
[Captivate Android Development] zuNcHAN:
You can try out the SuckerPunch kernel which is based off this Speedmod kernel, except with OC/UV.
[Captivate Android Development] TheDude:
Lmao, watch it Mike! If you damage their delicate and fragile self esteem they will report you! I know! But im with you Mike... crazy noobs ;)
[Captivate Android Development] TheDude:
Btw, this kernel is hardcore! Thanks for your work man! My battery rocks and my device is hella fast!
[Captivate Android Development] xreflection:
Running Darky's 9.2 with K13A and my phone is so fastttt. I love it.
[Captivate Android Development] rlamontjr:
didnt know if it is a kernel or rom thing. but when i am on the phone and i receive notifications (text, app, alarm) i heard no sound. just get the words in the top bar.
[Captivate Android Development] xThe Enforcer:
Speedmod = One of the best kernels ever!
[Captivate Android Development] delugeofspam:
Quoting myself from Cognition thread:

Turns out this actually isn't a ROM problem, it's related to the Android logger. I turned logging on so that I could reproduce the error and it went away entirely. I turned logging back off, thinking "must have been some quirk that went away because I rebooted" and the error came right back.

I'm thinking phone.apk is somehow dependent on the logs to tell it whether or not a call has been sent from the notification drawer. I don't really expect you to fix that as it's not much kernel related at all and the error is VERY minor. Just figured it should be known.
[Captivate Android Development] JGGW:
change notification settings in the sms app you are using to enable them.
[Captivate Android Development] rlamontjr:
it doesnt make a difference.
[Captivate Android Development] Johnston212:
Lol, just had to but in here and express my surprise/growing addiction at the fact that Hardcore hasn't released a new version of Speedmod in 6 days.
[Captivate Android Development] perosredo:
I flashed to the latest Speedmod on my stock froyo (I896). Well, not so stock anymore, am running the KP1 modem now as well.

Couple of questions:

In 'About', I only see 2.6.32.9 under Kernel version--no mention of speedmod; the update was succesful and I do get the custom Speedmod recovery and my screen is darker. Is the lack of an update to the Kernel version normal?

What's up with the 'extra' bootscreen? I now have my regular, plain, consists entirely of 'i897' as well as a more crowded 'Galaxy I897 Samsung' bootscreen.

I had something else but I forgot...
[Captivate Android Development] MikeyMike01:
It's quiet.

Too quiet.

Sent from my Captivate.
[Captivate Android Development] ryude:
You mean we finally get to use a version for longer than 1 day?
[Captivate Android Development] vvaffles:
is there anyway to change the picture at boot for the kernel, theres one that just saids Google that i snatched off cyanogen forums that i would love to have
[Captivate Android Development] ryude:
You have to re-compile the kernel in order to change the boot image.
[Captivate Android Development] JGGW:
kernel version 2.6.32.9 is normal

Hardcore added that screen to his kernel, I have the same problem. When you modify the Canadian version the boot screens are found in different places compared to the american versions (from what I understand), so there are two.
[Captivate Android Development] wibs:
Look out Fox, its a trap!
[Captivate Android Development] Barbarian:
LOL. Do a barrel roll!

Sent from my Captivate running Supernova
[Captivate Android Development] mengbo:
no new release for this kernel ?
[Captivate Android Development] Johnston212:
No you don't. I've fixed the boot image and I just got Root Explorer or Droid Explorer and changed the .zip file to bootanimation.zip and that's all it needed.
[Captivate Android Development] Johnston212:
No you don't. I've fixed the boot image and I just got Root Explorer or Droid Explorer and changed the .zip file to bootanimation.zip and that's all it needed.

Forgot to quote the message there, lol.
[Captivate Android Development] Fortune090:
That's not the boot image, that's the startup animation. ;) The boot up animation is the one that says Samsung I897 after the ATT logo.
[Captivate Android Development] existz:
The actual kernal boot image does have to be compiled in the kernel, which is right after the white att screen, the bootanimation.zip is different, which can just be swapped out with root explorer ,which is displayed right after the kernel boot image

Sent from my Captivate
[Captivate Android Development] xreflection:
There are technically 3 different boot screens. Theres the ATT one, which I changed after I flashed to 9.2 Darky. Then theres the one that says Samsung I897 or whatever, then theres the bootanimation. The bootanimation is the only one that can be changed easily (as said before). The other two need extra steps. The ATT logo specifically can be replaced if your rom somehow did not contain a logo_ATNT.jpg file.
[Captivate Android Development] Johnston212:
Ohh, well in that case let me know. While I LOVE Speedmod, the rather bland boot ani is something I would like to improve upon.
[Captivate Android Development] hardcore:
K13B: 16-Feb-2011

- Internal SD USB mount now works in Recovery mode

- New Android lowmemorykiller tweak: Increases usable RAM by 12MB

- Voice calls over headphones are louder
[Captivate Android Development] zerkai:
Sounds awesome! I'm on it! By any chance do you have a to do list? I keep thinking what's even left you could possibly do for this kernel!
[Captivate Android Development] Ikonomi:
Thank you for the update, hardcore. Gonna flash in a minute. The new memory tweak sounds interesting.

SGH-i897 | Perception 10.2 | SpeedMod K13A | TLJL3
[Captivate Android Development] :
I've noticed an increase in battery use. Anyone else seeing this?

Sent from my mobile
[Captivate Android Development] tietherope:
Someone will yell at me but spreading the news that Froyo has been released by AT&T.

http://www.engadget.com/2011/02/16/samsung-captivate-on-atandt-gets-android-2-2-all-that-froyo-hasn/

Edit: The page was removed, Samsung is just playing mind games now.

http://webcache.googleusercontent.c...&gl=us&client=firefox-a&source=www.google.com
[Captivate Android Development] n0stalgia:
Since K13A, yes.
[Captivate Android Development] ratatouille:
Hello, congrats for your work.... Is the 720p recording the only difference between K13B and K13BBIGMEM?
[Captivate Android Development] :
Im intrested in this tidbit. Do we actually gain 12 more MBs?
[Captivate Android Development] :
I went back to 12u and i'm getting a lot better battery life.

Sent from my mobile
[Captivate Android Development] existz:
Are you releasing sources as well for k13b?
[Captivate Android Development] hardcore:
Sure thing! It's up now.
[Captivate Android Development] hardcore:
No you don't gain more RAM in the usual sense, but more RAM can be used by apps before the Android memory manager starts killing them. Basically before, you can use up to about 290MB/339MB RAM, but now it can go up to 304MB/339MB or so.
[Captivate Android Development] nakedninja42:
hardcore, is it still necessary to apply the startup script anymore? I still go though the process since k12L, but was wondering if it still applicable today (even though K12L was a month ago)
[Captivate Android Development] MikeyMike01:
F*CK YEAH

You have no idea how many soft bricks that would have saved.

Sent from my Captivate.
[Captivate Android Development] sinichi21:
hardcore was wondering does this update include the dock audio?
[Captivate Android Development] hardcore:
Still recommended to apply them via recovery menu.
[Captivate Android Development] hardcore:
Not yet. I think there were still some issues with the patch, like some audio routing issue? But I haven't checked it recently.
[Captivate Android Development] nickfranky:
This Kernel works with Armani i9010???

Hi All!

I'm new in this post, this area, try to make good relationship with android. Just bought my new android phone, a galaxy s i9010 armani.

I like it very much, but not for the battery life. This speedmods, and kernels works not only with Captivate, but Armani as well???

Using samsung shipped original rom, what should i do for a better battery life, and speed for smooth reactions?

Thanks for any help!

(Or is there a forum for Galaxy S i9010 Samung Armani? ) :confused:
[Captivate Android Development] hardcore:
Not 100% sure but the i9010 sounds closer to the i9000. So u should be looking at the i9000 version of this kernel.
[Captivate Android Development] jaxf250:
Same here - I went back to 12U and my battery life got a lot better.... wonder what changed? HC any ideas?
[Captivate Android Development] trekie86:
What startup script are you talking about? I've gone through all of the recovery menu settings and haven't found anything. Please enlighten me.
[Captivate Android Development] nakedninja42:
check the OP, there is a link near the bottom of the first post that mentions the tweaks, go to the link and it gives a startup script and instructions for pushing it to your phone from ADB. It was my first successful attempt at using ADB :)

Edit: Went and grabbed it for you http://xdaforums.com/showthread.php?t=813309
[Captivate Android Development] nakedninja42:
Wait, so using this link http://xdaforums.com/showthread.php?t=813309 is different than what is mentioned in the OP? I alway make sure that the first 4 are enabled under Tweak in the recovery, is that what you are referring too?

Also, never understood if I was to apply this somehow

"

CONFIG_ANDROID_PMEM_MEMSIZE_PMEM=2048

CONFIG_ANDROID_PMEM_MEMSIZE_PMEM_GPU1=4096

CONFIG_ANDROID_PMEM_MEMSIZE_PMEM_ADSP=1500

CONFIG_WLAN_SAMSUNG_MEMSIZE_BCM=256

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC0=12288

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC1=1024

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC2=12288

CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC0=32768

CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC1=32768

CONFIG_VIDEO_SAMSUNG_MEMSIZE_TEXSTREAM=10240

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMD=3072"

or is that just a statement of what the kernel has as its settings?
[Captivate Android Development] existz:
Hardcores startup speed tweaks script is the samething thats in recovery under TWEAKS, theres no need for the scripts anymore..the settings in the startup speed tweaks thread are out dated compared to whats used in TWEAKS in recovery, which is prefered, so theres no need for the startup scripts...

As for the memory settings, those are just letting you know what settings are used in the kernel, they are not configurable unless you compile the kernel yourself
[Captivate Android Development] trekie86:
I thought that was the same thing that is in the TWEAKS menu in Recovery. So I guess I'm good to go if enabled the tweaks. Thanks.
[Captivate Android Development] nakedninja42:
Exactly what I needed to know, thanks for the reply
[Captivate Android Development] GGXtreme:
Well, this is unexpected. I installed K13B and now USB mounting in Android does not work for me anymore (phone says it is mounted but it isn't detected by any of the computers that used to see it just fine, tried all USB ports). Droid Explorer sees my device just fine though. I'm going to see if going back to K13A fixes the issue.
[Captivate Android Development] reinbeau:
I installed K13B this morning and then connected via USB to my computer to pull some wallpaper onto the sd card - no problems here.
[Captivate Android Development] wibs:
1 day and 8 hours so far and still 15% battery! 2.5 hours of display and 25 minutes of voice calling, along with checking gmail and word feud throughout that time... awesome!
[Captivate Android Development] mozillacn:
K13B is poor. it consumes much more battery than K13A.
[Captivate Android Development] michaelmenavargas:
Cognition 3.04

Hi, any body knows if this kernel is working good on cognition 3.04 rom including voice bluetooth calling thank you....
[Captivate Android Development] redjersey:
I tried k13a and b, and decided to switch back to k12u

k13 just drained my battery like crazy, I have lost 50% in 8 hours (from 7am - 3pm no phone calls, no sms, no nothing)

switched back to k12u, made a few changes in ultimatejuice, used autokiller instead of task manager, now I just lost 2% in 5 hours (1am-6am)

lets see how it goes the rest of the day and will report back here :)
[Captivate Android Development] xreflection:
I have to agree that K13 seems to eat up a lot more battery. But it seemed to get better after I calibrated and had a few charge/discharge cycles. I'll try that with K13b and see what happens.
[Captivate Android Development] dbaser:
I am feeling the same way. I'll reserve judgment on k13b after a few more cycles. It does appear to be consuming more battery than k13a at this time though...
[Captivate Android Development] hardcore:
There are no changes that could account for battery differences so it's probably just the usual battery meter inaccuracies. A reboot with usb unplugged and a few charge cycles should bring it back to normal.
[Captivate Android Development] dbaser:
That's what I was thinking and why I said I would reserve judgment.. :)
[Captivate Android Development] mattsternc:
That's been my exact experience on 13A. It was taking the battery down pretty quickly, but after a few cycles now it's been a lot more consistent! :D
[Captivate Android Development] xreflection:
Yep. I like how smooth K13 is overall anyway, so I'm going to give it a few cycles.
[Captivate Android Development] JGGW:
used k13A on cog 3.04 with jk4, tlj3 and kp1 modems. great combo!
[Captivate Android Development] Johnny Paranoid:
I'm on Cog v3.04 and I flashed SpeedMod vK13B over Firebird 2 v.09. Everything was good at first. I cleared Dalvik and enabled all the recommended tweaks and enabled the lagfix. Later I disabled the lagfix and I started getting all kinds of strange FC's I never got before. So I rebooted and now my phone will only boot to the Cognition screen and stays there. The screen turns off but if I push the power button it's still on the Cognition screen. Any idea what went wrong? I'd hate to wipe and re-flash the ROM if I don't have to.

EDIT: Nvm, I'm just gonna re-flash.
[Captivate Android Development] xdahgary:
love your work hardcore. Was wondering if your kernel has the audio thru USB fix and if not, can you add it in your next build. Thanks in advance.
[Captivate Android Development] color0:
So this is an "issue" I've mentioned before in other threads, thought it might be worth re-hashing over here as I don't think it's been covered (at least recently).

When flashing K13A and K13B onto my Captivate (formerly Cog 3.04, now Serendipity 5.9), a ClockWorkMod flash will sometimes cause the phone to cease booting successfully -- it'll get stuck at the AT&T screen. SGS Kernel flasher doesn't work either, same issue. When these two methods DO work, the phone will boot but the battery life is very poor, less than 12 hours.

The only solution that works for me is to download the TAR file off Hardcore's site and flash it manually using Odin. Everything goes smoothly, no boot issues, VERY good battery consumption: I'm dropping less than 1% an hour, theoretically we could go for 4 days on a charge.

Has anyone else observed this phenomenon? Also, the EXT2 lagfix is significantly faster and more battery-sipping than the EXT4 or EXT4NJ options. I haven't encountered any reliability problems so far aside from the boot issues, so why are so many lagfixes still centered on EXT4?
[Captivate Android Development] krufttangoud:
call quality on Speedmod K13B

Is there another Version that has a better call quality similar to the stock Samsung kernel? The people I call can barely hear me when I call them.

Thanks in advance,:confused:
[Captivate Android Development] dbaser:
Maybe they really don't want to talk to you and pretend like they can't hear you... j/k

Call quality is fine for me on AT&T with the JK4 modem. YMMV.
[Captivate Android Development] krufttangoud:
could you post jk4 modem zip? I tried to find it, really.
[Captivate Android Development] dbaser:
Look harder. It's in the modem thread.
[Captivate Android Development] krufttangoud:
It keeps downloading as a bin not a .zip. Is that the file I should execute when in recovery mode. Instructions say it should be a .zip
[Captivate Android Development] xdahgary:
KP1 crazy fast data and loud in call volume. Very nice. ymmv.

JK4:

http://xdaforums.com/attachment.php?attachmentid=463394&d=1292262582

KP1:

http://xdaforums.com/attachment.php?attachmentid=490494&d=1295122989
[Captivate Android Development] Johnny Paranoid:
http://xdaforums.com/showthread.php?t=876391
[Captivate Android Development] krufttangoud:
UCJJ4 - AT&T Captivate (Uses WCDMA 850 by default)

UCJI6 - AT&T Captivate (Uses WCDMA 850 by default)

XXJPP - European GT-i9000 (Does not use WCDMA 850 by default)

XXJPM - European GT-i9000 (Does not use WCDMA 850 by default)

UGJK3 - Bell Vibrant GT-i9000 (Uses WCDMA 850 by default)

UGJK4 - Bell Vibrant GT-i9000 (Uses WCDMA 850 by default) Thread

SO JK4 is ok for captivate?
[Captivate Android Development] jhernand1102:
Yes JK4 is fine, that is what I'm on right now. It will vary by location as to how good they work so I suggest you try a few to find what works for you.
[Captivate Android Development] mykwalkr:
Not trying to Hijack...

Is it safe to say that these are Clock Work flashable?
[Captivate Android Development] LightningGA:
Yes JK4 is a great modem to use with the Captivate. I've been using it for a while now.
[Captivate Android Development] LightningGA:
Yes they are.
[Captivate Android Development] dbaser:
Now back to the SpeedMod kernel discussion...

I'm sure hardcore doesn't want us hijacking his thread (I'm guilty as well...)
[Captivate Android Development] krufttangoud:
Thanks!!

Thanks for the help. I have never posted in the forum before for help. Its nice to not be lambasted by people who have the knowledge to help.

Your suggestion was right, blazing fast, call quality as good as stock.

Thanks again.

Can't for the next speedmod update.