yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] elghouchd:
Can somebody tell me, how do I know if i successfully overclocked my phone? I set -75 for all Hz and pressed apply now, but how do I know if its being overclocked successfully?

Thanks
[Captivate Android Development] davwman:
Thanks for the info. Keep it up!
[Captivate Android Development] nachin:
Thank you so much for the sources existz!!!! :). Now I will try to addapt this in my i9000b if I can :(
[Captivate Android Development] slaman:
JI have been getting charge and sleep deaths running -100 across the board at 1280... Lowered it to -75 and was getting a few sleep deaths...finally lowered it to -50 and haven't seen any sleep deaths in over two days
[Captivate Android Development] existz:
To compile it for the i9000, all you have to do is disable the captivate reoriented patch, im not sure if theres anything different you have to do for i9000b, but you can do a "make menuconfig" then goto system type and uncheck "select captivate" , also when unselecting for captivate, it will disable hpcall, when I added in the hpcall code it was depended on if captivate, so that should be the only thing different, to have hpcall support you will have to redo the hpcall code
[Captivate Android Development] nachin:
Ok, jeje, will see :) Thanks again

Sorry existz, I am on system type but I can see anything in relation with captivate. Can you give me a hand? :)
[Captivate Android Development] existz:
did you do make aries_eur_defconfig first? check your pm
[Captivate Android Development] elghouchd:
He existZ,

Can you teach me how to overlock this kernel using the Voltage app? I have all the Hz (up to 1200) on -75, and i pressed apply now. So im not sure if its being overclock successfully to 1200 hz. How do i know if its working?

Thanks!
[Captivate Android Development] lrs421:
Click states at the bottom of the app and. make sure 1200 is checked as well. No need to check anything else over 1000. As long as you have 1200 in the drop down menu selected and checked off in states you're good to go. Press apply now and if its stable press to apply as boot settings so you won't have to reset when restarting your phone.
[Captivate Android Development] elghouchd:
So is there any app or a feature of the Voltage Controll app telling what Hz the cpu running at at what time? Caus i wanna see if it actually hits 1200.

Thanks
[Captivate Android Development] lrs421:
Sure get a system info app from the market. I use quick system info and like it.
[Captivate Android Development] existz:
There's a few apps that show the current frequency, as mentioned above most system info apps show this, I use system monitor, there's a lot more others, if your just wondering if it actually works, yes it does
[Captivate Android Development] elghouchd:
Is there a widget that displays (live) what Hz my phone is hitting? Oh yeah and that System monitor app is AWESOME! Thanks a lot guys for the help!
[Captivate Android Development] existz:
I ment SystemPanel, had system monitor on my mind, just search the market for systempanel, there's a free version I believe

