yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] RKight:
I tried my hand at undervolting and the results weren't pretty. I set it to -75 across the board and my phone locked up. I did a battery pull and was asked if I wanted to change my lagfix configuration. I chose to discard the settings, then I got stuck in a soft boot loop. I did a restore, master cleared, and started over. As an experiment to get even better battery life than I already do, I decided to limit my CPU to 400mhz (mainly just for the several hours a night when I use my phone like an iPod). I set the voltage to -50 for 400, -25 for 200, and left 100 alone. Everything was running great but if I shut my screen off while the music player wasn't running, my phone wouldn't wake back up. I'm assuming this is the "sleeping death" I've heard so much about. Oh well.
[Captivate Android Development] johan8:
Try not to set any voltage, mine also have problem if change the voltage.

Now I haven't change the values, no problem at all.

If the phone freeze or hang, you don't need to pull the battery,

simply hold Vol up+Power for a few second, it will reboot itself.
[Captivate Android Development] mikejames07:
I'm having an issue with the voltage control app. Everytime I reboot, the changes are reset.

It did that last night after I rebooted. I then went to sleep and when i woke up a few minutes ago my battery said it was down to 6% from 46%.. I then changed settings in the voltage app and plugged the phone up. I rebooted and the voltage settings had reset again, and NY battery was showing 42% o_O?

Edit: I'm on 1.4.3 1280
[Captivate Android Development] shaolin95:
Did you read the OP amigo?

***TO MAKE UV SETTINGS STICK, NAVIGATE TO /system/etc/init.d/ WITH ROOT EXPLORER AND MOUNT R/W. IF YOU DON'T HAVE IT USE ADB:

You also need to rename the file there from scheduler to s_98_volt.sh or s99_volt.sh depending on your rom.

1GU55732G7457382R sorry for the small donation but Christmas is making me broker than usual! lol

I will send some more soon...if you get 1400 or 1450 to work more stable I will be more happier to send a bit extra on top of my second denotation LOL
[Captivate Android Development] slider2828:
Hey Shaolin... I tried 1400 and 1450 and its just plain unstable. 1350 I can do whatever normal stuff to the phone but I go on a lot of business trips and I play my snes4droid... and that thing really loads up the cappy fast....

So even 1350 its a killer

Does anyone play anything after overclocking? Like emu's because that is really the only thing that loads up the cappy for a long time. 1200 seems to do best....
[Captivate Android Development] shaolin95:
Well some of my findings , in my opinion, indicate that at 1400 the issue is not the CPU but some how the Video card or other component being stressed.

I can get 1400 MHZ to be good for video card or for CPU but not both as they require me to use a different voltage setting.

-100 gives me video card stability but if I push the CPU it runs out of juice.

-50 gives me CPU stability but the video card intensive apps freeze like NeoCore.
[Captivate Android Development] DAGr8:
I have said it many times .. its the kernel .. Oc ing a processor will NOT affect GPU ..nor the other way around ..

We simply need better kernel
[Captivate Android Development] shaolin95:
You have not read that thread on how they are related it seems. From what I have read it may be stressing out other components...you know like older mobos use to OC different bus and ended up crapping the Video card or others.

Did you see the test I did and have a better explanation for my findings? ;)

NeoCore is an automatic black screen at -50... I can see the the screen and start it at -75 but it freezes and it runs perfectly fine at -100

But that is too low voltage for the CPU as my CPU needs -50 for stability so clearly something is related.
[Captivate Android Development] Shammyh:
Yea, except do you actually know what's being overclocked in this kernel? There are a number of different clocks on our phones, and some of them do affect both the GPU and CPU.
[Captivate Android Development] smokestack76:
I agree. Seems there is alot more to the picture so to say.
[Captivate Android Development] DAGr8:
yea in a computer for example if you dont have 'strong' enough ram to support your cpu ' s OC it will not work .

EXACTLY .. one thing I know for sure the cpu can take it .

here is why:

if I do stuff cpu intensive it takes 1.45 but when doing something that doesnt require neither of the gpu nor cpu phone freeze this is completely irrelevant to the cpu clock , this kernel is doing something wrong to the rest of the phone , its not the processor causing that , witch is all im saying.

.

IMHO the kernel is all that matters in this case since its the only thing pushing the wrong buttons ....

Anyways you wanna see it , when a cpu cant take the OC it either overheats and worst case scenario it dies ....

