yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] joeybear23:
I know many of us have been trying to put together a working set of voltage settings for OC'ed kernels that works.

I also know that all hardware is not created equally, so this thread is meant to help with those users trying this for the first time as well as give people playing around with the settings a place to keep their data.

Please post a response in this format:

Kernel:

Scheduler: (scheduler is the top left option in Voltage Control)

Batch: (the batch number is listed behind the battery)

OC/UV Settings:

1600 - 175

1500 - 175

etc

Please post any commentary on your settings in the bottom of your post.

If you get a shutdown or freeze because of your settings, please edit your post to put the new settings.

***Also, please do not fill up this thread with questions. I would like this to be a repository of OC/UV settings only.***

Mods, if this is not the appropriate forum for this information, I apologize.
[Captivate Android Development] joeybear23:
Kernel: CogKernel 4

Scheduler: CFQ

Batch:1007

1200 - 50*

1120 - 50*

1000 - 0

900 - 100

800 - 100

600 - 100

400 - 100

200 - 100

100 - 100

*- previous setting of 175 crashed after several hours. now trying 50
[Captivate Android Development] gcamp0730:
You may also want to know what kernel and scheduler are being used. I've had issues (sleep of death) with bfq, but noop seems to be great.

kernel - SetiroN 1.4.7 1200

scheduler - noop

batch - 1007

1200 - 125

1000 - 125

800 - 125

400 - 125

200 - 125

100 - 125
[Captivate Android Development] vvaffles:
ooh great idea, maybe also include the kernel you are using atm, and if possible the phone batch number?

SetiroN's 1.4.6

batch 10.11

Scheduler: noop

OC/UV settings

1200 - 125

1000 - 100

800 - 125

400 - 150

200 - 150

100 - 200

there is rare freezes on android.core with this setup, but its not a big problem, and battery life is really good so this is my usual setup
[Captivate Android Development] designgears:
Kernel: CogKernel 4

Scheduler: CFQ

Batch: 1007

Voltage Settings:

1600

1500

1400 (-175)*

1300 (-175)

1200 (-150)

1120 (-150)

1000 (0)

900 (0)

800 (0)

600 (0)

400 (0)

200 (0)

100 (0)

* - current running and stable
[Captivate Android Development] s2h2golf:
SetiroN kernel 1.4.3

Scheduler: noop

Batch: 1007

OC/UV settings

1280 - 50

1000 - 50

800 - 75

400 - 100

200 - 100

100 - 125

Stable, no freezes, no charger death. Afraid to mess with it. I lose about 2% (total, not per hour) battery overnight (6-7 hours).
[Captivate Android Development] PAulyhoffman:
Kernel: CogKernel 4

Scheduler: CFQ

Batch: 1006 (is it old enough to be a classic?)

Voltage Settings:

*edit set 1300 to 150 (175 freezes, 125 freezes) and it seems to be working

1200 -100

1120 -100

1000 -100

900 -100

800 -100

600 -100

400 -100

200 -100

100 -100

1300 is running stable with above settings

1200 works with settings in black very stable
[Captivate Android Development] godzulu:
what cpu??
[Captivate Android Development] geokhentix:
Kernel: SetiroN 1.5.4 XT 1600MHz

Scheduler: BFQ

Batch: 1007

OC/UV Settings:

1600 - 75*

1552 - 75*

1504 - 0

1464 - 75*

1456 - 0

1400 - 0

1344 - 0

1288 - 50*

1200 - 50*

1000 - 0

800 - 0

400 - 0

200 - 0

100 - 0

*STABLE
[Captivate Android Development] godzulu:
set at 1300 cpu

settings in signature. So far, so good
[Captivate Android Development] waghoba:
Hey great thread...one Q where to look for batch number??
[Captivate Android Development] silverslotcar:
Underneath your battery is the batch number.

Kernel: Setiron 1.4.3

Scheduler: NOOP

Batch: 1008