But also as mentioned, in voltage control just set what states you want, (ie. If your wanting 1200, make sure the 1200 is selected, you don't have to choose 1120 for example) this enables the frequency, then set as max clock
[Captivate Android Development] elghouchd:
Is there a widget that displays (live) what Hz my phone is hitting? I just feel like it would be easier for me to see it straight on my homescreen then to go into the app. Oh yeah and that System panel app is AWESOME! Thanks a lot guys for the help!

And if you dont know an app that has a widget like that, its fine. I like system panel.
[Captivate Android Development] elghouchd:
And your saying that i should only select 1200 in the states if i want 1200? I dont have to select anything under that (dont have to select 1120, 1000, 800, etc.)?
[Captivate Android Development] existz:
I mean don't select anything else above 1000, so if you want 1200, select 1200, (keep 100,200,400,800,1000,1200 selected) or it wont run at those speeds, also remember that anything above 1000 is not guaranteed, some phones don't handle anything above stock very good, but some have no problem at 1400 (very lucky few).. so if you start having problems lower your clock, and also having to much UV can cause problems as well (sleep/charge death, apps freezing/closing, phone restarting...etc etc).. other than that I cant offer support for oc/uv, since its different for every phone, and an unstable oc/uv can cause so many different problems, I can't troubleshoot it since its not a kernel issue, just giving you the option to do it...
[Captivate Android Development] WickedNite:
You have to select 1000 and lower then select the max clock you want, for example 1280.

It should be like this:

☐ 1400 Mhz ☐ 1360 Mhz

☑ 1280 Mhz ☐ 1200 Mhz

☐ 1120 Mhz ☑ 1000 Mhz

☑ 800 Mhz ☑ 400 Mhz

☑ 200 Mhz ☑ 100 Mhz
[Captivate Android Development] elghouchd:
On my phone it has a question mark for Mv for 1280 mhz? Why is that?
[Captivate Android Development] nachin:
Ok existz

I have already tried to compile a kernel for my i9000b but I have serious problems with the arm-eabi, I am very new doing this.

I feel frustrated....:(

Thanks for your help, I will need to keep using my sgs without OC.
[Captivate Android Development] WickedNite:
You should click first the states below the Voltage Control app then it would give you the screen where you can select clocks. Tbh, I don't also know why it gives a ? on 1400 Mhz, 1360 Mhz, and 1280 Mhz on my phone.
[Captivate Android Development] elghouchd:
Thanks, and do you know why every time i unlock my phone, scrolling through screens is laggy? After like 2 minutes, it becomes normal. It happens every time i unlock my phone.
[Captivate Android Development] existz:
Could be from many things. Do you use lagfix? If not try converting to ext4 (i always recommend ext4 file system over RFS, IMO ext4 is way better) Try enabling tweaks from recovery (dont enable VM tweak, known to cause charge death, be fixed in next release) Do you have alot of apps installed? (if you have alot of apps, having system partition converted ext4 can help,) If theres alot of apps running in the background, or just 1 app hogging memory can cause lag...theres alot of things that could cause it. Also you might benefit from using the 500hz version (it can be smoother) if your running the 100hz version , (which i use 100hz version with no problems)
[Captivate Android Development] elghouchd:
If i want the 500 hz version, can i just flash it right over the 100 hz rom? Or do i have to go back to stock? Will i loose everything if i flash the 500hz over the 100hz?
[Captivate Android Development] lrs421:
You can flash it over.
[Captivate Android Development] elghouchd:
Will i loose anything?
[Captivate Android Development] existz:
No

10char
[Captivate Android Development] elghouchd:
How do i know if i have the lagfix enabled?
[Captivate Android Development] xThe Enforcer:
1.4... Holy crap. I'll have to give it a try sometime.
[Captivate Android Development] WickedNite:
Go to recovery menu then Advanced ClockworkMod. You should see there Lagfix options.

Sent from my Muscles using Brain Cells
[Captivate Android Development] existz:
More than likely if you dont know if you applied one, then its still on RFS. To enable lagfix goto recovery, Speedmod Features/ Lagfix ...and enable lagfix, it will convert data,dbata,cache to ext4, you can also convert system partition to ext4 if you prefer, if you have alot of apps i recommend it
[Captivate Android Development] elghouchd:
When i first flashed this it asked me if you want to install lagfix and i remeber pressing yes but im not completely positive. If i go to the recovery and enable lagfix, will it be bad if i installed it twice? Beacuse like i said i might have enabled it when i first flashed this kernel. Thanks!
[Captivate Android Development] existz:
When you go into recovery and select speedmod features/lagfix at the bottom it will show you what partitions are what, so if it shows ext4 you good to go, if they say rfs just select enable lagfix, it will reboot and then select backup and restore, it will convert it (DO NOT pull the battery while its doing this) then it will reboot... you can go back in recovery and look to see if it converted or use a terminal emulator and type "mount" And it will show all your partitions
[Captivate Android Development] elghouchd:
Ok i had the lagfix enabled, and do you know why in the voltage control app the 1280 hz + have question marks as the mV? I really want to try the higher Hz.
[Captivate Android Development] existz:
Its a cosmetic thing, it doesnt effect anything. its something in the source, pretty much I dont have it in the code set to specify it, so VC doesn't know what it is so it shows a ?.. You can still use the higher frequencies, its just not showing what the voltages are (which for 1200 up to 1400 the voltage is 1300mV) so if you drop it down 25mV it will be 1275mv.) again, its just something cosmetic for Voltage Control app (it just shows you what the original mV is and what it is after you lower it). Just set what frequency (states) you want in VC, and then set the max clock. Then you can UV whatever frequencies you want, make sure to test each time you up the frequency or change the UV, theres a mini OCing guide in the OP. As always, just remember you might not be able to use anything over 1000mhz, some have a hard time getting to 1200/1280, let alone anything higher.

Also remember I dont support anything to do with OC/UV, as each phone is different, an unstable OC/UV can cause alot of problems and where its different for each phone, and can cause alot of different problems, and since its not an actual kernel issue (its just your phone cant handle it) I cant troubleshoot it. (99.9% of the time the answer would be lower your oc/uv) But some members might be nice enough to get you going in the right direction to be able to find your max clock/max UV. But the best way to test is to use your phone, stress test are good, but if it works when u use it and doesn't cause any issues, your usually good to go
[Captivate Android Development] elghouchd:
Is 41 degrees Celsius for the temperature of the phone very hot? Whats a good temperature to be at? (Im at 1280 Hz)
[Captivate Android Development] :
...i generally consider anything under 50*C to be still safe

but thats me
[Captivate Android Development] existz:
Deleted..Updated to Test Build #39
[Captivate Android Development] Kizzmiazz:
I will definitely give it a shot to test the charging death, only reason I couldn't use it ;) I'll post results tomorrow. Thank you existz

Sent from my SuperDuper!Captivate | SuperNova v1.0 | Firebird 2 v0.7 | Member of Team Phoenix
[Captivate Android Development] existz:
It should help with the charge death, almost all users who tried it, confirmed it...im not sure if it will prevent charge death 100%, but its stopped it for alot of users
[Captivate Android Development] LimaI896:
Perfect timing! Something to flash right before bed. Your awesome existz :)
[Captivate Android Development] jjtitus098:
Have already flashed it. Will let you know how it goes. I did not have charge death though with the settings I had so just hoping to get even better battery life.

Sent from my Captivate running Precision v.2.0 with SuckerPunch @ 1200mHz.
[Captivate Android Development] existz:
I got a feeling I should go ahead and make this clear, when i say "DOES NOT cause charge death anymore" that mean the Kernel VM Tweak does not cause it anymore, there may be another factor causing the charge death for some users, but fixing this has resolved charge death for ALOT of other users, so its possible it could fix it for you....Thats why im slapping a TEST label on it
[Captivate Android Development] SeanHacker:
nice work man. this kernels smooth
[Captivate Android Development] Kizzmiazz:
I hope , but worries from me bro you make an awesome kernel and if it doesn't fix it on my phone that's just Captivate life lol

Sent from my SuperDuper!Captivate | SuperNova v1.0 | Firebird 2 v0.7 | Member of Team Phoenix
[Captivate Android Development] tietherope:
Awesome! Going to flash this right away. I would much rather have 600/900 over 1360/1400.
[Captivate Android Development] existz:
lol, i hear ya :) ...im hoping this fixes it for most users... we are heading in the right direction, atleast 1 cause of it is knocked down, hopefully we get it fixed all together pretty soon
[Captivate Android Development] Nick281051:
thanks alot, ive never gotten outstanding battery life with any rom and this might just do the trick along with some calibrating
[Captivate Android Development] daandman:
Forgive me for my super noobishness, but am I missing something here? I'm used to flashing 120mb ROM's, this one's only 6mb.
[Captivate Android Development] existz:
This is not a rom, its a kernel
[Captivate Android Development] daandman:
D'oh! Well don't I feel dumb, lol. Thanks.
[Captivate Android Development] existz:
Lol, ah it happends, I've done the same so don't feel bad
[Captivate Android Development] lrs421:
Hmm. Thanks.