In MY case the cpu takes it JUST FINE , without overheating , regardless of the UV , but phone freeze just buy going in the setttings while doing processor stress test the processor takes it just fine and even if it heats Its not that bad , so again , the cpu can take it , but the phone cant handle it , only possible answer is : its the kernel' s fault

If someone could make just a simple module (like it has been done on other phones ) we could crank the MHz and voltage to do some test on diffrent kernel I am sure we would have a definite answer ...

In the end I agree its all speculations , one thing I am sure is the humingbird can take more then 1450 mhz ...
[Captivate Android Development] geokhentix:
Just a question for you all, or SetiroN if he feels like responding; I know it's been stated that there will be no CWM flashable for 1350MHz+; would it create problems if it were cooked into a ROM via update.zip instead of Odin?(the 1450mhz)?

Just curious if there is some reason that it HAS to be flashed via Odin, instead of CWM. I ask this solely for my own cooked ROM's that I don't release to the world.
[Captivate Android Development] DAGr8:
I have done it , I didnt get any issues , but again I been saying htis kernel has issues for a few pages now so :eek:
[Captivate Android Development] slider2828:
I whole heartedly agree with shaolin, you and a couple of others. You just can't push clocks without a good core which controls and scales frequency and voltage for BOTH the Video and Processor....

Rasdeep's kernel stuck and worked fine at 1200mhz and he is standing saying that its stable at the frequency and he never suggested others to change the frequency because he said there is more to it than voltage and clock speed. I believe him as I have tried other speeds and all have frozen when playing SNESDROID games which emu's really work the core and the video. So ima stick to 1200mhz... even 1280 was not nice enough to work well....
[Captivate Android Development] SetiroN:
What version are you using? Have you tried reapplying BLN from CWM and checking with the app?

It works fine here.

No idea why it happens, sometimes the "go back" option gets removed. Just use the menu button, it works as back.

Sure, as soon as he publishes the new version's sources. I haven't had any luck trying to exract the ram disk from his compiled kernel.

I'm already aware of those, unfortunately they don't play well with Samsung's modified 2.32.9 kernel. I'll see what I can do.

Yeah, but it's gonna take some time, I'm quite busy these days.

Do you have a link to a kernel enabling it?

Wrong. :)

Only the 1450 clocks the GPU higher than stock, I'll reduce it in the next version.

There's no technical issue, I just wanted people trying high-clocked kernels to be in front of a pc, knowledgeable about entering download mode and able to use ODIN in case of failure.
[Captivate Android Development] darcjrt:
Is there a version for the vibrant of this kernel?
[Captivate Android Development] DAGr8:
haha I stand corrected as I only tested 1450 mhz , I guess it means I should test 1400 and wont have any issues then :)
[Captivate Android Development] shaolin95:
HA! I told ya! :D

Well I was sort of right as then it seems 1400 is not OCing the GPU and something else is causing my strange behavior...any thoughts on my test Setiron?
[Captivate Android Development] MikeyMike01:
I know about /system/etc/lagfix.conf, which contains the lagfix settings.

Is there any place that the tweaks could be enabled by default?
[Captivate Android Development] geokhentix:
Unfortunately I believe WiFi calling requires certain hardware that the Captivate may not have, and even if it did, the network needs to support WiFi calling, and AT&T's does not. AT&T uses femtocell (microcells) for those who have signal problems at their home. WiFi calling is meant to solve the exact same problem; so obviously AT&T won't have both. Can't really pull strings to get free air time on a MicroCell.

So, pretty sure this is a fact, WiFi calling will never work on AT&T.

Of course it may work on an unlocked Captivate with a T-Mobile SIM Card as their network DOES support WiFi calling, but ours does not, and most likely won't ever, or for a great while.
[Captivate Android Development] Pirateghost:
unfortunately, the WiFi calling on Tmob phones still eats up your minutes....its not UMA
[Captivate Android Development] bedwa:
You can however use GV, a sip account and a site where you use your SIP account to add a phone number to it. After verification (use a desktop agent), you can plug the SIP info into your fring application and make voip calls over your android device. I played with this for a while with my N1, but let my phoneline go past the 30 day inactivity time with this elsewise I would have been using it today. Expect horrible results unless in a SOLID 3G area though. :)
[Captivate Android Development] DAGr8:
Ok phone has no random freezing at 1400 its perfectly stable going around normal features so ill be waiting does Artie 1440 without gourmet Oct...