OC/UV Settings: 1280 - 25

1000 - 25

800 - 50

400 - 75

200 - 75

100 - 75

Updated voltage control app to get settings to stick on boot. Other than that no problems whatsoever and running stable and flawlessly.
[Captivate Android Development] ninjuh:
What does the scheduler and batch number signify?

Edit: only asking because I know others will be asking the same thing
[Captivate Android Development] capita:
Kernel: Setiron 1.4.4

Scheduler: BFQ

OC/UV Settings:

1300 - 25

1000 - 50

800 - 75

400 - 100

200 - 100

100 - 100

Voltages stick on boot. Didn't have to make any changes to the generated script. All I did was mount system as R/w first and then save the voltages settings from the voltage app.

Very stable, no FCs since I flashed...about 4 days ago.
[Captivate Android Development] geokhentix:
Batch number signifies what batch your phone was created in. Much like Sony and Microsoft use numbers with their consoles to indicate what hardware may reside in the chassis or what time period they were manufactured under, mobile phones, or much any electronic device that is released in cycles, follows the same principle.

As for the scheduler, a scheduler in terms of processing is in lamens terms...Processes waiting to be executed in your memory are allocated to the CPU by the scheduler. It selects the next operation to get executed from the RAM, basically. Operating Systems are processes in themselves, so there has to be a medium to make sure the operating system and application processes play nicely together. That's not all there is to it, the scheduler means a lot for I/O[input/output] operations as well, but we're keeping it lamen.

In a nutshell, it's the middle aged Nanny that lives inside your processor. It makes sure everything is clean, runs time efficiently [nannies are usually paid by the hour], and it makes sure none of the kids rough-house or make a mess. Done.

By the way, OP says no questions. I answered it because I'm obviously one of the coolest, nicest guys around, but let's keep it to a minimum and stay on track!
[Captivate Android Development] techmik67:
Kernel: CogKernel4

Scheduler: CFQ

Batch: 1006

I set max at 1300 now, since 1400 froze, but ONLY on 3d intensive stuff.

1600, -0

1500, -0

1400, -175 when in use

1300, -150

1200, -100

1120, -75

1000, -50
[Captivate Android Development] glitterballs:
Ok....when I see things like this, I'm just...baffled.

A.) Why you only undervolt the very high frequencies that your phone rarely uses? You phone spends most of the time at lower frequencies. Open setCPU go to info, and check time in state. You'll have almost always a 10:1 ratio of time at 100MHz to 1000MHz. You save a lot more battery by undervolting the lower frequencies where your CPU spends more time.

B.) I'm really skeptical of undervolting by 150 and 175MHz at those frequencies. On *stock* voltages, I haven't seen anyone get past 100mV at 1000MHz, but you're -150 at 1120, and -1-freaking-75 at 1200MHz?! If the kernel you're using OVERVOLTS the frequencies (which laststufo had been doing as well) that's about the only way I could imagine you could appear to be undervolting by 175mV @ 1200MHz. Ie, xan's app (last I knew) calculated the UV by the stock voltage, so if the voltage was raised in the kernel, it would look like you're undervolting by 175 when it might only be 100 or 75. Something the whoever you got your kernel from should let people know so they can make informed decisions about whether or not they want to overvolt their CPU.
[Captivate Android Development] drancid:
Kernel: CogKernel 4

Scheduler: CFQ

Batch:1007

1200 - 50

1120 - 50

1000 - 50

900 - 50

800 - 75

600 - 50

400 - 75

200 - 125

100 - 125
[Captivate Android Development] Milkshakes00:
Kernel: CogKernel 4

Scheduler: Noop

Batch: 1008

1200 - 0

1120 - 0

1000 - 0

900 - 0

800 - 0

600 - 0

400 - 0

200 - 0

100 - 0

Seems stable. Anything over 1200 on the drop down list instantly freezes, though. :/ I can't see any of these devices running 1.6 anywhere near stable, tbh.
[Captivate Android Development] BL4zD:
Kernel: glitterballs' CM reoriented