No wifi here.

existz, are the drivers different?

Have you considered a 1200 version when you remove the FM info?
[Captivate Android Development] existz:
No, everything is the same, try what I mentioned up above, worked for me, if you have IPv6 privacy enabled, disable it, but if its already disabled, try enabling it, reboot, then back to recovery and disable it, forcing it to unload, worked for me....either way, Hardcore is working on wifi connectivity issues in his K12R test build, so it will be updated in next release.. as for 1200, im not sure yet, I didn't plan on a 1280 but due to alot of request I made it, 1120 is actually my top build, it gets updated first ...but later on I might put out a 1200
[Captivate Android Development] lrs421:
I'll give this a shot. Thanks!
[Captivate Android Development] yokozuna82:


So what do I set it to?
[Captivate Android Development] existz:
It depends on your phone, all phones are different, try setting it 25 at a time, testing each one make sure its 100% stable, keep doing that until it gets unstable then back it down to the last setting that worked, do that for each frequency
[Captivate Android Development] ryude:
Ok, here it is. If existz doesn't want me to post it in his thread I will remove it though.

Also, I have to do the disclaimer thing: Flashing this is your own risk, blah blah, I am not responsible.

Doc's 9.1.2 XWJS3 "Stripped Clean"

Removed

- aldiko

- samsung keyboard

- swype

- bluetooth.apk (only needed for printing via bluetooth)

- bluetoothtestmode.apk