sent from the future using xda app
[Captivate Android Development] joeshmoe08:
Hello I have two quick questions about setron 1.4.3.

1) to clarify, when moving from version 1.2.6, all that I have to do extra is reset uv/oc settings meaning set them back to default right? (-0 -0 for uv and set oc to default 1.2 ghz)

2) Between the 1200 & 1280 varient which should I go for for more stability? Does 1280 make I considerably less stable?
[Captivate Android Development] DAGr8:
Wow auto correction is **** lol

Ill be waiting for 1.45 without gpu oc

sent from the future using xda app
[Captivate Android Development] Demented71:
Auto correct may be ****...but you should still be looking at what you have before you submit! lol That was funny...lol
[Captivate Android Development] shaolin95:
1) Set to -0 and remove the bios settings if you saved them to bios.

2) Only your phone can answer that as not all CPUs are created equal..try both..no big deal going from one to the other.

Good luck!
[Captivate Android Development] joeshmoe08:
Thanks for the quick reply shaolin. I'll see how it goes.
[Captivate Android Development] DAGr8:
lol sorry to hijack thread for this but im my defense it was late ( well for me anyways )
[Captivate Android Development] shaolin95:
Guys I am updating to Assonance 3.0 and have two questions:

Questions

#1 Since I am using one of the higher OCed Setiron Kernels instead of the one that comes with that ROM, is it recommended for me to install the ROM then without rebooting, install the Kernel or should I reboot then install the new kernel?

#2 How about the lag fix...I have been installing the new kernels without removing lag fix...is that a bad idea?
[Captivate Android Development] existz:
You can open your roms zip folder and put the zimage from setirons kernel in the /updates folder so when you install it will install the kernel you want instead of the one with the rom
[Captivate Android Development] SetiroN:
v1.5 OUT

- updated raspdeep's OC/UV to v300

- multiple performance levels:

100

200

400

800

1000

1200

1360 (GPU downclocked, don't worry performance improves anyway)

1400

1440 (GPU slightly overclocked)

1460 (GPU downclocked)

- Default clock at 1200MHz, additional frequencies can be enabled by editing /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table:

echo 0 0 1 0 1 1 1 1 1 1 > /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table will enable 1400MHz; remember that having too many perf levels is pointless and battery inefficient, so it'd be best to leave 1200MHz enabled and add just one additional frequency

in order to update the states table it's necessary to edit to 1 /sys/devices/system/cpu/cpu0/cpufreq/update_states (echo from terminal or by manually editing the file, just like the states table)

- added compatibility with Xan's voltage app v2.0 (please update, v1.9x wouldn't work correctly)

- reduced 14xxMHz default voltage to 1.3v

- updated CWM to include Hardcore's latest additions

- updated optimization scripts (now including battery optimizations and CIFS support)

- built-in support for ext2, ext3 and ext4 no-journaling (you will see a "configuration changed" screen if you had manually disabled journaling - select "No, enter recovery mode" and switch ext4 to ext4nj)

- built-in support for ext4 mount optimizations (writeback mode)

- v1.4.3

fixed 2e recovery, now completely functional

added 1350Mhz, 1400MHz and 1450MHz variants, only available as ODIN packages. The latter two have a default voltage of 1350mV. Keep using Xan's Voltage App v1.98b's 1200MHz setting to undervolt, higher frequencies replace the 1200MHz step, bear in mind the app doesn't show the updated frequency/voltage. Remember to reset said setting before upgrading and please realize how 14xxMHz will only run on few lucky devices

from now on there won't be a CWM version for 1350MHz+ and XT variants as well as a release integrating the modem, just install it on its own if necessary

To automatically enable additional frequencies at boot, after updating Xan's app to v2.0 recreate the boot script and add the following at the bottom:

#!/system/bin/sh

#set UV

echo "50 50 75 100 150 150 150 175 150 150 " > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

echo 1460000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

#set scheduler for stl, bml and mmc

for i in `ls /sys/block/stl*` /sys/block/bml* /sys/block/mmcblk*

do

echo "noop" > $i/queue/scheduler

done

echo 0 0 1 0 1 1 1 1 1 1 > /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table

echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/update_states
[Captivate Android Development] lpsi2000:
#1 yes, install it without rebooting if you can. I have been doing it this way for some time now. It save me the steps of replacing the kernel from the ROM package zip.

