yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] airbillion:
Hey exstiz,

Are you planning on adding any of hardcore's latest kernel tweaks from his new speedmod k12u version?

-O3 compiler optimizations except for sound soc codec

-Kernel scheduler tweak modified (improves GPS response)
[Captivate Android Development] mkr14:
Give it a shot and try it. I have seen reports of -100 working for people at 800. Just make sure you do not activate more than 7 steps as recommended by the the Voltage Control software.
[Captivate Android Development] existz:
Test Version #39

-New frequencies added

--100,200,400,600,800,1000,1120,1200,1300,1400

-Optimal conservative governor settings (better battery life)

-Fixed Kernel VM Tweak (Should prevent tweak from causing charge death)

Make sure to delete previous S_volt_scheduler in /etc/init.d (the order of states were changed, could cause issues)

NOTE

So I decided to compromise, I was having issues keeping all the frequencies while adding 600/900, so ..i left out the 900 as it was not being used much anyways, but I removed the 1280 step replacing it with 1300 (instead of 1360) ..Make sure to delete your previous voltage control settings, you may need to retest your UV settings as well.
[Captivate Android Development] Dlev7:
I took out the 900 as it was hardly being used at all. And Ill see how these setting sare tomorrow morning when I use the phone. Right now those settings are perfect for me and Ill just continue to play
[Captivate Android Development] airbillion:
existz,

Saw this post over in the i9000 forum:

http://xdaforums.com/showpost.php?p=11162667&postcount=12611

Hardcore:

I been using this memory configuration for a long time now and I know it works on my steam kernel without any problem. Maby you can try it out in your kernel to. Maby someone wants 350MB ram that works.

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC0=11264 CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC1=1024 CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC2=11264 CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC0=32768 CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC1=32768 CONFIG_VIDEO_SAMSUNG_MEMSIZE_TEXSTREAM=2048

Maybe you can implement this as well?

Thanks for all your work on this rom. I hope you don't mind these suggestions. I'm just trying to help make this kernel the best it can be.
[Captivate Android Development] aalh:
Battery drained overnight while phone was "sleeping"

using #36

Phoenix 4.5 rom

latest VC app

1280 1120 1000 800 400 200 100

0 -50 -50 -75 -75 -75 -75

I woke up this morning to find my phone off, thinking the shutdown issued had returned I tried to power it on, no go

I plug it into the charger to find that the battery is completely dead. It was at 100% last night

once it is turned on I find that 1360 was checked by accident, I have my clock limited to 1280 so that state was not used, I think

was having 8 states on though not used causing my phone to drain the battery?

I have never seen my phone drain the battery like this, it is like I left the screen on and it running benchmark loops, it was completely dead

last week I had it go 40hrs between charges (Phoenix 4.1 , SM -T 500), could have gone further but I wanted to xfer some files to it

****edit

I was looking through apps with logs to see if I could tell what happened to my battery last night

Juice Defender started recording constant "forced auto-sync" from 451am till the battery drained

I had wifi on but mobile data was off

what would make a log entry like that?

I uninstalled JD and rebooted since I seemed to detect strangeness around the time of installing it
[Captivate Android Development] Stephenv1971:
1.3 just came out. Looks like it no longer crashes on stock kernels for me. I thought I had a bad phone due to this bug. Probably will try sucker punch out again.
[Captivate Android Development] davwman:
Test 39 working great!
[Captivate Android Development] mrbloog:
Well it seems for me with the new test kernel, the Voltage Control app keeps force closing when detecting the clocks. And I even deleted the s volt scheduler. So can anyone help me?
[Captivate Android Development] lrs421:
Existz, you're messing with me and I know it :D

I don't see it in your changelog but MobileAP and Wifi are both working wonderfully now!

I'm going to see how the day goes. Please tell me you changed something :)
[Captivate Android Development] existz:
Make sure to reboot after deleting it
[Captivate Android Development] existz:
Lol, I promise I didn't change anything ..
[Captivate Android Development] mrbloog:
Thanks for the quick reply, but found out it was my fault with mounting with root explorer.
[Captivate Android Development] lrs421:
Well, it stopped working again :confused:

Back to my corner I go :(

It seems to work for about an hour.
[Captivate Android Development] existz:
Hey, I don't mind at all, always open to suggestions. Ill try it out and if it doesn't break anything we might be able to squeeze a few megabytes
[Captivate Android Development] r3ferrei:
Does this retain 720p recording? I remember hearing that certain memory configs remove that. Unless im thinking of something else.
[Captivate Android Development] lrs421:
Same here. I want to keep 720p.
[Captivate Android Development] existz:
Some memory configs break 720p recording, such as hardcores bigmem version, but with the mem settings above, everything is said to work. So as long as it doesn't break something I don't see why I wouldn't use those...ill try them out and hopefully have it in the next stable release

I might put a test version out later today with these just to see if everything still works

But don't worry, I wont scrafice something as important as 720p just for an extra 10mb that will never be used hardly anyways
[Captivate Android Development] joeshmoe08:
@ Existz Will you be adding the features from harcore's vesrion U in the final release of 39?

Thay are:

- Changes to color (less green)

- O3 compiler optimizations except for sound soc codec

- Kernel scheduler tweak modified (improves GPS response)
[Captivate Android Development] existz:
Ill probably add the kernel scheduler tweak. Ill look into what changes he made on the color and see... As for O3, ill probably stick with O2, but ill try it and if its noticeably faster I might switch, I personally think O2 is better, might not be as fast (most of the time you can't see the difference) but its more stable than O3 ..
[Captivate Android Development] joeshmoe08:
Alright thanks for the response. build 39 is looking nice.
[Captivate Android Development] aalh:
Is there an app other than setcpu that will track clock state use?

I am not against buying apps or donating, I have done both

but, I would rather not have to buy setcpu since it cant be used fully with these kernels
[Captivate Android Development] existz:
So far #39 has gave me best battery life, I really think the 600mhz step is working great. I've got a few other things I want to do before making it final, just some tiny tweaks here and there, like the modified scheduler tweak, and some tweaks of my own. There's more to come :)
[Captivate Android Development] lrs421:
I like the idea of the 600 step as well. No CD comments yet, fingers crossed. I hope we can move on to lrs421's issues now :) lol
[Captivate Android Development] ryude:
I'm waiting for the official word on if the charge death is fixed before I start using suckerpunch for my daily. It's looking like you might have figured it out.
[Captivate Android Development] Killemalll:
I think the free version of SystemPanel does it
[Captivate Android Development] existz:
Lol, ill get to it I promise... hopefully this takes care of the charge death for the most part, im sure a few will still have it, but ill try a few things and might get u a test build just for mobileap/wifi issues. Ill probably put a new stable release up tonite after people start commenting on the 600 step, but so far I think ill keep it.
[Captivate Android Development] existz:
I know it fixes it for most people, there was 1 or 2 that said it didn't work, but about 10-15 that says it fixed it. I still think some people need to check their UV settings, there's nothing I can do if they are to low causing it, even if they work with every other kernel, most of my settings and configs are way different (different governor settings, my oc/uv code is different, even some voltages are different than some kernels, so you might have to redo all your uv settings to be stable. (Im not directing this to you, just saying in general :p)
[Captivate Android Development] LimaI896:
Flashing #39 :D

Existz I think my CD is just my UV settings as I got it on test 38 but my phone wasn't off, just froze at full charge. Was weird to see but it makes sense as my CD was never consistent as my UV setting are never either :p

Also I got insane battery life yesterday, 22hours as I used my phone as a normal person. This is insane knowing my average is 7-8 hours on heavy use.
[Captivate Android Development] existz:
delete double post
[Captivate Android Development] existz:
Next Final Relase will Include-

-Added 600mhz step (Removed 1280/1360, Added 1300)

-350mb (720p working)

-Fixed Kernel VM Tweak (should prevent tweak from causing charge death)

-Modified Scheduler Tweak

-Tuned Conservative Governor Settings (better battery)

Im working on it now, but im going to wait on more people to comment on the latest test version before releasing an updated stable version..
[Captivate Android Development] Dlev7:
Hey Im still one build 38 but I removed the 900 step and the 600 step is the one giving me the best battery life I think i was just out for the past 2 hours texting, polling emails-1% battery drain. And I DID NOT have a charge death last night.

SuckerPunch FTW
[Captivate Android Development] zerkai:
All that and only 1%? Geez.
[Captivate Android Development] existz:
Awesome :) Theres no difference in Test Build #38 and #39 except that i removed the 900/1280/1360 step and added 1300, so you dont have to update if you dont want to, I really didnt see the 900 step helping much, i think the 600 step is the winner... glad to hear no CD :)
[Captivate Android Development] zerkai:
What frequency are you using for 600?
[Captivate Android Development] jjtitus098:
You only had 1% battery loss?! How the hell? I've never gotten that good.

Sent from my Captivate running Precision v.2.0 with SuckerPunch @ 1200mHz.
[Captivate Android Development] Dlev7:
Ya its insane neither have I but I calibrated all last night and then flashed this, the 600 step and the 800 step for me are the most used so I did the voltage centered around that, with Juice Defender, and just texting and some emails and ScoreCenter widget 1%.

SuckerPunch is insane actually and Im OC'ed to 1.2 ghz and getting the fastest scores IVE ever gotten
[Captivate Android Development] r3ferrei:
Everything is solid here on 39.
[Captivate Android Development] LimaI896:
Wow I lost 2% in 35 mins with just a couple texts. Your battery is insane lol
[Captivate Android Development] existz:
So i can confirm 720p recording works with those mem settings for 350mb. Ive went through and tested about everything i could think of and seems it works good. I probably wont label it a TEST version since theres really no testing needed, if we run into problems later on from it, i can always revert it back to 340mb. Ive already compiled #40 , ready to post it as latest stable release, just waiting to hear a few more inputs on #39
[Captivate Android Development] RonH54:
OT: I guess I am just old but I didn't realize that "SuckerPunch" is a Movie about to come out. I went to see "Sanctum" yesterday and saw the Poster for "SuckerPunch".
[Captivate Android Development] Dlev7:
My battery is typically terrible Like on a full heavy day of use I get about 12-13 hours. But today when I went out and sent out a good about of texts and stuff, and I wasnt using data much that may have done some of it but I only lost 1%. This is the best my phones EVER been.

Darky 9.2+SuckerPunch Build 38+JL3 Modem=Sex
[Captivate Android Development] RonH54:
I got same setup but I am still on 36 but will go to next Final Kernel. What Steps and UV you using on 38?

Thanks
[Captivate Android Development] Dlev7:
cfq-->-50,-75,-75,-100,-125,-125,-150.

The 600 step helps A LOT and the new settings he implemented are solid
[Captivate Android Development] Dlev7:
Ron the best way to get the best battery life for me is just disable data completely when your not using data, Juice Defender does a good job but sometimes like today I was at lunch I had no need to have my H on all the time. Just completely disabled it and was texting and I get no drain while the phone is off.
[Captivate Android Development] LimaI896:
My heavy usage is normally 6-8 hours ahaha. But that is still amazing battery life. This 600 step is going to do wonders. I see my phone more at 600hz now then 800.

Existz so far #39 has been flawless!
[Captivate Android Development] LimaI896:
Juice defender gives you the option to disable H?
[Captivate Android Development] aalh:
I could not find that option, the history button is inactive
[Captivate Android Development] Dlev7:
No I have Darkyy its in the dropdown menu where you can disable all data connections, but you can disable H completely I dont have the number punch in completely but look it up on XDA so you only get 3G which in retrospect saves more battery than H.

But I just completely disable data all together when Im not using it. On heavy usage when I get 12-13 hours is when Im OC'ed to 1200, data on the ENTIRE time, polling emails all day, and TONs of text messages. My battery is always good because I typically get home with like 8%. But with this set up according to Juice Plotter on that heavy usage that I normally do I should get 24-25 hours. : D
[Captivate Android Development] aalh:
I use Widgetsoid to switch data(H) off. I almost never have it on since I am near wifi usually
[Captivate Android Development] existz:
You can use SGS Tools to disable H, i always use 3G instead of H, awhile back i checked my dmesg and noticed it was switching from H to 3G back and forth every 30sec, killing my battery, so after disabling it and using only 3G, ive noticed a HUGE improvement in battery life
[Captivate Android Development] LimaI896:
Still pretty good battery life for that usage. My heavy usage is almost the same as yours but I am on tapa/xda a lot, wed browsing and of course my PSX app :) If I get over * hours its a good day.

Thanks I will try this out.
[Captivate Android Development] p4ranoid4ndroid:
Ive been trying to run this kernel since build 32 but I've had no long im currently using darky 9 with jl3 modem. Has anyone had success with this kernel/ rom combination? I keepgetting reboots on start or it just freezes when booting.
[Captivate Android Development] existz:
deleted post
[Captivate Android Development] Dlev7:
How do you do that? I have SGS Tools
[Captivate Android Development] existz:
Goto secret codes, then all the way to the bottom,switch 3g --hspa, choose #2, then #1 (hspa off)
[Captivate Android Development] existz:
*UPDATE*

Build #40

-Added 600mhz step (removed 1280/1360, added 1300)

--100,200,400,600,800,1000,1120,1200,1300,1400

-350mb RAM (720p WORKING)

-Fixed Kernel VM Tweak (should prevent tweak from causing charge death)

-Optimal Conservative Governor Settings (better battery life)

NOTE

This is a STABLE release, I usually dont post TEST builds, so most of the time my build numbers will not be posted as TEST or STABLE, they will all be STABLE unless posted otherwise ...
[Captivate Android Development] Dlev7:
And if I wanted to go back how would I do that?
[Captivate Android Development] existz:
Just do the same steps, #2, then choose #3 (HSDPA/HSUPA)
[Captivate Android Development] Dlev7:
Just did those steps and now I only get 3G so this should make my battery EVEN better?? Haha
[Captivate Android Development] existz:
Yep, (#2 then #1 (HSPA OFF) to disable H, then #2 and #3 (HSDPA/HSUPA) to enable H) that was probably the most noticable thing i done to save battery, helped me out alot
[Captivate Android Development] Dlev7:
Awesome! With SuckerPunch. My phone actually gets better and better every day... Thanks Existz!
[Captivate Android Development] LimaI896:
Is the battery draining from switching 3g to H all the time or just H?

If I put always on H would battery life be better?
[Captivate Android Development] Auridran:
Yes. I've found this to be the case. I've also found that only enabling the 850MHz band saves battery as well. 850MHz is the only band that works around here anyway.
[Captivate Android Development] existz:
In my case, it was cause it was switching constantly, but either way disabling H and using 3G only will help battery life
[Captivate Android Development] LimaI896:
Oh alright, was just curious as I'd just keep H enabled. I love my speed ;)

I cant find this secret code thing in my SGS toolbox :confused:
[Captivate Android Development] LimaI896:
I'm using the jk4 so its limited to 850mhz:)
[Captivate Android Development] ryude:
You can disable 1900, that's UMTS I think.
[Captivate Android Development] nybmx:
It's in the SGS tools app not SGS toolbox. It's the last code under the secret codes menu.

*#301279#
[Captivate Android Development] existz:
UMTS is 850/1900 , its the type of technology used, with 850/1900 the uplink and downlink are within the same band...it works on different mhz, some areas use 850, others use 1900, or both
[Captivate Android Development] ryude:
So which how do I make it only use 850?
[Captivate Android Development] lrs421:
In SGS tools, band selection. If you go to WCDMA bands you can select 850 only.
[Captivate Android Development] lrs421:
Yup. I leave it on auto because I travel a lot between Brooklyn, Queens and Long Island. 850 is great in LI but 1900 is better for me in Brooklyn and Queens.
[Captivate Android Development] LimaI896:
Can't find this app in the market :confused:
[Captivate Android Development] lrs421:
Look in the captivate themes and Apps forum for the latest version. Its usually on the first page.
[Captivate Android Development] mcord11758:
Not on market, can download app in op from phoenix.

Or just dial *#301279#
[Captivate Android Development] LimaI896:
Thank you!
[Captivate Android Development] existz:
You can dial the code above to disable HSPA (3.5G) and use UMTS only (3G)..I don't really see much gain from disabling 1900 and using 850 only, unless your in an area where it switches alot (not 3g-h, but switches 850-1900 bands), in my area 850 is only used, so 1900 isnt even used ...
[Captivate Android Development] sicmadek:
Jk4 uses 1900 and 850 as far as i know
[Captivate Android Development] Auridran:
Hey existz, I've been wanting to try different filesystems, and was wondering: is it possible to convert system to anything other than ext4/RFS?

Thanks.
[Captivate Android Development] existz:
It does, it just uses 850 by default
[Captivate Android Development] existz:
As of now, no. The reason is ext2 is more 'unsafe' than ext4, if your system gets corrupted, you have to wipe clean. As for jfs, its known if you run your battery down low it can cause corruption if it shuts off. So I've left it only ext4 to keep people from corruption. But you can convert data,dbdata,cache to ext2,3 and jfs if you wanted, leaving system ext4, same cautions apply
[Captivate Android Development] LimaI896:
Ok so I selected the H/H option but I still see my phone switch from 3g to H.
[Captivate Android Development] existz:
You need to select the first option,release r99, HSPA Off, it might take a couple minutes for it to change
[Captivate Android Development] zerkai:
Hey existz, I accidently deleted a directory or file in the /etc/init.d folder. Now I onlny have "S70zipalign" and "S99android_id_gen.sh" -- I was trying to delete the VC file, do you have any idea what file it was that I deleted or if I need it?
[Captivate Android Development] LimaI896:
This is how to enable only hspa?
[Captivate Android Development] Auridran:
Alright, thanks.

I hereby request this feature then! :p

I don't care about data reliability, especially on /system. If system gets corrupted I just reflash my ROM. No big deal.
[Captivate Android Development] existz:
No, if you choose #1, release r99 hspa off, it disables HSPA (3.5G) using only UMTS (3G), HSPA is used by default, so no need to change it if you want to use HSPA. Using just UMTS, it saves battery. There is no way to use just HSPA (UMTS off).
[Captivate Android Development] ryude:
Using #40 with 100/200/400/600/800 I'm getting really good battery life, hopefully it doesn't CD on me.
[Captivate Android Development] LimaI896:
Ohhh ok sorry I misunderstood. Though you said before you were only on Hspa/hspa and it improved battery.
[Captivate Android Development] existz:
Lol, ah it happens, im only on UMTS (hspa off) and its by far the most noticeable thing I've done to save battery. Which for me it was from where hspa and umts was switching every 30s accroding to dmesg log. It would switch every 30s for as long as I had the phone on, killing my battery. But either way umts-only saves battery over hspa
[Captivate Android Development] LimaI896:
Hmmm perhaps I'll try that n see if I can accept n enjoy the later speed ahaha. I got extra batteries so speed is more important to me. Battery life is more of a bonus n somthing to brag about.
[Captivate Android Development] WickedNite:
But turning off the HSPA will lower down the 3G download/upload speed right? Or it doesn't?
[Captivate Android Development] Hondo209:
any different camera.apk's? i keep getting fc on the video.
[Captivate Android Development] elghouchd:
Anybody know why I keep getting 55.3 FPS in Neocore when i usually get 55.7? Overclocked at 1.3 ghz
[Captivate Android Development] joeshmoe08:
Doesn't really matter, neocore won't change that much if any so its a useless benchmark unless comparing two different phones. Just try playing a game and see if it is any slower. Don't get swayed be benchmarks.
[Captivate Android Development] LimaI896:
I dont get a fc on video. Maybe download seredipity 5.3 and take the camera apk from there.
[Captivate Android Development] Hondo209:
Do i have to remove the old one first? if so, how?
[Captivate Android Development] existz:
0.4fps isn't much, an app in the background could be using a tiny bit more mem than before. If your comparing it against another kernel, this kernel will probably be slower in benchmarks, I use slower settings, the main reason is to save battery, if your comparing it to another suckerpunch build, I've lowered 1360 to 1300. It just depends, but either way 0.4fps is literally nothing to pay attention to...
[Captivate Android Development] LimaI896:
Nope if you use super manager or root explorer it should just copy right over it. Just make sure your system is set to r/w.
[Captivate Android Development] ryude:
My captivate takes 0.0002 more seconds to boot, this kernel sucks!!!

/sarcasm
[Captivate Android Development] Hondo209:
sorry for the n00bness, r/w read-write in cwm?
[Captivate Android Development] LimaI896:
Your kernel is doing amazing! Benchmarks are useless, my phone runs better then any one elses galaxyS that I know in person.
[Captivate Android Development] elghouchd:
Haha ok thanks, and do you think that because i am stable 1.3 ghz, 1.4 ghz should be stable too?
[Captivate Android Development] lrs421:
System read;write
[Captivate Android Development] LimaI896:
Get sgs toolbox set mount as r/w (stand for read/write) then copy the camera.apk to the system/app folder in super manager app.
[Captivate Android Development] GGXtreme:
Do you plan to add the new color-bias option in recovery that Hardcore added in K13A? The lack of a warm-color version was literally the only thing preventing me from trying this.
[Captivate Android Development] existz:
To be honest I haven't seen it yet, ill take a look at it, more than likley yes

EDIT

just checked it out, and as soon as he releases sources ill get a build up with it
[Captivate Android Development] lrs421:
I'm the only jerk playing with his phone at the super bowl party. Loving this new kernel!

More later :)
[Captivate Android Development] existz:
Hahah, you and me both, im excited more about hardcore putting selectable color profiles in cwm than I am the super bowl lol...wishing he would release sources soon