Scheduler: Noop

Batch: 1010

1200 - 100

1000 - 100

800 - 100

400 - 125

200 - 125

100 - 125
[HD2 Android Q&A, Help & Troubleshooting and Genera] MACBLACK91:
Hey i got a problem,

If I try to download something it looks like its about to start i even see how big the file is but then it just stops and exit back to the market front anybody got the same problem? :confused:
[HD2 Android Q&A, Help & Troubleshooting and Genera] Puppetmaster_sr:
Yes, exact problem I have. I also realized my sd card all of a sudden became "read only" and can't place anything on it (no pics/vids/etc). Read these forums and it's recommended to remove everything from sd card and format it again.,then place everything back.,.,gonna try it when I get home
[HD2 Android Q&A, Help & Troubleshooting and Genera] deadmansink:
Try unmounting sd card, download , then mount card...search for this and you'll find the answers
[HD2 Android Q&A, Help & Troubleshooting and Genera] MACBLACK91:
Yes i will try it also hope it works....
[HD2 Android Q&A, Help & Troubleshooting and Genera] MACBLACK91:
@deadmansink

didn't work it just stops immediately, its like one sec it shows like 324kb and then this disappears. I will try to make a new google account and see if that works
[HD2 Android Q&A, Help & Troubleshooting and Genera] deadmansink:
You can also search the net for .apk's or go here:

http://www.androidzoom.com/

Are you trying to download via WiFi or data, there may be issues there.
[HD2 Android Q&A, Help & Troubleshooting and Genera] MACBLACK91:
Im on data right now , im about to check if it works with wifi.

Could it maybe be becouse I updated my android market to the new one but it had errors and always closed so I put the firmware back on new now its the old one again?
[HD2 Android Q&A, Help & Troubleshooting and Genera] deadmansink:
I think it may be a connection problem. If it works with WiFi and not DATA, then we know it's a DATA problem...
[HD2 Android Q&A, Help & Troubleshooting and Genera] MACBLACK91:
well ... it still doesnt work ill do another reinstallation with another google email then we'll see if it works but that for the help:)
[HD2 Android Q&A, Help & Troubleshooting and Genera] [Krueger]Dr.Stein:
Mine automatically updated itself while I was out and about just now.

I am on DHD build and have the accounts & sync background data enabled all the time.
[Droid X Themes and Apps] kilgil27:
I'm really not even looking for a messaging app that looks like the iphone app, just one that acts like it. Every messaging app I've tried on android all take you back to the list of all messages after you reopen it again, and I'd really like to find one that keeps the last person you were texting open until you TELL it to go back. A modified version of the stock app would be best, but are there any that can do this?
[Droid X Themes and Apps] Ubermicro13:
If you use Handcent SMS and when you're done texting if you press the home button instead of the back key several times it will open back up to the last person you texted.
[Droid X Themes and Apps] freshk3v1n:
try gosms .
[Droid X Themes and Apps] mrksbrd:
crunch sms
[Captivate Q&A, Help & Troubleshooting] Noob4Life:
okay so I know this isn't exactly the best thread to post but I'm so overwelmed with info about this phone that I have no idea where to start! I figured I'd start by searching the market for Launcherpro but when I did that Launcherpro Plus won't show up. Can anybody PM on a good place to start or post in this thread? Thanks guys, also I'm thinking I may want to flash Cognition so what would I need to do in order to accomplish this? Thanks guys and sorry for the noob thread.
[Captivate Q&A, Help & Troubleshooting] Dungeon47:
Start by making sure you can manually enter download mode with keys.

Turn your phone off.

Plug in USB.

Hold Vol Up and Down and Power all at once until the green battery disappears, then release power, but continue to hold Vol Up and Down. This should get you a yellow yield sign with an Android on it shoveling or something.

After that, just pull battery and power on like normal.