#2 I am doing the same thing because my lagfix is customized. As long as the kernels support the file system within your lagfix then there is no real reason to disable lagfix.

I also want to say thanks for spending the time in testing the various combination of UV settings in the latest round of kernels. You and a few others in this thread have helped me customized my own settings during my testing too.
[Captivate Android Development] shaolin95:
Thanks and you are welcome my friend...we all work together to figure out how to max our phones.

Setiron....my phone was flashing when I refreshed the page and saw the new kernel! LOL

I have a hockey game so someone is going to be late for the warm up skating session today! :D

I have never edited that table as per

Sorry for being a noob but how would you enable 1460?
[Captivate Android Development] Da_G:
1.5 and 1.5xt are both no-booters on both my captivates.

@SetiroN:

BTW, check your PM, I dropped you a msg about 2 weeks ago.

[edit: nevermind about GPS + Mobile AP. Turns out GPS Logging was the cause.]
[Captivate Android Development] crazililazn:
Funny, 1.4.3 1450 mhz wouldn't boot for me, but with 1.5 im currently running 1460 mhz with a 50 UV and it works fine. except, quadrant scores are really low.... O.o I'm getting like 1752...

EDIT: yep... im only getting 14.2 mflops on linpack too.... wtfreak...

EDIT 2: Now im stuck in a boot loop.... even after flashing back 1.4.2 1.28 ghz kernel... :/

EDIT 3: After reading Setiron's post again, i "enabled" the higher frequencies by adding those lines to the boot script, and that seems to have caused me to not be able to boot :/ Hmm, so for my phone, it seems that 1460 or 1440 is quite out of reach. Maybe i will try for 1.36-1.4 next time :]
[Captivate Android Development] JPxM0Dz:
hmmm glad I read this before flashing :confused:
[Captivate Android Development] shaolin95:
I am flashing now...will report back soon.
[Captivate Android Development] chrism0483:
Anyone using this kernel with. Axura if so did u flash with no issues and what did u run it at. Is it popossible to flash with 1460 or stay safe at 1350. If anyone has experience with this and axura. Or just in general I would appriciate some advice. Thank you kindly in advance :-)
[Captivate Android Development] existz:
wish there was still a 1280 in the mix, 1360 is unstable for me
[Captivate Android Development] shaolin95:
I cannot get the states_enabled_table to stick my new settings no matter what.

First mine is defaulting to 1000 not 1200 then when I try to change it it changes and I come out and back in adn the changes are there but after I reboot it goes back to the original config...
[Captivate Android Development] JPxM0Dz:
Same here... Default is also 1000
[Captivate Android Development] crazililazn:
When u go to the states_enabled file, it is like this at first

"0 0 0 0 0 1 1 1 1 1"

Now each of those 0 or 1 stands for the frequency u need to enable, from highest to lowest, left to right.

So for example, if u change the first 0 to a 1, like so

"1 0 0 0 0 1 1 1 1 1"

That will enable 1460

If you change it like this

"1 0 0 0 1 1 1 1 1 1"

that will enable 1200 and 1460.

So you must change the numbers according to the clock speed you want :]