- buddiesnow.apk

- choco font

- cool font

- days.apk

- divx.apk

- dlna.apk (allshare)

- dualclock.apk

- fmradio.apk

- gmail.apk

- googlefeedback.apk

- googlequicksearchbox.apk

- htmlviewer.apk

- infoalarm.apk (daily briefing)

- flash player (download from market place if you want it)

- Layar

- lbstestmode.apk (only used for configuring GPS)

- livewallpapers (just drains battery)

- magicsmokewallpapers

- maps.apk (download from marketplace)

- mediauploader.apk

- memo.apk

- minidiary.apk

- mobiletrackerengine.apk

- mobiletrackerui.apk

- mtpapplication.apk (for kies)

- musicplayer.apk

- phonesetupwizard.apk (the setup that runs on first boot)

- picotts.apk (text-to-speech)

- pressreader.apk

- protips.apk (homescreen tips widget)

- rose font

- samsungapps.apk

- all samsung widgets

- screencaptureservice.apk

- selftestmode.apk

- snsaccount.apk(facebook/twitter)

- snsprovider.apk

- soundplayer.apk

- stk.apk (sim toolkit)

- street.apk (streetview for google maps)

- syncmldm.apk (OTA update)

- syncmlds.apk

- talk.apk (google talk)

- thinkdroid.apk (thinkfree office)

- everything TouchWiz

- voicedialer.apk

- voicerecorder.apk

- voicesearch.apk

- vpnservices.apk

- wipereceiver.apk

- wlantest.apk

- writeandgo.apk

- wssyncmlnps.apk (OTA)

- youtube.apk

- shutdown/startup sounds

- shutdown animation

- removed all but a few notification tones and 1 ringtone (Terminated)

Added

- Zeam launcher

- 2.2 Browser

- Black-theme modded AOSP MMS/Music/Calculator/Clock

- Black-theme modded marketplace

- black-theme Email

- 4 lockscreens

- accurate battery mod

- extended power menu

- default black wallpaper

- black-themed WP7 style gingerbread keyboard

- Xan's Voltage Control app 3.0a3

- JK4 Modem

- Suckerpunch 1120Mhz Kernel

Download: Removed

Fixing bugs and then will make my own thread.
[Captivate Android Development] LimaI896:
Im on the 1.28 kernel and my settings are -125/-125/-100/-100/-50/-50 havn't tried to go lower yet. I been stable for 2 hours.
[Captivate Android Development] sjavvaji:
Xan has a 3.0 final now

http://xdaforums.com/showthread.php?t=829731
[Captivate Android Development] c0ldburn3r:
Awesome kernel work! All the benefits of speedmod with a little OC/UV sprinkled on top.
[Captivate Android Development] rootnik:
I think you've done enough work to the base to post your own thread. Just my opinion.

I'm going to try it out, thanks for posting.
[Captivate Android Development] ryude:
I'm not a dev, just a tinkerer :) It would be an insult if I made my own ROM thread, all the real devs out there deserve the real spotlight, I just like having a really clean ROM :)

If there is any problems though let me know, I will do my best to help you out.
[Captivate Android Development] yokozuna82:
How do I turn off or on Ipv6
[Captivate Android Development] existz:
In recovery, select Speedmod Features / Tweaks / then IPv6 Privacy
[Captivate Android Development] LimaI896:
Whats ipv6, what does it do?
[Captivate Android Development] LimaI896:
Existz what is the voltage at for 600/900?
[Captivate Android Development] existz:
I promise ill get all the voltages added in so that it shows up once i figure out which frequencies im going to stick with

600 = 1175mV

900 = 1275mV
[Captivate Android Development] Dlev7:
Im on Build 36 OCed to 1.2 Ghz with the settings of -25,-100,-100,-100,-125,-150.

With VM tweak DISABLED and im getting no COD.

If i wanted to try the test version what features should I be expecting? I really want better battery life over speed but I love the OC speed at times. Are those UV settings to dramatic? They are stable for me but still
[Captivate Android Development] existz:
If your OCed at 1.2ghz you will get everything you already have plus extra 600/900 frequencies, these should add better battery life, as well as the new settings for the governor (notice I said "should") this is pretty much why i put the TEST label on it, I wanted to try these settings out, if they end up showing worst results, ill revert back to the old settings. In a limited beta test, about 4-5 users, it did show better results, so I wanted to open it up and see if it really does.