If that doesn't happen, then try again, or find better directions than mine until you are certain it won't work. This keeps you from bricking your phone any of the easy ways.
[Captivate Q&A, Help & Troubleshooting] Noob4Life:
Okay so I can get into downloading mode with just the keys, is this good?
[Captivate Q&A, Help & Troubleshooting] Dungeon47:
Very. It means that even if you totally screw your phone up so that it can't boot into the OS, you can just flash back to stock with ODIN and start over.

Next, if you are interested in trying ROMS out, you may want to check out Assonance: http://xdaforums.com/showpost.php?p=9513065&postcount=1

The directions are thorough and links are provided for just about everything. Use at own risk, and all that stuff; but if you were afraid to take tech risks, you wouldn't be here.
[Captivate Q&A, Help & Troubleshooting] Noob4Life:
Thanks Dungeon, I appreciate the help!

BTW guys does anybody know why I can't install the clockworkmod onto my phone via rom manager? I click on the option and it doesn't do anything... Thanks!
[Captivate Q&A, Help & Troubleshooting] silvertag:
Are you rooted ?
[Captivate Q&A, Help & Troubleshooting] Dungeon47:
ROM Manager is having trouble the last few days.

Go here: http://xdaforums.com/showpost.php?p=9876490&postcount=3

Copy that update.zip (the whole zip, don't extract it) to your sdcard, then get into recovery mode (hold Vol Up, Vol Dn, Power until you see the white ATT World Phone logo) then use Vol keys to move to "reinstall packages", click Power to go. It will do some stuff. Do it one more time, and you should boot into CWR with root so you can flash.
[Captivate Q&A, Help & Troubleshooting] v1rtu0s1ty:
Hi Dungeon47,

I forgot the reason why we need to install clockworkmod.

Thanks,

Neil
[Captivate Q&A, Help & Troubleshooting] avgjoegeek:
It gives you the advanced options while in recovery - helps you to install that custom ROM, or delete your battery stats, dalvik cache and even perform a factory reset/data wipe using that tool.
[Captivate Q&A, Help & Troubleshooting] v1rtu0s1ty:
Awesome! Thanks! :)
[Nexus S General] sombionix:
Most of you already know how to perform this procedure, but for those that don't, its simple.

NOTE: Unlocking your bootloader will perform a factory reset

Unlock Bootloader:

1. Open command prompt

2. Type 'adb reboot bootloader'

3. Type 'fastboot oem unlock'

4. Use volume keys to select 'yes, unlock bootloader'

5. Use power button to select option

6. Done!

Lock Bootloader:

1. Open command prompt

2. Type 'adb reboot bootloader'

3. Type 'fastboot oem lock'

4. Done!
[Nexus S General] SphericalPuma:
Is there an icon, like there was with the padlock on the nexus one, after you unlock it?
[Nexus S General] gtg465x:
On the Nexus S, you can do fastboot oem lock and it's like it never happened.
[Nexus S General] TheBiles:
Where are you getting the Nexus drivers? When I select the USB driver folder in the SDK (fully updated) it just tells me that no drivers were found.
[Nexus S General] SphericalPuma:
Ha, I just saw this. Great.
[Nexus S General] Nexus 1:
[REF] "fastboot oem lock" will lock the device back

at least the bootloader screen shows it can be locked back.

not tried really locked my customized kernel yet.

will update after trying
[Nexus S General] jroid:
I can confirm this. :D
[Nexus S General] Darrien13:
So you can lock the bootloader back after you unlock it? COOL :D
[Nexus S General] slowz3r:
This is good :)
[Nexus S General] Nexus 1:
update to the latest sdk
[Nexus S General] GrandMstrBud:
I do have the latest. I don't see any USB drivers in the package but it does show up as an android ADB device. Now I'm trying it on my laptop and it will not find any USB drivers so it's showing up as unknown device.
[Nexus S General] SphericalPuma:
Google USB Drivers are in the SDK manager under third-party, I had the same problem as you
[Nexus S General] GrandMstrBud:
I found those but those do not seem to work. When the phone is powered on it does show an ADB device but when in fastboot mode the drivers I downloaded do not work. So I need some samsung drivers or something for this?
[Nexus S General] GrandMstrBud:
Same thing here
[Nexus S General] delirial:
I have the same problem too. The drivers installed fine for the device in normal mode. But once I go into fastboot, it is displayed as an "Android 1.0", with the yellow icon in the device manager.