BTW, my phone sucks at OCing!!! >:O even at no undervolt, it isnt stable at 1.4 ghz :[
[Captivate Android Development] existz:
im getting endless boot cycle.. i can go back 1.4.3, 1.4.2 and 1.4.1 and they all work, but if i do 1.5 or 1.5 xt with cwm or odin,...i disabled UV, no lagfix, no tweaks and set states to 1200 then tried 1000mhz via recovery...still wont boot
[Captivate Android Development] crazililazn:
got that too.. had to restore a nandroid restore...
[Captivate Android Development] MikeyMike01:
I have the 2.0 rc Voltage App, and it's force closing when I try and open it.

Sent from my Captivate.
[Captivate Android Development] crazililazn:
which kernel? For 1.4.3, that is normal. If u are using 1.4.3 revert back to 1.98b. If you are on 1.5... then that is odd O.o
[Captivate Android Development] existz:
So u did get 1.5 working after doing restore?
[Captivate Android Development] Stephenv1971:
1.5 was a no boot for me as well. Gonna try starting over....

Starting over did not help. it locked at boot. at least 1.4.3 works well for me.

Edit. So assonance was set for 1280. Which I can't do. Installed 1.4.3 1200. Booted up assonance, set 1200 at boot in voltage control, saved settings permanently, rebooted into recovery, installed 1.5 xt and it worked.
[Captivate Android Development] crazililazn:
oh no, the boot loop was from my data being corrupted by an unstable oc. First boot was perfectly fine.
[Captivate Android Development] existz:
Hmm well its still a no go...even formatted system, data and cache and done a clean full install then loaded 1.5 right after and still got the boot loop..but 1.4.3 down still works

Ugh would like the option of setting no journaling without having to do it manually with 1.5
[Captivate Android Development] Stephenv1971:
try limiting to 1200 using voltage control 2.2 and 1.4.3. Then install 1.5.
[Captivate Android Development] lpsi2000:
Something is wrong the Voltage app is not writing anything in init.d folder with this kernel and I switch to previous kernel the app is writing fine
[Captivate Android Development] existz:
Already done that, even tried 1000mhz..also tried UV disabled, no lagfix and no tweaks
[Captivate Android Development] lpsi2000:
@SetiroN

Can you implement file system features to the 1.4.3 series. Fore me the 1.4 of that series was working well. I am thinking on the statement you made where not everyone would be able to achieve certain speed. I think because of that you should try to implement features for lower clock speed like 1.4., 1.28. 1.2 etc...
[Captivate Android Development] existz:
I would love a 1.4.3 or 1.4.2 1280mhz 500hz with the new lagfixes and tweaks ...would be a perfect combo
[Captivate Android Development] crazililazn:
I believe 1.3 Ghz would be the perfect OC for most people, where it has good clock speed, and you can still undervolt a bit. I mean on my phone, for 1.36 ghz, i have to not undervolt for it to be stable. So IMO, a 1.3 ghz setting would be perfect for the people who have average overclocking cpu's.

Plus the fact that 1.3 ghz just looks so much nicer on paper than 1.28 ghz. So much neater. LOLOL
[Captivate Android Development] shaolin95:
Make sure to click where it says Mount W/R for me it was defaulting to W/O does not allowing me to right to it.
[Captivate Android Development] lpsi2000:
Where is that option? May be I have the wrong version Voltage Application (2.0RC2).
[Captivate Android Development] shaolin95:
This is from within the Root Explorer program I use to change the file in init.d folder. When you inside that folder look at the top of the window it should very likely currently reads Mounted R/O and you want it to be R/W
[Captivate Android Development] lpsi2000:
Oh, okay. Yes, I am familiar with that. So you are changing the file manually too. I am just wondering if anyone is actually using the App and had success.
[Captivate Android Development] shaolin95:
Well there are two steps here...first make sure the app is able to create the file in the init.d folder then you of course need to rename the file so it sticks after rebooting. With my ROM I rename it to s99_volt.sh
[Captivate Android Development] lpsi2000:
Yes, I have rename it S_98_volt.sh. Nonetheless, the I can get anything to work right with this new release. I think we might have taken a step backward, although it is step forward from a configuration and capabilities perspective. But it seems to be getting a bit complicated with the new release. It also could be me being lazy and tired right now:D
[Captivate Android Development] joeshmoe08:
Sorry for the trouble but is it safe to flash rom with 1.2.6 setiron and jp8 modem, then flash JK3 modem, then flash setiron 1.4.3 1280 all in one go without rebooting in between?
[Captivate Android Development] bryman27:
probably as long as you flash the rom first and then the kernel and modem
[Captivate Android Development] Ryukeima:
Read the warning in the first post about updating pre 1.4 to post 1.4
[Captivate Android Development] MarlowXim:
After testing 1.5 both versions. The frequencies with gpu overclocked or underclocked frequencies cause lockups or weird behaviours.

They will run fine for a certain time (10-15 mind of use) with no errors but for underclocked gpus. Opengl based graphics will lose sync. Not lag but the image will cease to move to the next frame, but system is still responsive meaning you can exit.

The overclocked gpu frequency will run. Until the image corrupts or the system locks up.

Cpu remains stable on 1440 and 1460 done with setcpu stability test. Performance is very close to each other I'm guessing your tweaking the fsb values now. Perhaps locking the gpu frequency to default may help stability in the future.
[Captivate Android Development] joeshmoe08:
Oh so I specifically have to flash the modem after the kernel?

To Ryukeima:

Ya I read it. The only thing I have to do is reset UV settings but since I am never going to set them (I'll flash the new kernel immediately after rom) it shouldn't be a problem