As for your UV settings, they are not drastic, as i use 75-100-100-125-125-150 (1200-100)
[Captivate Android Development] Dlev7:
Ill try it out for you and tell you how it goes. and what scheduler do you prefer?
[Captivate Android Development] existz:
I prefer CFQ, the IO tweak in recovery was actually intended for CFQ by Hardcore. It should give as good if not better results than the other schedulers.

From all my testing, I really believe the 600/900 steps give better battery....as for the governor settings, these are something new, in theory they should provide better results, but i want to test them before throwing them into a final build.
[Captivate Android Development] Dlev7:
Ya I have mine on CFQ as well, flashing now its late at night so I wont be able to test like in real world but I will tomorrow. And when flashing from SuckerPunch kernel to suckerpunch do I need to delete my old voltage settings or no?
[Captivate Android Development] existz:
Usually you dont have to, but since I changed the frequencies, Im going to say yea delete them, cause the states were changed and the order of them was changed, just to prevent any issues..glad you mentioned this, need to add it to the download post
[Captivate Android Development] bamonkey:
well on accident i can report i didnt clear my frequencies and the update to #38 seemed to take just fine all new voltages were read to go :D *your milage my vary, all rules and restrictions apply, captivates may catch fire and blah blah blah blah;)*
[Captivate Android Development] existz:
good good..it should be fine, but theres always a chance something could go wrong, technically the worst thing that "should" happen is some frequencies might get disabled by default, which you can just re-enable in VC, but theres always that chance it could turn your phone into a one legged monkey, so better safe than sorry :P
[Captivate Android Development] Dlev7:
I deleted them flashed the kernel and it keeps freezing.

What UV settings would recommend for 1.2 OC? With the new 600 and 900 steps?

EDIT: Working perfectly it just froze up first time now Stability test is working perfectly but still would like to know som recommended stuff for the OC and UV for this build 38
[Captivate Android Development] mkr14:
Could you remove 1360 / 1280 and leave 1200 / 1400? Might as well provide the option to go high rather than fill the void with, in my opinion, pointless increments. The only real reason to overclock is for emulators (PSX) and games. Providing the maximum clock possible is more beneficial than providing small increments.

Could you do something like 1400, 1200, 1120, 1000, 900, 800, 600, 400, 200, 100?

Maybe remove 1120?
[Captivate Android Development] Dlev7:
Im using -25,-25,-25,-50,-75,-75,-100,-125.

(1200,1000,900,800,600,400,200,100) Steps. Anything I should do differently?Its not freezing anymore its just anything else that you would recommend steps wise and UVing wise to get good stable battery life
[Captivate Android Development] mkr14:
Use less steps. I would take out 2 of the steps, probably 900 / 600 or 1000 / 800. If you are concerned about battery life, dont use 1200 and maybe go the underclock route.
[Captivate Android Development] existz:
Shouldnt be a problem, the only issues im having right now, and the reason 1360/1400 are not in the TEST build, is because im having issues with anything other than 10 states. So yea, as long as I keep 10 states i can do any combo. I just wanted to see if everyone else thought 600/900 actually made a difference, But what I might do is something like this

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

As im not sure if the 900 step is really doing that much, i think the 600 step is whats giving the better battery life. And more than likely if you can do 1280, 1300 shouldnt be much harder to achieve, so ill work on this, try to get them evened out, I would love to keep all frequencies but as of right now i dont think I can. So we compromise :)
[Captivate Android Development] existz:
Im using the same steps, been using them for a few days now with no issues. But if you want you could disable the 900 step.. As for your UV, I really cant say, the best thing to do is find a program that monitors how much time is spent at each frequency, you can use SetCPU, but just use it to observate, dont set any profiles with it. Then once you see which frequencies are being used the most, try UVing them some more, but making sure its stable of course
[Captivate Android Development] Dlev7:
Ya using SetCPU to see. The 900 step gets used the least but the most used steps are 1200,800,600,200,100
[Captivate Android Development] existz:
im working on a new test version with

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

Ill see how it goes over next few min, and if its good ill post it as a new test version

EDIT

So far so good, getting ready to upload, Test Build #39 coming shortly
[Captivate Android Development] Dlev7:
Ya I took of the 900 step as it hardly gets used according to Set CPU but the 600 step gets used a lot so here is what I got running really stable right now without CD 1.2 Ghz CFQ:

-25,-50,-75,-75,-100,-100,-125.

800 and 600 steps get used the most out of any of them, I may just try to do -100 on both of them as well, what do you think?