Attempting 'fastboot oem unlock' it just stays there waiting for a device...
[Nexus S General] k0mpresd:
you need to manually install driver using "have disk".
[Nexus S General] vespid:
If you are having issues with the stock usb drivers, then try this:

http://xdaforums.com/showthread.php?p=9861928#post9861928
[Nexus S General] DKYang:
The part about installing PDAnet does fix the Android 1.0 driver problem, for me anyways. Once you get fastboot working, it seems fine to uninstall the program since it is still working for me.

The latest driver is version 4. You can open up the SDK Manager and download it. Look under available packages (I think that's what its called).

Yes. I've never had the Nexus One before, but the padlock icon did appear once I did the fastboot oem unlock.
[Nexus S General] GrandMstrBud:
So once we have clockwork recovery installed and rooted can we lock the bootloader with no problems?
[Nexus S General] nxt:
I'd like to know this too, would it see the clockwork mod as foreign and revert to stock recovery if the bootloader is relocked?
[Nexus S General] swetland:
fastboot oem unlock does the following:

- prompts for confirmation, aborts if NO

- erases data

- sets unlocked flag (to allow flash/erase of boot/recovery/system/etc)

fastboot oem lock

- clears unlocked flag (to disallow flash/erase of boot/recovery/system/etc)
[Nexus S General] nxt:
Yes we understand, the question is:

After we unlock, install clockwork, and root the phone, can we then relock the bootloader and still have root/clockworkmod working and all that jazz? (We don't like the 5 seconds we see the Lock icon :P )
[Nexus S General] swetland:
Yes -- locking the bootloader only disables the ability to use fastboot flash/erase until you unlock it again. It doesn't change anything else.
[Nexus S General] nxt:
Would "flash_image" work? Cuz if we wanted to update the recovery, we'd have to fastboot oem unlock again and that would wipe the phone clean.
[Nexus S General] swetland:
I thought most of the custom ROMs replaced recovery with a version that allowed reflashing? That's how I'd suggest doing it.

oem unlock only controls bootloader behaviour -- you could use your own recovery image which will flash anything or anything signed by your favorite distribution's key or your personal key or whatever.
[Nexus S General] tenbeau:
I have read and followed directions on all the threads I can find this evening concerning using or setting up fastboot. So far none have worked. I downloaded all the necessary files(from two different sources) and drivers and installed them on the root of the C: drive. I can attach my Vibrant and it will show up for adb devices but not for fastboot. The Nexus S just does not show up for either fastboot or adb. I cannot figure out what I am doing wrong. Kind of odd as I had boxed up the Nexus S this morning to take back and get a refund( I bought it off contract) and at the last minute decided to try it a couple more days. So far I must say the Vibrant is my preference. I sure it would help if I could get the Nexus s rooted and bootloader unlocked. This is really frustrating as I am reading and trying everything I can find but nothing works. I am familiar with Odin and have set up adb before but never have dealt with fastboot.Can anyone help me with some information? It would be greatly appreciated.

edit : Can anyone Please help me?
[Nexus S General] barmanham:
Download pdanet and run it had same problem drove me nuts
[Nexus S General] AndrewGoldy:
Excellent! Going to try this once mine arrives!

I'm currently an iPhone fanboy, but am changing!
[Nexus S General] jblade1000:
i had a quick question, if i've never turned the phone on and gone through the setup and all that, and I go into fastboot mode as the first time I turn the phone on does that matter? Since unlocked the bootloader does a factory reset anyways, i was just wondering if the phone had to already be set up to do it.
[Nexus S General] slowz3r:
guys with the driver issues, dont point it at the usb-drivers folder but point it at the SDK folder and check the lil box to check the sub folders..and then your done
[Nexus S General] me1111:
After running the fastboot oem unlock, my phone shows as unlocked but i can not see the phone when i run the ADB devices command, it shows up fine in device manager. I tried powering the phone off and back on, rebooted the computer, uninstalled Android ADI interface and reinstalled it nothing worked. i am running Windows 7 64Bit.

Please Help !

Edit: got it working!!!
[Nexus S General] lmerega:
How did you solve?

Thx
[Nexus S General] cyc1120:
Out of curiosity, are there any benefits to lock the bootloader after I unlock and root the phone?

Thx in advance
[Nexus S General] Kingken:
i also want to know... mayb the unlock icon (dun really like to see the icon there)
[Nexus S General] cmstlist:
Are there any clauses in the Nexus S warranty that specifically address unlocking the bootloader with fastboot, similar to the N1 warranty? Or not?

And if so - do you think there is any sort of invisible internal flag that still tells Samsung/Google that you did unlock the bootloader at some point?
[Nexus S General] iori:
so is locking back the bootloader will also wipe the phone?
[Nexus S General] death1246:
I want to know this too....
[Nexus S General] sektorNBA:
fastboot devices cant find any of my devices.

I am testing with a GT-I9000 ( 2.3.2 ) and GT-I9000B ( stock 2.2 )

I try to point drivers to SDK folder but windows said i am using the newer drivers.

How do i solve that?
[Nexus S General] DJTaurus:
delete post.................
[Nexus S General] sj_martin:
can anyone confirm this?
[Nexus S General] Manuel1948:
No

Please look at post 22 on page 3 ( http://xdaforums.com/showpost.php?p=9881321&postcount=22 )
[Nexus S General] robrob777:
Thanks, worked.
[Nexus S General] InfinitiGuy:
After unlocking (losing data) and then locking back (no data loss), will unlocking it again cause you to lose your data again? If so then it would be better to keep it unlocked?
[Nexus S General] cmstlist:
You may as well keep it unlocked; and if you ever have a need to relock it, do a nandroid backup first, so that you can restore later.
[Nexus S General] AskBack:
where i can get the link for fastboot oem bootloader man??? :)
[Nexus S General] InfinitiGuy:
So this means if I re-lock and then unlock I will lose data again like the first unlock?
[Nexus S General] cmstlist:
Yes, every bootloader unlock will wipe data.
[Nexus S General] devcager:
Hi,

I tried this commands and it told me something like that it is not internal command etc. (I dont have it in English). I cannot lock it and I need to send it to servis soon! :(

Any idea, please?
[Nexus S General] 4I-I:
You know how to use fastboot do you? With the tools folder etc...

sent while eating an ice cream sandwich in the matr1x
[Nexus S General] devcager:
well, I hope :). I managed to get it working. Now I have different problem. I want to lock it, ok.... and reboot it into fastboot and then type in cmd "fastboot oem lock" and it just says "waiting for device" and stucks :( I tried to reinstall drivers but I dont know if have the right one.
[Nexus S General] cmstlist:
Try fastboot devices. Does it show your device in the list? If not then it's a driver issue.
[Nexus S General] devcager:
Now it says that this is not a name of internal or external command, executable program or blah blah.... (something like that in English) :(

EDIT: Now, in tools it does not say anything. So I guess it looks like It starts the command but nothing to display. But I reinstalled drivers yesterday. Are there some newest versions for Nexus S?
[Nexus S General] y2kdread:
Is it possible to lock the bootloader through ADB?

My phone's USB port decided to crap out and now I need to lock to take it back into sprint.
[Nexus S General] hwr44ever:
doesn't work for me

It says that waiting for the device, while i connected the device and drivers are installed